hi, I'm sorry to trouble you,but I have a question with X server when start l4linux on dope. I have search a mail which you have sent:
Yes, I know that this setup is not easy. For overlay_wm driver to work it is necessary to apply patches to X Server sources, as I read. But I thought it must work with linux server with ordinary l4con/dope frambuffer driver. So, it won't, ok. -- When I checked on real machine (not with ramdisk), l4linux started and XServer starts OK.
I can start l4linux on dope and con,and also on serial console.The below is what I use in l4linux.cfg:
task "vmlinuz" "earlyprintk=yes mem=64M video=l4fb root=/dev/hda9 " all_sects_writable allow_vga allow_cli could you please tell me what I missing? thank you.
sorry for not putting the error message: (EE) VESA(0): No V_BIOS found. (EE)Screen(s) found, but none have a usable configureation. Fatal server error: no screen found
In my debian system,I have a gome desktop environment, and the vesa driver for the card.
thank you:)
2009/7/19 fang zhengshu fangzhsh07@gmail.com
hi, I'm sorry to trouble you,but I have a question with X server when start l4linux on dope. I have search a mail which you have sent:
Yes, I know that this setup is not easy. For overlay_wm driver to work it is necessary to apply
patches to X Server sources, as I read. But I thought it must work with linux server with ordinary l4con/dope frambuffer driver. So, it won't, ok. -- When I checked on real machine (not with ramdisk), l4linux started and XServer starts OK.
I can start l4linux on dope and con,and also on serial console.The below is what I use in l4linux.cfg:
task "vmlinuz" "earlyprintk=yes mem=64M video=l4fb root=/dev/hda9 " all_sects_writable allow_vga allow_cli could you please tell me what I missing? thank you. -- fang,
On Sun Jul 19, 2009 at 22:27:39 +0800, fang zhengshu wrote:
sorry for not putting the error message: (EE) VESA(0): No V_BIOS found. (EE)Screen(s) found, but none have a usable configureation. Fatal server error: no screen found
In my debian system,I have a gome desktop environment, and the vesa driver for the card.
thank you:)
You need to use the 'fbdev' driver in your X config. VESA is for the real screen, fbdev is for the frame-buffer.
Adam
l4-hackers@os.inf.tu-dresden.de