Vladimir 'φ-coder/phcoder' Serbinenko wrote:
...
> I discovered something. It looks like on Yeeloong the problem is caused
> by the skipped step of initialising of timings and power management.
> Quick and dirty fix:
...
Hello,
first of all sorry about delay - I am little bit busy now.
1.
I ful
Hi,
> > i have scruples about the semantics of
> > Platform ID which is global to the whole boot
> > catalog.
> Section header specifies the platform id of section entry
Oh. Somehow i oversaw that.
> > [detection of capabilities of xorriso version]
> What about checking error status of xorriso
Thomas Schmitt wrote:
> Hi,
>
> i took a look at grub-mkrescue.in with EFI and
> implemented the EFI-only case in xorriso-0.5.5
> timestamp 2010.04.20.103448:
>
>
Thanks, will test it later today.
> --efi-boot FILESet El Torito EFI boot image name and type
>
> Currently -b and --efi-bo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello devs,
Upgrading to GRUB 1.98 I fell victim for what appears to be an
incompatibility between GRUB and this controller.
Two drives are attached the controller, configured for mdraid in Linux.
Upon installation of grub-1.98 and the subsequent reb
Hi,
i took a look at grub-mkrescue.in with EFI and
implemented the EFI-only case in xorriso-0.5.5
timestamp 2010.04.20.103448:
--efi-boot FILESet El Torito EFI boot image name and type
Currently -b and --efi-boot override each other.
Who comes last will win.
--efi-boot is not yet immun