I have no complains regarding how linux implements support for
different features. I have some idea how hard it is even if you have
all documentation (because documentations contain erros, I know it from
my own experience). When you do not have documentation --- it is much
much harder.
What bothers me is that everything was working fine until recent upgrade.
For some reason superblock last write time is always in the future, which
causes errors. How to fix this is a question I would like answered.
Lazar
*/Mike McCarty <mike.mccarty@sbcglobal.net>/* wrote:
Gene Heskett wrote:
> A slim possibility is that you have acpi enabled on an nforce2
chipset.
> If thats the case, either shut it off, or go upgrade the bios to the
> latest as that fixed some other, non-disk related problems that
> several of us have had with that chipset.
I subscribe to three email echoes about Linux, and I see a
recurrent theme: mysterious errors, solved by booting with
ACPI turned off.
ISTM that either: Linux just doesn't properly support ACPI, or
BIOS implementors just don't know how to get it right.
Either way (and I don't care which) perhaps the default boot
should be with ACPI turned off, and add an option to turn it
on.
I had several mysterious problems with my machine until I
put "acpi=off" into my grub.conf.
Stock Windows XP has no problems with the ACPI on my machine.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com