Re: VESA module doesn't work with ATI Mach64 RagePro

1999-08-10 Thread Soren Schmidt

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
   BIOS is just a stub.  Such implementation is allowed in the VESA spec.
 
  Actually its because the ATI chip reports the modes as non-VGA modes, 
  which is correct (sortof), and our VESA code rejects those modeentries.
 
 Yes, thanks. Information reported by 0x4F01 function about any video
 mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR
 program for VESA support...
 
 I hate VESA 2.0/3.0 specification :-( I hate ATI :-(

Well well, no need to be that excited, if you hack out the test, the
BIOS will willingly setup the modes that you get. And IIRC we can now
support linear framebuffers in graphics modes, so support should be
fairly easy to add..

 Is there any good AGP graphics card with full BIOS support in hardware?

Dunno, but chances are getting smaller every day, most vendors relies
on winblows drivers delivered with the cards nowadays..

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: it's time...

1999-08-10 Thread Alex Zepeda

On Tue, 10 Aug 1999, Daniel O'Connor wrote:

 The sound card shuts up after reset, and only starts outputing noise again
 after the sound card has been probed/attached.

Perhaps the attach routine (or rc.something) should explicitly zero all
the volumes, so that the card will remain silent until the knobs are
called.

- alex

Experience something different
With our new imported dolly
She's lovely, warm, inflatable
And we guarantee her joy
  - The Police



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: it's time...

1999-08-10 Thread Alex Zepeda

On Mon, 9 Aug 1999, Brian F. Feldman wrote:

 On Mon, 9 Aug 1999, Alex Zepeda wrote:
 
  One could stuff it into rc.conf, but this means it's harder to
  automagically save the state upon shutdown/reboot.  But something like:
 
 Not really. You could do it with grep, awk, sed, or whatever you want,
 easily. The only possible problem would be... Getting it actually run
 at shutdown.

I missed jkh's argument, but as far as I'm concerned, my first
choice for this audio init stuff would be:

* a SysV style script (and then having rc.shutdown call
/usr/local/etc/rc.d/* w/ $1==stop; but that's another thread).

* an rc.audio or rc.multimedia (this could perhaps contain some bt484
related things).

But if it goes into "the" rc.conf, that would mean that whenever it runs
at shutdown, it edits rc.conf; this isn't IMO a real great idea.  
Anything automated (even sysinstall) editing rc.conf in any way shape or
form makes me leery because it's so much more error prone.

 It's at http://janus.syracuse.net/~green/rc.audio.patch, not vapor :)

When I wake up today, I'll check that out :^)

- alex

Experience something different
With our new imported dolly
She's lovely, warm, inflatable
And we guarantee her joy
  - The Police



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: VESA module doesn't work with ATI Mach64 RagePro

1999-08-10 Thread John Baldwin


On 10-Aug-99 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
  BIOS is just a stub.  Such implementation is allowed in the VESA spec.
 
 Actually its because the ATI chip reports the modes as non-VGA modes, 
 which is correct (sortof), and our VESA code rejects those modeentries.
 
 Yes, thanks. Information reported by 0x4F01 function about any video
 mode has set MODE_NON_VGA attribute indeed. And now I have found DOS TSR
 program for VESA support...
 
 I hate VESA 2.0/3.0 specification :-( I hate ATI :-(
 
 Is there any good AGP graphics card with full BIOS support in hardware?

Matrox G200 (and presumably G400).

---

John Baldwin [EMAIL PROTECTED] -- http://members.freedomnet.com/~jbaldwin/
PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.freebsd.org


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: VESA module doesn't work with ATI Mach64 RagePro

1999-08-10 Thread Vallo Kallaste

On Tue, Aug 10, 1999 at 07:04:15AM -0400, John Baldwin [EMAIL PROTECTED] wrote:

  I hate VESA 2.0/3.0 specification :-( I hate ATI :-(
  
  Is there any good AGP graphics card with full BIOS support in hardware?
 
 Matrox G200 (and presumably G400).

Now I'm set. I buy the G400, nothing else.
-- 

Vallo Kallaste
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: it's time...

1999-08-10 Thread Peter Wemm

"Cameron Grant" wrote:
 to let newpcm out of the cage so you can all get your grubby little hands on
 it.
 
 http://www.vilnya.demon.co.uk/newpcm+dfrpnp-19990807.diff.gz
 
 this is a patch against a recent -current.  if you have a pci or isapnp
 soundcard, you should have pnp0 and pcm0 in your kernel config as
 appropriate.  isapnp cards should not need any pnp lines in kernel.conf.
 
 the list of supported cards is as for luigi's driver, with the addition of a
 couple more mss-clones, and trident 4dwave.  there is a part done aureal
 vortex driver which is as yet nonfunctional.  mmap() is supported but not
 well tested.  format conversions are supported.  the code seems to be
 stable.
 
 please test it and email me success and failure reports.
 
 - cameron

You're missing a bit of the patch I sent you to fix some resource problems
caused by excessive cut/paste in Doug's code. Also, I implemented a proper
(but still a hack) resource printer so you see all ranges.

Before:
pcm0: Yamaha SA2 at port 0x220-0x22f,0x530-0x537 irq 5 drq 0,1 on isa0

After:
pcm0: Yamaha SA2 at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,\
0x370-0x371 irq 5 drq 0,1 on isa0

This still needs more work to handle line wraps etc.  Matthew Dodd did some
work in this area for the EISA code which should be able to be used.

Patch appended.  I don't think it's too critical since ISA_NPORT_IVARS is
the largest range, but the lower layers might end up trying to allocate on
rids that the upper layers can't handle.

Cheers,
-Peter

diff -ru3 --exclude=CVS /home/peter/merge/isa/isa_common.c ./isa/isa_common.c
--- /home/peter/merge/isa/isa_common.c  Tue Aug 10 20:17:51 1999
+++ ./isa/isa_common.c  Sat Aug  7 21:20:04 1999
@@ -270,12 +270,12 @@
 {
device_t dev = device_get_parent(child);
int success, i;
-   struct resource *res[ISA_NPORT];
+   struct resource *res[ISA_NIRQ];
 
/*
 * First clear out any existing resource definitions.
 */
-   for (i = 0; i  ISA_NPORT; i++) {
+   for (i = 0; i  ISA_NIRQ; i++) {
ISA_DELETE_RESOURCE(dev, child, SYS_RES_IRQ, i);
res[i] = NULL;
}
@@ -300,7 +300,7 @@
}
 
/*
-* If we didn't find a place for port range i, then
+* If we didn't find a place for irq range i, then
 * give up now.
 */
if (!res[i]) {
@@ -309,7 +309,7 @@
}
}
 
-   for (i = 0; i  ISA_NPORT; i++) {
+   for (i = 0; i  ISA_NIRQ; i++) {
if (res[i])
bus_release_resource(child, SYS_RES_IRQ,
 i, res[i]);
@@ -330,12 +330,12 @@
 {
device_t dev = device_get_parent(child);
int success, i;
-   struct resource *res[ISA_NPORT];
+   struct resource *res[ISA_NDRQ];
 
/*
 * First clear out any existing resource definitions.
 */
-   for (i = 0; i  ISA_NPORT; i++) {
+   for (i = 0; i  ISA_NDRQ; i++) {
ISA_DELETE_RESOURCE(dev, child, SYS_RES_DRQ, i);
res[i] = NULL;
}
@@ -360,7 +360,7 @@
}
 
/*
-* If we didn't find a place for port range i, then
+* If we didn't find a place for drq range i, then
 * give up now.
 */
if (!res[i]) {
@@ -369,7 +369,7 @@
}
}
 
-   for (i = 0; i  ISA_NPORT; i++) {
+   for (i = 0; i  ISA_NDRQ; i++) {
if (res[i])
bus_release_resource(child, SYS_RES_DRQ,
 i, res[i]);
@@ -507,26 +507,27 @@
 isa_print_resources(struct resource_list *rl, const char *name, int type,
const char *format)
 {
-   struct resource_list_entry *rle0 = resource_list_find(rl, type, 0);
-   struct resource_list_entry *rle1 = resource_list_find(rl, type, 1);
+   struct resource_list_entry *rle;
+   int printed;
+   int i;
 
-   if (rle0 || rle1) {
-   printf(" %s ", name);
-   if (rle0) {
-   printf(format, rle0-start);
-   if (rle0-count  1) {
-   printf("-");
-   printf(format, rle0-start + rle0-count - 1);
-   }
-   }
-   if (rle1) {
-   if (rle0)
+   printed = 0;
+   for (i = 0; i  16; i++) {  /* arbitary limit of 16 for now */
+   rle = resource_list_find(rl, type, i);
+   if (rle) {
+   if (printed == 0)
+   printf(" %s ", name);
+   else if (printed  0)
printf(",");
-   printf(format, rle1-start);
-   if (rle1-count  1) {

Re: it's time...

1999-08-10 Thread Jamie Bowden

On Tue, 10 Aug 1999, Alex Zepeda wrote:

:* an rc.audio or rc.multimedia (this could perhaps contain some bt484
:related things).
:
:But if it goes into "the" rc.conf, that would mean that whenever it runs
:at shutdown, it edits rc.conf; this isn't IMO a real great idea.  
:Anything automated (even sysinstall) editing rc.conf in any way shape or
:form makes me leery because it's so much more error prone.

Why not create such a file, and update it whenever a change is made?  The
settings are always in whatever state you last set them to, no matter when
it was, and you don't have to race shutdown.  

Jamie Bowden

-- 

If we've got to fight over grep, sign me up.  But boggle can go.
-Ted Faber (on Hasbro's request for removal of /usr/games/boggle)



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Improved support for NE2000 compatible ISA-PnP cards

1999-08-10 Thread Erik H. Bakke

The following has also been submitted in the form of a PR.
I am posting the information here because I think this will be of interest to
others out there as well.

If this is not the correct way to do it, or the correct place, please guide me
to the correct path, as this is my first submission (But probably not the last)

Here is the case:

FreeBSD-current does not support all NE-2000 compatible network cards,
nor will it probably ever do, but with the patch included below, at least some
cards will be supported.
The following will add support for a card, which under Windows platforms is
recognized as a CNet NE2000 compatible.

Quite simple patch...

** START OF INCLUDED TEXT **
*** if_ed.c Tue Jul  6 21:22:44 1999
--- if_ed.bak   Tue Aug 10 16:36:03 1999
***
*** 3443,3448 
--- 3443,3449 
  
  static pnpid_t edpnp_ids[] = {
{ 0xd680d041, "NE2000"},
+   { 0x0090252a, "CNet NE2000 Compatible"},
{ 0 }
  };
  
** END OF INCLUDED TEXT **

---
Erik H. Bakke
Habatech AS
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Upgrading the system.

1999-08-10 Thread Arthur H. Johnson II

When you go into upgrade under /stand/sysinstall, and select ftp and use
current.freebsd.org as the site, does it take the most recent snapshot?

Arthur H. Johnson II   [EMAIL PROTECTED]
Linuxberg Manager  Tucows.com Inc.
http://www.linuxberg.com



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: it's time...

1999-08-10 Thread Warner Losh

In message [EMAIL PROTECTED] Peter Wemm writes:
: This still needs more work to handle line wraps etc.  Matthew Dodd did some
: work in this area for the EISA code which should be able to be used.

I'd be very careful of line wrapping probe messages.  I have scripts
that rely on them being on one line to get a list of irqs, etc.

However, the whole issue of how probe messages should print, and how
much is a religious war that I try to steer clear of...

Warner



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: recent apm changes

1999-08-10 Thread Warner Losh

In message [EMAIL PROTECTED] Mitsuru IWASAKI writes:
: + error = DEVICE_SUSPEND(root_bus);
: + /*
: +  * XXX Shouldn't ignore the error like this, but should
: +  * instead fix the newbus code.  Until that happens,
: +  * I'm doing this to get suspend working again.
: +  */
: + if (error)
: + printf("DEVICE_SUSPEND error %d, ignored\n", error);

I think that it is now safe to make this warning an error...

Warner


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



installing hack(6) overwrites /var/games/hackdir/record file!

1999-08-10 Thread Andy Farkas


Perhaps this should be a PR...

Seeing as how we are recently being amused by fortune(6) quotes, I thought
I'd mention an acronymn that hasn't been used recently:  POLA

Can anyone explain why every time I upgrade world, my hard earned 'record'
file whilst playing hack(6) gets overwritten by /dev/null, and also all
the user 'bones' and 'save' files rm'd?

If the interface to these files changes, surely the game should recognise
it?

I propose the following patch to src/games/hack:

$ diff -u Makefile.orig Makefile
--- Makefile.orig   Wed Aug 11 04:16:06 1999
+++ MakefileWed Aug 11 04:16:20 1999
@@ -31,14 +31,14 @@
 beforeinstall:
${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} /dev/null \
${DESTDIR}/var/games/hackdir/perm
+.if !exists(${DESTDIR}/var/games/hackdir/record)
${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 460 /dev/null \
${DESTDIR}/var/games/hackdir/record
+.endif
${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 440 ${.CURDIR}/rumors \
${DESTDIR}/var/games/hackdir/rumors
${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \
${.CURDIR}/help  ${.CURDIR}/hh ${.CURDIR}/data \
${DESTDIR}/var/games/hackdir
-   rm -f ${DESTDIR}/var/games/hackdir/bones* \
-   ${DESTDIR}/var/games/hackdir/save/*
 
 .include bsd.prog.mk


--
 
 :{ [EMAIL PROTECTED]
  
Andy Farkas
System Administrator
   Speednet Communications
 http://www.speednet.com.au/
  




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)

1999-08-10 Thread Doug White

On Tue, 10 Aug 1999, Oliver Fromme wrote:

 Doug wrote in list.freebsd-current:
   On Mon, 9 Aug 1999, Brian McGroarty 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.
   
  Thanks for the response. FWIW I have no apm enabled and these
   drives don't have a chance to spin down since they're always busy when
   under load. 
 
 Do those drives happen to be IBM DeskStar drives?
 They spin down automatically when they have not been turned
 off for about a week, in order to clean the heads.
 It's a feature.

You've got to be kidding.  That makes them totally useless for server
operation -- at some random time every week, down goes your server for a
few minutes. :(

Doug White   
Internet:  [EMAIL PROTECTED]| FreeBSD: The Power to Serve
http://gladstone.uoregon.edu/~dwhite| www.freebsd.org



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)

1999-08-10 Thread Garrett Wollman

On Tue, 10 Aug 1999 12:38:02 -0700 (PDT), Doug White [EMAIL PROTECTED] 
said:

 You've got to be kidding.  That makes them totally useless for server
 operation -- at some random time every week, down goes your server for a
 few minutes. :(

Ye gets what ye pays for if you want a reliable server, use SCSI.

-GAWollman

--
Garrett A. Wollman   | O Siem / We are all family / O Siem / We're all the same
[EMAIL PROTECTED]  | O Siem / The fires of freedom 
Opinions not those of| Dance in the burning flame
MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)

1999-08-10 Thread Poul-Henning Kamp

In message [EMAIL PROTECTED], Garrett Wollman writes:
On Tue, 10 Aug 1999 12:38:02 -0700 (PDT), Doug White [EMAIL PROTECTED] 
said:

 You've got to be kidding.  That makes them totally useless for server
 operation -- at some random time every week, down goes your server for a
 few minutes. :(

Ye gets what ye pays for if you want a reliable server, use SCSI.

Fair to say in this case, IBM goes out of their way to explain that
*DESK*star is NOT for servers.

For a server you want ULTRAstar disks.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)

1999-08-10 Thread Soren Schmidt

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.

 Thanks for the response. FWIW I have no apm enabled and these
drives don't have a chance to spin down since they're always busy when
under load. 
  
  Do those drives happen to be IBM DeskStar drives?
  They spin down automatically when they have not been turned
  off for about a week, in order to clean the heads.
  It's a feature.
 
 You've got to be kidding.  That makes them totally useless for server
 operation -- at some random time every week, down goes your server for a
 few minutes. :(

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:

11:22PM  up 105 days,  4:18, 1 user, load averages: 1.06, 0.94, 0.91

dmesg snippet:
wdc0: unit 0 (wd0): IBM-DTTA-350840, DMA, 32-bit, multi-block-16
wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S

And none of the other machines I have with semilar or newer IBM's
have ever done this, in fact I've yet to see one of them fail in
any way..

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)

1999-08-10 Thread Francis Jordan

An unrelated question:

I get the following in my dmesg:

/kernel: ata0: master: setting up UDMA2 mode on PIIX4 chip OK
/kernel: ad0: TOSHIBA MK6409MAV/F5.01 A ATA-4 disk at ata0 as master
/kernel: ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T,
512 B/S
/kernel: ad0: piomode=4, dmamode=2, udmamode=2
/kernel: ad0: 16 secs/int, 0 depth queue, DMA mode
/kernel: acd0: UJDA150/1.02 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: Medium: CD-ROM unknown medium, unlocked
/kernel: ata_command: timeout waiting for interrupt

--^

It happens everytime I boot.  What does the last line mean, and why does
it appear?  BTW, there's an audio CD in the CD-ROM drive, so it's not
exactly "unknown" medium.  What can I do to help fix this?

Frank


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)

1999-08-10 Thread Soren Schmidt

It seems Francis Jordan wrote:
 /kernel: acd0: UJDA150/1.02 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: Medium: CD-ROM unknown medium, unlocked
 /kernel: ata_command: timeout waiting for interrupt
 
 --^
 
 It happens everytime I boot.  What does the last line mean, and why does
 it appear?  BTW, there's an audio CD in the CD-ROM drive, so it's not
 exactly "unknown" medium.  What can I do to help fix this?

I assume you only have those two devices on the ide channels right ??
Then the problem is that the CDROM drive doesn't respond proberly
to a command, in fact it doesn't respond at all, there is no interrupt.
Have you tried another CDROM drive ?? This smells alot like substandard 
hardware. 

-Søren



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)

1999-08-10 Thread Thierry Herbelot

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): IBM-DTTA-350840, DMA, 32-bit, multi-block-16
wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1): IBM-DTTA-351010, DMA, 32-bit, multi-block-16
wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
wdc1: unit 0 (wd2): IBM-DTTA-351010, DMA, 32-bit, multi-block-16
wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S


This is on my (very lightly loaded) home NFS server

TfH (trying to upgrade one BP6 to 4.0)

 
 11:22PM  up 105 days,  4:18, 1 user, load averages: 1.06, 0.94, 0.91
 
 dmesg snippet:
 wdc0: unit 0 (wd0): IBM-DTTA-350840, DMA, 32-bit, multi-block-16
 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S
 
 And none of the other machines I have with semilar or newer IBM's
 have ever done this, in fact I've yet to see one of them fail in
 any way..
 
 -Søren
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: wd0: interrupt timeout (status 58rdy,seekdone,drq error 1no_dam)

1999-08-10 Thread Soren Schmidt

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): IBM-DTTA-350840, DMA, 32-bit, multi-block-16
 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S
 wdc0: unit 1 (wd1): IBM-DTTA-351010, DMA, 32-bit, multi-block-16
 wd1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S
 wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa
 wdc1: unit 0 (wd2): IBM-DTTA-351010, DMA, 32-bit, multi-block-16
 wd2: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S
 
   TfH (trying to upgrade one BP6 to 4.0)

Have you tried putting disks on the UDMA66 channel ?? I think it
should work in upto WDMA mode now with the ata driver...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



ATA - Trouble mounting secondary master

1999-08-10 Thread Brian McGroarty

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.

Compiling the kernel with wd instead of ata eliminates the
problem.

# ls -la /dev/*wd2s1e
crw-r-   1 root   operator3, 0x00020014 Aug  7 09:06
rwd2s1e
brw-r-   1 root   operator0, 0x00020014 Aug  7 09:06
wd2s1e

# disklabel wd2
# /dev/rwd2c:
type: ESDI
disk: wd2s1
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 15
sectors/cylinder: 945
cylinders: 29872
sectors/unit: 28229040
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0   # milliseconds
track-to-track seek: 0  # milliseconds
drivedata: 0

8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  c: 282290400unused0 0 # (Cyl. 
  0 - 29871)
  e: 2822904004.2BSD0 0 0   # (Cyl. 
  0 - 29871)

# grep wd2 /etc/fstab
/dev/wd2s1e/homeufs   rw   2   2
_
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA - Trouble mounting secondary master

1999-08-10 Thread Kevin Street

Brian McGroarty [EMAIL PROTECTED] 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.

Nice timing, I was about to send a message with a description of a
similar (the same?) problem.  The first access to any IDE disk (except 
the one I'm booting from - wd1) fails with 'device not configured'.  This
affects swapon for wd2s2b during the boot as well as the first mount
for wd0 which happens to have only dos partitions on it.  So the
problem is not restricted to ufs partitions or to the secondary
controller.

Repeating the swapon or mount command works normally.

I've been seeing this problem for about a month, but I've been away on 
vacation so am just beginning to look into it.  I made changes to all
my drives and put them in LBA mode at about the same time as I began
seeing this, but I'm not sure if that is related.

ata-pci0: Intel PIIX4 IDE controller at device 4.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0

ata0: master: setting up UDMA2 mode on PIIX4 chip OK
ad0: WDC AC310200R/17.01J17 ATA-4 disk at ata0 as master
ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S
ad0: piomode=4, dmamode=2, udmamode=2
ad0: 16 secs/int, 0 depth queue, DMA mode
ata0: slave: setting up UDMA2 mode on PIIX4 chip OK
ad1: FUJITSU MPC3084AT/6021 ATA-3 disk at ata0 as slave 
ad1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S
ad1: piomode=4, dmamode=2, udmamode=2
ad1: 16 secs/int, 0 depth queue, DMA mode
ata1: master: setting up UDMA2 mode on PIIX4 chip OK
ad2: WDC AC36400L/09.09M08 ATA-4 disk at ata1 as master
ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S
ad2: piomode=4, dmamode=2, udmamode=2
ad2: 16 secs/int, 0 depth queue, DMA mode
acd0: MATSHITA CR-586/KS15 CDROM drive at ata1 as slave 
acd0: drive speed 5515KB/sec, 256KB cache
acd0: supported read types: CD-R, CD-RW, CD-DA
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked

-- 
Kevin Street
[EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA - Trouble mounting secondary master

1999-08-10 Thread Brian McGroarty

Also of interest -

I have a seperate access light for each of my drives, as they're
in removable bays.

I notice the access light for the secondary master remaining on
after the kernel driver has done its scanning. The light goes
off on this, the failed first access. I believe the light for
the primary slave stays on as well, but goes off on the first
access to the primary master (which does -not- fail).

--- Kevin Street [EMAIL PROTECTED] wrote:
 Brian McGroarty [EMAIL PROTECTED] 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.
 
 Nice timing, I was about to send a message with a description
 of a
 similar (the same?) problem.  The first access to any IDE disk
 (except 
 the one I'm booting from - wd1) fails with 'device not
 configured'.  This
 affects swapon for wd2s2b during the boot as well as the first
 mount
 for wd0 which happens to have only dos partitions on it.  So
 the
 problem is not restricted to ufs partitions or to the
 secondary
 controller.
 
 Repeating the swapon or mount command works normally.
 
 I've been seeing this problem for about a month, but I've been
 away on 
 vacation so am just beginning to look into it.  I made changes
 to all
 my drives and put them in LBA mode at about the same time as I
 began
 seeing this, but I'm not sure if that is related.
 
 ata-pci0: Intel PIIX4 IDE controller at device 4.1 on pci0
 ata-pci0: Busmastering DMA supported
 ata0 at 0x01f0 irq 14 on ata-pci0
 ata1 at 0x0170 irq 15 on ata-pci0
 
 ata0: master: setting up UDMA2 mode on PIIX4 chip OK
 ad0: WDC AC310200R/17.01J17 ATA-4 disk at ata0 as master
 ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T,
 512 B/S
 ad0: piomode=4, dmamode=2, udmamode=2
 ad0: 16 secs/int, 0 depth queue, DMA mode
 ata0: slave: setting up UDMA2 mode on PIIX4 chip OK
 ad1: FUJITSU MPC3084AT/6021 ATA-3 disk at ata0 as slave 
 ad1: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T,
 512 B/S
 ad1: piomode=4, dmamode=2, udmamode=2
 ad1: 16 secs/int, 0 depth queue, DMA mode
 ata1: master: setting up UDMA2 mode on PIIX4 chip OK
 ad2: WDC AC36400L/09.09M08 ATA-4 disk at ata1 as master
 ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T,
 512 B/S
 ad2: piomode=4, dmamode=2, udmamode=2
 ad2: 16 secs/int, 0 depth queue, DMA mode
 acd0: MATSHITA CR-586/KS15 CDROM drive at ata1 as slave 
 acd0: drive speed 5515KB/sec, 256KB cache
 acd0: supported read types: CD-R, CD-RW, CD-DA
 acd0: Audio: play, 256 volume levels
 acd0: Mechanism: ejectable tray
 acd0: Medium: CD-ROM 120mm data disc loaded, unlocked

_
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATA - Trouble mounting secondary master

1999-08-10 Thread Soren Schmidt

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.
  
  Compiling the kernel with wd instead of ata eliminates the
  problem.
 Hmm,
 
 I had exactly the same problem, although it manifested itself with a
 secondary master or slave.  It went away a few weeks ago, and I
 was never able to make any sensible progress in tracking the problem
 down.

Hmm, damn, after the problem went away for Geoff I thought it to be
solved since I've never heard of it anywhere else, and I cant reproduce
it here no matter what I try.
Does it help eany if you only has the root partition use the wd dev
and have the rest use the prober ad dev entries ?? It could be some
artifact from this...

-Søren


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message