Please comment only here on problems with my stages. DON'T FILE BUGS. NOTE: Don't use bootstrap.sh to test stage1 but uses bootstrap-new.sh instead.
Correction: Use bootstrap.sh from the portage snapshot ! Stages are on my devspace http://dev.gentoo.org/~kugelfang/stages/
the mountpoint /lib/firmware fails to mount on every boot. i am getting dma issues and mad system instability.
What kind of system do you have ? Please post the error messages about dma issues and describe the system instability. The /lib/firmware BUG is being worked on...
1- athlon64 2.0 ghz, on an nvidia nforce chipset, ga-k8n pro motherboard. 512 ram. using eide hd, onboard i8x0 audio and ethernet, sata disabled. 2- init script error : Mounting local filesystems... mount: mount point /lib/firmware does not exist * Some local filesystem failed to mount [ !! ] 3- dmesg is far from clean: Bootdata ok (command line is initrd=gentoo.igz root=/dev/ram0 init=/linuxrc looptype=squashfs loop=/livecd.squashfs noudev de vfs cdroot vga=791 dokeymap splash=silent,theme:livecd-2004.3 BOOT_IMAGE=gentoo ) Linux version 2.6.9-gentoo-r14 (root@phi) (gcc version 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7)) #1 SMP Sat Feb 19 20:39:53 UTC 2005 [....] sbp2: $Rev: 1219 $ Ben Collins <bcollins@debian.org> ReiserFS: hdc: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on hdc VFS: Can't find ext3 filesystem on dev hdc. VFS: Can't find ext2 filesystem on dev hdc. SQUASHFS error: Can't find a SQUASHFS superblock on hdc FAT: bogus number of reserved sectors VFS: Can't find a valid FAT filesystem on dev hdc. ISO 9660 Extensions: Microsoft Joliet Level 3 ISO 9660 Extensions: RRIP_1991A Uhhuh. NMI received for unknown reason 3d. Dazed and confused, but trying to continue Do you have a strange power saving mode enabled? Real Time Clock Driver v1.12 r8169 Gigabit Ethernet driver 1.2 loaded ACPI: PCI interrupt 0000:01:0b.0[A] -> GSI 19 (level, low) -> IRQ 19 eth0: Identified chip type is 'RTL8169s/8110s'. eth0: RTL8169 at 0xffffff000003e000, 00:0d:61:18:1d:b0, IRQ 19 r8169: eth0: link up fbsplash: console 11 using theme 'livecd-2004.3' fbsplash: switched splash state to 'on' on console 11
pre-init error: >> Filling tmpfs... >> Filling filesystem... /linuxrc:450 /tmp/.initrd/bin/[: not found
sorry, actually dmesg looks fine. its just the pre init: >> Filling filesystem.../linuxrc:450 /tmp/.initrd/bin/[: not found error, and the mount point /lib/firmware problem. maybe they're related? sidenote, the other system that booted off an old livecd, is processing stage1 flawlessy for an hour. gcc is almost complete... it's early, however the bootstrap is compiling very smoothly.
(non livecd issue) On a fresh stage1 installation, glibc won't compile because nptl is enabled with the current kernel. quote: [[ (5/6) Emerging libc/baselayout ]] Calculating dependencies ...done! >>> emerge (1 of 4) sys-libs/glibc-2.3.4.20050125 to / >>> md5 src_uri ;-) glibc-2.3.4.tar.bz2 >>> md5 src_uri ;-) glibc-linuxthreads-2.3.4.tar.bz2 >>> md5 src_uri ;-) glibc-2.3.4-patches-1.2.tar.bz2 >>> md5 src_uri ;-) glibc-manpages-2.3.4-r1.tar.bz2 >>> md5 src_uri ;-) glibc-infopages-2.3.4-r1.tar.bz2 * Warning! Gentoo's GLIBC with NPTL enabled now behaves like the * glibc from almost every other distribution out there. This means * that glibc is compiled -twice-, once with linuxthreads and once * with nptl. The NPTL version is installed to lib/tls and is still * used by default. If you do not need nor want the linuxthreads * fallback, you can disable this behavior by adding nptlonly to * USE to save yourself some compile time. >>> Unpacking source... * Checking gcc for __thread support ... yes * Checking kernel version (>=2.6.6) ... no * You need a kernel of at least version 2.6.6 * for NPTL support! !!! ERROR: sys-libs/glibc-2.3.4.20050125 failed. !!! Function check_nptl_support, Line 646, Exitcode 0 !!! Kernel version too low! This is a reproducable error for fresh systems
the hardware instability that i mentioned (lockups) appear to have been caused by apic. running this beta livecd with the noapic tag at boot cleared the instability. Mobo is a GA-K8N pro http://tw.giga-byte.com/MotherBoard/Products/Products_GA-K8N%20Pro.htm which uses the nForce3 150 chipset and realtek 8169 lan and needs noapic to function properly. (not a bug)
i think we can close this, right? :)
