Re: [gentoo-amd64] MSI Neo2 Platinum woes follow up

[Nuitari <nuitari@melchior.nuitari.net>]

> Same board.  Same BIOS upgrade (1.8 to 1.B).  I got 2.6.13-gentoo-r3 to work, 
> but I'm not using SATA so I can't speak to that.  But I couldn't get the 
> nvidia-kernel module to load.  I had to upgrade to the latest unstable 
> version to get it to work at all.  But then I discovered I couldn't even get 
> into the BIOS menu because the keyboard wasn't initialized until after it had 
> stopped listening for the DEL keystroke.  I downgraded back to 1.8 and now it 
> won't POST!
>
> Note that the versions released went from 1.8 to 1.9 to 1.B.  The fact that 
> 1.A is missing from the lineup makes me wonder if they were having serious 
> problems with it and decided to pull it.  Maybe 1.B still has some of those 
> problems.
>
> My ($10) replacement chip is slated to arrive today.  I've had to get by with 
> Knoppix on a Windows box for nearly a fortnight.  And this was in the middle 
> of my exams! 
> I'm half tempted to buy a chip programmer so that this can't happen again. 
> And if they release any more shoddy BIOS versions, I'd be tempted to avoid 
> MSI.

There was some issue discussed earlier about nvidia and 2.6.13 kernels 
which basically said to use the unstable (and up to date) version of the 
nvidia drivers.

Did you try connecting the keyboard via the PS/2 ports?
I had the same problem with my MSI board until I did it.Enabling Legacy 
USB support also works most of the time. I also found that sometimes the 
USB keyboard won't be initialized between the time the BIOS is done 
posting and until the linux kernel enables it making a mess of LILO but it 
only seems to happen on a boot out of 2.


There are plenty of cases where a BIOS updates skip a version steps.

-- 
gentoo-amd64@gentoo.org mailing list