3.2.30-1 FTBFS on mipsen
Apparently because NFS is statically linked (and we only ignore those ABI changes in the modules). Curious - is there a reason for statically linking NFS on mips? Perhaps sb1-bcm91250a and sb1a-bcm91480b need ROOT_NFS more than other architectures, but I that doesn't explain mipsel. -- 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/20120928072944.ga5...@dannf.org
Bug#685360: [PATCH 1/1] HID: Fix missing Unifying device issue
Hello Josip, This really looks like a different problem from the one addressed with this patch. I'll try to work on it as soon as I find some time for that. Thanks, Nestor. On Thu, Sep 27, 2012 at 8:56 PM, Josip Rodin j...@debbugs.entuzijast.netwrote: On Thu, Sep 27, 2012 at 09:04:26AM +0200, Josip Rodin wrote: On Mon, Sep 24, 2012 at 11:30:28AM +0200, Nestor Lopez Casado wrote: Josip, this is a different issue from the one addressed with the patch. 1) Can you try it on a 3.2 kernel ? I can try that too, I'll let you know how it went. Same thing, it doesn't work. -- 2. That which causes joy or happiness. -- To unsubscribe from this list: send the line unsubscribe linux-input in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Processed: retitle 683695 to nouveau needs patches backported from 3.4 to support GTX 550 Ti cards
Processing commands for cont...@bugs.debian.org: retitle 683695 nouveau needs patches backported from 3.4 to support GTX 550 Ti cards Bug #683695 [src:linux] nouveau needs patches backported from 3.4 to Changed Bug title to 'nouveau needs patches backported from 3.4 to support GTX 550 Ti cards' from 'nouveau needs patches backported from 3.4 to' thanks Stopping processing here. Please contact me if you need assistance. -- 683695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.134883792228958.transcr...@bugs.debian.org
Bug#641749: package libmtp-runtime breaks AR3011 Bluetooth
I also found that removal of the libmtp-runtime package (version
1.1.2-2) solved the problem with my AR3011 Bluetooth device.
(AMD64 CPU, Linux v3.2)
After reading here:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/714862/comments/43
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/714862/comments/45
http://permalink.gmane.org/gmane.linux.kernel1.73/1262485
-- that there was a firmware patch which supposedly addressed this
problem, I obtained the Ubuntu linux-firmware package which contains
the updated ath3k-1.fw file (as of version 1.73):
http://packages.ubuntu.com/precise/linux-firmware
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-firmware/linux-firmware_1.79/changelog
-- and substituted their file in place of the one from the Debian
firmware-atheros package (version 0.36). I confirmed that the firmware
images are in fact different.
Result: the firmware change appears to have no effect at all. I tried
booting up with all four combinations of
{libmtp-runtime present/not present} x {Debian firmware/Ubuntu firmware}
and the Bluetooth device works or not depending on the presence (no) or
absence (yes) of libmtp-runtime, regardless of the firmware version.
I urge other people to try this experiment.
Later comments in the corresponding Ubuntu bug report:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/714862
-- agree with this result:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/714862/comments/40
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/714862/comments/53
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/714862/comments/55
I apologize for taking so long to reply. I have reinstalled the newer
version of libmtp-runtime (1.1.3-x) and I confirm that now firmware to
the atheros bluetooth is loaded correctly.
I haven't tried any new firmware (in fact, as far asI know the
firmware patch never made into Debian). This is with current stock
wheezy kernel and firmware.
I think this bug can be closed.
--
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/CAH=dYrG=M7fZcLmwvc6nPET8n2=DyBvk9HBA5ypnR5=6gmh...@mail.gmail.com
Bug#660111: multiple, non-physically accesible, HDMI devices (Re: pulseaudio: pa can't handle multiple HDMI devices)
You're correct; even if the information is there, it isn't advertised in pavucontrol. I should probably implement that... (If you're using Ubuntu 12.04, you will have a new sound settings UI that hides unavailable devices. For upstreaming of this UI please see the gnome-cc list.) What you'll get is instead what the module-switch-on-port-available module provides. When you plug your headphones in, the selected port will switch (you should be able to notice this in pavucontrol I think), which means your media keys / sound indicator / etc would control your headphone's volume instead of your speaker's volume. For the multi HDMI case - if you have selected the wrong HDMI interface, and then activate your HDMI screen, module-switch-on-port-available should automatically switch to the correct one. This is all assuming you're running PulseAudio 2.0 - earlier versions of PulseAudio do not have this functionality. Should you be interested in backporting the jack detection kernel patches, I'll be happy to point you to the Ubuntu kernel's git tree, where I did the same thing. Has this been backported? Personally I think this bug should closed whether it's been backported or not. The gain in backporting jack detection is minimal because the GUI's haven't completely caught up with this feature yet as David mentioned and the user still needs to pick from one of the multiple HDMI ports advertised by the kernel. -- 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/CAH=dYrH7eMViw95-yxJA7n=6jme2bt4ltaogpcxaghle6na...@mail.gmail.com
Bug#641749: package libmtp-runtime breaks AR3011 Bluetooth
On 09/28/2012 09:25 AM, Andres Cimmarusti wrote: I apologize for taking so long to reply. I have reinstalled the newer version of libmtp-runtime (1.1.3-x) and I confirm that now firmware to the atheros bluetooth is loaded correctly. I haven't tried any new firmware (in fact, as far asI know the firmware patch never made into Debian). This is with current stock wheezy kernel and firmware. It made it's way to the upstream linux-firmware git repo, so Debian can pull it from there. The summary is that Atheros chips are designed to picid during the initialization process. We had one very specific chip that was not changing ID's. The firmware update caused this chip to change ID's with only minimal changes to the driver. I think this bug can be closed. -- 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/5065b901.7060...@canonical.com
Bug#641749: package libmtp-runtime breaks AR3011 Bluetooth
Hi James, James M Leddy wrote: On 09/28/2012 09:25 AM, Andres Cimmarusti wrote: I haven't tried any new firmware (in fact, as far asI know the firmware patch never made into Debian). This is with current stock wheezy kernel and firmware. It made it's way to the upstream linux-firmware git repo, so Debian can pull it from there. Are you sure? Looking at [1], the most recent change I see is in 2010-12-13. Curious, Jonathan [1] http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git;a=history;f=ath3k-1.fw -- 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/20120928154220.GA169@mannheim-rule.local
Bug#641749: package libmtp-runtime breaks AR3011 Bluetooth
On 09/28/2012 11:42 AM, Jonathan Nieder wrote: It made it's way to the upstream linux-firmware git repo, so Debian can pull it from there. Are you sure? Looking at [1], the most recent change I see is in 2010-12-13. Now I'm not so sure. I'll look in to this today and get back to you. -- 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/5065ccdb.4000...@canonical.com
Bug#641749: package libmtp-runtime breaks AR3011 Bluetooth
On 09/28/2012 11:42 AM, Jonathan Nieder wrote: Hi James, James M Leddy wrote: On 09/28/2012 09:25 AM, Andres Cimmarusti wrote: I haven't tried any new firmware (in fact, as far asI know the firmware patch never made into Debian). This is with current stock wheezy kernel and firmware. It made it's way to the upstream linux-firmware git repo, so Debian can pull it from there. Are you sure? Looking at [1], the most recent change I see is in 2010-12-13. Okay, it has been submitted [2], but it didn't make it into git yet. I'll ping David again about this. [1] http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git;a=history;f=ath3k-1.fw [2] https://lkml.org/lkml/2012/3/20/216 -- 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/5065d010.5060...@canonical.com
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 683695 important Bug #683695 [src:linux] nouveau needs patches backported from 3.4 to support GTX 550 Ti cards Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 683695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13488515372776.transcr...@bugs.debian.org
Bug#689096: linux-image-3.2.0-3-686-pae: ipw2200 crashes on wakeup
Package: src:linux Version: 3.2.23-1 Severity: normal Dear Maintainer, Ever since I upgraded to wheezy I get occasional crashes in the ipw2200 driver when my laptop wakes up from suspend. It does't always happen and it used to work flawlessly with squeeze. Here's what dmesg has to say about this: [59928.488934] wlan: Coming out of suspend... [59928.488943] ipw2200 :04:02.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [59928.490888] [ cut here ] [59928.490899] WARNING: at /build/buildd-linux_3.2.23-1-i386-qhsd1M/linux-3.2.23/drivers/base/firmware_class.c:537 _request_firmware+0xad/0x2f9() [59928.490922] Hardware name: 25256NG [59928.490925] Modules linked in: ipw2200 msr tg3 libphy cryptd aes_i586 aes_generic lib80211_crypt_ccmp cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave fuse ext3 jbd mbcache hidp hid rfcomm bluetooth crc16 dm_crypt dm_mod snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss thinkpad_acpi snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer pcmcia libipw snd_seq_device iTCO_wdt cfg80211 rfkill iTCO_vendor_support snd lib80211 nvram soundcore yenta_socket pcmcia_rsrc pcmcia_core psmouse rng_core snd_page_alloc serio_raw i2c_i801 pcspkr battery acpi_cpufreq ac power_supply mperf evdev processor xfs sg sd_mod crc_t10dif ata_generic ata_piix ahci libahci libata i915 scsi_mod sdhci_pci sdhci mmc_core i2c_algo_bit drm_kms_helper drm uhci_hcd ehci_hcd usbcore thermal video i2c_core thermal_sys usb_common button [last unloaded: ipw2200] [59928.491047] Pid: 19479, comm: kworker/0:0 Tainted: GW 3.2.0-3-686-pae #1 [59928.491050] Call Trace: [59928.491059] [c1037fcc] ? warn_slowpath_common+0x68/0x79 [59928.491063] [c11f9356] ? _request_firmware+0xad/0x2f9 [59928.491068] [c1037fea] ? warn_slowpath_null+0xd/0x10 [59928.491073] [c11f9356] ? _request_firmware+0xad/0x2f9 [59928.491077] [c11f95ab] ? request_firmware+0x9/0xc [59928.491088] [f89b3f78] ? ipw_up+0xdd/0x1165 [ipw2200] [59928.491094] [c102cccb] ? finish_task_switch+0x6d/0x94 [59928.491109] [f856b928] ? scsi_request_fn+0x303/0x3c3 [scsi_mod] [59928.491116] [c12bf943] ? _raw_spin_lock_irqsave+0x8/0x21 [59928.491121] [c1029ee0] ? should_resched+0x5/0x1e [59928.491128] [f89b51e8] ? ipw_bg_up+0x1c/0x25 [ipw2200] [59928.491134] [c104965c] ? process_one_work+0x112/0x1fa [59928.491141] [f89b51cc] ? ipw_net_init+0x32/0x32 [ipw2200] [59928.491146] [c104a367] ? worker_thread+0xa9/0x122 [59928.491150] [c104a2be] ? manage_workers.isra.23+0x13d/0x13d [59928.491155] [c104cca7] ? kthread+0x63/0x68 [59928.491160] [c104cc44] ? kthread_worker_fn+0x101/0x101 [59928.491167] [c12c473e] ? kernel_thread_helper+0x6/0x10 [59928.491170] ---[ end trace 489947a6c8cb68b7 ]--- [59928.491174] ipw2200 :04:02.0: firmware: ipw2200-bss.fw will not be loaded [59928.491178] ipw2200: ipw2200-bss.fw request_firmware failed: Reason -16 [59928.491182] ipw2200: Unable to load firmware: -16 -- Package-specific info: ** Version: Linux version 3.2.0-3-686-pae (Debian 3.2.23-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 03:50:34 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-3-686-pae root=UUID=88262002-52a8-49fa-ab66-637759ec0159 ro acpi_sleep=s3_bios splash quiet ** Tainted: W (512) * Taint on warning. ** Kernel log: [124138.880450] snd_intel8x0 :00:1e.2: restoring config space at offset 0x1 (was 0x297, writing 0x293) [124138.880608] tg3 :02:00.0: restoring config space at offset 0xc (was 0x0, writing 0xac00) [124138.880638] tg3 :02:00.0: restoring config space at offset 0x1 (was 0x100102, writing 0x100106) [124138.896067] sdhci-pci :04:00.1: BAR 0: set to [mem 0xa0201000-0xa02010ff] (PCI address [0xa0201000-0xa02010ff]) [124138.896105] sdhci-pci :04:00.1: restoring config space at offset 0x3 (was 0x80, writing 0x804000) [124138.896115] sdhci-pci :04:00.1: restoring config space at offset 0x1 (was 0x210, writing 0x2100106) [124138.896376] PM: early resume of devices complete after 56.287 msecs [124138.896531] i915 :00:02.0: power state changed by ACPI to D0 [124138.896536] i915 :00:02.0: power state changed by ACPI to D0 [124138.896545] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [124138.896550] i915 :00:02.0: setting latency timer to 64 [124138.952450] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [124138.952454] uhci_hcd :00:1d.0: power state changed by ACPI to D0 [124138.952461] uhci_hcd :00:1d.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [124138.952469] uhci_hcd :00:1d.0: setting latency timer to 64 [124138.952496] usb usb2: root hub lost power or was reset [124138.952509] uhci_hcd :00:1d.1: power state changed by ACPI to D0 [124138.952513] uhci_hcd :00:1d.1: power state changed by ACPI to D0 [124138.952519] uhci_hcd :00:1d.1: PCI INT B - GSI 17 (level, low) - IRQ 17 [124138.952527]
