On Wed, Aug 08, 2007 at 05:08:18AM +0200, Magnus Granberg wrote:
> >Sounds like I made the wrong guess, then. You need to figure out where's
> >that null pointer coming from. Doesn't seem to be root_dev..
>
> #1 0x08049385 in setup (prefix=0x80670b0 "(md0)(vg-boot)/grub",
> dir=0x8067008 "/boot
Sounds like I made the wrong guess, then. You need to figure out where's
that null pointer coming from. Doesn't seem to be root_dev..
#1 0x08049385 in setup (prefix=0x80670b0 "(md0)(vg-boot)/grub",
dir=0x8067008 "/boot/grub",
boot_file=, core_file=0x805cb2a "core.img",
root=0x8067050 "vg-b
On Sun, Aug 05, 2007 at 02:14:28PM +0200, Magnus Granberg wrote:
> >>>Could you try the attached patch?
> >>>
> >>>--
> >>>Robert Millan
> >>>
> >>It did't fix the Segmentation fault :(
> >
> >It wasn't supposed to. Did you see what the patch is doing?
> >
> >--
> >Robert Millan
>
> grub-setup:
>Could you try the attached patch?
>
>--
>Robert Millan
>
It did't fix the Segmentation fault :(
It wasn't supposed to. Did you see what the patch is doing?
--
Robert Millan
grub-setup: info: prefix = /grub
grub-setup: info: changing current directory to /dev/mapper
grub-setup: info: 2 roo
On Sat, Aug 04, 2007 at 08:13:21PM +0200, Magnus Granberg wrote:
> >>boot_file=, core_file=0x805cb2a "core.img",
> >> root=0x8067050 "vg-boot", dest=0x0, must_embed=1)
> >>at util/i386/pc/grub-setup.c:223
> >> #2 0x0804a0bc in main (argc=Cannot access memory at address 0xb
> >> ) at util/
>>boot_file=, core_file=0x805cb2a "core.img",
>> root=0x8067050 "vg-boot", dest=0x0, must_embed=1)
>>at util/i386/pc/grub-setup.c:223
>> #2 0x0804a0bc in main (argc=Cannot access memory at address 0xb
>> ) at util/i386/pc/grub-setup.c:733
>> (gdb)
>
>Could you try the attached patch?
>
>-
On Sat, Aug 04, 2007 at 04:37:03AM +0200, Magnus Granberg wrote:
> Starting program:
> /sbin/grub-setup --directory=/boot/grub --device-map=/boot/grub/device.map
> /dev/md0
>
> Program received signal SIGSEGV, Segmentation fault.
> grub_device_open (name=0x0) at kern/device.c:38
> 38
