Processed: Re: Bug#499067: radeonhd: The screen remains black, altough there are no crashes
Processing commands for [EMAIL PROTECTED]: > severity 499067 important Bug#499067: radeonhd: The screen remains black, altough there are no crashes Severity set to `important' from `grave' > retitle 499067 radeonhd: black screen with Mobility 3470 and 3GB of RAM (Asus > Pro72S) Bug#499067: radeonhd: The screen remains black, altough there are no crashes Changed Bug title to `radeonhd: black screen with Mobility 3470 and 3GB of RAM (Asus Pro72S)' from `radeonhd: The screen remains black, altough there are no crashes'. > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499067: radeonhd: The screen remains black, altough there are no crashes
severity 499067 important retitle 499067 radeonhd: black screen with Mobility 3470 and 3GB of RAM (Asus Pro72S) thank you Alex wrote: > The radeonhd driver is not able to show any image on the screen, while > the "vesa" and "ati" drivers can. This $ > looks a bit like the one described by the X.Org Wiki > (http://www.x.org/wiki/radeonhd, the one with the Asus la$ > more than 2 GB of memory). > Did you try to pass mem=2048M or so to the kernel command line? It could be https://bugs.freedesktop.org/show_bug.cgi?id=16892 Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498690: marked as done (video-intel: [G43] DVI disabled by starting X)
Your message dated Thu, 18 Sep 2008 07:58:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#498690: video-intel: [G43] DVI disabled by starting X has caused the Debian Bug report #498690, regarding video-intel: [G43] DVI disabled by starting X to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 498690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498690 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: xserver-xorg-video-intel Version: 2:2.3.2-2+lenny2 Severity: normal File: video-intel I tried running Debian Live on a board with integrated G43 chipset with DVI output (Asus P5QL-EM). The VGA outout works but when I start X while the screen is connected through the DVI port the DVI output is disabled until reboot. The X refuses to start but when it finishes there is nothing visible even on the console. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2008-09-12 13:49 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1719572 2008-08-26 17:48 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Eaglelake Integrated Graphics Controller (rev 03) /etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1077 2008-09-12 14:01 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 24256 2008-09-12 14:01 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-5) Current Operating System: Linux debian-ghost 2.6.26-1-486 #1 Thu Aug 28 11:14:57 UTC 2008 i686 Build Date: 26 August 2008 07:32:05PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Sep 12 14:01:58 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) |-->Input Device "Configured Mouse" (==) |-->Input Device "Generic Keyboard" (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts
Re: LVDS not detected by nv driver for Lenovo T61p (nvidia Quadro FX 570M)
Rainer Dorsch wrote: > When I boot the T61p on a port replicator with an external screen attached, I > get > > (II) NV(0): LVDS native size 738x414 > > vs > > (II) NV(0): LVDS native size 1920x1200 > > when I boot the laptop standalone. > What if you boot on a port replicator without the external screen attached? > If not, is this a bug, where should it be reported (against which package)? > xserver-xorg-video-nv, or (better) on bugzilla.freedesktop.org against product Xorg component Driver/Nvidia(free) Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493521: xserver-xorg: can only use half of my video RAM
On Wed, Sep 17, 2008 at 9:27 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote: > As Alex pointed out, the flicker is likely due to the two display > controllers and the accelerator fighting for memory bandwidth. You could > try playing with Option "DisplayPriority". Results in the other bug. zw
Bug#499206: xserver-xorg-video-radeon: R580 + EXA = screen flicker
On Wed, Sep 17, 2008 at 11:15 AM, Zack Weinberg <[EMAIL PROTECTED]> wrote: > So I had to work a little harder than I'd have liked to disable one of > the monitors (disconnect the DVI cable *and* comment out everything > related to it in xorg.conf, including the Virtual line) but yeah, > there's no flicker with EXA and just one monitor. Michael Danzer suggested I try the "DisplayPriority" option. Setting this to "BIOS" does not help. Setting it to "HIGH" seems to cut down on the frequency of all the display glitches I mentioned, but in the past five minutes that the X server's been running, I have seen all of them at least once. (By comparison, they were pretty much happening all the time with the default.) zw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461074: More info
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Mohammed Adnène Trojette escreveu: > On Wed, Jan 16, 2008, André Luís Lopes wrote: >>So, it seems it was really something in 1.1~cvs.20080104.1-1 which >> broke it for me. I'm not sure what was it, but I would guess it could be >> the fix for #444035. > > Hi, the fix for #444035 has been reverted. Does the problem still occurs > with 1.3-2? > > If so, could you send us your xorg.conf, the output of "setxkbmap > -print" and "xmodmap -pk"? First of all, sorry for taking so long to get back to you. I was so busy these last days that I had no time to answer non-work related mail. Anyway, I removed the hold on the previous version and upgraded to version 1.3-2. After that, I restarted X and logged in again and now I'm able to use keycode 49 as my grave accent when they key as pressed alone and as my dead_tilde when holding down my Shift_L key. So, as far I can understand, I would say this bug is fixed for me. Thanks for you work :-) Regards, - -- André Luís Lopes [EMAIL PROTECTED],debian}.org http://www.andrelop.org/blog/ Public GPG KeyID : 9D1B82F6 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjRRbAACgkQW4/i9Z0bgvb2RACfaDhuEQU+hCjny2OaOENfbo52 2HAAn0YJ8bq/a4AAcQ+et4+xcsOStDX9 =0lL5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499206: xserver-xorg-video-radeon: R580 + EXA = screen flicker
On Wed, Sep 17, 2008 at 7:36 AM, Alex Deucher <[EMAIL PROTECTED]> wrote: > This is very likely related to multiple monitors. Please try EXA with > one monitor and see if you still have the same problem. So I had to work a little harder than I'd have liked to disable one of the monitors (disconnect the DVI cable *and* comment out everything related to it in xorg.conf, including the Virtual line) but yeah, there's no flicker with EXA and just one monitor. zw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486925: additional information
On Wed, Sep 17, 2008 at 19:36:57 +0200, Brice Goglin wrote: > Stephen Frazier wrote: > > After some testing I have found that adding "DefaultDepth 24" in the > > Section "Screen" of file xorg.conf will correct the problem with > > s3virge_drv.so not displaying the correctly on my machine. > > You might want to send this update directly to the upstream bug at > https://bugs.freedesktop.org/show_bug.cgi?id=17634 > Well, I said that when I opened the bug already. That said, feel free to add more info there, Stephen. Cheers, Julien -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#461074: marked as done (xkb-data: No dead_tilde using "US Alternative international (former us_intl)" on white MacBook 13")
Your message dated Wed, 17 Sep 2008 20:03:27 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#461074: More info has caused the Debian Bug report #461074, regarding xkb-data: No dead_tilde using "US Alternative international (former us_intl)" on white MacBook 13" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 461074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=461074 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: xkb-data Version: 1.1~cvs.20080104.1-1 Severity: normal *** Please type your report below this line *** Hello, I was using the following in my $HOME/.xmodmap before I upgraded from xkb-data 1.0~cvs.20070916-1 to 1.1~cvs.20080104.1-1 : [EMAIL PROTECTED]:~$ cat .xmodmap keycode 49 = grave dead_tilde [EMAIL PROTECTED]:~$ The above settings would let me use my key identified by "xev" as keycode 49 as my grave accent when they key as pressed alone and as my dead_tilde when holding down my Shift_L key (which is identified by xev as having keycode 50). After the upgrade, the key cannot be used neither as grave nor as dead_tilde. If I map it to another keycode in my $HOME/.xmodmap I can use the key to produce the symbol this anoter keycode is supposed to produce. My laptop is a white 13.3" MacBook identified by dmidecode as : [EMAIL PROTECTED]:~$ sudo dmidecode -t 1 # dmidecode 2.9 SMBIOS 2.4 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Apple Inc. Product Name: MacBook2,1 Version: 1.0 Serial Number: W8723G7VYA2 UUID: 61F9E18A-38B2-B440-A87E-7457DF18863C Wake-up Type: Power Switch SKU Number: System SKUNumber Family: MacBook [EMAIL PROTECTED]:~$ I would be glad to help you to find the what is culprit, but would need some guidance on how I could accomplish that. Regards, -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23-1-686 (SMP w/2 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information -- André Luís Lopes [EMAIL PROTECTED],debian}.org http://www.andrelop.org/blog/ Public GPG KeyID : 9D1B82F6 --- End Message --- --- Begin Message --- On Wed, Sep 17, 2008, André Luís Lopes wrote: >So, as far I can understand, I would say this bug is fixed for me. Happy to hear that! Regards, -- Mohammed Adnène Trojette --- End Message ---
Bug#486925: additional information
Stephen Frazier wrote: > After some testing I have found that adding "DefaultDepth 24" in the > Section "Screen" of file xorg.conf will correct the problem with > s3virge_drv.so not displaying the correctly on my machine. You might want to send this update directly to the upstream bug at https://bugs.freedesktop.org/show_bug.cgi?id=17634 Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: bug 486925 is forwarded to http://bugs.freedesktop.org/show_bug.cgi?id=17634
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > forwarded 486925 http://bugs.freedesktop.org/show_bug.cgi?id=17634 Bug#486925: xorg: only displays top half of KDE screen Noted your statement that Bug has been forwarded to http://bugs.freedesktop.org/show_bug.cgi?id=17634. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499278: xorg: CTRL-ALT-Fn Doesn't work properly
Antoon Pardon wrote: > Package: xorg > Version: 1:7.3+16 > Severity: normal > > > After loging in with gdm, all seems to work fine until I want to > go to a console via CTRL-ALT-Fn. > > Upon doing so, I find that the text console seems to be expanded > vertically, making the two top lines and the bottom line invisible, > seeming to be above and below the screen. > > Going back with CTRL-ALT-F7, the screen is completely black and the > power light indicator of the monitor begins to flikker as if the > computer is turned off or blanked in screensaver mode. Nothing > I do can make the session active again, except for CTRL-ALT-BACKSPACE > that will break off the X-seesion and will give me a gdm inlog screen. > Did this problem appear recently? after upgrading from what to what? Your hardware is pretty recent, it might be good if you could test the latest upstream git, it could be better. You can either build it manually (look at http://bgoglin.livejournal.com/10936.html and replace intel with ati), or just upgrade your X packages to experimental. Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#499209: xserver-xorg-video-radeon: incorrect resolution choice for second monitor
Processing commands for [EMAIL PROTECTED]: > reassign 498571 xserver-xorg-core Bug#498571: xserver-xorg-video-intel: selects wrong resolution at startup Bug reassigned from package `xserver-xorg-video-intel' to `xserver-xorg-core'. > retitle 498571 Xserver shouldn't force the exact same resolution on both > screens by default Bug#498571: xserver-xorg-video-intel: selects wrong resolution at startup Changed Bug title to `Xserver shouldn't force the exact same resolution on both screens by default' from `xserver-xorg-video-intel: selects wrong resolution at startup'. > severity 498571 minor Bug#498571: Xserver shouldn't force the exact same resolution on both screens by default Severity set to `minor' from `normal' > thank you Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486925: additional information
After some testing I have found that adding "DefaultDepth 24" in the Section "Screen" of file xorg.conf will correct the problem with s3virge_drv.so not displaying the correctly on my machine. On another machine that uses vmware_drv.so the screen is displayed correctly with the supplied xorg.conf file. I hope this additional information helps in finding a fix for this problem. Thank you, -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499206: xserver-xorg-video-radeon: R580 + EXA = screen flicker
On Wed, Sep 17, 2008 at 7:36 AM, Alex Deucher <[EMAIL PROTECTED]> wrote: > On Tue, Sep 16, 2008 at 8:25 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote: >> >> With EXA enabled on a Radeon R580 (or possibly an X1900, ATI's numbering >> conventions confuse me) I see several sorts of display flicker: > > This is very likely related to multiple monitors. Please try EXA with > one monitor and see if you still have the same problem. Attempting to turn one display off with e.g. 'xrandr --output DVI-1 --off' causes both displays to lose signal and the X server to go catatonic. It's still running, but all clients hang; strace shows it receiving and dismissing an endless series of SIGALARMs, and it won't respond to anything short of kill -9. zw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#493521: xserver-xorg: can only use half of my video RAM
On Wed, 2008-09-17 at 08:53 -0700, Zack Weinberg wrote: > On Tue, Sep 16, 2008 at 9:56 PM, Brice Goglin <[EMAIL PROTECTED]> wrote: > > Zack Weinberg wrote: > >> (II) RADEON(0): Generation 2 PCI interface, using max accessible memory > >> (II) RADEON(0): Detected total video RAM=524288K, accessible=262144K > >> (PCI BAR=262144K) > >> (--) RADEON(0): Mapped VideoRAM: 262144 kByte (256 bit DDR SDRAM) > >> > > > > I am reading this as: > > * the driver rea somewhere in the registers that the board has 512MB > > * the PCI config space only makes 256 available through I/O MEM > > > > It could mean that the board keeps 256MB available for its own use > > (internal memory management, or DMA from/to the host) but the host > > cannot write/read directly in there. > > Yeah, that's how I read it too. It might be harmless; I'm really only > concerned with it because I wonder if it's a cause of some of the > other problems (like maybe the screen flicker issues would go away if > the X server wasn't having to do something unusually slow with the > frame buffer -- I guess a 3520x1200x32 fb is only 128MB or so, but > still) 3520 * 1200 * 4 / 1024 / 1024 = 16.1133 MB (the log file should mention this and other sizes) The above is harmless other than leaving part of video RAM unused. > The "Cannot get VRAM scratch space" part is more of a worry, honestly; > that seems like it might mess up things the firmware is doing. No, I think it's normal and harmless. As Alex pointed out, the flicker is likely due to the two display controllers and the accelerator fighting for memory bandwidth. You could try playing with Option "DisplayPriority". -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499212: xserver-xorg-video-radeon: rotated display + EXA crashes X server
On Wed, Sep 17, 2008 at 7:41 AM, Alex Deucher <[EMAIL PROTECTED]> wrote: > On Tue, Sep 16, 2008 at 8:52 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote: >> Per the bug I just filed, XAA is painfully slow at drawing a rotated display >> on the hardware I've got, so I tried EXA - but then the X server crashes on >> startup. I'll paste the relevant bit of the server log up here: > > This is a known bug. If you put a rotation in your config, you get a > crash because acceleration is not set up when the rotation is > initialized. When the ordering was changed to fix this, it led to a > worse bug (immediate hard lock), so it was reverted. No one has had > time to sort this out yet. You should be able to rotate once the X > server is up. Yup, rotation is fine once the X server is up, and a rotated display is usable with EXA - I can't tell the difference between the two screens acceleration-wise. zw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 499304 is wishlist
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > severity 499304 wishlist Bug#499304: xserver-xorg: debconf no longer allows setting up monitor properties Severity set to `wishlist' from `important' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499304: xserver-xorg: debconf no longer allows setting up monitor properties
Package: xserver-xorg Version: 1:7.3+15 Severity: important Hello I looked at the debconf templates fo X and I no longer find the options for setting up monitor parameters. There are several reasons why one might need these: - the monitor detection fails. Ideally this should be fixed in the X drivers but people probably would want some workaround until their driver is fixed. Also when using long or otherwise special VGA cables the detection always fails even in otherwise working setups. - the monitor detection works OK but you want to choose the resolution manually. This can be done per user in user settings of some desktops but setting the option globally might be also helpful if the default mode makes the login screen hard to use or such desktop is not installed. Also setting resolution with xrandr does not work with the vesa driver - it can be set only on X start for which I did not find any tool in Debian. This would be also useful for Debian Live where the X configuration is lost on reboot but a debconf option could be easily set based on a boot parameter. Thanks Michal -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2008-09-17 13:03 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1719572 2008-08-26 17:48 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1353 2008-09-17 16:22 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" #Driver "fbdev" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" SubSection "Display" Virtual 1024 768 Depth 24 EndSubSection SubSection "Display" Virtual 1024 768 Depth 16 EndSubSection SubSection "Display" Virtual 1024 768 Depth 15 EndSubSection SubSection "Display" Virtual 1024 768 Depth 8 EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 13629 2008-09-17 16:19 /var/log/Xorg.0.log -rw-r--r-- 1 root root 37301 2008-09-17 16:22 /var/log/Xorg.1.log Contents of most recent Xorg X server log file /var/log/Xorg.1.log: X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-5) Current Operating System: Linux debian-ghost 2.6.26-1-486 #1 Thu Aug 28 11:14:57 UTC 2008 i686 Build Date: 26 August 2008 07:32:05PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Wed Sep 17 16:22:11 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) |-->Input Device "Configured Mouse" (==) |-->Input Device "Generic Keyboard" (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first k
Bug#493521: xserver-xorg: can only use half of my video RAM
On Tue, Sep 16, 2008 at 9:56 PM, Brice Goglin <[EMAIL PROTECTED]> wrote: > Zack Weinberg wrote: >> (II) RADEON(0): Generation 2 PCI interface, using max accessible memory >> (II) RADEON(0): Detected total video RAM=524288K, accessible=262144K >> (PCI BAR=262144K) >> (--) RADEON(0): Mapped VideoRAM: 262144 kByte (256 bit DDR SDRAM) >> > > I am reading this as: > * the driver rea somewhere in the registers that the board has 512MB > * the PCI config space only makes 256 available through I/O MEM > > It could mean that the board keeps 256MB available for its own use > (internal memory management, or DMA from/to the host) but the host > cannot write/read directly in there. Yeah, that's how I read it too. It might be harmless; I'm really only concerned with it because I wonder if it's a cause of some of the other problems (like maybe the screen flicker issues would go away if the X server wasn't having to do something unusually slow with the frame buffer -- I guess a 3520x1200x32 fb is only 128MB or so, but still) The "Cannot get VRAM scratch space" part is more of a worry, honestly; that seems like it might mess up things the firmware is doing. zw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499209: xserver-xorg-video-radeon: incorrect resolution choice for second monitor
On Tue, Sep 16, 2008 at 9:46 PM, Brice Goglin <[EMAIL PROTECTED]> wrote: > > I might be the Xserver core choosing the same resolution at startup (so > that the login screen appears in the middle of both monitors instead of > risking of having it outside one of them). > > You should be able to work around the problem with PreferredMode. See > III.5 of http://wiki.debian.org/XStrikeForce/HowToRandR12 Setting a PreferredMode option for *both* monitors does work around the problem. If I give the option for just the larger monitor, then it tries to drive both of them at 1920x1200, which looks really bizarre on the 1600x1200 screen. I didn't need modelines. Thanks, zw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499212: xserver-xorg-video-radeon: rotated display + EXA crashes X server
On Tue, Sep 16, 2008 at 8:52 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote: > Package: xserver-xorg-video-radeon > Version: 1:6.9.0+git20080826.a3cc1d7a-1 > Severity: normal > > Per the bug I just filed, XAA is painfully slow at drawing a rotated display > on the hardware I've got, so I tried EXA - but then the X server crashes on > startup. I'll paste the relevant bit of the server log up here: This is a known bug. If you put a rotation in your config, you get a crash because acceleration is not set up when the rotation is initialized. When the ordering was changed to fix this, it led to a worse bug (immediate hard lock), so it was reverted. No one has had time to sort this out yet. You should be able to rotate once the X server is up. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499206: xserver-xorg-video-radeon: R580 + EXA = screen flicker
On Tue, Sep 16, 2008 at 8:25 PM, Zack Weinberg <[EMAIL PROTECTED]> wrote: > Package: xserver-xorg-video-radeon > Version: 1:6.9.0+git20080826.a3cc1d7a-1 > Severity: normal > > With EXA enabled on a Radeon R580 (or possibly an X1900, ATI's numbering > conventions confuse me) I see several sorts of display flicker: > > - Most frequent: the mouse pointer appears to vibrate up and down by > about half its vertical height, or has rapidly changing horizontal > stripes drawn over it. > > - Some window boundaries wiggle continuously and rapidly. The effect > appears only at the edges but seems to depend on what is drawn in the > window: a boring gnome-terminal doesn't do it, but OO.o calc did it > a lot. > > - Occasionally the entire display goes to black or garbage for a split > second. > > None of these phenomena occur if I drop back to XAA. > > The problem *might* depend on having both of the card's DVI outputs > active simultaneously; I didn't try EXA until after I got the second > monitor. > > The "most recent X server log file" below is with XAA active. Below > that is a log with EXA active. This is very likely related to multiple monitors. Please try EXA with one monitor and see if you still have the same problem. Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 499278 to xserver-xorg-video-ati
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > reassign 499278 xserver-xorg-video-ati Bug#499278: xorg: CTRL-ALT-Fn Doesn't work properly Bug reassigned from package `xorg' to `xserver-xorg-video-ati'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
reassign 499278 to xserver-xorg-video-ati
# Automatically generated email from bts, devscripts version 2.10.35 reassign 499278 xserver-xorg-video-ati -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499278: xorg: CTRL-ALT-Fn Doesn't work properly
Package: xorg Version: 1:7.3+16 Severity: normal After loging in with gdm, all seems to work fine until I want to go to a console via CTRL-ALT-Fn. Upon doing so, I find that the text console seems to be expanded vertically, making the two top lines and the bottom line invisible, seeming to be above and below the screen. Going back with CTRL-ALT-F7, the screen is completely black and the power light indicator of the monitor begins to flikker as if the computer is turned off or blanked in screensaver mode. Nothing I do can make the session active again, except for CTRL-ALT-BACKSPACE that will break off the X-seesion and will give me a gdm inlog screen. === xorg.conf === # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" BusID "PCI:1:0:0" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection == Xorg.0.log = X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-5) Current Operating System: Linux rcpc42 2.6.24-etchnhalf.1-686 #1 SMP Mon Sep 8 06:19:11 UTC 2008 i686 Build Date: 26 August 2008 07:32:05PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 17 14:19:35 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) |-->Input Device "Configured Mouse" (==) |-->Input Device "Generic Keyboard" (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) RgbPath set to "/etc/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81e3c00 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,29b0 card 1028,0211 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,29b1 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:03:0: chip 8086,29b4 card 1028,0211 rev 02 class 07,80,00 hdr 80 (II) PCI: 00:03:2: chip 8086,29b6 card 1028,0211 re
Bug#499238: xorg.conf and Xorg.0.log
On Wed, Sep 17, 2008 at 01:20:59PM +0200, Julien Cristau wrote: > On Wed, Sep 17, 2008 at 12:16:34 +0200, Antoon Pardon wrote: > > > (II) LoadModule: "mouse" > > (WW) Warning, couldn't open module mouse > > (II) UnloadModule: "mouse" > > (EE) Failed to load module "mouse" (module does not exist, 0) > > (II) LoadModule: "kbd" > > (WW) Warning, couldn't open module kbd > > (II) UnloadModule: "kbd" > > (EE) Failed to load module "kbd" (module does not exist, 0) > > Might explain the problem... Install xserver-xorg-input-mouse and > xserver-xorg-input-kbd. Yes that solved the problem, thanks! Strange that those weren't installed when I upgraded x11-common, xorg, xorg-server and xorg-server-core or on a dist-upgrade. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Request for new video driver
Hi all, I just found an accelerated video driver for SGI O2. It has been developed for netbsd and is available at ftp://ftp.ticklers.org/pub/NetBSD/NetBSD-current/xsrc/xfree/xc/programs/Xserver/hw/xfree86/drivers/crime/ Is there anyone interested in packaging it? I may test the resulting package. Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: forcibly merging 451791 484307
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > forcemerge 451791 484307 Bug#451791: [965G EXA] Fonts and many other items fail to render legibly Bug#484307: gdm: don't see fonts Bug#452268: [965G EXA] all fonts are unreadable Bug#462921: xserver-xorg-video-intel: exa corruption with 965Q Bug#481579: xserver-xorg-video-intel: grub2 splash image causes invisible text Bug#482645: [965GM] rendering problems (missing text/images) with exa composite Bug#483487: xserver-xorg-video-intel: font rendering problem hit me about two weeks ago Bug#495684: [965GM] no (Latin) characters and icons shown at login prompt and in the desktop Bug#496272: [965GM] fonts and menu icons are blank Bug#496543: [82G965] fonts not rendered due to EXA bug Forcibly Merged 451791 452268 462921 481579 482645 483487 484307 495684 496272 496543. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 484307 to xserver-xorg-video-intel
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > reassign 484307 xserver-xorg-video-intel Bug#484307: gdm: don't see fonts Bug reassigned from package `gdm' to `xserver-xorg-video-intel'. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499238: marked as done (xorg: No input possible after upgrade)
Your message dated Wed, 17 Sep 2008 13:20:59 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#499238: xorg.conf and Xorg.0.log has caused the Debian Bug report #499238, regarding xorg: No input possible after upgrade to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 499238: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499238 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: xorg Version: 1:7.3+16 Severity: grave Justification: renders package unusable After upgrading xorg and related packages, the computer no longer responds to mouse movements and keyboard input. It doesn't matter whether I try with gdm or via the console and startx. I tried to build a new xorg.conf with dexconf but that didn't make a difference. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-etchnhalf.1-686 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages xorg depends on: ii gnome-terminal [x-terminal-em 2.22.3-2 The GNOME 2 terminal emulator appl ii libgl1-mesa-glx [libgl1] 7.0.3-5A free implementation of the OpenG ii libglu1-mesa 7.0.3-5The OpenGL utility library (GLU) ii x11-apps 7.3+3 X applications ii x11-session-utils 7.3+1 X session utilities ii x11-utils 7.3+2 X11 utilities ii x11-xfs-utils 7.3+1 X font server utilities ii x11-xkb-utils 7.4+1 X11 XKB utilities ii x11-xserver-utils 7.3+5 X server utilities ii xauth 1:1.0.3-2 X authentication utility ii xfonts-100dpi 1:1.0.0-4 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-4 75 dpi fonts for X ii xfonts-base 1:1.0.0-5 standard fonts for X ii xfonts-scalable 1:1.0.0-6 scalable fonts for X ii xfonts-utils 1:7.4+1X Window System font utility progr ii xinit 1.0.9-2X server initialisation tool ii xkb-data 1.3-2 X Keyboard Extension (XKB) configu ii xserver-xorg 1:7.3+16 the X.Org X server ii xterm [x-terminal-emulator] 235-1 X terminal emulator Versions of packages xorg recommends: ii xorg-docs 1:1.4-2Miscellaneous documentation for th xorg suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On Wed, Sep 17, 2008 at 12:16:34 +0200, Antoon Pardon wrote: > (II) LoadModule: "mouse" > (WW) Warning, couldn't open module mouse > (II) UnloadModule: "mouse" > (EE) Failed to load module "mouse" (module does not exist, 0) > (II) LoadModule: "kbd" > (WW) Warning, couldn't open module kbd > (II) UnloadModule: "kbd" > (EE) Failed to load module "kbd" (module does not exist, 0) Might explain the problem... Install xserver-xorg-input-mouse and xserver-xorg-input-kbd. Cheers, Julien --- End Message ---
Processed: tagging 499238, severity of 499238 is important
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > tags 499238 moreinfo Bug#499238: xorg: No input possible after upgrade There were no tags set. Tags added: moreinfo > severity 499238 important Bug#499238: xorg: No input possible after upgrade Severity set to `important' from `grave' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499238: xorg.conf and Xorg.0.log
xorg.conf # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" EndSection Section "Device" Identifier "Configured Video Device" BusID "PCI:1:0:0" EndSection Section "Monitor" Identifier "Configured Monitor" EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection === Xorg.0.log == X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-5) Current Operating System: Linux rcpc42 2.6.24-etchnhalf.1-686 #1 SMP Mon Sep 8 06:19:11 UTC 2008 i686 Build Date: 26 August 2008 07:32:05PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 17 09:28:10 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) |-->Input Device "Configured Mouse" (==) |-->Input Device "Generic Keyboard" (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi (==) RgbPath set to "/etc/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (II) Open ACPI successful (/var/run/acpid.socket) (II) Loader magic: 0x81e3c00 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 2.0 X.Org XInput driver : 2.0 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.4.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 2.0 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,29b0 card 1028,0211 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,29b1 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:03:0: chip 8086,29b4 card 1028,0211 rev 02 class 07,80,00 hdr 80 (II) PCI: 00:03:2: chip 8086,29b6 card 1028,0211 rev 02 class 01,01,85 hdr 00 (II) PCI: 00:03:3: chip 8086,29b7 card 1028,0211 rev 02 class 07,00,02 hdr 00 (II) PCI: 00:19:0: chip 8086,10bd card 1028,0211 rev 02 class 02,00,00 hdr 00 (II) PCI: 00:1a:0: chip 8086,2937 card 1028,0211 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2938 card 1028,0211 rev 02 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,293c card 1028,0211 rev 02 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,293e card 1028,0211 rev 02 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,2940 card , rev 02 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2934 card 1028,0211 rev 02 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2935 c
Bug#499121: marked as done (PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf8010000/16)
Your message dated Wed, 17 Sep 2008 10:59:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#499121: PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf801/16 has caused the Debian Bug report #499121, regarding PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf801/16 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 499121: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499121 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems --- Begin Message --- Package: xserver-xorg-video-ati Version: 1:6.9.0-1+lenny2 Severity: normal Hello, I'm running lenny on i386 and my Xorg.0.log tells me: (--) PCI:*(3:0:0) ATI Technologies Inc RV370 5B65 [FireGL D1100 (PCIE)] rev 128, Mem @ 0xf000/27, 0xf800/16, I/O @ 0x9000/8 (--) PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf801/16 I tested it with 1:6.9.0-1+lenny2, 1:6.9.0-1+lenny4 and the one in experimental (rebuild it to get it installed) but always have this "unknown chipset". The card has a cradle for the two DVI outputs which are runing as clones after a lenny installation. How to get the chipset known to x.org? # lspci -n ... 03:00.0 0300: 1002:5b65 (rev 80) 03:00.1 0380: 1002:5b75 (rev 80) ... # lspci -vv ... 03:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B65 [FireGL D1100 (PCIE)] (rev 80) Subsystem: ATI Technologies Inc Device 0402 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: radeonfb 03:00.1 Display controller: ATI Technologies Inc Device 5b75 (rev 80) Subsystem: ATI Technologies Inc Device 0403 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- --- End Message --- --- Begin Message --- Noèl Köthe wrote: > Am Dienstag, den 16.09.2008, 13:29 +0200 schrieb Julien Cristau: > > >>> Do you need more information? >>> >>> >> Is there an actual problem? >> > > Sorry for being unclear.:( > > I just want to help with the information to get this chipset into the > database so its not unknown anymore. > > If it doesn't make any sense then just close it. > This secondary PCI id is just used by old windows to enable dual-monitor support IIRC. Xorg doesn't need it, only the primary device is used (and known). The secondary PCI id is probably missing from the pci id database (http://pci-ids.ucw.cz/iii/), but it doesn't matter for us. Brice --- End Message ---
Bug#499238: xorg: No input possible after upgrade
Antoon Pardon wrote: > Package: xorg > Version: 1:7.3+16 > Severity: grave > Justification: renders package unusable > > > After upgrading xorg and related packages, the computer no > longer responds to mouse movements and keyboard input. > > It doesn't matter whether I try with gdm or via the console > and startx. I tried to build a new xorg.conf with dexconf but > that didn't make a difference. > > If you want us to debug anything, we need at least your xorg.conf and Xorg.0.log... Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499238: xorg: No input possible after upgrade
Hello Antoon & XOrg maint, I'm experiencing a similar issue since the last week or so, see #499198. I gave the reason to a kernel problem, since not even a remote access via SSH is possible, and nothing is written to system logs (so it's something "bigger" than xorg). Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499238: xorg: No input possible after upgrade
Package: xorg Version: 1:7.3+16 Severity: grave Justification: renders package unusable After upgrading xorg and related packages, the computer no longer responds to mouse movements and keyboard input. It doesn't matter whether I try with gdm or via the console and startx. I tried to build a new xorg.conf with dexconf but that didn't make a difference. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-etchnhalf.1-686 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages xorg depends on: ii gnome-terminal [x-terminal-em 2.22.3-2 The GNOME 2 terminal emulator appl ii libgl1-mesa-glx [libgl1] 7.0.3-5A free implementation of the OpenG ii libglu1-mesa 7.0.3-5The OpenGL utility library (GLU) ii x11-apps 7.3+3 X applications ii x11-session-utils 7.3+1 X session utilities ii x11-utils 7.3+2 X11 utilities ii x11-xfs-utils 7.3+1 X font server utilities ii x11-xkb-utils 7.4+1 X11 XKB utilities ii x11-xserver-utils 7.3+5 X server utilities ii xauth 1:1.0.3-2 X authentication utility ii xfonts-100dpi 1:1.0.0-4 100 dpi fonts for X ii xfonts-75dpi 1:1.0.0-4 75 dpi fonts for X ii xfonts-base 1:1.0.0-5 standard fonts for X ii xfonts-scalable 1:1.0.0-6 scalable fonts for X ii xfonts-utils 1:7.4+1X Window System font utility progr ii xinit 1.0.9-2X server initialisation tool ii xkb-data 1.3-2 X Keyboard Extension (XKB) configu ii xserver-xorg 1:7.3+16 the X.Org X server ii xterm [x-terminal-emulator] 235-1 X terminal emulator Versions of packages xorg recommends: ii xorg-docs 1:1.4-2Miscellaneous documentation for th xorg suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#499121: PCI: (3:0:1) ATI Technologies Inc unknown chipset (0x5b75) rev 128, Mem @ 0xf8010000/16
Am Dienstag, den 16.09.2008, 13:29 +0200 schrieb Julien Cristau: > > Do you need more information? > > > Is there an actual problem? Sorry for being unclear.:( I just want to help with the information to get this chipset into the database so its not unknown anymore. If it doesn't make any sense then just close it. -- Noèl Köthe Debian GNU/Linux, www.debian.org signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
