Menu
▾
▴
linux-fbdev-users — Generic mailing list for users of frame buffers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(9) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(12) |
Feb
(10) |
Mar
|
Apr
(5) |
May
(3) |
Jun
|
Jul
(5) |
Aug
(7) |
Sep
(15) |
Oct
(4) |
Nov
(3) |
Dec
(7) |
| 2003 |
Jan
(5) |
Feb
(30) |
Mar
(5) |
Apr
(13) |
May
(12) |
Jun
(11) |
Jul
(1) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(7) |
| 2004 |
Jan
(4) |
Feb
(9) |
Mar
(16) |
Apr
(42) |
May
(5) |
Jun
(11) |
Jul
(3) |
Aug
(39) |
Sep
(5) |
Oct
(32) |
Nov
(27) |
Dec
|
| 2005 |
Jan
(11) |
Feb
(8) |
Mar
(22) |
Apr
(26) |
May
(9) |
Jun
(10) |
Jul
(7) |
Aug
(43) |
Sep
(23) |
Oct
(18) |
Nov
(15) |
Dec
(15) |
| 2006 |
Jan
(7) |
Feb
(16) |
Mar
(10) |
Apr
(1) |
May
(16) |
Jun
(8) |
Jul
(3) |
Aug
(35) |
Sep
(7) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
| 2007 |
Jan
(2) |
Feb
(30) |
Mar
(6) |
Apr
(7) |
May
(5) |
Jun
|
Jul
(15) |
Aug
(12) |
Sep
(22) |
Oct
(48) |
Nov
(9) |
Dec
(7) |
| 2008 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(4) |
Jun
(1) |
Jul
(5) |
Aug
(4) |
Sep
(4) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
| 2009 |
Jan
(3) |
Feb
|
Mar
|
Apr
(4) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(2) |
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: p <p...@jc...> - 2007-07-25 16:38:14
|
Hi all, this is my first post to the mailing list, so 'please handle with care' ;) I already tried the xen mailing lists and the irc chan, but nobody was able to help me. I a trying to get a framebuffer device in the dom0, but unfortunately the screen keeps black (the system is still booting and accessible through network). Tried it with Xen 3.04, 3.1 and current unstable tree on Debian Etch and Ubuntu 7.04. Tried it with module support and build-in (fb support, device drivers - both vesafb and radeonfb, and fbcon) The results had just been the same. Anyone already tried it or perhaps interessted in it now? Kind Regards Philipp |
|
From: Goins P. <ast...@ho...> - 2007-07-23 19:46:31
|
>Okay, I'm pretty sure there was a patch a year ago that added the Radeon >Xpress 1100 device id to the table. But to be sure, what is the output >of lspci -n? 00:00.0 0600: 1002:5950 (rev 10) 00:01.0 0604: 1002:5a3f 00:04.0 0604: 1002:5a36 00:05.0 0604: 1002:5a37 00:12.0 0101: 1002:4379 (rev 80) 00:13.0 0c03: 1002:4374 (rev 80) 00:13.1 0c03: 1002:4375 (rev 80) 00:13.2 0c03: 1002:4373 (rev 80) 00:14.0 0c05: 1002:4372 (rev 83) 00:14.1 0101: 1002:4376 (rev 80) 00:14.2 0403: 1002:437b (rev 01) 00:14.3 0601: 1002:4377 (rev 80) 00:14.4 0604: 1002:4371 (rev 80) 00:18.0 0600: 1022:1100 00:18.1 0600: 1022:1101 00:18.2 0600: 1022:1102 00:18.3 0600: 1022:1103 01:05.0 0300: 1002:5975 06:01.0 0200: 10ec:8139 (rev 10) 06:02.0 0200: 168c:001a (rev 01) 06:04.0 0607: 1524:1412 (rev 10) 06:04.1 0501: 1524:0530 (rev 01) 06:04.2 0805: 1524:0550 (rev 01) 06:04.3 0501: 1524:0520 (rev 01) 06:04.4 0501: 1524:0551 (rev 01) - Paul _________________________________________________________________ できる人は使っている！メッセンジャー×お仕事 活用術 http://messenger.live.jp/oshigoto/index.htm |
|
From: Antonino A. D. <ad...@gm...> - 2007-07-23 13:57:41
|
On Mon, 2007-07-23 at 18:28 +0900, Goins Paul wrote: > Done. Started without kdm at boot time. fglrx did not load and no longer > shows up on 'ls -l /sys/bus/pci/devices/0000:01:05.0/driver' - nothing > does. However, radeonfb still is dying silently. > Okay, I'm pretty sure there was a patch a year ago that added the Radeon Xpress 1100 device id to the table. But to be sure, what is the output of lspci -n? Tony |
|
From: Goins P. <ast...@ho...> - 2007-07-23 09:49:31
|
Done. Started without kdm at boot time. fglrx did not load and no longer shows up on 'ls -l /sys/bus/pci/devices/0000:01:05.0/driver' - nothing does. However, radeonfb still is dying silently. I forgot to upload my kernel config file on the last post, so I've attached it to this one. Apologies for not having it all together the first time. - Paul >From: "Antonino A. Daplas" <ad...@gm...> >To: lin...@li... >CC: Goins Paul <ast...@ho...> >Subject: Re: [Linux-fbdev-users] Problems running radeonfb on RadeonXpress1100 with 2.6. >Date: Mon, 23 Jul 2007 16:51:05 +0800 > >On Mon, 2007-07-23 at 16:40 +0900, Goins Paul wrote: > > Sure. The files are attached. Thanks. > >It seems that fglrx is already driving your card, so radeonfb fails >silently. > >Try removing the fglrx module, then load radeonfb > >Tony > _________________________________________________________________ スムーズな検索機能や役立つ最新情報を無料でフルに活用できるMSN版IE7をダウン ロード http://promotion.msn.co.jp/ie7/ |
|
From: Antonino A. D. <ad...@gm...> - 2007-07-23 08:51:55
|
On Mon, 2007-07-23 at 16:40 +0900, Goins Paul wrote: > Sure. The files are attached. Thanks. It seems that fglrx is already driving your card, so radeonfb fails silently. Try removing the fglrx module, then load radeonfb Tony |
|
From: Goins P. <ast...@ho...> - 2007-07-23 07:40:54
|
Sure. The files are attached. Thanks. - Paul _________________________________________________________________ マドンナ、レッチリ、リンキンパーク、ポリス他、LIVE EARTHのコンサート映像を無 料配信中！ http://liveearth.jp.msn.com/ |
|
From: Antonino A. D. <ad...@gm...> - 2007-07-23 06:31:23
|
On Mon, 2007-07-23 at 13:55 +0900, Goins Paul wrote: > I've posted this question on the Debian forums but have not got a response, > so I thought I'd go to the next level and ask here. > > I'm having trouble getting the radeonfb framebuffer device to work. I'm > running a Radeon Xpress 1100 integrated graphics card on a 1280x800 laptop > display. I'm running Debian Unstable using a 2.6.21 kernel, and I know for > a fact the kernel module is built, and I can even get it to load using > modprobe. > > If I boot with a "video=radeonfb" or "video=radeonfb:1280x800-32@60" > option, nothing seems to happen differently - no framebuffer is loaded. > Alternatively, if I do a modprobe on the module, I can load it. However, > this doesn't seem to enable a framebuffer. Nothing shows up under /proc/fb > or anything like that. Is there something I'm missing here? > > For full details, please take a look at my post here: > http://forums.debian.net/viewtopic.php?t=17216 Can you post your dmesg, kernel config, and the output of 'cat /proc/iomem' and 'ls -l /sys/bus/pci/devices/0000:01:05.0/driver' Tony |
|
From: Goins P. <ast...@ho...> - 2007-07-23 04:55:42
|
I've posted this question on the Debian forums but have not got a response, so I thought I'd go to the next level and ask here. I'm having trouble getting the radeonfb framebuffer device to work. I'm running a Radeon Xpress 1100 integrated graphics card on a 1280x800 laptop display. I'm running Debian Unstable using a 2.6.21 kernel, and I know for a fact the kernel module is built, and I can even get it to load using modprobe. If I boot with a "video=radeonfb" or "video=radeonfb:1280x800-32@60" option, nothing seems to happen differently - no framebuffer is loaded. Alternatively, if I do a modprobe on the module, I can load it. However, this doesn't seem to enable a framebuffer. Nothing shows up under /proc/fb or anything like that. Is there something I'm missing here? For full details, please take a look at my post here: http://forums.debian.net/viewtopic.php?t=17216 Thanks for any help you can provide. - Paul Goins _________________________________________________________________ できる人は使っている！メッセンジャー×お仕事 活用術 http://messenger.live.jp/oshigoto/index.htm |
|
From: Antonino A. D. <ad...@gm...> - 2007-07-17 11:26:04
|
On Mon, 2007-07-16 at 14:44 -0400, Mike Sharov wrote: > I am wondering if there is a way to set the hardware mouse cursor from > userspace. I can see the code in the drivers (fb_cursor), but I can't > find any way to get to it. Is FBIO_CURSOR ioctl supposed to do it? The ioctl is there but it's unimplemented. In short, no you can't (yet). Tony |
|
From: Mike S. <ms...@so...> - 2007-07-16 18:44:34
|
I am wondering if there is a way to set the hardware mouse cursor from userspace. I can see the code in the drivers (fb_cursor), but I can't find any way to get to it. Is FBIO_CURSOR ioctl supposed to do it? -- Mike ms...@us... |
|
From: Arvid B. <ar...@kt...> - 2007-07-12 09:45:02
|
On 2007-07-11 14:45, Stephan Diestelhorst wrote: >> I've been trying for a day now to get any kind of framebuffer support on my >> computer, with mainly two outcomes: > > You could probably try vesafb-tng / uvesafb, it has some more features than > standard vesafb. > > See http://dev.gentoo.org/~spock/projects/vesafb-tng/ and > http://dev.gentoo.org/~spock/projects/uvesafb/ > > Don't know if that helps, but it might be worth a shot! > > Stephan > Thanks. I checked out the install instructions for uvesafb (I can't run vesafb-tng since I'm on a x86_64 system), and it seems quite involved. Also, since both vesafb and radeonfb fails I'm thinking the chances of another vesa driver working is slim. Perhaps I'll try a graphic card BIOS upgrade instead, or else just await some kind of answer by a developer to my bug report(s) before doing anything else. Arvid |
|
From: Stephan D. <dr...@fr...> - 2007-07-11 12:45:36
|
> I've been trying for a day now to get any kind of framebuffer support on my > computer, with mainly two outcomes: You could probably try vesafb-tng / uvesafb, it has some more features than standard vesafb. See http://dev.gentoo.org/~spock/projects/vesafb-tng/ and http://dev.gentoo.org/~spock/projects/uvesafb/ Don't know if that helps, but it might be worth a shot! Stephan |
|
From: Arvid B. <ar...@kt...> - 2007-07-10 17:29:49
|
Hi,
I've been trying for a day now to get any kind of framebuffer support on my computer, with mainly two outcomes:
1) If I configure my kernel with Device drivers -> Graphics support -> Console display driver support -> <*> Framebuffer Console support, the system hangs on boot, with a black screen, without writing any logs. If I use the vesafb it seems it hangs very early in the boot process, after writing only a few lines of text. If I use radeonfb it hangs later (but still before mounting the disks).
2) If I configure my kernel without the above it boots (in normal text mode of course). If I then try to use /dev/fb0 (with fbi or GTK+ on DirectFB), all I get is a garbled text mode screen, with randomly colored random characters being printed in random locations on the screen.
I have configured my kernel with
Device drivers ->
Graphics support ->
<*> Support for frame buffer devices
<*> VESA VGA Graphics support
VESA driver type (vesafb) --->
<*> ATI Radeon display support
[*] DDC/I2C for ATI Radeon support
Console display driver support --->
<*> Framebuffer Console support
As indicated above, I have tried with and without Framebuffer Console support. I have also tried with vesafb and radeonfb exclusively.
I have tried kernel parameters
video=vesafb vga=0x318
video=vesafb vga=791
video=vesafb:ywrap,mtrr:3 vga=0x318
video=vesafb:ywrap,mtrr:2 vga=0x318
video=radeonfb:1024x768-24
video=radeonfb:1024x768
... with no difference in behaviour.
When I disable Framebuffer Console support and use the video=vesafb lines, no /dev/fb0 is created at all (and vesafb is not mentioned in dmesg). So I have only got outcome 2) above with video=radeonfb.
Although uname shows kernel 2.6.20 below, I actually started out with kernel 2.6.18 - there seems to be no difference regarding my framebuffer problem between the versions.
I am now at a loss of what to try next, so any advice is very much appreciated!
System info:
$ uname -a
Linux shuttle 2.6.20-gentoo-r8 #6 Tue Jul 10 14:05:30 CEST 2007 x86_64 AMD Athlon(tm) 64 Processor 3200+ AuthenticAMD GNU/Linux
$ sudo lspci
00:00.0 Host bridge: nVidia Corporation nForce3 250Gb Host Bridge (rev a1)
00:01.0 ISA bridge: nVidia Corporation nForce3 250Gb LPC Bridge (rev a2)
00:01.1 SMBus: nVidia Corporation nForce 250Gb PCI System Management (rev a1)
00:02.0 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.1 USB Controller: nVidia Corporation CK8S USB Controller (rev a1)
00:02.2 USB Controller: nVidia Corporation nForce3 EHCI USB 2.0 Controller (rev a2)
00:06.0 Multimedia audio controller: nVidia Corporation nForce3 250Gb AC'97 Audio Controller (rev a1)
00:08.0 IDE interface: nVidia Corporation CK8S Parallel ATA Controller (v2.5) (rev a2)
00:0a.0 IDE interface: nVidia Corporation CK8S Serial ATA Controller (v2.5) (rev a2)
00:0b.0 PCI bridge: nVidia Corporation nForce3 250Gb AGP Host to PCI Bridge (rev a2)
00:0e.0 PCI bridge: nVidia Corporation nForce3 250Gb PCI-to-PCI Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: ATI Technologies Inc R420 JI [Radeon X800PRO]
01:00.1 Display controller: ATI Technologies Inc Unknown device 4a69
02:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
02:08.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
Thanks,
Arvid
|
|
From: Bill G. <bg...@bi...> - 2007-05-21 03:32:18
|
Guys:
I'm using an SM501G8 on a PXA270, linux-2.6.21.1 kernel. I'm stuck with
this at boot:
[ 1.380000] sm501 sm501.0: SM501 At c181e000: Version 050100a0, 4 Mb,
IRQ 85
[ 1.410000] sm501 sm501.0: CurrentGate 00021807
[ 1.420000] sm501 sm501.0: CurrentClock 2a1a0a09
[ 1.440000] sm501 sm501.0: PowerModeControl 00000000
[ 1.450000] sm501-fb[0] flags 00000200: 13e80000..13e8ffff
[ 1.470000] sm501-fb[1] flags 00000200: 13f00000..13f4ffff
[ 1.480000] sm501-fb[2] flags 00000200: 10000000..103fffff
[ 1.500000] sm501-fb[3] flags 00000400: 00000055..00000055
[ 1.520000] sm501-fb.0: failed to claim resource 0
[ 1.530000] sm501 sm501.0: error registering sm501-fb (-16)
[ 1.550000] returning 0
My resource definition looks like this:
static struct resource sm501_device_resources[] = {
[0] = {.start = PXA_CS4_PHYS, .end = PXA_CS4_PHYS + (4 * 1024 * 1024) -
1, .flags = IORESOURCE_MEM,},
[1] = {.start = PXA_CS4_PHYS + 0x3e00000, .end = PXA_CS4_PHYS +
0x3e0fffff, .flags = IORESOURCE_MEM,},
[2] = {.start = IRQ_GPIO(53), .end = IRQ_GPIO(53), .flags =
IORESOURCE_IRQ,},
};
static struct platform_device sm501_device = {
.name = "sm501",
.id = 0,
.num_resources = ARRAY_SIZE(sm501_device_resources),
.resource = sm501_device_resources,
};
static struct platform_device *devices[] __initdata = {
&sm501_device,
...
};
platform_add_devices(devices, ARRAY_SIZE(devices));
All the above was gleaned from staring at the code in sm501.c, so I'm
probably doing something wrong. :) My theory right now is that I'm
not specifying the right ranges for the resources. For example, it
looks like I'm not supposed to resource _all_ the device's control
register memory, only a little bit (the code in sm501_register_display()
appears to grab the rest). But I haven't figured out what the right
combination of resources is...
Any suggestions? I'm not registering an "sm501-fb" device, only the
"sm501" device shown above.
b.g.
--
Bill Gatliff
bg...@bi...
|
|
From: Antonino A. D. <ad...@gm...> - 2007-05-04 19:52:36
|
On Fri, 2007-05-04 at 14:31 +0100, Matteo Vescovi wrote: > --- "Antonino A. Daplas" <ad...@gm...> wrote: > > > On Thu, 2007-05-03 at 16:57 -0400, DENNIS HALL > > wrote: > Tony, how much work would you say is required to add > mode setting capabilities to the intelfb driver? Documentation, basically. > I > might be able to donate some time to get this > working... it really bugs me that I can't use the > display at the native 1280x800 resolution. Dave Airlie is the current maintainer of intelfb and DRM. AFAIK, he has preliminary code for this but he hasn't released any of it yet. Tony |
|
From: Matteo V. <mat...@ya...> - 2007-05-04 13:31:41
|
--- "Antonino A. Daplas" <ad...@gm...> wrote: > On Thu, 2007-05-03 at 16:57 -0400, DENNIS HALL > wrote: > > The DirectFB driver for this card (intelfb) > complains about the video > > mode not being set even though I've set it using > the kernel parameters > > passed through grub: > > > > title Generic 2.6.21 with 945GM-21 > > root (hd0,0) > > kernel /bzImage945-21 root=/dev/hda3 > > > video=intelfb:mode=1024x768-16@85,accel=1,hwcursor=1,vram=8 > > > > The parameters above are listed in the kernel's fb > documentation > > (Documentation/fb/intelfb.txt). Does anyone know > why this is > > happening or how to fix it? > > > > Agp Info: > > Linux agpgart interface v0.102 (c) Dave Jones > > agpgart: Detected an Intel 945GM Chipset. > > agpgart: Detected 7932K stolen memory. > > agpgart: AGP aperture is 256M @ 0xd0000000 > > > > IntelFB Info: > > intelfb: intelfb_init > > intelfb: Framebuffer driver for Intel(R) > > 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM > chipsets > > intelfb: Version 0.9.4 > > intelfb: intelfb_setup > > intelfb: options: > mode=1024x768-16@85,accel=1,hwcursor=1,vram=8 > > intelfb: intelfb_pci_register > > intelfb: fb aperture: 0xd0000000/0x10000000, MMIO > region: > > 0xeff00000/0x80000 > > intelfb: 00:02.0: Intel(R) 945GM, aperture size > 256MB, stolen memory > > 7932kB > > intelfb: fb: 0xd3012000(+ 0x3012)/0x800000 > (0xfba12000) > > intelfb: MMIO: 0xeff00000/0x80000 (0xff280000) > > intelfb: ring buffer: 0xd3001000/0x10000 > (0xfba01000) > > intelfb: HW cursor: 0x37fe8000/0x1000 (0xfba11000) > (offset 0x3011) > > (phys 0x37fe8000) > > intelfb: options: vram = 8, accel = 1, hwcursor = > 1, fixed = 0, noinit > > = 0 > > intelfb: options: mode = "1024x768-16@85" > > intelfb: Non-CRT device is enabled ( LVDS port ). > Disabling mode > > switching. > > intelfb: Video mode must be programmed at boot > time. > > intelfb: cleanup > > > > When I try this with a CRT instead of an LCD > screen the kernel crashes > > before I can see anything. > > > > The intelfb driver cannot set the mode on its own > without the help of > the BIOS. Use the vga= (as you would with vesafb) > instead to set the > mode. > > Tony > Hi, I had the same problem, and was bitten by the kernel's intelfb documentation the same way you were. I eventually settled for the following: kernel /boot/vmlinuz root=/dev/hda1 ro video=intelfb:mode=1024x768-32@75 vga=792 GRUB understands hex, so you can just say vga=0x318, and avoid converting it to the decimal like I did. Tony, how much work would you say is required to add mode setting capabilities to the intelfb driver? I might be able to donate some time to get this working... it really bugs me that I can't use the display at the native 1280x800 resolution. - Matteo ___________________________________________________________ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com |
|
From: Antonino A. D. <ad...@gm...> - 2007-05-04 06:32:31
|
On Thu, 2007-05-03 at 16:57 -0400, DENNIS HALL wrote: > The DirectFB driver for this card (intelfb) complains about the video > mode not being set even though I've set it using the kernel parameters > passed through grub: > > title Generic 2.6.21 with 945GM-21 > root (hd0,0) > kernel /bzImage945-21 root=/dev/hda3 > video=intelfb:mode=1024x768-16@85,accel=1,hwcursor=1,vram=8 > > The parameters above are listed in the kernel's fb documentation > (Documentation/fb/intelfb.txt). Does anyone know why this is > happening or how to fix it? > > Agp Info: > Linux agpgart interface v0.102 (c) Dave Jones > agpgart: Detected an Intel 945GM Chipset. > agpgart: Detected 7932K stolen memory. > agpgart: AGP aperture is 256M @ 0xd0000000 > > IntelFB Info: > intelfb: intelfb_init > intelfb: Framebuffer driver for Intel(R) > 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets > intelfb: Version 0.9.4 > intelfb: intelfb_setup > intelfb: options: mode=1024x768-16@85,accel=1,hwcursor=1,vram=8 > intelfb: intelfb_pci_register > intelfb: fb aperture: 0xd0000000/0x10000000, MMIO region: > 0xeff00000/0x80000 > intelfb: 00:02.0: Intel(R) 945GM, aperture size 256MB, stolen memory > 7932kB > intelfb: fb: 0xd3012000(+ 0x3012)/0x800000 (0xfba12000) > intelfb: MMIO: 0xeff00000/0x80000 (0xff280000) > intelfb: ring buffer: 0xd3001000/0x10000 (0xfba01000) > intelfb: HW cursor: 0x37fe8000/0x1000 (0xfba11000) (offset 0x3011) > (phys 0x37fe8000) > intelfb: options: vram = 8, accel = 1, hwcursor = 1, fixed = 0, noinit > = 0 > intelfb: options: mode = "1024x768-16@85" > intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode > switching. > intelfb: Video mode must be programmed at boot time. > intelfb: cleanup > > When I try this with a CRT instead of an LCD screen the kernel crashes > before I can see anything. > The intelfb driver cannot set the mode on its own without the help of the BIOS. Use the vga= (as you would with vesafb) instead to set the mode. Tony |
|
From: DENNIS H. <dh...@ro...> - 2007-05-03 20:57:56
|
The DirectFB driver for this card (intelfb) complains about the video mode not being set even though I've set it using the kernel parameters passed through grub:
title Generic 2.6.21 with 945GM-21
root (hd0,0)
kernel /bzImage945-21 root=/dev/hda3 video=intelfb:mode=1024x768-16@85,accel=1,hwcursor=1,vram=8
The parameters above are listed in the kernel's fb documentation (Documentation/fb/intelfb.txt). Does anyone know why this is happening or how to fix it?
Agp Info:
Linux agpgart interface v0.102 (c) Dave Jones
agpgart: Detected an Intel 945GM Chipset.
agpgart: Detected 7932K stolen memory.
agpgart: AGP aperture is 256M @ 0xd0000000
IntelFB Info:
intelfb: intelfb_init
intelfb: Framebuffer driver for Intel(R) 830M/845G/852GM/855GM/865G/915G/915GM/945G/945GM chipsets
intelfb: Version 0.9.4
intelfb: intelfb_setup
intelfb: options: mode=1024x768-16@85,accel=1,hwcursor=1,vram=8
intelfb: intelfb_pci_register
intelfb: fb aperture: 0xd0000000/0x10000000, MMIO region: 0xeff00000/0x80000
intelfb: 00:02.0: Intel(R) 945GM, aperture size 256MB, stolen memory 7932kB
intelfb: fb: 0xd3012000(+ 0x3012)/0x800000 (0xfba12000)
intelfb: MMIO: 0xeff00000/0x80000 (0xff280000)
intelfb: ring buffer: 0xd3001000/0x10000 (0xfba01000)
intelfb: HW cursor: 0x37fe8000/0x1000 (0xfba11000) (offset 0x3011) (phys 0x37fe8000)
intelfb: options: vram = 8, accel = 1, hwcursor = 1, fixed = 0, noinit = 0
intelfb: options: mode = "1024x768-16@85"
intelfb: Non-CRT device is enabled ( LVDS port ). Disabling mode switching.
intelfb: Video mode must be programmed at boot time.
intelfb: cleanup
When I try this with a CRT instead of an LCD screen the kernel crashes before I can see anything.
Regards,
D.Hall
|
|
From: Stephan D. <dr...@fr...> - 2007-04-22 20:55:46
|
> Please post the boot messages from atyfb so I can > confirm that your case is similar. Kernel command line: root=/dev/hda3 resume=/dev/hda1 video=atyfb:xclk:63 atyfb: using auxiliary register aperture atyfb: 3D RAGE Mobility P/M (Mach64 LR, PCI) [0x4c52 rev 0x64] atyfb: Mach64 BIOS is located at c0000, mapped at c00c0000. atyfb: BIOS frequency table: atyfb: PCLK_min_freq 984, PCLK_max_freq 23600, ref_freq 2950, ref_divider 64 atyfb: MCLK_pwd 4200, MCLK_max_freq 8300, XCLK_max_freq 12500, SCLK_freq 5000 atyfb: BIOS contains driver information table. atyfb: colour active matrix monitor detected: 1024x512 Wide TFT Panel atyfb: id=7, 1024x512 pixels, 262144 colours (LT mode) atyfb: supports refresh rates [60], default 60 Hz atyfb: LCD CRTC parameters: 39.1795 1024 1032 1120 1184 512 513 527 550 atyfb: : 25595 64 1024 8 88 23 512 1 14 atyfb: 4M SDRAM (2:1) (32-bit), 29.498928 MHz XTAL, 236 MHz PLL, 83 Mhz MCLK, 63 MHz XCLK atyfb: fb0: ATY Mach64 frame buffer device on PCI As already mentioned, works flawlessly with full resolution now! > > Where can I find proper docs for the driver? (In > > the usual place aka. the source?) > > Yes. I should have guessed ;) I was fooled by the aty128fb.txt docs in kernel-source Documentation/fb/ Thanks, Stephan |
|
From: Ville <sy...@sc...> - 2007-04-22 19:19:45
|
On Sun, Apr 22, 2007 at 08:13:19PM +0200, Stephan Diestelhorst wrote: > > > With the panels native resolution of 1024x512, I can see that the screen > > > is initialised properly (to the full resolution), but consists only of > > > white on-pixel-wide vertical stripes. Some sort of blinking in the area > > > of the curser is also visible. > > > > Try booting with video=atyfb:xclk:63. > > Thanks, that helps partly! I can see a proper picture, however just in the > left 2/3 of the screen, I guess that is 640x480. It is also slightly shifted > downward. What does xclk do? It sets the memory clock to 63 MHz. Typically the BIOS tables specify 125 MHz, but for some laptops that's too much. There have been a few reports about laptops with 32bit memory interfaces that require halved XCLK (I had one). Please post the boot messages from atyfb so I can confirm that your case is similar. > Where can I find proper docs for the driver? (In > the usual place aka. the source?) Yes. -- Ville Syrjälä sy...@sc... http://www.sci.fi/~syrjala/ |
|
From: Stephan D. <dr...@fr...> - 2007-04-22 18:13:22
|
> > With the panels native resolution of 1024x512, I can see that the screen > > is initialised properly (to the full resolution), but consists only of > > white on-pixel-wide vertical stripes. Some sort of blinking in the area > > of the curser is also visible. > > Try booting with video=atyfb:xclk:63. Thanks, that helps partly! I can see a proper picture, however just in the left 2/3 of the screen, I guess that is 640x480. It is also slightly shifted downward. What does xclk do? Where can I find proper docs for the driver? (In the usual place aka. the source?) > > Changing timing information for atyfb (with M and R options in mode) > > didn't help, so did enabling the native panel interface in the kernel. > > What is this 'native panel interface'? It is the kernel option FB_ATY_GENERIC_LCD. Enabling it and your proposed kernel argument resulted in a pefectly working framebuffer! Yieppieh! Thanks! :) Thanks for the quick and helpful repy! --Stephan |
|
From: Stephan D. <lan...@we...> - 2007-04-22 14:25:12
|
> > With the panels native resolution of 1024x512, I can see that the screen > > is initialised properly (to the full resolution), but consists only of > > white on-pixel-wide vertical stripes. Some sort of blinking in the area > > of the curser is also visible. > > Try booting with video=atyfb:xclk:63. Thanks, that helps partly! I can see a proper picture, however just in the left 2/3 of the screen, I guess that is 640x480. It is also slightly shifted downward. What does xclk do? Where can I find proper docs for the driver? (In the usual place aka. the source?) > > Changing timing information for atyfb (with M and R options in mode) > > didn't help, so did enabling the native panel interface in the kernel. > > What is this 'native panel interface'? It is the kernel option FB_ATY_GENERIC_LCD (probably this, together with your fix could make things work perfectly, again) Thanks for the quick and helpful repy! --Stephan |
|
From: Ville <sy...@sc...> - 2007-04-22 00:15:19
|
On Sat, Apr 21, 2007 at 07:35:27PM +0200, Stephan Diestelhorst wrote: > Hi list, > I've just compiled Linux 2.6.20 on my Fujitsu FMV-253L with ATI Rage > Mobility P/M. > > Enabling the according framebuffer and giving the video=atyfb:... kernel > option doesn't work properly, however. > > With the panels native resolution of 1024x512, I can see that the screen is > initialised properly (to the full resolution), but consists only of white > on-pixel-wide vertical stripes. Some sort of blinking in the area of the > curser is also visible. Try booting with video=atyfb:xclk:63. > Changing to other resolutions (640x480) didn't change much, same white > stripes, but now with black borders left and right. > > Changing timing information for atyfb (with M and R options in mode) didn't > help, so did enabling the native panel interface in the kernel. What is this 'native panel interface'? -- Ville Syrjälä sy...@sc... http://www.sci.fi/~syrjala/ |
|
From: Stephan D. <dr...@fr...> - 2007-04-21 17:35:36
|
Hi list, I've just compiled Linux 2.6.20 on my Fujitsu FMV-253L with ATI Rage Mobility P/M. Enabling the according framebuffer and giving the video=atyfb:... kernel option doesn't work properly, however. With the panels native resolution of 1024x512, I can see that the screen is initialised properly (to the full resolution), but consists only of white on-pixel-wide vertical stripes. Some sort of blinking in the area of the curser is also visible. Changing to other resolutions (640x480) didn't change much, same white stripes, but now with black borders left and right. Changing timing information for atyfb (with M and R options in mode) didn't help, so did enabling the native panel interface in the kernel. Funny thing is, that everything works fine in X.org with the ati/mach64 driver, with a custom modeline. Any ideas / patches, I might try out? Thanks in advance, Stephan |
|
From: James S. <jsi...@in...> - 2007-04-01 01:03:49
|
Enable "Epson S1D13XXX framebuffer support" in the configuration. Let us know if it works. On Wed, 28 Mar 2007, Joshua Xie wrote: > Is there anybody working on the FB driver for SED1335? I would like to > join the development/testing if possible. I recently got an LCD with > build-in SED1335 controller and I would like to get it to work with my > TS-7250 ARM based SBC. Thank you. > > > > Joshua > > > > |
6 messages has been excluded from this view by a project administrator.
