RC1 and UEFI

[Bob Lightfoot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/13/2013 06:02 PM, Chuck Forsberg WA7KGX wrote:
> 
> On 12/13/2013 02:44 AM, Adam Williamson wrote:
>> On Fri, 2013-12-13 at 02:02 -0800, Chuck Forsberg WA7KGX wrote:
>>> On 12/12/2013 04:53 PM, Adam Williamson wrote:
>>>> On Thu, 2013-12-12 at 16:49 -0800, Chuck Forsberg WA7KGX
>>>> wrote:
>>>>> Could you be more specific about what information you need 
>>>>> and how I might get this information?
>>>> In your initial description you wrote "Anaconda cannot
>>>> modify the hard drive when booted UEFI." This is a somewhat
>>>> odd description, and impossible to interpret without more
>>>> details. What exactly do you mean by it? Can you please
>>>> describe, in detail and from start to finish, what you did
>>>> and what happened, rather than a cryptic one-liner? And, 
>>>> ideally, post the usual anaconda debugging logs -
>>>> anaconda.log , program.log , storage.log etc etc from a
>>>> failed install attempt. Thanks.
>>> The first thing I do when the Anaconda screen comes up is to
>>> select the hard drive and repartition it.  I select standard 
>>> partitions and then custom partitioning.  When booting under 
>>> UEFI Anaconda cannot modify the hard drive in any onbious way.
>> I still can't really understand what you mean by 'cannot modify
>> the hard drive in any obvious way'. Are you saying it does not
>> display any existing partitions? Can you provide a screenshot or
>> a precise description of what you see, and how it looks different
>> in a BIOS install?
>> 
>>> Please provide the name of a command that sends the required 
>>> files to Red Hat when this happens.
>> There actually is a somewhat obscure utility in anaconda that was
>> meant to do this, but I don't think it works any more. As long as
>> you have a network connection, you can just switch to
>> ctrl-alt-f2, find the log files in /tmp , and 'fpaste' or 'scp'
>> them out.
> I ran fpaste *.log from the /tmp directory. There were error
> messages. If it worked you should have the results.
> 
Chris if fpaste works it returns a URL address which is where the
posted files reside.  we'll need that URL to find them. Given you had
error messages I suspect that networking was not setup and activated
when you ran fpaste and no URL was returned.  If you can repeat and
provide the URL or the text of the error messages, then others can
assist I suspect.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSq5WlAAoJEKqgpLIhfz3XR9EIAJnKA7sSGbHBK2SqO8CeC7na
Pr/8ygNe0CfDum4Ogb63rDBNi+FUcDj626vRlaOeeU6d7BgPaAroASDmGftxUOx2
1ocdDCgpKviByM4V1f85jHYCnuZowGVGQSHwhi3rKF91rv2ge6tH1faB7/rTbVsO
x4ks1iiI9nJEuBoV2hAsCqXRiOxGH26plfK7Hwbr0NrkFDzjfDluLwWG0hVz87wJ
M7aE+DLseeQ2bbD3K909Xk5S1Igp3qp6Ui1BX9WsnxBIXuIVU032W2f6D9Z/Klep
Up/7ZAnopyu2bghv56p51H3ngqOMa5LXzzn3vjlB1gVJFXCxNytkEXTgRGevBLk=
=HH3t
-----END PGP SIGNATURE-----