prompt stringlengths 1 63.6k | completion stringlengths 1 53.1k |
|---|---|
So I recent got my hands on an old laptop: P2 333mhz 128 RAM 6gig hard drive And I thought hey debian will work on it! My problem is, since it does not have any integrated NIC I'm having an EXTREMELY hard time (mostly since I am new to linux) getting my wireless card to work. The wireless card I purchased is the D-Link DWL-G650 (version B5 Atheros chipset). I found some opensource drivers called madwifi for my chipset. (http://snapshots.madwifi.org/) Heres where my problem is, when I copy the files over, and try to make the driver I get the error: "/lib/modules/2.4.27-2-386/build is missing" This leads me to believe I'm missing my kernels source? If so where can I get it? Thanks | http://security.debian.org/debian-secur ... 1_i386.deb |
Debian has done something cool to the keymapping and I can now get diacriticals like accents and umlauts while typing... But it seems to have broken the double inverted commas. Instead of double-quote, this key (which is Shift-2 on a GB keyboard, rather than shift-apostrophe) gives me a naked umlaut. Which isn´t a double quote, and therefore won´t delimit strings or protect spaces from the shell l or... and is therefore very annoying! How can I get my inverted commas back? Preferably while still being able to type é and ü easily etc from the keyboard... | Is this console, XFree86 or Xorg? If it's Xfree or Xorg what keymap are you using? (dpkg-reconfigure xserver-xorg) andrew |
Hello, I'm having major problems with my system when connected to the interntet. the computer is an old toshiba satellite 2520CDS laptop. I installed debian using a woody installcd, but it upgraded automatically to sarge while installing because it had 'stable' in sources.list. It installed by default a 2.4 kernel. I upgraded to a 2.6 kernel (with devfs, not udev). I both tried installing a precompiled debian kernel and custom compiled vanilla sources but both give the same problem. this is the problem: as soon as the network comes up during boot I get errors like this: Code: Select allpcmcia: registered new device pcmcia0.0 eth0: NE2000 (DL10022 rev 30): io 0x300, irq 3, hw_addr 00:50:BA:7A:6C:31 irq 3: nobody cared (try booting with the "irqpoll" option) [<12345678>] __report_bad_irq+0x31/0x77 [<12345678>] note_interrupt+0x75/0x99 [<12345678>] __do_IRQ+0x19/0x24 ... handlers: [<c027858c>] (ei_irq_wrapper+0x0/0x27) Disabling IRQ #3 (sorry, too much to type...) The 12345678 is an 8-digit hex-code. There are 21 such lines. The last one contains start_kernel. then the same error appears again a few times. when I unplug the networkcable I get the folowing error each minute: Code: Select alleth0: interrupt(s) dropped! the networkcard is a dlink dfe-650 pcmcia card but the same happens with a dlink dwl-g650 (wireless) Does anybody have an idea where to start looking? I already tried the pci=biosirq kernel option. I don't really know how to use the irqpoll option mentionned in the errormessage the reason I want to switch to the 2.6 kernel is because the madwifi drivers for the wifi card only work with a 2.6 kernel. The wired networkcard works fine with 2.4. help... Johan | IRQ 3 is the second serial port normally. Does the laptop use a second serial port? Or IrDA on serial port 2? I'd look it up but I'm feeling lazy Possibly the IRQ is not right for that PCMCIA port. "Nobody cared", to me, would imply that the device didnt respond. It's completely possible I'm way off here though.... |
I'm having some problems with my 32-bit chroot on an amd64 sid system: it was working fine until recently when it broke for no obvious reason. The only thing I can think of is a package update may have done it. The chroot system is set up as per the instructions on alioth.debian.org Now, it can't find some files to start. It can find others, but they can't find parts necessary to start them. It also has trouble passing command-line options using the standard do_dchroot script. Here are some examples: Code: Select all$ dchroot -c ia32 -d echo (ia32) echo /bin/echo: /bin/echo: cannot execute binary file dchroot: Child exited non-zero. dchroot: Operation failed. Code: Select all$ dchroot -c ia32 -d oocalc (ia32) oocalc /usr/bin/oocalc: line 7: my: command not found /usr/bin/oocalc: line 9: my: command not found /usr/bin/oocalc: line 11: my: command not found /usr/bin/oocalc: oocalc: line 13: syntax error near unexpected token `{' /usr/bin/oocalc: oocalc: line 13: `if ($SystemInstallDir =~ /^@/) {' dchroot: Child exited non-zero. dchroot: Operation failed. Code: Select all$ dchroot -c ia32 -d "opera -newpage http://www.google.com" (ia32) opera -newpage http://www.google.com bash: opera -newpage http://www.google.com: No such file or directory dchroot: Child exited non-zero. dchroot: Operation failed. Code: Select all$ dchroot -c ia32 -d Executing shell in 'ia32' chroot. $ echo $ opera -newpage http://www.google.com opera: Activated running instance $ oocalc $ (Openoffice started fine in that last example) So it works without a problem if I use dchroot to create a shell in the 32-bit chroot and launch things from there, but it fails if I try to launch things directly or pass any arguments to them using dchroot. Any ideas, anyone? Thanks! | Well, thanks to a post on forums.gentoo.org [1] (much more active than these, sadly..), this is solved. It turns out that the su command had been updated and no longer included some stuff used by dchroot. As a result of this, dchroot cannot now execute arbitrary binaries in the chroot and just passes all of its unused command line arguments to bash in the chroot. We can take advantage of this by using the "-c" switch of bash to run any command. See below for the updated do_dchroot script. Code: Select all#!/bin/sh ARGS="" for i in "$@" ; do ARGS="$ARGS '$i'" done # Have had to add a bit of a hack here, so that it can cope # when not using GNU version of su. Put simply, dchroot # passes its "command" options as arguments to bash, so # requires a script. Using bash's "-c" option allows # arbitrary binary commands to be executed. "--" is # necessary because otherwise dchroot would think the # "-c" option was meant for it. exec dchroot -c ia32 -d -q -- -c ""`basename $0`" $ARGS" [1] http://tinyurl.com/ns9a6 |
Hello, I have a fresh Debian Sarge setup, and I followed EXACTLY the how-to on workaround.org to setup a Postfix server with MySQL user database. I've checked it twice, everything is exactly as described in this how-to, I also did all the test in between and they've all been successful. Now, like in step 9 I've created the following entries in the MySQL database like this: INSERT INTO domains (domain) VALUES ('virtual.test'); INSERT INTO users (email,password) VALUES ('user@virtual.test','secret'); INSERT INTO forwardings (source,destination) VALUES ('admin@virtual.test','user@virtual.test'); This also worked fine, at least I didn't get any errors. Now when I'm try to send an test-email with telnet localhost 25, I get 220 myserver ESMTP Postfix (Debian/GNU) which is good, I enter 'ehlo workaround.org', I get all the answers from the Postfix server as I should,but when I enter mail from:<test@workaround.org> but then I don't get an OK and telnet just hangs. In mail.log I have this: Apr 27 15:18:50 myserver postfix/trivial-rewrite[16550]: warning: connect to mysql server 127.0.0.1: Host 'localhost.localdomain' is not allowed to connect to this MySQL server Apr 27 15:18:50 myserver postfix/trivial-rewrite[16550]: fatal: mysql:/etc/postfix/mysql-virtual_forwardings.cf(0,100): table lookup problem So it seems it can't connect to the database. My /etc/postfix/mysql-virtual_forwardings.cf looks like this (as from workaround.org: Code: Select alluser = provider_admin password = secret dbname = provider table = forwardings select_field = destination where_field = source hosts = 127.0.0.1 In my my.cf I have the line bind-address = 127.0.0.1 and Postfix main.cf looks like this: Code: Select allmyhostname = myserver.de mydestination = myserver.de mynetworks = 127.0.0.1 virtual_alias_maps = mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_mailbox_base = /data/vmail virtual_uid_maps = static:7000 virtual_gid_maps = static:7000 smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_use_tls = yes smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key As I said, all previous steps worked flawlessly and I was always able to connect and I always got exactly the output that I should get according to workaround.org. Any suggestions on what could be wrong with my setup? [SOLVED] I've granted permissions to the mysql user again and now it works! Tom | elektrohirn wrote:Hello, I have a fresh Debian Sarge setup, and I followed EXACTLY the how-to on workaround.org to setup a Postfix server with MySQL user database. I've checked it twice, everything is exactly as described in this how-to, I also did all the test in between and they've all been successful. Now, like in step 9 I've created the following entries in the MySQL database like this: INSERT INTO domains (domain) VALUES ('virtual.test'); INSERT INTO users (email,password) VALUES ('user@virtual.test','secret'); INSERT INTO forwardings (source,destination) VALUES ('admin@virtual.test','user@virtual.test'); This also worked fine, at least I didn't get any errors. Now when I'm try to send an test-email with telnet localhost 25, I get 220 myserver ESMTP Postfix (Debian/GNU) which is good, I enter 'ehlo workaround.org', I get all the answers from the Postfix server as I should,but when I enter mail from:<test@workaround.org> but then I don't get an OK and telnet just hangs. In mail.log I have this: Apr 27 15:18:50 myserver postfix/trivial-rewrite[16550]: warning: connect to mysql server 127.0.0.1: Host 'localhost.localdomain' is not allowed to connect to this MySQL server Apr 27 15:18:50 myserver postfix/trivial-rewrite[16550]: fatal: mysql:/etc/postfix/mysql-virtual_forwardings.cf(0,100): table lookup problem So it seems it can't connect to the database. My /etc/postfix/mysql-virtual_forwardings.cf looks like this (as from workaround.org: Code: Select alluser = provider_admin password = secret dbname = provider table = forwardings select_field = destination where_field = source hosts = 127.0.0.1 In my my.cf I have the line bind-address = 127.0.0.1 and Postfix main.cf looks like this: Code: Select allmyhostname = myserver.de mydestination = myserver.de mynetworks = 127.0.0.1 virtual_alias_maps = mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual_domains.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual_mailboxes.cf virtual_mailbox_base = /data/vmail virtual_uid_maps = static:7000 virtual_gid_maps = static:7000 smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_use_tls = yes smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key ions to the mysql user again and now it works! Tom |
is it ok to go from stable straight to unstable, last time i went stable --> testing --> unstable. I could do without the extra downloading... | There is no need to go via Testing. Just set your sources.list pointing at unstable and go ahead. Keeping in mind that Unstable is pr definition 'un-safe' of course Tina |
Hi, I'm trying to install kde on my machine but apt-get is failing as follows: Code: Select allapt-get install kde Reading Package Lists... Done Building Dependency Tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: kde: Depends: kdenetwork but it is not going to be installed E: Broken packages Can anyone tell me how I can get around this? I'm using Debian Unstable (Sid). | It looks like kde has broken dependencies. kde is a big metapackage with lots and lots of dependencies but there's also another metapackage for kde, kde-core, that installs fewer packages. So you could try "apt-get install kde-core" and see if that succeeds any better. |
Hi, i'm running a debian Etch system wich work very fine but still got a problem to automount a partition on a sata drive. i can manually mount it but it's so boring :/ my fstab contains the following line /dev/sda1 /mnt/120 vfat rw,user,exec,auto 0 0 but it appears not to be enough to automount it at startup, so i tried with making a script in /etc/init.d/ Code: Select all#!/bin/sh mount /dev/sda1 then i've made a symbolic link from this script to /etc/rc2.d/ cd /etc/rc2.d/ ln -s /etc/init.d/mount_sata_drive.sh but it still don't work... i've heard about the rc-update so i tried to run rc-update.d /etc/init.d/mount_sata_drive default 99 but it seems not to be installed on my system and when i tried to install it from synaptic nothing's found. so, any idea ? | Hi amo, Strange that it doesn't mount automatically. If you boot and the partition isn't mounted, then as root you type Code: Select allmount -a -v does that mount the drive? If so, then look at the script for mounting all filesystems (it's /etc/init.d/mountall.sh in Sarge, not sure about Etch). It should contain a line saying something like Code: Select allmount -av -t nonfs,nonfs4,nosmbfs,nocifs,noncp,noncpfs,nocoda -- it doesn't by any chance have something like novfat or nofat or something, does it? Another possibility would be that for some reason the device node is not yet present when it's mounting. Then you should get error messages, I guess. In this case it'd be useful to give us these. Assuming we can't fix it, let's move on to your script. Is the file executable? (Test by ls -l /etc/init.d/mount_sata_drive.sh, or by trying to run it (as root) by typing its full path at the shell prompt.) Then, the filename should start with S and a number if you want it to be started when entering the runlevel. For example, S99mount_sata_drive.sh. So if you enter /etc/rc2.d, then Code: Select allls *mount_sata_drive.sh and remove the files you find, after that Code: Select allln -s ../init.d/mount_sata_drive.sh S99mount_sata_drive.sh (yes, that is the syntax -- first where it should point to, then the name.) This should do it. One more question for you: is the drive unmounted correctly when shutting down? HTH, |
I came to Debian by way of Ubuntu which had a handy little program to handle all my network interfaces, including my wireless card. I could just enter the ESSID of the wireless network I was trying to connect to (and IP info if necessary), and away it went. My Debian system doesn't seem to have this app anywhere I can find it and I can't install if if I don't know it's name. Does anyone know what I'm talking about, and is there a better app available in full-on Debian? | Deejmeister> Does anyone know what I'm talking about? Apparently not, but that usually doesn't stop us; just slows us down a bit. ;-) Run lspci -v to see how your wireless card identifies itself, and we'll go from there. |
Hi, I've just done a fresh install of Sarge and put the unstable repository in my /etc/apt/sources.list, then did an apt-get update and used text interface aptitude to upgrade and install packages I wanted. I've tried installing a few packages like a window manager, gkrellm and a few other basics, but I've got a horrible problem: I can't startx, I can't apt-get install xserver-xorg or xserver-xfree86 because there are broken dependencies. Apt-get tells me to run apt-get -f install which I do, it says that x11-common will be installed as an extra package and x11-common will be installed as a new package. I believe that aptitude text interface failed previouly with x11-common regarding dependencies apt-get does the same. The error I get is: Code: Select allWARNING: The following packages cannot be authenticated! x11-common so I say yes to install this without verification and then I get an error saying Code: Select allE:Sub-process /usr/bin/dpkg returned an error code (1) I can't get past this and I can't install anything. I'm stuck. Help? | You may want to re-install sarge with 2.6.8 kernel and work with that for awhile. You can get xorg from sarge backports and work with that for awhile. Then if you want to try etch or testing change your sources to point to testing and apt-get update. then use synaptic to install xorg packages and make sure this version of xorg works for you too. If your desktop is ok follow with linux-image-2.6.12x(for your cpu version) install from synaptic's base sytem section. If reboot is successful with new kernel and desktop ok then you can log out of desktop and do CTL+ALT+F1, login as root and do aptitude --with recommends dist-upgrade. aptitude -s --with recommends dist-upgrade will give you a practice run. This will get you debian etch install that is more likely to work. Plus etch has security updates too. Add unstable packages carefully and enjoy. Then again you can start with debian etch netinstall or use etch CD1 install disk to get much of basic desktop from the cd. |
Hi, How do I get rid of old kernel versions? I've currently got 2.6.8, 2.6.12 and 2.6.15 (or something like that) and I want to get rid of all but the latest one. My boot partition is only 32MB, and I don't want to run out of room in it if a new kernel version comes out. But I'm not sure which packages to purge. Advice? Thanks, Asfand Yar | Perhaps this will be helpful. It is from Debian Resource (a must read) http://www.debian.org/doc/manuals/refer ... eoldkernel Aaron |
Hi, I'm trying to get my wifi working in Linux and I can't load the ndiswrapper module. I'm using a custom compiled 2.6.14 vanilla kernel. I get the following error: Code: Select allFATAL: Error inserting ndiswrapper (/lib/modules/2.6.14/misc/ndiswrapper.ko): Unknown symbol in module, or unknown parameter (see dmesg) In dmesg I see: Code: Select allndiswrapper: Unknown symbol wireless_send_event Can anyone give any advice on how to fix this? | never mind, i had to recompile my kernel to give me the neccessary base support in order for it to have the symbol |
Hi, I've got no terminals on the vtys 2-6. Vty 1 is normal but the others are all blank with no login prompt. Ideas? | by default debian only attatches a login prompt to tty2-6 if you're using runlevels 2 or 3. If you are using runlevels 4 or 5 then you only get tty1. Are you using runlevel 4 or 5? If so have a look in /etc/inittab Code: Select all# /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> # # Note that on most Debian systems tty7 is used by the X Window System, # so if you want to add more getty's go ahead but skip tty7 if you run X. # 1:2345:respawn:/sbin/getty 38400 tty1 2:23:respawn:/sbin/getty 38400 tty2 3:23:respawn:/sbin/getty 38400 tty3 4:23:respawn:/sbin/getty 38400 tty4 5:23:respawn:/sbin/getty 38400 tty5 6:23:respawn:/sbin/getty 38400 tty6 I don't know for sure, but editing the second field of the lines for tty2-6 to 2345 should start these login prompts in run levels 4 and 5 as well. Hope this helps! |
Hi all, I'm trying to add a group with a space in the name to the sudoers file unsuccessfully (I'm pretty sure I'm not supposed to do this). What I want to know is if there is a way that I can do this anyway and make it work normally. The reason is that I'm trying to add the "domain admins" group from the NT domain authentication to have all sudo rights on this machine. I've tried using single and double quotes, all of the following lines in turn: Code: Select all%domain admins ALL=(ALL) ALL %"domain admins" ALL=(ALL) ALL "%domain admins" ALL=(ALL) ALL %'domain admins' ALL=(ALL) ALL '%domain admins' ALL=(ALL) ALL None of these seem to be valid syntax. Can anybody recommend how I should do this? | This would be a good question for the sudo-users mailing list. http://www.sudo.ws/mailman/listinfo/sudo-users |
Hi, I'm curious as to how Debian handles full sytem configuration updates when you do: Code: Select allapt-get update apt-get upgrade When the products are upgraded does it also upgrade configuration files with more recent versions? On Gentoo when you do an upgrade like this it is really annoying because you have to run etc-update and choose whether to keep the old configuration files with your settings or have them replaced with the new configuration file templates. What does Debian do? | Configuration files that are not changed will be updated. Configuration files that are changed by the admin and by the system administrator, will elicit a question by dpkg of what you want to do, defaulting to keeping your old config. Mostly, keeping your customised config is not a problem, only rarely changes to the default configuration will be important (enough), and the principle of least surprise is keeping the setting that you had when you actually looked manually at the configuration. You can find .dpkg-new and .dpkg-old files in /etc where dpkg leaves you new or replaced configuration files from during the installation, you can manually inspect them then. So the short summary is: you mostly shouldn't need to bother, and just have dpkg not overwrite your configuration. Or have dpkg update your configuration if you're sure that whatever you've changed there, can't be very interesting and you don't want to preserve it. |
I selected UK 104 key keyboard during installation. It works fine (I can even get pound/sterling signs!) but I get about five of these error dialogs when starting Gnone... Error activating XKB configuration Probably internal X Server problem blah,blah... I've tried Desktop->Keyboard and deleted current map and re-selected UK but with no success. I haven't set up any special keyboard handling stuff (no idea how to do that anyway!) I just want a bog-standard uk kb without error messages TIA | Set GB instead of UK. It cured the same problem for me! Why that selection isn't on a menu beats me. |
I just installed debian sarge, i am trying to get webmin going but I get a access denied from my network computers, i thought it was a firewall issue but have removed shorewall and I am still getting the access denied 403 error. i can go to webmin from the debian box using localhost so I know its working. also I did get the ssl certificate but after accepting it i got the access denied from 192.168.0.143 message (firefox) or you are not authorized to view this page (IE) I have looked for a .htaccess file but so far i am not finding one. also both the hosts.allow and hosts.deny files are empty. any ideas ???? thanks | No Starch : The Book of Webmin |
Mepis 3.3.1.1 (Debian Sarge) My printer does not show up in the Samba "Share Browser" automatically. Each time I boot Mepis, I must open "Control Center>Internet and Network>Samba Configuration" then login as root and go through the config to the point of opening and ok'ing printer edit. It always shows my printer and "All printers shared" After saying ok to that without changing anything, that window closes and "Apply" now appears instead of being grayed out. click Apply and go back to "Share Browser" and now my printer is under Mepisgrp>Mepis. But I have to go through that every time I start Mepis. There must be a way to save that setting so it stays active through a reboot. Any help? | If you are using CUPS, then you could always use IPP. What does your smb.conf file look like? |
Does aptitude check for previous packages or it just installs it......I mean I dont want to install some stuff a few times....thats all....??? Thank You | sandokan wrote:Does aptitude check for previous packages or it just installs it......I mean I dont want to install some stuff a few times....thats all....??? Thank You Aptitude is merely another program interfacing Debian's package management system, much like apt or dselect are. Of course it will notice that a certain package has already been installed and refuse to install it again. |
I'm trying to keep a package from being updated by apt-get. I'm using an avr-libc package that needs to remain unaltered. I've tried holding it in aptitude by searching for it and pressing =. A h appears, but an apt-get upgrade still tries to change the package. I've also tried "aptitude hold avr-libc", which seems to hold back the package, but as soon as I try and upgrade it tries to write over it again. What do I do in this situation? I've searched for this and as far as I can tell the package should be held. It just isn't. I'd like to automate updates, but this one package is keeping me from doing it. Thanks for any help. | Try this: Code: Select allecho "avr-libc hold"|dpkg --set-selections |
Hi I recently reinstalled debian testing (kernel-image-2.6.8-1-k7) on my box with the sarge installer RC2. Everything seemed fine excet cds wouldn't automount as a user, only as root. I had to add my user to the plugdev group to get automounting working. Code: Select alladduser youruser plugdev then log out and back in. note that I did a minimal install and then apt-got what I needed. Yanik | I'd like to know how you got automount working and also how you got the plugdev group, I've done a desktop install and there is not plugdev group on my machine. |
I've downloaded the kernel 2.6.7 from www.backports.org and it works almost. I've a problem with my mouse, but I don't know what to do. It's impossible to launch XFree There's the end of my log: (II) Keyboard "Generic Keyboard" handled by legacy driver (**) Option "Protocol" "PS/2" (**) Configured Mouse: Protocol: "PS/2" (**) Option "CorePointer" (**) Configured Mouse: Core Pointer (**) Option "Device" "/dev/psaux" (**) Option "Emulate3Buttons" "true" (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5" (**) Configured Mouse: ZAxisMapping: buttons 4 and 5 (**) Configured Mouse: Buttons: 5 (**) Option "Protocol" "ImPS/2" (**) Generic Mouse: Protocol: "ImPS/2" (**) Option "SendCoreEvents" "true" (**) Generic Mouse: always reports core events (**) Option "Device" "/dev/input/mice" (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such device. (EE) Generic Mouse: cannot open input device (EE) PreInit failed for input device "Generic Mouse" (II) UnloadModule: "mouse" (II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE) (II) Configured Mouse: ps2EnableDataReporting: succeeded Warning: font renderer for ".pcf" already registered at priority 0 Warning: font renderer for ".pcf.Z" already registered at priority 0 Warning: font renderer for ".pcf.gz" already registered at priority 0 Warning: font renderer for ".snf" already registered at priority 0 Warning: font renderer for ".snf.Z" already registered at priority 0 Warning: font renderer for ".snf.gz" already registered at priority 0 Warning: font renderer for ".bdf" already registered at priority 0 Warning: font renderer for ".bdf.Z" already registered at priority 0 Warning: font renderer for ".bdf.gz" already registered at priority 0 Warning: font renderer for ".pmf" already registered at priority 0 Thanks a lot | It's solved, only load psmouse and mousedev |
If I have to use the terminal, giving me the instructions will be appreciated | Code: Select all$ cat /sys/class/hwmon/hwmon*/name i350bb radeon coretemp coretemp nct7904 $ ls /sys/class/hwmon/ hwmon0 hwmon1 hwmon2 hwmon3 hwmon4 $ ls /sys/class/hwmon/hwmon4/ device fan5_input in11_input in16_input in4_input in9_input pwm2 pwm4_enable uevent fan1_input fan6_input in12_input in1_input in5_input name pwm2_enable subsystem fan2_input fan7_input in13_input in20_input in6_input power pwm3 temp1_input fan3_input fan8_input in14_input in2_input in7_input pwm1 pwm3_enable temp2_input fan4_input in10_input in15_input in3_input in8_input pwm1_enable pwm4 temp3_input $ cat /sys/class/hwmon/hwmon4/temp3_input 49500 $ cat /sys/class/hwmon/hwmon4/temp3_input | awk '{print $1/1000}' 49.25 $ notify-send "socket 1 temp $(cat /sys/class/hwmon/hwmon4/temp3_input | awk '{print $1/1000}')°" Figuring out what's what can be a challenge, but possible if you follow what I did there....Generally speaking CoreTemp is redundant bunk and not really actionable. You should figure out if there is a motherboard mounted sensor in/under the physical socket. There usually is, and this is the actual hot spot and the limiting factor. |
I have this laptop. I was playing a game on steam using bookworm and my computer just crashed (black screen, audio was a loud buzz EEEEEEEEEEEEE...) I restarted and the display stopped working. I took it to an hp repair guy and it costs more than 1k to get a new display panel, so I didn't opt for that. When I plug in an external display the screen remains blank as well. I unplugged the ribbon cable/laptop display from the motherboard and the external display didn't work, so it is now reattached. I cannot get the display to work at POST/BIOS/boot. The external display does not work either at these periods. I ran inxi and got the following output with an external display plugged into HDMI: Code: Select allSystem: Kernel: 6.1.0-33-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-33-amd64 root=UUID=4f9f6da4-911b-4d93-af63-b3a46bd2c890 ro quiet Console: pty pts/0 DM: LightDM v: 1.26.0 Distro: Debian GNU/Linux 12 (bookworm) Graphics: Device-1: Intel CometLake-H GT2 [UHD Graphics] vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1 empty: DP-3, DP-4, HDMI-A-2, HDMI-A-3, HDMI-A-4 bus-ID: 00:02.0 chip-ID: 8086:9bc4 class-ID: 0300 Device-2: NVIDIA TU117M [GeForce GTX 1650 Ti Mobile] vendor: Hewlett-Packard driver: nouveau v: kernel non-free: 530.xx+ status: current (as of 2023-03) arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-22 pcie: gen: 3 speed: 8 GT/s lanes: 8 link-max: lanes: 16 ports: active: none off: HDMI-A-1 empty: DP-1,DP-2 bus-ID: 01:00.0 chip-ID: 10de:1f95 class-ID: 0300 temp: 25.0 C Device-3: Chicony HP Wide Vision HD Camera type: USB driver: uvcvideo bus-ID: 1-6:3 chip-ID: 04f2:b6b6 class-ID: 0e02 serial: <filter> Display: server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris,nouveau gpu: i915,nouveau tty: 120x30 Monitor-1: HDMI-A-1 model: HP E243 serial: <filter> built: 2019 res: 1920x1080 dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8") ratio: 16:9 modes: max: 1920x1080 min: 720x400 Monitor-2: eDP-1 model: Samsung 0x4145 built: 2019 res: 3840x2160 dpi: 284 gamma: 1.2 size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 3840x2160 API: OpenGL Message: GL data unavailable in console. Try -G --display I ran lspci and got the following output: Code: Select all00:00.0 Host bridge: Intel Corporation 10th Gen Core Processor Host Bridge/DRAM Registers (rev 02) 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 02) 00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05) 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi 00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0 00:15.1 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller #1 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller 00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] 00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Device 06b7 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Comet Lake LPC Controller 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller 00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller 01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev a1) 01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1) 02:00.0 Non-Volatile memory controller: Toshiba Corporation XG6 NVMe SSD Controller 03:00.0 SD Host controller: Genesys Logic, Inc GL9750 SD Host Controller (rev 01) I don't see the devices in lspci, so I'm not sure what that means, but inxi shows them. I have the i915 and nouveau graphic drivers loaded. The laptop boots and connects to wifi. I can log in using a screen reader and run terminal. I have locked secure boot and cannot navigate the BIOS with the blank screen to shut it off, I was going to try the nvidia-proprietary driver in-case some magic happened and the displays worked with it. Is this a motherboard problem? (edit: turns out display is dead. To get external monitor working, I needed to press increase brightness on laptop keyboard. Laptop works with external display, but cannot access bios with external display.) (edit2: I upgraded the firmware with fwupdmgr and assumed secureboot is disabled cause it worked, and installed nvidia-driver. But secure boot was still enabled, and I had to purge it and reinstall nouveau. I found out that nouveau also requires firmware-misc-nonfree, which is not listed on the wiki. On the Gentoo wiki it says newer nvidia cards still need firmware to boot properly. So tl;dr unplugged laptop display ribbon cable, installed nouveau, installed nvidia-firmware -- trixie gnome is working now; bios does not display on external monitor.) | It well could be motherboard, but it may be not quite time to write it off totally. That inxi reports display details suggests it is a hardware problem. Conceivably the NVidia is removable and if removed graphics from the CometLake iGPU could work. Does attaching one or more bootable USB sticks before powering up change anything? What about booting without the HDD or SDD attached? You could try a BIOS reset by removing both batteries for a short while. First if it was me I'd detach the ribbon cable from the display panel again and just try using HDMI-connected display, to see if the reset BIOS permits recognition of the only video connection. You might also try the BBS Menu hotkey, probably F10, possibly F9 and/or ESC. |
Hi! I've been using Debian for a few months now and its worked great. However I have recently been having a problem with my internet connection. Im afraid that trouble shooting this may be a bit over my head as I am somewhat new to Linux. My problem is that every once in a while my ethernet connection randomly drops then reconnects. At this point it is happening once a day and only started happening I would say about a month ago, but I cant be for sure. I installed proprietary drivers for my realtek device, but that did not fix this issue. IP: Code: Select allenp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.0.0.196 netmask 255.255.255.0 broadcast 10.0.0.255 inet6 fe80::9e6b:ff:fe14:34b7 prefixlen 64 scopeid 0x20<link> inet6 2601:1c2:780:9180:9e6b:ff:fe14:34b7 prefixlen 64 scopeid 0x0<global> inet6 2601:1c2:780:9180::d9b5 prefixlen 64 scopeid 0x0<global> ether 9c:6b:00:14:34:b7 txqueuelen 1000 (Ethernet) RX packets 2216423 bytes 1517737227 (1.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1422243 bytes 402535571 (383.8 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 base 0xd000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 49431365 bytes 2810654675 (2.6 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 49431365 bytes 2810654675 (2.6 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lspci: Code: Select all00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset USB 3.1 xHCI Compliant Host Controller (rev 01) 02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset SATA Controller (rev 01) 02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Bridge (rev 01) 03:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) 03:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) 03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 400 Series Chipset PCIe Port (rev 01) 05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 07:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c7) 08:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c7) 09:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller 0a:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function 0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 0b:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 0b:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller Thank you in advance for any help you can provide! | Hello, The dmesg output only collects messages from the kernel, but not from system services. Can you report a detail of your ethernet network adapter ? You can use the command: Code: Select alllspci -vnn -d ::0200 Can you report the overall configuration of your ethernet network adapter ? You can use the command (note: ethtool package must be installed): Code: Select all$ su -l -c "ethtool enp5s0" You can inspect the systemd journal to verify if there are recorded some events potentially related to the link up/down; i.e. you can use the following command (logs for last three days): Code: Select allscript log.txt su -l -c "journalctl --since \"3 days ago\" --no-pager | grep -C 10 r8168.*link" exit The output from the systemd journal will be stored in the file named "log.txt" You can report logs in one of 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) Hope this helps. |
[size=85]I've used wired connections on this computer for a long time. I find that I need to use a wireless connection and I'm encountering issues. This is from the lspci -v command 05:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: ASUSTeK Computer Inc. QCA6174 802.11ac Wireless Network Adapter Flags: bus master, fast devsel, latency 0, IRQ 85, IOMMU group 12 Memory at f7200000 (64-bit, non-prefetchable) [size=2M] Capabilities: <access denied> Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci It seams the driver is loaded but I can't get it to connect to my wireless network. I have B/G 2.4GHz and A 5GHz listed in NetworkManager I have tried both. I'm using MATE as my window manager, I read something about NetworkManager only working with Gnome. What am I missing? Sam[/size] | Hello, SamuelMac wrote: 2025-03-17 01:22 I'm sorry I did not have the "firmware-atheros" installed I installed it and the wireless is working. 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). Then make the subject of the first post useful to find for other forum's readers with the same issue, i.e.: "[Solved] Wireless on Debian 11 with Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter." Thanks. Happy Debian ! -- EDIT Sat Mar 22 09:33:28 CET 2025: 1) discussion moved to "Hardware" sub-forum 2) added "with Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter" to the subject's topic and marked it as "[Solved]" |
I installed Debian 12 on an old PC with an Nvidia GT 610 graphics card using the open-source Nouveau driver. The system seems to be working fine—I can stream videos in browsers and play videos on VLC. However, upon booting, I see the following errors. Is this a cause for concern, or am I missing something? Please help me. dmesg | grep -i error [ 0.556750] RAS: Correctable Errors collector initialized. [ 7.335870] nouveau 0000:04:00.0: Direct firmware load for nouveau/nvd9_fuc084 failed with error -2 [ 7.335897] nouveau 0000:04:00.0: Direct firmware load for nouveau/nvd9_fuc084d failed with error -2 [ 17.964119] nouveau 0000:04:00.0: Direct firmware load for nouveau/nvd9_fuc084 failed with error -2 [ 17.964141] nouveau 0000:04:00.0: Direct firmware load for nouveau/nvd9_fuc084d failed with error -2 | Hello, See here: Debian Bug report logs - #990662 nouveau 0000:01:00.0: firmware: failed to load nouveau/nvd9_fuc084 (-2): Message #22 received at 990662@bugs.debian.org (full text, mbox, reply): From: Mathieu Malaterre <malat@debian.org> To: 990662@bugs.debian.org Subject: Steps Date: Mon, 11 Jul 2022 18:30:47 +0200 Local steps for me were: Code: Select all% wget https://raw.githubusercontent.com/envytools/firmware/master/extract_firmware.py % wget https://download.nvidia.com/XFree86/Linux-x86_64/340.108/NVIDIA-Linux-x86_64-340.108.run % sh NVIDIA-Linux-x86_64-340.108.run --extract-only % python3 extract_firmware.py % sudo mkdir /lib/firmware/nouveau % sudo cp nvd9_fuc084 /lib/firmware/nouveau Note that some firmware binaries (after extraction) are referenced as symbolic link to other firmware files. |
I have installed Debian 12 with Xfce on a system with two 8 GB RAM modules. On Ubuntu they are instantly recognized but Debian 12 Xfce does only find 4 GB. I would somehow understand how this issue occurs if it didn't understand one of the RAM modules but only half of one seems very obscure to me: Code: Select all$ free -h total used free Memory: 3,2Gi 1,1Gi 1,5Gi (7,9Mi / 760Mi / 2,1Gi) Swap: 974Mi 0B 974Mi | Hello, please post output of: Code: Select allsudo dmidecode -t memory AND Code: Select alllsmem |
Solution -> answer to my question : am i using nvidia drivers ? answer : yes, nvidia driver is used when needed for example for a video game Hello, I'm writing this post because I'm not sure that I'am really using NVIDIA driver. my setup is Debian 12.10 stable with KDEPlasma on an Acer laptop with a NVIDIA GTX 1060. I have installed the driver how is sugget in official debian guide, I have installed the driver 535.216.01. official debian documentation installation driver that i used : https://wiki.debian.org/NvidiaGraphicsDrivers if i check with glxinfo it saids that i'm using MESA drivers for rendering Code: Select all # glxinfo | grep render direct rendering: Yes GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, Extended renderer info (GLX_MESA_query_renderer): OpenGL renderer string: Mesa Intel(R) HD Graphics 630 (KBL GT2) GL_ARB_compute_variable_group_size, GL_ARB_conditional_render_inverted, GL_IBM_multimode_draw_arrays, GL_INTEL_blackhole_render, GL_NV_conditional_render, GL_NV_copy_image, GL_NV_depth_clamp, GL_ARB_compute_variable_group_size, GL_ARB_conditional_render_inverted, GL_INGR_blend_func_separate, GL_INTEL_blackhole_render, GL_NV_compute_shader_derivatives, GL_NV_conditional_render, GL_EXT_read_format_bgra, GL_EXT_render_snorm, GL_EXT_robustness, GL_EXT_unpack_subimage, GL_INTEL_blackhole_render, GL_NV_compute_shader_derivatives, GL_NV_conditional_render, GL_OES_element_index_uint, GL_OES_fbo_render_mipmap, also checking OS system information it said that the system is using graphics processor : Mesa Intel® HD Graphics 630 However when i launch CounterStrike 2 with steam this process will appear in output of nvidia-smi then my question is I'm using nvidia or mesa drivers? The performance in game is not good, the fps are between 30 and 60 with a lot of picks, probably because CS2 is a recent game and driver 535 isn't optimized for this one (or my laptop just sucks, others games run well), i don't really want to play to this game i was just curious to test the performance of some game and these questions come up on my mind. Code: Select allnvidia-smi Mon Mar 31 19:58:18 2025 +---------------------------------------------------------------------------------------+ | NVIDIA-SMI 535.216.01 Driver Version: 535.216.01 CUDA Version: 12.2 | |-----------------------------------------+----------------------+----------------------+ | GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=========================================+======================+======================| | 0 NVIDIA GeForce GTX 1060 On | 00000000:01:00.0 Off | N/A | | N/A 54C P2 28W / 78W | 2928MiB / 6144MiB | 16% Default | | | | N/A | +-----------------------------------------+----------------------+----------------------+ +---------------------------------------------------------------------------------------+ | Processes: | | GPU GI CI PID Type Process name GPU Memory | | ID ID Usage | |=======================================================================================| | 0 N/A N/A 755 G /usr/lib/xorg/Xorg 4MiB | | 0 N/A N/A 4704 C+G ...ebian-installation/logs/cef_log.txt 5MiB | | 0 N/A N/A 5109 C+G ...fensive/game/bin/linuxsteamrt64/cs2 2913MiB | +---------------------------------------------------------------------------------------+ Ps. nvidia-smi said also that he is used by /usr/lib/xorg/Xorg but i'am using wayland, why? | Does your laptop have switchable GPU's? Please post output of: Code: Select allinxi -Fzxx Your glxinfo should look like this: Code: Select alldirect rendering: Yes OpenGL renderer string: NVIDIA GeForce GTX 1650/PCIe/SSE2 GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth, GL_NVX_conditional_render, GL_NVX_gpu_memory_info, GL_NVX_nvenc_interop, GL_NV_compute_shader_derivatives, GL_NV_conditional_render, GL_NV_path_rendering, GL_NV_path_rendering_shared_edge, GL_NV_stereo_view_rendering, GL_NV_texgen_reflection, GL_ARB_compute_variable_group_size, GL_ARB_conditional_render_inverted, GL_NVX_conditional_render, GL_NVX_gpu_memory_info, GL_NVX_nvenc_interop, GL_NV_compute_shader_derivatives, GL_NV_conditional_render, GL_NV_path_rendering, GL_NV_path_rendering_shared_edge, GL_NV_stereo_view_rendering, GL_NV_texgen_reflection, GL_EXT_multisample_compatibility, GL_EXT_multisampled_render_to_texture, GL_EXT_multisampled_render_to_texture2, GL_EXT_raster_multisample, GL_EXT_read_format_bgra, GL_EXT_render_snorm, GL_NV_conditional_render, GL_NV_conservative_raster, GL_NV_path_rendering, GL_NV_path_rendering_shared_edge, GL_NV_shadow_samplers_cube, GL_NV_stereo_view_rendering, GL_OES_fbo_render_mipmap, GL_OES_geometry_point_size, GL_OVR_multiview_multisampled_render_to_texture |
I have an i9 13900k w/ 128gb of DDR4 and 2x980 Pro NVME in software RAID w/ ext4. When I initially build this system in April 2023, I deployed Ubuntu Desktop and subsequently moved to Debian 12 around Oct. This is not intended as a brag, but may be relevant to the crashes described below - I would not recommend such a configuration for most users. On both deployments, I've experienced disk lockups when performing a substantial amount of writes to the filesystem, I'm yet to be able to reproduce 100% reliably, but I most frequently saw this when attempting to perform a multi-threaded workload writing thousands of ~8mb files across 16-32 threads, bottle-necked by my 1GBE network connection, aside from this, I rarely see the lockup trigger - maybe once or twice a month but only under heavy disk load - I'm yet to confirm this is disk writes but I don't recall any specific issues with disk reads. With the above threaded app, I was able to trigger crashes relatively quickly, maybe within an hour. When a crash occurs, audio (youtube/spotify) continue to play for a duration of a few minutes, the system appears responsive to anything that doesn't involve disk access - opening a gnome terminal from an existing one will open a gnome terminal but no prompt will show, an existing terminal I can run 'whoami' but `ls` will freeze the terminal permanently. `dmesg` also freezes the terminal. Eventually, audio will freeze and the system will totally lock up - my guess is the browser and/or X11 attempt to write to a log and end up removing any remaining responsiveness of the system. I have previously tried: - Replacing the SSD to ensure that it was not SSD hardware related - the second drive also froze in a similar way, so I had two working drives hence the raid. - Moving from Ubuntu to Debian, which didn't resolve the issue I have a few theories: - My unusually large amount of ram (for the processor) is somehow triggering a condition where flushing to disk fails, noting this would be contradicted by workstations/servers with substantially more - Something related to the CPU / Motherboard which occurs only on heavy PCIE usage or similar I'm unsure how to best test any theories, nor if my theories are sound/complete. I don't particularly want to brutalize the SSDs if I can avoid it, and formatting those SSDs would be difficult (though, I do have a third lower performance NVME SSD I could dedicate to such a task). Has anyone experienced similar or could make other suggestions I should try both in an attempt to diagnose the issue as well as once a lockup has occurred? | It seems a common element in this type of issue is NVME drives. Segregate duties. IMO raid doesn't help anything. Give the OS a channel all to itself. Give the IO load a different one, it's own. |
When I purchased the niuzu-minicomputer, there was a 256 MB Lexar nvme disk, to which Debian 12 went smoothly. Bought a 1 GB Kingston nvme, but that has been just a PITA. Tried with ESP-paritition and without, but always the installation halts when trying to install grub. Searched, and found this https://wiki.debian.org/EFIStub Tryid the manual method, there was some changes in Debian 12, so could not follow the wiki-page literally. But this caused that niuzu always boots to bios. So I am quite stuck now. | Hello, arzgi wrote: 2025-04-04 19:07 A small step. Found that efiboomgr works after these commands Code: Select allmodprobe efivarfs mount -t efivarfs none /sys/firmware/efi/efivars/ root@niuzu:# efibootmgr BootCurrent: 0003 Timeout: 1 seconds BootOrder: 0002 Boot0000: Windows Boot Manager Boot0002: debian Boot0003* UEFI: HL-DT-STBD-RE BP55EB40 1.03 [..] It seems you are trying to address several issues at once: 1) you cannot boot Debian independently from the two nvme disks with EFI (each disk has an independent Debian installation) 2) you are trying to boot by replacing the EFI boot loader (grub-efi) with an efi stub I would suggest focusing on the first (1) topic in this discussion. While waiting for the answer to @Bloom's observation, I note that in the EFI non-volatile memory (NMV) by efibootmgr command there is only one Debian entry for boot (there should be two, one for each Debian nvme disk). |
I've been at this for two days and I'm going around in circles. inxi -E Bluetooth: Message: No bluetooth data found. But dmesg finds Bluetooth after I run modproble btusb dmesg | grep -i bluetooth [ 222.734241] Bluetooth: Core ver 2.22 [ 222.734281] NET: Registered PF_BLUETOOTH protocol family [ 222.734282] Bluetooth: HCI device and connection manager initialized [ 222.734287] Bluetooth: HCI socket layer initialized [ 222.734290] Bluetooth: L2CAP socket layer initialized [ 222.734295] Bluetooth: SCO socket layer initialized [ 259.298178] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 259.298183] Bluetooth: BNEP filters: protocol multicast [ 259.298187] Bluetooth: BNEP socket layer initialized lsmod | grep -i bluetooth bluetooth 970752 14 btrtl,btmtk,btintel,btbcm,bnep,btusb ecdh_generic 16384 1 bluetooth rfkill 36864 7 rt2x00lib,asus_wmi,bluetooth,cfg80211 crc16 16384 2 bluetooth,ext4 But lsusb finds nothing Service is started systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Sun 2025-04-06 23:42:59 EDT; 12s ago Docs: man:bluetoothd(8) Main PID: 2920 (bluetoothd) Status: "Running" Tasks: 1 (limit: 9286) Memory: 808.0K CPU: 34ms CGroup: /system.slice/bluetooth.service └─2920 /usr/libexec/bluetooth/bluetoothd Apr 06 23:42:59 hostname systemd[1]: Starting bluetooth.service - Bluetooth service... Apr 06 23:42:59 hostname bluetoothd[2920]: Bluetooth daemon 5.66 Apr 06 23:42:59 hostname systemd[1]: Started bluetooth.service - Bluetooth service. But the /sys/class/bluetooth directory is empty and the Bluetooth Manager won't start This laptop is shipped with a Bluetooth adapter according to the specs. Machine: Type: Laptop System: ASUSTeK product: X550LA v: 1.0 serial: EBN0CV05026045G Mobo: ASUSTeK model: X550LA v: 1.0 serial: BSN12345678901234567 UEFI: American Megatrends v: X550LA.509 date: 06/26/2014 CPU: Info: dual core model: Intel Core i5-4210U bits: 64 type: MT MCP cache: L2: 512 KiB Speed (MHz): avg: 799 min/max: 800/2700 cores: 1: 798 2: 800 3: 800 4: 800 Something is missing or something is blocking the driver from loading? | https://wiki.debian.org/BluetoothUser Is a good starting point to solving bluetooth problems. |
Please list the output of these command: sudo rfkill list Then install inxi sudo apt install inxi once installed issue this command. inxi -Nn List results. | Hello, You computer is equipped with a Intel Ultra 7 155H CPU that is a "formerly Meteor Lake" [1]. According to the Debian Bug Tracking System (DBTS), the error message "Not valid error log pointer 0x0027B0C0 for RT uCode" in your dmesg log is a firmware error and it is cited in the following bug report: Debian Bug report logs - #1072108 linux-image-amd64: Enable CONFIG_PINCTRL_METEORLAKE This bug has been fixed in the kernel version 6.9.2-1~exp1 currently in Debian Experimental. Before attempting to upgrade the kernel, I would suggest you try modifying the /etc/modprobe.d/iwlwifi.conf file: Code: Select alloptions iwlwifi swcrypto=1 11n_disable=1 Then, run the command: Code: Select allsudo update-initramfs -u Then, reboot. See also [2]. Hope this helps. -- [1] Intel® Core™ Ultra 7 Processor 155H [2] Intel Wireless WiFi Link, Wireless-N, Advanced-N, Ultimate-N devices -- note: a) please use code tags to include logs or commands in the body of text messages; I modified for you the first post. b) moved to "Hardware" sub-forum. |
Hello, I will be reloading an old dell T610 with a H700 perc controller. I remember the driver for the megaraid devices was dropped in some flavors of linux a while ago. However, I was wondering if debian still supports these devices? If not, If I can remember correctly, I had to download a driver for it but do not remember where. | Do you want to use the Dell HW raid mode? Dell drivers only support rpm based systems but I think it should work without drivers - did you try? Most people advise against it though and use software raid instead. It seems that card cannot be flashed into IT/HBA mode (https://forums.servethehome.com/index.p ... ode.12130/) so you cannot use software raid on it. Depending on how valuable the data is that you want to store ... that's of course your decision. |
Hi All, No microphone input on a NUC running Bookworm. The microphone is plugged into a usb port and recognised but no sound shows on the Debian settings page. Please help, | Hello, usernamepasswordbs wrote: 2025-04-20 09:20 Whilst writing the above I thought about usb ports and tried the microphone in another one and it worked... Any idea why? I'm glad you sorted it out. Just a shot in the dark: maybe the microphone is not compatible with the previous USB port ? -- note: please edit the subject of the first message from "SOLVED (In record time !) No microphone input" to "[Solved] (In record time !) No microphone input" |
This is my first post on the board, so apologies if I miss anything. I recently installed Debian 12 (no desktop, but I'm using i3). My RTL8852BE wifi card gave me trouble by not working out of the box even with non-free firmware, but after installing the rtw89 drivers and upgrading to the 6.12.12 linux kernerl from bookwrom backports, it worked. But now whenever I close the lid to put my system to sleep, the wifi turns off. - Restarting network manager with "sudo systemctl restart NetworkManager.service" successfully restarts the service, but the wifi remains off - nmcli shows the wloi device (which is normally connected to my wifi network) as "unavailable" - ip a shows wloi as DOWN rather than UP as it normally is I have not yet found a way to turn wifi on after it turns itself off. I am able to disable sleep/suspension using the "systemctl mask" command, which does technically solve the issue, but I would rather not have my laptop running at all times. It appears there are many people with this problem on the internet, but I tried each and every proposed solution and none worked for me. I am using an HP-15-fd1007ne laptop. As stated, I am running Debian 12 with kernel 6.12.12. Thank you all for your time. EDIT: Here is the output of "sudo dmesg | grep rtw89" when the system starts, if it is of any help: Code: Select all[ 3.182220] rtw89: loading out-of-tree module taints kernel. [ 3.182234] rtw89: module verification failed: signature and/or required > [ 3.203858] rtw89_8852be 0000:01:00.0: loaded firmware rtw89/rtw8852b_fw-> [ 3.203997] rtw89_8852be 0000:01:00.0: enabling device (0000 -> 0003) [ 3.218148] rtw89_8852be 0000:01:00.0: Firmware version 0.29.29.5 (da87cc> [ 3.218159] rtw89_8852be 0000:01:00.0: Firmware version 0.29.29.5 (da87cc> [ 3.509925] rtw89_8852be 0000:01:00.0: chip rfe_type is 1 [ 3.540383] rtw89_8852be 0000:01:00.0: rfkill hardware state changed to e> [ 3.601488] rtw89_8852be 0000:01:00.0 wlo1: renamed from wlan0 [ 1353.359480] rtw89_8852be 0000:01:00.0: Unable to change power state from > [ 1353.448730] rtw89_8852be 0000:01:00.0: failed to write DBI register, addr> [ 1353.451067] rtw89_8852be 0000:01:00.0: failed to write DBI register, addr> [ 1353.451283] rtw89_8852be 0000:01:00.0: failed to read DBI register, addr=> [ 1353.451291] rtw89_8852be 0000:01:00.0: failed to read PCI cap, ret=134 [ 1353.526872] rtw89_8852be 0000:01:00.0: xtal si not ready(W): offset=90 va> [ 1353.547843] rtw89_8852be 0000:01:00.0: mac init fail, ret:-110 (Repeat those last two lines ~10 times) | Hello, There's an issue report marked as "solved" in the github repository of rtw89_8852be: rtw89_8852be: after resume WIFI is broken: #308 https://github.com/lwfinger/rtw89/issue ... 1918258496: In the meanwhile I have found the solution/workaround and I want to share it here so others can also benefit from it. This post pointed me to a solution that works. The problem is actually the PCIe as a whole. By adding following kernel parameter resuming works like a charm: Code: Select allpcie_port_pm=off Hope this helps. note: 1) Moved to "hardware" sub-forum. 2) Please, use code tags to include commands and/or their logs in the body of a message. Fixed it for you this time. |
I recently bought a 2.5 G switch and USB Ethernet adapters. I am now interested in buying a pci-e ethernet card. Anybody have recommendations for cards readily available in the U.S.. perhaps from Amazon or BestBuy? The TEG-25GECTX is based on a Realtek chip and works great. I ordered two more. I put the first on in an old Dell Inspiron 3668 that multi-boots; Mint Cinnamon, Mint Mate, Mint Xfce, debian12, and win10. No issues. | Discussion moved from "General Questions" to "Hardware" sub-forum. |
Debian Bookworm, Beelink s13 N150 mini PC I am having trouble getting hardware transcoding enabled on Debian for Plex. So far I have: -added /dev/dri path to my plex container -enabled iGPU in BIOS -installed the intel drivers -enabled / disabled HDR tone mapping, as well as set "Intel Alder Lake-N" as -the hardware transcoding device in plex -and I have updated the kernel to the latest backports release(6.12.9+bpo-amd64). When i run the intel_gpu_top command I get this output: intel_gpu_top: ../tools/intel_gpu_top.c init_engine_classes: Assertion `max >= 0' failed. vainfo output: vainfo output: error: can't connect to X server! libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit and i found these errors from dmesg: [ 4.866374] ---[ end trace 0000000000000000 ]--- [ 4.866598] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 4.866885] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc.bin (-2) [ 4.866892] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc.bin (-2) [ 4.866893] i915 0000:00:02.0: Direct firmware load for i915/adlp_dmc.bin failed with error -2 [ 4.866901] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc_ver2_16.bin (-2) [ 4.866906] i915 0000:00:02.0: firmware: failed to load i915/adlp_dmc_ver2_16.bin (-2) [ 4.866907] i915 0000:00:02.0: Direct firmware load for i915/adlp_dmc_ver2_16.bin failed with error -2 [ 4.866909] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/adlp_dmc.bin (-ENOENT). Disabling runtime power management. [ 4.866910] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/ke ... rmware.git [ 4.867702] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.bin (-2) [ 4.867708] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.bin (-2) [ 4.867716] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.1.1.bin (-2) [ 4.867721] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_70.1.1.bin (-2) [ 4.867726] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_69.0.3.bin (-2) [ 4.867731] i915 0000:00:02.0: firmware: failed to load i915/tgl_guc_69.0.3.bin (-2) [ 4.867732] i915 0000:00:02.0: [drm] ERROR GT0: GuC firmware i915/tgl_guc_70.bin: fetch failed -ENOENT [ 4.867738] i915 0000:00:02.0: [drm] GT0: GuC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/ke ... /tree/i915 [ 4.868291] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/tgl_guc_70.bin version 0.0.0 [ 4.868365] i915 0000:00:02.0: [drm] ERROR GT0: GuC initialization failed -ENOENT [ 4.868368] i915 0000:00:02.0: [drm] ERROR GT0: Enabling uc failed (-5) [ 4.868371] i915 0000:00:02.0: [drm] ERROR GT0: Failed to initialize GPU, declaring it wedged! Not really sure where to go from here. If anyone has any suggestions, please leave a comment. Let me know if I can provide any additional information. | You're running on hardware that's newer than Bookworm. I answered your question on Debian discord but you need to enable backports, update kernel, firmware and Mesa stack and install intel-media-va-driver-nonfree from Debian repos. The open-source driver decodes only, you need the nonfree driver to encode. Hope this helps - edit: working with OP on discord. edit v2.0 - marking this resolved. |
As I think everyone or almost everyone, I get upset when I see that damn Discover icon telling me my system isn't up to date, so every time I see it bright up, I click there and ignore what are going to be updated put my password and keep doing whatever I was doing. But ow dear how do I regret it. I had some problems with my WiFi adapter and got help here: viewtopic.php?t=161574, thanks to the boys i was happily surfing on the internet using my onboard WiFi adapter. Problem is, yesterday I did some update, didn't pay attention what was being updated and now I'm back to square 0, or maybe even worse. It worsened after rebooting my system. My first reaction was to open discover to check some historic, but it crashed a few times. On the 4th time, it opened. But I couldn't find any history. Googled it and found out I could find some log at /var/log/dpkg.log Code: Select all2025-01-31 09:22:47 startup archives unpack 2025-01-31 09:22:48 upgrade bind9-host:amd64 1:9.18.28-1~deb12u2 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status half-configured bind9-host:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status unpacked bind9-host:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status half-installed bind9-host:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status triggers-pending man-db:amd64 2.11.2-2 2025-01-31 09:22:48 status unpacked bind9-host:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 upgrade bind9-dnsutils:amd64 1:9.18.28-1~deb12u2 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status half-configured bind9-dnsutils:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status unpacked bind9-dnsutils:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status half-installed bind9-dnsutils:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status unpacked bind9-dnsutils:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 upgrade bind9-libs:amd64 1:9.18.28-1~deb12u2 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status triggers-pending libc-bin:amd64 2.36-9+deb12u9 2025-01-31 09:22:48 status half-configured bind9-libs:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status unpacked bind9-libs:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status half-installed bind9-libs:amd64 1:9.18.28-1~deb12u2 2025-01-31 09:22:48 status unpacked bind9-libs:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 upgrade git-man:all 1:2.39.5-0+deb12u1 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 status half-configured git-man:all 1:2.39.5-0+deb12u1 2025-01-31 09:22:48 status unpacked git-man:all 1:2.39.5-0+deb12u1 2025-01-31 09:22:48 status half-installed git-man:all 1:2.39.5-0+deb12u1 2025-01-31 09:22:48 status unpacked git-man:all 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 upgrade git:amd64 1:2.39.5-0+deb12u1 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 status half-configured git:amd64 1:2.39.5-0+deb12u1 2025-01-31 09:22:48 status unpacked git:amd64 1:2.39.5-0+deb12u1 2025-01-31 09:22:48 status half-installed git:amd64 1:2.39.5-0+deb12u1 2025-01-31 09:22:48 status unpacked git:amd64 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 upgrade libopenjp2-7:i386 2.5.0-2 2.5.0-2+deb12u1 2025-01-31 09:22:48 status half-configured libopenjp2-7:i386 2.5.0-2 2025-01-31 09:22:48 status unpacked libopenjp2-7:i386 2.5.0-2 2025-01-31 09:22:48 status half-configured libopenjp2-7:amd64 2.5.0-2 2025-01-31 09:22:48 status half-installed libopenjp2-7:i386 2.5.0-2 2025-01-31 09:22:48 status unpacked libopenjp2-7:i386 2.5.0-2+deb12u1 2025-01-31 09:22:48 upgrade libopenjp2-7:amd64 2.5.0-2 2.5.0-2+deb12u1 2025-01-31 09:22:48 status unpacked libopenjp2-7:amd64 2.5.0-2 2025-01-31 09:22:48 status half-installed libopenjp2-7:amd64 2.5.0-2 2025-01-31 09:22:48 status unpacked libopenjp2-7:amd64 2.5.0-2+deb12u1 2025-01-31 09:22:48 startup packages configure 2025-01-31 09:22:48 configure bind9-libs:amd64 1:9.18.33-1~deb12u2 <none> 2025-01-31 09:22:48 status unpacked bind9-libs:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status half-configured bind9-libs:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status installed bind9-libs:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 configure libopenjp2-7:amd64 2.5.0-2+deb12u1 <none> 2025-01-31 09:22:48 status unpacked libopenjp2-7:amd64 2.5.0-2+deb12u1 2025-01-31 09:22:48 status half-configured libopenjp2-7:amd64 2.5.0-2+deb12u1 2025-01-31 09:22:48 status installed libopenjp2-7:amd64 2.5.0-2+deb12u1 2025-01-31 09:22:48 configure libopenjp2-7:i386 2.5.0-2+deb12u1 <none> 2025-01-31 09:22:48 status unpacked libopenjp2-7:i386 2.5.0-2+deb12u1 2025-01-31 09:22:48 status half-configured libopenjp2-7:i386 2.5.0-2+deb12u1 2025-01-31 09:22:48 status installed libopenjp2-7:i386 2.5.0-2+deb12u1 2025-01-31 09:22:48 configure git-man:all 1:2.39.5-0+deb12u2 <none> 2025-01-31 09:22:48 status unpacked git-man:all 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 status half-configured git-man:all 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 status installed git-man:all 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 configure bind9-host:amd64 1:9.18.33-1~deb12u2 <none> 2025-01-31 09:22:48 status unpacked bind9-host:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status half-configured bind9-host:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status installed bind9-host:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 configure git:amd64 1:2.39.5-0+deb12u2 <none> 2025-01-31 09:22:48 status unpacked git:amd64 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 status half-configured git:amd64 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 status installed git:amd64 1:2.39.5-0+deb12u2 2025-01-31 09:22:48 configure bind9-dnsutils:amd64 1:9.18.33-1~deb12u2 <none> 2025-01-31 09:22:48 status unpacked bind9-dnsutils:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status half-configured bind9-dnsutils:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 status installed bind9-dnsutils:amd64 1:9.18.33-1~deb12u2 2025-01-31 09:22:48 trigproc man-db:amd64 2.11.2-2 <none> 2025-01-31 09:22:48 status half-configured man-db:amd64 2.11.2-2 2025-01-31 09:22:49 status installed man-db:amd64 2.11.2-2 2025-01-31 09:22:49 trigproc libc-bin:amd64 2.36-9+deb12u9 <none> 2025-01-31 09:22:49 status half-configured libc-bin:amd64 2.36-9+deb12u9 2025-01-31 09:22:50 status installed libc-bin:amd64 2.36-9+deb12u9 Then I thought, I'll redo the steps from last time. But running lspci I got this. Code: Select all00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge 00:02.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge GPP Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Data Fabric; Function 7 01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Upstream Port (rev 01) 02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) 02:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) 02:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) 02:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) 02:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) 02:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) 02:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset PCIe Switch Downstream Port (rev 01) 04:00.0 PCI bridge: ASMedia Technology Inc. ASM2806 4-Port PCIe x2 Gen3 Packet Switch (rev 01) 05:00.0 PCI bridge: ASMedia Technology Inc. ASM2806 4-Port PCIe x2 Gen3 Packet Switch (rev 01) 05:06.0 PCI bridge: ASMedia Technology Inc. ASM2806 4-Port PCIe x2 Gen3 Packet Switch (rev 01) 05:0e.0 PCI bridge: ASMedia Technology Inc. ASM2806 4-Port PCIe x2 Gen3 Packet Switch (rev 01) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8126 (rev 01) 0a:00.0 SATA controller: ASMedia Technology Inc. ASM1064 Serial ATA Controller (rev 02) 0c:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43fc (rev 01) 0d:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] 600 Series Chipset SATA Controller (rev 01) 0e:00.0 PCI bridge: ASMedia Technology Inc. Device 2421 (rev 01) 0f:00.0 PCI bridge: ASMedia Technology Inc. Device 2423 (rev 01) 0f:01.0 PCI bridge: ASMedia Technology Inc. Device 2423 (rev 01) 0f:02.0 PCI bridge: ASMedia Technology Inc. Device 2423 (rev 01) 0f:03.0 PCI bridge: ASMedia Technology Inc. Device 2423 (rev 01) 70:00.0 USB controller: ASMedia Technology Inc. Device 2426 (rev 01) 71:00.0 USB controller: ASMedia Technology Inc. Device 2425 (rev 01) 72:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Granite Ridge [Radeon Graphics] (rev c6) 72:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller 72:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] VanGogh PSP/CCP 72:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI 72:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge USB 3.1 xHCI 72:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller 73:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b8 My dear 06:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01) isn't there. Already double checked the BIOS configuration to see if somehow it was disabled, but everything seems fine. Any ideas of what can I do ? | Hello, What is the kernel version you are currently running ? Are you double booting with another operating system (e.g. Windows) ? Does you bios detect the Wifi network adapter ? -- note: please edit the subject of the first post from "MB MSI X870-P WIFI - problem with Wifi network adapter Qualcomm WCN785x Wi-Fi 7(802.11be)" to "MB MSI X870-P WIFI - Wifi network adapter Qualcomm WCN785x Wi-Fi 7(802.11be) not detected" |
Ok.. Last post I saw regarding this was in 08, and that was specific to KDE. Quick down and dirty to get this working. The Makefiles in the official drivers from ASUS is going to fail, and I found it was just easier to do this vs. fixing their make files. My base system config is Debian 11.4, clean install. Bluetooth service and bluman and bluez are all installed and showing error free. I'm running kernel 5.18.0-4amd64. 1. Download the drivers from asus.. https://www.asus.com/us/Networking-IoT- ... _Download/ 2. unzip the archive and dig through the file structure (itll be different based on the driver version, but for me it was 2 levels deep before it becomes normal) until you find the rtkbt-firmware/lib/firmware folder. 3. Copy the rtl8761bu_config and rtl8761bu_fw files out and into /lib/firmware/rtl_bt folder (you'll have to create that) 4. rename both files to end in .bin 5. insert your usb bluetooth adapter and you should* see you bluetooth manager show up in your well.. wherever you'd expect to see it based on your desktop environment. bluetoothctl list will show your adpater as well so will hciconfig -a you may have to do a systemctl restart bluetooth for it to work if you've already inserted the bt adapter before step 5. I know this seems simple, and it should be... but their installer is jacked up. It starts by unloading the btusb module, then renaming it. Then it changes directories and the make file fails. It is supposed to create a new kernel module, but that isn't happening for whatever reason (I'm getting an error about all: on line 10 of the make file). All of these make files are doing is literally replacing a compatible module with a compatible module... and that is an absolute waste of time. The only thing missing in Debian 11.4 is the firmware that I have you copy and rename in 3 and 4. I hate to say it but this took me a couple hours to chase through errors and the like.. so as a newb I feel accomplished, and I hope I can save someone else some effort. The reason I bought this was because it said it supported linux out the box, and that may be true.. for kernels 2.6.32 - 5.7, but that's not what 11.4 ships with (which is 5.10 and higher). Hope this helps | I just looked at the ASUS download page you linked. Maybe the make problem is: Driver Package Version v0202 2020/12/08 4.9 MBytes ASUS USB-BT500 Driver 1.0.0.8 for Linux Support kernel 2.6.32 - 5.7.1 Manually copying the files to the correct location seems to be the obvious solution. Hopefully this thread will help others. Please edit the title of your first post to add [SOLVED] so it may. |
Hello friends For a laptop HP Pavilion g4-1387la was installed Debian 12 Desktop The ethernet and wifi connections are possible. But when only the WIFI is used (no ethernet cable connected) exists the problem that the internet speed is very slow. I put the same WIFI connection settings according with other laptops in the same LAN, all of them based with other Linux distributions. Of course the ipv4 is unique The wireless card is as follows (let me know if you need more data - pls indicate me the command execute to share the info): Code: Select alllspci -vq | grep -i wireless 02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 802.11bgn Wireless Network Adapter (rev 01) Subsystem: Hewlett-Packard Company BCM4313 802.11bgn Wireless Network Adapter Through Synaptic Package Manager using the Broadcom term exists the following: Ignore the airplane mode shown above in the right top Because it is a direct installation in the laptop and I don't want harm nothing What I should do? Yes, I already did do a research and I found the following just a kind of reference: How do I install non-free firmware in Debian 12 (Bookworm)? It to let me later install more packages about Broadcom (correct me if I am wrong) And execute the following commands (it according with some videos on YouTube about when Ubuntu (based on Debian) is installed in a MacBook Pro 2012 and the wifi card is not detected) Code: Select allsudo apt-get purge bcmwl-kernel-source sudo apt-get install firmware-b43-installer Thanks for your understanding | Hello, A similar discussion with different hardware is in progress: https://forums.debian.net/viewtopic.php?t=161347 You can try to take advice from it to check the hardware configuration, wireless protocols used, data rates (and so on) as seen by Debian to get more information and clues. -- notes: 1) moved to "Hardware" sub-forum 2) added "BCM4313 802.11bgn Wireless Network Adapter" to the subject of the first post |
I'm looking for some help/guidance about my WiFi connection. I am using an old Dell Laptop with an Intel Centrino Wireless N-230 adapter. The KDE graphical network manager scans the nearby networks but when a connection is attempted to one of them it just does not happen. The same happens when using nmcli from the console. I've been doing some googling and based on that here's some info. /etc/NetworkManager/NetworkManager.conf Code: Select all[main] plugins=ifupdown,keyfile [ifupdown] managed=true [device] wifi.scan-rand-mac-address=no /etc/network/interfaces Code: Select allsource /etc/network/interfaces.d/* auto lo iface lo inet loopback Package ifupdown is installed. I can provide any additional details as required. | Hello, Can you please provide more information about your computer's hardware and configuration ? You can use the following commands (the inxi package must be installed): Code: Select allinxi -nsrxxxz lspci -vnn -d ::0280 Is the firmware installed ? You can use the following command: Code: Select allsudo journalctl -b -g iwl\|firm How does the operating system recognise the capabilities of a wireless network adapter? You can use the following commands: Code: Select allsudo iw list nmcli dev show nmcli dev status Can you check the make and model of an access point you cannot connect to ? What are the AP you cannot connect ? You can use the following command: Code: Select allnmcli dev wifi list Hope this helps. -- note: 1) moved to "Hardware" sub-forum. 2) please add "Intel Centrino Wireless N-230 adapter" to the subject of the first post, i.e.: "Debian 12 KDE Wi-Fi connectivity issue with Intel Centrino Wireless N-230 adapter" -- [1] https://www.intel.com/content/www/us/en ... tions.html |
I'm facing a situation that I have no idea how to solve. Got my new MB and until now i cant get it to work properly. Sadly I only checked about the rtl8126 after getting it. There is a lot of sites saying it isnt good. But that is the lan, wifi bluetooth on this mb. At the moment i'm connected to internet using my smartphone tethered, it works but not optimal. I went to MSI looking for drivers but they only offer for windows 10 & 11 https://www.msi.com/Motherboard/PRO-X87 ... ort#driver. Then i looked the chipset and found out the name for at least the lan driver, my goal is to enable the wlan .. and I'm hoping this one solves everything tbh. I've downloaded the driver from Realtek from here: https://www.realtek.com/Download/List?cate_id=584. I've tryed both: 2.5G Ethernet LINUX driver r8125 for kernel up to 6.9 and the 5G Ethernet LINUX driver r8126 for kernel up to 6.8 after downloading I tryed to instal it, but the make command didnt work, sorry, i have not saved the message then, but had something with headers, i fixed it following this procedure https://www.tecmint.com/install-kernel- ... nd-debian/. In essence just one command was needed sudo apt install linux-headers-$(uname -r) Then now the make was supposed to run, but i got some new messages, and well I still cant install the damn driver. (changed my username because, well dont know) Code: Select all:~/Downloads/rtl8126$ sudo make CC: cc CCVERSION: 12 KERNEL_GCC_VERSION: KVER: 6.1.0-30-amd64 KMAJ: 6 KMIN: 1 KREV: 0 BASEDIR: /lib/modules/6.1.0-30-amd64 DRIVERDIR: /lib/modules/6.1.0-30-amd64/kernel/drivers/net/ethernet/realtek PWD: /home/username/Downloads/rtl8126 RTKDIR: kernel/drivers/net/ethernet/realtek make -C /lib/modules/6.1.0-30-amd64/build M=/home/username/Downloads/rtl8126 clean make[1]: Entering directory '/usr/src/linux-headers-6.1.0-30-amd64' CLEAN /home/username/Downloads/rtl8126/Module.symvers make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-30-amd64' make -C /lib/modules/6.1.0-30-amd64/build M=/home/username/Downloads/rtl8126 modules make[1]: Entering directory '/usr/src/linux-headers-6.1.0-30-amd64' CC [M] /home/username/Downloads/rtl8126/r8126_n.o CC [M] /home/username/Downloads/rtl8126/rtl_eeprom.o CC [M] /home/username/Downloads/rtl8126/rtltool.o LD [M] /home/username/Downloads/rtl8126/r8126.o MODPOST /home/username/Downloads/rtl8126/Module.symvers CC [M] /home/username/Downloads/rtl8126/r8126.mod.o LD [M] /home/username/Downloads/rtl8126/r8126.ko BTF [M] /home/username/Downloads/rtl8126/r8126.ko Skipping BTF generation for /home/username/Downloads/rtl8126/r8126.ko due to unavailability of vmlinux make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-30-amd64' make -C /lib/modules/6.1.0-30-amd64/build M=/home/username/Downloads/rtl8126 INSTALL_MOD_DIR=kernel/drivers/net/ethernet/realtek modules_install make[1]: Entering directory '/usr/src/linux-headers-6.1.0-30-amd64' INSTALL /lib/modules/6.1.0-30-amd64/kernel/drivers/net/ethernet/realtek/r8126.ko DEPMOD /lib/modules/6.1.0-30-amd64 Warning: modules_install: missing 'System.map' file. Skipping depmod. make[1]: Leaving directory '/usr/src/linux-headers-6.1.0-30-amd64' I looked for some way to fix it, but couldn't find anything i could really understand, so if someone could give me some heads up I'll be very gratefull. My skill level isn't very high, but i think i can run some commands. | Hello, Which of these two network adapters are you interested in? Code: Select all06:00.0 Network controller: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] (rev 01) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 8126 (rev 01) What is the output of the following commands ? Code: Select alllspci -vnn -d ::0200 lspci -vnn -d ::0280 |
Printer is connected via netvork. Driverless printing prints only single sided but I can print multiple copies. Whit HPLIP driver duplex printing works but only one copy. Any ideas to fix? | Could it be this issue? I have done some more digging - and paper wasting. It appears that on kernels past 5.15.0-86, it is necessary to explicitly set "Double Sided Printing" to "On" in "Printer Options" in printer setup. With kernels prior to 5.15.0-87, it is enough to tell the printer to print double sided (duplex) at print time. https://forums.linuxmint.com/viewtopic.php?t=406778 |
Hello y'all, I recently installed Debian 12 on my Laptop. So far, most things work fine but two. After wandering through countless discussions and forums, I must admit that I am now at my wits end. My specs are: 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-31-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-1035G4 CPU @ 1.10GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics Manufacturer: Acer Product Name: Spin SP314-54N System Version: V1.13 It is a Notebook, so I have a Touchscreen and a corresponding Pen. I am currently trying to get my touchpad to work. I've managed for it to be shown in my Settings (first it was nit detected at all) but I didn't get any further. In my Settings, the Laptop registers a Touchpad after I copied the file "40-libinput.conf" from usr/share/X11/xorg.conf.d to etc/X11/xorg.conf.d. I then stumbled across this forum post: https://wiki.debian.org/SynapticsTouchpad but either I do not understand it or it did not work. Using the first command, I get: N: Name="SynPS/2 Synaptics TouchPad" However, in my etc/X11/xorg.conf.d I cannot find a synaptics.conf file. If you need anything else, I am glad to provide you with more information. As far as I understood the forums, Touchscreen support does not come natively, is currently worked on and most of the time you have to try workarounds. Is that correct? Thank you in advance! | In cases like that I use to try it with different distros (Ventoy stick with Mint, MX ....) and if you are lucky, it works out of the box. Then there is the chance (inxi) to look for hardware and driver. Welcome to the forum |
Hi, I got this low end laptop (open box) for about $68.00 from Micro Center this morning. It came with Windows 10 and worked pretty good. I did a full hard drive install of Debian 12 and its working great with the exception that wifi did not work and the audio/microphone is very very low. I was able to fix the wifi by installing the drivers from this website: https://github.com/lwfinger/rtw88 Prerequiste before install: Code: Select allsudo apt update && sudo apt upgrade sudo apt install linux-headers-$(uname -r) build-essential git Installation: Code: Select allgit clone https://github.com/lwfinger/rtw88 cd rtw88 make sudo make install sudo make install_fw I just put the above wifi information in case someone else gets this laptop and comes across this post. I have not been able to find a solution to the audio issue though. Again the audio is very low and I can barely hear anything with max volume and the microphone has the same issue its very low. So basically low output and low input. Running inxi -A gives the following information: Code: Select allAudio: Device-1: Intel Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster driver: sof-audio-pci-intel-apl API: ALSA v: k6.1.0-31-amd64 status: kernel-api Server-1: PulseAudio v: 16.1 status: active Anyone have any tips/solutions on how I can get the audio/microphone to work normally? Thanks. | Welcome to the forum! Could we have full system information and kernel messages after a fresh boot please? Code: Select all$ inxi -Far --vs --za Code: Select all# dmesg | grep 'sof\|firmware\|audio\|snd\|hda\|intel|\alsa' Edit: used a better inxi command. |
Good morning. I realized that with LXQT on debian 11 there is no graphical application for managing Bluetooth devices. I think the integrated card is already working in fact from the terminal giving a rfkill I get Code: Select allID TYPE DEVICE SOFT HARD 0 bluetooth tpacpi_bluetooth_sw blocked unblocked 1 wlan phy0 unblocked unblocked I would like to know if the best way is to install the KDE tool and if the command below is sufficient: Code: Select all$ sudo apt install Bluetooth bluedevil bluez bluez-tools pulseaudio-module-Bluetooth Thanks so much in advance for your help | Install blueman? Code: Select all# apt install blueman |
I am on stable Code: Select all$ uname -r 6.1.0-31-amd64 Is there a way to show DDR5 memory temperature by, says, lm-sensors command? Web searches seem pointing to SPD5118 driver for a newer kernel?? https://sources.debian.org/src/linux/6. ... d5118.rst/ | Hello, Some interesting lectures: memtest86plus: Display DDR5 memory modules temperature memtest86plus: Display DDR5 SPD5 Hub memory modules temperature Linux Kernel: Kernel driver spd5118 [PATCH 0/3] hwmon: Add support for SPD5118 compliant temperature sensors The kernel module is named spd5118, see: Naming and data format standards for sysfs files With a recent kernel, you can inspect the /sys file system: Code: Select allls -Ra /sys/class/hwmon/ According to www.kernel.org, for 6.12 it should be merged on 2024-07-15: https://git.kernel.org/pub/scm/linux/ke ... q=SPD5118+ . AgeCommit message (Expand)AuthorFilesLines 2024-07-15Merge tag 'hwmon-for-v6.11' of git://git.kernel.org/pub/scm/linux/kernel/git/...Linus Torvalds92-2254/+4413 2024-06-18hwmon: (spd5118) Add support for Renesas/ITD SPD5118 hub controllersGuenter Roeck1-0/+56 2024-06-10hwmon: (spd5118) Add configuration option for auto-detectionGuenter Roeck2-2/+21 2024-06-10i2c: smbus: Support DDR5 and LPDDR5 SPD EEPROMsGuenter Roeck1-1/+5 2024-06-10hwmon: (spd5118) Add support for reading SPD dataGuenter Roeck2-4/+150 2024-06-10hwmon: Add support for SPD5118 compliant temperature sensorsGuenter Roeck5-0/+550[/code] |
I just installed OMV 5 on a R520 with a 10gb SFP NIC. I was able to use the NIC and set it up durning installation, but after I installed OMV it is no longer working. Both the standard Gig NIC are working but not the 10Gb. I am getting the following error : [683.622341] bnx2x 0000:0c:00.0: firmware: failed to load bnx2x/bnx2x-e2-7.13.11.0.fw (-2) [683.622604] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [683.622845] bnx2x: [bnx2x_func_hw_init:6002(enp12s0f0)] Error loading firmware [683.623109] bnx2x: [bnx2x_nic_load:2730(enp12s0f0)] HW init failed, aborting Code: Select allispci |egrep -i 'network|ethernet' 02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5720 Gigabit Ehternet PCIe 02:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5720 Gigabit Ehternet PCIe 0c:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10) 0c:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10) I have tried installing the Broadcom firmware: Code: Select allapt install firmware-bnx2x firmware-bnx2x is already the newest version (20190114-2) I reinstall both firmware-linux and firmware-linux-nonfree and nothing is helping. According to this site (https://cateee.net/lkddb/web-lkddb/NET_ ... ADCOM.html) this ethernet card is supported in 3.2–3.19, 4.0–4.20, 5.0–5.6, 5.7-rc+HEAD kernals. Code: Select alluname -a Linux Hulk 5.4.0-0.bpo.4-amd64 #1 SMP Debian 5.4.19-1~bpo10+1 (2020-03-09) x86-64 GNU/Linux Code: Select alldmesg |grep -i eth [ 1.652289] tg3 0000:02:00.0 eth0: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b0:83:fe:d9:87:e2 [ 1.652292] tg3 0000:02:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) [ 1.652293] tg3 0000:02:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] [ 1.652294] tg3 0000:02:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit] [ 1.676163] tg3 0000:02:00.1 eth1: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address b0:83:fe:d9:87:e3 [ 1.676166] tg3 0000:02:00.1 eth1: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) [ 1.676167] tg3 0000:02:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] [ 1.676168] tg3 0000:02:00.1 eth1: dma_rwctrl[00000001] dma_mask[64-bit] [ 1.678003] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36-0 (2014/02/10) [ 1.678105] tg3 0000:02:00.0 eno1: renamed from eth0 [ 1.697604] tg3 0000:02:00.1 eno2: renamed from eth1 [ 2.049215] bnx2x 0000:0c:00.1 enp12s0f1: renamed from eth1 [ 2.061828] bnx2x 0000:0c:00.0 enp12s0f0: renamed from eth0 [ 23.726535] ACPI Error: Aborting method \_SB.PMI0._GHL due to previous error (AE_NOT_EXIST) (20190816/psparse-531) [ 23.726644] ACPI Error: Aborting method \_SB.PMI0._PMC due to previous error (AE_NOT_EXIST) (20190816/psparse-531) Code: Select alllspci |grep -i broadcom 02:00.0 Ethernet controller: Broadcom Limited NetXtreme BCM5720 Gigabit Ethernet PCIe 02:00.1 Ethernet controller: Broadcom Limited NetXtreme BCM5720 Gigabit Ethernet PCIe 0c:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10) 0c:00.1 Ethernet controller: Broadcom Limited NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10) Code: Select alldmesg |grep bnx2x [ 1.678003] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.36-0 (2014/02/10) [ 1.678121] bnx2x 0000:0c:00.0: msix capability found [ 1.678348] bnx2x 0000:0c:00.0: part number 0-0-0-0 [ 1.830406] bnx2x 0000:0c:00.0: 16.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x4 link at 0000:00:1c.0 (capable of 32.000 Gb/s with 5 GT/s x8 link) [ 1.899294] bnx2x 0000:0c:00.1: msix capability found [ 1.899594] bnx2x 0000:0c:00.1: part number 0-0-0-0 [ 2.047248] bnx2x 0000:0c:00.1: 16.000 Gb/s available PCIe bandwidth, limited by 5 GT/s x4 link at 0000:00:1c.0 (capable of 32.000 Gb/s with 5 GT/s x8 link) [ 2.049215] bnx2x 0000:0c:00.1 enp12s0f1: renamed from eth1 [ 2.061828] bnx2x 0000:0c:00.0 enp12s0f0: renamed from eth0 Code: Select allmodinfo bnx2x filename: /lib/modules/5.4.0-0.bpo.4-amd64/kernel/drivers/net/ethernet/broadcom/bnx2x/bnx2x.ko firmware: bnx2x/bnx2x-e2-7.13.11.0.fw firmware: bnx2x/bnx2x-e1h-7.13.11.0.fw firmware: bnx2x/bnx2x-e1-7.13.11.0.fw version: 1.713.36-0 license: GPL description: QLogic BCM57710/57711/57711E/57712/57712_MF/57800/57800_MF/57810/57810_MF/57840/57840_MF Driver author: Eliezer Tamir srcversion: BAEF9F0DFB141BD2A3EE3A6 alias: pci:v000014E4d0000163Fsv*sd*bc*sc*i* alias: pci:v000014E4d0000163Esv*sd*bc*sc*i* alias: pci:v000014E4d0000163Dsv*sd*bc*sc*i* alias: pci:v00001077d000016ADsv*sd*bc*sc*i* alias: pci:v000014E4d000016ADsv*sd*bc*sc*i* alias: pci:v00001077d000016A4sv*sd*bc*sc*i* alias: pci:v000014E4d000016A4sv*sd*bc*sc*i* alias: pci:v000014E4d000016ABsv*sd*bc*sc*i* alias: pci:v000014E4d000016AFsv*sd*bc*sc*i* alias: pci:v000014E4d000016A2sv*sd*bc*sc*i* alias: pci:v00001077d000016A1sv*sd*bc*sc*i* alias: pci:v000014E4d000016A1sv*sd*bc*sc*i* alias: pci:v000014E4d0000168Dsv*sd*bc*sc*i* alias: pci:v000014E4d000016AEsv*sd*bc*sc*i* alias: pci:v000014E4d0000168Esv*sd*bc*sc*i* alias: pci:v000014E4d000016A9sv*sd*bc*sc*i* alias: pci:v000014E4d000016A5sv*sd*bc*sc*i* alias: pci:v000014E4d0000168Asv*sd*bc*sc*i* alias: pci:v000014E4d0000166Fsv*sd*bc*sc*i* alias: pci:v000014E4d00001663sv*sd*bc*sc*i* alias: pci:v000014E4d00001662sv*sd*bc*sc*i* alias: pci:v000014E4d00001650sv*sd*bc*sc*i* alias: pci:v000014E4d0000164Fsv*sd*bc*sc*i* alias: pci:v000014E4d0000164Esv*sd*bc*sc*i* depends: mdio,libcrc32c,ptp retpoline: Y intree: Y name: bnx2x vermagic: 5.4.0-0.bpo.4-amd64 SMP mod_unload modversions sig_id: PKCS#7 signer: Debian Secure Boot CA sig_key: A7:46:8D:EF sig_hashalgo: sha256 signature: B1:C2:FE:62:2E:6A:AD:E4:DE:1E:C3:4E:FC:78:29:BC:C6:D0:D8:8F: 03:62:26:45:21:01:2F:87:6F:61:47:05:F7:33:6B:63:E4:4A:9A:1A: F2:E6:B1:33:9F:F2:A4:4E:9F:65:E1:65:D7:26:2A:1F:04:23:CE:E3: 07:91:5C:83:53:A7:C9:F3:07:AD:1F:8D:2F:51:E7:25:37:D4:E1:CD: 9B:60:99:C5:18:42:11:DF:60:43:06:06:E6:50:B3:11:B0:CB:0B:97: 6A:E8:39:3F:94:E1:91:5D:54:0A:DE:5D:E4:19:E7:D7:1E:F9:48:15: 0F:37:48:BC:87:32:81:10:50:F5:0F:B4:9D:8F:15:51:5A:D4:41:20: 5B:84:53:20:B7:24:81:CC:73:67:38:DE:F4:31:A2:F3:28:B3:94:EA: 35:C2:52:FF:7E:38:46:DE:75:40:C2:02:E1:DE:ED:51:D9:C9:DB:C9: B9:EE:FE:B9:B7:0B:DA:E0:6B:82:8F:43:CD:DB:21:E3:AB:B1:76:51: 61:F8:D4:38:5E:BF:D0:8F:7E:F1:FC:B6:03:27:92:E3:E6:76:55:0B: 0C:5D:9C:92:89:AC:49:72:12:B5:DE:04:DD:6D:07:04:76:1B:5A:DE: B5:F7:85:68:FC:C9:39:B4:7D:0D:33:58:D8:4F:76:F5 parm: num_queues: Set number of queues (default is as a number of CPUs) (int) parm: disable_tpa: Disable the TPA (LRO) feature (int) parm: int_mode: Force interrupt mode other than MSI-X (1 INT#x; 2 MSI) (int) parm: dropless_fc: Pause on exhausted host ring (int) parm: mrrs: Force Max Read Req Size (0..3) (for debug) (int) parm: debug: Default debug msglevel (int) | Moved to "Hardware" sub-forum. marked as "Solved". |
Hey folks, I have a problem with one of my external usb disks. I have two different 8TB Seagate disks (ext4) on my homeserver (debian 12) and I managed to get the first one running and suspending like a charm - with some support of this fine forum in the following thread: viewtopic.php?p=810322#p810322 So I did the same things for the second drive and it looks like it should work the same way - but it doesn't. I added the quiks an now it reports all the expected data from hdparm and smartctl as expected. But when ever I use any hdparm command to suspend the disk (like hdparm -y), it spinns down and immediately up again. I don't know why. I read some stuff about btrace, but since I am a noob, I don't figured out, how to find threads that keep the disk active. Also it is not after some minutes, it is just immediately. I already checked for udisk, but it seems, that it is not present on my system. Any kind of guesses, hints and explanation on how to use btrace (or smth. similar) would be appreciated. Kind regards FatalDiskError | OK, so you obviously know about the hdparm setting to let it spin down when idle. It's USB, right? Most likely something on the system it tickling the disk to wake it up. You can try putting the system in single-user-mode to test this out. In runlevel-1 nothing should touch a USB disk unless you actively tickle it. If it still won't stay idle then the problem is probably in the disk itself, or the USB-to-sata controller. |
Hello, the brightness control on my laptop has not been working properly lately (I don't remember when it started not working or what package update could have broke it, sorry). Right after I boot my laptop, I am able to adjust the display brightness normally and it just works as it always has, however, if I put my laptop in sleep mode, upon waking it from sleep mode the brightness will only go between max brightness and slightly lower than max brightness, regardless of whether the i set it to 0% or 100%. So far, i've tried booting my PC with the kernel parameter "amdgpu.backlight=0" and "acpi_backlight=video" which did not help. The issue still occurs regardless of whether I use X11 or Wayland. I haven't enabled any power saving settings that would affect the brightness. amdgpu:brightness and amdgpu:actual_brightness both have correct values (I mention this since i've seen that people have had issues similar to what i'm describing caused by these values being wrong). Im assuming that this is caused by kernel 6.1 but I don't know when it was updated from 6.0 so it's possible that this is unrelated. here is the info output about the display by hwinfo in case its relevant: Code: Select all37: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.PcbQ5WIBmmB Parent ID: B35A.F7kdotf2ld0 Hardware Class: monitor Model: "LCD Monitor" Vendor: BOE Device: eisa 0x07b5 Serial ID: "0" Resolution: 1366x768@60Hz Size: 309x173 mm Year of Manufacture: 2018 Week of Manufacture: 5 Detailed Timings #0: Resolution: 1366x768 Horizontal: 1366 1414 1446 1528 (+48 +80 +162) -hsync Vertical: 768 771 777 790 (+3 +9 +22) +vsync Frequencies: 48.28 MHz, 31.60 kHz, 40.00 Hz Year of Manufacture: 2018 Week of Manufacture: 5 Detailed Timings #1: Resolution: 1366x768 Horizontal: 1366 1414 1446 1528 (+48 +80 +162) -hsync Vertical: 768 771 777 790 (+3 +9 +22) +vsync Frequencies: 72.42 MHz, 47.40 kHz, 59.99 Hz Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (VGA compatible controller) My PC is on Debian 12 stable with KDE plasma as the desktop environment and an AMD(integrated) GPU. Thank you for any help with troubleshooting this!! | Install brightnessctl then man it |
Dear Community, since I updated to the backported 6.11.x kernel and updated to the backported intel wifi drivers (because wifi wouldn't work without them), wifi (AX211) shows noticeably higher power draw in powertop. It seems that some powersaving features were disabled or do not work properly anymore. Do you experience the same? Is there a fix? Thanks in advance! Chief | Hello, ChiefBigFeather wrote: 2025-01-16 10:39 since I updated to the backported 6.11.x kernel and updated to the backported intel wifi drivers (because wifi wouldn't work without them), wifi (AX211) shows noticeably higher power draw in powertop. It seems that some powersaving features were disabled or do not work properly anymore. Do you experience the same? Is there a fix? What is you wireless device exactly as per lspci -vnn output ? Can you report figures from powertop ? You may see here: Linux Wireless documentation - iwlwifi: Power management Starting from 3.17, power management has been disabled in iwldvm because users reported it improved the behavior and was a valid work around for issues. The commit that disabled power management is here. To enable manually power management, you can set the following module parameters to these values: iwlwifi.power_save=Y and iwldvm.force_cam=N. iwlwifi: dvm: disable power save by default Hope this helps. |
Recently reinstalled Debian due to some issues. Previous install had Cinnamon default, which I later changed to XFCE via command line install. Then I had to do a full reinstall of Debian, I decided to choose the XFCE install image because i preferred it over Cinnamon. Both installs were on Debian 12. While everything else works great, for some reason the Wi-Fi speed is noticeably slower, on Cinnamon I had consistent 10mb/s downloading steam games and various packages, now on XFCE i barely get 1-2mb/s. I think i chose the live install image option both times, so the only difference would be in desktop environments. Running Code: Select alllspci -nnk | grep -iA3 net && iwconfig shows: Code: Select all01:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821] DeviceName: WLAN Subsystem: Hewlett-Packard Company RTL8821CE 802.11ac PCIe Wireless Network Adapter [103c:884d] Kernel driver in use: rtw_8821ce Kernel modules: rtw88_8821ce, rtw_8821ce 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) DeviceName: Hanksville Gbe Lan Connection Subsystem: Hewlett-Packard Company RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [103c:8905] Kernel driver in use: r8169 Kernel modules: r8169 lo no wireless extensions. eno1 no wireless extensions. wlo1 IEEE 802.11 ESSID:"*******************" Mode:Managed Frequency:2.462 GHz Access Point: CC:32:E5:7B:96:05 Bit Rate=135 Mb/s Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=59/70 Signal level=-51 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:3 Missed beacon:0 Looking around online, it seems like this card has a lot of issues on linux, so i might just get it replaced. I've tried: turning off power management (which made a small improvement), installing drivers from the rtw88 github repo by lwfinger, which didn't seem to have any effect. I also looked in /etc/NetworkManager/conf.d/ for a configuration file, but there seemed to be none. So, is there some kind of config setting present in the Cinnamon install, which is for some reason missing in the XFCE image? Is it just a problem with this specific Wi-Fi card? | Code: Select allarto@dell:~$ uname -a Linux dell 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) x86_64 GNU/Linux arto@dell:~$ Code: Select allarto@dell:~$ apt-file search 8821ce linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-29-amd64: /lib/modules/6.1.0-29-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-29-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-29-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-29-amd64-unsigned: /lib/modules/6.1.0-29-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-29-rt-amd64: /lib/modules/6.1.0-29-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-29-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-29-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-29-rt-amd64-unsigned: /lib/modules/6.1.0-29-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-30-amd64: /lib/modules/6.1.0-30-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-30-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-30-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-30-amd64-unsigned: /lib/modules/6.1.0-30-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-30-rt-amd64: /lib/modules/6.1.0-30-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-30-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-30-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-30-rt-amd64-unsigned: /lib/modules/6.1.0-30-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko arto@dell:~$ You should not need anything from the github. Also selected desktop does have nothing to do with wifi. But if you have found that device does not work well in Linux, maybe try an other. |
I am using a Dell Inspiron 3030S Small Desktop computer with Debian 12 Bookworm and XFCE, and I am not getting any sound from the rear audio line-out port. And pavucontrol lists, under "Output Devices", only the HDMI connection to my monitor ("HDMI/DisplayPort (plugged in)"). - The computer's BIOS says, under "Audio Controller", just "Cirrus". - The manual for the computer, downloaded from Dell's website (https://dl.dell.com/content/manual11111 ... uage=en-us), says, on Page 18, that the audio is "Cirrus Logic CS8409, CS42L42 (headphone codec)". - The output from lspci contains neither the word "Cirrus" nor the word "CS8409" anywhere. The following would seem to be the only relevant line in the output, and I suspect that it refers to the HDMI connection to my monitor: Code: Select all0000:00:1f.3 Audio device: Intel Corporation Alder Lake-S HD Audio Controller (rev 11) - The output from lshw contains neither the word "Cirrus" nor the word "CS8409" anywhere. The following would seem to be the only relevant lines in the output, and, again, I suspect that they refer to the HDMI connection to my monitor: Code: Select all*-multimedia description: Audio device product: Alder Lake-S HD Audio Controller vendor: Intel Corporation physical id: 1f.3 bus info: pci@0000:00:1f.3 logical name: card0 logical name: /dev/snd/controlC0 logical name: /dev/snd/hwC0D0 logical name: /dev/snd/hwC0D2 logical name: /dev/snd/pcmC0D3p logical name: /dev/snd/pcmC0D7p logical name: /dev/snd/pcmC0D8p logical name: /dev/snd/pcmC0D9p version: 11 width: 64 bits clock: 33MHz capabilities: pm msi bus_master cap_list configuration: driver=snd_hda_intel latency=64 resources: iomemory:600-5ff iomemory:600-5ff irq:159 memory:6003230000-6003233fff memory:6003000000-60030fffff - The output from "cat /proc/asound/card*/codec* | grep Codec" is: Code: Select allCodec: Cirrus Logic CS8409 Codec: Intel Alderlake HDMI - The output from "dmesg | grep -i audio" is: Code: Select all[ 2.041813] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 2.121021] snd_hda_codec_cs8409 hdaudioC0D0: autoconfig for CS8409: line_outs=1 (0x25/0x0/0x0/0x0/0x0) type:line [ 2.121025] snd_hda_codec_cs8409 hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 2.121027] snd_hda_codec_cs8409 hdaudioC0D0: hp_outs=1 (0x24/0x0/0x0/0x0/0x0) [ 2.121028] snd_hda_codec_cs8409 hdaudioC0D0: mono: mono_out=0x0 [ 2.121029] snd_hda_codec_cs8409 hdaudioC0D0: inputs: [ 2.121031] snd_hda_codec_cs8409 hdaudioC0D0: Mic=0x34 - The output from "journalctl -k | grep -Ei "ALSA|HDA|sof[-]|HDMI|snd[_-]|sound|hda.codec|hda.intel"" is: Code: Select allDec 14 21:45:18 [machine name] kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002) Dec 14 21:45:18 [machine name] kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Dec 14 21:45:18 [machine name] kernel: snd_hda_codec_cs8409 hdaudioC0D0: autoconfig for CS8409: line_outs=1 (0x25/0x0/0x0/0x0/0x0) type:line Dec 14 21:45:18 [machine name] kernel: snd_hda_codec_cs8409 hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Dec 14 21:45:18 [machine name] kernel: snd_hda_codec_cs8409 hdaudioC0D0: hp_outs=1 (0x24/0x0/0x0/0x0/0x0) Dec 14 21:45:18 [machine name] kernel: snd_hda_codec_cs8409 hdaudioC0D0: mono: mono_out=0x0 Dec 14 21:45:18 [machine name] kernel: snd_hda_codec_cs8409 hdaudioC0D0: inputs: Dec 14 21:45:18 [machine name] kernel: snd_hda_codec_cs8409 hdaudioC0D0: Mic=0x34 Dec 14 21:45:18 [machine name] kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15 Dec 14 21:45:18 [machine name] kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16 Dec 14 21:45:18 [machine name] kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17 Dec 14 21:45:18 [machine name] kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18 - One last bit of information: When I installed Debian 12, I instructed the installer to use non-free firmware, to use non-free software, and to use the "targeted drivers" option. And, after the installer was finished, I installed XFCE myself at the command line by executing "apt-get -y install xfce4". I see that there is, in bookworm-backports, a package named "firmware-cirrus" (https://packages.debian.org/bookworm-ba ... are-cirrus). Would this package be of help to me? Also, I came across this project: https://github.com/egorenar/snd-hda-codec-cs8409.git If installing "firmware-cirrus" from bookworm-backports would not be of help, I'll probably give this project a try, using GNU Make. Thank you so much in advance for any help or insight anyone can provide! | Welcome to the forum! Output should be in code tags please. Done it for you this time. What options are available in the Configuration tab of pavucontrol? |
Hi, I'm struggling to understand a secure boot issue related to booting with a docking station plugged in. The laptop is a "HP ProBook 440 G9" and the docking station is the basic USB-C docking station "M96882-001". The installed version of Debian is Bookworm. The test cases that I've identified are: 1/ With the docking station unplugged, with standard boot Result: Boots as expected 2/ With the docking station plugged in, with standard boot Result: Fails to boot with: Code: Select allLoading Linux 6.10.6+bpo-amd64 ... error: shim_lock protocol not found Loading initial ramdisk ... error: you need to load the kernel first. Press any key to continue... 3/ With the docking station plugged in, and selecting to boot from a file in the BIOS boot menu, using the shimx64.efi file Result: Boots as expected Also boots as expected when Code: Select allefibootmgr is used to select what to boot on the next boot. I do not understand why plugging in the docking station alters boot process? The work around is to simply plug in the docking station after booting, but this risks me forgetting the issue and wasting a load of time after some time away from the laptop. Any suggestions on how to ensure the laptop will boot with and without the docking station would be gratefully received. | Hello, techno_worm wrote: 2025-01-05 22:04 The laptop is a "HP ProBook 440 G9" and the docking station is the basic USB-C docking station "M96882-001". The installed version of Debian is Bookworm. [..] 2/ With the docking station plugged in, with standard boot Result: Fails to boot with: Code: Select allLoading Linux 6.10.6+bpo-amd64 ... error: shim_lock protocol not found Loading initial ramdisk ... error: you need to load the kernel first. Press any key to continue... Is this your USB-C hub ? https://www.hp.com/us-en/shop/pdp/hp-universal-usb-c-multiport-hub-p-50h98aa-abl-1 Are there any devices connected to the USB-C hub ? |
In my case, the USB dongle RTL8153 shows up in lshw but appears to be a Wired Connection with its network "Cable Unplugged". Here is the lshw output, note it seems to use driver=r8152 which is cool, and it correctly id's in Network Manager as a RTL8153, but cannot be configured as WiFi: *-usb description: Generic USB device product: USB 10/100/1000 LAN vendor: Realtek physical id: 3 bus info: usb@3:2.3.3 version: 30.00 serial: 000001 capabilities: usb-3.20 configuration: driver=r8152 maxpower=288mA speed=5000Mbit/s Here is the section of 'ip a' that appears relevant, should be a 'wl' interface, but appears as 'en' ("DOWN" is bad, right?) 4: enx8cae4cee72f4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 8c:ae:4c:ee:72:f4 brd ff:ff:ff:ff:ff:ff I also have Linux Mint 22 (ubuntu deriv) and it configures fine as WiFi OOB. LMDE seems to have a slightly different problem, fails to install a "non-free-driver" but this is a total headscratcher. Must be hundreds, if not hundreds of thousands of these cheap rtl8152 descendants out on the street. Bookworm fresh install if that matters. TIA! | Hello, almoendaledeb wrote: 2024-11-16 06:21 I was incorrect, the adapter was in fact an 8812BU WLan, and installing https://github.com/morrownr/88x2bu-20210702 took care of the issue for 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 adding the name of the device, e.g.: [Solved] Wireless device 8812BU WLan not working Thanks. -- notes: 1) moved to the "Hardware" sub-forum. |
Hello, I have yet another issue with WiFi on Debian. For context, I got this new motherboard on my birthday, an MSI MAG Tomahawk Max WiFi. It worked fine until today, night, I even finished torrentingn something. Today I booted up my PC, see that wifi just "disappeared". I tried solving it with ChatGPT and it was a failure. The device is seen as "RealTek mt7921e", Kernel Version is 6.1.0-27-amd64 I need this fixed today, because tomorrow I'll have an online conference where screen sharing will be needed! Any help is welcomed! (Plugging in the Ethernet is not an option, at all) | Hello, What is the output of the following commands ? Code: Select alllspci -vnn -d ::0280 Is still there the pre-installed wireless module in the M.2 (Key-E) slot ? (see [1]) May you take a photo of its identification data ? Hope this helps. note: moved to "Hardware" sub-forum. --- [1] MAG Series Motherboard MAG Z790 TOMAHAWK MAX WIFI User Guide, page 18 |
A friend was running Lubuntu 18.04 on a Lenovo B570 laptop. It basically did work there in dual boot with Windows but it developed more and more issues. Most notably in the end the system just went dead each time it went to sleep. And on the next boot afterwards it was always necessary to run fsck in order to be able to boot the OS again. Originally I thought this might be due to broken sectors on the hard disk. Nevertheless, I decided to try a clean install with Debian Buster LXDE. Since Debian doesn't actually share the same issue I guess it was just something related to some mess in the old installation and not a hardware problem. I installed the Xfce engery management tools and could adjust the power saving options with that. Now the system doesn't vanish after going to sleep mode any more. Debian Buster LXDE behaves rather nicely in general. But unfortunately, I am so far unable to get all 2nd function key controls working. I can change the audio volume but most importantly I can't adapt the screen brightness. Since the battery isn't so great any more it is relevant if the screen runs with full brightness all the time. I have searched for anything related to it but didn't find any mentioning of this issue for GNU/Linux systems. Maybe nobody tried to run Debian/LXDE on the Lenovo B570 so far. But the problem seems to sit deeper because the GUI slider doesn't do anything either. I found out that there is at least one last bios update 44CN43WW.exe (current bios version on the device: 44CN42WW) available but it is only provided as Windows executable and I don't know how I would be able to use it for updating when not running Windows. Besides, the release notes don't mention any fix for something like my issue. But that doesn't probably mean much since Lenovo obviously wasn't planing to consider GNU/Linux for this device anyway. Please tell me if anyone reading this can provide a hint for how to enable screen brightness control on this device! | https://askubuntu.com/questions/57236/u ... ovo-laptop ? |
Hi, Advanced debian noob here (got the basics right but not much more i think). I can't get the wifi to work on a fresh debian 11. Code: Select allip a show shows the wifi interface wlp1s0 as DOWN but still has an ip address (192.168.1.121). Code: Select allip link set wlp1s0 up returns no error at all, but the interface still shows as DOWN. Weirdly enough, at login, I can see the dashboard WLAN indicator connect, show signal as green, for like a second, and then nothing. I have tried manually setting things up in /etc/network/interfaces.d and /etc/network/interfaces, although I don't think I have what it takes to figure it out on my own (yet). I'm positive I have commented out every modification I have made, to try again fresh. UPDATE : Code: Select allwpa_supplicant -B -D wext -i wlan0 -c /etc/wpa_supplicant.conf returned Successfully initialized wpa_supplicant ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWENCODEEXT]: Invalid argument and Code: Select allip a show showed wlp1s0 as UP. and Code: Select alliwconfig showed active connection to the right SSID. But pings still didn't get through and I couldn't access the web. Now I don't know what I did differently but it no longer works. For info : the network controller lists as Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter in lspci Laptop is Lenovo 14W. Any help appreciated ! | Do you have package firmware-atheros installed? |
Hey everyone, I’m having trouble getting my laptop’s internal speakers to work, but the audio works fine with headphones. Here’s the deal: I cloned the installation from an old laptop, and everything works perfectly except the audio. I’ve seen on some forums (even for other distros) that this seems to be a common issue, supposedly fixed in newer kernels. Anyway, I’m sharing the dmesg output and appreciate any help you can offer. Thanks in advance! Code: Select all5.993176] sof-audio-pci-intel-mtl 0000:00:1f.3: enabling device (0000 -> 0002) [ 5.993491] sof-audio-pci-intel-mtl 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 5.993557] sof-audio-pci-intel-mtl 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 6.000516] sof-audio-pci-intel-mtl 0000:00:1f.3: use msi interrupt mode [ 6.030845] sof-audio-pci-intel-mtl 0000:00:1f.3: hda codecs found, mask 5 [ 6.030849] sof-audio-pci-intel-mtl 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 6.030854] sof-audio-pci-intel-mtl 0000:00:1f.3: DMICs detected in NHLT tables: 2 [ 6.034018] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware paths/files for ipc type 1: [ 6.034021] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware file: intel/sof-ipc4/mtl/sof-mtl.ri [ 6.034023] sof-audio-pci-intel-mtl 0000:00:1f.3: Firmware lib path: intel/sof-ipc4-lib/mtl [ 6.034024] sof-audio-pci-intel-mtl 0000:00:1f.3: Topology file: intel/sof-ace-tplg/sof-hda-generic-2ch.tplg [ 6.034825] sof-audio-pci-intel-mtl 0000:00:1f.3: Loaded firmware library: ADSPFW, version: 2.11.1.1 [ 6.209243] sof-audio-pci-intel-mtl 0000:00:1f.3: Booted firmware version: 2.11.1.1 [ 6.220750] sof-audio-pci-intel-mtl 0000:00:1f.3: Topology: ABI 3:29:1 Kernel ABI 3:23:1 [ 6.342533] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC245: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 6.342539] snd_hda_codec_realtek ehdaudio0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 6.342541] snd_hda_codec_realtek ehdaudio0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 6.342543] snd_hda_codec_realtek ehdaudio0D0: mono: mono_out=0x0 [ 6.342545] snd_hda_codec_realtek ehdaudio0D0: inputs: [ 6.342546] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 | Alsa and pulsaudio which are the two I have used, do have settings app, amixer for alsa and pavucontrol for pulsaudio, from those you can select the output device. I think pipewire most propably has also, but I have not experince of it. |
Hi everyone.. A question about touchscreen support on my acer cb CB5-132T that otherwise is working awesome after i put debian 12 on it. Is it possible to get touchscreen working , or is it not available yet. Very best - Lindis Code: Select allSystem: Kernel: 6.1.0-28-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Cinnamon v: 5.6.8 tk: GTK v: 3.24.38 dm: GDM3 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Laptop System: GOOGLE product: Cyan v: 1.0 serial: <superuser required> Chassis: type: 9 serial: <superuser required> Mobo: GOOGLE model: Cyan v: 1.0 serial: <superuser required> UEFI: coreboot v: MrChromebox-2408.1 date: 09/14/2024 Battery: ID-1: BAT0 charge: 12.0 Wh (40.3%) condition: 29.8/40.5 Wh (73.5%) volts: 11.0 min: 11.6 model: SANYO AC15A3J serial: <filter> status: discharging CPU: Info: dual core model: Intel Celeron N3060 bits: 64 type: MCP arch: Airmont rev: 4 cache: L1: 112 KiB L2: 2 MiB Speed (MHz): avg: 2480 min/max: 480/2480 cores: 1: 2480 2: 2480 bogomips: 6400 Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics driver: i915 v: kernel arch: Gen-8 ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:22b1 Device-2: Chicony HD WebCam type: USB driver: uvcvideo bus-ID: 1-4:2 chip-ID: 04f2:b490 Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 Monitor-1: eDP-1 model: AU Optronics 0x405c res: 1366x768 dpi: 136 diag: 294mm (11.6") API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 400 (BSW) direct-render: Yes Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:2284 API: ALSA v: k6.1.0-28-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin Network: Device-1: Intel Wireless 7265 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:095a IF: wlp2s0 state: up mac: <filter> Bluetooth: Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-5:3 chip-ID: 8087:0a2a Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.2 sub-v: 1000 Drives: Local Storage: total: 58.84 GiB used: 26.47 GiB (45.0%) ID-1: /dev/mmcblk0 vendor: HP model: DF4032 size: 29.12 GiB serial: <filter> ID-2: /dev/mmcblk1 vendor: Silicon Motion model: SM32G size: 29.72 GiB serial: <filter> Partition: ID-1: / size: 26.58 GiB used: 17.75 GiB (66.8%) fs: ext4 dev: /dev/dm-0 mapped: acer--mini--vg-root ID-2: /boot size: 455.1 MiB used: 149.3 MiB (32.8%) fs: ext2 dev: /dev/mmcblk0p2 ID-3: /boot/efi size: 511 MiB used: 5.8 MiB (1.1%) fs: vfat dev: /dev/mmcblk0p1 Swap: ID-1: swap-1 type: partition size: 976 MiB used: 183.5 MiB (18.8%) priority: -2 dev: /dev/dm-1 mapped: acer--mini--vg-swap_1 Sensors: System Temperatures: cpu: 50.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: Packages: 2015 pm: dpkg pkgs: 1987 pm: flatpak pkgs: 20 pm: snap pkgs: 8 Active apt repos in: /etc/apt/sources.list 1: deb http: //deb.debian.org/debian bookworm main contrib non-free non-free-firmware 2: deb http: //deb.debian.org/debian-security/ bookworm-security main contrib non-free non-free-firmware 3: deb http: //deb.debian.org/debian bookworm-updates main contrib non-free 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/teamviewer.list 1: deb [signed-by=/usr/share/keyrings/teamviewer-keyring.gpg] https: //linux.teamviewer.com/deb stable main Info: Processes: 212 Uptime: 3h 16m Memory: 3.77 GiB used: 2.4 GiB (63.8%) Init: systemd v: 252 target: graphical (5) default: graphical Compilers: gcc: 12.2.0 alt: 12 Client: Cinnamon v: 5.6.8 inxi: 3.3.26 | Hello! Google a bit, and responses showed that in Gnome and KDE it should work out of the box. |
Good day Everyone! I installed Debian 12 Bookworm (Kernel 6.1.0-28-amd64) recently on my laptop, it didn't had the drivers for my WIFI board so i had to install the latest rtw88 drivers from lwfinger on github to make the wi-fi work, but for some reason when i tried using "blueman-adapters" to see if i could use bluetooth, this message appeared on terminal: Code: Select all$ blueman-adapters Gtk-Message: 14:30:46.447: Failed to load module "xapp-gtk3-module" blueman-adapters 14.30.46 ERROR Adapter:63 __init__ : No adapter(s) found Code: Select all$ lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 288f:9863 Sunplus IT Co PC Camera Bus 001 Device 003: ID 258a:8080 SINO WEALTH USB KEYBOARD Bus 001 Device 002: ID 275d:0ba6 USB OPTICAL MOUSE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Code: Select all$ lspci 00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 36) 00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 36) 00:03.0 Multimedia controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit (rev 36) 00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 36) 00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 36) 00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 36) 00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 36) Code: Select all$ sudo journalctl | grep "bluetooth" Dec 29 14:45:51 ayanami NetworkManager[590]: <info> [1735490751.4856] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-bluetooth.so) Dec 29 14:45:58 ayanami systemd[1]: Starting bluetooth.service - Bluetooth service... Dec 29 14:45:58 ayanami (uetoothd)[820]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555) Dec 29 14:45:58 ayanami bluetoothd[820]: Bluetooth daemon 5.66 Dec 29 14:45:58 ayanami systemd[1]: Started bluetooth.service - Bluetooth service. Dec 29 14:45:58 ayanami bluetoothd[820]: Starting SDP server Dec 29 14:45:59 ayanami bluetoothd[820]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Dec 29 14:45:59 ayanami bluetoothd[820]: src/plugin.c:plugin_init() Failed to init vcp plugin Dec 29 14:45:59 ayanami bluetoothd[820]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Dec 29 14:45:59 ayanami bluetoothd[820]: src/plugin.c:plugin_init() Failed to init mcp plugin Dec 29 14:45:59 ayanami bluetoothd[820]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Dec 29 14:45:59 ayanami bluetoothd[820]: src/plugin.c:plugin_init() Failed to init bap plugin Dec 29 14:45:59 ayanami bluetoothd[820]: Bluetooth management interface 1.22 initialized Code: Select all$ sudo journalctl | grep "Bluetooth" Dec 29 14:45:47 ayanami kernel: Bluetooth: Core ver 2.22 Dec 29 14:45:47 ayanami kernel: Bluetooth: HCI device and connection manager initialized Dec 29 14:45:47 ayanami kernel: Bluetooth: HCI socket layer initialized Dec 29 14:45:47 ayanami kernel: Bluetooth: L2CAP socket layer initialized Dec 29 14:45:47 ayanami kernel: Bluetooth: SCO socket layer initialized Dec 29 14:45:47 ayanami kernel: Bluetooth: HCI UART driver ver 2.2.3634cd9.20220330-143427 Dec 29 14:45:47 ayanami kernel: Bluetooth: HCI H4 protocol initialized Dec 29 14:45:47 ayanami kernel: Bluetooth: HCI Realtek H5 protocol initialized Dec 29 14:45:49 ayanami systemd[1]: Starting blueman-mechanism.service - Bluetooth management mechanism... Dec 29 14:45:52 ayanami systemd[1]: Started blueman-mechanism.service - Bluetooth management mechanism. Dec 29 14:45:58 ayanami systemd[1]: Starting bluetooth.service - Bluetooth service... Dec 29 14:45:58 ayanami bluetoothd[820]: Bluetooth daemon 5.66 Dec 29 14:45:58 ayanami systemd[1]: Started bluetooth.service - Bluetooth service. Dec 29 14:45:59 ayanami kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Dec 29 14:45:59 ayanami kernel: Bluetooth: BNEP filters: protocol multicast Dec 29 14:45:59 ayanami kernel: Bluetooth: BNEP socket layer initialized Dec 29 14:45:59 ayanami bluetoothd[820]: Bluetooth management interface 1.22 initialized Is there any additional driver i need to install? | Welcome! Perhaps you don't need that github rw88. Code: Select allarto@dell:~$ apt-file search rtw88 firmware-realtek: /lib/firmware/rtw88/rtw8723d_fw.bin firmware-realtek: /lib/firmware/rtw88/rtw8821c_fw.bin firmware-realtek: /lib/firmware/rtw88/rtw8822b_fw.bin firmware-realtek: /lib/firmware/rtw88/rtw8822c_fw.bin firmware-realtek: /lib/firmware/rtw88/rtw8822c_wow_fw.bin firmware-realtek: /lib/firmware/rtw89/rtw8852a_fw.bin firmware-realtek: /lib/firmware/rtw89/rtw8852b_fw.bin firmware-realtek: /lib/firmware/rtw89/rtw8852c_fw.bin linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-25-amd64: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-25-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-25-amd64-unsigned: /lib/modules/6.1.0-25-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-25-rt-amd64: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-25-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-25-rt-amd64-unsigned: /lib/modules/6.1.0-25-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-27-amd64: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-27-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-27-amd64-unsigned: /lib/modules/6.1.0-27-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-27-rt-amd64: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-27-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-27-rt-amd64-unsigned: /lib/modules/6.1.0-27-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-28-amd64: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-28-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-28-amd64-unsigned: /lib/modules/6.1.0-28-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-28-rt-amd64: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-28-rt-amd64-dbg: /usr/lib/debug/lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723de.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821c.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8821ce.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822b.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822be.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822c.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8822ce.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_core.ko linux-image-6.1.0-28-rt-amd64-unsigned: /lib/modules/6.1.0-28-rt-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_pci.ko arto@dell:~$ You could also install inxi, and run in terminal Code: Select allrto@dell:~$ inxi -E Bluetooth: Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) type: USB driver: btusb Report: hciconfig ID: hci0 state: up address: 00:19:86:00:21:57 bt-v: 1.2 arto@dell:~$ |
I have an Asus Vivobook X1704VA laptop: my keyboard locks up randomly. At first I thought the problem might be with the xserver-xorg-input-libinput driver. But a few days ago, I found a topic on this forum describing a problem with an Asus Vivobook X1704VAP that looks a lot like mine: viewtopic.php?p=808370.. It pointed to bug #1078696: https://lists.debian.org/debian-kernel/ ... 00202.html. The proposed solution is as follows: Add the X1704VAP to the irq1_level_low_skip_override[] quirk table to fix this. I checked the change log for kernel 6.1.0.27 and I found this: Code: Select all$ apt changelog linux-image-6.1.0-27-amd64 | grep -i -A 1 'vivobook X1704' - ACPI: resource: Add Asus Vivobook X1704VAP to irq1_level_low_skip_override[] (Closes: #1078696) Apparently, for an Asus Vivobook X1704VAP, this problem was solved as of kernel 6.1.0.27, But nothing on my X1704VA laptop. Nevertheless, I thought this problem could be solved for mine too, so I deleted the i8042.dumbkbd=1 option, which seemed to be effective. But this morning I had exactly the same problem: my keyboard froze again. After rebooting, I checked a log that seems relevant (I'm not very sure): Code: Select all/var/log# less Xorg.0.log.old | grep keyboard | tail -n 5 [ 9.195] (**) Logitech Wireless Mouse: Applying InputClass "libinput keyboard catchall" [ 9.196] (II) event15 - Logitech Wireless Mouse: device is a keyboard [ 9.237] (II) event15 - Logitech Wireless Mouse: device is a keyboard [ 9.238] (**) Logitech Wireless Mouse: Applying InputClass "libinput keyboard catchall" [ 39105.554] (II) event0 - AT Translated Set 2 keyboard: device removed How do I add my X1704VA laptop to the irq1_level_low_skip_override[] table? I don't even know what a “quirk table” is and where to find it. If I have to recompile the kernel, I give up right away. Or should I report a bug for my laptop? | Hello, mazda1 wrote: 2024-12-02 10:27 I have an Asus Vivobook X1704VA laptop: my keyboard locks up randomly. At first I thought the problem might be with the xserver-xorg-input-libinput driver. But a few days ago, I found a topic on this forum describing a problem with an Asus Vivobook X1704VAP that looks a lot like mine: viewtopic.php?p=808370.. It pointed to bug #1078696: https://lists.debian.org/debian-kernel/ ... 00202.html. [..] You are reporting a "random keyboard lock", while the OP of the referenced discussion reported his/her keyboard was not working at all. So, yours is probably a different issue. It may be a firmware/hardware malfunction. You may analyze or share system logs for other clues. |
I have been trying to set up wifi for my new pc with the Debian 12 OS. I had learned that the drivers were not installed so I went on a search for them. I ended up following the github rtw89 instructions from lwfinger. Now, to my knowledge everything is downloaded yet # inxi -N reports no wifi driver. Only thing I can think of is that I blacklisted the wrong things while following the github instructions. === Network: Device-1: Realtek RTL8852CE PCIe 802.11ax Wireless Network driver: N/A Device-2: Realtek RTL8125 2.5GbE driver: r8169 === # apt search realtek === Sorting... Done Full Text Search... Done firmware-realtek/stable,now 20230210-5 all [installed] Binary firmware for Realtek wired/wifi/BT adapters firmware-realtek-rtl8723cs-bt/stable,now 20181104-2 all [installed] Bluetooth firmware for Realtek RTL8723CS flashrom/stable 1.3.0-2.1 amd64 Identify, read, write, erase, and verify BIOS/ROM/flash chips librtlsdr-dev/stable 0.6.0-4 amd64 Software defined radio receiver for Realtek RTL2832U (development) librtlsdr0/stable 0.6.0-4 amd64 Software defined radio receiver for Realtek RTL2832U (library) rtl-sdr/stable 0.6.0-4 amd64 Software defined radio receiver for Realtek RTL2832U (tools) rtw89-dkms/now 1.0.2-3 all [installed,local] dkms source for the Realtek rtw89 driver soapysdr-module-rtlsdr/stable 0.3.3-1 amd64 RTL-SDR device support for SoapySDR (default version) soapysdr0.8-module-rtlsdr/stable 0.3.3-1 amd64 RTL-SDR device support for SoapySDR === installed headers: === linux-headers-6.1.0-28-amd64/stable-security,now 6.1.119-1 amd64 [installed] Header files for Linux 6.1.0-28-amd64 linux-headers-6.1.0-28-common/stable-security,now 6.1.119-1 all [installed,automatic] Common header files for Linux 6.1.0-28 linux-headers-amd64/stable-security,now 6.1.119-1 amd64 [installed] Header files for Linux amd64 configuration (meta-package) === # uname -r === 6.1.0-28-amd64 === # rfkill list === 0: hci0: Bluetooth Soft blocked: no Hard blocked: no === # apt search rtw89 === Sorting... Done Full Text Search... Done firmware-realtek/stable,now 20230210-5 all [installed] Binary firmware for Realtek wired/wifi/BT adapters rtw89-dkms/now 1.0.2-3 all [installed,local] dkms source for the Realtek rtw89 driver === ~# ls === rtw89 rtw89_1.0.2-3_amd64.changes rtw89_1.0.2-3.dsc rtw89-dkms_1.0.2-3_all.deb rtw89_1.0.2-3_amd64.buildinfo rtw89_1.0.2-3.debian.tar.xz rtw89_1.0.2.orig.tar.xz === root:/etc/modprobe.d# ls === amd64-microcode-blacklist.conf blacklist-rtw89.conf dkms.conf === Both no output below # dmesg | grep rtw === === # lsmod | grep rtw89 === === | Hello, Are you booting with secure boot enabled ? What is the output of the following commands (the log is stored in the log.txt file)? Code: Select allscript log.txt sudo journalctl -b --no-pager -p err..warning exit If you wish, you can report logs in one of 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 attach the logs to a follow-up forum message as a compressed zip or gz file paste the logs into the body of a follow-up message between code tags (if they fit the size of a forum message) Hope this helps. -- note: 1) please, use code tags to include commands and/or their logs in the body of a message. Fixed it for you this time. 2) discussion moved to "Hardware" sub-forum. |
Hi all. I've been pulling my hair out trying to get a networked printer to work with a laptop running Debian 12. I was able to print from this same laptop when it was running Lubuntu, from a different laptop running Mint, and from a Windows machine. The printer is a Samsung C410. My desktop environment is LXQT, which installs with "system-config-printer". Steps I took to set the printer up: Prior to me doing anything, the printer automatically shows up in Print Settings (system-config-printer), but is not properly set up (URI is "file:///dev/null", make and model is "Local Raw Printer"). Install printer driver supplied by the manufacturer: https://ftp.hp.com/pub/softlib/software ... .17.tar.gz. Ran a script named "install-printer.sh". The script prompts me to automatically set up the firewall (giving no information as to what exactly it does), and ostensibly completes successfully. Edit existing printer properties: choose the correct installed driver (Samsung C410 Series), and set device URI (socket:/192.168.1.82:9100) When I try to print a test page, I get a dialog box that says "Error: There was a problem processing document 'Test Page' (job 1)." with a handy "Diagnose" button which, after a few clicks, produces the attached text file. Additionally, I tried printing a test page from another Debian 12 machine running KDE Plasma; this machine would have me believe the test page prints successfully, but nothing comes out of the printer. Random probably-useless bit of info (because I'm grasping at straws): when installing Debian on the two Debian machines I created a root account (because I didn't know I didn't have to enter a password for root). | Somebody else tearing their hair out - but found a solution. viewtopic.php?p=806288#p806288 |
Hello, I have debian installed on HP t620. Recently I've replaced the external SSD drive by WDC WD20 EFZX-68AWUN0 mount on sdb1 with encryption /dev/mapper/luks-dbe75eaf-bafd-49b6-b15f-d83844dc6624 On that disk I have NAS folder where is loaded backup from another machine. When disk is loaded with lot of data (21:27 in log below) then I start to have issue with it. Firstly I was thinking that it was due to high temperature, but in reality temperature of external drive is between 40 and 50 degrees. Here is log I have: Code: Select all20:31 Device: /dev/sdb [SAT], no ATA CHECK POWER STATUS support, ignoring -n Directive smartd 20:31 kvm: support for 'kvm_amd' disabled by bios 21:27 xhci_hcd 0000:00:10.0: xHCI host controller not responding, assume dead 21:27 xhci_hcd 0000:00:10.0: HC died; cleaning up 21:27 I/O error, dev sdb, sector 753811912 op 0x1:(WRITE) flags 0x800 phys_seg 12 prio class 2 ........ 21:27 Buffer I/O error on device dm-0, logical block 94222137 21:27 EXT4-fs (dm-0): I/O error while writing superblock 21:27 Failed unmounting NAS.mount - /NAS. 21:27 Device luks-dbe75eaf-bafd-49b6-b15f-d83844dc6624 is still in use. 21:27 Failed to deactivate: Device or resource busy 21:27 EXT4-fs error (device dm-0): ext4_journal_check_start:83: comm smbd: Detected aborted journal I hope this issue can be resolved with forum help. | Hello, Welcome to the forum. It is probably an hardware issue of your hard disk. You may check the heath status of your disk using smartctl command. Please rename the subject of the first topic to make it more informative, as: “External hard disk disconnects under load with a HP t620 running Debian 12” |
hello, Since my wifi doesn't work with kernel 1.0.26, I booted my laptop with kernel 1.0.25. I thought that maybe dkms-1.0.26 couldn't build install the driver for my Tp-Link AC600 adapter, I was therefore surprised to read the following Code: Select all~# uname -r 6.1.0-25-amd64 ~# dkms status rtl8821cu/5.12.0.4, 6.1.0-26-amd64, x86_64: installed 1- how, when I'm using kernel 1.0.25, can I get information about kernel 1.0.26? 2- is there anything I can do to fix this wifi problem, or do I have to wait for an update? PS1: 2 weeks ago, I tried kernel 1.10: wifi was OK. ..... For some reason, it no longer works. (2024/10/18) PS2: wifi is not blocked and there's nothing special about it in boot log | Hello, mazda1 wrote: 2024-10-12 09:38 Since my wifi doesn't work with kernel 1.0.26, I booted my laptop with kernel 1.0.25. I thought that maybe dkms-1.0.26 couldn't build install the driver for my Tp-Link AC600 adapter, You are probably referring to: 6.1.0-25 debian kernel package (currently shipped with Debian stable repositories) 6.1.0-26 debian kernel package (currently shipped with Debian stable-security repositories) mazda1 wrote: 2024-10-12 09:38 I was therefore surprised to read the following Code: Select all~# uname -r 6.1.0-25-amd64 ~# dkms status rtl8821cu/5.12.0.4, 6.1.0-26-amd64, x86_64: installed 1- how, when I'm using kernel 1.0.25, can I get information about kernel 1.0.26? According to your output, you are using the rtl8821cu/5.12.0.4 out-of-the-tree kernel module (which you probably downloaded from the Internet earlier), which was built using Dynamic Kernel Module Support (DKMS) for Debian kernel package version 6.1.0-26-amd64. The DKMS attempts to rebuild its registered kernel modules each time you upgrade the kernel or manually request a rebuild. Each kernel has its own binary kernel modules in a separated directory, usually called /lib/modules/ . So I have to assume that you previously installed the 6.1.0-26-amd64 Debian kernel package, and that the DKMS built the rtl8821cu/5.12.0.4 kernel module. Note that the version of the kernel module (/5.12.0.4) refers to a previous version of the kernel (it was probably originally built for the for 5.12.0.4 kernel version). mazda1 wrote: 2024-10-12 09:38 is there anything I can do to fix this wifi problem, or do I have to wait for an update? PS2: wifi is not blocked and there's nothing special about it in boot log You can try building the kernel module with your preferred running kernel version using the following commands (I assume you are using the amd64 architecture): Code: Select allsudo apt install linux-headers-amd64 sudo dkms status sudo dkms build rtl8821cu/5.12.0.4 mazda1 wrote: 2024-10-12 09:38 PS2: wifi is not blocked and there's nothing special about it in boot log Check if the rkfill command can help you: RFKILL(8) - System Administration Hope this helps. note: please add the name of the kernel module in the subject of the first post; e.g.: "Wifi no longer works after kernel update with Tp-Link AC600 adapter (rtl8821cu kernel module)" |
Hello Debian Bookworm Kernel: 6.1.0-25-amd64 I disabled the bluetooth on my machine in an attempt to disconnect a some troublesome earphones and then could not enable it again. following are the steps I took. first I checked the status of the bluetooth service. Code: Select allmadzi@Network-Rage:~$ sudo systemctl status bluetooth ○ bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: inactive (dead) Docs: man:bluetoothd(8) Oct 21 23:48:38 Network-Rage systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth) Oct 21 23:51:53 Network-Rage systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth) I checked /sys/class and the bluetooth directory was not present. after some digging around I ran Code: Select allmadzi@Network-Rage:/sys/class$ sudo modprobe bluetooth madzi@Network-Rage:/sys/class$ sudo systemctl restart bluetooth madzi@Network-Rage:/sys/class$ sudo systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; preset: enabled) Active: active (running) since Tue 2024-10-22 04:42:11 CAT; 4s ago Docs: man:bluetoothd(8) Main PID: 7899 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38352) Memory: 2.2M CPU: 26ms CGroup: /system.slice/bluetooth.service └─7899 /usr/libexec/bluetooth/bluetoothd Oct 22 04:42:11 Network-Rage bluetoothd[7899]: Bluetooth daemon 5.66 Oct 22 04:42:11 Network-Rage systemd[1]: Started bluetooth.service - Bluetooth service. Oct 22 04:42:11 Network-Rage bluetoothd[7899]: Starting SDP server Oct 22 04:42:11 Network-Rage bluetoothd[7899]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled Oct 22 04:42:11 Network-Rage bluetoothd[7899]: src/plugin.c:plugin_init() Failed to init vcp plugin Oct 22 04:42:11 Network-Rage bluetoothd[7899]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled Oct 22 04:42:11 Network-Rage bluetoothd[7899]: src/plugin.c:plugin_init() Failed to init mcp plugin Oct 22 04:42:11 Network-Rage bluetoothd[7899]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled Oct 22 04:42:11 Network-Rage bluetoothd[7899]: src/plugin.c:plugin_init() Failed to init bap plugin Oct 22 04:42:11 Network-Rage bluetoothd[7899]: Bluetooth management interface 1.22 initialized I do not know if this will help any further but here is the output of some other command. Code: Select allmadzi@Network-Rage:/sys/class$ sudo bluetoothctl Agent registered Code: Select allmadzi@Network-Rage:/sys/class$ sudo rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Code: Select allmadzi@Network-Rage:/sys/class$ bluetoothctl Agent registered [bluetooth]# power on No default controller available [bluetooth]# Any help would be greatly appreciated. | Hi I found a post that suggested a system shutdown instead of restarting and voilà!! Bluetooth controller found and enable button worked. |
Howdy I'm having a problem getting reliable connection with my eth0 LAN interface (connected to a switch). When performing pings to the switch, there's about 50% packet loss, and ifconfig shows a large number of RX errors (frame errors) But for some reason, I can often "fix it" just by issuing sudo ethtool -r eth0 Once it starts working, it will continuously give 0% packet loss, no RX errors at all (ie have tested for at least an hour of continuous pinging) However if it's working reliably and I issue sudo ethtool -r eth0 again, it will often go back to the RX errors again. It never swaps spontaneously between "reliable" and "RX errors", it only happens when I perform sudo ethtool -r eth0, or when I unplug the ethernet cable and then plug it in again It doesn't seem to make any difference whether I turn autoneg on or off. (sudo ethtool -s eth0 autoneg off). The duplex and speed shown by the interface are always correct Any clues on what's happening, or how I could troubleshoot it further? Cheers Richard Some extra details Raspbian GNU/Linux 12 (Bookworm) eth0 is smsc95xx version 6.6.51+rpt-rpi-v6 | Hello, TheGreyGhost wrote: 2024-10-23 00:14 Hi It's an old consumer-grade router (unmanaged) which I'm using as an L2 switch only. The logs don't show any info on the ports, unfortunately. Swapping cables didn't help. After thinking about it a bit more, I decided to borrow a switch (TPlink TL-SG2008, Small Office Home Office L2+ switch) and test that. Using the TL-SG2008 it works perfectly, I've been trying it ten times now over the last few hours and the problem hasn't recurred so I guess it's time to retire the old router. It doesn't seem to cause any problems with the other devices (windows PCs) connected to it but obviously it doesn't play properly with the NIC on the Raspberry Pi for some reason, and it's well past its obsolescence date now. Thanks for the suggestion! Cheers Richard I'm happy you sorted it out. Please mark the discussion as solved adding the tag [Solved] at the beginning of the subject of the first post. Thanks. -- note: moved to "Hardware" sub-forum. |
I am a linux newbie trying to get a ps4 dual shock controller to work on debian 12. It is detected and works on windows 11. here is the output from lsusb- Code: Select allBus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 054c:05c4 Sony Corp. DualShock 4 [CUH-ZCT1x] Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1872 ASUSTek Computer, Inc. AURA LED Controller Bus 001 Device 003: ID 0b05:185c ASUSTek Computer, Inc. Bluetooth Radio Bus 001 Device 002: ID c0f4:06f5 Usb KeyBoard Usb KeyBoard Bus 001 Device 005: ID 046d:c534 Logitech, Inc. Nano Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub here is the output from dmesg -L -w Code: Select all[ 1846.705620] usb 3-2: new full-speed USB device number 4 using xhci_hcd [ 1846.970345] usb 3-2: New USB device found, idVendor=054c, idProduct=05c4, bcdDevice= 1.00 [ 1846.970360] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1846.970367] usb 3-2: Product: Wireless controller [ 1846.970372] usb 3-2: Manufacturer: Sony Computer Entertainment [ 1852.186057] sony 0003:054C:05C4.0009: failed to retrieve feature report 0x81 with the DualShock 4 MAC address [ 1852.186250] sony 0003:054C:05C4.0009: hidraw6: USB HID v81.00 Gamepad [Sony Computer Entertainment Wireless controller] on usb-0000:06:00.0-2/input0 [ 1852.186264] sony 0003:054C:05C4.0009: failed to claim input Any help would be greatly appreciated. | Hello, Dzimbahwe wrote: 2024-10-04 13:05 I am a linux newbie trying to get a ps4 dual shock controller to work on debian 12. here is the output from lsusb- Code: Select allBus 003 Device 004: ID 054c:05c4 Sony Corp. DualShock 4 [CUH-ZCT1x] here is the output from dmesg -L -w Code: Select all[ 1846.705620] usb 3-2: new full-speed USB device number 4 using xhci_hcd [ 1846.970345] usb 3-2: New USB device found, idVendor=054c, idProduct=05c4, bcdDevice= 1.00 [ 1846.970360] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1846.970367] usb 3-2: Product: Wireless controller [ 1846.970372] usb 3-2: Manufacturer: Sony Computer Entertainment [ 1852.186057] sony 0003:054C:05C4.0009: failed to retrieve feature report 0x81 with the DualShock 4 MAC address [ 1852.186250] sony 0003:054C:05C4.0009: hidraw6: USB HID v81.00 Gamepad [Sony Computer Entertainment Wireless controller] on usb-0000:06:00.0-2/input0 [ 1852.186264] sony 0003:054C:05C4.0009: failed to claim input Any help would be greatly appreciated. It seems that your device Sony Corp. DualShock 4 [CUH-ZCT1x] (ID 054c:05c4) is detected, but it is not configured. Searching the internet, the following discussion was found: Multimedia and Games » [Understood/fixed] Can't get input from DualShock 4 Controller It seems that a kernel patch can help: Code: Select all--- a/drivers/hid/hid-sony.c +++ b/drivers/hid/hid-sony.c @@ -491,6 +491,7 @@ struct motion_output_report_02 { #define DS4_FEATURE_REPORT_0x02_SIZE 37 #define DS4_FEATURE_REPORT_0x05_SIZE 41 +#define DS4_FEATURE_REPORT_0x12_SIZE 16 #define DS4_FEATURE_REPORT_0x81_SIZE 7 #define DS4_FEATURE_REPORT_0xA3_SIZE 49 #define DS4_INPUT_REPORT_0x11_SIZE 78 @@ -2593,6 +2594,53 @@ static int sony_get_bt_devaddr(struct sony_sc *sc) return 0; } +static int sony_get_usb_ds4_devaddr(struct sony_sc *sc) +{ + u8 *buf = NULL; + int ret; + + buf = kmalloc(max(DS4_FEATURE_REPORT_0x12_SIZE, DS4_FEATURE_REPORT_0x81_SIZE), GFP_KERNEL); + if (!buf) + return -ENOMEM; + + /* + * The MAC address of a DS4 controller connected via USB can be + * retrieved with feature report 0x81. The address begins at + * offset 1. + */ + ret = hid_hw_raw_request(sc->hdev, 0x81, buf, + DS4_FEATURE_REPORT_0x81_SIZE, HID_FEATURE_REPORT, + HID_REQ_GET_REPORT); + if (ret == DS4_FEATURE_REPORT_0x81_SIZE) { + memcpy(sc->mac_address, &buf[1], sizeof(sc->mac_address)); + goto out_free; + } + dbg_hid("%s: hid_hw_raw_request(..., 0x81, ...) returned %d ", __func__, ret); + + /* + * Some variants do not implement feature report 0x81 at all. + * Fortunately, feature report 0x12 also contains the MAC address of + * a controller. + */ + ret = hid_hw_raw_request(sc->hdev, 0x12, buf, + DS4_FEATURE_REPORT_0x12_SIZE, HID_FEATURE_REPORT, + HID_REQ_GET_REPORT); + if (ret == DS4_FEATURE_REPORT_0x12_SIZE) { + memcpy(sc->mac_address, &buf[1], sizeof(sc->mac_address)); + goto out_free; + } + dbg_hid("%s: hid_hw_raw_request(..., 0x12, ...) returned %d ", __func__, ret); + + hid_err(sc->hdev, "failed to retrieve feature reports 0x81 and 0x12 with the DualShock 4 MAC address "); + ret = ret < 0 ? ret : -EINVAL; + +out_free: + + kfree(buf); + + return ret; +} + static int sony_check_add(struct sony_sc *sc) { u8 *buf = NULL; @@ -2613,26 +2661,9 @@ static int sony_check_add(struct sony_sc *sc) return 0; } } else if (sc->quirks & (DUALSHOCK4_CONTROLLER_USB | DUALSHOCK4_DONGLE)) { - buf = kmalloc(DS4_FEATURE_REPORT_0x81_SIZE, GFP_KERNEL); - if (!buf) - return -ENOMEM; - - /* - * The MAC address of a DS4 controller connected via USB can be - * retrieved with feature report 0x81. The address begins at - * offset 1. - */ - ret = hid_hw_raw_request(sc->hdev, 0x81, buf, - DS4_FEATURE_REPORT_0x81_SIZE, HID_FEATURE_REPORT, - HID_REQ_GET_REPORT); - - if (ret != DS4_FEATURE_REPORT_0x81_SIZE) { - hid_err(sc->hdev, "failed to retrieve feature report 0x81 with the DualShock 4 MAC address "); - ret = ret < 0 ? ret : -EINVAL; - goto out_free; - } - - memcpy(sc->mac_address, &buf[1], sizeof(sc->mac_address)); + ret = sony_get_usb_ds4_devaddr(sc); + if (ret < 0) + return ret; snprintf(sc->hdev->uniq, sizeof(sc->hdev->uniq), "%pMR", sc->mac_address); @@ -2670,6 +2701,7 @@ static int sony_check_add(struct sony_sc *sc) return 0; } + dbg_hid("%s: retrieved MAC address: %s ", __func__, sc->hdev->uniq); ret = sony_check_add_dev_list(sc); out_free: It is also reported that kernel >= 6.2 should fix the problem. Therefore, you may consider installing a newer kernel version from the Debian Backports Repositories; you can find instructions here: Debian Backports Hope this helps. Please let me know. -- note: please, use code tags to include commands and/or their logs in the body of a message. I fixed the previous message for you. |
I do have an Acer Spin 1 here. It is a neat little device that runs the Debian 12.7.0 Xfce Live system perfectly fine after I set a UEFI password, disabled secure boot and changed the boot order to first look for a system on my USB stick. Even the installation of the system on the 125 GB emmc disk /dev/mmcblk1p1 works flawlessly until it is time to create the GRUB menu. It fails with the message that it can't find the UEFI. So I need to finish the installation without creating a GRUB menu. In principle this doesn't sound like a big deal since it should be rather easy to generate the GRUB menu afterwards. Unfortunately, at the next boot the system disk can't be found in the UEFI any longer. I can still mount the disk from the live system and see that all the system files are where they are supposed to be. I found some guides I tried to install GRUB by hand but fail at an embarrassing point: I can't chroot into the disk with Debian installed because I so far couldn't figure out where to find bash. The GRUB configuration file I also can only find for the live system. It doesn't seem to be present on the system disk. I figure this isn't entirely surprising since I after all couldn't install GRUB during the installation routine. reddit guide installing ubuntu on an acer aspire es15 gcore.com: how to install grub bootloader in linux fosslinux.com: a complete guide to installing grub bootloader on linux unix.stackexchange.com: grub install command not found Here is some hopefully relevant command line output from my attempts to install GRUB using the live system: Code: Select alluser@debian:~$ sudo apt install grub-efi Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: libc6-i386 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: efibootmgr grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common mokutil shim-helpers-amd64-signed shim-signed shim-signed-common shim-unsigned The following packages will be REMOVED: grub-legacy The following NEW packages will be installed: efibootmgr grub-efi grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common mokutil shim-helpers-amd64-signed shim-signed shim-signed-common shim-unsigned 0 upgraded, 11 newly installed, 1 to remove and 0 not upgraded. Need to get 4,634 kB of archives. After this operation, 39.4 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://deb.debian.org/debian bookworm/main amd64 efibootmgr amd64 17-2 [27.6 kB] Get:2 http://deb.debian.org/debian bookworm/main amd64 grub2-common amd64 2.06-13+deb12u1 [614 kB] Get:3 http://deb.debian.org/debian bookworm/main amd64 grub-efi-amd64-bin amd64 2.06-13+deb12u1 [1,574 kB] Get:4 http://deb.debian.org/debian bookworm/main amd64 grub-efi-amd64 amd64 2.06-13+deb12u1 [45.7 kB] Get:5 http://deb.debian.org/debian bookworm/main amd64 grub-efi amd64 2.06-13+deb12u1 [2,388 B] Get:6 http://deb.debian.org/debian bookworm/main amd64 grub-efi-amd64-signed amd64 1+2.06+13+deb12u1 [1,259 kB] Get:7 http://deb.debian.org/debian bookworm/main amd64 mokutil amd64 0.6.0-2 [26.9 kB] Get:8 http://deb.debian.org/debian bookworm/main amd64 shim-unsigned amd64 15.8-1~deb12u1 [440 kB] Get:9 http://deb.debian.org/debian bookworm/main amd64 shim-helpers-amd64-signed amd64 1+15.8+1~deb12u1 [301 kB] Get:10 http://deb.debian.org/debian bookworm/main amd64 shim-signed-common all 1.44~1+deb12u1+15.8-1~deb12u1 [13.6 kB] Get:11 http://deb.debian.org/debian bookworm/main amd64 shim-signed amd64 1.44~1+deb12u1+15.8-1~deb12u1 [329 kB] Fetched 4,634 kB in 1s (3,533 kB/s) Preconfiguring packages ... (Reading database ... 245298 files and directories currently installed.) Removing grub-legacy (0.97-80) ... Selecting previously unselected package efibootmgr. (Reading database ... 245253 files and directories currently installed.) Preparing to unpack .../00-efibootmgr_17-2_amd64.deb ... Unpacking efibootmgr (17-2) ... Selecting previously unselected package grub2-common. Preparing to unpack .../01-grub2-common_2.06-13+deb12u1_amd64.deb ... Unpacking grub2-common (2.06-13+deb12u1) ... Selecting previously unselected package grub-efi-amd64-bin. Preparing to unpack .../02-grub-efi-amd64-bin_2.06-13+deb12u1_amd64.deb ... Unpacking grub-efi-amd64-bin (2.06-13+deb12u1) ... Selecting previously unselected package grub-efi-amd64. Preparing to unpack .../03-grub-efi-amd64_2.06-13+deb12u1_amd64.deb ... Unpacking grub-efi-amd64 (2.06-13+deb12u1) ... Selecting previously unselected package grub-efi. Preparing to unpack .../04-grub-efi_2.06-13+deb12u1_amd64.deb ... Unpacking grub-efi (2.06-13+deb12u1) ... Selecting previously unselected package grub-efi-amd64-signed. Preparing to unpack .../05-grub-efi-amd64-signed_1+2.06+13+deb12u1_amd64.deb ... Unpacking grub-efi-amd64-signed (1+2.06+13+deb12u1) ... Selecting previously unselected package mokutil. Preparing to unpack .../06-mokutil_0.6.0-2_amd64.deb ... Unpacking mokutil (0.6.0-2) ... Selecting previously unselected package shim-unsigned:amd64. Preparing to unpack .../07-shim-unsigned_15.8-1~deb12u1_amd64.deb ... Unpacking shim-unsigned:amd64 (15.8-1~deb12u1) ... Selecting previously unselected package shim-helpers-amd64-signed. Preparing to unpack .../08-shim-helpers-amd64-signed_1+15.8+1~deb12u1_amd64.deb ... Unpacking shim-helpers-amd64-signed (1+15.8+1~deb12u1) ... Selecting previously unselected package shim-signed-common. Preparing to unpack .../09-shim-signed-common_1.44~1+deb12u1+15.8-1~deb12u1_all.deb ... Unpacking shim-signed-common (1.44~1+deb12u1+15.8-1~deb12u1) ... Selecting previously unselected package shim-signed:amd64. Preparing to unpack .../10-shim-signed_1.44~1+deb12u1+15.8-1~deb12u1_amd64.deb ... Unpacking shim-signed:amd64 (1.44~1+deb12u1+15.8-1~deb12u1) ... Setting up efibootmgr (17-2) ... Setting up mokutil (0.6.0-2) ... Setting up grub-efi-amd64-signed (1+2.06+13+deb12u1) ... Setting up grub2-common (2.06-13+deb12u1) ... Installing new version of config file /etc/kernel/postinst.d/zz-update-grub ... Installing new version of config file /etc/kernel/postrm.d/zz-update-grub ... Setting up shim-signed-common (1.44~1+deb12u1+15.8-1~deb12u1) ... No DKMS packages installed: not changing Secure Boot validation state. Setting up grub-efi-amd64-bin (2.06-13+deb12u1) ... Setting up shim-unsigned:amd64 (15.8-1~deb12u1) ... Setting up grub-efi-amd64 (2.06-13+deb12u1) ... Creating config file /etc/default/grub with new version Setting up shim-helpers-amd64-signed (1+15.8+1~deb12u1) ... Setting up grub-efi (2.06-13+deb12u1) ... Setting up shim-signed:amd64 (1.44~1+deb12u1+15.8-1~deb12u1) ... No DKMS packages installed: not changing Secure Boot validation state. Processing triggers for man-db (2.11.2-2) ... user@debian:~$ sudo mkdir -p /boot/efi user@debian:~$ sudo mount /dev/mmcblk1p1 /boot/efi user@debian:~$ sudo grub-install /dev/mmcblk1p1 Installing for x86_64-efi platform. grub-install: error: failed to get canonical path of `overlay'. user@debian:~$ sudo chroot /mnt chroot: failed to run command ‘/bin/bash’: No such file or directory user@debian:~$ sudo mount /dev/mmcblk1p1 /mnt user@debian:~$ sudo mount --bind /dev /mnt/dev user@debian:~$ sudo mount --bind /sys /mnt/sys user@debian:~$ sudo chroot /mnt bash chroot: failed to run command ‘bash’: No such file or directory user@debian:~$ sudo chroot /mnt chroot: failed to run command ‘/bin/bash’: No such file or directory user@debian:~$ sudo chroot /mnt /mnt/bin/bash chroot: failed to run command ‘/mnt/bin/bash’: No such file or directory user@debian:~$ sudo mousepad /mnt/boot/efi/EFI/debian/grub.cfg user@debian:~$ sudo mousepad /mnt/etc/default/grub user@debian:~$ sudo mousepad /etc/grub.d/ user@debian:~$ sudo mousepad /etc/default/grub user@debian:~$ sudo mkdir -p /mnt/etc/default/ user@debian:~$ sudo cp /etc/default/grub /mnt/etc/default/ user@debian:~$ sudo chroot /mnt chroot: failed to run command ‘/bin/bash’: No such file or directory user@debian:~$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=1875396k,nr_inodes=468849,mode=755,inode64) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=384476k,mode=755,inode64) /dev/sda1 on /run/live/medium type iso9660 (ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8) /dev/loop0 on /run/live/rootfs/filesystem.squashfs type squashfs (ro,noatime,errors=continue) tmpfs on /run/live/overlay type tmpfs (rw,noatime,mode=755,inode64) overlay on / type overlay (rw,noatime,lowerdir=/run/live/rootfs/filesystem.squashfs/,upperdir=/run/live/overlay/rw,workdir=/run/live/overlay/work,redirect_dir=on) tmpfs on /usr/lib/live/mount type tmpfs (rw,nosuid,nodev,noexec,relatime,size=384476k,mode=755,inode64) /dev/sda1 on /usr/lib/live/mount/medium type iso9660 (ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8) /dev/loop0 on /usr/lib/live/mount/rootfs/filesystem.squashfs type squashfs (ro,noatime,errors=continue) tmpfs on /usr/lib/live/mount/overlay type tmpfs (rw,noatime,mode=755,inode64) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k,inode64) cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=29,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=450) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) ramfs on /run/credentials/systemd-sysusers.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) ramfs on /run/credentials/systemd-tmpfiles-setup-dev.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700) ramfs on /run/credentials/systemd-sysctl.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime,inode64) ramfs on /run/credentials/systemd-tmpfiles-setup.service type ramfs (ro,nosuid,nodev,noexec,relatime,mode=700) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=384472k,nr_inodes=96118,mode=700,uid=1000,gid=1000,inode64) portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) /dev/mmcblk1p1 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro) /dev/mmcblk1p1 on /mnt type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro) udev on /mnt/dev type devtmpfs (rw,nosuid,relatime,size=1875396k,nr_inodes=468849,mode=755,inode64) sysfs on /mnt/sys type sysfs (rw,nosuid,nodev,noexec,relatime) portal on /root/.cache/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=0,group_id=0) user@debian:~$ ls -l bin/bash ls: cannot access 'bin/bash': No such file or directory | Is /dev/mmcblk1p1 your /boot filesystem? If yes, it is normal that it does not contain bash. You need to mount your / filesystem too. Check "cat /proc/partitions" |
Hi folks, I have a Seagate NAS running Debian Bookworm. I'm unable to get it to sleep, or resume from sleep via a WOL packet like it does with the original firmware. I searched though the original firmware and found the required code. It doesn't actually sleep, it shuts down and can be woken by WOL. I figured out the box needs 2 things to accomplish this - the ethtool eth0 wol needs to be set to "g", and 2 GPIOs need to be set. Debian 12 (and perhaps earlier versions) already automatically sets eth0 WOL to g, but for the sake of completeness, this can be manually set with Code: Select allethtool -s eth0 wol g The GPIO code for enabling WOL in the ethernet chip on the Seagate is Code: Select allecho 59 > /sys/class/gpio/export echo 61 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio59/direction echo out > /sys/class/gpio/gpio61/direction echo 1 > /sys/class/gpio/gpio59/value echo 1 > /sys/class/gpio/gpio61/value echo 59 > /sys/class/gpio/unexport echo 61 > /sys/class/gpio/unexport Issue poweroff, and the NAS can be woken via WOL magic packet. | Hello tony_p, welcome to the forum! Thank you for sharing your solution. tony_p wrote: 2024-03-05 23:49 The GPIO code for enabling WOL in the ethernet chip on the Seagate is Where/how did you find this GPIO code sequence? |
Hi good day! I just installed debian 12 on my pc. I have TP Link Archer T2U Nano wireless adapter. Unfortunately during my switch to debian I can no longer use wifi as it seems its not detected. However, when I tried to check using lsusb this is what I got: Bus 001 Device 004: ID 2357:011e TP-Link AC600 wireless Realtek RTL8811AU [Archer T2U Nano] I cannot make it to work. I did check some forums with the similar issue but still unable to make it work. Thank you in advance. | You probably need a newer kernel. You can install it from Debian Backports. The discussion is moved to the "Hardware" sub-forum. |
I have an elitedesk 800 G3 TWR. It has 4 dimm slots, and can handle a maximum of 64 gb ram. I have 2x PSD416GB2133K (Patriot 16 Gb DDR4 2133 MHz), but each only shows up as 8 Gb. Code: Select all *-bank:0 description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns) product: PSD48G21332 vendor: Unknown - [0x0285] physical id: 0 serial: 00000000 slot: DIMM1 size: 8GiB width: 64 bits clock: 2133MHz (0.5ns) *-bank:1 .. *-bank:2 description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns) product: PSD48G21332 vendor: Unknown - [0x0285] physical id: 2 serial: 00000000 slot: DIMM3 size: 8GiB width: 64 bits clock: 2133MHz (0.5ns) [/pre] [b]I can't figure out why.[/b] What can I do? I've previously used these sticks in another computer where they showed up as 2x 16 Gb. If I add a third 16 Gb stick (HMA82GU6AFR8N-UH; 16 gb DDR4 2400 MHz), this new stick correctly shows up as 16 gb. The others are stuck at 8 gb each. [pre] *-memory description: System Memory physical id: 0 slot: System board or motherboard size: 32GiB *-bank:0 description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns) product: PSD48G21332 vendor: Unknown - [0x0285] physical id: 0 serial: 00000000 slot: DIMM1 size: 8GiB width: 64 bits clock: 2133MHz (0.5ns) *-bank:1 description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns) product: HMA82GU6AFR8N-UH vendor: Hynix/Hyundai physical id: 1 serial: 71CFC0AE slot: DIMM2 size: 16GiB width: 64 bits clock: 2133MHz (0.5ns) *-bank:2 description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2133 MHz (0.5 ns) product: PSD48G21332 vendor: Unknown - [0x0285] physical id: 2 serial: 00000000 slot: DIMM3 size: 8GiB width: 64 bits clock: 2133MHz (0.5ns) | perhaps a similar issue? https://forums.debian.net/viewtopic.php ... nk#p807790 Do the unknown vendor dimms have twice as many chips as the Hynix/Hyundai versions? |
I am trying to resurrect a leftover Macbook Air (Early 2014) (macbookair6,1) by using it as a workstation. As of now I only have the minimal Debian 12 installation on. Upon booting login screen and dmesg shows this particular message: Code: Select all[ 31.640991] irq 0: nobody cared (try booting with the "irqpoll" option) [ 31.641069] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 6.1.0-26-amd64 #1 Debian 6.1.112-1 [ 31.641079] Hardware name: Apple Inc. MacBookAir6,1/Mac-35C1E88140C3E6CF, BIOS 478.0.0.0.0 01/13/2023 [ 31.641083] Call Trace: [ 31.641088] <IRQ> [ 31.641093] dump_stack_lvl+0x44/0x5c [ 31.641106] __report_bad_irq+0x35/0xa7 [ 31.641117] note_interrupt.cold+0xa/0x62 [ 31.641126] handle_irq_event+0x6b/0x70 [ 31.641137] handle_edge_irq+0x87/0x220 [ 31.641147] __common_interrupt+0x3f/0xa0 [ 31.641157] common_interrupt+0x7d/0xa0 [ 31.641168] </IRQ> [ 31.641170] <TASK> [ 31.641173] asm_common_interrupt+0x22/0x40 [ 31.641183] RIP: 0010:cpuidle_enter_state+0xde/0x420 [ 31.641193] Code: 00 00 31 ff e8 43 13 97 ff 45 84 ff 74 16 9c 58 0f 1f 40 00 f6 c4 02 0f 85 25 03 00 00 31 ff e8 88 bc 9d ff fb 0f 1f 44 00 00 <45> 85 f6 0f 88 85 01 00 00 49 63 d6 48 8d 04 52 48 8d 04 82 49 8d [ 31.641199] RSP: 0018:ffffb757800cbe90 EFLAGS: 00000246 [ 31.641207] RAX: ffff907bab331a40 RBX: ffffd7577fd35600 RCX: 0000000000000000 [ 31.641211] RDX: 0000000000000002 RSI: fffffffcbfbdcad9 RDI: 0000000000000000 [ 31.641215] RBP: 0000000000000006 R08: 0000000000000002 R09: 0000000040000219 [ 31.641219] R10: 0000000000000014 R11: 00000000000000d0 R12: ffffffff8379fec0 [ 31.641223] R13: 000000075df30951 R14: 0000000000000006 R15: 0000000000000000 [ 31.641235] cpuidle_enter+0x29/0x40 [ 31.641242] do_idle+0x202/0x2a0 [ 31.641255] cpu_startup_entry+0x26/0x30 [ 31.641264] start_secondary+0x12a/0x150 [ 31.641276] secondary_startup_64_no_verify+0xe5/0xeb [ 31.641291] </TASK> [ 31.641293] handlers: [ 31.641316] [<00000000380bcdea>] dw_dma_interrupt [dw_dmac_core] [ 31.641376] Disabling IRQ #0 I am clueless as what exactly is the fault here, I haven't added the "irqpoll" boot option in GRUB, because I want to understand what is causing the crash in the first place. Attached is the full `dmesg` log. Thanks! | esters wrote: 2024-10-12 14:08 Thanks to the helpful people at Debian IRC. The issue is because ACPI forcefully tries to load _OSI as Darwin. Code: Select all[ 0.152895] ACPI: BIOS _OSI(Darwin) query honored via DMI [ 0.153454] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored After adding the following flags in GRUB (/etc/default/grub) and updating GRUB ( # update-grub ) Code: Select allGRUB_CMDLINE_LINUX="acpi_os_name="Linux" acpi_osi="!Darwin"" Debian boots without IRQ crash. Thanks for reporting back. |
Dear team We have a linux cluster - Debian 7 (Wheezy). In ths syslog file for the past dew days, following error message keeps on coming : Code: Select all/usr/sbin/irqbalance: Load average increasing, re-enabling all cpus for irq balancing I have checked and load average is normal contrary to the reported message. Additionally, we are getting error message on the cluster: Code: Select allCannot read from IPMI device Could you please suggest how to overcome and tackle these issues? Thanks so much for your help. | {IPMI} Have you had a recent power outage? Has the version changed? TC |
I have a Dell Latitude E5590 that can't recover from the lock screen. So far I tried (all GNOME): Ubuntu 20.04 Ubuntu 22.04 live system Ubuntu 22.04 Debian 12.7.0 live system The screen stays black and the device doesn't react to any keypress or touchpad input. The device power indicator light is still on, but since the device doesn't react to anything I can only force a shutdown by long-pressing the power button. It doesn't matter if the lock screen was initiated by selecting the option in the menu or when the automatic screen lock gets engaged after the time limit is reached. I couldn't find any configuration in the power settings that would avoid this problem ... other than just never allowing the system to lock the screen which isn't a viable option – mostly for security reasons. I tried several different power saving options in the UEFI menus, but to no avail. I guess it is a hardware problem. Did anyone of you already encounter such an issue and has found any solution? It seems other reports on the net who stumble upon something similar can overcome this because the problem doesn't sit as deep. I vaguely remember that once when I first installed Ubuntu 22.04 I was able to normally come back from the lock screen by just pressing a button and typing in my pass phrase, but this was only once the case and to my knowledge nothing was differently set-up then. I fear this suggests it is either nbot a hardware problem or one that does just occur most of the time, but not always. Can you think of any command that I should run to investigate further what causes this problem? So far I didn't try the Debian XFCE live system for example. ... I will do that and report back. | Seems to be an issue affecting Windows users too. Is there a BIOS update? https://www.dell.com/community/en/conve ... a8dea1aeda Check for firmware updates with fwupmgr https://github.com/fwupd/fwupd |
debian 12 intel centrino advanced n 6200 https://packages.debian.org/bookworm/al ... i/filelist Installing debian package iwlwifi will get the wifi card to work. I presume one or more firmware files in /lib/firmware/intel make the wifi card work. From the list of files displayed on https://packages.debian.org/bookworm/al ... i/filelist can you identify the specific files which make the wifi card work? There are no firmware files on the list named anything 6200. Thank you. This thread was posted shared to LinkedIn. -Best_Threads | https://wiki.debian.org/iwlwifi |
Hi, My Logitech K380 multi device bluetooth keyboard was working fine for a few hours and now it does not connect. My initial issue with this device was that there was a passcode that needed to be entered in order to connect to it and I was trying to do it through GUI which would bypass the passcode. I was able to get it to work by using bluetoothctl command in the terminal and it was working working for a few hours. The following is the output from the bluetoothctl: Code: Select all[NEW] Device 34:88:5D:F9:01:5B Keyboard K380 [bluetooth]# trust 34:88:5D:F9:01:5B [CHG] Device 34:88:5D:F9:01:5B Trusted: yes Changing 34:88:5D:F9:01:5B trust succeeded [bluetooth]# pair 34:88:5D:F9:01:5B Attempting to pair with 34:88:5D:F9:01:5B [CHG] Device 34:88:5D:F9:01:5B Connected: yes [agent] Passkey: 280755 [agent] Passkey: 280755 [agent] Passkey: 280755 [agent] Passkey: 280755 [agent] Passkey: 280755 [agent] Passkey: 280755 [agent] Passkey: 280755 [CHG] Device 34:88:5D:F9:01:5B Bonded: yes [CHG] Device 34:88:5D:F9:01:5B Modalias: usb:v046DpB342d4201 [CHG] Device 34:88:5D:F9:01:5B UUIDs: 00001000-0000-1000-8000-00805f9b34fb [CHG] Device 34:88:5D:F9:01:5B UUIDs: 00001124-0000-1000-8000-00805f9b34fb [CHG] Device 34:88:5D:F9:01:5B UUIDs: 00001200-0000-1000-8000-00805f9b34fb [CHG] Device 34:88:5D:F9:01:5B ServicesResolved: yes [CHG] Device 34:88:5D:F9:01:5B Paired: yes Pairing successful [CHG] Device 34:88:5D:F9:01:5B WakeAllowed: yes [CHG] Device 34:88:5D:F9:01:5B ServicesResolved: no [CHG] Device 34:88:5D:F9:01:5B Connected: no System info: Code: Select allHost: debian12 Kernel: 6.1.0-13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-13-amd64 root=UUID=c0fcb138-1e44-4b31-9219-368308210009 ro quiet Console: pty pts/1 DM: LightDM v: 1.26.0 Distro: Debian GNU/Linux 12 (bookworm) Machine: Type: Desktop System: LENOVO product: 3209EK4 v: ThinkCentre M92p serial: <superuser required> Mobo: LENOVO model: MAHOBAY serial: <superuser required> BIOS: LENOVO v: 9SKT41AUS date: 11/02/2012 CPU: Info: model: Intel Core i7-3770 bits: 64 type: MT MCP arch: Ivy Bridge gen: core 3 level: v2 built: 2012-15 process: Intel 22nm family: 6 model-id: 0x3A (58) stepping: 9 microcode: 0x21 Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB Speed (MHz): avg: 1638 high: 1875 min/max: 1600/3900 scaling: driver: intel_cpufreq governor: schedutil cores: 1: 1600 2: 1875 3: 1600 4: 1600 5: 1600 6: 1600 7: 1631 8: 1600 bogomips: 54273 Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 Vulnerabilities: Type: gather_data_sampling status: Not affected Type: itlb_multihit status: KVM: VMX unsupported Type: l1tf mitigation: PTE Inversion Type: mds mitigation: Clear CPU buffers; SMT vulnerable Type: meltdown mitigation: PTI Type: mmio_stale_data status: Unknown: No mitigations Type: retbleed status: Not affected Type: spec_rstack_overflow status: Not affected Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected Type: srbds status: Vulnerable: No microcode Type: tsx_async_abort status: Not affected Graphics: Device-1: Intel IvyBridge GT2 [HD Graphics 4000] vendor: Lenovo driver: i915 v: kernel arch: Gen-7 process: Intel 22nm built: 2012-13 ports: active: VGA-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:0162 class-ID: 0300 Display: x11 server: X.org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 tty: 80x24 Monitor-1: VGA-1 model: AOC 2269W serial: AHYGC9A012600 built: 2016 res: 1920x1080 dpi: 102 gamma: 1.2 size: 477x268mm (18.78x10.55") diag: 547mm (21.5") ratio: 16:9 modes: max: 1920x1080 min: 720x400 API: OpenGL Message: GL data unavailable in console. Try -G --display Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Lenovo 7 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1e20 class-ID: 0403 API: ALSA v: k6.1.0-13-amd64 status: kernel-api tools: alsamixer,amixer Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl Network: Device-1: Intel 82579LM Gigabit Network vendor: Lenovo driver: e1000e v: kernel port: f080 bus-ID: 00:19.0 chip-ID: 8086:1502 class-ID: 0200 IF: eno1 state: down mac: fc:4d:d4:3c:8a:ee Device-2: Realtek RTL8188EUS 802.11n Wireless Network Adapter type: USB driver: r8188eu bus-ID: 1-1.1:3 chip-ID: 0bda:8179 class-ID: 0000 serial: 00E04C0001 IF: wlx3c52a1932961 state: up mac: 3c:52:a1:93:29:61 Bluetooth: Device-1: ASUSTek Broadcom BCM20702A0 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-1.2.1:50 chip-ID: 0b05:17cb class-ID: fe01 serial: 5CF3709C2CF4 Report: hciconfig ID: hci0 rfk-id: 24 state: up address: 5C:F3:70:9C:2C:F4 bt-v: 2.1 lmp-v: 4.0 sub-v: 220e hci-v: 4.0 rev: 1000 Info: acl-mtu: 1021:8 sco-mtu: 64:1 link-policy: rswitch sniff link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio, telephony Drives: Local Storage: total: 3.67 TiB used: 2.4 TiB (65.4%) SMART Message: Required tool smartctl not installed. Check --recommends ID-1: /dev/sda maj-min: 8:0 vendor: PNY model: CS900 2TB SSD size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: PNY23172304280100513 rev: 0600 scheme: MBR ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: Seagate model: Ultra Slim MT size: 1.82 TiB block-size: physical: 4096 B logical: 512 B type: N/A serial: NA958A5M rev: 0304 scheme: MBR ID-3: /dev/sdc maj-min: 8:32 type: USB vendor: Kingston model: DataTraveler 2.0 size: 29.08 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: 00241D8CE563EE40B9380556 rev: PMAP scheme: MBR Partition: ID-1: / raw-size: 1.82 TiB size: 1.79 TiB (98.37%) used: 1.2 TiB (66.9%) fs: ext4 dev: /dev/sda1 maj-min: 8:1 Swap: Kernel: swappiness: 60 (default) cache-pressure: 100 (default) ID-1: swap-1 type: partition size: 976 MiB used: 975.9 MiB (100.0%) priority: -2 dev: /dev/sda5 maj-min: 8:5 Sensors: System Temperatures: cpu: 30.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 402 Uptime: 18d 18m wakeups: 618 Memory: 15.41 GiB used: 12.18 GiB (79.0%) Init: systemd v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12 Packages: pm: dpkg pkgs: 2009 libs: 1091 tools: apt,apt-get,gnome-software,synaptic Shell: Bash v: 5.2.15 running-in: pty pts/1 (SSH) inxi: 3.3.26 Anyone have any advice/solutions on how to resolve this issue? Thanks. | Same keyboard here found this link and all good https://unix.stackexchange.com/question ... untu-20-04 |
hello the brother dcp printer scanner does not work anymore since last kernel upgrade Linux debian 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux i did try to reinstall "printer-driver-brlaser" without luck can some one tell me how to make the printer and scanner work ? thank you | arzgi wrote: 2024-10-18 15:54 Code: Select allarto@dell:~/bin$ uname -a Linux dell 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-2 (2023-07-27) x86_64 GNU/Linux arto@dell:~/bin$ cat /etc/debian_version 12.7 arto@dell:~/bin$ So you use testing? It is normal. If you want to get jobs done, use stable. 6.1.0-26-amd64 is the current Stable kernel. |
Hi, Due to installing the wrong Nvidia driver (see my other thread, "[Borked] Missing Nvidia Graphics Firmware"), I now need to know if it is possible to get the laptop working again. Is it possible, perhaps by booting into "rescue mode", to make some changes that would allow the laptop to complete the bootup process beyond "started sddm service" where it now "hangs" ? Or am I now forced to do a complete new/(re-) install ? Stuart | Yes. No. |
Hello, I have been experiencing daily with graphical crashes where the GPU fails to recover and I have to do a hard reset to recover. The log from dmesg is below and from looking at the amd and mesa gitlab issues, it pops up a lot and appears to be possible bugs but not one solid solution. I tried adding amdgpu.aspm=0 amdgpu.gpu_recovery=1, to my grub boot but only once recovered which just logs me out. I started with looking at power, I have a 400W PSU and with a current meter I read following RMS values which I believe I have enough head room. I do not get any freezes when playing a video game or compiling something yet. It usually happens with a browser open, emacs, and terminal open. GPU Stress Test: 1.35A RMS/1.9A Peak 162W/229W Peak Compile all cores used: 1.51A RMS/2.13 Peak 181W/255W Peak Next I swapped for my old Radeon HD 5770 and ran for about 4 days without any issues. Here are the outputs comparing drivers and what I noticed is the 5770 uses radeon drivers verse the amdgpu drivers for the RX 6400. I was hoping that I could try using the radeon drivers for the RX 6400 and see if that prevents the crashes. If crashes still happen, then I would lead to hardware defect of card and seek a warranty related path. Code: Select allOld Card lspci -n -n -k | grep -A 2 -e VGA -e 3D 23:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] Subsystem: Micro-Star International Co., Ltd. [MSI] Juniper XT [Radeon HD 5770] [1462:2140] Kernel driver in use: radeon glxinfo | grep -e OpenGL.vendor -e OpenGL.renderer OpenGL vendor string: X.Org OpenGL renderer string: AMD JUNIPER (DRM 2.50.0 / 6.1.0-11-amd64, LLVM 15.0.6) new card 25:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] [1002:743f] (rev c7) Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M] [1043:0502] Kernel driver in use: amdgpu OpenGL vendor string: AMD OpenGL renderer string: AMD Radeon RX 6400 (navi24, LLVM 15.0.6, DRM 3.49, 6.1.0-11-amd64) I am note sure how to approach this, the wiki shows steps to enable amdgpu, would I just invert this? Any guidance is appreciated! I am nervous my HD 5770 will die any day being I bought it in 2009 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.cik_support=0 amdgpu.cik_support=1" Code: Select all[18408.443914] amdgpu 0000:25:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32769, for process Xorg pid 1150 thread Xorg:cs0 pid 1153) [18408.443931] amdgpu 0000:25:00.0: amdgpu: in page starting at address 0x000080050b20e000 from client 0x1b (UTCL2) [18408.443938] amdgpu 0000:25:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00601031 [18408.443943] amdgpu 0000:25:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [18408.443947] amdgpu 0000:25:00.0: amdgpu: MORE_FAULTS: 0x1 [18408.443951] amdgpu 0000:25:00.0: amdgpu: WALKER_ERROR: 0x0 [18408.443954] amdgpu 0000:25:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [18408.443957] amdgpu 0000:25:00.0: amdgpu: MAPPING_ERROR: 0x0 [18408.443960] amdgpu 0000:25:00.0: amdgpu: RW: 0x0 [18408.443966] amdgpu 0000:25:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32769, for process Xorg pid 1150 thread Xorg:cs0 pid 1153) [18408.443973] amdgpu 0000:25:00.0: amdgpu: in page starting at address 0x000080050b208000 from client 0x1b (UTCL2) [18408.443978] amdgpu 0000:25:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 [18408.443981] amdgpu 0000:25:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [18408.443985] amdgpu 0000:25:00.0: amdgpu: MORE_FAULTS: 0x0 [18408.443987] amdgpu 0000:25:00.0: amdgpu: WALKER_ERROR: 0x0 [18408.443990] amdgpu 0000:25:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [18408.443993] amdgpu 0000:25:00.0: amdgpu: MAPPING_ERROR: 0x0 [18408.443996] amdgpu 0000:25:00.0: amdgpu: RW: 0x0 [18408.444001] amdgpu 0000:25:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32769, for process Xorg pid 1150 thread Xorg:cs0 pid 1153) [18408.444008] amdgpu 0000:25:00.0: amdgpu: in page starting at address 0x000080050b208000 from client 0x1b (UTCL2) [18408.444012] amdgpu 0000:25:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 [18408.444015] amdgpu 0000:25:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [18408.444018] amdgpu 0000:25:00.0: amdgpu: MORE_FAULTS: 0x0 [18408.444021] amdgpu 0000:25:00.0: amdgpu: WALKER_ERROR: 0x0 [18408.444024] amdgpu 0000:25:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [18408.444027] amdgpu 0000:25:00.0: amdgpu: MAPPING_ERROR: 0x0 [18408.444029] amdgpu 0000:25:00.0: amdgpu: RW: 0x0 [18408.444036] amdgpu 0000:25:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:6 pasid:32769, for process Xorg pid 1150 thread Xorg:cs0 pid 1153) [18408.444041] amdgpu 0000:25:00.0: amdgpu: in page starting at address 0x000080050b20f000 from client 0x1b (UTCL2) [18408.444046] amdgpu 0000:25:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000 [18408.444049] amdgpu 0000:25:00.0: amdgpu: Faulty UTCL2 client ID: CB/DB (0x0) [18408.444052] amdgpu 0000:25:00.0: amdgpu: MORE_FAULTS: 0x0 [18408.444055] amdgpu 0000:25:00.0: amdgpu: WALKER_ERROR: 0x0 [18408.444057] amdgpu 0000:25:00.0: amdgpu: PERMISSION_FAULTS: 0x0 [18408.444060] amdgpu 0000:25:00.0: amdgpu: MAPPING_ERROR: 0x0 [18408.444063] amdgpu 0000:25:00.0: amdgpu: RW: 0x0 [18418.671966] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered | livix07 wrote: 2023-08-22 08:25 Please install firmware-linux-nonfree and firmware-misc-nonfree, then restart computer. There might be a better driver available in those packages. Firmware packages contain firmware, not drivers. They are different things. |
I am having issues on my Lenovo 300e 2nd gen 81M9 getting the touch screen working (not the trackpad). It doesn't seem to work at all and isn't showing in lsusb but it does seem to be listed as an input device. This is the latest Debian version with all updates running Cinnamon. Any ideas to get it working? I assume the touchscreen is the random ELAN device in xinput with no name. Touchscreen works fine in windows. | I have found that using the Gnome desktop was better for me when using a touchscreen device, I don't know if it is down to Wayland or Gnome but it's the desktop I have found to be most trouble free for this use case. |
Hi there! My computer is an ASUS NUC 14 Pro (NUC14RVHU7) and I recently experienced connection loss with its Intel Ethernet Controller I226-V. I'm using Debian 12, with the last Linux Libre kernel (6.11.0-gnu) and the controller driver is igc. Shortly after booting up, once connected to my session, the ethernet connection went dead. The problem occurred after just a few minutes. Just for the record, as I have a dual boot install with Ubuntu 24.04, I encounter the exact same bug though kernel is not the same (6.8.0-45-generic). I managed to find a solution and came here to share it. The problem is related to Active-State Power Management (ASPM) that saves power in the PCI Express subsystem by setting a lower power state for PCIe links when the devices to which they connect are not in use. It seems that ASPM is not well managed by the igc driver. So a solution is to disable ASPM in UEFI. You'll need to access the UEFI and then : Click on the “Power, Performance and Cooling” tab. Click on the “Secondary Power Settings” link. Scroll down and uncheck the “PCIe ASPM Support” option. Press F10 to save the change and exit. From now on, this power management-related connectivity loss problem should be solved once and for all. An other way to achieve this without accessing UEFI would be to pass the "pcie_aspm.policy=performance" kernel option at boot time through GRUB (by editing "/etc/default/grub" and passing this command through the GRUB_CMDLINE_LINUX_DEFAULT parameter). I found this solution here in a RHEL 7 guide, but it didn't work. You can also try the "pcie_aspm=off" kernel option, which I didn't try yet, as disabling it through UEFI works as expected. That's it. Hope it will help someone else. | Hello, miroslavbucek wrote: 2024-11-04 15:38 I noticed though that until I connect the NVMe drive, the I226-V works. A hardware issue ? The block diagram from: ASUS NUC 14 Pro/Pro+ Kit/Board/Mini-PC shows that lines for LAN and M2 slots are different. miroslavbucek wrote: 2024-11-04 15:38 If I plug it in, it works according to the LEDs on the connector a few seconds after boot, then the port is completely dead. I have a NUC14RVHU5 [..] It's running Proxmox, Linux kernel iris 6.8.12-3-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-3 (2024-10-23T11:41Z) x86_64 GNU/Linux BIOS latest version 44. You might try using Debian Bookworm with the latest kernel from Debian Backports. Hope this helps. |
Hi forum! I am quite new to Linux and played around on my Laptop with Linux Mint and recently I got a thin client for Plex, AdGuard, etc with CasaOS on Debian 12. This is the device I am talking about: Dell Wyse 5070. Installing Debian and CasaOS was pretty easy and I even managed basic things like installing packages via command line (I didn´t installed any xserver). I also attached an external harddrive via USB as NAS and storage for Plex. Seagate STGY8000400. But then I noticed, that it is continously spinning and not going into any suspend mode. I was following this great thread/post: viewtopic.php?p=743326#p743326 and I figured out, that my issues looked the same, but I don't understand the solution. I was able to reproduce most of the steps and I finally managed to communicate with the drive the same way IcIoNViO did on his post by adding my drive to quirks via the grub-menu (same link as in his linked post: https://www.smartmontools.org/wiki/SAT- ... agSettings). I also managed to install smartd (quite proud as a bloody beginner ) and figured out my drives vendor- and product-id with lsusb. Now I can use smartctl to get details from my disk. But the next step, executing Code: Select allhdparm -B 127 /dev/sdb2 failed with Code: Select allsetting Advanced Power Management level to 0x7f (127) HDIO_DRIVE_CMD failed: Input/output error APM_level = not supported I am totally honest: I don't know what usb_storage.quirks, NO_ATA_1X and UAS is and I have no idea how to continue. Google didn' helped me. Here are some outputs from smartctl and hdparm Code: Select allben@BenHomeserver:~$ sudo smartctl -d sat -a /dev/sdb2 smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-26-amd64] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate IronWolf Device Model: ST8000VN002-2ZM188 Serial Number: ZPV0R2Y1 LU WWN Device Id: 5 000c50 0e94780ff Firmware Version: SC60 User Capacity: 8.001.563.222.016 bytes [8,00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Form Factor: 3.5 inches Device is: In smartctl database 7.3/5319 ATA Version is: ACS-3 T13/2161-D revision 5 SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Oct 24 18:42:29 2024 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 880) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x70bd) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 079 066 006 Pre-fail Always - 75516802 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 18 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 045 Pre-fail Always - 4893098 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 71 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 18 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 076 046 040 Old_age Always - 24 (Min/Max 22/24) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 16 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 38 194 Temperature_Celsius 0x0022 024 054 000 Old_age Always - 24 (0 21 0 0 0) 195 Hardware_ECC_Recovered 0x001a 079 066 000 Old_age Always - 75516802 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 34h+54m+14.104s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 17883331298 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 134999722 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. and Code: Select allben@BenHomeserver:~$ sudo hdparm -I /dev/sdb2 /dev/sdb2: ATA device, with non-removable media Model Number: ST8000VN002-2ZM188 Serial Number: ZPV0R2Y1 Firmware Revision: SC60 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Used: unknown (minor revision code 0x006d) Supported: 10 9 8 7 6 5 Likely used: 10 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 15628053168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 7630885 MBytes device size with M = 1000*1000: 8001563 MBytes (8001 GB) cache/buffer size = unknown Form Factor: 3.5 inch Nominal Media Rotation Rate: 5400 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 16 Recommended acoustic management value: 128, current value: 128 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * DOWNLOAD_MICROCODE Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * Media Card Pass-Through * General Purpose Logging feature set * 64-bit World wide name * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE unknown 119[6] * unknown 119[7] * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Phy event counters * READ_LOG_DMA_EXT equivalent to READ_LOG_EXT DMA Setup Auto-Activate optimization Device-initiated interface power management * Software settings preservation unknown 78[7] * SMART Command Transport (SCT) feature set * SCT Write Same (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[7] unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) unknown 206[14] (vendor specific) * DOWNLOAD MICROCODE DMA command Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 882min for SECURITY ERASE UNIT. 882min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000c500e94780ff NAA : 5 IEEE OUI : 000c50 Unique ID : 0e94780ff Checksum: correct Can anyone help me to solve this like IcIoNViO did (or show another way). I really want my drive go to sleep when it's not in use... | Perhaps, udisks will solved this problem? man udisks |
Hi all, have been a Linux user close to 20 years now, a Debian user for 16 of those I'd say, and I'm currently a Linux SysAdmin for a department at the University for about 8 years now, so I know a thing or two about Linux and Debian, but there's even more that I don't know. Here's one example where yesterday I wiggled the mouse to wake up the screen on my workstation and login as usual, except after I entered my password, the login window froze. This system is running Debian 11 still and, at the time, it was running Linux 5.10.0-21-amd64, Debian 5.10.162-1 (2023-01-21). Keyboard and mouse were fine and I switched to a console to login. There was nothing new in the log files, so I just reboot'd the system since it had some updates recently. It booted up fine as I saw all the green OK messages as it loaded up everything. One of the last ones I see on this screen is [ OK ] Starting GNOME Display Manager and screen goes black and login window opens. Except this time I was greeted with the built-in autoblinder mechanism, on dual monitors, as depicted here https://redhat.discourse-cdn.com/fedora ... 45d7a0.png (sorry for tainting the forum with redhat material in my first post, but that's what ya get for attacking my eyes!) telling me there's a problem it can't recover from and to contact a sys admin. Egads computer, that's me! I switched back to a nice, black console and I was then shown these messages: Code: Select allnouveau 0000:01:00.0: firmware: failed to load nouveau/nve7_fuc084 (-2) nouveau 0000:01:00.0: firmware: failed to load nouveau/nve7_fuc084 (-2) nouveau 0000:01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 nouveau 0000:01:00.0: firmware: failed to load nouveau/nve7_fuc084d (-2) nouveau 0000:01:00.0: firmware: failed to load nouveau/nve7_fuc084d (-2) nouveau 0000:01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 nouveau 0000:01:00.0: msvld: unable to load firmware data nouveau 0000:01:00.0: msvld: init failed, -19 Well, I can see it doesn't like 084 anymore, but why? BTW, 01:00.0 is a: 01:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GTX 650] (rev a1) So far, I've tried: Upgrade xserver-xorg-video-nouveau:amd64 (1:1.0.17-1, 1:1.0.17-2) Upgrade: linux-image-amd64:amd64 (5.10.162-1, 6.1.99-1) (2024-07-15) Switched to the nvidia-tesla-470-driver packaged firmware Now, the login window doesn't even load, but there are no errors shown like with the nouveau firmware, but the console font and resolution have turned to sh*te, maybe 640x480 or less and Instead, these are the latest from dmesg: Code: Select allkernel: [ 0.589887] pci 0000:01:00.1: D0 power state depends on 0000:01:00.0 kernel: [ 11.440779] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem kernel: [ 14.609386] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0 I'm not sure what else to try to get it working. I found someone out there that had quite a technical approach with manual archive downloads from a vendor? somewhere and manually extracting code into the kernel source tree? I can find that again probably but that seemed way to technical and frakendebian as a viable solution. It seems wrong that this would suddenly start happening, and both updated nouveau and Nvidia drivers fail to ... well I don't know exactly, what happens when the display changes from the low-res text-based console to high-res graphics environment? Is the difference between the video modes used for the consoles and during booting compared to what something like Gnome uses able to be caused from a hardware issue?? It has to be hardware related I'm guessing, but not sure how the initial video during POST and boot and for the consoles is working if there's a hardware issue with the card. So, as usual need to figure out what's broken and why and how to fix it. Would appreciate your feedback and insights to figure it out ASAP. Thanks! | agi-sysadmin wrote: 2024-08-17 07:44 Gotcha. Yes could dump the whole log files, but I'm also trying to be succinct and rev. You're right though, I see now I have it configured to the stable branch instead of the code name. I don't see how this would cause driver corruption or whatever is going on here, considering Gnome has been starting and running fine forever before yesterday and there haven't been any system or relevant app updates. If you changed a Bullseye system sources to stable, you are asking it to upgrade to current stable which is Bookworm. If unattended-upgrades are active it may have upgraded the whole system but not completely. I suggest you do a console login and run as root apt full-upgrade to complete the transition to Bookworm. I'm not sure if this is what happened but /var/log/apt/history.log should be able to enlighten you. It's safer to keep your sources as release codename eg.bookworm to avoid surprise upgrades when a new version is released. |
Have a question and requesting some help. Would like to install Debian 12 server on a pcengines apu3 board that uses a serial port rather than a grahpics interface. Have installed the serial interface using and old pc running minicom with success but the install program (usb install program) hangs when selecting a drive (on the apu3 board) to perform the install. It consistently only allows install on the usb only that carries the install program and does not allow the boards msata 120G drive to be the selected install target. Any help would be appreciated. | Hello, Disclaimer: I have never installed Debian on this board. Are you asking how to get the internal MSATA drive recognised at install time? Have you installed the type of mSATA recommended by the manufacturer? https://pcengines.ch/msata16g.htm There is this interesting annotation in the link above: Note: mSATA and miniPCI express slots look exactly the same, but the SSD will only work in a mSATA slot. Please read the friendly board manual... Search the Debian Wiki, here is some general documentation: https://wiki.debian.org/FreedomBox/Hardware/APU Note: moved to "Hardware" sub-forum. |
This is more of a bug report but idk where I'm supposed to go. I also tried asking in the ubuntu and lenovo forums without much luck I want to swap my laptop over to debian but I have been having strange issues with some of the function keys. These issues occur in every distro I've tried and even happen in hyper-v on windows 11. If I tap or hold either volume key it will keep getting pressed forever until I hit either volume key. None of the lights on my function keys turn on or off. The laptop has a ryzen 7530u. | install inxi, and run in terminalCode: Select allinxi -Fx Post the output here, remember to use code tags. |
Hello! In Debian 12.2 w/KDE, my HP laptop's internal rtl8188ee wifi interface will go up and down, then stay down, even after reboots. I bought an external USB interface that uses rtl8821cu, and the same thing happens. The problem does not happen in Windows 7, but it does in Debian 12.2, Puppy Linux, Manjaro, and ArchCraft. I ran these from clean Live ISO's, or from fresh installations to an external hard drive. The logs below are from a Debian 12.2 Live ISO via Ventoy. Several posts recommend setting the rtl8188ee kernel module to switch to antenna #2, but current module does not have a parameter for this. Ideas? P.S. With each new fresh install or live ISO, the connection works fine for hours or days, and then fails more and more often, until the wifi will not find any networks where there are plenty available -- as if something "builds up" toward failure. Thanks for any insights! Code: Select all$ inxi -MnS System: Host: debian 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: Hewlett-Packard product: HP Pavilion 17 Notebook PC [...] UEFI: Insyde v: F.12 date: 08/18/2014 Network: Device-1: Realtek RTL8188EE Wireless Network Adapter driver: rtl8188ee IF: wlo1 state: down mac: 9e:e6:a2:8c:1d:64 Device-2: Realtek RTL810xE PCI Express Fast Ethernet driver: r8169 IF: eno1 state: up speed: 100 Mbps duplex: full mac: 38:63:bb:92:a9:11 Code: Select all$ nmcli device show wlo1 GENERAL.DEVICE: wlo1 GENERAL.TYPE: wifi GENERAL.HWADDR: AA:AE:0B:57:38:87 GENERAL.MTU: 1500 GENERAL.STATE: 30 (disconnected) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.GATEWAY: -- IP6.GATEWAY: -- Code: Select all$ nmcli device status DEVICE TYPE STATE CONNECTION eno1 ethernet connected Wired connection 1 lo loopback connected (externally) lo wlo1 wifi disconnected -- p2p-dev-wlo1 wifi-p2p disconnected -- Code: Select all$ lspci -nnk | grep -iA2 net 08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter [10ec:8179] (rev 01) DeviceName: Realtek RTL8188EE 802.11bgn Wi-Fi Adapter Subsystem: Hewlett-Packard Company RTL8188EE mini-PCIe card [103c:197d] Code: Select all$ NetworkManager --print-config # NetworkManager configuration: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf) [main] # rc-manager= # auth-polkit=true # dhcp=internal # iwd-config-path= plugins=ifupdown,keyfile configure-and-quit=no [ifupdown] managed=false [logging] # backend=journal # audit=true [device] # wifi.backend=wpa_supplicant [device-31-mac-addr-change] match-device=driver:eagle_sdio,driver:wl wifi.scan-rand-mac-address=no # no-auto-default file "/var/lib/NetworkManager/no-auto-default.state" Code: Select all$ rfkill list all 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Code: Select all$ iwconfig wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr=2347 B Fragment thr:off Encryption key:off Power Management:off Code: Select all$ modinfo rtl8188ee | grep "parm" # list module parameters parm: swenc:Set to 1 for software crypto (default 0) parm: ips:Set to 0 to not use link power save (default 1) parm: swlps:Set to 1 to use SW control power save (default 0) parm: fwlps:Set to 1 to use FW control power save (default 1) parm: msi:Set to 1 to use MSI interrupts mode (default 1) parm: aspm:Set to 1 to enable ASPM (default 1) parm: debug_level:Set debug level (0-5) (default 0) (int) parm: debug_mask:Set debug mask (default 0) (ullong) parm: disable_watchdog:Set to 1 to disable the watchdog (default 0) Code: Select all$ systool -v -m rtl8188ee #current running configuration Module = "rtl8188ee" Attributes: coresize = "114688" initsize = "0" initstate = "live" refcnt = "0" taint = "" uevent = <store method only> Parameters: aspm = "0" debug_level = "0" debug_mask = "0" disable_watchdog = "N" fwlps = "N" ips = "N" msi = "Y" swenc = "Y" swlps = "N" Code: Select all$ journalctl -u NetworkManager.service --grep=wlo1 May 30 19:06:41 device (wlo1): driver supports Access Point (AP) mode May 30 19:06:41 manager: (wlo1): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3) May 30 19:06:41 device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') May 30 19:06:41 device (wlo1): set-hw-addr: set MAC address to 2A:D6:EE:74:F6:1F (scanning) May 30 19:06:42 device (wlo1): supplicant interface state: internal-starting -> disconnected May 30 19:06:42 Wi-Fi P2P device controlled by interface wlo1 created May 30 19:06:42 manager: (p2p-dev-wlo1): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/4) May 30 19:06:42 device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') May 30 19:06:42 device (wlo1): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') May 30 19:06:42 device (p2p-dev-wlo1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') May 30 19:08:13 device (wlo1): Activation: starting connection 'Kinky Kitty 3' (727ddb0d-f5bb-4302-953a-ff91323da031) May 30 19:08:13 device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') May 30 19:08:13 device (wlo1): set-hw-addr: reset MAC address to C0:38:96:82:C6:9E (preserve) May 30 19:08:13 device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 30 19:08:13 device (wlo1): Activation: (wifi) access point 'Kinky Kitty 3' has security, but secrets are required. May 30 19:08:13 device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') May 30 19:08:13 sup-iface[178fb45a9d6ce7e6,0,wlo1]: wps: type pbc start... May 30 19:08:13 device (wlo1): supplicant interface state: disconnected -> interface_disabled May 30 19:08:13 device (p2p-dev-wlo1): supplicant management interface state: disconnected -> interface_disabled May 30 19:08:13 device (wlo1): supplicant interface state: interface_disabled -> inactive May 30 19:08:13 device (p2p-dev-wlo1): supplicant management interface state: interface_disabled -> inactive May 30 19:08:13 device (wlo1): supplicant interface state: inactive -> scanning May 30 19:08:13 device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning May 30 19:08:45 device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') May 30 19:08:45 device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 30 19:08:45 device (wlo1): Activation: (wifi) connection 'Kinky Kitty 3' has security, and secrets exist. No new secrets needed. May 30 19:08:45 device (wlo1): supplicant interface state: scanning -> authenticating May 30 19:08:45 device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating May 30 19:08:45 device (wlo1): supplicant interface state: authenticating -> associating May 30 19:08:45 device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating May 30 19:08:45 device (wlo1): supplicant interface state: associating -> 4way_handshake May 30 19:08:45 device (p2p-dev-wlo1): supplicant management interface state: associating -> 4way_handshake May 30 19:08:46 device (wlo1): supplicant interface state: 4way_handshake -> completed May 30 19:08:46 device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Kinky Kitty 3" May 30 19:08:46 device (p2p-dev-wlo1): supplicant management interface state: 4way_handshake -> completed May 30 19:08:46 device (wlo1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') May 30 19:08:46 dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds) May 30 19:08:47 dhcp4 (wlo1): state changed new lease, address=192.168.1.107 May 30 19:08:47 device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') May 30 19:08:47 device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') May 30 19:08:47 device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') May 30 19:08:47 device (wlo1): Activation: successful, device activated. May 30 19:08:47 dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds) May 30 19:08:47 dhcp6 (wlo1): state changed new lease, address=2600:1700:df50:a680::41 May 30 19:08:56 audit: op="statistics" interface="wlo1" ifindex=3 args="2000" pid=2395 uid=1000 result="success" May 30 19:10:33 policy: set 'Kinky Kitty 3' (wlo1) as default for IPv4 routing and DNS May 30 19:10:33 policy: set 'Kinky Kitty 3' (wlo1) as default for IPv6 routing and DNS May 30 19:29:35 audit: op="statistics" interface="wlo1" ifindex=3 args="2000" pid=2395 uid=1000 result="success" May 30 19:31:01 device (p2p-dev-wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') May 30 19:31:01 device (wlo1): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') May 30 19:31:01 device (wlo1): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed') May 30 19:31:01 dhcp4 (wlo1): canceled DHCP transaction May 30 19:31:01 dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds) May 30 19:31:01 dhcp4 (wlo1): state changed no lease May 30 19:31:01 dhcp6 (wlo1): canceled DHCP transaction May 30 19:31:01 dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds) May 30 19:31:01 dhcp6 (wlo1): state changed no lease May 30 19:31:01 device (wlo1): set-hw-addr: set MAC address to 92:E5:BA:33:49:7D (scanning) May 30 19:31:02 device (wlo1): supplicant interface state: completed -> disconnected May 30 19:31:02 device (wlo1): supplicant interface state: disconnected -> interface_disabled May 30 19:31:02 device (wlo1): supplicant interface state: interface_disabled -> disconnected May 30 19:31:02 device (wlo1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') May 30 19:31:02 device (wlo1): set-hw-addr: reset MAC address to C0:38:96:82:C6:9E (unmanage) May 31 07:02:03 device (wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') May 31 07:02:03 device (wlo1): set-hw-addr: set MAC address to 52:84:99:25:02:77 (scanning) May 31 07:02:04 device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') May 31 07:02:04 device (wlo1): supplicant interface state: internal-starting -> disconnected May 31 07:02:04 device (p2p-dev-wlo1): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') May 31 07:02:04 Wi-Fi P2P device controlled by interface wlo1 created May 31 07:02:04 manager: (p2p-dev-wlo1): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5) May 31 07:02:04 device (p2p-dev-wlo1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') May 31 07:02:04 device (wlo1): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') May 31 07:02:04 device (p2p-dev-wlo1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') May 31 07:02:05 device (wlo1): Activation: starting connection 'Kinky Kitty 3' (727ddb0d-f5bb-4302-953a-ff91323da031) May 31 07:02:05 device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') May 31 07:02:05 device (wlo1): set-hw-addr: reset MAC address to C0:38:96:82:C6:9E (preserve) May 31 07:02:05 device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 31 07:02:05 device (wlo1): Activation: (wifi) access point 'Kinky Kitty 3' has security, but secrets are required. May 31 07:02:05 device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') May 31 07:02:05 sup-iface[e01fd88d0e6cbb35,1,wlo1]: wps: type pbc start... May 31 07:02:05 device (wlo1): supplicant interface state: disconnected -> interface_disabled May 31 07:02:05 device (p2p-dev-wlo1): supplicant management interface state: disconnected -> interface_disabled May 31 07:02:05 device (wlo1): supplicant interface state: interface_disabled -> inactive May 31 07:02:05 device (p2p-dev-wlo1): supplicant management interface state: interface_disabled -> inactive May 31 07:02:05 device (wlo1): supplicant interface state: inactive -> scanning May 31 07:02:05 device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning May 31 07:02:32 device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') May 31 07:02:32 device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 31 07:02:32 device (wlo1): Activation: (wifi) connection 'Kinky Kitty 3' has security, and secrets exist. No new secrets needed. May 31 07:02:33 device (wlo1): supplicant interface state: scanning -> authenticating May 31 07:02:33 device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating May 31 07:02:36 device (wlo1): supplicant interface state: authenticating -> disconnected May 31 07:02:36 device (p2p-dev-wlo1): supplicant management interface state: authenticating -> disconnected May 31 07:02:36 device (wlo1): supplicant interface state: disconnected -> scanning May 31 07:02:36 device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning May 31 07:02:37 device (wlo1): supplicant interface state: scanning -> authenticating May 31 07:02:37 device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating May 31 07:02:37 device (wlo1): supplicant interface state: authenticating -> associating May 31 07:02:37 device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating May 31 07:02:37 device (wlo1): supplicant interface state: associating -> 4way_handshake May 31 07:02:37 device (p2p-dev-wlo1): supplicant management interface state: associating -> 4way_handshake May 31 07:02:41 device (wlo1): supplicant interface state: 4way_handshake -> disconnected May 31 07:02:41 device (wlo1): Activation: (wifi) disconnected during association, asking for new key May 31 07:02:41 device (wlo1): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') May 31 07:02:41 device (p2p-dev-wlo1): supplicant management interface state: 4way_handshake -> disconnected May 31 07:02:41 device (wlo1): supplicant interface state: disconnected -> inactive May 31 07:02:41 device (p2p-dev-wlo1): supplicant management interface state: disconnected -> inactive May 31 07:02:53 device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') May 31 07:02:53 device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 31 07:02:53 device (wlo1): Activation: (wifi) connection 'Kinky Kitty 3' has security, and secrets exist. No new secrets needed. May 31 07:02:54 device (wlo1): supplicant interface state: inactive -> scanning May 31 07:02:54 device (p2p-dev-wlo1): supplicant management interface state: inactive -> scanning May 31 07:02:55 device (wlo1): supplicant interface state: scanning -> authenticating May 31 07:02:55 device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating May 31 07:02:55 device (wlo1): supplicant interface state: authenticating -> associating May 31 07:02:55 device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating May 31 07:02:55 device (wlo1): supplicant interface state: associating -> 4way_handshake May 31 07:02:55 device (p2p-dev-wlo1): supplicant management interface state: associating -> 4way_handshake May 31 07:02:55 device (wlo1): supplicant interface state: 4way_handshake -> completed May 31 07:02:55 device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Kinky Kitty 3" May 31 07:02:55 device (p2p-dev-wlo1): supplicant management interface state: 4way_handshake -> completed May 31 07:02:55 device (wlo1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') May 31 07:02:55 dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds) May 31 07:02:55 dhcp4 (wlo1): state changed new lease, address=192.168.1.107 May 31 07:02:55 policy: set 'Kinky Kitty 3' (wlo1) as default for IPv4 routing and DNS May 31 07:02:55 device (wlo1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') May 31 07:02:55 device (wlo1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') May 31 07:02:55 device (wlo1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') May 31 07:02:55 device (wlo1): Activation: successful, device activated. May 31 07:02:57 dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds) May 31 07:02:57 policy: set 'Kinky Kitty 3' (wlo1) as default for IPv6 routing and DNS May 31 07:02:57 dhcp6 (wlo1): state changed new lease, address=2600:1700:df50:a680::41 May 31 07:03:33 audit: op="statistics" interface="wlo1" ifindex=3 args="2000" pid=2395 uid=1000 result="success" May 31 07:23:24 audit: op="statistics" interface="wlo1" ifindex=3 args="2000" pid=2395 uid=1000 result="success" May 31 07:31:20 dhcp6 (wlo1): state changed new lease, address=2600:1700:df50:a680::41 May 31 07:59:19 device (wlo1): supplicant interface state: completed -> disconnected May 31 07:59:19 device (p2p-dev-wlo1): supplicant management interface state: completed -> disconnected May 31 07:59:19 device (wlo1): supplicant interface state: disconnected -> scanning May 31 07:59:19 device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning May 31 07:59:34 debian NetworkManager[1717]: <warn> [1717160374.4851] device (wlo1): link timed out. May 31 07:59:34 device (wlo1): state change: activated -> failed (reason 'ssid-not-found', sys-iface-state: 'managed') May 31 07:59:34 device (wlo1): set-hw-addr: set MAC address to AA:AE:0B:57:38:87 (scanning) May 31 07:59:35 debian NetworkManager[1717]: <warn> [1717160375.3359] device (wlo1): Activation: failed for connection 'Kinky Kitty 3' May 31 07:59:35 device (wlo1): supplicant interface state: scanning -> interface_disabled May 31 07:59:35 device (p2p-dev-wlo1): supplicant management interface state: scanning -> interface_disabled May 31 07:59:35 device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') May 31 07:59:35 dhcp4 (wlo1): canceled DHCP transaction May 31 07:59:35 dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds) May 31 07:59:35 dhcp4 (wlo1): state changed no lease May 31 07:59:35 dhcp6 (wlo1): canceled DHCP transaction May 31 07:59:35 dhcp6 (wlo1): activation: beginning transaction (timeout in 45 seconds) May 31 07:59:35 dhcp6 (wlo1): state changed no lease May 31 07:59:35 device (wlo1): supplicant interface state: interface_disabled -> scanning May 31 07:59:35 device (p2p-dev-wlo1): supplicant management interface state: interface_disabled -> scanning May 31 07:59:36 device (wlo1): supplicant interface state: scanning -> disconnected May 31 07:59:36 device (p2p-dev-wlo1): supplicant management interface state: scanning -> disconnected May 31 08:06:27 device (wlo1): set-hw-addr: set MAC address to B2:B7:DE:24:65:78 (scanning) May 31 08:06:28 device (wlo1): supplicant interface state: disconnected -> interface_disabled May 31 08:06:28 device (p2p-dev-wlo1): supplicant management interface state: disconnected -> interface_disabled May 31 08:06:28 device (wlo1): supplicant interface state: interface_disabled -> inactive May 31 08:06:28 device (p2p-dev-wlo1): supplicant management interface state: interface_disabled -> inactive Code: Select all$ journalctl -u wpa_supplicant.service May 30 19:08:13 WPS-PBC-ACTIVE May 30 19:08:45 WPS-CANCEL May 30 19:08:45 SME: Trying to authenticate with cc:ab:2c:5c:6d:e4 (SSID='Kinky Kitty 3' freq=2447 MHz) May 30 19:08:45 Trying to associate with cc:ab:2c:5c:6d:e4 (SSID='Kinky Kitty 3' freq=2447 MHz) May 30 19:08:45 Associated with cc:ab:2c:5c:6d:e4 May 30 19:08:45 CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 30 19:08:45 CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US May 30 19:08:46 WPA: Key negotiation completed with cc:ab:2c:5c:6d:e4 [PTK=CCMP GTK=CCMP] May 30 19:08:46 CTRL-EVENT-CONNECTED - Connection to cc:ab:2c:5c:6d:e4 completed [id=0 id_str=] May 30 19:08:46 debian wpa_supplicant[1720]: bgscan simple: Failed to enable signal strength monitoring May 30 19:31:01 CTRL-EVENT-DISCONNECTED bssid=cc:ab:2c:5c:6d:e4 reason=3 locally_generated=1 May 30 19:31:01 CTRL-EVENT-DSCP-POLICY clear_all May 30 19:31:01 CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 30 19:31:02 CTRL-EVENT-DSCP-POLICY clear_all May 30 19:31:03 CTRL-EVENT-DSCP-POLICY clear_all May 30 19:31:03 debian wpa_supplicant[1720]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0 May 31 07:02:05 WPS-PBC-ACTIVE May 31 07:02:33 WPS-CANCEL May 31 07:02:33 SME: Trying to authenticate with cc:ab:2c:5c:6d:e4 (SSID='Kinky Kitty 3' freq=2447 MHz) May 31 07:02:37 SME: Trying to authenticate with cc:ab:2c:5c:6d:e4 (SSID='Kinky Kitty 3' freq=2447 MHz) May 31 07:02:37 Trying to associate with cc:ab:2c:5c:6d:e4 (SSID='Kinky Kitty 3' freq=2447 MHz) May 31 07:02:37 Associated with cc:ab:2c:5c:6d:e4 May 31 07:02:37 CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 31 07:02:37 CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US May 31 07:02:41 CTRL-EVENT-DISCONNECTED bssid=cc:ab:2c:5c:6d:e4 reason=15 May 31 07:02:41 WPA: 4-Way Handshake failed - pre-shared key may be incorrect May 31 07:02:41 CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Kinky Kitty 3" auth_failures=1 duration=10 reason=WRONG_KEY May 31 07:02:41 CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 31 07:02:55 SME: Trying to authenticate with cc:ab:2c:5c:6d:e4 (SSID='Kinky Kitty 3' freq=2447 MHz) May 31 07:02:55 Trying to associate with cc:ab:2c:5c:6d:e4 (SSID='Kinky Kitty 3' freq=2447 MHz) May 31 07:02:55 Associated with cc:ab:2c:5c:6d:e4 May 31 07:02:55 CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 May 31 07:02:55 CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=US May 31 07:02:55 WPA: Key negotiation completed with cc:ab:2c:5c:6d:e4 [PTK=CCMP GTK=CCMP] May 31 07:02:55 CTRL-EVENT-CONNECTED - Connection to cc:ab:2c:5c:6d:e4 completed [id=0 id_str=] May 31 07:02:55 debian wpa_supplicant[1720]: bgscan simple: Failed to enable signal strength monitoring May 31 07:59:19 CTRL-EVENT-DISCONNECTED bssid=cc:ab:2c:5c:6d:e4 reason=4 locally_generated=1 May 31 07:59:19 CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD May 31 07:59:35 Reject scan trigger since one is already pending May 31 07:59:35 Reject scan trigger since one is already pending Code: Select all$ dmesg | grep wlo1 [ 12.076372] rtl8188ee 0000:08:00.0 wlo1: renamed from wlan0 [ 182.085532] wlo1: authenticate with cc:ab:2c:5c:6d:e4 [ 182.085561] wlo1: 80 MHz not supported, disabling VHT [ 182.095613] wlo1: send auth to cc:ab:2c:5c:6d:e4 (try 1/3) [ 182.099011] wlo1: authenticated [ 182.100338] wlo1: associate with cc:ab:2c:5c:6d:e4 (try 1/3) [ 182.105996] wlo1: RX AssocResp from cc:ab:2c:5c:6d:e4 (capab=0x411 status=0 aid=14) [ 182.106228] wlo1: associated [ 182.180441] wlo1: Limiting TX power to 30 (30 - 0) dBm as advertised by cc:ab:2c:5c:6d:e4 [ 182.224512] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready Code: Select all$ sudo nmcli general logging level TRACE domains ALL $ systemctl restart NetworkManager.service $ journalctl -u NetworkManager.service # I am new to the forum, so I'm not sure if I'm using pastebin correctly [url]https://forums.debian.net/app.php/pastebin/?mode=view&s=106[/url] | lugnuts wrote: 2024-06-18 02:45 Code: Select all$ lspci -nnk | grep -iA2 net 08:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter [10ec:8179] (rev 01) DeviceName: Realtek RTL8188EE 802.11bgn Wi-Fi Adapter Subsystem: Hewlett-Packard Company RTL8188EE mini-PCIe card [103c:197d] Several posts recommend setting the rtl8188ee kernel module to switch to antenna #2, but current module does not have a parameter for this. Ideas? What you found is related to a different chipset: rtl8723be, not rtl8188ee. lugnuts wrote: 2024-06-18 02:45 P.S. With each new fresh install or live ISO, the connection works fine for hours or days, and then fails more and more often, until the wifi will not find any networks where there are plenty available -- as if something "builds up" toward failure. Thanks for any insights! In the excerpt of system logs you sent, it seems that the wlo1 network interfaces perhaps tries to connect to a Wi-Fi Direct device and this perhaps disrupt the normal behaviour of the wireless interface adapter: Code: Select allMay 31 07:02:37 device (p2p-dev-wlo1): supplicant management interface state: associating -> 4way_handshake May 31 07:02:41 device (wlo1): supplicant interface state: 4way_handshake -> disconnected May 31 07:02:41 device (wlo1): Activation: (wifi) disconnected during association, asking for new key May 31 07:02:41 device (wlo1): state change: config -> need-auth (reason 'supplicant-disconnect', sys-iface-state: 'managed') May 31 07:02:41 device (p2p-dev-wlo1): supplicant management interface state: 4way_handshake -> disconnected May 31 07:02:41 device (wlo1): supplicant interface state: disconnected -> inactive Check network manager for this p2p-dev-wlo1 connection. You need to connect using wlo1 device and not p2p-dev-wlo1 device. Hope this helps. --- notes: 1) moved to "Hardware" sub-forum. 2) please add the chipset name to the subject of the first post, e.g.: RealTek RTL8188EEWifi NIC fails on Bookworm, Derivatives, Arch |
Hi, In Chromium I have sound but not in Firefox. I am using Debian 12. ``` Code: Select all$ uname -a Linux macbookair 6.1.0-23-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.99-1 (2024-07-15) x86_64 GNU/Linux ``` ``` $ sudo lspci -k | grep -A 4 Audio [sudo] password for mtl: 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Apple Inc. Broadwell-U Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) Subsystem: Intel Corporation Wildcat Point-LP USB xHCI Controller -- 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Intel Corporation Wildcat Point-LP High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) Subsystem: Intel Corporation Wildcat Point-LP PCI Express Root Port ``` ``` $ pulseaudio -D E: [pulseaudio] main.c: Daemon startup failed. ``` ``` $ pgrep -a pulse 1364 /usr/bin/pulseaudio --daemonize=no --log-target=journal ``` ``` mtl@macbookair:~$ speaker-test --nloops 1 speaker-test 1.2.8 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 192 to 2097152 Period size range from 64 to 699051 Using max buffer size 2097152 Periods = 4 was set period_size = 524288 was set buffer_size = 2097152 0 - Front Left ``` Sound came out. What did I miss? Thank you in advance. | Use code tags for terminal text and errors etc. please. Fixed it for you this time. |
Since March 2019 I am using a donated Fujitsu-Siemens Lifebook e781 vPro as my device for work. I even managed to install more RAM on it than it is supposed to support. I have 12 GB instead if 8. And the device is working well so far. Recently I bought a used SATA ADATA XPG SX900 512 GB SSD and I wanted to use it as a replacement for my old HDD. I would expect it to make the system boot and loading applications considerably faster. Unfortunately, the SDD doesn't even get recognized in the bios. I found a guide detailing how one could approach this issue. And one of the first steps is to upgrade the bios so that it can recognize newer SSDs. I do have version 1.18 from 2012 while the newest available version would be 1.23 from 2017. Unfortunately, Fujitsu provides only an .exe file for older Windows versions and none for GNU/Linux. Is it even possible to upgrade the bios of this device on Debian? Or would it be easiest to look for a cheap used Windows system with a hard disk I could temporarily plug into this laptop for the bios upgrade? I need to admit that there is some doubt that the SSD is working despite the seller claiming that he used it before without any issues. I tried putting it in three different systems and none was able to recognize it. But I figure an updated bios in my laptop couldn't hurt anyway ... | Hello, As per specifications, your SSD is reported as a SATA III. In the computer's review you sent, it is reported that a SATA II was tested. Did you check the maximum speed of the computer's SATA interface ? You can probably verify checking system logs with the following command: Code: Select allsudo journalctl -b -g sata |
Hello fellow debian users! I've recently acquired a laptop from PCSpecialist (custom build laptop) that has an integrated Intel Tiger Lake-LP Smart Sound Audio card. only it doesn't work a all on debian. I'm dual booting the lapop with windows 10(where it works fine) and debian with KDE Plasma and settings don't show any audio output devices. Also an error at boot goes Code: Select all"firmware: failed to load intel/sof/sof-tgl.ri" inxi shows: Code: Select allinxi -A Audio: Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: sof-audio-pci Sound Server: ALSA v: k5.10.0-16-amd64 Kernel Log related to audio: Code: Select allsudo cat /var/log/kern.log | grep audio Jul 28 11:38:12 victor kernel: [ 4.070747] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 11:38:12 victor kernel: [ 4.070774] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 11:38:12 victor kernel: [ 4.070795] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 11:38:12 victor kernel: [ 4.071112] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 11:38:12 victor kernel: [ 4.071272] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 11:38:12 victor kernel: [ 4.117127] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 11:38:12 victor kernel: [ 4.205946] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 11:38:12 victor kernel: [ 4.205949] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 11:38:12 victor kernel: [ 4.205955] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 11:38:12 victor kernel: [ 4.205992] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 11:38:12 victor kernel: [ 4.206054] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 11:38:12 victor kernel: [ 4.206058] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 11:38:12 victor kernel: [ 4.206116] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 11:38:12 victor kernel: [ 4.206534] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 11:56:36 victor kernel: [ 4.331901] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 11:56:36 victor kernel: [ 4.331931] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 11:56:36 victor kernel: [ 4.331949] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 11:56:36 victor kernel: [ 4.341863] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 11:56:36 victor kernel: [ 4.342062] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 11:56:36 victor kernel: [ 4.372631] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 11:56:36 victor kernel: [ 4.422012] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 11:56:36 victor kernel: [ 4.422015] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 11:56:36 victor kernel: [ 4.422025] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 11:56:36 victor kernel: [ 4.422061] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 11:56:36 victor kernel: [ 4.423888] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 11:56:36 victor kernel: [ 4.423894] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 11:56:36 victor kernel: [ 4.425678] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 11:56:36 victor kernel: [ 4.429304] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 12:13:19 victor kernel: [ 3.760824] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 12:13:19 victor kernel: [ 3.760852] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 12:13:19 victor kernel: [ 3.760873] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 12:13:19 victor kernel: [ 3.761172] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 12:13:19 victor kernel: [ 3.761321] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 12:13:19 victor kernel: [ 3.767840] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 12:13:19 victor kernel: [ 3.825813] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 12:13:19 victor kernel: [ 3.825816] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 12:13:19 victor kernel: [ 3.825821] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 12:13:19 victor kernel: [ 3.825855] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 12:13:19 victor kernel: [ 3.825859] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 12:13:19 victor kernel: [ 3.825862] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 12:13:19 victor kernel: [ 3.825865] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 12:13:19 victor kernel: [ 3.826183] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 12:22:35 victor kernel: [ 4.373075] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 12:22:35 victor kernel: [ 4.373100] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 12:22:35 victor kernel: [ 4.373113] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 12:22:35 victor kernel: [ 4.373370] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 12:22:35 victor kernel: [ 4.373526] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 12:22:35 victor kernel: [ 4.380137] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 12:22:35 victor kernel: [ 4.442094] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 12:22:35 victor kernel: [ 4.442097] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 12:22:35 victor kernel: [ 4.442101] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 12:22:35 victor kernel: [ 4.442124] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 12:22:35 victor kernel: [ 4.442127] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 12:22:35 victor kernel: [ 4.442129] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 12:22:35 victor kernel: [ 4.442130] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 12:22:35 victor kernel: [ 4.442363] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 12:32:38 victor kernel: [ 4.431648] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 12:32:38 victor kernel: [ 4.431670] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 12:32:38 victor kernel: [ 4.431688] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 12:32:38 victor kernel: [ 4.431969] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 12:32:38 victor kernel: [ 4.432142] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 12:32:38 victor kernel: [ 4.438928] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 12:32:38 victor kernel: [ 4.546227] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 12:32:38 victor kernel: [ 4.546230] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 12:32:38 victor kernel: [ 4.546236] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 12:32:38 victor kernel: [ 4.546402] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 12:32:38 victor kernel: [ 4.546406] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 12:32:38 victor kernel: [ 4.546409] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 12:32:38 victor kernel: [ 4.546412] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 12:32:38 victor kernel: [ 4.562622] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 13:15:21 victor kernel: [ 4.370269] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 13:15:21 victor kernel: [ 4.370290] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 13:15:21 victor kernel: [ 4.370302] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 13:15:21 victor kernel: [ 4.370545] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 13:15:21 victor kernel: [ 4.370650] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 13:15:21 victor kernel: [ 4.377087] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 13:15:21 victor kernel: [ 4.442289] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 13:15:21 victor kernel: [ 4.442291] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 13:15:21 victor kernel: [ 4.442296] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 13:15:21 victor kernel: [ 4.442388] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 13:15:21 victor kernel: [ 4.442391] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 13:15:21 victor kernel: [ 4.442394] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 13:15:21 victor kernel: [ 4.442395] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 13:15:21 victor kernel: [ 4.452395] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 13:45:11 victor kernel: [ 4.345703] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 13:45:11 victor kernel: [ 4.345723] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 13:45:11 victor kernel: [ 4.345743] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 13:45:11 victor kernel: [ 4.345973] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 13:45:11 victor kernel: [ 4.354430] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 13:45:11 victor kernel: [ 4.360853] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 13:45:11 victor kernel: [ 4.425538] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 13:45:11 victor kernel: [ 4.425541] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 13:45:11 victor kernel: [ 4.425545] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 13:45:11 victor kernel: [ 4.425668] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 13:45:11 victor kernel: [ 4.425673] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 13:45:11 victor kernel: [ 4.425676] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 13:45:11 victor kernel: [ 4.425678] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 13:45:11 victor kernel: [ 4.425984] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 20:40:56 victor kernel: [ 4.323465] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 20:40:56 victor kernel: [ 4.323494] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 20:40:56 victor kernel: [ 4.323510] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 20:40:56 victor kernel: [ 4.324058] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 20:40:56 victor kernel: [ 4.324176] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 20:40:56 victor kernel: [ 4.330973] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 20:40:56 victor kernel: [ 4.349104] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 20:40:56 victor kernel: [ 4.349106] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 20:40:56 victor kernel: [ 4.349111] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 20:40:56 victor kernel: [ 4.349135] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 20:40:56 victor kernel: [ 4.349138] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 20:40:56 victor kernel: [ 4.349141] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 20:40:56 victor kernel: [ 4.349142] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 20:40:56 victor kernel: [ 4.349392] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 20:43:38 victor kernel: [ 4.054450] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 20:43:38 victor kernel: [ 4.054472] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 20:43:38 victor kernel: [ 4.054494] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 20:43:38 victor kernel: [ 4.054766] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 20:43:38 victor kernel: [ 4.054926] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 20:43:38 victor kernel: [ 4.061262] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 20:43:38 victor kernel: [ 4.096463] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 20:43:38 victor kernel: [ 4.096466] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 20:43:38 victor kernel: [ 4.096471] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 20:43:38 victor kernel: [ 4.096501] sof-audio-pci 0000:00:1f.3: firmware: failed to load intel/sof/sof-tgl.ri (-2) Jul 28 20:43:38 victor kernel: [ 4.096558] sof-audio-pci 0000:00:1f.3: Direct firmware load for intel/sof/sof-tgl.ri failed with error -2 Jul 28 20:43:38 victor kernel: [ 4.096561] sof-audio-pci 0000:00:1f.3: error: request firmware intel/sof/sof-tgl.ri failed err: -2 Jul 28 20:43:38 victor kernel: [ 4.096614] sof-audio-pci 0000:00:1f.3: error: failed to load DSP firmware -2 Jul 28 20:43:38 victor kernel: [ 4.096947] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -2 Jul 28 20:52:01 victor kernel: [ 4.091677] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 20:52:01 victor kernel: [ 4.091696] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 20:52:01 victor kernel: [ 4.091710] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 20:52:01 victor kernel: [ 4.092122] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 20:52:01 victor kernel: [ 4.092235] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 20:52:01 victor kernel: [ 4.099162] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 20:52:02 victor kernel: [ 4.157939] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 20:52:02 victor kernel: [ 4.157941] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 20:52:02 victor kernel: [ 4.157946] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 20:52:02 victor kernel: [ 4.158781] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof/sof-tgl.ri Jul 28 20:52:02 victor kernel: [ 4.158789] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 6 size 0x20 Jul 28 20:52:02 victor kernel: [ 4.158791] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 Jul 28 20:52:02 victor kernel: [ 4.158793] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 20:52:02 victor kernel: [ 4.158794] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel Jul 28 20:52:02 victor kernel: [ 4.158799] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 3 size 0x30 Jul 28 20:52:02 victor kernel: [ 4.158800] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 5 size 0x20 Jul 28 20:52:02 victor kernel: [ 4.258462] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 Jul 28 20:52:02 victor kernel: [ 4.258465] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 20:52:02 victor kernel: [ 4.258466] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel Jul 28 20:52:02 victor kernel: [ 4.262847] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-hda-generic-idisp-2ch.tplg Jul 28 20:52:02 victor kernel: [ 4.262853] sof-audio-pci 0000:00:1f.3: Topology: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 20:52:02 victor kernel: [ 4.262854] sof-audio-pci 0000:00:1f.3: warn: topology ABI is more recent than kernel Jul 28 20:52:02 victor kernel: [ 4.273118] sof-audio-pci 0000:00:1f.3: ASoC: Parent card not yet available, widget card binding deferred Jul 28 23:17:33 victor kernel: [ 4.288572] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 23:17:33 victor kernel: [ 4.288602] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 23:17:33 victor kernel: [ 4.288620] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 23:17:33 victor kernel: [ 4.289201] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 23:17:33 victor kernel: [ 4.289353] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 23:17:33 victor kernel: [ 4.296398] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 23:17:33 victor kernel: [ 4.405299] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 23:17:33 victor kernel: [ 4.405303] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 23:17:33 victor kernel: [ 4.405308] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 23:17:33 victor kernel: [ 4.406216] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof/sof-tgl.ri Jul 28 23:17:33 victor kernel: [ 4.406225] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 6 size 0x20 Jul 28 23:17:33 victor kernel: [ 4.406226] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 Jul 28 23:17:33 victor kernel: [ 4.406229] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 23:17:33 victor kernel: [ 4.406230] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel Jul 28 23:17:33 victor kernel: [ 4.406235] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 3 size 0x30 Jul 28 23:17:33 victor kernel: [ 4.406237] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 5 size 0x20 Jul 28 23:17:33 victor kernel: [ 4.493835] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 Jul 28 23:17:33 victor kernel: [ 4.493836] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 23:17:33 victor kernel: [ 4.493837] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel Jul 28 23:17:33 victor kernel: [ 4.770971] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-hda-generic-idisp-2ch.tplg Jul 28 23:17:33 victor kernel: [ 4.770981] sof-audio-pci 0000:00:1f.3: Topology: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 23:17:33 victor kernel: [ 4.770981] sof-audio-pci 0000:00:1f.3: warn: topology ABI is more recent than kernel Jul 28 23:17:33 victor kernel: [ 4.781128] sof-audio-pci 0000:00:1f.3: ASoC: Parent card not yet available, widget card binding deferred Jul 28 23:54:31 victor kernel: [ 4.409214] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 28 23:54:31 victor kernel: [ 4.409240] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 28 23:54:31 victor kernel: [ 4.409261] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 28 23:54:31 victor kernel: [ 4.409567] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 28 23:54:31 victor kernel: [ 4.409708] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 28 23:54:31 victor kernel: [ 4.417882] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 28 23:54:31 victor kernel: [ 4.484896] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 28 23:54:31 victor kernel: [ 4.484899] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 28 23:54:31 victor kernel: [ 4.484903] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 28 23:54:31 victor kernel: [ 4.485679] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof/sof-tgl.ri Jul 28 23:54:31 victor kernel: [ 4.485686] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 6 size 0x20 Jul 28 23:54:31 victor kernel: [ 4.485687] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 Jul 28 23:54:31 victor kernel: [ 4.485688] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 23:54:31 victor kernel: [ 4.485689] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel Jul 28 23:54:31 victor kernel: [ 4.485692] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 3 size 0x30 Jul 28 23:54:31 victor kernel: [ 4.485693] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 5 size 0x20 Jul 28 23:54:31 victor kernel: [ 4.573057] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 Jul 28 23:54:31 victor kernel: [ 4.573060] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 23:54:31 victor kernel: [ 4.573061] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel Jul 28 23:54:31 victor kernel: [ 4.693819] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-hda-generic-idisp-2ch.tplg Jul 28 23:54:31 victor kernel: [ 4.693830] sof-audio-pci 0000:00:1f.3: Topology: ABI 3:18:1 Kernel ABI 3:17:0 Jul 28 23:54:31 victor kernel: [ 4.693830] sof-audio-pci 0000:00:1f.3: warn: topology ABI is more recent than kernel Jul 28 23:54:31 victor kernel: [ 4.704649] sof-audio-pci 0000:00:1f.3: ASoC: Parent card not yet available, widget card binding deferred Jul 29 08:27:50 victor kernel: [ 3.855704] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 Jul 29 08:27:50 victor kernel: [ 3.855733] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver Jul 29 08:27:50 victor kernel: [ 3.855755] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002) Jul 29 08:27:50 victor kernel: [ 3.856057] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 Jul 29 08:27:50 victor kernel: [ 3.856206] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Jul 29 08:27:50 victor kernel: [ 3.863430] sof-audio-pci 0000:00:1f.3: use msi interrupt mode Jul 29 08:27:50 victor kernel: [ 3.929861] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 4 Jul 29 08:27:50 victor kernel: [ 3.929864] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now Jul 29 08:27:50 victor kernel: [ 3.929869] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2 Jul 29 08:27:50 victor kernel: [ 3.930782] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof/sof-tgl.ri Jul 29 08:27:50 victor kernel: [ 3.930798] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 6 size 0x20 Jul 29 08:27:50 victor kernel: [ 3.930799] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 Jul 29 08:27:50 victor kernel: [ 3.930801] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 Jul 29 08:27:50 victor kernel: [ 3.930802] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel Jul 29 08:27:50 victor kernel: [ 3.930806] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 3 size 0x30 Jul 29 08:27:50 victor kernel: [ 3.930808] sof-audio-pci 0000:00:1f.3: warning: unknown sof_ext_man header type 5 size 0x20 Jul 29 08:27:50 victor kernel: [ 4.017975] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:7:0-47d07 Jul 29 08:27:50 victor kernel: [ 4.017979] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:18:1 Kernel ABI 3:17:0 Jul 29 08:27:50 victor kernel: [ 4.017981] sof-audio-pci 0000:00:1f.3: warn: FW ABI is more recent than kernel Jul 29 08:27:51 victor kernel: [ 4.166645] sof-audio-pci 0000:00:1f.3: firmware: direct-loading firmware intel/sof-tplg/sof-hda-generic-idisp-2ch.tplg Jul 29 08:27:51 victor kernel: [ 4.166657] sof-audio-pci 0000:00:1f.3: Topology: ABI 3:18:1 Kernel ABI 3:17:0 Jul 29 08:27:51 victor kernel: [ 4.166658] sof-audio-pci 0000:00:1f.3: warn: topology ABI is more recent than kernel Jul 29 08:27:51 victor kernel: [ 4.176926] sof-audio-pci 0000:00:1f.3: ASoC: Parent card not yet available, widget card binding deferred I've already installed the file that's seemingly missing : Code: Select allls -la /lib/firmware/intel/sof/ total 1232 drwxr-xr-x 4 root root 4096 Jul 29 08:40 . drwxr-xr-x 4 root root 4096 Jul 28 20:51 .. drwxr-xr-x 2 root root 4096 Jul 28 20:51 community drwxr-xr-x 2 root root 4096 Jul 28 20:51 intel-signed -rw-r--r-- 1 root root 84176 Apr 6 2021 sof-apl.ldc lrwxrwxrwx 1 root root 23 Jun 13 2021 sof-apl.ri -> intel-signed/sof-apl.ri -rw-r--r-- 1 root root 60828 Apr 6 2021 sof-bdw.ldc -rw-r--r-- 1 root root 141296 Apr 6 2021 sof-bdw.ri -rw-r--r-- 1 root root 35716 Apr 6 2021 sof-byt.ldc -rw-r--r-- 1 root root 212544 Apr 6 2021 sof-byt.ri lrwxrwxrwx 1 root root 11 Jun 13 2021 sof-cfl.ldc -> sof-cnl.ldc lrwxrwxrwx 1 root root 23 Jun 13 2021 sof-cfl.ri -> intel-signed/sof-cfl.ri -rw-r--r-- 1 root root 35716 Apr 6 2021 sof-cht.ldc -rw-r--r-- 1 root root 213216 Apr 6 2021 sof-cht.ri lrwxrwxrwx 1 root root 11 Jun 13 2021 sof-cml.ldc -> sof-cnl.ldc lrwxrwxrwx 1 root root 23 Jun 13 2021 sof-cml.ri -> intel-signed/sof-cml.ri -rw-r--r-- 1 root root 88152 Apr 6 2021 sof-cnl.ldc lrwxrwxrwx 1 root root 23 Jun 13 2021 sof-cnl.ri -> intel-signed/sof-cnl.ri lrwxrwxrwx 1 root root 11 Jun 13 2021 sof-ehl.ldc -> sof-tgl.ldc lrwxrwxrwx 1 root root 23 Jun 13 2021 sof-ehl.ri -> intel-signed/sof-ehl.ri lrwxrwxrwx 1 root root 11 Jun 13 2021 sof-glk.ldc -> sof-apl.ldc lrwxrwxrwx 1 root root 23 Jun 13 2021 sof-glk.ri -> intel-signed/sof-glk.ri -rw-r--r-- 1 root root 87320 Apr 6 2021 sof-icl.ldc lrwxrwxrwx 1 root root 23 Jun 13 2021 sof-icl.ri -> intel-signed/sof-icl.ri -rw-r--r-- 1 root root 87320 Apr 6 2021 sof-jsl.ldc lrwxrwxrwx 1 root root 23 Jun 13 2021 sof-jsl.ri -> intel-signed/sof-jsl.ri -rw-r--r-- 1 root root 87688 Apr 6 2021 sof-tgl-h.ldc lrwxrwxrwx 1 root root 25 Jun 13 2021 sof-tgl-h.ri -> intel-signed/sof-tgl-h.ri -rw-r--r-- 1 root root 87688 Apr 6 2021 sof-tgl.ldc lrwxrwxrwx 1 root root 23 Jul 29 08:40 sof-tgl.ri -> intel-signed/sof-tgl.ri Any Ideas on how I can fix this??? | Code: Select allsof-tgl.ri is in Code: Select allfirmware-sof-signed Did you install that? Sorry -just had time for a quick look - may have missed something. Edit: I missed sof-tgl.ri in the list of files you posted, so obviously you installed the firmware. Do you also have Code: Select allalsa-ucm-conf ? I see mention of Skylake platform so you may need: Code: Select allfirmware-intel-sound Code: Select alloptions snd-intel-dspcfg dsp_driver=1 May work. https://bbs.archlinux.org/viewtopic.php?id=260139 For more info see: https://thesofproject.github.io/latest/ ... ction.html Edit 2: the latest kernel from backports might help too. |
Hello, System was just updated from 12.6 to 12.7 and now have no sound. Have tested various applications and also speaker and headphones. Sound works with same hardware using Windows. Is there anything which is needful after performing the update? Everything is vanilla Gnome install, did not need to do anything to get sound working when initially installed Debian. Code: Select all% inxi -Fxxxmprz | grep -A 9 'Audio:' Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403 Device-2: NVIDIA GM204 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fbb class-ID: 0403 API: ALSA v: k6.1.0-25-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin Code: Select all% lspci | grep -i audio 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31) 01:00.1 Audio device: NVIDIA Corporation GM204 High Definition Audio Controller (rev a1) Code: Select all% sudo dmesg | grep 'snd\|firmware\|audio' [ 1.349667] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/acr/bl.bin [ 1.349681] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/acr/ucode_load.bin [ 1.349693] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/acr/bl.bin [ 1.349703] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/acr/ucode_unload.bin [ 1.349706] nouveau 0000:01:00.0: pmu: firmware unavailable [ 1.349810] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/fecs_bl.bin [ 1.349824] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/fecs_inst.bin [ 1.349847] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/fecs_data.bin [ 1.349856] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/fecs_sig.bin [ 1.349869] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/gpccs_bl.bin [ 1.349881] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/gpccs_inst.bin [ 1.349889] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/gpccs_data.bin [ 1.349898] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/gpccs_sig.bin [ 1.349910] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/sw_nonctx.bin [ 1.349925] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/sw_ctx.bin [ 1.349938] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/sw_bundle_init.bin [ 1.349952] nouveau 0000:01:00.0: firmware: direct-loading firmware nvidia/gm204/gr/sw_method_init.bin [ 1.452596] ata5.00: Features: Trust Dev-Sleep NCQ-sndrcv [ 3.636829] platform regulatory.0: firmware: direct-loading firmware regulatory.db [ 3.636977] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s [ 3.638494] snd_hda_intel 0000:01:00.1: Disabling MSI [ 3.638500] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client [ 3.661679] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau]) [ 3.663744] snd_hda_codec_ca0132 hdaudioC0D0: autoconfig for Recon3Di: line_outs=3 (0xb/0x11/0x10/0x0/0x0) type:line [ 3.663758] snd_hda_codec_ca0132 hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 3.663761] snd_hda_codec_ca0132 hdaudioC0D0: hp_outs=1 (0xf/0x0/0x0/0x0/0x0) [ 3.663763] snd_hda_codec_ca0132 hdaudioC0D0: mono: mono_out=0x0 [ 3.663764] snd_hda_codec_ca0132 hdaudioC0D0: dig-out=0xc/0xd [ 3.663766] snd_hda_codec_ca0132 hdaudioC0D0: inputs: [ 3.663767] snd_hda_codec_ca0132 hdaudioC0D0: Mic=0x12 [ 3.663769] snd_hda_codec_ca0132 hdaudioC0D0: Line=0x13 [ 3.680370] snd_hda_intel 0000:00:1f.3: firmware: failed to load ctefx-r3di.bin (-2) [ 3.680384] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 3.680401] snd_hda_intel 0000:00:1f.3: firmware: failed to load ctefx-r3di.bin (-2) [ 3.680408] snd_hda_intel 0000:00:1f.3: Direct firmware load for ctefx-r3di.bin failed with error -2 [ 3.690487] snd_hda_intel 0000:00:1f.3: firmware: direct-loading firmware ctefx.bin [ 4.332842] snd_hda_codec_ca0132 hdaudioC0D0: ca0132 DSP downloaded and running I am new to linux but from the message it could need firmware update although this could be a furphy as the only change was going to Debian 12.7 and I couldn't see anything of note in changelog https://deb.debian.org/debian/dists/bookworm/ChangeLog but I may have missed something? | Hello, You can see this previous discussion about missing firmware (even if about Debian 11): [Solved] Audio card driver problems Debian 11 (Creative Sound Blaster Recon3Di). Hope this helps. |
One of our staff members bought an Asus Zenbook 14 Q425M for home use. We tested it with Debian Testing Live USB (weekly build, 09/09/2024). Things are not as smooth as our other office computers (all of which are AMD based), but we finally got it to work. One exception was that there is no sound from the build-in speakers. Sounds from the usb-C port and the headphone jack are OK. Lspci shows that the sound card is part of Intel's Meteor Lake chip, and a quick and dirty internet search shows that no Linux driver is yet available. Bummer. We may have to return this laptop? ? ? (The beauty with using a live usb is that we don't have to touch the Windows thus the machine is in a return-ready condition.) | Upgraded from Testing to Sid (and Linux kernel to 6.10.9), sound started coming out from the speakers. But after a reboot, we lost sound again. Since the usb-c port works, we may decide to keep it. This is actually a pretty good machine. |
hello, I'm trying to get Bluetooth to work, to no avail. So I ask for help. Code: Select all~$ inxi -E Bluetooth: Device-1: IMC Networks Wireless_Device type: USB driver: btusb Report: hciconfig ID: hci0 rfk-id: 2 state: down bt-service: enabled,running rfk-block: hardware: no software: no address: 00:00:00:00:00:00 ~$ bluetoothctl Agent registered [bluetooth]# show No default controller available # rfkill list all .......... 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: hci0: Bluetooth Soft blocked: no Hard blocked: no # dkms status rtl8821au/5.12.5.2, 6.1.0-25-amd64, x86_64: installed # dmesg -l err [ 6.578462] Bluetooth: hci0: Opcode 0x0c03 failed: -110 I've uploaded more relevant information about my installation at https://linux-hardware.org/?probe=5fd39b626d. If I read the line about Bluetooth, it says about the "btusb" driver: "detected" but "this device model is known to have problems". Could this be why I can't get Bluetooth to work? ps-1: Is this file called Generic Bluetooth USB driver https://github.com/torvalds/linux/blob/ ... th/btusb.c useful? If so, how can I install a driver from this type of file? ps-2: this module is already loaded: Code: Select all~# lsmod | grep bluetooth bluetooth 958464 13 btrtl,btmtk,btintel,btbcm,bnep,btusb | for Debian 12, the https://linux-hardware.org/?id=usb:13d3-3579 site reports that two installations "work". Both use a kernel from Backports Repository (6.5* series). So I installed version 6.10. Bluetooth still doesn't work. ps1: most likely, my adapter is not supported by Debian 12. I'll wait for an update that will do the trick. ps2: the adapter I bought is a TP-Link AC600 T2U nano, not a TP-Link AC600 T2UB nano as I thought, so no Bluetooth available. |
I did an in-place upgrade from Debian 11.11 to 12.7. One issue that occurred was no sound devices being seen in KDE anymore. I dual boot, and the sound continues to work in Windows, so this is not a hardware issue. My user is in the audio group. I removed ~/.config/pulse but that did nothing; it was regenerated and I rebooted, still no sound. Aplay will list the desired device, but it will not play the test file. I would like the audio to play from the Realtek ALCS1200A device. Looking at https://wiki.debian.org/ALSA#Wrong_card_used_by_default I'm not sure what entries I would use to specify the device order, or if that's even what I would need to do to fix it. Some command output that may be helpful: Code: Select alljoebob@DESKTOP-300RKCR:~$ cat /proc/asound/cards 0 [NVidia ]: HDA-Intel - HDA NVidia HDA NVidia at 0xf7080000 irq 110 1 [Generic ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xf7a00000 irq 112 2 [C920 ]: USB-Audio - HD Pro Webcam C920 HD Pro Webcam C920 at usb-0000:0b:00.3-4, high speed joebob@DESKTOP-300RKCR:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HP ZR2440w] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 7: HDMI 1 [DELL S2522HG] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 0: ALCS1200A Analog [ALCS1200A Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 joebob@DESKTOP-300RKCR:~$ inxi -SAGxz System: Kernel: 6.1.0-25-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: KDE Plasma v: 5.27.5 Distro: Debian GNU/Linux 12 (bookworm) Graphics: Device-1: NVIDIA GA102 [GeForce RTX 3080 Lite Hash Rate] driver: nvidia v: 535.183.01 arch: Ampere bus-ID: 09:00.0 Device-2: Logitech C920 PRO HD Webcam type: USB driver: snd-usb-audio,uvcvideo bus-ID: 5-4:5 Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 driver: X: loaded: nvidia gpu: nvidia resolution: 1: 1920x1200~60Hz 2: 1920x1080~60Hz API: OpenGL v: 4.6.0 NVIDIA 535.183.01 renderer: NVIDIA GeForce RTX 3080/PCIe/SSE2 direct-render: Yes Audio: Device-1: NVIDIA GA102 High Definition Audio driver: snd_hda_intel v: kernel bus-ID: 5-4:5 Device-2: AMD Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 0b:00.4 Device-3: Logitech C920 PRO HD Webcam type: USB driver: snd-usb-audio,uvcvideo API: ALSA v: k6.1.0-25-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active Server-2: PulseAudio v: 16.1 status: off (using pipewire-pulse) joebob@DESKTOP-300RKCR:~$ aplay /usr/share/sounds/alsa/Front_Right.wav Playing WAVE '/usr/share/sounds/alsa/Front_Right.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono ALSA lib pcm_pulse.c:758:(pulse_prepare) PulseAudio: Unable to create stream: Timeout aplay: set_params:1416: Unable to install hw params: ACCESS: RW_INTERLEAVED FORMAT: S16_LE SUBFORMAT: STD SAMPLE_BITS: 16 FRAME_BITS: 16 CHANNELS: 1 RATE: 48000 PERIOD_TIME: 125000 PERIOD_SIZE: 6000 PERIOD_BYTES: 12000 PERIODS: 4 BUFFER_TIME: 500000 BUFFER_SIZE: 24000 BUFFER_BYTES: 48000 TICK_TIME: [0 0] | Use code tags for terminal text, errors etc. please. Fixed it for you this time. Sound can be tricky with multiple devices so one solution may not work while others might. Try going into the Configuration tab of pavucontrol and set the HDMI device to Off. Both the devices use snd_hda_intel driver so you can't specify default using that. Did you try the second option in that wiki link? Create a file /etc/modprobe.d/sound.conf with this content: Code: Select alloptions snd_hda_intel index=1,0 ^This one usually works for me. Default card may also be set by pressing F6 in alsamixer which is part of alsa-utils package. Edited: correct filename is sound.conf, not just sound as previously written.. |
Hello everyone, I'm Chris from Germany and I'm new to this forum. I just moved from Mint to Debian and I really love it so far, everything's running perfectly fine. I have one weird issue, though, and I hope you guys can explain what's going on: I have 2 bars of 8GB-DDR4-RAM on my system (slots 1 and 3), so a total of 16GB, same brand, same model. When I go to Gnome settings > info, it shows 16GB. When I do Code: Select allsudo dmidecode --type memory the output is: Code: Select allGetting SMBIOS data from sysfs. SMBIOS 2.8 present. Handle 0x0011, DMI type 16, 23 bytes Physical Memory Array Location: System Board Or Motherboard Use: System Memory Error Correction Type: None Maximum Capacity: 128 GB Error Information Handle: 0x0010 Number Of Devices: 4 Handle 0x0018, DMI type 17, 40 bytes Memory Device Array Handle: 0x0011 Error Information Handle: 0x0017 Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: Unknown Set: None Locator: DIMM 0 Bank Locator: P0 CHANNEL A Type: Unknown Type Detail: Unknown Handle 0x001A, DMI type 17, 40 bytes Memory Device Array Handle: 0x0011 Error Information Handle: 0x0019 Total Width: 64 bits Data Width: 64 bits Size: 8 GB Form Factor: DIMM Set: None Locator: DIMM 1 Bank Locator: P0 CHANNEL A Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2667 MT/s Manufacturer: Micron Technology Serial Number: 2F897838 Asset Tag: Not Specified Part Number: 4ATF1G64AZ-3G2E1 Rank: 1 Configured Memory Speed: 2667 MT/s Minimum Voltage: 1.2 V Maximum Voltage: 1.2 V Configured Voltage: 1.2 V Handle 0x001D, DMI type 17, 40 bytes Memory Device Array Handle: 0x0011 Error Information Handle: 0x001C Total Width: Unknown Data Width: Unknown Size: No Module Installed Form Factor: Unknown Set: None Locator: DIMM 0 Bank Locator: P0 CHANNEL B Type: Unknown Type Detail: Unknown Handle 0x001F, DMI type 17, 40 bytes Memory Device Array Handle: 0x0011 Error Information Handle: 0x001E Total Width: 64 bits Data Width: 64 bits Size: 8 GB Form Factor: DIMM Set: None Locator: DIMM 1 Bank Locator: P0 CHANNEL B Type: DDR4 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 2667 MT/s Manufacturer: Micron Technology Serial Number: 2F89760F Asset Tag: Not Specified Part Number: 4ATF1G64AZ-3G2E1 Rank: 1 Configured Memory Speed: 2667 MT/s Minimum Voltage: 1.2 V Maximum Voltage: 1.2 V Configured Voltage: 1.2 V And this is the output of lshw -C memory: Code: Select all*-firmware description: BIOS vendor: American Megatrends International, LLC. physical id: 0 version: M.H0 date: 07/26/2022 size: 64KiB capacity: 16MiB capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb biosbootspecification uefi *-memory description: System Memory physical id: 11 slot: System board or motherboard size: 16GiB *-bank:0 description: 2667 MHz (0,4 ns) [empty] product: Unknown vendor: Unknown physical id: 0 serial: Unknown slot: DIMM 0 clock: 2667MHz (0.4ns) *-bank:1 description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2667 MHz (0,4 ns) product: 4ATF1G64AZ-3G2E1 vendor: Micron Technology physical id: 1 serial: 2F897838 slot: DIMM 1 size: 8GiB width: 64 bits clock: 2667MHz (0.4ns) *-bank:2 description: 2667 MHz (0,4 ns) [empty] product: Unknown vendor: Unknown physical id: 2 serial: Unknown slot: DIMM 0 clock: 2667MHz (0.4ns) *-bank:3 description: DIMM DDR4 Synchronous Unbuffered (Unregistered) 2667 MHz (0,4 ns) product: 4ATF1G64AZ-3G2E1 vendor: Micron Technology physical id: 3 serial: 2F89760F slot: DIMM 1 size: 8GiB width: 64 bits clock: 2667MHz (0.4ns) *-cache:0 description: L1 cache physical id: 13 slot: L1 - Cache size: 576KiB capacity: 576KiB clock: 1GHz (1.0ns) capabilities: pipeline-burst internal write-back unified configuration: level=1 *-cache:1 description: L2 cache physical id: 14 slot: L2 - Cache size: 3MiB capacity: 3MiB clock: 1GHz (1.0ns) capabilities: pipeline-burst internal write-back unified configuration: level=2 *-cache:2 description: L3 cache physical id: 15 slot: L3 - Cache size: 16MiB capacity: 16MiB clock: 1GHz (1.0ns) capabilities: pipeline-burst internal write-back unified configuration: level=3 However, when I type in Code: Select allfree -h I get Code: Select all gesamt benutzt frei gemns. Puffer/Cache verfügbar Speicher: 7,7Gi 4,3Gi 716Mi 60Mi 3,0Gi 3,3Gi Swap: 3,3Gi 0B 3,3Gi Stacer also shows 7,7 GB, and so does top. And sudo dmesg | grep Memory gives me: Code: Select all[ 0.052579] Memory: 3014432K/8312428K available (14342K kernel code, 2332K rwdata, 9060K rodata, 2796K init, 17404K bss, 405404K reserved, 0K cma-reserved) [ 0.255768] x86/mm: Memory block size: 128MB I have no idea what's going on... no entries in grub-cmdline, the Windows-installation on the same system correctly reports 16GB of installed RAM. Do you have any ideas? Any help is appreciated, thanks in advance, Chris | Welcome to the forums, and I have no idea! I am curious why they are in 1+3 and not 0+2. The bios's I'm used to have channel, stripe, mirror, independent settings for the slots. It may matter? The correct placement should be 0+2 or 0+1 depending on channel mode, as far as I know. |
This really isn't a Debian specific question, but there are enough people here who know what they're talking about. Today, my old HP Pavillion desktop, about 11 years old, started something strange. I rebooted from my Debian testing to go into my Mint. I saw the shutdown sequence in Debian, as per normal, and the reboot target was reached. The usual HP screen that comes up, where you have a second or two to do the key dance to get into BIOS, didn't appear. The monitor just went blank and went to power saving mode, as idling. The GRUB2 menu did not show up, either. I just sat there, confused a bit, but heard that the computer was obviously doing things. The display resumed absolutely fine once, I assume, the GRUB timer reached zero and it defaulted to Debian, and the kernel load began. First, I thought I maybe missed the GRUB screen because I wasn't paying attention and it timed out into Debian, as it is set to do. I rebooted again from the display manager login screen, and then confirmed, I'm not getting any OEM hardware splash screen or GRUB menu, just a suspended monitor until kernel load. So, instead of the usual complaint about there being no video display when the kernel is up and when the display manager is loaded, I've got the opposite. The monitor powers down and is showing no signal after the kernel shuts down for a reset, and when the computer is powered up, booting, but prior to kernel loading. No BIOS screen can be seen, no OEM splash screen, no GRUB menu. As soon as the kernel starts loading, I'm in business. I'm using it right now to post here. Resume from suspend is fine, too. I tried the keyboard dance to get the BIOS up, and I probably succeeded, but I couldn't tell visually. The monitor was in suspend. I rebooted from there, and got back into Debian, no problem. Any ideas about what may be amiss? The GPU is integrated and Intel, and I haven't seen this in 11 years of using this computer. I did power down completely and unplug the system for a few minutes, to no avail. I'm using HDMI, if that's of any interest. I'll be looking around for other cables while I'm at it, to see if it's HDMI being a problem. | I'm marking this as solved. Resetting the monitor did nothing. I ended up turning the monitor off, and physically unplugging it for half an hour. All seems to be working, at least at this moment. The monitor is old. The computer is ancient. If I have to replace either or both, they owe my nothing. |
Hi, I have buy an Asus Vivobook X1704V, and I have trouble with keyboard. Like many people : keyboard work well in BIOS and GRUB. But don't work under Linux. I try first to install Mageia9 with 6.5 kernel. Then Debian Bookworm with 6.1 kernel, dans sid with 6.10 kernel => Same result, keyboard don't work. According to these posts https://forums.debian.net/viewtopic.php?t=157149 https://bbs.archlinux.org/viewtopic.php?id=291569 https://unix.stackexchange.com/question ... linux-mint https://bbs.archlinux.org/viewtopic.php?id=277260 (Yes, very common problem, but no common solution) I disable "fast/quick startup" in Bios. I try some options to kernel, like i8042.reset i8042.nomux pnpacpi=off i8042.dumbkbd Some keys work : Fn with brightness, micro, backligth and calc And, i can see some output with "tail -f /dev/input/event0" only on these some keys. The only option which seems to do something is i8042.dumbkbd : with this option MajLocks led is off, and dmesg don't return atkbd error (atkbd serio0: keyboard reset failed on isa0060/serio0) Without this option MajLocks led is on and dmesg return the atkbd error. Best dmesg output : Code: Select all# dmesg |grep -C 2 serio [ 0.923993] i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 [ 0.923997] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp [ 0.925117] serio: i8042 KBD port at 0x60,0x64 irq 1 [ 0.925276] mousedev: PS/2 mouse device common for all mice [ 0.925293] rtc_cmos rtc_cmos: RTC can wake from S4 [ 0.926107] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 The only solution that I don't test is kernel Patch ( https://forums.debian.net/viewtopic.php?t=157149 ), because this patch is for kernel 6.1.49 ans don't apply to kernel 6.10 and this patch is for E1504GA computer, not for X1704V. I don't know how to modify this patch to adapt to PC and kernel. Can you help me with this problem ? Thank you. | Hello, Thanks for sharing your solution. I would suggest to open a bug report on the Debian Bug Tracking System for the involved kernel version attaching a working patch. Please send the reference to the bug number in a follow up message, if you do so. The patch might be included in Debian patches or forwarded upstream by Debian kernel maintainers. Hope this help. |
Hi everyone...here's the thing. I have a server running Openmediavault (a NAS interface for Debian) where I installed a Thunderbolt card. I configured the network interface, connected it directly to a MacBook via cable, bridged it, it works fine, I load the shares from the server via SMB, transfer super fast, everything works great. But...when I boot or turn off the Mac, the TB interface on the server disappears, and when I turn it back on it doesn't reappear. I discovered that when I turn off the server (not just boot it up) the interface reappears and everything works again...any idea what this could be? I'm lost here, and I don't want to keep turning the server on and off every time I close the Mac! Thanks for any help! BOLTCL shows: boltctl info 19408780-00e3-286c-ffff-ffffffffffff ● GIGABYTE GC-MAPLE RIDGE ├─ type: host ├─ name: GC-MAPLE RIDGE ├─ vendor: GIGABYTE ├─ uuid: 19408780-00e3-286c-ffff-ffffffffffff ├─ dbus path: /org/freedesktop/bolt/devices/19408780_00e3_286c_ffff_ffffffffffff ├─ generation: USB4 ├─ status: authorized │ ├─ domain: 19408780-00e3-286c-ffff-ffffffffffff │ ├─ parent: (null) │ ├─ syspath: /sys/devices/pci0000:00/0000:00:1c.4/0000:06:00.0/0000:07:00.0/0000:08:00.0/domain0/0-0 │ └─ authflags: none ├─ authorized: Fri 09 Aug 2024 08:23:45 PM UTC ├─ connected: Fri 09 Aug 2024 08:23:45 PM UTC └─ stored: no | Hello, andyvs wrote: 2024-08-10 18:25 Hi everyone...here's the thing. I have a server running Openmediavault (a NAS interface for Debian) where I installed a Thunderbolt card. I configured the network interface, connected it directly to a MacBook via cable, bridged it, it works fine, I load the shares from the server via SMB, transfer super fast, everything works great. But...when I boot or turn off the Mac, the TB interface on the server disappears, and when I turn it back on it doesn't reappear. I discovered that when I turn off the server (not just boot it up) the interface reappears and everything works again...any idea what this could be? I'm lost here, and I don't want to keep turning the server on and off every time I close the Mac! What is your Debian version ? What is the installed kernel version ? What is the Openmediavault version ? Can you please elaborate on the hardware connections between the server and the MacBook ? What is connected to the thunderbolt port ? What is the manufacturer and model of the thunderbolt interface ? Have you searched system logs for messages about the appearing and disappearing thunderbolt interface ? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.