[gentoo-user] grub on a SATA drive

[gentoo-user] grub on a SATA drive

[maxim wexler]

Hello everybody,

I've setup grub on /dev/sda2 of a new SATA HD, listed
in dmesg as /dev/sda. The other HDs are /dev/hda,
which does present boot duty and /dev/hdb, containing
/ etc.

Before moving files from /dev/hdb, which apparently
has an un-fixable boot sector, to /dev/sda, I'd like
to be able to boot using the SATA drive then ditch
/dev/hda.

I note grub doesn't like root(sd0,1), returns "Error
23: Error while parsing number".

But what do I call it? hd0 and hd1 are taken.

-mw


	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 227 bytes --]

On Thu, 24 Nov 2005 08:31:37 -0800 (PST), maxim wexler wrote:

> But what do I call it? hd0 and hd1 are taken.

hd2, it's the third hard drive.


-- 
Neil Bothwick

Me? FAT? No, just horizontally disproportionate...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] grub on a SATA drive

[Glenn Enright]

On Fri, 25 Nov 2005 05:31, maxim wexler wrote:

> I note grub doesn't like root(sd0,1), returns "Error
> 23: Error while parsing number".
>
> But what do I call it? hd0 and hd1 are taken.
>
> -mw

Just to make sure, remember that grub has to be installed in the boot sector 
of your drive and it needs a built in reference so it can find the config 
file and stage2-*s. Assuming you followed the install guides on gentoo.org 
you would have looked through the following
http://www.gentoo.org/doc/en/handbook/2005.0/handbook-x86.xml?part=1&chap=10#doc_chap2

Also consider that grub doesn't understand sda or hda terminology, only 
numbers. The stuff on the kernel line is for the kernel to pick up and use in 
conjunction with your /etc/fstab file
-- 
Sigh.  I like to think it's just the Linux people who want to be on
the "leading edge" so bad they walk right off the precipice.
	-- Craig E. Groeschel
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[Petr Kocmid]

On Thursday 24 of November 2005 17:31, maxim wexler wrote:

> But what do I call it? hd0 and hd1 are taken.

It may well depend on your chipset configuration, number of actually connected 
drives and bios boot settings. On my board, there are 2 PATA and 1 SATA 
channels on the same controller. In linux kernel, PATA is hda and hdb, SATA 
is hdc, no matter what drives are actually connected. When i migrated my 
installation from PATA hda to SATA hdc, grub detected hda as hd0 and hdc as 
hd1 before, but once I removed parallel drive, SATA become hd0 in grub (but 
still hdc in linux), since it is first (boot) bios drive. So I needed to fix 
grub config to hd0 and change a root= kernel parameter to hdc, since grub 
insists hd0 should be hda even if there is no drive connected on PATA:

root (hd0,0)
kernel /boot/bzImage-2.6.10 root=/dev/hdc1

Also, I did grub setup on SATA MBS from booted grub shell, not in linux, 
because what it sees is what it gets then.

Hope this may help you.

-- 
Petr
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[maxim wexler]

--- Petr Kocmid <Petr.Kocmid@project-bhairava.org>
wrote:

> On Thursday 24 of November 2005 17:31, maxim wexler
> wrote:
> 
> > But what do I call it? hd0 and hd1 are taken.
> 
> It may well depend on your chipset configuration,
> number of actually connected 
> drives and bios boot settings. On my board, there
> are 2 PATA and 1 SATA 
> channels on the same controller. In linux kernel,
> PATA is hda and hdb, SATA 
> is hdc, no matter what drives are actually
> connected. When i migrated my 
> installation from PATA hda to SATA hdc, grub
> detected hda as hd0 and hdc as 
> hd1 before, but once I removed parallel drive, SATA
> become hd0 in grub (but 
> still hdc in linux), since it is first (boot) bios
> drive. So I needed to fix 
> grub config to hd0 and change a root= kernel
> parameter to hdc, since grub 
> insists hd0 should be hda even if there is no drive
> connected on PATA:
> 
> root (hd0,0)
> kernel /boot/bzImage-2.6.10 root=/dev/hdc1

is this a gentoo box?

> 
> Also, I did grub setup on SATA MBS 

what's "MBS"?

> from booted grub shell, not in linux, 
> because what it sees is what it gets then.
> 
> Hope this may help you.

Thanks for your suggestions. Here's where things
stand:

I did a fresh 2005.1 stage3 install onto the SATA
drive without a hitch. I removed the ide drive, so
there's only one hd.

In dmesg the drive comes up as /dev/sda
   sda1(Macro$haft) sda2(/boot) < sda5(swap) sda6(/)
sda7(home)>

When I boot w/ the grub floppy I do:

grub> root (hd0,1)
      Fs is ext2, part type 0x83
grub> kernel /vmlinuz root=/dev/sda6
      [Linux-bzImage, setup=0x120, size 0x1463b31]

...so far, so good...

grub> boot

and get:

...VFS: Cannot open root device "sda6" or unknown
block (0,0)
Please append correct "root" boot option
Kernel Panic-not syncing: VFS: Unable to mount root fs
on unknown block (0,0)

So I'm at a loss. The grub commands went alright.
Wouldn't I get an error if one of the commands was
wrong? Don't know what's meant by "unknown block
(0,0)". Is it saying it's trying to mount / on
/dev/sda1? Doesn't make sense.

WinXP occupies 20G at /dev/sda1 and it boots OK. LBA
is activated and this is a brand new, modern drive on
a fairly up-to-date Asus, K8N, skt 754 mobo, so it
can't be that old BIOS drive limit from the 90s.

-mw

> 
> -- 
> Petr
> -- 
> gentoo-user@gentoo.org mailing list
> 
> 



		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free. 
http://music.yahoo.com/unlimited/
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[Heinz Sporn]

Am Montag, den 28.11.2005, 22:34 -0800 schrieb maxim wexler:
> 
> --- Petr Kocmid <Petr.Kocmid@project-bhairava.org>
> wrote:
> 
> > On Thursday 24 of November 2005 17:31, maxim wexler
> > wrote:
> > 
> > > But what do I call it? hd0 and hd1 are taken.
> > 
> > It may well depend on your chipset configuration,
> > number of actually connected 
> > drives and bios boot settings. On my board, there
> > are 2 PATA and 1 SATA 
> > channels on the same controller. In linux kernel,
> > PATA is hda and hdb, SATA 
> > is hdc, no matter what drives are actually
> > connected. When i migrated my 
> > installation from PATA hda to SATA hdc, grub
> > detected hda as hd0 and hdc as 
> > hd1 before, but once I removed parallel drive, SATA
> > become hd0 in grub (but 
> > still hdc in linux), since it is first (boot) bios
> > drive. So I needed to fix 
> > grub config to hd0 and change a root= kernel
> > parameter to hdc, since grub 
> > insists hd0 should be hda even if there is no drive
> > connected on PATA:
> > 
> > root (hd0,0)
> > kernel /boot/bzImage-2.6.10 root=/dev/hdc1
> 
> is this a gentoo box?
> 
> > 
> > Also, I did grub setup on SATA MBS 
> 
> what's "MBS"?
> 
> > from booted grub shell, not in linux, 
> > because what it sees is what it gets then.
> > 
> > Hope this may help you.
> 
> Thanks for your suggestions. Here's where things
> stand:
> 
> I did a fresh 2005.1 stage3 install onto the SATA
> drive without a hitch. I removed the ide drive, so
> there's only one hd.
> 
> In dmesg the drive comes up as /dev/sda
>    sda1(Macro$haft) sda2(/boot) < sda5(swap) sda6(/)
> sda7(home)>
> 
> When I boot w/ the grub floppy I do:
> 
> grub> root (hd0,1)
>       Fs is ext2, part type 0x83
> grub> kernel /vmlinuz root=/dev/sda6
>       [Linux-bzImage, setup=0x120, size 0x1463b31]

Shouldn't that read root=/dev/sda2 since your kernel obviously sits
in /boot == /dev/sda2 ? The root paramter should define the place where
your kernel / grub stage files reside IIRC and not where your root
filesystem is located. Naming the parameter root is quite misleading
though.

> 
> ...so far, so good...
> 
> grub> boot
> 
> and get:
> 
> ...VFS: Cannot open root device "sda6" or unknown
> block (0,0)
> Please append correct "root" boot option
> Kernel Panic-not syncing: VFS: Unable to mount root fs
> on unknown block (0,0)
> 
> So I'm at a loss. The grub commands went alright.
> Wouldn't I get an error if one of the commands was
> wrong? Don't know what's meant by "unknown block
> (0,0)". Is it saying it's trying to mount / on
> /dev/sda1? Doesn't make sense.
> 
> WinXP occupies 20G at /dev/sda1 and it boots OK. LBA
> is activated and this is a brand new, modern drive on
> a fairly up-to-date Asus, K8N, skt 754 mobo, so it
> can't be that old BIOS drive limit from the 90s.
> 
> -mw
> 
> > 
> > -- 
> > Petr
> > -- 
> > gentoo-user@gentoo.org mailing list
> > 
> > 
> 
> 
> 
> 		
> __________________________________ 
> Yahoo! Music Unlimited 
> Access over 1 million songs. Try it free. 
> http://music.yahoo.com/unlimited/
-- 
Mit freundlichen Grüßen

Heinz Sporn

SPORN it-freelancing

Mobile:  ++43 (0)699 / 127 827 07
Email:   heinz.sporn@sporn-it.com
         heinz.sporn@utanet.at
Website: http://www.sporn-it.com
Snail:   Steyrer Str. 20
         A-4540 Bad Hall
         Austria / Europe

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[Glenn Enright]

On Tue, 29 Nov 2005 19:45, Heinz Sporn wrote:
<snip>
> > When I boot w/ the grub floppy I do:
> >
> > grub> root (hd0,1)
> >       Fs is ext2, part type 0x83
> > grub> kernel /vmlinuz root=/dev/sda6
> >       [Linux-bzImage, setup=0x120, size 0x1463b31]
<snip>
> > ...VFS: Cannot open root device "sda6" or unknown
> > block (0,0)
> > Please append correct "root" boot option
> > Kernel Panic-not syncing: VFS: Unable to mount root fs
> > on unknown block (0,0)

In your /boot dir there should be a symlink called /boot which is linked 
to /boot! So when you have a seperate partition for your /boot area, 
using /boot/vmlinuz will stay valid through the entire boot process. So then 
your second line can read...

	kernel /boot/vmlinuz root=/dev/sda? ...
	        ^^^

-- 
Larkinson's Law:
	All laws are basically false.
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 789 bytes --]

On Tue, 29 Nov 2005 07:45:53 +0100, Heinz Sporn wrote:

> > grub> root (hd0,1)
> >       Fs is ext2, part type 0x83
> > grub> kernel /vmlinuz root=/dev/sda6
> >       [Linux-bzImage, setup=0x120, size 0x1463b31]
> 
> Shouldn't that read root=/dev/sda2 since your kernel obviously sits
> in /boot == /dev/sda2 ? The root paramter should define the place where
> your kernel / grub stage files reside IIRC and not where your root
> filesystem is located. Naming the parameter root is quite misleading
> though.

These are correct. The root (dh0,1) command is for sda2. The root
argument passed to the kernel is the root partition for Linux, nothing
to do with the location of the bootloader files. 


-- 
Neil Bothwick

Top Oxymorons Number 38: Government organization

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] grub on a SATA drive

[Chris Boot]

maxim wexler wrote:
> Thanks for your suggestions. Here's where things
> stand:
> 
> I did a fresh 2005.1 stage3 install onto the SATA
> drive without a hitch. I removed the ide drive, so
> there's only one hd.
> 
> In dmesg the drive comes up as /dev/sda
>    sda1(Macro$haft) sda2(/boot) < sda5(swap) sda6(/)
> sda7(home)>
> 
> When I boot w/ the grub floppy I do:
> 
> grub> root (hd0,1)
>       Fs is ext2, part type 0x83
> grub> kernel /vmlinuz root=/dev/sda6
>       [Linux-bzImage, setup=0x120, size 0x1463b31]
> 
> ...so far, so good...
> 
> grub> boot
> 
> and get:
> 
> ...VFS: Cannot open root device "sda6" or unknown
> block (0,0)
> Please append correct "root" boot option
> Kernel Panic-not syncing: VFS: Unable to mount root fs
> on unknown block (0,0)

So grub loads abd boots the Linux kernel, but the kernel can't mount the 
root FS on /dev/sda6. So /dev/sda6 doesn't exist for some reason, which 
could be one of:
1) There is no /dev/sda6 partition
2) You haven't compiled in support for your SATA controller in the kernel

There are two ways of doing SATA on Linux, one is through the IDE layer, 
which is deprecated and I strongly recommend against, the other is using 
libata through the SCSI layer.

> So I'm at a loss. The grub commands went alright.
> Wouldn't I get an error if one of the commands was
> wrong? Don't know what's meant by "unknown block
> (0,0)". Is it saying it's trying to mount / on
> /dev/sda1? Doesn't make sense.

That means it has no idea what sda6 is, that there is no such device.

HTH,
Chris

-- 
Chris Boot
bootc@bootc.net
http://www.bootc.net/
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[maxim wexler]

> 
> So grub loads abd boots the Linux kernel, but the
> kernel can't mount the 
> root FS on /dev/sda6. So /dev/sda6 doesn't exist for
> some reason, which 
> could be one of:
> 1) There is no /dev/sda6 partition

Huh? I just installed gentoo there.

> 2) You haven't compiled in support for your SATA
> controller in the kernel

Yes, I wondered about that. Previously in the config
options there were NV_SATA (this is an nVidia board)
and another for Sil3114(my SATA controller), forget
the exact option. That was for my earlier install when
I was still operating from the IDE HD and using that
to configure the SATA HD. This, present, install is
using the latest gentoo.org offering. These options
are nowhere to be found in make menuconfig, just a
generic-looking SATA_CONFIG(something like that). In
fact, when I boot from the install disk and do a lsmod
all the appropriate modules have been loaded(except
for the audio, which is easy to fix later), even
forcedeth, another option that this mobo requires
which was in the earlier config options but is now
missing. The Panic _does_ occur at about the spot
where the boot console is supposed to be finding the
drive. Why would they put drivers in the iso but not
the sources on the same CD? Weird.

> 
> There are two ways of doing SATA on Linux, one is
> through the IDE layer, 
> which is deprecated and I strongly recommend
> against, the other is using 
> libata through the SCSI layer.
> 
> > So I'm at a loss. The grub commands went alright.
> > Wouldn't I get an error if one of the commands was
> > wrong? Don't know what's meant by "unknown block
> > (0,0)". Is it saying it's trying to mount / on
> > /dev/sda1? Doesn't make sense.
> 
> That means it has no idea what sda6 is, that there
> is no such device.
> 
> HTH,
> Chris
> 
> -- 
> Chris Boot
> bootc@bootc.net
> http://www.bootc.net/
> -- 
> gentoo-user@gentoo.org mailing list
> 
> 



		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free. 
http://music.yahoo.com/unlimited/
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]

On Mon, 28 Nov 2005 22:34:45 -0800 (PST), maxim wexler wrote:

> In dmesg the drive comes up as /dev/sda
>    sda1(Macro$haft) sda2(/boot) < sda5(swap) sda6(/)
> sda7(home)>
> 
> When I boot w/ the grub floppy I do:
> 
> grub> root (hd0,1)
>       Fs is ext2, part type 0x83
> grub> kernel /vmlinuz root=/dev/sda6
>       [Linux-bzImage, setup=0x120, size 0x1463b31]
> 
> ...so far, so good...

Yes, GRUB is installed correctly and finding the kernel.

> grub> boot
> 
> and get:
> 
> ...VFS: Cannot open root device "sda6" or unknown
> block (0,0)
> Please append correct "root" boot option
> Kernel Panic-not syncing: VFS: Unable to mount root fs
> on unknown block (0,0)

This means the kernel cannot mount your root partition (/dev/sda6 IS the
correct setting for root). Either your root partitions's filesystem is
not compiled into your kernel or you have not added support for your SATA
controller. These must be compiled into the kernel, not as modules. You
need

CONFIG_SCSI_SATA=y
CONFIG_SCSI_SATA_YOURCONTROLLER=y


-- 
Neil Bothwick

DATA COMPRESSION: What You Get When You Squish An Android

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] grub on a SATA drive

[maxim wexler]

> 
> This means the kernel cannot mount your root
> partition (/dev/sda6 IS the
> correct setting for root). Either your root
> partitions's filesystem is
> not compiled into your kernel or you have not added
> support for your SATA
> controller. These must be compiled into the kernel,

I realize that.

> not as modules. You
> need
> 
> CONFIG_SCSI_SATA=y

Yes, I got that one.

> CONFIG_SCSI_SATA_YOURCONTROLLER=y

NV_SATA worked(although SIL_SATA didn't, despite
having a Sil3114 controller) before, but is not among
the options(nor, for that matter, SIL_SATA) in
menuconfig for this kernel. Is there a patch, I
require? 

More paradox: the kernel among the sources on the CD
is 2.6.12-r6, exactly the same as the one I had before
on the Maxtor IDE, upgraded using emerge about a month
and a half ago!

> 
> 
> -- 
> Neil Bothwick
> 
> DATA COMPRESSION: What You Get When You Squish An
> Android
> 



		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[Richard Fish]

On 11/29/05, maxim wexler <blissfix@yahoo.com> wrote:
> > CONFIG_SCSI_SATA=y
>
> Yes, I got that one.
>
> > CONFIG_SCSI_SATA_YOURCONTROLLER=y
>
> NV_SATA worked(although SIL_SATA didn't, despite
> having a Sil3114 controller) before, but is not among
> the options(nor, for that matter, SIL_SATA) in
> menuconfig for this kernel. Is there a patch, I
> require?

Also, don't forget SCSI disk support, CONFIG_BLK_DEV_SD=y

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[maxim wexler]

> 
> Also, don't forget SCSI disk support,
> CONFIG_BLK_DEV_SD=y

Well, I did forget it but it still doesn't work. Same
panic, same place.

> 
> -Richard
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 
> 



		
__________________________________ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free. 
http://music.yahoo.com/unlimited/
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[Richard Fish]

On 11/30/05, maxim wexler <blissfix@yahoo.com> wrote:
> >
> > Also, don't forget SCSI disk support,
> > CONFIG_BLK_DEV_SD=y
>
> Well, I did forget it but it still doesn't work. Same
> panic, same place.
>

Please post the output of:

grep "=[ym]" /usr/src/linux/.config

-Richard

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] grub on a SATA drive

[maxim wexler]

--- Richard Fish <bigfish@asmallpond.org> wrote:

> On 11/30/05, maxim wexler <blissfix@yahoo.com>
> wrote:
> > >
> > > Also, don't forget SCSI disk support,
> > > CONFIG_BLK_DEV_SD=y
> >
> > Well, I did forget it but it still doesn't work.
> Same
> > panic, same place.
> >
> 
> Please post the output of:
> 
> grep "=[ym]" /usr/src/linux/.config

CONFIG_X86=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
CONFIG_SYSVIPC=y
CONFIG_SYSCTL=y
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_KALLSYMS=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_KMOD=y
CONFIG_X86_PC=y
CONFIG_M586=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_PPRO_FENCE=y
CONFIG_X86_F00F_BUG=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_ALIGNMENT_16=y
CONFIG_PREEMPT=y
CONFIG_X86_MCE=y
CONFIG_X86_CPUID=m
CONFIG_DCDBAS=m
CONFIG_NOHIGHMEM=y
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_MTRR=y
CONFIG_SECCOMP=y
CONFIG_HZ_1000=y
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_ISA_DMA_API=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m
CONFIG_NET=y
CONFIG_PACKET=m
CONFIG_UNIX=m
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_FIB_HASH=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_TCP_CONG_BIC=y
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=m
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_SERIAL=m
CONFIG_PARPORT_1284=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=m
CONFIG_CDROM_PKTCDVD=m
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=m
CONFIG_IOSCHED_DEADLINE=m
CONFIG_IOSCHED_CFQ=m
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=m
CONFIG_BLK_DEV_IDEDISK=m
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=m
CONFIG_IDE_GENERIC=m
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_GENERIC=m
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_AMD74XX=m
CONFIG_BLK_DEV_SIIMAGE=m
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_SATA=y
CONFIG_SCSI_QLA2XXX=y 
CONFIG_IEEE1394=m
CONFIG_IEEE1394_OHCI1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_NET_PCI=y
CONFIG_S2IO=m
CONFIG_PLIP=m
CONFIG_PPP=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_SLIP=m
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_LIBPS2=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_CORE=y
CONFIG_UNIX98_PTYS=y
CONFIG_PRINTER=m
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_AGP=m
CONFIG_AGP_NVIDIA=m
CONFIG_DRM=m
CONFIG_DRM_RADEON=m
CONFIG_I2C=m
CONFIG_I2C_ALGOBIT=m
CONFIG_HWMON=y
CONFIG_FB=m
CONFIG_FB_CFB_FILLRECT=m
CONFIG_FB_CFB_COPYAREA=m
CONFIG_FB_CFB_IMAGEBLIT=m
CONFIG_FB_SOFT_CURSOR=m
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_DEBUG=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_SOUND=m
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_RTCTIMER=m
CONFIG_SND_GENERIC_DRIVER=y
CONFIG_SND_MPU401_UART=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MPU401=m
CONFIG_SND_AC97_CODEC=m
CONFIG_SND_AC97_BUS=m
CONFIG_SND_INTEL8X0=m
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=m
CONFIG_USB_DEBUG=y
CONFIG_USB_DEVICEFS=y
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y
CONFIG_EXT2_FS=y
CONFIG_REISERFS_FS=y
CONFIG_REISERFS_CHECK=y
CONFIG_REISERFS_PROC_INFO=y
CONFIG_DNOTIFY=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_NTFS_FS=y
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_NFS_FS=m
CONFIG_NFSD=m
CONFIG_LOCKD=m
CONFIG_EXPORTFS=m
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=m
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_1=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_EARLY_PRINTK=y
CONFIG_CRC_CCITT=m
CONFIG_CRC32=y
CONFIG_LIBCRC32C=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

> 
> -Richard
> 
> -- 
> gentoo-user@gentoo.org mailing list
> 
> 



		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs
-- 
gentoo-user@gentoo.org mailing list