Welcome! Log In Create A New Profile

Advanced

Booting Debian on Pogoplug Pro

Posted by bodhi 
Booting Debian on Pogoplug Pro
December 08, 2011 09:13PM
This procedure has been updated to add more details and incorporate the correction for installing Debian on Pogo plug Pro (OXNAS variation). See ArchLinux ARM site for information about different models in this family:
http://archlinuxarm.org/platforms/armv6/pogoplug-provideov3

Varkey and Shv have created and hosted a Debian rootfs for those who want to skip the manual step installation. Just grab Varkey's or Shv's rootfs, untar it to a USB drive and you're done! See below for Varkey's or Shv's Debian rootfs (If you have installed ALARM recently, the appropriate rootfs to use is Shv's rootfs).

Varkey's rootfs:
http://forum.doozan.com/read.php?3,6336,6371#msg-6371

Update 1: If you have installed ALARM recently (the kernel on NAND is different from the one we use circa 2011) try Shv's squeeze or wheezy roofts:

squeeze: http://forum.doozan.com/read.php?3,6336,10999#msg-10999
wheezy: http://forum.doozan.com/read.php?3,6336,13993#msg-13993

Update 2: To install Emdebian see installation procedure by ingmar-k:

https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian

Update 3: To install 3.x.x Arch kernel see navym uBoot and kernel:

http://archlinuxarm.org/forum/viewtopic.php?f=55&t=6193

Manual Installation on your existing Debian USB drive (same whether it's flash or HDD)

There are 2 parts in the installation: Install ArchLinux ARM (ALARM), and modification of an existing Debian rootfs. In this procedure, 2 USB sticks were used, one for Arch and one for Debian. The Debian thumb drives must be formatted EXT3. The Arch thumb drive is already formatted EXT3 during the Arch installation.

Part I

Follow the instruction to install Arch at ArchLinux ARM site. Install a complete ArchLinux system and make sure it's working first.
http://archlinuxarm.org/platforms/armv6/pogoplug-provideov3


In this procedure, these versions of Arch and Debian were installed:

#uname -a
Linux alarm 2.6.31.6_SMP_820 #99 SMP Sun May 29 03:04:43 EDT 2011 armv6l ARMv6-compatible processor rev 5 (v6l) Oxsemi NAS GNU/Linux

#uname -a
Linux debian 2.6.37.6 #2 PREEMPT Fri May 13 21:06:35 IST 2011 armv5tel GNU/Linux


Part II

Boot up the Popgoplug Pro with the Arch stick. After the system is up, plug the Debian stick in another USB port and mount this stick. In this configuration, the Arch stick is /dev/sda1 and the Debian stick is /dev/sdb1. Mount command shows (the Debian partition was labeled rootfs):

/dev/root on / type ext3 (rw,relatime,errors=continue,data=writeback)
/dev/sdb1 on /media/rootfs type ext3 (rw,nosuid,nodev,noexec,noatime,errors=remount-ro,barrier=1,data=ordered)


Modification to the Debian rootfs:

1. Copy OXNAS modules from Arch to Debian

[root@alarm local]# cd /media/rootfs/lib/modules/
[root@alarm modules]# cp -r /lib/modules/2.6.31.6_SMP_820 .

2. Copy /usr/local from Arch to Debian

[root@alarm modules]# cd /media/rootfs/usr/local/
[root@alarm local]# cp -rv /usr/local/* .
`/usr/local/mac_addr' -> `./mac_addr'
cp: cannot overwrite non-directory `./man' with directory `/usr/local/man'
cp: cannot overwrite directory `./share/man' with non-directory

(this error is OK).

3. Copy gmac firmware

[root@alarm local]# cd /media/rootfs/lib/firmware/
[root@alarm firmware]# mkdir 2.6.31.6_SMP_820
[root@alarm firmware]# cp /lib/modules/gmac_copro_firmware 2.6.31.6_SMP_820/


4. Copy LED support modules

[root@alarm firmware]# cd /media/rootfs/sbin/
[root@alarm sbin]# cp /sbin/proled .
[root@alarm sbin]# cp /sbin/devmem2 .


5. Modify /etc/modules to force load gmac module and others (an extra step will be needed later to force load the gmac module in rc.local)

[root@alarm sbin]# cat /media/rootfs/etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
mii
gmac
oxnas-led


6. Etracting the modules from Zip files

[root@alarm sbin]# cd /media/rootfs/lib/modules/2.6.31.6_SMP_820/kernel/drivers/net/gmac
[root@alarm gmac]# gunzip gmac.ko.gz

[root@alarm gmac]# cd /media/rootfs/lib/modules/2.6.31.6_SMP_820/kernel/drivers/net
[root@alarm net]# gunzip mii.ko.gz

7. Correct MAC address (static IP is used here, as example). Replace xx:xx:xx:xx:xx:xx with your MAC address, and the IP addresses according to your network.

[root@alarm net]# cat /media/rootfs/etc/network/interfaces
auto lo eth0
iface lo inet loopback
#iface eth0 inet dhcp
iface eth0 inet static
address 192.168.0.222
netmask 255.255.255.0
gateway 192.168.0.1
hwaddress ether xx:xx:xx:xx:xx:xx


8. Modify rc.local to force load the gmac module, also turn on the LED

[root@alarm net]# cat /media/rootfs/etc/rc.local

/sbin/depmod -a
/sbin/modprobe gmac
/sbin/modprobe mii
/sbin/modprobe oxnas-led

# turn on LED
/sbin/proled green

exit 0


9. Modify the halt script to turn off LED (Kxxhalt name is specific to your installation)

[root@alarm net]# cat /etc/rc0.d/K08halt

# add this before the halt action
/sbin/proled off
halt -d -f $netdown $poweroff $hddown

10. Shutdown, and cold start with the Debian stick

Done.


======= Below is the old post kept here for posterity:

Today I'm trying to install Debian on Pogoplug Pro. The current approach that was used by a few users on Fedora and Squeezebox just did not seem to work for me.

The approach was described by oddballhero (1st method) in this post:
http://forum.doozan.com/read.php?3,5728,5799#msg-5799

I'm posting the steps I did here. Really appreciate if you guys can help pointing out where the mistake was (or what am I missing)!

ArchLinux ARM was installed on a thumbdrive:
Linux alarm 2.6.31.6_SMP_820 #99 SMP Sun May 29 03:04:43 EDT 2011 armv6l ARMv6-compatible processor rev 5 (v6l) Oxsemi NAS GNU/Linux

The target Dockstar Debian USB thumbdrive:
Linux dockstar1 2.6.32-5-kirkwood #1 Wed Jan 12 15:27:07 UTC 2011 armv5tel GNU/Linux

=======================

Here are the modification to the Debian USB drive. The system cold boots with this Debian USB drive never comes up.

1. Replace /lib/modules on the Debian thumbdrive (which was automounted as /media/hd-sdb1)

[root@alarm ~]# cd /media/hd-sdb1/lib/modules/
[root@alarm modules]# rm -rf 2.6.32-5-kirkwood
[root@alarm modules]# cp -r /lib/modules/2.6.31.6_SMP_820 .
[root@alarm modules]# ls 2.6.31.6_SMP_820
kernel modules.ccwmap modules.devname modules.isapnpmap modules.pcimap modules.symbols
modules.alias modules.dep modules.ieee1394map modules.ofmap modules.seriomap modules.symbols.bin
modules.alias.bin modules.dep.bin modules.inputmap modules.order modules.softdep modules.usbmap

2. Replace /usr/local

[root@alarm modules]# cd /media/hd-sdb1/
[root@alarm usr]# rm -rf local
[root@alarm usr]# cp -r /usr/local .
[root@alarm usr]# ls local
bin cloudengines etc games include lib mac_addr man sbin share src

3. Copy gmac firmware

[root@alarm hd-sdb1]# pwd
/media/hd-sdb1

[root@alarm hd-sdb1]# ls lib/firmware/
[root@alarm hd-sdb1]# cp /lib/modules/gmac_copro_firmware /media/hd-sdb1/lib/firmware/
[root@alarm hd-sdb1]# ls lib/firmware/
gmac_copro_firmware

4. Verified currently loaded modules on the running PogoPro ArchLinux ARM:
[root@alarm ~]# lsmod
Module Size Used by
gmac 40372 0
mii 6328 1 gmac

5. Force load gmac module and others

[root@alarm hd-sdb1]# cat /media/hd-sdb1/etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
mii
gmac
power_button

6. Etracting the network modules from Zip files

[root@alarm gmac]# pwd
/media/hd-sdb1/lib/modules/2.6.31.6_SMP_820/kernel/drivers/net/gmac
[root@alarm gmac]# gunzip gmac.ko.gz

[root@alarm kernel]# pwd
/media/hd-sdb1/lib/modules/2.6.31.6_SMP_820/kernel
[root@alarm kernel]# cd drivers/
[root@alarm drivers]# cd net/
[root@alarm net]# gunzip mii.ko.gz
[root@alarm net]# ls
gmac mii.ko

[root@alarm plat-oxnas]# cd /media/hd-sdb1/lib/modules//2.6.31.6_SMP_820/kernel/arch/arm/plat-oxnas
[root@alarm plat-oxnas]# gunzip power_button.ko.gz
[root@alarm plat-oxnas]# ls
power_button.ko

7. Correct MAC address

[root@alarm hd-sdb1]# cat /media/hd-sdb1/etc/network/interfaces
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
hwaddress ether xx:xx:xx:xx:xx:xx

8. Shutdown, and cold start with the Debian stick

[root@alarm local]# sync
[root@alarm local]# shutdown -h now

============================

-bodhi
===========================
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
bodhi's u-boot GitHub
bodhi's corner



Edited 11 time(s). Last edit at 04/11/2014 03:36PM by bodhi.
Re: Booting Debian on Pogoplug Pro
December 09, 2011 03:21AM
bodhi Wrote:
-------------------------------------------------------
> Today I'm trying to install Debian on Pogoplug
> Pro. The current approach that was used by a few
> users on Fedora and Squeezebox just did not seem
> to work for me.
>
> The approach was described by oddballhero (1st
> method) in this post:
> http://forum.doozan.com/read.php?3,5728,5799#msg-5
> 799
>
> I'm posting the steps I did here. Really
> appreciate if you guys can help pointing out where
> the mistake was (or what am I missing)!
>
> ArchLinux ARM was installed on a thumbdrive:
> Linux alarm 2.6.31.6_SMP_820 #99 SMP Sun May 29
> 03:04:43 EDT 2011 armv6l ARMv6-compatible
> processor rev 5 (v6l) Oxsemi NAS GNU/Linux

So ArchlinuxArm Script usually has the root fs as ext3 in boot params.

>
> The target Dockstar Debian USB thumbdrive:
> Linux dockstar1 2.6.32-5-kirkwood #1 Wed Jan 12
> 15:27:07 UTC 2011 armv5tel GNU/Linux
>

What is the format is the Debian root fs? Hopefully not ext2. A "mount" command would be nice at this point.

> =======================
>
> Here are the modification to the Debian USB drive.
> The system cold boots with this Debian USB drive
> never comes up.
>
> 1. Replace /lib/modules on the Debian thumbdrive
> (which was automounted as /media/hd-sdb1)
>
> # cd /media/hd-sdb1/lib/modules/
> # rm -rf 2.6.32-5-kirkwood

You actually did not need to do this (rm) since the kernel will search for the proper location pointed to by uname -r which is why the ALARM linux install has both the oxnas and mainline modules.

> # cp -r /lib/modules/2.6.31.6_SMP_820 .
> # ls 2.6.31.6_SMP_820
> kernel modules.ccwmap
> modules.devname modules.isapnpmap
> modules.pcimap modules.symbols
> modules.alias modules.dep
> modules.ieee1394map modules.ofmap
> modules.seriomap modules.symbols.bin
> modules.alias.bin modules.dep.bin
> modules.inputmap modules.order
> modules.softdep modules.usbmap
>

This is ok. The modules should be under kernel /lib/modules/2.6.31.6_SMP_820/kernel

> 2. Replace /usr/local
>
> # cd /media/hd-sdb1/ ********** So here you are at the root of the drive.
> # rm -rf local ********** You removed local in the root (not /usr/local)? Did this actually remove anything?
> # cp -r /usr/local . ********** And you copy /usr/local to /local/ ?
> # ls local
> bin cloudengines etc games include lib
> mac_addr man sbin share src

Probably didn't need to the the rm. Just copy in the cloudengines to /usr/local/.

>
> 3. Copy gmac firmware
>
> # pwd
> /media/hd-sdb1
>
> # ls lib/firmware/ ********** So nothing under /lib/firmware on the target
> # cp /lib/modules/gmac_copro_firmware
> /media/hd-sdb1/lib/firmware/ ********** That was copied.
> # ls lib/firmware/
> gmac_copro_firmware
>
> 4. Verified currently loaded modules on the
> running PogoPro ArchLinux ARM:
> # lsmod
> Module Size Used by
> gmac 40372 0
> mii 6328 1 gmac
>

ok

> 5. Force load gmac module and others
>
> # cat /media/hd-sdb1/etc/modules
> # /etc/modules: kernel modules to load at boot
> time.
> #
> # This file contains the names of kernel modules
> that should be loaded
> # at boot time, one per line. Lines beginning with
> "#" are ignored.
> # Parameters can be specified after the module
> name.
> mii
> gmac
> power_button
>
> 6. Etracting the network modules from Zip files
>
> # pwd
> /media/hd-sdb1/lib/modules/2.6.31.6_SMP_820/kernel
> /drivers/net/gmac
> # gunzip gmac.ko.gz
>
> # pwd
> /media/hd-sdb1/lib/modules/2.6.31.6_SMP_820/kernel
>
> # cd drivers/
> # cd net/
> # gunzip mii.ko.gz
> # ls
> gmac mii.ko
>
> # cd
> /media/hd-sdb1/lib/modules//2.6.31.6_SMP_820/kerne
> l/arch/arm/plat-oxnas
> # gunzip power_button.ko.gz
> # ls
> power_button.ko
>
Feel free to unzip everything.

> 7. Correct MAC address
>
> # cat /media/hd-sdb1/etc/network/interfaces
> auto lo eth0
> iface lo inet loopback
> iface eth0 inet dhcp
> hwaddress ether 00:25:31:00:FF:7A
>

Ok dhcp.

> 8. Shutdown, and cold start with the Debian stick
>
> # sync
> # shutdown -h now
>
> ============================

And you pulled out the ArchLinux stick and left the Debian in.


So, Did I follow everything so far?

Append: I had to redo this reply since it did not keep my indents (doh!). Just read through above, I was a little bit messy, haven't slept in over a day.



Edited 1 time(s). Last edit at 12/09/2011 03:33AM by oddballhero.
Re: Booting Debian on Pogoplug Pro
December 09, 2011 04:08AM
@oddballhero,

Thanks for reviewing this! yes, I did make sure to do a tune2fs for the stick, since it was ext2. Sorry forgot to include it here!

[root@alarm ~]# tune2fs -j /dev/sdb1
tune2fs 1.41.14 (22-Dec-2010)
Creating journal inode: done
This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

- verify that it was converted to ext3

[root@alarm ~]# mount
/dev/root on / type ext3 (rw,relatime,errors=continue,data=writeback)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
/sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
/run on /run type tmpfs (rw,nosuid,nodev,relatime,size=10240k,mode=755)
udev on /dev type tmpfs (rw,nosuid,relatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
/dev/sdb1 on /media/hd-sdb1 type ext3 (rw,noatime)

About /usr/local, duh! cut/paste error in my post. I did copy to the right place on sdb1.

[root@alarm modules]# cd /media/hd-sdb1/
[root@alarm hd-sdb1]# ls
bin   dev  home        lib        lost+found  mnt          opt   root  selinux  swapfile1  tmp  var      webmin-setup.out
boot  etc  initrd.img  localdisk  media       nonexistent  proc  sbin  srv      sys        usr  vmlinuz

[root@alarm hd-sdb1]# ls usr
bin  games  include  lib  local  sbin  share  src

[root@alarm hd-sdb1]# cd usr
[root@alarm usr]# pwd
/media/hd-sdb1/usr

[root@alarm usr]# ls local
bin  etc  games  include  lib  man  sbin  share  src

[root@alarm usr]# rm -rf local
[root@alarm usr]# cp -r /usr/local .
[root@alarm usr]# ls local
bin  cloudengines  etc  games  include  lib  mac_addr  man  sbin  share  src



And yes, I shutdown, pulled out the ALARM stick and replace it with the Debian stick in the same slot (next to the Ethernet port).

The only thing left is, like you mentioned, probably could not hurt to unzip all modules in the kernel directory :-)

Appreciate your help! I'll do this again with a fresh stick, see what'll happen.



Edited 1 time(s). Last edit at 12/09/2011 04:17AM by bodhi.
Re: Booting Debian on Pogoplug Pro
December 09, 2011 01:56PM
I created a debian rootfs using the instructions given by Vlad and made the changes mentioned above. Same issue for me ie network is not coming up. But from the dmesg log in the USB drive I can see that it booted almost fine except for the network. Here is the dmesg output

[    0.000000] Linux version 2.6.31.6_SMP_820 (root@ProDev) (gcc version 4.6.0 20110429 (prerelease) (GCC) ) #99 SMP Sun May 29 03:04:43 EDT 2011
[    0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine: Oxsemi NAS
[    0.000000] 1 memory region
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c03f3f80, node_mem_map c041a000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32512 pages, LIFO batch:7
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 rootwait mem=128M poweroutage=yes
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 125524KB available (3636K code, 296K data, 128K init, 0K highmem)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:96
[    0.000000] OX820_RPS_init_irq: interrupts 64 to 96
[    0.010000] Console: colour dummy device 80x30
[    0.010000] console [ttyS0] enabled
[    0.020000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
[    0.260000] Security Framework initialized
[    0.260000] Mount-cache hash table entries: 512
[    0.270000] CPU: Testing write buffer coherency: ok
[    0.270000] Calibrating local timer... 349.99MHz.
[    0.340000] CPU1: Booted secondary processor
[    0.440000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
[    0.670000] Brought up 2 CPUs
[    0.680000] SMP: Total of 2 processors activated (558.69 BogoMIPS).
[    0.690000] NET: Registered protocol family 16
[    0.690000] Number of DMA channels = 4, version = 4
[    0.700000] Reserving a DMA channel for DirectRAID
[    0.700000] Allocating 389 SRAM generic DMA descriptors
[    1.210000] PCIeA version/deviceID 082510b5
[    1.210000] PCIeB version/deviceID 082510b5
[    4.240000] ox820_pci_preinit() PCIEB link up timeout (00001814)
[    4.240000] ox820_pcie_setup_resources() Enabling PCIe Pre-Emphasis
[    4.250000] ox820_pciea_setup_resources() resource c781b2c0
[    4.250000] ox820_pciea_setup_resources()    io:      0x4be00000 - 0x4befffff
[    4.260000] ox820_pciea_setup_resources()    non-pre: 0x48000000 - 0x49ffffff
[    4.270000] ox820_pciea_setup_resources()    pre:     0x4a000000 - 0x4bdfffff
[    4.270000] pci 0000:00:00.0: reg 10 32bit mmio: [0x000000-0x00ffff]
[    4.270000] PCI: bus0: Fast back to back transfers disabled
[    4.280000] PCI: bus1: Fast back to back transfers enabled
[    4.300000] bio: create slab <bio-0> at 0
[    4.310000] SCSI subsystem initialized
[    4.310000] libata version 3.00 loaded.
[    4.310000] usbcore: registered new interface driver usbfs
[    4.320000] usbcore: registered new interface driver hub
[    4.320000] usbcore: registered new device driver usb
[    4.360000] NET: Registered protocol family 2
[    4.360000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    4.370000] Switched to NOHz mode on CPU #0
[    4.370000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    4.370000] Switched to NOHz mode on CPU #1
[    4.380000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    4.390000] TCP: Hash tables configured (established 4096 bind 4096)
[    4.390000] TCP reno registered
[    4.400000] NET: Registered protocol family 1
[    4.400000] Create fragment cache
[    4.410000] fuse init (API version 7.12)
[    4.410000] msgmni has been set to 245
[    4.420000] alg: No test for stdrng (krng)
[    4.430000] io scheduler noop registered
[    4.430000] io scheduler anticipatory registered
[    4.430000] io scheduler deadline registered
[    4.440000] io scheduler cfq registered (default)
[    4.460000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    4.470000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
[    4.490000] brd: module loaded
[    4.490000] loop: module loaded
[    4.500000] ox820sata: OX820 sata core.
[    4.500000] scsi0 : oxnassata
[    4.510000] scsi1 : oxnassata
[    4.510000] ata1: SATA max UDMA/133 irq 50
[    4.510000] ata2: SATA max UDMA/133 irq 50
[    4.520000] ox820sata: reseting SATA core
[    4.880000] ata1: SATA link down (SStatus 0 SControl 300)
[    4.880000] ox820sata: reseting SATA core
[    5.240000] ata2: SATA link down (SStatus 0 SControl 300)
[    5.240000] tun: Universal TUN/TAP device driver, 1.6
[    5.250000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    5.250000] NAND: Page read time 40ms
[    5.260000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    5.270000] Scanning device for bad blocks
[    5.330000] Bad eraseblock 942 at 0x0000075c0000
[    5.350000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[    5.350000] 0x000000000000-0x000000e00000 : "boot"
[    5.360000] 0x000000e00000-0x000008000000 : "rootfs"
[    5.360000] UBI: attaching mtd2 to ubi0
[    5.370000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    5.370000] UBI: logical eraseblock size:    129024 bytes
[    5.380000] UBI: smallest flash I/O unit:    2048
[    5.380000] UBI: sub-page size:              512
[    5.390000] UBI: VID header offset:          512 (aligned 512)
[    5.390000] UBI: data offset:                2048
[    5.810000] UBI: attached mtd2 to ubi0
[    5.810000] UBI: MTD device name:            "rootfs"
[    5.810000] UBI: MTD device size:            114 MiB
[    5.820000] UBI: number of good PEBs:        911
[    5.820000] UBI: number of bad PEBs:         1
[    5.830000] UBI: max. allowed volumes:       128
[    5.830000] UBI: wear-leveling threshold:    4096
[    5.840000] UBI: number of internal volumes: 1
[    5.840000] UBI: number of user volumes:     1
[    5.850000] UBI: available PEBs:             0
[    5.850000] UBI: total number of reserved PEBs: 911
[    5.860000] UBI: number of PEBs reserved for bad PEB handling: 9
[    5.860000] UBI: max/mean erase counter: 2/0
[    5.870000] UBI: image sequence number: 0
[    5.870000] UBI: background thread "ubi_bgt0d" started, PID 297
[    5.870000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    5.870000] oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
[    5.870000] oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
[    5.910000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
[    5.930000] oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
[    5.930000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    5.940000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.940000] usb usb1: Product: OXNAS EHCI Host Controller
[    5.950000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
[    5.960000] usb usb1: SerialNumber: usb
[    5.960000] usb usb1: configuration #1 chosen from 1 choice
[    5.970000] hub 1-0:1.0: USB hub found
[    5.970000] hub 1-0:1.0: 2 ports detected
[    5.980000] Initializing USB Mass Storage driver...
[    5.980000] usbcore: registered new interface driver usb-storage
[    5.990000] USB Mass Storage support registered.
[    5.990000] mice: PS/2 mouse device common for all mice
[    6.000000] TCP cubic registered
[    6.000000] NET: Registered protocol family 10
[    6.010000] NET: Registered protocol family 17
[    6.010000] RPC: Registered udp transport module.
[    6.020000] RPC: Registered tcp transport module.
[    6.020000] Waiting for root device /dev/sda1...
[    6.290000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
[    6.440000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    6.440000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    6.450000] usb 1-1: Product: USB2.0 Hub
[    6.450000] usb 1-1: configuration #1 chosen from 1 choice
[    6.460000] hub 1-1:1.0: USB hub found
[    6.470000] hub 1-1:1.0: 4 ports detected
[    6.750000] usb 1-1.3: new high speed USB device using oxnas-ehci and address 3
[    6.860000] usb 1-1.3: New USB device found, idVendor=1b1c, idProduct=0ad0
[    6.860000] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.870000] usb 1-1.3: Product: Flash Voyager
[    6.870000] usb 1-1.3: Manufacturer: Corsair
[    6.880000] usb 1-1.3: SerialNumber: 000802214E61DC2D726E
[    6.890000] usb 1-1.3: configuration #1 chosen from 1 choice
[    6.890000] scsi2 : SCSI emulation for USB Mass Storage devices
[    6.900000] usb-storage: device found at 3
[    6.900000] usb-storage: waiting for device to settle before scanning
[   19.220000] scsi 2:0:0:0: Direct-Access     Corsair  Flash Voyager    1.00 PQ: 0 ANSI: 2
[   19.230000] usb-storage: device scan complete
[   19.230000] sd 2:0:0:0: [sda] 15859712 512-byte logical blocks: (8.12 GB/7.56 GiB)
[   19.240000] sd 2:0:0:0: [sda] Write Protect is off
[   19.250000] sd 2:0:0:0: [sda] Mode Sense: 03 00 00 00
[   19.250000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[   19.260000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[   19.260000]  sda: sda1 sda2 sda3
[   19.270000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[   19.280000] sd 2:0:0:0: [sda] Attached SCSI removable disk
[   19.340000] kjournald starting.  Commit interval 5 seconds
[   19.340000] EXT3 FS on sda1, internal journal
[   19.340000] EXT3-fs: mounted filesystem with writeback data mode.
[   19.340000] VFS: Mounted root (ext3 filesystem) on device 8:1.
[   19.340000] Freeing init memory: 128K
[   20.300000] PCI: enabling device 0000:00:00.0 (0140 -> 0142)
[   20.310000] 
[   20.310000] 
[   20.310000] === pAd = c8a3a000, size = 519160 ===
[   20.310000] 
[   20.320000] <-- RTMPAllocAdapterBlock, Status=0
[   20.330000] pAd->CSRBaseAddress =0xf5000000, csr_addr=0xf5000000!
[   26.360000] EXT3 FS on sda1, internal journal

I couldn't attach a serial cable as I wasn't able to open the casing. The transparent outer covering is just not moving! :P
Re: Booting Debian on Pogoplug Pro
December 09, 2011 02:22PM
Got network running as well :)

Just had to add the following to /etc/rc.local and the Pogoplug Pro booted fine with network! :-)

/sbin/depmod -a 
/sbin/modprobe gmac



Edited 1 time(s). Last edit at 12/09/2011 02:22PM by varkey.
Re: Booting Debian on Pogoplug Pro
December 09, 2011 02:31PM
varkey Wrote:
-------------------------------------------------------
> I created a debian rootfs using the instructions
> given by Vlad and made the changes mentioned
> above. Same issue for me ie network is not coming
> up. But from the dmesg log in the USB drive I can
> see that it booted almost fine except for the
> network. Here is the dmesg output
>
>
> I couldn't attach a serial cable as I wasn't able
> to open the casing. The transparent outer covering
> is just not moving! :P

You gotta be kidding. The transparent outer covering moves easily, I've done it enough times. I gave the references and nobody read Lerwick (here is a cut and paste):

Make sure to copy /lib/modules and /usr/local over from the PlugApps
FS. The network driver is compiled as a module, and it will not auto
load. Especially if you don't have a serial console set up, before
booting you'll need to pop in a script at
/etc/sysconfig/modules/oxnas-gmac.modules :

#!/bin/sh
exec /sbin/modprobe gmac >/dev/null 2>&1

Make sure it is chmod 755

Also the driver wants firmware for the TCP offload, and seems to have
a bug where it will just lock up the system if it can't find it.
You'll find it at /lib/modules/2.6.31.6_SMP_820/gmac_copro_firmware ,
just move it to /lib/firmware/ and you should have working ethernet.

There's some weirdness with the MAC address, the driver just sets it
to a hardwired default of "00:30:E0:00:00:00" as there does not seem
to be in-kernel infrastructure to read uboot variables. The PlugApps
install script writes the MAC into /usr/local/mac_addr and the network
scripts change it before bringing the interface up. I don't understand
why they don't just read it directly from NVRAM using
/usr/local/cloudengines/bin/blparam . But currently my Pogoplug Pro is
just using the default MAC. Setting the MAC properly should be a
simple matter of scripting...


I didn't have this problem since I used my own kernel with the network built in.
Re: Booting Debian on Pogoplug Pro
December 09, 2011 02:36PM
varkey Wrote:
-------------------------------------------------------
> Got network running as well :)
>
> Just had to add the following to /etc/rc.local and
> the Pogoplug Pro booted fine with network! :-)
>
>
> /sbin/depmod -a
> /sbin/modprobe gmac
>

Ok, sorry, didn't see this last post, was too busy cutting and pasting. Since you got the case open, might as well get the sata drive working. It's a lot faster.
Anyway, congratulations!
Re: Booting Debian on Pogoplug Pro
December 09, 2011 03:08PM
@oddballhero - Thanks for the help. Should have read all the info properly! :)

Anyway, I still didn't manage to remove that transparent cover, its too tight, will try some other day.

Btw do you know whether the internal SATA port support Port Multiplier function? I just need to attach a 4 Bay eSata case to it. OS can be loaded from another USB drive.
Re: Booting Debian on Pogoplug Pro
December 09, 2011 03:30PM
@oddballhero,

Sorry I did not follow the instruction in your reference about the modprobe gmac closely :-) But I thought step 5 would force load the gmac module the same way!

Is it odd that /etc/init.d/module-init-tools did not load the gmac mentioned in this file?

5. Force load gmac module and others

[root@alarm hd-sdb1]# cat /media/hd-sdb1/etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
mii
gmac
power_button

In any case, I put it the force load for gmac in rc.local and Debian comes up OK, yeah!!!

Thanks very much for your help! also thanks varkey for verifying your installation works with the rc.local change.

bodhi
Re: Booting Debian on Pogoplug Pro
December 09, 2011 04:43PM
varkey Wrote:
-------------------------------------------------------
> @oddballhero - Thanks for the help. Should have
> read all the info properly! :)
>
> Anyway, I still didn't manage to remove that
> transparent cover, its too tight, will try some
> other day.
>
> Btw do you know whether the internal SATA port
> support Port Multiplier function? I just need to
> attach a 4 Bay eSata case to it. OS can be loaded
> from another USB drive.

No problem Varkey, you did great! There are ridges after the first rib on both sides. Smooth plastic on smooth plastic usually allows it to slide over with some force. Inside is the internal sata connector (one only) with no port multiplier capability. When you have this connected, it is ALWAYS sda. So sorry but no port multiplier. Still it is faster. It does require a separate power supply. Be careful since I bought one that was poor quality and had to replace it about 10 months later with a better designed one. Since you did bring this up, the SOC on the Pogoplug Mobile (which is a Marvell) does support a port multiplier but does not appear to have a connector soldered in (I don't even know if it has a serial connector). Once it get's to around $40, I might buy one and see if I can put one on.
Re: Booting Debian on Pogoplug Pro
December 09, 2011 05:05PM
bodhi Wrote:
-------------------------------------------------------
> @oddballhero,
>
> Sorry I did not follow the instruction in your
> reference about the modprobe gmac closely :-) But
> I thought step 5 would force load the gmac module
> the same way!
>
> Is it odd that /etc/init.d/module-init-tools did
> not load the gmac mentioned in this file?
>

Probably since it is in /lib/firmware instead of /lib/modules and as Varkey did the depmod....

>
> 5. Force load gmac module and others
>
> # cat /media/hd-sdb1/etc/modules
> # /etc/modules: kernel modules to load at boot
> time.
> #
> # This file contains the names of kernel modules
> that should be loaded
> # at boot time, one per line. Lines beginning with
> "#" are ignored.
> # Parameters can be specified after the module
> name.
> mii
> gmac
> power_button
>

See above. I think I mention depmod on my very first long post.

>
> In any case, I put it the force load for gmac in
> rc.local and Debian comes up OK, yeah!!!
>
> Thanks very much for your help! also thanks varkey
> for verifying your installation works with the
> rc.local change.
>
> bodhi


You and Varkey did great. Kinda like the pioneers here. So go port and multiply and spread the word (couldn't resist that even though no port multiplier function). Like I mentioned to Varkey, the sata port is faster. It is always sda so plugging other drives in usb should not mess up the boot order. PLX oxnas original uboot always defaults to either sata or nand originally. CE just modified this for nand only. It is really neat to place a big swap partition on a hard drive which helps this memory deficient machine and prevents lockups on some applications. As a caveat to you both, for the next few days, monitor the size of the logs until everything looks ok.
Again, congratulations to Bodhi and Varkey!

Addendum:
You may want to create additional modules. On /lib/modules/2.6.31.6_SMP_820 you may want to create a build link to the kernel source (after downloading the source) and source link (see what under the kirkwood dir). Also under /usr/src a link from the source headers to linux-headers-2.6.31.6_SMP_820, basically see whats there under /usr/src for kirkwood and do the same for oxnas. You may want to make backups of your current modules. After making your modules and installing, always perform a "depmod -a". The new kernel may end up in /boot but remember the actual kernel is in nand. A lot of modules don't require the new kernel be loaded but if that happens, you need to load the new kernel like WarheadsSE's script did. If you do build a new kernel, remember that actual pros use pci and B0s don't. Get this wrong and it is serial cable/tftp time. Be careful and do this at your own risk!

Re Addendum:
By the way, the previous Addendum goes for ArchLinuxARM also (in terms of compiling modules and other sources). If WarheadsSE get's kexec running with the new kernel, then everything gets much simpler.



Edited 3 time(s). Last edit at 12/09/2011 06:31PM by oddballhero.
Re: Booting Debian on Pogoplug Pro
December 10, 2011 03:21AM
@varkey,

Does your PogoplugPro LED work properly?

While running Debian, and the ArchLinux stick mounted on sdb1, I've copied the devmem2 and the proled script to Debian /sbin. I believe these are needed for Oxnas LED.

# cp /media/sdb1/sbin/proled /sbin/
# cp /media/sdb1/sbin/devmem2 /sbin/

I setup rc.local and the /etc/rc0.d/K08halt script to turn on/off the LED light.
/sbin/proled green
/sbin/proled off

Did not seem to take. So I execute proled script directly to verify, it did not do anything. The LED light is flashing all the time after the system is running.

Note that the proled script executes correctly while I'm on ArchLinux (turning LED to green, off,...). And it depends on devmem2 only. I'm not sure what devmem2 needs, though. I'm wondering the xce module is the problem. xce module was loaded during boot, but then removed. So while Arch is running, only 2 modules were loaded (gmac and mii).

-bodhi
Re: Booting Debian on Pogoplug Pro
December 10, 2011 03:48AM
@oddballhero - :) Thanks, will keep that in mind. :)

@bodhi - You need to load the oxnas-led module for the LED to work. I just added it to /etc/modules
Re: Booting Debian on Pogoplug Pro
December 10, 2011 04:27AM
oddballhero Wrote:
-------------------------------------------------------
Get this wrong and it is serial cable/tftp time.

LOL. Thanks :-)
Re: Booting Debian on Pogoplug Pro
December 10, 2011 04:32AM
varkey Wrote:
-------------------------------------------------------
> @bodhi - You need to load the oxnas-led module for
> the LED to work. I just added it to /etc/modules

Thanks, but I could not find it! is it inside one of the tar files?

Update: ah, I saw on Arch forum, should be in the latest ALARM rootfs tar file?!



Edited 1 time(s). Last edit at 12/10/2011 04:38AM by bodhi.
Re: Booting Debian on Pogoplug Pro
December 10, 2011 04:59AM
^ I installed ArchLinux only few days back so I guess I got the latest rootfs. It was there /lib/modules directory. I just had to edit /etc/modules in Debian and add oxnas-led to the list.
Re: Booting Debian on Pogoplug Pro
December 10, 2011 04:32PM
Thanks for the info Varkey!

It's in the latest ArchLinux ARM rootfs (after November version):
http://archlinuxarm.org/os/ArchLinuxARM-oxnas-latest.tar.gz

The required modules and binaries location:
/lib/modules/2.6.31.6_SMP_820/kernel/oxnas-led.ko
/sbin/proled
/sbin/devmem2

The LED is working properly now! flashing when it's booting, off when it's shutdown, and solid green while running.
Re: Booting Debian on Pogoplug Pro
December 12, 2011 05:43PM
Thank you for this.

I'm now running Debian on 2 Pogoplug and 1 Pogoplug Pro!

I notice some errors on the Pogoplug Pro.....

(This doesn't happen when running ArchLinux - only when using the Debian USB stick)

Is there some OS process that's accessing the NAND that's causing this???????

I don't get these errors under ArchLinux.


Also - can someone tell me - do I need to load xce during boot or not???


thanks,

PHT



16.490000] Adding 529400k swap on /dev/sda2. Priority:-1 extents:1 across:529400k
[ 16.720000] uncorrectable error :
[ 16.720000] uncorrectable error :
[ 16.730000] end_request: I/O error, dev mtdblock0, sector 2048
[ 16.730000] Buffer I/O error on device mtdblock0, logical block 256
[ 16.760000] uncorrectable error :
[ 16.760000] uncorrectable error :
[ 16.770000] end_request: I/O error, dev mtdblock0, sector 768
[ 16.770000] Buffer I/O error on device mtdblock0, logical block 96
[ 16.780000] uncorrectable error :
[ 16.780000] uncorrectable error :
[ 16.790000] end_request: I/O error, dev mtdblock0, sector 768
[ 16.790000] Buffer I/O error on device mtdblock0, logical block 96
[ 16.800000] uncorrectable error :
[ 16.800000] uncorrectable error :
[ 16.800000] end_request: I/O error, dev mtdblock0, sector 776
[ 16.810000] Buffer I/O error on device mtdblock0, logical block 97
[ 16.820000] uncorrectable error :
[ 16.820000] uncorrectable error :
[ 16.820000] end_request: I/O error, dev mtdblock0, sector 776
[ 16.830000] Buffer I/O error on device mtdblock0, logical block 97
[ 16.840000] uncorrectable error :
[ 16.840000] uncorrectable error :
[ 16.840000] end_request: I/O error, dev mtdblock0, sector 784
[ 16.850000] Buffer I/O error on device mtdblock0, logical block 98
[ 16.860000] uncorrectable error :
[ 16.860000] uncorrectable error :
[ 16.860000] end_request: I/O error, dev mtdblock0, sector 784
[ 16.860000] Buffer I/O error on device mtdblock0, logical block 98
[ 16.870000] uncorrectable error :
[ 16.880000] uncorrectable error :
[ 16.880000] end_request: I/O error, dev mtdblock0, sector 512
[ 16.880000] Buffer I/O error on device mtdblock0, logical block 64
[ 16.920000] uncorrectable error :
[ 16.920000] uncorrectable error :
[ 16.930000] end_request: I/O error, dev mtdblock1, sector 2048
[ 16.930000] Buffer I/O error on device mtdblock1, logical block 256
[ 16.950000] uncorrectable error :
[ 16.950000] uncorrectable error :
[ 16.960000] end_request: I/O error, dev mtdblock1, sector 512
[ 16.960000] Buffer I/O error on device mtdblock1, logical block 64
[ 17.350000] uncorrectable error :
[ 17.350000] uncorrectable error :
[ 17.350000] end_request: I/O error, dev mtdblock0, sector 2048
[ 17.380000] uncorrectable error :
[ 17.380000] uncorrectable error :
[ 17.390000] end_request: I/O error, dev mtdblock0, sector 768
[ 17.390000] uncorrectable error :
[ 17.400000] uncorrectable error :
[ 17.400000] end_request: I/O error, dev mtdblock0, sector 768
[ 17.410000] uncorrectable error :
[ 17.410000] uncorrectable error :
[ 17.410000] end_request: I/O error, dev mtdblock0, sector 776
[ 17.420000] uncorrectable error :
[ 17.420000] uncorrectable error :
[ 17.430000] end_request: I/O error, dev mtdblock0, sector 776
[ 17.430000] uncorrectable error :
[ 17.440000] uncorrectable error :
[ 17.440000] end_request: I/O error, dev mtdblock0, sector 784
[ 17.440000] uncorrectable error :
[ 17.450000] uncorrectable error :
[ 17.450000] end_request: I/O error, dev mtdblock0, sector 784
[ 17.460000] uncorrectable error :
[ 17.460000] uncorrectable error :
[ 17.460000] end_request: I/O error, dev mtdblock0, sector 512
[ 17.500000] uncorrectable error :
[ 17.500000] uncorrectable error :
[ 17.500000] end_request: I/O error, dev mtdblock1, sector 2048
[ 17.520000] uncorrectable error :
[ 17.530000] uncorrectable error :
[ 17.530000] end_request: I/O error, dev mtdblock1, sector 512
[ 17.690000] EXT3 FS on sda1, internal journal
[ 18.120000] Probing for Synopsis GMAC, unit 0
[ 18.120000] eth0: Tuning GMAC 0 RGMII timings
[ 18.130000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 18.130000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
[ 18.140000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
[ 18.150000] eth0: Ethernet addr: 00:30:e0:00:00:00
[ 18.150000] probe() eth0: Leon x2 clock
[ 18.180000] Power button driver registered
[ 18.200000] Turning off blinking LED.
[ 18.640000] uncorrectable error :
[ 18.640000] uncorrectable error :
[ 18.640000] end_request: I/O error, dev mtdblock0, sector 2048
[ 18.670000] uncorrectable error :
[ 18.670000] uncorrectable error :
[ 18.680000] end_request: I/O error, dev mtdblock0, sector 768
[ 18.680000] uncorrectable error :
[ 18.680000] uncorrectable error :
[ 18.690000] end_request: I/O error, dev mtdblock0, sector 768
[ 18.690000] uncorrectable error :
[ 18.700000] uncorrectable error :
[ 18.700000] end_request: I/O error, dev mtdblock0, sector 776
[ 18.710000] uncorrectable error :
[ 18.710000] uncorrectable error :
[ 18.710000] end_request: I/O error, dev mtdblock0, sector 776
[ 18.720000] uncorrectable error :
[ 18.720000] uncorrectable error :
[ 18.730000] end_request: I/O error, dev mtdblock0, sector 784
[ 18.730000] uncorrectable error :
[ 18.740000] uncorrectable error :
[ 18.740000] end_request: I/O error, dev mtdblock0, sector 784
[ 18.750000] uncorrectable error :
[ 18.750000] uncorrectable error :
[ 18.750000] end_request: I/O error, dev mtdblock0, sector 512
[ 18.780000] uncorrectable error :
[ 18.790000] uncorrectable error :
[ 18.790000] end_request: I/O error, dev mtdblock1, sector 2048
[ 18.810000] uncorrectable error :
[ 18.810000] uncorrectable error :
[ 18.820000] end_request: I/O error, dev mtdblock1, sector 512
[ 18.910000] uncorrectable error :
[ 18.910000] uncorrectable error :
[ 18.920000] end_request: I/O error, dev mtdblock0, sector 2048
[ 18.940000] uncorrectable error :
[ 18.950000] uncorrectable error :
[ 18.950000] end_request: I/O error, dev mtdblock0, sector 768
[ 18.960000] uncorrectable error :
[ 18.960000] uncorrectable error :
[ 18.960000] end_request: I/O error, dev mtdblock0, sector 768
[ 18.970000] uncorrectable error :
[ 18.970000] uncorrectable error :
[ 18.970000] end_request: I/O error, dev mtdblock0, sector 776
[ 18.980000] uncorrectable error :
[ 18.980000] uncorrectable error :
[ 18.990000] end_request: I/O error, dev mtdblock0, sector 776
[ 18.990000] uncorrectable error :
[ 19.000000] uncorrectable error :
[ 19.000000] end_request: I/O error, dev mtdblock0, sector 784
[ 19.010000] uncorrectable error :
[ 19.010000] uncorrectable error :
[ 19.010000] end_request: I/O error, dev mtdblock0, sector 784
[ 19.020000] uncorrectable error :
[ 19.020000] uncorrectable error :
[ 19.030000] end_request: I/O error, dev mtdblock0, sector 512
[ 19.060000] uncorrectable error :
[ 19.060000] uncorrectable error :
[ 19.060000] end_request: I/O error, dev mtdblock1, sector 2048
[ 19.080000] uncorrectable error :
[ 19.090000] uncorrectable error :
[ 19.090000] end_request: I/O error, dev mtdblock1, sector 512
[ 19.280000] uncorrectable error :
[ 19.280000] uncorrectable error :
[ 19.280000] end_request: I/O error, dev mtdblock0, sector 2048
[ 19.310000] uncorrectable error :
[ 19.310000] uncorrectable error :
[ 19.320000] end_request: I/O error, dev mtdblock0, sector 768
[ 19.330000] uncorrectable error :
[ 19.330000] uncorrectable error :
[ 19.330000] end_request: I/O error, dev mtdblock0, sector 768
[ 19.340000] uncorrectable error :
[ 19.340000] uncorrectable error :
[ 19.340000] end_request: I/O error, dev mtdblock0, sector 776
[ 19.350000] uncorrectable error :
[ 19.350000] uncorrectable error :
[ 19.360000] end_request: I/O error, dev mtdblock0, sector 776
[ 19.360000] uncorrectable error :
[ 19.370000] uncorrectable error :
[ 19.370000] end_request: I/O error, dev mtdblock0, sector 784
[ 19.380000] uncorrectable error :
[ 19.380000] uncorrectable error :
[ 19.380000] end_request: I/O error, dev mtdblock0, sector 784
[ 19.390000] uncorrectable error :
[ 19.390000] uncorrectable error :
[ 19.400000] end_request: I/O error, dev mtdblock0, sector 512
[ 19.430000] uncorrectable error :
[ 19.430000] uncorrectable error :
[ 19.430000] end_request: I/O error, dev mtdblock1, sector 2048
[ 19.450000] uncorrectable error :
[ 19.460000] uncorrectable error :
[ 19.460000] end_request: I/O error, dev mtdblock1, sector 512
[ 19.550000] uncorrectable error :
[ 19.560000] uncorrectable error :
[ 19.560000] end_request: I/O error, dev mtdblock0, sector 2048
[ 19.590000] uncorrectable error :
[ 19.590000] uncorrectable error :
[ 19.590000] end_request: I/O error, dev mtdblock0, sector 768
[ 19.600000] uncorrectable error :
[ 19.600000] uncorrectable error :
[ 19.610000] end_request: I/O error, dev mtdblock0, sector 768
[ 19.610000] uncorrectable error :
[ 19.620000] uncorrectable error :
[ 19.620000] end_request: I/O error, dev mtdblock0, sector 776
[ 19.620000] uncorrectable error :
[ 19.630000] uncorrectable error :
[ 19.630000] end_request: I/O error, dev mtdblock0, sector 776
[ 19.640000] uncorrectable error :
[ 19.640000] uncorrectable error :
[ 19.640000] end_request: I/O error, dev mtdblock0, sector 784
[ 19.650000] uncorrectable error :
[ 19.650000] uncorrectable error :
[ 19.660000] end_request: I/O error, dev mtdblock0, sector 784
[ 19.660000] uncorrectable error :
[ 19.670000] uncorrectable error :
[ 19.670000] end_request: I/O error, dev mtdblock0, sector 512
[ 19.700000] uncorrectable error :
[ 19.710000] uncorrectable error :
[ 19.710000] end_request: I/O error, dev mtdblock1, sector 2048
[ 19.730000] uncorrectable error :
[ 19.730000] uncorrectable error :
[ 19.740000] end_request: I/O error, dev mtdblock1, sector 512
[ 20.310000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 20.310000] CoPro offload is active on eth0
[ 20.320000] Alloc'ing ARM descs 8192 bytes
[ 20.320000] Alloc'ing CoPro parameters 36 bytes
[ 20.320000] gmac gmac.0: firmware: requesting gmac_copro_firmware
[ 20.370000] CoPro: Programming start address as 0xd000e000
[ 20.470000] eth0: Resetting GMAC
[ 20.470000] eth0: GMAC reset complete
[ 20.480000] eth0: Setting Rx flow control thresholds for LAN port
[ 21.040000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 21.540000] eth0: link down
[ 23.500000] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 23.540000] eth0: link up, 100Mbps, full-duplex, using pause, lpa 0x45E1
[ 23.540000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 33.610000] eth0: no IPv6 routers present
[ 8210.830000] uncorrectable error :
[ 8210.830000] uncorrectable error :
[ 8210.830000] end_request: I/O error, dev mtdblock0, sector 2048
[ 8210.830000] __ratelimit: 50 callbacks suppressed
[ 8210.830000] Buffer I/O error on device mtdblock0, logical block 256
[ 8210.870000] uncorrectable error :
[ 8210.870000] uncorrectable error :
[ 8210.880000] end_request: I/O error, dev mtdblock0, sector 768
[ 8210.880000] Buffer I/O error on device mtdblock0, logical block 96
[ 8210.890000] uncorrectable error :
[ 8210.890000] uncorrectable error :
[ 8210.900000] end_request: I/O error, dev mtdblock0, sector 768
[ 8210.900000] Buffer I/O error on device mtdblock0, logical block 96
[ 8210.910000] uncorrectable error :
[ 8210.910000] uncorrectable error :
[ 8210.920000] end_request: I/O error, dev mtdblock0, sector 776
[ 8210.920000] Buffer I/O error on device mtdblock0, logical block 97
[ 8210.930000] uncorrectable error :
[ 8210.930000] uncorrectable error :
[ 8210.940000] end_request: I/O error, dev mtdblock0, sector 776
[ 8210.940000] Buffer I/O error on device mtdblock0, logical block 97
[ 8210.950000] uncorrectable error :
[ 8210.950000] uncorrectable error :
[ 8210.950000] end_request: I/O error, dev mtdblock0, sector 784
[ 8210.950000] Buffer I/O error on device mtdblock0, logical block 98
[ 8210.970000] uncorrectable error :
[ 8210.970000] uncorrectable error :
[ 8210.970000] end_request: I/O error, dev mtdblock0, sector 784
[ 8210.970000] Buffer I/O error on device mtdblock0, logical block 98
[ 8210.990000] uncorrectable error :
[ 8210.990000] uncorrectable error :
[ 8210.990000] end_request: I/O error, dev mtdblock0, sector 512
[ 8210.990000] Buffer I/O error on device mtdblock0, logical block 64
[ 8211.030000] uncorrectable error :
[ 8211.030000] uncorrectable error :
[ 8211.040000] end_request: I/O error, dev mtdblock1, sector 2048
[ 8211.040000] Buffer I/O error on device mtdblock1, logical block 256
[ 8211.060000] uncorrectable error :
[ 8211.070000] uncorrectable error :
[ 8211.070000] end_request: I/O error, dev mtdblock1, sector 512
[ 8211.070000] Buffer I/O error on device mtdblock1, logical block 64
Re: Booting Debian on Pogoplug Pro
December 12, 2011 06:14PM
When you type in "mount", what is the output (please copy and paste) also your /etc/fstab? mtdblock0 and mtdblock1 is the uboot and kernel respectively in nand space. Your system shouldn't be accessing it. Bodhi, Varkey, are you all getting the same errors?
Re: Booting Debian on Pogoplug Pro
December 12, 2011 06:16PM
I've have not seen any errors in dmesg. I've been monitoring logread once in a while and no error either!
Re: Booting Debian on Pogoplug Pro
December 12, 2011 06:51PM
bodhi Wrote:
-------------------------------------------------------
> I've have not seen any errors in dmesg. I've been
> monitoring logread once in a while and no error
> either!


Sounds great! Thanks for the immediate response Bodhi! As I mentioned before mtdblock0 and mtdblock1 are both in pogoplug nand and are the location of the uboot and kernel, respectively. The system should not be accessing these areas. The module xce.ko should not be loaded since that is only for cloudengines connect status light. The light is controlled by what Bodhi and Varkey have shown above.
Re: Booting Debian on Pogoplug Pro
December 12, 2011 11:06PM
No such errors for me as well. Anyway if anyone needs the debian rootfs with all the above modifications done, here it is -- http://www.varkey.in/files/debian-rootfs-pogopro-varkey.tar.gz

Just extract it to an ext3 formatted disk. After extracting update your correct ethernet MAC address in /etc/network/interfaces
Also regenerate your SSH keys once you are logged it to the debian system as given here -- http://www.cyberciti.biz/faq/howto-regenerate-openssh-host-keys/
The default login is root / root and the md5sum of the file is e77e6cfb585c1df7f0f0b0ab6c8796bc
Re: Booting Debian on Pogoplug Pro
December 13, 2011 12:05AM
mount produces:

rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,noatime,errors=remount-ro,user_xattr,acl,data=writeback)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,relatime,mode=755)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev type tmpfs (rw,relatime,size=10240k,mode=755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)


/etc/fstab

# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/root / ext2 noatime,errors=remount-ro 0 1
/dev/sda2 none swap sw 0 0
tmpfs /tmp tmpfs defaults 0 0
Re: Booting Debian on Pogoplug Pro
December 13, 2011 12:08AM
I've figured it out - it's 'blkid' that's doing it.

/dev/ubi0_0: UUID="5ba52dea-8b45-44b2-90e6-6633c6d44004" TYPE="ubifs"
/dev/sda1: UUID="247030d5-0017-4a12-904d-250a306880d4" TYPE="ext3"
/dev/sda2: UUID="2abb2682-f269-4da9-b3aa-4f98bbe84472" TYPE="swap"


I was checking and executed blkid. duh..

sorry.

PHT
Re: Booting Debian on Pogoplug Pro
December 13, 2011 04:24AM
varkey Wrote:
-------------------------------------------------------
> No such errors for me as well. Anyway if anyone
> needs the debian rootfs with all the above
> modifications done, here it is --
> http://www.varkey.in/files/debian-rootfs-pogopro-v
> arkey.tar.gz
>

You the man Varkey!

> Just extract it to an ext3 formatted disk. After
> extracting update your correct ethernet MAC
> address in /etc/network/interfaces
> Also regenerate your SSH keys once you are logged
> it to the debian system as given here --
> http://www.cyberciti.biz/faq/howto-regenerate-open
> ssh-host-keys/
> The default login is root / root and the md5sum of
> the file is e77e6cfb585c1df7f0f0b0ab6c8796bc

That makes it about as easy as it gets.

Addendum:
Download confirmed.

Addendum+:
@hopetindall
Glad you figured it out.

Addendum++:
@varkey
The /boot in your rootfs does include uImage.pci and uImage.nopci correct?



Edited 4 time(s). Last edit at 12/13/2011 05:06AM by oddballhero.
Re: Booting Debian on Pogoplug Pro
December 13, 2011 06:05AM
^ Nope, /boot has only the kirkwood kernel files, nothing else.

root@debian:/boot# ls
config-2.6.32-5-kirkwood      System.map-2.6.32-5-kirkwood
initrd.img-2.6.32-5-kirkwood  vmlinuz-2.6.32-5-kirkwood

Are the files uImage.pci and uImage.nopci important? My Pogo Pro is working fine without those files.
Re: Booting Debian on Pogoplug Pro
December 13, 2011 06:42AM
varkey Wrote:
-------------------------------------------------------
> ^ Nope, /boot has only the kirkwood kernel files,
> nothing else.
>
>
> root@debian:/boot# ls
> config-2.6.32-5-kirkwood
> System.map-2.6.32-5-kirkwood
> initrd.img-2.6.32-5-kirkwood
> vmlinuz-2.6.32-5-kirkwood
>
>
> Are the files uImage.pci and uImage.nopci
> important? My Pogo Pro is working fine without
> those files.

Those are the actual kernels used. The ALARM install has them both in /boot of their usb drive before installing the proper one into nand. The uImage.pci is for Pros and the uImage.nopci is for the B0Xs. With those, one can make a script for a standalone installation, especially if included in the tar file. In any case, it's nice to have the actual kernel in case of emergency.
Re: Booting Debian on Pogoplug Pro
December 13, 2011 10:48AM
Thanks again for creating this thread and all this information.

Can I just clarify....I thought the contents of /boot in the debian image didn't matter.

Doesn't the kernel that's run (which is the ALARM kernel) actually come from NAND? - the images in /boot aren't used; right?

(in fact - when I run Debian on my NSLU2 - (which also gets the kernel from the NAND - there isn't even a /boot on the disk)
PHT



Edited 1 time(s). Last edit at 12/13/2011 11:32AM by hopetindall.
Re: Booting Debian on Pogoplug Pro
December 13, 2011 02:27PM
varkey Wrote:
-------------------------------------------------------
> No such errors for me as well. Anyway if anyone
> needs the debian rootfs with all the above
> modifications done, here it is --
> http://www.varkey.in/files/debian-rootfs-pogopro-v
> arkey.tar.gz
>
> Just extract it to an ext3 formatted disk. After
> extracting update your correct ethernet MAC
> address in /etc/network/interfaces
> Also regenerate your SSH keys once you are logged
> it to the debian system as given here --
> http://www.cyberciti.biz/faq/howto-regenerate-open
> ssh-host-keys/
> The default login is root / root and the md5sum of
> the file is e77e6cfb585c1df7f0f0b0ab6c8796bc

Varkey,

Awesome! it's great to have this, especially now it seems the Pogoplug Pro variations are on sale:
http://www.buy.com/prod/pogoplug-file-sharing-solution-black/221688297.html

And thanks for providing your GoFlex Net rootfs at your site, too! saved me countless hours recovering from a botched install :-)

bodhi
Re: Booting Debian on Pogoplug Pro
December 13, 2011 04:51PM
hopetindall Wrote:
-------------------------------------------------------
> Thanks again for creating this thread and all this
> information.
>
> Can I just clarify....I thought the contents of
> /boot in the debian image didn't matter.
>
> Doesn't the kernel that's run (which is the ALARM
> kernel) actually come from NAND? - the images in
> /boot aren't used; right?
>
> (in fact - when I run Debian on my NSLU2 - (which
> also gets the kernel from the NAND - there isn't
> even a /boot on the disk)
> PHT

Well, if you read what I wrote, that is what was stated. The ALARM install has the kernels in /boot before installing it into NAND. After the install, it is in NAND. If you have the kernels, it does not matter whether they are in /boot or not but at LEAST if you have them, and something goes wrong, then you can recover. It does not matter, I was just thinking of a script that would install it directly from usb drive. Varkey already did most of the work. I thought it was just more convenient than having to reinstall with the ALARM install, especially since you don't have the convenience of falling back to the original environment as you do with the Kirkwood install. So, if you wanted to recover (since the kernel is in nand), you have to use a serial cable which leaves you with 2 options: 1. set parameters to the original kernel and the busybox env in firmware and rerun the ALARM install. 2. Just have the kernel on the usb and transfer it to NAND using a few commands. Ok, so as clarification, you don't need the kernels in /boot.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: