Debian on Dell Wyse 3020

bodhi Wrote:
-------------------------------------------------------
> Yes. Please do that. I think we are at the point
> for a detailed Howto.

Okey Dokey - ill start this when the unsullied one lands and post it for verification and feedback

interesting stuff to be had over here..... TX0d - homepage

buried in the files is an xml file that indicates what to install to what partition and also some informaton about the SPI - that bit is sailing over my head. but may help the community in understanding how to flash the spi

============================
Breaking stuff since 1994 :-)
============================



Edited 1 time(s). Last edit at 07/08/2023 06:58AM by Gravelrash.

> buried in the files is an xml file that indicates
> what to install to what partition and also some
> informaton about the SPI - that bit is sailing
> over my head. but may help the community in
> understanding how to flash the spi

That looks a bit more interesting!

I'm on travel currently, and will get back to this subject when I can.

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

bodhi Wrote:
> I'm on travel currently, and will get back to this
> subject when I can.


"Bodhi Bond" - International man of computing and all round nice guy with a licence to defeat uboot problems

xml code from above

<imageType><sourceMethod><merlinImage><versionNumber>3.4.0</versionNumber></merlinImage></sourceMethod></imageType><commandSet><commandEnvelope><downloadARMImageFromServerEx><transferEncoding><type>lzma</type><encodedSize>934186</encodedSize></transferEncoding><source><location>bootLoader.img</location><checksum>c67d</checksum><size>1179648</size></source><destination><securityKey><masterKey>0101072D</masterKey><masterKeyMask>FFFFFFFF</masterKeyMask><supportedKeySet><supportedKey><key>0101072D</key><mask>FFFFFFFF</mask></supportedKey></supportedKeySet></securityKey><bootLoader/></destination></downloadARMImageFromServerEx></commandEnvelope><commandEnvelope><downloadARMImageFromServerEx><transferEncoding><type>lzma</type><encodedSize>430</encodedSize></transferEncoding><source><location>cmos.img</location><checksum></checksum><size>327680</size></source><destination><securityKey><masterKey>0101072D</masterKey><masterKeyMask>FFFFFFFF</masterKeyMask><supportedKeySet><supportedKey><key>0101072D</key><mask>FFFFFFFF</mask></supportedKey></supportedKeySet></securityKey><cmos/></destination></downloadARMImageFromServerEx></commandEnvelope><commandEnvelope><downloadARMImageFromServerEx><transferEncoding><type>lzma</type><encodedSize>56563502</encodedSize></transferEncoding><source><location>par1.img</location><checksum></checksum><size>3909091328</size></source><destination><securityKey><masterKey>0101072D</masterKey><masterKeyMask>FFFFFFFF</masterKeyMask><supportedKeySet><supportedKey><key>0101072D</key><mask>FFFFFFFF</mask></supportedKey></supportedKeySet></securityKey><ide><channel>0</channel><drive>0</drive><scope><drive/></scope></ide></destination></downloadARMImageFromServerEx></commandEnvelope></commandSet><commandSet><configuration><spiflash><vendor>PCT</vendor><size>4</size></spiflash><spiflash><vendor>MXIC</vendor><size>4</size></spiflash><spiflash><vendor>MXIC</vendor><size>8</size></spiflash><spiflash><vendor>WINBOND</vendor><size>4</size></spiflash><spiflash><vendor>WINBOND</vendor><size>8</size></spiflash><spiflash><vendor>MICRON</vendor><size>8</size></spiflash><spiflash><vendor>GENERIC_SPI</vendor><size>4</size></spiflash><spiflash><vendor>GENERIC_SPI</vendor><size>8</size></spiflash></configuration></commandSet>

============================
Breaking stuff since 1994 :-)
============================



Edited 1 time(s). Last edit at 07/08/2023 02:53PM by Gravelrash.

Hi guys

That's my first topic here, as I am no specialist in linux. Actually, i know shit about it, but I have a new business idea related to usage of TX0d, as far as I would manage to make them run docker. That's for my introduction

I am trying to Install Fedora as described here: https://linux-mmp.docs.kernel.org/dell-wyse-3020.html but I cant find Fedora-Minimal-armhfp-32-1.6-sda.raw . In version armhpf-30-1.2 there's no dell-ariel dtb file,

Can someone please reupload Fedora-Minimal-armhfp-32-1.6-sda.raw or maybe mmp3-dell-ariel.dtb and dts ? I scrounged through whole Internet, twice, but there is no trace. :( Well I mean, there is only trace, here. So please, be that kind.

chomick,

I can't help you with Fedora, but you can find the DTS and DTB in my released tarball.

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

Quote

Latest released kernel: linux-6.3.8-mvebu-tld-1-bodhi.tar.bz2 (26 Jun 2023)

The ariel DTB is in this tarball:

linux-dtb-6.3.8-mvebu-tld-1.tar

DTS patch is in this file (the difference between the mainline Linux DTS and my customed Debian kernel linux-6.3.8-mvebu-tld-1):

linux-6.3.8-mvebu-tld-1.patch

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

Go here for the latest equivalent of Fedora - as Bodhi says, this forum is typically for debian, but we help where we can :)

https://fedoraproject.org/wiki/Architectures/ARM

https://fedoraproject.org/wiki/Architectures/ARM/Fedora_Linux_35#ARMv7hl

chomick Wrote:
-------------------------------------------------------
Fedora-Minimal-armhfp-32-1.6-sda.raw . In version armhpf-30-1.2 there's no dell-ariel dtb file, Can someone please reupload Fedora-Minimal-armhfp-32-1.6-sda.raw or maybe mmp3-dell-ariel.dtb and dts ? I

============================
Breaking stuff since 1994 :-)
============================



Edited 1 time(s). Last edit at 07/16/2023 09:58AM by Gravelrash.

Guys

I am struggling for past two weeks. A lot, as I really don't know how to work with linux. Now i try with Debian. I believe I've done everything properly, but I get message "Initrd: Bad MAGIC (0x0): Try Legacy Mode and everything halts. Please help

Can I connect via SSH with switch, or should computers be linked together?

chomick Wrote:
-------------------------------------------------------
> Guys
>
> I am struggling for past two weeks. A lot, as I
> really don't know how to work with linux. Now i
> try with Debian. I believe I've done everything
> properly, but I get message "Initrd: Bad MAGIC
> (0x0): Try Legacy Mode and everything halts.
> Please help
>
> Can I connect via SSH with switch, or should
> computers be linked together?

Repeat what you did, and post the log of the terminal session (copy and paste everything) here.

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

Ok, so we would need to start from the beginning. Serial console shows only couple lines before WLoader takes it over and I am not sure I am reaching the point where the terminal connection is possible, unless I don't fully understand even that part. I am constantly pinging the IP adress which my 3020 gets while running ThinOS, but there is no response. I attach screenshots of last two things I see before it freezes

So how would I make it happen, to have a log?

I found out that the message I get before everything freezes is related to bad headers. I've done everything described here: https://forum.doozan.com/read.php?2,134563,135415#msg-135415 step by step

chomick,

> Serial console shows only couple lines before
> WLoader takes it over and I am not sure I am
> reaching the point where the terminal connection
> is possible, unless I don't fully understand even
> that part

Yes, the serial console does not output anything before the Linux kernel starts running.

> I am constantly pinging the IP adress
> which my 3020 gets while running ThinOS, but there
> is no response.

If you did everything correctly, and the system has booted, then there is a new dynamic IP address in your network router that Debian acquires, the Thin OS behavior is not applicable here. You can also try

ping debian.local

> I've
> done everything described here:
> https://forum.doozan.com/read.php?2,134563,135415#msg-135415
> step by step

> So how would I make it happen, to have a log?

That instruction is not complete (it is too abbreviate). There are many details that need to be spelled out further (Gravelrash will write out the details here :). So you might have missed (or not aware what you need to do certain things).

That's why I asked if you could, repeat the whole thing (create the partitions on USB drive, download the kernel tarball, download the rootfs tarball, and extract them to the partitions, create the wloader config file ... ). And then copy eveything on the terminal session and paste it here. And then try booting, and copy everything on serial console session and paste that log here.

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



Edited 1 time(s). Last edit at 07/24/2023 01:29PM by bodhi.

I am back from my own prolonged travails... i have a few days me time next week so will start the howto then.

HOWTO - Install Debian on WYSE3020

============================
Breaking stuff since 1994 :-)
============================

Can anyone help me with making docker run?

root@debian:/mnt# docker run --restart=on-failure:5 iproyal/pawns-cli:latest -email=chomick@gmail.com -password=******* -device-name=debian -device-id=Arm1 -accept-tos
[  631.521036][ T1422] docker0: port 1(vethbd9e08c) entered blocking state
[  631.527806][ T1422] docker0: port 1(vethbd9e08c) entered disabled state
[  631.534766][ T1422] vethbd9e08c: entered allmulticast mode
[  631.550338][ T1422] vethbd9e08c: entered promiscuous mode
[  636.351607][ T1425] docker0: port 1(vethbd9e08c) entered disabled state
[  636.368898][ T1425] vethbd9e08c (unregistering): left allmulticast mode
[  636.375529][ T1425] vethbd9e08c (unregistering): left promiscuous mode
[  636.386877][ T1425] docker0: port 1(vethbd9e08c) entered disabled state
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting cgroup config for procHooks process: bpf_prog_query(BPF_CGROUP_DEVICE) failed: invalid argument: unknown.
ERRO[0007] error waiting for container:
root@debian:/mnt#

Would it be possible to run x86_64 emulator ? I need Dell Wyse 3020 to run a set of internet-sharing apps, most of them should run in docker for ARM, but two most essential - will not.



Edited 5 time(s). Last edit at 07/29/2023 12:58PM by chomick.

i strongly recomend you move this request to a different thread so as not to "pollute"/"hijack" this post.

in the new post, upload the log files for docker and if someone is knowledgeable with it - i don't mind having a tinker, time allowing. - then they will offer advise on ways forward.


you are jumping straight in the deep end though :) trying to run docker and X86 emulator when you consider yourself a newby...... i applaud you sir! BEST way to learn is dive in and see where you go

============================
Breaking stuff since 1994 :-)
============================

Guys,

new package doesnt work on wyse 3020 :(

root@debian:/boot# package architecture (armel) does not match system (armhf)

is there anyway to fix this?

chomick,

> root@debian:/boot# package architecture (armel)
> does not match system (armhf)
>
> is there anyway to fix this?

Make sure you installing the MVEBU kernel linux-6.4.11-mvebu-tld-1-bodhi.tar.bz2. Sounds like you're installing the wrong kernel (i.e Kirkwood).

If you meant "Debian package" then your apt source might be wrong.

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



Edited 1 time(s). Last edit at 08/22/2023 05:42PM by bodhi.

Do

cat /etc/apt/sources.list

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

Hi, can any owners of Wyse 3020 post output of:

/sys/kernel/debug/regmap/4-0058-ec_ram/registers

* (I don't know if it's exactly at this path, since I don't own this device)

I want to compare it with Wyse 3010. Thanks

--
TMN

tmn505,
Sorry for late reply, on 3020 it looks like that:

root@debian:~# ls -l /sys/kernel/debug/regmap/
total 0
drwxr-xr-x 2 root root 0 Jan  1  1970 0-0068
drwxr-xr-x 2 root root 0 Dec  9 14:19 2-0058-ec_ram
root@debian:~# cat /sys/kernel/debug/regmap/2-0058-ec_ram/registers 
00: ff
01: 01
02: 00
03: 01
04: ff
05: ff
06: ff
07: ff
08: ff
09: ff
0a: 01
0b: ff
0c: ff
0d: ff
0e: ff
0f: ff
10: 01
11: 01
12: 01
13: 01
14: 01
15: 01
16: 00
17: 00
18: 00
19: 00
1a: 00
1b: 00
1c: 00
1d: 00
1e: 00
1f: 00
20: 01
21: 01
22: 02
23: 00
24: 00
25: 00
26: 00
27: 00
28: 00
29: 00
2a: 00
2b: 00
2c: 00
2d: 00
2e: 00
2f: 00
30: 4a
31: 03
32: 02
33: 00
34: 00
35: 00
36: 00
37: 00
38: 00
39: 00
3a: 00
3b: 00
3c: 00
3d: 00
3e: 00
3f: 00
40: 00
41: 00
42: 00
43: 00
44: 99
45: ff
46: ff
47: ff
48: ff
49: ff
4a: ff
4b: ff
4c: ff
4d: ff
4e: ff
4f: ff
50: ff
51: ff
52: ff
53: ff
54: ff
55: ff
56: ff
57: ff
58: ff
59: ff
5a: ff
5b: ff
5c: ff
5d: ff
5e: ff
5f: ff
60: ff
61: ff
62: ff
63: ff
64: ff
65: ff
66: ff
67: ff
68: ff
69: ff
6a: ff
6b: ff
6c: ff
6d: ff
6e: ff
6f: ff
70: ff
71: ff
72: ff
73: ff
74: ff
75: ff
76: ff
77: ff
78: ff
79: ff
7a: ff
7b: ff
7c: ff
7d: ff
7e: ff
7f: ff
80: ff
81: ff
82: ff
83: ff
84: ff
85: ff
86: ff
87: ff
88: ff
89: ff
8a: ff
8b: ff
8c: ff
8d: ff
8e: ff
8f: ff
90: ff
91: ff
92: ff
93: ff
94: ff
95: ff
96: ff
97: ff
98: ff
99: ff
9a: ff
9b: ff
9c: ff
9d: ff
9e: ff
9f: ff
a0: ff
a1: ff
a2: ff
a3: ff
a4: ff
a5: ff
a6: ff
a7: ff
a8: ff
a9: ff
aa: ff
ab: ff
ac: ff
ad: ff
ae: ff
af: ff
b0: ff
b1: ff
b2: ff
b3: ff
b4: ff
b5: ff
b6: ff
b7: ff
b8: ff
b9: ff
ba: ff
bb: ff
bc: ff
bd: ff
be: ff
bf: ff
c0: ff
c1: ff
c2: ff
c3: ff
c4: ff
c5: ff
c6: ff
c7: ff
c8: ff
c9: ff
ca: ff
cb: ff
cc: ff
cd: ff
ce: ff
cf: ff
d0: ff
d1: ff
d2: ff
d3: ff
d4: ff
d5: ff
d6: ff
d7: ff
d8: ff
d9: ff
da: ff
db: ff
dc: ff
dd: ff
de: ff
df: ff
e0: ff
e1: ff
e2: ff
e3: ff
e4: ff
e5: ff
e6: ff
e7: ff
e8: ff
e9: ff
ea: ff
eb: ff
ec: ff
ed: ff
ee: ff
ef: ff
f0: ff
f1: ff
f2: ff
f3: ff
f4: ff
f5: ff
f6: ff
f7: ff
f8: ff
f9: ff
fa: ff
fb: ff
fc: ff
fd: ff
fe: ff
ff: ff
root@debian:~#

Hello, I am writing because I need help. This is my first time dealing with arm-based devices, but after reading the article here, I used version 6.6.2 of the Linux kernel image and Debian version 5.13.8 of the rootfs. The wloader.cfg setting was successfully applied, but the green indicator blinks and there is no response during booting. As I read the article, I learned that I need to connect via serial, but I don't have that much knowledge, so I don't know the detailed method yet.

My wloader.cfg configuration

<TX0D_START>
kernel=uImage
initrd=uInitrd
param="rootdelay=5 root=LABEL=rootfs raid=noautodetect console=ttyS2,115200 mtdparts=spi0.0:4m(boot) earlyprintk=serial"
<TX0D_END>

EDIT
I tried several times and the following occurred. When booting from USB, the keyboard light turns on and then immediately turns off. Also I am using thumb drive 32gb usb 3.0, perhaps the Dell 3020 custom kernel does not support USB 3.0?

I don't know if this is a good way, but I'm thinking of merging the wloader.cfg file with the rootfs. I thought it would be a little more convenient. I think I just need to know how to load rootfs into the 3020 hard disk (emmc?).

<TX0D_START>
kernel=./boot/uImage
initrd=./boot/uInitrd
param="rootdelay=5 root=LABEL=rootfs raid=noautodetect console=ttyS2,115200 mtdparts=spi0.0:4m(boot) earlyprintk=serial"
<TX0D_END>

I'm not good at hardware, but I'd like to help at least a little!



Edited 2 time(s). Last edit at 12/10/2023 09:02AM by LegacyObj.

Hi. My first post here. I got two Wyse 3020 terminals for really cheap (equivalent of $9 each including PSU and some crappy mouse) and for the last few days I'm playing with them. Thanks to tons of good info contained in this thread (great job guys!) I was able to install debian onto the emmc and configure wLoader to boot it.

However I come across an issue. To make it work I used Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 package but with linux-6.4.11-mvebu-tld-1-bodhi.tar.bz2 kernel.
When I try to boot from usb drive with Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2 rootfs and 6.6.2 kernel the boot process crashes with the following boot log:

[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 6.6.2-mvebu-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Mon Nov 20 18:44:27 PST 2023
[    0.000000][    T0] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d
[    0.000000][    T0] CPU: div instructions available: patching division code
[    0.000000][    T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: Dell Ariel
[    0.000000][    T0] Memory policy: Data cache writealloc
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   Normal   [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000][    T0]   HighMem  [mem 0x0000000030000000-0x000000007fefffff]
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000007fefffff]
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fefffff]
[    0.000000][    T0] percpu: Embedded 29 pages/cpu s25364 r8192 d85228 u118784
[    0.000000][    T0] Kernel command line: root=LABEL=rootfs raid=noautodetect console=ttyS2,115200
[    0.000000][    T0] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 522304
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000][    T0] Memory: 2052708K/2096128K available (10240K kernel code, 873K rwdata, 3492K rodata, 1024K init, 314K bss, 43420K reserved, 0K cma-reserved, 1309696K highmem)
[    0.000000][    T0] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] rcu:     RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000][    T0]  Trampoline variant of Tasks RCU enabled.
[    0.000000][    T0]  Tracing variant of Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] L2C: platform modifies aux control register: 0x02060000 -> 0x32860000
[    0.000000][    T0] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x32860000
[    0.000000][    T0] Tauros3 cache controller enabled, 8 ways, 512 kB
[    0.000000][    T0] Tauros3: CACHE_ID 0x880000ed, AUX_CTRL 0x32860000
[    0.000000][    T0] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000005][    T0] sched_clock: 32 bits at 26MHz, resolution 38ns, wraps every 82595524588ns
[    0.000065][    T0] clocksource: clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 73510017198 ns
[    0.000282][    T0] smp_twd: clock not found -2
[    0.000796][    T0] kfence: initialized - using 2097152 bytes for 255 objects at 0x(ptrval)-0x(ptrval)
[    0.001283][    T0] Console: colour dummy device 80x30
[    0.001330][    T0] Calibrating local timer... 2.16MHz.
[    0.060260][    T0] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    0.100286][    T0] CPU: Testing write buffer coherency: ok
[    0.100362][    T0] pid_max: default: 32768 minimum: 301
[    0.104652][    T0] LSM: initializing lsm=capability,integrity
[    0.105913][    T0] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.105933][    T0] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.111865][    T1] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.114022][    T1] RCU Tasks: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1.
[    0.114287][    T1] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1.
[    0.114498][    T1] Setting up static identity map for 0x100000 - 0x100060
[    0.115118][    T1] rcu: Hierarchical SRCU implementation.
[    0.115127][    T1] rcu:     Max phase no-delay instances is 1000.
[    0.116555][    T1] smp: Bringing up secondary CPUs ...
[    0.150292][    T0] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.151058][    T1] smp: Brought up 1 node, 2 CPUs
[    0.151076][    T1] SMP: Total of 2 processors activated (2382.23 BogoMIPS).
[    0.151089][    T1] CPU: All CPU(s) started in SVC mode.
[    0.153449][    T1] devtmpfs: initialized
[    0.165025][    T1] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[    0.165650][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.165692][    T1] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    0.168653][    T1] prandom: seed boundary self test passed
[    0.171227][    T1] prandom: 100 self tests passed
[    0.171243][    T1] pinctrl core: initialized pinctrl subsystem
[    0.173587][    T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.174232][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.185485][    T1] audit: initializing netlink subsys (disabled)
[    0.186904][    T1] thermal_sys: Registered thermal governor 'step_wise'
[    0.187030][   T30] audit: type=2000 audit(0.190:1): state=initialized audit_enabled=0 res=1
[    0.187106][    T1] cpuidle: using governor ladder
[    0.187158][    T1] cpuidle: using governor menu
[    0.187348][   T19] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0
[    0.187364][   T19] hw-breakpoint: CPU 0 failed to disable vector catch
[    0.187423][   T20] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 1
[    0.191202][    T1] platform soc: Fixed dependency cycle(s) with /soc/interrupt-controller@e0001000
[    0.370510][    T1] raid6: int32x8  gen()   223 MB/s
[    0.540595][    T1] raid6: int32x4  gen()   238 MB/s
[    0.710704][    T1] raid6: int32x2  gen()   366 MB/s
[    0.880872][    T1] raid6: int32x1  gen()   350 MB/s
[    0.880885][    T1] raid6: using algorithm int32x2 gen() 366 MB/s
[    1.050931][    T1] raid6: .... xor() 221 MB/s, rmw enabled
[    1.050943][    T1] raid6: using intx1 recovery algorithm
[    1.053082][    T1] SCSI subsystem initialized
[    1.053772][    T1] usbcore: registered new interface driver usbfs
[    1.053842][    T1] usbcore: registered new interface driver hub
[    1.053944][    T1] usbcore: registered new device driver usb
[    1.054437][    T1] pps_core: LinuxPPS API ver. 1 registered
[    1.054450][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.054482][    T1] PTP clock support registered
[    1.057581][    T1] vgaarb: loaded
[    1.058459][    T1] clocksource: Switched to clocksource clocksource
[    1.070719][    T1] VFS: Disk quotas dquot_6.6.0
[    1.071281][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.096720][    T1] NET: Registered PF_INET protocol family
[    1.097143][    T1] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    1.099479][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    1.099767][    T1] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    1.099848][    T1] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    1.099974][    T1] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    1.100113][    T1] TCP: Hash tables configured (established 8192 bind 8192)
[    1.101006][    T1] MPTCP token hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    1.101536][    T1] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    1.101578][    T1] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    1.102688][    T1] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    1.104109][    T1] RPC: Registered named UNIX socket transport module.
[    1.104126][    T1] RPC: Registered udp transport module.
[    1.104135][    T1] RPC: Registered tcp transport module.
[    1.104143][    T1] RPC: Registered tcp-with-tls transport module.
[    1.104151][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.104181][    T1] PCI: CLS 0 bytes, default 64
[    1.109179][   T29] Trying to unpack rootfs image as initramfs...
[    1.119920][    T1] Initialise system trusted keyrings
[    1.120061][    T1] Key type blacklist registered
[    1.120835][    T1] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    1.120942][    T1] zbud: loaded
[    1.153432][    T1] NFS: Registering the id_resolver key type
[    1.153521][    T1] Key type id_resolver registered
[    1.153532][    T1] Key type id_legacy registered
[    1.153906][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.153935][    T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.269433][    T1] xor: measuring software checksum speed
[    1.277679][    T1]    arm4regs        :  1198 MB/sec
[    1.289344][    T1]    8regs           :   855 MB/sec
[    1.298536][    T1]    32regs          :  1082 MB/sec
[    1.298556][    T1] xor: using function: arm4regs (1198 MB/sec)
[    1.298591][    T1] async_tx: api initialized (async)
[    1.298620][    T1] Key type asymmetric registered
[    1.298633][    T1] Asymmetric key parser 'x509' registered
[    1.299349][    T1] bounce: pool size: 64 pages
[    1.300576][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    1.301583][    T1] io scheduler bfq registered
[    1.332083][    T1] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.397905][   T29] Freeing initrd memory: 5136K
[    1.614834][    T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.626566][    T1] printk: console [ttyS2] disabled
[    1.627401][    T1] d4018000.serial: ttyS2 at MMIO 0xd4018000 (irq = 381, base_baud = 1625000) is a XScale
[    1.627460][    T1] printk: console [ttyS2] enabled
[    2.535239][    T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    2.543832][    T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[    2.568814][    T1] usbcore: registered new interface driver smsc75xx
[    2.576599][    T1] mv-ehci d4208000.usb: EHCI Host Controller
[    2.582560][    T1] mv-ehci d4208000.usb: new USB bus registered, assigned bus number 1
[    2.591980][    T1] mv-ehci d4208000.usb: irq 382, io mem 0xd4208000
[    2.618574][    T1] mv-ehci d4208000.usb: USB 2.0 started, EHCI 1.00
[    2.625562][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    2.634544][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.642455][    T1] usb usb1: Product: EHCI Host Controller
[    2.647987][    T1] usb usb1: Manufacturer: Linux 6.6.2-mvebu-tld-1 ehci_hcd
[    2.655021][    T1] usb usb1: SerialNumber: d4208000.usb
[    2.661888][    T1] hub 1-0:1.0: USB hub found
[    2.666377][    T1] hub 1-0:1.0: 1 port detected
[    2.671846][    T1] mv-ehci d4208000.usb: successful find EHCI device with regs 0x(ptrval) irq 382 working in Host mode
[    2.682963][    T1] usbcore: registered new interface driver usblp
[    2.689465][    T1] usbcore: registered new interface driver usb-storage
[    2.697586][    T1] mousedev: PS/2 mouse device common for all mice
[    2.704980][    T1] i2c_dev: i2c /dev entries driver
[    2.715582][    T1] device-mapper: uevent: version 1.0.3
[    2.721968][    T1] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
[    2.731898][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[    2.739189][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[    2.746456][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
[    2.754236][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    2.761647][    T1] sdhci: Secure Digital Host Controller Interface driver
[    2.768549][    T1] sdhci: Copyright(c) Pierre Ossman
[    2.774720][    T1] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.785014][    T1] hid: raw HID events driver (C) Jiri Kosina
[    2.792158][    T1] usbcore: registered new interface driver usbhid
[    2.798394][    T1] usbhid: USB HID core driver
[    2.807521][    T1] NET: Registered PF_INET6 protocol family
[    2.816005][    T1] Segment Routing with IPv6
[    2.820547][  T707] mmc0: SDHCI controller on d4281000.mmc [d4281000.mmc] using ADMA
[    2.820920][    T1] RPL Segment Routing with IPv6
[    2.833192][    T1] In-situ OAM (IOAM) with IPv6
[    2.837901][    T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.846923][    T1] NET: Registered PF_PACKET protocol family
[    2.853174][    T1] 8021q: 802.1Q VLAN Support v1.8
[    2.858200][    T1] Key type dns_resolver registered
[    2.863513][    T1] ThumbEE CPU extension supported.
[    2.868523][    T1] Registering SWP/SWPB emulation handler
[    2.873972][    T1] PJ4 iWMMXt v2 coprocessor enabled.
[    2.968587][   T23] usb 1-1: new high-speed USB device number 2 using mv-ehci
[    2.975985][    T1] registered taskstats version 1
[    2.981199][    T1] Loading compiled-in X.509 certificates
[    3.022040][    T1] Key type .fscrypt registered
[    3.026652][    T1] Key type fscrypt-provisioning registered
[    3.032542][    T1] Key type big_key registered
[    3.040619][   T69] mmc0: new HS200 MMC card at address 0001
[    3.042534][    T1] Key type encrypted registered
[    3.071758][  T707] mv-ehci f0001000.usb: EHCI Host Controller
[    3.077597][  T707] mv-ehci f0001000.usb: new USB bus registered, assigned bus number 2
[    3.085863][  T707] mv-ehci f0001000.usb: irq 384, io mem 0xf0001000
[    3.168514][  T707] mv-ehci f0001000.usb: USB 2.0 started, EHCI 1.00
[    3.175333][  T707] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    3.184296][  T707] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.192213][  T707] usb usb2: Product: EHCI Host Controller
[    3.197751][  T707] usb usb2: Manufacturer: Linux 6.6.2-mvebu-tld-1 ehci_hcd
[    3.204841][  T707] usb usb2: SerialNumber: f0001000.usb
[    3.211805][  T707] hub 2-0:1.0: USB hub found
[    3.216323][   T23] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=77.63
[    3.218648][  T707] hub 2-0:1.0: 1 port detected
[    3.225211][   T23] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    3.230977][  T707] mv-ehci f0001000.usb: successful find EHCI device with regs 0x(ptrval) irq 384 working in Host mode
[    3.237554][   T23] usb 1-1: Product: USB2.0 Hub
[    3.252140][    T1] clk: Disabling unused clocks
[    3.259033][   T23] hub 1-1:1.0: USB hub found
[    3.266549][    T1] Freeing unused kernel image (initmem) memory: 1024K
[    3.273260][   T23] hub 1-1:1.0: 4 ports detected
[    3.310672][    T1] Checked W+X mappings: passed, no W+X pages found
[    3.317010][    T1] Run /init as init process
[    3.323140][    T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    3.331449][    T1] CPU: 1 PID: 1 Comm: init Not tainted 6.6.2-mvebu-tld-1 #1
[    3.338533][    T1] Hardware name: Marvell MMP3
[    3.343036][    T1]  unwind_backtrace from show_stack+0x10/0x14
[    3.348943][    T1]  show_stack from dump_stack_lvl+0x40/0x4c
[    3.354665][    T1]  dump_stack_lvl from panic+0x104/0x308
[    3.360116][    T1]  panic from do_exit+0x264/0x8c4
[    3.364976][    T1]  do_exit from sys_exit_group+0x0/0x10
[    3.370350][    C0] CPU0: stopping
[    3.370361][    C0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.6.2-mvebu-tld-1 #1
[    3.370373][    C0] Hardware name: Marvell MMP3
[    3.370381][    C0]  unwind_backtrace from show_stack+0x10/0x14
[    3.370404][    C0]  show_stack from dump_stack_lvl+0x40/0x4c
[    3.370421][    C0]  dump_stack_lvl from do_handle_IPI+0x84/0x11c
[    3.370439][    C0]  do_handle_IPI from ipi_handler+0x14/0x20
[    3.370455][    C0]  ipi_handler from handle_percpu_devid_irq+0x4c/0xe8
[    3.370482][    C0]  handle_percpu_devid_irq from handle_irq_desc+0x1c/0x2c
[    3.370515][    C0]  handle_irq_desc from gic_handle_irq+0x58/0x64
[    3.370545][    C0]  gic_handle_irq from generic_handle_arch_irq+0x28/0x3c
[    3.370564][    C0]  generic_handle_arch_irq from __irq_svc+0x88/0xc8
[    3.370581][    C0] Exception stack(0xc1001f28 to 0xc1001f70)
[    3.370595][    C0] 1f20:                   00000000 c0de2baf 0001ce84 00000001 00000000 00000000
[    3.370608][    C0] 1f40: 00000000 c100e180 c100a010 c100a070 c0f42104 00000039 c1003d40 c1001f78
[    3.370618][    C0] 1f60: c0a87e38 c015674c 200c0013 ffffffff
[    3.370626][    C0]  __irq_svc from do_idle+0x108/0x280
[    3.370644][    C0]  do_idle from cpu_startup_entry+0x28/0x2c
[    3.370659][    C0]  cpu_startup_entry from rest_init+0xb8/0xd4
[    3.370677][    C0]  rest_init from arch_post_acpi_subsys_init+0x0/0x8
[    3.494256][    T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---

Any ideas how to fix this?
I did try kernel 6.3.5 and 6.4.11 and they worked. I didn't try kernel 6.5.7 yet.
EDIT: I checked kernel 6.5.7 and it booted successfully, so it does crash only on the latest kernel.


As for how I managed to make it boot directly from emmc, I'm not really sure which steps were necessary as I was just messing with different things, but in a nutshell:
- I installed Debian 6.6.2 with kernel 6.4.11 on USB flash drive, with two partitions, one FAT with uImage/uInitrd/wloader.cfg files and second ext3 with rootfs - the same thing other guys did.
- I booted successfully from this flash drive manualy from wLoader and sshed into it.
- No mmc was visible so I installed kernel 6.4.11 deb file and rebooted, after reboot mmc was present.
- I removed all partitions from mmc and created similar partition structure as on the flash drive - one FAT partition and one ext3 partition.
- I copied uImage/uInitrd/wloader.cfg into FAT partition and tried to boot from it manually through wLoader, however in this moment I noticed that it is not possible as uInitrd file doesn't have required mmc drivers (this is the reason I didn't see mmc after the first boot)
- So I run system from the flash drive again, use lsmod command to see which modules where loaded from rootfs and make those modules mandatory in config-6.4.11-mvebu-tld-1 file. Next, I run update-initramfs and mkimage commands to recreate uInitrd with all required drivers.
- I copied the new uInitrd file to FAT partition on mmc, and prepared ext3 partition on mmc using the same steps as with the flash drive.
- I removed the flash drive, rebooted the machine and entered wLoader settings.
- On the Settings page almost all controls were grayed, the bootloader mode was set to WTOS and only option was to change kernel image name, I changed it to uImage and clicked shutdown
- Next I rebooted the system but I was holding power button for 20 seconds trying to see if it will reset it to the factory settings.
- I'm not sure which of the previous steps helped, but after the next reboot when I opened wLoader, the Settings panel looked different (see attached screenshot), the mode was changed to Linux, all fields were editable and filled with completely different values. I changed kernel parameter field to the same line I used in wloader.cfg file and after the reboot the machine booted sucessfully from emmc.



Edited 2 time(s). Last edit at 02/06/2024 11:32AM by ksuszka.

I've just tested the wLoader mode change on the second terminal and it is super easy. There is no need to do anything with emmc or usb. Just open wLoader settings, go to the Setting tab, replace `T10D_wnos` text with `uImage` and hit enter key, after reboot go again to wLoader's Setting page and you should see boot mode changed to Linux.

I attached before and after screenshots only after replacing this single text entry.

Unfortunately, changing kernel text from uImage back to T10D_wnos doesn't restore previous boot mode, however after this change a new item in boot menu appears: "ImageUpgrade", so it should be possible to use an image from Dell website to go back to the original system.

EDIT: To go back to WNOS mode it is enough to reset WLoader to factory settings. There are two options to do so:

1. Press the power button for about four seconds until the power light turns green, and then press the G key. There should be a message about factory reset and after a while you can reboot machine and when you go to WLoader setting it should be back in WNOS mode.
2. Press the power button for about four seconds until the power light turns green, and then press the Delete key to enter WLoader settings. Enter "Fireport" password. Press Shutdown button and on the modal dialog box select checkbox to reset WLoader to factory settings.



Edited 2 time(s). Last edit at 02/09/2024 02:04PM by ksuszka.

Hello there,

This is my first time posting here as well. I really appreciate all the work that went into this, and would be very happy if I could help as well :).

I wrote this script to automate installation to a USB drive:

#!/bin/bash

# https://forum.doozan.com/read.php?2,32146
rootfs_dl="https://bit.ly/3Tq9pTO";
rootfs="Debian-6.6.2-mvebu-tld-1-rootfs-bodhi.tar.bz2"
rootfs_sig="009d315ebc813868344ce9221bcc3c70"

# 6.5.7
kernel_dl="https://bit.ly/3Qrb6i7";
kernel="linux-6.5.7-mvebu-tld-1-bodhi.tar.bz2"
kernel_sig="f972f4bf0e99859c9281bf67c361185d"

# 6.6.2 - currently broken for me
#kernel_dl="https://bit.ly/47Kt3hu";
#kernel="linux-6.6.2-mvebu-tld-1-bodhi.tar.bz2"
#kernel_sig="da257c4ecbc3eb5e39c11728dc85bacd"


if [ $# -eq 0 ]; then
    cat <<EOF
Usage: $(basename "$0") <device>

Install Linux MVEBU for Dell Wyse 3020 on a block device.

Arguments:
  <device>  Target device.

Example:
  $(basename "$0") /dev/sdX

Supported version:
  kernel: $kernel ($kernel_dl)
  rootfs: $rootfs ($rootfs_dl)
EOF
    exit 1
fi


if [ ! -e $rootfs ]; then
    echo "Error: $rootfs not found in current working directory. Please download it from $rootfs_dl"
    exit 1
fi
if [ ! -e $kernel ]; then
    echo "Error: $kernel not found in current working directory. Please download it from $kernel_dl"
    exit 1
fi

if [ ! $(md5sum $rootfs | awk '{print $1}') == $rootfs_sig ]; then
    echo "Error: MD5 hash verification for $rootfs failed."
fi
if [ ! $(md5sum $kernel | awk '{print $1}') == $kernel_sig ]; then
    echo "Error: MD5 hash verification for $kernel failed."
fi


if [ "$(id -u)" != "0" ]; then
    echo "This script requires root privileges."
    exit 1
fi

device=$1

if [ ! -e "$device" ]; then
    echo "Error: Device $device not found."
    exit 1
fi


read -p "Warning: This will overwrite all data on $device. Are you sure you want to continue? [y/N]: " confirm
if [ "$confirm" != "y" ]; then
    echo "Operation cancelled."
    exit 1
fi

set -e
set -x

sfdisk "$device" <<EOF
label: dos
device: $device
unit: sectors
sector-size: 512

${device}1 : start=        2048, size=      131072, type=c
${device}2 : start=      133120, size=            , type=83
EOF

mkfs -t fat ${device}1
mkfs -t ext3 ${device}2
e2label ${device}2 rootfs

mkdir /mnt/rootfs /mnt/bootfs
mount ${device}2 /mnt/rootfs
mount ${device}1 /mnt/bootfs

# https://forum.doozan.com/read.php?2,134563,135415#msg-135415
tar -C /mnt/rootfs/ -xf $rootfs 
tar -C /mnt/bootfs/ -xf $kernel
tar -C /mnt/bootfs/ -xf /mnt/bootfs/linux-dtb-*

cat /mnt/bootfs/zImage-* /mnt/bootfs/dts/mmp3-dell-ariel.dtb > /mnt/bootfs/zImage.fdt

mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -d /mnt/bootfs/zImage.fdt /mnt/bootfs/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -d /mnt/rootfs/boot/initrd.img-* /mnt/bootfs/uInitrd

rm /mnt/rootfs/root/set_persistent_mac_address
sed -i 's/ttyS0 115200/ttyS2 115200/' /mnt/rootfs/etc/inittab
sed -i '2a rename \/enx*=eth0' /mnt/rootfs/etc/network/interfaces

cat >/mnt/bootfs/wloader.cfg <<EOF
<TX0D_START>
kernel=uImage
initrd=uInitrd
param="rootdelay=5 root=LABEL=rootfs raid=noautodetect console=ttyS2,115200 mtdparts=spi0.0:4m(boot)"
<TX0D_END>
EOF

umount /mnt/rootfs /mnt/bootfs
rmdir /mnt/rootfs /mnt/bootfs

This allowed me to test a few different kernel releases, and I can verify that 6.6.2 causes a kernel panic:

[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 6.6.2-mvebu-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Mon Nov 20 18:44:27 PST 2023
[    0.000000][    T0] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d
[    0.000000][    T0] CPU: div instructions available: patching division code
[    0.000000][    T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: Dell Ariel
[    0.000000][    T0] Memory policy: Data cache writealloc
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   Normal   [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000][    T0]   HighMem  [mem 0x0000000030000000-0x000000007fefffff]
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000007fefffff]
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fefffff]
[    0.000000][    T0] percpu: Embedded 29 pages/cpu s25364 r8192 d85228 u118784
[    0.000000][    T0] Kernel command line: root=LABEL=rootfs raid=noautodetect console=ttyS2,115200
[    0.000000][    T0] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 522304
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000][    T0] Memory: 2052708K/2096128K available (10240K kernel code, 873K rwdata, 3492K rodata, 1024K init, 314K bss, 43420K reserved, 0K cma-reserved, 1309696K highmem)
[    0.000000][    T0] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] rcu: 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000][    T0] 	Trampoline variant of Tasks RCU enabled.
[    0.000000][    T0] 	Tracing variant of Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] L2C: platform modifies aux control register: 0x02060000 -> 0x32860000
[    0.000000][    T0] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x32860000
[    0.000000][    T0] Tauros3 cache controller enabled, 8 ways, 512 kB
[    0.000000][    T0] Tauros3: CACHE_ID 0x880000ed, AUX_CTRL 0x32860000
[    0.000000][    T0] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000005][    T0] sched_clock: 32 bits at 26MHz, resolution 38ns, wraps every 82595524588ns
[    0.000065][    T0] clocksource: clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 73510017198 ns
[    0.000280][    T0] smp_twd: clock not found -2
[    0.000792][    T0] kfence: initialized - using 2097152 bytes for 255 objects at 0x(ptrval)-0x(ptrval)
[    0.001282][    T0] Console: colour dummy device 80x30
[    0.001330][    T0] Calibrating local timer... 2.16MHz.
[    0.060261][    T0] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[    0.100288][    T0] CPU: Testing write buffer coherency: ok
[    0.100362][    T0] pid_max: default: 32768 minimum: 301
[    0.104653][    T0] LSM: initializing lsm=capability,integrity
[    0.105914][    T0] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.105933][    T0] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.111876][    T1] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.114044][    T1] RCU Tasks: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1.
[    0.114311][    T1] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1.
[    0.114521][    T1] Setting up static identity map for 0x100000 - 0x100060
[    0.115140][    T1] rcu: Hierarchical SRCU implementation.
[    0.115150][    T1] rcu: 	Max phase no-delay instances is 1000.
[    0.116582][    T1] smp: Bringing up secondary CPUs ...
[    0.150296][    T0] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.151060][    T1] smp: Brought up 1 node, 2 CPUs
[    0.151079][    T1] SMP: Total of 2 processors activated (2382.23 BogoMIPS).
[    0.151092][    T1] CPU: All CPU(s) started in SVC mode.
[    0.153449][    T1] devtmpfs: initialized
[    0.165040][    T1] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[    0.165665][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.165706][    T1] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[    0.168683][    T1] prandom: seed boundary self test passed
[    0.171257][    T1] prandom: 100 self tests passed
[    0.171271][    T1] pinctrl core: initialized pinctrl subsystem
[    0.173625][    T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.174268][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.185521][    T1] audit: initializing netlink subsys (disabled)
[    0.186939][    T1] thermal_sys: Registered thermal governor 'step_wise'
[    0.187064][   T30] audit: type=2000 audit(0.190:1): state=initialized audit_enabled=0 res=1
[    0.187141][    T1] cpuidle: using governor ladder
[    0.187194][    T1] cpuidle: using governor menu
[    0.187381][   T19] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0
[    0.187398][   T19] hw-breakpoint: CPU 0 failed to disable vector catch
[    0.187456][   T20] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 1
[    0.191230][    T1] platform soc: Fixed dependency cycle(s) with /soc/interrupt-controller@e0001000
[    0.370555][    T1] raid6: int32x8  gen()   223 MB/s
[    0.540683][    T1] raid6: int32x4  gen()   238 MB/s
[    0.710750][    T1] raid6: int32x2  gen()   365 MB/s
[    0.880884][    T1] raid6: int32x1  gen()   351 MB/s
[    0.880897][    T1] raid6: using algorithm int32x2 gen() 365 MB/s
[    1.050966][    T1] raid6: .... xor() 221 MB/s, rmw enabled
[    1.050978][    T1] raid6: using intx1 recovery algorithm
[    1.053111][    T1] SCSI subsystem initialized
[    1.053807][    T1] usbcore: registered new interface driver usbfs
[    1.053876][    T1] usbcore: registered new interface driver hub
[    1.053979][    T1] usbcore: registered new device driver usb
[    1.054468][    T1] pps_core: LinuxPPS API ver. 1 registered
[    1.054480][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.054512][    T1] PTP clock support registered
[    1.057622][    T1] vgaarb: loaded
[    1.058498][    T1] clocksource: Switched to clocksource clocksource
[    1.070755][    T1] VFS: Disk quotas dquot_6.6.0
[    1.071316][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.096763][    T1] NET: Registered PF_INET protocol family
[    1.097189][    T1] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    1.099531][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    1.099827][    T1] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    1.099908][    T1] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    1.100034][    T1] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    1.100172][    T1] TCP: Hash tables configured (established 8192 bind 8192)
[    1.101066][    T1] MPTCP token hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    1.101600][    T1] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    1.101643][    T1] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    1.102758][    T1] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    1.104182][    T1] RPC: Registered named UNIX socket transport module.
[    1.104198][    T1] RPC: Registered udp transport module.
[    1.104207][    T1] RPC: Registered tcp transport module.
[    1.104215][    T1] RPC: Registered tcp-with-tls transport module.
[    1.104224][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.104254][    T1] PCI: CLS 0 bytes, default 64
[    1.109233][   T29] Trying to unpack rootfs image as initramfs...
[    1.120032][    T1] Initialise system trusted keyrings
[    1.120195][    T1] Key type blacklist registered
[    1.120959][    T1] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    1.121072][    T1] zbud: loaded
[    1.153600][    T1] NFS: Registering the id_resolver key type
[    1.153667][    T1] Key type id_resolver registered
[    1.153677][    T1] Key type id_legacy registered
[    1.154051][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.154080][    T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[    1.269634][    T1] xor: measuring software checksum speed
[    1.277884][    T1]    arm4regs        :  1198 MB/sec
[    1.289551][    T1]    8regs           :   854 MB/sec
[    1.298741][    T1]    32regs          :  1082 MB/sec
[    1.298758][    T1] xor: using function: arm4regs (1198 MB/sec)
[    1.298793][    T1] async_tx: api initialized (async)
[    1.298819][    T1] Key type asymmetric registered
[    1.298831][    T1] Asymmetric key parser 'x509' registered
[    1.299546][    T1] bounce: pool size: 64 pages
[    1.300741][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    1.301755][    T1] io scheduler bfq registered
[    1.332208][    T1] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    1.397188][   T29] Freeing initrd memory: 5136K
[    1.598700][    T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.609294][    T1] printk: console [ttyS2] disabled
[    1.611100][    T1] d4018000.serial: ttyS2 at MMIO 0xd4018000 (irq = 381, base_baud = 1625000) is a XScale
[    1.611439][    T1] printk: console [ttyS2] enabled
[    2.520710][    T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    2.529317][    T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[    2.544262][    T1] usbcore: registered new interface driver smsc75xx
[    2.555031][    T1] mv-ehci d4208000.usb: EHCI Host Controller
[    2.566637][    T1] mv-ehci d4208000.usb: new USB bus registered, assigned bus number 1
[    2.576053][    T1] mv-ehci d4208000.usb: irq 382, io mem 0xd4208000
[    2.618590][    T1] mv-ehci d4208000.usb: USB 2.0 started, EHCI 1.00
[    2.625466][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    2.634440][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.642348][    T1] usb usb1: Product: EHCI Host Controller
[    2.647881][    T1] usb usb1: Manufacturer: Linux 6.6.2-mvebu-tld-1 ehci_hcd
[    2.654937][    T1] usb usb1: SerialNumber: d4208000.usb
[    2.661793][    T1] hub 1-0:1.0: USB hub found
[    2.666289][    T1] hub 1-0:1.0: 1 port detected
[    2.671743][    T1] mv-ehci d4208000.usb: successful find EHCI device with regs 0x(ptrval) irq 382 working in Host mode
[    2.683330][    T1] usbcore: registered new interface driver usblp
[    2.689846][    T1] usbcore: registered new interface driver usb-storage
[    2.697704][    T1] mousedev: PS/2 mouse device common for all mice
[    2.707001][    T1] i2c_dev: i2c /dev entries driver
[    2.715850][    T1] device-mapper: uevent: version 1.0.3
[    2.722154][    T1] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
[    2.732134][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[    2.739382][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[    2.746644][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
[    2.754190][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    2.761670][    T1] sdhci: Secure Digital Host Controller Interface driver
[    2.768567][    T1] sdhci: Copyright(c) Pierre Ossman
[    2.773766][    T1] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.780884][    T1] hid: raw HID events driver (C) Jiri Kosina
[    2.788118][    T1] usbcore: registered new interface driver usbhid
[    2.794419][    T1] usbhid: USB HID core driver
[    2.802202][    T1] NET: Registered PF_INET6 protocol family
[    2.810259][    T1] Segment Routing with IPv6
[    2.814600][    T1] RPL Segment Routing with IPv6
[    2.815586][   T25] mmc0: SDHCI controller on d4281000.mmc [d4281000.mmc] using ADMA
[    2.819549][    T1] In-situ OAM (IOAM) with IPv6
[    2.831838][    T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.841854][    T1] NET: Registered PF_PACKET protocol family
[    2.848210][    T1] 8021q: 802.1Q VLAN Support v1.8
[    2.853343][    T1] Key type dns_resolver registered
[    2.858936][    T1] ThumbEE CPU extension supported.
[    2.863942][    T1] Registering SWP/SWPB emulation handler
[    2.869551][    T1] PJ4 iWMMXt v2 coprocessor enabled.
[    2.958645][   T69] usb 1-1: new high-speed USB device number 2 using mv-ehci
[    2.969086][    T1] registered taskstats version 1
[    2.974202][    T1] Loading compiled-in X.509 certificates
[    3.016070][    T1] Key type .fscrypt registered
[    3.020966][    T1] Key type fscrypt-provisioning registered
[    3.026859][    T1] Key type big_key registered
[    3.036590][    T1] Key type encrypted registered
[    3.060198][   T61] mmc0: Tuning failed, falling back to fixed sampling clock
[    3.070994][   T26] mv-ehci f0001000.usb: EHCI Host Controller
[    3.077455][   T26] mv-ehci f0001000.usb: new USB bus registered, assigned bus number 2
[    3.085595][   T61] mmc0: new HS200 MMC card at address 0001
[    3.091646][   T26] mv-ehci f0001000.usb: irq 384, io mem 0xf0001000
[    3.148575][   T26] mv-ehci f0001000.usb: USB 2.0 started, EHCI 1.00
[    3.155467][   T26] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06
[    3.164462][   T26] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.170431][   T69] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=77.63
[    3.172426][   T26] usb usb2: Product: EHCI Host Controller
[    3.181214][   T69] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    3.186738][   T26] usb usb2: Manufacturer: Linux 6.6.2-mvebu-tld-1 ehci_hcd
[    3.194628][   T69] usb 1-1: Product: USB2.0 Hub
[    3.201614][   T26] usb usb2: SerialNumber: f0001000.usb
[    3.213422][   T26] hub 2-0:1.0: USB hub found
[    3.215499][   T69] hub 1-1:1.0: USB hub found
[    3.217932][   T26] hub 2-0:1.0: 1 port detected
[    3.222814][   T69] hub 1-1:1.0: 4 ports detected
[    3.229094][   T26] mv-ehci f0001000.usb: successful find EHCI device with regs 0x(ptrval) irq 384 working in Host mode
[    3.244282][    T1] clk: Disabling unused clocks
[    3.253269][    T1] Freeing unused kernel image (initmem) memory: 1024K
[    3.300658][    T1] Checked W+X mappings: passed, no W+X pages found
[    3.306991][    T1] Run /init as init process
[    3.313414][    T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    3.321720][    T1] CPU: 1 PID: 1 Comm: init Not tainted 6.6.2-mvebu-tld-1 #1
[    3.328805][    T1] Hardware name: Marvell MMP3
[    3.333313][    T1]  unwind_backtrace from show_stack+0x10/0x14
[    3.339222][    T1]  show_stack from dump_stack_lvl+0x40/0x4c
[    3.344944][    T1]  dump_stack_lvl from panic+0x104/0x308
[    3.350397][    T1]  panic from do_exit+0x264/0x8c4
[    3.355256][    T1]  do_exit from sys_exit_group+0x0/0x10
[    3.360631][    C0] CPU0: stopping
[    3.360641][    C0] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.6.2-mvebu-tld-1 #1
[    3.360654][    C0] Hardware name: Marvell MMP3
[    3.360663][    C0]  unwind_backtrace from show_stack+0x10/0x14
[    3.360686][    C0]  show_stack from dump_stack_lvl+0x40/0x4c
[    3.360702][    C0]  dump_stack_lvl from do_handle_IPI+0x84/0x11c
[    3.360720][    C0]  do_handle_IPI from ipi_handler+0x14/0x20
[    3.360736][    C0]  ipi_handler from handle_percpu_devid_irq+0x4c/0xe8
[    3.360763][    C0]  handle_percpu_devid_irq from handle_irq_desc+0x1c/0x2c
[    3.360798][    C0]  handle_irq_desc from gic_handle_irq+0x58/0x64
[    3.360829][    C0]  gic_handle_irq from generic_handle_arch_irq+0x28/0x3c
[    3.360847][    C0]  generic_handle_arch_irq from __irq_svc+0x88/0xc8
[    3.360864][    C0] Exception stack(0xc1001f28 to 0xc1001f70)
[    3.360878][    C0] 1f20:                   00000000 c0de2baf 00001214 00000001 00000000 00000000
[    3.360891][    C0] 1f40: 00000000 c100e180 c100a010 c100a070 c0f42104 00000039 c1003d40 c1001f78
[    3.360900][    C0] 1f60: c0a87e38 c015674c 200c0013 ffffffff
[    3.360908][    C0]  __irq_svc from do_idle+0x108/0x280
[    3.360927][    C0]  do_idle from cpu_startup_entry+0x28/0x2c
[    3.360942][    C0]  cpu_startup_entry from rest_init+0xb8/0xd4
[    3.360960][    C0]  rest_init from arch_post_acpi_subsys_init+0x0/0x8
[    3.484544][    T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---

Installing the 6.5.7 kernel with the 6.6.2 rootfs works perfectly fine however, so that's what I left in the installation script.

Here are a few observations that I have been able to make so far, hopefully the're helpful for anyone trying to boot Debian:
1. USB 3.0 drives definitely work with the stock bootloader
2. 8GB drives worked without any issues, but a 32GB drive was skipped by the bootloader, "No URL found".
3. Booting with "earlyprintk=serial" prevented the device from booting

That's everything that i currently have to add. Next I'll try following ksuszka's suggestions to boot directly from eMMC :).

- mmm

Hello again,

I worked a bit on my installation script, sadly can't update my old post but here's a link to the updated version.

Everything I got working:

• Ethernet
• Serial
• Power LED
• Shutdown
• Reboot
• RTC
• RTC after reboot
• Read SPI
• Read SPI after reboot
• Read eMMC
• Read eMMC after shutting down, removing power, and selecting USB from the boot menu
• Write to eMMC

What I couldn't get working:

• Power button
• Read eMMC after reboot
• Read eMMC after shutdown
• Boot from eMMC

I did get quite far into the eMMC installation however:

• Initial installation was done with the script
• I continued by installing the 6.5.7 kernel package onto the device (with the embedded "install-kernel.sh" script).
• I copied the installation script and required archives and ran it again, this time installing into /dev/mmcblk0.
• I was even able to change the Wloader boot mode to linux, using ksuszka's instructions.
• Buuuut it refused to boot from eMMC, "Cannot load OS from PAR1. Press any key to continue."
• Tried repartitioning the eMMC, changing the MBR label ID, but nothing seemed to help.

ksuszka, would you mind explaining how you partitioned the eMMC? Thanks :).

- mmm

@mmm If you want to boot from eMMC you need to include missing kernel modules into the initramfs image, So when you extract 6.5.7 kernel and before you use mkimage for uInitrd run something like:

sed -i -E 's/(CONFIG_MMC_BLOCK|CONFIG_USB_UAS|CONFIG_PXA_SSP|CONFIG_SPI_PXA2XX|CONFIG_I2C_PXA|CONFIG_UIO|CONFIG_UIO_PDRV_GENIRQ)=m/\1=y/' config-6.5.7-mvebu-tld-1

I partitioned the eMMC in exactly the same way as I did with the flash drive. My current partitions:

root@debian:/# fdisk -l
Disk /dev/mmcblk0: 3.64 GiB, 3909091328 bytes, 7634944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device         Boot  Start     End Sectors  Size Id Type
/dev/mmcblk0p1 *      2048  206847  204800  100M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      206848 7634943 7428096  3.5G 83 Linux


Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mtdblock0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

root@debian:/# lsblk -o name,mountpoint,label,size
\NAME         MOUNTPOINT LABEL      SIZE
sda                                  0B
mtdblock0                            4M
mmcblk0                            3.6G
|-mmcblk0p1             MMCBOOT    100M
`-mmcblk0p2  /          mmcrootfs  3.5G
mmcblk0boot0                         4M
mmcblk0boot1                         4M

root@debian:/# mount /dev/mmcblk0p1 /media/p1
root@debian:/# ls -al /media/p1
total 10194
drwxr-xr-x 2 root root   16384 Dec 31  1969 .
drwxr-xr-x 6 root root    4096 Feb  5 06:58 ..
-rwxr-xr-x 1 root root 5131373 Feb  4 20:52 uImage
-rwxr-xr-x 1 root root 5281910 Feb  4 22:42 uInitrd
-rwxr-xr-x 1 root root     143 Feb  8 12:08 wloader.cfg
root@debian:/# cat /media/p1/wloader.cfg
<TX0D_START>
kernel=uImage
initrd=uInitrd
param="root=LABEL=mmcrootfs raid=noautodetect console=ttyS2,115200 init=/usr/bin/systemd"
<TX0D_END>
root@debian:/#

I named it mmcrootfs instead of rootfs just because I wanted to be able to easily distinguish between them when I had my flash drive still connected.



Edited 3 time(s). Last edit at 02/09/2024 02:33PM by ksuszka.

> @mmm If you want to boot from eMMC you need to include missing kernel modules into the initramfs image, So when you extract 6.5.7 kernel and before you use mkimage for uInitrd run something like:

Sadly, no luck "Cannot load OS from PAR1".

root@devian:/boot# sed -i -E 's/(CONFIG_MMC_BLOCK|CONFIG_USB_UAS|CONFIG_PXA_SSP|CONFIG_SPI_PXA2XX|CONFIG_I2C_PXA|CONFIG_UIO|CONFIG_UIO_PDRV_GENIRQ)=m/\1=y/' config-6.5.7-mvebu-tld-1
root@debian:/boot# cat config-6.5.7-mvebu-tld-1 | grep CONFIG_MMC_BLOCK
CONFIG_MMC_BLOCK=y
CONFIG_MMC_BLOCK_MINORS=8
root@debian:/boot# cat zImage-* dts/mmp3-dell-ariel.dtb > zImage.fdt
root@debian:/boot# mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -d zImage.fdt uImage
Image Name:   
Created:      Fri Feb  9 12:53:50 2024
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    5157901 Bytes = 5037.01 KiB = 4.92 MiB
Load Address: 00008000
Entry Point:  00008000
root@debian:/boot# mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -d initrd.img-* uInitrd
Image Name:   
Created:      Fri Feb  9 12:53:57 2024
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    5275147 Bytes = 5151.51 KiB = 5.03 MiB
Load Address: 03000000
Entry Point:  03000000
root@debian:/boot# cp uImage uInitrd /mnt/
root@debian:/boot# ls -lah /mnt
total 53M
drwxr-xr-x  3 root root  16K Dec 31  1969 .
drwxrwxrwx 18 root root 4.0K Feb  9 11:47 ..
-rwxr-xr-x  1 root root 217K Feb  9 12:48 config-6.5.7-mvebu-tld-1
drwxr-xr-x  2 root root  10K Sep 28 15:52 dts
-rwxr-xr-x  1 root root  97K Oct 20 16:28 linux-6.5.7-mvebu-tld-1.patch
-rwxr-xr-x  1 root root 1.3M Oct 18 20:09 linux-dtb-6.5.7-mvebu-tld-1.tar
-rwxr-xr-x  1 root root 8.2M Oct 18 19:38 linux-headers-6.5.7-mvebu-tld-1_1_armhf.deb
-rwxr-xr-x  1 root root  23M Oct 18 19:37 linux-image-6.5.7-mvebu-tld-1_1_armhf.deb
-rwxr-xr-x  1 root root 5.0M Feb  9 12:54 uImage
-rwxr-xr-x  1 root root 5.1M Feb  9 12:54 uInitrd
-rwxr-xr-x  1 root root  155 Feb  9 12:38 wloader.cfg
-rwxr-xr-x  1 root root 5.0M Oct 18 19:16 zImage-6.5.7-mvebu-tld-1
-rwxr-xr-x  1 root root 5.0M Feb  9 12:38 zImage.fdt
root@debian:/boot# umount /mnt
root@debian:/boot# fdisk -l /dev/mmcblk0
mmcblk0       mmcblk0boot0  mmcblk0boot1  mmcblk0p1     mmcblk0p2     mmcblk0rpmb   
root@debian:/boot# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 3.64 GiB, 3909091328 bytes, 7634944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x893565bc

Device         Boot  Start     End Sectors  Size Id Type
/dev/mmcblk0p1 *      2048  133119  131072   64M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      133120 7634943 7501824  3.6G 83 Linux
root@debian:/boot# sfdisk --disk-id /dev/mmcblk0 0x0
Disk identifier changed from 0x893565bc to 0x00000000.

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
root@debian:/boot# fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 3.64 GiB, 3909091328 bytes, 7634944 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device         Boot  Start     End Sectors  Size Id Type
/dev/mmcblk0p1 *      2048  133119  131072   64M  c W95 FAT32 (LBA)
/dev/mmcblk0p2      133120 7634943 7501824  3.6G 83 Linux

- mmm



Edited 1 time(s). Last edit at 02/09/2024 03:11PM by mmm.

AFAIK par1 is the name of partition in ThinOS "Merlin" version. You can see it mentioned here: https://forum.doozan.com/read.php?2,63499,133037#msg-133037, but you can also download ThisOS for Wyse 3020 full version image from dell website and if you unpack it you will see par1.img file alongside bootLoader.img and cmos.img. But what I think it means in this context is that there is still some residue of previous setup on your machine. As you removed everything from eMMC it probably means that there is still something in WLoader settings which causes this issue.

A question - what is your boot order? How do you boot? Do you force booting from eMMC or do you rely on the boot order? Also did you perform factory reset before starting to change WLoader?

I would try to reset WLoader to factory settings first, perform complete power off and reboot cycle, enter WLoader and change image name to uImage, perform power off and reboot cycle, enter WLoader again to make sure that boot mode is switched to Linux, force boot from eMMC.

If it doesn't work then you can post here screenshots from your WLoader settings and boot order page and we will compare it to mine. You can see mine WLoader settings page attached to one of the previous posts. On my boot order page Hard Disk is on the top.

Quote
ksuszka
> - I copied uImage/uInitrd/wloader.cfg into FAT
> partition and tried to boot from it manually
> through wLoader, however in this moment I noticed
> that it is not possible as uInitrd file doesn't
> have required mmc drivers (this is the reason I
> didn't see mmc after the first boot)
> - So I run system from the flash drive again, use
> lsmod command to see which modules where loaded
> from rootfs and make those modules mandatory in
> config-6.4.11-mvebu-tld-1 file. Next, I run
> update-initramfs and mkimage commands to recreate
> uInitrd with all required drivers.

We should avoid doing the config hack. The Debian way to make these modules available at boot time is:

1. modify /etc/initramfs-tools/modules to include the list of needed modules
2. regenerate initramfs

update-initramfs -u

3. Recreate /boot/uInitrd

cd /boot
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs 6.6.2-mvebu-tld-1 -d initrd.img-6.6.2-mvebu-tld-1 uInitrd

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

Quote
ksuszka
> I would try to reset WLoader to factory settings
> first, perform complete power off and reboot
> cycle, enter WLoader and change image name to
> uImage, perform power off and reboot cycle, enter
> WLoader again to make sure that boot mode is
> switched to Linux, force boot from eMMC.
>
> If it doesn't work then you can post here
> screenshots from your WLoader settings and boot
> order page and we will compare it to mine. You can
> see mine WLoader settings page attached to one of
> the previous posts. On my boot order page Hard
> Disk is on the top.

Just did a full factory reset, but still no luck. I get the same error when I let it boot automatically from eMMC, and "Empty URL try next device..." when forcing boot from "Harddisk" in the boot menu. I attached screenshots, from the bootloader, but they seem pretty much identical. Are you on 6.5.7 or on 6.4.1?

Edit: I think I should also mention that I don't have any serial output when trying to boot from eMMC, so I'm not sure if this is caused by a lack of modules in the Initrd, i think wloader is doing something weird.

Quote
bodhi
> 1. modify /etc/initramfs-tools/modules to include the list of needed modules
> 2. regenerate initramfs
> update-initramfs -u
> 3. Recreate /boot/uInitrd
> cd /boot
> mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs 6.6.2-mvebu-tld-1 -d initrd.img-6.6.2-mvebu-tld-1 uInitrd

Thank you, now using this instead:

lsmod | awk '{print $1}' | tail -n +2 > /etc/initramfs-tools/modules
update-initramfs -u

I'm not using the 6.6.2 kernel however, due to the kernel panic. Should I set the addresses in the ramdisk to 0x00000000 when using 6.5.7 as well, or should 0x3000000 be used?

- mmm



Edited 1 time(s). Last edit at 02/09/2024 05:32PM by mmm.

mmm,

> I'm not using the 6.6.2 kernel however, due to the
> kernel panic. Should I set the addresses in the
> ramdisk to 0x00000000 when using 6.5.7 as well, or
> should 0x3000000 be used?

Ah OK. Normally, initramfs load address should be 0x00000000. But I see in previous posts

mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -d /mnt/rootfs/boot/initrd.img-* /mnt/bootfs/uInitrd

So yes, use 0x3000000:

mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -n initramfs 6.5.7-mvebu-tld-1 -d initrd.img-6.57-mvebu-tld-1 uInitrd

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

I'm still on 6.4.11 on eMMC. I tried 6.5.7 on the flash drive and it booted ok, but I didn't yet bother to upgrade eMMC. However it shouldn't matter as I understand that in your case it doesn't even start to boot from the kernel image. I assume that you have serial console connected as you were able to capture the kernel panic message so if you try to boot from eMMC do you see any activity from the kernel?

The boot order looks good to me, I've got HardDisk and next the USB but it shouldn't matter if USB is not inserted. However I've noticed a difference on the settings page. In my case the checkbox to override configuration file is grayed out, even after factory reset so it probably means that there is still some variation in our firmware versions or settings which is not affected by the factory reset.

Also, on a side note, I've noticed that in my case the Kernel Parameter doesn't really matter as params from wloader.cfg take precedence over it, so basically when I boot from eMMC on the attached monitor I can see the beginning of the param line from wloader.cfg on the eMMC and when I boot from USB I can see the beginning of the param line from wloader.cfg on the flash drive.

@bohdi, on another side note, I'm completely new to the /dev/mtd* stuff in the linux, but I've noticed that running commands like:

cat /dev/mtdblock0 > mtdblock0_cat.bin
cat /dev/mtd0 > mtd0_cat.bin
cat /dev/mtd0ro > mtd0ro_cat.bin

only seems to work. The content of captured files is basically garbage, it is a repeated block of the same fragment of the flash. For mtdblock0 it is 1KB block repated till 4MB. For mtd0 it is 256KB block repeated till 4MB. I'm not sure if this should work that way or is this even a sensible way to verify if it works.