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
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
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:
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
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
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. :(
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,
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
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.
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
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.
11 matches
Mail list logo
