Menu
▾
▴
linux-fbdev-devel
|
From: Stelian P. <ste...@fr...> - 2001-10-12 10:47:21
|
Hi everybody. I have a Vaio Picturebook C1VE running Linux, and I have a problem when using an external monitor with the CVS version of XFree86. I'm running the 2.4.10-ac12 version of the Linux kernel (which contains Marcel's patch for wide framebuffer console: CONFIG_FB_ATY_CT_VAIO_LCD). The ATI card is: 00:0d.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M (rev 64) When the framebuffer code is compiled into the kernel, external monitor picture is blurred. Since is rather hard to explain, here is a picture of the monitor taken with an digital camera: http://spop.free.fr/xfree/xfree-monitor.jpg If the framebuffer code is _not_ compiled into the kernel, external monitor works fine (note that this was not the case with XFree 4.1.0, only the CVS version contains the fixes to make it happen). I've also noted that even without launching X, when using the framebuffer, the external display picture is blurred too. However, in text mode this is hardly noticable. It is clear that the framebuffer code has a bug which causes the blur. But it isn't clear for me why XFree is not able to reinitialize the hardware correctly after the framebuffer code has touched it. I would really want to be able to use both features (framebuffer for wide console and X external monitor output)... A somewhat related question for linux framebuffer guys: is it possible to disable the framebuffer on boot (without having to compile two kernels, a framebuffer based one and one without) with some parameter ? I tried leaving out the vga=0x301 parameter, or put a vga= something else (80x25 text mode) etc, but the framebuffer code seems to initialize itself whatever option I put on the kernel boot line. Thanks, Stelian. -- Stelian Pop <ste...@fr...> |---------------- Free Software Engineer -----------------| | Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 | |------------- Alcôve, liberating software ---------------| |
|
From: Geert U. <ge...@li...> - 2001-10-12 11:23:50
|
On Fri, 12 Oct 2001, Stelian Pop wrote:
> I have a Vaio Picturebook C1VE running Linux, and I have a
> problem when using an external monitor with the CVS version
> of XFree86.
[...]
> It is clear that the framebuffer code has a bug which causes the
> blur. But it isn't clear for me why XFree is not able to
> reinitialize the hardware correctly after the framebuffer code has
> touched it.
XFree86 expects a chip configured to VGA text mode, unless you specify an
`fbdev' option (IIRC).
> A somewhat related question for linux framebuffer guys: is it
> possible to disable the framebuffer on boot (without having to
> compile two kernels, a framebuffer based one and one without)
> with some parameter ? I tried leaving out the vga=0x301
> parameter, or put a vga= something else (80x25 text mode) etc,
> but the framebuffer code seems to initialize itself whatever
> option I put on the kernel boot line.
video=atyfb:off
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Marc A. La F. <ts...@ua...> - 2001-10-12 12:09:58
|
On Fri, 12 Oct 2001, Geert Uytterhoeven wrote: > > I have a Vaio Picturebook C1VE running Linux, and I have a > > problem when using an external monitor with the CVS version > > of XFree86. > [...] > > It is clear that the framebuffer code has a bug which causes the > > blur. But it isn't clear for me why XFree is not able to > > reinitialize the hardware correctly after the framebuffer code has > > touched it. > XFree86 expects a chip configured to VGA text mode, unless you specify an > `fbdev' option (IIRC). That's not so. First, there is no 'fbdev' option of any kind. Second, XFree86's ATI driver assumes all aspects of the mode on entry are correctly programmed, whether or not it's a VGA text mode. Marc. +----------------------------------+-----------------------------------+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax: 1-780-492-1729 | | 352 General Services Building | email: ts...@ua... | | University of Alberta +-----------------------------------+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply | | CANADA | | +----------------------------------+-----------------------------------+ XFree86 Core Team member. ATI driver and X server internals. |
|
From: Branden R. <br...@de...> - 2001-10-12 15:44:42
|
On Fri, Oct 12, 2001 at 06:09:49AM -0600, Marc Aurele La France wrote: > On Fri, 12 Oct 2001, Geert Uytterhoeven wrote: > > XFree86 expects a chip configured to VGA text mode, unless you specify = an > > `fbdev' option (IIRC). >=20 > That's not so. First, there is no 'fbdev' option of any kind. Second, > XFree86's ATI driver assumes all aspects of the mode on entry are > correctly programmed, whether or not it's a VGA text mode. Perhaps he means: Section "Device" Identifier "Generic Video Card" Driver "ati" Option "UseFBDev" "true" EndSection =2E..which certainly does exist. --=20 G. Branden Robinson | If God had intended for man to go Debian GNU/Linux | about naked, we would have been br...@de... | born that way. http://people.debian.org/~branden/ | |
|
From: Marc A. La F. <ts...@ua...> - 2001-10-12 16:06:41
|
On Fri, 12 Oct 2001, Branden Robinson wrote: > On Fri, Oct 12, 2001 at 06:09:49AM -0600, Marc Aurele La France wrote: > > On Fri, 12 Oct 2001, Geert Uytterhoeven wrote: > > > XFree86 expects a chip configured to VGA text mode, unless you specify an > > > `fbdev' option (IIRC). > > That's not so. First, there is no 'fbdev' option of any kind. Second, > > XFree86's ATI driver assumes all aspects of the mode on entry are > > correctly programmed, whether or not it's a VGA text mode. > Perhaps he means: > Section "Device" > Identifier "Generic Video Card" > Driver "ati" > Option "UseFBDev" "true" > EndSection > ...which certainly does exist. We are talking about the Mobility M1, a Mach64 variant. My comment above stays. Marc. +----------------------------------+-----------------------------------+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax: 1-780-492-1729 | | 352 General Services Building | email: ts...@ua... | | University of Alberta +-----------------------------------+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply | | CANADA | | +----------------------------------+-----------------------------------+ XFree86 Core Team member. ATI driver and X server internals. |
|
From: Stelian P. <ste...@fr...> - 2001-10-12 13:42:39
|
On Fri, Oct 12, 2001 at 01:22:52PM +0200, Geert Uytterhoeven wrote: > > A somewhat related question for linux framebuffer guys: is it > > possible to disable the framebuffer on boot (without having to > > compile two kernels, a framebuffer based one and one without) > > with some parameter ? I tried leaving out the vga=0x301 > > parameter, or put a vga= something else (80x25 text mode) etc, > > but the framebuffer code seems to initialize itself whatever > > option I put on the kernel boot line. > > video=atyfb:off Thanks, it worked. No need for double kernel compiled now :-) Stelian. -- Stelian Pop <ste...@fr...> |---------------- Free Software Engineer -----------------| | Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 | |------------- Alcôve, liberating software ---------------| |
|
From: Marc A. La F. <ts...@ua...> - 2001-10-12 12:06:43
|
On Fri, 12 Oct 2001, Stelian Pop wrote: > I have a Vaio Picturebook C1VE running Linux, and I have a > problem when using an external monitor with the CVS version > of XFree86. > I'm running the 2.4.10-ac12 version of the Linux kernel > (which contains Marcel's patch for wide framebuffer console: > CONFIG_FB_ATY_CT_VAIO_LCD). > The ATI card is: > 00:0d.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M (rev 64) > When the framebuffer code is compiled into the kernel, external > monitor picture is blurred. Since is rather hard to explain, > here is a picture of the monitor taken with an digital camera: > http://spop.free.fr/xfree/xfree-monitor.jpg > If the framebuffer code is _not_ compiled into the kernel, > external monitor works fine (note that this was not the case with > XFree 4.1.0, only the CVS version contains the fixes to make it > happen). > I've also noted that even without launching X, when using the > framebuffer, the external display picture is blurred too. However, > in text mode this is hardly noticable. It sounds to me that atyfb isn't dealing with shadow registers properly. > It is clear that the framebuffer code has a bug which causes the > blur. But it isn't clear for me why XFree is not able to > reinitialize the hardware correctly after the framebuffer code has > touched it. If it did, it would not be able to restore the mode on entry properly. Marc. +----------------------------------+-----------------------------------+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax: 1-780-492-1729 | | 352 General Services Building | email: ts...@ua... | | University of Alberta +-----------------------------------+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply | | CANADA | | +----------------------------------+-----------------------------------+ XFree86 Core Team member. ATI driver and X server internals. |
|
From: Stelian P. <ste...@fr...> - 2001-10-12 13:45:44
|
On Fri, Oct 12, 2001 at 06:06:28AM -0600, Marc Aurele La France wrote: > > When the framebuffer code is compiled into the kernel, external > > monitor picture is blurred. Since is rather hard to explain, > > here is a picture of the monitor taken with an digital camera: > > http://spop.free.fr/xfree/xfree-monitor.jpg > > > If the framebuffer code is _not_ compiled into the kernel, > > external monitor works fine (note that this was not the case with > > XFree 4.1.0, only the CVS version contains the fixes to make it > > happen). > > It sounds to me that atyfb isn't dealing with shadow registers properly. Ok, it seems clear enough that this is 100% related to the framebuffer code, nothing to do with X. Let's take the discussion out of the X mailing list. Stelian. -- Stelian Pop <ste...@fr...> |---------------- Free Software Engineer -----------------| | Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 | |------------- Alcôve, liberating software ---------------| |
|
From: Stelian P. <ste...@fr...> - 2001-10-12 13:49:11
|
On Fri, Oct 12, 2001 at 06:06:28AM -0600, Marc Aurele La France wrote: > > When the framebuffer code is compiled into the kernel, external > > monitor picture is blurred. Since is rather hard to explain, > > here is a picture of the monitor taken with an digital camera: > > http://spop.free.fr/xfree/xfree-monitor.jpg > > > If the framebuffer code is _not_ compiled into the kernel, > > external monitor works fine (note that this was not the case with > > XFree 4.1.0, only the CVS version contains the fixes to make it > > happen). > > > I've also noted that even without launching X, when using the > > framebuffer, the external display picture is blurred too. However, > > in text mode this is hardly noticable. > > It sounds to me that atyfb isn't dealing with shadow registers properly. Marcel, as the original developer of the Vaio specific part of the code, do you have an idea on what needs to be done ? I would gladly test any kernel framebuffer patch any time, however I'm not good enough in fb / video code to search by myself the problem. Thanks, Stelian. -- Stelian Pop <ste...@fr...> |---------------- Free Software Engineer -----------------| | Alcôve - http://www.alcove.com - Tel: +33 1 49 22 68 00 | |------------- Alcôve, liberating software ---------------| |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X