[UTF-8]Vladimir 'Æ-coder/phcoder' Serbinenko writes:
On 09/15/2010 08:55 PM, Joey Korkames wrote:
Colin Watson writes:
On Xen (I'm told), it's possible to assign disk images in the host to
things that are named rather like partitions in the guest (e.g.
/dev/sda1), bu
Colin Watson writes:
On Xen (I'm told), it's possible to assign disk images in the host to
things that are named rather like partitions in the guest (e.g.
/dev/sda1), but that don't have an associated disk (e.g. /dev/sda);
indeed, the latter device is nonexistent. This confuses
grub_util_biosdi
This is aready worked on but the problem is that it generates too much
entries. If you have 5 different versions of hypervisor and 10
different
kernels you have 100 entries.
What if I add a max_entries option. Say, don't generate more than 4
stanzas total. Although I suppose then
A recent trunk commit (r2213) prevents me from building grub2 (Debian Lenny
amd64): here's my fix. I have no idea what the end result is (and have no
PPC equipment to test with), so maybe someone who understands this code can
clarify things.
The error that was being generated:
# make
...
gcc -
Colin Watson writes:
On Wed, Feb 17, 2010 at 05:37:16PM -0700, Joey Korkames wrote:
Christian Auby writes:
How would I go about setting up grub2 with both serial console and
graphical console?
You can't run simultaneous consoles with a stock grub2 build.
The experimental branch does su
Christian Auby writes:
How would I go about setting up grub2 with both serial console and
graphical console?
You can't run simultaneous consoles with a stock grub2 build.
The experimental branch does support it though:
http://robertmh.wordpress.com/2009/12/25/multiple-grub-terminals/#comment-
Lapohos Tibor writes:
... and I got a warning and an error message:
"Embedding area is too small for
core.img." and ...
It rather reads: "Your embedding area is unusually small. core.img won't fit in
it."
I found the error message accurate, but ultimately unhelpful when I got it.
I had t
I think this is growing severely overengineered. It is already more
complex than it needs to be.
The scripts in /etc/grub.d *are* config files. There's no reason you
can't edit them to suit your needs.
I agree that my solution does seem rather overengineered.
My problem is that while /etc/gr
> I don't know what pxegrub can do, but GRUB 2 has PXE support:
> http://grub.enbug.org/PXEBOOT
>
This would suffice for reading config and/or default from tftp so the
boot selection can be changed remotely on systems that have PXE.
I use PXE:UNDI all the time with Grub2, per that wiki. Works f
Joe McDonagh writes:
Hi all, I am having a rough time getting pxegrub to boot on a silicon
mechanics whitebox. I compiled the source from grub-1.96, and tried the
svn version, both with the same results. I haven't yet tested any other
systems, however this is what I see from tcpdump on the ser
Chip Panarchy writes:
If not, can we please work on a [PATCH] for GRUB2 to add support for
the Windows kernel?
Does this work?
insmod ntfs
set root=(hd0,1)
chainloader bootmgr
I don't have Vista/2008 so I can't test . . .
Perhaps bean's "loadbin" could be extended to support wrapping
Please use Multiboot. It's about time we start standarising on boot
protocols...
# kexec --type multiboot-x86 --load grub2.elf
issues this error:
> Base address: 8200 is not page aligned
Multiboot doesn't require that load addresses are page aligned, but I think you
can change the link ad
he boot
gets to where it was on the first patch. Boot log at bottom.
My ramdisk isn't fully populated yet so the launchd error is not
(necessarily) a bug.
I'm lurking on #grub as joeykork.
On Fri, Apr 24, 2009 at 2:41 AM, Joey Korkames
<mailto:joey%2bli...@kidfixit.com>joey+l
This patch did not work as well as the last one posted (on my test machine). The last one got
all the way to trying to run /sbin/launchd off the ramdisk - log post of
this one's boot attempt are attached.
Oh, here is my updated menuentry, works well and gives me serial output
of the darwin ker
Thanks for the comments. After reading those and peeking around your code, I
have a much better config that allos xnu.mod to give proper panic text:
#http://grub.enbug.org/gfxterm
loadfont /osstore/STAGE1a/grub2/unifont.pf2
set gfxmode="800x600x32"
set vbe_mode=0x115
terminal_output gfxterm
I have your whole patch series applied and have been trying to use this to
boot the PureDarwin 9 kernel (on various x86 32 & 64 bit machines):
menuentry "PureDarwin 9 (phcoder efiemu)" {
#efiemu_loadcore /osstore/STAGE1a/grub2/efiemu32.o
efiemu_loadcore /osstore/STAGE1a/grub2/efiem
Sounds like grub needs a git server (with /~user/stuff.git dirs)
I'll see about testing it with some various gear.
Thanks
-joey
phcoder writes:
Hello here is rediff & update of my efiemu patch. Now it's patched on
top of following patch chain:
bootmove->preboot->mmap->acpi
Now to use it
You can checkout the code via:
svn co svn://svn.savannah.gnu.org/grub/trunk/grub2
Then use the autocompile.sh
script that was posted earlier to make builds of grub2 or
you can wait for the nightly autobuilder to be set-up and just download its
results (from wherever they will be announced).
For a number of weird reasons, I would find the ability to kexec into grub2
from a running linux system useful.
In looking at the current code out there, there seems to be two ways to make
grub2 able to support this:
1) Add a 32-bit load segment to boot/i386/pc/lnxboot.S as described by
http
What's the advantage of booting with an mfsroot?
You can make a minimal fbsd system in the mfsroot that is smart enough to
"init_chroot" from a SMB/NFS netmount, or from a cloop file stored a CD or
http-sever (cached to a tmpfs (ramdisk)). Mine also unionfs-mounts a tmpfs
to what ever root th
That did the trick - amd64 boots with a mfsroot now. thanks!
-joey
phcoder writes:
Try this
Joey Korkames wrote:
phcoder writes:
Joey Korkames wrote:
Hmm, FreeBSD seems to choke when trying to load the grub-bootstrapped
mfsroot.gz (as the root device - haven't tried loading wi
phcoder writes:
Joey Korkames wrote:
Hmm, FreeBSD seems to choke when trying to load the grub-bootstrapped
mfsroot.gz (as the root device - haven't tried loading without rooting
from it)...
Thank you for the testing. Can you define "choke" more exactly?
Hmm, did my log
ction for that last patch:
-MOSTLYCLEANFILES += bsd_mod-loader_i386_bsd.d bsd_mod-loader_i386_bsd.d
+MOSTLYCLEANFILES += bsd_mod-loader_i386_bsd.d bsd_mod-loader_i386_bsd_helper.d
Thanks
joey
Joey Korkames writes:
Figured it out,
s/multiboot_mod-loader_i386_multiboot_helper/bsd_mod-loader_i3
Figured it out,
s/multiboot_mod-loader_i386_multiboot_helper/bsd_mod-loader_i386_bsd_helper/
and bingo!
Worked ion both Xen HVM and on a real amd64 box (over PXE)
Yay GRUB2 and its devs!
-joey
Joey Korkames writes:
I can't make grub2 build with phcoder's bsd64.diff. My guess it
I can't make grub2 build with phcoder's bsd64.diff. My guess it is beacuse conf/i386.mk is missing stuff related to
loader/i386/bsd_helper.S $(loader/i386/bsd_helper.S_DEPENDENCIES)?, but I wouldn't how or where to add it in.
cat kernel_syms.lst def-biosdisk.lst def-chain.lst def-linux16.ls
to include some chunks of this code? Alternatively
it may be that actually it needs only minor adjustments to the load code
Joey Korkames wrote:
phcoder writes:
Hello, could you do a research and tell me which binary format does
bsd64 use, the handoff CPU and the arguments on the stack?
*plane
phcoder writes:
Hello, could you do a research and tell me which binary format does
bsd64 use, the handoff CPU and the arguments on the stack?
*planes fly over my head*
Does this help?
http://svn.freebsd.org/viewvc/base?view=revision&revision=114379
I got that from looking over the svn log f
When migrating my Grub1 pxegrub setup to grub2 for testing, some of the new
quirks in the serial system have bothered me...
Unlike Grub Legacy, where I can specifiy
the serial console, and have the menu simul-displayed on both vga and serial
(if port actually exists); Grub2 can't simul-displ
28 matches
Mail list logo
