Bug#890326: linux: Thinkpad X61 brightness reset to 0% on each boot
FWIW, I am also seeing this bug after a recent kernel upgrade. The laptop is Asus UX303UA. I enclose the kernel information from reportbug in the attachment. Also I can confirm that the workaround given above works for me. -- David Banks <amoe...@gmail.com> reportbug-kernel-info.out Description: Binary data
Bug#664068: USB MIDI keyboard fails to initialize
Olivier Matz's solution is working for me. I did not realize that this was an interaction with laptop-mode, but indeed the keyboard only fails when the AC adapter is not plugged in and the laptop is running on battery. It works every time when the laptop is plugged into the AC adapter. I can confirm that the following line in /etc/laptop-mode/conf.d/usb-autosuspend.conf makes the keyboard reliably work in all circumstances: AUTOSUSPEND_USBID_BLACKLIST=0763:2027 Thanks Olivier! Cheers, -- David Banks amoe...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caobnz7zjsacbdeyxue+gvs_gjbxovqsn9wv1ranz_n+fabd...@mail.gmail.com
Bug#664068: linux-image-3.2.0-2-amd64: USB MIDI keyboard fails to initialize
Package: linux-2.6 Version: 3.2.10-1 Severity: normal My USB MIDI keyboard, which is an M-Audio Oxygen48, fails to operate about 90% of the time when plugged into my laptop, which is an Asus U35JC. When plugged in, the device will be recognized by ALSA, but no events will be received. amoe@vuurvlieg $ amidi -l Dir DeviceName IO hw:1,0,0 Oxygen 49 MIDI 1 amoe@vuurvlieg $ amidi -p hw:1,0,0 -d ... play some notes ... ^C 0 bytes read The messages from /var/log/kern.log are as follows: When plugged in: [ 430.698566] ehci_hcd :00:1d.0: BAR 0: set to [mem 0xd7407000-0xd74073ff] (PCI address [0xd7407000-0xd74073ff]) [ 430.698596] ehci_hcd :00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x104) [ 430.698629] ehci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x290, writing 0x292) [ 430.698789] ehci_hcd :00:1d.0: PME# disabled [ 430.698809] ehci_hcd :00:1d.0: PCI INT A - GSI 23 (level, low) - IRQ 23 [ 430.698821] ehci_hcd :00:1d.0: setting latency timer to 64 [ 430.714540] ehci_hcd :00:1a.0: BAR 0: set to [mem 0xd7408000-0xd74083ff] (PCI address [0xd7408000-0xd74083ff]) [ 430.714569] ehci_hcd :00:1a.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 430.714602] ehci_hcd :00:1a.0: restoring config space at offset 0x1 (was 0x290, writing 0x292) [ 430.714752] ehci_hcd :00:1a.0: PME# disabled [ 430.714769] ehci_hcd :00:1a.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 430.714781] ehci_hcd :00:1a.0: setting latency timer to 64 [ 430.918758] usb 2-1.2: new full-speed USB device number 6 using ehci_hcd [ 431.181225] usb 2-1.2: New USB device found, idVendor=0763, idProduct=2027 [ 431.181233] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 431.181239] usb 2-1.2: Product: Oxygen 49 [ 431.181243] usb 2-1.2: Manufacturer: M-Audio [ 433.740928] urb status -32 ... repeat many times ... [ 433.756467] urb status -32 [ 437.770374] ehci_hcd :00:1a.0: PCI INT A disabled [ 437.770434] ehci_hcd :00:1a.0: PME# enabled [ 437.786339] ehci_hcd :00:1d.0: PCI INT A disabled [ 437.786396] ehci_hcd :00:1d.0: PME# enabled When I unplug it, the following: [ 446.940947] ehci_hcd :00:1d.0: BAR 0: set to [mem 0xd7407000-0xd74073ff] (PCI address [0xd7407000-0xd74073ff]) [ 446.940977] ehci_hcd :00:1d.0: restoring config space at offset 0xf (was 0x100, writing 0x104) [ 446.941011] ehci_hcd :00:1d.0: restoring config space at offset 0x1 (was 0x290, writing 0x292) [ 446.941168] ehci_hcd :00:1d.0: PME# disabled [ 446.941188] ehci_hcd :00:1d.0: PCI INT A - GSI 23 (level, low) - IRQ 23 [ 446.941200] ehci_hcd :00:1d.0: setting latency timer to 64 [ 446.956861] ehci_hcd :00:1a.0: BAR 0: set to [mem 0xd7408000-0xd74083ff] (PCI address [0xd7408000-0xd74083ff]) [ 446.956890] ehci_hcd :00:1a.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [ 446.956923] ehci_hcd :00:1a.0: restoring config space at offset 0x1 (was 0x290, writing 0x292) [ 446.957070] ehci_hcd :00:1a.0: PME# disabled [ 446.957087] ehci_hcd :00:1a.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 446.957099] ehci_hcd :00:1a.0: setting latency timer to 64 [ 447.089300] usb 2-1.2: USB disconnect, device number 6 [ 449.707234] ehci_hcd :00:1a.0: PCI INT A disabled [ 449.707292] ehci_hcd :00:1a.0: PME# enabled [ 451.722036] ehci_hcd :00:1d.0: PCI INT A disabled [ 451.722097] ehci_hcd :00:1d.0: PME# enabled Note: This does not always happen. I know the keyboard is good because I also have a Squeeze machine where the device is operating fine. The equivalent log from that machine is as follows: [ 95.384057] usb 3-1: new full speed USB device using uhci_hcd and address 2 [ 95.674118] usb 3-1: New USB device found, idVendor=0763, idProduct=2027 [ 95.674126] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 95.674133] usb 3-1: Product: Oxygen 49 [ 95.674139] usb 3-1: Manufacturer: M-Audio [ 95.675129] usb 3-1: configuration #1 chosen from 1 choice ... I disconnect the keyboard ... [ 123.904080] usb 3-1: USB disconnect, address 2 I have successfully used the keyboard with this kernel before, but I can only get it to work under mysterious circumstances. Sometimes it will work after a fresh reboot (still, most of the time it won't). However, generally once this error has happened it won't work again in that power cycle. This may not be a definite pattern though. Cheers, David -- Package-specific info: ** Version: Linux version 3.2.0-2-amd64 (Debian 3.2.10-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Tue Mar 13 16:54:04 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64
Bug#658778: pm-suspend does not enter suspend and hangs system on Asus U35JC
lPlease find attached the reportbug output for the kernel. Information from the BIOS: BIOS vendor: American Megatrends Version: U35JC 207 VBIOS version: 1930.I11U35JC.002 EC version: 202c21 Cheers, -- David Banks amoe...@gmail.com kernel-reportbug.out Description: Binary data
Bug#606762: linux-2.6: intermittent wifi dropouts with iwlagn driver
Since first reporting this bug I have now found a workaround, though it's not nice. Disabling Wireless-N mode on the router and switching back to B/G mixed mode made the problem go away. I am using DD-WRT firmware on the router, which is a D-Link DIR-615. I noticed the problem went away when I was outside my house in a G-only network. Coincidentally one of my friends has the exact same model of router (it's given away free by the largest ISP here in the UK), but he uses the stock firmware, also in Wireless-N mode. When I used my laptop at his house the problem manifested again. However, I have not tested with any other model of Wireless-N capable router. So the problem is either all Wireless-N support in this driver, or a problem with the Wireless-N support in the hardware of this router model. -- David Banks amoe...@gmail.com -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTintrtie+F5wfVvn9kkYSEdGTWutSe+x=xpav...@mail.gmail.com
Bug#606762: linux-2.6: intermittent wifi dropouts with iwlagn driver
Package: linux-2.6 Version: 2.6.32-5-amd64 Severity: normal Hi all, My laptop is an Asus UL30A. It has an Intel Wireless-N 1000 BGN chip for wifi. The PCI ID is 8086:0083. I use the iwlagn driver along with the 'firmware-iwlwifi' package (non-free, sadly) in order to connect. My wifi network is Wireless-N and I do not use encryption. I intermittently experience network dropouts. This happens once every few days, with no obvious pattern. The network drops and all connections, local and WAN, give errors. Either the driver itself or NetworkManager will try to reconnect after around five minutes. I will then get a connection for a few minutes max before it drops again. This cycle goes on for a seemingly random amount of time. Sometimes it spontaneously fixes itself after half an hour. Sometimes I will have to reboot to fix it. It will generally work after a reboot, but not always! There seems to be no pattern to how long it lasts or what fixes it. I have noticed that I can nearly always trigger it by using something that generates a large amount of connections, for instance if I download a popular file through bittorrent without limiting the bandwidth use it will nearly always cause a dropout, which will then go through the disconnect/reconnect cycle described earlier for, again, a seemingly random amount of time. Error message in /var/log/messages: Dec 11 14:18:13 glimworm kernel: [10489.200053] iwlagn :02:00.0: iwl_tx_agg_start on ra = 1c:af:f7:99:72:0e tid = 0 Dec 11 14:19:32 glimworm kernel: [10567.517719] iwlagn :02:00.0: iwl_tx_agg_start on ra = 1c:af:f7:99:72:0e tid = 0 Dec 11 14:25:01 glimworm kernel: [10896.870454] iwlagn :02:00.0: iwl_tx_agg_start on ra = 1c:af:f7:99:72:0e tid = 0 Dec 11 14:27:23 glimworm kernel: [11038.818791] iwlagn :02:00.0: iwl_tx_agg_start on ra = 1c:af:f7:99:72:0e tid = 0 It seems that every time the network drops, one of these messages is logged to /var/log/messages. Meanwhile dmesg is cycling these messages: [11038.818791] iwlagn :02:00.0: iwl_tx_agg_start on ra = 1c:af:f7:99:72:0e tid = 0 [11132.37] wlan0: deauthenticated from 1c:af:f7:99:72:0e (Reason: 3) [11132.942116] wlan0: direct probe to AP 1c:af:f7:99:72:0e (try 1) [11132.945610] wlan0: direct probe responded [11132.945620] wlan0: authenticate with AP 1c:af:f7:99:72:0e (try 1) [11132.955145] wlan0: authenticated [11132.955187] wlan0: associate with AP 1c:af:f7:99:72:0e (try 1) [11132.961970] wlan0: RX AssocResp from 1c:af:f7:99:72:0e (capab=0x421 status=0 aid=1) [11132.961978] wlan0: associated [11137.929127] iwlagn :02:00.0: iwl_tx_agg_start on ra = 1c:af:f7:99:72:0e tid = 0 Anyone have any ideas? Cheers, David -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101211150222.2586.14539.report...@glimworm.solasistim.net
