Welcome! Log In Create A New Profile

Advanced

Debian on Promwad-Thinclient

Posted by cmp18 
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 25, 2025 11:09PM
bodhi,

>I could look into rolling new u-boot in a couple of months...

Wow! Good news, thanks!
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 26, 2025 09:35PM
Please see this post about release candidate for kernel 6.13.x:

https://forum.doozan.com/read.php?2,12096,138968#msg-138968

I've included the PCIe drivers for Intel AC 7260.

The USB issue is unchanged, still a puzzle. I suspect 3.3V regulator might have something to do with it, i.e. is not enough to drive all 7 ports. But I can't risk changing it to 5V. If one USB port is working, we might need to live with it.

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

WOW, its great!

But i read your instruction for assemble firmware with new kernel.
My skill is not enough fo this.

May be, someone (cmp18, for example:)) make this and upload to cloud?

It s will be interesting, really viewing for worked PCIe WiFi adapter.
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 27, 2025 05:29AM
Mikele25,

Do you need openwrt + kernel 6.13?
or debian at nand + kernel 6.13?
or debian at usb stick + kernel 6.13?

PS I don't think the card will work, since even without drivers it should be visible in lspci (which is what you saw on the stock firmware with kernel 2.39). But you didn't see it in lspci.



Edited 1 time(s). Last edit at 01/27/2025 05:30AM by cmp18.
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 27, 2025 06:36AM
cmp,

Quote
PS I don't think the card will work, since even without drivers it should be visible in lspci (which is what you saw on the stock firmware with kernel 2.39). But you didn't see it in lspci.

Yes, i think as you too. But bodhi sayed, this is normal and new kernel will repaire this card.

If that doesn't really load you up, then I'd like to give it a try openwrt + kernel 6.13.
Even if it doesn't work out, i still will have powerfull openwrt ethernet router:)
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 27, 2025 08:11AM
Mikele25,

>
Quote
PS I don't think the card will work, since
> even without drivers it should be visible in lspci
> (which is what you saw on the stock firmware with
> kernel 2.39). But you didn't see it in lspci.

>
>
>
> Yes, i think as you too. But bodhi sayed, this is
> normal and new kernel will repaire this card.

No, that's not what I said. There are 2 parts. The PCI ports and the card. First, the PCI ports should be shown in dmesg, but the card will not without the drivers. I added pcie1 in the DTS to make sure both ports are enumerated (before there was only pcie0).

A general pcie0 and pcie1 like below might not be enough, if the card is required to be defined on what device and lane it is on.
&pcie0 {
        status = "okay";
};

&pcie1 {
        status = "okay";
};
The first part (pcie ports) must happend (i.e. shown up in dmesg) before anything device plugging in will work at all. Look in dmesg to see the PCIe ports enumeraion.

It is not a sure thing. That's what testing is about.

====

Here is a working example on kernel 6.12.6

# dmesg | grep -iE 'pci|xhci'
[    1.886370] PCI: CLS 0 bytes, default 32
[    3.384439] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[    3.384470] mvebu-pcie mbus@f1000000:pcie@82000000: Parsing ranges property...
[    3.384501] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    3.384536] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    3.384567] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    3.384597] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    3.384626] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    3.384656] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    3.384676] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    3.385298] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    3.385317] pci_bus 0000:00: root bus resource [bus 00-ff]
[    3.385332] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    3.385346] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    3.385358] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    3.385369] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    3.385379] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    3.385389] pci_bus 0000:00: scanning bus
[    3.385490] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400 PCIe Root Port
[    3.385518] pci 0000:00:01.0: PCI bridge to [bus 00]
[    3.385532] pci 0000:00:01.0:   bridge window [io  0x0000-0x0fff]
[    3.385542] pci 0000:00:01.0:   bridge window [mem 0x00000000-0x000fffff]
[    3.396286] pci 0000:00:01.0: vgaarb: pci_notify
[    3.396463] /mbus@f1000000/pcie@82000000/pcie@1,0: Fixed dependency cycle(s) with /mbus@f1000000/pcie@82000000/pcie@1,0/interrupt-controller
[    3.397492] pci_bus 0000:00: fixups for bus
[    3.397507] PCI: bus0: Fast back to back transfers disabled
[    3.397518] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[    3.397528] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    3.397544] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[    3.397694] pci_bus 0000:01: scanning bus
[    3.397749] pci 0000:01:00.0: [1033:0194] type 00 class 0x0c0330 PCIe Endpoint
[    3.397789] pci 0000:01:00.0: BAR 0 [mem 0x90000000-0x90001fff 64bit]
[    3.397961] pci 0000:01:00.0: PME# supported from D0 D3hot
[    3.397976] pci 0000:01:00.0: PME# disabled
[    3.398036] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:01.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
[    3.398360] pci 0000:01:00.0: vgaarb: pci_notify
[    3.415781] pci_bus 0000:01: fixups for bus
[    3.415802] PCI: bus1: Fast back to back transfers disabled
[    3.415813] pci_bus 0000:01: bus scan returning with max=01
[    3.415824] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    3.415844] pci_bus 0000:00: bus scan returning with max=01
[    3.415878] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]: assigned
[    3.415896] pci 0000:01:00.0: BAR 0 [mem 0xe0000000-0xe0001fff 64bit]: assigned
[    3.415920] pci 0000:00:01.0: PCI bridge to [bus 01]
[    3.415934] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe00fffff]
[    3.415954] pci_bus 0000:00: resource 4 [mem 0xf1040000-0xf1041fff]
[    3.415965] pci_bus 0000:00: resource 5 [mem 0xf1044000-0xf1045fff]
[    3.415975] pci_bus 0000:00: resource 6 [mem 0xf1080000-0xf1081fff]
[    3.415985] pci_bus 0000:00: resource 7 [mem 0xe0000000-0xefffffff]
[    3.415995] pci_bus 0000:00: resource 8 [io  0x1000-0xeffff]
[    3.416005] pci_bus 0000:01: resource 1 [mem 0xe0000000-0xe00fffff]
[    3.416097] pcieport 0000:00:01.0: vgaarb: pci_notify
[    3.416127] pcieport 0000:00:01.0: assign IRQ: got 0
[    3.416144] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[    3.416164] pcieport 0000:00:01.0: enabling bus mastering
[    3.416187] pcieport 0000:00:01.0: vgaarb: pci_notify
[    3.416221] pci 0000:00:01.0: enabling bus mastering
[    4.989222] xhci_hcd 0000:01:00.0: vgaarb: pci_notify
[    4.989350] xhci_hcd 0000:01:00.0: assign IRQ: got 33
[    4.989427] xhci_hcd 0000:01:00.0: enabling bus mastering
[    4.989446] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    4.995495] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    5.109411] xhci_hcd 0000:01:00.0: hcc params 0x014042cb hci version 0x96 quirks 0x0000000000000004
[    5.119237] xhci_hcd 0000:01:00.0: enabling Mem-Wr-Inval
[    5.119704] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    5.125850] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[    5.133998] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    5.158308] usb usb2: Product: xHCI Host Controller
[    5.163907] usb usb2: Manufacturer: Linux 6.12.6-kirkwood-tld-1 xhci-hcd
[    5.221370] usb usb3: Product: xHCI Host Controller
[    5.241534] usb usb3: Manufacturer: Linux 6.12.6-kirkwood-tld-1 xhci-hcd
[    5.273394] xhci_hcd 0000:01:00.0: vgaarb: pci_notify
[    5.645947] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd

The 1st line below is the bridge, and the 2nd line is the USB 3.0 controller (builtin, not removable).

# lspci
00:01.0 PCI bridge: Marvell Technology Group Ltd. Device 6282 (rev 01)
01:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 27, 2025 10:13AM
bodhi,

Maybe, i was wrong undestand you. But in my log two PCIe ports was enumerated, and no enumerate for adding card.
IMHO, driver installed AFTER device dev ven ids received by bus.
Othervise how know, which driver needed?
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 27, 2025 02:56PM
Mikele25,

Did you boot this Debian kernel on USB?

https://forum.doozan.com/read.php?2,12096,138968#msg-138968

If you did then, log in and please post

dmesg
lspci

If there is no Wifi adapter shown, try
modprobe iwlwifi
modprobe iwlmvm

=====

If you want to boot OpenWrt, then you need to rebuild OpenWrt with these kernel configs (or make sure that these are already in its config):

CONFIG_IWLWIFI=m
CONFIG_IWLMVM=m

These are relevant driver code:

./drivers/net/wireless/intel/iwlwifi/iwlwifi.c
./drivers/net/wireless/intel/iwlwifi/cfg/7000.c

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



Edited 2 time(s). Last edit at 01/27/2025 04:56PM by bodhi.
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 27, 2025 11:32PM
bodhi,

Thanks.
I will try this solution.
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 30, 2025 01:21AM
bodhi,

I was reading instruction about new debian kernel.

Sorry for dummy questions, i'm taking the first steps.

WHERE are producing this building? On thin client? Or on Linux PC?

HOW all maked things put to USB flash?
May be, there is links for instruction about?
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 30, 2025 02:24PM
Mikele25,

See the Wiki thread for instruction how to install USB rootfs and boot with serial console:

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

Quote

Kirkwood plugs

Boot Kirkwood rootfs with stock u-boot

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

Thank you very much. I went to study:)
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 31, 2025 12:38AM
cmp18,

May be, you help to me.

I got another Thin client Depo Sky A60. Stock Debian 6. And it doesn't output anything to the console.
I cant find any good manual for administration of this device.

You wrote that you have the same situation.

How did you manage to turn on the console? Do you know the default root or user password?

And how write this console enabling to uboot environment?
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 31, 2025 09:36AM
Mikele25,

first,
is the u-boot banner displayed on the console when power on? or console always silent?


Link to the topic with admin manual in the first post of the my openwrt topic.
according to it:
root / nosoup4u
user / secret


PS if necessary, I can build a debian 12 with bodhi kernel 6.13 for flashing in internal nand. It will use ~300M, 700M will be free



Edited 1 time(s). Last edit at 01/31/2025 09:45AM by cmp18.
forserg
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 31, 2025 11:21AM
cmp18,
Can yoy shared him on cloud storage?
then I thank you
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 31, 2025 01:29PM
bodhi,

LED's GPIO different in two sections of kirkwood-promwad-wtplug.dts:

pmx_leds: pmx-leds {
				marvell,pins = "mpp38", "mpp39";
				marvell,function = "gpio";
			};

and

gpio-leds {
		compatible = "gpio-leds";
		pinctrl-0 = <&pmx_leds>;
		pinctrl-names = "default";

		led-red {
			label = "wtplug:red:stat";
			gpios = <&gpio1 6 GPIO_ACTIVE_HIGH>;
		};

		led-green {
			label = "wtplug:green:stat";
			gpios = <&gpio1 7 GPIO_ACTIVE_HIGH>;
                        linux,default-trigger = "default-on";
		};

        };

it must be 38 an 39 in both cases?
(gt thread)



Edited 1 time(s). Last edit at 01/31/2025 01:33PM by MM.
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 31, 2025 01:43PM
MM,

> LED's GPIO different in two sections of
> kirkwood-promwad-wtplug.dts:
> it must be 38 an 39 in both cases?

Yes, my bad! that was a cut/paste error. I'll correct it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 31, 2025 11:34PM
bodhi,

>I could look into rolling new u-boot in a couple of months...

Will 1M partition be enough for the new u-boot 2025?



Edited 1 time(s). Last edit at 01/31/2025 11:49PM by MM.
Re: Promwad-ThinClient - can't boot 6.11 kernel
January 31, 2025 11:48PM
MM,

> 1M partition ll be enouth for new 2025 u-boot?

1MB is more than enough for a Kirkwood u-boot. I expect this 2025 u-boot image is about 512k or less.

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

> MM,
>
> > LED's GPIO different in two sections of
> > kirkwood-promwad-wtplug.dts:
> > it must be 38 an 39 in both cases?
>
> Yes, my bad! that was a cut/paste error. I'll
> correct it.

Actually those were correct :) I did not read it closely and thought you calculated it correctly.

They are both 38 and 39 in both cases already.

marvell,pins = "mpp38", "mpp39";

			gpios = <&gpio1 6 GPIO_ACTIVE_HIGH>;   /* bank 1 is bit 32, so this is 38 */
			gpios = <&gpio1 7 GPIO_ACTIVE_HIGH>;   /* bank 1 is bit 32, so this is 39 */

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 01, 2025 01:53AM
bodhi

> Yes, my bad!

Sorry, it's mine)
I used wrong DTB (thin client for ip-plug) and got red blinking LED:)

> They are both 38 and 39 in both cases already.

I didn’t pay attention that this is the second bank
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 01:46AM
cmp18,

Thank you.

I was wrong with firmware version, this box was stock DEPO firmware.
And console always silent.

After opening the case, i find broken holder of tablet battery.
The battery itself was rolling freely inside.)

I was soldering holder and insert new battery, but console stiil nothing.

Well, at least the power supply will remain.)
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 02:00AM
cmp18,

Quote
PS if necessary, I can build a debian 12 with bodhi kernel 6.13 for flashing in internal nand. It will use ~300M, 700M will be free

That would be interesting.
Work in GUI with stock Debian6 was wery slow (most likely because of SIS Volari), and generally unnecessary for this box.
Really his tasks is a network services.

But if the problem is with USB and PCIe cards will be fixed, this will be the best solution, then OpenWRT.
And more flexible.
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 02:56AM
Mikele25 Wrote:
-------------------------------------------------------
> cmp18,
>
> Thank you.
>
> I was wrong with firmware version, this box was
> stock DEPO firmware.
> And console always silent.
>
> After opening the case, i find broken holder of
> tablet battery.
> The battery itself was rolling freely inside.)
>
> I was soldering holder and insert new battery, but
> console stiil nothing.
>
> Well, at least the power supply will remain.)


if you don't even see the uboot banner (the console doesn't display any characters) - this is a problem with the serial converter chip, I've already seen this a couple of times on some thin clients. you just need to power on and power off the thin client very many times (with an interval of 5 seconds) + also plug and unplug the serial adapter from the client and computer with this action. then, once every 20 times, the console comes to life, and you can flash it :)
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 03:00AM
Mikele25 Wrote:
-------------------------------------------------------
>
> That would be interesting.
> Work in GUI with stock Debian6 was wery slow (most
> likely because of SIS Volari), and generally
> unnecessary for this box.
> Really his tasks is a network services.
>
> But if the problem is with USB and PCIe cards will
> be fixed, this will be the best solution, then
> OpenWRT.
> And more flexible.

okay, when I get back home (a little less than a week), I'll upload deb12 for nand to the cloud. Now, I've added the latest dtb from bodhi to the openwrt builds. maybe it will be useful and some pci cards will work)
Mikele25
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 04:34AM
cmp18,

Thanks for your with serial console.
I'll definitely try it.

Quote
okay, when I get back home (a little less than a week), I'll upload deb12 for nand to the cloud. Now, I've added the latest dtb from bodhi to the openwrt builds. maybe it will be useful and some pci cards will work)

Very thanks to you. Waiting for this cool thing.)
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 02:35PM
cmp18,

Quote
bodhi
If you want to boot OpenWrt, then you need to rebuild OpenWrt with these kernel configs (or make sure that these are already in its config):

CONFIG_IWLWIFI=m
CONFIG_IWLMVM=m

Does OpenWrt already have the above configs?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
MM
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 02:48PM
bodhi,

6.13.0 kernel pci probe with realtek 8191 wifi card


root@debian:~# dmesg | grep -iE 'pci|xhci'
[    2.500094] PCI: CLS 0 bytes, default 32
[    4.024622] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[    4.034550] mvebu-pcie mbus@f1000000:pcie@82000000: Parsing ranges property...
[    4.034592] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[    4.044777] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[    4.054971] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[    4.065154] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    4.075858] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[    4.086565] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    4.097300] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[    4.108885] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    4.117312] pci_bus 0000:00: root bus resource [bus 00-ff]
[    4.123592] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[    4.134553] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[    4.145505] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[    4.156453] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    4.164092] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    4.171096] pci_bus 0000:00: scanning bus
[    4.171202] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400 PCIe Root Port
[    4.179297] pci 0000:00:01.0: PCI bridge to [bus 00]
[    4.185072] pci 0000:00:01.0:   bridge window [io  0x0000-0x0fff]
[    4.191902] pci 0000:00:01.0:   bridge window [mem 0x00000000-0x000fffff]
[    4.199806] pci 0000:00:01.0: vgaarb: pci_notify
[    4.199978] /mbus@f1000000/pcie@82000000/pcie@1,0: Fixed dependency cycle(s) with /mbus@f1000000/pcie@82000000/pcie@1,0/interrupt-controller
[    4.213468] pci 0000:00:02.0: [11ab:6282] type 01 class 0x060400 PCIe Root Port
[    4.221536] pci 0000:00:02.0: PCI bridge to [bus 00]
[    4.227254] pci 0000:00:02.0:   bridge window [io  0x0000-0x0fff]
[    4.234098] pci 0000:00:02.0:   bridge window [mem 0x00000000-0x000fffff]
[    4.241915] pci 0000:00:02.0: vgaarb: pci_notify
[    4.242154] /mbus@f1000000/pcie@82000000/pcie@2,0: Fixed dependency cycle(s) with /mbus@f1000000/pcie@82000000/pcie@2,0/interrupt-controller
[    4.256281] pci_bus 0000:00: fixups for bus
[    4.256305] PCI: bus0: Fast back to back transfers disabled
[    4.262614] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[    4.262630] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    4.271405] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 0
[    4.271422] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    4.280199] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[    4.280364] pci_bus 0000:01: scanning bus
[    4.280413] pci_bus 0000:01: fixups for bus
[    4.280424] PCI: bus1: Fast back to back transfers enabled
[    4.286659] pci_bus 0000:01: bus scan returning with max=01
[    4.286675] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    4.294055] pci 0000:00:02.0: scanning [bus 00-00] behind bridge, pass 1
[    4.294208] pci_bus 0000:02: scanning bus
[    4.294257] pci_bus 0000:02: fixups for bus
[    4.294268] PCI: bus2: Fast back to back transfers enabled
[    4.300482] pci_bus 0000:02: bus scan returning with max=02
[    4.300495] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    4.307870] pci_bus 0000:00: bus scan returning with max=02
[    4.307901] pci 0000:00:01.0: PCI bridge to [bus 01]
[    4.313626] pci 0000:00:02.0: PCI bridge to [bus 02]
[    4.319325] pci_bus 0000:00: resource 4 [mem 0xf1040000-0xf1041fff]
[    4.326346] pci_bus 0000:00: resource 5 [mem 0xf1044000-0xf1045fff]
[    4.333367] pci_bus 0000:00: resource 6 [mem 0xf1080000-0xf1081fff]
[    4.340367] pci_bus 0000:00: resource 7 [mem 0xe0000000-0xefffffff]
[    4.347385] pci_bus 0000:00: resource 8 [io  0x1000-0xeffff]
[    4.353829] pci 0000:00:01.0: skipping OF node: interrupt-controller
[    4.353899] pcieport 0000:00:01.0: vgaarb: pci_notify
[    4.353933] pcieport 0000:00:01.0: assign IRQ: got 0
[    4.353965] pcieport 0000:00:01.0: enabling bus mastering
[    4.353997] pcieport 0000:00:01.0: vgaarb: pci_notify
[    4.354035] pci 0000:00:02.0: skipping OF node: interrupt-controller
[    4.354087] pcieport 0000:00:02.0: vgaarb: pci_notify
[    4.354117] pcieport 0000:00:02.0: assign IRQ: got 0
[    4.354142] pcieport 0000:00:02.0: enabling bus mastering
[    4.354170] pcieport 0000:00:02.0: vgaarb: pci_notify
root@debian:~#
root@debian:~#
root@debian:~# 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@debian:~#

Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 03:26PM
MM,

> 6.13.0 kernel pci probe with realtek 8191 wifi
> card

Is this a plain 8191, or is there any s/u/c/e suffix in the model name?

For now, try

modprobe rtl8192ce

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Promwad-ThinClient - can't boot 6.11 kernel
February 03, 2025 03:28PM
cmp18,

Please change the Subject of the 1st post in this thread to "Debian on Promwad Thin Client".

Thanks!

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