Hi all,
I am using grub2 uhci.c usb driver for testing new hardware, on some
occuisions the UHCI signature test fails (can be found on the PCI iteration
routine), the driver thest if the controller founded by PCI has a signature
as uhci should have (0x0c0300), on some of my new hardwares the signat
On Fri, Jul 02, 2010 at 01:44:21AM +0200, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
> On 07/02/2010 01:32 AM, Colin Watson wrote:
> > The changes seem to have been to simplify the test to:
> >
> > [ "x`grub-probe -t abstraction --device ${GRUB_DEVICE}`" = "xlvm" ]
> >
> > Unfortunately this
Hi,
Sorry for breaking the thread, but I just stepped in because I
participated in the standarisation of the BIOS Boot Partition
mechanism, and in early discussions about this hybrid DOS/GPT protocol
which led to the standard being discussed, and I want to clarify
something.
GRUB implements the B
I've been looking at Felix's raid branch which adds support for mdadm
metadata version 1.x, and trying to bring it up to date. The first
thing I noticed was an issue with device naming. With mdadm metadata
0.9, md devices were just numbered. Easy. With mdadm metadata 1.x,
devices can also be na
I observed a similar beahaviour as stephen in my side.
Especially I had no dificulty at all to switch to a 1680x1050x32 graphic
mode (following Piscium's advices) in the grub2 interface with what
follows in grub.cfg
insmod efi_gop
insmod font
loadfont (hd1,gpt4)/usr/sh
Hi Reynold,
I've made some progress past you recently! I think there are bugs in
the Linux Kernel now that must be overcome by the folks over at kernel
development. Did you try the 'noefi' kernl boot flag? It allowed me to
get past the hang and my system would actually boot.
Also, I'm using th
On 07/02/2010 12:30 PM, jonatan perry wrote:
> Hi all,
> I am using grub2 uhci.c usb driver for testing new hardware, on some
> occuisions the UHCI signature test fails (can be found on the PCI
> iteration routine), the driver thest if the controller founded by PCI
> has a signature as uhci should
On 07/02/2010 03:13 PM, Colin Watson wrote:
> Does anyone object to this simple scheme?
>
> /dev/md/NAME => (md/NAME)
> all other md device name formats as before
>
>
I like the idea of prepending a name of subsystem to the named (and not
just numbered) devices. In retrospect lvm should have
hi there,
On Tue, Jun 29, 2010 at 07:30:57AM +0200, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
> I've cleaned up your patch using my more generic string parsing
> functions. Could you test attached patch?
i read over the patch and it looks good. i've just tested the patch
and grub-install, gr
Hi Stephen,
The situation is a little bit better in my side too...
I recompile the 2.6.34 kernel following the instructions in
Documentation/x86/x86_64/uefi.txt, from the kernel linux package.
Especially, I defined "CONFIG_FRAMEBUFFER_CONSOLE=y" int the .config file
instead of "CONFIG_FRAMEBUF
Most likely the disk enumeration is different than what you have in
the grub list.
boot into a working system, plug your disk with the linux in, and then
do sudo blkid
get the UUID of your root filesystem, and then put it as
root=UUID=00----0 instead of /dev/sda4.
On 07/01/10 15:42, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
After moving of partitions containing it's recommended to reinstall
bootloader
But I don't see the need to standartise the interface between MBR code
and the rest. Standartisation is good only for interoperability between
differe
12 matches
Mail list logo