Welcome! Log In Create A New Profile

Advanced

Debian on HP Thin Client T5335z

Posted by bodhi 
Re: Debian on HP Thin Client T5335z
October 15, 2018 05:17PM
Hi Koen,

> I didn't realise this was possible but after
> reading https://wiki.debian.org/Multiarch/HOWTO it
> is a bit clearer. I guess it is similar to running
> 32 bit packages on a 64 bit system.

In a way. But it is actually not that significant. amrhf and armel are both 32 bit. So their ABIs look the same to the kernel.

>
> At the moment I've got a working USB minimal
> 'hybrid' armel / armhf Debian jessie system based
> on 4.4.0 kirkwood rootfs with 4.18.5 mvebu kernel.
> Removing the old kernel and cleaning the apt cache
> results in a system of 392M which should fit on
> the internal memory as a recovery system.
>

Great!

>
> root@debian:/# cat /etc/debian_version 
> 8.11
> root@debian:/# uname -a
> Linux debian 4.18.5-mvebu-tld-1 #1 SMP PREEMPT Thu
> Aug 30 22:19:21 PDT 2018 armv7l GNU/Linux
> root@debian:/# dpkg --print-architecture
> armel
> root@debian:/# dpkg --print-foreign-architectures
> armhf
>
>
> Do you recommend upgrading this system to stretch
> before copying to the internal memory?
>

I would do upgrade to make it secured, but not needed to go to Debian 9.x for a rescue system. And then do cleanup to remove the cache to get it back to ~400MB.
apt-get update
apt-get upgrade
apt-get clean


> Also my architectures are the other way around.
> Does this matter?
>

This does not matter. The kernel does not use hard float. So when you run armel or armhf kernel it is practically the same kernel as far as Debian is concern.

When both architectures are in the rootfs, and you upgrade a package, it will be relevant which one is the native architecture, because you will pull from that distribution first.

For a main system rootfs (not rescue system), I would set native architecture to armhf and then when hard float is needed for a particular package, I would make sure that package is armhf (by doing apt-get install again). That way all existing armel packages can still be used normally until it got replaced.

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



Edited 2 time(s). Last edit at 10/15/2018 07:25PM by bodhi.
Re: Debian on HP Thin Client T5335z
October 15, 2018 06:09PM
Thanks for your help bodhi. I've copied the 'hybrid' USB system to the internal memory. Next I've set the following additional uboot environment variables.

set_recovargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 ${mtdparts} splash quiet earlyprintk=serial
bootcmd_recov=ide reset; ext2load ide 0:1 0x2000000 /boot/uImage; ext2load ide 0:1 0x3000000 /boot/uInitrd
recovery=run set_recovargs; run bootcmd_recov; bootm 0x2000000 0x3000000
bootcmd=run bootcmd_exec; run recovery

Now the device boots normal Debian stretch on the USB stick when it is present and 'hybrid' Debian jessie from the internal memory when there is no USB stick plugged in.

Koen
Re: Debian on HP Thin Client T5335z
October 15, 2018 07:42PM
Koen,

> Now the device boots normal Debian stretch on the
> USB stick when it is present and 'hybrid' Debian
> jessie from the internal memory when there is no
> USB stick plugged in.

I would use the rootfs label here to make it more resilient. I think it is ROOT. But you can relabel it, and also chnage the rescue system hostname to something unique.

set_recovargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 ${mtdparts} splash quiet earlyprintk=serial

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on HP Thin Client T5335z
October 16, 2018 02:25PM
Hi bodhi,

thanks for the advice. The thinpro setup uses root=/dev/sda1 so that 's why I set it up like that. However I've now changed the label and used the same configuration as booting from USB stick to keep things consistent. I did already change the hostname of the rescue system such that it is easy to see in my router settings which system is running. This should now be quite a reliable system with easy recovery option so I'm happy to hide the serial connection wires in the case and start using it as a replacement of my pogo E02.

Koen
Re: Debian on HP Thin Client T5335z
April 26, 2019 08:48AM
Hello. I try to install it from the flash card and in the boot process I get the following error. What is the reason?
cp -a zImage-4.12.1-kirkwood-tld-1  zImage.fdt
cat dts/dove-hp-t5335z.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.12.1-kirkwood-tld-1 -d zImage.fdt  uImage
sync

Resethub..Start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
3835355 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7245696 bytes read
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2019-04-26  13:19:19 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3835291 Bytes =  3.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes =  6.9 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported processor variant (0x560f5815).
Re: Debian on HP Thin Client T5335z
April 26, 2019 10:03AM
This is NOT kirkwood...

Use Debian-4.12.4-mvebu-tld-1-rootfs-bodhi.tar.bz2
Re: Debian on HP Thin Client T5335z
April 26, 2019 11:16AM
You're right! I confused him with HP t5325.
Re: Debian on HP Thin Client T5335z
April 26, 2019 08:45PM
WMLex,

The MVEBU rootfs is here in the released thread:

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

The instruction is here in this thread:

https://forum.doozan.com/read.php?2,66989,67269#msg-67269

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on HP Thin Client T5335z
April 29, 2019 09:53AM
Did you manage to start the video display on this thin client?
Re: Debian on HP Thin Client T5335z
April 29, 2019 05:24PM
WMLex Wrote:
-------------------------------------------------------
> Did you manage to start the video display on this
> thin client?


No, I did not have time to work on this subject. Will look into this in the future.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on HP Thin Client T5335z
March 23, 2020 12:33PM
Well I’ve tried a bunch of different things to get Xorg going -but no success. Is it accurate to say we need the xserver-Xorg-video-armada pkg to accompany the armada module in kernel? Would it be possible to default back to the dovefb so at least x can start? Vesa fbdev modesetting all report “no screens found”
Re: Debian on HP Thin Client T5335z
March 23, 2020 04:43PM
I have not given this box display any thought so don't have any idea yet.

Perhaps in a next few weeks, don't know. Self isolation will likely create a lot of free time :)

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



Edited 1 time(s). Last edit at 03/23/2020 08:27PM by bodhi.
Re: Debian on HP Thin Client T5335z
July 24, 2020 01:40AM
FYI,

I will revisit the display support for this box in a couple weeks.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on HP Thin Client T5335z
February 24, 2021 05:00AM
This updated instruction reflects the latest kernel and rootfs.

================

Here is how to boot Debian on the HP T5335z.

1. On another Linux box. Download Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 (or latest rootfs) from the release thread, create the USB rootfs (or use your existing MVEBU rootfs if you have one before for other boxes).

2. Create uImage with DTB appended (assuming the USB drive is mounted at /media/rootfs).

cd /media/rootfs/boot
cp -a zImage-5.2.9-mvebu-tld-1 zImage.fdt
cat dts/dove-hp-t5335z.dtb >> zImage.fdt 
mv uImage uImage.bak
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
sync

3. Boot

a. Unmount and remove the USB drive and attach it to the T5335z.
b. Power up and interrupt serial console.

setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial'
setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x2000000 /boot/uImage; ext2load usb 0:1 0x3000000 /boot/uInitrd'
setenv bootcmd_exec 'run set_bootargs; run bootcmd_usb; bootm 0x2000000 0x3000000'
run bootcmd_exec

4. (Deprecated).

5. To make it permannently boot into Debian rootfs on USB:

5.a Repeat Step 3 and save the envs in serial console:

setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial'
setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x2000000 /boot/uImage; ext2load usb 0:1 0x3000000 /boot/uInitrd'
setenv bootcmd_exec 'run set_bootargs; run bootcmd_usb; bootm 0x2000000 0x3000000'
run bootcmd_exec
saveenv

5.b Deprecated - Warning: The SPI flash envs is broken in the latest kernel (as of 27 Sep 2024). It's possible that it was broken long ago too, and I have not used fw_setenv on this box for a long time. So when changing u-boot envs, it must be done in serial console. fw_setenv in Debian will corrupt the flash envs space.


================

Update Nov 27, 2021

Please see this post for u-boot and u-boot envs images dump:

https://forum.doozan.com/read.php?2,66989,127769#msg-127769

These mtd0 and mtd1 dumps can be used to restore your box if it is messed up somehow. But these can only be flashed in either serial console or at Linux shell. UART booting with kwboot for this box is not possible, yet. So the safe way to install Debian on this box is still the instruction above.

IOW, don't fash these images as a quicker installation method, until there is a test done by me or other users.

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



Edited 4 time(s). Last edit at 09/28/2024 02:51PM by bodhi.
Gyan
Re: Debian on HP Thin Client T5335z
February 25, 2021 06:51AM
Hi, I have trouble locating the connector for the serial console on my t5335z.
I see two connector, a micro-jst 5 pin and 4-pin.
The 4-pin one resembles a micro-jst, but it has not exactly the same form factor.

I was able to connect to the 4 pin connector somehow, but no serial console output can be detetcted. So my doubt: is this the right point where to connect?

Can it be that my t5335z has no pre-soldered 4pin micro jst for serial console communication?

A picture to locate the right point on the motherboard would help.

Thanks a lot.
Re: Debian on HP Thin Client T5335z
February 25, 2021 07:23AM
Gyan,

I don't have a picture for it right now (probably somebody else took that). But I recorded the pinouts.

Ignore the color, the color marking was just from the microJST connector wires I used (I always do this so I can tell which wire is which after I put the case back).

(Reading from left to righ, from inside the case facing outward). So that is GND, RXD, TXD, 3.3V.

Left-Right, Inside facing out.  

MicroJST header

1. Green:  GND
2. Yellow: RxD
3. Black: TxD
4. N/A:  3.3V

The serial converter module you use will determine whether you need to cross connect TXD to RXD, RXD to TXD. Most new converter modules require cross connection. But some older CP2xxx converter modules were already crossed. So try swaping these 2 wires if you don't see any output.

If you still have trouble, post what type of serial converter module you use.

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



Edited 1 time(s). Last edit at 02/25/2021 07:27AM by bodhi.
Gyan
Re: Debian on HP Thin Client T5335z
February 25, 2021 08:27AM
Hi bodhi, thanks for you fast response.
I am using a converter with an FDI 1948-c rtc2326a chip.

Crossing or not TX and RX did not produce any change.
The converter itself works (tested it by shorting TX and rx, printout on my terminal was ok).

I have doubts on the electrical connection (had to cut a microjst conmector to make it fit to the one the board). I wonder whethwr it's best to just solder some wires from the motherboard, in the correct spots (which ones I am not sure).

Anyway, the connector I am working on is located on the west side of the board (south is the front part of the thin client, where the power button is)
Re: Debian on HP Thin Client T5335z
February 25, 2021 03:41PM
Gyan,

Found the pic (from someone's post way back) that I saved.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Attachments:
open | download - HP_T5335z_Serial_pinout.jpg (36.8 KB)
Gyan
Re: Debian on HP Thin Client T5335z
February 26, 2021 04:59AM
Hi bodhi,

Looks like that connector is not present on my unit's board (the one I mentioned is in a different position and has a slightly different shape, although still a 4-pin one).

I could find it on a t5325 unit, close to the speaker, but not on my t5335z - might be a motherboard revision with respect to your unit.

Thanks
Gyan
Re: Debian on HP Thin Client T5335z
February 26, 2021 05:08AM
Hey Gyan,

If I have a moment tomorrow, I will open the case and take the full pic for the board. That small picture was not quite clear, Only the the full view of the board would tell if you have a different version. As I recalled there is a 4-pin microJST header. But I don't recall exactly if I used a male header or just wires.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Gyan
Re: Debian on HP Thin Client T5335z
February 26, 2021 06:40AM
Thanks bodhi, your help is much appreciated :)

Gyan
Gyan
Re: Debian on HP Thin Client T5335z
February 26, 2021 10:21AM
bodhi,

I managed to get a serial console output! I will now follow your guide for Debian booting.
Do you happen to know which are the credentials to get into the stock OS?

Thanks,
Gyan
Re: Debian on HP Thin Client T5335z
February 26, 2021 04:53PM
Gyan,

Cool!

I don't recall ever log into stock OS on this box! Perhaps the credentials info is somewhere in the T5325 thread.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Debian on HP Thin Client T5335z
February 26, 2021 05:19PM
Gyan,

Try root and no password.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Gyan
Re: Debian on HP Thin Client T5335z
February 28, 2021 12:22PM
Hi bodhi,

I managed to get the boot process to start by following the latest steps you posted in this thread.
The machine is not able to boot the kernel and outputs the following message:

Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)

ALERT! LABEL=rootfs does not exist.

Any idea how I could solve this?

Thanks,

-Gyan
Gyan
Re: Debian on HP Thin Client T5335z
February 28, 2021 12:44PM
My bad: I forgot to give the label "rootfs" to the USB drive partition.

- Gyan
Gyan
Re: Debian on HP Thin Client T5335z
March 02, 2021 08:10AM
Hi bodhi,

Did you ever manage to get graphics working for the t5335z?

I tried to install the driver xserver-xorg-video-armada (can be found on github), but no results so far.

-Gyan
Re: Debian on HP Thin Client T5335z
March 02, 2021 04:06PM
Gyan,

> Did you ever manage to get graphics working for
> the t5335z?

Not yet! this is the last item on the list for this T5335z and Wyse T10/T50.

My latest kernel build was already configured to use Dove DRM (Direct Rendering Manager). But I have not tried very hard to get this working. The old frame buffer graphics driver (similar to one in stock) is no longer usable, so we would have to try to make DRM works.

(Forum member) Koen and I tried a little bit in the past but I did not have a monitor to test with this (now I do but don't have time to do testing).

Perhaps you could continue the testing? Plug in a monitor, and power on. Let it boot, capture serial consle log and post here.

I want to see if the LCD is detected by the kernel. And I might need to look at the stock u-boot source again to see how the LCD was power up in stock.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Gyan
Re: Debian on HP Thin Client T5335z
March 03, 2021 12:23PM
Hi bodhi,

Monitor is black (HDMI output from the t5335z via DVI port).
I reimaged the USB drive with a fresh Debian install, so no armada driver installed by me anymore.
Here the console log:

   	     __   _     .____    
   	    | ||_| |    |  _ \  
   	    |. _   |    | (._)))   
   	    |  |-| |    |  |      
   	    |_ | |_|.   |_ |  ...  
 ** LOADER **


U-Boot 2009.08 (Jul 01 2011 - 20:03:50)HP version: 5.4.2-V27

BootROM:
       Version on chip: 2.33
       Status: OK
       Retries #: 0
Board: RD-88AP510-Avengers
SoC:   88AP510 (A1)
CPU:   Marvell Sheeva (Rev 5)
       CPU @ 1000Mhz, L2 @ 500Mhz
Write Leveling Results:
       CS0, Lane: 0, value: 11
       CS0, Lane: 1, value: 17
       CS0, Lane: 2, value: 50
       CS0, Lane: 3, value: 34
DRAM:   1 GB
       CS 0: base 0x00000000 size  1 GB
       Addresses 12M - 0M are saved for the U-Boot usage.

Streaming disabled 
L2 Cache Prefetch disabled
L2 Cache ECC disabled
USB 0: Host Mode
USB 1: Host Mode
Setting VPU power ON.
Setting GPU power ON.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 
Resethub..Start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
5140240 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
9700490 bytes read
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-5.10.7-mvebu-tld-1
   Created:      2021-03-01  20:00:07 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5140176 Bytes =  4.9 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
   Image Name:   initramfs-5.10.7-mvebu-tld-1
   Created:      2021-03-01  20:00:20 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9700426 Bytes =  9.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.10.7-mvebu-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Sat Jan 16 19:49:06 PST 2021
[    0.000000][    T0] CPU: ARMv7 Processor [560f5815] revision 5 (ARMv7), cr=10c5387d
[    0.000000][    T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: HP Thin Client T5335z
[    0.000000][    T0] printk: bootconsole [earlycon0] enabled
[    0.000000][    T0] Memory policy: Data cache writeback
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   Normal   [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000][    T0]   HighMem  [mem 0x0000000030000000-0x000000003fffffff]
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000003fffffff]
[    0.000000][    T0] CPU: All CPU(s) started in SVC mode.
[    0.000000][    T0] percpu: Embedded 20 pages/cpu s52876 r8192 d20852 u81920
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 260608
[    0.000000][    T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=spi0.0:768k(u-boot),8k(uboot_env),8k(pu_env),8k(hp_env) earlyprintk=serial
[    0.000000][    T0] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000][    T0] Memory: 1012752K/1048576K available (10240K kernel code, 1470K rwdata, 3032K rodata, 1024K init, 361K bss, 35824K reserved, 0K cma-reserved, 262144K highmem)
[    0.000000][    T0] random: get_random_u32 called from ____cache_alloc+0x304/0x780 with crng_init=0
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] rcu: 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[    0.000000][    T0] 	Trampoline variant of Tasks RCU enabled.
[    0.000000][    T0] 	Tracing variant of Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[    0.000008][    T0] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[    0.008527][    T0] Switching to timer-based delay loop, resolution 6ns
[    0.016007][    T0] Console: colour dummy device 80x30
[    0.021204][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[    0.032415][    T0] pid_max: default: 32768 minimum: 301
[    0.038002][    T0] LSM: Security Framework initializing
[    0.043463][    T0] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.051483][    T0] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.061176][    T0] CPU: Testing write buffer coherency: ok
[    0.067066][    T1] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.074166][    T1] Setting up static identity map for 0x100000 - 0x100060
[    0.081903][    T1] rcu: Hierarchical SRCU implementation.
[    0.088675][    T1] smp: Bringing up secondary CPUs ...
[    0.093890][    T1] smp: Brought up 1 node, 1 CPU
[    0.098658][    T1] SMP: Total of 1 processors activated (333.33 BogoMIPS).
[    0.105593][    T1] CPU: All CPU(s) started in SVC mode.
[    0.111628][    T1] devtmpfs: initialized
[    0.121459][    T1] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 5
[    0.131074][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.142038][    T1] futex hash table entries: 256 (order: 2, 16384 bytes, linear)
[    0.180112][    T1] prandom32: self test passed (less than 6 bits correlated)
[    0.187233][    T1] prandom: seed boundary self test passed
[    0.195944][    T1] prandom: 100 self tests passed
[    0.200765][    T1] pinctrl core: initialized pinctrl subsystem
[    0.209642][    T1] NET: Registered protocol family 16
[    0.215784][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.226672][    T1] audit: initializing netlink subsys (disabled)
[    0.234941][    T1] thermal_sys: Registered thermal governor 'step_wise'
[    0.236375][    T1] cpuidle: using governor ladder
[    0.247996][   T28] audit: type=2000 audit(0.220:1): state=initialized audit_enabled=0 res=1
[    0.262431][    T1] cpuidle: using governor menu
[    0.267279][    T1] Dove 88AP510 SoC
[    0.271054][    T1] Tauros2: Disabling L2 prefetch.
[    0.275923][    T1] Tauros2: Disabling burst8 line fill.
[    0.281564][    T1] Tauros2: Enabling L2 cache.
[    0.286085][    T1] Tauros2: L2 cache support initialised in ARMv7 mode.
[    0.293339][    T1] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.619512][    T1] raid6: int32x8  gen()   159 MB/s
[    0.788993][    T1] raid6: int32x8  xor()    98 MB/s
[    0.958591][    T1] raid6: int32x4  gen()   173 MB/s
[    1.128665][    T1] raid6: int32x4  xor()   105 MB/s
[    1.298623][    T1] raid6: int32x2  gen()   278 MB/s
[    1.468582][    T1] raid6: int32x2  xor()   182 MB/s
[    1.638562][    T1] raid6: int32x1  gen()   348 MB/s
[    1.808544][    T1] raid6: int32x1  xor()   160 MB/s
[    1.813487][    T1] raid6: using algorithm int32x1 gen() 348 MB/s
[    1.819566][    T1] raid6: .... xor() 160 MB/s, rmw enabled
[    1.825108][    T1] raid6: using intx1 recovery algorithm
[    1.831773][    T1] vgaarb: loaded
[    1.837755][    T1] SCSI subsystem initialized
[    1.844039][    T1] usbcore: registered new interface driver usbfs
[    1.852289][    T1] usbcore: registered new interface driver hub
[    1.859005][    T1] usbcore: registered new device driver usb
[    1.865614][    T1] mc: Linux media interface: v0.10
[    1.872506][    T1] videodev: Linux video capture interface: v2.00
[    1.879442][    T1] pps_core: LinuxPPS API ver. 1 registered
[    1.885079][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.896143][    T1] PTP clock support registered
[    1.904520][    T1] clocksource: Switched to clocksource orion_clocksource
[    2.564524][    C0] random: fast init done
[    3.205730][    T1] VFS: Disk quotas dquot_6.6.0
[    3.210434][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    3.250530][    T1] NET: Registered protocol family 2
[    3.260883][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    3.270233][    T1] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    3.279033][    T1] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    3.287004][    T1] TCP: Hash tables configured (established 8192 bind 8192)
[    3.294268][    T1] MPTCP token hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    3.302448][    T1] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    3.309854][    T1] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    3.317800][    T1] NET: Registered protocol family 1
[    3.323446][    T1] RPC: Registered named UNIX socket transport module.
[    3.330106][    T1] RPC: Registered udp transport module.
[    3.335505][    T1] RPC: Registered tcp transport module.
[    3.340875][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    3.348002][    T1] PCI: CLS 0 bytes, default 64
[    3.352879][    T1] Trying to unpack rootfs image as initramfs...
[    3.972914][    T1] Freeing initrd memory: 9476K
[    3.977829][    T1] NetWinder Floating Point Emulator V0.97 (double precision)
[    3.987697][    T1] Initialise system trusted keyrings
[    3.992855][    T1] Key type blacklist registered
[    4.000774][    T1] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[    4.008133][    T1] zbud: loaded
[    4.012828][    T1] NFS: Registering the id_resolver key type
[    4.019086][    T1] Key type id_resolver registered
[    4.023945][    T1] Key type id_legacy registered
[    4.028786][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    4.036267][    T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    4.153456][    T1] xor: measuring software checksum speed
[    4.165991][    T1]    arm4regs        :  1415 MB/sec
[    4.185363][    T1]    8regs           :   688 MB/sec
[    4.198604][    T1]    32regs          :  1204 MB/sec
[    4.203631][    T1] xor: using function: arm4regs (1415 MB/sec)
[    4.209562][    T1] async_tx: api initialized (async)
[    4.214636][    T1] Key type asymmetric registered
[    4.219408][    T1] Asymmetric key parser 'x509' registered
[    4.225241][    T1] bounce: pool size: 64 pages
[    4.229912][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    4.238331][    T1] io scheduler bfq registered
[    4.245546][    T1] dove-pinctrl f10d0200.pin-ctrl: falling back to hardcoded PMU resource
[    4.254002][    T1] dove-pinctrl f10d0200.pin-ctrl: [Firmware Bug]: Missing pinctrl regs in DTB. Please update your firmware.
[    4.268713][    T1] dove-pinctrl f10d0200.pin-ctrl: registered pinctrl driver
[    4.283877][    T1] mvebu-pcie mbus:pcie: host bridge /mbus/pcie ranges:
[    4.292695][    T1] mvebu-pcie mbus:pcie:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    4.301538][    T1] mvebu-pcie mbus:pcie:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    4.310281][    T1] mvebu-pcie mbus:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    4.319426][    T1] mvebu-pcie mbus:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    4.328502][    T1] mvebu-pcie mbus:pcie:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    4.337550][    T1] mvebu-pcie mbus:pcie:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    4.347028][    T1] mvebu-pcie mbus:pcie: PCI host bridge to bus 0000:00
[    4.353707][    T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[    4.360164][    T1] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    4.371069][    T1] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    4.381967][    T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    4.389567][    T1] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    4.396666][    T1] pci 0000:00:01.0: [11ab:0510] type 01 class 0x060400
[    4.403358][    T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    4.411451][    T1] pci 0000:00:02.0: [11ab:0510] type 01 class 0x060400
[    4.418712][    T1] pci 0000:00:02.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    4.427814][    T1] PCI: bus0: Fast back to back transfers disabled
[    4.434068][    T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    4.443335][    T1] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    4.453539][    T1] PCI: bus1: Fast back to back transfers enabled
[    4.460073][    T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    4.468845][    T1] PCI: bus2: Fast back to back transfers enabled
[    4.475320][    T1] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    4.482675][    T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0000000-0xe00007ff pref]
[    4.490657][    T1] pci 0000:00:02.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[    4.498626][    T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[    4.504272][    T1] pci 0000:00:02.0: PCI bridge to [bus 02]
[    4.511339][    T1] mv_xor f1060800.dma-engine: Marvell shared XOR driver
[    4.575838][    T1] mv_xor f1060800.dma-engine: Marvell XOR (Registers Mode): ( xor cpy intr )
[    4.588276][    T1] mv_xor f1060900.dma-engine: Marvell shared XOR driver
[    4.655797][    T1] mv_xor f1060900.dma-engine: Marvell XOR (Registers Mode): ( xor cpy intr )
[    4.894418][    T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    4.907699][    T1] printk: console [ttyS0] disabled
[    4.912727][    T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 21, base_baud = 10416666) is a 16550A
[    4.926102][    T1] printk: console [ttyS0] enabled
[    4.926102][    T1] printk: console [ttyS0] enabled
[    4.936013][    T1] printk: bootconsole [earlycon0] disabled
[    4.936013][    T1] printk: bootconsole [earlycon0] disabled
[    4.948894][    T1] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 22, base_baud = 10416666) is a 16550A
[    4.962153][    T1] sata_mv f10a0000.sata-host: slots 32 ports 1
[    4.973625][    T1] scsi host0: sata_mv
[    4.978359][    T1] ata1: SATA max UDMA/133 irq 33
[    4.989387][    T1] spi-nor spi0.0: sst25vf080b (1024 Kbytes)
[    4.995980][    T1] 4 cmdlinepart partitions found on MTD device spi0.0
[    5.002565][    T1] Creating 4 MTD partitions on "spi0.0":
[    5.008220][    T1] 0x000000000000-0x0000000c0000 : "u-boot"
[    5.015917][    T1] 0x0000000c0000-0x0000000c2000 : "uboot_env"
[    5.024863][    T1] 0x0000000c2000-0x0000000c4000 : "pu_env"
[    5.033414][    T1] 0x0000000c4000-0x0000000c6000 : "hp_env"
[    5.042869][    T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[    5.053657][    T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[    5.067144][    T1] libphy: Fixed MDIO Bus: probed
[    5.079725][    T1] libphy: orion_mdio_bus: probed
[    5.105914][    T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    5.118278][    T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address f4:ce:46:24:d8:22
[    5.129496][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    5.138375][    T1] ehci-pci: EHCI PCI platform driver
[    5.143681][    T1] ehci-orion: EHCI orion driver
[    5.148932][    T1] orion-ehci f1050000.usb-host: EHCI Host Controller
[    5.155668][    T1] orion-ehci f1050000.usb-host: new USB bus registered, assigned bus number 1
[    5.164588][    T1] orion-ehci f1050000.usb-host: irq 26, io mem 0xf1050000
[    5.194578][    T1] orion-ehci f1050000.usb-host: USB 2.0 started, EHCI 1.00
[    5.201923][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    5.210897][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.218822][    T1] usb usb1: Product: EHCI Host Controller
[    5.224399][    T1] usb usb1: Manufacturer: Linux 5.10.7-mvebu-tld-1 ehci_hcd
[    5.231536][    T1] usb usb1: SerialNumber: f1050000.usb-host
[    5.238173][    T1] hub 1-0:1.0: USB hub found
[    5.243281][    T1] hub 1-0:1.0: 1 port detected
[    5.248958][    T1] orion-ehci f1051000.usb-host: EHCI Host Controller
[    5.256600][    T1] orion-ehci f1051000.usb-host: new USB bus registered, assigned bus number 2
[    5.265613][    T1] orion-ehci f1051000.usb-host: irq 27, io mem 0xf1051000
[    5.294552][    T1] orion-ehci f1051000.usb-host: USB 2.0 started, EHCI 1.00
[    5.301852][    T1] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    5.310890][    T1] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    5.318802][    T1] usb usb2: Product: EHCI Host Controller
[    5.324355][    T1] usb usb2: Manufacturer: Linux 5.10.7-mvebu-tld-1 ehci_hcd
[    5.331476][    T1] usb usb2: SerialNumber: f1051000.usb-host
[    5.338013][    T1] hub 2-0:1.0: USB hub found
[    5.343048][    T1] hub 2-0:1.0: 1 port detected
[    5.349519][    T1] usbcore: registered new interface driver usblp
[    5.357930][    T1] usbcore: registered new interface driver usb-storage
[    5.365583][    T1] mousedev: PS/2 mouse device common for all mice
[    5.375155][    T1] rtc-mv f10d8500.real-time-clock: registered as rtc0
[    5.381773][    T1] rtc-mv f10d8500.real-time-clock: setting system clock to 2021-03-03T18:05:50 UTC (1614794750)
[    5.395129][    T1] i2c /dev entries driver
[    5.403762][    T1] orion_wdt: Initial timeout 25 sec
[    5.412824][    T1] device-mapper: uevent: version 1.0.3
[    5.419496][    T1] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
[    5.429444][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[    5.436808][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[    5.444087][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
[    5.451482][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    5.458492][    T1] device-mapper: raid: Loading target version 1.15.1
[    5.468928][    T1] marvell-cesa f1030000.crypto-engine: CESA device successfully registered
[    5.477425][ T1242] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[    5.485655][    T1] hid: raw HID events driver (C) Jiri Kosina
[    5.491630][ T1242] ata1.00: ATA-7: JMicron, 100415, max UDMA/133
[    5.499013][ T1242] ata1.00: 946176 sectors, multi 1: LBA48 
[    5.505451][    T1] usbcore: registered new interface driver usbhid
[    5.511693][    T1] usbhid: USB HID core driver
[    5.518051][    T1] drop_monitor: Initializing network drop monitor service
[    5.525278][ T1242] ata1.00: configured for UDMA/133
[    5.531561][    T1] NET: Registered protocol family 10
[    5.537951][    T1] Segment Routing with IPv6
[    5.542740][   T15] scsi 0:0:0:0: Direct-Access     ATA      JMicron          15   PQ: 0 ANSI: 5
[    5.551758][    T1] RPL Segment Routing with IPv6
[    5.557946][    T7] sd 0:0:0:0: [sda] 946176 512-byte logical blocks: (484 MB/462 MiB)
[    5.566537][    T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    5.575111][    T7] sd 0:0:0:0: [sda] Write Protect is off
[    5.582320][    T1] NET: Registered protocol family 17
[    5.588773][    T7] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    5.598937][    T1] 8021q: 802.1Q VLAN Support v1.8
[    5.603861][    T1] Key type dns_resolver registered
[    5.610471][    T7]  sda: sda1
[    5.614029][    T1] ThumbEE CPU extension supported.
[    5.619060][   T19] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    5.627854][    T7] sd 0:0:0:0: [sda] Attached SCSI disk
[    5.634113][    T1] Registering SWP/SWPB emulation handler
[    5.639764][    T1] PJ4 iWMMXt v2 coprocessor enabled.
[    5.645296][    T1] registered taskstats version 1
[    5.650109][    T1] Loading compiled-in X.509 certificates
[    5.656057][    T1] zswap: loaded using pool lzo/zbud
[    5.661462][    T1] Key type ._fscrypt registered
[    5.666223][    T1] Key type .fscrypt registered
[    5.670826][    T1] Key type fscrypt-provisioning registered
[    5.678970][    T1] Key type big_key registered
[    5.709320][    T1] Key type encrypted registered
[    5.722941][    T1] Freeing unused kernel memory: 1024K
[    5.746781][    T1] Checked W+X mappings: passed, no W+X pages found
[    5.753126][    T1] Run /init as init process
Loading, please wait...
[    5.835277][   T19] usb 1-1: New USB device found, idVendor=058f, idProduct=6254, bcdDevice= 1.00
[    5.844140][   T19] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    5.858152][   T19] hub 1-1:1.0: USB hub found
[    5.869096][   T19] hub 1-1:1.0: 4 ports detected
Starting version 241
[    6.194646][   T19] usb 1-1.4: new high-speed USB device number 3 using orion-ehci
[    6.365643][   T19] usb 1-1.4: New USB device found, idVendor=abcd, idProduct=1234, bcdDevice= 1.00
[    6.391898][   T19] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    6.418962][   T19] usb 1-1.4: Product: 1
[    6.422966][   T19] usb 1-1.4: Manufacturer: 1
[    6.446618][   T19] usb 1-1.4: SerialNumber: Љ
[    6.457356][   T19] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[    6.480383][   T19] scsi host1: usb-storage 1-1.4:1.0
[    6.657415][ T1493] usbcore: registered new interface driver uas
[    7.065254][ T1491] i2c i2c-0: Added multiplexed i2c bus 1
[    7.126984][ T1491] i2c i2c-0: Added multiplexed i2c bus 2
[    7.176715][ T1491] i2c i2c-0: Added multiplexed i2c bus 3
[    7.250836][ T1498] sdhci: Secure Digital Host Controller Interface driver
[    7.340723][ T1498] sdhci: Copyright(c) Pierre Ossman
[    7.395606][ T1490] sdhci-pltfm: SDHCI platform and OF driver helper
[    7.403446][ T1436] mmc0 bounce up to 128 segments into one, max segment size 65536 bytes
[    7.447099][ T1436] mmc0: SDHCI controller on f1090000.sdio-host [f1090000.sdio-host] using DMA
[    7.467550][    T7] mmc1 bounce up to 128 segments into one, max segment size 65536 bytes
[    7.520134][    T7] mmc1: SDHCI controller on f1092000.sdio-host [f1092000.sdio-host] using DMA
[    7.621775][    T7] scsi 1:0:0:0: Direct-Access     General  UDisk            5.00 PQ: 0 ANSI: 2
[    7.649939][ T1436] sd 1:0:0:0: [sdb] 16384000 512-byte logical blocks: (8.39 GB/7.81 GiB)
[    7.675061][ T1436] sd 1:0:0:0: [sdb] Write Protect is off
[    7.686264][ T1436] sd 1:0:0:0: [sdb] No Caching mode page found
[    7.692292][ T1436] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[    7.780422][ T1436]  sdb: sdb1
[    7.789812][ T1436] sd 1:0:0:0: [sdb] Attached SCSI removable disk
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[   20.201822][ T1516] process '/usr/bin/fstype' started with executable stack
Begin: Will now check root file system ... fsck from util-linux 2.33.1
[/sbin/fsck.ext2 (1) -- /dev/sdb1] fsck.ext2 -a -C0 /dev/sdb1 
rootfs: clean, 27034/511056 files, 334147/2047744 blocks
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.

INIT: version 2.93 booting

Re: Debian on HP Thin Client T5335z
March 03, 2021 04:49PM
Gyan,

Thanks! I'll take a look closely later.

I forgot one more piece of info (too see if the DRM driver was loaded correctly):

lsmod

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

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: