Linux-Hardware Digest #59, Volume #14 Tue, 19 Dec 00 18:13:04 EST
Contents:
Re: adaptech AAA-131 RAID support (Markus Kossmann)
Re: Which kind of netcard is best support in Linux? ([EMAIL PROTECTED])
Re: ATI Rage Fury (Robert)
Re: Intel Easy PC camera - cannot be supported in Linux! ([EMAIL PROTECTED])
Re: Soundblaster 16 PCI (Joshua Beard)
Re: Sound Blaster not working (Higgins)
scanner (galaxy)
Re: Western Digital WD450AA 45GB and linux (Tore Ferner)
Re: Hercules 3D Prophet (Jasper Spit)
Re: Help me choose a motherboard! ("Monte")
Re: scanner ("Frederik Himpe")
Re: Intel Easy PC camera - cannot be supported in Linux! (A transfinite number of
monkeys)
Re: Iomega 250 USB Zip? (Chris Rankin)
Re: dying courier modem? ("cs")
Re: Intel Easy PC camera - cannot be supported in Linux! ([EMAIL PROTECTED])
Re: Hard disk partition problem (Mark Post)
Adaptec aic 7770 scsi controller (Travis Stevens)
Re: Intel Easy PC camera - cannot be supported in Linux! ([EMAIL PROTECTED])
Western Digital hard drive problem (James Johnson)
----------------------------------------------------------------------------
From: Markus Kossmann <[EMAIL PROTECTED]>
Subject: Re: adaptech AAA-131 RAID support
Date: Tue, 19 Dec 2000 19:03:43 +0100
Brett Wilks wrote:
>
> Has ayone no if this is supported I have looked on RH but I hve confiliction
> infromation.
>
It's not supported . The kernel configuration help for the aic7xxx
driver says:
[...]
> It does not support
> the AAA-13x RAID controllers from Adaptec, nor will it likely ever
> support them
[...]
> In general, if the controller is based on an Adaptec SCSI
controller
> chip from the aic777x series or the aic78xx series, this
driver
> should work. The only exception is the 7810 which is
specifically
> not supported (that's the RAID controller chip on the
AAA-13x
> cards).
--
Markus Kossmann
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Which kind of netcard is best support in Linux?
Date: Tue, 19 Dec 2000 19:05:52 GMT
I've used SOHOware's 10/100 PCI card using the newer tulip driver
without a problem. For older kernels the card comes with a Linux driver
on it's disk and easy instructions. This card costs about $20. I've
used a total of 5 of these cards in both Linux and Windows machines
without a problem.
In article <91fcou$jf0$[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> most stable and best support ?
>
> Sent via Deja.com
> http://www.deja.com/
>
Sent via Deja.com
http://www.deja.com/
------------------------------
From: Robert <[EMAIL PROTECTED]>
Subject: Re: ATI Rage Fury
Date: Tue, 19 Dec 2000 20:10:50 +0100
Reply-To: [EMAIL PROTECTED]
thanks it'll take a time cause the box using ATI is not mine but a
friend's
but i'll post the results when i work on it. where can i find this kind
of
documentation? www.xfree86.org doesnt have much...
Doug Kramer wrote:
>
> You have the ruby slipper's! Just rerun your xf86config and select the ATI
> Wonder SVGA. When you select the ATI Wonder SVGA server, your actually
> selecting the xf86_SVGA with the r128 driver.
>
> Here is what XFree86.org said pertaining to the ATI:
>
> 6. ATI
>
> 3.3.6:
> Accelerated support is provided for the Mach8 chips (by the XF86_Mach8
> server), Mach32 chips (by the XF86_Mach32 server), the following Mach64 and
> Rage chips: GX, CX, CT, ET, VT, VT3, GT, RageII+DVD, RagePro (GB, GD, GI,
> FP, GQ), VT4, Rage IIC (GV, GW, GZ), Rage LT Pro (LD, LB, LI, LP), Rage LT,
> Rage XL or XC (GL, GM, GN, GO, GR, GS) and Rage Mobility (LM, LN, LR, LS)
> (by the XF86_Mach64 server). Unaccelerated support is provided for most of
> the above (except some early Mach8 and Mach32 adapters), as well the old
> VGAWonder series chipsets (18800, 18800-1, 28800-2, 28800-4, 28800-5,
> 28800-6) by the XF86_SVGA server with the ati driver. Accelerated support is
> provided for the Rage 128 chips by the XF86_SVGA server with the r128
> driver.
>
> 4.0.1:
> Accelerated support is provided for the Rage 128 chips by the "r128" driver.
> Accelerated support is provided for the Mach64 Rage variants by the "ati"
> driver. Unaccelerated support is provided for all of the others except the
> Mach8 and some early Mach32 chips by the "ati" driver.
>
> Summary:
> All chips supported in 3.3.6 are supported in 4.0.1 except for Mach8 and
> some old Mach32 chips. The support in 4.0.1 is, however, unaccelerated for
> all chips except the Mach64, Rage and Rage 128 variants.
>
> Post a reply I would like to know how it worked out.
>
> "Robert" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > no i think my chipset is mach64 but is worth trying anyway,
> > where can i get it?
> >
> > Doug Kramer wrote:
> > >
> > > I am having problems with mine so I don't have room to talk!
> > >
> > > But wouldn't you want to install ATI Wonder SVGA server for your Rage
> 128
> > > chip? I thought that's what XFree86 suggested for this ATI hardware
> instead
> > > of the old Mach64 server under version 4.01.
> > >
> > > You want the R128 driver.
> > >
> > > "Robert" <[EMAIL PROTECTED]> wrote in message
> > > news:[EMAIL PROTECTED]...
> > > > i've tried lots of things on xf86config, perhaps a lower-level
> > > > configuration
> > > > can solve the problem. and what about the xserver? i'm using the
> mach64
> > > > server
> > > > and i've set the card to number 104 in xf86config, does it matter?
> > > >
> > > > James Richard Tyrer wrote:
> > > > >
> > > > > Robert wrote:
> > > > >
> > > > > > Hi all!
> > > > > > anyone been succesful on configuring an ATI Rage Fury under
> xfree86
> > > > > > 4.0.1?
> > > > > > i actually can only get 640x480, which is *pathetic*
> > > > >
> > > > > At the risk of being redundant:
> > > > >
> > > > > Section "Screen"
> > > > > Identifier "Screen 1"
> > > > > Device "ATI Rage IIC"
> > > > > Monitor "NEC MultiSync3V"
> > > > > DefaultDepth 24
> > > > >
> > > > > Subsection "Display"
> > > > > Depth 24
> > > > > Modes "1024x768"
> > > > > ViewPort 0 0
> > > > > EndSubsection
> > > > > EndSection
> > > > >
> > > > > Ad some other Modes if you want, need, and you monitor can support
> them.
> > > > >
> > > > > But this isn't enough, you have to have the proper horizontal
> refresh
> > > > > and vertical sync rates. And, don't enter something that your
> monitor
> > > > > won't handle or you may give new meaning to the term "smoke test".
> > > > >
> > > > > Section "Monitor"
> > > > >
> > > > > Identifier "NEC MultiSync3V"
> > > > >
> > > > > HorizSync 31.5 - 48.5
> > > > >
> > > > > VertRefresh 50-70
> > > > >
> > > > > EndSection
> > > > >
> > > > > The above range will support 1024 x 768.
> > > > >
> > > > > These are copies from my XFree86Config file.
> > > > >
> > > > > And, I presume that your driver (device) is also correct:
> > > > >
> > > > > Section "Device"
> > > > > Identifier "ATI Rage IIC"
> > > > > Driver "ati"
> > > > > #VideoRam 4096
> > > > > EndSection
> > > > >
> > > > > The documentation says not to tell it how much VRAM you have unless
> it
> > > > > can't figure it out for itself -- put in the figure, but leave it
> > > > > commented out.
> > > > >
> > > > > JRT
> >
> > --
> >
> > Have a lot of fun!
--
This is a .signature virus. Please add me to your signature file and
help me live
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.advocacy,alt.linux.sux
Subject: Re: Intel Easy PC camera - cannot be supported in Linux!
Reply-To: [EMAIL PROTECTED]
Date: Tue, 19 Dec 2000 19:29:57 GMT
On Tue, 19 Dec 2000 12:35:51 -0500, mlw <[EMAIL PROTECTED]> wrote:
>Taking your post as a whole, I have a much better definition of a
>retard. Someone who comes to conclusions based on unrelated facts.
It's the end result that matters, not how one arrived or didn't arrive
at it.
In this case the end result is taking pictures with a camera.
Windows can utilize the hardware, and as usual Linux can't.
>Whether or not Intel decides to support Linux for their camera, has
>nothing to do with the quality of linux. As a point of technical review,
>it would be a hard sell to even suggest that Windows is better than
>Linux in any respect. Windows isn't even a real operating system.
Who cares if Windows is a basket of apples?
The point is Whatever the technical definition of Windows is or isn't,
Windows is able to use the camera, and quite a bit of other hardware
designed for the home user, and Linux as usual, can't.
All the dictionaries in the world will are not going to make the poor
bastard saddled with Linux be able to use his hardware.
>Claiming quality concerns over vendor support for a cheap camera, is
>like saying a Mercedes is crap because Holley doesn't make a fuel
>injection system for it.
It has nothing to do with quality.
It has everything to do with taking pictures with a camera.
Windows for all of it's faults can do it, and Linux in this case (and
many others BTW) can't.
>> The Linux users need a reality check to see how much they are missing
>> since they last used Windows circa 3.0
>
>I use Linux instead of Windows for many reasons. Mostly because I want
>to focus on my work, not the stupidity of rebooting.
Use what works for you.
Linux doesn't work for quite a lot of people and that is why it is
virtually non-existant on the desktop of home users and will continue
to stay that way.
Flatfish
Why do they call it a flatfish?
Remove the ++++ to reply.
------------------------------
From: Joshua Beard <[EMAIL PROTECTED]>
Subject: Re: Soundblaster 16 PCI
Date: Tue, 19 Dec 2000 13:41:48 -0600
>From my experience, Linux does great with Sound Blaster cards, especially
Sound Blaster 16. I haven't tried a SB16 PCI, but I have been using an ISA
for months now and it does great (except the fact that it's an old card.)
Try running sndconfig like this:
sndconfig --noprobe
and see If you can manually configure it that way. If it tries to
autoconfigure it for you, try:
sndconfig --noprobe --noautoconfig
man sndconfig for more details.
Good luck,
Josh.
Anthony Hung wrote:
> Hi all,
>
> I just got a soundlbaster 16 PCI and my system doesn't seem to be able to
> recognize it. I am using redhat linux... linux 2.2. I ran sndconfig and it
> says does not recognize Ensoniq 1274:5880... strange. Just want to know
> if linux supports this before I make a lot of effort recompiling the
> kernel and stuff....
>
> thanks!
>
> Anthony
------------------------------
From: Higgins <[EMAIL PROTECTED]>
Subject: Re: Sound Blaster not working
Crossposted-To: alt.os.linux,comp.os.linux,comp.os.linux.help
Date: Tue, 19 Dec 2000 21:18:42 +0200
On Mon, 18 Dec 2000, Chris wrote:
>I installed this oss package, and it all went smoothly, except there was an
>error running soundon, and in the log file it says: sb: dsp reset failed
>
>Oh yes, the sound still doesn't work either...
If you have before Oss tryed with Alsaconf, try :
1.Delet the alsa entries (in the end?) of the /ect/modules.conf
2. Delet the soundmodules with: rcalsasound stop
3. Reboot the computer
4.(Re)install Oss ( right version for your kernel !!!!) to /usr/lib/oss
.
5. To boot Oss : /usr/lib/oss/soundon .
After configuration typing in
/sbin/init.d/boot.local this line : /usr/lib/oss/soundon
SuSE support was send these instructions to me, and "I have heard the sound"...
Higgins
------------------------------
From: galaxy <[EMAIL PROTECTED]>
Subject: scanner
Date: Tue, 19 Dec 2000 14:47:55 -0500
Hi! I would like to know what brand scanner machine which can work on
linux. I need to know what brand of scanner do you recommand?
Thanks
------------------------------
From: Tore Ferner <[EMAIL PROTECTED]>
Subject: Re: Western Digital WD450AA 45GB and linux
Date: Tue, 19 Dec 2000 21:05:13 +0100
Erling R Elvsrud wrote:
>
> In article <8vd8fk$2ik$[EMAIL PROTECTED]>, Erling R Elvsrud wrote:
> >I have just ordererd a WD450AA hd, and somewhere I red that it has
> >some problems when used with linux, something with dma transfers and
> >errror correction anyone have tried this drive?
> >should I exhange it for a IBM or something?
> >It is important that it is a silent drive.
> >As I mainly use linux I cannot have a drive that don't work properly
> >with dma, on wd's web site It was mentioned in a faq but they blamed
> >linux for all the problems..
> >
> >It it possible to use this drive properly with linux?
> >
>
> I have tried it and it seems to work well, also with dma.
> No problems at all so far.
Which kernel are you using?
Tore
------------------------------
From: Jasper Spit <[EMAIL PROTECTED]>
Subject: Re: Hercules 3D Prophet
Date: Tue, 19 Dec 2000 21:43:57 +0100
Markus Kiener wrote:
> Hello!
>
> I try to install Red Hat 7 and it seems that it does not support my 3D
> Prophet. I could not find it on the Red Hat Hardware Website. Any idea
> without changing graphic card?
You need XFree 4.0.1 instead of XFree 3.3.x. Take a look at www.xfree86.org.
Jasper
------------------------------
From: "Monte" <[EMAIL PROTECTED]>
Crossposted-To: alt.comp.hardware.homebuilt
Subject: Re: Help me choose a motherboard!
Date: Tue, 19 Dec 2000 20:43:19 GMT
You might want to read this before you buy, I like my KT7 Raid but it
doesn't seem to like Mandrake Linux 7.2. Take a little time and read the
article, I didn't go through the whole thing, not running Linux.
>From Paul's Unofficial ABIT KT7 Faq:
Why can't I install Mandrake Linux 7.2 on my KT7?
There appears to be a problem with the Mandrake Linux 7.2 distribution
concerning the use of DMA. Although this has only reported on the Abit KA7
it is likely to also apply to the KT7. A solution is provided by Pete
McDonnell's Linux Tips.
http://www.petey.org/linuxtips.html#tip1
------------------------------
From: "Frederik Himpe" <[EMAIL PROTECTED]>
Subject: Re: scanner
Date: Tue, 19 Dec 2000 20:46:59 GMT
In article <[EMAIL PROTECTED]>, "galaxy"
<[EMAIL PROTECTED]> wrote:
> Hi! I would like to know what brand scanner machine which can work on
> linux. I need to know what brand of scanner do you recommand? Thanks
Have a look at this site and check wich scanners are supported by Sane:
http://www.mostang.com/sane/
Greetings,
Frederik
--
Frederik's Linux-Mandrake Experience Story
http://www.mandrakestory.cjb.net
------------------------------
From: [EMAIL PROTECTED] (A transfinite number of monkeys)
Crossposted-To: comp.os.linux.advocacy,alt.linux.sux
Subject: Re: Intel Easy PC camera - cannot be supported in Linux!
Date: Tue, 19 Dec 2000 21:20:16 GMT
On Tue, 19 Dec 2000 16:43:00 GMT,
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
: You can argue till you are blue in the face about the evil hardware
: manufacturers withholding specs but it still boils down to the same
: thing.
:
: Linux sucks at supporting modern hardware.
Obviously why on my PC, such "archaic" hardware as:
SoundBlaster Live!
Creative Annihilator 2 (GeForce 2 GTS based card)
Micro$oft USB Intellimouse
IBM (really Xirlink) USB Camera
HP LaserJet 2100M
Adaptec 2940UW
Asus CUSL2 (i815e based) motherboard
3com 3c905 NIC
USB Zip 250
Jaz 1G
all work without a hitch, right? Yeah, all of that stuff is ancient, right?
--
Jason Costomiris <>< | Technologist, geek, human.
jcostom {at} jasons {dot} org | http://www.jasons.org/
Quidquid latine dictum sit, altum viditur.
------------------------------
From: Chris Rankin <au.zipworld.com@{no.spam}rankinc>
Subject: Re: Iomega 250 USB Zip?
Date: Wed, 20 Dec 2000 08:22:58 +1100
Chris Rankin wrote:
> The 2.2.18 kernel has USB support, but don't expect the USB ZIP drive to
> work because this device really needs the Linux 2.4 SCSI layer as well.
> This layer has *not* been backported.
LNyT wrote:
> Actually, I got mine to work with the 2.2.18 kernel :) The modules that
> need to be compiled specifically for the Zip250 USB are SCSI support, SCSI
> emulation and USB Mass Storage.
Well, I obviously hadn't tried to use a 250 MB USB ZIP drive ... ;-) The
source of my advice was the FAQs on www.linux-usb.org, which I guess
must be out of date.
Having said that, though, the 2.4 kernel does support an option for
scsi_mod.o called "scsihosts". This allows you to permanently associate
each SCSI host adapter with a SCSI controller number, and is quite handy
if you have to load multiple SCSI host adapter modules.
Chris
------------------------------
From: "cs" <[EMAIL PROTECTED]>
Crossposted-To: comp.dcom.modems
Subject: Re: dying courier modem?
Date: Tue, 19 Dec 2000 15:24:33 -0600
> Unfortunately, the Courier firmware haven't been upgraded for a
> long time.
So what do you think is better?
charles....
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.advocacy,alt.linux.sux
Subject: Re: Intel Easy PC camera - cannot be supported in Linux!
Reply-To: [EMAIL PROTECTED]
Date: Tue, 19 Dec 2000 21:55:58 GMT
On Tue, 19 Dec 2000 21:20:16 GMT, [EMAIL PROTECTED] (A transfinite
number of monkeys) wrote:
>
>Obviously why on my PC, such "archaic" hardware as:
>
>SoundBlaster Live!
Tell me how you get surround sound, or digital audio via the digital
audio spid/f connector under Linux?
Tell me about LiveWare for Linux?
Supported?
It's supported when I can read the outside of the box and use all of
the features I paid for under Linux.
Until then, you have no idea what you are missing by running a halfway
decent sound card under an inferior operating system like Linsux.
>Creative Annihilator 2 (GeForce 2 GTS based card)
And you get full use of all the 3d stuff and acceleration under Linux?
>Micro$oft USB Intellimouse
>IBM (really Xirlink) USB Camera
>HP LaserJet 2100M
>Adaptec 2940UW
>Asus CUSL2 (i815e based) motherboard
>3com 3c905 NIC
>USB Zip 250
>Jaz 1G
>
>all work without a hitch, right? Yeah, all of that stuff is ancient, right?
Big deal. Windows supports them as well, and all of the software that
comes with them works the way it is supposed to, as well as the
special offer software (I got Wordperfect Office 2000 professional for
$8.00 when I bought my Lexmark printer) works as well. With Linux you
get to use software that looks like it was written 10 years ago.
Flatfish
Why do they call it a flatfish?
Remove the ++++ to reply.
------------------------------
From: [EMAIL PROTECTED] (Mark Post)
Subject: Re: Hard disk partition problem
Date: Tue, 19 Dec 2000 22:23:26 GMT
On Sat, 16 Dec 2000 16:15:54 +0000, Richard Kimber <[EMAIL PROTECTED]>
wrote:
>I have a problem with my Mandrake 7.2 SCSI Buslogic system
>After re-seizing my partitions on my first disk, using Partition Magic in
>win95, I should have
>sda3 (vfat)
>sda4 (hpfs: OS/2a)
>sda5 (hpfs: OS/2b)
>sda6 (linux swap)
>my root is on sdb5 and linux seems to recognise the second disk OK.
>Partition Magic doesn't show any errors.
>However, linux complains that /dev/sda4 isn't a valid block device, and it
>mounts OS2a as /dev/sda5 and doesn't mount the two other partitions. It
>seems to want to recognise the swap as /dev/sda7. I.e. sda4 seems just to
>have "disappeared". It looks OK in /dev
Based on the device numbers sda5 and sda6, I would guess that you have one
extended partition, with several logical partitions within it. The extended
partition is most likely partition #4, which means that the first, second,
etc. logical partitions within it would be /dev/sda5, /dev/sda6, etc.
Mark Post
Postmodern Consulting
Information Technology and Systems Management Consulting
To send me email, replace 'nospam' with 'home'.
------------------------------
From: Travis Stevens <[EMAIL PROTECTED]>
Subject: Adaptec aic 7770 scsi controller
Date: Tue, 19 Dec 2000 15:28:26 -0700
Well, does anyone have this problem? I have an hp netserver (old)
and it has one Adaptec aic 7770 scsi controller. I need it to work in
order to install redhat 6.2. I can install turbolinux, and open BSD,
but I can't get the controller to work with redhat 6.2. Any
suggestions?
-Trav
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.advocacy,alt.linux.sux
Subject: Re: Intel Easy PC camera - cannot be supported in Linux!
Reply-To: [EMAIL PROTECTED]
Date: 20 Dec 2000 09:26:53 +1100
[EMAIL PROTECTED] writes:
>On Tue, 19 Dec 2000 12:35:51 -0500, mlw <[EMAIL PROTECTED]> wrote:
>In this case the end result is taking pictures with a camera.
>Windows can utilize the hardware, and as usual Linux can't.
Hmm, that sounds strangely familiar. Only the roles were reversed.
The ultra-cheap package of CMOS video camera and BT848-based capture card
I bought earlier this year never worked under Windows. Just wouldn't.
No go.
Good thing I didn't want to use it under Windows, anyway. It runs perfectly
under linux, once a bit of trial and error had determined which card type
I had to give the driver. You'd think that the Windows driver on the
CD that came with it would get it right, but no, apparently not. And it,
of course, doesn't take any parameters.
Does this mean that Windows is an "inferior OS"? I don't think so --- it
just means that this particular piece of junk is not supported by Windows,
despite claims to the contrary on the package. No more, and no less.
>Linux doesn't work for quite a lot of people and that is why it is
>virtually non-existant on the desktop of home users and will continue
>to stay that way.
I recently decided that I needed to install a slightly more up-to-date
distribution on one of my machines (people had been sending me bug reports
about some software of mine, and they seemed libc related). So I got
Mandrake 7.2 at the local swapmeet.
If I ever have a Windows installation that goes that smoothly, I shall
mark the day in my calendar with a big red circle. But don't hold your
breath.
While I was at it, I decided to also give the machine a performance boost,
and replaced the aging Celeron400 on a BP6 with a Duron running at 950MHz,
on a Soyo board. Then I put the Windows drive back onto the EIDE controller.
Oh my! It discovered lots and lots of new hardware (most of which wasn't
really all that new), but I expected that. What I didn't expect was the
total fit it threw over networking. OK, I got two ethernet cards in the
machine, but that certainly isn't *that* unusual. And it certainly isn't
an excuse for filling the routing table with half a dozen routes that
connect to interfaces I don't have, and the addresses for which appear
pretty much random. And not letting me delete those routes is extra naughty.
I ended up reinstalling from scratch, after trying to convince the stupid
thing in many ways that 169.254.114.118 (or something along those lines)
was not one of my interfaces, or at least that 192.168.243.32 *is* one
of them.
Does that mean Windows is inferior to Mandrake 7.2? I don't think so.
It just isn't very good at dealing with changing hardware. It isn't
very good at a whole lot of things, just like Linux. And it's quite
good at some others, just like Linux. And all the anecdotal evidence
in the world won't change that.
Bernie
P.S.: Welcome back, heather69. I suspect you will regale us with stories
about your retail experience in "major chainstores", and how
Linux is the "numero uno" returned item, right? What will your
relation to the manager be this time? Will she be your aunt? Your
daughter? Your brother's wife?
--
How you, rebellious Germany, laid your wretched head beneath the
feet of the great general
Ovid
Roman poet, 43 BC -- AD 17
------------------------------
From: James Johnson <[EMAIL PROTECTED]>
Subject: Western Digital hard drive problem
Date: Tue, 19 Dec 2000 17:59:14 -0500
I have a WD102AA IDE drive that generates some errors on bootup:
...
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xe000-0xe007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xe008-0xe00f, BIOS settings: hdc:DMA, hdd:DMA
hda: WDC WD102AA, ATA DISK drive
hdc: TOSHIBA CD-ROM XM-6302B, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: WDC WD102AA, 9787MB w/2048kB Cache, CHS=9942/32/63, (U)DMA
hdc: ATAPI 32X CD-ROM drive, 256kB Cache, DMA
...
Partition check:
hda:hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
ide_dmaproc: chipset supported ide_dma_timeout func only: 14
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: DMA disabled
ide0: reset: success
hda1 hda2
...
Once the machine boots, the drive appears to work correctly. Any ideas on
what's going on and how to fix it?
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.hardware.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
