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:
>
>
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:
driver bug: Unable to set devclass (c
It seems Takahashi Yoshihiro wrote:
> I got the following error. The kernel config has no pci device but
> ATA_NOPCI option.
Fixed. I just completely forgot that ISA only systems exists...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of th
I got the following error. The kernel config has no pci device but
ATA_NOPCI option.
cc -c -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I/usr/src/sys -I/usr/src/
I have corrected a number of problems on Serverworks & ALI chipsets
and it has been committed to -current.
There is an outstanding problem with having tags enabled on ATA disks,
and I have temporarily disabled tags support until I nail that nasty
problem.
So please update your sources and let me
The first round of ATA updates/fixes has been committed, please
let me know if you find any problems with it...
The commitlog say:
This moves all chipset specific code to a new file 'ata-chipset.c'.
Extensive use of tables and pointers to avoid having the same switch
on chipset type in several p
It seems David Schultz wrote:
> Thus spake Soeren Schmidt <[EMAIL PROTECTED]>:
> > I've prepared a patch that brings the ATA driver to the next level.
> >
> > This is mainly to prepare for other platforms which demanded
> > some changes to the driver infrastr
Thus spake Soeren Schmidt <[EMAIL PROTECTED]>:
> I've prepared a patch that brings the ATA driver to the next level.
>
> This is mainly to prepare for other platforms which demanded
> some changes to the driver infrastructure.
>
> It also fixes lots of outstand
It seems Sheldon Hearn wrote:
> On (2003/02/13 14:00), Soeren Schmidt wrote:
>
> > I've prepared a patch that brings the ATA driver to the next level.
>
> You've brought ata in under cam? ;-)
That wouldn't be forward moving now would it ?
> Sorry,
On (2003/02/13 14:00), Soeren Schmidt wrote:
> I've prepared a patch that brings the ATA driver to the next level.
You've brought ata in under cam? ;-)
*duck*
Sorry, couldn't resist.
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
I've prepared a patch that brings the ATA driver to the next level.
This is mainly to prepare for other platforms which demanded
some changes to the driver infrastructure.
It also fixes lots of outstanding problems and adds support several
new chipsets including SiS (thanks to Chri
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
e current ata driver on pc98 has a problem. I think that the
>following patch solves the problem. Please review it. This change
>must be in RELENG_5_0 branch.
>
>
>Index: sys/dev/ata/ata-disk.c
>===
>RCS file:
The current ata driver on pc98 has a problem. I think that the
following patch solves the problem. Please review it. This change
must be in RELENG_5_0 branch.
Index: sys/dev/ata/ata-disk.c
===
RCS file: /home/ncvs/src/sys/dev/ata
It seems Andrew Gallatin wrote:
>
> Kris Kennaway writes:
> > I got this on one of the gohan machines overnight. These machines
> > have failing disks -- I get a lot of hard read errors, but the
> > INVARIANTS panic could better be replaced by something else.
> >
> > I reported another inst
Kris Kennaway writes:
> I got this on one of the gohan machines overnight. These machines
> have failing disks -- I get a lot of hard read errors, but the
> INVARIANTS panic could better be replaced by something else.
>
> I reported another instance of this to sos a few weeks ago but didn't
I got this on one of the gohan machines overnight. These machines
have failing disks -- I get a lot of hard read errors, but the
INVARIANTS panic could better be replaced by something else.
I reported another instance of this to sos a few weeks ago but didn't
hear a reply.
Kris
ad0: hard error
Out of da blue Kris Kennaway aka ([EMAIL PROTECTED]) said:
> Kernels with the following configuration do not link:
>
> # ATA and ATAPI devices
> device ata
> device atapicd # ATAPI CDROM drives
>
> linking kernel.debug
> ata-all.o: In function `ata_boot_attach':
> ata-al
It seems Kris Kennaway wrote:
> ata-all.o: In function `ata_boot_attach':
> ata-all.o(.text+0x1590): undefined reference to `ata_raid_attach'
> ata-all.o(.text+0x1594): undefined reference to `ata_raid_attach'
Yes, I've seen it there is two other issues I'd like to fix also,
I'll ask re@ for appr
Kernels with the following configuration do not link:
# ATA and ATAPI devices
device ata
device atapicd # ATAPI CDROM drives
linking kernel.debug
ata-all.o: In function `ata_boot_attach':
ata-all.o(.text+0x1590): undefined reference to `ata_raid_attach'
ata-all.o(.text+0
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
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.
Here is a dmesg:
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989,
Due to new ioctl's and a rearrange of the old ones make sure
that burncd & kernel is in sync or wierd things can happen.
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
It seems Maxim Sobolev wrote:
> >
> > It seems Jim Bloom wrote:
> > > For the past couple weeks I have been unable to build a kernel for my
> > > laptop. I keep getting undefined symbols. The problem started with
> > > the split of the ata driver b
>
> It seems Jim Bloom wrote:
> > For the past couple weeks I have been unable to build a kernel for my
> > laptop. I keep getting undefined symbols. The problem started with
> > the split of the ata driver by different bus attachments. My laptop
> > only
It seems Jim Bloom wrote:
> For the past couple weeks I have been unable to build a kernel for my
> laptop. I keep getting undefined symbols. The problem started with
> the split of the ata driver by different bus attachments. My laptop
> only has ISA and not PCI so I don't i
For the past couple weeks I have been unable to build a kernel for my
laptop. I keep getting undefined symbols. The problem started with
the split of the ata driver by different bus attachments. My laptop
only has ISA and not PCI so I don't include PCI in the kernel config
file.
The e
with a -STABLE as of last night at 1:30 AM EST the ata driver refuses to
configure my DVD drive. Here is the output of a dmesg:
ad0: 8063MB [16383/16/63] at ata0-master UDMA33
ad1: 13029MB [26473/16/63] at ata1-master UDMA66
ad2: 14655MB [29777/16/63] at ata1-slave UDMA66
ata0-slave: <\M-v
In message <[EMAIL PROTECTED]> Will Andrews writes:
: On Tue, Oct 17, 2000 at 08:29:04PM +0200, Michael Reifenberger wrote:
: > it seems to be a ata issue because it worked before some ata-updates (after
: > SMPng).
: >
: > Is anyone using SANDISK SmartMedia successfully with -cuurent?
:
: Strang
On Tue, Oct 17, 2000 at 08:29:04PM +0200, Michael Reifenberger wrote:
> it seems to be a ata issue because it worked before some ata-updates (after
> SMPng).
>
> Is anyone using SANDISK SmartMedia successfully with -cuurent?
Strange, I get exactly the same output from September 29 -current. :(
Hi,
it seems to be a ata issue because it worked before some ata-updates (after
SMPng).
Attached is a (verbose)dmesg output during startup and insertion.
BTW: Why does it try to become ata4?
I have two ATA-Slots with disks in my TECRA-8000 notebook.
They are attached as ata0 and ata1 (master).
So
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
>
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 driver problem
Hi all,
Tried out the new ATAPI driver last night with a CVS from a couple of
days ago. All detected ok on boot but then I got a message roughly like:
timeout waiting for command
and then I get:
ata0: resetting devices ..
The system completely hung solid then.
Firstly a question. Is t
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
&g
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-0 disk at ata0 as ma
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 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
t *ticks is incrementing!
If I add 'ata' back in, buckus (DDB> print *ticks yields 0, machine
is screwed up).
When I remove 'ata' and enable the 'wd' driver, everything works
normally. The machine boots up fine.
I think there's something we
On 2000-Jan-06 18:38:08 +1100, Soren Schmidt <[EMAIL PROTECTED]> wrote:
>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).
...
>> acd0: read 1723KB/s (1723KB/s), 256KB buffer, DMA
>
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
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
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 light flashes briefly and the CD-ROM spins up.
The
of the physical
slice will abort with EINVAL, rather than returning a partial block.
2) There seems to be an off-by-1 error in the size reported by my
Fireball (or maybe in the request handling), causing it to report
an I/O error on the last sector.
The first problem would seem to b
> While this can be moved into the man page, I don't see how a
> message like this can significantly slow down booting, unless you have a
> slow serial console. However, a pointer is still useful; I'd suggest a
> shorter message like:
>
> ad0: DMA disabled: See ad(4) man page for possible
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
On Wed, 22 Dec 1999, Soren Schmidt wrote:
> > ad0: ATA-4 disk at ata0 as master
> > ad0: 12416MB (25429824 sectors), 25228 cyls, 16 heads, 63 S/T, 512 B/S
> > ad0: 16 secs/int, 1 depth queue, UDMA33
> > ...
> >
> > Although I coulda sworn it was an ATA/66 device with the proper cable.
> > Hmm.
It seems Pim van Grol wrote:
> Good job, the latest revision works, allthough in DMA mode.
Thanks!
> By the way, my motherboard (Epox EP-51MVP3G-M) indeed supports a
> 82c596 as south bridge, containing a (82c)571 device as IDE controller.
> From dmesg:
>
> found-> vendor=0x1106, dev=0x0
Soren Schmidt <[EMAIL PROTECTED]> wrote:
> It seems Nick Hibma wrote:
> > > If you end up doing this, can you have the driver print a line letting
> > > people know this is intentional? i.e.,
> > >
> > > ad0: DMA disabled: This drive does not properly support DMA mode.
> > > ad0: To force DMA
e 2nd line should go in the manual pages but keeping
the first line could reduce the number of user questions. Also, if
you have broken hardware, you probably don't care about boot speed.
Soren: thanks for the ATA driver. My Thinkpad 600 now happily runs
-CURRENT at UDMA33 mode. Only
It seems Nick Hibma wrote:
> > > Mentioning it in the manpage should be sufficient I guess. Blacklisting
> > > devices sounds like a good idea if tey fail to work correctly in many
> > > cases.
> >
> > The problem being how to get a list that is "good enough" for the
> > majority of cases.
>
> I
> > Mentioning it in the manpage should be sufficient I guess. Blacklisting
> > devices sounds like a good idea if tey fail to work correctly in many
> > cases.
>
> The problem being how to get a list that is "good enough" for the
> majority of cases.
I'd like to see it the other way around: Mak
It seems Nick Hibma wrote:
> > If you end up doing this, can you have the driver print a line letting
> > people know this is intentional? i.e.,
> >
> > ad0: DMA disabled: This drive does not properly support DMA mode.
> > ad0: To force DMA for this drive (at your own risk) set flags 0xXX.
>
> If you end up doing this, can you have the driver print a line letting
> people know this is intentional? i.e.,
>
> ad0: DMA disabled: This drive does not properly support DMA mode.
> ad0: To force DMA for this drive (at your own risk) set flags 0xXX.
Let's not go the Linux way and make the
It seems Pim van Grol wrote:
> For your information:
>
> I encountered the same problem on a MVP3 board (Epox ep-mvp3g-m)
> with via vt82c596, which worked well untill 13-12-99. Matrox HD.
Are you sure you mean 596 ?? that is NOT supported (yet).
> Correctly interpreted as doing UDMA33. From ve
It seems Alex Zepeda wrote:
>
> Perhaps blacklisting all WD/Maxtor drives that don't report an ATA
> version, as the ata (and wd) driver works flawlessly in UDMA33 mode with
> my setup:
Hmm, thats an idea...
> ata-pci0: at device 7.1 on pci0
> ata-pci0: Busmastering DMA supported
> ata0 at 0x0
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> It probably because I relaxed the requirements for doing WDMA on disks
> that doesn't bother to tell whihc verson of the ATA spec they conform to.
> I think your case is the more seldom one, but I'm this close to
> blacklisting all WD/Maxtor drives, tha
It seems Matthew Dillon wrote:
>
> The thread 'vm_page_remove panic' that Tamiji Homma initiated may be
> related. She is getting a panic in the buffer cache subsystem while
> using the new ATA driver with softupdates + NFS exported filesystems.
>
>
It seems Peter Wemm wrote:
>
> Same here, but with a toshiba laptop disk. I have to comment out a version
> test in ata-disk.c to get it to work.
I've just a few hours ago committed a change that does this...
>
> --- ata-disk.c 1999/12/18 20:06:30 1.46
> +++ ata-disk.c 1999/12/21 21:48:2
PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
The thread 'vm_page_remove panic' that Tamiji Homma initiated may be
related. She is getting a panic in the buffer cache subsystem while
using the new ATA driver with softupdates + NFS exported filesystems.
I do not know if it
Theo van Klaveren wrote:
>
> When installing the 08-dec-1999 snapshot (before ATA went in GENERIC),
> a recompile from the kernel with the ATA driver instead of the WD
> driver resulted in an unbootable system because of the following
> error (approx.):
>
> mounting r
It seems Doug White wrote:
> >
> > It probably because I relaxed the requirements for doing WDMA on disks
> > that doesn't bother to tell whihc verson of the ATA spec they conform to.
> > I think your case is the more seldom one, but I'm this close to
> > blacklisting all WD/Maxtor drives, that w
On Tue, 21 Dec 1999, Soren Schmidt wrote:
> > Harddisks: Western Digital Caviar (2.0 GB), non-DMA and
> >Western Digital Caviar (2.5 GB), DMA-33.
> > Mainboard: Asus P5A-B Super7
> > Chipset: ALi Aladdin V AGPset
>
> It probably because I relaxed the requirements for doing WDMA on di
I think your case is the more seldom one, but I'm this close to
> > > blacklisting all WD/Maxtor drives, that would make life alot easier...
> >
> > Hmmm... what exactly does the 'blacklisting all WD/Maxtor drives' mean?
> > That I can't use the AT
sting all WD/Maxtor drives, that would make life alot easier...
>
> Hmmm... what exactly does the 'blacklisting all WD/Maxtor drives' mean?
> That I can't use the ATA driver, or that the timeout for these drives
> is increased?
It means they will not do DMA without user inter
s the 'blacklisting all WD/Maxtor drives' mean?
That I can't use the ATA driver, or that the timeout for these drives
is increased?
Theo van Klaveren <[EMAIL PROTECTED]>
http://phoenix.student.utwente.nl / ICQ #1353681
- Why, oh why didn't I take the _blue_ pil
It seems Theo van Klaveren wrote:
>
> When installing the 08-dec-1999 snapshot (before ATA went in GENERIC),
> a recompile from the kernel with the ATA driver instead of the WD
> driver resulted in an unbootable system because of the following
> error (approx.):
>
> moun
When installing the 08-dec-1999 snapshot (before ATA went in GENERIC),
a recompile from the kernel with the ATA driver instead of the WD
driver resulted in an unbootable system because of the following
error (approx.):
mounting root /dev/ad0s1a
ata-master: lost disk contact
ata: resetting
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
able help ?
Purely a wild guess on my part:
If the BIOS is set to enable UDMA, then the bios sets both
the controller and the disk for UDMA. But, the ata driver
tries to set the disk to WDMA2 mode for "generic drivers".
If the controller is set for UDMA and the disk for WDMA2, they
might h
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...
tput from the old wd driver:
> wdc0: unit 0 (wd0):
> wd0: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S
So it didn't use multisector nor DMA, what does the ata driver say in
the probe ??
> PS: I can give you access to the machine if you like.
Well, if the ata dr
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
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 initialize 'Z:'
this message i have never seen before, so
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
andby to idle is
13 secs "typical" and 31 secs max for this drive. I'm assuming
that what we're seeing is that the ata driver "lost contact"
because the timeout is less that the time it takes to spinup
from standby to idle (or to spinup from an interrupted switch
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
1 - 100 of 287 matches
Mail list logo
