Re: Compiling module-init-tools versions after v3.0
On 8/8/05, Adrian Bunk <[EMAIL PROTECTED]> wrote: > Workaround: > > Remove the > > man_MANS = $(MAN5) $(MAN8) > > line in Makefile.in before running configure. On 8/8/05, Ken Moffat <[EMAIL PROTECTED]> wrote: > per LFS (http://www.linuxfromscratch.org/lfs/) make DOCBOOKTOMAN="" > (or look at BLFS for the gory details of docbook) Thank you both. Both of those workarounds seem to work for now. > But this could be better handled in module-init-tools. Here's hoping it will be once 3.2 is released. Thanks again. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Compiling module-init-tools versions after v3.0
Hello. I'm trying to upgrade one of my machines to module-init-tools-3.2-pre8 so that I can better assist a driver developer in debugging some issues with the OPL3SA2 driver from ALSA. The machine is currently running a slightly-modified Slackware 9.1 distribution (I've updated several packages to support the 2.6 kernel and other upgrades since the first install). I currently have module-init-tools 3.0 installed but I'd like to install version 3.2-pre8. The problem is that compiling module-init-tools versions after 3.0 seem require docbook-utils (the compile fails on a docbook2man operation) to be installed and docbook-utils requires jade which will not compile. I found one jade package called jade-1.2.1 (from '98 or '99) which will not compile. I tried openjade, but it does not seem to work when compiling docbook-tools (I made a symlink from the openjade binary to "jade"). Is there some other package that I'm overlooking that's required to get docbook-utils installed? If not, how have other people compiled and installed newer versions of module-init-tools? Thanks. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Compiling module-init-tools versions after v3.0
Hello. I'm trying to upgrade one of my machines to module-init-tools-3.2-pre8 so that I can better assist a driver developer in debugging some issues with the OPL3SA2 driver from ALSA. The machine is currently running a slightly-modified Slackware 9.1 distribution (I've updated several packages to support the 2.6 kernel and other upgrades since the first install). I currently have module-init-tools 3.0 installed but I'd like to install version 3.2-pre8. The problem is that compiling module-init-tools versions after 3.0 seem require docbook-utils (the compile fails on a docbook2man operation) to be installed and docbook-utils requires jade which will not compile. I found one jade package called jade-1.2.1 (from '98 or '99) which will not compile. I tried openjade, but it does not seem to work when compiling docbook-tools (I made a symlink from the openjade binary to jade). Is there some other package that I'm overlooking that's required to get docbook-utils installed? If not, how have other people compiled and installed newer versions of module-init-tools? Thanks. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Compiling module-init-tools versions after v3.0
On 8/8/05, Adrian Bunk [EMAIL PROTECTED] wrote: Workaround: Remove the man_MANS = $(MAN5) $(MAN8) line in Makefile.in before running configure. On 8/8/05, Ken Moffat [EMAIL PROTECTED] wrote: per LFS (http://www.linuxfromscratch.org/lfs/) make DOCBOOKTOMAN= (or look at BLFS for the gory details of docbook) Thank you both. Both of those workarounds seem to work for now. But this could be better handled in module-init-tools. Here's hoping it will be once 3.2 is released. Thanks again. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops when shutting down laptop
On 8/4/05, Kristian Grønfeldt Sørensen <[EMAIL PROTECTED]> wrote: > http://www.vkr.dk/~kriller/oops.jpg Sorry that I can't help. I actually have a machine that's Oops'ing during software suspend (with suspend2). I typed it all up last night, which was terribly time-consuming. I have another laptop, but it doesn't have any serial ports. I've tried taking pictures, but you can't read the text. How did you get that image? With a scan-converter? Thanks. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Oops when shutting down laptop
On 8/4/05, Kristian Grønfeldt Sørensen [EMAIL PROTECTED] wrote: http://www.vkr.dk/~kriller/oops.jpg Sorry that I can't help. I actually have a machine that's Oops'ing during software suspend (with suspend2). I typed it all up last night, which was terribly time-consuming. I have another laptop, but it doesn't have any serial ports. I've tried taking pictures, but you can't read the text. How did you get that image? With a scan-converter? Thanks. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Alsa-devel] Re: [2.6 patch] schedule obsolete OSS drivers for removal
On 7/31/05, Adrian Bunk <[EMAIL PROTECTED]> wrote: > Can you send me the bug numbers in the ALSA bug tracking system if you > have to send bug reports, so that I can track when these issues will be > resolved? Thorsten: Please remember to include the list(s) when emailing those links/numbers. I'd like to be able to watch it, too, and add any information that I can, rather than entering a duplicate bug. Thanks. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Alsa-devel] Re: [2.6 patch] schedule obsolete OSS drivers for removal
On 7/31/05, Adrian Bunk [EMAIL PROTECTED] wrote: Can you send me the bug numbers in the ALSA bug tracking system if you have to send bug reports, so that I can track when these issues will be resolved? Thorsten: Please remember to include the list(s) when emailing those links/numbers. I'd like to be able to watch it, too, and add any information that I can, rather than entering a duplicate bug. Thanks. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6 patch] schedule obsolete OSS drivers for removal
On 7/26/05, Adrian Bunk <[EMAIL PROTECTED]> wrote: > config SOUND_OPL3SA2 > tristate "Yamaha OPL3-SA2 and SA3 based PnP cards" > - depends on SOUND_OSS > + depends on SOUND_OSS && OBSOLETE_OSS_DRIVER > help > Say Y or M if you have a card based on one of these Yamaha sound > chipsets or the "SAx", which is actually a SA3. Read Forgive me if I'm misreading this (I'm hardly a coder and no kernel hacker) but, as it stands, the OPL3SA2 driver provided by ALSA and the main kernel tree work but are not correctly detected by ALSA's detection routines (in alsaconf) on the 2.6 kernel. The OSS drivers work, as well, but (AFAIK) there are no methods of automatic configuration with the OSS drivers. So, for people who don't feel like configuring ALSA with their OPL3SA2 card, the OSS modules may be easier to configure and thus should be left in until the ALSA/2.6 kernel problems are worked out with the OPL3SA2. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: Yamaha OPL3SA2 does not work with ALSA on 2.6 kernels.
On 7/26/05, Andrew Haninger <[EMAIL PROTECTED]> wrote: > I'll report what I know in bug #879. *Durr* I didn't scroll down. I've already reported my current semi-working (works+oopses) setup in that bug report I'm reporting this here now because of the part of that bug report that suggests that it might actually be a kernel bug. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: Yamaha OPL3SA2 does not work with ALSA on 2.6 kernels.
On 7/26/05, Jaroslav Kysela <[EMAIL PROTECTED]> wrote: > We have already two similar reports #440 and #879. Please, provide us > all info (working manual conf etc.).. Yes. #879 is the one that mentions that this might be a kernel bug (so I reported it here): "I suspect this is kernel bug and it conserns ISA support. I would be happy if you kick some kernel developers buts because they have ignored my bugreport for quite long time now." I don't know how correct/incorrect the above may be, but I figured it was possible. I'll report what I know in bug #879. Thanks. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: Yamaha OPL3SA2 does not work with ALSA on 2.6 kernels.
On 7/26/05, Jaroslav Kysela [EMAIL PROTECTED] wrote: We have already two similar reports #440 and #879. Please, provide us all info (working manual conf etc.).. Yes. #879 is the one that mentions that this might be a kernel bug (so I reported it here): I suspect this is kernel bug and it conserns ISA support. I would be happy if you kick some kernel developers buts because they have ignored my bugreport for quite long time now. I don't know how correct/incorrect the above may be, but I figured it was possible. I'll report what I know in bug #879. Thanks. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: Yamaha OPL3SA2 does not work with ALSA on 2.6 kernels.
On 7/26/05, Andrew Haninger [EMAIL PROTECTED] wrote: I'll report what I know in bug #879. *Durr* I didn't scroll down. I've already reported my current semi-working (works+oopses) setup in that bug report I'm reporting this here now because of the part of that bug report that suggests that it might actually be a kernel bug. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [2.6 patch] schedule obsolete OSS drivers for removal
On 7/26/05, Adrian Bunk [EMAIL PROTECTED] wrote: config SOUND_OPL3SA2 tristate Yamaha OPL3-SA2 and SA3 based PnP cards - depends on SOUND_OSS + depends on SOUND_OSS OBSOLETE_OSS_DRIVER help Say Y or M if you have a card based on one of these Yamaha sound chipsets or the SAx, which is actually a SA3. Read Forgive me if I'm misreading this (I'm hardly a coder and no kernel hacker) but, as it stands, the OPL3SA2 driver provided by ALSA and the main kernel tree work but are not correctly detected by ALSA's detection routines (in alsaconf) on the 2.6 kernel. The OSS drivers work, as well, but (AFAIK) there are no methods of automatic configuration with the OSS drivers. So, for people who don't feel like configuring ALSA with their OPL3SA2 card, the OSS modules may be easier to configure and thus should be left in until the ALSA/2.6 kernel problems are worked out with the OPL3SA2. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: Yamaha OPL3SA2 does not work with ALSA on 2.6 kernels.
On 7/25/05, Adrian Bunk <[EMAIL PROTECTED]> wrote: > Does the OSS driver work in 2.6? I was able to get the OSS module (opl3sa2) installed in 2.6 and I was able to get some nice hiss when doing 'cat /dev/urandom > /dev/dsp'. I used the following modprobe line: modprobe opl3sa2 io=0x370 irq=11 dma=0 dma2=1 mss_io=0x530 isapnp=0 the isapnp=0 part appeared to be required. The following showed up in dmesg upon inserting the OSS module: opl3sa2: Chipset version = 0x7 opl3sa2: Found OPL3-SA3 (YMF715E or YMF719E) However, when I try to rmmod the opl3sa2 module, I get an Oops: Unable to handle kernel NULL pointer dereference at virtual address printing eip: c037ae01 *pde = Oops: 0002 [#1] PREEMPT Modules linked in: opl3sa2 ad1848 mpu401 sound soundcore vfat fat sd_mod usb_storage lp parport ide_scsi rtc CPU:0 EIP:0060:[]Not tainted VLI EFLAGS: 00010046 (2.6.12.2) EIP is at wait_for_completion+0x71/0xf0 eax: cca91180 ebx: c52ea000 ecx: c52ebf20 edx: esi: c52ea000 edi: cca9117c ebp: c52ebf40 esp: c52ebef4 ds: 007b es: 007b ss: 0068 Process rmmod (pid: 11277, threadinfo=c52ea000 task=c79ce550) Stack: c79ce550 c0113cf0 c52ea000 c0e899e0 c0209ffe 0001 c79ce550 c0113cf0 cca91180 0114 0001 cca91174 0114 0001 c52ea000 cca8f964 cca91174 cca91200 Call Trace: [] default_wake_function+0x0/0x20 [] kobject_put+0x1e/0x30 [] default_wake_function+0x0/0x20 [] cleanup_opl3sa2+0x74/0x8c [opl3sa2] [] sys_delete_module+0x178/0x1b0 [] sys_munmap+0x50/0x80 [] syscall_call+0x7/0xb Code: 00 00 8b 03 c7 45 d4 01 00 00 00 c7 45 bc f0 3c 11 c0 c7 45 dc f0 3c 11 c0 89 45 b8 89 45 d8 8d 47 04 8b 50 04 89 45 e0 89 48 04 <89> 0a 89 55 e4 8d 76 00 8d bc 27 00 00 00 00 8b 03 c7 00 02 00 <6>note: rmmod[11277] exited with preempt_count 1 and now when I try to rmmod the module again, I get: ERROR: Removing 'opl3sa2': Device or resource busy So, yes, given the correct parameters, the OSS module (just like the ALSA module) works with the occasional Oops. I guess the Oopses are acceptable for now; it's the ALSA detection routines that are broken themselves or that are broken by something in the 2.6 kernel (remember that they work fine in 2.4). Thanks. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: "seeing minute plus hangs during boot" - 2.6.12 and 2.6.13
On 7/22/05, Francisco Figueiredo Jr. <[EMAIL PROTECTED]> wrote: > Hangs appears just before mounting filesystems message and before configuring > system to use udev. I don't know if this will help, but there were issues raised earlier about older versions of udev causing hangs on newer kernels. Look for the thread with the subject "2.6.12 udev hangs at boot". Actually, look here: http://marc.theaimsgroup.com/?l=linux-kernel=111909806104523=2 Basically, upgrade to a newer udev if you're running an older one (I think I had 0.30 at the time; installing 0.58 sped things up noticeably). HTH. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG: Yamaha OPL3SA2 does not work with ALSA on 2.6 kernels.
Hello. I have a 5 year old Gateway Solo 2500 that is currently running Linux 2.6.12.2. If I install ALSA and try to have alsaconf bruteforce-detect the OPL3SA2 sound card, it will say that it has detected it, but loading the modules will fail. If I install Linux 2.4 and recompile/rerun alsaconf, the detection works fine and the card works. Copying the configuration detected under 2.4 into a modprobe.conf on 2.6 allows me to use the card in 2.6 with occasional crashes (which might be due to suspend2). Searching around the net, I find many other people having trouble with these cards and the ALSA-Linux2.6 combination. On one page, someone suggested that there were changes made between 2.4 and 2.6 to the ISA code that broke ALSA's detection routines. I'm not sure what information might be needed in order to get this card working well once and for all, but if someone will let me know, I'd be happy to provide. Thanks. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
BUG: Yamaha OPL3SA2 does not work with ALSA on 2.6 kernels.
Hello. I have a 5 year old Gateway Solo 2500 that is currently running Linux 2.6.12.2. If I install ALSA and try to have alsaconf bruteforce-detect the OPL3SA2 sound card, it will say that it has detected it, but loading the modules will fail. If I install Linux 2.4 and recompile/rerun alsaconf, the detection works fine and the card works. Copying the configuration detected under 2.4 into a modprobe.conf on 2.6 allows me to use the card in 2.6 with occasional crashes (which might be due to suspend2). Searching around the net, I find many other people having trouble with these cards and the ALSA-Linux2.6 combination. On one page, someone suggested that there were changes made between 2.4 and 2.6 to the ISA code that broke ALSA's detection routines. I'm not sure what information might be needed in order to get this card working well once and for all, but if someone will let me know, I'd be happy to provide. Thanks. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: seeing minute plus hangs during boot - 2.6.12 and 2.6.13
On 7/22/05, Francisco Figueiredo Jr. [EMAIL PROTECTED] wrote: Hangs appears just before mounting filesystems message and before configuring system to use udev. I don't know if this will help, but there were issues raised earlier about older versions of udev causing hangs on newer kernels. Look for the thread with the subject 2.6.12 udev hangs at boot. Actually, look here: http://marc.theaimsgroup.com/?l=linux-kernelm=111909806104523w=2 Basically, upgrade to a newer udev if you're running an older one (I think I had 0.30 at the time; installing 0.58 sped things up noticeably). HTH. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: Yamaha OPL3SA2 does not work with ALSA on 2.6 kernels.
On 7/25/05, Adrian Bunk [EMAIL PROTECTED] wrote: Does the OSS driver work in 2.6? I was able to get the OSS module (opl3sa2) installed in 2.6 and I was able to get some nice hiss when doing 'cat /dev/urandom /dev/dsp'. I used the following modprobe line: modprobe opl3sa2 io=0x370 irq=11 dma=0 dma2=1 mss_io=0x530 isapnp=0 the isapnp=0 part appeared to be required. The following showed up in dmesg upon inserting the OSS module: opl3sa2: Chipset version = 0x7 opl3sa2: Found OPL3-SA3 (YMF715E or YMF719E) However, when I try to rmmod the opl3sa2 module, I get an Oops: Unable to handle kernel NULL pointer dereference at virtual address printing eip: c037ae01 *pde = Oops: 0002 [#1] PREEMPT Modules linked in: opl3sa2 ad1848 mpu401 sound soundcore vfat fat sd_mod usb_storage lp parport ide_scsi rtc CPU:0 EIP:0060:[c037ae01]Not tainted VLI EFLAGS: 00010046 (2.6.12.2) EIP is at wait_for_completion+0x71/0xf0 eax: cca91180 ebx: c52ea000 ecx: c52ebf20 edx: esi: c52ea000 edi: cca9117c ebp: c52ebf40 esp: c52ebef4 ds: 007b es: 007b ss: 0068 Process rmmod (pid: 11277, threadinfo=c52ea000 task=c79ce550) Stack: c79ce550 c0113cf0 c52ea000 c0e899e0 c0209ffe 0001 c79ce550 c0113cf0 cca91180 0114 0001 cca91174 0114 0001 c52ea000 cca8f964 cca91174 cca91200 Call Trace: [c0113cf0] default_wake_function+0x0/0x20 [c0209ffe] kobject_put+0x1e/0x30 [c0113cf0] default_wake_function+0x0/0x20 [cca8f964] cleanup_opl3sa2+0x74/0x8c [opl3sa2] [c0131bc8] sys_delete_module+0x178/0x1b0 [c015b2c0] sys_munmap+0x50/0x80 [c0103205] syscall_call+0x7/0xb Code: 00 00 8b 03 c7 45 d4 01 00 00 00 c7 45 bc f0 3c 11 c0 c7 45 dc f0 3c 11 c0 89 45 b8 89 45 d8 8d 47 04 8b 50 04 89 45 e0 89 48 04 89 0a 89 55 e4 8d 76 00 8d bc 27 00 00 00 00 8b 03 c7 00 02 00 6note: rmmod[11277] exited with preempt_count 1 and now when I try to rmmod the module again, I get: ERROR: Removing 'opl3sa2': Device or resource busy So, yes, given the correct parameters, the OSS module (just like the ALSA module) works with the occasional Oops. I guess the Oopses are acceptable for now; it's the ALSA detection routines that are broken themselves or that are broken by something in the 2.6 kernel (remember that they work fine in 2.4). Thanks. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PS/2 Keyboard is dead after resume.
On 7/16/05, Dmitry Torokhov <[EMAIL PROTECTED]> wrote: > Ok, so you start with IRQ 12 disabled.. You don't have a PS/2 mouse, > do you? Nope :). > > serio: i8042 AUX port at 0x60,0x64 irq 12 > > serio: i8042 KBD port at 0x60,0x64 irq 1 > > You did not select PNP support (but as far as keyboard controller settings > go we don't trust it anyway on i386). I've never ever found it to work, so I usually disable it. > And here you have a bunch of hardware gets assigned to IRQ 12... > Hmm, I tought ACPI would try not use 12 unless it is absolutely > necessary. What appens if you use "pci=routeirq" boot option? The keyboard was still dead after resume. > You can try working around this with "i8042.noaux" kernel boot option, > but we should probably teach i8042 driver to not touch AUX port on resume > if it was disabled. This worked. Strangely enough, after googling for i8042 and suspend last night, I found the 2.6.12 kernel boot options file. I tried i8042.nomux, i8042.direct, and some others, but nothing worked. Just for fun, I tried booting without any kernel boot options (just the suspend2 option) and with a PS/2 mouse plugged in. On suspend, the keyboard worked. Maybe this could/should be added to the suspend2 code as well? Whatever. It works for now. If you'd like any more information, just let me know. Thanks! -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PS/2 Keyboard is dead after resume.
On 7/16/05, Dmitry Torokhov [EMAIL PROTECTED] wrote: Ok, so you start with IRQ 12 disabled.. You don't have a PS/2 mouse, do you? Nope :). serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 You did not select PNP support (but as far as keyboard controller settings go we don't trust it anyway on i386). I've never ever found it to work, so I usually disable it. And here you have a bunch of hardware gets assigned to IRQ 12... Hmm, I tought ACPI would try not use 12 unless it is absolutely necessary. What appens if you use pci=routeirq boot option? The keyboard was still dead after resume. You can try working around this with i8042.noaux kernel boot option, but we should probably teach i8042 driver to not touch AUX port on resume if it was disabled. This worked. Strangely enough, after googling for i8042 and suspend last night, I found the 2.6.12 kernel boot options file. I tried i8042.nomux, i8042.direct, and some others, but nothing worked. Just for fun, I tried booting without any kernel boot options (just the suspend2 option) and with a PS/2 mouse plugged in. On suspend, the keyboard worked. Maybe this could/should be added to the suspend2 code as well? Whatever. It works for now. If you'd like any more information, just let me know. Thanks! -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PS/2 Keyboard is dead after resume.
On 7/15/05, Dmitry Torokhov <[EMAIL PROTECTED]> wrote: > Could you try doing: > > echo 1 > /sys/modules/i8042/parameters/debug > > before suspending and the post your dmesg, please? Maybe we see something > there. Here you go: 12) *0, disabled. ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *15, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs *21) ACPI: PCI Interrupt Link [ALKC] (IRQs *22) ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled. SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Machine check exception polling timer started. audit: initializing netlink socket (disabled) audit(1121412889.356:0): initialized Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). Initializing Cryptographic API ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Sleep Button (CM) [SLPB] ACPI: Fan [FAN] (on) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Thermal Zone [THRM] (29 C) lp: driver loaded but no devices found serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A parport0: PC-style at 0x378 [PCSPP(,...)] lp0: using parport0 (polling). io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 8139too Fast Ethernet driver 0.9.27 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:0b.0[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10 eth0: RealTek RTL8139 at 0xc400, 00:30:1b:3d:91:ee, IRQ 10 eth0: Identified 8139 chip type 'RTL-8100B/8139D' Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt :00:0a.0[A] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11 eth1: Lite-On PNIC-II rev 37 at 0001c000, 00:C0:F0:70:43:C6, IRQ 11. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller at PCI slot :00:0f.0 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 12 PCI: setting IRQ 12 as level-triggered ACPI: PCI Interrupt :00:0f.0[A] -> Link [LNKA] -> GSI 12 (level, low) -> IRQ 12 PCI: Via IRQ fixup for :00:0f.0, from 255 to 12 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci:00:0f.0 ide0: BM-DMA at 0xcc00-0xcc07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: IBM-DTLA-307015, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: WDC WD102BA, ATA DISK drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 128KiB hda: 29336832 sectors (15020 MB) w/1916KiB Cache, CHS=29104/16/63, UDMA(100) hda: cache flushes not supported hda: hda1 hda2 hdc: max request size: 128KiB hdc: 20028960 sectors (10254 MB) w/2048KiB Cache, CHS=19870/16/63, UDMA(66) hdc: cache flushes not supported hdc: hdc1 ACPI: PCI Interrupt :00:10.4[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10 ehci_hcd :00:10.4: VIA Technologies, Inc. USB 2.0 ehci_hcd :00:10.4: new USB bus registered, assigned bus number 1 ehci_hcd :00:10.4: irq 10, io mem 0xee043000 ehci_hcd :00:10.4: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0: USB hub found hub 1-0:1.0: 8 ports detected USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt :00:10.0[A] -> Link [LNKA] -> GSI 12 (level, low) -> IRQ 12 uhci_hcd :00:10.0: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller uhci_hcd :00:10.0: new USB bus registered, assigned bus number 2 uhci_hcd :00:10.0: irq 12, io base 0xd000 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.1[A] -> Link [LNKA] -> GSI 12 (level, low) -> IRQ 12 uhci_hcd :00:10.1: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#2) uhci_hcd :00:10.1: new USB bus registered, assigned bus number 3 uhci_hcd :00:10.1: irq 12, io base 0xd400 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.2[B] -> Link [LNKB] -> GSI 11 (level, low) -> IRQ 11 uhci_hcd :00:10.2: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#3) uhci_hcd :00:10.2: new USB bus registered, assigned bus number 4 uhci_hcd :00:10.2: irq 11, io base 0xd800 hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports
Re: PS/2 Keyboard is dead after resume.
On 7/15/05, Dmitry Torokhov [EMAIL PROTECTED] wrote: Could you try doing: echo 1 /sys/modules/i8042/parameters/debug before suspending and the post your dmesg, please? Maybe we see something there. Here you go: 12) *0, disabled. ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *15, disabled. ACPI: PCI Interrupt Link [ALKB] (IRQs *21) ACPI: PCI Interrupt Link [ALKC] (IRQs *22) ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled. SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try pci=routeirq. If it helps, post a report Machine check exception polling timer started. audit: initializing netlink socket (disabled) audit(1121412889.356:0): initialized Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). Initializing Cryptographic API ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Sleep Button (CM) [SLPB] ACPI: Fan [FAN] (on) ACPI: CPU0 (power states: C1[C1] C2[C2]) ACPI: Thermal Zone [THRM] (29 C) lp: driver loaded but no devices found serio: i8042 AUX port at 0x60,0x64 irq 12 serio: i8042 KBD port at 0x60,0x64 irq 1 Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A parport0: PC-style at 0x378 [PCSPP(,...)] lp0: using parport0 (polling). io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 8139too Fast Ethernet driver 0.9.27 ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:0b.0[A] - Link [LNKC] - GSI 10 (level, low) - IRQ 10 eth0: RealTek RTL8139 at 0xc400, 00:30:1b:3d:91:ee, IRQ 10 eth0: Identified 8139 chip type 'RTL-8100B/8139D' Linux Tulip driver version 1.1.13 (May 11, 2002) ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11 PCI: setting IRQ 11 as level-triggered ACPI: PCI Interrupt :00:0a.0[A] - Link [LNKB] - GSI 11 (level, low) - IRQ 11 eth1: Lite-On PNIC-II rev 37 at 0001c000, 00:C0:F0:70:43:C6, IRQ 11. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller at PCI slot :00:0f.0 ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 12 PCI: setting IRQ 12 as level-triggered ACPI: PCI Interrupt :00:0f.0[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 PCI: Via IRQ fixup for :00:0f.0, from 255 to 12 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci:00:0f.0 ide0: BM-DMA at 0xcc00-0xcc07, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xcc08-0xcc0f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: IBM-DTLA-307015, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: WDC WD102BA, ATA DISK drive ide1 at 0x170-0x177,0x376 on irq 15 Probing IDE interface ide2... Probing IDE interface ide3... Probing IDE interface ide4... Probing IDE interface ide5... hda: max request size: 128KiB hda: 29336832 sectors (15020 MB) w/1916KiB Cache, CHS=29104/16/63, UDMA(100) hda: cache flushes not supported hda: hda1 hda2 hdc: max request size: 128KiB hdc: 20028960 sectors (10254 MB) w/2048KiB Cache, CHS=19870/16/63, UDMA(66) hdc: cache flushes not supported hdc: hdc1 ACPI: PCI Interrupt :00:10.4[C] - Link [LNKC] - GSI 10 (level, low) - IRQ 10 ehci_hcd :00:10.4: VIA Technologies, Inc. USB 2.0 ehci_hcd :00:10.4: new USB bus registered, assigned bus number 1 ehci_hcd :00:10.4: irq 10, io mem 0xee043000 ehci_hcd :00:10.4: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0: USB hub found hub 1-0:1.0: 8 ports detected USB Universal Host Controller Interface driver v2.2 ACPI: PCI Interrupt :00:10.0[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 uhci_hcd :00:10.0: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller uhci_hcd :00:10.0: new USB bus registered, assigned bus number 2 uhci_hcd :00:10.0: irq 12, io base 0xd000 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.1[A] - Link [LNKA] - GSI 12 (level, low) - IRQ 12 uhci_hcd :00:10.1: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#2) uhci_hcd :00:10.1: new USB bus registered, assigned bus number 3 uhci_hcd :00:10.1: irq 12, io base 0xd400 hub 3-0:1.0: USB hub found hub 3-0:1.0: 2 ports detected ACPI: PCI Interrupt :00:10.2[B] - Link [LNKB] - GSI 11 (level, low) - IRQ 11 uhci_hcd :00:10.2: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (#3) uhci_hcd :00:10.2: new USB bus registered, assigned bus number 4 uhci_hcd :00:10.2: irq 11, io base 0xd800 hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports detected ACPI: PCI Interrupt
PS/2 Keyboard is dead after resume.
Hello. I'm using Linux Kernel 2.6.12.2 plus suspend 2.1.9.9 and acpi-20050408 with the hibernate-1.10 script. My machine is a Shuttle SK43G which has a VIA KM400 chipset with an Athlon XP CPU. Suspension seems to work well. However, when I resume, the keyboard is dead and there is a warning in dmesg before and after suspension: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. Please include the following information in bug reports: - SUSPEND core : 2.1.9.9 - Kernel Version : 2.6.12.2 - Compiler vers. : 3.3 - Attempt number : 1 - Pageset sizes : 5821 (5821 low) and 118350 (118350 low). - Parameters : 0 32 0 1 0 5 - Calculations : Image size: 124376. Ram to suspend: 2240. - Limits : 126960 pages RAM. Initial boot: 123894. - Overall expected compression percentage: 0. - Compressor lzf enabled. Compressed 508604416 bytes into 23739845 (95 percent compression). - Swapwriter active. Swap available for image: 487964 pages. - Filewriter inactive. - Preemptive kernel. - Max extents used: 4 - I/O speed: Write 251 MB/s, Read 198 MB/s. Resume block device is defe0860. Real Time Clock Driver v1.12 atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. This machine doesn't have XFree86 on it. I am presuming that this is a bug since I've used the exact same kernel+patches (with hibernate 1.09 script) on another machine without issues. I'm not sure if it's a suspension bug or if it's a kernel bug that is brought to light by the suspend2 patches. If I'm wrong and I've made a mistake, I'd love to hear it. Thanks. -Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
PS/2 Keyboard is dead after resume.
Hello. I'm using Linux Kernel 2.6.12.2 plus suspend 2.1.9.9 and acpi-20050408 with the hibernate-1.10 script. My machine is a Shuttle SK43G which has a VIA KM400 chipset with an Athlon XP CPU. Suspension seems to work well. However, when I resume, the keyboard is dead and there is a warning in dmesg before and after suspension: atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. Please include the following information in bug reports: - SUSPEND core : 2.1.9.9 - Kernel Version : 2.6.12.2 - Compiler vers. : 3.3 - Attempt number : 1 - Pageset sizes : 5821 (5821 low) and 118350 (118350 low). - Parameters : 0 32 0 1 0 5 - Calculations : Image size: 124376. Ram to suspend: 2240. - Limits : 126960 pages RAM. Initial boot: 123894. - Overall expected compression percentage: 0. - Compressor lzf enabled. Compressed 508604416 bytes into 23739845 (95 percent compression). - Swapwriter active. Swap available for image: 487964 pages. - Filewriter inactive. - Preemptive kernel. - Max extents used: 4 - I/O speed: Write 251 MB/s, Read 198 MB/s. Resume block device is defe0860. Real Time Clock Driver v1.12 atkbd.c: Spurious ACK on isa0060/serio0. Some program, like XFree86, might be trying access hardware directly. This machine doesn't have XFree86 on it. I am presuming that this is a bug since I've used the exact same kernel+patches (with hibernate 1.09 script) on another machine without issues. I'm not sure if it's a suspension bug or if it's a kernel bug that is brought to light by the suspend2 patches. If I'm wrong and I've made a mistake, I'd love to hear it. Thanks. -Andy - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
