Welcome! Log In Create A New Profile

Advanced

Debian on Promwad-Thinclient

Posted by cmp18 
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 01, 2025 11:47PM
MM & cmp18,

Thanks for the log.

Yes, the i2c pinctrl error need to be fixed before we can see the hub spins up or not!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 02, 2025 10:47AM
bodhi, cmp18


6282 has two i2c buses, may be 64 is valid addres for second?

http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/145043.html
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 02, 2025 12:07PM
...

from kirkwood-6282.dtsi:


/*
			 * Default I2C1 pinctrl setting on mpp36/mpp37,
			 * overwrite marvell,pins on board level if required.
			 */
			pmx_twsi1: pmx-twsi1 {
				marvell,pins = "mpp36", "mpp37";
				marvell,function = "twsi1";
			};

in the 6282 dtsi i2c1 is defined, not i2c0
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 02, 2025 01:41PM
MM,

> in the 6282 dtsi i2c1 is defined, not i2c0

i2c0 is defined in kirkwood.dtsi. Look at the include chain. Usually, a board uses i2c0, unless it is more complex and needs i2c1.

People have seen 64 as the 2nd address, but nobody has bothered trying to figure out whether it is i2c1. The guess is it is for debugging purpose.

===
edit: typos

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



Edited 1 time(s). Last edit at 01/02/2025 02:56PM by bodhi.
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 02, 2025 01:45PM
Here is another version for the DTB.

In retrospect, using the OpenBlocks A7 board DTS as a base was my mistake. By now, I've realized that it has almost nothing in common with the PrompWad.

We'll need to strip out more nodes from this DTS. But for now, it is to solve the USB problem first so I let it stay the way it is, unless there is a conflict.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Attachments:
open | download - kirkwood-promwad-thin-client.dtb (11.3 KB)
open | download - kirkwood-promwad-thin-client.dts (2.7 KB)
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 02, 2025 03:16PM
bodhi,

cool,

pin8 and pin9 (twsi0) was busy by uart1

Thanks!

====
edit: i reread pin functions and dts)



Edited 1 time(s). Last edit at 01/02/2025 11:56PM by MM.
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 03, 2025 09:24AM
bodhi,

log with new DTB
Attachments:
open | download - 03_01_log.txt (80.8 KB)
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 03, 2025 10:38AM
the new box seems to have problems(

log from the old one
Attachments:
open | download - new_log.txt (26.7 KB)
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 09, 2025 10:33PM
MM,

The patch linux-3.1.1_r1416.patch is quite confusing. I think the patch is wrong.

i2c0 is for the Audio device.
+static struct i2c_board_info i2c0_board_info[] __initdata = {
+	{
+		I2C_BOARD_INFO("alc5621", 0x1a),
+		.platform_data = &alc5621_data,
+	},
+};

But the USB hub is on i2c1 only and if it is not Thin Client.

+#ifdef CONFIG_WTPLUG_THINCLIENT
+static struct alc5623_platform_data alc5621_data = {
+	.add_ctrl = 0x3700,
+	.jack_det_ctrl = 0x4980,
+};
+
+static struct i2c_board_info i2c0_board_info[] __initdata = {
+	{
+		I2C_BOARD_INFO("alc5621", 0x1a),
+		.platform_data = &alc5621_data,
+	},
+};
+
+#else
+
+static struct i2c_board_info i2c1_board_info[] __initdata = {
+	{
+		I2C_BOARD_INFO("usb2514", 0x2c),
+	},
+};
+
+#endif


+#ifndef CONFIG_WTPLUG_THINCLIENT
+	platform_device_register(&wtplug_leds);
+	/* set poweroff function */
+	pm_power_off = wtplug_poweroff;
+	
+#if defined(CONFIG_USB_251XHUB)
+	usb2514_hub_to_smbus();
+#endif
+	i2c_register_board_info(1, i2c1_board_info,
+			ARRAY_SIZE(i2c1_board_info));
+#endif
+#ifdef CONFIG_WTPLUG_THINCLIENT
+	i2c_register_board_info(0, i2c0_board_info,
+		ARRAY_SIZE(i2c0_board_info));
+	kirkwood_audio_init();
+#endif

Could you try

i2c probe 0
i2c probe 1

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



Edited 1 time(s). Last edit at 01/09/2025 10:35PM by bodhi.
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 10, 2025 12:56PM
bodhi,

u-boot i2c probe:

Marvell>> i2c probe
Valid chip addresses: 1A 64
Marvell>> i2c probe 0
Valid chip addresses: 1A 64
Marvell>> i2c probe 1
Valid chip addresses: 1A 64
Marvell>>
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 23, 2025 02:41PM
All,

Please try these new DTBs. I've changed USB Hub to i2c1 and added PCIe.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Attachments:
open | download - kirkwood-promwad-wtplug.dtb (11.3 KB)
open | download - kirkwood-promwad-thin-client.dtb (11.3 KB)
open | download - kirkwood-promwad.dts.tar (10 KB)
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 24, 2025 07:40AM
bodhi,

With new kirkwood-promwad-thin-client.dtb USB power insufficient is not repaired:(
PCIe not testing yet.
Log attached.

U-Boot 2011.06 (Jan 03 2013 - 16:19:06)
Promwad-ThinClient

SoC:   Kirkwood 88F6282_?? RevID 0x01
DRAM:  1 GiB
NAND:  1024 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1121 Initialized on egiga0, devadr 1
88E1121 Initialized on egiga1, devadr 0
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0xa00000
 10485760 bytes read: OK
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-5.15.167-1
   Created:      2025-01-24  13:10:05 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3123953 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 6.6.63 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 13.3.0 r28161-ea17e958b9) 13.3.0, GNU ld (GNU Binutils) 2.42) #0 Tue Dec  3 11:41:08 2024
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] OF: fdt: Machine model: Promwad WTPlug Thin Client
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Ignoring RAM at 0x30000000-0x40000000
[    0.000000] Consider using a HIGHMEM enabled kernel.
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000002fffffff]
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Kernel command line: console=ttyS0,115200 loglevel=9 mtdparts=orion_nand:1M(U-Boot),10M(uImage),-(ubipart) earlyprintk=serial ubi.mtd=2 ubi.block=0,rootfs root=/dev/ubiblock0_0
[    0.000000] Unknown kernel command line parameters "earlyprintk=serial", will be passed to user space.
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 194880
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 767560K/786432K available (7189K kernel code, 594K rwdata, 1076K rodata, 1024K init, 235K bss, 18872K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000001] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000025] Switching to timer-based delay loop, resolution 5ns
[    0.000099] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.000114] CPU: Testing write buffer coherency: ok
[    0.000178] pid_max: default: 32768 minimum: 301
[    0.007328] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.007346] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.013428] RCU Tasks Trace: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=1.
[    0.013581] Setting up static identity map for 0x100000 - 0x10003c
[    0.013745] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[    0.017414] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.017434] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.019282] pinctrl core: initialized pinctrl subsystem
[    0.021518] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.021932] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.022694] thermal_sys: Registered thermal governor 'step_wise'
[    0.022718] cpuidle: using governor ladder
[    0.022987] [Firmware Bug]: Feroceon L2: bootloader left the L2 cache on!
[    0.022993] Feroceon L2: Cache support initialised.
[    0.027238] No ATAGs?
[    0.032322] SCSI subsystem initialized
[    0.032829] libata version 3.00 loaded.
[    0.033014] usbcore: registered new interface driver usbfs
[    0.033073] usbcore: registered new interface driver hub
[    0.033110] usbcore: registered new device driver usb
[    0.034518] clocksource: Switched to clocksource orion_clocksource
[    0.042233] NET: Registered PF_INET protocol family
[    0.042486] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.045097] tcp_listen_portaddr_hash hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.045122] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.045136] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    0.045229] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.046198] TCP: Hash tables configured (established 8192 bind 8192)
[    0.046702] MPTCP token hash table entries: 1024 (order: 1, 12288 bytes, linear)
[    0.046900] UDP hash table entries: 512 (order: 1, 8192 bytes, linear)
[    0.046933] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes, linear)
[    0.047567] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.047606] PCI: CLS 0 bytes, default 32
[    0.050672] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.051887] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.051896] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.057344] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.059370] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.060363] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    0.060892] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[    0.061271] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[    0.061307] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    0.061330] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    0.061350] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    0.061369] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    0.061387] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    0.061405] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    0.061418] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    0.061797] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    0.061811] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.061824] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    0.061834] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    0.061844] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    0.061852] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    0.061860] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    0.061925] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400
[    0.062803] PCI: bus0: Fast back to back transfers disabled
[    0.062814] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.062924] PCI: bus1: Fast back to back transfers enabled
[    0.062934] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.062956] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.063442] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.066474] printk: console [ttyS0] disabled
[    0.066770] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[    0.066804] printk: console [ttyS0] enabled
[    0.739055] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xd3
[    0.745470] nand: Samsung NAND 1GiB 3,3V 8-bit
[    0.749935] nand: 1024 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.757682] Scanning device for bad blocks
[    0.908832] Bad eraseblock 1943 at 0x00000f2e0000
[    0.989853] Bad eraseblock 2952 at 0x000017100000
[    1.273687] Bad eraseblock 6642 at 0x000033e40000
[    1.395617] 3 cmdlinepart partitions found on MTD device orion_nand
[    1.401912] Creating 3 MTD partitions on "orion_nand":
[    1.407079] 0x000000000000-0x000000100000 : "U-Boot"
[    1.438803] 0x000000100000-0x000000b00000 : "uImage"
[    1.445104] 0x000000b00000-0x000040000000 : "ubipart"
[    1.466245] hwmon hwmon0: temp1_input not attached to any thermal zone
[    1.475015] hwmon hwmon1: temp1_input not attached to any thermal zone
[    1.482951] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    1.565674] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 02:50:43:13:fd:78
[    1.655634] mv643xx_eth_port mv643xx_eth_port.1 eth1: port 0 with MAC address 02:50:43:40:fd:3c
[    1.664984] rtc-mv f1010300.rtc: registered as rtc0
[    1.669905] rtc-mv f1010300.rtc: setting system clock to 2025-01-24T13:26:23 UTC (1737725183)
[    1.678564] i2c_dev: i2c /dev entries driver
[    1.684654] orion_wdt: Initial timeout 21 sec
[    1.689190] kirkwood-pinctrl f1010000.pin-controller: unsupported function gpio on pin mpp7
[    1.697602] pinctrl core: failed to register map default (1): invalid type given
[    1.713370] marvell-cesa f1030000.crypto: CESA device successfully registered
[    1.721975] NET: Registered PF_INET6 protocol family
[    1.729287] Segment Routing with IPv6
[    1.733030] In-situ OAM (IOAM) with IPv6
[    1.737076] NET: Registered PF_PACKET protocol family
[    1.742174] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.755440] 8021q: 802.1Q VLAN Support v1.8
[    1.794720] ubi0: attaching mtd2
[    2.404619] ubi0: scanning is finished
[    2.449173] ubi0: volume 0 ("rootfs") re-sized from 7315 to 7940 LEBs
[    2.456750] ubi0: attached mtd2 (name "ubipart", size 1013 MiB)
[    2.462710] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[    2.469640] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[    2.476381] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[    2.483201] ubi0: good PEBs: 8101, bad PEBs: 3, corrupted PEBs: 0
[    2.489335] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[    2.496593] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 2101493414
[    2.505774] ubi0: available PEBs: 0, total reserved PEBs: 8101, PEBs reserved for bad PEB handling: 157
[    2.515409] ubi0: background thread "ubi_bgt0d" started, PID 358
[    2.544965] block ubiblock0_0: created from ubi0:0(rootfs)
[    2.550486] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    2.557661] clk: Disabling unused clocks
[    2.585551] UBIFS (ubi0:0): Mounting in unauthenticated mode
[    2.604979] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 362
[    2.815363] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    2.822813] UBIFS (ubi0:0): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    2.832789] UBIFS (ubi0:0): FS size: 1023031296 bytes (975 MiB, 7929 LEBs), max 8191 LEBs, journal size 9033728 bytes (8 MiB, 71 LEBs)
[    2.844942] UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
[    2.850801] UBIFS (ubi0:0): media format: w4/r0 (latest is w5/r0), UUID C178C717-EA12-4947-9CDD-BB2DA50458F5, small LPT model
[    2.862844] VFS: Mounted root (ubifs filesystem) on device 0:12.
[    2.871727] Freeing unused kernel image (initmem) memory: 1024K
[    2.877704] Run /sbin/init as init process
[    2.881818]   with arguments:
[    2.884801]     /sbin/init
[    2.887522]   with environment:
[    2.890669]     HOME=/
[    2.893032]     TERM=linux
[    2.895751]     earlyprintk=serial
[    3.141819] init: Console is alive
[    3.154874] init: - watchdog -
[    3.335124] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    3.400725] orion-ehci f1050000.ehci: EHCI Host Controller
[    3.406306] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    3.414122] orion-ehci f1050000.ehci: irq 34, io mem 0xf1050000
[    3.465057] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    3.485381] hub 1-0:1.0: USB hub found
[    3.494865] hub 1-0:1.0: 1 port detected
[    3.604747] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    3.622725] init: - preinit -
[    3.814581] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    4.036640] hub 1-1:1.0: USB hub found
[    4.064550] hub 1-1:1.0: 7 ports detected
[    4.069509] hub 1-1:1.0: insufficient power available to use all downstream ports
[    5.504552] random: crng init done
Cannot parse config file '/etc/fw_env.config': No such file or directory
Failed to find NVMEM device
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[   10.357902] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   10.476513] mount_root: mounting /dev/root with options
[   10.506500] urandom-seed: Seed file not found (/etc/urandom.seed)
[   10.598943] procd: - early -
[   10.601982] procd: - watchdog -
[   11.227422] procd: - watchdog -
[   11.245998] procd: - ubus -
[   11.308862] procd: - init -
Please press Enter to activate this console.
[   11.773904] urngd: jent-rng init failed, err: 11
[   12.164670] kmodloader: loading kernel modules from /etc/modules.d/*
[   12.482542] PPP generic driver version 2.4.2
[   12.505686] NET: Registered PF_PPPOX protocol family
[   12.535361] kmodloader: done loading kernel modules from /etc/modules.d/*

login[881]: root login on 'ttyS0'


BusyBox v1.36.1 (2024-12-03 11:41:08 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 24.10.0-rc2, r28161-ea17e958b9
 -----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@(none):~# [   24.386648] br-lan: port 1(eth0) entered blocking state
[   24.391918] br-lan: port 1(eth0) entered disabled state
[   24.397237] mv643xx_eth_port mv643xx_eth_port.0 eth0: entered allmulticast mode
[   24.404792] mv643xx_eth_port mv643xx_eth_port.0 eth0: entered promiscuous mode
[   28.037813] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control enabled
[   28.047712] br-lan: port 1(eth0) entered blocking state
[   28.052965] br-lan: port 1(eth0) entered forwarding state

root@OpenWrt:~# [   32.644538] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
dmesg | grep usb
[    0.033014] usbcore: registered new interface driver usbfs
[    0.033073] usbcore: registered new interface driver hub
[    0.033110] usbcore: registered new device driver usb
[    3.814581] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   32.644538] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
root@OpenWrt:~# [   72.074526] usb 1-1.3: new high-speed USB device number 4 using orion-ehci
[   72.366852] usb 1-1.3: rejected 1 configuration due to insufficient available bus power
[   72.374931] usb 1-1.3: no configuration chosen from 1 choice
root@OpenWrt:~# dmesg | grep usb
[    0.033014] usbcore: registered new interface driver usbfs
[    0.033073] usbcore: registered new interface driver hub
[    0.033110] usbcore: registered new device driver usb
[    3.814581] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   32.644538] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[   72.074526] usb 1-1.3: new high-speed USB device number 4 using orion-ehci
[   72.366852] usb 1-1.3: rejected 1 configuration due to insufficient available bus power
[   72.374931] usb 1-1.3: no configuration chosen from 1 choice
root@OpenWrt:~# [  101.214624] usb 1-1.3: USB disconnect, device number 4
[  112.774527] usb 1-1.3: new high-speed USB device number 5 using orion-ehci
[  112.925950] usb 1-1.3: rejected 1 configuration due to insufficient available bus power
[  112.934015] usb 1-1.3: no configuration chosen from 1 choice

root@OpenWrt:~# dmesg | grep usb
[    0.033014] usbcore: registered new interface driver usbfs
[    0.033073] usbcore: registered new interface driver hub
[    0.033110] usbcore: registered new device driver usb
[    3.814581] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   32.644538] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[   72.074526] usb 1-1.3: new high-speed USB device number 4 using orion-ehci
[   72.366852] usb 1-1.3: rejected 1 configuration due to insufficient available bus power
[   72.374931] usb 1-1.3: no configuration chosen from 1 choice
[  101.214624] usb 1-1.3: USB disconnect, device number 4
[  112.774527] usb 1-1.3: new high-speed USB device number 5 using orion-ehci
[  112.925950] usb 1-1.3: rejected 1 configuration due to insufficient available bus power
[  112.934015] usb 1-1.3: no configuration chosen from 1 choice
root@OpenWrt:~# [  125.790623] usb 1-1.3: USB disconnect, device number 5
[  127.070620] usb 1-1.1: USB disconnect, device number 3
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 24, 2025 09:57AM
bodhi,

With PCIe wifi card inserted dmesg output was not changed.

For stock firmware this card viewed by ven dev id.
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 24, 2025 01:10PM
bodhi,

thanks for new dtb, could you share the dts?

I bought wtplug (version without usb/pcie) someday I'll get around to it for OpenWrt and then thin client will return for Debian

there can't be too many ARM devices ;)
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 24, 2025 01:52PM
MM,

I've attached the DTS files kirkwood-promwad.dts.tar to the previous post above.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 24, 2025 01:58PM
Mikele25,

> With PCIe wifi card inserted dmesg output was not
> changed.
>
> For stock firmware this card viewed by ven dev id.

Looks like the Wtplug has 1 PCIe port, but the Thin Client has 2 PCIe ports, not one. So I'll include both in the next DTB version.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 24, 2025 04:08PM
This kirkwood-promwad.dtb.250124_1307.tar contains 4 files.

I've added PCIe1 to kirkwood-promwad-thin-client.dts.

kirkwood-promwad-wtplug.dtb
kirkwood-promwad-wtplug.dts
kirkwood-promwad-thin-client.dtb
kirkwood-promwad-thin-client.dts

It may or may not work for the mPCIe card yet. It depends what type of card and whether we have the driver in the kernel or not.

If the mPCIe card is not enumerated, please find out (open the box and look at the card if factory installed) the model of the card. Or is it something you added later?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Attachments:
open | download - kirkwood-promwad.dtb.250124_1307.tar (40 KB)
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 24, 2025 11:44PM
Michele25,

has kmod-i2c-core been added to the kernel?
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 01:16AM
MM Wrote:
-------------------------------------------------------
> Michele25,
>
> has kmod-i2c-core been added to the kernel?

Sorry, i dont know, i is novice. I just make new image from generic cisco with cmp18 instruction, and add new .dtb for thin client.

Logs with latest kirkwood-promwad-thin-client.dtb:

root@OpenWrt:~# dmesg | grep pci
[    0.061342] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[    0.061378] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    0.061400] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    0.061420] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    0.061439] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    0.061457] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    0.061474] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    0.061488] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    0.061990] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    0.062004] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.062018] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    0.062029] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    0.062039] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    0.062047] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    0.062055] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    0.062120] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400
[    0.062426] pci 0000:00:02.0: [11ab:6282] type 01 class 0x060400
[    0.063243] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.063255] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.063392] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.063526] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    0.063549] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.063564] pci 0000:00:02.0: PCI bridge to [bus 02]


root@OpenWrt:~# lspci
00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6282 (rev 01)
00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6282 (rev 01)



root@OpenWrt:~# dmesg | grep usb
[    0.033080] usbcore: registered new interface driver usbfs
[    0.033140] usbcore: registered new interface driver hub
[    0.033178] usbcore: registered new device driver usb
[    4.014662] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    4.604629] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[    4.784819] usb 1-1.1: rejected 1 configuration due to insufficient available bus power
[    4.792885] usb 1-1.1: no configuration chosen from 1 choice


root@OpenWrt:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux 6.6.63 ehci_hcd EHCI Host Controller
Bus 001 Device 002: ID 0000:0000  
Bus 001 Device 003: ID 13fe:3223          silicon-power

PCIE card is not recognized, but two slots appears.
USB still bugs
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 01:21AM
MM,

Add i2c module, reboot, usb still power error.
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 01:23AM
Mikele25,

> PCIE card is not recognized,

It is quite normal.

Quote

It may or may not work for the mPCIe card yet. It depends what type of card and whether we have the driver in the kernel or not.

If the mPCIe card is not enumerated, please find out (open the box and look at the card if factory installed) the model of the card. Or is it something you added later?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 01:42AM
bohdhi,

Ok, i will post there card data later.

Thanks for your work.
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 03:45AM
Quote
MM
I bought wtplug..

could you tell the model of the device, by which it can be found on the secondary market?
little interest)
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 08:42AM
Mikele25 Wrote:
-------------------------------------------------------
> bohdhi,
>
> Ok, i will post there card data later.
>

MiniPCIE card Intel AC 7260, 8086:08b1
Card is 100% worked (with old HP noutbook), and appears in dmesg by dev:ven on thin client stock firmware (Debian 6).
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 09:39AM
cmp18,

ak-systems ip-plug (cost about $5)

Something tells me we'll be getting ip-plug openwrt build in a few weeks)
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 12:01PM
Mikele25,

> MiniPCIE card Intel AC 7260, 8086:08b1
> Card is 100% worked (with old HP noutbook), and
> appears in dmesg by dev:ven on thin client stock
> firmware (Debian 6).

It will be configured in the next kernel release.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 12:58PM
Mikele25,

The implementation of Intel AC 7260 support is in the kmod-iwlwifi module, let's try it
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 01:46PM
bodhi,

Is it possible to make u-boot 2017 for promwad boxes?

netconsole is very good on my goflexnet, on wtplug access to UART also requires disassembling the entire box
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 01:47PM
MM Wrote:
-------------------------------------------------------
> Mikele25,
>
> The implementation of Intel AC 7260 support is in
> the kmod-iwlwifi module, let's try it

I try it, no success.
If system cant determine device on bus, driver not helped.

bodhi wrote, support will be with new kernel release.
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 07:49PM
MM ,

> Is it possible to make u-boot 2017 for promwad
> boxes?

I think it is possible to have 2025.01 u-boot. But I'm out of time at the moment. I could look into rolling new u-boot in a couple of months (end of March).

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

Your Email:


Subject:


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