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

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

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

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

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. --

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

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

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

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:

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

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

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

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,

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

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. :(

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

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,

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:

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

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

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

1999-08-10 Thread Francis Jordan
Soren Schmidt wrote: 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:

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.

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

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

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.