It seems Matthew Dillon wrote:
>
> Here's some more info. If the dd is stuck and systat -vm 1 is showing
> no interrupts occuring on, for example, ahc2 (irq17), and I then do
> something that causes an interrupt to occur on mux (irq19), which I
> guess is ahc1, ahc2 then starts
It seems Dag-Erling Smorgrav wrote:
> Richard Tobin <[EMAIL PROTECTED]> writes:
> > Is that relevant for 3.2 as well as current? And by "disabling ultra
> > DMA" did you mean "disabling UDMA66" or "disabling UDMA completely"?
> > (You can permanently disable UDMA66 with a DOS utility available
>
It seems Dag-Erling Smorgrav wrote:
> "Brian F. Feldman" <[EMAIL PROTECTED]> writes:
> > On 4 Jul 1999, Dag-Erling Smorgrav wrote:
> > > Depends on your motherboard. Try to just disable UDMA66 first. If that
> > > doesn't help, or if you have a "known bad" chipset (e.g. AcerLabs
> > > Aladdin), di
It seems Nick Hibma wrote:
> > > I should have said "known bad configuration". I know Søren's ATA
> > > driver supports UDMA on the Aladdin, but I don't have the luxury of
> > > expendable file systems, so I don't use it. I also think it's the
> > > wrong direction to go off in; if we're going
It seems Peter Wemm wrote:
> > Well, CAM & ATAPI is "fairly" easy, the only problem being all the
> > little details that are different enough to make it non-trivial to
> > maintain. I once sat down and tried to get all the details on how
> > the CCB's where different, and decided that I wouldn't
It seems Thomas Schuerger wrote:
> Hi!
>
> I've set the option
>
> IDE_DELAY=1500
>
> and compiled and installed my kernel (I even did config -r
> before that), but when booting, the IDE driver still waits
> for about half a minute before continuing, instead for
> about 1.5 seconds. Has anyon
It seems Mike Hoskins wrote:
> and I just installed a Promise Ultra66. Here's my relevant kernel config
> stuff (following LINT's example):
>
> pci0: unknown card DBZ4d38 (vendor=0x105a, dev=0x4d38) at 14.0 irq 9
Thats the promise controller, try the ata driver instead an use the
following patc
It seems Kazutaka YOKOTA wrote:
>
> >I have switched graphics card from S3Virge to ATI Mach64 RagePro rev 92
> >with 8 MB RAM a I have noticed that VESA module doesn't work with this
> >graphics card on my -current box - I can't use VESA_XXX console modes now.
> >Command kldstat says there is loa
It seems Cejka Rudolf wrote:
>
> Soren Schmidt wrote (1999/08/09):
>
> > It seems Kazutaka YOKOTA wrote:
> > > There is a good possibility that the VESA BIOS extension for this card
> > > is provided in a DOS TSR program and the VESA BIOS entry in the ROM
It seems Doug White wrote:
> > >
> > > > FWIW - I enabled APM over the weekend, configuring drives to
> > > > spin down when not used for a good period of time. I get the
> > > > message you list below, alternately with status 50 and 58, any
> > > > time a drive needs to spin up.
> > >
> >
It seems Francis Jordan wrote:
> /kernel: acd0: CDROM drive at ata1 as master
> /kernel: acd0: drive speed 4134KB/sec, 128KB cache
> /kernel: acd0: supported read types: CD-R, CD-RW, CD-DA
> /kernel: acd0: Audio: play, 256 volume levels
> /kernel: acd0: Mechanism: ejectable tray
> /kernel: acd0:
It seems Thierry Herbelot wrote:
> Soren Schmidt wrote:
> >
> [SNIP]
> >
> > That can't be true, at least not for the IBM DeskStars I own, I've
> > NEVER EVER seen them do that, one proof should be:
>
> same here
>
> wdc0: unit 0 (wd0): ,
It seems Geoff Rehmet wrote:
> Brian McGroarty writes :
> > In using the ATA driver, I'm unable to automatically mount a
> > partition on a master drive on the secondary controller. fsck
> > complains that device rwd2s1e isn't configured and exists.
> > Immediately mounting by hand works perfectly
It seems Francis Jordan wrote:
> Yes, HDD on the primary, CD-ROM on the secondary controller. This is a
> notebook I'm talking about, so I haven't tried any other CD-ROM drives.
> If it doesn't respond at all, then how do you get all the other
> information, such as supported read types, speed,
It seems Geoff Rehmet wrote:
> Hmm,
>
> My root device still lands up on "wd0" - even though my fstab has
> the root filesystem on ad0s1a. I haven't looked at getting it to
> use the ad dev entries for the root file system. (I'm assuming that
> is still WIP.)
Our boot blocks/loader dont have t
It seems Francis Jordan wrote:
> Soren Schmidt wrote:
> >
> > Hmm try the patch below so we can tell what command it is failing on..
>
> After removing the quotation mark after the word command in the above
> patch (smile), it prints:
Yeah, so much for writing c
It seems Thierry Herbelot wrote:
> Soren Schmidt wrote:
> >
> [SNIP]
> >
> > Have you tried putting disks on the UDMA66 channel ?? I think it
> > should work in upto WDMA mode now with the ata driver...
>
> I have first to install 4.0 and from my wd2 (I
It seems Mike Smith wrote:
> > Our boot blocks/loader dont have the needed computrons to use the
> > "ad" device name. However I have some patches to boot2 that allows
> > to boot off an ad root device, provided you dont use the loader, and
> > put the rigth boot string in boot.config.
>
> This s
It seems Nicolas Souchu wrote:
> acd0: CDROM drive at ata0 as master
> acd0: drive speed 0KB/sec
> acd0: supported read types:
> acd0: Mechanism: caddy
> acd0: Medium: CD-ROM unknown medium
>
> Any clue?
>
> The drive was running flawlessly with the old wdc driver and with various
> primary rel
It seems Valentin S. Chopov wrote:
>
> It seems there is something for
>
> #if NPCI > 0 ... #endif
Yup, forgot that one, fixed.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Brian Fundakowski Feldman wrote:
> I just noticed a problem with the ATA driver with my (not quite, but to me)
> new CD-R drive. The behavior is that underruns and overruns are handled
> incorrectly, due to a mixup between variables. The end result is that
> too much data is sent to the
It seems Brian Fundakowski Feldman wrote:
> On Tue, 4 Jan 2000, Soren Schmidt wrote:
>
> > Either the patch is very short, or you forgot to include it :)
>
> *LOL* I can't believe I did that :) It'll be on this one!!
Yup, this time there is a patch :)
> > T
It seems Alex wrote:
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0xbff21000
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc0214ffe
> stack pointer = 0x10:0xc02f6b58
> frame pointer = 0x10:0xc0
It seems Marc Schneiders wrote:
> Where do I look for new man pages? I would like to read those for the
> new ata driver and for ntpd. They were not created during a build
> world some 5 days ago. And I cannot find them in
> /usr/src/share/man/man4, where I would expect man ata/ad in any case.
Th
It seems Brian Fundakowski Feldman wrote:
>
> I used a multiple of the blocksize, and it works fine, except for on
> the very last bit of data. The very last bit of data is what causes
> an underrun, and the code that's there for overrun/underrun is
> wrong right now. For underrun, it ends up w
It seems Kris Kennaway wrote:
> One of my Western Digital Caviars doesn't work under the new ATA driver:
> upon trying to access the disk (via swapon or mount during boot) it gives
> the famous "lost contact with disk" message and falls back to PIO mode.
> Interestingly, my two older WDCs work fin
It seems Kris Kennaway wrote:
> On Wed, 5 Jan 2000, Soren Schmidt wrote:
>
> > The disk probably has problems with DMA mode (lots of older WD disks
> > has that). You only get WDMA2 mode since you controller is an older
> > Intel PIIX that can't do UDMA...
>
>
It seems Peter Jeremy wrote:
> I just discovered that my ATAPI CD-ROM is no longer usable - when I
> try to mount it, my maching hangs (hard).
>
> I'm running -current from cvs-cur 5961 (Monday about UTC).
>
> The symptoms are:
>
> Run "mount -r /dev/acd0c /cdrom"
> The CD-ROM activity ligh
It seems Brian Fundakowski Feldman wrote:
> How about this? It's mostly the changes in your patch, but it also takes
> into account non-int{8,16}_t-sizing/alignment. It also takes care of the
> truncation problem when you use outsl and insl, as part of that. Please
> review it, as I think it sh
It seems Brian Fundakowski Feldman wrote:
>
> It's just as well. It's almost 4 AM and I've just about given up on getting
> this all working. Anyway, if everything has to be DEV_BSIZE, then I guess
> that would simplify things, except when I try, say, writing 4697 bytes
> as an audio blocksize (
I've just done a replacement for wormcontrol that allows burning CDR/CDRW
with just one command. Its simpleminded but it works.
Just a FYI as I know several people have said they where thinking
about doing such a thingy.
The API to the kernel has changed too, finally I got around to cleaning
up
It seems Luigi Rizzo wrote:
> [Charset ISO-8859-1 unsupported, filtering to ASCII...]
> >
> > I've just done a replacement for wormcontrol that allows burning CDR/CDRW
> > with just one command. Its simpleminded but it works.
> >
> > Just a FYI as I know several people have said they where think
It seems Luigi Rizzo wrote:
> > > > I've just done a replacement for wormcontrol that allows burning CDR/CDRW
> > > > with just one command. Its simpleminded but it works.
>
> btw for the records -- on 2.2.x i noticed i needed some wait between
> the transfer of data to CDR, and the "fixate" comm
I've just committed burncd the wormcontrol replacement.
The ATAPI burner API has changed, so wormcontrol does
no longer work, use burncd instead (see burncd.8)
The DVD ioctl's has changed numbers, so those using that
should recompile thier apps.
Wormcontrol and related files will be removed soo
It seems Alexander Langer wrote:
> Thus spake Soren Schmidt ([EMAIL PROTECTED]):
>
> > The DVD ioctl's has changed numbers, so those using that
> > should recompile thier apps.
> > Wormcontrol and related files will be removed soon.
>
> I saw changes for the
It seems Matthew Dillon wrote:
>
> :From what I can tell so far, something during the kernel boot is
> :disabling the timer interrupt. The ATA probe does a tsleep() which
> :never times out. Output is queued to the console during the boot
> :sequence which is never printed (unti
It seems Peter Jeremy wrote:
> On 2000-Jan-06 10:38:51 +1100, I wrote:
> ["dd if=/dev/rad0c of=/dev/null bs=64k" dies with an error]
>
> I did some poking around and found that there are two bugs which
> conspire together to cause this:
> 1) diskstrategy() does not detect dscheck() returning EOF,
It seems Alexander Langer wrote:
> > > ata* doesn't work for me at the moment, thus I'm using the wd drivers.
> > What is your problem ??
>
> I posted this to the -current ml 3 weeks ago, when I wanted to switch.
> See the "ata: Mount root failure: 6"-thread.
Hmm, that one, I thought (wrongly) t
It seems Fritz Heinrichmeyer wrote:
>
> I tried the ATA_ENABLE_ATAPI_DMA option, it gave:
>
> ../../dev/ata/atapi-all.c: In function `atapi_attach':
> ../../dev/ata/atapi-all.c:150: syntax error before `)'
fixed.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd
It seems Amancio Hasty wrote:
> {root} mount -t cd9660 /dev/acd0a /cdrom
> cd9660: Block device required
> {root} mount /dev/acd0a /cdrom
> mount: Block device required
>
> ls -ald /dev/acd0c
> brw-r- 1 root operator 19, 2 Jan 7 20:27 /dev/acd0c
>
If this is current it should be:
cr
It seems Amancio Hasty wrote:
> Tnks
>
> Yes, I am running current as of today . also while trying to read a DVD
> I think that your driver is not setting cap.dvdrom flag so when I ask for
> report key it returns with failure. Just wondering if you her of such
> a problem currently. I am more
It seems Amancio Hasty wrote:
> I did a fresh re-install and all is working well over here. Now my real hacking
> begins that is to modify the DVD mpeg player to use the brand new spanking
> functions in XFree86 to do yuv->rgb + scaling with hardware assist 8)
You should look at the livid site, t
It seems Theo van Klaveren wrote:
>
> I still can't seem to be able to boot -CURRENT with the ATA driver,
> much as I'd like to, due to the `timeout-resetting device' error, which
> I've seen more people report. I've sacrificed some dead trees to give
> you the exact boot messages:
>
> ad0: ATA
It seems Theo van Klaveren wrote:
> >
> > Mode 4 is PIO4 that is no DMA, it could very well be the problem,
> > WD has made a lot of problematic drives in this area.
> > You could try to comment out the dmainit call in ata-disk.c and
> > see if that helps you.
>
> That helps me, but if I'm not
It seems Kris Kennaway wrote:
>
> acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04
Sounds like the drive doesn't like this, it probably only supports
PLAY_MSF..
> ata1-slave: piomode=3 dmamode=0 udmamode=-1 dmaflag=1
> ata1-slave: timeout waiting for command=ef s=00 e=00
> ata1-slave:
It seems Brian Fundakowski Feldman wrote:
> I'm sure everyone's seen my e-mail and others' e-mail about ATAPI in the
> ATA driver, at least, being broken (WRT CD-Rs). The question is, does
> anyone have any idea at all why? I tried reverting to just before the
> CDRIOC* changes, and that didn't
It seems Brian Fundakowski Feldman wrote:
>
> I was trying to rule out the CDRIO* changes themselves being at fault.
> It seems they're not, but another person also share's my experiences
> with no longer being able to write CDs now. How about this: I'll
> find out when it broke, and perhaps we
It seems Brian Beattie wrote:
> I have been looking at UDF ( the filesystem used on CD-RW and DVD's ). I
> was wondering if anybody was working on it. I'm thinking about trying to
> implement it for CD-RW's and would like to avoid duplication of effort and
> the anoyance of getting half way thro
It seems Vladimir B. Grebeschikov wrote:
>
> With new ATA driver I have big trouble
> - I can't use my CDROM
>
> while I am do 'mount_cd9660 /dev/acd0c /m/cd'
> system compleatly holds, no core, no panic - hold (may be deadloop in
> kernel mode ?)
> optionsATA_ENABLE_ATAPI_DMA#Enab
It seems Daniel J. O'Connor wrote:
>
> On 14-Jan-00 Soren Schmidt wrote:
> > Dont define this until you know the drive is functioning otherwise,
> > LOTS and I mean LOTS of atapi devices dont do DMA even if advertised.
>
> Would it be possible to implement this as
It seems Bryan Liesner wrote:
> On Sun, 16 Jan 2000, Brian Fundakowski Feldman wrote:
>
> >Can you try this patch to src/usr.sbin/burncd, and see if things work
> >after that? Thanks! (BTW, there's also an extra feature in there, hope
> >you don't mind :)
> >
>
> Yes, I burned a full 650MB onto
It seems Russell L. Carter wrote:
>
> I swapped out my motherboard and am seeing this now:
>
> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
> ad0: UDMA CRC WRITE ERROR blk# 1140495 retrying
> ad0: UDMA CRC WRITE ERROR blk# 1140495WARNING: WAIT
It seems Brian Somers wrote:
> Hi,
>
> I don't know if you'd class this as a bug report or more as an
> observation. I have a machine with the following:
bug :)
> ata-pci0: port 0xf000-0xf00f at device 15.0 on
>pci0
> ata-pci0: Busmastering DMA supported
> ata0 at 0x01f0 irq 14 on ata-pci0
It seems Valentin S. Chopov wrote:
>
> It seems that we need #if...#endif here, maybe
> something like that:
>
> ...
> #if NATAPICD > 0 || NATAPIFD > 0 || NATAPIST > 0
> /* then the atapi devices */
> for (ctlr=0; ctlr if (!atadevices[ctlr]) continue;
> if (atadevices[ct
It seems Russell L. Carter wrote:
>
> Hi Soren,
>
> I am beginning to believe that the FIC mb is the problem. My
> IBM-DPTA-372050 is only half as fast (500MB bonnie)
> as on the P2B (~10MB/s vs. ~19MB/s). A Jan 11 kernel
> doesn't downgrade to PIO on the
> IBM-DTTA-371440 as fast as this eve
It seems Motomichi Matsuzaki wrote:
>
> Hi.
>
> I updated to today's -current from -stable.
> My ATAPI CD-ROM drive doesn't probed,
> and is seemed to be halted.
> (The tray is locked, won't open, and the LED keeps being on.)
>
> Mother board: ABIT BH6
> CD-ROM drive: ATAPI [CDU77E-NE] on prima
It seems Kenneth Wayne Culver wrote:
> I recently downloaded and tried xmovie (there is a link to it at
> www.opensound.com) and when I tried to play a vob file from the DVD my
> xconsole filled with this error:
>
> acd0: READ_BIG - ILLEGAL REQUEST asc=6f ascq=03 error=00
>
> Is this an ATA driv
It seems TrouBle wrote:
> this is a brand new 10gig UDMA 66 maxtor is this a disk problem via
> hardware, or is it a BSD issue with the new code ???
> angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 7801951 retrying
The driver is telling you that the transfers CRC check are not valid
It seems Kris Kennaway wrote:
> Since the most recent round of ATA updates, my CDROM is no longer even
> probed at boot time.
>
> deviceata0
> deviceatadisk0
> deviceatapicd0
> options ATA_STATIC_ID
>
I know of this, it should be fixed in my
It seems Yosuke Koshino wrote:
> Hi,there
>
> I install FreeBSD-current-2122.
> I tried to write CD-R with burncd, but writing of CD-R is failed
> at the 'fixate' sequence. At the same time, I got the next error
> message.
> The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy".
> The
It seems Yosuke Koshino wrote:
> "Soren Schmidt <[EMAIL PROTECTED]>" wrote:
> > > The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy".
> > > Then, I add "sleep(10);" in 'fixate' code of burncd.c.
> >
> > Y
The management of next_writeable has been move from the
kernel to userspace. This means that the burncd command
must be in sync with the kernel. So make world is your
friend.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Kris Kennaway wrote:
> On Mon, 24 Jan 2000, Jordan K. Hubbard wrote:
>
> > On the 29th of January, I'll be freezing the -current branch (well,
> > OK, the trunk). That means NO commits without my review first and I
>
> Hmm. What does this mean for the ATA driver? I know Soren has some
It seems TrouBle wrote:
> does it look like this ???
Could I have a complete dmesg, or at least all the lines that belongs
to the ata driver ??
I need to know what chips etc to be able to diagnose further...
> ad0: 9770MB (20010816 sectors), 19852 cyls, 16 heads, 63 S/T, 512 B/S
> ad0: 16 secs/i
It seems Greg Childers wrote:
>
> >Huh, you have only told me about the missing CDROM (should be fixed
> >with the commit I just did), what else seems to be a problem ??
>
> On some older PCI systems, including my Pentium 66, the driver still detects
> irq 0 for ata-pci0. Hardwiring it to irq 1
It seems Motomichi Matsuzaki wrote:
>
> Thank you for fixing, but still not probed.
> What can I do for your work?
> ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0
> ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000
> ata0: mask=03 status0=50 status1=00
> ata0: mask=03 status0=00 status1=00
It seems Anders Andersson wrote:
> I have the same problem:
>
> [anders@enterprise:anders] $ dmesg | grep ata
> ata-pci0: port 0xffa0-0xffaf at device 7.1
> on pci0
> ata0 at 0x01f0 irq 14 on ata-pci0
> ata-isa0: already registered as ata0
> ata0-slave: ata_command: timeout waiting for intr
> at
It seems Greg Childers wrote:
> Hope this helps!
It may be helping you, but everyone having more than the ATA chip
on the motherboard is going to be bitten severely by this as
the interrupt for the primary channel on all controllers are
now hardwired to irq 14.
What does the Detected irq: say on
It seems Tom Embt wrote:
> Don't mean to butt in here, I haven't really been following the thread -
> but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x)
> on secondary master of the PIIX4 on my BP6. By going into the BIOS (the
> section of it where you would set CHS numbers
It seems Alex wrote:
> Speaking of identify failed, I get the following:
>
> ata-pci0: port 0xfcf0-0xfcff at device
> 1.1 on pci0
> ata0 at 0x01f0 irq 14 on ata-pci0
> ata1 at 0x0170 irq 15 on ata-pci0
>
> ...
>
> ata1-slave: ata_command: timeout waiting for intr
> ata1-slave: identify failed
It seems F. Heinrichmeyer wrote:
> Last weekend i tried patches from Soren Schmidt to reactivate my old
> cdrom which went away after the ata-update around the 18. January. This
> patches completely broke ata support for me (that means the kernel did
> not boot anymore). Of cours
It seems Alex wrote:
> > You need to update..
>
>
> OK - I've just updated. Here goes again:
>
> ata1-slave: ata_command: timeout waiting for intr
> ata1-slave: identify failed
> ad0: 6194MB [13424/15/63] at ata0-master using
> UDMA33
> acd0: CDROM at ata1-master using PIO4
> Mounting root
It seems Alex Zepeda wrote:
> I haven't been able to mount an msdos (FAT16) formattted zip disk (well
> any FAT16 formatted zip disk) for quite a while. Currently I'm trying to
> mount afd0s4, but no such luck (I think the latest error is something
> about reading the partition table). The wd dr
It seems Alex Zepeda wrote:
> On Wed, 26 Jan 2000, Soren Schmidt wrote:
>
> > I still have that on my list, but I've not gotten down to it yet, sorry...
>
> Well as long as I've got the wd driver, I'm fine.
>
> Anything in perticular where I might be able
It seems Alex Zepeda wrote:
> On Wed, 26 Jan 2000, Soren Schmidt wrote:
>
> > You could try to do a dd of the first say 2 cyls of the ZIP with
> > both drivers and check is they are different, they shouldn't be...
>
> How many bytes is this again?
Erhm, I've
It seems Alex Zepeda wrote:
> On Wed, 26 Jan 2000, Soren Schmidt wrote:
>
> > Erhm, I've forgotten the geometry of the zip, just be sure to have
> > the first two tracks.
>
> [counting on fingers, then toes, then kunckles ensues]
>
> afd0: 96MB (196608 secto
It seems Russell L. Carter wrote:
>
> Yah... as before ok I fixed this by swapping in an ASUS K7M (forget the audio,
> I can't figure that one out)
Working on it :)
> For all of the bitching on Soren's ata driver, I'd like to
> make this observation on a 500MHz/256MB ASUS K7 systemm, bonnie -s
It seems Alex wrote:
>
> OK - here's the part relevant to ata:
>
>
> ata-pci0: port 0xfcf0-0xfcff at device
> 1.1 on pci0
> ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0
> ata0: mask=03 status0=50 status1=00
> ata0: mask=03 status0=50 status1=00
> ata0: devices = 0x1
> ata0 at 0x01f0 irq
It seems Edwin Mons wrote:
> On Thu, 27 Jan 2000, Matthew N. Dodd wrote:
> > On Thu, 27 Jan 2000, Edwin Mons wrote:
> > > and the setup continues as if nothing has happened. The drive is
> > > configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA,
> > > the chipset apparently does)
/atapi-all.c
> > ../../dev/ata/atapi-all.c: In function `atapi_attach':
> > ../../dev/ata/atapi-all.c:96: syntax error before `}'
> > *** Error code 1
>
> Soren Schmidt (sos) made some recent commits to the ATA driver. Perhaps
> these problems are the result.
It seems Alex Zepeda wrote:
OK, I got my junkbox back into commission today, I just need to get it
update into -current, then I'll take a stab at it...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems D. Rock wrote:
> Hi,
>
> just noticed the new sysctl variable for ata. I just wanted to
> use the new way for disabling DMA on my disk (has some strange
> problems, even under windows).
>
> Previously I just commented out the ata_dmainit() lines in
> ata_disk.c, now I wanted to set it w
It seems Kris Kennaway wrote:
> My CDROM still refuses to work with cdcontrol, although the 30-seconds of
> kernel spinning is now fixed.
>
> Trying to play a track gives:
>
> acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04
I'll bet this drive doesn't support PLAY_BIG but only PLAY_MSF
It seems Kris Kennaway wrote:
> On Sun, 30 Jan 2000, Soren Schmidt wrote:
>
> > > Trying to play a track gives:
> > >
> > > acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04
> >
> > I'll bet this drive doesn't support PLAY_BIG but
It seems Alexander Langer wrote:
> For the archive of this ml:
>
> Some of the commits over the time since I got this error solved the
> problem silently.
>
> I'm now using ata this machine w/o any problem.
>
> On another machine that had problems with DMA with the old wd drivers
> UDMA33 now w
It seems Peter Jeremy wrote:
> Yesterday, I upgraded my system from mid-Jan to the latest
> (cvs-cur.6044) to see if it would cure some hard-hangs.
>
> Last night, I got the following messages:
>
> Feb 1 18:00:21 gsmx07 /kernel: ad2: ad_timeout: lost disk contact - resetting
> Feb 1 18:00:21 g
It seems Alex wrote:
>
> Mike, I couldn't find your fix in the commit logs - perhaps someone else
> committed it? Do you have the revision number? The problem still
> persists:
>
> ata1-slave: ata_command: timeout waiting for intr
> ata1-slave: identify failed
> ad0: 6194MB [13424/15/63] at a
It seems Andreas Klemm wrote:
>
> b) Can't mount cdrom
>
> mount /cdrom
> Device busy
Have you upgraded you /dev entries ??
> # Device Mountpoint FStype Options DumpPass#
> /dev/wd0s2b noneswapsw 0 0
> /dev
It seems Eric Jacoboni wrote:
> Hi,
>
> Sometimes, i'm unable to mount my ATAPI CDROM :
>
> The light of the drive is on, i can hear the drive working, but
> nothing... After a while (some minutes), the light turns off, the CD
> is not mounted and i can't eject it anymore until a reboot :(
>
>
It seems Klaus Herrmann wrote:
>
> ad0: 6197MB [12592/16/63] at ata0-master using UDMA33
> [ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1]
> [ata1-master: success setting up WDMA2 mode on VIA chip]
> ata1-master: CDROM device - NO DRIVER!
>
> Fatal trap 12: page fault while in ker
It seems Wes Morgan wrote:
> Has there been any resolution to the known-broken-dma drives and the ata
> driver? I haven't seen any commits or LINT options to this effect, and it
> seems to me that since it is the new default driver that something should
> be in place before it goes to -release.
L
It seems F. Heinrichmeyer wrote:
> when trying to do
>
> mdir z:
>
> my current kernel immediately freezes!
Yeah, I used a bde patch verbatim, shouldn't have done that :)
Fixed.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messa
It seems F. Heinrichmeyer wrote:
> todays current kernel made the ata-zip drive useable again.
I know, I committed the fix yesterday, I even mailed you so :)
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Adriel Ickler wrote:
> /dev# dmesg | grep cd0
> acd0: CD-RW at ata1-master using PIO4
> /dev# wormcontrol -f racd0a prepdisk quad
> wormcontrol: ioctl(WORMIOCPREPDISK): Inappropriate ioctl for device
> /dev# Feb 11 10:13:27 misty /kernel: acd0: READ_TOC - ILLEGAL REQUEST
> asc=24 ascq
It seems Shrihari Pandit wrote:
> Hi, I just installed 4.0-2208-CURRENT,
>
> During the device probe, it detected our IDE tape drive "SuperStation-Int/1.06"
> then displayed "NO DRIVER!" and paniced. This was working properly under
> 3.4-RELEASE/STABLE.
That panic was fixed earlier today,
It seems Hans Ottevanger wrote:
> Hi folks,
>
> I am currently having problems with my new Dual Celeron testsystem,
> when trying to use UDMA66.
> ABIT BP6
> 2x Celeron 466 (NOT overclocked)
> 128 Mbyte RAM
> Matrox G400 16 MByte
> 3Com 905B
> 2x Maxtor 92041U4 20 GByte
> Aopen CDROM 48x
> Whe
It seems Ashley Penney wrote:
>
> [Incidently, since then I've had another timeout or two, but it doesn't
> kill the machine anymore. Sos, is there anything I can do to help find
> out what's causing this?]
Hmm, could you send me a complete verbose boot dmesg ?, just so I can
get an idea on you
It seems Marius Strom wrote:
> Hans and others,
> I have the same situation - happy to get a new motherboard and processor,
> unhappy to hang FreeBSD. My situation is different, however - I'm running
> single processor currently and it still hangs. I've also experienced this
> issue with and wit
It seems Don Croyle wrote:
> I recently moved one of my machines to -current and I see a lot of
> these when I do buildworlds and other large builds. With a kernel
> built yesterday after the last set of ATA changes and and boot_verbose
> set, the exact message is:
>
> ad0: ad_timeout: lost disk
It seems Don Croyle wrote:
> I really can't tell you for sure. This machine had been running
> 2.2.8 before, and I didn't think to save a dmesg before I wiped it and
> reinstalled from a snapshot.
Aha! 2.2.x didn't do DMA at all
> If it would help, I'll try setting it to PIO with sysctl and
1 - 100 of 567 matches
Mail list logo
