| View previous topic :: View next topic |
| Author |
Message |
pns
n00b
Joined: 25 Aug 2006
Posts: 5
|
 Posted: Fri Aug 25, 2006 7:22 am Post subject: NIC detected but not working [solved] |
 |
|
Hi,
I tried to install gentoo 2006.0 from the minimal boot images. Unfortunately my NIC does not work. It is detected correctly as via-rhine and I can assign an IP etc. but it just does not connect. I can't ping anywhere, not even my router. I attached the "messages" (because it contains some error messages that might help you telling me what's wrong) and and output of "ifconfig eth0".
http://pastebin.ca/148585 (ifconfig eth0)
http://pastebin.ca/148587 (/var/log/messages, if you scroll down you'll see some messages regarding the via-rhine NIC)
Thanks in advance!
Last edited by pns on Sat Aug 26, 2006 1:21 pm; edited 1 time in total |
|
| Back to top |
|
 |
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Fri Aug 25, 2006 10:54 am Post subject: |
|
|
i would have two ideas: a) did you try to disable acpi? (kernel option "noacpi") b) could you post the output of "route -n"?
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
davascript
l33t
Joined: 07 Apr 2004
Posts: 618
Location: Pennsylvania
|
| Posted: Fri Aug 25, 2006 1:33 pm Post subject: |
|
|
It sounds like your name resolution isnt working. But can you post the contents of your networking files
| Code: | nano -w /etc/resolv.conf
nano -w /etc/conf.d/net |
|
|
| Back to top |
|
|
pns
n00b
Joined: 25 Aug 2006
Posts: 5
|
| Posted: Fri Aug 25, 2006 5:25 pm Post subject: |
|
|
So I disabled acpi, unloaded the firewire kernel module (I read about it on these forums) and completely reconfigured the eth0 device. It still does not work.
@davascript: It's not a dns prob as I can't even ping my own router. It's not a router/nic prob either, it works fine.
well here some data:
ifconfig eth0
| Code: | eth0 Link encap:Ethernet HWaddr 00:13:D3:CB:03:E2
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:4 overruns:0 frame:0
TX packets:0 errors:5 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:3 Base address:0x8000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3976 (3.8 Kb) TX bytes:3976 (3.8 Kb)
|
/etc/conf.d/net
| Code: | config_eth0=( "192.168.1.100 netmask 255.255.255.0 broadcast 192.168.1.255" )
routes_eth0=( "default via 192.168.1.254" )
dns_servers_ESSID=( "192.168.1.254" )
|
route -n
| Code: | Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 192.168.1.254 0.0.0.0 UG 0 0 0 eth0
|
lsmod:
acpi, ieee1394 = not loaded
via_rhine = loaded (among others of course, I got a dump of lsmod as well but it's quite long so I didn't post it)
Thanks so far, for your replies! |
|
| Back to top |
|
|
davascript
l33t
Joined: 07 Apr 2004
Posts: 618
Location: Pennsylvania
|
| Posted: Fri Aug 25, 2006 6:09 pm Post subject: |
|
|
| Quote: | | It's not a dns prob as I can't even ping my own router. |
Does your router have reply to ping enabled? Can you ping it from another OS? |
|
| Back to top |
|
|
pns
n00b
Joined: 25 Aug 2006
Posts: 5
|
| Posted: Fri Aug 25, 2006 8:19 pm Post subject: |
|
|
| davascript wrote: | | Quote: | | It's not a dns prob as I can't even ping my own router. |
Does your router have reply to ping enabled? Can you ping it from another OS? |
Yes icmp reply is enabled. It is not a router prob. It is definitely some sort of driver/kernel module prob or maybe a setting. But outside of the gentoo cli (i.e. in ubuntu) it works just fine. |
|
| Back to top |
|
|
davascript
l33t
Joined: 07 Apr 2004
Posts: 618
Location: Pennsylvania
|
| Posted: Fri Aug 25, 2006 8:32 pm Post subject: |
|
|
| Quote: | | It is not a router prob |
I do not think tyour router has a problem. I am just shooting for the little things thathelp me visualize your problem, situation, and configuration.
Is via_rhine compiled as amodule in your kernel. please post your kernel config file specifically just the device drivers section. |
|
| Back to top |
|
|
pns
n00b
Joined: 25 Aug 2006
Posts: 5
|
| Posted: Fri Aug 25, 2006 8:44 pm Post subject: |
|
|
| davascript wrote: | | I do not think tyour router has a problem. I am just shooting for the little things thathelp me visualize your problem, situation, and configuration. |
I didn't mean to be rude, sorry! I just wanted to avoid to go down the router-problem-road, simply to save time.
| davascript wrote: | | Is via_rhine compiled as amodule in your kernel. please post your kernel config file specifically just the device drivers section. |
I didn't compile a kernel, I'm stuck at the installation (the cli right after you boot from cd and typed the boot command). So this is the default kernel which came with the 2006.0 minimal image, that's why it surprises me that it doesn't work. Every other distro I use hasn't ever had a prob with my nic. |
|
| Back to top |
|
|
davascript
l33t
Joined: 07 Apr 2004
Posts: 618
Location: Pennsylvania
|
| Posted: Fri Aug 25, 2006 8:52 pm Post subject: |
|
|
it looks like the kernel on the livecd istn liking your NIC. try passing some of the other hardware options at boot time
| Code: | Aug 25 00:29:12 livecd eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Aug 25 00:30:40 livecd NETDEV WATCHDOG: eth0: transmit timed out
Aug 25 00:30:40 livecd eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Aug 25 00:30:40 livecd via-rhine: Reset not complete yet. Trying harder.
Aug 25 00:30:40 livecd eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Aug 25 00:32:26 livecd NETDEV WATCHDOG: eth0: transmit timed out
Aug 25 00:32:26 livecd eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Aug 25 00:32:26 livecd via-rhine: Reset not complete yet. Trying harder.
Aug 25 00:32:26 livecd eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Aug 25 00:32:42 livecd NETDEV WATCHDOG: eth0: transmit timed out
Aug 25 00:32:42 livecd eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Aug 25 00:32:42 livecd via-rhine: Reset not complete yet. Trying harder.
Aug 25 00:32:42 livecd eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Aug 25 00:33:58 livecd NETDEV WATCHDOG: eth0: transmit timed out
Aug 25 00:33:58 livecd eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Aug 25 00:33:58 livecd via-rhine: Reset not complete yet. Trying harder.
Aug 25 00:33:58 livecd eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Aug 25 00:37:28 livecd NETDEV WATCHDOG: eth0: transmit timed out
Aug 25 00:37:28 livecd eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Aug 25 00:37:28 livecd via-rhine: Reset not complete yet. Trying harder.
Aug 25 00:37:28 livecd eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Aug 25 00:38:05 livecd eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Aug 25 00:38:05 livecd eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 |
did you try |
|
| Back to top |
|
|
pns
n00b
Joined: 25 Aug 2006
Posts: 5
|
| Posted: Sat Aug 26, 2006 1:13 am Post subject: |
|
|
It's all sorted now. Turns out my hunch with the firewire adaptor was right. It was in fact the eth0 device and ONLY after booting with "gentoo-nofb acpi=off noapic" and unloading all kernel modules refering to ieee1394 it disabled it. And then, finally, I could set up the NIC as eth1.
Anyway, I thank you for the help and time  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
