Debian on Dell Wyse T10 / T50
Posted by Koen
|
Re: Debian on Dell Wyse T10 / T50 October 31, 2022 12:55PM |
Registered: 2 years ago Posts: 27 |
Xabby76 Wrote:
-------------------------------------------------------
> Great wildhem.!!!!!
>
> Congratulations.!!!!
>
> Do you have also video output or not.?
> Can you share with us all the process .?
>
> Thanks a lot.!!
using the binwalk tool, I extracted the bootLoader.img file from the official software and got a file with a size of 704 KB, which I increased to the size of my spi memory chip (8 MB) by adding zeros using a hex editor. Then I programmed it through ch341a and after turning on the device, wLoader from Wyse will appear on the screen and at the first start it will ask you to set the mac address and serial number. After this operation we can boot from usb, but we need an additional fat32 partition with linux kernel, initial ramdisk and configuration file wloader.cfg which will refer to the rootfs partition (it can be a separate flash drive)
I used the Bodhi kernel on the first partition of my flash drive, the second is the ext4 filesystem.
I enclose the unpacked wLoader for self-processing.
Unfortunately, the system does not display the screen, but ssh and serial port works.
Edited 1 time(s). Last edit at 10/31/2022 12:58PM by wildhem.
-------------------------------------------------------
> Great wildhem.!!!!!
>
> Congratulations.!!!!
>
> Do you have also video output or not.?
> Can you share with us all the process .?
>
> Thanks a lot.!!
using the binwalk tool, I extracted the bootLoader.img file from the official software and got a file with a size of 704 KB, which I increased to the size of my spi memory chip (8 MB) by adding zeros using a hex editor. Then I programmed it through ch341a and after turning on the device, wLoader from Wyse will appear on the screen and at the first start it will ask you to set the mac address and serial number. After this operation we can boot from usb, but we need an additional fat32 partition with linux kernel, initial ramdisk and configuration file wloader.cfg which will refer to the rootfs partition (it can be a separate flash drive)
I used the Bodhi kernel on the first partition of my flash drive, the second is the ext4 filesystem.
I enclose the unpacked wLoader for self-processing.
Unfortunately, the system does not display the screen, but ssh and serial port works.
Edited 1 time(s). Last edit at 10/31/2022 12:58PM by wildhem.
|
Re: Debian on Dell Wyse T10 / T50 October 31, 2022 01:21PM |
Admin Registered: 12 years ago Posts: 17,318 |
> I ran debian on my t10 :)
Cool!
> with the power button and the green LED is
> blinking all the time
That could mean the LED GPIOs are different. However, do this to check
And where xxx is the name of each LED GPIO,
-bodhi
===========================
Forum Wiki
bodhi's corner
Cool!
> with the power button and the green LED is
> blinking all the time
That could mean the LED GPIOs are different. However, do this to check
ls -lR /sys/class/leds/
And where xxx is the name of each LED GPIO,
cat /sys/class/leds/xxx/trigger
-bodhi
===========================
Forum Wiki
bodhi's corner
|
Re: Debian on Dell Wyse T10 / T50 October 31, 2022 01:28PM |
Admin Registered: 12 years ago Posts: 17,318 |
> However, do this to check
>
>
> And where xxx is the name of each LED GPIO,
>
>
NVM. The DTS does not have any LED GPIOs defined yet :)
-bodhi
===========================
Forum Wiki
bodhi's corner
>
>
> ls -lR /sys/class/leds/ >>
> And where xxx is the name of each LED GPIO,
>
>
> cat /sys/class/leds/xxx/trigger >
NVM. The DTS does not have any LED GPIOs defined yet :)
-bodhi
===========================
Forum Wiki
bodhi's corner
|
Re: Debian on Dell Wyse T10 / T50 October 31, 2022 01:32PM |
Registered: 2 years ago Posts: 27 |
bodhi Wrote:
-------------------------------------------------------
>
> That could mean the LED GPIOs are different.
> However, do this to check
>
I don't know if it should look like this
-------------------------------------------------------
>
> That could mean the LED GPIOs are different.
> However, do this to check
>
I don't know if it should look like this
root@debian:/# ls -lR /sys/class/leds/ /sys/class/leds/: total 0 drwxr-xr-x 2 root root 0 Oct 31 09:28 . drwxr-xr-x 55 root root 0 Oct 31 09:28 .. lrwxrwxrwx 1 root root 0 Oct 31 09:41 input4::capslock -> ../../devices/platform/mbus/mbus:internal-regs/f1050000.usb-host/usb1/1-1/1-1.3/1-1.3:1.0/0003:04D9:1702.0003/input/input4/input4::capslock lrwxrwxrwx 1 root root 0 Oct 31 09:41 input4::numlock -> ../../devices/platform/mbus/mbus:internal-regs/f1050000.usb-host/usb1/1-1/1-1.3/1-1.3:1.0/0003:04D9:1702.0003/input/input4/input4::numlock lrwxrwxrwx 1 root root 0 Oct 31 09:41 input4::scrolllock -> ../../devices/platform/mbus/mbus:internal-regs/f1050000.usb-host/usb1/1-1/1-1.3/1-1.3:1.0/0003:04D9:1702.0003/input/input4/input4::scrolllock lrwxrwxrwx 1 root root 0 Oct 31 09:41 mmc0:: -> ../../devices/platform/mbus/mbus:internal-regs/f1090000.sdio-host/leds/mmc0:: lrwxrwxrwx 1 root root 0 Oct 31 09:41 mmc1:: -> ../../devices/platform/mbus/mbus:internal-regs/f1092000.sdio-host/leds/mmc1::
|
Re: Debian on Dell Wyse T10 / T50 October 31, 2022 02:54PM |
Admin Registered: 12 years ago Posts: 17,318 |
>
>
These look like defaults for Dove SoC DTS.
I've looked at the DTS for T50, which Koen and I created. We did not have any LED GPIOs definition (LEDs are not relevant to running the box).
So now the question is what is ThinOS ? is it a Linux derivative? if it is, then we can find the GPIOs while in a shell. But it seems there is no way to do that with ThinOS.
-bodhi
===========================
Forum Wiki
bodhi's corner
>
> root@debian:/# ls -lR /sys/class/leds/ > /sys/class/leds/: > total 0 > drwxr-xr-x 2 root root 0 Oct 31 09:28 . > drwxr-xr-x 55 root root 0 Oct 31 09:28 .. > lrwxrwxrwx 1 root root 0 Oct 31 09:41 > input4::capslock -> > ../../devices/platform/mbus/mbus:internal-regs/f1050000.usb-host/usb1/1-1/1-1.3/1-1.3:1.0/0003:04D9:1702.0003/input/input4/input4::capslock > lrwxrwxrwx 1 root root 0 Oct 31 09:41 > input4::numlock -> > ../../devices/platform/mbus/mbus:internal-regs/f1050000.usb-host/usb1/1-1/1-1.3/1-1.3:1.0/0003:04D9:1702.0003/input/input4/input4::numlock > lrwxrwxrwx 1 root root 0 Oct 31 09:41 > input4::scrolllock -> > ../../devices/platform/mbus/mbus:internal-regs/f1050000.usb-host/usb1/1-1/1-1.3/1-1.3:1.0/0003:04D9:1702.0003/input/input4/input4::scrolllock > lrwxrwxrwx 1 root root 0 Oct 31 09:41 mmc0:: -> > ../../devices/platform/mbus/mbus:internal-regs/f1090000.sdio-host/leds/mmc0:: > lrwxrwxrwx 1 root root 0 Oct 31 09:41 mmc1:: -> > ../../devices/platform/mbus/mbus:internal-regs/f1092000.sdio-host/leds/mmc1:: >
These look like defaults for Dove SoC DTS.
I've looked at the DTS for T50, which Koen and I created. We did not have any LED GPIOs definition (LEDs are not relevant to running the box).
So now the question is what is ThinOS ? is it a Linux derivative? if it is, then we can find the GPIOs while in a shell. But it seems there is no way to do that with ThinOS.
-bodhi
===========================
Forum Wiki
bodhi's corner
|
Re: Debian on Dell Wyse T10 / T50 October 31, 2022 09:49PM |
Registered: 2 years ago Posts: 27 |
bodhi Wrote:
-------------------------------------------------------
>
> So now the question is what is ThinOS ? is it a
> Linux derivative? if it is, then we can find the
> GPIOs while in a shell. But it seems there is no
> way to do that with ThinOS.
while looking at ThinOS files I saw some mention of https://en.wikipedia.org/wiki/ECos
but it's hardly here to look for a solution.
I ran official ubuntu on my device, the procedure is similar to the previous one, we need 2 partitions.
The first fat32 containing the kernel I got by extracting the par3.im file from 20120203-0_U-1.041_T50_merlin.
There in the boot directory is vmlinuz-2.6.32-217-hedley which we have to run with the command
then put it on the first partition of the flash drive along with the file wloader.cfg containing
The resulting file from par3.img extracted by binwalk must be saved on the second partition of the device using the dd utility.
The T10 does not differ much from the T50, it lacks internal memory and has other software pre-loaded as standard.
The led and the power button are working properly on this old ubuntu.
-------------------------------------------------------
>
> So now the question is what is ThinOS ? is it a
> Linux derivative? if it is, then we can find the
> GPIOs while in a shell. But it seems there is no
> way to do that with ThinOS.
while looking at ThinOS files I saw some mention of https://en.wikipedia.org/wiki/ECos
but it's hardly here to look for a solution.
I ran official ubuntu on my device, the procedure is similar to the previous one, we need 2 partitions.
The first fat32 containing the kernel I got by extracting the par3.im file from 20120203-0_U-1.041_T50_merlin.
There in the boot directory is vmlinuz-2.6.32-217-hedley which we have to run with the command
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n "Hedley kernel" -d vmlinuz-2.6.32-217-hedley uImage
then put it on the first partition of the flash drive along with the file wloader.cfg containing
kernel=./uImage initrd=./uInitrd param="rootdelay=20 root=/dev/sda2 pm_disable usb0Mode=host usb1Mode=host video=dovefb:lcd0:1024x768-32@60,lcd1:1024x768-32@60 clcd.lcd0_enable=1 clcd.lcd1_enable=1 clcd.lcd0_clk=3 clcd.lcd1_clk=1 splash no_console_suspend kb3310_disable=1 cpufreq_disable=1 vmalloc=384M console=tty0 console=ttyS0,115200 "
The resulting file from par3.img extracted by binwalk must be saved on the second partition of the device using the dd utility.
The T10 does not differ much from the T50, it lacks internal memory and has other software pre-loaded as standard.
The led and the power button are working properly on this old ubuntu.
|
karrelax
Re: Debian on Dell Wyse T10 / T50 November 01, 2022 12:33PM |
Hi everyone,
I am still stuck with my ubuntu 12.04 and half the screen.
I did format the internal mmcblk0 to have two partitions, one fat and one ext4. I copied the root to the p2, and all the possible kernels that I have to the fat partition, but It wont start.
BTW, I happen to get something new about the wloader.
Until now, my wloader menu showed "wloader type: WNOS" (not editable). But now it shows "LINUX".
I can edit "PATH" and "KERNEL", but still, not working. Default PATH is "./;".
I have a USB with the wloader and the uInitrd and uImage pointing the root to the partition p2 and that works. Lots of issues, but so far so good. That way I have screen working, ethernet working, access to mmcblk0. Issue with the CPU1 and its voltage regulation appears constantly, so the ttys are not much usable, they get flooded with this error:
([ 2253.384887] cpu1 turning on!
[ 2253.407897] CPU1: Booted secondary processor
[ 2253.407928] CPU1: Unknown IPI message 0x1
[ 2253.408020] Switched to NOHz mode on CPU #1
[ 2253.408111] CPUFREQ cpu 1 support for mmp3 initialized, cur 1066666
[ 2253.408294] CPUMON U 92 [ 2253.408294] cpu1 on end!
[ 2253.658447] <PM:0>:CPU@[pll1_clkoutp]|MM: 533333|MP1:1066666|MP2:1066666|FAB: 533333| 0 us|1536
[ 2253.658569] <PM:0>:CPU@[ pll1_d_2]|MM: 100000|MP1: 100000|MP2: 100000|FAB: 100000| 7 us|1536
[ 2253.658691] Voltage updated to 1200
[ 2253.658782] Failed to set dvfs regulator vcc_main [ 2253.658905] Failed to set regulator vcc_main for clock cpu to 1200 mV
[ 2253.659057] <PM:0>:AXI@[ pll1]|A1: 400000|A2: 200000| | | 0 us|1003
[ 2253.659240] <PM:0>:AXI@[ pll1_d_2]|A1: 100000|A2: 100000| | |12 us|1003
[ 2255.488800] cpu1 turning off!
[ 2255.492065] do_nothing: cpu 1
[ 2255.511688] CPU1: shutdown
[ 2255.516357] CPU1: shutdown
[ 2255.525573] CPUMON D 8
[ 2255.525634] cpu1 off end!
@Wildhem, one question: you said
"The resulting file from par3.img extracted by binwalk must be saved on the second partition of the device using the dd utility."
That means, I need 3 partitions? Said, p1 vfat (kernel + initrd + wloader.cfg) , p2 (where you DD the par3.img direclty ? ) and the p3 ext4 for the rootfs?
If i try the same with the Memory extracted from my wyse 3020 (with USB Firmware updater) (I got booloader.img cmos.img and par1.img) I get useles files, but inside the _par1.img.extracted Ifind a file called "0" that is the complete disk with 4 partitions:
I could not go further here. I took each of them (with dd) to single files. Extracting this file with binwalk -eM I get iles in pairs (FILE + FILE.zlip). Most of them are "data", some are interesting :
p1 https://pastebin.com/yLnBBEYy
p2 https://pastebin.com/FZaTSESi
p3 https://pastebin.com/mPUxW1Hk
,p4 https://pastebin.com/QHZ6hPMX
I am still stuck with my ubuntu 12.04 and half the screen.
I did format the internal mmcblk0 to have two partitions, one fat and one ext4. I copied the root to the p2, and all the possible kernels that I have to the fat partition, but It wont start.
BTW, I happen to get something new about the wloader.
Until now, my wloader menu showed "wloader type: WNOS" (not editable). But now it shows "LINUX".
I can edit "PATH" and "KERNEL", but still, not working. Default PATH is "./;".
I have a USB with the wloader and the uInitrd and uImage pointing the root to the partition p2 and that works. Lots of issues, but so far so good. That way I have screen working, ethernet working, access to mmcblk0. Issue with the CPU1 and its voltage regulation appears constantly, so the ttys are not much usable, they get flooded with this error:
([ 2253.384887] cpu1 turning on!
[ 2253.407897] CPU1: Booted secondary processor
[ 2253.407928] CPU1: Unknown IPI message 0x1
[ 2253.408020] Switched to NOHz mode on CPU #1
[ 2253.408111] CPUFREQ cpu 1 support for mmp3 initialized, cur 1066666
[ 2253.408294] CPUMON U 92 [ 2253.408294] cpu1 on end!
[ 2253.658447] <PM:0>:CPU@[pll1_clkoutp]|MM: 533333|MP1:1066666|MP2:1066666|FAB: 533333| 0 us|1536
[ 2253.658569] <PM:0>:CPU@[ pll1_d_2]|MM: 100000|MP1: 100000|MP2: 100000|FAB: 100000| 7 us|1536
[ 2253.658691] Voltage updated to 1200
[ 2253.658782] Failed to set dvfs regulator vcc_main [ 2253.658905] Failed to set regulator vcc_main for clock cpu to 1200 mV
[ 2253.659057] <PM:0>:AXI@[ pll1]|A1: 400000|A2: 200000| | | 0 us|1003
[ 2253.659240] <PM:0>:AXI@[ pll1_d_2]|A1: 100000|A2: 100000| | |12 us|1003
[ 2255.488800] cpu1 turning off!
[ 2255.492065] do_nothing: cpu 1
[ 2255.511688] CPU1: shutdown
[ 2255.516357] CPU1: shutdown
[ 2255.525573] CPUMON D 8
[ 2255.525634] cpu1 off end!
@Wildhem, one question: you said
"The resulting file from par3.img extracted by binwalk must be saved on the second partition of the device using the dd utility."
That means, I need 3 partitions? Said, p1 vfat (kernel + initrd + wloader.cfg) , p2 (where you DD the par3.img direclty ? ) and the p3 ext4 for the rootfs?
If i try the same with the Memory extracted from my wyse 3020 (with USB Firmware updater) (I got booloader.img cmos.img and par1.img) I get useles files, but inside the _par1.img.extracted Ifind a file called "0" that is the complete disk with 4 partitions:
Command (m for help): p Disk 0: 3,64 GiB, 3909091328 bytes, 7634944 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type 0p1 256 1933311 1933056 943,9M c W95 FAT32 (LBA) 0p2 1933312 3866623 1933312 944M c W95 FAT32 (LBA) 0p3 * 3866624 5799935 1933312 944M c W95 FAT32 (LBA) 0p4 5799936 7634943 1835008 896M c W95 FAT32 (LBA)
I could not go further here. I took each of them (with dd) to single files. Extracting this file with binwalk -eM I get iles in pairs (FILE + FILE.zlip). Most of them are "data", some are interesting :
p1 https://pastebin.com/yLnBBEYy
p2 https://pastebin.com/FZaTSESi
p3 https://pastebin.com/mPUxW1Hk
,p4 https://pastebin.com/QHZ6hPMX
|
Re: Debian on Dell Wyse T10 / T50 November 01, 2022 12:35PM |
Admin Registered: 12 years ago Posts: 17,318 |
wildhem
> The T10 does not differ much from the T50, it
> lacks internal memory and has other software
> pre-loaded as standard.
Then perhaps the GPIOs are the same.
>
> The led and the power button are working properly
> on this old ubuntu.
See if you can find the LEDs the same way in /sys/class?
-bodhi
===========================
Forum Wiki
bodhi's corner
> The T10 does not differ much from the T50, it
> lacks internal memory and has other software
> pre-loaded as standard.
Then perhaps the GPIOs are the same.
>
> The led and the power button are working properly
> on this old ubuntu.
See if you can find the LEDs the same way in /sys/class?
ls -l /sys/class/leds/
-bodhi
===========================
Forum Wiki
bodhi's corner
|
Re: Debian on Dell Wyse T10 / T50 November 01, 2022 01:26PM |
Registered: 2 years ago Posts: 27 |
karrelax Wrote:
-------------------------------------------------------
>
> I have a Wyse 3020 with thinOs Lite.
>
I have a Wyse 3010, it's a different device, you have to use different files.
if you use
bodhi Wrote:
-------------------------------------------------------
>
> See if you can find the LEDs the same way in
> /sys/class?
>
-------------------------------------------------------
>
> I have a Wyse 3020 with thinOs Lite.
>
I have a Wyse 3010, it's a different device, you have to use different files.
if you use
binwalk -e par3.imgyou will get the file /_par1.img.extracted/0, this "0" file is just the image of the second partition you write with dd
dd if=/_par3.img.extracted/0 of=dev/sdX2
bodhi Wrote:
-------------------------------------------------------
>
> See if you can find the LEDs the same way in
> /sys/class?
>
root@LWT0080XXXXXXXX:/etc/apt# ls -l /sys/class/leds/ total 0 lrwxrwxrwx 1 root root 0 2022-11-01 09:35 mmc0:: -> ../../devices/platform/sdhci-mv.1/leds/mmc0::
|
Re: Debian on Dell Wyse T10 / T50 November 01, 2022 01:30PM |
Admin Registered: 12 years ago Posts: 17,318 |
> > See if you can find the LEDs the same way in
> > /sys/class?
> >
>
>
So it looks like the LEDs controls were hardcoded in this kernel.
-bodhi
===========================
Forum Wiki
bodhi's corner
> > /sys/class?
> >
>
>
> root@LWT0080XXXXXXXX:/etc/apt# ls -l > /sys/class/leds/ > total 0 > lrwxrwxrwx 1 root root 0 2022-11-01 09:35 mmc0:: > -> ../../devices/platform/sdhci-mv.1/leds/mmc0:: >
So it looks like the LEDs controls were hardcoded in this kernel.
-bodhi
===========================
Forum Wiki
bodhi's corner
|
Re: Debian on Dell Wyse T10 / T50 November 01, 2022 01:55PM |
Registered: 2 years ago Posts: 27 |
bodhi Wrote:
-------------------------------------------------------
> So it looks like the LEDs controls were hardcoded
> in this kernel.
I found a script that runs at startup
ec-led probably communicates over the i2c bus
there are even more files to analyze
edit:
there is also ec-r program
Edited 4 time(s). Last edit at 11/01/2022 02:08PM by wildhem.
-------------------------------------------------------
> So it looks like the LEDs controls were hardcoded
> in this kernel.
I found a script that runs at startup
#!/bin/sh # File Name: /etc/addons.d/WYSE_PATCH/wyse-led-linux.sh # Function: Turn on the Green LED when starting Linux # NOTE: This script gets executed during boot process, # so use sh instead of bash for faster processing. [ -x /usr/sbin/ec-led ] && /usr/sbin/ec-led g 1 exit 0
ec-led probably communicates over the i2c bus
there are even more files to analyze
edit:
root@LWT00XXXXXXXX:/# ec-led
How to run this program?
Type 'ec-led arg1 arg2'
arg1
arg1=p for power LED
arg1=a for amber color of the LED next to POWER LED
arg1=g for green color of the LED next to POWER LED
arg2
arg2=0 for LED off
arg2=1 for LED on
arg2=2 for LED slow glowing
arg2=3 for LED flashing(0.5s)
No arg or wrong number of args or wrong value of args would print this help message
there is also ec-r program
root@LWT00XXXXXXXX:/etc/apt# ec-r
Reading first 128 bytes of ec memory
0000: *
0010: *
0020: *
0030: *
0040: *
0050: *
0060: f*
0070: ffff ffff ffff ffff ffff ffff ffff ffff ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
addr: value Meaning
00: ff not 'set to default'
01: 01 Power LED on
02: 00 The amber color of the LED next to Power LED is off
03: 01 The green color of the LED next to Power LED is on
10: 01 RJ45 is enabled
11: 01 wifi is enabled
12: 01 usb_f1 is enabled
13: 01 usb_f2 is enabled
14: 01 usb_b1 is enabled
15: 01 usb_b2 is enabled
16: 00 Always off/default
20: 01 'wake on lan' is enabled
21: 01 'wake on usb' is enabled
22: 02 14/power_bottom_on
30: 4d platform=Mimas
31: 03 Build=PVT
32: 04 ec_version=0.4
How to run this program?
Either type 'ec-r' or 'ec-r arg'
Type 'ec-r arg' to read LED status
arg
arg=p to read status of power LED
arg=a to read the amber status of the LED next to POWER LED
arg=g to read the green status of the LED next to POWER LED
arg=e to read EC info only
arg=h to print out this usage
Type 'ec-r' without args to read all EC memory
Edited 4 time(s). Last edit at 11/01/2022 02:08PM by wildhem.
|
Re: Debian on Dell Wyse T10 / T50 November 01, 2022 04:37PM |
Registered: 5 months ago Posts: 11 |
wildhem Wrote:
-------------------------------------------------------
> Xabby76 Wrote:
> -------------------------------------------------------
> > Great wildhem.!!!!!
> >
> > Congratulations.!!!!
> >
> > Do you have also video output or not.?
> > Can you share with us all the process .?
> >
> > Thanks a lot.!!
>
> using the binwalk tool, I extracted the
> bootLoader.img file from the official software and
> got a file with a size of 704 KB, which I
> increased to the size of my spi memory chip (8 MB)
> by adding zeros using a hex editor. Then I
> programmed it through ch341a and after turning on
> the device, wLoader from Wyse will appear on the
> screen and at the first start it will ask you to
> set the mac address and serial number. After this
> operation we can boot from usb, but we need an
> additional fat32 partition with linux kernel,
> initial ramdisk and configuration file wloader.cfg
> which will refer to the rootfs partition (it can
> be a separate flash drive)
> I used the Bodhi kernel on the first partition of
> my flash drive, the second is the ext4
> filesystem.
> I enclose the unpacked wLoader for
> self-processing.
>
> Unfortunately, the system does not display the
> screen, but ssh and serial port works.
Thank you so much wildhem.!!!!! :)
-------------------------------------------------------
> Xabby76 Wrote:
> -------------------------------------------------------
> > Great wildhem.!!!!!
> >
> > Congratulations.!!!!
> >
> > Do you have also video output or not.?
> > Can you share with us all the process .?
> >
> > Thanks a lot.!!
>
> using the binwalk tool, I extracted the
> bootLoader.img file from the official software and
> got a file with a size of 704 KB, which I
> increased to the size of my spi memory chip (8 MB)
> by adding zeros using a hex editor. Then I
> programmed it through ch341a and after turning on
> the device, wLoader from Wyse will appear on the
> screen and at the first start it will ask you to
> set the mac address and serial number. After this
> operation we can boot from usb, but we need an
> additional fat32 partition with linux kernel,
> initial ramdisk and configuration file wloader.cfg
> which will refer to the rootfs partition (it can
> be a separate flash drive)
> I used the Bodhi kernel on the first partition of
> my flash drive, the second is the ext4
> filesystem.
> I enclose the unpacked wLoader for
> self-processing.
>
> Unfortunately, the system does not display the
> screen, but ssh and serial port works.
Thank you so much wildhem.!!!!! :)
|
Re: Debian on Dell Wyse T10 / T50 November 01, 2022 07:11PM |
Registered: 2 years ago Posts: 27 |
|
Re: Debian on Dell Wyse T10 / T50 November 02, 2022 05:52PM |
Registered: 2 years ago Posts: 27 |
in logread on debian it displays the missing dtb entry
on stock ubuntu in folder /dev there are two i2c controllers (i2c-0, i2c-1), but on debian only i2c-0, maybe it causes an error?
edit:
I enabled i2c-1 by editing the dtb file, the above error still shows, but ls -l /sys/class/leds/ command returns one additional entry
Edited 3 time(s). Last edit at 11/02/2022 07:12PM by wildhem.
Nov 2 15:29:53 debian user.warn kernel: [ 3.239507][ T1] dove-pinctrl f10d0200.pin-ctrl: falling back to hardcoded PMU resource Nov 2 15:29:53 debian user.warn kernel: [ 3.239847][ T1] dove-pinctrl f10d0200.pin-ctrl: [Firmware Bug]: Missing pinctrl regs in DTB. Please update your firmware. Nov 2 15:29:53 debian user.info kernel: [ 3.240736][ T1] dove-pinctrl f10d0200.pin-ctrl: registered pinctrl driver
on stock ubuntu in folder /dev there are two i2c controllers (i2c-0, i2c-1), but on debian only i2c-0, maybe it causes an error?
edit:
I enabled i2c-1 by editing the dtb file, the above error still shows, but ls -l /sys/class/leds/ command returns one additional entry
root@debian:/dev# ls -l /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Nov 2 16:43 . drwxr-xr-x 54 root root 0 Nov 2 16:43 .. lrwxrwxrwx 1 root root 0 Nov 2 16:50 mmc0:: -> ../../devices/platform/mbus/mbus:internal-regs/f1090000.sdio-host/leds/mmc0:: lrwxrwxrwx 1 root root 0 Nov 2 16:50 mmc1:: -> ../../devices/platform/mbus/mbus:internal-regs/f1092000.sdio-host/leds/mmc1::ic2-1 also appeared in the / dev folder, besides it also i2c-2, i2c-3 and I'm not sure if there were gpiochip0, gpiochip1, gpiochip2 here before
Edited 3 time(s). Last edit at 11/02/2022 07:12PM by wildhem.
|
Re: Debian on Dell Wyse T10 / T50 November 02, 2022 09:13PM |
Admin Registered: 12 years ago Posts: 17,318 |
wildhem,
> Nov 2 15:29:53 debian user.warn kernel: [
> 3.239507][ T1] dove-pinctrl f10d0200.pin-ctrl:
> falling back to hardcoded PMU resource
> Nov 2 15:29:53 debian user.warn kernel: [
> 3.239847][ T1] dove-pinctrl f10d0200.pin-ctrl:
> [Firmware Bug]: Missing pinctrl regs in DTB.
> Please update your firmware.
> Nov 2 15:29:53 debian user.info kernel: [
> 3.240736][ T1] dove-pinctrl f10d0200.pin-ctrl:
> registered pinctrl driver
> [/code]
I don't think this is related to i2c. It is just the new DTS binding that we need to update to. It's running OK on the HP T5335z. Everything works except the display (I was still investigating using the kernel DRM, and now it seems there is a simple way to use it).
This pinctrl issue is definitely something needs to be done.
-bodhi
===========================
Forum Wiki
bodhi's corner
> Nov 2 15:29:53 debian user.warn kernel: [
> 3.239507][ T1] dove-pinctrl f10d0200.pin-ctrl:
> falling back to hardcoded PMU resource
> Nov 2 15:29:53 debian user.warn kernel: [
> 3.239847][ T1] dove-pinctrl f10d0200.pin-ctrl:
> [Firmware Bug]: Missing pinctrl regs in DTB.
> Please update your firmware.
> Nov 2 15:29:53 debian user.info kernel: [
> 3.240736][ T1] dove-pinctrl f10d0200.pin-ctrl:
> registered pinctrl driver
> [/code]
I don't think this is related to i2c. It is just the new DTS binding that we need to update to. It's running OK on the HP T5335z. Everything works except the display (I was still investigating using the kernel DRM, and now it seems there is a simple way to use it).
This pinctrl issue is definitely something needs to be done.
-bodhi
===========================
Forum Wiki
bodhi's corner
|
Re: Debian on Dell Wyse T10 / T50 November 05, 2022 07:47AM |
Registered: 2 years ago Posts: 27 |
I have another boot log from the launch of the pendrive prepared by dell usb imagging.
After displaying the dialog box and pressing the power button, the following information appears on the screen:
and another log, the kernel loaded from usb imaging with an attempt to boot the stock ubuntu from /dev/sda2. Display looping "error kb3310 1-0058: invalid toggle bit", I removed it from this log
Uncompressing Linux.................................................................................................................................................................................................. done, booting the kernel.
Linux version 2.6.32-206-mimas (buildd@cushaw) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #19hedley2-Ubuntu Fri Jul 30 09:33:57 UTC 2010 (Ubuntu 2.6.32-206.19hedley2-mimas 2.6.32.15+drm33.5)
CPU: Marvell PJ4 v7 Processor-wmmx-wco [560f5815] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: WYSE Mimas Board
Marvell Dove DRAM parameters found (version = 0x09080000)
Machine: WYSE Titan Board
Memory policy: ECC disabled, Data cache writeback
wait table c0e76020
Built 1 zonelists in Zone order, mobility grouping off. Total pages: 203200
Kernel command line: rootdelay=5 root=/dev/ram0 rw ramdisk_size=136314880 ip=$(ipaddr):$(serverip)$(bootargs_end) usb0Mode=host usb1Mode=host video=dovefb:lcd0:1024x600-16@60-edid,lcd1:1024x768-16@60-edid clcd.lcd0_enable=1 clcd.lcd1_enable=1 pm_disable titan earlyprintk console=tty0 console=ttyS0,115200
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 800MB = 800MB total
Memory: 784640KB available (5516K code, 706K data, 168K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:135
Console: colour dummy device 80x30
console [tty0] enabled
Calibrating delay loop... 992.87 BogoMIPS (lpj=4964352)
Security Framework initialized
AppArmor: AppArmor initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
NET: Registered protocol family 16
Dove MV88AP510-Rev-Unsupported SoC, TCLK = 167MHz
DOVE_MC @ 0x280 is 010E0202
PLiao: DOVE_MC @ 0x510 is 01010101
Tauros2: Disabling L2 prefetch.
Tauros2: L2 cache support initialised in ARMv7 mode.
Setting gpu clock to 500000000 (divider: 4)
Setting axi clock to 333000000 (divider: 5)
titan_eneec_gpio_setup()
Dove: failed to setup EC_IRQ GPIO
Initializing USB0 Host
Initializing USB1 Host
Dove PCIe port 0: link down, ignoring
Dove PCIe port 1: link down, ignoring
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NetLabel: Initializing
NetLabel: domain hash size = 128
NetLabel: protocols = UNLABELED CIPSOv4
NetLabel: unlabeled traffic allowed by default
Switching to clocksource orion_clocksource
AppArmor: AppArmor Filesystem Enabled
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Power Management for Marvell Dove.
PMU Detected Frequencies CPU 800Mhz, AXI 200Mhz, L2 400Mhz, DDR 400Mhz
Dove cpuFreq Driver Initialized (1/0)
Dove hwmon thermal sensor initialized.
cesadev_modinit
cesadev_probe
cesadev_init(c005f7cc)
mvCesaInit: sessions=640, queue=64, pSram=fdb00000
audit: initializing netlink socket (disabled)
type=2000 audit(0.241:1): initialized
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
squashfs: version 4.0 (2009/01/31) Phillip Lougher
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 1533
alg: No test for cipher_null (cipher_null-generic)
alg: No test for ecb(cipher_null) (ecb-cipher_null)
alg: No test for digest_null (digest_null-generic)
alg: No test for compress_null (compress_null-generic)
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
Dove Backlight Driver start power on sequence.
backlight power on
first time topanel power on(FB_BLANK_UNBLANK)
Dove Backlight Driver Initialized.
dovedcon has been initialized.
dovefb_display_init
dovefb_display driver init ok.
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 7) is a 16550A
console [ttyS0] enabled
serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 8) is a 16550A
brd: module loaded
loop: module loaded
mvumi:2.0.4.9 Jan 22, 2008
sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 1
Freeing initrd memory: 18620K
scsi0 : sata_mv
ata1: SATA max UDMA/133 irq 62
orion_spi orion_spi.0: use polling mode
m25p80 spi0.0: unrecognized JEDEC id ef4017
m25p80 spi0.0: found UNKNOWN, expected mx25l3205
MV-643xx 10/100/1000 ethernet driver version 1.4
mv643xx_eth smi: probed
ata1: SATA link down (SStatus 0 SControl F300)
net eth0: port 0 with MAC address 00:80:64:e8:66:ba
Registering VMETA UIO driver:.
o Mapping registers at 0xf1c00000 Size 2560 KB.
o Mapping buffer at 928 MB Size 95 MB.
VMETA UIO driver registered successfully.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
orion-ehci orion-ehci.0: Marvell Orion EHCI
orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
orion-ehci orion-ehci.0: irq 24, io mem 0xf1050000
orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
orion-ehci orion-ehci.1: Marvell Orion EHCI
orion-ehci orion-ehci.1: new USB bus registered, assigned bus number 2
orion-ehci orion-ehci.1: irq 25, io mem 0xf1051000
orion-ehci orion-ehci.1: USB 2.0 started, EHCI 1.00
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver ums-datafab
usbcore: registered new interface driver ums-freecom
usbcore: registered new interface driver ums-jumpshot
usbcore: registered new interface driver ums-sddr09
usbcore: registered new interface driver ums-sddr55
eneec_init
mice: PS/2 mouse device common for all mice
rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0
IRQ 133/rtc-mv: IRQF_DISABLED is not guaranteed on shared IRQs
i2c /dev entries driver
eneec_probe with name = KB39XX, addr = 0x58, irq = 71
Drain data : 0x0303
IRQ 71 requested
Driver for 1-wire Dallas network protocol.
1-Wire driver for the DS2760 battery monitor chip - (c) 2004-2005, Szabolcs Gyurko
device-mapper: uevent: version 1.0.3
OUT: 0xff30
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci: Requesting irq host->irq=35, host->irqn
mmc0: SDHCI controller on sdhci-mv.0 [sdhci-mv.0] using DMA
sdhci: Requesting irq host->irq=36, host->irqn
mmc1: SDHCI controller on sdhci-mv.1 [sdhci-mv.1] using DMA
mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
usb 1-1: new high speed USB device using orion-ehci and address 2
mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
asoc: RT5630 HiFi <-> mv88fx-i2s1 mapping ok
ALSA device list:
#0: Dove-I2S-RT5630 (RT5630)
aufs 2-standalone.tree-20091207
oprofile: using arm/mrvl_pj4
TCP cubic registered
NET: Registered protocol family 17
lib80211: common routines for IEEE802.11 drivers
XScale iWMMXt coprocessor detected.
VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 5
Dove FB driver:
Initialize /proc/mv_dump_lcd0
use cat /proc/mv_dump_lcd0 to see reg settings
o Kernel parameter: 1024x600-16@60.
o Found i2c adapter for EDID detection
i2c i2c-1: unable to read EDID block.
i2c i2c-1: unable to read EDID block.
i2c i2c-1: unable to read EDID block.
o Failed to read EDID information,using driver resolutions table.
------------<GFX Layer 0 video mode database>-----------
mode 0: <1920x1200@60> pico=5177
fb timings 336 128 38 1 208 3
xorg timings 1920 2048 2256 2592 1200 1201 1204 1242
mode 1: <1920x1080@60> pico=6734
fb timings 148 88 36 4 44 5
xorg timings 1920 2008 2052 2200 1080 1084 1089 1125
mode 2: <1650x1050@60> pico=6888
fb timings 288 104 33 1 184 3
xorg timings 1650 1754 1938 2226 1050 1051 1054 1087
mode 3: <1366x 768@60> pico=11659
fb timings 216 72 23 1 144 3
xorg timings 1366 1438 1582 1798 768 769 772 795
mode 4: <1280x1024@60> pico=9262
fb timings 248 48 38 1 112 3
xorg timings 1280 1328 1440 1688 1024 1025 1028 1066
mode 5: <1280x 720@60> pico=13468
fb timings 220 110 20 5 40 5
xorg timings 1280 1390 1430 1650 720 725 730 750
mode 6: <1024x 768@85> pico=10581
fb timings 208 48 36 1 96 3
xorg timings 1024 1072 1168 1376 768 769 772 808
mode 7: <1024x 768@70> pico=13346
fb timings 144 24 29 3 136 6
xorg timings 1024 1048 1184 1328 768 771 777 806
mode 8: <1024x 768@60> pico=15385
fb timings 160 24 29 3 136 6
xorg timings 1024 1048 1184 1344 768 771 777 806
mode 9: <1024x 600@60> pico=22401
fb timings 38 38 8 8 100 4
xorg timings 1024 1062 1162 1200 600 608 612 620
mode 10: < 800x 600@85> pico=17790
fb timings 152 32 27 1 64 3
xorg timings 800 832 896 1048 600 601 604 631
mode 11: < 800x 600@75> pico=20234
fb timings 160 16 21 1 80 2
xorg timings 800 816 896 1056 600 601 603 624
mode 12: < 800x 600@72> pico=20052
fb timings 64 56 23 37 120 6
xorg timings 800 856 976 1040 600 637 643 666
mode 13: < 800x 600@60> pico=25131
fb timings 88 40 23 1 128 4
xorg timings 800 840 968 1056 600 601 605 628
mode 14: < 800x 600@56> pico=26515
fb timings 128 32 14 1 128 4
xorg timings 800 832 960 1088 600 601 605 619
mode 15: < 640x 480@85> pico=27780
fb timings 112 32 25 1 48 3
xorg timings 640 672 720 832 480 481 484 509
mode 16: < 640x 480@75> pico=31746
fb timings 48 16 32 11 96 2
xorg timings 640 656 752 800 480 491 493 525
mode 17: < 640x 480@72> pico=32102
fb timings 128 24 28 9 40 3
xorg timings 640 664 704 832 480 489 492 520
mode 18: < 640x 480@60> pico=39758
fb timings 48 16 31 11 96 2
xorg timings 640 656 752 800 480 491 493 524
found <1024x600@60>, pixclock=22401
YC pitch is 0.User program needs refine
Console: switching to colour frame buffer device 128x37
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
o dovefb: frame buffer device was successfully loaded.
Dove FB driver:
Initialize /proc/mv_dump_lcd1
use cat /proc/mv_dump_lcd1 to see reg settings
o Kernel parameter: 1024x768-16@60.
o Found i2c adapter for EDID detection
========================================
Display Information (EDID)
========================================
EDID Version 1.3
Manufacturer: BNQ
Model: 785e
Serial#: 21573
Year: 2010 Week 38
Serial Number: F9A07309SL000
Monitor Name: G2420HDBL
Display Characteristics:
Monitor Operating Limits: From EDID
H: 24-83KHz V: 50-76Hz DCLK: 170MHz
Analog Display Input: Input Voltage - 0.700V/0.300V
Sync: Separate Composite Sync on Green
Max H-size in cm: 53
Max V-size in cm: 29
Gamma: 2.20
DPMS: Active yes, Suspend no, Standby no
RGB Color Display
Chroma
RedX: 0.649 RedY: 0.338
GreenX: 0.289 GreenY: 0.609
BlueX: 0.146 BlueY: 0.070
WhiteX: 0.313 WhiteY: 0.329
Default color format is primary
First DETAILED Timing is preferred
Detailed Timings
148 MHz 1920 2008 2052 2200 1080 1084 1089 1125 +HSync +VSync
Supported VESA Modes
720x400@70Hz
640x480@60Hz
640x480@75Hz
800x600@60Hz
800x600@75Hz
832x624@75Hz
1024x768@60Hz
1024x768@75Hz
1280x1024@75Hz
1152x870@75Hz
Manufacturer's mask: 0
Standard Timings
1152x1152@60Hz
1280x720@60Hz
1280x960@60Hz
1280x1024@60Hz
1600x900@60Hz
1680x1680@60Hz
1920x1080@60Hz
========================================
------------<GFX Layer 1 video mode database>-----------
mode 0: <1920x1080@60> pico=5783
fb timings 329 123 34 1 206 3
xorg timings 1920 2043 2249 2578 1080 1081 1084 1118
mode 1: <1680x1680@60> pico=4159
fb timings 313 128 54 1 184 3
xorg timings 1680 1808 1992 2305 1680 1681 1684 1738
mode 2: <1600x 900@60> pico=8429
fb timings 261 92 28 1 169 3
xorg timings 1600 1692 1861 2122 900 901 904 932
mode 3: <1280x1024@60> pico=9259
fb timings 248 48 38 1 112 3
xorg timings 1280 1328 1440 1688 1024 1025 1028 1066
mode 4: <1280x 960@60> pico=9259
fb timings 312 96 36 1 112 3
xorg timings 1280 1376 1488 1800 960 961 964 1000
mode 5: <1280x 720@60> pico=13401
fb timings 194 61 22 1 133 3
xorg timings 1280 1341 1474 1668 720 721 724 746
mode 6: <1152x1152@60> pico=9006
fb timings 200 76 36 1 124 3
xorg timings 1152 1228 1352 1552 1152 1153 1156 1192
mode 7: <1152x 864@75> pico=9259
fb timings 256 64 32 1 128 3
xorg timings 1152 1216 1344 1600 864 865 868 900
mode 8: <1280x1024@75> pico=7407
fb timings 248 16 38 1 144 3
xorg timings 1280 1296 1440 1688 1024 1025 1028 1066
mode 9: <1024x 768@75> pico=12690
fb timings 176 16 28 1 96 3
xorg timings 1024 1040 1136 1312 768 769 772 800
mode 10: <1024x 768@60> pico=15384
fb timings 160 24 29 3 136 6
xorg timings 1024 1048 1184 1344 768 771 777 806
mode 11: < 832x 624@75> pico=18715
fb timings 130 43 24 1 87 3
xorg timings 832 875 962 1092 624 625 628 652
mode 12: < 800x 600@75> pico=20202
fb timings 160 16 21 1 80 3
xorg timings 800 816 896 1056 600 601 604 625
mode 13: < 800x 600@60> pico=25000
fb timings 88 40 23 1 128 4
xorg timings 800 840 968 1056 600 601 605 628
mode 14: < 640x 480@75> pico=31746
fb timings 120 16 16 1 64 3
xorg timings 640 656 720 840 480 481 484 500
mode 15: < 640x 480@60> pico=39682
fb timings 48 16 33 10 96 2
xorg timings 640 656 752 800 480 490 492 525
mode 16: < 720x 400@70> pico=38210
fb timings 88 17 13 1 71 3
xorg timings 720 737 808 896 400 401 404 417
mode 17: <1920x1080@60> pico=6734
fb timings 148 88 36 4 44 5
xorg timings 1920 2008 2052 2200 1080 1084 1089 1125
found <1024x768@60>, pixclock=15384
YC pitch is 0.User program needs refine
o dovefb: frame buffer device was successfully loaded.
atkbd.c: keyboard reset failed on eneec/serio0
OUT: 0xf230
rtc-mv rtc-mv: setting system clock to 2022-11-04 00:51:48 UTC (1667523108)
usb 1-1.1: new high speed USB device using orion-ehci and address 3
OUT: 0xed30
usb 1-1.1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
OUT: 0xff40
usb 1-1.2: new low speed USB device using orion-ehci and address 4
usb 1-1.2: configuration #1 chosen from 1 choice
input: USB Keyboard as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input0
generic-usb 0003:04D9:1702.0001: input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-orion-ehci.0-1.2/input0
input: USB Keyboard as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2:1.1/input/input1
generic-usb 0003:04D9:1702.0002: input: USB HID v1.10 Device [ USB Keyboard] on usb-orion-ehci.0-1.2/input1
usb 1-1.3: new full speed USB device using orion-ehci and address 5
usb 1-1.3: configuration #1 chosen from 1 choice
input: Logitech USB Receiver as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input2
generic-usb 0003:046D:C52F.0003: input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-orion-ehci.0-1.3/input0
input: Logitech USB Receiver as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input3
generic-usb 0003:046D:C52F.0004: input: USB HID v1.11 Device [Logitech USB Receiver] on usb-orion-ehci.0-1.3/input1
usb 1-1.4: new high speed USB device using orion-ehci and address 6
usb 1-1.4: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Mass Storage devices
atkbd.c: keyboard reset failed on eneec/serio1
OUT: 0xf240
OUT: 0xed40
IP-Config: Guessing netmask 255.0.0.0
IP-Config: Complete:
device=eth0, addr=77.0.0.0, mask=255.0.0.0, gw=255.255.255.255,
host=77.0.0.0, domain=, nis-domain=(none),
bootserver=209.0.0.0, rootserver=209.0.0.0, rootpath=
OUT: 0xf240
Waiting 5sec before mounting root device...
eth0: link up, 1000 Mb/s, full duplex, flow control disabled
scsi 1:0:0:0: Direct-Access USB Flash Disk 1100 PQ: 0 ANSI: 4
sd 1:0:0:0: [sda] 7866368 512-byte logical blocks: (4.02 GB/3.75 GiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] Attached SCSI removable disk
scsi 2:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4
sd 2:0:0:0: [sdb] 15155200 512-byte logical blocks: (7.75 GB/7.22 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1 sdb2
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
RAMDISK: gzip image found at block 0
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing init memory: 168K
init: ureadahead main process (197) terminated with status 127
[H[J[H[J
Merlin Version Number 3.5.4
[H[J
Imaging Agent started !!!!!!!!!!!!!!
[H[Jcat: /tmp/triton_recovery.txt: No such file or directory
[: 10: unexpected operator
cat: /tmp/triton_recovery.txt: No such file or directory
[: 19: unexpected operator
cat: /tmp/triton_recovery.txt: No such file or directory
[: 28: unexpected operator
sh: /usr/sbin/dmidecode: not found
[H[J[H[Jsh: cannot create /proc/splash: Directory nonexistent
After displaying the dialog box and pressing the power button, the following information appears on the screen:
eneec_interrupt IN : 0x7432and when released
eneec_interrupt IN : 0xf433
and another log, the kernel loaded from usb imaging with an attempt to boot the stock ubuntu from /dev/sda2. Display looping "error kb3310 1-0058: invalid toggle bit", I removed it from this log
Uncompressing Linux.................................................................................................................................................................................................. done, booting the kernel. Linux version 2.6.32-206-mimas (buildd@cushaw) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #19hedley2-Ubuntu Fri Jul 30 09:33:57 UTC 2010 (Ubuntu 2.6.32-206.19hedley2-mimas 2.6.32.15+drm33.5) CPU: Marvell PJ4 v7 Processor-wmmx-wco [560f5815] revision 5 (ARMv7), cr=10c53c7f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: WYSE Mimas Board Marvell Dove DRAM parameters found (version = 0x09080000) Machine: WYSE Mimas Board Memory policy: ECC disabled, Data cache writeback wait table c0e74020 wait table c0e76040 Built 1 zonelists in Zone order, mobility grouping off. Total pages: 203200 Kernel command line: rootdelay=15 root=/dev/sda2 pm_disable usb0Mode=host usb1Mode=host video=dovefb:lcd0:1024x768-32@60,lcd1:1024x768-32@60 clcd.lcd0_enable=1 clcd.lcd1_enable=1 clcd.lcd0_clk=3 clcd.lcd1_clk=1 splash no_console_suspend kb3310_disable=1 cpufreq_disable=1 vmalloc=384M console=tty0 console=ttyS0,115200 PID hash table entries: 4096 (order: 2, 16384 bytes) Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 600MB 200MB = 800MB total Memory: 784448KB available (5516K code, 706K data, 168K init, 204800K highmem) Hierarchical RCU implementation. NR_IRQS:135 Console: colour dummy device 80x30 console [tty0] enabled Calibrating delay loop... 992.87 BogoMIPS (lpj=4964352) Security Framework initialized AppArmor: AppArmor initialized Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok devtmpfs: initialized NET: Registered protocol family 16 Dove MV88AP510-Rev-Unsupported SoC, TCLK = 167MHz DOVE_MC @ 0x280 is 010E0202 PLiao: DOVE_MC @ 0x510 is 01010101 Tauros2: Disabling L2 prefetch. Tauros2: L2 cache support initialised in ARMv7 mode. Setting gpu clock to 500000000 (divider: 4) Setting axi clock to 333000000 (divider: 5) Initializing USB0 Host Initializing USB1 Host Dove PCIe port 0: link down, ignoring Dove PCIe port 1: link down, ignoring bio: create slab <bio-0> at 0 vgaarb: loaded SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default Switching to clocksource orion_clocksource AppArmor: AppArmor Filesystem Enabled NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 RPC: Registered udp transport module. RPC: Registered tcp transport module. RPC: Registered tcp NFSv4.1 backchannel transport module. Power Management for Marvell Dove. PMU Detected Frequencies CPU 800Mhz, AXI 200Mhz, L2 400Mhz, DDR 400Mhz Dove hwmon thermal sensor initialized. cesadev_modinit cesadev_probe cesadev_init(c005f7cc) mvCesaInit: sessions=640, queue=64, pSram=fdb00000 audit: initializing netlink socket (disabled) type=2000 audit(0.241:1): initialized Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (no cpio magic); looks like an initrd highmem bounce pool size: 64 pages squashfs: version 4.0 (2009/01/31) Phillip Lougher JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc. msgmni has been set to 1133 alg: No test for cipher_null (cipher_null-generic) alg: No test for ecb(cipher_null) (ecb-cipher_null) alg: No test for digest_null (digest_null-generic) alg: No test for compress_null (compress_null-generic) alg: No test for stdrng (krng) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) Dove Backlight Driver start power on sequence. backlight power on first time topanel power on(FB_BLANK_UNBLANK) Dove Backlight Driver Initialized. dovedcon has been initialized. dovefb_display_init dovefb_display driver init ok. Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 7) is a 16550A console [ttyS0] enabled serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 8) is a 16550A brd: module loaded loop: module loaded mvumi:2.0.4.9 Jan 22, 2008 sata_mv sata_mv.0: version 1.28 sata_mv sata_mv.0: slots 32 ports 1 Freeing initrd memory: 18620K scsi0 : sata_mv ata1: SATA max UDMA/133 irq 62 orion_spi orion_spi.0: use polling mode m25p80 spi0.0: unrecognized JEDEC id ef4017 m25p80 spi0.0: found UNKNOWN, expected mx25l3205 MV-643xx 10/100/1000 ethernet driver version 1.4 mv643xx_eth smi: probed net eth0: port 0 with MAC address 00:80:64:e8:66:ba Registering VMETA UIO driver:. o Mapping registers at 0xf1c00000 Size 2560 KB. o Mapping buffer at 928 MB Size 95 MB. VMETA UIO driver registered successfully. ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver orion-ehci orion-ehci.0: Marvell Orion EHCI orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 orion-ehci orion-ehci.0: irq 24, io mem 0xf1050000 orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected orion-ehci orion-ehci.1: Marvell Orion EHCI orion-ehci orion-ehci.1: new USB bus registered, assigned bus number 2 ata1: SATA link down (SStatus 0 SControl F300) orion-ehci orion-ehci.1: irq 25, io mem 0xf1051000 orion-ehci orion-ehci.1: USB 2.0 started, EHCI 1.00 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 1 port detected usbcore: registered new interface driver usblp Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. usbcore: registered new interface driver ums-datafab usbcore: registered new interface driver ums-freecom usbcore: registered new interface driver ums-jumpshot usbcore: registered new interface driver ums-sddr09 usbcore: registered new interface driver ums-sddr55 eneec_init mice: PS/2 mouse device common for all mice rtc-mv rtc-mv: rtc core: registered rtc-mv as rtc0 IRQ 133/rtc-mv: IRQF_DISABLED is not guaranteed on shared IRQs i2c /dev entries driver kb3310 1-0058: KB3310 PS2 Keyboard/Mouse driver loaded! enedev driver(major 252) installed. kb3310 Read_Resp: id:91 reg:01 data:fa kb3310 Read_Resp: id:91 reg:02 data:fa kb3310 Read_Resp: id:81 reg:03 data:03 kb3310 Read_Resp: id:81 reg:10 data:01 kb3310 Read_Resp: id:81 reg:11 data:01 kb3310 Read_Resp: id:81 reg:12 data:01 kb3310 Read_Resp: id:81 reg:13 data:01 kb3310 Read_Resp: id:81 reg:14 data:01 kb3310 Read_Resp: id:81 reg:15 data:01 kb3310 Read_Resp: id:81 reg:16 data:00 kb3310 Read_Resp: id:81 reg:20 data:01 kb3310 Read_Resp: id:81 reg:21 data:01 kb3310 Read_Resp: id:81 reg:22 data:02 kb3310 Read_Resp: id:81 reg:30 data:4d kb3310 Read_Resp: id:81 reg:31 data:03 Driver for 1-wire Dallas network protocol. 1-Wire driver for the DS2760 battery monitor chip - (c) 2004-2005, Szabolcs Gyurko device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com cpuidle: using governor ladder cpuidle: using governor menu sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman sdhci: Requesting irq host->irq=35, host->irqn mmc0: SDHCI controller on sdhci-mv.0 [sdhci-mv.0] using DMA sdhci: Requesting irq host->irq=36, host->irqn mmc1: SDHCI controller on sdhci-mv.1 [sdhci-mv.1] using DMA mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) usb 1-1: new high speed USB device using orion-ehci and address 2 mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) mv_xor mv_xor.2: Marvell XOR: ( xor cpy ) mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy ) usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.21. asoc: RT5630 HiFi <-> mv88fx-i2s1 mapping ok ALSA device list: #0: Dove-I2S-RT5630 (RT5630) aufs 2-standalone.tree-20091207 oprofile: using arm/mrvl_pj4 TCP cubic registered NET: Registered protocol family 17 lib80211: common routines for IEEE802.11 drivers XScale iWMMXt coprocessor detected. VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 5 usb 1-1: configuration #1 chosen from 1 choice hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected Dove FB driver: Initialize /proc/mv_dump_lcd0 use cat /proc/mv_dump_lcd0 to see reg settings o Kernel parameter: 1024x768-32@60. ------------<GFX Layer 0 video mode database>----------- mode 0: <1920x1200@60> pico=5177 fb timings 336 128 38 1 208 3 xorg timings 1920 2048 2256 2592 1200 1201 1204 1242 mode 1: <1920x1080@60> pico=6734 fb timings 148 88 36 4 44 5 xorg timings 1920 2008 2052 2200 1080 1084 1089 1125 mode 2: <1650x1050@60> pico=6888 fb timings 288 104 33 1 184 3 xorg timings 1650 1754 1938 2226 1050 1051 1054 1087 mode 3: <1366x 768@60> pico=11659 fb timings 216 72 23 1 144 3 xorg timings 1366 1438 1582 1798 768 769 772 795 mode 4: <1280x1024@60> pico=9262 fb timings 248 48 38 1 112 3 xorg timings 1280 1328 1440 1688 1024 1025 1028 1066 mode 5: <1280x 720@60> pico=13468 fb timings 220 110 20 5 40 5 xorg timings 1280 1390 1430 1650 720 725 730 750 mode 6: <1024x 768@85> pico=10581 fb timings 208 48 36 1 96 3 xorg timings 1024 1072 1168 1376 768 769 772 808 mode 7: <1024x 768@70> pico=13346 fb timings 144 24 29 3 136 6 xorg timings 1024 1048 1184 1328 768 771 777 806 mode 8: <1024x 768@60> pico=15385 fb timings 160 24 29 3 136 6 xorg timings 1024 1048 1184 1344 768 771 777 806 mode 9: <1024x 600@60> pico=22401 fb timings 38 38 8 8 100 4 xorg timings 1024 1062 1162 1200 600 608 612 620 mode 10: < 800x 600@85> pico=17790 fb timings 152 32 27 1 64 3 xorg timings 800 832 896 1048 600 601 604 631 mode 11: < 800x 600@75> pico=20234 fb timings 160 16 21 1 80 2 xorg timings 800 816 896 1056 600 601 603 624 mode 12: < 800x 600@72> pico=20052 fb timings 64 56 23 37 120 6 xorg timings 800 856 976 1040 600 637 643 666 mode 13: < 800x 600@60> pico=25131 fb timings 88 40 23 1 128 4 xorg timings 800 840 968 1056 600 601 605 628 mode 14: < 800x 600@56> pico=26515 fb timings 128 32 14 1 128 4 xorg timings 800 832 960 1088 600 601 605 619 mode 15: < 640x 480@85> pico=27780 fb timings 112 32 25 1 48 3 xorg timings 640 672 720 832 480 481 484 509 mode 16: < 640x 480@75> pico=31746 fb timings 48 16 32 11 96 2 xorg timings 640 656 752 800 480 491 493 525 mode 17: < 640x 480@72> pico=32102 fb timings 128 24 28 9 40 3 xorg timings 640 664 704 832 480 489 492 520 mode 18: < 640x 480@60> pico=39758 fb timings 48 16 31 11 96 2 xorg timings 640 656 752 800 480 491 493 524 found <1024x768@60>, pixclock=15385 YC pitch is 0.User program needs refine Console: switching to colour frame buffer device 128x48 o dovefb: frame buffer device was successfully loaded. Dove FB driver: Initialize /proc/mv_dump_lcd1 use cat /proc/mv_dump_lcd1 to see reg settings o Kernel parameter: 1024x768-32@60. ------------<GFX Layer 1 video mode database>----------- mode 0: <1920x1200@60> pico=5177 fb timings 336 128 38 1 208 3 xorg timings 1920 2048 2256 2592 1200 1201 1204 1242 mode 1: <1920x1080@60> pico=6734 fb timings 148 88 36 4 44 5 xorg timings 1920 2008 2052 2200 1080 1084 1089 1125 mode 2: <1650x1050@60> pico=6888 fb timings 288 104 33 1 184 3 xorg timings 1650 1754 1938 2226 1050 1051 1054 1087 mode 3: <1366x 768@60> pico=11659 fb timings 216 72 23 1 144 3 xorg timings 1366 1438 1582 1798 768 769 772 795 mode 4: <1280x1024@60> pico=9262 fb timings 248 48 38 1 112 3 xorg timings 1280 1328 1440 1688 1024 1025 1028 1066 mode 5: <1280x 720@60> pico=13468 fb timings 220 110 20 5 40 5 xorg timings 1280 1390 1430 1650 720 725 730 750 mode 6: <1024x 768@85> pico=10581 fb timings 208 48 36 1 96 3 xorg timings 1024 1072 1168 1376 768 769 772 808 mode 7: <1024x 768@70> pico=13346 fb timings 144 24 29 3 136 6 xorg timings 1024 1048 1184 1328 768 771 777 806 mode 8: <1024x 768@60> pico=15385 fb timings 160 24 29 3 136 6 xorg timings 1024 1048 1184 1344 768 771 777 806 mode 9: <1024x 600@60> pico=22401 fb timings 38 38 8 8 100 4 xorg timings 1024 1062 1162 1200 600 608 612 620 mode 10: < 800x 600@85> pico=17790 fb timings 152 32 27 1 64 3 xorg timings 800 832 896 1048 600 601 604 631 mode 11: < 800x 600@75> pico=20234 fb timings 160 16 21 1 80 2 xorg timings 800 816 896 1056 600 601 603 624 mode 12: < 800x 600@72> pico=20052 fb timings 64 56 23 37 120 6 xorg timings 800 856 976 1040 600 637 643 666 mode 13: < 800x 600@60> pico=25131 fb timings 88 40 23 1 128 4 xorg timings 800 840 968 1056 600 601 605 628 mode 14: < 800x 600@56> pico=26515 fb timings 128 32 14 1 128 4 xorg timings 800 832 960 1088 600 601 605 619 mode 15: < 640x 480@85> pico=27780 fb timings 112 32 25 1 48 3 xorg timings 640 672 720 832 480 481 484 509 mode 16: < 640x 480@75> pico=31746 fb timings 48 16 32 11 96 2 xorg timings 640 656 752 800 480 491 493 525 mode 17: < 640x 480@72> pico=32102 fb timings 128 24 28 9 40 3 xorg timings 640 664 704 832 480 489 492 520 mode 18: < 640x 480@60> pico=39758 fb timings 48 16 31 11 96 2 xorg timings 640 656 752 800 480 491 493 524 found <1024x768@60>, pixclock=15385 YC pitch is 0.User program needs refine o dovefb: frame buffer device was successfully loaded. atkbd.c: keyboard reset failed on i2c/addr-58/dev-30/irq-47 rtc-mv rtc-mv: setting system clock to 2022-11-04 00:18:58 UTC (1667521138) Waiting 15sec before mounting root device... usb 1-1.1: new high speed USB device using orion-ehci and address 3 usb 1-1.1: configuration #1 chosen from 1 choice scsi1 : SCSI emulation for USB Mass Storage devices usb 1-1.2: new low speed USB device using orion-ehci and address 4 usb 1-1.2: configuration #1 chosen from 1 choice input: USB Keyboard as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input0 generic-usb 0003:04D9:1702.0001: input: USB HID v1.10 Keyboard [ USB Keyboard] on usb-orion-ehci.0-1.2/input0 input: USB Keyboard as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2:1.1/input/input1 generic-usb 0003:04D9:1702.0002: input: USB HID v1.10 Device [ USB Keyboard] on usb-orion-ehci.0-1.2/input1 usb 1-1.3: new full speed USB device using orion-ehci and address 5 usb 1-1.3: configuration #1 chosen from 1 choice input: Logitech USB Receiver as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input2 generic-usb 0003:046D:C52F.0003: input: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-orion-ehci.0-1.3/input0 input: Logitech USB Receiver as /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3:1.1/input/input3 generic-usb 0003:046D:C52F.0004: input: USB HID v1.11 Device [Logitech USB Receiver] on usb-orion-ehci.0-1.3/input1 scsi 1:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 4 sd 1:0:0:0: [sda] 15155200 512-byte logical blocks: (7.75 GB/7.22 GiB) sd 1:0:0:0: [sda] Write Protect is off sd 1:0:0:0: [sda] Assuming drive cache: write through sd 1:0:0:0: [sda] Assuming drive cache: write through sda: sda1 sda2 sd 1:0:0:0: [sda] Assuming drive cache: write through sd 1:0:0:0: [sda] Attached SCSI removable disk
|
Re: Debian on Dell Wyse T10 / T50 November 06, 2022 04:37AM |
Registered: 4 months ago Posts: 1 |
Hi there!
@wildhem but that means you have perfectly functional screen? lucky guy! :) Mine can only show 3/4 parts of the screen and only one avaialable mode.
Appart from that, I am pissed with my inhability to produce a working pair of uImage/uInitrd.
I have done what everybody else, but it just stops. After any try of replacing my kernel (from the DELL USB) 3.0.27-1-dajia , I get stucked.
I tested Debian, another Debian (for olpc), Fedora (also for olpc), and I even installed on my ubuntu 12.04 the source and started to compile it from scratch (but could not find the exact acrchitecture of my wyse, PXA2128 in the kernel menuconfig, so probably this one could not work anyhow).
I also found out that my dtb for my wyse (mmp3-dell-ariel.dtb) has diferent size compared to the same obtained from diferent source. Tested both. NaH!
# cat vmlinuz mmp3-dell-ariel.dtb > zImage
# mkimage -A arm -O linux -C none -T kernel -a 0x00008000 -e 0x00008000 -d zImage uImage
# mkimage -A arm -O linux -C none -T ramdisk -d initramfs uInitrd
With these steps I never managed to get something "bootable".
I just formated my mmcblk0 to contain the root of my ubuntu 12.04. I boot from a USB with uInitrd and uImage from USBDELL. I have screen (-ish) and SSH. My idea is to use it as low-energy consuming Home Assistant.
@wildhem but that means you have perfectly functional screen? lucky guy! :) Mine can only show 3/4 parts of the screen and only one avaialable mode.
Appart from that, I am pissed with my inhability to produce a working pair of uImage/uInitrd.
I have done what everybody else, but it just stops. After any try of replacing my kernel (from the DELL USB) 3.0.27-1-dajia , I get stucked.
I tested Debian, another Debian (for olpc), Fedora (also for olpc), and I even installed on my ubuntu 12.04 the source and started to compile it from scratch (but could not find the exact acrchitecture of my wyse, PXA2128 in the kernel menuconfig, so probably this one could not work anyhow).
I also found out that my dtb for my wyse (mmp3-dell-ariel.dtb) has diferent size compared to the same obtained from diferent source. Tested both. NaH!
# cat vmlinuz mmp3-dell-ariel.dtb > zImage
# mkimage -A arm -O linux -C none -T kernel -a 0x00008000 -e 0x00008000 -d zImage uImage
# mkimage -A arm -O linux -C none -T ramdisk -d initramfs uInitrd
With these steps I never managed to get something "bootable".
I just formated my mmcblk0 to contain the root of my ubuntu 12.04. I boot from a USB with uInitrd and uImage from USBDELL. I have screen (-ish) and SSH. My idea is to use it as low-energy consuming Home Assistant.
|
Re: Debian on Dell Wyse T10 / T50 November 06, 2022 06:00AM |
Registered: 2 years ago Posts: 27 |
karrelax Wrote:
-------------------------------------------------------
> Hi there!
> @wildhem but that means you have perfectly
> functional screen? lucky guy! :) Mine can only
> show 3/4 parts of the screen and only one
> avaialable mode.
Unfortunately, my screen does not show anything after starting debian.
Try to use the wloader from the OS_Merlin_v8.6_B013_3020_T10D_ENG package, I prepared it for you.
Could someone take detailed pictures of the wyse T50 motherboard? I am mainly interested in the area next to the minipcie slot and the SD card reader
-------------------------------------------------------
> Hi there!
> @wildhem but that means you have perfectly
> functional screen? lucky guy! :) Mine can only
> show 3/4 parts of the screen and only one
> avaialable mode.
Unfortunately, my screen does not show anything after starting debian.
Try to use the wloader from the OS_Merlin_v8.6_B013_3020_T10D_ENG package, I prepared it for you.
Could someone take detailed pictures of the wyse T50 motherboard? I am mainly interested in the area next to the minipcie slot and the SD card reader
|
Re: Debian on Dell Wyse T10 / T50 November 06, 2022 08:59AM |
Registered: 4 years ago Posts: 180 |
Hi wildhem,
here are a couple images. Not sure how long the free service will keep them online for so maybe save a local copy to be safe.
Regards,
Koen
motherboard
https://postimg.cc/wtp1khxS
detailed
https://postimg.cc/RWbtQ3Jm
here are a couple images. Not sure how long the free service will keep them online for so maybe save a local copy to be safe.
Regards,
Koen
motherboard
https://postimg.cc/wtp1khxS
detailed
https://postimg.cc/RWbtQ3Jm
|
Re: Debian on Dell Wyse T10 / T50 November 06, 2022 03:56PM |
Registered: 2 years ago Posts: 27 |
|
Re: Debian on Dell Wyse T10 / T50 November 06, 2022 04:00PM |
Registered: 5 months ago Posts: 11 |
wildhem Wrote:
-------------------------------------------------------
> Thank you so much Koen!
> Can you check what markings have probably mosfets
> marked in red? If you can read them, my green ones
> are MM6 C7, yours are the same?
> My board doesn't have all the red ones.
I was going to ask the same question.... :)
Thank you so much Koen and wildhem
-------------------------------------------------------
> Thank you so much Koen!
> Can you check what markings have probably mosfets
> marked in red? If you can read them, my green ones
> are MM6 C7, yours are the same?
> My board doesn't have all the red ones.
I was going to ask the same question.... :)
Thank you so much Koen and wildhem
|
Re: Debian on Dell Wyse T10 / T50 November 06, 2022 04:44PM |
Registered: 4 years ago Posts: 180 |
Hi wildhem,
I've taken another 2 pictures with a bright flashlight from the side to show the markings. I hope that helps.
Koen
https://postimg.cc/K4jZ8tTm
https://postimg.cc/N9fQTHP7
I've taken another 2 pictures with a bright flashlight from the side to show the markings. I hope that helps.
Koen
https://postimg.cc/K4jZ8tTm
https://postimg.cc/N9fQTHP7
|
Re: Debian on Dell Wyse T10 / T50 November 06, 2022 05:29PM |
Registered: 5 months ago Posts: 11 |
|
Re: Debian on Dell Wyse T10 / T50 January 31, 2023 09:31PM |
Registered: 8 years ago Posts: 375 |
I mentioned this before in this thread, but I've seen further posting that has me convinced that some people are confused about which Dell device they have. The Dell Wyse 3010 (sometimes listed as TX0, T10 or T50) has a single DVI-I video output and contains the Marvell Dove 88AP510 SOC, the Dell Wyse 3020 (sometimes listed as TX0D, T10D or T20D) has dual DVI-I and DVI-D video output and contains the Marvell PXA2128 @1.2GHz Dual-core SOC and is already supported in the mainline Linux kernel with mmp3-dell-ariel.dts and there is an info page at Linux on Marvell MMP. Hope this helps some as current listings on Ebay for the Dell Wyse 3020 appear to be considerably less expensive than the Dell Wyse 3010.
Ray
Ray
