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<br>