I decided to create one bug for both grub patches and gfxboot because lots of testers commented that it's too hard to get all necessary things from bugs #79230 and #85779. Here are installations instructions: 1. download grub and gfxboot ebuilds and put them into your overlay (grub should go to sys-boot and gfxboot to media-gfx). 2. download patchset and put it into yout distfiles. 3. create digests 4. unmerge old grub and remove all *stage* files from /usr/lib/grub and /boot 5. emerge new grub and install it as usually 6. emerge gfxboot 7. download gentoo-krystal-gfxboot theme, unpack it and make 8. copy boot/message to /boot/grub/gentoo-krystal.gfxmenu 9. add something like `gfxmenu (hd0,0)/grub/gentoo-krystal.gfxboot` into your grub.conf 10. if you'd like to use wildcards - read grub's info pages and take a look at my grub.conf below timeout 5 default 0 gfxmenu (hd0,0)/grub/gentoo-krystal.gfxboot title * root (hd0,2) wildcard (hd0,0)/vmlinuz-* kernel (hd0,0)/vmlinuz-* root=/dev/hda3 video=radeonfb:1280x1024-32@85 splash=silent,theme:livecd-2005.1 quiet CONSOLE=/dev/tty1 initrd (hd0,0)/splash-livecd-2005.1-1280x1024 Seems, that's all.
Created attachment 66496 [details] grub-0.97 ebuild
Created attachment 66498 [details] grub-0.97 ext patchset
Created attachment 66499 [details] gfxboot-3.0.15-r1 ebuild
Created attachment 66500 [details, diff] gfxboot-3.0.15-r1 patch
Created attachment 66501 [details] gentoo-krystal-gfxboot-0.1 theme
*** Bug 85779 has been marked as a duplicate of this bug. ***
*** Bug 79230 has been marked as a duplicate of this bug. ***
Created attachment 85470 [details] gfxboot ebuild with amd64 This one contains a slightly modified ebuild for use with amd64 computers. It works for me :)
not really interested in updating 0.9x anymore
Created attachment 105831 [details] gfxboot-3.3.18.ebuild ebuild for gfxboot 3.3.18.10 probably you'll need to change version in src uri for download file
Created attachment 105833 [details] gfxboot-3.3.18.patch put it to files directory in gfxboot overlay
Created attachment 105835 [details] grub-0.97-r3.ebuild patched grub ebuild based on official 0.97-r3. no new patches from last version
Created attachment 105839 [details] grub-0.97-patches-1.4-ext.tar.bz2 new patchset for new grub. put it ti distfiles
Comment on attachment 105839 [details] grub-0.97-patches-1.4-ext.tar.bz2 new patchset for new grub. put it to distfiles.
probably you will cant to compile gentoo theme from wiki. size of default suse theme from rpm package too large (>300kb) when will need about 170kb as somebody say on one ubuntu forum. you can google other themes or create yours
Me and some other people get this error when compiling any theme: Including "keymap.sv.inc" Including "locale.inc" Undefined words: bootloader, blend2, usernote, biosmem, getinfo, fade, fadein, bootdrive, findmode, getvideomode, updatedisk make: *** [bootdir] Error 10 Does anyone know how to solve it, please?
(In reply to comment #16) > Does anyone know how to solve it, please? > i had the same error when compiled old themes. just try themes from gfxboot rpm package for test. i guess problem in compatibility but don't know where exactly.
(In reply to comment #17) You were right. Themes from the src.rpm compile fine. The error occures even when compiling gentoo-krystal-gfxboot-0.1.theme which probably means that this theme is obsolete.
Created attachment 114899 [details] gfxboot-3.3.24.3.ebuild ebuild was totally rewritten now you can emerge with use flags: themes doc with themes flag will be installed some useless staff but it help you to understand how to make themes dont forget to download bininstall.patch also and put it files dir
Created attachment 114900 [details, diff] bininstall.patch replace installation from /usr/sbin to /usr/bin
Created attachment 116494 [details] gfxboot_overlay.tar.bz2 full overlay with new updated patch for gfxboot in grub now you can use big message files :-) i take one with size > 300kB and it works! also download grub-0.97-patches-1.5-ext.tar.bz2
Created attachment 116496 [details] grub-0.97-patches-1.5-ext.tar.bz2 updated patchset
Created attachment 123599 [details] gfxboot_overlay.tar.bz2 LINGUAS settings new ebuild for gfxboot removes useless staff in accordance with linguas variable from /etc/make.conf
IMHO it would be great have gfxboot in portage (even better with a use flag directly in the grub ebuild). Why resolved with WONTFIX?
Okay, one of the problems is the changing versions of gfxboot rpm's. I have uploaded the current Suse stable one and created an ebuild and theme for it. here is the source rpm download location http://filebin.ca/jezrxz/gfxboot-3.3.38-2.src.rpm
Created attachment 143727 [details] updated gfxboot ebuild Here is the updated ebuild to use with the above Suse source rpm. After downloading and adding the gfxboot overlay to your local overlays, delete the older gfxboot ebuild and manifest and replace with my versions.
Created attachment 143729 [details] manifest for updated ebuild Here is the new manifest
Created attachment 143733 [details] New working Gentoo gfxboot theme This theme was created based on this theme that just didn't work. http://www.kde-look.org/content/show.php/gentoo+black+gfxboot?content=74695 Its been modified slightly to make it work with the new suse gfxboot file format. The gray message box has been removed and the gentoo icon has been moved up and to the right but its basically the same. Enjoy
Created attachment 143736 [details] Gfxboot theme based on livecd 2007 verbose splash theme Just to give people some options here is a second theme based on the livecd 2007 gentoo theme
I did this whole thing on a second box in about 15 minutes. I just wanted to update the directions so that no one gets confused. 1- Download gfxboot_overlay.tar.bz2 from above. Extract the file and add the entire folder as a local overlay to your system. If you put the file in /usr/local/portage/gfxboot_overlay as I did on my system, in your make.conf, add /usr/local/portage/gfxboot_overlay to this line like this PORTDIR_OVERLAY="/usr/local/portage/gfxboot_overlay" . Afterwards delete the gfxboot ebuild and manifest in the media gfx folder and replace with gfxboot-3.3.38.2.ebuild and Manifest from the above attachments. 2- Download these two files and place in /usr/portage/distfiles grub-0.97-patches-1.5-ext.tar.bz2 --from above attachments http://filebin.ca/jezrxz/gfxboot-3.3.38-2.src.rpm --source rpm from online filebin 3- Place these lines in your /etc/portage files (also place keyword files if you are running a stable system) in package.mask sys-boot/grub in package.unmask =sys-boot/grub-0.97-r3 4- emerge grub gfxboot 5- reinstall grub by doing grub-install /dev/hda ********BE SURE TO REPLACE /dev/hda WITH THE LOCATION OF YOUR GRUB CURRENTLY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 6- Download the above files message and message.livecd2007 and place them in /boot 7- Adjust your /boot/grub/menu.1st like this #splashimage=(hd2,1)/boot/grub/splash.xpm.gz gfxmenu (hd2,1)/boot/message or like this for the livecd2007 theme #splashimage=(hd2,1)/boot/grub/splash.xpm.gz gfxmenu (hd2,1)/boot/message.livecd2007 YOU'RE DONE!!!!!!!!!!!!!!!
BTW, don't use the themes use flag, the package wont emerge nor if it did would the themes work.
Created attachment 143815 [details] Gfxboot overlay (updated) and themes I have updated the ebuilds and you no longer have to download separate files and place them in dfferent places. Simply download gfxboot attachment and it contains the updated overlay (with a profiles folder) and also the themes to place in /boot. After adding the overlay to your system, emerge grub gfxboot (ebuilds will grab all necessary files), reinstall grub to it's previous location, move the 2 themes to /boot, and modify your menu.1st to use the them of your choice. It's a real shame we can't get this included in the main portage tree. I am going to ask the desktop effects maintainer if they wish to include the ebuilds in their overlay.
Can you please change your attachments to application/x-tar-bz2.. Thnx!
Have done some work on the themes. 6 new or updated themes now available at http://filebin.ca/hazdex/gfx-themes.tar.bz2
Created attachment 145038 [details] Updated Overlay and themes
(In reply to comment #35) > Created an attachment (id=145038) [edit] > Updated Overlay and themes > could you post the files as tgz and not as txt/plain text?! thanks
Created attachment 149872 [details] gfxboot-4.0.2 newest version nice ebuild
Created attachment 149873 [details, diff] newest grub_legacy patch from suse
Created attachment 149875 [details] newest grub_legacy (0.97-r5) with gfxboot use flag
Created attachment 149876 [details] cvs grub ebuild grub devs claimed native gfxboot support * fixed version, better detection and compatibility with gentoo * debug support * html docs support (needs 32bit static liblzo on amd64 systems)
Created attachment 149877 [details] lzo-2.02-r1.ebuild with fix for grub support on amd64
before testing on real systems try in vm or with "usermod -a disk <user> qemu -boot c -hda /dev/<your real HDD>"
great job, Sergey! can you create overlay and for example put it to code.google.com? btw, grub-0.97-gfxmenu-v8.patch is not newest one but last if v8 is version and yet, too many files already in this bug tracker. so i think overlay is necessery. i'll be glad to help you with it :-)
(In reply to comment #43) > great job, Sergey! > can you create overlay and for example put it to code.google.com? thanks. i have ftp server with my ebuilds on ftp://dfx.homeftp.net/services/GENTOO/v-fox , but connection is poor so it's temporary. as for overlay, i really like to but don't know if i be able maintain it well for nearest future. > btw, grub-0.97-gfxmenu-v8.patch is not newest one but last if v8 is version > and yet, too many files already in this bug tracker. so i think overlay is > necessery. i'll be glad to help you with it :-) > don't know what "v8" stands for but patches with same name from 3.3.38 and 4.0.2 really differs. however, this whole thing is still buggy and not tested well with gentoo-patchset therefore someone and somewhere should test and fix that. so overlay really is a way to go. maybe we should discuss that somewhere like freenode #gfxboot in spare time ?
(In reply to comment #39) > Created an attachment (id=149875) [edit] > newest grub_legacy (0.97-r5) with gfxboot use flag > Now this ebuild is not working. can't find grub-0.97-suse-patchset.tar.bz2 anybody fix it?
Created attachment 155119 [details] newest grub_legacy (0.97-r5) with gfxboot use flag
Created attachment 155121 [details] gfxboot-4.0.14-r2
Created attachment 155123 [details] gfxboot-3.3.38
Created attachment 155125 [details] cvs grub ebuild * updated [!] this compiles fine,i can boot grub after installing it on my hard drive but damn thing doesn't want to boot any OS or even use config file or loaded\build-in features [!] something must be made with 'special generated unicode font' (look at some grub gfxmenu manuals) and 'config-updating script' (look at debian stuff and /etc/grub.d/)
(In reply to comment #46) > Created an attachment (id=155119) [edit] > newest grub_legacy (0.97-r5) with gfxboot use flag > I can't emerge with newest ebuild when i use gfxboot flag get some error * Messages for package sys-boot/grub-0.97-r5: * Failed Patch: grub-0.97-gfxmenu-v8.patch ! * ( /usr/local/portage/gfxboot_overlay/sys-boot/grub/files/grub-0.97-gfxmenu-v8.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-boot/grub-0.97-r5/temp/grub-0.97-gfxmenu-v8.patch-25390.out * * ERROR: sys-boot/grub-0.97-r5 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2986: Called epatch 'src_unpack' * environment, line 1676: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: grub-0.97-gfxmenu-v8.patch! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-boot/grub-0.97-r5/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-boot/grub-0.97-r5/temp/environment'. * This ebuild is from an overlay: '/usr/local/portage/gfxboot_overlay/'
> * Include in your bugreport the contents of: >/var/tmp/portage/sys-boot/grub-0.97-r5/temp/grub-0.97-gfxmenu-v8.patch-25390.out part didn't told you about anything ? and you absolutely sure you were using grub-0.97-gfxmenu-v8.patch provided by me ? [!] grub 0.97-r5 with gentoo patchset and gfxmenu patch is NOT launching gfxboot menu with error "not enough memory" (some buffer is insufficient) and falling back on whatever you specified in config. help required
(In reply to comment #51) > > * Include in your bugreport the contents of: > >/var/tmp/portage/sys-boot/grub-0.97-r5/temp/grub-0.97-gfxmenu-v8.patch-25390.out > part didn't told you about anything ? > > and you absolutely sure you were using grub-0.97-gfxmenu-v8.patch provided by > me ? > > [!] grub 0.97-r5 with gentoo patchset and gfxmenu patch is NOT launching > gfxboot menu with error "not enough memory" (some buffer is insufficient) and > falling back on whatever you specified in config. help required > yeah i using your v8 patch. Anything else in this place? :) this is my grub-0.97-gfxmenu-v8.patch-25390.out ***** grub-0.97-gfxmenu-v8.patch ***** ====================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/sys-boot/grub/files/grub-0.97-gfxmenu-v8.patch ====================================== patching file docs/grub.texi patching file grub/asmstub.c Hunk #1 succeeded at 480 (offset -18 lines). patching file stage2/asm.S Hunk #1 succeeded at 1610 (offset -4 lines). patching file stage2/builtins.c Hunk #2 FAILED at 1353. Hunk #3 succeeded at 4845 (offset -51 lines). 1 out of 3 hunks FAILED -- saving rejects to file stage2/builtins.c.rej patching file stage2/shared.h patching file stage2/stage2.c Hunk #4 succeeded at 1554 (offset -3 lines). patching file stage2/stage2.c Hunk #1 succeeded at 827 with fuzz 2 (offset -372 lines). ====================================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/sys-boot/grub/files/grub-0.97-gfxmenu-v8.patch ====================================== can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- docs/grub.texi |+++ docs/grub.texi -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 29 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- grub/asmstub.c |+++ grub/asmstub.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 64 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/asm.S |+++ stage2/asm.S -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored can't find file to patch at input line 353 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/builtins.c |+++ stage2/builtins.c -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored can't find file to patch at input line 399 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/shared.h |+++ stage2/shared.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 463 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/stage2.c |+++ stage2/stage2.c -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored can't find file to patch at input line 997 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/stage2.c |+++ stage2/stage2.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ====================================== PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/sys-boot/grub/files/grub-0.97-gfxmenu-v8.patch ====================================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- docs/grub.texi |+++ docs/grub.texi -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored missing header for unified diff at line 29 of patch can't find file to patch at input line 29 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- grub/asmstub.c |+++ grub/asmstub.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 64 of patch can't find file to patch at input line 64 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/asm.S |+++ stage2/asm.S -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 353 of patch can't find file to patch at input line 353 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/builtins.c |+++ stage2/builtins.c -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored missing header for unified diff at line 399 of patch can't find file to patch at input line 399 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/shared.h |+++ stage2/shared.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored missing header for unified diff at line 463 of patch can't find file to patch at input line 463 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/stage2.c |+++ stage2/stage2.c -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored missing header for unified diff at line 997 of patch can't find file to patch at input line 997 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/stage2.c |+++ stage2/stage2.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ====================================== PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/sys-boot/grub/files/grub-0.97-gfxmenu-v8.patch ====================================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- docs/grub.texi |+++ docs/grub.texi -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored missing header for unified diff at line 29 of patch can't find file to patch at input line 29 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- grub/asmstub.c |+++ grub/asmstub.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 64 of patch can't find file to patch at input line 64 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/asm.S |+++ stage2/asm.S -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 353 of patch can't find file to patch at input line 353 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/builtins.c |+++ stage2/builtins.c -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored missing header for unified diff at line 399 of patch can't find file to patch at input line 399 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/shared.h |+++ stage2/shared.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored missing header for unified diff at line 463 of patch can't find file to patch at input line 463 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/stage2.c |+++ stage2/stage2.c -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored missing header for unified diff at line 997 of patch can't find file to patch at input line 997 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/stage2.c |+++ stage2/stage2.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ====================================== PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/sys-boot/grub/files/grub-0.97-gfxmenu-v8.patch ====================================== missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- docs/grub.texi |+++ docs/grub.texi -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored missing header for unified diff at line 29 of patch can't find file to patch at input line 29 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- grub/asmstub.c |+++ grub/asmstub.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 64 of patch can't find file to patch at input line 64 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/asm.S |+++ stage2/asm.S -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored missing header for unified diff at line 353 of patch can't find file to patch at input line 353 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/builtins.c |+++ stage2/builtins.c -------------------------- No file to patch. Skipping patch. 3 out of 3 hunks ignored missing header for unified diff at line 399 of patch can't find file to patch at input line 399 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/shared.h |+++ stage2/shared.h -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored missing header for unified diff at line 463 of patch can't find file to patch at input line 463 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/stage2.c |+++ stage2/stage2.c -------------------------- No file to patch. Skipping patch. 4 out of 4 hunks ignored missing header for unified diff at line 997 of patch can't find file to patch at input line 997 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- stage2/stage2.c |+++ stage2/stage2.c -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored I think some source code can't find and patch it
>yeah i using your v8 patch. it's not my,actually. it's just updated (yeh, who knows what "v8" stands for) >I think some source code can't find and patch it maybe your grub tarball is damaged,etc ? maybe something outdated and acting crazy ? i really can't imagine what's wrong. PS: please, attach big stuff like this :)
Created attachment 155585 [details] grub-0.97-r6 working pack all necessary patches has been added at last. so, it's alive and kicking now. requesting to reclose this bug with FIXED
Thank you Serey. Now your newest ebuild working perfectly! :)
you are welcome ;) but it's not me, actually, and i'm not quite a "Serey". all thanks to Rion this time. he managed to find missing patches.
I tried to install latest gfxboot (4.0.14-13): * Messages for package media-gfx/gfxboot-4.0.14.13: * Failed Patch: bininstall.patch ! * ( /usr/local/portage/gfxboot_overlay/media-gfx/gfxboot/files/bininstall.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/media-gfx/gfxboot-4.0.14.13/temp/bininstall.patch-5512.out Contents from bininstall.patch-5512.out: ***** bininstall.patch ***** ============================ PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/media-gfx/gfxboot/files/bininstall.patch ============================ patching file Makefile Hunk #1 FAILED at 40. 1 out of 1 hunk FAILED -- saving rejects to file Makefile.rej ============================ PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/media-gfx/gfxboot/files/bininstall.patch ============================ missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2006-09-14 16:02:58.000000000 +0600 |+++ Makefile 2007-03-28 19:10:21.000000000 +0600 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ============================ PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/media-gfx/gfxboot/files/bininstall.patch ============================ missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2006-09-14 16:02:58.000000000 +0600 |+++ Makefile 2007-03-28 19:10:21.000000000 +0600 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ============================ PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/media-gfx/gfxboot/files/bininstall.patch ============================ missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2006-09-14 16:02:58.000000000 +0600 |+++ Makefile 2007-03-28 19:10:21.000000000 +0600 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored ============================ PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/local/portage/gfxboot_overlay/media-gfx/gfxboot/files/bininstall.patch ============================ missing header for unified diff at line 3 of patch can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- Makefile.old 2006-09-14 16:02:58.000000000 +0600 |+++ Makefile 2007-03-28 19:10:21.000000000 +0600 -------------------------- No file to patch. Skipping patch. 1 out of 1 hunk ignored I can't manage to install any of the gfxboot versions :-(
Created attachment 161340 [details] gfxboot-4.0.14-r4 from openSuSe 11 release What patch ? this is not using any patches. [!] if you using grub2 you should add RESTRICT="strip" in ebuild otherwise it's not working at all
(In reply to comment #58) > What patch ? this is not using any patches. Er, in #54 you posted an ebuild with patches, how is this not using any patches? Are those patches needed now or not anymore? It's not obvious how to get this to work at all right now.
(In reply to comment #59) > Er, in #54 you posted an ebuild with patches, how is this not using any > patches? Are those patches needed now or not anymore? It's not obvious how to > get this to work at all right now. > if you see closely - #57 is about gfxboot which is not using any patches.
(In reply to comment #60) > (In reply to comment #59) > > Er, in #54 you posted an ebuild with patches, how is this not using any > > patches? Are those patches needed now or not anymore? It's not obvious how to > > get this to work at all right now. > > > > if you see closely - #57 is about gfxboot which is not using any patches. Ah, OK. Had problems getting this to work because the theme I was trying didn't work: http://www.kde-look.org/content/show.php/Gentoo-blue+GRUB+gfx-theme+1280x1024?content=69522 Is 1280x1024 not possible at all anymore? Also, some sources of themes can't be compiled because "help2txt" is missing?
Created attachment 176420 [details] grub-0.97-r8.ebuild Here's grub-0.97-r8.ebuild with gfxboot patches but also the patch for ext4 support from bug 250829 (copy http://bugs.gentoo.org/attachment.cgi?id=176097 to sys-boot/grub/files/grub-0.97-ext4extents.patch).
Created attachment 176422 [details, diff] grub-0.97-r8.ebuild.patch Or, if you prefer an ebuild patch, here's the patch for patching the portage version of grub-0.97-r8.ebuild to get gfxboot and ext4.
hi, is there an patched ebuild for grub-static? I'm using amd64 no-multilib, and grub is masked there. thx
I ask again (sb asked it already with no response): why won't fix?
(In reply to comment #65) > I ask again (sb asked it already with no response): why won't fix? > because gentoo devels dont like graphics in boot loader.
(In reply to comment #66) > (In reply to comment #65) > > I ask again (sb asked it already with no response): why won't fix? > > > > because gentoo devels dont like graphics in boot loader. > I doubt it, there *must* be a good reason I think, in other case it would conflict with gentoo philosophy (from gentoo.org main website: [...]Gentoo is a community—there is no "me" and "them", there is only "we,"[...])
a statement clearly made by someone who doesnt track grub, otherwise you'd know that the existing splash screen code is a patch Gentoo carries and not part of grub upstream. gfxboot is a large chunk of changes that no one has accepted, and no one has time to review. and the resulting "value add" is negligible considering the huge risk trade-off. we spend time on grub patches that fix existing bugs or adds support for necessary things: new file systems or disk storage.
(In reply to comment #68) > a statement clearly made by someone who doesnt track grub, otherwise you'd know > that the existing splash screen code is a patch Gentoo carries and not part of > grub upstream. > > gfxboot is a large chunk of changes that no one has accepted, and no one has > time to review. and the resulting "value add" is negligible considering the > huge risk trade-off. we spend time on grub patches that fix existing bugs or > adds support for necessary things: new file systems or disk storage. Would it be acceptable to introduce a USE flag for gfxboot in grub and print a big, fat warning if the user enables the USE flag?
problem is that if it's in the ebuild, people are going to file bugs and expect things to get fixed. that is quite a feat considering gfxboot code size and grub priorities. i could add /etc/portage/patches/ support to grub so you guys can just save the patch in /etc/portage/patches/sys-boot/grub-0.97/ and have it auto applied when you update ...
Well, I'm perfectly fine with how this currently are. I'm just mentioning this since people can't really comprehend why openSUSE can have this pretty Grub menu while Gentoo can not :P
because people at novell are paid to do it :p if you paid me the same i'd work on it ;)
(In reply to comment #72) > because people at novell are paid to do it :p > > if you paid me the same i'd work on it ;) I understand. But being open source has the benefit that you can simply grab their work to make your favorite toy just as good :P
hm what if somebody will help support gfxboot in official tree?
Created attachment 182144 [details] Updated Overlay and themes to grub-0.97-r9 I have updated to overlay and theme pack, here are the install instructions 1- Download gfxboot.tar.bz2 from above. Extract the file and add the entire folder as a local overlay to your system. If you put the file in /usr/local/portage/gfxboot_overlay as I did on my system, in your make.conf, add /usr/local/portage/gfxboot_overlay to this line like this PORTDIR_OVERLAY="/usr/local/portage/gfxboot_overlay" 2- Download gfxboot-extras.tar.bz2 from http://filebin.ca/wrbkqv/gfxboot-extras.tar.bz2 Place gfxboot rpm in /usr/portage/distfiles Place gfx-themes folder in /boot 3- Place these lines in your /etc/portage files (also place keyword files if you are running a stable system) in package.mask sys-boot/grub in package.unmask =sys-boot/grub-0.97-r9 in package.use media-gfx/gfxboot themes doc animate speech beep 4- emerge grub gfxboot 5- reinstall grub by doing grub-install /dev/hda ********BE SURE TO REPLACE /dev/hda WITH THE LOCATION OF YOUR GRUB CURRENTLY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 6- Adjust your /boot/grub/menu.1st like this for natural-gentoo theme #splashimage=(hd2,1)/boot/grub/splash.xpm.gz gfxmenu (hd2,1)/boot/gfx-themes/message.natural-gentoo or like this for the livecd2007 theme #splashimage=(hd2,1)/boot/grub/splash.xpm.gz gfxmenu (hd2,1)/boot/gfx-themes/message.livecd-2007.0-silent YOU'RE DONE!!!!!!!!!!!!!!!
There is a problem with the themes download. The downloaded file will not extract. I have uploaded it to a different service. It can be found at http://omploader.org/vMTk2Yw
Created attachment 182153 [details] Updated Overlay and themes to grub-0.97-r9 This is the corrected version with working download locations in instructions. Complete install instructions are included in download. Basically the grub-0.97-r9 ebuild from the official portage tree with just the gfx patches modification. The download link in instructions http://omploader.org/vMTk2Yw has all themes I have created on kde-look.org previously and also the gfxboot rpm so that if Suse updates the rpm and the download location from the ebuild ends up changing, you still have the needed file.
Hello Billy. Wouldn't it be easier to create an overlay on gitorious.org and possibly submit it to the layman list? Much easier than doing the updates here on bugzilla.
(In reply to comment #78) > Hello Billy. > > Wouldn't it be easier to create an overlay on gitorious.org and possibly submit > it to the layman list? Much easier than doing the updates here on bugzilla. > layman -a rion
Please someone could make grub-static package/ebuild?
There was an update to gfxboot-4.1.39.1.1.1 in rion overlay, but it doesn't build: make -C help-install make[3]: Entering directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/themes/upstream/help-install' ../../../gfxboot --help-create en.hlp --define product='Linux' fkey_help=F1 fkey_lang=F2 fkey_video=F3 fkey_inst=F4 fkey_dud=F6 --navi en/navi.html en/main*.html || true Can't locate HTML/Parser.pm in @INC (@INC contains: /etc/perl /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.8.8 /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi /usr/lib64/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib64/perl5/5.8.8 /usr/local/lib/site_perl .) at ../../../gfxboot line 424. BEGIN failed--compilation aborted at ../../../gfxboot line 424. make[3]: Leaving directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/themes/upstream/help-install' make -C po make[3]: Entering directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/themes/upstream/po' make[3]: Nothing to be done for `all'. make[3]: Leaving directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/themes/upstream/po' make -C fonts make[3]: Entering directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/themes/upstream/fonts' make[3]: Leaving directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/themes/upstream/fonts' perl -p -e 's/^(layout=.*)/$1,install/' src/gfxboot.cfg >bootlogo.dir/gfxboot.cfg perl -pi -e 's/^(theme=).*/$1upstream/' bootlogo.dir/gfxboot.cfg cp -rL data-install/* fonts/*.fnt po/*.tr bootlogo.dir cp -rL help-install/*.hlp bootlogo.dir cp: cannot stat `help-install/*.hlp': No such file or directory make[2]: *** [bootlogo] Error 1 make[2]: Leaving directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/themes/upstream' make[1]: *** [all] Error 2 make[1]: Leaving directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/themes/upstream' make -j2 doc make -C doc doc make[1]: Entering directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/doc' make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. ./mkdoc ../bincode.asm >reference.xml xmlto html-nochunks gfxboot.xml xmlto: /var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/doc/gfxboot.xml does not validate (status 3) xmlto: Fix document syntax or use --skip-validation option /var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/doc/gfxboot.xml:9: warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" > ^ warning: failed to load external entity "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" validity error : Could not load the external subset "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" Document /var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/doc/gfxboot.xml does not validate make[1]: *** [html] Error 13 make[1]: Leaving directory `/var/tmp/portage/media-gfx/gfxboot-4.1.39.1.1.1/work/gfxboot-4.1.39/doc' make: *** [doc] Error 2
(In reply to comment #81) > There was an update to gfxboot-4.1.39.1.1.1 in rion overlay, but it doesn't > build: can you upload full build.log ?
Created attachment 216170 [details] build.log Here it is.
(In reply to comment #83) > Created an attachment (id=216170) [details] > build.log > > Here it is. > hm docbookx.dtd should be installed with app-text/docbook-xml-dtd package, which is dependency of app-text/xmlto which is installed at least as dependency of gfxboot with doc USE flag. # equery files app-text/docbook-xml-dtd | grep docbookx.dtd /usr/share/sgml/docbook/xml-dtd-4.1.2/docbookx.dtd /usr/share/sgml/docbook/xml-dtd-4.2/docbookx.dtd /usr/share/sgml/docbook/xml-dtd-4.3/docbookx.dtd /usr/share/sgml/docbook/xml-dtd-4.4/docbookx.dtd /usr/share/sgml/docbook/xml-dtd-4.5/docbookx.dtd AFAIK, xmlto should not download DTD file from internet if it already has it locally, so i guess its problem of xmlto package or something wrong with your system, since i can't reproduce this. try "emerge -DuNv world" instaed of plain gfxboot installation.
equery files app-text/docbook-xml-dtd | grep docbookx.dtd /usr/share/sgml/docbook/xml-dtd-4.2/docbookx.dtd /usr/share/sgml/docbook/xml-dtd-4.3/docbookx.dtd /usr/share/sgml/docbook/xml-dtd-4.4/docbookx.dtd docbook-xml-dtd:4.5 is *not* installed. "emerge -uDN --with-bdeps=y world" does not try to install 4.5 since nothing needs it on my system. However, I installed it manually but the error persists.
ok, seems i got it. gfxboot requires 4.1.2 dtd. i added this dependency to ebuild, try to update overlay
Works fine now. Though dispatch-conf catches 31 /etc updates. I think the themes should be moved somewhere else. /etc doesn't look like the best choice for them on Gentoo.
agreed. patches are welcome
It disappeared from the overlay; where is it?
unmaintained anymore. use grub2
(In reply to comment #90) > unmaintained anymore. > use grub2 grub2 is hard-masked. Can you keep grub1 around until grub2 is at least in ~arch?
no, sorry. i don't want to maintain heavily patched and not quite stable software which i don't use myself. you can always download revision where it still exists and copy ebuilds into your overlay.
(In reply to comment #92) > no, sorry. > i don't want to maintain heavily patched and not quite stable software which i > don't use myself. > you can always download revision where it still exists and copy ebuilds into > your overlay. I want to do that, but I've no idea how :-P Any help?
try hg clone -r 2229 http://rion-overlay.googlecode.com/hg/
