Debian on Dell Wyse T10 / T50

wildhem,

For Dell Wyse T10 / T50, everything should work, except the display.

Thanks for reminding, I forgot to add this box and HP T5335z to the the Installation list in the release thread..

> terminal but it probably has a blocked bios

Are you sure your box has a BIOS? this box uses U-Boot as loot loader. If it has a BIOS then it is a different Thin Client (Intel x86 base).

> is it possible to revive
> it somehow?

Yes, assuming you have the T10 / T50, connect serial console and it should be possible to install Debian on USB.

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

Thank you for your work and instructions on how to do it.
However, I have a problem with the installation.
I connected the adapter on the ch340g chip and the only thing I get from the console are the following characters:

root@acab-VirtualBox:/media/acab/rootfs/boot# picocom -b 115200 /dev/ttyUSB0
picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready

123ABCcd
12345

Attempts to send commands in your hp t5335z manual do not bring any results despite the rootfs flash drive.

wildhem,

> Type [C-a] [C-h] to see available commands
> Terminal ready
>
> 123ABCcd
> 12345

It looks like your serial connection did not work. Check the GND wire. And try hitting the Enter/Return key several times to see if you get any output.

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

Im sure of the good gnd connection and further the serial console is not working. I also tried to connect the gnd to a different place on the board and then the same.
Maybe there is some other installation method, such as read spi memory, edit and save with programmer?



Edited 1 time(s). Last edit at 06/28/2021 07:25AM by wildhem.

wildhem,

Usually when you see something garbage characters printed out like above, it might be the baud rate, or some partity settings are wrong.

Try specifying all paramaters explicitly like this:

picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0

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

I bought CP2102 usb to uart and still same output (before i use ch340g)

hp@debian:~$ sudo picocom --b 115200 --f n --p n --d 8 /dev/ttyUSB0
[sudo] hasło użytkownika hp: 
picocom v3.1

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv -E
imap is        : 
omap is        : 
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is  : not set
exit is        : no

Type [C-a] [C-h] to see available commands
Terminal ready

123ABCcd
12345

But now something bad is happening to my device. after connecting the power, the orange led lights up for 4 seconds, the terminal spits out these garbage characters in the console, then the device goes out and I cannot turn it on, it does not respond to the power button. I have two of these terminals and it's the same on both.
I used to be able to run them both, but I needed desktop login credentials that I didn't have.

wildhem,

I hope you only connect 3 wires: GND, TX, and RX?

Let it sit unplugged for a while (hours) and try power up again.

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

bodhi,
yes, I only connected these. I left the terminal disconnected from the power supply and took out the battery and the the device starts up.

It has the system version 8.1_027. Maybe there is some way to update the official system or restore factory settings and maybe then the terminal will start communicating?

wildhem,

> yes, I only connected these. I left the terminal
> disconnected from the power supply and took out
> the battery and the the device starts up.

So now it's booting normally again?

>
> It has the system version 8.1_027. Maybe there is
> some way to update the official system or restore
> factory settings and maybe then the terminal will
> start communicating?

I am not familiar with the restore procedure on this box. I had bought a used box a long time go, but have not tried to do any thing with it! all the testing was done by Koen.

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

bodhi,
>
> So now it's booting normally again?
>

yes, it boots up the system but the console continues to show the same

> I am not familiar with the restore procedure on
> this box. I had bought a used box a long time go,
> but have not tried to do any thing with it! all
> the testing was done by Koen.

I have two such devices and I would like to use them. I would be grateful for any tips that may help me.

these are the basic versions without flash memory, the only memory I see are 2 spi memory chips, one of them (winbond 25q64fvsig) I made a dump with the ch341a programmer, the other (mxic) marked as "ec socket" is protected against reading from the outside.



Edited 1 time(s). Last edit at 07/18/2021 05:05AM by wildhem.

wildhem,

> these are the basic versions without flash memory,
> the only memory I see are 2 spi memory chips, one
> of them (winbond 25q64fvsig) I made a dump with
> the ch341a programmer, the other (mxic) marked as
> "ec socket" is protected against reading from the
> outside.

Yes, this box has only SPI flash (no NAND). If you can log into stock, then post dmesg here. It shows which SPI chip driver was used. I'd expect it to be the same as Koen's box.

And regarding serial console, here is Koen's summary in this thread (booted successfully into Debian using Recovery method):

https://forum.doozan.com/read.php?2,63499,63914#msg-63914

I have not reread the thread, but looks like Koen had the similar problem with serial console.

If Koen and you can only see output to the Display, but not serial console, then I'd say that this stock u-boot version intentionally turned it of. They probably want to avoid interruption so all the stdout and stderr only routed to the LCD.

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

Finally, I was able to run the terminal with the admin account, the password for which I found in the spi memory dump file. Then I updated the system to the latest version by replacing the initial 7501 KB of the dump file with DOVE_boot.i2d from the OS_Web_v8.6_206_3010_T10_ENG package
However, I still can't start the serial console or ssh. The DEL and P keys at startup also have no effect.
I could probably edit the wloader.cfg file with a hex editor, there are boot commands for the device in it.

Probably the booted system is first unpacked to RAM and only started on the device. Below is the beginning of the event log from the ThinOS system:

System Start Date: 2021/08/24 Tuesday DST
System Version: 8.6_206
Characteristics: FilesystemSecurity
CPU Version: Marvell PJ4 v7 Processor-wmmx rev5 (v7l)
00: 00: 00.000 Embedded Controller Version: 3.04
17: 59: 05.000 CESA: driver register OK.
18: 59: 05.090 PKG: extracting rom.pkg V1.1 ...
18: 59: 05.348 rom.pkg: 280 files extracted

Edited 1 time(s). Last edit at 08/24/2021 04:15PM by wildhem.

Editing boot commands in the spi dump file had no effect.
I think if we compiled the uboot for this board and replaced it in the spi memory chip marked as EC, we would get a fully manageable device.
Currently, for the T10 model it is not possible to boot into debian.

Hello, I have some Tx0 terminals, I previously had a version of OS Citrix, I got a WYSE version on a Russian site, but the MAC address is in the file that goes in the 8mb SPI memory, causing network problems. I'm not a programmer, I just know a little bit of electronica, would I be able to change this address in the file??

ps: sorry for the english , made in google translate.

marcio,

> the MAC address is in the file
> that goes in the 8mb SPI memory, causing network
> problems.

I assume this Wyse Thin Client is an ARM box. There are some Wyse that are x86 base (in this case I cannot help you).

Usually, the MAC address can be modified using serial console. So connect serial console and see if you can interrupt u-boot. If this is an ARM box then there is a pretty good chance you can change the MAC address.

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

I would still like to run debian on this terminal. Could someone send me a spi memory dump from a terminal that managed to run a different system than the official one?

Hello all.

I, like others in this thread, have acquired a number of T50s WYSE thin clients, and would like to run something more modern than their Ubuntu 10.04. I'm very grateful for the treasure trove of information in this thread, and the work done by others to try to support this hardware.

Unfortunately, I'm still having issues, and I fear that I'm missing a key piece somewhere that I haven't realized on my own. I'm going to share the steps that I'm currently using, in the hopes that bodhi or Koen can point me in the right direction (and also in order to document what I've tried for future readers).

mkfs.ext3 /dev/sdb1
mkdir /mnt/sda2
mkdir /mnt/sdb1
mount /dev/sda2 /mnt/sda2
mount /dev/sdb1 /mnt/sdb1
cd /mnt/sdb1

# This is the tar downloaded from the releases page
tar -xjf Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2

cd boot
cp -a zImage-5.2.9-mvebu-tld-1 zImage.fdt
cat dts/dove-wyse-t50.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.2.9-mvebu-tld-1 -d zImage.fdt uImage

cp uImage /mnt/sda2
cp uInitrd /mnt/sda2

I then rebooted, entered WLoader, changed the recovery boot params to replace `root=/dev/ram0 rw ramdisk_size=136314880` with `root=/dev/sdb1` and add `clcd.lcd0_clk=3 clcd.lcd1_clk=1 vmalloc=384M` and remove `pm_disable titan`. (As had been mentioned working previously in this thread.) (I'm using the slightly older 5.2.9 rootfs in an attempt to minimize variables.)

Booting the machine then drops me to a black screen. Nothing appears on the connected monitor, ethernet doesn't appear to be working, I don't get anything over serial except for "Uncompressing Linux... done, booting the kernel." I suspect that there's some fundamental issue with my rootfs that is causing the boot to fail before transferring to Linux. But without any u-Boot output, and since I followed the commands posted here as closely as possible, I can't guess what the issue is.

Thanks for any suggestions for further debug steps.

MatthiasPortzel,

> I then rebooted, entered WLoader, changed the
> recovery boot params to replace `root=/dev/ram0 rw
> ramdisk_size=136314880` with `root=/dev/sdb1` and
> add `clcd.lcd0_clk=3 clcd.lcd1_clk=1 vmalloc=384M`
> and remove `pm_disable titan`. (As had been
> mentioned working previously in this thread.) (I'm
> using the slightly older 5.2.9 rootfs in an
> attempt to minimize variables.)
>
> Booting the machine then drops me to a black
> screen. Nothing appears on the connected monitor,

The new kernel does not have support for this display (at least not yet). You would have to rely on serial console.

> ethernet doesn't appear to be working, I don't get
> anything over serial except for "Uncompressing
> Linux... done, booting the kernel." I suspect that
> there's some fundamental issue with my rootfs that
> is causing the boot to fail before transferring to
> Linux. But without any u-Boot output, and since I
> followed the commands posted here as closely as
> possible, I can't guess what the issue is.

I recall there was some problem with serial console reported by Koen somewhere in this thread, but could not remember exactly.

I have not yet booted my Wyse T50. I bought a used box during Koen's testing, but since Koen did a great job, I did not bother try booting it myself.

I would suggest going back to the beginning of this thread and browse the posts to see if you can find this issue. If you cannot, I'd boot up my box when I have chance.

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

Koen's post about booting successfiully starts here:

https://forum.doozan.com/read.php?2,63499,63914#msg-63914

Now I realize that I forgot to add this to the main installation thread! Will do that shortly.

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

Thanks for the reply. Yes, that post was one of my primary resources, and was extremely helpful. The commands I posted above are my attempted at implementing those steps. I was hoping you would be able to see an obvious deviation at the root of my problem.

While I have some experience as an admin of Linux servers, I'm new to tinkering with embedded Linux. So I have a couple of ideas, but without any error messages, no clear direction.

MatthiasPortzel,

> While I have some experience as an admin of Linux
> servers, I'm new to tinkering with embedded Linux.
> So I have a couple of ideas, but without any error
> messages, no clear direction.

Sure, just post the serial console log here. And we'll go from there, don't describe the problem, the best description is the log.

You already mentioned you have created the USB rootfs to trigger the Recovery process for this box, as Koen showed. So we know what's in the USB rootfs.

There is no input/output for serial console during u-boot booting, but there will be output during kernel booting. So wait a bit to see any output after the kernel is decompressed.

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

The instruction given by Koen does not work for me on Wyse T10 - I can not enter the wloader settings or enable the root account.
There is no ubuntu in this device, but some wyse system that fits in 8 megabyte spi memory and probably unpacks to ram on boot, hence no possibility to get to the ssh console.
I also tried using the bootloader from the HP T5335z but the device won't boot.
The next thing I want to check is the barebox bootloader. It has solidrun cubox support for the dove platform. I have already done a test build for my wyse t10 but I am currently unable to program the spi chip.
The solution for me could also be a bootloader dump from wyse t50 from the spi memory chip.

Hello everybody,

I am also having troubles with my T10D (wyse 3020).
It comes with ThinOS, but no single app is available on the original system, it just waits for the server to provide everything.

My steps:

I have a monitor connected, and a USB+serial adaptor, so I can see the serial output (and hopefully will be able to log form there at some point).

I tried the rootfs with debian from this site, but also the fedora minial from https://linux-mmp.docs.kernel.org/dell-wyse-3020.html
Nothing works.

I used the USB Firmware updater from wyse, but not the last version, the 2.0 version, which gives also the ARM possibility. With this one, a large partition FAT is created on the USB and includes some uInitrd and uImage, that will load and start a Ubuntu 12 on the RAM, but then it gives no terminal whatsoever, it just provides the menu to copy system to USB or USB to system (I also tried in this direction without success: the "load image from USB to system" needs he xml or rsp, that I can fake, but then it needs a complete image that I never managed to work).

I tried changing the uImage, the uInitrd, tried modifiing the wloader.cfg to point the root to an ad-hoc created partition with the debian from this site on it, but nothing works. Kernel Panic everytime.

Anyone have any tip of us, poor noobies trying to play with a small, old device ? :) thanks!

karrelax Wrote:
-------------------------------------------------------
> Hello everybody,
>
> I am also having troubles with my T10D (wyse
> 3020).
> It comes with ThinOS, but no single app is
> available on the original system, it just waits
> for the server to provide everything.
>
> My steps:
>
> I have a monitor connected, and a USB+serial
> adaptor, so I can see the serial output (and
> hopefully will be able to log form there at some
> point).
>
> I tried the rootfs with debian from this site,

Power up, on serial console, enter the envs to boot the rootfs. Boot it. And post the entire log here.

> but
> also the fedora minial from
> https://linux-mmp.docs.kernel.org/dell-wyse-3020.html
> Nothing works.
>
> I used the USB Firmware updater from wyse, but not
> the last version, the 2.0 version, which gives
> also the ARM possibility. With this one, a large
> partition FAT is created on the USB and includes
> some uInitrd and uImage, that will load and start
> a Ubuntu 12 on the RAM, but then it gives no
> terminal whatsoever, it just provides the menu to
> copy system to USB or USB to system (I also tried
> in this direction without success: the "load image
> from USB to system" needs he xml or rsp, that I
> can fake, but then it needs a complete image that
> I never managed to work).
>
> I tried changing the uImage, the uInitrd, tried
> modifiing the wloader.cfg to point the root to an
> ad-hoc created partition with the debian from this
> site on it, but nothing works. Kernel Panic
> everytime.
>
> Anyone have any tip of us, poor noobies trying to
> play with a small, old device ? :) thanks!

If you followed Koen steps, it should boot to Debian. But it's been a long time, I can no longer recall the details.

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

Dear Bodhi,
thanks for replying. I know it is a very old thread...

Loading the system as-is (thinOS) will just stop after the console shows this:

�}[z��_�����[@�*** 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

If I use the Dell firmware upgrade tool (2.0) I can load the menu that asks to either "Pull an Image from device to USB key" or "Push an Image to device from USB key", making use of the wloader.cfg:

"<TX0D_START>

kernel=./kernel/TX0D/uImage
initrd=./initrd/TX0D/uInitrd
param="root=/dev/ram0 usb0Mode=host usb1Mode=host video=dovefb:lcd0:1024x600-16@60-edid,lcd1:1024x768-16@60-edid clcd.lcd0_enable=1 clcd.lcd1_enable=1 clcd.lcd0_clk=3 clcd.lcd1_clk=1 vmalloc=384M"

<TX0D_END>"

The serial USB shows this:

<5>Linux version 3.0.31-1-dajia (root@ubuntu-12.04) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #131 SMP PREEMPT Mon Oct 14 19:44:17 PDT 2013
CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Ariel
Memory policy: ECC disabled, Data cache writealloc
<7>On node 0 totalpages: 523776
<7>free_area_init_node: node 0, pgdat c08a2fa0, node_mem_map c08fc000
<7>  Normal zone: 1728 pages used for memmap
<7>  Normal zone: 0 pages reserved
<7>  Normal zone: 219456 pages, LIFO batch:31
<7>  HighMem zone: 2366 pages used for memmap
<7>  HighMem zone: 300226 pages, LIFO batch:31
<6>PERCPU: Embedded 7 pages/cpu @c190b000 s7648 r8192 d12832 u32768
<7>pcpu-alloc: s7648 r8192 d12832 u32768 alloc=8*4096
<7>pcpu-alloc: [0] 0 [0] 1 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 519682
<5>Kernel command line: root=/dev/ram0  usb0Mode=host usb1Mode=host video=dovefb ramdisk_size=136314880
<6>PID hash table entries: 4096 (order: 2, 16384 bytes)
<6>Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
<6>Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>Memory: 2030MB 16MB = 2046MB total
<5>Memory: 2022952k/2022952k available, 73176k reserved, 1193984K highmem
<5>Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xf6800000 - 0xfe000000   ( 120 MB)
    lowmem  : 0xc0000000 - 0xf6000000   ( 864 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc0050000   ( 288 kB)
      .text : 0xc0050000 - 0xc0861658   (8262 kB)
      .data : 0xc0862000 - 0xc08ac758   ( 298 kB)
       .bss : 0xc08ac77c - 0xc08fb650   ( 316 kB)
<6>Preemptible hierarchical RCU implementation.
<6>NR_IRQS:405 nr_irqs:469 469
<6>sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
<6>Console: colour dummy device 80x30

If I change the uImage or uInitrd the system fails to boot. Not sure what I am doing wrong.

I only managed to do this with the USB prepared from the Dell Firmware software. Any other alternative does not boot.

Am I missing something fundamental here?

Recovery method needs to save the uImage and uInitrd to sda2, but I have no way to do this. I dont have any terminal in the system, nor via ttyUSB0 .

Oh, I forgot, the kernelmsg.log file created in the USB when loading such DELLWYSE thing:

0.775909] We do not need to touch APMU_LCD, just enable pll3
[    0.775909] calling our customized mmp3_pll3 enable function
[    0.775939] Desired clk_rate in Hz = 85506626
[    0.775970] Inside mmp3_clk_pll3_enable_parallel
[    0.776000] Calculated pclk from pll3 will be 84499993
[    0.776000] REFDIV=3
[    0.776031] FBDIV=195
[    0.776031] CLK_INT_DIV=10
[    0.777069] lcd_pn1_clk_enable PMUA_DISPLAY1 = 0x11b, clk from pll3
[    0.777099] Dynamic resolution change for fbi->id: 0
[    0.777099] HActive: 1360
[    0.777130] VActive: 768
[    0.777130] Hvirtual: 1360
[    0.777160] Vvirtual: 768
[    0.777160] bits_per_pixel: 32
[    0.777191] red.offset: 16
[    0.777191] red.length: 8
[    0.777221] green.offset: 8
[    0.777221] green.length: 8
[    0.777252] blue.offset: 0
[    0.777282] blue.length: 8
[    0.777282] transp.offset: 0
[    0.777313] transp.length: 8
[    0.777313] xres_virtual: 1360
[    0.777343] yres_virtual: 768
[    0.777343] xoffset: 0
[    0.777374] yoffset: 0
[    0.777374] bpp: 32
[    0.777404] nonstd: 7340032
[    0.777404] activate: 0
[    0.777435] height: 0
[    0.777435] width: 0
[    0.777465] accel_flags: 0
[    0.777465] pixclock: 11695
[    0.777496] left_margin: 256
[    0.777496] right_margin: 64
[    0.777526] upper_margin: 18
[    0.777526] lower_margin: 3
[    0.777557] hsync_len: 112
[    0.777557] vsync_len: 6
[    0.777587] sync: 3
[    0.777587] vmode: 0
[    0.777618] rotate: 0
[    0.777618] 
[    0.777618] set_clock_divider sclk_src 85506626 sclk_div 0xe000000a
[    0.778137] pxa168fb_open GFX layer, fbi 0 opened 0 times ----
[    0.778259] Interface is parallel
[    0.778289] In the calculate_lcd_sclk func for pclk 85506626
[    0.778289] pixel clock is 85506626 Hz
[    0.778289] **Choice Ch7033 register -- Frequence = ( 85506 )
[    0.993560] start to reset ch7033 ...
[    1.000244] ***Frank set_clock_divider/707 fbi->clk=c086f8dc fclk->name=lcd1
[    1.000244] ***Frank lcd_pn1_clk_disable/1708 clk=c086f8dc clk->name=lcd1
[    1.001251] lcd_pn1_clk_disable PMUA_DISPLAY1 = 0x11b, clk from pll3
[    1.001281] Returning rate 85506626 from function mmp3_clk_pll3_round_rate
[    1.001281] We will not round rate or do anything here...
[    1.001281] ***Frank lcd_clk_setrate/1750 clk=c086f8dc clk->name=lcd1
[    1.001312] Setting pixclk rate as a pll3 desired rate in its clock...
[    1.001312] ***Frank lcd_pn1_clk_enable/1643 clk=c086f8dc clk->name=lcd1
[    1.001312] We do not need to touch APMU_LCD, just enable pll3
[    1.001342] calling our customized mmp3_pll3 enable function
[    1.001342] Desired clk_rate in Hz = 85506626
[    1.001342] Inside mmp3_clk_pll3_enable_parallel
[    1.001342] Calculated pclk from pll3 will be 84499993
[    1.001373] REFDIV=3
[    1.001373] FBDIV=195
[    1.001373] CLK_INT_DIV=10
[    1.002380] lcd_pn1_clk_enable PMUA_DISPLAY1 = 0x11b, clk from pll3
[    1.002410] Dynamic resolution change for fbi->id: 0
[    1.002410] HActive: 1360
[    1.002410] VActive: 768
[    1.002441] Hvirtual: 1360
[    1.002441] Vvirtual: 768
[    1.002441] bits_per_pixel: 32
[    1.002441] red.offset: 16
[    1.002441] red.length: 8
[    1.002471] green.offset: 8
[    1.002471] green.length: 8
[    1.002471] blue.offset: 0
[    1.002471] blue.length: 8
[    1.002471] transp.offset: 0
[    1.002502] transp.length: 8
[    1.002502] xres_virtual: 1360
[    1.002502] yres_virtual: 768
[    1.002502] xoffset: 0
[    1.002502] yoffset: 0
[    1.002502] bpp: 32
[    1.002532] nonstd: 7340032
[    1.002532] activate: 0
[    1.002532] height: 0
[    1.002532] width: 0
[    1.002532] accel_flags: 0
[    1.002563] pixclock: 11695
[    1.002563] left_margin: 256
[    1.002563] right_margin: 64
[    1.002563] upper_margin: 18
[    1.002563] lower_margin: 3
[    1.002593] hsync_len: 112
[    1.002593] vsync_len: 6
[    1.002593] sync: 3
[    1.002593] vmode: 0
[    1.002593] rotate: 0
[    1.002593] 
[    1.002624] set_clock_divider sclk_src 85506626 sclk_div 0xe000000a
[    1.028961] Console: switching to colour frame buffer device 170x48
[    1.146667] pxa168fb: frame buffer device was loaded to /dev/fb0 <GFX Layer>.
[    1.161499] arm_vmregion_alloc: allocation too big (requested 0xfd3000)
[    1.166595] ---------FB DMA buffer phy addr : 29000000
[    1.176818] fb1: sclk_src 0 clk_get_rate = 26000000
[    1.178497] vdma enabled, sram_paddr 0xd1027800 sram_size 0x7800
[    1.180511] pxa168fb: frame buffer device was loaded to /dev/fb1 <TV GFX Layer>.
[    1.183074] uvesafb: failed to execute /sbin/v86d
[    1.184814] uvesafb: make sure that the v86d helper is installed and executable
[    1.186706] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)
[    1.188568] uvesafb: vbe_init() failed with -22
[    1.190643] uvesafb: probe of uvesafb.0 failed with error -22
[    1.372070] pxa2xx-uart.2: ttyS2 at MMIO 0xd4018000 (irq = 56) is a STUART
[    1.479248] mmp3 system setting module was loaded
[    1.481536] [drm] Initialized drm 1.1.0 20060810
[    1.484558] [drm] Initialized vivante 1.0.0 20120216 on minor 0
[    1.492797] brd: module loaded
[    1.498046] loop: module loaded
[    1.500427] android_pmem android_pmem.0: pmem: 1 1 init
[    1.503387] android_pmem android_pmem.1: pmem_adsp: 0 0 init
[    1.506286] android_pmem android_pmem.2: pmem_wc: 0 1 init
[    1.510070] m25p80 spi2.255: found w25q32, expected m25p80
[    1.512481] m25p80 spi2.255: w25q32 (4096 Kbytes)
[    1.514892] Creating 1 MTD partitions on "spi_flash":
[    1.517425] 0x000000000000-0x000000400000 : "bootloader(spi)"
[    1.521148] usbcore: registered new interface driver asix
[    1.523895] usbcore: registered new interface driver cdc_ether
[    1.526702] usbcore: registered new interface driver cdc_eem
[    1.529418] usbcore: registered new interface driver smsc75xx
[    1.532196] usbcore: registered new interface driver net1080
[    1.535003] usbcore: registered new interface driver rndis_host
[    1.537780] usbcore: registered new interface driver cdc_subset
[    1.540557] usbcore: registered new interface driver zaurus
[    1.543334] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[    1.546081] cdc_ncm: 04-Aug-2011
[    1.548950] usbcore: registered new interface driver cdc_ncm
[    1.553924] Init usb phy!!!
[    1.558135] pxa-otg pxa-otg: successful probe OTG device without clock gating.
[    1.561248] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.564575] pxa-ehci pxa-u2oehci: successful find EHCI device with regs 0xf686a140 irq 76 working in OTG mode
[    1.567901] mmp3_hsic_phy_init !!!
[    1.721282] pxa-ehci mmp3-hsic: Marvell EHCI
[    1.724578] pxa-ehci mmp3-hsic: new USB bus registered, assigned bus number 1
[    1.752105] pxa-ehci mmp3-hsic: irq 54, io mem 0xf0001800
[    1.767700] pxa-ehci mmp3-hsic: USB 2.0 started, EHCI 1.00
[    1.771820] hub 1-0:1.0: USB hub found
[    1.774993] hub 1-0:1.0: 1 port detected
[    1.778564] pxa-ehci mmp3-hsic: successful find EHCI device with regs 0xf686e140 irq 54 working in Host mode
[    1.782012] usbcore: registered new interface driver cdc_acm
[    1.785308] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    1.788604] Initializing USB Mass Storage driver...
[    1.792022] usbcore: registered new interface driver usb-storage
[    1.795288] USB Mass Storage support registered.
[    1.798797] pxa-u2o pxa-u2o: successful probe UDC device with clock gating.
[    1.802307] g_mass_storage gadget: controller 'mv_udc' not recognized
[    1.805755] g_mass_storage gadget: Mass Storage Function, version: 2009/09/11
[    1.809112] g_mass_storage gadget: Number of LUNs=1
[    1.812377]  lun0: LUN: removable file: (no medium)
[    1.815704] g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11
[    1.819000] g_mass_storage gadget: userspace failed to provide iSerialNumber
[    1.822387] g_mass_storage gadget: g_mass_storage ready
[    1.825805] eneec_probe with name = KB39XX, addr = 0x58, irq = 273
[    1.830963] i2c-core: driver [eneec] using legacy suspend method
[    1.834350] i2c-core: driver [eneec] using legacy resume method
[    1.837738] eneec_spi_init
[    1.841247] eneec_spi_probe with modalias = eneec_spi, irq = 273
[    1.844818] Drain data : 0x00aa
[    1.848358] Drain data : 0x0000
[    1.852020] IRQ 273 requested
[    1.856506] mousedev: PS/2 mouse device common for all mice
[    1.861724] mmp-rtc mmp-rtc: warning: initializing default clockdivider/trim value
[    1.865509] scan code fa
[    1.869110] scan code aa
[    1.870025] using rtc device, mmp-rtc, for alarms
[    1.870086] mmp-rtc mmp-rtc: rtc core: registered mmp-rtc as rtc0
[    1.882141] mmp_rtc_probe End!!!
[    1.885925] i2c /dev entries driver
[    1.891265] Linux media interface: v0.10
[    1.894958] Linux video capture interface: v2.00
[    1.899078] path 0 video layer : request vdma fail
[    1.903137] pxa168_v4l2_ovly: registered and initialized video1: minor num 0 [v4l2]
[    1.906829] path 1 video layer : request vdma fail
[    1.910919] pxa168_v4l2_ovly: registered and initialized video2: minor num 1 [v4l2]
[    1.919128] device-mapper: uevent: version 1.0.3
[    1.923217] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com
[    1.927490] cpuidle: using governor ladder
[    1.931335] cpuidle: using governor menu
[    1.934997] sdhci: Secure Digital Host Controller Interface driver
[    1.938629] sdhci: Copyright(c) Pierre Ossman
[    1.942718] mmc0: no vmmc regulator found
[    1.946380] Registered led device: mmc0::
[    1.946563] mmc0: SDHCI controller on sdhci-pxa.2 [sdhci-pxa.2] using ADMA
[    1.950286] mmc1: no vmmc regulator found
[    1.953826] Registered led device: mmc1::
[    1.953979] mmc1: SDHCI controller on sdhci-pxa.0 [sdhci-pxa.0] using ADMA
[    1.957824] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.961669] usbcore: registered new interface driver usbhid
[    1.965209] usbhid: USB HID core driver
[    1.969177] usbcore: registered new interface driver snd-usb-audio
[    1.973907] paul init and register ce156 i2c driver:
[    1.977386] CE156: register i2c driver successfully
[    1.981201] codec register ce156.2-0030
[    1.984802] codec num_dai 1
[    1.991119] scan code fa
[    1.994598] scan code ab
[    1.998107] scan code 41
[    2.002197] usb 1-1: new high speed USB device number 2 using pxa-ehci
[    2.010620] scan code fa
[    2.015930] scan code fa
[    2.020935] scan code fa
[    2.027770] scan code fa
[    2.032562] scan code fa
[    2.035980] input: AT Translated Set 2 keyboard as /devices/platform/pxa2xx-spi.3/spi_master/spi3/spi3.255/serio0/input/input0
[    2.058715] ce156 reg write finished
[    2.061889] SND_SOC_BIAS_PREPARE
[    2.093933] success set the ce156 reg!
[    2.097198] ce156: initial ok
[    2.100677]  audio subsystem power on (A stepping) 0x00001806
[    2.139282] mmc0: new high speed MMC card at address 0001
[    2.142456] mmc0: ios: 50000000 Hz, 8 bit width
[    2.146362] mmcblk0: mmc0:0001 H4G2a 3.64 GiB 
[    2.149932] mmcblk0boot0: mmc0:0001 H4G2a partition 1 4.00 MiB
[    2.153564] mmcblk0boot1: mmc0:0001 H4G2a partition 2 4.00 MiB
[    2.159606] hub 1-1:1.0: USB hub found
[    2.162933]  mmcblk0: p1 p2 p3 p4
[    2.167602] hub 1-1:1.0: 3 ports detected
[    2.182708]  mmcblk0boot1: unknown partition table
[    2.196899]  mmcblk0boot0: unknown partition table
[    2.432250] asoc: CE156 <-> mmp3-sspa-dai.0 mapping ok
[    2.437255] CE156: register i2c device successfully
[    2.440216] ALSA device list:
[    2.443298]   #0: mmp3 asoc
[    2.446319] Netfilter messages via NETLINK v0.30.
[    2.449401] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    2.452880] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[    2.456054] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[    2.459106] usb 1-1.1: new high speed USB device number 3 using pxa-ehci
[    2.462707] IPv4 over IPv4 tunneling driver
[    2.466461] ip_tables: (C) 2000-2006 Netfilter Core Team
[    2.469696] TCP cubic registered
[    2.473052] NET: Registered protocol family 10
[    2.476776] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    2.479705] IPv6 over IPv4 tunneling driver
[    2.483154] NET: Registered protocol family 17
[    2.486175] NET: Registered protocol family 15
[    2.489379] L2TP core driver, V2.0
[    2.492309] lib80211: common routines for IEEE802.11 drivers
[    2.495330] lib80211_crypt: registered algorithm 'NULL'
[    2.495361] Registering the dns_resolver key type
[    2.498413] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[    2.501770] ThumbEE CPU extension supported.
[    2.505035] PJ4 iWMMXt coprocessor enabled.
[    2.508270] mmp PM-hotplug init function
[    2.515258] hdmi_probe hpd pull out
[    2.519104] mmp-rtc mmp-rtc: setting system clock to 2022-09-25 13:52:28 UTC (1664113948)
[    2.522918]  alarm_dev_init, rtc power up : 0, alarm time: 0
[    2.526519] RAMDISK: gzip image found at block 0
[    2.587738] scsi0 : usb-storage 1-1.1:1.0
[    2.674377] usb 1-1.2: new high speed USB device number 4 using pxa-ehci
[    2.795989] smsc75xx v1.0.0
[    2.875671] smsc75xx 1-1.2:1.0: eth0: register 'smsc75xx' at usb-mv ehci-1.2, smsc75xx USB 2.0 Gigabit Ethernet, 00:80:64:ea:5c:2f
[    3.564727] pxa-otg pxa-otg: change from state undefined to a_idle
[    3.568298] pxa-otg pxa-otg: change from state a_idle to a_wait_vrise
[    3.571868] pxa-otg pxa-otg: change from state a_wait_vrise to a_wait_bcon
[    3.575500] pxa-otg pxa-otg: start host
[    3.578948] pxa-ehci pxa-u2oehci: Marvell EHCI
[    3.584930] pxa-ehci pxa-u2oehci: new USB bus registered, assigned bus number 2
[    3.589996] scsi 0:0:0:0: Direct-Access     Generic  Ultra HS-COMBO   2.01 PQ: 0 ANSI: 0
[    3.596832] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    3.619293] pxa-ehci pxa-u2oehci: irq 76, io mem 0xd4207000
[    3.634887] pxa-ehci pxa-u2oehci: USB 2.0 started, EHCI 1.00
[    3.639465] hub 2-0:1.0: USB hub found
[    3.643249] hub 2-0:1.0: 1 port detected
[    3.647369] pxa-otg pxa-otg: change from state a_wait_bcon to a_host
[    3.971160] usb 2-1: new high speed USB device number 2 using pxa-ehci
[    4.130157] hub 2-1:1.0: USB hub found
[    4.135284] hub 2-1:1.0: 4 ports detected
[    4.346069] EXT2-fs (ram0): warning: maximal mount count reached, running e2fsck is recommended
[    4.349731] VFS: Mounted root (ext2 filesystem) on device 1:0.
[    4.353668] devtmpfs: mounted
[    4.357604] Freeing init memory: 288K
[    4.432220] usb 2-1.1: new high speed USB device number 3 using pxa-ehci
[    4.554473] scsi1 : usb-storage 2-1.1:1.0
[    4.635375] usb 2-1.3: new low speed USB device number 4 using pxa-ehci
[    4.761352] input: Kensington      Kensington USB/PS2 Orbit as /devices/platform/pxa-u2oehci/usb2/2-1/2-1.3/2-1.3:1.0/input/input1
[    4.762084] generic-usb 0003:047D:1022.0001: input: USB HID v1.10 Mouse [Kensington      Kensington USB/PS2 Orbit] on usb-mv ehci-1.3/input0
[    5.801910] scsi 1:0:0:0: Direct-Access     SMI      USB DISK         1100 PQ: 0 ANSI: 6
[    5.803833] sd 1:0:0:0: [sdb] 30720000 512-byte logical blocks: (15.7 GB/14.6 GiB)
[    5.804931] sd 1:0:0:0: [sdb] Write Protect is off
[    5.805053] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[    5.806060] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.813354]  sdb: sdb1 sdb2
[    5.817443] sd 1:0:0:0: [sdb] Attached SCSI removable disk

Sorry for spanning that many comments, I comment while testing stuff..

If I create a USB with 2 partitions,
sdb1 , VFAT , with wloader.cfg file on it
sdb2, EXT3, with rootfs on it

Keeping the wloader as it is, it loads the ramdisk and shows the menu onscreen. No terminal in USB serial).
If i take the uImage and uInitrd created from the files in rootfs, making use of mmp3-dell-ariel.dtb obtained from the fedora file in https://linux-mmp.docs.kernel.org/ , then it gives kernel panic.

If I try to use the DELLWYSE files (uInitrd and uImage) but changing the "root" to "Root=/dev/sdb2" paramenter then i get kernel panic but with a new info:
"Not syncing: VFS: Unable to mount root fs on unknown-block(2,9)
Please apperd a correct "root=" boot option; here are the available partitions:
b300 mmcblk0 driver mmcblk
b301 966528 mmcblk0p1
b302 966656 mmcblk0p2
b303 966656 mmcblk0p3
b304 917504 mmcblk0p4

b320 4096 mmcblk0boot1 (driver?)
b310 4096 mmcblk0boot0 (driver?)

karrelax,

It does not seem you've followed what Koen and Bob did. Here is the post in this thread where Koen reported booting into Debian.

https://forum.doozan.com/read.php?2,63499,66134#msg-66134

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

Dear Bodhi,
the problem with the solution of Koen (https://forum.doozan.com/read.php?2,63499,63914#msg-63914) is that he used "recovery", copying the uImage and uInitrd to /dev/sda2...because he already had ubuntu on his system. I have a ThinOs with no apps, so I cannot see files, not drives, I cannot configure ssh nor...anything.

So I am left with no posibility of modifying data from the system.

I can just use the FirmwareupdateUSB (DELLWYSEUSB, fat32 with wloader on it and its own uInitrd and uImage).

Creating a rootfs on a USB does not help, as it will not boot at all. If i use uInitrd and uImage created from it (as koen did) gives me the two files, but then I dont know what to do with them. I tried loading them with the wloader on the fat32 partition, but again, this does not work.

I am feeling more and more dumb. I have the feeling everybody knows how to do it, but me. :(

Hi all,

sorry for the late reply. I've still got my T50 but I have not used it for a while so the best way to get things working is to read through the topic from the start and repeat the same steps. All my notes / info is posted in this thread on the forum, I don't have any other info unfortunately. I've also bought a T10 at some point but I've not touched it at all so I'm not sure if the same procedure would work on that.

Koen