Debian on Dell Wyse T10 / T50
Posted by Koen
|
Re: Dell Wyse T10 / T50 August 28, 2018 02:42AM |
Admin Registered: 13 years ago Posts: 18,575 |
Bob,
Does your stock OS have the same /etc/fw_env.config as Koen’s?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Does your stock OS have the same /etc/fw_env.config as Koen’s?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 28, 2018 05:28AM |
Hi bodhi
Yes it's the same. I was wondering if it might be a generic one, but Koen was able to read his chip after replacing the contents of fw_env.config with the Ubuntu values. The stock Ubuntu doesn't expose the mtd device. So even if I install u-boot-tools on that fw_printenv can't find it.
I spent some time yesterday looking into mtd and looking at the output of mtd_debug and mtdinfo and I don't see how the values in the Ubuntu fw_env.config file correspond to the output from those tools.
I looked at the source code you mentioned a few posts back and the mimas board .c file has offset as 0 for the mtd device (if I'm reading that right).
Yes it's the same. I was wondering if it might be a generic one, but Koen was able to read his chip after replacing the contents of fw_env.config with the Ubuntu values. The stock Ubuntu doesn't expose the mtd device. So even if I install u-boot-tools on that fw_printenv can't find it.
I spent some time yesterday looking into mtd and looking at the output of mtd_debug and mtdinfo and I don't see how the values in the Ubuntu fw_env.config file correspond to the output from those tools.
mtd_debug info /dev/mtd0 mtd.type = MTD_NORFLASH mtd.flags = MTD_CAP_NORFLASH mtd.size = 4194304 (4M) mtd.erasesize = 4096 (4K) mtd.writesize = 1 mtd.oobsize = 0 regions = 0
mtdinfo --all /dev/mtd0 Count of MTD devices: 1 Present MTD devices: mtd0 Sysfs interface supported: yes mtd0 Name: spi0.0 Type: nor Eraseblock size: 4096 bytes, 4.0 KiB Amount of eraseblocks: 1024 (4194304 bytes, 4.0 MiB) Minimum input/output unit size: 1 byte Sub-page size: 1 byte Character device major/minor: 90:0 Bad blocks are allowed: false Device is writable: true
I looked at the source code you mentioned a few posts back and the mimas board .c file has offset as 0 for the mtd device (if I'm reading that right).
|
Re: Dell Wyse T10 / T50 August 28, 2018 12:09PM |
Admin Registered: 13 years ago Posts: 18,575 |
Bob,
> I looked at the source code you mentioned a few
> posts back and the mimas board .c file has offset
> as 0 for the mtd device (if I'm reading that
> right).
That's incorrect. That code is the kernel code patch which does not have any info about boot loader. What we lack is the GPL for their boot loader version. And they also turned off input/ouput for this boot loader so we can't see anything.
That's why I said I don't know yet where is the evns location, other than what Koen posted. Can you do a hex dump for mtd to see you can guess where the envs are, or you can dd the mtd0 and upload the dump somewhere so I can take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I looked at the source code you mentioned a few
> posts back and the mimas board .c file has offset
> as 0 for the mtd device (if I'm reading that
> right).
That's incorrect. That code is the kernel code patch which does not have any info about boot loader. What we lack is the GPL for their boot loader version. And they also turned off input/ouput for this boot loader so we can't see anything.
That's why I said I don't know yet where is the evns location, other than what Koen posted. Can you do a hex dump for mtd to see you can guess where the envs are, or you can dd the mtd0 and upload the dump somewhere so I can take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 28, 2018 12:39PM |
|
Bob
Re: Dell Wyse T10 / T50 August 28, 2018 07:41PM |
Hi bodhi
Looking at the dump in a hex editor there's a chunk of data that begins at E000 which sounds like a likely offset to me.
I've tried using these settings in the fw_env.config:
Looking at the dump in a hex editor there's a chunk of data that begins at E000 which sounds like a likely offset to me.
I've tried using these settings in the fw_env.config:
device offset: 0xe000 env. size: 0x400000 flash sector size: 0x1000 number of sectors: 400And I get:
Read error on /dev/mtd0: Success
|
Re: Dell Wyse T10 / T50 August 28, 2018 09:14PM |
Admin Registered: 13 years ago Posts: 18,575 |
Bob,
I took a look. There is no envs in there that I can see.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I took a look. There is no envs in there that I can see.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 29, 2018 05:31AM |
|
Re: Dell Wyse T10 / T50 August 29, 2018 04:10PM |
Registered: 5 years ago Posts: 182 |
Just got home and it is great to see that more progress has been made. Below is the dmesg output of booting with the latest dtb file. Ethernet is working and the box powers off properly as well.
My fw_env.config settings:
Output from cat /proc/mtd:
Output from fw_printenv:
I'll chase Dell again to see if we can get more info about the version of uboot they have used and hopefully the sources.
Koen
Edited 1 time(s). Last edit at 08/29/2018 04:16PM by Koen.
root@debian:~# dmesg
[ 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 e6ff8000
[ 0.000000] Normal zone: 1264 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 161792 pages, LIFO batch:31
[ 0.000000] HighMem zone: 100352 pages, LIFO batch:31
[ 0.000000] CPU: All CPU(s) started in SVC mode.
[ 0.000000] percpu: Embedded 17 pages/cpu @e6fd9000 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: 260880
[ 0.000000] Kernel command line: rootdelay=5 root=/dev/sdb1 pm_disable usb0Mode=host usb1Mode=host video=dovefb:lcd0:1024x600-16@60-edid,lcd1:1024x768-16@60-edid clcd.lcd0_enable=1 clcd.lcd1_enable=1 clcd.lcd0_clk=3 clcd.lcd1_clk=1 vmalloc=384M
[ 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: 1017980K/1048576K available (8192K kernel code, 712K rwdata, 2080K rodata, 1024K init, 331K bss, 30596K reserved, 0K cma-reserved, 401408K highmem)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xe8000000 - 0xff800000 ( 376 MB)
lowmem : 0xc0000000 - 0xe7800000 ( 632 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.000041] Switching to timer-based delay loop, resolution 6ns
[ 0.000581] Console: colour dummy device 80x30
[ 0.001322] console [tty0] enabled
[ 0.001364] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.001428] pid_max: default: 32768 minimum: 301
[ 0.001618] Security Framework initialized
[ 0.001731] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001775] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.002571] CPU: Testing write buffer coherency: ok
[ 0.002928] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.040181] Setting up static identity map for 0x100000 - 0x100060
[ 0.120089] smp: Bringing up secondary CPUs ...
[ 0.120142] smp: Brought up 1 node, 1 CPU
[ 0.120178] SMP: Total of 1 processors activated (333.33 BogoMIPS).
[ 0.120211] CPU: All CPU(s) started in SVC mode.
[ 0.121065] devtmpfs: initialized
[ 0.130508] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 5
[ 0.131050] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.131132] futex hash table entries: 256 (order: 2, 16384 bytes)
[ 0.131422] prandom: seed boundary self test passed
[ 0.134484] prandom: 100 self tests passed
[ 0.134517] pinctrl core: initialized pinctrl subsystem
[ 0.135616] NET: Registered protocol family 16
[ 0.136587] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.141194] cpuidle: using governor ladder
[ 0.141293] cpuidle: using governor menu
[ 0.141718] Dove 88AP510 SoC
[ 0.141764] Tauros2: Disabling L2 prefetch.
[ 0.141795] Tauros2: Disabling burst8 line fill.
[ 0.141824] Tauros2: Enabling L2 cache.
[ 0.141852] Tauros2: L2 cache support initialised in ARMv7 mode.
[ 0.142227] hw-breakpoint: debug architecture 0x4 unsupported.
[ 0.240633] vgaarb: loaded
[ 0.240967] SCSI subsystem initialized
[ 0.250159] libata version 3.00 loaded.
[ 0.250414] usbcore: registered new interface driver usbfs
[ 0.250509] usbcore: registered new interface driver hub
[ 0.250587] usbcore: registered new device driver usb
[ 0.250824] media: Linux media interface: v0.10
[ 0.250896] Linux video capture interface: v2.00
[ 0.260662] clocksource: Switched to clocksource orion_clocksource
[ 0.335266] VFS: Disk quotas dquot_6.6.0
[ 0.335390] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.353890] NET: Registered protocol family 2
[ 0.354930] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.355029] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.355140] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.355261] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.355317] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.355508] NET: Registered protocol family 1
[ 0.376204] RPC: Registered named UNIX socket transport module.
[ 0.376248] RPC: Registered udp transport module.
[ 0.376277] RPC: Registered tcp transport module.
[ 0.376306] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.376344] PCI: CLS 0 bytes, default 64
[ 0.376530] Unpacking initramfs...
[ 0.855389] Freeing initrd memory: 8072K
[ 0.855864] NetWinder Floating Point Emulator V0.97 (double precision)
[ 0.857625] audit: initializing netlink subsys (disabled)
[ 0.858828] Initialise system trusted keyrings
[ 0.858905] Key type blacklist registered
[ 0.859006] audit: type=2000 audit(0.857:1): state=initialized audit_enabled=0 res=1
[ 0.859246] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[ 0.859388] zbud: loaded
[ 0.880640] NFS: Registering the id_resolver key type
[ 0.880695] Key type id_resolver registered
[ 0.880724] Key type id_legacy registered
[ 0.880761] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.880796] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.881034] jffs2: version 2.2. (NAND) (SUMMARY) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
[ 0.881567] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 0.881829] orangefs_init: module version upstream loaded
[ 0.887124] Key type asymmetric registered
[ 0.887163] Asymmetric key parser 'x509' registered
[ 0.887248] bounce: pool size: 64 pages
[ 0.887321] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[ 0.887372] io scheduler noop registered
[ 0.887401] io scheduler deadline registered
[ 0.887476] io scheduler cfq registered (default)
[ 0.888245] dove-pinctrl f10d0200.pin-ctrl: falling back to hardcoded PMU resource
[ 0.888418] dove-pinctrl f10d0200.pin-ctrl: [Firmware Bug]: Missing pinctrl regs in DTB. Please update your firmware.
[ 0.889144] dove-pinctrl f10d0200.pin-ctrl: registered pinctrl driver
[ 0.892871] mvebu-pcie mbus:pcie: PCI host bridge to bus 0000:00
[ 0.892923] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.892961] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.893000] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.893035] pci_bus 0000:00: scanning bus
[ 0.893066] pci 0000:00:01.0: [11ab:0510] type 01 class 0x060400
[ 0.893110] pci 0000:00:01.0: calling pci_fixup_ide_bases+0x0/0x3c
[ 0.894447] pci 0000:00:02.0: [11ab:0510] type 01 class 0x060400
[ 0.894483] pci 0000:00:02.0: calling pci_fixup_ide_bases+0x0/0x3c
[ 0.895133] pci_bus 0000:00: fixups for bus
[ 0.895149] PCI: bus0: Fast back to back transfers disabled
[ 0.895195] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[ 0.895204] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.895263] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[ 0.895271] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.895328] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[ 0.895541] pci_bus 0000:01: scanning bus
[ 0.895577] pci 0000:01:00.0: [1814:3090] type 00 class 0x028000
[ 0.895608] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x0000ffff]
[ 0.895670] pci 0000:01:00.0: calling pci_fixup_ide_bases+0x0/0x3c
[ 0.920888] pci_bus 0000:01: fixups for bus
[ 0.920901] PCI: bus1: Fast back to back transfers disabled
[ 0.920943] pci_bus 0000:01: bus scan returning with max=01
[ 0.920955] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 0.920970] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[ 0.921188] pci_bus 0000:02: scanning bus
[ 0.921199] pci_bus 0000:02: fixups for bus
[ 0.921205] PCI: bus2: Fast back to back transfers enabled
[ 0.921243] pci_bus 0000:02: bus scan returning with max=02
[ 0.921253] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 0.921264] pci_bus 0000:00: bus scan returning with max=02
[ 0.921277] pci 0000:00:01.0: fixup irq: got 0
[ 0.921284] pci 0000:00:01.0: assigning IRQ 00
[ 0.921294] pci 0000:00:02.0: fixup irq: got 0
[ 0.921301] pci 0000:00:02.0: assigning IRQ 00
[ 0.921395] pci 0000:01:00.0: fixup irq: got 43
[ 0.921403] pci 0000:01:00.0: assigning IRQ 43
[ 0.921441] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[ 0.921486] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe000ffff]
[ 0.921527] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.921565] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 0.921606] pci 0000:00:02.0: PCI bridge to [bus 02]
[ 0.921718] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[ 0.921768] pcieport 0000:00:01.0: enabling bus mastering
[ 0.921844] pcieport 0000:00:02.0: enabling bus mastering
[ 0.922643] mv_xor f1060800.dma-engine: Marvell shared XOR driver
[ 0.981580] mv_xor f1060800.dma-engine: Marvell XOR (Registers Mode): ( xor cpy sg intr )
[ 0.981953] mv_xor f1060900.dma-engine: Marvell shared XOR driver
[ 1.041561] mv_xor f1060900.dma-engine: Marvell XOR (Registers Mode): ( xor cpy sg intr )
[ 1.162794] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 1.166112] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 21, base_baud = 10416666) is a 16550A
[ 1.167181] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 22, base_baud = 10416666) is a 16550A
[ 1.169368] sata_mv f10a0000.sata-host: version 1.28
[ 1.169521] sata_mv f10a0000.sata-host: slots 32 ports 1
[ 1.182011] scsi host0: sata_mv
[ 1.182414] ata1: SATA max UDMA/133 irq 33
[ 1.184214] m25p80 spi0.0: s25fl064k (8192 Kbytes)
[ 1.186837] libphy: Fixed MDIO Bus: probed
[ 1.187701] libphy: orion_mdio_bus: probed
[ 1.187752] [Firmware Warn]: /mbus/internal-regs/mdio-bus@72004/ethernet-phy: Whitelisted compatible string. Please remove
[ 1.204968] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 1.301780] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:80:64:aa:7d:6c
[ 1.302354] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.302412] ehci-pci: EHCI PCI platform driver
[ 1.302506] ehci-orion: EHCI orion driver
[ 1.302701] orion-ehci f1050000.usb-host: EHCI Host Controller
[ 1.302762] orion-ehci f1050000.usb-host: new USB bus registered, assigned bus number 1
[ 1.302942] orion-ehci f1050000.usb-host: irq 26, io mem 0xf1050000
[ 1.330641] orion-ehci f1050000.usb-host: USB 2.0 started, EHCI 1.00
[ 1.331012] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.331055] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.331105] usb usb1: Product: EHCI Host Controller
[ 1.331138] usb usb1: Manufacturer: Linux 4.12.4-mvebu-tld-1 ehci_hcd
[ 1.331173] usb usb1: SerialNumber: f1050000.usb-host
[ 1.331964] hub 1-0:1.0: USB hub found
[ 1.332079] hub 1-0:1.0: 1 port detected
[ 1.332621] orion-ehci f1051000.usb-host: EHCI Host Controller
[ 1.332681] orion-ehci f1051000.usb-host: new USB bus registered, assigned bus number 2
[ 1.332848] orion-ehci f1051000.usb-host: irq 27, io mem 0xf1051000
[ 1.360636] orion-ehci f1051000.usb-host: USB 2.0 started, EHCI 1.00
[ 1.360941] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.360983] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.361034] usb usb2: Product: EHCI Host Controller
[ 1.361066] usb usb2: Manufacturer: Linux 4.12.4-mvebu-tld-1 ehci_hcd
[ 1.361101] usb usb2: SerialNumber: f1051000.usb-host
[ 1.361813] hub 2-0:1.0: USB hub found
[ 1.361929] hub 2-0:1.0: 1 port detected
[ 1.362979] usbcore: registered new interface driver usblp
[ 1.363179] usbcore: registered new interface driver usb-storage
[ 1.363606] mousedev: PS/2 mouse device common for all mice
[ 1.364667] rtc-mv f10d8500.real-time-clock: rtc core: registered f10d8500.real-time- as rtc0
[ 1.365012] i2c /dev entries driver
[ 1.367990] orion_wdt: Initial timeout 25 sec
[ 1.371700] marvell-cesa f1030000.crypto-engine: CESA device successfully registered
[ 1.372013] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.372509] usbcore: registered new interface driver usbhid
[ 1.372546] usbhid: USB HID core driver
[ 1.372793] drop_monitor: Initializing network drop monitor service
[ 1.372888] Netfilter messages via NETLINK v0.30.
[ 1.372935] ip_set: protocol 6
[ 1.373266] NET: Registered protocol family 10
[ 1.384502] Segment Routing with IPv6
[ 1.384602] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 1.386405] NET: Registered protocol family 17
[ 1.386494] 8021q: 802.1Q VLAN Support v1.8
[ 1.386564] Key type dns_resolver registered
[ 1.386993] ThumbEE CPU extension supported.
[ 1.387029] Registering SWP/SWPB emulation handler
[ 1.387061] PJ4 iWMMXt v2 coprocessor enabled.
[ 1.387951] registered taskstats version 1
[ 1.387987] Loading compiled-in X.509 certificates
[ 1.388068] zswap: loaded using pool lzo/zbud
[ 1.471983] Key type big_key registered
[ 1.478833] Key type encrypted registered
[ 1.481177] rtc-mv f10d8500.real-time-clock: setting system clock to 2018-08-29 21:00:54 UTC (1535576454)
[ 1.481381] PM: Hibernation image not present or could not be loaded.
[ 1.680640] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl F300)
[ 1.710628] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 1.710914] ata1.00: CFA: 1GB ATA Flash Disk, AD B612J, max UDMA/66
[ 1.710952] ata1.00: 2001888 sectors, multi 0: LBA
[ 1.740817] ata1.00: configured for UDMA/66
[ 1.751439] scsi 0:0:0:0: Direct-Access ATA 1GB ATA Flash Di 612J PQ: 0 ANSI: 5
[ 1.752942] sd 0:0:0:0: [sda] 2001888 512-byte logical blocks: (1.02 GB/977 MiB)
[ 1.753060] sd 0:0:0:0: [sda] Write Protect is off
[ 1.753097] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.753204] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.755374] sda: sda1 sda2 sda3
[ 1.757259] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.758910] Freeing unused kernel memory: 1024K
[ 1.853258] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 1.853824] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 1.853970] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 1.864474] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.865531] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.866070] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.866670] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.867237] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.867770] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.868252] random: udevadm: uninitialized urandom read (16 bytes read)
[ 1.882575] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 1.882628] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.882666] usb 1-1: Product: USB2.0 Hub
[ 1.885533] hub 1-1:1.0: USB hub found
[ 1.885956] hub 1-1:1.0: 4 ports detected
[ 2.200657] usb 1-1.4: new high-speed USB device number 3 using orion-ehci
[ 2.290952] i2c i2c-0: Added multiplexed i2c bus 1
[ 2.291340] i2c i2c-0: Added multiplexed i2c bus 2
[ 2.291663] i2c i2c-0: Added multiplexed i2c bus 3
[ 2.351699] usb 1-1.4: New USB device found, idVendor=0781, idProduct=5530
[ 2.351758] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.351810] usb 1-1.4: Product: Cruzer
[ 2.351841] usb 1-1.4: Manufacturer: SanDisk
[ 2.351872] usb 1-1.4: SerialNumber: 20060775210A3B80C5B2
[ 2.352631] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 2.368292] scsi host1: usb-storage 1-1.4:1.0
[ 2.389922] sdhci: Secure Digital Host Controller Interface driver
[ 2.389975] sdhci: Copyright(c) Pierre Ossman
[ 2.412818] sdhci-pltfm: SDHCI platform and OF driver helper
[ 2.471819] mmc0: SDHCI controller on f1090000.sdio-host [f1090000.sdio-host] using DMA
[ 2.533035] mmc1: SDHCI controller on f1092000.sdio-host [f1092000.sdio-host] using DMA
[ 2.613789] random: fast init done
[ 3.456288] scsi 1:0:0:0: Direct-Access SanDisk Cruzer 1.26 PQ: 0 ANSI: 5
[ 3.472618] sd 1:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[ 3.473355] sd 1:0:0:0: [sdb] Write Protect is off
[ 3.473397] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 3.474106] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3.479216] sdb: sdb1
[ 3.482607] sd 1:0:0:0: [sdb] Attached SCSI removable disk
[ 3.485192] usbcore: registered new interface driver uas
[ 8.900011] EXT4-fs (sdb1): mounting ext3 file system using the ext4 subsystem
[ 8.921447] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 11.322934] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 11.323215] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 12.109617] pci 0000:00:01.0: enabling bus mastering
[ 12.109635] rt2800pci 0000:01:00.0: enabling device (0140 -> 0142)
[ 12.109698] rt2800pci 0000:01:00.0: enabling bus mastering
[ 12.109710] rt2800pci 0000:01:00.0: enabling Mem-Wr-Inval
[ 12.115789] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3090, rev 3212 detected
[ 12.119284] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[ 12.164618] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 13.119914] rt2800pci 0000:01:00.0 wlp1s0: renamed from wlan0
[ 13.771424] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro
[ 14.190696] random: crng init done
[ 16.393320] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.758217] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 18.758335] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
root@debian:~#
My fw_env.config settings:
root@debian:~# cat /etc/fw_env.config # MTD device offset size erase_size /dev/mtd0 0xc0000 0x10000 0x10000 root@debian:~#
Output from cat /proc/mtd:
root@debian:~# cat /proc/mtd dev: size erasesize name mtd0: 00800000 00001000 "spi0.0" root@debian:~#
Output from fw_printenv:
root@debian:~# fw_printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200 useNandHal=single
mtdparts=mtdparts=spi0.0:768k(u-boot)ro,128k(uboot_env),-(kernel)
arcNumber=1789
CASset=min
MALLOC_len=5
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::dove:eth0:none
image_name=uImage
tftpbootcmd=tftpboot 0x2000000 ${image_name}; setenv bootargs ${console} ${mtdparts} ${bootargs_root} nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}${bootargs_end} usb0Mode=${usb0Mode} usb1Mode=${usb1Mode} video=dovefb:lcd0:${lcd0_params},lcd1:${lcd1_params} clcd.lcd0_enable=${lcd0_enable} clcd.lcd1_enable=${lcd1_enable}; bootm 0x2000000;
standalone=fsload 0x2000000 ${image_name};setenv bootargs ${console} ${mtdparts} root=/dev/mtdblock0 rw ip=${ipaddr}:${serverip}${bootargs_end} usb0Mode=${usb0Mode} usb1Mode=${usb1Mode} video=dovefb:lcd0:${lcd0_params},lcd1:${lcd1_params} clcd.lcd0_enable=${lcd0_enable} clcd.lcd1_enable=${lcd1_enable}; bootm 0x2000000;
bootsd=sflash read a0000 0x2000000 0x300000;setenv bootargs ${console} ${mtdparts} rootdelay=5 root=/dev/mmcblk0 rw usb0Mode=${usb0Mode} usb1Mode=${usb1Mode} video=dovefb:lcd0:${lcd0_params},lcd1:${lcd1_params} clcd.lcd0_enable=${lcd0_enable} clcd.lcd1_enable=${lcd1_enable}; bootm 0x2000000;
bootusb=sflash read a0000 0x2000000 0x300000;setenv bootargs ${console} ${mtdparts} rootdelay=5 root=/dev/sda rw usb0Mode=${usb0Mode} usb1Mode=${usb1Mode} video=dovefb:lcd0:${lcd0_params},lcd1:${lcd1_params} clcd.lcd0_enable=${lcd0_enable} clcd.lcd1_enable=${lcd1_enable}; bootm 0x2000000;
bootnand=sflash read a0000 0x2000000 0x300000;setenv bootargs ${console} ${mtdparts} ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw usb0Mode=${usb0Mode} usb1Mode=${usb1Mode} video=dovefb:lcd0:${lcd0_params},lcd1:${lcd1_params} clcd.lcd0_enable=${lcd0_enable} clcd.lcd1_enable=${lcd1_enable}; bootm 0x2000000;
disaMvPnp=no
usb0Mode=host
usb1Mode=host
yuk_ethaddr=00:00:00:EE:51:81
lcd0_enable=0
lcd1_enable=1
ethact=egiga0
bootcmd=sf read 0x2000000 0x400000 0x380000;bootm 0x2000000
stdin=serial
stdout=serial
stderr=serial
passDramInitTag=yes
mainlineLinux=yes
enaMonExt=no
pexMode=RC
disL2Cache=no
disL2Ecc=no
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootcmd_orig=echo Scanning for boot devices;usb start;ide reset;for i in usb ide;do for j in 0 1; do for l in / /boot/;do for m in fat ext2;do setenv interface $i;setenv device $j;setenv prefix $l;setenv fs $m;setenv partition 1;echo Scanning ${fs} ${interface} ${device} on prefix ${prefix} ...;if ${fs}load ${interface} ${device} 1000 ${prefix}boot.scr; then;if imi 1000; then echo boot.scr found! Executing ...;autoscr 1000;fi;fi;done;done;done;done;echo No boot device found. Falling back to TFTP boot;run tftpbootcmd;
bootdelay=3
menucmd=wtest t;wconsole y;run usb_kbd
get=tftpboot 0x2000000 u-boot-m.bin;go 0x2000000
usb_kbd=echo no USB Keyboard support
enaL2ExtraFeatures=yes
enaCpuStream=no
enaVpuPower=yes
enaGpuPower=yes
ethaddr=00:80:64:2a:1b:3a
bootargs=rootdelay=10 mtdparts=spi0.0:8192k(u-boot)rw root=/dev/sda3 rw ip=10.4.50.165:10.4.50.5:::dove:eth0:none usb0Mode=host usb1Mode=host video=dovefb:lcd0:1366x768-16@60-edid,lcd1:1366x768-16@60-edid clcd.lcd0_enable=1 clcd.lcd1_enable=1 pm_disable no_console_suspend clcd.lcd0_clk=3 clcd.lcd1_clk=1 cpufreq_disable quiet vmalloc=384MB
root@debian:~#
I'll chase Dell again to see if we can get more info about the version of uboot they have used and hopefully the sources.
Koen
Edited 1 time(s). Last edit at 08/29/2018 04:16PM by Koen.
|
Re: Dell Wyse T10 / T50 August 29, 2018 04:31PM |
Registered: 5 years ago Posts: 182 |
Some more info about mtd. It seems the chip in my box is 8M while that in Bob's device is reported to be only 4M although that may possibly be due to different fw_env.config settings.
Koen
Koen
root@debian:~# mtd_debug info /dev/mtd0 mtd.type = MTD_NORFLASH mtd.flags = MTD_CAP_NORFLASH mtd.size = 8388608 (8M) mtd.erasesize = 4096 (4K) mtd.writesize = 1 mtd.oobsize = 0 regions = 0
root@debian:~# mtdinfo --all /dev/mtd0 Count of MTD devices: 1 Present MTD devices: mtd0 Sysfs interface supported: yes mtd0 Name: spi0.0 Type: nor Eraseblock size: 4096 bytes, 4.0 KiB Amount of eraseblocks: 2048 (8388608 bytes, 8.0 MiB) Minimum input/output unit size: 1 byte Sub-page size: 1 byte Character device major/minor: 90:0 Bad blocks are allowed: false Device is writable: true
|
Re: Dell Wyse T10 / T50 August 29, 2018 04:33PM |
Admin Registered: 13 years ago Posts: 18,575 |
Koen Wrote:
-------------------------------------------------------
> Ethernet is
> working and the box powers off properly as well.
Cool!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Ethernet is
> working and the box powers off properly as well.
Cool!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 29, 2018 04:42PM |
Admin Registered: 13 years ago Posts: 18,575 |
Ok so
@Bob,
Try using the same fw_env.config as Koen's
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
Bob
output of cat /proc/mtd:
dev: size erasesize name
mtd0: 00400000 00001000 "spi0.0"
Quote
Koen
root@debian:~# cat /proc/mtd
dev: size erasesize name
mtd0: 00800000 00001000 "spi0.0"
@Bob,
Try using the same fw_env.config as Koen's
root@debian:/etc# cat /etc/fw_env.config # MTD device offset size erase_size /dev/mtd0 0xc0000 0x10000 0x10000
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 29, 2018 05:17PM |
|
Re: Dell Wyse T10 / T50 August 29, 2018 05:26PM |
Admin Registered: 13 years ago Posts: 18,575 |
Bob Wrote:
-------------------------------------------------------
> Hi bodhi and Koen
>
> I already tried that (default Ubuntu) config. It
> just gives a bad CRC message.
>
> Perhaps the dtb needs to match my spi chip? I
> edited the last dts with the details for my chip
> but couldn't figure out how to compile it to a
> dtb.
Let me find the sector size.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Hi bodhi and Koen
>
> I already tried that (default Ubuntu) config. It
> just gives a bad CRC message.
>
> Perhaps the dtb needs to match my spi chip? I
> edited the last dts with the details for my chip
> but couldn't figure out how to compile it to a
> dtb.
Let me find the sector size.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 29, 2018 06:09PM |
Admin Registered: 13 years ago Posts: 18,575 |
bodhi Wrote:
>
> Let me find the sector size.
The definition in /etc/fw_env.config should be the same. Unless a different u-boot version is on Bob's box, therefore the location is different.
I'm compiling a new DTB to see if Bob can use to eliminate that SPI chip variation.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
>
> Let me find the sector size.
The definition in /etc/fw_env.config should be the same. Unless a different u-boot version is on Bob's box, therefore the location is different.
I'm compiling a new DTB to see if Bob can use to eliminate that SPI chip variation.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 29, 2018 07:34PM |
Admin Registered: 13 years ago Posts: 18,575 |
Here is the new DTB for Bob and Koen to check SPI flash.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/29/2018 07:35PM by bodhi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 08/29/2018 07:35PM by bodhi.
|
Bob
Re: Dell Wyse T10 / T50 August 29, 2018 07:55PM |
|
Re: Dell Wyse T10 / T50 August 29, 2018 08:43PM |
Admin Registered: 13 years ago Posts: 18,575 |
That's right, should be either st or macronix.
Here is another compilation using st.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Here is another compilation using st.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 August 30, 2018 05:19AM |
Hi bodhi
That doesn't change anything here. Still get the same message in dmesg:
That doesn't change anything here. Still get the same message in dmesg:
dmesg | grep spi [ 1.118180] m25p80 spi0.0: found mx25l3205d, expected s25fl064k [ 1.118196] m25p80 spi0.0: mx25l3205d (4096 Kbytes)and the same output from fw_printenv:
fw_printenv Warning: Bad CRC, using default environment
|
Re: Dell Wyse T10 / T50 August 30, 2018 12:33PM |
Registered: 5 years ago Posts: 182 |
|
Re: Dell Wyse T10 / T50 August 30, 2018 01:11PM |
Admin Registered: 13 years ago Posts: 18,575 |
Koen,
> do you want me to try these latest dtb files as
> well? I've had another response from Dell that
> they will chase the technical team for the uboot
> GPL sources of the T50.
Sure, please try the latest DTB file (good to do regression test).
Hope they will make GPL source available, that will solve the remaining issues for us. The fact that CRC error show up in Bob's box make me think there are 2 different u-boot version for T50 (Bob) and T10 (yours).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> do you want me to try these latest dtb files as
> well? I've had another response from Dell that
> they will chase the technical team for the uboot
> GPL sources of the T50.
Sure, please try the latest DTB file (good to do regression test).
Hope they will make GPL source available, that will solve the remaining issues for us. The fact that CRC error show up in Bob's box make me think there are 2 different u-boot version for T50 (Bob) and T10 (yours).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 August 30, 2018 03:52PM |
Registered: 5 years ago Posts: 182 |
|
Re: Dell Wyse T10 / T50 August 31, 2018 12:31AM |
Admin Registered: 13 years ago Posts: 18,575 |
Hi Koen,
> Some more info about mtd. It seems the chip in my
> box is 8M while that in Bob's device is reported
> to be only 4M although that may possibly be due to
> different fw_env.config settings.
No, it is not fw_env.config. The size of the mtd is recognized by the kernel when it probes the mtd. So the mtd sizes are correct as the kernel sees. What in the fw_env.config is not the mtd size, it is the envs size. So if the envs size or the location are different, then the CRC error would make sense (this would be true if the u-boot versions are different between the 2 boxes).
This should be commented as:
Note that erase_size is the sector size (64KB). And the total envs size is 64KB. These 2 chip types also have 4K sector erase capability. Regardless, erase size 64KB is OK here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Some more info about mtd. It seems the chip in my
> box is 8M while that in Bob's device is reported
> to be only 4M although that may possibly be due to
> different fw_env.config settings.
No, it is not fw_env.config. The size of the mtd is recognized by the kernel when it probes the mtd. So the mtd sizes are correct as the kernel sees. What in the fw_env.config is not the mtd size, it is the envs size. So if the envs size or the location are different, then the CRC error would make sense (this would be true if the u-boot versions are different between the 2 boxes).
This should be commented as:
root@debian:/etc# cat /etc/fw_env.config # MTD device offset env size erase_size /dev/mtd0 0xc0000 0x10000 0x10000
Note that erase_size is the sector size (64KB). And the total envs size is 64KB. These 2 chip types also have 4K sector erase capability. Regardless, erase size 64KB is OK here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Dell Wyse T10 / T50 September 01, 2018 09:54AM |
Registered: 5 years ago Posts: 182 |
I've had a look through the Ubuntu sources and found this stuff related to the different SPI chips. Not sure if useful since source code is like a foreign language to me.
in ubuntu-lucid/arm/arch/mach-dove/dove-db-setup.c it mentions an 8M chip that looks a bit like the one in my dmesg log (s25fl064k )
while in ubuntu-lucid/arm/arch/mach-dove/mimas.c it mentions a 4M chip which matches the chip in Bobs machine. (mx25l3205d)
Koen
Edited 1 time(s). Last edit at 09/01/2018 10:10AM by Koen.
in ubuntu-lucid/arm/arch/mach-dove/dove-db-setup.c it mentions an 8M chip that looks a bit like the one in my dmesg log (s25fl064k )
/*****************************************************************************
* SPI Devices:
* SPI0: 8M Flash ST-M25P64-VMF6P
****************************************************************************/
static const struct flash_platform_data dove_db_spi_flash_data = {
.type = "m25p64",
};
static struct spi_board_info __initdata dove_db_spi_flash_info[] = {
{
.modalias = "m25p80",
.platform_data = &dove_db_spi_flash_data,
.irq = -1,
.max_speed_hz = 20000000,
.bus_num = 0,
.chip_select = 0,
},
};
while in ubuntu-lucid/arm/arch/mach-dove/mimas.c it mentions a 4M chip which matches the chip in Bobs machine. (mx25l3205d)
/*****************************************************************************
* SPI Devices:
* SPI0: 4M Flash MX25L3205D
****************************************************************************/
static const struct flash_platform_data spi_flash_data = {
.type = "mx25l3205d",
};
static struct spi_board_info __initdata spi_flash_info[] = {
{
.modalias = "m25p80",
.platform_data = &spi_flash_data,
.irq = -1,
.max_speed_hz = 20000000,
.bus_num = 0,
.chip_select = 0,
},
};
Koen
Edited 1 time(s). Last edit at 09/01/2018 10:10AM by Koen.
|
Re: Dell Wyse T10 / T50 September 01, 2018 03:31PM |
Admin Registered: 13 years ago Posts: 18,575 |
Hi Bob,
Rename the attached DTB to dove-wyse-t50.dtb and try booting with it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Rename the attached DTB to dove-wyse-t50.dtb and try booting with it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 September 01, 2018 04:36PM |
Hi bodhi
That one seems to find my spi chip ok:
That one seems to find my spi chip ok:
dmesg | grep spi [ 1.118436] m25p80 spi0.0: mx25l3205d (4096 Kbytes)However I still get the bad CRC message with fw_printenv:
fw_printenv Warning: Bad CRC, using default environmentUsing default values from Ubuntu:
cat /etc/fw_env.config # MTD device offset size erase_size /dev/mtd0 0xc0000 0x10000 0x10000
|
Re: Dell Wyse T10 / T50 September 01, 2018 04:51PM |
Admin Registered: 13 years ago Posts: 18,575 |
Bob,
> That one seems to find my spi chip ok:
>
That's is actually the same as what you got before (the 2nd line where the kernel determined the right chip after the 1st message). I just want to show you the confirmation.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> That one seems to find my spi chip ok:
>
> dmesg | grep spi > [ 1.118436] m25p80 spi0.0: mx25l3205d (4096 > Kbytes) >
That's is actually the same as what you got before (the 2nd line where the kernel determined the right chip after the 1st message). I just want to show you the confirmation.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 September 01, 2018 04:54PM |
|
Re: Dell Wyse T10 / T50 September 01, 2018 05:22PM |
Admin Registered: 13 years ago Posts: 18,575 |
Hi Bob,
> I just assumed that it was working better now that
> it didn't have the "found mx25l3205d, expected
> s25fl064k" line.
I meant to assure you that it works the same way regardless of that warning. The 2nd line is all we need to know that the chip was recognized correctly by the kernel.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I just assumed that it was working better now that
> it didn't have the "found mx25l3205d, expected
> s25fl064k" line.
I meant to assure you that it works the same way regardless of that warning. The 2nd line is all we need to know that the chip was recognized correctly by the kernel.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Bob
Re: Dell Wyse T10 / T50 September 01, 2018 05:28PM |
Hi bodhi
OK, cool. It would be nice to have it working at some stage. I'd like to see if I can clean up the boot entries in the spi. I was able to edit them on Ubuntu with spi-w but they would reset back to default after a reboot. Which had me wonder if this was working right at all. Koen seemed to be able to edit them fine.
OK, cool. It would be nice to have it working at some stage. I'd like to see if I can clean up the boot entries in the spi. I was able to edit them on Ubuntu with spi-w but they would reset back to default after a reboot. Which had me wonder if this was working right at all. Koen seemed to be able to edit them fine.
|
Re: Dell Wyse T10 / T50 September 01, 2018 06:49PM |
Admin Registered: 13 years ago Posts: 18,575 |
New kernel was uploaded. Please upgrade your T50/T10 box to this kernel.
The Armada DRM was configured in this kernel as module armada.
I'm not sure if the bootargs video name should be armada, but probably not dovefb anymore.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
The Armada DRM was configured in this kernel as module armada.
I'm not sure if the bootargs video name should be armada, but probably not dovefb anymore.
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
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
