Pogoplug v2 doesn't show up on LAN after Archlinux install

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Re: Pogoplug v2 doesn't show up on LAN after Archlinux insta

Postby Waynosan » Sun Jan 25, 2015 3:00 am

Thank you for the response. Not sure what exactly you mean by that... I created another ALARM USB drive on my Linux box. Getting the same type of network errors when booting up with that USB drive.
$this->bbcode_second_pass_code('', 'U-Boot 2014.04.R3-1 (May 26 2014 - 19:45:55) Arch Linux ARM
Pogo E02

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 63 31251961 229807f6-01 83
Attempting to boot from usb 0:1...
** File not found /boot/uEnv.txt **
Checking if uenvcmd is set ...
Running default loadzimage ...
** File not found /boot/zImage **
Running default loaduimage ...
4028544 bytes read in 363 ms (10.6 MiB/s)
Booting from 0 ...
## Booting kernel from Legacy Image at 00810000 ...
Image Name: Linux-3.18.1-1-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4028480 Bytes = 3.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.18.1-1-ARCH (nobody@root-armv5-copy) (gcc version 4.9.2 (GCC) ) #1 PREEMPT Tue Dec 23 02:43:32 MST 2014
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397 f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Pogoplug E02
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pag es: 65024
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rw rootw ait mtdparts=orion_nand:1M(u-boot),-(rootfs)
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 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.000000] allocated 524288 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memor y cgroups
[ 0.000000] Memory: 250668K/262144K available (5616K kernel code, 351K rwdata , 1704K rodata, 268K init, 704K bss, 11476K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc072e518 (7322 kB)
[ 0.000000] .init : 0xc072f000 - 0xc0772000 ( 268 kB)
[ 0.000000] .data : 0xc0772000 - 0xc07c9ebc ( 352 kB)
[ 0.000000] .bss : 0xc07c9ebc - 0xc0879f04 ( 705 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:114
[ 0.000011] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474 836475ns
[ 13.825657] Console: colour dummy device 80x30
[ 13.825684] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[ 13.915558] pid_max: default: 32768 minimum: 301
[ 13.915655] Security Framework initialized
[ 13.915729] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 13.915748] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 13.916424] Initializing cgroup subsys memory
[ 13.916469] Initializing cgroup subsys devices
[ 13.916493] Initializing cgroup subsys freezer
[ 13.916511] Initializing cgroup subsys net_cls
[ 13.916528] Initializing cgroup subsys blkio
[ 13.916543] Initializing cgroup subsys bfqio
[ 13.916560] Initializing cgroup subsys perf_event
[ 13.916580] Initializing cgroup subsys net_prio
[ 13.916670] CPU: Testing write buffer coherency: ok
[ 13.917117] Setting up static identity map for 0x55a220 - 0x55a278
[ 13.919242] devtmpfs: initialized
[ 13.923026] pinctrl core: initialized pinctrl subsystem
[ 13.923676] NET: Registered protocol family 16
[ 13.924144] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 13.945560] cpuidle: using governor ladder
[ 13.975558] cpuidle: using governor menu
[ 13.975708] Kirkwood: MV88F6281-A0, TCLK=200000000.
[ 13.975731] Feroceon L2: Enabling L2
[ 13.975769] Feroceon L2: Cache support initialised.
[ 14.007220] vgaarb: loaded
[ 14.007559] SCSI subsystem initialized
[ 14.008070] usbcore: registered new interface driver usbfs
[ 14.008146] usbcore: registered new interface driver hub
[ 14.008214] usbcore: registered new device driver usb
[ 14.008383] pps_core: LinuxPPS API ver. 1 registered
[ 14.008392] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giome tti <giometti@linux.it>
[ 14.008427] PTP clock support registered
[ 14.009445] Switched to clocksource orion_clocksource
[ 14.028470] FS-Cache: Loaded
[ 14.041688] NET: Registered protocol family 2
[ 14.042572] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 14.042610] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 14.042640] TCP: Hash tables configured (established 2048 bind 2048)
[ 14.042705] TCP: reno registered
[ 14.042719] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 14.042740] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 14.042937] NET: Registered protocol family 1
[ 14.044689] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 14.057215] VFS: Disk quotas dquot_6.5.2
[ 14.057480] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 14.059297] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 14.060466] fuse init (API version 7.23)
[ 14.062478] aufs 3.x-rcN-20141215
[ 14.062514] msgmni has been set to 489
[ 14.064465] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 2 50)
[ 14.064488] io scheduler noop registered
[ 14.064503] io scheduler deadline registered
[ 14.064803] io scheduler cfq registered
[ 14.065289] io scheduler bfq registered (default)
[ 14.065297] BFQ I/O-scheduler version: v7r6
[ 14.065494] mv_xor mv_xor.0: Marvell shared XOR driver
[ 14.099532] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 14.139521] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 14.139720] mv_xor mv_xor.1: Marvell shared XOR driver
[ 14.179518] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 14.219516] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 14.225007] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 14.226080] console [ttyS0] disabled
[ 14.246189] serial8250 serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base _baud = 12500000) is a 16550A
[ 14.763395] console [ttyS0] enabled
[ 14.776335] brd: module loaded
[ 14.784046] loop: module loaded
[ 14.788380] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 14.794801] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 14.799436] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 14.805142] Scanning device for bad blocks
[ 14.886878] 2 cmdlinepart partitions found on MTD device orion_nand
[ 14.893191] Creating 2 MTD partitions on "orion_nand":
[ 14.898352] 0x000000000000-0x000000100000 : "u-boot"
[ 14.903826] 0x000000100000-0x000008000000 : "rootfs"
[ 14.916348] libphy: orion_mdio_bus: probed
[ 14.920621] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 16.000477] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:02:21:5c
[ 16.009435] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 16.016033] ehci-pci: EHCI PCI platform driver
[ 16.020584] ehci-orion: EHCI orion driver
[ 16.024692] orion-ehci orion-ehci.0: EHCI Host Controller
[ 16.030163] orion-ehci orion-ehci.0: new USB bus registered, assigned bus num ber 1
[ 16.037902] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 16.059477] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 16.066394] hub 1-0:1.0: USB hub found
[ 16.070249] hub 1-0:1.0: 1 port detected
[ 16.074839] usbcore: registered new interface driver uas
[ 16.080367] usbcore: registered new interface driver usb-storage
[ 16.086461] usbcore: registered new interface driver ums-alauda
[ 16.092505] usbcore: registered new interface driver ums-cypress
[ 16.098596] usbcore: registered new interface driver ums-datafab
[ 16.104706] usbcore: registered new interface driver ums_eneub6250
[ 16.110991] usbcore: registered new interface driver ums-freecom
[ 16.117075] usbcore: registered new interface driver ums-isd200
[ 16.123094] usbcore: registered new interface driver ums-jumpshot
[ 16.129270] usbcore: registered new interface driver ums-karma
[ 16.135208] usbcore: registered new interface driver ums-onetouch
[ 16.141432] usbcore: registered new interface driver ums-realtek
[ 16.147517] usbcore: registered new interface driver ums-sddr09
[ 16.153537] usbcore: registered new interface driver ums-sddr55
[ 16.159561] usbcore: registered new interface driver ums-usbat
[ 16.165862] mousedev: PS/2 mouse device common for all mice
[ 16.389502] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 16.542015] hub 1-1:1.0: USB hub found
[ 16.546166] hub 1-1:1.0: 4 ports detected
[ 16.829794] usb 1-1.4: new high-speed USB device number 3 using orion-ehci
[ 16.942810] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 16.949412] scsi host0: usb-storage 1-1.4:1.0
[ 17.179470] rtc-mv rtc-mv: internal RTC not ticking
[ 17.184525] i2c /dev entries driver
[ 17.188649] sdhci: Secure Digital Host Controller Interface driver
[ 17.194880] sdhci: Copyright(c) Pierre Ossman
[ 17.199327] sdhci-pltfm: SDHCI platform and OF driver helper
[ 17.205552] ledtrig-cpu: registered to indicate activity on CPUs
[ 17.211762] usbcore: registered new interface driver r8712u
[ 17.217560] gre: GRE over IPv4 demultiplexor driver
[ 17.222516] TCP: cubic registered
[ 17.225865] NET: Registered protocol family 17
[ 17.230475] Key type dns_resolver registered
[ 17.235738] registered taskstats version 1
[ 17.241128] console [netcon0] enabled
[ 17.244811] netconsole: network logging started
[ 17.249521] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 17.257068] Waiting for root device /dev/sda1...
[ 18.061770] scsi 0:0:0:0: Direct-Access Kingston DT 101 II 1.00 PQ : 0 ANSI: 2
[ 18.071340] sd 0:0:0:0: [sda] 31252024 512-byte logical blocks: (16.0 GB/14.9 GiB)
[ 18.079180] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 18.084696] sd 0:0:0:0: [sda] Write Protect is off
[ 18.090322] sd 0:0:0:0: [sda] Incomplete mode parameter data
[ 18.096008] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 18.105886] sda: sda1
[ 18.110696] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 18.140707] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsyste m
[ 20.076993] EXT4-fs (sda1): recovery complete
[ 20.084204] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 20.091973] VFS: Mounted root (ext3 filesystem) on device 8:1.
[ 20.102383] devtmpfs: mounted
[ 20.106308] Freeing unused kernel memory: 268K (c072f000 - c0772000)
[ 20.488614] NET: Registered protocol family 10
[ 20.494278] systemd[1]: Inserted module 'ipv6'
[ 20.506434] random: systemd urandom read with 57 bits of entropy available
[ 20.523439] systemd[1]: systemd 218 running in system mode. (+PAM -AUDIT -SEL INUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL + XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD +IDN)
[ 20.541932] systemd[1]: Detected architecture 'arm'.

Welcome to Arch Linux ARM!

[ 20.570608] systemd[1]: Set hostname to <alarm>.
[ 21.143255] systemd[1]: Cannot add dependency job for unit display-manager.se rvice, ignoring: Unit display-manager.service failed to load: No such file or di rectory.
[ 21.166405] systemd[1]: Starting Root Slice.
[ OK ] Created slice Root Slice.
[ 21.189640] systemd[1]: Created slice Root Slice.
[ 21.194552] systemd[1]: Starting Delayed Shutdown Socket.
[ OK ] Listening on Delayed Shutdown Socket.
[ 21.219616] systemd[1]: Listening on Delayed Shutdown Socket.
[ 21.225580] systemd[1]: Starting udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 21.249607] systemd[1]: Listening on udev Kernel Socket.
[ 21.255098] systemd[1]: Starting Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket (/dev/log).
[ 21.279608] systemd[1]: Listening on Journal Socket (/dev/log).
[ 21.285716] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ OK ] Listening on /dev/initctl Compatibility Named Pipe.
[ 21.309614] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 21.316762] systemd[1]: Starting LVM2 metadata daemon socket.
[ OK ] Listening on LVM2 metadata daemon socket.
[ 21.339609] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 21.345901] systemd[1]: Expecting device dev-ttyS0.device...
Expecting device dev-ttyS0.device...
[ 21.388264] systemd[1]: Listening on Journal Audit Socket.
[ 21.394125] systemd[1]: Starting Journal Socket.
[ OK ] Listening on Journal Socket.
[ 21.419629] systemd[1]: Listening on Journal Socket.
[ 21.424901] systemd[1]: Starting System Slice.
[ OK ] Created slice System Slice.
[ 21.449620] systemd[1]: Created slice System Slice.
[ 21.454737] systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 21.483967] systemd[1]: Mounting Debug File System...
Mounting Debug File System...
[ 21.499763] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ 21.533682] systemd[1]: Starting Arbitrary Executable File Formats File Syste m Automount Point.
[ OK ] Set up automount Arbitrary Executab...ats File System Automount Point.
[ 21.579730] systemd[1]: Set up automount Arbitrary Executable File Formats Fi le System Automount Point.
[ 21.595441] systemd[1]: Started Set Up Additional Binary Formats.
[ 21.601885] systemd[1]: Starting Remount Root and Kernel File Systems...
Starting Remount Root and Kernel File Systems...
[ 21.633595] systemd[1]: Starting Encrypted Volumes.
[ OK ] Reached target Encrypted Volumes.
[ 21.659726] systemd[1]: Reached target Encrypted Volumes.
[ 21.673622] systemd[1]: Started Load Kernel Modules.
[ 21.678819] systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 21.724040] systemd[1]: Mounted Huge Pages File System.
[ 21.733658] systemd[1]: Starting User and Session Slice.
[ OK ] Created slice User and Session Slice.
[ 21.763028] systemd[1]: Created slice User and Session Slice.
[ 21.769047] systemd[1]: Starting Slices.
[ OK ] Reached target Slices.
[ 21.789639] systemd[1]: Reached target Slices.
[ 21.794297] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 21.802424] systemd[1]: Started Forward Password Requests to Wall Directory W atch.
[ 21.810246] systemd[1]: Starting system-getty.slice.
[ OK ] Created slice system-getty.slice.
[ 21.839628] systemd[1]: Created slice system-getty.slice.
[ 21.845228] systemd[1]: Starting Swap.
[ OK ] Reached target Swap.
[ 21.869603] systemd[1]: Reached target Swap.
[ 21.874121] systemd[1]: Mounting FUSE Control File System...
Mounting FUSE Control File System...
[ 21.903606] systemd[1]: Mounted Configuration File System.
[ 21.909396] systemd[1]: Starting system-serial\x2dgetty.slice.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ 21.936901] systemd-journald[64]: File /var/log/journal/35c03120e82f4f1ba307d 8d650c18384/system.journal corrupted or uncleanly shut down, renaming and replac ing.
[ 21.951705] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 21.958263] systemd[1]: Starting Setup Virtual Console...
Starting Setup Virtual Console...
[ 21.984209] systemd[1]: Starting Create list of required static device nodes for the current kernel...
Starting Create list of required st... nodes for the current kernel...
[ 22.023919] systemd[1]: Starting udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 22.059693] systemd[1]: Listening on udev Control Socket.
[ 22.065446] systemd[1]: Starting udev Coldplug all Devices...
Starting udev Coldplug all Devices...
[ 22.093654] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ OK ] Listening on Device-mapper event daemon FIFOs.
[ 22.129675] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 22.136575] systemd[1]: Mounting Temporary Directory...
Mounting Temporary Directory...
[ 22.228495] systemd[1]: Starting Remote File Systems.
[ OK ] Reached target Remote File Systems.
[ 22.289678] systemd[1]: Reached target Remote File Systems.
[ 22.295569] systemd[1]: Starting Dispatch Password Requests to Console Direct ory Watch.
[ 22.324742] systemd[1]: Started Dispatch Password Requests to Console Directo ry Watch.
[ 22.349723] systemd[1]: Starting Paths.
[ OK ] Reached target Paths.
[ 22.369641] systemd[1]: Reached target Paths.
[ OK ] Mounted FUSE Control File System.
[ 22.409643] systemd[1]: Mounted FUSE Control File System.
[ OK ] Mounted Debug File System.
[ 22.439634] systemd[1]: Mounted Debug File System.
[ OK ] Mounted POSIX Message Queue File System.
[ 22.469692] systemd[1]: Mounted POSIX Message Queue File System.
[ OK ] Mounted Temporary Directory.
[ 22.489732] systemd[1]: Mounted Temporary Directory.
[ OK ] Started Remount Root and Kernel File Systems.
[ 22.519659] systemd[1]: Started Remount Root and Kernel File Systems.
[ OK ] Started Apply Kernel Variables.
[ 22.539842] systemd[1]: Started Apply Kernel Variables.
[ OK ] Started Setup Virtual Console.
[ 22.559682] systemd[1]: Started Setup Virtual Console.
[ OK ] Started Create list of required sta...ce nodes for the current kernel.
[ 22.589671] systemd[1]: Started Create list of required static device nodes f or the current kernel.
[ OK ] Started udev Coldplug all Devices.
[ 22.819673] systemd[1]: Started udev Coldplug all Devices.
[ OK ] Started Journal Service.
[ 22.899708] systemd[1]: Started Journal Service.
Starting Create Static Device Nodes in /dev...
Starting Load/Save Random Seed...
Starting Flush Journal to Persistent Storage...
[ OK ] Started Create Static Device Nodes in /dev.
[ OK ] Started Load/Save Random Seed.
[ 23.581022] systemd-journald[64]: Received request to flush runtime journal f rom PID 1
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting udev Kernel Device Manager...
[ 24.049529] random: nonblocking pool is initialized
[ OK ] Started udev Kernel Device Manager.
[ OK ] Started Flush Journal to Persistent Storage.
[ OK ] Found device /dev/ttyS0.
Starting Create Volatile Files and Directories...
[ OK ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown...
Starting Network Time Synchronization...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
Stopping Network Time Synchronization...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Network Time Synchronization.
See "systemctl status systemd-timesyncd.service" for details.
[ OK ] Reached target System Time Synchronized.
[ OK ] Reached target System Initialization.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Timers.
[ OK ] Reached target Basic System.
Starting Login Service...
Starting Permit User Sessions...
Starting D-Bus System Message Bus...
[ OK ] Started D-Bus System Message Bus.
Starting Network Service...
Starting Entropy Harvesting Daemon...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for details.
[ OK ] Started Permit User Sessions.
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Login Service...
[ OK ] Stopped Login Service.
Starting Login Service...
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
Starting Getty on tty1...
[ OK ] Started Getty on tty1.
Starting Serial Getty on ttyS0...
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.
[ OK ] Started Login Service.
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
[ OK ] Started Entropy Harvesting Daemon.
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
Stopping Network Service...
[ OK ] Stopped Network Service.
Starting Network Service...
[FAILED] Failed to start Network Service.
See "systemctl status systemd-networkd.service" for details.
[ OK ] Reached target Network.
Starting OpenSSH Daemon...
[ OK ] Started OpenSSH Daemon.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See "systemctl status systemd-resolved.service" for details.
Stopping Network Name Resolution...
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See "systemctl status systemd-resolved.service" for details.
Stopping Network Name Resolution...
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See "systemctl status systemd-resolved.service" for details.
Stopping Network Name Resolution...
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See "systemctl status systemd-resolved.service" for details.
Stopping Network Name Resolution...
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See "systemctl status systemd-resolved.service" for details.
Stopping Network Name Resolution...
[ OK ] Stopped Network Name Resolution.
Starting Network Name Resolution...
[FAILED] Failed to start Network Name Resolution.
See "systemctl status systemd-resolved.service" for details.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.

Arch Linux 3.18.1-1-ARCH (ttyS0)
')

Here is the response from the mount command:
$this->bbcode_second_pass_code('', '[root@alarm ~]# mount
/dev/sda1 on / type ext3 (rw,relatime,data=ordered)
devtmpfs on /dev type devtmpfs (rw,relatime,size=125332k,nr_inodes=31333,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/bfqio type cgroup (rw,nosuid,nodev,noexec,relatime,bfqio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=25096k,mode=700)
')

What should I be looking for?
Waynosan
 
Posts: 22
Joined: Wed Mar 06, 2013 2:49 pm

Re: Pogoplug v2 doesn't show up on LAN after Archlinux insta

Postby WarheadsSE » Sun Jan 25, 2015 5:25 am

At this point, I would be examining the journal's for the services, and their statuses, as denoted in the boot log.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Pogoplug v2 doesn't show up on LAN after Archlinux insta

Postby Waynosan » Sun Jan 25, 2015 7:43 am

WarheadsSE,
Thank you. Is there a guide somewhere that you could point me to regarding these journals? Very new at this. Also, should I rule-out uboot at this point? Not sure why the PP doesn't boot properly (with network) when there is no USB drive connected.

Is there a way to flash everything back to stock at this point and just start over?
Waynosan
 
Posts: 22
Joined: Wed Mar 06, 2013 2:49 pm

Re: Pogoplug v2 doesn't show up on LAN after Archlinux insta

Postby Waynosan » Sun Feb 08, 2015 6:46 pm

OK, I'm still struggling with this. Here is what I see in the systemd logs.

$this->bbcode_second_pass_code('', '
[root@alarm ~]# systemctl status systemd-timesyncd.service -l
* systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit) since Wed 2014-12-10 22:16:51 UTC; 7min ago
Docs: man:systemd-timesyncd.service(8)
Process: 134 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
Main PID: 134 (code=exited, status=1/FAILURE)

Dec 10 22:16:51 alarm systemd[1]: Failed to start Network Time Synchronization.
Dec 10 22:16:51 alarm systemd[1]: Unit systemd-timesyncd.service entered failed state.
Dec 10 22:16:51 alarm systemd[1]: systemd-timesyncd.service failed.
Dec 10 22:16:51 alarm systemd[1]: systemd-timesyncd.service has no holdoff time, scheduling restart.
Dec 10 22:16:51 alarm systemd[1]: Stopping Network Time Synchronization...
Dec 10 22:16:51 alarm systemd[1]: Starting Network Time Synchronization...
Dec 10 22:16:51 alarm systemd[1]: start request repeated too quickly for systemd-timesyncd.service
Dec 10 22:16:51 alarm systemd[1]: Failed to start Network Time Synchronization.
Dec 10 22:16:51 alarm systemd[1]: Unit systemd-timesyncd.service entered failed state.
Dec 10 22:16:51 alarm systemd[1]: systemd-timesyncd.service failed.
[root@alarm ~]#
[root@alarm ~]# systemctl status systemd-networkd.service -l
* systemd-networkd.service - Network Service
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit) since Wed 2014-12-10 22:16:53 UTC; 8min ago
Docs: man:systemd-networkd.service(8)
Process: 157 ExecStart=/usr/lib/systemd/systemd-networkd (code=exited, status=1/FAILURE)
Main PID: 157 (code=exited, status=1/FAILURE)

Dec 10 22:16:53 alarm systemd[1]: Failed to start Network Service.
Dec 10 22:16:53 alarm systemd[1]: Unit systemd-networkd.service entered failed state.
Dec 10 22:16:53 alarm systemd[1]: systemd-networkd.service failed.
Dec 10 22:16:53 alarm systemd[1]: systemd-networkd.service has no holdoff time, scheduling restart.
Dec 10 22:16:53 alarm systemd[1]: Stopping Network Service...
Dec 10 22:16:53 alarm systemd[1]: Starting Network Service...
Dec 10 22:16:53 alarm systemd[1]: start request repeated too quickly for systemd-networkd.service
Dec 10 22:16:53 alarm systemd[1]: Failed to start Network Service.
Dec 10 22:16:53 alarm systemd[1]: Unit systemd-networkd.service entered failed state.
Dec 10 22:16:53 alarm systemd[1]: systemd-networkd.service failed.
')

When I look at the journal I see the RTC as the first red item... Jan 01 00:00:06 alarm kernel: rtc-mv rtc-mv: internal RTC not ticking. Here is some of the log where you can see the errors... I tried to bold them but apparently you can't use bold and code at the same time.

$this->bbcode_second_pass_code('', '[root@alarm ~]# journalctl
-- Logs begin at Thu 1970-01-01 00:00:06 UTC, end at Wed 2014-12-10 22:20:33 UTC
Jan 01 00:00:06 alarm systemd-journal[75]: Runtime journal is using 4.0M (max al
Jan 01 00:00:06 alarm systemd-journal[75]: Permanent journal is using 8.0M (max
Jan 01 00:00:06 alarm systemd-journal[75]: Time spent on flushing to /var is 15.
Jan 01 00:00:06 alarm kernel: Booting Linux on physical CPU 0x0
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys cpuset
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys cpu
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys cpuacct
Jan 01 00:00:06 alarm kernel: Linux version 3.18.1-1-ARCH (nobody@root-armv5-cop
Jan 01 00:00:06 alarm kernel: CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5
Jan 01 00:00:06 alarm kernel: CPU: VIVT data cache, VIVT instruction cache
Jan 01 00:00:06 alarm kernel: Machine: Pogoplug E02
Jan 01 00:00:06 alarm kernel: Memory policy: Data cache writeback
Jan 01 00:00:06 alarm kernel: On node 0 totalpages: 65536
Jan 01 00:00:06 alarm kernel: free_area_init_node: node 0, pgdat c07c2504, node_
Jan 01 00:00:06 alarm kernel: Normal zone: 512 pages used for memmap
Jan 01 00:00:06 alarm kernel: Normal zone: 0 pages reserved
Jan 01 00:00:06 alarm kernel: Normal zone: 65536 pages, LIFO batch:15
Jan 01 00:00:06 alarm kernel: pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Jan 01 00:00:06 alarm kernel: pcpu-alloc: [0] 0
Jan 01 00:00:06 alarm kernel: Built 1 zonelists in Zone order, mobility grouping
Jan 01 00:00:06 alarm kernel: Kernel command line: console=ttyS0,115200 root=/de
Jan 01 00:00:06 alarm kernel: PID hash table entries: 1024 (order: 0, 4096 bytes
Jan 01 00:00:06 alarm kernel: Dentry cache hash table entries: 32768 (order: 5,
Jan 01 00:00:06 alarm kernel: Inode-cache hash table entries: 16384 (order: 4, 6
Jan 01 00:00:06 alarm kernel: allocated 524288 bytes of page_cgroup
Jan 01 00:00:06 alarm kernel: please try 'cgroup_disable=memory' option if you d
Jan 01 00:00:06 alarm kernel: Memory: 250668K/262144K available (5616K kernel co
Jan 01 00:00:06 alarm kernel: Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
vmalloc : 0xd0800000 - 0xff000000 ( 744 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc072e518 (7322 kB)
.init : 0xc072f000 - 0xc0772000 ( 268 kB)
.data : 0xc0772000 - 0xc07c9ebc ( 352 kB)
.bss : 0xc07c9ebc - 0xc0879f04 ( 705 kB)
Jan 01 00:00:06 alarm kernel: SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1,
Jan 01 00:00:06 alarm kernel: Preemptible hierarchical RCU implementation.
Jan 01 00:00:06 alarm kernel: NR_IRQS:114
Jan 01 00:00:06 alarm kernel: sched_clock: 32 bits at 200MHz, resolution 5ns, wr
Jan 01 00:00:06 alarm kernel: Console: colour dummy device 80x30
Jan 01 00:00:06 alarm kernel: Calibrating delay loop... 1191.11 BogoMIPS (lpj=59
Jan 01 00:00:06 alarm kernel: pid_max: default: 32768 minimum: 301
Jan 01 00:00:06 alarm kernel: Security Framework initialized
Jan 01 00:00:06 alarm kernel: Mount-cache hash table entries: 1024 (order: 0, 40
Jan 01 00:00:06 alarm kernel: Mountpoint-cache hash table entries: 1024 (order:
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys memory
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys devices
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys freezer
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys net_cls
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys blkio
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys bfqio
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys perf_event
Jan 01 00:00:06 alarm kernel: Initializing cgroup subsys net_prio
Jan 01 00:00:06 alarm kernel: CPU: Testing write buffer coherency: ok
Jan 01 00:00:06 alarm kernel: Setting up static identity map for 0x55a220 - 0x55
Jan 01 00:00:06 alarm kernel: devtmpfs: initialized
Jan 01 00:00:06 alarm kernel: pinctrl core: initialized pinctrl subsystem
Jan 01 00:00:06 alarm kernel: NET: Registered protocol family 16
Jan 01 00:00:06 alarm kernel: DMA: preallocated 256 KiB pool for atomic coherent
Jan 01 00:00:06 alarm kernel: cpuidle: using governor ladder
Jan 01 00:00:06 alarm kernel: cpuidle: using governor menu
Jan 01 00:00:06 alarm kernel: Kirkwood: MV88F6281-A0, TCLK=200000000.
Jan 01 00:00:06 alarm kernel: Feroceon L2: Enabling L2
Jan 01 00:00:06 alarm kernel: Feroceon L2: Cache support initialised.
Jan 01 00:00:06 alarm kernel: initial MPP regs: 01111111 11113322 00001111 00100
Jan 01 00:00:06 alarm kernel: final MPP regs: 01111111 11113322 00001111 00000
Jan 01 00:00:06 alarm kernel: vgaarb: loaded
Jan 01 00:00:06 alarm kernel: SCSI subsystem initialized
Jan 01 00:00:06 alarm kernel: libata version 3.00 loaded.
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver usbfs
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver hub
Jan 01 00:00:06 alarm kernel: usbcore: registered new device driver usb
Jan 01 00:00:06 alarm kernel: pps_core: LinuxPPS API ver. 1 registered
Jan 01 00:00:06 alarm kernel: pps_core: Software ver. 5.3.6 - Copyright 2005-200
Jan 01 00:00:06 alarm kernel: PTP clock support registered
Jan 01 00:00:06 alarm kernel: Switched to clocksource orion_clocksource
Jan 01 00:00:06 alarm kernel: FS-Cache: Loaded
Jan 01 00:00:06 alarm kernel: NET: Registered protocol family 2
Jan 01 00:00:06 alarm kernel: TCP established hash table entries: 2048 (order: 1
Jan 01 00:00:06 alarm kernel: TCP bind hash table entries: 2048 (order: 1, 8192
Jan 01 00:00:06 alarm kernel: TCP: Hash tables configured (established 2048 bind
Jan 01 00:00:06 alarm kernel: TCP: reno registered
Jan 01 00:00:06 alarm kernel: UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan 01 00:00:06 alarm kernel: UDP-Lite hash table entries: 256 (order: 0, 4096 b
Jan 01 00:00:06 alarm kernel: NET: Registered protocol family 1
Jan 01 00:00:06 alarm kernel: PCI: CLS 0 bytes, default 32
Jan 01 00:00:06 alarm kernel: futex hash table entries: 256 (order: -1, 3072 byt
Jan 01 00:00:06 alarm kernel: VFS: Disk quotas dquot_6.5.2
Jan 01 00:00:06 alarm kernel: Dquot-cache hash table entries: 1024 (order 0, 409
Jan 01 00:00:06 alarm kernel: jffs2: version 2.2. (NAND) <C2><A9> 2001-2006 Red
Jan 01 00:00:06 alarm kernel: fuse init (API version 7.23)
Jan 01 00:00:06 alarm kernel: aufs 3.x-rcN-20141215
Jan 01 00:00:06 alarm kernel: msgmni has been set to 489
Jan 01 00:00:06 alarm kernel: Block layer SCSI generic (bsg) driver version 0.4
Jan 01 00:00:06 alarm kernel: io scheduler noop registered
Jan 01 00:00:06 alarm kernel: io scheduler deadline registered
Jan 01 00:00:06 alarm kernel: io scheduler cfq registered
Jan 01 00:00:06 alarm kernel: io scheduler bfq registered (default)
Jan 01 00:00:06 alarm kernel: BFQ I/O-scheduler version: v7r6
Jan 01 00:00:06 alarm kernel: mv_xor mv_xor.0: Marvell shared XOR driver
Jan 01 00:00:06 alarm kernel: mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
Jan 01 00:00:06 alarm kernel: mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
Jan 01 00:00:06 alarm kernel: mv_xor mv_xor.1: Marvell shared XOR driver
Jan 01 00:00:06 alarm kernel: mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
Jan 01 00:00:06 alarm kernel: mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
Jan 01 00:00:06 alarm kernel: Serial: 8250/16550 driver, 2 ports, IRQ sharing di
Jan 01 00:00:06 alarm kernel: console [ttyS0] disabled
Jan 01 00:00:06 alarm kernel: serial8250 serial8250.0: ttyS0 at MMIO 0xf1012000
Jan 01 00:00:06 alarm kernel: console [ttyS0] enabled
Jan 01 00:00:06 alarm kernel: brd: module loaded
Jan 01 00:00:06 alarm kernel: loop: module loaded
Jan 01 00:00:06 alarm kernel: nand: device found, Manufacturer ID: 0xec, Chip ID
Jan 01 00:00:06 alarm kernel: nand: Samsung NAND 128MiB 3,3V 8-bit
Jan 01 00:00:06 alarm kernel: nand: 128MiB, SLC, page size: 2048, OOB size: 64
Jan 01 00:00:06 alarm kernel: Scanning device for bad blocks
Jan 01 00:00:06 alarm kernel: 2 cmdlinepart partitions found on MTD device orion
-- Reboot --
Jan 01 00:00:06 alarm systemd-journal[65]: Runtime journal is using 4.0M (max al
-- Reboot --
Jan 01 00:00:06 alarm kernel: Creating 2 MTD partitions on "orion_nand":
Jan 01 00:00:06 alarm kernel: 0x000000000000-0x000000100000 : "u-boot"
Jan 01 00:00:06 alarm kernel: 0x000000100000-0x000008000000 : "rootfs"
Jan 01 00:00:06 alarm kernel: libphy: orion_mdio_bus: probed
Jan 01 00:00:06 alarm kernel: mv643xx_eth: MV-643xx 10/100/1000 ethernet driver
Jan 01 00:00:06 alarm kernel: mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 w
Jan 01 00:00:06 alarm kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI
Jan 01 00:00:06 alarm kernel: ehci-pci: EHCI PCI platform driver
Jan 01 00:00:06 alarm kernel: ehci-orion: EHCI orion driver
Jan 01 00:00:06 alarm kernel: orion-ehci orion-ehci.0: EHCI Host Controller
Jan 01 00:00:06 alarm kernel: orion-ehci orion-ehci.0: new USB bus registered, a
Jan 01 00:00:06 alarm kernel: orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
Jan 01 00:00:06 alarm kernel: orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.0
Jan 01 00:00:06 alarm kernel: hub 1-0:1.0: USB hub found
Jan 01 00:00:06 alarm kernel: hub 1-0:1.0: 1 port detected
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver uas
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver usb-stora
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-alaud
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-cypre
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-dataf
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums_eneub
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-freec
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-isd20
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-jumps
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-karma
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-oneto
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-realt
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-sddr0
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-sddr5
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver ums-usbat
Jan 01 00:00:06 alarm kernel: mousedev: PS/2 mouse device common for all mice
Jan 01 00:00:06 alarm kernel: usb 1-1: new high-speed USB device number 2 using
Jan 01 00:00:06 alarm kernel: hub 1-1:1.0: USB hub found
Jan 01 00:00:06 alarm kernel: hub 1-1:1.0: 4 ports detected
Jan 01 00:00:06 alarm kernel: usb 1-1.4: new high-speed USB device number 3 usin
Jan 01 00:00:06 alarm kernel: usb-storage 1-1.4:1.0: USB Mass Storage device det
Jan 01 00:00:06 alarm kernel: scsi host0: usb-storage 1-1.4:1.0
[b]Jan 01 00:00:06 alarm kernel: rtc-mv rtc-mv: internal RTC not ticking[/b]
Jan 01 00:00:06 alarm kernel: i2c /dev entries driver
Jan 01 00:00:06 alarm kernel: sdhci: Secure Digital Host Controller Interface dr
Jan 01 00:00:06 alarm kernel: sdhci: Copyright(c) Pierre Ossman
Jan 01 00:00:06 alarm kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Jan 01 00:00:06 alarm kernel: ledtrig-cpu: registered to indicate activity on CP
Jan 01 00:00:06 alarm kernel: usbcore: registered new interface driver r8712u
Jan 01 00:00:06 alarm kernel: gre: GRE over IPv4 demultiplexor driver
Jan 01 00:00:06 alarm kernel: TCP: cubic registered
Jan 01 00:00:06 alarm kernel: NET: Registered protocol family 17
Jan 01 00:00:06 alarm kernel: Key type dns_resolver registered
Jan 01 00:00:06 alarm kernel: registered taskstats version 1
Jan 01 00:00:06 alarm kernel: console [netcon0] enabled
Jan 01 00:00:06 alarm kernel: netconsole: network logging started
[b]Jan 01 00:00:06 alarm kernel: drivers/rtc/hctosys.c: unable to open rtc device ([/b]
Jan 01 00:00:06 alarm kernel: Waiting for root device /dev/sda1...
Jan 01 00:00:06 alarm kernel: scsi 0:0:0:0: Direct-Access Kingston DT 101 II
Jan 01 00:00:06 alarm kernel: sd 0:0:0:0: [sda] 31252024 512-byte logical blocks
Jan 01 00:00:06 alarm kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan 01 00:00:06 alarm kernel: sd 0:0:0:0: [sda] Write Protect is off
Jan 01 00:00:06 alarm kernel: sd 0:0:0:0: [sda] Mode Sense: 16 25 09 51
Jan 01 00:00:06 alarm kernel: sd 0:0:0:0: [sda] Incomplete mode parameter data
Jan 01 00:00:06 alarm kernel: sd 0:0:0:0: [sda] Assuming drive cache: write thro
Jan 01 00:00:06 alarm kernel: sda: sda1
Jan 01 00:00:06 alarm kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
')
Waynosan
 
Posts: 22
Joined: Wed Mar 06, 2013 2:49 pm

Re: Pogoplug v2 doesn't show up on LAN after Archlinux insta

Postby Waynosan » Sun Feb 15, 2015 10:22 pm

Got the device restored with much help from bodhi... Thank you!!!!!

Followed the install process again. Someone needs to update the install how-to located here:

http://archlinuxarm.org/platforms/armv5 ... 2-pinkgray

To not use bsdtar because it ends up failing. I used regular tar and it worked OK.

After the update it appears that Archlinux is installed and working OK. Please consider this issue closed.
Waynosan
 
Posts: 22
Joined: Wed Mar 06, 2013 2:49 pm

Previous

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 9 guests