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 impleme
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.
> Act
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 ag
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 befor
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
>
> 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 ru
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... G
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 natu
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> sys/i386/i3
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
[EMAIL PROTECTED] wrote:
>>
>> As far as I know, rc.shutdown doesn't get run unless you go to single
>> user mode (for example, 'shutdown -h now' will not cause init to run
>> rc.shutdown).
I think FreeBSD-current was fixed and everytime run rc.shutdown.
SEE GNATS DB bin/12093.
http://www.fr
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
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 star
In message <[EMAIL PROTECTED]> Peter Mutsaers writes:
: it, but I got suspicious because I'm running setiathome which accesses
: the harddrive occasionally, and even during suspend mode I heard the
: typical HDD sound sometimes.
When I had my Libreto 50CT, I found that apm -Z (put into standby)
w
>> "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
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 respon
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.
Myself, I'm curious about why the access light stays on on just
one of the three
subscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I'm starting to see the following errors more frequently on my 3
servers running current dated July 30.
Aug 6 14:08:36 /kernel: wd0: interrupt timeout
(status 58 error 1)
Aug 6 14:08:38 /kernel: wd0: wdtimeout() DMA status 4
All 3 servers locked up over the weekend, although
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
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: on motherboard
pci0: on pcib0
chip0:
> > 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 u
> 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 \\
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
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 just need to find somewhere to put
this instea
> 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
> b
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 noth
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 BI
> 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.
>
>
On Mon, 9 Aug 1999, Daniel O'Connor wrote:
> > Why that complex? Couldn't I just drop in a small script using awk and
> > sh, to grab the mixer volumes, and drop it in rc.shutdown? Or even a
> > small C program would suffice if scripting isn't your cup of tea.
>
> Hmm.. true.. so have a sh
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 complex?
On 09-Aug-99 Alex Zepeda wrote:
> Why that complex? Couldn't I just drop in a small script using awk and
> sh, to grab the mixer volumes, and drop it in rc.shutdown? Or even a
> small C program would suffice if scripting isn't your cup of tea.
Hmm.. true.. so have a shell script to write t
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 compl
On Sun, 8 Aug 1999, Mike Smith wrote:
> > On Sun, 8 Aug 1999, Brian F. Feldman wrote:
> >
> > > > It works ok for me, but one nice feature of the sound system would be if
> > > > upon shutdown (I don't leave my machine on all the time right now) OS
> > > > somehow looked at a config file (call i
34 matches
Mail list logo
