on 09/11/2010 20:14 Alexander Motin said the following:
> Hmm. There was not much changes in ATA last time and I can't expect what
> of them could affect PATA. Probe code wasn't changed for long time.
>
> This check was actually added after some ata(4) bug found two years ago.
> So I am not sure y
Andriy Gapon wrote:
> on 09/11/2010 19:04 Alexander Motin said the following:
>> Andriy Gapon wrote:
>>> Since one of the recent updates (not sure which revision though) I started
>>> to get
>>> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
>>> message
>>> every other b
on 09/11/2010 19:04 Alexander Motin said the following:
> Andriy Gapon wrote:
>> Since one of the recent updates (not sure which revision though) I started
>> to get
>> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
>> message
>> every other boot, i.e. not always.
>>
>>
Andriy Gapon wrote:
> Since one of the recent updates (not sure which revision though) I started to
> get
> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
> message
> every other boot, i.e. not always.
>
> I added some more debug code there and here's a tack trace:
>
>
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
> I guess the correct pseudocode then is:
>
> if (disk is ata &&
> unit < 4 &&
> size < 65535C x 8H x 17S x 512B) {
> use 8/17 geometry
> }
>
> Is this correctly understood ?
> So this would no
It seems Takahashi Yoshihiro wrote:
> In article <[EMAIL PROTECTED]>
> [EMAIL PROTECTED] writes:
>
> > Is it only for ATA/IDE disks ?
> > Does it depend on the size of the disks ?
>
> Only for the internal IDE controller. The internal IDE controller on
> pc98 uses the fixed geometry which is 8 h
In message <[EMAIL PROTECTED]>, Takahashi Yoshihiro
writes:
>In article <[EMAIL PROTECTED]>
>[EMAIL PROTECTED] writes:
>
>> Is it only for ATA/IDE disks ?
>> Does it depend on the size of the disks ?
>
>Only for the internal IDE controller. The internal IDE controller on
>pc98 uses the fixed geom
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
> Is it only for ATA/IDE disks ?
> Does it depend on the size of the disks ?
Only for the internal IDE controller. The internal IDE controller on
pc98 uses the fixed geometry which is 8 heads and 17 sectors. If the
size of the disk is lar
I really wish somebody could tell us conclusively when to use
the compat geometry and when not ?
Is it only for ATA/IDE disks ?
Does it depend on the size of the disks ?
Does it also affect SCSI disks ?
Poul-Henning
In message <[EMAIL PROTECTED]>, Takahashi Yoshihiro
writes:
>The current ata
Hello, Niels.
On Sat, Sep 28, 2002 at 07:35:13PM +0200, Niels Chr. Bank-Pedersen wrote:
> On Sat, Sep 28, 2002 at 05:55:02PM +0100, Mark Murray wrote:
> > Hi
> >
> > I can't boot a kernel after my 22nd Sept one. The ATA disk controller
> > does not probe at all, and no bootable disk is found by
Quoting "Niels Chr. Bank-Pedersen" <[EMAIL PROTECTED]>:
| On Sat, Sep 28, 2002 at 05:55:02PM +0100, Mark Murray wrote:
| > Hi
| >
| > I can't boot a kernel after my 22nd Sept one. The ATA disk controller
| > does not probe at all, and no bootable disk is found by the kernel.
| >
| > The
On Sat, Sep 28, 2002 at 05:55:02PM +0100, Mark Murray wrote:
> Hi
>
> I can't boot a kernel after my 22nd Sept one. The ATA disk controller
> does not probe at all, and no bootable disk is found by the kernel.
>
> The machine is a Toshiba Libretto 110CT.
I'm seeing the same (sortof) on my Dual
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
On Sat, 8 Jan 2000, Soren Schmidt wrote:
> It seems Theo van Klaveren wrote:
> >
> > That helps me, but if I'm not mistaken it also disabled UDMA33 on the
> > second drive.
>
> Yup, it was more to determine is DMA really was your problem...
It was :)
> >
> > That'd be really nice, though if
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
On Sat, 8 Jan 2000, Soren Schmidt wrote:
> It seems Theo van Klaveren wrote:
> >
> > I'm in doubt as to the first drive though: The BIOS says it's 'Mode 4',
> > is that the same as WDMA2? Could the harddisk be reporting the wrong
> > value, even though the BIOS is giving the correct one? I'm jus
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 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,
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, instead
passing a zero-length request
On Fri, 17 Dec 1999, Soren Schmidt wrote:
> It seems Fritz Heinrichmeyer wrote:
> >
> > Of course i wish you a nice weekend ... but only mtools work.
> >
> > Mount_msdos still fails:
> >
> > mount_msdos /dev/afd0s4 /mnt
> > mount_msdos: /dev/afd0s4: Invalid argument
>
> Hmm, strange, are you
It seems Allen Pulsifer wrote:
> According to the DPTA-3x spec from IBM, if the drive has fully entered
> Standby mode, it can take up to 31 seconds for it to spin back up.
> (See sections 3.3.6.1 and 13.0). Other drive models may take even
> longer, and even after the drive is back up, it ma
]
> Cc: Richard Seaman Jr.; [EMAIL PROTECTED]
> Subject: Re: ATA driver problem?? (lost disk contact)
>
>
> It seems Dave J. Boers wrote:
> > On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote:
> > > There is no way to see if the disk was in suspend mode, you can
On Sat, Dec 18, 1999 at 11:20:51PM +0100, Martin Blapp wrote:
>
> Sorry,
>
> I found a rather easy workaround. Disable DMA for
> the disks in the BIOS ... But I still wonder why
> enable/disable ATA DMA in kernel has no effect for
> this crash. Why does only the BIOS disable help ?
Purely a wil
It seems Martin Blapp wrote:
>
> Sorry,
>
> I found a rather easy workaround. Disable DMA for
> the disks in the BIOS ... But I still wonder why
> enable/disable ATA DMA in kernel has no effect for
> this crash. Why does only the BIOS disable help ?
No idea, I have to study AMD's southbridge fi
Sorry,
I found a rather easy workaround. Disable DMA for
the disks in the BIOS ... But I still wonder why
enable/disable ATA DMA in kernel has no effect for
this crash. Why does only the BIOS disable help ?
ata-pci0: at device 7.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq
It seems Dave J. Boers wrote:
> On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote:
> > There is no way to see if the disk was in suspend mode, you can
> > give it a command and se how long it takes before it comes back :)
> >
> > The problem here is that it takes the command and OK's
On Sat, Dec 18, 1999 at 08:44:42PM +0100, Soren Schmidt wrote:
> There is no way to see if the disk was in suspend mode, you can
> give it a command and se how long it takes before it comes back :)
>
> The problem here is that it takes the command and OK's it, but it
> takes the spinuptime + over
It seems Richard Seaman, Jr. wrote:
> On Fri, Dec 17, 1999 at 02:28:29PM +0100, Soren Schmidt wrote:
>
> > Because the wd driver has a 10 secs timeout, and ata has 5 secs.
> > I think the easiest way to "solve" this is to increase the
> > timeout to 10-15 secs, as little as I want to do that...
It seems Martin Blapp wrote:
> I've bought two new 16GB ATA disks and am not able to boot
> anymore since wd0 has been retired:
>
> Fresh current from today:
>
> [...]
> ad0: ad_timeout: lost disk contact
> ata0: resetting devices
>
> and after it hangs forever.
>
> I tried IDE_DELAY=1 and
hi,
I've bought two new 16GB ATA disks and am not able to boot
anymore since wd0 has been retired:
Fresh current from today:
[...]
ad0: ad_timeout: lost disk contact
ata0: resetting devices
and after it hangs forever.
I tried IDE_DELAY=1 and 15000 but it did not change anything.
Break i
On Fri, Dec 17, 1999 at 02:28:29PM +0100, Soren Schmidt wrote:
> Because the wd driver has a 10 secs timeout, and ata has 5 secs.
> I think the easiest way to "solve" this is to increase the
> timeout to 10-15 secs, as little as I want to do that...
I don't really understand disk drivers, so if
On 17 Dec, Fritz Heinrichmeyer wrote:
> drive z: file="/dev/afd0s4" partition=4 # this works
>
> and now it works!
Confirmed, mtools works (mount remains).
I think this gives Søren a start to look at.
If I remember correctly one of the first versions of ata didn´t had this
problem (it stop
On 17 Dec, Soren Schmidt wrote:
>> Of course i wish you a nice weekend ... but only mtools work.
>>
>> Mount_msdos still fails:
>>
>> mount_msdos /dev/afd0s4 /mnt
>> mount_msdos: /dev/afd0s4: Invalid argument
>
> Hmm, strange, are you sure the dospartition is on slice 4 ??
Yes (mounting /dev
It seems Fritz Heinrichmeyer wrote:
>
> Of course i wish you a nice weekend ... but only mtools work.
>
> Mount_msdos still fails:
>
> mount_msdos /dev/afd0s4 /mnt
> mount_msdos: /dev/afd0s4: Invalid argument
Hmm, strange, are you sure the dospartition is on slice 4 ??
-Søren
To Unsubscrib
Of course i wish you a nice weekend ... but only mtools work.
Mount_msdos still fails:
mount_msdos /dev/afd0s4 /mnt
mount_msdos: /dev/afd0s4: Invalid argument
--
Fritz Heinrichmeyer mailto:[EMAIL PROTECTED]
FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany)
tel:+49 2331/987-1166 fax:987-35
It seems Fritz Heinrichmeyer wrote:
> today i tried again a windows formatted ZIP disk with mtools. First
> with a line in /usr/local/etc/mtools.conf
>
> drive z: file="/dev/afd0s4" <--- this does not work!!
>
> i had a message like
>
> init Z: sector size too big
> Cannot initi
It seems Richard Seaman, Jr. wrote:
>
> > Yup, sounds like the problem some are seing, now I wonder why I
> > havn't seen it on any of the IBM disks I've access to, hmm...
> >
> > It apparantly can't be disabled, but I'll try to figure out if
> > I can detect when the drive is in this mode, or p
On Fri, Dec 17, 1999 at 08:22:03AM +0100, Soren Schmidt wrote:
> Yup, sounds like the problem some are seing, now I wonder why I
> havn't seen it on any of the IBM disks I've access to, hmm...
>
> It apparantly can't be disabled, but I'll try to figure out if
> I can detect when the drive is in
In message <[EMAIL PROTECTED]>, Soren Schmidt writes:
>It seems Richard Seaman, Jr. wrote:
>
>Yup, sounds like the problem some are seing, now I wonder why I
>havn't seen it on any of the IBM disks I've access to, hmm...
>
>It apparantly can't be disabled, but I'll try to figure out if
>I can dete
It seems Richard Seaman, Jr. wrote:
Yup, sounds like the problem some are seing, now I wonder why I
havn't seen it on any of the IBM disks I've access to, hmm...
It apparantly can't be disabled, but I'll try to figure out if
I can detect when the drive is in this mode, or put it in
standby mode
On Thu, Dec 16, 1999 at 04:50:55PM -0600, Richard Seaman, Jr. wrote:
> Check http://www.storage.ibm.com/techsup/hddtech/prodspec/djna_spw.pdf
> If a command is received during spin down of ADM, the drive quits the spin down
> and tries to complete the command as soon as possible.
> In case the sp
On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote:
> There is this thing with the IBM's doing some headcleaning stuff once
> a day/week, but I've never seen any of my IBM's do that (I got plenty
> of them). I'll try to get more info on that from IBM...
Check http://www.storage.ibm.co
It seems Dave J. Boers wrote:
> On Thu, Dec 16, 1999 at 03:02:24PM +0100, Soren Schmidt wrote:
> > Uhm, that wont be new WD drives, as they are exactly the same as
> > IBM drives give or take the label :)
>
> Huh? That I didn't know. So you're saying that WD and IBM 18 Gb disks are
> the same har
On Thu, Dec 16, 1999 at 03:02:24PM +0100, Soren Schmidt wrote:
> Uhm, that wont be new WD drives, as they are exactly the same as
> IBM drives give or take the label :)
Huh? That I didn't know. So you're saying that WD and IBM 18 Gb disks are
the same hardware?
My disk:
ad0: ATA-4 disk at at
It seems Dave J. Boers wrote:
> On Thu, Dec 16, 1999 at 07:10:46AM -0600, Richard Seaman, Jr. wrote:
>
> > Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact -
>resetting
> > Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done
>
> > Dec 16 07:01:24 test /kernel:
On Thu, Dec 16, 1999 at 07:10:46AM -0600, Richard Seaman, Jr. wrote:
> Dec 15 19:01:02 test /kernel: ata0-master: ad_timeout: lost disk contact - resetting
> Dec 15 19:01:02 test /kernel: ata0: resetting devices .. done
> Dec 16 07:01:24 test /kernel: ata0-master: ad_timeout: lost disk contact
On Thu, Dec 16, 1999 at 09:25:11AM +0100, Soren Schmidt wrote:
> It seems Dave J. Boers wrote:
> >
> > I am still having "disc contact lost messages" regularly too. I've been
> > posting about them on several occasions some time ago. I haven't been able
> > to pinn it down, however. IF they occu
Hi Soren,
No unfortunately it still fails with the patch and the UDMA disabled in
the BIOS.
I'd be happy to try anything else you can think of. :)
Thanks.
--
Regards, Devin.
Soren Schmidt wrote:
>
> It seems Devin Butterfield wrote:
> > Hi Soren/group,
> >
> > After spending a little time sni
It seems Devin Butterfield wrote:
> Hi Soren/group,
>
> After spending a little time sniffing around in my BIOS I realized that
> my BIOS (Award BIOS) defaults to disabling UDMA for both master and
> slave and for some reason I never thought to check thisduh. Anyway
> after setting this to "a
hi, there!
On Thu, 16 Dec 1999, Dave J. Boers wrote:
> I am still having "disc contact lost messages" regularly too.
[...]
> There are two important aspects of the problem:
>
> 1. The problem does not always occur: it's unpredictable
> 2. When it occurs, I can actually hear the disk spinnin
hi, there!
On Thu, 16 Dec 1999, Dave J. Boers wrote:
> Could you tell met the exact time on which these messages occurred?
> Anywhere near 10:15 or 9:15 ?
nope. the time is unpredictable.
sometimes it can work more than a day without spilling out those messages
/fjoe
To Unsubscribe: send m
Hi Soren/group,
After spending a little time sniffing around in my BIOS I realized that
my BIOS (Award BIOS) defaults to disabling UDMA for both master and
slave and for some reason I never thought to check thisduh. Anyway
after setting this to "auto" for both master and slave the problem see
On Thu, Dec 16, 1999 at 03:29:30PM +0600, Max Khon wrote:
> hi, there!
> same here, dmesg output:
>
> ata_command: timeout waiting for interrupt
> Mounting root from ufs:/dev/ad0s2a
> ata0-master: ad_timeout: lost disk contact - resetting
> ata0: resetting devices .. done
> ata0-master: ad_timeo
It seems Devin Butterfield wrote:
> That's interesting...In my case it is quite easily reproduced (very
> predictable). All I have to do is reboot and then run sysinstall and
> when it probes the devices the disks time out. So far I have not been
> able to get this behavior at any other time.
>
>
On Thu, Dec 16, 1999 at 09:36:42AM +0100, Soren Schmidt wrote:
> One more thing, do you have SMART enabled in your BIOS ??, if so
> turn it off, and see if that changes anything...
I don't recall having it enabled; but I will check to make sure as soon as
I get home from work (which is still some
Hi,
"Dave J. Boers" wrote:
>
> On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote:
> > It seems Devin Butterfield wrote:
> > > I just recently compiled a kernel with the new ATA driver and have
> > > discovered a problem: if I run sysinstall, right when it says "probing
> > > devices,
It seems Soren Schmidt wrote:
> It seems Dave J. Boers wrote:
> >
> > I am still having "disc contact lost messages" regularly too. I've been
> > posting about them on several occasions some time ago. I haven't been able
> > to pinn it down, however. IF they occur, they occur somewhere between 9
It seems Dave J. Boers wrote:
>
> I am still having "disc contact lost messages" regularly too. I've been
> posting about them on several occasions some time ago. I haven't been able
> to pinn it down, however. IF they occur, they occur somewhere between 9:15
> and 9:20 a.m. OR p.m. But they don
On Thu, Dec 16, 1999 at 08:29:14AM +0100, Soren Schmidt wrote:
> It seems Devin Butterfield wrote:
> > I just recently compiled a kernel with the new ATA driver and have
> > discovered a problem: if I run sysinstall, right when it says "probing
> > devices, please wait (this can be a while)" error
It seems Devin Butterfield wrote:
> Hi,
>
> I just recently compiled a kernel with the new ATA driver and have
> discovered a problem: if I run sysinstall, right when it says "probing
> devices, please wait (this can be a while)" error messages saying...
[snip]
> and after printing these messages
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
Doug Ambrisko schrieb:
>
> D. Rock writes:
> | I just re-enabled the ATA driver again after reading the change log
> | of better error handling and automatic falldown DMA->PIO under specific
> | circumstances.
> | But a few days later, while making world (with the ata driver), the
> | system
> |
D. Rock writes:
| I just re-enabled the ATA driver again after reading the change log
| of better error handling and automatic falldown DMA->PIO under specific
| circumstances.
| But a few days later, while making world (with the ata driver), the
| system
| crashed quite heavily. The file system w
David O'Brien schrieb:
>
> Since the ATA driver is destined to be the default in 4.0-R, and we hare
> hitting the feature freeze date; can we make the switch now?
>
> I think it is very important to get ATA into more hands to see where it
> breaks. It certainly has problems on my Vaio 505 lapto
hi, there!
On Tue, 7 Dec 1999, Alex wrote:
> > The other one is my laptop, and that one seems to be a lot faster and
> > the system load is down (PIIX4 chipset). Except that it always gives me
> > a timeout at boot.
> >
> > acd0: CDROM drive at ata1 as master
> > acd0: read 2416KB/s (2416KB/s),
Nick Hibma wrote:
>
> The other one is my laptop, and that one seems to be a lot faster and
> the system load is down (PIIX4 chipset). Except that it always gives me
> a timeout at boot.
>
> acd0: CDROM drive at ata1 as master
> acd0: read 2416KB/s (2416KB/s), 128KB buffer, PIO
> acd0: supported
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
Good idea.
I'm using it on two machines here. One has a (known) broken hard disk,
but I don't care whether it drops a few sectors each day. ATA is keeping
it more or less alive.
The other one is my laptop, and that one seems to be a lot faster and
the system load is down (PIIX4 chipset). Except
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 capable disks, ata driver
> doesn't. It claims
On Sun, 5 Dec 1999 19:36:38 -0800, David O'Brien wrote:
>Since the ATA driver is destined to be the default in 4.0-R, and we hare
>hitting the feature freeze date; can we make the switch now?
>
>I think it is very important to get ATA into more hands to see where it
>breaks. It certainly has pro
On Sun, Dec 05, 1999 at 07:36:38PM -0800, David O'Brien <[EMAIL PROTECTED]> wrote:
> Since the ATA driver is destined to be the default in 4.0-R, and we hare
> hitting the feature freeze date; can we make the switch now?
>
> I think it is very important to get ATA into more hands to see where it
Today Bryan Liesner wrote:
> I've been having trouble mounting my ATAPI CDROM using the new ATA drivers
> And here are my /dev entries:
>
> brw-r- 1 root operator 19, 0 Oct 22 01:34 /dev/acd0a
> brw-r- 1 root operator 19, 2 Oct 22 01:34 /dev/acd0c
> brw-r- 1 root opera
Quoting Bryan Liesner ([EMAIL PROTECTED]):
> I've been having trouble mounting my ATAPI CDROM using the new ATA drivers
> When I do a:
>
> %mount /cdrom, the system complains:
%mount_cd9660 /cdrom
or
%mount -t cd9660 /cdrom
#:^)
--
bush doctor
harder than the rest ...
To Unsubscribe: send m
Soren Schmidt wrote:
> 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 qu
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
sure, as soon as i get a chance, I'll do that for ya.
Ken
On Sun, 10 Oct 1999, Soren Schmidt wrote:
> 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 .
It doesn't seem to have bad sectors...
found-> vendor=0x109e, dev=0x036e, revid=0x02
class=04-00-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
intpin=a, irq=9
map[0]: type 3, range 32, base ea002000, size 12
found-> vendor=0x109e, dev=0x0878, re
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:
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
> A dmesg to start with would be fine that way I may be able to reproduce
> it here pn semilar HW.
wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16,
sleep-hack
wd0: 8693MB (17803440 sectors), 1108 cyls, 255 heads, 63 S/T, 512 B/S
(sleep-hack I turned on last night)
>> > /kernel: wd0
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
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 with you.
> >
> Hi I don't know if it i
> "Soren" == Soren Schmidt <[EMAIL PROTECTED]> writes:
Soren> 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 -
>r
On Mon, 27 Sep 1999, Soren Schmidt wrote:
>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
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
On Mon, 27 Sep 1999, Soren Schmidt wrote:
>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
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 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
On Mon, 13 Sep 1999, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]
> l>, Pascal Hofstee writes:
> >As of 4.0-CURRENT about a few hours ago the ATA-driver screws up with my
> >secondary master IDE drive ... wd1s1e gets mounted perfectly ... all other
> >wd1s1 entries fail:
>
> Make sur
In message <[EMAIL PROTECTED]
l>, Pascal Hofstee writes:
>As of 4.0-CURRENT about a few hours ago the ATA-driver screws up with my
>secondary master IDE drive ... wd1s1e gets mounted perfectly ... all other
>wd1s1 entries fail:
Make sure you have rev 1.6 of sys/kern/subr_disk.c
--
Poul-Henning K
I'm condisering such an animal for PicoBSD.
I'm willing to do it for current and other branches,
if and only if I can get three solid alpha testers.
"Daniel C. Sobral" wrote:
> Nick Hibma wrote:
> >
> > Jordan, you said nowadays one can simply compile a kernel < 1.44Mb and
> > stick it on the d
> Jordan, you said nowadays one can simply compile a kernel < 1.44Mb and
> stick it on the disk kern.flp?
Yep! You can even make one > 1.44MB and gzip it first (but remember
to call it /kernel.gz or the loader won't be smart enough to un-gzip
it). As long as the kernel is compiled with options M
Great idea.
I'll be the first one to try it with the USB support...
> > People could appreciate this. I for one would like to make demo floppies
> > to send to companies having supplied devices for USB support to show
> > their devices at work.
>
> So, anyone up for creating a web page generat
Nick Hibma wrote:
>
> Jordan, you said nowadays one can simply compile a kernel < 1.44Mb and
> stick it on the disk kern.flp?
It is possible. Even more, you can add kld modules to that disk, and
then edit loader.rc to load them too, so you don't even need to
compile a kernel.
> People could appr
-- Forwarded message --
Date: Tue, 20 Apr 1999 18:29:04 +0200 (CEST)
From: Nick Hibma
To: Erik Haugen Bakke
Subject: Re: ATA driver for alpha
Jordan, you said nowadays one can simply compile a kernel < 1.44Mb and
stick it on the disk kern.flp?
People could appreciate this
> On Mon, 19 Apr 1999 e...@habatech.no wrote:
>
> >
> > On 19-Apr-99 Doug Rabson wrote:
> > > I have ported the new ATA driver to the FreeBSD/alpha. This provides
> > > support for IDE disks and cdroms. The version of the driver in the tree
> > > has only been tested on one old 433au machine so
In article <199903051706.taa00...@hangdog.is.co.za>,
Geoff Rehmet wrote:
>
> I've just decided to keep my list of bonnie tests running. I haven't
> pulled the latest changes yet, as CVSUP is basically a day behind
> from cvsup.za.freebsd.org.
Are you sure? The CVSup server logs on freefall sh
On Tue, 2 Mar 1999, Geoff Rehmet wrote:
> Just some results of testing the comparison of wd and ata:
>
> Both bonnie tests were run on a freshly booted machine, P133,
> 64M RAM, running X and netscape, but only Bonnie active:
Odd. My (crapy?) WD drive is much faster with DMA (not UDMA AFAIK), s
> Just some results of testing the comparison of wd and ata:
>
> Both bonnie tests were run on a freshly booted machine, P133,
> 64M RAM, running X and netscape, but only Bonnie active:
>
>
> ---Sequential Output ---Sequential Input--
> --Random--
> -Per
> Just some results of testing the comparison of wd and ata:
...
> -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
>MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU
>ATA64 3237 69.0 2913 14.0 1409 9.4 2951 59.3 3043 11.6 5
1 - 100 of 101 matches
Mail list logo
