From: <gl...@ds...> - 2005-09-05 08:11:55
Attachments:
XF86Config-4
XFree86.0.log
|
Hello everyone Trying to get the xserver (Knoppix 3.8 XFree86 4.3.0.1) over framebuffer. The hw is the following: 0000:00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) 0000:00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics Device (rev 02) (btw, why do I get 2?) If I try he intelfb kernel driver, I get intelfb: intelfb_init intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G chipsets intelfb: Version 0.9.2 intelfb: intelfb_setup intelfb: no options intelfb: intelfb_pci_register intelfb: fb aperture: 0xd8000000/0x8000000, MMIO region: 0xe8180000/0x80000 intelfb: 00:02.0: Intel(R) 855GME, aperture size 128MB, stolen memory 32636kB intelfb: fb: 0xdb012000(+ 0x3012)/0x400000 (0xd1992000) intelfb: MMIO: 0xe8180000/0x80000 (0xd1e00000) intelfb: ring buffer: 0xdb001000/0x10000 (0xd1981000) intelfb: HW cursor: 0xdd24000/0x1000 (0xd1991000) (offset 0x3011) (phys 0xdd24000) intelfb: options: vram = 4, accel = 1, hwcursor = 1, fixed = 0, noinit = 0 intelfb: options: mode = "" intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode switching. intelfb: Video mode must be programmed at boot time. intelfb: cleanup I tried setting "vga=..." - no way. With vga16fb I can boot with the framebuffer, i.e. it will be used by the console, but I cannot get X running over it. I can run it over i810 X driver, but I need fb... XF86Config-4 (BusID under "Card1" is just a test - tried without any too) and XFree86.0.log attached. BTW, the reason why I want to run X over fb is, that I need to use touchscreen, about which I read in a HowTo, that it only works if X runs over fb, is it still true? Any hints would be greatly appreciated Thanks in advance Guennadi --------------------------------- Guennadi Liakhovetski, Ph.D. DSA Daten- und Systemtechnik GmbH Pascalstr. 28 D-52076 Aachen Germany |
From: Antonino A. D. <ad...@gm...> - 2005-09-05 11:09:16
|
gl...@ds... wrote: > Hello everyone > > Trying to get the xserver (Knoppix 3.8 XFree86 4.3.0.1) over > framebuffer. The hw is the following: > > 0000:00:02.0 VGA compatible controller: Intel Corp. 82852/855GM > Integrated Graphics Device (rev 02) > 0000:00:02.1 Display controller: Intel Corp. 82852/855GM Integrated > Graphics Device (rev 02) > > (btw, why do I get 2?) If I try he intelfb kernel driver, I get > > intelfb: intelfb_init > intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G > chipsets > intelfb: Version 0.9.2 > intelfb: intelfb_setup > intelfb: no options > intelfb: intelfb_pci_register > intelfb: fb aperture: 0xd8000000/0x8000000, MMIO region: 0xe8180000/0x80000 > intelfb: 00:02.0: Intel(R) 855GME, aperture size 128MB, stolen memory > 32636kB > intelfb: fb: 0xdb012000(+ 0x3012)/0x400000 (0xd1992000) > intelfb: MMIO: 0xe8180000/0x80000 (0xd1e00000) > intelfb: ring buffer: 0xdb001000/0x10000 (0xd1981000) > intelfb: HW cursor: 0xdd24000/0x1000 (0xd1991000) (offset 0x3011) (phys > 0xdd24000) > intelfb: options: vram = 4, accel = 1, hwcursor = 1, fixed = 0, noinit = 0 > intelfb: options: mode = "" > intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode > switching. > intelfb: Video mode must be programmed at boot time. > intelfb: cleanup > > I tried setting "vga=..." - no way. With vga16fb I can boot with the Try vga=ask. Then choose from those options until you get a framebuffer, vesafb or intelfb. > framebuffer, i.e. it will be used by the console, but I cannot get X > running over it. I can run it over i810 X driver, but I need fb... Default vga16fb mode is planar, and I don't believe X supports that yet. Tony |
From: <gl...@ds...> - 2005-09-05 11:25:41
|
Hi and thanks for the reply On Mon, 5 Sep 2005, Antonino A. Daplas wrote: >> I tried setting "vga=..." - no way. With vga16fb I can boot with the > > Try vga=ask. Then choose from those options until you get a framebuffer, > vesafb or intelfb. Hm, did try that, but will try again. >> framebuffer, i.e. it will be used by the console, but I cannot get X >> running over it. I can run it over i810 X driver, but I need fb... > > Default vga16fb mode is planar, and I don't believe X supports that yet. "default" - you mean, I can switch it to another mode? A brief look through Documentation/fb / fbdev.c didn't reveal any useful info. I tried vesafb shortly too - to no awail... Thanks Guennadi --------------------------------- Guennadi Liakhovetski, Ph.D. DSA Daten- und Systemtechnik GmbH Pascalstr. 28 D-52076 Aachen Germany |
From: <gl...@ds...> - 2005-09-05 12:30:37
|
On Mon, 5 Sep 2005, gl...@ds... wrote: > On Mon, 5 Sep 2005, Antonino A. Daplas wrote: > >>> I tried setting "vga=..." - no way. With vga16fb I can boot with the >> >> Try vga=ask. Then choose from those options until you get a framebuffer, >> vesafb or intelfb. > > Hm, did try that, but will try again. Just tried all (reasonable) options - no success. Thanks Guennadi --------------------------------- Guennadi Liakhovetski, Ph.D. DSA Daten- und Systemtechnik GmbH Pascalstr. 28 D-52076 Aachen Germany |
From: <gl...@ds...> - 2005-09-05 15:23:51
|
As a follow-up to the previous thread, but not hardware-specific: where is the screen_info.orig_video_isVGA variable set and is it user-settable? Actually, is the test if (FIXED_MODE(dinfo) && ORIG_VIDEO_ISVGA != VIDEO_TYPE_VLFB) { ERR_MSG("Video mode must be programmed at boot time.\n"); cleanup(dinfo); return -ENODEV; } in intelfbdev.c (2.6.13) correct? (ok, this one is hardware-specific, maybe). Thanks Guennadi --------------------------------- Guennadi Liakhovetski, Ph.D. DSA Daten- und Systemtechnik GmbH Pascalstr. 28 D-52076 Aachen Germany |
From: Antonino A. D. <ad...@gm...> - 2005-09-06 01:02:40
|
gl...@ds... wrote: > As a follow-up to the previous thread, but not hardware-specific: where > is the screen_info.orig_video_isVGA variable set and is it user-settable? > This is set in arch/i386/boot/video.S with the vga= parameter. VIDEO_TYPE_VLFB is VESA graphics mode. Tony |
From: Antonino A. D. <ad...@gm...> - 2005-09-06 01:29:38
|
gl...@ds... wrote: >> >> Default vga16fb mode is planar, and I don't believe X supports that yet. > > "default" - you mean, I can switch it to another mode? A brief look > through Documentation/fb / fbdev.c didn't reveal any useful info. > Yes, the vga16fb code does support packed-pixel mode. You have to do an fbset -nonstd true. But I haven't checked this functionality yet, it probably depends on the hardware, probably works in 2.4, but I'm not sure in 2.6. Tony |
From: James L. <ja...@ak...> - 2005-09-06 08:00:44
|
EZFB has an example touch screen application that has nothing to do with X. It reads directly from the touch screen device and translates coordinates from the physical touch screen to the visible frame buffer resolution. http://www.akrobiz.com/ezfb/ Look at "tsc" James. :o) ----- Original Message ----- From: <gl...@ds...> To: <lin...@li...> Sent: Monday, September 05, 2005 4:11 AM Subject: [Linux-fbdev-users] X over fb: "EGA/VGA planes are not yet supported by the fbdev driver [1]" > Hello everyone > > Trying to get the xserver (Knoppix 3.8 XFree86 4.3.0.1) over framebuffer. > The hw is the following: > > 0000:00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated > Graphics Device (rev 02) > 0000:00:02.1 Display controller: Intel Corp. 82852/855GM Integrated > Graphics Device (rev 02) > > (btw, why do I get 2?) If I try he intelfb kernel driver, I get > > intelfb: intelfb_init > intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G chipsets > intelfb: Version 0.9.2 > intelfb: intelfb_setup > intelfb: no options > intelfb: intelfb_pci_register > intelfb: fb aperture: 0xd8000000/0x8000000, MMIO region: 0xe8180000/0x80000 > intelfb: 00:02.0: Intel(R) 855GME, aperture size 128MB, stolen memory 32636kB > intelfb: fb: 0xdb012000(+ 0x3012)/0x400000 (0xd1992000) > intelfb: MMIO: 0xe8180000/0x80000 (0xd1e00000) > intelfb: ring buffer: 0xdb001000/0x10000 (0xd1981000) > intelfb: HW cursor: 0xdd24000/0x1000 (0xd1991000) (offset 0x3011) (phys 0xdd24000) > intelfb: options: vram = 4, accel = 1, hwcursor = 1, fixed = 0, noinit = 0 > intelfb: options: mode = "" > intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode switching. > intelfb: Video mode must be programmed at boot time. > intelfb: cleanup > > I tried setting "vga=..." - no way. With vga16fb I can boot with the > framebuffer, i.e. it will be used by the console, but I cannot get X > running over it. I can run it over i810 X driver, but I need fb... > XF86Config-4 (BusID under "Card1" is just a test - tried without any too) > and XFree86.0.log attached. > > BTW, the reason why I want to run X over fb is, that I need to use > touchscreen, about which I read in a HowTo, that it only works if X runs > over fb, is it still true? > > Any hints would be greatly appreciated > Thanks in advance > Guennadi > --------------------------------- > Guennadi Liakhovetski, Ph.D. > DSA Daten- und Systemtechnik GmbH > Pascalstr. 28 > D-52076 Aachen > Germany |
From: <gl...@ds...> - 2005-09-06 09:23:10
|
On Tue, 6 Sep 2005, James Lehman wrote: > EZFB has an example touch screen application that has nothing to do with X. > It reads directly from the touch screen device and translates coordinates > from the physical touch screen to the visible frame buffer resolution. > > http://www.akrobiz.com/ezfb/ > > Look at "tsc" Thanks, James. I'll have a look, although, I think, we really need a complete support for the touchscreen as an input device. Thanks Guennadi --------------------------------- Guennadi Liakhovetski, Ph.D. DSA Daten- und Systemtechnik GmbH Pascalstr. 28 D-52076 Aachen Germany |