[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Not accessing network after apparently succesful settrans of the /hurd/pfinet



On Sun, Aug 28, 2005 at 07:33:08PM -0600, Javier-Elias Vasquez-Vivas wrote:
> After not being able to use the ethernet device of my laptop, I
> decided to try out a friend's box after a crosshurd installation.
> 
> When performing "cat /dev/klog" I get:
> 
> eth0: VIA VT6105LOM Rhine-III (3106) at 0xd000, (MISSING EEPROM
> ADDRESS)3e:4c:69:6e:75:78, IRQ 10.
> eth0: MII PHY found at address 1, status 0x786d advertising 5e1 Link 45e1.
> 
> Apparently the ethernet card was recognized...  

You can make sure by running 'devprobe eth0' as root.  It should output
'eth0' if the network driver is indeed present as far as Mach is
concerned.

> root  90  0.0  0.3  131M  1.44M  -  So  7:42PM  0:00.03  /hurd/pfinet 
> -i eth0  -a <assigned_ip>  -m 255.255.255.0  -g <dhcp_server_ip>
> 
> However after performing "ping <dhcp_server_ip>" the console just
> hangs forever.  In case "ping" was not working properly I also tried
> "apt-get update", and it also hangs forever.  I looked at the card
> leds, and although it's powered, it experiences no activity...

Did you set a DNS server in /etc/resolv.conf?  Does it hang when you
ping IP addresses as well?  Try 'ping <dhcp_server_ip>', does that work?


Michael

-- 
Michael Banck
Debian Developer
mbanck@debian.org
http://www.advogato.org/person/mbanck/diary.html



Reply to: