https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED AssignedTo|bnc-team-xorg-bugs@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c2 --- Comment #2 from Eduard Avetisyan 2012-07-17 19:42:32 UTC --- I will reinstall this machine and test (sorry, couldn't keep it flickering for too long). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c4 Terje J. Hanssen changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent CC| |terje@nordland-teknikk.no --- Comment #4 from Terje J. Hanssen 2012-08-05 11:27:26 UTC --- Looks like I have got a similar broken and unuseable diskplay graphic on my hp8710w mobile workstation with nVidia Quadro FX3600M. Everything worked fine up to 12.2 RC1 included and with Tumbleweed in dualboot. But after upgrade (zypper dup) to RC2, the display graphic has been broken similar to a black and white mosaic bacground. Have also tried a RC2 new installation from DVD. The first login after installation looks ok, but from the next logon on the display graphic is broken already from the GDM login menu display. The mouse cursor has changed to a square, and moves slowly stepwise or is almost invisible. The login is terrible slow (minutes). If I open a Ctrl-Alt-F1 console login and then top on beforehand, I see that that the Xorg and rsyslogd processes each eats up to 100% CPU during the graphical login process. If I try graphical logon first, it looks like the system freeze and doesn't react on Ctrl-Alt-F1 to console login, and power off/on button is neccessary. Attached below two screenshot of the broken graphical logon display. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c6 --- Comment #6 from Terje J. Hanssen 2012-08-05 11:32:27 UTC --- Created an attachment (id=501149) --> (http://bugzilla.novell.com/attachment.cgi?id=501149) RC2 broken desktop graphic -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c8 Johannes Kapune changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |johannes.kapune@gmx.de --- Comment #8 from Johannes Kapune 2012-08-11 11:25:43 UTC --- (In reply to comment #0)

User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.5) Gecko/20120605 Firefox/10.0.5

After installing RC1 and doing an online update, during reboot the screen gets garbled right after the chameleon picture appears (on first boot all was ok), to a level that nothing can be recognized on the screen. Escaping to text console works only if Ctrl-Alt-F1 is pressed early in the stage of bootup, afterwards it's fully stuck, can only hard reset. Booting up with 'nomodeset' option works (huge "thanks" to grub2 inventors, one now has to guess for hours where exactly which option goes to), but it seems that the fbdev driver is loaded to handle the graphics. Funny enough, fbdev results in twice as much FPS in glxgears test (1000) as nouveau managed after first boot with KMS (500 only).

One more thing - if one simply searches on opensuse wiki for kms or nomodeset, nothing's found. Forums have some information, google helps as well, but wiki apparently only scans the page titles, not contents. This makes the mileage of finding the necessary options longer. In fact, with grub2 (especially text mode) a small info piece on 12.2 release page would be good.

Reproducible: Always

Steps to Reproduce: 1.install, reboot - all fine (500FPS with nouveau driver) 2.online update, reboot (get stuck with "Power down" message) 3.bootup - screen garbled, no reaction on input 4.bootup with nomodeset option - all works, but fbdev is loaded (1000FPS, yet flickeryng)

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c10 Eduard Avetisyan changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical --- Comment #10 from Eduard Avetisyan 2012-08-11 11:57:55 UTC --- (In reply to comment #4)

Looks like I have got a similar broken and unuseable diskplay graphic on my hp8710w mobile workstation with nVidia Quadro FX3600M. Everything worked fine up to 12.2 RC1 included and with Tumbleweed in dualboot.

But after upgrade (zypper dup) to RC2, the display graphic has been broken similar to a black and white mosaic bacground. Have also tried a RC2 new installation from DVD. The first login after installation looks ok, but from the next logon on the display graphic is broken already from the GDM login menu display. The mouse cursor has changed to a square, and moves slowly stepwise or is almost invisible.

The login is terrible slow (minutes). If I open a Ctrl-Alt-F1 console login and then top on beforehand, I see that that the Xorg and rsyslogd processes each eats up to 100% CPU during the graphical login process. If I try graphical logon first, it looks like the system freeze and doesn't react on Ctrl-Alt-F1 to console login, and power off/on button is neccessary.

Attached below two screenshot of the broken graphical logon display.

The reason it moves slow is because the drivers flood the kernel log with error messages. In my case the screen looked even worse than yours, there was hardly anything readable and eventually the system is so slow it stops responding... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c12 --- Comment #12 from Terje J. Hanssen 2012-08-11 14:03:26 UTC --- (In reply to comment #11)

(In reply to comment #7)

...

I will add that Booting with Grub2 Advanced option > Recovery mode does work with correct display graphic. As this now is latest RC2, I yet change this bug to be of Major and High importance.

Later experience showed me that though the Recovery display graphic has been readable, it was flickering and not stable and smooth (i.e web page scrolling). So also the case with the "weak" mouse cursor.

As this graphic problem occured between 12.1 RC1 and RC2 on a proven reliable and SLED certified hardware, I wonder if anyone is working with it? http://developer.novell.com/yes/91882.htm

Typo, should be "between 12.2 RC1 and RC2". Sorry, -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c14 --- Comment #14 from Eduard Avetisyan 2012-08-13 06:55:56 UTC --- I don't really understand what's the problem with this bug. It WAS ok with RC1 fresh install, it got broken with the very first online update. Is it that difficult to dig out the changelogs and revert all to the state of RC1 ? Including the hugely creative change of the location of graphical console from 7 to 8. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c16 Franck Bourdonnec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbourdonnec@chez.com --- Comment #16 from Franck Bourdonnec 2012-08-13 09:59:33 UTC --- same bug here : 775489 remove "splah=silent" from grub Franck -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c18 --- Comment #18 from Terje J. Hanssen 2012-08-13 16:52:47 UTC --- (In reply to comment #16)

remove "splah=silent" from grub

Yes, using grub2 I edited /etc/default/grub and this worked for me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c20 --- Comment #20 from Dmitry Roshchin 2012-08-13 20:56:39 UTC --- Created an attachment (id=502189) --> (http://bugzilla.novell.com/attachment.cgi?id=502189) 12.2 RC2 plymouth screen duplication -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c22 --- Comment #22 from Eduard Avetisyan 2012-08-29 11:40:23 UTC --- 7 days to the release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

(In reply to comment #21)

...

(In reply to comment #15)

...

(In reply to comment #9)

...

Here I have Toshiba Tecra Laptop with NVidia G86M (Quadro NVS 150 M). same behavior after update but I can get login after Ctr-Alt-F1 as root and start startx and after this as root everything runs OK

Where to find more information to find reason?

After installing Nvidia 304.32 eveything seems OK

Did you use an opensuse repository or downloaded the drivers from Nvidia ?

I downloaded the drivers from NVidia. Since now I didn't get any problems with this driver.

Maybe it was my mistake but I did not know that there was a opensuse repository for NVidia. Well, for 12.2 there isn't (yet), I would be glad if opensuse provides the

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c24 --- Comment #24 from Eduard Avetisyan 2012-08-30 11:39:22 UTC --- (In reply to comment #23) proper repositories for accelerated graphics by the time of GM release or even in Beta phase, but this normally happens between 2 weeks and 2 months after the release. Here you will find the repositories for previous releases: http://en.opensuse.org/Additional_package_repositories#NVIDIA_drivers -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c26 --- Comment #26 from Eduard Avetisyan 2012-08-30 12:02:41 UTC --- (In reply to comment #25)

The 12.2 NVIDIA repo is already in place. Unfortunately it's currently in an inconsistent state, i.e. meta data files (./repodata) has been synced, but not the RPMs themselves. :-(

sudo zypper ar http://download.nvidia.com/opensuse/12.2/ NVIDIA-12.2

Thanks Stefan, I've updated the wiki accordingly. Will give it a try soon (hope the rpms are in already by then!) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c28 --- Comment #28 from Stefan Dirsch 2012-08-30 14:39:06 UTC --- Fortunately that's a cosmetic issue. ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c30 --- Comment #30 from Stefan Dirsch 2012-08-30 23:04:01 UTC --- Sure, this is normal. About 60 fps I guess, right? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c32 --- Comment #32 from Franck Bourdonnec 2012-08-31 08:58:57 UTC --- this on the LENEVO T61: Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 2272 frames in 5.0 seconds = 454.307 FPS 2480 frames in 5.0 seconds = 495.982 FPS 2484 frames in 5.0 seconds = 496.658 FPS 2467 frames in 5.0 seconds = 493.136 FPS 2440 frames in 5.0 seconds = 487.864 FPS 2403 frames in 5.0 seconds = 480.444 FPS If you can't fix the switch from plymouth graphic mode to nouveau graphic mode, manage to insert a text mode step between them. Either plymouth leaves the card in a strange mode or nouveau fails to really setup the card. Franck -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c34 Norm Decelles changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Rosewood_Arts@Hotmail.com Platform|x86-64 |PC Version|RC 2 |Final --- Comment #34 from Norm Decelles 2012-09-08 16:19:12 UTC --- Nearly identical problem here on other nvidia. Multiple new clean install attempts with 12.2 on nvidia GS8400M Dell xps m1330 laptop...tried both 32 and 64 bit versions. Same results. BOTTOM LINE: Nouveau & Desktops install fine (gnome, kde, xfce were fine). First reboot-> black & white mosaic screen with square cursor...desktop not responsive. Screen appears like alternating black and white inter-locking Z's or 2's. Reboot into recovery mode -> no problem. Norm -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c36 Uwe Geuder changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell-ugeuder@sneakemail.c | |om --- Comment #36 from Uwe Geuder 2012-09-10 22:42:39 UTC --- Updated my Dell Latitude E6510 to 12.2. sudo /sbin/lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [NVS 3100M] (rev a2) First sessions went fine, but after upgrading packages the initial X screen shows some checkerboard pattern and is unusable. work-around 1: remove "splash=silent" from grub command line as advised before. X screen is usable from the beginning or alternatively work-around 2: When the initial X screen is unusable, switch to text virtual console (Alt-Ctrl-F1), login and give command $ sudo systemctl try-restart xdm.service (I use KDE desktop, not sure whether the service is the same for other desktops) X screen becomes usable after this command -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c38 --- Comment #38 from Franck Bourdonnec 2012-09-11 15:21:37 UTC --- bad news updating with https://build.opensuse.org/package/binary?arch=x86_64&filename=drm-nouveau-kmp-desktop-20120906.0144_k3.4.6_2.10-1.1.x86_64.rpm&package=drm-nouveau&project=home%3Ajobermayr&repository=openSUSE_12.2 failed the same way ! (driver filename: /lib/modules/3.4.6-2.10-desktop/updates/drivers/gpu/drm/nouveau/nouveau.ko) installed with some depmod/mkinitrd SIMPLEST WORKAROUND not permanent : CRTL-ALT-BACKSPACE. Hit twice backspace, like double clic. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c40 Franck Bourdonnec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|fbourdonnec@chez.com | --- Comment #40 from Franck Bourdonnec 2012-09-11 16:50:12 UTC --- Created an attachment (id=505264) --> (http://bugzilla.novell.com/attachment.cgi?id=505264) lenovo T61 dmesg boot may I suggest you work on plymouth resetting the card to a known text mode or working on the NV chipset init sequence Obviously, switching from graph mode to graph mode fails. Starting from any textmode is good for NV driver. Franck -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c42 Johannes Obermayr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |fbourdonnec@chez.com --- Comment #42 from Johannes Obermayr 2012-09-13 23:00:56 UTC --- (In reply to comment #40)

Created an attachment (id=505264) --> (http://bugzilla.novell.com/attachment.cgi?id=505264) [details] lenovo T61 dmesg boot

Frank, I assume you didn't see the garbled screen. There should be sth. like this in the log: [ 53.003528] [drm] nouveau 0000:01:00.0: fail set_domain [ 53.003531] [drm] nouveau 0000:01:00.0: validate vram_list [ 53.003534] [drm] nouveau 0000:01:00.0: validate: -22 Please add "log_buf_len=1M" to boot parameters, then wait until garbled screen occurs, press immediately Crtl-Alt-Backspace-Backspace and then attach dmesg output here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c44 Johannes Obermayr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |golstar@gmail.com --- Comment #44 from Johannes Obermayr 2012-09-14 22:33:54 UTC --- *** Bug 779686 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=779686 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c46 Johannes Obermayr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.huelsmann@gmx.net --- Comment #46 from Johannes Obermayr 2012-09-14 22:39:21 UTC --- *** Bug 775489 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=775489 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c Johannes Obermayr changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch Summary|After installation nouveau |Nouveau: Kernel issue on |driver loads fine. After |switch from plymouth to X |the first online update and |[possible fix] |reboot the screen is | |garbled and unresponsive, | |can't even get to text | |console. nomodeset helps | |(fbdev used) | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c49 --- Comment #49 from Johannes Obermayr 2012-09-15 00:27:36 UTC --- Created an attachment (id=505915) --> (http://bugzilla.novell.com/attachment.cgi?id=505915) dmesg output with drm-nouveau-kmp-desktop on ION Works with drm-nouveau-kmp-{flavor} package from home:jobermayr. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c51 --- Comment #51 from Bjørn Lie 2012-09-16 01:28:06 CEST --- I can confirm that using Johannes drm-nouveau-kmp-desktop fixes the issue here as well. Model: "nVidia Quadro NVS 135M" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x042b "Quadro NVS 135M" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c53 --- Comment #53 from Uwe Geuder 2012-09-17 21:28:16 UTC --- I could try to test the packages from http://download.opensuse.org/repositories/home:/jobermayr/openSUSE_12.2/x86_... but please excuse my ignorance, I have no idea how. I'd guess the kernel driver is in http://download.opensuse.org/repositories/home:/jobermayr/openSUSE_12.2/x86_... My existing module nouveau.ko comes from $ rpm -qf /lib/modules/3.4.6-2.10-desktop/kernel/drivers/gpu/drm/nouveau/nouveau.ko kernel-desktop-3.4.6-2.10.1.x86_64 So will the new model just override the old one because it comes first in module search path or how does it work? Furthermore I'd guess... http://download.opensuse.org/repositories/home:/jobermayr/openSUSE_12.2/x86_... ... is part of the fix. However, I have no package with that name installed. Instead there is $ rpm -qa | grep libdrm libdrm_nouveau1-2.4.33-2.3.2.x86_64 libdrm2-2.4.33-2.3.2.x86_64 libdrm_radeon1-2.4.33-2.3.2.x86_64 libdrm2-32bit-2.4.33-2.3.2.x86_64 libdrm_intel1-2.4.33-2.3.2.x86_64 Additionally there are Mesa and xorg-x11-driver packages built in the same repo, just built a bit later. Do they belong to the same fix? With that many questions I did not dare to start any trial and error, especially not past midnight... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c55 --- Comment #55 from Franck Bourdonnec 2012-09-18 09:08:58 UTC --- hello, fixed with installation of rpm -i --force libdrm-2.4.99.git20120915.0206-1.1.x86_64.rpm rpm -i drm-all-kmp-desktop-20120916.2158_k3.4.6_2.10-1.1.x86_64.rpm Franck lenevo T61 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [Quadro NVS 140M] (rev a1) Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 2626 frames in 5.0 seconds = 525.103 FPS 2852 frames in 5.0 seconds = 570.289 FPS 2852 frames in 5.0 seconds = 570.305 FPS 2850 frames in 5.0 seconds = 569.856 FPS 2819 frames in 5.0 seconds = 563.715 FPS # dmesg |grep drm [ 2.655548] [drm] Initialized drm 1.1.0 20120916.2158 5698bd7 < drm-fixes 610bd7d < drm-next 0b2443e < drm-next-3.7-wip 9355465 < nouveau-master 0a5cdb7 < openchrome/master 38f9643 < drm-intel-next-queued 6d01110 [ 2.885410] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 2.885416] [drm] No driver support for vblank timestamp query. [ 4.636557] drm: registered panic notifier [ 4.636569] [drm] Initialized nouveau 1.1.0 20120916.2158 5698bd7 < drm-fixes 610bd7d < drm-next 0b2443e < drm-next-3.7-wip 9355465 < nouveau-master 0a5cdb7 < openchrome/master 38f9643 < drm-intel-next-queued 6d01110 for 0000:01:00.0 on minor 0 # dmesg |grep nouveau [ 2.655548] [drm] Initialized drm 1.1.0 20120916.2158 5698bd7 < drm-fixes 610bd7d < drm-next 0b2443e < drm-next-3.7-wip 9355465 < nouveau-master 0a5cdb7 < openchrome/master 38f9643 < drm-intel-next-queued 6d01110 [ 2.680621] fb: conflicting fb hw usage nouveaufb vs VESA VGA - removing generic driver [ 2.682515] nouveau 0000:01:00.0: power state changed by ACPI to D0 [ 2.682528] nouveau 0000:01:00.0: power state changed by ACPI to D0 [ 2.683662] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x086900a2 [ 2.683671] nouveau [ DEVICE][0000:01:00.0] Chipset: G86 (NV86) [ 2.683678] nouveau [ DEVICE][0000:01:00.0] Family : NV50 [ 2.692364] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image... [ 2.791037] nouveau [ VBIOS][0000:01:00.0] ... appears to be valid [ 2.791047] nouveau [ VBIOS][0000:01:00.0] using image from PRAMIN [ 2.801433] nouveau [ VBIOS][0000:01:00.0] BIT signature found [ 2.801446] nouveau [ VBIOS][0000:01:00.0] version 60.86.3e.00 [ 2.801837] nouveau [ MXM][0000:01:00.0] no VBIOS data, nothing to do [ 2.823715] nouveau [ PFB][0000:01:00.0] RAM type: GDDR3 [ 2.823725] nouveau [ PFB][0000:01:00.0] RAM size: 128 MiB [ 2.850967] nouveau [ DRM] VRAM: 128MiB [ 2.850974] nouveau [ DRM] GART: 512MiB [ 2.850985] nouveau [ DRM] BIT BIOS found [ 2.850994] nouveau [ DRM] Bios version 60.86.3e.00 [ 2.851017] nouveau [ DRM] TMDS table version 2.0 [ 2.851023] nouveau [ DRM] DCB version 4.0 [ 2.851031] nouveau [ DRM] DCB outp 00: 01000323 00010034 [ 2.851039] nouveau [ DRM] DCB outp 01: 02811300 00000028 [ 2.851046] nouveau [ DRM] DCB outp 02: 02822312 00010030 [ 2.851053] nouveau [ DRM] DCB outp 03: 014333f1 0080c080 [ 2.851060] nouveau [ DRM] DCB conn 00: 0040 [ 2.851067] nouveau [ DRM] DCB conn 01: 0100 [ 2.851073] nouveau [ DRM] DCB conn 02: 1231 [ 2.851225] nouveau [ DRM] DCB conn 03: 0311 [ 2.884153] nouveau W[ DRM] DCB encoder 1 unknown [ 2.884161] nouveau W[ DRM] TV-1 has no encoders, removing [ 2.885424] nouveau [ DRM] ACPI backlight interface available, not registering our own [ 4.471304] nouveau [ DRM] 3 available performance level(s) [ 4.471318] nouveau [ DRM] 0: core 169MHz shader 338MHz memory 100MHz voltage 1150mV fanspeed 100% [ 4.471331] nouveau [ DRM] 1: core 275MHz shader 550MHz memory 301MHz voltage 1150mV fanspeed 100% [ 4.471342] nouveau [ DRM] 2: core 400MHz shader 800MHz memory 600MHz voltage 1200mV fanspeed 100% [ 4.471353] nouveau [ DRM] c: core 275MHz shader 550MHz memory 302MHz voltage 1150mV [ 4.506170] nouveau [ DRM] MM: using CRYPT for buffer copies [ 4.600913] nouveau [ DRM] allocated 1440x900 fb: 0x60000, bo ffff880036cb2c00 [ 4.601135] fbcon: nouveaufb (fb0) is primary device [ 4.636552] fb0: nouveaufb frame buffer device [ 4.636569] [drm] Initialized nouveau 1.1.0 20120916.2158 5698bd7 < drm-fixes 610bd7d < drm-next 0b2443e < drm-next-3.7-wip 9355465 < nouveau-master 0a5cdb7 < openchrome/master 38f9643 < drm-intel-next-queued 6d01110 for 0000:01:00.0 on minor 0 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c57 --- Comment #57 from Uwe Geuder 2012-09-18 21:23:06 UTC --- Used stellarium for a while (I could guess this stresses the drm driver a bit). No problems observed, typically 30-40 fps in full screen mode. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c59 Michal Marek changed: What |Removed |Added ---------------------------------------------------------------------------- CC|jkosina@suse.com |mmarek@suse.com --- Comment #59 from Michal Marek 2012-09-19 12:09:47 UTC --- (In reply to comment #52)

https://build.opensuse.org/request/show/134726

The update is bigger because I must rebuild the complete drm stack:

What upstream version is this? Also, could you create a patch series that applies to the openSUSE-12.2 branch of kernel-source.git, so that we do not have two differing version of drivers/gpu/drm? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c61 --- Comment #61 from Jeff Mahoney 2012-09-19 08:44:39 EDT --- http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=... is a one line patch that very obviously does not change the kABI. Where did the discussion about updating *all* of DRM come from? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c63 --- Comment #63 from Marcus Meissner 2012-09-19 13:06:14 UTC --- my main concern would be: if we have bricked users machines (or make them start in textmode), we cannot easily make them revert to a good state. of course we can delete the update, but this will not help users that installed it already. this has the potential of high frustration. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c65 --- Comment #65 from Johannes Obermayr 2012-09-19 13:17:04 UTC --- (In reply to comment #63)

my main concern would be:

if we have bricked users machines (or make them start in textmode), we cannot easily make them revert to a good state.

of course we can delete the update, but this will not help users that installed it already.

this has the potential of high frustration.

-> nomodeset (this is what sndirsch tells all bug reporters) -> zypper rm drm-all-kmp-{flavor} or zypper in --force drm-all-kmp-{flavor}-${version} -> boot without nomodeset again I can also update %description. Do you think problems with fglrx or nvidia are easier to solve? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c67 --- Comment #67 from Takashi Iwai 2012-09-19 13:46:05 UTC --- Well, I'm confused what you guys are discussing... We have to think two things separately: fixing a bug on openSUSE 12.2, and providing drm-kmp. If any fix is needed for the current kernel, this should be applied to the kernel itself, not provided as a kmp. This is the primary option. Is this already done regarding this bug at all...? (The one in comment 61 is marked with Cc to stable, so it shall be included to 12.2 kernel sooner or later.) Providing a KMP is basically an enhancement, and it's no real "fix", although it may casually fix as it can paper over a bug. So, it's bad to release it as an official online update for 12.2. Meanwhile, I'm basically for drm-kmp pacakage, as long as it stays in OBS. Then the chance to drag an unexpected package becomes smaller, and people can still have a good chance for temporary workarounds. (Not sure whether OBS Kernel:openSUSE-12.2 is the right place, though. Maybe better to be in an own repo?) For example, alsa-driver-kmp has been provided over ages as an update to the latest snapshot version. This has been always good as a test case (that I can suggest at first when I get a bug report). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c69 --- Comment #69 from Takashi Iwai 2012-09-19 14:59:07 UTC --- (In reply to comment #68)

(In reply to comment #67)

...

If any fix is needed for the current kernel, this should be applied to the kernel itself, not provided as a kmp. This is the primary option. Is this already done regarding this bug at all...? (The one in comment 61 is marked with Cc to stable, so it shall be included to 12.2 kernel sooner or later.)

Providing a KMP is basically an enhancement, and it's no real "fix", although it may casually fix as it can paper over a bug. So, it's bad to release it as an official online update for 12.2.

Do you have the time to bisect the necessary patch(es) upstream for a bug reported on bnc (esp. if you do not have the hardware and summary does not really point to it)?

If it's needed, we must do. Or better to say: as an online-update "fix", you must understand what you fixed and how it's fixed. By upgrading the whole stack, a bug might be fixed coincidentally, but you don't know always why it's fixed. And more badly, you don't know always whether any new regression might be introduced, too.

So it is easier to provide a official drm package which people can easily revert if it breaks things and have a highly motivated maintainer who also reads specific mailing lists.

Sorry, the "easiness" alone is no good justification. For example, did you think how to handle security fixes once when the codes are split to KMP and kernel?

But I assume sndirsch's comments like "use nomodeset" are more welcomed than "attach dmesg and /var/log/Xorg.0.log" and fixing the error and/or speaking with upstream developers.

But my experience with maintainers on openSUSE main projects is like belonging to an elitist group of people cooking their own soup and/or doing nothing to recruit maintainers: https://bugzilla.novell.com/show_bug.cgi?id=706813

Well, your argument seems going to offtopic... Again, I'm not against having drm-kmp. It's good for a rolling update model like Tumbleweed. But this cannot be a "fix", thus cannot be provided as a maintenance update. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c71 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|maintenance@opensuse.org | Resolution| |FIXED AssignedTo|kernel-maintainers@forge.pr |jeffm@suse.com |ovo.novell.com | Summary|Nouveau: Kernel issue on |Nouveau: Kernel issue on |switch from plymouth to X |switch from plymouth to X |[pending update] | --- Comment #71 from Jeff Mahoney 2012-09-19 11:46:42 EDT --- I've applied the fix to the 12.2 repo. Closing as fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c73 Johannes Obermayr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|FIXED | --- Comment #73 from Johannes Obermayr 2012-09-19 15:49:23 UTC --- The bug can be closed when available in Update for download. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c75 --- Comment #75 from Takashi Iwai 2012-09-19 16:15:18 UTC --- Just to avoid misunderstanding: we appreciate your previous works, of course! And actually I personally am *for* rolling updates, too. But for *this* particular bug for openSUSE 12.2, the most appropriate fix would be patching the kernel package with the commit you spotted. There can be a better way to manage in future, but it simply doesn't fit with openSUSE 12.2. So, let's continue the discussion in other places. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c77 --- Comment #77 from Jogchum Reitsma 2012-10-01 17:56:13 UTC --- (In reply to comment #75)

But for *this* particular bug for openSUSE 12.2, the most appropriate fix would be patching the kernel package with the commit you spotted.

Any idea when this new, patched kernel package will be available? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c79 --- Comment #79 from Jogchum Reitsma 2012-10-01 18:45:27 UTC --- I removed kernel-desktop, selected kernel-desktop-base from the KOTD repo, and alongside kernel-debug was selected. Starting the kernel-desktop-base gives a mandatory root login, and no desktop. I don't have the time to investigate this tonight (nor tomorrow, I'm afraid). But the debug-kernel is the default, and works, so for the moment the WAF (see bug 779447, which is a duplicate of this one) is OK again. Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |obs:running:970:important -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c82 --- Comment #82 from Uwe Geuder 2012-10-13 12:12:33 UTC --- I can confirm that the new kernel packages solves this problem for me (NVIDIA Corporation GT218 [NVS 3100M] (rev a2)) 1. Uninstalled drm-all-kmp-desktop from the work-around above 2. Reboot --> problem is back. X works only on second attempt (restarting X required) 3. updated kernel-desktop to 3.4.11-2.16.1.x86_64 4, Reboot --> X working without restart Thanks everybody involved! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c84 --- Comment #84 from Jogchum Reitsma 2012-10-14 18:30:53 UTC --- Here too, thanks everyone! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=771392 https://bugzilla.novell.com/show_bug.cgi?id=771392#c85 --- Comment #85 from Swamp Workflow Management 2013-02-09 14:05:08 UTC --- openSUSE-SU-2013:0261-1: An update that solves one vulnerability and has 14 fixes is now available. Category: security (moderate) Bug References: 569991,770763,771392,773831,774859,776925,778630,780624,781327,783615,783965,784192,792500,793671,799209 CVE References: CVE-2012-3520 Sources used: openSUSE 12.2 (src): kernel-docs-3.4.28-2.20.2, kernel-source-3.4.28-2.20.1, kernel-syms-3.4.28-2.20.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=771392 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:970:important | -- You are receiving this mail because: You are on the CC list for the bug.