no sound in glx since installed new ubuntu

If you've had any problems with Nexuiz, or would like to report bugs, post here.

Moderators: Nexuiz Moderators, Moderators

Postby divVerent » Tue Nov 04, 2008 11:48 am

Maybe there were legal reasons for that. fglrx is not GPL.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

Postby Alien » Tue Nov 04, 2008 12:02 pm

This is not a reason to release in such state. So patch Xorg if you can't patch fglrx.

Talking about alsa:

application -> alsa-lib pulseaudio backend-> pulseaudio server-> alsa hardware layer
instead of application -> alsa-lib -> alsa hardware layer. Of course, it's a matter or personal preference.
Alien
Forum addon
 
Posts: 1212
Joined: Tue Apr 22, 2008 7:12 am

Postby divVerent » Tue Nov 04, 2008 12:09 pm

There are good reasons NOT to use alsa-lib directly, and to have a sound server in between, namely ALSA's bad support for multiple sound sources on one sound device. "dmix" is known broken, and what else is there? Nothing.

So they made a sound server, hoping it does that in a better way.

Also, the sound server can be accessed by apps directly. This has the advantage that apps do not NEED to be specifically written for ALSA, which is for Linux only. A pulseaudio app can be used on many other operating systems too.

Now for non-pulseaudio apps, the path must be alsa-lib -> pulseaudio -> alsa-lib -> alsa-kernel and NOT alsa-lib -> alsa-kernel, as only one app can use the alsa sound output in the kernel at once for many sound cards.

Or do you think

alsa-lib -> pulseaudio -> alsa-lib -> dmix -> alsa-kernel
alsa-lib -> dmix -> alsa-kernel

is any better? That way, pulseaudio-using apps have to go through TWO sound mixers. That would be REALLY insane...
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

Postby divVerent » Tue Nov 04, 2008 12:11 pm

Alien wrote:This is not a reason to release in such state. So patch Xorg if you can't patch fglrx.


Who says it was even POSSIBLE to patch X.org for this? What if the change was a larger change in the architecture of X.org, and nothing that can be easily reverted? Then you'd be able to EITHER support old fglrx, OR support new drivers for new hardware.

No, in this case, ATI was clearly at fault for dropping support for old hardware. Halting X.org development just for an old legacy driver made by a company which refuses to update that driver is certainly not a solution.

Here you rather see why closed source drivers are bad.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

Postby Alien » Tue Nov 04, 2008 12:22 pm

This WAS not architecture related. It was just stupid driver X -version check, which WAS FIXED later. Everything happened because xorg changed numbering scheme and nobody at ati fixed their abandoned drivers. Far easier change was to change version output instead of blaming ati. End users do not care about this, they want working system (my windows were working, blah blah).
Alien
Forum addon
 
Posts: 1212
Joined: Tue Apr 22, 2008 7:12 am

Postby divVerent » Tue Nov 04, 2008 12:39 pm

I still see no reason for Ubuntu or ANY OTHER sane distro to mess with stuff like version number reporting (which IS important for when X.org have to deal bug reports by Ubuntu users) because some third party driver for outdated hardware is broken.

And what if another driver (e.g. the nvidia driver) checks for the NEW version number scheme, and will fail with the old one? What now?
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

Postby Alien » Tue Nov 04, 2008 12:43 pm

Ok, so it seems that the best thing is to leave users for their own fate. Sorry, I don't agree and don't want to argue more.
Alien
Forum addon
 
Posts: 1212
Joined: Tue Apr 22, 2008 7:12 am

Postby divVerent » Tue Nov 04, 2008 1:26 pm

?

A working driver for these cards is contained in X.org, which was why ATI discontinued support. Note that ATI discontinued support. Not Ubuntu.

So where is your problem? "BUT I WANT TO USE THAT DRIVER FROM ATI INSTEAD!!!!!!!!!eleven"?

BTW, same happened with nvidia. IIRC their legacy driver for Geforce 1 cards no longer compiles in current kernels (but I may be wrong with this). Are you expecting distributions to stay at old kernel versions so that legacy driver works?

Or, a case I have. I have an eeepc. To change the CPU speed, I need a special "eee" kernel module from http://code.google.com/p/eeepc-linux/ - but this module does not compile with Fedora's current kernel. Now is Fedora at fault for this? No, the authors of this module are, as well as the Linux Kernel developers for not keeping a stable API for drivers.
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

Postby Alien » Tue Nov 04, 2008 1:34 pm

At that time there was no 3d acceleration in oss driver (r300 is experimental).
Alien
Forum addon
 
Posts: 1212
Joined: Tue Apr 22, 2008 7:12 am

Postby divVerent » Tue Nov 04, 2008 1:46 pm

Alien wrote:At that time there was no 3d acceleration in oss driver (r300 is experimental).


SavageX wrote:You are saying that it's not ATI/Nvidia's fault but write "cause ATI stopped the drivers development for older cards." The reasoning behind them (=ATI) stopping fglrx-development was that there are open-source drivers available already (with 3D support), so why not let user use those free drivers?


Now what? The open source drivers being "experimental" is no reason against, because, what software you use is NOT experimental?
1. Open Notepad
2. Paste: ÿþMSMSMS
3. Save
4. Open the file in Notepad again

You can vary the number of "MS", so you can clearly see it's MS which is causing it.
divVerent
Site admin and keyboard killer
 
Posts: 3809
Joined: Thu Mar 02, 2006 4:46 pm
Location: BRLOGENSHFEGLE

PreviousNext

Return to Nexuiz - Support / Bugs

Who is online

Users browsing this forum: No registered users and 1 guest

cron