new install is successful but when reboots, gets no IP address

[ghurty]

I have a fresh install on a atom d510 motherboard.

Everything installed successfully, and I was able to access the system from a different computer.

However, now that I restarted it, it does not get an IP address.

After waiting a while getting getting IP for eth0, it says that no bytes recieved for when it was pinging 192.168.1.1 from 192.168.1.151 (which was its old ip address).

Thanks

 

[blanchae]

From the Linux command prompt, what does "ifconfig" respond with?

 

[ghurty]

It lists tons of data for eht0, which one should I pass one, there is no IP address, but there is an inet6 addr

 

[grumpy]

Is it an Intel motherboard or a third party with an atom on it? (my intel atom board had no driver issues)

From the Linux command prompt, what does "dmesg" respond with? Looking for a line like this.

eth0: RTL8168c/8111c at 0xf88e4000, 00:1c:c0:c2:09:d7, XID 1c4000c0 IRQ 50

also if you use netconfig or setup are you able to put in a static ip?

 

[blanchae]

Do you have an "/etc/sysconfig/network-scripts/ifcfg-eth0.cfg" file? Are there any ifcfg-eth?.cfg files present?

 

[blanchae]

Here's what a typical static IP /etc/sysconfig/network-scripts/ifcfg-eth0.cfg looks like:

BOOTPROTO=none
NAME="Data Interface"
DEVICE=eth0
MTU=""
HWADDR=00:12:34:56:78:90
IPADDR=192.168.102.254
NETMASK=255.255.255.0
ONBOOT=yes

HWADDR is the mac address of your NIC. In /etc/sysconfig/network should be an entry for your default gateway.

 

[Linetux]

You have a bad driver on the NIC.

You need to do one of two things:

1) Upgrade the driver manually

2) Upgrade your version of PIAF, as the newest version with Cent 5.3 fixes this issue.

 

[ghurty]

When I run netconfig and set it manually, it gets an IP address, however it sometimes still has problems pinging.


I am using the latest build of pbiaf so that has centos5.5
and I do have the ifcfg-eth0.cfg file.

Thanks

 

[grumpy]

Great you now have a connection of sorts! Seeing as it is a fresh install how about running:

update-source
update-scripts
update-fixes

when you ran netconfig did you use a static ip, or set it back for DHCP with a reservation in the router for that mac address?

 

[Linetux]

Telltale sign of a bad driver on these NIC's: errors on the interface:


$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:30:48:9E:53:8A
inet addr:172.20.16.8 Bcast:172.20.16.255 Mask:255.255.255.0
inet6 addr: fe80::230:48ff:fe9e:538a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:41562179 errors:0 dropped:0 overruns:0 frame:0
TX packets:60925293 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3166143968 (2.9 GiB) TX bytes:1083958886 (1.0 GiB)
Interrupt:58 Base address:0x4000

 

[Linetux]

The real problem is the r8169 driver. If you have it, you need to get the updated one.

$ lsmod | grep r8169

If you get a response, you have the wrong driver installed. You need to get the 8168 driver (you can get it from Realtek's site) and compile it, then blacklist the 8169 driver.

I believe this has already been covered in the forums, so I won't post details here again.

 

[dswartz]

wouldn't it be better to use piafextras-menu and install that way? I seem to recall my intel atom (jetway?) mobo just needed the v007 8169 driver installed.

 

[Linetux]

8169 in some Atom boards causes this problem... you need the 8168.

 

[grumpy]

Linetux is this issue in some but not others, reason I ask it seems like I have that driver. And the only network issues I'm having are due to 2 routers connected but on different networks.

************************
root@pbx:~ $ lsmod | grep r8169
r8169 43461 0
mii 9409 1 r8169
root@pbx:~ $


Thread with the instructions.

http://pbxinaflash.com/community/threads/how-to-get-around-eee-box-b202-nic-issue.4794/?t=4794

 

[Linetux]

Check for bad packets as I said above. If you see them, you've got a bad driver and you need to change it.

I'm pretty sure this is a chipset/southbridge problem, which means that some boards will have the issue, others won't.

 

[dswartz]

not to beat a dead horse, but i would try the piafextras approach. it will let you either use the 8168 driver or a newer 8169 driver - try both and see which works best for you.

 

[ghurty]

I tried all the options in the xtras menu with no success. I think there is a problem with this particular board, as I have successfully installed piaf on a dm510mo in the past.