Good point. But the rolling release model also implies a slightly higher workload on the administrator (time is a problem for me as my work has nothing to do with computers so the time I spend on them is lost to other things). Arch appears to expect (justifably, in terms of its model) more of its administrators than server OSs like Debian. Or is this just a mis-impression?

If you're going to set-and-forget, does it matter where evolution takes those not stuck in time? (just an observation, I do understand in both directions.)

I've updated the first post to pull all information together and clean up the installation steps.

Hello,

Thanks for all the info here guys.

I got a POGO-P24, with works using the Arch Linux Pogoplug Pro/Video/v3.

So after installing alarm I've extracted Varkey's image to a second USB Flash, changed the Mac address, and placed on the same USB port as the working alarm install.

The green light blinks for some time, then I get a solid green led, but the device won't register in the DHCP server. It looks like the network won't come up.

The image I've downloaded already came with the

/sbin/depmod -a
/sbin/modprobe gmac

in its /etc/rc.local.

I'm also posting my vat/log/dmesg.

Any ideas of what I have to do to troubleshoot this network problem ?

Is there a way to get the netconsole on it ?

My second usb drive with alarm comes up normally.

Thanks a lot for the help!

root@amadea:/media/25b36417-9f0f-4ef1-83dd-b25911ab96e7# cat var/log/dmesg
[ 0.000000] Linux version 2.6.31.6_SMP_820 (root@ProDev) (gcc version 4.6.0 20110429 (prerelease) (GCC) ) #100 SMP Sun May 29 04:53:45 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 c04008e0, node_mem_map c0426000
[ 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: 125496KB available (3692K code, 291K data, 124K 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
[ 0.720000] bio: create slab <bio-0> at 0
[ 0.730000] SCSI subsystem initialized
[ 0.730000] libata version 3.00 loaded.
[ 0.730000] usbcore: registered new interface driver usbfs
[ 0.740000] usbcore: registered new interface driver hub
[ 0.740000] usbcore: registered new device driver usb
[ 0.780000] NET: Registered protocol family 2
[ 0.780000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.790000] Switched to NOHz mode on CPU #0
[ 0.790000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.790000] Switched to NOHz mode on CPU #1
[ 0.800000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.810000] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.810000] TCP reno registered
[ 0.820000] NET: Registered protocol family 1
[ 0.820000] Create fragment cache
[ 0.830000] fuse init (API version 7.12)
[ 0.830000] msgmni has been set to 245
[ 0.840000] alg: No test for stdrng (krng)
[ 0.850000] io scheduler noop registered
[ 0.850000] io scheduler anticipatory registered
[ 0.850000] io scheduler deadline registered
[ 0.860000] io scheduler cfq registered (default)
[ 0.880000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.890000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
[ 0.910000] brd: module loaded
[ 0.910000] loop: module loaded
[ 0.920000] ox820sata: OX820 sata core.
[ 0.920000] scsi0 : oxnassata
[ 0.930000] scsi1 : oxnassata
[ 0.930000] ata1: SATA max UDMA/133 irq 50
[ 0.930000] ata2: SATA max UDMA/133 irq 50
[ 0.940000] ox820sata: reseting SATA core
[ 1.300000] ata1: SATA link down (SStatus 0 SControl 300)
[ 1.300000] ox820sata: reseting SATA core
[ 1.660000] ata2: SATA link down (SStatus 0 SControl 300)
[ 1.660000] tun: Universal TUN/TAP device driver, 1.6
[ 1.670000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 1.670000] NAND: Page read time 40ms
[ 1.680000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[ 1.690000] Scanning device for bad blocks
[ 1.690000] Bad eraseblock 74 at 0x000000940000
[ 1.700000] Bad eraseblock 79 at 0x0000009e0000
[ 1.770000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[ 1.780000] 0x000000000000-0x000000e00000 : "boot"
[ 1.780000] 0x000000e00000-0x000008000000 : "rootfs"
[ 1.790000] UBI: attaching mtd2 to ubi0
[ 1.790000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 1.800000] UBI: logical eraseblock size: 129024 bytes
[ 1.800000] UBI: smallest flash I/O unit: 2048
[ 1.810000] UBI: sub-page size: 512
[ 1.810000] UBI: VID header offset: 512 (aligned 512)
[ 1.820000] UBI: data offset: 2048
[ 2.230000] UBI: attached mtd2 to ubi0
[ 2.240000] UBI: MTD device name: "rootfs"
[ 2.240000] UBI: MTD device size: 114 MiB
[ 2.250000] UBI: number of good PEBs: 912
[ 2.250000] UBI: number of bad PEBs: 0
[ 2.250000] UBI: max. allowed volumes: 128
[ 2.260000] UBI: wear-leveling threshold: 4096
[ 2.260000] UBI: number of internal volumes: 1
[ 2.270000] UBI: number of user volumes: 1
[ 2.270000] UBI: available PEBs: 0
[ 2.280000] UBI: total number of reserved PEBs: 912
[ 2.280000] UBI: number of PEBs reserved for bad PEB handling: 9
[ 2.290000] UBI: max/mean erase counter: 2/0
[ 2.290000] UBI: image sequence number: 0
[ 2.300000] UBI: background thread "ubi_bgt0d" started, PID 295
[ 2.300000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 2.300000] oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
[ 2.300000] oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
[ 2.330000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
[ 2.350000] oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
[ 2.350000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 2.360000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.360000] usb usb1: Product: OXNAS EHCI Host Controller
[ 2.370000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
[ 2.380000] usb usb1: SerialNumber: usb
[ 2.380000] usb usb1: configuration #1 chosen from 1 choice
[ 2.390000] hub 1-0:1.0: USB hub found
[ 2.390000] hub 1-0:1.0: 2 ports detected
[ 2.400000] Initializing USB Mass Storage driver...
[ 2.400000] usbcore: registered new interface driver usb-storage
[ 2.410000] USB Mass Storage support registered.
[ 2.410000] mice: PS/2 mouse device common for all mice
[ 2.420000] TCP cubic registered
[ 2.420000] NET: Registered protocol family 10
[ 2.430000] NET: Registered protocol family 17
[ 2.430000] RPC: Registered udp transport module.
[ 2.440000] RPC: Registered tcp transport module.
[ 2.440000] Waiting for root device /dev/sda1...
[ 2.710000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
[ 2.860000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 2.860000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.870000] usb 1-1: Product: USB2.0 Hub
[ 2.870000] usb 1-1: configuration #1 chosen from 1 choice
[ 2.880000] hub 1-1:1.0: USB hub found
[ 2.890000] hub 1-1:1.0: 4 ports detected
[ 3.170000] usb 1-1.3: new high speed USB device using oxnas-ehci and address 3
[ 3.280000] usb 1-1.3: New USB device found, idVendor=18a5, idProduct=0302
[ 3.280000] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.290000] usb 1-1.3: Product: STORE N GO
[ 3.300000] usb 1-1.3: Manufacturer: Verbatim
[ 3.300000] usb 1-1.3: SerialNumber: 3A9A2D09D2FD7E33
[ 3.310000] usb 1-1.3: configuration #1 chosen from 1 choice
[ 3.310000] scsi2 : SCSI emulation for USB Mass Storage devices
[ 3.320000] usb-storage: device found at 3
[ 3.320000] usb-storage: waiting for device to settle before scanning
[ 8.320000] scsi 2:0:0:0: Direct-Access Verbatim STORE N GO 1.00 PQ: 0 ANSI: 2
[ 8.330000] usb-storage: device scan complete
[ 8.330000] sd 2:0:0:0: [sda] 7829504 512-byte logical blocks: (4.00 GB/3.73 GiB)
[ 8.340000] sd 2:0:0:0: [sda] Write Protect is off
[ 8.340000] sd 2:0:0:0: [sda] Mode Sense: 03 00 00 00
[ 8.340000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 8.350000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 8.360000] sda: sda1 sda2
[ 8.360000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[ 8.370000] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 8.390000] kjournald starting. Commit interval 5 seconds
[ 8.390000] EXT3 FS on sda1, internal journal
[ 8.390000] EXT3-fs: mounted filesystem with writeback data mode.
[ 8.390000] VFS: Mounted root (ext3 filesystem) on device 8:1.
[ 8.390000] Freeing init memory: 124K
[ 15.720000] EXT3 FS on sda1, internal journal
[ 15.980000] Probing for Synopsis GMAC, unit 0
[ 15.980000] eth0: Tuning GMAC 0 RGMII timings
[ 15.990000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 16.000000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
[ 16.000000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
[ 16.010000] eth0: Ethernet addr: 00:30:e0:00:00:00
[ 16.010000] probe() eth0: Leon x2 clock
[ 16.040000] Turning off blinking LED.
[ 17.630000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 17.640000] CoPro offload is active on eth0
[ 17.640000] Alloc'ing ARM descs 8192 bytes
[ 17.640000] Alloc'ing CoPro parameters 36 bytes
[ 17.650000] gmac gmac.0: firmware: requesting gmac_copro_firmware
[ 17.680000] CoPro: Programming start address as 0xd000e000
[ 17.790000] eth0: Resetting GMAC
[ 17.790000] eth0: GMAC reset complete
[ 17.800000] eth0: Setting Rx flow control thresholds for LAN port
[ 18.350000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[ 18.850000] eth0: link down
[ 20.810000] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 20.850000] eth0: link up, 100Mbps, full-duplex, using pause, lpa 0x45E1
[ 20.860000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

I have had similar problems with every form of OS on pogo v2 except the original version that came with it. I have tried Arch alarm, Debian, Jeff's recompiled rescue system V2. None of them can get an internet address when not behind a router. Behind a router, all versions can get an ip address on the local net. Only the original pogoplug was able to communicate with my isp's dhcp server and accept the offered address. The others got as far as sending out discoveries, having offers made to them, but never to accepting those offers. I have tried many, many different dhcp setups and the result has always been the same or worse. (No discovery packets even.)

Under Arch alarm, the file dhcpcd-eth0.lease always comes up with the Dec 31, 1969 date and is in a binary format of some kind. I eventually get a proper time going using ntp, but a 1969 lease is pretty old.

When I finally deploy this pogoplug for collecting remote data, it will have to talk to the isp directly. Any ideas where the failure occurs? The captured packets from wireshark indicate that the discover comes from 0.0.0.0 but that the Offer is sent to the previous ip address. I tried setting eth0 promiscuous so it should get anything, but that didn't change anything.

I would use the original software with optware, except that I don't have an original kernel image since I used the rescueV2 scripts. The rescue V2 kernel won't run most optware packages. And, although I can boot into the V2 rescue system, I haven't succeeded in mounting it from a USB boot. The kernel doesn't seem to be making the right devices for mounting UBIFS.

Help please..

TJ

Wladston Viana Wrote:
-------------------------------------------------------
> Hello,
>
> Thanks for all the info here guys.
>
> I got a POGO-P24, with works using the Arch Linux
> Pogoplug Pro/Video/v3.
>
> So after installing alarm I've extracted Varkey's
> image to a second USB Flash, changed the Mac
> address, and placed on the same USB port as the
> working alarm install.
>
> The green light blinks for some time, then I get a
> solid green led, but the device won't register in
> the DHCP server. It looks like the network won't
> come up.
>
> The image I've downloaded already came with the
>
> /sbin/depmod -a
> /sbin/modprobe gmac
>
> in its /etc/rc.local.
>
> I'm also posting my vat/log/dmesg.
>
> Any ideas of what I have to do to troubleshoot
> this network problem ?
>
> Is there a way to get the netconsole on it ?
>
> My second usb drive with alarm comes up normally.
>
> Thanks a lot for the help!
>

I don't think we can get net console working on this (I've asked at Arch Linux ARM forum). You could connect a serial console, though. My dmesg output shows some differences with yours but nothing out of ordinary (mine has PCI, and the build number is #99). 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.420000] 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.340000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[    5.350000] 0x000000000000-0x000000e00000 : "boot"
[    5.350000] 0x000000e00000-0x000008000000 : "rootfs"
[    5.360000] UBI: attaching mtd2 to ubi0
[    5.360000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    5.370000] UBI: logical eraseblock size:    129024 bytes
[    5.370000] UBI: smallest flash I/O unit:    2048
[    5.380000] UBI: sub-page size:              512
[    5.380000] UBI: VID header offset:          512 (aligned 512)
[    5.390000] UBI: data offset:                2048
[    5.800000] 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:        912
[    5.820000] UBI: number of bad PEBs:         0
[    5.830000] UBI: max. allowed volumes:       128
[    5.830000] UBI: wear-leveling threshold:    4096
[    5.830000] UBI: number of internal volumes: 1
[    5.840000] UBI: number of user volumes:     1
[    5.840000] UBI: available PEBs:             0
[    5.850000] UBI: total number of reserved PEBs: 912
[    5.850000] UBI: number of PEBs reserved for bad PEB handling: 9
[    5.860000] UBI: max/mean erase counter: 2/1
[    5.860000] 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.900000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
[    5.920000] oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
[    5.920000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    5.930000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.930000] usb usb1: Product: OXNAS EHCI Host Controller
[    5.940000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
[    5.950000] usb usb1: SerialNumber: usb
[    5.950000] usb usb1: configuration #1 chosen from 1 choice
[    5.960000] hub 1-0:1.0: USB hub found
[    5.960000] hub 1-0:1.0: 2 ports detected
[    5.970000] Initializing USB Mass Storage driver...
[    5.970000] usbcore: registered new interface driver usb-storage
[    5.980000] USB Mass Storage support registered.
[    5.980000] mice: PS/2 mouse device common for all mice
[    5.990000] TCP cubic registered
[    5.990000] NET: Registered protocol family 10
[    6.000000] NET: Registered protocol family 17
[    6.000000] RPC: Registered udp transport module.
[    6.010000] RPC: Registered tcp transport module.
[    6.010000] Waiting for root device /dev/sda1...
[    6.280000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
[    6.430000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    6.430000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    6.440000] usb 1-1: Product: USB2.0 Hub
[    6.440000] usb 1-1: configuration #1 chosen from 1 choice
[    6.450000] hub 1-1:1.0: USB hub found
[    6.460000] hub 1-1:1.0: 4 ports detected
[    6.740000] usb 1-1.1: new high speed USB device using oxnas-ehci and address 3
[    6.850000] usb 1-1.1: New USB device found, idVendor=0781, idProduct=556b
[    6.850000] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.860000] usb 1-1.1: Product: Cruzer Edge
[    6.860000] usb 1-1.1: Manufacturer: SanDisk
[    6.870000] usb 1-1.1: SerialNumber: xxxxxxxxxx
[    6.870000] usb 1-1.1: configuration #1 chosen from 1 choice
[    6.880000] scsi2 : SCSI emulation for USB Mass Storage devices
[    6.890000] usb-storage: device found at 3
[    6.890000] usb-storage: waiting for device to settle before scanning
[   11.890000] scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer Edge      1.14 PQ: 0 ANSI: 2
[   11.900000] usb-storage: device scan complete
[   11.900000] sd 2:0:0:0: [sda] 7821312 512-byte logical blocks: (4.00 GB/3.72 GiB)
[   11.910000] sd 2:0:0:0: [sda] Write Protect is off
[   11.910000] sd 2:0:0:0: [sda] Mode Sense: 03 00 00 00
[   11.910000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[   11.920000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[   11.930000]  sda: sda1
[   11.940000] sd 2:0:0:0: [sda] Assuming drive cache: write through
[   11.950000] sd 2:0:0:0: [sda] Attached SCSI removable disk
[   11.960000] kjournald starting.  Commit interval 5 seconds
[   11.960000] EXT3 FS on sda1, internal journal
[   11.960000] EXT3-fs: mounted filesystem with writeback data mode.
[   11.960000] VFS: Mounted root (ext3 filesystem) on device 8:1.
[   11.960000] Freeing init memory: 128K
[   13.180000] PCI: enabling device 0000:00:00.0 (0140 -> 0142)
[   13.190000] 
[   13.190000] 
[   13.190000] === pAd = c8a3a000, size = 519160 ===
[   13.190000] 
[   13.200000] <-- RTMPAllocAdapterBlock, Status=0
[   13.210000] pAd->CSRBaseAddress =0xf5000000, csr_addr=0xf5000000!
[   15.080000] EXT3 FS on sda1, internal journal
[   15.350000] Probing for Synopsis GMAC, unit 0
[   15.350000] eth0: Tuning GMAC 0 RGMII timings
[   15.350000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[   15.360000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
[   15.370000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
[   15.370000] eth0: Ethernet addr: 00:30:e0:00:00:00
[   15.380000] probe() eth0: Leon x2 clock
[   15.410000] Turning off blinking LED.
[   16.650000] Adding 1048568k swap on /swapfile1.  Priority:-1 extents:621 across:1550432k 
[   17.290000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[   17.290000] CoPro offload is active on eth0
[   17.300000] Alloc'ing ARM descs 8192 bytes
[   17.300000] Alloc'ing CoPro parameters 36 bytes
[   17.310000] gmac gmac.0: firmware: requesting gmac_copro_firmware
[   17.340000] CoPro: Programming start address as 0xd000e000
[   17.450000] eth0: Resetting GMAC
[   17.450000] eth0: GMAC reset complete
[   17.460000] eth0: Setting Rx flow control thresholds for LAN port
[   18.010000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[   18.510000] eth0: link down
[   20.470000] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.010000] eth0: link up, 1000Mbps, full-duplex, using pause, lpa 0xC5E1
[   21.010000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   31.890000] eth0: no IPv6 routers present

I have been using archlinux on my pogoplugpro for a while. I am thinking of migrating it to either debian or ubuntu, the main reason for this switch being I am very comfortable using debian and its derivatives. I was thinking of using varkey's rootfs which I believe is based off squeeze. Obviously we have wheezy round the corner, which would mean support for squeeze is numbered. Since we are tied to the 2.6.31 kernel for the time being I was wondering if anyone has tried building a lucid rootfs. My main reasoning for trying lucid armel is that lucid LTS support would be available for server edition till 2015. This would be a big advantage over debian imho. If no one has tried lucid on pogoplug can anyone suggest how much additional work is required to get the rootfs working. Does it just require one to copy the kernel modules, firmware and led related tools from the ALARM rootfs?

bharath Wrote:
-------------------------------------------------------
Does it just require one to copy the
> kernel modules, firmware and led related tools
> from the ALARM rootfs?

Yes, basically that's the first steps we need to do to start booting with Debian rootfs. We also need other minor things such as Mac address, LED settings and depmod in rc.local. The first post basically laid out all we need to do for Debian.

The problem right now that has prevented one using Debian wheezy is udev (I found that seems to be the biggest hurdle in my several attempts to upgrade to Wheezy). Since the kernel installed in the Pro is using a much older version of udev, it must have caused some conflicts during boot time. I was not able to boot with Wheezy at all. I also briefly looked into using netconsole to troubleshoot the problem, but don't think this Arch kernel support it (not entirely sure about this, I got no clear response from others), so deciding to wait for WarheadsSE to upgrade to 3.1.x before looking further. It's too bad we can't use it to maximum potentials right now, unless using Arch.

bodhi Wrote:
-------------------------------------------------------
> bharath Wrote:
> --------------------------------------------------
> -----
> Does it just require one to copy the
> > kernel modules, firmware and led related tools
> > from the ALARM rootfs?
>
> Yes, basically that's the first steps we need to
> do to start booting with Debian rootfs. We also
> need other minor things such as Mac address, LED
> settings and depmod in rc.local. The first post
> basically laid out all we need to do for Debian.

Thanks for letting me know what exactly is need for me to migrate to debian.

> The problem right now that has prevented one using
> Debian wheezy is udev (I found that seems to be
> the biggest hurdle in my several attempts to
> upgrade to Wheezy). Since the kernel installed in
> the Pro is using a much older version of udev, it
> must have caused some conflicts during boot time.
> I was not able to boot with Wheezy at all. I also
> briefly looked into using netconsole to
> troubleshoot the problem, but don't think this
> Arch kernel support it (not entirely sure about
> this, I got no clear response from others), so
> deciding to wait for WarheadsSE to upgrade to
> 3.1.x before looking further. It's too bad we
> can't use it to maximum potentials right now,
> unless using Arch.

It is extremely unfortunate the oxnas patches are in such bad shape that it isnt easy to migrate to a newer kernel. Have you tried using serial console instead of netconsole to get it to work. I just opened my case and installed an esata adapter and have a serial console port as well.

I mispoke a litle bit above:

I also briefly looked into using netconsole to troubleshoot the problem, but don't think this Uboot version support it (not entirely sure about this, I got no clear response from others)

I've opened up the case to check out the Sata port to make sure I get the right cable. But I have not bought the serial header yet. I'm a little bit discourage to try to do more given the problems with upgrading, so right now I use it as a NAS box only.

Can you post a link where to get the right serial header here? thanks!

bodhi Wrote:
-------------------------------------------------------
> I mispoke a litle bit above:
>

> I also briefly looked into using netconsole to
> troubleshoot the problem, but don't think this
> Uboot version support it (not entirely sure
> about this, I got no clear response from others)
>

>

I am sorry I misread the post as well.

> I've opened up the case to check out the Sata port
> to make sure I get the right cable. But I have not
> bought the serial header yet. I'm a little bit
> discourage to try to do more given the problems
> with upgrading, so right now I use it as a NAS box
> only.

The main reason for my move towards eSATA being that I dont have to ever touch the NAND when I upgrade. That gives me a very big advantage. Also when you are buying the esata adapter make sure the sata connector is short, else you will not be able to close the case. I think WarheadsSE has posted in his picture which esata adapter he used.

> Can you post a link where to get the right serial
> header here? thanks!

The right serial header is 4-pin micro 2.0 JST PH which is basically a CDROM audio cable.

If not you can always get things from ebay, I would get these
http://www.ebay.com/itm/Micro-JST-PH-2-0-4-Pin-Connector-plug-Male-and-Female-Crimps-x-50-Sets-/120967395755

Crimping is going to be tricky.

edit:
I just found this on ebay http://www.ebay.com/itm/Micro-Mini-JST-2-0-PH-4-Pin-Connector-w-Wire-x-10-Sets-/170901825560 you wouldnt have to crimp.



Edited 1 time(s). Last edit at 09/02/2012 08:08PM by bharath.

Thanks for the JST header link!

Just to be clear about the upgrading trouble I had. I think most likely it's udev-related because it's one of the significant updates from Squeeze to Wheezy. Hopefully when I have a chance to hookup the serial console, it will provide more information.

By the way, it's great that we can even run Debian on this box :-) it's a bonus really, since it's OXNAS, not Kirwood. OTOH, I'm more than happy running Arch Linux ARM on it. I have 2 boxes, one runing Arch and the other running Debian. The box running Arch performs flawlessly for me.

Varkey

I appreciate your debian files. It works like a charm. It has been on for a long time at my house.

Now, it comes to a situation that I need a linux webcam on this pink box (pogoplug pro v2). However, the existing kernel does not load wecam modules. I have no way to obtain the kirkwood source code to build the kernel myself.

Can you re-build the debian with a new kernel with webcam support? Thanks!!!

lijianch Wrote:
-------------------------------------------------------
> Varkey
>
> I appreciate your debian files. It works like a
> charm. It has been on for a long time at my house.
>
>
> Now, it comes to a situation that I need a linux
> webcam on this pink box (pogoplug pro v2).
> However, the existing kernel does not load wecam
> modules. I have no way to obtain the kirkwood
> source code to build the kernel myself.
>
> Can you re-build the debian with a new kernel with
> webcam support? Thanks!!!

You could try "modprobe" the webcam module. See if it works instead of replacing the whole rootfs?

I tried and it gives me error.

FATAL: Module webcam not found.

I tried module-assistant

There is no SMP source header available.

You should find out the name of the module that supports the webcam model that you have. Arch Linux wiki has a list of webcams:
https://wiki.archlinux.org/index.php/Webcam_Setup#Linux_webcam_support

After identifying the name of the module, look for that inside your Arch Linux ARM rootfs USB drive. It should be somewhere under /lib/modules. Once you've found it, copy it to the same location on the Debian USB rootfs (i.e. /lib/modules/2.6.31.6_SMP_820/...), if the module is not already there. Rememember to unzip if the file name has extension ".ko.gz".

Modprobe this module in /etc/rc.local (look for "modprobe gmac" in there as example).

Basically these are the steps that Varkey will likely do if he creates another rootfs that includes support for this particular webcam.



Edited 1 time(s). Last edit at 09/08/2012 03:15PM by bodhi.

Does Debian not support compressed kernel modules for some reason? I have that support built into the kernel...

@WarheadsSE,

It's been a while ago, but I think back then Debian version we used did not have this support. I guess now one can just copy the whole modules tree from ALARM to /lib/modules and use it as is, providing the installed Debian version has the support.

I don't know if this is dead, or anything.

I used the ALARM installer, and my PogoPlug Pro boots into Arch pretty well. But I don't like Arch.

I downloaded the prebuilt Debian, and extracted it onto another USB. When trying to boot from USB, the PogoPlug blinks constantly and nothing happens. However booting off Arch works fine.

more than likely, it needs the newer kernel modules :)

Well, a bit of good news!

I've successfully upgraded the PogoPro Debian rootfs to Wheezy. It was a massive upgrade to go from Squeeze to Wheezy, but it went relatively without incident! The only times the upgrade process stopped were a few normal questions when one upgrading from one Debian version to the next (e.g. the current settings should be reused? should daemons be restarted automatically?...)

It's the old saying: when failed, try again, and again ... :-)

Addendum: I'm still using the same ALARM kernel modules from alarm 2.6.31.6_SMP_820 #99 SMP Sun May 29 03:04:43 EDT 2011



Edited 1 time(s). Last edit at 09/19/2012 11:49PM by bodhi.

Daniel Wrote:
-------------------------------------------------------
> I don't know if this is dead, or anything.
>
> I used the ALARM installer, and my PogoPlug Pro
> boots into Arch pretty well. But I don't like
> Arch.
>
> I downloaded the prebuilt Debian, and extracted it
> onto another USB. When trying to boot from USB,
> the PogoPlug blinks constantly and nothing
> happens. However booting off Arch works fine.

As Warhead said, look at the kernel modules under /lib/modules/2.6.31.6_SMP_820 in the your Debian rootfs. Since you've installed ALARM recently, newer kernel modules, if any, needed to be there (compare them with ones in the ALARM rootfs).

@bodhi this great news that you are using wheezy with debian. Any specific things to take care off?

@bharath,

I've not yet cleaning up the log file to get all the details. But here are the main points and things I've observed.

1. Upgrade using the current Debian Squeeze rootfs, don't start with Wheezy rootfs.

# cat /etc/apt/sources.list
deb http://ftp.us.debian.org/debian wheezy main

#apt-get update
#apt-get upgrade

I was never successful starting from Wheezy rootfs, because a lot of important differences would cause booting problem. I've hooked up the serial console and was expecting to spend time troubleshooting, but decided to start upgrading from the current USB stick instead. Perhaps that (starting from 3.2.xx) is something worth doing now that I can observe the serial console output.

2. apt-get upgrade reported: 115 upgraded, 0 newly installed, 0 to remove and 333 not upgraded. So it looks like the current Wheezy packages are now smart enough to hold back packages to avoid dependencies/conflicts. However, if one is looking for a specific version in Wheezy package, then look at the output and see if that package will be upgrade.

3. udev is kept the same version (164), instead of a much later version (I'm seeing ver 175 in Debian 3.2.28 and 164 in Debian 2.6.37). I believe 164 is in the ALARM kernel.

4. xfce was upgraded to 4.8. Which is good news, because now hald daemon is gone, yah :-) xfce 4.8 multi-threaded GTK+ and lots of things have improved. The PogoPro is now running a lot faster than the PogoPink V2 when I use remote desktop (I've been running xfce4.8 on the Pink for a few months).

Addendum:

5. Here are the questions and anwers during the upgrade. Most are trivials, except the one about the disks UUID. And at the end, initramfs-tools tried to generate the ramdisk image unsuccessful [EDIT: Closer look of the log, it did generate new ramdisk image, but gave errors in post-installation script /etc/initramfs/post-update.d//flash-kernel], but it does not matter because we're actually running the ALARM kernel.

- Configuring libc6 ... Restart services during package upgrades without asking? 
No

- Restart samba cups cron?
OK

- Configuration file `/etc/cups/cups-pdf.conf'  ... The default action is to keep your current version.
OK

- Configuring linux-base ... Update disk device IDs in system configuration?
Yes
 
- Setting up flash-kernel (3.2) ...
Configuration file `/etc/kernel/postinst.d/zz-flash-kernel'...
 ....     N or O  : keep your currently-installed version
 *** zz-flash-kernel (Y/I/N/O/D/Z) [default=N] ? 
N

6. Here is the serial console output:

U-Boot 1.1.2 (Jul 29 2010 - 19:36:07)

U-Boot code: 60D00000 -> 60D1C030  BSS: -> 60D21800
RAM Configuration:
	Bank #0: 60000000 128 MB
SRAM Configuration:
	64KB at 0x50000000
NAND:128 MiB
In:    serial
Out:   serial
Err:   serial
Setting Linux mem= boot arg value
Hit any key to stop autoboot:  2  1  0 

Loading from device 0: 128MiB 3,3V 8-bit (offset 0x500000)
   -- Using 1bit ECC style encoding
   Image Name:   Linux-2.6.31.6_SMP_820
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2132260 Bytes =  2 MB
   Load Address: 60008000
   Entry Point:  60008000
## Booting image at 60500000 ...
   Image Name:   Linux-2.6.31.6_SMP_820
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2132260 Bytes =  2 MB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux................................................................................................................................. done, booting the kernel.
[    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

..... (the rest are same as dmesg output)

Edited 3 time(s). Last edit at 09/21/2012 02:18AM by bodhi.

Great news, I just got varkeys rootfs setup on a usb key now. Will test it out for a few days and if all is good migrate to debian. I guess starting from scratch rootfs using debootstrap might have significant issues due to conflicts. Hopefully all the other packages that dont depend on udev get easily upgraded.

If you guys use the updated kernel, it has devtmpfs support, and a simple acept4 syscall hack should allow much more current udev's.

See https://github.com/archlinuxarm/PKGBUILDs/tree/master/alarm/libaccept4

@WarheadsSE,

Thanks for the udev tip!

BTW, what you do think about the idea of using your procedure for Booting the PogoPro entirely from SATA, but replacing Arch uImage with Debian uImage? is that possible or bad idea? If it is possible, would you give us some hints (if there is no NDA problem of course).

Thanks,
bodhi

I dont think it is going to be any different from booting of the USB. At the end of the day the root partition will have the debian filesystem instead of archlinux.

bharath Wrote:
-------------------------------------------------------
> I dont think it is going to be any different from
> booting of the USB. At the end of the day the root
> partition will have the debian filesystem instead
> of archlinux.

In fact, I think there are some differences. Remember we are running kernel 2.6.31.6 with 3.x.x rootfs. There are some packages with old version that can't be upgraded. We're stuck in 2.6.31 in those area :-) So I thought if there is an easy way to replace uImage with one that came from Debian then we can just build that image whenever we want from the 3.x.x. tree.

However, I'm happy that we can upgrade most of them to 3.x.x.

If you have a working rootfs on the USB drive you can use that as the rootfs for the SATA drive as well. I am not sure what the current status of 3.x kernel is for oxnas that warheadsse was working on.