Bug#555531: linux-image-2.6.26-2-amd64: sound not working in OSS games after update
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-19lenny2 Severity: normal After the latest kernel update, sound no longer works in tyr-quake or other id engine games. I have 'tyr-quake 0 0 disable direct' in /proc/asound/card0/pcm0p/oss. It was working the day before I updated. bran...@brandon-desktop:~$ tyr-quake Added packfile /home/brandon/.tyrquake/id1/pak0.pak (339 files) Added packfile /home/brandon/.tyrquake/id1/pak1.pak (85 files) Playing registered version. Console initialized. UDP, Local address: 127.0.1.1 UDP Initialized (127.0.1.1) Exe: 21:53:41 Nov 5 2009 8.0 megabyte heap Using XFree86-VidModeExtension Version 2.2 600k surface cache VID: shared memory id=589840, addr=0xf73ff000 VID: shared memory id=622609, addr=0xf73c Sound Initialization GETOSPACE: Invalid argument Um, can't do GETOSPACE? S_Startup: SNDDMA_Init failed. CD Audio Initialized CDAudio_Init: No CD in player. Callback: in_dgamouse ON Callback: _windowed_mouse OFF 3 demo(s) in loop Playing demo from demo1.dem. Quake Initialized= TyrQuake -- Version 0.61 -- Package-specific info: ** Version: Linux version 2.6.26-2-amd64 (Debian 2.6.26-19lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 21:38:07 UTC 2009 ** Command line: root=/dev/md1 ro quiet ** Tainted: P (1) ** Kernel log: [ 11.587012] ivtv: Start initialization, version 1.3.0 [ 11.587112] ivtv0: Initializing card #0 [ 11.587115] ivtv0: Autodetected Hauppauge card (cx23416 based) [ 11.587403] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18 [ 11.587411] ACPI: PCI Interrupt :05:08.0[A] - Link [APC3] - GSI 18 (level, low) - IRQ 18 [ 11.587419] ivtv0: Unreasonably low latency timer, setting to 64 (was 32) [ 11.639406] tveeprom 2-0050: Hauppauge model 26132, rev F0B2, serial# 9399668 [ 11.639409] tveeprom 2-0050: tuner model is TCL M2523_5N_E (idx 112, type 50) [ 11.639412] tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) [ 11.639414] tveeprom 2-0050: audio processor is CX25841 (idx 35) [ 11.639416] tveeprom 2-0050: decoder processor is CX25841 (idx 28) [ 11.639419] tveeprom 2-0050: has no radio, has IR receiver, has IR transmitter [ 11.639421] ivtv0: Autodetected Hauppauge WinTV PVR-150 [ 11.639423] ivtv0: Reopen i2c bus for IR-blaster support [ 11.730777] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22 [ 11.730781] ACPI: PCI Interrupt :00:04.0[A] - Link [APCJ] - GSI 22 (level, low) - IRQ 22 [ 11.730801] PCI: Setting latency timer of device :00:04.0 to 64 [ 11.930189] cx25840 2-0044: cx25841-24 found @ 0x88 (ivtv i2c driver #0) [ 11.939249] tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) [ 11.939270] wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) [ 12.048024] input: PC Speaker as /class/input/input5 [ 12.052023] intel8x0_measure_ac97_clock: measured 54691 usecs [ 12.052026] intel8x0: clocking to 46878 [ 12.113405] tuner-simple 2-0061: creating new instance [ 12.113409] tuner-simple 2-0061: type set to 50 (TCL 2002N) [ 12.114714] ivtv0: Registered device video0 for encoder MPG (4096 kB) [ 12.114731] ivtv0: Registered device video32 for encoder YUV (2048 kB) [ 12.114748] ivtv0: Registered device vbi0 for encoder VBI (1024 kB) [ 12.114764] ivtv0: Registered device video24 for encoder PCM (320 kB) [ 12.114767] ivtv0: Initialized card #0: Hauppauge WinTV PVR-150 [ 12.114869] ivtv: End initialization [ 12.321773] pnp: the driver 'parport_pc' has been registered [ 12.321790] parport_pc 00:09: reported by Plug and Play ACPI [ 12.321838] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [ 12.362087] pnp: the driver 'mpu401' has been registered [ 12.386907] pnp: the driver 'ns558' has been registered [ 12.416083] parport_pc 00:09: driver attached [ 12.416901] mpu401 00:0b: driver attached [ 12.416922] ns558 00:0c: driver attached [ 12.443349] gameport: NS558 PnP Gameport is pnp00:0c/gameport0, io 0x201, speed 926kHz [ 13.462036] Adding 979956k swap on /dev/sda2. Priority:-1 extents:1 across:979956k [ 13.480001] Adding 979956k swap on /dev/sdb2. Priority:-2 extents:1 across:979956k [ 13.822002] EXT3 FS on md1, internal journal [ 14.062121] loop: module loaded [ 14.145708] lirc_dev: IR Remote Control driver registered, major 61 [ 14.215954] bttv: driver version 0.9.17 loaded [ 14.215958] bttv: using 8 buffers with 2080k (520 pages) each for capture [ 14.292350] cx88/0: cx2388x v4l2 driver version 0.0.6 loaded [ 14.310488] lirc_i2c: chip 0x10020 found @ 0x71 (Hauppauge PVR150) [ 14.310507] lirc_dev: lirc_register_driver: sample_rate: 10 [ 14.821916] fuse init (API version 7.9) [ 14.930633] kjournald starting. Commit interval 5 seconds [ 14.936152] EXT3 FS on hdb1, internal journal [ 14.936156] EXT3-fs: mounted filesystem with ordered data mode. [ 16.317685] skge eth1: enabling interface [ 17.023853] powernow-k8: Found 1 AMD Athlon(tm) 64
Bug#555512: marked as done (linux-libc-dev: Querying Debian BTS for reports on linux-2.6 (source)...)
Your message dated Tue, 10 Nov 2009 10:00:00 +0100 with message-id 20091110085959.ga8...@wavehammer.waldi.eu.org and subject line Re: Bug#12: linux-libc-dev: Querying Debian BTS for reports on linux-2.6 (source)... has caused the Debian Bug report #12, regarding linux-libc-dev: Querying Debian BTS for reports on linux-2.6 (source)... to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 12: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=12 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-libc-dev Version: 2.6.30-8 Severity: important -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.31.5-netxx01 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information timex.h is missing: #define MOD_NANO ADJ_NANO This breaks ntp. (I have submitted a workaround patch to the ntp maintainers, but the bug is really in the kernel headers/this package.) ---End Message--- ---BeginMessage--- On Mon, Nov 09, 2009 at 10:53:26PM -0500, Christopher Hoover wrote: timex.h is missing: #define MOD_NANO ADJ_NANO This breaks ntp. (I have submitted a workaround patch to the ntp maintainers, but the bug is really in the kernel headers/this package.) No. The MOD_* defines are already described as compatibility names. The mentioned name was added since Lenny, so it does not fall into any backward compatibility class. If you think this is a bug, please discuss it with Linux upstream, I don't see one, closing. Bastian -- Those who hate and fight must stop themselves -- otherwise it is not stopped. -- Spock, Day of the Dove, stardate unknown ---End Message---
Re: [PATCH] postinst: get rid of reverse symlinks handling
On Mon, 09 Nov 2009, Sebastian Andrzej Siewior wrote: maximilian suggested to grab an axe and rip the reverse symlinks handling out. The man page for kernel-img.conf has no reference to it anymore. Signed-off-by: Sebastian Andrzej Siewior sebast...@breakpoint.cc thanks a lot, applied. :) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#548290: A solution (for me, at least)
Hi Christophe, Good work. I found this bug on util-linux pertaining to this issue: udev: root partition's UUID not detected http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552578 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504391: Please enable CONFIG_MMC_UNSAFE_RESUME
On Tue, Nov 10, 2009 at 12:51:27PM +0100, Wouter van Heyst wrote: I second the request for turning CONFIG_MMC_UNSAFE_RESUME on, for me with /home on a SD card fixed firmly in it's slot, having it turned on is the only safe option. Off: filesystem corruption after suspend/resume On: everything works fine And for the majority of SD/MMC card users, the choice is: off: everything works fine on: filesystem corruption after card change while system is off I don't think we should change the default to suit the minority of users with hardware that abuses SD/MMC for fixed storage devices. However this probably should be a module option rather than a compile-time option. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504391: Please enable CONFIG_MMC_UNSAFE_RESUME
On Tue, Nov 10, 2009 at 02:51:52PM +, Ben Hutchings wrote: On Tue, Nov 10, 2009 at 12:51:27PM +0100, Wouter van Heyst wrote: I second the request for turning CONFIG_MMC_UNSAFE_RESUME on, for me with /home on a SD card fixed firmly in it's slot, having it turned on is the only safe option. Off: filesystem corruption after suspend/resume On: everything works fine And for the majority of SD/MMC card users, the choice is: off: everything works fine on: filesystem corruption after card change while system is off I don't think we should change the default to suit the minority of users with hardware that abuses SD/MMC for fixed storage devices. Ah. I had thought that switching a card while the system is off would be far more rare. I see my view is limited to netbooks, quite disjunct from, say, photographers. However this probably should be a module option rather than a compile-time option. Yes, rebuilding kernels myself every time there is a security update has become tiring. The impact of CONFIG_MMC_UNSAFE_RESUME seems to be contstrained to let #define mmc_suspend NULL #define mmc_resume NULL #define mmc_sd_suspend NULL #define mmc_sd_resume NULL if it's not defined, and with implementations otherwise, filling the mmc_ops and mmc_sd_ops structs. After that my kernel fu is too weak. What needs to be done to get this to be a module option? Wouter van Heyst -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: linux-image-2.6.29-1-686: please add CONFIG_MOUSE_PS2_ELANTECH=y for the Asus eee pc 1000
Processing commands for cont...@bugs.debian.org: retitle 522920 linux-2.6: please set CONFIG_MOUSE_PS2_ELANTECH=y (for various EeePC models) Bug #522920 [linux-2.6] linux-image-2.6.29-1-686: please add CONFIG_MOUSE_PS2_ELANTECH=y for the Asus eee pc 1000 Changed Bug title to 'linux-2.6: please set CONFIG_MOUSE_PS2_ELANTECH=y (for various EeePC models)' from 'linux-image-2.6.29-1-686: please add CONFIG_MOUSE_PS2_ELANTECH=y for the Asus eee pc 1000' usertag 522920 debian-eeepc-de...@lists.alioth.debian.org Bug#522920: linux-2.6: please set CONFIG_MOUSE_PS2_ELANTECH=y (for various EeePC models) User is li...@youmustbejoking.demon.co.uk There were no usertags set. Usertags are now: debian-eeepc-de...@lists.alioth.debian.org. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555531: linux-image-2.6.26-2-amd64: sound not working in OSS games after update
On Tue, Nov 10, 2009 at 12:16:19AM -0800, Brandon Del Bel wrote: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-19lenny2 Severity: normal After the latest kernel update, sound no longer works in tyr-quake or other id engine games. I have 'tyr-quake 0 0 disable direct' in /proc/asound/card0/pcm0p/oss. It was working the day before I updated. Can you revert to the 2.6.26-19lenny1 kernel and retest? I don't see anything new in 19lenny2 that could obviously break this. It would also be useful to verify w/o the nvidia driver loaded, if possible. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#522920: linux-image-2.6.29-1-686: please add CONFIG_MOUSE_PS2_ELANTECH=y for the Asus eee pc 1000
retitle 522920 linux-2.6: please set CONFIG_MOUSE_PS2_ELANTECH=y (for various EeePC models) usertag 522920 debian-eeepc-de...@lists.alioth.debian.org thanks The issue is about kernel support. All that's needed to allow this bug report to be closed is for CONFIG_MOUSE_PS2_ELANTECH to be enabled. Lenny userland stuff is a separate, though related, issue (but see http://alioth.debian.org/~dsalt-guest/eee/ for new-enough X drivers). -- | Darren Salt| linux at youmustbejoking | nr. Ashington, | Doon | using Debian GNU/Linux | or ds,demon,co,uk| Northumberland | Army | + http://www.youmustbejoking.demon.co.uk/ If I save time, when do I get to spend it? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555526: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot
On Tue, Nov 10, 2009 at 01:15:40AM -0600, Karl O. Pinc wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-19lenny2 Severity: normal Hello, I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2 with the latest security update and I found my system would hang during the boot. By 'hang' I mean that the boot process seems to stop -- no further messages on the console and the network never came up. Would you be able to test the 2.6.26-19lenny1 kernel to verify that it did work? I don't see anything in 2.6.26-19lenny2 that could obviously cause this, so it would be good to confirm that we're looking in the right place. -- dann frazier -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555640: linux-image-2.6.31-1-amd64: wifi network does not start
Package: linux-2.6 Version: 2.6.31-1 Severity: important Hello, When I start the kernel 2.6.31, the wifi does not start, while it runs correctly with the kernel 2.6.30. It seems that the wireless parameters of /etc/network/interfaces are not given to the script /etc/network/if-pre-up.d/wireless-tools. As you may see in the kernel log, wlan0 is 'not ready' at system startup time. Looking at the device by iwconfig shows empty values but scanning by iwlist works correctly. To make the device work, I must set manually the iwconfig parameters: # iwconfig wlan0 essid moine mode managed enc ... and then start the dhcp client (both dhclient3 and dhcpcd give the same results). If I try to set down and then up the device, I get: - down r...@tele:/home/jef# ifdown -v wlan0 Configuring interface wlan0=wlan0 (inet) run-parts --verbose /etc/network/if-down.d dhcpcd -k wlan0 ifconfig wlan0 down run-parts --verbose /etc/network/if-post-down.d run-parts: executing /etc/network/if-post-down.d/wireless-tools Error for wireless request Set Mode (8B06) : SET failed on device wlan0 ; Invalid argument. - up r...@tele:/home/jef# ifup -v wlan0 Configuring interface wlan0=wlan0 (inet) run-parts --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wireless-tools dhcpcdwlan0 err, wlan0: timed out warn, wlan0: using IPV4LL address 169.254.12.77 run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/mountnfs dhcpcd.sh: interface wlan0 has been configured with new IP=169.254.12.77 and iwconfig shows empty values. I am not new to Linux, but I could not find how the kernel might change the scanning of the configuration file! Regards. -- Package-specific info: ** Version: Linux version 2.6.31-1-amd64 (Debian 2.6.31-1) (wa...@debian.org) (gcc version 4.3.4 (Debian 4.3.4-5) ) #1 SMP Sat Oct 24 17:50:31 UTC 2009 ** Command line: root=/dev/sda3 ro ** Not tainted ** Kernel log: [4.471076] ACPI: Power Button [PWRF] [4.471208] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3 [4.471260] ACPI: Power Button [PWRB] [4.486250] ACPI: WMI: Mapper loaded [4.563771] input: PC Speaker as /devices/platform/pcspkr/input/input4 [4.731341] EDAC MC: Ver: 2.1.0 Oct 24 2009 [4.735285] k8temp :00:18.3: Temperature readouts might be wrong - check erratum #141 [4.771345] EDAC amd64_edac: Ver: 3.2.0 Oct 24 2009 [4.771635] EDAC amd64: This node reports that Memory ECC is currently disabled. [4.771688] EDAC amd64: bit 0x40 in register F3x44 of the MISC_CONTROL device (:00:18.3) should be enabled [4.771742] EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded. [4.771744] Either Enable ECC in the BIOS, or use the 'ecc_enable_override' parameter. [4.771745] Might be a BIOS bug, if BIOS says ECC is enabled [4.771747] Use of the override can cause unknown side effects. [4.771935] amd64_edac: probe of :00:18.2 failed with error -22 [4.869786] i2c-adapter i2c-0: nForce2 SMBus adapter at 0x2d00 [4.869849] i2c-adapter i2c-1: nForce2 SMBus adapter at 0x2e00 [4.960033] Initializing USB Mass Storage driver... [4.960433] scsi4 : SCSI emulation for USB Mass Storage devices [4.960589] usb-storage: device found at 2 [4.960593] usb-storage: waiting for device to settle before scanning [4.960602] usbcore: registered new interface driver usb-storage [4.960643] USB Mass Storage support registered. [5.029065] cfg80211: Using static regulatory domain info [5.029107] cfg80211: Regulatory domain: US [5.029144] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [5.029194] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [5.029235] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [5.029275] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [5.029316] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [5.029356] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [5.029396] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [5.029443] cfg80211: Calling CRDA for country: US [5.188525] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5 [5.351562] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 21 [5.351608] HDA Intel :00:07.0: PCI INT A - Link[LAZA] - GSI 21 (level, low) - IRQ 21 [5.351708] HDA Intel :00:07.0: setting latency timer to 64 [5.940013] hda_codec: Unknown model for ALC888, trying auto-probe from BIOS... [5.956100] input: HDA Digital PCBeep as /devices/pci:00/:00:07.0/input/input6 [6.021172] phy0: Selected rate control algorithm 'minstrel' [6.021813] Registered led device: rt73usb-phy0::radio [6.021870] Registered led device: rt73usb-phy0::assoc [6.021924] Registered
Bug#537305: Still present in 2.6.30-2
On Tue, Oct 27, 2009 at 03:47:51PM -0400, Robert Jacobs wrote: I recently tried installing and rebooting into 2.6.30-2 on this machine -- the problem with dropping blocks of audio is still present. (This also happens on my desktop, which is an athlon-tbird with a snd-cmipci) 2.6.31 is present and available for testing. thanks Hi Maximilian- Just to let you know that I'm not just being a bad bug reporter -- 2.6.31 still hasn't made it into unstable (nor experimental?) for architectures other than amd64. Thanks- Robert -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555526: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot
On 11/10/2009 10:30:54 AM, dann frazier wrote: On Tue, Nov 10, 2009 at 01:15:40AM -0600, Karl O. Pinc wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-19lenny2 Severity: normal Hello, I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2 with the latest security update and I found my system would hang during the boot. Would you be able to test the 2.6.26-19lenny1 kernel to verify that it did work? I suspect the problem may not be in the kernel. Now that I've had time to think it seems significant that once I removed the serial console kernel parameters the system, eventually, dropped me into single user mode due to an fsck error. I was interacting with the the box via vga not the serial port. Though the vga gets kernel messages and eventually gets a getty it seems it does not get any of the regular boot messages. So that's where the hang is. I'd like to keep this report and send is somewhere, as an enhancement if nothing else. It sure would be nice if there was either a way to have whichever kernel parameter console=foo that happens to be the one being used actually work as the console throughout the whole boot process. (Grub does this, which probably contributed to my confusion because I was interacting with grub just fine.) Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555526: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot
Whoops. Sorry. Hit the send button by accident. On 11/10/2009 10:30:54 AM, dann frazier wrote: On Tue, Nov 10, 2009 at 01:15:40AM -0600, Karl O. Pinc wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-19lenny2 Severity: normal Hello, I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2 with the latest security update and I found my system would hang during the boot. Would you be able to test the 2.6.26-19lenny1 kernel to verify that it did work? I suspect the problem may not be in the kernel. Now that I've had time to think it seems significant that once I removed the serial console kernel parameters the system, eventually, dropped me into single user mode due to an fsck error. I was interacting with the the box via vga not the serial port. Though the vga gets kernel messages and eventually gets a getty it seems it does not get any of the regular boot messages. So that's where the hang is. I'd like to keep this report and send is somewhere, as an enhancement if nothing else. It sure would be nice if there was either a way to have whichever kernel parameter console=foo that happens to be the one being used actually work as the console throughout the whole boot process. (Grub does this, which probably contributed to my confusion because I was interacting with grub just fine.) Absent that at warning would be nice. Perhaps the kernel could emit something to those consoles not available to init noting that the action is happening elsewhere. I would also like to see some more documentation. I can't figure out just how it is that init gets the console it does. (I suspect it takes the last console=foo.) Thanks for the help. Karl k...@meme.com Free Software: You don't pay back, you pay forward. -- Robert A. Heinlein -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537305: Still present in 2.6.30-2
On Tue, Nov 10, 2009 at 11:48:35AM -0500, Robert Jacobs wrote: On Tue, Oct 27, 2009 at 03:47:51PM -0400, Robert Jacobs wrote: I recently tried installing and rebooting into 2.6.30-2 on this machine -- the problem with dropping blocks of audio is still present. (This also happens on my desktop, which is an athlon-tbird with a snd-cmipci) 2.6.31 is present and available for testing. thanks Hi Maximilian- Just to let you know that I'm not just being a bad bug reporter -- 2.6.31 still hasn't made it into unstable (nor experimental?) for architectures other than amd64. ftp master have just processed them so they should appear soonest. thanks for your patience. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555671: linux-image-2.6.26-2-686: Conflicts: yaird ( 0.0.13) but 0.0.12-25 is to be installed
Package: linux-image-2.6.26-2-686 Severity: normal Hi, in lenny linux-image-2.6.26-2-686 failed because it want a version of yaird that doesn't exist. Matthieu -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555673: /boot/vmlinuz-2.6.31-1-686: ipw* wireless driver does not support new rfkill framework
Package: linux-2.6 Version: 2.6.31-1 Severity: normal File: /boot/vmlinuz-2.6.31-1-686 Hi, I'm using a ipw2200 wireless card. The upcoming NetworkManager 0.8 package uses the new rfkill switch framework to determine the rfkill state. The ipw* drivers do not seem to use the new framework (I don't have any entry in /sys/class/rfkill for this device). There only is /sys/devices/pci:00/:00:1e.0/:02:02.0/rf_kill file, which I was told is a ipw* specific rfkill implementation. Cheers, Michael -- Package-sVpecific info: 02:02.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection [8086:4220] (rev 05) Subsystem: Hewlett-Packard Company Device [103c:12f5] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 128 (750ns min, 6000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 5 Region 0: Memory at 9000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ipw2200 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.31-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.31-1-686 depends on: ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.11-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.31-1-686 recommends: ii firmware-linux-free 2.6.31-1 Binary firmware for various driver ii libc6-i6862.10.1-6 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.31-1-686 suggests: pn grub | lilo none (no description available) pn linux-doc-2.6.31 none (no description available) Versions of packages linux-image-2.6.31-1-686 is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) ii firmware-ipw2x00 0.21 Binary firmware for Intel Pro Wire pn firmware-ivtv none (no description available) pn firmware-iwlwifi none (no description available) pn firmware-linuxnone (no description available) ii firmware-linux-nonfree0.21 Binary firmware for various driver pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555676: initramfs-tools: initram image fails to boot crypto disks because of wrong quotes
Package: initramfs-tools
Version: 0.93.4
Severity: normal
Tags:
Hi, I am using luks encryption on my whole filesystem, debian squeeze
on an Acer Aspire One.
After upgrading packages this evening, I booted from the new kernel
(2.6.30-2-686): the system did not ask for
the luks passphrase, saying unterminated quotes error in
/scripts/local-top/cryptroot
(absolute path for script included in initram image).
I checked the syntax of the script (original path
/usr/share/initramfs-tools/scripts/local-top/cryptroot) with bash
-v,
and found out that the new script version fails to correctly bash-expand
the kernel cryptopts option you can see below
(cryptopts=target=sda2_crypt,source=/dev/sda2,lvm=wudangshan-root):
the syntax {$x%=*} in the script gives
$PARAM: target (uncorrect param because of leading , correct VALUE)
$PARAM: source (correct PARAM, correct VALUE)
$PARAM: lvm
$VALUE: wudangshan-root (correct PARAM, uncorrect VALUE because of trailing ).
I stress that the syntax of the kernel command line option did not
cause any problem with previous releases, so
it should be correct, as far as I know.
I made a workaround by adding
if [ $PARAM = lvm ]; then
VALUE=wudangshan-root
elif [ $PARAM = \target ]; then
PARAM=target
fi
before line 130 (i.e. before eval export CRYPTTAB_OPTION..)
I recreated the initram image for this kernel and rebooted the system:
the system now boots without any problem.
This works for me because I have this certain order of cryptopts in
the kernel cmdline.: a generic patch
that strips quotes from all the cryptopts is needed, I think.
As far as I know (I checked in the squeeze packages list), the script
I modified is included in initramfs-tools.
I also read the package buglist to check if this bug has been already
submitted, but I did not found anything.
I apologize if I failed to notice a previous bug report concerning this issue.
Best regards,
Pietro
P.S. In the following I cut the lsmod info, that seemed to me to be
uncorrelated with the issue.
-- Package-specific info:
-- /proc/cmdline
root=/dev/mapper/wudangshan-root ro
cryptopts=target=sda2_crypt,source=/dev/sda2,lvm=wudangshan-root
-- /etc/crypttab
# target name source device key file options
wudangshan-root /dev/sda2 noneluks,lvm=wudangshan-root
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages initramfs-tools depends on:
ii cpio 2.10-1 GNU cpio -- a program to manage ar
ii findutils 4.4.2-1utilities for finding files--find,
ii klibc-utils 1.5.15-1 small utilities built with klibc f
ii module-init-tools 3.11-1 tools for managing Linux kernel mo
ii udev 146-5 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.14.2-2 Tiny utilities for small and embed
initramfs-tools suggests no packages.
-- no debconf information
--
It is better to be a warrior in a garden than to be a gardener in a war.
If you have to write your ethics rules down, you've already lost.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555680: System information in bug reports may be security-sensitive
Package: linux-2.6 Version: 2.6.31-1 Severity: normal Tags: security The bug script now offers to include network configuration and status. The network configuration file /etc/network/interfaces may include encryption keys for wireless networks, which we should scrub. There is also a more general problem of sensitive information in the kernel log, but I'm not sure what we can do about that. Ben. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.31-1-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
Processed: severity of 555673 is wishlist
Processing commands for cont...@bugs.debian.org: severity 555673 wishlist Bug #555673 [linux-2.6] /boot/vmlinuz-2.6.31-1-686: ipw* wireless driver does not support new rfkill framework Severity set to 'wishlist' from 'normal' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555640: linux-image-2.6.31-1-amd64: wifi network does not start
On Tue, 2009-11-10 at 18:40 +0100, Jean-Francois Moine wrote: Package: linux-2.6 Version: 2.6.31-1 Severity: important Hello, When I start the kernel 2.6.31, the wifi does not start, while it runs correctly with the kernel 2.6.30. It seems that the wireless parameters of /etc/network/interfaces are not given to the script /etc/network/if-pre-up.d/wireless-tools. As you may see in the kernel log, wlan0 is 'not ready' at system startup time. This is normal. A wireless network interface only becomes 'ready' when it is associated with a network. [...] r...@tele:/home/jef# ifup -v wlan0 Configuring interface wlan0=wlan0 (inet) run-parts --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wireless-tools dhcpcdwlan0 err, wlan0: timed out warn, wlan0: using IPV4LL address 169.254.12.77 run-parts --verbose /etc/network/if-up.d run-parts: executing /etc/network/if-up.d/mountnfs dhcpcd.sh: interface wlan0 has been configured with new IP=169.254.12.77 and iwconfig shows empty values. I am not new to Linux, but I could not find how the kernel might change the scanning of the configuration file! Of course it doesn't. But it seems as if the wireless configuration set before the interface is brought up is being discarded by the kernel for some reason. Please report this upstream at http://bugzilla.kernel.org and let us know the bug number. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Bug#555531: linux-image-2.6.26-2-amd64: sound not working in OSS games after update
On Tue, Nov 10, 2009 at 8:41 AM, dann frazier da...@debian.org wrote: Can you revert to the 2.6.26-19lenny1 kernel and retest? I don't see anything new in 19lenny2 that could obviously break this. It would also be useful to verify w/o the nvidia driver loaded, if possible. -- dann frazier I reverted and the problem still occurred. I also temporarily uninstalled the nvidia module, but that didn't help. It's possible that I did something dumb, and the timing of the kernel update was coincidental, but I can't imagine what that would be. According to synaptic's history, these are the only packages that changed between when sound was working and when it wasn't: kdelibs-data (4:3.5.10.dfsg.1-0lenny2) to 4:3.5.10.dfsg.1-0lenny3 kdelibs4c2a (4:3.5.10.dfsg.1-0lenny2) to 4:3.5.10.dfsg.1-0lenny3 linux-headers-2.6.26-2-amd64 (2.6.26-19lenny1) to 2.6.26-19lenny2 linux-headers-2.6.26-2-common (2.6.26-19lenny1) to 2.6.26-19lenny2 linux-image-2.6.26-2-686 (2.6.26-19lenny1) to 2.6.26-19lenny2 linux-image-2.6.26-2-amd64 (2.6.26-19lenny1) to 2.6.26-19lenny2 linux-libc-dev (2.6.26-19lenny1) to 2.6.26-19lenny2 -Brandon Del Bel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555671: marked as done (linux-image-2.6.26-2-686: Conflicts: yaird ( 0.0.13) but 0.0.12-25 is to be installed)
Your message dated Wed, 11 Nov 2009 02:40:53 + with message-id 1257907253.2237.44.ca...@localhost and subject line Re: Bug#555671: linux-image-2.6.26-2-686: Conflicts: yaird ( 0.0.13) but 0.0.12-25 is to be installed has caused the Debian Bug report #555671, regarding linux-image-2.6.26-2-686: Conflicts: yaird ( 0.0.13) but 0.0.12-25 is to be installed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 555671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Severity: normal Hi, in lenny linux-image-2.6.26-2-686 failed because it want a version of yaird that doesn't exist. Matthieu ---End Message--- ---BeginMessage--- On Wed, 2009-11-11 at 00:14 +0100, matthieu castet wrote: Package: linux-image-2.6.26-2-686 Severity: normal Hi, in lenny linux-image-2.6.26-2-686 failed because it want a version of yaird that doesn't exist. No, it *conflicts* with the old version of yaird that you have installed. yaird is not included in 'lenny'; you should use initramfs-tools instead. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part ---End Message---
Bug#504391: [PATCH] mmc: add module parameter to set whether cards are assumed removable
Some people run general-purpose distribution kernels on netbooks with
a card that is physically non-removable or logically non-removable
(e.g. used for /home) and cannot be cleanly unmounted during suspend.
Add a module parameter to set whether cards are assumed removable or
non-removable, with the default set by CONFIG_MMC_UNSAFE_RESUME.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
drivers/mmc/core/Kconfig |4 +++-
drivers/mmc/core/core.c | 16
drivers/mmc/core/core.h |2 ++
drivers/mmc/core/mmc.c | 23 +--
drivers/mmc/core/sd.c| 21 +
5 files changed, 23 insertions(+), 43 deletions(-)
diff --git a/drivers/mmc/core/Kconfig b/drivers/mmc/core/Kconfig
index ab37a6d..bb22ffd 100644
--- a/drivers/mmc/core/Kconfig
+++ b/drivers/mmc/core/Kconfig
@@ -3,7 +3,7 @@
#
config MMC_UNSAFE_RESUME
- bool Allow unsafe resume (DANGEROUS)
+ bool Assume MMC/SD cards are non-removable (DANGEROUS)
help
If you say Y here, the MMC layer will assume that all cards
stayed in their respective slots during the suspend. The
@@ -14,3 +14,5 @@ config MMC_UNSAFE_RESUME
This option is usually just for embedded systems which use
a MMC/SD card for rootfs. Most people should say N here.
+ This option sets a default which can be overridden by the
+ module parameter removable=0 or removable=1.
diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
index d98b0e2..010c964 100644
--- a/drivers/mmc/core/core.c
+++ b/drivers/mmc/core/core.c
@@ -48,6 +48,22 @@ int use_spi_crc = 1;
module_param(use_spi_crc, bool, 0);
/*
+ * We normally treat cards as removed during suspend if they are not
+ * known to be on a non-removable bus, to avoid the risk of writing
+ * back data to a different card after resume. Allow this to be
+ * overridden if necessary.
+ */
+#ifdef CONFIG_MMC_UNSAFE_RESUME
+int mmc_assume_removable;
+#else
+int mmc_assume_removable = 1;
+#endif
+module_param_named(removable, mmc_assume_removable, bool, 0644);
+MODULE_PARM_DESC(
+ removable,
+ MMC/SD cards are removable and may be removed during suspend);
+
+/*
* Internal function. Schedule delayed work in the MMC work queue.
*/
static int mmc_schedule_delayed_work(struct delayed_work *work,
diff --git a/drivers/mmc/core/core.h b/drivers/mmc/core/core.h
index 1c68783..d20b7bc 100644
--- a/drivers/mmc/core/core.h
+++ b/drivers/mmc/core/core.h
@@ -64,7 +64,9 @@ int mmc_attach_mmc(struct mmc_host *host, u32 ocr);
int mmc_attach_sd(struct mmc_host *host, u32 ocr);
int mmc_attach_sdio(struct mmc_host *host, u32 ocr);
+/* Module parameters */
extern int use_spi_crc;
+extern int mmc_assume_removable;
/* Debugfs information for hosts and cards */
void mmc_add_host_debugfs(struct mmc_host *host);
diff --git a/drivers/mmc/core/mmc.c b/drivers/mmc/core/mmc.c
index bfefce3..c111894 100644
--- a/drivers/mmc/core/mmc.c
+++ b/drivers/mmc/core/mmc.c
@@ -602,25 +602,6 @@ static int mmc_awake(struct mmc_host *host)
return err;
}
-#ifdef CONFIG_MMC_UNSAFE_RESUME
-
-static const struct mmc_bus_ops mmc_ops = {
- .awake = mmc_awake,
- .sleep = mmc_sleep,
- .remove = mmc_remove,
- .detect = mmc_detect,
- .suspend = mmc_suspend,
- .resume = mmc_resume,
- .power_restore = mmc_power_restore,
-};
-
-static void mmc_attach_bus_ops(struct mmc_host *host)
-{
- mmc_attach_bus(host, mmc_ops);
-}
-
-#else
-
static const struct mmc_bus_ops mmc_ops = {
.awake = mmc_awake,
.sleep = mmc_sleep,
@@ -645,15 +626,13 @@ static void mmc_attach_bus_ops(struct mmc_host *host)
{
const struct mmc_bus_ops *bus_ops;
- if (host-caps MMC_CAP_NONREMOVABLE)
+ if (host-caps MMC_CAP_NONREMOVABLE || !mmc_assume_removable)
bus_ops = mmc_ops_unsafe;
else
bus_ops = mmc_ops;
mmc_attach_bus(host, bus_ops);
}
-#endif
-
/*
* Starting point for MMC card init.
*/
diff --git a/drivers/mmc/core/sd.c b/drivers/mmc/core/sd.c
index 10b2a4d..fdd414e 100644
--- a/drivers/mmc/core/sd.c
+++ b/drivers/mmc/core/sd.c
@@ -606,23 +606,6 @@ static void mmc_sd_power_restore(struct mmc_host *host)
mmc_release_host(host);
}
-#ifdef CONFIG_MMC_UNSAFE_RESUME
-
-static const struct mmc_bus_ops mmc_sd_ops = {
- .remove = mmc_sd_remove,
- .detect = mmc_sd_detect,
- .suspend = mmc_sd_suspend,
- .resume = mmc_sd_resume,
- .power_restore = mmc_sd_power_restore,
-};
-
-static void mmc_sd_attach_bus_ops(struct mmc_host *host)
-{
- mmc_attach_bus(host, mmc_sd_ops);
-}
-
-#else
-
static const struct mmc_bus_ops mmc_sd_ops = {
.remove = mmc_sd_remove,
.detect = mmc_sd_detect,
@@ -643,15 +626,13 @@ static void mmc_sd_attach_bus_ops(struct mmc_host *host)
{
const struct mmc_bus_ops *bus_ops;
- if (host-caps MMC_CAP_NONREMOVABLE)
+ if
Re: Bug#555531: linux-image-2.6.26-2-amd64: sound not working in OSS games after update
On Tue, 2009-11-10 at 18:52 -0800, Brandon Del Bel wrote: On Tue, Nov 10, 2009 at 8:41 AM, dann frazier da...@debian.org wrote: Can you revert to the 2.6.26-19lenny1 kernel and retest? I don't see anything new in 19lenny2 that could obviously break this. It would also be useful to verify w/o the nvidia driver loaded, if possible. -- dann frazier I reverted and the problem still occurred. I also temporarily uninstalled the nvidia module, but that didn't help. It's possible that I did something dumb, and the timing of the kernel update was coincidental, but I can't imagine what that would be. [...] After a kernel upgrade, you reboot. If you don't reboot often, you may then find that forgot to save some configuration changes that you made on the running system. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
