U-Boot 2015.10 for Iomega HMNHDCE
Posted by mari8b
|
mari8b
U-Boot 2015.10 for Iomega HMNHDCE August 09, 2018 08:51AM |
In the thread "2015.10 U-Boot for Pogoplug V3 (OXNAS OX820)" DaveP mentioned, that this U-Boot breath new life into Iomega HMNHDCE NAS. Is there somebody, who knew how to do it?
Quote
DaveP Re: 2015.10 U-Boot for Pogoplug V3 (OXNAS OX820) April 13, 2016 09:35PM Hello Bodhi, Fantastic work so far. I've been able to breath new life into my Iomega HMNHD CE thanks to your and others work. Do you know when the latest u-boot will be updated to include SATA support? -DaveP
|
mari8b
Re: U-Boot 2015.10 for Iomega HMNHDCE August 09, 2018 08:53AM |
This is serial log from my HMNHDCE:
Stage-1 Bootloader Mon Feb 7 16:35:00 MST 2011
Attempting to set PLLA to 600MHz ...
plla_ctrl0 : 0x0000021A
plla_ctrl1 : 0x00480000
plla_ctrl2 : 0x008F008B
plla_ctrl3 : 0x00000154
PLLA Set
Setup memory, testing
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001873C
Hdr CRC: 0x9C321E55
OK
Initialising disks
SATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: SAMSUNG HD103SJ Firm: 1AJ100E4 Ser#: S246J90Z193866
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
Device 1: not available
Environment successfully read from disk 0 primary image
U-Boot 1.1.2 (Sep 8 2012 - 10:03:04)
U-Boot code: 60D00000 -> 60D1873C BSS: -> 60D1C3CC
RAM Configuration:
Bank #0: 60000000 256 MB
SRAM Configuration:
64KB at 0x50000000
In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value
IDE read: device 0 block # 288, count 1 ... 1 blocks read: OK
Hit any key to stop autoboot: 0
IDE device 0: Model: SAMSUNG HD103SJ Firm: 1AJ100E4 Ser#: S246J90Z193866
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
... is now current device
IDE read: device 0 block # 1290, count 6144 ... 6144 blocks read: OK
IDE read: device 0 block # 16674, count 6144 ... 6144 blocks read: OK
## Booting image at 60500000 ...
Image Name: Linux-3.12.6
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2982328 Bytes = 2.8 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 61000000 ...
Image Name:
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3073589 Bytes = 2.9 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Starting kernel ...
Stage-1 Bootloader Mon Feb 7 16:35:00 MST 2011
Attempting to set PLLA to 600MHz ...
plla_ctrl0 : 0x0000021A
plla_ctrl1 : 0x00480000
plla_ctrl2 : 0x008F008B
plla_ctrl3 : 0x00000154
PLLA Set
Setup memory, testing
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001873C
Hdr CRC: 0x9C321E55
OK
Initialising disks
SATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: SAMSUNG HD103SJ Firm: 1AJ100E4 Ser#: S246J90Z193866
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
Device 1: not available
Environment successfully read from disk 0 primary image
U-Boot 1.1.2 (Sep 8 2012 - 10:03:04)
U-Boot code: 60D00000 -> 60D1873C BSS: -> 60D1C3CC
RAM Configuration:
Bank #0: 60000000 256 MB
SRAM Configuration:
64KB at 0x50000000
In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value
IDE read: device 0 block # 288, count 1 ... 1 blocks read: OK
Hit any key to stop autoboot: 0
IDE device 0: Model: SAMSUNG HD103SJ Firm: 1AJ100E4 Ser#: S246J90Z193866
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
... is now current device
IDE read: device 0 block # 1290, count 6144 ... 6144 blocks read: OK
IDE read: device 0 block # 16674, count 6144 ... 6144 blocks read: OK
## Booting image at 60500000 ...
Image Name: Linux-3.12.6
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2982328 Bytes = 2.8 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 61000000 ...
Image Name:
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3073589 Bytes = 2.9 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Starting kernel ...
|
mari8b
Re: U-Boot 2015.10 for Iomega HMNHDCE August 09, 2018 08:57AM |
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 09, 2018 12:44PM |
Admin Registered: 13 years ago Posts: 18,543 |
mari8b,
> Starting kernel ...[/i]
There should be more after this (the kernel boot log).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Starting kernel ...[/i]
There should be more after this (the kernel boot log).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 09, 2018 12:46PM |
Admin Registered: 13 years ago Posts: 18,543 |
mari8b,
> In the thread "2015.10 U-Boot for Pogoplug V3
> (OXNAS OX820)" DaveP mentioned, that this U-Boot
> breath new life into Iomega HMNHDCE NAS. Is there
> somebody, who knew how to do it?
Please post link to the post you've quoted above.
Update: I found it. Unfortunately DaveP did not post the boot log with new u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/09/2018 12:52PM by bodhi.
> In the thread "2015.10 U-Boot for Pogoplug V3
> (OXNAS OX820)" DaveP mentioned, that this U-Boot
> breath new life into Iomega HMNHDCE NAS. Is there
> somebody, who knew how to do it?
Please post link to the post you've quoted above.
Update: I found it. Unfortunately DaveP did not post the boot log with new u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/09/2018 12:52PM by bodhi.
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 10, 2018 12:46AM |
Registered: 9 years ago Posts: 442 |
If I recall correctly the OX820 will try to boot from SATA first, although it appears that OpenWRT uses a chain-loaded U-Boot to boot the current kernel on this hardware. You may find some useful information at https://github.com/olderzeus/Iomega-HMNHDCE that would help get a newer U-Boot.
Ray
Ray
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 10, 2018 03:07AM |
Admin Registered: 13 years ago Posts: 18,543 |
rayknight Wrote:
-------------------------------------------------------
> If I recall correctly the OX820 will try to boot
> from SATA first, although it appears that OpenWRT
> uses a chain-loaded U-Boot to boot the current
> kernel on this hardware. You may find some useful
> information at
> https://github.com/olderzeus/Iomega-HMNHDCE that
> would help get a newer U-Boot.
>
> Ray
Apparently, DaveP installed my released uboot and rootfs, not ones from other source.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> If I recall correctly the OX820 will try to boot
> from SATA first, although it appears that OpenWRT
> uses a chain-loaded U-Boot to boot the current
> kernel on this hardware. You may find some useful
> information at
> https://github.com/olderzeus/Iomega-HMNHDCE that
> would help get a newer U-Boot.
>
> Ray
Apparently, DaveP installed my released uboot and rootfs, not ones from other source.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
mari8b
Re: U-Boot 2015.10 for Iomega HMNHDCE August 10, 2018 04:06AM |
bodhi Wrote:
-------------------------------------------------------
> mari8b,
>
> > Starting kernel ...
>
> There should be more after this (the kernel boot
> log).
There is much more... didn't know it's important, it's about starting Debian...
------
Moderator edit: please use code tags (formatted code button) to post log
Edited 1 time(s). Last edit at 08/10/2018 04:49AM by bodhi.
-------------------------------------------------------
> mari8b,
>
> > Starting kernel ...
>
> There should be more after this (the kernel boot
> log).
There is much more... didn't know it's important, it's about starting Debian...
Uncompressing Linux... done, booting the kernel. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.12.6_OXNAS+ (root@PogoplugPro) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Sun Jan 12 08:07:56 CST 2014 [ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine: PLXTECH NAS782X SoC (Flattened Device Tree), model: Iomega Home Media Network Hard Drive, Cloud Edition [ 0.000000] Memory policy: ECC disabled, Data cache writealloc [ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map [ 0.000000] PERCPU: Embedded 7 pages/cpu @c07b7000 s6464 r8192 d14016 u32768 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [ 0.000000] Kernel command line: root=/dev/sda1 console=ttyS0,115200 elevator=cfq mem=256M poweroutage=yes mac_adr=0x00,0xd0,0xb8,0x19,0x34,0x6b [ 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] Memory: 250960K/262144K available (4149K kernel code, 208K rwdata, 1068K rodata, 150K init, 208K bss, 11184K reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 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 - 0xc05206f4 (5218 kB) [ 0.000000] .init : 0xc0521000 - 0xc0546940 ( 151 kB) [ 0.000000] .data : 0xc0548000 - 0xc057c020 ( 209 kB) [ 0.000000] .bss : 0xc057c028 - 0xc05b0158 ( 209 kB) [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] NR_IRQS:160 [ 0.000000] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 42949ms [ 0.000000] Console: colour dummy device 80x30 [ 0.000268] Calibrating delay loop... 239.61 BogoMIPS (lpj=1198080) [ 0.069939] pid_max: default: 32768 minimum: 301 [ 0.070272] Mount-cache hash table entries: 512 [ 0.071672] CPU: Testing write buffer coherency: ok [ 0.072215] Setting up static identity map for 0xc03f3338 - 0xc03f3370 [ 0.074101] CPU1: Booted secondary processor [ 0.140172] Brought up 2 CPUs [ 0.140206] SMP: Total of 2 processors activated. [ 0.141765] devtmpfs: initialized [ 0.145756] pinctrl core: initialized pinctrl subsystem [ 0.146250] NET: Registered protocol family 16 [ 0.146956] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.150894] gpio-oxnas 44000000.gpio: at address d0846000 [ 0.151170] gpio-oxnas 44100000.gpio: at address d0848000 [ 0.151823] pinctrl-oxnas pinctrl.5: initialized OX820 pinctrl driver [ 0.158694] bio: create slab <bio-0> at 0 [ 0.160015] vgaarb: loaded [ 0.160524] SCSI subsystem initialized [ 0.161400] usbcore: registered new interface driver usbfs [ 0.161507] usbcore: registered new interface driver hub [ 0.161786] usbcore: registered new device driver usb [ 0.161971] pps_core: LinuxPPS API ver. 1 registered [ 0.161991] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.162035] PTP clock support registered [ 0.164794] Switched to clocksource rps_clocksource_timer [ 0.175936] cfg80211: Calling CRDA to update world regulatory domain [ 0.180846] NET: Registered protocol family 2 [ 0.181872] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 0.181962] TCP bind hash table entries: 2048 (order: 2, 16384 bytes) [ 0.182033] TCP: Hash tables configured (established 2048 bind 2048) [ 0.182138] TCP: reno registered [ 0.182167] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 0.182220] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 0.182658] NET: Registered protocol family 1 [ 0.183068] Unpacking initramfs... [ 0.637496] Freeing initrd memory: 2996K (c1001000 - c12ee000) [ 0.668492] fuse init (API version 7.22) [ 0.669329] msgmni has been set to 496 [ 0.671915] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 0.671946] io scheduler noop registered [ 0.671959] io scheduler deadline registered [ 0.672289] io scheduler cfq registered (default) [ 0.672791] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled [ 0.674170] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A [ 1.097003] console [ttyS0] enabled [ 1.102456] scsi0 : sata_oxnas [ 1.105948] ata1: SATA max UDMA/133 irq 50 [ 1.110156] ox820sata: reseting SATA core [ 1.111457] stmmac - user ID: 0x12, Synopsys ID: 0x35 [ 1.111462] Ring mode enabled [ 1.111472] DMA HW capability register supported [ 1.111472] Enhanced/Alternate descriptors [ 1.111475] Enabled extended descriptors [ 1.111482] RX Checksum Offload Engine supported (type 2) [ 1.111485] TX Checksum insertion supported [ 1.111488] Wake-Up On Lan supported [ 1.111493] Enable RX Mitigation via HW Watchdog Timer [ 1.181043] libphy: stmmac: probed [ 1.184512] eth0: PHY ID 001cc914 at 0 IRQ 0 (stmmac-0:00) active [ 1.190592] eth0: PHY ID 001cc914 at 2 IRQ 0 (stmmac-0:02) [ 1.196167] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.202670] ehci-pci: EHCI PCI platform driver [ 1.207610] oxnas-ehci 40200100.ehci: EHCI Host Controller [ 1.213120] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1 [ 1.220922] oxnas-ehci 40200100.ehci: irq 39, io mem 0x40200100 [ 1.244277] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00 [ 1.250688] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 1.257502] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.264732] usb usb1: Product: EHCI Host Controller [ 1.269593] usb usb1: Manufacturer: Linux 3.12.6_OXNAS+ ehci_hcd [ 1.275589] usb usb1: SerialNumber: 40200100.ehci [ 1.281256] hub 1-0:1.0: USB hub found [ 1.285140] hub 1-0:1.0: 2 ports detected [ 1.289879] usbcore: registered new interface driver usb-storage [ 1.296663] input: gpio-keys.6 as /devices/gpio-keys.6/input/input0 [ 1.305036] usbcore: registered new interface driver usbhid [ 1.310589] usbhid: USB HID core driver [ 1.314800] TCP: cubic registered [ 1.319480] NET: Registered protocol family 10 [ 1.325621] sit: IPv6 over IPv4 tunneling driver [ 1.332336] ip6_gre: GRE over IPv6 tunneling driver [ 1.338257] NET: Registered protocol family 17 [ 1.604293] usb 1-2: new high-speed USB device number 2 using oxnas-ehci [ 1.669995] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 1.681940] ata1.00: ATA-8: SAMSUNG HD103SJ, 1AJ100E4, max UDMA/133 [ 1.688192] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 0/32) [ 1.700751] ata1.00: configured for UDMA/133 [ 1.705748] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 1AJ1 PQ: 0 ANSI: 5 [ 1.715192] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB) [ 1.723555] sd 0:0:0:0: [sda] Write Protect is off [ 1.728673] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.765611] usb 1-2: New USB device found, idVendor=0951, idProduct=168a [ 1.772377] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1.779509] usb 1-2: Product: DT Micro [ 1.783316] usb 1-2: Manufacturer: Kingston [ 1.787507] usb 1-2: SerialNumber: 50E549C20280BC31700001F5 [ 1.793653] sda: sda1 sda2 [ 1.794280] usb-storage 1-2:1.0: USB Mass Storage device detected [ 1.803415] scsi1 : usb-storage 1-2:1.0 [ 1.805416] sd 0:0:0:0: [sda] Attached SCSI disk [ 1.805729] Freeing unused kernel memory: 148K (c0521000 - c0546000) Loading, please wait... [ 1.960110] udevd[67]: starting version 175 Begin: Loading essential drivers ... [ 2.790466] md: raid0 personality registered for level 0 [ 2.815267] md: raid1 personality registered for level 1 [ 2.838264] md: linear personality registered for level -1 [ 2.880409] device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: dm-devel@redhat.com [ 2.889582] scsi 1:0:0:0: Direct-Access Kingston DT Micro PMAP PQ: 0 ANSI: 0 CCS [ 2.931591] md: raid10 personality registered for level 10 [ 2.940180] xor: measuring software checksum speed [ 3.039933] arm4regs : 831.200 MB/sec [ 3.139919] 8regs : 421.200 MB/sec [ 3.239920] 32regs : 513.200 MB/sec [ 3.244090] xor: using function: arm4regs (831.200 MB/sec) [ 3.420454] raid6: int32x1 26 MB/s [ 3.590272] raid6: int32x2 46 MB/s [ 3.760174] raid6: int32x4 47 MB/s [ 3.930237] raid6: int32x8 48 MB/s [ 3.933969] raid6: using algorithm int32x8 (48 MB/s) [ 3.938910] raid6: using intx1 recovery algorithm [ 3.956280] md: raid6 personality registered for level 6 [ 3.961774] md: raid5 personality registered for level 5 [ 3.967078] md: raid4 personality registered for level 4 [ 3.974466] device-mapper: raid: Loading target version 1.5.2 done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD arrays ... mdadm: No arrays found in config file or automatically Failure: failed to assemble all arrays. done. done. Begin: Running /scripts/local-premount ... done. modprobe: module ext3 not found in modules.dep [ 4.277708] sd 1:0:0:0: [sdb] 15356160 512-byte logical blocks: (7.86 GB/7.32 GiB) [ 4.285934] sd 1:0:0:0: [sdb] Write Protect is off [ 4.291302] sd 1:0:0:0: [sdb] No Caching mode page found [ 4.296640] sd 1:0:0:0: [sdb] Assuming drive cache: write through [ 4.309040] sd 1:0:0:0: [sdb] No Caching mode page found [ 4.314439] sd 1:0:0:0: [sdb] Assuming drive cache: write through [ 4.358289] sdb: sdb1 [ 4.365972] sd 1:0:0:0: [sdb] No Caching mode page found [ 4.371397] sd 1:0:0:0: [sdb] Assuming drive cache: write through [ 4.377484] sd 1:0:0:0: [sdb] Attached SCSI removable disk [ 10.277624] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (4) [ 10.288015] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 10.946918] EXT4-fs (sda1): 1 orphan inode deleted [ 10.951792] EXT4-fs (sda1): recovery complete [ 11.130631] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 11.166853] EXT2-fs (sdb1): warning: mounting ext3 filesystem as ext2 [ 11.319063] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem [ 11.334128] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. INIT: version 2.88 booting [info] Using makefile-style concurrent boot in runlevel S. [....] Starting the hotplug events dispatcher: udevd[ 13.314365] udevd[280]: starting version 175 . ok [ ok ] Synthesizing the initial hotplug events...done. [ ok ] Waiting for /dev to be fully populated...done. [ ok ] Activating swap...done. [ 15.959751] EXT4-fs (sda1): re-mounted. Opts: (null) [....] Checking root file system...fsck from util-linux 2.25.2 /dev/sda1: clean, 12284/524288 files, 197129/2097152 blocks done. [ 16.424650] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro [ ok ] Activating lvm and md swap...done. [....] Checking file systems...fsck from util-linux 2.25.2 done. [ ok ] Loading kernel modules...done. [ ok ] Cleaning up temporary files... /tmp. [ ok ] Mounting local filesystems...done. [ ok ] Activating swapfile swap...done. [ ok ] Cleaning up temporary files.... [ ok ] Setting kernel variables ...done. [ 21.059340] eth0: device MAC address da:0d:10:ca:8b:57 [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.2.2 Copyright 2004-2011 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/da:0d:10:ca:8b:57 Sending on LPF/eth0/da:0d:10:ca:8b:57 Sending on Socket/fallback DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15 DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 No DHCPOFFERS received. Trying recorded lease 192.168.8.130 PING 192.168.8.48 (192.168.8.48) 56(84) bytes of data. --- 192.168.8.48 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms No working leases in persistent database - sleeping. done. [ ok ] Starting rpcbind daemon.... [ ok ] Starting NFS common utilities: statd. [ ok ] Cleaning up temporary files.... INIT: Entering runlevel: 2 [info] Using makefile-style concurrent boot in runlevel 2. [ ok ] Starting NTP server: ntpd. [ ok ] Starting rpcbind daemon...[....] Already running.. [....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd... 1336 (syslogd) . ok [ ok ] Starting system message bus: dbus. [ ok ] Starting NFS common utilities: statd. [ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon. [warn] Not starting NFS kernel daemon: no exports. ... (warning). [ ok ] Starting OpenBSD Secure Shell server: sshd. [....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd... 1339 (klogd) . ok Debian GNU/Linux 8 debian ttyS0 debian login:
------
Moderator edit: please use code tags (formatted code button) to post log
Edited 1 time(s). Last edit at 08/10/2018 04:49AM by bodhi.
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 10, 2018 05:00AM |
Admin Registered: 13 years ago Posts: 18,543 |
Ok so it is a Pogoplug Pro V3 clone.
You can proceed to install uboot.2015.10-tld-2:
https://forum.doozan.com/read.php?3,16017
and if desired, a new rootfs Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2:
https://forum.doozan.com/read.php?2,16044
Note: the current rootfs you have is OK to use, and you can upgrade the kernel to linux-4.4.133-oxnas-tld-1 (tarball linux-4.4.133-oxnas-tld-1.bodhi.tar.bz2), if you don't want to upgrade rootfs becasue you have insalled too many packages.
==============
One thing to pay attention to before installing new u-boot is olderzeus' rootfs and setup do not have the MTD partition defined. These are needed before new u-boot can be installed.
But do take a look at the 2 threads I posted above to see if you are comfortable with performing these procedures. And come back and let me know you want to proceed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You can proceed to install uboot.2015.10-tld-2:
https://forum.doozan.com/read.php?3,16017
and if desired, a new rootfs Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2:
https://forum.doozan.com/read.php?2,16044
Note: the current rootfs you have is OK to use, and you can upgrade the kernel to linux-4.4.133-oxnas-tld-1 (tarball linux-4.4.133-oxnas-tld-1.bodhi.tar.bz2), if you don't want to upgrade rootfs becasue you have insalled too many packages.
==============
One thing to pay attention to before installing new u-boot is olderzeus' rootfs and setup do not have the MTD partition defined. These are needed before new u-boot can be installed.
1. uBoot envs config and mtd partitions must be defined as followed in your rootfs cat /etc/fw_env.config # pogoplug v3 /dev/mtd0 0x00100000 0x20000 0x20000 cat /proc/mtd dev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "data"
But do take a look at the 2 threads I posted above to see if you are comfortable with performing these procedures. And come back and let me know you want to proceed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
mari8b
Re: U-Boot 2015.10 for Iomega HMNHDCE August 10, 2018 06:21AM |
bodhi Wrote:
-------------------------------------------------------
> One thing to pay attention to before installing
> new u-boot is olderzeus' rootfs and setup do not
> have the MTD partition defined. These are needed
> before new u-boot can be installed.
How should I define MTD partitions? There is a /etc/fw_env.config in the rootfs...
-------------------------------------------------------
> One thing to pay attention to before installing
> new u-boot is olderzeus' rootfs and setup do not
> have the MTD partition defined. These are needed
> before new u-boot can be installed.
How should I define MTD partitions? There is a /etc/fw_env.config in the rootfs...
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 10, 2018 08:13AM |
Admin Registered: 13 years ago Posts: 18,543 |
Note the 1st step
The mtdpart definition needs to be passed into the kernel bootargs with u-boot env. So we nned to look at your current mtdparts (if any) and u-boot env.
1. In Debian
2. Power up interrupt serial console and
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
1. uBoot envs config and mtd partitions must be defined as followed in your rootfs
cat /etc/fw_env.config
# pogoplug v3
/dev/mtd0 0x00100000 0x20000 0x20000
cat /proc/mtd
dev: size erasesize name
mtd0: 00e00000 00020000 "boot"
mtd1: 07200000 00020000 "data"
If you don't have /etc/fw_env.config file in your system, then you are running either stock Pogo OS, or earlier version of Arch Linux ARM. Go ahead and create this file with the above content.
The mtdpart definition needs to be passed into the kernel bootargs with u-boot env. So we nned to look at your current mtdparts (if any) and u-boot env.
1. In Debian
cat /proc/mtd
2. Power up interrupt serial console and
printenv
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 10, 2018 08:22AM |
Registered: 5 years ago Posts: 11 |
1. cat /proc/mtd (none MTD partitions)
2. printenv (is it what you need?)
root@debian:~# cat /proc/mtd dev: size erasesize name
2. printenv (is it what you need?)
PLX>>printenv bootcmd=run select0 load1 load_rd1 boot || run lightled select0 load2 load_rd2 extinguishled boot || lightled bootdelay=3 baudrate=115200 ethaddr=00:30:e0:00:00:01 ipaddr=172.31.0.128 serverip=172.31.0.100 autoload=n netmask=255.255.0.0 bootfile="uImage" select0=ide dev 0 load1=ide read 0x60500000 50a 1800 load2=ide read 0x60500000 e3e8 1800 load_rd1=ide read 0x61000000 4122 1800 load_rd2=ide read 0x61000000 7d3a 1800 lightled=ledfail 1 extinguishled=ledfail 0 boot=bootm 60500000 61000000 stdin=serial stdout=serial stderr=serial bootargs=root=/dev/sda1 console=ttyS0,115200 elevator=cfq mem=256M poweroutage=yes mac_adr=0x00,0xd0,0xb8,0x19,0x34,0x6b
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 10, 2018 08:38AM |
Admin Registered: 13 years ago Posts: 18,543 |
mari8b,
> root@debian:~# cat /proc/mtd
> dev: size erasesize name
Ok. That's what I expected.
> 2. printenv (is it what you need?)
Yes, it is.
> bootargs=root=/dev/sda1 console=ttyS0,115200
> elevator=cfq mem=256M poweroutage=yes
> mac_adr=0x00,0xd0,0xb8,0x19,0x34,0x6b
The bootargs need to have mtdparts env in it.
Power up, interrupt serial console, and execute:
Let it boot into Debian, login and check:
If it shows the mtdparts as below, then you are ready to install u-boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> root@debian:~# cat /proc/mtd
> dev: size erasesize name
Ok. That's what I expected.
> 2. printenv (is it what you need?)
Yes, it is.
> bootargs=root=/dev/sda1 console=ttyS0,115200
> elevator=cfq mem=256M poweroutage=yes
> mac_adr=0x00,0xd0,0xb8,0x19,0x34,0x6b
The bootargs need to have mtdparts env in it.
Power up, interrupt serial console, and execute:
setenv mtdparts 'mtdparts=41000000.nand:14m(boot),-(data)' setenv bootargs 'root=/dev/sda1 console=ttyS0,115200 elevator=cfq mem=256M poweroutage=yes mac_adr=0x00,0xd0,0xb8,0x19,0x34,0x6b $(mtdparts)' boot
Let it boot into Debian, login and check:
cat /proc/mtd
If it shows the mtdparts as below, then you are ready to install u-boot.
dev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "data"
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 13, 2018 02:20AM |
Registered: 5 years ago Posts: 11 |
Hi bodhi,
thank you very much for your support, but no MTD partitions was created...
Now it looks like this:
1.
2.
Did I forget something?
(There is no 'boot' command like you mentioned in your code, but I think, this is not important...)
Edited 1 time(s). Last edit at 08/13/2018 02:34AM by mari8b.
thank you very much for your support, but no MTD partitions was created...
Now it looks like this:
1.
root@debian:~# cat /proc/mtd dev: size erasesize name
2.
PLX>>printenv bootcmd=run select0 load1 load_rd1 boot || run lightled select0 load2 load_rd2 extinguishled boot || lightled bootdelay=3 baudrate=115200 ethaddr=00:30:e0:00:00:01 ipaddr=172.31.0.128 serverip=172.31.0.100 autoload=n netmask=255.255.0.0 bootfile="uImage" select0=ide dev 0 load1=ide read 0x60500000 50a 1800 load2=ide read 0x60500000 e3e8 1800 load_rd1=ide read 0x61000000 4122 1800 load_rd2=ide read 0x61000000 7d3a 1800 lightled=ledfail 1 extinguishled=ledfail 0 boot=bootm 60500000 61000000 mtdparts=mtdparts=41000000.nand:14m(boot),-(data) stdin=serial stdout=serial stderr=serial bootargs=root=/dev/sda1 console=ttyS0,115200 elevator=cfq $(mtdparts) mem=256M poweroutage=yes mac_adr=0x00,0xd0,0xb8,0x19,0x34,0x6b Environment size: 718/8188 bytes
Did I forget something?
(There is no 'boot' command like you mentioned in your code, but I think, this is not important...)
Edited 1 time(s). Last edit at 08/13/2018 02:34AM by mari8b.
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 13, 2018 04:06AM |
Admin Registered: 13 years ago Posts: 18,543 |
Power up, interrupt serial console, and execute:
Login into Debian, and
and post the entired log (from u-boot banner until the last line you see in your terminal) here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
setenv bootargs 'root=/dev/sda1 console=ttyS0,115200 mtdparts=41000000.nand:14m(boot),-(data)' run bootcmd
Login into Debian, and
cat /proc/mtd
and post the entired log (from u-boot banner until the last line you see in your terminal) here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 13, 2018 04:25AM |
Registered: 5 years ago Posts: 11 |
Nothing has changed - no MTD partitions...
setenv bootargs 'root=/dev/sda1 console=ttyS0,115200 mtdparts=41000000.nand:14m(boot),-(data)'
PLX>>printenv
bootcmd=run select0 load1 load_rd1 boot || run lightled select0 load2 load_rd2 extinguishled boot || lightled
bootdelay=3
baudrate=115200
ethaddr=00:30:e0:00:00:01
ipaddr=172.31.0.128
serverip=172.31.0.100
autoload=n
netmask=255.255.0.0
bootfile="uImage"
select0=ide dev 0
load1=ide read 0x60500000 50a 1800
load2=ide read 0x60500000 e3e8 1800
load_rd1=ide read 0x61000000 4122 1800
load_rd2=ide read 0x61000000 7d3a 1800
lightled=ledfail 1
extinguishled=ledfail 0
boot=bootm 60500000 61000000
stdin=serial
stdout=serial
stderr=serial
bootargs=root=/dev/sda1 console=ttyS0,115200 mtdparts=41000000.nand:14m(boot),-(data)
Environment size: 621/8188 bytes
PLX>>run bootcmd
IDE device 0: Model: SAMSUNG HD103SJ Firm: 1AJ100E4 Ser#: S246J90Z193866
Type: Hard Disk
Capacity: 131071.9 MB = 127.9 GB (268435455 x 512)
... is now current device
IDE read: device 0 block # 1290, count 6144 ... 6144 blocks read: OK
IDE read: device 0 block # 16674, count 6144 ... 6144 blocks read: OK
## Booting image at 60500000 ...
Image Name: Linux-3.12.6
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2982328 Bytes = 2.8 MB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 61000000 ...
Image Name:
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3073589 Bytes = 2.9 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.12.6_OXNAS+ (root@PogoplugPro) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Sun Jan 12 08:07:56 CST 2014
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: PLXTECH NAS782X SoC (Flattened Device Tree), model: Iomega Home Media Network Hard Drive, Cloud Edition
[ 0.000000] Memory policy: ECC disabled, Data cache writealloc
[ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
[ 0.000000] PERCPU: Embedded 7 pages/cpu @c07b7000 s6464 r8192 d14016 u32768
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: root=/dev/sda1 console=ttyS0,115200 mtdparts=41000000.nand:14m(boot),-(data)
[ 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] Memory: 250960K/262144K available (4149K kernel code, 208K rwdata, 1068K rodata, 150K init, 208K bss, 11184K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 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 - 0xc05206f4 (5218 kB)
[ 0.000000] .init : 0xc0521000 - 0xc0546940 ( 151 kB)
[ 0.000000] .data : 0xc0548000 - 0xc057c020 ( 209 kB)
[ 0.000000] .bss : 0xc057c028 - 0xc05b0158 ( 209 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] NR_IRQS:160
[ 0.000000] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 42949ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000273] Calibrating delay loop... 239.61 BogoMIPS (lpj=1198080)
[ 0.069941] pid_max: default: 32768 minimum: 301
[ 0.070269] Mount-cache hash table entries: 512
[ 0.071687] CPU: Testing write buffer coherency: ok
[ 0.072235] Setting up static identity map for 0xc03f3338 - 0xc03f3370
[ 0.074137] CPU1: Booted secondary processor
[ 0.140167] Brought up 2 CPUs
[ 0.140198] SMP: Total of 2 processors activated.
[ 0.141754] devtmpfs: initialized
[ 0.145879] pinctrl core: initialized pinctrl subsystem
[ 0.146362] NET: Registered protocol family 16
[ 0.147010] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.151042] gpio-oxnas 44000000.gpio: at address d0846000
[ 0.151344] gpio-oxnas 44100000.gpio: at address d0848000
[ 0.152084] pinctrl-oxnas pinctrl.5: initialized OX820 pinctrl driver
[ 0.159239] bio: create slab <bio-0> at 0
[ 0.160570] vgaarb: loaded
[ 0.161064] SCSI subsystem initialized
[ 0.161920] usbcore: registered new interface driver usbfs
[ 0.162030] usbcore: registered new interface driver hub
[ 0.162321] usbcore: registered new device driver usb
[ 0.162501] pps_core: LinuxPPS API ver. 1 registered
[ 0.162519] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.162565] PTP clock support registered
[ 0.165171] Switched to clocksource rps_clocksource_timer
[ 0.166220] cfg80211: Calling CRDA to update world regulatory domain
[ 0.181189] NET: Registered protocol family 2
[ 0.182182] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.182279] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.182353] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.182464] TCP: reno registered
[ 0.182499] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.182561] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.183009] NET: Registered protocol family 1
[ 0.183457] Unpacking initramfs...
[ 0.637647] Freeing initrd memory: 2996K (c1001000 - c12ee000)
[ 0.654005] fuse init (API version 7.22)
[ 0.655019] msgmni has been set to 496
[ 0.657625] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.657653] io scheduler noop registered
[ 0.657666] io scheduler deadline registered
[ 0.658009] io scheduler cfq registered (default)
[ 0.658511] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.659909] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A
[ 1.079825] console [ttyS0] enabled
[ 1.085363] scsi0 : sata_oxnas
[ 1.088737] ata1: SATA max UDMA/133 irq 50
[ 1.094440] stmmac - user ID: 0x12, Synopsys ID: 0x35
[ 1.099476] Ring mode enabled
[ 1.099993] ox820sata: reseting SATA core
[ 1.106562] DMA HW capability register supported
[ 1.111075] Enhanced/Alternate descriptors
[ 1.115453] Enabled extended descriptors
[ 1.119452] RX Checksum Offload Engine supported (type 2)
[ 1.124925] TX Checksum insertion supported
[ 1.129172] Wake-Up On Lan supported
[ 1.132815] Enable RX Mitigation via HW Watchdog Timer
[ 1.167001] libphy: stmmac: probed
[ 1.170408] eth0: PHY ID 001cc914 at 0 IRQ 0 (stmmac-0:00) active
[ 1.176535] eth0: PHY ID 001cc914 at 2 IRQ 0 (stmmac-0:02)
[ 1.182103] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.188672] ehci-pci: EHCI PCI platform driver
[ 1.193646] oxnas-ehci 40200100.ehci: EHCI Host Controller
[ 1.199196] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1
[ 1.207016] oxnas-ehci 40200100.ehci: irq 39, io mem 0x40200100
[ 1.234298] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00
[ 1.240696] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.247508] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.254727] usb usb1: Product: EHCI Host Controller
[ 1.259589] usb usb1: Manufacturer: Linux 3.12.6_OXNAS+ ehci_hcd
[ 1.265589] usb usb1: SerialNumber: 40200100.ehci
[ 1.271188] hub 1-0:1.0: USB hub found
[ 1.275082] hub 1-0:1.0: 2 ports detected
[ 1.279879] usbcore: registered new interface driver usb-storage
[ 1.286661] input: gpio-keys.6 as /devices/gpio-keys.6/input/input0
[ 1.295004] usbcore: registered new interface driver usbhid
[ 1.300559] usbhid: USB HID core driver
[ 1.304778] TCP: cubic registered
[ 1.309501] NET: Registered protocol family 10
[ 1.315676] sit: IPv6 over IPv4 tunneling driver
[ 1.322465] ip6_gre: GRE over IPv6 tunneling driver
[ 1.328384] NET: Registered protocol family 17
[ 1.594324] usb 1-2: new high-speed USB device number 2 using oxnas-ehci
[ 1.620019] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 1.631979] ata1.00: ATA-8: SAMSUNG HD103SJ, 1AJ100E4, max UDMA/133
[ 1.638236] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 1.650821] ata1.00: configured for UDMA/133
[ 1.655825] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD103SJ 1AJ1 PQ: 0 ANSI: 5
[ 1.665546] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 1.673815] sd 0:0:0:0: [sda] Write Protect is off
[ 1.678876] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.721692] sda: sda1 sda2
[ 1.727032] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.732044] Freeing unused kernel memory: 148K (c0521000 - c0546000)
Loading, please wait...
[ 1.759290] usb 1-2: New USB device found, idVendor=0951, idProduct=168a
[ 1.766087] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.773222] usb 1-2: Product: DT Micro
[ 1.777044] usb 1-2: Manufacturer: Kingston
[ 1.781237] usb 1-2: SerialNumber: 50E549C20280BC31700001F5
[ 1.788239] usb-storage 1-2:1.0: USB Mass Storage device detected
[ 1.795143] scsi1 : usb-storage 1-2:1.0
[ 1.920143] udevd[65]: starting version 175
Begin: Loading essential drivers ... [ 2.758620] md: raid0 personality registered for level 0
[ 2.783541] md: raid1 personality registered for level 1
[ 2.796989] scsi 1:0:0:0: Direct-Access Kingston DT Micro PMAP PQ: 0 ANSI: 0 CCS
[ 2.810539] sd 1:0:0:0: [sdb] 15356160 512-byte logical blocks: (7.86 GB/7.32 GiB)
[ 2.819151] sd 1:0:0:0: [sdb] Write Protect is off
[ 2.830156] sd 1:0:0:0: [sdb] No Caching mode page found
[ 2.835481] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[ 2.845388] md: linear personality registered for level -1
[ 2.859361] sd 1:0:0:0: [sdb] No Caching mode page found
[ 2.864747] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[ 2.893207] sdb: sdb1
[ 2.901760] sd 1:0:0:0: [sdb] No Caching mode page found
[ 2.907197] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[ 2.913297] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 2.952230] device-mapper: ioctl: 4.26.0-ioctl (2013-08-15) initialised: dm-devel@redhat.com
[ 2.995932] md: raid10 personality registered for level 10
[ 3.007180] xor: measuring software checksum speed
[ 3.109952] arm4regs : 827.200 MB/sec
[ 3.209955] 8regs : 407.200 MB/sec
[ 3.309928] 32regs : 513.200 MB/sec
[ 3.314101] xor: using function: arm4regs (827.200 MB/sec)
[ 3.492116] raid6: int32x1 26 MB/s
[ 3.661050] raid6: int32x2 47 MB/s
[ 3.830440] raid6: int32x4 47 MB/s
[ 4.000791] raid6: int32x8 48 MB/s
[ 4.004546] raid6: using algorithm int32x8 (48 MB/s)
[ 4.009487] raid6: using intx1 recovery algorithm
[ 4.029808] md: raid6 personality registered for level 6
[ 4.035210] md: raid5 personality registered for level 5
[ 4.040522] md: raid4 personality registered for level 4
[ 4.047774] device-mapper: raid: Loading target version 1.5.2
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD arrays ... mdadm: No arrays found in config file or automatically
Failure: failed to assemble all arrays.
done.
done.
Begin: Running /scripts/local-premount ... done.
modprobe: module ext3 not found in modules.dep
[ 10.369057] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2
[ 10.409697] EXT2-fs (sdb1): warning: mounting ext3 filesystem as ext2
[ 10.451563] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[ 10.466749] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[ 12.542492] udevd[276]: starting version 175
. ok
[ ok ] Synthesizing the initial hotplug events...done.
[ ok ] Waiting for /dev to be fully populated...done.
[ ok ] Activating swap...done.
[ 15.179253] EXT4-fs (sda1): re-mounted. Opts: (null)
[....] Checking root file system...fsck from util-linux 2.25.2
/dev/sda1: clean, 12308/524288 files, 250958/2097152 blocks
done.
[ 15.643970] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.25.2
done.
[ ok ] Loading kernel modules...done.
[ ok ] Cleaning up temporary files... /tmp.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[ 20.229719] eth0: device MAC address b6:58:aa:ea:3b:0e
[ 22.230177] libphy: stmmac-0:00 - Link is Up - 100/Full
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/b6:58:aa:ea:3b:0e
Sending on LPF/eth0/b6:58:aa:ea:3b:0e
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPNAK from 192.168.8.48
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.8.48
DHCPACK from 192.168.8.48
bound to 192.168.8.142 -- renewal in 35835 seconds.
done.
[ ok ] Starting rpcbind daemon....
[ ok ] Starting NFS common utilities: statd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting rpcbind daemon...[....] Already running..
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1345 (syslogd)
. ok
[ ok ] Starting system message bus: dbus.
[ ok ] Starting NFS common utilities: statd.
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1352 (klogd)
. ok
Debian GNU/Linux 8 debian ttyS0
debian login: root
Password:
Last login: Mon Aug 13 02:18:50 PDT 2018 on ttyS0
Linux debian 3.12.6_OXNAS+ #1 SMP Sun Jan 12 08:07:56 CST 2014 armv6l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@debian:~# cat /proc/mtd
dev: size erasesize name
root@debian:~#
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 13, 2018 05:51AM |
Admin Registered: 13 years ago Posts: 18,543 |
So the kernel on your rootfs is not good. No NAND mtd support.
Time to try booting with Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2, as I mentioned:
https://forum.doozan.com/read.php?3,64624,64754#msg-64754
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
[ 0.000000] Linux version 3.12.6_OXNAS+ (root@PogoplugPro) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Sun Jan 12 08:07:56 CST 2014
Time to try booting with Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2, as I mentioned:
https://forum.doozan.com/read.php?3,64624,64754#msg-64754
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 13, 2018 06:54AM |
Registered: 5 years ago Posts: 11 |
bodhi Wrote:
-------------------------------------------------------
> ...
> Time to try booting with
> Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2, as
> I mentioned...
But I think, that booting another kernel is not possible without new U-boot...
On my device are the 'uImage' (kernel) and 'initrd' image written in the first 32MB on the HDD. These newer kernels are much bigger as the old one (4.4MB vs 2.8MB), so it can't be written to the first 32MB...
So what do you think is the procedure for booting with Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2?
Preparation of the first 32MB of the HDD looks like this:
Maybe can be the boot command changed to boot kernel and initrd from rootfs/boot directory, but I really don't know how...
Edited 2 time(s). Last edit at 08/13/2018 07:58AM by mari8b.
-------------------------------------------------------
> ...
> Time to try booting with
> Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2, as
> I mentioned...
But I think, that booting another kernel is not possible without new U-boot...
On my device are the 'uImage' (kernel) and 'initrd' image written in the first 32MB on the HDD. These newer kernels are much bigger as the old one (4.4MB vs 2.8MB), so it can't be written to the first 32MB...
So what do you think is the procedure for booting with Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2?
Preparation of the first 32MB of the HDD looks like this:
dd if=bootrom.warpped of=$1 bs=512 dd if=stage1.wrapped of=$1 seek=34 dd if=u-boot.sd.wrapped of=$1 seek=154 dd if=u-boot.sd.env of=$1 seek=558 dd if=uImage.wrapped of=$1 seek=1290 dd if=initrd.wrapped of=$1 seek=16674 dd if=serial.warpped of=$1 seek=57080 dd if=stage1.wrapped of=$1 seek=57088 dd if=u-boot.sd.wrapped of=$1 seek=57208 dd if=uImage.wrapped of=$1 seek=58344
Maybe can be the boot command changed to boot kernel and initrd from rootfs/boot directory, but I really don't know how...
Edited 2 time(s). Last edit at 08/13/2018 07:58AM by mari8b.
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 13, 2018 07:46AM |
Admin Registered: 13 years ago Posts: 18,543 |
mari8b,
I meant to create the Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 rootfs on USB.
And then in serial console, enter a set of new u-boot envs to boot with USB rootfs. This will be a little slow (I don't have my old notes with me so I will need to either find the instruction in forum old threads, or write them from scratch).
But booting from USB is safer, so that you can avoid touching your current HDD rootfs.
So take a look at the kernel/rootfs thread.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I meant to create the Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 rootfs on USB.
And then in serial console, enter a set of new u-boot envs to boot with USB rootfs. This will be a little slow (I don't have my old notes with me so I will need to either find the instruction in forum old threads, or write them from scratch).
But booting from USB is safer, so that you can avoid touching your current HDD rootfs.
So take a look at the kernel/rootfs thread.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 13, 2018 09:54AM |
Registered: 5 years ago Posts: 11 |
I have an empty HDD, so I don't care about touching my current HDD rootfs, I don't need to boot from USB now, but if it's necessary, I would do it.
I have read many threads, but didn't find instructions to boot the Iomega HMNHDCE another way than the first 32MB.
Here is described, what is stored in the first 32MB of the HDD
I have read many threads, but didn't find instructions to boot the Iomega HMNHDCE another way than the first 32MB.
Here is described, what is stored in the first 32MB of the HDD
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 13, 2018 11:10AM |
Admin Registered: 13 years ago Posts: 18,543 |
mari8b,
> I have an empty HDD, so I don't care about
> touching my current HDD rootfs, I don't need to
> boot from USB now, but if it's necessary, I would
> do it.
> I have read many threads, but didn't find instructions to boot the Iomega HMNHDCE another way than the first 32MB.
Once you've installed the new u-boot, this particular HDD scheme is no longer needed. You can boot with Debian rootfs on HDD or USB, as a normal system. So I would not waste time making it work now. I would just go straight to booting USB rootfs, get it booting, install new u-boot, and create a new HDD rootfs.
It is more convenient to have a booting system while you work on installing stuff, so keeping the stock HDD rootfs intact is a good idea.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I have an empty HDD, so I don't care about
> touching my current HDD rootfs, I don't need to
> boot from USB now, but if it's necessary, I would
> do it.
> I have read many threads, but didn't find instructions to boot the Iomega HMNHDCE another way than the first 32MB.
Once you've installed the new u-boot, this particular HDD scheme is no longer needed. You can boot with Debian rootfs on HDD or USB, as a normal system. So I would not waste time making it work now. I would just go straight to booting USB rootfs, get it booting, install new u-boot, and create a new HDD rootfs.
It is more convenient to have a booting system while you work on installing stuff, so keeping the stock HDD rootfs intact is a good idea.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 14, 2018 03:38AM |
Registered: 5 years ago Posts: 11 |
I think, I'm starting to understand...
There's no NAND flash on the Iomega Home Media CE (HMNHDCE). Everything (including U-boot) is written on the HDD. So if I understand it right, there's no need for MTD partitions support...
Description of the first 32MB of the HDD:
Here is the code to write everything needed to the first 32MB:
So how did DaveP do it with the new U-boot?
There's no NAND flash on the Iomega Home Media CE (HMNHDCE). Everything (including U-boot) is written on the HDD. So if I understand it right, there's no need for MTD partitions support...
Description of the first 32MB of the HDD:
start/sector size content 0 512 Legacy MBR 1 1536 GPT Partition table 34 8736 Stage-1 Bootloader 154 103552 U-Boot 558 At least 608 U-Boot environment 1290 2189216 uImage kernel 16674 2787216 uImage initrd 57080 5 0x69 0xD3 0xAB 0x52 0x31 unknown - not Serial number, not the MAC address, same on all devices 57088 4640 Stage-1 Bootloader (2nd copy) 57208 103568 U-Boot (2nd copy) 58344 2189216 uImage kernel (2nd copy)
Here is the code to write everything needed to the first 32MB:
dd if=bootrom.wrapped of=$1 bs=512 dd if=stage1.wrapped of=$1 seek=34 dd if=u-boot.sd.wrapped of=$1 seek=154 dd if=u-boot.sd.env of=$1 seek=558 dd if=uImage.wrapped of=$1 seek=1290 dd if=initrd.wrapped of=$1 seek=16674 dd if=serial.warpped of=$1 seek=57080 dd if=stage1.wrapped of=$1 seek=57088 dd if=u-boot.sd.wrapped of=$1 seek=57208 dd if=uImage.wrapped of=$1 seek=58344
So how did DaveP do it with the new U-boot?
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 14, 2018 04:16AM |
Admin Registered: 13 years ago Posts: 18,543 |
mari8b Wrote:
-------------------------------------------------------
> I think, I'm starting to understand...
>
> There's no NAND flash on the Iomega Home Media CE
> (HMNHDCE). Everything (including U-boot) is
> written on the HDD. So if I understand it right,
> there's no need for MTD partitions support...
>
> Description of the first 32MB of the HDD:
>
> Here is the code to write everything needed to the
> first 32MB:
>
> So how did DaveP do it with the new U-boot?
My guess is DaveP flashed (using dd):
- SPL image to Stage-1 Bootloader
- new u-boot image to U-Boot
- new u-boot env image to U-Boot environment
But that is only an educated guess. That's what I would do if I have serial console and not afraid of bricking the box, and have cloned the HDD to another HDD as backup.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I think, I'm starting to understand...
>
> There's no NAND flash on the Iomega Home Media CE
> (HMNHDCE). Everything (including U-boot) is
> written on the HDD. So if I understand it right,
> there's no need for MTD partitions support...
>
> Description of the first 32MB of the HDD:
>
> start/sector size content > 0 512 Legacy MBR > 1 1536 GPT Partition table > 34 8736 Stage-1 Bootloader > 154 103552 U-Boot > 558 At least 608 U-Boot environment > 1290 2189216 uImage kernel > 16674 2787216 uImage initrd > 57080 5 0x69 0xD3 0xAB 0x52 0x31 > unknown - not Serial number, not the MAC > address, same on all devices > 57088 4640 Stage-1 Bootloader (2nd copy) > 57208 103568 U-Boot (2nd copy) > 58344 2189216 uImage kernel (2nd copy) > >>
> Here is the code to write everything needed to the
> first 32MB:
>
> dd if=bootrom.wrapped of=$1 bs=512 > dd if=stage1.wrapped of=$1 seek=34 > dd if=u-boot.sd.wrapped of=$1 seek=154 > dd if=u-boot.sd.env of=$1 seek=558 > dd if=uImage.wrapped of=$1 seek=1290 > dd if=initrd.wrapped of=$1 seek=16674 > dd if=serial.warpped of=$1 seek=57080 > dd if=stage1.wrapped of=$1 seek=57088 > dd if=u-boot.sd.wrapped of=$1 seek=57208 > dd if=uImage.wrapped of=$1 seek=58344 >>
> So how did DaveP do it with the new U-boot?
34 8736 Stage-1 Bootloader 154 103552 U-Boot 558 At least 608 U-Boot environment
My guess is DaveP flashed (using dd):
- SPL image to Stage-1 Bootloader
- new u-boot image to U-Boot
- new u-boot env image to U-Boot environment
But that is only an educated guess. That's what I would do if I have serial console and not afraid of bricking the box, and have cloned the HDD to another HDD as backup.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 14, 2018 09:51AM |
Registered: 5 years ago Posts: 11 |
bodhi Wrote:
> My guess is DaveP flashed (using dd):
>
> - SPL image to Stage-1 Bootloader
> - new u-boot image to U-Boot
> - new u-boot env image to U-Boot environment
>
> But that is only an educated guess. That's what I
> would do if I have serial console and not afraid
> of bricking the box, and have cloned the HDD to
> another HDD as backup.
It's not working...
New U-boot is too big. I really can't imagine how DaveP did it (if he did it).
I think the only way for a new Debian is to compile new kernel, that is small enough (max 2918400 bytes) for loading with current U-boot. I don't know if it's possible, I have no experience with that.
Here are scripts (settings, patches) from seidler2547, who did the first Debian kernel for HMNHDCE...
> My guess is DaveP flashed (using dd):
>
> - SPL image to Stage-1 Bootloader
> - new u-boot image to U-Boot
> - new u-boot env image to U-Boot environment
>
> But that is only an educated guess. That's what I
> would do if I have serial console and not afraid
> of bricking the box, and have cloned the HDD to
> another HDD as backup.
It's not working...
New U-boot is too big. I really can't imagine how DaveP did it (if he did it).
I think the only way for a new Debian is to compile new kernel, that is small enough (max 2918400 bytes) for loading with current U-boot. I don't know if it's possible, I have no experience with that.
Here are scripts (settings, patches) from seidler2547, who did the first Debian kernel for HMNHDCE...
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 14, 2018 01:23PM |
Admin Registered: 13 years ago Posts: 18,543 |
Here is how boot with direct SATA on Pogo Pro
https://forum.doozan.com/read.php?2,32994,33021#msg-33021
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?2,32994,33021#msg-33021
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE August 15, 2018 07:52AM |
Registered: 5 years ago Posts: 11 |
|
Re: U-Boot 2015.10 for Iomega HMNHDCE July 20, 2019 08:59AM |
Registered: 4 years ago Posts: 10 |
Hello!
I have iomega HMNHDCE where I have oldzeus's uboot and debian buster installed. But I can't use it with open vpn. Old kernel can't create tun.
So i found this forum and used direct sata boot instructions with spl for pogoplug pro. My problem is that iomega 's ram is 256M not 128M as pogoplug so my checksum verification is failing at boot?
My question is: is it possible for whoever created spl for pogoplug to make version with 256m ram support please! And please keep rom support, because believe it or not I've soldered 128m nand to iomega HMNHDCE motherboard and it is recognized at boot by spl. (It shows as 16m at first boot and 128m at reboot)?
My intention is to get sata boot to be able to flush ny nand with pogoplug's spl for nand and boot rootfs from USB to OMV. This way my sata could be whipped and/or swapped without compromising ability to boot.
I also have 16Gb nand on hand and wonder if I can solder and be able to boot to it. So with 16Gb nand I'll have OMV on nand no need for USB-boot.
Whoever will reply to me, please give me more detailed instructions, I'm new in Linux (something you can do in 30mins I'll do in 3 weeks googling on how to).
Thank you for your support and help!!!
I have iomega HMNHDCE where I have oldzeus's uboot and debian buster installed. But I can't use it with open vpn. Old kernel can't create tun.
So i found this forum and used direct sata boot instructions with spl for pogoplug pro. My problem is that iomega 's ram is 256M not 128M as pogoplug so my checksum verification is failing at boot?
My question is: is it possible for whoever created spl for pogoplug to make version with 256m ram support please! And please keep rom support, because believe it or not I've soldered 128m nand to iomega HMNHDCE motherboard and it is recognized at boot by spl. (It shows as 16m at first boot and 128m at reboot)?
My intention is to get sata boot to be able to flush ny nand with pogoplug's spl for nand and boot rootfs from USB to OMV. This way my sata could be whipped and/or swapped without compromising ability to boot.
I also have 16Gb nand on hand and wonder if I can solder and be able to boot to it. So with 16Gb nand I'll have OMV on nand no need for USB-boot.
Whoever will reply to me, please give me more detailed instructions, I'm new in Linux (something you can do in 30mins I'll do in 3 weeks googling on how to).
Thank you for your support and help!!!
|
Re: U-Boot 2015.10 for Iomega HMNHDCE July 21, 2019 12:18AM |
Admin Registered: 13 years ago Posts: 18,543 |
sobir,
Connect seral console, and post the entire serial bootlog here. I'll take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Connect seral console, and post the entire serial bootlog here. I'll take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: U-Boot 2015.10 for Iomega HMNHDCE July 21, 2019 01:31PM |
Registered: 4 years ago Posts: 10 |
hi bodhi!
here is what I did today:
I booted to usb wheezy from odzeus's uboot to empty hdd and here is log from screen:
and it stuck there. I'm not getting to second stage. I don't have any distro in /dev/sda1 is it a proble? I think at list it should load second stage and tell no filesystem found or smth?
I'm supprised to see chechsum verification Ok, was failing before.
then i took ddh out to linux PC and unzipped wheezy from oldzeus to rootfs and tryed it here:
I'm not expert, I think is it because my ram is 256M but spl uses 128M module and it screws up memory?
Anyway that was all logs I have.
Thank you for your help. I really don't know what I would do without you.!!!
Edited 3 time(s). Last edit at 07/21/2019 01:59PM by sobir.
here is what I did today:
I booted to usb wheezy from odzeus's uboot to empty hdd and here is log from screen:
root@OXNAS:~$uname -a
Linux OXNAS 3.12.6_OXNAS+ #1 SMP Sun Jan 12 08:07:56 CST 2014 armv6l GNU/Linux
root@OXNAS:~$dd if=/dev/zero of=/dev/sda bs=1M count=34
34+0 records in
34+0 records out
35651584 bytes (36 MB) copied, 1.01906 s, 35.0 MB/s
root@OXNAS:~$parted /dev/sda
GNU Parted 2.3
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel gpt
(parted) print
Model: ATA WDC WD800JD-75MS (scsi)
Disk /dev/sda: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
(parted) mkpart
Partition name? []? rootfs
File system type? [ext2]? ext3
Start? 2048M
End? 10240M
(parted) print
Model: ATA WDC WD800JD-75MS (scsi)
Disk /dev/sda: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 2048MB 10.2GB 8193MB ext3 rootfs
(parted) quit
Information: You may need to update /etc/fstab.
root@OXNAS:~$mkfs.ext3 /dev/sda1
root@OXNAS:~$mount /dev/sda1 /mnt
root@OXNAS:~$cd /mnt
Root@OXNAS:/mnt$rm -R lost+found
root@OXNAS:/mnt$tar -zxvf /root/ox820-sata-uboot.tar.gz
root@OXNAS:/mnt/boot$ls
dts u-boot.img uImage uInitrd
u-boot.env u-boot-spl.bin uImage_2.6.31.14_OX820_1.2_shv.Pro
root@OXNAS:/mnt/boot$nano script
#!/bin/sh
# uncomment line below and set to the correct disk
disk=/dev/sda
#pay attention to fit yourself.this is my situation
if [ -z "${disk}" ] ; then
echo "You must uncomment/set the 'disk' variable"
exit -1
fi
workarea=/mnt/boot
stage1File=$workarea/u-boot-spl.bin
perl <<EOF | dd of="$disk" bs=512
print "\x00" x 0x1a4;
print "\x00\x5f\x01\x00";
print "\x00\xdf\x00\x00";
print "\x00\x80\x00\x00";
print "\x00" x (0x1b0 -0x1a4 -12 );
print "\x22\x80\x00\x00";
print "\x22\x00\x00\x00";
print "\x00\x80\x00\x00";
EOF
if [ -f $stage1File ];then
echo "Writing stage 1"
dd if=$stage1File of="$disk" bs=512 seek=34
fi
root@OXNAS:/mnt/boot$chmod +x ./script
root@OXNAS:/mnt/boot$./script
0+1 records in
0+1 records out
444 bytes (444 B) copied, 0.0750592 s, 5.9 kB/s
Writing stage 1
62+1 records in
62+1 records out
32120 bytes (32 kB) copied, 0.015895 s, 2.0 MB/s
root@OXNAS:/mnt/boot$reboot
################################### reboot #############################
U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34)
Boot device: SATA
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1
PLLA Set
Bus 0: OK
Device 0:
** File not found /boot/bootargs.bin **
U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS
DRAM: 128 MiB
IDE: Bus 0: OK
Device 0: Model: WDC WD800JD-75MSA3 Firm: 10.01E04 Ser#: WD-WMAM9AR84678
Type: Hard Disk
Supports 48-bit addressing
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
NAND: 16 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 3 ^H^H^H 2
OX820 # setenv uinitrd_addr '0x60e00000'
OX820 # setenv uimage_addr '0x60500000'
OX820 # setenv dtb_addr '0x62c00000'
OX820 # setenv ide_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev$
OX820 # setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr'
OX820 # setenv dt_load_dtb 'ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug$
OX820 # setenv dt_load_initrd 'ext2load ide 0:1 $uinitrd_addr /boot/uInitrd'
OX820 # setenv dt_load_uimage 'ext2load ide 0:1 $uimage_addr /boot/uImage'
OX820 # setenv dt_ide_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load$
OX820 # setenv dt_ide_bootcmd 'run ide_set_bootargs; run dt_ide_boot'
OX820 # setenv dt_bootcmd_ide 'ide reset; run dt_ide_bootcmd; reset'
OX820 # setenv bootcmd 'run dt_bootcmd_ide'
OX820 # boot
Reset IDE: Bus 0: OK
Device 0: Model: WDC WD800JD-75MSA3 Firm: 10.01E04 Ser#: WD-WMAM9AR84678
Type: Hard Disk
Supports 48-bit addressing
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
3676848 bytes read in 812 ms (4.3 MiB/s)
2103272 bytes read in 469 ms (4.3 MiB/s)
7029 bytes read in 27 ms (253.9 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.12.13-oxnas-tld-5
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3676784 Bytes = 3.5 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.12.13-oxnas-tld-5
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 2103208 Bytes = 2 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c26000, end 67e277a8 ... OK
Loading Device Tree to 67c21000, end 67c25b74 ... OK
Led: GREEN
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
and it stuck there. I'm not getting to second stage. I don't have any distro in /dev/sda1 is it a proble? I think at list it should load second stage and tell no filesystem found or smth?
I'm supprised to see chechsum verification Ok, was failing before.
then i took ddh out to linux PC and unzipped wheezy from oldzeus to rootfs and tryed it here:
U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34)
Boot device: SATA
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1
PLLA Set
Bus 0: OK
Device 0:
** File not found /boot/bootargs.bin **
U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS
DRAM: 128 MiB
IDE: Bus 0: OK
Device 0: Model: WDC WD800JD-75MSA3 Firm: 10.01E04 Ser#: WD-WMAM9AR84678
Type: Hard Disk
Supports 48-bit addressing
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
NAND: 16 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 3 ^H^H^H 0
OX820 # setenv uinitrd_addr '0x60e00000'
OX820 # setenv uimage_addr '0x60500000'
OX820 # setenv dtb_addr '0x62c00000'
OX820 # setenv ide_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev$
OX820 # setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr'
OX820 # setenv dt_load_dtb 'ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug$
OX820 # setenv dt_load_initrd 'ext2load ide 0:1 $uinitrd_addr /boot/uInitrd'
OX820 # setenv dt_load_uimage 'ext2load ide 0:1 $uimage_addr /boot/uImage'
OX820 # setenv dt_ide_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load$
OX820 # setenv dt_ide_bootcmd 'run ide_set_bootargs; run dt_ide_boot'
OX820 # setenv dt_bootcmd_ide 'ide reset; run dt_ide_bootcmd; reset'
OX820 # setenv bootcmd 'run dt_bootcmd_ide'
OX820 # boot
Reset IDE: Bus 0: OK
Device 0: Model: WDC WD800JD-75MSA3 Firm: 10.01E04 Ser#: WD-WMAM9AR84678
Type: Hard Disk
Supports 48-bit addressing
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
3676848 bytes read in 855 ms (4.1 MiB/s)
2103272 bytes read in 485 ms (4.1 MiB/s)
7029 bytes read in 28 ms (245.1 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.12.13-oxnas-tld-5
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3676784 Bytes = 3.5 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.12.13-oxnas-tld-5
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 2103208 Bytes = 2 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... Bad Data CRC
Led: ORANGE (Failed)
I'm not expert, I think is it because my ram is 256M but spl uses 128M module and it screws up memory?
Anyway that was all logs I have.
Thank you for your help. I really don't know what I would do without you.!!!
Edited 3 time(s). Last edit at 07/21/2019 01:59PM by sobir.
|
Re: U-Boot 2015.10 for Iomega HMNHDCE July 21, 2019 11:45PM |
Admin Registered: 13 years ago Posts: 18,543 |
sobir,
No, you got it boot far enough. It is not memory problem. You have more RAM than the SPL set it to. So once you got it booting into Debian, you can only use 128MB, which is perfectly fine.
When you see this error:
It means the rootfs was not prepared cleanly. That SPL should get pass the first stage without error.
Try again to prepare the disk.
At this point, you should do a few sync and then list the files to see the size of these files are sane.
Then run the script.
And then after running the script, before reboot, sync the disk again
See if it helps.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
> 3676848 bytes read in 855 ms (4.1 MiB/s)
> 2103272 bytes read in 485 ms (4.1 MiB/s)
> 7029 bytes read in 28 ms (245.1 KiB/s)
> ## Booting kernel from Legacy Image at 60500000
> ...
> Image Name: Linux-3.12.13-oxnas-tld-5
> Image Type: ARM Linux Kernel Image
> (uncompressed)
> Data Size: 3676784 Bytes = 3.5 MiB
> Load Address: 60008000
> Entry Point: 60008000
> Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 60e00000 ...
> Image Name: initramfs-3.12.13-oxnas-tld-5
> Image Type: ARM Linux RAMDisk Image (gzip
> compressed)
> Data Size: 2103208 Bytes = 2 MiB
> Load Address: 60000000
> Entry Point: 60000000
> Verifying Checksum ... Bad Data CRC
>
> Led: ORANGE (Failed)
> [/code]
> I'm not expert, I think is it because my ram is
> 256M but spl uses 128M module and it screws up
> memory?
>
No, you got it boot far enough. It is not memory problem. You have more RAM than the SPL set it to. So once you got it booting into Debian, you can only use 128MB, which is perfectly fine.
When you see this error:
PLLA Set Bus 0: OK Device 0: ** File not found /boot/bootargs.bin **
It means the rootfs was not prepared cleanly. That SPL should get pass the first stage without error.
Try again to prepare the disk.
Quote
root@OXNAS:~$mkfs.ext3 /dev/sda1
root@OXNAS:~$mount /dev/sda1 /mnt
root@OXNAS:~$cd /mnt
Root@OXNAS:/mnt$rm -R lost+found
root@OXNAS:/mnt$tar -zxvf /root/ox820-sata-uboot.tar.gz
At this point, you should do a few sync and then list the files to see the size of these files are sane.
sync sync ls -larth /mnt/boot/
Then run the script.
And then after running the script, before reboot, sync the disk again
sync sync reboot
See if it helps.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
