Pogoplug - rc.local is empty?

I just realised that the rc.local file is empty on my new weeezy installation - while before my re-installation, there was code concerning the LED in it.

Can somebody enlighten me what might have happened? The LEDs were fine before, but are only orange after the re-installation and reset of uBoot.

Thanks,

Rainer

rkrug,

> I just realised that the rc.local file is empty on
> my new weeezy installation - while before my
> re-installation, there was code concerning the LED
> in it.

How did you perform this wheezy installation?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I re-installed the uBoot environment (resetted the variables) as I must have messed them up earlier (I have the rescue system installed if important - but some time ago) and the followed your tutorial for Debian Wheezy (I have now debian Wheezy 7.8 installed), and my /etc/rc.local looks as follow:

!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.

exit 0

The boot messages via the netconsole are:

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1614840 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
6894410 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   kernel 3.2.0-4-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1614776 Bytes = 1.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   ramdisk 3.2.0-4-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6894346 Bytes = 6.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Edited 2 time(s). Last edit at 03/23/2015 02:51AM by rkrug.

rkrug,

> I re-installed the uBoot environment (resetted the
> variables) as I must have messed them up earlier
> (I have the rescue system installed if important -
> but some time ago) and the followed your
> for Debian Wheezy

The linked tutorial is Jeff's tutorial, not mine!

When you've successfully installed Debian wheezy using Jeff's script, you have the mainline Debian installation. The LED is not controlled out of the box for mainline, you will need to add to /etc/rc.local to turn on the green LED, and add to /etc/init.d/halt to turn off the green LED.

The rootfs that I've provided can be found here: http://forum.doozan.com/read.php?2,12096. Although you're fine running the mainline 3.2 kernel, you could use my rootfs as a base and get the LED control correctly in that by default. If you'd rather run the mainline version, then download this rootfs anyway, to copy/paste the LED controls to yours rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/23/2015 03:43AM by bodhi.

Sorry - my error.

OK - now I understand it.
So, before indulging into this adventure, I would like to know what the advantages are for running your kernel as it really seems to be the easiest to just extract the rc.local and halt from your rootfs and add the LED code from your init.d/halt to the installed version and copy the rc.local?

Rainer,

http://forum.doozan.com/read.php?2,12096

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)