Re: Thinkpad T14 Gen 5, touchpad not detected
> I just installed Debian Testing on my new Thinkpad T14 Gen 5 and I found out > that the touchpad is not actually detected by the system. Maybe it's the same issue as the one posted very recently under the subject: Touchpad not detected by kernel on ThinkPad X13 Gen5 - Stefan
Re: Thinkpad T14 Gen 5, touchpad not detected
On Sun, 9 Jun 2024 06:51:00 +0200 Timothée Jaussoin wrote: > Is there something in particular I should look for ? > I would look for some of the identifiers in those dmsg lines you showed earlier. See if the touchpad was detected but rejected. That migh give you a clue as to why it was rejected. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Thinkpad T14 Gen 5, touchpad not detected
Is there something in particular I should look for ?
Re: Thinkpad T14 Gen 5, touchpad not detected
On Sat, 8 Jun 2024 22:17:49 +0200 Timothée Jaussoin wrote: > If you need some more information I'd be pleased to share whatever is > required :) You might look at the installation logs. /var/log/installer/ -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Thinkpad T14 Gen 5, touchpad not detected
Hi, I just installed Debian Testing on my new Thinkpad T14 Gen 5 and I found out that the touchpad is not actually detected by the system. I have nothing in dmesg or xinput. However it is fully functional in other Live USB distros (Fedora and Ubuntu LTS 24.04, they have the same 6.8 Linux kernel). Here is my current hardware https://linux-hardware.org/?probe=13318ed64a Here is the dmesg in Fedora: [ 5.398935] input: ELAN0676:00 04F3:3195 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN0676:00/0018:04F3:3195.0001/input/input8 [ 5.480290] input: ELAN0676:00 04F3:3195 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-0/i2c-ELAN0676:00/0018:04F3:3195.0001/input/input11 I don't have those lines in my Debian dmesg. If you need some more information I'd be pleased to share whatever is required :) Regards, edhelas
Re: Looking for some pre-buying verification: will an external display actually work with a Lenovo Thinkpad P16 Gen 2?
On 06/06/2024 16:57, Lists wrote: As I don't do anything remotely graphically taxing I don't need a speedy GPU. More powerful GPU may mean better quality of local (offline) AI assistant. Perhaps it is too early to say that it is must have, but it seems changes are coming.
Re: Looking for some pre-buying verification: will an external display actually work with a Lenovo Thinkpad P16 Gen 2?
On 2024-06-03 23:50, Felix Miata wrote: Lists composed on 2024-06-03 22:39 (UTC+0200): I am thinking of replacing my old workstation with a Lenovo Thinkpad P16 Gen 2. That's a model line, not a model. It's available with multiple CPU/GPU combinations. You are correct. That slipped by me when I wrote my mail. To use it as described, I suggest to get one with only one GPU. Most problems laptop users want help with have hybrid graphics, and/or NVidia graphics as part of their mix. The reason for hybrid graphics is basically for maximizing both battery life and graphics performance. The former has no material relevance when rarely running on battery. Thanks for that idea. As I don't do anything remotely graphically taxing I don't need a speedy GPU. Most of my work on this machine will be programming and remote admin. Apart from watching a 4K video once in a while I dabble a bit in CAD, but those are fairly simple drawings that would in no way require a super-duper GPU. I'll try to find out if they allow for a configuration with an Intel graphics iGPU only, or otherwise the simplest dGPU. Ada 1000 seems to be the lowest spec available if I remember correctly. That should be more than sufficient. Grx HdV
Re: Looking for some pre-buying verification: will an external display actually work with a Lenovo Thinkpad P16 Gen 2?
Lists composed on 2024-06-03 22:39 (UTC+0200): > I am thinking of replacing my old workstation with a Lenovo Thinkpad P16 > Gen 2. That's a model line, not a model. It's available with multiple CPU/GPU combinations. To use it as described, I suggest to get one with only one GPU. Most problems laptop users want help with have hybrid graphics, and/or NVidia graphics as part of their mix. The reason for hybrid graphics is basically for maximizing both battery life and graphics performance. The former has no material relevance when rarely running on battery. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Looking for some pre-buying verification: will an external display actually work with a Lenovo Thinkpad P16 Gen 2?
Hi all, I am thinking of replacing my old workstation with a Lenovo Thinkpad P16 Gen 2. There's one thing that makes me hesitate though: on my current laptop (Thinkpad P1 Gen 1) the external display is hardwired to a specific port. Sadly, I have never been able to use any external display with that laptop. Not with the integrated graphics, nor with the discrete graphics. I am hoping to prevent this from happening again, as in this case that would be a critical "failure". The idea is that this machine will run with the lid closed using a large external monitor. In case that might be relevant: I am planning to buy the Universal Thunderbolt 4 Dock with this laptop. Are there any users of this laptop here on the list that can tell me if this exact type of Thinkpad can actually drive external displays when running Debian? I can't find any definite information regarding this issue on the Lenovo website and Google didn't get me any further either. Thanks in advance for any helpful information! Grx HdV
Re: Touchpad not detected by kernel on ThinkPad X13 Gen5
Le lundi 27 mai 2024 à 19:32 +0200, Sébastien Villemot a écrit : > I recently bought a ThinkPad X13 Gen5 (benefiting from the discount > generously offered by Lenovo to Debian Developers). > However, I still can’t get the touchpad to work. It is apparently not > recognized by the kernel, since the touchpad does not appear in > /proc/bus/input/devices, and there is nothing in the kernel log. Note > that the computer runs a custom build of Linux kernel 6.9.1. Actually, as pointed out privately to me by Mark Pearson, the problem is that CONFIG_PINCTRL_METEORLAKE was not enabled in my kernel configuration. This issue is tracked in Debian as #1072108. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Re: Touchpad not detected by kernel on ThinkPad X13 Gen5
On Mon, 27 May 2024 at 17:39, Sébastien Villemot wrote: > I recently bought a ThinkPad X13 Gen5 (benefiting from the discount > generously offered by Lenovo to Debian Developers). > > The laptop runs Debian Bookworm, and I got almost all the hardware to > work by using more recent kernel and firmware files (see Debian bug > reports #1070647, #1070648, #1070650). > > However, I still can’t get the touchpad to work. It is apparently not > recognized by the kernel, since the touchpad does not appear in > /proc/bus/input/devices, and there is nothing in the kernel log. Note > that the computer runs a custom build of Linux kernel 6.9.1. > > I opened a bug report against the kernel: > https://bugzilla.kernel.org/show_bug.cgi?id=218868 > > I’m largely ignorant of everything related to input drivers, so ideally > I would need help to further debug this and provide more useful > information to the kernel developers. Hi, This discussion related to those bugs might interest you: https://lists.debian.org/debian-kernel/2024/04/msg00247.html https://lists.debian.org/debian-kernel/2024/05/msg00032.html
Touchpad not detected by kernel on ThinkPad X13 Gen5
Hi, I recently bought a ThinkPad X13 Gen5 (benefiting from the discount generously offered by Lenovo to Debian Developers). The laptop runs Debian Bookworm, and I got almost all the hardware to work by using more recent kernel and firmware files (see Debian bug reports #1070647, #1070648, #1070650). However, I still can’t get the touchpad to work. It is apparently not recognized by the kernel, since the touchpad does not appear in /proc/bus/input/devices, and there is nothing in the kernel log. Note that the computer runs a custom build of Linux kernel 6.9.1. I opened a bug report against the kernel: https://bugzilla.kernel.org/show_bug.cgi?id=218868 I’m largely ignorant of everything related to input drivers, so ideally I would need help to further debug this and provide more useful information to the kernel developers. Thanks, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part
Re: Thunderbolt i debian 12: Thinkpad x390
Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-LM (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 root@triptofan:~# lsusb Bus 002 Device 008: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Kyson Bus 002 Device 011: ID 17ef:3082 Lenovo ThinkPad TBT 3 Dock Bus 002 Device 010: ID 17ef:307f Lenovo USB3.1 Hub Bus 002 Device 009: ID 17ef:307f Lenovo USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 2386:4338 Raydium Corporation Raydium Touch System Bus 001 Device 033: ID 2109:8887 VIA Labs, Inc. 40AN Bus 001 Device 031: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse Bus 001 Device 030: ID 413c:2106 Dell Computer Corp. QuietKey Keyboard Bus 001 Device 035: ID 17ef:30c9 Lenovo ThinkPad Thunderbolt 3 Dock USB Audio Bus 001 Device 032: ID 17ef:3081 Lenovo USB2.0 HUB Bus 001 Device 029: ID 17ef:3080 Lenovo USB2.0 Hub Bus 001 Device 028: ID 17ef:3080 Lenovo USB2.0 Hub Bus 001 Device 006: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # lshw -c Network *-network description: Ethernet interface physical id: 9 bus info: usb@2:2.1.2 logical name: enx047bcb643baf serial: 04:7b:cb:64:3b:af size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.12.13 duplex=full ip=10.*** link=yes multicast=yes port=MII speed=1Gbit/s root@triptofan:~# ethtool enx047bcb643baf Settings for enx047bcb643baf: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Auto-negotiation: on Port: MII PHYAD: 32 Transceiver: internal Supports Wake-on: pumbg Wake-on: g Current message level: 0x7fff (32767) drv probe link timer ifdown ifup rx_err tx_err tx_queued intr tx_done rx_status pktdata hw wol Link detected: yes # PANTALLA He provat de connectar la pantalla a través de la dock i res, no ha funcionat. L'altre dia vaig aconseguir que funcionés la pantalla. Així que he posat el cable Thunderbolt 4 i la pantalla ha funcionat, però ha deixat de funcionar la xarxa. Com que la pantalla a través de la dock es veu com blanquinosa, he tornat a connectar el cable HDMI directament al port del portàtil. Pregunta: algun motiu de perquè la pantalla es veu blanquinosa a través de la dock? el cable és el mateix. # BOLTCTL Per veure els dominis utilitzo boltctl domains root@triptofan:~# boltctl domains ● domain0 cd01-00a2-a098-2054-c02e6c7X ├─ bootacl: 0/16 └─ security: none root@triptofan:~# boltctl info cd01-00a2-a098-2054-c02e6c7X ○ Lenovo X390/T490s ├─ type: host ├─ name: X390/T490s ├─ vendor:Lenovo ├─ uuid: cd01-00a2-a098-2054-c02e6c7X ├─ dbus path: /org/freedesktop/bolt/devices/cd01_00a2_a098_2054_c02e6c7X ├─ generation:Thunderbolt 3 ├─ status:disconnected ├─ authorized:divendres, 24 de maig de 2024, 18:07:09 ├─ connected: divendres, 24 de maig de 2024, 18:07:09 └─ stored:dilluns, 29 d’abril de 2024, 09:16:40 ├─ policy: manual └─ key:no Si desconnecto el cable, aleshores surt així: root@triptofan:~# boltctl domains ○ domain cd01-00a2-a098-2054-c02e6c734026 ├─ bootacl: 0/16 └─ security: none I perquè torni a estar amb el puntet verd (que no s'aprecia al estar en text), he de reiniciar. He provat de jugar amb diferents comandes del bol
Thunderbolt i debian 12: Thinkpad x390
Bona tarda, Obro un fil nou per a mostrar els veus avenços. Aprofito per explicar les coses que m'he anat trobant per a les persones que encara no heu tocat aquesta tecnologia. Spoiler: Era el cable, però tot i això no acaba d'anar del tot la cosa # BIOS Anem per la part més de ferro. A la BIOS, hi ha un apartat a config the és Thunderbolt (TM) 3. Atenció lu del numero és important. Thunderbolt 3 != Thunderbolt 4 (tot i que quan vaig comprar el cable dèia que Thunderbolt 4 també servia per Thunderbolt 3 i de moment sembla que no amb el què m'he trobat). Hi ha dues opcions que s'han de tenir en compte 1. Security Level: [No Security | User Authorization | Secure Connect | Diplay Port and USB] He definit "No Security", això fa que es validi automàticament Thunderbolt. Entenc que el boltctl serviria per autoritzar la connexió d'aquests dispositius. 2. Support in Pre Boot Environment, Thunderbolt (TM) Device: [Disabled| Enabled| Pre-Boot ACL] - Pre-OS support for Thunderbold devices attached to Thunderbolt 3 port. [Enabled] - Thunderbolt devices to be connected automatically [Pre-Boot ACL] - Thunderbolt devices to be connected after de the user authorization or automatically with security level "No Security" [Disabled] He provat les tres opcions, i no hi ha canvi. La que he deixat ara mateix és Pre-Boot ACL. Al arrancar la màquina he buscat alguna cosa de gestionar thunderbolt sense arrancar el sistema i no he vist cap opció. # UBUNTU He reiniciat i la ethernet seguia sense aparèixer. Així que he arrancat amb la liveCD d'ubuntu. Allà he anat a buscar thunderbolt i dintre d'opcions > security, allà hi era. Però no detectava la dock station. Se m'ha ocorregut canviar el cable per el que venia amb la dockstation que és massa curt i per a això vaig comprar-ne un de nou i dadá! la ethernet ha funcionat i ha detectat la dockstation però tampoc em deixava fer gran cosa. El cable que venia amb la dock és Thunderbolt 3 i el que vaig comprar Thunderbolt 4. He provat de canviar els cables un parell de cops i el 4 no l'hi agradava, en comptes el 3 si. El boltcl domains em detectava el domini actiu. He reiniciat a debian de nou i amb el cable Thunderbolt 3 la xarxa ha funcionat correctament. He buscat el nom de la interfície però no l'hi posa nom, sembla que ho fa directament des de la dock. Ni amb lspci ni amb lsusb, ni amb lshw veig el nom de la interfície root@triptofan:~# lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:16.3 Serial controller: Intel Corporation Cannon Point-LP Keyboard and Text (KT) Redirection (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #1 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-LM (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 root@triptofan:~# lsusb Bus 002 Device 008: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Kyson Bus 002 Device 011: ID 17ef:3082 Lenovo ThinkPad TBT 3 Dock Bus 002 Device 010: ID 17ef:307f Lenovo USB3.1 Hub Bus 002 Device 009: ID 17ef:307f Lenovo USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 2386:4338 Raydium Corporation Raydium Touch System Bus 001 Device 033: ID 2109:8887 VIA Labs, Inc. 40AN Bus 001 D
Re: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
On Mon 22 Jan 2024 at 07:40:00 (+0100), Geert Stappers wrote: > On Sun, Jan 21, 2024 at 04:34:23PM -0600, David Wright wrote: > > On Sun 21 Jan 2024 at 22:41:01 (+0100), Geert Stappers wrote: > > > Pressing "Function key with symbol of computer sending signal" has no > > > effect. Which could be caused by the horrible state of keyboard. > > > When keyboard is needed, is an USB-attached keyboard needed. Usual use > > > case of the laptop is "headless server, server with SSH access". > > > > I'm not sure what you mean by horrible state. > > That the laptop has a worndown (usage damaged) keyboard. [1] > > > > So I'm ask if > > > export KEYCODE=42 > > > echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16 > > > could cause "wlan radio enable"? Or should KEYCODE be another magic > > > number? > > > > FWIW my wifi hardware button's keycode is 246. > > How was that keycode found? By running xev and pressing the button, which is on the front edge of the laptop. Having the button there is really inconvenient, as it's easy for a belt buckle or such to accidentally press it. In theory, that should be easily noticed, as the button is translucent and illuminated when wifi is connected (and flashes when attempting to connect). However, the light is not consistent in behaviour. But another suggestion comes from a more modern laptop, which has an aeroplane Fn-key (action/hot key), and that uses 255. So that's 246 / XF86WLAN on an old laptop with a physical button, and 255 / XF86RFKill on a newer laptop with a Fn-key. [ … ] > Back to "send key code". One can but try. Did you check the BIOS, BTW? $ xmodmap -pk or -pke will print what keycodes are available, but I don't claim to know how all this stuff works (if it does). Cheers, David.
Re: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
On Sun, Jan 21, 2024 at 04:34:23PM -0600, David Wright wrote: > On Sun 21 Jan 2024 at 22:41:01 (+0100), Geert Stappers wrote: > > Pressing "Function key with symbol of computer sending signal" has no > > effect. Which could be caused by the horrible state of keyboard. > > When keyboard is needed, is an USB-attached keyboard needed. Usual use > > case of the laptop is "headless server, server with SSH access". > > I'm not sure what you mean by horrible state. That the laptop has a worndown (usage damaged) keyboard. [1] > > So I'm ask if > > export KEYCODE=42 > > echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16 > > could cause "wlan radio enable"? Or should KEYCODE be another magic number? > > FWIW my wifi hardware button's keycode is 246. How was that keycode found? > But I would have thought the files to peruse might be: > > $ ls -GlgR /sys/class/rfkill/rfkill0/ > /sys/class/rfkill/rfkill0/: > total 0 > lrwxrwxrwx 10 Jan 21 16:13 device -> ../../phy0 > -r--r--r-- 1 4096 Jan 21 16:13 hard > -r--r--r-- 1 4096 Jan 21 16:13 index > -r--r--r-- 1 4096 Jan 21 16:13 name > -r--r--r-- 1 4096 Jan 21 16:13 persistent > drwxr-xr-x 20 Jan 21 16:13 power > -rw-r--r-- 1 4096 Jan 21 16:13 soft > -rw-r--r-- 1 4096 Jan 21 16:13 state > lrwxrwxrwx 10 Jan 21 16:13 subsystem -> > ../../../../../../../class/rfkill > -r--r--r-- 1 4096 Jan 21 16:13 type > -rw-r--r-- 1 4096 Jan 21 16:13 uevent > > /sys/class/rfkill/rfkill0/power: > total 0 > -rw-r--r-- 1 4096 Jan 21 16:14 async > -rw-r--r-- 1 4096 Jan 21 16:14 autosuspend_delay_ms > -rw-r--r-- 1 4096 Jan 21 16:14 control > -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_kids > -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_time > -r--r--r-- 1 4096 Jan 21 16:14 runtime_enabled > -r--r--r-- 1 4096 Jan 21 16:14 runtime_status > -r--r--r-- 1 4096 Jan 21 16:14 runtime_suspended_time > -r--r--r-- 1 4096 Jan 21 16:14 runtime_usage > $ Ah, nice. root@nero:/sys/class/rfkill/rfkill2# ls device hard index name persistent power soft state subsystem type uevent root@nero:/sys/class/rfkill/rfkill2# head * ==> device <== head: error reading 'device': Is a directory ==> hard <== 1 ==> index <== 2 ==> name <== phy0 ==> persistent <== 0 ==> power <== head: error reading 'power': Is a directory ==> soft <== 0 ==> state <== 2 ==> subsystem <== head: error reading 'subsystem': Is a directory ==> type <== wlan ==> uevent <== RFKILL_NAME=phy0 RFKILL_TYPE=wlan RFKILL_STATE=2 root@nero:/sys/class/rfkill/rfkill2# echo 0 > hard -bash: hard: Permission denied root@nero:/sys/class/rfkill/rfkill2# echo 1 > soft root@nero:/sys/class/rfkill/rfkill2# rfkill list 2 2: phy0: Wireless LAN Soft blocked: yes Hard blocked: yes root@nero:/sys/class/rfkill/rfkill2# echo 0 > soft root@nero:/sys/class/rfkill/rfkill2# rfkill list 2 2: phy0: Wireless LAN Soft blocked: no Hard blocked: yes root@nero:/sys/class/rfkill/rfkill2# Almost there and then reached a dead end. Back to "send key code". > > What also would be helpfull, is knowning if > > > > echo 4242 > /devics/platform/laptop_chipset/input/input17 > > > > could change brightness (or another visible effect) > > Likewise: > > $ ls -GlgR /sys/class/backlight/intel_backlight/ > $ > > A recent thread on that starts at: > > https://lists.debian.org/debian-user/2023/10/msg00621.html > > with a nice algorithm in: > > https://lists.debian.org/debian-user/2023/10/msg00648.html > Yes, nice. However the /sys/class/backlight/intel_backlight/ translates to the /sys/class/rfkill/rfkill2/ which has been explored. > Cheers, > David. Groeten Geert Stappers [1] The "horrible state" was and is also "best days are over" -- Silence is hard to parse
Re: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
On Sun, 21 Jan 2024 22:41:01 +0100 Geert Stappers wrote: > Hoping that is it possible: > > How to inject key stroke or "button pressed" in > /devices/platform/thinkpad_acpi/input/input16 ? Thinkwiki might be useful. https://www.thinkwiki.org/wiki/ThinkWiki -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
On Sun 21 Jan 2024 at 22:41:01 (+0100), Geert Stappers wrote: > Pressing "Function key with symbol of computer sending signal" has no > effect. Which could be caused by the horrible state of keyboard. > When keyboard is needed, is an USB-attached keyboard needed. Usual use > case of the laptop is "headless server, server with SSH access". I'm not sure what you mean by horrible state. > So I'm ask if > export KEYCODE=42 > echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16 > could cause "wlan radio enable"? Or should KEYCODE be another magic number? FWIW my wifi hardware button's keycode is 246. But I would have thought the files to peruse might be: $ ls -GlgR /sys/class/rfkill/rfkill0/ /sys/class/rfkill/rfkill0/: total 0 lrwxrwxrwx 10 Jan 21 16:13 device -> ../../phy0 -r--r--r-- 1 4096 Jan 21 16:13 hard -r--r--r-- 1 4096 Jan 21 16:13 index -r--r--r-- 1 4096 Jan 21 16:13 name -r--r--r-- 1 4096 Jan 21 16:13 persistent drwxr-xr-x 20 Jan 21 16:13 power -rw-r--r-- 1 4096 Jan 21 16:13 soft -rw-r--r-- 1 4096 Jan 21 16:13 state lrwxrwxrwx 10 Jan 21 16:13 subsystem -> ../../../../../../../class/rfkill -r--r--r-- 1 4096 Jan 21 16:13 type -rw-r--r-- 1 4096 Jan 21 16:13 uevent /sys/class/rfkill/rfkill0/power: total 0 -rw-r--r-- 1 4096 Jan 21 16:14 async -rw-r--r-- 1 4096 Jan 21 16:14 autosuspend_delay_ms -rw-r--r-- 1 4096 Jan 21 16:14 control -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_kids -r--r--r-- 1 4096 Jan 21 16:14 runtime_active_time -r--r--r-- 1 4096 Jan 21 16:14 runtime_enabled -r--r--r-- 1 4096 Jan 21 16:14 runtime_status -r--r--r-- 1 4096 Jan 21 16:14 runtime_suspended_time -r--r--r-- 1 4096 Jan 21 16:14 runtime_usage $ > What also would be helpfull, is knowning if > > echo 4242 > /devics/platform/laptop_chipset/input/input17 > > could change brightness (or another visible effect) Likewise: $ ls -GlgR /sys/class/backlight/intel_backlight/ /sys/class/backlight/intel_backlight/: total 0 -r--r--r-- 1 4096 Jan 21 16:19 actual_brightness -rw-r--r-- 1 4096 Jan 21 16:19 bl_power -rw-r--r-- 1 4096 Jan 18 21:57 brightness lrwxrwxrwx 10 Jan 21 16:19 device -> ../../card1-eDP-1 -r--r--r-- 1 4096 Jan 18 21:57 max_brightness drwxr-xr-x 20 Jan 21 16:19 power -r--r--r-- 1 4096 Jan 21 16:19 scale lrwxrwxrwx 10 Jan 18 21:57 subsystem -> ../../../../../../../class/backlight -r--r--r-- 1 4096 Jan 18 21:57 type -rw-r--r-- 1 4096 Jan 18 21:57 uevent /sys/class/backlight/intel_backlight/power: total 0 -rw-r--r-- 1 4096 Jan 21 16:19 async -rw-r--r-- 1 4096 Jan 21 16:19 autosuspend_delay_ms -rw-r--r-- 1 4096 Jan 21 16:19 control -r--r--r-- 1 4096 Jan 21 16:19 runtime_active_kids -r--r--r-- 1 4096 Jan 21 16:19 runtime_active_time -r--r--r-- 1 4096 Jan 21 16:19 runtime_enabled -r--r--r-- 1 4096 Jan 21 16:19 runtime_status -r--r--r-- 1 4096 Jan 21 16:19 runtime_suspended_time -r--r--r-- 1 4096 Jan 21 16:19 runtime_usage $ A recent thread on that starts at: https://lists.debian.org/debian-user/2023/10/msg00621.html with a nice algorithm in: https://lists.debian.org/debian-user/2023/10/msg00648.html Cheers, David.
ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16
Hi, Hoping that is it possible: How to inject key stroke or "button pressed" in /devices/platform/thinkpad_acpi/input/input16 ? Website https://xyproblem.info says I should tell what the original problem is. It is `rfkill list` reporting "hard blocked", not being enable to use WIFI, `nmcli radio wifi` reporting "disabled". Pressing "Function key with symbol of computer sending signal" has no effect. Which could be caused by the horrible state of keyboard. When keyboard is needed, is an USB-attached keyboard needed. Usual use case of the laptop is "headless server, server with SSH access". So I'm ask if export KEYCODE=42 echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16 could cause "wlan radio enable"? Or should KEYCODE be another magic number? What also would be helpfull, is knowning if echo 4242 > /devics/platform/laptop_chipset/input/input17 could change brightness (or another visible effect) Regards Geert Stappers Below some information from the original problem. root@nero:~# dmesg | grep -e thinkpad -e iwlwifi -e rfkill [7.867099] thinkpad_acpi: ThinkPad ACPI Extras v0.26 [7.867103] thinkpad_acpi: http://ibm-acpi.sf.net/ [7.867106] thinkpad_acpi: ThinkPad BIOS 8QET54WW (1.15 ), EC unknown [7.867108] thinkpad_acpi: Lenovo ThinkPad X121e, model 304579G [7.870746] thinkpad_acpi: radio switch found; radios are disabled [7.870778] thinkpad_acpi: Tablet mode switch found (type: MHKG), currently in laptop mode [7.870815] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver [7.870817] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... [7.952756] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is blocked [7.976749] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is blocked [7.978727] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one [7.979632] thinkpad_acpi: Console audio control enabled, mode: monitor (read only) [8.002749] thinkpad_acpi: Error probing battery 2 [8.003148] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input16 [8.397512] iwlwifi :02:00.0: can't disable ASPM; OS doesn't have ASPM control [8.405654] iwlwifi :02:00.0: firmware: direct-loading firmware iwlwifi-1000-5.ucode [8.405864] iwlwifi :02:00.0: loaded firmware version 39.31.5.1 build 35138 1000-5.ucode op_mode iwldvm [8.405909] iwlwifi :02:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [8.658837] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUG disabled [8.658843] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEBUGFS disabled [8.658846] iwlwifi :02:00.0: CONFIG_IWLWIFI_DEVICE_TRACING disabled [8.658850] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1000 BGN, REV=0x6C [8.676689] iwlwifi :02:00.0: reporting RF_KILL (radio disabled) [8.702522] iwlwifi :02:00.0: RF_KILL bit toggled to disable radio. [8.778160] iwlwifi :02:00.0 wlp2s0: renamed from wlan0 root@nero:~# -- Silence is hard to parse
Re: Fn keys not working in Debian 12 on Lenovo Thinkpad T450s
Nicolas George writes: > Rodolfo Medina (12024-01-11): >> As my machine has a dual boot with MS Windows, F2 and F3 keyboard keys work >> fine in Windows in lowering and increasing sound volume, and F1 for muting >> it etcetera F4, F5, F6..., but in Debian they don't seem to work. > > Hi. > > Try testing them with xev. Show what you get if you cannot read it. Thanks. Here's the whole output: Outer window is 0x221, inner window is 0x222 PropertyNotify event, serial 8, synthetic NO, window 0x221, atom 0x27 (WM_NAME), time 33946030, state PropertyNewValue PropertyNotify event, serial 9, synthetic NO, window 0x221, atom 0x22 (WM_COMMAND), time 33946030, state PropertyNewValue PropertyNotify event, serial 10, synthetic NO, window 0x221, atom 0x28 (WM_NORMAL_HINTS), time 33946030, state PropertyNewValue CreateNotify event, serial 11, synthetic NO, window 0x221, parent 0x221, window 0x222, (10,10), width 50, height 50 border_width 4, override NO PropertyNotify event, serial 14, synthetic NO, window 0x221, atom 0x167 (WM_PROTOCOLS), time 33946030, state PropertyNewValue MapNotify event, serial 15, synthetic NO, window 0x221, event 0x221, window 0x222, override NO PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x186 (_NET_WM_VISIBLE_NAME), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x188 (_NET_WM_VISIBLE_ICON_NAME), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x1c1 (_OB_APP_ROLE), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x1c3 (_OB_APP_NAME), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x1c4 (_OB_APP_CLASS), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x1c5 (_OB_APP_GROUP_NAME), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x1c6 (_OB_APP_GROUP_CLASS), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x1c2 (_OB_APP_TITLE), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x1c7 (_OB_APP_TYPE), time 33946031, state PropertyNewValue PropertyNotify event, serial 18, synthetic NO, window 0x221, atom 0x18e (_NET_WM_ICON), time 33946031, state PropertyNewValue ReparentNotify event, serial 18, synthetic NO, window 0x221, event 0x221, window 0x221, parent 0x40169d, (0,0), override NO PropertyNotify event, serial 21, synthetic NO, window 0x221, atom 0x18b (_NET_WM_STATE), time 33946031, state PropertyNewValue ConfigureNotify event, serial 21, synthetic NO, window 0x221, event 0x221, window 0x221, (0,0), width 178, height 178, border_width 0, above 0x4016e9, override NO ConfigureNotify event, serial 21, synthetic NO, window 0x221, event 0x221, window 0x221, (1,22), width 178, height 178, border_width 0, above 0x4016e9, override NO PropertyNotify event, serial 21, synthetic NO, window 0x221, atom 0x195 (_NET_FRAME_EXTENTS), time 33946031, state PropertyNewValue PropertyNotify event, serial 21, synthetic NO, window 0x221, atom 0x194 (_KDE_NET_WM_FRAME_STRUT), time 33946031, state PropertyNewValue PropertyNotify event, serial 22, synthetic NO, window 0x221, atom 0x191 (_NET_WM_ALLOWED_ACTIONS), time 33946031, state PropertyNewValue ConfigureNotify event, serial 22, synthetic YES, window 0x221, event 0x221, window 0x221, (1045,20), width 178, height 178, border_width 2, above 0x0, override NO PropertyNotify event, serial 22, synthetic NO, window 0x221, atom 0x189 (_NET_WM_DESKTOP), time 33946032, state PropertyNewValue MapNotify event, serial 39, synthetic NO, window 0x221, event 0x221, window 0x221, override NO VisibilityNotify event, serial 39, synthetic NO, window 0x221, state VisibilityFullyObscured PropertyNotify event, serial 39, synthetic NO, window 0x221, atom 0x168 (WM_STATE), time 33946033, state PropertyNewValue VisibilityNotify event, serial 39, synthetic NO, window 0x221, state VisibilityUnobscured Expose event, serial 39, synthetic NO, window 0x221, (0,0), width 178, height 10, count 3 Expose event, serial 39, synthetic NO, window 0x221, (0,10), width 10, height 58, count 2 Expose event, serial 39, synthetic NO, window 0x221, (68,10), width 110, height 58, count 1 Expose event, serial 39, synthetic NO, window 0x221, (0,68), width 178, height 110, count 0 FocusIn event, serial 40, synthetic NO, window 0x221, mode NotifyNormal, detail NotifyNonlinear
Re: Fn keys not working in Debian 12 on Lenovo Thinkpad T450s
On Thu, Jan 11, 2024 at 10:29:37AM +, Rodolfo Medina wrote: [...] > Following your example, I aptitude-installed acpid and created > /etc/apt/events/briteup and /etc/acpi/actions/brite and filled them with the > stuff you reported; and then I did `chmod +x brite'... Then? ...you might be able to change your screen's brightness by hitting your brightness keys (here they are Fn+F8, Fn+F9). Note that you might have to adjust the events to listen to or the paths to the backlight system files (my "/sys/class/backlight/intel_backlight" and companions). Some tinkering possibly needed :-) Cheers -- t signature.asc Description: PGP signature
Re: Fn keys not working in Debian 12 on Lenovo Thinkpad T450s
writes: > On Thu, Jan 11, 2024 at 08:53:46AM +, Rodolfo Medina wrote: >> As my machine has a dual boot with MS Windows, F2 and F3 keyboard keys work >> fine in Windows in lowering and increasing sound volume, and F1 for muting it >> etcetera F4, F5, F6..., but in Debian they don't seem to work. > > "In Debian" is a wide land :-) It's Bookworm with Openbox. > OT1H... > > A week ago I installed Debian's Bookworm with MATE on a friend's computer > (Thinkpad x270) and the loudness keys worked out of the box. > > OTOH... > > Myself -- I have no desktop environment (fvwm on X, *no* systemd, *no* > DBUS, so that would count as "exotic guy"). > > On my laptop (a Thinkpad x230) the background brightness wasn't working > (I don't know about the loudness things, since I never needed/used them). > > Therefore I decided to catch ACPI events and set up this: > > --- --- > tomas@trotzki:~$ cat /etc/acpi/events/briteup > > event=video/brightnessup > action=/etc/acpi/actions/brite "%e" > --- --- > tomas@trotzki:~$ cat /etc/acpi/events/britedn > > event=video/brightnessdown > action=/etc/acpi/actions/brite "%e" > --- --- > tomas@trotzki:~$ cat /etc/acpi/actions/brite > > #!/bin/sh > logger "[ACPI] $@" > BASE="/sys/class/backlight/intel_backlight" > CURR=$(cat "$BASE/brightness") > MAX=$(cat "$BASE/max_brightness") > # MIN is some arbitrary "low" value. Note that for values > # of MIN below 6 (more precisely: 2/11 for our factor), the > # thing gets stuck at the low end: (13 * x) / 11 == x, > # in integer arithmetic, for x <= 5. > # > # The "exponential" algorithm is a bit long at the low > # end. We might consider stretching there. Or increasing > # MIN. > > MIN=20 > if [ "$CURR" -lt "$MIN" ] ; then CURR="$MIN" ; fi > > # NOTE: 11/13 is approx the fourth root of 1/2: > # i.e. four steps are a doubling/halving > # of brightness (constant steps gave too > # coarse jumps in the low range) > > case $1 in > video/brightnessdown* ) > NEW=$(( (11 * CURR) / 13 )) > ;; > video/brightnessup* ) > NEW=$(( (13 * CURR) / 11 )) > ;; > * ) > exit 0 > ;; > esac > > if [ "$NEW" -lt "$MIN" ] ; then NEW="$MIN" ; fi > if [ "$NEW" -gt "$MAX" ] ; then NEW="$MAX" ; fi > logger "[ACPI] brightness $CURR --> $NEW" > echo "$NEW" > $BASE/brightness > --- --- > > (The charm of using ACPI is that it works independently of X). > > To find which events to wait on, just run acpi_listen on a > terminal and hit your dream's key. Following your example, I aptitude-installed acpid and created /etc/apt/events/briteup and /etc/acpi/actions/brite and filled them with the stuff you reported; and then I did `chmod +x brite'... Then? Thanks, Rodolfo
Re: Fn keys not working in Debian 12 on Lenovo Thinkpad T450s
On Thu, Jan 11, 2024 at 10:08:53AM +0100, Nicolas George wrote: > Rodolfo Medina (12024-01-11): > > As my machine has a dual boot with MS Windows, F2 and F3 keyboard keys work > > fine in Windows in lowering and increasing sound volume, and F1 for muting > > it > > etcetera F4, F5, F6..., but in Debian they don't seem to work. > > Hi. > > Try testing them with xev. Show what you get if you cannot read it. See my other post: I did start with xev, but I like things working on the Linux console too, that's why I moved to ACPI events (but this is special to special keys and won't catch regular keys. Alas.) Cheers -- t signature.asc Description: PGP signature
Re: Fn keys not working in Debian 12 on Lenovo Thinkpad T450s
On Thu, Jan 11, 2024 at 08:53:46AM +, Rodolfo Medina wrote: > As my machine has a dual boot with MS Windows, F2 and F3 keyboard keys work > fine in Windows in lowering and increasing sound volume, and F1 for muting it > etcetera F4, F5, F6..., but in Debian they don't seem to work. "In Debian" is a wide land :-) OT1H... A week ago I installed Debian's Bookworm with MATE on a friend's computer (Thinkpad x270) and the loudness keys worked out of the box. OTOH... Myself -- I have no desktop environment (fvwm on X, *no* systemd, *no* DBUS, so that would count as "exotic guy"). On my laptop (a Thinkpad x230) the background brightness wasn't working (I don't know about the loudness things, since I never needed/used them). Therefore I decided to catch ACPI events and set up this: --- --- tomas@trotzki:~$ cat /etc/acpi/events/briteup event=video/brightnessup action=/etc/acpi/actions/brite "%e" --- --- tomas@trotzki:~$ cat /etc/acpi/events/britedn event=video/brightnessdown action=/etc/acpi/actions/brite "%e" --- --- tomas@trotzki:~$ cat /etc/acpi/actions/brite #!/bin/sh logger "[ACPI] $@" BASE="/sys/class/backlight/intel_backlight" CURR=$(cat "$BASE/brightness") MAX=$(cat "$BASE/max_brightness") # MIN is some arbitrary "low" value. Note that for values # of MIN below 6 (more precisely: 2/11 for our factor), the # thing gets stuck at the low end: (13 * x) / 11 == x, # in integer arithmetic, for x <= 5. # # The "exponential" algorithm is a bit long at the low # end. We might consider stretching there. Or increasing # MIN. MIN=20 if [ "$CURR" -lt "$MIN" ] ; then CURR="$MIN" ; fi # NOTE: 11/13 is approx the fourth root of 1/2: # i.e. four steps are a doubling/halving # of brightness (constant steps gave too # coarse jumps in the low range) case $1 in video/brightnessdown* ) NEW=$(( (11 * CURR) / 13 )) ;; video/brightnessup* ) NEW=$(( (13 * CURR) / 11 )) ;; * ) exit 0 ;; esac if [ "$NEW" -lt "$MIN" ] ; then NEW="$MIN" ; fi if [ "$NEW" -gt "$MAX" ] ; then NEW="$MAX" ; fi logger "[ACPI] brightness $CURR --> $NEW" echo "$NEW" > $BASE/brightness --- --- (The charm of using ACPI is that it works independently of X). To find which events to wait on, just run acpi_listen on a terminal and hit your dream's key. > Please help who can, thanks in advance. The appropriate medication will depend on your microbiome ;-) Cheers -- t signature.asc Description: PGP signature
Re: Fn keys not working in Debian 12 on Lenovo Thinkpad T450s
Rodolfo Medina (12024-01-11): > As my machine has a dual boot with MS Windows, F2 and F3 keyboard keys work > fine in Windows in lowering and increasing sound volume, and F1 for muting it > etcetera F4, F5, F6..., but in Debian they don't seem to work. Hi. Try testing them with xev. Show what you get if you cannot read it. Regards, -- Nicolas George
Re: Fn keys not working in Debian 12 on Lenovo Thinkpad T450s
Rodolfo Medina writes: > As my machine has a dual boot with MS Windows, F2 and F3 keyboard keys work > fine in Windows in lowering and increasing sound volume, and F1 for muting it > etcetera F4, F5, F6..., but in Debian they don't seem to work. Sorry, I forgot to say that Openbox is my graphical environment. Thanks, Rodolfo
Fn keys not working in Debian 12 on Lenovo Thinkpad T450s
As my machine has a dual boot with MS Windows, F2 and F3 keyboard keys work fine in Windows in lowering and increasing sound volume, and F1 for muting it etcetera F4, F5, F6..., but in Debian they don't seem to work. Please help who can, thanks in advance. Rodolfo
Re: Thinkpad x13 AMD Ryzen microphone not working in Debian Bookworm
I found out that when I plugin a headset the microphone works. So it seems that this is related only to the internal microphone. *-multimedia:2 description: Audio device product: Family 17h/19h HD Audio Controller vendor: Advanced Micro Devices, Inc. [AMD] physical id: 0.6 bus info: pci@:c3:00.6 logical name: card1 logical name: /dev/snd/controlC1 logical name: /dev/snd/hwC1D0 logical name: /dev/snd/pcmC1D0c logical name: /dev/snd/pcmC1D0p version: 00 width: 32 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:107 memory:905c-905c7fff *-input:0 product: HDA Digital PCBeep physical id: 0 logical name: input15 logical name: /dev/input/event13 capabilities: pci *-input:1 product: HD-AudioGeneric Mic physical id: 1 logical name: input19 logical name: /dev/input/event14 *-input:2 product: HD-AudioGeneric Headphone physical id: 2 logical name: input20 logical name: /dev/input/event15 Jiri -- On 10/12/23 20:30, Jiri Kanicky wrote: I have installed Debian Bookworm on X13 with AMD Ryzen 7840U and microphone is not working. It shows inactive. I use KDE and installed pipewire. The mic did not work since base install. Any advise? $ inxi -A Audio: Device-1: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel API: ALSA v: k6.5.0-0.deb12.1-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active $ inxi CPU: 8-core AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics (-MT MCP-) speed/min/max: 1337/400/5132:6076:5605:5289:5447:5760:5918 MHz Kernel: 6.5.0-0.deb12.1-amd64 x86_64 Up: 6m Mem: 4206.1/30781.0 MiB (13.7%) Storage: 476.94 GiB (3.3% used) Procs: 370 Shell: Bash inxi: 3.3.26 $ pactl list cards Card #44 Name: alsa_card.pci-_c3_00.1 Driver: alsa Owner Module: n/a Properties: api.acp.auto-port = "false" api.acp.auto-profile = "false" api.alsa.card = "0" api.alsa.card.longname = "HD-Audio Generic at 0x905c8000 irq 106" api.alsa.card.name = "HD-Audio Generic" api.alsa.path = "hw:0" api.alsa.use-acp = "true" api.dbus.ReserveDevice1 = "Audio0" device.api = "alsa" device.bus = "pci" device.bus_path = "pci-:c3:00.1" device.description = "Rembrandt Radeon High Definition Audio Controller" device.enum.api = "udev" device.icon_name = "audio-card-analog-pci" device.name = "alsa_card.pci-_c3_00.1" device.nick = "HD-Audio Generic" device.plugged.usec = "5163628" device.product.id = "0x1640" device.product.name = "Rembrandt Radeon High Definition Audio Controller" device.subsystem = "sound" sysfs.path = "/devices/pci:00/:00:08.1/:c3:00.1/sound/card0" device.vendor.id = "0x1002" device.vendor.name = "Advanced Micro Devices, Inc. [AMD/ATI]" media.class = "Audio/Device" factory.id = "14" client.id = "34" object.id = "44" object.serial = "44" object.path = "alsa:pcm:0" alsa.card = "0" alsa.card_name = "HD-Audio Generic" alsa.long_card_name = "HD-Audio Generic at 0x905c8000 irq 106" alsa.driver_name = "snd_hda_intel" device.string = "0" Profiles: off: Off (sinks: 0, sources: 0, priority: 0, available: yes) output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, sources: 0, priority: 5900, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no)
Thinkpad x13 AMD Ryzen microphone not working in Debian Bookworm
I have installed Debian Bookworm on X13 with AMD Ryzen 7840U and microphone is not working. It shows inactive. I use KDE and installed pipewire. The mic did not work since base install. Any advise? $ inxi -A Audio: Device-1: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor driver: N/A Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel API: ALSA v: k6.5.0-0.deb12.1-amd64 status: kernel-api Server-1: PipeWire v: 0.3.65 status: active $ inxi CPU: 8-core AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics (-MT MCP-) speed/min/max: 1337/400/5132:6076:5605:5289:5447:5760:5918 MHz Kernel: 6.5.0-0.deb12.1-amd64 x86_64 Up: 6m Mem: 4206.1/30781.0 MiB (13.7%) Storage: 476.94 GiB (3.3% used) Procs: 370 Shell: Bash inxi: 3.3.26 $ pactl list cards Card #44 Name: alsa_card.pci-_c3_00.1 Driver: alsa Owner Module: n/a Properties: api.acp.auto-port = "false" api.acp.auto-profile = "false" api.alsa.card = "0" api.alsa.card.longname = "HD-Audio Generic at 0x905c8000 irq 106" api.alsa.card.name = "HD-Audio Generic" api.alsa.path = "hw:0" api.alsa.use-acp = "true" api.dbus.ReserveDevice1 = "Audio0" device.api = "alsa" device.bus = "pci" device.bus_path = "pci-:c3:00.1" device.description = "Rembrandt Radeon High Definition Audio Controller" device.enum.api = "udev" device.icon_name = "audio-card-analog-pci" device.name = "alsa_card.pci-_c3_00.1" device.nick = "HD-Audio Generic" device.plugged.usec = "5163628" device.product.id = "0x1640" device.product.name = "Rembrandt Radeon High Definition Audio Controller" device.subsystem = "sound" sysfs.path = "/devices/pci:00/:00:08.1/:c3:00.1/sound/card0" device.vendor.id = "0x1002" device.vendor.name = "Advanced Micro Devices, Inc. [AMD/ATI]" media.class = "Audio/Device" factory.id = "14" client.id = "34" object.id = "44" object.serial = "44" object.path = "alsa:pcm:0" alsa.card = "0" alsa.card_name = "HD-Audio Generic" alsa.long_card_name = "HD-Audio Generic at 0x905c8000 irq 106" alsa.driver_name = "snd_hda_intel" device.string = "0" Profiles: off: Off (sinks: 0, sources: 0, priority: 0, available: yes) output:hdmi-stereo: Digital Stereo (HDMI) Output (sinks: 1, sources: 0, priority: 5900, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (sinks: 1, sources: 0, priority: 5700, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (sinks: 1, sources: 0, priority: 800, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (sinks: 1, sources: 0, priority: 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (sinks: 1, sources: 0, priority: 600, available: no) pro-audio: Pro Audio (sinks: 4, sources: 0, priority: 1, available: yes) Active Profile: off Ports: hdmi-output-0: HDMI / DisplayPort (type: HDMI, priority: 5900, latency offset: 0 usec, availability group: Legacy 1, not available) Properties: port.type = "hdmi" port.availability-group = "Legacy 1" device.icon_name = "video-display" card.profile.port = "0" Part of profile(s): output:hdmi-stereo,
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
On 20/10/2023 20:13, Anssi Saari wrote: Max Nikulin writes: A decade ago I used a HDMI to DVI adapter plugged into the monitor (a case a bit larger than a DVI male connector having a HDMI slot). I would check if DP to DVI or DP to HDMI converters exist and have no compatibility issues (e.g. I have heard of bugs related to support of USB-C to DP chips). [...] It would only display its native resolution of 2560x1600 via dual link DVI, just connecting via HDMI to DVI cable got me a quarter resolution 1280x800 which was quite grainy on a 30" display. I found some converter boxes existed. From memory I think you could go from DP to DL-DVI directly, from HDMI you needed to convert to DP first. [...] BTW, considering the resolution and monitor in question, 1600x900 is single link DVI territory so easier conversion and cables. In my case it was a cheap adapter to connect HDMI (laptop) to DVI (monitor). It worked perfectly with a LG monitor having 1600x1200 resolution. By the way, this monitor worked reliably with an even older laptop that had VGA connector only. Of course, it was necessary to regularly run autoadjustment. As for DP, my current laptop has "DP" label next to a USB-C connector. I am unsure if X220T has real DP connector.
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
Max Nikulin writes: > A decade ago I used a HDMI to DVI adapter plugged into the monitor (a > case a bit larger than a DVI male connector having a HDMI slot). I > would check if DP to DVI or DP to HDMI converters exist and have no > compatibility issues (e.g. I have heard of bugs related to support of > USB-C to DP chips). I looked into this some time ago, we had a giveaway of some old monitors at work, mostly awful stuff but there was one 30" monitor. It would only display its native resolution of 2560x1600 via dual link DVI, just connecting via HDMI to DVI cable got me a quarter resolution 1280x800 which was quite grainy on a 30" display. I found some converter boxes existed. From memory I think you could go from DP to DL-DVI directly, from HDMI you needed to convert to DP first. I decided it was too much hassle and money (converter box and cables) for a free display. BTW, considering the resolution and monitor in question, 1600x900 is single link DVI territory so easier conversion and cables. Well, going from DP to HDMI/DVI is still a bear but if the laptop has a HDMI transmitter then the "conversion" is a matter of plugging in an adapter which tells the video transmitter to switch to HDMI mode.
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
Max Nikulin wrote: > On 20/10/2023 07:46, riveravaldez wrote: > > Certainly, but it hasn't. It has only VGA and DVI-D (Dual Link) inputs, > > and the laptop has only DP and VGA outputs, so, VGA is the first > > option... > > A decade ago I used a HDMI to DVI adapter plugged into the monitor (a case a > bit larger than a DVI male connector having a HDMI slot). I would check if > DP to DVI or DP to HDMI converters exist and have no compatibility issues > (e.g. I have heard of bugs related to support of USB-C to DP chips). DP to DVI and DP to HDMI both exist, and are reasonably cheap. There are a couple of quality grades, but they only make a difference at 4K or high refresh rates. -dsr-
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
riveravaldez composed on 2023-10-19 21:46 (UTC-0300): > Felix Miata wrote: >> riveravaldez composed on 2023-10-18 16:05 (UTC-0300): >>> Hi everybody, I'm having a resolution issue trying to connect an >>> external monitor to a laptop. >> ... > Hi, Felix, thanks a lot for your very detailed reply and help, it's most > appreciated. >> Using DP instead of VGA would likely solve this if your display had a DP >> input. :p > Certainly, but it hasn't. It has only VGA and DVI-D (Dual Link) inputs, and > the laptop has only DP and VGA outputs, so, VGA is the first option... >> ..., give us something to work from: >> 1-copy & paste input/output from >> inxi -GSaz >> run from an GUI terminal. > $ inxi -GSaz > System: > Kernel: 5.10.0-26-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 > parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-26-amd64 > root=UUID=f80500ac-b2c4-4b08-b123-7dc04b22ea33 ro quiet > Desktop: IceWM 2.7.0 dm: LightDM 1.26.0 Distro: Debian GNU/Linux > bookworm/sid > Graphics: > Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics > vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 > class ID: 0300 > Device-2: Chicony Lenovo Integrated Camera (0.3MP) type: USB driver: > uvcvideo > bus ID: 1-1.6:3 chip ID: 04f2:b217 class ID: 0e02 > Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting > unloaded: fbdev,vesa display ID: :0 screens: 1 > Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") > s-diag: 414mm (16.3") > Monitor-1: LVDS-1 res: 1366x768 hz: 60 dpi: 125 size: 277x156mm (10.9x6.1") > diag: 318mm (12.5") > OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 > Mesa 20.3.5 > compat-v: 3.0 direct render: Yes >> 2-pastebin Xorg.0.log from either /var/log/ or ~/.local/share/xorg/ and >> provide >> its URL. > /var/log/Xorg.0.log > https://paste.debian.net/plain/1295616 https://paste.debian.net/1295628 >> Below in file named /etc/X11/xorg.conf.d/50-monitor.conf could be part of a >> solution, with more information the above request would supply. > Thanks a lot for the proposed solutions. I'm gonna check them and read what's > needed about X to try to put them at work. Hope there's more help I can get > with the info just added. The only clue I see in either log is the very last line of the newer, where X allocates a 1600x900 space, but there's nothing more. Check your VGA cable. If it doesn't have 15 pins on both ends, try one that does. Have you checked BIOS to ensure there isn't anything in it that could block the VGA output? What follows is from a laptop older than yours: # xdriinfo Screen 0: crocus # inxi -GSaz --vs --zl --hostname inxi 3.3.30-00 (2023-09-25) System: Host: e6400 Kernel: 6.1.0-13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 clocksource: hpet available: acpi_pm parameters: BOOT_IMAGE=/vmlinuz root=LABEL= resume=LABEL= ipv6.disable=1 net.ifnames=0 consoleblank=0 preempt=full mitigations=off no_console_suspend Desktop: Trinity v: R14.1.0 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0 vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 12 (bookworm) Graphics: Device-1: Intel Mobile 4 Series Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen-5 process: Intel 45nm built: 2008 ports: active: HDMI-A-1,LVDS-1 empty: DP-1, DP-2, DP-3, HDMI-A-2, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:2a42 class-ID: 0300 Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: crocus gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 3200x1080 s-dpi: 109 s-size: 749x253mm (29.49x9.96") s-diag: 791mm (31.13") Monitor-1: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: Acer K272HUL serial: built: 2018 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400 Monitor-2: LVDS-1 pos: right model: Seiko Epson 0x5441 built: 2008 res: 1280x800 hz: 60 dpi: 107 gamma: 1.2 size: 303x190mm (11.93x7.48") diag: 358mm (14.1") ratio: 16:10 modes: 1280x800 API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11: drv: crocus inactive: wayland API: OpenGL v: 2.1 vendor: intel mesa v: 22.3.6 glx-v: 1.4 es-v: 2.0 direct-render: yes renderer: Mesa Mobile Intel GM45 Express (CTG) device-ID: 8086:2a42 memory: 1.46 GiB unified: yes # While it reports HDMI and LVDS (internal) connected displays, in fact the external is connected to the laptop's DisplayPort, while the input to the display is a DVI port. DP-to-DVI cables and adapters on eBay go for as little as under USD$10. I suggest you try one if a 15 pin cable doesn't suffice. Other than that one line mentioned, I see nothing helpful in the two logs. It's possible there might be something useful in the journal. First, try: journalctl -b
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
On 20/10/2023 07:46, riveravaldez wrote: Certainly, but it hasn't. It has only VGA and DVI-D (Dual Link) inputs, and the laptop has only DP and VGA outputs, so, VGA is the first option... A decade ago I used a HDMI to DVI adapter plugged into the monitor (a case a bit larger than a DVI male connector having a HDMI slot). I would check if DP to DVI or DP to HDMI converters exist and have no compatibility issues (e.g. I have heard of bugs related to support of USB-C to DP chips). Was external monitor connected and turned on when you were collecting logs? I assume that your monitor may report supported modes. May it happen that the VGA cable lacks wires related to the digital link for DDC communication and allowing to get EDID info? I would try to get list of modes in a more direct way (adjust card-port path component) edid-decode /sys/class/drm/card0-eDP-1/edid or parse-edid < /sys/class/drm/card0-HDMI-A-1/edid from read-edid and edid-decode packages. P.S. Do not neglect screws on VGA connectors.
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
On 10/19/23, Stefan Monnier wrote: >> /var/log/Xorg.0.log https://paste.debian.net/plain/1295616 > > IIUC this is an `Xorg.0.log` from when the external monitor was > not connected. > > I suspect a more useful one would be when the external monitor was > connected as well. Certainly, Stefan, sounds pretty logic to me... Sorry. /var/log/Xorg.0.log https://paste.debian.net/1295628 There it goes. Thanks a lot!
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
> /var/log/Xorg.0.log https://paste.debian.net/plain/1295616 IIUC this is an `Xorg.0.log` from when the external monitor was not connected. I suspect a more useful one would be when the external monitor was connected as well. Stefan
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
On 10/18/23, Felix Miata wrote: > riveravaldez composed on 2023-10-18 16:05 (UTC-0300): > >> Hi everybody, I'm having a resolution issue trying to connect an >> external monitor to a laptop. > ... Hi, Felix, thanks a lot for your very detailed reply and help, it's most appreciated. > Using DP instead of VGA would likely solve this if your display had a DP > input. :p Certainly, but it hasn't. It has only VGA and DVI-D (Dual Link) inputs, and the laptop has only DP and VGA outputs, so, VGA is the first option... > ..., give us something to work from: > > 1-copy & paste input/output from > inxi -GSaz > run from an GUI terminal. $ inxi -GSaz System: Kernel: 5.10.0-26-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-26-amd64 root=UUID=f80500ac-b2c4-4b08-b123-7dc04b22ea33 ro quiet Desktop: IceWM 2.7.0 dm: LightDM 1.26.0 Distro: Debian GNU/Linux bookworm/sid Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0126 class ID: 0300 Device-2: Chicony Lenovo Integrated Camera (0.3MP) type: USB driver: uvcvideo bus ID: 1-1.6:3 chip ID: 04f2:b217 class ID: 0e02 Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa display ID: :0 screens: 1 Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.2x8.0") s-diag: 414mm (16.3") Monitor-1: LVDS-1 res: 1366x768 hz: 60 dpi: 125 size: 277x156mm (10.9x6.1") diag: 318mm (12.5") OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) v: 3.3 Mesa 20.3.5 compat-v: 3.0 direct render: Yes > 2-pastebin Xorg.0.log from either /var/log/ or ~/.local/share/xorg/ and > provide > its URL. /var/log/Xorg.0.log https://paste.debian.net/plain/1295616 > Below in file named /etc/X11/xorg.conf.d/50-monitor.conf could be part of a > solution, with more information the above request would supply. > ... Thanks a lot for the proposed solutions. I'm gonna check them and read what's needed about X to try to put them at work. Hope there's more help I can get with the info just added. Kind regards!
Re: xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
riveravaldez composed on 2023-10-18 16:05 (UTC-0300): > Hi everybody, I'm having a resolution issue trying to connect an > external monitor to a laptop. ... > https://support.lenovo.com/us/en/solutions/pd015807-detailed-specifications-thinkpad-x220-tablet That URL covers multiple configurations, so we can't know all that is relevant from it. Using DP instead of VGA would likely solve this if your display had a DP input. :p VGA is analog. DP, HDMI, DVI are all digital. So is your CPU, GPU and software. The conversion to analog from digital typically is worse than flawless. That said, give us something to work from: 1-copy & paste input/output from inxi -GSaz run from an GUI terminal. 2-pastebin Xorg.0.log from either /var/log/ or ~/.local/share/xorg/ and provide its URL. Below in file named /etc/X11/xorg.conf.d/50-monitor.conf could be part of a solution, with more information the above request would supply. Section "Monitor" Identifier "ExtMonitor" VendorName "Samsung" ModelName "S20A300B" HorizSync 30-83 VertRefresh 56-76 Option "PreferredMode" "1600x900" EndSection This is essentially the information that the EDID from the Samsung should be supplying that X seems to be mishandling. The numbers for sync and ref are estimates, simply copied from a 2012 20" Dell 1600x900 I have here. With only one display it would be enough, but it needs to be assigned to the VGA port connection via another file, /etc/X11/xorg.conf.d/50-device.conf. The following might be enough: Section "Device" Identifier "ExtDevice" Option "monitor-VGA-1" "ExtMonitor" EndSection I've always been able to use files in /etc/X11/xorg.conf.d/ to manage unruly displays rather than resorting to CVT or GTF for manual modeline generation. X knows quite well how to generate appropriate modelines when it has the correct specifications to work with. EDID is supposed to do that. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
xrandr 1600x900 (ThinkPad X220T VGA-port) becomes 1440x900 (Samsung SyncMaster S20A300B)
Hi everybody, I'm having a resolution issue trying to connect an external monitor to a laptop. Laptop: ThinkPad X220T External Monitor: Samsung SyncMaster S20A300B Debian: 11.8 (bullseye), updated Connecting through laptop's VGA port (to VGA input in external monitor) everything works apparently normal except that I can't get the resolution right. Laptop goes at 1366x768, and monitor informs 1600x900 as optimal (which laptop's VGA-port should have no problem in providing, apparently[0]), but from xrandr that mode doesn't appears as automatically available. I've tried adding it by hand: $ cvt 1600 900 # 1600x900 59.95 Hz (CVT 1.44M9) hsync: 55.99 kHz; pclk: 118.25 MHz Modeline "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync $ xrandr --newmode "1600x900_60.00" 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync $ xrandr --addmode VGA-1 1600x900_60.00 $ xrandr --output VGA-1 --mode 1600x900_60.00 , but then the monitor informs it's receiving 1440x900, the GUI gets strangely distributed and image doesn't cover all of it (horizontally), while laptop's GUI suddenly extends beyond its display size. I've also tried with lower resolutions and, for instance, both 1440x768 and 1368x768 are informed by monitor as 1280x768 -but at least at 1368x768 both screens have same GUI distribution (consistent) except that monitor seems a little horizontally compressed... Any recommendation on how to make this work properly (I mean, to have full-surface image on monitor, without deformation, and at 1600x900)? Thanks a lot in advance! [0] https://support.lenovo.com/us/en/solutions/pd015807-detailed-specifications-thinkpad-x220-tablet
Thinkpad acpi_call not working on Debian Sid
Hi, I've been trying use certain features offered by tlp (like discharging and re-calibration) but getting an error. Did a little digging and found out some clues as to what's going on. output of "tlp-stat -b": > tpacpi-bat (acpi_call) = inactive (kernel error) searching in the logs using journalctl I got: > acpi_call: loading out-of-tree module taints kernel. > 440 kernel: acpi_call: module verification failed: signature and/or required key missing - tainting kernel I'm using a Thinkpad T440, secureboot disabled. Kernel: /5.15.0-2-amd64./ Is this a bug? // Regards, Apurv
Re: Problème avec un Lenovo Thinkpad 15v gen1
Bonsoir Nicolas,
Nicolas FRANCOIS, on 2021-09-26:
> Mon lycée m'a confié la bête sus-mentionnée. J'ai un gros problème avec
> cette bestiole, initialement fournie avec Window$ 10 : son écran. C'est
> un écran UHD, de résolution 3840*2160 (ils sont cinglés de mettre un
> tel écran, ça sert à RIEN sur un écran de 15.6" !!!).
>
> Résultat : avec XFCE, tout est MICROSCOPIQUE :-( Et je n'ai pas trouvé
> de solutions tout à fait satisfaisantes sur le net. J'ai réussi à
> forcer Grub à se lancer avec une police et une résolution correctes,
> mais le bureau XFCE reste quasiment illisible. Si je modifie certains
> réglages dans les paramètres (DPI, taille des polices système), cela
> change certaines choses, mais pas tout, donc c'est pas utilisable tel
> quel.
>
> Certains d'entre vous ont-ils réussi à rendre ce portable utilisable ?
Avec la dernière mouture de xfce4 pour debian 11, il y a une
option pour multiplier par deux la taille de la quasi-totalité
des éléments graphiques. C'est un peu caché :
- il faut lancer `xfce4-appearance-settings`
- et dans l'onglet "Paramètres" ("Settings"),
- passer le menu déroulant "Mise à l'échelle des fenêtres"
("Window Scaling") sur "2×".
Ceci dit, certaines bibliothèques graphique ne prennent pas en
charge la densité de pixels de l'écran, et peuvent donc avoir
tendance à rester illisibles ; je pense notamment à quelques
applications écrites en java, du type jconsole, mais j'en ai
peut-être loupé d'autres.
Bonne soirée, :)
--
.''`. Étienne Mollier
: :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
`. `' sent from /dev/pts/2, please excuse my verbosity
`-
signature.asc
Description: PGP signature
Re : Problème avec un Lenovo Thinkpad 15v gen1
Bonjour François. Le problème des écrans 4K n'est pas encore pris en compte par Debian, je m'en suis aperçu. Il y a plusieurs manières d'améliorer le problème. Tout d'abord au démarrage avec Grub, il faut modifier dans /etc/default/ le fichier grub : À la ligne qui traite de la résolution il faut mettre la variable GRUB_GFXPAYLOAD à 1280x720 ou 1024x768 ou 800x600 selon le résultat Exemple : GRUB_GFXPAYLOAD=1024x768 Puis une fois l'identification faite, il faut aller dans les réglages du panneau de configuration. Régler l'échelle à 300x comme cela a été dit est une solution, mais tu peux descendre car pour ma part à 175x, cela donne un bon résultat. Il faut aussi trouver à régler les polices et là tu peux y aller en passant les polices de 10pt à 16pt et les petites polices de 8pt à 14pt Puis il faut trouver les réglages des icônes et des curseurs pour les grossir. Selon les bureaux (KDE, XFCE, Gnome, ..., ces paramètres ne sont pas aux aux mêmes endroits. Cela ne t'empêchera pas d'avoir à régler certaines applications comme Inkscape pour laquelle, il faut régler la taille des icônes via le préférences de l'application. Bon courage Cassis - Mail d'origine - De: Nicolas FRANCOIS À: debian-user-french Envoyé: Sun, 26 Sep 2021 21:11:05 +0200 (CEST) Objet: Problème avec un Lenovo Thinkpad 15v gen1 Bonsoir. Mon lycée m'a confié la bête sus-mentionnée. J'ai un gros problème avec cette bestiole, initialement fournie avec Window$ 10 : son écran. C'est un écran UHD, de résolution 3840*2160 (ils sont cinglés de mettre un tel écran, ça sert à RIEN sur un écran de 15.6" !!!). Résultat : avec XFCE, tout est MICROSCOPIQUE :-( Et je n'ai pas trouvé de solutions tout à fait satisfaisantes sur le net. J'ai réussi à forcer Grub à se lancer avec une police et une résolution correctes, mais le bureau XFCE reste quasiment illisible. Si je modifie certains réglages dans les paramètres (DPI, taille des polices système), cela change certaines choses, mais pas tout, donc c'est pas utilisable tel quel. Certains d'entre vous ont-ils réussi à rendre ce portable utilisable ? Si oui, vos lumières sont les bienvenues, et ma gratitude éternelle promise ;-) \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin
Re: Problème avec un Lenovo Thinkpad 15v gen1
Le Mon, 27 Sep 2021 11:57:13 +, Hugues Larrive a écrit : > Le plus simple c'est probablement de configurer l'affichage en > 1920x1080, comme c'est pile la moitié ça devrait rester > parfaitement net. C'est une excellente idée, je m'étonne de ne pas l'avoir eue moi-même :-) Merci à tous les contributeurs pour leurs lumières. Et oui, j'ai des yeux qui vieillissent :-( \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin
Re : Re: Problème avec un Lenovo Thinkpad 15v gen1
Le lundi 27 septembre 2021 à 05:52, Basile Starynkevitch a écrit : > On 26/09/2021 21:11, Nicolas FRANCOIS wrote: > > > Bonsoir. > > > > Mon lycée m'a confié la bête sus-mentionnée. J'ai un gros problème avec > > > > cette bestiole, initialement fournie avec Window$ 10 : son écran. C'est > > > > un écran UHD, de résolution 3840*2160 (ils sont cinglés de mettre un > > > > tel écran, ça sert à RIEN sur un écran de 15.6" !!!). > > Je suis en désaccord. Avec de bon yeux et pour certaines applications > > graphiques (par exemple la CAO ou le dessin), une haute résolution est > > utile. > Ça fait des pixels de 0,9mm discernables jusqu'à une distance de 31cm avec une acuité de 10/10. Non seulement c'est inutile mais c'est même mauvais pour la santé (mettez le portable sur vos genoux et placez vos yeux à 30 cm de l'écran afin de distinguer les détails...) Pour la CAO ? Si on vous vendais une imprimante A4 en vous disant qu'elle a la même résolution qu'une A2 vous diriez probablement "non, A4 c'est trop petit pour mes plans". En 15,6" 1920x1080 c'est déjà limite pour la plupart des gens avec de bons yeux. Le plus simple c'est probablement de configurer l'affichage en 1920x1080, comme c'est pile la moitié ça devrait rester parfaitement net. publickey - hlarrive@pm.me - 0xE9429B87.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: Problème avec un Lenovo Thinkpad 15v gen1
Le dimanche 26 septembre 2021 à 21:11 +0200, Nicolas FRANCOIS a écrit : > Bonsoir. > > Mon lycée m'a confié la bête sus-mentionnée. J'ai un gros problème > avec > cette bestiole, initialement fournie avec Window$ 10 : son écran. > C'est > un écran UHD, de résolution 3840*2160 (ils sont cinglés de mettre un > tel écran, ça sert à RIEN sur un écran de 15.6" !!!). Qui peut le plus peut le moins, je suppose qu'on peut avoir un meilleur piqué, et ça a peut-être plus d'intérêt associé à un grand écran externe dans la même résolution. Bref, une résolution ça se change, si tu n'en n'a pas l'usage, plutôt que bricoler les tailles, tu peux baisser la résolution, les écrans et cartes graphiques savent gérer plusieurs résolutions. Enfin, je ne sais pas si sur XFCE tu as ce paramètre, mais il doit se trouver dans Gnome et Cinnamon : Double (Hi-DPI)
Re: Problème avec un Lenovo Thinkpad 15v gen1
On 26/09/2021 21:11, Nicolas FRANCOIS wrote: Résultat : avec XFCE, tout est MICROSCOPIQUE :-( Et je n'ai pas trouvé de solutions tout à fait satisfaisantes sur le net. J'ai réussi à forcer Grub à se lancer avec une police et une résolution correctes, mais le bureau XFCE reste quasiment illisible. Dans ton .bashrc, tu peux utiliser: xrandr --scale-from -- Fabien
Re: Problème avec un Lenovo Thinkpad 15v gen1
On 26/09/2021 21:11, Nicolas FRANCOIS wrote: Bonsoir. Mon lycée m'a confié la bête sus-mentionnée. J'ai un gros problème avec cette bestiole, initialement fournie avec Window$ 10 : son écran. C'est un écran UHD, de résolution 3840*2160 (ils sont cinglés de mettre un tel écran, ça sert à RIEN sur un écran de 15.6" !!!). Je suis en désaccord. Avec de bon yeux et pour certaines applications graphiques (par exemple la CAO ou le dessin), une haute résolution est utile. Résultat : avec XFCE, tout est MICROSCOPIQUE :-( Et je n'ai pas trouvé de solutions tout à fait satisfaisantes sur le net. J'ai réussi à forcer Grub à se lancer avec une police et une résolution correctes, mais le bureau XFCE reste quasiment illisible. Si je modifie certains réglages dans les paramètres (DPI, taille des polices système), cela change certaines choses, mais pas tout, donc c'est pas utilisable tel quel. Certains d'entre vous ont-ils réussi à rendre ce portable utilisable ? Si oui, vos lumières sont les bienvenues, et ma gratitude éternelle promise ;-) Est-ce que ce portable boote sans système graphique (ni X11, ni Wayland)? On peut essayer par exemple d'enfoncer Alt+Ctrl+F3 (ou bien F4 ou F5 ou F6 au lieu de F3). Avec de la chance, on a alors une interface en ligne de commande et probablement une police petite mais lisible -- Basile Starynkevitch (only mine opinions / les opinions sont miennes uniquement) 92340 Bourg-la-Reine, France web page: starynkevitch.net/Basile/
Re: Problème avec un Lenovo Thinkpad 15v gen1
Bonsoir Le 26/09/2021 à 21:11, Nicolas FRANCOIS a écrit : Bonsoir. Mon lycée m'a confié la bête sus-mentionnée. J'ai un gros problème avec cette bestiole, initialement fournie avec Window$ 10 : son écran. C'est un écran UHD, de résolution 3840*2160 (ils sont cinglés de mettre un tel écran, ça sert à RIEN sur un écran de 15.6" !!!). Résultat : avec XFCE, tout est MICROSCOPIQUE :-( Et je n'ai pas trouvé de solutions tout à fait satisfaisantes sur le net. J'ai réussi à forcer Grub à se lancer avec une police et une résolution correctes, mais le bureau XFCE reste quasiment illisible. Si je modifie certains réglages dans les paramètres (DPI, taille des polices système), cela change certaines choses, mais pas tout, donc c'est pas utilisable tel quel. Certains d'entre vous ont-ils réussi à rendre ce portable utilisable ? Si oui, vos lumières sont les bienvenues, et ma gratitude éternelle promise ;-) J'ai cette résolution sur mon portable at ai réglé dans les paramètres écran (Ubuntu 20) l'échelle à 300%. Une autre solution testée qui me convenanit moins était de jouer avec l'accès universel => grand texte & zoom -- Daniel
Problème avec un Lenovo Thinkpad 15v gen1
Bonsoir. Mon lycée m'a confié la bête sus-mentionnée. J'ai un gros problème avec cette bestiole, initialement fournie avec Window$ 10 : son écran. C'est un écran UHD, de résolution 3840*2160 (ils sont cinglés de mettre un tel écran, ça sert à RIEN sur un écran de 15.6" !!!). Résultat : avec XFCE, tout est MICROSCOPIQUE :-( Et je n'ai pas trouvé de solutions tout à fait satisfaisantes sur le net. J'ai réussi à forcer Grub à se lancer avec une police et une résolution correctes, mais le bureau XFCE reste quasiment illisible. Si je modifie certains réglages dans les paramètres (DPI, taille des polices système), cela change certaines choses, mais pas tout, donc c'est pas utilisable tel quel. Certains d'entre vous ont-ils réussi à rendre ce portable utilisable ? Si oui, vos lumières sont les bienvenues, et ma gratitude éternelle promise ;-) \bye -- Nicolas FRANCOIS | /\ http://nicolas.francois.free.fr | |__| X--/\\ We are the Micro$oft. _\_V Resistance is futile. You will be assimilated. darthvader penguin
Re: Video hangs on ThinkPad X220 T
riveravaldez (12021-03-26): > debian kernel: i915 :00:02.0: [drm] GPU HANG: ecode 6:1:85fc, > in eadedCompositor [10433] > debian kernel: i915 :00:02.0: [drm] Resetting chip for stopped > heartbeat on rcs0 > debian kernel: i915 :00:02.0: [drm] eadedCompositor[10433] context > reset due to GPU hang > > Any idea what to do/where to look? > > Sometimes you get logged-off from your session and put back to the DM > log-in screen. Other times you have to kill the WM from another tty and then > re-log. Everything else seems ok. There is a rather severe glitch with the i915 driver and 5.10 kernels that has very similar effects. If this you are using a 5.10 kernel, try rebooting on a 5.9, for me it fixed the issue (20 days and counting). Regards, -- Nicolas George signature.asc Description: PGP signature
Re: Video hangs on ThinkPad X220 T
riveravaldez composed on 2021-03-26 23:23 (UTC-0300): > Any idea what to do/where to look? Any chance the cooling system needs cleaning? Are you using a display manager (login greeter) to launch? There are two DDX drivers applicable to your (>9 years old) Sandy Bridge IGP: intel modesetting If xserver-xorg-video-intel is installed, typically its provided intel DDX will be employed. Without it, normally modesetting will be employed, a component of the server .deb, and the upstream default. xserver-xorg-video-intel is informally deprecated, getting mostly only bug fixes for the past 7 years, and no official release since then. A look through /var/log/Xorg.0.log should make it obvious which is in use, lots of intel(0) strings or lots of modeset(0) strings, but not both. Sometimes one may find an override specification either in /etc/X11/xorg.conf or in /etc/X11/xorg.conf.d/25-intel.conf or other xorg.conf.d/*conf. Try switching from one DDX to the other. Which kernel, 5.10.x, or 5.11.x? If the latter, try a 5.10.x if you can, or at least an older 5.11.x. In none of this helps: pastebinit /var/log/Xorg.0.log and share here the resulting URL. If /var/log/Xorg.0.log is absent, look in ~/.local/share/xorg/ for it. -- Evolution as taught in public schools, like religion, is based on faith, not on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Video hangs on ThinkPad X220 T
Hi, I'm having what I suppose are random (not frequent) video server hangs. This is a ThinkPad X220 T with Debian Testing and: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) I'm using IceWM here, but not sure if that's relevant. The symptoms are that randomly screen image gets frozen, but with some (also random) little variations, but mostly frozen, meanwhile everything else in the system seems to keep working fine, even the WM keyboard shortcuts (but you have to imagine what's happening, of course). Only thing I found that seems apparently relevant in both `sudo journalctl` and `sudo dmesg` is: debian kernel: i915 :00:02.0: [drm] GPU HANG: ecode 6:1:85fc, in eadedCompositor [10433] debian kernel: i915 :00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0 debian kernel: i915 :00:02.0: [drm] eadedCompositor[10433] context reset due to GPU hang Any idea what to do/where to look? Sometimes you get logged-off from your session and put back to the DM log-in screen. Other times you have to kill the WM from another tty and then re-log. Everything else seems ok. Thanks a lot in advance for any help.
Re: Follow up, was: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Andrei POPESCU wrote: > Try comparing kernel messages (dmesg). Or install the old kernel image into the buster and try to eliminate or confirm it depends on library or on kernel driver. >From what I read it is kernel driver issue and it was fixed, then broken then fixed, then broken etc.
Re: Follow up, was: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
On Lu, 18 ian 21, 14:09:17, Ottavio Caruso wrote: > > I have a usb flash drive with an old (2 years or so) Debian Testing image > (Buster, which in the meantime is stable) running kernel 4.9.0-14 (same as > the one I'm currently running now, but probably built on top of different > libraries). I installed cheese and the webcam was recognized instantly. I > played around with it for a bit and even shook the laptop, just to see if > there was a problem with some internal cable and the camera was still > working. > > I don't know what to make of it. This rules out a possible hardware problem; > but also a problem with that kernel series? Try comparing kernel messages (dmesg). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
On Jo, 07 ian 21, 23:35:23, Ottavio Caruso wrote: > > Thanks. So, this is the list of all linux-image-amd64: > https://snapshot.debian.org/binary/linux-image-amd64/ You might want to read the description for 'linux-image-amd64' first ;) > Which one should I install? Which was the first kernel that came with > Stretch? The exact version that was released with stretch might be difficult to find out. A good approximation would be to search for the first Debian Security Advisory (DSA) for linux in stretch, it will mention the next higher version. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Ottavio Caruso wrote: > Thanks. So, this is the list of all linux-image-amd64: > https://snapshot.debian.org/binary/linux-image-amd64/ > > Which one should I install? Which was the first kernel that came with > Stretch? Otavio, come on, does google not work on your PC? https://wiki.debian.org/DebianStretch says 4.9 and 4.10, but even without this you can find the images based on the debian version. 4.9+80+deb9u12 (source: linux-latest 80+deb9u12) 4.9+80+deb9u11 (source: linux-latest 80+deb9u11) 4.9+80+deb9u10 (source: linux-latest 80+deb9u10) 4.9+80+deb9u9 (source: linux-latest 80+deb9u9) 4.9+80+deb9u8 (source: linux-latest 80+deb9u8) 4.9+80+deb9u7 (source: linux-latest 80+deb9u7) 4.9+80+deb9u6 (source: linux-latest 80+deb9u6) 4.9+80+deb9u5 (source: linux-latest 80+deb9u5) 4.9+80+deb9u4 (source: linux-latest 80+deb9u4) 4.9+80+deb9u3 (source: linux-latest 80+deb9u3) 4.9+80+deb9u2 (source: linux-latest 80+deb9u2) 4.9+80+deb9u1 (source: linux-latest 80+deb9u1)
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
On Thu, Jan 07, 2021 at 09:44:49AM +0100, deloptes wrote: > Andrei POPESCU wrote: > > > Some of us do need the webcam for video calls / conferences ;) > > (family, friends or work) > > > > Andrei, forgive me the the joke, but I doubt you are a model or movie star, > I would insist looking at :D - same for me :D. > I understand this but do not understand completely why would this be > mandatory. > > > > There are also much more elegant solutions (just an example): > > > > https://shop.protonmail.com/products/webcam-cover > > another one made out of plastic and in China - pfui! [...] A while ago, one of our local geekspace presented a clever origami-like scheme to make such a retractable cover out of post-it notes [1]. The sticker part sticks to the laptop bezel and it has a sliding part to open and close the lid. Text is in German, but it should be easy to follow without the language. Cheers [1] https://quotes.yourdictionary.com/author/quotes/194924 - t signature.asc Description: Digital signature
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
On Jo, 07 ian 21, 14:22:30, deloptes wrote: > Andrei POPESCU wrote: > > > Typically a Debian release should run with the kernel from the previous > > release (makes dist-upgrade easier), specific exceptions are mentioned > > in the Release Notes. > > > > If possible you should stick with kernels from the LTS project (as far > > as I know stretch is still supported). > > > > For testing purposes you can find all Debian packages ever uploaded to > > the archive at https://snapshot.debian.org. > > but Otavio is looking for older kernel and I looked for such few weeks ago > and couldn't find such. http://snapshot.debian.org/package/linux/ (unless you know the exact package name search by source package name) > I would try jessie > http://ftp.at.debian.org/debian/pool/main/l/linux/kernel-image-3.16.0-6-amd64-di_3.16.56-1+deb8u1_amd64.udeb > > if this is what you mean that it should work with older release That is a special kernel for the Debian Installed (note the -di in the name) Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Andrei POPESCU wrote: > Typically a Debian release should run with the kernel from the previous > release (makes dist-upgrade easier), specific exceptions are mentioned > in the Release Notes. > > If possible you should stick with kernels from the LTS project (as far > as I know stretch is still supported). > > For testing purposes you can find all Debian packages ever uploaded to > the archive at https://snapshot.debian.org. but Otavio is looking for older kernel and I looked for such few weeks ago and couldn't find such. I would try jessie http://ftp.at.debian.org/debian/pool/main/l/linux/kernel-image-3.16.0-6-amd64-di_3.16.56-1+deb8u1_amd64.udeb if this is what you mean that it should work with older release
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
On Thu, 7 Jan 2021 09:37:42 +0200 Andrei POPESCU wrote: > On Jo, 07 ian 21, 02:06:33, deloptes wrote: > > > > I'm just wondering why one would want to have a spy cam on his notebook > > working. In the company everybody glue something on the webcam or painted > > it with permanent black. > > At home - audio is off and the webcam is fully covered as well. > > ... but in the case it is your privacy matter. > > Some of us do need the webcam for video calls / conferences ;) > (family, friends or work) > > There are also much more elegant solutions (just an example): > > https://shop.protonmail.com/products/webcam-cover Yes. And what does "audio is off" mean - is the microphone physically sound-shielded, or just disabled in software (on some level of the system)? If the latter, why shouldn't that suffice for the camera as well? Celejar
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
On Jo, 07 ian 21, 09:37:10, Ottavio Caruso wrote: > On 07/01/2021 01:06, deloptes wrote: > > Ottavio Caruso wrote: > > > > > In this case, what's the oldest kernel I can install on Stretch? > > you mean the most recent? > > No, I mean the opposite. The oldest that can be installed on Stretch Because > I didn't have a problem with older kernels. I must have uninstalled some of > the oldest kernel I had. At the moment I have: > > > $ dpkg -l|grep linux-image > ii linux-image-4.19.0-0.bpo.9-amd64 4.19.118-2+deb10u1~bpo9+1 > amd64Linux 4.19 for 64-bit PCs (signed) > ii linux-image-4.9.0-11-amd644.9.189-3+deb9u2 amd64 > Linux 4.9 for 64-bit PCs > ii linux-image-4.9.0-12-amd644.9.210-1+deb9u1 amd64 > Linux 4.9 for 64-bit PCs > ii linux-image-4.9.0-14-amd644.9.246-2 amd64Linux > 4.9 for 64-bit PCs > ii linux-image-amd64 4.19+105+deb10u4~bpo9+1 > amd64Linux for 64-bit PCs (meta-package) Typically a Debian release should run with the kernel from the previous release (makes dist-upgrade easier), specific exceptions are mentioned in the Release Notes. If possible you should stick with kernels from the LTS project (as far as I know stretch is still supported). For testing purposes you can find all Debian packages ever uploaded to the archive at https://snapshot.debian.org. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Ottavio Caruso wrote: > No, I mean the opposite. The oldest that can be installed on Stretch > Because I didn't have a problem with older kernels. I must have > uninstalled some of the oldest kernel I had. At the moment I have: > from what I read you need a 3.x kernel to be sure it works. Last time I checked the kernels in backports I couldn't find older one ... but there are bugs one would not want to have ... I can't help - sorry.
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Andrei POPESCU wrote: > Some of us do need the webcam for video calls / conferences ;) > (family, friends or work) > Andrei, forgive me the the joke, but I doubt you are a model or movie star, I would insist looking at :D - same for me :D. I understand this but do not understand completely why would this be mandatory. > There are also much more elegant solutions (just an example): > > https://shop.protonmail.com/products/webcam-cover another one made out of plastic and in China - pfui! My solution is displaceable and replaceable piece of paper with duct tape. It has even lower CO2 footprint :D
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
On Jo, 07 ian 21, 02:06:33, deloptes wrote: > > I'm just wondering why one would want to have a spy cam on his notebook > working. In the company everybody glue something on the webcam or painted > it with permanent black. > At home - audio is off and the webcam is fully covered as well. > ... but in the case it is your privacy matter. Some of us do need the webcam for video calls / conferences ;) (family, friends or work) There are also much more elegant solutions (just an example): https://shop.protonmail.com/products/webcam-cover Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Ottavio Caruso wrote: > In this case, what's the oldest kernel I can install on Stretch? you mean the most recent? I don't know - it looks like there is no solution though as even in later 5.6 similar issues are reported. The latest stable kernel is 5.10.5 https://www.kernel.org/ Better think of subscribing some kernel list and asking there for instructions. I would patch/compile the latest kernel nice make -j`nproc` bindeb-pkg https://wiki.debian.org/BuildADebianKernelPackage I am not authorized by any entity to tell you what to do - may be there are better ideas around. I just remember struggling with similar issue years ago. You either 1. get your hands dirty (means you debug and probably solve the issue yourself) 2. get into alliance with the kernel guys (if you are lucky to find someone to help do the dirty work for or with you - chances are good as it seems they are working on that) 3. let the kernel guys do the dirty work (follow the commits on the uvcvideo) and just test and keep what is good for you https://bugzilla.kernel.org/show_bug.cgi?id=111291#c20 here the guy says it was working with pre v4 kernel. May be try some liveCD/USB. I'm just wondering why one would want to have a spy cam on his notebook working. In the company everybody glue something on the webcam or painted it with permanent black. At home - audio is off and the webcam is fully covered as well. ... but in the case it is your privacy matter.
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Ottavio Caruso wrote: > [18820.144438] uvcvideo: Found UVC 1.00 device Integrated Camera > [(5986:0299) 18820.147743] uvcvideo 2-4:1.0: Entity type for entity > [Processing 2 was > not initialized! > [18820.147758] uvcvideo 2-4:1.0: Entity type for entity Camera 1 was not > initialized! > [18820.147768] uvcvideo 2-4:1.0: Entity type for entity Extension 4 was > not initialized! > [18820.148049] input: Integrated Camera: Integrated C as > /devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/input/input78 So - briefly no luck :/ you better follow the kernel guys - there might be patch or something that works for you. Sorry, but there are often issues with integrated stuff.
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Ottavio Caruso wrote: > Thanks. This is the dmesg log while giving the 2 commands as above: > > After `sudo rmmod uvcvideo`: > [15630.304614] usbcore: deregistering interface driver uvcvideo > > After `sudo modprobe -v uvcvideo`: > > [15651.636552] uvcvideo: Found UVC 1.00 device Integrated Camera > [(5986:0299) 15651.639063] uvcvideo 2-4:1.0: Entity type for entity > [Processing 2 was > not initialized! > [15651.639074] uvcvideo 2-4:1.0: Entity type for entity Camera 1 was not > initialized! > [15651.639082] uvcvideo 2-4:1.0: Entity type for entity Extension 4 was > not initialized! > [15651.639381] input: Integrated Camera: Integrated C as > /devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/input/input67 > [15651.639689] usbcore: registered new interface driver uvcvideo > [15651.639698] USB Video Class driver (1.1.1) > > > > I'll try again from a live usb image. may be it will not help as looking for the output I find this bug report still in recent kernels. https://bugzilla.kernel.org/show_bug.cgi?id=111291 And a proposed solution https://bbs.archlinux.org/viewtopic.php?id=259134
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Ottavio Caruso wrote: > I have installed uvcdynctrl, but I don't know what to make of its output: > > $ sudo uvcdynctrl -l > Listing available devices: > video0 Integrated Camera: Integrated C > Media controller device: /dev/media0 > Entity 1: Integrated Camera: Integrated C. Type: 65537, Revision: > 0, Flags: 1, Group-id: 0, Pads: 1, Links: 0 > Device node > Entity: 1, Pad 0, Flags: 1 > video1 Integrated Camera: Integrated C > Media controller device /dev/media1 doesn't exist > ERROR: Unable to list device entities: Invalid device or device cannot > be opened. (Code: 5) and there is again this? uvcvideo: Failed to resubmit video URB (-19) can you try unloading uvcvideo and loading it again? sudo rmmod uvcvideo sudo modprobe -v uvcvideo if this does not help - try some live USB distro and check if it works. It could be anywhere from the hardware/bios through firmware, kernel and udev
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Ottavio Caruso wrote: > I've added the stretch-backports repos and installed the new kernel and > headers: > > $ uname -r > 4.19.0-0.bpo.9-amd64 > > But it doesn't seem to have sorted much out. The camera gets recognised > for a few minutes and then it stops. > I just did a search in google for TP 130 https://wiki.debian.org/InstallingDebianOn/Thinkpad/Edge-E130/wheezy http://linux-hardware.org/index.php?id=usb:5986-0299 It looks like it is supported since wheezy and reported to be recognized up to kernel 5.10. If it does not work - either there is something else or a regression. Something else could be udev or some other subsystem that messes up. especially "[ 83.457152] uvcvideo: Failed to resubmit video URB (-19)." Ubuntu users report solving similar issue with uvcdynctrl https://askubuntu.com/questions/1214794/usb-camera-is-not-detected-anymore
Re: Audio broken on Lenovo ThinkPad T14 by recent upgrade on testing
On Lu, 04 ian 21, 21:57:20, Patrick Elsen wrote: > Hey all, > > I'm not sure if this is the right way or place to report this, but I've > been running Debian bullseye (Testing) for some months now and it's > been a really great experience, everything works out of the box > (backlight, suspend, display brightness control, switching between > speakers and headphones when plugged in). > > However, in a recent update, my audio has been broken. Now, I have > three outputs that I didn't have before (labelled HDMI1, HDMI2, HDMI3), > it doesn't recognize my internal speakers or headphones anymore, > meaning that audio playback is completely broken. What does 'aplay -l' and 'aplay -L' show? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Audio broken on Lenovo ThinkPad T14 by recent upgrade on testing
Patrick Elsen writes: > Hey all, > > I'm not sure if this is the right way or place to report this, but I've > been running Debian bullseye (Testing) for some months now and it's > been a really great experience, everything works out of the box > (backlight, suspend, display brightness control, switching between > speakers and headphones when plugged in). > > However, in a recent update, my audio has been broken. Now, I have > three outputs that I didn't have before (labelled HDMI1, HDMI2, HDMI3), > it doesn't recognize my internal speakers or headphones anymore, > meaning that audio playback is completely broken. > > I don't know what package specfically is responsible, but I have > attached the /var/log/apt/history.log entry that was the update that I > think bricked things. I can provide more logs and information if > needed. > > My guess would be that alsa-topology-conf or alsa-ucm-conf are the > culprit, because those two are the only ones I see that are related to > sound and audio things? > > Maybe someone here can help me or look into it. Dear Patrick, Please forgive me to say off-topic. At past days, me also did try to hard linux install. Especially i always did fail to setup device driver correctly. So someday i did make chage the strategy. Chromebook is already to finished them. So i don't have the stress to setup drivers in linux installation. Then i only have to just software such as emacs, firefox, gitlab, etc, ... So i am happy now with no-stress furthermore i have plan to buy new thinkpad-chromebook [zork-morphius]. At there i will install the great *Bullseye*. (currently i am on Ubuntu 18.04 under chromebook [oak-birch]) Sincerely, Linux fan Byung-Hee -- ^고맙습니다 _救濟蒼生_ 감사합니다_^))//
Audio broken on Lenovo ThinkPad T14 by recent upgrade on testing
Hey all, I'm not sure if this is the right way or place to report this, but I've been running Debian bullseye (Testing) for some months now and it's been a really great experience, everything works out of the box (backlight, suspend, display brightness control, switching between speakers and headphones when plugged in). However, in a recent update, my audio has been broken. Now, I have three outputs that I didn't have before (labelled HDMI1, HDMI2, HDMI3), it doesn't recognize my internal speakers or headphones anymore, meaning that audio playback is completely broken. I don't know what package specfically is responsible, but I have attached the /var/log/apt/history.log entry that was the update that I think bricked things. I can provide more logs and information if needed. My guess would be that alsa-topology-conf or alsa-ucm-conf are the culprit, because those two are the only ones I see that are related to sound and audio things? Maybe someone here can help me or look into it. Cheers, -Patrick Start-Date: 2020-12-27 23:06:21 Commandline: apt upgrade Requested-By: patrick (1000) Install: libdeflate0:amd64 (1.6-1, automatic), libadwaitaqtpriv1:amd64 (1.2.0-2, automatic), llvm-11-runtime:amd64 (1:11.0.0-5+b1, automatic), libges-1.0-0:amd64 (1.18.2-1, automatic), libgit2-1.1:amd64 (1.1.0+dfsg.1-2, automatic), liblist-moreutils-xs-perl:amd64 (0.430-2, automatic), containerd:amd64 (1.4.3~ds1-1, automatic), libboost-locale1.74.0:amd64 (1.74.0-3+b1, automatic), libadwaitaqt1:amd64 (1.2.0-2, automatic), llvm-11-dev:amd64 (1:11.0.0-5+b1, automatic), gedit-plugin-text-size:amd64 (3.38.1-1, automatic), libplymouth5:amd64 (0.9.5-2, automatic), libxkbregistry0:amd64 (1.0.3-2, automatic), clang-format-11:amd64 (1:11.0.0-5+b1, automatic), ruby-rubygems:amd64 (3.2.0~rc.2-5, automatic), llvm-11-tools:amd64 (1:11.0.0-5+b1, automatic), linux-image-5.9.0-5-amd64:amd64 (5.9.15-1, automatic), llvm-11:amd64 (1:11.0.0-5+b1, automatic) Upgrade: speech-dispatcher-espeak-ng:amd64 (0.10.2-1, 0.10.2-2), gir1.2-lokdocview-0.1:amd64 (1:7.0.3-4+b1, 1:7.0.4~rc2-1+b1), speech-dispatcher-audio-plugins:amd64 (0.10.2-1, 0.10.2-2), fdisk:amd64 (2.36.1-2, 2.36.1-3), alsa-topology-conf:amd64 (1.2.3-1, 1.2.4-1), texlive-plain-generic:amd64 (2020.20200925-1, 2020.20201129-2), node-os-locale:amd64 (4.0.0-1, 5.0.0-1), libjson-glib-1.0-0:amd64 (1.6.0-1, 1.6.0-2), libxencall1:amd64 (4.14.0+80-gd101b417b7-1, 4.14.0+88-g1d1d1f5391-2), manpages:amd64 (5.09-2, 5.10-1), perl-base:amd64 (5.32.0-5, 5.32.0-6), init:amd64 (1.59, 1.60), libreoffice-math:amd64 (1:7.0.3-4+b1, 1:7.0.4~rc2-1+b1), init-system-helpers:amd64 (1.59, 1.60), libssh2-1:amd64 (1.8.0-2.1, 1.9.0-2), node-resolve:amd64 (1.19.0+~cs4.20.2-1, 1.19.0+~cs5.20.8-2), aspell-pt-pt:amd64 (20201103-2, 20201212-1), libgovirt2:amd64 (0.3.7-1, 0.3.7-2), python3-pyside2.qtwidgets:amd64 (5.15.0-5+b1, 5.15.0-6), liblibreoffice-java:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1), fonts-lyx:amd64 (2.3.5.2-1, 2.3.6-1), bsdextrautils:amd64 (2.36.1-2, 2.36.1-3), python3-cupshelpers:amd64 (1.5.12-1, 1.5.13-1), texlive-metapost-doc:amd64 (2020.20200925-1, 2020.20201203-2), texlive-font-utils:amd64 (2020.20201129-1, 2020.20201129-2), texlive-lang-spanish:amd64 (2020.20200925-2, 2020.20201129-1), libseccomp2:amd64 (2.5.0-3+b1, 2.5.1-1), util-linux-locales:amd64 (2.36.1-2, 2.36.1-3), libencode-locale-perl:amd64 (1.05-1, 1.05-1.1), texlive-publishers-doc:amd64 (2020.20201129-1, 2020.20201129-2), uno-libs-private:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1+b1), libao4:amd64 (1.2.2+20180113-1+b1, 1.2.2+20180113-1.1), libaudit-common:amd64 (1:2.8.5-3.1, 1:3.0-1), uim-data:amd64 (1:1.8.8-6.1, 1:1.8.8-7), adwaita-qt:amd64 (1.1.4-1, 1.2.0-2), uim-fep:amd64 (1:1.8.8-6.1+b2, 1:1.8.8-7), texlive-latex-base:amd64 (2020.20200925-1, 2020.20201203-2), uuid-runtime:amd64 (2.36.1-2, 2.36.1-3), libquvi-scripts-0.9:amd64 (0.9.20131130-1.1, 0.9.20131130-1.2), libqt5multimediagsttools5:amd64 (5.15.1-2, 5.15.2-2), python3-zope.interface:amd64 (5.1.2-1, 5.1.2-1+b1), iportuguese:amd64 (20201103-2, 20201212-1), libfdisk1:amd64 (2.36.1-1, 2.36.1-3), publicsuffix:amd64 (20200729.1725-1, 20201215.0006-1), javascript-common:amd64 (11, 11+nmu1), libauthen-sasl-perl:amd64 (2.1600-1, 2.1600-1.1), libdrm-nouveau2:amd64 (2.4.103-1, 2.4.103-2), osinfo-db:amd64 (0.20201119-1, 0.20201218-1), hunspell-fr:amd64 (1:6.4.1-1, 1:7.0-1), libreoffice-l10n-zh-cn:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1), libridl-java:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1), node-jquery:amd64 (3.5.1+dfsg+~3.5.4-2, 3.5.1+dfsg+~3.5.4-3), librygel-renderer-gst-2.6-2:amd64 (0.38.3-1, 0.40.0-1), libreoffice-l10n-zh-tw:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1), linux-libc-dev:amd64 (5.9.9-1, 5.9.15-1), liblist-moreutils-perl:amd64 (0.416-1+b6, 0.430-2), libxml-sax-base-perl:amd64 (1.09-1, 1.09-1.1), libpython3.8-dev:amd64 (3.8.6-1, 3.8.7-1), llvm:amd64 (1:9.0-49.1, 1:11.0-51+nmu1), alsa-ucm-conf:amd64 (1.2.3-1, 1.2.4-1), feynmf:amd64 (1.08-11, 1.08-12),
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Dan Ritter wrote: > If you absolutely need a working camera as soon as possible, buy > a new USB camera. but the subject says it is integrated. I suggest just install a new kernel (may be from back ports if available and you want to stay on stretch) you can compile new kernel or simply upgrade to buster.
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
Ottavio Caruso wrote: > https://paste.debian.net/plainh/1c22d1aa Your kernel believes you have two video cameras, one named Trust. They have different USB ids. They both get recognized repeatedly in your snippet, but because there is not enough context, I can't tell whether that means - you put the laptop to sleep/wake. - the cameras were unplugged/replugged. - the kernel had an oops. If you absolutely need a working camera as soon as possible, buy a new USB camera. -dsr-
Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch
On 1/4/21 1:00 PM, Ottavio Caruso wrote: > Hi, > > $ uname -a > Linux e130 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64 > GNU/Linux > > $ cat /etc/debian_version > 9.13 > > $ inxi -M > Machine: > Type: Laptop System: LENOVO product: 33588QG v: ThinkPad Edge E130 > > I have had a problem with having the integrated webcam to be recognized > by various applications (cheese, Microsoft Teams [yes...], Zoom, etc). > It does work sometimes and it doesn't at other times. > > I have various kernels installed (4.9.0-11-amd64 all the way through > 4.9.0-14-amd64) and rebooting into each of these kernels won't make much > difference. > > I have uninstalled, purged and reinstalled build-essential > linux-headers-`uname -r` linux-image-amd64`uname -r` (for each of the > kernel versions) and usbutils, and I have also uninstalled tlp, but it > doesn't seems to make much difference. > > This is the full log of `dmesg|grep video` of today, when I had the last > failure: > > https://paste.debian.net/plainh/1c22d1aa > > I can't upgrade to Debian stable for a number of reasons that it will > take to long to explain and I have to stick with Stretch for the time > being. I've only had this problem for the last 6 months, presumably > after some upgrades. > > Any help will be appreciated. > > Hi Ottavio, if the issue with your camera is a kernel thing then you can install newer kernel from backports. According to this page - https://tracker.debian.org/pkg/linux Linux 4.19.118 is available for Debian 9. HTH Kind regards Georgi
Re: Trackpoint not work properly on Thinkpad T470
Thanks for the tip! I will have to check those out as well. I believe I did have the non free when I setup to ensure Wi-Fi support. I don't know if the miscellaneous non free was included with that build. I used an unofficial build from here using the netinst.iso writtento a USB. https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/amd64/iso-cd/ Here are my apt sources. Anything you think I should add? # deb cdrom:[Debian GNU/Linux 10.2.0 _Buster_ - Unofficial amd64 NETINST with firmware 20191116-09:56]/ buster contrib main non-free # deb cdrom:[Debian GNU/Linux 10.2.0 _Buster_ - Unofficial amd64 NETINST with firmware 20191116-09:56]/ buster contrib main non-free deb http://deb.debian.org/debian/ buster main non-free contrib deb-src http://deb.debian.org/debian/ buster main non-free contrib deb http://security.debian.org/debian-security buster/updates main contrib non-free deb-src http://security.debian.org/debian-security buster/updates main contrib non-free # buster-updates, previously known as 'volatile' deb http://deb.debian.org/debian/ buster-updates main contrib non-free deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free # This system was installed using small removable media # (e.g. netinst, live or single CD). The matching "deb cdrom" # entries were disabled at the end of the installation process. # For information about how to configure apt package sources, # see the sources.list(5) manual. deb [arch=amd64] https://download.docker.com/linux/debian buster stable # deb-src [arch=amd64] https://download.docker.com/linux/debian buster stable # deb-src [arch=amd64] https://download.docker.com/linux/debian buster stable On Sun, Sep 6, 2020, 9:50 AM Andrew Cater wrote: > Also - check carefully what firmware it might require. You have, for > example, installed firmware-linux-nonfree, firmware-misc-nonfree to enable > non-free firmware possibly? > > On Sat, Sep 5, 2020 at 10:12 PM riveravaldez > wrote: > >> On 9/5/20, rhkra...@gmail.com wrote: >> > On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote: >> >> Well, I don't think it's a hardware issue. The computer is less than a >> >> year old and it's been used sporadically over the last year. Any >> >> thoughts >> >> on how to rule hardware out as an issue? >> > >> > Oh, maybe one idea, did it come with Windows and is it still there (I >> mean, can you boot into Windows?) -- if so, do that, and try a similar app >> in Windows. >> > >> > In Linux, does the problem happen in only one application, or in other >> > applications as well? >> >> Basic thought: grab any-distro LiveUSB and boot from there and check >> if the issue persist. >> >> If any other OS makes the hardware works fine then at least that cause >> could be ruled out. >> >> Hope this help, best regards. >> >>
Re: Trackpoint not work properly on Thinkpad T470
Also - check carefully what firmware it might require. You have, for example, installed firmware-linux-nonfree, firmware-misc-nonfree to enable non-free firmware possibly? On Sat, Sep 5, 2020 at 10:12 PM riveravaldez wrote: > On 9/5/20, rhkra...@gmail.com wrote: > > On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote: > >> Well, I don't think it's a hardware issue. The computer is less than a > >> year old and it's been used sporadically over the last year. Any > >> thoughts > >> on how to rule hardware out as an issue? > > > > Oh, maybe one idea, did it come with Windows and is it still there (I > mean, can you boot into Windows?) -- if so, do that, and try a similar app > in Windows. > > > > In Linux, does the problem happen in only one application, or in other > > applications as well? > > Basic thought: grab any-distro LiveUSB and boot from there and check > if the issue persist. > > If any other OS makes the hardware works fine then at least that cause > could be ruled out. > > Hope this help, best regards. > >
Re: Trackpoint not work properly on Thinkpad T470
On 9/5/20, rhkra...@gmail.com wrote: > On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote: >> Well, I don't think it's a hardware issue. The computer is less than a >> year old and it's been used sporadically over the last year. Any >> thoughts >> on how to rule hardware out as an issue? > > Oh, maybe one idea, did it come with Windows and is it still there (I mean, > can you boot into Windows?) -- if so, do that, and try a similar app in > Windows. > > In Linux, does the problem happen in only one application, or in other > applications as well? Basic thought: grab any-distro LiveUSB and boot from there and check if the issue persist. If any other OS makes the hardware works fine then at least that cause could be ruled out. Hope this help, best regards.
Re: Trackpoint not work properly on Thinkpad T470
On Saturday, September 05, 2020 12:34:37 PM Aaron Elmquist wrote: > Well, I don't think it's a hardware issue. The computer is less than a > year old and it's been used sporadically over the last year. Any thoughts > on how to rule hardware out as an issue? Sorry, no, not off the top of my head, and no time to dig into it, atm. Oh, maybe one idea, did it come with Windows and is it still there (I mean, can you boot into Windows?) -- if so, do that, and try a similar app in Windows. In Linux, does the problem happen in only one application, or in other applications as well? I hope somebody else will be able to help you.
Re: Trackpoint not work properly on Thinkpad T470
Well, I don't think it's a hardware issue. The computer is less than a year old and it's been used sporadically over the last year. Any thoughts on how to rule hardware out as an issue? On Sat, Sep 5, 2020 at 6:18 AM wrote: > On Friday, September 04, 2020 07:55:43 PM Aaron Elmquist wrote: > > I'm on debian buster using KDE as my GUI. My trackpoint was working quite > > well until a month or two ago (maybe more). Now it has some odd behavior > > where it will snap to the bottom of the screen every so often when I'm > > using it. > > > > Seems like the input is very sensitive to the bottom direction. No > > snapping to any other location Really seems like the input in the down > > direction became overly sensitive. I can't really control the rate of a > > downward cursor movement consistently. It's just to fast from time to > > time. > > > > Any help would be appreciated. I would provide more details, configs, > > etc., but I'm not really sure what's relevant. > > I suspect you suspect the same thing I do, that it is a hardware problem. > > I don't have any idea how hard it may be to get or to replace a trackpoint > -- > you may have to replace the entire keyboard as a unit, which may not be > all > that hard. > > If it were mine, I would look for an external tracking device (mouse, > trackball, ???) and start using it instead of the trackpoint. For > traveling, > there are some very small mice available. > >
Re: Trackpoint not work properly on Thinkpad T470
On Friday, September 04, 2020 07:55:43 PM Aaron Elmquist wrote: > I'm on debian buster using KDE as my GUI. My trackpoint was working quite > well until a month or two ago (maybe more). Now it has some odd behavior > where it will snap to the bottom of the screen every so often when I'm > using it. > > Seems like the input is very sensitive to the bottom direction. No > snapping to any other location Really seems like the input in the down > direction became overly sensitive. I can't really control the rate of a > downward cursor movement consistently. It's just to fast from time to > time. > > Any help would be appreciated. I would provide more details, configs, > etc., but I'm not really sure what's relevant. I suspect you suspect the same thing I do, that it is a hardware problem. I don't have any idea how hard it may be to get or to replace a trackpoint -- you may have to replace the entire keyboard as a unit, which may not be all that hard. If it were mine, I would look for an external tracking device (mouse, trackball, ???) and start using it instead of the trackpoint. For traveling, there are some very small mice available.
Trackpoint not work properly on Thinkpad T470
Hi, I'm on debian buster using KDE as my GUI. My trackpoint was working quite well until a month or two ago (maybe more). Now it has some odd behavior where it will snap to the bottom of the screen every so often when I'm using it. Seems like the input is very sensitive to the bottom direction. No snapping to any other location Really seems like the input in the down direction became overly sensitive. I can't really control the rate of a downward cursor movement consistently. It's just to fast from time to time. Any help would be appreciated. I would provide more details, configs, etc., but I'm not really sure what's relevant. Thanks, Aaron
Re: Sound issues on ThinkPad X220T (Lenovo)
Hi, For the record, I had the exact same problem on a computer running buster that I don't use very often. For sure, it was working fine even with timidity installed a few months ago. Many thanks to Andrei for the 'lsof | grep /dev/snd' command that pointed us in the right direction! Debugging these sound issues that appear spontaneously on a previously-working setup is not easy, especially now that PulseAudio is required everywhere. Regards -- Florent
Re: Sound issues on ThinkPad X220T (Lenovo)
riveravaldez wrote: > On 4/12/20, riveravaldez wrote: >> On 4/12/20, Andrei POPESCU wrote: >>> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >>>> >>>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >>>> speaker-test -c2' works flawlessly. (The idea to check that came from >>>> [1].) >>> >>> Some program might be blocking the sound card, check also the output of >>> 'lsof | grep /dev/snd' (as root). >>> >>> Kind regards, >>> Andrei >> >> Thanks a lot for your answer and help, Andrei. >> I've got these: >> >> $ sudo lsof | grep /dev/snd/ >> timidity 644timidity mem CHR >> 116,213463 /dev/snd/pcmC0D0p >> timidity 644timidity3r CHR >>116,33 0t0 12547 /dev/snd/timer >> timidity 644timidity4u CHR >> 116,2 0t0 13463 /dev/snd/pcmC0D0p >> timidity 644timidity5u CHR >> 116,9 0t0 13479 /dev/snd/controlC0 >> timidity 644timidity6u CHR >> 116,1 0t0 12548 /dev/snd/seq >> alsamixer 2150thinkpad3u CHR >> 116,9 0t0 13479 /dev/snd/controlC0 >> >> Maybe a timidity configuration issue? > > Oh, mother-bugger... Problem - practically - solved. > IT is known issue with timidity. I did not know that sound can be played via root account though. We learned a bit more.
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, riveravaldez wrote: > On 4/12/20, Andrei POPESCU wrote: >> On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >>> >>> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >>> speaker-test -c2' works flawlessly. (The idea to check that came from >>> [1].) >> >> Some program might be blocking the sound card, check also the output of >> 'lsof | grep /dev/snd' (as root). >> >> Kind regards, >> Andrei > > Thanks a lot for your answer and help, Andrei. > I've got these: > > $ sudo lsof | grep /dev/snd/ > timidity 644timidity mem CHR > 116,213463 /dev/snd/pcmC0D0p > timidity 644timidity3r CHR >116,33 0t0 12547 /dev/snd/timer > timidity 644timidity4u CHR > 116,2 0t0 13463 /dev/snd/pcmC0D0p > timidity 644timidity5u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > timidity 644 timidity6u CHR > 116,1 0t0 12548 /dev/snd/seq > alsamixer 2150thinkpad3u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > > Maybe a timidity configuration issue? Oh, mother-bugger... Problem - practically - solved. I did: $ sudo apt-get purge timidity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Los siguientes paquetes se ELIMINARÁN: timidity* timidity-daemon* 0 actualizados, 0 nuevos se instalarán, 2 para eliminar y 9 no actualizados. Se liberarán 1.655 kB después de esta operación. ¿Desea continuar? [S/n] (Leyendo la base de datos ... 123466 ficheros o directorios instalados actualmente.) Desinstalando timidity-daemon (2.14.0-8) ... Desinstalando timidity (2.14.0-8) ... Procesando disparadores para mime-support (3.64) ... Procesando disparadores para man-db (2.9.1-1) ... Procesando disparadores para desktop-file-utils (0.24-1) ... (Leyendo la base de datos ... 123413 ficheros o directorios instalados actualmente.) Purgando ficheros de configuración de timidity-daemon (2.14.0-8) ... Purgando ficheros de configuración de timidity (2.14.0-8) ... Procesando disparadores para systemd (244.3-1) ... And everything came to work. Pavucontrol shows the devices, streams and configurations. All media-players (audacious, mplayer, firefox, audacity, etc.) work with default audio configuration, and even JACK is working flawlessly. In fact, tested JACK (qjackctl) with qsynt and vmpk and everything worked fine (maybe I don't even need timidity at all?). And then - testing if could reinstall - found the cause of the problem: $ sudo apt-get install timidity Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Paquetes sugeridos: fluid-soundfont-gs pmidi timidity-daemon Se instalarán los siguientes paquetes NUEVOS: timidity 0 actualizados, 1 nuevos se instalarán, 0 para eliminar y 9 no actualizados. Se necesita descargar 0 B/627 kB de archivos. Se utilizarán 1.582 kB de espacio de disco adicional después de esta operación. Obteniendo informes de fallo... Finalizado Analizando información Encontrada/Corregida... Finalizado Fallos critical del paquete timidity (→ 2.14.0-8) b1 - #901148 - timidity: upgrading to 2.14.0-2 broke sound via pulseaudio Fusionado con: 902330 904652 918522 Resumen: timidity(1 fallo) ¿Está seguro de que desea instalar/actualizar los paquetes mostrados anteriormente? [Y/n/?/...] n * ** Saliendo con error para detener la instalación. ** * E: El subproceso /usr/bin/apt-listbugs apt devolvió un código de error (10) E: Failure running script /usr/bin/apt-listbugs apt Don't know how that passed without me noticing it... Last messages from: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901148#147 > After many tests I have found the solution about the > bugs around timidity-daemon and pulseaudio. > > timidity-daemon installs an system-wide daemon. But > pulseaudio is a user-wide "daemon". I guess that explains the 'sudo works, non-sudo non-works'? > With my appended patch the system-wide daemon will be > removed and a xdg/autostart script will be installed. > > After that timidity together with pulseaudio runs > perfectly. > Now I have made new Debian packages for buster and testing > including my patch: That last's from 20 Feb 2020, maybe still not uploaded? Should I mark this as 'SOLVED' in some manner? Thanks a lot for everything. Andrei, you saved me. ^_^ (!)
Re: Sound issues on ThinkPad X220T (Lenovo)
On Du, 12 apr 20, 11:39:52, riveravaldez wrote: > > $ groups > thinkpad cdrom floppy sudo audio dip video plugdev netdev Ok. > $ speaker-test -c2 [Still not sound.] And no error... > $ sudo speaker-test -c2 [Sounds OK.] That would indicate that sound is handled differently for the regular user (e.g. via pulseaudio) vs. the root user. This could be either pulseaudio or an .asoundrc (do you have one in your home directory?). Try this as user: pasuspender -- speaker-test -c2 > $ sudo lsof | grep /dev/snd/ > timidity 644timidity mem CHR > 116,213463 /dev/snd/pcmC0D0p > timidity 644timidity3r CHR >116,33 0t0 12547 /dev/snd/timer > timidity 644timidity4u CHR > 116,2 0t0 13463 /dev/snd/pcmC0D0p > timidity 644timidity5u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > timidity 644timidity6u CHR > 116,1 0t0 12548 /dev/snd/seq > alsamixer 2150thinkpad3u CHR > 116,9 0t0 13479 /dev/snd/controlC0 > > Maybe a timidity configuration issue? Try stopping / disabling it and see if that helps. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, deloptes wrote: > riveravaldez wrote: > >> But this not, even as sudo (and the error is similar to JACK one): >> $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav >> aplay: main:830: audio open error: Device or resource bussy > > aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav Problem persists, no sound: $ aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav aplay: main:830: audio open error: Device or resource busy > read this > https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture I'll check it again. > > you should know what you are doing Yes, that's the idea. Any help? Thanks!
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/12/20, Andrei POPESCU wrote: > On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: >> >> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >> speaker-test -c2' works flawlessly. (The idea to check that came from >> [1].) > > Any error message? Is your user a member of group 'audio'? > > Some program might be blocking the sound card, check also the output of > 'lsof | grep /dev/snd' (as root). > > Kind regards, > Andrei Thanks a lot for your answer and help, Andrei. I've got these: $ groups thinkpad cdrom floppy sudo audio dip video plugdev netdev $ speaker-test -c2 [Still not sound.] speaker-test 1.2.2 Playback device is default Stream parameters are 48000Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 96 to 1048576 Period size range from 32 to 349526 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Time per period = 12,314270 0 - Front Left 1 - Front Right ^CTime per period = 12,317682 $ sudo speaker-test -c2 [Sounds OK.] speaker-test 1.2.2 Playback device is default Stream parameters are 48000Hz, S16_LE, 2 channels Using 16 octaves of pink noise Rate set to 48000Hz (requested 48000Hz) Buffer size range from 2048 to 16384 Period size range from 1024 to 1024 Using max buffer size 16384 Periods = 4 was set period_size = 1024 was set buffer_size = 16384 0 - Front Left 1 - Front Right Time per period = 5,644667 0 - Front Left ^CWrite error: -4,Llamada al sistema interrumpida xrun_recovery failed: -4,Llamada al sistema interrumpida Transfer failed: Llamada al sistema interrumpida [System is in Spanish, last lines mean, 'Interrupted system-call'.] $ sudo lsof | grep /dev/snd/ timidity 644timidity mem CHR 116,213463 /dev/snd/pcmC0D0p timidity 644timidity3r CHR 116,33 0t0 12547 /dev/snd/timer timidity 644timidity4u CHR 116,2 0t0 13463 /dev/snd/pcmC0D0p timidity 644timidity5u CHR 116,9 0t0 13479 /dev/snd/controlC0 timidity 644timidity6u CHR 116,1 0t0 12548 /dev/snd/seq alsamixer 2150thinkpad3u CHR 116,9 0t0 13479 /dev/snd/controlC0 Maybe a timidity configuration issue?
Re: Sound issues on ThinkPad X220T (Lenovo)
riveravaldez wrote: > But this not, even as sudo (and the error is similar to JACK one): > $ aplay -vv -D front:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav > aplay: main:830: audio open error: Device or resource bussy aplay -vv -D plughw:CARD=PCH,DEV=0 /usr/share/sounds/alsa/Noise.wav read this https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture you should know what you are doing
Re: Sound issues on ThinkPad X220T (Lenovo)
On Sb, 11 apr 20, 21:02:39, riveravaldez wrote: > > Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo > speaker-test -c2' works flawlessly. (The idea to check that came from > [1].) Any error message? Is your user a member of group 'audio'? Some program might be blocking the sound card, check also the output of 'lsof | grep /dev/snd' (as root). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser signature.asc Description: PGP signature
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/11/20, riveravaldez wrote: > On 4/11/20, riveravaldez wrote: >> Hi, >> >> I would like to know what's the proper way to solve this. I'm on an >> updated debian-testing installation (with pulseaudio installed and >> working, but the problem seems to be previous, i.e., in ALSA, because >> pavucontrol doesn't show the soundcard in its correspondent tab). >> >> I can get audio from audacity and audacious as long as I choose >> manually the proper soundcard in its options, but not from other >> programs (e.g., firefox, mplayer, etc.), which I suppose use the >> default soundcard. >> >> Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo >> speaker-test -c2' works flawlessly. (The idea to check that came from >> [1].) >> >> I already tested (following [2]): >> >> $ sudo alsactl init >> Found hardware: "HDA-Intel" "Conexant CX20590" >> "HDA:14f1506e,17aa21db,0013 HDA:80862805,80860101,0010" >> "0x17aa" "0x21db" >> Hardware is initialized using a generic method >> >> But nothing changed after reboot. (Though, the CX20590 is the working >> choice for audacious/audacity.) >> >> I have this info: >> >> $ cat /proc/asound/cards >> 0 [PCH]: HDA-Intel - HDA Intel PCH >> HDA Intel PCH at 0xf252 irq 35 >> >> $ lspci -v >> 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset >> Family High Definition Audio Controller (rev 04) >> Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition >> Audio Controller >> Flags: bus master, fast devsel, latency 0, IRQ 35 >> Memory at f252 (64-bit, non-prefetchable) [size=16K] >> Capabilities: >> Kernel driver in use: snd_hda_intel >> Kernel modules: snd_hda_intel >> >> Any other info I could provide? >> What should I do? >> >> BTW, JACK also fails to work, with these messages: >> >> 20:59:14.349 Reiniciar estadísticas. >> 20:59:14.356 Cambios en las conexiones ALSA. >> Cannot connect to server socket err = No existe el fichero o el >> directorio >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> 20:59:31.365 JACK está iniciándose... >> 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D >> -Chw:PCH,0 -Phw:PCH,0 >> Cannot connect to server socket err = No existe el fichero o el >> directorio >> Cannot connect to server request channel >> jack server is not running or cannot be started >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, >> skipping unlock >> 20:59:31.382 JACK se inició con PID=3144. >> no message buffer overruns >> no message buffer overruns >> no message buffer overruns >> jackdmp 1.9.12 >> Copyright 2001-2005 Paul Davis and others. >> Copyright 2004-2016 Grame. >> Copyright 2016-2017 Filipe Coelho. >> jackdmp comes with ABSOLUTELY NO WARRANTY >> This is free software, and you are welcome to redistribute it >> under certain conditions; see the file COPYING for details >> JACK server starting in realtime mode with priority 10 >> self-connect-mode is "Don't restrict self connect requests" >> Jack: JackPosixThread::StartImp : create non RT thread >> Jack: JackPosixThread::ThreadHandler : start >> Jack: capture device hw:PCH,0 >> Jack: playback device hw:PCH,0 >> Jack: apparent rate = 48000 >> Jack: frames per period = 512 >> Jack: JackDriver::Open capture_driver_name = hw:PCH,0 >> Jack: JackDriver::Open playback_driver_name = hw:PCH,0 >> Jack: Check protocol client = 8 server = 8 >> Jack: JackEngine::ClientInternalOpen: name = system >> Jack: JackEngine::AllocateRefNum ref = 0 >> Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = >> 0 >> Jack: JackEngine::NotifyAddClient: name = system >> Jack: JackGraphManager::SetBufferSize size = 512 >> Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 >> Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 >> Jack: JackDriver::SetupDriverSync driver sem in flush mode >> audio_reservation_init >> Acquire audio card Audio0 >> creating alsa driver ... >> hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit >> ATTENTION: The playback device "hw:PCH,0" is already in use. Please >> stop the application using it and run JACK again >> Jack: JackDriver::Close >> Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 >> Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 >> Jack: JackEngine::ClientInternalClose ref = 0 >> Jack: JackEngine::ClientCloseAux ref = 0 >> Jack: JackGraphManager::RemoveAllPorts ref = 0 >> Released audio card Audio0 >> audio_reservation_finish >> Jack: ~JackDriver >> Cannot initialize driver >> Jack: no message buffer overruns >> Jack: JackPosixThread::Stop >>
Re: Sound issues on ThinkPad X220T (Lenovo)
On 4/11/20, riveravaldez wrote: > Hi, > > I would like to know what's the proper way to solve this. I'm on an > updated debian-testing installation (with pulseaudio installed and > working, but the problem seems to be previous, i.e., in ALSA, because > pavucontrol doesn't show the soundcard in its correspondent tab). > > I can get audio from audacity and audacious as long as I choose > manually the proper soundcard in its options, but not from other > programs (e.g., firefox, mplayer, etc.), which I suppose use the > default soundcard. > > Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo > speaker-test -c2' works flawlessly. (The idea to check that came from > [1].) > > I already tested (following [2]): > > $ sudo alsactl init > Found hardware: "HDA-Intel" "Conexant CX20590" > "HDA:14f1506e,17aa21db,0013 HDA:80862805,80860101,0010" > "0x17aa" "0x21db" > Hardware is initialized using a generic method > > But nothing changed after reboot. (Though, the CX20590 is the working > choice for audacious/audacity.) > > I have this info: > > $ cat /proc/asound/cards > 0 [PCH]: HDA-Intel - HDA Intel PCH > HDA Intel PCH at 0xf252 irq 35 > > $ lspci -v > 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset > Family High Definition Audio Controller (rev 04) > Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition > Audio Controller > Flags: bus master, fast devsel, latency 0, IRQ 35 > Memory at f252 (64-bit, non-prefetchable) [size=16K] > Capabilities: > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > Any other info I could provide? > What should I do? > > BTW, JACK also fails to work, with these messages: > > 20:59:14.349 Reiniciar estadísticas. > 20:59:14.356 Cambios en las conexiones ALSA. > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > 20:59:31.365 JACK está iniciándose... > 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D > -Chw:PCH,0 -Phw:PCH,0 > Cannot connect to server socket err = No existe el fichero o el directorio > Cannot connect to server request channel > jack server is not running or cannot be started > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, > skipping unlock > 20:59:31.382 JACK se inició con PID=3144. > no message buffer overruns > no message buffer overruns > no message buffer overruns > jackdmp 1.9.12 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2016 Grame. > Copyright 2016-2017 Filipe Coelho. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > JACK server starting in realtime mode with priority 10 > self-connect-mode is "Don't restrict self connect requests" > Jack: JackPosixThread::StartImp : create non RT thread > Jack: JackPosixThread::ThreadHandler : start > Jack: capture device hw:PCH,0 > Jack: playback device hw:PCH,0 > Jack: apparent rate = 48000 > Jack: frames per period = 512 > Jack: JackDriver::Open capture_driver_name = hw:PCH,0 > Jack: JackDriver::Open playback_driver_name = hw:PCH,0 > Jack: Check protocol client = 8 server = 8 > Jack: JackEngine::ClientInternalOpen: name = system > Jack: JackEngine::AllocateRefNum ref = 0 > Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0 > Jack: JackEngine::NotifyAddClient: name = system > Jack: JackGraphManager::SetBufferSize size = 512 > Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackDriver::SetupDriverSync driver sem in flush mode > audio_reservation_init > Acquire audio card Audio0 > creating alsa driver ... > hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit > ATTENTION: The playback device "hw:PCH,0" is already in use. Please > stop the application using it and run JACK again > Jack: JackDriver::Close > Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 > Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 > Jack: JackEngine::ClientInternalClose ref = 0 > Jack: JackEngine::ClientCloseAux ref = 0 > Jack: JackGraphManager::RemoveAllPorts ref = 0 > Released audio card Audio0 > audio_reservation_finish > Jack: ~JackDriver > Cannot initialize driver > Jack: no message buffer overruns > Jack: JackPosixThread::Stop > Jack: JackPosixThread::ThreadHandler : exit > JackServer::Open failed with -1 > Jack: Succeeded in unlocking 82280346 byte memory area > Jack:
Sound issues on ThinkPad X220T (Lenovo)
Hi, I would like to know what's the proper way to solve this. I'm on an updated debian-testing installation (with pulseaudio installed and working, but the problem seems to be previous, i.e., in ALSA, because pavucontrol doesn't show the soundcard in its correspondent tab). I can get audio from audacity and audacious as long as I choose manually the proper soundcard in its options, but not from other programs (e.g., firefox, mplayer, etc.), which I suppose use the default soundcard. Strangely, 'speaker-test -c2' doesn't produce a sound. But 'sudo speaker-test -c2' works flawlessly. (The idea to check that came from [1].) I already tested (following [2]): $ sudo alsactl init Found hardware: "HDA-Intel" "Conexant CX20590" "HDA:14f1506e,17aa21db,0013 HDA:80862805,80860101,0010" "0x17aa" "0x21db" Hardware is initialized using a generic method But nothing changed after reboot. (Though, the CX20590 is the working choice for audacious/audacity.) I have this info: $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf252 irq 35 $ lspci -v 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) Subsystem: Lenovo 6 Series/C200 Series Chipset Family High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 35 Memory at f252 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Any other info I could provide? What should I do? BTW, JACK also fails to work, with these messages: 20:59:14.349 Reiniciar estadísticas. 20:59:14.356 Cambios en las conexiones ALSA. Cannot connect to server socket err = No existe el fichero o el directorio Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock 20:59:31.365 JACK está iniciándose... 20:59:31.366 /usr/bin/jackd -v -dalsa -r48000 -p512 -n2 -Xseq -D -Chw:PCH,0 -Phw:PCH,0 Cannot connect to server socket err = No existe el fichero o el directorio Cannot connect to server request channel jack server is not running or cannot be started JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock 20:59:31.382 JACK se inició con PID=3144. no message buffer overruns no message buffer overruns no message buffer overruns jackdmp 1.9.12 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2016 Grame. Copyright 2016-2017 Filipe Coelho. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" Jack: JackPosixThread::StartImp : create non RT thread Jack: JackPosixThread::ThreadHandler : start Jack: capture device hw:PCH,0 Jack: playback device hw:PCH,0 Jack: apparent rate = 48000 Jack: frames per period = 512 Jack: JackDriver::Open capture_driver_name = hw:PCH,0 Jack: JackDriver::Open playback_driver_name = hw:PCH,0 Jack: Check protocol client = 8 server = 8 Jack: JackEngine::ClientInternalOpen: name = system Jack: JackEngine::AllocateRefNum ref = 0 Jack: JackLinuxFutex::Allocate name = jack_sem.1000_default_system val = 0 Jack: JackEngine::NotifyAddClient: name = system Jack: JackGraphManager::SetBufferSize size = 512 Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0 Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Jack: JackDriver::SetupDriverSync driver sem in flush mode audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:PCH,0|hw:PCH,0|512|2|48000|0|0|nomon|swmeter|-|32bit ATTENTION: The playback device "hw:PCH,0" is already in use. Please stop the application using it and run JACK again Jack: JackDriver::Close Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0 Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0 Jack: JackEngine::ClientInternalClose ref = 0 Jack: JackEngine::ClientCloseAux ref = 0 Jack: JackGraphManager::RemoveAllPorts ref = 0 Released audio card Audio0 audio_reservation_finish Jack: ~JackDriver Cannot initialize driver Jack: no message buffer overruns Jack: JackPosixThread::Stop Jack: JackPosixThread::ThreadHandler : exit JackServer::Open failed with -1 Jack: Succeeded in unlocking 82280346 byte memory area Jack: JackShmMem::delete size = 0 index = 0 Jack: ~JackDriver Jack: Succeeded in unlocking 1187 byte memory area Jack: JackShmMem::delete size = 0 index = 1 Jack: Cleaning up shared memory Jack: Cleaning up files Jack: Unregistering server `default' Failed to open server
Re: Understanding the ThinkPad W550s keyboard
On Sun, 1 Dec 2019 23:33:10 -0300 Henrique de Moraes Holschuh wrote: Thanks for the help (and for your work on the thinkpad-acpi driver). > On Sun, 01 Dec 2019, Celejar wrote: > > 1) Most of the function keys don't seem to have scancodes / keycodes > > (evtest doesn't react in any way to their press / release). Is this a > > hardware thing - they just aren't designed as keyboard keys - or a > > failure of the kernel? Some of the ones that have no keycodes do work, > > however (F5-7). Is this happening through the BIOS or something at a > > lower level than the kernel? > > The thinkpad-acpi exports a fully reconfigurable input device. *If* it > gets the keycode from the thinkpad firmware, it can map it to any EV_KEY > event. Refer to its documentation (and to udev's) for details. I tried reading through Documentation/admin-guide/laptops/thinkpad-acpi.rst.gz It's a little over my head, and also apparently somewhat outdated (e.g., the table that describes what the Fn keys do on IBM and Lenovo machines does not at all match what the keys do on the W550s). I gather that for the keys that aren't showing anything at all under evtest, the firmware isn't sending anything to the driver? Or is it doing something via the acpi system that doesn't show up under evtest? I don't really understand the details of acpi and how it interacts with the keyboard. > Maybe someone wrote a GUI thing to remap input device events. If such a > thing exists, you can use it. I'm happy to use the CLI or a configuration file, as long as they're documented clearly in a way that a layman (as opposed to a kernel hacker or udev expert) can understand ;) > > 2) How do the function keys that are supposed to do stuff in Windows > > work? If they don't send scancodes, how do they communicate with the > > operating system, and how can they be used under Linux? > > In windows, a Lenovo driver hooks to ACPI and WMI and does whatever is > needed. Thinkpad-acpi can handle the ACPI events. No idea about WMI > ones. > > > 3) Why doesn't F4 do anything (the microphone continues to work > > regardless of my pressing F4)? > > Because you need to mess with the HDA mixer for that to work, I think. > If there *is* an ACPI fuction to change a gate that the standard audio > subsystem cannot mess with, thinkpad-acpi alone might be able to do > something about it. > > But if you need to mess with the HDA mixer, you need a cross-subsystem > callback layer to let something inside the kernel order ALSA to mute the > mic and not let anything else unmute it. I don't think this exists > [yet]. So, it boils down to: thinkpad-acpi could generate an input > event, and something in userspace would have to handle it and mute the > mic through alsa. > > You could reprogram the thinkpad-acpi input device to issue MIC_MUTE and > see if that gets handled by something in your desktop environment... I get the bottom line, if not quite all the details. That seems to be how F1 (speaker mute) is working here: MUTE is issued, and XFCE ties that to "amixer set Master toggle". Thanks again for the help. Celejar
Re: Understanding the ThinkPad W550s keyboard
On Sun, 01 Dec 2019, Celejar wrote: > 1) Most of the function keys don't seem to have scancodes / keycodes > (evtest doesn't react in any way to their press / release). Is this a > hardware thing - they just aren't designed as keyboard keys - or a > failure of the kernel? Some of the ones that have no keycodes do work, > however (F5-7). Is this happening through the BIOS or something at a > lower level than the kernel? The thinkpad-acpi exports a fully reconfigurable input device. *If* it gets the keycode from the thinkpad firmware, it can map it to any EV_KEY event. Refer to its documentation (and to udev's) for details. Maybe someone wrote a GUI thing to remap input device events. If such a thing exists, you can use it. > 2) How do the function keys that are supposed to do stuff in Windows > work? If they don't send scancodes, how do they communicate with the > operating system, and how can they be used under Linux? In windows, a Lenovo driver hooks to ACPI and WMI and does whatever is needed. Thinkpad-acpi can handle the ACPI events. No idea about WMI ones. > 3) Why doesn't F4 do anything (the microphone continues to work > regardless of my pressing F4)? Because you need to mess with the HDA mixer for that to work, I think. If there *is* an ACPI fuction to change a gate that the standard audio subsystem cannot mess with, thinkpad-acpi alone might be able to do something about it. But if you need to mess with the HDA mixer, you need a cross-subsystem callback layer to let something inside the kernel order ALSA to mute the mic and not let anything else unmute it. I don't think this exists [yet]. So, it boils down to: thinkpad-acpi could generate an input event, and something in userspace would have to handle it and mute the mic through alsa. You could reprogram the thinkpad-acpi input device to issue MIC_MUTE and see if that gets handled by something in your desktop environment... -- Henrique Holschuh
Understanding the ThinkPad W550s keyboard
Hello,
I've always had trouble understanding how all the layers of keyboard
handling code fit together. Here's another attempt at understanding why
some things work on my keyboard and some don't, and - even more
importantly - why.
This is a Lenovo W550s ThinkPad running Debian Sid, with the XFCE
desktop. Here's a chart of what I see with regard to some of the
"special" keys:
Key Keycode (from evtest) Result
--- --
F1 KEY_MUTEmute speaker
F2 KEY_VOLUMEDOWN volume down
F3 KEY_VOLUMEUPvolume up
F4 ("Mutes or unmutes the microphones"
according to User Guide, but doesn't actually do anything on my system)
F5 screen brightness down
F6 screen brightness up
F7 ("Manages external displays" according
to User Guide - not tested)
F8 rfkill soft block (wifi)
F9 (Does stuff in Windows, according to
User Guide - doesn't do anything here)
F10 (Does stuff in Windows, according to
User Guide - doesn't do anything here)
F11 ("Views all the programs that you have
opened", according to the User Guide - doesn't do anything here)
F12 (Does stuff in Windows, according to
User Guide - doesn't do anything here)
Calculator KEY_CALC
LockKEY_LEFTMETA + KEY_L'n' ['l' is mapped to 'n' in the Dvorak
layout in use]
Browser KEY_HOMEPAGE
ComputerKEY_LEFTMETA + KEY_E'.' ['l' is mapped to 'n' in the Dvorak
keymapping in use]
F1-F3 generate keycodes that are congruent to the function they
have according to the User Guide. I think that the actual work is
handled by XFCE - in its settings I see that they are linked to "amixer
set Master toggle", "amixer set Master 2%-", and "amixer set Master 2%
+" respectively. Similarly, the last four special keys just generate
particular scancodes, which I suppose I could easily map to functions
in those XFCE settings (or using other tools).
Questions:
1) Most of the function keys don't seem to have scancodes / keycodes
(evtest doesn't react in any way to their press / release). Is this a
hardware thing - they just aren't designed as keyboard keys - or a
failure of the kernel? Some of the ones that have no keycodes do work,
however (F5-7). Is this happening through the BIOS or something at a
lower level than the kernel?
2) How do the function keys that are supposed to do stuff in Windows
work? If they don't send scancodes, how do they communicate with the
operating system, and how can they be used under Linux?
3) Why doesn't F4 do anything (the microphone continues to work
regardless of my pressing F4)?
Celejar
Re: trying to grab video of screen on a Thinkpad x130e netbook . . .
On 8/24/19, Pétùr wrote: > ffmpeg -f x11grab -s 1280x720 -r 25 -i :0.0 screencast.mp4 but where did the audio go? it worked but not always. base on its logs ffmpeg seems to be making a video, but vlc doesn't show to me the actual video even though the file is there. Why is it that the video is recorded and displayed in some cases onle? lbrtchx
Re: trying to grab video of screen on a Thinkpad x130e netbook . . .
On 8/24/19 3:53 PM, Pétùr wrote: > On 24/08/19 13:29, Albretch Mueller wrote: >> How can I make a video from what is displayed on the screen using >> ffmpeg, aconv or whatever? > > ffmpeg -f x11grab -s 1280x720 -r 25 -i :0.0 screencast.mp4 > > Or you can use Simple Screen Recorder https://tracker.debian.org/pkg/simplescreenrecorder
Re: trying to grab video of screen on a Thinkpad x130e netbook . . .
On 24/08/19 13:29, Albretch Mueller wrote: How can I make a video from what is displayed on the screen using ffmpeg, aconv or whatever? ffmpeg -f x11grab -s 1280x720 -r 25 -i :0.0 screencast.mp4
trying to grab video of screen on a Thinkpad x130e netbook . . .
Hi *: I have to ask after trying to do it in many ways, checking all kinds of posts, searching and following guidelines. https://trac.ffmpeg.org/wiki/Capture/Desktop https://wiki.ubuntuusers.de/Videograbbing/ I am running: $ uname -a Linux niggahme 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) x86_64 GNU/Linux on an "old" X130e Thinkpad which has 4 Gb of RAM. Nothing is listed under: # ls -l /dev/video* ls: cannot access '/dev/video*': No such file or directory # As I remember, some time ago I had to do some kernel tinkering in order to make the screen work fine on Linux: # lshw -class cpu *-cpu description: CPU product: AMD E-450 APU with Radeon(tm) HD Graphics vendor: Advanced Micro Devices [AMD] physical id: 2e bus info: cpu@0 version: AMD E-450 APU with Radeon(tm) HD Graphics slot: Socket FT1 size: 1650MHz capacity: 1650MHz width: 64 bits clock: 100MHz capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni monitor ssse3 cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch ibs skinit wdt hw_pstate vmmcall arat npt lbrv svm_lock nrip_save pausefilter cpufreq configuration: cores=2 enabledcores=2 threads=2 # # lshw -class display *-display description: VGA compatible controller product: Wrestler [Radeon HD 6320] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 1 bus info: pci@:00:01.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:25 memory:e000-efff ioport:3000(size=256) memory:f030-f033 memory:c-d # this are the sound cards on the X130e: # lshw -class sound *-multimedia:0 description: Audio device product: Wrestler HDMI Audio vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 1.1 bus info: pci@:00:01.1 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:24 memory:f0344000-f0347fff *-multimedia:1 description: Audio device product: SBx00 Azalia (Intel HDA) vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 14.2 bus info: pci@:00:14.2 version: 40 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: driver=snd_hda_intel latency=64 resources: irq:16 memory:f034-f0343fff # $ cat /proc/asound/cards 0 [Generic]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xf0344000 irq 24 1 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xf034 irq 16 this is what ffmpeg supports on my installation: $ ffmpeg -devices ffmpeg version 3.2.14-1~deb9u1 Copyright (c) 2000-2019 the FFmpeg developers built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516 configuration: --prefix=/usr --extra-version='1~deb9u1' --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --enable-gpl --disable-stripping --enable-avresample --enable-avisynth --enable-gnutls --enable-ladspa --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libebur128 --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libgme --enable-libgsm --enable-libmp3lame --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libssh --enable-libtheora --enable-libtwolame --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx265 --enable-libxvid --enable-libzmq --enable-libzvbi --enable-omx --enable-openal --enable-opengl --enable-sdl2 --enable-libdc1394 --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libopencv --enable-libx264 --enable-shared libavutil 55. 34.101 / 55. 34.101 libavcodec 57. 64.101 / 57. 64.101 libavformat57. 56.101 / 57. 56.101 libavdevice57. 1.100 / 57. 1.100 libavfilter 6. 65.100 / 6. 65.100 libavresample 3. 1. 0 / 3. 1. 0 libswscale 4. 2.100 / 4. 2.100 libswresample 2. 3.100 / 2. 3.100 libpostproc54. 1.100 / 54. 1.100 Devices: D. = Demuxing supported .E = Muxing supported -- DE alsaALSA audio output E cacacaca (color ASCII art) output device D dv1394 DV1394 A/V grab DE fbdev
