"The eeepc's bios have its resolutions listed incorrectly. This prevents us from using the console with a framebuffer at the resolution of 800×480. That is unless we use the 915resolution tool. Now I've seen guides that say to use 915resolution + klibc and, v86d using the userspace, kernelspace linker. However I found this buggy, though lucky for there is an alternative. Nathan Coulson wrote a patch for Grub2 that lets us use 915resolution before we load our kernel. This eliminates the need for klibc ,v86d, and the kernel linker. It also appears to a lot more stable." (from: http://wiki.eeeuser.com/howto:installgentoo ) Sorry if I copied-paste the website (it's creative common) but I'd like to suggest you to introduce that patch in grub-1.96.ebuild
Created attachment 177222 [details, diff] Includes 915resolution support directly into grub2-alpha This solution is more straight forward than kernel patches supported by userspace drivers.
Created attachment 188697 [details, diff] diff against current ebuild to apply i915resolution patch Here is a modified ebuild that successfully applies the patch to the source, as suggested on eeeuser.com. I used an 'i915' USE flag to conditionally apply the patch. It still needs some work since there isn't any 915resolution.mod file after the build.
Created attachment 188712 [details, diff] 915resolution patch with updated conf/common.mk Nathan Coulson's patch modified conf/common.rmk, so conf/common.mk needs to be re-generated. This requires ruby and is not done during a normal compile/make. This patch includes an updated conf/common.mk and will result in correctly emerging grub with 915resolution.mod included.
Is this still needed with 1.97.x?
Created attachment 227545 [details, diff] base 915resolution patch (includes common.mk generated by piping the .rmk through genmk.rb) I'm currently using this to get native resolution framebuffer (and X with fbdev) on my Dell Inspiron Mini 10, without using proprietary drivers. I'll post the patches here in case anyone is interested. If anyone wants more info about the Mini 10 then see here: http://en.gentoo-wiki.com/wiki/Dell_Inspiron_Mini_10_(1010)
Created attachment 227547 [details, diff] fix to compile with >=grub-1.97
Created attachment 227551 [details, diff] add support for GMA 500 chipset (tested with Dell Inspiron Mini 10) This is a rebased version of the patch from here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543917
not sure how Tomas feels about this ...
Created attachment 289019 [details, diff] 915resolution patch from grub-extras I patch it src_prepare like this: epatch "$FILESDIR"/grub-1.9.9-915resolution.patch # Include grub-extras/915resolution in the build: # GRUB_CONTRIB must be the name of single directory for autogen.sh # to include $GRUB_CONTRIB/* subdirectories (exactly 1 level deep). export GRUB_CONTRIB=grub-extras sed -i -e '/^autoreconf/s:^:e:' autogen.sh || die ( . ./autogen.sh )
I would recommend going ahead with this patch as upstream is not exactly responsive so we should keep this working.
(In reply to comment #9) > Created attachment 289019 [details, diff] [details, diff] > 915resolution patch from grub-extras > > I patch it src_prepare like this: > > epatch "$FILESDIR"/grub-1.9.9-915resolution.patch > # Include grub-extras/915resolution in the build: > # GRUB_CONTRIB must be the name of single directory for autogen.sh > # to include $GRUB_CONTRIB/* subdirectories (exactly 1 level deep). > export GRUB_CONTRIB=grub-extras > sed -i -e '/^autoreconf/s:^:e:' autogen.sh || die > ( . ./autogen.sh ) Since the GRUB ebuild contains epatch_user you should simply place the patch in: /etc/portage/patches/sys-boot/grub/yourpatchgoeshere.patch Which means you won't have to edit the ebuild every time a new grub comes out. :)
(In reply to comment #9) > epatch "$FILESDIR"/grub-1.9.9-915resolution.patch > # Include grub-extras/915resolution in the build: > # GRUB_CONTRIB must be the name of single directory for autogen.sh > # to include $GRUB_CONTRIB/* subdirectories (exactly 1 level deep). > export GRUB_CONTRIB=grub-extras > sed -i -e '/^autoreconf/s:^:e:' autogen.sh || die > ( . ./autogen.sh ) Also too bad the ebuild edit doesn't work anymore: ./autogen.sh: line 9: autogen: command not found Where would I get the autogen.sh script from, is it included with grub-extras or just taken out of grub-2.00-beta2-r1?
(In reply to comment #12) > (In reply to comment #9) > > epatch "$FILESDIR"/grub-1.9.9-915resolution.patch > > # Include grub-extras/915resolution in the build: > > # GRUB_CONTRIB must be the name of single directory for autogen.sh > > # to include $GRUB_CONTRIB/* subdirectories (exactly 1 level deep). > > export GRUB_CONTRIB=grub-extras > > sed -i -e '/^autoreconf/s:^:e:' autogen.sh || die > > ( . ./autogen.sh ) > > Also too bad the ebuild edit doesn't work anymore: > > ./autogen.sh: line 9: autogen: command not found > > Where would I get the autogen.sh script from, is it included with > grub-extras or just taken out of grub-2.00-beta2-r1? Fixed it for <sys-devel/grub-9999: - For minimal ebuild editing, place the patch in /etc/portage/patches/sys-boot/grub/patchgoeshere.patch - Add the following lines to the "else" code of "if [[ ${PV} == "9999" ]]" near the start of the ebuild: export GRUB_CONTRIB=grub-extras DO_AUTORECONF=true I'll try to create a modified ebuild with i915 USE flag and upload.
> Fixed it for <sys-devel/grub-9999: > > - For minimal ebuild editing, place the patch in > /etc/portage/patches/sys-boot/grub/patchgoeshere.patch > - Add the following lines to the "else" code of "if [[ ${PV} == "9999" ]]" > near the start of the ebuild: > > export GRUB_CONTRIB=grub-extras > DO_AUTORECONF=true > > I'll try to create a modified ebuild with i915 USE flag and upload. Any progress on this? I tried it but no 915resolution.mod file was compiled.
add to /etc/portage/env/grub-video AUTOTOOLS_AUTORECONF=1 GRUB_CONTRIB=grub-extras add to /etc/portage/package.env/grub-video sys-boot/grub grub-video.conf Throw patch into /etc/portage/patches/sys-boot/grub and compile all done :)
the patch does not work anymore for the current versions grub-2.00-r4 and grub-2.00_p5107-r1. Any progress in making this availible in the portage tree?
cat /var/tmp/portage/sys-boot/grub-2.00_p5107-r1/temp/grub-2.00_p5107-r1-915resolution.patch.out ***** grub-2.00_p5107-r1-915resolution.patch ***** PWD: /var/tmp/portage/sys-boot/grub-2.00_p5107-r1/work/grub-2.00 ================================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//sys-boot/grub/grub-2.00_p5107-r1-915resolution.patch' ================================================== patch program exited with status 1 ================================================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//sys-boot/grub/grub-2.00_p5107-r1-915resolution.patch' ================================================== patch program exited with status 1 ================================================== PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//sys-boot/grub/grub-2.00_p5107-r1-915resolution.patch' ================================================== patch program exited with status 1 ================================================== PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//sys-boot/grub/grub-2.00_p5107-r1-915resolution.patch' ================================================== patch program exited with status 1 ================================================== PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < '/etc/portage/patches//sys-boot/grub/grub-2.00_p5107-r1-915resolution.patch' ================================================== patch program exited with status 1
I've successfully applied the patch to grub-2.00_p5107-r2 now. You need to set these env options: AUTOTOOLS_AUTORECONF=1 GRUB_AUTOGEN=1 GRUB_CONTRIB=grub-extras In addition, you need to emerge autogen first. A proper ebuild with support for the patch would be great.
It seems strange to me that this module has not been merged upstream. It's not something that I really want to officially support.
