• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: [1] 2 3 ... 16
1  General Category / Application ideas and development Q/A / Re: Using the Sheevaplug Blue LED to notify of new mail. on: May 06, 2012, 03:27:02 PM
small update to this.   This has been bulletproof for many years.   However I recently updated my plug to a new kernel and new Debian install, and this stopped working.    It's because it finally uses the correct LED labels in the kernel now...   The Blue LED's are referenced by blue in the script...

echo "none" > /sys/class/leds/plug\:blue\:health/trigger

Just incase someone else uses this and wonders why it stopped working...
2  Linux Stuff / Kernel / Re: sheeva/dream 3.2.5 new kernel available on: February 10, 2012, 10:01:58 AM
First I tried...

Unfortunately, anyone else that takes the link from the Debian Linux page will also see the recommendation to upgrade u-boot.

http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html

"You have to upgrade the u-boot boot loader before you can install Debian. "

This was the root of all my problems :-(
3  Linux Stuff / Kernel / Re: sheeva/dream 3.2.5 new kernel available on: February 08, 2012, 11:28:13 AM
Confirmed working on my Sheevaplug running Denx U-Boot 2011.12 (Jan 08 2012 - 21:53:47)

This is the first 3.2 kernel that has worked for me using this U-Boot (they all worked using the Marvell U-Boot).
4  Linux Stuff / Kernel / Re: Booting kernels 3.2 and later on: February 07, 2012, 10:57:45 AM
Hmm, wondering if this is the problem I was having with non booting kernels on a sheevaplug?

I ran 3.2 without any problems, using an old u-boot, I rebuilt my plug and used the latest DENX u-boot and it wouldn't boot the same 3.2 binary that booted previously with a tweaked Marvell uboot(3.4.27 - pingtoo patch.03)...  I sorta mentioned this a while back.

Before I go off and screw up my plug, do you think things are now OK in respect to the non-booting problems?  Will my u-boot change be the culprit of why I couldn't boot 3.2?
5  Linux Stuff / Kernel / Re: 3.2 new kernel available on: January 12, 2012, 12:03:19 PM
Can confirm Something fishy going on with 3.2...

http://www.plugcomputer.org/plugforum/index.php?topic=6029.0
6  Linux Stuff / General Linux questions / Re: Big problems trying to update my original Sheevaplug. on: January 12, 2012, 12:02:18 PM
3.1.8 brought things back to life!

Just as a sanity check, flashed 3.2 again from a fresh download, and it was borked again.  Flashed 3.1.8 and it was fine again...

Something REALLY fishy going on, as like I said before I decided to tinker, I did have 3.2 running on this same plug. (the only different I can think could be partition layout or the fact I was using an old Marvell uboot rather than the new uboot).

Either way, going to stay on 3.1.8 for the moment until someone smarter than me can work out what's wrong...
7  Linux Stuff / General Linux questions / Re: Big problems trying to update my original Sheevaplug. on: January 12, 2012, 09:45:58 AM
I'll give it  ago in the next couple of hours.

What's interesting, I usually keep ontop of kernels, and the plug WAS running 3.2 totally fine until I started tinkering.  So if it's not happy now, it's something specific in what I have done, as it's CAPABLE of running 3.2.
8  Linux Stuff / General Linux questions / Big problems trying to update my original Sheevaplug. on: January 12, 2012, 05:32:07 AM
I had some problems with Debian, so I decided to wipe and start again, and whilst at it, load the new DENX u-boot.  I am installing to internal NAND for performance reasons.

After a whole evening wasted because ESIA was copying zero byte instimg and initrd...   Sorted that by copying the files manually, and I can get the provided Debian ESIA image loaded and it booting.

However, there is something badly wrong with it, as CXBikers kernel update scripts fail to work for numerous reasons.

I then used my Debian rootfs again using ESIA, and it loaded the old kernel that ships with it, but with the updated rootfs (after changing the MD5 checksum in the manifest).

CXBikers kernel then flashes correctly, however it does not boot, it hangs on "Uncompressing Linux... done, booting the kernel.".

Can someone take a look here at my uboot enviroment and see if it looks sensible?

Quote
Marvell>> reset
resetting ...


U-Boot 2011.12 (Jan 08 2012 - 21:53:47)
Marvell-Sheevaplug - eSATA - SD/MMC

SoC:   Kirkwood 88F6281_A0
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.2.0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2911752 Bytes = 2.8 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.







Marvell>> printenv
app_name=Debian_Squeeze
app_summary=Debian Stable (Squeeze) ARM5 SheevaPlug Distribution
arcNumber=2097
baudrate=115200
bootargs_console=console=ttyS0,115200
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootdelay=3
ethact=egiga0
ethaddr=00:50:43:01:D1:E5
filesize=32D29A
install_options=backup= url=Debian_Squeeze kernel=uImage rootfs=root.tar.gz modules=modules.tar.gz apptype= access=c2hlZXZhOnBsdWcK
mainlineLinux=yes
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
nand_erasesize=20000
nand_oobsize=40
nand_writesize=800
real_bootcmd=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
rec33=setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand $(install_options); bootm 0x00800000 0x01100000
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; run rec33
recover3=run recover4
recover4=usb start; fatload usb 0 0x00800000 instImg; fatload usb 0 0x01100000 initrd
stderr=serial
stdin=serial
stdout=serial
x_bootargs=console=ttyS0,115200 mtdparts=orion_nand:512k(uboot),4m@1m(kernel),507m@5m(rootfs) rw
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootcmd_kernel=nand read 0x6400000 0x100000 0x400000
x_bootcmd_sata=ide reset;
x_bootcmd_usb=usb start;

Environment size: 1684/131068 bytes




Really keen to get this back online, as it's my mailserver amonst other things, and my ISP will soon start bouncing messages.
9  Linux Stuff / Kernel / Re: 2.6.38.4 new kernel available on: April 22, 2011, 02:16:20 AM
Would be nice if the script would get the latest and greatest if the version is not specified.
10  Linux Stuff / Kernel / Re: 2.6.38.2, 2.6.37.6 and 2.6.32.36 new kernels available on: April 10, 2011, 10:05:46 AM
Would be nice if the script would get the latest and greatest if the version is not specified.
11  Linux Stuff / Kernel / Re: 2.6.38.1 and 2.6.37.5 new kernels available on: March 28, 2011, 11:08:10 AM
Well the plug rebooted and is running again, should I be concerned about any side-effects from this?
12  Linux Stuff / Kernel / Re: 2.6.38.1 and 2.6.37.5 new kernels available on: March 28, 2011, 12:42:52 AM
The the following errors during flashing, what do they mean?:

Code:
Extracting modules
Flashing kernel to NAND
flash_eraseall has been replaced by `flash_erase <mtddev> 0 0`; please use it
Erasing 128 Kibyte @ 0 --  0 % complete libmtd: error!: unaligned address 2, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 20000 --  3 % complete libmtd: error!: unaligned address 131074, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 40000 --  6 % complete libmtd: error!: unaligned address 262146, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 60000 --  9 % complete libmtd: error!: unaligned address 393218, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 80000 -- 12 % complete libmtd: error!: unaligned address 524290, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ a0000 -- 15 % complete libmtd: error!: unaligned address 655362, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ c0000 -- 18 % complete libmtd: error!: unaligned address 786434, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ e0000 -- 21 % complete libmtd: error!: unaligned address 917506, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 100000 -- 25 % complete libmtd: error!: unaligned address 1048578, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 120000 -- 28 % complete libmtd: error!: unaligned address 1179650, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 140000 -- 31 % complete libmtd: error!: unaligned address 1310722, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 160000 -- 34 % complete libmtd: error!: unaligned address 1441794, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 180000 -- 37 % complete libmtd: error!: unaligned address 1572866, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 1a0000 -- 40 % complete libmtd: error!: unaligned address 1703938, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 1c0000 -- 43 % complete libmtd: error!: unaligned address 1835010, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 1e0000 -- 46 % complete libmtd: error!: unaligned address 1966082, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 200000 -- 50 % complete libmtd: error!: unaligned address 2097154, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 220000 -- 53 % complete libmtd: error!: unaligned address 2228226, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 240000 -- 56 % complete libmtd: error!: unaligned address 2359298, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 260000 -- 59 % complete libmtd: error!: unaligned address 2490370, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 280000 -- 62 % complete libmtd: error!: unaligned address 2621442, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 2a0000 -- 65 % complete libmtd: error!: unaligned address 2752514, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 2c0000 -- 68 % complete libmtd: error!: unaligned address 2883586, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 2e0000 -- 71 % complete libmtd: error!: unaligned address 3014658, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 300000 -- 75 % complete libmtd: error!: unaligned address 3145730, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 320000 -- 78 % complete libmtd: error!: unaligned address 3276802, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 340000 -- 81 % complete libmtd: error!: unaligned address 3407874, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 360000 -- 84 % complete libmtd: error!: unaligned address 3538946, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 380000 -- 87 % complete libmtd: error!: unaligned address 3670018, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 3a0000 -- 90 % complete libmtd: error!: unaligned address 3801090, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 3c0000 -- 93 % complete libmtd: error!: unaligned address 3932162, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 3e0000 -- 96 % complete libmtd: error!: unaligned address 4063234, mtd0 page size is 2048
flash_erase: error!: /dev/mtd0: MTD writeoob failure
             error 22 (Invalid argument)
Erasing 128 Kibyte @ 3e0000 -- 100 % complete
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
Writing data to block 6 at offset 0xc0000
Writing data to block 7 at offset 0xe0000
Writing data to block 8 at offset 0x100000
Writing data to block 9 at offset 0x120000
Writing data to block 10 at offset 0x140000
Writing data to block 11 at offset 0x160000
Writing data to block 12 at offset 0x180000
Writing data to block 13 at offset 0x1a0000
Writing data to block 14 at offset 0x1c0000
Writing data to block 15 at offset 0x1e0000
Writing data to block 16 at offset 0x200000
Writing data to block 17 at offset 0x220000
Writing data to block 18 at offset 0x240000
Writing data to block 19 at offset 0x260000
Writing data to block 20 at offset 0x280000
Writing data to block 21 at offset 0x2a0000
13  Linux Stuff / Linux distributions / Re: The alternative Debian install method. on: February 24, 2011, 02:01:43 AM
  • Script now online
  • Updated Squeeze rootfs (dated yesterday), tested.  Included a PackageList.txt
  • Uploading Wheezy rootfs (dated today), untested.  Included a PackageList.txt

Enjoy.   If anyone is brave enough to try out the wheezy rootfs, please post here if it's working for you.  I have uber-stable Squeeze setup and I don't want to disturb that right now, but as squeeze packages become outdated I will switch to wheezy at some point.

If you want to see the package differences between Squeeze and Wheezy, I have attached a HTML report with the differences.
14  Linux Stuff / Linux distributions / Re: The alternative Debian install method. on: February 23, 2011, 01:52:50 AM
Just updating my script, retired Lenny, promoted Squeeze to stable, and introduced Wheezy...

Script is online, testing the prebuilt packages now, will upload them when done.
15  General Category / General Discussion / Re: Dropbox for LinuxARM. on: February 20, 2011, 10:55:15 AM
Bump..

https://www.dropbox.com/votebox/358/linux-arm-support

Don't forget, you can use all your points again after 30 days!
Pages: [1] 2 3 ... 16