Debian on Dell Wyse 3020
Posted by Mischif
|
Re: Debian on Dell Wyse 3020 February 25, 2024 01:38PM |
Admin Registered: 13 years ago Posts: 18,575 |
@ksuszka,
Thanks. So let me upload a new DTB later to see if we can get around this problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thanks. So let me upload a new DTB later to see if we can get around this problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 February 25, 2024 04:09PM |
Admin Registered: 13 years ago Posts: 18,575 |
bodhi Wrote:
-------------------------------------------------------
> @ksuszka,
>
> Thanks. So let me upload a new DTB later to see if
> we can get around this problem.
UPDATE1: looks like I need to investigate further. My initial thought about tweaking the DTS is probably not good.
UPDATE2: looks like I need to build a new kernel to test this kernel panic issue.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 02/25/2024 07:11PM by bodhi.
-------------------------------------------------------
> @ksuszka,
>
> Thanks. So let me upload a new DTB later to see if
> we can get around this problem.
UPDATE1: looks like I need to investigate further. My initial thought about tweaking the DTS is probably not good.
UPDATE2: looks like I need to build a new kernel to test this kernel panic issue.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 3 time(s). Last edit at 02/25/2024 07:11PM by bodhi.
|
Re: Debian on Dell Wyse 3020 February 26, 2024 09:33PM |
Admin Registered: 13 years ago Posts: 18,575 |
All,
Please try this kernel. See if it helps with the kernel panic.
linux-6.7.5-mvebu-tld-2-bodhi.tar.bz2
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Please try this kernel. See if it helps with the kernel panic.
linux-6.7.5-mvebu-tld-2-bodhi.tar.bz2
md5: 8a84e9d35625d3fc5ddd07b52ab271f2 sha256: cb96edad9c0b47ed13bef090d661d2c81fb7650f40269068ad3d461fa72d3a26This tarball contains 5 files
linux-image-6.7.5-mvebu-tld-2_2_armhf.deb linux-headers-6.7.5-mvebu-tld-2_2_armhf.deb zImage-6.7.5-mvebu-tld-2 config-6.7.5-mvebu-tld-2 linux-dtb-6.7.5-mvebu-tld-2.tar
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 February 27, 2024 02:14AM |
Registered: 2 months ago Posts: 34 |
Unfortunatelly, there is still a kernel panic:
For clarification what I did:
- after previous test I restored uImage/uInitrd for kernel 6.5.7 to have a working system
- I downloaded the new kernel archive to the machine and extracted files
- I extracted linux-dtb-6.7.5-mvebu-tld-2.tar file to a temporary folder and compared dts/mmp3-dell-ariel.dtb file to the one I have in my dts folder from kernel 6.5.7 and there was no change
- I installed both deb files from the archive in the system
- I run following commands to recreate boot images
*** FlashNumber... Code: : *** Loading Next Image... *** Loading Next Image... *** Set Partition for Image... *** Validate Image... *** GPIO_14, GPIO_13 both low ... Controller1 DDR size reg is 0xE ... *** Your OBM Boot Test Successes ... *** Shutting ports and transferring control ... 123ABC 12345 [ 0.000000][ T0] Booting Linux on physical CPU 0x0 [ 0.000000][ T0] Linux version 6.7.5-mvebu-tld-2 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #2 SMP PREEMPT Sun Feb 25 19:19:00 PST 2024 [ 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: rootdelay=5 root=LABEL=mmcrootfs raid=noautodetect console=ttyS2,115200 mtdparts=spi0.0:4m(boot) [ 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: 2052660K/2096128K available (10240K kernel code, 873K rwdata, 3536K rodata, 1024K init, 318K bss, 43468K 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.000006][ T0] sched_clock: 32 bits at 26MHz, resolution 38ns, wraps every 82595524588ns [ 0.000068][ T0] clocksource: clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 73510017198 ns [ 0.000283][ T0] smp_twd: clock not found -2 [ 0.000792][ T0] kfence: initialized - using 2097152 bytes for 255 objects at 0x(ptrval)-0x(ptrval) [ 0.001281][ T0] Console: colour dummy device 80x30 [ 0.001329][ T0] Calibrating local timer... 2.16MHz. [ 0.060263][ T0] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 0.100287][ T0] CPU: Testing write buffer coherency: ok [ 0.100363][ T0] pid_max: default: 32768 minimum: 301 [ 0.104625][ T0] LSM: initializing lsm=capability,integrity [ 0.106018][ T0] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.106038][ T0] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.112022][ T1] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.114178][ T1] RCU Tasks: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1. [ 0.114441][ T1] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1. [ 0.114646][ T1] Setting up static identity map for 0x100000 - 0x100060 [ 0.115257][ T1] rcu: Hierarchical SRCU implementation. [ 0.115267][ T1] rcu: Max phase no-delay instances is 1000. [ 0.116720][ T1] smp: Bringing up secondary CPUs ... [ 0.150293][ T0] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.151059][ T1] smp: Brought up 1 node, 2 CPUs [ 0.151080][ T1] SMP: Total of 2 processors activated (2382.23 BogoMIPS). [ 0.151091][ T1] CPU: All CPU(s) started in SVC mode. [ 0.153445][ T1] devtmpfs: initialized [ 0.164919][ T1] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 [ 0.165513][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.165555][ T1] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.168551][ T1] prandom: seed boundary self test passed [ 0.171127][ T1] prandom: 100 self tests passed [ 0.171141][ T1] pinctrl core: initialized pinctrl subsystem [ 0.173422][ T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.174114][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.185125][ T1] audit: initializing netlink subsys (disabled) [ 0.186535][ T1] thermal_sys: Registered thermal governor 'step_wise' [ 0.186640][ T30] audit: type=2000 audit(0.190:1): state=initialized audit_enabled=0 res=1 [ 0.186716][ T1] cpuidle: using governor ladder [ 0.186769][ T1] cpuidle: using governor menu [ 0.187004][ T19] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0 [ 0.187019][ T19] hw-breakpoint: CPU 0 failed to disable vector catch [ 0.187081][ T20] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 1 [ 0.190857][ T1] platform soc: Fixed dependency cycle(s) with /soc/interrupt-controller@e0001000 [ 0.370512][ T1] raid6: int32x8 gen() 222 MB/s [ 0.540607][ T1] raid6: int32x4 gen() 236 MB/s [ 0.710719][ T1] raid6: int32x2 gen() 362 MB/s [ 0.880841][ T1] raid6: int32x1 gen() 357 MB/s [ 0.880855][ T1] raid6: using algorithm int32x2 gen() 362 MB/s [ 1.050942][ T1] raid6: .... xor() 219 MB/s, rmw enabled [ 1.050952][ T1] raid6: using intx1 recovery algorithm [ 1.053066][ T1] SCSI subsystem initialized [ 1.053744][ T1] usbcore: registered new interface driver usbfs [ 1.053841][ T1] usbcore: registered new interface driver hub [ 1.053936][ T1] usbcore: registered new device driver usb [ 1.054407][ T1] pps_core: LinuxPPS API ver. 1 registered [ 1.054418][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 1.054449][ T1] PTP clock support registered [ 1.057410][ T1] vgaarb: loaded [ 1.058328][ T1] clocksource: Switched to clocksource clocksource [ 1.070367][ T1] VFS: Disk quotas dquot_6.6.0 [ 1.070930][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.096084][ T1] NET: Registered PF_INET protocol family [ 1.096513][ T1] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 1.098867][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) [ 1.099163][ T1] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 1.099243][ T1] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 1.099370][ T1] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 1.099510][ T1] TCP: Hash tables configured (established 8192 bind 8192) [ 1.100400][ T1] MPTCP token hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 1.100963][ T1] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 1.101005][ T1] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 1.102078][ T1] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 1.103584][ T1] RPC: Registered named UNIX socket transport module. [ 1.103599][ T1] RPC: Registered udp transport module. [ 1.103608][ T1] RPC: Registered tcp transport module. [ 1.103616][ T1] RPC: Registered tcp-with-tls transport module. [ 1.103624][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.103653][ T1] PCI: CLS 0 bytes, default 64 [ 1.109147][ T29] Trying to unpack rootfs image as initramfs... [ 1.109553][ T1] Initialise system trusted keyrings [ 1.109687][ T1] Key type blacklist registered [ 1.110285][ T1] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 1.110392][ T1] zbud: loaded [ 1.134638][ T1] NFS: Registering the id_resolver key type [ 1.134711][ T1] Key type id_resolver registered [ 1.134720][ T1] Key type id_legacy registered [ 1.135093][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 1.135126][ T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 1.292593][ T1] xor: measuring software checksum speed [ 1.300917][ T1] arm4regs : 1197 MB/sec [ 1.312491][ T1] 8regs : 855 MB/sec [ 1.321667][ T1] 32regs : 1081 MB/sec [ 1.321685][ T1] xor: using function: arm4regs (1197 MB/sec) [ 1.321718][ T1] async_tx: api initialized (async) [ 1.321745][ T1] Key type asymmetric registered [ 1.321759][ T1] Asymmetric key parser 'x509' registered [ 1.322516][ T1] bounce: pool size: 64 pages [ 1.323697][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245) [ 1.324700][ T1] io scheduler bfq registered [ 1.350865][ T1] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 1.376783][ T29] Freeing initrd memory: 5172K [ 1.587360][ T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 1.597392][ T1] printk: legacy console [ttyS2] disabled [ 1.600094][ T1] d4018000.serial: ttyS2 at MMIO 0xd4018000 (irq = 381, base_baud = 1625000) is a XScale [ 1.600187][ T1] printk: legacy console [ttyS2] enabled [ 2.513473][ T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. [ 2.522331][ T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved. [ 2.543147][ T1] usbcore: registered new interface driver smsc75xx [ 2.553772][ T1] mv-ehci d4208000.usb: EHCI Host Controller [ 2.559742][ T1] mv-ehci d4208000.usb: new USB bus registered, assigned bus number 1 [ 2.569131][ T1] mv-ehci d4208000.usb: irq 382, io mem 0xd4208000 [ 2.608404][ T1] mv-ehci d4208000.usb: USB 2.0 started, EHCI 1.00 [ 2.615147][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.07 [ 2.624110][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.632025][ T1] usb usb1: Product: EHCI Host Controller [ 2.637558][ T1] usb usb1: Manufacturer: Linux 6.7.5-mvebu-tld-2 ehci_hcd [ 2.644602][ T1] usb usb1: SerialNumber: d4208000.usb [ 2.651643][ T1] hub 1-0:1.0: USB hub found [ 2.656136][ T1] hub 1-0:1.0: 1 port detected [ 2.661989][ T1] mv-ehci d4208000.usb: successful find EHCI device with regs 0x(ptrval) irq 382 working in Host mode [ 2.673573][ T1] usbcore: registered new interface driver usblp [ 2.680084][ T1] usbcore: registered new interface driver usb-storage [ 2.687948][ T1] mousedev: PS/2 mouse device common for all mice [ 2.696536][ T1] i2c_dev: i2c /dev entries driver [ 2.704675][ T1] device-mapper: uevent: version 1.0.3 [ 2.710927][ T1] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com [ 2.720822][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded [ 2.728007][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded [ 2.735341][ T1] device-mapper: multipath service-time: version 0.3.0 loaded [ 2.742886][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded [ 2.750180][ T1] sdhci: Secure Digital Host Controller Interface driver [ 2.757009][ T1] sdhci: Copyright(c) Pierre Ossman [ 2.763642][ T1] sdhci-pltfm: SDHCI platform and OF driver helper [ 2.771422][ T1] hid: raw HID events driver (C) Jiri Kosina [ 2.780373][ T1] usbcore: registered new interface driver usbhid [ 2.786682][ T1] usbhid: USB HID core driver [ 2.794447][ T1] NET: Registered PF_INET6 protocol family [ 2.803710][ T1] Segment Routing with IPv6 [ 2.808049][ T1] RPL Segment Routing with IPv6 [ 2.812838][ T25] mmc0: SDHCI controller on d4281000.mmc [d4281000.mmc] using ADMA [ 2.820736][ T1] In-situ OAM (IOAM) with IPv6 [ 2.825536][ T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 2.836009][ T1] NET: Registered PF_PACKET protocol family [ 2.842369][ T1] 8021q: 802.1Q VLAN Support v1.8 [ 2.847396][ T1] Key type dns_resolver registered [ 2.853006][ T1] ThumbEE CPU extension supported. [ 2.858444][ T1] Registering SWP/SWPB emulation handler [ 2.864110][ T1] PJ4 iWMMXt v2 coprocessor enabled. [ 2.949699][ T68] usb 1-1: new high-speed USB device number 2 using mv-ehci [ 2.965777][ T1] registered taskstats version 1 [ 2.971378][ T1] Loading compiled-in X.509 certificates [ 3.011717][ T1] Key type .fscrypt registered [ 3.016326][ T1] Key type fscrypt-provisioning registered [ 3.022288][ T1] Key type big_key registered [ 3.047840][ T1] Key type encrypted registered [ 3.073207][ T26] mv-ehci f0001000.usb: EHCI Host Controller [ 3.080144][ T26] mv-ehci f0001000.usb: new USB bus registered, assigned bus number 2 [ 3.088803][ T26] mv-ehci f0001000.usb: irq 384, io mem 0xf0001000 [ 3.137490][ T8] mmc0: new HS200 MMC card at address 0001 [ 3.144788][ T8] mmcblk0: mmc0:0001 H4G2a 3.64 GiB [ 3.153560][ T8] mmcblk0: p1 p2 [ 3.158435][ T26] mv-ehci f0001000.usb: USB 2.0 started, EHCI 1.00 [ 3.158524][ T8] mmcblk0boot0: mmc0:0001 H4G2a 4.00 MiB [ 3.165549][ T26] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.07 [ 3.173067][ T68] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=77.63 [ 3.179439][ T26] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.189961][ T8] mmcblk0boot1: mmc0:0001 H4G2a 4.00 MiB [ 3.196152][ T26] usb usb2: Product: EHCI Host Controller [ 3.201915][ T68] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3.208036][ T26] usb usb2: Manufacturer: Linux 6.7.5-mvebu-tld-2 ehci_hcd [ 3.215396][ T68] usb 1-1: Product: USB2.0 Hub [ 3.222276][ T26] usb usb2: SerialNumber: f0001000.usb [ 3.232357][ T8] mmcblk0rpmb: mmc0:0001 H4G2a 4.00 MiB, chardev (244:0) [ 3.234617][ T26] hub 2-0:1.0: USB hub found [ 3.240450][ T68] hub 1-1:1.0: USB hub found [ 3.245206][ T26] hub 2-0:1.0: 1 port detected [ 3.248708][ T68] hub 1-1:1.0: 4 ports detected [ 3.255794][ T26] mv-ehci f0001000.usb: successful find EHCI device with regs 0x(ptrval) irq 384 working in Host mode [ 3.270812][ T1] clk: Disabling unused clocks [ 3.279041][ T1] Freeing unused kernel image (initmem) memory: 1024K [ 3.330505][ T1] Checked W+X mappings: passed, no W+X pages found [ 3.336912][ T1] Run /init as init process [ 3.343289][ T1] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 [ 3.351596][ T1] CPU: 0 PID: 1 Comm: init Not tainted 6.7.5-mvebu-tld-2 #2 [ 3.358681][ T1] Hardware name: Marvell MMP3 [ 3.363184][ T1] unwind_backtrace from show_stack+0x10/0x14 [ 3.369090][ T1] show_stack from dump_stack_lvl+0x40/0x4c [ 3.374811][ T1] dump_stack_lvl from panic+0x104/0x308 [ 3.380265][ T1] panic from do_exit+0x264/0x8b8 [ 3.385123][ T1] do_exit from sys_exit_group+0x0/0x10 [ 3.390509][ C1] CPU1: stopping [ 3.390519][ C1] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.7.5-mvebu-tld-2 #2 [ 3.390530][ C1] Hardware name: Marvell MMP3 [ 3.390538][ C1] unwind_backtrace from show_stack+0x10/0x14 [ 3.390562][ C1] show_stack from dump_stack_lvl+0x40/0x4c [ 3.390578][ C1] dump_stack_lvl from do_handle_IPI+0x84/0x11c [ 3.390595][ C1] do_handle_IPI from ipi_handler+0x14/0x20 [ 3.390612][ C1] ipi_handler from handle_percpu_devid_irq+0x4c/0xe8 [ 3.390641][ C1] handle_percpu_devid_irq from handle_irq_desc+0x1c/0x2c [ 3.390660][ C1] handle_irq_desc from gic_handle_irq+0x58/0x64 [ 3.390678][ C1] gic_handle_irq from generic_handle_arch_irq+0x28/0x3c [ 3.390694][ C1] generic_handle_arch_irq from call_with_stack+0x18/0x20 [ 3.390716][ C1] call_with_stack from __irq_svc+0x98/0xc8 [ 3.390731][ C1] Exception stack(0xf0859f60 to 0xf0859fa8) [ 3.390747][ C1] 9f60: 00000001 c0ded327 00002794 00000001 00000000 00000000 00000001 c194ba80 [ 3.390759][ C1] 9f80: c100a010 c100a04c 00000000 00000000 00000000 f0859fb0 c0a9d158 c0156e38 [ 3.390768][ C1] 9fa0: 200c0013 ffffffff [ 3.390775][ C1] __irq_svc from do_idle+0x108/0x280 [ 3.390795][ C1] do_idle from cpu_startup_entry+0x28/0x2c [ 3.390812][ C1] cpu_startup_entry from secondary_start_kernel+0xfc/0x11c [ 3.390830][ C1] secondary_start_kernel from 0x1016a0 [ 3.519132][ T1] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---
For clarification what I did:
- after previous test I restored uImage/uInitrd for kernel 6.5.7 to have a working system
- I downloaded the new kernel archive to the machine and extracted files
- I extracted linux-dtb-6.7.5-mvebu-tld-2.tar file to a temporary folder and compared dts/mmp3-dell-ariel.dtb file to the one I have in my dts folder from kernel 6.5.7 and there was no change
- I installed both deb files from the archive in the system
- I run following commands to recreate boot images
KERNEL_VERSION=6.7.5-mvebu-tld-2
cat zImage-${KERNEL_VERSION} dts/mmp3-dell-ariel.dtb > zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x8000 -e 0x8000 -n Linux-${KERNEL_VERSION} -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x3000000 -e 0x3000000 -d initrd.img-${KERNEL_VERSION} uInitrd
- I copied created uImage/uInitrd files to the boot partition and rebooted the system
|
Re: Debian on Dell Wyse 3020 February 27, 2024 01:44PM |
Admin Registered: 13 years ago Posts: 18,575 |
|
Re: Debian on Dell Wyse 3020 March 03, 2024 04:25PM |
Admin Registered: 13 years ago Posts: 18,575 |
I can see this problem a bit better now. This might be the issue with cpuidle is broken for this SoC during early booting.
But unfortunately we don't have coherency fabric defined in the MMP3 DTS (so we can mark cpuidle as broken).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
But unfortunately we don't have coherency fabric defined in the MMP3 DTS (so we can mark cpuidle as broken).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 April 01, 2024 05:21AM |
Registered: 26 days ago Posts: 4 |
Hello
I also want to install Debian on this thing but it is hard for me to read through all these things and understand everything. I created the Debian stick with the rootfs and the bootfs partition successfully but I don’t no how to install the uboot loader or what I have to do with the wloader or how to install it.
I also want to install Debian on this thing but it is hard for me to read through all these things and understand everything. I created the Debian stick with the rootfs and the bootfs partition successfully but I don’t no how to install the uboot loader or what I have to do with the wloader or how to install it.
|
Re: Debian on Dell Wyse 3020 April 01, 2024 02:15PM |
Admin Registered: 13 years ago Posts: 18,575 |
maxt1907,
We don't have the installation instruction written for this box yet.
But basically you'd start from Mischif's post here:
https://forum.doozan.com/read.php?2,134563,134729#msg-134729
And later we refined the wloader.cfg:
As ksuszka and mmm found during testing later, the last kernel that boots without panic problem is 6.5.7-mvebu-tld-1.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
We don't have the installation instruction written for this box yet.
But basically you'd start from Mischif's post here:
https://forum.doozan.com/read.php?2,134563,134729#msg-134729
Quote
I create a FAT32 partition mounted at /mnt/bootfs to hold the kernel/initrd/wloader.conf, then I create an ext3 filesystem mounted at /mnt/rootfs to hold the rootfs. From there I just extract everything as necessary and delete unused files:
tar -C /mnt/rootfs/ -x -j -f ~/Downloads/Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2
tar -C /mnt/BOOTFS/ -x -j -f ~/Downloads/linux-6.2.8-mvebu-tld-2.x-bodhi.tar.bz2
cat /mnt/BOOTFS/zImage-6.2.8-mvebu-tld-2.0 /mnt/BOOTFS/dts/mmp3-dell-ariel.dtb > /mnt/BOOTFS/zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -d /mnt/BOOTFS/zImage.fdt /mnt/BOOTFS/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -d /mnt/rootfs/boot/initrd.img-5.13.8-mvebu-tld-1 /mnt/BOOTFS/uInitrd
wloader.conf looks like this:
<TX0D_START>
kernel=uImage
initrd=uInitrd
param="rootdelay=5 root=/dev/sda2 console=ttyS2,115200 raid=noautodetect"
<TX0D_END>
/mnt/bootfs looks like this:
drwxr-xr-x 2 mischif mischif 1536 Dec 31 1969 .
-rw-r--r-- 1 mischif mischif 4973597 Apr 9 21:24 uImage
-rw-r--r-- 1 mischif mischif 9649885 Apr 9 21:26 uInitrd
-rw-r--r-- 1 mischif mischif 136 Apr 9 21:28 wloader.cfg
drwxr-x---+ 4 root root 34 Apr 9 21:45 ..
And later we refined the wloader.cfg:
Quote
Modify the wloader.cfg
<TX0D_START> kernel=uImage initrd=uInitrd param="rootdelay=5 root=LABEL=rootfs raid=noautodetect console=ttyS2,115200 mtdparts=spi1.0:4m(boot)" <TX0D_END>
As ksuszka and mmm found during testing later, the last kernel that boots without panic problem is 6.5.7-mvebu-tld-1.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Max
Re: Debian on Dell Wyse 3020 April 03, 2024 05:21AM |
I created the Install USB stick with your guide and the provided information. Do I need to create the wloader.cfg just as an file or is it created while an installing process of this wloader?
My BOOTFS volume looks like this:
My rootfs volume looks like this:
My BOOTFS volume looks like this:
max@max-OptiPlex-3020:~/Downloads$ ls /media/max/BOOTFS/ config-6.5.7-mvebu-tld-1 dts linux-6.5.7-mvebu-tld-1.patch linux-dtb-6.5.7-mvebu-tld-1.tar linux-headers-6.5.7-mvebu-tld-1_1_armhf.deb linux-image-6.5.7-mvebu-tld-1_1_armhf.deb uImage uInitrd zImage-6.5.7-mvebu-tld-1 zImage.fdt
My rootfs volume looks like this:
max@max-OptiPlex-3020:~/Downloads$ ls /media/max/rootfs/ bin dev home lost+found mnt proc run srv tmp var boot etc lib media opt root sbin sys usr
|
Re: Debian on Dell Wyse 3020 April 03, 2024 09:35AM |
Registered: 2 months ago Posts: 34 |
wLoader is the bootloader installed on this terminal. Here is some basic info about wLoader: https://linux-mmp.docs.kernel.org/dell-wyse-3020.html. Keep in mind that it is rather old article so you should use it just as a guideline and use commands/files content from bodhi's post instead.
|
Max
Re: Debian on Dell Wyse 3020 April 03, 2024 11:49AM |
I booted the USB stick but I get an black screen after the bootloader screen and selecting the usb stick. The LEDs of the ethernet connection lights up after some seconds but the screen stays black. I connected an working monitor directly via DVI cable (no adapters or anything else).
Is an serial connection needed for setting this up? ssh doesn't worked. But it looks like it is online. Sorry for my bad english.
Thank you for your help.
Is an serial connection needed for setting this up? ssh doesn't worked. But it looks like it is online. Sorry for my bad english.
Thank you for your help.
|
Re: Debian on Dell Wyse 3020 April 03, 2024 01:48PM |
Registered: 2 months ago Posts: 34 |
Unfortunately, the current version of the debian kernel from this site does not support video output at all. So don't expect working video output even if you manage to boot linux sucessfully. As far as I know there is no working DTS file which supports video output available publicly.
So the first thing to do after boot is to check if your router (or whatever dhcp server you are running) assigns an IP address to your device. If it is not the case then probably you missed some configuration steps.
Check following links for more info:
- The original post by Mischif
- The revised post with some additional required configuration steps
- An attempt of automated installation script by mmm which can be used as a reference
But the best bet is to set up a serial connection to see what is the issue directly on the machine. Here are some directions: https://forum.doozan.com/read.php?2,134563,136696#msg-136696
So the first thing to do after boot is to check if your router (or whatever dhcp server you are running) assigns an IP address to your device. If it is not the case then probably you missed some configuration steps.
Check following links for more info:
- The original post by Mischif
- The revised post with some additional required configuration steps
- An attempt of automated installation script by mmm which can be used as a reference
But the best bet is to set up a serial connection to see what is the issue directly on the machine. Here are some directions: https://forum.doozan.com/read.php?2,134563,136696#msg-136696
|
Re: Debian on Dell Wyse 3020 April 03, 2024 02:04PM |
Admin Registered: 13 years ago Posts: 18,575 |
> An
> attempt of automated installation script by mmm
> which can be used as a reference
My bad. I forgot mmm has written this. Yes, that script should be used as a reference.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> attempt of automated installation script by mmm
> which can be used as a reference
My bad. I forgot mmm has written this. Yes, that script should be used as a reference.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Max
Re: Debian on Dell Wyse 3020 April 04, 2024 10:43AM |
Thank you very much for your help. I booted it now and it works fine.
I now want to install it to the local hard drive of the device but in parted and lsblk the local hard drive (4GB) is not detected.
Is there anything I can do? I also want to get an 802.11n 8188 usb stick to work.
The usb stick is detected as the following: "Realtek Semiconductor Corp. RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter"
Can I install non-free firmware or anything to get this stick to work?
The main problem is the local storage not detected. In lsblk only usb stick shows up. Thank you for your help again.
I now want to install it to the local hard drive of the device but in parted and lsblk the local hard drive (4GB) is not detected.
Is there anything I can do? I also want to get an 802.11n 8188 usb stick to work.
The usb stick is detected as the following: "Realtek Semiconductor Corp. RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter"
Can I install non-free firmware or anything to get this stick to work?
The main problem is the local storage not detected. In lsblk only usb stick shows up. Thank you for your help again.
|
Re: Debian on Dell Wyse 3020 April 04, 2024 02:11PM |
Admin Registered: 13 years ago Posts: 18,575 |
@Max,
Boot with USB, log in and do
See if it is now initiliazed.
If it's OK, add the mmc_block module to initramfs:
https://forum.doozan.com/read.php?2,134563,136672#msg-136672
Note that since you are running 6.5.7, the mkimage command should be:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 04/04/2024 02:35PM by bodhi.
Boot with USB, log in and do
modprobe mmc_block
See if it is now initiliazed.
If it's OK, add the mmc_block module to initramfs:
https://forum.doozan.com/read.php?2,134563,136672#msg-136672
Note that since you are running 6.5.7, the mkimage command should be:
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-6.5.7-mvebu-tld-1 -d initrd.img-6.5.7-mvebu-tld-1 uInitrd
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 04/04/2024 02:35PM by bodhi.
|
Re: Debian on Dell Wyse 3020 April 05, 2024 06:40AM |
Registered: 26 days ago Posts: 4 |
@bodhi
This is the result when typing the command in the command line:
Is this happening because I used the wrong command for mkimage I used the updated automated script which is one or two posts under the one you linked at ?It uses another mkimage commands
How do I add the mmc_block to the initramfs?
Thank you for your time and help.
Edited 1 time(s). Last edit at 04/05/2024 06:41AM by maxt1907.
This is the result when typing the command in the command line:
root@debian:~# modprobe mmc_block modprobe: FATAL: Module mmc_block not found in directory /lib/modules/6.5.7-mvebu-tld-1
Is this happening because I used the wrong command for mkimage I used the updated automated script which is one or two posts under the one you linked at ?It uses another mkimage commands
How do I add the mmc_block to the initramfs?
Thank you for your time and help.
Edited 1 time(s). Last edit at 04/05/2024 06:41AM by maxt1907.
|
Re: Debian on Dell Wyse 3020 April 05, 2024 02:09PM |
Admin Registered: 13 years ago Posts: 18,575 |
Max,
> Is this happening because I used the wrong command
> for mkimage I used the updated automated script
> which is one or two posts under the one you linked
> at ?It uses another mkimage commands
>
Yes, I forgot that the load address 0x3000000 correct for this box.
So you did use the right command.
Perhaps something went wrong during your installation. Check if the module is in the rootfs:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Is this happening because I used the wrong command
> for mkimage I used the updated automated script
> which is one or two posts under the one you linked
> at ?It uses another mkimage commands
>
Yes, I forgot that the load address 0x3000000 correct for this box.
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
So you did use the right command.
Perhaps something went wrong during your installation. Check if the module is in the rootfs:
uname -a ls -lart /boot find /lib/modules/6.5.7-mvebu-tld-1/ -name '*mmc*'
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Max
Re: Debian on Dell Wyse 3020 April 06, 2024 04:13AM |
|
Re: Debian on Dell Wyse 3020 April 06, 2024 04:45AM |
Registered: 2 months ago Posts: 34 |
Max, we missed one important link with a vital piece of info - the post with generic instruction on how to install debian on those embedded machines. There is a section about installing custom version of kernel on top of existing rootfs. One step you probably missed is to install kernel deb package inside an os booted from usb stick. This is most likely the reason you don't have additional kernel modules.
You need to boot OS from the usb stick, ssh into it and run
For a long run you should probably also install your custom kernel headers.
After you do this, you should be able to access mmc from your usb booted OS. Next, If you think about booting from mmc, you need to add this driver to initrd, so you need to add it to /etc/initramfs-tools/modules, update initramfs, recreate initrd, put it into bootfs. Then you will have the boot partition with a kernel which is able to access mmc by itself and can be used as a kernel to boot from mmc directly.
Edited 3 time(s). Last edit at 04/06/2024 04:56AM by ksuszka.
You need to boot OS from the usb stick, ssh into it and run
dpkg -i linux-image-6.5.7-mvebu-tld-1_1_armhf.debcommand in a folder where you unpacked the 6.5.7 kernel. If you unpacked it into bootfs then you may to need to mount it first or even simpler - attach the usb stick back to you main computer and unpack kernel archive somewhere on your rootfs - I usually use the /boot folder on rootfs for it.
For a long run you should probably also install your custom kernel headers.
After you do this, you should be able to access mmc from your usb booted OS. Next, If you think about booting from mmc, you need to add this driver to initrd, so you need to add it to /etc/initramfs-tools/modules, update initramfs, recreate initrd, put it into bootfs. Then you will have the boot partition with a kernel which is able to access mmc by itself and can be used as a kernel to boot from mmc directly.
Edited 3 time(s). Last edit at 04/06/2024 04:56AM by ksuszka.
|
Re: Debian on Dell Wyse 3020 April 06, 2024 01:14PM |
Registered: 26 days ago Posts: 4 |
Ok this worked now I can see the Mmc device. How can I install the Linux on the local hard disk? I created an 100MB Fat32 boot partition and the rest as an ext3 Debian partition. So I extract the tar image to the rootfs image but what to do with the boot fs image? Just run the kernel-install.sh script for the bootfs? Do I need to extract the kernel tar file to the bootfs 100mb boot partition?
Is there a guide on how to create the partitioning?
Is there a guide on how to create the partitioning?
|
Re: Debian on Dell Wyse 3020 April 06, 2024 01:23PM |
Registered: 2 months ago Posts: 34 |
It is basically the same as with the usb stick. So you can copy everything from your bootable usb stick bootfs partition to the bootfs partition on the mmc, but first you need to make sure that mmc_block module is in initrd file on this boot partition because without it it will start booting and then it will fail as it won't be able to read the rest of the system from mmc.
Next you need to configure WLoader to boot from emmc which is a bit tricky. See this post and later discussions: https://forum.doozan.com/read.php?2,134563,136655#msg-136655
Here are some commands I used in the past: https://forum.doozan.com/read.php?2,134563,136687#msg-136687
Edited 1 time(s). Last edit at 04/06/2024 01:28PM by ksuszka.
Next you need to configure WLoader to boot from emmc which is a bit tricky. See this post and later discussions: https://forum.doozan.com/read.php?2,134563,136655#msg-136655
Here are some commands I used in the past: https://forum.doozan.com/read.php?2,134563,136687#msg-136687
Edited 1 time(s). Last edit at 04/06/2024 01:28PM by ksuszka.
|
Re: Debian on Dell Wyse 3020 April 07, 2024 06:52AM |
Registered: 26 days ago Posts: 4 |
|
Re: Debian on Dell Wyse 3020 April 07, 2024 07:26AM |
Registered: 2 months ago Posts: 34 |
|
Max
Re: Debian on Dell Wyse 3020 April 07, 2024 09:47AM |
|
Re: Debian on Dell Wyse 3020 April 11, 2024 08:28AM |
Registered: 5 months ago Posts: 4 |
|
Re: Debian on Dell Wyse 3020 April 11, 2024 10:42AM |
Registered: 2 months ago Posts: 34 |
@Max, you can use fdisk, sfdisk, parted and probably a dozen other command line partition tools. You also need mkfs.ext3 and mkfs.vfat to make file system. Also e2label may be useful to change partition label (however you can do this also with parition tools).
You can use @mmm script mentioned before as a reference. It is doing partitioning using sfdisk.
You can use @mmm script mentioned before as a reference. It is doing partitioning using sfdisk.
|
Re: Debian on Dell Wyse 3020 April 15, 2024 10:23PM |
Registered: 13 days ago Posts: 6 |
Anyone know what I'm doing wrong?
[root@localhost home]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 15G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 14G 0 part ├─fedora-root 253:0 0 12.5G 0 lvm / └─fedora-swap 253:1 0 1.5G 0 lvm [SWAP] sdb 8:16 1 14.9G 0 disk sr0 11:0 1 1024M 0 rom [root@localhost home]# arm-image-installer --resizefs --target=olpc_xo175 --media=/dev/sdb --image=/ home/Fedora-Minimal-armhfp-32-1.6-sda.raw.xz ===================================================== = Selected Image: = /home/Fedora-Minimal-armhfp-32-1.6-sda.raw.xz = Selected Media : /dev/sdb = U-Boot Target : olpc_xo175 = Root partition will be resized ===================================================== ***************************************************** ***************************************************** ******** WARNING! ALL DATA WILL BE DESTROYED ******** ***************************************************** ***************************************************** Type 'YES' to proceed, anything else to exit now = Proceed? YES = Writing: = /home/Fedora-Minimal-armhfp-32-1.6-sda.raw.xz = To: /dev/sdb .... 196878336 bytes (197 MB, 188 MiB) copied, 1 s, 197 MB/s 291545088 bytes (292 MB, 278 MiB) copied, 2 s, 146 MB/s ... 2081914880 bytes (2.1 GB, 1.9 GiB) copied, 303 s, 6.9 MB/s 2087419904 bytes (2.1 GB, 1.9 GiB) copied, 304 s, 6.9 MB/s 0+157215 records in 0+157215 records out 2088763392 bytes (2.1 GB, 1.9 GiB) copied, 485.728 s, 4.3 MB/s = Writing image complete! = Resizing /dev/sdb .... Checking that no-one is using this disk right now ... OK [1mDisk /dev/sdb: 14.94 GiB, 16015949824 bytes, 31281152 sectors [0mDisk model: USB 2.0 FD 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: 0xbacf5465 Old situation: [1mDevice[0m [1mBoot[0m [1m Start[0m [1m End[0m [1mSectors[0m [1m Size[0m [1mId[0m [1mType[0m /dev/sdb1 8192 163839 155648 76M c W95 FAT32 (LBA) /dev/sdb2 * 163840 1163263 999424 488M 83 Linux /dev/sdb3 1163264 3899391 2736128 1.3G 83 Linux /dev/sdb3: New situation: Disklabel type: dos Disk identifier: 0xbacf5465 [1mDevice[0m [1mBoot[0m [1m Start[0m [1m End[0m [1m Sectors[0m [1m Size[0m [1mId[0m [1mType[0m /dev/sdb1 8192 163839 155648 76M c W95 FAT32 (LBA) /dev/sdb2 * 163840 1163263 999424 488M 83 Linux /dev/sdb3 1163264 31281151 30117888 14.4G 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. e2fsck 1.45.5 (07-Jan-2020) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information _/: 36555/85536 files (1.3% non-contiguous), 271034/342016 blocks resize2fs 1.45.5 (07-Jan-2020) Resizing the filesystem on /dev/sdb3 to 3764736 (4k) blocks. The filesystem on /dev/sdb3 is now 3764736 (4k) blocks long. = Copying loader scripts to boot partition = Installation Complete! Insert into the olpc_xo175 and boot. [root@localhost home]# mount /dev/sdb2 /mnt [root@localhost home]# mount /dev/sdb1 /mnt/efi/ [root@localhost home]# rm -rf /mnt/efi/* [root@localhost home]# cat /mnt/vmlinuz-* /mnt/dtb-*/mmp3-dell-ariel.dtb >/mnt/zImage [root@localhost home]# mkimage -A arm -O linux -C none -T kernel -a 0x00008000 -e 0x00008000 -d /mn t/zImage /mnt/efi/uImage Image Name: Created: Mon Apr 15 23:03:12 2024 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 7654917 Bytes = 7475.50 KiB = 7.30 MiB Load Address: 00008000 Entry Point: 00008000 [root@localhost home]# mkimage -A arm -O linux -C none -T ramdisk -d /mnt/initramfs-* /mnt/efi/uIni trd Image Name: Created: Mon Apr 15 23:03:26 2024 Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 51619027 Bytes = 50409.21 KiB = 49.23 MiB Load Address: 00000000 Entry Point: 00000000 [root@localhost home]# nano /mnt/efi/wloader.cfg <TX0D_START> kernel=./uImage initrd=./uInitrd param="$(sed -n 's/^[\t ]*append //p' /mnt/extlinux/extlinux.conf)" <TX0D_END> [root@localhost home]# umount /mnt/efi /mnt [root@localhost home]# umount /mnt/efi /mntexit Script done on 2024-04-15 23:06:38-04:00 [COMMAND_EXIT_CODE="0"]
|
Re: Debian on Dell Wyse 3020 April 16, 2024 12:32AM |
Admin Registered: 13 years ago Posts: 18,575 |
Looks like you are using a wrong tutorial.
This is what we are using here:
https://linux-mmp.docs.kernel.org/dell-wyse-3020.html
And in this thread, this is the post you should start from:
https://forum.doozan.com/read.php?2,137328,137330#msg-137330
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
This is what we are using here:
https://linux-mmp.docs.kernel.org/dell-wyse-3020.html
And in this thread, this is the post you should start from:
https://forum.doozan.com/read.php?2,137328,137330#msg-137330
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 April 17, 2024 01:41AM |
Registered: 13 days ago Posts: 6 |
Mischif Wrote:
-------------------------------------------------------
> bodhi,
>
> There are two sets of headers which look like UART
> ports on
> the
> motherboard; I've tried connecting to both
> but only one seems to be functional with the Dell
> kernel and it doesn't seem to let me data back.
>
> I can create a new USB drive to test the new
> kernel and I can try hooking up to serial again to
> see if the new kernel will give me additional
> control, would I need all the files like the
> System.map too or would the zImage and initrd be
> enough?
Will this work? https://www.ebay.com/itm/355519965973
-------------------------------------------------------
> bodhi,
>
> There are two sets of headers which look like UART
> ports on
> the
> motherboard; I've tried connecting to both
> but only one seems to be functional with the Dell
> kernel and it doesn't seem to let me data back.
>
> I can create a new USB drive to test the new
> kernel and I can try hooking up to serial again to
> see if the new kernel will give me additional
> control, would I need all the files like the
> System.map too or would the zImage and initrd be
> enough?
Will this work? https://www.ebay.com/itm/355519965973
|
Re: Debian on Dell Wyse 3020 April 17, 2024 06:22PM |
Admin Registered: 13 years ago Posts: 18,575 |
> Will this work?
> https://www.ebay.com/itm/355519965973
That looks OK, it's the right chip. But as with any cheap serial converter module from eBay, you'd have to try to know for sure.
If it does not work, see in the Wiki thread:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/17/2024 06:31PM by bodhi.
> https://www.ebay.com/itm/355519965973
That looks OK, it's the right chip. But as with any cheap serial converter module from eBay, you'd have to try to know for sure.
If it does not work, see in the Wiki thread:
Quote
Unbricking with Serial Console & JTAG console
How to unbrick your box using serial console with kwboot
....
Serial Port connector - what are people using to make it work
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/17/2024 06:31PM by bodhi.
