* Asus MB and 2.6.12 Problems
@ 2005-06-24 15:34 Frank Peters
2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky
` (2 more replies)
0 siblings, 3 replies; 29+ messages in thread
From: Frank Peters @ 2005-06-24 15:34 UTC (permalink / raw)
To: linux-kernel
Hello,
For the very first time in the long history of the Linux kernel,
I am having significant problems.
After downloading and compiling the latest version 2.6.12, my
keyboard becomes unresponsive and dead following the boot process.
This doesn't occur all of the time, but only some of the time.
In particular, the follwing boot up message will be seen at
sporadic places among the other text output:
input: AT Translated Set 2 keyboard on isa0060/serio0
When this message does not occur anywhere in the boot messages,
the keyboard is not functional. When the message does occur, then
the keyboard will respond, but sometimes with an erratic key
repeat rate. After rebooting several times I can usually get
the system up and running smoothly, but with this current kernel
2.6.12, there is no guarantee that it will boot properly at any
given time.
Also, after a successful boot with 2.6.12, I will attempt to
connect with my cable Internet service using the following
commands:
modprobe 3c59x (load the ethernet modules)
dhcpcd -t 240 (get the IP address from my ISP)
Formerly, with kernels 2.6.11 and earlier, the connection could
be established very quickly (about 10-15 seconds). But with
kernel 2.6.12, it now requires about 3-4 minutes to establish
the link.
My system is an ASUS P4B533 motherboard with a Pentium 3.6 Ghz
Hyperthreaded processor and 1 GHz RAM. The kernel is the stock
linux kernel (compiled with gcc-2.95.3) and the rest of my software
is self-compiled (i.e. no distribution).
If I disable ACPI, either by compiling a new 2.6.12 kernel or
through boot up parameters, the keyboard will respond normally
without any problems, but the kernel will not recognize my
hyperthreaded processor. Only one CPU will be initialized and
active.
Thus, I can enjoy a problem-free 2.6.12 kernel if I choose to
sacrifice ACPI and hyperthreading.
However in either case the cable Internet connection with DHCP
still takes 3-4 minutes, which is markedly different from previous
behavior.
If anyone has any suggestions or needs any more information,
please CC me at the address frank.peters@comcast.net as I am not
a subscriber to the list.
Frank Peters
^ permalink raw reply [flat|nested] 29+ messages in thread* isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-06-24 15:34 Asus MB and 2.6.12 Problems Frank Peters @ 2005-06-24 16:10 ` Michael Krufky 2005-06-24 16:59 ` Frank Peters 2005-06-27 11:39 ` Michael Krufky [not found] ` <1119633158.3180.5.camel@home-lap> 2005-06-26 19:47 ` Alexey Dobriyan 2 siblings, 2 replies; 29+ messages in thread From: Michael Krufky @ 2005-06-24 16:10 UTC (permalink / raw) To: vojtech; +Cc: Frank Peters, linux-kernel Frank Peters <frank.peters@comcast.net> wrote: >After downloading and compiling the latest version 2.6.12, my >keyboard becomes unresponsive and dead following the boot process. >This doesn't occur all of the time, but only some of the time. >In particular, the follwing boot up message will be seen at >sporadic places among the other text output: > >input: AT Translated Set 2 keyboard on isa0060/serio0 > >When this message does not occur anywhere in the boot messages, >the keyboard is not functional. When the message does occur, then >the keyboard will respond, but sometimes with an erratic key >repeat rate. After rebooting several times I can usually get >the system up and running smoothly, but with this current kernel >2.6.12, there is no guarantee that it will boot properly at any >given time. > > ... >My system is an ASUS P4B533 motherboard with a Pentium 3.6 Ghz >Hyperthreaded processor and 1 GHz RAM. The kernel is the stock >linux kernel (compiled with gcc-2.95.3) and the rest of my software >is self-compiled (i.e. no distribution). > >If I disable ACPI, either by compiling a new 2.6.12 kernel or >through boot up parameters, the keyboard will respond normally >without any problems, but the kernel will not recognize my >hyperthreaded processor. Only one CPU will be initialized and >active. > >Thus, I can enjoy a problem-free 2.6.12 kernel if I choose to >sacrifice ACPI and hyperthreading. > > ... >If anyone has any suggestions or needs any more information, >please CC me at the address frank.peters@comcast.net as I am not >a subscriber to the list. > > I am having the same problem with my Shuttle FT61 motherboard, although I have not tried to disable ACPI... Until now I thought I just had a faulty keyboard, as my method to fix this was to unplug the keyboard and plug it back in after bootup. When this happens, I see this in dmesg as the last line: input: AT Translated Set 2 keyboard on isa0060/serio0 I am also having problems with my AUX mouse, as seen in message Subject: 2.6.12-rc5-mm1 breaks serio: i8042 AUX port Frank, are you having problems with your ps/2 mouse port as well? I haven't spent enough time experimenting with this, as I thought it might have had something to to with my hardware / KVM switch. Seeing Frank's message is the reason why I've decided to chime back in on this. As a clarification, I have been having these keyboard problems intermittently, regardless of whether I'm using -mm or mainline kernel. I was NOT having this problem in 2.6.11 I wasn't having the psaux mouse problems in 2.6.11 either .... I unplugged my psaux mouse from that machine before 2.6.12-mainline was released, so I don't know if those symptoms are still present. (using USB mouse now instead). I am currently in my office, so I can't test this right now, and I will be away for this weekend. I'll be able to make these tests again come Sunday night/Monday. ...and I will try it this time WITHOUT the kvm switch. -- Michael Krufky ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky @ 2005-06-24 16:59 ` Frank Peters 2005-06-24 17:12 ` Michael Krufky 2005-06-27 11:39 ` Michael Krufky 1 sibling, 1 reply; 29+ messages in thread From: Frank Peters @ 2005-06-24 16:59 UTC (permalink / raw) To: linux-kernel; +Cc: mkrufky On Fri, 24 Jun 2005 12:10:18 -0400 Michael Krufky <mkrufky@m1k.net> wrote: > I am having the same problem with my Shuttle FT61 motherboard, although > I have not tried to disable ACPI... Until now I thought I just had a > faulty keyboard, as my method to fix this was to unplug the keyboard and > plug it back in after bootup. When this happens, I see this in dmesg as > the last line: > > input: AT Translated Set 2 keyboard on isa0060/serio0 > > I am also having problems with my AUX mouse, as seen in message > > Subject: 2.6.12-rc5-mm1 breaks serio: i8042 AUX port > > Frank, are you having problems with your ps/2 mouse port as well? > I am so glad that you asked this. I have not been able to get my ps/2 mouse to function with any 2.6.x or 2.4.x kernel (same ASUS MB). The problem is already so long standing that I have completely given up on it and use a serial mouse exclusively and no longer bother with ps/2. (I also hate to report that since I dual boot with MS Windows, the ps/2 mouse functions properly under the same conditions with MS Windows 2K. The hardware cannot be at fault.) > As a clarification, I have been having these keyboard problems > intermittently, regardless of whether I'm using -mm or mainline kernel. > I was NOT having this problem in 2.6.11 I wasn't having the psaux mouse > problems in 2.6.11 either .... I unplugged my psaux mouse from that > machine before 2.6.12-mainline was released, so I don't know if those > symptoms are still present. Actually, my keyboard problems began with kernel-2.6.11, but were quickly resolved when I used the following parameter in my lilo.conf file: i8042.nomux When I use this parameter, or any other i8042 specific parameter, with kernel-2.6.12, there is no effect. The keyboard still occasionally comes up dead. Thanks for the information on unplugging and re-plugging the keyboard. I'll give that a try soon. Frank Peters (Please CC to frank.peters@comcast.net as I am not a subscriber to this list.) ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-06-24 16:59 ` Frank Peters @ 2005-06-24 17:12 ` Michael Krufky [not found] ` <20050728222838.64517cc9.akpm@osdl.org> 2005-08-04 20:19 ` Andrew Morton 0 siblings, 2 replies; 29+ messages in thread From: Michael Krufky @ 2005-06-24 17:12 UTC (permalink / raw) To: Frank Peters; +Cc: linux-kernel, vojtech I am cc'ing your message to Vojtech Pavlik, the INPUT DRIVERS kernel maintainer. Vojtech, I figured these should be sent to you. If I am wrong, please redirect them to the correct person / list and let us know. Thank you. Frank Peters wrote: >On Fri, 24 Jun 2005 12:10:18 -0400 >Michael Krufky <mkrufky@m1k.net> wrote: > > > >>I am having the same problem with my Shuttle FT61 motherboard, although >>I have not tried to disable ACPI... Until now I thought I just had a >>faulty keyboard, as my method to fix this was to unplug the keyboard and >>plug it back in after bootup. When this happens, I see this in dmesg as >>the last line: >> >>input: AT Translated Set 2 keyboard on isa0060/serio0 >> >>I am also having problems with my AUX mouse, as seen in message >> >>Subject: 2.6.12-rc5-mm1 breaks serio: i8042 AUX port >> >>Frank, are you having problems with your ps/2 mouse port as well? >> >> >> > >I am so glad that you asked this. > >I have not been able to get my ps/2 mouse to function with any >2.6.x or 2.4.x kernel (same ASUS MB). The problem is already >so long standing that I have completely given up on it and use >a serial mouse exclusively and no longer bother with ps/2. > >(I also hate to report that since I dual boot with MS Windows, >the ps/2 mouse functions properly under the same conditions >with MS Windows 2K. The hardware cannot be at fault.) > > > >>As a clarification, I have been having these keyboard problems >>intermittently, regardless of whether I'm using -mm or mainline kernel. >>I was NOT having this problem in 2.6.11 I wasn't having the psaux mouse >>problems in 2.6.11 either .... I unplugged my psaux mouse from that >>machine before 2.6.12-mainline was released, so I don't know if those >>symptoms are still present. >> >> > >Actually, my keyboard problems began with kernel-2.6.11, but were >quickly resolved when I used the following parameter in my lilo.conf >file: > >i8042.nomux > >When I use this parameter, or any other i8042 specific parameter, >with kernel-2.6.12, there is no effect. The keyboard still occasionally >comes up dead. > >Thanks for the information on unplugging and re-plugging the keyboard. >I'll give that a try soon. > >Frank Peters > >(Please CC to frank.peters@comcast.net as I am not a subscriber to this >list.) >- >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in >the body of a message to majordomo@vger.kernel.org >More majordomo info at http://vger.kernel.org/majordomo-info.html >Please read the FAQ at http://www.tux.org/lkml/ > > -- Michael Krufky ^ permalink raw reply [flat|nested] 29+ messages in thread
[parent not found: <20050728222838.64517cc9.akpm@osdl.org>]
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems [not found] ` <20050728222838.64517cc9.akpm@osdl.org> @ 2005-07-29 5:44 ` Michael Krufky 2005-07-29 5:54 ` Andrew Morton 2005-07-29 18:33 ` Frank Peters 1 sibling, 1 reply; 29+ messages in thread From: Michael Krufky @ 2005-07-29 5:44 UTC (permalink / raw) To: Andrew Morton; +Cc: frank.peters, vojtech, LKML Andrew Morton wrote: >Michael Krufky <mkrufky@m1k.net> wrote: > > >>I am cc'ing your message to Vojtech Pavlik, the INPUT DRIVERS kernel >>maintainer. >> >>Vojtech, I figured these should be sent to you. If I am wrong, please >>redirect them to the correct person / list and let us know. >> >>Thank you. >> >>Frank Peters wrote: >> >> >> >>>On Fri, 24 Jun 2005 12:10:18 -0400 >>>Michael Krufky <mkrufky@m1k.net> wrote: >>> >>> >>> >>> >>> >>>>I am having the same problem with my Shuttle FT61 motherboard, although >>>>I have not tried to disable ACPI... Until now I thought I just had a >>>>faulty keyboard, as my method to fix this was to unplug the keyboard and >>>>plug it back in after bootup. When this happens, I see this in dmesg as >>>>the last line: >>>> >>>>input: AT Translated Set 2 keyboard on isa0060/serio0 >>>> >>>>I am also having problems with my AUX mouse, as seen in message >>>> >>>>Subject: 2.6.12-rc5-mm1 breaks serio: i8042 AUX port >>>> >>>>Frank, are you having problems with your ps/2 mouse port as well? >>>> >>>> >>>> >>>> >>>> >>>I am so glad that you asked this. >>> >>>I have not been able to get my ps/2 mouse to function with any >>>2.6.x or 2.4.x kernel (same ASUS MB). The problem is already >>>so long standing that I have completely given up on it and use >>>a serial mouse exclusively and no longer bother with ps/2. >>> >>>(I also hate to report that since I dual boot with MS Windows, >>>the ps/2 mouse functions properly under the same conditions >>>with MS Windows 2K. The hardware cannot be at fault.) >>> >>> >>> >>> >>> >>>>As a clarification, I have been having these keyboard problems >>>>intermittently, regardless of whether I'm using -mm or mainline kernel. >>>>I was NOT having this problem in 2.6.11 I wasn't having the psaux mouse >>>>problems in 2.6.11 either .... I unplugged my psaux mouse from that >>>>machine before 2.6.12-mainline was released, so I don't know if those >>>>symptoms are still present. >>>> >>>> >>>> >>>> >>>Actually, my keyboard problems began with kernel-2.6.11, but were >>>quickly resolved when I used the following parameter in my lilo.conf >>>file: >>> >>>i8042.nomux >>> >>>When I use this parameter, or any other i8042 specific parameter, >>>with kernel-2.6.12, there is no effect. The keyboard still occasionally >>>comes up dead. >>> >>>Thanks for the information on unplugging and re-plugging the keyboard. >>>I'll give that a try soon. >>> >>> >>> > >Guys, are these problems fixed in 2.6.13-rc4? > >If not, please cc linux-kernel on the reply, thanks. > > Sadly, I must report that yes, the problem still intermittently occurs in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61 Motherboard. Never has a problem in windows and never in 2.6.11 and earlier. I first noticed this problem sometime during 2.6.12-rc series. -- Michael Krufky ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-29 5:44 ` Michael Krufky @ 2005-07-29 5:54 ` Andrew Morton 2005-07-30 2:44 ` Zwane Mwaikambo 2005-07-30 3:48 ` Michael Krufky 0 siblings, 2 replies; 29+ messages in thread From: Andrew Morton @ 2005-07-29 5:54 UTC (permalink / raw) To: mkrufky; +Cc: frank.peters, vojtech, linux-kernel Michael Krufky <mkrufky@m1k.net> wrote: > > Sadly, I must report that yes, the problem still intermittently occurs > in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61 > Motherboard. Never has a problem in windows and never in 2.6.11 and > earlier. > > I first noticed this problem sometime during 2.6.12-rc series. Sigh. I think it would help if you could generate a new report, please. We need a super-easy way for people to do bisection searching. ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-29 5:54 ` Andrew Morton @ 2005-07-30 2:44 ` Zwane Mwaikambo 2005-07-30 3:48 ` Michael Krufky 1 sibling, 0 replies; 29+ messages in thread From: Zwane Mwaikambo @ 2005-07-30 2:44 UTC (permalink / raw) To: Andrew Morton; +Cc: mkrufky, frank.peters, vojtech, linux-kernel On Thu, 28 Jul 2005, Andrew Morton wrote: > Michael Krufky <mkrufky@m1k.net> wrote: > > > > Sadly, I must report that yes, the problem still intermittently occurs > > in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61 > > Motherboard. Never has a problem in windows and never in 2.6.11 and > > earlier. > > > > I first noticed this problem sometime during 2.6.12-rc series. > > Sigh. I think it would help if you could generate a new report, please. > > We need a super-easy way for people to do bisection searching. ketchup is extremely handy for narrowing it down to a release, you then pray that the bug is in the -mm tree first so that it's easier to check all the patches individually ;) ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-29 5:54 ` Andrew Morton 2005-07-30 2:44 ` Zwane Mwaikambo @ 2005-07-30 3:48 ` Michael Krufky 2005-07-30 3:52 ` Michael Krufky 2005-07-30 4:37 ` Andrew Morton 1 sibling, 2 replies; 29+ messages in thread From: Michael Krufky @ 2005-07-30 3:48 UTC (permalink / raw) To: Andrew Morton; +Cc: frank.peters, vojtech, linux-kernel Andrew Morton wrote: >Michael Krufky <mkrufky@m1k.net> wrote: > > >> Sadly, I must report that yes, the problem still intermittently occurs >> in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61 >> Motherboard. Never has a problem in windows and never in 2.6.11 and >> earlier. >> >> I first noticed this problem sometime during 2.6.12-rc series. >> >> > >Sigh. I think it would help if you could generate a new report, please. > >We need a super-easy way for people to do bisection searching. > > I dug up the original email that I sent to LKML... Michael Krufky wrote (5/26/2005 10:16 PM): > In 2.6.12-rc5-mm1, I can't use my psaux mouse, but it worked perfectly > fine in both 2.6.12-rc5 and in 2.6.12-rc4-mm2. > > In 2.6.12-rc5-mm1 , dmesg says: > > PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > Failed to disable AUX port, but continuing anyway... Is this a SiS? > If AUX port is really absent please use the 'i8042.noaux' option. > serio: i8042 KBD port at 0x60,0x64 irq 1 > > This is what dmesg says in both 2.6.12-rc4-mm2 and 2.6.12-rc5 : > > PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > serio: i8042 AUX port at 0x60,0x64 irq 12 > serio: i8042 KBD port at 0x60,0x64 irq 1 > > I am using a Shuttle FT61 motherboard. Is there any more information > necessary to debug this? > -- Michael Krufky ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-30 3:48 ` Michael Krufky @ 2005-07-30 3:52 ` Michael Krufky 2005-07-30 4:18 ` Michael Krufky 2005-07-30 4:37 ` Andrew Morton 1 sibling, 1 reply; 29+ messages in thread From: Michael Krufky @ 2005-07-30 3:52 UTC (permalink / raw) To: Andrew Morton; +Cc: frank.peters, vojtech, linux-kernel Oops... I'm sorry, that was the OLD dmesg... I am still having the same symptoms, but the log shows up different error message in newer kernels... I'll have to reproduce that and send it an another email. ... soon to follow ... Michael Krufky wrote: > I dug up the original email that I sent to LKML... > > Michael Krufky wrote (5/26/2005 10:16 PM): > >> In 2.6.12-rc5-mm1, I can't use my psaux mouse, but it worked >> perfectly fine in both 2.6.12-rc5 and in 2.6.12-rc4-mm2. >> >> In 2.6.12-rc5-mm1 , dmesg says: >> >> PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 >> Failed to disable AUX port, but continuing anyway... Is this a SiS? >> If AUX port is really absent please use the 'i8042.noaux' option. >> serio: i8042 KBD port at 0x60,0x64 irq 1 >> >> This is what dmesg says in both 2.6.12-rc4-mm2 and 2.6.12-rc5 : >> >> PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 >> serio: i8042 AUX port at 0x60,0x64 irq 12 >> serio: i8042 KBD port at 0x60,0x64 irq 1 >> >> I am using a Shuttle FT61 motherboard. Is there any more information >> necessary to debug this? >> > -- Michael Krufky ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-30 3:52 ` Michael Krufky @ 2005-07-30 4:18 ` Michael Krufky 0 siblings, 0 replies; 29+ messages in thread From: Michael Krufky @ 2005-07-30 4:18 UTC (permalink / raw) To: Andrew Morton; +Cc: mkrufky, frank.peters, vojtech, linux-kernel [-- Attachment #1: Type: text/plain, Size: 1212 bytes --] Michael Krufky wrote: > Oops... I'm sorry, that was the OLD dmesg... I am still having the > same symptoms, but the log shows up different error message in newer > kernels... I'll have to reproduce that and send it an another email. > ... soon to follow ... In newer kernels (including 2.6.13-rc4), my ps/2 mouse USUALLY doesn't work... It is an intermittent problem. The problem does not exist on 2.6.11 kernels, nor does it exist in windows. In newer kernels, 4 / 5 times, it will not work. I can no longer find an error in dmesg for this, so I have attached my entire dmesg log, along with my .config. I know that this is a lot to post to the list, but I have found absolutely no indication of an error in this log, maybe someone will see something I've missed. I am using a Shuttle FT61 motherboard. If you want to know more about what hardware is on that board, I can probably get that for you. I think this problem started around 2.6.12-rc5 or earlier, but I don't know for sure. Before that I was using 2.6.11 gentoo kernels and never had a problem. I've also tried 2.6.13-linus kernels on the same machine under debian and experienced the same problem. -- Michael Krufky [-- Attachment #2: dmesg.2.6.13-rc4 --] [-- Type: text/plain, Size: 16035 bytes --] Linux version 2.6.13-rc4 (root@aftermath) (gcc version 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)) #1 SMP Thu Jul 28 22:57:20 UTC 2005 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f400 (usable) BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003def0000 (usable) BIOS-e820: 000000003def0000 - 000000003def3000 (ACPI NVS) BIOS-e820: 000000003def3000 - 000000003df00000 (ACPI data) BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) Warning only 896MB will be used. Use a HIGHMEM enabled kernel. 896MB LOWMEM available. found SMP MP-table at 000f4ef0 On node 0 totalpages: 229376 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.2 present. ACPI: RSDP (v000 XPC ) @ 0x000f69b0 ACPI: RSDT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3def3000 ACPI: FADT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3def3040 ACPI: MADT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3def6240 ACPI: DSDT (v001 XPC ST61 0x00001000 MSFT 0x0100000e) @ 0x00000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:2 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 15:2 APIC version 20 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 21 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3df00000 (gap: 3df00000:c0d00000) Built 1 zonelists Kernel command line: root=/dev/ram0 real_root=/dev/sda3 init=/linuxrc ramdisk_size=8192 udev mapped APIC to ffffd000 (fee00000) mapped IOAPIC to ffffc000 (fec00000) Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 3060.002 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 903216k/917504k available (3130k kernel code, 13632k reserved, 1051k data, 216k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 6125.24 BogoMIPS (lpj=12250486) Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU0: Thermal monitoring enabled mtrr: v2.0 (20020519) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. CPU0: Intel(R) Pentium(R) 4 CPU 3.06GHz stepping 09 Booting processor 1/1 eip 2000 Initializing CPU#1 Calibrating delay using timer specific routine.. 6119.38 BogoMIPS (lpj=12238764) CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#1. CPU1: Intel P4/Xeon Extended MCE MSRs (12) available CPU1: Thermal monitoring enabled CPU1: Intel(R) Pentium(R) 4 CPU 3.06GHz stepping 09 Total of 2 processors activated (12244.62 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 checking TSC synchronization across 2 CPUs: passed. Brought up 2 CPUs checking if image is initramfs... it is Freeing initrd memory: 878k freed NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfb460, last bus=2 PCI: Using configuration type 1 ACPI: Subsystem revision 20050408 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI: Ignoring BAR0-3 of IDE controller 0000:00:14.1 Boot video device is 0000:01:05.0 PCI: Transparent bridge - 0000:00:14.4 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled. ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled. ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled. ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 11 devices SCSI subsystem initialized PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report PCI: Bridge: 0000:00:01.0 IO window: b000-bfff MEM window: ec000000-ec0fffff PREFETCH window: e4000000-e7ffffff PCI: Bridge: 0000:00:14.4 IO window: c000-dfff MEM window: e8000000-ebffffff PREFETCH window: 3df00000-3dffffff pnp: 00:01: ioport range 0x228-0x22f has been reserved pnp: 00:01: ioport range 0x40b-0x40b has been reserved pnp: 00:01: ioport range 0x4d6-0x4d6 has been reserved pnp: 00:01: ioport range 0xc00-0xc01 has been reserved pnp: 00:01: ioport range 0xc14-0xc14 has been reserved pnp: 00:01: ioport range 0xc50-0xc52 has been reserved pnp: 00:01: ioport range 0xc6c-0xc6d has been reserved pnp: 00:01: ioport range 0xc6f-0xc6f has been reserved Machine check exception polling timer started. Installing knfsd (copyright (C) 1996 okir@monad.swb.de). JFS: nTxBlock = 7065, nTxLock = 56522 SGI XFS with large block numbers, no debug enabled Initializing Cryptographic API ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Fan [FAN] (on) ACPI: CPU0 (power states: C1[C1]) ACPI: Processor [CPU0] (supports 8 throttling states) ACPI: CPU1 (power states: C1[C1]) ACPI: Processor [CPU1] (supports 8 throttling states) ACPI: Thermal Zone [THRM] (43 C) Real Time Clock Driver v1.12 Non-volatile memory driver v1.2 PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 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 $ 4 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered floppy0: no floppy controllers found RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize loop: loaded (max 8 devices) b44.c:v0.95 (Aug 3, 2004) ACPI: PCI Interrupt 0000:02:06.0[A] -> GSI 18 (level, low) -> IRQ 16 eth0: Broadcom 4400 10/100BaseT Ethernet 00:30:1b:b2:16:03 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ATIIXP: IDE controller at PCI slot 0000:00:14.1 ACPI: PCI Interrupt 0000:00:14.1[A] -> GSI 16 (level, low) -> IRQ 17 ATIIXP: chipset revision 0 ATIIXP: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: SONY DVD RW DRU-710A, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: SanDisk SDCFB-1024, CFA DISK drive ide1 at 0x170-0x177,0x376 on irq 15 hdc: max request size: 128KiB hdc: 2001888 sectors (1024 MB) w/1KiB Cache, CHS=1986/16/63 hdc: cache flushes not supported hdc: hdc1 hda: ATAPI 48X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.20 libata version 1.11 loaded. sata_sil version 0.9 ACPI: PCI Interrupt 0000:02:05.0[A] -> GSI 17 (level, low) -> IRQ 18 ata1: SATA max UDMA/100 cmd 0xF8802080 ctl 0xF880208A bmdma 0xF8802000 irq 18 ata2: SATA max UDMA/100 cmd 0xF88020C0 ctl 0xF88020CA bmdma 0xF8802008 irq 18 ata1: dev 0 cfg 49:2f00 82:7c6b 83:7f09 84:4063 85:7c69 86:3e01 87:4063 88:207f ata1: dev 0 ATA, max UDMA/133, 398297088 sectors: lba48 ata1: dev 0 configured for UDMA/100 scsi0 : sata_sil ata2: no device found (phy stat 00000000) scsi1 : sata_sil Vendor: ATA Model: Maxtor 6B200M0 Rev: BANC Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB) SCSI device sda: drive cache: write back SCSI device sda: 398297088 512-byte hdwr sectors (203928 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 mice: PS/2 mouse device common for all mice NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 p4-clockmod: P4/Xeon(TM) CPU On-Demand Clock Modulation available Starting balanced_irq Using IPI Shortcut mode Freeing unused kernel memory: 216k freed usbcore: registered new driver usbfs usbcore: registered new driver hub ACPI: PCI Interrupt 0000:00:13.2[A] -> GSI 19 (level, low) -> IRQ 19 ehci_hcd 0000:00:13.2: ATI Technologies Inc EHCI USB Controller ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:13.2: irq 19, io mem 0xec102000 ehci_hcd 0000:00:13.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004 hub 1-0:1.0: USB hub found hub 1-0:1.0: 6 ports detected input: AT Translated Set 2 keyboard on isa0060/serio0 usb 1-5: new high speed USB device using ehci_hcd and address 4 usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.01:USB HID core driver Initializing USB Mass Storage driver... scsi2 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 4 usb-storage: waiting for device to settle before scanning usbcore: registered new driver usb-storage USB Mass Storage support registered. USB Universal Host Controller Interface driver v2.3 ohci_hcd: 2005 April 22 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ACPI: PCI Interrupt 0000:00:13.0[A] -> GSI 19 (level, low) -> IRQ 19 ohci_hcd 0000:00:13.0: ATI Technologies Inc OHCI USB Controller #1 ohci_hcd 0000:00:13.0: new USB bus registered, assigned bus number 2 ohci_hcd 0000:00:13.0: irq 19, io mem 0xec100000 hub 2-0:1.0: USB hub found hub 2-0:1.0: 3 ports detected ACPI: PCI Interrupt 0000:00:13.1[A] -> GSI 19 (level, low) -> IRQ 19 ohci_hcd 0000:00:13.1: ATI Technologies Inc OHCI USB Controller #2 ohci_hcd 0000:00:13.1: new USB bus registered, assigned bus number 3 ohci_hcd 0000:00:13.1: irq 19, io mem 0xec101000 hub 3-0:1.0: USB hub found hub 3-0:1.0: 3 ports detected ohci1394: $Rev: 1299 $ Ben Collins <bcollins@debian.org> ACPI: PCI Interrupt 0000:02:0b.0[A] -> GSI 19 (level, low) -> IRQ 19 ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[19] MMIO=[eb083000-eb0837ff] Max Packet=[2048] sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org> device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com ReiserFS: sda3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on sda3 kjournald starting. Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on sda3, internal journal EXT3-fs: mounted filesystem with ordered data mode. usb 2-1: new low speed USB device using ohci_hcd and address 2 hiddev96: USB HID v1.10 Device [DVICO DVICO USB HID Remocon V1.00] on usb-0000:00:13.0-1 usb 3-1: new low speed USB device using ohci_hcd and address 2 input: USB HID v1.10 Mouse [Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)] on usb-0000:00:13.1-1 ieee1394: Host added: ID:BUS[0-00:1023] GUID[00301bae00001667] Adding 1052216k swap on /dev/sda6. Priority:-1 extents:1 EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on sda3, internal journal Vendor: USB2.0 Model: CardReader CF RW Rev: 0.0> Type: Direct-Access ANSI SCSI revision: 00 Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0 Attached scsi generic sg1 at scsi2, channel 0, id 0, lun 0, type 0 usb-storage: device scan complete kjournald starting. Commit interval 5 seconds EXT3 FS on sda5, internal journal EXT3-fs: mounted filesystem with ordered data mode. Linux agpgart interface v0.101 (c) Dave Jones agpgart: Detected Ati IGP9100/M chipset agpgart: AGP aperture is 64M @ 0xe0000000 ACPI: PCI Interrupt 0000:00:14.5[B] -> GSI 17 (level, low) -> IRQ 18 ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 16 (level, low) -> IRQ 17 radeonfb: Found Intel x86 BIOS ROM Image radeonfb: Retreived PLL infos from BIOS radeonfb: Reference=14.32 MHz (RefDiv=6) Memory=300.00 Mhz, System=200.00 MHz radeonfb: PLL min 20000 max 35000 Linux video capture interface: v1.00 cx2388x v4l2 driver version 0.0.5 loaded cx2388x dvb driver version 0.0.5 loaded parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] radeonfb: Monitor 1 type CRT found radeonfb: Monitor 2 type no found Console: switching to colour frame buffer device 80x30 radeonfb (0000:01:05.0): ATI Radeon X4 ACPI: PCI Interrupt 0000:02:07.0[A] -> GSI 19 (level, low) -> IRQ 19 cx88[0]: subsystem: 18ac:d820, board: DViCO FusionHDTV 3 Gold-T [card=28,autodetected] TV tuner 60 at 0x1fe, Radio tuner -1 at 0x1fe cx88[0]/0: found at 0000:02:07.0, rev: 5, irq: 19, latency: 64, mmio: 0xe8000000 : chip found @ 0xc2 (cx88[0]) tuner 4-0061: type set to 60 (Thomson DDT 7611 (ATSC/NTSC)) cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 ACPI: PCI Interrupt 0000:02:07.2[A] -> GSI 19 (level, low) -> IRQ 19 cx88[0]/2: found at 0000:02:07.2, rev: 5, irq: 19, latency: 64, mmio: 0xea000000 cx88[0]/2: cx2388x based dvb card DVB: registering new adapter (cx88[0]). DVB: registering frontend 0 (DViCO FusionHDTV 3 Gold-T)... b44: eth0: Link is up at 100 Mbps, full duplex. b44: eth0: Flow control is on for TX and on for RX. NETDEV WATCHDOG: eth0: transmit timed out b44: eth0: transmit timed out, resetting b44: eth0: Link is down. b44: eth0: Link is up at 100 Mbps, full duplex. b44: eth0: Flow control is on for TX and on for RX. [drm] Initialized drm 1.0.0 20040925 ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 16 (level, low) -> IRQ 17 [drm] Initialized radeon 1.16.0 20050311 on minor 0: ATI Technologies Inc Radeon 9100 IGP agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0. agpgart: reserved bits set in mode 0x1f00020f. Fixed. agpgart: X tried to set rate=x12. Setting to AGP3 x8 mode. agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode agpgart: Putting AGP V3 device at 0000:01:05.0 into 8x mode [drm] Loading R200 Microcode [-- Attachment #3: kernel-config-x86-2.6.13-rc4 --] [-- Type: text/plain, Size: 36794 bytes --] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.13-rc4 # Thu Jul 28 22:52:20 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y CONFIG_CLEAN_COMPILE=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y # CONFIG_POSIX_MQUEUE is not set # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y # CONFIG_AUDIT is not set CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y # CONFIG_CPUSETS is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_HPET_TIMER=y CONFIG_HPET_EMULATE_RTC=y CONFIG_SMP=y CONFIG_NR_CPUS=2 CONFIG_SCHED_SMT=y CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT is not set CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_TSC=y CONFIG_X86_MCE=y CONFIG_X86_MCE_NONFATAL=y CONFIG_X86_MCE_P4THERMAL=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_X86_REBOOTFIXUPS is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set CONFIG_X86_CPUID=m # # Firmware Drivers # # CONFIG_EDD is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y # CONFIG_DISCONTIGMEM_MANUAL is not set # CONFIG_SPARSEMEM_MANUAL is not set CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_IRQBALANCE=y CONFIG_HAVE_DEC_LOCK=y # CONFIG_REGPARM is not set CONFIG_SECCOMP=y # CONFIG_HZ_100 is not set CONFIG_HZ_250=y # CONFIG_HZ_1000 is not set CONFIG_HZ=250 CONFIG_PHYSICAL_START=0x100000 # CONFIG_KEXEC is not set # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SOFTWARE_SUSPEND is not set # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_AC=y CONFIG_ACPI_BATTERY=y CONFIG_ACPI_BUTTON=y CONFIG_ACPI_VIDEO=m CONFIG_ACPI_HOTKEY=m CONFIG_ACPI_FAN=y CONFIG_ACPI_PROCESSOR=y CONFIG_ACPI_THERMAL=y # CONFIG_ACPI_ASUS is not set CONFIG_ACPI_IBM=m # CONFIG_ACPI_TOSHIBA is not set CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y # CONFIG_X86_PM_TIMER is not set # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support # # CONFIG_APM is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y # CONFIG_CPU_FREQ_STAT_DETAILS is not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=y CONFIG_CPU_FREQ_GOV_USERSPACE=y # CONFIG_CPU_FREQ_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=y # CONFIG_X86_POWERNOW_K6 is not set # CONFIG_X86_POWERNOW_K7 is not set # CONFIG_X86_POWERNOW_K8 is not set # CONFIG_X86_GX_SUSPMOD is not set CONFIG_X86_SPEEDSTEP_CENTRINO=y CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y # CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE is not set # CONFIG_X86_SPEEDSTEP_ICH is not set # CONFIG_X86_SPEEDSTEP_SMI is not set CONFIG_X86_P4_CLOCKMOD=y # CONFIG_X86_CPUFREQ_NFORCE2 is not set # CONFIG_X86_LONGRUN is not set # CONFIG_X86_LONGHAUL is not set # # shared options # # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set CONFIG_X86_SPEEDSTEP_LIB=y # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_MSI is not set CONFIG_PCI_LEGACY_PROC=y CONFIG_PCI_NAMES=y CONFIG_ISA_DMA_API=y # CONFIG_ISA is not set # CONFIG_MCA is not set # CONFIG_SCx200 is not set # CONFIG_HOTPLUG_CPU is not set # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_MISC=y # # Networking # CONFIG_NET=y # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set CONFIG_UNIX=y # CONFIG_NET_KEY is not set CONFIG_INET=y CONFIG_IP_MULTICAST=y # CONFIG_IP_ADVANCED_ROUTER is not set CONFIG_IP_FIB_HASH=y # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set # CONFIG_SYN_COOKIES is not set # CONFIG_INET_AH is not set # CONFIG_INET_ESP is not set # CONFIG_INET_IPCOMP is not set # CONFIG_INET_TUNNEL is not set CONFIG_IP_TCPDIAG=y # CONFIG_IP_TCPDIAG_IPV6 is not set # CONFIG_TCP_CONG_ADVANCED is not set CONFIG_TCP_CONG_BIC=y # CONFIG_IPV6 is not set # CONFIG_NETFILTER is not set # # SCTP Configuration (EXPERIMENTAL) # # CONFIG_IP_SCTP is not set # CONFIG_ATM is not set # CONFIG_BRIDGE is not set # CONFIG_VLAN_8021Q is not set # CONFIG_DECNET is not set # CONFIG_LLC2 is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_X25 is not set # CONFIG_LAPB is not set # CONFIG_NET_DIVERT is not set # CONFIG_ECONET is not set # CONFIG_WAN_ROUTER is not set # CONFIG_NET_SCHED is not set # CONFIG_NET_CLS_ROUTE is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # CONFIG_HAMRADIO is not set # CONFIG_IRDA is not set # CONFIG_BT is not set # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=m # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m CONFIG_PARPORT_SERIAL=m # CONFIG_PARPORT_PC_FIFO is not set CONFIG_PARPORT_PC_SUPERIO=y # CONFIG_PARPORT_GSC is not set CONFIG_PARPORT_1284=y # # Plug and Play support # CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # CONFIG_PNPACPI=y # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_CPQ_CISS_DA is not set # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=y CONFIG_BLK_DEV_CRYPTOLOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_SX8 is not set # CONFIG_BLK_DEV_UB is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=8192 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_LBD=y # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set CONFIG_BLK_DEV_IDESCSI=y CONFIG_IDE_TASK_IOCTL=y # # IDE chipset support/bugfixes # # CONFIG_IDE_GENERIC is not set # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_IDEPNP is not set CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y # CONFIG_BLK_DEV_OFFBOARD is not set # CONFIG_BLK_DEV_GENERIC is not set # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set # CONFIG_IDEDMA_PCI_AUTO is not set # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set CONFIG_BLK_DEV_ATIIXP=y # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5520 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_BLK_DEV_HPT366 is not set # CONFIG_BLK_DEV_SC1200 is not set # CONFIG_BLK_DEV_PIIX is not set # CONFIG_BLK_DEV_IT821X is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_SVWKS is not set CONFIG_BLK_DEV_SIIMAGE=y # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_VIA82CXXX is not set # CONFIG_IDE_ARM is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_IVB is not set # CONFIG_IDEDMA_AUTO is not set # CONFIG_BLK_DEV_HD is not set # # SCSI device support # CONFIG_SCSI=y CONFIG_SCSI_PROC_FS=y # # SCSI support type (disk, tape, CD-ROM) # CONFIG_BLK_DEV_SD=y # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set CONFIG_BLK_DEV_SR=y # CONFIG_BLK_DEV_SR_VENDOR is not set CONFIG_CHR_DEV_SG=y # CONFIG_CHR_DEV_SCH is not set # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # # SCSI Transport Attributes # CONFIG_SCSI_SPI_ATTRS=m # CONFIG_SCSI_FC_ATTRS is not set # CONFIG_SCSI_ISCSI_ATTRS is not set # # SCSI low-level drivers # # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_3W_9XXX is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AACRAID is not set # CONFIG_SCSI_AIC7XXX is not set # CONFIG_SCSI_AIC7XXX_OLD is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set CONFIG_SCSI_SATA=y # CONFIG_SCSI_SATA_AHCI is not set # CONFIG_SCSI_SATA_SVW is not set # CONFIG_SCSI_ATA_PIIX is not set # CONFIG_SCSI_SATA_NV is not set # CONFIG_SCSI_SATA_PROMISE is not set # CONFIG_SCSI_SATA_QSTOR is not set # CONFIG_SCSI_SATA_SX4 is not set CONFIG_SCSI_SATA_SIL=y # CONFIG_SCSI_SATA_SIS is not set # CONFIG_SCSI_SATA_ULI is not set # CONFIG_SCSI_SATA_VIA is not set # CONFIG_SCSI_SATA_VITESSE is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_PPA is not set # CONFIG_SCSI_IMM is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_IPR is not set # CONFIG_SCSI_QLOGIC_FC is not set # CONFIG_SCSI_QLOGIC_1280 is not set CONFIG_SCSI_QLA2XXX=y # CONFIG_SCSI_QLA21XX is not set # CONFIG_SCSI_QLA22XX is not set # CONFIG_SCSI_QLA2300 is not set # CONFIG_SCSI_QLA2322 is not set # CONFIG_SCSI_QLA6312 is not set # CONFIG_SCSI_QLA24XX is not set # CONFIG_SCSI_LPFC is not set # CONFIG_SCSI_DC395x is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_NSP32 is not set # CONFIG_SCSI_DEBUG is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=m CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m # CONFIG_MD_RAID10 is not set CONFIG_MD_RAID5=m # CONFIG_MD_RAID6 is not set CONFIG_MD_MULTIPATH=m # CONFIG_MD_FAULTY is not set CONFIG_BLK_DEV_DM=m # CONFIG_DM_CRYPT is not set # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # CONFIG_FUSION_SPI is not set # CONFIG_FUSION_FC is not set # # IEEE 1394 (FireWire) support # CONFIG_IEEE1394=m # # Subsystem Options # # CONFIG_IEEE1394_VERBOSEDEBUG is not set # CONFIG_IEEE1394_OUI_DB is not set # CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set # CONFIG_IEEE1394_EXPORT_FULL_API is not set # # Device Drivers # # CONFIG_IEEE1394_PCILYNX is not set CONFIG_IEEE1394_OHCI1394=m # # Protocol Drivers # # CONFIG_IEEE1394_VIDEO1394 is not set CONFIG_IEEE1394_SBP2=m # CONFIG_IEEE1394_SBP2_PHYS_DMA is not set # CONFIG_IEEE1394_ETH1394 is not set CONFIG_IEEE1394_DV1394=m CONFIG_IEEE1394_RAWIO=m CONFIG_IEEE1394_CMP=m CONFIG_IEEE1394_AMDTP=m # # I2O device support # CONFIG_I2O=m CONFIG_I2O_EXT_ADAPTEC=y CONFIG_I2O_CONFIG=m CONFIG_I2O_CONFIG_OLD_IOCTL=y # CONFIG_I2O_BUS is not set CONFIG_I2O_BLOCK=m CONFIG_I2O_SCSI=m CONFIG_I2O_PROC=m # # Network device support # CONFIG_NETDEVICES=y CONFIG_DUMMY=m # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_NET_SB1000 is not set # # ARCnet devices # # CONFIG_ARCNET is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=y # CONFIG_HAPPYMEAL is not set # CONFIG_SUNGEM is not set # CONFIG_NET_VENDOR_3COM is not set # # Tulip family network device support # CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_TULIP=m # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set CONFIG_DE4X5=m CONFIG_WINBOND_840=m CONFIG_DM9102=m # CONFIG_HP100 is not set CONFIG_NET_PCI=y # CONFIG_PCNET32 is not set # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set CONFIG_B44=y # CONFIG_FORCEDETH is not set # CONFIG_DGRS is not set # CONFIG_EEPRO100 is not set # CONFIG_E100 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set # CONFIG_NE2K_PCI is not set # CONFIG_8139CP is not set # CONFIG_8139TOO is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set # CONFIG_E1000 is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SKGE is not set # CONFIG_SK98LIN is not set # CONFIG_VIA_VELOCITY is not set # CONFIG_TIGON3 is not set # CONFIG_BNX2 is not set # # Ethernet (10000 Mbit) # # CONFIG_IXGB is not set # CONFIG_S2IO is not set # # Token Ring devices # # CONFIG_TR is not set # # Wireless LAN (non-hamradio) # CONFIG_NET_RADIO=y # # Obsolete Wireless cards support (pre-802.11) # # CONFIG_STRIP is not set # # Wireless 802.11b ISA/PCI cards support # CONFIG_HERMES=m CONFIG_PLX_HERMES=m CONFIG_TMD_HERMES=m CONFIG_PCI_HERMES=m # CONFIG_ATMEL is not set # # Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support # CONFIG_PRISM54=m CONFIG_NET_WIRELESS=y # # Wan interfaces # # CONFIG_WAN is not set # CONFIG_FDDI is not set # CONFIG_HIPPI is not set # CONFIG_PLIP is not set CONFIG_PPP=m # CONFIG_PPP_MULTILINK is not set # CONFIG_PPP_FILTER is not set CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPPOE=m # CONFIG_SLIP is not set # CONFIG_NET_FC is not set # CONFIG_SHAPER is not set # CONFIG_NETCONSOLE is not set # CONFIG_NETPOLL is not set # CONFIG_NET_POLL_CONTROLLER is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_TSDEV is not set # CONFIG_INPUT_EVDEV is not set # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y # CONFIG_KEYBOARD_SUNKBD is not set # CONFIG_KEYBOARD_LKKBD is not set # CONFIG_KEYBOARD_XTKBD is not set # CONFIG_KEYBOARD_NEWTON is not set CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y # CONFIG_MOUSE_SERIAL is not set # CONFIG_MOUSE_VSXXXAA is not set # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y # CONFIG_SERIO_SERPORT is not set # CONFIG_SERIO_CT82C710 is not set # CONFIG_SERIO_PARKBD is not set # CONFIG_SERIO_PCIPS2 is not set CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set # CONFIG_GAMEPORT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y # CONFIG_SERIAL_NONSTANDARD is not set # # Serial drivers # CONFIG_SERIAL_8250=y # CONFIG_SERIAL_8250_CONSOLE is not set # CONFIG_SERIAL_8250_ACPI is not set CONFIG_SERIAL_8250_NR_UARTS=4 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=y # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 CONFIG_PRINTER=m # CONFIG_LP_CONSOLE is not set # CONFIG_PPDEV is not set # CONFIG_TIPAR is not set # # IPMI # # CONFIG_IPMI_HANDLER is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set CONFIG_HW_RANDOM=y CONFIG_NVRAM=y CONFIG_RTC=y # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # CONFIG_SONYPI is not set # # Ftape, the floppy tape device driver # CONFIG_AGP=m # CONFIG_AGP_ALI is not set CONFIG_AGP_ATI=m # CONFIG_AGP_AMD is not set # CONFIG_AGP_AMD64 is not set # CONFIG_AGP_INTEL is not set # CONFIG_AGP_NVIDIA is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_SWORKS is not set # CONFIG_AGP_VIA is not set # CONFIG_AGP_EFFICEON is not set CONFIG_DRM=m # CONFIG_DRM_TDFX is not set # CONFIG_DRM_R128 is not set CONFIG_DRM_RADEON=m # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_DRM_VIA is not set # CONFIG_MWAVE is not set # CONFIG_RAW_DRIVER is not set # CONFIG_HPET is not set # CONFIG_HANGCHECK_TIMER is not set # # TPM devices # # CONFIG_TCG_TPM is not set # # I2C support # CONFIG_I2C=m CONFIG_I2C_CHARDEV=m # # I2C Algorithms # CONFIG_I2C_ALGOBIT=m # CONFIG_I2C_ALGOPCF is not set # CONFIG_I2C_ALGOPCA is not set # # I2C Hardware Bus support # # CONFIG_I2C_ALI1535 is not set # CONFIG_I2C_ALI1563 is not set # CONFIG_I2C_ALI15X3 is not set # CONFIG_I2C_AMD756 is not set # CONFIG_I2C_AMD8111 is not set # CONFIG_I2C_I801 is not set # CONFIG_I2C_I810 is not set # CONFIG_I2C_PIIX4 is not set # CONFIG_I2C_ISA is not set # CONFIG_I2C_NFORCE2 is not set # CONFIG_I2C_PARPORT is not set # CONFIG_I2C_PARPORT_LIGHT is not set # CONFIG_I2C_PROSAVAGE is not set # CONFIG_I2C_SAVAGE4 is not set # CONFIG_SCx200_ACB is not set # CONFIG_I2C_SIS5595 is not set # CONFIG_I2C_SIS630 is not set # CONFIG_I2C_SIS96X is not set # CONFIG_I2C_STUB is not set # CONFIG_I2C_VIA is not set # CONFIG_I2C_VIAPRO is not set # CONFIG_I2C_VOODOO3 is not set # CONFIG_I2C_PCA_ISA is not set # CONFIG_I2C_SENSOR is not set # # Miscellaneous I2C Chip support # # CONFIG_SENSORS_DS1337 is not set # CONFIG_SENSORS_DS1374 is not set # CONFIG_SENSORS_EEPROM is not set # CONFIG_SENSORS_PCF8574 is not set # CONFIG_SENSORS_PCA9539 is not set # CONFIG_SENSORS_PCF8591 is not set # CONFIG_SENSORS_RTC8564 is not set # CONFIG_SENSORS_MAX6875 is not set # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # CONFIG_HWMON=y # CONFIG_SENSORS_ADM1021 is not set # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1031 is not set # CONFIG_SENSORS_ADM9240 is not set # CONFIG_SENSORS_ASB100 is not set # CONFIG_SENSORS_ATXP1 is not set # CONFIG_SENSORS_DS1621 is not set # CONFIG_SENSORS_FSCHER is not set # CONFIG_SENSORS_FSCPOS is not set # CONFIG_SENSORS_GL518SM is not set # CONFIG_SENSORS_GL520SM is not set # CONFIG_SENSORS_IT87 is not set # CONFIG_SENSORS_LM63 is not set # CONFIG_SENSORS_LM75 is not set # CONFIG_SENSORS_LM77 is not set # CONFIG_SENSORS_LM78 is not set # CONFIG_SENSORS_LM80 is not set # CONFIG_SENSORS_LM83 is not set # CONFIG_SENSORS_LM85 is not set # CONFIG_SENSORS_LM87 is not set # CONFIG_SENSORS_LM90 is not set # CONFIG_SENSORS_LM92 is not set # CONFIG_SENSORS_MAX1619 is not set # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_SMSC47M1 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_VIA686A is not set # CONFIG_SENSORS_W83781D is not set # CONFIG_SENSORS_W83L785TS is not set # CONFIG_SENSORS_W83627HF is not set # CONFIG_SENSORS_W83627EHF is not set # CONFIG_HWMON_DEBUG_CHIP is not set # # Misc devices # # CONFIG_IBM_ASM is not set # # Multimedia devices # CONFIG_VIDEO_DEV=m # # Video For Linux # # # Video Adapters # CONFIG_VIDEO_BT848=m # CONFIG_VIDEO_BWQCAM is not set # CONFIG_VIDEO_CQCAM is not set # CONFIG_VIDEO_W9966 is not set # CONFIG_VIDEO_CPIA is not set # CONFIG_VIDEO_SAA5246A is not set # CONFIG_VIDEO_SAA5249 is not set # CONFIG_TUNER_3036 is not set # CONFIG_VIDEO_STRADIS is not set # CONFIG_VIDEO_ZORAN is not set # CONFIG_VIDEO_SAA7134 is not set # CONFIG_VIDEO_MXB is not set # CONFIG_VIDEO_DPC is not set # CONFIG_VIDEO_HEXIUM_ORION is not set # CONFIG_VIDEO_HEXIUM_GEMINI is not set CONFIG_VIDEO_CX88=m CONFIG_VIDEO_CX88_DVB=m # CONFIG_VIDEO_OVCAMCHIP is not set # # Radio Adapters # # CONFIG_RADIO_GEMTEK_PCI is not set # CONFIG_RADIO_MAXIRADIO is not set # CONFIG_RADIO_MAESTRO is not set # # Digital Video Broadcasting Devices # CONFIG_DVB=y CONFIG_DVB_CORE=m # # Supported SAA7146 based PCI Adapters # # CONFIG_DVB_AV7110 is not set # CONFIG_DVB_BUDGET is not set # CONFIG_DVB_BUDGET_CI is not set # CONFIG_DVB_BUDGET_AV is not set # # Supported USB Adapters # # CONFIG_DVB_USB is not set # CONFIG_DVB_TTUSB_BUDGET is not set # CONFIG_DVB_TTUSB_DEC is not set # CONFIG_DVB_CINERGYT2 is not set # # Supported FlexCopII (B2C2) Adapters # # CONFIG_DVB_B2C2_FLEXCOP is not set # # Supported BT878 Adapters # # CONFIG_DVB_BT8XX is not set # # Supported Pluto2 Adapters # # CONFIG_DVB_PLUTO2 is not set # # Supported DVB Frontends # # # Customise DVB Frontends # # # DVB-S (satellite) frontends # # CONFIG_DVB_STV0299 is not set # CONFIG_DVB_CX24110 is not set # CONFIG_DVB_TDA8083 is not set # CONFIG_DVB_TDA80XX is not set # CONFIG_DVB_MT312 is not set # CONFIG_DVB_VES1X93 is not set # CONFIG_DVB_S5H1420 is not set # # DVB-T (terrestrial) frontends # # CONFIG_DVB_SP8870 is not set # CONFIG_DVB_SP887X is not set # CONFIG_DVB_CX22700 is not set CONFIG_DVB_CX22702=m # CONFIG_DVB_L64781 is not set # CONFIG_DVB_TDA1004X is not set # CONFIG_DVB_NXT6000 is not set CONFIG_DVB_MT352=m # CONFIG_DVB_DIB3000MB is not set # CONFIG_DVB_DIB3000MC is not set # # DVB-C (cable) frontends # # CONFIG_DVB_ATMEL_AT76C651 is not set # CONFIG_DVB_VES1820 is not set # CONFIG_DVB_TDA10021 is not set # CONFIG_DVB_STV0297 is not set # # ATSC (North American/Korean Terresterial DTV) frontends # # CONFIG_DVB_NXT2002 is not set # CONFIG_DVB_OR51211 is not set CONFIG_DVB_OR51132=m # CONFIG_DVB_BCM3510 is not set CONFIG_DVB_LGDT330X=m CONFIG_VIDEO_TUNER=m CONFIG_VIDEO_BUF=m CONFIG_VIDEO_BUF_DVB=m CONFIG_VIDEO_BTCX=m CONFIG_VIDEO_IR=m CONFIG_VIDEO_TVEEPROM=m # # Graphics support # CONFIG_FB=y CONFIG_FB_CFB_FILLRECT=y CONFIG_FB_CFB_COPYAREA=y CONFIG_FB_CFB_IMAGEBLIT=y CONFIG_FB_SOFT_CURSOR=y # CONFIG_FB_MACMODES is not set CONFIG_FB_MODE_HELPERS=y # CONFIG_FB_TILEBLITTING is not set # CONFIG_FB_CIRRUS is not set # CONFIG_FB_PM2 is not set # CONFIG_FB_CYBER2000 is not set # CONFIG_FB_ARC is not set # CONFIG_FB_ASILIANT is not set # CONFIG_FB_IMSTT is not set # CONFIG_FB_VGA16 is not set CONFIG_FB_VESA=y CONFIG_VIDEO_SELECT=y # CONFIG_FB_HGA is not set # CONFIG_FB_NVIDIA is not set # CONFIG_FB_RIVA is not set # CONFIG_FB_I810 is not set # CONFIG_FB_INTEL is not set # CONFIG_FB_MATROX is not set # CONFIG_FB_RADEON_OLD is not set CONFIG_FB_RADEON=m CONFIG_FB_RADEON_I2C=y # CONFIG_FB_RADEON_DEBUG is not set # CONFIG_FB_ATY128 is not set # CONFIG_FB_ATY is not set # CONFIG_FB_SAVAGE is not set # CONFIG_FB_SIS is not set # CONFIG_FB_NEOMAGIC is not set # CONFIG_FB_KYRO is not set # CONFIG_FB_3DFX is not set # CONFIG_FB_VOODOO1 is not set # CONFIG_FB_TRIDENT is not set # CONFIG_FB_GEODE is not set # CONFIG_FB_S1D13XXX is not set # CONFIG_FB_VIRTUAL is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y CONFIG_DUMMY_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE=y # CONFIG_FONTS is not set CONFIG_FONT_8x8=y CONFIG_FONT_8x16=y # # Logo configuration # CONFIG_LOGO=y CONFIG_LOGO_LINUX_MONO=y CONFIG_LOGO_LINUX_VGA16=y CONFIG_LOGO_LINUX_CLUT224=y # CONFIG_BACKLIGHT_LCD_SUPPORT is not set # # Sound # CONFIG_SOUND=y # # Advanced Linux Sound Architecture # CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_SEQUENCER=m # CONFIG_SND_SEQ_DUMMY is not set CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_SEQUENCER_OSS=y # CONFIG_SND_RTCTIMER is not set # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set # # Generic devices # # CONFIG_SND_DUMMY is not set # CONFIG_SND_VIRMIDI is not set # CONFIG_SND_MTPAV is not set # CONFIG_SND_SERIAL_U16550 is not set # CONFIG_SND_MPU401 is not set # # PCI devices # CONFIG_SND_AC97_CODEC=m # CONFIG_SND_ALI5451 is not set CONFIG_SND_ATIIXP=m CONFIG_SND_ATIIXP_MODEM=m # CONFIG_SND_AU8810 is not set # CONFIG_SND_AU8820 is not set # CONFIG_SND_AU8830 is not set # CONFIG_SND_AZT3328 is not set CONFIG_SND_BT87X=m # CONFIG_SND_BT87X_OVERCLOCK is not set # CONFIG_SND_CS46XX is not set # CONFIG_SND_CS4281 is not set # CONFIG_SND_EMU10K1 is not set # CONFIG_SND_EMU10K1X is not set # CONFIG_SND_CA0106 is not set # CONFIG_SND_KORG1212 is not set # CONFIG_SND_MIXART is not set # CONFIG_SND_NM256 is not set # CONFIG_SND_RME32 is not set # CONFIG_SND_RME96 is not set # CONFIG_SND_RME9652 is not set # CONFIG_SND_HDSP is not set # CONFIG_SND_HDSPM is not set # CONFIG_SND_TRIDENT is not set # CONFIG_SND_YMFPCI is not set # CONFIG_SND_ALS4000 is not set # CONFIG_SND_CMIPCI is not set # CONFIG_SND_ENS1370 is not set # CONFIG_SND_ENS1371 is not set # CONFIG_SND_ES1938 is not set # CONFIG_SND_ES1968 is not set # CONFIG_SND_MAESTRO3 is not set # CONFIG_SND_FM801 is not set # CONFIG_SND_ICE1712 is not set # CONFIG_SND_ICE1724 is not set # CONFIG_SND_INTEL8X0 is not set # CONFIG_SND_INTEL8X0M is not set # CONFIG_SND_SONICVIBES is not set # CONFIG_SND_VIA82XX is not set # CONFIG_SND_VIA82XX_MODEM is not set # CONFIG_SND_VX222 is not set # CONFIG_SND_HDA_INTEL is not set # # USB devices # # CONFIG_SND_USB_AUDIO is not set # CONFIG_SND_USB_USX2Y is not set # # Open Sound System # # CONFIG_SOUND_PRIME is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB=m # CONFIG_USB_DEBUG is not set # # Miscellaneous USB options # CONFIG_USB_DEVICEFS=y # CONFIG_USB_BANDWIDTH is not set # CONFIG_USB_DYNAMIC_MINORS is not set # CONFIG_USB_SUSPEND is not set # CONFIG_USB_OTG is not set # # USB Host Controller Drivers # CONFIG_USB_EHCI_HCD=m # CONFIG_USB_EHCI_SPLIT_ISO is not set # CONFIG_USB_EHCI_ROOT_HUB_TT is not set # CONFIG_USB_ISP116X_HCD is not set CONFIG_USB_OHCI_HCD=m # CONFIG_USB_OHCI_BIG_ENDIAN is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=m # CONFIG_USB_SL811_HCD is not set # # USB Device Class drivers # # CONFIG_USB_AUDIO is not set # CONFIG_USB_BLUETOOTH_TTY is not set # CONFIG_USB_MIDI is not set # CONFIG_USB_ACM is not set CONFIG_USB_PRINTER=m # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; see USB_STORAGE Help for more information # CONFIG_USB_STORAGE=m # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_DPCM is not set # CONFIG_USB_STORAGE_USBAT is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # # USB Input Devices # CONFIG_USB_HID=m CONFIG_USB_HIDINPUT=y # CONFIG_HID_FF is not set CONFIG_USB_HIDDEV=y # # USB HID Boot Protocol drivers # # CONFIG_USB_KBD is not set # CONFIG_USB_MOUSE is not set # CONFIG_USB_AIPTEK is not set # CONFIG_USB_WACOM is not set # CONFIG_USB_ACECAD is not set # CONFIG_USB_KBTAB is not set # CONFIG_USB_POWERMATE is not set # CONFIG_USB_MTOUCH is not set # CONFIG_USB_ITMTOUCH is not set # CONFIG_USB_EGALAX is not set # CONFIG_USB_XPAD is not set CONFIG_USB_ATI_REMOTE=m # CONFIG_USB_KEYSPAN_REMOTE is not set # # USB Imaging devices # # CONFIG_USB_MDC800 is not set # CONFIG_USB_MICROTEK is not set # # USB Multimedia devices # # CONFIG_USB_DABUSB is not set # CONFIG_USB_VICAM is not set # CONFIG_USB_DSBR is not set # CONFIG_USB_IBMCAM is not set # CONFIG_USB_KONICAWC is not set # CONFIG_USB_OV511 is not set # CONFIG_USB_SE401 is not set # CONFIG_USB_SN9C102 is not set # CONFIG_USB_STV680 is not set # CONFIG_USB_PWC is not set # # USB Network Adapters # # CONFIG_USB_CATC is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set # CONFIG_USB_USBNET is not set # CONFIG_USB_ZD1201 is not set CONFIG_USB_MON=y # # USB port drivers # # CONFIG_USB_USS720 is not set # # USB Serial Converter support # # CONFIG_USB_SERIAL is not set # # USB Miscellaneous drivers # # CONFIG_USB_EMI62 is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_AUERSWALD is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_LEGOTOWER is not set # CONFIG_USB_LCD is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_PHIDGETKIT is not set # CONFIG_USB_PHIDGETSERVO is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_SISUSBVGA is not set # CONFIG_USB_LD is not set # CONFIG_USB_TEST is not set # # USB DSL modem support # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # CONFIG_MMC=m # CONFIG_MMC_DEBUG is not set CONFIG_MMC_BLOCK=m # CONFIG_MMC_WBSD is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # SN Devices # # # File systems # CONFIG_EXT2_FS=y # CONFIG_EXT2_FS_XATTR is not set # CONFIG_EXT2_FS_XIP is not set CONFIG_EXT3_FS=y CONFIG_EXT3_FS_XATTR=y # CONFIG_EXT3_FS_POSIX_ACL is not set # CONFIG_EXT3_FS_SECURITY is not set CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=y # CONFIG_REISERFS_CHECK is not set CONFIG_REISERFS_PROC_INFO=y # CONFIG_REISERFS_FS_XATTR is not set CONFIG_JFS_FS=y # CONFIG_JFS_POSIX_ACL is not set # CONFIG_JFS_SECURITY is not set # CONFIG_JFS_DEBUG is not set # CONFIG_JFS_STATISTICS is not set # CONFIG_FS_POSIX_ACL is not set # # XFS support # CONFIG_XFS_FS=y CONFIG_XFS_EXPORT=y # CONFIG_XFS_RT is not set # CONFIG_XFS_QUOTA is not set # CONFIG_XFS_SECURITY is not set # CONFIG_XFS_POSIX_ACL is not set # CONFIG_MINIX_FS is not set CONFIG_ROMFS_FS=y CONFIG_INOTIFY=y # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y # CONFIG_AUTOFS_FS is not set # CONFIG_AUTOFS4_FS is not set # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_ZISOFS_FS=y CONFIG_UDF_FS=y CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=m CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=m CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=m # CONFIG_NTFS_DEBUG is not set # CONFIG_NTFS_RW is not set # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_TMPFS_XATTR is not set # CONFIG_HUGETLBFS is not set # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set CONFIG_CRAMFS=y # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set CONFIG_UFS_FS=m # CONFIG_UFS_FS_WRITE is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_V3_ACL is not set # CONFIG_NFS_V4 is not set # CONFIG_NFS_DIRECTIO is not set CONFIG_NFSD=y CONFIG_NFSD_V3=y # CONFIG_NFSD_V3_ACL is not set # CONFIG_NFSD_V4 is not set # CONFIG_NFSD_TCP is not set CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y # CONFIG_RPCSEC_GSS_KRB5 is not set # CONFIG_RPCSEC_GSS_SPKM3 is not set CONFIG_SMB_FS=m # CONFIG_SMB_NLS_DEFAULT is not set CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set # CONFIG_CIFS_XATTR is not set # CONFIG_CIFS_EXPERIMENTAL is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=y # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set # CONFIG_NLS_CODEPAGE_850 is not set # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set # CONFIG_NLS_ASCII is not set CONFIG_NLS_ISO8859_1=y # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set # CONFIG_DEBUG_KERNEL is not set CONFIG_LOG_BUF_SHIFT=15 CONFIG_DEBUG_BUGVERBOSE=y CONFIG_EARLY_PRINTK=y CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=m CONFIG_CRYPTO_SHA1=m # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=m CONFIG_CRYPTO_BLOWFISH=m CONFIG_CRYPTO_TWOFISH=m # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set CONFIG_CRYPTO_ARC4=m # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set CONFIG_CRYPTO_DEFLATE=y # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # CONFIG_CRC_CCITT=m CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_SMP=y CONFIG_X86_HT=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y CONFIG_PC=y ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-30 3:48 ` Michael Krufky 2005-07-30 3:52 ` Michael Krufky @ 2005-07-30 4:37 ` Andrew Morton 2005-07-30 5:57 ` Dmitry Torokhov 2005-07-30 6:34 ` Frank Peters 1 sibling, 2 replies; 29+ messages in thread From: Andrew Morton @ 2005-07-30 4:37 UTC (permalink / raw) To: mkrufky; +Cc: frank.peters, vojtech, linux-kernel Michael Krufky <mkrufky@m1k.net> wrote: > > Andrew Morton wrote: > > >Michael Krufky <mkrufky@m1k.net> wrote: > > > > > >> Sadly, I must report that yes, the problem still intermittently occurs > >> in 2.6.13-rc4 :-( I'm the one that tested on the Shuttle FT61 > >> Motherboard. Never has a problem in windows and never in 2.6.11 and > >> earlier. > >> > >> I first noticed this problem sometime during 2.6.12-rc series. > >> > >> > > > >Sigh. I think it would help if you could generate a new report, please. > > > >We need a super-easy way for people to do bisection searching. > > > > > I dug up the original email that I sent to LKML... > > Michael Krufky wrote (5/26/2005 10:16 PM): > > > In 2.6.12-rc5-mm1, I can't use my psaux mouse, but it worked perfectly > > fine in both 2.6.12-rc5 and in 2.6.12-rc4-mm2. > > > > In 2.6.12-rc5-mm1 , dmesg says: > > > > PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > > Failed to disable AUX port, but continuing anyway... Is this a SiS? > > If AUX port is really absent please use the 'i8042.noaux' option. > > serio: i8042 KBD port at 0x60,0x64 irq 1 > > > > This is what dmesg says in both 2.6.12-rc4-mm2 and 2.6.12-rc5 : > > > > PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 > > serio: i8042 AUX port at 0x60,0x64 irq 12 > > serio: i8042 KBD port at 0x60,0x64 irq 1 > > > > I am using a Shuttle FT61 motherboard. Is there any more information > > necessary to debug this? > > The diff between 2.6.12-rc4-mm2 and 2.6.12-rc5-mm1 is enormous, but there aren't any significant input driver changes there: http://www.zip.com.au/~akpm/linux/patches/stuff/diffstat-2.6.12-rc4-mm2-2.6.12-rc5-mm1 Similarly, the 2.6.12-rc5-mm1 diff is large, but there aren't input driver changes: http://www.zip.com.au/~akpm/linux/patches/stuff/diffstat-2.6.12-rc5-mm1 So I dunno, sorry. Brute-force it with a git bisection search, perhaps? ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-30 4:37 ` Andrew Morton @ 2005-07-30 5:57 ` Dmitry Torokhov 2005-07-30 6:34 ` Frank Peters 1 sibling, 0 replies; 29+ messages in thread From: Dmitry Torokhov @ 2005-07-30 5:57 UTC (permalink / raw) To: linux-kernel; +Cc: Andrew Morton, mkrufky, frank.peters, vojtech On Friday 29 July 2005 23:37, Andrew Morton wrote: > > The diff between 2.6.12-rc4-mm2 and 2.6.12-rc5-mm1 is enormous, but there > aren't any significant input driver changes there: > http://www.zip.com.au/~akpm/linux/patches/stuff/diffstat-2.6.12-rc4-mm2-2.6.12-rc5-mm1 > >From the original thread it seems that the usual suspects (input and ACPI updates) were not causing the failure, at leat not directly: > >>I applied bk-input.patch directly to 2.6.12-rc5, and it did NOT break it > >>this time. Looks like either a different patch is the culprit, or the > >>combination of this patch and another. > >> > >> > >> > > > >Please try adding bk-acpi to the mix. > > > > > > > Combination of both bk-input and bk-acpi applied to 2.6.12-rc5 still > doesn't break it. What next? Some other patch must be messing things up somehow... -- Dmitry ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-30 4:37 ` Andrew Morton 2005-07-30 5:57 ` Dmitry Torokhov @ 2005-07-30 6:34 ` Frank Peters 2005-07-31 18:45 ` Vojtech Pavlik 1 sibling, 1 reply; 29+ messages in thread From: Frank Peters @ 2005-07-30 6:34 UTC (permalink / raw) To: Andrew Morton; +Cc: mkrufky, vojtech, linux-kernel On Fri, 29 Jul 2005 21:37:24 -0700 Andrew Morton <akpm@osdl.org> wrote: > > So I dunno, sorry. Brute-force it with a git bisection search, perhaps? I compiled 2.6.13-rc4 with ACPI debugging enabled. During a failed boot, when the keyboard was unresponsive, I managed to capture a kernel log of this failure. Here are the lines that caught my attention: kernel: i8042.c: Can't read CTR while initializing i8042. kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A kernel: ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 16 kernel: ttyS2 at I/O 0xb800 (irq = 16) is a 16550A This error/warning message does not occur all the time, but it has appeared at least twice during my brief experimentation and I would consider it something that can be duplicated. So far it is the only anomoly that I have seen anywhere, but it may be more a result of the problem rather than the cause. Frank Peters ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-30 6:34 ` Frank Peters @ 2005-07-31 18:45 ` Vojtech Pavlik 2005-07-31 19:24 ` Frank Peters 0 siblings, 1 reply; 29+ messages in thread From: Vojtech Pavlik @ 2005-07-31 18:45 UTC (permalink / raw) To: Frank Peters; +Cc: Andrew Morton, mkrufky, linux-kernel On Sat, Jul 30, 2005 at 02:34:53AM -0400, Frank Peters wrote: > On Fri, 29 Jul 2005 21:37:24 -0700 > Andrew Morton <akpm@osdl.org> wrote: > > > > > So I dunno, sorry. Brute-force it with a git bisection search, perhaps? > > I compiled 2.6.13-rc4 with ACPI debugging enabled. > > During a failed boot, when the keyboard was unresponsive, I managed > to capture a kernel log of this failure. Here are the lines that caught > my attention: > > kernel: i8042.c: Can't read CTR while initializing i8042. > kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled > kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > kernel: ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 16 > kernel: ttyS2 at I/O 0xb800 (irq = 16) is a 16550A > > This error/warning message does not occur all the time, but it > has appeared at least twice during my brief experimentation and > I would consider it something that can be duplicated. > > So far it is the only anomoly that I have seen anywhere, but it may > be more a result of the problem rather than the cause. Please try 'usb-handoff' on the kernel command line. This looks like an usual symptom on machines that need it. -- Vojtech Pavlik SuSE Labs, SuSE CR ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-31 18:45 ` Vojtech Pavlik @ 2005-07-31 19:24 ` Frank Peters 2005-07-31 20:42 ` Andrew Morton 0 siblings, 1 reply; 29+ messages in thread From: Frank Peters @ 2005-07-31 19:24 UTC (permalink / raw) To: Vojtech Pavlik; +Cc: akpm, mkrufky, linux-kernel On Sun, 31 Jul 2005 20:45:32 +0200 Vojtech Pavlik <vojtech@suse.cz> wrote: > > > > During a failed boot, when the keyboard was unresponsive, I managed > > to capture a kernel log of this failure. Here are the lines that caught > > my attention: > > > > kernel: i8042.c: Can't read CTR while initializing i8042. > > kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled > > kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > > kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > > kernel: ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 16 > > kernel: ttyS2 at I/O 0xb800 (irq = 16) is a 16550A > > > > Please try 'usb-handoff' on the kernel command line. This looks like an > usual symptom on machines that need it. > > > It works! :-))) Booting linux-2.6.13-rc4 with the "usb-handoff" option gives me a working keyboard everytime now. Thank you very much for your interest in this problem. Frank Peters ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-31 19:24 ` Frank Peters @ 2005-07-31 20:42 ` Andrew Morton 2005-07-31 23:48 ` Frank Peters 0 siblings, 1 reply; 29+ messages in thread From: Andrew Morton @ 2005-07-31 20:42 UTC (permalink / raw) To: Frank Peters; +Cc: vojtech, mkrufky, linux-kernel Frank Peters <frank.peters@comcast.net> wrote: > > On Sun, 31 Jul 2005 20:45:32 +0200 > Vojtech Pavlik <vojtech@suse.cz> wrote: > > > > > > > During a failed boot, when the keyboard was unresponsive, I managed > > > to capture a kernel log of this failure. Here are the lines that caught > > > my attention: > > > > > > kernel: i8042.c: Can't read CTR while initializing i8042. > > > kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled > > > kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > > > kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A > > > kernel: ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 16 > > > kernel: ttyS2 at I/O 0xb800 (irq = 16) is a 16550A > > > > > > > Please try 'usb-handoff' on the kernel command line. This looks like an > > usual symptom on machines that need it. > > > > > > > > It works! :-))) > > Booting linux-2.6.13-rc4 with the "usb-handoff" option gives me > a working keyboard everytime now. But 2.6.12 did not require this workaround, yes? ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-07-31 20:42 ` Andrew Morton @ 2005-07-31 23:48 ` Frank Peters 0 siblings, 0 replies; 29+ messages in thread From: Frank Peters @ 2005-07-31 23:48 UTC (permalink / raw) To: Andrew Morton; +Cc: vojtech, mkrufky, linux-kernel On Sun, 31 Jul 2005 13:42:45 -0700 Andrew Morton <akpm@osdl.org> wrote: > > > > Booting linux-2.6.13-rc4 with the "usb-handoff" option gives me > > a working keyboard everytime now. > > But 2.6.12 did not require this workaround, yes? > I still have linux-2.6.12.3 on my machine and the "usb-handoff" option fixes things for that version also. Linux-2.6.12.3 does need this option with my hardware. Frank Peters ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems [not found] ` <20050728222838.64517cc9.akpm@osdl.org> 2005-07-29 5:44 ` Michael Krufky @ 2005-07-29 18:33 ` Frank Peters [not found] ` <20050804162812.29a3f2b2.akpm@osdl.org> 1 sibling, 1 reply; 29+ messages in thread From: Frank Peters @ 2005-07-29 18:33 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, vojtech On Thu, 28 Jul 2005 22:28:38 -0700 Andrew Morton <akpm@osdl.org> wrote: > > Guys, are these problems fixed in 2.6.13-rc4? > > If not, please cc linux-kernel on the reply, thanks. > Unfortunately, with 2.6.13-rc4 the problems are still here. It takes, on average, about 5-6 reboots before I get a working keyboard. It's a problem I can live with. Once things get going, the system runs without any problems for the rest of the day. If there is anything I can do to assist, just let me know. Frank Peters ^ permalink raw reply [flat|nested] 29+ messages in thread
[parent not found: <20050804162812.29a3f2b2.akpm@osdl.org>]
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems [not found] ` <20050804162812.29a3f2b2.akpm@osdl.org> @ 2005-08-05 3:09 ` Frank Peters 2005-08-05 3:20 ` Dmitry Torokhov 0 siblings, 1 reply; 29+ messages in thread From: Frank Peters @ 2005-08-05 3:09 UTC (permalink / raw) To: Andrew Morton; +Cc: vojtech, linux-kernel I'll use bugzilla to report any problems with 2.6.13-rc6. But since I've included the "usb-handoff" option at boot time, all my problems (except the long dhcp/eth0 connect time) are now gone. Right now I'm using 2.6.13-rc5. I understand the need to pinpoint the kernel version, but the "usb-handoff" option has even corrected some problems that started in linux-2.4.x. For example, my PS/2 mouse now functions normally. It has not worked with this motherboard since some time in the 2.4.x series. Also, my keyboard lights were malfunctioning under X-Window since early 2.6.x, but with the "usb-handoff" option they are working normally now. If I had known about the "usb-handoff" option earlier, this thread probalby would not even have come into existence. As long as "usb-handoff" keeps working, I would consider the issue closed. Frank Peters On Thu, 4 Aug 2005 16:28:12 -0700 Andrew Morton <akpm@osdl.org> wrote: > > Frank, if any problems remain in 2.6.13-rc6 could you please raise new > bugzilla.kernel.org records for them? That way poor old me will be able to > keep tabs on progress more easily. > > (It's especially important to identify the most recent kernel version which > didn't have a particular bug) > > Thanks. ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-08-05 3:09 ` Frank Peters @ 2005-08-05 3:20 ` Dmitry Torokhov 2005-08-05 3:54 ` Andrew Morton 0 siblings, 1 reply; 29+ messages in thread From: Dmitry Torokhov @ 2005-08-05 3:20 UTC (permalink / raw) To: linux-kernel; +Cc: Frank Peters, Andrew Morton, vojtech On Thursday 04 August 2005 22:09, Frank Peters wrote: > I'll use bugzilla to report any problems with 2.6.13-rc6. > > But since I've included the "usb-handoff" option at boot time, > all my problems (except the long dhcp/eth0 connect time) are > now gone. Right now I'm using 2.6.13-rc5. > > I understand the need to pinpoint the kernel version, but the > "usb-handoff" option has even corrected some problems that > started in linux-2.4.x. For example, my PS/2 mouse now functions > normally. It has not worked with this motherboard since some time > in the 2.4.x series. Also, my keyboard lights were malfunctioning > under X-Window since early 2.6.x, but with the "usb-handoff" option > they are working normally now. > > If I had known about the "usb-handoff" option earlier, this thread > probalby would not even have come into existence. As long as "usb-handoff" > keeps working, I would consider the issue closed. > We really really need to make usb-handoff default. Even if there known boxes that don't like it the blacklist would be rather short, much shorter than a whitelist. -- Dmitry ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-08-05 3:20 ` Dmitry Torokhov @ 2005-08-05 3:54 ` Andrew Morton 2005-08-05 4:07 ` Dmitry Torokhov 2005-08-05 4:07 ` Michael Krufky 0 siblings, 2 replies; 29+ messages in thread From: Andrew Morton @ 2005-08-05 3:54 UTC (permalink / raw) To: Dmitry Torokhov; +Cc: linux-kernel, frank.peters, vojtech Dmitry Torokhov <dtor_core@ameritech.net> wrote: > > On Thursday 04 August 2005 22:09, Frank Peters wrote: > > I'll use bugzilla to report any problems with 2.6.13-rc6. > > > > But since I've included the "usb-handoff" option at boot time, > > all my problems (except the long dhcp/eth0 connect time) are > > now gone. Right now I'm using 2.6.13-rc5. > > > > I understand the need to pinpoint the kernel version, but the > > "usb-handoff" option has even corrected some problems that > > started in linux-2.4.x. For example, my PS/2 mouse now functions > > normally. It has not worked with this motherboard since some time > > in the 2.4.x series. Also, my keyboard lights were malfunctioning > > under X-Window since early 2.6.x, but with the "usb-handoff" option > > they are working normally now. > > > > If I had known about the "usb-handoff" option earlier, this thread > > probalby would not even have come into existence. As long as "usb-handoff" > > keeps working, I would consider the issue closed. > > > > We really really need to make usb-handoff default. Even if there known boxes > that don't like it the blacklist would be rather short, much shorter than > a whitelist. Sounds like a fun thing for post-2.6.13. What does usb-handoff do, precisely? ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-08-05 3:54 ` Andrew Morton @ 2005-08-05 4:07 ` Dmitry Torokhov 2005-08-05 10:40 ` Marc Ballarin 2005-08-05 4:07 ` Michael Krufky 1 sibling, 1 reply; 29+ messages in thread From: Dmitry Torokhov @ 2005-08-05 4:07 UTC (permalink / raw) To: Andrew Morton; +Cc: linux-kernel, frank.peters, vojtech On Thursday 04 August 2005 22:54, Andrew Morton wrote: > Dmitry Torokhov <dtor_core@ameritech.net> wrote: > > > > On Thursday 04 August 2005 22:09, Frank Peters wrote: > > > I'll use bugzilla to report any problems with 2.6.13-rc6. > > > > > > But since I've included the "usb-handoff" option at boot time, > > > all my problems (except the long dhcp/eth0 connect time) are > > > now gone. Right now I'm using 2.6.13-rc5. > > > > > > I understand the need to pinpoint the kernel version, but the > > > "usb-handoff" option has even corrected some problems that > > > started in linux-2.4.x. For example, my PS/2 mouse now functions > > > normally. It has not worked with this motherboard since some time > > > in the 2.4.x series. Also, my keyboard lights were malfunctioning > > > under X-Window since early 2.6.x, but with the "usb-handoff" option > > > they are working normally now. > > > > > > If I had known about the "usb-handoff" option earlier, this thread > > > probalby would not even have come into existence. As long as "usb-handoff" > > > keeps working, I would consider the issue closed. > > > > > > > We really really need to make usb-handoff default. Even if there known boxes > > that don't like it the blacklist would be rather short, much shorter than > > a whitelist. > > Sounds like a fun thing for post-2.6.13. > > What does usb-handoff do, precisely? > It requests BIOS to hand off control of USB which disables USB legacy emulation and all troubles associated with it. We could start with -mm... -- Dmitry ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-08-05 4:07 ` Dmitry Torokhov @ 2005-08-05 10:40 ` Marc Ballarin 0 siblings, 0 replies; 29+ messages in thread From: Marc Ballarin @ 2005-08-05 10:40 UTC (permalink / raw) To: Dmitry Torokhov; +Cc: akpm, linux-kernel, frank.peters, vojtech On Thu, 4 Aug 2005 23:07:33 -0500 Dmitry Torokhov <dtor_core@ameritech.net> wrote: > It requests BIOS to hand off control of USB which disables USB legacy emulation > and all troubles associated with it. We could start with -mm... This also fixes an issue I encountered while doing power measurements: without uhci-hcd loaded, the system could not enter C3 state. This could be fixed by either loading uhci-hcd without devices attached or by specifying "usb-handoff". So, this can also fix "silent" issues. Regards ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-08-05 3:54 ` Andrew Morton 2005-08-05 4:07 ` Dmitry Torokhov @ 2005-08-05 4:07 ` Michael Krufky 2005-08-05 6:43 ` Vojtech Pavlik 1 sibling, 1 reply; 29+ messages in thread From: Michael Krufky @ 2005-08-05 4:07 UTC (permalink / raw) To: Andrew Morton; +Cc: Dmitry Torokhov, linux-kernel, frank.peters, vojtech Andrew Morton wrote: >Dmitry Torokhov <dtor_core@ameritech.net> wrote: > > >>On Thursday 04 August 2005 22:09, Frank Peters wrote: >> >> >>>I'll use bugzilla to report any problems with 2.6.13-rc6. >>> >>>But since I've included the "usb-handoff" option at boot time, >>>all my problems (except the long dhcp/eth0 connect time) are >>>now gone. Right now I'm using 2.6.13-rc5. >>> >>>I understand the need to pinpoint the kernel version, but the >>>"usb-handoff" option has even corrected some problems that >>>started in linux-2.4.x. For example, my PS/2 mouse now functions >>>normally. It has not worked with this motherboard since some time >>>in the 2.4.x series. Also, my keyboard lights were malfunctioning >>>under X-Window since early 2.6.x, but with the "usb-handoff" option >>>they are working normally now. >>> >>>If I had known about the "usb-handoff" option earlier, this thread >>>probalby would not even have come into existence. As long as "usb-handoff" >>>keeps working, I would consider the issue closed. >>> >>We really really need to make usb-handoff default. Even if there known boxes >>that don't like it the blacklist would be rather short, much shorter than >>a whitelist. >> >> >Sounds like a fun thing for post-2.6.13. > >What does usb-handoff do, precisely? > I just did a series tests. This is necessary, because the problem was intermittent for me. usb-handoff fixes all of my problems!!! without using usb-handoff, my ps/2 mouse works 1/10 times using usb-handoff, my ps/2 mouse works 10/10 times I consider the problem solved... If Dmitry wants to make usb-handoff the default, he has my support :-). -- Michael Krufky ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-08-05 4:07 ` Michael Krufky @ 2005-08-05 6:43 ` Vojtech Pavlik 0 siblings, 0 replies; 29+ messages in thread From: Vojtech Pavlik @ 2005-08-05 6:43 UTC (permalink / raw) To: Michael Krufky; +Cc: Andrew Morton, Dmitry Torokhov, linux-kernel, frank.peters On Fri, Aug 05, 2005 at 12:07:55AM -0400, Michael Krufky wrote: > >Sounds like a fun thing for post-2.6.13. > > > >What does usb-handoff do, precisely? > > > I just did a series tests. This is necessary, because the problem was > intermittent for me. usb-handoff fixes all of my problems!!! > > without using usb-handoff, my ps/2 mouse works 1/10 times > using usb-handoff, my ps/2 mouse works 10/10 times > > I consider the problem solved... If Dmitry wants to make usb-handoff the > default, he has my support :-). Here is a patch from the SuSE kernel CVS. It's been in SuSE's kernels since 9.1 I believe, and that's a long time. [usb-handoff-default.diff] Date: Fri Mar 4 21:53:39 CET 2005 From: Vojtech Pavlik <vojtech@suse.cz> Subject: Make "usb-handoff" the default, "usb-no-handoff" turns it off. ============================================================================================= Documentation/kernel-parameters.txt | 1 + drivers/pci/quirks.c | 8 +++++++- 2 files changed, 8 insertions(+), 1 deletion(-) ============================================================================================= diff -ur linux-2.6.12/Documentation/kernel-parameters.txt linux-2.6.12-input/Documentation/kernel-parameters.txt --- linux-2.6.12/Documentation/kernel-parameters.txt 2005-06-24 15:56:17.000000000 +0200 +++ linux-2.6.12-input/Documentation/kernel-parameters.txt 2005-06-24 15:57:06.000000000 +0200 @@ -1456,6 +1456,7 @@ Format: <io>,<irq> usb-handoff [HW] Enable early USB BIOS -> OS handoff + usb-no-handoff [HW] Disable early USB BIOS -> OS handoff usbhid.mousepoll= [USBHID] The interval which mice are to be polled at. diff -ur linux-2.6.12/drivers/pci/quirks.c linux-2.6.12-input/drivers/pci/quirks.c --- linux-2.6.12/drivers/pci/quirks.c 2005-06-24 15:56:17.000000000 +0200 +++ linux-2.6.12-input/drivers/pci/quirks.c 2005-06-24 15:56:42.000000000 +0200 @@ -902,13 +902,23 @@ #define EHCI_USBLEGCTLSTS 4 /* legacy control/status */ #define EHCI_USBLEGCTLSTS_SOOE (1 << 13) /* SMI on ownership change */ +#if defined(__i386__) || defined(__x86_64__) +int usb_early_handoff __devinitdata = 1; /* Do handoff by default */ +#else int usb_early_handoff __devinitdata = 0; +#endif static int __init usb_handoff_early(char *str) { usb_early_handoff = 1; return 0; } __setup("usb-handoff", usb_handoff_early); +static int __init usb_no_handoff_early(char *str) +{ + usb_early_handoff = 0; + return 0; +} +__setup("usb-no-handoff", usb_no_handoff_early); static void __devinit quirk_usb_handoff_uhci(struct pci_dev *pdev) { -- Vojtech Pavlik SuSE Labs, SuSE CR ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-06-24 17:12 ` Michael Krufky [not found] ` <20050728222838.64517cc9.akpm@osdl.org> @ 2005-08-04 20:19 ` Andrew Morton 1 sibling, 0 replies; 29+ messages in thread From: Andrew Morton @ 2005-08-04 20:19 UTC (permalink / raw) To: mkrufky; +Cc: frank.peters, linux-kernel, vojtech Michael Krufky <mkrufky@m1k.net> wrote: > > I am cc'ing your message to Vojtech Pavlik, the INPUT DRIVERS kernel > maintainer. > > Vojtech, I figured these should be sent to you. If I am wrong, please > redirect them to the correct person / list and let us know. > (Pleasee don't top-post. See what a mess you've made!) I don't think we've fixed all the bugs which people were reporting in this thread. Could people please retest 2.6.13-rc6 when it's out and generate new reports for any remaining problems? Via bugzilla.kernel.org would be preferred (by me. Otherwise tracking the status of these things is a nightmare). Thanks. (And, unlike previous cycles, I'll be tracking these bugs into the 2.6.14 series, so nobody can hide!) (As long as they're in bugzilla) > > Frank Peters wrote: > > >On Fri, 24 Jun 2005 12:10:18 -0400 > >Michael Krufky <mkrufky@m1k.net> wrote: > > > > > > > >>I am having the same problem with my Shuttle FT61 motherboard, although > >>I have not tried to disable ACPI... Until now I thought I just had a > >>faulty keyboard, as my method to fix this was to unplug the keyboard and > >>plug it back in after bootup. When this happens, I see this in dmesg as > >>the last line: > >> > >>input: AT Translated Set 2 keyboard on isa0060/serio0 > >> > >>I am also having problems with my AUX mouse, as seen in message > >> > >>Subject: 2.6.12-rc5-mm1 breaks serio: i8042 AUX port > >> > >>Frank, are you having problems with your ps/2 mouse port as well? > >> > >> > >> > > > >I am so glad that you asked this. > > > >I have not been able to get my ps/2 mouse to function with any > >2.6.x or 2.4.x kernel (same ASUS MB). The problem is already > >so long standing that I have completely given up on it and use > >a serial mouse exclusively and no longer bother with ps/2. > > > >(I also hate to report that since I dual boot with MS Windows, > >the ps/2 mouse functions properly under the same conditions > >with MS Windows 2K. The hardware cannot be at fault.) > > > > > > > >>As a clarification, I have been having these keyboard problems > >>intermittently, regardless of whether I'm using -mm or mainline kernel. > >>I was NOT having this problem in 2.6.11 I wasn't having the psaux mouse > >>problems in 2.6.11 either .... I unplugged my psaux mouse from that > >>machine before 2.6.12-mainline was released, so I don't know if those > >>symptoms are still present. > >> > >> > > > >Actually, my keyboard problems began with kernel-2.6.11, but were > >quickly resolved when I used the following parameter in my lilo.conf > >file: > > > >i8042.nomux > > > >When I use this parameter, or any other i8042 specific parameter, > >with kernel-2.6.12, there is no effect. The keyboard still occasionally > >comes up dead. > > > >Thanks for the information on unplugging and re-plugging the keyboard. > >I'll give that a try soon. > > > >Frank Peters > > > >(Please CC to frank.peters@comcast.net as I am not a subscriber to this > >list.) > >- > >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > >the body of a message to majordomo@vger.kernel.org > >More majordomo info at http://vger.kernel.org/majordomo-info.html > >Please read the FAQ at http://www.tux.org/lkml/ > > > > > > > -- > Michael Krufky > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: isa0060/serio0 problems -WAS- Re: Asus MB and 2.6.12 Problems 2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky 2005-06-24 16:59 ` Frank Peters @ 2005-06-27 11:39 ` Michael Krufky 1 sibling, 0 replies; 29+ messages in thread From: Michael Krufky @ 2005-06-27 11:39 UTC (permalink / raw) To: mkrufky; +Cc: vojtech, Frank Peters, linux-kernel Michael Krufky wrote: > Frank Peters <frank.peters@comcast.net> wrote: > >> After downloading and compiling the latest version 2.6.12, my >> keyboard becomes unresponsive and dead following the boot process. >> This doesn't occur all of the time, but only some of the time. >> In particular, the follwing boot up message will be seen at >> sporadic places among the other text output: >> >> input: AT Translated Set 2 keyboard on isa0060/serio0 >> >> When this message does not occur anywhere in the boot messages, >> the keyboard is not functional. When the message does occur, then >> the keyboard will respond, but sometimes with an erratic key >> repeat rate. After rebooting several times I can usually get >> the system up and running smoothly, but with this current kernel >> 2.6.12, there is no guarantee that it will boot properly at any >> given time. >> >> > ... > >> My system is an ASUS P4B533 motherboard with a Pentium 3.6 Ghz >> Hyperthreaded processor and 1 GHz RAM. The kernel is the stock >> linux kernel (compiled with gcc-2.95.3) and the rest of my software >> is self-compiled (i.e. no distribution). >> >> If I disable ACPI, either by compiling a new 2.6.12 kernel or >> through boot up parameters, the keyboard will respond normally >> without any problems, but the kernel will not recognize my >> hyperthreaded processor. Only one CPU will be initialized and >> active. >> >> Thus, I can enjoy a problem-free 2.6.12 kernel if I choose to >> sacrifice ACPI and hyperthreading. >> >> > ... > >> If anyone has any suggestions or needs any more information, >> please CC me at the address frank.peters@comcast.net as I am not >> a subscriber to the list. >> >> > I am having the same problem with my Shuttle FT61 motherboard, > although I have not tried to disable ACPI... Until now I thought I > just had a faulty keyboard, as my method to fix this was to unplug the > keyboard and plug it back in after bootup. When this happens, I see > this in dmesg as the last line: > > input: AT Translated Set 2 keyboard on isa0060/serio0 > > I am also having problems with my AUX mouse, as seen in message > > Subject: 2.6.12-rc5-mm1 breaks serio: i8042 AUX port > > Frank, are you having problems with your ps/2 mouse port as well? > > I haven't spent enough time experimenting with this, as I thought it > might have had something to to with my hardware / KVM switch. Seeing > Frank's message is the reason why I've decided to chime back in on this. > > As a clarification, I have been having these keyboard problems > intermittently, regardless of whether I'm using -mm or mainline > kernel. I was NOT having this problem in 2.6.11 I wasn't having the > psaux mouse problems in 2.6.11 either .... I unplugged my psaux mouse > from that machine before 2.6.12-mainline was released, so I don't know > if those symptoms are still present. (using USB mouse now instead). > I am currently in my office, so I can't test this right now, and I > will be away for this weekend. I'll be able to make these tests again > come Sunday night/Monday. ...and I will try it this time WITHOUT the > kvm switch. > I tested the above scenarios with 2.6.12-mm2 and everything is working normally again. ...still having input problems with older -mm kernels, but if -mm2 is working then I must assume that the problem, (at least MY problem) has already been fixed. Thank you! ^ permalink raw reply [flat|nested] 29+ messages in thread
[parent not found: <1119633158.3180.5.camel@home-lap>]
* Re: Asus MB and 2.6.12 Problems [not found] ` <1119633158.3180.5.camel@home-lap> @ 2005-06-24 18:07 ` Frank Peters 0 siblings, 0 replies; 29+ messages in thread From: Frank Peters @ 2005-06-24 18:07 UTC (permalink / raw) To: linux-kernel; +Cc: Sean Bruno On Fri, 24 Jun 2005 10:12:38 -0700 Sean Bruno <sean.bruno@dsl-only.net> wrote: > > Can you post the output of dmesg and lspci -vv please? > Following the latest successful boot, with keyboard functioning normally, here is the kernal log. To save space, I deleted the "Jun 24 10:52:09 (none) kernel:" that occurs before every line. klogd 1.4.1, log source = /proc/kmsg started. Inspecting /boot/System.map Loaded 23754 symbols from /boot/System.map. Symbols match kernel version 2.6.12. No module symbols loaded - kernel modules not enabled. Linux version 2.6.12 (root@localhost.localdomain) (gcc version 2.95.3 20010315 (release)) #9 SMP Tue Jun 21 11:09:26 EDT 2005 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003ffec000 (usable) BIOS-e820: 000000003ffec000 - 000000003ffef000 (ACPI data) BIOS-e820: 000000003ffef000 - 000000003ffff000 (reserved) BIOS-e820: 000000003ffff000 - 0000000040000000 (ACPI NVS) BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved) 127MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 262124 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 32748 pages, LIFO batch:15 DMI 2.3 present. ACPI: RSDP (v000 ASUS ) @ 0x000f52b0 ACPI: RSDT (v001 ASUS P4B533 0x42302e31 MSFT 0x31313031) @ 0x3ffec000 ACPI: FADT (v001 ASUS P4B533 0x42302e31 MSFT 0x31313031) @ 0x3ffec0c0 ACPI: BOOT (v001 ASUS P4B533 0x42302e31 MSFT 0x31313031) @ 0x3ffec030 ACPI: MADT (v001 ASUS P4B533 0x42302e31 MSFT 0x31313031) @ 0x3ffec058 ACPI: DSDT (v001 ASUS P4B533 0x00001000 MSFT 0x0100000b) @ 0x00000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:2 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 15:2 APIC version 20 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 40000000 (gap: 40000000:bec00000) Built 1 zonelists Kernel command line: BOOT_IMAGE=2.6.12 ro root=302 pci=usepirqmask i8042.nomux mapped APIC to ffffd000 (fee00000) mapped IOAPIC to ffffc000 (fec00000) Initializing CPU#0 PID hash table entries: 4096 (order: 12, 65536 bytes) Detected 3102.282 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 1035872k/1048496k available (1368k kernel code, 11864k reserved, 571k data, 408k init, 130992k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 6127.61 BogoMIPS (lpj=3063808) Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. CPU0: Intel(R) Pentium(R) 4 CPU 3.06GHz stepping 09 Booting processor 1/1 eip 2000 Initializing CPU#1 Calibrating delay loop... 6193.15 BogoMIPS (lpj=3096576) CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080 00004400 00000000 00000000 CPU1: Intel(R) Pentium(R) 4 CPU 3.06GHz stepping 09 Total of 2 processors activated (12320.76 BogoMIPS). ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 checking TSC synchronization across 2 CPUs: passed. Brought up 2 CPUs CPU0 attaching sched-domain: domain 0: span 03 groups: 01 02 domain 1: span 03 groups: 03 CPU1 attaching sched-domain: domain 0: span 03 groups: 02 01 domain 1: span 03 groups: 03 NET: Registered protocol family 16 PCI: PCI BIOS revision 2.10 entry at 0xf1eb0, last bus=2 PCI: Using configuration type 1 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20050309 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) PCI: Enabled i801 SMBus device PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1 Boot video device is 0000:01:00.0 PCI: Transparent bridge - 0000:00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI2._PRT] PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report Simple Boot Flag at 0x3a set to 0x80 highmem bounce pool size: 64 pages 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 ACPI: PCI Interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 22 ttyS4 at I/O 0xb800 (irq = 22) is a 16550A io scheduler noop registered io scheduler anticipatory registered Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH4: IDE controller at PCI slot 0000:00:1f.1 ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18 ICH4: chipset revision 1 ICH4: not 100%% native mode: will probe irqs later ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio Probing IDE interface ide0... hda: WDC WD800BB-00CAA1, ATA DISK drive hdb: WDC WD300BB-32CCB0, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: PLEXTOR DVDR PX-712A, ATAPI CD/DVD-ROM 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: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100) hda: cache flushes not supported hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 > hdb: max request size: 128KiB hdb: 58633344 sectors (30020 MB) w/2048KiB Cache, CHS=58168/16/63, UDMA(100) hdb: cache flushes not supported hdb: hdb1 hdb2 hdb3 hdb4 < hdb5 hdb6 hdb7 hdb8 > mice: PS/2 mouse device common for all mice NET: Registered protocol family 2 IP: routing cache hash table of 4096 buckets, 64Kbytes TCP established hash table entries: 262144 (order: 10, 4194304 bytes) TCP bind hash table entries: 65536 (order: 7, 786432 bytes) TCP: Hash tables configured (established 262144 bind 65536) NET: Registered protocol family 1 Starting balanced_irq ReiserFS: hda2: found reiserfs format "3.6" with standard journal ReiserFS: hda2: using ordered data mode ReiserFS: hda2: journal params: device hda2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda2: checking transaction log (hda2) ReiserFS: hda2: Using r5 hash to sort names VFS: Mounted root (reiserfs filesystem) readonly. Freeing unused kernel memory: 408k freed Adding 1952992k swap on /dev/hda3. Priority:-1 extents:1 ReiserFS: hda6: found reiserfs format "3.6" with standard journal ReiserFS: hda6: using ordered data mode ReiserFS: hda6: journal params: device hda6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda6: checking transaction log (hda6) ReiserFS: hda6: Using r5 hash to sort names ReiserFS: hda5: found reiserfs format "3.6" with standard journal ReiserFS: hda5: using ordered data mode ReiserFS: hda5: journal params: device hda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda5: checking transaction log (hda5) ReiserFS: hda5: Using r5 hash to sort names Real Time Clock Driver v1.12 input: AT Translated Set 2 keyboard on isa0060/serio0 ACPI: PCI Interrupt 0000:02:0c.0[A] -> GSI 20 (level, low) -> IRQ 20 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 0000:02:0c.0: 3Com PCI 3c900 Cyclone 10Mbps TPO at 0xa000. Vers LK1.1.19 NET: Registered protocol family 17 ACPI: PCI Interrupt 0000:02:0c.0[A] -> GSI 20 (level, low) -> IRQ 20 Following an unsuccessful boot, with the keyboard dead, the log is identical except that the "input: AT Translated Set 2 keyboard on isa0060/serio0" line does not appear. During a successful boot up, with keyboard functional, this line is liable to pop up in different places (on the terminal screen) as if there is a variable lag in keyboard detection. But there are never any obvious error messages of any kind. Here is output from lspci -vv: 00:00.0 Class 0600: 8086:1a30 (rev 11) Subsystem: 1043:8088 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- Latency: 0 Region 0: Memory at fc000000 (32-bit, prefetchable) [size=32M] Capabilities: [e4] #09 [a104] Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> 00:01.0 Class 0604: 8086:1a31 (rev 11) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: ee000000-efdfffff Prefetchable memory behind bridge: eff00000-fbffffff BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B- 00:1d.0 Class 0c03: 8086:24c2 (rev 01) Subsystem: 1043:8089 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 A routed to IRQ 11 Region 4: I/O ports at d800 [size=32] 00:1d.1 Class 0c03: 8086:24c4 (rev 01) Subsystem: 1043:8089 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 10 Region 4: I/O ports at d400 [size=32] 00:1d.2 Class 0c03: 8086:24c7 (rev 01) Subsystem: 1043:8089 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 C routed to IRQ 255 Region 4: I/O ports at d000 [size=32] 00:1d.7 Class 0c03: 8086:24cd (rev 01) (prog-if 20) Subsystem: 1043:8089 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 D routed to IRQ 9 Region 0: Memory at ed800000 (32-bit, non-prefetchable) [size=1K] 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- Capabilities: [58] #0a [2080] 00:1e.0 Class 0604: 8086:244e (rev 81) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR+ Latency: 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=32 I/O behind bridge: 0000a000-0000bfff Memory behind bridge: ec800000-ed7fffff Prefetchable memory behind bridge: efe00000-efefffff BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B- 00:1f.0 Class 0601: 8086:24c0 (rev 01) 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 00:1f.1 Class 0101: 8086:24cb (rev 01) (prog-if 8a [Master SecP PriP]) Subsystem: 1043:8089 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 A routed to IRQ 18 Region 0: I/O ports at <unassigned> Region 1: I/O ports at <unassigned> Region 2: I/O ports at <unassigned> Region 3: I/O ports at <unassigned> Region 4: I/O ports at f000 [size=16] Region 5: Memory at 40000000 (32-bit, non-prefetchable) [size=1K] 00:1f.3 Class 0c05: 8086:24c3 (rev 01) Subsystem: 1043:8089 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- Interrupt: pin B routed to IRQ 0 Region 4: I/O ports at e800 [size=32] 01:00.0 Class 0300: 10de:0185 (rev c1) 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: 64 (1250ns min, 250ns max) Interrupt: pin A routed to IRQ 11 Region 0: Memory at ee000000 (32-bit, non-prefetchable) [size=16M] Region 1: Memory at f0000000 (32-bit, prefetchable) [size=128M] Expansion ROM at effe0000 [disabled] [size=128K] Capabilities: [60] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [44] AGP version 3.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none> 02:0a.0 Class 0780: 11c1:0480 Subsystem: 11c1:5656 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 (63000ns min, 3500ns max) Interrupt: pin A routed to IRQ 22 Region 0: Memory at ed000000 (32-bit, non-prefetchable) [size=256] Region 1: I/O ports at b800 [size=256] Region 2: I/O ports at b400 [size=256] Region 3: I/O ports at b000 [size=8] Capabilities: [f8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 02:0b.0 Class 0401: 1102:0002 (rev 07) Subsystem: 1102:8071 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: 32 (500ns min, 5000ns max) Interrupt: pin A routed to IRQ 9 Region 0: I/O ports at a800 [size=32] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 02:0b.1 Class 0980: 1102:7002 (rev 07) Subsystem: 1102:0020 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: 32 Region 0: I/O ports at a400 [size=8] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 02:0c.0 Class 0200: 10b7:9004 (rev 04) Subsystem: 10b7:9004 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: 32 (2500ns min, 12000ns max), cache line size 08 Interrupt: pin A routed to IRQ 20 Region 0: I/O ports at a000 [size=128] Region 1: Memory at ec800000 (32-bit, non-prefetchable) [size=128] Expansion ROM at <unassigned> [disabled] [size=128K] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Frank Peters (Please CC at frank.peters@comcast.net because I am not a subscriber to this list.) ^ permalink raw reply [flat|nested] 29+ messages in thread
* Re: Asus MB and 2.6.12 Problems 2005-06-24 15:34 Asus MB and 2.6.12 Problems Frank Peters 2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky [not found] ` <1119633158.3180.5.camel@home-lap> @ 2005-06-26 19:47 ` Alexey Dobriyan 2 siblings, 0 replies; 29+ messages in thread From: Alexey Dobriyan @ 2005-06-26 19:47 UTC (permalink / raw) To: Frank Peters; +Cc: linux-kernel On Friday 24 June 2005 19:34, Frank Peters wrote: > Also, after a successful boot with 2.6.12, I will attempt to > connect with my cable Internet service using the following > commands: > > modprobe 3c59x (load the ethernet modules) > dhcpcd -t 240 (get the IP address from my ISP) > > Formerly, with kernels 2.6.11 and earlier, the connection could > be established very quickly (about 10-15 seconds). But with > kernel 2.6.12, it now requires about 3-4 minutes to establish > the link. I've filed a bug at kernel bugzilla for this part of the problem, so your report won't be lost. See http://bugme.osdl.org/show_bug.cgi?id=4803 You can register at http://bugme.osdl.org/createaccount.cgi and add yourself to CC list. P. S.: Compilation for keyboard problem will be filed RSN. ^ permalink raw reply [flat|nested] 29+ messages in thread
end of thread, other threads:[~2005-08-05 10:43 UTC | newest]
Thread overview: 29+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-24 15:34 Asus MB and 2.6.12 Problems Frank Peters
2005-06-24 16:10 ` isa0060/serio0 problems -WAS- " Michael Krufky
2005-06-24 16:59 ` Frank Peters
2005-06-24 17:12 ` Michael Krufky
[not found] ` <20050728222838.64517cc9.akpm@osdl.org>
2005-07-29 5:44 ` Michael Krufky
2005-07-29 5:54 ` Andrew Morton
2005-07-30 2:44 ` Zwane Mwaikambo
2005-07-30 3:48 ` Michael Krufky
2005-07-30 3:52 ` Michael Krufky
2005-07-30 4:18 ` Michael Krufky
2005-07-30 4:37 ` Andrew Morton
2005-07-30 5:57 ` Dmitry Torokhov
2005-07-30 6:34 ` Frank Peters
2005-07-31 18:45 ` Vojtech Pavlik
2005-07-31 19:24 ` Frank Peters
2005-07-31 20:42 ` Andrew Morton
2005-07-31 23:48 ` Frank Peters
2005-07-29 18:33 ` Frank Peters
[not found] ` <20050804162812.29a3f2b2.akpm@osdl.org>
2005-08-05 3:09 ` Frank Peters
2005-08-05 3:20 ` Dmitry Torokhov
2005-08-05 3:54 ` Andrew Morton
2005-08-05 4:07 ` Dmitry Torokhov
2005-08-05 10:40 ` Marc Ballarin
2005-08-05 4:07 ` Michael Krufky
2005-08-05 6:43 ` Vojtech Pavlik
2005-08-04 20:19 ` Andrew Morton
2005-06-27 11:39 ` Michael Krufky
[not found] ` <1119633158.3180.5.camel@home-lap>
2005-06-24 18:07 ` Frank Peters
2005-06-26 19:47 ` Alexey Dobriyan
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.