It may be useful to see what the difference is between a normal boot and a failsafe boot on your PC.
Please post the contents of your menu.lst file to New - Pastie (and provide us with the website/URL location) so we can see the difference between a normal boot and a fail safe boot.
You can do that by running:
su -c 'cat /boot/grub/menu.lst' > bootfile.txt
and enter root password when prompted and then open bootfile.txt with a text editor and copy and paste the contents to New - Pastie and post here the URL/web site location.
Just tried the .rpm which I got from the Intel website, no luck, if i go into the ‘configure display setting’ in my bottom panel it says unknown in red at the top.
And as far as that command, it returns a No such file in directory.
I dread to think what has been messed up as a result of this attempt which (without more detail) I believe to have been ill advised.
Copy and paste that command (don’t try to retype it) into a terminal, as a regular user, where that terminal has just been opened (and hence it is in your /home/daredeval directory). The file will be there. That command works on ALL openSUSE versions.
su -c 'cat /boot/grub/menu.lst' > bootfile.txt
Once the command is complete, if in gnome type:
gedit bootfile.txt
and if in kde type
kwrite bootfile.txt
and then copy it to: New - Pastie and don’t forget to copy the resultant URL and post here.
This is basic Linux stuff … so please just have patience and keep trying and be assured that it DOES work.
My guess it is likely either “highres=off” or “x11failsafe” that enables your “failsafe” kernel(s) to boot, while the one’s without that boot code do not. I recommend you test that hypothesis / guess of mine. In the very first boot/splash menu (where you select the kernels upon boot) select a normal (non-failsafe) kernel to boot, and type: highres=off x11failsafe
… such that will show up on the options line and there will be a space between the 1st letter of highres and the “5” in vga=0x305. Do they boot now to full screen ?
If that is the case, this is a driver problem and you need to tell us what driver is in use when you get the 5x5 screen and what driver is in use when you get the full screen. There is advise on how to do that here :
Please read both the above posts and then please tell us what graphic driver is in USE when you get the 5x5 and what one is in use when you get the full screen.