Re: Debian 11 on Sheevaplug?

[Gilles]

On 09/06/2022 15:48, Martin Michlmayr wrote:

* Gilles  [2022-06-09 15:14]:

U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
=> Does Uboot support ext4, or just ext2? Or is the 2011.12 release too old,
and I should either upgrade or go back to ext2 instead?

It might be worth upgrading u-boot just in case.  These instructions
are still correct:
https://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/

(It's not the latest version of u-boot, but it is one that worked for
a long of people.  Rick Thomas agreed to test the latest and report
back.  I will update my web site accordingly.)

I'm not sure about ext4, but we generally recommend a separate /boot
partition with ext2 and that's IIRC what the guided partitioner
creates.

I let the installer reformat and repartition the pendrive, with /boot as 
ext2 and / as ext4, and D11 installed successuflly.


Lessons learned:

1. If the pendrive has an MBR, convert it to GPT

2. On a computer, perform a full test to check for backblocks

3. Uboot might not support ext4, so either upgrade or use ext2 for /boot

Thanks all!

Re: Debian 11 on Sheevaplug?

[Gilles]

Forgot to write that I tried this line manually:

Marvell>> setenv bootcmd_usb 'usb start; ext4load usb 0:1 0x0080 
/uImage; ext4load usb 0:1 0x0110 /uInitrd'



Marvell>> print
baudrate=115200
bootargs=console=ttyS0,115200
bootargs_console=console=ttyS0,115200
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 
0x0080 0x0110
bootcmd_usb=usb start; ext4load usb 0:1 0x0080 /uImage; ext4load usb 
0:1 0x0110 /uInitrd

bootdelay=3
ethact=egiga0
ethaddr=02:50:43:e7:5c:e1
ipaddr=192.168.0.10
serverip=192.168.0.12
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 0x640 0x10 0x40
x_bootcmd_sata=ide reset;
x_bootcmd_usb=usb start;
Environment size: 706/131068 bytes

Marvell>> run bootcmd

(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
   scanning bus for storage devices... 1 Storage Device(s) found
Unknown command 'ext4load' - try 'help'
Unknown command 'ext4load' - try 'help'
## Booting kernel from Legacy Image at 0080 ...
   Image Name:   kernel 4.9.0-18-marvell
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2080634 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Marvell>>

On 09/06/2022 15:14, Gilles wrote:
I used another USB stick, with the root+boot formated in ext4, the 
install completed, but… Uboot fails loading:


=
U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
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
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
   scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/uImage" from usb device 0:1 (usbda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:1 **
Loading file "/uInitrd" from usb device 0:1 (usbda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:1 **
## Booting kernel from Legacy Image at 0080 ...
   Image Name:   kernel 4.9.0-18-marvell
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2080634 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Marvell>>
=

That was with the original settings:
setenv bootargs_console console=ttyS0,115200
setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x0080 /uImage; 
ext2load usb 0:1 0x0110 /uInitrd'
setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_usb; 
bootm 0x0080 0x0110'


=> Does Uboot support ext4, or just ext2? Or is the 2011.12 release 
too old, and I should either upgrade or go back to ext2 instead?


On 08/06/2022 15:36, Philip Hands wrote:

Gilles  writes:


On 08/06/2022 00:54, Rick Thomas wrote:

On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote:
It ends with a single error : "partman: mkswap: can't open 
'/dev/sda5':

No such file or directory":

https://pastebin.com/raw/h0beZWnP
It looks like /dev/sd5 doesn't actually exist.  This is probably 
because the USB stick has an MBR partition table which by default 
only provides partitions 1-4.  You may need to pre-partition it 
with a GUID partition table.


Rick

Good call. After using Windows' diskpart*, I removed the MBR and
converted to GPT. The installer went one step further… and failed:

https://postimg.cc/ns5XMQL7

Here's the log:

https://pastebin.com/raw/htYCmhS3

The ``bad block bitmap checksum'' relating to /dev/sda2, followed by
``Remounting filesystem read-only'' seems to be the source of your
problem.

After that point nothing's going to work because your new root
filesystem (/target/) is faulty, and is now read-only, so there's no way
to create the /target/boot directory, so the mount of the boot partition
fails.

My guess would be an underlying hardware fault on whatever /dev/sda2 is.

I don't suppose there's any chance it's a fake USB stick - see:

   http://oss.digirati.com.br/f3/  (packaged for Debian as ``f3'')

Cheers, Phil.

Re: Debian 11 on Sheevaplug?

[Gilles]

I used another USB stick, with the root+boot formated in ext4, the 
install completed, but… Uboot fails loading:


=
U-Boot 2011.12 (Mar 11 2012 - 18:59:46)
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
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
   scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/uImage" from usb device 0:1 (usbda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:1 **
Loading file "/uInitrd" from usb device 0:1 (usbda1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - usb 0:1 **
## Booting kernel from Legacy Image at 0080 ...
   Image Name:   kernel 4.9.0-18-marvell
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2080634 Bytes = 2 MiB
   Load Address: 8000
   Entry Point:  8000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Marvell>>
=

That was with the original settings:
setenv bootargs_console console=ttyS0,115200
setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x0080 /uImage; 
ext2load usb 0:1 0x0110 /uInitrd'
setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_usb; 
bootm 0x0080 0x0110'


=> Does Uboot support ext4, or just ext2? Or is the 2011.12 release too 
old, and I should either upgrade or go back to ext2 instead?


On 08/06/2022 15:36, Philip Hands wrote:

Gilles  writes:


On 08/06/2022 00:54, Rick Thomas wrote:

On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote:

It ends with a single error : "partman: mkswap: can't open '/dev/sda5':
No such file or directory":

https://pastebin.com/raw/h0beZWnP

It looks like /dev/sd5 doesn't actually exist.  This is probably because the 
USB stick has an MBR partition table which by default only provides partitions 
1-4.  You may need to pre-partition it with a GUID partition table.

Rick

Good call. After using Windows' diskpart*, I removed the MBR and
converted to GPT. The installer went one step further… and failed:

https://postimg.cc/ns5XMQL7

Here's the log:

https://pastebin.com/raw/htYCmhS3

The ``bad block bitmap checksum'' relating to /dev/sda2, followed by
``Remounting filesystem read-only'' seems to be the source of your
problem.

After that point nothing's going to work because your new root
filesystem (/target/) is faulty, and is now read-only, so there's no way
to create the /target/boot directory, so the mount of the boot partition
fails.

My guess would be an underlying hardware fault on whatever /dev/sda2 is.

I don't suppose there's any chance it's a fake USB stick - see:

   http://oss.digirati.com.br/f3/  (packaged for Debian as ``f3'')

Cheers, Phil.

Re: Debian 11 on Sheevaplug?

[Gilles]

On 08/06/2022 00:54, Rick Thomas wrote:

On Tue, Jun 7, 2022, at 6:32 AM, Gilles wrote:

It ends with a single error : "partman: mkswap: can't open '/dev/sda5':
No such file or directory":

https://pastebin.com/raw/h0beZWnP

It looks like /dev/sd5 doesn't actually exist.  This is probably because the 
USB stick has an MBR partition table which by default only provides partitions 
1-4.  You may need to pre-partition it with a GUID partition table.

Rick


Good call. After using Windows' diskpart*, I removed the MBR and 
converted to GPT. The installer went one step further… and failed:


https://postimg.cc/ns5XMQL7

Here's the log:

https://pastebin.com/raw/htYCmhS3

* https://www.diskpart.com/articles/remove-mbr-partition-3889i.html

Re: Debian 11 on Sheevaplug?

[Gilles]

On 07/06/2022 05:57, Martin Michlmayr wrote:

* Gilles  [2022-06-06 18:02]:

Using a fresh 64GB USB keydrive, I sucessfully launched the D11 installer
with default options… which fails creating the swap partition:

https://gofile.io/d/MO7pb1

Can you go back to the main menu when this happens and open a shell
(it's at the bottom of the list) and then look at /var/log/syslog to
see what the exact error is.



It ends with a single error : "partman: mkswap: can't open '/dev/sda5': 
No such file or directory":


https://pastebin.com/raw/h0beZWnP

I then ran the D11 installer on another, 4GB USB keydrive. The installer 
worked, but the keydrive fails booting:


sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK cmd_age=0s

sd 0:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 77 2d 20 00 00 08 00
blk_update_request: I/O error, dev sda, sector 7810336 op 0x0:(READ) 
flags 0x80700 phys_seg 1 prio class 0


https://pastebin.com/raw/9HnhZDkT

Next, to check if the original problematic 64GB keydrive had a hardware 
problem, I used Rufus on Windows to burn Ubuntu on it, and then used it 
boot a laptop: Success.

Debian 11 on Sheevaplug?

[Gilles]

Hello,

A search in the archives returned no hits.

Martin Michlmayr's page* shows how to install Debian 10 on a USB 
keydrive to run on a Sheevaplug.


Does it mean Debian 11 still isn't available for that device?

Thank you.

* https://www.cyrius.com/debian/kirkwood/sheevaplug/install/

Re: Pi2 does not boot with debian-10.3.0-armhf-netinst.iso on SDCard

[Gilles Risch]

On 4/26/20 12:29, Reco wrote:

Hi.

On Fri, Apr 24, 2020 at 10:21:04AM -0500, Gunnar Wolf wrote:

There is a very minor issue with the 0/1 image (which I intend to fix now).

There are two, actually:

1) /etc/network/interfaces.d/eth0 has a hook to load netfilter rules,
but the appropriate files are missing:

 pre-up iptables-restore < /etc/iptables/rules.v4
 pre-up ip6tables-restore < /etc/iptables/rules.v6

2) An attempt to launch agetty on ttyS1 (which should be uart console
according to /proc/cmdline) fails with:

agetty[655]: /dev/ttyS1: not a tty

Reco





Autopedestres__Roedgen(1).gpx
Description: application/gpx

Re: Debain on a Buffalo TeraStation Live (HS-DHTGL/R5)

[Gilles Risch]

On 26/03/2020 18:25, Arnd Bergmann wrote:
>> On Thu, Mar 26, 2020 at 1:15 PM Gilles Risch  wrote:
>>
>> Hello,
>>
>> During these days of isolation I reanimated my old TeraStation Live
>> (HS-DHTGL/R5), equipped it with some new disks and installed the latest
>> official firmware (2.14). This firmware is based on a quiet old Linux
>> kernel:
>>   #uname -a
>>   Linux TS-LIVE 2.6.16.16-arm1 #9 Fri Aug 31 13:42:57 JST 2007 armv5tejl
>> unknown
>>
>> So I decided to look for something newer. Is it possible to install and
>> run a recent version of Debian on this Marvell Orion based NAS?
> 
> There is still minimal kernel support for this platform in the old board
> files (not in the .dts format), and the armel kernel enables support, but
> as far as I can tell, it only has 128MB of RAM, and the official minimum
> for a Debian installation is now 256MB, so this may be a rough ride.
> 
> Using OpenWRT instead of Debian would better fit into the RAM, but
> they have removed support for all Marvell Orion5x based platforms
> a few months ago, making that also a bit hard, though depending on
> how motivated you are, you could add back OpenWRT support by
> creating a dts file for their "Kirkwood" port.
> 
>Arnd
> 


Thanks,

I'll have a look at OpenWRT.

Regards,
Gilles



signature.asc
Description: OpenPGP digital signature

Debain on a Buffalo TeraStation Live (HS-DHTGL/R5)

[Gilles Risch]

Hello,

During these days of isolation I reanimated my old TeraStation Live
(HS-DHTGL/R5), equipped it with some new disks and installed the latest
official firmware (2.14). This firmware is based on a quiet old Linux
kernel:
  #uname -a
  Linux TS-LIVE 2.6.16.16-arm1 #9 Fri Aug 31 13:42:57 JST 2007 armv5tejl
unknown

So I decided to look for something newer. Is it possible to install and
run a recent version of Debian on this Marvell Orion based NAS?

Kind regards,
Gilles



signature.asc
Description: OpenPGP digital signature

Re: Busbox missing fdisk and fsck: How to add?

[Gilles]

On 23/05/2018 11:57, Paul Wise wrote:

On Wed, May 23, 2018 at 4:55 PM, Gilles wrote:


It looks like the easiest solution to the problem would be cross-compiling
fsck on a i386 Linux host, and copying the binary onto the the appliance.

It is getting better but usually compiling natively is much easier.


I only have shallow experience with cross-compiling, though: Is this
newbie-doable or am I in for days of head-scratching ?

If the source package is cross-compilable, then it isn't much
different from compiling natively.

https://wiki.debian.org/CrossCompiling

IIRC Helmut (one of the few people working on it) says only about 10%
of Debian is cross-compilable though. If anyone wants to help improve
that, please introduce yourself on the debian-cross mailing list.

https://lists.debian.org/debian-cross/

Thanks for the infos. I'll try this if I need to cross-compile an app 
one day.

Re: Busbox missing fdisk and fsck: How to add?

[Gilles]

On 23/05/2018 11:09, Mark Morgan Lloyd wrote:
Please excuse a comment from a lurker, but I'd suggest that it would 
be worth having at least  fdisk -l  capability enabled by default 
since one of the first things one wants to do when in any sort of 
development or recovery situation is to work out what media is 
attached and whether it's partitioned or a single fiefsystem.


I agree. It's too bad the image I found had Busybox compiled without 
fdisk and fsck.

Re: Busbox missing fdisk and fsck: How to add?

[Gilles]

Edit: Elsewhere, someone mentioned a much easier solution : Just unplug 
the USB keydrive from the ARM appliance, and perform the fsck onto a PC 
running Linux.


Why didn't I think of this (face-palm) ?

Thank you.

===
Thanks very much for the infos.

It looks like the easiest solution to the problem would be 
cross-compiling fsck on a i386 Linux host, and copying the binary onto 
the the appliance.


I only have shallow experience with cross-compiling, though: Is this 
newbie-doable or am I in for days of head-scratching ?


On 23/05/2018 04:01, Paul Wise wrote:

On Tue, May 22, 2018 at 8:42 PM, Gilles wrote:


On an ARM appliance, as a way to run fsck on a USB keydrive that holds /boot
and /, I was thinking of running a small Linux image from RAM after
downloading it through TFTP.

Another option would be to use debirf to build an initramfs-based live
system that looks like your normal system (minus logs/data/config),
runs entirely from RAM and contains fsck and any other tools needed
for rescuing the system. I'm not sure if it can do cross-arch builds
but failing that you could build it on the ARM system you have.

http://cmrg.fifthhorseman.net/wiki/debirf


Problem is, the Busybox it contains is missing fdisk and fsck:

It should be feasible to download the source package, tweak the build
config, rebuild the binary packages, extract the relevant binaries and
include them in your small Linux image.

apt build-dep busybox
apt source busybox
cd busybox-*/
$EDITOR 
dpkg-buildpackage
cd ..
dpkg-deb -x busybox-static*.deb busybox-static
cp busybox-static/bin/busybox /srv/tftp/


Is there a way to download a compatible fsck binary from somewhere?

You would have to either build it or get someone else to do that for you.

You could use the one from the normal fsck packages instead of busybox.

I don't know how big the busybox fdisk/fsck support is, but it might
be worth reporting a bug on busybox asking for them to be enabled.
Alternatively, a bug report asking for a busybox-static-full package
containing support for every busybox applet might be a good idea.

Re: Busbox missing fdisk and fsck: How to add?

[Gilles]

Thanks very much for the infos.

It looks like the easiest solution to the problem would be 
cross-compiling fsck on a i386 Linux host, and copying the binary onto 
the the appliance.


I only have shallow experience with cross-compiling, though: Is this 
newbie-doable or am I in for days of head-scratching ?


On 23/05/2018 04:01, Paul Wise wrote:

On Tue, May 22, 2018 at 8:42 PM, Gilles wrote:


On an ARM appliance, as a way to run fsck on a USB keydrive that holds /boot
and /, I was thinking of running a small Linux image from RAM after
downloading it through TFTP.

Another option would be to use debirf to build an initramfs-based live
system that looks like your normal system (minus logs/data/config),
runs entirely from RAM and contains fsck and any other tools needed
for rescuing the system. I'm not sure if it can do cross-arch builds
but failing that you could build it on the ARM system you have.

http://cmrg.fifthhorseman.net/wiki/debirf


Problem is, the Busybox it contains is missing fdisk and fsck:

It should be feasible to download the source package, tweak the build
config, rebuild the binary packages, extract the relevant binaries and
include them in your small Linux image.

apt build-dep busybox
apt source busybox
cd busybox-*/
$EDITOR 
dpkg-buildpackage
cd ..
dpkg-deb -x busybox-static*.deb busybox-static
cp busybox-static/bin/busybox /srv/tftp/


Is there a way to download a compatible fsck binary from somewhere?

You would have to either build it or get someone else to do that for you.

You could use the one from the normal fsck packages instead of busybox.

I don't know how big the busybox fdisk/fsck support is, but it might
be worth reporting a bug on busybox asking for them to be enabled.
Alternatively, a bug report asking for a busybox-static-full package
containing support for every busybox applet might be a good idea.

Busbox missing fdisk and fsck: How to add?

[Gilles]

Hello,

On an ARM appliance, as a way to run fsck on a USB keydrive that holds 
/boot and /, I was thinking of running a small Linux image from RAM 
after downloading it through TFTP.


Problem is, the Busybox it contains is missing fdisk and fsck:


BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # help
Built-in commands:
--
    . : [ bg break cd chdir command continue echo eval exec exit
    export false fg getopts hash help history jobs kill let local
    printf pwd read readonly return set shift test times trap true
    type ulimit umask unset wait

~ # fdisk -l
/bin/sh: fdisk: not found

~ # fsck /dev/sda1
/bin/sh: fsck: not found


It does contain wget, however: Is there a way to download a compatible 
fsck binary from somewhere?


Thank you.

Re: Latest Debian for Sheevaplug?

[Gilles]

On Thu, 26 Mar 2015 15:20:03 +0100, Gilles 
wrote:
>Next, tried connecting with Debian and minicom, and then CuteCom, same
>issue: The Sheevaplug says nothing when rebooting the device :-/

For some reason, rebooting the device bricked it.

Back in business after following the documents below to unbrick it,
and install the latest Debian to a USB keydrive:

http://hanixdiy.blogspot.fr/2013/12/how-to-unbrick-sheevaplug.html
http://www.cyrius.com/debian/kirkwood/sheevaplug/install/

Between faulty PSUs and bricking, I'll investigate alternatives to the
SheevaPlug before recommending it to others, though.

Thank you.


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8ii8hatur1v8drtmnkk9844iggg24ue...@4ax.com

Re: Latest Debian for Sheevaplug?

[Gilles]

On Wed, 25 Mar 2015 18:00:03 +0100, Gilles 
wrote:
>I'm no expert and would like to upgrade a Sheevaplug to the latest
>stable release of Debian.

I rebooted with a cable connecting my Windows host to the mini-USB
port, but get nothing from the Sheevaplug, although the serial
connection worked fine before rebooting.

Next, tried connecting with Debian and minicom, and then CuteCom, same
issue: The Sheevaplug says nothing when rebooting the device :-/


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/e948ha9n89frinmiltsmspkl58omimc...@4ax.com

Re: Latest Debian for Sheevaplug?

[Gilles]

On Thu, 26 Mar 2015 13:30:01 +0100, Rick Thomas 
wrote:
>I’ve heard (but can’t remember where, sadly) that this is *not* a sign of the 
>mmcblk device wearing out.  It’s actually (according to my, possibly faulty, 
>recollection) indicative of a difference in understanding between uboot and 
>Linux as to what the partition table should look like for an mmcblk device.  
>Whatever is doing the read is referring to an address beyond the end of the 
>logical device because it thinks the logical device is bigger than it actually 
>is.
>
>In any case, I’ve been getting it on reboots for years and not had any 
>difficulty.  It only shows up on booting, not during actual run-time.

Thanks for the tip.

But I'm also getting errors when trying to upgrade the kernel after
running "apt-get update":


# 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.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? Y

Setting up linux-image-3.2.0-4-kirkwood (3.2.65-1+deb7u2) ...
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools
3.2.0-4-kirkwood /boot/vmlinuz-3.2.0-4-kirkwood
update-initramfs: Generating /boot/initrd.img-3.2.0-4-kirkwood
cp: reading `/sbin/udevd': Input/output error
cp: failed to extend `/var/tmp/mkinitramfs_5dxt8L//sbin/udevd':
Input/output error
E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
update-initramfs: failed for /boot/initrd.img-3.2.0-4-kirkwood with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
code 1
Failed to process /etc/kernel/postinst.d at
/var/lib/dpkg/info/linux-image-3.2.0-4-kirkwood.postinst line 696.
dpkg: error processing linux-image-3.2.0-4-kirkwood (--configure):
 subprocess installed post-installation script returned error exit
status 1
Errors were encountered while processing:
 linux-image-3.2.0-4-kirkwood
E: Sub-process /usr/bin/dpkg returned an error code (1)


Should I reboot, try again, reboot, and expect Debian to load the
latest and greatest kernel?


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/v2v7hatffrbu2snddv8vsftqhse465p...@4ax.com

Re: Latest Debian for Sheevaplug?

[Gilles]

Thanks for the infos.

At 18:09 25/03/2015, Björn Wetterbom wrote:


You should start at

http://cyrius.com/debian/kirkwood/sheevaplug/

I think you'll find everything you need there.

(Skickat från min telefon == Sent from my phone)



--
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150326110552.cbc37...@bendel.debian.org

Re: Latest Debian for Sheevaplug?

[Gilles]

On Wed, 25 Mar 2015 21:00:03 +0100, "Jim MacKenzie" 
wrote:
>If your SheevaPlug is already running Debian and you simply want to upgrade
>it, you can upgrade to Debian 7 in-place.  This requires a firmware upgrade
>to the SheevaPlug (in some cases) as the Debian 7 kernel isn't compatible
>with older versions of the SheevaPlug's boot loader.  I just upgraded my two
>SheevaPlugs a few weeks ago.

I've been running Debian on that device for about a year, and would
like to upgrade to the latest stable kernel, and also either move the
whole thing from the SD card (where I think it's living) to the NAND,
or replace the current SD card with a new one, since dmesg isn't
happy:

=
# dmesg | tail
[42113305.934129] mmcblk0: error -110 transferring data, sector
1230482, nr 6, cmd response 0x900, card status 0x0
[42113305.944295] end_request: I/O error, dev mmcblk0, sector 1230482
[42113306.123221] mmcblk0: error -110 transferring data, sector
1230480, nr 8, cmd response 0x900, card status
0xb00
[42113306.133560] mmcblk0: retrying using single block read
[42113306.306724] mmcblk0: error -110 transferring data, sector
1230480, nr 8, cmd response 0x900, card status 0x0
[42113306.316885] end_request: I/O error, dev mmcblk0, sector 1230480
[42113306.490929] mmcblk0: error -110 transferring data, sector
1230481, nr 7, cmd response 0x900, card status 0x0
[42113306.501094] end_request: I/O error, dev mmcblk0, sector 1230481
[42113306.676773] mmcblk0: error -110 transferring data, sector
1230483, nr 5, cmd response 0x900, card status 0x0
[42113306.686937] end_request: I/O error, dev mmcblk0, sector 1230483
=

How can I…
1. Check what the NAND contains? I assume Uboot lives in the first
block, and the other two are empty:

=
# cat /proc/mtd
dev:size   erasesize  name
mtd0: 0010 0002 "u-boot"
mtd1: 0040 0002 "uImage"
mtd2: 1fb0 0002 "root"
=
# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
(rw,relatime,size=10240k,nr_inodes=63463,mode=755)
devpts on /dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs
(rw,nosuid,noexec,relatime,size=51516k,mode=755)
/dev/disk/by-uuid/b1767040-9366-43c0-9684-3a8ff83f6547 on / type ext4
(rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs
(rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs
(rw,nosuid,nodev,noexec,relatime,size=146840k)
/dev/mmcblk0p1 on /boot type ext2 (rw,relatime,errors=continue)
=

2. Upgrade to the latest Debian, and replace the SD card?

I was thinking of backing up user data to an other host, shutting it
down, replacing the SD card, download a workable image through TFTP,
perform a fresh install, and restore user files.

>As for /tmp etc., you will extend the life of the SD card if you do that but
>I haven't had great problems with SD card life as long as you buy
>high-quality ones (cheap ones can be a problem though).  Use the "noatime"
>option in /etc/fstab to disable file access date recording; that will reduce
>writing to the disk by avoiding writing to every file when it's read.

I'll check it out. Currently, /etc/fstab says this:

=
UUID=b1767040-9366-43c0-9684-3a8ff83f6547 /   ext4
barrier=0,errors=remount-ro 0   1
# /boot was on /dev/mmcblk0p1 during installation
UUID=45b3b845-431e-4278-b97d-6d61328171fb /boot   ext2
defaults0   2
# swap was on /dev/mmcblk0p5 during installation
UUID=36b91ac2-8b5f-4ec9-ac4b-4127407d8477 noneswapsw 0

0
=

Thank you.


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/dta6ha52kv7c4p03t7qkstiv8jrnuu9...@4ax.com

Latest Debian for Sheevaplug?

[Gilles]

Hello

I'm no expert and would like to upgrade a Sheevaplug to the latest
stable release of Debian.

Sheevaplug manufacturer GlobalScale provides two files: 

Sheeva-Debian7-SW.rar
sheevaplug_env.tar.rar
http://globalscaletechnologies.com/download/

Should I go ahead with those files or are there better alternatives?

Also, to minimize use of the NAND flash memory and the SD card, I'd
like to keep /tmp and other temporary files in RAM. Is this OK?

Thank you.


-- 
To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/bgp5ha1mq2tsrub363ee03bvh92s09u...@4ax.com

Re: cmake on arm64

[Gilles Filippini]

Hi Peter,

peter green a écrit , Le 02/08/2014 05:14:
> peter green wrote:
>> The latest upload of cmake for arm64 failed to build (and stuff is
>> piling up behind it).
> It was given back and succeeded but then someone uploaded a new NMU and
> that failed with a different testsuite failure.
> 
> Any thoughts on where we go from here?
> 
> Adding cmake maintainers and the uploaded of the NMU to cc

If you think my NMU has broken something please give more context so I
understand what's going on. To my knowledge cmake-2.8.12.1-1.6 builds
successfully for all archs:


Thansk,

_g.




signature.asc
Description: OpenPGP digital signature