FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 06-15-2010, 09:01 AM
Julien Cristau
 
Default Bug#585822: xserver-xorg-video-radeon: radeon/KMS wrong monitor resolution due to mistakenly detected TV-out (S-video) for RV350 chipset (with workaround)

reassign 585822 linux-2.6 2.6.32-15
severity 585822 normal
kthxbye

On Sun, Jun 13, 2010 at 22:39:20 -0400, Stefano wrote:

> Package: xserver-xorg-video-radeon
> Version: 1:6.13.0-2
> Severity: important
> Tags: squeeze sid
>
> *** Please type your report below this line ***
>
> Lately, I started playing with radeon/KMS (see e.g. #585815).

Reassigning to the kernel.

> Now, I don't know if it was because of my intervention or of a recent
> upgrade, but when I started my laptop the screen resolution was all
> messed up.
>
> I had 800x600 instead of the usual 1024x768.
>
> Looking around, I discovered that some graphic cards mistakenly detect
> the S-video/TV-out output as connected and set the screen resolution at
> 800x600. This has been disabled by default for some chipsets, but not
> for mine (RV350 - Mobility Radeon 9600 M10).
>
> A solution is to disable the S-video output by default at the boot.
>
> I added the kernel parameter
>
> video=SVIDEO-1:d
>
> to GRUB_CMDLINE_LINUX in /etc/default/grub and ran update-grub as root.
>
> That restores the resolution that I had before.
>
> Beware that the correct value for the "video=" parameter is listed in
> /sys/class/drm so it maight be different for other users.
>
> I have read that this option does not allow to use the S-video output,
> but I could not verify it (I don't use that output at all).
>
> Also, I have read that the parameter must be the last of the kernel
> options otherwise it won't work. Again, I have not verified that.
>
> Now, it don't know if it would be a good option to disable the S-video
> output for my chipset directly in the driver or to disable it using the
> kernel parameter.
>
Is 2.6.34 (from experimental) better? If not, please file a bug at
bugs.freedesktop.org against product DRI, component DRM/radeon,
attaching your X and kernel logs.

[...]
> DRM Information from dmesg:
> [ 0.168192] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT]
> [ 0.957810] Linux agpgart interface v0.103
> [ 0.957897] agpgart-intel 0000:00:00.0: Intel 855GM Chipset
> [ 0.979328] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xe0000000
> [ 28.664898] [drm] Initialized drm 1.1.0 20060810
> [ 29.733132] [drm] radeon kernel modesetting enabled.
> [ 29.736539] [drm] radeon: Initializing kernel modesetting.
> [ 29.741045] [drm] Forcing AGP to PCI mode
> [ 29.741081] [drm] register mmio base: 0xD0100000
> [ 29.741083] [drm] register mmio size: 65536
> [ 29.742409] [drm] GPU reset succeed (RBBM_STATUS=0x00000140)
> [ 29.742430] [drm] Generation 2 PCI interface, using max accessible memory
> [ 29.742435] [drm] radeon: VRAM 64M
> [ 29.742437] [drm] radeon: VRAM from 0x00000000 to 0x03FFFFFF
> [ 29.742440] [drm] radeon: GTT 512M
> [ 29.742442] [drm] radeon: GTT from 0x20000000 to 0x3FFFFFFF
> [ 29.742465] [drm] radeon: irq initialized.
> [ 29.743439] [drm] Detected VRAM RAM=64M, BAR=128M
> [ 29.743443] [drm] RAM width 128bits DDR
> [ 29.743900] [drm] radeon: 64M of VRAM memory ready
> [ 29.743902] [drm] radeon: 512M of GTT memory ready.
> [ 29.743923] [drm] GART: num cpu pages 131072, num gpu pages 131072
> [ 29.745656] [drm] radeon: 1 quad pipes, 1 Z pipes initialized.
> [ 29.745669] [drm] radeon: cp idle (0x10000C03)
> [ 29.745727] [drm] Loading R300 Microcode
> [ 29.760148] [drm] radeon: ring at 0x0000000020000000
> [ 29.760172] [drm] ring test succeeded in 2 usecs
> [ 29.760302] [drm] radeon: ib pool ready.
> [ 29.760807] [drm] ib test succeeded in 0 usecs
> [ 29.761167] [drm] Panel ID String: AUO Color LCD
> [ 29.761172] [drm] Panel Size 1024x768
> [ 29.761265] [drm] Default TV standard: NTSC-J
> [ 29.761267] [drm] 27.000000000 MHz TV ref clk
> [ 29.761271] [drm] Default TV standard: NTSC-J
> [ 29.761273] [drm] 27.000000000 MHz TV ref clk
> [ 29.761332] [drm] Radeon Display Connectors
> [ 29.761335] [drm] Connector 0:
> [ 29.761337] [drm] VGA
> [ 29.761340] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
> [ 29.761343] [drm] Encoders:
> [ 29.761345] [drm] CRT1: INTERNAL_DAC1
> [ 29.761348] [drm] Connector 1:
> [ 29.761350] [drm] LVDS
> [ 29.761351] [drm] Encoders:
> [ 29.761353] [drm] LCD1: INTERNAL_LVDS
> [ 29.761355] [drm] Connector 2:
> [ 29.761357] [drm] S-video
> [ 29.761359] [drm] Encoders:
> [ 29.761361] [drm] TV1: INTERNAL_DAC2
> [ 29.773269] [drm] forcing SVIDEO-1 connector OFF
> [ 29.793650] [drm] fb mappable at 0xD8040000
> [ 29.793653] [drm] vram apper at 0xD8000000
> [ 29.793655] [drm] size 3145728
> [ 29.793657] [drm] fb depth is 24
> [ 29.793659] [drm] pitch is 4096
> [ 29.860837] fb0: radeondrmfb frame buffer device
> [ 29.875811] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0
>
Cheers,
Julien
 
Old 06-15-2010, 03:18 PM
Alex Deucher
 
Default Bug#585822: xserver-xorg-video-radeon: radeon/KMS wrong monitor resolution due to mistakenly detected TV-out (S-video) for RV350 chipset (with workaround)

On Sun, Jun 13, 2010 at 10:39 PM, Stefano <pietranera@gmail.com> wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:6.13.0-2
> Severity: important
> Tags: squeeze sid
>
> *** Please type your report below this line ***
>
> Lately, I started playing with radeon/KMS (see e.g. #585815).
>
> Now, I don't know if it was because of my intervention or of a recent
> upgrade, but when I started my laptop the screen resolution was all
> messed up.
>
> I had 800x600 instead of the usual 1024x768.
>
> Looking around, I discovered that some graphic cards mistakenly detect
> the S-video/TV-out output as connected and set the screen resolution at
> 800x600. This has been disabled by default for some chipsets, but not
> for mine (RV350 - Mobility Radeon 9600 M10).
>
> A solution is to disable the S-video output by default at the boot.
>
> I added the kernel parameter
>
> video=SVIDEO-1:d
>
> to GRUB_CMDLINE_LINUX in /etc/default/grub and ran update-grub as root.
>
> That restores the resolution that I had before.
>
> Beware that the correct value for the "video=" parameter is listed in
> /sys/class/drm so it maight be different for other users.
>
> I have read that this option does not allow to use the S-video output,
> but I could not verify it (I don't use that output at all).
>

You can still use it in X; that parameter just disables it for the console.

> Also, I have read that the parameter must be the last of the kernel
> options otherwise it won't work. Again, I have not verified that.
>
> Now, it don't know if it would be a good option to disable the S-video
> output for my chipset directly in the driver or to disable it using the
> kernel parameter.

The option you used is the correct one. Unfortunately, load detection
for tv-out is often unreliable. There's not a lot you can do to fix
it.

Alex



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTimpEMgrZRTq954-4bAgN95WxSiWXwJJPM8Ud75V@mail.gmail.com">http://lists.debian.org/AANLkTimpEMgrZRTq954-4bAgN95WxSiWXwJJPM8Ud75V@mail.gmail.com
 
Old 07-10-2010, 01:36 PM
Stefano
 
Default Bug#585822: xserver-xorg-video-radeon: radeon/KMS wrong monitor resolution due to mistakenly detected TV-out (S-video) for RV350 chipset (with workaround)

On Tuesday 15 June 2010 05:01:23 Julien Cristau wrote:
>
> Is 2.6.34 (from experimental) better? If not, please file a bug at
> bugs.freedesktop.org against product DRI, component DRM/radeon,
> attaching your X and kernel logs.

Hello,

sorry for the late reply.

Kernel 2.6.34 solves this bug (I don't have to specify any parameter at boot) but
brakes compositing (KDE4 tells me that compositing is not available).

For now I'll stick to 2.6.32 with the kernel parameters set at boot.

I would investigate further but I don't have much time right now.

Anyway, if you have any other questions, I am available to answer.

> Cheers,

Thanks,

> Julien

--
Stefano

Fortune of the day: "You will pioneer the first Martian colony."


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201007100936.29594.pietranera@gmail.com">http://lists.debian.org/201007100936.29594.pietranera@gmail.com
 

Thread Tools




All times are GMT. The time now is 11:16 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org