Pogoplug v2 doesn't show up on LAN after Archlinux install
Posted by Waynosan
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 09, 2015 10:46PM |
Registered: 9 years ago Posts: 29 |
@bodhi,
So can I reboot it now? Not sure how to get the blparam binary onto the USB stick otherwise. The USB stick is in ext3 format so I don't think that my windows machine will read it. I can boot up Mint and put it on the USB stick that way. Let me know which is preferred and if it needs to be in one of the specific directories that you mentioned. Maybe there is a way to copy a file off of my PC with the serial console/Archlinux?
Have a good night.
So can I reboot it now? Not sure how to get the blparam binary onto the USB stick otherwise. The USB stick is in ext3 format so I don't think that my windows machine will read it. I can boot up Mint and put it on the USB stick that way. Let me know which is preferred and if it needs to be in one of the specific directories that you mentioned. Maybe there is a way to copy a file off of my PC with the serial console/Archlinux?
Have a good night.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 09, 2015 11:10PM |
Admin Registered: 13 years ago Posts: 19,107 |
Waynosan,
> I can boot up
> Mint and put it on the USB stick that way.
Download it on Mint, put it on a different USB stick, plug the stick into the Pogo, and copy it to the same directory you are on (for convenience). Then execute it:
It is a precaution mostly. Since we can't do anything to verify the u-boot flash before reboot (other than dumping it and do a binary diff), so at least blparam will do a sanity check by listing the envs from the envs area within mtd0.
If you list envs with blparam and get a sane listing with no error, you can reboot, and monitor the boot progress with serial console. It should boot into the Pogo OS and give you a prompt to log in.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I can boot up
> Mint and put it on the USB stick that way.
Download it on Mint, put it on a different USB stick, plug the stick into the Pogo, and copy it to the same directory you are on (for convenience). Then execute it:
./blparam
It is a precaution mostly. Since we can't do anything to verify the u-boot flash before reboot (other than dumping it and do a binary diff), so at least blparam will do a sanity check by listing the envs from the envs area within mtd0.
If you list envs with blparam and get a sane listing with no error, you can reboot, and monitor the boot progress with serial console. It should boot into the Pogo OS and give you a prompt to log in.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 10, 2015 04:10PM |
Registered: 9 years ago Posts: 29 |
OK, I had to reboot before copying the blparam file on because I have Mint on the same PC. After I copied the file onto another USB stick I was not able to reconnect to PP2 over the serial bus (or at least Putty wouldn't display anything). After rebooting PP2 it still wasn't showing anything but I knew things weren't too bad because I got an orange LED on PP2 and both ethernet lights were blinking. I rebooted the PC and now serial comms is working again.
Here is the boot log... looks like it's complaining about a bad CRC... The MAC address needs to be corrected somehow? I found it's present MAC address by aborting the boot and using "printenv" (output below). Looks like I need to copy the blparam file from PP1 to PP2 and update the MAC address... is that all? One problem I see is that when I do a ./blparam it shows a bunch of output in HEX... PP1 only shows text output. Not sure how to deal with that.
There are two blparam files:
Here's the output of printenv if I abort the boot process:
How do I go about correcting the MAC address and the other errors?
ps: Please send me your paypal address because I have to at least buy you a beer for all of this help.
Edited 7 time(s). Last edit at 02/10/2015 05:02PM by Waynosan.
Here is the boot log... looks like it's complaining about a bad CRC... The MAC address needs to be corrected somehow? I found it's present MAC address by aborting the boot and using "printenv" (output below). Looks like I need to copy the blparam file from PP1 to PP2 and update the MAC address... is that all? One problem I see is that when I do a ./blparam it shows a bunch of output in HEX... PP1 only shows text output. Not sure how to deal with that.
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16) U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM Total size 256MB 16bit width Flash: 0 kB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:128 MB *** Warning - bad CRC or NAND, using default environment CPU : Marvell Feroceon (Rev 1) CLOUD ENGINES BOARD (GUESSED): PP_V2 Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x100000, size 0x200000 Reading data from 0x2ff800 -- 100% complete. 2097152 bytes read: OK ## Booting image at 00800000 ... Image Name: Linux-2.6.22.18 Created: 2010-10-19 23:05:02 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1979140 Bytes = 1.9 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux............................................................................................................................ done, booting the kernel. [ 0.000000] Linux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010 [ 0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177 [ 0.000000] Machine: Feroceon-KW [ 0.000000] Using UBoot passing parameters structure [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] CPU0: D VIVT write-back cache [ 0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets [ 0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets [ 0.000000] Built 1 zonelists. Total pages: 65024 [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro [ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes) [ 0.000000] Console: colour dummy device 80x30 [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.010000] Memory: 256MB 0MB 0MB 0MB = 256MB total [ 0.010000] Memory: 255872KB available (3592K code, 253K data, 124K init) [ 0.250000] Mount-cache hash table entries: 512 [ 0.250000] CPU: Testing write buffer coherency: ok [ 0.250000] NET: Registered protocol family 16 [ 0.250000] [ 0.250000] CPU Interface [ 0.250000] ------------- [ 0.250000] SDRAM_CS0 ....base 00000000, size 256MB [ 0.250000] SDRAM_CS1 ....disable [ 0.250000] SDRAM_CS2 ....disable [ 0.250000] SDRAM_CS3 ....disable [ 0.250000] PEX0_MEM ....base e8000000, size 128MB [ 0.250000] PEX0_IO ....base f2000000, size 1MB [ 0.250000] INTER_REGS ....base f1000000, size 1MB [ 0.250000] NFLASH_CS ....base fa000000, size 2MB [ 0.250000] SPI_CS ....base f4000000, size 16MB [ 0.250000] BOOT_ROM_CS ....no such [ 0.250000] DEV_BOOTCS ....no such [ 0.250000] CRYPT_ENG ....base f0000000, size 2MB [ 0.250000] [ 0.250000] Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG Soc: 88F6281 A0 LE [ 0.250000] [ 0.250000] Detected Tclk 200000000 and SysClk 400000000 [ 0.250000] MV Buttons Device Load [ 0.250000] Marvell USB EHCI Host controller #0: c0652600 [ 0.750000] PEX0 interface detected no Link. [ 0.750000] PCI: bus0: Fast back to back transfers enabled [ 0.750000] SCSI subsystem initialized [ 0.750000] usbcore: registered new interface driver usbfs [ 0.750000] usbcore: registered new interface driver hub [ 0.750000] usbcore: registered new device driver usb [ 0.750000] NET: Registered protocol family 2 [ 0.760000] Time: kw_clocksource clocksource has been installed. [ 0.850000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.850000] TCP established hash table entries: 8192 (order: 4, 65536 bytes) [ 0.850000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes) [ 0.850000] TCP: Hash tables configured (established 8192 bind 8192) [ 0.850000] TCP reno registered [ 0.880000] RTC has been updated!!! [ 0.880000] RTC registered [ 0.880000] Use the XOR engines (acceleration) for enhancing the following functions: [ 0.880000] o RAID 5 Xor calculation [ 0.880000] o kernel memcpy [ 0.880000] o kenrel memzero [ 0.880000] Number of XOR engines to use: 4 [ 0.880000] cesadev_init(c00117b0) [ 0.880000] mvCesaInit: sessions=640, queue=64, pSram=f0000000 [ 0.880000] MV Buttons Driver Load [ 0.880000] squashfs: version 3.3 (2007/10/31) Phillip Lougher [ 0.880000] squashfs: LZMA suppport for slax.org by jro [ 0.880000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.880000] io scheduler noop registered [ 0.880000] io scheduler anticipatory registered (default) [ 0.900000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled [ 0.900000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 0.910000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize [ 0.920000] Loading Marvell Ethernet Driver: [ 0.920000] o Cached descriptors in DRAM [ 0.920000] o DRAM SW cache-coherency [ 0.930000] o Single RX Queue support - ETH_DEF_RXQ=0 [ 0.930000] o Single TX Queue support - ETH_DEF_TXQ=0 [ 0.940000] o TCP segmentation offload enabled [ 0.940000] o Receive checksum offload enabled [ 0.950000] o Transmit checksum offload enabled [ 0.950000] o Network Fast Processing (Routing) supported [ 0.960000] o Driver ERROR statistics enabled [ 0.960000] o Driver INFO statistics enabled [ 0.970000] o Proc tool API enabled [ 0.970000] o Rx descripors: q0=128 [ 0.970000] o Tx descripors: q0=532 [ 0.980000] o Loading network interface(s): [ 0.990000] o eth0, ifindex = 1, GbE port = 0 [ 0.990000] o eth1, ifindex = 2, GbE port = 1 [ 1.000000] [ 1.000000] mvFpRuleDb (cfdf6000): 2048 entries, 8192 bytes [ 1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI [ 1.010000] Copyright (c) 1999-2006 Intel Corporation. [ 1.020000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI [ 1.020000] e100: Copyright(c) 1999-2006 Intel Corporation [ 1.030000] [ 1.030000] Warning Sata is Powered Off [ 1.030000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ [ 1.040000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit) [ 1.050000] Scanning device for bad blocks [ 1.100000] Using static partition definition [ 1.110000] Creating 4 MTD partitions on "nand_mtd": [ 1.110000] 0x00000000-0x00100000 : "u-boot" [ 1.120000] 0x00100000-0x00500000 : "uImage" [ 1.120000] 0x00500000-0x02500000 : "root" [ 1.130000] 0x02500000-0x08000000 : "data" [ 1.130000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI [ 1.140000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1 [ 1.180000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100 [ 1.200000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 [ 1.200000] usb usb1: configuration #1 chosen from 1 choice [ 1.210000] hub 1-0:1.0: USB hub found [ 1.210000] hub 1-0:1.0: 1 port detected [ 1.330000] USB Universal Host Controller Interface driver v3.0 [ 1.610000] usb 1-1: new high speed USB device using ehci_marvell and address 2 [ 1.760000] usb 1-1: configuration #1 chosen from 1 choice [ 1.760000] hub 1-1:1.0: USB hub found [ 1.770000] hub 1-1:1.0: 4 ports detected [ 1.880000] usbcore: registered new interface driver usblp [ 1.880000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver [ 1.890000] Initializing USB Mass Storage driver... [ 1.890000] usbcore: registered new interface driver usb-storage [ 1.900000] USB Mass Storage support registered. [ 1.910000] mice: PS/2 mouse device common for all mice [ 1.910000] i2c /dev entries driver [ 1.910000] Linux telephony interface: v1.00 [ 1.920000] md: linear personality registered for level -1 [ 1.920000] md: raid0 personality registered for level 0 [ 1.930000] md: raid1 personality registered for level 1 [ 2.100000] raid6: int32x1 97 MB/s [ 2.270000] raid6: int32x2 114 MB/s [ 2.440000] raid6: int32x4 122 MB/s [ 2.610000] raid6: int32x8 110 MB/s [ 2.610000] raid6: using algorithm int32x4 (122 MB/s) [ 2.610000] md: raid6 personality registered for level 6 [ 2.620000] md: raid5 personality registered for level 5 [ 2.620000] md: raid4 personality registered for level 4 [ 2.630000] raid5: measuring checksumming speed [ 2.680000] arm4regs : 1084.000 MB/sec [ 2.730000] 8regs : 754.800 MB/sec [ 2.780000] 32regs : 900.000 MB/sec [ 2.780000] raid5: using function: arm4regs (1084.000 MB/sec) [ 2.790000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com [ 2.790000] dm_crypt using the OCF package. [ 2.800000] sdhci: Secure Digital Host Controller Interface driver [ 2.800000] sdhci: Copyright(c) Pierre Ossman [ 2.810000] usbcore: registered new interface driver usbhid [ 2.810000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver [ 2.820000] TCP cubic registered [ 2.820000] NET: Registered protocol family 1 [ 2.830000] NET: Registered protocol family 17 [ 2.830000] md: Autodetecting RAID arrays. [ 2.840000] md: autorun ... [ 2.840000] md: ... autorun DONE. [ 4.060000] Empty flash at 0x009ac208 ends at 0x009ac800 [ 8.800000] VFS: Mounted root (jffs2 filesystem) readonly. [ 8.800000] Freeing init memory: 124K init started: BusyBox v1.7.0 (2008-02-26 19:25:17 IST) starting pid 267, tty '': '/etc/init.d/rcS' [ 11.030000] eth0: link down [ 11.030000] eth0: started udhcpc (v1.7.0) started HWADDR 00 0x50 0x43 0x00 0x02 0x02 PIP0 2 PIP1 2 cat: can't open '/etc/resolv.conf': No such file or directory route: SIOCDELRT: No such process grep: /etc/resolv.conf: No such file or directory Sending discover... Sending discover... [ 14.680000] eth0: link up, full duplex, speed 1 Gbps Sending discover... Sending select for 192.168.1.41... Lease of 192.168.1.41 obtained, lease time 86400 HWADDR 00 0x50 0x43 0x00 0x02 0x02 PIP0 2 PIP1 2 route: SIOCDELRT: No such process Loading fs modules: [ 17.340000] fuse init (API version 7.8) Success [ 17.680000] ufsd: module license 'Commercial product' taints kernel. [ 17.700000] ufsd: driver (8.6, Jun 5 2013 10:00:32, LBD=ON, ioctl) loaded at bf040000 [ 17.700000] NTFS support included [ 17.700000] Hfs+/HfsX support included [ 17.700000] For 'CloudEngines_PogoPlug_2011-08-03' Loading rt3070sta.ko: [ 18.170000] rtusb init ---> [ 18.170000] usbcore: registered new interface driver rt2870 Success Loading tun.ko: [ 18.200000] tun: Universal TUN/TAP device driver, 1.6 [ 18.200000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Success Loading xce.ko: [ 18.240000] Cloud Engines XCE Init [Version: 2.0.5.10] [ 18.240000] XCE: CPU MEMORY MAP: [ 18.240000] XCE: -- 0x00001000 - 0xbeffffff (3055 MB) User Space Mappings [ 18.250000] XCE: -- 0xbf000000 - 0xbfffffff ( 16 MB) Kernel module space [ 18.260000] XCE: -- 0xc0000000 - 0xcfffffff ( 256 MB) Kernel direct-mapped ram [ 18.270000] XCE: -- 0xd0800000 - 0xe7ffffff ( 376 MB) Kernel vmalloc space [ 18.270000] XCE: -- 0xe8000000 - 0xfeffffff ( 367 MB) Kernel platform space [ 18.280000] XCE: CPU FEATURES: [ 18.280000] XCE: -- I Cache: enabled [ 18.290000] XCE: -- D Cache: enabled [ 18.290000] XCE: -- Branch Predict: enabled [ 18.300000] XCE: -- MMU: enabled [ 18.300000] XCE: -- Alignment Abort: enabled [ 18.310000] XCE: -- ICache Prefetch: enabled [ 18.310000] XCE: -- DCache Prefetch: enabled [ 18.310000] XCE: -- L2 Cache: enabled [ 18.320000] XCE: -- L2 Prefetch: disabled [ 18.320000] XCE: -- L2 Writethrough: disabled [ 18.330000] XCE: -- Write Allocate: disabled [ 18.330000] XCE: -- Streaming: disabled [ 18.340000] XCE: BLPARAMS: reading 2048 bytes @ a0000 [ 18.340000] XCE: BLPARAMS: -- Too many bit errors -- Can't correct! [ 18.350000] XCE: Loaded Property Size: 0 [ 18.350000] XCE: No board spec found matching boardid '<NULL>' -- Using 'PP_GTI:2.0' [ 18.360000] XCE: Current GPIO State: [ 18.370000] XCE: GPIO L OUT: 0xeff00000 [ 18.370000] XCE: GPIO L OE: 0xefffffff [ 18.370000] XCE: GPIO L BLINK: 0x00000000 [ 18.380000] XCE: GPIO L POL: 0x00000000 [ 18.380000] XCE: GPIO L IN: 0x00000080 [ 18.390000] XCE: GPIO H OUT: 0xfffeffff [ 18.390000] XCE: GPIO H OE: 0xfffc3fff [ 18.390000] XCE: GPIO H BLINK: 0x00008000 [ 18.400000] XCE: GPIO H POL: 0x00000000 [ 18.400000] XCE: GPIO H IN: 0x0002c000 [ 18.410000] XCE: Kernel thread starting PID: 398 Success Starting hbplug: Success starting pid 400, tty '': '/bin/sh' -sh-4.3# [ 20.380000] XCE: BLPARAMS: reading 2048 bytes @ a0000 [ 20.390000] XCE: BLPARAMS: -- Too many bit errors -- Can't correct! [ 25.630000] XCE: XCE: LED -> CONNECTED
There are two blparam files:
-sh-4.3# find -name blparam ./usr/sbin/blparam ./usr/local/cloudengines/bin/blparam
Here's the output of printenv if I abort the boot process:
CE>> printenv baudrate=115200 loads_echo=0 ipaddr=169.254.254.253 serverip=169.254.254.254 rootpath=/mnt/ARM_FS/ netmask=255.255.0.0 run_diag=yes stdin=serial stdout=serial stderr=serial console=console=ttyS0,115200 mainlineLinux=no CASset=min enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes MALLOC_len=1 ethprime=egiga0 netbsd_en=no vxworks_en=no bootargs_root=root=/dev/mtdblock2 ro bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000 ceboardver=PP_V2 bootdelay=3 disaMvPnp=no ethaddr=00:50:XX:XX:XX:XX ethmtu=1500 usb0Mode=host nandEcc=1bit ethact=egiga0 Environment size: 700/131068 bytes
How do I go about correcting the MAC address and the other errors?
ps: Please send me your paypal address because I have to at least buy you a beer for all of this help.
Edited 7 time(s). Last edit at 02/10/2015 05:02PM by Waynosan.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 10, 2015 09:00PM |
Admin Registered: 13 years ago Posts: 19,107 |
Waynosan,
Cool! you are back to Pogo OS.
> How do I go about correcting the MAC address and
> the other errors?
Looks like the default envs are OK. Power up again, interrupt serial console and at the prompt, printenv again, make sure the MAC address is correct and other envs are listed OK like before. You can use setenv to set the MAC address in serial console.
And then do
This way the checksum is rebuilt, and you won't see the CRC error anymore. And also blparm will work correctly after this.
> ps: Please send me your paypal address because I
> have to at least buy you a beer for all of this
> help.
Thanks :) but please PM Jeff and buy him a beer instead :) It must cost him some time and money hosting the forum for all of us.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 02/10/2015 09:04PM by bodhi.
Cool! you are back to Pogo OS.
> How do I go about correcting the MAC address and
> the other errors?
Looks like the default envs are OK. Power up again, interrupt serial console and at the prompt, printenv again, make sure the MAC address is correct and other envs are listed OK like before. You can use setenv to set the MAC address in serial console.
setenv ethaddr xx.xx.xx.xx
And then do
saveenv
This way the checksum is rebuilt, and you won't see the CRC error anymore. And also blparm will work correctly after this.
> ps: Please send me your paypal address because I
> have to at least buy you a beer for all of this
> help.
Thanks :) but please PM Jeff and buy him a beer instead :) It must cost him some time and money hosting the forum for all of us.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 02/10/2015 09:04PM by bodhi.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 10, 2015 11:19PM |
Registered: 9 years ago Posts: 29 |
OK, set the ethernet address and blparam does appear good. Correct IP address is being set. Here's the blparam output:
Still getting an orange LED up-front though and not seeing the device using the pogoplug webaccess software.
At this point, should I try to restart the Archlinux installation process? Also, re-flashing the mtd0 seems to have solved the connection problem, doesn't that indicate that there was indeed a problem with uboot? Just trying to make sense of why the Archlinux install failed before I try it again. Let me know if you know of a different process I should follow than the one I linked to in the OP.
Here's the serial log as of right now (yellow front LED). The only thing bad that I see is
cat: can't open '/etc/resolv.conf': No such file or directory
route: SIOCDELRT: No such process
PM to Jeff sent.
Thank you again!
Pogoplug:~$ cd /usr/local/cloudengines Pogoplug:/usr/local/cloudengines$ ls bin etc hbplug.conf Pogoplug:/usr/local/cloudengines$ cd bin Pogoplug:/usr/local/cloudengines/bin$ ls blparam hbplug rt3070sta.ko chkhfs hbplug_init tun.ko chkntfs hbusbpr udhcpc_ra0_init dcraw hbwd ufsd.ko dosfsck hfs.ko vfat.ko dropbear_init hfsplus.ko xce.ffpreset e2fsck mv_eth_tool xce.high.ffpreset fat.ko ntfs.ko xce.ko ffmpeg ntfs_3g xce.low.ffpreset fuse.ko ppsync xce.medium.ffpreset hbixc ppvseg xce.veryhigh.ffpreset Pogoplug:/usr/local/cloudengines/bin$ ./blparam baudrate=115200 loads_echo=0 ipaddr=169.254.254.253 serverip=169.254.254.254 rootpath=/mnt/ARM_FS/ netmask=255.255.0.0 run_diag=yes console=console=ttyS0,115200 CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=root=/dev/mtdblock2 ro bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(boo targs_root); bootm 0x800000 ceboardver=PP_V2 ethmtu=1500 usb0Mode=host nandEcc=1bit ethact=egiga0 stdin=serial stdout=serial stderr=serial mainlineLinux=no enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no bootdelay=3 disaMvPnp=no ethaddr=00:XX:XX:XX:XX:XX Pogoplug:/usr/local/cloudengines/bin$
Still getting an orange LED up-front though and not seeing the device using the pogoplug webaccess software.
At this point, should I try to restart the Archlinux installation process? Also, re-flashing the mtd0 seems to have solved the connection problem, doesn't that indicate that there was indeed a problem with uboot? Just trying to make sense of why the Archlinux install failed before I try it again. Let me know if you know of a different process I should follow than the one I linked to in the OP.
Here's the serial log as of right now (yellow front LED). The only thing bad that I see is
cat: can't open '/etc/resolv.conf': No such file or directory
route: SIOCDELRT: No such process
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16) U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM Total size 256MB 16bit width Flash: 0 kB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:128 MB CPU : Marvell Feroceon (Rev 1) CLOUD ENGINES BOARD: PP_V2 Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x100000, size 0x200000 Reading data from 0x2ff800 -- 100% complete. 2097152 bytes read: OK ## Booting image at 00800000 ... Image Name: Linux-2.6.22.18 Created: 2010-10-19 23:05:02 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1979140 Bytes = 1.9 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux............................................................................................. ............................... done, booting the kernel. [ 0.000000] Linux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010 [ 0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177 [ 0.000000] Machine: Feroceon-KW [ 0.000000] Using UBoot passing parameters structure [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] CPU0: D VIVT write-back cache [ 0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets [ 0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets [ 0.000000] Built 1 zonelists. Total pages: 65024 [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro [ 0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes) [ 0.000000] Console: colour dummy device 80x30 [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.010000] Memory: 256MB 0MB 0MB 0MB = 256MB total [ 0.010000] Memory: 255872KB available (3592K code, 253K data, 124K init) [ 0.250000] Mount-cache hash table entries: 512 [ 0.250000] CPU: Testing write buffer coherency: ok [ 0.250000] NET: Registered protocol family 16 [ 0.250000] [ 0.250000] CPU Interface [ 0.250000] ------------- [ 0.250000] SDRAM_CS0 ....base 00000000, size 256MB [ 0.250000] SDRAM_CS1 ....disable [ 0.250000] SDRAM_CS2 ....disable [ 0.250000] SDRAM_CS3 ....disable [ 0.250000] PEX0_MEM ....base e8000000, size 128MB [ 0.250000] PEX0_IO ....base f2000000, size 1MB [ 0.250000] INTER_REGS ....base f1000000, size 1MB [ 0.250000] NFLASH_CS ....base fa000000, size 2MB [ 0.250000] SPI_CS ....base f4000000, size 16MB [ 0.250000] BOOT_ROM_CS ....no such [ 0.250000] DEV_BOOTCS ....no such [ 0.250000] CRYPT_ENG ....base f0000000, size 2MB [ 0.250000] [ 0.250000] Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG Soc: 88F6281 A0 LE [ 0.250000] [ 0.250000] Detected Tclk 200000000 and SysClk 400000000 [ 0.250000] MV Buttons Device Load [ 0.250000] Marvell USB EHCI Host controller #0: c0652600 [ 0.750000] PEX0 interface detected no Link. [ 0.750000] PCI: bus0: Fast back to back transfers enabled [ 0.750000] SCSI subsystem initialized [ 0.750000] usbcore: registered new interface driver usbfs [ 0.750000] usbcore: registered new interface driver hub [ 0.750000] usbcore: registered new device driver usb [ 0.750000] NET: Registered protocol family 2 [ 0.760000] Time: kw_clocksource clocksource has been installed. [ 0.850000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.850000] TCP established hash table entries: 8192 (order: 4, 65536 bytes) [ 0.850000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes) [ 0.850000] TCP: Hash tables configured (established 8192 bind 8192) [ 0.850000] TCP reno registered [ 0.880000] RTC has been updated!!! [ 0.880000] RTC registered [ 0.880000] Use the XOR engines (acceleration) for enhancing the following functions: [ 0.880000] o RAID 5 Xor calculation [ 0.880000] o kernel memcpy [ 0.880000] o kenrel memzero [ 0.880000] Number of XOR engines to use: 4 [ 0.880000] cesadev_init(c00117b0) [ 0.880000] mvCesaInit: sessions=640, queue=64, pSram=f0000000 [ 0.880000] MV Buttons Driver Load [ 0.880000] squashfs: version 3.3 (2007/10/31) Phillip Lougher [ 0.880000] squashfs: LZMA suppport for slax.org by jro [ 0.880000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.880000] io scheduler noop registered [ 0.880000] io scheduler anticipatory registered (default) [ 0.900000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled [ 0.900000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 0.910000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize [ 0.920000] Loading Marvell Ethernet Driver: [ 0.920000] o Cached descriptors in DRAM [ 0.920000] o DRAM SW cache-coherency [ 0.930000] o Single RX Queue support - ETH_DEF_RXQ=0 [ 0.930000] o Single TX Queue support - ETH_DEF_TXQ=0 [ 0.940000] o TCP segmentation offload enabled [ 0.940000] o Receive checksum offload enabled [ 0.950000] o Transmit checksum offload enabled [ 0.950000] o Network Fast Processing (Routing) supported [ 0.960000] o Driver ERROR statistics enabled [ 0.960000] o Driver INFO statistics enabled [ 0.970000] o Proc tool API enabled [ 0.970000] o Rx descripors: q0=128 [ 0.970000] o Tx descripors: q0=532 [ 0.980000] o Loading network interface(s): [ 0.990000] o eth0, ifindex = 1, GbE port = 0 [ 0.990000] o eth1, ifindex = 2, GbE port = 1 [ 1.000000] [ 1.000000] mvFpRuleDb (cfdf6000): 2048 entries, 8192 bytes [ 1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI [ 1.010000] Copyright (c) 1999-2006 Intel Corporation. [ 1.020000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI [ 1.020000] e100: Copyright(c) 1999-2006 Intel Corporation [ 1.030000] [ 1.030000] Warning Sata is Powered Off [ 1.030000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ [ 1.040000] NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit) [ 1.050000] Scanning device for bad blocks [ 1.100000] Using static partition definition [ 1.110000] Creating 4 MTD partitions on "nand_mtd": [ 1.110000] 0x00000000-0x00100000 : "u-boot" [ 1.120000] 0x00100000-0x00500000 : "uImage" [ 1.120000] 0x00500000-0x02500000 : "root" [ 1.130000] 0x02500000-0x08000000 : "data" [ 1.130000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI [ 1.140000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1 [ 1.180000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100 [ 1.200000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 [ 1.200000] usb usb1: configuration #1 chosen from 1 choice [ 1.210000] hub 1-0:1.0: USB hub found [ 1.210000] hub 1-0:1.0: 1 port detected [ 1.330000] USB Universal Host Controller Interface driver v3.0 [ 1.610000] usb 1-1: new high speed USB device using ehci_marvell and address 2 [ 1.760000] usb 1-1: configuration #1 chosen from 1 choice [ 1.760000] hub 1-1:1.0: USB hub found [ 1.770000] hub 1-1:1.0: 4 ports detected [ 1.880000] usbcore: registered new interface driver usblp [ 1.880000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver [ 1.890000] Initializing USB Mass Storage driver... [ 1.890000] usbcore: registered new interface driver usb-storage [ 1.900000] USB Mass Storage support registered. [ 1.910000] mice: PS/2 mouse device common for all mice [ 1.910000] i2c /dev entries driver [ 1.910000] Linux telephony interface: v1.00 [ 1.920000] md: linear personality registered for level -1 [ 1.920000] md: raid0 personality registered for level 0 [ 1.930000] md: raid1 personality registered for level 1 [ 2.100000] raid6: int32x1 97 MB/s [ 2.270000] raid6: int32x2 114 MB/s [ 2.440000] raid6: int32x4 122 MB/s [ 2.610000] raid6: int32x8 110 MB/s [ 2.610000] raid6: using algorithm int32x4 (122 MB/s) [ 2.610000] md: raid6 personality registered for level 6 [ 2.620000] md: raid5 personality registered for level 5 [ 2.620000] md: raid4 personality registered for level 4 [ 2.630000] raid5: measuring checksumming speed [ 2.680000] arm4regs : 1071.600 MB/sec [ 2.730000] 8regs : 754.800 MB/sec [ 2.780000] 32regs : 900.000 MB/sec [ 2.780000] raid5: using function: arm4regs (1071.600 MB/sec) [ 2.790000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com [ 2.790000] dm_crypt using the OCF package. [ 2.800000] sdhci: Secure Digital Host Controller Interface driver [ 2.800000] sdhci: Copyright(c) Pierre Ossman [ 2.810000] usbcore: registered new interface driver usbhid [ 2.810000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver [ 2.820000] TCP cubic registered [ 2.820000] NET: Registered protocol family 1 [ 2.830000] NET: Registered protocol family 17 [ 2.830000] md: Autodetecting RAID arrays. [ 2.840000] md: autorun ... [ 2.840000] md: ... autorun DONE. [ 4.060000] Empty flash at 0x009ac208 ends at 0x009ac800 [ 8.800000] VFS: Mounted root (jffs2 filesystem) readonly. [ 8.800000] Freeing init memory: 124K init started: BusyBox v1.7.0 (2008-02-26 19:25:17 IST) starting pid 267, tty '': '/etc/init.d/rcS' [ 11.030000] eth0: link down [ 11.030000] eth0: started udhcpc (v1.7.0) started HWADDR 00 0x25 0x31 0x02 0x21 0x5c PIP0 33 PIP1 92 cat: can't open '/etc/resolv.conf': No such file or directory route: SIOCDELRT: No such process grep: /etc/resolv.conf: No such file or directory Sending discover... Sending discover... [ 14.780000] eth0: link up, full duplex, speed 1 Gbps Sending discover... Sending select for 192.168.1.21... Lease of 192.168.1.21 obtained, lease time 86400 HWADDR 00 0xXX 0xXX 0xXX 0xXX 0xXX PIP0 33 PIP1 92 route: SIOCDELRT: No such process Loading fs modules: [ 17.330000] fuse init (API version 7.8) Success [ 17.670000] ufsd: module license 'Commercial product' taints kernel. [ 17.690000] ufsd: driver (8.6, Jun 5 2013 10:00:32, LBD=ON, ioctl) loaded at bf040000 [ 17.690000] NTFS support included [ 17.690000] Hfs+/HfsX support included [ 17.690000] For 'CloudEngines_PogoPlug_2011-08-03' Loading rt3070sta.ko: [ 18.160000] rtusb init ---> [ 18.160000] usbcore: registered new interface driver rt2870 Success Loading tun.ko: [ 18.190000] tun: Universal TUN/TAP device driver, 1.6 [ 18.190000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Success Loading xce.ko: [ 18.230000] Cloud Engines XCE Init [Version: 2.0.5.10] [ 18.230000] XCE: CPU MEMORY MAP: [ 18.230000] XCE: -- 0x00001000 - 0xbeffffff (3055 MB) User Space Mappings [ 18.240000] XCE: -- 0xbf000000 - 0xbfffffff ( 16 MB) Kernel module space [ 18.250000] XCE: -- 0xc0000000 - 0xcfffffff ( 256 MB) Kernel direct-mapped ram [ 18.260000] XCE: -- 0xd0800000 - 0xe7ffffff ( 376 MB) Kernel vmalloc space [ 18.260000] XCE: -- 0xe8000000 - 0xfeffffff ( 367 MB) Kernel platform space [ 18.270000] XCE: CPU FEATURES: [ 18.270000] XCE: -- I Cache: enabled [ 18.280000] XCE: -- D Cache: enabled [ 18.280000] XCE: -- Branch Predict: enabled [ 18.290000] XCE: -- MMU: enabled [ 18.290000] XCE: -- Alignment Abort: enabled [ 18.300000] XCE: -- ICache Prefetch: enabled [ 18.300000] XCE: -- DCache Prefetch: enabled [ 18.300000] XCE: -- L2 Cache: enabled [ 18.310000] XCE: -- L2 Prefetch: disabled [ 18.310000] XCE: -- L2 Writethrough: disabled [ 18.320000] XCE: -- Write Allocate: disabled [ 18.320000] XCE: -- Streaming: disabled [ 18.330000] XCE: BLPARAMS: reading 2048 bytes @ a0000 [ 18.330000] XCE: Loaded Property Size: 2048 [ 18.340000] XCE: - 'ceboardver' -> 'PP_V2' [ 18.340000] XCE: No board spec found matching boardid 'PP_V2' -- Using 'PP_GTI:2.0' [ 18.350000] XCE: Current GPIO State: [ 18.350000] XCE: GPIO L OUT: 0xeff00000 [ 18.360000] XCE: GPIO L OE: 0xefffffff [ 18.360000] XCE: GPIO L BLINK: 0x00000000 [ 18.370000] XCE: GPIO L POL: 0x00000000 [ 18.370000] XCE: GPIO L IN: 0x00000080 [ 18.380000] XCE: GPIO H OUT: 0xfffeffff [ 18.380000] XCE: GPIO H OE: 0xfffc3fff [ 18.380000] XCE: GPIO H BLINK: 0x00008000 [ 18.390000] XCE: GPIO H POL: 0x00000000 [ 18.390000] XCE: GPIO H IN: 0x00024000 [ 18.400000] XCE: Kernel thread starting PID: 398 Success Starting hbplug: Success starting pid 400, tty '': '/bin/sh' -sh-4.3# [ 20.370000] XCE: BLPARAMS: reading 2048 bytes @ a0000 [ 20.380000] XCE: BLPARAMS: reading 2048 bytes @ a0800 [ 20.380000] XCE: BLPARAMS: reading 2048 bytes @ a1000 [ 20.390000] XCE: BLPARAMS: reading 2048 bytes @ a1800 [ 25.640000] XCE: XCE: LED -> CONNECTED [ 197.000000] usb 1-1.4: new high speed USB device using ehci_marvell and address 3 [ 197.220000] usb 1-1.4: configuration #1 chosen from 1 choice [ 197.230000] scsi0 : SCSI emulation for USB Mass Storage devices [ 202.240000] scsi 0:0:0:0: Direct-Access JetFlash Transcend 4GB 8.07 PQ: 0 ANSI: 2 [ 202.250000] sd 0:0:0:0: [sda] 7827456 512-byte hardware sectors (4008 MB) [ 202.250000] sd 0:0:0:0: [sda] Write Protect is off [ 202.260000] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 202.270000] sd 0:0:0:0: [sda] 7827456 512-byte hardware sectors (4008 MB) [ 202.270000] sd 0:0:0:0: [sda] Write Protect is off [ 202.280000] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 202.290000] sda: sda1 [ 202.300000] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 202.310000] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 202.500000] EXT3-fs: INFO: recovery required on readonly filesystem. [ 202.500000] EXT3-fs: write access will be enabled during recovery. [ 209.860000] kjournald starting. Commit interval 5 seconds [ 209.870000] EXT3-fs: recovery complete. [ 209.880000] EXT3-fs: mounted filesystem with ordered data mode. [ 210.060000] kjournald starting. Commit interval 5 seconds [ 210.070000] EXT3 FS on sda1, internal journal [ 210.070000] EXT3-fs: mounted filesystem with ordered data mode.
PM to Jeff sent.
Thank you again!
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 11, 2015 02:10AM |
Admin Registered: 13 years ago Posts: 19,107 |
Waynosan,
>
> At this point, should I try to restart the
> Archlinux installation process? Also, re-flashing
> the mtd0 seems to have solved the connection
> problem, doesn't that indicate that there was
> indeed a problem with uboot? Just trying to make
> sense of why the Archlinux install failed before I
> try it again. Let me know if you know of a
> different process I should follow than the one I
> linked to in the OP.
Your Arch installation was successful. There was nothing wrong with that u-boot installation. The only problem was systemd network related which is inside Arch Linux. After you reflashed mtd0, you went back to Pogo Linux OS, that's why the network connection is working.
I'm wondering why you want to use Arch but not Debian?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
>
> At this point, should I try to restart the
> Archlinux installation process? Also, re-flashing
> the mtd0 seems to have solved the connection
> problem, doesn't that indicate that there was
> indeed a problem with uboot? Just trying to make
> sense of why the Archlinux install failed before I
> try it again. Let me know if you know of a
> different process I should follow than the one I
> linked to in the OP.
Your Arch installation was successful. There was nothing wrong with that u-boot installation. The only problem was systemd network related which is inside Arch Linux. After you reflashed mtd0, you went back to Pogo Linux OS, that's why the network connection is working.
I'm wondering why you want to use Arch but not Debian?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 11, 2015 09:19AM |
Registered: 9 years ago Posts: 29 |
OK, I see.
I'm not married to Archlinux; it's just that there are the most examples for setting it up on the internet for at least some of what I want to do with it. Being a noob regarding this stuff I figured it would be the easiest way to approach it. My goals are:
I assume that Debian can probably do the same stuff but I get the impression that it would take more know-how than Archlinux.
ps: Any idea why I'm seeing the orange light on the device and I can't see it with the Pogoplug software? Not sure if I should be worrying about it at this point but if I end up implementing point 4 above then I probably should figure it out before proceeding.
I'm not married to Archlinux; it's just that there are the most examples for setting it up on the internet for at least some of what I want to do with it. Being a noob regarding this stuff I figured it would be the easiest way to approach it. My goals are:
- Serve files to my network without having to use the Popoplug software on my local PCs (I often have to "refresh" it to see my drives)
- Serve media files to my Raspberry Pi XBMC and tablet
- Run an automatic backup of select important directories to another hard drive
- (optional) Run the Pogoplug serivce so I can still access my music remotely through my Android phone. If this can be done without the Pogoplug service then even better.
- (stretch goal) Connect my multifunction Canon printer/scanner to it so I can use it from multiple PCs (It only has a USB connection). I know that the printing function should be easy but not sure if the scanning function will be as trivial.
I assume that Debian can probably do the same stuff but I get the impression that it would take more know-how than Archlinux.
ps: Any idea why I'm seeing the orange light on the device and I can't see it with the Pogoplug software? Not sure if I should be worrying about it at this point but if I end up implementing point 4 above then I probably should figure it out before proceeding.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 11, 2015 01:08PM |
Admin Registered: 13 years ago Posts: 19,107 |
Waynosan,
> I'm not married to Archlinux; it's just that there
> are the most examples for setting it up on the
> internet for at least some of what I want to do
> with it. Being a noob regarding this stuff I
> figured it would be the easiest way to approach
> it.
> I assume that Debian can probably do the same
> stuff but I get the impression that it would take
> more know-how than Archlinux.
True. There are more info and tutorial for Arch Linux ARM available at Arch site. It is well organized. OTOH, Debian ARM info are scattered. We are mainly a hacking forum here (i.e. get it to work). Things on your list are available too, in other general Debian forums. Except for the below task:
> [*] (optional) Run the Pogoplug serivce so I can
> still access my music remotely through my Android
> phone. If this can be done without the Pogoplug
> service then even better.
>
moonman at ALARM sitte has a well written procedure that allows you to run Pogo service in Arch, so it is a good choice to go with Arch for you.
> ps: Any idea why I'm seeing the orange light on
> the device and I can't see it with the Pogoplug
> software? Not sure if I should be worrying about
> it at this point but if I end up implementing
> point 4 above then I probably should figure it out
> before proceeding.
At this point, I would not worry about this, since you can run it from Arch as mentioned. For reference, I think this is an indicator about the Pogoplug service is not running yet, there is more reverse works need to be done to start the service.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/11/2015 01:24PM by bodhi.
> I'm not married to Archlinux; it's just that there
> are the most examples for setting it up on the
> internet for at least some of what I want to do
> with it. Being a noob regarding this stuff I
> figured it would be the easiest way to approach
> it.
> I assume that Debian can probably do the same
> stuff but I get the impression that it would take
> more know-how than Archlinux.
True. There are more info and tutorial for Arch Linux ARM available at Arch site. It is well organized. OTOH, Debian ARM info are scattered. We are mainly a hacking forum here (i.e. get it to work). Things on your list are available too, in other general Debian forums. Except for the below task:
> [*] (optional) Run the Pogoplug serivce so I can
> still access my music remotely through my Android
> phone. If this can be done without the Pogoplug
> service then even better.
>
moonman at ALARM sitte has a well written procedure that allows you to run Pogo service in Arch, so it is a good choice to go with Arch for you.
> ps: Any idea why I'm seeing the orange light on
> the device and I can't see it with the Pogoplug
> software? Not sure if I should be worrying about
> it at this point but if I end up implementing
> point 4 above then I probably should figure it out
> before proceeding.
At this point, I would not worry about this, since you can run it from Arch as mentioned. For reference, I think this is an indicator about the Pogoplug service is not running yet, there is more reverse works need to be done to start the service.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/11/2015 01:24PM by bodhi.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 11, 2015 07:07PM |
Registered: 9 years ago Posts: 29 |
bohdi,
Thank you so much again for your help. I was planning on perhaps following this procedure and using Jeff's uboot as listed here:
http://www.instructables.com/id/Linux-hints/step6/Pogoplug-V2/
Do you foresee any issues with this approach?
Again, you've helped more than enough so if you're done with this topic don't feel bad about not answering. All the best to you.
Thank you so much again for your help. I was planning on perhaps following this procedure and using Jeff's uboot as listed here:
http://www.instructables.com/id/Linux-hints/step6/Pogoplug-V2/
Do you foresee any issues with this approach?
Again, you've helped more than enough so if you're done with this topic don't feel bad about not answering. All the best to you.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 12, 2015 02:28AM |
Admin Registered: 13 years ago Posts: 19,107 |
Waynosan,
> http://www.instructables.com/id/Linux-hints/step6/
> Pogoplug-V2/
>
> Do you foresee any issues with this approach?
I would not use that approach. If you are going to run Arch, then you should use Arch u-boot and its installation procedure. But if you want to use a different u-boot, you can install my u-boot image later, after you got Arch running.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> http://www.instructables.com/id/Linux-hints/step6/
> Pogoplug-V2/
>
> Do you foresee any issues with this approach?
I would not use that approach. If you are going to run Arch, then you should use Arch u-boot and its installation procedure. But if you want to use a different u-boot, you can install my u-boot image later, after you got Arch running.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
samad
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 25, 2015 07:48AM |
Hi there,
Im having a similar issue - pogoplug won't show up on the network but the LED in front is green. network LEDs show activity.
Previously had arch on the device, and I tried following a step here to boot back into pogoplug software (which did not work)
http://mhassan.me/2012/06/27/swapping-between-pogoplug-original-and-custom-firmware/
The step was renaming uImage to uImage.hide
After many unsuccessful attempts to boot into either Arch or Pogoplug FS, I decided to reinstall arch. I was not getting any LED indicator in the front but ethernet LEDs were blinking.
I followed the guide here to reinstall arch http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3312&p=19207#p19207
Now, at least the front LED comes on, but still no network. I've even tried setting a static lease on my router for the Pogoplug's mac address.
It is an E02 V2 Gray model
Any tips? I do not have a serial cable, and would prefer to avoid getting one for now if I can (its on my wish list)
Im having a similar issue - pogoplug won't show up on the network but the LED in front is green. network LEDs show activity.
Previously had arch on the device, and I tried following a step here to boot back into pogoplug software (which did not work)
http://mhassan.me/2012/06/27/swapping-between-pogoplug-original-and-custom-firmware/
The step was renaming uImage to uImage.hide
After many unsuccessful attempts to boot into either Arch or Pogoplug FS, I decided to reinstall arch. I was not getting any LED indicator in the front but ethernet LEDs were blinking.
I followed the guide here to reinstall arch http://archlinuxarm.org/forum/viewtopic.php?f=18&t=3312&p=19207#p19207
Now, at least the front LED comes on, but still no network. I've even tried setting a static lease on my router for the Pogoplug's mac address.
It is an E02 V2 Gray model
Any tips? I do not have a serial cable, and would prefer to avoid getting one for now if I can (its on my wish list)
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 25, 2015 12:08PM |
Admin Registered: 13 years ago Posts: 19,107 |
@samad,
> Now, at least the front LED comes on, but still no
> network. I've even tried setting a static lease on
> my router for the Pogoplug's mac address.
Best way to recover without serial console in this situaton is to boot into a working rootfs, and then mount your Arch stick, examine it.
You can temporarily boot into Debian. Get the rootfs 3.16 from this thread, and use the version:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Now, at least the front LED comes on, but still no
> network. I've even tried setting a static lease on
> my router for the Pogoplug's mac address.
Best way to recover without serial console in this situaton is to boot into a working rootfs, and then mount your Arch stick, examine it.
You can temporarily boot into Debian. Get the rootfs 3.16 from this thread, and use the version:
Quote
Updated 02 Sept 2014:
Rootfs Debian-3.16.0-kirkwood-tld-2
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 25, 2015 04:20PM |
Registered: 11 years ago Posts: 165 |
Sorry, I didn't read this thread but wanted to throw out one reason why this happened - Pogoplug v2 doesn't show up on LAN after Archlinux install -to one of my blog readers.
The Pogoplug E02 uBoot was from Jeff Doozan, but he followed the re-installation instructions from archlinuxarm.org which explicitely instructs the user to format the USB drive as EXT4 (and not EXT3 as expected by the uBoot env). The uBoot from archlinuxarn.org, I guess, detects the fstype dynamically and supports EXT4.
The reinstallation instructions I'm referring to: http://archlinuxarm.org/support/reinstallation
Just wanted to throw it out there for future readers (and you @samad).
The Pogoplug E02 uBoot was from Jeff Doozan, but he followed the re-installation instructions from archlinuxarm.org which explicitely instructs the user to format the USB drive as EXT4 (and not EXT3 as expected by the uBoot env). The uBoot from archlinuxarn.org, I guess, detects the fstype dynamically and supports EXT4.
The reinstallation instructions I'm referring to: http://archlinuxarm.org/support/reinstallation
Just wanted to throw it out there for future readers (and you @samad).
|
samad
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install February 26, 2015 12:24AM |
thank you both.
i was able to get the pogoplug to boot back into arch linux using grayman4hire's link. the difference between this step and what i did last night to reinstall was changing filesystem to ext4 (i tried ext3 yesterday)
ext4 allowed me to get back into my pogoplug via ssh and it shows up on the network. ext3 failed at some point, but i didn't have logs (reinstalled on same flash drive)
i may try to install debian on another flash drive using your link bodhi so i can hotswap between the two, but for now my issue is solved. can finally migrate all my content off pogoplug cloud.
thanks agian
i was able to get the pogoplug to boot back into arch linux using grayman4hire's link. the difference between this step and what i did last night to reinstall was changing filesystem to ext4 (i tried ext3 yesterday)
ext4 allowed me to get back into my pogoplug via ssh and it shows up on the network. ext3 failed at some point, but i didn't have logs (reinstalled on same flash drive)
i may try to install debian on another flash drive using your link bodhi so i can hotswap between the two, but for now my issue is solved. can finally migrate all my content off pogoplug cloud.
thanks agian
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 13, 2015 10:57AM |
Registered: 9 years ago Posts: 29 |
Additional quick question... if I want to move ALARM from the slow USB flash drive that I'm currently using to a small USB HD that I have are there any modifications necessary? I was able to copy (using cp) ALARM from one USB flash drive onto another without issues (ALARM booted up and I was able to SSH into it w/o problems), but when I did the same using a USB HD as the destination then I'm not able to connect to the pogoplug/ALARM.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 13, 2015 03:48PM |
Admin Registered: 13 years ago Posts: 19,107 |
@Waynosan,
You need to verify these:
- Check if you have used the copy command cp -aR while logged in as root.
- After cloning the rootfs, check udev rules files:
http://forum.doozan.com/read.php?2,18007,18008#msg-18008
Also, if the USB flash drive is plugged in, u-boot envs should be modified to boot with both drives attached.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/13/2015 04:05PM by bodhi.
You need to verify these:
- Check if you have used the copy command cp -aR while logged in as root.
- After cloning the rootfs, check udev rules files:
http://forum.doozan.com/read.php?2,18007,18008#msg-18008
Also, if the USB flash drive is plugged in, u-boot envs should be modified to boot with both drives attached.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/13/2015 04:05PM by bodhi.
|
TEN
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 16, 2015 08:15PM |
Thanks for this thread!
Documenting for others who might end up in similar situations (when trying to get their device to boot anything from USB):
With yet another black Pogoplug E02 mislabelled POGO-P24,
I had also stepped into the "death trap" that http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray has become, while looking good at first glance:
Fortunately bodhi pointed out that "If you ran this recently, this procedure installed the Arch new u-boot. It was setup to load uImage only, and won't try to detect uInitrd (which Debian rootfs needs). So that was probably why you could not boot with Debian rootfs."
With no other ARM around, to the rescue I did this on Ubuntu 14.04 LTS (after sudo passwd root) with a new USB stick:
Now from this working stage (in Arch only), to avoid further pitfalls, how do I most safely
Documenting for others who might end up in similar situations (when trying to get their device to boot anything from USB):
With yet another black Pogoplug E02 mislabelled POGO-P24,
I had also stepped into the "death trap" that http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray has become, while looking good at first glance:
From this point onward, even with a Debian FDT rootfs USB stick (i.e. worse than by Waynosan's account), the front LED stayed dark all the time (as if it were bricked) while there is some flicker from the rear LAN green&amber LEDs (only the latter staying on if a USB stick is plugged), but no DHCP let alone sshd anymore.Quote
ssh root@192.168.2.110
root@192.168.2.110's password:
-bash-3.2# killall hbwd
-bash-3.2# cd /tmp
-bash-3.2# wget http://archlinuxarm.org/os/armv5te/boot/pogo_e02/pogo_e02.sh
Connecting to archlinuxarm.org (50.116.36.110:80)
pogo_e02.sh 100% |*******************************| 2239 --:--:-- ETA
-bash-3.2# chmod +x pogo_e02.sh
-bash-3.2# ./pogo_e02.sh
Downloading flash utilities..
blparam [OK]
flash_erase [OK]
fw_printenv [OK]
nanddump [OK]
nandwrite [OK]
Downloading U-Boot and environment..
uboot-pogo_e02.kwb [OK]
uboot-pogo_e02.env [OK]
Installing..
saving MAC address [00:25:31:02:2C:CE]
erasing U-Boot NAND [OK]
erasing environment [OK]
writing U-Boot [OK]
writing environment [OK]
Validating..
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
checking U-Boot [OK]
checking environment [OK]
setting MAC [OK]
U-Boot has been installed successfully.
-bash-3.2# /sbin/reboot
Fortunately bodhi pointed out that "If you ran this recently, this procedure installed the Arch new u-boot. It was setup to load uImage only, and won't try to detect uInitrd (which Debian rootfs needs). So that was probably why you could not boot with Debian rootfs."
With no other ARM around, to the rescue I did this on Ubuntu 14.04 LTS (after sudo passwd root) with a new USB stick:
This created (after several minutes wait on umount!) a bootable Arch at last - probably the only thing this "new" U-Boot does boot.Quote
root
apt-get install bsdtar
umount /media/sdl1
mke2fs -j /dev/sdl1
mount /dev/sdl1 /media/sdl1
cd /media/sdl1
wget http://archlinuxarm.org/os/ArchLinuxARM-kirkwood-latest.tar.gz
bsdtar -xpf ArchLinuxARM-kirkwood-latest.tar.gz
cd
umount /media/sdl1
sync
Now from this working stage (in Arch only), to avoid further pitfalls, how do I most safely
- ensure that there is a fallback to the built-in system & Busybox shell again (in case of missing or unreadable USB)
- permanently disable hwnd in there so it can't phone home to lock me out in any unexpected update (similar to commenting out "/etc/init.d/hbmgr.sh start" from /etc/init.d/rcS per http://ahsoftware.de/dockstar/)
- get the most versatile, reliable U-Boot (presumably http://forum.doozan.com/read.php?3,12381 or should http://projects.doozan.com/uboot/ do?) that is able to launch either of Arch, Cloud Engines or Debian up to jessie on Kernel 3.18 from http://forum.doozan.com/read.php?2,12096 - and provide a netconsole for emergencies?
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 16, 2015 09:17PM |
Admin Registered: 13 years ago Posts: 19,107 |
TEN,
Yes, and set up netconsole right away, especially with no serial console set up. Furthermore, with this new u-boot, you will have the LED flashing correctly in the boot sequence, so the quick visual indicator is available (most of the time, it is enough to tell that something went wrong by looking at the LED light).
I've also kept the option for booting Arch in u-boot envs. So it will work by just plugging in the Arch rootfs and boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/16/2015 09:30PM by bodhi.
Yes, and set up netconsole right away, especially with no serial console set up. Furthermore, with this new u-boot, you will have the LED flashing correctly in the boot sequence, so the quick visual indicator is available (most of the time, it is enough to tell that something went wrong by looking at the LED light).
I've also kept the option for booting Arch in u-boot envs. So it will work by just plugging in the Arch rootfs and boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/16/2015 09:30PM by bodhi.
|
TEN
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 02:51AM |
>
> Yes, and set up netconsole right away, especially with no serial console set up. Furthermore, with this new u-boot,
> you will have the LED flashing correctly in the boot sequence, so the quick visual indicator is available
> (most of the time, it is enough to tell that something went wrong by looking at the LED light).
However none of the utilities needed (fw_printenv, flash_erase, nandwrite) are in Arch by default.
Should I use those mountable from /usr/bin under mount /dev/mtdblock2 /media/nand -t jffs2 -o noatime, or rather
> I've also kept the option for booting Arch in u-boot envs. So it will work by just plugging in the Arch rootfs and boot.
Bootable "out of the box", i.e. no particular setup needed for Arch, nor for recent FDT Debian, and it will also fall back into the internal, original OS if there is no USB media?
Or will I need to make changes (in spite of the now jessie / 3.18 kernel thread) as Section C of the above U-Boot thread still says "to boot FDT kernel (starting 3.17), please see the kernel 3.17 thread (Updated 26 Oct 2014) section 4a for instruction on how to modify u-boot envs further in order to boot kernel 3.17 and later. The default u-boot envs for FDT kernel will be released in the near future" ?
>
> Yes, and set up netconsole right away, especially with no serial console set up. Furthermore, with this new u-boot,
> you will have the LED flashing correctly in the boot sequence, so the quick visual indicator is available
> (most of the time, it is enough to tell that something went wrong by looking at the LED light).
However none of the utilities needed (fw_printenv, flash_erase, nandwrite) are in Arch by default.
Should I use those mountable from /usr/bin under mount /dev/mtdblock2 /media/nand -t jffs2 -o noatime, or rather
... i.e. is the process you describe for installing your U-Boot known to work for Pogo E02 from within Arch just as well (while "its" U-Boot won't let me boot anything else) ?Quote
pacman -S uboot-env mtd-utils
Packages (2) mtd-utils-1.5.1-1 uboot-tools-2015.01-1
> I've also kept the option for booting Arch in u-boot envs. So it will work by just plugging in the Arch rootfs and boot.
Bootable "out of the box", i.e. no particular setup needed for Arch, nor for recent FDT Debian, and it will also fall back into the internal, original OS if there is no USB media?
Or will I need to make changes (in spite of the now jessie / 3.18 kernel thread) as Section C of the above U-Boot thread still says "to boot FDT kernel (starting 3.17), please see the kernel 3.17 thread (Updated 26 Oct 2014) section 4a for instruction on how to modify u-boot envs further in order to boot kernel 3.17 and later. The default u-boot envs for FDT kernel will be released in the near future" ?
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 04:22AM |
Admin Registered: 13 years ago Posts: 19,107 |
@TE,
> However none of the utilities needed (fw_printenv,
> flash_erase, nandwrite) are in Arch by default.
> Should I use those mountable from /usr/bin under
> mount /dev/mtdblock2 /media/nand -t jffs2 -o
> noatime, or rather
>
> installing your U-Boot known to work for Pogo E02
> from within Arch just as well (while "its"
> U-Boot won't let me boot anything else) ?
It is the same u-boot-tools and mtd-utils packages that need to be installed to provide those utilities whether in Arch or Debian. (in Debian: apt-get u-boot-tools mtd-utils).
>
> > I've also kept the option for booting Arch in
> u-boot envs. So it will work by just plugging in
> the Arch rootfs and boot.
>
> Bootable "out of the box", i.e. no particular
> setup needed for Arch, nor for recent FDT Debian,
> and it will also fall back into the internal,
> original OS if there is no USB media?
No. There is no Pogo OS consideration in neither u-boot. That's something you need to take care of afterward.
> Or will I need to make changes
Yes, you will need to know which type of rootfs that you will run, FDT or non-FDT, and setup u-boot envs according to the instruction. Remember, this installation procedure is manual, not a script like Arch's. So "plugging it in" means that the envs needed to be set up before that it will boot an appropriate rootfs. Sorry, it's not really plug-and-play for both systems :)
The bottom line is: if you intend to run Arch, never Debian then perhaps you should stay with Arch's u-boot (it has a very nice setup and tailored to Arch rootfs). OTOH, if you need netconsole, SNTP, and other minor capabilities only exist in this image, and perhaps want to boot a mix of Arch, Debian, OpenWRT, or Fedora then it is more appropriate to use this u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 4 time(s). Last edit at 03/17/2015 04:32AM by bodhi.
> However none of the utilities needed (fw_printenv,
> flash_erase, nandwrite) are in Arch by default.
> Should I use those mountable from /usr/bin under
> mount /dev/mtdblock2 /media/nand -t jffs2 -o
> noatime, or rather
>
> ... i.e. is the process you describe forQuote
pacman -S uboot-env mtd-utils
Packages (2)
> mtd-utils-1.5.1-1 uboot-tools-2015.01-1
> installing your U-Boot known to work for Pogo E02
> from within Arch just as well (while "its"
> U-Boot won't let me boot anything else) ?
It is the same u-boot-tools and mtd-utils packages that need to be installed to provide those utilities whether in Arch or Debian. (in Debian: apt-get u-boot-tools mtd-utils).
>
> > I've also kept the option for booting Arch in
> u-boot envs. So it will work by just plugging in
> the Arch rootfs and boot.
>
> Bootable "out of the box", i.e. no particular
> setup needed for Arch, nor for recent FDT Debian,
> and it will also fall back into the internal,
> original OS if there is no USB media?
No. There is no Pogo OS consideration in neither u-boot. That's something you need to take care of afterward.
> Or will I need to make changes
Yes, you will need to know which type of rootfs that you will run, FDT or non-FDT, and setup u-boot envs according to the instruction. Remember, this installation procedure is manual, not a script like Arch's. So "plugging it in" means that the envs needed to be set up before that it will boot an appropriate rootfs. Sorry, it's not really plug-and-play for both systems :)
The bottom line is: if you intend to run Arch, never Debian then perhaps you should stay with Arch's u-boot (it has a very nice setup and tailored to Arch rootfs). OTOH, if you need netconsole, SNTP, and other minor capabilities only exist in this image, and perhaps want to boot a mix of Arch, Debian, OpenWRT, or Fedora then it is more appropriate to use this u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 4 time(s). Last edit at 03/17/2015 04:32AM by bodhi.
|
TEN
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 07:28AM |
Just wondering how to do this from Arch with minimal risk, since that's an E02 on which, as the Great Bodhi writes, ;) at every glitch it's "JTAG time".Quote
bodhi
There is no Pogo OS consideration in neither u-boot. That's something you need to take care of afterward.
The fallback to the built-in OS (as provided by Jeff's installer IIRC when the USB was unplugged) always comes in handy as the partition's there anyway, and can only be used for this or another rescue system.
BTW there is no /dev/mtdblock2 on E02 even after modprobe mtdblocks, so I had to install the tools via pacman anyway.
I have had some trouble finding feasible "revert" instructions from Arch to E02 (as are offered for several other platforms) to start over from the interal OS though.
Anyhow wouldn't your U-Boot preferentially be deployed through an installer like Jeff's or Arch's in the first place?Quote
you will need to know which type of rootfs that you will run, FDT or non-FDT, and setup u-boot envs according to the instruction. Remember, this installation procedure is manual, not a script like Arch's. So "plugging it in" means that the envs needed to be set up before that it will boot an appropriate rootfs. Sorry, it's not really plug-and-play for both systems :)
Your kernel thread might actually limit the reference to usable (back to 2009-2011) ones to "non-stock" U-Boots as I understand a replacement over the factory one is always needed to boot from anything but NAND.
Ideally, anything with a fallback to NAND (i.e. some usable shell) after attempting to boot from the widest possible variety of USB media will do, and hopefully be installable from Arch now as well.Quote
if you intend to run Arch, never Debian then perhaps you should stay with Arch's u-boot (it has a very nice setup and tailored to Arch rootfs). OTOH, if you need netconsole, SNTP, and other minor capabilities only exist in this image, and perhaps want to boot a mix of Arch, Debian, OpenWRT, or Fedora then it is more appropriate to use this u-boot.
|
TEN
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 02:15PM |
BTW the latest Arch (or its http://os.archlinuxarm.org/os/armv5te/boot/pogo_e02/uboot-pogo_e02.env already) doesn't seem to get the NAND partitions right (booted systems sees only 2), which might complicate U-Boot replacement:
http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637&p=45984#p45984
I also doubt the revert instructions at http://myownhomeserver.com/2012/11/how-to-make-a-cheap-home-server-using-a-pogoplug-v2/#li-comment-202 really do apply to Pogoplug V2.
http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637&p=45984#p45984
I also doubt the revert instructions at http://myownhomeserver.com/2012/11/how-to-make-a-cheap-home-server-using-a-pogoplug-v2/#li-comment-202 really do apply to Pogoplug V2.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 03:21PM |
Admin Registered: 13 years ago Posts: 19,107 |
@TEN,
> Just wondering how to do
> this from Arch with minimal risk
It is minimized if the instruction is followed without any modification. Usually we get into trouble thinking something is equivalent and tweak the instruction just a bit :) with boot loader installation, it is best to do exactly (copy/paste) as the instruction states. And also, if you post the entire log of installation here before rebooting then I'd say the risk is very small.
>
> The fallback to the built-in OS (as provided by
> Jeff's installer IIRC when the USB was unplugged)
> always comes in handy as the partition's there
> anyway, and can only be used for this or another
> rescue system.
>
Jeff and davygravy have released rescue systems here in this forum. Also Arch has new rescue system, too. IMO, that's a better option than using stock OS for that purpose.
> BTW there is no /dev/mtdblock2 on E02 even after
> modprobe mtdblocks, so I had to install the tools
> via pacman anyway.
Arch u-boot went completely modern, and the mtds were redefined as 2 mtds: 0 and 1. This actually is what I would do for my own boxes to store kernel and rootfs. But for general consumption, I'd like to keep them the same as before so that users can decide. I think each of us has our own needs, if someone understands NANDs and wants to use it for rescue/rootfs/kernel then changing the definition is very easy to do anyway.
> Anyhow wouldn't your U-Boot
> preferentially be deployed through an installer
> like Jeff's or Arch's in the first place?
Yes. But I need free time to do it :) It will take a lot of time to test.
> Your kernel thread might actually limit the
> reference to usable (back to 2009-2011)
This is only a conservative estimate. The kernel actually would work with any u-boot that has USB support. But some stock u-boot does not have USB support. Even without USB, if it has tftp then it would work that way too..
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Just wondering how to do
> this from Arch with minimal risk
It is minimized if the instruction is followed without any modification. Usually we get into trouble thinking something is equivalent and tweak the instruction just a bit :) with boot loader installation, it is best to do exactly (copy/paste) as the instruction states. And also, if you post the entire log of installation here before rebooting then I'd say the risk is very small.
>
> The fallback to the built-in OS (as provided by
> Jeff's installer IIRC when the USB was unplugged)
> always comes in handy as the partition's there
> anyway, and can only be used for this or another
> rescue system.
>
Jeff and davygravy have released rescue systems here in this forum. Also Arch has new rescue system, too. IMO, that's a better option than using stock OS for that purpose.
> BTW there is no /dev/mtdblock2 on E02 even after
> modprobe mtdblocks, so I had to install the tools
> via pacman anyway.
Arch u-boot went completely modern, and the mtds were redefined as 2 mtds: 0 and 1. This actually is what I would do for my own boxes to store kernel and rootfs. But for general consumption, I'd like to keep them the same as before so that users can decide. I think each of us has our own needs, if someone understands NANDs and wants to use it for rescue/rootfs/kernel then changing the definition is very easy to do anyway.
> Anyhow wouldn't your U-Boot
> preferentially be deployed through an installer
> like Jeff's or Arch's in the first place?
Yes. But I need free time to do it :) It will take a lot of time to test.
> Your kernel thread might actually limit the
> reference to usable (back to 2009-2011)
This is only a conservative estimate. The kernel actually would work with any u-boot that has USB support. But some stock u-boot does not have USB support. Even without USB, if it has tftp then it would work that way too..
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 03:34PM |
Registered: 11 years ago Posts: 165 |
FYI - I do not currently recommend the archlinuxarm uboot for the E02. Either use Jeff's or Bodhi.
There are a few minor bugs with the archlinuxarm uboot, mainly netconsole not working as expected (no preboot) and you will not be able to boot the default Pogoplug OS because the uboot is missing the fsload needed to chainload the original uboot.
Not supporting Debian by default is a new one for me, so another reason not to use it.
Edited 2 time(s). Last edit at 03/17/2015 03:39PM by grayman4hire.
There are a few minor bugs with the archlinuxarm uboot, mainly netconsole not working as expected (no preboot) and you will not be able to boot the default Pogoplug OS because the uboot is missing the fsload needed to chainload the original uboot.
Not supporting Debian by default is a new one for me, so another reason not to use it.
Edited 2 time(s). Last edit at 03/17/2015 03:39PM by grayman4hire.
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 03:46PM |
Admin Registered: 13 years ago Posts: 19,107 |
grayman4hire,
> There are a few minor bugs with the archlinuxarm
> uboot, mainly netconsole not working as expected
> (no preboot) and you will not be able to boot the
> default Pogoplug OS because the uboot is missing
> the fsload needed to chainload the original
> uboot.
>
> Not supporting Debian by default is a new one for
> me, so another reason not to use it.
Thanks for mentioning it! jffs2 fsload/fsls was patched in my release to keep it working. I consider it a minor improvement (because of ubifs is better), but for someone who needs to run stock OS it is indeed a big deal.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> There are a few minor bugs with the archlinuxarm
> uboot, mainly netconsole not working as expected
> (no preboot) and you will not be able to boot the
> default Pogoplug OS because the uboot is missing
> the fsload needed to chainload the original
> uboot.
>
> Not supporting Debian by default is a new one for
> me, so another reason not to use it.
Thanks for mentioning it! jffs2 fsload/fsls was patched in my release to keep it working. I consider it a minor improvement (because of ubifs is better), but for someone who needs to run stock OS it is indeed a big deal.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
TEN
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 03:47PM |
bodhi Wrote:
-------------------------------------------------------
> > Just wondering how to do this from Arch with minimal risk
>
> It is minimized if the instruction is followed without any modification.
Well, the mod is Arch's not mine in this case. ;)
> > The fallback to the built-in OS (as provided by Jeff's installer IIRC when the USB was unplugged)
> > always comes in handy as the partition's there anyway, and can only be used for this or another rescue system.
> Jeff and davygravy have released rescue systems here in this forum. Also Arch has new rescue system, too.
> IMO, that's a better option than using stock OS for that purpose.
Stock OS of course has the benefit of "Just Being There" already.
> > BTW there is no /dev/mtdblock2 on E02 even after modprobe mtdblocks
> > the latest Arch (or its http://os.archlinuxarm.org/os/armv5te/boot/pogo_e02/uboot-pogo_e02.env already)
> > doesn't seem to get the NAND partitions right (booted systems sees only 2),
> > which might complicate U-Boot replacement:
> > http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637&p=45984#p45984
> Arch u-boot went completely modern, and the mtds were redefined as 2 mtds: 0 and 1.
However this isn't what's actually found on the NAND at that point (as even the Arch U-Boot installer -hopefully/fortunately- would not reformat the original partitions):
Accordingly mount /dev/mtdblock1 takes minutes to return, filling dmesg with scary errors of alleged NAND brokenness.
> This actually is what I would do for my own boxes to store kernel and rootfs.
I also recall the Emdebian idea in the early days, but even /boot on NAND never seems to have become commonplace.
> The kernel actually would work with any u-boot that has USB support.
> But some stock u-boot does not have USB support.
So which is the elusive "section 4a" that actually applies to your jessie build,
and what would boot back into Stock (or a replacement rescue system) from where I am now?
> Even without USB, if it has tftp then it would work that way too.
Does stock U-Boot have that? Could be a new avenue to unbricking (e.g. got a DockStar dead after power outage, but then again that might suffer from NAND corruption needing JTAG indeed) with no wires other than Ethernet...
-------------------------------------------------------
> > Just wondering how to do this from Arch with minimal risk
>
> It is minimized if the instruction is followed without any modification.
Well, the mod is Arch's not mine in this case. ;)
> > The fallback to the built-in OS (as provided by Jeff's installer IIRC when the USB was unplugged)
> > always comes in handy as the partition's there anyway, and can only be used for this or another rescue system.
> Jeff and davygravy have released rescue systems here in this forum. Also Arch has new rescue system, too.
> IMO, that's a better option than using stock OS for that purpose.
Stock OS of course has the benefit of "Just Being There" already.
> > BTW there is no /dev/mtdblock2 on E02 even after modprobe mtdblocks
> > the latest Arch (or its http://os.archlinuxarm.org/os/armv5te/boot/pogo_e02/uboot-pogo_e02.env already)
> > doesn't seem to get the NAND partitions right (booted systems sees only 2),
> > which might complicate U-Boot replacement:
> > http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637&p=45984#p45984
> Arch u-boot went completely modern, and the mtds were redefined as 2 mtds: 0 and 1.
However this isn't what's actually found on the NAND at that point (as even the Arch U-Boot installer -hopefully/fortunately- would not reformat the original partitions):
Accordingly mount /dev/mtdblock1 takes minutes to return, filling dmesg with scary errors of alleged NAND brokenness.
> This actually is what I would do for my own boxes to store kernel and rootfs.
I also recall the Emdebian idea in the early days, but even /boot on NAND never seems to have become commonplace.
> The kernel actually would work with any u-boot that has USB support.
> But some stock u-boot does not have USB support.
So which is the elusive "section 4a" that actually applies to your jessie build,
and what would boot back into Stock (or a replacement rescue system) from where I am now?
> Even without USB, if it has tftp then it would work that way too.
Does stock U-Boot have that? Could be a new avenue to unbricking (e.g. got a DockStar dead after power outage, but then again that might suffer from NAND corruption needing JTAG indeed) with no wires other than Ethernet...
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 03:54PM |
Admin Registered: 13 years ago Posts: 19,107 |
TEN,
> Well, the mod is Arch's not mine in this case. ;)
:))
> Stock OS of course has the benefit of "Just Being
> There" already.
Yes. You can use graymanforhire's instruction about how to boot back to stock Pogo OS from the new u-boot.
> However this isn't what's actually found on the
> NAND at that point (as even the Arch U-Boot
> installer -hopefully/fortunately- would not
> reformat the original partitions):
> Accordingly mount /dev/mtdblock1 takes minutes to
> return, filling dmesg with scary errors of alleged
> NAND brokenness.
I think they were left alone intact. If you redefine them then they will be usable.
> Does stock U-Boot have that? Could be a new avenue
> to unbricking (e.g. got a DockStar dead after
> power outage, but then again that might suffer
> from NAND corruption needing JTAG indeed) with no
> wires other than Ethernet...
Yes. The stock Pogo E02 has tftp. But you will need netconsole or serial console to get to it (and if u-boot was not corrupted).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 03/17/2015 04:01PM by bodhi.
> Well, the mod is Arch's not mine in this case. ;)
:))
> Stock OS of course has the benefit of "Just Being
> There" already.
Yes. You can use graymanforhire's instruction about how to boot back to stock Pogo OS from the new u-boot.
> However this isn't what's actually found on the
> NAND at that point (as even the Arch U-Boot
> installer -hopefully/fortunately- would not
> reformat the original partitions):
> Accordingly mount /dev/mtdblock1 takes minutes to
> return, filling dmesg with scary errors of alleged
> NAND brokenness.
I think they were left alone intact. If you redefine them then they will be usable.
> Does stock U-Boot have that? Could be a new avenue
> to unbricking (e.g. got a DockStar dead after
> power outage, but then again that might suffer
> from NAND corruption needing JTAG indeed) with no
> wires other than Ethernet...
Yes. The stock Pogo E02 has tftp. But you will need netconsole or serial console to get to it (and if u-boot was not corrupted).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 03/17/2015 04:01PM by bodhi.
|
TEN
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 04:02PM |
grayman4hire Wrote:
-------------------------------------------------------
> I do not currently recommend the archlinuxarm uboot for the E02.
Sadly (as you've seen in the forum over there) http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray gave no such advance warning. ;(
> Either use Jeff's or Bodhi.
> There are a few minor bugs with the archlinuxarm uboot, mainly netconsole not working as expected
> (no preboot) and you will not be able to boot the default Pogoplug OS because the uboot is missing
> the fsload needed to chainload the original uboot.
So I understand it could be replaced with bodhi's while booted into the working Arch (after fixing /etc/fw_env.config at least, or better yet reflecting all 4 mtds as they are to properly nanddump and disable hbmgr.sh as well, in http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637)?
> Not supporting Debian by default is a new one for me, so another reason not to use it.
From http://os.archlinuxarm.org/os/armv5te/boot/pogo_e02/uboot-pogo_e02.env I understand it should be able to boot FDT, but then again maybe only ext3 and certain constellations?
With the NAND mapped differently, I am trying to find out how safe (and feasible) it is to make changes by fw_setenv or reflash to bodhi's U-Boot from within Arch (and preferably keep the latter bootable as well alongside Debian and Stock).
-------------------------------------------------------
> I do not currently recommend the archlinuxarm uboot for the E02.
Sadly (as you've seen in the forum over there) http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray gave no such advance warning. ;(
> Either use Jeff's or Bodhi.
> There are a few minor bugs with the archlinuxarm uboot, mainly netconsole not working as expected
> (no preboot) and you will not be able to boot the default Pogoplug OS because the uboot is missing
> the fsload needed to chainload the original uboot.
So I understand it could be replaced with bodhi's while booted into the working Arch (after fixing /etc/fw_env.config at least, or better yet reflecting all 4 mtds as they are to properly nanddump and disable hbmgr.sh as well, in http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637)?
> Not supporting Debian by default is a new one for me, so another reason not to use it.
From http://os.archlinuxarm.org/os/armv5te/boot/pogo_e02/uboot-pogo_e02.env I understand it should be able to boot FDT, but then again maybe only ext3 and certain constellations?
With the NAND mapped differently, I am trying to find out how safe (and feasible) it is to make changes by fw_setenv or reflash to bodhi's U-Boot from within Arch (and preferably keep the latter bootable as well alongside Debian and Stock).
|
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 17, 2015 06:07PM |
Admin Registered: 13 years ago Posts: 19,107 |
TEN,
> So I understand it could be replaced with bodhi's
> while booted into the working Arch (after fixing
> /etc/fw_env.config at least, or better yet
> reflecting all 4 mtds as they are to properly
> nanddump and disable hbmgr.sh as well, in
> http://archlinuxarm.org/forum/viewtopic.php?f=23&t
> =8637)?
Yes.
> > Not supporting Debian by default is a new one
> for me, so another reason not to use it.
>
> From
> http://os.archlinuxarm.org/os/armv5te/boot/pogo_e0
> 2/uboot-pogo_e02.env I understand it should be
> able to boot FDT, but then again maybe only ext3
> and certain constellations?
No, Arch u-boot could boot anything with some changes in u-boot envs (except stock Pogo OS). As an out of the box installation, it should be used only with Arch rootfs.
>
> With the NAND mapped differently, I am trying to
> find out how safe (and feasible) it is to make
> changes by fw_setenv or reflash to bodhi's U-Boot
> from within Arch (and preferably keep the latter
> bootable as well alongside Debian and Stock).
IIRC, It is the same as you would in Debian, since only mtd0 is being written to. If you list the mtds here, I would be more certain.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/17/2015 06:10PM by bodhi.
> So I understand it could be replaced with bodhi's
> while booted into the working Arch (after fixing
> /etc/fw_env.config at least, or better yet
> reflecting all 4 mtds as they are to properly
> nanddump and disable hbmgr.sh as well, in
> http://archlinuxarm.org/forum/viewtopic.php?f=23&t
> =8637)?
Yes.
> > Not supporting Debian by default is a new one
> for me, so another reason not to use it.
>
> From
> http://os.archlinuxarm.org/os/armv5te/boot/pogo_e0
> 2/uboot-pogo_e02.env I understand it should be
> able to boot FDT, but then again maybe only ext3
> and certain constellations?
No, Arch u-boot could boot anything with some changes in u-boot envs (except stock Pogo OS). As an out of the box installation, it should be used only with Arch rootfs.
>
> With the NAND mapped differently, I am trying to
> find out how safe (and feasible) it is to make
> changes by fw_setenv or reflash to bodhi's U-Boot
> from within Arch (and preferably keep the latter
> bootable as well alongside Debian and Stock).
IIRC, It is the same as you would in Debian, since only mtd0 is being written to. If you list the mtds here, I would be more certain.
cat /proc/mtd dmesg | grep -5 'MTD partitions'
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/17/2015 06:10PM by bodhi.
|
TEN
Re: Pogoplug v2 doesn't show up on LAN after Archlinux install March 18, 2015 01:41AM |
bodhi Wrote:
> > So I understand it could be replaced with
> > bodhi's while booted into the working Arch
> > (after fixing /etc/fw_env.config at least, or better yet
> > reflecting all 4 mtds as they are to properly
> > nanddump and disable hbmgr.sh as well, in
> http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637)?
>
> Yes.
>
> > > Not supporting Debian by default is a new one
> > for me, so another reason not to use it.
> Arch u-boot could boot anything with some changes in u-boot envs (except stock Pogo OS).
Will your U-Boot require "someone else's" dump of the original U-Boot (to chainload) presumably not preserved by Arch's installer?
> > With the NAND mapped differently, I am trying to
> > find out how safe (and feasible) it is to make
> > changes by fw_setenv or reflash to bodhi's U-Boot
> > from within Arch (and preferably keep the latter
> > bootable as well alongside Debian and Stock).
>
> IIRC, It is the same as you would in Debian, since
> only mtd0 is being written to. If you list the
> mtds here, I would be more certain.
Sorry, had only linked to http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637&p=45984#p45984 - here they come:
> > So I understand it could be replaced with
> > bodhi's while booted into the working Arch
> > (after fixing /etc/fw_env.config at least, or better yet
> > reflecting all 4 mtds as they are to properly
> > nanddump and disable hbmgr.sh as well, in
> http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637)?
>
> Yes.
>
> > > Not supporting Debian by default is a new one
> > for me, so another reason not to use it.
> Arch u-boot could boot anything with some changes in u-boot envs (except stock Pogo OS).
Will your U-Boot require "someone else's" dump of the original U-Boot (to chainload) presumably not preserved by Arch's installer?
> > With the NAND mapped differently, I am trying to
> > find out how safe (and feasible) it is to make
> > changes by fw_setenv or reflash to bodhi's U-Boot
> > from within Arch (and preferably keep the latter
> > bootable as well alongside Debian and Stock).
>
> IIRC, It is the same as you would in Debian, since
> only mtd0 is being written to. If you list the
> mtds here, I would be more certain.
Sorry, had only linked to http://archlinuxarm.org/forum/viewtopic.php?f=23&t=8637&p=45984#p45984 - here they come:
[root@alarm ~]# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 07f00000 00020000 "rootfs" [root@alarm ~]# dmesg | grep -5 'MTD partitions' [ 13.816253] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1 [ 13.822635] nand: Hynix NAND 128MiB 3,3V 8-bit [ 13.827110] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 13.834724] Scanning device for bad blocks [ 13.916525] 2 cmdlinepart partitions found on MTD device orion_nand [ 13.922820] Creating 2 MTD partitions on "orion_nand": [ 13.928004] 0x000000000000-0x000000100000 : "u-boot" [ 13.933455] 0x000000100000-0x000008000000 : "rootfs" [ 13.946036] libphy: orion_mdio_bus: probed [ 13.950258] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 15.036062] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address [root@alarm ~]# fw_printenv Cannot parse config file: Invalid argumentThe latter is probably due to /etc/fw_env.config containing nothing but comment lines (none of which applicable to Pogo E02).
