Text 13690, 72 rader
Skriven 2009-12-19 13:42:06 av James Bradley (1:342/77.0)
     Kommentar till en text av Wayne Chirnside
Ärende: All better now
======================
On or about 12-14-09 18:21, WAYNE CHIRNSIDE allegedly uttered "Re: All better
now" to JAMES BRADLEY:

 -=> ROSS CASSELL wrote to JAMES BRADLEY <=-

 RC> 12 Dec 09 15:24, you wrote to Wayne Chirnside:

 JB> Long long ago, in a galaxy... I digress. I recall reading the order of
 JB> control that occurs after a boot, and took from those words that the
 JB> firmware on the vid (I *think* it's a BIOS routine.) runs through its
 JB> business before POST on the main board, and then any other controllers
 JB> (IE: NIC SCSI/RAID...) before the kernel is called.

 RC> A. Layer One = BIOS
 RC> B. Layer Two = Operating System
 RC> C. Layer Three = Programs

 RC> The individual I was conversing with, was insisting that his bootloader
 RC> was loading a video driver, before his BIOS even posted and executed
 RC> the bootloader.

 WC> The firmware in BIOS'ed video card *was* in fact linked to
 WC> lilo.conf in the MBR *before* the motherboard BIOS
 WC> attempted to take over, and failed dramatically,
 WC> to reestablish itself.

Your machine locks with the NVidia card, and is fine without? This leads back
to an address conflict, no? BIOS isn't being told to drop its onboard vid, or
is reserving something you need for the NVidia. 

 WC> Anyway, as I mentioned all before as well
 WC> simply google the following keywords:
 WC> Linux GeForce MX-400 experiences

This is why I suspect the canned NVidia driver. I know ATI has a
aftermarket/isolationism driver that is run in an executable file, and I
suspect NVidia is guilty of the same tomfoolery. I'm not up on it, and I can
only write from what I know in the here and now. That's the way it used to
work, and what is up to date aint me. <G>

 WC> IOW's plenty of other people found this out before
 WC> me and but also unfortunately after I followed
 WC> some very unsafe and ill advised advice.

I'm all ears, if you'd care to further my understanding of "the latest and
'greatest'".

 WC> Right now that card and it's software driver sits in the bottom
 WC> of a drawer with my nefver intending to mess with such
 WC> a piece of poorly designed firmware and software *both*.

Might be a good candidate for a "friends" Windows machine. <G+D>

 WC> As a *final*, I hope, comment on this issue I
 WC> may very well get an Nvidia equipped motherboard
 WC> with compatible BIOS only because quite soon
 WC> Nvidia's driver will be made available as part
 WC> of the new Linux kernel and thus not taint the kernel
 WC> rendering it worse than useless with another video card
 WC> as does Nvidia's proprietary software for the GeForce MX-400 .

It might be a keeper after all of that. Maybe the N-S bridge by the same
company can be copasetic with it. What's the buzz on their chipsets? I tend to
taint my opinions with the company's past performance. This *does* sound like a
doozie!


... Why be difficult, when with a bit of effort you can be impossible.
___ MultiMail/Linux v0.49

--- Maximus 3.01
 * Origin: -=-= Calgary Organization CDN (403) 242-3221 (1:342/77)