Network Issues after U-Boot Update 3.4.24 Downgrade 3.4.19

[odoll]

Hi, tried to upgrade to uboot 3.4.24, but couldn't boot from the SD-Card after the upgrade any longer. It complains the kernel would have an CRC error:

SD found. Card desciption is:
Manufacturer:       0x03, OEM "SD"
Product name:       "SD01G", revision 8.0
Serial number:      8941601
Manufacturing date: 5/2006
CRC:                0x00, b0 = 0

2770888 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.31.6
   Created:      2009-11-10   7:03:59 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2770824 Bytes =  2.6 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad CRC

As I couldn't get it fixed I decided to downgrade back to it's initial state of 3.4.19.

Though the kernel boots now

SD found. Card desciption is:
Manufacturer:       0x03, OEM "SD"
Product name:       "SD01G", revision 8.0
Serial number:      8941601
Manufacturing date: 5/2006
CRC:                0x00, b0 = 0

2770888 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.31.6
   Created:      2009-11-10   7:03:59 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2770824 Bytes =  2.6 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK

and everything seems to be mounted OK the ethernet interface is not coming up!? Both green and yellow LEDs are lit and blinking randomly. Just have the loopback interface?

root@Share:~# ifconfig
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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


However in u-boot I can ping remote hosts.

U-Boot 1.1.4 (Sep 14 2009 - 15:36:37) Marvell version: 3.4.19
[...]
Marvell>> setenv ipaddr a.b.c.254
Marvell>> ping a.b.c.1
Using egiga0 device
host a.b.c.1 is alive
Marvell>> ping a.b.c.5
Using egiga0 device
host a.b.c.5 is alive

PS:
root@Share:/proc# /etc/init.d/networking restart
 * Reconfiguring network interfaces...                                          SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
eth0: ERROR while getting interface flags: No such device
Failed to bring up eth0.

[odoll]

PS: my Marvell>> printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
serverip=10.10.0.2
ipaddr=10.10.0.1
cesvcid=ULULULULULULPPULULULULULDA
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethaddr=00:50:43:01:DA:3B
run_diag=no
arcNumber=2097
bootargs=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
bootcmd_nand_orig=nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_nand=setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd=run bootcmd_sd; run bootcmd_nand
bootargs_nand=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
bootcmd_sd=setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x8000000
console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=10 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=00 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no

[samweber]

Note that your "console" environment variable is whacked to "a0000".  It can be fixed by "resetenv" followed by "reset" but then you have to type in your non-default environment variables.  This probably has nothing to do with your network issue.  You could try the 3.4.25 u-boot from my "odd output" thread since it seems to have gotten past the environment corruption issue.  The "bad CRC" mess can be overcome by reloading the kernel per instructions there.  On the other hand, my plug has never booted from SD and I'm beginning to doubt that it ever will.  Hence, no warranty expressed or implied in my suggestions.

[rooster]

your console env is corrupted, fix it first.
You could also try the 3.4.25 I uploaded that fixes this one @ http://plugcomputer.org/plugforum/index.php?topic=921.msg5830#msg5830

[odoll]

thx for the hints - tried to fix the console variable but (as with 3.4.19?) it always shows up as odd.

Anyhow, got it 'fixed' for now by adding the IP info to the bootargs_sd string (strange: hasn't been there before and it worked so far!). Now it looks OK again:

Marvell>> setenv console 'console==ttyS0,115200'
Marvell>> setenv e
Marvell>> setenv bootargs_sd 'console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=10 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
Marvell>> saveenv

IP-Config: Complete:
     device=eth0, addr=10.4.50.4, mask=255.255.255.0, gw=10.4.50.5,
     host=DB88FXX81, domain=, nis-domain=(none),
     bootserver=10.4.50.5, rootserver=10.4.50.5, rootpath=
Waiting 10sec before mounting root device...
eth0: link up, 1000 Mb/s, full duplex, flow control disabled


root@Share:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:43:01:da:3b
          inet addr:a.b.c.254  Bcast:a.b.c.255  Mask:255.255.255.0
          inet6 addr: fe80::250:43ff:fe01:da3b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1991 (1.9 KB)  TX bytes:7870 (7.8 KB)
          Interrupt:11

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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

However there's another error running through while booting:

udevd-event[662]: error changing netif name eth0 to eth1: Device or resource busy

I think it has been there before already, because I always had that odd message in syslog:

Nov 14 15:27:44 Share nmbd[1619]:   queue_query_name: interface 1 has NULL IP address !

As I "bricked" both of my Plugs (thou one to be a cold standby as the other breaks) and as it took me quite some time today to fix it I don't know if I'm prepared to have another test with the 3.4.25 version, yet ... :-(

I think I'll need some tea first ... ;-)

[odoll]

The "bad CRC" mess can be overcome by reloading the kernel per instructions there.

Sorry, read thru the post but frankly - can't find the section you're referring, too - maybe because I'm on SD?
Or do you mean the section where you do the

Marvell>> nand erase clean 0x00100000 0x00400000

plus following? Oh, no - enough hassel for today 

[odoll]

OK, upgraded to u-boot 3.4.25 on my spare plug

U-Boot 1.1.4 (Nov 11 2009 - 16:17:48) Marvell version: 3.4.25

Marvell>> resetenv
Erase Env parameters offset 0xa0000... done
Warning: Default Environment Variables will take effect Only after RESET
Marvell>> reset
Marvell>> printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
bootcmd=tftpboot 0x2000000 $(image_name); setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000;
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
bootdelay=3
disaMvPnp=no
ethaddr=00:50:43:8e:22:31
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
pcieTune=no
ethact=egiga0

Set my (previous working) boot variables

setenv arcNumber 2097
setenv mainlineLinux yes
setenv bootcmd_uboot2_4_25 'tftpboot 0x2000000 $(image_name); setenv bootargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000;'
setenv bootcmd_orig 'nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
setenv bootargs_nand 'rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none'
setenv bootcmd_nand 'setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
setenv bootargs_sd 'console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=10 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw ip=a.b.c.253:a.b.c.1:a.b.c.1:255.255.255.0:DB88FXX81:eth0:none'
setenv bootcmd_sd 'setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x8000000'

Hence, no boot from SD any longer

SD found. Card desciption is:
Manufacturer:       0x03, OEM "SD"
Product name:       "SD01G", revision 8.0
Serial number:      8940619
Manufacturing date: 5/2006
CRC:                0x00, b0 = 0

2770888 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.31.6
   Created:      2009-11-10   7:03:59 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2770824 Bytes =  2.6 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.31.1
   Created:      2009-09-29  14:06:20 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2770136 Bytes =  2.6 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.31.1 (kelly@speedy) (gcc version 4.2.1) #1 PREEMPT Tue Sep 29 08:06:14 MDT 2009

[rooster]

Hi odoll,

So you can not load kernel from SD card and you were able to do it with 3.4.19 with the same uboot settings?
And NAND based kernel works fine, right?

[odoll]

Hi rooster,

correct.

In summary: SanDISK 1GB SD-Card with two partitions

Disk /dev/mmcblk0: 1015 MB, 1015808000 bytes
255 heads, 63 sectors/track, 123 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x6e652072

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1               1           2       16033+  83  Linux
/dev/mmcblk0p2               3         123      971932+  83  Linux

root@Share:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mmcblk0p2          956500    525084    392540  58% /
tmpfs                   256688         0    256688   0% /lib/init/rw
varrun                  256688       984    255704   1% /var/run
varlock                 256688         0    256688   0% /var/lock
udev                    256688       124    256564   1% /dev
tmpfs                   256688         0    256688   0% /dev/shm
/dev/mmcblk0p1           15523      8112      6610  56% /boot
/dev/sda1            961432072 865804516  85859948  91% /mnt/sda1
tmpfs                   256688     21824    234864   9% /var/cache/apt



U-boot 3.4.19: plug boots either from SD (if attached) or NAND.
Upgrade to 3.4.24: SD Kernel supposed to have CRC. Plug boots only from NAND
Downgrade to 3.4.19: boots from SD, but no eth interface till I added the IP info to the bootargs
Upgrade to 3.4.25: SD Kernel supposed to have CRC. Plug boots only from NAND

[carlos]

I have the same problem here on 2 of my sheevaplugs regarding the CRC error.
Regards

Carlos

[rooster]

Downgrade to 3.4.19: boots from SD, but no eth interface till I added the IP info to the bootargs

This sounds strange  , try to burn 3.4.19 and perform: reset;resetenv;reset

If no eth interface till you add the IP info to the bootargs then there is some change in your distro/uImage from the time it did work for you.

[carlos]

I am back now to 3.4.23 and everything is fine.
Regards

Carlos

[vioan]

I have the same Bad CRC. Where did you find 3.4.23? I am asking that because every time when I want to download and install 3.4.23 from the links mentioned in these forum, I get 3.4.24  . Thanks.

[carlos]

Look here:
http://www.plugcomputer.org/index.php/us/resources/downloads?func=select&id=6

[vioan]

Thanks. But, I think it is too much for me, I expected to find .bin file not all files.