Re: [gentoo-user] 2.6.19-r5 kernel disaster
On Thursday 12 April 2007, maxim wexler wrote: Hi group, After running make menuconfig 4x on a PIII, re-emerging --emptytree world and either booting to a highly unstable system or a maintenance login I feel it's time to call on the authorities. It looks like the kernel can't find the / device. The whole IDE/ATA/SATA/PATA/SCSI layout hingy changed with 2.6.19, so first thing to check is that everything you need is actually enabled in the kernel (yeah, there's some gotchas in there). Please post your .config alan -- Optimists say the glass is half full, Pessimists say the glass is half empty, Developers say wtf is the glass twice as big as it needs to be? Alan McKinnon alan at linuxholdings dot co dot za +27 82, double three seven, one nine three five -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] 2.6.19-r5 kernel disaster
On Thursday 12 April 2007 03:02, maxim wexler wrote: Hi group, snip When I chroot from the livecd(2005.1) everything seems to work; the modules all load, the software works etc. So, I'm at a complete loss. FWIW, when I do boot the maintenance console and run udevstart the system crashes forcing a reset. -mw I had a similar problem once, It might not be your case but this one time I forgot to mount '/boot' before installing the new kernel via 'make install', so the system presented similar errors, since the modules and old kernel couldn't work together. It might be that... ( don't laugh ) -- Guillermo A. Amaral, CSE # Free Open Source Advocate nick: guillermoamaral @ blog: http://blog.guillermoamaral.com/ @ site: http://www.guillermoamaral.com/ $ irc: [EMAIL PROTECTED] % gpg: http://downloads.guillermoamaral.com/public.asc pgpsXhLONuTSV.pgp Description: PGP signature
Re: [gentoo-user] 2.6.19-r5 kernel disaster
On 4/12/07, Alan McKinnon [EMAIL PROTECTED] wrote: On Thursday 12 April 2007, maxim wexler wrote: Hi group, After running make menuconfig 4x on a PIII, re-emerging --emptytree world and either booting to a highly unstable system or a maintenance login I feel it's time to call on the authorities. It looks like the kernel can't find the / device. The whole IDE/ATA/SATA/PATA/SCSI layout hingy changed with 2.6.19, so first thing to check is that everything you need is actually enabled in the kernel (yeah, there's some gotchas in there). Please post your .config If init starts then the kernel found his root partition (otherwise it panics with a VFS layer message).
Re: [gentoo-user] 2.6.19-r5 kernel disaster
I think you did not enable the Unix Domain Sockets in your make menuconfig: Networking - Networking Support - Networking Options - Unix Domain Sockets This is the same thing Devon was talking about. On 11/04/07, maxim wexler [EMAIL PROTECTED] wrote: Hi group, After running make menuconfig 4x on a PIII, re-emerging --emptytree world and either booting to a highly unstable system or a maintenance login I feel it's time to call on the authorities. Don't even have gpm so I can't scroll the choice bits of the boot messages. It all starts to fall apart on the following line in the boot console * Starting udev... then udevd[367]: init_udevd socket: error getting socket: Address family not supported by protocol error initializing udevd socket udevd[367]: main: error initializing udevd socket [!!] ... * Checking root filesystem... Failed to open the device '/dev/hda3': No such file or directory * Filesystem couldn't be fe fixed :( [!!] Give root password for maintenance /dev/hda3 is reiserfs and reiserfs support is configured into the kernel as is ATA and IDE support. /etc/fstab is the same one(modified for different partitioning systems, of course) I've been using for years. /etc/fstab is not the problem. Yes, I did this: File systems --- Pseudo filesystems --- [*] /proc file system support [*] Virtual memory file system support (former shm fs) And have baselayout-1.12.9. When I chroot from the livecd(2005.1) everything seems to work; the modules all load, the software works etc. So, I'm at a complete loss. FWIW, when I do boot the maintenance console and run udevstart the system crashes forcing a reset. -mw Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 -- [EMAIL PROTECTED] mailing list -- Fabio A. Correa D. Physics Dept, Universidad Nacional, Bogota, Colombia [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] My webpage and OpenPGP key at http://facorread.150m.com My alexandria.cc address is not available anymore. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] 2.6.19-r5 kernel disaster
Hi! On Wed, 11 Apr 2007 20:02:54 -0700 (PDT) maxim wexler [EMAIL PROTECTED] wrote: After running make menuconfig 4x on a PIII, re-emerging --emptytree world and either booting to a highly unstable system or a maintenance login I feel it's time to call on the authorities. Don't even have gpm so I can't scroll the choice bits of the boot messages. You don't need gpm for that. SHIFT-PgUp and SHIFT-PgDn can do that too. ;-) And the following excerpt from /etc/conf.d/rc might help in debugging boot problems: === # RC_BOOTLOG will generate a log of the boot messages shown on the # console. Useful for headless machines or debugging. You need to # emerge the app-admin/showconsole package for this to work. Note that # this probably won't work correctly with boot splash. RC_BOOTLOG=no === Cheers, Renat -- Probleme kann man niemals mit derselben Denkweise loesen, durch die sie entstanden sind. (Einstein) signature.asc Description: PGP signature
[gentoo-user] 2.6.19-r5 kernel disaster
Hi group, After running make menuconfig 4x on a PIII, re-emerging --emptytree world and either booting to a highly unstable system or a maintenance login I feel it's time to call on the authorities. Don't even have gpm so I can't scroll the choice bits of the boot messages. It all starts to fall apart on the following line in the boot console * Starting udev... then udevd[367]: init_udevd socket: error getting socket: Address family not supported by protocol error initializing udevd socket udevd[367]: main: error initializing udevd socket [!!] ... * Checking root filesystem... Failed to open the device '/dev/hda3': No such file or directory * Filesystem couldn't be fe fixed :( [!!] Give root password for maintenance /dev/hda3 is reiserfs and reiserfs support is configured into the kernel as is ATA and IDE support. /etc/fstab is the same one(modified for different partitioning systems, of course) I've been using for years. /etc/fstab is not the problem. Yes, I did this: File systems --- Pseudo filesystems --- [*] /proc file system support [*] Virtual memory file system support (former shm fs) And have baselayout-1.12.9. When I chroot from the livecd(2005.1) everything seems to work; the modules all load, the software works etc. So, I'm at a complete loss. FWIW, when I do boot the maintenance console and run udevstart the system crashes forcing a reset. -mw Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] 2.6.19-r5 kernel disaster
Check that you have CONFIG_UNIX=y in your .config. The udev daemon (udevd) listens on a unix domain socket. When udevd doesn't run your hda3 device is not created in /dev which explains the later messages. I'm not sure why udevstart would crash your system though. Do you get a kernel oops or does it just reboot? dcm On 4/11/07, maxim wexler [EMAIL PROTECTED] wrote: Hi group, After running make menuconfig 4x on a PIII, re-emerging --emptytree world and either booting to a highly unstable system or a maintenance login I feel it's time to call on the authorities. Don't even have gpm so I can't scroll the choice bits of the boot messages. It all starts to fall apart on the following line in the boot console * Starting udev... then udevd[367]: init_udevd socket: error getting socket: Address family not supported by protocol error initializing udevd socket udevd[367]: main: error initializing udevd socket [!!] ... * Checking root filesystem... Failed to open the device '/dev/hda3': No such file or directory * Filesystem couldn't be fe fixed :( [!!] Give root password for maintenance /dev/hda3 is reiserfs and reiserfs support is configured into the kernel as is ATA and IDE support. /etc/fstab is the same one(modified for different partitioning systems, of course) I've been using for years. /etc/fstab is not the problem. Yes, I did this: File systems --- Pseudo filesystems --- [*] /proc file system support [*] Virtual memory file system support (former shm fs) And have baselayout-1.12.9. When I chroot from the livecd(2005.1) everything seems to work; the modules all load, the software works etc. So, I'm at a complete loss. FWIW, when I do boot the maintenance console and run udevstart the system crashes forcing a reset. -mw Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. http://farechase.yahoo.com/promo-generic-14795097 -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
