Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 13089 - LiveCD bootup crash at eth16i with nForce2 board
Summary: LiveCD bootup crash at eth16i with nForce2 board
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Release Media
Classification: Unclassified
Component: Everything (show other bugs)
Hardware: All All
: High critical
Assignee: Bob Johnson (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-02 08:21 UTC by Harald Glatt
Modified: 2003-04-04 01:28 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Glatt 2003-01-02 08:21:24 UTC
I've got a mainboard (ASUS A7N8X Deluxe) with an Nvidia Nforce2 Chipset.
It has an integrated nvidia networking adapter and an integrated 3com networking
adapter.
Also i've got a 8139too networking adapter installed in one of the pci slots.

When I bootup the rc2 LiveCD it hangs in INIT at following line:
"Auto-scrambling root password for security"
"Auto-detecting network modules..."
"Scanning for eth16i..."

I also tried noapic acpi=off and all other stuff but it always hangs at eth16i.
Only thing I can do is nonet. Then it boots up normally. I need to modprobe
nvnet manually then and dhcpcd eth0. After that I can start to use the livecd.
Comment 1 Bob Johnson (RETIRED) gentoo-dev 2003-01-12 18:29:16 UTC
Nvidia drivers non-GPL?
Comment 2 Harald Glatt 2003-01-13 05:47:03 UTC
Yeah, the NVIDIA net drivers are closed source and therefore non-GPL... 
Well surly you could fix that bug. It would be ugly but it would probably work.
You could load nvnet prior to loading eth16i. After loading nvnet your script
could check via return code or via lsmod if the driver has been successfully
loaded. If it has been successfully loaded the mainboard is a NForce or NForce2
Chipset mainboard and the eth16i will crash. So you continue loading other
networking drivers except the eth16i, you just exclude it and write something
like "Won't probe eth16i, please insmod manually". Of course if the nvnet driver
didn't load you know that isn't a NFORCE mainboard and you can probe the eth16i.

the script should look somethink like this:

0. net detection script is started
1. load nvnet
2. check if it has been loaded
2a. continue loading all drivers except eth16i (when 2 was true)
2b. continue loading all drivers (when 2 was false)

How about that?
Comment 3 Brandon Low (RETIRED) gentoo-dev 2003-01-13 17:02:45 UTC
nforce2 boards aren't supported by the linux kernel yet.  give it time, friends,
they are working on it.
Comment 4 Daniel Robbins (RETIRED) gentoo-dev 2003-01-14 20:59:04 UTC
This bug shouldn't have been closed.
Comment 5 Bob Johnson (RETIRED) gentoo-dev 2003-01-18 01:37:45 UTC
Drobbins, not sure what i can do about this as far as the kernel goes.  
nvnet isnt gpl, so i cant touch it in the kernel. 
 
The nonet usage does not seem out of line to me when your talking about  
unsupported (or very little support) hardware. 
 
If you know of a way i can fix this, let me know. 
 
Harald, 
    gs-sources has the recent nforce2 ide fixes, and the asus 3c59x fixes. 
Comment 6 Harald Glatt 2003-01-19 08:24:03 UTC
What about my fix suggestion?! Or won't that crash happen with the new
gs-sources anymore?!
Comment 7 John Davis (zhen) (RETIRED) gentoo-dev 2003-04-04 01:23:11 UTC
db fix
Comment 8 John Davis (zhen) (RETIRED) gentoo-dev 2003-04-04 01:28:04 UTC
db fix