https://bugzilla.novell.com/show_bug.cgi?id=376310 User matt@genesi-usa.com added comment https://bugzilla.novell.com/show_bug.cgi?id=376310#c1 Matt Sealey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matt@genesi-usa.com --- Comment #1 from Matt Sealey 2008-04-03 08:01:00 MST --- This is not the whole story. It would also be preferable (but probably worth another bug) for kernel packages to automatically run mkzimage on kernel installation, otherwise security updates and updated kernels may not actually be deployed properly. -- 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=376310 User locilka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=376310#c2 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |juhliarik@novell.com --- Comment #2 from Lukas Ocilka 2008-04-04 05:17:53 MST --- Juhliarik, yours or Kernel-maintainers'? -- 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=376310 User aosthof@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=376310#c4 Alexander Osthof changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |pczanik@genesi-usa.com --- Comment #4 from Alexander Osthof 2008-04-16 00:15:45 MST --- Reading the output of the command executed in comment #3 tells that the produced output file is 2773200 bytes too large. Could it be that the partition where /boot is located is simply too small? -- 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=376310 User pczanik@genesi-usa.com added comment https://bugzilla.novell.com/show_bug.cgi?id=376310#c6 peter czanik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|pczanik@genesi-usa.com | --- Comment #6 from peter czanik 2008-04-21 05:25:43 MST --- The different PPC boards can be detected by hwinfo, this is already used in many situations by the installer (YaST) and lilo (the boot loader installer / configurator package on PPC, which mkzimage is part of). The output of 'mkzimage' boots fine on Pegasos and EFIKA machine, and as EFIKA has no and Pegasos only partial support for yaboot, 'mkzimage' is the preferred method. -- 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=376310 Stephan Kulow 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=376310 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|SHIP_STOPPER+ |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=376310 User matt@genesi-usa.com added comment https://bugzilla.novell.com/show_bug.cgi?id=376310#c9 --- Comment #9 from Matt Sealey 2008-10-22 10:02:36 MDT --- Hi Olaf, This isn't working in Factory, and never worked on 11.0. I am working on a bootloader solution (a modification of YaST2-bootloader possibly, plus some support utilities for a Forth boot menu) which should solve a bunch of stuff but it will not be ready for 11.1 and I doubt it would make it onto the CD for release anyway. I would really like to know what you actually patched to handle pegasos in the first place and where you modified YaST2-bootloader or LILO to support mkzimage (and how you detect Pegasos or Efika, since both of them can be detected in the same way by looking at /proc/device-tree/openprom/CODEGEN,vendor = "bplan" so the check should not even have had to be updated?) If anything I would like to patch it back out when I have finished my support tools, but it is also a good start on where to throw patches at to gain support for the new bootloader tools (the idea is to mimic "grub" as much as possible, so that mkzimage can be run, forth scripts can be generated from efika.forth, a custom menuing solution can be installed and updated). I have had a chat with Josef Uhliarik who agreed to at least help. I would much rather take on the burden and responsibility myself if possible so as not to waste time during the release process, however a couple questions remain; where is the canonical source for YaST2-bootloader and what did you modify to fix this patch? -- 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=376310 User matt@genesi-usa.com added comment https://bugzilla.novell.com/show_bug.cgi?id=376310#c11 --- Comment #11 from Matt Sealey 2008-11-26 13:13:51 MST --- Created an attachment (id=255953) --> (https://bugzilla.novell.com/attachment.cgi?id=255953) Boot Menu Forth Script -- 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=376310 User matt@genesi-usa.com added comment https://bugzilla.novell.com/show_bug.cgi?id=376310#c13 --- Comment #13 from Matt Sealey 2008-11-27 09:37:57 MST --- Can I make a case for fixing mkzimage so that it treats Efika properly? pmac is so wrong I don't know what to say.. this is causing mkzimage to require an extra argument when it kind of shouldn't (it is a kernel mishap that /proc/cpuinfo doesn't mention CHRP) We would really like some code somewhere that automates bootloader stuff for Efika and Pegasos. I've been hammering away at something but the organization of yast2-bootloader and perl-bootloader are really disgusting.. some of the nastiest perl I have ever read. While the concept is sound (treat every bootloader as LILO) it takes so long to even find the part of the code that could even support the "ppc" bootloader (which I still did not find). Is there a hint as to the code that parses out lilo.conf and generates bootloaders (for instance prep partitions, yaboot configuration etc.) so I can try and submit a patch for efika/pegasos to maintain this method? -- 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=376310 User matt@genesi-usa.com added comment https://bugzilla.novell.com/show_bug.cgi?id=376310#c14 --- Comment #14 from Matt Sealey 2009-01-02 12:39:08 MST --- I'm still beating my head on the desk over this. yast2-bootloader has ample code to support iSeries and PREP with mkzimage, and it's well known that yaboot simply doesn't work on most configurations (here it installed /yaboot file but it's in the root directory, not /boot, and the firmware may not be able to read the root directory which is why /boot exists in the first place). Running yaboot from the disk on my Pegasos does not successfully boot, and it's running a 1.2 firmware (i.e. production) and ext3 (with 128 byte inode) partitions throughout (I accepted the default partitioning proposal in 11.1) Can't we just treat Efika/Pegasos or any Genesi/bplan machine exactly the same?- let's remove the dependencies on specific board names, let's assume yaboot needs mkzimage to be run like yast2-bootloader for PREP and iSeries does, and that all Genesi systems will ship with "broken" firmware and everyone would prefer just to boot the zImage directly)? yast2-bootloader and /lib/lilo/ etc. scripts all detect Efika and Pegasos just fine.. just some wrong decision has been made about what these boards SHOULD run. This is just not the reality, though, and no amount of breaking Linux distributions to try and "coerce" firmware teams into releasing updates should be done, as it annoys users and causes systems to be unbootable even after installation. All this running around working out workarounds and driver updates to resolve issues with a 3 year old decision to force people to try and use yaboot when it would clean up and code fix a lot of problems by simply not supporting it.. it simply makes me want to cry with frustration that nobody can see the real issue here, which is that trying to imply that yaboot is the standard bootloader is both 1) not born out by the code in the ppc bootloader support since it can support mkzimage just fine and 2) never going to work this way anyway -- 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=376310 Alexander Osthof 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.