On Mon, 30 Apr 2012 12:28:30 +0530, Felix Miata <mrmazda@earthlink.net> wrote:
On 2012/04/30 11:26 (GMT+0530) phanisvara das composed:
i add "nomodeset" to the kernel boot parameters. it's not supposed to be needed after properly installing video, but it does no harm.
Oh, but it can...
i'm sure it can, but for me it's necessary, even with nueveau (IIRC). depends on the video hardware and drivers used. i'm NOT saying everybody should include it, no questions asked.
there was a long discussion somewhere...<snip>
I remember the thread, but not how long ago it ran or the particular subject line, which IIRC was poorly related to the actual very long discussion that ensued.
exactly; not enough to go looking for it now.
The way I understand KMS & nomodeset:
As of 11.3, and since, adding nomodeset during installation only hurts nothing for the installation process itself, which uses a (slow) generic video driver supported by the maximum possible range of video chips.
The problem is the installation process automatically adopts added boot parameters from installation to the installed bootloader stanzas. This means post-installation, nomodeset for those who don't customize bootloader stanzas during installation to explicitly remove nomodeset from them, is turning off KMS, which in turn completely prevents use of FOSS radeon, intel and nouveau drivers, which are the drivers most non-gaming people actually need for normal use.
i'm 'non-gaming people' and have been using nueveau (or whichever way it's spelled) for a while since 12.1. for some reason though everything looks "clearer" with the prop. driver, so i went back to it. perhaps i could have solved this by fiddling with xorg parameters or xrandr, but installing nvidia was easier. didn't know the installer adopted the used kernel parameters; interesting. during the last kernel update 'nomodeset' was automatically removed from my menu.lst, and i had to add it back again.
Proprietary non-FOSS ATI (IIUC) & NVidia (at least) drivers _need_ KMS turned off (via nomodeset) to function.
Whatever method *buntu and Fedora may be using to work around this FOSS vs. proprietary conflict I have no idea. I've several of those installed for occasional use, but never use proprietary drivers with any Linux.
-- phani. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org