Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

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

Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby ejblom » Mon Aug 12, 2013 7:06 pm

Dear Arch-ers

After a failed upgrade (V2 wouldn't boot) I did a fresh installation. Since i ***** up my installation on my V2 regularly, I am now an expert in re-installing my V2.

However, this time, my V2 wouldn't come up. And it appears I am not the only one.

I enabled netconsole and used my ubuntu server to obtain the messages:

Uboot
$this->bbcode_second_pass_code('', 'nc -lu 10.10.10.5 6666

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

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 91 MiB
UBI: number of good PEBs: 724
UBI: number of bad PEBs: 4
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 713
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
2889400 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.1.10-22-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2889336 Bytes = 2.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xdd6 from environment

Starting kernel ...
')

$this->bbcode_second_pass_code('', 'nc -lu 10.10.10.4 6666
[ 7.012636] console [netcon0] enabled
[ 7.016325] netconsole: network logging started
[ 7.020956] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 7.027592] Waiting 10sec before mounting root device...
[ 17.043035] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[ 17.317436] EXT4-fs (sda1): recovery complete
[ 17.323911] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 17.331673] VFS: Mounted root (ext3 filesystem) on device 8:1.
[ 17.341953] devtmpfs: mounted
[ 17.345597] Freeing init memory: 172K
[ 17.771737] systemd[1]: systemd 204 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
[ 17.850012] systemd[1]: Inserted module 'autofs4'
[ 17.894617] NET: Registered protocol family 10
[ 17.902913] systemd[1]: Inserted module 'ipv6'
[ 17.909320] systemd[1]: Set hostname to <alarm>.
[ 18.106501] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. See system logs and 'systemctl status display-manager.service' for details.
[ 18.128992] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[ 18.137123] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 18.144908] systemd[1]: Expecting device dev-ttyS0.device...
[ 18.171697] systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
[ 18.201667] systemd[1]: Starting Remote File Systems.
[ 18.221649] systemd[1]: Reached target Remote File Systems.
[ 18.227351] systemd[1]: Starting Device-mapper event daemon FIFOs.
[ 18.251655] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[ 18.258315] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[ 18.281650] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[ 18.288738] systemd[1]: Starting Delayed Shutdown Socket.
[ 18.311654] systemd[1]: Listening on Delayed Shutdown Socket.
[ 18.317523] systemd[1]: Starting LVM2 metadata daemon socket.
[ 18.341654] systemd[1]: Listening on LVM2 metadata daemon socket.
[ 18.347879] systemd[1]: Starting Encrypted Volumes.
[ 18.371649] systemd[1]: Reached target Encrypted Volumes.
[ 18.377305] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[ 18.411664] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 18.421239] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[ 18.429567] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 18.437636] systemd[1]: Starting Paths.
[ 18.461662] systemd[1]: Reached target Paths.
[ 18.466151] systemd[1]: Starting Journal Socket.
[ 18.491730] systemd[1]: Listening on Journal Socket.
[ 18.496873] systemd[1]: Mounting Debug File System...
[ 18.630529] systemd[1]: Starting Apply Kernel Variables...
[ 18.706658] systemd[1]: Started Set Up Additional Binary Formats.
[ 18.715830] systemd[1]: Starting Journal Service...
[ 18.801847] systemd[1]: Started Journal Service.
[ 18.807595] systemd[1]: Starting Create static device nodes in /dev...
[ 18.872450] systemd[1]: Starting udev Kernel Socket.
[ 18.901748] systemd[1]: Listening on udev Kernel Socket.
[ 18.907531] systemd[1]: Starting udev Control Socket.
[ 18.931722] systemd[1]: Listening on udev Control Socket.
[ 18.937605] systemd[1]: Starting udev Coldplug all Devices...
[ 19.002891] systemd[1]: Starting Setup Virtual Console...
[ 19.052337] systemd[1]: Mounting POSIX Message Queue File System...
[ 19.125285] systemd[1]: Started Load Kernel Modules.
[ 19.130439] systemd[1]: Mounted FUSE Control File System.
[ 19.149581] systemd[1]: Mounted Huge Pages File System.
[ 19.155075] systemd[1]: Mounted Configuration File System.
[ 19.160684] systemd[1]: Starting Swap.
[ 19.181673] systemd[1]: Reached target Swap.
[ 19.186078] systemd[1]: Mounting Temporary Directory...
[ 19.256981] systemd[1]: Started File System Check on Root Device.
[ 19.264529] systemd[1]: Starting Remount Root and Kernel File Systems...
[ 19.361711] systemd[1]: Mounted Debug File System.
[ 19.421715] systemd[1]: Started Apply Kernel Variables.
[ 19.481670] systemd[1]: Started Create static device nodes in /dev.
[ 19.591727] systemd[1]: Started Setup Virtual Console.
[ 19.621747] systemd[1]: Mounted POSIX Message Queue File System.
[ 19.641715] systemd[1]: Mounted Temporary Directory.
[ 19.701672] systemd[1]: Started Remount Root and Kernel File Systems.
[ 19.761670] systemd[1]: Started udev Coldplug all Devices.
[ 19.767398] systemd[1]: Starting Load Random Seed...
[ 19.834084] systemd[1]: Starting udev Kernel Device Manager...
[ 19.920832] systemd-udevd[67]: starting version 204
[ 19.961776] systemd[1]: Started Load Random Seed.
[ 20.041877] systemd[1]: Started udev Kernel Device Manager.
[ 20.051843] systemd[1]: Starting Local File Systems (Pre).
[ 20.081762] systemd[1]: Reached target Local File Systems (Pre).
[ 20.087956] systemd[1]: Starting Local File Systems.
[ 20.121810] systemd[1]: Reached target Local File Systems.
[ 20.131953] systemd[1]: Starting Recreate Volatile Files and Directories...
[ 20.222308] systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
[ 20.321742] systemd[1]: Found device /dev/ttyS0.
[ 20.381778] systemd[1]: Started Recreate Volatile Files and Directories.
[ 20.388772] systemd[1]: Starting Update UTMP about System Reboot/Shutdown...
[ 20.501859] systemd[1]: Found device /sys/subsystem/net/devices/eth0.
[ 20.821755] systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
[ 20.881882] systemd[1]: Started Update UTMP about System Reboot/Shutdown.
[ 20.889196] systemd[1]: Starting System Initialization.
[ 20.911700] systemd[1]: Reached target System Initialization.
[ 20.917699] systemd[1]: Starting D-Bus System Message Bus Socket.
[ 20.942271] systemd[1]: Listening on D-Bus System Message Bus Socket.
[ 20.949056] systemd[1]: Starting Sockets.
[ 20.971712] systemd[1]: Reached target Sockets.
[ 20.976384] systemd[1]: Starting Daily Cleanup of Temporary Directories.
[ 20.983453] systemd[1]: Started Daily Cleanup of Temporary Directories.
[ 20.990432] systemd[1]: Starting Timers.
[ 21.011747] systemd[1]: Reached target Timers.
[ 21.016326] systemd[1]: Starting Basic System.
[ 21.041707] systemd[1]: Reached target Basic System.
[ 21.046817] systemd[1]: Starting Automatic wired network connection using netctl profiles...
[ 21.141789] systemd[1]: Started Automatic wired network connection using netctl profiles.
[ 21.150222] systemd[1]: Starting Entropy Harvesting Daemon...
[ 21.212872] systemd[1]: Started SSH Key Generation.
[ 21.218046] systemd[1]: Starting OpenSSH Daemon...
[ 21.301790] systemd[1]: Started OpenSSH Daemon.
[ 21.306564] systemd[1]: Starting D-Bus System Message Bus...
[ 21.391801] systemd[1]: Started D-Bus System Message Bus.
[ 21.398286] systemd[1]: Starting Login Service...
[ 21.482317] systemd[1]: Starting Permit User Sessions...
[ 36.767308] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
')

In my router, my V2 always gets the same IP address based on its MAC address. Can't ping it though. The messages do not seem very disturbing, but some way, the system won't get an eth0 link....

Anyone with a solution?
ejblom
 
Posts: 27
Joined: Sun Feb 10, 2013 12:12 pm

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby kmihelich » Mon Aug 12, 2013 7:29 pm

All of the new rootfs's are using netctl with ifplugd, which on other platforms isn't showing an issue. You might try just unplugging the ethernet cable and plugging it back in, see if that will trigger ifplugd to do its thing.
Arch Linux ARM exists and continues to grow through community support, please donate today!
kmihelich
Developer
 
Posts: 1133
Joined: Tue Jul 20, 2010 6:55 am
Location: aka leming #archlinuxarm

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby WarheadsSE » Mon Aug 12, 2013 7:30 pm

Have you ever seen issues with the device in regards to dhcp?
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby ejblom » Mon Aug 12, 2013 7:36 pm

$this->bbcode_second_pass_quote('', 'A')ll of the new rootfs's are using netctl with ifplugd, which on other platforms isn't showing an issue. You might try just unplugging the ethernet cable and plugging it back in, see if that will trigger ifplugd to do its thing.


Thanks for the suggestion, tried it, didn't work unfortunately...

$this->bbcode_second_pass_quote('', '
')Have you ever seen issues with the device in regards to dhcp?

Never, always worked like a charm.
ejblom
 
Posts: 27
Joined: Sun Feb 10, 2013 12:12 pm

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby pepedog » Mon Aug 12, 2013 10:42 pm

Some people with pi have said systemctl enable netctl-ifplugd@eth0 isn't doing the job.
systemctl enable dhcpcd@eth0 does work.
Maybe it's differences in tolerence, cable, router?
Does SkipNoCarrier=yes in profile help?
man netctl.profile
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby ejblom » Tue Aug 13, 2013 4:43 pm

$this->bbcode_second_pass_quote('', 'S')ome people with pi have said systemctl enable netctl-ifplugd@eth0 isn't doing the job.
systemctl enable dhcpcd@eth0 does work.
Maybe it's differences in tolerence, cable, router?
Does SkipNoCarrier=yes in profile help?
man netctl.profile


Yes! You are my hero :-)

Here is what I did (for other people).
Boot into pogoplug without the USB stick, login with root and your predefined root pass
After logging in, stick in the USB stick and do the following:

cd /tmp
mkdir usb
mount /dev/sda1 usb

the stick is now mounted, I am assuming everything is already copied onto the stick.
Next:
cp /tmp/usb/etc/netctl/examples/ethernet-static /tmp/usb/etc/netctl/profile

vi profile
curse vi commands since you already forgot them
edit the profile file so that it matches your network settings and below the IP4 settings, add this line:
SkipNoCarrier=yes
save profile (in vi --> :wq)
umount /tmp/usb

reboot

enjoy!
ejblom
 
Posts: 27
Joined: Sun Feb 10, 2013 12:12 pm
Top

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby pepedog » Tue Aug 13, 2013 6:21 pm

I almost wish I had the problem myself, so I could test on other platforms
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby caldersm » Thu Aug 15, 2013 1:50 am

OMG....OMG.....I am trying this.....it isnt working, but I am having the same issue.

Dont understand how to do a netconsole yet.....so I am glad someone is trying to make this work.

What did you mean by: edit the profile file so that it matches your network settings and below the IP4 settings, add this line:

I am not sure how to change the IP address line......my current IP is 192.168.0.3, and I can boot into it without the usb key. I did edit the profile in VI.....I added that line for the skip carrier after the IP4, but before the IP6 stuff.

Do you leave the profile file in that same directory that we copied to....? I am struggling so badly here....looked like a 30 minute job to set up as a Samba share....but this is Day 3 of frustration...!! Tried 4 different Usb keys....none of them will give me the root prompt in putty.

Looks like this is working for you....any ideas....I am a noob as you can tell....

Thanks....Steve
caldersm
 
Posts: 18
Joined: Thu Aug 15, 2013 1:42 am

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby pepedog » Thu Aug 15, 2013 8:51 am

Can you try
boot to stock
plug in stick with rootfs already on it, mount, cd to it
vi etc/netctl/eth0
Add this line at bottom
SkipNoCarrier=yes
save profile (in vi --> :wq)
cd ..
umount usb
/sbin/reboot
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: Faulty ArchLinuxARM-armv5te-latest.tar.gz on V2?

Postby caldersm » Thu Aug 15, 2013 1:02 pm

I will do that when I get home....thanks...!!

One thing I noticed while browsing around the awesome forums here.....a lot of people are saying to:
Add PRE_UP="sleep 15" to the /etc/network.d/wired-eth0

But when I go to the USB drive that I have installed Arch to(about 10 times..!!), I dont have a network.d directory. They were talking about netctrl not being installed(?).....do I need to do that...? If so, how do I do that, because pacman is not a recognized command when I boot stock....so I dont know how to install it....maybe I dont need to....so lost...hehehehe.

Your thoughts about that...? And THANK YOU so much...!! I am absorbing this stuff like sponge....but feel pretty stupid about now.

Steve
caldersm
 
Posts: 18
Joined: Thu Aug 15, 2013 1:42 am

Next

Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 23 guests