[Bug 393030] New: kernel install/remove leaves broken system ...
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c392054 Summary: kernel install/remove leaves broken system ... Product: openSUSE 11.0 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Booting AssignedTo: jsrain@novell.com ReportedBy: mmeeks@novell.com QAContact: jsrain@novell.com Found By: --- Sooo ... perhaps this is a side-effect of #392054# / #389177# - however I have removed my /.buildenv and (I believe) can expect my machine to continue to work. So - to reproduce: I install the kernel-debug package: this results in a happy looking /boot - though (most strangely) - while I now have 3 kernels installed: kernel-default, kernel-debug and kernel-xen: I only have one mentioned (kernel-debug) in /boot/grub/menu.lst. Nevertheless - since kernel-debug doesn't boot (#393002#) I try to remove it: zypper rm kernel-debug it is removed; and (as if by magic) /boot has a broken initrd link, and grub/menu.lst is now completely devoid of useful content :-) Quite how this happens is rather a mystery: before I started trying to repeat this I had at least a 'failsafe' option in the grub menu. Now I still have 2 kernels installed and neither of them in my boot menu :-) I attach an strace of the zypper rm in case it helps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c1 --- Comment #1 from Michael Meeks <mmeeks@novell.com> 2008-05-21 04:16:11 MST --- Created an attachment (id=217190) --> (https://bugzilla.novell.com/attachment.cgi?id=217190) zipped zypper strace -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c2 --- Comment #2 from Michael Meeks <mmeeks@novell.com> 2008-05-21 04:18:57 MST --- after the breakage: $ rpm -qa | grep kernel kernel-default-2.6.25.4-2 linux-kernel-headers-2.6.25-6 kernel-xen-2.6.25.4-2 kernel-source-2.6.25.4-2 nfs-kernel-server-1.1.2-8 $ ls -l /boot total 37996 -rw-r--r-- 1 root root 1175292 May 17 21:14 System.map-2.6.25.4-2-default -rw-r--r-- 1 root root 1102220 May 17 21:22 System.map-2.6.25.4-2-xen -rw------- 1 root root 512 May 8 15:12 backup_mbr lrwxrwxrwx 1 root root 1 May 20 19:04 boot -> . drwxr-xr-x 5 root root 4096 May 16 11:48 boot-backup -rw-r--r-- 1 root root 83017 May 17 21:26 config-2.6.25.4-2-default -rw-r--r-- 1 root root 81838 May 17 21:26 config-2.6.25.4-2-xen drwxr-xr-x 2 root root 4096 May 21 11:03 grub lrwxrwxrwx 1 root root 23 May 21 11:02 initrd -> initrd-2.6.25.4-2-debug -rw-r--r-- 1 root root 5643033 May 20 21:10 initrd-2.6.25.4-2-default -rw-r--r-- 1 root root 5274636 May 20 21:10 initrd-2.6.25.4-2-xen lrwxrwxrwx 1 root root 21 May 20 19:48 initrd-xen -> initrd-2.6.25.4-2-xen drwx------ 2 root root 16384 May 8 15:07 lost+found -rw-r--r-- 1 root root 115828 May 18 00:44 memtest.bin -rw-r--r-- 1 root root 407552 May 20 19:10 message -rw-r--r-- 1 root root 392704 May 8 15:12 message.old -rw-r--r-- 1 root root 108292 May 17 21:31 symsets-2.6.25.4-2-default.tar.gz -rw-r--r-- 1 root root 107822 May 17 21:27 symsets-2.6.25.4-2-xen.tar.gz -rw-r--r-- 1 root root 441063 May 17 21:32 symtypes-2.6.25.4-2-default.gz -rw-r--r-- 1 root root 436839 May 17 21:27 symtypes-2.6.25.4-2-xen.gz -rw-r--r-- 1 root root 126697 May 17 21:29 symvers-2.6.25.4-2-default.gz -rw-r--r-- 1 root root 126049 May 17 21:27 symvers-2.6.25.4-2-xen.gz -rw-r--r-- 1 root root 2502846 May 17 21:25 vmlinux-2.6.25.4-2-default.gz -rw-r--r-- 1 root root 2334394 May 17 21:26 vmlinux-2.6.25.4-2-xen.gz lrwxrwxrwx 1 root root 24 May 21 11:02 vmlinuz -> vmlinuz-2.6.25.4-2-debug -rw-r--r-- 1 root root 2107448 May 17 21:15 vmlinuz-2.6.25.4-2-default -rw-r--r-- 1 root root 1949894 May 17 21:22 vmlinuz-2.6.25.4-2-xen lrwxrwxrwx 1 root root 22 May 20 19:48 vmlinuz-xen -> vmlinuz-2.6.25.4-2-xen -rw-r--r-- 1 root root 425915 May 18 02:17 xen-3.2.1_16881_01-11.gz lrwxrwxrwx 1 root root 24 May 20 18:56 xen-3.2.gz -> xen-3.2.1_16881_01-11.gz lrwxrwxrwx 1 root root 24 May 20 18:56 xen-3.gz -> xen-3.2.1_16881_01-11.gz -rw-r--r-- 1 root root 466711 May 18 02:15 xen-dbg-3.2.1_16881_01-11.gz lrwxrwxrwx 1 root root 28 May 20 18:56 xen-dbg-3.2.gz -> xen-dbg-3.2.1_16881_01-11.gz lrwxrwxrwx 1 root root 28 May 20 18:56 xen-dbg-3.gz -> xen-dbg-3.2.1_16881_01-11.gz lrwxrwxrwx 1 root root 28 May 20 18:56 xen-dbg.gz -> xen-dbg-3.2.1_16881_01-11.gz lrwxrwxrwx 1 root root 26 May 20 18:56 xen-syms -> xen-syms-3.2.1_16881_01-11 -rw-r--r-- 1 root root 6514449 May 18 02:17 xen-syms-3.2.1_16881_01-11 lrwxrwxrwx 1 root root 30 May 20 18:56 xen-syms-dbg -> xen-syms-dbg-3.2.1_16881_01-11 -rw-r--r-- 1 root root 6787785 May 18 02:15 xen-syms-dbg-3.2.1_16881_01-11 lrwxrwxrwx 1 root root 24 May 20 18:56 xen.gz -> xen-3.2.1_16881_01-11.gz $ cat /boot/grub/menu.lst # Modified by YaST2. Last modification on Wed May 21 11:03:33 BST 2008 default 0 timeout 8 gfxmenu (hd1,2)/message ###Don't change this comment - YaST2 identifier: Original name: Linux (/dev/sda3)### title Linux (/dev/sda3) rootnoverify (hd1,2) chainloader (hd0,2)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd1,2) chainloader (fd0)+1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c3 --- Comment #3 from Michael Meeks <mmeeks@novell.com> 2008-05-21 04:21:00 MST --- Created an attachment (id=217195) --> (https://bugzilla.novell.com/attachment.cgi?id=217195) y2logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c4 Michael Meeks <mmeeks@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Major --- Comment #4 from Michael Meeks <mmeeks@novell.com> 2008-05-21 04:33:55 MST --- mercifully force re-installing kernel-default made the system happy again ;-) fixed the initrd, and menu.lst: so perhaps this is 'kernel-[de]bug' specific ? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c5 Andreas Gruenbacher <agruen@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@novell.com |aosthof@novell.com --- Comment #5 from Andreas Gruenbacher <agruen@novell.com> 2008-05-22 03:16:19 MST --- Alex, could you please have a look at what's going on here with the interaction with perl-Bootloader? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User roland.kletzing@materna.de added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c6 roland kletzing <roland.kletzing@materna.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |roland.kletzing@materna.de --- Comment #6 from roland kletzing <roland.kletzing@materna.de> 2008-05-23 16:18:36 MDT --- it happened for the second time now: after updating to latest factory, everything needed for linux boot was removed from grub - i had kernel-default there, kernel-vanilla, kernel from kotd. now on boot i have "Windows" and "Diskette" to choose from. everything else has been deleted. do you want users to stay away from linux ? ;) looks like those kernel packages have been removed by factory update, and thus grub entries. now i have kernel-pae-2.6.25.4-2 and kernel-xen-2.6.25.4-2 going to reinstall kotd package now, as kernel-2.6.25.4-2 also has problems.... i`m not sure if this is my fault and i did oversee something during update.....but it`s strange. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User aosthof@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c7 --- Comment #7 from Alexander Osthof <aosthof@novell.com> 2008-05-27 08:54:34 MDT --- Alright, I think I've found the problem: Investigating the file perl-BL-standalone-log (included in attached YaST2 logs) one can see that following sections (which get misleadingly removed) are using symlinks for kernel and initrd instead of the full file names: --------------------------------------------------------------------------- 2008-05-13 17:36:51 MILESTONE: GRUB::Parselines: input from menu.lst : '# Modified by YaST2. Last modification on Thu May 8 15:12:16 BST 2008' ' default 0' ' timeout 8' ' gfxmenu (hd1,2)/message' ' ' ' ###Don't change this comment - YaST2 identifier: Original name: linux###' ' title openSUSE' ' root (hd1,2)' ' kernel /vmlinuz root=/dev/disk/by-id/scsi-SATA_Maxtor_6Y120P0_Y3NF4VFE-part5 resume=/dev/md0 splash=silent showopts vga=0x317' ' initrd /initrd' [snip] ' ###Don't change this comment - YaST2 identifier: Original name: failsafe###' ' title Failsafe -- openSUSE' ' root (hd1,2)' ' kernel /vmlinuz root=/dev/disk/by-id/scsi-SATA_Maxtor_6Y120P0_Y3NF4VFE-part5 showopts ide=nodma apm=off acpi=off noresume edd=off x1 1failsafe vga=0x317' ' initrd /initrd' --------------------------------------------------------------------------- After installing the kernel-debug package, those symlinks get adjusted to point to the kernel-debug files, thus "vmlinuz-2.6.25.3-2-debug" and "initrd-2.6.25.3-2-debug". Eventually, when the kernel-debug package gets removed afterwards, the above mentioned 2 sections are also matching because their symlinks get resolved, point to the same files and so get removed, too. So, the question is where those sections using symlinks stem from? I'm asking because after a fresh installation of openSUSE long names are used, so are they after an update using rpm or zypper. Concerning the additional and unwanted xen kernel - I don't have a clue. There's no dependency in perl-Bootloader which trigger xen kernels to get installed or removed. Maybe some zypper dependency? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c8 --- Comment #8 from Michael Meeks <mmeeks@novell.com> 2008-05-27 10:52:26 MDT --- The Xen kernel is wanted :-) I installed it: I had hoped it would show up in the boot menu (indeed it did before I started loosing entries having installed / removed the debug kernel). I've done a number of zypper dup's on this machine - for a long while - without a clean re-install - and it was initially installed from a Beta2 live-CD (AFAIR). Anyhow - great detective work :-) looking forward to a fix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User aosthof@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c9 Alexander Osthof <aosthof@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #9 from Alexander Osthof <aosthof@novell.com> 2008-05-29 06:27:13 MDT --- Sorry, but I have to disappoint you. In both cases of either a fresh installation or and "normal" kernel update long names of images (vmlinuz & initrd) will be entered in the menu.lst, e.g. "vmlinuz-2.6.22.17-0.1-default" or "initrd-2.6.22.17-0.1-default", to avoid above described confusions. Using symlinks for those file as in your case most likely stems from a manual intervention, thus there's nothing systematic I can do. Changing the symlinks (thus let them point to a new image) even happens in the post install/uninstall script of kernel packages, which I'm not responsible for. And I don't think this will be changed due to legacy issues IMHO. Closing bug RESOLVED INVALID. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c10 --- Comment #10 from Michael Meeks <mmeeks@novell.com> 2008-05-29 09:51:03 MDT --- Ah - as in, you think I went and symlinked files in /boot that is of course possible :-) clearly having had to repair the machine having had the kernel and boot auto-broken on upgrade - means I had to sod about on the console a fair bit. If so, apologies & glad it's not going to affect anyone else. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User roland.kletzing@materna.de added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c11 --- Comment #11 from roland kletzing <roland.kletzing@materna.de> 2008-05-29 11:37:24 MDT --- Alexander, thanks for looking at that. i'm not sure if this really is resolved. iirc, i never use symlinks. if is see an entry in grub pointing to a symlink, the first thing i`m doing is adjusting the entry to point to the full path. so my issue was different. will reopen or post another bug report if i have a proper repro-case... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User roland.kletzing@materna.de added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c12 --- Comment #12 from roland kletzing <roland.kletzing@materna.de> 2008-06-02 01:48:52 MDT --- i don`t have a repro-case, but i`d like to report that for the third time now i lost my linux-kernel boot entry in menu.lst. this happens when booting after factory upgrade - i can only choose between windows and failsafe and need to repair this manually now (boot cd). this really sucks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c13 Michael Meeks <mmeeks@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical Status|RESOLVED |REOPENED Resolution|INVALID | Summary|kernel install/remove leaves broken system ... |live-CD kernel install/remove leaves broken | |system ... Version|Beta 2 |RC 1 --- Comment #13 from Michael Meeks <mmeeks@novell.com> 2008-06-02 03:47:46 MDT ---
Sorry, but I have to disappoint you. In both cases of either a fresh installation or and "normal" kernel update long names of images (vmlinuz & initrd) will be entered in the menu.lst, e.g. "vmlinuz-2.6.22.17-0.1-default" or "initrd-2.6.22.17-0.1-default", to avoid above described confusions.
Re-opening & bumping priority - I just did a live-CD install of RC1; and my /boot/grub/menu.lst emphatically uses symlinks to initrd and vmlinuz: $ ls -l /boot total 12644 .. drwxr-xr-x 2 root root 4096 Jun 2 09:42 grub lrwxrwxrwx 1 root root 25 Jun 2 09:42 initrd -> initrd-2.6.25.4-8-default -rw-r--r-- 1 root root 5777149 Jun 2 09:42 initrd-2.6.25.4-8-default .. lrwxrwxrwx 1 root root 26 Jun 2 09:36 vmlinuz -> vmlinuz-2.6.25.4-8-default -rw-r--r-- 1 root root 2125760 May 27 01:47 vmlinuz-2.6.25.4-8-default $ cat grub/menu.lst # Modified by YaST2. Last modification on Mon Jun 2 09:42:30 BST 2008 default 0 timeout 8 gfxmenu (hd0,5)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.0 root (hd0,5) kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-SATA_WDC_WD800BB-75FWD-WCAJD1497090-part6 resume=/dev/sda5 splash=silent showopts vga=0x305 initrd /boot/initrd ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,5) chainloader (hd0,1)+1 ###Don't change this comment - YaST2 identifier: Original name: floppy### title Floppy rootnoverify (hd0,5) chainloader (fd0)+1 ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 11.0 root (hd0,5) kernel /boot/vmlinuz root=/dev/disk/by-id/scsi-SATA_WDC_WD800BB-75FWD-WCAJD1497090-part6 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x305 initrd /boot/initrd
Using symlinks for those file as in your case most likely stems from a manual intervention, thus there's nothing systematic I can do. Changing the symlinks (thus let them point to a new image) even happens in the post install/uninstall script of kernel packages, which I'm not responsible for. And I don't think this will be changed due to legacy issues IMHO.
Quite possibly this is a live-CD specific problem; re-opening & upping priority. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User mmeeks@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c14 --- Comment #14 from Michael Meeks <mmeeks@novell.com> 2008-06-02 03:52:59 MDT --- Created an attachment (id=219461) --> (https://bugzilla.novell.com/attachment.cgi?id=219461) console log With this system; zypper in -y kernel-default appears to result in (at least) a system that will boot [ albeit having dropped the non-debug kernel ]; however zypper rm kernel-debug unfortunately removes the debug kernel entries leaving no kernel ;-) [ and the broken initrd etc. symlinks ]. HTH. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 JP Rosevear <jpr@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c15 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|SHIP_STOPPER? |SHIP_STOPPER+ --- Comment #15 from Stephan Kulow <coolo@novell.com> 2008-06-02 23:39:41 MDT --- I'm heavily undecided about ship_stopper state. On one hand this is surely not what the average user will do - and !average users will be able to call yast2 bootloader to fix it. On the other hand this shows that update-bootloader still does not work as it should work, so there might be more to it than what the words say. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c16 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Critical |Blocker --- Comment #16 from Stephan Kulow <coolo@novell.com> 2008-06-03 03:36:08 MDT --- ok, I verified the bug is evil: zypper in kernel-pae -> I get pae entries twice in menu.lst (the default is gone) zypper rm kernel-pae -> no kernel left at all -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c17 --- Comment #17 from Stephan Kulow <coolo@novell.com> 2008-06-03 06:35:28 MDT --- I can not reproduce the "pae twice", but I can very well reproduce the second step ;( /usr/lib/bootloader/bootloader_entry remove pae 2.6.25.4-8-pae vmlinuz-2.6.25.4-8-pae initrd-2.6.25.4-8-pae -> no entries left. And this is what I get during the run of it: Bootloader::Tools::AdjustSectionNameAppendix(): Invalid parameters. 2008-06-03 12:20:08 MILESTONE: Tools::match_section: matching section name: Failsafe -- openSUSE 11.0 - 2.6.25.4-6 2008-06-03 12:20:08 MILESTONE: Tools::match_section: matching key: initrd 2008-06-03 12:20:08 MILESTONE: Tools::match_section: key: initrd, matched: /boot/initrd-2.6.25.4-6-default, with: /boot/initrd-2.6.25.4-8-pae, result: 2008-06-03 12:20:08 MILESTONE: Tools::match_section: end result: 2008-06-03 12:20:08 MILESTONE: Tools::RemoveSections: All available sections (after removal): the "result:" seems to be taken as 1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c18 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aosthof@novell.com |juhliarik@novell.com Status|REOPENED |NEW --- Comment #18 from Stephan Kulow <coolo@novell.com> 2008-06-03 07:47:21 MDT --- ok, #17 is invalid. The other sections were removed because there was no valid initrd entry. The real bug is that the live installer uses /vmlinuz and not the name. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c19 --- Comment #19 from Stephan Kulow <coolo@novell.com> 2008-06-03 16:34:16 MDT --- do I read the logs right, that it thought kernel-pae would have been the better kernel and is confused because still kernel-default was installed? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User jsrain@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c20 --- Comment #20 from Jiri Srain <jsrain@novell.com> 2008-06-04 02:38:06 MDT --- the installed kernel should not matter here; the recommendation is in fact used only during installation -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=393030 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=393030#c21 Jozef Uhliarik <juhliarik@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #21 from Jozef Uhliarik <juhliarik@novell.com> 2008-06-04 02:46:35 MDT --- problem with solving simlinks for kernel and initrd is fixed in yast2-bootloader version 2.16.18 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com