[opensuse] How to get the correct entries in Grub (legacy)?
Hi all you people that selflessly helped me the last few days, ;-) Felix dragged me trough a fastcourse booting without bootloader, and i thank him for taking the effort and the patience to help me. His deduction made it possible to boot my eee pc again. (remnants of grub2 need:) grub>linux (hdo,msdos3)/vmlinuz noresume 5 grub>initrd (hd0,msdos3)/initrd grub>boot Brought me back into my desktop again. Installing the grub legacy went ok sofar, that there were no entries left on the drive, so i asked to propose them to me. It looked right to me, but i get an error message, and only the Kernel option, the last one boots, but not gladly. The message is this one: 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 (?) kernel /vmlinuz-3.7.0-rc2-4-desktop root=/dev/system/root video=1024x600 (rather 1024x768) resume=/dev/system/swap splash=silent quiet [linux-bzImage, setup=0x4200, size=0x4cf960] initrd/initrd-3.7.0-rc2-4-desktop-kdump Error 15: File not found My question is: How do i find the right things to put here, and how do i do it? -- 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
On 2012-11-01 16:34 (GMT+0100) Oddball composed:
My question is: How do i find the right things to put here, and how do i do it?
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. 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. 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. 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. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012-11-01 16:34 (GMT+0100) Oddball composed:
My question is: How do i find the right things to put here, and how do i do it?
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.
Op 01-11-12 16:58, Felix Miata schreef: menu.lst # Modified by YaST2. Last modification on do nov 1 16:47:34 CET 2012 # THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader # For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader 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 -----------------------------------------------________________________----------------------------------------------------------------------------------- Device map, what is left of it from grub2: (also in grub) (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. 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 /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. So everything takes too much time, and some things still are not fixed. The upstream theme looks absolutely good enough for me: grub background is very nice, and login screen is acceptable, so i will use that for a while. If i am not able to get it done: fix the booting, i will choose to get rid off the lvm stuff, and start over. I am getting very tired, working for days without pause takes its toll, as you already noticed earlier.
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.
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.
## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(grub,lilo,none) ## Default: grub # # Type of bootloader in use. # For making the change effect run bootloader configuration tool # and configure newly selected bootloader # # LOADER_TYPE="grub" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: string ## Default: "splash=silent quiet showotps" # # Arguments for kernel which is used like default boot section. # If the options is commented perl-Bootloader uses his default arguments # for kernel. # DEFAULT_APPEND="video=1024x768 resume=/dev/system/swap splash=silent quiet showopts" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: string ## Default: none # # VGA option for kernel which is used like default boot section. # If the options is commented or empty perl-Bootloader doesn't use it. # Empty option could be cause of broken size of fonts etc. # DEFAULT_VGA="" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: string ## Default: "showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe" # # Arguments for kernel which is used like failsafe boot section # If the options is commented perl-Bootloader uses his default arguments # for kernel. # FAILSAFE_APPEND="showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: string ## Default: none # # VGA option for kernel which is used like failsafe boot section. # If the options is commented or empty perl-Bootloader doesn't use it. # Empty option could be cause of broken size of fonts etc. # FAILSAFE_VGA="" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: string ## Default: "splash=silent quiet showotps" # # Arguments for XEN kernel in Dom0. # If the options is commented perl-Bootloader uses his default arguments # for XEN kernel. # XEN_KERNEL_APPEND="video=1024x600 resume=/dev/system/swap splash=silent quiet showopts" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: string ## Default: none # # Arguments for XEN hypervisor # Usually it is empty or includes arguments like crashkernel for kdump etc. # XEN_APPEND="" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: string ## Default: none # # VGA option for XEN kernel. # If the options is commented or empty perl-Bootloader doesn't use it. # Empty option could be cause of broken size of fonts etc. # XEN_VGA="" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: yesno ## Default: no # # Should the boot cycle detection be used to # avoid unconditional reboot cycles of not # supervised system. # CYCLE_DETECTION="no" ## Type: integer(0:) ## Default: 1 # # The number of the entry in grub's menu.lst # which should be used on the next reboot cycle. # Note that the first entry has the number 0. # CYCLE_NEXT_ENTRY="1" ## Path: System/Bootloader ## Description: Bootloader configuration ## Type: list(floppy,mbr,root,boot,custom,none) ## Default: mbr # # Location of boot loader. # For making the change effect run bootloader configuration tool # # LOADER_LOCATION="" -- 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
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 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.
/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.
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.
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. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
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
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
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
On 2012-11-02 15:12 (GMT+0100) Oddball composed:
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.
What do you mean by "that"? vga=791 would not apply to a 1024x600 screen, but would on a 1024x768 screen, and I can't find anywhere that you told us which it is you have, only where you wrote "1024x600 or 1024x768". It must be one or the other, not both. So, take away the vga=791, and change the video= to whatever your screen's resolution actually is. Which model eee pc do you have? What screen resolution does it have?
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 (?)
I have no idea where this is from. Exactly when do you see it? Is part of it something you see on your screen, and part your description of what you see? Please distinguish between what appears on screen and your added comments. EXT2 is probably on your sda3 /boot partition, and EXT4 is probably on your LVM partitions. If you show us your fstab this might become clear. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012-11-02 11:39 (GMT+0100) Oddball composed:
...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.
Please explain "searches and corrects" in some detail, and what you mean by "find the bootstraps". How does this selection differ in result from what happens when you try the others?
It does not matter what i change, it is always wrong.
Change using what and how to change? Are you logged in as regular user?
/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,
http://www.kernel.org/doc/Documentation/kernel-parameters.txt explains what most mean. The placement of showopts determines how much of cmdline you can see to edit when the Grub menu is on the screen to boot.
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.
For editing menu.lst apparently you're trying to use the wrong tool. If there was a bug, others would have had the same problem a long time ago. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 02-11-12 16:06, Felix Miata schreef:
On 2012-11-02 15:12 (GMT+0100) Oddball composed:
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.
It is a too high number, and not in the list of available modes. i can 'scan' but it is difficult for me to know how fi 80x43 looks like before i see it, and this applies only for the text that is shown during boot, which is about 3 seconds? Please no offense, i am 'cool' with your input.
What do you mean by "that"? vga=791 would not apply to a 1024x600 screen, but would on a 1024x768 screen, and I can't find anywhere that you told us which it is you have, only where you wrote "1024x600 or 1024x768". It must be one or the other, not both. So, take away the vga=791, and change the video= to whatever your screen's resolution actually is.
Which model eee pc do you have? What screen resolution does it have?
I have a 901, and the resolutions are both. 1024x600 is ok, but best is 1024x768.
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 (?)
I have no idea where this is from. Exactly when do you see it? Is part of it something you see on your screen, and part your description of what you see? Please distinguish between what appears on screen and your added comments.
It appears on the black screen instead of booting, immediately after the bootloader choices screen.
EXT2 is probably on your sda3 /boot partition, and EXT4 is probably on your LVM partitions. If you show us your fstab this might become clear.
No it is not. I remember that because i wondered why lvm choose ext4 for a /boot partition, i always use ext2 for that, because it nearest to fat16. And does not need journaling of a kind, as it is static, sometimes changed information.
/dev/system/swap swap swap defaults 0 0 /dev/system/root / ext4 acl,user_xattr 1 1 /dev/disk/by-id/ata-RunCore_64G-C_SSD_000901022255-part3 /boot ext4 acl,user_xattr 1 2 /dev/system/home /home ext4 acl,user_xattr 1 2 /dev/disk/by-id/ata-RunCore_64G-C_SSD_000901022255-part1 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=nl_NL.UTF-8 0 0 /dev/disk/by-id/usb-Single_Flash_Reader_058F63356336-0:0-part1 /windows/D vfat users,gid=users,umask=0002,utf8=true,nofail 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0
-- 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
On 2012-11-02 11:39 (GMT+0100) Oddball composed:
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.
Now it's time to use it. Login as root on a tty, open mc, and go fix menu.lst....
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.
All the eeepcs I checked have 1024x600 or 1368x768 screens. Which is yours?
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.)
If you are in X trying to do these system file modifications, then you're likely not root, and editing system files is problematic. Until you are able to get into X as root to start with, for menu.lst, device.map, fstab, bootloader and other system files, do Ctrl-Alt-F2, login as root, mc, and edit as you please without error dialogs to get in your way. After starting MC, goto /boot/grub. Highlight/select menu.lst. Press Shift-F3, then right-arrow, and append something like "-20121102" to indicate you're making a backup copy of what it was when you started to edit. Now move the highlight/select back to menu.lst and press F4. Make the changes you wish and save/exit. That's how simple it can be. Mcedit (F4) is an easy to use and intuitive editor. And, it works both in X and on ttys, which means you can use it to fix a broken X, and on a system that doesn't even have X, like a rescue boot. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 02-11-12 16:53, Felix Miata schreef:
On 2012-11-02 11:39 (GMT+0100) Oddball composed:
...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.
Please explain "searches and corrects" in some detail, and what you mean by "find the bootstraps". How does this selection differ in result from what happens when you try the others?
with the others i get the message about the wrongly interpreted fs Error 15, and than press any key to proceed, than the black 'dossy' screen appears to pick another option, you must have seen such screen before. The last entry comes to the same point, but moves on, no error message, looks around gives output about it, i might opt to step boot, to capture the exact message, but eventually comes to kdm, and the rest is init 5.
It does not matter what i change, it is always wrong.
Change using what and how to change? Are you logged in as regular user?
No, if i fire up yast to install or change whatever, i have to be root, and i would not want it any other way.
/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,
What was meant by the error message 'name already in use, pick another one'
http://www.kernel.org/doc/Documentation/kernel-parameters.txt explains what most mean. The placement of showopts determines how much of cmdline you can see to edit when the Grub menu is on the screen to boot.
but after many tries, the result was the same dialog box and the 'boing', so i assumed another bug, and i quit.
This is in the install bootloader section of yast.
At this point my feelings towards a fresh install grew bigger.
For editing menu.lst apparently you're trying to use the wrong tool. If there was a bug, others would have had the same problem a long time ago.
I always used kate for it, and believe me, i had to correct things many times during my alpha and beta tester days. -- 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
Op 02-11-12 17:10, Felix Miata schreef:
On 2012-11-02 11:39 (GMT+0100) Oddball composed:
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.
Now it's time to use it. Login as root on a tty, open mc, and go fix menu.lst....
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.
All the eeepcs I checked have 1024x600 or 1368x768 screens. Which is yours? 1024x600 and 1024x768. The latter is best.
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.)
If you are in X trying to do these system file modifications, then you're likely not root, and editing system files is problematic. Until you are able to get into X as root to start with, for menu.lst, device.map, fstab, bootloader and other system files, do Ctrl-Alt-F2, login as root, mc, and edit as you please without error dialogs to get in your way.
I ctrl+alt+F2 to the tty, and get root there. Than i open mc. But i can not edit the file there.
After starting MC, goto /boot/grub. Highlight/select menu.lst. Press Shift-F3, then right-arrow, and append something like "-20121102" to indicate you're making a backup copy of what it was when you started to edit. Now move the highlight/select back to menu.lst and press F4. Make the changes you wish and save/exit. That's how simple it can be. Mcedit (F4) is an easy to use and intuitive editor. And, it works both in X and on ttys, which means you can use it to fix a broken X, and on a system that doesn't even have X, like a rescue boot.
Hmmm, sounds not wrong. Only now this time i get no tty from F1-6, only a black screen no prompt. F7 brings me back into the desktop. -- 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
On 2012-11-02 16:56 (GMT+0100) Oddball composed:
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.
It is a too high number, and not in the list of available modes. i can 'scan' but it is difficult for me to know how fi 80x43 looks like
You probably don't want 80x43, but anything is better than just black.
before i see it, and this applies only for the text that is shown during boot, which is about 3 seconds?
I looked at http://en.wikipedia.org/wiki/Asus_Eee_PC to find that 1024x600 is the native resolution for a 901, so let's stick to that for now at least. You can change it after everything else seems to behave as expected/wanted. So, change the last stanza to read thus: title openSUSE default kernel with neither KDM nor resume root (hd0,2) kernel /vmlinuz showopts noresume video=1024x600 splash=verbose 3 initrd /initrd
Which model eee pc do you have? What screen resolution does it have?
I have a 901, and the resolutions are both. 1024x600 is ok, but best is 1024x768.
The kernel cmdline video option only applies outside of X. I find it hard to believe 1024x768 can be supported happily on a 1024x600 panel, if supported at all. If you can get X to do 1024x768, and you like it, good for you. But let's stick to 1024x600 during boot and see if you can keep away so much black screen. If you still see more black screen than you want before KDM appears, maybe you should try 'zypper rm plymouth splashy bootsplash'. I taboo all three when I install.
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 (?)
I have no idea where this is from. Exactly when do you see it? Is part of it something you see on your screen, and part your description of what you see? Please distinguish between what appears on screen and your added comments.
It appears on the black screen instead of booting, immediately after the bootloader choices screen.
But what exactly does it say (without your added comments)? If it's what I think, it doesn't matter. It's just a short comment from Grub that it's actually doing something. Just ignore it, or blink.
EXT2 is probably on your sda3 /boot partition, and EXT4 is probably on your LVM partitions. If you show us your fstab this might become clear.
No it is not. I remember that because i wondered why lvm choose ext4 for a /boot partition, i always use ext2 for that, because it nearest to fat16. And does not need journaling of a kind, as it is static, sometimes changed information.
EXT4 is a derivative of EXT2 that has journaling and other features. The partition table type for both is the same. I too always use EXT2 for /boot. I've never yet used EXT4, ever. All my /home and / partitions are EXT3 for backwards compatibility with old kernels, since most of my systems are multiboot and still have some very old distro versions installed.
/dev/system/swap swap swap defaults 0 0 /dev/system/root / ext4 acl,user_xattr 1 1 /dev/disk/by-id/ata-RunCore_64G-C_SSD_000901022255-part3 /boot ext4 acl,user_xattr 1 2 /dev/system/home /home ext4 acl,user_xattr 1 2 /dev/disk/by-id/ata-RunCore_64G-C_SSD_000901022255-part1 /windows/C ntfs-3g users,gid=users,fmask=133,dmask=022,locale=nl_NL.UTF-8 0 0 /dev/disk/by-id/usb-Single_Flash_Reader_058F63356336-0:0-part1 /windows/D vfat users,gid=users,umask=0002,utf8=true,nofail 0 0
Proof your native partitions are all either swap or EXT4. For a /boot partition, acl & user_xattr seem just as pointless as a journal. Next install be more careful if you really want EXT2 for /boot. ;-) -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Felix Miata -
Oddball