LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Suse/Novell (http://www.linuxquestions.org/questions/suse-novell-60/)
-   -   10.3 32 Bit Realtek HD Audio Fixed - but will 64 bit version work (http://www.linuxquestions.org/questions/suse-novell-60/10-3-32-bit-realtek-hd-audio-fixed-but-will-64-bit-version-work-642835/)

1kyle 05-17-2008 06:20 AM

10.3 32 Bit Realtek HD Audio Fixed - but will 64 bit version work
 
Hi all

I'm using a 32 bit version of SUSE 10.3. Downloading the 5.0.3 HD Audio driver from the realtek site and following the instructions CAREFULLY I got sound working fine.

http://122.146.118.42/downloads/down...&GetDown=false



Would these drivers also compile on a 64 bit system.

(The install is quite simple - download the drivers switch to the directory you extract the files to and run ./install

Then re-boot and BEFORE STARTING X run ALSACONF as root.)

Note the ALSACONF starts automatically after the install -- quit this and re-boot. Then run ALSACONF again from a CONSOLE -- don't start X.

I'd like to go to 64 bit especially for release 11.0 but not if I can't get sound working.


BTW The Linux HD driver supports these codecs

Support Codec list:
====AC97 Codec=====
ALC100,100P
ALC200,200P
ALC650D
ALC650E
ALC650F
ALC650
ALC655
ALC653
ALC658
ALC658D
ALC850
ALC101
ALC202
ALC250
ALC203

====HD Audio codec ====
ALC260
ALC262
ALC268
ALC269
ALC660
ALC660VD
ALC662
ALC663
ALC861
ALC861VD
ALC880
ALC882
ALC883
ALC885
ALC888
ALC889A


Cheers

-K

egandb 06-26-2008 06:36 PM

Be careful!
 
If you're running openSUSE 10.3 and you try to use the auto ./install as suggested by 1kyle above, you might run into the same problem I did. I did as 1kyle suggested and per the instructions within Realtek's driver LinuxPkg_5.04.tar.bz2 tarball. I didn't read through the ./install script first, where there are these instructions on lines 43-48 of the ./install script:

Code:

## for x86
echo "Remove old alsa library"
rm -rf /lib/libasound.* > /dev/null 2>&1
rm -rf /lib64/libasound.* > /dev/null 2>&1
rm -rf /usr/lib/libasound.* > /dev/null 2>&1
rm -rf /usr/lib64/libasound.* > /dev/null 2>&1

When the installation of the Realtek drivers was completed and I rebooted, I got the following when I tried to login as root (or replace root with any other user that was on my system):

Code:

/etc/X11/xim: Checking whether an input method should be started.
/etc/X11/xim: user environment variable LANG=POSIX
/etc/X11/xim: user environment variable LC_CTYPE=en_US.UTF-8
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale en_US.UTF-8 ...
There is no default input method for the current locale.
No profile for user 'root' found
===== BEGIN MILESTONES (/usr/sbin/sabayon-apply) =====
MainThread 2008/06/05 12:03:34.1511 (sabayon-apply): Fatal exception!  Exiting abnormally.
MainThread 2008/06/05 12:03:34.1521 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 99, in <module>
    sys.exit (util.EXIT_CODE_FATAL)
SystemExit: 1

===== END MILESTONES (/usr/sbin/sabayon-apply) =====
===== BEGIN RING BUFFER (/usr/sbin/sabayon-apply) =====
MainThread 2008/06/05 12:03:34.1511 (sabayon-apply): Fatal exception!  Exiting abnormally.
MainThread 2008/06/05 12:03:34.1521 (sabayon-apply): Traceback (most recent call last):
  File "/usr/sbin/sabayon-apply", line 99, in <module>
    sys.exit (util.EXIT_CODE_FATAL)
SystemExit: 1

===== END RING BUFFER (/usr/sbin/sabayon-apply) =====


This configuration for the debug log can be re-created
by putting the following in ~/sabayon-debug-log.conf
(use ';' to separate domain names):

[debug log]
max lines = 1000
/usr/bin/gnome-session: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory

I had to reinstall the entire operating system!

What did work was the manual installation of the drivers, but I had to make sure to install the kernel-source and the GCC compiler first.

The other thing I had to do was run alsaconf from a console prompt before running alsamixer before logging into the GUI.

I hope this saves someone from a lot of re-installation work by running the ./install script. Just make sure libasound (AKA: old ALSA library) doesn't need to be there for a user to be able to login.

You could always manually back-up the /lib/libasound. , /lib64/libasound.* , /usr/lib/libasound.* and /usr/lib64/libasound.* directories first, just in case!!


All times are GMT -5. The time now is 02:20 PM.