it's almost umbelivable, but it's in front of my eyes :-) > as i formerly wrote , i tried daily build 20110916 , and reported no > changed behaviour, in my local console graphic crash.. > > yesterday i discovered the official 0.8 release :-) > so i plugged keyb mice and monitor to my htpc , for the last disk cloning > before new release, > forgot to enter the bios, Voyage started and...HEY, IT WORKS ! O_o > > local console is no more crashing! > it ever stays into a real 80x25 text environment, never switch to > simil-char graphic console, and i don't have /dev/fb0 anymore... > > i don't exactly know what i did (except that all my attempts were reported > here) i presume the attempt to install ATI driver, which crashed early for > lack of an X server... > > i will check with a fresh official 0.8 release :-) > > > 2011/9/16 Kim-man 'Punky' TSE <[email protected]> > >> Hi Marco, >> >> I would recommend you to try out the daily MPD to see if the problem is >> resolved. If not, I will try if there are further work to do for this >> before 0.8.0 is released. >> >> Regards, >> Punky >> >> >> On 9/16/2011 12:32 AM, mad qwerty wrote: >> >>> Hi list, it's my first post here.. >>> 1st of all, HUGE Thanks to Punky-tse and all contributors for this GREAT >>> project :-) >>> >>> i'm very rookie with Linux in general, so i anticipate my excuses, >>> try to be more simple as possible, when helping me (thanks in advance) >>> >>> I'm using Voyage MPD 0.7.5 onto an AMD E-350 platform (exactly this : >>> http://www.asus.com/**Motherboards/AMD_CPU_on_Board/**E35M1I_DELUXE/<http://www.asus.com/Motherboards/AMD_CPU_on_Board/E35M1I_DELUXE/>) >>> and had some tests on different notebooks, and VMware. >>> >>> 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) >>> 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. >>> >>> This operation goes OK on older notebooks, >>> but into an almost-modern HP EliteBook 6930p, and into my reference >>> platform (AMD E350) this operation leads to a graphic failure, >>> screen filled of random pixels, and there's no way to get local console >>> resetting or working, >>> i can't switch tty virtual consoles, nor "clear" or "clear_console" >>> commands reset this crash. >>> >>> SSH sessions via IP connection are available, as Voyage continues to >>> boot without worries. >>> >>> i searched info by googling the web : >>> - similar problem here : 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%7Ett%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%7Ett%**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%7Ett%2Fjournal%2F531820&act=url>> >>> but no solution provided (if i well understood the translation) >>> - AMD driver doesn't install because it needs an X server ( >>> http://forums.amd.com/forum/**messageview.cfm?catid=390&** >>> threadid=145785<http://forums.amd.com/forum/messageview.cfm?catid=390&threadid=145785>< >>> http://forums.amd.com/forum/**messageview.cfm?catid=390&** >>> threadid=145785<http://forums.amd.com/forum/messageview.cfm?catid=390&threadid=145785>> >>> ) >>> >>> - 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 >>> - 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) >>> >>> can someone help me, >>> is there a way to avoid this "simil-tex" switch, and remain into a real >>> 80x25 text console, >>> or where i can control and set this graphic "simil-text" behaviour ? >>> >>> another curious thing : >>> 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, >>> and the virtual voyage doesn't have /dev/fb0 framebuffer! of course, >>> also fbset won't work.. >>> 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) >>> >>> Can be a possibility to replicate / impose this use of a very >>> basic-common video driver, >>> also into my real E350 environment ? >>> >>> Strong thanks in advance to all of you, >>> best regards, >>> Marco >>> >>> >>> ______________________________**_________________ >>> Voyage-linux mailing list >>> [email protected] >>> http://list.voyage.hk/mailman/**listinfo/voyage-linux<http://list.voyage.hk/mailman/listinfo/voyage-linux> >>> >> >> >> -- >> Regards, >> Kim-man "Punky" Tse >> >> * Open Source Embedded Solutions and Systems >> - Voyage Linux (http://linux.voyage.hk) >> - Voyage ONE >> (http://linux.voyage.hk/**voyage-one<http://linux.voyage.hk/voyage-one> >> ) >> - Voyage MPD >> (http://linux.voyage.hk/**voyage-mpd<http://linux.voyage.hk/voyage-mpd> >> ) >> * Voyage Store (http://store.voyage.hk) >> >> >> >
_______________________________________________ Voyage-linux mailing list [email protected] http://list.voyage.hk/mailman/listinfo/voyage-linux
