Ugly display after an upgrade

CPU Gastronomy · 2011-03-05 18:57:18

It seems that it is a kernel bug after all : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613078.
There is a patch, but like said Sven in the bug report,

"The mentioned patch was rather a hack, 2.6.38-rc6 has a proper patch that supposedly fixes the problem"

and that implies a rebuilt of the kernel or, in the other hand, playing with an experimental kernel.

The link to the patch : https://bugs.freedesktop.org/attachment.cgi?id=43011

EDIT :
I forgot to say that, some people applied the patch and it seems to work, samething with the kernel 2.6.38-rc6.
I didn't tested personnally any of these because I got a heavy load of works this weekend.

Last edited by CPU Gastronomy (2011-03-05 19:01:26)

CPU Gastronomy · 2011-03-14 14:24:31

I confirm that it is working with the kernel 2.6.38-rc8 without any problem to now.

beachcoder · 2011-03-27 20:07:35

Hello folks,

I'm having the same problem since I updated today.
Is there any applicable solution for a novice like me? => Means: I don't want to compile my own kernel, I feel a little nervous to result in a system that doesn't boot anything at all (e.g. encrypted harddiscs, etc).

Any urgent help, please!

CPU Gastronomy · 2011-03-27 20:38:04

As he said, you could downgrade the packages :

berbae wrote:

I had to downgrade the drm and nouveau related packages to recover the graphical environment :
libdrm (2.4.23-1 -> 2.4.22-3)
libgl (7.10-1 -> 7.9.0.git20101207-2)
libva (1.0.8-1 -> 1.0.6-1)
mesa (7.10-1 -> 7.9.0.git20101207-2)
xf86-video-nouveau (0.0.16_git20101217-1 -> 0.0.16_git20100819-2)
running the commands under root :
cd /var/cache/pacman/pkg
pacman -U libdrm-2.4.22-3-x86_64.pkg.tar.xz libgl-7.9.0.git20101207-2-x86_64.pkg.tar.xz libva-1.0.6-1-x86_64.pkg.tar.xz mesa-7.9.0.git20101207-2-x86_64.pkg.tar.xz xf86-video-nouveau-0.0.16_git20100819-2-x86_64.pkg.tar.xz
As you have the nouveau-dri package you will have to downgrade it too.
You should do that after having killed the graphical processes.

Sure, maybe you'll have to change the package name to the previous ones you had if needed.

Compiling a new kernel isn't that dangerous as long you don't save it over your current one (and don't play blindly in the config).
For your encrypted hardisks, don't worry, it doesn't modify your main configurations (ex : most of all in /etc).

I compiled my first kernel when I got this problem with my display and I had encrypted disks too.
Just check a little this page :
https://wiki.archlinux.org/index.php/Ke … rom_Source
It explains very well how to compile it safely without erasing your current one (meaning that if the new kernel isn't correct, you still can go with your current one).

But if it is an emergency, try to downgrade.

Last edited by CPU Gastronomy (2011-03-27 20:40:18)

beachcoder · 2011-03-28 07:52:46

Hello CPU Gastronomy, thanks for your quick answer.

CPU Gastronomy wrote:

Compiling a new kernel isn't that dangerous as long you don't save it over your current one (and don't play blindly in the config).
For your encrypted hardisks, don't worry, it doesn't modify your main configurations (ex : most of all in /etc).
I compiled my first kernel when I got this problem with my display and I had encrypted disks too.
Just check a little this page :
https://wiki.archlinux.org/index.php/Ke … rom_Source
It explains very well how to compile it safely without erasing your current one (meaning that if the new kernel isn't correct, you still can go with your current one).

Well I tried to downgrade first, but this didn't take any effects. I also tried out some of the git-packages from AUR, e.g. nouveau-dri-git, but this even did not solve the problem.
But your words sound very helpful and stressless to build a kernel on my own, so I'll try this. (yet, I only had build Enlightenment, my favorite window manager on my own).

One more question to you: There is a kernel package in AUR, called aur/kernel26-nouveau-git, may I use this one or should I better do it the way described in https://wiki.archlinux.org/index.php/Ke … rom_Source?

CPU Gastronomy wrote:

But if it is an emergency, try to downgrade.

For now, I switched to the legacy closed source drivers. Bad console resolution, slow tty switching, but it works for now.
I really miss nouveau, but have some more calmness now to try the kernel build.

Thanks a lot, and hopefully this problem will also be fixed soon in the standard packages of Arch.

So long,
beachcoder

sacarde · 2011-04-11 11:15:47

ok

kernel 38 solve

student975 · 2011-04-16 10:15:42

sacarde wrote:

ok
kernel 38 solve

I still have

(EE) [drm] No DRICreatePCIBusID symbol

with current official state (kernel 2.6.38.2 and so on) with this card:

$ lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation G98 [GeForce 8400 GS] (rev a1)

sacarde · 2011-04-16 11:35:43

I use driver: nouveau

with: GeForce 6150SE nForce 430

student975 · 2011-04-16 11:40:14

sacarde wrote:

I use driver: nouveau

Yes, I'm saying about nouveau.

sacarde · 2011-04-16 11:49:24

https://bbs.archlinux.org/viewtopic.php?pid=725151

?

student975 · 2011-04-16 11:53:23

sacarde wrote:

https://bbs.archlinux.org/viewtopic.php?pid=725151
?

Can you be more elaborate? What does this question mark mean?

sacarde · 2011-04-16 12:04:07

...only ... if you have read that link

student975 · 2011-04-16 17:29:46

sacarde wrote:

...only ... if you have read that link

I have. What must I understand?

There is an information it is a kernel bug (I mean "no symbol"): https://bugs.archlinux.org/task/22700 OTOH some archers have downgraded noveau driver and are happy. So, I don't understand where is the reason of the symbol error. I have understrood your message as if with last driver and kernel all does work.

diegoviola · 2011-04-24 22:34:05

Deleted.

Last edited by diegoviola (2023-04-17 22:42:11)

CPU Gastronomy · 2011-04-24 23:03:16

@student975
I think you should create another thread if the bug persists, because it is not the same problem as the one that started the thread (that is solved).

student975 · 2011-04-24 23:36:57

@diegoviola

Thanks for informing! At last I have successfully started X with nouveau driver (being under one just now). I have 'G98 [GeForce 8400 GS] (rev a1)' fanless card.

@CPU Gastronomy

As you see, I'm here That error with symbol appears with 'sudo Xorg -configure' only, not preventing to start X. Cirrent X11 log hasn't the error.

diegoviola · 2011-04-25 19:35:49

Deleted.

Last edited by diegoviola (2023-04-17 22:41:49)

student975 · 2011-04-25 20:22:15

diegoviola wrote:

You should report upstream if the new nouveau/kernel fixed your issue.

I'm sure, I shouldn't At first, it isn't "my" issue - just have got a screen similar to one presented in the first topic post. Next, why I must bother developers not being a reporter (or even subsciber) of a bug when there isn't any problems? There are thousands of packages, and millions of users knowing "aha, with this release of that package that issue has gone, nice". Must all these millions notify developers at such situation?

Agree?

Last edited by student975 (2011-04-25 20:23:17)

diegoviola · 2011-04-28 18:15:01

Deleted.

Last edited by diegoviola (2023-04-17 22:41:14)

student975 · 2011-04-28 18:52:38

@diegoviola

Have you read my message? Again: why must I (or anybody) bother developers when there is not a problem? As for filing new issues - please, believe me, during ten years with single-boot linux workstation I have reported plenty of them "student" means desire to learn rather age

diegoviola · 2011-04-29 01:44:41

Deleted.

Last edited by diegoviola (2023-04-17 22:40:58)

Arch Linux

#26 2011-03-05 18:57:18

Re: Ugly display after an upgrade

#27 2011-03-14 14:24:31

Re: Ugly display after an upgrade

#28 2011-03-27 20:07:35

Re: Ugly display after an upgrade

#29 2011-03-27 20:38:04

Re: Ugly display after an upgrade

#30 2011-03-28 07:52:46

Re: Ugly display after an upgrade

#31 2011-04-11 11:15:47

Re: Ugly display after an upgrade

#32 2011-04-16 10:15:42

Re: Ugly display after an upgrade

#33 2011-04-16 11:35:43

Re: Ugly display after an upgrade

#34 2011-04-16 11:40:14

Re: Ugly display after an upgrade

#35 2011-04-16 11:49:24

Re: Ugly display after an upgrade

#36 2011-04-16 11:53:23

Re: Ugly display after an upgrade

#37 2011-04-16 12:04:07

Re: Ugly display after an upgrade

#38 2011-04-16 17:29:46

Re: Ugly display after an upgrade

#39 2011-04-24 22:34:05

Re: Ugly display after an upgrade

#40 2011-04-24 23:03:16

Re: Ugly display after an upgrade

#41 2011-04-24 23:36:57

Re: Ugly display after an upgrade

#42 2011-04-25 19:35:49

Re: Ugly display after an upgrade

#43 2011-04-25 20:22:15

Re: Ugly display after an upgrade

#44 2011-04-28 18:15:01

Re: Ugly display after an upgrade

#45 2011-04-28 18:52:38

Re: Ugly display after an upgrade

#46 2011-04-29 01:44:41

Re: Ugly display after an upgrade

Board footer