<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc="http://microsoft.com/officenet/conferencing" xmlns:D="DAV:" xmlns:Repl="http://schemas.microsoft.com/repl/" xmlns:mt="http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda="http://www.passport.com/NameSpace.xsd" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs="http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p="http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss="http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi="http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi="http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp="http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl="http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl="http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Trebuchet MS";
panose-1:2 11 6 3 2 2 2 2 2 4;}
@font-face
{font-family:Webdings;
panose-1:5 3 1 2 1 5 9 6 7 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Good Morning everyone,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have a Sony Via laptop (700mhz) that has the same problem. Has there been any more discussion or a workaround for this?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thank you,<br><br><br><br>Chance Walton<br>chanwalt@technicalelite.com<br>P: 813-936-2030<br>C: 813-482-8877<br>F: 813-936-9268<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:24.0pt;font-family:Webdings;color:green'>P</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='font-size:10.0pt;font-family:"Trebuchet MS","sans-serif";color:green'>Please consider the environment before printing this e-mail.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> voyage-linux-bounces+chanwalt=technicalelite.com@list.voyage.hk [mailto:voyage-linux-bounces+chanwalt=technicalelite.com@list.voyage.hk] <b>On Behalf Of </b>mad qwerty<br><b>Sent:</b> Thursday, September 15, 2011 12:33 PM<br><b>To:</b> voyage-linux@voyage.hk<br><b>Subject:</b> [Voyage-linux] Local console graphic failure<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi list, it's my first post here..<br>1st of all, HUGE Thanks to Punky-tse and all contributors for this GREAT project :-)<br><br>i'm very rookie with Linux in general, so i anticipate my excuses, <br>try to be more simple as possible, when helping me (thanks in advance)<br><br>I'm using Voyage MPD 0.7.5 onto an AMD E-350 platform (exactly this : <a href="http://www.asus.com/Motherboards/AMD_CPU_on_Board/E35M1I_DELUXE/">http://www.asus.com/Motherboards/AMD_CPU_on_Board/E35M1I_DELUXE/</a> ) <br>and had some tests on different notebooks, and VMware.<br><br>It seems that Voyage starts booting with a real 80x25-char text console, then, at a certain time, it changes the screen output into a graphic "simil-text" console (i read somewhere the correct name of this "simil-text" but i can't remember now)<br>you can clearly see monitor going off for a while, then come back with a graphic "simil-text" behaviour, with more line & rows char width and length.<br><br>This operation goes OK on older notebooks, <br>but into an almost-modern HP EliteBook 6930p, and into my reference platform (AMD E350) this operation leads to a graphic failure, <br>screen filled of random pixels, and there's no way to get local console resetting or working, <br>i can't switch tty virtual consoles, nor "clear" or "clear_console" commands reset this crash.<br><br>SSH sessions via IP connection are available, as Voyage continues to boot without worries.<br><br>i searched info by googling the web :<br>- similar problem here : <a href="http://translate.google.com/translate?sl=ja&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fslashdot.jp%2F~tt%2Fjournal%2F531820&act=url">http://translate.google.com/translate?sl=ja&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fslashdot.jp%2F~tt%2Fjournal%2F531820&act=url</a> but no solution provided (if i well understood the translation)<br>- AMD driver doesn't install because it needs an X server ( <a href="http://forums.amd.com/forum/messageview.cfm?catid=390&threadid=145785">http://forums.amd.com/forum/messageview.cfm?catid=390&threadid=145785</a> )<br>- i tried installing "fbset" , and i was able to change /dev/fb0 width and height on working hardware, but no change or variations in not-working hardware<br>- i tried vga=nnn parameter onto kernel row on /boot/grub/menu.lst, but it changes the behaviour only for the period from startup to the crash (change to "simil-text" console will always perform)<br><br>can someone help me, <br>is there a way to avoid this "simil-tex" switch, and remain into a real 80x25 text console, <br>or where i can control and set this graphic "simil-text" behaviour ?<br><br>another curious thing : <br>if i take an image of the Voyage disk running with AMD E350, and restoring it into a virtual environment, the switch from real 80x25 text console to "simil-text" graphic console doesn't happen,<br>and the virtual voyage doesn't have /dev/fb0 framebuffer! of course, also fbset won't work..<br>it seems like VMware tells Voyage about a very basic video hardware, and Voyage responds with a very basic-default video driver, with no framebuffer support (and no graphic crash also) <br><br>Can be a possibility to replicate / impose this use of a very basic-common video driver, <br>also into my real E350 environment ?<br><br>Strong thanks in advance to all of you,<br>best regards, <br>Marco<o:p></o:p></p></div></body></html>