Skip to contentSkip to conversation

2.6 input drivers FAQ

DISCUSSION Vojtech Pavlik 14 participants 31 messages Feb 1, 2004 – Feb 17, 2004

lore
Share & tools
lore
#0 lore raw

Common problems and solutions with 2.6 input drivers:

Problems:
~~~~~~~~~

How do I get a list of the input devices in my system?
How can I check that the input drivers have found my devices correctly?

Solution:
~~~~~~~~~

'cat /proc/bus/input/devices' and 'dmesg' are your friends here. The first lists all devices known to the input core with their properties, and the latter shows the messages from boot. There you can spot any errors that happened in the probing process.

Problems:
~~~~~~~~~

I'm getting double clicks when I click only once. My scroll wheel scrolls by two lines/screens instead of one. My mouse moves too fast.

Solution:
~~~~~~~~~

Check your XFree86 config file.

You probably have two "mouse" entries there, one pointing to /dev/psaux and the other to /dev/input/mice, so that you can get both your PS/2 and USB mouse working on 2.4.

2.6 uses the input subsystem for both PS2 and USB, and thus both devices will report events from both mice, resulting in doubled events.

Remove either the /dev/psaux or /dev/input/mice entry, depending what suits you better for 2.4 compatibility should you ever need go back to 2.4.

Problems:
~~~~~~~~~

My mouse wheel is not working in X.
My Logitech (MousManPS/2) mouse stopped working in X. My extra buttons don't work in X.

Solution:
~~~~~~~~~

Check your XFree86 config file.

Make sure the mouse protocol is set to "ExplorerPS/2", as that is what the 2.6 kernel exports to applications regardless of the real mouse type.

Make sure you have an "ZAxisMapping 4 5" entry.

Make sure you have an entry for remapping the extra buttons above 5.

Problem:
~~~~~~~~

Kernel reports:

	atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
	atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.

Solution:
~~~~~~~~~

Well, the kernel means what it says. XFree86 boldly goes and accesses the keyboard controller registers when it starts up. This is a bad thing to do, as it can conflict with the kernel using these registers at the same time. The kernel spots this and complains, and in most cases is not affected by the problem.

So, unless you are an XFree86 developer and can fix X, ignore this message.

Problem:
~~~~~~~~

I get the message above, but I'm not running X.

Solution:
~~~~~~~~~

Other applications (for example kbdrate) may also access the keyboard controller. This will trigger the same message.

Fix your application / utility or ignore the message.

Problem:
~~~~~~~~

My multimedia keys don't work at all and instead emit a message like this:

	atkbd.c: Unknown key pressed (translated set 2, code 0x83 on isa0060/serio0).
	atkbd.c: Use 'setkeycodes e003 <keycode>' to make it known.
	atkbd.c: Unknown key released (translated set 2, code 0x83 on isa0060/serio0).
	atkbd.c: Use 'setkeycodes e003 <keycode>' to make it known.

Solution:
~~~~~~~~~

Do what the kernel says. Use the setkeycodes utility with the suggested scncode value. For the keycode value, look into /usr/include/linux/input.h, where is a list of all defined Linux keycodes.

Then you can verify that the keyboard works correctly by using the evtest program:

evtest /dev/input/event#

Where # is the number of the input device that is your keyboard.

Problem:
~~~~~~~~

setkeycodes refuses to work with keycodes above 127.

Solution:
~~~~~~~~~

Get a recent version of kbd-utils, and recompile on a 2.6 kernel.

Problem:
~~~~~~~~

Ok, evtest shows everything correctly, but I get incorrect keysyms assigned to these keys in XFree86.

Solution:
~~~~~~~~~

While the 2.6 kernel tries to use the "standard" scancodes as much as possible, it is not posible for all keys.

A good solution is to modify the XKB keyboard definition to match the scancodes one can obtain from 'showkeys -s', after the above problem is solved and the keys work in evtest.

An better solution would be to write a kernel-2.6 keyboard definition, as the scancodes are the same for every type of keyboard, independend of the hardware. This is called hardware abstraction.

A perfect solution would be to get X to use the event protocol. If you're an XFree86 developer, you might consider this.

Problem:
~~~~~~~~

My PC Speaker is not beeping anymore in 2.6.

Solution:
~~~~~~~~~

Enable it in the kernel config. Go to Drivers->Input->Misc->PC Speaker.

Problem:
~~~~~~~~

My Synaptics touchpad lost the ability of tap-to-click, scroll, etc.

Solution:
~~~~~~~~~

The easy solution is to pass psmouse.proto=imps on the kernel command line, or proto=imps on the psmouse module command line. This will restore 2.4 behavior.

A better solution is to download the new XFree86 Synaptics driver that cooperates with the input drivers nicely, from:

	http://w1.894.telia.com/~u89404340/touchpad/index.html

This will allow you to configure the behavior of the touchpad in detail and give you all the features it can do, including palm detection and similar.

In case you want to get this running at the console, too, an updated GPM package can be found here:

http://www.geocities.com/dt_or/gpm/gpm.html

Problem:
~~~~~~~~

When I switch my KVM, my PS/2 mouse goes all crazy.

Solution:
~~~~~~~~~

Use psmouse.proto=bare on the kernel command line, or proto=bare on the psmouse module command line.

Problem:
~~~~~~~~

I'm getting these:

psmouse.c: PS/2 mouse at serio0 lost synchronization, throwing 2 bytes away.

Solution:
~~~~~~~~~

Check your mouse cable. If this only happens when you move your mouse in a certain way, fix the mouse cable or replace the mouse.

Check your kernel and harddisk settings. This message can also happen when the mouse interrupt is delayed more than one half of a second. Make sure DMA is enabled for your harddrive and CD-ROM. Kill your ACPI/APM battery monitoring applet. Try disabling ACPI, frequency scaling. Make sure your time is ticking correctly, often with frequency scaling it gets unreliable. Even if you're using the ACPI PM Timer as a clock source - actually this often leads to the above problem.

Problem:
~~~~~~~~

My keyboard autorepeat is not as snappy as it used to be in the 2.5 series.

Solution:
~~~~~~~~~

Use atkbd.softrepeat=1 on the kernel command line, or "softrepeat=1" on atkbd module command line. This will enable kernel internal repeat generation, which is much more flexible and allows higher repeat rates and shorter repeat delays than the keyboard itself does.

Problem:
~~~~~~~~

kbdrate doesn't work when I use atkbd.softrepeat.

Solution:
~~~~~~~~~

Get an up-to-date version of kbd-utils. Recompile on 2.6.

Problem:
~~~~~~~~

I've read through the whole file, and it did not help me at all!

Solution:
~~~~~~~~~

Either you didn't have any problem in the first place, or it's something that is not very often and thus not listed. Try contacting the driver author/maintainer, the kernel mailing list, or enter the problem into the Linux kernel bugzilla.

#1 lore raw
Quoted 1 line · Vojtech Pavlik

Common problems and solutions with 2.6 input drivers:

Good!

Quoted 1 line

Get a recent version of kbd-utils, and recompile on a 2.6 kernel.

Is there something called kbd-utils?
I maintain the kbd package. Maybe recent versions will work on both 2.4 and 2.6, regardless where they were compiled.

(Send bug reports to [email protected])

Andries

#2 lore raw
Quoted 6 lines · Andries Brouwer
Quoted 1 line · Vojtech Pavlik

Common problems and solutions with 2.6 input drivers:

Good!

Quoted 7 lines
Quoted 1 line

Get a recent version of kbd-utils, and recompile on a 2.6 kernel.

Is there something called kbd-utils?
I maintain the kbd package. Maybe recent versions will work on both 2.4 and 2.6, regardless where they were compiled.

(Send bug reports to [email protected])

Sorry. I was typing that from memory. I'll fix it. Btw, could you make the kbd package accept scancodes in the 0x80-0xff range (same as e000 to e07f), if it is not yet there? And how about scancodes in the 0x100-0x1ff range? Will those work?

One more question: Will kbdrate work properly (use ioctls) when compiled on a 2.6 kernels?

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#6 lore raw
In reply to Andries Brouwer

Andries,

Quoted 9 lines · Andries Brouwer
Quoted 1 line · Vojtech Pavlik

Common problems and solutions with 2.6 input drivers:

Good!

Quoted 1 line

Get a recent version of kbd-utils, and recompile on a 2.6 kernel.

on both 2.4 and 2.6, regardless where they were compiled.

ON Fedora development (around 30 jan)

% rpm -qf /usr/bin/setkeycodes
kbd-1.08-12

% /usr/bin/setkeycodes e001 130
setkeycode: code outside bounds
usage: setkeycode scancode keycode ...
(where scancode is either xx or e0xx, given in hexadecimal,
and keycode is given in decimal)

-Marcel

Signature · 6 lines
     ======--------         Marcel J.E. Mol                MESA Consulting B.V.
    =======---------        ph. +31-(0)6-54724868          P.O. Box 112
    =======---------        [email protected]                 2630 AC  Nootdorp
__==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
 They couldn't think of a number,           Linux user 1148  --  counter.li.org
    so they gave me a name!  -- Rupert Hine  --  www.ruperthine.com
#3 lore raw
In reply to Vojtech Pavlik
Quoted 4 lines · Vojtech Pavlik

Sorry. I was typing that from memory. I'll fix it. Btw, could you make the kbd package accept scancodes in the 0x80-0xff range (same as e000 to e07f), if it is not yet there? And how about scancodes in the 0x100-0x1ff range? Will those work?

What is needed for the 2.6 kernel is rather volatile (and maybe the present kernel version is not quite final yet). But setkeycodes does ioctl(fd,KDSETKEYCODE,&a) where

                a.keycode = atoi(argv[2]);
                a.scancode = strtol(argv[1], &ep, 16);
                if (a.scancode >= 0xe000) {
                        a.scancode -= 0xe000;
                        a.scancode += 128;      /* some kernels needed +256 */
                }

The 2.6.1 kernel is still very messy, with code

        if (atkbd->emul) {
                if (--atkbd->emul)
                        goto out;
                code |= (atkbd->set != 3) ? 0x80 : 0x100;
        }

where the representation of the e0 prefix depends on the current scancode mode. A bad idea.

Quoted 2 lines

One more question: Will kbdrate work properly (use ioctls) when compiled on a 2.6 kernels?

kbdrate first tries the KDKBDREP ioctl, then the KIOCSRATE ioctl, and if both fail it will try to write to /dev/port.

Andries

#7 lore raw
In reply to Marcel J.E. Mol
Quoted 9 lines · Marcel J.E. Mol

Andries,

ON Fedora development (around 30 jan)

% rpm -qf /usr/bin/setkeycodes
kbd-1.08-12

% /usr/bin/setkeycodes e001 130
setkeycode: code outside bounds

Yes. Try kbd-1.12.

#8 lore raw
In reply to Vojtech Pavlik

And what about dell latitude laptops (synaptics touchpad - works fine - plus that mouse stick - no reaction at all?

Usualy I'm fine with the touchpad, but some people prefer to use the stick or both. Any idea?

devices: (plus pcspeaker and keyboard):
I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1
B: EV=b
B: KEY=6420 0 670000 0 0 0 0 0 0 0 0
B: ABS=11000003

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=synaptics-pt/serio0/input0
H: Handlers=mouse1 event2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

XF86Config:
Section "InputDevice"

        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "ExplorerPS/2"
        Option      "Device" "/dev/input/mouse0"
        Option      "Emulate3Buttons" "on"

EndSection

config:
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
CONFIG_INPUT_UINPUT=y

Andreas

#9 lore raw
Quoted 5 lines · Andreas Jellinghaus

And what about dell latitude laptops (synaptics touchpad - works fine - plus that mouse stick - no reaction at all?

Usualy I'm fine with the touchpad, but some people prefer to use the stick or both. Any idea?

X isn't reading from /dev/input/mouse1, which is where the events for the stick go in your case. You need to add another InputDevice to your X config or use the /dev/input/mice device node.

Quoted 25 lines

devices: (plus pcspeaker and keyboard):
I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1
B: EV=b
B: KEY=6420 0 670000 0 0 0 0 0 0 0 0
B: ABS=11000003

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=synaptics-pt/serio0/input0
H: Handlers=mouse1 event2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

XF86Config:
Section "InputDevice"

        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "ExplorerPS/2"
        Option      "Device" "/dev/input/mouse0"
        Option      "Emulate3Buttons" "on"

EndSection

Signature · 2 lines
Peter Osterlund - [email protected]
http://w1.894.telia.com/~u89404340
#12 lore raw
In reply to Vojtech Pavlik
Quoted 1 line · Vojtech Pavlik

I'm getting double clicks when I click only once.

I get these spuriously and i'm using only /dev/input/mice in my config flie.

Signature · 1 line
Joshua Kwan
#10 lore raw
In reply to Peter Osterlund
Quoted 11 lines · Peter Osterlund
Quoted 5 lines · Andreas Jellinghaus

And what about dell latitude laptops (synaptics touchpad - works fine - plus that mouse stick - no reaction at all?

Usualy I'm fine with the touchpad, but some people prefer to use the stick or both. Any idea?

X isn't reading from /dev/input/mouse1, which is where the events for the stick go in your case. You need to add another InputDevice to your X config or use the /dev/input/mice device node.

ah, stupid me. Thanks, now it is working.

Regards, Andreas

#13 lore raw
In reply to Joshua Kwan
Quoted 5 lines · Joshua Kwan
Quoted 1 line · Vojtech Pavlik

I'm getting double clicks when I click only once.

I get these spuriously and i'm using only /dev/input/mice in my config flie.

In years past, the mouse double-click for a single click syndrome was caused by the pushbutton switch in the mouse becoming unsoldered, as in a microscopic crack in the solder you had to use a strong glass to see around the switches pin in the puddle of solder. Holding the switch solidly against the board and resoldering fixed it right up.

Not for folks who don't know which end of the soldering iron gets hot...

What was happening is that the switch would close and send the event, but the finger then pushed the switch down against the board anotheer thousandth, causeing the pin to rise slightly on the bottom of the board, breaking the solder connection, which sent that event as a button rise, and the situation was then reversed as the finger came back up, giving 2 full clicks for one push.

Signature · 8 lines
Cheers, Gene
"There are four boxes to be used in defense of liberty: soap,
ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
#11 lore raw
In reply to Andreas Jellinghaus
Quoted 15 lines · Andreas Jellinghaus

And what about dell latitude laptops (synaptics touchpad - works fine - plus that mouse stick - no reaction at all?

Usualy I'm fine with the touchpad, but some people prefer to use the stick or both. Any idea?

devices: (plus pcspeaker and keyboard):
I: Bus=0011 Vendor=0002 Product=0007 Version=0000
N: Name="SynPS/2 Synaptics TouchPad"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0 event1
B: EV=b
B: KEY=6420 0 670000 0 0 0 0 0 0 0 0
B: ABS=11000003

Quoted 7 lines

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=synaptics-pt/serio0/input0
H: Handlers=mouse1 event2
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

This means both the touchpad and the touchpoint were found correctly. Can you supply your 'dmesg'? Best contact Dmitry Torokhov about this - he's the Synaptics expert.

Quoted 37 lines

XF86Config:
Section "InputDevice"

        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Protocol" "ExplorerPS/2"
        Option      "Device" "/dev/input/mouse0"
        Option      "Emulate3Buttons" "on"

EndSection

config:
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_EVDEV=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=y
CONFIG_INPUT_UINPUT=y

Andreas

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#25 lore raw

Re: 2.6 input drivers FAQ (ir-kbd-gpio.ko)

In reply to Vojtech Pavlik
Quoted 5 lines · Vojtech Pavlik

Common problems and solutions with 2.6 input drivers:
Problem:
~~~~~~~~
I've read through the whole file, and it did not help me at all!

The following is not a problem, but a question I have been unable to answer by myself. Is with respect to the recent addition of "input layer based support for infrared remote controls", mainly for use with TV tuner cards based on bttv.

Gerd Knorr did the patch that was integrated into mainstream as ChangeSet 1.1474.131.296, and I was trying to use the new standard driver instead of the ported one from 2.4.x, which I got from LIRC mailinglists, and has been working OK with 2.5.x and 2.6.x.

If I load the new kernel modules ir_kbd_gpio and ir_common I get in the logs:
ir-kbd-gpio: bttv IR (card=41) detected at pci-0000:00:0b.0/ir0

And from /proc/bus/input/devices:
I: Bus=0001 Vendor=1461 Product=0001 Version=0001
N: Name="bttv IR (card=41)"
P: Phys=pci-0000:00:0b.0/ir0
H: Handlers=kbd event3
B: EV=100003
B: KEY=c304 80100040 0 0 30000 0 2008000 80 1 9e0000 7bb80 0 0

So everything seems to be detected OK. But when I start lircd 0.6.6-7, it seems to come up fine, but as soon as any application tries to get keypresses from /dev/lirc the daemon exists, because of:
could not open /dev/lirc

So it seems the new kernel driver for TV capture card based remote controls doesn't use /dev/lirc as the place to "send" events from which applications read them.

I have downloaded LIRC from CVS (0.7.0pre1), tried to compile it with little overall success, and started "lircd --device=/dev/lircd --nodaemon". Next I started "irw" to show "keypresses" on the screen, and the daemon doesn't complain, but nothing seems to be received neither.

So the question is, is something unusual needed to make the remote work with the recently added ir-kbd-gpio.ko ?.

Greetings.

Signature · 2 lines
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Sid (Linux 2.6.2-bk3)
#15 lore raw
In reply to Joshua Kwan
Quoted 5 lines · Joshua Kwan
Quoted 1 line · Vojtech Pavlik

I'm getting double clicks when I click only once.

I get these spuriously and i'm using only /dev/input/mice in my config flie.

OK.. and here I thought I was getting senile or Mozilla was buggy. Every once in a while (a few times a day at most) I'd middle-click a link to open it in a new tab, and get 2 tabs.

It may affect left-button as well, I don't often do things where a single or double left-click produce different noticably results.

#16 lore raw
Quoted 8 lines · On Mon, Feb 02, 2004 at 12:27:57AM -0500, [email protected] wrote:
Quoted 5 lines · Joshua Kwan
Quoted 1 line · Vojtech Pavlik

I'm getting double clicks when I click only once.

I get these spuriously and i'm using only /dev/input/mice in my config flie.

Quoted 6 lines

OK.. and here I thought I was getting senile or Mozilla was buggy. Every once in a while (a few times a day at most) I'd middle-click a link to open it in a new tab, and get 2 tabs.

It may affect left-button as well, I don't often do things where a single or double left-click produce different noticably results.

Are you sure you don't have the mouse configured twice in XFree86 config? It's a rather common error.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#23 lore raw
In reply to Joshua Kwan
Quoted 5 lines · Joshua Kwan
Quoted 1 line · Vojtech Pavlik

I'm getting double clicks when I click only once.

I get these spuriously and i'm using only /dev/input/mice in my config flie.

Can yo send me the XF86Config file, dmesg, /proc/bus/input/devices, etc, so that we can debug this?

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#24 lore raw
Quoted 2 lines · Vojtech Pavlik

Can yo send me the XF86Config file, dmesg, /proc/bus/input/devices, etc, so that we can debug this?

Gladly, see attached:

devices.txt - content of /proc/bus/input/devices
XF86Config-4 - duh
dmesg.txt - output of dmesg
config.txt - kernel config

If you need any more information contact me again.

Signature · 1 line
Joshua Kwan

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

I: Bus=0003 Vendor=045e Product=0040 Version=0300
N: Name="Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)"
P: Phys=usb-0000:00:02.0-1/input0
H: Handlers=mouse0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=103

I: Bus=0003 Vendor=046d Product=c216 Version=3600
N: Name="Logitech Logitech Dual Action"
P: Phys=usb-0000:00:02.1-1/input0
H: Handlers=js0
B: EV=b
B: KEY=fff 0 0 0 0 0 0 0 0 0
B: ABS=30027

Linux version 2.6.1-rc1-mm2 (joshk@darjeeling) (gcc version 3.3.3 20031229 (prerelease) (Debian)) #4 Mon Jan 5 17:12:58 PST 2004 BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001fff0000 (usable)
BIOS-e820: 000000001fff0000 - 000000001fff3000 (ACPI NVS)
BIOS-e820: 000000001fff3000 - 0000000020000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
511MB LOWMEM available.
On node 0 totalpages: 131056
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 126960 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
DMI 2.2 present.
ACPI: RSDP (v000 Nvidia ) @ 0x000f6f50
ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3000
ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff3040
ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x1fff7880
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
Building zonelist for node : 0
Kernel command line: auto BOOT_IMAGE=Linux root=302 video=radeonfb:1024x768-32@60
current: c0388a60
current->thread_info: c03d8000
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 1830.134 MHz processor.
Using tsc for high-res timesource
Console: colour VGA+ 80x25
Memory: 514836k/524224k available (2214k kernel code, 8644k reserved, 691k data, 352k init, 0k highmem) zapping low mappings.
Calibrating delay loop... 3620.86 BogoMIPS

Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU:     After generic identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU:     After vendor identify, caps: 0383fbff c1c3fbff 00000000 00000000
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU:     After all inits, caps: 0383fbff c1c3fbff 00000000 00000020

Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU: AMD Athlon(tm) XP 2500+ stepping 00
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xfb590, last bus=2
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20031203
ACPI: IRQ9 SCI: Edge set to Level Trigger.
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (00:00)
PCI: Probing PCI hardware (bus 00)
PCI: disabling nForce2 Halt Disconnect and Stop Grant Disconnect
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [APC1] (IRQs *16)
ACPI: PCI Interrupt Link [APC2] (IRQs 17)
ACPI: PCI Interrupt Link [APC3] (IRQs 18)
ACPI: PCI Interrupt Link [APC4] (IRQs *19)
ACPI: PCI Interrupt Link [APC5] (IRQs 16)
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCS] (IRQs *23)
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22)
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22)
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Scanning system for PnP BIOS support...
PnPBIOS: Found PnP BIOS installation structure at 0xc00fbfe0
PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0xc010, dseg 0xf0000
PnPBIOS: 16 nodes reported by PnP BIOS; 16 recorded by driver
SCSI subsystem initialized
drivers/usb/core/usb.c: registered new driver usbfs drivers/usb/core/usb.c: registered new driver hub
ACPI: PCI Interrupt Link [LSMB] enabled at IRQ 12
ACPI: PCI Interrupt Link [LUBA] enabled at IRQ 11
ACPI: PCI Interrupt Link [LUBB] enabled at IRQ 5
ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 12
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 11
ACPI: PCI Interrupt Link [LACI] enabled at IRQ 11
ACPI: PCI Interrupt Link [LNK1] enabled at IRQ 12
ACPI: PCI Interrupt Link [LNK4] enabled at IRQ 5
PCI: Using ACPI for IRQ routing
PCI: if you experience problems, try using option 'pci=noacpi' or even 'acpi=off' radeonfb_pci_register BEGIN
radeonfb: ref_clk=2700, ref_div=60, xclk=18300 from BIOS
radeonfb: probed DDR SGRAM 65536k videoram
radeon_get_moninfo: bios 4 scratch = 0
radeonfb: ATI Radeon QD DDR SGRAM 64 MB
radeonfb: CRT port CRT monitor connected
radeonfb_pci_register END
Machine check exception polling timer started.
ikconfig 0.7 with /proc/config*
udf: registering filesystem
ACPI: Power Button (FF) [PWRF]
ACPI: Sleep Button (CM) [SLPB]
ACPI: Fan [FAN] (on)
ACPI: Processor [CPU0] (supports C1)
ACPI: Thermal Zone [THRM] (40 C)
hStart = 1032, hEnd = 1176, hTotal = 1344
vStart = 771, vEnd = 777, vTotal = 806
h_total_disp = 0x7f00a7 hsync_strt_wid = 0x920405
v_total_disp = 0x2ff0325 vsync_strt_wid = 0x860302
post div = 0x2
fb_div = 0x121
ppll_div_3 = 0x10121
ron = 2688, roff = 20160
vclk_freq = 6503, per = 720
Console: switching to colour frame buffer device 128x48
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected NVIDIA nForce2 chipset
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: AGP aperture is 64M @ 0xe8000000
[drm] Initialized radeon 1.9.0 20020828 on minor 0
Hangcheck: starting hangcheck timer 0.5.0 (tick is 180 seconds, margin is 60 seconds).
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 [PCSPP,TRISTATE]
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
Using anticipatory io scheduler
FDC 0 is a post-1991 82077
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller

    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA

hda: WDC WD800JB-00ETA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: Hewlett-Packard CD-Writer Plus 8200, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 1024KiB
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
hdc: ATAPI 24X CD-ROM CD-R/RW drive, 2048kB Cache, DMA
Uniform CD-ROM driver Revision: 3.20
Console: switching to colour frame buffer device 128x48
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
Advanced Linux Sound Architecture Driver Version 0.9.7 (Thu Sep 25 19:16:36 2003 UTC). ALSA device list:
No soundcards found.
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
ACPI: (supports S0 S1 S4 S5)
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 352k freed
Adding 1502036k swap on /dev/hda7. Priority:-1 extents:1
EXT3 FS on hda2, internal journal
hostap_crypt: registered algorithm 'NULL'
hostap_plx: CVS (Jouni Malinen <[email protected]>)
PLX9052 PCI/PCMCIA adapter: mem=0xee000000, plx_io=0x9000, irq=12, pccard_io=0x9400
hostap_plx: CIS: 01 03 00 00 ff 17 ...
hostap_plx: manfid=0x0156, 0x0002
hostap_plx: cor_index=0x1 cor_offset=0x3e0
Prism2/2.5 PC Card detected in PLX9052 adapter
PLX_INTCSR=0x1063
PLX_CNTRL=0x180066d2 (Serial EEPROM present=1)
hostap_plx: Registered netdevice wifi0
prism2_hw_init: initialized in 107 ms
wifi0: NIC: id=0x8002 v1.0.0
wifi0: PRI: id=0x15 v0.3.0
wifi0: STA: id=0x1f v1.4.9
wifi0: defaulting to bogus WDS frame as a workaround for firmware bug in Host AP mode WDS
wifi0: registered netdevice wlan0
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.19.
PCI: Setting latency timer of device 0000:00:04.0 to 64
eth0: forcedeth.c: subsystem: 01297:0531
PCI: Setting latency timer of device 0000:00:06.0 to 64
intel8x0_measure_ac97_clock: measured 49459 usecs
intel8x0: clocking to 47480
ehci_hcd 0000:00:02.2: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: irq 12, pci mem e4905000
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-13
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2003 Oct 13 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: irq 11, pci mem e4952000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ohci_hcd 0000:00:02.1: OHCI Host Controller
PCI: Setting latency timer of device 0000:00:02.1 to 64
ohci_hcd 0000:00:02.1: irq 5, pci mem e4954000
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 3 ports detected
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
hub 2-0:1.0: new USB device on port 1, assigned address 2
input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:02.0-1 hub 3-0:1.0: new USB device on port 1, assigned address 2
input: USB HID v1.10 Joystick [Logitech Logitech Dual Action] on usb-0000:00:02.1-1
prism2: wlan0: operating mode changed 3 -> 2
wifi0: TXEXC - status=0x0004 ([Discon]) tx_control=000c
retry_count=0 tx_rate=0 fc=0x0108 (Data::0 ToDS)
A1=00:00:00:00:00:00 A2=00:90:d1:07:e7:bc A3=ff:ff:ff:ff:ff:ff A4=00:00:00:00:00:00
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:05:5d:ee:5c:d4
wifi0: LinkStatus=1 (Connected)
wifi0: LinkStatus: BSSID=00:05:5d:ee:5c:d4
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
lp0: using parport0 (polling).
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode
agpgart: Putting AGP V2 device at 0000:02:00.0 into 1x mode
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
wlan0: no IPv6 routers present
spurious 8259A interrupt: IRQ7.
hub 2-0:1.0: new USB device on port 2, assigned address 3
usb 2-2: USB disconnect, address 3
hub 2-0:1.0: new USB device on port 2, assigned address 4
drivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005 drivers/usb/core/usb.c: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver

# XF86Config-4 (XFree86 X server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. #
# Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades *only*

# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4 > /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86

Section "Files"

	FontPath	"unix/:7100"			# local font server
	# if the local font server has problems, we can fall back on these
	FontPath	"/usr/lib/X11/fonts/Type1"
	FontPath	"/usr/lib/X11/fonts/CID"
	FontPath	"/usr/lib/X11/fonts/Speedo"
	FontPath	"/usr/lib/X11/fonts/misc"
	FontPath	"/usr/lib/X11/fonts/cyrillic"
	FontPath	"/usr/lib/X11/fonts/100dpi"
	FontPath	"/usr/lib/X11/fonts/75dpi"

EndSection

Section "Module"

	Load	"GLcore"
	Load	"bitmap"
	Load	"dbe"
	Load	"ddc"
	Load	"dri"
	Load	"extmod"
	Load	"freetype"
	Load	"glx"
	Load	"int10"
	Load	"record"
	Load	"speedo"
	Load	"type1"
	Load	"vbe"

EndSection

Section "InputDevice"

	Identifier	"Generic Keyboard"
	Driver		"keyboard"
	Option		"CoreKeyboard"
	Option		"XkbRules"	"xfree86"
	Option		"XkbModel"	"pc104"
	Option		"XkbLayout"	"us"

EndSection

Section "InputDevice"

	Identifier	"Generic Mouse"
	Driver		"mouse"
	Option		"SendCoreEvents"	"true"
	Option		"Device"		"/dev/input/mice"
	Option		"Protocol"		"ImPS/2"
	Option		"ZAxisMapping"		"4 5"

EndSection

Section "Device"

	Identifier	"ATI Technologies, Inc. Radeon [QD]"
	Driver		"ati"

EndSection

Section "Monitor"

	Identifier	"Generic Monitor"
	HorizSync	30-60
	VertRefresh	50-75
	Option		"DPMS"

EndSection

Section "Screen"

	Identifier	"Default Screen"
	Device		"ATI Technologies, Inc. Radeon [QD]"
	Monitor		"Generic Monitor"
	DefaultDepth	24
	SubSection "Display"
		Depth		1
		Modes		"1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		4
		Modes		"1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		8
		Modes		"1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		15
		Modes		"1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		16
		Modes		"1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth		24
		Modes		"1024x768" "800x600" "640x480"
	EndSubSection

EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Generic Mouse" "CorePointer"
EndSection

Section "DRI"

	Mode	0666

EndSection

#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
# CONFIG_STANDALONE is not set
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
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

#
# Processor support
#

#
# Select all processors your kernel should support #
# CONFIG_CPU_386 is not set
# CONFIG_CPU_486 is not set
# CONFIG_CPU_586 is not set
# CONFIG_CPU_586TSC is not set
# CONFIG_CPU_586MMX is not set
# CONFIG_CPU_686 is not set
# CONFIG_CPU_PENTIUMII is not set
# CONFIG_CPU_PENTIUMIII is not set
# CONFIG_CPU_PENTIUMM is not set
# CONFIG_CPU_PENTIUM4 is not set
# CONFIG_CPU_K6 is not set
CONFIG_CPU_K7=y
# CONFIG_CPU_K8 is not set
# CONFIG_CPU_CRUSOE is not set
# CONFIG_CPU_WINCHIPC6 is not set
# CONFIG_CPU_WINCHIP2 is not set
# CONFIG_CPU_WINCHIP3D is not set
# CONFIG_CPU_CYRIXIII is not set
# CONFIG_CPU_VIAC3_2 is not set CONFIG_CPU_ONLY_K7=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_USE_3DNOW=y
# CONFIG_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set # CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_X86_UP_APIC is not set CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# 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_SOFTWARE_SUSPEND is not set
# CONFIG_PM_DISK 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=y
CONFIG_ACPI_BATTERY=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_FAN=y
CONFIG_ACPI_PROCESSOR=y
CONFIG_ACPI_THERMAL=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# 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_ACPI_RELAXED_AML is not set
# CONFIG_X86_PM_TIMER is not set

#
# APM (Advanced Power Management) BIOS Support
#
# CONFIG_APM is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
# CONFIG_HOTPLUG is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m

#
# Device Drivers
#

#
# Generic Driver Options
#

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=y
# CONFIG_PARPORT_SERIAL is not set
# CONFIG_PARPORT_PC_FIFO is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play support
#

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_LBD 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_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
# CONFIG_IDE_GENERIC is not set
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# 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_IDEDMA_PCI_WIP is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
CONFIG_BLK_DEV_AMD74XX=y
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_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_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
CONFIG_SCSI=y
# CONFIG_SCSI_PROC_FS is not set

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

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

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX_CONFIG=y
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA23XX is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set

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

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

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

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Macintosh device drivers
#

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN 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_IPV6=m
# CONFIG_IPV6_PRIVACY is not set
# CONFIG_INET6_AH is not set
# CONFIG_INET6_ESP is not set
# CONFIG_INET6_IPCOMP is not set
# CONFIG_IPV6_TUNNEL is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=m
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

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

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
CONFIG_FORCEDETH=m
# CONFIG_DGRS is not set
# CONFIG_EEPRO100 is not set
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
CONFIG_NET_RADIO=y

#
# Obsolete Wireless cards support (pre-802.11)
#
# CONFIG_STRIP is not set

#
# Wireless 802.11b ISA/PCI cards support
#
# CONFIG_AIRO is not set
CONFIG_HERMES=m
CONFIG_PLX_HERMES=m
# CONFIG_TMD_HERMES is not set
# CONFIG_PCI_HERMES is not set
CONFIG_NET_WIRELESS=y

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# Bluetooth support
#
# CONFIG_BT is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL 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=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
CONFIG_GAMEPORT=m
CONFIG_SOUND_GAMEPORT=m
CONFIG_GAMEPORT_NS558=m
# CONFIG_GAMEPORT_L4 is not set
# CONFIG_GAMEPORT_EMU10K1 is not set
# CONFIG_GAMEPORT_VORTEX is not set
# CONFIG_GAMEPORT_FM801 is not set
# CONFIG_GAMEPORT_CS461x is not set
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
CONFIG_INPUT_JOYSTICK=y
CONFIG_JOYSTICK_ANALOG=m
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDDLER is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_INPUT_JOYDUMP is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
CONFIG_SERIAL_8250=y
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set

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

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

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

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# 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 is not set
CONFIG_AGP_NVIDIA=y
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HANGCHECK_TIMER=y

#
# I2C support
#
# CONFIG_I2C 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_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_VIDEO_SELECT is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_MATROX is not set
CONFIG_FB_RADEON=y
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY 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_PCI_CONSOLE=y
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

#
# Logo configuration
#
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
# CONFIG_LOGO_LINUX_CLUT224 is not set
CONFIG_LOGO_DEBIAN_CLUT224=y

#
# Sound
#
CONFIG_SOUND=y

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

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 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_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# ALSA USB devices
#
# CONFIG_SND_USB_AUDIO is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_UHCI_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
# CONFIG_USB_STORAGE_HP8200e is not set
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set

#
# USB Human Interface Devices (HID)
#
CONFIG_USB_HID=y
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_XPAD is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set

#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set

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

#
# USB Network adaptors
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set

#
# USB port drivers
#
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_TEST is not set
# CONFIG_USB_GADGET is not set

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

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
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=y
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# 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_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=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V4 is not set
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
# CONFIG_EXPORTFS is not set
CONFIG_SUNRPC=y
# CONFIG_SUNRPC_GSS is not set
CONFIG_SMB_FS=m
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_DEBUG_SPINLOCK_SLEEP=y
CONFIG_FRAME_POINTER=y

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
# CONFIG_CRYPTO is not set

#
# Library routines
#
CONFIG_CRC32=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

#4 lore raw
In reply to Andries Brouwer
Quoted 5 lines · Andries Brouwer
Quoted 2 lines

One more question: Will kbdrate work properly (use ioctls) when compiled on a 2.6 kernels?

kbdrate first tries the KDKBDREP ioctl, then the KIOCSRATE ioctl, and if both fail it will try to write to /dev/port.

Could you disable accessing /dev/port if running on a 2.6 kernel?

If the controller is in MUX mode it can disturb it rather badly. It's wrong anyway, because if the user has an USB keyboard, and in the case of a legacyless system it'll even try to access nonexisting hardware.

The problem is that when you're in X, and root, the ioctls will fail, but /dev/port will still work, and cause trouble.

I'd even vote in favor of ditching the /dev/port code completely, because all reasonable kernels support the ioctls, but that's your call.

----

Btw, what would you think about having the setkeycodes and kbdrate (and possibly some other tools, too) take an optional argument of /dev/input/event#, and then use the EVIOCSKEYCODE ioctl and EV_REP write to set the scancodes and repeat on that single device? It'd be very useful if one has more than one keyboard in the system.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#5 lore raw
In reply to Andries Brouwer
Quoted 11 lines · Andries Brouwer
Quoted 4 lines · Vojtech Pavlik

Sorry. I was typing that from memory. I'll fix it. Btw, could you make the kbd package accept scancodes in the 0x80-0xff range (same as e000 to e07f), if it is not yet there? And how about scancodes in the 0x100-0x1ff range? Will those work?

What is needed for the 2.6 kernel is rather volatile (and maybe the present kernel version is not quite final yet). But setkeycodes does ioctl(fd,KDSETKEYCODE,&a) where

Quoted 6 lines
                a.keycode = atoi(argv[2]);
                a.scancode = strtol(argv[1], &ep, 16);
                if (a.scancode >= 0xe000) {
                        a.scancode -= 0xe000;
                        a.scancode += 128;      /* some kernels needed +256 */
                }

I think this is fine. It keeps backwards compatibility with people's old scripts and still it allows arbitrary scancodes.

Quoted 10 lines

The 2.6.1 kernel is still very messy, with code

        if (atkbd->emul) {
                if (--atkbd->emul)
                        goto out;
                code |= (atkbd->set != 3) ? 0x80 : 0x100;
        }

where the representation of the e0 prefix depends on the current scancode mode. A bad idea.

Well, I think it's a bad idea to have the userspace tool know about the e0 thing at all. It should be just opaque numbers to it.

I agree that the above code choosing between 0x80 and 0x100 is not very nice, but it has two reasons:

0) e0+(00..7f) is the most common code for extra keys in set2, while (80..df) is the most common code for extra keys in set3

1) it will work in old setkeycodes - although the values you'll have to specify with set3 are rather nonsensical, you still will be able to set extra keys on a set3 keyboard.

2) the scancode tables are much more compact.

I don't have a problem with swapping the set3 table, if setkeycodes works reasonably now for scancodes above 128.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#26 lore raw

Re: 2.6 input drivers FAQ (ir-kbd-gpio.ko)

In reply to Jose Luis Domingo Lopez
Quoted 6 lines

And from /proc/bus/input/devices:
N: Name="bttv IR (card=41)"
H: Handlers=kbd event3

I have downloaded LIRC from CVS (0.7.0pre1), tried to compile it with little overall success, and started "lircd --device=/dev/lircd --nodaemon".

The device is /dev/input/event3.

Gerd

Signature · 1 line
"... und auch das ganze Wochenende oll" -- Wetterbericht auf RadioEins
#14 lore raw
In reply to Gene Heskett
Quoted 5 lines · Gene Heskett

In years past, the mouse double-click for a single click syndrome was caused by the pushbutton switch in the mouse becoming unsoldered, as in a microscopic crack in the solder you had to use a strong glass to see around the switches pin in the puddle of solder. Holding the switch solidly against the board and resoldering fixed it right up.

Wow. What are the chances of that happening to two different Microsoft Trackball Opticals, purchased at different times, but failing at the same time? (I have one that stays with the docking station in the one office space I use, and another that travels with me to the other office space, or home, or plane, or whatever)...

#30 lore raw
In reply to Vojtech Pavlik
Quoted 16 lines · Vojtech Pavlik

Problems:
~~~~~~~~~

I'm getting double clicks when I click only once. My scroll wheel scrolls by two lines/screens instead of one. My mouse moves too fast.

Solution:
~~~~~~~~~

Check your XFree86 config file.

You probably have two "mouse" entries there, one pointing to /dev/psaux and the other to /dev/input/mice, so that you can get both your PS/2 and USB mouse working on 2.4.

Quoted 5 lines

2.6 uses the input subsystem for both PS2 and USB, and thus both devices will report events from both mice, resulting in doubled events.

Remove either the /dev/psaux or /dev/input/mice entry, depending what suits you better for 2.4 compatibility should you ever need go back to 2.4.

Finally! Thanks so much for putting together this FAQ Vojtech! This mouse thing has been driving me crazy, and despite all my googling around for a solution, I never found the one above.

Jesse

#17 lore raw
In reply to Vojtech Pavlik
Quoted 2 lines · Vojtech Pavlik

Are you sure you don't have the mouse configured twice in XFree86 config? It's a rather common error.

Section "InputDevice"

        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Device" "/dev/psaux"
        Option      "Protocol" "ExplorerPS/2"
        Option      "Buttons" "7"
        Option      "Emulate3Buttons" "on"
        Option      "ZAxisMapping" "6 7"

EndSection

And if I *had* gotten it in there twice, why would it only hit sporadically once or twice a day, as opposed to *all* mouse events (clicks, moves, etc) being doubled?

#18 lore raw
Quoted 8 lines · On Mon, Feb 02, 2004 at 01:12:06PM -0500, [email protected] wrote:

Section "InputDevice"

        Identifier  "Mouse0"
        Driver      "mouse"
        Option      "Device" "/dev/psaux"
        Option      "Protocol" "ExplorerPS/2"
        Option      "Buttons" "7"
        Option      "Emulate3Buttons" "on"
        Option      "ZAxisMapping" "6 7"
Quoted 5 lines

EndSection

And if I *had* gotten it in there twice, why would it only hit sporadically once or twice a day, as opposed to *all* mouse events (clicks, moves, etc) being doubled?

Because normally the X server reads them in very quick succession and if you don't make a very short click, the sequence looks like this:

push1 push2 release1 release2, which is fine, because X interprets that as just a push and a release.

If there is disk activity or something else that causes the scheduling to be delayed, it's push1 release1 push2 release2, which counts as a doubleclick.

Hence sporadic doubleclicking.

For movement, of course, you get twice the mouse speed, but usually most people just adjust the acceleration settings and are done with that.

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#19 lore raw
Quoted 1 line · Vojtech Pavlik

Hence sporadic doubleclicking.

There's no chance that /dev/input/mice is reading from my mouse twice, right?

BTW, the information you asked for is in another message in this thread, just in case you missed it.

Signature · 1 line
Joshua Kwan
#21 lore raw
In reply to Vojtech Pavlik
Quoted 11 lines · Vojtech Pavlik

Because normally the X server reads them in very quick succession and if you don't make a very short click, the sequence looks like this:

push1 push2 release1 release2, which is fine, because X interprets that as just a push and a release.

If there is disk activity or something else that causes the scheduling to be delayed, it's push1 release1 push2 release2, which counts as a doubleclick.

Hence sporadic doubleclicking.

Well.. that would explain things except for the single /dev/psaux I have.

Could a similar timing hole happen if the system submerged into SMM code for a battery check or similar? (I know, that *should* cause lost events not duplicated, but....)

Quoted 2 lines

For movement, of course, you get twice the mouse speed, but usually most people just adjust the acceleration settings and are done with that.

Haven't seen this.

#20 lore raw
In reply to Joshua Kwan
Quoted 5 lines · Joshua Kwan
Quoted 1 line · Vojtech Pavlik

Hence sporadic doubleclicking.

There's no chance that /dev/input/mice is reading from my mouse twice, right?

No.

Quoted 2 lines

BTW, the information you asked for is in another message in this thread, just in case you missed it.

I've looked at it. Everything looks correct. Did you try with a different mouse, too?

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#22 lore raw
In reply to [email protected]
Quoted 12 lines · On Mon, Feb 02, 2004 at 03:28:49PM -0500, [email protected] wrote:
Quoted 10 lines · Vojtech Pavlik

Because normally the X server reads them in very quick succession and if you don't make a very short click, the sequence looks like this:

push1 push2 release1 release2, which is fine, because X interprets that as just a push and a release.

If there is disk activity or something else that causes the scheduling to be delayed, it's push1 release1 push2 release2, which counts as a doubleclick.

Quoted 7 lines
Quoted 1 line

Hence sporadic doubleclicking.

Well.. that would explain things except for the single /dev/psaux I have.

Could a similar timing hole happen if the system submerged into SMM code for a battery check or similar? (I know, that *should* cause lost events not duplicated, but....)

I don't see a way how this could happen. One thing you could try - run evtest on the mouse event device in a window/on another vc, and when the doubleclick happens, examine the last sreenful of events.

Quoted 4 lines
Quoted 2 lines

For movement, of course, you get twice the mouse speed, but usually most people just adjust the acceleration settings and are done with that.

Haven't seen this.

Most likely your problem comes from elsewhere. Did you try another mouse?

Signature · 2 lines
Vojtech Pavlik
SuSE Labs, SuSE CR
#27 lore raw

Re: 2.6 input drivers FAQ (ir-kbd-gpio.ko)

In reply to Jose Luis Domingo Lopez

Hi!

Quoted 27 lines
Quoted 6 lines

Common problems and solutions with 2.6 input drivers:
Problem:
~~~~~~~~
I've read through the whole file, and it did not help me at all!

The following is not a problem, but a question I have been unable to answer by myself. Is with respect to the recent addition of "input layer based support for infrared remote controls", mainly for use with TV tuner cards based on bttv.

Gerd Knorr did the patch that was integrated into mainstream as ChangeSet 1.1474.131.296, and I was trying to use the new standard driver instead of the ported one from 2.4.x, which I got from LIRC mailinglists, and has been working OK with 2.5.x and 2.6.x.

If I load the new kernel modules ir_kbd_gpio and ir_common I get in the logs:
ir-kbd-gpio: bttv IR (card=41) detected at pci-0000:00:0b.0/ir0

And from /proc/bus/input/devices:
I: Bus=0001 Vendor=1461 Product=0001 Version=0001
N: Name="bttv IR (card=41)"
P: Phys=pci-0000:00:0b.0/ir0
H: Handlers=kbd event3
B: EV=100003
B: KEY=c304 80100040 0 0 30000 0 2008000 80 1 9e0000 7bb80 0 0

Quoted 8 lines

So everything seems to be detected OK. But when I start lircd 0.6.6-7, it seems to come up fine, but as soon as any application tries to get keypresses from /dev/lirc the daemon exists, because of:
could not open /dev/lirc

So it seems the new kernel driver for TV capture card based remote controls doesn't use /dev/lirc as the place to "send" events from which applications read them.

Exactly. With this driver, this is just another keyboard, not lirc device. You should not need lircd.

Pavel

Signature · 2 lines
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
#28 lore raw

Re: 2.6 input drivers FAQ (ir-kbd-gpio.ko)

Quoted 6 lines · Pavel Machek
Quoted 3 lines

So it seems the new kernel driver for TV capture card based remote controls doesn't use /dev/lirc as the place to "send" events from which applications read them.

Exactly. With this driver, this is just another keyboard, not lirc device. You should not need lircd.

I have no idea how to use lirc ready apps without lircd but cvs version of lircd is able to deal with ir-kbd drivers - it reads events from /dev/input/eventX.

Quoted 1 line

Pavel

Signature · 2 lines
Arkadiusz Miśkiewicz     CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux
#29 lore raw

Re: 2.6 input drivers FAQ (ir-kbd-gpio.ko)

In reply to Pavel Machek
Quoted 7 lines
Quoted 4 lines

The following is not a problem, but a question I have been unable to answer by myself. Is with respect to the recent addition of "input layer based support for infrared remote controls", mainly for use with TV tuner cards based on bttv.

Exactly. With this driver, this is just another keyboard, not lirc device. You should not need lircd.

The cvs version can also work with the linux event layer, so it is possible to use lircd if you want. It isn't mandatory through.

Documentation/video4linux/README.ir has some more notes.

Gerd