Welcome! Log In Create A New Profile

Advanced

2017.07- 2024.10 U-Boot Kirkwood

Posted by bodhi 
pengu
Re: possible U-Boot for ZyXEL NSA310?
May 18, 2015 05:26AM
Yes, I've tried UART booting (kwboot) so I could test the mentioned U-Boot build.
This was successfull except the LAN Part.
'So I flashed it to NAND and this is working too, with the mentioned exception of a long boot delay at cold boot.
Re: possible U-Boot for ZyXEL NSA310?
May 18, 2015 03:50PM
pengu Wrote:
-------------------------------------------------------
> Yes, I've tried UART booting (kwboot) so I could
> test the mentioned U-Boot build.
> This was successfull except the LAN Part.
> 'So I flashed it to NAND and this is working too,
> with the mentioned exception of a long boot delay
> at cold boot.

Do you know where I can get the source code (or patch) for this, or other NSA310 u-boot?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
@bodhi

Hopefully you can help me recover from a blunder I made on NSA325v2. I edited /etc/fw_env.config with /dev/mtd0 0xc0000 0x20000 0x20000 as indicated, and before doing anything else, I ran a reboot command. Now I'm not getting any response from the device on the serial interface (the connection is made but there's no text). I tried unplugging and replugging etc... still nothing.



Edited 3 time(s). Last edit at 05/25/2015 02:36PM by archon.
archon,

If you've only changed /etc/fw_env.config then it should not effect the serial console at all.

- Did you change anything else before that? are you installing u-boot? if you were, then describe the whole series of steps that you did before changing this file.

- Can you let it boot all the way into Debian and SSH in?

- Which Debian kernel/rootfs is on your boot drive?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 05/25/2015 03:59PM by bodhi.
bodhi,

Thanks for the fast reply. Indeed, I was trying to install your latest uBoot. I'm setting up the NAS from scratch after a run to_stock, so there's no OS installed yet to boot into.

Actually, I got the steps mixed up in my previous post. I didn't stop at editing /etc/fw_env.config (step 1), but after step 2, where I ran fw_printenv ethaddr and got an "ethaddr not defined" error some such, then rebooted.

By that step you did mention "it must be set before rebooting the system", so that seems consistent with my problem? Between the run to_stock and the reboot I simply followed the first 2 steps in your first post—there were no other operations.



Edited 2 time(s). Last edit at 05/25/2015 06:55PM by archon.
archon,

> Between the
> run to_stock and the reboot
> I simply followed the first 2 steps in your first
> post—there were no other operations.

These should not effect the serial console. You should let it boot and try to SSH into stock OS, like you expect it would after running "to_stock". See if you can find the box IP address. If you can log in stock OS then you can fix anything wrong with it.

If you're alsolutely sure that it did not boot into stock OS. Then:

- Make sure you serial console works. Did it work before?

- If serial console was working before, and currently stock OS did not boot. Try UART booting using the u-boot binary attached in this post:
http://forum.doozan.com/read.php?2,14351,17193#msg-17193

Note about UART booting the NSA325v2: prepare the kwboot command, but don't execute it yet. Press the blue power button on the NSA325v2, it will be ON briefly and then OFF, within 1 or 2 seconds after this, that's when you can execute kwboot command.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
bodhi Wrote:
-------------------------------------------------------
> - Make sure you serial console works. Did it work before?

I'm not following you here. The serial console (as in, the USB to UART adapter's) is how I accessed the device in the first place and ran the commands mentioned above, so obviously it worked before. It doesn't now, and that's the problem. Well, the adapter itself seems to work, but it doesn't show any sign of communicating with the NAS.

I'm getting no SSH access either after powering up and waiting a few minutes, though I don't know how to tell if it boots to an OS or not. The blue LED is on, and the my router is set up to assign a static IP to the device's MAC address, so unless the MAC address changed it should be the only possible IP, and I don't see any new device in the router's device list.

As for kwboot tool, I'm running Windows and have no Linux machine locally. I'll get one booting from a stick or something I guess, but it will have to wait.

Honestly, I'm starting to think the device is dead. You said what I did shouldn't affect the serial link, and SSH isn't getting through which it should after a reset to stock, so maybe I just broke it somehow.



Edited 1 time(s). Last edit at 05/26/2015 07:22AM by archon.
archon,

> I'm not following you here. The serial console (as
> in, the USB to UART adapter's) is how I accessed
> the device in the first place and ran the
> commands mentioned above, so obviously it worked
> before.

I see. I assumed you were connecting with SSH.

> As for kwboot tool, I'm running Windows and have
> no Linux machine locally. I'll get one booting
> from a stick or something I guess, but it will
> have to wait.

Yes. Boot with Linux Live CD on Windows (it could be prepared on a USB stick).

> Honestly, I'm starting to think the device is
> dead. You said what I did shouldn't affect the
> serial link, and SSH isn't getting through which
> it should after a reset to stock, so maybe I just
> broke it somehow.

It's not entirely dead. Stock u-boot could not start, probably because the envs that were set by to_stock were not usable.

The NSA325v2 has UART booting, so once you have Linux, run the kwboot version that appropriate for your hardware (either x86 or ARM):

- For 64-bit Ubuntu version, see davygravy thread:
http://forum.doozan.com/read.php?3,7852

- For ARM version, the 1st post of this thread,

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
bodhi Wrote:
-------------------------------------------------------
> I see. I assumed you were connecting with SSH.

Yeah, my mistake. For some reason I assumed the instructions were supposed to be run via serial link only.

Anyway, I'll try the kwboot probably over the weekend. Will let you know.
pengu
possible U-Boot for ZyXEL NSA310?
May 30, 2015 08:08AM
now I'm using another U-Boot (for NSA325) and this seems to work.
The boot delay is gone but still no ethernet because it uses the wrong driver.
What I didn't recognize in the past is, that ethernet doesn't work in the stock U-Boot.
pengz
Re: possible U-Boot for ZyXEL NSA310?
May 30, 2015 10:30AM
the system boots but there were some memory relatet trouble beacause the NSA325 has a different memory layout
so this isn't a solution
Re: possible U-Boot for ZyXEL NSA310?
May 30, 2015 05:33PM
pengz Wrote:
-------------------------------------------------------
> the system boots but there were some memory
> relatet trouble beacause the NSA325 has a
> different memory layout
> so this isn't a solution

We dont have the NSA310 u-boot yet. So the NSA325 u-boot can be used for rescue purpose only. Can you boot with UART (kwboot)?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
pengu
Re: possible U-Boot for ZyXEL NSA310?
May 31, 2015 08:08PM
@bodhi
sorry for the bad post, that's the point, so I've tried several U-Boot versions with different results.

The NSA320 U-Boot from you doesn't work (kwboot), so there aren't any reason to flash it
The NSA325 U-Boot from you comes up fine (kwboot) so I flashed it with the same result.
I've tried to boot an updated 3.18.5 rootfs and for some seconds I'm lucky, but than the system just crashad after some ethernet traffic.
I think this is because the NSA325 has more ram and this is passed to the kernel.

I've mentioned two other U-Boot versions which seemed to work woth the NSA310 (u-boot_nsa310_NANDv1.kwb and u-boot_nsa310_NAND_oryg.kwb).

The last one seems to be a recompile of the original sources and the first one has FDT enabled.
But there is a long delay on one device after U-Boot is up and running.
On another NSA310 there is no delay.
Re: possible U-Boot for ZyXEL NSA310?
June 01, 2015 12:44AM
pengu Wrote:
-------------------------------------------------------
> @bodhi
> sorry for the bad post, that's the point, so I've
> tried several U-Boot versions with different
> results.
>
> The NSA320 U-Boot from you doesn't work (kwboot),
> so there aren't any reason to flash it
> The NSA325 U-Boot from you comes up fine (kwboot)
> so I flashed it with the same result.
> I've tried to boot an updated 3.18.5 rootfs and
> for some seconds I'm lucky, but than the system
> just crashad after some ethernet traffic.
> I think this is because the NSA325 has more ram
> and this is passed to the kernel.
>
> I've mentioned two other U-Boot versions which
> seemed to work woth the NSA310
> (u-boot_nsa310_NANDv1.kwb and
> u-boot_nsa310_NAND_oryg.kwb).
>
> The last one seems to be a recompile of the
> original sources and the first one has FDT
> enabled.
> But there is a long delay on one device after
> U-Boot is up and running.
> On another NSA310 there is no delay.

OK. I will revisit this it a few weeks, I think it's fine to build new u-boot sine we knew UART booting works.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Hi I'm new to Linux.
I attempted to install uboot as well as debian Linux and I belive that I may have bricked my pogoplug v4.
Here is the info that I can see when I boot the pogo with a usb inserted.

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Warning: failed to set MAC address

Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Reset IDE: ide_preinit failed
** Bad device size - ide 0 **
** Bad device size - ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...


U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Warning: failed to set MAC address

Hit any key to stop autoboot: 0

==========

If I do not have a usb installed this is what I see at bootup.
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Warning: failed to set MAC address

Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
** Bad device mmc 0 **
** Bad device mmc 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Reset IDE: ide_preinit failed
** Bad device size - ide 0 **
** Bad device size - ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...


U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Warning: failed to set MAC address


I would prefer to boot to the NAND so that I can utilize the usb 2.0 on the top for an additional drive if possible.

Since this has happened I had a friend assist me in installing a serial connection via a uart controller with putty software for access. I can see the cycling reboot that it is doing. I have also tried to flash a usb on a Ubuntu machine to work around this issue but the usb keeps loosing its ext2 partition.

By the way, when I access the Pogo now I have a command prompt that shows Pogov4>
I am not able to change to any directories and am not able to set any enviro variables.
aquaboy,

It's definitely not a brick. Your rootfs or lack thereof on USB drive is the problem. Did you follow the instruction in this thread to create a Debian rootfs on USB drive? If you did that, then there might be a step missing somewhere.

So go ahead and recreate rootfs on a single Ext3 partition on USB stick using the instruction in the kernel/rootfs thread, and keep the log of what you did. If you can't boot with it, then post the log here. To make things simple, you can use the rootfs version 3.16 in that thread (scrolldown to the section Updated 02 Sept 2014).

You can upgrade the kernel later to 4.0 after it's working.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I will try that tonight and let you know how it goes. Thanks for the help!
Here is where I am stuck now. I downloaded to tar file from dropbox and followed the instructions at the other thread. I was able to format the usb to est2 and mount it. I then copied the tar file to the usb and extracted it. Here is where it gave me several errors.

I am going to try again tomorrow to extract the file again to see if it is successful. By the way. I did the formatting and extract all within ubuntu desktop environment as I was not able to do so in the command prompt window.

Below is what I now get on the pogo plug v4 after it reboots and finds the USB drive with rootfs 3.16 on it with the errors. I tried it just for the heck to see if it would work even with the errors during extraction.


U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Warning: failed to set MAC address

Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
2756040 bytes read in 448 ms (5.9 MiB/s)
6032465 bytes read in 496 ms (11.6 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.16.0-kirkwood-tld-2
Created: 2014-09-01 23:18:31 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2755976 Bytes = 2.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.16.0-kirkwood-tld-2
Created: 2014-09-01 23:18:48 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6032401 Bytes = 5.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Using machid 0x831 from environment

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.16.0-kirkwood-tld-2 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #2 PREEMPT Sun Aug 31 18:56:01 PDT 2014
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Marvell SheevaPlug Reference Board
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 115744K/131072K available (5441K kernel code, 397K rwdata, 1840K rodata, 257K init, 299K bss, 15328K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc07248b0 (7283 kB)
[ 0.000000] .init : 0xc0725000 - 0xc0765444 ( 258 kB)
[ 0.000000] .data : 0xc0766000 - 0xc07c975c ( 398 kB)
[ 0.000000] .bss : 0xc07c975c - 0xc08144dc ( 300 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:114
[ 0.000017] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[ 7.475931] Console: colour dummy device 80x30
[ 7.475974] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[ 7.565585] pid_max: default: 32768 minimum: 301
[ 7.565758] Security Framework initialized
[ 7.565857] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.565886] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.567200] Initializing cgroup subsys devices
[ 7.567291] Initializing cgroup subsys freezer
[ 7.567332] Initializing cgroup subsys net_cls
[ 7.567404] Initializing cgroup subsys blkio
[ 7.567550] CPU: Testing write buffer coherency: ok
[ 7.568249] Setting up static identity map for 0x5273f0 - 0x527448
[ 7.571814] devtmpfs: initialized
[ 7.577857] prandom: seed boundary self test passed
[ 7.583853] prandom: 100 self tests passed
[ 7.583887] pinctrl core: initialized pinctrl subsystem
[ 7.584653] regulator-dummy: no parameters
[ 7.585353] NET: Registered protocol family 16
[ 7.586193] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 7.588067] cpuidle: using governor ladder
[ 7.588110] cpuidle: using governor menu
[ 7.588320] Kirkwood: MV88F6281-A1, TCLK=166666667.
[ 7.588353] Feroceon L2: Enabling L2
[ 7.588406] Feroceon L2: Cache support initialised.
[ 7.627749] vgaarb: loaded
[ 7.628259] usbcore: registered new interface driver usbfs
[ 7.628370] usbcore: registered new interface driver hub
[ 7.628548] usbcore: registered new device driver usb
[ 7.629989] Switched to clocksource orion_clocksource
[ 7.685556] NET: Registered protocol family 2
[ 7.686977] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.687013] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.687042] TCP: Hash tables configured (established 1024 bind 1024)
[ 7.687147] TCP: reno registered
[ 7.687165] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 7.687197] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 7.687501] NET: Registered protocol family 1
[ 7.687973] RPC: Registered named UNIX socket transport module.
[ 7.687990] RPC: Registered udp transport module.
[ 7.688000] RPC: Registered tcp transport module.
[ 7.688011] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 7.688443] Unpacking initramfs...
[ 8.425015] Freeing initrd memory: 5884K (c1101000 - c16c0000)
[ 8.425215] NetWinder Floating Point Emulator V0.97 (double precision)
[ 8.426873] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 8.426968] audit: initializing netlink subsys (disabled)
[ 8.427045] audit: type=2000 audit(0.940:1): initialized
[ 8.428215] zbud: loaded
[ 8.428596] VFS: Disk quotas dquot_6.5.2
[ 8.428669] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 8.429468] NFS: Registering the id_resolver key type
[ 8.429573] Key type id_resolver registered
[ 8.429587] Key type id_legacy registered
[ 8.429623] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 8.429643] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 8.429892] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 8.430402] msgmni has been set to 237
[ 8.430620] Key type big_key registered
[ 8.434048] alg: No test for stdrng (krng)
[ 8.434215] bounce: pool size: 64 pages
[ 8.434308] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 8.434335] io scheduler noop registered
[ 8.434355] io scheduler deadline registered
[ 8.434597] io scheduler cfq registered (default)
[ 8.435222] mv_xor mv_xor.0: Marvell shared XOR driver
[ 8.470096] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 8.510083] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 8.510340] mv_xor mv_xor.1: Marvell shared XOR driver
[ 8.550079] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 8.590078] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 8.590701] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 8.592146] console [ttyS0] disabled
[ 8.612230] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 10416666) is a 16550A
[ 9.155960] console [ttyS0] enabled
[ 9.161414] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 9.167739] nand: Hynix H27U1G8F2BTR-BC
[ 9.171597] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 9.177249] Scanning device for bad blocks
[ 9.296509] 4 cmdlinepart partitions found on MTD device orion_nand
[ 9.302772] Creating 4 MTD partitions on "orion_nand":
[ 9.307898] 0x000000000000-0x000000100000 : "u-boot"
[ 9.313431] 0x000000100000-0x000000500000 : "uImage"
[ 9.318891] 0x000000500000-0x000002500000 : "rootfs"
[ 9.324403] 0x000002500000-0x000008000000 : "data"
[ 9.330951] libphy: Fixed MDIO Bus: probed
[ 9.351657] libphy: orion_mdio_bus: probed
[ 9.355908] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 10.438799] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:00:00:00:00:00
[ 10.447824] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 10.454360] ehci-pci: EHCI PCI platform driver
[ 10.458889] ehci-orion: EHCI orion driver
[ 10.463020] orion-ehci orion-ehci.0: EHCI Host Controller
[ 10.468432] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 10.476171] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 10.500042] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 10.506203] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 10.513002] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 10.520221] usb usb1: Product: EHCI Host Controller
[ 10.525080] usb usb1: Manufacturer: Linux 3.16.0-kirkwood-tld-2 ehci_hcd
[ 10.531778] usb usb1: SerialNumber: orion-ehci.0
[ 10.537454] hub 1-0:1.0: USB hub found
[ 10.541305] hub 1-0:1.0: 1 port detected
[ 10.546466] mousedev: PS/2 mouse device common for all mice
[ 10.860069] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 11.012809] usb 1-1: New USB device found, idVendor=0951, idProduct=1607
[ 11.019503] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 11.026654] usb 1-1: Product: DataTraveler 2.0
[ 11.031103] usb 1-1: Manufacturer: Kingston
[ 11.035271] usb 1-1: SerialNumber: 899810310000000000000A2C
[ 11.560040] rtc-mv rtc-mv: internal RTC not ticking
[ 11.565175] i2c /dev entries driver
[ 11.570289] hidraw: raw HID events driver (C) Jiri Kosina
[ 11.576177] drop_monitor: Initializing network drop monitor service
[ 11.582797] TCP: cubic registered
[ 11.586117] NET: Registered protocol family 17
[ 11.590802] Key type dns_resolver registered
[ 11.596090] registered taskstats version 1
[ 11.601654] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 11.610765] Freeing unused kernel memory: 256K (c0725000 - c0765000)
Loading, please wait...
[ 11.714525] udevd[55]: starting version 175
[ 11.968564] SCSI subsystem initialized
[ 11.976042] mvsdio mvsdio: no pins associated
[ 12.017671] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 12.078697] scsi0 : usb-storage 1-1:1.0
[ 12.091590] usbcore: registered new interface driver usb-storage
[ 12.124089] usbcore: registered new interface driver uas
[ 13.091215] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
[ 13.142640] sd 0:0:0:0: [sda] 3913728 512-byte logical blocks: (2.00 GB/1.86 GiB)
[ 13.151739] sd 0:0:0:0: [sda] Write Protect is off
[ 13.157094] sd 0:0:0:0: [sda] No Caching mode page found
[ 13.162553] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 13.175049] sda: sda1
[ 13.181228] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 13.203123] sd 0:0:0:0: Attached scsi generic sg0 type 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
mount: mounting /dev/sda1 on /root failed: Invalid argument
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
[ 22.487293] uhci_hcd: USB Universal Host Controller Interface driver
[ 22.504941] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 22.523688] usbcore: registered new interface driver usbhid
[ 22.529250] usbhid: USB HID core driver


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)
aquaboy,

> the other thread. I was able to format the usb to
> est2 and mount it. I then copied the tar file to
> the usb and extracted it. Here is where it gave me
> several errors.

You need to format it to EXt3, as I've mentioned above.

If that still does not allow mounting rootfs successfully. Power up, interrupt the serial console and pls get the listing of:
printenv


BTW, you've missed some steps in the installation. arcNumber was not set correctly:
[ 0.000000] Machine: Marvell SheevaPlug Reference Board

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 06/05/2015 12:05AM by bodhi.
Hi Bodhi,
Here's what I have found at my last attempt to extract the tar file.
It seems that it is not getting enough permissions from the user account to fully extract all files and folders. I then tried to manually open the tar file and extract each folder and its group of files manually. It allowed me to do this for all but the few files located in the dev folder.

I formatted to EXT2 only because uboot is specifically looking for EXT2 extension. I will try to change this to EXT3 tonight and do the process of extraction again.

I was thinking that maybe my usb was the issue as it is only 2GB. So, I extracted the files to a folder on my C Drive and then copied those files and folders over to the USB. I still had the same issue with permissions. I think part of the problem I am having is that I am using Ubuntu 12 and booting from a DVD. When it boots the computer, it boots directly to the desktop. It never asks me for any type of username or password.
I think this is where my primary issue resides.

Here is the print out of what the Pogo is doing now.

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Warning: failed to set MAC address

Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
2756040 bytes read in 445 ms (5.9 MiB/s)
6032465 bytes read in 490 ms (11.7 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.16.0-kirkwood-tld-2
Created: 2014-09-01 23:18:31 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2755976 Bytes = 2.6 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.16.0-kirkwood-tld-2
Created: 2014-09-01 23:18:48 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6032401 Bytes = 5.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Using machid 0x831 from environment

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.16.0-kirkwood-tld-2 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #2 PREEMPT Sun Aug 31 18:56:01 PDT 2014
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine: Marvell SheevaPlug Reference Board
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 115744K/131072K available (5441K kernel code, 397K rwdata, 1840K rodata, 257K init, 299K bss, 15328K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc07248b0 (7283 kB)
[ 0.000000] .init : 0xc0725000 - 0xc0765444 ( 258 kB)
[ 0.000000] .data : 0xc0766000 - 0xc07c975c ( 398 kB)
[ 0.000000] .bss : 0xc07c975c - 0xc08144dc ( 300 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:114
[ 0.000017] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[ 7.482308] Console: colour dummy device 80x30
[ 7.482351] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[ 7.571961] pid_max: default: 32768 minimum: 301
[ 7.572134] Security Framework initialized
[ 7.572234] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.572263] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.573577] Initializing cgroup subsys devices
[ 7.573668] Initializing cgroup subsys freezer
[ 7.573708] Initializing cgroup subsys net_cls
[ 7.573781] Initializing cgroup subsys blkio
[ 7.573927] CPU: Testing write buffer coherency: ok
[ 7.574626] Setting up static identity map for 0x5273f0 - 0x527448
[ 7.578191] devtmpfs: initialized
[ 7.584233] prandom: seed boundary self test passed
[ 7.590230] prandom: 100 self tests passed
[ 7.590264] pinctrl core: initialized pinctrl subsystem
[ 7.591030] regulator-dummy: no parameters
[ 7.591730] NET: Registered protocol family 16
[ 7.592570] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 7.594444] cpuidle: using governor ladder
[ 7.594486] cpuidle: using governor menu
[ 7.594696] Kirkwood: MV88F6281-A1, TCLK=166666667.
[ 7.594730] Feroceon L2: Enabling L2
[ 7.594783] Feroceon L2: Cache support initialised.
[ 7.634126] vgaarb: loaded
[ 7.634635] usbcore: registered new interface driver usbfs
[ 7.634747] usbcore: registered new interface driver hub
[ 7.634924] usbcore: registered new device driver usb
[ 7.636365] Switched to clocksource orion_clocksource
[ 7.691932] NET: Registered protocol family 2
[ 7.693354] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.693389] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 7.693419] TCP: Hash tables configured (established 1024 bind 1024)
[ 7.693523] TCP: reno registered
[ 7.693542] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 7.693574] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 7.693878] NET: Registered protocol family 1
[ 7.694350] RPC: Registered named UNIX socket transport module.
[ 7.694367] RPC: Registered udp transport module.
[ 7.694377] RPC: Registered tcp transport module.
[ 7.694387] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 7.694819] Unpacking initramfs...
[ 8.431371] Freeing initrd memory: 5884K (c1101000 - c16c0000)
[ 8.431571] NetWinder Floating Point Emulator V0.97 (double precision)
[ 8.433229] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 8.433325] audit: initializing netlink subsys (disabled)
[ 8.433401] audit: type=2000 audit(0.940:1): initialized
[ 8.434569] zbud: loaded
[ 8.434947] VFS: Disk quotas dquot_6.5.2
[ 8.435020] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 8.435812] NFS: Registering the id_resolver key type
[ 8.435895] Key type id_resolver registered
[ 8.435909] Key type id_legacy registered
[ 8.435946] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 8.435967] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 8.436215] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 8.436728] msgmni has been set to 237
[ 8.436948] Key type big_key registered
[ 8.440372] alg: No test for stdrng (krng)
[ 8.440539] bounce: pool size: 64 pages
[ 8.440631] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 8.440657] io scheduler noop registered
[ 8.440678] io scheduler deadline registered
[ 8.440925] io scheduler cfq registered (default)
[ 8.441545] mv_xor mv_xor.0: Marvell shared XOR driver
[ 8.476475] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 8.516460] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[ 8.516715] mv_xor mv_xor.1: Marvell shared XOR driver
[ 8.556457] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 8.596456] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[ 8.597081] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 8.598519] console [ttyS0] disabled
[ 8.618600] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 10416666) is a 16550A
[ 9.162321] console [ttyS0] enabled
[ 9.167773] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 9.174099] nand: Hynix H27U1G8F2BTR-BC
[ 9.177956] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 9.183611] Scanning device for bad blocks
[ 9.302871] 4 cmdlinepart partitions found on MTD device orion_nand
[ 9.309132] Creating 4 MTD partitions on "orion_nand":
[ 9.314258] 0x000000000000-0x000000100000 : "u-boot"
[ 9.319793] 0x000000100000-0x000000500000 : "uImage"
[ 9.325257] 0x000000500000-0x000002500000 : "rootfs"
[ 9.330766] 0x000002500000-0x000008000000 : "data"
[ 9.337311] libphy: Fixed MDIO Bus: probed
[ 9.357884] libphy: orion_mdio_bus: probed
[ 9.362141] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 10.445173] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:00:00:00:00:00
[ 10.454204] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 10.460746] ehci-pci: EHCI PCI platform driver
[ 10.465273] ehci-orion: EHCI orion driver
[ 10.469405] orion-ehci orion-ehci.0: EHCI Host Controller
[ 10.474818] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[ 10.482558] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[ 10.506415] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[ 10.512571] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 10.519368] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 10.526590] usb usb1: Product: EHCI Host Controller
[ 10.531448] usb usb1: Manufacturer: Linux 3.16.0-kirkwood-tld-2 ehci_hcd
[ 10.538148] usb usb1: SerialNumber: orion-ehci.0
[ 10.543826] hub 1-0:1.0: USB hub found
[ 10.547680] hub 1-0:1.0: 1 port detected
[ 10.552851] mousedev: PS/2 mouse device common for all mice
[ 10.866444] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 11.019198] usb 1-1: New USB device found, idVendor=0951, idProduct=1607
[ 11.025897] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 11.033049] usb 1-1: Product: DataTraveler 2.0
[ 11.037498] usb 1-1: Manufacturer: Kingston
[ 11.041666] usb 1-1: SerialNumber: 899810310000000000000A2C
[ 11.566418] rtc-mv rtc-mv: internal RTC not ticking
[ 11.571551] i2c /dev entries driver
[ 11.576677] hidraw: raw HID events driver (C) Jiri Kosina
[ 11.582568] drop_monitor: Initializing network drop monitor service
[ 11.589182] TCP: cubic registered
[ 11.592502] NET: Registered protocol family 17
[ 11.597162] Key type dns_resolver registered
[ 11.602453] registered taskstats version 1
[ 11.608029] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[ 11.617134] Freeing unused kernel memory: 256K (c0725000 - c0765000)
Loading, please wait...
[ 11.720329] udevd[55]: starting version 175
[ 11.959160] mvsdio mvsdio: no pins associated
[ 11.974427] SCSI subsystem initialized
[ 12.030607] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 12.088850] scsi0 : usb-storage 1-1:1.0
[ 12.099109] usbcore: registered new interface driver usb-storage
[ 12.137154] usbcore: registered new interface driver uas
[ 13.087604] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
[ 13.139155] sd 0:0:0:0: [sda] 3913728 512-byte logical blocks: (2.00 GB/1.86 GiB)
[ 13.148257] sd 0:0:0:0: [sda] Write Protect is off
[ 13.153608] sd 0:0:0:0: [sda] No Caching mode page found
[ 13.159070] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 13.171940] sda: sda1
[ 13.178240] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 13.200170] sd 0:0:0:0: Attached scsi generic sg0 type 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
mount: mounting /dev/sda1 on /root failed: Invalid argument
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
[ 22.493192] uhci_hcd: USB Universal Host Controller Interface driver
[ 22.510736] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 22.529444] usbcore: registered new interface driver usbhid
[ 22.535004] usbhid: USB HID core driver


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) [ 68.766486] random: nonblocking pool is initialized



Unable to get printenv details as it is (initramfs)
when I type printenv I get this error
/bin/sh: printenv: not found
I power down pogo and brought back up and here are the printenv of pogo prior to booting to usb

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 128 MiB
MMC: kwsdio: 0
In: serial
Out: serial
Err: serial
Net: egiga0
Warning: failed to set MAC address

Hit any key to stop autoboot: 0
Pogov4> printenv
arcNumber=2097
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=0x831
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.0.220
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 2193/131068 bytes
aquaboy,

> I formatted to EXT2 only because uboot is
> specifically looking for EXT2 extension. I will
> try to change this to EXT3 tonight and do the
> process of extraction again.

The default u-boot env for rootfs type is Ext3. Don't be mislead by the command name extt2load, it is just a command that will load files from ext2/ext3 file system.
rootfstype=ext3

You can boot with Ext2 rootfs, it will still work, but it's better to use Ext3 so you don't have other problems later.

> I think part of the
> problem I am having is that I am using Ubuntu 12
> and booting from a DVD. When it boots the
> computer, it boots directly to the desktop. It
> never asks me for any type of username or
> password.
> I think this is where my primary issue resides.

Yes. This is the problem. You have to be root while extracting the tarball to have correct permission (sudo will not work). So after login into Ubuntu Live DVD,

See who you are
whoami
Become root
su root
If you can't become root with su root, try
su

and then cd to the USB drive, extract the tarball.

BTW, you also have problem with MAC address, but you have serial console, so it is OK to wait until you have booted in Debian to fix it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thank you!
I am going to try that and see if that works. Yes, I know there is an issue with MAC I have tried to set it in uboot but as close as I could get so far is to set eth0 to the mac address, but still not fixed.
Also I was able to change the arcNumber to 3960, I believe. I also was able to save this info to the NAND.

I will report back my results soon.
Still unable to login on terminal as root user
Using Ubuntu 12.04 live cd and keep getting failure. tried typical root password as well as null and keep getting access denied. Created another user account called roo and made it administrator. Still getting the apparent authority issues. Here is the failures that I am seeing.

ubuntu@ubuntu:/media/rootfs$ tar -xjf Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2
tar: ./dev/mem: Cannot mknod: Operation not permitted
tar: ./dev/loop4: Cannot mknod: Operation not permitted
tar: ./dev/port: Cannot mknod: Operation not permitted
tar: ./dev/loop1: Cannot mknod: Operation not permitted
tar: ./dev/ram8: Cannot mknod: Operation not permitted
tar: ./dev/ram11: Cannot mknod: Operation not permitted
tar: ./dev/ram16: Cannot mknod: Operation not permitted
tar: ./dev/ram1: Cannot mknod: Operation not permitted
tar: ./dev/ram14: Cannot mknod: Operation not permitted
tar: ./dev/tty: Cannot mknod: Operation not permitted
tar: ./dev/kmem: Cannot mknod: Operation not permitted
tar: ./dev/ram0: Cannot mknod: Operation not permitted
tar: ./dev/ram2: Cannot mknod: Operation not permitted
tar: ./dev/loop6: Cannot mknod: Operation not permitted
tar: ./dev/ram13: Cannot mknod: Operation not permitted
tar: ./dev/zero: Cannot mknod: Operation not permitted
tar: ./dev/ram6: Cannot mknod: Operation not permitted
tar: ./dev/ram15: Cannot mknod: Operation not permitted
tar: ./dev/loop7: Cannot mknod: Operation not permitted
tar: ./dev/tty0: Cannot mknod: Operation not permitted
tar: ./dev/loop5: Cannot mknod: Operation not permitted
tar: ./dev/loop3: Cannot mknod: Operation not permitted
tar: ./dev/urandom: Cannot mknod: Operation not permitted
tar: ./dev/ram10: Cannot mknod: Operation not permitted
tar: ./dev/console: Cannot mknod: Operation not permitted
tar: ./dev/ram12: Cannot mknod: Operation not permitted
tar: ./dev/random: Cannot mknod: Operation not permitted
tar: ./dev/loop2: Cannot mknod: Operation not permitted
tar: ./dev/full: Cannot mknod: Operation not permitted
tar: ./dev/ptmx: Cannot mknod: Operation not permitted
tar: ./dev/ram7: Cannot mknod: Operation not permitted
tar: ./dev/null: Cannot mknod: Operation not permitted
tar: ./dev/ram5: Cannot mknod: Operation not permitted
tar: ./dev/ram9: Cannot mknod: Operation not permitted
tar: ./dev/ram3: Cannot mknod: Operation not permitted
tar: ./dev/loop0: Cannot mknod: Operation not permitted
tar: ./dev/ram4: Cannot mknod: Operation not permitted
tar: ./lost+found: Cannot utime: Operation not permitted
tar: Exiting with failure status due to previous errors

Thinking that I am going to have to fully install Ubuntu on my windows box and try again at this user account issue.
aquaboy,

Have you tried
sudo su
whoami

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Hi bodhi,

this is just another verification that your latest uBoot i.e. NSA320 u-boot 2014.07-tld-3 image
worked fine with uart booting and kwboot on a NSA320 box here, so I flashed it and configured the
uboot envs and its running properly with only minor issues, (see below),
to everybody else who also tries this,

please use the latest tools from ftp://ftp.denx.de/pub/u-boot/u-boot-2015.01.tar.bz2
where (after one has compiled the tools from the tools directory) especially
mkenvimage version 2015.01 is quite handy when transfering the old u-boot
environment, to the new u-boot after the flash,.. this has already been discussed
in this thread, I just wanted to mention from where the tools can be downloaded,..


the few glitches which occured are more or less all attributed to devices attached which in the early u-boot start phase
don't behave properly,..

first a sata sandisk ssd, (we saw this before also with davygravys v4 uboot for the NSA320, perhaps you remember this), and a sandisk ultra fit usb 3.0 usbstick, which give a hickup, when the rootfs should have been loaded from it in the boot phase, after the initramfs has been decompressed,

when testing another sandisk ultra usb 2.0 stick behaved properly, also it was possible
to boot the sandisk ssd once it was put in an usb 3.0 seagate disk enclosure with hdparm data rates
around 30 MB/s, so I left the NSA320 in this configuration, both sata slots can now become populated with sata disks
and the rootfs resides on a usb disk, which also makes standby modes of the sata drives easier,..

best wishes pbg4

logs are as follows:

problems with the sandisk ultra fit usb 3.0 stick:

Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... [   17.823601] usb 1-1.2: device descriptor read/64, error -110
[   23.013595] usb 1-1.2: device descriptor read/64, error -71
[   23.203595] usb 1-1.2: new high-speed USB device number 4 using orion-ehci
[   23.313592] usb 1-1.2: device descriptor read/64, error -71
[   23.513594] usb 1-1.2: device descriptor read/64, error -71
done.
Gave up waiting for root device.  Common problems:

both delay values rootdelay and bootdelay were set to 10 seconds, which was more than enough for all
the other usb rootfs devices tested,.. the stick was also recognized in the early boot phase as a storage device
and uImage and uInitrd could also be loaded from it, once the debian os was loaded from
another usbstick, the ultra fit could be used without problems, with hdparm read rates around 28 MB/s,..

i.e.:

U-Boot 2014.07-tld-3 (Mar 07 2015 - 00:59:52)
ZyXEL NSA320 2-Bay Power Media Server

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on 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     21920           60729952        00000000-01     83 Boot
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
(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
3061534 bytes read in 342 ms (8.5 MiB/s)
6671624 bytes read in 404 ms (15.7 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.0.0-kirkwood-tld-2
   Created:      2015-06-25  18:26:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3061470 Bytes = 2.9 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.0.0-kirkwood-tld-2
   Created:      2015-06-07  14:19:51 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6671560 Bytes = 6.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

here is the sandisk ssd problem, please watch for the capacity values which are also a mess:

U-Boot 2014.07-tld-3 (Mar 07 2015 - 00:59:52)
ZyXEL NSA320 2-Bay Power Media Server

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

no USB devices available
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
stopping USB..

Reset IDE: Bus 0: OK Bus 1: OK 
  Device 0: Model: ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ Firm: ?ÿ?ÿ?ÿ?ÿ Ser#: ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ?ÿ
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 427923841.5 MB = 417894.3 GB (4611474908973580287 x 512)
IDE read: device 0 not ready
IDE read: device 0 not ready
  Device 1: Model: SAMSUNG HD154UI  Firm: 1AG01118 Ser#: S1Y6J9AS810343
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (2930277168 x 512)
** No partition table - ide 0 **
** No partition table - ide 0 **
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
resetting ...

if the sandisk ssd is put in an usb 3.0 enclosure and booted from usb everything is fine,..



Edited 5 time(s). Last edit at 06/12/2015 04:32PM by pbg4.
@pbg4,

1. problems with the sandisk ultra fit usb 3.0 stick:

Yes, I think this is definitely the problem with the Sandisk Ultra Fit USB 3.0. This is possibly can be resolved with a quirk, but we don't know what that quirk should be.

2. sandisk ssd problem

Yes, it seems some Sandisk SSDs have some kind of timing problem. We've seen this exact behavior with the Sandisk Readycache 32GB. Once you've booted into Debian, it wil be initialized correctly as a SATA disk (no need to put it an USB enclosure). And it's true that if it's installed an USB enclosure and connect to a USB 2.0 port, then it is OK to boot with it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
bodhi Wrote:
-------------------------------------------------------
> @pbg4,
>
> 1. problems with the sandisk ultra fit usb 3.0
> stick:
>
> Yes, I think this is definitely the problem with
> the Sandisk Ultra Fit USB 3.0. This is possibly
> can be resolved with a quirk, but we don't know
> what that quirk should be.
>
> 2. sandisk ssd problem
>
> Yes, it seems some Sandisk SSDs have some kind of
> timing problem. We've seen this exact behavior
> with the Sandisk Readycache 32GB. Once you've
> booted into Debian, it wil be initialized
> correctly as a SATA disk (no need to put it an USB
> enclosure). And it's true that if it's installed
> an USB enclosure and connect to a USB 2.0 port,
> then it is OK to boot with it.

Sadly, I just bought two ultra 3.0 sandisk flash drives that aren't working. If it helps you narrow down the quirk, I'm seeing the same above behavior, the kernel is loaded from the drive but when the kernel later tires to load the usb device it cannot enumerate it. However, ff I unplug and replug the drive in between the kernel load into memory and the usb poll, the device will be properly recognized and the system will fully boot. Also, if i hit the reset button after it fails to enumerate the first time, it will no longer be recognized at all by uboot until a reboot command or a full power off or I unplug and replug the device. Can mount and read the device in the rescue system and on the latest jessie build you put out when loaded from another flash drive.

Would really like to see this working as it is a really small drive and has fast read/write speeds compared to my other drives
East2West,

I plan to investigate this problem in a couple weeks when I have more time.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
pbg4,

Thanks for the confirmation:

Quote

this is just another verification that your latest uBoot i.e. NSA320 u-boot 2014.07-tld-3 image
worked fine with uart booting and kwboot on a NSA320 box here, so I flashed it and configured the
uboot envs and its running properly with only minor issue,

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Sorry, you can't reply to this topic. It has been closed.