Printable View
During the install it asks if you want to configure the network or let Dotsch do it. I always let it do it's thing. I've run Dotsh on everything up to and including my i7-920 and this is the first time I've had this issue. I think I have an old PCI network card around here somewhere. If I can dig it up I'll try it. If not, and this can't be fixed any other way I'll just let it run on Win7Quote:
Originally Posted by PoppaGeek
It'd be very unusual for it not to be able to handle the network interface.
can you copy and paste the output when you enter ifconfig -a as it might help
Here ya goQuote:
Originally Posted by D_A
boinc@Dotschhdd8:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr bc:ae:c5:a8:ac:9c
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:5661785488 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:249
eth0:avahi Link encap:Ethernet HWaddr bc:ae:c5:a8:ac:9c
inet addr:169.254.9.237 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:249
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:40 errors:0 dropped:0 overruns:0 frame:0
TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2944 (2.9 KB) TX bytes:2944 (2.9
How aboutOne of my machines looks like:Code:cat /etc/network/interfaces
Quote:
michael@node2:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth1
iface eth1 inet static
address 192.168.1.7
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.254
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.1.2
My guess is DHCP is not getting or not able to get it's IP. Make sure you have a good network cable. Is there a blinking light on the ethernet port?Quote:
Originally Posted by nanoprobe
This line shows linux sees the device:
eth0 Link encap:Ethernet HWaddr bc:ae:c5:a8:ac:9c <-- HWaddr is the Mac Address of the ethernet controller.
Goto System > Preferences > Network Connections then click eth0 then click Edit then on IPv4 Settings tab and make sure Method says Automatic (DHCP)
Added a Network Troubleshooting section to first page, second post. Comments and suggestions please.
Please keep in mind I am trying to keep things as simple as possible and still useful using the commands installed by default.
Question. Is showing the full printout of the ifconfig command too much info? shoued I edit out all that is not helpful?
I think the full return would be most appropriate just so folks don't think it will only return a couple of lines and instead get a page of stuff and freak.
I think it's great!
Thanks for input!
Added Quote boxes to output for readability and did some editing.
Sorry for the delay in getting back. When I go to network connection it shows auto eth5 instead of eth0. Also, on the right side of the window it says never in what looks to be grayed out print. I tried to edit it to eth0 but that didn't work. DHCP is on auto.Quote:
Originally Posted by PoppaGeek
If you can tell me the make model of the motherboard, assuming the nic is built in, I can try and find the chipset and see if drivers are available. I have a feeling that the distro does not have the drivers for the nic.
Thanks
It would be a VERY odd nic that doesn't have drivers in Linux of any modern distro.
nano
enterinto a terminal an paste the output here for us.Code:cat /etc/network/interfaces
Do not know how easy it is for him to cut and paste if it is not on the network.Quote:
Originally Posted by D_A
Ok then, let's back up a bit. nano, when you were working on it before did you have terminal access or are you using a desktop (gnome/KDE/XFCE etc)?
Here ya go.Quote:
Originally Posted by D_A
boinc@dotschuxUSB3:~$ cat /etc/network/interfaces
# Used by ifup(8) and ifdown(8). See the interfaces(5) manpage or
# /usr/share/doc/ifupdown/examples for more information.
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet dhcp
auto eth2
iface eth2 inet dhcp
auto eth3
iface eth3 inet dhcp
Hmmm ... You see any problem with that PG, coz I don't ... unless the router has either run out of dynamic address space or just isn't accepting DHCP requests.
nano you can try typing at the command line sudo ifconfig eth0 192.168.1.50 netmask 255.255.255.0 up IF your network is 192.168.1.x if not then use thec correct network and an ip not used elsewhere. Tells us what is says.
OK 2 things you can do although they are getting kinda ugly.
Do a sudo lsmod and post the output here, since you seem to have a way of doing that.
Do a sudo lshw the output will probably be very long. It will show if there is a driver loaded for the nic. Look for the line description: Ethernet interface. Then in that block look for driver=:
If driver= shows nothing then second and third line product: and vendor: lines. Or just post the same block here. If there is more than one Ethernet interface then we need all.Quote:
*-bridge:0
description: Ethernet interface
product: MCP55 Ethernet
vendor: nVidia Corporation
physical id: 8
bus info: pci@0000:00:08.0
logical name: eth0
version: a3
serial: 00:50:45:02:61:49
width: 32 bits
clock: 66MHz
capabilities: bridge bus_master cap_list ethernet physical
configuration: broadcast=yes driver=forcedeth driverversion=0.64 latency=0 maxlatency=20 mingnt=1 multicast=yes
resources: irq:30 memory:d0009000-d0009fff ioport:2808(size=8) memory:d0005800-d00058ff memory:d0005400-d000540f
Went back thru your posts. The Asus P8P67-M Pro uses the Realtek RTL8111E Gigabit LAN controller and should be supported. To try and make this a little easier please try these in order.
Swap ethernet cable
Check if leds are blinking at ethernet port
Wait a few minutes then type ifconfig and see if there is an IP number assigned. Try to ping 8.8.8.8
If still no IP Try typing at the command line sudo ifconfig eth0 192.168.1.50 netmask 255.255.255.0 up IF your network is 192.168.1.x if not then use the correct network and an ip not used elsewhere. If you do not know what your network is try this on a Windows machine. ipconfig Notice this is iPconfig not the ifconfig on linux. Look for IPv4 Address.......: might ought to write down Default Gateway as well may need it later. Use the same numbers as what ipconfig shows except for last one. Use a number under 254 that is not used on another machine on the network. So if the ipconfig on Windows shows 10.10.1.20 replace 192.168.1.50 with 10.10.1.100. BTW 2 common network numbers are 192.168.1.x and 192.168.0.x These are NOT the same network. First 3 sets of numbers need to be the same and last one unique between 2 and 254. The Netmask should be 255.255.255.0
After running sudo ifconfig eth0 192.168.1.50 netmask 255.255.255.0 up try to ping your router or another PC on your network or 8.8.8.8 (Googles DNS server)
To get to a command prompt on Windows:Quote:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\poppageek>ipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::f9fd:3135:256:fcd%10
IPv4 Address. . . . . . . . . . . : 192.168.1.119
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
Tunnel adapter Local Area Connection* 6:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Local Area Connection* 7:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:1444:1147:3f57:fe88
Link-local IPv6 Address . . . . . : fe80::1444:1147:3f57:fe88%12
Default Gateway . . . . . . . . . : ::
C:\Users\poppageek>
Start Button > All Programs > Accessories > Command Prompt
Not trying to say you do not know how to do anything just not making any assumptions and this info might help others.:up:
To manually setup a network interface instead of using DHCP:
Assumes Ubuntu, wired ethernet and using GUI.
System > Preferences > Network Connections > Click on interface listed such as eth0 > Edit > IPv4 Settings tab
Next to Method click on and select Manual > Add > Enter Address, Netmask and Gateway then DNS servers. Use your router, ISP DNS servers or Googles DNS 8.8.8.8 8.8.4.4 which I find are more reliable and faster than my ISPs. Just click on the box under each to start entering Address, Netmask and Gateway.
Gateway will usually be your router. Netmask is usually 255.255.255.0.
http://img.techpowerup.org/110209/111222333.jpg
In network connections it lists auto eth5 not eth0. I tried to manually set it but when I reboot it's back to auto. I'm beginning to think that this hardware is just too new and I don't have the correct driver. I'm going to try a beta live CD and see if that connects.Quote:
Originally Posted by PoppaGeek
I booted to a live cd beta and it connects so I'm guessing this is a driver issue. I noticed that when I try to manually set up the network in Dotsch it doesn't see the router. I put in the gateway IP but when I hit ok the ip goes to 0.0.0.0
Thanks for all the help. I don't think there is anything else that can be done.
I wonder if permissions are keeping you from saving the settings. :shrug:
Why not install the latest release of Ubuntu? I did searches and the chipset does seem to be supported in 10.x.
How do I find out if I have the proper permissions and is there a way to change it if I don't?Quote:
Originally Posted by PoppaGeek
I may do that. It's just that I really like Dotsch for dedicated crunchers.Quote:
Originally Posted by PoppaGeek
I run Ubuntu Server edition for my headless rigs. Very lean install but NO desktop environment (which would steal cycles anyway). Just make sure you select to install the OpenSSH Server at install time so you can log in for maintenance remotely. You'll get the option to choose if you want automatic updates or not as well and BOINC is in the repositories, which I recommend you use so that it will run without a user logged in.