http://people.freebsd.org/~msmith/acpica-bsd-20001007.tar.gz
This includes:
- ACPI as PnP enumerator for ISA (there are issues here, and this doesn't
disable the "real" PnPBIOS code yet, so you will get duplicates on some
machines).
- Power/Sleep button code (Iwasaki-san)
- Improved
.
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
superblocks?
Just FYI, Mandrake 7.1 does the same thing out of the box.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 04-Oct-00 Alain Thivillon wrote:
I have noticed that -CURRENT (build last week) is subject to a very high
clock deviation:
I run -CURRENT on a laptop, it seems that last commit in idle loop (the
one replacing loop by HLT and lowering temperature) broke the clock.
Hmm, this
I don't know of any problems related to this at this time. Make sure you
have the latest BIOS from Intel for the ISP2150.
I installed 4.1.1 on an Intel ISP 2150 with a Mylex AcceleRAID 250. The
fireware on the controller is 4.06 .
After install and while it starts to boot I get:
BTX
started lerning ACPICA with documents and
source code.
Mike, I'm feeling we need to have a migration plan. Do you have any
plan on this?
I have an enormous patch that I can put up later tonight on Freefall.
I have the ACPICA 2915 release fully integrated, and I've ported
their sample OSPM
Here's what seems to be an interesting AML or AML parser bug.
OperationRegion(PSRG, SystemMemory, 0x0410, 0x1)
Field(PSRG, DWordAcc, NoLock, Preserve) {
, 2,
PS2E, 1
}
The field is marked for 32-bit access, but the region is only 1
I have an enormous patch that I can put up later tonight on Freefall.
Actually, I couldn't make CVS do what I wanted, so it's a big tarball
with an itty-bitty little patch instead.
This requires an up-to-date -current kernel (for the pci_cfgreg changes,
etc.)
I haven't done anything special
Great! This is really great!! I didn't think we can have ACPICA
kernel so earlier.
Well, let's see if it works right first. 8) I hear from Intel that they
plan to release a new code revision today, so I will be updating when
they do. I also hear that Andrew Grover (the chap at Intel
This is still very obscure; I'd like to see:
size (was 1234, should be 5678)
cksum (was 42424242, should be 69696969)
...so that it's clear what the meaning of the numbers is.
In that case I think I would like to loose the ',' also.
While you're at it,
I hate to spoil the moment ... but does anyone have an idea what the
fix is? g Nothing in the amd directory seems to have changed in the
past couple of weeks, so it must be somewhere else, and I'm not bright
enough to figure out where.
Yeah, somebody forgot that typedefs and structure
PowerResource code keeps pointers to the PowerResource objects, then
finds a pointer to methods of the object dynamically. Can we do it in
similar way for thermal management?
Well, yes, but you have to go back and re-parse the actual AML. I'm not
even sure if it's safe to
Here's what seems to be an interesting AML or AML parser bug.
OperationRegion(PSRG, SystemMemory, 0x0410, 0x1)
Field(PSRG, DWordAcc, NoLock, Preserve) {
, 2,
PS2E, 1
}
The field is marked for 32-bit access, but the region is only
Ah, thanks :)
Does it possibly belong in /etc/defaults/rc.devfs, to slurp in
/etc/rc.devfs (if it exists) at the end?
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
* installed ports; 2) uninstall
them all; then 3) rebuild and install them all, with a report about
failures would make me happy.
That way, I'd know that all the ports were built against the current
system, which would make me feel much safer.
mike
To Unsubscribe: send mail
Alexander Langer writes:
Thus spake Mike Meyer ([EMAIL PROTECTED]):
Does it possibly belong in /etc/defaults/rc.devfs, to slurp in
/etc/rc.devfs (if it exists) at the end?
No - instead we should add something like devfs_permission{0,1,2,etc}
(and maybe ownership) to rc.conf, which can
Please test this; there are lots of opportunities for error in these
changes. In particular, I am afraid that I may have broken I/O from AML
I did test it, S1, S5 transition, PowerResource On/OFF and GPE handling
by kernel thread, everything seems OK!
I think nobody has objections for
Cool. On some machine, thermal management requires Embedded Controller I/O.
Anybody working on this?
Yeah. I just discovered that I need this.
I haven't look at how operation regions are handled, so I'm not sure how
hard it's going to be to implement the hooks necessary for this.
Seigo Tanimura writes:
On Sat, 30 Sep 2000 13:35:48 -0500 (CDT), Mike Meyer [EMAIL PROTECTED] said:
Mike Seigo Tanimura writes:
Completely automatic update of installed ports is acutally difficult
because we cannot get to know the language or required toolkit from
the name of a binary
Run 4.0 or piss off...
Actually, no. This message contains useful diagnostic information, and
can be used to resolve the problem.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of CHOI Junho
Sent: Saturday, September 30, 2000 11:22 PM
To: [EMAIL
Here's the latest ACPI megapatch:
- Move all the register I/O into a separate file
- Made all the I/O spaces use proper bus resources
- Allocate the resources in machine-dependant code
- Map ACPI-used memory in machine-dependant code
- Create a machine-dependant "acpiprobe" device which
I'd like to move and rename them as I said in my previous mail,
sys/acpi.h - sys/dev/acpi/acpi.h
shared by both kernel and userland programs
sys/dev/acpi/acpi.h - sys/dev/acpi/acpivar.h
shared within kernel code (acpi stuff and related drivers)
IMHO, it's desirable to use
Thanks a lot mike, these are mostly acceptable for me.
- Made all the I/O spaces use proper bus resources
- Allocate the resources in machine-dependant code
I prefer previous patch because most of the code in i386/acpi_machdep.c
can be shared with IA64 I think.
I'm not so sure about
And probe method and identify method should not be confused.
Memory area check etc can be in MD acpi probe code.
Can you explain what you mean here a bit more? The FACT lookup and
resource establishment need to be done in the identify routine, not the
probe routine...
--
... every
OK, understood. How about having MD sub-routine in the same interface
(say acpi_set_resources() or acpi_create_instance() or whatever) for
i386 and ia64? Then generic ACPI identify method calls suitable
sub-routine depending on machine architecture.
- i386/i386/acpi_machdep.c
Ok. Based on all the suggestions, received today, and some more ideas
besides, here's the latest megapatch.
- Move all register I/O into a new file
- Move event handling into a new file
- Move headers to acpivar/acpireg/acpiio
- Move find-RSDT and find-ACPI-owened-memory into acpi_machdep
As Iwasaki-san pointed out, I left acpi_event.c out of the previous
megapatch. Rather than resend the entire thing, you can fetch the
complete patch from:
http://people.freebsd.org/~msmith/acpi-2929.diff.gz
Regards,
--
... every activity meets with opposition, everyone who acts has
With the addition of ACPI kernel thread, my system hangs in about
10 miniutes use after boot up. By disabling kernel thread, system
runs just fine.
Do you have any idea where to look at?
I'll try and see what I can do myself.
Please set debug.aml_debug and debug.acpi_debug to 1 and
Please set debug.aml_debug and debug.acpi_debug to 1 and
see what will happen.
It wouldn't surprise me if the system wasn't running out of kernel
memory. Right now we just keep mallocing storage to queue ACPI events
(bad idea). The entire event/Notify stuff needs to be
Currently kernel thread seems broken, so mallocing storage in
acpi_queue_event() never be freed. I think number of events at a
point of tme is limited and we can have static storage for the events.
The implementaion of sys/i386/apm/apm.c:apm_record_event() (it's for apmd)
would be
I can second this... on my PC the cpu used to run around about 84 degrees
F with the case at 80 degrees F, now the cpu runs at about 91-93 degrees F
while the case runs at 80 degrees F.
While you're tinkering with SMPng, be VERY SURE that you do not have acpi
enabled (ie. make sure it's not
My laptop does seem to run *MUCH* warmer than before as well. It runs
hot to begin with, but with the latest kernels it runs really hot. It
used to get this hot only when I compiled -j 4. I don't have ACPI
enabled and am using UP kernel. There really needs to be a HLT in the
idle loop to
In message [EMAIL PROTECTED] Mike Smith writes:
: If I remember from a discussion with John Baldwin, the reason we don't do
: this (yet) is that HLT only wakes up when you take an interrupt, and
: there are cases where we can't guarantee that we'll take an interrupt in
: order to get us
: If I remember from a discussion with John Baldwin, the reason we
: don't do this (yet) is that HLT only wakes up when you take an
: interrupt, and there are cases where we can't guarantee that we'll
: take an interrupt in order to get us out of the HLT.
:
: I thought that's what the
Vallo Kallaste writes:
On Sat, Sep 16, 2000 at 03:01:28PM -0500, Mike Meyer [EMAIL PROTECTED] wrote:
I've had a ton of experience with ahc lately, as those of you who follow
-questions, -stable, or -scsi know. r1.48 of aic7xxx.c is horribly
broken. I can't get current snaps after
wanted to see what others thought of it before
trying it.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
was about to step from PRE_SMPNG back to
-current, but you've just made me nervous!
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
or current message I missed or hadn't read yet?
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
forward with
getting this patch to the point where it can be committed, i'd
certainly appreciate it. alternately, any feedback on whether the
patch is necessary and/or functional on your machine, laptop or no,
would be interesting.
- Forwarded message from mike ryan [EMAIL PROTECTED
Ben Smithurst writes:
Mike Meyer wrote:
I cvsupped and rebuilt earlier to today, only to find that the kernel
was installed as /boot/kernel/kernel instead of
/boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of
a surprise.
Is this a bug, or did I happen to catch
e in the future". This is an
example where they could presumably be useful.
Doesn't Oracle run MUCH better when given raw block disk devices to store
data on?
Oracle wants to cache it's own data, it doesn't want the buffer cache
behind it.
Could this have lead to some of the poor pe
ost certainly. If you really want to make C programming look like
Perl programming, could you do it by adding new library calls, instead
of changing the semantics of existing ones?
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I just realized this may be a difference due to a between -current and
-stable, so I've moved discussion to -current to check. Apologies if
this was the wrong thing to do.
On Wed, 13 Sep 2000, Mike Meyer wrote:
It then fails to install for me with the error messages:
/tmp/sv001.tmp/setup.bin
I have two questions. Recently, I started seeing the message:
module sn already present!
when dhclient runs on my sn device. What causes this?
It's caused by the 'sn' driver's module being called 'sn' rather than
'if_sn'. The code in ifconfig that tries to autoload modules for
Robert Nordier wrote:
Julian Elischer wrote:
with newly CVSup'd sources (I cannot compile the bootblocks..)
(also with everything checked out to PRE_SMPNG)
It get's the following error:
/usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In
function `
Robert Nordier wrote:
Julian Elischer wrote:
with newly CVSup'd sources (I cannot compile the bootblocks..)
(also with everything checked out to PRE_SMPNG)
It get's the following error:
/usr/obj/usr/src/sys/boot/i386/loader/../libi386/libi386.a(pxe.o): In
ix?
Isn't a stray IRQ a hardware glitch? If so, I'd say that logging it
and then ignoring it would be the right thing.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Sep 7 14:35:55 laptop /kernel: microuptime() went backwards (10412.355980 -
10412, -694583121)y
this is bad.. right ? :-)
Well, at any rate it looks very funny. If this is a laptop, try
building a kernel without apm and see if that helps.
It only helps "hide" the problem. There's
looks like the boot loader is killing -current. I have a patch, but
it just cuts all the offending references.
Comments?
rebuild/reinstall libstand. Sorry; should have HEADS-UPped that one.
Warner
cc -nostdlib -static -Ttext 0x0 -o loader.sym
I have collected all the emails I've received and I have identified
at least two different causes:
There is a bogus i8254 implementation on certain Athlon Mobos, this
is a non-brainer since they should not use the i8254 but the TSC.
s/TSC/ACPI timer/
It might even work on those systems.
here, though.
Thanks guys,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I'd like to hear a few more success stories first (only one so far) from
people using the kit to add the driver to their 4.x systems. With all
the breakage in -current's PCI support at the moment, I don't expect to
hear too many people there reporting on it just yet.
Maybe
I've just committed a driver for the abovementioned RAID adapter families
provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver
will be maintained by Adaptec, with a little help from yours truly if
really necessary.
Excellent! Any ideas when this might be
an
onboard 7890.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
working kernel was built August 26, 10:05 GMT.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
At 01/09/2000 10:30, Mike Smith wrote:
I've just committed a driver for the abovementioned RAID adapter families
provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver
will be maintained by Adaptec, with a little help from yours truly if
really necessary.
With any luck
er?
(I'll probably throw out a response to myself once I get the CVS/recompile
done, assuming that incoming telnet works again.)
--mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Looks like 3dfx linux emulation aren't mixing well. Since I don't
use 3dfx, I turn off that module.
What we really need is a system that lets me specify *which* modules
to build. Hmmm.
mike
=== 3dfx
make: don't know how to make @/i386/linux/linux_ioctl.h. Stop
*** Error code 2
I've just committed a driver for the abovementioned RAID adapter families
provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver
will be maintained by Adaptec, with a little help from yours truly if
really necessary.
With any luck, we should see the complete set of
Maybe. It's also not clear to me whether my current breakage is PCI related
or device.hints related (it appears that the read of my /boot/devices.hints
file gets things garbled):
What makes you say that? This all looks fine to me. (The hang is not so
good though...)
Hit [Enter] to boot
are old, stupid
devices for compatability reasons so it's best to have a working hints
file around.
Just curious - are there no defaults at all if you don't have a hints
file somewhere? That seems a bit strange.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
configured in the kernel? Do both
methods throw out such data, or do both save it?
Basically, which will provide the smallest running kernel, and if it's
the same, which will boot fastest?
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cu
ation here
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
I tried just cvsup the gnu src today, but cvsup completed successfully w/o any
files. Can this be fixed w/o starting from a "clean slate" ?
Thanks,
Mike Endsley
--
Declared free
files. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from shooting yourself in the foot?
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
on each box makes my life much simpler.
As for GENERIC, it's what people run by default, and it can be used as
is on much hardware. The documentation is a bit behind - the handbook
should mention setting KERNEL in /etc/make.conf when it talks about
buildkernel and installkernel.
mike
Donn Miller writes:
Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having an
empty one keeps you from shooting yourself
Maxim Sobolev writes:
Mike Meyer wrote:
Donn Miller writes:
Mike Meyer wrote:
I do read cvs-all, and I missed it. Not did I find device.hints in the
relevant Makefiles. Can you provide a pointer to details on how
/boot/device.hints is used in the build process, or how having
Maxim Sobolev writes:
Mike Meyer wrote:
Will the system fail to boot if there isn't an empty device.hints
file?
No, it will boot, but some devices (like keyboard, console etc) would not work.
That's clearly not true - I just removed an empty /boot/device.hints
and rebooted
over the whole
mess).
Thanks to everyone who replied. I'm now typing this message from the
machine that I had to do the re-install on, so all is good.
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
John Baldwin writes:
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Sat Aug 26 11:14:35 GMT 2000)
/kernel text=0x2432ca zf_read: fill error
elf_loadexec: archsw.readin failed
Your floppy is bad. Try a different one.
Not necessarily. This also happens if
very well :-(.
-Mike
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
- End of forwarded message from Mike Pritchard -
--
Mike Pritchard
[EMAIL PROTECTED] or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
This is not an "IDE RAID" controller. It's an IDE controller with some
lame "RAID" software in the BIOS. We don't support this.
(excuse complete ignorance as far as IDE RAID below)
For the buildbox here, I decided to go ahead with Soren's ATA-100 RAID
suggestion, and bought an Abit
I'm curious -- what kinds of cards are supported by this routine?
Does this include the DPT SmartRAID V, as well as the older SmartRAID
IV? I've got an anonymous ftp server I need to rebuild -- it had
previously been running Slackware Linux, but as the kernel got
updated, the
Satoshi - Ports Wraith - Asami writes:
* From: Kris Kennaway [EMAIL PROTECTED]
* On Wed, 23 Aug 2000, Mike Meyer wrote:
* How does it decide whether or not a package conforms?
* Probably by looking for files which get installed in /usr/local or
* /usr/X11R6 instead of ${LOCALBASE
with perl modules installing in /usr/local no
matter where LOCALBASE points, I reported it at one point. Non-trivial
is an understatement.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
)/lib/5.6.0 to the search path
for modules.
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Konstantin Chuguev writes:
"Jacques A. Vidrine" wrote:
On Wed, Aug 23, 2000 at 01:01:59AM -0500, Mike Meyer wrote:
Um - why? If you removed the setting of LOCALBASE in that case, you
wouldn't change the disk layout at all.
I prefer installed executables, data files, and
Would it be possible to revert the DPT commits made by peter on
Mon Aug 7 18:48:14 2000 in the RELENG_4 branch? It seems that the
dpt_attatch is failing in bus_alloc_resource(9) for the IRQ, and I have
production machines that need worlds built for some other updates as
well.. I
Satoshi - Ports Wraith - Asami writes:
* From: Mike Meyer [EMAIL PROTECTED]
* However, I was wondering if there was anyone who could fix things that
* weren't PREFIX clean who would also find them on a regular
* basis. That's not you.
I can help you when the new package building cluster
nd I agree on that.
If the answer from the person who would have to approve the code had
come back "Ok, provide the code and we'll see how well it works in
practice", I'd do the code. But when it appears the code would never
make it into the tree to be used, why waste my time?
mike
To Un
ime?
'coz we're taking a page from Linus.
Does Linus tell people something is a bad idea, and then use it
anyway? Or does he just not bother to respond to questions about
whether or not something would be a usefull addition?
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with &q
to that :-)
Actually, two. You can *always* work on something yourself!
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
to be on a man page. Soren?
Mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Jacques A. Vidrine writes:
On Mon, Aug 21, 2000 at 11:59:26PM -0500, Mike Meyer wrote:
I'm curious - are there any committers who regularly use a system with
LOCALBASE set to something other than /usr/local?
I have LOCALBASE=/opt for a couple of years now.
OTOH, I also have a symlink
(much, *much*) smaller burncd.
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Kenneth D. Merry writes:
On Mon, Aug 21, 2000 at 10:54:49 -0500, Mike Meyer wrote:
I'm curious - is there some reason that the CDR ioctls (in
/usr/include/sys/cdrio.h) aren't supported for MMC cds? It looks like
doing them for MMC would be straightforward, it's the kind of thing
don't want to write it if it
will never go in the distribution.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Kenneth D. Merry writes:
On Mon, Aug 21, 2000 at 18:19:47 -0500, Mike Meyer wrote:
Kenneth D. Merry writes:
Which should actually be smaller than the flood of mail saying things
like "why doesn't burncd support my nice, standard-compliant CD-R?" In
fact,
the CD driver + MMC extensions that gets first crack at CDROM
drives, and recognizes MMC drives, but not others?
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
use the same basic command set (MMC)
as SCSI ones, only they don't have legacy problems - so it should be
possible.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Christopher Masto writes:
I'd rather see cdrecord work on ATAPI CD-Rs. burncd gives me a lot of
trouble.
Spoke to soon - according to the pkg/DESCR file, it should work on
them now.
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
I'm curious - are there any committers who regularly use a system with
LOCALBASE set to something other than /usr/local?
Thanx,
mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Warner Losh writes:
In message [EMAIL PROTECTED] Mike Meyer writes:
: The nasty downside of the the module system is that people who don't
: adequately test module code before checking it in will screw up kernel
: builds for kernels that don't need that code.
But I did test it. But I had
Warner Losh writes:
In message [EMAIL PROTECTED] Mike Meyer writes:
: Warner Losh writes:
: In message [EMAIL PROTECTED] Mike Meyer writes:
: : The nasty downside of the the module system is that people who don't
: : adequately test module code before checking it in will screw up kernel
to be the one that caused the problem this time.
Pointing fingers isn't the difference I was talking about. It's more
in the attitude after the fact. On FreeBSD, it's "Ok, I fixed
it." Elsewhere, people apologize for breaking the bulid.
mike
To Unsubscribe: send mail to [EMAIL
builds for kernels that don't need that code.
Since you probably don't need the oldcard module. Just comment it out
of /usr/src/sys/modules/Makefile, and rebuild the kernel. You may want
to comment out pccard as well.
mike
=== oldcard
cc -O -pipe -D_KERNEL -Wall -Wredundant-decls
On Thu, 10 Aug 2000, Evan Oldford wrote:
This happens whenever I shutdown the system too. It tries to unmount one of
the partitions and hangs before the "dirty flag" is removed from any of the
partitions. Thats why all the partitions are checked/repaired by fsck
_everytime_ I boot.
ys/gnu/dev/sound/pci/emu10k1.h
from -current and recompile kernel.. no problems.
-mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I wonder what the back servers that handle the mail are running though... I
wonder if they are gonna be changed to windows 2000 ..
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
* Stephen McKay [EMAIL PROTECTED] [000805 08:49] wrote:
Patch 2 is smaller and possibly controversial. Normally bufdaemon and
syncer are sleeping when they are told to suspend. This delays shutdown
by a few boring seconds. With this patch, it is zippier. I expect people
to
1001 - 1100 of 1810 matches
Mail list logo
