In Gentoo 2004.1 Minimal Live CD, the nForce2 audio and my ATI Radeon 9700 are detected and configured properly, BUT NOT THE nForce2 ETHERNET. In Gentoo 2004.0 Minimal Live CD, the nForce2 audio and my ATI Radeon 9700 are detected and NOT CONFIGURED PROPERLY (Unknown...), but the nForce2 Ethernet is OK via DHCP. I like the having the nForce2 audio and ATI detection corrected, but I can't install anything because I need to download it off the net with my non-functional nForce2 Ethernet. ;oP Can you guys put out a 2004.11 that blends both functional detections? Reproducible: Always Steps to Reproduce: 1.Insert Minimal x86 Gentoo Live CD into CD-ROM drive, 2.Reboot PC, 3.Choose "gentoo dofirewire" kernel, 4.Try to "ping -c 3 www.yahoo.com", 5."Unkown host..." 6.Run ifconfig, 7."Link encap: UNSPEC...", 8.Run net-setup, DHCP, 9.Run ifconfig, 10."Link encap: UNSPEC...", 11.Run net-setup, manual, 12.Run ifconfig, 13."Link encap: UNSPEC...". Actual Results: For ping -c 3 www.yahoo.com: "Unkown host..." For ifconfig: "Link encap: UNSPEC..." Expected Results: For ping -c 3 www.yahoo.com: "...Packet sent x, packet received x, packet lost 0..." For ifconfig: "Link encap: Ethernet..." nForce2 Ethernet adaptor was detected and configured properly in Gentoo Minimal Install 2004.0 nForce2 Ethernet adaptor is no longer detected and configured properly in Gentoo Minimal Install 2004.1
*** Bug 49245 has been marked as a duplicate of this bug. ***
Since the more generic bug 49245 was marked as a duplicate to this bug, I'll add my problem here: I have an 8139too based nic that isn't being detected by 2004.1 (x86-minimal) that is detected by 2004.0 (x86-universal). A simple: # modprobe 8139too # dhcpcd eth0 fixes it. I should note that I do not have firewire (ieee1394) on this box as some have reported that to be the problem. You can also find a discussion in the forums at http://forums.gentoo.org/viewtopic.php?p=1086796
Rewritten summary since it's a global network autoconfiguration issue, not an nforce specific one. I played recently with catalyst and observed the same results. When I build a LiveCD with a 2.4 kernel, hwconfig detects the card, the module is autoloaded and autoconfig sees it. When I build the exact same LiveCD with a 2.6 kernel, hwconfig still works (/etc/sysconfig/knoppix lists the network adapters), but the module is not autoloaded and autoconfig (which does not read the knoppix hwconfig files) does not see it. I think it's some kind of hwconfig/autoconfig/2.6 kernel issue. -K
ieee1394 hardware detected when it is not present hiding actual nic. # modprobe tulip # dhcpcd eth0 As in comment#2 above gets my network going.
Experienced the same problem on my laptop, an HP nc8000. The firewire was detected as eth0, not the onboard Broadcom NIC. This explains why manual configuration of eth0 failed to work. I manually brought up eth1, the Broadcom nic after modprobing tg3 and DHCP works fine, I'm online. May be confusing for some first time users though and I'm not totally convinced this isn't a hardware issue. (Sorry, missed the dup comment on 49245).
broadcom tigon3 was detected in 2004.0 but not 2004.1
*** Bug 49447 has been marked as a duplicate of this bug. ***
Here's a "me too" on this bug using a Supermicro P4DP6 mobo and the onboard Intel Pro 100 nic(s). Modprobing eepro100 and running net-setup gets everything going fine...
I have the same problem - my eth0/1 are detected under 2004.0, but not in 2004.1 on a P3 497MHz with intel NICs. Using x86 universal live CD's in both cases. Cheers
I have the precise problem that the original bug submitter describes. My Radeon 9700 and audio come up perfectly, but the nvnet module doesnt even exist! The only fix i've seen is to somehow get the nvnet modules off nvidia into your prechroot livecd, make it, and insmod it, then configure it. I'm yet to try this personally, due to the effort factor, and instead I'm going to stick to the 2004.0 minimal boot cd where nvnet loads properly. This seems like quite a large bug, made worse by the fact that the 2.4.25 kernel that ships with 2004.1 has no support for nvnet (unlike 8139) and thus those of us with nforce-net adapters are completely stuck.
*** Bug 49970 has been marked as a duplicate of this bug. ***
*** Bug 50046 has been marked as a duplicate of this bug. ***
*** Bug 48868 has been marked as a duplicate of this bug. ***
*** Bug 50220 has been marked as a duplicate of this bug. ***
I too had this problem when using the 2004.1 install CD, so I used the 2004.0 install CD to boot up, and downloaded and installed the 2004.1 stage3 tarball. Rebooted with the gentoo-2.6.5-r1 kernel with minimal options and networking worked fine. Rebuilt the kernel with a full set of options to support all hardware on my laptop (including the firewire port) and all of the sudden, the network won't work. Removed the eth1394 support from the kernel and rebooted, and it now works. Looks like this may be an issue with hotplug.
I've also got this problem, except with a Netgear FA310TX card. I modprobe tulip, do net-setup eth0, no go. Cable Modem (Toshiba PCX1100U) -> Router (Netgear RP114) -> PC (Netgear FA310TX, tulip) It's worked on every other liveCD but this one.
*** Bug 49677 has been marked as a duplicate of this bug. ***
My Broadcom Tigon3 also was detected in 2004.0, but was not in 2004.1!
Thanks all for the bug reports. We are aware of the problem and are looking into possible solutions. Would anyone willing to test experimental 2004.2 LiveCD's shoot me an email, so I can give you the address to where I will be placing my test CDs. We are working to iron out all of these bugs before release.
I have this same problem. My onboard Realtek 8139 is detected on the 2004 cd but the bootstrap.sh doesnt work on that installation cd and now when i try to use 2004.1 my onboard lan card isnt detected.
Yeah I had this problem too. I have a ne2000 pci compatible card in here. I was a little surprised about it happening but though , oh it's a beta cd right!. Then I found out that it is in fact not a beta!... I thought I could fix it by manually loading the module but that gave half a page of error and as a result not being able to load anything at all anymore. Something need fast fixing here! The lice cd is the "cradle" of a gentoo system.
to get eth0 working on 2004.1: nano /etc/rc.conf/net change iface_eth0="192.168. ????????????????????????" to iface_eth0="dhcp" save and exit livecd root # /etc/init.d/net.eth0 stop livecd root # /etc/init.d/net.eth0 start that's how i get it working.
correction to comment #22. nano /etc/conf.d/net instead of nano /etc/rc.conf/net sorry about the confusion.
I've tried the modprobe/dhcpd, modprobe/net-setup, and nano /etc/conf.d/net tricks to no avail. BTW, I'm booting with 2004.1. I went back to my Knoppix cd which detects both nics in my machine. An lsmod in that environment shows the following module dependencies. 8139too mii [8139too] crc32 [8139too] When booting 2004.1, lsmod only shows mii present. I tried to modprobe crc32 but modprobe couldn't find it. Jumping back to Knoppix, a perusal (actually a grep) of modules.dep shows that several different nics require crc32. Perhaps this is the reason why the problem is so widespread. I still haven't solved my issue with 2004.1. I suspect I'm going to have to edit the modules.dep file and make sure that crc32.o is somewhere that modprobe can find it. So far, just sticking crc32.o in the /lib/modules/'uname -r/kernel/ directory and running modprobe hasn't worked. I think that's becasue the dependency has to be listed in modules.dep too. I'm just not there yet.
The crc32 module was compiled statically into the kernel, and therefore won't work as a module, no matter what you do. As for your network card not working, that was an unfortunate problem with 2004.1 that plagued many people. The truth of the matter is that the tool which we use for building our LiveCD's had a bug in it which caused some major problems with modules. If you would be so kind as to help us QA our new test CDs, perhaps you can get this situation resolved and also get your machine up and running without resorting to using the LiveCD of another distribution. The location for the 2004.2-test CDs is http://dev.gentoo.org/~wolf31o2/releng and there is also a bug #51396 where you can submit any bugs that you may find with the -test CDs. I am going to go ahead and mark this one as RESOLVED-FIXED simply because I believe that we have already resolved this with our newer CD set, which will be released July 26th.
Can you please tell us how you did it, re: http://forums.gentoo.org/viewtopic.php?t=184165
Huh? I'm not sure I understand what you're asking. How I did what, exactly? If you mean the fixes to the LiveCD, then you'll find that I have been working with the genkernel team to get the problems that faced 2004.1 fixed. A simple fix for people using genkernel on their machines is to configure the interface that is found. If that is eth1, then configure that one instead of eth0 (which is eth1394). A fixed version of genkernel will be added to cvs once a few other problems are ironed out which I am currently working on getting resolved.
Oh. I was hoping for the solution sought in my link.
Judging from the content of <http://forums.gentoo.org/viewtopic.php?t=184165>, it looks like the installed userland is affected by the bug, not just the LiveCD. For those installing from the test CDs at <http://dev.gentoo.org/~wolf31o2/releng/>, do you recommend avoiding certain versions of the kernel, hotplug, or whatnot? For example, should one avoid downloading and unpacking the stage3 tarball of 2004.1 as part of the installation?
Hi all, I had more or less the same trouble to install the nic. They (eepro100 and 3c59x) were not recognized and I had to modprobe(I've tried and retried changing kerneloptions at boot). Nothing dramatic. Though, the installation became more problematic when I tried to modprobe the eepro driver. This made the system hang. I've tried it several times and the result was always the same. Finally I switched some cables and all worked just fine with the 3c59x. Laurent
If you're referring to any CD other than the CD on /experimental/x86/livecd on the Gentoo mirrors, there really is not a point. There is nothing we can do to fix a release that has already been done. We can, however, make the next one better. In the /experimental folder, you will find my -test4 CD. Please use that one instead.
"In the /experimental folder, you will find my -test4 CD. Please use that one instead." Could you also put a README in there, to point out what versions of hotplug or kernel or tarballs of stages 1, 2, or 3 to avoid, if any?
You don't need to avoid anything with the CD. It should be fully compatable with all the current kernels and all versions of hotplug. You can also use any stages that you wish, since my CD does not have any on it.
*** Bug 55903 has been marked as a duplicate of this bug. ***
I had a similar problem ... Machine is Compaq ML370, it did not boot with 2004.0 probably because of RAID, however 2004.1 booted but found no eth0. Since then I have tried a number of test CDs (as described in previous comments above) and all hung at: * Starting pci hotplugging... (which did not happen with 2004.1) I have tried the bootup parameter nohotplug but it makes no difference. TIA for any thoughts Charles
Which generation ML370? I have done testing myself on one and had no problems. Also, could every one *please* quit posting to this bug. It has been resolved for some time. Any other issues which you might want to discuss here are most likely a separate issue and should go under a separate bug.
