Re: Help understanding Anaconda source - walk through needed.
On 24 March 2014 19:26, Matthew Garrett mj...@srcf.ucam.org wrote: On Mon, Mar 24, 2014 at 07:21:51PM +, Aaron Gray wrote: The HP Dl140 G3 has MCA based graphics. F20 seems to be mainly fixed apart from MCA based Anaconda, which gets the resolution wrong, the screen being too small for the Anaconda graphics. VESA setup mode works fine however. Ah. You mean MGA, not MCA. It's entirely possible that there's a bug in the mgag200 driver that's resulting in a failure to get the correct EDID, but that's a kernel bug rather than an anaconda one. Why is the system when installed fine then ? Its just Anaconda setup that's getting the lower resolution. Aaron -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
On 17 March 2014 22:02, Adam Williamson awill...@redhat.com wrote: On Mon, 2014-03-17 at 09:39 -0400, Adam Jackson wrote: On Wed, 2014-03-12 at 20:07 +, Aaron Gray wrote: I am looking for someone to walk me through the Anaconda source as I need to understand it and cannot find where its 'main' is and how it launches X Windows as I need to work out why the main installer is not working on my HP D140 G3's with MCA video controllers. Anaconda doesn't really configure X before running it, it just relies on X's autoconfiguration logic to Do The Right Thing. I'm hoping you don't really mean MCA to mean Micro Channel Architecture there, one I didn't think anybody besides IBM was foolish enough to use that and two Fedora's X hasn't supported buses older than PCI for a couple of releases now. Whatever problem you're having with graphics at install time, you will almost certainly also have after installed; it's usually easier to debug by going ahead and installing in text mode and then debugging graphics once installed. I think the system he's referring to is this one: http://reviews.cnet.com/soho-servers/hp-proliant-dl140/4507-3125_7-30620088.html Graphics Controller Type Integrated Interface Type PCI Graphics Processor / Vendor ATI RAGE XL Video Memory 8 MB / 8 MB (max) SDRAM Video Interfaces VGA Adam, We thought it was an ATI Rage to begin with but X.org says differently for my systems. Aaron -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
The HP Dl140 G3 has MCA based graphics. F20 seems to be mainly fixed apart from MCA based Anaconda, which gets the resolution wrong, the screen being too small for the Anaconda graphics. VESA setup mode works fine however. On 17 March 2014 22:02, Adam Williamson awill...@redhat.com wrote: On Mon, 2014-03-17 at 09:39 -0400, Adam Jackson wrote: On Wed, 2014-03-12 at 20:07 +, Aaron Gray wrote: I am looking for someone to walk me through the Anaconda source as I need to understand it and cannot find where its 'main' is and how it launches X Windows as I need to work out why the main installer is not working on my HP D140 G3's with MCA video controllers. Anaconda doesn't really configure X before running it, it just relies on X's autoconfiguration logic to Do The Right Thing. I'm hoping you don't really mean MCA to mean Micro Channel Architecture there, one I didn't think anybody besides IBM was foolish enough to use that and two Fedora's X hasn't supported buses older than PCI for a couple of releases now. Whatever problem you're having with graphics at install time, you will almost certainly also have after installed; it's usually easier to debug by going ahead and installing in text mode and then debugging graphics once installed. I think the system he's referring to is this one: http://reviews.cnet.com/soho-servers/hp-proliant-dl140/4507-3125_7-30620088.html Graphics Controller Type Integrated Interface Type PCI Graphics Processor / Vendor ATI RAGE XL Video Memory 8 MB / 8 MB (max) SDRAM Video Interfaces VGA -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
On Mon, Mar 24, 2014 at 07:21:51PM +, Aaron Gray wrote: The HP Dl140 G3 has MCA based graphics. F20 seems to be mainly fixed apart from MCA based Anaconda, which gets the resolution wrong, the screen being too small for the Anaconda graphics. VESA setup mode works fine however. Ah. You mean MGA, not MCA. It's entirely possible that there's a bug in the mgag200 driver that's resulting in a failure to get the correct EDID, but that's a kernel bug rather than an anaconda one. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
On Wed, 2014-03-12 at 20:07 +, Aaron Gray wrote: I am looking for someone to walk me through the Anaconda source as I need to understand it and cannot find where its 'main' is and how it launches X Windows as I need to work out why the main installer is not working on my HP D140 G3's with MCA video controllers. Anaconda doesn't really configure X before running it, it just relies on X's autoconfiguration logic to Do The Right Thing. I'm hoping you don't really mean MCA to mean Micro Channel Architecture there, one I didn't think anybody besides IBM was foolish enough to use that and two Fedora's X hasn't supported buses older than PCI for a couple of releases now. Whatever problem you're having with graphics at install time, you will almost certainly also have after installed; it's usually easier to debug by going ahead and installing in text mode and then debugging graphics once installed. - ajax -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
On Mon, 2014-03-17 at 09:39 -0400, Adam Jackson wrote: On Wed, 2014-03-12 at 20:07 +, Aaron Gray wrote: I am looking for someone to walk me through the Anaconda source as I need to understand it and cannot find where its 'main' is and how it launches X Windows as I need to work out why the main installer is not working on my HP D140 G3's with MCA video controllers. Anaconda doesn't really configure X before running it, it just relies on X's autoconfiguration logic to Do The Right Thing. I'm hoping you don't really mean MCA to mean Micro Channel Architecture there, one I didn't think anybody besides IBM was foolish enough to use that and two Fedora's X hasn't supported buses older than PCI for a couple of releases now. Whatever problem you're having with graphics at install time, you will almost certainly also have after installed; it's usually easier to debug by going ahead and installing in text mode and then debugging graphics once installed. I think the system he's referring to is this one: http://reviews.cnet.com/soho-servers/hp-proliant-dl140/4507-3125_7-30620088.html Graphics Controller Type Integrated Interface Type PCI Graphics Processor / Vendor ATI RAGE XL Video Memory 8 MB / 8 MB (max) SDRAM Video Interfaces VGA -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
Thanks for putting me right, will have to look into this properly. I was mainly looking at Anaconda and F20 for my HP DL140 G3 servers which there are problems with the video with. On 14 March 2014 01:05, Adam Williamson awill...@redhat.com wrote: On Thu, 2014-03-13 at 14:38 +, Aaron Gray wrote: Not sure yet but Anaconda has some specialised support for CPU's presumably the processor name at a minimum. I'm not sure if I'm missing something or you are, but Anaconda doesn't really distinguish between CPUs, and it does support ARM. anaconda is a supported deployment method for Calxeda ARM systems in Fedora 20: https://fedoraproject.org/wiki/Architectures/ARM/F20/Installation#Calxeda_EnergyCore_.28HighBank_and_Midway.29 anaconda does have a concept of *platforms*. The various platforms are defined in blivet these days, in fact, in blivet/platform.py: class X86(Platform): class EFI(Platform): class MacEFI(EFI): class Aarch64EFI(EFI): class PPC(Platform): class IPSeriesPPC(PPC): class NewWorldPPC(PPC): class PS3(PPC): class S390(Platform): class ARM(Platform): class omapARM(ARM): and used in several places in blivet and anaconda (mainly partitioning and bootloader installation). 'Aarch64EFI' is for aarch64 systems using UEFI firmware, IIRC. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
Not sure yet but Anaconda has some specialised support for CPU's presumably the processor name at a minimum. On 12 March 2014 21:55, Jon jdisn...@gmail.com wrote: On Wed, Mar 12, 2014 at 4:16 PM, Aaron Gray aaronngray.li...@gmail.com wrote: Okay think I have got a handle on it now, the main python file in the root does not have a .py extension. Very helpful ! Another interesting thing is there is no ARM support which I will be needing at some point. Aaron On 12 March 2014 20:07, Aaron Gray aaronngray.li...@gmail.com wrote: Hi, I am looking for someone to walk me through the Anaconda source as I need to understand it and cannot find where its 'main' is and how it launches X Windows as I need to work out why the main installer is not working on my HP D140 G3's with MCA video controllers. https://git.fedorahosted.org/cgit/anaconda.git/tree/?h=f20-branch Hope someone kind person has time to help me. Regards, Aaron What kind of ARM support will you be looking to have? -Jon Disnard fas: parasense irc: masta -- -Jon -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
On Thu, 2014-03-13 at 14:38 +, Aaron Gray wrote: Not sure yet but Anaconda has some specialised support for CPU's presumably the processor name at a minimum. I'm not sure if I'm missing something or you are, but Anaconda doesn't really distinguish between CPUs, and it does support ARM. anaconda is a supported deployment method for Calxeda ARM systems in Fedora 20: https://fedoraproject.org/wiki/Architectures/ARM/F20/Installation#Calxeda_EnergyCore_.28HighBank_and_Midway.29 anaconda does have a concept of *platforms*. The various platforms are defined in blivet these days, in fact, in blivet/platform.py: class X86(Platform): class EFI(Platform): class MacEFI(EFI): class Aarch64EFI(EFI): class PPC(Platform): class IPSeriesPPC(PPC): class NewWorldPPC(PPC): class PS3(PPC): class S390(Platform): class ARM(Platform): class omapARM(ARM): and used in several places in blivet and anaconda (mainly partitioning and bootloader installation). 'Aarch64EFI' is for aarch64 systems using UEFI firmware, IIRC. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Help understanding Anaconda source - walk through needed.
Hi, I am looking for someone to walk me through the Anaconda source as I need to understand it and cannot find where its 'main' is and how it launches X Windows as I need to work out why the main installer is not working on my HP D140 G3's with MCA video controllers. https://git.fedorahosted.org/cgit/anaconda.git/tree/?h=f20-branch Hope someone kind person has time to help me. Regards, Aaron -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
Okay think I have got a handle on it now, the main python file in the root does not have a .py extension. Very helpful ! Another interesting thing is there is no ARM support which I will be needing at some point. Aaron On 12 March 2014 20:07, Aaron Gray aaronngray.li...@gmail.com wrote: Hi, I am looking for someone to walk me through the Anaconda source as I need to understand it and cannot find where its 'main' is and how it launches X Windows as I need to work out why the main installer is not working on my HP D140 G3's with MCA video controllers. https://git.fedorahosted.org/cgit/anaconda.git/tree/?h=f20-branch Hope someone kind person has time to help me. Regards, Aaron -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Help understanding Anaconda source - walk through needed.
On Wed, Mar 12, 2014 at 4:16 PM, Aaron Gray aaronngray.li...@gmail.com wrote: Okay think I have got a handle on it now, the main python file in the root does not have a .py extension. Very helpful ! Another interesting thing is there is no ARM support which I will be needing at some point. Aaron On 12 March 2014 20:07, Aaron Gray aaronngray.li...@gmail.com wrote: Hi, I am looking for someone to walk me through the Anaconda source as I need to understand it and cannot find where its 'main' is and how it launches X Windows as I need to work out why the main installer is not working on my HP D140 G3's with MCA video controllers. https://git.fedorahosted.org/cgit/anaconda.git/tree/?h=f20-branch Hope someone kind person has time to help me. Regards, Aaron What kind of ARM support will you be looking to have? -Jon Disnard fas: parasense irc: masta -- -Jon -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
