Bug#235704: MonitorLayout detection fails with VGA + S-Video out on Radeon 7000 / QY
On Sunday 14 January 2007 17:09, Brice Goglin wrote: > Hi Josh, > > About 3 years ago, you reported a bug to the Debian BTS regarding > monitor layout failing with VGA/Svideo output on a Radeon 7000 QY board. > Did you reproduce this problem recently? If not, I will close this bug > in the next weeks. > > Thanks, > Brice Brice, Thanks for checking. I still have the workaround (manually specifying MonitorLayout in xorg.conf) implemented, so I don't know if xorg now correctly detects things. I'll try to find a convinient time in the next couple days to restart X with that line commented out to see if the bug is fixed. Josh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: X and 2.6.5 kernel: update of 2.6.5 kernel locks my laptop
On Fri, 30 Apr 2004, Branden Robinson wrote: On Thu, Apr 29, 2004 at 09:14:58AM +, slaven peles wrote: Apr 29 08:25:01 ivor kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). Apr 29 08:25:01 ivor kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. Apr 29 08:25:01 ivor kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). Apr 29 08:25:01 ivor kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly. On Thu, Apr 29, 2004 at 10:54:24AM -0500, Diego Enrique Rodriguez wrote: I have same problem look my log in http://uvirtual.ean.edu.co/~derodriguez/kernelprob/XFree86.0.log On Thu, Apr 29, 2004 at 03:52:18PM -0400, Josh Metzler wrote: This happens to me, too - Radeon 7000, same kernel. I filed bug #246587 against kernel-image-2.6.5-1-686. Hi guys, This should be fixed in the version of XFree86 that entered sid on 29 April. xfree86 (4.3.0.dfsg.1-1) unstable; urgency=low [...] * Fix AT keyboard rate I/O controls by operating on the actual console file descriptor, not on file descriptor zero (thanks, Keith Packard). Suppresses warning messages from Linux 2.6. (Closes: #224909) [...] -- Fabio M. Di Nitto <[EMAIL PROTECTED]> Wed, 28 Apr 2004 18:55:17 +0200 Thanks, but slaven misdiagnosed the cause of the problem. These atkbd.c errors are unrelated to it (though may be the errors Diego was talking about). The removal of the non-free radeon firmware from the kernel causes the X server to lock up using 100% cpu (and to fill up XFree86.0.log with error messages). I was able to ssh into my box and reboot it, so using the power button is not necessary if you can connect remotely. See bug #246587 against kernel-image-2.6.5-1-686 for more details. Josh
Re: Re: Bug#246627: Radeon card firmware problem
On Fri, 30 Apr 2004, Fabio Massimo Di Nitto wrote: On Fri, 30 Apr 2004, Daniel Stone wrote: On Fri, Apr 30, 2004 at 08:53:41AM +0200, Fabio Massimo Di Nitto wrote: > It should be able to fix the problem but i cannot test it myself since I > lack that kind of hardware. I can test any of these patches, Please do so! but I doubt stuff like 3D will work if this microcode is actually needed! This would be really, really, really bad if we can do neither 3D nor acceleration. Yes these was mentioned on debian-x. Sorry i don't have the message reference handy. Next time we need a more thorough analysis, not just 'I don't think this file gets used much anywhere'. That includes testing on the relevant hardware: I have a Radeon 9000 which can be used for testing Radeon stuff, but I just assumed it had been tested when it was asserted that it was thoroughly unnecessary. http://lists.debian.org/debian-x/2004/debian-x-200404/msg00955.html I did call for testers after we changed/removed the code from X but there have no replies to it. I assumed that noone had problems with it. Fabio This is not a problem with the new XFree86. It works fine with Debian kernel version 2.6.5-2. Non-free firmware was also pulled from the Debian kernel starting in version 2.6.5-3, and that is what causes this problem. See bug #246587 against kernel-image-2.6.5-1-686. It would be nice, though, if X didn't lockup using 100% cpu in this situation. Josh
Re: X and 2.6.5 kernel: update of 2.6.5 kernel locks my laptop
slaven peles wrote: > After updating kernel 2.6.5-1-686 from version 2.6.5-2 to 2.6.5-3, my laptop > gets locked as soon as X is started upon boot. I get just a blank screen, > keyboard does not respond, and all I can do is to turn the power off. This happens to me, too - Radeon 7000, same kernel. I filed bug #246587 against kernel-image-2.6.5-1-686. I believe it is due to firmware being removed from the radeon kernel module, according to this excerpt from the kernel-source-2.6.5 2.6.5-3 changelog: * Added firmware loading support (Nathaneal Nerode): . drivers/char/drm/Kconfig . drivers/char/drm/Makefile . drivers/char/drm/r128_cce.c . drivers/char/drm/r128_drv.h . drivers/char/drm/r128_firmware_loader.c . drivers/char/drm/radeon_cp.c . drivers/char/drm/radeon_drv.h . drivers/char/drm/radeon_firmware_loader.c * Removed non-free firmware: . R128 firmware: drivers/char/drm/r128_cce.c . Radeon firmware: drivers/char/drm/radeon_cp.c Downgrading the kernel to 2.6.5-2 worked for me. Josh
Bug#235704: MonitorLayout detection fails with VGA + S-Video out on Radeon 7000 / QY
Package: xserver-xfree86 Version: 4.3.0-3 I have a Radeon 7000 / QY (rv100) with both VGA and S-Video outputs. I have my CRT monitor connected to the VGA out. There is nothing connected to the S-Video out. The radeon driver claims to detect two monitors, but fails to fetch the VertSync and HorizSync for the 2nd monitor (which makes sense, as there isn't one), so I end up with a 640x480 display instead of 1600x1200. Detection worked correctly with 4.2.1. Adding the line Option "MonitorLayout" "CRT,NONE" to the Device section works around the problem. Josh Metzler [EMAIL PROTECTED]:~$ lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8374 P4X400 Host Controller/AGP Bridge (rev 03) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 50) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Files" # FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/CID" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID" FontPath"/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/psaux" Option "Protocol" "ImPS/2" Option "Emulate3Buttons" "true" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "ATI Radeon VE QY" Driver "radeon" Option "AGPMode" "4" Option "AGPFastWrite" "true" Option "EnablePageFlip""true" BusID "PCI:01:00:00" EndSection Section "Monitor" Identifier "Mag 986FS" HorizSync 30-86 VertRefresh 50-160 DisplaySize 37 28
Re: xbase-clients 4.3.0-pre1v4: incorrect permissions set on /usr/X11R6/bin
On Friday 14 November 2003 02:06 am, Branden Robinson wrote: > On Tue, Nov 11, 2003 at 11:15:43AM -0500, Josh Metzler wrote: > > I did a fresh install of Debian using the new debian-installer. I only > > installed the base packages. I then dist-upgraded to unstable. I > > installed xfree86 4.3.0-pre1v4 with no previous version of x installed. > > I also installed KDE from unstable. > > > > I was unable to login as a normal user using KDM. So, I tried > > > > ~$ startx > > -bash: startx: command not found > > > > After some searching, I finally checked the permissions on > > /usr/X11R6/bin and found: > > > > ~# ls -l /usr/X11R6 > > total 16 > > drwx--2 root root 4096 Nov 11 10:23 bin > > drwxr-xr-x3 root root 4096 Nov 11 09:14 include > > drwxr-xr-x4 root root 4096 Nov 11 09:17 include > > drwxr-xr-x6 root root 4096 Nov 11 09:17 include > > > > doing a "chmod +rx /usr/X11R6/bin" fixed everything for me. I suggest > > checking what permissions the experimental xbase-clients sets on this > > directory. > > I've heard a few reports of this, but I am totally stumped by what could > be causing this. The xfree86 packages almost certainly appear to *not* > be at fault, as the attached data collected auric.debian.org (Debian's > master archive) illustrates. > > Do you have any other packages that ship this directory? > > The command "dpkg -S usr/X11R6/bin" should tell you. You are right. I had assumed it was an XFree86 package that had created the directory, but gv must have gotten installed first. This bug was filed against gv yesterday (#221042).
xbase-clients 4.3.0-pre1v4: incorrect permissions set on /usr/X11R6/bin
I did a fresh install of Debian using the new debian-installer. I only installed the base packages. I then dist-upgraded to unstable. I installed xfree86 4.3.0-pre1v4 with no previous version of x installed. I also installed KDE from unstable. I was unable to login as a normal user using KDM. So, I tried ~$ startx -bash: startx: command not found After some searching, I finally checked the permissions on /usr/X11R6/bin and found: ~# ls -l /usr/X11R6 total 16 drwx--2 root root 4096 Nov 11 10:23 bin drwxr-xr-x3 root root 4096 Nov 11 09:14 include drwxr-xr-x4 root root 4096 Nov 11 09:17 include drwxr-xr-x6 root root 4096 Nov 11 09:17 include doing a "chmod +rx /usr/X11R6/bin" fixed everything for me. I suggest checking what permissions the experimental xbase-clients sets on this directory. Josh
4.3.0-pre1v4 radeon driver wrongly detects two monitors
First of all, thank you guys for the effort you put into packaging XFree86. I have a Radeon VE/7000 QY card with both DVI and VGA ports. I have a single 19 inch monitor, and it is connected to the VGA port. When I upgraded to XFree86 4.3.0-pre1v4 from 4.2.1-13, the X server would only start up in 640x480 rather than 1600x1200. Looking through the log, I found that the driver was detecting two monitors. Since I hadn't specified any information about a second monitor, it was using the default hsync and vrefresh, which disallowed all modes higher than 640x480. I solved the problem by specifying the Options "CloneHSync" and "CloneVRefresh" in the Device section to be the same as the hsync and vrefresh of the monitor. Now I get X at 1600x1200 again. However, the radeon driver should be able to detect that I only have one monitor. I'm running the 2.6.0-test9-1-386 kernel if that matters. And, the xserver from 4.2.1-13 does only detect my single monitor. Please CC me on replies, as I'm not subscribed to the list. Josh Relevant sections of log (from before specifying these options) - I can post more of it if you are interested: (II) RADEON(0): Displays Detected: Monitor1--Type 1, Monitor2--Type 1 ... (II) RADEON(0): Primary Display == Type 1 (II) RADEON(0): Clone Display == Type 1 (II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=35000; xclk=15000 (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0) (II) RADEON(0): Clone modes validation (WW) RADEON(0): Mag 986FS: Using default hsync range of 28.00-33.00kHz (WW) RADEON(0): Mag 986FS: using default vrefresh range of 43.00-72.00Hz ... (II) RADEON(0): Validating modes on Primary head - (II) RADEON(0): Mag 986FS: Using hsync range of 30.00-86.00 kHz (II) RADEON(0): Mag 986FS: Using vrefresh range of 50.00-160.00 Hz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]