On 06/12/2015 01:12, Marcelo Ricardo Leitner wrote:
Em 05-12-2015 05:35, Duncan Brown escreveu:
On 04/12/2015 19:17, Marcelo Ricardo Leitner wrote:
Em 03-12-2015 14:46, Duncan Brown escreveu:
Here is a couple of pictures,
http://i.imgur.com/Vqvqn1H.jpg http://i.imgur.com/WQaz1j9.png
Any use?
Of some. It's failing on ftrace initialization while allocating memory, but can't know the real reason. It can be just lack of memory or any other bug.
Probably by that stage of the boot, framebuffer is already loaded. Use vga=0x317 boot option to get a bigger resolution and more lines on it, then send another pic.
I hope it fits this time. If not, pick 0x31A, if your monitor allows.
(kernel src, Documentation/fb/vesafb.txt) | 640x480 800x600 1024x768 1280x1024 ----+------------------------------------- 256 | 0x301 0x303 0x305 0x307 32k | 0x310 0x313 0x316 0x319 64k | 0x311 0x314 0x317 0x31A 16M | 0x312 0x315 0x318 0x31B
Marcelo
Hi Marcelo
Thanks for the suggestion
I've worked through a decent selection and cant get any to show a higher resolution than it's currently at, in fact most just leave me with a blank screen
Note I can change the resolution all I want if I boot via the previous kernel
Damn :-( Serial cable then? heh
Cheers, Marcelo
Yeah I've got a nice little usb one I can hook directly into a raspberry pi on the way
I'm totally expecting this to get fixed in a kernel update before the thing even arrives, but it'll be a good learning experience and will probably be useful in the future!