Welcome! Log In Create A New Profile

Advanced

HP T5325 Thin Client Debian

Posted by Gravelrash 
HP T5325 Thin Client Debian
January 27, 2016 01:34PM
@bodhi

Below are the attached and unfiltered outputs as taken straight from the unit - I was lucky in that the default password for the root account hadnt been changed (pheew)

Attached are the outputs from the following : fstab : fw_printenv : fdisk -l : dmesg

I havent got as far as attempting to do a kwboot with the device as I am going to have to get my soldering iron in there, the connector for the serial console is absolutely tiny, so small that it makes the one on the Pogoplug pink look like giant

I hope you can help with this one

EDIT 2 : link to original discussion to create consistency for anyone following
http://forum.doozan.com/read.php?8,25389

============================
Breaking stuff since 1994 :-)
============================



Edited 4 time(s). Last edit at 02/29/2016 07:00PM by Gravelrash.
Attachments:
open | download - dmesg.txt (12.5 KB)
open | download - fdisk and fstab.txt (775 bytes)
open | download - printenv.txt (1.9 KB)
Re: HP T5325 Thin Client Debian
January 27, 2016 05:34PM
I have one of these and the stock firmware is Debian Lenny. You can see the entry I created on wikidevi about 2 years ago for more details (https://wikidevi.com/wiki/HP_t5325).
Re: HP T5325 Thin Client Debian
January 27, 2016 06:37PM
@rayknight
are you running the current uboot and filesystem from bodhi? if so what did you do to get it working
Re: HP T5325 Thin Client Debian
January 27, 2016 10:34PM
Gravelrash,

Looks good so far! Please post these in code tags (attached files are hard to read):

cat /etc/fw_env.config
fw_printenv
which fw_setenv
dpkg -l | grep -i mtd
cat /proc/mtd
ls -l /dev/mtd*

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 3 time(s). Last edit at 01/28/2016 05:03AM by bodhi.
Re: HP T5325 Thin Client Debian
January 28, 2016 05:01AM
With serial console, booting the latest Debian rootfs will be much easier and safer. Everything I've seen telling me that we'll able to do that.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 28, 2016 07:27AM
cat /etc/fw_env.config
root@HPf4ce462327d3:/# cat /etc/fw_env.config
cat: /etc/fw_env.config: No such file or directory


fw_printenv
root@HPf4ce462327d3:/# fw_printenv
baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
run_diag=no
console=console=ttyS0,115200 mtdparts=spi_flash:0x80000@0(uboot)ro,0x80000@0x80000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
usb_bootargs=root=/dev/ram rw
bootusb=usb start;fatload usb 0 0x800000 /boot/uImage.usb;fatload usb 0 0x1100000 /boot/uInitrd.usb
usbboot=setenv bootargs $(usb_bootargs); run bootusb; bootm 0x800000 0x1100000
thinpro_bootargs=root=/dev/sda1 rw init=/init video=xgifb splash quiet
thinpro=ide reset; ext2load ide 0:1 0x200000 /boot/uImage; wol; setenv bootargs $(thinpro_bootargs); bootm 0x200000
pcieTune=yes
mfgmode=setenv bootdelay 3; setenv in_mfg yes;setenvh GotoWOL Yes; setenvh WOLEnabled No; setenv bootcmd run mfgboot; saveenv; reset
mfgbootargs=setenv bootargs root=/dev/sdb1 rw init=/init ip=dhcp rootdelay=8 $(console) udevtimeout=8
mfgboot=usb start; ext2load usb 0:1 0x2000000 /boot/uImage; run mfgbootargs; bootm 0x2000000
product=setenv bootdelay 1; setenv in_mfg no;setenvh GotoWOL No; setenvh WOLEnabled Yes; setenv bootcmd run thinpro; saveenv; reset
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
ethaddr=f4:ce:46:23:27:d3
gatewayip=10.4.50.5
netmask=255.255.255.0
ipaddr=10.4.50.151
serverip=10.4.50.5
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes
bootdelay=1
in_mfg=no
bootcmd=run thinpro
root@HPf4ce462327d3:/#

which fw_setenv
root@HPf4ce462327d3:/# which fw_setenv
/usr/sbin/fw_setenv

dpkg -l | grep -i mtd
root@HPf4ce462327d3:/# dpkg -l | grep -i mtd
root@HPf4ce462327d3:/#

cat /proc/mtd
root@HPf4ce462327d3:/# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00010000 00010000 "u-boot env"
mtd1: 00010000 00010000 "permanent u-boot env"
mtd2: 00010000 00010000 "HP env"
mtd3: 00080000 00010000 "u-boot"
mtd4: 00040000 00010000 "SSD firmware"

ls -l /dev/mtd*
root@HPf4ce462327d3:/# ls -l /dev/mtd*
crw-rw---- 1 root root 90, 0 Jan 28 12:11 /dev/mtd0
crw-rw---- 1 root root 90, 1 Jan 28 12:11 /dev/mtd0ro
crw-rw---- 1 root root 90, 2 Jan 28 12:11 /dev/mtd1
crw-rw---- 1 root root 90, 3 Jan 28 12:11 /dev/mtd1ro
crw-rw---- 1 root root 90, 4 Jan 28 12:11 /dev/mtd2
crw-rw---- 1 root root 90, 5 Jan 28 12:11 /dev/mtd2ro
crw-rw---- 1 root root 90, 6 Jan 28 12:11 /dev/mtd3
crw-rw---- 1 root root 90, 7 Jan 28 12:11 /dev/mtd3ro
crw-rw---- 1 root root 90, 8 Jan 28 12:11 /dev/mtd4
crw-rw---- 1 root root 90, 9 Jan 28 12:11 /dev/mtd4ro
brw-rw---- 1 root disk 31, 0 Jan 28 12:11 /dev/mtdblock0
brw-rw---- 1 root disk 31, 1 Jan 28 12:11 /dev/mtdblock1
brw-rw---- 1 root disk 31, 2 Jan 28 12:11 /dev/mtdblock2
brw-rw---- 1 root disk 31, 3 Jan 28 12:11 /dev/mtdblock3
brw-rw---- 1 root disk 31, 4 Jan 28 12:11 /dev/mtdblock4

fdisk and fstab
:: FDISK ::
Disk /dev/sda: 486 MB, 486162432 bytes
16 heads, 63 sectors/track, 942 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         942      474736+  83  Linux

----------------------------------------------------------------

:: /etc/fstab ::
LABEL=ROOT	/.flash		ext3		noauto,rw	0	0
/dev/loop0	/.flash/origfs	squashfs	noauto,ro	0	0
aufs		/		aufs		noauto,ro,noplink,br:/.flash/root-cow=rw:/.flash/origfs=rr	0	0
aufs		/writable	aufs		noauto,rw,noplink,br:/.flash/writable-cow=rw:/.flash/origfs/writable=rr	0	0
proc		/proc		proc		defaults 0	0
none		/tmp		tmpfs		rw	 0	0

----------------------------------------------------------------

DMESG
[    0.000000] Linux version 2.6.22.18-2-armel (root@lenny-devel) (gcc version 4.2.1) #1 PREEMPT Tue Nov 17 13:34:38 EST 2009
[    0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 131072
[    0.000000]   DMA zone: 1024 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 130048 pages, LIFO batch:31
[    0.000000]   Normal zone: 0 pages used for memmap
[    0.000000] CPU0: D VIVT write-back cache
[    0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] Built 1 zonelists.  Total pages: 130048
[    0.000000] Kernel command line: root=/dev/sda1 rw init=/init video=xgifb splash quiet
[    0.000000] PID hash table entries: 2048 (order: 11, 8192 bytes)
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.020000] Memory: 256MB 256MB 0MB 0MB = 512MB total
[    0.020000] Memory: 515584KB available (3508K code, 463K data, 108K init)
[    0.020000] Calibrating delay loop... 1199.30 BogoMIPS (lpj=5996544)
[    0.250000] Security Framework v1.0.0 initialized
[    0.250000] SELinux:  Disabled at boot.
[    0.250000] Capability LSM initialized
[    0.250000] Mount-cache hash table entries: 512
[    0.250000] CPU: Testing write buffer coherency: ok
[    0.250000] NET: Registered protocol family 16
[    0.250000] 
[    0.250000] CPU Interface
[    0.250000] -------------
[    0.250000] SDRAM_CS0 ....base 00000000, size 256MB 
[    0.250000] SDRAM_CS1 ....base 10000000, size 256MB 
[    0.250000] SDRAM_CS2 ....disable
[    0.250000] SDRAM_CS3 ....disable
[    0.250000] PEX0_MEM ....base e8000000, size 128MB 
[    0.250000] PEX0_IO ....base f2000000, size   1MB 
[    0.250000] INTER_REGS ....base f1000000, size   1MB 
[    0.250000] NFLASH_CS ....base fa000000, size   2MB 
[    0.250000] SPI_CS ....base f4000000, size  16MB 
[    0.250000] BOOT_ROM_CS ....no such
[    0.250000] DEV_BOOTCS ....no such
[    0.250000] CRYPT_ENG ....base f0000000, size   2MB 
[    0.250000] 
[    0.250000]   Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- OpenRD-Base  Soc: 88F6281 A0 LE
[    0.250000] 
[    0.250000]  Detected Tclk 200000000 and SysClk 400000000 
[    0.250000] MV Buttons Device Load
[    0.250000] rt5623 Codec device register
[    0.250000] Marvell USB EHCI Host controller #0: c0893200
[    0.750000] PEX0 interface detected Link X1
[    0.750000] PCI: bus0: Fast back to back transfers disabled
[    0.750000] SCSI subsystem initialized
[    0.760000] usbcore: registered new interface driver usbfs
[    0.760000] usbcore: registered new interface driver hub
[    0.760000] usbcore: registered new device driver usb
[    0.760000] NET: Registered protocol family 2
[    0.770000] Time: kw_clocksource clocksource has been installed.
[    0.770000] Switched to high resolution mode on CPU 0
[    0.850000] IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.850000] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
[    0.850000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[    0.850000] TCP: Hash tables configured (established 65536 bind 65536)
[    0.850000] TCP reno registered
[    0.880000] RTC registered
[    0.880000] Use the XOR engines (acceleration) for enhancing the following functions:
[    0.880000]   o RAID 5 Xor calculation
[    0.880000]   o kernel memcpy
[    0.880000]   o kenrel memzero
[    0.880000] Number of XOR engines to use: 4
[    0.880000] CESA test started: bufNum = 1, bufSize = 20000
[    0.880000] Cesa Test Start: pMbufSrc=c092f000, pFragsSrc=c08ae000, pMbufDst=c0929000, pFragsDst=c08f0000
[    0.900000] mvCesaInit: sessions=32, queue=252, pSram=f0000000
[    0.920000] cesadev_init(c0010edc)
[    0.920000] Warning: TS unit is powered off.
[    0.920000] MV Buttons Driver Load
[    0.920000] audit: initializing netlink socket (disabled)
[    0.920000] audit(1453933386.889:1): initialized
[    0.920000] VFS: Disk quotas dquot_6.5.1
[    0.920000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.920000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[    0.920000] squashfs: LZMA suppport for slax.org by jro
[    0.920000] aufs 20090126
[    0.920000] io scheduler noop registered
[    0.920000] io scheduler cfq registered (default)
[    0.920000] XGIfb: Options <NULL>
[    0.920000] XGIfb: Relocate IO address: 1000 [00001030] 
[    0.920000] XGIfb: Enable PCI device
[    0.920000] XGIfb: SR14=41 DramSzie 1000000 ChannelNum 1
[    0.920000] XGIfb: Framebuffer at 0xe8000000, mapped to 0xe1000000, size 16384k
[    0.920000] XGIfb: MMIO at 0xec000000, mapped to 0xe0880000, size 256k
[    0.920000] XGIfb: XGIInitNew() ...OK
[    0.920000] XGIfb: Memory heap starting at 8192K
[    0.920000] XGIfb: Default mode is 1024x768x16 (60Hz)
[    0.920000] XGIfb: Change mode to 1024x768x16-60Hz
[    0.970000] Console: switching to colour frame buffer device 128x48
[    1.020000] XGIfb: Installed XGIFB_GET_INFO ioctl (80046ef8)
[    1.020000] fb0:  frame buffer device, Version 0.8.01
[    1.040000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    1.040000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    1.040000] serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A
[    1.040000] RAMDISK driver initialized: 16 RAM disks of 8192K size 4096 blocksize
[    1.040000] loop: module loaded
[    1.040000] Loading Marvell Ethernet Driver:
[    1.040000]   o Cached descriptors in DRAM
[    1.040000]   o DRAM SW cache-coherency
[    1.040000]   o Single RX Queue support - ETH_DEF_RXQ=0
[    1.040000]   o Single TX Queue support - ETH_DEF_TXQ=0
[    1.040000]   o TCP segmentation offload enabled
[    1.040000]   o Receive checksum offload enabled
[    1.040000]   o Transmit checksum offload enabled
[    1.040000]   o Network Fast Processing (Routing) supported
[    1.040000]   o Driver ERROR statistics enabled
[    1.040000]   o Driver INFO statistics enabled
[    1.040000]   o Proc tool API enabled
[    1.040000]   o Rx descripors: q0=128
[    1.040000]   o Tx descripors: q0=532
[    1.040000]   o Loading network interface(s):
[    1.050000]     o  register under eth%d platform
[    1.050000]     o eth0, ifindex = 1, GbE port = 0
[    1.050000]     o eth1, ifindex = 2, GbE port = 1
[    1.050000] 
[    1.050000] mvFpRuleDb (de710000): 16384 entries, 65536 bytes
[    1.050000] Integrated Sata device found
[    1.070000] scsi0 : Marvell SCSI to SATA adapter
[    1.070000] scsi1 : Marvell SCSI to SATA adapter
[    1.070000] SPI Serial flash detected @ 0xf4000000, 1024KB (16sec x 64KB)
[    1.070000] Creating 5 MTD partitions on "spi_flash":
[    1.070000] 0x000c0000-0x000d0000 : "u-boot env"
[    1.070000] 0x000d0000-0x000e0000 : "permanent u-boot env"
[    1.070000] 0x000e0000-0x000f0000 : "HP env"
[    1.070000] 0x00000000-0x00080000 : "u-boot"
[    1.080000] 0x00080000-0x000c0000 : "SSD firmware"
[    1.080000] usbmon: debugfs is not available
[    1.080000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.080000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.110000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.130000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    1.130000] usb usb1: configuration #1 chosen from 1 choice
[    1.130000] hub 1-0:1.0: USB hub found
[    1.130000] hub 1-0:1.0: 1 port detected
[    1.240000] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.240000] mice: PS/2 mouse device common for all mice
[    1.240000] i2c /dev entries driver
[    1.240000] Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC).
[    1.240000] ASoC version 0.13.1
[    1.240000] rt5623: RT5623 Audio Codec 0.01
[    1.240000] asoc: RT5623 <-> mv88fx_-i2s mapping ok
[    1.250000] rt5623_codec_probe OK
[    1.250000] ALSA device list:
[    1.250000]   #0: Dove (RT5623)
[    1.250000] Mirror/redirect action on
[    1.250000] TCP cubic registered
[    1.250000] NET: Registered protocol family 17
[    1.250000] scsi: waiting for bus probes to complete ...
[    1.520000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[    1.610000] scsi 0:0:0:0: Direct-Access     ATA      SM224            I052 PQ: 0 ANSI: 5
[    1.610000] sd 0:0:0:0: [sda] 949536 512-byte hardware sectors (486 MB)
[    1.610000] sd 0:0:0:0: [sda] Write Protect is off
[    1.610000] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[    1.610000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.610000] sd 0:0:0:0: [sda] 949536 512-byte hardware sectors (486 MB)
[    1.610000] sd 0:0:0:0: [sda] Write Protect is off
[    1.610000] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[    1.610000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.610000]  sda: sda1
[    1.610000] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.610000] kjournald starting.  Commit interval 5 seconds
[    1.620000] EXT3 FS on sda1, internal journal
[    1.620000] EXT3-fs: mounted filesystem with ordered data mode.
[    1.620000] VFS: Mounted root (ext3 filesystem).
[    1.620000] Freeing init memory: 108K
[    1.620000] Warning: unable to open an initial console.
[    1.700000] usb 1-1: configuration #1 chosen from 1 choice
[    1.710000] hub 1-1:1.0: USB hub found
[    1.710000] hub 1-1:1.0: 4 ports detected
[    2.010000] NET: Registered protocol family 1
[    2.080000] usb 1-1.1: new full speed USB device using ehci_marvell and address 3
[    2.180000] usb 1-1.1: configuration #1 chosen from 1 choice
[    2.320000] usbcore: registered new interface driver hiddev
[    2.460000] input: Logitech USB Receiver as /class/input/input0
[    2.460000] input: USB HID v1.11 Keyboard [Logitech USB Receiver] on usb-ehci_marvell.70059-1.1
[    2.500000] input: Logitech USB Receiver as /class/input/input1
[    2.500000] input,hiddev96: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-ehci_marvell.70059-1.1
[    2.540000] hiddev97: USB HID v1.11 Device [Logitech USB Receiver] on usb-ehci_marvell.70059-1.1
[    2.540000] usbcore: registered new interface driver usbhid
[    2.540000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    4.890000] EXT3 FS on sda1, internal journal
[    7.050000] udevd version 125 started
[   27.700000] NET: Registered protocol family 10
[   27.700000] lo: Disabled Privacy Extensions
[   27.700000] Mobile IPv6
[   35.290000] XGIfb: Change mode to 1024x768x16-60Hz
[   35.630000] phys_mem_access_prot called - offset f2001000, uncached_access = -1071249904
[   37.310000] eth0: link up, full duplex, speed 100 Mbps
[   37.310000] eth0: started
[   37.570000] phys_mem_access_prot called - offset ec000000, uncached_access = -1071249904
[   37.570000] phys_mem_access_prot called - offset e8000000, uncached_access = -1071249904
[   48.260000] eth0: no IPv6 routers present
[  649.790000] usb 1-1.2: new high speed USB device using ehci_marvell and address 4
[  649.890000] usb 1-1.2: configuration #1 chosen from 1 choice
[  650.110000] Initializing USB Mass Storage driver...
[  650.120000] scsi2 : SCSI emulation for USB Mass Storage devices
[  650.120000] usb-storage: device found at 4
[  650.120000] usb-storage: waiting for device to settle before scanning
[  650.120000] usbcore: registered new interface driver usb-storage
[  650.120000] USB Mass Storage support registered.
[  655.120000] usb-storage: device scan complete
[  655.120000] scsi 2:0:0:0: Direct-Access     SanDisk  Cruzer           8.02 PQ: 0 ANSI: 0 CCS
[  655.140000] sd 2:0:0:0: [sdb] 3907583 512-byte hardware sectors (2001 MB)
[  655.150000] sd 2:0:0:0: [sdb] Write Protect is off
[  655.150000] sd 2:0:0:0: [sdb] Mode Sense: 45 00 00 08
[  655.150000] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[  655.170000] sd 2:0:0:0: [sdb] 3907583 512-byte hardware sectors (2001 MB)
[  655.190000] sd 2:0:0:0: [sdb] Write Protect is off
[  655.190000] sd 2:0:0:0: [sdb] Mode Sense: 45 00 00 08
[  655.190000] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[  655.190000]  sdb: sdb1
[  655.200000] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[  655.730000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Re: HP T5325 Thin Client Debian
January 28, 2016 08:01AM
1. Debian:

usb_bootargs=root=/dev/ram rw
bootusb=usb start;fatload usb 0 0x800000 /boot/uImage.usb;fatload usb 0 0x1100000 /boot/uInitrd.usb
usbboot=setenv bootargs $(usb_bootargs); run bootusb; bootm 0x800000 0x1100000
bootcmd=run thinpro

We could change these to boot the new rootfs now. But to be safe, we should do that in serial console.

2. U-Boot:

UART booting is important. If UART booting works then this should be a lot easier.

3. One more check (why are we seeing "/etc/fw_env.config: No such file or directory", perhaps this rootfs is too old)

dpkg -l | grep u-boot

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 28, 2016 09:19AM
@bodhi

1 & 2
I will attempt the UART boot after solder this weekend - if it doesn't pan out that i can get serial console access in any sensible way. I have no problem "living dangerously" and issuing the commands from a live system...

3 dpkg -l | grep u-boot
root@HPf4ce462327d3:~# cd /
root@HPf4ce462327d3:/# dpkg -l | grep u-boot
root@HPf4ce462327d3:/#

and just for fun
root@HPf4ce462327d3:/# uname -a
Linux HPf4ce462327d3 2.6.22.18-2-armel #1 PREEMPT Tue Nov 17 13:34:38 EST 2009 armv5tejl GNU/Linux

root@HPf4ce462327d3:/etc# cat /etc/debian_version 
5.0.5

Im gonna go with not so much old as "archaic" :)
Re: HP T5325 Thin Client Debian
January 28, 2016 02:15PM
Gravelrash,

> I will attempt the UART boot after solder this
> weekend - if it doesn't pan out that i can get
> serial console access in any sensible way. I have
> no problem "living dangerously" and issuing the
> commands from a live system...
>

I know :)

The current set of envs looks sane enough that I don't think we gonna get lock out even if we change these in live system. I have not seen stock serial bootlog, so I can only guess: it looks as though this box has been modded before to add USB booting envs. But it does not point to USB rootfs, so I'm so sure, perhaps the previous owner failed to make it boot with USB so it got sold.

>
> Im gonna go with not so much old as "archaic" :)

6 years is ancient!

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 28, 2016 02:48PM
bodhi Wrote:
-------------------------------------------------------
>
it looks as though this box has been modded before to add USB booting envs. But it does not point to USB rootfs, so I'm so sure, perhaps the previous owner failed to make it boot with USB so it got sold.
>

apparently usb booting on this device is a standard feature, according to the manual for the device, is the way to recover the system and update the "firmware".

I wonder if "Uncle Google" has any answers where i can locate the tools they are talking about and possibly an old image....

(trouble shooting guide) http://h20566.www2.hp.com/hpsc/doc/public/display?docId=emr_na-c01940143
Creating a Bootable USB Flash Drive Page - 29

To create a bootable USB flash drive for purposes of reflashing or restoring the software image on
the onboard flash, see the HP ThinPro Administrator’s Guide, section HP ThinState Utility >
Manage the ThinPro Image > Capture HP ThinPro Image to a Bootable USB Flash Drive.
NOTE: During the restore process, the thin client flash drive is reformatted and all data is erased
before the system image is copied to it. To prevent loss of data, be sure to save any user-created
data from the flash drive. Restoring the software image may take approximately five minutes.

Booting from a USB Flash Drive

To boot the USB flash drive created in the previous section:
1. Power off the unit.
2. Insert the ThinState drive into one of the USB slots on the thin client.
3. Press and release the power button, and then quickly press and release the power button again.
4. After about 15 seconds, the unit beeps and a dialog is displayed verifying that you wish to reimage
the device.
NOTE: Some USB flash drives may not work. If the unit does not boot from the USB flash drive, try
removing all other USB devices and insert the USB flash drive into one of the rear USB ports. If the
unit still does not boot from the USB flash drive, try a different flash drive.

Restoring a Corrupt uBoot page 30
If uBoot on the thin client is corrupt, the unit will not boot. The unit must be sent back for repair.
Updating uBoot
To update uBoot:
1. Create a ThinState key as described in Restoring the Flash Image on page 29.
2. Insert the key into a computer.
3. Edit the file settings.ini to set useQuickImageMode to 0.
4. Save the file.
5. Copy the new uBoot binary to the uBoot directory on the USB drive.
6. Safely remove the USB drive from the computer
7. Boot the ThinState USB drive as described in Booting from a USB Flash Drive on page 29.
8. After about 15 seconds, the unit beeps and a menu is displayed.
9. Type 4 to enter “Update uBoot Mode” and follow the on-screen prompts.
CAUTION: Do not turn off power or attempt to reboot the computer during the upgrade process.

P.S. I cant believe i have just publicly soiled my "man cred" by admitting to reading a manual.....luckily the other half never reads this forum
:) :)
Re: HP T5325 Thin Client Debian
January 28, 2016 02:57PM
> apparently usb booting on this device is a
> standard feature, according to the manual for the
> device, is the way to recover the system and
> update the "firmware".

Cool! it means this is the recovery path if we can't get UART booting to work. It would be educational to see the content of this USB drive.

> P.S. I cant believe i have just publicly soiled my
> "man cred" by admitting to reading a
> manual.....luckily the other half never reads this
> forum
> :) :)

Too late, but tell your other half that sometimes we do RTFM :)

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 28, 2016 03:08PM
bodhi Wrote:
-------------------------------------------------------
> Cool! it means this is the recovery path if we
> can't get UART booting to work. It would be
> educational to see the content of this USB drive.

"Uncle Google" came up trumps - not only do i have the information I also have the original HP pdf... so first thing when i get home this evening is to attempt the backup following the procedure as described in the manual.

Hopefully time will allow for me to dd the image off the usb disk and ill upload it do dropbox and share it from there if you are inerested??
Re: HP T5325 Thin Client Debian
January 28, 2016 03:30PM
Gravelrash,

> Hopefully time will allow for me to dd the image
> off the usb disk and ill upload it do dropbox and
> share it from there if you are inerested??

Sure, only at your convenience, no hurry.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 29, 2016 03:58AM
looking good so far... The creation of the recovery disk went well and i know have the disk ready.

The format of the disk is as follows.

Its a fat32 file system with the below directory structure and files

gravelrash@40 ~ $ cd /media/gravelrash/HPTC\ Imgr/
gravelrash@40 /media/gravelrash/HPTC Imgr $ ls -R
.:
boot  images  init.sh  settings.ini  uboot

./boot:
uImage.dove.usb  uImage.usb  uInitrd.dove.usb  uInitrd.usb

./images:
ThinPro-T5A32014-2016-01-28.dd.gz

./uboot:
u-boot-3.4.19_V16.bin

gravelrash@40 /media/gravelrash/HPTC Imgr $ 

Re: HP T5325 Thin Client Debian
January 29, 2016 04:36PM
Interesting! stock u-boot must have implemented the power button command to start this recovery process (running init.sh script).

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 29, 2016 05:15PM
I wonder if thats something that could be used on other boxes for making upgrades etc easier....
Re: HP T5325 Thin Client Debian
January 29, 2016 05:27PM
Gravelrash Wrote:
-------------------------------------------------------
> I wonder if thats something that could be used on
> other boxes for making upgrades etc easier....

Sure, for boxes that have button (nsa3xx, nsa3xxs, pogo v4, iconnect, goflex home,...) that could be done. The nsa325 u-boot-2015.10 currently has button capability. You have caused a lightbulb :) which boxes do you have?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 30, 2016 06:55AM
I currently have
Pogo V4 sata and none sata - kernel 3.14
Pogo V3 - kernel 3.18.5
Pogo V2 - arch and 3.18

HP Thinclient (arm and Intel)

and some Orange Pi Ones on order awaiting delivery



Edited 1 time(s). Last edit at 01/30/2016 06:57AM by Gravelrash.
Re: HP T5325 Thin Client Debian
January 30, 2016 09:13AM
Time to "live dangerously" - wasnt able to solder in the appropriate cable to get a uart boot. or for that matter attempt a kwboot.

but for anyone thats interested - the pinout on the uart port is the same as the Pogoplug - seems to be a standard across the marvel kirkwood range

Looking from the front of the board / device the pins are as follows

Left ---------------------------> Right

|| 3.3v Power  || Tx || RX || Ground ||  
===========================

Left ---------------------------> Right


along with finding the above out from another forum, dont ask me which one - my laptop threw a wobbly and i couldnt find it again, i managed to find the following piece of uboot log

       _   _     .____    
      | |_| |    |  _ \  
      |  _  |    | (_))   
      | |-| |    | |      
      |_| |_|    |_|  ..  
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** LOADER **
 ** BOARD: DB-88F6281A-BP LE 

U-Boot 1.1.4 (Nov 27 2009 - 14:25:23) MIC version: 3.4.19-15

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CD4E0

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM CS[1] base 0x10000000   size 256MB 
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
[1024kB@f8000000] Flash:  1 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled 
Write allocate disabled


USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0 

Reset IDE: 
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: SM22 Firm: I052 Ser#: (03)5526888-20080228
            Type: Hard Disk
            Capacity: 463.6 MB = 0.4 GB (949536 x 512)


1888432 bytes read
Checking Button Status: off
Checking GotoWOL Status: on, setting to off
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
Entering WOL mode
--------------
Scaling down CPU freq
PEX is Powered Off - 2
USB is Powered Off - 3
SDIO is Powered Off (clock only) - 4
TSU is Powered Off (clock only) - 5
XOR0 is Powered Off (clock only) - 8
Audio is Powered Off (clock only) - 9
SATA0 is Powered Off - 14
SATA1 is Powered Off - 15
XOR1 is Powered Off (clock only) - 16
CESA is Powered Off (clock only) - 17
Giga1 is Powered Off (clock only) - 19
TDM is Powered Off (clock only) - 20
Setting PHY interrupt mode
Setting GPIOs as input
Setting GPIOs mask
Setting main high interrupt mask

Checking link...
No link, waiting for cable insertion.
And thats all i could find..

Q - can we mash netconsole onto this version of uboot? if we can mash the configs to it i can attempt a netconsole log.



Edited 1 time(s). Last edit at 01/30/2016 09:29AM by Gravelrash.
Re: HP T5325 Thin Client Debian
January 30, 2016 09:35AM
Gravelrash,

1. Perhaps you should try the 3 shirt-pins apprach (to push them in temporarily)?

2. Or try to make a clip on header with something like this:
http://www.ebay.com/itm/10pcs-4-Pin-2-54mm-Single-Row-Right-Angle-Female-Pin-Header-USA-Seller-Free-Ship-/222009548254?hash=item33b0ccddde:g:J3sAAOSwp5JWZZbH

I think you can find a narrower pitch header similar to this, and then use an aligator clip to clam it onto the unpopulated serial port?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 30, 2016 09:42AM
Gravelrash,

> ** BOARD: DB-88F6281A-BP LE
>
> U-Boot 1.1.4 (Nov 27 2009 - 14:25:23) MIC version:
> 3.4.19-15
>
> U-Boot code: 00600000 -> 0067FFF0 BSS: ->
> 006CD4E0
>
> Soc: 88F6281 A0 (DDR2)
> CPU running @ 1200Mhz L2 running @ 400Mhz
> SysClock = 400Mhz , TClock = 200Mhz

Good news. This looks just like any other stock Marvell u-boot. It means high probabilty to build new u-boot for it.

>
> Q - can we mash netconsole onto this version of
> uboot? if we can mash the configs to it i can
> attempt a netconsole log.

No, stock u-boot usually don't have netconsole (I never seen one that does).

UPDATE:

BTW, this stock u-boot is horrible, for rebooting. Looks like it keeps rewriting the envs to NAND at each boot.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 2 time(s). Last edit at 01/30/2016 09:49AM by bodhi.
Re: HP T5325 Thin Client Debian
January 30, 2016 10:11AM
Living dangerously:

1. Create the latest USB rootfs using Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2.

In step 4, use the sheevaplug
cat dts/kirkwood-sheevaplug.dtb  >> zImage.fdt

And remember to label the USB rootfs to rootfs.

2. Boot to stock OS and mount the USB rootfs.

3. Change u-boot envs (the dangerous part is in red):

fw_setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10'
fw_setenv load_usb 'usb start; ext2load usb 0:1 0x800000 /boot/uImage; ext2load usb 0:1 0x1100000 /boot/uInitrd'
fw_setenv bootcmd_usb 'setenv bootargs $(bootargs_usb); run load_usb; bootm 0x800000 0x1100000
fw_setenv bootcmd 'run bootcmd_usb; run thinpro'

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian
January 30, 2016 11:29AM
@bodhi....

here we go.... if it borks it borks.... no loss no foul :)

if it works it works - then YIPPEE count me in for a "uboot mashing" to a decent one.


Currently rebuilding a debian server, so may not feed back till late this evening or tomorrow.......




P.S. I cant wait!!!!!
Re: HP T5325 Thin Client Debian
January 30, 2016 06:20PM
Tried the other suggested options. to gain console access, gut feeling is that the "com port" is faulty

Trying the above and issuing the fw_printenv commands worked (after i added the missing ') the disk was inserted and boot attempted.

Im guessing it hung somewhere as after a few minutes there still wasn't anything showing on the network

GOOD NEWS IS that the system rebooted straight back into the HP OS, when the USB key was removed and a power cycle applied


Project on hold till i go shopping and get a 1.25mm pitch JST cable. 

PROJECT ON HOLD : 30 - 1 - 2016
Re: HP T5325 Thin Client Debian
January 30, 2016 06:37PM
Gravelrash,

> GOOD NEWS IS that the system rebooted
> straight back into the HP OS, when the USB key was
> removed and a power cycle applied

Cool! it means that the stock u-boot deal with the envs the way I expected.

It might be the case that it does not like ext2load. If that's indeed the problem then we'll have to use 2 partition disks.

/boot is in a FAT32 parition and / is in an Ext3 partition. And the FAT32 partition must be the 1st partition.

And these would be

fw_setenv bootargs_usb 'console=ttyS0,115200 root=LABEL=rootfs rootdelay=10'
fw_setenv load_usb 'usb start; fatload usb 0:1 0x800000 /boot/uImage; fatload usb 0:1  0x1100000 /boot/uInitrd'
fw_setenv bootcmd_usb 'setenv bootargs $(bootargs_usb); run load_usb; bootm 0x800000 0x1100000
fw_setenv bootcmd 'run bootcmd_usb; run thinpro'

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian : Project on Hold 30-01-2016
January 30, 2016 06:56PM
Interesting - the only other time I came across the need to do a split disk setup that was on the Cubieboard 2 and the Raspi

Would i need to make any mods to the following and if so what do you recommend

/etc/fstab

machid = i notice one isnt set anywhere, im guessing that the sheevaplug setup we are "borrowing" will need it?



Just ordered these
http://www.ebay.co.uk/sch/i.html?_from=R40&_trksid=p2050601.m570.l1313.TR0.TRC0.H0.XJST+1.25+4-Pin.TRS0&_nkw=JST+1.25+4-Pin&_sacat=0
Re: HP T5325 Thin Client Debian : Project on Hold 30-01-2016
January 30, 2016 07:05PM
I envisage something like this in the /etc/fstab

/dev/sda1  /boot   vfat    defaults                        0 0
/dev/sda2  /       ext3    defaults,noatime             0 0



Edited 1 time(s). Last edit at 01/30/2016 07:06PM by Gravelrash.
Re: HP T5325 Thin Client Debian : Project on Hold 30-01-2016
January 30, 2016 07:11PM
> Interesting - the only other time I came across
> the need to do a split disk setup that was on the
> Cubieboard 2 and the Raspi

Right now it is only a guess. Because the recovery script uses fatload, so my deduction that it might lack ext2load. But if HP actually did remove ext2load then I'd say that it is a bad decision to save some bytes. Hard to say though, because we are blind without serial console.

>
> Would i need to make any mods to the following and
> if so what do you recommend
>
> /etc/fstab
>
Should be the same because we are booting with the label rootfs.

> machid = i notice one isnt set anywhere, im
> guessing that the sheevaplug setup we are
> "borrowing" will need it?

It does not need arcNumber or machid because the DTB is embedded. If we are booting 3.16 then yes, we'll need both.

To confirm this, on a box with FDT rootfs running, and you have serial console. Reboot, interrupt serial console and remove both with setenv, then boot.

>
> Just ordered these
> http://www.ebay.co.uk/sch/i.html?_from=R40&_trksid
> =p2050601.m570.l1313.TR0.TRC0.H0.XJST+1.25+4-Pin.T
> RS0&_nkw=JST+1.25+4-Pin&_sacat=0

Wow, that's a really tiny JST header! So my clip-on header idea is more difficult to do. I wonder if there is a right angle 4-pin header (with female connector) that small?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian : Project on Hold 30-01-2016
January 30, 2016 07:13PM
Gravelrash Wrote:
-------------------------------------------------------
> I envisage something like this in the /etc/fstab
>
>
> /dev/sda1  /boot   vfat    defaults               
>         0 0
> /dev/sda2  /       ext3    defaults,noatime       
>      0 0
> 
>

Yes this would be fine. However, in recent kernels, the label rootfs takes precedent for mounting.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: HP T5325 Thin Client Debian : Project on Hold 30-01-2016
January 30, 2016 08:15PM
no joy - we are running blind so prob best to wait till the JST headers land.

WDYT ?
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: