Silly question … what happens if you boot WITHOUT nomodeset, but instead in the grub boot menu, remove the entry “vga=0xYYY” ? There is a bug report where that is a solution for some Intel integrated graphic user on openSUSE-11.4, and I am curious if your hardware falls in that category.
In that case, it appears the nominal “Intel” graphic driver is not working for you (assuming that your install is good). Along that lines (is this a good install ) ? did you run an md5sum of the downloaded .iso file and compare that to the md5sum on the download website ? Were they they the same? Assuming they were the same, did you burn the .iso file to a dvd/cd at the slowest speed your burner allows to a +R or -R (and NOT an RW) using high quality media and NOT some bargain basement special ? And did you run the media check option on the dvd/cd and have it pass?
Assuming you did all that appropriately, then we know Intel graphic driver is not working and FBDEV driver (which you get when you use the boot code ‘nomodeset’) is working.
You could try (1) vesa driver, or (2) intellegacy driver.
I recommend you (having done the above cd/dvd quality checks) install the application midnight commander (mc) if not already installed. You may need that to do edits of text files in a text mode and ‘mc’ is VERY user friendly. With ‘mc’ installed you can launch it by typing ‘mc’ (no quotes) and use the easy to follow Fx keys to navigate.
Then go ahead and edit the /etc/X11/xorg.conf.d/50-device.conf file (with root permissions) , so as to have it load the intellegacy video driver (which is in fact a very old version of the Intel graphic driver) and see if that works better. Assuming you have the rpm xorg-x11-driver-video-intel-legacy installed, then the /etc/X11/xorg.conf.d/50-device.conf file should look like (after your edits with root permissions):
Identifier "Default Device"
## Required magic for radeon/radeonhd drivers; output name
## (here: "DVI-0") can be figured out via 'xrandr -q'
#Option "monitor-DVI-0" "Default Monitor"
Note the line I added.
Then reboot and test.
If “intellegacy” does not work, then try “vesa” instead of “intellegacy” in same file.
Note from command line one can restart the PC with:
As an aside, did you confirm the quality of your installation CD/DVD was good prior to installing ? ie run the md5sum against your downloaded .iso file and confirm that the downloaded .iso file has the same md5sum as that posted on the download web site? Also burn to a +R or -R CD/DVD (and not to an RW) at the slowest speed your burner allows to a high quality media (and not some bargain basement special) ? And finally did you perform the ‘mediacheck’ on the installation CD/DVD to confirm it passes ?
I note openSUSE-11.4 comes with the 2.14 Intel driver. There is a 2.15 Intel driver available from Intel, but it has not been packaged yet for openSUSE. At some point in the future it may be packaged for tumbleweed, but its not there yet. I note from the openSUSE weekly news an openSUSE user has successfully installed the 2.15 driver, with a blog article here: Ladislav’s blog: Installing latest Intel graphics driver to openSUSE 11.4
That may or may not help. It may in fact make things worse forcing a re-install. … but then again, it may work. Its up to you to decide if it worth following. Note one needs a reasonable level of Linux knowledge to follow that blog.
Edit - note there is an rpm available in the unstable X11 repos:
Yes there is. It requires a change to the /boot/grub/menu.lst file. Post here the content of that file and I can point out the edit.
I am curious thou, is it the FBDEV driver that is being loaded with this combination? Can you paste the contents of your /var/log/Xorg.0.log file to SUSE Paste and the post here the URL where that paste is located ?
Interesting … I see many " (II) intellegacy(0) " entries, which says to me that even though the ‘nomodeset’ boot code is specified, as long as “intellegacy” is specified in the 50-device.conf file, then the intellegacy (old intel version) driver is loaded and not the FBDEV driver.
On 2011-04-26 19:06, AndrewjBarratt wrote:
> i accidentally booted today without “nomodeset” and have discovered the
> screen isnt actually off, its just that dark that it appears that its
> off, i can faintly in the background see the desktop
That is a very important detail, you know. It might just be that the
backlight is off.
My laptop also has a GM45 chipset and works fine without doing anything.
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
To be expected, since “nomodeset” doesn’t actually load a driver. The “intel” driver cannot load without KMS support, so “fbdev” loads by default. If you specify “intellegacy” (KMS not required) it will load whether or not you specify “nomodeset”.