I seem to have broken something in Vinum's RAID-5 support while
importing it to the source tree. It works fine when all disks are up,
but things go to hell in degraded mode. I'll have it fixed in a day
or two, but in the meantime don't try testing degraded mode: it don't
work.
Greg
--
See
On Mon, 9 Aug 1999, Daniel O'Connor wrote:
You could do it something like the way boot -c stuff or the splash screen is
done, ie load a 'module' which is just a text file for the sound system to
parse..
Don't know how you'd go unload'ing and load'ing the file though.
Why that
plm In contract, if I suspend in Linux of Windows, the computer shuts up
plm immediateley and is quiet. Only sometimes there is a (not too loud)
plm little fan (I think it is the CPU fan) running for a few more minutes.
I've read Linux code (v2.2.9) closely, noticed they put cli
before APM BIOS
I just downloaded the latest snap (080799) and tried installing it.
When getting to the media section and configuring ppp for a ftp install,
I try going to vty3 (alt-f3). However, that vty is not available. I have
tried this 3 times now. Is this broken?
I did a search for this but have found
plm In contract, if I suspend in Linux of Windows, the computer shuts up
plm immediateley and is quiet. Only sometimes there is a (not too loud)
plm little fan (I think it is the CPU fan) running for a few more minutes.
I've read Linux code (v2.2.9) closely, noticed they put cli
before
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
As far as the segment registers, we do an explicit save of them already
when we switch into VM86 mode, so it should be necessary to save them
twice.
VM86 mode is only used to enable APM; after that we are using the
32-bit protected mode interface.
--
\\ The mind's the standard \\
As far as the segment registers, we do an explicit save of them already
when we switch into VM86 mode, so it should be necessary to save them
twice.
VM86 mode is only used to enable APM; after that we are using the
32-bit protected mode interface.
Ahh... In the old code, we used to
Today I thought I would upgrade my 4.0 box from a July 15th snapshot
to an August 9th snapshot. Only problem is I can't, because the August
9th snapshot's boot kernel refuses to locate my 486's PCI bus.
Previously, the bus was detetected as follows:
pcib0: PCI host bus adapter on motherboard
Daniel O'Connor wrote:
On 09-Aug-99 Alex Zepeda wrote:
Actually at shutdown would be cool. So it could save the current
volumes,
and restore them at startup. Altho, at suspend and resume time
wouldn't
be a bad idea either.
You could do it something like the way boot -c stuff or
I'm starting to see the following errors more frequently on my 3
servers running current dated July 30.
Aug 6 14:08:36 kern.crit /kernel: wd0: interrupt timeout
(status 58rdy,seekdone,drq error 1no_dam)
Aug 6 14:08:38 kern.crit /kernel: wd0: wdtimeout() DMA status 4
All 3
"MI" == Mitsuru IWASAKI [EMAIL PROTECTED] writes:
plm In contract, if I suspend in Linux of Windows, the computer shuts up
plm immediateley and is quiet. Only sometimes there is a (not too loud)
plm little fan (I think it is the CPU fan) running for a few more minutes.
MI I've
On Mon, 9 Aug 1999, Brian F. Feldman wrote:
You guys don't see the point. The point is a single, simple place to put
default mixer values for any number of devices, and fitting in with the
current configuration file scenario. rc is the natural place for this,
because _it_ gets run at
On 09-Aug-99 Brian F. Feldman wrote:
You guys don't see the point. The point is a single, simple place to put
default mixer values for any number of devices, and fitting in with the
current configuration file scenario. rc is the natural place for this,
because _it_ gets run at startup. I
Hi,
MI I've read Linux code (v2.2.9) closely, noticed they put cli
MI before APM BIOS call and save restore segment registers. I
MI suspect these two (or only cli?) affect the suspending state.
MI To clarify, could you try attached patches (for
MI
On Tue, 10 Aug 1999, Daniel O'Connor wrote:
On 09-Aug-99 Brian F. Feldman wrote:
You guys don't see the point. The point is a single, simple place to put
default mixer values for any number of devices, and fitting in with the
current configuration file scenario. rc is the natural
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...
On 10-Aug-99 Brian F. Feldman wrote:
Sure.. but you still have window of time where the audio is at its default
level before the rc stuff is run..
Why... would audio be playing from rc? Bear in mind, it would be set
even before rc.local...
I have a radio connected to line in on my sound
On Tue, 10 Aug 1999, Daniel O'Connor wrote:
On 10-Aug-99 Brian F. Feldman wrote:
Sure.. but you still have window of time where the audio is at its default
level before the rc stuff is run..
Why... would audio be playing from rc? Bear in mind, it would be set
even before
On 10-Aug-99 Brian F. Feldman wrote:
I have a radio connected to line in on my sound card.
Then that would be playing during the entire bootup, wouldn't it? What,
does it play only after the card has been detected?
The sound card shuts up after reset, and only starts outputing noise again
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
21 matches
Mail list logo
