Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Block device /dev/sda3 is not a valid root device
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Installing Gentoo
View previous topic :: View next topic  
Author Message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Sat Oct 20, 2012 4:48 pm    Post subject: Block device /dev/sda3 is not a valid root device Reply with quote

I installed a new system and it fails with the following error:
Code:

!! Block device /dev/sda3 is not a valid root device...
!! Could not find the root block device in .
Please specify another value or: press Enter for the same, type "shell" for shell, or "q" to skip...
root block device() ::


Code:
cat lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series]
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 09)
03:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)


Configuratio of grub.conf

Code:
default 0
timeout 10
splashimage=(hd0,0)/boot/grub/splash.xpm.gz

title Gentoo Linux
root (hd0,0)
kernel /boot/kernel-genkernel-x86_64-3.4.9-gentoo root=/dev/ram0 init=linuxrc ramdisk=8192 real_root=/dev/sda3 "rootfstype=ext4"
initrd /boot/initramfs-genkernel-x86_64-3.4.9-gentoo

# vim:ft=conf:


Code:

/dev/sda1            /boot               ext3            defaults,noatime 1 2
/dev/sda3            /                     ext4            defaults, noatime 0 1
/dev/sda2            none                swap            sw              0 0
/dev/cdrom          /mnt/cdrom       auto            noauto,ro       0 0
none                   /dev/bus/usb     usbfs           devgid=1014,devmode=664 0 0
proc                    /proc               proc            defaults        0 0
shm                    /dev/shm          tmpfs           nodev,nosuid,noexec 0 0


I am not sure any more where is the problem.

Everything looks ok in the kernel. I enabled scsi support, also scsi low level, sata.

Regards
Queen
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43194
Location: 56N 3W

PostPosted: Sat Oct 20, 2012 4:56 pm    Post subject: Reply with quote

queen,

Code:
!! Could not find the root block device in .
This line is important. It should list all the block devices the kernel can see.
In your case none.

Code:
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)

You need SCSI Disk support built in, the AHCI driver build in and in some cases the AHCI Platform Driver built in.

"rootfstype=ext4" does not need the quotes and should not be needed. It just stops the kernel trying ext3 and ext2 before ext4.

Fix your kernel and try again.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sat Oct 20, 2012 6:12 pm    Post subject: Reply with quote

boot cd, mount gentoo partitions, enter the chroot, nominally:
Code:
  mount /dev/sda3 /mnt/gentoo
mount /dev/sda1 /mnt/gentoo/boot
cp /etc/resolv.conf /mnt/gentoo/etc/resolv.conf
mount -t proc none /mnt/gentoo/proc
mount --rbind /sys /mnt/gentoo/sys
mount --rbind /dev /mnt/gentoo/dev
chroot /mnt/gentoo /bin/bash
env-update
source /etc/profile
export PS1="(chroot) $PS1"
then
Code:
genkernel --menuconfig all
edit menuconfig to remove the bad module
Quote:
Device Drivers --->
SCSI device support --->
[ ] SCSI low-level drivers --->
which will eliminate the offending <M> LibFC module as well as a lot of SCSI low-level drivers for equipments you don't have. Exit out of menuconfig saving the configuration and allow genkernel to complete. Then
Code:
exit
reboot

_________________
Defund the FCC.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Thu Oct 25, 2012 11:24 am    Post subject: Reply with quote

Sorry for the late reply.

I did both recommendations of DONAHUE and NeddySeagoon but still it doesn't boot. Gets stuck at the same place.

I attach the configurations:

Code:
 grep -i sata .config

CONFIG_SATA_PMP=y
CONFIG_SATA_AHCI=y
CONFIG_SATA_AHCI_PLATFORM=y
CONFIG_SATA_ACARD_AHCI=y


Code:
 grep -i scsi .config

CONFIG_SCSI_MOD=y
CONFIG_SCSI=y
CONFIG_SCSI_DMA=y
CONFIG_SCSI_TGT=y
CONFIG_SCSI_NETLINK=y
CONFIG_SCSI_PROC_FS=y
CONFIG_SCSI_MULTI_LUN=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_SCSI_WAIT_SCAN=m
CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SCSI_FC_ATTRS=y
CONFIG_SCSI_SAS_ATTRS=y


Is there something wrong with this configuration? Any other suggestions?

Queen
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43194
Location: 56N 3W

PostPosted: Thu Oct 25, 2012 7:11 pm    Post subject: Reply with quote

queen,

Please put your entire kernel .config on a pastebin and tell us the link.
Options you have off are just as important as the options you have on, so we need to know about them too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Sat Oct 27, 2012 11:19 pm    Post subject: Reply with quote

NeddySeagoon wrote:
queen,

Please put your entire kernel .config on a pastebin and tell us the link.
Options you have off are just as important as the options you have on, so we need to know about them too.


Thanks. Here is the link:

http://pastebin.com/S0PWKL2y
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7090
Location: Saint Amant, Acadiana

PostPosted: Sat Oct 27, 2012 11:34 pm    Post subject: Reply with quote

Code:
# CONFIG_MSDOS_PARTITION is not set

Is this intentional, you sure you do not need it?
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sun Oct 28, 2012 1:04 am    Post subject: Reply with quote

I seem to see a 32 vs 64 bit problem in your kernel config.
You have:
Quote:
# Automatically generated file; DO NOT EDIT.
# Linux/x86 3.4.9-gentoo Kernel Configuration
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
The title suggesting the advanced 32 bit version. But the settings are for 64 bit.

Default 64 bit:
Quote:
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.4.9-gentoo Kernel Configuration
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"


64 bit Pappy's kenel-seeds.org has:
Quote:
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.4.9-gentoo Kernel Configuration
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"


32 bit Pappy's kenel-seeds.org has:
Quote:
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 3.4.9-gentoo Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"


Did you change any of these settings?
Cross check /etc/make.conf and /etc/portage/make.conf (ACCEPT_KEYWORDS=) and the install cd and the stage 3 tarball ( stage3- ?.tar.bz2 ) for the same (32 or 64) bitness throughout.
If this helps find the problem, I'd wipe the install and do over.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Sun Oct 28, 2012 7:19 am    Post subject: Reply with quote

Jaglover wrote:
Code:
# CONFIG_MSDOS_PARTITION is not set

Is this intentional, you sure you do not need it?


Mistake. I didn't notice. Will correct. Thanks for tip.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Sun Oct 28, 2012 2:48 pm    Post subject: Reply with quote

Thanks Donahue for the tip. I didn't notice it. Here are the details I have for /etc/portage/make.conf

Code:

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.
CFLAGS="-march=native -O2 -pipe"
CXXFLAGS="${CFLAGS}"
# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult http://www.gentoo.org/doc/en/change-chost.xml before changing.
CHOST="x86_64-pc-linux-gnu"
# These are the USE flags that were used in addition to what is provided by the
# profile used for building.
USE="mmx sse sse2 bluetooth alsa"
MAKEOPTS="-j5"

GENTOO_MIRRORS="http://mirror.isoc.org.il/pub/gentoo/"

ACCEPT_KEYWORDS="x86"
PORTAGE_TMPDIR=/var/tmp/portage
PORTDIR=/usr/portage
DISTDIR=${PORTDIR}/distfiles
PKGDIR=${PORTDIR}/packages
PORT_LOGDIR=/var/log/portage
PORTDIR_OVERLAY=/usr/local/portage
#SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
#SYNC="rsync://rsync.belnet.be/gentoo-portage"
#rsync://rsync.europe.gentoo.org/gentoo-portage
#SYNC="rsync://rsync.jp.gentoo.org/gentoo-portage"
# rsync://rsync.namerica.gentoo.org/gentoo-portage rsync://linux.rz.ruhr-uni-bochum.de/gentoo-portage/ rsync://trupetti.atm.tut.fi/gentoo-portage/ rsync://mirror.hamakor.org.il/gentoo-portage"
PORTAGE_RSYNC_RETRIES="5"
PORTAGE_RSYNC_TIMEOUT=60
PORTAGE_NICENESS=3
AUTOCLEAN="yes"
PORTAGE_TMPFS="/dev/shm"
FEATURES="sandbox ccache distcc distlocks"
CCACHE_SIZE="1G"
PORTAGE_ELOG_CLASSES="error log"
PORTAGE_ELOG_SYSTEM="save"
PORTAGE_ELOG_MAILSUBJECT="package \${PACKAGE} merged on \${HOST} with notice"

PORTAGE_RSYNC_INITIAL_TIMEOUT=500
LINGUAS="en,he"
INPUT_DEVICES="evdev keyboard mouse"
VIDEO_CARDS="fglrx,intel"
ALSA_CARDS="intel8x0,intel8x0m"
#GENTOO_MIRRORS="http://mirror.netcologne.de/gentoo"
#GENTOO_MIRRORS="http://mirror.hamakor.org.il/pub/mirrors/gentoo-portage"
#ACCEPT_LICENSE="dlj-1.1"
ACCEPT_LICENSE="*"
SYNC="rsync://rsync11.de.gentoo.org/gentoo-portage"
EMERGE_DEFAULT_OPTS="--autounmask=n"


The uname of the livecd is:

Code:
cat uname-a
Linux Gentoo-2012 3.3.0-gentoo-r1 #1 SMP Fri Mar 30 06:21:40 UTC 2012 x86_64 Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz GenuineIntel GNU/Linux


I don't remember what was the stage3. I removed it. Is there a way to find out before I wipe out everything?

I remember that when I set the ACCEPT_KEYWORDS I tried to use x86_64 and got an error. Now I see on some document that I should have chosen amd64.

Regarding 32 bit: I would like to have in the future the option to compile some programs of 32bit that don't support 64 bit. What would be the best approach?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43194
Location: 56N 3W

PostPosted: Sun Oct 28, 2012 3:31 pm    Post subject: Reply with quote

queen,

If you choose a standard 64 bit profile (not no-multilib) you will get libraries to support 32 and 64 bit code.
In the kernel you need to choose 32 bit emulation too, so the kernel will support 32 bit code.

Thats not the same as x32 support. x32 is a hybrid 64 bit and 32 bit system.
It provides for a 32 bit address space, uses 32 bit pointers but you get the 64 bit instructions and additional registers of a 64 bit CPU.
Its supposed to be both faster and smaller than pure 64 bit ... bits its new. You need a glibc that supports it, a toolchain that can build it and a stage3 to get you started.

Go for a standard amd64 multilib install. Thats probably what you have now, so just fix your kernel. There is no need to wipe anything.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sun Oct 28, 2012 3:39 pm    Post subject: Reply with quote

the default 64 bit amd64 x86_64 install by the handbook is multilib meaning it can run both 64 and 32 bit programs.
ACCEPT_KEYWORDS="x86" in the make.conf suggests that the stage3 tarball was 32bit or if the tarball was 64 bit the make.conf was edited. In any case, any packages emerged have been x86 32 bit versions.
Still recommend a do over. 64 bit install cd, install-amd64-minimal-20121013.iso stage 3.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43194
Location: 56N 3W

PostPosted: Sun Oct 28, 2012 3:53 pm    Post subject: Reply with quote

DONAHUE wrote:
ACCEPT_KEYWORDS="x86" in the make.conf ...

Oops I missed that.

However
Code:
CHOST="x86_64-pc-linux-gnu
says it was a 64 bit stage3 tarball.
Changing the CHOST kills the toolchain, we can be sure that its not been edited.

As
Code:
CFLAGS="-march=native -O2 -pipe"
is set, the compiler will have produced 64 bit code. So, anything that is built is OK.

Code:
ACCEPT_KEYWORDS="x86"
is "mostly harmless" - it makes only packages keyworded for x86 available.
As the amd64 tree is mostly ahead of the x86 tree, fixing the ACCEPT_KEYWORDS and doing
Code:
emerge @world -uDNav --with-bdeps=y --keep-going
will bring everything up to the expected versions.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Sun Oct 28, 2012 5:14 pm    Post subject: Reply with quote

NeddySeagoon wrote:
DONAHUE wrote:
ACCEPT_KEYWORDS="x86" in the make.conf ...

Oops I missed that.

However
Code:
CHOST="x86_64-pc-linux-gnu
says it was a 64 bit stage3 tarball.
Changing the CHOST kills the toolchain, we can be sure that its not been edited.

As
Code:
CFLAGS="-march=native -O2 -pipe"
is set, the compiler will have produced 64 bit code. So, anything that is built is OK.

Code:
ACCEPT_KEYWORDS="x86"
is "mostly harmless" - it makes only packages keyworded for x86 available.
As the amd64 tree is mostly ahead of the x86 tree, fixing the ACCEPT_KEYWORDS and doing
Code:
emerge @world -uDNav --with-bdeps=y --keep-going
will bring everything up to the expected versions.


I"ll fix the ACCEPT_KEYWORDS=amd64 and emerge world. Thanks. Do you think this will solve the problem of the boot?
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43194
Location: 56N 3W

PostPosted: Sun Oct 28, 2012 5:24 pm    Post subject: Reply with quote

queen,

It won't fix the boot issue. Thats a problem with either your kernel or your grub.conf
Post your
Code:
fdisk -l
to see if we can narrow the boot issue down a little.

Reinstalling won't fix it either - you will just have an opportunity to not make the same mistake again.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sun Oct 28, 2012 7:31 pm    Post subject: Reply with quote

menuconfig:
Quote:
File systems --->
< > Second extended fs support
< > Ext3 journalling file system support
<*> The Extended 4 (ext4) filesystem
[*] Use ext4 for ext2/ext3 file systems (NEW)
[*] Ext4 extended attributes (NEW)
[ ] Ext4 POSIX Access Control Lists (NEW)
[ ] Ext4 Security Labels (NEW)
[ ] EXT4 debugging support (NEW)
and/or
Quote:
rootfstype=ext4
on the kernel line in grub.conf have been reported to cure ext4 root problems
_________________
Defund the FCC.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Sun Oct 28, 2012 9:13 pm    Post subject: Reply with quote

DONAHUE wrote:
the default 64 bit amd64 x86_64 install by the handbook is multilib meaning it can run both 64 and 32 bit programs.
ACCEPT_KEYWORDS="x86" in the make.conf suggests that the stage3 tarball was 32bit or if the tarball was 64 bit the make.conf was edited. In any case, any packages emerged have been x86 32 bit versions.
Still recommend a do over. 64 bit install cd, install-amd64-minimal-20121013.iso stage 3.


DONAHUE, I edited make.conf. I added the cflags to fit the i7 and I also edited ACCEPT_KEYWORDS and mirrors, etc. First I tried x86_64 which gave me an error and then I corrected to x86.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Sun Oct 28, 2012 9:22 pm    Post subject: Reply with quote

NeddySeagoon wrote:
queen,

It won't fix the boot issue. Thats a problem with either your kernel or your grub.conf
Post your
Code:
fdisk -l
to see if we can narrow the boot issue down a little.

Reinstalling won't fix it either - you will just have an opportunity to not make the same mistake again.


Code:
cat fdisk

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xe43c923a

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      206847      102400   83  Linux
/dev/sda2          206848    33761279    16777216   82  Linux swap / Solaris
/dev/sda3        33761280  1953525167   959881944   83  Linux
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43194
Location: 56N 3W

PostPosted: Sun Oct 28, 2012 9:35 pm    Post subject: Reply with quote

queen,

queen wrote:
I edited make.conf. I added the cflags to fit the i7 and I also edited ACCEPT_KEYWORDS and mirrors, etc. First I tried x86_64 which gave me an error and then I corrected to x86.
Close but no cigar,

ACCEPT_KEYWORDS="x86" gives you packages that are keyworded for 32 bit Intel/AMD CPUs
You want ACCEPT_KEYWORDS="amd64" even on an Intel system.
The history behind that is Intel were first with a 64 bit CPU (Itainium) but it was not backwards compatible and the emulator that Intel released my thins very slow.
AMD developed a 64 bit CPU that could run existing 32 bit code too. Intel licenced the AMD design and the rest is history.

The x86_64 is the arch in the kernel for all amd64 CPUs, including Intel ones.

Do you only have a single HDD?
For some reason, I thought you had two.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Sun Oct 28, 2012 10:43 pm    Post subject: Reply with quote

Recommend:
Quote:
Device Drivers --->
<*> Serial ATA and Parallel ATA drivers --->
--- Serial ATA and Parallel ATA drivers
[ ] Verbose ATA error reporting
[*] ATA ACPI Support
[ ] SATA Port Multiplier support
*** Controllers with non-SFF native interface ***
<*> AHCI SATA support
< > Platform AHCI SATA support
< > Initio 162x SATA support
< > ACard AHCI variant (ATP 8620)
< > Silicon Image 3124/3132 SATA support
[*] ATA SFF support
*** SFF controllers with custom DMA interface ***
< > Pacific Digital ADMA support
< > Pacific Digital SATA QStor support
< > Promise SATA SX4 support (Experimental)
[*] ATA BMDMA support
*** SATA SFF controllers with BMDMA ***
<*> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
< > Marvell SATA support
< > NVIDIA SATA support
< > Promise SATA TX2/TX4 support
< > Silicon Image SATA support
< > SiS 964/965/966/180 SATA support
< > ServerWorks Frodo / Apple K2 SATA support
< > ULi Electronics SATA support
< > VIA SATA support
< > VITESSE VSC-7174 / INTEL 31244 SATA support
*** PATA SFF controllers with BMDMA ***
< > ALi PATA support
< > AMD/NVidia PATA support
< > ARASAN CompactFlash PATA Controller Support
< > ARTOP 6210/6260 PATA support
< > ATI PATA support
< > ARTOP/Acard ATP867X PATA support
< > CMD64x PATA support
< > CS5510/5520 PATA support
< > CS5530 PATA support
< > CS5536 PATA support
< > Cypress CY82C693 PATA support (Very Experimental)
< > EFAR SLC90E66 support
< > HPT 366/368 PATA support
< > HPT 370/370A/371/372/374/302 PATA support
< > HPT 371N/372N/302N PATA support
< > HPT 343/363 PATA support
< > IT8213 PATA support (Experimental)
< > IT8211/2 PATA support
< > JMicron PATA support
< > Marvell PATA support via legacy mode
< > NETCELL Revolution RAID support
< > Ninja32/Delkin Cardbus ATA support
< > Nat Semi NS87415 PATA support
< > Intel PATA old PIIX support
< > OPTI FireStar PATA support (Very Experimental)
< > Promise PATA 2027x support
< > Older Promise PATA controller support
< > RADISYS 82600 PATA support (Experimental)
< > RDC PATA support
< > SC1200 PATA support
< > Intel SCH PATA support
< > SERVERWORKS OSB4/CSB5/CSB6/HT1000 PATA support
< > CMD / Silicon Image 680 PATA support
< > SiS PATA support
< > Toshiba Piccolo support (Experimental)
< > Compaq Triflex PATA support
< > VIA PATA support
< > Winbond SL82C105 PATA support
*** PIO-only SFF controllers ***
< > CMD640 PCI PATA support (Experimental)
< > Intel PATA MPIIX support
< > Nat Semi NS87410 PATA support
< > OPTI621/6215 PATA support (Very Experimental)
< > PC Tech RZ1000 PATA support
*** Generic fallback / legacy drivers ***
< > ACPI firmware driver for PATA
< > Generic ATA support
< > Legacy ISA PATA support (Experimental)
to cover the driver bases. ahci is likely to be your driver. ATA_PIIX may be your driver. If bios is set to legacy ide; ATA_PIIX is your driver until you change the bios setting to the faster and better ahci mode. If you do not have a sata pmp you don't want to select it.
Your lspci does not show a fusion mpt controller but you have:
Quote:
[*] Fusion MPT device support --->
--- Fusion MPT device support
<*> Fusion MPT ScsiHost drivers for SPI
<*> Fusion MPT ScsiHost drivers for FC
<*> Fusion MPT ScsiHost drivers for SAS
(128) Maximum number of scatter gather entries (16 - 128) (NEW)
<*> Fusion MPT misc device (ioctl) driver
[ ] Fusion MPT logging facility (NEW)

_________________
Defund the FCC.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Mon Oct 29, 2012 10:00 am    Post subject: Reply with quote

NeddySeagoon wrote:
queen,

queen wrote:
I edited make.conf. I added the cflags to fit the i7 and I also edited ACCEPT_KEYWORDS and mirrors, etc. First I tried x86_64 which gave me an error and then I corrected to x86.
Close but no cigar,

ACCEPT_KEYWORDS="x86" gives you packages that are keyworded for 32 bit Intel/AMD CPUs
You want ACCEPT_KEYWORDS="amd64" even on an Intel system.
The history behind that is Intel were first with a 64 bit CPU (Itainium) but it was not backwards compatible and the emulator that Intel released my thins very slow.
AMD developed a 64 bit CPU that could run existing 32 bit code too. Intel licenced the AMD design and the rest is history.

The x86_64 is the arch in the kernel for all amd64 CPUs, including Intel ones.

Do you only have a single HDD?
For some reason, I thought you had two.


Only one HDD. 1TB. ;-)
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Mon Oct 29, 2012 11:00 am    Post subject: Reply with quote

DONAHUE wrote:
Recommend:
Quote:
Device Drivers --->
<*> Serial ATA and Parallel ATA drivers --->
--- Serial ATA and Parallel ATA drivers
[ ] Verbose ATA error reporting
[*] ATA ACPI Support
[ ] SATA Port Multiplier support
*** Controllers with non-SFF native interface ***
<*> AHCI SATA support
< > Platform AHCI SATA support
< > Initio 162x SATA support
< > ACard AHCI variant (ATP 8620)
< > Silicon Image 3124/3132 SATA support
[*] ATA SFF support
*** SFF controllers with custom DMA interface ***
< > Pacific Digital ADMA support
< > Pacific Digital SATA QStor support
< > Promise SATA SX4 support (Experimental)
[*] ATA BMDMA support
*** SATA SFF controllers with BMDMA ***
<*> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support
< > Marvell SATA support
< > NVIDIA SATA support
< > Promise SATA TX2/TX4 support
< > Silicon Image SATA support
< > SiS 964/965/966/180 SATA support
< > ServerWorks Frodo / Apple K2 SATA support
< > ULi Electronics SATA support
< > VIA SATA support
< > VITESSE VSC-7174 / INTEL 31244 SATA support
*** PATA SFF controllers with BMDMA ***
< > ALi PATA support
< > AMD/NVidia PATA support
< > ARASAN CompactFlash PATA Controller Support
< > ARTOP 6210/6260 PATA support
< > ATI PATA support
< > ARTOP/Acard ATP867X PATA support
< > CMD64x PATA support
< > CS5510/5520 PATA support
< > CS5530 PATA support
< > CS5536 PATA support
< > Cypress CY82C693 PATA support (Very Experimental)
< > EFAR SLC90E66 support
< > HPT 366/368 PATA support
< > HPT 370/370A/371/372/374/302 PATA support
< > HPT 371N/372N/302N PATA support
< > HPT 343/363 PATA support
< > IT8213 PATA support (Experimental)
< > IT8211/2 PATA support
< > JMicron PATA support
< > Marvell PATA support via legacy mode
< > NETCELL Revolution RAID support
< > Ninja32/Delkin Cardbus ATA support
< > Nat Semi NS87415 PATA support
< > Intel PATA old PIIX support
< > OPTI FireStar PATA support (Very Experimental)
< > Promise PATA 2027x support
< > Older Promise PATA controller support
< > RADISYS 82600 PATA support (Experimental)
< > RDC PATA support
< > SC1200 PATA support
< > Intel SCH PATA support
< > SERVERWORKS OSB4/CSB5/CSB6/HT1000 PATA support
< > CMD / Silicon Image 680 PATA support
< > SiS PATA support
< > Toshiba Piccolo support (Experimental)
< > Compaq Triflex PATA support
< > VIA PATA support
< > Winbond SL82C105 PATA support
*** PIO-only SFF controllers ***
< > CMD640 PCI PATA support (Experimental)
< > Intel PATA MPIIX support
< > Nat Semi NS87410 PATA support
< > OPTI621/6215 PATA support (Very Experimental)
< > PC Tech RZ1000 PATA support
*** Generic fallback / legacy drivers ***
< > ACPI firmware driver for PATA
< > Generic ATA support
< > Legacy ISA PATA support (Experimental)
to cover the driver bases. ahci is likely to be your driver. ATA_PIIX may be your driver. If bios is set to legacy ide; ATA_PIIX is your driver until you change the bios setting to the faster and better ahci mode. If you do not have a sata pmp you don't want to select it.
Your lspci does not show a fusion mpt controller but you have:
Quote:
[*] Fusion MPT device support --->
--- Fusion MPT device support
<*> Fusion MPT ScsiHost drivers for SPI
<*> Fusion MPT ScsiHost drivers for FC
<*> Fusion MPT ScsiHost drivers for SAS
(128) Maximum number of scatter gather entries (16 - 128) (NEW)
<*> Fusion MPT misc device (ioctl) driver
[ ] Fusion MPT logging facility (NEW)


DONAHUE, according to
Code:
 lspci -k

00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
        Kernel driver in use: agpgart-intel
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
        Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
        Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
        Kernel driver in use: ehci_hcd
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
        Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4)
        Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4)
        Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
        Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
        Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series]
        Subsystem: Samsung Electronics Co Ltd Device c0d8
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 09)
        Subsystem: Samsung Electronics Co Ltd Device c0da
        Kernel driver in use: r8169
03:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)
        Subsystem: Samsung Electronics Co Ltd Device 4105
        Kernel driver in use: ath9k
it uses ahci. So I need to select <*> Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support too? I also checked the bios and it has ahci enabled.
Back to top
View user's profile Send private message
DONAHUE
Watchman
Watchman


Joined: 09 Dec 2006
Posts: 7552
Location: Goose Creek SC

PostPosted: Mon Oct 29, 2012 2:45 pm    Post subject: Reply with quote

https://forums.gentoo.org/viewtopic-p-4570091.html#4570091 not if you are sure your hardware is ahci only.
_________________
Defund the FCC.
Back to top
View user's profile Send private message
queen
Veteran
Veteran


Joined: 19 Jul 2005
Posts: 1626

PostPosted: Mon Oct 29, 2012 4:03 pm    Post subject: Reply with quote

DONAHUE wrote:
https://forums.gentoo.org/viewtopic-p-4570091.html#4570091 not if you are sure your hardware is ahci only.


Thanks for the link. I verified both with lspi, lspci -k and bios. They all show ahci.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43194
Location: 56N 3W

PostPosted: Mon Oct 29, 2012 7:33 pm    Post subject: Reply with quote

queen,
Code:
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
        Subsystem: Samsung Electronics Co Ltd Device c0d8
        Kernel driver in use: ahci


Tells that you need SCSI Disk and the AHCI driver as built ins. You may also need AHCI Platform too. That seems to be BIOS dependent.

Your fdisk tells that you really have a MSDOS Partition Table, so you need support for it. That was missing further up the thread.
You also need your root filesystem support built in. That covers the hardware settings.

The boot process won't get very far after root is mounted unless you also have DEVTMPFS and mount DEVTMPFS. If you miss that, udev will hate you.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Installing Gentoo All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum