Forums before death by AOL, social media and spammers... "We can't have nice things"
|    linux.debian.kernel    |    Debian kernel discussions    |    2,884 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,776 of 2,884    |
|    Uwe =?utf-8?Q?Kleine-K=C3=B6nig?= to pelzi@flying-snail.de    |
|    Re: Bug#1127678: linux-image-6.12.69+deb    |
|    18 Feb 26 17:30:02    |
      XPost: linux.debian.bugs.dist       From: ukleinek@debian.org              Control: tag -1 + moreinfo              Hello,              On Wed, Feb 11, 2026 at 03:18:21PM +0100, pelzi@flying-snail.de wrote:       > Package: linux-image-6.12.69+deb13-amd64       > Version: 6.12.69-1       > Severity: important       > X-Debbugs-Cc: debian-amd64@lists.debian.org       > User: debian-amd64@lists.debian.org       > Usertags: amd64       >        > Dear Maintainer,       >        > after inclusion in mainline kernel, the module rtw_usb with its dependent        > modules,       > detected and initialized the USB wifi dongle with the followinig IDs:       > idVendor=0bda, idProduct=a811, bcdDevice= 2.00       >        > This did work fine with the kernels installed from Debian stable linux-image       up       > to version 6.12.48-1.       >        > After upgrading to version 6.12.63-1, this module fails to identify the        > device,       > and upgrading again to version 6.12.69-1 does not cure the problem.       >        > The outcome of adding this wifi dongle with 6.12.63-1 or 6.12.69-1 are the        > following       > entries in dmesg:       > usb 1-7: USB disconnect, device number 6       > usb 1-7: new high-speed USB device number 8 using xhci_hcd       > usb 1-7: New USB device found, idVendor=0bda, idProduct=a811, bcdDevice=       2.00       > usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3       > usb 1-7: Product: 802.11ac WLAN Adapter        > usb 1-7: Manufacturer: Realtek        > usb 1-7: SerialNumber: 00e04c000001       >        > No additional entries are generated in dmesg.       >        > The expected outcome are additional entries in dmesg like       > usbcore: registered new interface driver rtw_8821au       > usbcore: registered new interface driver rt2800usb              Can you please provide a full kernel log for both the working and the       broken kernel?              Does the broken kernel emit anything to the kernel log when you plug in       the dongle in the completely booted system?              Best regards       Uwe              -----BEGIN PGP SIGNATURE-----              iQEzBAABCgAdFiEEP4GsaTp6HlmJrf7Tj4D7WH0S/k4FAmmV5nsACgkQj4D7WH0S       /k7J+Qf+NUbuX09s6TnjLU+8b9lTx1mADx8ftOQ7xxVT7idWv+RJnbBWzrdAvIkj       pLD+bXsEigp19mfbyioHumJ+qo2Wh7H0LI+D9C1iGr9fCWUaMpPYwtnSdfKKwqcn       sFn0S7TJCtYRjgItZwj+dbrbVsY2x1tWDQX33U7k/R/rAgn0QyWPIQYaCo3pUSLg       n2Kc4EMOQE/0XHhUdooHiA34pC9AOxj60Pbo6GYujZvOHHhGFlbj12gX4ZT5oMYB       cr4KAu1VMBoBnIhMlwJvRURFZbe/UgrEGstnTshm0RUPiROicqGe1DkM1tyF6Tv6       NeqWBMgowT9qhEiFg4rzn3oQYjNVOg==       =eusU       -----END PGP SIGNATURE-----              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca