1 |
> Same board. Same BIOS upgrade (1.8 to 1.B). I got 2.6.13-gentoo-r3 to work, |
2 |
> but I'm not using SATA so I can't speak to that. But I couldn't get the |
3 |
> nvidia-kernel module to load. I had to upgrade to the latest unstable |
4 |
> version to get it to work at all. But then I discovered I couldn't even get |
5 |
> into the BIOS menu because the keyboard wasn't initialized until after it had |
6 |
> stopped listening for the DEL keystroke. I downgraded back to 1.8 and now it |
7 |
> won't POST! |
8 |
> |
9 |
> Note that the versions released went from 1.8 to 1.9 to 1.B. The fact that |
10 |
> 1.A is missing from the lineup makes me wonder if they were having serious |
11 |
> problems with it and decided to pull it. Maybe 1.B still has some of those |
12 |
> problems. |
13 |
> |
14 |
> My ($10) replacement chip is slated to arrive today. I've had to get by with |
15 |
> Knoppix on a Windows box for nearly a fortnight. And this was in the middle |
16 |
> of my exams! |
17 |
> I'm half tempted to buy a chip programmer so that this can't happen again. |
18 |
> And if they release any more shoddy BIOS versions, I'd be tempted to avoid |
19 |
> MSI. |
20 |
|
21 |
There was some issue discussed earlier about nvidia and 2.6.13 kernels |
22 |
which basically said to use the unstable (and up to date) version of the |
23 |
nvidia drivers. |
24 |
|
25 |
Did you try connecting the keyboard via the PS/2 ports? |
26 |
I had the same problem with my MSI board until I did it.Enabling Legacy |
27 |
USB support also works most of the time. I also found that sometimes the |
28 |
USB keyboard won't be initialized between the time the BIOS is done |
29 |
posting and until the linux kernel enables it making a mess of LILO but it |
30 |
only seems to happen on a boot out of 2. |
31 |
|
32 |
|
33 |
There are plenty of cases where a BIOS updates skip a version steps. |
34 |
|
35 |
-- |
36 |
gentoo-amd64@g.o mailing list |