В Thu, 7 Feb 2013 15:56:34 -0800
Jordan Uggla пишет:
>
> The difference probably comes from using the 32 bit linux loading
> protocol rather than the 16 bit one. Try using "linux16" as a test.
>
I confirm that after booting with linux16 edd works.
__
On Thu, Feb 7, 2013 at 9:01 PM, Wang Weber wrote:
> Hi,
>
> My end goal is to get BIOS disk information from EDD module. More precisely,
> the /sys/firmware/edd/ entries.
That's not an end goal, that's a step toward an end goal. What
information do you want and why?
See also: http://www.catb.org
On Wed, Feb 6, 2013 at 7:21 PM, Wang Weber wrote:
> Hi,
>
> Recently I tried to create a Fedora 14 bootable USB key for X86_64. In the
> Kickstart script I want to use Linux EDD (Bios Enhanced Disk Drive Services)
> module to get the biosdisk information,
What information are you trying to get? W
В Thu, 7 Feb 2013 11:21:42 +0800
Wang Weber пишет:
> Hi,
>
> Recently I tried to create a Fedora 14 bootable USB key for X86_64. In the
> Kickstart script I want to use Linux EDD (Bios Enhanced Disk Drive
> Services) module to get the biosdisk information, however I met some
> strange behaviors
Hi,
Recently I tried to create a Fedora 14 bootable USB key for X86_64. In the
Kickstart script I want to use Linux EDD (Bios Enhanced Disk Drive
Services) module to get the biosdisk information, however I met some
strange behaviors. Following is the two tests:
1. Install GRUB2 ((GRUB) 2.00) to
