2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Hello,

Upon bootup, kernels 2.6.9 and 2.6.10 do not respond to keyboard input 
(e.g., I enter a few chars at the prompt but I see nothing).  I can SSH 
into the system, though, but I don't know what to do from there. I used 
the .config from my 2.6.7 kernel, which works properly (I did run 'make 
oldconfig'). In all .config files, I have the following:

  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

So that looks OK... I also SSH'd into the system, did a 'cat 
/dev/input/event0' and typed on the system's keyboard, but 'cat' 
remained silent. Perhaps there is a better way to see if the system is 
recognizing the keyboard input (or even seeing the keyboard 
itself).  I give up.. what am I doing wrong???


Thanks,

Roey Katz 
PS: please CC responses to roey at freeshell dot org, thanks!

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Saturday 01 January 2005 03:27 am, Roey Katz wrote:
> Hello,
> 
> Upon bootup, kernels 2.6.9 and 2.6.10 do not respond to keyboard input 
> (e.g., I enter a few chars at the prompt but I see nothing).  I can SSH 
> into the system, though, but I don't know what to do from there. I used 
> the .config from my 2.6.7 kernel, which works properly (I did run 'make 
> oldconfig'). In all .config files, I have the following:
> 
>   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
> 
> So that looks OK... I also SSH'd into the system, did a 'cat 
> /dev/input/event0' and typed on the system's keyboard, but 'cat' 
> remained silent. Perhaps there is a better way to see if the system is 
> recognizing the keyboard input (or even seeing the keyboard 
> itself).  I give up.. what am I doing wrong???
> 

What does /proc/bus/input/devices show? Do you have Synaptics touchpad/
driver in your box?

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

On Sat, 1 Jan 2005, Dmitry Torokhov wrote:

> What does /proc/bus/input/devices show? Do you have Synaptics touchpad/
> driver in your box?

Dmitry,

I do not have a Synaptics touchpad on this computer nor do I have the 
driver installed (though all I know is 'grep SYN .config' returned 
empty, so I may be mistaken).  Does the Synaptics driver mess with the 
keyboard at all?


Regarding /proc/bus/input/devices, listing (a) is from 2.6.7 and (b) is 
from 2.6.10.  Note that the mouse and keyboard have switched devices 
(event0 and event1) between kernel versions.  Does this affect it at all 
maybe? BTW, I do have a USB Wacom tablet attached.  Interestingly, 2.6.7 
does not seem to list it in /proc/bus/input/devices.



Thanks!
Roey


listing (a):

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Logitech Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event1
B: EV=120003
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: LED=7

I: Bus=0003 Vendor=046d Product=c50e Version=2500
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:10.1-2/input0
H: Handlers=mouse1 event2
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=103

listing (b):

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Logitech Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0003 Vendor=046d Product=c50e Version=2500
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:10.1-2/input0
H: Handlers=mouse1 event2
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=056a Product=0022 Version=0101
N: Name="Tablet GD-0912-U"
P: Phys=usb-0000:00:10.3-2/input0
H: Handlers=mouse2 event3
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=103

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Sunday 02 January 2005 01:28 am, Roey Katz wrote:
> On Sat, 1 Jan 2005, Dmitry Torokhov wrote:
> 
> > What does /proc/bus/input/devices show? Do you have Synaptics touchpad/
> > driver in your box?
> 
> Dmitry,
> 
> I do not have a Synaptics touchpad on this computer nor do I have the 
> driver installed (though all I know is 'grep SYN .config' returned 
> empty, so I may be mistaken).  Does the Synaptics driver mess with the 
> keyboard at all?
>

Not exactly - Synaptics X driver "grabs" the device it uses so other
processes do not get any data from the touchpad when its active. When
keyboard and mouse initialization got swapped around many people who
were specifying /dev/input/event0 as a device were in for surprise as
the driver "grabbed" keyboard making it impossible to type.

> 
> Regarding /proc/bus/input/devices, listing (a) is from 2.6.7 and (b) is 
> from 2.6.10.  Note that the mouse and keyboard have switched devices 
> (event0 and event1) between kernel versions.  Does this affect it at all 
> maybe? BTW, I do have a USB Wacom tablet attached.  Interestingly, 2.6.7 
> does not seem to list it in /proc/bus/input/devices.
> 

Does the keyboard work when you are not in X (like when booting to
runlevel 3)? It looks like everything is detected correctly...

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1035 bytes --]

On Sun, 2 Jan 2005, Dmitry Torokhov wrote:

>> Dmitry,
>>
>> I do not have a Synaptics touchpad on this computer nor do I have the
>> driver installed (though all I know is 'grep SYN .config' returned
>> empty, so I may be mistaken).  Does the Synaptics driver mess with the
>> keyboard at all?
>>
>
> Not exactly - Synaptics X driver "grabs" the device it uses so other
> processes do not get any data from the touchpad when its active. When
> keyboard and mouse initialization got swapped around many people who
> were specifying /dev/input/event0 as a device were in for surprise as
> the driver "grabbed" keyboard making it impossible to type.

Perhaps the wacom driver is doing some of its own grabbing.  Does the 
evdev device matter to the console (i.e., a pty)?

>
> [snip]
>
> Does the keyboard work when you are not in X (like when booting to
> runlevel 3)? It looks like everything is detected correctly...

That's the thing -- the keyboard is unresponsive right from the login 
prompt.


- Roey

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Dmitry, here is an output listing of a diff I did between the 
.configs of the nonworking 2.6.10 and  the working 2.6.7.


- Roey

-------- diff 2.6.10/.config 2.6.7/.config ------

3,4d2
< # Linux kernel version: 2.6.10
< # Sat Jan  1 01:15:22 2005
10d7
< CONFIG_GENERIC_IOMAP=y
16a14
> CONFIG_STANDALONE=y
18d15
< CONFIG_LOCK_KERNEL=y
23d19
< CONFIG_LOCALVERSION=""
32d27
< CONFIG_KOBJECT_UEVENT=y
38d32
< # CONFIG_KALLSYMS_EXTRA_PASS is not set
40a35,38
> CONFIG_IOSCHED_NOOP=y
> CONFIG_IOSCHED_AS=y
> CONFIG_IOSCHED_DEADLINE=y
> CONFIG_IOSCHED_CFQ=y
42,47d39
< 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
57d48
< # CONFIG_MODULE_SRCVERSION_ALL is not set
86d76
< # CONFIG_MEFFICEON is not set
141d130
< # CONFIG_PM_DEBUG is not set
142a132
> # CONFIG_PM_DISK is not set
155d144
< # CONFIG_ACPI_VIDEO is not set
160d148
< # CONFIG_ACPI_IBM is not set
162d149
< CONFIG_ACPI_BLACKLIST_YEAR=0
180d166
< # CONFIG_CPU_FREQ_DEBUG is not set
188d173
< CONFIG_CPU_FREQ_GOV_ONDEMAND=m
198d182
< CONFIG_X86_POWERNOW_K8_ACPI=y
204d187
< # CONFIG_X86_CPUFREQ_NFORCE2 is not set
209,213d191
< # shared options
< #
< # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
<
< #
224c202
< CONFIG_PCI_MSI=y
---
> # CONFIG_PCI_USE_VECTOR is not set
232,237c210
< # PCCARD (PCMCIA/CardBus) support
< #
< # CONFIG_PCCARD is not set
<
< #
< # PC-card bridges
---
> # PCMCIA/CardBus support
238a212
> # CONFIG_PCMCIA is not set
266,268c240
< CONFIG_STANDALONE=y
< CONFIG_PREVENT_FIRMWARE_BUILD=y
< CONFIG_FW_LOADER=m
---
> # CONFIG_FW_LOADER is not set
291,297d262
< CONFIG_PNP=y
< # CONFIG_PNP_DEBUG is not set
<
< #
< # Protocols
< #
< CONFIG_PNPACPI=y
311,312c276
< CONFIG_BLK_DEV_SX8=y
< # CONFIG_BLK_DEV_UB is not set
---
> CONFIG_BLK_DEV_CARMEL=y
314d277
< CONFIG_BLK_DEV_RAM_COUNT=16
316d278
< CONFIG_INITRAMFS_SOURCE=""
318,328d279
< CONFIG_CDROM_PKTCDVD=m
< CONFIG_CDROM_PKTCDVD_BUFFERS=8
< # CONFIG_CDROM_PKTCDVD_WCACHE is not set
<
< #
< # IO Schedulers
< #
< CONFIG_IOSCHED_NOOP=y
< CONFIG_IOSCHED_AS=y
< CONFIG_IOSCHED_DEADLINE=y
< CONFIG_IOSCHED_CFQ=y
339d289
< CONFIG_BLK_DEV_IDE_SATA=y
346c296
< # CONFIG_BLK_DEV_IDESCSI is not set
---
> CONFIG_BLK_DEV_IDESCSI=m
347a298
> # CONFIG_IDE_TASKFILE_IO is not set
354d304
< CONFIG_BLK_DEV_IDEPNP=y
364a315
> CONFIG_BLK_DEV_ADMA=y
398c349
< CONFIG_SCSI=y
---
> CONFIG_SCSI=m
404c355
< CONFIG_BLK_DEV_SD=y
---
> CONFIG_BLK_DEV_SD=m
409c360
< CONFIG_CHR_DEV_SG=y
---
> CONFIG_CHR_DEV_SG=m
428d378
< # CONFIG_SCSI_3W_9XXX is not set
435,448c385,387
< # CONFIG_MEGARAID_NEWGEN is not set
< # CONFIG_MEGARAID_LEGACY is not set
< CONFIG_SCSI_SATA=y
< CONFIG_SCSI_SATA_AHCI=y
< # 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=y
< CONFIG_SCSI_SATA_SX4=y
< # CONFIG_SCSI_SATA_SIL is not set
< # 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_ADVANSYS is not set
> # CONFIG_SCSI_MEGARAID is not set
> # CONFIG_SCSI_SATA is not set
456d394
< # CONFIG_SCSI_INITIO is not set
465c403
< CONFIG_SCSI_QLA2XXX=y
---
> CONFIG_SCSI_QLA2XXX=m
485d422
< CONFIG_MD_RAID10=m
489d425
< CONFIG_MD_FAULTY=m
531,533d466
< CONFIG_INET_TUNNEL=m
< CONFIG_IP_TCPDIAG=m
< CONFIG_IP_TCPDIAG_IPV6=y
539d471
< CONFIG_INET6_TUNNEL=m
560a493,494
> # CONFIG_NET_FASTROUTE is not set
> # CONFIG_NET_HW_FLOWCONTROL is not set
566d499
< # CONFIG_NET_CLS_ROUTE is not set
582d514
< # CONFIG_NET_SB1000 is not set
645d576
< # CONFIG_R8169_NAPI is not set
647d577
< # CONFIG_VIA_VELOCITY is not set
716,717c646
< CONFIG_SERIO_PCIPS2=y
< # CONFIG_SERIO_RAW is not set
---
> CONFIG_SERIO_PCIPS2=m
749,750c678
< CONFIG_SERIAL_8250=y
< # CONFIG_SERIAL_8250_CONSOLE is not set
---
> CONFIG_SERIAL_8250=m
763c691
< CONFIG_SERIAL_CORE=y
---
> CONFIG_SERIAL_CORE=m
769a698
> # CONFIG_QIC02_TAPE is not set
780c709
< CONFIG_HW_RANDOM=m
---
> # CONFIG_HW_RANDOM is not set
805a735
> # CONFIG_DRM_GAMMA is not set
812d741
< # CONFIG_HPET is not set
826d754
< CONFIG_I2C_ALGOPCA=m
849d776
< # CONFIG_I2C_STUB is not set
853d779
< # CONFIG_I2C_PCA_ISA is not set
860,862d785
< # CONFIG_SENSORS_ADM1025 is not set
< # CONFIG_SENSORS_ADM1026 is not set
< # CONFIG_SENSORS_ADM1031 is not set
868d790
< # CONFIG_SENSORS_LM63 is not set
870d791
< # CONFIG_SENSORS_LM77 is not set
875d795
< # CONFIG_SENSORS_LM87 is not set
878,879d797
< # CONFIG_SENSORS_PC87360 is not set
< # CONFIG_SENSORS_SMSC47M1 is not set
898,902d815
< # Dallas's 1-wire bus
< #
< # CONFIG_W1 is not set
<
< #
934d846
< # CONFIG_VIDEO_OVCAMCHIP is not set
961a874
> # CONFIG_MDA_CONSOLE is not set
1003d915
< # CONFIG_SND_ATIIXP_MODEM is not set
1038c950
< # USB devices
---
> # ALSA USB devices
1041d952
< # CONFIG_SND_USB_USX2Y is not set
1060,1063d970
< # CONFIG_USB_SUSPEND is not set
< # CONFIG_USB_OTG is not set
< CONFIG_USB_ARCH_HAS_HCD=y
< CONFIG_USB_ARCH_HAS_OHCI=y
1073d979
< # CONFIG_USB_SL811_HCD is not set
1083,1086d988
<
< #
< # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be 
needed;see USB_STORAGE Help for more information
< #
1089d990
< # CONFIG_USB_STORAGE_RW_DETECT is not set
1100c1001
< # USB Input Devices
---
> # USB Human Interface Devices (HID)
1136a1038
> # CONFIG_USB_PWC is not set
1138d1039
< # CONFIG_USB_SN9C102 is not set
1139a1041
> # CONFIG_USB_W9968CF is not set
1142c1044
< # USB Network Adapters
---
> # USB Network adaptors
1172d1073
< # CONFIG_USB_PHIDGETKIT is not set
1177,1180d1077
< # USB ATM/DSL drivers
< #
<
< #
1186,1193d1082
< # MMC/SD Card support
< #
< CONFIG_MMC=m
< # CONFIG_MMC_DEBUG is not set
< CONFIG_MMC_BLOCK=m
< # CONFIG_MMC_WBSD is not set
<
< #
1222d1110
< CONFIG_DNOTIFY=y
1234d1121
< CONFIG_UDF_NLS=y
1242,1243d1128
< CONFIG_FAT_DEFAULT_CODEPAGE=437
< CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
1257,1258d1141
< CONFIG_TMPFS_XATTR=y
< CONFIG_TMPFS_SECURITY=y
1292d1174
< # CONFIG_RPCSEC_GSS_SPKM3 is not set
1334d1215
< # CONFIG_NLS_ASCII is not set
1359,1360c1240,1242
< CONFIG_MAGIC_SYSRQ=y
< CONFIG_SCHEDSTATS=y
---
> CONFIG_EARLY_PRINTK=y
> # CONFIG_DEBUG_STACKOVERFLOW is not set
> # CONFIG_DEBUG_STACK_USAGE is not set
1361a1244
> CONFIG_MAGIC_SYSRQ=y
1363,1364c1246
< # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
< # CONFIG_DEBUG_KOBJECT is not set
---
> # CONFIG_DEBUG_PAGEALLOC is not set
1366a1249
> # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
1368,1372d1250
< CONFIG_EARLY_PRINTK=y
< # CONFIG_DEBUG_STACKOVERFLOW is not set
< # CONFIG_KPROBES is not set
< # CONFIG_DEBUG_STACK_USAGE is not set
< # CONFIG_DEBUG_PAGEALLOC is not set
1380d1257
< # CONFIG_KEYS is not set
1394d1270
< CONFIG_CRYPTO_WP512=m
1399c1275
< CONFIG_CRYPTO_AES_586=m
---
> CONFIG_CRYPTO_AES=m
1402d1277
< CONFIG_CRYPTO_TEA=m
1404,1405d1278
< CONFIG_CRYPTO_KHAZAD=m
< CONFIG_CRYPTO_ANUBIS=m
1414d1286
< CONFIG_CRC_CCITT=m
1419,1420d1290
< CONFIG_GENERIC_HARDIRQS=y
< CONFIG_GENERIC_IRQ_PROBE=y
1421a1292
> CONFIG_X86_STD_RESOURCES=y

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Sunday 02 January 2005 09:53 pm, Roey Katz wrote:
> Dmitry, here is an output listing of a diff I did between the 
> .configs of the nonworking 2.6.10 and  the working 2.6.7.
> 

Roey,

Could you please try compiling a minimal kernel (no ACPI, no USB, etc)
to make sure that the changes to input system that were merged in 2.6.9
are to blame.

Also, if you could change #undef DEBUG to #define DEBUG in
drivers/input/serio/i8042.c and send me the entire dmesg output that
could help determining what is the problem. You may want to boot with
log_buf_len=131072 to capture entire dmesg. Don't forget to hit couple
of keys at the login prompt so we can see if we get them from the KBC
controller and loose them somewhere or the KBC is left in funky state.

Thanks!
 
-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Dmitry,

I have the contents of 'kern.log' at:

   http://roey.freeshell.org/mystuff/kernel/kern.log-2.6.10

I will shortly post the output of 'dmesg' as well.


Roey

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Monday 03 January 2005 12:37 am, Roey Katz wrote:
> Dmitry,
> 
> I have the contents of 'kern.log' at:
> 
>    http://roey.freeshell.org/mystuff/kernel/kern.log-2.6.10
> 

The following looks very suspicious:

Jan  2 23:05:17 tits kernel: drivers/input/serio/i8042.c: f2 -> i8042 (kbd-data) [4842]
Jan  2 23:05:17 tits kernel: drivers/input/serio/i8042.c: fa <- i8042 (interrupt, kbd, 1, timeout) [4866]
Jan  2 23:05:17 tits kernel: drivers/input/serio/i8042.c: ab <- i8042 (interrupt, kbd, 1, timeout) [4874]
Jan  2 23:05:17 tits kernel: drivers/input/serio/i8042.c: 41 <- i8042 (interrupt, kbd, 1, timeout) [4882]
Jan  2 23:05:17 tits kernel: drivers/input/serio/i8042.c: ed -> i8042 (kbd-data) [4882]
Jan  2 23:05:17 tits kernel: drivers/input/serio/i8042.c: fa <- i8042 (interrupt, kbd, 1) [4894]
Jan  2 23:05:17 tits kernel: drivers/input/serio/i8042.c: 00 -> i8042 (kbd-data) [4894]
Jan  2 23:05:17 tits kernel: drivers/input/serio/i8042.c: fa <- i8042 (interrupt, kbd, 1) [4906]

atkbd driver tries to get ID from the attached device but although the
controller responds with valid keyboard ID it also for some reason indicates
that the connected device times out. Wierd...

Could you try booting with "acpi=off"?

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Dmitry,

kernel bootup, syslog and dmesg outputs are here:

   http://roey.freeshell.org/mystuff/kernel/

all end in "-20050103"

This is with "acpi=off" as you instructed.


- Roey

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Mon, 3 Jan 2005 13:21:02 +0000 (UTC), Roey Katz
<roey@sdf.lonestar.org> wrote:
> Dmitry,
> 
> kernel bootup, syslog and dmesg outputs are here:
> 
>   http://roey.freeshell.org/mystuff/kernel/
> 
> all end in "-20050103"
> 
> This is with "acpi=off" as you instructed.
>

That is even wierdier. The keyboard controller does not respond to the
most basic command. I have seen one report of this happening
(http://bugme.osdl.org/show_bug.cgi?id=3830) but acpi=off helped in
that case. I wonder, when you tried acpi=off, did you power off your
box or just rebooted?

The big input update went in with 2.6.9-rc2-bk4. Could you please try
bk3 and bk4 to verify that this update is causing the problems or we
shoudl look elsewhere.

I am CCing Vojtech, maybe he has some ideas...

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

On Mon, 3 Jan 2005, Dmitry Torokhov wrote:

>> [snip]
>
> That is even wierdier. The keyboard controller does not respond to the
> most basic command. I have seen one report of this happening
> (http://bugme.osdl.org/show_bug.cgi?id=3830) but acpi=off helped in
> that case. I wonder, when you tried acpi=off, did you power off your
> box or just rebooted?

I rebooted with the 'reboot' command.

> The big input update went in with 2.6.9-rc2-bk4. Could you please try
> bk3 and bk4 to verify that this update is causing the problems or we
> shoudl look elsewhere.

This problem happened for me with 
2.6.9-final as well. I will try with rc2-bk3 and bk4 and keep you posted.

By the way, this box runs Debian 
SID, and SID's own kernel 2.6.9-amd64 image resets the system before it 
gets to the module-loading stage (how weird!)


- Roey

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Dmitry,

I have tried kernels 2.6.9-rc2-bk3 and 2.6.9-rc2-bk4. I first copied the 
.config from the stripped-down 2.6.10 into the 2.6.9- directories and then 
ran make oldconfig (hopefully make oldconfig works in reverse?).  Then I 
built and ran the kernels. Both exhibit the same behavior as 2.6.10 
regarding the keyboard.

The /var/log/{dmesg,syslog,messages,kern.log} files for both kernels are 
available at:

  http://roey.freeshell.org/mystuff/kernel/


- Roey

PS:  I forgot the log_buf_len=131072, hope it's ok for you...
PPS: I also forgot "acpi=off".  Should I re-run these tests?



On Mon, 3 Jan 2005, Dmitry Torokhov wrote:

> Date: Mon, 3 Jan 2005 11:35:25 -0500
> From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Reply-To: dtor_core@ameritech.net
> To: Roey Katz <roey@sdf.lonestar.org>
> Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
> Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
> 
> On Mon, 3 Jan 2005 13:21:02 +0000 (UTC), Roey Katz
> <roey@sdf.lonestar.org> wrote:
>> Dmitry,
>>
>> kernel bootup, syslog and dmesg outputs are here:
>>
>>   http://roey.freeshell.org/mystuff/kernel/
>>
>> all end in "-20050103"
>>
>> This is with "acpi=off" as you instructed.
>>
>
> That is even wierdier. The keyboard controller does not respond to the
> most basic command. I have seen one report of this happening
> (http://bugme.osdl.org/show_bug.cgi?id=3830) but acpi=off helped in
> that case. I wonder, when you tried acpi=off, did you power off your
> box or just rebooted?
>
> The big input update went in with 2.6.9-rc2-bk4. Could you please try
> bk3 and bk4 to verify that this update is causing the problems or we
> shoudl look elsewhere.
>
> I am CCing Vojtech, maybe he has some ideas...
>
> -- 
> Dmitry
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Tuesday 04 January 2005 12:49 am, Roey Katz wrote:
> Dmitry,
> 
> I have tried kernels 2.6.9-rc2-bk3 and 2.6.9-rc2-bk4. I first copied the 
> .config from the stripped-down 2.6.10 into the 2.6.9- directories and then 
> ran make oldconfig (hopefully make oldconfig works in reverse?).  Then I 
> built and ran the kernels. Both exhibit the same behavior as 2.6.10 
> regarding the keyboard.
> 
> The /var/log/{dmesg,syslog,messages,kern.log} files for both kernels are 
> available at:
> 
>   http://roey.freeshell.org/mystuff/kernel/
> 
> 
> - Roey
> 
> PS:  I forgot the log_buf_len=131072, hope it's ok for you...
> PPS: I also forgot "acpi=off".  Should I re-run these tests?
> 

Ok, it looks that the big input update is not to blame. Just to make sure
could you re-run the tests with -bk3 and -bk4 but with powering the box
down instead of simply rebooting to ensure that noth kernels get completely
fresh start. If keyboard still does not work I am afraid you will have to
resort to binary search to figure out which 2.6.9-*-bk is at fault. 

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Ya know what, I haven't tried any of the 2.6.8 kernels at all, so maybe 
for that binsearch I could start at 2.8-final? All this, of course after 
testing a full powercycle, as you suggested.

And another thing.. something with libata doesn't jive right with my 
sata drives.  I have 2x74 GB SATA western digital raptors in a Raid 1 
configuration, and it panics if I don't use the pre-libata drivers. I'll 
write up another post about this one -- maybe I'll ask Jeff 
Garzik about this, too, as he works on libata.


Thanks,
- Roey


On Tue, 4 Jan 2005, Dmitry Torokhov wrote:

> Ok, it looks that the big input update is not to blame. Just to make sure
> could you re-run the tests with -bk3 and -bk4 but with powering the box
> down instead of simply rebooting to ensure that noth kernels get completely
> fresh start. If keyboard still does not work I am afraid you will have to
> resort to binary search to figure out which 2.6.9-*-bk is at fault.
>
> -- 
> Dmitry
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Tuesday 04 January 2005 01:17 am, Dmitry Torokhov wrote:
> On Tuesday 04 January 2005 12:49 am, Roey Katz wrote:
> > Dmitry,
> > 
> > I have tried kernels 2.6.9-rc2-bk3 and 2.6.9-rc2-bk4. I first copied the 
> > .config from the stripped-down 2.6.10 into the 2.6.9- directories and then 
> > ran make oldconfig (hopefully make oldconfig works in reverse?).  Then I 
> > built and ran the kernels. Both exhibit the same behavior as 2.6.10 
> > regarding the keyboard.
> > 
> > The /var/log/{dmesg,syslog,messages,kern.log} files for both kernels are 
> > available at:
> > 
> >   http://roey.freeshell.org/mystuff/kernel/
> > 
> > 
> > - Roey
> > 
> > PS:  I forgot the log_buf_len=131072, hope it's ok for you...
> > PPS: I also forgot "acpi=off".  Should I re-run these tests?
> > 
> 
> Ok, it looks that the big input update is not to blame. Just to make sure
> could you re-run the tests with -bk3 and -bk4 but with powering the box
> down instead of simply rebooting to ensure that noth kernels get completely
> fresh start. If keyboard still does not work I am afraid you will have to
> resort to binary search to figure out which 2.6.9-*-bk is at fault. 
> 

Roey,

I just realized that -bk3 also had input changes. Could you try booting -bk2?

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Heh I've already downloaded and patched nine or so release 
candidate kernels from the 2.6.8 and 2.6.9 series, including -bk2.
I'm going to compile them this weekend.

Roey



On Wed, 5 Jan 2005, Dmitry Torokhov wrote:

> Roey,
>
> I just realized that -bk3 also had input changes. Could you try booting -bk2?
>
> -- 
> Dmitry
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Dmitry,

Bingo!
2.6.9-rc2-bk2 worked (where bk3 hadn't before).
The system responded to keyboard input.
What's the next step?


Roey


On Wed, 5 Jan 2005, Dmitry Torokhov wrote:

> Roey,
>
> I just realized that -bk3 also had input changes. Could you try booting -bk2?
>
> -- 
> Dmitry
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Thursday 06 January 2005 11:06 pm, Roey Katz wrote:
> Dmitry,
> 
> Bingo!
> 2.6.9-rc2-bk2 worked (where bk3 hadn't before).
> The system responded to keyboard input.
> What's the next step?
> 

I am not quite sure yet. Could you post the boot log of -bk2 with debug
enabled on your web site, please?

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Done. (the debug was just that initial #define DEBUG in
drivers/input/serio/i8042.c as you specified)


Roey

On Fri, 7 Jan 2005, Dmitry Torokhov wrote:

> I am not quite sure yet. Could you post the boot log of -bk2 with debug
> enabled on your web site, please?

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

Ok, so the timeouts are here even with good version. Hmm...

Ok, one thing is that in -bk3 I moved i8042 initialization earlier,
could you try reversing the fragment below (it is cut and paste so
patch won't work, you'll have to move that line manually). And touch
i8042.c to force rebuild.

If this does not work try disabling psmouse - does it help with the keyboard?

-- 
Dmitry

--- a/drivers/Makefile  2004-09-07 23:33:07 -07:00
+++ b/drivers/Makefile  2004-09-13 03:28:52 -07:00
@@ -16,6 +16,9 @@
 # char/ comes before serial/ etc so that the VT console is the boot-time
 # default.
 obj-y                          += char/
+# we also need input/serio early so serio bus is initialized by the time
+# serial drivers start registering their serio ports
+obj-$(CONFIG_SERIO)            += input/serio/
 obj-y                          += serial/
 obj-$(CONFIG_PARPORT)          += parport/
 obj-y                          += base/ block/ misc/ net/ media/
@@ -40,7 +43,6 @@
 obj-$(CONFIG_USB_GADGET)       += usb/gadget/
 obj-$(CONFIG_INPUT)            += input/
 obj-$(CONFIG_GAMEPORT)         += input/gameport/
-obj-$(CONFIG_SERIO)            += input/serio/
 obj-$(CONFIG_I2O)              += message/
 obj-$(CONFIG_I2C)              += i2c/
 obj-$(CONFIG_W1)               += w1/

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Dmitry,

maybe I'm misunderstanding you;  how should the file look like once I 
modify it with your changes (what does "reversing the fragment" mean 
here)?

On Fri, 7 Jan 2005, Dmitry Torokhov wrote:

> Ok, so the timeouts are here even with good version. Hmm...
>
> Ok, one thing is that in -bk3 I moved i8042 initialization earlier,
> could you try reversing the fragment below (it is cut and paste so
> patch won't work, you'll have to move that line manually). And touch
> i8042.c to force rebuild.
>
> If this does not work try disabling psmouse - does it help with the keyboard?
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Sunday 09 January 2005 12:14 am, Roey Katz wrote:
> Dmitry,
> 
> maybe I'm misunderstanding you;  how should the file look like once I 
> modify it with your changes (what does "reversing the fragment" mean 
> here)?
>

Now that I am at my box, just try applying the patch below.

-- 
Dmitry

===== drivers/Makefile 1.50 vs edited =====
--- 1.50/drivers/Makefile	2004-12-01 01:00:21 -05:00
+++ edited/drivers/Makefile	2005-01-09 00:33:32 -05:00
@@ -21,9 +21,6 @@
 obj-$(CONFIG_FB_I810)           += video/i810/
 obj-$(CONFIG_FB_INTEL)          += video/intelfb/
 
-# we also need input/serio early so serio bus is initialized by the time
-# serial drivers start registering their serio ports
-obj-$(CONFIG_SERIO)		+= input/serio/
 obj-y				+= serial/
 obj-$(CONFIG_PARPORT)		+= parport/
 obj-y				+= base/ block/ misc/ net/ media/
@@ -46,6 +43,7 @@
 obj-$(CONFIG_TC)		+= tc/
 obj-$(CONFIG_USB)		+= usb/
 obj-$(CONFIG_USB_GADGET)	+= usb/gadget/
+obj-$(CONFIG_SERIO)		+= input/serio/
 obj-$(CONFIG_INPUT)		+= input/
 obj-$(CONFIG_GAMEPORT)		+= input/gameport/
 obj-$(CONFIG_I2O)		+= message/

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

I tried (at the top of 2.6.9rc2-bk3/ ), "cat 
dmitrys-patch | patch -p1".  It complained of rejecting hunks and whatnot:

patching file drivers/Makefile
Hunk #1 FAILED at 21.
Hunk #2 FAILED at 43.
2 out of 2 hunks FAILED -- saving rejects to file drivers/Makefile.rej

I tried this in 2.6.10/, but got the same response.


Roey


On Sun, 9 Jan 2005, Dmitry Torokhov wrote:

> Date: Sun, 9 Jan 2005 00:35:02 -0500
> From: Dmitry Torokhov <dtor_core@ameritech.net>
> To: linux-kernel@vger.kernel.org
> Cc: Roey Katz <roey@sdf.lonestar.org>
> Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
> 
> On Sunday 09 January 2005 12:14 am, Roey Katz wrote:
>> Dmitry,
>>
>> maybe I'm misunderstanding you;  how should the file look like once I
>> modify it with your changes (what does "reversing the fragment" mean
>> here)?
>>
>
> Now that I am at my box, just try applying the patch below.
>
> -- 
> Dmitry
>
> ===== drivers/Makefile 1.50 vs edited =====
> --- 1.50/drivers/Makefile	2004-12-01 01:00:21 -05:00
> +++ edited/drivers/Makefile	2005-01-09 00:33:32 -05:00
> @@ -21,9 +21,6 @@
> obj-$(CONFIG_FB_I810)           += video/i810/
> obj-$(CONFIG_FB_INTEL)          += video/intelfb/
>
> -# we also need input/serio early so serio bus is initialized by the time
> -# serial drivers start registering their serio ports
> -obj-$(CONFIG_SERIO)		+= input/serio/
> obj-y				+= serial/
> obj-$(CONFIG_PARPORT)		+= parport/
> obj-y				+= base/ block/ misc/ net/ media/
> @@ -46,6 +43,7 @@
> obj-$(CONFIG_TC)		+= tc/
> obj-$(CONFIG_USB)		+= usb/
> obj-$(CONFIG_USB_GADGET)	+= usb/gadget/
> +obj-$(CONFIG_SERIO)		+= input/serio/
> obj-$(CONFIG_INPUT)		+= input/
> obj-$(CONFIG_GAMEPORT)		+= input/gameport/
> obj-$(CONFIG_I2O)		+= message/
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Sunday 09 January 2005 09:24 am, Roey Katz wrote:
> I tried (at the top of 2.6.9rc2-bk3/ ), "cat 
> dmitrys-patch | patch -p1".  It complained of rejecting hunks and whatnot:
> 
> patching file drivers/Makefile
> Hunk #1 FAILED at 21.
> Hunk #2 FAILED at 43.
> 2 out of 2 hunks FAILED -- saving rejects to file drivers/Makefile.rej
> 
> I tried this in 2.6.10/, but got the same response.
>

Most likely you selected and then pasted the patch while in X. This caused
whitespace damage to the patch (tabs were converted to spaces). Try saving
the entire message into a file with your MUA and feed the result to the
"patch" command.

Alternatively, just edit drivers/Makefile and move the line mentioning
"input/serio" to be just above the line mentioning "input".
  
> > ===== drivers/Makefile 1.50 vs edited =====
> > --- 1.50/drivers/Makefile	2004-12-01 01:00:21 -05:00
> > +++ edited/drivers/Makefile	2005-01-09 00:33:32 -05:00
> > @@ -21,9 +21,6 @@
> > obj-$(CONFIG_FB_I810)           += video/i810/
> > obj-$(CONFIG_FB_INTEL)          += video/intelfb/
> >
> > -# we also need input/serio early so serio bus is initialized by the time
> > -# serial drivers start registering their serio ports
> > -obj-$(CONFIG_SERIO)		+= input/serio/
> > obj-y				+= serial/
> > obj-$(CONFIG_PARPORT)		+= parport/
> > obj-y				+= base/ block/ misc/ net/ media/
> > @@ -46,6 +43,7 @@
> > obj-$(CONFIG_TC)		+= tc/
> > obj-$(CONFIG_USB)		+= usb/
> > obj-$(CONFIG_USB_GADGET)	+= usb/gadget/
> > +obj-$(CONFIG_SERIO)		+= input/serio/
> > obj-$(CONFIG_INPUT)		+= input/
> > obj-$(CONFIG_GAMEPORT)		+= input/gameport/
> > obj-$(CONFIG_I2O)		+= message/
> >
> 

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

OK, I moved that input/serio line to be just above the line mentioning 
"input".  Rebooted;  still got this error.  See all the -2.6.9-rc2-bk3 
logs on my web site (http://roey.freeshell.org/mystuff/kernel/) for 
details. I will follow up with psmouse disabled if you want.


Roey
PS: just changing a Makefile makes a difference?


> Most likely you selected and then pasted the patch while in X. This caused
> whitespace damage to the patch (tabs were converted to spaces). Try saving
> the entire message into a file with your MUA and feed the result to the
> "patch" command.
>
> Alternatively, just edit drivers/Makefile and move the line mentioning
> "input/serio" to be just above the line mentioning "input".
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]

On Sunday 09 January 2005 08:09 pm, Roey Katz wrote:
> OK, I moved that input/serio line to be just above the line mentioning 
> "input".  Rebooted;  still got this error.  See all the -2.6.9-rc2-bk3 
> logs on my web site (http://roey.freeshell.org/mystuff/kernel/) for 
> details. I will follow up with psmouse disabled if you want.
> 

I just don't see anything wrong with it... oh well...

Ok, I have cut out everything but input changes from -rc2-bk3, could you
pleasde try appying the patch below to -rc2. If it does not work it will
prove that the input code is to blame and we'll start reverting changes
one by one to find out the one that broke the keyboard.

Make you are booting with log_buf_len=131072 as some of your logs are
short. And be sure hit keyboard couple of times after the mox finished
booting (single user mode preferably).

Btw, does your mouse work?

> 
> Roey
> PS: just changing a Makefile makes a difference?
>
This particular chane make keyboard controller initialization code run later
in the startup sequence, but apparently it had no visible effect.
 
-- 
Dmitry


[-- Attachment #2: patch-bk3.bz2 --]
[-- Type: application/x-bzip2, Size: 37170 bytes --]

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Dmitry,

I have placed the results of the patched 2.6.9-rc2-bk2 kernel at the 
following address:

   http://roey.freeshell.org/mystuff/kernel/*-20050112

As expected, the system was unresponsive to keyboard input.
Regarding your mouse question:
How do I test the mouse if they keyboard does not work (is there some 
way to output the contents of /dev/psaux on startup? I'm not sure anymore 
what file the mouse data appears in, too)

- Roey


On Tue, 11 Jan 2005, Dmitry Torokhov wrote:

> Date: Tue, 11 Jan 2005 02:39:33 -0500
> From: Dmitry Torokhov <dtor_core@ameritech.net>
> To: linux-kernel@vger.kernel.org
> Cc: Roey Katz <roey@sdf.lonestar.org>
> Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
> 
> On Sunday 09 January 2005 08:09 pm, Roey Katz wrote:
>> OK, I moved that input/serio line to be just above the line mentioning
>> "input".  Rebooted;  still got this error.  See all the -2.6.9-rc2-bk3
>> logs on my web site (http://roey.freeshell.org/mystuff/kernel/) for
>> details. I will follow up with psmouse disabled if you want.
>>
>
> I just don't see anything wrong with it... oh well...
>
> Ok, I have cut out everything but input changes from -rc2-bk3, could you
> pleasde try appying the patch below to -rc2. If it does not work it will
> prove that the input code is to blame and we'll start reverting changes
> one by one to find out the one that broke the keyboard.
>
> Make you are booting with log_buf_len=131072 as some of your logs are
> short. And be sure hit keyboard couple of times after the mox finished
> booting (single user mode preferably).
>
> Btw, does your mouse work?
>
>>
>> Roey
>> PS: just changing a Makefile makes a difference?
>>
> This particular chane make keyboard controller initialization code run later
> in the startup sequence, but apparently it had no visible effect.
>
> -- 
> Dmitry
>
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Wednesday 12 January 2005 10:19 pm, Roey Katz wrote:
> Dmitry,
> 
> I have placed the results of the patched 2.6.9-rc2-bk2 kernel at the 
> following address:
> 
>    http://roey.freeshell.org/mystuff/kernel/*-20050112
> 
> As expected, the system was unresponsive to keyboard input.

And what if you do not compile PS/2 mouse support in? Is keyboard still
dead?

> Regarding your mouse question:
> How do I test the mouse if they keyboard does not work (is there some 
> way to output the contents of /dev/psaux on startup? I'm not sure anymore 
> what file the mouse data appears in, too)
> 

Install GPM and try moving your mouse after booting into runlevel 3 -
if cursor moves mouse works.

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Matthew Harrell]

:
: And what if you do not compile PS/2 mouse support in? Is keyboard still
: dead?
:

I also have an inresponsive keyboard and mouse on my laptop with later kernels.
To qualify that more, the same setup used to compile 2.6.10, 2.6.10-mm2,
2.6.10-mm3, 2.6.11-rc1 only gives me a working keyboard and mouse on the
2.6.10 kernel.  I can plug in a USB keyboard and mouse and they work fine.
Not sure if it's the same problem as the original author.  I just compiled
2.6.11-rc1 with the ps/2 mouse as a module (hoping that forcing it to load
later would help) but that didn't seem to make a difference even though it
looks like the mouse was loaded (by hotplug) after the keyboard should have
been setup.  If you want I'll try another in a few minutes without the
mouse entirely.  It looks like acpi does detect both keyboard and mouse
controllers.  For those interested kernel bootup messages and kernel config
are available here

        http://alecto.bittwiddlers.com/files/linux/boot-2.6.11rc1.log
        http://alecto.bittwiddlers.com/files/linux/defconfig-2.6.11rc1

-- 
  Matthew Harrell                          Failure is not an option. It comes
  Bit Twiddlers, Inc.                       bundled with your Microsoft
  mharrell@bittwiddlers.com                 product.

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Matthew Harrell]

Oh and I think there was a question of whether the mouse worked while the
keyboard did not.  Well in my case neither work post 2.6.10.  I typically
work on the system with a USB keyboard and mouse and everything else works
fine as long as I don't try to use those built into the laptop

-- 
  Matthew Harrell                          Nondeterminism means never
  Bit Twiddlers, Inc.                       having to say you are wrong.
  mharrell@bittwiddlers.com     

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Friday 14 January 2005 06:06 pm, Matthew Harrell wrote:
> To qualify that more, the same setup used to compile 2.6.10, 2.6.10-mm2,
> 2.6.10-mm3, 2.6.11-rc1 only gives me a working keyboard and mouse on the
> 2.6.10 kernel.

Hi,

your scenario is a bit different, it looks like the controller does not want
to response right from the beginning (while on Roey's box kernel detects both
keyboard and mouse just fine):
 
> ACPI: PS/2 Keyboard Controller [KBC] at I/O 0x60, 0x66, irq 1
> ACPI: PS/2 Mouse Controller [PS2M] at irq 12
> i8042.c: Can't read CTR while initializing i8042.

Could you try booting with acpi=off and without PNP compiled in? And maybe
with pci=routeirq

Also, there is a patch my Alan Cox dealing with legacy emulation (but note
that first part (udelay(50)) has already been applied:

http://marc.theaimsgroup.com/?l=linux-kernel&m=109096903809223&q=raw

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Matthew Harrell]

: Could you try booting with acpi=off and without PNP compiled in? And maybe
: with pci=routeirq

Ok, I tried all them individually (hope you didn't mean all at once).  pnp
and pci=routeirq had no effect.  acpi got it to work again but sacrificed 
my second HT cpu and battery monitoring.  I'm going to try to turn acpi on
and pnpacpi off in the kernel and see if that helps.  I'll then try Alan's
patch and see what happens there

-- 
  Matthew Harrell                          I don't suffer from insanity - 
  Bit Twiddlers, Inc.                       I enjoy every minute of it.
  mharrell@bittwiddlers.com     

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Matthew Harrell]

: Also, there is a patch my Alan Cox dealing with legacy emulation (but note
: that first part (udelay(50)) has already been applied:
: 
: http://marc.theaimsgroup.com/?l=linux-kernel&m=109096903809223&q=raw

Well acpipnp didn't have any effect.

I tried the patch above but there's an undefined function, pci_find_class,
in i8042_spank_usb.  Did it change names?

-- 
  Matthew Harrell                          All science is either physics or
  Bit Twiddlers, Inc.                       stamp collecting.
  mharrell@bittwiddlers.com     

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Friday 14 January 2005 09:58 pm, Matthew Harrell wrote:
> : Also, there is a patch my Alan Cox dealing with legacy emulation (but note
> : that first part (udelay(50)) has already been applied:
> : 
> : http://marc.theaimsgroup.com/?l=linux-kernel&m=109096903809223&q=raw
> 
> Well acpipnp didn't have any effect.
> 
> I tried the patch above but there's an undefined function, pci_find_class,
> in i8042_spank_usb.  Did it change names?
> 

I think it supposed to be pci_get_class now.

You might want to ask on ACPI list if they have any idea why i8042 is
dead with ACPI activated.

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Vojtech Pavlik]

On Fri, Jan 14, 2005 at 08:31:09PM -0500, Dmitry Torokhov wrote:
> On Friday 14 January 2005 06:06 pm, Matthew Harrell wrote:
> > To qualify that more, the same setup used to compile 2.6.10, 2.6.10-mm2,
> > 2.6.10-mm3, 2.6.11-rc1 only gives me a working keyboard and mouse on the
> > 2.6.10 kernel.
> 
> Hi,
> 
> your scenario is a bit different, it looks like the controller does not want
> to response right from the beginning (while on Roey's box kernel detects both
> keyboard and mouse just fine):
>  
> > ACPI: PS/2 Keyboard Controller [KBC] at I/O 0x60, 0x66, irq 1
> > ACPI: PS/2 Mouse Controller [PS2M] at irq 12
> > i8042.c: Can't read CTR while initializing i8042.
> 
> Could you try booting with acpi=off and without PNP compiled in? And maybe
> with pci=routeirq

I expect the problem to be coming from the fact that the keyboard
controller uses ports 0x60 and 0x64, not 0x66 as ACPI tries to tell us
here.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Matthew Harrell]

: 
: I expect the problem to be coming from the fact that the keyboard
: controller uses ports 0x60 and 0x64, not 0x66 as ACPI tries to tell us
: here.
: 

Interesting - hadn't noticed that.  Is there an easy solution around it that
doesn't entail turning off acpi?

-- 
  Matthew Harrell                          I don't suffer from insanity - 
  Bit Twiddlers, Inc.                       I enjoy every minute of it.
  mharrell@bittwiddlers.com     

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Vojtech Pavlik]

On Mon, Jan 17, 2005 at 02:58:15PM -0500, Matthew Harrell wrote:
> : 
> : I expect the problem to be coming from the fact that the keyboard
> : controller uses ports 0x60 and 0x64, not 0x66 as ACPI tries to tell us
> : here.
> : 
> 
> Interesting - hadn't noticed that.  Is there an easy solution around it that
> doesn't entail turning off acpi?
 
The only one I see would be using "i8042.noacpi=1" on the kernel command
line.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Having disabled ALL mouse functionality (including 'mousedev'), I 
compiled 2.6.9-rc2-bk2.  On bootup, keyboard input worked great.
So many it's a conflict with the mouse driver then.
BTW, I haven an MSI NEO K8T FIS2R motherboard with an athlon64/3200+,
for what it's worth.
I will follow up with logs shortly.


Roey


On Wed, 12 Jan 2005, Dmitry Torokhov wrote:

[snip]
> And what if you do not compile PS/2 mouse support in? Is keyboard still
> dead?
>
[snip]

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Hello again Dmitry,

is there anything new about this issue? any fixes in the kernel?
If you want, I can continue doing the test/debug cycle as before.

Roey


On Wed, 12 Jan 2005, Dmitry Torokhov wrote:

> Date: Wed, 12 Jan 2005 22:42:51 -0500
> From: Dmitry Torokhov <dtor_core@ameritech.net>
> To: linux-kernel@vger.kernel.org
> Cc: Roey Katz <roey@sdf.lonestar.org>
> Subject: Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup
> 
> On Wednesday 12 January 2005 10:19 pm, Roey Katz wrote:
>> Dmitry,
>>
>> I have placed the results of the patched 2.6.9-rc2-bk2 kernel at the
>> following address:
>>
>>    http://roey.freeshell.org/mystuff/kernel/*-20050112
>>
>> As expected, the system was unresponsive to keyboard input.
>
> And what if you do not compile PS/2 mouse support in? Is keyboard still
> dead?
>
>> Regarding your mouse question:
>> How do I test the mouse if they keyboard does not work (is there some
>> way to output the contents of /dev/psaux on startup? I'm not sure anymore
>> what file the mouse data appears in, too)
>>
>
> Install GPM and try moving your mouse after booting into runlevel 3 -
> if cursor moves mouse works.
>
> -- 
> Dmitry
>

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Saturday 12 February 2005 12:50, Roey Katz wrote:
> Hello again Dmitry,
> 
> is there anything new about this issue? any fixes in the kernel?
> If you want, I can continue doing the test/debug cycle as before.
> 

Hi Roey,

I have been looking over your logs one more time and it looks like
there is a small change in i8042 init sequence that I have overlooked
before.

Could you please tell me if booting with i8042.nomux option helps your
keyboard?

Thanks!

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Dmitry,

I fixed the problem by updating my BIOS.  My motherboard is an MSI K8T NEO 
FIS2R with a BIOS from 2004.  I just yesterday flashed the BIOS and now 
kernel 2.6.10 boots and responds to the keyboard fine.

The changelog for the MSI BIOS is here:
http://www.msicomputer.com/support/bios_result.asp?platform=AMD&model=K8T%20Neo-FIS2R/FSR%20(MS-6702)&newsearch=1



Thanks so much!!
Roey

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Roey Katz]

Hello again Dmitry,

sorry about that long and ugly post.  Here's more-precisely-formated one 
(made with diff -u):

http://roey.freeshell.org/mystuff/kernel/diff-against-2.6.7


Thanks again,
Roey

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Marco Cipullo]

Same problem with me. I also have a laptop and I also have the same problem 
started in the same period.

Below my logs and config:
Bye
Marco

kernel: Inspecting /boot/System.map-2.6.11-rc1
kernel: Loaded 23459 symbols from /boot/System.map-2.6.11-rc1.
kernel: Symbols matchkernel version 2.6.11.
kernel: No module symbols loaded -kernel modules not enabled. 
kernel: BIOS-provided physical RAM map:
kernel: 511MB LOWMEM available.
kernel: On node 0 totalpages: 130928
kernel:   DMA zone: 4096 pages, LIFO batch:1
kernel:   Normal zone: 126832 pages, LIFO batch:16
kernel:   HighMem zone: 0 pages, LIFO batch:1
kernel: DMI present.
kernel: ACPI: RSDP (v002 IBM                                   ) @ 0x000f7010
kernel: ACPI: XSDT (v001 IBM    TP-1I    0x00002032  LTP 0x00000000) @ 
0x1ff73397
kernel: ACPI: FADT (v001 IBM    TP-1I    0x00002032 IBM  0x00000001) @ 
0x1ff733e3
kernel: ACPI: SSDT (v001 IBM    TP-1I    0x00002032 MSFT 0x0100000d) @ 
0x1ff73497
kernel: ACPI: ECDT (v001 IBM    TP-1I    0x00002032 IBM  0x00000001) @ 
0x1ff7df54
kernel: ACPI: TCPA (v001 IBM    TP-1I    0x00002032 PTL  0x00000001) @ 
0x1ff7dfa6
kernel: ACPI: BOOT (v001 IBM    TP-1I    0x00002032  LTP 0x00000001) @ 
0x1ff7dfd8
kernel: ACPI: DSDT (v001 IBM    TP-1I    0x00002032 MSFT 0x0100000d) @ 
0x00000000
kernel: ACPI: PM-Timer IO Port: 0x1008
kernel: mapped APIC to ffffd000 (01401000)
kernel: Initializing CPU#0
kernel: Using pmtmr for high-res timesource
kernel: Memory: 515516k/523712k available (1512kkernel code, 7640k reserved, 
684k data, 180k init, 0k highmem)
kernel: Calibrating delay loop... 3915.77 BogoMIPS (lpj=1957888)
kernel: CPU: After generic identify, caps: bfebf9ff 00000000 00000000 00000000 
00000400 00000000 00000000
kernel: CPU: After vendor identify, caps: bfebf9ff 00000000 00000000 00000000 
00000400 00000000 00000000
kernel: CPU: Trace cache: 12K uops, L1 D cache: 8K
kernel: CPU: L2 cache: 512K
kernel: CPU: After all inits, caps: bfebf9ff 00000000 00000000 00000080 
00000400 00000000 00000000
kernel: Intel machine check architecture supported.
kernel: Intel machine check reporting enabled on CPU#0.
kernel: CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
kernel: CPU0: Thermal monitoring enabled
kernel: Enabling fast FPU save and restore... done.
kernel: Enabling unmasked SIMD FPU exception support... done.
kernel: Checking 'hlt' instruction... OK.
kernel: checking if image is initramfs...it isn't (no cpio magic); looks like 
an initrd
kernel: Freeing initrd memory: 156k freed
kernel: NET: Registered protocol family 16
kernel: PCI: PCI BIOS revision 2.10 entry at 0xfd8fe, last bus=8
kernel: PCI: Using configuration type 1
kernel: mtrr: v2.0 (20020519)
kernel: ACPI: Subsystem revision 20041210
kernel: ACPI: Found ECDT
kernel: ACPI: Interpreter enabled
kernel: ACPI: Using PIC for interrupt routing
kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
kernel: PCI: Transparent bridge - 0000:00:1e.0
kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
kernel: ACPI: Embedded Controller [EC] (gpe 28)
kernel: ACPI: Power Resource [PUBS] (on)
kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCI1._PRT]
kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
kernel: pnp: PnP ACPI init
kernel: pnp: PnP ACPI: found 13 devices
kernel: PnPBIOS: Disabled by ACPI
kernel: PCI: Using ACPI for IRQ routing
kernel: ** PCI interrupts are no longer routed automatically.  If this
kernel: ** causes a device to stop working, it is probably because the
kernel: ** driver failed to call pci_enable_device().  As a temporary
kernel: ** workaround, the "pci=routeirq" argument restores the old
kernel: ** behavior.  If this argument makes the device work again,
kernel: ** please email the output of "lspci" to bjorn.helgaas@hp.com
kernel: ** so I can fix the driver.
kernel: Simple Boot Flag at 0x35 set to 0x1
kernel: IBM machine detected. Enabling interrupts during APM calls.
kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
kernel: apm: overridden by ACPI.
kernel: Initializing Cryptographic API
kernel: vesafb: framebuffer at 0xe8000000, mapped to 0xe0880000, using 1875k, 
total 16320k
kernel: vesafb: mode is 800x600x16, linelength=1600, pages=16
kernel: vesafb: protected mode interface info at c000:5613
kernel: vesafb: scrolling: redraw
kernel: vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
kernel: fb0: VESA VGA frame buffer device
kernel: isapnp: Scanning for PnP cards...
kernel: isapnp: No Plug & Play device found
kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing 
enabled
kernel: ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 11 (level, low) -> IRQ 11
kernel: io scheduler noop registered
kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with 
idebus=xx
kernel: ICH3M: IDE controller at PCI slot 0000:00:1f.1
kernel: ACPI: PCI interrupt 0000:00:1f.1[A] -> GSI 11 (level, low) -> IRQ 11
kernel: ICH3M: chipset revision 2
kernel: ICH3M: not 100%% native mode: will probe irqs later
kernel:     ide0: BM-DMA at 0x1860-0x1867, BIOS settings: hda:DMA, hdb:pio
kernel:     ide1: BM-DMA at 0x1868-0x186f, BIOS settings: hdc:DMA, hdd:pio
kernel: Probing IDE interface ide0...
kernel: Probing IDE interface ide1...
kernel: hda: max request size: 128KiB
kernel: hda: 78140160 sectors (40007 MB) w/7898KiB Cache, CHS=65535/16/63, 
UDMA(100)
kernel: hda: cache flushes not supported
kernel:  hda: hda1 hda2 hda3 < hda5 hda6 hda7 >
kernel: mice: PS/2 mouse device common for all mice
kernel: NET: Registered protocol family 2
kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes
kernel: TCP: Hash tables configured (established 32768 bind 32768)
kernel: NET: Registered protocol family 1
kernel: ACPI: (supports S0 S3 S4 S5)
kernel: RAMDISK: Compressed image found at block 0
kernel: EXT3-fs: mounted filesystem with ordered data mode.
kernel: kjournald starting.  Commit interval 5 seconds
kernel: Freeing unusedkernel memory: 180k freed
kernel: ACPI: AC Adapter [AC] (on-line)
kernel: ACPI: Battery Slot [BAT0] (battery present)
kernel: ACPI: Power Button (FF) [PWRF]
kernel: ACPI: Lid Switch [LID]
kernel: ACPI: Sleep Button (CM) [SLPB]
kernel: ibm_acpi: IBM ThinkPad ACPI Extras v0.8
kernel: ibm_acpi: http://ibm-acpi.sf.net/
kernel: ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
kernel: ACPI: Processor [CPU] (supports 8 throttling states)
kernel: ACPI: Thermal Zone [THM0] (54 C)
kernel: ACPI: Video Device [VID] (multi-head: yes  rom: no  post: no)
kernel: usbcore: registered new driver usbfs
kernel: usbcore: registered new driver hub
kernel: USB Universal Host Controller Interface driver v2.2
kernel: ACPI: PCI interrupt 0000:00:1d.0[A] -> GSI 11 (level, low) -> IRQ 11
kernel: uhci_hcd 0000:00:1d.0: Intel Corp. 82801CA/CAM USB (Hub #1)
kernel: PCI: Setting latency timer of device 0000:00:1d.0 to 64
kernel: uhci_hcd 0000:00:1d.0: irq 11, io base 0x1800
kernel: uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
kernel: uhci_hcd 0000:00:1d.0: detected 2 ports
kernel: usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
kernel: usb usb1: default language 0x0409
kernel: usb usb1: Product: Intel Corp. 82801CA/CAM USB (Hub #1)
kernel: usb usb1: Manufacturer: Linux 2.6.11-rc1 uhci_hcd
kernel: usb usb1: SerialNumber: 0000:00:1d.0
kernel: usb usb1: hotplug
kernel: usb usb1: adding 1-0:1.0 (config #1, interface 0)
kernel: usb 1-0:1.0: hotplug
kernel: hub 1-0:1.0: usb_probe_interface
kernel: hub 1-0:1.0: usb_probe_interface - got id
kernel: hub 1-0:1.0: USB hub found
kernel: hub 1-0:1.0: 2 ports detected
kernel: hub 1-0:1.0: standalone hub
kernel: hub 1-0:1.0: no power switching (usb 1.0)
kernel: hub 1-0:1.0: individual port over-current protection
kernel: hub 1-0:1.0: power on to power good time: 2ms
kernel: hub 1-0:1.0: local power source is good
kernel: hub 1-0:1.0: state 5 ports 2 chg 0006 evt 0007
kernel: hub 1-0:1.0: port 1, status 0100, change 0000, 12 Mb/s
kernel: hub 1-0:1.0: port 2, status 0100, change 0000, 12 Mb/s
kernel: ACPI: PCI interrupt 0000:00:1d.1[B] -> GSI 11 (level, low) -> IRQ 11
kernel: uhci_hcd 0000:00:1d.1: Intel Corp. 82801CA/CAM USB (Hub #2)
kernel: PCI: Setting latency timer of device 0000:00:1d.1 to 64
kernel: uhci_hcd 0000:00:1d.1: irq 11, io base 0x1820
kernel: uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
kernel: uhci_hcd 0000:00:1d.1: detected 2 ports
kernel: usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
kernel: usb usb2: default language 0x0409
kernel: usb usb2: Product: Intel Corp. 82801CA/CAM USB (Hub #2)
kernel: usb usb2: Manufacturer: Linux 2.6.11-rc1 uhci_hcd
kernel: usb usb2: SerialNumber: 0000:00:1d.1
kernel: usb usb2: hotplug
kernel: usb usb2: adding 2-0:1.0 (config #1, interface 0)
kernel: usb 2-0:1.0: hotplug
kernel: hub 2-0:1.0: usb_probe_interface
kernel: hub 2-0:1.0: usb_probe_interface - got id
kernel: hub 2-0:1.0: USB hub found
kernel: hub 2-0:1.0: 2 ports detected
kernel: hub 2-0:1.0: standalone hub
kernel: hub 2-0:1.0: no power switching (usb 1.0)
kernel: hub 2-0:1.0: individual port over-current protection
kernel: hub 2-0:1.0: power on to power good time: 2ms
kernel: hub 2-0:1.0: local power source is good
kernel: hub 2-0:1.0: state 5 ports 2 chg 0006 evt 0007
kernel: uhci_hcd 0000:00:1d.1: port 1 portsc 01a3,00
kernel: hub 2-0:1.0: port 1, status 0301, change 0001, 1.5 Mb/s
kernel: ACPI: PCI interrupt 0000:00:1d.2[C] -> GSI 11 (level, low) -> IRQ 11
kernel: uhci_hcd 0000:00:1d.2: Intel Corp. 82801CA/CAM USB (Hub #3)
kernel: PCI: Setting latency timer of device 0000:00:1d.2 to 64
kernel: uhci_hcd 0000:00:1d.2: irq 11, io base 0x1840
kernel: hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x301
kernel: uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
kernel: uhci_hcd 0000:00:1d.2: detected 2 ports
kernel: usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
kernel: usb usb3: default language 0x0409
kernel: usb usb3: Product: Intel Corp. 82801CA/CAM USB (Hub #3)
kernel: usb usb3: Manufacturer: Linux 2.6.11-rc1 uhci_hcd
kernel: usb usb3: SerialNumber: 0000:00:1d.2
kernel: usb usb3: hotplug
kernel: usb usb3: adding 3-0:1.0 (config #1, interface 0)
kernel: usb 3-0:1.0: hotplug
kernel: hub 3-0:1.0: usb_probe_interface
kernel: hub 3-0:1.0: usb_probe_interface - got id
kernel: hub 3-0:1.0: USB hub found
kernel: hub 3-0:1.0: 2 ports detected
kernel: hub 3-0:1.0: standalone hub
kernel: hub 3-0:1.0: no power switching (usb 1.0)
kernel: hub 3-0:1.0: individual port over-current protection
kernel: hub 3-0:1.0: power on to power good time: 2ms
kernel: hub 3-0:1.0: local power source is good
kernel: usb 2-1: new low speed USB device using uhci_hcd and address 2
kernel: uhci_hcd 0000:00:1d.0: suspend_hc
kernel: usb 2-1: skipped 1 descriptor after interface
kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 2-1: default language 0x0409
kernel: usb 2-1: Product: USB Mouse
kernel: usb 2-1: Manufacturer: Logitech
kernel: usb 2-1: hotplug
kernel: usb 2-1: adding 2-1:1.0 (config #1, interface 0)
kernel: usb 2-1:1.0: hotplug
kernel: hub 2-0:1.0: port 2, status 0100, change 0000, 12 Mb/s
kernel: hub 3-0:1.0: state 5 ports 2 chg 0006 evt 0007
kernel: hub 3-0:1.0: port 1, status 0100, change 0000, 12 Mb/s
kernel: hub 3-0:1.0: port 2, status 0100, change 0000, 12 Mb/s
kernel: hub 2-0:1.0: state 5 ports 2 chg 0000 evt 0002
kernel: uhci_hcd 0000:00:1d.2: suspend_hc
kernel: usbcore: registered new driver hiddev
kernel: usbhid 2-1:1.0: usb_probe_interface
kernel: usbhid 2-1:1.0: usb_probe_interface - got id
kernel: input: USB HID v1.10 Mouse [Logitech USB Mouse] on usb-0000:00:1d.1-1
kernel: usbcore: registered new driver usbhid
kernel: /bk/linux-2.6/drivers/usb/input/hid-core.c: v2.0:USB HID core driver
kernel: EXT3 FS on hda5, internal journal
kernel: Adding 511520k swap on /dev/hda6.  Priority:-1 extents:1
kernel: Non-volatile memory driver v1.2
kernel: Linux agpgart interface v0.100 (c) Dave Jones
kernel: agpgart: Detected an Intel i845 Chipset.
kernel: agpgart: Maximum main memory to use for agp memory: 439M
kernel: agpgart: AGP aperture is 64M @ 0xe0000000
kernel: kjournald starting.  Commit interval 5 seconds
kernel: EXT3 FS on hda7, internal journal
kernel: EXT3-fs: mounted filesystem with ordered data mode.
kernel: NTFS driver 2.1.22 [Flags: R/O MODULE].
kernel: NTFS volume version 3.1.
kernel: loop: loaded (max 8 devices)
kernel: hdc: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
kernel: Uniform CD-ROM driver Revision: 3.20
kernel: e100: Intel(R) PRO/100 Network Driver, 3.3.6-k2-NAPI
kernel: e100: Copyright(c) 1999-2004 Intel Corporation
kernel: ACPI: PCI interrupt 0000:02:08.0[A] -> GSI 11 (level, low) -> IRQ 11
kernel: e100: eth0: e100_probe: addr 0xd0200000, irq 11, MAC addr 
00:09:6B:93:2E:5C
kernel: NET: Registered protocol family 17
kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
kernel: CSLIP: code copyright 1989 Regents of the University of California
kernel: PPP generic driver version 2.4.2
kernel: ACPI: PCI interrupt 0000:00:1f.5[B] -> GSI 11 (level, low) -> IRQ 11
kernel: PCI: Setting latency timer of device 0000:00:1f.5 to 64
kernel: intel8x0_measure_ac97_clock: measured 49423 usecs
kernel: intel8x0: clocking to 48000
kernel: Kernel logging (proc) stopped.
kernel: Kernel log daemon terminating.
 





#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11-rc1
# Sat Jan 15 11:06:45 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_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y

#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_EMBEDDED=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
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

#
# 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

#
# 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_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_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
CONFIG_X86_MCE_P4THERMAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
CONFIG_MICROCODE=m
CONFIG_X86_MSR=m
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_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_REGPARM 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_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
# CONFIG_ACPI_ASUS is not set
CONFIG_ACPI_IBM=m
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_CUSTOM_DSDT 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=y
# CONFIG_ACPI_CONTAINER is not set

#
# APM (Advanced Power Management) BIOS Support
#
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
CONFIG_APM_ALLOW_INTS=y
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

#
# CPU Frequency scaling
#
CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_DEBUG=y
# CONFIG_CPU_FREQ_PROC_INTF is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=m
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=y
# CONFIG_CPU_FREQ_24_API is not set
CONFIG_CPU_FREQ_GOV_ONDEMAND=m
CONFIG_CPU_FREQ_TABLE=y

#
# CPUFreq processor drivers
#
CONFIG_X86_ACPI_CPUFREQ=m
# 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=m
CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y
CONFIG_X86_SPEEDSTEP_ICH=m
CONFIG_X86_SPEEDSTEP_SMI=m
CONFIG_X86_P4_CLOCKMOD=m
# 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=m
CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=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_PCI_MSI=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set

#
# PC-card bridges
#
CONFIG_PCMCIA_PROBE=y

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_MISC=m

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_STANDALONE is not set
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
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_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_PC_SUPERIO=y
# CONFIG_PARPORT_OTHER is not set
# CONFIG_PARPORT_1284 is not set

#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set

#
# Protocols
#
CONFIG_ISAPNP=y
CONFIG_PNPBIOS=y
CONFIG_PNPBIOS_PROC_FS=y
CONFIG_PNPACPI=y

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
CONFIG_PARIDE=m
CONFIG_PARIDE_PARPORT=m

#
# Parallel IDE high-level drivers
#
CONFIG_PARIDE_PD=m
CONFIG_PARIDE_PCD=m
CONFIG_PARIDE_PF=m
# CONFIG_PARIDE_PT is not set
CONFIG_PARIDE_PG=m

#
# Parallel IDE protocol modules
#
# CONFIG_PARIDE_ATEN is not set
# CONFIG_PARIDE_BPCK is not set
# CONFIG_PARIDE_BPCK6 is not set
# CONFIG_PARIDE_COMM is not set
# CONFIG_PARIDE_DSTR is not set
# CONFIG_PARIDE_FIT2 is not set
# CONFIG_PARIDE_FIT3 is not set
# CONFIG_PARIDE_EPAT is not set
# CONFIG_PARIDE_EPIA is not set
# CONFIG_PARIDE_FRIQ is not set
# CONFIG_PARIDE_FRPW is not set
# CONFIG_PARIDE_KBIC is not set
# CONFIG_PARIDE_KTTI is not set
# CONFIG_PARIDE_ON20 is not set
# CONFIG_PARIDE_ON26 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_LOOP=m
CONFIG_BLK_DEV_CRYPTOLOOP=m
CONFIG_BLK_DEV_NBD=m
# 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=32000
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_LBD=y
CONFIG_CDROM_PKTCDVD=m
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=m
CONFIG_IOSCHED_DEADLINE=m
CONFIG_IOSCHED_CFQ=m
# 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=m
CONFIG_BLK_DEV_IDETAPE=m
CONFIG_BLK_DEV_IDEFLOPPY=m
CONFIG_BLK_DEV_IDESCSI=m
CONFIG_IDE_TASK_IOCTL=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=m
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_OFFBOARD=y
# 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=y
# CONFIG_IDEDMA_ONLYDISK 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 is not set
# 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=y
CONFIG_HPT34X_AUTODMA=y
CONFIG_BLK_DEV_HPT366=y
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# 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 is not set
# 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_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y

#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_CHR_DEV_SG=m

#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set

#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# 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_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 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_SCSI_IN2000 is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
CONFIG_SCSI_EATA=m
CONFIG_SCSI_EATA_TAGGED_QUEUE=y
# CONFIG_SCSI_EATA_LINKED_COMMANDS is not set
CONFIG_SCSI_EATA_MAX_TAGS=16
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
CONFIG_SCSI_GDTH=m
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_GENERIC_NCR5380_MMIO 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_NCR53C406A is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=m
# 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_SYM53C416 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_ULTRASTOR is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=m
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=m
CONFIG_UNIX=y
CONFIG_NET_KEY=m
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE 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 is not set
# CONFIG_IP_TCPDIAG_IPV6 is not set
# CONFIG_IPV6 is not set
# CONFIG_NETFILTER is not set
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
CONFIG_ATM=m
CONFIG_ATM_CLIP=m
# CONFIG_ATM_CLIP_NO_ICMP is not set
CONFIG_ATM_LANE=m
CONFIG_ATM_MPOA=m
CONFIG_ATM_BR2684=m
CONFIG_ATM_BR2684_IPFILTER=y
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
CONFIG_LLC=m
CONFIG_LLC2=m
# 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

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP 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=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA 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_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_CS89x0 is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=m
CONFIG_E100=m
# CONFIG_E100_NAPI 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
# CONFIG_NET_POCKET 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_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 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 is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# ATM drivers
#
CONFIG_ATM_TCP=m
# CONFIG_ATM_LANAI is not set
# CONFIG_ATM_ENI is not set
# CONFIG_ATM_FIRESTREAM is not set
# CONFIG_ATM_ZATM is not set
# CONFIG_ATM_NICSTAR is not set
# CONFIG_ATM_IDT77252 is not set
# CONFIG_ATM_AMBASSADOR is not set
# CONFIG_ATM_HORIZON is not set
# CONFIG_ATM_IA is not set
# CONFIG_ATM_FORE200E_MAYBE is not set
# CONFIG_ATM_HE 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=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m
CONFIG_PPPOATM=m
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE 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=m
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=m
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PARKBD=m
CONFIG_SERIO_PCIPS2=m
CONFIG_SERIO_LIBPS2=y
CONFIG_SERIO_RAW=m

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=m
# 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=m
CONFIG_MOUSE_SERIAL=m
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_UINPUT=m

#
# 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=y
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
# CONFIG_SERIAL_8250_MANY_PORTS is not set
CONFIG_SERIAL_8250_SHARE_IRQ=y
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_RSA is not set

#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=m
CONFIG_LP_CONSOLE=y
CONFIG_PPDEV=m
# CONFIG_TIPAR is not set

#
# IPMI
#
CONFIG_IPMI_HANDLER=m
CONFIG_IPMI_PANIC_EVENT=y
CONFIG_IPMI_PANIC_STRING=y
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
# CONFIG_IPMI_POWEROFF is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
CONFIG_NVRAM=m
CONFIG_RTC=m
CONFIG_GEN_RTC=m
CONFIG_GEN_RTC_X=y
CONFIG_DTLK=m
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
CONFIG_AGP_INTEL_MCH=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=m
# 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_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
CONFIG_MWAVE=m
CONFIG_RAW_DRIVER=m
CONFIG_HPET=y
CONFIG_HPET_RTC_IRQ=y
CONFIG_HPET_MMAP=y
CONFIG_MAX_RAW_DEVS=256
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m

#
# I2C Algorithms
#
CONFIG_I2C_ALGOBIT=m
CONFIG_I2C_ALGOPCF=m
# CONFIG_I2C_ALGOPCA is not set

#
# I2C Hardware Bus support
#
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_AMD756=m
# CONFIG_I2C_AMD756_S4882 is not set
CONFIG_I2C_AMD8111=m
# CONFIG_I2C_ELEKTOR is not set
CONFIG_I2C_I801=m
CONFIG_I2C_I810=m
CONFIG_I2C_ISA=m
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
CONFIG_I2C_PIIX4=m
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
# CONFIG_SCx200_ACB is not set
CONFIG_I2C_SIS5595=m
CONFIG_I2C_SIS630=m
CONFIG_I2C_SIS96X=m
# CONFIG_I2C_STUB is not set
CONFIG_I2C_VIA=m
CONFIG_I2C_VIAPRO=m
CONFIG_I2C_VOODOO3=m
# CONFIG_I2C_PCA_ISA is not set

#
# Hardware Sensors Chip support
#
CONFIG_I2C_SENSOR=m
CONFIG_SENSORS_ADM1021=m
CONFIG_SENSORS_ADM1025=m
# CONFIG_SENSORS_ADM1026 is not set
CONFIG_SENSORS_ADM1031=m
CONFIG_SENSORS_ASB100=m
CONFIG_SENSORS_DS1621=m
CONFIG_SENSORS_FSCHER=m
CONFIG_SENSORS_GL518SM=m
CONFIG_SENSORS_IT87=m
# CONFIG_SENSORS_LM63 is not set
CONFIG_SENSORS_LM75=m
CONFIG_SENSORS_LM77=m
CONFIG_SENSORS_LM78=m
CONFIG_SENSORS_LM80=m
CONFIG_SENSORS_LM83=m
CONFIG_SENSORS_LM85=m
# CONFIG_SENSORS_LM87 is not set
CONFIG_SENSORS_LM90=m
CONFIG_SENSORS_MAX1619=m
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
# CONFIG_SENSORS_SMSC47M1 is not set
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_W83781D=m
CONFIG_SENSORS_W83L785TS=m
CONFIG_SENSORS_W83627HF=m

#
# Other I2C Chip support
#
CONFIG_SENSORS_EEPROM=m
CONFIG_SENSORS_PCF8574=m
CONFIG_SENSORS_PCF8591=m
CONFIG_SENSORS_RTC8564=m
# 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=m
# CONFIG_W1_MATROX is not set
# CONFIG_W1_DS9490 is not set
CONFIG_W1_THERM=m
# CONFIG_W1_SMEM is not set

#
# Misc devices
#
# CONFIG_IBM_ASM is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
CONFIG_FB=y
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_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
CONFIG_FB_VGA16=m
CONFIG_FB_VESA=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_HGA=m
# CONFIG_FB_HGA_ACCEL is not set
# CONFIG_FB_RIVA is not set
CONFIG_FB_I810=m
# CONFIG_FB_I810_GTF 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_VIRTUAL is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set
# CONFIG_FONT_MINI_4x6 is not set
# CONFIG_FONT_SUN8x16 is not set
# CONFIG_FONT_SUN12x22 is not set

#
# Logo configuration
#
CONFIG_LOGO=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_LOGO_LINUX_VGA16=y
CONFIG_LOGO_LINUX_CLUT224=y

#
# Sound
#
CONFIG_SOUND=m

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
CONFIG_SND_SEQ_DUMMY=m
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
CONFIG_SND_DUMMY=m
CONFIG_SND_VIRMIDI=m
CONFIG_SND_MTPAV=m
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m

#
# ISA devices
#
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# 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 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_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=m
CONFIG_SND_INTEL8X0M=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
CONFIG_SND_VIA82XX_MODEM=m
# CONFIG_SND_VX222 is not set

#
# USB devices
#
CONFIG_SND_USB_AUDIO=m
# CONFIG_SND_USB_USX2Y is not set

#
# Open Sound System
#
CONFIG_SOUND_PRIME=m
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_SOUND_FUSION is not set
# CONFIG_SOUND_CS4281 is not set
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_MAESTRO3 is not set
CONFIG_SOUND_ICH=m
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
# CONFIG_SOUND_VIA82CXXX is not set
CONFIG_SOUND_OSS=m
# CONFIG_SOUND_TRACEINIT is not set
CONFIG_SOUND_DMAP=y
# CONFIG_SOUND_AD1816 is not set
# CONFIG_SOUND_AD1889 is not set
# CONFIG_SOUND_SGALAXY is not set
# CONFIG_SOUND_ADLIB is not set
# CONFIG_SOUND_ACI_MIXER is not set
# CONFIG_SOUND_CS4232 is not set
# CONFIG_SOUND_SSCAPE is not set
# CONFIG_SOUND_GUS is not set
CONFIG_SOUND_VMIDI=m
# CONFIG_SOUND_TRIX is not set
CONFIG_SOUND_MSS=m
CONFIG_SOUND_MPU401=m
# CONFIG_SOUND_NM256 is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_SOUND_PAS is not set
# CONFIG_SOUND_PSS is not set
CONFIG_SOUND_SB=m
# CONFIG_SOUND_AWE32_SYNTH is not set
# CONFIG_SOUND_WAVEFRONT is not set
# CONFIG_SOUND_MAUI is not set
# CONFIG_SOUND_YM3812 is not set
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_OPL3SA2 is not set
# CONFIG_SOUND_YMFPCI is not set
CONFIG_SOUND_UART6850=m
# CONFIG_SOUND_AEDSP16 is not set
# CONFIG_SOUND_TVMIXER is not set
# CONFIG_SOUND_KAHLUA is not set
# CONFIG_SOUND_ALI5455 is not set
# CONFIG_SOUND_FORTE is not set
# CONFIG_SOUND_RME96XX is not set
# CONFIG_SOUND_AD1980 is not set

#
# USB support
#
CONFIG_USB=m
CONFIG_USB_DEBUG=y

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
CONFIG_USB_BANDWIDTH=y
CONFIG_USB_DYNAMIC_MINORS=y
CONFIG_USB_SUSPEND=y
# CONFIG_USB_OTG is not set
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_UHCI_HCD=m
# CONFIG_USB_SL811_HCD is not set

#
# USB Device Class drivers
#
CONFIG_USB_AUDIO=m
CONFIG_USB_BLUETOOTH_TTY=m
CONFIG_USB_MIDI=m
CONFIG_USB_ACM=m
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_RW_DETECT=y
CONFIG_USB_STORAGE_DATAFAB=y
CONFIG_USB_STORAGE_FREECOM=y
CONFIG_USB_STORAGE_ISD200=y
CONFIG_USB_STORAGE_DPCM=y
CONFIG_USB_STORAGE_HP8200e=y
CONFIG_USB_STORAGE_SDDR09=y
CONFIG_USB_STORAGE_SDDR55=y
CONFIG_USB_STORAGE_JUMPSHOT=y

#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
CONFIG_HID_FF=y
CONFIG_HID_PID=y
CONFIG_LOGITECH_FF=y
CONFIG_THRUSTMASTER_FF=y
CONFIG_USB_HIDDEV=y

#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
CONFIG_USB_AIPTEK=m
CONFIG_USB_WACOM=m
CONFIG_USB_KBTAB=m
CONFIG_USB_POWERMATE=m
CONFIG_USB_MTOUCH=m
CONFIG_USB_EGALAX=m
CONFIG_USB_XPAD=m
CONFIG_USB_ATI_REMOTE=m

#
# USB Imaging devices
#
CONFIG_USB_MDC800=m
CONFIG_USB_MICROTEK=m

#
# USB Multimedia devices
#
CONFIG_USB_DABUSB=m

#
# Video4Linux support is needed for USB Multimedia device support
#

#
# USB Network Adapters
#
CONFIG_USB_CATC=m
CONFIG_USB_KAWETH=m
CONFIG_USB_PEGASUS=m
CONFIG_USB_RTL8150=m
CONFIG_USB_USBNET=m

#
# USB Host-to-Host Cables
#
CONFIG_USB_ALI_M5632=y
CONFIG_USB_AN2720=y
CONFIG_USB_BELKIN=y
CONFIG_USB_GENESYS=y
CONFIG_USB_NET1080=y
CONFIG_USB_PL2301=y
CONFIG_USB_KC2190=y

#
# Intelligent USB Devices/Gadgets
#
CONFIG_USB_ARMLINUX=y
CONFIG_USB_EPSON2888=y
CONFIG_USB_ZAURUS=y
CONFIG_USB_CDCETHER=y

#
# USB Network Adapters
#
CONFIG_USB_AX8817X=y

#
# USB port drivers
#
CONFIG_USB_USS720=m

#
# USB Serial Converter support
#
CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_GENERIC=y
CONFIG_USB_SERIAL_BELKIN=m
CONFIG_USB_SERIAL_WHITEHEAT=m
CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m
CONFIG_USB_SERIAL_CYPRESS_M8=m
CONFIG_USB_SERIAL_EMPEG=m
CONFIG_USB_SERIAL_FTDI_SIO=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_IPAQ=m
CONFIG_USB_SERIAL_IR=m
CONFIG_USB_SERIAL_EDGEPORT=m
CONFIG_USB_SERIAL_EDGEPORT_TI=m
CONFIG_USB_SERIAL_GARMIN=m
CONFIG_USB_SERIAL_IPW=m
CONFIG_USB_SERIAL_KEYSPAN_PDA=m
CONFIG_USB_SERIAL_KEYSPAN=m
# CONFIG_USB_SERIAL_KEYSPAN_MPR is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XA is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA28XB is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19 is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA18X is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QW is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA19QI is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49W is not set
# CONFIG_USB_SERIAL_KEYSPAN_USA49WLC is not set
CONFIG_USB_SERIAL_KLSI=m
CONFIG_USB_SERIAL_KOBIL_SCT=m
CONFIG_USB_SERIAL_MCT_U232=m
CONFIG_USB_SERIAL_PL2303=m
CONFIG_USB_SERIAL_SAFE=m
CONFIG_USB_SERIAL_SAFE_PADDED=y
CONFIG_USB_SERIAL_TI=m
CONFIG_USB_SERIAL_CYBERJACK=m
CONFIG_USB_SERIAL_XIRCOM=m
CONFIG_USB_SERIAL_OMNINET=m
CONFIG_USB_EZUSB=y

#
# USB Miscellaneous drivers
#
CONFIG_USB_EMI62=m
CONFIG_USB_EMI26=m
CONFIG_USB_AUERSWALD=m
CONFIG_USB_RIO500=m
CONFIG_USB_LEGOTOWER=m
CONFIG_USB_LCD=m
CONFIG_USB_LED=m
CONFIG_USB_CYTHERM=m
CONFIG_USB_PHIDGETKIT=m
CONFIG_USB_PHIDGETSERVO=m
CONFIG_USB_TEST=m

#
# USB ATM/DSL drivers
#
CONFIG_USB_ATM=m
CONFIG_USB_SPEEDTOUCH=m

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# MMC/SD Card support
#
# CONFIG_MMC is not set

#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
# CONFIG_EXT2_FS_POSIX_ACL is not set
# CONFIG_EXT2_FS_SECURITY is not set
CONFIG_EXT3_FS=m
CONFIG_EXT3_FS_XATTR=y
# CONFIG_EXT3_FS_POSIX_ACL is not set
# CONFIG_EXT3_FS_SECURITY is not set
CONFIG_JBD=m
# CONFIG_JBD_DEBUG is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
CONFIG_ROMFS_FS=m
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=m

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
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_DEVFS_FS is not set
# 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 is not set
# 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 is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS 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=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
# CONFIG_MAC_PARTITION is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_MINIX_SUBPARTITION is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
CONFIG_LDM_PARTITION=y
# CONFIG_LDM_DEBUG is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_ULTRIX_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
# CONFIG_EFI_PARTITION is not set

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_CODEPAGE_852=m
# 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=m
CONFIG_NLS_CODEPAGE_1251=m
CONFIG_NLS_ASCII=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_2=m
# 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=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
CONFIG_NLS_UTF8=m

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
CONFIG_FRAME_POINTER=y
# CONFIG_EARLY_PRINTK is not set
CONFIG_4KSTACKS=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=m
# CONFIG_CRYPTO_MD4 is not set
CONFIG_CRYPTO_MD5=m
# CONFIG_CRYPTO_SHA1 is not set
# CONFIG_CRYPTO_SHA256 is not set
# CONFIG_CRYPTO_SHA512 is not set
# CONFIG_CRYPTO_WP512 is not set
CONFIG_CRYPTO_DES=m
# CONFIG_CRYPTO_BLOWFISH is not set
# CONFIG_CRYPTO_TWOFISH is not set
# 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 is not set
# CONFIG_CRYPTO_KHAZAD is not set
# CONFIG_CRYPTO_ANUBIS is not set
# CONFIG_CRYPTO_DEFLATE is not set
# 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=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[Dmitry Torokhov]

On Saturday 15 January 2005 06:05 am, Marco Cipullo wrote:
> Same problem with me. I also have a laptop and I also have the same problem 
> started in the same period.
> 
...
> #
> # Input I/O drivers
> #
> # CONFIG_GAMEPORT is not set
> CONFIG_SOUND_GAMEPORT=y
> CONFIG_SERIO=y
> CONFIG_SERIO_I8042=m

Make i8042 compiled in or make sure that your init scripts load it. Right now
there are no traces of it in your boot log.

-- 
Dmitry

Re: 2.6.9 & 2.6.10 unresponsive to keyboard upon bootup

[marco]

Dmitry Torokhov ha scritto:
> On Saturday 15 January 2005 06:05 am, Marco Cipullo wrote:
> 
>>Same problem with me. I also have a laptop and I also have the same problem 
>>started in the same period.
>>
> 
> ...
> 
>>#
>># Input I/O drivers
>>#
>># CONFIG_GAMEPORT is not set
>>CONFIG_SOUND_GAMEPORT=y
>>CONFIG_SERIO=y
>>CONFIG_SERIO_I8042=m
> 
> 
> Make i8042 compiled in or make sure that your init scripts load it. Right now
> there are no traces of it in your boot log.
> 
Now it's in.....

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=m
CONFIG_SERIO_CT82C710=m
CONFIG_SERIO_PARKBD=m
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=m
CONFIG_SERIO_RAW=m

....but it doesn't work the same.

Bye
Marco