[oS-EN] Can't see the WiFi on new laptop
Hi, on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it. tlp-stat says there is no WiFi: Laicolasse:~ # tlp-stat --rfkill --- TLP 1.4.0 -------------------------------------------- +++ Wireless bluetooth = on wifi = none (no device) wwan = on hci0(btusb) : bluetooth, not connected Laicolasse:~ # Laicolasse:~ # hwinfo --wlan Laicolasse:~ #
Laicolasse:~ # inxi --bluetooth -n -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 100 Mbps duplex: full mac: f4:a8:0d:7a:49:01 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb Report: bt-adapter ID: hci0 state: up address: 60:E9:AA:A0:1A:4A Laicolasse:~ #
I don't see it on the journal: <https://paste.opensuse.org/pastes/ccc804e35e3c> The laptop is customized, and in the papers it clearly says WiFi is included: Wireless - RZ616 Wi-Fi 6E 11AX (2x2) & Bluetooth 5.1 Ethernet - Ethernet con cable Laicolasse:~ # lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 30c9:0050 Luxvisions Innotech Limited Integrated RGB Camera Bus 003 Device 003: ID 058f:9540 Alcor Micro Corp. AU9540 Smartcard Reader Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00f9 Synaptics, Inc. Bus 001 Device 002: ID 0489:e0d8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Laicolasse:~ # --verbose Bus 001 Device 002: ID 0489:e0d8 Foxconn / Hon Hai Wireless_Device Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 239 Miscellaneous Device bDeviceSubClass 2 bDeviceProtocol 1 Interface Association bMaxPacketSize0 64 idVendor 0x0489 Foxconn / Hon Hai idProduct 0xe0d8 bcdDevice 1.00 iManufacturer 5 MediaTek Inc. iProduct 6 Wireless_Device iSerial 7 000000000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x00fe bNumInterfaces 3 bConfigurationValue 1 iConfiguration 8 Config_01 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Association: bLength 8 bDescriptorType 11 bFirstInterface 0 bInterfaceCount 3 bFunctionClass 224 Wireless bFunctionSubClass 1 Radio Frequency bFunctionProtocol 1 Bluetooth iFunction 4 BT_FUNCTION Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 1 BT_ACL_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 2 BT_SCO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 2 BT_SCO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 2 BT_SCO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0011 1x 17 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0011 1x 17 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 2 BT_SCO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0019 1x 25 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0019 1x 25 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 2 BT_SCO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0021 1x 33 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0021 1x 33 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 5 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 2 BT_SCO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0031 1x 49 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0031 1x 49 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 6 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 2 BT_SCO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x003f 1x 63 bytes bInterval 4 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x003f 1x 63 bytes bInterval 4 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 3 BT_ISO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x8a EP 10 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x0a EP 10 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 3 BT_ISO_If Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x8a EP 10 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x0a EP 10 OUT bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 1 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x000c bNumDeviceCaps 1 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x00000000 (Missing must-be-set LPM bit!) Device Status: 0x0001 Self Powered What's next? Was the WiFi not included? Some command to reveal it? inxi seems to see it. lsusb seems to confirm. The Lenovo L15 can be obtained with Ubuntu, but not the L14 (15/14 are the inches). -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On Tue, 28 Mar 2023 20:36:22 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
What's next? Was the WiFi not included? Some command to reveal it? inxi seems to see it. lsusb seems to confirm.
err, inxi sees what, a bluetooth device? why would lsusb see a pci device? what system are you running? Specifically what kernel and do you know for sure that it supports the device?
The Lenovo L15 can be obtained with Ubuntu, but not the L14 (15/14 are the inches).
On 2023-03-28 21:17, Dave Howorth wrote:
On Tue, 28 Mar 2023 20:36:22 +0200 "Carlos E. R." <> wrote:
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
What's next? Was the WiFi not included? Some command to reveal it? inxi seems to see it. lsusb seems to confirm.
err, inxi sees what, a bluetooth device?
I think it is the same card. The new protocols can link with BT, then change over to WiFi for the actual transfer of large data. This means same chip or card. It is in the detailed invoice: Wireless - RZ616 Wi-Fi 6E 11AX (2x2) & Bluetooth 5.1
why would lsusb see a pci device?
I have no idea.
what system are you running? Specifically what kernel and do you know for sure that it supports the device?
openSUSE Leap 15.4 with current kernel, which you can see in the journal output I posted: Mar 28 20:10:30 Laicolasse kernel: Linux version 5.14.21-150400.24.46-default (geeko@buildhost) (gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binutils; SUSE Linux Enterprise 15) 2.39.0.20220810-150100.7.40) #1 SMP PREEMPT_DYNAMIC Thu Feb 9 08:38:18 UTC 2023 (2d95137) Mar 28 20:10:30 Laicolasse kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150400.24.46-default root=UUID=858cc569-e2ae-4d12-adf6-3a06ade8281c splash=silent resume=/dev/disk/by-label/Swap preempt=full mitigations=auto quiet security=apparmor Laicolasse:~ # uname -a Linux Laicolasse 5.14.21-150400.24.46-default #1 SMP PREEMPT_DYNAMIC Thu Feb 9 08:38:18 UTC 2023 (2d95137) x86_64 x86_64 x86_64 GNU/Linux Laicolasse:~ # I have no idea about what kernel supports it, or if any kernel supports it at all. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On Tue, 28 Mar 2023 21:27:54 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2023-03-28 21:17, Dave Howorth wrote:
On Tue, 28 Mar 2023 20:36:22 +0200 "Carlos E. R." <> wrote:
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
What's next? Was the WiFi not included? Some command to reveal it? inxi seems to see it. lsusb seems to confirm.
err, inxi sees what, a bluetooth device?
I think it is the same card. The new protocols can link with BT, then change over to WiFi for the actual transfer of large data. This means same chip or card.
Err device-1 is the BT. I think device -2 is the wifi & says it is a MEDIATEK MT7922
It is in the detailed invoice:
Wireless - RZ616 Wi-Fi 6E 11AX (2x2) & Bluetooth 5.1
What the invoice says is not relevant. What the hardware reports is.
why would lsusb see a pci device?
I have no idea.
OK. I'll give you a clue. It wouldn't.
what system are you running? Specifically what kernel and do you know for sure that it supports the device?
openSUSE Leap 15.4 with current kernel, which you can see in the journal output I posted:
Mar 28 20:10:30 Laicolasse kernel: Linux version 5.14.21-150400.24.46-default (geeko@buildhost) (gcc (SUSE Linux) [snip] I have no idea about what kernel supports it, or if any kernel supports it at all.
I believe 5.17 is the first kernel to support it. Caution - I am not a hardware and especially not a wifi expert.
On 2023-03-28 21:47, Dave Howorth wrote:
On Tue, 28 Mar 2023 21:27:54 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2023-03-28 21:17, Dave Howorth wrote:
On Tue, 28 Mar 2023 20:36:22 +0200 "Carlos E. R." <> wrote:
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
What's next? Was the WiFi not included? Some command to reveal it? inxi seems to see it. lsusb seems to confirm.
err, inxi sees what, a bluetooth device?
I think it is the same card. The new protocols can link with BT, then change over to WiFi for the actual transfer of large data. This means same chip or card.
Err device-1 is the BT. I think device -2 is the wifi & says it is a MEDIATEK MT7922
It is in the detailed invoice:
Wireless - RZ616 Wi-Fi 6E 11AX (2x2) & Bluetooth 5.1
What the invoice says is not relevant. What the hardware reports is.
why would lsusb see a pci device?
I have no idea.
OK. I'll give you a clue. It wouldn't.
I mean have no idea where the WiFi card is. I used lsusb because somewhere I saw a mention of radio in the usb. Now that you mention pci, I'll try:
Laicolasse:~ # lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:02.6 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 01:00.0 Non-Volatile memory controller: KIOXIA Corporation Device 000c
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0e)
04:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)
06:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barcelo (rev d1) 07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller 07:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor 07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 07:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 07:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor (rev 01) 07:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller Laicolasse:~ #
what system are you running? Specifically what kernel and do you know for sure that it supports the device?
openSUSE Leap 15.4 with current kernel, which you can see in the journal output I posted:
Mar 28 20:10:30 Laicolasse kernel: Linux version 5.14.21-150400.24.46-default (geeko@buildhost) (gcc (SUSE Linux) [snip] I have no idea about what kernel supports it, or if any kernel supports it at all.
I believe 5.17 is the first kernel to support it.
How do you know? :-? Ok, where do I obtain it?
Caution - I am not a hardware and especially not a wifi expert.
-- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On Tue, 28 Mar 2023 21:58:02 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
I believe 5.17 is the first kernel to support it.
How do you know? :-?
Because I'm awake and I can google?
Ok, where do I obtain it?
I have no idea. I would assume that when you buy a new laptop you check what hardware is in it*, and that the hardware is supported by linux and what version you need. I don't use laptops so I don't know. * and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
On 2023-03-28 22:38, Dave Howorth wrote:
On Tue, 28 Mar 2023 21:58:02 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
I believe 5.17 is the first kernel to support it.
How do you know? :-?
Because I'm awake and I can google?
I wouldn't know what phrase to google for. I tried some strings, found nothing relevant.
Ok, where do I obtain it?
I have no idea. I would assume that when you buy a new laptop you check what hardware is in it*, and that the hardware is supported by linux and what version you need. I don't use laptops so I don't know.
Well, the brand does install Ubuntu in a variant of this model (bigger screen). I did ask if i could install Linux, they said yes. There is no real better choice of laptop for me.
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On 2023-03-28 22:44, Carlos E. R. wrote:
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
Mar 28 20:10:30 Laicolasse kernel: pci 0000:06:00.0: [14c3:0616] type 00 class 0x028000 In your paste.opensuse you have wifi on pci 06:0.0 with 14c3:0616 https://linux-hardware.org/?view=search&vendorid=14c3&deviceid=0616&typeid=net%2Fwireless#list -- /bengan
On 2023-03-28 22:54, Bengt Gördén wrote:
On 2023-03-28 22:44, Carlos E. R. wrote:
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
Mar 28 20:10:30 Laicolasse kernel: pci 0000:06:00.0: [14c3:0616] type 00 class 0x028000
In your paste.opensuse you have wifi on pci 06:0.0 with 14c3:0616
https://linux-hardware.org/?view=search&vendorid=14c3&deviceid=0616&typeid=net%2Fwireless#list
Thanks, but I don't know how to interpret that. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On 2023-03-28 22:58, Carlos E. R. wrote:
On 2023-03-28 22:54, Bengt Gördén wrote:
On 2023-03-28 22:44, Carlos E. R. wrote:
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
Mar 28 20:10:30 Laicolasse kernel: pci 0000:06:00.0: [14c3:0616] type 00 class 0x028000
In your paste.opensuse you have wifi on pci 06:0.0 with 14c3:0616
https://linux-hardware.org/?view=search&vendorid=14c3&deviceid=0616&typeid=net%2Fwireless#list
Thanks, but I don't know how to interpret that.
If you click on someone in the list, you will see which probes have found that particular hw. You can sort so you can check some other distros and what kernel they have. But I think it's like Dave said, kernel 5.14 doesn't have that hw. I can't see Opensuse Leap 15.4 anywhere in the listings. You will probably need to install a newer kernel. Maybe go for the HEAD. https://doc.opensuse.org/documentation/leap/reference/html/book-reference/ch... -- /bengan
On 2023-03-28 23:11, Bengt Gördén wrote:
On 2023-03-28 22:58, Carlos E. R. wrote:
On 2023-03-28 22:54, Bengt Gördén wrote:
On 2023-03-28 22:44, Carlos E. R. wrote:
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
Mar 28 20:10:30 Laicolasse kernel: pci 0000:06:00.0: [14c3:0616] type 00 class 0x028000
In your paste.opensuse you have wifi on pci 06:0.0 with 14c3:0616
https://linux-hardware.org/?view=search&vendorid=14c3&deviceid=0616&typeid=net%2Fwireless#list
Thanks, but I don't know how to interpret that.
If you click on someone in the list, you will see which probes have found that particular hw. You can sort so you can check some other distros and what kernel they have. But I think it's like Dave said, kernel 5.14 doesn't have that hw. I can't see Opensuse Leap 15.4 anywhere in the listings. You will probably need to install a newer kernel.
Maybe go for the HEAD. https://doc.opensuse.org/documentation/leap/reference/html/book-reference/ch...
Ok, tomorrow. Enough for today, long day. I recall that Andrei Borzenkov said once that Kernel:HEAD is built against factory so intended for TW. For Leap better use Kernel:HEAD:Backport. But I have no idea what directory to use, there are a lot of them. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On Tue, 2023-03-28 at 23:31 +0200, Carlos E. R. wrote:
On 2023-03-28 23:11, Bengt Gördén wrote:
On 2023-03-28 22:58, Carlos E. R. wrote:
On 2023-03-28 22:54, Bengt Gördén wrote:
On 2023-03-28 22:44, Carlos E. R. wrote:
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
Mar 28 20:10:30 Laicolasse kernel: pci 0000:06:00.0: [14c3:0616] type 00 class 0x028000
In your paste.opensuse you have wifi on pci 06:0.0 with 14c3:0616
https://linux-hardware.org/?view=search&vendorid=14c3&deviceid=0616&typeid=net%2Fwireless#list
Thanks, but I don't know how to interpret that.
If you click on someone in the list, you will see which probes have found that particular hw. You can sort so you can check some other distros and what kernel they have. But I think it's like Dave said, kernel 5.14 doesn't have that hw. I can't see Opensuse Leap 15.4 anywhere in the listings. You will probably need to install a newer kernel.
Maybe go for the HEAD. https://doc.opensuse.org/documentation/leap/reference/html/book-reference/ch...
Ok, tomorrow. Enough for today, long day.
I recall that Andrei Borzenkov said once that Kernel:HEAD is built against factory so intended for TW. For Leap better use Kernel:HEAD:Backport.
But I have no idea what directory to use, there are a lot of them.
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
I've never used Leap on baremetal myself, but I had no issues using Kernel:stable:Backport on a kvm machine. I just added the repo and ran `sudo zypper up --details --allow-vendor-change` and it installed the kernel[-default] and firmware for the lp154 release. scott@opensuse154:~> cat /etc/os-release ; uname -r NAME="openSUSE Leap" VERSION="15.4" ID="opensuse-leap" ID_LIKE="suse opensuse" VERSION_ID="15.4" PRETTY_NAME="openSUSE Leap 15.4" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:leap:15.4" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" DOCUMENTATION_URL="https://en.opensuse.org/Portal:Leap" LOGO="distributor-logo-Leap" 6.2.8-lp154.2.g221c28f-default scott@opensuse154:~> cat Downloads/Kernel\:stable\:Backport.repo [Kernel_stable_Backport] name=Kernel builds for branch stable (standard) type=rpm-md baseurl=https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard... gpgcheck=1 gpgkey=https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard... enabled=1 It does appear that the 0616 ID doesn't show up as a "pci_device_id" until 5.17 - so I'd assume that's why you can't make use of it - the kernel doesn't associate the h/w with that driver; I downloaded a few kernel releases and don't see 0616 in drivers/net/wireless/mediatek/mt76/mt7921/pci.c until >= 5.17 ... I have a similar scenario w/ a USB WiFi 6 device that needs to use the 8852au driver for a RealTek chip. -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2023-03-28 at 22:07 -0000, Scott Bradnick via openSUSE Users wrote:
On Tue, 2023-03-28 at 23:31 +0200, Carlos E. R. wrote:
On 2023-03-28 23:11, Bengt Gördén wrote:
On 2023-03-28 22:58, Carlos E. R. wrote:
On 2023-03-28 22:54, Bengt Gördén wrote:
On 2023-03-28 22:44, Carlos E. R. wrote:
...
I've never used Leap on baremetal myself, but I had no issues using Kernel:stable:Backport on a kvm machine. I just added the repo and ran `sudo zypper up --details --allow-vendor-change` and it installed the kernel[-default] and firmware for the lp154 release.
...
scott@opensuse154:~> cat Downloads/Kernel\:stable\:Backport.repo
... Thank you for the detailed information, will try tomorrow. I'm too tired now, long day. Just having a last look at email.
It does appear that the 0616 ID doesn't show up as a "pci_device_id" until 5.17 - so I'd assume that's why you can't make use of it - the kernel doesn't associate the h/w with that driver; I downloaded a few kernel releases and don't see 0616 in drivers/net/wireless/mediatek/mt76/mt7921/pci.c until >= 5.17 ... I have a similar scenario w/ a USB WiFi 6 device that needs to use the 8852au driver for a RealTek chip.
I see. Tomorrow I have to investigate another issue: can't hibernate or sleep machine from command or menu. It returns instantly, no error logged. However, it seems to sleep peacefully if I close the lid (as long as I don't connect the Ethernet cable). - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZCOYIBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVHg4AnjH//gadjRvJ7KHIru56 ZaJxo1+lAJ9bLK6/zS++XUdEl7ZVyU0v8mce+A== =q58x -----END PGP SIGNATURE-----
Carlos E. R. wrote:
On 2023-03-28 23:11, Bengt Gördén wrote:
Maybe go for the HEAD.
https://doc.opensuse.org/documentation/leap/reference/html/book-reference/ch...
Ok, tomorrow. Enough for today, long day.
I recall that Andrei Borzenkov said once that Kernel:HEAD is built against factory so intended for TW. For Leap better use Kernel:HEAD:Backport.
But I have no idea what directory to use, there are a lot of them.
It doesn't really matter - a kernel is relatively "stand alone", you can switch between them as you please. Install one, try it out, see if it works. -- Per Jessen, Zürich (7.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Hi Carlos, I am running kernel 6.2.8 from this repo https://download.opensuse.org/repositories/home:/T4597421/15.4/ Regards, Francesco On Tue, Mar 28, 2023 at 11:31 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2023-03-28 23:11, Bengt Gördén wrote:
On 2023-03-28 22:58, Carlos E. R. wrote:
On 2023-03-28 22:54, Bengt Gördén wrote:
On 2023-03-28 22:44, Carlos E. R. wrote:
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
Mar 28 20:10:30 Laicolasse kernel: pci 0000:06:00.0: [14c3:0616] type 00 class 0x028000
In your paste.opensuse you have wifi on pci 06:0.0 with 14c3:0616
https://linux-hardware.org/?view=search&vendorid=14c3&deviceid=0616&typeid=net%2Fwireless#list
Thanks, but I don't know how to interpret that.
If you click on someone in the list, you will see which probes have found that particular hw. You can sort so you can check some other distros and what kernel they have. But I think it's like Dave said, kernel 5.14 doesn't have that hw. I can't see Opensuse Leap 15.4 anywhere in the listings. You will probably need to install a newer kernel.
Maybe go for the HEAD. https://doc.opensuse.org/documentation/leap/reference/html/book-reference/ch...
Ok, tomorrow. Enough for today, long day.
I recall that Andrei Borzenkov said once that Kernel:HEAD is built against factory so intended for TW. For Leap better use Kernel:HEAD:Backport.
But I have no idea what directory to use, there are a lot of them.
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
Am Dienstag, 28. März 2023, 22:58:48 CEST schrieb Carlos E. R.:
On 2023-03-28 22:54, Bengt Gördén wrote:
On 2023-03-28 22:44, Carlos E. R. wrote:
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
Mar 28 20:10:30 Laicolasse kernel: pci 0000:06:00.0: [14c3:0616] type 00 class 0x028000
In your paste.opensuse you have wifi on pci 06:0.0 with 14c3:0616
https://linux-hardware.org/?view=search&vendorid=14c3&deviceid=0616&typeid=net%2Fwireless#list
Thanks, but I don't know how to interpret that.
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
On Wed, 29 Mar 2023 07:12:21 +0200 Stephan Hemeier <Sauerlandlinux@gmx.de> wrote:
Am Dienstag, 28. März 2023, 22:58:48 CEST schrieb Carlos E. R.:
On 2023-03-28 22:54, Bengt Gördén wrote:
On 2023-03-28 22:44, Carlos E. R. wrote:
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
Mar 28 20:10:30 Laicolasse kernel: pci 0000:06:00.0: [14c3:0616] type 00 class 0x028000
In your paste.opensuse you have wifi on pci 06:0.0 with 14c3:0616
https://linux-hardware.org/?view=search&vendorid=14c3&deviceid=0616&typeid=net%2Fwireless#list
Thanks, but I don't know how to interpret that.
-- Cheers / Saludos,
Carlos E. R.
(from Elesar, using openSUSE Leap 15.4)
That says the same as we've already established, I think: lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD
Dave Howorth wrote:
On Wed, 29 Mar 2023 07:12:21 +0200 Stephan Hemeier <Sauerlandlinux@gmx.de> wrote:
That says the same as we've already established, I think:
lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD
Above is says 5.12-5.19 ? Looking at kernel 5.14.21 (config.gz) as installed on a 15.4 system, the module is enabled. pjessen@office212:/home/pjessen> zgrep MT79 /proc/config.gz CONFIG_MT7915E=m CONFIG_MT7921E=m The needed module is in kernel-default-extra, so maybe try installing that, Carlos. -- Per Jessen, Zürich (15.3°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-29 14:20, Per Jessen wrote:
Dave Howorth wrote:
On Wed, 29 Mar 2023 07:12:21 +0200 Stephan Hemeier <Sauerlandlinux@gmx.de> wrote:
That says the same as we've already established, I think:
lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD
Above is says 5.12-5.19 ? Looking at kernel 5.14.21 (config.gz) as installed on a 15.4 system, the module is enabled.
pjessen@office212:/home/pjessen> zgrep MT79 /proc/config.gz CONFIG_MT7915E=m CONFIG_MT7921E=m
The needed module is in kernel-default-extra, so maybe try installing that, Carlos.
Ok, that can be done quickly. [...] It was installed already. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-03-29 14:20, Per Jessen wrote:
pjessen@office212:/home/pjessen> zgrep MT79 /proc/config.gz CONFIG_MT7915E=m CONFIG_MT7921E=m
The needed module is in kernel-default-extra, so maybe try installing that, Carlos.
Ok, that can be done quickly. [...] It was installed already.
Okay, it wasn't on my test system. what happened when you loaded the module? -- Per Jessen, Zürich (15.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-29 14:43, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-29 14:20, Per Jessen wrote:
pjessen@office212:/home/pjessen> zgrep MT79 /proc/config.gz CONFIG_MT7915E=m CONFIG_MT7921E=m
The needed module is in kernel-default-extra, so maybe try installing that, Carlos.
Ok, that can be done quickly. [...] It was installed already.
Okay, it wasn't on my test system.
what happened when you loaded the module?
Huh, I may need another tea. Load what and how? The only waiting idea I have is download and install newer kernel.
Laicolasse:~ # inxi -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A Laicolasse:~ # lsmod | grep -i mt7922 Laicolasse:~ # modprobe mt7922 modprobe: FATAL: Module mt7922 not found in directory /lib/modules/5.14.21-150400.24.46-default Laicolasse:~ # locate mt7922 Laicolasse:~ #
Must have another name. Ah. I have mt7922, not 21. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-03-29 14:43, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-29 14:20, Per Jessen wrote:
pjessen@office212:/home/pjessen> zgrep MT79 /proc/config.gz CONFIG_MT7915E=m CONFIG_MT7921E=m
The needed module is in kernel-default-extra, so maybe try installing that, Carlos.
Ok, that can be done quickly. [...] It was installed already.
Okay, it wasn't on my test system.
what happened when you loaded the module?
Huh, I may need another tea. Load what and how?
Carlos, you're sounding like a newbie - which you're certainly not. Load what - the module. "mt7921e" Load how - the usual way people load modules, with "modprobe"
The only waiting idea I have is download and install newer kernel.
You've been jumping to conclusion based on minimal evidence. It looks like "mt7921e" might solve your problem, IF it supports your mt7922 hardware. I did not check that it does - "modinfo mt7921e" will tell you which PCI identifiers it supports, and you can match those against your lspci output.
Ah. I have mt7922, not 21.
Yes, but they seem to be minor variations of each other. However, when mt7921e was not loaded automatically, something does appear to be missing. What happened when you loaded mt7921e ? -- Per Jessen, Zürich (17.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-29 15:11, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-29 14:43, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-29 14:20, Per Jessen wrote:
pjessen@office212:/home/pjessen> zgrep MT79 /proc/config.gz CONFIG_MT7915E=m CONFIG_MT7921E=m
The needed module is in kernel-default-extra, so maybe try installing that, Carlos.
Ok, that can be done quickly. [...] It was installed already.
Okay, it wasn't on my test system.
what happened when you loaded the module?
Huh, I may need another tea. Load what and how?
Carlos, you're sounding like a newbie - which you're certainly not.
I am a newbie in things about WiFi.
Load what - the module. "mt7921e" Load how - the usual way people load modules, with "modprobe"
Ok, but who has told me to load that module? I have mt7922, not 21. I couldn't guess to load an older module.
The only waiting idea I have is download and install newer kernel.
You've been jumping to conclusion based on minimal evidence.
It looks like "mt7921e" might solve your problem, IF it supports your mt7922 hardware. I did not check that it does - "modinfo mt7921e" will tell you which PCI identifiers it supports, and you can match those against your lspci output.
Ah. I have mt7922, not 21.
Yes, but they seem to be minor variations of each other. However, when mt7921e was not loaded automatically, something does appear to be missing.
What happened when you loaded mt7921e ?
Nothing.
Laicolasse:~ # modprobe --verbose mt7921e insmod /lib/modules/5.14.21-150400.24.46-default/kernel/net/wireless/cfg80211.ko.zst insmod /lib/modules/5.14.21-150400.24.46-default/kernel/lib/crypto/libarc4.ko.zst insmod /lib/modules/5.14.21-150400.24.46-default/kernel/net/mac80211/mac80211.ko.zst insmod /lib/modules/5.14.21-150400.24.46-default/kernel/drivers/net/wireless/mediatek/mt76/mt76.ko.zst insmod /lib/modules/5.14.21-150400.24.46-default/kernel/drivers/net/wireless/mediatek/mt76/mt76-connac-lib.ko.zst insmod /lib/modules/5.14.21-150400.24.46-default/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko.zst Laicolasse:~ # inxi -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A Laicolasse:~ #
Laicolasse:~ # hwinfo --netcard 07: PCI 300.0: 0200 Ethernet controller [Created at pci.386] Unique ID: rBUF.Osz2B5WC6KD Parent ID: aYFK.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.3/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x50ae Revision: 0x0e Driver: "r8169" Driver Modules: "r8169" Device File: eth0 I/O Ports: 0x2000-0x2fff (rw) Memory Range: 0xfd604000-0xfd604fff (rw,non-prefetchable) Memory Range: 0xfd600000-0xfd603fff (rw,non-prefetchable) IRQ: 41 (no events) HW Address: f4:a8:0d:7a:49:01 Permanent HW Address: f4:a8:0d:7a:49:01 Link detected: yes Module Alias: "pci:v000010ECd00008168sv000017AAsd000050AEbc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (PCI bridge)
27: PCI 600.0: 0280 Network controller [Created at pci.386] Unique ID: vTuk.elCpZcgOa6E Parent ID: AXjq.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.6/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0xe0c6 Memory Range: 0xe0200000-0xe02fffff (ro,non-prefetchable,disabled) Memory Range: 0xfd400000-0xfd407fff (rw,non-prefetchable,disabled) IRQ: 255 (no events) Module Alias: "pci:v000014C3d00000616sv000017AAsd0000E0C6bc02sc80i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #28 (PCI bridge) Laicolasse:~ #
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-03-29 15:51, Andrei Borzenkov wrote:
On Wed, Mar 29, 2023 at 4:48 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
Ok, but who has told me to load that module? I have mt7922, not 21. I couldn't guess to load an older module.
Yes, you could. But as usual, you demand fish, not information how to catch it.
No, I couldn't. I thought it would eat my kittens. I can read generic howtos, but I suck at finding the correct one. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 3/29/23 10:04 AM, Carlos E. R. wrote:
On 2023-03-29 15:51, Andrei Borzenkov wrote:
On Wed, Mar 29, 2023 at 4:48 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
Ok, but who has told me to load that module? I have mt7922, not 21. I couldn't guess to load an older module.
Yes, you could. But as usual, you demand fish, not information how to catch it.
No, I couldn't. I thought it would eat my kittens.
I can read generic howtos, but I suck at finding the correct one.
It's been a very long time since I messed with modules. And I never enjoyed running insmod or modprobe and then-- probably-- having to run rmmod... and that was back when there were four or maybe six modules to deal with. Now we have # lsmod|wc -l 177 Insane!
Carlos E. R. wrote:
On 2023-03-29 15:11, Per Jessen wrote:
Carlos E. R. wrote:
Huh, I may need another tea. Load what and how?
Carlos, you're sounding like a newbie - which you're certainly not.
I am a newbie in things about WiFi.
There is zero in this thread that is wifi specific. It is all about a non-functioning device and why the module doesn't work or isn't being loaded.
Load what - the module. "mt7921e" Load how - the usual way people load modules, with "modprobe"
Ok, but who has told me to load that module? I have mt7922, not 21. I couldn't guess to load an older module.
Actually, if you had read what a number of people have posted, that is the suggestion. I think both Stephan and David posted material listing "mt7921e" as the module to support your hardware.
What happened when you loaded mt7921e ?
Nothing.
Okay, sorry, I should have said "please post dmesg output after loading mt7921e". There will most likely be some output from that module, maybe complaining about something. Maybe the firmware didn't load. You could also post output of "ip addr" to show us if a wifi device has turned up. -- Per Jessen, Zürich (17.0°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-29 16:06, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-29 15:11, Per Jessen wrote:
Carlos E. R. wrote:
Huh, I may need another tea. Load what and how?
Carlos, you're sounding like a newbie - which you're certainly not.
I am a newbie in things about WiFi.
There is zero in this thread that is wifi specific. It is all about a non-functioning device and why the module doesn't work or isn't being loaded.
Load what - the module. "mt7921e" Load how - the usual way people load modules, with "modprobe"
Ok, but who has told me to load that module? I have mt7922, not 21. I couldn't guess to load an older module.
Actually, if you had read what a number of people have posted, that is the suggestion. I think both Stephan and David posted material listing "mt7921e" as the module to support your hardware.
I did read *all* the links that have been posted in this thread. I did not notice that I should have tried loading module "mt7921e", I was looking for "mt7922". If it was said, sorry, I missed it.
What happened when you loaded mt7921e ?
Nothing.
Okay, sorry, I should have said "please post dmesg output after loading mt7921e". There will most likely be some output from that module, maybe complaining about something. Maybe the firmware didn't load. You could also post output of "ip addr" to show us if a wifi device has turned up.
Per, I did not post dmesg output because I looked and there was *none*. Please give me some slack. Posting it now: (starts with messages about waking up from sleep. The detected USB is the Synaptics touchpad)
[16805.711074] amdgpu 0000:07:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 [16805.711075] amdgpu 0000:07:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 [16805.711076] amdgpu 0000:07:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 [16805.786815] OOM killer enabled. [16805.786819] Restarting tasks ... [16805.788091] usb 1-4: USB disconnect, device number 12 [16805.789934] done. [16805.798787] PM: suspend exit [16805.839062] Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC) [16805.918984] usb 1-4: new full-speed USB device number 13 using xhci_hcd [16805.964795] r8169 0000:03:00.0 eth0: Link is Down [16806.087259] usb 1-4: New USB device found, idVendor=06cb, idProduct=00f9, bcdDevice= 0.00 [16806.087271] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=1 [16806.087274] usb 1-4: SerialNumber: ed75c0d74110 [16808.849238] r8169 0000:03:00.0 eth0: Link is Up - 1Gbps/Full - flow control off [16808.849270] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [16854.045190] cfg80211: Loading compiled-in X.509 certificates for regulatory database [16854.045329] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Laicolasse:~ #
Ok, "ip addr" shows something else besides the address, did not think of that. Did think of ifconfig, but it is not installed. Trying now. [...] Nope. Just eth0 and lo. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
What happened when you loaded mt7921e ?
Nothing.
Okay, sorry, I should have said "please post dmesg output after loading mt7921e". There will most likely be some output from that module, maybe complaining about something. Maybe the firmware didn't load. You could also post output of "ip addr" to show us if a wifi device has turned up.
Per, I did not post dmesg output because I looked and there was *none*. Please give me some slack.
Well, it's difficult to keep track of what you know and what you don't know. Above you didn't know what and how to load a module, I felt it would have been silly to assume you knew how to look for the output.
cfg80211: Loading compiled-in X.509 certificates for regulatory database cfg80211: Loaded X.509 cert 'sforshee: [00b28ddf47aef9cea7'
Those are the only ones that pertain to the loading of that module. (well, to cfg80211 which was automatically pulled in).
Ok, "ip addr" shows something else besides the address, did not think of that. Did think of ifconfig, but it is not installed.
ifconfig was deprecated years ago, it was later moved into a separate package.
Trying now. [...] Nope. Just eth0 and lo.
Right. My gut feeling says "firmware issue", but there is nothing to confirm that. Do you have "kernel-firmware-mediatek" installed ? -- Per Jessen, Zürich (19.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-29 17:02, Per Jessen wrote:
Carlos E. R. wrote:
What happened when you loaded mt7921e ?
Nothing.
Okay, sorry, I should have said "please post dmesg output after loading mt7921e". There will most likely be some output from that module, maybe complaining about something. Maybe the firmware didn't load. You could also post output of "ip addr" to show us if a wifi device has turned up.
Per, I did not post dmesg output because I looked and there was *none*. Please give me some slack.
Well, it's difficult to keep track of what you know and what you don't know. Above you didn't know what and how to load a module, I felt it would have been silly to assume you knew how to look for the output.
I know how to manually load a module, just that nobody had said what module to try, as I have mt7922 hardware, not 7921. Thus I asked what module? And I still don't know how to automatically load that module by the wifi tools.
cfg80211: Loading compiled-in X.509 certificates for regulatory database cfg80211: Loaded X.509 cert 'sforshee: [00b28ddf47aef9cea7'
Those are the only ones that pertain to the loading of that module. (well, to cfg80211 which was automatically pulled in).
That message comes from cfg80211.ko.zst, not the mt7921e, which said nothing.
Ok, "ip addr" shows something else besides the address, did not think of that. Did think of ifconfig, but it is not installed.
ifconfig was deprecated years ago, it was later moved into a separate package.
Still, it is what I use preferably.
Trying now. [...] Nope. Just eth0 and lo.
Right. My gut feeling says "firmware issue", but there is nothing to confirm that. Do you have "kernel-firmware-mediatek" installed ?
Yes. I posted the contents of the directory yesterday:
]> Laicolasse:/lib/firmware/mediatek # ls -lh | grep "BT_RAM_CODE_MT7922_1_1_hdr.bin\|WIFI_MT7922_patch_mcu_1_1_hdr.bin\|WIFI_RAM_CODE_MT7922_1.bin" ]> -rw-r--r-- 1 root root 486K Oct 31 07:18 BT_RAM_CODE_MT7922_1_1_hdr.bin.xz ]> -rw-r--r-- 1 root root 135K Oct 31 07:18 WIFI_MT7922_patch_mcu_1_1_hdr.bin.xz ]> -rw-r--r-- 1 root root 747K Oct 31 07:18 WIFI_RAM_CODE_MT7922_1.bin.xz ]> Laicolasse:/lib/firmware/mediatek # -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
I posted the contents of the directory yesterday:
]> Laicolasse:/lib/firmware/mediatek # ls -lh | grep "BT_RAM_CODE_MT7922_1_1_hdr.bin\|WIFI_MT7922_patch_mcu_1_1_hdr.bin\|WIFI_RAM_C ODE_MT7922_1.bin" ]> -rw-r--r-- 1 root root 486K Oct 31 07:18 BT_RAM_CODE_MT7922_1_1_hdr.bin.xz ]> -rw-r--r-- 1 root root 135K Oct 31 07:18 WIFI_MT7922_patch_mcu_1_1_hdr.bin.xz ]> -rw-r--r-- 1 root root 747K Oct 31 07:18 WIFI_RAM_CODE_MT7922_1.bin.xz ]> Laicolasse:/lib/firmware/mediatek #
If the pci id of your device isn't a part of a specific kernel's mt7921e module it's VERY unlikely it'd 'just work' in any capacity, at least not w/o some other type of coaxing. I feel pretty confident in saying you _have to_ have >= kernel 5.17 to have the device show up; using kernel:stable:Backport should be an easy, quick method to give a try. The important part here, for you, is "616" which is referenced by 6.2.8-lp154: opensuse154:~ # modinfo mt7921e | grep pci\: alias: pci:v000014C3d00000616sv*sd*bc*sc*i* alias: pci:v000014C3d00000608sv*sd*bc*sc*i* alias: pci:v000014C3d00007922sv*sd*bc*sc*i* alias: pci:v000014C3d00007961sv*sd*bc*sc*i* opensuse154:~ # uname -a Linux opensuse154 6.2.8-lp154.2.g221c28f-default #1 SMP PREEMPT_DYNAMIC Wed Mar 22 18:56:06 UTC 2023 (221c28f) x86_64 x86_64 x86_64 GNU/Linux But missing from 5.14.21-150400: opensuse154:~ # modinfo mt7921e | grep pci\: alias: pci:v000014C3d00007961sv*sd*bc*sc*i* opensuse154:~ # uname -a Linux opensuse154 5.14.21-150400.24.46-default #1 SMP PREEMPT_DYNAMIC Thu Feb 9 08:38:18 UTC 2023 (2d95137) x86_64 x86_64 x86_64 GNU/Linux -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Beelink SER6 Pro [AMD Rembrandt [Radeon 680M]] (x86_64) |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- IceWhale ZimaBoard 832 [Intel HD Graphics 500] (x86_64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote:
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
I posted the contents of the directory yesterday:
]> Laicolasse:/lib/firmware/mediatek # ls -lh | grep "BT_RAM_CODE_MT7922_1_1_hdr.bin\|WIFI_MT7922_patch_mcu_1_1_hdr.bin\|WIFI_RAM_C ODE_MT7922_1.bin" ]> -rw-r--r-- 1 root root 486K Oct 31 07:18 BT_RAM_CODE_MT7922_1_1_hdr.bin.xz ]> -rw-r--r-- 1 root root 135K Oct 31 07:18 WIFI_MT7922_patch_mcu_1_1_hdr.bin.xz ]> -rw-r--r-- 1 root root 747K Oct 31 07:18 WIFI_RAM_CODE_MT7922_1.bin.xz ]> Laicolasse:/lib/firmware/mediatek #
If the pci id of your device isn't a part of a specific kernel's mt7921e module it's VERY unlikely it'd 'just work' in any capacity, at least not w/o some other type of coaxing.
Ok, so that is the meaning of "pci id" that I did not understand.
I feel pretty confident in saying you _have to_ have >= kernel 5.17 to have the device show up; using kernel:stable:Backport should be an easy, quick method to give a try.
Yes, I am going to try that now. I had other things to do first.
The important part here, for you, is "616" which is referenced by 6.2.8-lp154:
opensuse154:~ # modinfo mt7921e | grep pci\: alias: pci:v000014C3d00000616sv*sd*bc*sc*i* alias: pci:v000014C3d00000608sv*sd*bc*sc*i* alias: pci:v000014C3d00007922sv*sd*bc*sc*i* alias: pci:v000014C3d00007961sv*sd*bc*sc*i*
Sorry, I do not understand what means that "616". Laicolasse:~ # lspci | grep 616 Laicolasse:~ # Ah: Laicolasse:~ # lspci -nn | grep 616 06:00.0 Network controller [0280]: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616] Laicolasse:~ #
opensuse154:~ # uname -a Linux opensuse154 6.2.8-lp154.2.g221c28f-default #1 SMP PREEMPT_DYNAMIC Wed Mar 22 18:56:06 UTC 2023 (221c28f) x86_64 x86_64 x86_64 GNU/Linux
But missing from 5.14.21-150400:
opensuse154:~ # modinfo mt7921e | grep pci\: alias: pci:v000014C3d00007961sv*sd*bc*sc*i*
opensuse154:~ # uname -a Linux opensuse154 5.14.21-150400.24.46-default #1 SMP PREEMPT_DYNAMIC Thu Feb 9 08:38:18 UTC 2023 (2d95137) x86_64 x86_64 x86_64 GNU/Linux
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-03-29 21:57, Carlos E. R. wrote:
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote:
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
I feel pretty confident in saying you _have to_ have >= kernel 5.17 to have the device show up; using kernel:stable:Backport should be an easy, quick method to give a try.
Yes, I am going to try that now. I had other things to do first.
Laicolasse:~ # zypper ar --refresh -k -f -n "Kernel:stable:Backports" "https://download.opensuse.org/repositories/Kernel:/stable:/Backport/standard..." "Kernel_stable_Backports" Only kernel available is 6.2.8. I tick that. I don't know if I have to update any other package, but YaST doesn't bring any other dependency or recommend. Laicolasse:~ # rpm -qa | grep kernel kernel-firmware-media-20220509-150400.4.13.1.noarch kernel-firmware-ath10k-20220509-150400.4.13.1.noarch kernel-firmware-nvidia-20220509-150400.4.13.1.noarch kernel-firmware-chelsio-20220509-150400.4.13.1.noarch kernel-default-6.2.8-lp154.3.1.gc9a94ac.x86_64 kernel-firmware-realtek-20220509-150400.4.13.1.noarch kernel-firmware-marvell-20220509-150400.4.13.1.noarch kernel-default-optional-5.14.21-150400.24.46.1.x86_64 kernel-firmware-amdgpu-20220509-150400.4.13.1.noarch kernel-firmware-nfp-20220509-150400.4.13.1.noarch kernel-firmware-prestera-20220509-150400.4.13.1.noarch kernel-firmware-brcm-20220509-150400.4.13.1.noarch kernel-default-5.14.21-150400.24.46.1.x86_64 kernel-firmware-radeon-20220509-150400.4.13.1.noarch kernel-firmware-i915-20220509-150400.4.13.1.noarch kernel-firmware-sound-20220509-150400.4.13.1.noarch kernel-firmware-liquidio-20220509-150400.4.13.1.noarch kernel-firmware-usb-network-20220509-150400.4.13.1.noarch kernel-firmware-mediatek-20220509-150400.4.13.1.noarch kernel-default-extra-5.14.21-150400.24.46.1.x86_64 kernel-firmware-network-20220509-150400.4.13.1.noarch kernel-firmware-ath11k-20220509-150400.4.13.1.noarch kernel-firmware-platform-20220509-150400.4.13.1.noarch kernel-firmware-bnx2-20220509-150400.4.13.1.noarch kernel-firmware-qlogic-20220509-150400.4.13.1.noarch kernel-firmware-dpaa2-20220509-150400.4.13.1.noarch kernel-firmware-serial-20220509-150400.4.13.1.noarch kernel-firmware-iwlwifi-20220509-150400.4.13.1.noarch kernel-firmware-all-20220509-150400.4.13.1.noarch kernel-firmware-ueagle-20220509-150400.4.13.1.noarch kernel-firmware-mwifiex-20220509-150400.4.13.1.noarch purge-kernels-service-0-150200.8.6.1.noarch kernel-firmware-bluetooth-20220509-150400.4.13.1.noarch kernel-firmware-qcom-20220509-150400.4.13.1.noarch kernel-firmware-intel-20220509-150400.4.13.1.noarch kernel-firmware-ti-20220509-150400.4.13.1.noarch kernel-firmware-mellanox-20220509-150400.4.13.1.noarch kernel-firmware-atheros-20220509-150400.4.13.1.noarch [1]+ Done yast2 sw_single Laicolasse:~ # I'm sure I should update the firmware package, too. And kernel-default-extra. Any thing else? perhaps all the above? They are not "multiversion", they are one or the other. Huh, there is no "kernel-default-extra" in that repo. This is very confusing. Oh, now yast demands to update several other packages. 60, in fact. kernel-firmware-all kernel-firmware-amdgpu kernel-firmware-ath10k kernel-firmware-ath11k kernel-firmware-atheros kernel-firmware-bluetooth kernel-firmware-bnx2 kernel-firmware-brcm kernel-firmware-chelsio kernel-firmware-dpaa2 kernel-firmware-i915 kernel-firmware-intel kernel-firmware-iwlwifi kernel-firmware-liquidio kernel-firmware-marvell kernel-firmware-media kernel-firmware-mediatek kernel-firmware-mellanox kernel-firmware-mwifiex kernel-firmware-network kernel-firmware-nfp kernel-firmware-nvidia kernel-firmware-platform kernel-firmware-prestera kernel-firmware-qcom kernel-firmware-qlogic kernel-firmware-radeon kernel-firmware-realtek kernel-firmware-serial kernel-firmware-sound kernel-firmware-ti kernel-firmware-ueagle kernel-firmware-usb-network Laicolasse:~ # rpm -qa | grep kernel kernel-firmware-radeon-20230320-lp154.2.1.noarch kernel-firmware-brcm-20230320-lp154.2.1.noarch kernel-firmware-nfp-20230320-lp154.2.1.noarch kernel-default-6.2.8-lp154.3.1.gc9a94ac.x86_64 kernel-firmware-amdgpu-20230320-lp154.2.1.noarch kernel-firmware-bnx2-20230320-lp154.2.1.noarch kernel-default-optional-5.14.21-150400.24.46.1.x86_64 kernel-firmware-network-20230320-lp154.2.1.noarch kernel-firmware-usb-network-20230320-lp154.2.1.noarch kernel-firmware-all-20230320-lp154.2.1.noarch kernel-firmware-liquidio-20230320-lp154.2.1.noarch kernel-firmware-mwifiex-20230320-lp154.2.1.noarch kernel-firmware-ath10k-20230320-lp154.2.1.noarch kernel-default-5.14.21-150400.24.46.1.x86_64 kernel-firmware-media-20230320-lp154.2.1.noarch kernel-firmware-ueagle-20230320-lp154.2.1.noarch kernel-firmware-serial-20230320-lp154.2.1.noarch kernel-firmware-iwlwifi-20230320-lp154.2.1.noarch kernel-default-extra-5.14.21-150400.24.46.1.x86_64 kernel-firmware-qlogic-20230320-lp154.2.1.noarch kernel-firmware-dpaa2-20230320-lp154.2.1.noarch kernel-firmware-marvell-20230320-lp154.2.1.noarch kernel-firmware-ti-20230320-lp154.2.1.noarch kernel-firmware-realtek-20230320-lp154.2.1.noarch kernel-firmware-intel-20230320-lp154.2.1.noarch kernel-firmware-qcom-20230320-lp154.2.1.noarch kernel-firmware-chelsio-20230320-lp154.2.1.noarch kernel-firmware-nvidia-20230320-lp154.2.1.noarch kernel-firmware-bluetooth-20230320-lp154.2.1.noarch kernel-firmware-i915-20230320-lp154.2.1.noarch kernel-firmware-prestera-20230320-lp154.2.1.noarch purge-kernels-service-0-150200.8.6.1.noarch kernel-firmware-atheros-20230320-lp154.2.1.noarch kernel-firmware-mellanox-20230320-lp154.2.1.noarch kernel-firmware-platform-20230320-lp154.2.1.noarch kernel-firmware-ath11k-20230320-lp154.2.1.noarch kernel-firmware-mediatek-20230320-lp154.2.1.noarch kernel-firmware-sound-20230320-lp154.2.1.noarch Laicolasse:~ # Well, it booted. No screech noises. The kittens are silent. And...:
Laicolasse:~ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether f4:a8:0d:7a:49:01 brd ff:ff:ff:ff:ff:ff altname enp3s0f0 inet 192.168.2.17/16 brd 192.168.255.255 scope global dynamic noprefixroute eth0 valid_lft 43148sec preferred_lft 43148sec inet6 fe80::f6a8:dff:fe7a:4901/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether ee:19:17:ef:15:3d brd ff:ff:ff:ff:ff:ff permaddr 60:e9:aa:a0:1a:49 altname wlp6s0 Laicolasse:~ #
Whoa! :-))
Laicolasse:~ # ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether f4:a8:0d:7a:49:01 brd ff:ff:ff:ff:ff:ff altname enp3s0f0 inet 192.168.2.17/16 brd 192.168.255.255 scope global dynamic noprefixroute eth0 valid_lft 42622sec preferred_lft 42622sec inet6 fe80::f6a8:dff:fe7a:4901/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 60:e9:aa:a0:1a:49 brd ff:ff:ff:ff:ff:ff altname wlp6s0 inet 192.168.2.18/16 brd 192.168.255.255 scope global dynamic noprefixroute wlan0 valid_lft 43170sec preferred_lft 43170sec inet6 fe80::167c:b416:5e91:9d9e/64 scope link noprefixroute valid_lft forever preferred_lft forever Laicolasse:~ #
cer@Telcontar:~> ssh -X root@192.168.2.18 The authenticity of host '192.168.2.18 (192.168.2.18)' can't be established. ECDSA key fingerprint is SHA256:NIhuSB76yyS2tZrKYDHMOeoYWLjGsFKXFaFYjgJ+MO0. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '192.168.2.18' (ECDSA) to the list of known hosts. Password: Last login: Wed Mar 29 22:21:46 2023 from 192.168.1.14 Have a lot of fun... dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.InvalidArgs: Invalid environment assignments Laicolasse:~ # Laicolasse:~ # Laicolasse:~ # Laicolasse:~ #
I don't believe my eyes. I'm still expecting to look back and find my kittens are dead. :-D This easy? Suspend works. Hibernate doesn't, same as before. Sound works. I am amazed. No cons? Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-? -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-03-29 22:38, Carlos E. R. wrote:
On 2023-03-29 21:57, Carlos E. R. wrote:
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote:
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-30-23 16:40]:
On 2023-03-29 22:38, Carlos E. R. wrote:
On 2023-03-29 21:57, Carlos E. R. wrote:
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote:
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit)
??? you list everything BUT the subject ITEM ??? that's real planning. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-03-30 23:06, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [03-30-23 16:40]:
On 2023-03-29 22:38, Carlos E. R. wrote:
On 2023-03-29 21:57, Carlos E. R. wrote:
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote:
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit)
??? you list everything BUT the subject ITEM ???
that's real planning.
Sorry, I don't understand. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-30-23 20:17]:
On 2023-03-30 23:06, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [03-30-23 16:40]:
On 2023-03-29 22:38, Carlos E. R. wrote:
On 2023-03-29 21:57, Carlos E. R. wrote:
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote:
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit)
??? you list everything BUT the subject ITEM ???
that's real planning.
Sorry, I don't understand.
what is causing the problem, what wifi card? should be main interest aside the operating system and platform. what card? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-03-31 02:24, Patrick Shanahan wrote:
* Carlos E. R. <> [03-30-23 20:17]:
On 2023-03-30 23:06, Patrick Shanahan wrote:
* Carlos E. R. <> [03-30-23 16:40]:
On 2023-03-29 22:38, Carlos E. R. wrote:
On 2023-03-29 21:57, Carlos E. R. wrote:
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote: > On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit)
??? you list everything BUT the subject ITEM ???
that's real planning.
Sorry, I don't understand.
what is causing the problem, what wifi card? should be main interest aside the operating system and platform. what card?
Well, it is in the output of several commands which I included: inxi Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A lspci 06:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter hwinfo Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo" If you ask about a photo of the actual hardware, I have not seen it, and I am not going to risk opening the laptop. And if I have missed some other information, they can ask. I can not think of everything, but I am not hiding anything either. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-30-23 20:33]:
On 2023-03-31 02:24, Patrick Shanahan wrote:
* Carlos E. R. <> [03-30-23 20:17]:
On 2023-03-30 23:06, Patrick Shanahan wrote:
* Carlos E. R. <> [03-30-23 16:40]:
On 2023-03-29 22:38, Carlos E. R. wrote:
On 2023-03-29 21:57, Carlos E. R. wrote: > On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote: > > On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit)
??? you list everything BUT the subject ITEM ???
that's real planning.
Sorry, I don't understand.
what is causing the problem, what wifi card? should be main interest aside the operating system and platform. what card?
Well, it is in the output of several commands which I included:
inxi Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A
lspci
06:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
hwinfo
Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo"
If you ask about a photo of the actual hardware, I have not seen it, and I am not going to risk opening the laptop.
And if I have missed some other information, they can ask. I can not think of everything, but I am not hiding anything either.
no, I am saying that it should be the SUBJECT of your bug report. it is of primary concern and will help others who search to identify the bug report. your concern is about that particular card and it should be of primary interest and easily identifiable. you fail to provide that information. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-03-31 04:23, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [03-30-23 20:33]:
On 2023-03-31 02:24, Patrick Shanahan wrote:
* Carlos E. R. <> [03-30-23 20:17]:
On 2023-03-30 23:06, Patrick Shanahan wrote:
* Carlos E. R. <> [03-30-23 16:40]:
On 2023-03-29 22:38, Carlos E. R. wrote: > On 2023-03-29 21:57, Carlos E. R. wrote: >> On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote: >>> On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
> Ok, should I report this in Bugzilla, perhaps the kernel devs can > consider backporting support for this laptop? It is an enterprise > laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit)
??? you list everything BUT the subject ITEM ???
that's real planning.
Sorry, I don't understand.
what is causing the problem, what wifi card? should be main interest aside the operating system and platform. what card?
Well, it is in the output of several commands which I included:
inxi Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A
lspci
06:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
hwinfo
Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo"
If you ask about a photo of the actual hardware, I have not seen it, and I am not going to risk opening the laptop.
And if I have missed some other information, they can ask. I can not think of everything, but I am not hiding anything either.
no, I am saying that it should be the SUBJECT of your bug report. it is of primary concern and will help others who search to identify the bug report. your concern is about that particular card and it should be of primary interest and easily identifiable. you fail to provide that information.
I disagree. The important thing is the laptop model. The wifi hardware is which comes with that laptop model, clients don't have a choice. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Fri, 31 Mar 2023 09:23:59 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2023-03-31 04:23, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [03-30-23 20:33]:
On 2023-03-31 02:24, Patrick Shanahan wrote:
* Carlos E. R. <> [03-30-23 20:17]:
On 2023-03-30 23:06, Patrick Shanahan wrote:
* Carlos E. R. <> [03-30-23 16:40]: > On 2023-03-29 22:38, Carlos E. R. wrote: >> On 2023-03-29 21:57, Carlos E. R. wrote: >>> On 2023-03-29 21:11, Scott Bradnick via openSUSE Users >>> wrote: >>>> On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote: > > ... > >> Ok, should I report this in Bugzilla, perhaps the kernel devs >> can consider backporting support for this laptop? It is an >> enterprise laptop, after all. :-? > > > Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. > (edit)
??? you list everything BUT the subject ITEM ???
that's real planning.
Sorry, I don't understand.
what is causing the problem, what wifi card? should be main interest aside the operating system and platform. what card?
Well, it is in the output of several commands which I included:
inxi Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A
lspci
06:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
hwinfo
Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo"
If you ask about a photo of the actual hardware, I have not seen it, and I am not going to risk opening the laptop.
And if I have missed some other information, they can ask. I can not think of everything, but I am not hiding anything either.
no, I am saying that it should be the SUBJECT of your bug report. it is of primary concern and will help others who search to identify the bug report. your concern is about that particular card and it should be of primary interest and easily identifiable. you fail to provide that information.
I disagree. The important thing is the laptop model. The wifi hardware is which comes with that laptop model, clients don't have a choice.
I agree with Patrick here. It's the wifi hardware that is causing the problem, so that is most important. Yes, it's fitted in that laptop but it might be fitted in others as well. So the wifi part number should be in the subject.
Dave Howorth wrote:
On Fri, 31 Mar 2023 09:23:59 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
no, I am saying that it should be the SUBJECT of your bug report. it is of primary concern and will help others who search to identify the bug report. your concern is about that particular card and it should be of primary interest and easily identifiable. you fail to provide that information.
I disagree. The important thing is the laptop model. The wifi hardware is which comes with that laptop model, clients don't have a choice.
I agree with Patrick here. It's the wifi hardware that is causing the problem, so that is most important. Yes, it's fitted in that laptop but it might be fitted in others as well. So the wifi part number should be in the subject.
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware. -- Per Jessen, Zürich (17.7°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-31 14:05, Per Jessen wrote:
Dave Howorth wrote:
On Fri, 31 Mar 2023 09:23:59 +0200 "Carlos E. R." <> wrote:
no, I am saying that it should be the SUBJECT of your bug report. it is of primary concern and will help others who search to identify the bug report. your concern is about that particular card and it should be of primary interest and easily identifiable. you fail to provide that information.
I disagree. The important thing is the laptop model. The wifi hardware is which comes with that laptop model, clients don't have a choice.
I agree with Patrick here. It's the wifi hardware that is causing the problem, so that is most important. Yes, it's fitted in that laptop but it might be fitted in others as well. So the wifi part number should be in the subject.
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [03-31-23 12:42]:
On 2023-03-31 14:05, Per Jessen wrote:
Dave Howorth wrote:
On Fri, 31 Mar 2023 09:23:59 +0200 "Carlos E. R." <> wrote:
no, I am saying that it should be the SUBJECT of your bug report. it is of primary concern and will help others who search to identify the bug report. your concern is about that particular card and it should be of primary interest and easily identifiable. you fail to provide that information.
I disagree. The important thing is the laptop model. The wifi hardware is which comes with that laptop model, clients don't have a choice.
I agree with Patrick here. It's the wifi hardware that is causing the problem, so that is most important. Yes, it's fitted in that laptop but it might be fitted in others as well. So the wifi part number should be in the subject.
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
YOU can edit the subject line of your bug (and should). -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-03-31 20:33, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [03-31-23 12:42]:
On 2023-03-31 14:05, Per Jessen wrote:
Dave Howorth wrote:
On Fri, 31 Mar 2023 09:23:59 +0200 "Carlos E. R." <> wrote:
no, I am saying that it should be the SUBJECT of your bug report. it is of primary concern and will help others who search to identify the bug report. your concern is about that particular card and it should be of primary interest and easily identifiable. you fail to provide that information.
I disagree. The important thing is the laptop model. The wifi hardware is which comes with that laptop model, clients don't have a choice.
I agree with Patrick here. It's the wifi hardware that is causing the problem, so that is most important. Yes, it's fitted in that laptop but it might be fitted in others as well. So the wifi part number should be in the subject.
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
YOU can edit the subject line of your bug (and should).
PLEASE! Will you have some patience!? :-/ -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-03-31 14:05, Per Jessen wrote:
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
I see you added "Mediatek", which in my opinion is only of minimal more use than the laptop model. My brainwaves tell me to write "MT7922" - maybe something like "wifi interface not supported, driver does not work for MT7922". -- Per Jessen, Zürich (11.9°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-04-01 09:58, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-31 14:05, Per Jessen wrote:
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
I see you added "Mediatek", which in my opinion is only of minimal more use than the laptop model. My brainwaves tell me to write "MT7922" - maybe something like "wifi interface not supported, driver does not work for MT7922".
Ok... next time. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [04-01-23 06:37]:
On 2023-04-01 09:58, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-31 14:05, Per Jessen wrote:
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
I see you added "Mediatek", which in my opinion is only of minimal more use than the laptop model. My brainwaves tell me to write "MT7922" - maybe something like "wifi interface not supported, driver does not work for MT7922".
Ok... next time.
so the information for "this time" will not be easily found. why not just "do it right", finally. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-04-01 16:04, Patrick Shanahan wrote:
* Carlos E. R. <> [04-01-23 06:37]:
On 2023-04-01 09:58, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-31 14:05, Per Jessen wrote:
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
I see you added "Mediatek", which in my opinion is only of minimal more use than the laptop model. My brainwaves tell me to write "MT7922" - maybe something like "wifi interface not supported, driver does not work for MT7922".
Ok... next time.
so the information for "this time" will not be easily found. why not just "do it right", finally.
Are you aware that if I change it now it generates an email to everybody involved, causing them to waste time? Do you do this pestering to other people to perfection in their bugzilla subjects? -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [04-01-23 14:26]:
On 2023-04-01 16:04, Patrick Shanahan wrote:
* Carlos E. R. <> [04-01-23 06:37]:
On 2023-04-01 09:58, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-31 14:05, Per Jessen wrote:
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
I see you added "Mediatek", which in my opinion is only of minimal more use than the laptop model. My brainwaves tell me to write "MT7922" - maybe something like "wifi interface not supported, driver does not work for MT7922".
Ok... next time.
so the information for "this time" will not be easily found. why not just "do it right", finally.
Are you aware that if I change it now it generates an email to everybody involved, causing them to waste time?
not any more than the exasperating length of this (and many other) threads.
Do you do this pestering to other people to perfection in their bugzilla subjects?
only if i notice :). if consideration was present, this would not happen. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-04-01 21:47, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [04-01-23 14:26]:
On 2023-04-01 16:04, Patrick Shanahan wrote:
* Carlos E. R. <> [04-01-23 06:37]:
On 2023-04-01 09:58, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-31 14:05, Per Jessen wrote: > +1. Nobody cares about the laptop model. The support for the wifi > module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
I see you added "Mediatek", which in my opinion is only of minimal more use than the laptop model. My brainwaves tell me to write "MT7922" - maybe something like "wifi interface not supported, driver does not work for MT7922".
Ok... next time.
so the information for "this time" will not be easily found. why not just "do it right", finally.
Are you aware that if I change it now it generates an email to everybody involved, causing them to waste time?
not any more than the exasperating length of this (and many other) threads.
They are not here. They don't read any of this.
Do you do this pestering to other people to perfection in their bugzilla subjects?
only if i notice :). if consideration was present, this would not happen.
Yeah, sure. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-04-01 09:58, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-31 14:05, Per Jessen wrote:
+1. Nobody cares about the laptop model. The support for the wifi module is not specific to the hardware.
Ok, next time then. I will try to edit the line if possible.
I see you added "Mediatek", which in my opinion is only of minimal more use than the laptop model. My brainwaves tell me to write "MT7922" - maybe something like "wifi interface not supported, driver does not work for MT7922".
Ok... next time.
Of course, it is up to you what to do next. The whole thing is an exercise similar to ESRs "How to ask questions the smart way". Maybe we should call it "How to report bugs the smart way" ? There is in fact a section in HTAQTSW named "Use meaningful, specific subject headers". -- Per Jessen, Zürich (10.6°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-30 22:38, Carlos E. R. wrote:
On 2023-03-29 22:38, Carlos E. R. wrote:
On 2023-03-29 21:57, Carlos E. R. wrote:
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote:
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit)
Takashi Iwai says it is supported in 15.5, which is fine with me. But Stephan Hemeier said here it is not. :-? <https://lists.opensuse.org/archives/list/users@lists.opensuse.org/message/LJBW2M24IVP5NN7ROACLRI4V7DZ7IZ56/> So I have to install 15.5 in another partition for testing. He also added that this wifi hardware causes an hibernation panic, with a workaround (bsc#1207948). Very interesting read. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-03-30 22:38, Carlos E. R. wrote:
On 2023-03-29 22:38, Carlos E. R. wrote:
On 2023-03-29 21:57, Carlos E. R. wrote:
On 2023-03-29 21:11, Scott Bradnick via openSUSE Users wrote:
On Wed, 2023-03-29 at 20:45 +0200, Carlos E. R. wrote:
...
Ok, should I report this in Bugzilla, perhaps the kernel devs can consider backporting support for this laptop? It is an enterprise laptop, after all. :-?
Bug 1209980 - Lenovo L14 Gen3, wifi card not recognized. (edit)
Takashi Iwai says it is supported in 15.5, which is fine with me.
But Stephan Hemeier said here it is not. :-?
So I have to install 15.5 in another partition for testing.
No, you only need to test the kernel. -- Per Jessen, Zürich (14.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Per Jessen wrote:
So I have to install 15.5 in another partition for testing.
No, you only need to test the kernel.
As Stephan said yesterday (confirmed btw) the module in the 5.14.21 kernel does not contain the right aliases. They are only for module auto loading though, so I expect you can manually load the module, that ought to work. -- Per Jessen, Zürich (17.7°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-31 13:18, Per Jessen wrote:
Per Jessen wrote:
So I have to install 15.5 in another partition for testing.
No, you only need to test the kernel.
As Stephan said yesterday (confirmed btw) the module in the 5.14.21 kernel does not contain the right aliases. They are only for module auto loading though, so I expect you can manually load the module, that ought to work.
Takashi Iwai got confused and thought I had the atheros chip, not the Mediatek. Less than an hour later he said so, thus the panorama changed within the hour I was reading and posting here. My current plan is to install 15.5 fresh in a new partition (I left space on the disk for that purpose) and test both hibernation and WiFi, then report with new bugs. Yes, updating kernel alone would be enough, but I think better test the whole stack and report other possible bugs. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-03-31 13:24, Carlos E. R. wrote:
On 2023-03-31 13:18, Per Jessen wrote:
Per Jessen wrote:
So I have to install 15.5 in another partition for testing.
No, you only need to test the kernel.
As Stephan said yesterday (confirmed btw) the module in the 5.14.21 kernel does not contain the right aliases. They are only for module auto loading though, so I expect you can manually load the module, that ought to work.
Takashi Iwai got confused and thought I had the atheros chip, not the Mediatek. Less than an hour later he said so, thus the panorama changed within the hour I was reading and posting here.
My current plan is to install 15.5 fresh in a new partition (I left space on the disk for that purpose) and test both hibernation and WiFi, then report with new bugs.
Yes, updating kernel alone would be enough, but I think better test the whole stack and report other possible bugs.
Takashi Iwai has been very nice and created a backported kernel for 15.5 in his home repo. Me, I installed 15.5 in a new partition (I had left space for this in advance), tested it, and worked fine. :-DDD 15.5 looks nice. What is the timetable for it? -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 31.03.2023 23:03, Carlos E. R. wrote:
15.5 looks nice. What is the timetable for it?
Are you trying to tell us that you have never heard about https://en.opensuse.org/openSUSE:Roadmap?
On 2023-03-31 22:05, Andrei Borzenkov wrote:
On 31.03.2023 23:03, Carlos E. R. wrote:
15.5 looks nice. What is the timetable for it?
Are you trying to tell us that you have never heard about https://en.opensuse.org/openSUSE:Roadmap?
Yes, but I had forgotten the name of the page :-D And I have seen that page be incorrect some times. According to the page: Wed, Feb 16, 2023 Beta build is done Thu, April 6th, 2023 Checkin Deadline for RC In that case, I may try to upgrade the machine main partition next week. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. wrote:
On 2023-03-31 22:05, Andrei Borzenkov wrote:
On 31.03.2023 23:03, Carlos E. R. wrote:
15.5 looks nice. What is the timetable for it?
Are you trying to tell us that you have never heard about https://en.opensuse.org/openSUSE:Roadmap?
Yes, but I had forgotten the name of the page :-D
If you google "opensuse 15.5 timetable", guess what the topmost hit is? :-)
And I have seen that page be incorrect some times.
Entirely unlike information on this list :-) -- Per Jessen, Zürich (11.0°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-04-01 08:28, Per Jessen wrote:
Carlos E. R. wrote:
On 2023-03-31 22:05, Andrei Borzenkov wrote:
On 31.03.2023 23:03, Carlos E. R. wrote:
15.5 looks nice. What is the timetable for it?
Are you trying to tell us that you have never heard about https://en.opensuse.org/openSUSE:Roadmap?
Yes, but I had forgotten the name of the page :-D
If you google "opensuse 15.5 timetable", guess what the topmost hit is? :-)
Oops.
And I have seen that page be incorrect some times.
Entirely unlike information on this list :-)
It was corrected with information posted in the mail list :-p -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Le 29/03/2023 à 16:43, Carlos E. R. a écrit :
I did read *all* the links that have been posted in this thread. I did not notice that I should have tried loading module "mt7921e", I was looking for "mt7922". If it was said, sorry, I missed it.
as a general purpose hint, when you run a command, always use the completion TAB, twice if nothing appears. That way modprobe mt <TAB> should have shown all the mt* modules localhost:~ # modprobe mt79 <press TAB> mt7915e mt7921-common mt7921e mt7921s mt7921u mt7996e this can give you the idea of testing one of the others ocalhost:~ # modprobe mt7921-common lhost:~ # lsmod | grep mt mt7921_common 118784 0 mt76_connac_lib 90112 1 mt7921_common mt76 122880 2 mt7921_common,mt76_connac_lib (....) jdd -- mon serveur usenet: dodin.fr.nf c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet
On 2023-03-29 18:33, jdd@dodin.org wrote:
Le 29/03/2023 à 16:43, Carlos E. R. a écrit :
I did read *all* the links that have been posted in this thread. I did not notice that I should have tried loading module "mt7921e", I was looking for "mt7922". If it was said, sorry, I missed it.
as a general purpose hint, when you run a command, always use the completion TAB, twice if nothing appears. That way modprobe mt <TAB> should have shown all the mt* modules
I did do that.
localhost:~ # modprobe mt79 <press TAB> mt7915e mt7921-common mt7921e mt7921s mt7921u mt7996e
this can give you the idea of testing one of the others
ocalhost:~ # modprobe mt7921-common lhost:~ # lsmod | grep mt mt7921_common 118784 0 mt76_connac_lib 90112 1 mt7921_common mt76 122880 2 mt7921_common,mt76_connac_lib (....)
It only offers now "mt7915e". The others are probably loaded already. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Am Mittwoch, 29. März 2023, 16:06:31 CEST schrieb Per Jessen:
Carlos E. R. wrote:
On 2023-03-29 15:11, Per Jessen wrote:
Carlos E. R. wrote:
Huh, I may need another tea. Load what and how?
Carlos, you're sounding like a newbie - which you're certainly not.
I am a newbie in things about WiFi.
There is zero in this thread that is wifi specific. It is all about a non-functioning device and why the module doesn't work or isn't being loaded.
Load what - the module. "mt7921e" Load how - the usual way people load modules, with "modprobe"
Ok, but who has told me to load that module? I have mt7922, not 21. I couldn't guess to load an older module.
Actually, if you had read what a number of people have posted, that is the suggestion. I think both Stephan and David posted material listing "mt7921e" as the module to support your hardware.
What happened when you loaded mt7921e ?
Nothing.
Okay, sorry, I should have said "please post dmesg output after loading mt7921e". There will most likely be some output from that module, maybe complaining about something. Maybe the firmware didn't load. You could also post output of "ip addr" to show us if a wifi device has turned up.
Only one ID in the module: /usr/sbin/modinfo mt7921e filename: /lib/modules/5.14.21-150400.24.46-default/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko.zst license: Dual BSD/GPL author: Lorenzo Bianconi <lorenzo@kernel.org> author: Sean Wang <sean.wang@mediatek.com> firmware: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin suserelease: SLE15-SP4 srcversion: 22ECA6A110356295CBBFDE6 alias: pci:v000014C3d00007961sv*sd*bc*sc*i* depends: mac80211,mt76,mt76-connac-lib,cfg80211 Thats also what the Linux Kernel Driver DataBase said: Raw data from LKDDb: lkddb module mt7921e CONFIG_MT7921E : drivers/net/wireless/mediatek/mt76/mt7921/Kconfig : "MediaTek MT7921E (PCIe) support" # in 5.12–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 0608 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7922 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.16–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7961 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.16–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7961 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.12–5.15 Try a newer kernel from kernel:stable:backports. Stephan
On 2023-03-29 16:48, Stephan Hemeier wrote:
Am Mittwoch, 29. März 2023, 16:06:31 CEST schrieb Per Jessen:
Carlos E. R. wrote:
On 2023-03-29 15:11, Per Jessen wrote:
Carlos E. R. wrote:
...
What happened when you loaded mt7921e ?
Nothing.
Okay, sorry, I should have said "please post dmesg output after loading mt7921e". There will most likely be some output from that module, maybe complaining about something. Maybe the firmware didn't load. You could also post output of "ip addr" to show us if a wifi device has turned up.
Only one ID in the module: /usr/sbin/modinfo mt7921e filename: /lib/modules/5.14.21-150400.24.46-default/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko.zst license: Dual BSD/GPL author: Lorenzo Bianconi <lorenzo@kernel.org> author: Sean Wang <sean.wang@mediatek.com> firmware: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin suserelease: SLE15-SP4 srcversion: 22ECA6A110356295CBBFDE6 alias: pci:v000014C3d00007961sv*sd*bc*sc*i* depends: mac80211,mt76,mt76-connac-lib,cfg80211
Thats also what the Linux Kernel Driver DataBase said: Raw data from LKDDb:
lkddb module mt7921e CONFIG_MT7921E : drivers/net/wireless/mediatek/mt76/mt7921/Kconfig : "MediaTek MT7921E (PCIe) support" # in 5.12–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 0608 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7922 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.16–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7961 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.16–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7961 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.12–5.15
Sorry, I don't know how to interpret those two pastes.
Try a newer kernel from kernel:stable:backports.
Yes, that's what I'm going to do, hopefully this afternoon. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Am Mittwoch, 29. März 2023, 16:55:44 CEST schrieb Carlos E. R.:
Try a newer kernel from kernel:stable:backports.
Yes, that's what I'm going to do, hopefully this afternoon.
Maybe better is to install Leap 15.5 Leap 15.5 has a backported kernel 5.18 or 5.19. Leap 15. only backported kernel 5.16 or so..... So I install Leap 15.5 in a VM and will give you an answer. Stephan
Am Mittwoch, 29. März 2023, 17:00:22 CEST schrieb Stephan Hemeier:
Maybe better is to install Leap 15.5 Leap 15.5 has a backported kernel 5.18 or 5.19. Leap 15. only backported kernel 5.16 or so.....
So I install Leap 15.5 in a VM and will give you an answer.
Stephan
Leap 15.5 has also only 2 ID's inside: /usr/sbin/modinfo mt7921e filename: /lib/modules/5.14.21-150500.46-default/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko.zst license: Dual BSD/GPL author: Lorenzo Bianconi <lorenzo@kernel.org> author: Sean Wang <sean.wang@mediatek.com> firmware: mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin firmware: mediatek/WIFI_RAM_CODE_MT7922_1.bin firmware: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin suserelease: SLE15-SP5 srcversion: 5E5E30BB24F73C57BBD7A4E alias: pci:v000014C3d00007922sv*sd*bc*sc*i* alias: pci:v000014C3d00007961sv*sd*bc*sc*i* depends: mac80211,mt76,mt76-connac-lib,cfg80211 So I think, only Solution is kernel:stable:backports Stephan
On 2023-03-29 16:55, Carlos E. R. wrote:
Try a newer kernel from kernel:stable:backports.
Yes, that's what I'm going to do, hopefully this afternoon.
Don't forget to enable multiple kernels. Okay. You can boot into a different snapshot and rollback but I find it convenient to be able to choose between kernels. in /etc/zypp/zypp.conf multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,running You can also pin down your kernel that you have right now. Use what it says in # uname --kernel-release Due to some old bugs I needed 5.8.12 for a while. I have this on my dev machine: multiversion.kernels = latest,running,5.8.12-1-default,5.8.12-1 -- /bengan
Bengt Gördén wrote:
On 2023-03-29 16:55, Carlos E. R. wrote:
Try a newer kernel from kernel:stable:backports.
Yes, that's what I'm going to do, hopefully this afternoon.
Don't forget to enable multiple kernels. Okay. You can boot into a different snapshot and rollback but I find it convenient to be able to choose between kernels.
in /etc/zypp/zypp.conf
multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,running
I think it's the default - at least judging by my recent installations. -- Per Jessen, Zürich (17.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-29 17:06, Bengt Gördén wrote:
On 2023-03-29 16:55, Carlos E. R. wrote:
Try a newer kernel from kernel:stable:backports.
Yes, that's what I'm going to do, hopefully this afternoon.
Don't forget to enable multiple kernels. Okay. You can boot into a different snapshot and rollback but I find it convenient to be able to choose between kernels.
I don't have snapshots. I don't have any machine with btrfs root. Too experimental. aka I don't use on "/" a filesystem I don't understand.
in /etc/zypp/zypp.conf
multiversion = provides:multiversion(kernel) multiversion.kernels = latest,latest-1,running
You can also pin down your kernel that you have right now. Use what it says in # uname --kernel-release
Laicolasse:~ # uname --kernel-release 5.14.21-150400.24.46-default Laicolasse:~ #
Due to some old bugs I needed 5.8.12 for a while. I have this on my dev machine: multiversion.kernels = latest,running,5.8.12-1-default,5.8.12-1
Ok. I used that setting not very long ago and it did not work. I have written: ]> multiversion.kernels = latest,latest-1,running,5.14.21-150400.24.46-default -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Stephan Hemeier wrote:
Only one ID in the module: /usr/sbin/modinfo mt7921e filename: /lib/modules/5.14.21-150400.24.46-default/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko.zst license: Dual BSD/GPL author: Lorenzo Bianconi <lorenzo@kernel.org> author: Sean Wang <sean.wang@mediatek.com> firmware: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin suserelease: SLE15-SP4 srcversion: 22ECA6A110356295CBBFDE6 alias: pci:v000014C3d00007961sv*sd*bc*sc*i* depends: mac80211,mt76,mt76-connac-lib,cfg80211
Ah, that _would_ be a problem. It also doesn't list the firmware for mt7922.
Try a newer kernel from kernel:stable:backports.
Yes, that sounds like the thing to do now. -- Per Jessen, Zürich (17.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On Wed, 29 Mar 2023 14:20:25 +0200 Per Jessen <per@jessen.ch> wrote:
Dave Howorth wrote:
On Wed, 29 Mar 2023 07:12:21 +0200 Stephan Hemeier <Sauerlandlinux@gmx.de> wrote:
That says the same as we've already established, I think:
lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD
Above is says 5.12-5.19 ? Looking at kernel 5.14.21 (config.gz) as installed on a 15.4 system, the module is enabled.
No, it doesn't. Look closely for the matching vendor and especially device ID. It says 5.17-5.19 as I already said, twice. Don't try what Per suggests Carlos unless you want to waste your time.
Dave Howorth wrote:
On Wed, 29 Mar 2023 14:20:25 +0200 Per Jessen <per@jessen.ch> wrote:
Dave Howorth wrote:
On Wed, 29 Mar 2023 07:12:21 +0200 Stephan Hemeier <Sauerlandlinux@gmx.de> wrote:
That says the same as we've already established, I think:
lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD
Above is says 5.12-5.19 ? Looking at kernel 5.14.21 (config.gz) as installed on a 15.4 system, the module is enabled.
No, it doesn't. Look closely for the matching vendor and especially device ID. It says 5.17-5.19 as I already said, twice.
With "above" being the Linux Kernel Drivers Database at https://cateee.net/lkddb/web-lkddb/MT7921E.html, it _really_ does say 5.12-5.19, see screenshot attached. I also checked the sources in kernel 5.12.1 - it's there. -- Per Jessen, Zürich (16.6°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
Am Donnerstag, 30. März 2023, 17:45:19 CEST schrieb Per Jessen:
With "above" being the Linux Kernel Drivers Database at https://cateee.net/lkddb/web-lkddb/MT7921E.html, it _really_ does say 5.12-5.19, see screenshot attached.
I also checked the sources in kernel 5.12.1 - it's there.
But you have to check the ID. Only as I posted it is available in Leap 15.4 for: alias: pci:v000014C3d00007961sv*sd*bc*sc*i* See /usr/sbin/modinfo mt7921e And https://cateee.net/lkddb/web-lkddb/MT7921E.html says the same: LKDDb Raw data from LKDDb: lkddb module mt7921e CONFIG_MT7921E : drivers/net/wireless/mediatek/mt76/mt7921/Kconfig : "MediaTek MT7921E (PCIe) support" # in 5.12–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 0608 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7922 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.16–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7961 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.16–5.19, 6.0–6.2, 6.3-rc+HEAD lkddb pci 14c3 7961 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.12–5.15 Compare the ID's. The one we are talking about is inserted as ID in kerbnel 5.17. lkddb pci 14c3 0616 .... .... ...... : CONFIG_MT76_CORE CONFIG_MT7921E CONFIG_MT7921_COMMON CONFIG_WLAN CONFIG_WLAN_VENDOR_MEDIATEK : drivers/net/wireless/mediatek/mt76/mt7921/pci.c # in 5.17–5.19, 6.0–6.2, 6.3-rc+HEAD Stephan.
Stephan Hemeier wrote:
Am Donnerstag, 30. März 2023, 17:45:19 CEST schrieb Per Jessen:
With "above" being the Linux Kernel Drivers Database at https://cateee.net/lkddb/web-lkddb/MT7921E.html, it _really_ does say 5.12-5.19, see screenshot attached.
I also checked the sources in kernel 5.12.1 - it's there.
But you have to check the ID.
Yes, I agree, the needed aliases are not listed in the module, that is true. I was really only commenting on what LKDDB says. -- Per Jessen, Zürich (17.6°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes
On 2023-03-30 18:22, Stephan Hemeier wrote:
Am Donnerstag, 30. März 2023, 17:45:19 CEST schrieb Per Jessen:
With "above" being the Linux Kernel Drivers Database at https://cateee.net/lkddb/web-lkddb/MT7921E.html, it _really_ does say 5.12-5.19, see screenshot attached.
I also checked the sources in kernel 5.12.1 - it's there.
But you have to check the ID.
Only as I posted it is available in Leap 15.4 for: alias: pci:v000014C3d00007961sv*sd*bc*sc*i*
See /usr/sbin/modinfo mt7921e
With upgraded kernel:
Laicolasse:~ # uname -a Linux Laicolasse 6.2.8-lp154.3.gc9a94ac-default #1 SMP PREEMPT_DYNAMIC Tue Mar 28 07:54:15 UTC 2023 (c9a94ac) x86_64 x86_64 x86_64 GNU/Linux Laicolasse:~ # Laicolasse:~ # lsmod | grep mt79 mt7921e 36864 0 mt7921_common 118784 1 mt7921e mt76_connac_lib 90112 2 mt7921e,mt7921_common mt76 122880 3 mt7921e,mt7921_common,mt76_connac_lib mac80211 1490944 3 mt76,mt7921_common,mt76_connac_lib cfg80211 1261568 4 mt76,mac80211,mt7921_common,mt76_connac_lib Laicolasse:~ #
Laicolasse:~ # modinfo mt7921e filename: /lib/modules/6.2.8-lp154.3.gc9a94ac-default/kernel/drivers/net/wireless/mediatek/mt76/mt7921/mt7921e.ko.zst license: Dual BSD/GPL author: Lorenzo Bianconi <lorenzo@kernel.org> author: Sean Wang <sean.wang@mediatek.com> firmware: mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin firmware: mediatek/WIFI_RAM_CODE_MT7922_1.bin firmware: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin firmware: mediatek/WIFI_RAM_CODE_MT7961_1.bin suserelease: openSUSE Tumbleweed srcversion: 2916AFA1218E56F98193D33 alias: pci:v000014C3d00000616sv*sd*bc*sc*i* alias: pci:v000014C3d00000608sv*sd*bc*sc*i* alias: pci:v000014C3d00007922sv*sd*bc*sc*i* alias: pci:v000014C3d00007961sv*sd*bc*sc*i* depends: mt76-connac-lib,mt76,mt7921-common retpoline: Y intree: Y name: mt7921e vermagic: 6.2.8-lp154.3.gc9a94ac-default SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Kernel OBS Project sig_key: BC:B2:07:5D:92:88:1E:7C sig_hashalgo: sha256 signature: 5C:AB:5B:74:88:EF:09:6B:B4:DC:D6:A4:1B:7B:E7:7E:5E:51:63:02: E2:56:E5:30:A9:3F:6B:A0:DE:95:3F:52:74:4C:D1:10:77:8D:AB:AB: D3:25:07:C6:78:C9:FE:BA:78:D2:B9:37:C4:EB:E1:21:06:87:9A:5D: DE:40:FC:83:D8:25:FA:6C:B3:A0:6B:5F:A4:87:28:08:DD:BB:F9:41: A1:9D:4C:D3:71:5F:CE:63:2F:CA:7E:A8:9F:A7:42:27:77:DD:C3:60: 34:67:07:AD:35:C9:55:24:2F:54:81:9E:68:4F:7B:87:53:D2:B1:55: 03:C0:B7:3F:18:E5:46:F2:AE:7D:69:EE:24:F8:9F:F9:A5:1C:A1:D6: EF:59:0C:07:49:90:A8:60:F6:46:9B:3E:61:3E:D0:9D:28:1A:98:20: 0B:B1:B9:20:51:BB:41:15:CE:8C:10:8E:F5:01:78:80:7A:F4:0F:A1: D4:12:B1:CD:10:26:4E:BA:C2:8C:F5:DD:13:A0:8A:4D:89:28:EA:5A: 7A:E4:F5:19:2D:9A:CA:B1:B5:12:35:74:26:46:10:96:B5:AE:1A:D0: E6:D5:7B:E3:52:34:0F:B9:64:B6:FE:33:FA:5A:77:19:55:D0:46:85: 70:76:33:F7:E0:8D:87:32:2D:8B:69:DA:D6:5D:BC:88 parm: disable_aspm:disable PCI ASPM support (bool) Laicolasse:~ #
I must say that the ssh session I use to connect to the laptop is not fully responsive, I see a delay when typing. The laptop is 2 meters away, tops, from the AP. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Le 28/03/2023 à 22:44, Carlos E. R. a écrit :
There is no real better choice of laptop for me.
you can still for the moment use a wifi usb pen, may be your card will be supported sometime soon. what disturb me is on an other of your posts, the notice that bluetooth works, WWan works but not wifi. I never had any WWAn on mpy computers and wonder is the device is not either BT+wifi OR BT+WWan but not hte three of them? jdd -- mon serveur usenet: dodin.fr.nf c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet
On 2023-03-29 08:52, jdd@dodin.org wrote:
Le 28/03/2023 à 22:44, Carlos E. R. a écrit :
There is no real better choice of laptop for me.
you can still for the moment use a wifi usb pen, may be your card will be supported sometime soon.
Yes, I thought of that. First I will try with a newer kernel, then with a dongle. In that case, I will ask for advice on which ;.)
what disturb me is on an other of your posts, the notice that bluetooth works, WWan works but not wifi. I never had any WWAn on mpy computers and wonder is the device is not either BT+wifi OR BT+WWan but not hte three of them?
Huh, I have not tried BT yet. I know that it is detected, but I have not tried it. My past history with BT is not a success history. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Tue, 28 Mar 2023 22:44:42 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2023-03-28 22:38, Dave Howorth wrote:
On Tue, 28 Mar 2023 21:58:02 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
I believe 5.17 is the first kernel to support it.
How do you know? :-?
Because I'm awake and I can google?
I wouldn't know what phrase to google for.
Duh, I googled for MT7922 linux and the first hit is https://linux-hardware.org/?id=pci:14c3-0616-105b-e0cd
I tried some strings, found nothing relevant.
Ok, where do I obtain it?
I have no idea. I would assume that when you buy a new laptop you check what hardware is in it*, and that the hardware is supported by linux and what version you need. I don't use laptops so I don't know.
Well, the brand does install Ubuntu in a variant of this model (bigger screen). I did ask if i could install Linux, they said yes.
There is no real better choice of laptop for me.
* and FWIW an RZ616 is apparently the same thing as a MT7922 so the invoice is correct.
no idea.
On 2023-03-29 13:07, Dave Howorth wrote:
On Tue, 28 Mar 2023 22:44:42 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2023-03-28 22:38, Dave Howorth wrote:
On Tue, 28 Mar 2023 21:58:02 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
I believe 5.17 is the first kernel to support it.
How do you know? :-?
Because I'm awake and I can google?
I wouldn't know what phrase to google for.
Duh, I googled for MT7922 linux and the first hit is https://linux-hardware.org/?id=pci:14c3-0616-105b-e0cd
Well, you have better google skills than me. I googled for "Lenovo L14 Wifi Linux".
I tried some strings, found nothing relevant.
... -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Le 28/03/2023 à 20:36, Carlos E. R. a écrit :
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
some hardware switch? jdd -- mon serveur usenet: dodin.fr.nf c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet
On 2023-03-28 21:44, jdd@dodin.org wrote:
Le 28/03/2023 à 20:36, Carlos E. R. a écrit :
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
some hardware switch?
It has to be in software, if there is any. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
Le 28/03/2023 à 21:57, Carlos E. R. a écrit :
On 2023-03-28 21:44, jdd@dodin.org wrote:
Le 28/03/2023 à 20:36, Carlos E. R. a écrit :
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
some hardware switch?
It has to be in software, if there is any.
I have a Lenovo Yoga with a Fn Key wifi switch, dunno at wich level it works jdd -- mon serveur usenet: dodin.fr.nf c'est quoi, usenet? http://www.dodin.org/wiki/pmwiki.php?n=Usenet.Usenet
On 2023-03-28 22:01, jdd@dodin.org wrote:
Le 28/03/2023 à 21:57, Carlos E. R. a écrit :
On 2023-03-28 21:44, jdd@dodin.org wrote:
Le 28/03/2023 à 20:36, Carlos E. R. a écrit :
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
some hardware switch?
It has to be in software, if there is any.
I have a Lenovo Yoga with a Fn Key wifi switch, dunno at wich level it works
Good point. Will try. [...] I have an "airplane key". There is no reaction in the log, or in tlp-stat command. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
On 28.03.23 20:36, Carlos E. R. wrote:
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
Laicolasse:~ # tlp-stat --rfkill --- TLP 1.4.0 --------------------------------------------
+++ Wireless bluetooth = on wifi = none (no device) wwan = on
hci0(btusb) : bluetooth, not connected
Laicolasse:~ #
Laicolasse:~ # hwinfo --wlan Laicolasse:~ #
Laicolasse:~ # inxi --bluetooth -n -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 100 Mbps duplex: full mac: f4:a8:0d:7a:49:01 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb Report: bt-adapter ID: hci0 state: up address: 60:E9:AA:A0:1A:4A Laicolasse:~ #
Did you install firmware for device-2 ? If there is no matching rpm package available you might check <https://github.com/morrownr/USB-WiFi/blob/main/home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md>
On 2023-03-28 22:17, Markus Koßmann wrote:
On 28.03.23 20:36, Carlos E. R. wrote:
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
tlp-stat says there is no WiFi:
Laicolasse:~ # tlp-stat --rfkill --- TLP 1.4.0 --------------------------------------------
+++ Wireless bluetooth = on wifi = none (no device) wwan = on
hci0(btusb) : bluetooth, not connected
Laicolasse:~ #
Laicolasse:~ # hwinfo --wlan Laicolasse:~ #
Laicolasse:~ # inxi --bluetooth -n -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 100 Mbps duplex: full mac: f4:a8:0d:7a:49:01 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb Report: bt-adapter ID: hci0 state: up address: 60:E9:AA:A0:1A:4A Laicolasse:~ #
Did you install firmware for device-2 ?
I have no idea how to do that or if it is necessary. I ask for advice because I have absolutely no idea what to do.
If there is no matching rpm package available you might check <https://github.com/morrownr/USB-WiFi/blob/main/home/How_to_Install_Firmware_for_Mediatek_based_USB_WiFi_adapters.md>
Apparently, I have them all already:
Laicolasse:/lib/firmware/mediatek # ls -lh | grep "BT_RAM_CODE_MT7922_1_1_hdr.bin\|WIFI_MT7922_patch_mcu_1_1_hdr.bin\|WIFI_RAM_CODE_MT7922_1.bin" -rw-r--r-- 1 root root 486K Oct 31 07:18 BT_RAM_CODE_MT7922_1_1_hdr.bin.xz -rw-r--r-- 1 root root 135K Oct 31 07:18 WIFI_MT7922_patch_mcu_1_1_hdr.bin.xz -rw-r--r-- 1 root root 747K Oct 31 07:18 WIFI_RAM_CODE_MT7922_1.bin.xz Laicolasse:/lib/firmware/mediatek #
-- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2023-03-28 at 19:47 -0400, gebser@mousecar.com wrote:
On 3/28/23 4:17 PM, Markus Koßmann wrote:
Laicolasse:~ # hwinfo --wlan
Try
hwinfo --netcard
Laicolasse:~ # hwinfo --netcard 07: PCI 300.0: 0200 Ethernet controller [Created at pci.386] Unique ID: rBUF.Osz2B5WC6KD Parent ID: aYFK.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.3/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x50ae Revision: 0x0e Driver: "r8169" Driver Modules: "r8169" Device File: eth0 I/O Ports: 0x2000-0x2fff (rw) Memory Range: 0xfd604000-0xfd604fff (rw,non-prefetchable) Memory Range: 0xfd600000-0xfd603fff (rw,non-prefetchable) IRQ: 41 (no events) HW Address: f4:a8:0d:7a:49:01 Permanent HW Address: f4:a8:0d:7a:49:01 Link detected: yes Module Alias: "pci:v000010ECd00008168sv000017AAsd000050AEbc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (PCI bridge) 27: PCI 600.0: 0280 Network controller [Created at pci.386] Unique ID: vTuk.elCpZcgOa6E Parent ID: AXjq.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.6/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0xe0c6 Memory Range: 0xe0200000-0xe02fffff (ro,non-prefetchable,disabled) Memory Range: 0xfd400000-0xfd407fff (rw,non-prefetchable,disabled) IRQ: 255 (no events) Module Alias: "pci:v000014C3d00000616sv000017AAsd0000E0C6bc02sc80i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #28 (PCI bridge) Laicolasse:~ # Good catch. - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZCOZSBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV51UAn1IxrxmbSNpzUmI0vT2s wTokEc/5AJ9YqHh19F7CT3Ecc70WmKEDoxWnFQ== =zBXc -----END PGP SIGNATURE-----
On 3/28/23 9:50 PM, Carlos E. R. wrote:
On Tuesday, 2023-03-28 at 19:47 -0400, gebser@mousecar.com wrote:
On 3/28/23 4:17 PM, Markus Koßmann wrote:
Laicolasse:~ # hwinfo --wlan
Try
hwinfo --netcard
Laicolasse:~ # hwinfo --netcard 07: PCI 300.0: 0200 Ethernet controller [Created at pci.386] Unique ID: rBUF.Osz2B5WC6KD Parent ID: aYFK.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.3/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x50ae Revision: 0x0e Driver: "r8169" Driver Modules: "r8169" Device File: eth0 I/O Ports: 0x2000-0x2fff (rw) Memory Range: 0xfd604000-0xfd604fff (rw,non-prefetchable) Memory Range: 0xfd600000-0xfd603fff (rw,non-prefetchable) IRQ: 41 (no events) HW Address: f4:a8:0d:7a:49:01 Permanent HW Address: f4:a8:0d:7a:49:01 Link detected: yes Module Alias: "pci:v000010ECd00008168sv000017AAsd000050AEbc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (PCI bridge)
27: PCI 600.0: 0280 Network controller [Created at pci.386] Unique ID: vTuk.elCpZcgOa6E Parent ID: AXjq.nSObxEWmqk3 SysFS ID: /devices/pci0000:00/0000:00:02.6/0000:06:00.0 SysFS BusID: 0000:06:00.0 Hardware Class: network Model: "MEDIATEK Network controller" Vendor: pci 0x14c3 "MEDIATEK Corp." Device: pci 0x0616 SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0xe0c6 Memory Range: 0xe0200000-0xe02fffff (ro,non-prefetchable,disabled) Memory Range: 0xfd400000-0xfd407fff (rw,non-prefetchable,disabled) IRQ: 255 (no events) Module Alias: "pci:v000014C3d00000616sv000017AAsd0000E0C6bc02sc80i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #28 (PCI bridge) Laicolasse:~ #
Good catch.
-- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar)
Although I have never set up wifi on my Thinkpad, the output of that command is much happier: $ hwinfo --netcard 15: PCI 14.3: 0282 WLAN controller [Created at pci.386] Unique ID: Dhtl.gy222222222 SysFS ID: /devices/pci0000:00/0000:00:14.3 SysFS BusID: 0000:00:14.3 Hardware Class: network Model: "Intel Comet Lake PCH CNVi WiFi" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x06f0 "Comet Lake PCH CNVi WiFi" SubVendor: pci 0x8086 "Intel Corporation" SubDevice: pci 0x0070 Driver: "iwlwifi" Driver Modules: "iwlwifi" Device File: wlp0s20f3 Features: WLAN Memory Range: 0x604111c000-0x604111ffff (rw,non-prefetchable) IRQ: 16 (5 events) HW Address: f2:9b:c4:80:03:47 Permanent HW Address: 38:fc:98:5c:64:c1 Link detected: no WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 36 40 44 48 52 56 60 64 68 72 76 80 84 88 92 96 100 104 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.34 5.36 5.38 5.4 5.42 5.44 5.46 5.48 5.5 5.52 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v00008086d000006F0sv00008086se00000070de02sc80i00" Driver Info #0: Driver Status: iwlwifi is active Driver Activation Cmd: "modprobe iwlwifi" Config Status: cfg=new, avail=yes, need=no, active=unknown .... (other cards listed)
On 2023-03-28 20:36, Carlos E. R. wrote:
Hi,
on my new laptop (Lenovo L14 gen 3) I can not see the WiFi. Network manager doesn't see it.
...
Laicolasse:~ # inxi --bluetooth -n -N Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: eth0 state: up speed: 100 Mbps duplex: full mac: f4:a8:0d:7a:49:01 Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter driver: N/A Bluetooth: Device-1: Foxconn / Hon Hai Wireless_Device type: USB driver: btusb Report: bt-adapter ID: hci0 state: up address: 60:E9:AA:A0:1A:4A Laicolasse:~ #
Bugzilla – Bug 1209980 Lenovo L14 Gen3 AMD, wifi card (Mediatek MT7922) not recognized. Summary. Support has been backported to the kernel that Leap 15.5 has, which will be provided by the first kernel update after install. That is, the installation media will not have support for this WiFi chip. I did not ask if 15.4 would get this backport, but it works with the patched test kernel. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (12)
-
Andrei Borzenkov -
Bengt Gördén -
Carlos E. R. -
Dave Howorth -
Francesco Teodori -
gebser＠mousecar.com -
jdd＠dodin.org -
Markus Koßmann -
Patrick Shanahan -
Per Jessen -
Scott Bradnick -
Stephan Hemeier