Re: RC1 and UEFI
On 13.12.2013 23:14, Pete Travis wrote: > anaconda-devel-list has never struck me as an end user support list. I > don't think it is the appropriate place to ask for help reporting problems > with Fedora prereleases. This test@ list, however, seems to be working well > for the purpose. One thing is certain, you won't ask 'anaconda-patches' :) poma -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
-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- -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
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. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
On Dec 13, 2013 3:12 AM, "poma" wrote: > > On 13.12.2013 11:02, Chuck Forsberg WA7KGX wrote: > > > Please provide the name of a command that sends the required > > files to Red Hat when this happens. > > https://fedoraproject.org/wiki/How_to_debug_installation_problems :) > BTW don't hesitate to ask directly on > https://www.redhat.com/mailman/listinfo/anaconda-devel-list > > > poma > anaconda-devel-list has never struck me as an end user support list. I don't think it is the appropriate place to ask for help reporting problems with Fedora prereleases. This test@ list, however, seems to be working well for the purpose. --Pete -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
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. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
On 13.12.2013 11:02, Chuck Forsberg WA7KGX wrote: > Please provide the name of a command that sends the required > files to Red Hat when this happens. https://fedoraproject.org/wiki/How_to_debug_installation_problems :) BTW don't hesitate to ask directly on https://www.redhat.com/mailman/listinfo/anaconda-devel-list poma -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
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. Please provide the name of a command that sends the required files to Red Hat when this happens. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
On Dec 12, 2013, at 5:49 PM, Chuck Forsberg WA7KGX wrote: > Could you be more specific about what information you need > and how I might get this information? On Dec 5th in thread "Re: TC5 at Caddyshack" I replied to all, and asked you for roughly 8 pieces of information related to assertions that UEFI booting wasn't working, but you still haven't replied. But you often do this routine where you throw out global "it doesn't work" messages, and then people ask you for more information and only sometimes do you answer, and when you do answer they're often selective answers rather than complete ones. *shrug* Chris Murphy -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
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. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
Could you be more specific about what information you need and how I might get this information? On 12/12/2013 02:34 PM, Adam Williamson wrote: On Thu, 2013-12-12 at 08:32 -0800, Chuck Forsberg WA7KGX wrote: UEFI situation with 64 bit netinst is apparently unchanged. Still can't write to the hard drive. I did such an install. Worked fine. You tend to hit a problem, pull out two of the five hundred potential factors in play for any given problem, assume those two are causing the problem for no reason at all, and give us absolutely zero data on any of the other 498. It makes it effectively impossible to ever troubleshoot or do anything useful with your reports... -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: RC1 and UEFI
On Thu, 2013-12-12 at 08:32 -0800, Chuck Forsberg WA7KGX wrote: > UEFI situation with 64 bit netinst is apparently unchanged. > Still can't write to the hard drive. I did such an install. Worked fine. You tend to hit a problem, pull out two of the five hundred potential factors in play for any given problem, assume those two are causing the problem for no reason at all, and give us absolutely zero data on any of the other 498. It makes it effectively impossible to ever troubleshoot or do anything useful with your reports... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
RC1 and UEFI
UEFI situation with 64 bit netinst is apparently unchanged. Still can't write to the hard drive. Install without UEFI was nominal. -- Chuck Forsberg WA7KGX c...@omen.com www.omen.com Developer of Industrial ZMODEM(Tm) for Embedded Applications Omen Technology Inc "The High Reliability Software" 10255 NW Old Cornelius Pass Portland OR 97231 503-614-0430 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
