Network issue after upgrading

[littlebigman]

Hello

Based on this article, I ran the following commands to upgrade the applications:

 1. apt-get update
 3. apt-get dist-upgrade
 5. apt-get autoremove
 7. Launch a new SSH connection to the device to make sure you can still connect
 8. reboot

After rebooting the SP, I can no longer connect through SSH

So, following this article, I used the USB serial connection and typed the following commands, without understanding how to configure the IP part (192.168.0.10 = SP, 192.168.0.3 = Linux workstation, 192.168.0.254 = gw):

Code:

> setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=192.168.0.10:192.168.0.3:192.168.0.254:255.255.255.0:DB88FXX81:eth0:none init=/bin/bash
> boot

There seems to be an issue with how the network is configured:

Code:

eth0: link down
eth0: started
Sending DHCP requests .<5>eth0: link up, full duplex, speed 100 Mbps
..... timed out!
eth0: stopped
IP-Config: Reopening network devices...
eth0: link down
eth0: started
Sending DHCP requests .<5>eth0: link up, full duplex, speed 100 Mbps
., OK
IP-Config: Got DHCP answer from 0.0.0.0, my address is 192.168.0.10
IP-Config: Complete:
      device=eth0, addr=192.168.0.10, mask=255.255.255.0, gw=192.168.0.254,
     host=DB88FXX81, domain=, nis-domain=(none),
     bootserver=0.0.0.0, rootserver=0.0.0.0, rootpath=
md: Autodetecting RAID arrays.
[...]
Freeing init memory: 104K
root@DB88FXX81:/# ifconfig
Warning: cannot open /proc/net/dev (No such file or directory). Limited output.

FWIW, the LED on the hub shows that the SP is connected at 10Mbps, although the log says "eth0: link up, full duplex, speed 100 Mbps".

If someone's had the same issue, do you know what the problem is, and how to solve it?

Thank you.

[fragfutter]

ah copy paste... please decide which forum you want to ask the question and post a link in the other forum.



be careful with dist-upgrade, ubuntu 9.04 is the last version that supports armv5 (in case you rebuild the system i suggest switching to debian).

it would be interesting what errors you see when you reboot the plug with attached console.

But having connected a serial console and replacing init was a good idea. As a result you are now running a single process (bash) which did not do any init tasks. So nobody mounted procfs on /proc and ifconfig can't find anything there. So this seems fine. Please check a normal boot process with the console attached.