Re: Problems with IDE on GA-7VAXP motherboard

Re: Problems with IDE on GA-7VAXP motherboard

[misty-]

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

On Thu, Jun 19, 2003 at 02:29:40PM +0200, Bernd Schubert wrote:
> have you already looked at the irq's from the lspci output? Especially the
> usage from 16 to 19, for graphics-, sound- and network-card looks a bit
> wrong.
No, I hadn't noticed that. hmm. However I have both tried with and
without ACPI and APCI or whatever it is (One does stuff like APM and the
other one does the irq routing among other things IIRC.) People have
told me to both turn it on and off. Anyway, later on today I'm going to
try using a minimal kernel built with no options I absolutely don't need
to have to boot this thing. Might work.

dmseg attached.

Timothy C. McGrath

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 9110 bytes --]

Linux version 2.4.21 (misty@oorodina) (gcc version 3.3 (Debian)) #2 Wed Jun 18 14:36:40 MDT 2003
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 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.
found SMP MP-table at 000f4c50
hm, page 000f4000 reserved twice.
hm, page 000f5000 reserved twice.
hm, page 000f0000 reserved twice.
hm, page 000f1000 reserved twice.
On node 0 totalpages: 131056
zone(0): 4096 pages.
zone(1): 126960 pages.
zone(2): 0 pages.
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 Pentium(tm) Pro APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.
Enabling APIC mode: Flat.	Using 1 I/O APICs
Processors: 1
Kernel command line: BOOT_IMAGE=old ro root=302 ide0=nodma,ide1=nodma,ide2=nodma,ide3=nodma
ide_setup: ide0=nodma,ide1=nodma,ide2=nodma,ide3=nodma -- BAD OPTION
Initializing CPU#0
Detected 2086.519 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 4154.98 BogoMIPS
Memory: 516092k/524224k available (1281k kernel code, 7744k reserved, 319k data, 268k init, 0k highmem)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: CLK_CTL MSR was 60031223. Reprogramming to 20031223
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0383fbff c1c3fbff 00000000 00000000
CPU:             Common caps: 0383fbff c1c3fbff 00000000 00000000
CPU: AMD Athlon(tm) XP 2600+ stepping 01
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-15, 2-18, 2-20, 2-21, 2-22, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 15.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................

IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.......    : Delivery Type: 0
.......    : LTS          : 0
.... register #01: 00178003
.......     : max redirection entries: 0017
.......     : PRQ implemented: 1
.......     : IO APIC version: 0003
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 000 00  1    0    0   0   0    0    0    00
 01 001 01  0    0    0   0   0    1    1    39
 02 001 01  0    0    0   0   0    1    1    31
 03 001 01  0    0    0   0   0    1    1    41
 04 001 01  0    0    0   0   0    1    1    49
 05 000 00  1    0    0   0   0    0    0    00
 06 001 01  0    0    0   0   0    1    1    51
 07 001 01  0    0    0   0   0    1    1    59
 08 001 01  0    0    0   0   0    1    1    61
 09 001 01  0    0    0   0   0    1    1    69
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 001 01  0    0    0   0   0    1    1    71
 0d 001 01  0    0    0   0   0    1    1    79
 0e 001 01  0    0    0   0   0    1    1    81
 0f 000 00  1    0    0   0   0    0    0    00
 10 001 01  1    1    0   1   0    1    1    89
 11 001 01  1    1    0   1   0    1    1    91
 12 000 00  1    0    0   0   0    0    0    00
 13 001 01  1    1    0   1   0    1    1    99
 14 000 00  1    0    0   0   0    0    0    00
 15 000 00  1    0    0   0   0    0    0    00
 16 000 00  1    0    0   0   0    0    0    00
 17 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ16 -> 0:16
IRQ17 -> 0:17
IRQ19 -> 0:19
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2086.5624 MHz.
..... host bus clock speed is 333.8500 MHz.
cpu: 0, clocks: 3338500, slice: 1669250
CPU0<T0:3338496,T1:1669232,D:14,S:1669250,C:3338500>
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xf9ea0, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router default [1106/3189] at 00:00.0
PCI->APIC IRQ transform: (B0,I9,P0) -> 17
PCI->APIC IRQ transform: (B0,I11,P0) -> 19
PCI->APIC IRQ transform: (B0,I12,P0) -> 16
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Journalled Block Device driver loaded
 tbxface-0099 [01] Acpi_load_tables      : ACPI Tables successfully loaded
Parsing Methods:...............................................................................................................................................
143 Control Methods found and parsed (501 nodes total)
ACPI Namespace successfully loaded at root c02e9540
ACPI: Core Subsystem version [20011018]
evxfevnt-0081 [-23] Acpi_enable           : Transition to ACPI mode successful
Executing device _INI methods:.................................................
49 Devices found: 49 _STA, 1 _INI
Completing Region and Field initialization:...........................
17/22 Regions, 10/10 Fields initialized (501 nodes total)
ACPI: Subsystem enabled
ACPI: System firmware supports S0 S1 S4 S5
Processor[0]: C0 C1 C2, 2 throttling states
ACPI: Power Button (FF) found
ACPI: Multiple power buttons detected, ignoring fixed-feature
ACPI: Power Button (CM) found
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
tulip0: no phy info, aborting mtable build
eth0: Macronix 98715 PMAC rev 37 at 0xd800, 00:80:AD:7F:9D:9D, IRQ 16.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.
[drm] Initialized tdfx 1.0.0 20010216 on minor 0
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 00:11.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci00:11.1
    ide0: BM-DMA at 0xe800-0xe807, BIOS settings: hda:DMA, hdb:pio
hda: WDC WD102AA, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: attached ide-disk driver.
hda: host protected area => 1
hda: 20044080 sectors (10263 MB) w/2048KiB Cache, CHS=1247/255/63
Partition check:
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 65536)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 268k freed
Adding Swap: 128516k swap-space (priority -1)
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,2), internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,5), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,6), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,7), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,8), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ttyS0: LSR safety check engaged!
ttyS0: LSR safety check engaged!
ttyS1: LSR safety check engaged!
ttyS1: LSR safety check engaged!
ttyS0: LSR safety check engaged!
ttyS1: LSR safety check engaged!
Adding Swap: 127992k swap-space (priority -2)

Re: Problems with IDE on GA-7VAXP motherboard

[misty-]

I believe I have nailed the problem to the wall. Your talk about the
bios misdetecting the cable got me to thinking - I hadn't actually been
able to see what the bios said it was configuring the disks attached to
since lilo's menu came up microseconds later.

I still haven't bothered checking, however I believe the bios is on a
very unhealthy volume of crack. :)

using hdparm -i /dev/hda shows the disk wasn't configured to do any pio
mode or udma/dma mode at boot time. Strange, right?

Stranger when you do hdparm -I on the disk again and it shows the disk
is set to use udma4 - and the disk only understands up to udma2! - now
add in the fact I currently have a 40 wire cable connected to the disk
and my brain starts frying :)

At a suggestion of a friend, I set the disk to use mdma2 - via the line:

hdparm -Xmdma2 -d1 /dev/hda

It worked, for all of two seconds. Remember, this is a WD drive. WD
drives, or at least mine, like to screw up in pretty amazing ways when
you turn dma on initially. Mine throws a screenful of CRC errors,
causing the kernel to reset the ide channel. Oddly, I noticed that dma
was still on despite the fact the channel had been reset - so I checked
with -I again, only to find out now the disk was told to use udma*3*! -
this wasn't getting me anywhere. >D Anyway, the simple fix was to force
it to keep settings across a reset by doing:

hdparm -Xmdma2 -k1 -d1 /dev/hda

- I am no longer getting any hda: lost interrupt messages, nor am I
  getting any errors at all about the disk losing data or getting
  confused. It's running slower than I'm used to, as I used to run it in
  ata66 mode, but MUCH faster than it was a day ago. :) All I need to do now is migrate the information from this disk to one of my maxtors and I'm all set. Finally, I can start setting this machine up. Note, I could get this disk to use ata66 again if I switched cables to the 80 wire variant - but I plan on replacing this disk asap anyway.

So, to summarize: The BIOS in the Gigabyte GA-7VAXP motherboard (and
likely all variants using the same bios) is getting confused and
misdetecting both the cable's abilities and the hard disks abilities,
causing linux to have a very nasty fit when you try using it without
manually changing the settings using hdparm.

I have not tried, nor will I likely try, setting the PIO modes up with
this motherboard as I don't need to. However, it is very likely that the
same problem occurs with dma disabled as with dma enabled - you need to
manually reconfigure the hard disk and disk controller using hdparm to
the correct values, or it just basically gets all confused and whines.

Also note, I tested this setup after configuring with hdparm in three
ways: First, I did a test using hdparm -t -T /dev/hda - Passed. A little
slow, but understandable considering. Second, I did a simple test doing
find / - this almost always caused the thing to throw a hda: lost
interrupt before at some point or another. Passed. Finally, I'm
currently doing a kernel compile. As I said, a P1 133 was outpacing this
machine before. This is a AMD XP 2600+ - it's absolutely ludicrous for a
P1 to outpace this thing, unless some unsane overclocker ... no, I don't
want to encourage anyone. :P Anyway, even with the slow settings, the
kernel compile is going quite nicely, and is going much faster than the
P1 could ever hope to do.

Note that the bios in this motherboard does not support turning OFF dma
support - the only options are 'auto' 'ata33' and 'ata66/100/133' - all
of which don't appear to actually work. For instance, I have the bios
set to ata33 right now as I write this, and despite this, it was still
trying to set the disk up to use udma4!

A buggy bios a happy linux user does not make. :)

  Thank you for all your help, time and effort. It was greatly
  appreciated.

  Tim McGrath

Re: Problems with IDE on GA-7VAXP motherboard

[Vojtech Pavlik]

On Fri, Jun 20, 2003 at 03:52:51AM -0400, misty-@charter.net wrote:

> I believe I have nailed the problem to the wall. Your talk about the
> bios misdetecting the cable got me to thinking - I hadn't actually been
> able to see what the bios said it was configuring the disks attached to
> since lilo's menu came up microseconds later.
> 
> I still haven't bothered checking, however I believe the bios is on a
> very unhealthy volume of crack. :)
> 
> using hdparm -i /dev/hda shows the disk wasn't configured to do any pio
> mode or udma/dma mode at boot time. Strange, right?

Not very strange. Some disks even cannot report it. And, any disk if set
to PIO only may not report any mode as active, since that is only
applicable to DMA modes.

> Stranger when you do hdparm -I on the disk again and it shows the disk
> is set to use udma4 - and the disk only understands up to udma2! - now

If you use hdparm -I and the drive reports udma4, it can understand
udma4, since hdparm -I is straight from the drive's mouth.

> add in the fact I currently have a 40 wire cable connected to the disk
> and my brain starts frying :)

That's a problem I assume. If the drive can do udma3 and higher, the
chipset can do udma3 and higher, and you have a 40-wire cable and some
bad luck, the BIOS or the driver may misdetect the cable and try to
operate the drive at, most likely, udma4. This won't work, of course.

> At a suggestion of a friend, I set the disk to use mdma2 - via the line:
> 
> hdparm -Xmdma2 -d1 /dev/hda

Don't do this. If your drive supports udma, then there is no reason to
use mwdma. Ever. mwdma is not crc-protected and that can lead to drive
data corruption, namely in the case where you seem to have cabling
problems.

If you have a 40-wire cable, udma2 will work just fine on it. If you
want a slower speed, use udma1 or udma0, which is the same speed as
mwdma2, but is CRC protected and thanks to the udma signalling also more
robust.

> It worked, for all of two seconds. Remember, this is a WD drive. WD
> drives, or at least mine, like to screw up in pretty amazing ways when
> you turn dma on initially. Mine throws a screenful of CRC errors,
> causing the kernel to reset the ide channel.

CRC errors in mwdma mode? Weird. Those CRC errors must've come from the
drive itself - them not being transfer CRC errors but surface CRC
errors. That's mean the drive is dying and you should be getting them in
PIO mode as well

> Oddly, I noticed that dma
> was still on despite the fact the channel had been reset - so I checked
> with -I again, only to find out now the disk was told to use udma*3*! -
> this wasn't getting me anywhere. >D

Note that the asterisk stays even after the drive is used back in PIO
mode. The way to check if DMA is being used is hdparm /dev/hd*

> Anyway, the simple fix was to force
> it to keep settings across a reset by doing:
> 
> hdparm -Xmdma2 -k1 -d1 /dev/hda
> 
> - I am no longer getting any hda: lost interrupt messages, nor am I
> getting any errors at all about the disk losing data or getting
> confused. It's running slower than I'm used to, as I used to run it in
> ata66 mode, but MUCH faster than it was a day ago. :) All I need to do
> now is migrate the information from this disk to one of my maxtors and
> I'm all set. Finally, I can start setting this machine up. Note, I
> could get this disk to use ata66 again if I switched cables to the 80
> wire variant - but I plan on replacing this disk asap anyway.
> 
> So, to summarize: The BIOS in the Gigabyte GA-7VAXP motherboard (and
> likely all variants using the same bios) is getting confused and
> misdetecting both the cable's abilities and the hard disks abilities,
> causing linux to have a very nasty fit when you try using it without
> manually changing the settings using hdparm.
> 
> I have not tried, nor will I likely try, setting the PIO modes up with
> this motherboard as I don't need to. However, it is very likely that
> the same problem occurs with dma disabled as with dma enabled - you
> need to manually reconfigure the hard disk and disk controller using
> hdparm to the correct values, or it just basically gets all confused
> and whines.
> 
> Also note, I tested this setup after configuring with hdparm in three
> ways: First, I did a test using hdparm -t -T /dev/hda - Passed. A
> little slow, but understandable considering. Second, I did a simple
> test doing find / - this almost always caused the thing to throw a
> hda: lost interrupt before at some point or another. Passed. Finally,
> I'm currently doing a kernel compile. As I said, a P1 133 was
> outpacing this machine before. This is a AMD XP 2600+ - it's
> absolutely ludicrous for a P1 to outpace this thing, unless some
> unsane overclocker ... no, I don't want to encourage anyone. :P
> Anyway, even with the slow settings, the kernel compile is going quite
> nicely, and is going much faster than the P1 could ever hope to do.
> 
> Note that the bios in this motherboard does not support turning OFF
> dma support - the only options are 'auto' 'ata33' and 'ata66/100/133'
> - all of which don't appear to actually work. For instance, I have the
> bios set to ata33 right now as I write this, and despite this, it was
> still trying to set the disk up to use udma4!
> 
> A buggy bios a happy linux user does not make. :)
> 
>   Thank you for all your help, time and effort. It was greatly
>   appreciated.
> 
>   Tim McGrath - To unsubscribe from this list: send the line
>   "unsubscribe linux-kernel" in the body of a message to
>   majordomo@vger.kernel.org More majordomo info at
>   http://vger.kernel.org/majordomo-info.html Please read the FAQ at
>   http://www.tux.org/lkml/

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: Problems with IDE on GA-7VAXP motherboard

[misty-]

On Fri, Jun 20, 2003 at 10:58:53AM +0200, Vojtech Pavlik wrote:
> On Fri, Jun 20, 2003 at 03:52:51AM -0400, misty-@charter.net wrote:
> 
> > using hdparm -i /dev/hda shows the disk wasn't configured to do any pio
> > mode or udma/dma mode at boot time. Strange, right?
> 
> Not very strange. Some disks even cannot report it. And, any disk if set
> to PIO only may not report any mode as active, since that is only
> applicable to DMA modes.
Hmm. Interesting, as the information shown with -i matches what the disk
supports, and -I matches what the controller supports. maybe a bug in
hdparm, or perhaps I was using it incorrectly. I'll investigate.

> If you use hdparm -I and the drive reports udma4, it can understand
> udma4, since hdparm -I is straight from the drive's mouth.
again that's interesting as -i shows the max the disk can do is udma2 -
and in fact, that *is* the max.

> > add in the fact I currently have a 40 wire cable connected to the disk
> > and my brain starts frying :)
> 
> That's a problem I assume. If the drive can do udma3 and higher, the
> chipset can do udma3 and higher, and you have a 40-wire cable and some
> bad luck, the BIOS or the driver may misdetect the cable and try to
> operate the drive at, most likely, udma4. This won't work, of course.
hrm. The BIOS detects I have a 40 wire cable, however tells the chipset
that I have an 80 wire cable. (Confirmed by checking /proc/ide/via) So, things are pretty f'd up in the BIOS, and I can't figure out why it's doing this. Not that it really matters now that I can get it to work *anyway* - but.

> > At a suggestion of a friend, I set the disk to use mdma2 - via the line:
> > 
> > hdparm -Xmdma2 -d1 /dev/hda
> 
> Don't do this. If your drive supports udma, then there is no reason to
> use mwdma. Ever. mwdma is not crc-protected and that can lead to drive
> data corruption, namely in the case where you seem to have cabling
> problems.
I was totally unaware of this. Thanks for the information!

> 
> If you have a 40-wire cable, udma2 will work just fine on it. If you
> want a slower speed, use udma1 or udma0, which is the same speed as
> mwdma2, but is CRC protected and thanks to the udma signalling also more
> robust.
OK, I wasn't aware udma2 worked on this type of cable, and was planning
on switching back to the other 80 wire cable before I continued. Thanks.

> 
> > It worked, for all of two seconds. Remember, this is a WD drive. WD
> > drives, or at least mine, like to screw up in pretty amazing ways when
> > you turn dma on initially. Mine throws a screenful of CRC errors,
> > causing the kernel to reset the ide channel.
> 
> CRC errors in mwdma mode? Weird. Those CRC errors must've come from the
> drive itself - them not being transfer CRC errors but surface CRC
> errors. That's mean the drive is dying and you should be getting them in
> PIO mode as well
I know a little more about this than you having dealt with this buggy
drive for more than two years. Basically wd drives don't deal well with
DMA as their hardware doesn't follow the spec - specifically, something
in the crc handling is f'd up, so occasionally the drive will report a
crc error that doesn't actually exist. And it will continue reporting
crc errors infinitely until the ide channel and all devices on it are
reset - which can be maddening at times when I'm playing quake,
something tries to load a file and for two seconds my computer is
frozen. Luckily due to the kernel's error handling, it can deal with
this, and life goes on. I've never lost any data due to this hardware
bug, it's just annoying. If you're in the market for a hard disk, I'd
avoid Western Digital hard disks for this very reason - they're cheap
for a reason. :)

The whole crc errors filling the screen thing - that's actually NORMAL
for this disk when you initially turn dma on. It used to happen on the
old system, so I was actually glad to see it happening again, because it
meant things were working. The error messages weren't showing up in
udma4 mode, and in fact it was acting as if dma was totally turned
off... I guess because the disk doesn't understand udma4 at all.

> > Oddly, I noticed that dma
> > was still on despite the fact the channel had been reset - so I checked
> > with -I again, only to find out now the disk was told to use udma*3*! -
> > this wasn't getting me anywhere. >D
> 
> Note that the asterisk stays even after the drive is used back in PIO
> mode. The way to check if DMA is being used is hdparm /dev/hd*
Yes, I did that, which is why I noticed dma was still enabled to my
astonishment. Rather than get my hopes up, I checked what the drive was
set to with -i, and nothing showed up - so I checked with -I and my
eyebrow started twitching because it had neither stayed at the setting
I'd set nor gone back to the setting it was at before.

I've never set up a hard disk with PIO modes before, so I'd like to hear
any advice you have on that - currently whatever setup the hard disk is
trying to use with dma off is malfunctioning in a grand manner, and I'd
like to have a failsafe in case for whatever reason the hard disk throws
the gauntlet down and refuses to do dma in the future for whatever
reason.

Mostly, I want to know if what is listed by a -i/-I is assumed 'safe' to
use. Certaintly I'm expecting you to say 'no, backup your data first
before experimenting' so, you need not surprise me. However, any other
advice you have would certaintly be appreciated. Also, I have a 486 with
dma capable hard disks that has a non dma capable disk controller, so if
I can get PIO modes working on it's hard disks it might speed things up
slightly, who knows.

Thanks for your comments,
Timothy C. McGrath

Re: Problems with IDE on GA-7VAXP motherboard

[Vojtech Pavlik]

On Fri, Jun 20, 2003 at 07:40:30AM -0400, misty-@charter.net wrote:

> Mostly, I want to know if what is listed by a -i/-I is assumed 'safe' to
> use. Certaintly I'm expecting you to say 'no, backup your data first
> before experimenting' so, you need not surprise me. However, any other
> advice you have would certaintly be appreciated. Also, I have a 486 with
> dma capable hard disks that has a non dma capable disk controller, so if
> I can get PIO modes working on it's hard disks it might speed things up
> slightly, who knows.

Well, send me the output of your dmesg (only the IDE parts),
/proc/ide/via, hdparm /dev/hd*, hdparm -i /dev/hd* and I'll write a
commentary on what means what and what's the maximum speed the thing is
expected to operate at.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: Problems with IDE on GA-7VAXP motherboard

[misty-]

On Fri, Jun 20, 2003 at 01:57:41PM +0200, Vojtech Pavlik wrote:
> Well, send me the output of your dmesg (only the IDE parts),
> /proc/ide/via, hdparm /dev/hd*, hdparm -i /dev/hd* and I'll write a
> commentary on what means what and what's the maximum speed the thing is
> expected to operate at.

Will do this tomorrow, need to sleep now. Thanks for the help :)

Timothy C. McGrath

Re: Problems with IDE on GA-7VAXP motherboard

[Henning P. Schmiedehausen]

misty-@charter.net writes:

>I believe I have nailed the problem to the wall. Your talk about the
>bios misdetecting the cable got me to thinking - I hadn't actually been
>able to see what the bios said it was configuring the disks attached to
>since lilo's menu came up microseconds later.

Put your Boot Sequence on "Floppy --> Anything else" and format a floppy
with just plain DOS. :-)

Works for me every time. 

	Regards
		Henning


-- 
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen          INTERMETA GmbH
hps@intermeta.de        +49 9131 50 654 0   http://www.intermeta.de/

Java, perl, Solaris, Linux, xSP Consulting, Web Services 
freelance consultant -- Jakarta Turbine Development  -- hero for hire

Re: Problems with IDE on GA-7VAXP motherboard

[misty-]

Alright, minor update. I was messing around tonight not really expecting
to get anywhere, and to my horror, saw a 'hda: lost interrupt' message.
Again. So. Off I go, trying to figure out what is going on and what do I
find out? You sir were totally right. even with the -k1 setting, the wd
drive changes it's settings back to whatever it wants when it throws the
crc errors. Which incidentally appears to be settings it shouldn't be
capable of supporting, but... whatever. Anyway. A friend of mine (who
I'm very grateful for putting up with me) helped me screw around with
PIO modes, and we managed to get the disk working with dma off and PIO
mode 4 enabled.

What was likely fooling me into thinking the drive was working properly
is the enormous amount of ram my computer has now - I tend to forget
that with almost 512MB free of ram, my disk cache can be absolutely
enormous. Which of course means I can easily  get fooled into thinking a
disk operation is working perfectly fine when in fact the disk isn't
even being touched at all.

it looks like I was very lucky with my original motherboard and that the
wd drive was able to communicate at it's stock settings without having
any special setup - otherwise, this entire assumption would never have
happened - the disk worked perfectly fine with dma on my previous
motherboard, which is why I was so surprised things broke so damn fast
now.

So, the Gigabyte motherboard I'm using is still missetting the values
for the hard disks - but on the other hand, my hard disk was also
playing foul games.

I tested right after doing a reboot with the PIO4 settings, and it
appears to be working just fine. My test consisted of a hdparm -t -T
/dev/hda and also a tar c / > /dev/null for completeness. No problems.

I'll have more detailed information on my setup for you to look at
fairly soon.

After I get the data moved off of it, I plan on sticking this WD drive
into my 486, where it will happily work without any dma support at all.
And it can stay there, for all I care. :)

Timothy C. McGrath

Re: Problems with IDE on GA-7VAXP motherboard

[Tim McGrath]

To my astonishment, everything is working now that I've had time to sort
out all the problems.

What I had to do: First off, the WD drive was causing a lot of strange
problems all by itself. Removing it from my computer made everything
work a lot better - both maxtors have their DMA modes correctly detected
and turned on at boot time, although I still manually prefer to turn
them on and do small amounts of tuning myself using hdparm once the
kernel starts.

Weird problems I've noticed include that the kernel and motherboard
disagree with the CHS attributes of my larger disk, a 120GB maxtor 7200
rpm drive. I'm pretty sure the kernel is right, mostly because using the
CHS settings the motherboard insists on cause braindamage in DOS,
including but not limited to the partition table being misdetected, the
files on the disk I copied there from linux to dos going missing, 6mb of
'bad sectors' when I try formatting the partition (Which goes away when 
I enter linux.) and when linux fscks the disk, it can find DOS's files
and believes the disk has enormous filesystem corruption. Oddly enough,
the 40GB maxtor hard disk I have (That incidentally originally came with
the ps2 linux kit) is correctly detected.

I haven't yet tried fiddling with the motherboard's settings for the
first hard disk - everything is still on auto, but I'm pretty sure there
is nothing I can do to manually set the CHS, which will be a problem if
I want to boot dos correctly. :( I've checked with maxtor's site, but
their maxblast program only works in windows according to it, which is a
pity since I don't have that installed here. I'll likely be forced to
use dosemu, although right now I can neither get sound nor VGA/SVGA to
work in it. *shrugs* I'm sure given enough time I can nail this too,
although I'd love suggestions. ... Hmm, just had a thought. Worst case,
I can make the 40GB disk have a dos partition and tell lilo to swap the
disk appearance for dos when I want to run dos. ... I might go with
that, actually.

Things that I've tried and haven't worked, include manually setting the
CHS in lilo's append command - obviously this only works for the linux
kernel. I've tried using grub as well, and it fixes the braindamage by
itself - problem is according to what little I've read of grub's
documentation there is no way to boot dos using it that I can see. If
I'm wrong, please inform me where the documentation for doing it is
located?

So. Problems with the Gigabyte GA-7VAXP motherboard I've found with
linux and it's F11 variant of the bios include:

Western Digital drives go absofuckinglutely insane in linux, which
actually isn't abnormal from what I've read - seems to be an issue more
with the disk being insane in the first place, and telling the BIOS it
can do things it not only can't do, but won't do, nor will the disk
complain when you try to do them. If you have one of these disks, the
only thing I can really say to you is to force dma OFF and experiment
with PIO mode. Mode 4 worked on my hard disk, but yours might be
different from mine, keep this in mind. Also note PIO mode is *slow* -
unbelievably slow compared to DMA. If you are stuck with one of these
disks, if you can return it and get your money back - do it. Otherwise,
you might consider getting a different manufacturers hard disk - from
what I've read using google.com about western digital disks and linux,
they just plain don't work with dma in linux, and the company seems to
have no plans on fixing this problem.

Large hard disks have their CHS values incorrectly detected.

Not including this, I've noted that the onboard fan that came with the
board which cools the agp chipset (at least I think it does - has a 'AGP
8x' sticker on it) is starting to wear out. I'm sure I can find a
replacement for it at radio shack, but I think it's a little silly for
it to be wearing out already.

I can't really recommend this board to other people, especially as I
haven't even tried enabling the other hard disk controller (which uses a
promise bios and can do ATA/RAID) and the problems I've had with this
motherboard were really absurd at some points. Also one of the things
you WON'T see on websites trying to sell you this board is that the bios
doesn't let you change important things - like memory timings, wether or
not dma should be totally turned OFF to hard disks, among other things.
I've not investigated yet, but I have a feeling I'm not going to be able
to manually set the CHS either, which would be a pity. None of these
things really makes a difference in linux, but on the other hand it
makes it a lot easier to track down problems if you can force the bios
to do the hard work for you when you're trying to figure out what's
wrong with the machine. Trying to fix problems on this motherboard makes
me feel half the time like I've got a hand tied behind my back. Another
thing is that the manual tends to be in engrish, so it's a little hard
to read at times. I won't be buying a gigabyte motherboard next time -
they're nice and slick, have pretty pictures, have a easy to use bios,
so long as you don't do things it doesn't understand, but although I
like having an 'autodetect' mode, I also like being able to manually set
the bios to do things. I had and still have this same type of problem
with my IBM PS/1 2155-78C(SL-B) which was built almost ten years ago -
it's silly to see people still building motherboards that don't have the
ability for the user to set settings manually.

Timothy C. McGrath

Re: Problems with IDE on GA-7VAXP motherboard

[Tim McGrath]

Well, I just rebooted and checked - I can, in fact, set the CHS
settings. However, not to the settings I need. ... Which explains nicely
why my bios can't figure out what to do with my disk. Ah well, I tried.

Anyone with suggestions on how to get DOS booting and happy would be
appreciated.

Tim McGrath

Re: Problems with IDE on GA-7VAXP motherboard

[Bartlomiej Zolnierkiewicz]

On 26 Jun 2003, Tim McGrath wrote:

> Well, I just rebooted and checked - I can, in fact, set the CHS
> settings. However, not to the settings I need. ... Which explains nicely
> why my bios can't figure out what to do with my disk. Ah well, I tried.
>
> Anyone with suggestions on how to get DOS booting and happy would be
> appreciated.

Maybe you can use dosemu under Linux instead?
http://www.dosemu.org

There is also GPLed DOS replacement, maybe it doesn't use CHS info,
if it does you have source code available ;-).
http://www.freedos.org

--
Bartlomiej

> Tim McGrath

Re: Problems with IDE on GA-7VAXP motherboard

[Tim McGrath]

On Thu, 2003-06-26 at 06:50, Bartlomiej Zolnierkiewicz wrote:
> Maybe you can use dosemu under Linux instead?
> http://www.dosemu.org
Well, yes, it works - problem is I can't figure out how to get sound nor
VGA/SVGA working in it, and I need both to play the games I use DOS for.

> There is also GPLed DOS replacement, maybe it doesn't use CHS info,
> if it does you have source code available ;-).
> http://www.freedos.org
Nope, not even going to try that one - I've used it before and the last
time I tried it, it had the same problems dos did. Not that it's a bad
program or anything.

Thanks for trying to help. If you know how to get dosemu working with
vga/svga and sound in linux console/x let me know.

Another option I'm going to try is booting off the 40GB disk I have
instead of the 100GB disk - should work as the CHS info given by the
bios agrees with the kernel.

We'll see.

Timothy C. McGrath

Re: Problems with IDE on GA-7VAXP motherboard

[Bernd Schubert]

Hi,

have you already looked at the irq's from the lspci output? Especially
the
usage from 16 to 19, for graphics-, sound- and network-card looks a bit
wrong.
>From your kernel-configuration I can see that you have acpi enabled, the
first I would do is booting with acpi=off as kernel option. If you
really need acpi later on, you should try with pci=noacpi or pci=biosirq. Also
consider to use a more recent acpi from acpi.sf.net.

If this doesn't help, I would suggest that you also send some lines from
dmesg-output, so that the real experts can see whats going on with your
irq-routing.

Best regards,
        Bernd

Re: Problems with IDE on GA-7VAXP motherboard

[John Bradford]

> Please forgive me if I've sent this to the wrong address, it is the one
> listed in the 2.4.21 sources in the MAINTAINERS file as the IDE
> maintainer.

> Okay, I've spent a LONG time (>48 hrs) trying to fix this problem on my own, and I
> have no idea what is causing this totally weird behavior.

> I just recently replaced a broken system with a new gigabyte GA-7VAXP
> motherboard and an athlon XP 2600 cpu. The Gigabyte motherboard has the
> Via VT82C586/B/686A/B (according to lspci -v) chipset on ide0, which is
> being used for the WDC WD102AA hard disk (according to
> /proc/ide/ide0/hda/model)

I have two Gigabyte GA-7VA based machines here with Athlon XP 2200+
cpus.  This board also uses the VT82C586B chipset for IDE. 

They works fine here, except for mis-detection of a 40-way cable as
80-way, (and the devices on the 40-way cable only support a maximum of
33.3MB/s anyway, so it's not a big problem at the moment). 

> I have disabled everything I possibly could in the bios without making
> it impossible to boot the system. I have tried using the original cables
> from the old machine, as well as the new cables that came with the
> motherboard. I have tried the hard disk in both master and cable select modes.
> I have both enabled and disabled ACPI, to see if that would make it
> work. I have tried moving the hard disk to a different ide channel. I
> have removed all other hard disks from the system. (All are experiencing
> the problems, not just this one) I have asked everyone I know that knows
> anything about computers what could be wrong - most of their replies were
> variants of the above.

The default BIOS settings worked fine for me.  I notice you've got the
IO-APIC enabled - I've left it disabled, basically because I don't
need the functionality yet, and it avoids any bugs in the kernel
IO-APIC code.

> The problem I'm seeing is, even with literally every single setting
> disabled in hdparm, the system is VERY VERY SLOW, and I'm often seeing
> 'hda: lost interrupt' in console when I try to read/write a large amount
> of data.

Hmmm, try disabling IO-APIC.

> It's so bad I'm actually having to compile my kernels on a separate
> pentium 1 133 because it's compiling them *faster* than my computer can.

Heh, must take about an hour :-).  My rarely-used MMX-200 compiles
recent 2.4 trees in about 30-40 minutes.

> I am currently using the 2.4.21 kernel, although I started trying this
> on the 2.4.20 kernel. Both exhibit the same problem unfortunately.

I've used 2.4.21-RC1 and 2.4.21-RC2 on these boxes without problems,
but I've been too busy to try more recent trees.  I did boot a recent
2.5 tree on one of them, and it booted successfully, but I didn't do
much testing, (due to lack of time).  I installed KDE, and noticed
that it was much slower to start under 2.5, but I've not investigated
that.

> I am familiar with patching kernels, and am able to fix cosmetic to
> minor problems in source, so sending me a patch and saying 'try this'
> isn't a problem.

> I *am* willing to experiment and try using 2.5.whatever but *only* if
> the ide maintainer or someone familiar with the ide subsystem tells me
> that it's safe to use in a certain configuration. I don't want to lose
> the data on my hard disk, it doesn't have a backup. (long story short, I
> was about to do a backup on the machine when the motherboard blewup.
> Seriously!)

If you don't enable exotic options like IO-APIC and ACPI, I seriously
doubt you'll get massive file corruption.  The only reasons I'm not
using 2.5 as a deault on most of my production boxes, are time and
security fixes not having gone in yet.

> If someone gives me a patch which makes the machine stable and able to
> work even if it's *slow* I'll be happy. I don't want the thing to lose
> data, and the message the kernel is giving me could be really really bad
> IIRC if it's trying to write when it loses the interrupt. :(

Try booting a 2.5 kernel, and mount the root filesystem read-only if
you're really worried about corruption.

> I currently am limited to using a keyboard only, and I'm stuck in
> console as I am unable to use X windows due to problems I was attempting
> to fix before the original system blewup. So... it's hard for me to copy
> and paste anything - I have to type it in manually. I would fix X, but
> considering doing 'make dep' on a 2.4.21 kernel currently takes longer
> on my XP 2600 system than it does to compile the *entire kernel* on a P1
> 133 (I'm stone cold serious.) ... ... ... No. Until I can get this fixed, I can't fix X.

> I have attached output from lspci -v, /proc/interrupts, my kernel
> .config and /proc/ioports in the hopes it is useful to you.
> (You'll likely notice I've thrown the kitchen sink at it. *shrugs*)

> If you can think of *anything* I can send you that might clear up this
> problem, ask for it.

Compile a minimal kernel without things like IO-APIC and ACPI
enabled.

Oh, I don't use modules by the way, so any issues with things being
compiled as modules won't be apparent to me :-).  So, you might want
to try compiling everything in.

John.

Problems with IDE on GA-7VAXP motherboard

[misty-]

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

Please forgive me if I've sent this to the wrong address, it is the one
listed in the 2.4.21 sources in the MAINTAINERS file as the IDE
maintainer.

Okay, I've spent a LONG time (>48 hrs) trying to fix this problem on my own, and I
have no idea what is causing this totally weird behavior.

I just recently replaced a broken system with a new gigabyte GA-7VAXP
motherboard and an athlon XP 2600 cpu. The Gigabyte motherboard has the
Via VT82C586/B/686A/B (according to lspci -v) chipset on ide0, which is
being used for the WDC WD102AA hard disk (according to
/proc/ide/ide0/hda/model)

I have disabled everything I possibly could in the bios without making
it impossible to boot the system. I have tried using the original cables
from the old machine, as well as the new cables that came with the
motherboard. I have tried the hard disk in both master and cable select modes.
I have both enabled and disabled ACPI, to see if that would make it
work. I have tried moving the hard disk to a different ide channel. I
have removed all other hard disks from the system. (All are experiencing
the problems, not just this one) I have asked everyone I know that knows
anything about computers what could be wrong - most of their replies were
variants of the above.

The problem I'm seeing is, even with literally every single setting
disabled in hdparm, the system is VERY VERY SLOW, and I'm often seeing
'hda: lost interrupt' in console when I try to read/write a large amount
of data.

It's so bad I'm actually having to compile my kernels on a separate
pentium 1 133 because it's compiling them *faster* than my computer can.

I am currently using the 2.4.21 kernel, although I started trying this
on the 2.4.20 kernel. Both exhibit the same problem unfortunately.

I am familiar with patching kernels, and am able to fix cosmetic to
minor problems in source, so sending me a patch and saying 'try this'
isn't a problem.

I *am* willing to experiment and try using 2.5.whatever but *only* if
the ide maintainer or someone familiar with the ide subsystem tells me
that it's safe to use in a certain configuration. I don't want to lose
the data on my hard disk, it doesn't have a backup. (long story short, I
was about to do a backup on the machine when the motherboard blewup.
Seriously!)

If someone gives me a patch which makes the machine stable and able to
work even if it's *slow* I'll be happy. I don't want the thing to lose
data, and the message the kernel is giving me could be really really bad
IIRC if it's trying to write when it loses the interrupt. :(

I currently am limited to using a keyboard only, and I'm stuck in
console as I am unable to use X windows due to problems I was attempting
to fix before the original system blewup. So... it's hard for me to copy
and paste anything - I have to type it in manually. I would fix X, but
considering doing 'make dep' on a 2.4.21 kernel currently takes longer
on my XP 2600 system than it does to compile the *entire kernel* on a P1
133 (I'm stone cold serious.) ... ... ... No. Until I can get this fixed, I can't fix X.

I have attached output from lspci -v, /proc/interrupts, my kernel
.config and /proc/ioports in the hopes it is useful to you.
(You'll likely notice I've thrown the kitchen sink at it. *shrugs*)

If you can think of *anything* I can send you that might clear up this
problem, ask for it.

Special note: Please send all followups to this address, as I do not
have a subscription to the linux kernel mailing list. (Although I don't
mind followups that wind up on the list too - I just won't see them :)

Timothy C. McGrath

[-- Attachment #2: lspci.txt --]
[-- Type: text/plain, Size: 2066 bytes --]

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Flags: bus master, 66Mhz, medium devsel, latency 8
	Memory at e0000000 (32-bit, prefetchable) [size=128M]
	Capabilities: [a0] AGP version 2.0
	Capabilities: [c0] Power Management version 2

00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 [Normal decode])
	Flags: bus master, 66Mhz, medium devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	Capabilities: [80] Power Management version 2

00:09.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) (prog-if 00 [VGA])
	Subsystem: 3Dfx Interactive, Inc. Voodoo3
	Flags: fast devsel, IRQ 17
	Memory at e8000000 (32-bit, non-prefetchable) [size=32M]
	Memory at ea000000 (32-bit, prefetchable) [size=32M]
	I/O ports at d000 [size=256]
	Expansion ROM at <unassigned> [disabled] [size=64K]
	Capabilities: [60] Power Management version 1

00:0b.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
	Subsystem: Ensoniq Creative Sound Blaster AudioPCI128
	Flags: bus master, slow devsel, latency 32, IRQ 19
	I/O ports at d400 [size=64]
	Capabilities: [dc] Power Management version 1

00:0c.0 Ethernet controller: Macronix, Inc. [MXIC] MX987x5 (rev 25)
	Flags: bus master, stepping, medium devsel, latency 32, IRQ 16
	I/O ports at d800 [size=256]
	Memory at ed000000 (32-bit, non-prefetchable) [size=256]
	Expansion ROM at <unassigned> [disabled] [size=256K]
	Capabilities: [44] Power Management version 1

00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Flags: bus master, stepping, medium devsel, latency 0
	Capabilities: [c0] Power Management version 2

00:11.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
	Subsystem: Giga-byte Technology GA-7VAX Mainboard
	Flags: bus master, medium devsel, latency 32
	I/O ports at e800 [size=16]
	Capabilities: [c0] Power Management version 2


[-- Attachment #3: ioports.txt --]
[-- Type: text/plain, Size: 493 bytes --]

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
02f8-02ff : serial(set)
03c0-03df : vga+
03f6-03f6 : ide0
03f8-03ff : serial(set)
0cf8-0cff : PCI conf1
d000-d0ff : 3Dfx Interactive, Inc. Voodoo 3
d400-d43f : Ensoniq 5880 AudioPCI
d800-d8ff : Macronix, Inc. [MXIC] MX987x5
  d800-d8ff : tulip
e800-e80f : VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE
  e800-e807 : ide0

[-- Attachment #4: interrupts.txt --]
[-- Type: text/plain, Size: 369 bytes --]

           CPU0       
  0:     208427    IO-APIC-edge  timer
  1:      13743    IO-APIC-edge  keyboard
  2:          0          XT-PIC  cascade
  9:          0    IO-APIC-edge  acpi
 12:          6    IO-APIC-edge  PS/2 Mouse
 14:      12154    IO-APIC-edge  ide0
 16:      10144   IO-APIC-level  eth0
NMI:          0 
LOC:     208378 
ERR:          0
MIS:          0

[-- Attachment #5: config --]
[-- Type: text/plain, Size: 22622 bytes --]

#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
# CONFIG_MODVERSIONS is not set
# CONFIG_KMOD is not set

#
# Processor type and features
#
# 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_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE 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_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_HAS_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_PGE=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_F00F_WORKS_OK=y
CONFIG_X86_MCE=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_HIGHMEM is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_SMP is not set
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
# CONFIG_X86_TSC_DISABLE is not set
CONFIG_X86_TSC=y

#
# General setup
#
CONFIG_NET=y
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_ISA=y
CONFIG_PCI_NAMES=y
CONFIG_EISA=y
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
# CONFIG_HOTPLUG_PCI is not set
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
# CONFIG_BINFMT_AOUT is not set
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_PM=y
CONFIG_ACPI=y
CONFIG_ACPI_DEBUG=y
CONFIG_ACPI_BUSMGR=y
CONFIG_ACPI_SYS=y
CONFIG_ACPI_CPU=y
CONFIG_ACPI_BUTTON=y
CONFIG_ACPI_AC=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_CMBATT=y
CONFIG_ACPI_THERMAL=y
# CONFIG_APM is not set

#
# 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 is not set
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y

#
# Plug and Play configuration
#
CONFIG_PNP=y
CONFIG_ISAPNP=y

#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE 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_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_BLK_STATS=y

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
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_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set

#
# Appletalk devices
#
# CONFIG_DEV_APPLETALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_LLC 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

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set
# CONFIG_PHONE_IXJ_PCMCIA is not set

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=m
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_BLK_DEV_CMD640=y
CONFIG_BLK_DEV_CMD640_ENHANCED=y
CONFIG_BLK_DEV_ISAPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
# CONFIG_IDEDMA_PCI_AUTO is not set
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_ADMA100 is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_AMD74XX_OVERRIDE is not set
CONFIG_BLK_DEV_CMD64X=y
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_PDC202XX_OLD=y
# CONFIG_PDC202XX_BURST is not set
CONFIG_BLK_DEV_PDC202XX_NEW=y
# CONFIG_PDC202XX_FORCE is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_SC1200 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=y
CONFIG_IDE_CHIPSETS=y
# CONFIG_BLK_DEV_4DRIVES is not set
# CONFIG_BLK_DEV_ALI14XX is not set
# CONFIG_BLK_DEV_DTC2278 is not set
# CONFIG_BLK_DEV_HT6560B is not set
# CONFIG_BLK_DEV_PDC4030 is not set
# CONFIG_BLK_DEV_QD65XX is not set
# CONFIG_BLK_DEV_UMC8672 is not set
# CONFIG_IDEDMA_AUTO is not set
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_PDC202XX=y
CONFIG_BLK_DEV_IDE_MODES=y
# CONFIG_BLK_DEV_ATARAID is not set
# CONFIG_BLK_DEV_ATARAID_PDC is not set
# CONFIG_BLK_DEV_ATARAID_HPT is not set
# CONFIG_BLK_DEV_ATARAID_SII is not set

#
# SCSI support
#
CONFIG_SCSI=m
CONFIG_BLK_DEV_SD=m
CONFIG_SD_EXTRA_DEVS=40
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=m
# CONFIG_SCSI_DEBUG_QUEUES is not set
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID 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_AHA1740 is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA 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_GENERIC_NCR5380 is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
CONFIG_SCSI_PPA=m
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_IZIP_EPP16 is not set
# CONFIG_SCSI_IZIP_SLOW_CTR is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_NCR53C8XX is not set
# CONFIG_SCSI_SYM53C8XX is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I 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_SEAGATE is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_SYM53C416 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

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set

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

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
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

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_SUNLANCE is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE 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
# 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_CS89x0 is not set
CONFIG_TULIP=y
# CONFIG_TULIP_MWI is not set
# CONFIG_TULIP_MMIO is not set
# CONFIG_DE4X5 is not set
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_EEPRO100_PIO is not set
# CONFIG_E100 is not set
# CONFIG_LNE390 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_NE3210 is not set
# CONFIG_ES3210 is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_SUNDANCE_MMIO is not set
# CONFIG_TLAN is not set
# CONFIG_TC35815 is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_VIA_RHINE_MMIO is not set
# CONFIG_WINBOND_840 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_MYRI_SBUS 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_TIGON3 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 is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER 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

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

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

#
# Input core support
#
CONFIG_INPUT=m
# CONFIG_INPUT_KEYBDEV is not set
# CONFIG_INPUT_MOUSEDEV is not set
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_EVDEV is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=y
# CONFIG_SERIAL_CONSOLE is not set
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_UNIX98_PTYS is not set
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set
# CONFIG_MK712_MOUSE is not set

#
# Joysticks
#
CONFIG_INPUT_GAMEPORT=m
CONFIG_INPUT_NS558=m
# CONFIG_INPUT_LIGHTNING is not set
# CONFIG_INPUT_PCIGAME is not set
# CONFIG_INPUT_CS461X is not set
# CONFIG_INPUT_EMU10K1 is not set
# CONFIG_INPUT_SERIO is not set
# CONFIG_INPUT_SERPORT is not set
CONFIG_INPUT_ANALOG=m
# CONFIG_INPUT_A3D is not set
# CONFIG_INPUT_ADI is not set
# CONFIG_INPUT_COBRA is not set
# CONFIG_INPUT_GF2K is not set
# CONFIG_INPUT_GRIP is not set
# CONFIG_INPUT_INTERACT is not set
# CONFIG_INPUT_TMDC is not set
# CONFIG_INPUT_SIDEWINDER is not set
# CONFIG_INPUT_IFORCE_USB is not set
# CONFIG_INPUT_IFORCE_232 is not set
# CONFIG_INPUT_WARRIOR is not set
# CONFIG_INPUT_MAGELLAN is not set
# CONFIG_INPUT_SPACEORB is not set
# CONFIG_INPUT_SPACEBALL is not set
# CONFIG_INPUT_STINGER is not set
# CONFIG_INPUT_DB9 is not set
# CONFIG_INPUT_GAMECON is not set
# CONFIG_INPUT_TURBOGRAFX is not set
# CONFIG_QIC02_TAPE is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_IPMI_PANIC_EVENT is not set
# CONFIG_IPMI_DEVICE_INTERFACE is not set
# CONFIG_IPMI_KCS is not set
# CONFIG_IPMI_WATCHDOG is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_SCx200_GPIO is not set
# CONFIG_AMD_RNG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_AMD_PM768 is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# 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_INTEL is not set
# CONFIG_AGP_I810 is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD_8151 is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_SWORKS is not set
CONFIG_DRM=y
# CONFIG_DRM_OLD is not set
CONFIG_DRM_NEW=y
CONFIG_DRM_TDFX=y
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I810_XFREE_41 is not set
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BEFS_DEBUG is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_UMSDOS_FS=m
# CONFIG_VFAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_TMPFS is not set
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
# CONFIG_JFS_FS is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_MINIX_FS=m
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_EXT2_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=m
# CONFIG_NFS_V3 is not set
# CONFIG_ROOT_NFS is not set
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=m
CONFIG_LOCKD=m
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
CONFIG_ZISOFS_FS=m

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

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# 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 is not set
# 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

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
# CONFIG_VIDEO_SELECT is not set
# CONFIG_MDA_CONSOLE is not set

#
# Frame-buffer support
#
# CONFIG_FB is not set

#
# Sound
#
CONFIG_SOUND=m
# CONFIG_SOUND_ALI5455 is not set
# CONFIG_SOUND_BT878 is not set
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_EMU10K1 is not set
# CONFIG_MIDI_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_FORTE is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_RME96XX is not set
# 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_MIDI_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 is not set
# CONFIG_SOUND_TRIX is not set
# CONFIG_SOUND_MSS is not set
# CONFIG_SOUND_MPU401 is not set
# CONFIG_SOUND_NM256 is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_SOUND_PAS is not set
# CONFIG_PAS_JOYSTICK is not set
# CONFIG_SOUND_PSS is not set
CONFIG_SOUND_SB=m
# CONFIG_SOUND_AWE32_SYNTH is not set
# CONFIG_SOUND_KAHLUA is not set
# CONFIG_SOUND_WAVEFRONT is not set
# CONFIG_SOUND_MAUI is not set
CONFIG_SOUND_YM3812=m
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_OPL3SA2 is not set
# CONFIG_SOUND_YMFPCI is not set
# CONFIG_SOUND_YMFPCI_LEGACY is not set
# CONFIG_SOUND_UART6850 is not set
# CONFIG_SOUND_AEDSP16 is not set
# CONFIG_SOUND_TVMIXER is not set

#
# USB support
#
CONFIG_USB=m
# CONFIG_USB_DEBUG is not set
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_EHCI_HCD is not set
# CONFIG_USB_UHCI is not set
CONFIG_USB_UHCI_ALT=m
# CONFIG_USB_OHCI is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_BLUETOOTH is not set
# CONFIG_USB_MIDI is not set
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
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_CATC is not set
# CONFIG_USB_CDCETHER is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_USS720 is not set

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_TIGL is not set
# CONFIG_USB_BRLVGER is not set
# CONFIG_USB_LCD is not set

#
# Bluetooth support
#
# CONFIG_BLUEZ is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set

#
# Library routines
#
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=y