| View previous topic :: View next topic |
| Author |
Message |
sustain
n00b
Joined: 30 Jun 2007
Posts: 11
|
 Posted: Sat Jun 30, 2007 11:58 am Post subject: Can't get connected to the internet |
 |
|
Hi
I finally decided to get gentoo on my laptop. The installation went pretty well but when I chrooted I wasn't able to get my network running.
I emerged dhcpcd but the client fails to load at start up - it just simply times out and I get the error:
"Error, eth0: timed out"
After login I checked ifconfig and eth0 is not activated. I then tried "ifconfig eth0 up" and now eth0 seems to activated in the list of ifconfig but again, if I try running "/etc/init.d/net.eth0 start" dhcpcd fails to load with the same error as above.
If it can be of any help this is my /etc/conf.d/net:
config_eth0( "dhcp" )
dhcp_eth0="nodns nontp nonis"
If you need more info, just let me know 
... and thanks for a great forum! |
|
| Back to top |
|
 |
John R. Graham
Administrator
Joined: 08 Mar 2005
Posts: 10733
Location: Somewhere over Atlanta, Georgia
|
| Posted: Sat Jun 30, 2007 12:12 pm Post subject: |
|
|
Yep, more info needed.  Tell me what lspci says about your Ethernet adapter. Then we'll check out what drivers you need to enable for that hardware.
- John |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54850
Location: 56N 3W
|
| Posted: Sat Jun 30, 2007 12:17 pm Post subject: |
|
|
sustain,
Try the steps here if that fails we need the following information.
The Ethernet line from use the liveCD if needed.
The list of interfaces from when you boot normally and the network fails.
If eth0 is not listed, your kernel module is not loaded.
Exact error messages from dmesg or the screen.
When it looks like it might be alive, try
and if the first works but not the second, you have a name resolution issue, as they are both google.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Sat Jun 30, 2007 12:30 pm Post subject: |
|
|
Try setting the timeout option for dhcpcd. It's supposed to default to 20s. If you start eth0 manually, is that about how long it takes before you get the error message? Older versions used a timeout of 60s.
_________________
Thomas S. Howard |
|
| Back to top |
|
|
sustain
n00b
Joined: 30 Jun 2007
Posts: 11
|
| Posted: Mon Jul 02, 2007 10:49 am Post subject: |
|
|
NeddySeagoon,
I followed your guide and eth0 and eth1 are listed using ifconfig -a.
eth0 has the HWaddr 65-3F-02-00-2D-42-40-84-00-00-00-00-00-00-00-00
does this mean that eth0 is ethernet over firewire and how do I solve this? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54850
Location: 56N 3W
|
| Posted: Mon Jul 02, 2007 5:58 pm Post subject: |
|
|
sustain,
Yes - your eth0 is ethernet over firewire.
Find the eth1394 entry in and either rename the file or delete it.
Thats a bit of a dirty hack as it will come back next kernel update.
When the module can no longer load, the old eth1 will become eth0.
You can also just set up eth1 and ignore eth0
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
didymos
Advocate
Joined: 10 Oct 2005
Posts: 4798
Location: California
|
| Posted: Mon Jul 02, 2007 6:10 pm Post subject: |
|
|
Couldn't you just change the interface number with a udev rule?
_________________
Thomas S. Howard |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54850
Location: 56N 3W
|
| Posted: Mon Jul 02, 2007 6:29 pm Post subject: |
|
|
didymos,
You cannot normally use kernel names, as the interface name you want to use could already e allocated but yes, you can do interface naming based on the MAC adderss. Thats a lot harder to explain though.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
|
Networking & Security
