Hi,
Is there a known problem with these devices in GRUB?
I have a core i7 based Dell Latitude 6430 with an integrated broadcom smart
card reader. The devices looks like it is a USB 1.0/1.1 device, probably
sitting behind some hub to the EHCI-controller.
As far as I can tell, this machine does no
On Wed, Aug 28, 2013 at 04:51:00PM +0200, Vladimir 'φ-coder/phcoder' Serbinenko
wrote:
> On 28.08.2013 09:05, Michael Chang wrote:
> > Hi Andrey,
> >
> > 2013/3/29 Andrey Borzenkov :
> >> Is it intentional? I hit it when testing grub on encrypted partition.
> >> When no, I'll submit a patch.
> >
When allocating memory for the heap on ARMv7 UEFI, the init code
pretty much just allocates a chunk from the top of available RAM.
This means that when grub_mm_init_region is called for a region
extending to the top of the 32-bit address space, addr + size == 0.
However, this is not taken into acc
On Thu, 15 Aug 2013 17:51:03 +0100
TJ wrote:
> So I'd like to know what support for key-files and/or fingerprint
> reading is/could be as input for LUKS unlocking?
>
> My other thought, to keep things simple, is to encrypt the entire
> hard drive and install GRUB and the /boot/ files on the remo
On 29/08/13 20:13, Glenn Washburn wrote:
> On Thu, 15 Aug 2013 17:51:03 +0100
> TJ wrote:
>
>> So I'd like to know what support for key-files and/or fingerprint
>> reading is/could be as input for LUKS unlocking?
>>
>> My other thought, to keep things simple, is to encrypt the entire
>> hard driv
I would like to know if the following is possible:
* USB thumb drive has grub-1.98 on hd(0,1) gpt layout (boot-bios is hd0,2)
* hd(0,1)/boot/freedos has files
autoexec.bat, command.com, config.sys, kernel.sys, sys.com
Un-tarred from freedos FDOEM.144 and copied into folder
* Boot into USB drive's
