|
Bugzilla – Full Text Bug Listing |
|
Description
Pavel pavel
2009-03-09 13:30:05 UTC
Created attachment 278075 [details]
/etc/X11/xorg.conf
This happens on my machines as well: Custom Built openSUSE 11.1 + KDE 4.2 (factory) nVidia GeForce 8600 GT MacBook Pro openSUSE 11.1 + KDE 4.2 (factory) ATI Radeon X1600 Current workaround is to downgrade, from the openSUSE 11.1 OSS repo, to the following RPMs: xorg-x11-server-7.4-11.5 xorg-x11-driver-input-7.4-17.3 (only on MacBookPro) xorg-x11-driver-video-7.4-19.4 (only on MacBookPro) xorg-x11-driver-video-radeonhd-1.2.3_081202_ed532a7-1.1 Once the above RPMs are downgraded, X works. This includes full KDE 4.2 desktop effects on both computer systems. I will be attaching the Xorg.0.log files for the failed X session as well has the xorg.conf for the Custom Built machine. Created attachment 278083 [details]
Xorg.0.log file for failed X startup after upgrading
Created attachment 278085 [details]
X configuration file for the Custom Built machine
i've tried to downgrade... but it doesn't help me.. Created attachment 278088 [details]
hwinfo --gfx
Created attachment 278089 [details]
Xorg.1.log
(II) Loading extension MIT-SCREEN-SAVER
(EE) module ABI major version (5) doesn't match the server's version (4)
(EE) Failed to load module "intel" (module requirement mismatch, 0)
(EE) No drivers available.
Created attachment 278090 [details]
rpm --changelog -q libdrm | head -n3
Created attachment 278091 [details]
rpm --changelog -q Mesa | head -n3
Created attachment 278092 [details]
rpm --changelog -q xorg-x11-driver-input | head -n3
Created attachment 278093 [details]
rpm --changelog -q xorg-x11-driver-video | head -n3
Created attachment 278094 [details]
rpm --changelog -q xorg-x11-server | head -n3
(In reply to comment #3) > Created an attachment (id=278083) [details] > Xorg.0.log file for failed X startup after upgrading This is nvidia, not intel driver. No idea if nvidia driver already works with xorg-server 1.6. (In reply to comment #7) > Created an attachment (id=278089) [details] > Xorg.1.log > > (II) Loading extension MIT-SCREEN-SAVER > (EE) module ABI major version (5) doesn't match the server's version (4) > (EE) Failed to load module "intel" (module requirement mismatch, 0) > (EE) No drivers available. You're mixing incompatible xorg-x11-server/xorg-x11-driver-input packages. Either use the packgaes from X11:XOrg or 11.1 DVD. Don't mix them. INVALID. (In reply to comment #13) > (In reply to comment #3) > > Created an attachment (id=278083) [details] [details] > > Xorg.0.log file for failed X startup after upgrading > > This is nvidia, not intel driver. No idea if nvidia driver already works > with xorg-server 1.6. It was my understanding that this bug report entry was reporting a failure in the Xorg packages in the X11:Xorg repo and not a report for a specific video card. The comments I made for this entry was to show that this bug is not only effecting the OP video card but nvidia (with nvidia driver) as well as ati video card (with radeonhd and fglrx) driver. Therefore, this bug is, IMO, applicable to intel, nvidia and ati (via radeonhd). If the problem is simply that the xorg-server in X11:Xorg is simply too new for the nvidia driver, I can accept that. I will downgrade Xorg on that machine. However, the problem still occurs on the MacBookPro that uses the radeonhd driver. Correct me if I am wrong, but since xorg-x11-driver-video-radeonhd is provided by X11:Xorg, then this issue must surely still be valid? Hm.. I've just update all rpm URL: http://download.opensuse.org/repositories/X11%3a/XOrg/openSUSE_11.1/ and now after normal boot i get black screen after safe mode boot i get black screen with cursor.. (cursor can move) but in 10-20 seconds pointer hangs... and black screen remaining.... it's strange and Fn key Fn+F5 (on\off bluetooth working...) Who can fix this? PS. i uploaded video stream, which i've just recorded... look here http://www.youtube.com/watch?v=8egaLJ6wPBE Pavel, so even failsafe mode hangs, i.e. fbdev or vesa driver. Can't you boot into runlevel 3 and provide the latest logfile /var/log/Xorg.0.log? Alvin, could you provide logs for radeonhd driver? This driver should work with xorg-server 1.6, yes. Stefan, ok.. i'll do it.. Created attachment 278163 [details]
Xorg.0.log
Created attachment 278165 [details]
Xorg.0.log
it's after failsave mode
(In reply to comment #20) > Created an attachment (id=278163) [details] > Xorg.0.log hangs ... (**) intel(0): Depth 24, (--) framebuffer bpp 32 (==) intel(0): RGB weight 888 (==) intel(0): Default visual is TrueColor (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM (--) intel(0): Chipset: "965GM" (--) intel(0): Linear framebuffer at 0xE0000000 (--) intel(0): IO registers at addr 0xF8100000 (WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB (==) intel(0): Using EXA for acceleration (II) intel(0): 2 display pipes available. (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Module "ddc" already built-in (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Module "i2c" already built-in Could be a duplicate of Bug #480374. (In reply to comment #21) > Created an attachment (id=278165) [details] > Xorg.0.log > > it's after failsave mode ... doesn't hang. > Could be a duplicate of Bug #480374. To make sure could you update to latest xorg-x11-driver-video package? Latest RPM changelog entry: * Mon Mar 9 14:36:32 CET 2009 - sndirsch@suse.de - removed xf86-video-intel-sdvo_detect.diff due to a severe regression in G45 startup (bnc #480374) yes.. i 've just tried it (30 minutes ago).. and i get black screen yet... Ok. Let's wait for the feedback by Alvin. See comment #18. ps. i also have compiz turned on... and 3d acceleartion on.. (In reply to comment #25) > Ok. Let's wait for the feedback by Alvin. See comment #18. Unfortunately, I don't have the laptop with me right now (I left it at home). I will get the logs posted in a couple of hours. Just to confirm, I should include the failed Xorg.0.log file. Should I also include the other files (hwinfo, changelog of libdrm, xorg-x11-server, etc.)? i'll repeat that earlier (in february) all updates from X11\Xorg repo works for me! (http://download.opensuse.org/repositories/X11%3a/XOrg/openSUSE_11.1/) but since Marth after updating last builds... i get black screen.. so.. any sugguestions to return Last build in Marth 2009 of these rpms for me? :) Alvin, including the failed Xorg.0.log file should be enough. Created attachment 278207 [details]
X log file of failed X startup on a MacBook Pro + radeonhd
Attached is the Xorg.0.log file for the failed startup of X.
The system is:
openSUSE 11.1 + KDE 4.2 (factory)
Mobility Radeon X1600
As with the OP, that last successful upgrade from X11:Xorg was around the end of February 2009. Since then, the following packages needed to be downgrade to the versions in the openSUSE OSS repo:
xorg-x11-server
xorg-x11-driver-input
xorg-x11-driver-video
xorg-x11-driver-video-radeonhd
hwinfo --gfx reports:
25: PCI 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_1002_71c5
Unique ID: VCu0.Itj4koQ1gi0
Parent ID: vSkL.rxAOeWuq8i6
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "Apple MacBook Pro"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x71c5 "Mobility Radeon X1600"
SubVendor: pci 0x106b "Apple Computer Inc."
SubDevice: pci 0x0080 "MacBook Pro"
Memory Range: 0x80000000-0x8fffffff (rw,prefetchable)
I/O Ports: 0x3000-0x3fff (rw)
Memory Range: 0x98300000-0x9830ffff (rw,non-prefetchable)
Memory Range: 0x98320000-0x9833ffff (ro,prefetchable,disabled)
IRQ: 10 (no events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00001002d000071C5sv0000106Bsd00000080bc03sc00i00"
Driver Info #0:
XFree86 v4 Server Module: radeonhd
Driver Info #1:
XFree86 v4 Server Module: radeonhd
3D Support: yes
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #9 (PCI bridge)
Primary display adapter: #25
> (II) RADEONHD(0): LVDS 24Bit: 0x0 > (II) RADEONHD(0): LVDS FPDI: 0x0 > (II) RADEONHD(0): LVDS Temporal Dither : 0x1 > (II) RADEONHD(0): LVDS Spatial Dither : 0x1 > (II) RADEONHD(0): LVDS Grey Level: 0x2 > (II) RADEONHD(0): AtomBIOS returned 2 Grey Levels > (--) RADEONHD(0): Detected a 18bit dual link panel. > (--) RADEONHD(0): Attaching Output LVDS to Connector PANEL > (--) RADEONHD(0): Attaching Output DAC B to Connector DVI-I 1 > (==) RADEONHD(0): Setting TMDS A to incoherent > (--) RADEONHD(0): Attaching Output TMDS A to Connector DVI-I 1 Rüdiger Oertel had exactly the same issue. On Sat, Mar 07, 2009 at 11:48:04AM +0100, Ruediger Oertel wrote: > Hi, > > since the latest update in factory, the xserver does not > come up anymore with the radeonhd driver, > neither with the package from factory nor with the git compiled one. > > last lines in Xorg.0.log are: > > (II) RADEONHD(0): LVDS 24Bit: 0x0 > (II) RADEONHD(0): LVDS FPDI: 0x0 > (II) RADEONHD(0): LVDS Temporal Dither : 0x1 > (II) RADEONHD(0): LVDS Spatial Dither : 0x0 > (II) RADEONHD(0): LVDS Grey Level: 0x2 > (II) RADEONHD(0): AtomBIOS returned 2 Grey Levels > (--) RADEONHD(0): Detected a 18bit dual link panel. > (--) RADEONHD(0): Attaching Output LVDS to Connector PANEL > (--) RADEONHD(0): Attaching Output DAC B to Connector DVI-I 1 > (--) RADEONHD(0): Attaching Output TMDS A to Connector DVI-I 1 I think he didn't open a bugreport yet. Alvin, please open a seperate bugreport. Ste(In reply to comment #31) > > (II) RADEONHD(0): LVDS 24Bit: 0x0 > > (II) RADEONHD(0): LVDS FPDI: 0x0 > > (II) RADEONHD(0): LVDS Temporal Dither : 0x1 > > (II) RADEONHD(0): LVDS Spatial Dither : 0x1 > > (II) RADEONHD(0): LVDS Grey Level: 0x2 > > (II) RADEONHD(0): AtomBIOS returned 2 Grey Levels > > (--) RADEONHD(0): Detected a 18bit dual link panel. > > (--) RADEONHD(0): Attaching Output LVDS to Connector PANEL > > (--) RADEONHD(0): Attaching Output DAC B to Connector DVI-I 1 > > (==) RADEONHD(0): Setting TMDS A to incoherent > > (--) RADEONHD(0): Attaching Output TMDS A to Connector DVI-I 1 > > Rüdiger Oertel had exactly the same issue. > > On Sat, Mar 07, 2009 at 11:48:04AM +0100, Ruediger Oertel wrote: > > Hi, > > > > since the latest update in factory, the xserver does not > > come up anymore with the radeonhd driver, > > neither with the package from factory nor with the git compiled one. > > > > last lines in Xorg.0.log are: > > > > (II) RADEONHD(0): LVDS 24Bit: 0x0 > > (II) RADEONHD(0): LVDS FPDI: 0x0 > > (II) RADEONHD(0): LVDS Temporal Dither : 0x1 > > (II) RADEONHD(0): LVDS Spatial Dither : 0x0 > > (II) RADEONHD(0): LVDS Grey Level: 0x2 > > (II) RADEONHD(0): AtomBIOS returned 2 Grey Levels > > (--) RADEONHD(0): Detected a 18bit dual link panel. > > (--) RADEONHD(0): Attaching Output LVDS to Connector PANEL > > (--) RADEONHD(0): Attaching Output DAC B to Connector DVI-I 1 > > (--) RADEONHD(0): Attaching Output TMDS A to Connector DVI-I 1 > > I think he didn't open a bugreport yet. Alvin, please open a seperate > bugreport. Stefan, what can you recommend me with my trouble? > Stefan, what can you recommend me with my trouble?
Switch back to xorg-x11-server/xorg-x11-driver-video/xorg-x11-driver-input combo from openSUSE 11.1. We'll try to reproduce this issue on one of our 965GM machines.
(In reply to comment #33) > > Stefan, what can you recommend me with my trouble? > > Switch back to xorg-x11-server/xorg-x11-driver-video/xorg-x11-driver-input > combo from openSUSE 11.1. We'll try to reproduce this issue on one of our 965GM > machines. I've already tried... but it didn't help me... I am observing the same issue with Radeon X1650 (non-mobile, PCIExpress gfx card by Gigabyte).
X.org ends in black screen, with keyboard/mouse unresponsive; it is not possible to get out of X via keyboard, but the kernel seems to be alive; it can be switched off via ACPI event, and the screen sometimes even reappers during the shutdown.
I have tried with 'radeonhd' as well as 'radeon' and 'vesa', all ended up in the same way, except that 'vesa' did not block the keyboard, but was not able to restore text mode anyway after Ctrl-Alt-Backspace.
The 'radeonhd' driver, however, printed out some debugging data that might be of interest (or maybe not), please see them attached.
Output of 'hwinfo --gfxcard' follows:
30: PCI 100.0: 0300 VGA compatible controller(VGA)
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_1002_71c7
Unique ID: VCu0.iLksmpVN1G9
Parent ID: _Znp.NfWwNi5KJ96
SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "ATI Radeon X1650"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x71c7 "Radeon X1650"
SubVendor: pci 0x1458 "Giga-byte Technology"
SubDevice: pci 0x2160
Revision: 0x9e
Memory Range: 0xd0000000-0xdfffffff (rw,prefetchable)
Memory Range: 0xfdaf0000-0xfdafffff (rw,non-prefetchable)
I/O Ports: 0xde00-0xdeff (rw)
Memory Range: 0xfda00000-0xfda1ffff (ro,prefetchable,disabled)
IRQ: 18 (120065 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v00001002d000071C7sv00001458sd00002160bc03sc00i00"
Driver Info #0:
XFree86 v4 Server Module: radeonhd
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #9 (PCI bridge)
31: PCI 100.1: 0380 Display controller
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_1002_71e7
Unique ID: NXNs.jFy8g5oIWxC
Parent ID: _Znp.NfWwNi5KJ96
SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:01:00.1
SysFS BusID: 0000:01:00.1
Hardware Class: graphics card
Model: "ATI RV535 [Radeon X1650 Series]"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x71e7 "RV535 [Radeon X1650 Series]"
SubVendor: pci 0x1458 "Giga-byte Technology"
SubDevice: pci 0x2161
Revision: 0x9e
Memory Range: 0xfdae0000-0xfdaeffff (rw,non-prefetchable)
Module Alias: "pci:v00001002d000071E7sv00001458sd00002161bc03sc80i00"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #9 (PCI bridge)
Created attachment 278261 [details]
X log file by radeonhd on Radeon X1650
Guys, could you please discuss the radeon/radeonhd driver issues in a seperate bugreport? Thanks. (In reply to comment #31) > > (II) RADEONHD(0): LVDS 24Bit: 0x0 > > (II) RADEONHD(0): LVDS FPDI: 0x0 > > (II) RADEONHD(0): LVDS Temporal Dither : 0x1 > > (II) RADEONHD(0): LVDS Spatial Dither : 0x1 > > (II) RADEONHD(0): LVDS Grey Level: 0x2 > > (II) RADEONHD(0): AtomBIOS returned 2 Grey Levels > > (--) RADEONHD(0): Detected a 18bit dual link panel. > > (--) RADEONHD(0): Attaching Output LVDS to Connector PANEL > > (--) RADEONHD(0): Attaching Output DAC B to Connector DVI-I 1 > > (==) RADEONHD(0): Setting TMDS A to incoherent > > (--) RADEONHD(0): Attaching Output TMDS A to Connector DVI-I 1 > > Rüdiger Oertel had exactly the same issue. > > On Sat, Mar 07, 2009 at 11:48:04AM +0100, Ruediger Oertel wrote: > > (II) RADEONHD(0): LVDS 24Bit: 0x0 > > (II) RADEONHD(0): LVDS FPDI: 0x0 > > (II) RADEONHD(0): LVDS Temporal Dither : 0x1 > > (II) RADEONHD(0): LVDS Spatial Dither : 0x0 > > (II) RADEONHD(0): LVDS Grey Level: 0x2 > > (II) RADEONHD(0): AtomBIOS returned 2 Grey Levels > > (--) RADEONHD(0): Detected a 18bit dual link panel. > > (--) RADEONHD(0): Attaching Output LVDS to Connector PANEL > > (--) RADEONHD(0): Attaching Output DAC B to Connector DVI-I 1 > > (--) RADEONHD(0): Attaching Output TMDS A to Connector DVI-I 1 > > I think he didn't open a bugreport yet. Alvin, please open a seperate > bugreport. I believe I found one that already exists. AFAICT, it was opened 1-2 days ago on the 8th of March. https://bugzilla.novell.com/show_bug.cgi?id=483244 Yes, that's the correct one. *** Bug 483756 has been marked as a duplicate of this bug. *** (In reply to comment #33) > > Stefan, what can you recommend me with my trouble? > > Switch back to xorg-x11-server/xorg-x11-driver-video/xorg-x11-driver-input > combo from openSUSE 11.1. We'll try to reproduce this issue on one of our 965GM > machines. Have you already test this issue on one of your 965GM machines? No, unfortunately I won't have access to 965GM until Wednesday next week. I've just updated intel driver to 2.6.99.901 (2.7 prerelease) in X11.XOrg/xorg-x11-driver-video. Can you still reproduce this issue with this driver release? (In reply to comment #42) > No, unfortunately I won't have access to 965GM until Wednesday next week. > > I've just updated intel driver to 2.6.99.901 (2.7 prerelease) in > X11.XOrg/xorg-x11-driver-video. Can you still reproduce this issue with this > driver release? I can't check it, because download.opensuse.org is DOWN now... (In reply to comment #43) > (In reply to comment #42) > > No, unfortunately I won't have access to 965GM until Wednesday next week. > > > > I've just updated intel driver to 2.6.99.901 (2.7 prerelease) in > > X11.XOrg/xorg-x11-driver-video. Can you still reproduce this issue with this > > driver release? > > I can't check it, because download.opensuse.org is DOWN now... I've just checked.. the result is the same - it doesn't work... Every time after XServer had start I got black screen..) PS. I want repeat that in february it was Ok after updating through repo... but since Marth I've been getting black screen... Hi all. I'm sorry to write at this point but I have this problem with nvidia driver since I update x11-server and driver-video on 5 and 7th Mars. I can't use anything related with X. I change driver to vesa,fbdev...anything and all is the same: black screen and hard reset. Now I downgrade 3 files I had (backup) from 17th febrary: x11-server,driver-imput and driver-video.Install again nvidia driver (I compile myself) and voila... I can see again my kde4 desk.Also cube works... ;) I think it is a serious problem we have. Luck to X-team Regards Chema (In reply to comment #45) > Hi all. > I'm sorry to write at this point but I have this problem with nvidia driver > since I update x11-server and driver-video on 5 and 7th Mars. I can't use > anything related with X. I change driver to vesa,fbdev...anything and all is > the same: black screen and hard reset. > Now I downgrade 3 files I had (backup) from 17th febrary: > x11-server,driver-imput and driver-video.Install again nvidia driver (I compile > myself) and voila... > I can see again my kde4 desk.Also cube works... ;) > I think it is a serious problem we have. > Luck to X-team > Regards > Chema hm... can you share this rpm's with me??) I have no problem Pavel but I think you use 86_64 and me 86_32... Do you want them? Regards Chema hm... i said that you have analogical problem with this... (black screen) ?! ah( i have 86_64.... it won't install in my OS... (In reply to comment #45) > Hi all. > I'm sorry to write at this point but I have this problem with nvidia driver > since I update x11-server and driver-video on 5 and 7th Mars. I can't use > anything related with X. I change driver to vesa,fbdev...anything and all is > the same: black screen and hard reset. > Now I downgrade 3 files I had (backup) from 17th febrary: This was before we updated to xorg-server 1.6. > x11-server,driver-imput and driver-video.Install again nvidia driver (I compile > myself) and voila... xorg-x11-driver-video is irrelevant if you use the nvidia driver. Well Stefan,I know I use nvidia and 86_32 system but I have the same problem than Pavel. I don't know if you prefer I open an other bug. Today I see there are new x11 rpm's on Factory.I'm afraid to use then now... Regards Chema not working (all updates) for me on 14.03.09.... :( - black screen! Can't reproduce this issue on my GM45 machine (965 family). I've installed openSUSE 11.1-x86_64 + updated it with all current packages from X11:XOrg. Even after updating to 2.6.29 kernel from factory X still starts fine. Need to close this one as WORKSFORME. If you still have this problem, please report it upstream. --- I'm afraid such driver issues need to be addressed by Intel's Linux driver development team. Thus I would like to ask you to report this issue upstream on bugs.freedesktop.org according to http://intellinuxgraphics.org/how_to_report_bug.html and add the following Bugzilla accounts to Cc: eich@pdx.freedesktop.org kent.liu@intel.com quanxian.wang@intel.com sndirsch@suse.de You'll need to register for an account on bugs.freedesktop.org first, in case you don't have one yet. Thanks. --- No, I won't handle issues with other drivers in this bugreport. these lines i found in /var/log/messages: Mar 20 00:12:54 linux-trdb gdm[3285]: WARNING: GdmDisplay: display lasted 0.403707 seconds Mar 20 00:12:55 linux-trdb gdm[3285]: WARNING: GdmDisplay: display lasted 0.295122 seconds Mar 20 00:12:55 linux-trdb gdm[3285]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors Any advices how can i fix my trouble? Stefan(In reply to comment #53) > Can't reproduce this issue on my GM45 machine (965 family). I've installed > openSUSE 11.1-x86_64 + updated it with all current packages from X11:XOrg. Even > after updating to 2.6.29 kernel from factory X still starts fine. Need to close > this one as WORKSFORME. If you still have this problem, please report it > upstream. > > --- > I'm afraid such driver issues need to be addressed by Intel's Linux > driver development team. Thus I would like to ask you to report this > issue upstream on bugs.freedesktop.org according to > > http://intellinuxgraphics.org/how_to_report_bug.html > > and add the following Bugzilla accounts to Cc: > > eich@pdx.freedesktop.org > kent.liu@intel.com > quanxian.wang@intel.com > sndirsch@suse.de > > You'll need to register for an account on bugs.freedesktop.org > first, in case you don't have one yet. Thanks. > --- > > No, I won't handle issues with other drivers in this bugreport. PS. in Xorg.0.log - there are no errors.... >these lines i found in /var/log/messages: > >Mar 20 00:12:54 linux-trdb gdm[3285]: WARNING: GdmDisplay: display lasted >0.403707 seconds >Mar 20 00:12:55 linux-trdb gdm[3285]: WARNING: GdmDisplay: display lasted >0.295122 seconds >Mar 20 00:12:55 linux-trdb gdm[3285]: WARNING: GdmLocalDisplayFactory: maximum >number of X display failures reached: check X server log for errors This means gdm tried several times to start the Xserver, but failed. >Any advices how can i fix my trouble? Not at all. I suggest to go back to X.Org packages of openSUSE 11.1 and maybe try again with openSUSE 11.2 Beta1. PS. in Xorg.0.log - there are no errors.... Probably it didn't come up in time (hangs somewehere), so gdm gave up. (In reply to comment #56) > >these lines i found in /var/log/messages: > > > >Mar 20 00:12:54 linux-trdb gdm[3285]: WARNING: GdmDisplay: display lasted > >0.403707 seconds > >Mar 20 00:12:55 linux-trdb gdm[3285]: WARNING: GdmDisplay: display lasted > >0.295122 seconds > >Mar 20 00:12:55 linux-trdb gdm[3285]: WARNING: GdmLocalDisplayFactory: maximum > >number of X display failures reached: check X server log for errors > > This means gdm tried several times to start the Xserver, but failed. > > >Any advices how can i fix my trouble? > > Not at all. I suggest to go back to X.Org packages of openSUSE 11.1 and maybe > try again with openSUSE 11.2 Beta1. > > PS. in Xorg.0.log - there are no errors.... > > Probably it didn't come up in time (hangs somewehere), so gdm gave up. with opensuse 11.1 X.Org packages (from dvd) it works... but i have hangs of pc when trying to launch any opengl application... (any game, google earth, etc...) ps. when i was upgrading all from Xorg\X11 repo in february everything was working fine!... So any ideas or close the topic? The latter. It wasn't me who reopened it. Pavel (still with us, I hope?), please check if the problem is the same as with bug #487621 (symptoms: black screen and blocked console in modes higher than 1600x1200 through DVI; lower modes and VGA work fine). Reopening this bug, assigned to me (not that I am able to fix it, unfortunately); if we find it is the same problem as #487621, I will make it a duplicate. Comment on attachment 278165 [details]
Xorg.0.log
Changed MIME type to make the file readable in normal viewer (bad bugzilla, no biscuit!).
Could it be, that on all of these machines hald is not running? Thus mouse not working and keyboard falling back to pre-XKB ... Created attachment 282479 [details]
with_last_xorg-imput_file
Hi again.
I updated yesterday my system and the same problem continues...
I changed my xorg.conf to low modes but I didn't saw any difference.
I must downgraded to 17 feb. files again.
I send you 2 xorg.log I have with the new xorg files I updated yesterday.
The difference is one has all new files and the other has old xorg_imput rpm. (I try to run with it). I saw black screen in both changes...
Also I send you my hwinfo --gfx
28: PCI 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.318]
UDI: /org/freedesktop/Hal/devices/pci_10de_421
Unique ID: VCu0.YsKCOWb68p0
Parent ID: vSkL.695oDIffHYA
SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "nVidia GeForce 8500 GT"
Vendor: pci 0x10de "nVidia Corporation"
Device: pci 0x0421 "GeForce 8500 GT"
SubVendor: pci 0x1acc
SubDevice: pci 0x848d
Revision: 0xa1
Driver: "nvidia"
Driver Modules: "nvidia"
Memory Range: 0xfd000000-0xfdffffff (rw,non-prefetchable)
Memory Range: 0xc0000000-0xdfffffff (rw,prefetchable)
Memory Range: 0xfa000000-0xfbffffff (rw,non-prefetchable)
I/O Ports: 0xbc00-0xbc7f (rw)
Memory Range: 0xfe8e0000-0xfe8fffff (ro,prefetchable,disabled)
IRQ: 16 (101219 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v000010DEd00000421sv00001ACCsd0000848Dbc03sc00i00"
Driver Info #0:
XFree86 v4 Server Module: nv
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #10 (PCI bridge)
Primary display adapter: #28
**************
Regards
Chema
Created attachment 282480 [details]
with_old_xorg-imput_file
It doesn't seem to be HAL related, otherwise evdev wouldn't have been loaded at all. Chema, you're using the NVIDIA driver. If it results in a black screen we can't do anything here. nv driver would be a better choice. (In reply to comment #65) > Created an attachment (id=282480) [details] > with_old_xorg-imput_file This cannot work it's the wrong ABI version. Well Stefan,I know nvidia driver is not "public" but I send this info because is possible the new changes on xorg-server than make errors to Pavel are the same than make errors with me and we use differents systems (x86_64 and x86_32) and differents cards graphics. If you think that if I use nv driver and kernel-2.6.29-rc8-5-default nv's modules from factory I have not problems I do it... Do you want I make a changes from nvidia to nv and send you the result? Regards Chema > Do you want I make a changes from nvidia to nv and send you the result?
If this is an option for you, this would be appreciated, yes. But be aware that you need to uninstall and reinstall later again the NVIDIA driver. Otherwise you're testing a messed up system.
Well I'll try to do but I don't see any nv driver compatible with my new kernel-2.6.29-rc8-5-default Regards Chema You don't need any kernel support for nv driver. This is more an issue if you use the NVIDIA driver. Hi again. I'm sorry.You have reason I don't need any modules,only xorg-x11-video rpm. Well I do any probes and send you a log. All goes wrong.I can't see anything than black screen. Regards Chema Created attachment 282542 [details]
testing with new X server and nv driver
(II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Module "ddc" already built-in (--) NV(0): Connector map: (--) NV(0): Bus 0 -> DAC1 (--) NV(0): Bus 0 -> SOR0 (--) NV(0): Bus 1 -> DAC2 (--) NV(0): Load detection: 340 (II) NV(0): I2C bus "I2C0" initialized. (II) NV(0): Output VGA1 using monitor section Monitor[0] (**) NV(0): Option "PreferredMode" "1280x1024" (II) NV(0): Output DVI0 has no monitor section (II) NV(0): I2C bus "I2C1" initialized. (II) NV(0): Output VGA2 has no monitor section ************ The same when change vesa driver with nv driver. WITH ALL THIS CHANGES,ALLWAYS BLACK SCREEN AND HARD RESET ==> So it seems to be in DDC probing. Seeing the same or similar problem with my Intel GM45 machine (Sony Vaio laptop). Running Factory Live CD (compiled on March 25th) and live CD simply boots into black screen. Impossible to kill X or switch consoles, only thing that computer responds to in power button to shut down computer. Sounds like the same problem to me. This issue could be related to new EEDID probing in xorg-server 1.6. Then it would be monitor/display panel related. Does this issue still occur when adding Option "NoDDC2" to 'Section "Device"' or your /etc/X11/xorg.conf? (In reply to comment #75) > This issue could be related to new EEDID probing in xorg-server 1.6. Then it > would be monitor/display panel related. Does this issue still occur when adding > > Option "NoDDC2" > > to 'Section "Device"' or your /etc/X11/xorg.conf? Ok.. i'll check it.. Just tested with "NoDDC2" - this does not help, screen remains black. Rolled back to 11.1 xorg packages. Thanks for the feedback. A logfile with *and* without this option would have been even more helpful. But now you're already back to original 11.1 packages. :-( I've just tested with "NoDDC2" option and it doesn't work.. i'm getting black screen.. So no changes in the logfile with this option? (In reply to comment #80) > So no changes in the logfile with this option? i can't check it.. sorry Why? Also already back to original 11.1 packages? (In reply to comment #82) > Why? Also already back to original 11.1 packages? yes, and then update some packages from repo "11.1 : update".... Mattias could reproduce this issue on 945GME ... (In reply to comment #84) > Mattias could reproduce this issue on 945GME ... ? who is Mattias? Matthias Hopf <mhopf@novell.com> (In reply to comment #86) > Matthias Hopf <mhopf@novell.com> he can reproduce "black screen" effect too, yes? Yes, I think so. And if I recall correctly he workarounded it with NoDDC. At this time I didn't know that there is a NoDDC2 option. It looked to me that there were only changes for the DDC2 path, so I proposed to you to try with NoDDC2. (In reply to comment #88) > Yes, I think so. And if I recall correctly he workarounded it with NoDDC. At > this time I didn't know that there is a NoDDC2 option. > > It looked to me that there were only changes for the DDC2 path, so I proposed > to you to try with NoDDC2. i've already checked it.. - https://bugzilla.novell.com/show_bug.cgi?id=483424#c79 so.. it doesn't work for me (In reply to comment #88) > Yes, I think so. And if I recall correctly he workarounded it with NoDDC. Unfortunately it was a different issue and he could fix it by updating the kernel. (In reply to comment #90) > (In reply to comment #88) > > Yes, I think so. And if I recall correctly he workarounded it with NoDDC. > > Unfortunately it was a different issue and he could fix it by updating the > kernel. hm.. i've updated my kernel yesterday. Is there any chance to lead it to work now? (by updating through X11:Xorg repo) ? or no? I don't think so. As already said on Mattias' machine it was a completely unrelated issue. Need to close this one (again) as WORKSFORME as long as we can't reproduce the issue inhouse. :-( *** Bug 491245 has been marked as a duplicate of this bug. *** this seems to be a pretty serious bug to me. i have a factory install sitting here without gui for weeks. i'm ready to provide any debugging information necessary. this machine has, according to lspci: 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) should i open a new report or provide information here ? in any case, what information would be helpful (ther's a lot already attached, i'd prefer not duplicating it all without a reason). What we would need is hardware, on which we can reproduce this issue. Stefan. Finally I resolved this bug by updating ALL (!) packages from X11:Xorg repo! Cheers! Hi: I update all from x11:Xorg and still have black and blocked screen. I remember people I use nvidia Pavel? any change with ddc options? Regards Chema I also update Mesa packages... you didn't mention _which_ xorg repo did you use. i tried adding http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_Factory/ and updating all xorg packages from that repo - no change, still hangs. this seems to be a pretty serious issue, and i don't think it can be set to 'fixed'. I'm sorry I believed I did it. I use the same as your. I go back again to previous version. At this moment I have no time to check all X-server possibilities... Regards Chema |