On 4/19/06, Michael Sullivan <[EMAIL PROTECTED]> wrote: > The guy I'm helping to install Gentoo says that he can get to his Linux > installation and log in, but that he has no network unless he boots with > the LiveCD. I've tried every trick I know. At this point he's booted > with the LiveCD and entered his chroot install environment. Out of > desperation for some way to find what the problem is, I asked him to > take a look at ifconfig. According to what he told me, eth1 has an IP > address, but there's no mention of eth0. In the past he's told me that
The genkernel on the LiveCD supports most hardware, so, its likely it suports firewire, but maybe the kernel you're booting after without the CD doesn't, so, you gotta add the eth0 to the runlevel. In any case, try both. The most obvious reason he doesn't have network when booting without the LiveCD is because: 1) Wrong init script (eth0 or eth1) 2) Wrong or no kernel module or support builtin for the network card. > the PC he's installing Gentoo on has a wired NIC and a wireless NIC. I > assume this is why his network card is assigned eth1, and that the > wireless card is eth0 and the LiveCD doesn't support it. The handbook MOST wireless cards are unsupported but can be used (not for installation) with ndiswrapper (that is the case for MOST notebooks outthere). The cause of the eth1 being the second NIC is probably because your friend has a Firewire connector, that is recognized by most kernels as an ethernet adapter (I even disabled mine). Try booting using the nofirewire option for the kernel on the LiveCD, if your NIC becomes eth0, you got the problem. > says that if multiple network interfaces exist, one can create symlinks > to /etc/init.d/net.eth0 for each successive network interface. My > question is if I tell him to rc-update add net.eth1 default and then to > symlink /etc/init.d/net.eth1 to /etc/init.d/net.eth0, when he reboots, > won't Gentoo just try to start /etc/init.d/net.eth0, which won't work at No, I was also confused once by the way symlinks work, but when its regarding init scripts, trust the manual. It won't boot unless you ADD it to the runlevel. It seems the name is more important than the file itself at this point. > this point? What should I do? I've told him what the handbook says, > but I'm not sure that it will work. Besides, configuration is read from /etc/conf.d/net for each card, if you don't define any, it will read DHCP for any eth.* on your init level. -- Daniel da Veiga Computer Operator - RS - Brazil -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE BLOCK------ -- gentoo-user@gentoo.org mailing list
