• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 ... 6 7 [8] 9 10
106  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 27, 2009, 02:51:56 AM
In .27 I first loaded the same kernel image once from usb (booting) and once from SD to the same memory location (having the strange idea that the ext2load in .27 might not fully load the image). Hence "CRC" error:

Marvell>> usb start
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
Marvell>> fatload usb 0:1 0x8000000 /uimage.bin
reading /uimage.bin
...

2861324 bytes read
Marvell>> mmcinit
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
Marvell>> ext2load mmc 0:1 0x8000000 /uImage

2861324 bytes read
Marvell>> bootm 0x8000000
## 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


BTW0: why does USB START report 2 and then just 1 USB device to be found? Is there another internal device connected by usb?!
BTW1: someone an idea, why the MMCINIT has the error message with SDs. As far as I can tell I don't get that message if I use SDHC!? And what does that message mean?

Another test .23 vs .27. I loaded the same kernel image once from usb (booting) and once from SD to different memory locations and did a memory comparison (cmp.b). When using .23 the loaded image in RAM is identical, if loaded with .27 they aren't (see attached files).
107  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 26, 2009, 03:14:12 PM
Came to the strange idea that the issue might be caused by an offset, but at least it's not as simple as

Marvell>>  ext2load mmc 0 0x8000000 /uImage

2861324 bytes read
Marvell>> bootm 0x8000001
## Booting image at 08000001 ...
Bad Magic Number
Marvell>> bootm 0x7ffffff
## Booting image at 07ffffff ...
Bad Magic Number
Marvell>> bootm 0x8000000
## 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
Marvell>> ext2load mmc 0:1 0x8000000 /uImage

2861324 bytes read
Marvell>> bootm 0x8000000
## 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


Though FAT from an USB-Pen works

Marvell>> usb start
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
Marvell>> fatload usb 0 0x8000000 /uimage.bin
reading /uimage.bin
...

2861324 bytes read
Marvell>> bootm 0x8000000
## 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 ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[...]
Debian GNU/Linux 5.0 debian ttyS0

debian login:



108  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 26, 2009, 11:13:07 AM
Quote from: pingtoo
I hope your did not take it offense ...

no, sure, np. Just happy to understand what I'm doing.

BTW: did another test with 3.4.23 vs. 3.4.27 and an SD formatted with FAT. With this .27 also has an issue though it looks a bit different. The fatload command goes wrong with .27 already (see attached file).

Saw you posted a startup script, but I didn't had time to look at it, yet. However will do for sure. Anyway I think the script won't work around the issue some of use are facing booting from SD since uboot 3.4.24!?
109  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 26, 2009, 08:17:49 AM
Quote from: pingtoo
If you still games, we can try this, do the same test sequence(6:5,5:5,5:6,6:6), only in between test you insert this
Code:
Marvell>> mw.b 0x08000000 0 0x400000
Marvell>> mw.b 0x00800000 0 0x400000
I think this will show you why your load command and bootm command must match.

yep, you're right - unfortunately my sequence wasn't the best one to go with. I'll cleared the ram as advised between the tests now and the result is as you expected.
110  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 25, 2009, 07:53:48 AM
Quote from: ccp
If you still games, we can try this, do the same test sequence(6:5,5:5,5:6,6:6), only in between test you insert this

@ccp: Planning to do some more testing as advised, but I spent this morning to prepare some SD-Cards for another test:

Quote from: rooster
Have you noticed that bot uboot versions the mmcinit gives some error?
Have you tried another SD card?

@rooster: yes, I noted the error, however as I get it either with 2.4.23 and 2.4.27 I didn't paid it too much attention, so far.

I hoped that the issue might be related to SD vs SDHC cards, but I tested a few this morning, which makes me think it doesn't.

I just noted that the error message doesn't show up if I use an SDHC (alike) card.

Summary: I cloned my working Debian RFS used on my test plug to a couple of other SDs (see attached jpg; only one still had a copy of the Ubuntu FS from my primary plug).

As with uboot 2.4.23 all work, as with uboot 2.4.27 all get a "Bad Data CRC" and they fall back to the kernel in NAND (see attached txt-files).

If you want to play around with my image: I made one a couple of days ago for a friend and put onto a network share. I can send you details if just like, just contact me.

Would it be possible to build and send me some (four) 2.3.24 flavors, each just adding one of the four fixes you made from .23 -> .24?

Quote
  U-boot 3.4.24
  =============
  -) Fixed in mv_main.c the initialization of nandEnvBase from "" assignment of the env variable which caused wrong display of "" in the mmcinit command to strcpy.
  -) Fixed nand mark bad function in nand_base.c to support non sector aligned addresses.
  -) Changed device number 1155 to 6282
  -) Fixed in nand_base.c the string assignments to nandEcc parameter which caused it to overflow into other strings.

 Thus I could at least identify with fix introduces the behavior I see.
111  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 24, 2009, 09:15:11 AM
Quote from: ccp
The linux kernel need to be load into memory completely before it can be started so the ext2load read from storage (SD,NAND,USB) into main memory then the bootm try to start it.

But isn't that exactly what confuses me!?! I again made a small test with 4 ext2load / bootm combinations, both for uboot 3.4.23 and 3.4.27 (nothing changed else!). I call them x:y where x stands for the number of trailing "0"s in ext2load command and y for the number of trailing zeros in bootm statement.

With 3.4.23 all combinations except for the first (6:5) boot the Debian from SD
With 3.4.27 all combinations except for the first (6:5) give a "Bad Data CRC".

For both uboot 3.4.23 and 3.4.27 the combination 6:5 gives a Bad Magic Number (see txt-files attached).
112  Hardware and U-Boot firmware / U-Boot stuff / Re: Howto copy debian on an usb-stick to a sd-card and boot from that? on: December 24, 2009, 08:13:45 AM
I once used the instructions at http://computingplugs.com/index.php/Booting_entirely_off_an_external_USB_device#Copy_over_the_default_kernel_and_filesystem to move the FS from the NAND to an SD-Card. I guess you can do the same adapting it for USB-Stick to SD.

However I would even would make an easier approach: making an image (e.g. with Winimage) of my USB-Stick and put the image back to my SD.

Of course you'd need to adapt the boot parameters as well, but because the confusion I have with those myself I won't make any recommendations ;-)
113  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 24, 2009, 06:14:48 AM
BTW: whether bootm 0x00800000 or bootm 0x008000000 makes no difference

I'm really getting confused: I find various versions in the Wikis, e.g.

http://www.plugcomputer.org/plugwiki/index.php/U-Boot_Quick_Reference
http://www.plugcomputer.org/plugwiki/index.php/External_Hard_Drives
http://computingplugs.com/index.php/Booting_entirely_off_an_external_USB_device
http://www.cyrius.com/debian/kirkwood/sheevaplug/unpack.html

Or does it depend on whether it's NAND, USB or SD?

However, either a get a "Bad Magic Number" error (bootm 0x00800000)
ot the "Bad Data CRC" error (bootm 0x008000000)
114  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 24, 2009, 05:26:08 AM
BTW: whether bootm 0x00800000 or bootm 0x008000000 makes no difference

Hit any key to stop autoboot:  0
Marvell>> mmcinit
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
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read
Marvell>> bootm 0x008000000
## 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


However with uboot 3.4.23

Marvell>> bubt u-boot-3.4.23.bin
Using egiga0 device
TFTP from server a.b.c.5; our IP address is a.b.c.253
Filename 'u-boot-3.4.23.bin'.
Load address: 0x2000000
Loading: #################################################################
         ############################
done
Bytes transferred = 474596 (73de4 hex)

**Warning**
If U-Boot Endiannes is going to change (LE->BE or BE->LE), Then Env parameters should be overriden..
Override Env parameters? (y/n) n
Erase 0 - 655360 ...
Copy to Nand Flash...
done
Marvell>> reset

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

U-Boot 1.1.4 (Nov  4 2009 - 12:58:36) Marvell version: 3.4.23

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
Marvell>> mmcinit
Error! cmd : 8, err : 0201
SDa0000 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
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read

Marvell>> bootm 0x00800000
## 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
115  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.27 on: December 24, 2009, 04:53:40 AM
Hi odoll,

I think you already spot your own error Smiley [...]  if you do [...] this should work.
rickyleeb and odol,
Did you get this uboot version working for you after setting the right uboot parameters?

Unfortunately no:

Hit any key to stop autoboot:  0
Marvell>> ext2load mmc 0 0x00800000 /uImage
** Bad partition 1 **
Marvell>> mmcinit
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
Marvell>> ext2load mmc 0 0x00800000 /uImage

2861324 bytes read
Marvell>> bootm 0x00800000
## 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 ... Bad Data CRC

116  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25 on: December 23, 2009, 01:38:33 PM
Yes, must be me being mistaken loading the kernel from NAND, but having the RFS running from SD :-(

Marvell>> setenv bootcmd_nand 'setenv bootargs $(bootargs_sd); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000'
Marvell>> run bootcmd_nand

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
[...]
Starting periodic command scheduler: crond.

Debian GNU/Linux 5.0 debian ttyS0

debian login:
117  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25 on: December 23, 2009, 01:14:38 PM
Puh, though really having no clue want I'm doing here neither understanding the bits and peaces of the boot variables I think I got it working, once!

While I was trying to boot the kernel from NAND but using the RFS from SD I figured that my NAND and SD strings differ at the following part (red):

bootargs_sd=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=5 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw ip=a.b.c.253:a.b.c.254:a.b.c.1:255.255.255.0:DB88FXX81:eth0:none
bootargs_nand=rootfstype=jffs2 console=ttyS0,115200 mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=a.b.c.253:a.b.c.254:a.b.c.1:255.255.255.0:DB88FXX81:eth0:none
bootcmd_nand=setenv bootargs $(bootargs_nand); nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_sd=setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x8000000


Thus I think I changed it to

setenv bootcmd_sd 'setenv bootargs $(bootargs_sd); mmcinit; ext2load mmc 0 0x8000000 /uImage; bootm 0x800000'

and it worked as I could log into the Debian.

However while trying to make it permanent it's going wrong again.

118  Hardware and U-Boot firmware / U-Boot stuff / Re: new uboot version 3.4.25 on: December 23, 2009, 12:04:45 PM
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!?
119  Linux Stuff / Linux distributions / Re: Ubuntu 9.04: No Updates since month? on: December 12, 2009, 12:57:51 PM
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.
120  Linux Stuff / Linux distributions / Ubuntu 9.04: No Updates since month? on: December 12, 2009, 05:39:58 AM
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!
Pages: 1 ... 6 7 [8] 9 10