All,
I'm going to release kernel linux-4.20.6-kirkwood-tld-1 shortly.
I'm going to release kernel linux-4.20.6-kirkwood-tld-1 shortly.
↧
Re: Linux Kernel 4.19.0 Kirkwood package and Debian rootfs
↧
Re: NETGEAR STORA - Bad Magic Number
Hi Bodhi,
I've perform a nand scrub and now no Bad eraseblock.
I'm trying to flash the uboot having this issue
Dirk Pitt.
I've perform a nand scrub and now no Bad eraseblock.
dmesg | grep -i 'bad' [ 8.865697] Scanning device for bad blocksStrange thing because on uboot I've this output
Netgear Stora> nand bad Device 0 bad blocks: 048a0000 076c0000 0b560000
I'm trying to flash the uboot having this issue
root@debian:~/tools# ./flash_erase /dev/mtd0 0 4
flash_erase: error!: /dev/mtd0
error 13 (Permission denied)
root@debian:~/tools# ./nandwrite /dev/mtd0 uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb
nandwrite: error!: /dev/mtd0
error 13 (Permission denied)
Is the NAND in read only mode. On debian I'm logged as root...
Dirk Pitt.
↧
↧
Re: NETGEAR STORA - Bad Magic Number
Dirk Pitt,
> Is the NAND in read only mode. On debian I'm
> logged as root...
It should be writeable.
Please post
> Is the NAND in read only mode. On debian I'm
> logged as root...
It should be writeable.
Please post
dmesg cat /proc/mtd
↧
Re: Troubleshooting Freeze Issue on Debian 9 - SSH, Ping, Logs
I've cloned the rootfs onto a USB 2.0 thumb drive with ext4 (with journaling enabled) and that seems to have resolved the issue, thank you!
↧
Re: GoFlex Home Battery Replacement
asterix Wrote:
-------------------------------------------------------
> By the way, how about the copy speed of your goflex home? mine dropped to around 15mb/s recently, don't know why. Usually around 30mb/s in the pass.
>
15 mbps less than 2MBps. R U sure it is not 15 MBps?
-------------------------------------------------------
> By the way, how about the copy speed of your goflex home? mine dropped to around 15mb/s recently, don't know why. Usually around 30mb/s in the pass.
>
15 mbps less than 2MBps. R U sure it is not 15 MBps?
↧
↧
Re: NETGEAR STORA - Bad Magic Number
Hi Bodhi,
root@debian:~/tools# dmesg
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.12.1-kirkwood-tld-1 (root@tldDebian) (gcc versio7
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=000539f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] OF: fdt: Machine model: NETGEAR MS2000 / MS2110 aka Stora
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] On node 0 totalpages: 32768
[ 0.000000] free_area_init_node: node 0, pgdat c0d9e084, node_mem_map c7ef900
[ 0.000000] Normal zone: 256 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 32768 pages, LIFO batch:7
[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pa2
[ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootw
[ 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: 109420K/131072K available (8192K kernel code, 716K rwdat)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xc8800000 - 0xff800000 ( 880 MB)
lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc0900000 (9184 kB)
.init : 0xc0c00000 - 0xc0d00000 (1024 kB)
.data : 0xc0d00000 - 0xc0db3274 ( 717 kB)
.bss : 0xc0db9b9c - 0xc0e01e60 ( 289 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xfs
[ 0.000009] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 1073s
[ 0.000053] Switching to timer-based delay loop, resolution 5ns
[ 0.000618] Console: colour dummy device 80x30
[ 0.000659] Calibrating delay loop (skipped), value calculated using timer f)
[ 0.000687] pid_max: default: 32768 minimum: 301
[ 0.000919] Security Framework initialized
[ 0.001067] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001091] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.002128] CPU: Testing write buffer coherency: ok
[ 0.003349] Setting up static identity map for 0x100000 - 0x100058
[ 0.003676] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.007621] devtmpfs: initialized
[ 0.012971] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, ms
[ 0.013003] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.013480] prandom: seed boundary self test passed
[ 0.017987] prandom: 100 self tests passed
[ 0.018001] pinctrl core: initialized pinctrl subsystem
[ 0.019395] NET: Registered protocol family 16
[ 0.019981] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.021995] cpuidle: using governor ladder
[ 0.022080] cpuidle: using governor menu
[ 0.022627] Feroceon L2: Enabling L2
[ 0.022684] Feroceon L2: Cache support initialised.
[ 0.023117] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet
[ 0.029225] No ATAGs?
[ 0.040495] vgaarb: loaded
[ 0.040890] SCSI subsystem initialized
[ 0.041110] libata version 3.00 loaded.
[ 0.041458] usbcore: registered new interface driver usbfs
[ 0.041550] usbcore: registered new interface driver hub
[ 0.041656] usbcore: registered new device driver usb
[ 0.043021] clocksource: Switched to clocksource orion_clocksource
[ 0.150709] VFS: Disk quotas dquot_6.6.0
[ 0.150801] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.163578] NET: Registered protocol family 2
[ 0.164453] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.164485] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.164510] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.164616] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.164645] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.164858] NET: Registered protocol family 1
[ 0.165354] RPC: Registered named UNIX socket transport module.
[ 0.165369] RPC: Registered udp transport module.
[ 0.165378] RPC: Registered tcp transport module.
[ 0.165386] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.165401] PCI: CLS 0 bytes, default 32
[ 0.165667] Unpacking initramfs...
[ 0.958574] Freeing initrd memory: 7076K
[ 0.958759] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.959912] audit: initializing netlink subsys (disabled)
[ 0.960503] Initialise system trusted keyrings
[ 0.960571] Key type blacklist registered
[ 0.960683] audit: type=2000 audit(0.957:1): state=initialized audit_enabled1
[ 0.960794] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[ 0.960877] zbud: loaded
[ 0.962049] NFS: Registering the id_resolver key type
[ 0.962081] Key type id_resolver registered
[ 0.962093] Key type id_legacy registered
[ 0.962113] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.962126] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.962362] jffs2: version 2.2. (NAND) (SUMMARY) \xffffffc2\xffffffa9 2001-.
[ 0.962595] fuse init (API version 7.26)
[ 0.963121] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 0.963428] orangefs_init: module version upstream loaded
[ 0.963442] SGI XFS with ACLs, security attributes, realtime, no debug enabld
[ 2.553030] random: fast init done
[ 8.015939] Key type asymmetric registered
[ 8.015959] Asymmetric key parser 'x509' registered
[ 8.016038] Block layer SCSI generic (bsg) driver version 0.4 loaded (major )
[ 8.016052] io scheduler noop registered
[ 8.016062] io scheduler deadline registered
[ 8.016161] io scheduler cfq registered (default)
[ 8.017656] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl drir
[ 8.019937] mvebu-pcie mbus@f1000000:pcie-controller@82000000: PCI host brid0
[ 8.019963] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 8.019979] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 8.019995] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 8.020010] pci_bus 0000:00: scanning bus
[ 8.020054] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[ 8.020104] pci 0000:00:01.0: calling pci_fixup_ide_bases+0x0/0x40
[ 8.020379] pci_bus 0000:00: fixups for bus
[ 8.020394] PCI: bus0: Fast back to back transfers disabled
[ 8.020413] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[ 8.020423] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reg
[ 8.020444] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[ 8.020596] pci_bus 0000:01: scanning bus
[ 8.020608] pci_bus 0000:01: fixups for bus
[ 8.020615] PCI: bus1: Fast back to back transfers enabled
[ 8.020629] pci_bus 0000:01: bus scan returning with max=01
[ 8.020642] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 8.020655] pci_bus 0000:00: bus scan returning with max=01
[ 8.020671] pci 0000:00:01.0: fixup irq: got 0
[ 8.020679] pci 0000:00:01.0: assigning IRQ 00
[ 8.020705] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 8.020817] pcieport 0000:00:01.0: enabling bus mastering
[ 8.021355] mv_xor f1060800.xor: Marvell shared XOR driver
[ 8.084070] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy sg )
[ 8.084332] mv_xor f1060900.xor: Marvell shared XOR driver
[ 8.143938] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy sg )
[ 8.144453] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 8.146042] console [ttyS0] disabled
[ 8.146121] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud =A
[ 8.798565] console [ttyS0] enabled
[ 8.812295] loop: module loaded
[ 8.815894] sata_mv f1080000.sata: version 1.28
[ 8.816212] sata_mv f1080000.sata: slots 32 ports 2
[ 8.824519] scsi host0: sata_mv
[ 8.828218] scsi host1: sata_mv
[ 8.831653] ata1: SATA max UDMA/133 irq 33
[ 8.835832] ata2: SATA max UDMA/133 irq 33
[ 8.840843] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xda
[ 8.847351] nand: Samsung NAND 256MiB 3,3V 8-bit
[ 8.851990] nand: 256 MiB, MLC, erase size: 4096 KiB, page size: 4096, OOB s8
[ 8.859804] nand: WARNING: f4000000.nand: the ECC used on your system is toop
[ 8.871364] Scanning device for bad blocks
[ 8.879659] 3 cmdlinepart partitions found on MTD device orion_nand
[ 8.885979] Creating 3 MTD partitions on "orion_nand":
[ 8.891155] 0x000000000000-0x000000100000 : "uboot"
[ 8.896085] mtd: partition "uboot" doesn't end on an erase block -- force rey
[ 8.905356] 0x000000100000-0x000000500000 : "kernel"
[ 8.910353] mtd: partition "kernel" doesn't start on an erase block boundaryy
[ 8.920659] 0x000000500000-0x000010000000 : "rootfs"
[ 8.925709] mtd: partition "rootfs" doesn't start on an erase block boundaryy
[ 8.937494] libphy: Fixed MDIO Bus: probed
[ 8.942642] libphy: orion_mdio_bus: probed
[ 8.946850] [Firmware Warn]: /ocp@f1000000/mdio-bus@72004/ethernet-phy@8: Whe
[ 8.963646] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 9.174528] ata1: SATA link down (SStatus 0 SControl F300)
[ 9.524502] ata2: SATA link down (SStatus 0 SControl F300)
[ 10.074613] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC addres1
[ 10.083644] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 10.090227] ehci-pci: EHCI PCI platform driver
[ 10.094800] ehci-orion: EHCI orion driver
[ 10.099085] orion-ehci f1050000.ehci: EHCI Host Controller
[ 10.104669] orion-ehci f1050000.ehci: new USB bus registered, assigned bus n1
[ 10.112581] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 10.143065] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 10.149388] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 10.156252] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber1
[ 10.163538] usb usb1: Product: EHCI Host Controller
[ 10.168441] usb usb1: Manufacturer: Linux 4.12.1-kirkwood-tld-1 ehci_hcd
[ 10.175196] usb usb1: SerialNumber: f1050000.ehci
[ 10.180686] hub 1-0:1.0: USB hub found
[ 10.184571] hub 1-0:1.0: 1 port detected
[ 10.189258] usbcore: registered new interface driver usb-storage
[ 10.195769] mousedev: PS/2 mouse device common for all mice
[ 10.543063] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 10.754463] usb 1-1: New USB device found, idVendor=0781, idProduct=5583
[ 10.761217] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 10.768418] usb 1-1: Product: Ultra Fit
[ 10.772292] usb 1-1: Manufacturer: SanDisk
[ 10.776432] usb 1-1: SerialNumber: 4C530000041215115005
[ 10.782715] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 10.789305] scsi host2: usb-storage 1-1:1.0
[ 11.283057] rtc-mv f1010300.rtc: internal RTC not ticking
[ 11.288702] i2c /dev entries driver
[ 11.299352] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
[ 11.309501] hidraw: raw HID events driver (C) Jiri Kosina
[ 11.315464] drop_monitor: Initializing network drop monitor service
[ 11.322052] NET: Registered protocol family 17
[ 11.326657] Key type dns_resolver registered
[ 11.331912] registered taskstats version 1
[ 11.336068] Loading compiled-in X.509 certificates
[ 11.340950] zswap: loaded using pool lzo/zbud
[ 11.357596] Key type big_key registered
[ 11.373016] Key type encrypted registered
[ 11.380191] rtc-pcf8563 0-0051: setting system clock to 2019-02-03 12:55:59 )
[ 11.389073] PM: Hibernation image not present or could not be loaded.
[ 11.393360] Freeing unused kernel memory: 1024K
[ 11.847341] scsi 2:0:0:0: Direct-Access SanDisk Ultra Fit 1.00 P6
[ 11.865412] sd 2:0:0:0: [sda] 30031872 512-byte logical blocks: (15.4 GB/14.)
[ 11.882288] sd 2:0:0:0: [sda] Write Protect is off
[ 11.890860] sd 2:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 11.891656] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doA
[ 11.916566] sda: sda1
[ 11.924399] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 11.976063] usbcore: registered new interface driver uas
[ 22.769227] EXT4-fs (sda1): recovery complete
[ 22.775674] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:)
[ 25.046227] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 25.352903] lm75 0-0048: hwmon0: sensor 'lm75'
[ 25.523445] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 25.572695] orion_wdt: Initial timeout 21 sec
[ 25.642811] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ 25.840566] random: crng init done
[ 27.342411] EXT4-fs (sda1): re-mounted. Opts: (null)
[ 27.776845] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 34.711855] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, fud
[ 37.234338] NET: Registered protocol family 10
[ 37.241585] Segment Routing with IPv6
root@debian:~/tools# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00400000 "uboot"
mtd1: 00400000 00400000 "kernel"
mtd2: 0fb00000 00400000 "rootfs"
root@debian:~/tools#
Dirk Pitt
↧
Flash NAND with bad blocks
Hello,
I am posting here as somebody proposed this on the OpenWrt forum, please tell me if it's not the right place.
I would like to install OpenWrt on an NSA310. The installation instructions are to first flash a newer U-Boot version, set the proper environment variables, then flash the firmware image through these commands:
(also, I do not actually find these "nand" commands through the U-Boot documentation that I could find)
Thanks for any info!
I am posting here as somebody proposed this on the OpenWrt forum, please tell me if it's not the right place.
I would like to install OpenWrt on an NSA310. The installation instructions are to first flash a newer U-Boot version, set the proper environment variables, then flash the firmware image through these commands:
usb reset fatload usb 0 0x2000000 nsa310.bin nand erase.part ubi nand write 0x2000000 ubi 0x600000But looking through the boot log of the original firmware of the device, I see that there are 2 bad NAND blocks, and I would like to know if this flashing procedure can handle them in a safe way. I don't know enough about the low level details, so I do not know if the bad blocks info is stored in the NAND directly or somewhere at a higher filesystem level.
(also, I do not actually find these "nand" commands through the U-Boot documentation that I could find)
Thanks for any info!
↧
Re: Troubleshooting Freeze Issue on Debian 9 - SSH, Ping, Logs
I was able to crash/freeze my system again in a similar way. This time I was doing an rsync of a 2TB external drive to another 2TB external drive. I did get into htop a few times and saw RAM usage going up to 125MB so maybe it maxed out at some point, but my Pogo E-02 has 256MB with 512MB of swap enabled.
Anyway I could still Ping the IP, but not the hostname. No SSH (refused) and other services were unavailable.
Checking /var/log/messages
There were a ton of these daemon.err smbd messages about being unable to open new log file. Not sure why it would be trying to?
And then the ssh session closing is about when everything likely became unavailable. Nothing more helpful than that as far as I could tell.
I don't expect to be running massive rsync sessions so often, but if it keeps happening regardless of what I'm doing on the Pogo I'll plan to hook up a serial connection.
Anyway I could still Ping the IP, but not the hostname. No SSH (refused) and other services were unavailable.
Checking /var/log/messages
Feb 2 19:35:44 Pogoplug daemon.err smbd[1837]: Unable to open new log file '/tmp/var/.log': No such file or directory Feb 2 19:36:08 Pogoplug authpriv.info sshd[2086]: pam_unix(sshd:session): session closed for user root
There were a ton of these daemon.err smbd messages about being unable to open new log file. Not sure why it would be trying to?
And then the ssh session closing is about when everything likely became unavailable. Nothing more helpful than that as far as I could tell.
I don't expect to be running massive rsync sessions so often, but if it keeps happening regardless of what I'm doing on the Pogo I'll plan to hook up a serial connection.
↧
Re: Troubleshooting Freeze Issue on Debian 9 - SSH, Ping, Logs
cdlenfert,
> Anyway I could still Ping the IP, but not the
> hostname. No SSH (refused) and other services were
> unavailable.
That means avahi-daemon is not responsive. And I think because either CPU probably maxed out or it hung up waiting for its turn to run, as same as sshd daemon.
> Anyway I could still Ping the IP, but not the
> hostname. No SSH (refused) and other services were
> unavailable.
That means avahi-daemon is not responsive. And I think because either CPU probably maxed out or it hung up waiting for its turn to run, as same as sshd daemon.
↧
↧
Re: NETGEAR STORA - Bad Magic Number
Dirk,
mtd is not initialized correctly yet.
So even though the definition is OK. It still not writeable.
Let me think of something to try.
mtd is not initialized correctly yet.
[ 8.885979] Creating 3 MTD partitions on "orion_nand": [ 8.891155] 0x000000000000-0x000000100000 : "uboot" [ 8.896085] mtd: partition "uboot" doesn't end on an erase block -- force rey [ 8.905356] 0x000000100000-0x000000500000 : "kernel" [ 8.910353] mtd: partition "kernel" doesn't start on an erase block boundaryy [ 8.920659] 0x000000500000-0x000010000000 : "rootfs" [ 8.925709] mtd: partition "rootfs" doesn't start on an erase block boundaryy
So even though the definition is OK. It still not writeable.
root@debian:~/tools# cat /proc/mtd dev: size erasesize name mtd0: 00100000 00400000 "uboot" mtd1: 00400000 00400000 "kernel" mtd2: 0fb00000 00400000 "rootfs"
Let me think of something to try.
↧
Re: Flash NAND with bad blocks
kent_c,
> Hello,
>
> I am posting here as somebody proposed this on the
> OpenWrt forum, please tell me if it's not the
> right place.
>
That's OK. If you are going to flash my released u-boot then for sure it is the right place. But even you are flashing other u-boot, I will help.
> I would like to install OpenWrt on an NSA310. The
> installation instructions are to first flash a
> newer U-Boot version,
You meant flashing this u-boot?
> set the proper environment
> variables, then flash the firmware image through
> these commands:
>
> firmware of the device, I see that there are 2 bad
> NAND blocks,
I need to see that info in boot log.
> and I would like to know if this
> flashing procedure can handle them in a safe way.
> I don't know enough about the low level details,
> so I do not know if the bad blocks info is stored
> in the NAND directly or somewhere at a higher
> filesystem level.
> (also, I do not actually find these "nand"
> commands through the U-Boot documentation that I
> could find)
>
Sounds like you want to flash u-boot in serial console. Can you log into stock OS, or Dedbian on this box? If you can't log into any Linux system on this box, then serial console flashing is OK (it's easier to flash new u-boot in Linux).
Power up, interrupt serial console, and
> Hello,
>
> I am posting here as somebody proposed this on the
> OpenWrt forum, please tell me if it's not the
> right place.
>
That's OK. If you are going to flash my released u-boot then for sure it is the right place. But even you are flashing other u-boot, I will help.
> I would like to install OpenWrt on an NSA310. The
> installation instructions are to first flash a
> newer U-Boot version,
You meant flashing this u-boot?
uboot.2017.07-tld-1.nsa310.kwb
> set the proper environment
> variables, then flash the firmware image through
> these commands:
>
> usb reset > fatload usb 0 0x2000000 nsa310.bin > nand erase.part ubi > nand write 0x2000000 ubi 0x600000 >> But looking through the boot log of the original
> firmware of the device, I see that there are 2 bad
> NAND blocks,
I need to see that info in boot log.
> and I would like to know if this
> flashing procedure can handle them in a safe way.
> I don't know enough about the low level details,
> so I do not know if the bad blocks info is stored
> in the NAND directly or somewhere at a higher
> filesystem level.
> (also, I do not actually find these "nand"
> commands through the U-Boot documentation that I
> could find)
>
Sounds like you want to flash u-boot in serial console. Can you log into stock OS, or Dedbian on this box? If you can't log into any Linux system on this box, then serial console flashing is OK (it's easier to flash new u-boot in Linux).
Power up, interrupt serial console, and
printenv nand bad mtdpartsAnd please post this serial console log here.
↧
Re: Linux Kernel 4.19.0 Kirkwood package and Debian rootfs
Kernel linux-4.20.6-kirkwood-tld-1 package has been uploaded. Please 1st post for download link.
↧
Re: GoFlex Home Battery Replacement
So I finally got the bottom off. It really didn't want to come loose and a little plastic got cracked. I found an AG13 battery with solder tabs. I will tackle getting it out and getting a replacement soon. It is really an academic exercise at this point because I decided I can no longer trust my backups to this unit. Besides losing the date and time when I power cycled, it required a power cycle once a week to remember passwords. I spent a bit more money and got a Synology DS418 NAS with dual 4TB drives (in their form of RAID-1).
↧
↧
Re: GoFlex Home Battery Replacement
fishga
> it
> required a power cycle once a week to remember
> passwords.
Sounds like you are running stock OS?
> it
> required a power cycle once a week to remember
> passwords.
Sounds like you are running stock OS?
↧
Re: GoFlex Home Battery Replacement
fishga Wrote:
-------------------------------------------------------
> So I finally got the bottom off. It really didn't
> want to come loose and a little plastic got
> cracked. I found an AG13 battery with solder
> tabs. I will tackle getting it out and getting a
> replacement soon. It is really an academic
> exercise at this point because I decided I can no
> longer trust my backups to this unit. Besides
> losing the date and time when I power cycled, it
> required a power cycle once a week to remember
> passwords. I spent a bit more money and got a
> Synology DS418 NAS with dual 4TB drives (in their
> form of RAID-1).
fishga thanks a lot for documenting what your eyes see in this - I had no idea it's so hard to find.
Just wondering how long the old battery worked for?
* and yes, my own skin crawled ever mentioning my own non-US batteries, but again it was only when Wal Mart was out of Energizer that I stopped at Dollar Tree.
-------------------------------------------------------
> So I finally got the bottom off. It really didn't
> want to come loose and a little plastic got
> cracked. I found an AG13 battery with solder
> tabs. I will tackle getting it out and getting a
> replacement soon. It is really an academic
> exercise at this point because I decided I can no
> longer trust my backups to this unit. Besides
> losing the date and time when I power cycled, it
> required a power cycle once a week to remember
> passwords. I spent a bit more money and got a
> Synology DS418 NAS with dual 4TB drives (in their
> form of RAID-1).
fishga thanks a lot for documenting what your eyes see in this - I had no idea it's so hard to find.
Just wondering how long the old battery worked for?
* and yes, my own skin crawled ever mentioning my own non-US batteries, but again it was only when Wal Mart was out of Energizer that I stopped at Dollar Tree.
↧
Re: Flash NAND with bad blocks
Hi, and thanks for answering!
Yes, the plan is to flash U-Boot via the serial console. I can currently log into the stock OS via both the serial console and telnet.
I am not sure about the source of the OpenWrt-provided U-Boot,...
The mtdparts is not implemented in the stock U-Boot, but the partitions can be seen in the kernel boot arguments and the kernel log.
And what I think is the relevant part of the boot log, please tell me if this is not enough:
Yes, the plan is to flash U-Boot via the serial console. I can currently log into the stock OS via both the serial console and telnet.
I am not sure about the source of the OpenWrt-provided U-Boot,...
The mtdparts is not implemented in the stock U-Boot, but the partitions can be seen in the kernel boot arguments and the kernel log.
NSA310>> printenv bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000 bootdelay=2 baudrate=115200 loads_echo=0 eth1addr=00:19:CB:00:51:82 ipaddr=10.4.50.165 serverip=10.4.50.5 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 nandEcc=1bit MODEL_ID=A203 PRODUCT_NAME=NSA-310 FEATURE_BIT=00 CONTRY_TYPE=FF VENDOR_NAME=ZyXEL Communications Corp. run_diag=yes ethaddr=xx:xx:xx:xx:xx:xx stdin=serial stdout=serial stderr=serial console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root) mainlineLinux=no CASset=min enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes ethprime=egiga1 netbsd_en=no vxworks_en=no bootargs_root=root=/dev/nfs rw bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000; disaMvPnp=no ethmtu=1500 eth1mtu=1500 mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 usb0Mode=host yuk_ethaddr=00:00:00:EE:51:81 hddPowerCtrl=no netretry=no rcvrip=169.254.100.100 loadaddr=0x02000000 autoload=no enaAutoRecovery=yes kernel_addr=0xc80000 pcieTune=no ethact=egiga1
NSA310>> nand bad Device 0 bad blocks: 00e80000 033a0000
And what I think is the relevant part of the boot log, please tell me if this is not enough:
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: RD-88F6281A LE
U-Boot 1.1.4 (Jun 8 2011 - 18:48:37) Marvell version: 3.4.19
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFEE0
Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash: 0 kB
CPU : Marvell Feroceon (Rev 1)
Kernel address is 0xc80000.
Streaming disabled
Write allocate disabled
Module 0 is RGMII
Module 1 is TDM
USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net: egiga0, egiga1 [PRIME]
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0xc80000, size 0xa00000
Bad block at 0xe80000 in erase block from 0xe80000 will be skipped
Reading data from 0x169f800 -- 100% complete.
10485760 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.31.8
Created: 2016-03-11 9:35:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5696716 Bytes = 5.4 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK
Starting kernel ...
Uncompressing Linux............................................................................................................................................................................................................................................................................ done, booting the kernel.
Linux version 2.6.31.8 (root@BuildMachine) (gcc version 4.3.2 (sdk3.3-ct-ng-1.4.1) ) #2 Fri Mar 11 17:35:20 CST 2016
CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
CPU: VIVT data cache, VIVT instruction cache
Machine: Feroceon-KW
Using UBoot passing parameters structure
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 65024
Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
PID hash table entries: 1024 (order: 10, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 244992KB available (5304K code, 300K data, 2804K init, 0K highmem)
.......
CPU Interface
-------------
SDRAM_CS0 ....base 00000000, size 256MB
SDRAM_CS1 ....disable
SDRAM_CS2 ....disable
SDRAM_CS3 ....disable
PEX0_MEM ....base e0000000, size 128MB
PEX0_IO ....base f2000000, size 1MB
PEX1_MEM ....no such
PEX1_IO ....no such
INTER_REGS ....base f1000000, size 1MB
NFLASH_CS ....base fa000000, size 2MB
SPI_CS ....base f4000000, size 16MB
BOOT_ROM_CS ....no such
DEV_BOOTCS ....no such
CRYPT_ENG ....base f0000000, size 2MB
Marvell Development Board (LSP Version KW_LSP_5.1.3_patch18)-- RD-88F6281A Soc: 88F6281 A1 LE
........
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
........
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 116 at 0x000000e80000
Bad eraseblock 413 at 0x0000033a0000
9 cmdlinepart partitions found on MTD device nand_mtd
Using command line partition definition
Creating 9 MTD partitions on "nand_mtd":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "uboot_env"
0x000000180000-0x000000200000 : "key_store"
0x000000200000-0x000000280000 : "info"
0x000000280000-0x000000c80000 : "etc"
0x000000c80000-0x000001680000 : "kernel_1"
0x000001680000-0x000004640000 : "rootfs1"
0x000004640000-0x000005040000 : "kernel_2"
0x000005040000-0x000008000000 : "rootfs2"
........
*** Stage 2: Prepare the root file system ***
Mount system partition...
yaffs: dev is 32505862 name is "mtdblock6" ro
yaffs: passed flags ""
/dev/sda1 /zyxel/mnt/sysdisk ext2 ro,relatime,errors=continue 0 0
0
Boot from disk
Checksum of sysdisk.img : c196092a6409259bb076b47ed4e62236
Checksum from INFO : c196092a6409259bb076b47ed4e62236
Checksum pass!
Mount system disk image ...
yaffs: dev is 32505860 name is "mtdblock4" rw
yaffs: passed flags ""
/etc/zyxel/conf exist..
Start rcS2 of ZyXEL style
↧
Re: GoFlex Home Battery Replacement
Duracell AA / AAA batteries are guaranteed to leak these years...
↧
↧
Re: GoFlex Home Battery Replacement
Yes I am running the stock OS. And this was a refurb unit that never really kept proper time. I suspect the battery was bad when I received it. I had no luck in finding any sort of replacement on eBay, either battery or holder with tabs in the right places. Another reason why I am done with Seagate. Selling a unit like this that is impossible to repair is beyond belief! To say nothing of my less than satisfactory experience with Seagate support.
↧
Re: GoFlex Home Battery Replacement
Bodhi's kirkwood uboot has snpt, so no worries... software solved the battery problem...
https://forum.doozan.com/read.php?3,16003
https://forum.doozan.com/read.php?3,16003
↧
Re: GoFlex Home Battery Replacement
daviddyer Wrote:
-------------------------------------------------------
> Bodhi's kirkwood uboot has snpt, so no worries...
> software solved the battery problem...
>
>
> https://forum.doozan.com/read.php?3,16003
Thanks David! I've forgot all about this instruction! it is indeed a good way to get around the battery problem. A little bit better than Debian ntp because the RTC is set earlier.
I've just modified it to make clear that the RTC is set automatically by u-boot using this approach.
-------------------------------------------------------
> Bodhi's kirkwood uboot has snpt, so no worries...
> software solved the battery problem...
>
>
> https://forum.doozan.com/read.php?3,16003
Thanks David! I've forgot all about this instruction! it is indeed a good way to get around the battery problem. A little bit better than Debian ntp because the RTC is set earlier.
I've just modified it to make clear that the RTC is set automatically by u-boot using this approach.
↧