https://bugzilla.novell.com/show_bug.cgi?id=431703 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@novell.com AssignedTo|bnc-team-screening@forge.provo.novell.com |agruen@novell.com Priority|P5 - None |P2 - High -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c2 --- Comment #2 from Dave Plater 2008-10-02 15:15:42 MDT --- Is it not possible to put the post install scripts in a separate rpm? -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c4 --- Comment #4 from Dave Plater 2008-10-03 01:31:48 MDT --- I don't understand the mechanics of the satsolver or what determines the order of installation of the kernel packages but if this was determinable then the scripts would be the last to be 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c6 --- Comment #6 from Andreas Gruenbacher 2008-10-03 02:54:33 MDT --- This is not about the order in which the kernel packages get installed. We cannot create an initrd only in the -base package: even if we managed to get the package order "right" within a single transaction, the user would still be able to install kernel-$foo-base, kernel-$foo, kernel-$foo-extra from the command line, separately, in this order. (It could be that there is a way to play some really evil tricks with triggers, but I can't say that this idea really thrills me.) -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c8 --- Comment #8 from Dave Plater 2008-10-04 02:42:18 MDT --- I had a boot problem after upgrade to beta 2 and blamed it on grub but it seems that grub was not at fault. I'm not that familiar with grub, my system booted as far a the grub shell, would this indicate that my initrd was at fault? -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c10 --- Comment #10 from Dave Plater 2008-10-04 04:17:22 MDT --- (In reply to comment #9 from Andreas Gruenbacher)

That's impossible to tell without additional information such as the YAST logs of the update, or the error messages you got during boot.

Nothing was loaded all I had was the grub shell. I thought it was https://bugzilla.novell.com/show_bug.cgi?id=428127 and used 11.0 dvd rescue system to replace the files in /boot/grub with a backup then I could boot to grub boot menu which pointed at my old non existent kernel. I then used 11.0 dvd system repair expert install new bootloader to point to correct kernel vmlinuz-2.6.27-rc7-12-pae and initrd-2.6.27-rc7-12-pae. I create a symlink to /mnt/boot called boot, in ctrl/alt/F2 console, to enable me to browse to the correct kernel and initrd in the bootloader repair program. That means that initrd-2.6.27-rc7-12-pae was present prior to finishing the repair so it must have been created during install. Grub was also updated to grub-0.97-151.3, which is supposed to work, during my upgrade. I reopened the grub bug and then forced a reinstallation of grub-0.97-151.3 and the system still booted, now I am not sure what caused the boot failure. -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c12 --- Comment #12 from Dave Plater 2008-10-04 05:00:27 MDT --- Anything other steps I can take please ask. -- 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c14 Andreas Gruenbacher changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maxime.pierron@lippi.fr --- Comment #14 from Andreas Gruenbacher 2008-10-07 02:16:40 MDT --- *** Bug 432583 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=432583 -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c16 --- Comment #16 from Dave Plater 2008-10-07 03:28:53 MDT --- A clue might be when I execute kexec-bootloader I receive the message:- "Default boot section is no image." -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c18 --- Comment #18 from Dave Plater 2008-10-07 03:41:01 MDT --- output of mkinitrd:- Kernel image: /boot/vmlinuz-2.6.27-rc7-12-pae Initrd image: /boot/initrd-2.6.27-rc7-12-pae Root device: /dev/disk/by-id/ata-WDC_WD800JB-00JJC0_WD-WMAM9RA78067-part1 (/dev/sda1) (mounted on / as xfs) find: `/lib/modules/2.6.27-rc7-12-pae/kernel/drivers/s390': No such file or directory find: `/lib/modules/2.6.27-rc7-12-pae/kernel/drivers/s390': No such file or directory Kernel Modules: dock scsi_mod libata ata_piix xfs processor thermal fan edd ahci pata_rz1000 pata_pdc2027x pata_sis pdc_adma sata_mv sata_nv pata_sch sata_promise pata_sc1200 sata_qstor sata_sil pata_serverworks sata_sil24 sata_sis sata_svw sata_sx4 sata_uli sata_via sata_vsc pata_sil680 ata_generic pata_acpi pata_ali pata_amd pata_sl82c105 pata_artop pata_atiixp pata_cmd640 pata_cmd64x pata_cs5520 pata_cs5530 pata_cs5535 pata_cs5536 pata_cypress pata_efar pata_hpt366 pata_hpt37x pata_hpt3x2n pata_hpt3x3 pata_isapnp pata_it8213 pata_it821x pata_jmicron pata_legacy pata_marvell pata_mpiix pata_netcell pata_ninja32 pata_ns87410 pata_ns87415 pata_oldpiix pata_opti pata_optidma pcmcia_core pcmcia pata_pcmcia pata_pdc202xx_old pata_qdi pata_radisys pata_triflex pata_via pata_winbond sata_inic162x ide-core ide-disk cdrom ide-cd_mod ide-floppy ide-generic dtc2278 ht6560b ide-cs qd65xx umc8672 ali14xx ide-4drives ide_platform aec62xx alim15x3 amd74xx atiixp cmd64x cs5520 cs5530 cs5535 hpt366 ns87415 opti621 pdc202xx_new pdc202xx_old piix rz1000 serverworks siimage sis5513 trm290 via82cxxx cmd640 delkin_cb ide-pci-generic it8213 it821x jmicron sc1200 slc90e66 triflex ide-pnp ide-tape BusLogic crc-t10dif sd_mod sg sr_mod st 3w-9xxx 3w-xxxx aacraid scsi_transport_spi aic79xx aic7xxx scsi_transport_sas libsas aic94xx arcmsr atp870u ch dc395x scsi_dh scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac dmx3191d dpt_i2o eata scsi_tgt scsi_transport_fc libfc fcoe fdomain gdth hptiop ide-scsi parport imm ipr ips scsi_transport_iscsi libiscsi iscsi_tcp libsrp lpfc megaraid_mm megaraid_mbox megaraid_sas megaraid mvsas nsp32 osst aha152x_cs fdomain_cs nsp_cs qlogicfas408 qlogic_cs sym53c500_cs ppa qla1280 qla2xxx qla4xxx sym53c416 t128 raid_class scsi_debug in2000 initio pas16 scsi_transport_srp scsi_wait_scan enclosure ses stex sym53c8xx tmscsim NCR53c406a a100u2w advansys aha152x aha1542 aic7xxx_old dtc g_NCR5380 g_NCR5380_mmio qlogicfas u14-34f ultrastor wd7000 usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 39468 blocks Still no sections in yast2 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c20 Andreas Gruenbacher changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@novell.com --- Comment #20 from Andreas Gruenbacher 2008-10-07 04:11:51 MDT --- This sounds like a bad interaction between perl-Bootloader and the kernel-$flavor-base %post script. It may be that perl-Bootloader chokes when asked to add a bootloader entry even though the initrd doesn't exit yet at that point in time. Adding the perl-Bootloader maintainer as well ... One thing to try would be to downgrade to the old kernel, then upgrade to the new kernel by installing the new kernel-$flavor-base and kernel-$flavor packages while running the scripts by hand, like this: rpm -U --noscripts $foo.rpm rpm -qp --qf '%{postin}' $foo.rpm > post.sh bash -x post.sh > post-$foo.log 2>&1 this should show all the commands, messages, and errors. /boot/grub/menu.lst would be interesting in its state with the old kernel, with only the kernel-$flavor-base package installed, and with the kernel-$flavor package installed as well. -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c22 --- Comment #22 from Dave Plater 2008-10-07 04:24:55 MDT --- I did a kdiff on postin sripts from previous and present kernel-pae note not pae-base which fails anyway and after finding what I think might be the problem :- run_bootloader () { # Only create the bootloader entry when installing kernel-$flavor-base. if [ kernel-pae != kernel-pae-base ]; then return 1 fi This is in the new kernel-pae and would prevent bootloader from being updated. After running rpm -U --force -vv kernel-pae-base-2.6.27-12.1.i586.rpm Yast bootloader now shows sections therefore when I reboot it should work. I've attached the output of above command. -- 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c24 --- Comment #24 from Andreas Gruenbacher 2008-10-07 05:10:30 MDT --- It seems that kernel-pae-base doesn't add the bootloader entry because mkinitrd fails before that. Once that is fixed (even though kernel-pae-base won't be able to create the initrd), kernel-base won't have a reason to add the same bootloader entry a second time. That's what the check in run_bootloader was meant for. -- 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c26 Andreas Gruenbacher changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Errormessages when updating factory to Beta2 |Errormessages when updating factory to Beta2 |with root on reiserfs |with root on [non-ext3] --- Comment #26 from Andreas Gruenbacher 2008-10-07 07:22:37 MDT --- I think we have a reasonable solution to this problem now: we agreed that mkinitrd will use a different status code for reporting when required modules are missing (such as reiserfs or xfs). In that case, it also won't create an initrd, because that initrd wouldn't boot, anyway. In the various kernel's %post scripts I will check for this particular status code, and not error out. On top of that, the %post scripts will only add a bootloader entry when an initrd has been created (or the kernel has been compiled without modules, and doesn't need one). Other than now, the code adding the bootloader entry may get run repeatedly now; at most three times if an initrd could already be created with kernel-$flavor-base. -- 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c28 --- Comment #28 from Andreas Gruenbacher 2008-10-07 07:54:13 MDT --- Oh, before I forget ... only creating the bootloader entry if we have an initrd (or the kernel isn't modular in the first place) also means that we may end up without a bootloader entry if mkinitrd gets it wrong, but that's not so much different from trying to boot with a broken initrd. The one case I am unsure about is the installation order of kernel packages and KMPs: in case mkinitrd decides to depend on a module from a KMP, there is no guarantee that the KMP with that module will get installed before the kernel package(s). We *could* try to add bootloader entries out of KMP %post scripts, but that seems really ugly to me --- so maybe a package manager hack would be more acceptable? -- 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=431703 User dave.plater@yahoo.co.uk added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c30 --- Comment #30 from Dave Plater 2008-10-07 08:32:09 MDT --- Do you mean it is possible to upgrade base version without upgrading none and extra? When I force upgraded base only it didn't harm the system and the bootloader was fixed. -- 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=431703 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c32 --- Comment #32 from Josef Reidinger 2008-10-07 08:50:28 MDT --- (In reply to comment #31 from Andreas Gruenbacher)

...

Only problem is when you upgrade only one part...because it have same image and initrd name it remove it after first upgrade...so if you have base and extra and you update only base, then extra is removed from entry.

I don't understand: the kernel-$flavor-base, kernel-$flavor, and kernel-$flavor-extra packages are all for the same kernel, they all have the same package version and release number, and they all refer to the same /boot/vmlinu* and /boot/initrd file. The kernel-$flavor and kernel-$flavor-extra packages only contain additional modules.

yes, but if you call in post script remove some image and initrd it doesn't check if it exist only remove it. So if you upgrade base and old base is uninstalled if you call remove for post script it remove old entry even default and extra can still have old image. Or I bad understand it? -- 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=431703 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c34 --- Comment #34 from Josef Reidinger 2008-10-07 23:59:49 MDT --- (In reply to comment #33 from Dave Plater)

This is for the future, when upgrade will be up to three kernel packages? Then the last installed part of kernel packages will have to do postin script.

This must be done now, because in simplier case if you install base, normal and extra package and then remove extra, then extra cannot call post-uninstall script for bootloader (It looks like not this is done as during test after uninstall bootloader menu is correct). And one note which I find during testing. If you have installed base and normal package and want uninstall normal and let only base, it is not possible, because you are forced to install another kernel. -- 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=431703 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c36 --- Comment #36 from Josef Reidinger 2008-10-08 00:33:35 MDT --- Yes and this must not change. -- 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=431703 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c38 --- Comment #38 from Josef Reidinger 2008-10-08 01:26:39 MDT --- (In reply to comment #37 from Dave Plater)

Where are the split source rpms factory src repo only contains single kernel source rpms?

I think that it is in one rpm where modules depend only on spec file, where is specified more packages? -- 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c40 --- Comment #40 from Andreas Gruenbacher 2008-10-08 02:05:21 MDT ---

And one note which I find during testing. If you have installed base and normal package and want uninstall normal and let only base, it is not possible, because you are forced to install another kernel.

I don't understand -- what do you mean? -- 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=431703 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c42 --- Comment #42 from Josef Reidinger 2008-10-08 02:19:06 MDT --- (In reply to comment #41 from Josef Reidinger)

(In reply to comment #40 from Andreas Gruenbacher)

...

...

And one note which I find during testing. If you have installed base and normal package and want uninstall normal and let only base, it is not possible, because you are forced to install another kernel.

I don't understand -- what do you mean?

Try zypper in kernel-default. It also install base...but then you want only base, so you do zypper rm kernel-default and it force you to install another kernel. I test it with the newest zypper. Maybe I have only old one.

Sorry it is just old zypper, in beta2 this is allowed correctly. So you can reduce your kernel to only base. -- 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c44 --- Comment #44 from Andreas Gruenbacher 2008-10-08 02:39:38 MDT --- Look at the package dependencies: kernel-pae-extra requires kernel-pae, and kernel-pae requires kernel-pae-base. So it's completely normal that removing kernel-pae will also remove kernel-pae-extra. (Side note: we could technically make kernel-pae-extra require only kernel-pae-base, but I can't imagine that this would ever lead to a useful result.) -- 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=431703 User jreidinger@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c46 Josef Reidinger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmarsik@novell.com --- Comment #46 from Josef Reidinger 2008-10-09 02:59:25 MDT --- *** Bug 431631 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=431631 -- 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=431703 User agruen@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=431703#c48 --- Comment #48 from Andreas Gruenbacher 2008-10-21 05:20:28 MDT --- Thanks for confirming! -- 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.