LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Multimedia problems in -current (https://www.linuxquestions.org/questions/slackware-14/multimedia-problems-in-current-4175457212/)

FeyFre 04-07-2013 05:08 AM

Multimedia problems in -current
 
Hi

I have installed -current on my PC, not trying to setup it. So have 2 problems:
1. Cannot install AMD driver for video. ./amd-driver-install*run --buildpkg finishes with error of unfounded version.h
Tryied to do instructions from here - that instruction is fake I think because it is already broken on 3rd step(not such /lib/modules/fglrx/build_mod directory left after installer breaks).


2. There are no sound in any browser I run: opera, firefox, chrome. But Amarok plays nicely. mp3blaster to. Installed pulseaudio from SBo - no result

Is there any workable solutions for such problems?

EDIT: part1 not more necessary now, since driver causes segfault of X.

willysr 04-07-2013 07:29 AM

Have you installed the kernel-source package. Typically most driver requires kernel source in order to compile a module linked to the kernel

FeyFre 04-07-2013 07:39 AM

Full installation of course. I have managed to trick it.
1. Run installer, select wanted action to do(to build package for instance), but not confirm it.
2. Switch to other terminal, navigate to temporary directory created by installer, and apply patch there.
3. Confirm action.
Now it works.
Installed, rebooted, configured, running X.
But soon enough happened bad think: X segfaulted in fglrx code(google chrome in stack trace present also). So for now I reverted back.
But second problem not solved yet.

willysr 04-07-2013 07:58 AM

that's not how to properly build the driver

FeyFre 04-07-2013 08:49 AM

willysr, that how it builds. And since there is no alternative it is properly build river by definition.

willysr 04-07-2013 09:06 AM

You can create the lib/modules/fglrx/build_mod directory using root
I think Henry has created that directory before as he continuously following Catalyst driver development

FeyFre 04-07-2013 09:38 AM

So I did it. It is empty now, but exists! Then, as instruction advices, I did "patch -p0 <3.8.patch" there, and? surprise, surprise, it fails, because patch cannot patch non-existing files.
Nothing changed! Installer does not uses that path. And Henry's algorithm as much useless as our conversation here.

willysr 04-07-2013 09:52 AM

did you run the installer first? It's said that when you encounter any error, exit the installer and start patching it

Darth Vader 04-07-2013 09:53 AM

Quote:

Originally Posted by FeyFre (Post 4926859)
... as much useless as our conversation here.

Chill out, young padawan!

Nobody here is on Slackware Call Center Support! That guy spent his time, trying to help you, out of generosity. You should respect that.

FeyFre 04-07-2013 10:47 AM

willysr, I DID it. I am mature enough to follow instructions without errors.
1. change directory to the path where the installer is
DONE. In my case it is /usr/src
2. run the installer as root (superuser):
# ./amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run
DONE.
3. follow the instructions, at the end of installation process you will get notice that there are some errors.
DONE. Yes, there was errors.
4. exit the installer
DONE.
5. at console, copy the patch file (fglrx-3.8.patch) to /lib/modules/fglrx/build_mod/
NOT DONE. There is not any /lib/modules/fglrx/build_mod/ directory. OK, created it(it is empty now), on copied given patch file. DONE.
6. (optional, if you don't find version.h in /lib/modules/3.8.2/build/include/linux) Make symlink of version.h:
# ln -s /lib/modules/3.8.2/build/include/generated/uapi/linux/version.h /lib/modules/3.8.2/build/include/linux/version.h
DONE. In my case it was 3.8.4-smp
7. change directory to /lib/modules/fglrx/build_mod/
DONE.
8. patch the fglrx source:
# patch -p0 < fglrx-3.8.patch
NOT DONE. patch asks me for file name to patch to. What I should answer here?
9. compile the fglrx modules:
# ./make.sh
# cd ..
# ./make_install.sh
NOT CAN DO. There is no such files make.sh and make_install.sh
10. reboot
NOT DONE. No reason.
Quote:

start patching it
Start patching what? Empty space? Installer unpacks its sources into temporary directory and removes it completely it after exit. 4th step of instruction breaks whole instruction. Does anybody has reasons to consider me child/idiot? In any case, I done with this part of problem since, I do not need X to segfault every 5 minutes.

Darth Vader 04-07-2013 11:15 AM

Quote:

Originally Posted by FeyFre (Post 4926906)
willysr, I DID it. I am mature enough to follow instructions without errors.
1. change directory to the path where the installer is
DONE. In my case it is /usr/src
2. run the installer as root (superuser):
# ./amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run
DONE.
3. follow the instructions, at the end of installation process you will get notice that there are some errors.
DONE. Yes, there was errors.
4. exit the installer
DONE.
5. at console, copy the patch file (fglrx-3.8.patch) to /lib/modules/fglrx/build_mod/
NOT DONE. There is not any /lib/modules/fglrx/build_mod/ directory. OK, created it(it is empty now), on copied given patch file. DONE.
6. (optional, if you don't find version.h in /lib/modules/3.8.2/build/include/linux) Make symlink of version.h:
# ln -s /lib/modules/3.8.2/build/include/generated/uapi/linux/version.h /lib/modules/3.8.2/build/include/linux/version.h
DONE. In my case it was 3.8.4-smp
7. change directory to /lib/modules/fglrx/build_mod/
DONE.
8. patch the fglrx source:
# patch -p0 < fglrx-3.8.patch
NOT DONE. patch asks me for file name to patch to. What I should answer here?
9. compile the fglrx modules:
# ./make.sh
# cd ..
# ./make_install.sh
NOT CAN DO. There is no such files make.sh and make_install.sh
10. reboot
NOT DONE. No reason.
Start patching what? Empty space? Installer unpacks its sources into temporary directory and removes it completely it after exit. 4th step of instruction breaks whole instruction. Does anybody has reasons to consider me child/idiot? In any case, I done with this part of problem since, I do not need X to segfault every 5 minutes.

How about running that:

Code:

./amd-driver-installer-13.1-x86.x86_64.run --extract catalyst_files
Then look what is in the new catalyst_files (sub-)directory...

hotchili 04-07-2013 11:22 AM

If you run slackware-current it will probably not work anyway.
Xorg is too new for catalyst driver (unless there was a new catalyst update). (I am still running the old xorg here...)

FeyFre 04-07-2013 11:24 AM

Quote:

How about running that:
Not. Instruction says just run as usual. I follow strictly instruction. Doesn't works. (Consider me stupid clerk instead of experienced developer.)
And YES, I did tried that too. Failed and failed again.
So forget that. Now I interested in second issue more(no sound in browsers).

Darth Vader 04-07-2013 11:42 AM

Forget that instructions. Here is how you can make a properly installation of your fglrx in Slackware:

1. Be sure that that the symlink /usr/src/linux-3.8.4/include/linux/version.h exists.

2. mkdir -p /etc/ati/patch

3. copy the provided fglrx-3.8.patch patch (which is correct) as /etc/ati/patch/patch-9.012-3.8.4-smp

4. run ./amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --buildpkg

5. Install the new generated fglrx-9.012-x86-1.tgz package.

6. run aticonfig --initial

willysr 04-07-2013 11:48 AM

Are you running Slackware64-Current or Slackware-Current?
Just to be sure since the driver mentioned is for x86_64

Darth Vader 04-07-2013 11:52 AM

Quote:

Originally Posted by willysr (Post 4926944)
Slackware64-Current or Slackware-Current?

My bet is on i486-current because he mentioned that have the kernel 3.8.4-smp. There is no SMP kernel variant on x86_64.

willysr 04-07-2013 12:22 PM

and the article is using x86_64. No wonder he gets an empty directory :)

Pixxt 04-07-2013 02:22 PM

I always use
Quote:

./amd-driver-installer-catalyst-13.1-linux-x86.x86_64.run --buildpkg Slackware/Slackware

TobiSGD 04-07-2013 03:38 PM

Just to clarify some things here:
1. AMD's driver is a unified version that is made for both, 32 and 64 bit, versions of Linux, so that driver is in fact the correct one.
2. While the patch will provide compatibility for kernel 3.8 the driver still lacks support for xorg-server version 1.14, which is currently used in -current. Given the speed of AMD's driver development we may get that in 3-6 months.

So if you have/want to use the Catalyst driver your only option currently is to run 14.0 or -current with an older version of Xorg.

BroX 04-07-2013 06:15 PM

FWIW: latest AMD Catalyst 13.3 LINUX Beta Driver now supports kernels 3.7 and 3.8 so no need to patch it. You can build a neat Slackware package using
Code:

# sh amd-driver-installer-catalyst-13.3-beta3-linux-x86.x86_64.run --buildpkg Slackware/Slackware
Unfortunately, it still lacks support for xorg-server version 1.14.

FeyFre 04-08-2013 03:36 AM

Quote:

Originally Posted by hotchili (Post 4926922)
If you run slackware-current it will probably not work anyway.
Xorg is too new for catalyst driver (unless there was a new catalyst update). (I am still running the old xorg here...)

It is possible, but the reason why I installed -current is in my Slackware-14 installation X starts into black screen, not matters how I start it. In -current it starts even w/o this catalyst driver. So I have not wide choice.
Quote:

Originally Posted by Darth Vader
Forget that instructions. Here is how you can make a properly installation of your fglrx in Slackware:

1. Be sure that that the symlink /usr/src/linux-3.8.4/include/linux/version.h exists.
...
6. run aticonfig --initial

Thanks, I shall try it today later.

Quote:

Are you running Slackware64-Current or Slackware-Current?
Just to be sure since the driver mentioned is for x86_64
i686, and no, that instruction and catalyst driver are unified.
Quote:

So if you have/want to use the Catalyst driver your only option currently is to run 14.0 or -current with an older version of Xorg.
I would be happy to use 14.0, but as I mentioned earlier its Xorg has problems with video even on provided with kernels drivers(starting into black screen), but -current's version works. So choosing between does-not-work-at-all(14.0) and works(-current) I choose works one.

But now I trying to guess out what wrong with my audio subsystem, or probably configuration of it so half of software does not emits sounds.

TobiSGD 04-08-2013 05:32 AM

You mentioned that you installed Pulseaudio, I recently switched to that, too, but it only worked after creating a file /etc/asound.conf with this content:
Code:

# Use PulseAudio by default
pcm.!default {
  type pulse
  fallback "sysdefault"
  hint {
    show on
    description "Default ALSA Output (currently PulseAudio Sound Server)"
  }
}

ctl.!default {
  type pulse
  fallback "sysdefault"
}

You can try if that helps in your case.


All times are GMT -5. The time now is 04:51 PM.