Quantcast
Channel: Linux Device Hacking
Viewing all 47157 articles
Browse latest View live
↧

Re: WD MyCloud Mirror Gen2 (BWVZ, GrandTeton)

April 6, 2020, 6:07 am
$
0
0
> I am glad it works for you! But I think it is the
> wrong approach to change the GPIO trigger. This is
> only related to disk GPIO trigger.
I've added a missing function to the DTS setup. It was really strange to have GPIO available but not settable in DTS!
In fact timer, one-shot, and pattern are all configurable trough led-pattern parameter. This patch can be useful also for other thinks.

> 2nd is a better approach than 1st . Because while
> 1st is easier, but adding 2 more triggers just for
> this seems too "cookie cutter" and overkill.
To me too. My ideas were:
1) "copy" the gpio trigger function to the ide-disk1/2 and use it to invert the ide-disk1/2 logic (too much device dependent?)
2) add the inverted function to the ide-disk1/2 to invert the logic and somehow attach the gpio to the inverted parameter.

I did not try neither the approaches because the required effort is not cost-effective to me, so i preferred to "sacrifice" an additional led.
But if you want to add this function, we can collaborate!

> So I have started working on a patch on the 2nd
> approach (It has not worked yet).
>
> I hope to add this for the next release of
> Kirkwood and MVEBU kernels.

Wonderful!
In this case, please use my DTSs + poweron/off patch to have a new release compatible also with WDMCG2 and WDEXU2. They are the same, changes only the ram amount!

Please, note that the "2 -" DTSs I've uploaded contains an error. Substitute keep with "keep" (add quotation marks).

I'm refining my notes to make a new resuming post containing the compiled kernel (-cpk-1) the full dts, the patches, and the edits I made to the kernel config.

Thank you so much for your help!
↧
Search

Re: Debian on WD MyCloud EX2 Ultra

April 6, 2020, 7:51 am
$
0
0
Thank you, I'm interested too in your results.

I point you that our devices have an hw crypto engine (CESA) that can be used to improve disk encryption, as pointed at https://wiki.kobol.io/helios4/cesa/

Quote

In order to offload disk encryption on the CESA unit, you will need to specify to cryptsetup the following cipher: aes-cbc-essiv:sha256. Therefore the command to create your encrypted disk should looked as follow: 
sudo cryptsetup -v -y -c aes-cbc-essiv:sha256 luksFormat /dev/sda1

You can verify running 
cryptsetup benchmark


Also, note that this device has the same hardware of WD My Cloud Mirror Gen 2 (https://forum.doozan.com/read.php?2,28939), but with 1GB of Ram (WDMCMG2 has only 512). So you can find useful the results and the updated DTS i'm providing :)

Like me, you can build an usb drive to contain debian rootfs, kernel and initrd to bypass the size limits of the nand partitions, and keep the device compatibile with the original software as fallback.

Disk encryption like you is my final scope, and I think to modify mi usb drive in order to have a small partition unencrypted /boot partition and the debian rootfs and the data encrypted! This way, the hard drive can shutdown without spinning all the time.

Also, I'm exploring btrfs instead of lvm+ext4

What do you think about?
↧
↧

Re: Debian on WD MyCloud EX2 Ultra

April 6, 2020, 9:49 am
$
0
0
Quote
I point you that our devices have an hw crypto engine (CESA) that can be used to improve disk encryption

Interesting, I probably should re-encrypt by HDD raid then. Thank you for this.

Quote
Also, note that this device has the same hardware of WD My Cloud Mirror Gen 2


I have tried the .dts file from that device but I still have no luck to boot. But I think I do have correct .dts file from a friend. But for some reason the kernel couldb't find Ininrd to boot. @bodhi says it is easy to handle, so there is hope.

Quote
Like me, you can build an usb drive to contain debian rootfs, kernel and initrd to bypass the size limits of the nand partitions

That could be a solution. But how do you boot then? With a reset button pressed during the boot? And then do you have to keep that USB drive inserted into the device all the time? Or you can remove it after the deviced has booted?

Quote
Also, I'm exploring btrfs instead of lvm+ext4

Yes, I have also looked at that, but that seemed to me more complicated at that time.
↧

Re: Debian on WD MyCloud EX2 Ultra

April 6, 2020, 11:28 am
$
0
0
Look to my post: https://forum.doozan.com/read.php?2,28939,98649#msg-98649
Also this for latest DTS: https://forum.doozan.com/read.php?2,28939,99099#msg-99099

In days I'll release a more refined version.

About using BTRFS:
It should be BTRFS over LUKS directly, managing both volumes and raid instead of EXT4 over LUKS over RAID.
Also take a moment to understand what is better between LUKS over RAID or RAID over LUKS.

***edit***
BTRFS over LUKS gives very low performances (~34MB/s to me), but it appear a common problem: https://unix.stackexchange.com/questions/203677/abysmal-general-dm-crypt-luks-write-performance
↧

Re: Sandisk U3 performance

April 6, 2020, 1:45 pm
$
0
0
habibie Wrote:
-------------------------------------------------------
> asterix Wrote:
> -------------------------------------------------------
> > bought some when it on sale: 8.5 for 2, but not
> >
> Nice.
>
> > just test it now. The speed much faster than
> other microSD: write 66MB/s, read 85MB/s.
> >
> Excellent.
>
> BTW, how did you test the R/W speed? In my
> post,
> I used f3
> utility to perform R/W tests.

use ATTO to test it, also wrote a 2GB file from PC to this SD card
↧
↧

Re: Sandisk U3 performance

April 6, 2020, 1:47 pm
$
0
0
JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> asterix Wrote:
> -------------------------------------------------------
> > bought some when it on sale: 8.5 for 2, but not
> > $49
>
> > seems not bad as Pi's system disk
>
> Any advice when & where to see these on sale?
> Those are beautiful specs!

a friend told me, he also bought a lot for his Pis :)
↧

Re: WD MyCloud Mirror Gen2 (BWVZ, GrandTeton)

April 6, 2020, 3:43 pm
$
0
0
CyberPK,

> To me too. My ideas were:
> 1) "copy" the gpio trigger function to the
> ide-disk1/2 and use it to invert the ide-disk1/2
> logic (too much device dependent?)
> 2) add the inverted function to the ide-disk1/2 to
> invert the logic and somehow attach the gpio to
> the inverted parameter.

I think the above is too specific. Triggers should work for all boxes. The right way to enable a trigger for a specific box is to bind it with a GPIO, and set the state to whatever appropriate behavior for that box.

So to follow the current kernel design, when there is a disk present that was detected by the kernel, a function X in the SATA driver will invoke ledtrig_disk_activity() to set the LED and/or some state. The code change is thus encapsulated in the appropriate functions.


> In this case, please use my DTSs + poweron/off
> patch to have a new release compatible also with
> WDMCG2 and WDEXU2. They are the same, changes only
> the ram amount!

That would be great. However, the RAM change is really not necessary (u-boot will override that settings in DTS). Whatever DTS patch you have is OK for this box. But Power On/Off should be looked at to make sure it applies to this box only. Other Armada boxes should not be effected by that.

A critic on using the Red LED: this color usually indicates a fault condition. So that should be reserved to be used in that case. Blue solid, and Blue flashing is much better indicators of the disk present and disk activity.
↧

Re: Need help with creating USB for the new uBoot

April 6, 2020, 4:03 pm
$
0
0
I spent yesterday but was unable to get the wifi working yet as I don't remember how I did it years ago. But now I have another POGO-E02 box that I updated the uboot (U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)) years ago but it won't boot. So I put it in the closet. I don't have the USB stick I put debian in years ago so I am using the one above that I prepared for the POGO-B01 instead. This is what happen when we boot: 

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
ping - send ICMP ECHO_REQUEST to network host

Usage:
ping pingAddress
Hit any key to stop autoboot:  0 
PogoE02> boot
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
4621824 bytes read in 465 ms (9.5 MiB/s)
EHCI timed out on TD - token=0x1e008d80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x1f8c80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x1f8c80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x1f8c80
EHCI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x1f8c80
EHCI timed out on TD - token=0x80008d80
 ** ext4fs_devread read error - block
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.54-oxnas-tld-1
   Created:      2017-08-01   4:45:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4621760 Bytes = 4.4 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0x831 from environment

Starting kernel ...

So I want to update the new uboot 2017.07 U-Boot Kirkwood on this one. I am stuck from step one.

Quote
1. uBoot envs config should be defined as followed in your /etc/fw_env.config

cat /etc/fw_env.config
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

- And your mtd partitions should be:

cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "rootfs"
mtd3: 0db00000 00020000 "data"

Note: for boxes such as Pogo V4 and Zyxel NSA3xx, the mtd partition definition are kept the same as stock definition, therefore is different from the one above.

If you don't have /etc/fw_env.config file in your system then go ahead and create this file with the above content. MTD parts are not important for booting and it can be adjusted later. For users who like to keep the stock mtd definition, there is no need to adjust it to the above definition. As long as mtd0 is defined as 1MB (0x00100000) or greater then it will be OK:
mtd0: 00100000 00020000 "u-boot"

I don't have the /proc/mtd. Could you please guide me to the right place for flashing?
↧
Search

Re: Debian on WD MyCloud EX2 Ultra

April 6, 2020, 4:38 pm
$
0
0
vzhilov,


USB booting:

> That could be a solution. But how do you boot
> then? With a reset button pressed during the boot?

With changes in u-boot envs, you should be able to boot with USB rootfs (unless it has some restriction like a few other Armada boxes).

> And then do you have to keep that USB drive
> inserted into the device all the time? Or you can
> remove it after the deviced has booted?

It is your system rootfs, so must be attached at all time.
↧
↧

Re: Need help with creating USB for the new uBoot

April 6, 2020, 4:46 pm
$
0
0
jeyrey,

This box is different. The rootfs is Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2.

https://forum.doozan.com/read.php?2,12096
Quote

Latest released rootfs: Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (25 Aug 2019)

It is OK to use U-Boot 2014.07-tld-1. Get it boot into Debian and then flash new u-boot 2017.07-tld-1.

You should use a different USB to create the new rootfs. And use Ext3 partition.
↧

Re: Need help with creating USB for the new uBoot

April 6, 2020, 4:51 pm
$
0
0
Thank you bodhi for the prompt response. Anywhere I can an image of a working kernel for a usb stick that I can use to boot into Debian? I don't have a working USB stick for this box right now.
↧

Re: Need help with creating USB for the new uBoot

April 6, 2020, 5:30 pm
$
0
0
Hi bodhi, I have created a stick and cold boot the box. This is what I am getting. It is stuck. 


U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
ping - send ICMP ECHO_REQUEST to network host

Usage:
ping pingAddress
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
4973786 bytes read in 591 ms (8 MiB/s)
9713936 bytes read in 787 ms (11.8 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2020-04-07   1:01:21 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4973722 Bytes = 4.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2019-08-25   2:22:50 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0x831 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


Here is the printenv response: 

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

Environment size: 2233/131068 bytes
PogoE02>

I also tried 
setenv dtb_file '/boot/dts/kirkwood-pogo-e02.dtb'

but that did not help.
↧

Re: Need help with creating USB for the new uBoot

April 6, 2020, 6:59 pm
$
0
0
jeyrey,

> Hi bodhi, I have created a stick and cold boot the
> box. This is what I am getting. It is stuck.

> I also tried
> 
> setenv dtb_file '/boot/dts/kirkwood-pogo-e02.dtb'
>
>
> but that did not help.

Ah, it was because back then, U-Boot 2014.07-tld-1 was still not set up to boot with the separated DTB.


So when you create USB rootfs now, you need to do Step 4b:

Quote

4b. Boot with DTB file embedded in the kernel image (no U-Boot envs changes are needed if your system already booting on USB or HDD). Again, this step 4b is for stock U-Boot only.

Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box.

Generate the uImage and uInitrd (the kernel files vmlinuz-5.5.1-kirkwood-tld-1 and initrd.img-5.5.1-kirkwood-tld-1 were generated by dpkg in Step 3):
cd /boot
mv uImage uImage.orig
mv uInitrd uInitrd.orig
cp -a zImage-5.5.1-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.5.1-kirkwood-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.5.1-kirkwood-tld-1 -d initrd.img-5.5.1-kirkwood-tld-1 uInitrd

After it booted into Debian, you can install new u-boot, and then reverse Step 4b to boot with separate DTB.
↧
↧

Re: Need help with creating USB for the new uBoot

April 6, 2020, 7:33 pm
$
0
0
Still no go. It's stuck. 

Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
4973786 bytes read in 461 ms (10.3 MiB/s)
9713936 bytes read in 750 ms (12.4 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2020-04-07   2:25:20 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4973722 Bytes = 4.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2020-04-07   2:26:10 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0x831 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Note that I followed the step 4b above with replacement of 5.5.1 with 5.2.9 since that is what I have in the tar ball. Or am I supposed to get a different kernel?
↧

Re: Debian on WD MyCloud EX2 Ultra

April 7, 2020, 1:43 am
$
0
0
Quote
You'are very close to get it booted. This problem "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)" is easy to solve.

Is there anything I could do?
↧
Search

Re: Need help with creating USB for the new uBoot

April 7, 2020, 3:15 am
$
0
0
jeyrey,

Power up, interrupt u-boot at count down, and, 

setenv set_bootargs_usb 'setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts earlyprintk=serial'
boot

And post the entire serial console log here (in both cases, whether it boots successfully or not).
↧

Re: Debian on WD MyCloud EX2 Ultra

April 7, 2020, 3:23 am
$
0
0
vzhilov,

Create a USB rootfs using Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2.

And boot with that. Some envs need to be adjusted to boot USB. I can help you with this.

And then after it booted into Debian, setup your RAID.
↧
↧

Re: Debian on WD MyCloud EX2 Ultra

April 7, 2020, 3:38 am
$
0
0
I'm not bricked. I can boot with my old parameters without having rootfs on USB.

I'm going to boot BusyBox from nand partition. I'm looking to avoid using USB drive for booting. I do have my own Initrd and rootfs. But I really suffer from having old kernel as I can't update cryptsetup in Initrd. And the one you have (5.5.3) doesn't boot with my setup giving the above error. The old kernel 4.14 that I have boots up fine.

My only partitions are /dev/mtdblock1 for uImage and /dev/mtdblock2 for uInitrd. I don't use anything else for initial booting.
↧

Re: Need help with creating USB for the new uBoot

April 7, 2020, 4:24 am
$
0
0
Hi bodhi, Here is where it is stuck. 


U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
ping - send ICMP ECHO_REQUEST to network host

Usage:
ping pingAddress
Hit any key to stop autoboot:  0
PogoE02> setenv set_bootargs_usb 'setenv bootargs console=$console root=$usb_roo
t rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts earlyprintk=serial'
PogoE02> boot
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
4973786 bytes read in 591 ms (8 MiB/s)
9713936 bytes read in 790 ms (11.7 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.2.9-kirkwood-tld-1
   Created:      2020-04-07  11:13:11 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4973722 Bytes = 4.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.2.9-kirkwood-tld-1
   Created:      2020-04-07  11:16:08 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9713872 Bytes = 9.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0x831 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.2.9-kirkwood-tld-1 (root@tldDebian) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Sat Aug 17 15:00:56 
PDT 2019
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr
=0005397f
[    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: CloudEngines Pogoplug E02
[    0.000000][    T0] printk: bootconsole [earlycon0] enabled
[    0.000000][    T0] Memory policy: Data cache writeback
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 65
024
[    0.000000][    T0] Kernel command line: console=ttyS0,115200 root=/dev/sda1 
rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootf
s),-(data) earlyprintk=serial
[    0.000000][    T0] Dentry cache hash table entries: 32768 (order: 5, 131072 
bytes)
[    0.000000][    T0] Inode-cache hash table entries: 16384 (order: 4, 65536 by
tes)
[    0.000000][    T0] Memory: 234804K/262144K available (9216K kernel code, 868
K rwdata, 3400K rodata, 1024K init, 301K bss, 27340K reserved, 0K cma-reserved)
[    0.000000][    T0] random: get_random_u32 called from cache_alloc_refill+0x3
8c/0x928 with crng_init=0
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0]  Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay i
s 10 jiffies.
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycl
es: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000009][    T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps eve
ry 10737418237ns
[    0.008603][    T0] Switching to timer-based delay loop, resolution 5ns
[    0.015992][    T0] Console: colour dummy device 80x30
[    0.021246][    T0] Calibrating delay loop (skipped), value calculated using
timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.032569][    T0] pid_max: default: 32768 minimum: 301
[    0.038281][    T0] LSM: Security Framework initializing
[    0.043852][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 byte
s)
[    0.051256][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096
 bytes)
[    0.059936][    T0] *** VALIDATE proc ***
[    0.064221][    T0] *** VALIDATE cgroup1 ***
[    0.068523][    T0] *** VALIDATE cgroup2 ***
[    0.072947][    T0] CPU: Testing write buffer coherency: ok
[    0.080343][    T1] Setting up static identity map for 0x100000 - 0x100058
[    0.087529][    T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x2
[    0.093746][    T1] rcu: Hierarchical SRCU implementation.
[    0.102617][    T1] devtmpfs: initialized
[    0.111971][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffff
ffff, max_idle_ns: 19112604462750000 ns
[    0.122638][    T1] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.129796][    T1] xor: measuring software checksum speed
[    0.228628][    T1]    arm4regs  :  1083.600 MB/sec
[    0.328628][    T1]    8regs     :   650.400 MB/sec
[    0.428627][    T1]    32regs    :   945.600 MB/sec
[    0.433541][    T1] xor: using function: arm4regs (1083.600 MB/sec)
[    0.439875][    T1] prandom: seed boundary self test passed
[    0.449706][    T1] prandom: 100 self tests passed
[    0.454527][    T1] pinctrl core: initialized pinctrl subsystem
[    0.461940][    T1] NET: Registered protocol family 16
[    0.467728][    T1] DMA: preallocated 256 KiB pool for atomic coherent alloca
tions
[    0.476196][    T1] audit: initializing netlink subsys (disabled)
[    0.483650][   T14] audit: type=2000 audit(0.470:1): state=initialized audit_
enabled=0 res=1
[    0.492278][    T1] cpuidle: using governor ladder
[    0.497168][    T1] cpuidle: using governor menu
[    0.502462][    T1] Feroceon L2: Enabling L2
[    0.506797][    T1] Feroceon L2: Cache support initialised.
[    0.517874][    T1] No ATAGs?
[    2.568610][    C0] random: fast init done
[    6.482799][   T71] alg: No test for lzo-rle (lzo-rle-generic)
[    6.489374][   T73] alg: No test for lzo-rle (lzo-rle-scomp)
[    6.668932][    T1] raid6: int32x8  gen()   127 MB/s
[    6.839038][    T1] raid6: int32x8  xor()    86 MB/s
[    7.009033][    T1] raid6: int32x4  gen()   129 MB/s
[    7.178889][    T1] raid6: int32x4  xor()    83 MB/s
[    7.348808][    T1] raid6: int32x2  gen()   132 MB/s
[    7.518921][    T1] raid6: int32x2  xor()    94 MB/s
[    7.689171][    T1] raid6: int32x1  gen()   100 MB/s
[    7.858886][    T1] raid6: int32x1  xor()    68 MB/s
[    7.863873][    T1] raid6: using algorithm int32x2 gen() 132 MB/s
[    7.870011][    T1] raid6: .... xor() 94 MB/s, rmw enabled
[    7.875522][    T1] raid6: using intx1 recovery algorithm
[    7.881220][    T1] vgaarb: loaded
[    7.885145][    T1] SCSI subsystem initialized
[    7.890141][    T1] usbcore: registered new interface driver usbfs
[    7.896406][    T1] usbcore: registered new interface driver hub
[    7.902562][    T1] usbcore: registered new device driver usb
[    7.908513][    T1] pps_core: LinuxPPS API ver. 1 registered
[    7.914219][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodol
fo Giometti <giometti@linux.it>
[    7.924121][    T1] PTP clock support registered
[    7.930161][    T1] clocksource: Switched to clocksource orion_clocksource
[    8.974372][    T1] VFS: Disk quotas dquot_6.6.0
[    8.979101][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 
bytes)
[    8.996707][    T1] NET: Registered protocol family 2
[    9.002670][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 
0, 4096 bytes)
[    9.011159][    T1] TCP established hash table entries: 2048 (order: 1, 8192 
bytes)
[    9.018872][    T1] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    9.026029][    T1] TCP: Hash tables configured (established 2048 bind 2048)
[    9.033248][    T1] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    9.039825][    T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    9.047075][    T1] NET: Registered protocol family 1
[    9.052832][    T1] RPC: Registered named UNIX socket transport module.
[    9.059481][    T1] RPC: Registered udp transport module.
[    9.064989][    T1] RPC: Registered tcp transport module.
[    9.070438][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    9.077607][    T1] PCI: CLS 0 bytes, default 32
[    9.082503][    T1] Trying to unpack rootfs image as initramfs...
[    9.088627][    T1] Initramfs unpacking failed: invalid magic at start of com
pressed archive
[    9.123887][    T1] Freeing initrd memory: 9488K
[    9.128766][    T1] NetWinder Floating Point Emulator V0.97 (double precision
)
[    9.137237][    T1] Initialise system trusted keyrings
[    9.142483][    T1] Key type blacklist registered
[    9.147407][    T1] workingset: timestamp_bits=30 max_order=16 bucket_order=0
[    9.154751][    T1] zbud: loaded
[    9.159102][    T1] NFS: Registering the id_resolver key type
[    9.164992][    T1] Key type id_resolver registered
[    9.169894][    T1] Key type id_legacy registered
[    9.174681][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering
...
[    9.182169][    T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    9.189546][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat
, Inc.
[    9.197579][    T1] fuse: init (API version 7.31)
[    9.202733][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[    9.210080][    T1] orangefs_init: module version upstream loaded
[    9.216231][    T1] SGI XFS with ACLs, security attributes, realtime, scrub, 
no debug enabled
[    9.227958][    T1] async_tx: api initialized (async)
[    9.233118][    T1] Key type asymmetric registered
[    9.237928][    T1] Asymmetric key parser 'x509' registered
[    9.243645][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded 
(major 246)
[    9.252940][    T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    9.268217][    T1] loop: module loaded
[    9.273836][    T1] libphy: Fixed MDIO Bus: probed
[    9.279347][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Drive
r
[    9.286702][    T1] ehci-pci: EHCI PCI platform driver
[    9.291942][    T1] ehci-orion: EHCI orion driver
[    9.296865][    T1] usbcore: registered new interface driver usb-storage
[    9.303991][    T1] mousedev: PS/2 mouse device common for all mice
[    9.310616][    T1] i2c /dev entries driver
[    9.315403][    T1] device-mapper: uevent: version 1.0.3
[    9.321099][    T1] device-mapper: ioctl: 4.40.0-ioctl (2019-01-18) initialis
ed: dm-devel@redhat.com
[    9.330716][    T1] device-mapper: multipath round-robin: version 1.2.0 loade
d
[    9.337973][    T1] device-mapper: multipath queue-length: version 0.2.0 load
ed
[    9.345381][    T1] device-mapper: multipath service-time: version 0.3.0 load
ed
[    9.352836][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    9.359661][    T1] device-mapper: raid: Loading target version 1.14.0
[    9.366357][    T1] kirkwood-cpufreq kirkwood-cpufreq: Unable to get cpuclk
[    9.373410][    T1] kirkwood-cpufreq: probe of kirkwood-cpufreq failed with e
rror -22
[    9.381728][    T1] hidraw: raw HID events driver (C) Jiri Kosina
[    9.388166][    T1] drop_monitor: Initializing network drop monitor service
[    9.395511][    T1] NET: Registered protocol family 17
[    9.400950][    T1] Key type dns_resolver registered
[    9.406835][    T1] registered taskstats version 1
[    9.411684][    T1] Loading compiled-in X.509 certificates
[    9.417267][    T1] zswap: loaded using pool lzo/zbud
[    9.437491][    T1] Key type big_key registered
[    9.445502][    T1] Key type encrypted registered
[    9.452294][    T1] hctosys: unable to open rtc device (rtc0)
[   11.844280][    T1] Unable to handle kernel paging request at virtual address
 d0000004
[   11.852246][    T1] pgd = (ptrval)
[   11.855662][    T1] [d0000004] *pgd=00000000
[   11.859957][    T1] Internal error: Oops: 5 [#1] PREEMPT ARM
[   11.865638][    T1] Modules linked in:
[   11.869410][    T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.2.9-kirkwood-tl
d-1 #1
[   11.877095][    T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[   11.884089][    T1] PC is at crc32_be+0xac/0x160
[   11.888720][    T1] LR is at 0xd0000000
[   11.892575][    T1] pc : [<c06214c0>]    lr : [<d0000000>]    psr: 80000053
[   11.899567][    T1] sp : cf88bed0  ip : 00000007  fp : c0e57838
[   11.905514][    T1] r10: c0fd9300  r9 : c0fd9300  r8 : 00000000
[   11.911463][    T1] r7 : 00000000  r6 : 565629fc  r5 : 71c0daf0  r4 : c149588
0
[   11.918718][    T1] r3 : c0a6f7b0  r2 : b2285660  r1 : f0defde0  r0 : d68e4b5
9
[   11.925974][    T1] Flags: Nzcv  IRQs on  FIQs off  Mode SVC_32  ISA ARM  Seg
ment none
[   11.933925][    T1] Control: 0005397f  Table: 00004000  DAC: 00000053
[   11.940395][    T1] Process swapper (pid: 1, stack limit = 0x(ptrval))
[   11.946953][    T1] Stack: (0xcf88bed0 to 0xcf88c000)
[   11.952031][    T1] bec0:                                     f0defde7 c101e6
04 c0f04028 c0e449a8
[   11.960946][    T1] bee0: 00000000 c0e449e8 ffffe000 c0fb44a0 c0f04028 c01035
2c c0ca5039 c0136908
[   11.969857][    T1] bf00: c0168fd0 c0f04000 00000000 c0e004a4 c0d4ffb4 000000
e6 00000007 00000007
[   11.978769][    T1] bf20: 00000000 c0d511ac 000000e5 c0d511ac c0fb44a0 cfffce
3f cfffce4b e160994a
[   11.987681][    T1] bf40: 00000000 e160994a cfffcdc0 00000008 c0e65d6c 000000
e6 c0fb44a0 c0e57834
[   11.996592][    T1] bf60: c0fd9300 c0e011e8 00000007 00000007 00000000 c0e004
a4 00000000 00000000
[   12.005504][    T1] bf80: c09dced8 00000000 c09dced8 00000000 00000000 000000
00 00000000 00000000
[   12.014415][    T1] bfa0: 00000000 c09dcee0 00000000 c01010e0 00000000 000000
00 00000000 00000000
[   12.023327][    T1] bfc0: 00000000 00000000 00000000 00000000 00000000 000000
00 00000000 00000000
[   12.032239][    T1] bfe0: 00000000 00000000 00000000 00000000 00000013 000000
00 00000000 00000000
[   12.041167][    T1] [<c06214c0>] (crc32_be) from [<c0e449e8>] (of_fdt_raw_init+0x40/0x84)
[   12.049391][    T1] [<c0e449e8>] (of_fdt_raw_init) from [<c010352c>] (do_one_initcall+0xbc/0x220)
[   12.058311][    T1] [<c010352c>] (do_one_initcall) from [<c0e011e8>] (kernel_init_freeable+0x290/0x2dc)
[   12.067754][    T1] [<c0e011e8>] (kernel_init_freeable) from [<c09dcee0>] (kernel_init+0x8/0x10c)
[   12.076670][    T1] [<c09dcee0>] (kernel_init) from [<c01010e0>] (ret_from_fork+0x14/0x34)
[   12.084973][    T1] Exception stack(0xcf88bfb0 to 0xcf88bff8)
[   12.090747][    T1] bfa0:                                     00000000 00000000 00000000 00000000
[   12.099662][    T1] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   12.108572][    T1] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   12.115917][    T1] Code: e0230420 1afffff7 eb0e82bc e8bd81f0 (e59e6004) 
[   12.122736][    T1] ---[ end trace 6ce7bcae0bcc8616 ]---
[   12.128339][    T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[   12.136734][    T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
↧

Re: Need help with creating USB for the new uBoot

April 7, 2020, 8:46 am
$
0
0
OK bodhi, when I flashed the uboot years ago, I also had created a usb stick to go with it but I never booted successfully as I didn't have a serial cable at the time. Luckily I never deleted it. After stuck with the new rootfs above, I have tried the old USB stick and new I am in debian. Here is its version: 
root@debian:~# uname -a
Linux debian 2.6.32-5-kirkwood #1 Tue May 13 17:59:08 UTC 2014 armv5tel GNU/Linux

So I tried to follow the steps to flash the 2017.07 U-Boot Kirkwood. I am now at step 4
Quote
4. Be sure there is no bad block in the first 1M of your NAND (check dmesg). This is very important, if there is bad block in the first 1M (8 blocks), don't flash u-boot, because you will almost certainly brick your box. Please post your question here (there is a work around for it).

Example of bad block in mtd0:
dmesg | grep -i 'bad'

[ 2.413231] Scanning device for bad blocks
[ 2.417731] Bad eraseblock 3 at 0x000000060000

This bad block is the 4th block which resides within mtd0 (block 0 to block 7). So u-boot should not be flashed.
This is what mine gave: 
root@debian:~# dmesg | grep -i 'bad'
[   22.284760] Scanning device for bad blocks
[   22.289172] Bad eraseblock 7 at 0x0000000e0000
It said that I should not flash the uboot. What should I do with it now?
↧
Viewing all 47157 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>