<div dir="ltr"><div>how do I go about getting in a position to do a git bisect. I know C/C++ and I know git, and I know hardware. Its the Fedora side of things that I am very unsure of. Some help and advice and pointers to what to look at and learn would be much appreciated.</div>
<div> </div><div>There seem to be three areas that need attacking/looking at :-</div><div> </div><div>a) The Anaconda main graphic interface gives a random coloured effect, not even a wrong x axis length style random screen.</div>
<div>b) The 'Basic Graphics Mode' screen is the top left hand corner of the full display image.</div><div>c) The graphics once you get it working is using a much lower resolution 640 by 480 where the ATI Rage XL supports 1600 by 1200. And it calls itself a 'Laptop' in the 'System Settings'.</div>
<div> </div><div>It looks like there must just be missing a configuration in X that by the looks of it was also missing in Ubuntu 8.10.</div><div> </div><div>As I say I don't really know where to start. I have tried making configuration modifications to X before but with very little joy.</div>
<div> </div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 3 April 2013 22:31, Bruno Wolff III <span dir="ltr"><<a href="mailto:bruno@wolff.to" target="_blank">bruno@wolff.to</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, Apr 03, 2013 at 22:22:12 +0100,<br>
Aaron Gray <<a href="mailto:aaronngray.lists@gmail.com" target="_blank">aaronngray.lists@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
I am a C/C++ coder and would love to be brought up to speed with what is<br>
required to be able fix bugs and problems in new releases for the hardware<br>
I posse. It seems things do get broken or left behind all too often. The<br>
nice IBM PowerPC based RAID cards in my older Fujitsu-Siemens 970's worked<br>
to FC9 then stopped and started working again in F14. Something to do with<br>
kudzu and hardware probing, but I never found out why in the end which was<br>
frustrating.<br>
</blockquote>
<br></div>
As noted in other replies timely testing. It is a lot easier to be successful getting something fixed if breakage is reported very shortly after the change that broke it.<br>
<br>
Finding the change that broke it yourself (say using git bisect) is also helpful as it points developers at exactly where the problem is in most cases. (Saving them time that can be used to consider how to fix the problem.)<br>
<br>
Being able to supply patches for fixes is even more valuable.<br>
</blockquote></div><br></div>