Hello, I have had problems using a projector under Fedora.
For most applications, when I plug the projector into my laptop (DELL Latitude 610) the screen is echoed reasonably, but a strip at the edge of the display is missing. Fiddling with the 'Display' and 'Screen Resolution' don't seem to help (and the dual head does nothing!). Shame, but not crucial.
However, with mplayer 1.0rc2 (locally compiled) the -vo options xv and gl look fine on the laptop screen but give a 'blue screen' in their piece of the projected image. I have never seen that before. 'gl2' works, but is very slow and finally times out. Finally 'dga' (root!) shows a completely corrupt image, but the same on both screens. -x11 sort-of works, but it cannot be resized and is not very nice. Any ideas anyone? Bill
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 12 November 2003 09:44, William John Murray wrote:
(DELL Latitude 610) the screen is echoed reasonably, but a
What is the video chipset... and what's in your /etc/X11/XF86Config?
- -Andy
Hi Andy, sorry, I should have said:
Video card: Radeon Mobility M6 LY (Recognised during setup by Fedora, unlike the Dell FP display)
Full XF86config follows, to save discussion! (I know the mouse is wrong for my internal laptopn mouse, but that has gone 'bad' so is disabled)
# XFree86 4 configuration created by redhat-config-xfree86
Section "ServerLayout" Identifier "single head configuration" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection
Section "Files" FontPath "unix/:7100" EndSection
Section "Module"
# Load "record" # X event recorder # You only need the following two modules if you do not use xfs. # Load "freetype" # TrueType font handler # Load "type1" # Adobe Type 1 font handler Load "dbe" # Double-buffering Load "GLcore" # OpenGL support Load "dri" # Direct rendering infrastructure Load "glx" # OpenGL X protocol interface Load "extmod" # Misc. required extensions Load "v4l" # Video4Linux EndSection
Section "InputDevice" Identifier "Keyboard0" Driver "keyboard" Option "XkbLayout" "gb" EndSection
Section "InputDevice"
# Modified by mouseconfig # Modified by mouseconfig Identifier "Mouse0" Driver "mouse" Option "Device" "/dev/mouse" Option "Protocol" "IMPS/2" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection
Section "Monitor"
# HorizSync 31.5 - 90.0 # VertRefresh 59.0 - 75.0 Identifier "Dell 1400X Laptop Display Panel" VendorName "Unknown" ModelName "Dell 1400x1050 Laptop Display Panel" DisplaySize 286 215 HorizSync 31.5 - 90.0 VertRefresh 59.0 - 75.0 Option "dpms" EndSection
Section "Device" Identifier "ATI Radeon Mobility M6" Driver "radeon" BoardName "ATI Radeon Mobility M6" EndSection
Section "Screen" Identifier "Screen0" Device "ATI Radeon Mobility M6" Monitor "Dell 1400X Laptop Display Panel" DefaultDepth 16 Option "backingstore" SubSection "Display" Depth 16 Modes "1400x1050" "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1400x1050" "1280x1024" "1024x768" "800x600" EndSubSection EndSection
Section "DRI" Mode 0666 EndSection
On Wed, 2003-11-12 at 10:27, Andy Green wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 12 November 2003 09:44, William John Murray wrote:
(DELL Latitude 610) the screen is echoed reasonably, but a
What is the video chipset... and what's in your /etc/X11/XF86Config?
- -Andy
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/sgsljKeDCxMJCTIRAjWKAJ0VfsJOj1XOmm/DootuiktUWz2VNgCfaWHd jzNU0bIQLIeupJDq1i5+wQY= =cp3c -----END PGP SIGNATURE-----
-- fedora-list mailing list fedora-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-list
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 12 November 2003 10:37, William John Murray wrote:
(I know the mouse is wrong for my internal laptopn mouse, but that has gone 'bad' so is disabled)
Hm, wonder if its as disabled as you think it is... maybe its spamming interrupts somewhere and causing trouble that way. What kind of bad did it go?
Section "Device" Identifier "ATI Radeon Mobility M6" Driver "radeon"
I would # out the Driver "radeon" line and try it with Driver "vesa" just to see if that made any difference.
I would also fiddle with kernel params added in /boot/grub/grub.conf to kill acpi, eg, acpi=off
Alan Cox had these wise words to share with us earlier today:
o System boots to graphical desktop but the desktop appears and then the machine crashes
Boot with "apm=off" and see if this helps. A few laptops have buggy battery query support.
- -Andy
Thanks Andy! All sorts of interesting things happen: (Relevant to the recent X/Autodetect thread) I have been experimenting with a second monitor, not a projector. But it feels very similar to me...)
1) radeon->vesa driver for my radeon card
This drops glxgears from 600->175, and dri support goes. mplayer knows xv will not work, so picks x11. Which means I do get a display, without having to think, even if it is not a nice one. However, the alt-F8 works as it did on RH-9. It seemed to be disabled before. So I can choose laptop, projector or both.
2) apm on/off does nothing for me.
3) apci off/on does nothing for me.
4) Start X WITHOUT the external display, and then plugging it in, fixes the problem.
So it seems that it recognises the second screen and tries to do something clever in consequence. So I can summarise: A) Start X with projector connected Screen position correct, no clipping, but 680x480 only. xv output only displayed on laptop.
In XFree86.0.log I notice: (**) RADEON(0): *Mode "1400x1050" (**) RADEON(0): *Mode "1280x1024" (**) RADEON(0): *Mode "1280x960" (**) RADEON(0): *Mode "1152x864" (**) RADEON(0): *Mode "1024x768" (**) RADEON(0): *Mode "800x600" (**) RADEON(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) RADEON(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (**) RADEON(0): Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D) (II) RADEON(0): Modeline "320x240" 12.60 320 328 376 400 240 245 246 262 doublescan -hsync -vsync
B) Start X without, then plug-in xv works nicely screen display slightly misplaced 1400x1050 seems to work on this monitor.
Does that suggest anything about the source? Bill
On Thu, 2003-11-13 at 12:09, Andy Green wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 12 November 2003 10:37, William John Murray wrote:
(I know the mouse is wrong for my internal laptopn mouse, but that has gone 'bad' so is disabled)
Hm, wonder if its as disabled as you think it is... maybe its spamming interrupts somewhere and causing trouble that way. What kind of bad did it go?
Section "Device" Identifier "ATI Radeon Mobility M6" Driver "radeon"
I would # out the Driver "radeon" line and try it with Driver "vesa" just to see if that made any difference.
I would also fiddle with kernel params added in /boot/grub/grub.conf to kill acpi, eg, acpi=off
Alan Cox had these wise words to share with us earlier today:
o System boots to graphical desktop but the desktop appears and then the machine crashes
Boot with "apm=off" and see if this helps. A few laptops have buggy battery query support.
- -Andy
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/s3SLjKeDCxMJCTIRAgJFAJ430qJNaemVD3T8E6X7nJxKVLst+ACgljrm Ej/z/hrm0yimDoahVYnRD7w= =YH1q -----END PGP SIGNATURE-----
-- fedora-list mailing list fedora-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-list
On Thu, 2003-11-13 at 11:41, William John Murray wrote:
Thanks Andy! All sorts of interesting things happen: (Relevant to the recent X/Autodetect thread) I have been experimenting with a second monitor, not a projector. But it feels very similar to me...)
- radeon->vesa driver for my radeon card
This drops glxgears from 600->175, and dri support goes. mplayer knows xv will not work, so picks x11. Which means I do get a display, without having to think, even if it is not a nice one. However, the alt-F8 works as it did on RH-9. It seemed to be disabled before. So I can choose laptop, projector or both.
apm on/off does nothing for me.
apci off/on does nothing for me.
Start X WITHOUT the external display, and then plugging it in,
fixes the problem.
So it seems that it recognises the second screen and tries to do something clever in consequence. So I can summarise: A) Start X with projector connected Screen position correct, no clipping, but 680x480 only. xv output only displayed on laptop.
In XFree86.0.log I notice: (**) RADEON(0): *Mode "1400x1050" (**) RADEON(0): *Mode "1280x1024" (**) RADEON(0): *Mode "1280x960" (**) RADEON(0): *Mode "1152x864" (**) RADEON(0): *Mode "1024x768" (**) RADEON(0): *Mode "800x600" (**) RADEON(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) RADEON(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (**) RADEON(0): Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D) (II) RADEON(0): Modeline "320x240" 12.60 320 328 376 400 240 245 246 262 doublescan -hsync -vsync
B) Start X without, then plug-in xv works nicely screen display slightly misplaced 1400x1050 seems to work on this monitor.
Does that suggest anything about the source? Bill
On Thu, 2003-11-13 at 12:09, Andy Green wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 12 November 2003 10:37, William John Murray wrote:
(I know the mouse is wrong for my internal laptopn mouse, but that has gone 'bad' so is disabled)
Hm, wonder if its as disabled as you think it is... maybe its spamming interrupts somewhere and causing trouble that way. What kind of bad did it go?
Section "Device" Identifier "ATI Radeon Mobility M6" Driver "radeon"
I would # out the Driver "radeon" line and try it with Driver "vesa" just to see if that made any difference.
I would also fiddle with kernel params added in /boot/grub/grub.conf to kill acpi, eg, acpi=off
Alan Cox had these wise words to share with us earlier today:
o System boots to graphical desktop but the desktop appears and then the machine crashes
Boot with "apm=off" and see if this helps. A few laptops have buggy battery query support.
- -Andy
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/s3SLjKeDCxMJCTIRAgJFAJ430qJNaemVD3T8E6X7nJxKVLst+ACgljrm Ej/z/hrm0yimDoahVYnRD7w= =YH1q -----END PGP SIGNATURE-----
-- fedora-list mailing list fedora-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-list
Just noticed this post while cleaning out mail. So this reply might be too late, but you never know.
I have a Dell Latitude C610 and needed to add the following option to my XF86Config file in the Device Section:
Option "OverlayOnCRTC2" "true"
This forces hardware overlay to the clone head, which will allow XV output to display to a secondary CRT. This allows me to use my docking station with XV video. No need to change this option for normal laptop usage either.
I use the "ati" driver, but the "radeon" driver should work fine I think (equivalent).
I think it should fix the "blue screen" problem when using the external video port on the laptop. But then if sending output to both simultaneously you may end up with a "blue screen" on your laptop instead -- don't know for sure though, never tried it.
The other problem probably has something to do with matching the right monitor definition (Section "Monitor") with your display. You may need to play with other device driver options as well (ie. "MonitorLayout"). May or may not be worth the time spent figuring it out.
Hope that helps.
Jon
XV is the method you want to use. That is usually only available if the driver supports it.
That's about all I know. Anyone else want to elaborate? -- Kevin G. Francis http://denial.loose-screws.com/
Andy Green wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 12 November 2003 09:44, William John Murray wrote:
(DELL Latitude 610) the screen is echoed reasonably, but a
What is the video chipset... and what's in your /etc/X11/XF86Config?
- -Andy
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/sgsljKeDCxMJCTIRAjWKAJ0VfsJOj1XOmm/DootuiktUWz2VNgCfaWHd jzNU0bIQLIeupJDq1i5+wQY= =cp3c -----END PGP SIGNATURE-----
-- fedora-list mailing list fedora-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-list
I don't know if its possible to use Xv on the external monitor.
If it is, I'd also like to know, but I haven't really looked into it yet anyway. With my last laptop, with a Savage IX-NX (I think) I couldn't see any Xv contents in the external monitor. I just assumed it wasn't possible.
Rui
On Wed, 2003-11-12 at 09:44, William John Murray wrote:
Hello, I have had problems using a projector under Fedora.
For most applications, when I plug the projector into my laptop (DELL Latitude 610) the screen is echoed reasonably, but a strip at the edge of the display is missing. Fiddling with the 'Display' and 'Screen Resolution' don't seem to help (and the dual head does nothing!). Shame, but not crucial.
However, with mplayer 1.0rc2 (locally compiled) the -vo options xv and gl look fine on the laptop screen but give a 'blue screen' in their piece of the projected image. I have never seen that before. 'gl2' works, but is very slow and finally times out. Finally 'dga' (root!) shows a completely corrupt image, but the same on both screens. -x11 sort-of works, but it cannot be resized and is not very nice. Any ideas anyone? Bill
-- fedora-list mailing list fedora-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-list
-
Andy Green -
Jonathan DeSena -
Kevin Francis -
Rui Miguel Silva Seabra -
William John Murray