On Tue, Apr 5, 2011 at 12:02, Seth Goldberg wrote:
> It's not just USB. Loading large files via UEFI with GRUB2 takes an
> extremely long time. One of the things phcoder suggested was changing the
> cache size, which you've done. Od love to see a larger cache committed to
> the trunk so UEFI
On 05.04.2011 08:32, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 05.04.2011 07:33, Aravind Srinivasan wrote:
include/grub/disk.h
/* The size of a disk cache in sector units. */
#define GRUB_DISK_CACHE_SIZE 8
#define GRUB_DISK_CACHE_BITS 3
I tried changing this value to 8192 - and the
On 05.04.2011 09:17, KESHAV P.R. wrote:
In a crude benchmarking using s top watch, the
time between selection of menuentry to seeing the kernel boot messages
is approx 4 minutes (236 seconds) measured using a stop watch. I have
not yet tested with an updated ovmf in qemu or in duet.
You push for
2011/4/5 Vladimir 'φ-coder/phcoder' Serbinenko :
> On 05.04.2011 09:17, KESHAV P.R. wrote:
>>
>> In a crude benchmarking using stop watch, the
>> time between selection of menuentry to seeing the kernel boot messages
>> is approx 4 minutes (236 seconds) measured using a stop watch. I have
>> not ye
Hi,
currently you can't use an image which has whitespace in its filename as
GRUB background image because grub-mkconfig_lib lacks proper variable
quoting (see [1] for more information). I've attached three patches
which should fix this problem:
quote-big.patch:
This patch fixes the problem wi
Hy i have a question,
its possible execute a bash script on grub commando line? (option "c" on
grub), to be more especificle a have two motherboards and i need to
detect her before the kernel is loaded,
the bash script for example verify with "lspci" and make a "choice" in
to menu.lst, and
Yes, I agree.
thanks,
bvk.chaitanya
2011/3/31 Vladimir 'φ-coder/phcoder' Serbinenko :
> Hello, when discussing after the temporary wiki problems it was decided
> that it would be better to migrate the information from wiki into the
> manual and developper manual where legal reasons permit. You
Hi! I just realised nearly a month had passed and I never actually posted a
reply to this, although I meant to.
In short: This solved all my problems. Thanks for the help!
2011/3/11 Vladimir 'φ-coder/phcoder' Serbinenko
>
> > Is something like this already possible today, in ways I haven't
On 05.04.2011 14:56, gilson.san...@redepontocerto.com.br wrote:
>
> Hy i have a question,
>
> its possible execute a bash script on grub commando line? (option "c"
> on grub), to be more especificle a have two motherboards and i need to
> detect her before the kernel is loaded,
>
> the bash script
On Tue, Apr 05, 2011 at 09:56:28AM -0300, gilson.san...@redepontocerto.com.br
wrote:
> its possible execute a bash script on grub commando line? (option
> "c" on grub), to be more especificle a have two motherboards and i
> need to detect her before the kernel is loaded,
>
> the bash script for e
Hi,
I wanted to checkout the GRUB2 git repository. Can somebody please provide
me the correct link ?
--Thanks
Naresh Bhat
___
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
On Tue, Apr 05, 2011 at 07:19:51PM +0530, Naresh Bhat wrote:
> I wanted to checkout the GRUB2 git repository. Can somebody please provide
> me the correct link ?
GRUB is maintained in Bazaar, not git. Instructions are here:
http://www.gnu.org/software/grub/grub-download.en.html
--
Colin Wats
Ok, Collin
So a think in use "lspci" because my two motherboard is not equal, the
chipset and video card is different, but i think to use "lswh" i not
shure about it works, in GRUB legancy i not see any commands for help
with to create a performs conditions
Em 5/4/2011 13:01, grub-devel-r
Ok, Collin
So a think in use "lspci" because my two motherboard is not equal, the
chipset and video card is different, but i think to use "lswh" i not
shure about it works, in GRUB legancy i not see any commands for help
with to create a performs conditions
Em 5/4/2011 13:01, grub-devel-req
Tried the block IO patch. It is much better than the current default
performance
of 1.99. For the same initrd image (160M), loading from USB took approx 20
secs.
I also tried changing the value of GRUB_DISK_CACHE_BITS from 6 to 8, and load
time improved to approx 12 secs.
Just to note, on Le
Ok, Collin
So a think in use "lspci" because my two motherboard is not equal, the
chipset and video card is different, but i think to use "lswh" i not
shure about it works, in GRUB legancy i not see any commands for help
with to create a performs conditions
Em 5/4/2011 13:01, grub-devel-r
On 05.04.2011 18:39, gilson.san...@redepontocerto.com.br wrote:
>
> Ok, Collin
>
> So a think in use "lspci" because my two motherboard is not equal, the
> chipset and video card is different, but i think to use "lswh" i not
> shure about it works, in GRUB legancy i not see any commands for help
>
Le 05/04/2011 14:55, Alexander Kurtz a écrit :
Hi,
currently you can't use an image which has whitespace in its filename as
GRUB background image because grub-mkconfig_lib lacks proper variable
quoting (see [1] for more information). I've attached three patches
which should fix this problem:
On Tue, Apr 05, 2011 at 09:16:13PM +0200, Nicolas de Pesloüan wrote:
> Why do you use construct like "${x}" instead of "$x"?
There's a fair bit of this in existing GRUB code. I agree it's fairly
pointless, but in general it's best for patches to follow local style.
--
Colin Watson
Am Dienstag, den 05.04.2011, 21:16 +0200 schrieb Nicolas de Pesloüan:
> Why do you use construct like "${x}" instead of "$x"?
Because code isn't written once and then stays untouched forever. It
changes over time and may be used in situations you did not anticipate.
Writing solid code (and in shel
On Tue, Apr 05, 2011 at 09:32:40PM +0200, Alexander Kurtz wrote:
> Am Dienstag, den 05.04.2011, 21:16 +0200 schrieb Nicolas de Pesloüan:
> > Why do you use construct like "${x}" instead of "$x"?
>
> Because code isn't written once and then stays untouched forever. It
> changes over time and may be
Le 05/04/2011 21:32, Alexander Kurtz a écrit :
Am Dienstag, den 05.04.2011, 21:16 +0200 schrieb Nicolas de Pesloüan:
Why do you use construct like "${x}" instead of "$x"?
Because code isn't written once and then stays untouched forever. It
changes over time and may be used in situations you di
On Tue, Apr 05, 2011 at 10:07:46PM +0200, Nicolas de Pesloüan wrote:
> On the same kind of things, the construct if test "x$foo" = "x" is
> pointless. It is a very strange heritage from DOS, where IF x%A = x
> was a common construct, because DOS (command.com) lack quoting. (Is
> wasn't possible to
Le 05/04/2011 22:53, Colin Watson a écrit :
On Unix-like systems, though, and particularly when it comes to shell,
this often involves knowing about historical behaviour as well as
current behaviour.
Thanks Colin, for clarifying this!!
Very appreciated.
Nicolas.
24 matches
Mail list logo
