Sorry, I no longer have access to that hardware to perform the test (it was
the property of a former employer).  However, I can tell you I did perform a
network install using the mini iso as late as about three/four weeks ago.
At that time (post 8.4.1 release) it still had a problem.

I did do a few internet searches on the matter and it appears the problem
may be fixed in more recent kernels.  I found a few threads talking about
how support had been additional display frequencies.  Aparently the display
adapter in the Geode was confused by some of these frequencies (it did not
support them but they were close enough to the ones it did support that it
thought they were supported).  That code was then removed from subsequent
kernel builds as a solution until it could get worked out.  IIRC, this all
took place around the first/second week of May.

Sorry for being so vague, but since I had the work around noted in the bug
report, I just moved forward with that.  Also all my documentation was left
at my former employer.  However, I am confident that kernels developed after
about May 15th will likely work w/o issue.


On 8/28/08, Leann Ogasawara <[EMAIL PROTECTED]> wrote:
>
> The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
> upcoming Intrepid Ibex 8.10 release.  As a result, the kernel team would
> appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
> There are one of two ways you should be able to test:
>
> 1)  If you are comfortable installing packages on your own, the linux-
> image-2.6.27-* package is currently available for you to install and
> test.
>
> --or--
>
> 2)  The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer
> 2.6.27 Ubuntu kernel.  Alpha5 is set to be released Thursday Sept 4.
> Please watch http://www.ubuntu.com/testing for Alpha5 to be announced.
> You should then be able to test via a LiveCD.
>
> Please let us know immediately if this newer 2.6.27 kernel resolves the
> bug reported here or if the issue remains.  More importantly, please
> open a new bug report for each new bug/regression introduced by the
> 2.6.27 kernel and tag the bug report with 'linux-2.6.27'.  Also, please
> specifically note if the issue does or does not appear in the 2.6.26
> kernel.  Thanks again, we really appreicate your help and feedback.
>
> ** Tags added: cft-2.6.27
>
> --
> Corrupt Terminal Graphics
> https://bugs.launchpad.net/bugs/228706
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "linux" source package in Ubuntu: Incomplete
>
> Bug description:
> I have two Ampro ETX 610 boards (
> http://www.ampro.com/Products/ETX%2DXTX/ETX%5F610/), one connected to a
> VGA CRT monitor, the other connected to an NEC SVA150XG05TB flat panel
> display.  This bug ONLY applies to the one with the NEC flat panel,
> everything worked just fine on the one with the CRT monitor.
>
> I successfully installed the CLI only (ie no xorg, window manager, etc.)
> using the Ubuntu 8.04 mini.iso.  However, at bootup, the graphics would
> crash shortly after "Loading Hardware Drivers" is displayed.  After several
> minutes, the sytem would crash and reboot.  Note, usplash is NOT installed,
> boot status is purely text based.
>
> As mentioned earlier, the problem does not exist on the system with the CRT
> monitor, so I moved the drive to that setup, and installed xorg, gdm, and
> fluxbox.  I then replaced the card in the system with the NEC flat
> panel.  The graphics still get corrupt at the same point, however the
> graphics return once gdm is loaded.
>
> Changing to a virtual terminal causes the same viceo corruption to
> appear.  The graphics return to normal once returned to the desktop.  Also
> the same graphics corruption is seen when rebooting/shutting down (again,
> usplash is not installed, so shutdown should be text based).
>
> No corruption is present within fluxbox terminal windows.
>
>
> Attached is lspci -vv output
>

-- 
Corrupt Terminal Graphics
https://bugs.launchpad.net/bugs/228706
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to