via-rhine livecd 1.4_rc1: autodetected but non-functioning

b1nd0x · n00b Joined: 11 Sep 2002 Posts: 8 Location: cambridge, ma

I actually got around this problem (in the subject: via-rhine not working after booting 1.4livecd) by booting off of the 1.2 CD (where via-rhine, mii are loaded as modules automatically by the pci-autodetect rather than built in) and then decompressing the 1.4 stage 1 tarball off the 1.4 CD, but i'm still curious as to why this was happening:

After booting from the 1.4 live cd, DMESG indicates that it found the via-rhine and eth0 is using it, but then dhcpcd eth0 results in nothing, no error message nothing just (presumably) a timeout and no connection.

This resulted in an amusing catch-22: at my school, if you're connecting to the network with a new ethernet controller, you have to validate the account with your username, student ID, etc., so you don't get a real IP and can't get outside connections: if you bring up a browser a transparent proxy bounces you to the registration page. However when booting off of 1.2, i would need to download lynx so i could register my connection so i could make outside connections to download lynx! Luckily you can just type in the MAC address, so after a while staring at the screen i remembered this and went and did it from a comp. down the hall.

b1nd0x · n00b Joined: 11 Sep 2002 Posts: 8 Location: cambridge, ma

oh, btw it's a SOYO dragon ultra (KT400) with onboard ethernet. now only if it would boot (ah hardware raid, how i love and loathe thee)

sdsheeks · Posted: Sat Dec 21, 2002 4:44 pm Post subject: Thanks :)

I installed Gentoo a few weeks ago after spending 4 hours trying to get my card to work. I then decided to come to this forum for some help and found your article. Thank you

It worked just fine after booting from the 1.2livecd then using the 1.4 files after the network was setup.

Great!

Thanks
Dave
_________________
--sdsheeks

ki · n00b Joined: 11 Feb 2003 Posts: 1 Location: NH

I also ran into this same problem.
Here's a question for you though- I can't seem to get the internet to work after downloading all the packages. I've tried compiling the via-rhine support into the kernel and as a module (and modprobing it), but neither seemed to work w/o the disc...

Thanks
_________________
#--Ki--#

Gnufsh · Guru Joined: 28 Dec 2002 Posts: 400 Location: Portland, OR

found a couple posts in the kernel mailing lists. This one reports the problem:

Gnufsh · Guru Joined: 28 Dec 2002 Posts: 400 Location: Portland, OR

found a couple posts in the kernel mailing lists. This one reports the problem:

HuGoBioS · Posted: Sat May 03, 2003 9:21 pm Post subject:

i've got the same motherboard and the only way i found was to disable APIC-IO ...
but the matter is that SCSI controllers (aic7xx or dc390) need APIC-IO too work ... so i can't have both lan and scsi :cry:

_________________
N'imitez pas : INNOVEZ

HuGoBioS · Posted: Sat May 03, 2003 10:55 pm Post subject:

ok solved : active APIC-IO in the kernel BUT de-activate it in the bios !
_________________
N'imitez pas : INNOVEZ

muckdog · n00b Joined: 05 Jun 2003 Posts: 5

I'm having the same problem with the via-rhine device. It is the on board card on my Soyo SY-K7VME (KT400 chipset). However I figured I could get around this by slapping in a known good 3com 3c905 card. Same problem. Kernel sees it modules load but I can't bring up the link. I have a cable tester and teh cable was good. This onboard card did work when I was running win2K on it. I don't have a firewire module incorrectly loaded like one post mentioned. I've tried the 2004.1 live CD and the knoppix 3.3 cd. I've disabled APIC in the bios and when booting the kernel.

wolfger · Posted: Thu Jul 08, 2004 12:16 am Post subject:

I have Soyo Dragon Ultra mobo, and I am having problems as well. With APIC enabled in bios, it detects my eth0 as module eth1394, but the dhcp assigned ip is wrong, and even if I manually set the ip, I can't see anything else on the network. Modprobing via-rhine doesn't help.

If I disable APIC in bios, things are worse. No hardware detection at all.

:-(

(using 2004.1 universal)