prompt stringlengths 1 63.6k | completion stringlengths 1 53.1k |
|---|---|
Hello, I have an Acer Nitro 5 laptop with a pretty generic install of Debian 12.4, no special nVidia drivers or anything.It has the geforce rtx 4050 chip. It appears it also has an Intel video controller in the chipset: Code: Select all0000:00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT1 [UHD Graphics] (rev 0c) 0000:01:00.0 VGA compatible controller: NVIDIA Corporation AD107M [GeForce RTX 4050 Max-Q / Mobile] (rev a1) I could have sworn I had used this computer in a dual monitor setup with my TV on the HDMI port, but now, nothing. The only change I can think of was going from Debian 12.1 to 12.4 I am so used to things "just working" that I am afraid I'm a bit rusty at dealing with display issues. I tried a bunch of things, including installing the proprietary (ugh) nVidia driver, and that trashed the system, so obviously I futzed that up somehow. I am not sure what information is relevant, so am happy to post whatever is requested. I hope someone can point me in the right direction, at least. I used to be pretty good at figuring this stuff out, starting with Sarge in 2005, but either I'm getting dumber, or too much has changed....old dogs, new tricks and all that. I just want to be able to once again use a dual monitor setup.... *Edit* I noticed it's running the nouveau driver....something else I just noticed; when I plug in the cable, the little window pops up to set the orientation of the monitors, although it doesn't do anything, and won't go away until I unplug the cable. I wouldn't be surprised it it's something simple.... The plot thickens, both controllers are at /dev/fb0 Code: Select allgary@debian:~$ sudo lshw -C video *-display description: VGA compatible controller product: AD107M [GeForce RTX 4050 Max-Q / Mobile] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:01:00.0 logical name: /dev/fb0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list fb configuration: depth=32 latency=0 mode=1920x1080 visual=truecolor xres=1920 yres=1080 resources: iomemory:600-5ff iomemory:620-61f memory:61000000-61ffffff memory:6000000000-61ffffffff memory:6200000000-6201ffffff ioport:4000(size=128) memory:62080000-620fffff *-display description: VGA compatible controller product: Alder Lake-P GT1 [UHD Graphics] vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 logical name: /dev/fb0 version: 0c width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 resolution=1920,1080 resources: iomemory:620-61f iomemory:400-3ff irq:165 memory:6204000000-6204ffffff memory:4000000000-400fffffff ioport:5000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff | Something to try... Press the F2 (or whatever) at startup to get into the CMOS setup Select Advanced Select the Display mode and change it to Discrete GPU only Save and exit... Gaming laptops sometimes cannot dynamically switch between the 2 GPUs. I don't have a laptop like this but I've seen people running Linux on similar setups. If that option isn't in the CMOS I don't know. |
Hi, I have the Brother QL1110NWB Label Printer and cannot get it to function on Linux. I am hoping someone here may be able to help get it working. I am using Debian 12 on KDE. When I plug the printer into my system via USB, CUPS will detect the USB connection, but printing simply does not commence. It will always say IDLE and just stay there, despite changing the paper size to 4×6”. I have tried the official CUPS wrapper from Brother's website, which I will link below. And I have also tried the ptouch-brother driver that I found in the Debian repo search that says it supports QL series, but I don't see my model in the driver list in CUPS anyway. So far, no luck with making it actually print labels. https://support.brother.com/g/b/downloa ... 1110nwbeus | The device seems to support AirPrint for connections (driverless). AirPrint driver and CUPS driver compatibility The QL1100 uses the CUPS driver for the USB connection. It is not AirPrint compatible. The QL1110NWB uses the AirPrint driver for USB, wired, wireless, and Bluetooth connections on a Macintosh computer. A CUPS driver is not available. AirPrint is supported on iOS on Apple mobile devices. Note The AirPrint driver is not the same as the AirPrint connection protocol that allows for driverless communication from an Apple device to a Brother machine. To use the AirPrint connection protocol, your machine must be connected using a Wired Network or Wireless Network connection. A Bluetooth connection is not supported in conjunction with the AirPrint connection protocol. Click here to display all models covered by this answer. Products Quick Labeler QL1100 QL1110NWB https://help.brother-usa.com/app/answer ... patibility The USB connection will not work with drivers from Brother. Note that IPP-over-USB reserves the USB interface connection with the printer/scanner exclusively for itself and communication with a printer/scanner device by software that does not operate using the IPP-over-USB protocol becomes impossible while ipp-usb is running. This is a consequence of the design of USB communication. It is not a bug in ipp-usb. https://wiki.debian.org/CUPSDriverlessP ... _and_Setup Debian does AirPrint (driverless) too, so you should try to set up a use the driverless connection via USB first. It is possible to disable IPP-over-USB and use the Brother drivers with a USB connection, but use of drivers is now deprecated. If driverless works, use that. At some point CUPS will stop supporting drivers, so better to be future proof. Edit: correction. A driverless printer queue is set up automatically when a driverless device is plugged in, so changed to use rather than set up. |
I just received a new GMKtec G3 N100 NUC Box. I'm currently testing a bunch of distros to see what works and what doesn't. I removed the include nvme SSD with Win11 and filed it away. So on a new nvme ssd I installed Debian 12 xfce4 using the expert method in order to be able to use btrfs with my choice of subvolumes. After booting I check dmesg to see if things were broken and found some firmware issues. On an earlier test I found Bluetooth was not connecting so I went back start over so I could collect data before trying the whole connect process. I found this in the dmesg log: Code: Select all[ 3.751144] Bluetooth: hci0: RTL: examining hci_ver=0b hci_rev=000b lmp_ver=0b lmp_subver=8852 [ 3.753608] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 3.753612] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852bu_fw.bin [ 3.753636] bluetooth hci0: firmware: failed to load rtl_bt/rtl8852bu_fw.bin (-2) [ 3.753638] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 3.753645] bluetooth hci0: firmware: failed to load rtl_bt/rtl8852bu_fw.bin (-2) [ 3.753646] bluetooth hci0: Direct firmware load for rtl_bt/rtl8852bu_fw.bin failed with error -2 [ 3.753649] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852bu_fw.bin not found I included non-free firmware and software during install. Some inxi info: Code: Select alljim@jim-nucboxg3:~$ inxi -Fxxx System: Host: jim-nucboxg3 Kernel: 6.1.0-22-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7 dm: LightDM v: 1.26.0 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: N/A System: GMKtec product: NucBox G3 v: N/A serial: <superuser required> Mobo: GMKtec model: GMKtec serial: <superuser required> UEFI: American Megatrends LLC. v: GMK_G3 date: 10/21/2023 Battery: Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard serial: eb-a9-59-08 charge: 55% (should be ignored) rechargeable: yes status: discharging Device-2: hidpp_battery_1 model: Logitech M570 serial: 0d-67-d9-20 charge: 100% rechargeable: yes status: discharging CPU: Info: quad core model: Intel N100 bits: 64 type: MCP smt: <unsupported> arch: Alder Lake rev: 0 cache: L1: 384 KiB L2: 2 MiB L3: 6 MiB Speed (MHz): avg: 719 high: 754 min/max: 700/3400 cores: 1: 700 2: 706 3: 718 4: 754 bogomips: 6451 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Alder Lake-N [UHD Graphics] driver: i915 v: kernel arch: Gen-12.2 ports: active: HDMI-A-2 empty: HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:46d1 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26") s-diag: 583mm (22.95") Monitor-1: HDMI-A-2 mapped: HDMI-2 model: Sony TV 30 serial: 16843009 res: 1920x1080 hz: 120 dpi: 34 size: 1439x809mm (56.65x31.85") diag: 1651mm (65") modes: max: 3840x2160 min: 640x480 API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel Graphics (ADL-N) direct-render: Yes Audio: Device-1: Intel Alder Lake-N PCH High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 1-6:6 chip-ID: 0573:1573 class-ID: 0300 serial: A34004801402 Device-2: Zoran Personal Media Division (Nogatech) USB Audio and HID type: USB driver: snd-usb-audio API: ALSA v: k6.1.0-22-amd64 status: kernel-api Server-1: PulseAudio v: 16.1 status: active Network: Device-1: Realtek RTL8852BE PCIe 802.11ax Wireless Network driver: N/A pcie: speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 01:00.0 chip-ID: 10ec:b852 class-ID: 0280 Device-2: Intel Ethernet I226-V driver: igc v: kernel pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 03:00.0 chip-ID: 8086:125c class-ID: 0200 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: e0:51:d8:13:36:69 Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-8:8 chip-ID: 0bda:b85b class-ID: e001 serial: 00e04c000001 Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: not found rfk-block: hardware: no software: no address: see --recommends Drives: Local Storage: total: 931.51 GiB used: 2.03 GiB (0.2%) ID-1: /dev/nvme0n1 vendor: Western Digital model: WD Blue SN580 1TB size: 931.51 GiB speed: 63.2 Gb/s lanes: 4 type: SSD serial: 24153L801363 rev: 281010WD temp: 52.9 C scheme: GPT Partition: ID-1: / size: 465.66 GiB used: 2.02 GiB (0.4%) fs: btrfs dev: /dev/nvme0n1p2 ID-2: /boot/efi size: 486 MiB used: 12 MiB (2.5%) fs: vfat dev: /dev/nvme0n1p1 ID-3: /home size: 465.66 GiB used: 2.02 GiB (0.4%) fs: btrfs dev: /dev/nvme0n1p2 ID-4: /var/log size: 465.66 GiB used: 2.02 GiB (0.4%) fs: btrfs dev: /dev/nvme0n1p2 ID-5: /var/tmp size: 465.66 GiB used: 2.02 GiB (0.4%) fs: btrfs dev: /dev/nvme0n1p2 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 50.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 190 Uptime: 17m wakeups: 5 Memory: 7.51 GiB used: 2.54 GiB (33.9%) Init: systemd v: 252 target: graphical (5) default: graphical Compilers: N/A Packages: pm: dpkg pkgs: 1310 Shell: Bash v: 5.2.15 running-in: xfce4-terminal inxi: 3.3.26 What is the next step to get this working? | This is a supported chipset, did you enable non-free firmware when you installed Debian? The package you need is called "firmware-realtek" and is in Bookworm's repository. You might want to check /etc/apt/sources.list to ensure that non-free firmware is enabled so your firmware will get upgrades when available. See here - scroll down to the part that says "If you need the contrib, non-free and non-free-firmware components https://wiki.debian.org/SourcesList#Exa ... urces.list Make the changes to /etc/apt/sources.list (you'll need to be root to do this), then run apt update and install firmware-realtek. Reboot the machine and wifi should work. Good luck - |
I have installed Debian 12 with Gnome today and the wifi is not working (it is not showing up in Gnome settings and nmtui). I already tried to fix it for about 2 hours now. The laptop is a brand new GIGABYTE AORUS 16X ASG with Windows 11 dual-booted (Wifi working there and fast startup disabled). Ethernet and Bluetooth are working fine. Proprietary nVidia driver is installed and backports repo enabled. Here is a lot of diagnostic data: Code: Select alluser@computer~$ lspci 0000:00:00.0 Host bridge: Intel Corporation Device a702 (rev 01) 0000:00:01.0 PCI bridge: Intel Corporation Device a70d (rev 01) 0000:00:02.0 VGA compatible controller: Intel Corporation Raptor Lake-S UHD Graphics (rev 04) 0000:00:04.0 Signal processing controller: Intel Corporation Raptor Lake Dynamic Platform and Thermal Framework Processor Participant (rev 01) 0000:00:06.0 System peripheral: Intel Corporation RST VMD Managed Controller 0000:00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01) 0000:00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01) 0000:00:0e.0 RAID bus controller: Intel Corporation Volume Management Device NVMe RAID Controller Intel Corporation 0000:00:14.0 USB controller: Intel Corporation Device 7a60 (rev 11) 0000:00:14.2 RAM memory: Intel Corporation Device 7a27 (rev 11) 0000:00:15.0 Serial bus controller: Intel Corporation Device 7a4c (rev 11) 0000:00:16.0 Communication controller: Intel Corporation Device 7a68 (rev 11) 0000:00:1a.0 PCI bridge: Intel Corporation Device 7a48 (rev 11) 0000:00:1c.0 PCI bridge: Intel Corporation Device 7a3b (rev 11) 0000:00:1c.6 PCI bridge: Intel Corporation Device 7a3e (rev 11) 0000:00:1c.7 PCI bridge: Intel Corporation Device 7a3f (rev 11) 0000:00:1e.0 Communication controller: Intel Corporation Device 7a28 (rev 11) 0000:00:1e.3 Serial bus controller: Intel Corporation Device 7a2b (rev 11) 0000:00:1f.0 ISA bridge: Intel Corporation Device 7a0c (rev 11) 0000:00:1f.3 Multimedia audio controller: Intel Corporation Device 7a50 (rev 11) 0000:00:1f.4 SMBus: Intel Corporation Device 7a23 (rev 11) 0000:00:1f.5 Serial bus controller: Intel Corporation Device 7a24 (rev 11) 0000:01:00.0 VGA compatible controller: NVIDIA Corporation AD106M [GeForce RTX 4070 Max-Q / Mobile] (rev a1) 0000:01:00.1 Audio device: NVIDIA Corporation Device 22bd (rev a1) 0000:02:00.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 0000:03:00.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 0000:03:01.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 0000:03:02.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 0000:03:03.0 PCI bridge: Intel Corporation Device 1133 (rev 02) 0000:04:00.0 USB controller: Intel Corporation Device 1134 0000:38:00.0 USB controller: Intel Corporation Device 1135 0000:6c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 0000:6d:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 0000:6e:00.0 Network controller: Intel Corporation Device 272b (rev 1a) 10000:e0:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 01) 10000:e0:1b.0 System peripheral: Intel Corporation RST VMD Managed Controller 10000:e0:1b.4 PCI bridge: Intel Corporation Device 7a44 (rev 11) 10000:e1:00.0 Non-Volatile memory controller: Phison Electronics Corporation PS5021-E21 PCIe4 NVMe Controller (DRAM-less) (rev 01) 10000:e2:00.0 Non-Volatile memory controller: Phison Electronics Corporation PS5021-E21 PCIe4 NVMe Controller (DRAM-less) (rev 01) Code: Select alluser@computer:~$ uname -a Linux hostname 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux Code: Select alluser@computer:~$ sudo apt install -t bookworm-backports firmware-iwlwifi Reading package lists... Done Building dependency tree... Done Reading state information... Done firmware-iwlwifi is already the newest version (20230210-5). 0 upgraded, 0 newly installed, 0 to remove and 102 not upgraded. Code: Select alluser@computer:~$ ip link show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: enp109s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether {REDACTED} brd ff:ff:ff:ff:ff:ff Code: Select alluser@computer:~$ cat /etc/network/interfaces cat: /etc/network/interfaces: No such file or directory Code: Select alluser@computer:~$ cat /etc/apt/sources.list #deb cdrom:[Debian GNU/Linux 12.5.0 _Bookworm_ - Official amd64 NETINST with firmware 20240210-11:27]/ bookworm contrib main non-free-firmware deb http://debian.ethz.ch/debian/ bookworm main non-free-firmware non-free contrib deb-src http://debian.ethz.ch/debian/ bookworm main non-free-firmware non-free contrib deb http://security.debian.org/debian-security bookworm-security main non-free-firmware deb-src http://security.debian.org/debian-security bookworm-security main non-free-firmware deb http://deb.debian.org/debian bookworm-backports main non-free-firmware non-free contrib # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports deb http://debian.ethz.ch/debian/ bookworm-updates main non-free-firmware deb-src http://debian.ethz.ch/debian/ bookworm-updates main non-free-firmware # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual. | Code: Select all6.538653] iwlwifi 0000:6e:00.0: PNVM data is missing, please install iwlwifi-gl-c0-fm-c0.pnvm Looks like you also need that firmware file. When you say you installed proprietary Nvidia drivers, do you mean downloaded .run file from Nvidia site? They will always break with a new kernel, you need to reinstall it. It's always better to install nvidia-driver package from Debian repo if possible but I don't think the currently available one has great support for RTX 4070; from what I have read it needs at least 535.x driver and stable still has 525.x. |
I have a Dell Latitude 5550 that I installed Debian 12.5 on. I've noticed that running Debian, I am unable to use two-finger scrolling on the touchpad. Having looked through the output of xinput, the only input device I've seen related to the touchpad is PS/2 Generic Mouse. I have tried using the Ubuntu 24.04 Live CD on this same laptop, and the touchpad (with two-finger scrolling) works correctly, and shows up as a device using the i2c-hid driver. So far, I've tried the following, to no avail: Switching to Sid and updating Compiling and installing the latest version of both libinput and the libinput X driver Compiling and installing the latest stable kernel (6.9.5) I've looked through dmesg, and haven't seen any messages that jumped out to me as being particularly useful, relating to i2c or hid. At this point I'm pretty much out of ideas for what else I should try, so I would appreciate any input. Thanks! | Can you write here all your input devices? They should be seen by this command: Code: Select allcat /proc/bus/input/devices . |
Hallo, my config is: Lenovo Thinkpad P14S, AMD Ryzen 7 Pro 6850U with Radeon Graphics (rembrandt), 28G Ram, Debian 12, x86_64 kernel 6.1.0-22-amd64, Gnome 43.6, Screen Resolution 1920x1080, Lenovo USB-C Dock. from time to time the external screen become blank for apx. 10 to 30 sec, then reappears. When using the internal screen everything works fine. I'm just a "normal" user so it would be nice if someone can give me directions how to locate the error. Thank you all stay safe Reinhard | Hello oida. Can you see any related error messages in journal of systemd in times of blank screen? Code: Select allsudo journalctl -b 0 |
I am awaiting the arrival of a Radeon GPU for my system and currently have an Nvidia GPU. So, my question is how to properly remove the Nvidia GPU and then install the new Radeon GPU. Should I remove the Nvidia drivers first and then take out the physical GPU. Then after I install the Radeon GPU and fire the machine up will I need to run any utilities so that it will be recognized by Debian or will it just recognize it and basically be plug and play? | jam7755 wrote: 2024-07-21 14:52 will it just recognize it and basically be plug and play? Generally, yes. I can't speak to NVidia drivers, or wayalnd installs since I never use them. I have seen issues with xorg declarations preventing auto detection. With that in mind I would probably downgrade the existing machine to nouveau first, make sure all firmware is installed, then switch the gpu. I have moved installations between machines with various gpus and the Xorg auto detection works fine when left alone. It will be easy enough to swap back for a moment if something goes wrong, should be fine. keep in mind, here is a note on what that auto detection magic needs. viewtopic.php?p=804148#p804148 |
Do you use GNOME on X.org? This should write you maximum human-readable information about your graphics: Code: Select allinxi -Gxxxz Sometimes turning off asynchronous power management helps with monitor wake-up (but not always, of course): Code: Select allsudo sh -c 'echo 0 > /sys/power/pm_async' | Hello, stevep wrote: 2024-07-27 01:06 [..] There are many other factors too - two kernel updates IIRC since I posted this, but many dozens of kernel updates before had not fixed it. So swapping the roles of the monitors would appear (Occam's razor) to be the most likely explanation Thanks for the feedback. It may be useful to change the subject of the first post to make it easier to find by other Debian users with the same problem; i.e.: [Solved] HP Z420 mini-tower + NVIDIA GeForce GT1030: displayPort monitor intermittently fails with two monitors Happy Debian! :-) EDIT Sun Sep 1 10:52:21 CEST 2024: updated the subject of the first post |
Hello, I have Debian installed on an external SSD (connected via USB). Is there any way to power off the SSD right before shutting down the system? I ask because currently when I shut down the system the POR Recovery attribute in S.M.A.R.T is increased. | amn1997 wrote: 2024-07-30 12:33 Is there any way to power off the SSD right before shutting down the system? Out of sequence. Shut down, then power off. The POR increment is insignificant. Moved to Hardware |
I recently set-up some old laptops with Debian 12 and GNOME. I noticed that 4GB RAM still works without issues. But in two cases the devices do have only 1 GB of RAM. And this doesn't give a pleasant user experience with GNOME. Therefore, I wondered what max RAM capacity those devices have. It is usually easy to find this information online if I know the exact model of the device. But in this case I struggle to find this information and I wonder if any of you does know an online archive where I might be able to find this information. The laptop is a: HP Pavilion G3000 RM455EA#ABD Unfortunately, I don't have the device with me, so I can't check on the device itself. (This information is probably not listed on the old BIOS, but there might be a terminal tool/command that can still access this information on such old hardware. I tried "dmidecode" but it couldn't access this information. Probably because it expects newer hardware/standards.) From my research I learned that this laptop still uses DDR2 and it seems that the usual maximal capacity of such modules is 2 GB. (On Wikipedia even 8 GB is mentioned, but this does seem to be a rare exception and it probably is only true for desktop RAM anyway.) I figure, if the device has two banks it should be possible to upgrade it to 4 GB. And it seems this would allow GNOME to run just fine on this device. In the past I used the LXDE desktop on such old hardware but since the system needs to be easy to use for random people who never saw free software before, it seems sensible to set those devices up with a desktop that is comfortable and very easy to use. Unfortunately, some common things like the management of wireless connections are more tricky to do with LXDE. (I could use one of the other desktops like LxQt, Xfce or Mate, but I don't have much experience with those and therefore it would be hard for me to troubleshoot them if the need arises. And since GNOME has become noticeable less demanding in recent years I was bold enough to use it on these old laptops. I suspect compared to most other desktops GNOME isn't as much heavier than for example Xfce like it used to be. | Max RAM for that machine is 2GB - found that on several sites that sell RAM. Here's one - https://www.mrmemory.co.uk/memory-ram-u ... /g3000-cto |
Hi there I have an issue which I gather from Googling is fairly common and that is my Asus laptop doesn't always shutdown completely. The power light stays on and I have to press the power button to shutdown completely. Having googled I have tried various ways to sort this out without success. However, I have found that if I turn the wifi off and then shutdown it works every time. So it is not a big issue, but wondered if there was a way of fixing it. My laptop is an ASUS FX502VD and I am running Debian 12. | Hello, reformedhatter wrote: 2024-06-19 07:09 my Asus laptop doesn't always shutdown completely. The power light stays on and I have to press the power button to shutdown completely. [..] if I turn the wifi off and then shutdown it works every time. So it is not a big issue, but wondered if there was a way of fixing it. My laptop is an ASUS FX502VD and I am running Debian 12. This previous topic maybe could be useful: [Solved] Debian 12 does not properly shutdown nor reboot Please report what is your wireless network adapter; you can do it with the following command: Code: Select alllspci -vnn -d ::0280 Hope this help. --- note: discussion moved to "Hardware" sub-forum |
Hello, According to your log, this is your wireless network card [1]: Code: Select alliwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 Just a wild guess. You may try disabling some WiFi 11n features adding a file named /etc/modprobe.d/iwlwifi.conf containing: Code: Select all# parm: 11n_disable:disable 11n functionality, bitmap: # 1: full, # 2: disable agg TX, # 4: disable agg RX, # 8: enable agg TX (uint) options iwlwifi 11n_disable=2 Then, run the command: Code: Select allsudo update-initramfs -u Then, reboot. -- [1] Intel® Dual Band Wireless-AC 8265 | Hello, Mejajsit wrote: 2024-07-27 08:41 I tried Live Ubuntu distro and got the same problem. The wireless adapter uses the same firmware (Intel) because it is almost 10 years old and the kernel has supported it for a long time. This means that the results can be expected to be the same across different distributions. before buying a new device, you may want to check if there is interference from other sources or wireless devices in your area when the wifi connection drops. You can try using the program linssid [1] to analyse the WiFi channel usage in the area where you are operating when the connection drops, or the following command [2] to analyse the WiFi channel usage of your network compared to others: Code: Select allnmcli device wifi -- [1] linssid [2] Is there a tool like wifi analyzer ? |
I have a Brother HL 2390DW laser printer scvanner with USB and wifi.I installed the brother driver install tool from their website that was a .deb package (https://support.brother.com/g/b/downloa ... _us&os=128) After installation I had an error message to run fix broken install and it was a 32 bit package and I have a 64 bit pc, so I did that. WIFI printing works fine without the USB cable but the scanner won't work without the USB cable. Now everything seems to work ok except sleep does not work with the printer USB cable connected. If I unplug it sleep works fine. Any idea why this happens? | It looks like an additional driver may be needed to do wireless scanning. Check it out - https://help.brother-usa.com/app/answer ... 29---linux |
1. Used to have proprietary drivers with my Nvidia card 2. Switched to AMD GPU 3. Since then, am not able to boot into Debian. I get black screen with words "Nvidia GPU not detected"/"failed to load amdgpu" and everything freezes on "loading sddm manager" 4. The only way to load into Debian is to set "nomodeset" parameter on bootup, but then everything is either 640x480 or everything is lagging and tearing, unusable I have so far: 1. Used timeshift to go back to clean debian installation (without nvidia drivers), then updated kernel to 6.9 and all packages — no improvement. 2. Used timeshift to go back to current debian (with Nvidia drivers), purged Nvidia drivers and followed these instructions: https://wiki.debian.org/ChangingFromNvidiaToAmd — no improvement 3. Followed the amd GPU installation guide from Debian docs — no improvement 4. Extracted every single .bin file from kernel directory and put it into lib/firmware as described https://www.reddit.com/r/debian/commen ... o_amd_gpu/ No improvement. At the same time, Fedora worked with the current installation from the very beginning, I didn't have to do anything. So what am I supposed to do to fix this? Any help appreciated. Thanks. | AMD didn't release a Linux driver for this card until about two months ago so it's unlikely it's gonna work with Debian's proprietary drivers in Stable right now. How to get rid of the Nvidia stuff? As root:Code: Select allapt purge nvidia* apt-get autopurgeYou should be able to use open-source drivers for the AMD card now. Please note that Debian does not recommend installing drivers from the vendor's website. https://wiki.debian.org/DontBreakDebian ... ll_scripts Hope this clears things up a little - |
So this is an interesting mystery... Every once in a while, my Lenovo IdeaPad 1 14ALC7 (running Debian Bookworm with KDE) becomes sluggish after boot. Apps take 10x longer than usual to launch, touchpad input lags, the desktop takes ages to start. And, this is the most interesting thing, programs take MUCH more CPU time than they should. Normally htop uses about 5% of one core; in this sluggish state, it cranks away at 20-30% (and lags). Reboot always fixes it. Never even takes more than one try. Reboot once and the laptop is good as new. I haven't remembered to get logs or system info yet - it's somewhat hampered by the machine being barely possible to use in that state. My guess is either a kernel oops or some kind of frequency scaling issue. But I'm curious if anyone else with a recent-ish AMD system has seen this behavior and/or knows a mechanism. | diziet_sma wrote: 2024-05-16 22:16 Code: Select allMay 15 19:19:31 chinchilla kernel: Unstable clock detected, switching default tracing clock to "global" If you want to keep using the local clock, then add: "trace_clock=local" on the kernel command line Maybe Code: Select all#> journalctl -b -g "lock|hpet|tsc|time" --no-pager will give more clues when this happens. If you add trace_clock=global to the GRUB command line, does it triggers the problem? You can also check if trace_clock=local prevents the problem. In this case, the question would be why is the clock unstable? |
I am trying to use and install Debian 12.5 using the live ISO, but my wifi adapter is not recognised. I'm booted into the GNOME desktop, and in the settings it says "no wi-fi adapter found". With the lsusb command in the terminal, it shows that it can see the adapter and has ID 2357:0138 TP-Link 802.11ac NIC. The nmcli command shows that I have a loopback device as well as ethernet. I'm assuming this is because Debian does not include the particular firmware/drivers that my adapter needs, but unfortunately I have no way of connecting via ethernet to download them once I'm booted into Debian. Is there any way around this? I am wondering if there is any way to add the drivers to the ISO before I use it to boot, or if there is some way to specify what drivers you need when downloading the ISO. I was able to use wifi on Ubuntu that I had installed previously, for what that's worth. Any help would be much appreciated | This is the first place to look for Linux hardware info - https://linux-hardware.org/?id=usb:2357-0138 You need a kernel 6.2 or higher, Bookworm has kernel 6.1 so you need to install a later kernel from Backports. Enable the Backports repo - https://wiki.debian.org/Backports and do: Code: Select allapt install linux-image-amd64 linux-headers-amd64 This currently should install linux-image-6.7.12+bpo-amd64 If that doesn't work you may need to compile a driver from Github as linked in the linux-hardware page. You also will need firmware-realtek. If you don't have ethernet you may be able to tether a phone for connection, or download the kernel packages on another computer and copy them to a USB drive then install them manually. you would need to get linux-image-6.7.12+bpo-amd64 linux-headers-6.7.12+bpo-amd64 Easier to take your computer to an ethernet connection though. |
Hi, I've installed Debian Bookworm with KDE on my Thinkpad X13 AMD Gen 1. Just after authenticating to enter my account, the laptop is going to sleep. The laptop is on a 40AH docking station, screen closed when this happen. If I open the screen, I don't have this behavior. Fimware seems to be up-to-date, fwupdmgr didn't report something to update. Because of my wifi card (Mediatek MT7921), I need to be on backported kernel, actually 6.7.12. I tried to go checking on /var/log, but I didn't find something relevant. But I'm no specialist... Is someone have an idea ? Bests regards, | As root, edit /etc/systemd/logind.conf - uncomment and set the following parameters:Code: Select allHandleLidSwitch=ignore HandleLidSwitchExternalPower=ignore HandleLidSwitchDocked=ignoreReboot and the issue should be resolved. Good luck! |
After examining a number of distros, I chose Debian for it's stability and all open-source software. After installing for another user, the Epson 3850 won't do duplex mode(print both sides of page). I tried installing the printer Debian software driver. No effect. I found scanner software, 'document scanner' and it worked. Also, I've found 'scanlite' is good. When tried to install their scanner software, app won't display 'epson 3850' in the window. As I am helping someone else, I won't able to respond for about 3-5 days. Thanks. (wrong forum - change to hardware) | With Libre Office, I tried another duplex print with two pages. This time I noticed the printer display had a notice, 'wrong paper size/type used'. I hit the 'ok' button. I attempted to print duplex again and checked the print settings for paper type. It was set to 'A4' (no idea what that was). I changed it to 'US Letter' and the two page duplex print worked. However, the pages had a number of white lines through the text, but not the previous single sided print of 20 pages. The epson printer scanner software now detects it's own scanner. End topic... |
I'm using Debian 12 "Bookworm". Since last week I'm using only alsa without any sound server. Today, I've realized that built-in mic is not giving any output. After 1h+ of reading manuals, browsing web etc. I've run out of ideas. arecord -l: Code: Select allcard 1: PCH [HDA Intel PCH], device 0: ALC3239 Analog [ALC3239 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 lspci -k | grep -A2 Audio: Code: Select all00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel -- 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04) Subsystem: Lenovo 8 Series/C220 Series Chipset High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel arecord -f s16_le | xxd: Code: Select allRecording WAVE 'stdin' : Signed 16 bit Little Endian, Rate 8000 Hz, Mono 00000000: 5249 4646 2400 0080 5741 5645 666d 7420 RIFF$...WAVEfmt 00000010: 1000 0000 0100 0100 401f 0000 803e 0000 ........@....>.. 00000020: 0200 1000 6461 7461 0000 0080 0000 0000 ....data........ 00000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000040: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................ ...and so on... and interesting errors in journal: journalctl -b --no-pager | grep snd: Code: Select allNov 14 20:31:16 kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3239: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker Nov 14 20:31:16 kernel: snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Nov 14 20:31:16 kernel: snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) Nov 14 20:31:16 kernel: snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 Nov 14 20:31:16 kernel: snd_hda_codec_realtek hdaudioC1D0: inputs: Nov 14 20:31:16 kernel: snd_hda_codec_realtek hdaudioC1D0: Mic=0x19 Nov 14 20:31:16 kernel: snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 Nov 14 20:31:16 kernel: snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Nov 14 20:31:19 alsactl[398]: alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Nov 14 20:31:19 alsactl[398]: alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -2 Nov 14 20:31:19 alsactl[398]: alsa-lib main.c:1541:(snd_use_case_mgr_open) error: failed to import hw:29 use case configuration -2 Nov 14 20:52:14 kernel: snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj. Running Debian 12 "Bookworm" on Lenovo Thinkpad m5400 Any ideas what to do next? (except reinstalling PulseAudio ) | What is output of Code: Select all$ arecord -l ? Can you record with arecord using the --device option? |
Hello, I'm using Linux 6.7.12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.7.12-1 (2024-04-24) x86_64 GNU/Linux and trying to get an Alfa AWUS036ACM wifi dongle working which has a MediaTek mt76x2u chipset. According to the product specifications the necessary drivers should be included in the kernel, however I'm frequently experiencing wifi drop outs and getting various outputs from dmesg. Most commonly occurring is Code: Select alldisconnect from AP 5c:53:c3:22:31:ac for new auth to 5c:53:c3:22:31:ad, in context: Code: Select all[ 19.319427] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ac (local address=00:c0:ca:b4:b3:f6) [ 19.319431] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ac (try 1/3) [ 19.325607] wlx00c0cab4b3f6: authenticated [ 19.328249] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ac (try 1/3) [ 19.341080] wlx00c0cab4b3f6: RX AssocResp from 5c:53:c3:22:31:ac (capab=0x1411 status=0 aid=23) [ 19.342772] wlx00c0cab4b3f6: associated [ 19.417995] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ac [ 340.145189] wlx00c0cab4b3f6: disconnect from AP 5c:53:c3:22:31:ac for new auth to 5c:53:c3:22:31:ad [ 341.253164] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 341.253167] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 341.357130] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 341.769134] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 342.185430] wlx00c0cab4b3f6: authentication with 5c:53:c3:22:31:ad timed out [ 344.703287] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ac (local address=00:c0:ca:b4:b3:f6) [ 344.703290] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ac (try 1/3) [ 344.710250] wlx00c0cab4b3f6: authenticated [ 344.717108] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ac (try 1/3) [ 344.725235] wlx00c0cab4b3f6: RX AssocResp from 5c:53:c3:22:31:ac (capab=0x1411 status=0 aid=24) [ 344.726949] wlx00c0cab4b3f6: associated [ 344.739868] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ac [ 664.986389] wlx00c0cab4b3f6: disconnect from AP 5c:53:c3:22:31:ac for new auth to 5c:53:c3:22:31:ad [ 666.047576] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 666.047581] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 666.150173] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 666.565887] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 666.982137] wlx00c0cab4b3f6: authentication with 5c:53:c3:22:31:ad timed out [ 675.016230] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ac (local address=00:c0:ca:b4:b3:f6) [ 675.016235] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ac (try 1/3) [ 675.025912] wlx00c0cab4b3f6: authenticated [ 675.029596] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ac (try 1/3) [ 675.035246] wlx00c0cab4b3f6: RX AssocResp from 5c:53:c3:22:31:ac (capab=0x1411 status=0 aid=8) [ 675.036932] wlx00c0cab4b3f6: associated [ 675.099371] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ac [ 995.335897] wlx00c0cab4b3f6: disconnect from AP 5c:53:c3:22:31:ac for new auth to 5c:53:c3:22:31:ad [ 996.412581] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 996.412586] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 996.516145] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 996.931891] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 997.347900] wlx00c0cab4b3f6: authentication with 5c:53:c3:22:31:ad timed out [ 1005.202008] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ac (local address=00:c0:ca:b4:b3:f6) [ 1005.202014] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ac (try 1/3) [ 1005.209830] wlx00c0cab4b3f6: authenticated [ 1005.214564] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ac (try 1/3) [ 1005.219869] wlx00c0cab4b3f6: RX AssocResp from 5c:53:c3:22:31:ac (capab=0x1411 status=0 aid=9) [ 1005.221574] wlx00c0cab4b3f6: associated [ 1005.242412] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ac [ 1325.512152] wlx00c0cab4b3f6: disconnect from AP 5c:53:c3:22:31:ac for new auth to 5c:53:c3:22:31:ad [ 1326.588922] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 1326.588928] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 1327.004060] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 1327.420067] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 1327.629417] wlx00c0cab4b3f6: authenticated [ 1327.634326] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ad (try 1/3) [ 1327.640750] wlx00c0cab4b3f6: RX ReassocResp from 5c:53:c3:22:31:ad (capab=0x1011 status=0 aid=12) [ 1327.642437] wlx00c0cab4b3f6: associated [ 1327.705907] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:adrepeating of course. While it doesn't take too long to re-authenticate it is long enough to time out what ever game I'm playing or video I'm watching. Paired with how frequently it's happening it is very annoying and renders online gaming impossible. Second most common issue is Code: Select allmt76x2u 4-3:1.0: tx urb failed: -71 in context: Code: Select all[ 3682.363581] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 3682.363587] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 3682.787222] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 3683.203409] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 3683.458484] wlx00c0cab4b3f6: authenticated [ 3683.459234] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ad (try 1/3) [ 3683.469492] wlx00c0cab4b3f6: RX ReassocResp from 5c:53:c3:22:31:ad (capab=0x1011 status=0 aid=15) [ 3683.471371] wlx00c0cab4b3f6: associated [ 3683.487570] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ad [ 3781.300858] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3781.349103] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3781.357110] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3781.429582] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3781.596916] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3781.670239] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3781.844948] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3782.150638] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3782.337799] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3783.165467] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3783.328904] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3785.087728] mt76x2u 4-3:1.0: tx urb failed: -71 ... This can be fixed by removing the dongle and plugging it back. The third most common issue is Code: Select allmt76x2u 4-3:1.0: vendor request req:07 off:1200 failed:-110 Unplugging the usb dongle crashes the usb port and while the system remains stable the port becomes unusable. Code: Select all[30118.247186] mt76x2u 4-3:1.0: vendor request req:47 off:9018 failed:-110 [30121.447172] mt76x2u 4-3:1.0: vendor request req:47 off:9018 failed:-110 [30124.651231] mt76x2u 4-3:1.0: vendor request req:47 off:9018 failed:-110 [30127.845098] mt76x2u 4-3:1.0: vendor request req:47 off:9018 failed:-110 [30131.045133] mt76x2u 4-3:1.0: vendor request req:47 off:9018 failed:-110 [30134.245170] mt76x2u 4-3:1.0: vendor request req:47 off:9018 failed:-110 [30134.461197] usb 4-3: USB disconnect, device number 6 [30134.493543] xhci_hcd 0000:0c:00.0: WARN Event TRB for slot 13 ep 7 with no TDs queued? [30134.493707] xhci_hcd 0000:0c:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state. [30134.621839] mt76x2u 4-3:1.0: MAC error detected [30134.841390] mt76x2u 4-3:1.0: MAC stop failed [30134.842953] wlx00c0cab4b3f6: deauthenticating from 5c:53:c3:22:31:ad by local choice (Reason: 3=DEAUTH_LEAVING) [30135.059507] mt76x2u 4-3:1.0: MAC error detected [30135.277188] mt76x2u 4-3:1.0: MAC stop failed [30135.381204] mt76x2u 4-3:1.0: MAC error detected [30135.485183] mt76x2u 4-3:1.0: timed out waiting for pending tx [30135.601193] mt76x2u 4-3:1.0: MAC stop failed [30155.809455] xhci_hcd 0000:0c:00.0: Timeout while waiting for setup device command [30174.571519] xhci_hcd 0000:0c:00.0: Abort failed to stop command ring: -110 [30174.571607] xhci_hcd 0000:0c:00.0: xHCI host controller not responding, assume dead [30174.571627] xhci_hcd 0000:0c:00.0: HC died; cleaning up [30174.571679] xhci_hcd 0000:0c:00.0: Timeout while waiting for setup device command [30174.571704] clocksource: Long readout interval, skipping watchdog check: cs_nsec: 4938079399 wd_nsec: 4938081724 [30174.571722] usb 3-5: USB disconnect, device number 11 [30174.572227] usb 3-6: USB disconnect, device number 4 [30174.572229] usb 3-6.3: USB disconnect, device number 5 [30174.572230] usb 3-6.3.1: USB disconnect, device number 6 [30174.572824] usb 3-6.3.2: USB disconnect, device number 8 [30174.573313] usb 3-6.3.3: USB disconnect, device number 9 [30174.573659] usb 3-6.3.5: USB disconnect, device number 7 [30174.574085] usb 3-7: USB disconnect, device number 2 [30174.574304] usb 3-9: USB disconnect, device number 3 [30174.785704] usb 4-3: device not accepting address 7, error -62 [30174.785733] usb usb4-port3: couldn't allocate usb_device [30174.785738] usb 4-6: USB disconnect, device number 3 [30174.785740] usb 4-6.1: USB disconnect, device number 4 It just goes through the usb numbers but never initialises any device I plug into that port within the same session. It stays like that even after logging out and back into the session. A reset fixes the problem and the USB port works again. I have a suspicion that the entire hub controller crashes because all my usb ports on top of the tower cease working. And rarely I get Code: Select allpage_pool_release_retry() stalled pool shutdown 10 inflight 422 sec. This is sometimes mixes with the vendor request failure. In context : Code: Select all[ 3855.302088] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3856.438791] wlx00c0cab4b3f6: deauthenticating from 5c:53:c3:22:31:ad by local choice (Reason: 3=DEAUTH_LEAVING) [ 3860.162128] usb 4-3: USB disconnect, device number 2 [ 3864.742931] usb 4-3: new SuperSpeed USB device number 3 using xhci_hcd [ 3864.768700] usb 4-3: New USB device found, idVendor=0e8d, idProduct=7612, bcdDevice= 1.00 [ 3864.768703] usb 4-3: New USB device strings: Mfr=2, Product=3, SerialNumber=4 [ 3864.768704] usb 4-3: Product: Wireless [ 3864.768705] usb 4-3: Manufacturer: MediaTek Inc. [ 3864.768706] usb 4-3: SerialNumber: 000000000 [ 3864.941514] usb 4-3: reset SuperSpeed USB device number 3 using xhci_hcd [ 3864.967253] mt76x2u 4-3:1.0: ASIC revision: 76120044 [ 3864.986981] mt76x2u 4-3:1.0: firmware: direct-loading firmware mt7662_rom_patch.bin [ 3864.987010] mt76x2u 4-3:1.0: ROM patch build: 20141115060606a [ 3865.118435] mt76x2u 4-3:1.0: firmware: direct-loading firmware mt7662.bin [ 3865.118473] mt76x2u 4-3:1.0: Firmware Version: 0.0.00 [ 3865.118474] mt76x2u 4-3:1.0: Build: 1 [ 3865.118475] mt76x2u 4-3:1.0: Build Time: 201507311614____ [ 3865.840192] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 3865.857985] mt76x2u 4-3:1.0 wlx00c0cab4b3f6: renamed from wlan0 [ 3879.529767] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 3879.529772] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 3879.946465] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 3880.366474] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 3880.556949] wlx00c0cab4b3f6: authenticated [ 3880.561116] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ad (try 1/3) [ 3880.567091] wlx00c0cab4b3f6: RX AssocResp from 5c:53:c3:22:31:ad (capab=0x1011 status=0 aid=23) [ 3880.568792] wlx00c0cab4b3f6: associated [ 3880.636251] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ad [ 3920.671182] page_pool_release_retry() stalled pool shutdown 10 inflight 60 sec [ 3932.873569] wlx00c0cab4b3f6: deauthenticated from 5c:53:c3:22:31:ad (Reason: 4=DISASSOC_DUE_TO_INACTIVITY) [ 3934.162245] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 3934.162250] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 3934.271428] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 3934.683678] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 3935.101085] wlx00c0cab4b3f6: authentication with 5c:53:c3:22:31:ad timed out [ 3937.926388] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ac (local address=00:c0:ca:b4:b3:f6) [ 3937.926393] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ac (try 1/3) [ 3937.930617] wlx00c0cab4b3f6: authenticated [ 3937.935492] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ac (try 1/3) [ 3937.947569] wlx00c0cab4b3f6: RX AssocResp from 5c:53:c3:22:31:ac (capab=0x1411 status=0 aid=18) [ 3937.949269] wlx00c0cab4b3f6: associated [ 3938.021464] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ac [ 3981.085636] page_pool_release_retry() stalled pool shutdown 10 inflight 120 sec [ 4041.501416] page_pool_release_retry() stalled pool shutdown 10 inflight 181 sec [ 4101.918571] page_pool_release_retry() stalled pool shutdown 10 inflight 241 sec [ 4162.339746] page_pool_release_retry() stalled pool shutdown 10 inflight 302 sec [ 4222.757036] page_pool_release_retry() stalled pool shutdown 10 inflight 362 sec [ 4258.117980] wlx00c0cab4b3f6: disconnect from AP 5c:53:c3:22:31:ac for new auth to 5c:53:c3:22:31:ad [ 4259.186513] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 4259.186518] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 4259.601686] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 4260.025969] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 4260.207285] wlx00c0cab4b3f6: authenticated [ 4260.211620] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ad (try 1/3) [ 4260.218313] wlx00c0cab4b3f6: RX ReassocResp from 5c:53:c3:22:31:ad (capab=0x1011 status=0 aid=19) [ 4260.220012] wlx00c0cab4b3f6: associated [ 4260.223023] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ad [ 4283.170163] page_pool_release_retry() stalled pool shutdown 10 inflight 422 sec [ 4343.587395] page_pool_release_retry() stalled pool shutdown 10 inflight 483 sec [ 4404.004641] page_pool_release_retry() stalled pool shutdown 10 inflight 543 sec [ 4464.421897] page_pool_release_retry() stalled pool shutdown 10 inflight 604 sec [ 4524.843180] page_pool_release_retry() stalled pool shutdown 10 inflight 664 sec [ 4585.256723] page_pool_release_retry() stalled pool shutdown 10 inflight 724 sec [ 4612.457395] mt76x2u 4-3:1.0: error: mt76x02u_mcu_wait_resp failed with -110 [ 4645.673791] page_pool_release_retry() stalled pool shutdown 10 inflight 785 sec [ 4675.146994] wlx00c0cab4b3f6: deauthenticating from 5c:53:c3:22:31:ad by local choice (Reason: 3=DEAUTH_LEAVING) [ 4680.854756] mt76x2u 4-3:1.0: timed out waiting for pending tx [ 4694.379447] mt76x2u 4-3:1.0: error: mt76x02u_mcu_wait_resp failed with -110 [ 4706.091053] page_pool_release_retry() stalled pool shutdown 10 inflight 845 sec [ 4713.699517] usb 4-3: USB disconnect, device number 3 [ 4713.710680] mt76x2u 4-3:1.0: MAC error detected [ 4713.929376] mt76x2u 4-3:1.0: MAC stop failed [ 4717.404333] usb 4-3: new SuperSpeed USB device number 4 using xhci_hcd [ 4717.425828] usb 4-3: New USB device found, idVendor=0e8d, idProduct=7612, bcdDevice= 1.00 [ 4717.425833] usb 4-3: New USB device strings: Mfr=2, Product=3, SerialNumber=4 [ 4717.425835] usb 4-3: Product: Wireless [ 4717.425836] usb 4-3: Manufacturer: MediaTek Inc. [ 4717.425837] usb 4-3: SerialNumber: 000000000 [ 4717.598717] usb 4-3: reset SuperSpeed USB device number 4 using xhci_hcd [ 4717.620493] mt76x2u 4-3:1.0: ASIC revision: 76120044 [ 4717.640441] mt76x2u 4-3:1.0: firmware: direct-loading firmware mt7662_rom_patch.bin [ 4717.640467] mt76x2u 4-3:1.0: ROM patch build: 20141115060606a [ 4717.771532] mt76x2u 4-3:1.0: firmware: direct-loading firmware mt7662.bin [ 4717.771568] mt76x2u 4-3:1.0: Firmware Version: 0.0.00 [ 4717.771569] mt76x2u 4-3:1.0: Build: 1 [ 4717.771570] mt76x2u 4-3:1.0: Build Time: 201507311614____ [ 4718.493585] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 4718.511712] mt76x2u 4-3:1.0 wlx00c0cab4b3f6: renamed from wlan0 [ 4729.286871] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) [ 4729.286876] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 1/3) [ 4729.711565] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 2/3) [ 4730.139846] wlx00c0cab4b3f6: send auth to 5c:53:c3:22:31:ad (try 3/3) [ 4730.331861] wlx00c0cab4b3f6: authenticated [ 4730.335578] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ad (try 1/3) [ 4730.342930] wlx00c0cab4b3f6: RX AssocResp from 5c:53:c3:22:31:ad (capab=0x1011 status=0 aid=17) [ 4730.344649] wlx00c0cab4b3f6: associated [ 4730.356711] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ad While this can fix itself during the error I have no internet connection and what ever I'm doing usually times out. I don't know what triggers these errors. Sometimes I can watch youtube for hours or play online games for an entire afternoon, and sometimes I have to replug the dongle between every forum page. I can confirm that there is nothing wrong with the modem, I have flawless wifi connection on my android phone. Also I'd like to mention that I switched to Debian testing from stable because under Debian stable I had the vendor request failure and the tx urb failure but way more often and for some reason the connection was painfully slow but somehow I didn't get any of the authentication/deauthentication spam nor the page_pool errors. I have read a similar issue involving a PI device that was traced back to insufficient power supply cause, but I'm on pc and I have a 1000W corsair PSU so I don't think power is an issue. I've attached the full dmesg reports I saved during the crashes should I've missed some important detail. | Hello, Your USB 3 device is recognized as: Code: Select all[ 3860.162128] usb 4-3: USB disconnect, device number 2 [ 3864.742931] usb 4-3: new SuperSpeed USB device number 3 using xhci_hcd [ 3864.768700] usb 4-3: New USB device found, idVendor=0e8d, idProduct=7612, bcdDevice= 1.00 [ 3864.768703] usb 4-3: New USB device strings: Mfr=2, Product=3, SerialNumber=4 [ 3864.768704] usb 4-3: Product: Wireless [ 3864.768705] usb 4-3: Manufacturer: MediaTek Inc. [ 3864.768706] usb 4-3: SerialNumber: 000000000 [ 3864.941514] usb 4-3: reset SuperSpeed USB device number 3 using xhci_hcd [ 3864.967253] mt76x2u 4-3:1.0: ASIC revision: 76120044 [ 3864.986981] mt76x2u 4-3:1.0: firmware: direct-loading firmware mt7662_rom_patch.bin [ 3864.987010] mt76x2u 4-3:1.0: ROM patch build: 20141115060606a [ 3865.118435] mt76x2u 4-3:1.0: firmware: direct-loading firmware mt7662.bin [ 3865.118473] mt76x2u 4-3:1.0: Firmware Version: 0.0.00 [ 3865.118474] mt76x2u 4-3:1.0: Build: 1 [ 3865.118475] mt76x2u 4-3:1.0: Build Time: 201507311614____ [ 3865.840192] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 3865.857985] mt76x2u 4-3:1.0 wlx00c0cab4b3f6: renamed from wlan0 [ 3879.529767] wlx00c0cab4b3f6: authenticate with 5c:53:c3:22:31:ad (local address=00:c0:ca:b4:b3:f6) Therefore, the idVendor/idProduct is: Code: Select allidVendor=0e8d, idProduct=7612 According to the LKDDb, the device is supported by kernel versions 4.19 and newer : Device 'MediaTek MT7612U 802.11a/b/g/n/ac Wireless Adapter' This is the Linux support status by the manufacturer: Linux support for MT7612U based products As you can see, according to the manufacturer, this WiFi USB adapter is a MT7612U based products. The WiFi adapter loads two firmware files, none of the is for the mt76x2u: Code: Select all$ grep "mt76" vendor.txt | grep -a2 -b2 -i firmware 0-[ +0.021320] mt76x2u 4-3:1.0: ASIC revision: 76120044 55:[ +0.010901] mt76x2u 4-3:1.0: firmware: direct-loading firmware mt7662_rom_patch.bin 141-[ +0.000017] mt76x2u 4-3:1.0: ROM patch build: 20141115060606a 205:[ +0.113228] mt76x2u 4-3:1.0: firmware: direct-loading firmware mt7662.bin 281:[ +0.000057] mt76x2u 4-3:1.0: Firmware Version: 0.0.00 337-[ +0.000002] mt76x2u 4-3:1.0: Build: 1 377-[ +0.000001] mt76x2u 4-3:1.0: Build Time: 201507311614____ These firmwares are distributed with the firmware-misc-nonfree package: Code: Select all$ apt-file search mt7662.bin firmware-misc-nonfree: /lib/firmware/mt7662.bin $ apt-file search mt7662_rom_patch.bin firmware-misc-nonfree: /lib/firmware/mt7662_rom_patch.bin I don't know if newer versions of the firmware is available. According to your logs, USB problems arises soon after transmitting power management kicks in: Code: Select all[ 3683.459234] wlx00c0cab4b3f6: associate with 5c:53:c3:22:31:ad (try 1/3) [ 3683.469492] wlx00c0cab4b3f6: RX ReassocResp from 5c:53:c3:22:31:ad (capab=0x1011 status=0 aid=15) [ 3683.471371] wlx00c0cab4b3f6: associated [ 3683.487570] wlx00c0cab4b3f6: Limiting TX power to 30 (30 - 0) dBm as advertised by 5c:53:c3:22:31:ad [ 3781.300858] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3781.349103] mt76x2u 4-3:1.0: tx urb failed: -71 [ 3781.357110] mt76x2u 4-3:1.0: tx urb failed: -71 [..] According to the Git repository for the Linux kernel, there are only two new commits after kernel version 6.7.12 (which you are currently using) up to version 6.9.3 regarding the source code for the mt76x0 kernel module: Code: Select all$ git log v6.7.12..v6.9.3 --format="%h %as %s" -- ./drivers/net/wireless/mediatek/mt76/mt76x0/ 0a44dfc07074 2024-01-29 wifi: mac80211: simplify non-chanctx drivers f3f8f0503168 2024-01-30 wifi: fill in MODULE_DESCRIPTION()s for mt76 drivers The mt76x2u kernel module depends on these other kernel modules: Code: Select all$ /sbin/modinfo mt76x2u | grep depends depends: mt76x02-usb,mt76x02-lib,mt76,usbcore,mt76x2-common,mt76-usb,mac80211 If you search for commits related to all involved modules list above, there are many more commits between kernel version 6.7.12 (which you are currently using) and version 6.9.3 (latest "upstream" stable): Code: Select all$ git log v6.7.12..v6.9.3 --format="%h %as %s" --grep "mt76x0" --grep "mt76x02-usb" --grep "mt76x02-lib" --grep "mt76" --grep "usbcore" --grep "mt76x2-common" --grep "mt76-usb" --grep "mac80211" -- ./drivers/net/wireless/mediatek/mt76 11b5c4d590b9 2024-04-03 wifi: mt76: connac: use muar idx 0xe for non-mt799x as well ef46dbb93fc9 2024-03-20 wifi: mt76: mt7996: fix potential memory leakage when reading chip temperature 4bbb20401944 2024-03-19 wifi: mt76: mt7996: fix uninitialized variable in mt7996_irq_tasklet() 99e504272523 2024-03-07 wifi: mt76: mt7925: ensure 4-byte alignment for suspend & wow command e55e743830cf 2024-03-05 wifi: mt76: mt7996: fix size of txpower MCU command e469218765b2 2024-03-01 wifi: mt76: connac: check for null before dereferencing ef22ea340552 2024-04-03 wifi: mt76: mt7603: add wpdma tx eof flag for PSE client reset be7f3a092cec 2024-04-02 wifi: mt76: mt7603: fix tx queue of loopback packets 62a2f9608910 2024-03-19 wifi: mt76: mt7915: workaround too long expansion sparse warnings ddb02739a2be 2024-03-26 wifi: mt76: mt7915: add missing chanctx ops a1e163bd298d 2024-02-07 wifi: mt76: Remove redundant assignment to variable tidno e9a46175a79f 2024-02-07 wifi: mt76: fix the issue of missing txpwr settings from ch153 to ch177 8cd725742eaf 2024-02-07 wifi: mt76: mt7921: fix suspend issue on MediaTek COB platform 352d966126e6 2024-02-06 wifi: mt76: mt7921: fix a potential association failure upon resuming c2b22e26755c 2024-01-16 wifi: mt76: mt7921: fix the unfinished command of regd_notifier before suspend 420ad9182c01 2024-01-16 wifi: mt76: mt792x: update the country list of EU for ACPI SAR 07ce1d463724 2024-01-16 wifi: mt76: mt792x: fix a potential loading failure of the 6Ghz channel config from ACPI b6351ef9994c 2024-01-16 wifi: mt76: mt7921: fix incorrect type conversion for CLC command a5a5f4413d91 2024-01-13 wifi: mt76: mt7925e: fix use-after-free in free_irq() c957280ef6ab 2024-01-13 wifi: mt76: mt7921e: fix use-after-free in free_irq() 926f9fb7df9e 2024-01-11 wifi: mt76: mt792x: add the illegal value check for mtcl table of acpi 1f01276b7ab8 2024-01-10 wifi: mt76: mt7925: fix the wrong data type for scan command 3c37da57131f 2023-12-12 wifi: mt76: set page_pool napi pointer for mmio devices 8a7386e787ef 2023-12-11 wifi: mt76: move wed common utilities in wed.c 7b4f9cd6a5fc 2024-01-27 wifi: mt76: mt792x: fix ethtool warning de8882775156 2024-01-26 wifi: mt76: mt7996: fix HIF_TXD_V2_1 value 098428c400ff 2024-01-26 wifi: mt76: connac: set correct muar_idx for mt799x chipsets 3687854d3e7e 2024-01-26 wifi: mt76: mt7996: add locking for accessing mapped registers 83877ed1ad2b 2024-01-26 wifi: mt76: mt7996: remove TXS queue setting d3ad99be7cc2 2024-01-26 wifi: mt76: mt7996: fix efuse reading issue c3ee77ceed9c 2024-01-26 wifi: mt76: mt7996: mark GCMP IGTK unsupported e1a491e856a8 2024-01-26 wifi: mt76: mt7996: fix HE beamformer phy cap for station vif 5d197d37809b 2024-01-26 wifi: mt76: mt7996: ensure 4-byte alignment for beacon commands d52c97592f06 2024-01-26 wifi: mt76: mt7996: fix incorrect interpretation of EHT MCS caps 5d5edc09197c 2024-01-26 wifi: mt76: mt7996: disable AMSDU for non-data frames 5c832c228f6a 2024-01-26 wifi: mt76: mt7996: fix TWT issues 9c9c25f1dcdd 2024-01-26 wifi: mt76: mt7996: check txs format before getting skb by pid 396e41a74a88 2023-12-24 wifi: mt76: mt7925: support temperature sensor 0844947ccf64 2023-12-29 wifi: mt76: mt7925: update PCIe DMA settings 8536ef0aeae1 2023-12-29 wifi: mt76: mt7925: add support to set ifs time by mcu command 9300ae0cd9e8 2023-12-29 wifi: mt76: mt7925: add flow to avoid chip bt function fail d8cf7e134472 2023-12-29 wifi: mt76: mt7925: fix the wrong header translation config 47916693ec7c 2023-12-29 wifi: mt76: mt7925: fix WoW failed in encrypted mode 6864bc734a48 2023-12-29 wifi: mt76: mt7925: fix fw download fail 9d89edb576e3 2023-12-29 wifi: mt76: mt7925: fix wmm queue mapping 2f475cb63eb3 2023-12-29 wifi: mt76: mt7925: fix mcu query command fail 243cecc85773 2023-12-29 wifi: mt76: mt7925: fix SAP no beacon issue in 5Ghz and 6Ghz band 479146078a21 2023-12-29 wifi: mt76: mt7925: fix connect to 80211b mode fail in 2Ghz band 70b8250b30e2 2023-12-22 wifi: mt76: mt76x2u: add netgear wdna3100v3 to device table 181fa3452784 2023-12-23 wifi: mt76: mt792xu: enable dmashdl support 5304bf3b9915 2023-12-23 wifi: mt76: usb: store usb endpoint in mt76_queue 375c5eebbfa2 2023-12-23 wifi: mt76: usb: create a dedicated queue for psd traffic 030d2e287a90 2023-12-21 wifi: mt76: mt7996: fix fw loading timeout 8b0fdca33d3d 2023-10-17 wifi: mt76: mt7915: update mt798x_wmac_adie_patch_7976 0937f95ab07a 2023-08-15 wifi: mt76: mt7915: add locking for accessing mapped registers 350f63c9624b 2024-01-18 wifi: mt76: mt7915: fix error recovery with WED enabled 6178554066bc 2023-12-08 wifi: mt76: check txs format before getting skb by pid 775cf70c409b 2023-09-06 wifi: mt76: disable HW AMSDU when using fixed rate 6030b3a469f8 2024-02-16 wifi: mac80211: check beacon countdown is complete on per link basis 04ada8599c35 2024-01-30 wifi: mac80211: add support to call csa_finish on a link 6092077ad09c 2024-01-29 wifi: mac80211: introduce 'channel request' 0a44dfc07074 2024-01-29 wifi: mac80211: simplify non-chanctx drivers 0647903efbc8 2024-02-03 wifi: mt76: mt7996: fix fortify warning f3f8f0503168 2024-01-30 wifi: fill in MODULE_DESCRIPTION()s for mt76 drivers 0ee28c9ae042 2023-12-18 Merge tag 'wireless-next-2023-12-18' of git://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next 40d51f70f082 2023-12-12 wifi: mt76: mt7996: Use DECLARE_FLEX_ARRAY() and fix -Warray-bounds warnings 10f2903147ed 2023-11-22 wifi: mt76: mt7921: fix wrong 6Ghz power type d0a2bc5fe712 2023-11-22 wifi: mt76: mt7921: fix CLC command timeout when suspend/resume fa6ad88e023d 2023-11-22 wifi: mt76: mt7921: fix country count limitation for CLC 4812ba9ab940 2023-11-22 wifi: mt76: mt7921: reduce the size of MCU firmware download Rx queue 4920a3a1285f 2023-11-17 wifi: mt76: mt7996: set DMA mask to 36 bits for boards with more than 4GB of RAM 92184eae1d5a 2023-11-17 wifi: mt76: mt7921s: fix workqueue problem causes STA association fail d07974645570 2023-11-17 wifi: mt76: Convert to platform remove callback returning void 170a8969db88 2023-11-13 wifi: mt76: mt7925: remove iftype from mt7925_init_eht_caps signature 3d3f117a259a 2023-11-13 wifi: mt76: mt7996: add PCI IDs for mt7992 408566db8cad 2023-11-13 wifi: mt76: connac: add new definition of tx descriptor 8df63a4bbe3d 2023-11-13 wifi: mt76: mt7996: adjust interface num and wtbl size for mt7992 2cbbefdc5c9c 2023-11-13 wifi: mt76: mt7996: support mt7992 eeprom loading 50fbebf6a151 2023-11-13 wifi: mt76: mt7996: rework register offsets for mt7992 9fe6690b8bef 2023-11-13 wifi: mt76: mt7996: add DMA support for mt7992 a63b75aac846 2023-11-13 wifi: mt76: connac: add firmware support for mt7992 1e1e563fe3bd 2023-11-13 wifi: mt76: mt7996: introduce mt7996_band_valid() 2ee1c40daeb9 2023-11-10 wifi: mt76: mt7996: fix mt7996_mcu_all_sta_info_event struct packing ff434cc129d6 2023-11-06 wifi: mt76: mt7915: also MT7981 is 3T3R but nss2 on 5 GHz band 3531c72aedb9 2023-11-06 wifi: mt76: mt7915: fix EEPROM offset of TSSI flag on MT7981 2c2f50bf6407 2023-11-02 wifi: mt76: connac: fix EHT phy mode check eb80e02b2c03 2023-11-02 wifi: mt76: connac: add beacon protection support for mt7996 b769f7d8d900 2023-11-02 wifi: mt76: mt7996: rework ampdu params setting d58a9778f7ca 2023-11-02 wifi: mt76: mt7996: fix alignment of sta info event d57e1b255475 2023-11-02 wifi: mt76: mt7996: switch to mcu command for TX GI report 1e12f0f81f36 2023-11-02 wifi: mt76: use chainmask for power delta calculation f75e4779d215 2023-11-02 wifi: mt76: mt7996: add txpower setting support 11a60bd2a590 2023-11-02 wifi: mt76: change txpower init to per-phy 1e3f387736c7 2023-10-23 wifi: mt76: mt7996: fix rate usage of inband discovery frames 22f5dc781574 2023-10-23 wifi: mt76: mt7996: align the format of fixed rate command 8c8f77e0a656 2023-10-23 wifi: mt76: mt7996: handle IEEE80211_RC_SMPS_CHANGED 4ef49d1858e7 2023-10-23 wifi: mt76: connac: set fixed_bw bit in TX descriptor for fixed rate frames de2a41cbfc7a 2023-10-23 wifi: mt76: mt7996: adjust WFDMA settings to improve performance 4aa9992674e7 2023-10-23 wifi: mt76: mt7996: fix the size of struct bss_rate_tlv 254ab81f3b82 2023-10-23 wifi: mt76: connac: add beacon duplicate TX mode support for mt7996 6879b2e94172 2023-10-23 wifi: mt76: mt7996: add thermal sensor device support 21f290884bc1 2023-10-23 wifi: mt76: connac: add thermal protection support for mt7996 0afb228d9bd4 2023-10-23 wifi: mt76: mt7996: add TX statistics for EHT mode in debugfs af2825729b52 2023-10-23 wifi: mt76: mt7996: add support for variants with auxiliary RX path 5f9d5d4fc561 2023-10-20 wifi: mt76: mt7915: fallback to non-wed mode if platform_get_resource fails in mt7915_mmio_wed_init() a5d028d66836 2023-10-20 wifi: mt76: mt7996: add wed rro delete session garbage collector 00d2ced0deb3 2023-10-20 wifi: mt76: mt7996: add wed reset support d4b85aff3ab3 2023-10-20 wifi: mt76: move wed reset common code in mt76 module 950d0abb5cd9 2023-10-20 wifi: mt76: mt7996: add wed rx support b8b36f47070f 2023-10-20 wifi: mt76: mt7996: use u16 for val field in mt7996_mcu_set_rro signature 5bb7a655045e 2023-10-20 wifi: mt76: dma: introduce __mt76_dma_queue_reset utility routine 83eafc9251d6 2023-10-20 wifi: mt76: mt7996: add wed tx support af8d2af57584 2023-10-20 wifi: mt76: increase MT_QFLAG_WED_TYPE size 2e420b88ca86 2023-10-20 wifi: mt76: introduce wed pointer in mt76_queue 132d74d31e86 2023-10-20 wifi: mt76: introduce mt76_queue_is_wed_tx_free utility routine ac4659856c22 2023-10-20 wifi: mt76: move mt76_net_setup_tc in common code 5f60735c08ce 2023-10-20 wifi: mt76: move mt76_mmio_wed_offload_{enable,disable} in common code b92158a8dc41 2023-10-20 wifi: mt76: mmio: move mt76_mmio_wed_{init,release}_rx_buf in common code 2fac91f2a1db 2023-10-20 wifi: mt76: Remove unnecessary (void*) conversions fdddaa52641e 2023-10-18 wifi: mt76: permit to load precal from NVMEM cell for mt7915 a1f57685fe85 2023-10-18 wifi: mt76: permit to use alternative cell name to eeprom NVMEM load 3d96764e6a22 2023-10-18 wifi: mt76: make mt76_get_of_eeprom static again a6342c31ab3b 2023-10-18 wifi: mt76: limit support of precal loading for mt7915 to MTD only c33e5f4cbb9f 2023-10-18 wifi: mt76: fix typo in mt76_get_of_eeprom_from_nvmem function e874a79250b3 2023-10-18 wifi: mt76: fix broken precal loading from MTD for mt7915 706e83b33103 2023-10-12 wifi: mt76: mt7996: fix uninitialized variable in parsing txfree ce18572b7b59 2023-10-01 wifi: mt76: mt7921: support 5.9/6GHz channel config in acpi 14cdeaf9504c 2023-08-25 wifi: mt76: add ability to explicitly forbid LED registration with DT This commit could be interesting (in respect to power settings): Code: Select all$ git show e9a46175a79f commit e9a46175a79fbc591c48d433020444b8fa2750ee Author: Ming Yen Hsieh <mingyen.hsieh@mediatek.com> Date: Wed Feb 7 11:31:23 2024 +0800 wifi: mt76: fix the issue of missing txpwr settings from ch153 to ch177 Because the number of channels to be configured is calculated using the %, and it results in 0 when there's an exact division, this leads to some channels not having their tx power configured. Fixes: 7801da338856 ("wifi: mt76: mt7921: enable set txpower for UNII-4") Signed-off-by: Ming Yen Hsieh <mingyen.hsieh@mediatek.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> diff --git a/drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c b/drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c index 9aff0c13efd7..af0c2b2aacb0 100644 --- a/drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c +++ b/drivers/net/wireless/mediatek/mt76/mt76_connac_mcu.c @@ -2104,7 +2104,7 @@ mt76_connac_mcu_rate_txpower_band(struct mt76_phy *phy, int j, msg_len, num_ch; struct sk_buff *skb; - num_ch = i == batch_size - 1 ? n_chan % batch_len : batch_len; + num_ch = i == batch_size - 1 ? n_chan - i * batch_len : batch_len; msg_len = sizeof(tx_power_tlv) + num_ch * sizeof(sku_tlbv); skb = mt76_mcu_msg_alloc(dev, NULL, msg_len); if (!skb) { These commits relates to USB issues: Code: Select all$ git log v6.7.12..v6.9.3 --format="%h %as %s" --grep "usb" -- ./drivers/net/wireless/mediatek/mt76 181fa3452784 2023-12-23 wifi: mt76: mt792xu: enable dmashdl support 5304bf3b9915 2023-12-23 wifi: mt76: usb: store usb endpoint in mt76_queue 375c5eebbfa2 2023-12-23 wifi: mt76: usb: create a dedicated queue for psd traffic Therefore, you probably need to test a newer kernel. |
I connect to the internet via WiFi and it happens that occasionally and recurrently the connection keeps dropping and coming back on its own. It's true that there are several similar topics to this one, however, I haven't found any that are actually the same as my case. I managed to collect some logs, but I don't have the necessary knowledge to understand what they mean. So, any help to solve this would be REALLY appreciated! A few days passed and something happened that seemed very strange to me. I have another notebook (which I will call machine 2) and now it is having the same problem, however, it has different logs. Meanwhile, machine 1 (the notebook that initially had the problem) is working normally now, without connection drops. Machine 1: Specs (from neofetch): Code: Select allOS: Debian GNU/Linux 12 (bookworm) x86_64 Host: Inspiron 15 3520 Kernel: 6.1.0-20-amd64 WM: i3 Output of inxi -N: Code: Select allNetwork: Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter driver: rtw_8821ce Logs: Host 1 dmesg logs Host 1 network-manager (v1.42.4-1) logs Host 1 wpa_supplicant (v2:2.10-12) logs Machine 2: Specs (from neofetch): Code: Select allOS: Debian GNU/Linux trixie/sid x86_64 Host: Aspire A515-51 V2.02 Kernel: 6.7.12-amd64 WM: i3 Output of inxi -N: Code: Select allNetwork: Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet driver: r8169 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter driver: ath10k_pci Logs: Host 2 dmesg logs Host 2 network-manager (v1.46.0-1) logs Host 2 wpa_supplicant (v2:2.10-21) logs If you have any other relevant information that I can provide, please let me know. EDIT 1: Unintentionally, I ended up getting another observation about the problem... I had to go somewhere outside my home network (to a friend's house) and I took my second notebook (machine 2) which was the only computer connected to the network and consequently the only Linux with NetworkManager running and to my surprise, the disconnection problem stopped happening... when I returned to my house and connected to the network, the problem returned, exactly the same. Can I assume then that the problem is that there is another device (machine 1) on the network that also has NetworkManger running? Why and how is this possible?! How to deal with this situation? | Hello, rhuanpk wrote: 2024-05-01 20:33 EDIT 1: [..] I had to go somewhere outside my home network (to a friend's house) and I took my second notebook (machine 2) which was the only computer connected to the network and consequently the only Linux with NetworkManager running and to my surprise, the disconnection problem stopped happening... when I returned to my house and connected to the network, the problem returned, exactly the same. Does the wireless machine2 connection drop for incompatibility with your home's access point protocol ? rhuanpk wrote: 2024-05-01 20:33 Can I assume then that the problem is that there is another device (machine 1) on the network that also has NetworkManger running? Why and how is this possible?! It is very unlikely. rhuanpk wrote: 2024-05-01 20:33 How to deal with this situation? You can check: Access point (AP) configuration and its compatibility with regional configuration for wireless standards wireless adapter configuration and its compatibility with regional wireless standards compatibility between the WiFi standards supported by "machine 2's" wireless adapter and the AP nearby sources of wireless interference rhuanpk wrote: 2024-05-02 03:20 Furthermore I verified that: On machine 1, the firmware-realtek package does NOT support RTL8821CE On machine 2, the firmware-atheros package supports QCA9377 How can we proceed with this information? You can try with a newer kernel/firmware for Debian Backports. Hope this helps. |
Hi Everyone, As of recently i have a new laptop for work (Asus TUF A15 FA506N) which i turned into a dual boot with Windows and Debian (Gnome). First thing i have noticed was that my wifi adapter did not work, so i've added bookworm-backports to /etc/apt/sources.list. It installed a new kernel version (6.7.12+bpo-amd64) and after that wifi worked just fine. Next thing i have done was install Nvidia drivers, which installed succesfully. One thing i noticed was that the windowing system moved from wayland to X11, but i'm fine with that. Finally i noticed that the laptops build-in monitor's brightness can not be changed. The brightness is dim compared to the external monitor and it's causing me to get a headache. I am able to change the slider in Gnome's settings, but the change does not reflect into the actual brightness changing. When booting into Windows, i am able to change the brightness. I have already followed some suggestions online, but none fixed my issue. I am open to do a clean install if needed. Does anyone know where to start with this issue? Thanks in advance! | Hello, Raxus wrote: 2024-06-06 07:06 As of recently i have a new laptop for work (Asus TUF A15 FA506N) which i turned into a dual boot with Windows and Debian (Gnome). [..] I noticed that the laptops build-in monitor's brightness can not be changed. The brightness is dim compared to the external monitor and it's causing me to get a headache. I am able to change the slider in Gnome's settings, but the change does not reflect into the actual brightness changing. When booting into Windows, i am able to change the brightness. Does the brightness control work from the keyboard ? You computer uses a hybrid graphic architecture (amd+nvidia). You may try setting the amdgpu.backlight parameter (amdgpu.backlight=0): Code: Select all/sbin/modinfo amdgpu | grep backlight parm: abmlevel:ABM level (0 = off (default), 1-4 = backlight reduction level) (uint) parm: backlight:Backlight control (0 = pwm, 1 = aux, -1 auto (default)) (bint) Please add "Asus TUF A15 FA506N" to the subject of the first post, like that: "Laptop brightness can not be changed with Asus TUF A15 FA506N" Hope this helps. -- note: moved to "Hardware" sub-forum. |
I bought a GMKtec NucBox-G3. It has an unrecognized WiFi: Code: Select all01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller Subsystem: Realtek Semiconductor Co., Ltd. RTL8852BE PCIe 802.11ax Wireless Network Controller Flags: fast devsel, IRQ 255, IOMMU group 12 I/O ports at 3000 [disabled] [size=256] Memory at 80700000 (64-bit, non-prefetchable) [disabled] [size=1M] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-88-52-01 Capabilities: [158] Latency Tolerance Reporting Capabilities: [160] L1 PM Substates Anyone know when I'll get a driver that supports Realtek RTL8852BE? | It seems you already posted about the same subject few months ago: viewtopic.php?p=787893#p787893 Haven't you already sorted it out? - - - Moved to “Hardware”sub-forum. |
Hello, I am completely new here and this is the first IT/technology forum at all for me. So, I am sorry if my post is not at the correct place and in the correct format. With reference to the post "[Solved] Laptop keyboard not detected on debian 12 (Asus Vivobook Go E1504GA)": viewtopic.php?t=157149 which helped me a lot, I would like to report on a successful installation of Debian 12 Bookworm on a recent ASUS ExpertBook B1402CBA. Here the problem with the non-responding keyboard during installation could be solved more easily. See below. 1. I purchased a ASUS ExpertBook B1402CBA recently (April-2024). Since this is my 3rd ASUS laptop and every time Linux was possible to run on it in the past, I assumed that there won't be any problem again. 2. I tested first the laptop using a Debian 12 live DVD. Everything seemed OK, but the laptop keyboard did not respond after installation. I thought this is not a real problem and kept the laptop. 3. I installed Debian 12 (with all non-free drivers etc.) from DVD using an external DVD drive, but encountered exactly the same problem as in the post above. The laptop keyboard responded only at the very beginning of the installation process but then later during the process not any more. Mouse worked but keyboard not. This persisted despite various attempts. 4. I used then an external keyboard. This worked without problems. After completion of the installation I did the usual: a) include the necessary sources in sources.list according to: https://wiki.debian.org/SourcesList ("If you need the contrib, non-free and non-free-firmware components, add contrib non-free non-free-firmware after main. For example, for Debian 12/Bookworm: " b) Do # apt update, # apt upgrade After restarting the laptop keyboard worked and still works !! | Welcome to our community. I'm glad to hear of your successful installation of Debian albeit after quite a few failed attempts> I'd say that you've most likely not only learned a lot about yourself but also about the power of sticking with a goal until you get your desired goals achieved. |
Hello, Whenever I type the password for the Wi-Fi, it sort of connects but not really. It doesn't give me the password prompt again when I click connect again and the Wi-Fi icon stays greyed out. However, I do not have access to it. I have to go into settings and delete that connection to get prompted for the password again. This has happened on many different routers and the only router my macbook seems to work with is my home router, from which I installed mint with. Also, it doesn't connect to my phone's Wi-Fi if there's a password on it, however, if the password is removed, it then succesfully connects. Please help me troubleshoot this. Here is the output of Code: Select allinxi -Fxz Code: Select allSystem: Kernel: 6.1.0-21-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Machine: Type: Laptop System: Apple product: MacBookPro11,1 v: 1.0 serial: <superuser required> Mobo: Apple model: Mac-189A3D4F975D5FFC v: MacBookPro11,1 serial: <superuser required> UEFI: Apple v: 431.140.6.0.0 date: 06/13/2021 CPU: Info: dual core model: Intel Core i5-4308U bits: 64 type: MT MCP arch: Haswell rev: 1 cache: L1: 128 KiB L2: 512 KiB L3: 3 MiB Speed (MHz): avg: 800 min/max: 800/3300 cores: 1: 800 2: 800 3: 800 4: 800 bogomips: 22399 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Haswell-ULT Integrated Graphics vendor: Apple driver: i915 v: kernel arch: Gen-7.5 bus-ID: 00:02.0 Display: wayland server: X.Org v: 1.22.1.9 with: Xwayland v: 22.1.9 compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1280x800~60Hz Message: No known Wayland EGL/GBM data sources. API: EGL/GBM Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Apple driver: snd_hda_intel v: kernel bus-ID: 00:03.0 Device-2: Intel 8 Series HD Audio driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 Device-3: Broadcom 720p FaceTime HD Camera driver: N/A bus-ID: 02:00.0 API: ALSA v: k6.1.0-21-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active Server-2: PulseAudio v: 16.1 status: off (using pipewire-pulse) Network: Device-1: Broadcom BCM4360 802.11ac Wireless Network Adapter vendor: Apple driver: wl v: kernel bus-ID: 03:00.0 IF: wlp3s0 state: up mac: <filter> IF-ID-1: docker0 state: down mac: <filter> Additionally, here is the output of Code: Select alliwconfig Code: Select alllo no wireless extensions. wlp3s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off docker0 no wireless extensions. P.S This is definitely not the router's problem. Thank you in advance. | Hello, This is you wireless network adapter: Code: Select allDevice-1: Broadcom BCM4360 802.11ac Wireless Network Adapter vendor: Apple driver: wl v: kernel bus-ID: 03:00.0 See here: Broadcom BCM4311, BCM4312, BCM4313, BCM4321, BCM4322, BCM43224, BCM43225, BCM43227, BCM43228, BCM43142, BCM4331, BCM4352, BCM4360 devices (wl) Please add to the subject of the first post the computer model;e.g: My MacBookPro11,1 can't connect to any Wi-Fi (Broadcom BCM4360 802.11ac) note: discussion moved to "Hardware" sub-forum. |
I got the most recent HPLIP "automatic" installer. Double checked it should work in Debian 12 Bookworm per HPLIP devs webpages.(I love this code name, thanks, Debian Devs ). Used USB cable twixt printer and 'puter. QUESTIONS: Is python3-pyqt5 compatible here? Is it deprecated? FWIW, I cannot post this question at the HPLIP forum as my Ubuntu One credentials are recognized, but broken and I cannot even report the login bug code due to that. Go Figure! Ran the installer from the terminal. Edited output of run, below: Code: Select all error: Command failed. Re-try #3... Running 'su -c "apt-get install --force-yes -y python3-dbus.mainloop.qt"' Please wait, this may take several minutes... [b]error: Package install command failed with error code 100[/b] note: Some packages may not get installed on python3 due to distro incompatibilites note: Please check for more information at http://hplipopensource.com/node/369 Would you like to retry installing the missing package(s) (y=yes*, n=no, q=quit) ? y warning: Some HPLIP functionality might not function due to missing package(s). Running 'su -c "apt-get install --force-yes -y policykit-1"' Please wait, this may take several minutes... Running 'su -c "apt-get install --force-yes -y policykit-1-gnome"' Please wait, this may take several minutes... Running 'su -c "apt-get install --force-yes -y python3-dbus.mainloop.pyqt5"' Please wait, this may take several minutes... Running 'su -c "apt-get install --force-yes -y xsane"' Please wait, this may take several minutes... error: A required dependency 'python3-pyqt4 (PyQt 4- Qt interface for Python (for Qt version 4.x))' is still missing. RUNNING POST-PACKAGE COMMANDS ----------------------------- OK RE-CHECKING DEPENDENCIES ------------------------ error: A required dependency 'python3-pyqt4 (PyQt 4- Qt interface for Python (for Qt version 4.x))' is still missing. error: Installation cannot continue without this dependency. error: Please manually install this dependency and re-run this installer. | JeSuisFlaneur wrote: 2024-06-27 18:49 I got the most recent HPLIP "automatic" installer. Take a step back. Why? You have a recently released printer that won't work with hplip from the repository? Then is it driverless enabled, in which case it probably won't even need hplip? https://wiki.debian.org/SystemPrinting Apologies if you have a legitimate reason for wanting to install the latest hplip, but if you have, it would be helpful if you could explain it. What printer do you have, and what do you need to do with hplip that you can't do with a driverless setup, or with hplip from the Debian repository? |
Hi Folks I'm running a Dell XPS17 9700 with Debian 12 and apart from the fingerprint reader, everything has been working perfectly for months. Amongst other things, I do use it for audio work (so sometimes with a USB DAC) but for normal day to day stuff, I do use the laptop's internal mic and speakers. The latest update has just 'broken' the internal speaker and microphone functionality; the speaker icon on the icons only task manager shows a diagonal line through it and when I click on it, the pop-up states that 'no output or input devices found' (and indeed, PulseAudio Volume Control shows no devices as being present) so I now have no 'internal' sound functionality at all. From journalctl -b the below shows some sound related entries with the last three lines being in red: Code: Select allApr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: enabling device (0000 -> 0002) Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 17 10:43:25 dell kernel: iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100 Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: use msi interrupt mode Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: hda codecs found, mask 4 Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: firmware: direct-loading firmware intel/sof/sof-cml.ri Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: firmware intel/sof/sof-cml.ri contains unsupported or invalid extended manifest: -22 Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: failed to load DSP firmware -22 Apr 17 10:43:25 dell kernel: sof-audio-pci-intel-cnl 0000:00:1f.3: error: sof_probe_work failed err: -22 The Dell also received a bios/efi update (via Discover Software Centre) and where it was on 1.28.0 it's now on 1.29.0. I did wonder about whether that was the cause. I did ponder installing the previous bios/efi, but rather than try that, I instead just booted the laptop from the Debian 12 Live edition (from a USB stick) and the sound worked fine (I also tried booting into Windows 10 and the sound's working fine with that) so to me it looks suspiciously like one of the recent apt update packages has caused the problem. If anyone has any thoughts, they'd be gratefully received as at the moment I have no sound (unless using an external DAC and monitor, which isn't available where I daily drive my laptop) so somewhat horrifically (to me), I'm going to have to use Windows 10 until I find a fix. Briain PS When I first installed Debian 12, the microphone didn't work (the speaker was always fine) but I found fix for that; see here: viewtopic.php?p=797264#p797264 (I'm just positing that in case anyone with a similar issue finds this post) and it's been working ever since. With that fault, the hardware all appeared (and no errors in journalctl -b) but the mic didn't pick up any sound, so a very different to the recent update issue described in the main part of my above post. | Hello, Briain wrote: 2024-04-17 10:36 PS When I first installed Debian 12, the microphone didn't work (the speaker was always fine) but I found fix for that; see here: viewtopic.php?p=797264#p797264 It is worth noting that the script that you used to fix your initial problem basically removes files from the official firmware-sof-signed package and replaces them with new versions. These unsupported versions probably explain the error you encounter. |
pipewire PipeWire Sound Server pulse PulseAudio Sound Server Do you still have PulseAudio installed? It can conflict with Pipewire. pipewire-pulse should have uninstalled PulseAudio. Not sure why it is still showing up as a server. Could you post output of the following please? Code: Select all# dmesg | grep 'sof\|snd\|audio\|firmware' Reference to a digital microphone (dmix), so you might need to select digital input and analogue output in pavucontrol. System might be trying to use SOF for the digital microphone. dmesg will clarify. | Could you try booting from a Debian Testing live image? This will tell us if any updates to the kernel/ucm files/firmware have fixed this? https://cdimage.debian.org/cdimage/week ... so-hybrid/ |
So, allow me to start by saying I have been using Debian since debian 9 was out. I have used it on the same laptop with the same wifi card. the laptop is an Asus K53-Z and the wifi card is a Intel 7260 rev. 73 (2 channel 866mhz AC class card) My wireless access point is an Asus RT-AX1800S On Debian 9/10/11 I could leave my wireless access point set at 80mhz wifi channel. This works fine on Debian 9/10/11. But on Debian 12 this causes my wifi to stop after about a minute or so. The only way I can "fix" this is to go into my routers setup page and change the wifi channel bandwidth from 80mh to 40mhz. (20mhz also works). To be clear, when my wifi stops working, it is only stopped working on my laptop, all the rest of the wifi devices continue to work normally. Steps to troubleshoot: After experiencing this issue with debian 12, I live booted a debian 11 dvd to test the wifi, and sure enough it works fine on 80mhz channel bandwidth. But if I boot back into debian 12 it will quit again after 1 minute or so unless I change the channel bandwidth back to 40mhz. I tried changing wifi channels from 36 to 48 to 149. It crashes my wifi on all channels if the bandwidth is set to 80mhz. I disables power save in the debian terminal but this had no effect on crashing during 80mhz bandwidth. No other devices in the household have issues with 80mhz bandwidth except this one laptop, and only if it is booted into debian 12. So I gotta think that something changed between debian 11 and debian 12 that is causing my issue, but I am not smart enough to figure it out. If you guys would like some logs let me know which ones and thank you for any help. Update: After many, many hours of internet based investigating, I was able to fix the issue by adding a file to /etc/modprobe.d called iwlwifi.conf The contents of the file are very simple, just : "options iwlwifi enable_ini=0" and then restart debian. This fixed it. It's been 6 hours now and no more wifi crashes on 80mhz channel bandwidth! | Hello, Florida-Man wrote: 2024-08-12 02:59 So, allow me to start by saying I have been using Debian since debian 9 was out. I have used it on the same laptop with the same wifi card. the laptop is an Asus K53-Z and the wifi card is a Intel 7260 rev. 73 (2 channel 866mhz AC class card) My wireless access point is an Asus RT-AX1800S On Debian 9/10/11 I could leave my wireless access point set at 80mhz wifi channel. This works fine on Debian 9/10/11. But on Debian 12 this causes my wifi to stop after about a minute or so. The only way I can "fix" this is to go into my routers setup page and change the wifi channel bandwidth from 80mh to 40mhz. (20mhz also works). Hello, Have you checked for missing network card firmware? You can check if there are any messages about this in the system logs; you can use the following command: Code: Select allsu -l -c "journalctl -b -g firmware:" Please update the subject of the initial post to include the hardware involved (so other users can easily find it); e.g.: Debian 12 cannot set 80mhz WiFi with Intel 7260 rev. 73 (2 channel 866mhz AC class card) note: discussion moved to "Hardware" sub-forum. |
Hello all. So, Iḿ running a OpenMediaVault NAS (x86), which is just an interface for Debian. Iḿ going to install a thunderbolt 4 card to enable a direct connection to a MacBook with thunderbolt 4 ports. The card is a Gigabyte GC Maple Ridge on a compatible Aorus motherboard. Iḿ fairly new to Linux in general. My reasearch led me to assume that the card is supported by the system and should work out of the box. Is that so? Any hints&tips on how to configure this connection? I can REALLY use a hand here! thanks, Andre | I'll reply although I only have the result of a quick google to offer you. To get more expert help you need to read the post on asking a good question, which tells you how to get your specs and logs in order. TB4 requires windows Gigabyte update to activate, additionally some motherboards don't have a thunderbolt header and a hack is required. Have you seen this 2021 blog post which goes into this? https://chrisbergeron.com/2021/07/25/ul ... and-linux/ |
________________________________________ FINAL COMMENTS: For anyone looking to solve nVidia issues, the takeaway in this thread is that newer nVidia hardware keeps critical firmware on the card (out of the public domain) hence the open source nVidia drivers don't work on older cards, like my Quadro K2200. You need the proprietary ones. If you're seeing this in dmesg: Code: Select all[ 26.055648] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:13ba) NVRM: installed in this system is not supported by open NVRM: nvidia.ko because it does not include the required GPU NVRM: System Processor (GSP). NVRM: Please see the 'Open Linux Kernel Modules' and 'GSP NVRM: Firmware' sections in the driver README, available on NVRM: the Linux graphics driver download page at NVRM: www.nvidia.com. Do this: Code: Select all$ sudo apt autoremove *nvidia* --purge $ sudo apt install nvidia-driver nvidia-smi nvidia-settings $ sudo reboot For Quadro K2200 at least, I strongly recommend using the nVidia drivers. The output is much nicer and I suspect the nouveau driver was damaging my card. I've been experiencing two separate (but possibly causally related) intermittent issues with X. Both can be corrected by restarting X, without rebooting. Code: Select allsudo service lightdm restart The primary issue has been the driver freezing, corrupting and locking the display. This seems to have been fixed by switching from the nouveau to the nvidia driver. The secondary issue, which I'm still seeing with the nvidia driver, is the driver going into some kind of wait loop. The display remains active, but is blank, with only a laggy mouse pointer. I think this is related to waking after sleep, so I need to explore that angle. I'm fairly sure I saw this issue before the driver change, but I think it was probably being masked by the primary issue. I don't have any log of it with nouveau installed. From /var/log/Xorg.1.log Code: Select all[ 23492.639] (--) NVIDIA(GPU-0): [ 23493.118] (--) NVIDIA(GPU-0): AOC 2450W (DFP-1): connected [ 23493.118] (--) NVIDIA(GPU-0): AOC 2450W (DFP-1): Internal TMDS [ 23493.118] (--) NVIDIA(GPU-0): AOC 2450W (DFP-1): 165.0 MHz maximum pixel clock [ 23493.118] (--) NVIDIA(GPU-0): . . . Repeats 14865 times... It's possible it's a hardware problem with my card, however I ran my system for years on Ubuntu, with no graphics issues. They only appeared after I switched to Debian and xfce. I'm assuming (but haven't checked) that the Ubuntu system was using nVidia drivers. I like Debian/xfce and don't intend to go back to Ubuntu, but it would be good if somebody could do an audit of differences in the low level graphics software between the two systems. ________________________________________ ORIGINAL POST: Hi, apologies for the new thread but the existing ones are too cluttered with overlapping issues.. Nouveau was periodically crashing on my machine and maybe killing my GPU, or maybe it's actually a developing hardware issue. The desktop could be restored without rebooting using sudo service lightdm restart. Anyway, I used these instructions to install the nvidia driver... But it won't load... Code: Select allsudo dmesg . . [ 26.054765] nvidia-nvlink: Nvlink Core is being initialized, major device number 242 [ 26.055587] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=io+mem [ 26.055648] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:13ba) NVRM: installed in this system is not supported by open NVRM: nvidia.ko because it does not include the required GPU NVRM: System Processor (GSP). NVRM: Please see the 'Open Linux Kernel Modules' and 'GSP NVRM: Firmware' sections in the driver README, available on NVRM: the Linux graphics driver download page at NVRM: www.nvidia.com. [ 26.055672] nvidia: probe of 0000:01:00.0 failed with error -1 [ 26.055684] NVRM: The NVIDIA probe routine failed for 1 device(s). [ 26.055685] NVRM: None of the NVIDIA devices were initialized. [ 26.055891] nvidia-nvlink: Unregistered Nvlink Core, major device number 242 . . Can anyone pinpoint the problem and suggest a fix? I'd be grateful for a link to the relevant Debian wiki instructions for: nVidia driver installation. changing kernel version, including manual editing grub (I have other boot drives). Failing a resolution I'm going to pull my GPU card and use the on board graphics, hoping my install has drivers for that. Also, can I revert to nouveau easily (without uninstalling nvidia) while I explore the options? My system currently works, but with low res graphics. Ps: I wasn't familiar with timeshift, but I think I'll start using it! Can I use it to copy an installed system onto another drive (ie, able to run as OS from grub)? ____________________________ ____________________________ ____________________________ Code: Select all$ inxi -CGSxxz System: Kernel: 6.1.0-20-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm dm: LightDM Distro: Debian GNU/Linux 12 (bookworm) CPU: Info: quad core model: Intel Core i7-4790 bits: 64 type: MT MCP arch: Haswell rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB Speed (MHz): avg: 1062 high: 2900 min/max: 800/4000 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 2900 8: 801 bogomips: 57600 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: NVIDIA GM107GL [Quadro K2200] driver: N/A arch: Maxwell pcie: speed: 5 GT/s lanes: 16 bus-ID: 01:00.0 chip-ID: 10de:13ba Device-2: Logic3 / SpectraVideo plc LG Optical Mouse 3D-310 type: USB driver: hid-generic,usbhid bus-ID: 2-3.1.3:9 chip-ID: 1267:0210 Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nouveau,vesa unloaded: fbdev,modesetting alternate: nv dri: swrast gpu: N/A display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1024x768 s-dpi: 96 Monitor-1: default res: 1024x768 size: N/A API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 256 bits) direct-render: Yes Code: Select all$ nvidia-detect Detected NVIDIA GPUs: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) Checking card: NVIDIA Corporation GM107GL [Quadro K2200] (rev a2) Your card is supported by all driver versions. Your card is also supported by the Tesla drivers series. Your card is also supported by the Tesla 470 drivers series. It is recommended to install the nvidia-driver package. Code: Select all$ dpkg -l "*nvidia" Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=========================-============-============-===========================================> un bumblebee-nvidia <none> <none> (no description available) ii glx-alternative-nvidia 1.2.2 amd64 allows the selection of NVIDIA as GLX provi> un libegl1-glvnd-nvidia <none> <none> (no description available) un libegl1-nvidia <none> <none> (no description available) un libgldispatch0-nvidia <none> <none> (no description available) un libgles1-glvnd-nvidia <none> <none> (no description available) un libgles2-glvnd-nvidia <none> <none> (no description available) un libglvnd0-nvidia <none> <none> (no description available) un libglx0-glvnd-nvidia <none> <none> (no description available) un libopengl0-glvnd-nvidia <none> <none> (no description available) ii xserver-xorg-video-nvidia 550.54.15-1 amd64 NVIDIA binary Xorg driver Code: Select all$ apt list --installed | grep nvidia WARNING: apt does not have a stable CLI interface. Use with caution in scripts. firmware-nvidia-gsp/unknown,now 550.54.15-1 amd64 [installed,automatic] firmware-nvidia-tesla-gsp/stable-updates,now 525.147.05-7~deb12u1 amd64 [installed] glx-alternative-nvidia/stable,now 1.2.2 amd64 [installed,automatic] libegl-nvidia0/unknown,now 550.54.15-1 amd64 [installed,automatic] libgl1-nvidia-glvnd-glx/unknown,now 550.54.15-1 amd64 [installed,automatic] libgles-nvidia1/unknown,now 550.54.15-1 amd64 [installed,automatic] libgles-nvidia2/unknown,now 550.54.15-1 amd64 [installed,automatic] libglx-nvidia0/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-allocator1/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-cfg1/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-egl-gbm1/stable,now 1.1.0-2 amd64 [installed,automatic] libnvidia-eglcore/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-encode1/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-glcore/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-glvkspirv/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-gpucomp1/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-ml1/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-ptxjitcompiler1/unknown,now 550.54.15-1 amd64 [installed,automatic] libnvidia-rtcore/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-alternative/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-detect/unknown,now 550.54.15-1 amd64 [installed] nvidia-driver-bin/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-driver-libs/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-driver/unknown,now 550.54.15-1 amd64 [installed] nvidia-egl-common/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-egl-icd/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-installer-cleanup/stable,now 20220217+3~deb12u1 amd64 [installed,automatic] nvidia-kernel-common/stable,now 20220217+3~deb12u1 amd64 [installed,automatic] nvidia-kernel-open-dkms/unknown,now 550.54.15-1 amd64 [installed] nvidia-kernel-support/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-legacy-check/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-modprobe/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-persistenced/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-settings/unknown,now 550.54.15-1 amd64 [installed] nvidia-smi/unknown,now 550.54.15-1 amd64 [installed] nvidia-support/stable,now 20220217+3~deb12u1 amd64 [installed,automatic] nvidia-vdpau-driver/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-vulkan-common/unknown,now 550.54.15-1 amd64 [installed,automatic] nvidia-vulkan-icd/unknown,now 550.54.15-1 amd64 [installed,automatic] xserver-xorg-video-nvidia/unknown,now 550.54.15-1 amd64 [installed,automatic] Code: Select all$ apt list --installed | grep firmware WARNING: apt does not have a stable CLI interface. Use with caution in scripts. atmel-firmware/stable,now 1.3-7 all [installed] bluez-firmware/stable,now 1.2-9 all [installed] dahdi-firmware-nonfree/stable,now 2.11.1.0.20170917-2 all [installed] firmware-amd-graphics/stable,now 20230210-5 all [installed] firmware-ast/stable,now 20140808-7 all [installed] firmware-ath9k-htc/stable,now 1.4.0-108-gd856466+dfsg1-1.3+deb12u1 all [installed] firmware-atheros/stable,now 20230210-5 all [installed] firmware-bnx2/stable,now 20230210-5 all [installed] firmware-bnx2x/stable,now 20230210-5 all [installed] firmware-brcm80211/stable,now 20230210-5 all [installed] firmware-cavium/stable,now 20230210-5 all [installed] firmware-intel-sound/stable,now 20230210-5 all [installed] firmware-ipw2x00/stable,now 20230210-5 all [installed] firmware-ivtv/stable,now 20230210-5 all [installed] firmware-iwlwifi/stable,now 20230210-5 all [installed] firmware-libertas/stable,now 20230210-5 all [installed] firmware-linux-free/stable,now 20200122-1 all [installed] firmware-linux-nonfree/stable,now 20230210-5 all [installed,automatic] firmware-misc-nonfree/stable,now 20230210-5 all [installed] firmware-myricom/stable,now 20230210-5 all [installed] firmware-netronome/stable,now 20230210-5 all [installed] firmware-netxen/stable,now 20230210-5 all [installed] firmware-nvidia-gsp/unknown,now 550.54.15-1 amd64 [installed,automatic] firmware-nvidia-tesla-gsp/stable-updates,now 525.147.05-7~deb12u1 amd64 [installed] firmware-qcom-soc/stable,now 20230210-5 all [installed] firmware-qlogic/stable,now 20230210-5 all [installed] firmware-realtek-rtl8723cs-bt/stable,now 20181104-2 all [installed] firmware-realtek/stable,now 20230210-5 all [installed] firmware-samsung/stable,now 20230210-5 all [installed] firmware-siano/stable,now 20230210-5 all [installed] firmware-sof-signed/stable,now 2.2.4-1 all [installed] firmware-ti-connectivity/stable,now 20230210-5 all [installed] firmware-zd1211/stable,now 1:1.5-10 all [installed] hdmi2usb-fx2-firmware/stable,now 0.0.0~git20151225-3 all [installed] Code: Select all$ lspci -knn 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM Controller [1458:5000] Kernel driver in use: hsw_uncore 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [1458:5000] Kernel driver in use: pcieport 00:14.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB xHCI Controller [8086:8cb1] Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family USB xHCI Controller [1458:5007] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 9 Series Chipset Family ME Interface #1 [8086:8cba] Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family ME Interface [1458:1c3a] Kernel driver in use: mei_me Kernel modules: mei_me 00:1a.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2 [8086:8cad] Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family USB EHCI Controller [1458:5006] Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1b.0 Audio device [0403]: Intel Corporation 9 Series Chipset Family HD Audio Controller [8086:8ca0] Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family HD Audio Controller [1458:a182] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 [8086:8c90] (rev d0) Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family PCI Express Root Port 1 [1458:5001] Kernel driver in use: pcieport 00:1c.2 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 3 [8086:8c94] (rev d0) Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family PCI Express Root Port 3 [1458:5001] Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 [8086:8c96] (rev d0) Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family PCI Express Root Port 4 [1458:5001] Kernel driver in use: pcieport 00:1d.0 USB controller [0c03]: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1 [8086:8ca6] Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family USB EHCI Controller [1458:5006] Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1f.0 ISA bridge [0601]: Intel Corporation Z97 Chipset LPC Controller [8086:8cc4] Subsystem: Gigabyte Technology Co., Ltd Z97 Chipset LPC Controller [1458:5001] Kernel driver in use: lpc_ich Kernel modules: lpc_ich 00:1f.2 SATA controller [0106]: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode] [8086:8c82] Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family SATA Controller [AHCI Mode] [1458:b005] Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 9 Series Chipset Family SMBus Controller [8086:8ca2] Subsystem: Gigabyte Technology Co., Ltd 9 Series Chipset Family SMBus Controller [1458:5001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] Kernel modules: nvidia 01:00.1 Audio device [0403]: NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX] [10de:0fbc] (rev a1) Subsystem: NVIDIA Corporation GM107 High Definition Audio Controller [GeForce 940MX] [10de:1097] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000] Kernel driver in use: r8169 Kernel modules: r8169 04:00.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev 41) Subsystem: Gigabyte Technology Co., Ltd 82801 PCI Bridge [1458:8892] 05:00.0 Ethernet controller [0200]: Qualcomm Atheros AR2417 Wireless Network Adapter [AR5007G 802.11bg] [168c:001d] (rev 01) Subsystem: Qualcomm Atheros AR2417 Wireless Network Adapter [AR5007G 802.11bg] [168c:2055] Kernel driver in use: ath5k Kernel modules: ath5k Code: Select all$ lsmod | sort acpi_pad 184320 0 aesni_intel 393216 0 ahci 49152 4 async_memcpy 20480 2 raid456,async_raid6_recov async_pq 20480 2 raid456,async_raid6_recov async_raid6_recov 24576 1 raid456 async_tx 20480 5 async_pq,async_memcpy,async_xor,raid456,async_raid6_recov async_xor 20480 3 async_pq,raid456,async_raid6_recov at24 28672 0 ath 36864 1 ath5k ath5k 167936 0 autofs4 53248 2 binfmt_misc 24576 1 blake2b_generic 20480 0 btrfs 1789952 0 button 24576 0 cdrom 81920 1 sr_mod cfg80211 1142784 3 ath,ath5k,mac80211 chacha_x86_64 28672 1 libchacha20poly1305 configfs 57344 1 coretemp 20480 0 crc16 16384 1 ext4 crc32c_generic 16384 0 crc32c_intel 24576 7 crc32_pclmul 16384 0 crc64 20480 1 crc64_rocksoft crc64_rocksoft 20480 1 t10_pi crc_t10dif 20480 1 t10_pi crct10dif_common 16384 3 crct10dif_generic,crc_t10dif,crct10dif_pclmul crct10dif_generic 16384 0 crct10dif_pclmul 16384 1 cryptd 28672 2 crypto_simd,ghash_clmulni_intel crypto_simd 16384 1 aesni_intel curve25519_x86_64 36864 1 wireguard dm_mod 184320 0 drm 614400 1 drm_kms_helper drm_kms_helper 208896 0 efi_pstore 16384 0 ehci_hcd 102400 1 ehci_pci ehci_pci 20480 0 enclosure 20480 1 ses evdev 28672 9 ext4 983040 3 fan 20480 0 fuse 176128 5 ghash_clmulni_intel 16384 0 hid 159744 2 usbhid,hid_generic hid_generic 16384 0 i2c_i801 36864 0 i2c_smbus 20480 1 i2c_i801 intel_cstate 20480 0 intel_pmc_bxt 16384 1 iTCO_wdt intel_powerclamp 20480 0 intel_rapl_common 32768 1 intel_rapl_msr intel_rapl_msr 20480 0 intel_uncore 217088 0 ip6_udp_tunnel 16384 1 wireguard ip_tables 36864 0 irqbypass 16384 1 kvm iTCO_vendor_support 16384 1 iTCO_wdt iTCO_wdt 16384 0 jbd2 167936 1 ext4 kvm 1146880 1 kvm_intel kvm_intel 380928 0 ledtrig_audio 16384 1 snd_hda_codec_generic libahci 49152 1 ahci libarc4 16384 1 mac80211 libata 401408 2 libahci,ahci libchacha 16384 1 chacha_x86_64 libchacha20poly1305 16384 1 wireguard libcrc32c 16384 4 nf_conntrack,btrfs,nf_tables,raid456 libcurve25519_generic 49152 2 curve25519_x86_64,wireguard libphy 180224 3 r8169,mdio_devres,realtek linear 20480 0 loop 32768 0 lp 20480 0 lpc_ich 28672 0 mac80211 1175552 1 ath5k mbcache 16384 1 ext4 mdio_devres 16384 1 r8169 md_mod 192512 6 raid1,raid10,raid0,linear,raid456,multipath mei 159744 3 mei_hdcp,mei_me mei_hdcp 24576 0 mei_me 53248 1 Module Size Used by multipath 20480 0 nf_conntrack 188416 1 xt_connmark nf_defrag_ipv4 16384 1 nf_conntrack nf_defrag_ipv6 24576 1 nf_conntrack nfnetlink 20480 2 nft_compat,nf_tables nf_tables 303104 661 nft_compat nft_compat 20480 116 overlay 163840 0 parport 73728 3 parport_pc,lp,ppdev parport_pc 40960 1 pcspkr 16384 0 poly1305_x86_64 28672 1 libchacha20poly1305 ppdev 24576 0 qrtr 49152 4 r8169 94208 0 raid0 24576 0 raid10 65536 0 raid1 53248 0 raid456 180224 0 raid6_pq 122880 4 async_pq,btrfs,raid456,async_raid6_recov rapl 20480 0 realtek 36864 1 rfkill 36864 2 cfg80211 scsi_common 16384 6 scsi_mod,usb_storage,uas,libata,sg,sr_mod scsi_mod 286720 8 ses,scsi_transport_sas,sd_mod,usb_storage,uas,libata,sg,sr_mod scsi_transport_sas 49152 1 ses sd_mod 65536 5 ses 20480 0 sg 40960 0 sha1_ssse3 32768 0 sha256_ssse3 32768 0 sha512_generic 16384 1 sha512_ssse3 sha512_ssse3 49152 0 snd 126976 19 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm snd_compress 28672 1 snd_soc_core snd_hda_codec 184320 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hda_codec_generic 98304 1 snd_hda_codec_realtek snd_hda_codec_hdmi 81920 1 snd_hda_codec_realtek 172032 1 snd_hda_core 122880 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_hda_intel 57344 5 snd_hwdep 16384 1 snd_hda_codec snd_intel_dspcfg 36864 1 snd_hda_intel snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg snd_pcm 159744 8 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_soc_rt5640,snd_compress,snd_soc_core,snd_hda_core snd_soc_core 352256 1 snd_soc_rt5640 snd_soc_rl6231 20480 1 snd_soc_rt5640 snd_soc_rt5640 147456 0 snd_timer 49152 1 snd_pcm soundcore 16384 1 snd sr_mod 28672 0 t10_pi 16384 1 sd_mod uas 32768 0 udp_tunnel 24576 1 wireguard usb_common 16384 3 xhci_hcd,usbcore,ehci_hcd usbcore 348160 7 xhci_hcd,ehci_pci,usbhid,usb_storage,ehci_hcd,xhci_pci,uas usbhid 65536 0 usb_storage 81920 1 uas vboxdrv 602112 2 vboxnetadp,vboxnetflt vboxnetadp 28672 0 vboxnetflt 32768 0 video 65536 0 watchdog 45056 1 iTCO_wdt wireguard 98304 0 wmi 36864 1 video x86_pkg_temp_thermal 20480 0 xhci_hcd 315392 1 xhci_pci xhci_pci 24576 0 xor 24576 2 async_xor,btrfs x_tables 61440 6 nft_compat,xt_tcpudp,xt_comment,xt_connmark,ip_tables,xt_mark xt_comment 16384 96 xt_connmark 16384 12 xt_mark 16384 8 xt_tcpudp 20480 0 zstd_compress 294912 1 btrfs Code: Select all$ apt list "linux-headers*" Listing... Done linux-headers-6.1.0-11-amd64/stable-security 6.1.38-4 amd64 linux-headers-6.1.0-11-cloud-amd64/stable-security 6.1.38-4 amd64 linux-headers-6.1.0-11-common-rt/stable-security 6.1.38-4 all linux-headers-6.1.0-11-common/stable-security 6.1.38-4 all linux-headers-6.1.0-11-rt-amd64/stable-security 6.1.38-4 amd64 linux-headers-6.1.0-12-amd64/stable-security,now 6.1.52-1 amd64 [installed,automatic] linux-headers-6.1.0-12-cloud-amd64/stable-security 6.1.52-1 amd64 linux-headers-6.1.0-12-common-rt/stable-security 6.1.52-1 all linux-headers-6.1.0-12-common/stable-security,now 6.1.52-1 all [installed,automatic] linux-headers-6.1.0-12-rt-amd64/stable-security 6.1.52-1 amd64 linux-headers-6.1.0-15-amd64/stable 6.1.66-1 amd64 linux-headers-6.1.0-15-cloud-amd64/stable 6.1.66-1 amd64 linux-headers-6.1.0-15-common-rt/stable 6.1.66-1 all linux-headers-6.1.0-15-common/stable 6.1.66-1 all linux-headers-6.1.0-15-rt-amd64/stable 6.1.66-1 amd64 linux-headers-6.1.0-16-amd64/stable-updates 6.1.67-1 amd64 linux-headers-6.1.0-16-cloud-amd64/stable-updates 6.1.67-1 amd64 linux-headers-6.1.0-16-common-rt/stable-updates 6.1.67-1 all linux-headers-6.1.0-16-common/stable-updates 6.1.67-1 all linux-headers-6.1.0-16-rt-amd64/stable-updates 6.1.67-1 amd64 linux-headers-6.1.0-17-amd64/stable-security 6.1.69-1 amd64 linux-headers-6.1.0-17-cloud-amd64/stable-security 6.1.69-1 amd64 linux-headers-6.1.0-17-common-rt/stable-security 6.1.69-1 all linux-headers-6.1.0-17-common/stable-security 6.1.69-1 all linux-headers-6.1.0-17-rt-amd64/stable-security 6.1.69-1 amd64 linux-headers-6.1.0-18-amd64/stable 6.1.76-1 amd64 linux-headers-6.1.0-18-cloud-amd64/stable 6.1.76-1 amd64 linux-headers-6.1.0-18-common-rt/stable 6.1.76-1 all linux-headers-6.1.0-18-common/stable 6.1.76-1 all linux-headers-6.1.0-18-rt-amd64/stable 6.1.76-1 amd64 linux-headers-6.1.0-20-amd64/stable-security,now 6.1.85-1 amd64 [installed,automatic] linux-headers-6.1.0-20-cloud-amd64/stable-security 6.1.85-1 amd64 linux-headers-6.1.0-20-common-rt/stable-security 6.1.85-1 all linux-headers-6.1.0-20-common/stable-security,now 6.1.85-1 all [installed,automatic] linux-headers-6.1.0-20-rt-amd64/stable-security 6.1.85-1 amd64 linux-headers-amd64/stable-security,now 6.1.85-1 amd64 [installed] linux-headers-cloud-amd64/stable-security 6.1.85-1 amd64 linux-headers-rt-amd64/stable-security 6.1.85-1 amd64 Code: Select all$ sudo grep non-free /etc/apt/sources.list # deb cdrom:[Debian GNU/Linux 12 _Bookworm_ - Official Snapshot amd64 LIVE/INSTALL Binary 20230610-08:51]/ bookworm main non-free-firmware deb http://deb.debian.org/debian/ bookworm contrib main non-free-firmware deb-src http://deb.debian.org/debian/ bookworm contrib main non-free-firmware deb http://security.debian.org/debian-security bookworm-security contrib main non-free-firmware deb-src http://security.debian.org/debian-security bookworm-security contrib main non-free-firmware deb http://deb.debian.org/debian/ bookworm-updates contrib main non-free-firmware deb-src http://deb.debian.org/debian/ bookworm-updates contrib main non-free-firmware Code: Select all$ dpkg -l linux-image* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-===================================-============-============-=================================> un linux-image <none> <none> (no description available) rc linux-image-6.1.0-11-amd64 6.1.38-4 amd64 Linux 6.1 for 64-bit PCs (signed) un linux-image-6.1.0-11-amd64-unsigned <none> <none> (no description available) ii linux-image-6.1.0-12-amd64 6.1.52-1 amd64 Linux 6.1 for 64-bit PCs (signed) un linux-image-6.1.0-12-amd64-unsigned <none> <none> (no description available) ii linux-image-6.1.0-20-amd64 6.1.85-1 amd64 Linux 6.1 for 64-bit PCs (signed) un linux-image-6.1.0-20-amd64-unsigned <none> <none> (no description available) rc linux-image-6.1.0-9-amd64 6.1.27-1 amd64 Linux 6.1 for 64-bit PCs (signed) un linux-image-6.1.0-9-amd64-unsigned <none> <none> (no description available) ii linux-image-amd64 6.1.85-1 amd64 Linux for 64-bit PCs (meta-packag> un linux-image-generic <none> <none> (no description available) | 5648] NVRM: The NVIDIA GPU 0000:01:00.0 (PCI ID: 10de:13ba) NVRM: installed in this system is not supported by open NVRM: nvidia.ko because it does not include the required GPU NVRM: System Processor (GSP). NVRM: Please see the 'Open Linux Kernel Modules' and 'GSP NVRM: Firmware' sections in the driver README, available on NVRM: the Linux graphics driver download page at NVRM: www.nvidia.com. The open dkms kernel module supports cards RTX 2000 series and newer, install the nvidia kernel dkms module instead. |
In the "Power Manager"/"System" setting, I have "When Laptop lid is closed" set to "Lock Screen" for both "On Battery" and "Plugged in". It sure does lock when I close the lid but if I leave the lid closed for a longer period (didn't exactly measure it but more than 15 minutes or so), I don't get the Login screen back when I open the lid. Instead it's blank and no matter what I do, I can't get to bring it alive. The only option seems to be hard reboot. It's very annoying to say the least. I searched around and couldn't find anything that stands out. lshw output is attached. Any help will be appreciated. Thank you! | Likely your machine is going into sleep/suspend mode after a while, and it is not working properly for you. Check all the 'Power Manager' settings, and make sure to set: 'Put to sleep after' = Never |
Hi, I believe that I understood this message correctly: W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 I've tried to install firmware-linux package, but the warning is still there (right after install). I'm not familiar with the problem or even with its nature, so, please be patient and explain in more details if you answer I've found this problem by looking the messages log, where there was the line: r8169 0000:07:00.0: eth0: unable to load firmware patch rtl_nic/rtl8168e-1.fw (-2) Then I read in another place that the firmware-linux package is meant to contain the said patch, but it looks like it's not there. Where is it? | You will need firmware-realtek from backports or upgrade to wheezy. http://packages.debian.org/squeeze-back ... re-realtek |
Hi, This is on a fresh install of Debian 12.0 on a Fujitsu LifeBook U series (Alder Lake), with xfce4. The sound card is a Realtek ACL257. My internal microphone is detected, but does not seem to work. I can see it in `xfce4-pulseaudio-plugin` and in `alsamixer`, but it just does not record anything. Tried `arecord`, zoom and an online microphone test tool. None of them recorded any sound. The speakers work fine on the other hand. As far as I can tell all the drivers are installed. Am I maybe missing a setting somewhere? Any help is appreciated. Thanks | Great you got it sorted. Please edit the title of your first post to add prefix [Solved} so it may help others searching for the same solution. |
4/16/2013 Edit: Just on a whim, I thought of trying simple-scan and it works like a charm now in spite of sane-find-scanner -v -v -f continuing to say " # No USB scanners found." as noted here. See "Edit" at top of my followup post for the real solution to the initial scan failures prompting this post. But now I wonder: How is this possible Code: Select allfind /dev -name "*scan*" -printreturns nothing And that is probably why sane-find-scanner thinks there is nothing also . . . _____End-of-Edit It's a nice, uncomplicated piece of hardware, and I feel like I'm just missing some small piece of the configuration puzzle to get the scanning function to work. I read that Panasonic may not be the best Linux supporter, but they have put out a .deb package that's supposed to work with sane for this model, so it seems like there is hope First lsusb appears to recognize something relavent:Code: Select allBus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 04b4:0001 Cypress Semiconductor Corp. Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 04da:0f0b Panasonic (Matsushita) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub I have installed the two driver packages provided by Panasonic for each function (Printer Driver and Scanner Driver). However, when I do "ls -al /dev/usb" all I get is the printer:Code: Select alldrwxr-xr-x 2 root root 60 Apr 14 18:13 . drwxr-xr-x 15 root root 3520 Apr 14 18:13 .. crw-rw---- 1 root lp 180, 0 Apr 14 18:13 lp0 No scanners are shown, which may explain why sane doesn't find anything. "sane-find-scanner -v -f" yields:Code: Select allThis is sane-find-scanner from sane-backends 1.0.21 # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Access to resource has been denied) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Access to resource has been denied) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking /dev/usbscanner14... failed to open (Invalid argument) checking /dev/usbscanner15... failed to open (Invalid argument) # No USB scanners found. If you expected something different, make sure that # you have loaded a kernel driver for your USB host controller and have setup # the USB system correctly. See man sane-usb for details. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. done After installation of the Panasonic ScanDriver package the following updates to the sane library were in place:Code: Select allnick@debhome:~$ ls -al /usr/lib/sane/*pana* lrwxrwxrwx 1 root root 20 Apr 14 18:04 /usr/lib/sane/libsane-panamfs.so -> libsane-panamfs.so.1 lrwxrwxrwx 1 root root 24 Apr 14 18:04 /usr/lib/sane/libsane-panamfs.so.1 -> libsane-panamfs.so.1.0.1 -rwxr-xr-x 1 root root 331651 Aug 8 2012 /usr/lib/sane/libsane-panamfs.so.1.0.1 nick@debhome:~$ Also, /etc/sane.d/panamfs.conf was created and "panamfs" shows up in /etc/sane.d/dll.conf. The contents of panamfs.conf isCode: Select all# # Panasonic Multi-Function Station scanners DBG_LEVEL 0 /dev/scanner # KX-MC6000 usb 0x04da 0x1509 # KX-MC6015 # KX-MC6020 usb 0x04da 0x150a # KX-MC6040 usb 0x04da 0x150b # KX-MC6255 # KX-MC6260 usb 0x04da 0x1511 # DP-MC210 usb 0x04da 0x0f05 # KX-MB3000/DP-MB300 series usb 0x04da 0x0f06 # KX-MB2000 series usb 0x04da 0x0f07 # KX-MB2060 series usb 0x04da 0x0f08 # KX-MC6280N usb 0x04da 0x0f09 # KX-MB1500 series usb 0x04da 0x0f0b # Network # # to auto seach scane # net autodiscovery # # # net 192.168.1.123 # net autodiscovery network KX-MC6 network DP-MC2 network KX-MB3 network DP-MB3 network KX-MB2 network KX-MB1 Since it appears that sane-find-scanner looks for usb scanners in /dev/usb, not /dev, I tried changing /dev/scanner to /dev/usb/scanner or /dev/usb/scanner0 with no success Perhaps there is some problem recognizing two separate items on the same usb device? Thanks in advance for all your advice. Nick | 4/16/2013 Edit: Fixing /lib/udev/rules.d/10-libsane.rules as shown below did the trick, though why sane-find-scanner continues to conclude there are no USB scanners (as detailed in the rest of this post) remains a mystery Quick Update: sane-find-scanner -v -v -f actually does see both scanner and printer on USB device 001:003:Code: Select all<device descriptor of 0x04da/0x0f0b at 001:003 (Panasonic KX-MB1520)> bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x04DA idProduct 0x0F0B bcdDevice 1.00 iManufacturer 1 (Panasonic) iProduct 2 (KX-MB1520) iSerialNumber 3 (01DX02022533) bNumConfigurations 1 <configuration 0> bLength 9 bDescriptorType 2 wTotalLength 69 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 4 (Default Configurataion) bmAttributes 192 (Self-powered) MaxPower 2 mA <interface 0> <altsetting 0> bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 5 bInterfaceClass 6 bInterfaceSubClass 1 bInterfaceProtocol 255 iInterface 6 (Scanner USB Interface) <endpoint 0> bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 32 bInterval 11 ms bRefresh 0 bSynchAddress 0 <endpoint 1> bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 <endpoint 2> bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 <endpoint 3> bLength 7 bDescriptorType 5 bEndpointAddress 0x05 (out 0x05) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 <endpoint 4> bLength 7 bDescriptorType 5 bEndpointAddress 0x86 (in 0x06) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 <interface 1> <altsetting 0> bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 7 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 5 (Printer USB Interface) <endpoint 0> bLength 7 bDescriptorType 5 bEndpointAddress 0x04 (out 0x04) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 but then still says:Code: Select all # No USB scanners found. If you expected something different, make sure that # you have loaded a kernel driver for your USB host controller and have setup # the USB system correctly. See man sane-usb for details. So on some level the scanner is detected, but then sane just won't do anything with it I also realized that /lib/udev/rules.d/10-libsane.rules needed to have this added to it:Code: Select all# Panasonic MFS scanners ATTRS{idVendor}=="04da", ATTRS{idProduct}=="0f0b", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes" EDIT: In stretch, the file is /lib/udev/rules.d/60-libsane.rules Finally, for the record, especally if anybody else is searching around for dirvers and instructions for this machine, they are here. It took me and hour, and only after some very un-obvious google keyword-entry, to stumble accross it. Panasonic really doesn't seem to want anyone to find it, even though they went to the trouble of putting some half-way decent deb and rpm packages together and posting them on this website |
I have an old Del 630. It has allways worked out of the box with Debian. However after installing bookworm it was able to connect to the wifi, but not getting internet. Determining it was a broadcom wifi adapter I followed this guide https://wiki.debian.org/wl However doing this I somehow managed to complete turn wifi off. Now there is only ethernet in the networkmanager. Can I turn the wifi on again? Thanks | Hello, What is the output of the following command ? Code: Select alllspci -vnn -d ::02xx |
Hi! I've installed Debian 12 for the first time, and I cannot use it properly because both Ethernet and WiFi have a 70%+ packet loss and I'm struggling to fix this issue. I've already made sure that the problem is not DNS related by using Code: Select allping -c3 8.8.8.8 Here's some info that might be useful to solve this issue: iwlwifi kernel logs: Code: Select alluser@debian:~$ sudo dmesg | grep iwlwifi [sudo] password di user: [ 19.968224] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) [ 19.977397] iwlwifi 0000:00:14.3: firmware: direct-loading firmware iwlwifi-so-a0-hr-b0-72.ucode [ 19.977424] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver [ 19.977460] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 [ 19.978185] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 19.978271] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 19.978327] iwlwifi 0000:00:14.3: loaded firmware version 72.daa05125.0 so-a0-hr-b0-72.ucode op_mode iwlmvm [ 20.046826] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x370 [ 20.164069] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100 [ 20.231526] iwlwifi 0000:00:14.3: base HW address: f4:46:37:ac:7f:0b [ 20.307951] iwlwifi 0000:00:14.3 wlo1: renamed from wlan0 lspci output: Code: Select all00:00.0 Host bridge: Intel Corporation Device 4649 (rev 02) 00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x16 Controller #1 (rev 02) 00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT1 [UHD Graphics] (rev 0c) 00:04.0 Signal processing controller: Intel Corporation Alder Lake Innovation Platform Framework Processor Participant (rev 02) 00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #0 (rev 02) 00:06.2 PCI bridge: Intel Corporation 12th Gen Core Processor PCI Express x4 Controller #2 (rev 02) 00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI Express Root Port #0 (rev 02) 00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor Gaussian & Neural Accelerator (rev 02) 00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01) 00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB Controller (rev 02) 00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI #0 (rev 02) 00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI Host Controller (rev 01) 00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01) 00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi (rev 01) 00:15.0 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #0 (rev 01) 00:15.2 Serial bus controller: Intel Corporation Alder Lake PCH Serial IO I2C Controller #2 (rev 01) 00:16.0 Communication controller: Intel Corporation Alder Lake PCH HECI Controller (rev 01) 00:1f.0 ISA bridge: Intel Corporation Alder Lake PCH eSPI Controller (rev 01) 00:1f.3 Audio device: Intel Corporation Alder Lake PCH-P High Definition Audio Controller (rev 01) 00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 01) 00:1f.5 Serial bus controller: Intel Corporation Alder Lake-P PCH SPI Controller (rev 01) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (16) I219-LM (rev 01) 01:00.0 VGA compatible controller: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GA106 High Definition Audio Controller (rev a1) 02:00.0 Non-Volatile memory controller: Intel Corporation SSD 670p Series [Keystone Harbor] (rev 03) 03:00.0 Non-Volatile memory controller: Shenzhen Longsys Electronics Co., Ltd. Lexar NM620 NVME SSD (DRAM-less) (rev 01) I'm running on a fresh installation of Debian 12 with Linux 6.1.0-20-amd64. Hope you can help me! I wanted to switch to a more stable distribution, but it's the first time I've encountered such an issue with my laptop. Thanks in advance! ---- SOLVED ---- I'm ashamed to say that I wasted 3 times complaining about my hardware & my software only to discover that it was my housing provider rate limiting my MAC address... I'm really speechless. I want to thank everybody that took their time to read & maybe think about a possible solution to such issue. | Can you see related errors in journal (of systemd)? |
SOLVED ! Need to remove libcamera and use LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4l/v4lconvert.so.0 cheese. Hello I have Asus Laptop (PRO36S) issued around 2011. I remember around June 2023 (I used sid) I got upside down webcam and still solveable by using : Code: Select allLD_PRELOAD=/usr/lib/x86_64-linux-gnu/libv4lconvert.so.0 cheese. Going back until now, The LD_PRELOAD way is no longer works, even when I decided to move to ubuntu, It's still doesn't work. I have a thought that maybe I can use v4l-utils from June 2023 and maybe uvcvideo driver from that time. Is it possible ? Thanks. | Hello, Perhaps this could be useful: LD_PRELOAD does not work and LD_DEBUG shows nothing Hope this helps. |
Hi everyone! I'm a new user getting started in Debian. I have an old Sony Vaio E series laptop that I've erased the current Windows 10 and giving it a new life with Debian 12. I followed along the installation instructions to the last step where it asks me to choose which desktop environment to install. Because I want a server environment, I only checked 3 boxes: web server, ssh server and standard system utilities. After that, I chose Yes to install GRUB as Debian is the only OS on my machine. Then at the last step, I chose 'reboot', unplug my USB and it did reboot into a terminal screen asking for my login information but while I was remembering my login credentials for a few seconds it has turned off and I can't find a way to reboot. I've tried the power button along with other buttons and it does not respond. Is there anyway I could reboot the machine again so maybe I can try to reinstall Debian with a desktop environment? Please help me because I've searched through the forum and google but couldn't find a working answer for my situation. | This sure sounds like a hardware issue. Are you sure battery is charged and external power supply is working? |
Hello! I've been using the Spanish (latin american) keyboard layout on my Debian 12 xfce for many months now without a problem. Same with the korean layout. Everything fit with my keyboard, everything worked great. However, today when after the customary apt update, apt upgrade, the accent key does not work, whenever I press it nothing happens, it's as if the key doesn't exist. And the korean layout doesn't work at all - none of the keys work. I have tried changing the layout to english us for example, and the same physical key works great (so it isn't a physical problem with my keyboard). I have also tried all the variations of the Spanish Latin American layout available in xfce, and still, none of them have working accent keys. I'm assuming there is some kind of problem with iBus and the things that were upgraded today. I have checked all the settings in iBus and everything is as it was before this problem. Could this be some kind of bug? Everything worked great before the update. Things I have tried: - Trying other layouts to discard possible physical problems with my keyboard - Changing the layout in both iBus and the keyboard preferences - Making sure the ibus-daemon --xim is running (it is) | Hello, There seems to be a problem with the latest glib2.0 security update (2.74.6-2+deb12u1), see this topic. |
Hi, Since I changed the computer (now I have an Acer nitro n50-640), it crashes once or twice a day, for no apparent reason. The mouse stops and the keyboard doesn't respond, everything is blocked and there is no other option but to press the power button. It always happens when I'm moving the mouse, so I've already tried with another mouse, changing the port, but the problem remains. It doesn't seem to depend on the programs that are running. And when it happens there is nothing to do, neither mouse nor keyboard responds, although it seems to continue with the tasks it had active. Any idea what could be the problem? (I have Debian 12.) Thanks in advance! | Hello, It looks like an nvidia equipped computer: Nitro N50-640 Gaming Desktop Computer Just a guess: it could be the display server (Wayland vs. Xorg) or the kernel module that controls the video card (nouveau vs. nvidia). You can verify using the command (the inxi package must be installed): Code: Select all$ inxi -Gaz |
Hello, I've been experiencing an issue on my desktop PC for a while now, which is that around half the time (it seems random) when I boot my PC, the mouse doesn't respond unless I unplug and replug my mouse from the USB port. This is very inconvenient to have to do, as my PC is under the desk, and the mouse is plugged into the back. My mouse is the Logitech G305 wireless mouse. Thanks very much in advance for any advice. | Assuming its not the battery, can you run Code: Select all$ usbreset Output should show your mouse: Code: Select allUsage: usbreset PPPP:VVVV - reset by product and vendor id usbreset BBB/DDD - reset by bus and device number usbreset "Product" - reset by product name Devices: Number 001/007 ID 17ef:602e USB Optical Mouse Next time the mouse isn't responding, run Code: Select all# usbreset "USB Optical Mouse" Edit: change for the actual name of your device, obviously. (or use product/vendor or bus/device ID). If that works, it is possible to autorun the command after suspend. See: https://askubuntu.com/questions/1044988 ... untu-18-04 |
Hello, I have an hp deskjet 3050 printer and scanner. I want to scan some documents but its not detected with the document scanner that comes with the cinnamon DE | You don't actually need hplip for older scanners like this (or the newer ones, because they are driverless). Got mine working without the bloat: http://dontsurfinthenude.blogspot.com/2 ... inter.html? |
Hi, I have a HP Microserver Gen 10 (AMD Opteron(tm) X3421 APU) freshly installed with Debian bookworm (6.1.0-21-amd64 /Debian 6.1.90-1 (2024-05-03) x86_64) with 4x WD RED SATA 6TB Disks and one WD Blue 250GB SATA SSD I am entirely unable to interact with the four disks in the front bays, however I can see the disk I'm booting from on the discrete SATA port. - I have put them in JBOD in the controller: (01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2 4-port SATA 6 Gb/s RAID Controller (rev 11) I see all the disks in BIOS and in the F11 "Boot menu" Disks accessible without fault when using TrueNAS (BSD) The following output can be seen whilst booting or if manually initiating a scan (echo "- - -" > /sys/class/scsi_host/host${i}/scan): Code: Select all[ 2.435457] scsi host1: ahci [ 2.435981] scsi host2: ahci [ 2.436363] scsi host3: ahci [ 2.436623] usb: port power management may be unreliable [ 2.437047] scsi host4: ahci [ 2.437608] scsi host5: ahci [ 2.438027] scsi host6: ahci [ 2.438403] scsi host7: ahci [ 2.438797] scsi host8: ahci [ 2.439008] ata2: SATA max UDMA/133 abar m2048@0xfea40000 port 0xfea40100 irq 34 [ 2.439073] ata3: SATA max UDMA/133 abar m2048@0xfea40000 port 0xfea40180 irq 34 [ 2.439134] ata4: SATA max UDMA/133 abar m2048@0xfea40000 port 0xfea40200 irq 34 [ 2.439194] ata5: SATA max UDMA/133 abar m2048@0xfea40000 port 0xfea40280 irq 34 [ 2.439253] ata6: SATA max UDMA/133 abar m2048@0xfea40000 port 0xfea40300 irq 34 [ 2.439318] ata7: SATA max UDMA/133 abar m2048@0xfea40000 port 0xfea40380 irq 34 [ 2.439378] ata8: SATA max UDMA/133 abar m2048@0xfea40000 port 0xfea40400 irq 34 [ 2.439437] ata9: SATA max UDMA/133 abar m2048@0xfea40000 port 0xfea40480 irq 34 [ 2.467995] tg3 0000:02:00.1 enp2s0f1: renamed from eth1 [ 2.507963] tg3 0000:02:00.0 enp2s0f0: renamed from eth0 [ 2.683860] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 2.756502] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 2.756625] ata7: SATA link down (SStatus 0 SControl 310) [ 2.756732] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 2.756821] ata6: SATA link down (SStatus 0 SControl 310) [ 2.756900] ata8: SATA link down (SStatus 0 SControl 310) [ 2.840419] usb 1-1: New USB device found, idVendor=0438, idProduct=7900, bcdDevice= 0.18 [ 2.840492] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 2.842082] hub 1-1:1.0: USB hub found [ 2.843049] hub 1-1:1.0: 4 ports detected [ 2.895894] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 2.897948] ata1.00: ATA-9: WDC WDS250G1B0A-00H9H0, X41100WD, max UDMA/133 [ 2.898067] ata1.00: 488397168 sectors, multi 1: LBA48 NCQ (depth 32), AA [ 2.898775] ata1.00: Features: Dev-Sleep [ 2.901601] ata1.00: configured for UDMA/133 [ 2.902112] scsi 0:0:0:0: Direct-Access ATA WDC WDS250G1B0A- 00WD PQ: 0 ANSI: 5 [ 2.935875] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3.115885] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3.131869] usb 1-1.3: new low-speed USB device number 3 using ehci-pci [ 3.246378] usb 1-1.3: New USB device found, idVendor=045e, idProduct=07f8, bcdDevice= 3.00 [ 3.246449] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.246502] usb 1-1.3: Product: Wired Keyboard 600 [ 3.246546] usb 1-1.3: Manufacturer: Microsoft [ 3.327878] usb 1-1.4: new low-speed USB device number 4 using ehci-pci [ 3.331077] ata9.00: ATAPI: MARVELL VIRTUAL, 1.09, max UDMA/66 [ 3.331230] ahci 0000:01:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0002 address=0xdff7d840 flags=0x0050] [ 3.355883] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 3.440211] usb 1-1.4: New USB device found, idVendor=0001, idProduct=0000, bcdDevice= 1.00 [ 3.440285] usb 1-1.4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 3.440342] usb 1-1.4: Product: MEC0003 [ 7.831925] ata2.00: qc timeout after 5000 msecs (cmd 0xec) [ 8.087905] ata3.00: qc timeout after 5000 msecs (cmd 0xec) [ 8.332622] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 8.343863] ata4.00: qc timeout after 5000 msecs (cmd 0xec) [ 8.587874] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 8.599898] ata5.00: qc timeout after 5000 msecs (cmd 0xec) [ 8.599976] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 8.844084] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 8.916128] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 9.148215] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 9.404536] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 9.660513] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 18.583962] ata9.00: qc timeout after 15000 msecs (cmd 0xef) [ 19.083977] ata9.00: failed to set xfermode (err_mask=0x4) [ 19.095849] ata5.00: qc timeout after 10000 msecs (cmd 0xec) [ 19.095924] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 19.095992] ata5: limiting SATA link speed to 3.0 Gbps [ 19.351860] ata2.00: qc timeout after 10000 msecs (cmd 0xec) [ 19.412472] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 320) [ 19.607848] ata3.00: qc timeout after 10000 msecs (cmd 0xec) [ 19.852634] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 19.852709] ata2: limiting SATA link speed to 3.0 Gbps [ 19.863864] ata4.00: qc timeout after 10000 msecs (cmd 0xec) [ 19.900158] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 20.108601] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 20.108677] ata3: limiting SATA link speed to 3.0 Gbps [ 20.363904] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 20.363980] ata4: limiting SATA link speed to 3.0 Gbps [ 20.668444] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 320) [ 20.924129] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 320) [ 21.180562] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 320) [ 24.983935] ata9.00: qc timeout after 5000 msecs (cmd 0xa1) [ 25.484047] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 25.484116] ata9.00: revalidation failed (errno=-5) [ 26.300547] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 36.503933] ata9.00: qc timeout after 10000 msecs (cmd 0xa1) [ 37.003884] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 37.003951] ata9.00: revalidation failed (errno=-5) [ 37.004003] ata9.00: disable device [ 38.320543] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 50.327906] ata5.00: qc timeout after 30000 msecs (cmd 0xec) [ 50.327983] ata5.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 50.644563] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 320) [ 52.375869] ata4.00: qc timeout after 30000 msecs (cmd 0xec) [ 52.375950] ata3.00: qc timeout after 30000 msecs (cmd 0xec) [ 52.376025] ata2.00: qc timeout after 30000 msecs (cmd 0xec) [ 52.876226] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 52.876309] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 52.876375] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 53.692622] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 320) [ 53.692726] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 320) [ 53.692831] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 320) Is there something I'm doing wrong here? I have verified as far as I can that the disks are JBOD, healthy (SMART) and usable in TrueNAS, however in Linux I'm unable to list them or interact with them at all. Grateful for any advice. M. | A bit old and supposedly *fixed* horkage, but mucking with (i.e. disabling) IOMMU and VTd (BIOS/kernel command-line) might still be worth a shot, at least in aid of diagnostics. |
After struggling a lot, I could finally install Debian 12 (Weekly) using ISO CD & Ethernet cable on MacbookPro 2019 with Intel & T2: I did the following: Code: Select all$ sudo iwconfig lo no wireless extensions. enx00e04c680318 no wireless extensions. $ lspci -nn | grep Network 05:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4364 802.11ac Wireless Network Adapter [14e4:4464] (rev 04) /etc/modprobe.d$ ls -l total 12 -rw-r--r-- 1 root root 180 Dec 26 2022 broadcom-sta-dkms.conf -rw-r--r-- 1 root root 127 Mar 7 10:33 dkms.conf -rw-r--r-- 1 root root 154 Mar 12 23:28 intel-microcode-blacklist.conf $ sudo apt-get install linux-image-$(uname -r) linux-image-6.6.15-amd64 is already the newest version (6.6.15-2). $ sudo apt-get install linux-headers-$(uname -r) $ sudo apt-get install broadcom-sta-dkms $ find /lib/modules/$(uname -r)/updates /lib/modules/6.6.15-amd64/updates /lib/modules/6.6.15-amd64/updates/dkms /lib/modules/6.6.15-amd64/updates/dkms/wl.ko.xz $ sudo modprobe -r b44 b43 b43legacy ssb brcmsmac bcma $ sudo modprobe wl $ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback $ nmcli networking on Added the PATH to modprobe in .bashrc file: export PATH=$PATH:/sbin:/usr/sbin Still the WiFi is NOT showing up. Any Help? I SOLVED it by following the steps in https://wiki.t2linux.org/guides/wifi-bluetooth/ Used commands (NOT scripts) | Moved to "Hardware" sub-forum. |
Hi everybody, I have an issue with the external display of my laptop (HP EliteBook 655 G10). The screen plugged (BenQ GW2470) is displaying very bad colors. Especially the greys that become nearly white. This make the use very complicated, because I cannot see the selected item, or some buttons are not visible. The problem is the same with Windows, and I fixed it by adjusting the contrast value on that display with the ADM driver software. I have spent a lot of time to set the contrast on my Debian, but I haven't found any solution (neither in the admgpu parameter, neither by importing the ICC profile of the windows). Do you have any idea to set the contrast ? Is it a missing feature of the AMD GPU driver ? I'm using Debian 12, wayland (even I have also tested Xorg). The GPU is a graphic car include in the AMD Ryzen 7730 U. modinfo amdgpu |grep filename filename: /lib/modules/6.1.0-18-amd64/kernel/drivers/gpu/drm/amd/amdgpu/amdgpu.ko | Don't neglect to try the adjustments on the monitor itself. |
Hi everyone, I need a graphic card for my server/desktop running under Debian 12 or SID. The computer is a virtualization server plus my desktop. Currently it run a very old Nvidia that freeze my GUI with legacy driver (both nouveau and proprietary). Here my requirements for the ideal card: Free driver Rock stable Enough powerfull for photo treatment, no video game Second hand In fact an intel card would do the job but recent standalone intel cards are expansive and too much sized for my usage. What about recent (< 5 years) AMD cards ? Thank you for your advice! | That means this is an older Xeon? I'd use any professional series (WX?) amd that fits your preference. I wouldn't use a triple fan OC gamer gadget. Let the cpu's do the work. Make sure you enable the slotted card and disable the onboard in the motherboard bios. |
I have a Acasis EC-7352 set to JBOD mode (Just Bunch Of Disks) so not trying to do hardware raid. (that's another story I abandoned) I have 2 identical WD Ultrastar HUS726T6TALE 6TB hard drives. I have (had) a working raid-1 that mounts and runs ok for a few weeks, seeming like earlier problems were in the past. Code: Select all$ fdisk -l Disk /dev/sdc: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: EC-73520 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: BF5C5010-71BF-4FE6-852F-1E01DD90C1E5 Device Start End Sectors Size Type /dev/sdc1 2048 11721043967 11721041920 5.5T Linux filesystem Disk /dev/sdd: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: EC-73521 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 4096 bytes / 33553920 bytes Disklabel type: gpt Disk identifier: CC9B7C53-E025-41EC-8BAB-877D884E190A Device Start End Sectors Size Type /dev/sdd1 2048 11721043967 11721041920 5.5T Linux filesystem $ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdc 8:32 0 5.5T 0 disk └─sdc1 8:33 0 5.5T 0 part └─md0 9:0 0 5.5T 0 raid1 /mnt/Acasis_RAID1_6Tb sdd 8:48 0 5.5T 0 disk └─sdd1 8:49 0 5.5T 0 part └─md0 9:0 0 5.5T 0 raid1 /mnt/Acasis_RAID1_6Tb $ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active raid1 sdc1[0] sdd1[1] 5860388864 blocks super 1.2 [2/2] [UU] bitmap: 0/44 pages [0KB], 65536KB chunk unused devices: <none> $ sudo mdadm -D /dev/md0 /dev/md0: Version : 1.2 Creation Time : Sat Jan 27 12:07:27 2024 Raid Level : raid1 Array Size : 5860388864 (5588.90 GiB 6001.04 GB) Used Dev Size : 5860388864 (5588.90 GiB 6001.04 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Intent Bitmap : Internal Update Time : Mon Jan 29 18:26:15 2024 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Consistency Policy : bitmap Name : roxy10-debian11-x64:0 (local to host roxy10-debian11-x64) UUID : 1e3f7f7e:23a5b75f:6f76abf5:88f5e704 Events : 21674 Number Major Minor RaidDevice State 0 8 33 0 active sync /dev/sdc1 1 8 49 1 active sync /dev/sdd1 $ df /dev/md0 5813107304 2543033168 2977054696 47% /mnt/Acasis_RAID1_6Tb $ lsusb Bus 003 Device 003: ID 214b:7250 Huasheng Electronics USB2.0 HUB Bus 003 Device 002: ID 214b:7250 Huasheng Electronics USB2.0 HUB $ cat /etc/debian_version 11.8 Today I powered it up, and tried to mount it, but it failed. After 5 minutes the computer froze up, no screen updates, no keyboard. Frozen. Rebooted, and looked at /var/log/messages Lots of errors, several call-Trace events. I repeated the sequence and confirmed it is repeatable. Code: Select all$ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : inactive sdc1[0](S) sdd1[1](S) 11720777728 blocks super 1.2 unused devices: <none> $ sudo mount /mnt/Acasis_RAID1_6Tb/ mount: /mnt/Acasis_RAID1_6Tb: can't read superblock on /dev/md0. I have clipped the 5 minutes of /var/log/messages showing the attempts to mount the drives, the multiple Call-Trace events, right up to the system freezing. It is long and repetitive, but contains useful back trace I hope. See zip file. Besides saying the enclosure firmware is garbage, despite being advertised as being compatible with linux, can anyone say why it crashes so badly? and anything I should try before tearing it apart and trying other solutions to get my data rescued? Thanks | Hello, Errors reported in the logs are low level errors (sata errors). You may move the disks to a working different enclosure to verify if they works or if it is the Acasis enclosure at fault. |
I've been using Debian (bookworm) with KDE plasma for a few months and have recently started having an issue with my laptop keyboard. Every time the system goes to sleep (whether it be automatically after a period of time, manually by using the Plasma sleep button, or by closing the laptop lid), upon waking again the laptop keyboard is completely unresponsive. It detects no input, including capslock. The only solution I've found is to restart the system. I've tried plugging in an external USB keyboard and that worked fine. Any advice is appreciated. inxi output: Code: Select allSystem: Kernel: 6.1.0-18-amd64 arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.5 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Laptop System: Dell product: Latitude 3570 v: N/A serial: <superuser required> Mobo: Dell model: 0YKP8M v: A04 serial: <superuser required> UEFI: Dell v: 1.24.0 date: 03/23/2022 Battery: ID-1: BAT0 charge: 52.2 Wh (97.8%) condition: 53.4/66.6 Wh (80.2%) CPU: Info: dual core model: Intel Core i5-6200U bits: 64 type: MT MCP cache: L2: 512 KiB Speed (MHz): avg: 544 min/max: 400/2800 cores: 1: 400 2: 700 3: 678 4: 400 Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] driver: i915 v: kernel Device-2: Suyin Integrated_Webcam_HD type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1: 1920x1080~60Hz 2: 1366x768~60Hz API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 520 (SKL GT2) Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel API: ALSA v: k6.1.0-18-amd64 status: kernel-api Server-1: PulseAudio v: 16.1 status: active Network: Device-1: Qualcomm Atheros AR9462 Wireless Network Adapter driver: ath9k IF: wlp2s0 state: up mac: <filter> Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 238.47 GiB used: 81.18 GiB (34.0%) ID-1: /dev/sda vendor: Samsung model: MZ7TY256HDHP-00000 size: 238.47 GiB Partition: ID-1: / size: 95.61 GiB used: 81.06 GiB (84.8%) fs: ext4 dev: /dev/sda4 ID-2: /boot/efi size: 495 MiB used: 51.3 MiB (10.4%) fs: vfat dev: /dev/sda1 Swap: ID-1: swap-1 type: partition size: 977 MiB used: 72.5 MiB (7.4%) dev: /dev/sda5 Sensors: System Temperatures: cpu: 48.0 C pch: 42.5 C mobo: 42.0 C Fan Speeds (RPM): cpu: 0 Info: Processes: 185 Uptime: 58m Memory: 7.5 GiB used: 5.11 GiB (68.2%) Shell: Bash inxi: 3.3.26 | Hello, You may try installing a newer kernel from bookworm-backports repository: https://backports.debian.org/ |
Hello, My setup is as follows: * Lenovo Thinkpad T15 with Debian 12 + Cinnamon installed * T15 is connected via Thunderbolt cable to Lenovo ThinkPad Thunderbolt 3 Dock station * two monitors are connected to ThinkPad Thunderbolt 3 Dock via DP cables I'm using only two external monitors, T15 lid is closed. When I power on the laptop via dock station, Grub menu appears on both external monitors, after that when I select Debian, monitors start to blink and after some time they are disabled. In order to get Debian working I need to * open laptop lid * disconnect Thunderbolt cable from the laptop * wait for Debian to appear on laptop screen * connect back Thunderbolt cable from the Dock to laptop * after above operations, both external monitors are working correctly and I can close laptop lid In 'Display settings', I have laptop screen disabled and one of external monitors is set as Primary. In 'Power Management' settings I have: * When the ld s closed: Do nothing (for both On A/C power and On battery power) * Perform lid-closed action even with external monitors attached - ENABLED Earlier I was using Linux Mint 21.1 with Cinnamon with above settings and I did not have such issues, everything was working flawlessly. It looks that latest firmware is installed: Code: Select allroot@T15:~# fwupdmgr get-updates Devices with no available firmware updates: • UEFI Device Firmware • UEFI Device Firmware • UEFI Device Firmware • UEFI Device Firmware • UEFI Device Firmware • Integrated Camera • ThinkPad Thunderbolt 3 Dock • UEFI dbx Devices with the latest available firmware version: • Embedded Controller • Intel Management Engine • Intel Management Engine • System Firmware • MZVLB512HBJQ-000L7 • Prometheus • Prometheus IOTA Config No updates available root@T15:~# I would appreciate hints on what logs to check and how to fix the issue. Thanks in advance. Przemek | I don't use laptops with docking stations, so can offer little, but I noticed zero responses after more than two days. I would not expect desktop settings for displays to have any impact whatsoever on lack of screen output before and when the GUI login screen is supposed to appear on at least the primary display. https://www.kernel.org/doc/Documentation/fb/modedb.txt explains how to use video= in Grub stanzas to configure various display parameters. Once you know the output names from Xorg.0.log or from xrandr output, they can be used to disable and/or specifically configure each display. So to disable the laptop screen you might need to include video=eDP-1:d, or force native mode on one of the external displays video=DP-1-1:2560x1440. These should take effect when KMS takes over during init, so after several seconds or more past Grub menu disappearance. They should persist on the tty framebuffers, but have no applicability in X, other than the possiblity that KMS using them for the framebuffers may cause those modes to persist when it wants to paint your login screen where you want it. Because Mint was OK, if you haven't already, I'd report a bug about this. |
In the kernel logs provided by the dmesg command it says "Alternate GPT is invalid, using primary GPT.". If I verify the /dev/nvme0n1 disk with the gdisk command I get: Code: Select allProblem: The secondary header's self-pointer indicates that it doesn't reside at the end of the disk. If you've added a disk to a RAID array, use the 'e' option on the experts' menu to adjust the secondary header's and partition table's locations. Problem: main GPT header's current LBA pointer (1) doesn't match the backup GPT header's alternate LBA pointer(500118191). Problem: main GPT header's backup LBA pointer (500118191) doesn't match the backup GPT header's current LBA pointer (1). The 'e' option on the experts' menu may fix this problem. Problem: The backup partition table overlaps the backup header. Using 'e' on the experts' menu may fix this problem. Identified 4 problems! Is it sufficient to execute the "e" command from the expert menu? Expert menu commands Code: Select alla set attributes b byte-swap a partition's name c change partition GUID d display the sector alignment value e relocate backup data structures to the end of the disk f randomize disk and partition unique GUIDs g change disk GUID h recompute CHS values in protective/hybrid MBR i show detailed information on a partition j move the main partition table l set the sector alignment value m return to main menu n create a new protective MBR o print protective MBR data p print the partition table q quit without saving changes r recovery and transformation options (experts only) s resize partition table t transpose two partition table entries u replicate partition table on new device v verify disk w write table to disk and exit z zap (destroy) GPT data structures and exit ? print this menu | As root:Code: Select allsgdisk -v /dev/nvme0n1sgdisk will detect the error and repair it. Good luck! |
I had a working mdadm raid1. With the intent of making a backup of my primary OS when it was unmounted, and after researching the safe commands to reassemble the raid in a different linux OS, I rebooted to System-Rescue-10, copied the mdadm.conf to /etc over the existing template. and attempted to mount /dev/md0 I got only one drive up. Ensue the mild panic, because this is the reason I did research first. I aborted, and rebooted back to Debian 11 to see if anything was harmed. Sadly yes. It says the drives are clean, but it won't reassemble. I am uncertain which path to take to get it back together. If it was marked degraded, I would remove the bad one, and re-add it. How can I determine why it is getting stuck? Code: Select all$ sudo mdadm --examine /dev/sd[de]1 /dev/sdd1: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : 1e3f7f7e:23a5b75f:6f76abf5:88f5e704 Name : roxy10-debian11-x64:0 (local to host roxy10-debian11-x64) Creation Time : Sat Jan 27 12:07:27 2024 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 11720777728 (5588.90 GiB 6001.04 GB) Array Size : 5860388864 (5588.90 GiB 6001.04 GB) Data Offset : 264192 sectors Super Offset : 8 sectors Unused Space : before=264112 sectors, after=0 sectors State : clean Device UUID : b65dd512:8928c097:47debae7:9c944a3e Internal Bitmap : 8 sectors from superblock Update Time : Sat Mar 2 18:50:02 2024 Bad Block Log : 512 entries available at offset 32 sectors Checksum : 39e567c9 - correct Events : 21691 Device Role : Active device 0 Array State : AA ('A' == active, '.' == missing, 'R' == replacing) /dev/sde1: Magic : a92b4efc Version : 1.2 Feature Map : 0x1 Array UUID : 1e3f7f7e:23a5b75f:6f76abf5:88f5e704 Name : roxy10-debian11-x64:0 (local to host roxy10-debian11-x64) Creation Time : Sat Jan 27 12:07:27 2024 Raid Level : raid1 Raid Devices : 2 Avail Dev Size : 11720777728 (5588.90 GiB 6001.04 GB) Array Size : 5860388864 (5588.90 GiB 6001.04 GB) Data Offset : 264192 sectors Super Offset : 8 sectors Unused Space : before=264112 sectors, after=0 sectors State : clean Device UUID : c7b9578b:0eef6ae2:6c33a25b:386cf478 Internal Bitmap : 8 sectors from superblock Update Time : Tue Mar 5 07:38:27 2024 Bad Block Log : 512 entries available at offset 32 sectors Checksum : aba80e46 - correct Events : 21704 Device Role : Active device 1 Array State : .A ('A' == active, '.' == missing, 'R' == replacing) $ sudo mdadm --assemble --verbose /dev/md0 /dev/sdd1 /dev/sde1 mdadm: looking for devices for /dev/md0 mdadm: /dev/sdd1 is busy - skipping mdadm: Merging with already-assembled /dev/md0 mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 0. mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1. mdadm: /dev/sdd1 is already in /dev/md0 as 0 mdadm: added /dev/sde1 to /dev/md0 as 1 mdadm: /dev/md0 has been started with 1 drive (out of 2). $ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] md0 : active (auto-read-only) raid1 sde1[1] 5860388864 blocks super 1.2 [2/1] [_U] bitmap: 1/44 pages [4KB], 65536KB chunk unused devices: <none> $ lsblk sdd 8:48 0 5.5T 0 disk └─sdd1 8:49 0 5.5T 0 part sde 8:64 0 5.5T 0 disk └─sde1 8:65 0 5.5T 0 part └─md0 9:0 0 5.5T 0 raid1 /mnt/Ugreen_RAID1_6Tb $ sudo dmsetup table No devices found $ sudo mdadm -E /dev/sdd /dev/sdd: MBR Magic : aa55 Partition[0] : 4294967295 sectors at 1 (type ee) $ sudo mdadm -E /dev/sde /dev/sde: MBR Magic : aa55 Partition[0] : 4294967295 sectors at 1 (type ee) Among the attempts I did also do a mdadm --stop md0 to remove the busy message, then reassemble from the right starting point, not showing in lsblk. Also the 21,000 events happened with the previous enclosure in January, so is not relevant now. I want to understand what happened before trying --force, or --zero-superblock, which appeared as solutions in my subsequent searches. I can't tell for sure if the superblock is the problem, but since I don't see any error about it, I am looking for other ideas. Code: Select all$ cat /etc/fstab | grep dev/md /dev/md0 /mnt/Ugreen_RAID1_6Tb ext3 defaults,noatime,rw,nofail,x-systemd.device-timeout=4 0 0 $ sudo fdisk -l /dev/sdd Disk /dev/sdd: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: 726T6TALE604 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 89AEDBB8-E01E-47FA-859B-A415D7DDEE35 Device Start End Sectors Size Type /dev/sdd1 2048 11721043967 11721041920 5.5T Linux filesystem $ sudo fdisk -l /dev/sde Disk /dev/sde: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: 726T6TALE604 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: FF7400C3-E30B-43C6-98F4-9783F92981D0 Device Start End Sectors Size Type /dev/sde1 2048 11721043967 11721041920 5.5T Linux filesystem $ cat /etc/mdadm/mdadm.conf ARRAY /dev/md0 metadata=1.2 name=roxy10-debian11-x64:0 UUID=1e3f7f7e:23a5b75f:6f76abf5:88f5e704 $ cat /proc/version Linux version 5.10.0-26-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.197-1 (2023-09-29) $ cat /etc/debian_version 11.8 Thank you | Hello, As you reported, mdadm cannot access to disk /dev/sdd1: Code: Select all$ sudo mdadm --assemble --verbose /dev/md0 /dev/sdd1 /dev/sde1 mdadm: looking for devices for /dev/md0 --> mdadm: /dev/sdd1 is busy - skipping <-- mdadm: Merging with already-assembled /dev/md0 mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 0. mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1. mdadm: /dev/sdd1 is already in /dev/md0 as 0 mdadm: added /dev/sde1 to /dev/md0 as 1 mdadm: /dev/md0 has been started with 1 drive (out of 2). I may be useful to check system journal/logs for errors about the busy disk (/dev/sdd1) and/or if other processes are accessing it. |
I tried to fix one ram slot that stopped working. Last time blowing dust out would let me boot but after switching sticks, the slot would give me an error again so i tried something else. I poured the 99% alcohol into the dim slots but am pretty sure some got to the cpu and went under there. Now I found out it was too cold for it to evaporate. I put the pc on the heater now and tomorrow blow dry the cpu region but it did not start up only one led on the cmos clear and sometimes no led when power on. Can my pc come back from this or do I need a new Mainboard & cpu or which one is more likely to be broken now ? Its a msi Z170a pc mate and a intel i7. | Pure isopropyl alcohol does not conduct electricity. It may however dissolve certain materials. Pouring it in is a bad idea. It should be used to dampen a lint-free cloth or something and gently wipe the area to be cleaned. If your motherboard still won't boot after cleaning and proper drying, there's a good chance it is FUBAR. It may also be possible your power supply has become defective. |
Not sure what I am missing? I have slower than what i Would expected on file transfers on 10gb ethernet from NVME to NVME over SMB and NFS. Test transfer of a 30 GB Folder containing mixed files @ 226 MB/s. My Setup is 2 HP z620 dual e5-2670, Broadcom 57810S Dual Port 10Gb NIC RJ45 MTU 9000 and 1 each NVMe WD Green SN350 1TB per machine. First HP z620 is running Debian 12 using Proxmox 8.1.4 as a hypervisor and Open Media Vault Version 6.5.0-3(Shaitan) running as a VM SMB Server Open Media Vault SMB Shares. First SMB is Raid 5 with 3 HDD read speed on a 30 GigByte Folder containing mixed files 196 MB/s. Expectation would be around 220 so it is close slightly low. Second SMB is NVMe WD Green SN350 1TB. read speed on a 30 GigByte Folder containing mixed files 226 MB/s. Expectation would be saturating the 10 Gb link at 900+ Only 30MB/s difference between Raid 5 and NVME? Second HP z620 is running Debian 12 desktop Drive is PCI(E) passed through on Proxmox node no option to test drive speed at this point Drive Speed Proxmox VM Code: Select allsudo hdparm -Tt /dev/sdx /dev/nvme0n1: Timing cached reads: 16896 MB in 1.99 seconds = 8487.12 MB/sec Timing buffered disk reads: 3784 MB in 3.00 seconds = 1260.86 MB/sec Drive Speed Desktop Code: Select allsudo hdparm -Tt /dev/nvme0n1 /dev/nvme0n1: Timing cached reads: 17450 MB in 1.99 seconds = 8772.46 MB/sec Timing buffered disk reads: 2904 MB in 3.00 seconds = 967.67 MB/sec Iperf3 results between 2 PC’s root@jaime-hpz620workstation:/etc/samba# Code: Select alliperf3 -c 10.0.40.169 Connecting to host 10.0.40.169, port 5201 [ 5] local 10.0.40.175 port 40206 connected to 10.0.40.169 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 1.12 GBytes 9.62 Gbits/sec 0 3.15 MBytes [ 5] 1.00-2.00 sec 1.15 GBytes 9.86 Gbits/sec 0 3.15 MBytes [ 5] 2.00-3.00 sec 1.14 GBytes 9.82 Gbits/sec 0 3.15 MBytes [ 5] 3.00-4.00 sec 1.14 GBytes 9.82 Gbits/sec 0 3.15 MBytes [ 5] 4.00-5.00 sec 1.15 GBytes 9.87 Gbits/sec 0 3.15 MBytes [ 5] 5.00-6.00 sec 1.15 GBytes 9.85 Gbits/sec 0 3.15 MBytes [ 5] 6.00-7.00 sec 1.15 GBytes 9.88 Gbits/sec 0 3.15 MBytes [ 5] 7.00-8.00 sec 1.15 GBytes 9.85 Gbits/sec 0 3.15 MBytes [ 5] 8.00-9.00 sec 1.13 GBytes 9.71 Gbits/sec 0 3.15 MBytes [ 5] 9.00-10.00 sec 1.15 GBytes 9.90 Gbits/sec 0 3.15 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 11.4 GBytes 9.82 Gbits/sec 0 sender [ 5] 0.00-10.04 sec 11.4 GBytes 9.77 Gbits/sec receiver Although I have excellent throughput via the iperf3 results I did swap the cable to see if that was the issue no change. I did test this with a windows10 device with an SSD and the same 30 GB folder. It starteed at 800Mb and after about 10 seconds droped down to about 150 so I am guess SSD cahe was exhausted. Any suggestions appreciated. | jaimarti wrote: 2024-03-12 20:09 I think I figured it out thanks to https://www.servethehome.com/wd-green-s ... -review/3/ It appears that the NVME's I choose are not the best performers. I guess I will need to buy the some better NVME's I'm glad you sorted it out. :) Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message (after other tags, if any); i.e. : [Solved] Slower than expected file transfers on 10gb ethernet Happy Debian ! -- note: moved to "Hardware" sub-forum. |
Hi, been trying quite a while now to get a TP-Link UB500 bluetooth adopter working on my new install. I can only see old threads here related to my problem. Running Debian 5.27.5 KDE Plasma 5.103.0 Kernel version 6.1.0-18-amd64 (64-bit) PC HP Elite Desk 800 mini with 8 × Intel® Core™ i7-6700T CPU @ 2.80GHz Ram 16 gig I cant enable via the GUI hcitool dev shows no devices. Code: Select allhciconfig -a hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:21 acl:0 sco:0 events:2 errors:0 TX bytes:6 acl:0 sco:0 commands:2 errors:0 Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: PERIPHERAL ACCEPT This appears to show the firmware / driver for my adopter is not installed. Code: Select allsudo dmesg | grep -i bluetooth [ 5.297639] Bluetooth: Core ver 2.22 [ 5.297658] NET: Registered PF_BLUETOOTH protocol family [ 5.297659] Bluetooth: HCI device and connection manager initialized [ 5.297678] Bluetooth: HCI socket layer initialized [ 5.297680] Bluetooth: L2CAP socket layer initialized [ 5.297685] Bluetooth: SCO socket layer initialized [ 5.363125] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 5.364115] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 5.364119] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 5.364920] bluetooth hci0: firmware: failed to load rtl_bt/rtl8761bu_fw.bin (-2) [ 5.364983] bluetooth hci0: firmware: failed to load rtl_bt/rtl8761bu_fw.bin (-2) [ 5.365005] bluetooth hci0: Direct firmware load for rtl_bt/rtl8761bu_fw.bin failed with error -2 [ 5.365008] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761bu_fw.bin not found [ 6.561220] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.561228] Bluetooth: BNEP filters: protocol multicast [ 6.561237] Bluetooth: BNEP socket layer initialized [ 217.454234] Bluetooth: hci1: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821 [ 217.455185] Bluetooth: hci1: RTL: rom_version status=0 version=1 [ 217.455190] Bluetooth: hci1: RTL: loading rtl_bt/rtl8821c_fw.bin [ 217.455208] bluetooth hci1: firmware: failed to load rtl_bt/rtl8821c_fw.bin (-2) [ 217.455221] bluetooth hci1: firmware: failed to load rtl_bt/rtl8821c_fw.bin (-2) [ 217.455224] bluetooth hci1: Direct firmware load for rtl_bt/rtl8821c_fw.bin failed with error -2 [ 217.455228] Bluetooth: hci1: RTL: firmware file rtl_bt/rtl8821c_fw.bin not found [ 713.170188] Bluetooth: RFCOMM TTY layer initialized [ 713.170196] Bluetooth: RFCOMM socket layer initialized [ 713.170201] Bluetooth: RFCOMM ver 1.11 Here are the entries in my sources file eb cdrom:[Debian GNU/Linux 12.5.0 _Bookworm_ - Official amd64 NETINST with firmware 20240210-11:27]/ bookworm contrib main non-free-firmware deb http://deb.debian.org/debian/ bookworm main non-free non-free-firmware contrib deb-src http://deb.debian.org/debian/ bookworm main non-free non-free-firmware contrib deb http://security.debian.org/debian-security/ bookworm-security main non-free non-free-firmware contrib deb-src http://security.debian.org/debian-security/ bookworm-security main non-free non-free-firmware contrib # bookworm-updates, to get updates before a point release is made; # see https://www.debian.org/doc/manuals/debi ... _backports deb http://deb.debian.org/debian/ bookworm-updates main non-free non-free-firmware contrib deb-src http://deb.debian.org/debian/ bookworm-updates main non-free non-free-firmware contrib # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual. The system is up to date. Any help or something I missed would be great. J | SeeYouNextTuesday wrote: 2024-03-21 18:15 Thank you sooo much to @bbbhltz running... Code: Select all sudo apt install firmware-realtek ... and then rebooting finally solved this form me. I'm glad you sorted it out. :) Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message (after other tags, if any). It is also an opportunity to the make the subject more understandable to other forum users and readers, if necessary; i.e. : [Solved] TP-Link UB500 bluetooth adapter - Cant Enable Bluetooth / Missing Firmware Happy Debian ! |
I would like to see the output while my system (details at bottom) boots when the monitor is connected only with an HDMI cable. Currently I have both DVI and HDMI and I have no problem seeing the output using DVI but see nothing with HDMI. I have an Nvidia 1070 and a motherboard that does not support UEFI. I do not use a display manager but boot into a console and once the login prompt appears, log in and start X manually. I want to continue this (even though I do check boot output later with This is to understand what would be needed to switch to a newer graphics card and monitor that would come without any DVI interfaces. I suspect this might be fixed with a better grub config. System details: trixie/sid, linux-image-amd64 6.5.13-1, nvidia-driver 525.147.05-4, systemd 255.2-2 /etc/default/grub: Code: Select allGRUB_DEFAULT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_TIMEOUT=11 GRUB_CMDLINE_LINUX_DEFAULT="loglevel=5" GRUB_CMDLINE_LINUX="splash nomodeset loglevel=5 fsck.mode=force video=HDMI-0:e" GRUB_BACKGROUND=/boot/grub/splash_images/gnome-splash-curves.png GRUB_GFXMODE=2560x1440,1920x1080,1600x1200x16,1600x1200,800x600x16,800x600,640x480,auto GRUB_DISABLE_LINUX_UUID=true Any ideas for how to make this work? thanks! | JSJB wrote: 2024-03-26 14:34 I would like to see the output while my system (details at bottom) boots when the monitor is connected only with an HDMI cable. Have you tried it with the DVI disconnected? The initial boot screen doesn't have anything to do with any OS, or grub. I have mentioned before a particular monitor that would not initialize the hdmi input on power up, that was the monitor not the gpu or OS. Maybe a new-to-you gpu, most all cards I've ever used will initialize the only connected output regardless of the typical priority order of vga>dvi>dp>hdmi. But then maybe I don't always pay attention... |
Hi all! New here. So after many years of fedora, I am Debian for my laptop. However, my laptop that works well, does not have working keyboard. And just need your help! Strange part is that it works in Grub. But after that. No matter what kernel I use, even up to experimental kernel in Manjaro. It still doesn't work. I tried debian 10, but wont start instead. I tried i8042.reset i8042.unlock i8042.nopnp i8042... many of them, The only one that works is i8042.dumbkbd. However. they keys lags a lot, and if i press for example F, it get FFFFFFFFFFFFFFFFFFF. I also tried different xorg set ups, but might have done it wrongly. So, any log you need I will provide, but unsure what you want. The computer is an oddball named Cepter Any help would be wonderful! | Hello, Can you report your general hardware/software configuration ? You can use the following command (the inxi program must be installed): Code: Select allinxi -Fz |
This is a fairly fresh Debian install, only a few days I believe. I can't remember if bluetooth worked initially or not. If I try to pair a bluetooth device via Plasma's interface, I get the message "The setup of (bluetooth device) has failed". Debian 11.2 Stable lspci output: Code: Select all00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 11) 00:13.0 Serial controller: Intel Corporation Cannon Point-LP Integrated Sensor Hub (rev 11) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 11) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 (rev 11) 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 (rev 11) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 11) 00:16.3 Serial controller: Intel Corporation Cannon Point-LP Keyboard and Text (KT) Redirection (rev 11) 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 11) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f1) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f1) 00:1d.6 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #15 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11) 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI Controller (rev 11) 01:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 02:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 02:01.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 02:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 02:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018] (rev 06) 03:00.0 System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018] (rev 06) 37:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] (rev 06) 38:00.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06) 39:02.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06) 39:04.0 PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge DD 2018] (rev 06) 3a:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller [Titan Ridge 4C 2018] (rev 06) 6c:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a) 6d:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 (rev 03) 6e:00.0 Non-Volatile memory controller: Intel Corporation Device 0975 If I check the service status of bluetooth by running sudo systemctl status bluetooth.service, it indicates an issue with something but I'm not sure exactly what this is saying. "Sap driver initialization failed", and "protocol not available". Code: Select all● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-02-20 21:36:47 CST; 14min ago Docs: man:bluetoothd(8) Main PID: 1258 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18927) Memory: 4.0M CPU: 99ms CGroup: /system.slice/bluetooth.service └─1258 /usr/libexec/bluetooth/bluetoothd Feb 20 21:36:47 Dragonfly bluetoothd[1258]: Bluetooth daemon 5.55 Feb 20 21:36:47 Dragonfly systemd[1]: Started Bluetooth service. Feb 20 21:36:47 Dragonfly bluetoothd[1258]: Starting SDP server Feb 20 21:36:47 Dragonfly bluetoothd[1258]: Bluetooth management interface 1.18 initialized Feb 20 21:36:49 Dragonfly bluetoothd[1258]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed. Feb 20 21:36:49 Dragonfly bluetoothd[1258]: sap-server: Operation not permitted (1) Feb 20 21:38:21 Dragonfly bluetoothd[1258]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 08:DF:1F:36:8F:F7: Protocol not available Feb 20 21:39:11 Dragonfly bluetoothd[1258]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 08:DF:1F:36:8F:F7: Protocol not available Feb 20 21:39:30 Dragonfly bluetoothd[1258]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 08:DF:1F:36:8F:F7: Protocol not available Feb 20 21:48:04 Dragonfly bluetoothd[1258]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 04:5D:4B:C0:D9:6D: Protocol not available Any ideas or insight is very much appreciated - Please let me know any additional info or output you'd like to see as well. Side note, but besides this bluetooth hiccup I'm loving Debian so far, and it has otherwise been my most stable Plasma experience thus far on this laptop/docking station combo. Edit: I attempted to edit /etc/systemd/system/bluetooth.target.wants/bluetooth.service: ExecStart=/usr/lib/bluetooth/bluetoothd to ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap This got rid of the "Sap driver initialization failed" message on the bluetooth.service status, however I still get a protocol error as listed here, and bluetooth connection still fails with the same message in Plasma: Code: Select all● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-02-20 22:00:28 CST; 1min 36s ago Docs: man:bluetoothd(8) Main PID: 852 (bluetoothd) Status: "Running" Tasks: 1 (limit: 18927) Memory: 4.0M CPU: 52ms CGroup: /system.slice/bluetooth.service └─852 /usr/libexec/bluetooth/bluetoothd --noplugin=sap Feb 20 22:00:28 Dragonfly systemd[1]: Starting Bluetooth service... Feb 20 22:00:28 Dragonfly bluetoothd[852]: Bluetooth daemon 5.55 Feb 20 22:00:28 Dragonfly bluetoothd[852]: Starting SDP server Feb 20 22:00:28 Dragonfly bluetoothd[852]: Excluding (cli) sap Feb 20 22:00:28 Dragonfly systemd[1]: Started Bluetooth service. Feb 20 22:00:28 Dragonfly bluetoothd[852]: Bluetooth management interface 1.18 initialized Feb 20 22:01:37 Dragonfly bluetoothd[852]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 04:5D:4B:C0:D9:6D: Protocol not available | https://wiki.debian.org/BluetoothUser/a ... _available |
This is driving me insane. I didn't upgrade forever because I was worried something would break, didn't think it would be wifi. I do want 12 but had to go to 11 first. Anyway here is the problem: USB wifi worked great on 10. Stopped as soon as I rebooted into 11. Am typing this from mac, so can't cut and paste but here is some important info: lsusb: Code: Select allBus 001 Device 003: ID 0b05:184c ASUSTek Computer, Inc. 802.11ac NIC DMESG (at first did complain no firmware, I have loaded it in since): Code: Select allusb1-4: New USB device found, idVendor=0b05, idProduct=184c, bcdDevice=2.10 usb1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb1-4: Product 802.11ac NIC usb1-4: Manufacturer: Realtek usb1-4: SerialNumber 123456 and output from ip a: Code: Select all1 lo: I am skipping this as it looks correct if needed let me know 2: enps4s0: NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast DOWN group defaul qlen 1000 link/ether 00:d8:61:50:6d:84 brd ff:ff:ff:ff:ff:ff KDE does not show wireless network at all, I can tether with my cell phone temporarily. Am I missing something simple? Thanks! | Hello, aschueler wrote: 2024-02-18 16:41 DMESG (at first did complain no firmware, I have loaded it in since): Code: Select allusb1-4: New USB device found, idVendor=0b05, idProduct=184c, bcdDevice=2.10 usb1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb1-4: Product 802.11ac NIC usb1-4: Manufacturer: Realtek usb1-4: SerialNumber 123456 Are you currently using an external USB WiFi adapter or is it integrated in the computer ? Can you report the output of the following command (the inxi program must be installed ?) Code: Select allinxi -Fz Can you report the full system log after boot ? You can use the command: Code: Select allscript log.txt su -l -c "journalctl -b --nopager" exit You can report logs in one the following ways: paste them into the Debian Pastezone service (https://paste.debian.net) and report the URL/link of the paste in a follow-up message attaching the logs to a follow-up forum message as a compressed zip or gz file paste logs into the body of a follow-up message between code tags (if they fit the size of a forum message) Anyway, according to the followind hardware database, you WiFi adapter (Device 'ASUSTek Computer 802.11ac NIC', usb:0b05-184c) should be supported from kernel version 6.2+ (Debian 10 is reported as not working): https://linux-hardware.org/?id=usb:0b05-184c |
Hi Folks, My problem is, that the new wifi6 never works, while image greater than subver. 13 ... This is the working state: Code: Select allroot@xxx:~# lsmod | grep rtw rtw_8852be 16384 0 rtw_8852b 372736 1 rtw_8852be rtw89pci 65536 1 rtw_8852be rtw89core 540672 2 rtw89pci,rtw_8852b mac80211 1175552 2 rtw89pci,rtw89core cfg80211 1134592 3 rtw89core,mac80211,rtw_8852b root@xxx:~# uname -a Linux xxx 6.1.0-13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux All later builds of kernel cannot use the card ( it is an HP laptop ) Any idea, what can i do? Where can i post my issue? thx -- Olivér EDIT Of course, non-free and non-free-firmware are in sources ( bookworm ) /EDIT | Hello, The rtw8852be seems an unofficial kernel module (for Debian). Where did you get it ? May you report hardware details of your network adapter ? You can use the following commands: Code: Select alllspci -vnn -d::02xx lsusb |
I am trying to work out what I have done to cause a crash, affecting window and preventing me shutting down. Prior to making changes I had a stable system once I added boot arg in respect of nvme (the boot drive) I added a SATA drive internal which registers as HDD0, when the boot drive nvme is HDD1 I altered drive behaviour to add write cache to the SATA HDD0 [corrected this on SATA drive HDD0. I tried a new USB 3.0 external SATA drive and soon afterwards the crash occurred The Desktop crashed - it affected windows and i couldn't shutdown until i held power key down for a minute Recovery failed looking for btrfs. See the snippet below for the recovery screen. I was able to reboot into standard debian 12 and its behaving normally now but Hot corners stopped working, so I disabled it in settings. I reinserted the USB 3.0 drive (called Goldenfir) and no crashes in the past hour. app.php/pastebin/?mode=view&s=77 Code: Select all[ BIOS HDD0 is SATA 480G drive which is configured ACPI and is checked first for grub/efi but its not a boot drive. Recovery failed - Begin: Mounting root file systen ... Begin: Running /scripts/local-top ... Begin: Running /scripts/local-premount ... done. Scanning for Btrfs filesystems [4.0317181] Btrfs loaded, crc32c=crc32c-intel, zoned=yes, fsverity=yes [36.287293] nvme nvme0: controller is down: will reset: CSTS=Oxffffffff, PCI_STATUS=0xffff 36.291273] nvne nvme0: Does your device have a faulty power saving mode enabled? 36.2912731 nvme nvme0: Try "nume_core.default_ps_max_latency_us=0 pcie_aspn-off" and report a bug /code] dmesg https://forums.debian.net/app.php/pastebin/?mode=view&s=77 | Hello, It seems to be all right, according to the log linked to in the previous post. |
Hi I am using a PocketBeagle that is on Bullseye 5.10 kernel and I am trying to get the TP-Link Nano USB Bluetooth 5.0 UB5A (same as UB500) dongle working. The vendor:product id is 2357:0604 it's version 2.0 and the chip is Realtek RTL8761B. I have manually installed firmware as it's not present in the 5.10 distribution, taking the deb file from here: http://ftp.us.debian.org/debian/pool/no ... +1_all.deb and installing using dpkg -i firmware-realtek_20230210-5~bpo11+1_all.deb As I have found others have posted about both here and linux mint forums, the device is recognised but hcitool scan doesn't find any devices. This is my first post and I'm new at troubleshooting linux hardware so if I've missed anything in the diag stuff below I can run any other commands necessary. Thanks! Code: Select alldebian@BeagleBone:~$ inxi -Fxxxrz perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = "en_GB.UTF-8" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). System: Kernel: 5.10.168-ti-r71 armv7l bits: 32 compiler: gcc v: 10.2.1 Console: tty 0 Distro: Debian GNU/Linux 11 (bullseye) Machine: Type: ARM Device System: TI AM335x PocketBeagle details: Generic AM33XX rev: N/A serial: <filter> CPU: Info: Single Core model: ARMv7 v7l variant: cortex-a8 bits: 32 type: UP arch: v7l rev: 2 features: Use -f option to see features bogomips: 995 Speed: 1000 MHz min/max: 300/1000 MHz Core speed (MHz): 1: 1000 Graphics: Message: No ARM data found for this feature. Display: server: No display server data found. Headless machine? tty: 221x90 Message: Advanced graphics data unavailable in console. Try -G --display Audio: Message: No ARM data found for this feature. Network: Message: No ARM data found for this feature. IF-ID-1: can0 state: down mac: N/A IF-ID-2: can1 state: down mac: N/A IF-ID-3: usb0 state: up speed: N/A duplex: N/A mac: <filter> IF-ID-4: usb1 state: up speed: N/A duplex: N/A mac: <filter> Bluetooth: Device-1: TP-Link UB5A Adapter type: USB driver: btusb v: 0.8 bus ID: 2-1:2 chip ID: 2357:0604 class ID: e001 serial: <filter> Report: ID: hci0 state: up running bt-v: 3.0 lmp-v: 5.1 sub-v: 8761 hci-v: 5.1 rev: b address: <filter> Drives: Local Storage: total: 14.44 GiB used: 3 GiB (20.8%) ID-1: /dev/mmcblk0 model: SA16G size: 14.44 GiB rotation: SSD serial: <filter> scheme: MBR Partition: ID-1: / size: 14.13 GiB used: 3 GiB (21.2%) fs: ext4 dev: /dev/mmcblk0p1 Swap: Alert: No Swap data was found. Sensors: Message: No sensors data was found. Is sensors configured? Repos: Packages: apt: 596 Active apt repos in: /etc/apt/sources.list 1: deb http://deb.debian.org/debian bullseye main contrib non-free 2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free 3: deb http://deb.debian.org/debian bullseye-updates main contrib non-free 4: deb [arch=armhf signed-by=/usr/share/keyrings/rcn-ee-archive-keyring.gpg] http://repos.rcn-ee.com/debian/ bullseye main Active apt repos in: /etc/apt/sources.list.d/brostrend.list 1: deb https://linux.brostrend.com stable main previous Info: Processes: 106 Uptime: 43m Memory: 482.6 MiB used: 78.2 MiB (16.2%) Init: systemd v: 247 runlevel: 5 Compilers: gcc: 10.2.1 alt: 10 Shell: Bash v: 5.1.4 running in: tty 0 inxi: 3.3.01 Code: Select alldebian@BeagleBone:~$ dmesg | grep -i usb [ 4.285073] usbcore: registered new interface driver usbfs [ 4.285134] usbcore: registered new interface driver hub [ 4.285193] usbcore: registered new device driver usb [ 7.334189] usbcore: registered new interface driver smsc95xx [ 7.336860] am335x-phy-driver 47401300.usb-phy: supply vcc not found, using dummy regulator [ 7.337257] am335x-phy-driver 47401300.usb-phy: dummy supplies not allowed for exclusive requests [ 7.344254] am335x-phy-driver 47401b00.usb-phy: supply vcc not found, using dummy regulator [ 7.344570] am335x-phy-driver 47401b00.usb-phy: dummy supplies not allowed for exclusive requests [ 7.347359] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 7.352738] musb-hdrc musb-hdrc.0: MUSB HDRC host driver [ 7.352784] musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1 [ 7.353149] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10 [ 7.353162] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 7.353172] usb usb1: Product: MUSB HDRC host driver [ 7.353181] usb usb1: Manufacturer: Linux 5.10.168-ti-r71 musb-hcd [ 7.353189] usb usb1: SerialNumber: musb-hdrc.0 [ 7.354083] hub 1-0:1.0: USB hub found [ 7.361860] musb-hdrc musb-hdrc.1: MUSB HDRC host driver [ 7.361908] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2 [ 7.362452] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10 [ 7.362467] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 7.362477] usb usb2: Product: MUSB HDRC host driver [ 7.362485] usb usb2: Manufacturer: Linux 5.10.168-ti-r71 musb-hcd [ 7.362494] usb usb2: SerialNumber: musb-hdrc.1 [ 7.363492] hub 2-0:1.0: USB hub found [ 7.408903] usbcore: registered new interface driver usbhid [ 7.408916] usbhid: USB HID core driver [ 7.778915] usb 2-1: new full-speed USB device number 2 using musb-hdrc [ 7.927636] usb 2-1: New USB device found, idVendor=2357, idProduct=0604, bcdDevice= 2.00 [ 7.927662] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 7.927672] usb 2-1: Product: TP-Link UB5A Adapter [ 7.927681] usb 2-1: Manufacturer: [ 7.927689] usb 2-1: SerialNumber: E848B8C84000 [ 29.777155] usb0: HOST MAC 1c:63:49:f1:b6:fb [ 29.777179] usb0: MAC 1c:63:49:f1:b6:fc [ 29.798552] usb1: HOST MAC 1c:63:49:f1:b6:fd [ 29.798577] usb1: MAC 1c:63:49:f1:b6:fe [ 40.368244] usbcore: registered new interface driver btusb [ 517.115893] usb 2-1: USB disconnect, device number 2 [ 521.355927] usb 2-1: new full-speed USB device number 3 using musb-hdrc [ 521.505781] usb 2-1: New USB device found, idVendor=2357, idProduct=0604, bcdDevice= 2.00 [ 521.505808] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 521.505818] usb 2-1: Product: TP-Link UB5A Adapter [ 521.505827] usb 2-1: Manufacturer: [ 521.505836] usb 2-1: SerialNumber: E848B8C84000 Code: Select alldebian@BeagleBone:~$ dmesg | grep -i bluetooth [ 39.900881] Bluetooth: Core ver 2.22 [ 39.901113] Bluetooth: HCI device and connection manager initialized [ 39.901148] Bluetooth: HCI socket layer initialized [ 39.901164] Bluetooth: L2CAP socket layer initialized [ 39.901206] Bluetooth: SCO socket layer initialized [ 44.622913] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 44.622937] Bluetooth: BNEP filters: protocol multicast [ 44.622972] Bluetooth: BNEP socket layer initialized Code: Select alldebian@BeagleBone:~$ lsmod Module Size Used by pru_rproc 28672 0 cmac 16384 3 algif_hash 16384 1 irq_pruss_intc 20480 0 aes_arm_bs 24576 2 crypto_simd 16384 1 aes_arm_bs cryptd 20480 2 crypto_simd algif_skcipher 16384 1 af_alg 24576 6 algif_hash,algif_skcipher bnep 28672 2 pm33xx 20480 0 pruss 20480 1 pru_rproc pvrsrvkm 368640 0 btusb 57344 0 btrtl 24576 1 btusb btbcm 16384 1 btusb btintel 24576 1 btusb bluetooth 520192 28 btrtl,btintel,bnep,btbcm,btusb c_can_platform 16384 0 c_can 24576 1 c_can_platform can_dev 28672 1 c_can evdev 24576 1 wkup_m3_ipc 20480 1 pm33xx uio_pdrv_genirq 20480 0 uio 20480 1 uio_pdrv_genirq cpufreq_dt 20480 0 Code: Select alldebian@BeagleBone:~$ lsusb Bus 002 Device 003: ID 2357:0604 TP-Link TP-Link UB5A Adapter Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub debian@BeagleBone:~$ lsusb -vd 2357:0604 Bus 002 Device 003: ID 2357:0604 TP-Link TP-Link UB5A Adapter Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize0 64 idVendor 0x2357 TP-Link idProduct 0x0604 bcdDevice 2.00 iManufacturer 1 iProduct 2 TP-Link UB5A Adapter iSerial 3 E848B8C84000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x00b1 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 4 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 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 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 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 1 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 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 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 1 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 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 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 1 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 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 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 1 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 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 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 1 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 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 5 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 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 1 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 1 Code: Select alldebian@BeagleBone:~$ systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2024-01-07 14:41:04 UTC; 43min ago Docs: man:bluetoothd(8) Main PID: 920 (bluetoothd) Status: "Running" Tasks: 1 (limit: 1022) Memory: 3.1M CPU: 193ms CGroup: /system.slice/bluetooth.service └─920 /usr/libexec/bluetooth/bluetoothd --noplugin=sap --compat Jan 07 14:41:04 BeagleBone systemd[1]: Starting Bluetooth service... Jan 07 14:41:04 BeagleBone bluetoothd[920]: Bluetooth daemon 5.55 Jan 07 14:41:04 BeagleBone systemd[1]: Started Bluetooth service. Jan 07 14:41:04 BeagleBone bluetoothd[920]: Starting SDP server Jan 07 14:41:04 BeagleBone bluetoothd[920]: Excluding (cli) sap Jan 07 14:41:04 BeagleBone bluetoothd[920]: Bluetooth management interface 1.18 initialized Code: Select alldebian@BeagleBone:~$ cat /etc/systemd/system/bluetooth.target.wants/bluetooth.service [Unit] Description=Bluetooth service Documentation=man:bluetoothd(8) ConditionPathIsDirectory=/sys/class/bluetooth [Service] Type=dbus BusName=org.bluez ExecStart=/usr/libexec/bluetooth/bluetoothd --noplugin=sap --compat NotifyAccess=main #WatchdogSec=10 #Restart=on-failure CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE LimitNPROC=1 ProtectHome=true ProtectSystem=full [Install] WantedBy=bluetooth.target Alias=dbus-org.bluez.service Code: Select alldebian@BeagleBone:/usr/lib$ rfkill ID TYPE DEVICE SOFT HARD 0 bluetooth hci0 unblocked unblocked Code: Select alldebian@BeagleBone:/usr/lib$ hcitool dev Devices: hci0 E8:48:B8:C8:40:00 debian@BeagleBone:/usr/lib$ hciconfig -a hci0: Type: Primary Bus: USB BD Address: E8:48:B8:C8:40:00 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING RX bytes:1048 acl:0 sco:0 events:61 errors:0 TX bytes:2723 acl:0 sco:0 commands:60 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'BeagleBone' Class: 0x000000 Service Classes: Unspecified Device Class: Miscellaneous, HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) Log having inserted the device: Code: Select alldebian@BeagleBone:~$ tail /var/log/syslog Jan 7 15:26:30 BeagleBone kernel: [ 2769.919194] usb 2-1: new full-speed USB device number 4 using musb-hdrc Jan 7 15:26:30 BeagleBone kernel: [ 2770.068951] usb 2-1: New USB device found, idVendor=2357, idProduct=0604, bcdDevice= 2.00 Jan 7 15:26:30 BeagleBone kernel: [ 2770.068977] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jan 7 15:26:30 BeagleBone kernel: [ 2770.068987] usb 2-1: Product: TP-Link UB5A Adapter Jan 7 15:26:30 BeagleBone kernel: [ 2770.068996] usb 2-1: Manufacturer: Jan 7 15:26:30 BeagleBone kernel: [ 2770.069005] usb 2-1: SerialNumber: E848B8C84000 Jan 7 15:26:30 BeagleBone systemd[1]: Starting Load/Save RF Kill Switch Status... Jan 7 15:26:31 BeagleBone systemd[1]: Started Load/Save RF Kill Switch Status. Jan 7 15:26:31 BeagleBone systemd[981]: Reached target Bluetooth. Jan 7 15:26:31 BeagleBone systemd[1]: Reached target Bluetooth. Nothing shown in the scan Code: Select alldebian@BeagleBone:/usr/lib$ hcitool scan Scanning ... | Hello, If I read this correctly, it seems that support for your bluetooth USB Dongle: Code: Select all$ lsusb -vd 2357:0604 Bus 002 Device 003: ID 2357:0604 TP-Link TP-Link UB5A Adapter has been added with the following commit [1]: Code: Select allauthor Nicholas Flintham <nick@flinny.org> 2021-09-30 09:22:39 +0100 committer Marcel Holtmann <marcel@holtmann.org> 2021-10-01 11:39:40 +0200 commit 4fd6d490796171bf786090fee782e252186632e4 (patch) tree c46a4d4bd0f3caa515aa191ea9125c9b6400ef27 parent 64ba2eb35fa076d5914e3a3e374898ca31c29e84 (diff) download linux-4fd6d490796171bf786090fee782e252186632e4.tar.gz Bluetooth: btusb: Add support for TP-Link UB500 Adapter Add support for TP-Link UB500 Adapter (RTL8761B) * /sys/kernel/debug/usb/devices T: Bus=01 Lev=02 Prnt=05 Port=01 Cnt=01 Dev#= 78 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=2357 ProdID=0604 Rev= 2.00 S: Manufacturer= S: Product=TP-Link UB500 Adapter S: SerialNumber=E848B8C82000 C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms Signed-off-by: Nicholas Flintham <nick@flinny.org> Signed-off-by: Marcel Holtmann <marcel@holtmann.org> since kernel version v5.16: Code: Select all$ git tag --contains 4fd6d490796171bf786090fee782e252186632e4 | head -n 2 contains v5.16 Therefore, your Linux kernel: Code: Select allSystem: Kernel: 5.10.168-ti-r71 armv7l bits: 32 compiler: gcc v: 10.2.1 Console: tty 0 Distro: Debian GNU/Linux 11 (bullseye) should not support the bluetooth adapter (unless it is out of sync with the upstream kernel version). Is it your kernel from BeagleBoard repositories (and not from Debian repositories) ? --- [1] kernel.org: Bluetooth: btusb: Add support for TP-Link UB500 Adapter |
Never paid attention to it , but recently come to the realization that both USB ports on the right side are not functioning : https://asus-rog-gl753vd.rogdoc.com/en/ ... ight-side/ The two ports on the left side , which I always used until now , are working properly : https://asus-rog-gl753vd.rogdoc.com/en/ ... left-side/ Whatever is plugged in , is not recognized by the system . Helpful information ? output lsusb : Code: Select allphil@phil-gl753vd:~$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 0b05:1854 ASUSTek Computer, Inc. ITE Device(8910) Bus 001 Device 002: ID 045e:076c Microsoft Corp. Comfort Mouse 4500 Bus 001 Device 005: ID 13d3:5666 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub phil@phil-gl753vd:~$ output lspci -v : Code: Select allphil@phil-gl753vd:~$ lspci -v 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers Flags: bus master, fast devsel, latency 0, IOMMU group 1 Capabilities: <access denied> Kernel driver in use: skl_uncore 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05) (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. 6th-10th Gen Core Processor PCIe Controller (x16) Flags: bus master, fast devsel, latency 0, IRQ 122, IOMMU group 2 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: e000-efff [size=4K] [16-bit] Memory behind bridge: de000000-df0fffff [size=17M] [32-bit] Prefetchable memory behind bridge: c0000000-d1ffffff [size=288M] [32-bit] Capabilities: <access denied> Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) (prog-if 00 [VGA controller]) DeviceName: Onboard IGD Subsystem: ASUSTeK Computer Inc. HD Graphics 630 Flags: bus master, fast devsel, latency 0, IRQ 131, IOMMU group 0 Memory at dd000000 (64-bit, non-prefetchable) [size=16M] Memory at b0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model Flags: fast devsel, IRQ 255, IOMMU group 3 Memory at df430000 (64-bit, non-prefetchable) [disabled] [size=4K] Capabilities: <access denied> 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller Flags: bus master, medium devsel, latency 0, IRQ 128, IOMMU group 4 Memory at df410000 (64-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family Thermal Subsystem Flags: fast devsel, IRQ 18, IOMMU group 4 Memory at df42f000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 (rev 31) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family Serial IO I2C Controller Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 5 Memory at df42e000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family MEI Controller Flags: bus master, fast devsel, latency 0, IRQ 132, IOMMU group 6 Memory at df42d000 (64-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) (prog-if 01 [AHCI 1.0]) Subsystem: ASUSTeK Computer Inc. HM170/QM170 Chipset SATA Controller [AHCI Mode] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 129, IOMMU group 7 Memory at df428000 (32-bit, non-prefetchable) [size=8K] Memory at df42c000 (32-bit, non-prefetchable) [size=256] I/O ports at f090 [size=8] I/O ports at f080 [size=4] I/O ports at f060 [size=32] Memory at df42b000 (32-bit, non-prefetchable) [size=2K] Capabilities: <access denied> Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family PCI Express Root Port Flags: bus master, fast devsel, latency 0, IRQ 123, IOMMU group 8 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: [disabled] [16-bit] Memory behind bridge: df300000-df3fffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: <access denied> Kernel driver in use: pcieport 00:1c.3 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 (rev f1) (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family PCI Express Root Port Flags: bus master, fast devsel, latency 0, IRQ 124, IOMMU group 9 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: d000-dfff [size=4K] [16-bit] Memory behind bridge: df200000-df2fffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: <access denied> Kernel driver in use: pcieport 00:1c.6 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #7 (rev f1) (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family PCI Express Root Port Flags: bus master, fast devsel, latency 0, IRQ 125, IOMMU group 10 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: [disabled] [16-bit] Memory behind bridge: df100000-df1fffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Capabilities: <access denied> Kernel driver in use: pcieport 00:1f.0 ISA bridge: Intel Corporation HM175 Chipset LPC/eSPI Controller (rev 31) Subsystem: ASUSTeK Computer Inc. HM175 Chipset LPC/eSPI Controller Flags: bus master, medium devsel, latency 0, IOMMU group 11 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family Power Management Controller Flags: fast devsel, IOMMU group 11 Memory at df424000 (32-bit, non-prefetchable) [disabled] [size=16K] 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) (prog-if 80) Subsystem: ASUSTeK Computer Inc. CM238 HD Audio Controller Flags: bus master, fast devsel, latency 32, IRQ 134, IOMMU group 11 Memory at df420000 (64-bit, non-prefetchable) [size=16K] Memory at df400000 (64-bit, non-prefetchable) [size=64K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family SMBus Flags: medium devsel, IRQ 16, IOMMU group 11 Memory at df42a000 (64-bit, non-prefetchable) [size=256] I/O ports at f040 [size=32] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1) Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] Flags: bus master, fast devsel, latency 0, IRQ 130, IOMMU group 2 Memory at de000000 (32-bit, non-prefetchable) [size=16M] Memory at c0000000 (64-bit, prefetchable) [size=256M] Memory at d0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at df000000 [disabled] [size=512K] Capabilities: <access denied> Kernel driver in use: nouveau Kernel modules: nouveau 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [Stone Peak 2 AC] Flags: bus master, fast devsel, latency 0, IRQ 133, IOMMU group 12 Memory at df300000 (64-bit, non-prefetchable) [size=8K] Capabilities: <access denied> Kernel driver in use: iwlwifi Kernel modules: iwlwifi 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Flags: bus master, fast devsel, latency 0, IRQ 19, IOMMU group 13 I/O ports at d000 [size=256] Memory at df204000 (64-bit, non-prefetchable) [size=4K] Memory at df200000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: r8169 Kernel modules: r8169 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01) Subsystem: ASUSTeK Computer Inc. RTS5229 PCI Express Card Reader Flags: bus master, fast devsel, latency 0, IRQ 126, IOMMU group 14 Memory at df100000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci phil@phil-gl753vd:~$ output dmidecode -t 8 : Code: Select allphil@phil-gl753vd:~$ sudo dmidecode -t 8 [sudo] wachtwoord voor phil: # dmidecode 3.4 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Handle 0x0004, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: PS2Mouse External Connector Type: PS/2 Port Type: Mouse Port Handle 0x0005, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: Keyboard External Connector Type: PS/2 Port Type: Keyboard Port Handle 0x0006, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A1 Internal Connector Type: None External Reference Designator: TV Out External Connector Type: Mini Centronics Type-14 Port Type: Other Handle 0x0007, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A2A Internal Connector Type: None External Reference Designator: COM A External Connector Type: DB-9 male Port Type: Serial Port 16550A Compatible Handle 0x0008, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2A2B Internal Connector Type: None External Reference Designator: Video External Connector Type: DB-15 female Port Type: Video Port Handle 0x0009, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J3A1 Internal Connector Type: None External Reference Designator: USB1 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J3A1 Internal Connector Type: None External Reference Designator: USB2 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J3A1 Internal Connector Type: None External Reference Designator: USB3 External Connector Type: Access Bus (USB) Port Type: USB Handle 0x000C, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9A1 - TPM HDR Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000D, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9C1 - PCIE DOCKING CONN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2B3 - CPU FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x000F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6C2 - EXT HDMI Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0010, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J3C1 - GMCH FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0011, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1D1 - ITP Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0012, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9E2 - MDC INTPSR Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0013, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9E4 - MDC INTPSR Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0014, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9E3 - LPC HOT DOCKING Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0015, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9E1 - SCAN MATRIX Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0016, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J9G1 - LPC SIDE BAND Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0017, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J8F1 - UNIFIED Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0018, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J6F1 - LVDS Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x0019, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2F1 - LAI FAN Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001A, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J2G1 - GFX VID Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other Handle 0x001B, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1G6 - AC JACK Internal Connector Type: Other External Reference Designator: Not Specified External Connector Type: None Port Type: Other phil@phil-gl753vd:~$ Soluble ? ... and how ? Thank You | Hetzer wrote: 2024-01-11 12:08 Do ye rebember if these ports have ever worked at all? Was that laptop dismantled before? There's possibilty that something wasn't connected properly, so it doesn't work I highly doubt if it's a system-level problem, since nearly every USB controller hub is recognizable by linux Concerns a laptop I took over from a friend that was running under windows10 but could not be upgraded to the current Windows11 ... because of the too old CPU ( sic ) . Can still vaguely remember that I had quite some trouble throwing Windows10 off it and installing Debian in its place ( Single Boot ) . What did I do ? - Removed the HDD and kept only the 128 GB NVMe drive . - took the laptop to my dealer to reinstall Windows10 to enable me to disable Windows Boot Manager : cmd as administrator > bcdedit /set {bootmgr} timeout 0 . - Finally installed Debian Single Boot on it . Has worked perfectly since and until now ( cross fingers ) . Translated with DeepL.com (free version) Code: Select allphil@phil-gl753vd:~$ inxi -Fxpmrz System: Kernel: 6.1.0-17-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Cinnamon v: 5.6.8 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Laptop System: ASUSTeK product: GL753VD v: 1.0 serial: <superuser required> Mobo: ASUSTeK model: GL753VD v: 1.0 serial: <superuser required> UEFI: American Megatrends v: GL753VD.308 date: 04/29/2019 Battery: ID-1: BAT0 charge: 37.3 Wh (96.1%) condition: 38.8/47.5 Wh (81.7%) volts: 16.0 min: 14.4 model: Simplo SDI ICR18650 status: not charging Memory: RAM: total: 7.64 GiB used: 2.67 GiB (34.9%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. CPU: Info: quad core model: Intel Core i7-7700HQ bits: 64 type: MT MCP arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 6 MiB Speed (MHz): avg: 799 high: 800 min/max: 800/3800 cores: 1: 799 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 44798 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Graphics: Device-1: Intel HD Graphics 630 vendor: ASUSTeK driver: i915 v: kernel arch: Gen-9.5 bus-ID: 00:02.0 Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: ASUSTeK driver: nouveau v: kernel arch: Pascal bus-ID: 01:00.0 temp: 32.0 C Device-3: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo bus-ID: 1-11:5 Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 630 (KBL GT2) direct-render: Yes Audio: Device-1: Intel CM238 HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 API: ALSA v: k6.1.0-17-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active Server-2: PulseAudio v: 16.1 status: off (using pipewire-pulse) Network: Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: <filter> Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: d000 bus-ID: 03:00.0 IF: enp3s0 state: down mac: <filter> Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-9:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: <filter> Drives: Local Storage: total: 119.24 GiB used: 35.23 GiB (29.5%) ID-1: /dev/sda vendor: SK Hynix model: HFS128G39TND-N210A size: 119.24 GiB Partition: ID-1: / size: 114.53 GiB used: 35.22 GiB (30.8%) fs: ext4 dev: /dev/sda2 ID-2: /boot/efi size: 299.4 MiB used: 5.8 MiB (1.9%) fs: vfat dev: /dev/sda1 Swap: ID-1: swap-1 type: partition size: 2.02 GiB used: 0 KiB (0.0%) dev: /dev/sda3 Sensors: System Temperatures: cpu: 44.0 C pch: 43.5 C mobo: N/A gpu: nouveau temp: 32.0 C Fan Speeds (RPM): cpu: 0 Repos: Packages: 2372 Active apt repos in: /etc/apt/sources.list 1: deb https://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware 2: deb https://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware 3: deb https://security.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware Active apt repos in: /etc/apt/sources.list.d/eid.list 1: deb https://files.eid.belgium.be/debian bookworm main Info: Processes: 231 Uptime: 8h 24m Init: systemd target: graphical (5) Compilers: gcc: 12.2.0 Shell: Bash v: 5.2.15 inxi: 3.3.26 phil@phil-gl753vd:~$ |
Hi, After a year or so I finally was able to get my bluetooth devices working on my Debian computers but one issue remains which are the constant popups I get which are caused by my mouse connecting and reconnecting. As per an older post I read on this forum this may be a power saving issue which causes the constant connecting/reconnecting. Functionally the mouse and bluetooth work fine with no issues but the constant popups which occur every 2-5 minutes require me to close those popup windows. These popups seem to be a new feature with Debian 12 as I don't see them on Debian 11. Does anyone know how to disable the popup windows which show that a device has been connected/disconnected? I apologize if this is a quick and simple solution that one can look up on a search engine but currently I only have access to this forum for Debian related help. Thanks. | You didn't mention which bluetooth manager you use but assuming you're using blueman - right-click the tray icon, select "Plugins" and uncheck the "ConnectionNotifier" plugin. Hope this helps - |
hi, i had install KDE plasma. i had sound on DEB10, but after upgrade to DEB12, i lost it. it seems to have a problem with intel chipset HD sound device. AMD graphical card take the sound at place. but no sound possible with my screens... these are some command helping you to help me. XD. thanks in advance. VERSION : (automatic package update for intel microfsoftware this morning but no change.) Linux XXXXX 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) x86_64 GNU/Linux LSPCI: Code: Select all00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series] APLAY: Code: Select all**** Liste des périphériques matériels PLAYBACK **** carte 1 : HDMI [HDA ATI HDMI], périphérique 3 : HDMI 0 [HDMI 0] Sous-périphériques : 1/1 Sous-périphérique #0 : subdevice #0 carte 1 : HDMI [HDA ATI HDMI], périphérique 7 : HDMI 1 [HDMI 1] Sous-périphériques : 1/1 Sous-périphérique #0 : subdevice #0 PACTL: Code: Select allCarte #40 Nom : alsa_card.pci-0000_01_00.1 Pilote : alsa Module propriétaire : n/d Propriétés : api.acp.auto-port = "false" api.acp.auto-profile = "false" api.alsa.card = "1" api.alsa.card.longname = "HDA ATI HDMI at 0xf1140000 irq 138" api.alsa.card.name = "HDA ATI HDMI" api.alsa.path = "hw:1" api.alsa.use-acp = "true" api.dbus.ReserveDevice1 = "Audio1" device.api = "alsa" device.bus = "pci" device.bus_path = "pci-0000:01:00.1" device.description = "Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]" device.enum.api = "udev" device.icon_name = "audio-card-analog-pci" device.name = "alsa_card.pci-0000_01_00.1" device.nick = "HDA ATI HDMI" device.plugged.usec = "4939935" device.product.id = "0xaab0" device.product.name = "Oland/Hainan/Cape Verde/Pitcairn HDMI Audio [Radeon HD 7000 Series]" device.subsystem = "sound" sysfs.path = "/devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1" device.vendor.id = "0x1002" device.vendor.name = "Advanced Micro Devices, Inc. [AMD/ATI]" media.class = "Audio/Device" factory.id = "14" client.id = "33" object.id = "40" object.serial = "40" object.path = "alsa:pcm:1" alsa.card = "1" alsa.card_name = "HDA ATI HDMI" alsa.long_card_name = "HDA ATI HDMI at 0xf1140000 irq 138" alsa.driver_name = "snd_hda_intel" device.string = "1" Profils : off: Éteint (sinks: 0, sources: 0, priority: 0, available: oui) output:hdmi-stereo: Sortie Stéréo numérique (HDMI) (sinks: 1, sources: 0, priority: 5900, available: non) output:hdmi-stereo-extra1: Sortie Digital Stereo (HDMI 2) (sinks: 1, sources: 0, priority: 5700, available: non) output:hdmi-surround: Sortie Surround numérique 5.1 (HDMI) (sinks: 1, sources: 0, priority: 800, available: non) output:hdmi-surround71: Sortie Digital Surround 7.1 (HDMI) (sinks: 1, sources: 0, priority: 800, available: non) output:hdmi-surround-extra1: Sortie Digital Surround 5.1 (HDMI 2) (sinks: 1, sources: 0, priority: 600, available: non) output:hdmi-surround71-extra1: Sortie Digital Surround 7.1 (HDMI 2) (sinks: 1, sources: 0, priority: 600, available: non) pro-audio: Pro Audio (sinks: 2, sources: 0, priority: 1, available: oui) Profil actif : pro-audio Ports : hdmi-output-0: HDMI / DisplayPort (type: HDMI, priority: 5900, latency offset: 0 usec, availability group: Legacy 1, not available) Propriétés : port.type = "hdmi" port.availability-group = "Legacy 1" device.icon_name = "video-display" card.profile.port = "0" Partie du(des) profil(s) : output:hdmi-stereo, output:hdmi-surround, output:hdmi-surround71 hdmi-output-1: HDMI / DisplayPort 2 (type: HDMI, priority: 5800, latency offset: 0 usec, availability group: Legacy 2, not available) Propriétés : port.type = "hdmi" port.availability-group = "Legacy 2" device.icon_name = "video-display" card.profile.port = "1" Partie du(des) profil(s) : output:hdmi-stereo-extra1, output:hdmi-surround-extra1, output:hdmi-surround71-extra1 fuser -v /dev/snd: Code: Select allUTIL. PID ACCÈS COMMANDE /dev/snd/controlC1: megs 846 F.... wireplumber /dev/snd/seq: megs 845 F.... pipewire | I had no sound upgrading to Bookworm from Bullseye. Fixed by: Code: Select allapt purge pipewire wireplumber then checked the correct sound card was selected in pavucontrol and alsamixer, and volumes were up and channels unmuted in alsamixer. KDE Plasma in Bookworm still uses Pulseaudio in a default install, but for some reason Pipewire packages are pulled in when upgrading from Bullseye. |
Since doing a clean install of Debian 12, my hard drive activity light continuously runs. I have checked processes, memory usage and everything seems to be okay. I've also verified that the drive and the hardware is okay and they are. Still the light stays on and programs load really slowly. Any ideas? | Hello, rervin wrote: 2024-01-19 19:27 Still the light stays on and programs load really slowly. Just guessing: could it be that the kernel is continuously detecting disk errors ? You can check taking a look at system logs. --- note: moved to "Hardware" sub-forum |
Hi So I've had some networking issues for a while now, and I'm starting to suspect there might have been at least two separate issues at the same time. Long story short, I've had sudden loss of ethernet connection at random times and logs showed a lot of the link going up and down in a short time span, interspersed with other networking messages. At first I thought there were physical issues with my then-aging system (like the network port on the motherboard not working properly), so I tried a few different things there like a usb dongle and changing ethernet cables, before I recently upgraded most of my components without that changing anything about this issue. So, I recently decided I had to try to eliminate as many variables as possible from the equation, which included a switch, so I bought a long cable and I'm now directly connected to the main modem. As of right now, I believe one part of the issue might be gone: I haven't yet experienced sudden loss of internet for no apparent reason. One part of the problem remains, however, although perhaps in a slightly different form: When I first boot -- and this happens every time now, consistently -- the interface seems to start up with 1000 mb/s for a few seconds before suddenly going to 100 mb/s after some messages which have been part of what I've been seeing in logs for the "old" problem too -- which leads me to believe there might have been at least two issues, or perhaps that this is indicative of the main issue and maybe that the switch being in the path before somehow made the situation worse. So for journalctl output, this is where it seems to be happening (I removed some entries in between here that said something about my user account logon): Code: Select allaug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.6633] device (enp5s0): carrier: link connected aug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.6639] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'man> aug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.6654] policy: auto-activating connection 'Wired connection 1' (a06f5c71-4ecf-4fbb-8a8c-f10354a3490b) aug. 07 17:16:33 COMPUTOR kernel: igc 0000:05:00.0 enp5s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX aug. 07 17:16:33 COMPUTOR kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready aug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.6660] device (enp5s0): Activation: starting connection 'Wired connection 1' (a06f5c71-4ecf-4fbb-8a8c-f10354a3490b) aug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.6661] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') aug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.6664] manager: NetworkManager state is now CONNECTING aug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.7507] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') aug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.7512] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') aug. 07 17:16:33 COMPUTOR NetworkManager[929]: <info> [1691421393.7515] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds) aug. 07 17:16:33 COMPUTOR avahi-daemon[869]: Joining mDNS multicast group on interface enp5s0.IPv6 with address fe80::a6ad:2c4d:4f1c:749c. aug. 07 17:16:33 COMPUTOR avahi-daemon[869]: New relevant interface enp5s0.IPv6 for mDNS. aug. 07 17:16:33 COMPUTOR avahi-daemon[869]: Registering new address record for fe80::a6ad:2c4d:4f1c:749c on enp5s0.*. aug. 07 17:16:34 COMPUTOR systemd[1]: systemd-rfkill.service: Deactivated successfully. aug. 07 17:16:36 COMPUTOR NetworkManager[929]: <info> [1691421396.4272] device (enp5s0): carrier: link connected aug. 07 17:16:36 COMPUTOR kernel: igc 0000:05:00.0 enp5s0: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX aug. 07 17:16:36 COMPUTOR NetworkManager[929]: <info> [1691421396.6737] dhcp6 (enp5s0): activation: beginning transaction (timeout in 45 seconds) aug. 07 17:16:36 COMPUTOR NetworkManager[929]: <info> [1691421396.6740] policy: set 'Wired connection 1' (enp5s0) as default for IPv6 routing and DNS aug. 07 17:16:36 COMPUTOR avahi-daemon[869]: Leaving mDNS multicast group on interface enp5s0.IPv6 with address fe80::a6ad:2c4d:4f1c:749c. aug. 07 17:16:36 COMPUTOR avahi-daemon[869]: Joining mDNS multicast group on interface enp5s0.IPv6 with address 2a01:799:1b9e:1b00:7468:56a4:1d1a:78e5. aug. 07 17:16:36 COMPUTOR avahi-daemon[869]: Registering new address record for 2a01:799:1b9e:1b00:7468:56a4:1d1a:78e5 on enp5s0.*. aug. 07 17:16:36 COMPUTOR avahi-daemon[869]: Withdrawing address record for fe80::a6ad:2c4d:4f1c:749c on enp5s0. aug. 07 17:16:36 COMPUTOR NetworkManager[929]: <info> [1691421396.6778] dhcp6 (enp5s0): state changed new lease If I use ethtool -s enp5s0 speed 1000, it goes to 1000 and thus far, it hasn't dropped down again within one session. I'm hoping someone has any ideas on how to resolve this, so that I don't have to run that command every time I log on? | Hello, You didn't report the model/manufacturer of the network interface card. Can you send the output of the following command ? Code: Select alllspci -d::0200 -nnv From the log in your previous message (kernel name for adapter), it could be an Intel(R) Ethernet Controller I225-LM/I225-V. In this case, you could see this previous discussion: [SOLVED] disabling EEE on I225-V Hope this helps. |
Updating manually (apt update/upgrade) gave many versions of the following error message: "Possible missing firmware /lib/firmware/amdgpu/... for module amdgpu." See below for the complete list. But when I used Synaptic and searched on "amdgpu," I saw that the only relevant item "firmware-amd-graphics," was already installed. How do I fix this? Code: Select allupdate-initramfs: Generating /boot/initrd.img-6.1.0-13-amd64 W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module am dgpu W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdg pu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for mod ule amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdg pu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_11_toc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_10_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_imu.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_rlc.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mec.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_me.bin for module am dgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_pfp.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_rlc.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mec.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_me.bin for module am dgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_pfp.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/sdma_6_0_3.bin for module amdg pu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for mo dule amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for mod ule amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdg pu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_4_mes.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module a mdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_2_mes_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_1_mes_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_mes_2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/smu_13_0_10.bin for module amd gpu | "W:" indicates that this is a warning, not an error. If your GPU drivers function as expected, disregard it. Otherwise, you might look into more recent kernel images and firmware packages from backports. |
Hi, I can anyone please help/advise of a suitable graphics card for Debian 12 that is easy to install. I do not need it for gaming but for heavy image processing and running 2 VM's and 2 monitors. Previously running Debian 11 with a Radeon Pro W3100 which worked ok but cannot get it running on '12'. I have followed online instructions (https://wiki.debian.org/AtiHowTo) to the letter but does not seen to install the 'Barts Microcode' as when I check dmesg there is no listing for Radeon. Reinstalled' firmware-amd-graphics' updated, restarted. Any help would be much appreciated. TIA John | Radeontop is a monitor, the only diagnostics it does is if it runs. Since it did, the gpu is installed and working.? johna1954 wrote: 2024-02-02 16:08 cannot get it running on '12' Upgrade from 11 or a fresh attempt? That card should be using amdgpu? Code: Select alllspci -kd 1002: |
Hello, I have a Thinkpad L390 with Debian 12.4. With the latest kernel image 6.1.0-17 the Bluetooth doesn´t work. From Gnome appear always disabled with no option to enable it. But if I use kernel 6.1.0-16 the Bluetooth works perfectly. Checking dmesg with the kernel 6.1.0-16 I can see this message: Code: Select allsudo dmesg | grep bluetooth [sudo] password for ben: [ 19.046769] bluetooth hci0: firmware: direct-loading firmware intel/ibt-17-16-1.sfi [ 20.490801] bluetooth hci0: firmware: direct-loading firmware intel/ibt-17-16-1.ddc Using the kernel 6.1.0-17 checking the dmesg I can see this message: Code: Select allsudo dmesg |grep bluetooth [sudo] password for ben: [ 2.583949] bluetooth hci0: firmware: failed to load intel/ibt-17-16-1.sfi (-2) [ 2.583964] bluetooth hci0: firmware: failed to load intel/ibt-17-16-1.sfi (-2) From lsusb the bluetooth device is: Code: Select alllsusb Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) And to make it even more strange, it must be said that most of the time with kernel 6.1.0-17 Bluetooth does not work (it always appears disabled with no option to activate), but rarely when restarting Bluetooth does work, only 5% (to say something very low) of the occasions. By now, I always have to reboot and use kernel 6.1.0-16... with this kernel image the bluetooth always works. Thanks, | Hello, You might try installing the package: https://packages.debian.org/bookworm/firmware-iwlwifi It should install the ibt-17-16-1.sfi firmware file. Hope this helps. |
EDIT: Solved. Printer works on Debian 10, Debian 11, Debian 12, and even on non-Debian based Linux distro. Solution is in 2 posts: viewtopic.php?p=792499#p792499 viewtopic.php?p=792483#p792483 On non-Debian based Linux distro the only difference is that proprietary filter file goes into different location. /usr/lib64 instead of /usr/lib. (The same proprietary filter file from Pantum official Ubuntu driver. Code: Select allsudo cp pt2500Filter /usr/lib64/cups/filter/pt2500Filter sudo chmod +x /usr/lib64/cups/filter/pt2500Filter Hello! My Pantum Printer P2500 stopped working after I upgraded to Debian 11.5. It still works well on my other computer with Debian 10. I wrote a letter to Pantum support, but no answer so far. They Provide an Ubuntu driver. I extract pt2500Filter file and put it into /usr/lib/cups/filter/ then I add a printer using 'Print Settings' and choose a 'Pantum-P2500-Series.ppd' file extracted from the driver. Everything worked fine on Debian 11 and 10, but now with Debian 11.5 the printer no longer works. Had anyone experienced the same problem? | If your printer is one of these, then it supports driverless printing. Pantum P2500NW AirPrint™ Pantum P2500NWe AirPrint™ Pantum P2500W AirPrint™ https://openprinting.github.io/printers/ Use of drivers with driverless capable printers in Debian 11 is deprecated, and you should set up the printer using your preferred method as described here: https://wiki.debian.org/CUPSDriverlessPrinting NB, existing USB print queues will fail in Debian 11: the print queue must be driverless. |
Hi all, I use an Intel NUC8i3BEH, which has HDMI CEC and an internal CEC header, which typically is used for the Pulse Eight CEC adapter. I plan to use CEC for a project (not the Pulse Eight adapter, I'm planning CEC communication with an Arduino). I use debian bookworm 64bit, and I installed v4l-utils and cec-utils, but any cec-related command from these packages yields "/dev/cec0 no file or device found". dmesg does not list anything with cec in it. So I was wondering if I need to activate some kernel module or anything else. I've searched the internet half a day long, but documentation is surprisingly scarce. Btw.: I tried all kind of variations in the BIOS. Intel doc's say: To use the internal header, you need to disable HDMI CEC in the BIOS, did this, but also tried with HDMI CEC enabled, to see if the HDMI port CEC registers somehow. Somewhat at a loss right now, any help appreciated! Best Hauke | Hello, _Hauke_ wrote: 2024-02-10 20:27 Hi all, I use an Intel NUC8i3BEH, which has HDMI CEC and an internal CEC header, which typically is used for the Pulse Eight CEC adapter. I plan to use CEC for a project (not the Pulse Eight adapter, I'm planning CEC communication with an Arduino). [..] I've learnt by your post that CEC stands for: CEC (Consumer Electronics Control) is the control protocol found in HDMI®. It seems that the support for CEC devices is from CEC kernel modules: https://sources.debian.org/src/linux/6.1.76-1/drivers/media/cec/ The Linux driver implementer’s API guide » Media subsystem kernel internal API » 6. CEC Kernel Support Since I suppose your arduino device is an USB-CEC adapter, you could start checking if the Linux kernel recognizes the adapter as an USB device with the command: Code: Select alllsusb If yes, you can check what is the usb kernel module (driver) used with the following command from usbutils package: Code: Select allusb-devices You can also check system logs for messages: Code: Select allsu -l -c "journalctl -b --no-pager -g cec" Not all CEC kernel modules are active by default in Debian kernels: Code: Select all$ grep CONFIG_CEC /boot/config-$(uname -r) CONFIG_CEC_CORE=m CONFIG_CEC_NOTIFIER=y # CONFIG_CEC_CH7322 is not set # CONFIG_CEC_CROS_EC is not set # CONFIG_CEC_GPIO is not set CONFIG_CEC_SECO=m # CONFIG_CEC_SECO_RC is not set Therefore, if you are using a CEC device that is supported by a currently inactive kernel module, you will need to recompile the kernel to enable it. Hope this helps. Let me know. |
I have a Lenovo M5400 laptop with rtl8723be wireless card. Previous user told me that wifi card is probably broken. He has been running Ubuntu on it a few years ago. And, in fact, wifi does not work. But card is - at least partially - alive. I'm using ifupdown & wpasupplicant. The symptoms are: ifup wlp4s0 ends with dhclient timeout after many attempts to obtain an IP addressenable_network in wpa_cli goes into slow, infinite loop of "SCAN-STARTED... SCAN-RESULTS... NETWORK_NOT-FOUND..."manually scanning for networks with wpa_cli randomly shows all APs, or none Example: /etc/wpa_supplicant/wpa_supplicant.conf:Code: Select allctrl_interface=/run/wpa_supplicant update_config=1 # I've successfully tested it with an USB wireless adapter network={ ssid="<my network ssid>" psk="<password>" mesh_fwding=1 disabled=1 } I launch manually wpa supplicant Code: Select allwpa_supplicant -B -i wlp4s0 -c /etc/wpa_supplicant/wpa_supplicant.conf then Code: Select allroot@hostname:~# wpa_cli wpa_cli v2.10 Copyright (c) 2004-2022, Jouni Malinen <j@w1.fi> and contributors This software may be distributed under the terms of the BSD license. See README for more details. Selected interface 'wlp4s0' Interactive mode >Everything goes well up to this moment. Then I run the scan:Code: Select all> scan OK <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE <3>CTRL-EVENT-NETWORK-NOT-FOUND > scan_results bssid / frequency / signal level / flags / ssid 6c:ba:b8:8c:8a:10 2462 -16 [WPA2-PSK-CCMP][WPS][ESS] <my network ssid>Awesome, let's connect to this AP!Code: Select all> enable_network 0 OK <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE <3>SME: Trying to authenticate with 6c:ba:b8:8c:8a:10 (SSID='<my network ssid>' freq=2462 MHz) <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE <3>SME: Trying to authenticate with 6c:ba:b8:8c:8a:10 (SSID='<my network ssid>' freq=2462 MHz) <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE <3>SME: Trying to authenticate with 6c:ba:b8:8c:8a:10 (SSID='<my network ssid>' freq=2462 MHz) <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS <3>WPS-AP-AVAILABLE <3>CTRL-EVENT-NETWORK-NOT-FOUND <3>CTRL-EVENT-SCAN-STARTED <3>CTRL-EVENT-SCAN-RESULTS #and so on forever, only the "WPS-AP-AVAILABLE" message doesn't show up anymoreOccasionally, after some time I manage to get apropriate results from 'scan' command. Sometimes it does not work at all just after boot. I've been browsing the web for solutions for couple of months. Things I've already done: [set parameters in /etc/modprobe.d/rtl8723be.conf: ant_sel, fwlps, ips to values other than default (one at a time) and rebooted (after every change)checked the journal for firmware related stuff - it's clean.checked if this device is suported by firmware-realtek packageinstalled firmware-misc-nonfreechecked if the appropriate firmware is loadedtaken the laptop apart and checked if antennas are not damaged and connected correctly into wireless adaptermany other things I forgot to mention Any ideas what to try next? Maybe just thow the adapter away and buy a new one? What do you think about it? I can provide more info, just tell me what do you would like to see. | Hello @dashek, It would be useful to check: whether the regional settings of the wireless card configuration are compatible with those of the wireless access point if both the wireless card and the AP are able to transmit using the same WiFi protocol and can use the same WiFi channel Hope this helps. |
Hello all, Broadcom BCM57416 NetXtreme-E dual port 10Gb on a Thinkstation P520 with Debian 12.1 does not work after resume (onboard Intel NIC works fine): any help much appreciated!! Thank you. Code: Select all[16965.702706] bnxt_en 0000:17:00.0 enp23s0f0np0: Error (timeout: 500015) msg {0x0 0xe0} len:0 [16965.702722] bnxt_en 0000:17:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -19 [16965.702739] bnxt_en 0000:17:00.0: PM: failed to resume async: error -19 ... [16966.628444] bnxt_en 0000:17:00.1 enp23s0f1np1: Error (timeout: 500015) msg {0x0 0x4196} len:0 [16966.628460] bnxt_en 0000:17:00.1: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -19 [16966.628475] bnxt_en 0000:17:00.1: PM: failed to resume async: error -19 .... [16968.383356] bnxt_en 0000:17:00.0 enp23s0f0np0: Error (timeout: 500015) msg {0xb0 0xe1} len:0 [16968.383363] bnxt_en 0000:17:00.0 enp23s0f0np0: hwrm stat ctx alloc failure rc: fffffff0 [16968.383388] bnxt_en 0000:17:00.0 enp23s0f0np0: bnxt_init_nic err: fffffff0 [16969.253653] bnxt_en 0000:17:00.1 enp23s0f1np1: Error (timeout: 500015) msg {0xb0 0x4197} len:0 [16969.253661] bnxt_en 0000:17:00.1 enp23s0f1np1: hwrm stat ctx alloc failure rc: fffffff0 [16969.253670] bnxt_en 0000:17:00.1 enp23s0f1np1: bnxt_init_nic err: fffffff0 Last but not least a huge THANKS to the Debian Community for your efforts on Debian 12 - it's amazing that such an high-quality software comes for free! | Hello, classicdeb wrote: 2023-09-14 07:50 Broadcom BCM57416 NetXtreme-E dual port 10Gb on a Thinkstation P520 with Debian 12.1 does not work after resume (onboard Intel NIC works fine) Is the "Broadcom BCM57416 NetXtreme-E dual port" a PCI board ? If yes, report back the lspci output for the device. You may try disabling "Energy Efficient Ethernet (EEE) settings" before entering suspension; see: README Notes Broadcom bnxt_en Linux Driver Version 1.8.1 07/11/2017 You may also access computer BIOS for dedicated BIOS entries for the board or for BIOS power saving settings for the board; see "System Level Configuration" in the User's Manual: Broadcom® NetXtreme-E USER’S MANUAL |
Hello, This is my first post to the Debian forums, so please let me know if I need to make any edits to my post. Using the Intel AX210 160MHz WiFi and Bluetooth chip with my desktop leads to non-functional Bluetooth which is stuck in an endless loop of connecting and disconnecting. System Info: Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-14-amd64 (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 lspci output: Code: Select all04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz (rev 1a) sudo systemctl status bluetooth.service output: Code: Select all● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Sat 2023-12-09 11:33:54 MST; 58min ago Docs: man:bluetoothd(8) Main PID: 613 (bluetoothd) Status: "Running" Tasks: 1 (limit: 19033) Memory: 2.6M CPU: 813ms CGroup: /system.slice/bluetooth.service └─613 /usr/libexec/bluetooth/bluetoothd Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: Bluetooth daemon 5.66 Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: Starting SDP server Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Dec 09 11:33:54 ForwardUntoDawn systemd[1]: Started bluetooth.service - Bluetooth service. Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: src/plugin.c:plugin_init() Failed to init vcp plugin Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: src/plugin.c:plugin_init() Failed to init mcp plugin Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: src/plugin.c:plugin_init() Failed to init bap plugin Dec 09 11:33:54 ForwardUntoDawn bluetoothd[613]: Bluetooth management interface 1.22 initialized lshw -C network shows I have the most updated drivers and firmware installed: Code: Select alldriver=iwlwifi driverversion=6.1.0-14-amd64 firmware=59.601f3a66.0 Scanning through the discussion of this bug report didn't reveal any actionable solutions, and this thread just suggests a kernel rollback. Does anyone know how I can get the Bluetooth functioning for my system using the current Kernel? Or do I need to try the kernel rollback? | Welcome! You could install rfkill, and see if your bluetooth is blocked Code: Select allsudo apt install rfkill [sudo] arto-käyttäjän salasana: Luetaan pakettiluetteloita... Valmis Muodostetaan riippuvuussuhteiden puu... Valmis Luetaan tilatiedot... Valmis rfkill is already the newest version (2.38.1-5+b1). 0 päivitetty, 0 uutta asennusta, 0 poistettavaa ja 0 päivittämätöntä. Code: Select allarto@dell:~$ sudo rfkill ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 30 bluetooth hci0 unblocked unblocked arto@dell:~$ Debian wiki is good place to Debian users, I have no direct answer, but check this https://wiki.debian.org/BluetoothUser |
This USB Bluetooth does not work in Debian 12, it is detected but when I scan for new bluetooth devices using bluetoothctl the list is empty. I have installed firmware-realtek, bluez and other related packages Code: Select all➜ sudo rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Code: Select all➜ ls /lib/firmware/rtl_bt rtl8192ee_fw.bin rtl8723b_fw.bin rtl8723bs_fw.bin rtl8761a_fw.bin rtl8761bu_config.bin rtl8821a_config.bin rtl8821c_fw.bin rtl8822cs_config.bin rtl8822cu_fw.bin rtl8852bu_config.bin rtl8852cu_fw.bin rtl8192eu_fw.bin rtl8723bs_config-OBDA0623.bin rtl8723d_config.bin rtl8761b_config.bin rtl8761bu_fw.bin rtl8821a_fw.bin rtl8822b_config.bin rtl8822cs_fw.bin rtl8852au_config.bin rtl8852bu_fw.bin rtl8723a_fw.bin rtl8723bs_config-OBDA8723.bin rtl8723d_fw.bin rtl8761b_fw.bin rtl8812ae_fw.bin rtl8821c_config.bin rtl8822b_fw.bin rtl8822cu_config.bin rtl8852au_fw.bin rtl8852cu_config.bin Code: Select all➜ sudo dmesg | egrep -i 'blue|firm' [ 0.375468] Spectre V2 : Enabling Restricted Speculation for firmware calls [ 0.585679] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 0.594792] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge [ 2.356880] usb 1-9: Product: Bluetooth Radio [ 4.036173] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_sos.bin [ 4.036194] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_ta.bin [ 6.603402] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_smc.bin [ 6.603458] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_dmcub.bin [ 6.603460] [drm] Loading DMUB firmware via PSP: version=0x02020017 [ 6.603497] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_pfp.bin [ 6.603530] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_me.bin [ 6.603559] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_ce.bin [ 6.603577] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_rlc.bin [ 6.603610] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_mec.bin [ 6.603650] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_mec2.bin [ 6.603998] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_sdma.bin [ 6.604104] amdgpu 0000:0a:00.0: firmware: direct-loading firmware amdgpu/dimgrey_cavefish_vcn.bin [ 6.604106] [drm] Found VCN firmware Version ENC: 1.26 DEC: 2 VEP: 0 Revision: 0 [ 6.604110] amdgpu 0000:0a:00.0: amdgpu: Will use PSP to load VCN firmware [ 239.615489] Bluetooth: Core ver 2.22 [ 239.615500] NET: Registered PF_BLUETOOTH protocol family [ 239.615501] Bluetooth: HCI device and connection manager initialized [ 239.615504] Bluetooth: HCI socket layer initialized [ 239.615505] Bluetooth: L2CAP socket layer initialized [ 239.615507] Bluetooth: SCO socket layer initialized [ 240.541776] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 240.541778] Bluetooth: BNEP filters: protocol multicast [ 240.541782] Bluetooth: BNEP socket layer initialized [ 240.542484] Bluetooth: MGMT ver 1.22 [ 240.555356] Bluetooth: RFCOMM TTY layer initialized [ 240.555361] Bluetooth: RFCOMM socket layer initialized [ 240.555364] Bluetooth: RFCOMM ver 1.11 [ 240.762457] r8169 0000:07:00.0: firmware: direct-loading firmware rtl_nic/rtl8168h-2.fw In Fedora it does work Code: Select all➜ dmesg | egrep -i 'blue|firm' [ 0.427171] Spectre V2 : Enabling Restricted Speculation for firmware calls [ 0.590108] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 0.616158] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge [ 2.075157] usb 1-9: Product: Bluetooth Radio [ 7.465174] [drm] Loading DMUB firmware via PSP: version=0x02020020 [ 7.466425] [drm] Found VCN firmware Version ENC: 1.27 DEC: 2 VEP: 0 Revision: 0 [ 7.466432] amdgpu 0000:0a:00.0: amdgpu: Will use PSP to load VCN firmware [ 30.243660] systemd[1]: systemd-pcrmachine.service - TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f). [ 30.832783] Bluetooth: Core ver 2.22 [ 30.832798] NET: Registered PF_BLUETOOTH protocol family [ 30.832800] Bluetooth: HCI device and connection manager initialized [ 30.832804] Bluetooth: HCI socket layer initialized [ 30.832806] Bluetooth: L2CAP socket layer initialized [ 30.832813] Bluetooth: SCO socket layer initialized [ 30.912915] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 30.915909] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 30.915913] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 30.959862] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 30.960208] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 [ 31.708023] Bluetooth: hci0: RTL: fw version 0xdfc6d922 [ 31.904780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 31.904783] Bluetooth: BNEP filters: protocol multicast [ 31.904786] Bluetooth: BNEP socket layer initialized [ 31.905628] Bluetooth: MGMT ver 1.22 [ 36.934573] Bluetooth: RFCOMM TTY layer initialized [ 36.934581] Bluetooth: RFCOMM socket layer initialized [ 36.934585] Bluetooth: RFCOMM ver 1.11 | @bluetoothbroken great work! Hardware support, particularly for recent hardware, is often added to newer kernels. Please mark the topic solved by editing the title in your first post to add prefix [Solved] so it may help others with a similar issue. |
Hi, am new in this forum. I have many different problem with Debian 12 on a MacBook Pro (mid 2012): 1. I can only work with the driver b43 firmware-b43-installer but is very slow. 12Mbps Down and 12Mbps Up 2- When I try to install private driver broadcom-sta-dkms this doesnt exist, just said that other package mentioned 3- I downloaded manual driver from debian web package and I installed with dpkg -i (I blocked other modules with modprobe b43, etc, etc) and the system crash. Just uninstalled the driver and the system works again. I re-installed the b43 dirver but again... to slow. Any one knows what happen with de package broadcom-sta-dkms? | broadcom-sta-dkms is in the repos non-free section - https://packages.debian.org/search?keyw ... m-sta-dkms Are you sure you have non-free in your sources? Also there is a bug report for the current kernel which I think affects this. A new kernel should be available shortly with a fix. Also drivers and firmware are different things, you need both. |
Hi all, I installed from scratch (erasing everything) Debian 12 bookworm on an HP Laptop 14s-dq0xxx, however whereas on Windows 11 the earphones worked perfectly, on Debian 12 the earphones fail to be detected. Here's `inxi -Fxxxrz && aplay -l' output: Code: Select allSystem: Kernel: 6.1.0-13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: i3 v: 4.23-7-g69f68dcd info: i3bar vt: 7 dm: LightDM v: 1.26.0 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Laptop System: HP product: HP Laptop 14s-dq0xxx v: N/A serial: <superuser required> Chassis: type: 10 serial: <superuser required> Mobo: HP model: 864D v: 58.20 serial: <superuser required> UEFI: AMI v: F.30 date: 07/04/2023 Battery: ID-1: BAT0 charge: 37.2 Wh (89.4%) condition: 41.6/41.6 Wh (100.0%) volts: 12.5 min: 11.4 model: HP Primary type: Li-ion serial: N/A status: discharging CPU: Info: quad core model: Intel Celeron N4120 bits: 64 type: MCP smt: <unsupported> arch: Goldmont Plus rev: 8 cache: L1: 224 KiB L2: 4 MiB Speed (MHz): avg: 1106 high: 1625 min/max: 800/2600 cores: 1: 800 2: 1625 3: 800 4: 1200 bogomips: 8755 Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel GeminiLake [UHD Graphics 600] vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-9 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:3185 class-ID: 0300 Device-2: Quanta HP TrueVision HD Camera type: USB driver: uvcvideo bus-ID: 1-6:3 chip-ID: 0408:5365 class-ID: 0e02 Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93") Monitor-1: eDP-1 model: AU Optronics 0xdc90 res: 1920x1080 hz: 60 dpi: 158 size: 309x174mm (12.17x6.85") diag: 355mm (14") modes: 1920x1080 API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 600 (GLK 2) direct-render: Yes Audio: Device-1: Intel Celeron/Pentium Silver Processor High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:0e.0 chip-ID: 8086:3198 class-ID: 0403 API: ALSA v: k6.1.0-13-amd64 status: kernel-api Server-1: PulseAudio v: 16.1 status: active Network: Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard driver: rtw_8822ce v: N/A pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:c822 class-ID: 0280 IF: wlo1 state: up mac: <filter> Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-5:2 chip-ID: 0bda:b00c class-ID: e001 serial: <filter> Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1 sub-v: abd3 hci-v: 5.1 rev: ffb8 Drives: Local Storage: total: 58.24 GiB used: 8.4 GiB (14.4%) ID-1: /dev/mmcblk0 vendor: SanDisk model: DA4064 size: 58.24 GiB type: SSD serial: <filter> rev: 0x8 scheme: GPT Partition: ID-1: / size: 18.91 GiB used: 4.17 GiB (22.1%) fs: ext4 dev: /dev/dm-1 mapped: satyr--vg-root ID-2: /boot size: 455.1 MiB used: 80.9 MiB (17.8%) fs: ext2 dev: /dev/mmcblk0p2 ID-3: /boot/efi size: 511 MiB used: 5.8 MiB (1.1%) fs: vfat dev: /dev/mmcblk0p1 ID-4: /home size: 36.03 GiB used: 4.14 GiB (11.5%) fs: ext4 dev: /dev/dm-3 mapped: satyr--vg-home Swap: ID-1: swap-1 type: partition size: 976 MiB used: 0 KiB (0.0%) priority: -2 dev: /dev/dm-2 mapped: satyr--vg-swap_1 Sensors: System Temperatures: cpu: 36.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: Packages: pm: dpkg pkgs: 1397 Active apt repos in: /etc/apt/sources.list 1: deb http://deb.debian.org/debian/ bookworm main non-free-firmware 2: deb-src http://deb.debian.org/debian/ bookworm main non-free-firmware 3: deb http://security.debian.org/debian-security bookworm-security main non-free-firmware 4: deb-src http://security.debian.org/debian-security bookworm-security main non-free-firmware Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main Active apt repos in: /etc/apt/sources.list.d/i3-autobuild.list 1: deb https://baltocdn.com/i3-window-manager/i3/i3-autobuild/ all main Info: Processes: 170 Uptime: 8m wakeups: 25763 Memory: 3.64 GiB used: 1.75 GiB (47.9%) Init: systemd v: 252 target: graphical (5) default: graphical Compilers: N/A Shell: Bash v: 5.2.15 running-in: x-terminal-emul inxi: 3.3.26 Code: Select all**** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC236 Analog [ALC236 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 Let me know if you require any other output. Has anyone else ran into this same issue with their setup/HP laptop or any other type of laptop? | Unmute headphone jack in alsamixer. You might need to change the card, if I remember that it was F6, It is quite long since I used alsa, but alsamixer has quite good explanations for each key/command, |
I Only use my HP LaserJet PRO M426dfw printer about twice a year. I haven't had a need to do two-sided printing since switching to Debian about 18-20 months ago. At one time it did work fine...Set the job option to duplex-long-edge and only use half the paper of a full print job. For whatever reason the current incarnation of the hplip driver is broken. Any attempt to send to a printer, where the duplex option is set, and only the first page (front side) is printed, then the printer hangs forever with the paper stuck in the bowels of the printer until the job is cancelled on the printer itself and the paper is removed. one-sided jobs work flawlessly. hplip version 3.21 (upstream site says printer is supported starting at 3.15) printer connection is via IP/ethernet Suggestions? | What I've discovered is that the only situation where duplex printing works in my use-case is when printing a single physical sheet of paper (front and back). Any attempt to do more than a single page cause the cups system to print the back face of the first page, then hang. Duplex mode is being selected within the end-user app: lowriter, okular, whatever, from the print pulldown. Nothing like the efficiency of having to print a 200 page document two pages at a time, Yee Haw...love FOSS! |
Here's again this forum's nightmare, me lol So, finally everything is set up, Debian is working great but... my printer is not. I tried using the step by step guide provided by @Hallvor here: viewtopic.php?t=155919 , using Code: Select allcups. I'm asked to find and upload a ppd file for my printer, which I found on a website???? I also managed to find the printer's driver on the website of the manufacturer, in the form of a tarball.gz (I don't have any clue about how to install it or even if I better don't). Anyways, I uploaded this ppd and the printer appeared to be installed on cups (although a message said it was deprecated and probably won't work anymore on next versions of cups). I tried to print a test page but here I receive a notification "Job was stopped", I mean....why? Tried again with the printer that was automatically recognized by Debian (I had two printers at this point and don't even know why lol), same result. I start the job and the job is immediately interrupted and nothing is printed. Tried to delete one of the printers and keep only the "cups one". Nothing changed. Tried to print an actual document. Same. Before doing anything I want to ask your advice. I also created a snapshot via Timeshift, just in case. Please forgive the lenght of my post, but I wanted to be the most accurate I could. Printer model is: Samsung Xpress M2020 series (USB only printer). Thanks in advance, have a nice day. I really appreciate everything you guys do in and for this community. | viewtopic.php?t=150682 ? |
Hi I'm new to Debian, though not to new with Linux as my main computer is running ARCH I've just set up a Lenovo Tiny PC, mainly just for running Home Assistant, just received it, wiped Windows and installed Bookworm, all went well and is working fine. Running kernel version 6.1.0-10 With the Lenovo a Wi-Fi usb was supplied, doing lsucb gives me : Realtek Semiconductor Corp. RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter Have already done sudo apt install firmware-realtek I cannot find any drivers for the RTL8188FTV except https://github.com/1999AZZAR/use-RTL8188FTV-on-linux, but this is for Ubuntu with add a Kelebek Repository but again only for Ubuntu and not Debian So I'm lost, or is it just because this dongle is not really for Debian and if so what should I replace it with ? The dongle works perfectly with my Arch PC but is not recognised by Bookworm, so any help would be appreciated Thanks | Minty95 wrote: 2023-07-19 14:41 would I be correct in doing this https://www.linuxcapable.com/how-to-ins ... ian-linux/ to upgrade the kernel, and will it / is it stable ? or is there a better way ? Not being used to Debian Liquorix kernel is good in Debian. I use it myself and have for a few years, works better for audio production. Whether it will help your situation I have no idea. The only possible gotcha is if you need to use DKMS to build kernel modules such as the Nvidia proprietary driver. The instruction in your link install the kernel metapackage which means upgrades install the latest available Liquorix kernel and sometimes the module releases lag behind. I use Nvidia driver and just add the Liquorix repo and choose Liquorix kernel versions and not the metapackage to get around this. It won't be an issue to try it, you can always boot to a different installed kernel if you need. |
There is several minutes delay for SD cards to be detected and mounted after they have been inserted. I have never seen something like this before. Usually something either works or it doesn't. PC is HP Victus 15-FB1010. Running bookworm with default kernel. dmesg output immediately after inserting an SD card: Code: Select all[ 1956.466086] pcieport 0000:00:02.4: AER: Uncorrected (Non-Fatal) error received: 0000:00:02.4 [ 1956.466115] pcieport 0000:00:02.4: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID) [ 1956.466126] pcieport 0000:00:02.4: device [1022:14ba] error status/mask=00100000/00400000 [ 1956.466135] pcieport 0000:00:02.4: [20] UnsupReq (First) [ 1956.466144] pcieport 0000:00:02.4: AER: TLP Header: 00000000 00000000 00000000 00000000 [ 1956.466243] pcieport 0000:00:02.4: AER: device recovery successful I found (quite by mistake) that I can trick the OS into noticing the SD card if I run "hw-probe" (linux-hardware.org). Code: Select all[ 2286.625609] Non-volatile memory driver v1.3 [ 2292.527721] st: Version 20160209, fixed bufsize 32768, s/g segs 256 [ 2293.846887] mmc0: new high speed SD card at address 1234 [ 2293.854234] mmcblk0: mmc0:1234 SA02G 1.81 GiB When I try to eject the SD card via "Files" I get an error "unable to eject". I physically remove the SD card, and "eject" again and the icon finally goes away. When I re-insert the SD card, dmesg says: Code: Select all[ 2632.858964] ldm_validate_partition_table(): Disk read failed. [ 2632.859007] Dev mmcblk0: unable to read RDB block 0 [ 2632.859067] mmcblk0: unable to read partition table If I run hw-probe again, it is detected and is mounted: Code: Select all[ 3010.649458] mmc0: new high speed SD card at address 1234 [ 3010.650112] mmcblk0: mmc0:1234 SA02G 1.81 GiB [ 3010.651790] mmcblk0: p1 I suspect the root cause is the initial AER / TLP issue, but I don't know where to begin troubleshooting it. Any help would be appreciated! | Off the top of my head the issue may be this scenario has two devices, the reader is one and the media is another. The answer may vary depending on the hardware, but there can be confusion between removing the reader itself or removing the media. I have no examples is memory, but have seen the issue and seem to remember avoiding 'eject' commands and use unmount, then yank. |
I had created a NAS with a Raspberry Pi4B, but got tired of issues with Raspberry OS, and other ARM issues. I bought this NUC to use debian12 amd64. I shrunk the win 11 partition and installed debian12. I can't get debian12 to turn on Bluetooth, but I added a keyboard under win 11. The BIOS has too many settings related to Wi-Fi, and Bluetooth. But since win 11 worked, Bluetooth must be on in bios. Code: Select allBus 001 Device 004: ID 0bda:b85b Realtek Semiconductor Corp. Bluetooth Radio | Hello, What is exactly your bluetooth device ? Take a look at: Debian Wiki - BluetoothUser note: discussion moved from "General Questions" to "Hardware" sub-forum. |
Hi! All was working fine except I realized my headphone jack wasn't working. Debian was detecting something plugged in it but no sound coming out from many headĥones tried. The jack works, I'm sure of this, My actual situation: No more volume icon in systray No more volume control from function keys (F1 to F4) The light on the F4 key (mic un/mute) stays on, not doing the job Other function keys work great Headphone jack still doesn't work. I'd like to at least come back to the point only the headphones jack wasn't working. How this happened I reinstalled pulseaudio, trying to fix my jack (as per a troubleshooting I saw on a forum). I'm a bit confused, since installing pulseaudio fixed my function keys issue and a static problem at the beginning. I checked the shortcuts were still valid and they are. I'm asked to replace the default one already assigned to it when trying assigning it) What did I missed? Any hint were to look at? Below, some infos you might need! -Thanks! Code: Select allSystem: Kernel: 6.1.0-13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_wayland dm: SDDM Distro: Debian GNU/Linux 12 (bookworm) CPU: Info: quad core model: Intel Core i7-6820HQ bits: 64 type: MT MCP arch: Skylake-S rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB Speed (MHz): avg: 800 min/max: 800/3600 cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 43198 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170 API: ALSA v: k6.1.0-13-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active Server-2: PulseAudio v: 16.1 status: off (using pipewire-pulse) Code: Select all**** List of PLAYBACK Hardware Devices **** card 0: PCH [HDA Intel PCH], device 0: ALC3235 Analog [ALC3235 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 | From your user name, I guess you have KDE? Looks like an unexpected Pipewire install (PulseAudio is default in KDE) breaking PulseAudio (the two are known to conflict). Most recently, see here: viewtopic.php?t=157571 |
Hello, I'm running Debian testing on Samsung laptop and most sound devices work great. Speakers work and Bluetooth audio works, no issues. My only problem is with wired headphones, when I plug them in the sound device appears (Headphones Alder Lake PCH-P High Definition Audio Controller) but the sound is really bad. I can't hear anything with volume below 80% and above sound is riddled with crackles and noise. Headphones work fine when plugged into my cell phone. I know Linux sound on laptops is a bit of an issue but is there anything I can upgrade or configure to make my headphones work? Thank you for your help, K | katzen wrote: 2023-06-03 17:13 I can see these (driver) modules being loaded: soundwire_intel snd_hda_intel And a bunch of snd_soc, snd_sof and snd_hda drivers, but these are the hardware drivers. I'm not sure what is the audio framework that's running, I can see these processes: /usr/bin/pipewire /usr/bin/wireplumber /usr/bin/pipewire-pulse Any ideas on how I can find out more about my audio system? Thank you, K For Alder Lake, you will need to make sure the SOF driver is running correctly. Do you have firmware-sof-signed installed? Do you have theses repositories enabled in your /etc/apt/source.list? Code: Select alldeb https://deb.debian.org/debian bookworm main contrib non-free non-free-firmware Please post output of following: Code: Select all# dmesg | grep 'sof\\snd\|audio\|firmware' Code: Select all# journalctl -k | grep -i 'alsa\|hda\|sof\|snd' |
I'm having to manually open alsamixer to change audio output for card sof-essx8336. Suggested solutions have not worked in the six weeks since I've had this laptop. Changing things in the Pulseaudio gui doesn't work, putting the defaults in ~/.asoundrc doesn't. If I'm using headphones I don't need to make the alteration, but the default is as seen in the first image. I'm using Debian 12 64 bit Xfce edition, all updates applied. Thanks for any help. I'm rusty with sorting this sort of thing out and have forgotten a lot so if there's anything else you need to know let me know. | See: viewtopic.php?p=785368&hilit=essx8336#p785368 |
Hello Guys, I just bought this wireless usb adapter but I can't install it. I spent hour to find solution but nothing worked. The given installtion script from ASUS fails (it's 11 years old script..shame) after I went thorugh this : viewtopic.php?t=151730 It seems worked with older kernels but with the latest kernel throws error : Code: Select allroot@debian:/var/lib/dkms/rtl8192fu/5.8.6.2/build# uname -r 6.1.0-13-amd64 ---------------------------------------------------------------------------------------------------- Code: Select allroot@debian:~# dkms build rtl8192fu/5.8.6.2 Sign command: /usr/lib/linux-kbuild-6.1/scripts/sign-file Signing key: /var/lib/dkms/mok.key Public certificate (MOK): /var/lib/dkms/mok.pub Building module: Cleaning build area... 'make' all KVER=6.1.0-13-amd64....(bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-13-amd64 (x86_64) Consult /var/lib/dkms/rtl8192fu/5.8.6.2/build/make.log for more information. ---------------------------------------------------------------------------------------------------- Code: Select allroot@debian:/var/lib/dkms/rtl8192fu/5.8.6.2/build# cat make.log DKMS make.log for rtl8192fu-5.8.6.2 for kernel 6.1.0-13-amd64 (x86_64) Fri Dec 8 04:17:04 PM CET 2023 /bin/sh: 1: bc: not found make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/6.1.0-13-amd64/build M=/var/lib/dkms/rtl8192fu/5.8.6.2/build modules make[1]: Entering directory '/usr/src/linux-headers-6.1.0-13-amd64' /bin/sh: 1: bc: not found CC [M] /var/lib/dkms/rtl8192fu/5.8.6.2/build/core/rtw_cmd.o CC [M] /var/lib/dkms/rtl8192fu/5.8.6.2/build/core/rtw_security.o CC [M] /var/lib/dkms/rtl8192fu/5.8.6.2/build/core/rtw_debug.o /var/lib/dkms/rtl8192fu/5.8.6.2/build/core/rtw_debug.c: In function ‘dump_drv_version’: /var/lib/dkms/rtl8192fu/5.8.6.2/build/core/rtw_debug.c:45:69: error: macro "DATE" might prevent reproducible builds [-Werror=date-time] 45 | RTW_PRINT_SEL(sel, "build time: %s %s ", DATE, TIME); | ^ In file included from /var/lib/dkms/rtl8192fu/5.8.6.2/build/include/drv_types.h:60, from /var/lib/dkms/rtl8192fu/5.8.6.2/build/core/rtw_debug.c:17: /var/lib/dkms/rtl8192fu/5.8.6.2/build/core/rtw_debug.c:45:51: error: macro "TIME" might prevent reproducible builds [-Werror=date-time] 45 | RTW_PRINT_SEL(sel, "build time: %s %s ", DATE, TIME); | ^~~~~~~~ /var/lib/dkms/rtl8192fu/5.8.6.2/build/include/rtw_debug.h:224:46: note: in definition of macro ‘RTW_PRINT_SEL’ 224 | _seqdump(sel, fmt, ##arg) /rtw_warn_on(1)/; | ^~~ cc1: some warnings being treated as errors make[2]: *** [/usr/src/linux-headers-6.1.0-13-common/scripts/Makefile.build:255: /var/lib/dkms/rtl8192fu/5.8.6.2/build/core/rtw_debug.o] Error 1 make[1]: *** [/usr/src/linux-headers-6.1.0-13-common/Makefile:2039: /var/lib/dkms/rtl8192fu/5.8.6.2/build] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-13-amd64' make: *** [Makefile:2328: modules] Error 2 ----------------------------------------------------------------------------------------- This adapter would need a Realtek RTL8192FU driver but I can't find anything which would serve this. Anyone uses this or similar adapted on Bookworm ? Or how can I solve the error above ? I need it very much Thanks in advance | Hello, See this previous discussion: [SOLVED] ASUS USB wifi adapter installation Hope this helps. Let me know. |
Hello all, I am using Debian Bookworm (the latest version) and this WiFi dongle is not working. It came with a CD and looks like the driver is on there. Copying and pasting the driver directory so you can see what RTL it uses: Fenvi Driver/LINUX/RTL8812BU（RTL8822BU_WiFi_linux_v5.2.4.4_25643.20171212_COEX20171012-5044/RTL88x2BU_WiFi_linux_v5.2.4.4_25643.20171212_COEX20171012-5044/driver In the directory /lib/firmware/rtlwifi it has rtl8812efw.bin, rt18812aefw_wowlan.bin, and rtl8822befw.bin. Those are the closest ones I see in that directory related to the one(s) used by the Fenvi WiFi dongle. Unfortunately I have no experience in installing drivers in Linux. Can anyone help me to get this working? Also here is the link to the product for more information if needed: https://www.newegg.com/fenvi-f-ac1200u- ... DXZEAB0193 Thanks. | Hello, DebianMan wrote: 2023-12-08 15:39 Copying and pasting the driver directory so you can see what RTL it uses. Fenvi Driver/LINUX/RTL8812BU（RTL8822BU_WiFi_linux_v5.2.4.4_25643.20171212_COEX20171012-5044/RTL88x2BU_WiFi_linux_v5.2.4.4_25643.20171212_COEX20171012-5044/driver You can see this previous discussion: [Networking] [Solved] Installing RTL8812BU driver in Debian 12 Hope this helps. Let me know. note: moved to "Hardware" sub forum. |
Hello! I need to use Debian 10 because my printer does not support driverless printing and it's drivers only work on Debian 10. I've read that with Alder Lake P (12th generation CPUs) and all future Intel platforms, the GuC firmware and its usage is now mandatory since power management is offloaded to this micro-controller. I want to assemble a new PC. It will have 2 SSDs, one with Debian 10 to work with printer and another with Debian 12 for general use. I need a Intel CPU with integrated graphics and low power usage (preferable), that will work well with Debian 10 (buster). Can I use 11th generation Intel CPU, or do I need to use older models (10th gen, 9th gen, 8th gen)? Thanks! | Your printer issue is going to grow more and more complicated to resolve over time. Have you tried using this printer from a Debian 10 VM? This would solve your issue permanently, and you can test it now. I had to use the Debian Backports kernel on Bullseye (Debian 11) with a 10th gen. |
... I really don't know if the sound was working in the system before the update...! My case is that the ALSA service seems to be working, I can't hear anything through the speakers. systemctl status alsa-state.service ● alsa-state.service - Manage Sound Card State (restore and store) Loaded: loaded (/lib/systemd/system/alsa-state.service; static) Active: active (running) since Sat 2023-12-09 19:17:47 CET; 9min ago Docs: man:alsactl(1) Main PID: 3577 (alsactl) Tasks: 1 (limit: 4727) Memory: 3.0M CPU: 46ms CGroup: /system.slice/alsa-state.service └─3577 /usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime -s -n 19 -c rdaemon On the other hand, I launch this command and... systemctl status alsa-store.service Unit alsa-store.service could not be found. I'm lost... Can anyone give me a hand? | What Frank said^^^. alsactl is part of alsa-utils package which may not be installed by default. Just install it. It has some handy utilities including alsamixer for choosing sound card, and adjusting volumes and mutes. |
I installed Debian 11 from an ISO and as part of the default things it installs is GDM. In GDM by default the audio doesn't work until I add Code: Select alloptions snd-hda-intel dmic_detect=0 to Code: Select all/etc/modprob.d/alsa-base.conf Everything works fine here, however I have to run a provisioning script (we do this for every machine) and part of the provisioning script we have Code: Select all# get rid of the window manager apt remove -y gdm3 apt install -y lightdm systemctl disable lightdm.service So when I run the machine after rebooting I enter tty1 and enter the root accounts credentials. This is all expected, however after I start lightdm by running Code: Select all lightdm and enter the user credentials, I don't have any output devices in my sound settings. Also when I run Code: Select all echo $XDG_RUNTIME_DIR the output is empty so I can see that's not being set when I run lightdm, which is what I suspect is part of the problem. Is there anything I can add to the script to get audio working via the setup we have right now? (logging in as root through tty and starting lightdm) | gamenite-safwaan wrote: 2023-12-22 23:11 (logging in as root through tty and starting lightdm) Nope, not good. As such, your child processes of root do not get a sound server. This is the problem. A typical install should automatically execute lightdm on tty2 with a subsequent graphical user on tty7. ...as I remember, I don't use lightdm much. |
Hi! I installed Debian 12 Bookworm on my old QboxN270 machine. Everything works fine except the RTL8187SE wireless LAN controller. When I connect to my home network, the connection speed is very slow. In fact, it is so slow that I can't even SSH into my machine because the connection breaks every minute or so. Any ideas what is the problem? I am currently using my smartphone in USB-tethering mode to connect to the internet. I am using systemd-networkd to manage my network configuration, systemd-resolved for domain name resolution and iwd to connect to wifi. iwctl station wlan0 show: Code: Select allStation: wlan0 -------------------------------------------------------------------------------- Settable Property Value -------------------------------------------------------------------------------- Scanning no State connected Connected network DIR-615 IPv4 address 192.168.0.250 ConnectedBss 90:94:e4:33:89:cc Frequency 2437 Security WPA2-Personal RSSI -69 dBm AverageRSSI -71 dBm TxBitrate 48000 Kbit/s RxBitrate 1000 Kbit/s ExpectedThroughput 15750 Kbit/s The correct kernel module is loaded: lspci -k: Code: Select all00:00.0 Host bridge: Intel Corporation Mobile 945GSE Express Memory Controller Hub (rev 03) Subsystem: Foxconn International, Inc. Mobile 945GSE Express Memory Controller Hub 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller (rev 03) Subsystem: Foxconn International, Inc. Mobile 945GSE Express Integrated Graphics Controller Kernel driver in use: i915 Kernel modules: i915 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) Subsystem: Foxconn International, Inc. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family PCI Express Port 1 Kernel driver in use: pcieport 00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family PCI Express Port 2 Kernel driver in use: pcieport 00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family PCI Express Port 3 Kernel driver in use: pcieport 00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family USB UHCI Controller Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family USB UHCI Controller Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family USB UHCI Controller Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family USB UHCI Controller Kernel driver in use: uhci_hcd Kernel modules: uhci_hcd 00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family USB2 EHCI Controller Kernel driver in use: ehci-pci Kernel modules: ehci_pci 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) Subsystem: Foxconn International, Inc. 82801 Mobile PCI Bridge 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) Subsystem: Foxconn International, Inc. 82801GBM (ICH7-M) LPC Interface Bridge Kernel driver in use: lpc_ich Kernel modules: intel_rng, lpc_ich, leds_ss4200 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02) Subsystem: Foxconn International, Inc. 82801G (ICH7 Family) IDE Controller Kernel driver in use: ata_piix Kernel modules: ata_piix, ata_generic 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] (rev 02) Subsystem: Foxconn International, Inc. 82801GBM/GHM (ICH7-M Family) SATA Controller [IDE mode] Kernel driver in use: ata_piix Kernel modules: ata_piix, ata_generic 00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02) Subsystem: Foxconn International, Inc. NM10/ICH7 Family SMBus Controller Kernel driver in use: i801_smbus Kernel modules: i2c_i801 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8187SE Wireless LAN Controller (rev 22) Subsystem: Foxconn International, Inc. RTL8187SE Wireless LAN Controller Kernel driver in use: rtl818x_pci Kernel modules: rtl818x_pci 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller (rev 01) Subsystem: Foxconn International, Inc. RTL810xE PCI Express Fast Ethernet controller Kernel driver in use: r8169 Kernel modules: r8169 ip link show: Code: Select all1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000 link/ether 70:1a:04:74:02:a3 brd ff:ff:ff:ff:ff:ff 3: enxe2a3a1e07a5a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 1000 link/ether e2:a3:a1:e0:7a:5a brd ff:ff:ff:ff:ff:ff 4: enp3s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 90:fb:a6:2a:7a:8d brd ff:ff:ff:ff:ff:ff | Do an internet search, e.g., something as simple as linux rtl8187se. It's an old problem and I didn't see any current solutions. Switching to a USB wifi adapter might be your best option. |
Hello all, I am facing the following problem. I bought a Wacom Intuos pro M, which is also recognized immediately by Bookworm/XFCE (current/up to date) (on Dell Latitude 5490). Unfortunately, the Wacom Pen that comes with the tablet is not working as expected. The following: When I write/draw in Xournal++, for example, the pen continues to draw the line (albeit weaker) when I move it to about 1.5 cm away from the tablet (i.e. no longer in direct contact). The same happens in other applications (okular, openboard). For testing purposes I tried the same with Linux Mint (Live version), there this does not happen at least in Xournal++. What is installed: * libwacom * X.Org X Server -- Wacom input driver With Synaptics I don't find any other packages (except application programs) , when I search for wacom. In Xournal++, I can make the continuous stroke almost invisible via the program's internal settings dialogs "Minimum pressure/pressure multiplier" set to lowest value. But you can still see it... I searched and tried in the settings of XFCE, also via the terminal with xsetwacom. But since I don't really understand the various parameters there, it's not surprising that it didn't work. At least, as far as I can see, I was able to reset all settings. Since the problem appears again and again in the net, suggestions can be found there: * Change the pen head (I did - several times - without success). * Leave the pen in the pen holder without the pen nib for one night (sounds like magic) (I did it - without success) * The pen could be damaged - I don't think so, as this doesn't occur on macOS. Is there anyone among you who has a solution or starting point? Of course I will be happy to share more information if it seems necessary to solve the problem. Thanks in advance Peter P.S.: Just now I tried writing/drawing with Krita. There the effect does not occur. | It's been a while since I tested wacom drawing boards, but I remember starting 'linux wacom' web search and then found some link that helped to make system detect mouse and pen separately, and there was even some program which was made to drawing boards. It was in the current stables Bookworm repo but don't even remember that Used that and gimp. Sorry, can't be more specific. |
I'm a new Debian 12 user. Apologies if I haven't provided enough information. I have a dual boot Huawei Matebook D15 laptop. Debian 12 and Windows 11 (laptop came with Windows already on it). Grub is installed. It's a fresh Debian 12 install and sound did not work out of the box. Sound does work on Windows 11. I had a Dummy Output in the Audio Mixer but I fixed that by adding the following Code: Select allsudo nano /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT "snd_intel_dspcfg.dsp_driver=3" I believe that the headphone volume and speaker volume are swapped for some reason. When I mute the headphone output the speakers are muted. This is an alsamixer screenshot. Some other information I have about my setup. Code: Select alluname -r 6.1.0-13-amd64 Code: Select allpactl info Server String: /run/user/1000/pulse/native Library Protocol Version: 35 Server Protocol Version: 35 Is Local: yes Client Index: 77 Tile Size: 65472 User Name: paddy Host Name: PaddyDebian12 Server Name: PulseAudio (on PipeWire 0.3.65) Server Version: 15.0.0 Default Sample Specification: float32le 2ch 48000Hz Default Channel Map: front-left,front-right Default Sink: alsa_output.pci-0000_00_1f.3-platform-sof-essx8336.pro-output-0 Default Source: alsa_input.pci-0000_00_1f.3-platform-sof-essx8336.pro-input-0 Cookie: e420:c342 Code: Select alldmesg | grep sof dmesg: read kernel buffer failed: Operation not permitted Code: Select alllspci -k | grep -A 4 Audio 00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20) Subsystem: QUANTA Computer Inc Tiger Lake-LP Smart Sound Technology Audio Controller Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20) Subsystem: QUANTA Computer Inc Tiger Lake-LP SMBus Controller Code: Select allinxi -A Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: sof-audio-pci-intel-tgl API: ALSA v: k6.1.0-13-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active Code: Select alllspci -nnk | grep -i -A7 audio 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20) Subsystem: QUANTA Computer Inc Tiger Lake-LP Smart Sound Technology Audio Controller [152d:127d] Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 00:1f.4 SMBus [0c05]: Intel Corporation Tiger Lake-LP SMBus Controller [8086:a0a3] (rev 20) Subsystem: QUANTA Computer Inc Tiger Lake-LP SMBus Controller [152d:127d] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller [8086:a0a4] (rev 20) Subsystem: QUANTA Computer Inc Tiger Lake-LP SPI Controller [152d:127d] Code: Select allmodinfo snd_intel_dspcfg filename: /lib/modules/6.1.0-13-amd64/kernel/sound/hda/snd-intel-dspcfg.ko import_ns: SND_INTEL_SOUNDWIRE_ACPI description: Intel DSP config driver license: GPL v2 depends: snd-intel-sdw-acpi retpoline: Y intree: Y name: snd_intel_dspcfg vermagic: 6.1.0-13-amd64 SMP preempt mod_unload modversions sig_id: PKCS#7 signer: Debian Secure Boot CA sig_key: 32:A0:28:7F:84:1A:03:6F:A3:93:C1:E0:65:C4:3A:E6:B2:42:26:43 sig_hashalgo: sha256 signature: 67:65:0C:16:D4:4C:88:48:08:D8:D0:AA:D2:0E:03:01:00:88:B7:C7: 52:99:1A:DF:B8:9E:A1:7E:3A:E2:FE:C2:5F:F0:5E:F0:AB:A0:52:7E: D9:B1:F2:A0:C0:7D:03:EC:FD:B5:DD:05:23:9F:1B:1A:73:13:4D:D2: 5C:FF:2A:49:30:4B:99:19:C3:1B:9D:6C:03:8C:35:7E:39:EA:D6:A1: 9E:6C:E6:09:D2:3A:2F:5F:68:15:41:8C:2D:4D:D0:15:09:82:F3:97: 3B:FB:02:6E:5C:B8:65:53:DB:94:06:D5:B6:55:C7:A7:B0:4B:FA:78: 44:8B:14:1D:DA:D3:3A:15:17:E8:93:C4:A6:B3:6A:8E:BD:35:B6:1B: 4E:FA:4E:EA:46:41:D0:D8:02:C5:A1:0C:25:E0:CF:55:C2:63:26:BF: DD:19:F5:53:61:19:AD:7B:F7:8E:6D:AC:6C:1C:45:CE:78:B8:47:A9: 41:D8:3D:3E:85:EE:8B:BF:45:F1:36:43:08:4D:4C:1B:DC:02:B0:1E: 59:21:AE:35:5C:DF:A9:9C:D0:CA:DB:25:81:F7:59:1E:D3:2C:BF:0A: 73:96:DE:8B:C3:88:AF:AC:AC:F5:DF:54:57:32:63:29:DC:69:DC:F1: E4:27:C0:CC:CC:8B:5D:F9:6B:98:A4:DC:3A:EA:77:93 parm: dsp_driver:Force the DSP driver for Intel DSP (0=auto, 1=legacy, 2=SST, 3=SOF) (int) Code: Select allpacmd list-sinks No PulseAudio daemon running, or not running as session daemon. Thanks for an help in advance. | Support for the ESSX8336 codec is still under development. viewtopic.php?t=153813 You could see if it works in a live image of Debian Testing. https://cdimage.debian.org/cdimage/week ... so-hybrid/ |
Hello! I'm very new in this forum, so I'm sorry if I posted in wrong section. Yesterday I made dual boot with Debian and Windows 11 on my PC, so I could learn more about using Debian, which is very important for dev, aside being sick of direction Windows is going today. I'll use only Windows for apps that doesn't work on Linux even with Wine and some gaming. I installed Debian and configured everything, and something is fine, expect for Wi-Fi driver that it isn't recognizing, so I have to use my phone to tether USB. I have tried following guides to install RTL8812BU driver and they aren't working. I want to connect to Wi-Fi and I'm lazy to use Ethernet and I don't want to use my phone to be a ethernet for my computer. Do you have any ideas to what to do? My Wi-Fi adapter is generic Multilaser AC1300 USB adapter, I see this is RTL8812BU by looking at box. If you are interested, my PC has Ryzen 5 5600G, Gigabyte B450 AORUS M and 2x8GB (16GB) RAM DDR4 3200MHz, it has 7 months since I built it. Sorry for bad english, I'm Brazilian. Thanks. | Hello, Thanks for reporting the solution: can you report the URL of RTL8812BU GitHub drivers, too ? Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message (after other tags, if any); for example:[Networking][Solved] Installing RTL8812BU driver in Debian 12 |
How to disable non-free-frimware installation while installing Debian in normal installation mode? Why isn't installing Debian asking for permission to install non-free-firmware? (in normal mode) | Hello, dlu2021 wrote: 2023-10-31 16:30 It looks like you can disable by adding firmware=never to the installer boot parameter: https://wiki.debian.org/Firmware#How_to ... e_firmware Yes, for Debian Bookworm installer (as @dlu2021 pointed out in previous post). It was discussed in this previous topic: https://forums.debian.net/viewtopic.php?t=156355 |
Hi, I downloaded printing drivers for my Epson Stylus SX420W from here: https://download.ebz.epson.net/dsc/sear ... archModule Epson Inkjet Printer Driver (ESC/P-R) for Linux 1.8.1 Epson Printer Utility for Linux 1.1.2 Scanner Driver Linux 2.30.4 All-in-one package I managed to install them. The scanner works regularly, but printing gets stopped every time I launch a print job. Could you help me figure it out and fix it please? Thanks | I fixed it by installing epson driver from synaptic directly, then setting it up via CUPS |
Hi, I've been using Debian for a few years and decided to install Debian Testing on my laptop. I would like to install the Nvidia drivers, but I don't know how. I made a few attempts by issuing the following commands: Code: Select allsudo apt install nvidia-driver firmware-misc-nonfree but the glxinfo command doesn't seem to indicate that the nvidia card is being used --> https://dpaste.com/DPZSLDC2S Code: Select all$ glxinfo|egrep "OpenGL vendor|OpenGL renderer" OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) HD Graphics 520 (SKL GT2) I tried giving these commands following a "how to", but in the end it didn't let me install any nvidia drivers because it says it's already installed Code: Select allcat <<EOF | sudo tee /etc/modprobe.d/blacklist-nouveau.conf blacklist nouveau blacklist lbm-nouveau options nouveau modeset=0 alias nouveau off alias lbm-nouveau off EOF echo options nouveau modeset=0 | sudo tee -a /etc/modprobe.d/nouveau-kms.conf sudo update-initramfs -u I have modified the /etc/default/grub file: Code: Select allGRUB_CMDLINE_LINUX_DEFAULT="quiet rd.driver.blacklist=grub.nouveau rcutree.rcu_idle_gp_delay=1" The driver seems to be installed, but the nvidia graphic card seems not in use. I'm not very familiar with configuring graphics cards, can anyone help? My system is this: Code: Select all$ sudo inxi -Fxz System: Kernel: 6.5.0-3-amd64 arch: x86_64 bits: 64 compiler: gcc v: 13.2.0 Desktop: KDE Plasma v: 5.27.8 Distro: Debian GNU/Linux trixie/sid Machine: Type: Laptop System: ASUSTeK product: UX303UB v: 1.0 serial: <filter> Mobo: ASUSTeK model: UX303UB v: 1.0 serial: <filter> UEFI: American Megatrends v: UX303UB.202 date: 08/27/2015 Battery: ID-1: BAT0 charge: 44.3 Wh (85.4%) condition: 51.9/50.0 Wh (103.8%) volts: 11.3 min: 11.3 model: ASUSTeK ASUS Battery status: charging CPU: Info: dual core model: Intel Core i7-6500U bits: 64 type: MT MCP arch: Skylake rev: 3 cache: L1: 128 KiB L2: 512 KiB L3: 4 MiB Speed (MHz): avg: 1005 high: 1086 min/max: 400/3100 cores: 1: 1086 2: 1039 3: 1003 4: 892 bogomips: 20799 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Skylake GT2 [HD Graphics 520] vendor: ASUSTeK driver: i915 v: kernel arch: Gen-9 bus-ID: 00:02.0 Device-2: NVIDIA GM108M [GeForce 940M] vendor: ASUSTeK driver: nvidia v: 525.125.06 arch: Maxwell bus-ID: 01:00.0 Device-3: Realtek USB2.0 HD UVC WebCam driver: uvcvideo type: USB bus-ID: 1-5:2 Display: server: X.Org v: 1.23.2.2 with: Xwayland v: 23.2.2 driver: X: loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa dri: iris gpu: i915 resolution: 1920x1080~60Hz API: EGL v: 1.5 drivers: iris,nvidia,swrast platforms: active: gbm,x11,surfaceless,device inactive: wayland,device-2 API: OpenGL v: 4.6 vendor: intel mesa v: 23.2.1-1 glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 520 (SKL GT2) Audio: Device-1: Intel Sunrise Point-LP HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 API: ALSA v: k6.5.0-3-amd64 status: kernel-api Server-1: PulseAudio v: 16.1 status: active (root, process) Network: Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: <filter> Bluetooth: Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB bus-ID: 1-8:3 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: <filter> Drives: Local Storage: total: 238.47 GiB used: 143.34 GiB (60.1%) ID-1: /dev/sda vendor: SK Hynix model: HFS256G32MND-2200A size: 238.47 GiB Partition: ID-1: / size: 34.02 GiB used: 12.31 GiB (36.2%) fs: ext4 dev: /dev/sda2 ID-2: /boot/efi size: 511 MiB used: 10.5 MiB (2.1%) fs: vfat dev: /dev/sda1 ID-3: /home size: 174.82 GiB used: 131.02 GiB (74.9%) fs: ext4 dev: /dev/sda4 Swap: ID-1: swap-1 type: partition size: 4.46 GiB used: 0 KiB (0.0%) dev: /dev/sda3 Sensors: System Temperatures: cpu: 46.0 C pch: 41.0 C mobo: N/A Fan Speeds (rpm): cpu: 2300 Info: Processes: 224 Uptime: 43m Memory: total: 12 GiB available: 11.58 GiB used: 5.47 GiB (47.3%) igpu: 32 MiB Init: systemd target: graphical (5) Compilers: gcc: 13.2.0 Packages: 2291 Shell: Sudo v: 1.9.14p2 inxi: 3.3.30 Code: Select all$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation GM108M [GeForce 940M] (rev a2) 02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) Thanks in advance | stevepusser wrote: 2023-10-31 06:02 Also, a 940 is getting a bit old now, and may only be supported by one of the Nvidia legacy drivers. Per the wiki, what did nvidia-detect report when you ran it? 940M is supported by the latest Nvidia drivers. I just checked the Nvidia site - https://www.nvidia.com/Download/driverR ... 711/en-us/ I suspect OP will need to use NVIDIA PRIME Render Offload to utilise the Nvidia card, as per the link in @tilla's post above. |
Hi I am stuck in a weird situation. I am using HP X360 laptop and I have installed Debian 12. Linux MX, Manjaro, and Windows. When I type: "a" it types "ad", "d" it types "ad" "q" it types "qe" "e" it types "qe" "z" it types "zc" "c" it types "zc" "1" it types "13" "3" it types "13" I ran Windows troubleshoot, checked that the drivers are updated, uninstalled the keyboard and restarted my laptop but nothing is fixing the issue. The keyboard is behaving the same in all OS's installed on my system i-e Debian 12. Linux MX, Manjaro, and Windows. It was working perfect the last night when I shut down my laptop. Please help resolving the issue Faisal | faisal892 wrote: 2023-11-07 19:06Last night, I posted the above and then slept. When I woke up in the morning today, turned on my laptop and the keyboard is working fine .. lol Guess your keyboard needed a sleep too. Please mark the topic solved by editing the title in your first post and add prefix [Solved]. |
Hello community, I have some experience with Linux but every once in a while I feel more like a newbie... Lenovo Thinkcenter Tiny M73 i5-4590 / 8GB Ram Kernel 6.1.0-12-amd64 Fresh installed with no desktop and installed Docker/Portainer, all good so far but now I need a second NIC so I plugged in this USB to Ethernet Gb adaptor in the hope that I would see it show up and get an IP but that is not happening. I've been searching for a couple of days now, it appears it is trying to use a generic driver and I believe I should be installing some drivers but that is where the newbie in me starts... As a logical approach I went to Realtek here but it they indicate their driver is for up to kernel 5.17 Not sure where to go from here. More info: lsusb: Code: Select allBus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter lshw: Code: Select all*-usb description: Generic USB device product: USB 10/100/1000 LAN vendor: Realtek physical id: 3 bus info: usb@2:3 version: 30.00 serial: 000000 capabilities: usb-2.10 configuration: driver=r8152 maxpower=200mA speed=480Mbit/s Help...! | Hello, Welcome to the forum. Note: moved to “Hardware” sub-forum. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.