Bug#399324: linux-image-2.6.17-2-686: OSS layer for ALSA mixer module bugs PCM volume setting
Le Thu, 25 Dec 2008 17:02:49 +0100, Moritz Muehlenhoff a écrit: On Tue, Jun 03, 2008 at 11:38:02AM +0200, maximilian attems wrote: as this seems an longstanding bug, please report upstream on bugzilla.kernel.org include the output of this alsa script http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh thanks for letting us know the upstream bug number. Fabien, did you report this to the Linux kernel developers? Cheers, Moritz No, and I won't. I initially reported the bug during Etch prerelease, in the hope it would improve Etch release. This bug is now more than 2 years old, and I lost any hope in Debian bug handling process. FYI it's not just this one, I have faithfully reported a few dozens bugs and apart from a few exceptions they all followed about the same story. Lenny is about to come out stable and still has the bug, and I'm convinced that whatever efforts I did or will do won't make any fix into stable Lenny. So I give up, sorry. -- Cordialement, Fabien COUTANT. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#399324: linux-image-2.6.17-2-686: OSS layer for ALSA mixer module bugs PCM volume setting
Le Thu, 25 Dec 2008 17:02:49 +0100, Moritz Muehlenhoff a écrit: On Tue, Jun 03, 2008 at 11:38:02AM +0200, maximilian attems wrote: as this seems an longstanding bug, please report upstream on bugzilla.kernel.org include the output of this alsa script http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh thanks for letting us know the upstream bug number. Fabien, did you report this to the Linux kernel developers? Cheers, Moritz No, and I won't. I initially reported the bug during Etch prerelease, in the hope it would improve Etch release. This bug is now more than 2 years old, and I lost any hope in Debian bug handling process. FYI it's not just this one, I have faithfully reported a few dozens bugs and apart from a few exceptions they all followed about the same story. Lenny is about to come out stable and still has the bug, and I'm convinced that whatever efforts I did or will do won't make any fix into stable Lenny. So I give up, sorry. -- Cordialement, Fabien COUTANT. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#398449: closed by Bastian Blank [EMAIL PROTECTED] (uses new-style rtc and hpet emulation now)
Le Sat, 13 Sep 2008 20:18:07 +, Debian Bug Tracking System a écrit: It has been closed by Bastian Blank [EMAIL PROTECTED]. [...cut...] Version: 2.6.26-1 Since 2.6.26 we only have new-style RTC and the HPET irq emulation enabled. This should have fixed this. Dunno... 2.6.26 isn't in Etch, so this doesn't fix Etch :/ Meanwhile, 2.6.18 was out in Etch, and then 2.6.24 in Etch'n half. I'm currently running the latter. After spending more time investigating, I concluded the standard rtc driver is at least partly broken in those kernels (and probably 2.6.26 too) on many motherboards (Asrock 775i65g here at home, Dell Optiplex 320DT at work). Is it the one based on HPET ? Because, a working solution better than --direct-isa is to replace it _at_boot_ with genrtc (listing it in /etc/modules + blacklist rtc in /etc/modprobe.d/somefile + reboot). So the genrtc works perfect (with hwclock, chrony etc), but what is it based on ? -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399324: linux-image-2.6.17-2-686: OSS layer for ALSA mixer module bugs PCM volume setting
On Monday, 20 November 2006, you (dann frazier) wrote: Please see if you can reproduce with the 2.6.18 kernel in sid. Etch will ship with 2.6.18, 2.6.17 packages are no longer maintained. I could reproduce: $ dpkg -l linux-image* | grep ^.i ii linux-image-2.6-686 2.6.17+2 Linux kernel 2.6 image on PPro/Celeron/PII/P ii linux-image-2.6.17-2-686 2.6.17-9 Linux 2.6.17 image on PPro/Celeron/PII/PIII/ ii linux-image-2.6.18-2-686 2.6.18-5 Linux 2.6.18 image on PPro/Celeron/PII/PIII/ $ uname -a Linux harris 2.6.18-2-686 #1 SMP Wed Nov 8 19:52:12 UTC 2006 i686 GNU/Linux But bug is still here, symptoms are identical to the report on 2.6.17. -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399324: linux-image-2.6.17-2-686: OSS layer for ALSA mixer module bugs PCM volume setting
Package: linux-image-2.6.17-2-686 Version: 2.6.17-9 Severity: normal Master volume setting isn't working at all, be it through OSS or ALSA. PCM volume setting works only when set directly to ALSA (using alsamixer or gamix), and only if there's no sound daemon (I tried esd and pulseaudio) running. NB: actually I don't need a sound daemon to multiplex sound output, this was just a try. As soon as I open an OSS mixer (such as aumix), PCM volume set in alsamixer becomes a no-op. In the OSS mixer, the PCM setting behaves as if it was stuck at 100%. After I quit the OSS mixer, PCM control is back to alsamixer. I need OSS mixer working to use GTK aumix, because it's the only heavy-desktop-free mixer software with horizontal volume bars. Unfortunately it's OSS only... This may be specific to my hardware, so here's some info about it: $ lspci -vv ... 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) Subsystem: ASRock Incorporation Unknown device 9761 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 209 Region 0: I/O ports at d800 [size=256] Region 1: I/O ports at dc00 [size=64] Region 2: Memory at ff27f800 (32-bit, non-prefetchable) [size=512] Region 3: Memory at ff27f400 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- ... $ cat /proc/asound/cards 0 [ICH5 ]: ICH4 - Intel ICH5 Intel ICH5 with CMI9761 at 0xff27f800, irq 209 $ cat /proc/asound/devices 0: [ 0] : control 16: [ 0- 0]: digital audio playback 20: [ 0- 4]: digital audio playback 24: [ 0- 0]: digital audio capture 25: [ 0- 1]: digital audio capture 26: [ 0- 2]: digital audio capture 27: [ 0- 3]: digital audio capture 33:: timer $ cat /proc/asound/pcm 00-04: Intel ICH - IEC958 : Intel ICH5 - IEC958 : playback 1 00-03: Intel ICH - ADC2 : Intel ICH5 - ADC2 : capture 1 00-02: Intel ICH - MIC2 ADC : Intel ICH5 - MIC2 ADC : capture 1 00-01: Intel ICH - MIC ADC : Intel ICH5 - MIC ADC : capture 1 00-00: Intel ICH : Intel ICH5 : playback 1 : capture 1 -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.17-2-686 depends on: ii initramfs-tools [linux-initra 0.85a tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-2-686 recommends: ii libc6-i686 2.3.6.ds1-7 GNU C Library: Shared libraries [i -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686: -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390302: linux-image-2.6.17-2-686: master and pcm volume not working with CMI9761 (AC97)
On Wednesday, 04 October 2006, you (dann frazier) wrote: [...cut...] Can you test with 2.6.18 from sid? This is the kernel planned for etch. Fortunately the .deb worked on sarge (with a small quirk on /boot/config*), so I could test it. To be precise I used linux-image-2.6.18-1-686_2.6.18-2_i386.deb . Yet it has the same symptoms, the bug is still here :-/ -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390302: linux-image-2.6.17-2-686: master and pcm volume not working with CMI9761 (AC97)
Package: linux-image-2.6.17-2-686 Version: 2.6.17-9~bpo.1 Severity: important I bought a Asrock 775i65G R2.0 board and it has a CMI9761A audio chip (I checked in Windows). lspci -vvv excerpt: :00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) Subsystem: ASRock Incorporation: Unknown device 9761 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 193 Region 0: I/O ports at d800 [size=256] Region 1: I/O ports at dc00 [size=64] Region 2: Memory at ff27f800 (32-bit, non-prefetchable) [size=512] Region 3: Memory at ff27f400 (32-bit, non-prefetchable) [size=256] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- With this kernel, neither master nor pcm volumes are working (either through an OSS mixer (aumix) or alsamixer). Actually PCM volume is blocked at maximum. Master seems to have absolutely no effect (volume, muting and unmuting). However muting pcm works as expected, but is pretty useless in this situation. I also tested a live KUbuntu 6.06 cd, it has a (modified) 2.6.15 kernel, and with it the situation is better: pcm volume is working as expected (but master is still inoperant). So the hardware has a working mixer (at least partially), and the current sound driver seems broken (snd_intel8x0? snd_ac97_codec? snd_ac97_bus?) because it has worked somewhere in the past. In case it's relevant, a Intel Core2Duo E6400 is plugged in the board, so the kernel works in SMP (and effectively shows 2 CPUs). -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.17-2-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.17-2-686 depends on: ii module-init-tools3.2.2-2bpo1 tools for managing Linux kernel mo ii yaird [linux-initramfs-t 0.0.12-8bpo1+fc Yet Another mkInitRD -- debconf information: linux-image-2.6.17-2-686/postinst/old-initrd-link-2.6.17-2-686: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.17-2-686/postinst/old-dir-initrd-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/lilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/failed-to-move-modules-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/depmod-error-initrd-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/create-kimage-link-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/bootloader-test-error-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.17-2-686/prerm/removing-running-kernel-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/abort-overwrite-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/already-running-this-2.6.17-2-686: linux-image-2.6.17-2-686/postinst/old-system-map-link-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/bootloader-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/preinst/initrd-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/abort-install-2.6.17-2-686: linux-image-2.6.17-2-686/preinst/overwriting-modules-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/kimage-is-a-directory: linux-image-2.6.17-2-686/preinst/elilo-initrd-2.6.17-2-686: true linux-image-2.6.17-2-686/prerm/would-invalidate-boot-loader-2.6.17-2-686: true linux-image-2.6.17-2-686/postinst/depmod-error-2.6.17-2-686: false linux-image-2.6.17-2-686/postinst/bootloader-error-2.6.17-2-686: -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346141: linux-image-2.6.15-1-k7-smp: the package doesn't configure
Package: linux-image-2.6.15-1-k7-smp Version: 2.6.15-0bpo1 Severity: grave Justification: renders package unusable I downloaded this package from backports.org, to install it on a Sarge. I first see the following warning message: -- Configuring linux-image-2.6.15-1-k7-smp You are installing a kernel with an initrd image You are attempting to install an initrd kernel image (version 2.6.15-1-k7-smp) on a machine currently running kernel version 2.4.31-k7-smp. I have been unable to find a suitable tool for generating initrd images (I looked at the list mkinitramfs mkinitrd.yaird) This will break the installation, unless such tools are also being installed right now in the same run. (This means, one from the following list yaird (= 0.0.11-8) | initramfs-tools (= 0.35) | linux-initramfs-tool,) Ok -- Then at console: -- Could not find mkinitramfs mkinitrd.yaird. at /var/lib/dpkg/tmp.ci/preinst line 236, STDIN line 9. Done. Unpacking replacement linux-image-2.6.15-1-k7-smp ... Running postrm hook /sbin/update-grub . Searching for GRUB installation directory ... found: /boot/grub . Setting up linux-image-2.6.15-1-k7-smp (2.6.15-0bpo1) ... Running depmod. Finding valid ramdisk creators. Failed to find suitable ramdisk generation tool for kernel version 2.6.15-1-k7-smp on running kernel 2.4.31-k7-smp in mkinitramfs mkinitrd.yaird dpkg: error processing linux-image-2.6.15-1-k7-smp (--install): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.15-1-k7-smp -- It seems to complain that it can't find mkinitrd.yaird, but I installed yaird from the same source and mkinitrd.yaird is located in /usr/sbin. My /etc/kernel-img.conf is original, it doesn't contain any ramdisk= directive. This is supposed to install fine on a sarge, but it doesn't. Is it a packaging bug, or is there anything (undocumented) missing ? -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.31-k7-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.15-1-k7-smp depends on: ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool 0.0.12-2bpo1 Yet Another mkInitRD -- debconf information: linux-image-2.6.15-1-k7-smp/postinst/old-initrd-link-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/preinst/abort-install-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/postinst/depmod-error-initrd-2.6.15-1-k7-smp: false linux-image-2.6.15-1-k7-smp/prerm/would-invalidate-boot-loader-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/preinst/elilo-initrd-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/postinst/bootloader-error-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/preinst/lilo-has-ramdisk: linux-image-2.6.15-1-k7-smp/postinst/kimage-is-a-directory: linux-image-2.6.15-1-k7-smp/preinst/already-running-this-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/postinst/depmod-error-2.6.15-1-k7-smp: false linux-image-2.6.15-1-k7-smp/preinst/abort-overwrite-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/preinst/initrd-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/preinst/failed-to-move-modules-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/preinst/bootloader-initrd-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/preinst/overwriting-modules-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/prerm/removing-running-kernel-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/postinst/old-dir-initrd-link-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/postinst/create-kimage-link-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/postinst/bootloader-test-error-2.6.15-1-k7-smp: linux-image-2.6.15-1-k7-smp/postinst/old-system-map-link-2.6.15-1-k7-smp: true linux-image-2.6.15-1-k7-smp/preinst/lilo-initrd-2.6.15-1-k7-smp: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#311145: new info
Hi, After lot of tries I finally discovered a configuration that works: I had to patch my stock kernel with the devmapper patch from Debian kernel patches. With the devmapper patch applied, mkinitrd works like a charm, and so does kernel package: I could build .debs for my 2.4.31 kernel and now they install fine (I'm now running on it). As I said in first message I'm using LVM2 but this is not part of the stock kernel (seems to be the primary reason for mkinitrd failure); Unfortunately LVM2 packages don't warn you about this when you install them, and mkinitrd error message is misleading (I didn't know at first that LVM2 wasn't available in a stock kernel). -- Hope this helps, Fabien. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
