Welcome! Log In Create A New Profile

Advanced

Pogo V3 Booting problem

Posted by agiorgio 
Pogo V3 Booting problem
December 03, 2015 09:23AM
Well, I tried both Debian rootfs' from the first post (3.12.13 and 3.17.0), and neither one is letting me on the network. I'd like to update my uboot, but I can't do so unless I get a shell on the system.

I also tried varkey's rootfs, but that didn't seem to accept the changes I made to the /etc/network/interfaces file for the MAC address. The very end of the log shows a MAC address that doesn't match the hardware. Here is the /var/log/messages output from that attempt:

Jan  1 05:30:17 debian kernel: imklog 4.6.4, log source = /proc/kmsg started.
Jan  1 05:30:17 debian rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="746" x-info="http://www.rsyslog.com";] (re)start
Jan  1 05:30:17 debian kernel: 000000] Machine: Oxsemi NAS
Jan  1 05:30:17 debian kernel: [    0.000000] 1 memory region
Jan  1 05:30:17 debian kernel: [    0.000000] Ignoring unrecognised tag 0x00000000
Jan  1 05:30:17 debian kernel: [    0.000000] Memory policy: ECC disabled, Data cache writealloc
Jan  1 05:30:17 debian kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Jan  1 05:30:17 debian kernel: [    0.000000] Kernel command line: root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 rootwait mem=128M poweroutage=yes
Jan  1 05:30:17 debian kernel: [    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
Jan  1 05:30:17 debian kernel: [    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Jan  1 05:30:17 debian kernel: [    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Jan  1 05:30:17 debian kernel: [    0.000000] Memory: 128MB = 128MB total
Jan  1 05:30:17 debian kernel: [    0.000000] Memory: 125112KB available (4012K code, 316K data, 144K init, 0K highmem)
Jan  1 05:30:17 debian kernel: [    0.000000] Hierarchical RCU implementation.
Jan  1 05:30:17 debian kernel: [    0.000000] NR_IRQS:96
Jan  1 05:30:17 debian kernel: [    0.000000] OX820_RPS_init_irq: interrupts 64 to 96
Jan  1 05:30:17 debian kernel: [    0.010000] Console: colour dummy device 80x30
Jan  1 05:30:17 debian kernel: [    0.010000] console [ttyS0] enabled
Jan  1 05:30:17 debian kernel: [    0.020000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
Jan  1 05:30:17 debian kernel: [    0.260000] Security Framework initialized
Jan  1 05:30:17 debian kernel: [    0.260000] Mount-cache hash table entries: 512
Jan  1 05:30:17 debian kernel: [    0.270000] CPU: Testing write buffer coherency: ok
Jan  1 05:30:17 debian kernel: [    0.270000] Calibrating local timer... 349.99MHz.
Jan  1 05:30:17 debian kernel: [    0.340000] CPU1: Booted secondary processor
Jan  1 05:30:17 debian kernel: [    0.440000] Calibrating delay loop... 279.34 BogoMIPS (lpj=1396736)
Jan  1 05:30:17 debian kernel: [    0.670000] Brought up 2 CPUs
Jan  1 05:30:17 debian kernel: [    0.680000] SMP: Total of 2 processors activated (558.69 BogoMIPS).
Jan  1 05:30:17 debian kernel: [    0.690000] devtmpfs: initialized
Jan  1 05:30:17 debian kernel: [    0.700000] NET: Registered protocol family 16
Jan  1 05:30:17 debian kernel: [    0.700000] Number of DMA channels = 4, version = 4
Jan  1 05:30:17 debian kernel: [    0.710000] Reserving a DMA channel for DirectRAID
Jan  1 05:30:17 debian kernel: [    0.710000] Allocating 389 SRAM generic DMA descriptors
Jan  1 05:30:17 debian kernel: [    1.220000] PCIeA version/deviceID 082510b5
Jan  1 05:30:17 debian kernel: [    1.220000] PCIeB version/deviceID 082510b5
Jan  1 05:30:17 debian kernel: [    4.250000] ox820_pci_preinit() PCIEB link up timeout (00001814)
Jan  1 05:30:17 debian kernel: [    4.250000] ox820_pcie_setup_resources() Enabling PCIe Pre-Emphasis
Jan  1 05:30:17 debian kernel: [    4.260000] ox820_pciea_setup_resources() resource c781b140
Jan  1 05:30:17 debian kernel: [    4.260000] ox820_pciea_setup_resources()    io:      0x4be00000 - 0x4befffff
Jan  1 05:30:17 debian kernel: [    4.270000] ox820_pciea_setup_resources()    non-pre: 0x48000000 - 0x49ffffff
Jan  1 05:30:17 debian kernel: [    4.280000] ox820_pciea_setup_resources()    pre:     0x4a000000 - 0x4bdfffff
Jan  1 05:30:17 debian kernel: [    4.280000] PCI: bus0: Fast back to back transfers disabled
Jan  1 05:30:17 debian kernel: [    4.290000] PCI: bus1: Fast back to back transfers enabled
Jan  1 05:30:17 debian kernel: [    4.310000] bio: create slab <bio-0> at 0
Jan  1 05:30:17 debian kernel: [    4.320000] SCSI subsystem initialized
Jan  1 05:30:17 debian kernel: [    4.320000] usbcore: registered new interface driver usbfs
Jan  1 05:30:17 debian kernel: [    4.330000] usbcore: registered new interface driver hub
Jan  1 05:30:17 debian kernel: [    4.330000] usbcore: registered new device driver usb
Jan  1 05:30:17 debian kernel: [    4.370000] NET: Registered protocol family 2
Jan  1 05:30:17 debian kernel: [    4.370000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 05:30:17 debian kernel: [    4.380000] Switched to NOHz mode on CPU #0
Jan  1 05:30:17 debian kernel: [    4.380000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
Jan  1 05:30:17 debian kernel: [    4.380000] Switched to NOHz mode on CPU #1
Jan  1 05:30:17 debian kernel: [    4.390000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
Jan  1 05:30:17 debian kernel: [    4.400000] TCP: Hash tables configured (established 4096 bind 4096)
Jan  1 05:30:17 debian kernel: [    4.400000] TCP reno registered
Jan  1 05:30:17 debian kernel: [    4.410000] NET: Registered protocol family 1
Jan  1 05:30:17 debian kernel: [    4.410000] Create fragment cache
Jan  1 05:30:17 debian kernel: [    4.440000] fuse init (API version 7.12)
Jan  1 05:30:17 debian kernel: [    4.440000] msgmni has been set to 244
Jan  1 05:30:17 debian kernel: [    4.450000] alg: No test for stdrng (krng)
Jan  1 05:30:17 debian kernel: [    4.450000] io scheduler noop registered
Jan  1 05:30:17 debian kernel: [    4.460000] io scheduler anticipatory registered
Jan  1 05:30:17 debian kernel: [    4.460000] io scheduler deadline registered
Jan  1 05:30:17 debian kernel: [    4.460000] io scheduler cfq registered (default)
Jan  1 05:30:17 debian kernel: [    4.490000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Jan  1 05:30:17 debian kernel: [    4.500000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
Jan  1 05:30:17 debian kernel: [    4.510000] brd: module loaded
Jan  1 05:30:17 debian kernel: [    4.520000] loop: module loaded
Jan  1 05:30:17 debian kernel: [    4.530000] ox820sata: OX820 sata core.
Jan  1 05:30:17 debian kernel: [    4.530000] scsi0 : oxnassata
Jan  1 05:30:17 debian kernel: [    4.540000] scsi1 : oxnassata
Jan  1 05:30:17 debian kernel: [    4.540000] ata1: SATA max UDMA/133 irq 50
Jan  1 05:30:17 debian kernel: [    4.540000] ata2: SATA max UDMA/133 irq 50
Jan  1 05:30:17 debian kernel: [    4.910000] ata1: SATA link down (SStatus 0 SControl 300)
Jan  1 05:30:17 debian kernel: [    5.270000] ata2: SATA link down (SStatus 0 SControl 300)
Jan  1 05:30:17 debian kernel: [    5.270000] tun: Universal TUN/TAP device driver, 1.6
Jan  1 05:30:17 debian kernel: [    5.280000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan  1 05:30:17 debian kernel: [    5.280000] NAND: Page read time 40ms
Jan  1 05:30:17 debian kernel: [    5.290000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
Jan  1 05:30:17 debian kernel: [    5.300000] Scanning device for bad blocks
Jan  1 05:30:17 debian kernel: [    5.370000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
Jan  1 05:30:17 debian kernel: [    5.380000] 0x000000000000-0x000000e00000 : "boot"
Jan  1 05:30:17 debian kernel: [    5.380000] 0x000000e00000-0x000008000000 : "rootfs"
Jan  1 05:30:17 debian kernel: [    5.390000] UBI: attaching mtd2 to ubi0
Jan  1 05:30:17 debian kernel: [    5.390000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
Jan  1 05:30:17 debian kernel: [    5.400000] UBI: logical eraseblock size:    129024 bytes
Jan  1 05:30:17 debian kernel: [    5.400000] UBI: smallest flash I/O unit:    2048
Jan  1 05:30:17 debian kernel: [    5.410000] UBI: sub-page size:              512
Jan  1 05:30:17 debian kernel: [    5.410000] UBI: VID header offset:          512 (aligned 512)
Jan  1 05:30:17 debian kernel: [    5.420000] UBI: data offset:                2048
Jan  1 05:30:17 debian kernel: [    5.830000] UBI: attached mtd2 to ubi0
Jan  1 05:30:17 debian kernel: [    5.830000] UBI: MTD device name:            "rootfs"
Jan  1 05:30:17 debian kernel: [    5.840000] UBI: MTD device size:            114 MiB
Jan  1 05:30:17 debian kernel: [    5.840000] UBI: number of good PEBs:        912
Jan  1 05:30:17 debian kernel: [    5.850000] UBI: number of bad PEBs:         0
Jan  1 05:30:17 debian kernel: [    5.850000] UBI: max. allowed volumes:       128
Jan  1 05:30:17 debian kernel: [    5.860000] UBI: wear-leveling threshold:    4096
Jan  1 05:30:17 debian kernel: [    5.860000] UBI: number of internal volumes: 1
Jan  1 05:30:17 debian kernel: [    5.870000] UBI: number of user volumes:     1
Jan  1 05:30:17 debian kernel: [    5.870000] UBI: available PEBs:             0
Jan  1 05:30:17 debian kernel: [    5.880000] UBI: total number of reserved PEBs: 912
Jan  1 05:30:17 debian kernel: [    5.880000] UBI: number of PEBs reserved for bad PEB handling: 9
Jan  1 05:30:17 debian kernel: [    5.890000] UBI: max/mean erase counter: 2/0
Jan  1 05:30:17 debian kernel: [    5.890000] UBI: image sequence number: 0
Jan  1 05:30:17 debian kernel: [    5.890000] UBI: background thread "ubi_bgt0d" started, PID 313
Jan  1 05:30:17 debian kernel: [    5.890000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jan  1 05:30:17 debian kernel: [    5.890000] oxnas-ehci oxnas-ehci.0: OXNAS EHCI Host Controller
Jan  1 05:30:17 debian kernel: [    5.900000] oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
Jan  1 05:30:17 debian kernel: [    5.930000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x00000000
Jan  1 05:30:17 debian kernel: [    5.950000] oxnas-ehci oxnas-ehci.0: USB 0.0 started, EHCI 1.00
Jan  1 05:30:17 debian kernel: [    5.950000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jan  1 05:30:17 debian kernel: [    5.960000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jan  1 05:30:17 debian kernel: [    5.970000] usb usb1: Product: OXNAS EHCI Host Controller
Jan  1 05:30:17 debian kernel: [    5.970000] usb usb1: Manufacturer: Linux 2.6.31.6_SMP_820 ehci_hcd
Jan  1 05:30:17 debian kernel: [    5.980000] usb usb1: SerialNumber: usb
Jan  1 05:30:17 debian kernel: [    5.980000] usb usb1: configuration #1 chosen from 1 choice
Jan  1 05:30:17 debian kernel: [    5.990000] hub 1-0:1.0: USB hub found
Jan  1 05:30:17 debian kernel: [    5.990000] hub 1-0:1.0: 2 ports detected
Jan  1 05:30:17 debian kernel: [    6.000000] Initializing USB Mass Storage driver...
Jan  1 05:30:17 debian kernel: [    6.000000] usbcore: registered new interface driver usb-storage
Jan  1 05:30:17 debian kernel: [    6.010000] USB Mass Storage support registered.
Jan  1 05:30:17 debian kernel: [    6.010000] usbcore: registered new interface driver libusual
Jan  1 05:30:17 debian kernel: [    6.020000] mice: PS/2 mouse device common for all mice
Jan  1 05:30:17 debian kernel: [    6.020000] usbcore: registered new interface driver hiddev
Jan  1 05:30:17 debian kernel: [    6.030000] usbcore: registered new interface driver usbhid
Jan  1 05:30:17 debian kernel: [    6.040000] usbhid: v2.6:USB HID core driver
Jan  1 05:30:17 debian kernel: [    6.040000] TCP cubic registered
Jan  1 05:30:17 debian kernel: [    6.040000] NET: Registered protocol family 10
Jan  1 05:30:17 debian kernel: [    6.050000] lo: Disabled Privacy Extensions
Jan  1 05:30:17 debian kernel: [    6.050000] NET: Registered protocol family 17
Jan  1 05:30:17 debian kernel: [    6.060000] RPC: Registered udp transport module.
Jan  1 05:30:17 debian kernel: [    6.060000] RPC: Registered tcp transport module.
Jan  1 05:30:17 debian kernel: [    6.070000] Waiting for root device /dev/sda1...
Jan  1 05:30:17 debian kernel: [    6.310000] usb 1-1: new high speed USB device using oxnas-ehci and address 2
Jan  1 05:30:17 debian kernel: [    6.460000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
Jan  1 05:30:17 debian kernel: [    6.460000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Jan  1 05:30:17 debian kernel: [    6.470000] usb 1-1: Product: USB2.0 Hub
Jan  1 05:30:17 debian kernel: [    6.480000] usb 1-1: configuration #1 chosen from 1 choice
Jan  1 05:30:17 debian kernel: [    6.480000] hub 1-1:1.0: USB hub found
Jan  1 05:30:17 debian kernel: [    6.490000] hub 1-1:1.0: 4 ports detected
Jan  1 05:30:17 debian kernel: [    6.770000] usb 1-1.2: new high speed USB device using oxnas-ehci and address 3
Jan  1 05:30:17 debian kernel: [    6.920000] usb 1-1.2: New USB device found, idVendor=174c, idProduct=55aa
Jan  1 05:30:17 debian kernel: [    6.920000] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
Jan  1 05:30:17 debian kernel: [    6.930000] usb 1-1.2: Product: ASMT1051
Jan  1 05:30:17 debian kernel: [    6.930000] usb 1-1.2: Manufacturer: asmedia
Jan  1 05:30:17 debian kernel: [    6.940000] usb 1-1.2: SerialNumber: 123456789012
Jan  1 05:30:17 debian kernel: [    6.940000] usb 1-1.2: configuration #1 chosen from 1 choice
Jan  1 05:30:17 debian kernel: [    6.950000] scsi2 : SCSI emulation for USB Mass Storage devices
Jan  1 05:30:17 debian kernel: [   11.960000] scsi 2:0:0:0: Direct-Access     ASMT     2105             0    PQ: 0 ANSI: 6
Jan  1 05:30:17 debian kernel: [   11.970000] sd 2:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
Jan  1 05:30:17 debian kernel: [   11.980000] sd 2:0:0:0: [sda] Write Protect is off
Jan  1 05:30:17 debian kernel: [   12.000000]  sda: sda1 sda2 sda3
Jan  1 05:30:17 debian kernel: [   12.090000] sd 2:0:0:0: [sda] Attached SCSI disk
Jan  1 05:30:17 debian kernel: [   12.150000] kjournald starting.  Commit interval 5 seconds
Jan  1 05:30:17 debian kernel: [   12.150000] EXT3 FS on sda1, internal journal
Jan  1 05:30:17 debian kernel: [   12.150000] EXT3-fs: mounted filesystem with writeback data mode.
Jan  1 05:30:17 debian kernel: [   12.150000] VFS: Mounted root (ext3 filesystem) on device 8:1.
Jan  1 05:30:17 debian kernel: [   12.180000] devtmpfs: mounted
Jan  1 05:30:17 debian kernel: [   12.180000] Freeing init memory: 144K
Jan  1 05:30:17 debian kernel: [   13.240000] udev[391]: starting version 164
Jan  1 05:30:17 debian kernel: [   13.580000] PCI: enabling device 0000:00:00.0 (0140 -> 0142)
Jan  1 05:30:17 debian kernel: [   13.590000] 
Jan  1 05:30:17 debian kernel: [   13.590000] 
Jan  1 05:30:17 debian kernel: [   13.590000] === pAd = c8a3a000, size = 519160 ===
Jan  1 05:30:17 debian kernel: [   13.590000] 
Jan  1 05:30:17 debian kernel: [   13.600000] <-- RTMPAllocAdapterBlock, Status=0
Jan  1 05:30:17 debian kernel: [   13.600000] pAd->CSRBaseAddress =0xf5000000, csr_addr=0xf5000000!
Jan  1 05:30:17 debian kernel: [   15.560000] EXT3 FS on sda1, internal journal
Jan  1 05:30:17 debian kernel: [   15.830000] Turning off blinking LED.
Jan  1 05:30:18 debian kernel: [   18.950000] Probing for Synopsis GMAC, unit 0
Jan  1 05:30:18 debian kernel: [   18.950000] eth0: Tuning GMAC 0 RGMII timings
Jan  1 05:30:18 debian kernel: [   18.960000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
Jan  1 05:30:18 debian kernel: [   18.960000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
Jan  1 05:30:18 debian kernel: [   18.970000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
Jan  1 05:30:18 debian kernel: [   18.980000] eth0: Ethernet addr: 00:30:e0:00:00:00
Jan  1 05:30:18 debian kernel: [   18.980000] probe() eth0: Leon x2 clock



Edited 2 time(s). Last edit at 12/03/2015 06:00PM by bodhi.
Re: Pogo V3 Booting problem
December 03, 2015 06:15PM
agiorgio,

The stock u-boot does not use fw_printev/setenv. You will need to use blparam to print out the envs. Look in /usr/bin/cloudengines or /usr/sbin/cloudengines such directory.

Your best bet is to connect serial console. The rootfs is too old, I don't think we remember any quirks that needs to be worked around. Setting a correct MAC address in /etc/network/interfaces is a major thing.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo V3 Booting problem
December 04, 2015 09:24AM
Well, I don't have a serial cable handy, so I guess I'll have to look into that. This system was working fine, until the hard drive started failing. I was trying to reinstall on a replacement drive, and ran into all these issues.
Re: Pogo V3 Booting problem
December 04, 2015 10:13AM
I struggled for a long time without one, but serial cable has pride of place in my toolbox, and highly recommended :) Less than £5 I think I paid from Amazon.co.uk ... one like this :

http://www.amazon.co.uk/super9shop-PL2303HX-RS232-module-Converter/dp/B008AGDTA4/ref=sr_1_2?ie=UTF8&qid=1449245152&sr=8-2&keywords=usb+to+ttl+cable

or this :

http://www.amazon.co.uk/Fivesix-PL2303HX-RS232-Converter-Module/dp/B00WEMQ7IQ/ref=sr_1_5?ie=UTF8&qid=1449245530&sr=8-5&keywords=usb+to+ttl+cable

or this :

http://www.amazon.co.uk/UART-CP2102-Module-Serial-Converter/dp/B00AFRXKFU/ref=sr_1_1?ie=UTF8&qid=1449245556&sr=8-1&keywords=usb+to+ttl+cable

Mine is the all-in-on type with intelligence moulded into the usb plug ...

Cheers

Don Charisma ... because anything is possible with Charisma

My blog - http://DonCharisma.org
Our commercial site - http://DonCharisma.com
Re: Pogo V3 Booting problem
December 04, 2015 10:18AM
PS, openwrt also has an info page on serial cables, which I'm 99.9% sure is applicable to serial connections to embedded ARM boards :

https://wiki.openwrt.org/doc/hardware/port.serial.cables

Cheers

Don Charisma ... because anything is possible with Charisma

My blog - http://DonCharisma.org
Our commercial site - http://DonCharisma.com
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: