It seems Hans Ottevanger wrote:
> Tried this patch, and the system does not hang any more. Even better,
> I/O to this disk is still quite fast, at least way faster than using the
> "standard" interface on this board (and even that is not really slow).
> I'll run a "buildworld" as torture test thi
It seems Chris Radek wrote:
>
> Hi,
>
> I have a group of Compaq LTE Elite 4/50CX laptops (486dx2/50, 24meg
> ram, two PCMCIA slots), on which I am attempting to install the
> 4.0 snapshot from 2209. Two of these machines report an IBM
> disk (this is `-v' transcribed by hand):
>
> ad0: A
It seems Don Croyle wrote:
> Soren Schmidt <[EMAIL PROTECTED]> writes:
>
> > > If it would help, I'll try setting it to PIO with sysctl and doing
> > > another buildworld.
> >
> > It probably will...
>
> Made it through the world safely. I
It seems Julian Elischer wrote:
> I have been hired to add UDF/DVD-R support to FreeBSD
> I will be spending the next few weeks basically doing research
> but would like to hear from anyone who is already working in these
> areas.
>
> This may impact un the following areas:
> SCSI subsystem
> ATA
It seems Dan Langille wrote:
> On 14 Feb 00, at 22:02, Dan Langille wrote:
>
> > On 7 Feb 00, at 18:12, Dan Langille wrote:
> >
> > > I have one box which is slow to boot under -current (mind you, I've never
> > > run anything but -current on this box). There are two pauses. One after
> > > at
It seems Bryan Liesner wrote:
> On Sat, 19 Feb 2000, Soren Schmidt wrote:
>
> >Have you rebuild your modules lately ??
> >
> >-Søren
> >
> Yes. My world is current as of a few hours ago. I did a make world
> right after finding out about the loader problem
It seems Andrew Gallatin wrote:
> > It seems that the 0xa5 value means "no device" too, on lots of
> > controllers, and its not valid anyways, so it wouldn't hurt..."
>
> That works! The pause is gone and the reboot time is more than cut in
> half. I urge you to commit this ;-)
I will, its
It seems Bryan Liesner wrote:
> >Do you use KLMs?
>
> Yes, I do! I was loading a screen saver with the boot loader. And
> now I see I am wrong about rebuilding the loader! When I had success
> loading the kernel directly, I moved loading the screensaver into
> rc.conf instead. Then I thought th
It seems Andreas Klemm wrote:
> On Tue, Feb 22, 2000 at 10:15:42PM +0100, Soren Schmidt wrote:
> > There are two posibilities, either the cable is bad or the disk is bad.
> > Since you could talk to it, and you didn't get ICRC errors, my bet is
> > that the particul
It seems Mike Smith wrote:
> > Forgive me if I'm beating a dead horse... I'm still having the following
> > problem if I load any modules from /boot/loader.conf:
>
> I've reproduced this here, and narrowed it down to Soren's ATA megacommit
> on the 18th. Unfortunately, the newbus patches (teste
It seems Dan Langille wrote:
> I have one box which is slow to boot under -current (mind you, I've never
> run anything but -current on this box). In my previous message, there
> were two excessively long pauses. One after ata0 appears and another
> after ata-isa0 appears. I've been able to
It seems Andrew Gallatin wrote:
> Is there any way to tell the driver not to reduce the timeout to
> something less than 31s? Or would it be easier for me to just #if 0
> the lun1 (iobase_2..) code in ata_pciattach()?
>
> I'm asking because we have about 20 boxes like this. All of which are
> "
It seems Bryan Liesner wrote:
>
> The latest ata commits left my system completely unbootable. No disks
> were probed.
He, you always seem to be lucky when I change something :)
> I have on the motherboard's Alladin controller:
> HP 4x4x24 CD burner as master primary channel
> 40x CD as slave
It seems Bryan Liesner wrote:
> On Sat, 19 Feb 2000, Soren Schmidt wrote:
>
> >It seems Bryan Liesner wrote:
> >>
> >> The latest ata commits left my system completely unbootable. No disks
> >> were probed.
> >
> >He, you always seem to be luc
It seems Jose Gabriel Marcelino wrote:
Well, rebuild the loader, that helped Bryan, apparently it has
nothing to do with the ata driver
> The latest ata commits left me unbootable too, the patch you provided
> below didn't help this too. I have a very different configuration from
> Bryan's
It seems Donn Miller wrote:
> Say I do something like
>
> find /cdrom
>
> is the HD light supposed to be blinking as if the hard drives are being
> accessed? I did the above command (note that it doesn't involve finding
> files on the hard drives at all), and basically the HD light and th
It seems Jonathan Smith wrote:
> Is it a general problem that audio CD's fail to play in a dvd drive (or
> cd drive, for that matter ;) via cdcontrol as of the past few days and/or
> dvd's not being accessed properly, ie. with DeCSS? Cdcontrol would not
> eject, but would close until the buildwor
It seems Andreas Klemm wrote:
> Hi !
>
> I have hangs and timeouts using the EIDE disk in my computer.
> The controller is a Abit Hot Rod 66 and Maxtor Diamond Max 54098U8.
> I use the 80 pin cable from the Abit EIDE controller special for UDMA.
>
> Messages are:
> ad4: READ command timeout - re
It seems Morten Seeberg wrote:
> I have a Teac 6 CD changer (acd0: CDROM with 6 CD changer at
> ata1-master using PIO4), which works just fine in 3.x except for the usual
> error message when the CD-ROM drive is empty and I start up
> /stand/sysinstall), but in subj. when starting /stand/sysinsta
It seems Arun Sharma wrote:
> I have the above hardware combination and here's the dmesg from
> 4.0-current:
>
> atapci0: port 0xf000-0xf00f at device 7.1 on pci0
> atapci1: port
>0xb400-0xb4ff,0xb000-0xb003,0xac00-0xac07 irq 11 at device 19.0 on pci0
> ata2: at 0xac00 on atapci1
> atapci2:
It seems Andreas Klemm wrote:
> Newfs'ing and mounting the filesystem went fine.
> I enabled softupdates prior mounting.
>
> But when I tried fire up bonnie -s 100
> I soon get after nearly writing the 100 MB characterwise...
>
> ad4: READ command timeout - resetting
> ata2: resettin
It seems Akinori -Aki- MUSHA wrote:
> Hi,
>
> I'm running recent 4.0-CURRENT and my Seagate Barracuda ST320430A
> 20GB hard drive connected with Promise Ultra66 card isn't recognized
> as an Ultra ATA/66 drive but only /33.
Could I have a verbote boot log please, that would give some hints..
It seems Arun Sharma wrote:
> > Do you have the prober 80pin cable ?? if so please provide a verbose boot...
>
> Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very
> unscientific benchmark that I ran didn't seem to produce much of a difference
> between UDMA33 and UDMA66.
It seems Akinori -Aki- MUSHA wrote:
> Alright, I booted the system with boot_verbose=1, and the dmesg
> output was as follows. I wish this would help your investigation.
It does:
> ata2-master: success setting up UDMA2 mode on Promise chip
> ad4: ATA-4 disk at ata2 as master
> ad4: 19569MB (
It seems Andreas Klemm wrote:
> On Tue, Feb 22, 2000 at 01:39:46PM +0100, Soren Schmidt wrote:
> > Try to use a "normal" ie 40pin cable, that will limit the disk to
> > UDMA33 mode, if that works, well...
>
> Hurray, using a normal cable works. I got 2 cab
It seems Doug Rabson wrote:
> >
> > That megapatch was only newbus patches and cosmetics around that, one
> > new item was cmd646 support but that is hardly the problem here.
> >
> > > Soren - this is somewhat of a showstopper. Can you reproduce it there?
> >
> > Nope, I've tried several machi
It seems Mike Smith wrote:
> >
> > That megapatch was only newbus patches and cosmetics around that, one
> > new item was cmd646 support but that is hardly the problem here.
>
> You didn't mention the 0xa5 test, and I forgot to tell you that I backed
> it out as well (no change).
yeah, cosmeti
It seems Christoph Kukulies wrote:
>
> -current of Feb, 26th.
>
> Innocently I wanted to
>
> mount -t cd9660 /dev/acd1c /dist
>
> to grab some newer XF86 from the CD when
>
> cd9660: device not configured
>
> was thrown at me.
And you have an acd1 device ??
check you /dev for up to date
It seems John Hay wrote:
> Hi,
>
> I have been trying to install yesterday's 4.0 snap on a no-name brand
> motherboard with the VIA chipset, but I'm running in some problems. I
> suspect there is a problem with the DMA. The error I'm getting when the
> disk is newfs'ed is a repeating:
>
> ad0: W
It seems Ben Smithurst wrote:
> ok, this was partly caused by dodgy hardware it seems, so don't worry
> too much, but it would be nice if a panic could be avoided.
aaiiighh! I knwo exactly what wrong, dont call make_dev early :)
Thanks, that probably one of the most complete reports I've seen in
It seems Hans Ottevanger wrote:
> Hi folks,
>
> I just tried to boot the RC3 install floppies on my Pentium 66 testbox.
> It gets through the config stage without trouble, but then panics
> immediately with:
>
> ...
> pcib0: on motherboard
> pci0: on pcib0
> atapci0: possible> port 0
> x3f4-0
It seems Julian Elischer wrote:
> It is most ironic that of course you were the loudest supporter of
> SOS when he ripped out all my code that did EXACTLY all this.
> (I might add that this was done without any warning to me. The
> The commit messages being my first notice).
>
> It was fully work
It seems Donn Miller wrote:
> I've got two HD's in my machine: one's an older one (WDMA2) and the other
> one, my main one, is newer (UDMA33). With recent kernel builds, I've
> noticed some strange problems with the older HD. When I try to to
> something like fsck -y on the drive, fsck just han
It seems Matthew Sean Thyer wrote:
> Please leave the wd driver for those who cannot use the ATA driver.
> At least until the ATA driver gets support for more older disks.
>
> I cant be the only person using an old 80 MB IDE drive as / with
> another drive as /usr (a 400 MB SCSI).
>
> I haven't
It seems Greg Childers wrote:
> Hi,
>
> I can't find the date or sender of the original email - the mailing list archives
>haven't been updated since Feb 20 - but my Pentium 66 still panics during boot with a
>kernel compiled today. Here's what I get...
>
> atapci0: port
>0x3f4-0x3f7,0x1f0-
It seems David Gilbert wrote:
> I still have hardware that works with wd and not ata. I posted awhile
> ago that ata gets stuck in a retry loop on my system. This is with a
> CVSUP of a couple of days ago.
>
Be sure you have the abosolutely latest version of the ata driver,
a bug was fixed in
It seems Bruce Evans wrote:
> On Tue, 14 Mar 2000, Jeroen Ruigrok van der Werven wrote:
>
> > Yes...
> >
> > That's right.
> >
> > Use ata and related stuff instead.
>
> No.
Yes.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mes
It seems Thomas Veldhouse wrote:
> Are there any plans to support the buggy CMD640 interface in the future
> now that 4.0-RELEASE has come and gone? I have a box that is running 3.4
> happily, and it has this interface. I really would like the chance to use
> some of the 4.0 features, but I can
It seems Mathew Kanner wrote:
> Hi All,
> I wanted to document my difficuties with Vinum and multiple
> disks on Promise controllers. I believe that the problems lies with
> multiple cards on the same interupt but what do I know -- execpt that
> the problem goes away when I disable
It seems Chris D. Faulhaber wrote:
> On Sat, 18 Mar 2000, Alan Clegg wrote:
>
> > Panasonic CD-ROM Changer that is found in by the kernel as:
> >
> > acd0-4: CDROM with 5 CD changer at ata0-master using PIO4
> >
> > Mounting /cdrom1 works just fine:
> >
> > /dev/acd0c on /cdrom1 (cd9660, loca
It seems Nicolas Souchu wrote:
> On Mon, Aug 23, 1999 at 08:27:15AM +0200, Soren Schmidt wrote:
> >
> >It seems Nicolas Souchu wrote:
> >> acd0: CDROM drive at ata0 as master
> >> acd0: drive speed 0KB/sec
> >> acd0: supported read types:
> >&g
A little while ago I enabled DMA on atapi devices, and while this
generally is a good thing (CPU usage wise), there seems to be
some delicate problems with this on some chipsets and devices.
If you use the new ATA driver and has atapi devices that use DMA
could you please check that they are wor
It seems Kevin Street wrote:
> Two things I've noticed:
> 1) my cdrom delivers about 2M/s which is the same as before DMA. Is
> the improvement only in cpu usage or should I be seeing a speed
> improvement too?
Depends.. There are many factors involved here, using DMA only lowers
the CPU usage,
It seems Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Michael
>Reifenberger writes:
> : if I do an upgrade to -current on my Tecra8000 the ep* driver stopps working.
>
> The ep driver works in -current.
>
> : The message from pccardc is that he failed the resouce allocation.
>
> Fix the
It seems Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Soren Schmidt writes:
> : Hmm, I'm also having a hell of a time here, on closer inspection it
> : turns out that my problem is that the kernel allways finds an ed0
> : device allthough none is present. I have both
It seems Doug Rabson wrote:
> >
> > Hmm, I'm also having a hell of a time here, on closer inspection it
> > turns out that my problem is that the kernel allways finds an ed0
> > device allthough none is present. I have both an ed0 & an ep0 device
> > in my config as I use both type of cards. So m
It seems Soren Schmidt wrote:
> It seems Doug Rabson wrote:
> > >
> > > Hmm, I'm also having a hell of a time here, on closer inspection it
> > > turns out that my problem is that the kernel allways finds an ed0
> > > device allthough none is present.
It seems Kazutaka YOKOTA wrote:
>
> It appears that if you hit the keyboard before (at the boot loader
> prompt or during the kernel is probing devices) or while the keyboard
> driver is being initialized, you may see the problem.
Hmm I've seen the problem where on "loose" the input at the loade
It seems Gary Hampton wrote:
> I have been trying to get the ata drivers to work on my system for a
> a while now but can't seem to mount my cdrom drives. This is what I get on
> boot up:
> atapi: DMA transfer mode set
> acd0: CDROM drive at ata0 as master
I'll bet that your CDROM doesn't do DM
Ten'th update to the new ATA/ATAPI driver:
It been awhile since the last major update, as a benefit there
are some cool things in this one (and new bugs probably :) )...
The ATA driver has grown "real" timeout support for all devices.
This means that it should be possible to get in contact with
It seems Cejka Rudolf wrote:
>
> I'm trying to update my -current system compiled from July 12 (both
> kernel and base system). But before all system updating I have tried to
> compile and run new kernel from today (September 25) - and it won't
> boot so I'm afraid to update all the system...
> B
It seems Thomas Veldhouse wrote:
> Hello,
>
> I have noticed over time that many people are test driving the new
> ATA
> Drivers. I attempted to do it a while back but I couldn't boot because of
> the device name changes. I did not know what the new device names were.
> Anyway - is there
It seems Cejka Rudolf wrote:
> I think internal bad block remapping is long time here. But
> in the middle of 1996 I have bought a new Western Digital disk
> with some bad sectors and it runs without any problems till today
> (and without any new bad sectors - I have tried new disk format
> some
It seems Viren R. Shah wrote:
>
> I made world and build a new kernel on Friday the 24th, and later that
> evening, I got these:
>
> Sep 24 18:00:33 jabberwock /kernel: ata0-master: ad_timeout: lost disk contact -
>resetting
> Sep 24 18:00:33 jabberwock /kernel: ata0: resetting devices .. done
n neutral brown paper and
it should pass customs just fine :)
My snail mail addresss is:
Soren Schmidt
Soparken 61, Klokkerholm
DK9320 Hjallerup
Denmark
-Soren (and yes today I'm on a 7bit line too :) )
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Jeroen Ruigrok/Asmodai wrote:
>
> you know I have the possession of a development box with the HPT366,
> right? [well you should since I mailed you those timing-tables =P ]
I know :)
> Anyways, as soon as I have enough cash again I will buy an /66 disk
> and stuff it on the free contro
It seems Jeremy L. Stock wrote:
> I have two hard drives both Western Digital 8.4GB (primary master) 6.4GB
> (primary slave) and a CDROM as secondary master. The driver detects the
> 8.4GB and my cdrom but doesn't seem to see the second hd at all. I'd provide
> more info if I could but / lives on
It seems Jeremy L. Stock wrote:
>>Are you sure you have the latest versions of everything in /sys/dev/ata ??
>>There was a window of opportunity where I messed up unless ATA_STATIC_ID
>>was defined...
>>
>>-Søren
>>
>
>Fairly positive I have the latest versions. I cvsup'ed twice yesterday. I
>forg
It seems Kenneth Wayne Culver wrote:
> On Thu, 30 Sep 1999, Luke wrote:
>
> > On 01-Oct-99 Kenneth Wayne Culver wrote:
> > > The ata driver seems to be having problems staying in contact with my
> > > disks again. Let me know what details are needed to fix the problem, and
> > > I'll get in touch
It seems Daniel M. Eischen wrote:
>
> More info on the kernel hang.
>
> Removing pnp from the kernel configuration will allow me to boot
> and successfully detects my pnp modem. So the culprit seems to
> be the new pnp code. Suggestions welcome.
Hmm, I also have severe problems with the PnP s
It seems Timo Geusch wrote:
> On Fri, Oct 01, 1999 at 02:32:11PM +0200, Soren Schmidt wrote:
> > Hmm, I also have severe problems with the PnP stuff and my 3C509
> > cards, it just wont work as the pnp code finds and allocates
> > adresses for the card, but the card probe
It seems Erik H. Bakke wrote:
> I am still having problems with the ATA driver.
> I am seeing the same error messages as has been reported on the lists during
> the last few weeks, both on i386 and alpha platforms.
> On the i386, the problem is just an irritating itch, but it seems to be
> far mor
It seems Justin T. Gibbs wrote:
> It looks like both nsio and sio have PCCARD support disabled at the
> moment. Is there any other way I can get the system to recognize my
> modem?
Fix the broken sio, it might be KNF and all but it doesn't work...
-Soren
To Unsubscribe: send mail to [EMAIL PR
It seems Kenneth Culver wrote:
Is this with the latest that I committed yesterday ??
-Søren
> I finally got a chance to put the ata driver back in my kernel, and this
> is what happens: Whenever I am doing something that requires a lot of disk
> activity, (on the latest errors, I was recompilin
It seems Kenneth Culver wrote:
> ata0: slave: success setting up UDMA2 mode on PIIX4 chip
> ad1: piomode=4 dmamode=2 udmamode=2
> ad1: ATA-3 disk at ata0 as slave
> ad1: 4120MB (8438850 sectors), 8930 cyls, 15 heads, 63 S/T, 512 B/S
> ad1: 16 secs/int, 0 depth queue, UDMA33
Uh oh, I had one of
It seems Kenneth Culver wrote:
> Oct 10 12:29:48 culverk /kernel: ata0-slave: ad_timeout: lost disk contact
> - res
> etting
> Oct 10 12:29:49 culverk /kernel: ata0: resetting devices .. DANGER
> active=3
> Oct 10 12:29:49 culverk /kernel: done
> Oct 10 12:29:49 culverk /kernel: ad1: status=51 err
It seems Maxim Sobolev wrote:
> It seems that ATA is broken - it paniced when kernel is booting. Following is
> diagnostic output:
>
> isa0: on motherboard
> pccard0: on motherboard
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address= 0xc
> fault code
It seems Maxim Sobolev wrote:
[Charset koi8-r unsupported, filtering to ASCII...]
> Soren Schmidt wrote:
>
> > It seems Maxim Sobolev wrote:
> > > It seems that ATA is broken - it paniced when kernel is booting. Following is
> > > diagnostic output:
> >
It seems Valentin S. Chopov wrote:
>
> How the ATA_16BIT_ONLY in ata-disk.c and atapi-all.c
> will be defined - kernel option, autodetection or
> device flag?
For now kernel options, later auto for ISA & 486 arch machines..
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscr
It seems Bob Bishop wrote:
> Hi,
>
> -current kernels from the past 48hrs or so lock up during boot on my SMP
> box, as in:
>
> ...and there it freezes. Total lockup, reset button or power cycle only.
> Apparently it's barfing either on one of the PCI netcard probes, or trying
> to initialise ed
It seems Doug Rabson wrote:
> On Sun, 31 Oct 1999, Brian Fundakowski Feldman wrote:
>
> > Have you either tried disabling DMA on the drive? This is easily achieved
> > by the following (whitespace mangled):
>
> I'll try it on Monday.
Hmm, as well as DMA might be the reason, it only applies to
It seems Kazutaka YOKOTA wrote:
>
> AFAIK, not all video cards generate the vertical retrace interrupt.
> Even worse, some BIOSes have a configuration option which instract the
> BIOS NOT to assign an IRQ to the PCI video card.
>
> I fully agree that the vertical retrace interrupt will be of gre
It seems Amancio Hasty wrote:
> > It seems Kazutaka YOKOTA wrote:
> > >
> > > AFAIK, not all video cards generate the vertical retrace interrupt.
> > > Even worse, some BIOSes have a configuration option which instract the
> > > BIOS NOT to assign an IRQ to the PCI video card.
> > >
> > > I full
It seems Amancio Hasty wrote:
>
> Just trying to prevent dragging the whole X server to the kernel --
> Actually dragging the whole X server to the kernel is not a bad
> idea --- however it is something that I can not afford to do right now :(
Ahh, horror, Terry's old idea is coming back again :
It seems Amancio Hasty wrote:
> > Lets step back for a moment, this is clearly the wrong solution to
> > everything, what exactly is it you want to do or want to accomplish??
> > Lets see if we can come up with another way of doing that...
>
> Okay,
>
> The problem that the XFree86 group is tryi
It seems Donn Miller wrote:
> On Sun, 7 Nov 1999, Jeroen Ruigrok/Asmodai wrote:
>
> > libggi has more support for FreeBSD than svgalib has and it also seems
> > to be preferred over svgalib due to security hassles and all that.
> >
> > So you might want to try that route.
>
> I saw where libvgl
It seems Andrzej Bialecki wrote:
> >
> > Oops, sos and I have developed a new version of libsvgl which can
> > handle VESA modes in addition to the standard VGA graphics modes.
> > But I haven't committed it to the source tree yet (yes, I should have
> > done so weeks ago ;-(
> >
> > Anyway, if
It seems F. Heinrichmeyer wrote:
> more observations to the zip-drive problem:
> First the relevant dmesg-line:
>
> atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00
> afd0: rewriteable drive at ata0 as master
> afd0: 96MB (196608 sectors), 32 cyls, 64 heads, 96 S/T, 512 B
It seems Bryan Liesner wrote:
> On Fri, 26 Nov 1999, Soren Schmidt wrote:
>
> <>It seems F. Heinrichmeyer wrote:
> <>> more observations to the zip-drive problem:
> <>> First the relevant dmesg-line:
>
> I'm also still having a small problem wi
It seems Alexander Leidinger wrote:
> I didn´t tried to reproduce this recently, but you could try to format
> the ZIP-disc with mtools:
>
> mformat -t 96 -h 64 -s 32 -H 32 z:
I'll dig out my ZIP drive tonight a do some testing...
> ---snip---
> wdc0: unit 1 (atapi): , removable, intr, iordis
>
It seems Wes Morgan wrote:
>
> ad0: ATA-? disk at ata0 as master
> ad0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S
> ad0: 16 secs/int, 0 depth queue, DMA
> ad1: ATA-4 disk at ata0 as slave
> ad1: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S
> ad1: 16 se
It seems Richard Seaman, Jr. wrote:
> On Mon, Dec 06, 1999 at 12:19:16PM +0200, Vallo Kallaste wrote:
>
> > It doesn't know about SiS 5591 PCI IDE controller, the wdc controller
> > knows. I'm speaking about boot messages, nothing else. Furthermore the
> > wdc driver sets up UDMA mode on my UDMA
Well subject says it all, the ata driver is now default in GENRIC & PCCARD.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Richard Seaman, Jr. wrote:
> On Wed, Dec 08, 1999 at 12:55:35PM +0100, Poul-Henning Kamp wrote:
> >
> > In a few days time the wd driver will be retired from FreeBSDs
> > i386 architecture.
> >
>
> Since the ata driver does not support DMA on my chipset, at
> least the last time I trie
It seems Alexander Leidinger wrote:
>
> It isn´t only a matter of providing feedback... the maintainer also has
> to work on it.
Yeah, right...
> I offered feedback in every mail regarding my problem with ata &
> msdos-ZIPs (they aren´t accessible), but most of the time I havn´t got a
> reply (
It seems D. Rock wrote:
> I don't think I have the same problem. My drive definitely doesn't spin
> down. It sometimes occurs during heavy usage, so the drive should still
> be very alive. With PIO mode I also don't have any timeout problems.
> I also had the same DMA problems with the old wd driv
It seems Julian Elischer wrote:
> please do not remove it..
And why is that ?? There is no point in having done a new one then, and
you guys have known I've been working on this for ages so this cannot
come as a surprise to anybody...
The same thing is about to apply to the woxware sound code,
It seems Julian Elischer wrote:
>while you're about it the cyrix GXM?
Docs? HW? tester? in that order
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Christopher Masto wrote:
> On Wed, Dec 08, 1999 at 10:56:24AM -0800, Mike Smith wrote:
> > > You shouldn't remove a function until it has been properly replaced.
> > > A very simple concept some people seem to have trouble grasping.
> >
> > Actually, that's not at all correct. We've dem
It seems Andrey A. Chernov wrote:
> As I see by quick check, CD-related soft from ports understand SCSI only.
> Does anybody use new ATAPI CD-R (acd)? If yes, please tell me how.
I use it every day, well almost :)
Look in /usr/share/examples/atapi...
-Søren
To Unsubscribe: send mail to [EMA
It seems Richard S. Straka wrote:
> I have recently performed some testing on the ata and wd drivers
> on my system. When writing to and reading from a file on the same
> file system in the same directory, the ata driver appears to take almost
>
> double the CPU time as compared to the wd driver
It seems Richard Seaman, Jr. wrote:
> On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote:
>
> > OK, you asked for it, following is a patch to support the
> > sis 5591 chipset. Remember this is done blindfolded, I
> > have no HW to test on, but you guys
It seems Blaz Zupan wrote:
> On Wed, 8 Dec 1999, Christopher Masto wrote:
> > I fully agree that these things are neccessary and good. I just think
> > we need avoid jumping the gun on removing the old code, when some
> > people still need it to boot their machines.
>
> Actually I completely dis
It seems Vallo Kallaste wrote:
> On Thu, Dec 09, 1999 at 08:39:46AM +0600, Boris Popov <[EMAIL PROTECTED]> wrote:
>
> > > Problem: Computer _sometimes_ stops after the "Mounting root from
> > > ufs:/dev/ad0s2a" line.
> > > Running Current, built world yesterday. (Problem appeared fairly
> > > rec
It seems Greg Lehey wrote:
> > OK, you asked for it, following is a patch to support the
> > sis 5591 chipset. Remember this is done blindfolded, I
> > have no HW to test on, but you guys do :)
> >
> > Let me know what happens...
>
> OK. Let's defer removing wd until we know that ata DMA works o
It seems Maxim Sobolev wrote:
> > There also exist cases where the chipset is supported but a particular
> > functionality isn_t supported yet (in my case it_s the possibility to
> > access MS-DOS formated ZIP-disks, harddisk access works well, and I_m
> > not the only one with this problem (not c
It seems Richard Seaman Jr. wrote:
> >
> > It already being tested, and it works, but at the same tike I found
> > out that the code in the old driver for the sis is schizofrenic, it
> > has one way of setting things up, and another way of reporting how
> > it is set :(, that way it is difficult
It seems Greg Lehey wrote:
> >>
> >> I think the old wd code was broken on reporting. The reporting
> >> was changed from the original submission, when it was committed.
> >
> > Yep, but it does mean that people _belive_ they are running UDMA
> > where in fact they aren't, and now they blaim the
It seems Jeroen Ruigrok/Asmodai wrote:
> -On [19991209 06:58], Andrey A. Chernov ([EMAIL PROTECTED]) wrote:
> >Do you have a plan to merge ATAPI as part of SCSI (CAM) interface as
> >NetBSD already does? It will solve problems with all SCSI-only CD* soft
> >automatically.
>
> I thought this was
It seems Christopher Masto wrote:
> On Thu, Dec 09, 1999 at 06:38:46AM +0300, Andrey A. Chernov wrote:
> > On Wed, Dec 08, 1999 at 09:34:24PM +0100, Soren Schmidt wrote:
> > > I use it every day, well almost :)
> > > Look in /usr/share/examples/atapi...
> >
&
101 - 200 of 567 matches
Mail list logo
