Op 02-11-12 11:39, Oddball schreef:
Op 01-11-12 23:48, Felix Miata schreef:
On 2012-11-01 20:28 (GMT+0100) Oddball composed:
Felix Miata composed:
Find menu.lst if it exists in the /boot tree somewhere and show us what it contains. Also if you can, find grub.cfg in the /boot tree somewhere, and show us what it contains.
# menu.lst
default 0 timeout 8 gfxmenu (hd0,2)/message ##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 12.2 root (hd0,2) kernel /vmlinuz-3.7.0-rc2-4-desktop root=/dev/system/root video=1024x768 resume=/dev/system/swap splash=silent quiet showopts initrd /initrd-3.7.0-rc2-4-desktop-kdump
###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader +1
###Don't change this comment - YaST2 identifier: Original name: failsafe### title Veilige modus -- openSUSE 12.2 root (hd0,2) kernel /vmlinuz-3.7.0-rc2-4-desktop root=/dev/system/root showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe initrd /initrd-3.7.0-rc2-4-desktop-kdump
###Don't change this comment - YaST2 identifier: Original name: linux### title Kernel-3.7.0-rc2-4-desktop root (hd0,2) kernel /vmlinuz-3.7.0-rc2-4-desktop root=/dev/system/root video=1024x600 resume=/dev/system/swap splash=silent quiet showopts initrd /initrd-3.7.0-rc2-4-desktop
It appears you don't *need* to change anything from what YaST has done, but for your own convenience I suggest to add the following to menu.lst:
title openSUSE default kernel with KDM & resume root (hd0,2) kernel /vmlinuz showopts resume=/dev/system/swap vga=791 video=1024x768 initrd /initrd
title openSUSE default kernel with neither KDM nor resume root (hd0,2) kernel /vmlinuz showopts noresume vga=791 video=1024x768 3 initrd /initrd
The VGA option does not exist, besides that it is tft, it returns with a lot of modes which do not apply, so i will remove that. The only thing is still: root (hd0,2) Filesystem type is ext2fs. (but this is not true, as lvm proposed ext4 for that, and i choose to give it a try.) partition type 0x83 (?) so if i am able to find that file, i also have to know the partition type for ext4. But with that changed, it should work.
Future updates to menu.lst from updates and new kernels will not change these. The latter is similar to what you typed from the Grub prompt. This form makes it easier at each boot for you to edit on the fly should you wish or need to without having to fall back to a grub prompt. For instance, if you want for a new boot just once with KDM but without resume, either select the latter, then BS once to make the 3 disappear before hitting enter, or select the first, and edit away noresume.
# Device map, what is left of it from grub2: (also in grub)
Actually YaST created this for Grub Legacy, even though not the default. NAICT, Grub2 doesn't use device.map.
(hd0) /dev/disk/by-id/ata-RunCore_64G-C_SSD_000901022255 (hd1) /dev/disk/by-id/usb-Single_Flash_Reader_058F63356336-0:0
Note that you still are booting with Grub2 until you perform the steps outlined in http://orgs.man.ac.uk/documentation/grub/grub_3.html#SEC9 or get YaST to do it. To get a good boot menu with less work, choose bootloader from the YaST menu and make it install Grub in the place where Grub2 is now, which seems to be EXT2 sda3 on your system. If you cannot get that to work, report back with those two files for next steps to try.
I already let Yast install it before i asked the question. There were no entries left, so i had to let yast make a proposel The thing is that the /boot partition was proposed by lvm, and suggested ext4 which i did. A big mistake to let lvm handle my set-up. So what i was trying to do is change yasts suggestion: 'ext2fs' into 'ext4fs', what it actually is. But i am again, not able to find where this comes from.
I'm a little lost about this. Maybe it's just about labeling for Grub boot menu setup. I thought you have EXT4 on your LVM volume(s), but EXT2 on your sda3 /boot.
Please do not get me wrong: I want to learn these things, because kind of things happen regularly when testing, and with no working, or non-existing tools, one must know/learn how to fix things without them.
boot.readme:
set LOADER_TYPE="none" in /etc/sysconfig/bootloader. Hint is used
You should change it to "grub" and let yast2-bootloader do what it knows how to do at update and new kernel times. You can always tweak menu.lst after YaST gets done with it.
It is "grub" now, but it only can boot from the last option:
title Kernel-3.7.0-rc2-4-desktop root (hd0,2) kernel /vmlinuz-3.7.0-rc2-4-desktop root=/dev/system/root video=1024x600 resume=/dev/system/swap splash=silent quiet showopts initrd /initrd-3.7.0-rc2-4-desktop
But than it searches and corrects things, to find the bootstraps.
/boot/vmlinuz and /boot/initrd symlinks as files which is already point to actual kernel. WARNING after kernel upgrade you must update also configuration manually, otherwise you cannot boot.
That is what i wanted to do, create it like this, because it worked en is simple. But when i actually do it, yast refuses to save/apply, and says: name already in use, choose another one.
Again I'm lost. Choose another name for what, a stanza? If so, change one.
It does not matter what i change, it is always wrong.
/boot/vmlinuz /boot/initrd
is what i wanted to be in the lines, and:
video=1024x768 resume=/dev/system/swap splash=silent quiet showopts
As i did not understand what was meant, i tried to change every line, but after many tries, the result was the same dialog box and the 'boing', so i assumed another bug, and i quit.
At this point my feelings towards a fresh install grew bigger.
Note too that from cmdline login as root on tty[1-6] life is easier if you learn to use Midnight Commander to navigate and view and edit files. Just mc as root, use the arrow keys to move around, and as the bar at the bottom shows, F3 to view highlighted file, F4 to edit highlighted file, F9 menu to do other things like search for a file or what file contains a string, all very easy compared to typing and remembering what to type for everything you want to do at repair time.
If command not found for mc, just 'zypper in mc' and try again.
At this point 'ctrl+alt+F1-7' to get to a tty and back, very accurate. cnf mc, brought up the repo, and the command to install it, also very accurate. So it is installed now.
As a test of mc, navigate into /etc/sysconfig, and look at bootloader file with F3. There you should see the default cmdline options that installation chose to use. For Grub Legacy this is the "DEFAULT_APPEND=" line. It is important information to rebuild your Grub menu, if it actually needs rebuilding. Before you try rebuilding, show it/them to us.
Have you tried this yet? It really can make the cmdline environment easy to use.
DEFAULT_APPEND=" video=1024x600 resume=/dev/system/swap splash=silent quiet showopts"
I would like to have the default on 1024x768 for this eee pc.
But there is no editing the file here, even when root with mcedit, "This is not a normal file" (Normally i use from desktop 'alt+F2>kdesu kate' to look at and edit rootfiles, which is npwse.)
-- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-4-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.9.2 "release 511" -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org