When trying to install 1.4_rc2, the install script seg faults on the nvnet network driver. The system then enters a state where lsmod shows the nvnet module forever (initializing). Therefore it cannot be unloaded. This blocks all further network configuration and stops any attempt at installing gentoo. My hardware: motherboard FIC VA-503+ cpu k6-2 500 ram 256M eth0 dec 21104 (tulip) eth1 d-link (via-rhine) sound none hd two maxtor ide Reproducible: Always Steps to Reproduce: 1.Boot 1.4_rc2 live cd 2. 3. Actual Results: system stuck in uncorrectable state Expected Results: The install script should not try to load nvnet driver, or give a way to filter the problem drivers from the autoprobe script.
you can use the nonet option to not autoprobe any nic modules.
i have the same problem motherboard: asus P5a (ali chipset) cpu: amd k6-2/500mhz even with no nic in the pc installation with nonet option worked fine for me
hmmm... we are both running k6-2 500Mhz.. i wonder if that has anything to do with it? I think i have an old 350 around here somewhere I might try to throw in to see if that works..
I experienced this problem as well with AMD K6-2 400 MHz. It comes with RC2 and RC3, but not with RC1. My motherboard reports to be a K6BV3+ (don't remember the manufacturer).
Scanning for nvnet... /sbin/runscript.sh: line 39: 2878 Segmentation fault insmod -f ${x} >/dev/null 2>&1 After this happens I boot to the normal Welcome to Gentoo screen. I'm able to modprobe tulip for my NIC, then dhcpcd eth0 and everything hums along fine. I, too, am using an AMD K6-2 350MHz on a P5BV3+ mobo
try latest livecds , more then likely was gcc opts used on -rc2
closing due to no feedback
