[Voyage-linux] Howto get Framebuffer working

Kim-man 'Punky' TSE (spam-protected)
Thu Nov 13 09:26:27 HKT 2008


Hi all,

I have updated the kernel with proper settings.  Framebuffer console 
should work now.  You can find the latest kernel in:

    
http://www.voyage.hk/dists/experimental/linux/linux-image-2.6.26-486-voyage_6.0-1_i386.deb

voyage-lenny distro and live-cd are updated as well.

Please test and feedback

Regards,
Punky



Kim-man 'Punky' TSE wrote:
> Hi all,
>
> There had been reported problem on the framebuffer support in voyage.  
> But I am quite suere lxfb.ko should be included in 0.5.2 and lenny 
> release.
>
> You may find the documentation of lxfb in the link below
>    http://lxr.linux.no/linux+v2.6.26.7/Documentation/fb/lxfb.txt
>
> You can also run "modinfo lxfb" to see the support module parameters.
> If anyone in the list has successful story in using the framebuffer or 
> X with ALIX, please share your experience with us.  Of course, I would 
> want to get the framebuffer issue sorted out before 0.6.0 release.
>
> Regards,
> Punky
>
>
> Rainer Stratmann wrote:
>> Hello Richard,
>>
>> the framebuffer works for me if I use a Knoppix Kernel!
>> May be this is not an elegant solution, but it works for me.
>>
>> Also you have to chmod /dev/fb0 somewhere in thee bootprocess (for 
>> example in rc.local) in order to have the accessrights to the 
>> framebuffer.
>>
>> Rainer
>>
>> Am Mittwoch, 22. Oktober 2008 20:28 schrieb Richard Urwin:
>>  
>>> I have an ALIX 3C3, and it's running voyage-lenny well. I would be 
>>> happy to
>>> downgrade to stable if that is my problem.
>>>
>>> This project is to build a, frankly over-engineered, digital 
>>> photo-frame.
>>>
>>> I've done some reading, and I think I need to either use framebuffer 
>>> or X.
>>>
>>> I don't need X - I think I can do everything with just a 
>>> command-line and
>>> framebuffer.
>>>
>>> I tried adding the lxfb module, but got a black screen with green 
>>> lines. Us
>>> old-timers recognise this as the monitor in graphics mode and the OS 
>>> still
>>> thinking it's in character mode. I've tried adding vga=785 to the boot
>>> command, and got a simple black screen (much earlier in the boot.)
>>>
>>> I think I need to enable this in the kernel, but it will be the 
>>> first one
>>> I've ever built, and I don't have any clear idea what I'm supposed 
>>> to do to
>>> it. I notice that back in May someone posted a kernel with framebuffer
>>> enabled, but it seems to have disappeared now.
>>>
>>> Complications: My other machine is an AMD64x2, in native mode, so not a
>>> truly similar environment. It's running Hardy Heron. Until a bigger 
>>> CF card
>>> arrives I'm limited to 256MB on the ALIX. It's never going to be huge.
>>> Although maybe I could use USB memory sticks to extend this, or use 
>>> an NFS
>>> share to the big machine.
>>>
>>> Questions: What is the least I have to do to a stock voyage-linux to 
>>> get a
>>> useable framebuffer? If I need to build the kernel, what is the best
>>> machine to do it on, the Hardy one, or the ALIX?
>>>
>>> TIA
>>>     
>>
>> _______________________________________________
>> Voyage-linux mailing list
>> Voyage-linux at list.voyage.hk
>> http://list.voyage.hk/mailman/listinfo/voyage-linux
>>   
>
>


-- 
Regards,
Punky

Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
  - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
  - Network Engineering, Development Platform and Consultation
  
	





More information about the Voyage-linux mailing list