1 |
Tim Ames posted |
2 |
<6.2.0.14.2.20050709130256.027253c8@××××××××××××××××××.org>, excerpted |
3 |
below, on Sat, 09 Jul 2005 13:05:25 -0700: |
4 |
|
5 |
> Thanks for the reply. I updated the bios on the sk8v with the beta version |
6 |
> that was posted on the asus website. |
7 |
> |
8 |
> bad news got a cmos error. Went through all the proper steps, called tech |
9 |
> at asus and I fried the bios chip they |
10 |
> are sending me a new one, so next week I'll try this again. But this was a |
11 |
> fresh install, fresh fdisk and I did the first emerge sync and this happened. |
12 |
|
13 |
You've /gotta/ have something /seriously/ wrong with that thing! MD5s |
14 |
going crazy, a BIOS update failing (I've /never/ seen that happen unless |
15 |
the power dies in the middle). There's just too much weird stuff going on |
16 |
for it to be anything but hardware! |
17 |
|
18 |
Hopefully, it was the old BIOS, and an entirely new chip fixes it. If |
19 |
not, I'd consider switching boards or memory or CPU or SOMETHING! If |
20 |
that isn't possible, then yes, on that one, I'd say run a binary install |
21 |
of /something/, because if it's that unstable, I can't believe you could |
22 |
reliably compile stuff either, and if you can't do that, who's to say |
23 |
/what/ you'll find yourself overwriting, so better go with precompiled |
24 |
binaries. Even then, you've no idea when it'll suddenly start overwriting |
25 |
stuff on your disk, so be prepared to reinstall when needed, and keep |
26 |
daily, even hourly, backups, to clean media each time so it can't |
27 |
overwrite /that/ with crazy stuff! |
28 |
|
29 |
-- |
30 |
Duncan - List replies preferred. No HTML msgs. |
31 |
"Every nonfree program has a lord, a master -- |
32 |
and if you use the program, he is your master." Richard Stallman in |
33 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
34 |
|
35 |
|
36 |
-- |
37 |
gentoo-amd64@g.o mailing list |