public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Randolph <mattr@erols.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] MSI Neo2 Platinum woes follow up
Date: Sat, 29 Oct 2005 15:23:51 -0400	[thread overview]
Message-ID: <4363CC47.80607@erols.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0510291313450.8162@melchior.nuitari.net>

Nuitari wrote:

>
> 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.

FWIW, I was cheerfully using 2.6.13 with nvidia-kernel-1.0.6629-r6 for 
some time with no ill effects. Starting as of about an hour ago, I'm 
using 1.0.7676-r1 but I may revert to the stable version if I discover 
any issues with my applications.

>
> 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.
>
I tried both USB and PS/2 keyboards without luck. Part of the problem is 
that you need to be able to get into the BIOS to change that setting. 
And after a flash, it might have reverted to the default value, which 
may or may not be what you want. That should be a problem that is unique 
to USB keyboards though, so I was surprised that I had a similar problem 
with a PS/2 one.

>
> There are plenty of cases where a BIOS updates skip a version steps.
>
Thank you for the reminder. I notice that they skipped 1.6 too. I know 
that software of any kind sometimes skips a version between releases. I 
expect there can be any of a wide range of reasons for this, but I 
wouldn't be surprised if it is at least occasionally because of problems 
with a release candidate.

BTW, the chip came and I'm back in business. There's no place like 
/home. Do not envy me the two weeks worth of updates I'm about to 
emerge. Fortunately, I have decided that I can still get away with using 
1.8 for now (after all that!).

I shouldn't have been nasty about MSI previously. I have been very happy 
with them by and large. And that's based on owning about half a dozen of 
their motherboards over the last few years. I do hope they resolve any 
issues people are having with 1.B, though.

You may find this even more entertaining than version numbers in hex: 
You know how big a PLCC-32 chip is? That's right, it's about the size of 
your fingernail. The box they sent my chip in is big enough to hold a 
small pizza.

-- 
gentoo-amd64@gentoo.org mailing list



      reply	other threads:[~2005-10-29 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29  6:21 [gentoo-amd64] MSI Neo2 Platinum woes follow up Lee Thompson
2005-10-29  6:40 ` Nuitari
2005-10-31 18:09   ` Lee Thompson
2005-10-29 13:25 ` Matt Randolph
2005-10-29 17:22   ` Nuitari
2005-10-29 19:23     ` Matt Randolph [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4363CC47.80607@erols.com \
    --to=mattr@erols.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox