Complete Mesa 9.0.2 and Xorg 1.13.2 port for Rosa 2012.1

[GvMariani]

* Mesa-9.0.1-69.2:
- added provision to build: osmesa library packages (enabled because it is needed by Wine 1.5.10+); wayland packages (enabled as in the standard packaging); radeonsi gallium driver (disabled for now because it needs the glamor library, not yet provided on Rosa 2012.1); opencl support for radeon (disabled for now because it needs llvm > 3.2 and libclc, not yet provided); support for the new glsl compiler for radeons (disabled for now because it needs llvm > 3.2);
- built also the drivers needed for VmWare (xa state tracker);
- built XvMC support and added a config file needed to having it actually work (but you will have to edit it according to your video card type: for instructions see the included README.XvMC file);
- removed vaapi build support and relevant patch and packages, because it was removed upstream;
- enabled, for testing purpose, some performance patches for r600g, taken from upstream: "make use of VRAM rather than GTT memory" and "re-enable discard_range handling";
- enabled the support of the texture-float feature, and hence the support for OpenGL 3.0 (3.1 on intel drivers).

I'll take a close look at this package and most likely merge all non-experimental features to the official Rosa 2012.1 Mesa package.

You're welcome...
You could also directly look at my gvm/mesa fork on ABF (branch rosa 2012.1):
I already have synced that with my actual packages because I'm planning to use ABF as main store for my MIB packages
(and use the master as play land for toying with the "future" packages from the git).

However I would more like to help directly if only I could find someone to interact with...

GvM

[GvMariani]

ma può darsi ch GvM, ci possa dare qualche suggerimento / configurazione sperimentale

Sorry...
I'm fond only on Radeon matters.

GvM

[NicCo]

The issue with text corruption here again, since few minutes,
it started appearing only after a good massive use of firefox,
so the xorg without the use of cache for pixman is necessary

I mean the second part with repository /no-new-pixman should be installed

It's strange that this issue appear after about one entire day of fine woking...

[GvMariani]

The issue with text corruption here again, since few minutes,
it started appearing only after a good massive use of firefox,
so the xorg without the use of cache for pixman is necessary
I mean the second part with repository /no-new-pixman should be installed
It's strange that this issue appear after about one entire day of fine woking...

I guess there is some type of condition that triggers the cache corruption, but is not always present...
That warrants a bug on fdo bugzilla, IMHO, to allow the upstream developers to find the cause and correct it.

GvM

[andreas]

After the update I lost the HDMI audio output in my nvidia card. The workaround described in various forums no more works (i.e. aplay -l to determine the card number and the phisical outputs available, then aplay -D plughw:x,x soundfile to determine which output is phisically in use) and no sound is generated, despite is evident that the system is trying to play the sound file.
Thus I guess that there is a bug somewhere in the update (may be the nvidia-current or x11-driver-nvidia-current?).
Below is the output of the variious commands I used:

[root@Desktop-1 sounds]# aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default
Default ALSA Output (currently PulseAudio Sound Server)
hdmi:CARD=NVidia,DEV=0
HDA NVidia, HDMI 0
HDMI Audio Output
hdmi:CARD=NVidia,DEV=1
HDA NVidia, HDMI 0
HDMI Audio Output
hdmi:CARD=NVidia,DEV=2
HDA NVidia, HDMI 0
HDMI Audio Output
hdmi:CARD=NVidia,DEV=3
HDA NVidia, HDMI 0
HDMI Audio Output

[root@Desktop-1 sounds]# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 7: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0]
Subdevices: 0/1
Subdevice #0: subdevice #0

[root@Desktop-1 sounds]# aplay -D plughw:0,3 ia_ora-startup.wav
Playing WAVE 'ia_ora-startup.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Stereo
[root@Desktop-1 sounds]# aplay -D plughw:0,7 ia_ora-startup.wav
Playing WAVE 'ia_ora-startup.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Stereo
[root@Desktop-1 sounds]# aplay -D plughw:0,8 ia_ora-startup.wav
Playing WAVE 'ia_ora-startup.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Stereo
[root@Desktop-1 sounds]# aplay -D plughw:0,9 ia_ora-startup.wav
aplay: main:696: audio open error: Device or resource busy

[GvMariani]

After the update I lost the HDMI audio output in my nvidia card. The workaround described in various forums no more works (i.e. aplay -l to determine the card number and the phisical outputs available, then aplay -D plughw:x,x soundfile to determine which output is phisically in use) and no sound is generated, despite is evident that the system is trying to play the sound file.
Thus I guess that there is a bug somewhere in the update (may be the nvidia-current or x11-driver-nvidia-current?).
...
[root@Desktop-1 sounds]# aplay -D plughw:0,9 ia_ora-startup.wav
aplay: main:696: audio open error: Device or resource busy

What version of nvidia-current are you using now? And what before the upgrade?
Does trying another release of it change something? (in our repo, we have a couple of version for both long-lived and current)

And about where the bug lies, please remember that you are using the "closed source" drivers:
the building process for these packages does very little other than packaging the binaries from the original distribution blobs from Nvidia.
So I would guess that it could be involved here something other than the packages you cited...
For this reasoning I would try to use another version of -current, or also a long-lived one: if the problem goes away, then we are sure that it lies in the nvidia driver side, otherwise
we are rather sure that it lies somewhere in the other part of the updated packages.

POST-EDIT:
I suppose you already know about this document: ftp://download.nvidia.com/XFree86/gpu-h ... audio.html and the troubleshoot passes it suggests...


GvM

[andreas]

Thank for the answer.
The release of the driver is the same 3.10.19 but, of course, the build is different. The reason why I was addressing the problem to the driver is that I have no evidence of a relationship among pulse and xorg, so I was assuming it could be something related to the build of the nvidia driver. From the tests I made it looks like alsa is properly workig, but something is broken in the alsa to pulse connection, as I am not able to hear the sounds that alsa generates.
I may try the long-lived drivers, but I guess that the building environment is the same. One thing I noticed is that prior to upgrade the card was numbered as Device 1, while now it is numbered as Device 0.

[NicCo]

Did you tried to delete the pulse config?
Deleting or renaming the existant /home/.pulse folder, so using a new clean config

You can also try starting from a new created user, so all configs would be full clean

[andreas]

Did you tried to delete the pulse config?
Deleting or renaming the existant /home/.pulse folder, so using a new clean config

You can also try starting from a new created user, so all configs would be full clean

Thanks.
I tried to delete the pulse directory but nothing changed.
Tomorrow I will try to change the Nvidia driver, but I don't expect big results.
If I play something I see the vue-meter bar in Pulse Volume moving, so it may be something that prevents pulse to connect to the hardware. Any test I can do to determine which soft or hard link is broken?

[GvMariani]

Did you tried to delete the pulse config?
Deleting or renaming the existant /home/.pulse folder, so using a new clean config
You can also try starting from a new created user, so all configs would be full clean

Thanks.
I tried to delete the pulse directory but nothing changed.
Tomorrow I will try to change the Nvidia driver, but I don't expect big results.
If I play something I see the vue-meter bar in Pulse Volume moving, so it may be something that prevents pulse to connect to the hardware. Any test I can do to determine which soft or hard link is broken?

What does Pavucontrol (ie Pulseaudio Volume Control) in the Configuration tab?
If you have two or more sound devices (e.g. the one attached to the video card and a real audio device), it could be that by installing the driver you also provoked a change in the device index (ie
the device that before was "0", now is "1" and so on): in such case Pulseaudio continues to send its output to the wrong device...

GvM

[andreas]

No, the internal card is disabled in Bios, and I did it three or four months ago, when I bought a monitor able to handle HDMI audio, as my previous one prematurely died after four years. The pauv volume control shows only one output device per time as does alsamixer.
In any case I will try later to downgrade the video driver and will report the result.

[andreas]

What a mess!!!!
I could not test the older drivers because on my system with the old drivers xorg simply does not start.
I tried to:
- unload the previous drivers via software install and then load the older ones: xorg did not start
- start in recovery mode and try to install the old drivers from XFdrake: XFdrake ended stating that the screen was too litle for the applicatrion to run and invited me to resize(in text mode on a 2560x1440 monitor!!!) and retry
- still in recovery uninstall the drivers and let XFdrake install the drivers (I had to manually start all the network services as it looks like in recovery they are not started): same result as above
- always through XFdrake, install the nouveau drivers: still the same result
- So I installed the vesa driver and this time xorg started

At this point I reloaded the old drivers and tried to instal them via graphical installer + the latest nrjql kernel packets that XFdrake asked me to install (I don' t understand why): at the reboot Xorg didn' t start.
Back to the recovery console after a couple of attempts to install the old nvidia drivers via rpm and then XFrake I reinstalled the vesa driver and booted back in rosa.
This time I removed the old nvidia drivers via urpme and did an install of the drivers via the graphical installer in Kde control center and this time they worked.

At this point the good news: I decided to test again the audio system and it worked, but the working port is now port 8 and not more port 7 that worked in rosa lts and the previous version of xorg.
Moreover Pulse Volume Control identifies that port as Display port 3 that is not present on my card (only two display ports and I' m attached to port 1), and in KDE sound and video configuration, at the audiohardware setup of Phonon, the profile tab is blank: if I choose any of the available options of that tab I lose my Audio.

Back to an Nvidia driver build related problem that misleads phonon?

Now I patched my pulse.pa file and I hope that tomorrow, when I' ll boot again my PC the audio will still be there.

[ninarello19]

Installato tutto.
Nessun problema.

Code: Select all

utente@localhost ~]$ su
Password: 
[root@localhost utente]# inxi -F
System:    Host: localhost.localdomain Kernel: 3.6.11-nrj-desktop-1rosa x86_64 (64 bit) 
           Desktop KDE 4.9.4 Distro: RosaDesktop.Fresh 2012.1 belka
Machine:   Mobo: ASUSTeK model: P8H77-V version: Rev X.0x serial: 120902122101108
           Bios: American Megatrends version: 1103 date: 10/12/2012
CPU:       Quad core Intel Core i7-3770T CPU (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) 
           Clock Speeds: 1: 1600.00 MHz 2: 1600.00 MHz 3: 1600.00 MHz 4: 1600.00 MHz 5: 1600.00 MHz 6: 1600.00 MHz 7: 1600.00 MHz 8: 1600.00 MHz
Graphics:  Card: NVIDIA G80 [GeForce 8800 GTS] X.org: 1.13.1 drivers: nvidia,v4l tty size: 92x32 Advanced Data: N/A for root 
Audio:     Card-1: Intel 7 Series/C210 Series Chipset Family High Definition Audio Controller driver: snd_hda_intel
           Card-2: Logitech Webcam C300 driver: USB Audio
           Sound: Advanced Linux Sound Architecture ver: 1.0.25
Network:   Card: Atheros AR8161 Gigabit Ethernet driver: alx 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 50:46:5d:8b:29:4d
Drives:    HDD Total Size: 3000.6GB (16.0% used) 1: /dev/sdb WDC_WD10EADS 1000.2GB 
           2: /dev/sda WDC_WD10EADS 1000.2GB 3: USB /dev/sdc 28AS 1000.2GB 
Partition: ID: / size: 40G used: 7.3G (20%) fs: rootfs ID: / size: 40G used: 7.3G (20%) fs: ext4 
           ID: /home size: 839G used: 52G (7%) fs: ext4 ID: swap-1 size: 42.95GB used: 0.00GB (0%) fs: swap 
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 52C 
           Fan Speeds (in rpm): cpu: N/A 
Info:      Processes: 236 Uptime: 48 min Memory: 895.7/16008.7MB Client: Shell inxi: 1.7.24 
[root@localhost utente]# 

[NicCo]

I inform You that in the X13 repositories there are many updates:

precisely:
- Libdrm 2.4.41
- Mesa 9.0.2

and updated versions of some drivers
- Joystick driver 1.6.2
- VMware driver 13.0.0 (mouse & video)
- Intel 2.20.18 & 2.20.19


soon, after next media_info update,
you'll get also new stuff:
- XServer 1.13.2
- ATI fglrx 9.012

[NicCo]

Updates in repo: I'm updating to libdrm 2.4.2 and new Intel driver 2.21.0:
after the reboot, my PC works fine, video 2D and 3D are OK

Code: Select all

[root@localhost ~]# urpmi --auto-select
Per soddisfare le dipendenze, saranno installati i seguenti pacchetti:
 Pacchetto                      Versione     Release       Dist  DEpoch Arch. 
(supporto "Main_64_updates")
 lib64cairo2                    1.12.12      1             rosa  2012.1 x86_64 
(supporto "MIB-X13")
 lib64drm2                      2.4.42       69.1          mib   2012.1 x86_64 
 lib64drm_intel1                2.4.42       69.1          mib   2012.1 x86_64 
 lib64drm_nouveau2              2.4.42       69.1          mib   2012.1 x86_64 
 lib64drm_radeon1               2.4.42       69.1          mib   2012.1 x86_64 
 lib64kms1                      2.4.42       69.1          mib   2012.1 x86_64 
 lib64vdpau1                    0.6          69.1          mib   2012.1 x86_64 
 lib64wayland-client0           1.0.4        69.1          mib   2012.1 x86_64 
 lib64wayland-server0           1.0.4        69.1          mib   2012.1 x86_64 
 libdrm-common                  2.4.42       69.1          mib   2012.1 x86_64 
 x11-data-cursor-themes         1.0.3        69.1          mib   2012.1 noarch [root@localhost ~]# urpmi --auto-select
Per soddisfare le dipendenze, saranno installati i seguenti pacchetti:
 Pacchetto                      Versione     Release       Dist  DEpoch Arch. 
(supporto "Main_64_updates")
 lib64cairo2                    1.12.12      1             rosa  2012.1 x86_64 
(supporto "MIB-X13")
 lib64drm2                      2.4.42       69.1          mib   2012.1 x86_64 
 lib64drm_intel1                2.4.42       69.1          mib   2012.1 x86_64 
 lib64drm_nouveau2              2.4.42       69.1          mib   2012.1 x86_64 
 lib64drm_radeon1               2.4.42       69.1          mib   2012.1 x86_64 
 lib64kms1                      2.4.42       69.1          mib   2012.1 x86_64 
 lib64vdpau1                    0.6          69.1          mib   2012.1 x86_64 
 lib64wayland-client0           1.0.4        69.1          mib   2012.1 x86_64 
 lib64wayland-server0           1.0.4        69.1          mib   2012.1 x86_64 
 libdrm-common                  2.4.42       69.1          mib   2012.1 x86_64 
 x11-data-cursor-themes         1.0.3        69.1          mib   2012.1 noarch 
 x11-docs                       1.7          69.1          mib   2012.1 noarch 
 x11-driver-video-intel         2.21.0       69.1          mib   2012.1 x86_64 
Altri 6.8MB di spazio disco saranno utilizzati.
verranno scaricati 14MB di pacchetti.
Procedo con l'installazione di 13 pacchetti? (S/n) s
 x11-docs                       1.7          69.1          mib   2012.1 noarch 
 x11-driver-video-intel         2.21.0       69.1          mib   2012.1 x86_64 
Altri 6.8MB di spazio disco saranno utilizzati.
verranno scaricati 14MB di pacchetti.
Procedo con l'installazione di 13 pacchetti? (S/n) s