Debian on Dell Wyse T10 / T50
Posted by Koen
|
Bob
Re: Dell Wyse T10 / T50 August 23, 2018 03:34PM |
Hi bodhi
I rolled one of the T50s back to the stock Ubuntu install and re-ran hwinfo. The output is identical.
Here's the full output from hwinfo on the stock Ubuntu:
https://pastebin.com/raw/Dbgragv6
I rolled one of the T50s back to the stock Ubuntu install and re-ran hwinfo. The output is identical.
Here's the full output from hwinfo on the stock Ubuntu:
https://pastebin.com/raw/Dbgragv6
|
Re: Dell Wyse T10 / T50 August 23, 2018 04:51PM |
Admin Registered: 13 years ago Posts: 18,548 |
Hi Bob,
Thanks! I double checked and saw some problem in my last DTS so will recompile and upload a new version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thanks! I double checked and saw some problem in my last DTS so will recompile and upload a new version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 23, 2018 09:45PM |
Admin Registered: 13 years ago Posts: 18,548 |
Hopefully Ethernet will be available with this new version. Please try!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 24, 2018 05:42AM |
Hi bodhi
Ethernet is working fine with this new dtb!
Here's the full dmesg output. There's an error unpacking the initramfs that I'll have to look into but otherwise it seems good.
Ethernet is working fine with this new dtb!
[ 15.910226] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
Here's the full dmesg output. There's an error unpacking the initramfs that I'll have to look into but otherwise it seems good.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.12.4-mvebu-tld-1 (root@tldDebianVM) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #1 SMP PREEMPT Sat Jul 29 21:56:37 PDT 2017
[ 0.000000] CPU: ARMv7 Processor [560f5815] revision 5 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] OF: fdt: Machine model: Dell Wyse T50
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] On node 0 totalpages: 262144
[ 0.000000] free_area_init_node: node 0, pgdat c0d9d700, node_mem_map ef7f8000
[ 0.000000] Normal zone: 1536 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 196608 pages, LIFO batch:31
[ 0.000000] HighMem zone: 65536 pages, LIFO batch:15
[ 0.000000] CPU: All CPU(s) started in SVC mode.
[ 0.000000] percpu: Embedded 17 pages/cpu @ef7d9000 s40460 r8192 d20980 u69632
[ 0.000000] pcpu-alloc: s40460 r8192 d20980 u69632 alloc=17*4096
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: rootdelay=5 root=/dev/sdb1 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
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 1022124K/1048576K available (8192K kernel code, 712K rwdata, 2080K rodata, 1024K init, 331K bss, 26452K reserved, 0K cma-reserved, 262144K highmem)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc0900000 (9184 kB)
.init : 0xc0c00000 - 0xc0d00000 (1024 kB)
.data : 0xc0d00000 - 0xc0db2308 ( 713 kB)
.bss : 0xc0db9a84 - 0xc0e0ca58 ( 332 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[ 0.000007] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[ 0.000040] Switching to timer-based delay loop, resolution 6ns
[ 0.000580] Console: colour dummy device 80x30
[ 0.001301] console [tty0] enabled
[ 0.001344] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.001408] pid_max: default: 32768 minimum: 301
[ 0.001598] Security Framework initialized
[ 0.001713] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001758] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.002555] CPU: Testing write buffer coherency: ok
[ 0.002912] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.040179] Setting up static identity map for 0x100000 - 0x100060
[ 0.120087] smp: Bringing up secondary CPUs ...
[ 0.120140] smp: Brought up 1 node, 1 CPU
[ 0.120177] SMP: Total of 1 processors activated (333.33 BogoMIPS).
[ 0.120211] CPU: All CPU(s) started in SVC mode.
[ 0.121064] devtmpfs: initialized
[ 0.130425] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 5
[ 0.130992] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.131072] futex hash table entries: 256 (order: 2, 16384 bytes)
[ 0.131360] prandom: seed boundary self test passed
[ 0.134422] prandom: 100 self tests passed
[ 0.134454] pinctrl core: initialized pinctrl subsystem
[ 0.135549] NET: Registered protocol family 16
[ 0.136429] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.141188] cpuidle: using governor ladder
[ 0.141286] cpuidle: using governor menu
[ 0.141632] Dove 88AP510 SoC
[ 0.141678] Tauros2: Disabling L2 prefetch.
[ 0.141709] Tauros2: Disabling burst8 line fill.
[ 0.141738] Tauros2: Enabling L2 cache.
[ 0.141767] Tauros2: L2 cache support initialised in ARMv7 mode.
[ 0.142157] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.240626] vgaarb: loaded
[ 0.240963] SCSI subsystem initialized
[ 0.250155] libata version 3.00 loaded.
[ 0.250401] usbcore: registered new interface driver usbfs
[ 0.250495] usbcore: registered new interface driver hub
[ 0.250590] usbcore: registered new device driver usb
[ 0.250830] media: Linux media interface: v0.10
[ 0.250902] Linux video capture interface: v2.00
[ 0.260576] clocksource: Switched to clocksource orion_clocksource
[ 0.335191] VFS: Disk quotas dquot_6.6.0
[ 0.335312] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.353873] NET: Registered protocol family 2
[ 0.354963] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.355062] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.355173] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.355292] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.355348] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.355534] NET: Registered protocol family 1
[ 0.376175] RPC: Registered named UNIX socket transport module.
[ 0.376219] RPC: Registered udp transport module.
[ 0.376249] RPC: Registered tcp transport module.
[ 0.376278] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.376316] PCI: CLS 0 bytes, default 64
[ 0.376502] Unpacking initramfs...
[ 0.376537] Initramfs unpacking failed: junk in compressed archive
[ 0.382093] Freeing initrd memory: 3928K
[ 0.382438] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.384163] audit: initializing netlink subsys (disabled)
[ 0.385172] Initialise system trusted keyrings
[ 0.385249] Key type blacklist registered
[ 0.385412] audit: type=2000 audit(0.384:1): state=initialized audit_enabled=0 res=1
[ 0.385682] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[ 0.385812] zbud: loaded
[ 0.406963] NFS: Registering the id_resolver key type
[ 0.407019] Key type id_resolver registered
[ 0.407049] Key type id_legacy registered
[ 0.407086] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.407121] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.407350] jffs2: version 2.2. (NAND) (SUMMARY) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
[ 0.407872] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 0.408115] orangefs_init: module version upstream loaded
[ 0.413489] Key type asymmetric registered
[ 0.413530] Asymmetric key parser 'x509' registered
[ 0.413616] bounce: pool size: 64 pages
[ 0.413689] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[ 0.413740] io scheduler noop registered
[ 0.413769] io scheduler deadline registered
[ 0.413844] io scheduler cfq registered (default)
[ 0.414602] dove-pinctrl f10d0200.pin-ctrl: falling back to hardcoded PMU resource
[ 0.414774] dove-pinctrl f10d0200.pin-ctrl: [Firmware Bug]: Missing pinctrl regs in DTB. Please update your firmware.
[ 0.415501] dove-pinctrl f10d0200.pin-ctrl: registered pinctrl driver
[ 0.419134] mvebu-pcie mbus:pcie: PCI host bridge to bus 0000:00
[ 0.419188] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.419225] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.419264] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.419300] pci_bus 0000:00: scanning bus
[ 0.419331] pci 0000:00:01.0: [11ab:0510] type 01 class 0x060400
[ 0.419375] pci 0000:00:01.0: calling pci_fixup_ide_bases+0x0/0x3c
[ 0.421181] pci 0000:00:02.0: [11ab:0510] type 01 class 0x060400
[ 0.421219] pci 0000:00:02.0: calling pci_fixup_ide_bases+0x0/0x3c
[ 0.421537] pci_bus 0000:00: fixups for bus
[ 0.421553] PCI: bus0: Fast back to back transfers disabled
[ 0.421601] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[ 0.421610] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.421669] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[ 0.421677] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.421734] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[ 0.421945] pci_bus 0000:01: scanning bus
[ 0.421955] pci_bus 0000:01: fixups for bus
[ 0.421961] PCI: bus1: Fast back to back transfers enabled
[ 0.421998] pci_bus 0000:01: bus scan returning with max=01
[ 0.422009] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 0.422022] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[ 0.422207] pci_bus 0000:02: scanning bus
[ 0.422217] pci_bus 0000:02: fixups for bus
[ 0.422223] PCI: bus2: Fast back to back transfers enabled
[ 0.422260] pci_bus 0000:02: bus scan returning with max=02
[ 0.422270] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 0.422281] pci_bus 0000:00: bus scan returning with max=02
[ 0.422293] pci 0000:00:01.0: fixup irq: got 0
[ 0.422300] pci 0000:00:01.0: assigning IRQ 00
[ 0.422310] pci 0000:00:02.0: fixup irq: got 0
[ 0.422317] pci 0000:00:02.0: assigning IRQ 00
[ 0.422342] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.422384] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 0.422501] pcieport 0000:00:01.0: enabling bus mastering
[ 0.422574] pcieport 0000:00:02.0: enabling bus mastering
[ 0.423329] mv_xor f1060800.dma-engine: Marvell shared XOR driver
[ 0.481517] mv_xor f1060800.dma-engine: Marvell XOR (Registers Mode): ( xor cpy sg intr )
[ 0.481901] mv_xor f1060900.dma-engine: Marvell shared XOR driver
[ 0.541483] mv_xor f1060900.dma-engine: Marvell XOR (Registers Mode): ( xor cpy sg intr )
[ 0.661780] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.665189] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 21, base_baud = 10416666) is a 16550A
[ 0.666266] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 22, base_baud = 10416666) is a 16550A
[ 0.668427] sata_mv f10a0000.sata-host: version 1.28
[ 0.668581] sata_mv f10a0000.sata-host: slots 32 ports 1
[ 0.680891] scsi host0: sata_mv
[ 0.681304] ata1: SATA max UDMA/133 irq 33
[ 0.683083] m25p80 spi0.0: found mx25l3205d, expected s25fl064k
[ 0.683134] m25p80 spi0.0: mx25l3205d (4096 Kbytes)
[ 0.685738] libphy: Fixed MDIO Bus: probed
[ 0.686586] libphy: orion_mdio_bus: probed
[ 0.686638] [Firmware Warn]: /mbus/internal-regs/mdio-bus@72004/ethernet-phy: Whitelisted compatible string. Please remove
[ 0.696975] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 0.791860] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address xx:xx:xx:xx:xx:xx
[ 0.792684] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.792743] ehci-pci: EHCI PCI platform driver
[ 0.792891] ehci-orion: EHCI orion driver
[ 0.793091] orion-ehci f1050000.usb-host: EHCI Host Controller
[ 0.793152] orion-ehci f1050000.usb-host: new USB bus registered, assigned bus number 1
[ 0.793332] orion-ehci f1050000.usb-host: irq 26, io mem 0xf1050000
[ 0.820622] orion-ehci f1050000.usb-host: USB 2.0 started, EHCI 1.00
[ 0.820901] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.820942] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.820992] usb usb1: Product: EHCI Host Controller
[ 0.821025] usb usb1: Manufacturer: Linux 4.12.4-mvebu-tld-1 ehci_hcd
[ 0.821061] usb usb1: SerialNumber: f1050000.usb-host
[ 0.821881] hub 1-0:1.0: USB hub found
[ 0.821948] hub 1-0:1.0: 1 port detected
[ 0.822473] orion-ehci f1051000.usb-host: EHCI Host Controller
[ 0.822533] orion-ehci f1051000.usb-host: new USB bus registered, assigned bus number 2
[ 0.822704] orion-ehci f1051000.usb-host: irq 27, io mem 0xf1051000
[ 0.850576] orion-ehci f1051000.usb-host: USB 2.0 started, EHCI 1.00
[ 0.850826] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.850868] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.850918] usb usb2: Product: EHCI Host Controller
[ 0.850951] usb usb2: Manufacturer: Linux 4.12.4-mvebu-tld-1 ehci_hcd
[ 0.850986] usb usb2: SerialNumber: f1051000.usb-host
[ 0.851758] hub 2-0:1.0: USB hub found
[ 0.851822] hub 2-0:1.0: 1 port detected
[ 0.852894] usbcore: registered new interface driver usblp
[ 0.853094] usbcore: registered new interface driver usb-storage
[ 0.853517] mousedev: PS/2 mouse device common for all mice
[ 0.854570] rtc-mv f10d8500.real-time-clock: rtc core: registered f10d8500.real-time- as rtc0
[ 0.854920] i2c /dev entries driver
[ 0.858638] orion_wdt: Initial timeout 25 sec
[ 0.861414] marvell-cesa f1030000.crypto-engine: CESA device successfully registered
[ 0.861719] hidraw: raw HID events driver (C) Jiri Kosina
[ 0.862207] usbcore: registered new interface driver usbhid
[ 0.862244] usbhid: USB HID core driver
[ 0.862486] drop_monitor: Initializing network drop monitor service
[ 0.862598] Netfilter messages via NETLINK v0.30.
[ 0.862645] ip_set: protocol 6
[ 0.862974] NET: Registered protocol family 10
[ 0.874197] Segment Routing with IPv6
[ 0.874293] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 0.876076] NET: Registered protocol family 17
[ 0.876164] 8021q: 802.1Q VLAN Support v1.8
[ 0.876236] Key type dns_resolver registered
[ 0.876584] ThumbEE CPU extension supported.
[ 0.876621] Registering SWP/SWPB emulation handler
[ 0.876653] PJ4 iWMMXt v2 coprocessor enabled.
[ 0.877526] registered taskstats version 1
[ 0.877562] Loading compiled-in X.509 certificates
[ 0.877641] zswap: loaded using pool lzo/zbud
[ 0.952219] Key type big_key registered
[ 0.952775] Key type encrypted registered
[ 0.954885] rtc-mv f10d8500.real-time-clock: setting system clock to 2018-08-24 10:30:38 UTC (1535106638)
[ 0.955078] PM: Hibernation image not present or could not be loaded.
[ 0.955211] Waiting 5 sec before mounting root device...
[ 1.200544] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 1.230551] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[ 1.260743] ata1.00: CFA: 1GB ATA Flash Disk, AD B612J, max UDMA/66
[ 1.260782] ata1.00: 2001888 sectors, multi 0: LBA
[ 1.290736] ata1.00: configured for UDMA/66
[ 1.301371] scsi 0:0:0:0: Direct-Access ATA 1GB ATA Flash Di 612J PQ: 0 ANSI: 5
[ 1.302862] sd 0:0:0:0: [sda] 2001888 512-byte logical blocks: (1.02 GB/977 MiB)
[ 1.302979] sd 0:0:0:0: [sda] Write Protect is off
[ 1.303016] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.303123] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.305317] sda: sda1 sda2 sda3
[ 1.307200] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.392208] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 1.392254] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.392291] usb 1-1: Product: USB2.0 Hub
[ 1.393157] hub 1-1:1.0: USB hub found
[ 1.393580] hub 1-1:1.0: 4 ports detected
[ 1.710537] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[ 1.810713] random: fast init done
[ 1.866079] usb 1-1.2: New USB device found, idVendor=13fe, idProduct=36ff
[ 1.866121] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.866171] usb 1-1.2: Product: USB DISK
[ 1.866202] usb 1-1.2: SerialNumber: 7FB80C00FFAF28B4
[ 1.867023] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 1.877488] scsi host1: usb-storage 1-1.2:1.0
[ 1.970539] usb 1-1.3: new low-speed USB device number 4 using orion-ehci
[ 2.070537] usb 1-1.3: device descriptor read/64, error -32
[ 2.290536] usb 1-1.3: device descriptor read/64, error -32
[ 2.510535] usb 1-1.3: new low-speed USB device number 5 using orion-ehci
[ 2.610535] usb 1-1.3: device descriptor read/64, error -32
[ 2.830533] usb 1-1.3: device descriptor read/64, error -32
[ 2.892403] scsi 1:0:0:0: Direct-Access USB DISK DL11 PQ: 0 ANSI: 0 CCS
[ 2.904995] sd 1:0:0:0: [sdb] 3842048 512-byte logical blocks: (1.97 GB/1.83 GiB)
[ 2.905478] sd 1:0:0:0: [sdb] Write Protect is off
[ 2.905516] sd 1:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 2.905978] sd 1:0:0:0: [sdb] No Caching mode page found
[ 2.906016] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[ 2.911212] sdb: sdb1
[ 2.914356] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 3.050536] usb 1-1.3: new low-speed USB device number 6 using orion-ehci
[ 3.490536] usb 1-1.3: device not accepting address 6, error -32
[ 3.590536] usb 1-1.3: new low-speed USB device number 7 using orion-ehci
[ 4.030535] usb 1-1.3: device not accepting address 7, error -32
[ 4.030959] usb 1-1-port3: unable to enumerate USB device
[ 6.002834] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 6.028277] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 6.028366] VFS: Mounted root (ext3 filesystem) readonly on device 8:17.
[ 6.031916] devtmpfs: mounted
[ 6.033747] Freeing unused kernel memory: 1024K
[ 7.881813] i2c i2c-0: Added multiplexed i2c bus 1
[ 7.886797] i2c i2c-0: Added multiplexed i2c bus 2
[ 7.887234] i2c i2c-0: Added multiplexed i2c bus 3
[ 8.209053] sdhci: Secure Digital Host Controller Interface driver
[ 8.209118] sdhci: Copyright(c) Pierre Ossman
[ 8.215920] sdhci-pltfm: SDHCI platform and OF driver helper
[ 8.240880] usbcore: registered new interface driver uas
[ 8.242413] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 8.242890] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 8.281671] mmc0: SDHCI controller on f1090000.sdio-host [f1090000.sdio-host] using DMA
[ 8.341740] mmc1: SDHCI controller on f1092000.sdio-host [f1092000.sdio-host] using DMA
[ 10.627779] EXT4-fs (sdb1): re-mounted. Opts: (null)
[ 10.846055] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro
[ 13.274602] random: crng init done
[ 13.433256] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 15.910226] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 15.910343] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
|
Re: Dell Wyse T10 / T50 August 24, 2018 05:54AM |
Admin Registered: 13 years ago Posts: 18,548 |
> Ethernet is working fine with this new dtb!
Cool :) We are getting closer.
Thanks Bob!
This problem is due to the load address of the uInitrd. Did you use the same location in u-boot env as Koen's?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Cool :) We are getting closer.
Thanks Bob!
[ 0.376537] Initramfs unpacking failed: junk in compressed archive
This problem is due to the load address of the uInitrd. Did you use the same location in u-boot env as Koen's?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 24, 2018 07:16AM |
Hi bodhi
The problem was at my end. In my hurry to get the kernel going I think I was reusing the old one that came with the rootfs. Plus, I was also working with the old kernel.
So I built a fresh uImage and uInitrd with the 4.16.7 package and it's all good.
I then went a step further and replaced the stock kernel and filesystem so it now boots into Debian without using the recovery partition or usb stick. In this case the initrd isn't used (as with the stock install, the kernel partition only has uImage). It works but space is very tight so I think I'll try and remove the recovery partition next.
The problem was at my end. In my hurry to get the kernel going I think I was reusing the old one that came with the rootfs. Plus, I was also working with the old kernel.
So I built a fresh uImage and uInitrd with the 4.16.7 package and it's all good.
I then went a step further and replaced the stock kernel and filesystem so it now boots into Debian without using the recovery partition or usb stick. In this case the initrd isn't used (as with the stock install, the kernel partition only has uImage). It works but space is very tight so I think I'll try and remove the recovery partition next.
|
Re: Dell Wyse T10 / T50 August 24, 2018 11:26AM |
Admin Registered: 13 years ago Posts: 18,548 |
Hi Bob,
That's strange, the old kernel in the rootfs should work fine with the new DTB. But I'm glad you've solved the problem using the new kernel!
The new kernel should boot fine with uImage only. However, you will miss a whole bunch of modules that were configured in the initramfs. So it is best to boot with uInitrd. If you have problem loading it using whatever address in stock envs , try adding this env before the bootcmd executed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
That's strange, the old kernel in the rootfs should work fine with the new DTB. But I'm glad you've solved the problem using the new kernel!
The new kernel should boot fine with uImage only. However, you will miss a whole bunch of modules that were configured in the initramfs. So it is best to boot with uInitrd. If you have problem loading it using whatever address in stock envs , try adding this env before the bootcmd executed.
setenv initrd_high 0xffffffff
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 24, 2018 11:50AM |
Hi bodhi
Yeah I was thinking it might be a good idea to use the initrd. I just put it into the kernel partition alongside the uImage and it loads fine.
Right now I'm doing some experimenting with removing the recovery partition and getting the USB tool to pull and push an image successfully. It takes quite a while to pull an image as it compresses it first.
One issue I'm finding with the new kernel is that I can't shutdown the unit over ssh. It seems to hang somewhere so I have to hold in the power button to get it to power off.
Yeah I was thinking it might be a good idea to use the initrd. I just put it into the kernel partition alongside the uImage and it loads fine.
Right now I'm doing some experimenting with removing the recovery partition and getting the USB tool to pull and push an image successfully. It takes quite a while to pull an image as it compresses it first.
One issue I'm finding with the new kernel is that I can't shutdown the unit over ssh. It seems to hang somewhere so I have to hold in the power button to get it to power off.
|
Re: Dell Wyse T10 / T50 August 24, 2018 01:53PM |
Admin Registered: 13 years ago Posts: 18,548 |
Bob,
> One issue I'm finding with the new kernel is that
> I can't shutdown the unit over ssh. It seems to
> hang somewhere so I have to hold in the power
> button to get it to power off.
This is where a serial console will help seeing the exact behavior. I'll take a look at the DTS to see if I can find some hint.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> One issue I'm finding with the new kernel is that
> I can't shutdown the unit over ssh. It seems to
> hang somewhere so I have to hold in the power
> button to get it to power off.
This is where a serial console will help seeing the exact behavior. I'll take a look at the DTS to see if I can find some hint.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 24, 2018 02:28PM |
Admin Registered: 13 years ago Posts: 18,548 |
All,
Perhaps the Wyse T50/T10 patches can be found in the hedley repo as Koen reported:
https://forum.doozan.com/read.php?2,63499,65094#msg-65094
What Bob saw was probably the lack of T50/T10 poweroff (GPIO or what not) driver hook in new kernel. This can be found in GPL.
@Koen, what do you see when power off in Debian?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Perhaps the Wyse T50/T10 patches can be found in the hedley repo as Koen reported:
https://forum.doozan.com/read.php?2,63499,65094#msg-65094
What Bob saw was probably the lack of T50/T10 poweroff (GPIO or what not) driver hook in new kernel. This can be found in GPL.
@Koen, what do you see when power off in Debian?
shutdown -h now
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 24, 2018 03:30PM |
Admin Registered: 13 years ago Posts: 18,548 |
Quote
bodhi
All,
Perhaps the Wyse T50/T10 patches can be found in the hedley repo as Koen reported:
https://forum.doozan.com/read.php?2,63499,65094#msg-65094
Yes it is. The kernel patches is in
http://oem.archive.canonical.com/updates/pool/public/l/linux-mvl-dove/linux-mvl-dove_2.6.32-212.28hedley14.tar.gz
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 24, 2018 03:53PM |
Admin Registered: 13 years ago Posts: 18,548 |
Quote
bodhi
What Bob saw was probably the lack of T50/T10 poweroff (GPIO or what not) driver hook in new kernel. This can be found in GPL.
Yes. There is a GPIO power off in there.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 25, 2018 09:20AM |
Hi bodhi
Serial would be helpful alright. What I can say is it goes far enough that USB powers down. Perhaps it's just failing at the final stage.
Would this output from my earlier dmesg be related?
Serial would be helpful alright. What I can say is it goes far enough that USB powers down. Perhaps it's just failing at the final stage.
Would this output from my earlier dmesg be related?
[ 0.414602] dove-pinctrl f10d0200.pin-ctrl: falling back to hardcoded PMU resource [ 0.414774] dove-pinctrl f10d0200.pin-ctrl: [Firmware Bug]: Missing pinctrl regs in DTB. Please update your firmware. [ 0.415501] dove-pinctrl f10d0200.pin-ctrl: registered pinctrl driver
|
Re: Dell Wyse T10 / T50 August 25, 2018 10:17AM |
Registered: 5 years ago Posts: 180 |
|
Re: Dell Wyse T10 / T50 August 25, 2018 02:35PM |
Admin Registered: 13 years ago Posts: 18,548 |
@Koen,
> I did have the same issue
> with shutdown not working properly and ended up
> just pulling the power cable.
Thanks! good to hear that confirmation.
@Bob,
It's unrelated to poweroff, but it's a good hint that the PMU needs to be activated.
@all,
I've looked at the Dell (Machine: WYSE Mimas Board) patches. Indeed, this box uses GPIO for power off. Also, other hardware aspects are in there (in the old style kernel board-specific code), that can be used to make new DTS nodes.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I did have the same issue
> with shutdown not working properly and ended up
> just pulling the power cable.
Thanks! good to hear that confirmation.
@Bob,
[ 0.414602] dove-pinctrl f10d0200.pin-ctrl: falling back to hardcoded PMU resource [ 0.414774] dove-pinctrl f10d0200.pin-ctrl: [Firmware Bug]: Missing pinctrl regs in DTB. Please update your firmware. [ 0.415501] dove-pinctrl f10d0200.pin-ctrl: registered pinctrl driver
It's unrelated to poweroff, but it's a good hint that the PMU needs to be activated.
@all,
I've looked at the Dell (Machine: WYSE Mimas Board) patches. Indeed, this box uses GPIO for power off. Also, other hardware aspects are in there (in the old style kernel board-specific code), that can be used to make new DTS nodes.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 25, 2018 02:48PM |
Admin Registered: 13 years ago Posts: 18,548 |
Here is another DTB version. This one has GPIO power-off node to shutdown the box properly.
Warning: there is a small risk in testing GPIO, I would caution that you back up your stock rootfs and envs, just in case. Usually I do these tests myself before publishing it, but I have not received my eBay box yet, so I can't test the HW to be sure, that I will brick my box first if I made a mistake :-).
Update:
This DTB version did not work :) back to previous one.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/25/2018 05:31PM by bodhi.
Warning: there is a small risk in testing GPIO, I would caution that you back up your stock rootfs and envs, just in case. Usually I do these tests myself before publishing it, but I have not received my eBay box yet, so I can't test the HW to be sure, that I will brick my box first if I made a mistake :-).
Update:
This DTB version did not work :) back to previous one.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/25/2018 05:31PM by bodhi.
|
Bob
Re: Dell Wyse T10 / T50 August 25, 2018 04:43PM |
|
Re: Dell Wyse T10 / T50 August 25, 2018 05:34PM |
Admin Registered: 13 years ago Posts: 18,548 |
Bob Wrote:
-------------------------------------------------------
> Hi bodhi
>
> I tried this new dtb but the system shuts down
> around where it would start booting the rootfs.
Thanks Bob!
So either GPIO 8 is not the right one or it is the Active High/Low problem!
Please post your stock dmesg log. I'd like to check if it is the same as Koen's.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Hi bodhi
>
> I tried this new dtb but the system shuts down
> around where it would start booting the rootfs.
Thanks Bob!
So either GPIO 8 is not the right one or it is the Active High/Low problem!
Please post your stock dmesg log. I'd like to check if it is the same as Koen's.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 25, 2018 05:44PM |
Admin Registered: 13 years ago Posts: 18,548 |
I think I need to see serial console output during shut down (with Aug 23 DTB).
The Mimas kernel patch looks to be a correct one for Koen's dmesg.
Update:
Ah. Seems to be Active Low/High problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/25/2018 06:03PM by bodhi.
The Mimas kernel patch looks to be a correct one for Koen's dmesg.
Update:
Ah. Seems to be Active Low/High problem.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/25/2018 06:03PM by bodhi.
|
Bob
Re: Dell Wyse T10 / T50 August 25, 2018 06:11PM |
Hi bodhi. Here's the dmesg output from stock Ubuntu:
Linux version 2.6.32-217-hedley (buildd@shedir) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #34hedley46-Ubuntu Wed Dec 14 07:47:31 UTC 2011 (Ubuntu 2.6.32-217.34hedley46-hedley 2.6.32.41+drm33.18) CPU: Marvell PJ4 v7 Processor-wmmx [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 On node 0 totalpages: 204800 free_area_init_node: node 0, pgdat c0728790, node_mem_map c07ad000 Normal zone: 1200 pages used for memmap Normal zone: 0 pages reserved Normal zone: 152400 pages, LIFO batch:31 wait table c0fad020 HighMem zone: 400 pages used for memmap HighMem zone: 50800 pages, LIFO batch:15 wait table c0faf040 Built 1 zonelists in Zone order, mobility grouping off. Total pages: 203200 Kernel command line: root=/dev/sda3 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 quiet 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: 801856KB available (6684K code, 758K data, 180K 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=7) SoC, TCLK = 167MHz DOVE_MC @ 0x280 is 010E0202 PLiao: DOVE_MC @ 0x510 is 01010101 Tauros2: Disabling L2 prefetch. Tauros2: Enabling L2 cache. Tauros2: L2 cache support initialised in ARMv7 mode. Setting gpu clock to 500000000 (divider: 4) Setting axi clock to 333000000 (divider: 5) Mimas DVT board detected Initializing USB0 Host Initializing USB1 Host LCD0 doesn't use PLL. LCD1 uses PLL. Turn on PLL accurate mode. Dove PCIe port 0: link down, ignoring Dove PCIe port 1: link down, ignoring bio: create slab <bio-0> at 0 SCSI subsystem initialized libata version 3.00 loaded. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Bluetooth: Core ver 2.15 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized cfg80211: Calling CRDA to update world regulatory domain 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 1000Mhz, AXI 250Mhz, L2 500Mhz, DDR 500Mhz Dove hwmon thermal sensor initialized. [galcore] registerBase =0xf1840000, registerMemSize = 0x0003ffff, contiguousBase= 0x32000000, contiguousSize = 0x07ffffff [galcore] real contiguouSize = 0x07ffffff [galcore] chipModel=0x600,chipRevision=0x19,chipFeatures=0x87ecd,chipMinorFeatures=0x7 cesadev_modinit cesadev_probe cesadev_init(c006f66c) mvCesaInit: sessions=640, queue=64, pSram=fdb00000 audit: initializing netlink socket (disabled) type=2000 audit(0.240:1): initialized 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 1167 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) Initializing ths8200_init 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 serial8250.1: ttyS1 at MMIO 0xf1012100 (irq = 8) is a 16550A brd: module loaded loop: module loaded BMM Module Vmeta memroy start: 0x3a000000, size: 100663296 BMM init with size=96MB 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 scsi0 : sata_mv ata1: SATA max UDMA/133 irq 62 MV-643xx 10/100/1000 ethernet driver version 1.4 mv643xx_eth smi: probed net eth0: port 0 with MAC address xx:xx:xx:xx:xx:xx PPP generic driver version 2.4.2 tun: Universal TUN/TAP device driver, 1.6 tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> 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 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 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 Bluetooth: Generic Bluetooth USB driver ver 0.6 usbcore: registered new interface driver btusb 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=36, host->irqn Registered led device: mmc0:: mmc0: 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 input: AT Translated Set 2 keyboard as /devices/platform/mv64xxx_i2c_exp.1/i2c-1/1-0058/serio0/input/input0 mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300) mv_xor mv_xor.2: Marvell XOR: ( xor cpy ) ata1.00: CFA: 1GB ATA Flash Disk, AD B612J, max UDMA/66 ata1.00: 2001888 sectors, multi 0: LBA ata1.00: configured for UDMA/66 scsi 0:0:0:0: Direct-Access ATA 1GB ATA Flash Di AD B PQ: 0 ANSI: 5 sd 0:0:0:0: [sda] 2001888 512-byte logical blocks: (1.02 GB/977 MiB) sd 0:0:0:0: [sda] Write Protect is off sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sda: sda1 sda2 sda3 sd 0:0:0:0: [sda] Attached SCSI disk 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. usbcore: registered new interface driver snd-usb-audio asoc: RT5630 HiFi <-> mv88fx-i2s1 mapping ok ALSA device list: #0: Dove-I2S-RT5630 (RT5630) aufs 2-standalone.tree-20091207 marvell_mrvl_pj4_detect_pmu: detected arm/mrvl_pj4 PMU oprofile: using arm/mrvl_pj4 Netfilter messages via NETLINK v0.30. TCP cubic registered NET: Registered protocol family 10 IPv6 over IPv4 tunneling driver NET: Registered protocol family 17 Bluetooth: L2CAP ver 2.14 Bluetooth: L2CAP socket layer initialized Bluetooth: SCO (Voice Link) ver 0.6 Bluetooth: SCO socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM ver 1.11 Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Bluetooth: BNEP filters: protocol multicast Bluetooth: HIDP (Human Interface Emulation) ver 1.2 lib80211: common routines for IEEE802.11 drivers lib80211_crypt: registered algorithm 'NULL' 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 dovefb dovefb.0: use ref clock IDT_CLK1 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 set clk 1 to 64998375 dividers found (in lookup table) for Fout = 64998375. n=234 d=5 odiv 18 YC pitch is 0.User program needs refine set clk 1 to 64998375 dividers found (in lookup table) for Fout = 64998375. n=234 d=5 odiv 18 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 dovefb dovefb.1: use ref clock accurate_LCDCLK 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 set internal refclk divider to 31.0.(accurate mode) YC pitch is 0.User program needs refine o dovefb: frame buffer device was successfully loaded. rtc-mv rtc-mv: setting system clock to 2018-08-25 22:56:12 UTC (1535237772) kjournald starting. Commit interval 5 seconds EXT3-fs warning: checktime reached, running e2fsck is recommended EXT3 FS on sda3, internal journal EXT3-fs: mounted filesystem with writeback data mode. VFS: Mounted root (ext3 filesystem) on device 8:3. devtmpfs: mounted Freeing init memory: 180K usb 1-1: new high speed USB device using orion-ehci and address 2 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 usb 1-1.1: new low speed USB device using orion-ehci and address 3 usb 1-1.1: configuration #1 chosen from 1 choice input: Cherry GmbH Cherry TouchBoard as /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input1 generic-usb 0003:046A:002F.0001: input,hidraw0: USB HID v1.11 Keyboard [Cherry GmbH Cherry TouchBoard] on usb-orion-ehci.0-1.1/input0 input: Cherry GmbH Cherry TouchBoard as /devices/platform/orion-ehci.0/usb1/1-1/1-1.1/1-1.1:1.1/input/input2 generic-usb 0003:046A:002F.0002: input,hidraw1: USB HID v1.11 Mouse [Cherry GmbH Cherry TouchBoard] on usb-orion-ehci.0-1.1/input1 usb 1-1.2: new high speed USB device using orion-ehci and address 4 usb 1-1.2: configuration #1 chosen from 1 choice scsi1 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning wco.c:v0.01 10/02/2012 WriteCO Control Driver udev: starting version 151 scsi 1:0:0:0: Direct-Access wyse.rmd Virtual HDD 1.00 PQ: 0 ANSI: 0 CCS usb-storage: device scan complete sd 1:0:0:0: [sdb] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB) sd 1:0:0:0: [sdb] Write Protect is off sd 1:0:0:0: [sdb] Mode Sense: 10 00 00 00 sd 1:0:0:0: [sdb] Assuming drive cache: write through sd 1:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 1:0:0:0: [sdb] Assuming drive cache: write through sd 1:0:0:0: [sdb] Attached SCSI removable disk ADDRCONF(NETDEV_UP): eth0: link is not ready set clk 1 to 64998375 dividers found (in lookup table) for Fout = 64998375. n=234 d=5 odiv 18 set internal refclk divider to 31.0.(accurate mode) set clk 1 to 108003024 dividers found (in lookup table) for Fout = 108003024. n=216 d=5 odiv 10 DCON fb callback: blank... YC pitch is 0.User program needs refine YC pitch is 0.User program needs refine set internal refclk divider to 18.5.(accurate mode) DCON fb callback: unblanking... eth0: link up, 1000 Mb/s, full duplex, flow control disabled ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready eth0: link down eth0: link up, 1000 Mb/s, full duplex, flow control disabled eth0: link down eth0: link up, 1000 Mb/s, full duplex, flow control disabled Setting vmeta clock to 500000000 (divider: 4) DCON fb callback: unblanking...
|
Re: Dell Wyse T10 / T50 August 25, 2018 07:53PM |
Admin Registered: 13 years ago Posts: 18,548 |
Here is another version. Please try the shutdown.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 25, 2018 08:13PM |
|
Re: Dell Wyse T10 / T50 August 25, 2018 08:39PM |
Admin Registered: 13 years ago Posts: 18,548 |
Bob Wrote:
-------------------------------------------------------
> Hi bodhi
>
> That one seems to works here. Booted into the
> system fine and it shutdown fully when I sent a
> poweroff command.
Cool! I got it in reverse bfore (the Active Low state of this GPIO , meaning it should be high when the kernel started and we want to trigger it to be low when shutting down). So that code is the right patch.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Hi bodhi
>
> That one seems to works here. Booted into the
> system fine and it shutdown fully when I sent a
> poweroff command.
Cool! I got it in reverse bfore (the Active Low state of this GPIO , meaning it should be high when the kernel started and we want to trigger it to be low when shutting down). So that code is the right patch.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 26, 2018 07:43AM |
Hi bodhi
Is it safe to use this dtb now? I'm just thinking about your warning earlier about possible corruption if the GPIO is not correct.
I tested it on my spare T50 but if it's safe I could put it onto my main T50 which is now happily running Debian 9 thanks to your work.
P.S. it seems both of mine have a different spi chip than Koens:
Is it safe to use this dtb now? I'm just thinking about your warning earlier about possible corruption if the GPIO is not correct.
I tested it on my spare T50 but if it's safe I could put it onto my main T50 which is now happily running Debian 9 thanks to your work.
P.S. it seems both of mine have a different spi chip than Koens:
[ 0.683083] m25p80 spi0.0: found mx25l3205d, expected s25fl064k [ 0.683134] m25p80 spi0.0: mx25l3205d (4096 Kbytes)
|
Re: Dell Wyse T10 / T50 August 26, 2018 11:19AM |
Admin Registered: 13 years ago Posts: 18,548 |
Hi Bob,
> Is it safe to use this dtb now? I'm just thinking
> about your warning earlier about possible
> corruption if the GPIO is not correct.
Yes. It is safe to use. The behavior is exactly what I expected from reading the Dell patch.
> P.S. it seems both of mine have a different spi
> chip than Koens:
>
>
It is indeed different. But as long as it was detected correctly by the driver, it's OK. If you can list the envs like Koen did using fw_printenv and the modified /etc/fw_env.config file then it is working. We cannot change envs yet (a little bit risky to do in Debian as we still don't know much about this u-boot yet).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/26/2018 12:13PM by bodhi.
> Is it safe to use this dtb now? I'm just thinking
> about your warning earlier about possible
> corruption if the GPIO is not correct.
Yes. It is safe to use. The behavior is exactly what I expected from reading the Dell patch.
> P.S. it seems both of mine have a different spi
> chip than Koens:
>
>
> [ 0.683083] m25p80 spi0.0: found mx25l3205d, > expected s25fl064k > [ 0.683134] m25p80 spi0.0: mx25l3205d (4096 > Kbytes) >
It is indeed different. But as long as it was detected correctly by the driver, it's OK. If you can list the envs like Koen did using fw_printenv and the modified /etc/fw_env.config file then it is working. We cannot change envs yet (a little bit risky to do in Debian as we still don't know much about this u-boot yet).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/26/2018 12:13PM by bodhi.
|
Bob
Re: Dell Wyse T10 / T50 August 26, 2018 12:32PM |
|
Re: Dell Wyse T10 / T50 August 27, 2018 12:30PM |
Admin Registered: 13 years ago Posts: 18,548 |
Bob,
> It's unable to read the chip with fw_printenv
> after editing fw_env.config. Gives a bad CRC
> message.
That CRC error does not mean the chip is inaccesible. It means the envs are either at wrong location, or it was not initialized.
To determine if the SPI chip was OK, and mtd partition(s) is on it:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> It's unable to read the chip with fw_printenv
> after editing fw_env.config. Gives a bad CRC
> message.
That CRC error does not mean the chip is inaccesible. It means the envs are either at wrong location, or it was not initialized.
To determine if the SPI chip was OK, and mtd partition(s) is on it:
cat /proc/mtd
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 27, 2018 01:56PM |
Hi bodhi
I see. I guess I didn't edit the config properly. It doesn't help that the format is different from the old Ubuntu version.
contents of original Ubuntu fw_env.config:
I see. I guess I didn't edit the config properly. It doesn't help that the format is different from the old Ubuntu version.
contents of original Ubuntu fw_env.config:
# MTD device offset size erase_size /dev/mtd0 0xc0000 0x10000 0x10000output of cat /proc/mtd:
dev: size erasesize name mtd0: 00400000 00001000 "spi0.0"What should my new config be?
|
Bob
Re: Dell Wyse T10 / T50 August 27, 2018 02:13PM |
|
Re: Dell Wyse T10 / T50 August 27, 2018 03:26PM |
Admin Registered: 13 years ago Posts: 18,548 |
Bob Wrote:
-------------------------------------------------------
> Hi bodhi
>
> I see. I guess I didn't edit the config properly.
> It doesn't help that the format is different from
> the old Ubuntu version.
>
> contents of original Ubuntu fw_env.config:
>
> # MTD device offset size erase_size
> /dev/mtd0 0xc0000 0x10000 0x10000
This location looks like one for my uboot envs.
>
> output of cat /proc/mtd:
>
No idea! The env location is somewhere in mtd0. It should not be 0x0, though.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Hi bodhi
>
> I see. I guess I didn't edit the config properly.
> It doesn't help that the format is different from
> the old Ubuntu version.
>
> contents of original Ubuntu fw_env.config:
>
> # MTD device offset size erase_size
> /dev/mtd0 0xc0000 0x10000 0x10000
This location looks like one for my uboot envs.
>
> output of cat /proc/mtd:
>
> dev: size erasesize name > mtd0: 00400000 00001000 "spi0.0" >> What should my new config be?
No idea! The env location is somewhere in mtd0. It should not be 0x0, though.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
