I installed Gentoo Linux 1.1a from the 16MB tarball over the past couple of days. I followed the instructions *to the letter*. Everything with the install went well, but when I rebooted, I got the following: ... TCP: Hash Tables Configured (established 32768 bind 32768) ip_conntrack (4,094 buckets, 32752 max) ip_tables: (C) 2000 - 2002 Netfilter core team NET4: Unix Domain Sockets 1.0/SMP for Linux NET4.0. FAT: bogus logical sector size 0 UMSDOS: msdos_read_super failed; mount aborted. FAT: bogus logical sector size 0 FAT: bogus logical sector size 0 invalid operand: 0000 CPU: 0 EIP: 0010:[<c0133c5c>] Not tainted EFLAGS: 00010286 eax: fffffe00 ebx: 00000003 ecx: 00000200 edx: 00000000 esi: 00000000 edi: 00000303 ebp: 00000000 esp: c187de40 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 1, stackpage=c187d000) Stack: 00000303 00000000 00000000 dfeb9120 000046c0 c031320eb 00000303 00000000 00000000 c187ded8 dfe7c400 dfe7c44c c01322c8 000000303 00000000 00000000 00000000 c01a271c 00000303 00000000 00000000 000000000 c01ab3ed dfe7c400 Call Trace: [<c01320eb>] [<c01322c8>] [<c01a271c>] [<c01ab3ed>] [<c013470b>] [<c0134a5e>] [<c010502d>] [<c0105040>] [<c0105478>] Code: 0f 0b b9 ff ff ff ff 89 fa b6 00 8b 44 24 20 41 d3 e0 3d ff <0>kernel panic: attempted to kill init! Seeing the fat and umsdos calls above, I reasoned that it had to do with thefact that I was compiling suport for file systems directly into the kernel. I made all my file system support into modules, and recompiled the kernel. It booted fine after that. To test my suspeicions, I recompiled the kernel again, this time with file system supports supported directly by the kernel, and got the *exact* same errors. Recompiling the kernel with file support as modules lets me boot into gentoo with no problem. The file systesm I am compiling (as modules, so I can use my system ;) ) are as follows: Amiga FFS file system support Ext3 Journalling File system support - JBD (ext3) debugging support DOS FAT fs support - MSDOS fs support -- UMSDOS: Unix-like file system on top or a regular MSDOS fs ISO 9660 CDROM file system support - Microsoft Joliet CDROM extensions - Transparent Decompression extension Minix fs support NTS File system support (read only) OS/2 HPFS File system support /proc file system support /dev file system support - Automatically mount at boot /dev/pts file system for Unix98 PTYs QNX4 File system support (read only) ROM file system support Second extended fs support System V/Xenix/V7/Coherent file system support UDF File system support (read only) UFS file system support (read only) SGI XFS File system support - Enable XFS Realtime support - Enable XFS Quota - Enable XFS DMAPI Note that I am using the sys-kernel/xfs-sources for my kernel, as I have /dev/hda3 (/ROOT) partitioned as an KFS file system. It should be noted, too (I don't know if it makes a difference) that I have /dev/hda1 (/BOOT) formatted as an Ext3 partition. As I said, this error is reproducable on demand.
Duh, I forgot the hardware: Intel PIII 733 512MB RAM 60GB HDD Sony 12X DVD Sony 16X CDRW 3.5" Floppy 3Com 3c905 NIC I can get more specific if needs be... but I'd have to open the machine. ;)
If you've read the installation docs on www.gentoo.org you'll see that you should NOT compile /dev and /dev/pts support. You should only compile /dev filesystem support. That may not be the source of your problems, but it is a source of one problem anyway. And anyway, filesystem stuff should be compiled as modules, except for the couple/few that you use for /boot and /. Did you make this bug report to enhance Gentoo's installation docs or what?
Well, I didn't make the bug to enhance the install docs, but now it seems like I should have. I reread them, and it says "You <i>don't</i> need to enable /dev/pts." It doesn't say that you *shouldn't*. However, it doesn't really matter at this point. After recompiling my kernel with no file systems built in except those I was actively using, I am getting that error every time. (Note that they are not even being compiled as modules, I am saying "no" to any file systems that I am not actively using.) I am going to reinstall from scratch (fun, since I'm on dial-up ;) ). And I (personally, imho) don't think that I should have to compile file systems that I regularly use in as modules. Having to load modules every time I want to read FAT floppies is a PITA, and I've never had to worry about this before. It's much easier to add them to the kernel and then just mount them when I need to (which is often, unfortunately). I will let you know the results of the reinstall.
try the 1.2 or 1.3 stage1s.
Documentation error, and will be fixed or has been fixed, plus the new kernel has a better default config.
