Thanks for your effort  rooster, however unfortunately same issue here:

Updated from uboot-3.4.23 to .27. So far I could boot both an Ubuntu 9.04 from NAND and a Debian from SD (both with kernel 2.6.32.2 these days).

As with the uboot versions 3.4.24 and 3.4.25 the kernel  from SD is reported to have a "Bad Data CRC".

Luckily it falls back to the kernel in NAND and boots the Ubuntu. Mounting the SD and rewriting the kernel is not mitigating the situation.

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Dec 23 2009 - 13:32:43) Marvell version: 3.4.27

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
Error! cmd : 8, err : 0201
SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0

2861324 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 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.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.32.2 (kelly@speedy) (gcc version 4.2.1) #1 PREEMPT Fri Dec 18 22:54:28 MST 2009
[...]
Ubuntu 9.04 debian ttyS0

debian login: root
Password:
Last login: Wed Dec 23 19:31:06 CET 2009 on ttyS0
Linux debian 2.6.32.2 #1 PREEMPT Fri Dec 18 22:54:28 MST 2009 armv5tel
[...]
root@debian:~# mount /dev/mmcblk0p1 /boot
root@debian:/boot# ls -al /boot/
total 5545
drwxr-xr-x  3 root root    1024 Dec 19 12:02 .
drwxr-xr-x 21 root root       0 Dec 19 07:04 ..
drwx------  2 root root   12288 Dec 13 19:09 lost+found
-rw-r--r--  1 root root 2777892 Dec 19 12:00 sheeva-2.6.31.9-uImage
-rw-r--r--  1 root root 2861324 Dec 19 12:00 sheeva-2.6.32.2-uImage
lrwxrwxrwx  1 root root      22 Dec 19 12:02 uImage -> sheeva-2.6.32.2-uImage
root@debian:~# ./README-2.6.32.2 --rootkernel
Downloading files
Extracting modules
Writing kernel to /boot
****************************************************************
 update your bootcmd to load sheeva-2.6.32.2-uImage
 or use a symlink from /boot/sheeva-2.6.32.2-uImage to /boot/uImage
****************************************************************
root@debian:~# ls -al /boot/
total 5545
drwxr-xr-x  3 root root    1024 Dec 19 12:02 .
drwxr-xr-x 21 root root       0 Dec 19 07:04 ..
drwx------  2 root root   12288 Dec 13 19:09 lost+found
-rw-r--r--  1 root root 2777892 Dec 19 12:00 sheeva-2.6.31.9-uImage
-rw-r--r--  1 root root 2861324 Dec 23 19:39 sheeva-2.6.32.2-uImage
lrwxrwxrwx  1 root root      22 Dec 19 12:02 uImage -> sheeva-2.6.32.2-uImage
root@debian:~#reboot

[...]

SD found. Card desciption is:
Manufacturer:       0x1c, OEM "SV"
Product name:       "SDM  ", revision 1.0
Serial number:      2415946749
Manufacturing date: 3/2007
CRC:                0x00, b0 = 0

2861324 bytes read
## Booting image at 08000000 ...
   Image Name:   Linux-2.6.32.2
   Created:      2009-12-19   5:54:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2861260 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

PS: as the issue was introduced with .24 - what of the four changes from .23 may have introduced this behavior!?

OK - tnx. I read the nailed note about 9.10 http://plugcomputer.org/plugforum/index.php?topic=885.msg5473#msg5473, however reading

"The 9.04 Jaunty Jackalope version will be keep up-to-date by Ubuntu until 2011 or so, yet its not official. However you won't get the latest updates/packages like you'll get with 9.10 and future releases.
A solution is switching to Debian or another distribution."

I was under the impression that there would be at least some updates.

u-boot 3.423 / Kernel 2.6.32 / Ubuntu 9.04

Hi, I got my plug working since a few month now (from SD).  However, since the first update, following the instructions at http://plugcomputer.org/plugwiki/index.php/New_Plugger_How_To#Fixing_the_existing_Ubuntu_install, I think I never got any further updates for my installed packages, though adding new packages works.

root@Share:~# apt-get update
Hit http://ports.ubuntu.com jaunty Release.gpg
Hit http://ports.ubuntu.com jaunty Release
Hit http://ports.ubuntu.com jaunty/main Packages
Hit http://ports.ubuntu.com jaunty/restricted Packages
Hit http://ports.ubuntu.com jaunty/universe Packages
Hit http://ports.ubuntu.com jaunty/multiverse Packages
Reading package lists... Done
root@Share:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I find this odd as my Ubuntu-dist on my PC came with several updates since then?!? Is this just because the cycles on the ARM-branch are more seldom? Or is still something wrong with my FS?

root@Share:~# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/mmcblk0p2          956500    558372    359252  61% /
tmpfs                   256584         0    256584   0% /lib/init/rw
varrun                  256584      5476    251108   3% /var/run
varlock                 256584         0    256584   0% /var/lock
udev                    256584       124    256460   1% /dev
tmpfs                   256584         0    256584   0% /dev/shm
/dev/mmcblk0p1           15523      5601      9121  39% /boot
/dev/sda1            961432072 911760128  39904336  96% /mnt/sda1
tmpfs                   256584     21824    234760   9% /var/cache/apt

Feedback, hints and/or suggestions welcome!

as far as I can tell I was able to boot from SD with the 3.4.19 and 3.4.23 version (you should find a link for both somewhere in this forum).
I ran into trouble with 3.4.24 though also still waiting for an "official" 3.4.25 for some time, now  (http://plugcomputer.org/plugforum/index.php?topic=921.msg6113#msg6113)

http://thread.gmane.org/gmane.linux.kernel/921855 - eom

hm, since my plug was already on u-boot 3.4.25 and I couldn't boot fron SD any longer but from NAND I decided to test your ping issue and updated my spare plug from 2.6.31.1 in NAND to 2.6.31.6 (http://plugcomputer.org/plugforum/index.php?topic=921.msg5861#msg5861)

Unfortunately it doesn't boot any longer from NAND neither, now. I get a "Bad Magic Number" message. Couldn't get it solved so far (only limited time). Looks like I've to recover as explained in http://plugcomputer.org/plugforum/index.php?topic=921.msg5979#msg5979!?

Or would it be more easy to do a NAND 1-to-1 dump from my primary to my spare plug (going back to 3.4.19 and 2.6.31.1 in NAND in one go)?

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

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

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 

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 ... ;-)

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

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.

I accidently still hat the pre migation IP address in the cache file wins.dat. After deleting (renaming) the files the Plug comes properly as the primary DC.

think I got it, when I added host to

 name resolve order = wins host bcast

in the smb.conf

Hmm, tried to tweak IPv6, but issue persists ... anybody maybe any other hints?

****

PS: 2.6.31.4 #2 PREEMPT Tue Oct 13 07:36:55 MDT 2009 armv5tel

re https://help.ubuntu.com/community/WebBrowsingSlowIPv6IPv4
or https://help.ubuntu.com/9.04/internet/C/troubleshooting-lan.html#network-troubleshooting-ifconfig

 root@Share:/etc/modprobe.d# lsmod | grep inet6

but

 root@Share:/etc/modprobe.d# lsmod
 Module                  Size  Used by
 dm_crypt               14460  0
 dm_mod                 70700  1 dm_crypt
 ipv6                  271508  18

Created file etc/modprobe.d/aliases

 root@Share:/etc/modprobe.d# cat aliases
 alias net-pf-10 off

But after reboot though

 root@Share:/etc/modprobe.d# lsmod
 Module                  Size  Used by
 dm_crypt               14460  0
 dm_mod                 70700  1 dm_crypt

 root@Share:~# smbclient -L localhost
 Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME)

Created file /etc/modprobe.d/blacklist.local

 root@Share:/etc/modprobe.d# echo 'blacklist ipv6' | sudo tee -a '/etc/modprobe.d/blacklist.local' >/dev/null

But after reboot

 root@Share:~# lsmod
 Module                  Size  Used by
 dm_crypt               14460  0
 dm_mod                 70700  1 dm_crypt

 root@Share:~# smbclient -L localhost
 Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME)

 root@Share:~# ifconfig
 eth0      Link encap:Ethernet  HWaddr 00:50:43:01:d8:11
           inet addr:a.b.c.d  Bcast:a.b.c.255  Mask:255.255.255.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:504 errors:0 dropped:0 overruns:0 frame:0
           TX packets:497 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:44822 (44.8 KB)  TX bytes:46516 (46.5 KB)
           Interrupt:11

 lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:5 errors:0 dropped:0 overruns:0 frame:0
           TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:396 (396.0 B)  TX bytes:396 (396.0 B)

 root@Share:/etc/modprobe.d# rm aliases blacklist.local

Reboot

 root@Share:~# ifconfig
 eth0      Link encap:Ethernet  HWaddr 00:50:43:01:d8:11
           inet addr:a.b.c.d  Bcast:a.b.c.255  Mask:255.255.255.0
           inet6 addr: x::y:z:a:b/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:568 errors:0 dropped:0 overruns:0 frame:0
           TX packets:577 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:48945 (48.9 KB)  TX bytes:50671 (50.6 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)

Changed ipv6 entry in /etc/hosts from

 ::1     ip6-localhost ip6-loopback

to
 ::1     localhost ip6-localhost ip6-loopback

Reboot. No!

 root@Share:/etc# smbclient -L localhost
 Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME)

 root@Share:/etc# net rpc user
 Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME)

but

 root@Share:/etc# net rpc group
 Enter root's password:
 Domain Guests
 Domain Computers
 Domain Admins
 Domain Users