|
Re: Debian on Dell Wyse 3020 April 17, 2024 08:08PM |
Registered: 6 months ago Posts: 6 |
Is there a comprehensive guide, step 1 to end, on how to install a Linux distribution on a 3020? I am waiting for my uart USB unit to arrive, but in the meanwhile I was wondering if there is a comprehensive list of steps. Should be possible to make such a guide since I doubt these units have much in the way of variety to them.
|
Re: Debian on Dell Wyse 3020 April 17, 2024 09:48PM |
Admin Registered: 13 years ago Posts: 18,997 |
@primuspaul,
> Is there a comprehensive guide, step 1 to end, on
> how to install a Linux distribution on a 3020?
No we don't, atm. This is where you should start reading:
https://forum.doozan.com/read.php?2,134563,137251#msg-137251
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Is there a comprehensive guide, step 1 to end, on
> how to install a Linux distribution on a 3020?
No we don't, atm. This is where you should start reading:
https://forum.doozan.com/read.php?2,134563,137251#msg-137251
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 April 18, 2024 11:53PM |
Registered: 6 months ago Posts: 2 |
primuspaul Wrote:
-------------------------------------------------------
> Is there a comprehensive guide, step 1 to end, on
> how to install a Linux distribution on a 3020? I
> am waiting for my uart USB unit to arrive, but in
> the meanwhile I was wondering if there is a
> comprehensive list of steps. Should be possible to
> make such a guide since I doubt these units have
> much in the way of variety to them.
With mmm updated script mmm updated creator you can easy make a bootable USB drive (you need a linux machine or a virtual machine). If you set your wyse3020 to boot from usb first, and plug usb key to device, you will get a working linux remote machine (no video output, only ssh or serial console).
-------------------------------------------------------
> Is there a comprehensive guide, step 1 to end, on
> how to install a Linux distribution on a 3020? I
> am waiting for my uart USB unit to arrive, but in
> the meanwhile I was wondering if there is a
> comprehensive list of steps. Should be possible to
> make such a guide since I doubt these units have
> much in the way of variety to them.
With mmm updated script mmm updated creator you can easy make a bootable USB drive (you need a linux machine or a virtual machine). If you set your wyse3020 to boot from usb first, and plug usb key to device, you will get a working linux remote machine (no video output, only ssh or serial console).
|
Re: Debian on Dell Wyse 3020 April 19, 2024 12:31PM |
Registered: 6 months ago Posts: 6 |
parittya Wrote:
-------------------------------------------------------
> primuspaul Wrote:
> -------------------------------------------------------
> > Is there a comprehensive guide, step 1 to end,
> on
> > how to install a Linux distribution on a 3020?
> I
> > am waiting for my uart USB unit to arrive, but
> in
> > the meanwhile I was wondering if there is a
> > comprehensive list of steps. Should be possible
> to
> > make such a guide since I doubt these units
> have
> > much in the way of variety to them.
>
> With mmm updated script
> mmm
> updated creator you can easy make a bootable
> USB drive (you need a linux machine or a virtual
> machine). If you set your wyse3020 to boot from
> usb first, and plug usb key to device, you will
> get a working linux remote machine (no video
> output, only ssh or serial console).
I see. So do I understand correctly that the device will only ever be accessible via ssh over network and the dvi ports will never work? With the exception of accessing the terminal output directly via another device through a USB uart cable?
Another question: how exactly does the process of booting it work? Meaning if I use that script maker and connect to ethernet and ssh in, will that be the OS running on the USB or do I then install the os onto the internal 4gb drive of the wyse 3020 and use that?
-------------------------------------------------------
> primuspaul Wrote:
> -------------------------------------------------------
> > Is there a comprehensive guide, step 1 to end,
> on
> > how to install a Linux distribution on a 3020?
> I
> > am waiting for my uart USB unit to arrive, but
> in
> > the meanwhile I was wondering if there is a
> > comprehensive list of steps. Should be possible
> to
> > make such a guide since I doubt these units
> have
> > much in the way of variety to them.
>
> With mmm updated script
> mmm
> updated creator you can easy make a bootable
> USB drive (you need a linux machine or a virtual
> machine). If you set your wyse3020 to boot from
> usb first, and plug usb key to device, you will
> get a working linux remote machine (no video
> output, only ssh or serial console).
I see. So do I understand correctly that the device will only ever be accessible via ssh over network and the dvi ports will never work? With the exception of accessing the terminal output directly via another device through a USB uart cable?
Another question: how exactly does the process of booting it work? Meaning if I use that script maker and connect to ethernet and ssh in, will that be the OS running on the USB or do I then install the os onto the internal 4gb drive of the wyse 3020 and use that?
|
Re: Debian on Dell Wyse 3020 April 19, 2024 02:29PM |
Admin Registered: 13 years ago Posts: 18,997 |
@ksuszka,
Please try the new kernel 6.8.7-mvebu-tld-1:
https://forum.doozan.com/read.php?2,32146
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Please try the new kernel 6.8.7-mvebu-tld-1:
https://forum.doozan.com/read.php?2,32146
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 April 19, 2024 04:41PM |
Registered: 9 months ago Posts: 38 |
@bodhi yes, I've installed it on the usb stick and it seems to be booting just fine. Great job!
Here is the boot log for reference:
Here is the boot log for reference:
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 6.8.7-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 Thu Apr 18 14:14:32 PDT 2024 [ 0.000000] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache [ 0.000000] OF: fdt: Machine model: Dell Ariel [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x0000000000000000-0x000000002fffffff] [ 0.000000] HighMem [mem 0x0000000030000000-0x000000007fefffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000000000-0x000000007fefffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fefffff] [ 0.000000] percpu: Embedded 29 pages/cpu s25300 r8192 d85292 u118784 [ 0.000000] pcpu-alloc: s25300 r8192 d85292 u118784 alloc=29*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Kernel command line: root=LABEL=rootfs raid=noautodetect console=ttyS2,115200 [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 522304 [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] Memory: 2052676K/2096128K available (10240K kernel code, 860K rwdata, 3500K rodata, 1024K init, 319K bss, 43452K reserved, 0K cma-reserved, 1309696K highmem) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 [ 0.000000] L2C: platform modifies aux control register: 0x02060000 -> 0x32860000 [ 0.000000] L2C: DT/platform modifies aux control register: 0x02060000 -> 0x32860000 [ 0.000000] Tauros3 cache controller enabled, 8 ways, 512 kB [ 0.000000] Tauros3: CACHE_ID 0x880000ed, AUX_CTRL 0x32860000 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000006] sched_clock: 32 bits at 26MHz, resolution 38ns, wraps every 82595524588ns [ 0.000068] clocksource: clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 73510017198 ns [ 0.000283] smp_twd: clock not found -2 [ 0.000806] kfence: initialized - using 2097152 bytes for 255 objects at 0x(ptrval)-0x(ptrval) [ 0.001303] Console: colour dummy device 80x30 [ 0.001354] Calibrating local timer... 2.16MHz. [ 0.060264] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 0.100291] CPU: Testing write buffer coherency: ok [ 0.100366] pid_max: default: 32768 minimum: 301 [ 0.105948] LSM: initializing lsm=capability,integrity [ 0.107303] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.107325] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) [ 0.111565] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.113687] RCU Tasks: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1. [ 0.113955] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1. [ 0.114163] Setting up static identity map for 0x100000 - 0x100060 [ 0.114780] rcu: Hierarchical SRCU implementation. [ 0.114791] rcu: Max phase no-delay instances is 1000. [ 0.116190] smp: Bringing up secondary CPUs ... [ 0.150295] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.150986] smp: Brought up 1 node, 2 CPUs [ 0.151007] SMP: Total of 2 processors activated (2382.23 BogoMIPS). [ 0.151022] CPU: All CPU(s) started in SVC mode. [ 0.153388] devtmpfs: initialized [ 0.164703] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6 [ 0.165353] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.165400] futex hash table entries: 512 (order: 3, 32768 bytes, linear) [ 0.169083] prandom: seed boundary self test passed [ 0.171660] prandom: 100 self tests passed [ 0.171675] pinctrl core: initialized pinctrl subsystem [ 0.174046] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.174677] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.185263] audit: initializing netlink subsys (disabled) [ 0.186674] thermal_sys: Registered thermal governor 'step_wise' [ 0.186781] audit: type=2000 audit(0.190:1): state=initialized audit_enabled=0 res=1 [ 0.186858] cpuidle: using governor ladder [ 0.186915] cpuidle: using governor menu [ 0.187101] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0 [ 0.187119] hw-breakpoint: CPU 0 failed to disable vector catch [ 0.187181] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 1 [ 0.190891] platform soc: Fixed dependency cycle(s) with /soc/interrupt-controller@e0001000 [ 0.370571] raid6: int32x8 gen() 222 MB/s [ 0.540593] raid6: int32x4 gen() 237 MB/s [ 0.710705] raid6: int32x2 gen() 366 MB/s [ 0.880834] raid6: int32x1 gen() 377 MB/s [ 0.880848] raid6: using algorithm int32x1 gen() 377 MB/s [ 1.050957] raid6: .... xor() 189 MB/s, rmw enabled [ 1.050970] raid6: using intx1 recovery algorithm [ 1.053201] SCSI subsystem initialized [ 1.053580] libata version 3.00 loaded. [ 1.053969] usbcore: registered new interface driver usbfs [ 1.054040] usbcore: registered new interface driver hub [ 1.054112] usbcore: registered new device driver usb [ 1.054618] pps_core: LinuxPPS API ver. 1 registered [ 1.054632] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 1.054663] PTP clock support registered [ 1.057741] vgaarb: loaded [ 1.058686] clocksource: Switched to clocksource clocksource [ 1.070944] VFS: Disk quotas dquot_6.6.0 [ 1.071503] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.097183] NET: Registered PF_INET protocol family [ 1.097626] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) [ 1.099913] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear) [ 1.100209] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 1.100291] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) [ 1.100418] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear) [ 1.100562] TCP: Hash tables configured (established 8192 bind 8192) [ 1.101449] MPTCP token hash table entries: 1024 (order: 2, 16384 bytes, linear) [ 1.102010] UDP hash table entries: 512 (order: 2, 16384 bytes, linear) [ 1.102053] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) [ 1.103237] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 1.104776] RPC: Registered named UNIX socket transport module. [ 1.104794] RPC: Registered udp transport module. [ 1.104804] RPC: Registered tcp transport module. [ 1.104813] RPC: Registered tcp-with-tls transport module. [ 1.104823] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.104855] PCI: CLS 0 bytes, default 64 [ 1.109404] Trying to unpack rootfs image as initramfs... [ 1.120876] Initialise system trusted keyrings [ 1.121098] Key type blacklist registered [ 1.121769] workingset: timestamp_bits=14 max_order=19 bucket_order=5 [ 1.121915] zbud: loaded [ 1.156762] NFS: Registering the id_resolver key type [ 1.156900] Key type id_resolver registered [ 1.156912] Key type id_legacy registered [ 1.157318] nfs4filelayout_init: NFSv4 File Layout Driver Registering... [ 1.157348] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... [ 1.315274] xor: measuring software checksum speed [ 1.323616] arm4regs : 1198 MB/sec [ 1.335121] 8regs : 869 MB/sec [ 1.344253] 32regs : 1086 MB/sec [ 1.344266] xor: using function: arm4regs (1198 MB/sec) [ 1.344301] async_tx: api initialized (async) [ 1.344329] Key type asymmetric registered [ 1.344343] Asymmetric key parser 'x509' registered [ 1.345095] bounce: pool size: 64 pages [ 1.346321] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245) [ 1.347382] io scheduler bfq registered [ 1.373258] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 1.382737] Freeing initrd memory: 5172K [ 1.596611] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled [ 1.605988] printk: legacy console [ttyS2] disabled [ 1.607561] d4018000.serial: ttyS2 at MMIO 0xd4018000 (irq = 381, base_baud = 1625000) is a XScale [ 1.607970] printk: legacy console [ttyS2] enabled [ 2.514898] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information. [ 2.523535] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved. [ 2.539777] usbcore: registered new interface driver smsc75xx [ 2.551224] mv-ehci d4208000.usb: EHCI Host Controller [ 2.557081] mv-ehci d4208000.usb: new USB bus registered, assigned bus number 1 [ 2.566615] mv-ehci d4208000.usb: irq 382, io mem 0xd4208000 [ 2.598758] mv-ehci d4208000.usb: USB 2.0 started, EHCI 1.00 [ 2.605765] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08 [ 2.614739] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.623213] usb usb1: Product: EHCI Host Controller [ 2.628803] usb usb1: Manufacturer: Linux 6.8.7-mvebu-tld-1 ehci_hcd [ 2.635809] usb usb1: SerialNumber: d4208000.usb [ 2.642780] hub 1-0:1.0: USB hub found [ 2.647307] hub 1-0:1.0: 1 port detected [ 2.653383] mv-ehci d4208000.usb: successful find EHCI device with regs 0x(ptrval) irq 382 working in Host mode [ 2.664478] usbcore: registered new interface driver usblp [ 2.671030] usbcore: registered new interface driver usb-storage [ 2.678907] mousedev: PS/2 mouse device common for all mice [ 2.686060] i2c_dev: i2c /dev entries driver [ 2.694274] device-mapper: uevent: version 1.0.3 [ 2.700395] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com [ 2.710306] device-mapper: multipath round-robin: version 1.2.0 loaded [ 2.717488] device-mapper: multipath queue-length: version 0.2.0 loaded [ 2.724816] device-mapper: multipath service-time: version 0.3.0 loaded [ 2.732419] device-mapper: dm-log-userspace: version 1.3.0 loaded [ 2.739725] sdhci: Secure Digital Host Controller Interface driver [ 2.746559] sdhci: Copyright(c) Pierre Ossman [ 2.753532] sdhci-pltfm: SDHCI platform and OF driver helper [ 2.760928] hid: raw HID events driver (C) Jiri Kosina [ 2.768472] usbcore: registered new interface driver usbhid [ 2.774872] usbhid: USB HID core driver [ 2.783000] NET: Registered PF_INET6 protocol family [ 2.791428] Segment Routing with IPv6 [ 2.795771] RPL Segment Routing with IPv6 [ 2.801190] In-situ OAM (IOAM) with IPv6 [ 2.802428] mmc0: SDHCI controller on d4281000.mmc [d4281000.mmc] using ADMA [ 2.805910] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver [ 2.822613] NET: Registered PF_PACKET protocol family [ 2.829485] 8021q: 802.1Q VLAN Support v1.8 [ 2.834501] Key type dns_resolver registered [ 2.839784] ThumbEE CPU extension supported. [ 2.844737] Registering SWP/SWPB emulation handler [ 2.915522] registered taskstats version 1 [ 2.920603] Loading compiled-in X.509 certificates [ 2.948838] usb 1-1: new high-speed USB device number 2 using mv-ehci [ 2.968443] Key type .fscrypt registered [ 2.973224] Key type fscrypt-provisioning registered [ 2.979300] Key type big_key registered [ 3.138183] mmc0: new HS200 MMC card at address 0001 [ 3.145998] mmcblk0: mmc0:0001 H4G2a\x11 3.64 GiB [ 3.155058] mmcblk0: p1 p2 [ 3.160491] mmcblk0boot0: mmc0:0001 H4G2a\x11 4.00 MiB [ 3.170024] mmcblk0boot1: mmc0:0001 H4G2a\x11 4.00 MiB [ 3.178925] mmcblk0rpmb: mmc0:0001 H4G2a\x11 4.00 MiB, chardev (244:0) [ 3.187554] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=77.63 [ 3.196555] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3.204512] Key type encrypted registered [ 3.209388] usb 1-1: Product: USB2.0 Hub [ 3.219937] hub 1-1:1.0: USB hub found [ 3.224929] hub 1-1:1.0: 4 ports detected [ 3.236272] mv-ehci f0001000.usb: EHCI Host Controller [ 3.242223] mv-ehci f0001000.usb: new USB bus registered, assigned bus number 2 [ 3.250568] mv-ehci f0001000.usb: irq 384, io mem 0xf0001000 [ 3.288751] mv-ehci f0001000.usb: USB 2.0 started, EHCI 1.00 [ 3.295494] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08 [ 3.304459] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.312360] usb usb2: Product: EHCI Host Controller [ 3.317898] usb usb2: Manufacturer: Linux 6.8.7-mvebu-tld-1 ehci_hcd [ 3.324925] usb usb2: SerialNumber: f0001000.usb [ 3.331454] hub 2-0:1.0: USB hub found [ 3.336439] hub 2-0:1.0: 1 port detected [ 3.342412] mv-ehci f0001000.usb: successful find EHCI device with regs 0x(ptrval) irq 384 working in Host mode [ 3.354875] clk: Disabling unused clocks [ 3.363176] Freeing unused kernel image (initmem) memory: 1024K [ 3.372460] Checked W+X mappings: passed, no W+X pages found [ 3.378857] Run /init as init process [ 3.383215] with arguments: [ 3.383231] /init [ 3.383244] with environment: [ 3.383256] HOME=/ [ 3.383269] TERM=linux [ 3.529026] usb 2-1: new high-speed USB device number 2 using mv-ehci [ 3.564780] usb 1-1.1: new high-speed USB device number 3 using mv-ehci [ 3.722680] usb 1-1.1: New USB device found, idVendor=0718, idProduct=070a, bcdDevice= 1.00 [ 3.731765] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.739774] usb 1-1.1: Product: TF10 [ 3.744015] usb 1-1.1: Manufacturer: TDK LoR [ 3.749016] usb 1-1.1: SerialNumber: 0703341D121F0148 [ 3.758983] usb-storage 1-1.1:1.0: USB Mass Storage device detected [ 3.771766] usb 2-1: New USB device found, idVendor=0424, idProduct=2640, bcdDevice= a.a0 [ 3.774126] scsi host0: usb-storage 1-1.1:1.0 [ 3.786654] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 3.819231] hub 2-1:1.0: USB hub found [ 3.828851] hub 2-1:1.0: 3 ports detected [ 3.859257] usbcore: registered new interface driver uas [ 3.898806] usb 1-1.2: new low-speed USB device number 4 using mv-ehci [ 4.053463] usb 1-1.2: New USB device found, idVendor=046a, idProduct=b091, bcdDevice= 1.00 [ 4.078851] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.087513] usb 1-1.2: Product: Cherry USB Optical Mouse [ 4.101213] usb 1-1.2: Manufacturer: PixArt [ 4.124067] input: PixArt Cherry USB Optical Mouse as /devices/platform/soc/d4200000.axi/d4208000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:046A:B091.0001/input/input0 [ 4.159956] hid-generic 0003:046A:B091.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt Cherry USB Optical Mouse] on usb-d4208000.usb-1.2/input0 [ 4.218888] usb 2-1.1: new high-speed USB device number 3 using mv-ehci [ 4.288804] usb 1-1.3: new low-speed USB device number 5 using mv-ehci [ 4.395378] usb 2-1.1: New USB device found, idVendor=0424, idProduct=4040, bcdDevice= 2.01 [ 4.404540] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.412599] usb 2-1.1: Product: Ultra Fast Media Reader [ 4.418500] usb 2-1.1: Manufacturer: Generic [ 4.423521] usb 2-1.1: SerialNumber: 000000264001 [ 4.431693] usb-storage 2-1.1:1.0: USB Mass Storage device detected [ 4.443245] scsi host1: usb-storage 2-1.1:1.0 [ 4.464939] usb 1-1.3: New USB device found, idVendor=045e, idProduct=07b9, bcdDevice= 1.14 [ 4.488764] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4.496743] usb 1-1.3: Product: USB Keyboard [ 4.508757] usb 1-1.3: Manufacturer: LITEON Technology [ 4.529754] input: LITEON Technology USB Keyboard as /devices/platform/soc/d4200000.axi/d4208000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:045E:07B9.0002/input/input1 [ 4.548860] usb 2-1.2: new high-speed USB device number 4 using mv-ehci [ 4.611382] hid-generic 0003:045E:07B9.0002: input,hidraw1: USB HID v1.10 Keyboard [LITEON Technology USB Keyboard] on usb-d4208000.usb-1.3/input0 [ 4.720007] usb 2-1.2: New USB device found, idVendor=0424, idProduct=7500, bcdDevice= 1.00 [ 4.738760] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4.746717] usb 2-1.2: Product: LAN7500 [ 4.768781] usb 2-1.2: Manufacturer: SMSC [ 4.773468] usb 2-1.2: SerialNumber: 000000003 [ 4.783470] smsc75xx v1.0.0 [ 4.881688] scsi 0:0:0:0: Direct-Access TDK LoR TF10 PMAP PQ: 0 ANSI: 4 [ 4.903716] sd 0:0:0:0: [sda] 15116736 512-byte logical blocks: (7.74 GB/7.21 GiB) [ 4.912870] sd 0:0:0:0: [sda] Write Protect is off [ 4.918340] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00 [ 4.920362] sd 0:0:0:0: [sda] No Caching mode page found [ 4.926352] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.933956] smsc75xx 2-1.2:1.0 eth0: register 'smsc75xx' at usb-f0001000.usb-1.2, smsc75xx USB 2.0 Gigabit Ethernet, 00:80:64:e6:dd:a1 [ 4.970906] sda: sda1 sda2 [ 4.991274] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 5.042959] smsc75xx 2-1.2:1.0 enx008064e6dda1: renamed from eth0 [ 5.261969] (null): Enabling slave mode [ 5.285833] pxa2xx-spi d4035000.spi: no DMA channels available, using PIO [ 5.312153] rtc-ds1307 0-0068: registered as rtc0 [ 5.326335] rtc-ds1307 0-0068: setting system clock to 2024-04-19T21:31:22 UTC (1713562282) [ 5.349759] i2c i2c-0: PXA I2C adapter, slave address 1 [ 5.379776] (null): Enabling slave mode [ 5.396957] i2c i2c-1: PXA I2C adapter, slave address 1 [ 5.420736] (null): Enabling slave mode [ 5.475575] i2c i2c-2: PXA I2C adapter, slave address 1 [ 5.520506] scsi 1:0:0:0: Direct-Access Generic Ultra HS-COMBO 2.01 PQ: 0 ANSI: 0 [ 5.532052] sd 1:0:0:0: [sdb] Media removed, stopped polling [ 5.540179] sd 1:0:0:0: [sdb] Attached SCSI removable disk [ 6.328408] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 6.334874] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 6.890341] EXT4-fs (sda2): mounting ext3 file system using the ext4 subsystem [ 6.947565] EXT4-fs (sda2): mounted filesystem 644a2135-2baf-49ef-841d-74e1ff13c2ef ro with ordered data mode. Quota mode: none. [ 13.062903] EXT4-fs (sda2): re-mounted 644a2135-2baf-49ef-841d-74e1ff13c2ef r/w. Quota mode: none. [ 15.198784] random: crng init done [ 15.394532] smsc75xx 2-1.2:1.0 eth0: renamed from enx008064e6dda1 [ 19.063165] smsc75xx 2-1.2:1.0 eth0: link up, 1000Mbps, full-duplex, lpa 0xCDE1 [ 68.113256] usb 1-1.2: USB disconnect, device number 4 [ 69.688613] usb 1-1.2: new low-speed USB device number 6 using mv-ehci [ 69.843413] usb 1-1.2: New USB device found, idVendor=046a, idProduct=b091, bcdDevice= 1.00 [ 69.852504] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 69.860550] usb 1-1.2: Product: Cherry USB Optical Mouse [ 69.866524] usb 1-1.2: Manufacturer: PixArt [ 69.879601] input: PixArt Cherry USB Optical Mouse as /devices/platform/soc/d4200000.axi/d4208000.usb/usb1/1-1/1-1.2/1-1.2:1.0/0003:046A:B091.0003/input/input2 [ 69.896185] hid-generic 0003:046A:B091.0003: input,hidraw0: USB HID v1.11 Mouse [PixArt Cherry USB Optical Mouse] on usb-d4208000.usb-1.2/input0
|
Re: Debian on Dell Wyse 3020 April 19, 2024 06:44PM |
Admin Registered: 13 years ago Posts: 18,997 |
> @bodhi yes, I've installed it on the usb stick and it seems to be booting just fine. Great job!
Cool! Thanks!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/20/2024 08:27PM by bodhi.
Cool! Thanks!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/20/2024 08:27PM by bodhi.
|
Re: Debian on Dell Wyse 3020 April 19, 2024 11:43PM |
Registered: 6 months ago Posts: 2 |
primuspaul Wrote:
-------------------------------------------------------
> parittya Wrote:
> -------------------------------------------------------
> > primuspaul Wrote:
> >
> -------------------------------------------------------
> > > Is there a comprehensive guide, step 1 to
> end,
> > on
> > > how to install a Linux distribution on a
> 3020?
> > I
> > > am waiting for my uart USB unit to arrive,
> but
> > in
> > > the meanwhile I was wondering if there is a
> > > comprehensive list of steps. Should be
> possible
> > to
> > > make such a guide since I doubt these units
> > have
> > > much in the way of variety to them.
> >
> > With mmm updated script
> >
> mmm
> > updated creator you can easy make a
> bootable
> > USB drive (you need a linux machine or a
> virtual
> > machine). If you set your wyse3020 to boot from
> > usb first, and plug usb key to device, you will
> > get a working linux remote machine (no video
> > output, only ssh or serial console).
>
> I see. So do I understand correctly that the
> device will only ever be accessible via ssh over
> network and the dvi ports will never work? With
> the exception of accessing the terminal output
> directly via another device through a USB uart
> cable?
>
> Another question: how exactly does the process of
> booting it work? Meaning if I use that script
> maker and connect to ethernet and ssh in, will
> that be the OS running on the USB or do I then
> install the os onto the internal 4gb drive of the
> wyse 3020 and use that?
The device booted from usb stick, and working from it. I did not try to install buit in emmc, but use it (after when formatted) to storage. I used 6.5.7 kernel for making boot (that is the default in the linked script)
I used the machine over ethernet with cable, for torrent server with external usb ssd.
I did not try to use uart, the ethernet connection is enough fro me, and boot process successed at first try, got IP address from DHCP.
Video output gone immediatelly after the start of boot process.
The "boot maker" script make a bootable usb stick for you, and use that stick to use for the wyse3020.
-------------------------------------------------------
> parittya Wrote:
> -------------------------------------------------------
> > primuspaul Wrote:
> >
> -------------------------------------------------------
> > > Is there a comprehensive guide, step 1 to
> end,
> > on
> > > how to install a Linux distribution on a
> 3020?
> > I
> > > am waiting for my uart USB unit to arrive,
> but
> > in
> > > the meanwhile I was wondering if there is a
> > > comprehensive list of steps. Should be
> possible
> > to
> > > make such a guide since I doubt these units
> > have
> > > much in the way of variety to them.
> >
> > With mmm updated script
> >
> mmm
> > updated creator you can easy make a
> bootable
> > USB drive (you need a linux machine or a
> virtual
> > machine). If you set your wyse3020 to boot from
> > usb first, and plug usb key to device, you will
> > get a working linux remote machine (no video
> > output, only ssh or serial console).
>
> I see. So do I understand correctly that the
> device will only ever be accessible via ssh over
> network and the dvi ports will never work? With
> the exception of accessing the terminal output
> directly via another device through a USB uart
> cable?
>
> Another question: how exactly does the process of
> booting it work? Meaning if I use that script
> maker and connect to ethernet and ssh in, will
> that be the OS running on the USB or do I then
> install the os onto the internal 4gb drive of the
> wyse 3020 and use that?
The device booted from usb stick, and working from it. I did not try to install buit in emmc, but use it (after when formatted) to storage. I used 6.5.7 kernel for making boot (that is the default in the linked script)
I used the machine over ethernet with cable, for torrent server with external usb ssd.
I did not try to use uart, the ethernet connection is enough fro me, and boot process successed at first try, got IP address from DHCP.
Video output gone immediatelly after the start of boot process.
The "boot maker" script make a bootable usb stick for you, and use that stick to use for the wyse3020.
|
Re: Debian on Dell Wyse 3020 April 22, 2024 04:34PM |
Admin Registered: 13 years ago Posts: 18,997 |
@ksuszka,
> Here is the boot log for reference
I did not see Wifi in the log. Perhaps I need to do more configuration for it.
UPDATE:
It seems already configured
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/22/2024 04:44PM by bodhi.
> Here is the boot log for reference
I did not see Wifi in the log. Perhaps I need to do more configuration for it.
UPDATE:
It seems already configured
RT2800USB_RT35XX [=y]
Quote
WI1 module IF: USB (non-standard connector)
WI1 chip1: Ralink RT3572
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/22/2024 04:44PM by bodhi.
|
Re: Debian on Dell Wyse 3020 April 22, 2024 04:53PM |
Admin Registered: 13 years ago Posts: 18,997 |
@ksuszka et al,
Please try:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 04/22/2024 04:54PM by bodhi.
Please try:
modprobe rt2800usb dmesg ifconfig -a
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 04/22/2024 04:54PM by bodhi.
|
Re: Debian on Dell Wyse 3020 April 22, 2024 05:57PM |
Registered: 9 months ago Posts: 38 |
Quote
bodhi
I did not see Wifi in the log. Perhaps I need to do more configuration for it.
that is most like due to the fact that both my units came without wifi modules. As I gathered from images of the inside of various versions of those terminals from the internet there is no wifi builtin on the main board but it is provided in some units by an extension card. See this picture: wyse 3020 with wifi adapter. My units don't have this green card and antennas.
So depending on where you source them from you can get a unit with or without a wifi module.
Edited 2 time(s). Last edit at 04/22/2024 06:02PM by ksuszka.
|
Re: Debian on Dell Wyse 3020 April 22, 2024 06:55PM |
Admin Registered: 13 years ago Posts: 18,997 |
> that is most like due to the fact that both my
> units came without wifi modules. As I gathered
> from images of the inside of various versions of
> those terminals from the internet there is no wifi
> builtin on the main board but it is provided in
> some units by an extension card. See this picture:
> wyse
> 3020 with wifi adapter. My units don't have
> this green card and antennas.
>
> So depending on where you source them from you can
> get a unit with or without a wifi module.
Thanks!
I guess it's time I open up my Wyse 3020. You guys have been doing such a great job so I have not even power up my box yet :))
Perhaps when I can find a good time to investigate the display, I'm thinking we could just run a simple FB DRM in this kernel. There is no public info about the MMP3 SoC GPU, so it might be hard to get it working.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/22/2024 07:01PM by bodhi.
> units came without wifi modules. As I gathered
> from images of the inside of various versions of
> those terminals from the internet there is no wifi
> builtin on the main board but it is provided in
> some units by an extension card. See this picture:
> wyse
> 3020 with wifi adapter. My units don't have
> this green card and antennas.
>
> So depending on where you source them from you can
> get a unit with or without a wifi module.
Thanks!
I guess it's time I open up my Wyse 3020. You guys have been doing such a great job so I have not even power up my box yet :))
Perhaps when I can find a good time to investigate the display, I'm thinking we could just run a simple FB DRM in this kernel. There is no public info about the MMP3 SoC GPU, so it might be hard to get it working.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/22/2024 07:01PM by bodhi.
|
Re: Debian on Dell Wyse 3020 April 24, 2024 04:37PM |
Admin Registered: 13 years ago Posts: 18,997 |
All,
I'm looking for the Git(Hub) URL (I think it is OpenWrt staging) of Lubomir Rintel (the MMP3 Arch maintainer and author of this Ariel DTS). I want to see if the DTS has been updated by Lubomir.
Thanks!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I'm looking for the Git(Hub) URL (I think it is OpenWrt staging) of Lubomir Rintel (the MMP3 Arch maintainer and author of this Ariel DTS). I want to see if the DTS has been updated by Lubomir.
Thanks!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 April 25, 2024 03:05PM |
Admin Registered: 13 years ago Posts: 18,997 |
@ksuszka,
Pardon me if I missed what you have posted about this topic.
Have you figured out if we can install Linux on this box without using the wloader GUI to select booting from USB? or is it the only way?
=======
Speaking about display, I've found what need to be done in the kernel to start enable video. I'll need to build a new kernel for this.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/25/2024 03:08PM by bodhi.
Pardon me if I missed what you have posted about this topic.
Have you figured out if we can install Linux on this box without using the wloader GUI to select booting from USB? or is it the only way?
=======
Speaking about display, I've found what need to be done in the kernel to start enable video. I'll need to build a new kernel for this.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/25/2024 03:08PM by bodhi.
|
Re: Debian on Dell Wyse 3020 April 25, 2024 09:37PM |
Registered: 6 months ago Posts: 6 |
bodhi Wrote:
-------------------------------------------------------
> > 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:
>
>
I got the usb/uart device. What software do I need to use it?
-------------------------------------------------------
> > 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:
>
>
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
>
I got the usb/uart device. What software do I need to use it?
|
Re: Debian on Dell Wyse 3020 April 25, 2024 10:04PM |
Admin Registered: 13 years ago Posts: 18,997 |
> I got the usb/uart device. What software do I need
> to use it?
On a Linux host: picocom or minicom. On MacOS: screen. On Windows: putty.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> to use it?
On a Linux host: picocom or minicom. On MacOS: screen. On Windows: putty.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 April 26, 2024 01:26AM |
Registered: 9 months ago Posts: 38 |
@bodhi
TL;DR How to permamently boot linux from USB drive
Go to WLoader Setup, switch to Boot Order tab, move USB to the top, clik OK, save settings, reboot.
TL;DR How to permamently boot linux from internal eMMC drive
WLoader changes
To temporary select a different boot device, press the power button for about four seconds until the power light turns green, and then press the P key. Enter the "Fireport" password and select a device to boot from.
To access the WLoader settings, press the power button for about four seconds until the power light turns green, and then press the Delete key. Enter the "Fireport" password.
To reset WLoader to factory settings, press the power button for about four seconds until the power light turns green, and then press the G key.
OR
Access the WLoader settings, press Shutdown button and on the modal dialog box select checkbox to reset WLoader to factory settings.
See https://photos.app.goo.gl/Hxo3LPDaUAvnLuHU7 screen shots for reference.
Switching boot mode
WLoader can work in 3 booting modes: WTOS Mode, WinCE Mode, Linux Mode. The WTOS Mode is the default one. To boot linux from eMMC it needs to be switched into the "Linux Mode".
To switch to the linux boot mode:
1. 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. 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.
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.
See https://forum.doozan.com/read.php?2,134563,136655#msg-136655 for more details.
Changing the boot device order
To permamently change the device boot order, open WLoader settings, switch to the "Boot Order" page, move your preferred device to the top, click OK, save settings and reboot.
If you change focus to the specific device on the "Boot Order" page and the "URL" field is empty it means that WLoader doesn't recognize the file system on this device and it will not boot from it even if it is moved to the top. If the file system is recognized there should be "D:/;" or similar text in the URL field.
Another way to see which file systems were recognized and are eligible for booting is to check the "Event Log" tab. There should be entry like "D: registered, type 0xc, size 100MB" for each recognized partition.
Edited 1 time(s). Last edit at 04/26/2024 10:12AM by ksuszka.
TL;DR How to permamently boot linux from USB drive
Go to WLoader Setup, switch to Boot Order tab, move USB to the top, clik OK, save settings, reboot.
TL;DR How to permamently boot linux from internal eMMC drive
- Install linux on eMMC drive with the same parition structure and content as on the USB stick.
- Switch WLoader's boot mode to linux:
- Go to WLoader Setup, switch to Setting tab, enter "uImage" in the "Kernel image" textbox, clik OK, save settings, reboot
- Switch device boot order:
- Go to WLoader Setup, switch to Boot Order tab, move HardDisk to the top, clik OK, save settings, reboot.
WLoader changes
To temporary select a different boot device, press the power button for about four seconds until the power light turns green, and then press the P key. Enter the "Fireport" password and select a device to boot from.
To access the WLoader settings, press the power button for about four seconds until the power light turns green, and then press the Delete key. Enter the "Fireport" password.
To reset WLoader to factory settings, press the power button for about four seconds until the power light turns green, and then press the G key.
OR
Access the WLoader settings, press Shutdown button and on the modal dialog box select checkbox to reset WLoader to factory settings.
See https://photos.app.goo.gl/Hxo3LPDaUAvnLuHU7 screen shots for reference.
Switching boot mode
WLoader can work in 3 booting modes: WTOS Mode, WinCE Mode, Linux Mode. The WTOS Mode is the default one. To boot linux from eMMC it needs to be switched into the "Linux Mode".
To switch to the linux boot mode:
1. 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. 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.
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.
See https://forum.doozan.com/read.php?2,134563,136655#msg-136655 for more details.
Changing the boot device order
To permamently change the device boot order, open WLoader settings, switch to the "Boot Order" page, move your preferred device to the top, click OK, save settings and reboot.
If you change focus to the specific device on the "Boot Order" page and the "URL" field is empty it means that WLoader doesn't recognize the file system on this device and it will not boot from it even if it is moved to the top. If the file system is recognized there should be "D:/;" or similar text in the URL field.
Another way to see which file systems were recognized and are eligible for booting is to check the "Event Log" tab. There should be entry like "D: registered, type 0xc, size 100MB" for each recognized partition.
Edited 1 time(s). Last edit at 04/26/2024 10:12AM by ksuszka.
|
Re: Debian on Dell Wyse 3020 April 26, 2024 01:17PM |
Admin Registered: 13 years ago Posts: 18,997 |
@ksuszka,
Thanks! that was great info.
However, you did not answer my question:
It is OK if we have use the keyboard and monitor to select the boot mode during initial installation. But it's even better if there is a way to install Linux in a headless configuration.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thanks! that was great info.
However, you did not answer my question:
Quote
Have you figured out if we can install Linux on this box without using the wloader GUI to select booting from USB? or is it the only way?
It is OK if we have use the keyboard and monitor to select the boot mode during initial installation. But it's even better if there is a way to install Linux in a headless configuration.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 April 26, 2024 02:10PM |
Registered: 9 months ago Posts: 38 |
Sorry, I didn't catch what you were asking for. So as far as I know the answer is no, you cannot install linux from the usb drive in the headless mode because if you reset the device to factory settings (and I assume that for most users the seller will reset the device before sending it) it changes the boot mode to WNOS and puts HardDisk as the first boot device. So by default it always boots the installed WNOS from the eMMC.
If you open the box there are some pin connectors with an unknown use. Some are described here: https://linux-mmp.docs.kernel.org/dell-wyse-3020/connectors.html, so maybe with a proper tooling you could force boot from the usb using them.
And of course you could use an external flash programmer with a chip clip to replace WLoader with the Open Firmware (the idea described here: https://linux-mmp.docs.kernel.org/dell-wyse-3020.html#installing-open-firmware) but besides this old page I found no other information which would suggest that someone actually succeeded doing it.
EDIT: One more idea, when I played with the WLoader settings and I changed some options and then I read the flash memory those changes were easily identificable inside the flash. So in theory, if you could force it to boot from USB you could then modify the flash directly to change the boot order. But at this point connecting the keyboard and the monitor seems like a much simpler solution ;)
Edited 1 time(s). Last edit at 04/26/2024 02:23PM by ksuszka.
If you open the box there are some pin connectors with an unknown use. Some are described here: https://linux-mmp.docs.kernel.org/dell-wyse-3020/connectors.html, so maybe with a proper tooling you could force boot from the usb using them.
And of course you could use an external flash programmer with a chip clip to replace WLoader with the Open Firmware (the idea described here: https://linux-mmp.docs.kernel.org/dell-wyse-3020.html#installing-open-firmware) but besides this old page I found no other information which would suggest that someone actually succeeded doing it.
EDIT: One more idea, when I played with the WLoader settings and I changed some options and then I read the flash memory those changes were easily identificable inside the flash. So in theory, if you could force it to boot from USB you could then modify the flash directly to change the boot order. But at this point connecting the keyboard and the monitor seems like a much simpler solution ;)
Edited 1 time(s). Last edit at 04/26/2024 02:23PM by ksuszka.
|
Re: Debian on Dell Wyse 3020 April 28, 2024 03:26PM |
Admin Registered: 13 years ago Posts: 18,997 |
@ksuszka,
> EDIT: One more idea, when I played with the
> WLoader settings and I changed some options and
> then I read the flash memory those changes were
> easily identificable inside the flash. So in
> theory, if you could force it to boot from USB you
> could then modify the flash directly to change the
> boot order. But at this point connecting the
> keyboard and the monitor seems like a much simpler
> solution ;)
Indeed. Connect monitor and keyboard is a simple solution! Just that I noticed on eBay there are quite a few Wyse 3020 on sale for 10-15 USD without keyboard, mouse, and also without power supply. Just the box itself.
Finally open the box and connect a prepared USB, but it stuck at loading. It never finished loading.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/28/2024 03:28PM by bodhi.
> EDIT: One more idea, when I played with the
> WLoader settings and I changed some options and
> then I read the flash memory those changes were
> easily identificable inside the flash. So in
> theory, if you could force it to boot from USB you
> could then modify the flash directly to change the
> boot order. But at this point connecting the
> keyboard and the monitor seems like a much simpler
> solution ;)
Indeed. Connect monitor and keyboard is a simple solution! Just that I noticed on eBay there are quite a few Wyse 3020 on sale for 10-15 USD without keyboard, mouse, and also without power supply. Just the box itself.
Finally open the box and connect a prepared USB, but it stuck at loading. It never finished loading.
Loading D:/./uImage .....Should there be anything appearing on the monitor during and after this message? And any of the 4 USB ports will work?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/28/2024 03:28PM by bodhi.
|
Re: Debian on Dell Wyse 3020 April 29, 2024 01:17AM |
Registered: 9 months ago Posts: 38 |
AFAIK all 4 USB ports are working the same.
And yes, you won't see anyting besides "Loading" text even if it boots successfully. I attach photo of my screen when it is booting from eMMC.
As I set different label on my eMMC's rootfs partition I could use this screen to easily distinguish which partition it tried to boot from. But it stays at this screen regardless if it boots successfully or if it fails.
I use leds on the ethernet port as an indicator if it managed to boot successfully.
Edited 2 time(s). Last edit at 04/29/2024 01:33AM by ksuszka.
And yes, you won't see anyting besides "Loading" text even if it boots successfully. I attach photo of my screen when it is booting from eMMC.
As I set different label on my eMMC's rootfs partition I could use this screen to easily distinguish which partition it tried to boot from. But it stays at this screen regardless if it boots successfully or if it fails.
I use leds on the ethernet port as an indicator if it managed to boot successfully.
Edited 2 time(s). Last edit at 04/29/2024 01:33AM by ksuszka.
|
Re: Debian on Dell Wyse 3020 April 29, 2024 02:44PM |
Admin Registered: 13 years ago Posts: 18,997 |
|
Re: Debian on Dell Wyse 3020 April 30, 2024 12:08AM |
Admin Registered: 13 years ago Posts: 18,997 |
Quote
AFAIK all 4 USB ports are working the same.
And yes, you won't see anyting besides "Loading" text even if it boots successfully. I attach photo of my screen when it is booting from eMMC.
As I set different label on my eMMC's rootfs partition I could use this screen to easily distinguish which partition it tried to boot from. But it stays at this screen regardless if it boots successfully or if it fails.
I use leds on the ethernet port as an indicator if it managed to boot successfully.
Yeah, it was a HW problem. The noname USB was too old, probably dying :) Using a new 32GB Sandisk USB and it booted without issue.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 04/30/2024 12:11AM by bodhi.
|
Re: Debian on Dell Wyse 3020 April 30, 2024 02:27PM |
Admin Registered: 13 years ago Posts: 18,997 |
> I use leds on the ethernet port as an indicator if
> it managed to boot successfully.
Better yet, put this (or run a script) at the end of your /etc/rc.local. The box Status LED is amber when it is powered up. So it will turn green after the kernel has booted successfully.
Turn on Status Led
And then it will take some seconds to mount the rootfs. We can use the heartbeat LED during this time, but it is simpler just wait 10-20 seconds before trying to login.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> it managed to boot successfully.
Better yet, put this (or run a script) at the end of your /etc/rc.local. The box Status LED is amber when it is powered up. So it will turn green after the kernel has booted successfully.
Turn on Status Led
# Wyse 3020 if [ -d /sys/class/leds/green\:status ]; then echo none > /sys/class/leds/amber\:status/trigger echo default-on > /sys/class/leds/green\:status/trigger fi
And then it will take some seconds to mount the rootfs. We can use the heartbeat LED during this time, but it is simpler just wait 10-20 seconds before trying to login.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 May 01, 2024 01:06AM |
Admin Registered: 13 years ago Posts: 18,997 |
This is causing some problem with things run on a timer.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
[ 0.000286][ T0] smp_twd: clock not found -2
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 May 05, 2024 07:32AM |
Registered: 9 months ago Posts: 38 |
I connected my terminal through HDMI grabber and I captured various WLoader screenshots in the original resolution after the factory reset, during and after switching to the linux boot mode, with and without bootable usb connected.
I attach them here for a reference.
@bodhi It seems that WDM used in various parts of WLoader setup stands for "Wyse Device Manager" and it is a software package from Dell which enables remote management of those devices. You can see it in action here: https://www.youtube.com/watch?v=qxhqHKPX4vQ&ab_channel=BrucePless.
So it seems that there is a way to make those devices to boot from a custom network source without connecting keyboard/display. You would need to connect the device to your local network, set up a fake WDM server and maybe add some custom options to your DHCP server.
I attach them here for a reference.
@bodhi It seems that WDM used in various parts of WLoader setup stands for "Wyse Device Manager" and it is a software package from Dell which enables remote management of those devices. You can see it in action here: https://www.youtube.com/watch?v=qxhqHKPX4vQ&ab_channel=BrucePless.
So it seems that there is a way to make those devices to boot from a custom network source without connecting keyboard/display. You would need to connect the device to your local network, set up a fake WDM server and maybe add some custom options to your DHCP server.
|
Re: Debian on Dell Wyse 3020 May 05, 2024 01:30PM |
Admin Registered: 13 years ago Posts: 18,997 |
@ksuszka,
> I connected my terminal through HDMI grabber and I
> captured various WLoader screenshots in the
> original resolution after the factory reset,
> during and after switching to the linux boot mode,
> with and without bootable usb connected.
>
> I attach them here for a reference.
Nice!
>
> @bodhi It seems that WDM used in various parts of
> WLoader setup stands for "Wyse Device Manager" and
> it is a software package from Dell which enables
> remote management of those devices. You can see it
> in action here:
> https://www.youtube.com/watch?v=qxhqHKPX4vQ&ab_channel=BrucePless.
>
> So it seems that there is a way to make those
> devices to boot from a custom network source
> without connecting keyboard/display. You would
> need to connect the device to your local network,
> set up a fake WDM server and maybe add some custom
> options to your DHCP server.
Good to know! it will come in handy in some circumstances. But now knowing there is a Remote Managment capability, we would also want to set up the router to reject any request to/from that Dell domain :)
=========
On another topic. To do a stress test, I have added this box to my kernel build farm. While it is running gcc to compile the kernel code, the CPU was maxed out at 100% continuously for a couple hours, and used the network to send and receive compilation jobs. All went well! so I think it is good for production use.
However, I have not been able to figure out the issue with "smp_twd: clock not found -2". It looks like everything was set up OK. But it seems there is no implemented specific clock source for this MMP3 SoC.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I connected my terminal through HDMI grabber and I
> captured various WLoader screenshots in the
> original resolution after the factory reset,
> during and after switching to the linux boot mode,
> with and without bootable usb connected.
>
> I attach them here for a reference.
Nice!
>
> @bodhi It seems that WDM used in various parts of
> WLoader setup stands for "Wyse Device Manager" and
> it is a software package from Dell which enables
> remote management of those devices. You can see it
> in action here:
> https://www.youtube.com/watch?v=qxhqHKPX4vQ&ab_channel=BrucePless.
>
> So it seems that there is a way to make those
> devices to boot from a custom network source
> without connecting keyboard/display. You would
> need to connect the device to your local network,
> set up a fake WDM server and maybe add some custom
> options to your DHCP server.
Good to know! it will come in handy in some circumstances. But now knowing there is a Remote Managment capability, we would also want to set up the router to reject any request to/from that Dell domain :)
=========
On another topic. To do a stress test, I have added this box to my kernel build farm. While it is running gcc to compile the kernel code, the CPU was maxed out at 100% continuously for a couple hours, and used the network to send and receive compilation jobs. All went well! so I think it is good for production use.
However, I have not been able to figure out the issue with "smp_twd: clock not found -2". It looks like everything was set up OK. But it seems there is no implemented specific clock source for this MMP3 SoC.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 May 05, 2024 07:20PM |
Admin Registered: 13 years ago Posts: 18,997 |
bodhi Wrote:
I spoke too soon :) I could crash this box with just a simple hearbeat LED. Looks like it's related to the TWD timer.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
> All went well! so I think it is
> good for production use.
>
> However, I have not been able to figure out the
> issue with "smp_twd: clock not found -2". It looks
> like everything was set up OK. But it seems there
> is no implemented specific clock source for this
> MMP3 SoC.
I spoke too soon :) I could crash this box with just a simple hearbeat LED. Looks like it's related to the TWD timer.
root@Wyse3020:~# echo heartbeat > /sys/class/leds/green\:status/trigger
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on Dell Wyse 3020 May 06, 2024 10:20AM |
Registered: 9 months ago Posts: 38 |
@bodhi I'm not sure if this info may be of any use to you, but I tried (with a minor success) to repeat steps @karrelax performed here https://forum.doozan.com/read.php?2,63499,132998#msg-132998.
I downloaded Dell_Wyse_USB_Imaging_Tool_2.1.4 from this site https://technicalhelp.de/downloads/ (unfortunatelly, the official Wyse website is down for good). I used it to create the "recovery" usb for this terminal. I tried newer versions but they didn't work as Dell dropped support for 3020 terminal in v3 of their imaging tool.
I booted the terminal from that recovery usb and it booted into ASCII based recovery tool. The screen was extremely glitched, but it was displaying something. It created a boot log file on the usb stick very similar to the one pasted in @karrelax's post. I attach mine here. In this log file there is some info about frame buffer configuration but I know very little about this.
I downloaded Dell_Wyse_USB_Imaging_Tool_2.1.4 from this site https://technicalhelp.de/downloads/ (unfortunatelly, the official Wyse website is down for good). I used it to create the "recovery" usb for this terminal. I tried newer versions but they didn't work as Dell dropped support for 3020 terminal in v3 of their imaging tool.
I booted the terminal from that recovery usb and it booted into ASCII based recovery tool. The screen was extremely glitched, but it was displaying something. It created a boot log file on the usb stick very similar to the one pasted in @karrelax's post. I attach mine here. In this log file there is some info about frame buffer configuration but I know very little about this.
|
Re: Debian on Dell Wyse 3020 May 06, 2024 01:43PM |
Admin Registered: 13 years ago Posts: 18,997 |
@ksuszka,
Thanks!
I'm going to try the latest DTS in Lubomir's staging tree.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/06/2024 02:43PM by bodhi.
Thanks!
I'm going to try the latest DTS in Lubomir's staging tree.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/06/2024 02:43PM by bodhi.
