<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966#c73">Comment # 73</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - No signal to monitor with X and openchrome using VX855 chipset graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=91966">bug 91966</a> from <a class="email" href="mailto:kevinbrace@gmx.com" title="Kevin Brace <kevinbrace@gmx.com>"> Kevin Brace</a> <pre>(In reply to Christopher from <a href="show_bug.cgi?id=91966#c72">comment #72</a>) Hi Christopher, > So... wait. This is a *kernel* issue? Is this something I need to go to, er, > Mr Linus Himself for? (I hope not... although I'd be interested in hearing > his reaction to the fact that I've got a computer much like his famous 386 > :P probably I'd hear either 'bin it' or 'get cracking' tho... right now the > cynic in me is leaning towards the former.) > > Also, worth noting -- Puppy uses a 'patched' kernel. Something to do with > aufs, I think. (That's really all I know. Honest.) I may be able to talk > 666philb into adding an extra patch if he knows what exactly to stuff in... In addition to adjusting AGP Aperture size (i.e., make it larger), is it possible for your to adjust your integrated graphics frame buffer size (i.e., also make it larger)? I will attach my dmesg and Xorg.0.log shortly as a reference. At least on my laptop, the AGP Aperture is 128 MB and integrated graphics frame buffer is 64 MB. Regards, Kevin Brace</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>