[opensuse] Corrupted audio driver 10.2/64bit?
Hi, Am running Suse 10.2 X64, and up until the other day, working perfectly (well, almost.) Have had a few issues intermittently with the audio drivers (onboard, Realtek/Intel/VIA/Azalia HD Audio), with trying to get some applications to 'share' the sound card, but nothing huge.. until now! Thought I would be clever (1st mistake!) and see if there were any drivers specifically for the sound card, so came across realtek-linux-audiopack-4.05f on the Realtek site (http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false#High Definition Audio Codecs) Installed and since have no sound at all. in KDE if trying to play sound, either get nothing, or the message "xine was unable to initialize any audio drivers." KMix shows up as empty. Trying to use Yast (it recognises VIA High Definition Audio Controller - Not configured) to update drivers gives me :" an error occurred during the installation of VIA High Defintion Audio Controller. The kernel module snd-hda-intel for sound support could not be loaded. This can be caused by incorrect module parameters, including invalid IO or IRQ parameters." After having done this, running lsmod shows that the module IS actually loaded, but get the same messages.... I REALLY don't want to have to rebuild the OS. Can't find any uninstall for realtek-linux-audiopack-4.05f?? Have deleted the directory created and makes no difference. I'm NOT an expert, but know a little.... I'm assuming that there is a module loading that shouldn't be... or something wrong with the loading of a module, but can't figure out where all of that is done. Any help appreciated!! John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 21 May 2007 06:33, John wrote:
I REALLY don't want to have to rebuild the OS. Can't find any uninstall for realtek-linux-audiopack-4.05f?? Have deleted the directory created and makes no difference. I'm NOT an expert, but know a little.... I'm assuming that there is a module loading that shouldn't be... or something wrong with the loading of a module, but can't figure out where all of that is done. Any help appreciated!!
If you looked in install script than you can see it removed all of alsa without using rpm, so YaST believes that alsa is still present. I didn't looked details so first I would try to "update" alsa. If it fails than try to "uninstall" using YaST, and again install. If YaST complains about dependencies, as alsa is dependency for other packages, simply ignore it and don't let YaST to remove all other packages that depend on alsa because if you let it do that than you will have to reinstall quite a few. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Rajko M. <rmatov101@charter.net> [05-21-07 21:19]:
On Monday 21 May 2007 06:33, John wrote:
I REALLY don't want to have to rebuild the OS. Can't find any uninstall for realtek-linux-audiopack-4.05f?? Have deleted the directory created and makes no difference. I'm NOT an expert, but know a little.... I'm assuming that there is a module loading that shouldn't be... or something wrong with the loading of a module, but can't figure out where all of that is done. Any help appreciated!!
If you looked in install script than you can see it removed all of alsa without using rpm, so YaST believes that alsa is still present. I didn't looked details so first I would try to "update" alsa.
No, the first action should be to rebuild the rpm database, "man rpm" search for rebuilddb. Then Yast will know what is on the system and can take whatever steps necessary. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 21 May 2007 20:46, Patrick Shanahan wrote:
* Rajko M. <rmatov101@charter.net> [05-21-07 21:19]:
On Monday 21 May 2007 06:33, John wrote:
I REALLY don't want to have to rebuild the OS. Can't find any uninstall for realtek-linux-audiopack-4.05f?? Have deleted the directory created and makes no difference. I'm NOT an expert, but know a little.... I'm assuming that there is a module loading that shouldn't be... or something wrong with the loading of a module, but can't figure out where all of that is done. Any help appreciated!!
If you looked in install script than you can see it removed all of alsa without using rpm, so YaST believes that alsa is still present. I didn't looked details so first I would try to "update" alsa.
No, the first action should be to rebuild the rpm database, "man rpm" search for rebuilddb. Then Yast will know what is on the system and can take whatever steps necessary.
I don't know internals of rpm --rebuilddb but I was using it and it seems that it doesn't search hard disk for installed third party software. The sound driver is: realtek-linux-audiopack-4.05f.tar.bz2 and it will compile alsa driver and some XRealMixer v0.5 from sources. John mentioned that he removed directories, but I didn't ask which as installing alsa via YaST should bring sound in order. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Rajko M. <rmatov101@charter.net> [05-21-07 22:20]:
I don't know internals of rpm --rebuilddb but I was using it and it seems that it doesn't search hard disk for installed third party software.
The sound driver is: realtek-linux-audiopack-4.05f.tar.bz2 and it will compile alsa driver and some XRealMixer v0.5 from sources. John mentioned that he removed directories, but I didn't ask which as installing alsa via YaST should bring sound in order.
Using an rpm-based system requires the use of rpm packages. The use of tar-balls will corrupt the rpm system and do not show up in the rpm database. Tar installations can replace libraries required by your (rpm) installed system and break things as you seem to have found with the alsa package. Removal of tar installations and source built installations is very difficult. You must be experienced and knowledgable to incorporate a mix. The only really safe usage for the unknowning is those tar packages which are self contained static packages which install in their own directory and are removable by deleting that directory structure. If you *must* build a driver (as it appears) you should incorporate the use of "checkinstall" which generates rpm packages for installation after build and allows for save removal, if necessary or desired. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 21 May 2007 22:13, Patrick Shanahan wrote:
* Rajko M. <rmatov101@charter.net> [05-21-07 22:20]:
I don't know internals of rpm --rebuilddb but I was using it and it seems that it doesn't search hard disk for installed third party software.
The sound driver is: realtek-linux-audiopack-4.05f.tar.bz2 and it will compile alsa driver and some XRealMixer v0.5 from sources. John mentioned that he removed directories, but I didn't ask which as installing alsa via YaST should bring sound in order.
Using an rpm-based system requires the use of rpm packages. The use of tar-balls will corrupt the rpm system and do not show up in the rpm database. Tar installations can replace libraries required by your (rpm) installed system and break things as you seem to have found with the alsa package. Removal of tar installations and source built installations is very difficult.
You must be experienced and knowledgable to incorporate a mix. The only really safe usage for the unknowning is those tar packages which are self contained static packages which install in their own directory and are removable by deleting that directory structure.
If you *must* build a driver (as it appears) you should incorporate the use of "checkinstall" which generates rpm packages for installation after build and allows for save removal, if necessary or desired.
Well, it's not my problem :-) I always check before using tarballs for all reasons that you listed above. John (original poster) can look in install script and see what was removed, but as you said it is not easy. That is the reason I proposed reinstallation of alsa. If that doesn't help, than he can always analyze the problem which can take more time than reinstallation of whole system, and of course next time install and use "checkinstall". -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Monday 21 May 2007 22:13, Patrick Shanahan wrote:
* Rajko M. <rmatov101@charter.net> [05-21-07 22:20]:
I don't know internals of rpm --rebuilddb but I was using it and it seems that it doesn't search hard disk for installed third party software.
The sound driver is: realtek-linux-audiopack-4.05f.tar.bz2 and it will compile alsa driver and some XRealMixer v0.5 from sources. John mentioned that he removed directories, but I didn't ask which as installing alsa via YaST should bring sound in order.
Using an rpm-based system requires the use of rpm packages. The use of tar-balls will corrupt the rpm system and do not show up in the rpm database. Tar installations can replace libraries required by your (rpm) installed system and break things as you seem to have found with the alsa package. Removal of tar installations and source built installations is very difficult.
You must be experienced and knowledgable to incorporate a mix. The only really safe usage for the unknowning is those tar packages which are self contained static packages which install in their own directory and are removable by deleting that directory structure.
If you *must* build a driver (as it appears) you should incorporate the use of "checkinstall" which generates rpm packages for installation after build and allows for save removal, if necessary or desired.
Well, it's not my problem :-) I always check before using tarballs for all reasons that you listed above.
John (original poster) can look in install script and see what was removed, but as you said it is not easy. That is the reason I proposed reinstallation of alsa. If that doesn't help, than he can always analyze the problem which can take more time than reinstallation of whole system, and of course next time install and use "checkinstall".
Sorry, don't mean to keep on about this (obviously haven't had any success), can't I just remove a hardware device, and let Suse reinstall it.... That would be a lot easier... ;-) John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 24 May 2007 05:49, John wrote:
Sorry, don't mean to keep on about this (obviously haven't had any success), can't I just remove a hardware device, and let Suse reinstall it.... That would be a lot easier... ;-) John.
You have to reinstall alsa that is compiled for SUSE as suggested in first reply. Now alsa is registered as installed, you can look in YaST Software Management, as Realtek installer removed it without using rpm program so alsa is still present in database. Rebuild database with rpm --rebuilddb probably will not work as it is meant to correct database entries not to scan system and see what is installed. The other option checkinstall is for the future installations of similar software, now it can't correct anything. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Rajko M. <rmatov101@charter.net> [05-24-07 20:44]: [...]
You have to reinstall alsa that is compiled for SUSE as suggested in first reply.
Now alsa is registered as installed, you can look in YaST Software Management, as Realtek installer removed it without using rpm program so alsa is still present in database. Rebuild database with rpm --rebuilddb probably will not work as it is meant to correct database entries not to scan system and see what is installed. The other option checkinstall is for the future installations of similar software, now it can't correct anything.
No, aiui, that is the function of 'rpm --rebuilddb'. from TFM: REBUILD DATABASE OPTIONS The general form of an rpm rebuild database command is rpm {--initdb|--rebuilddb} [-v] [--dbpath DIRECTORY] [--root DIRECTORY] Use --initdb to create a new database, use --rebuilddb to rebuild the database indices from the installed package headers. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 OpenSUSE Linux http://en.opensuse.org/ Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Does a "reinstall" over the top, fix probs like that?? John On 5/25/07, Rajko M. <rmatov101@charter.net> wrote:
On Thursday 24 May 2007 05:49, John wrote:
Sorry, don't mean to keep on about this (obviously haven't had any success), can't I just remove a hardware device, and let Suse reinstall it.... That would be a lot easier... ;-) John.
You have to reinstall alsa that is compiled for SUSE as suggested in first reply.
Now alsa is registered as installed, you can look in YaST Software Management, as Realtek installer removed it without using rpm program so alsa is still present in database. Rebuild database with rpm --rebuilddb probably will not work as it is meant to correct database entries not to scan system and see what is installed. The other option checkinstall is for the future installations of similar software, now it can't correct anything.
-- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 24 May 2007 22:46, John Bennett wrote:
On 5/25/07, Rajko M. <rmatov101@charter.net> wrote:
On Thursday 24 May 2007 05:49, John wrote:
Sorry, don't mean to keep on about this (obviously haven't had any success), can't I just remove a hardware device, and let Suse reinstall it.... That would be a lot easier... ;-) John.
You have to reinstall alsa that is compiled for SUSE as suggested in first reply.
Now alsa is registered as installed, you can look in YaST Software Management, as Realtek installer removed it without using rpm program so alsa is still present in database. Rebuild database with rpm --rebuilddb probably will not work as it is meant to correct database entries not to scan system and see what is installed. The other option checkinstall is for the future installations of similar software, now it can't correct anything.
Does a "reinstall" over the top, fix probs like that??
Reinstall over the top of what? Existing installation? Maybe, call it update existing system. Running system repair from instalation CD/DVD is one of options. But before you use system repair, just to make sure that I'm not wrong, open console program, login as root and run: rpm --rebuilddb and when is rpm done, try to reinstall sound card using YaST. If it doesn't help. Than use method in first reply. And don't be afraid, just try it. The worst that can happen is already done. If this doesn't work than I have to see what exactly Realtek install script did to your openSUSE installation. Whatever was done is not irreversible. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rajko M. wrote:
On Thursday 24 May 2007 22:46, John Bennett wrote:
On 5/25/07, Rajko M. <rmatov101@charter.net> wrote:
On Thursday 24 May 2007 05:49, John wrote:
Sorry, don't mean to keep on about this (obviously haven't had any success), can't I just remove a hardware device, and let Suse reinstall it.... That would be a lot easier... ;-) John.
You have to reinstall alsa that is compiled for SUSE as suggested in first reply.
Now alsa is registered as installed, you can look in YaST Software Management, as Realtek installer removed it without using rpm program so alsa is still present in database. Rebuild database with rpm --rebuilddb probably will not work as it is meant to correct database entries not to scan system and see what is installed. The other option checkinstall is for the future installations of similar software, now it can't correct anything.
Does a "reinstall" over the top, fix probs like that??
Reinstall over the top of what? Existing installation? Maybe, call it update existing system.
Running system repair from instalation CD/DVD is one of options.
But before you use system repair, just to make sure that I'm not wrong, open console program, login as root and run: rpm --rebuilddb and when is rpm done, try to reinstall sound card using YaST.
If it doesn't help. Than use method in first reply. And don't be afraid, just try it. The worst that can happen is already done. If this doesn't work than I have to see what exactly Realtek install script did to your openSUSE installation.
Whatever was done is not irreversible.
Well, gave up and did a reinstall...... Had tried the rebuilddb bit - didn't work, still the same error. Tried most of the other suggestions as well, and nothing worked, so now am rebuilding from scratch - at least I now have sound!! And being used to Windows systems, am a fairly regular rebuilder anyway.... :-) Thanks for all the tips, and if I'm feeling particularly brave one day, might try the Realtek drivers again, but a little more carefully next time! (checkinstall, was it??!!) Thanks a lot, John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 24 May 2007 22:46, John Bennett wrote: I didn't receive any messages in mail box and looking for reasons found your reply in archives.
Well, gave up and did a reinstall...... Had tried the rebuilddb bit - didn't work, still the same error. Tried most of the other suggestions as well, and nothing worked, so now am rebuilding from scratch - at least I now have sound!! And being used to Windows systems, am a fairly regular rebuilder anyway.... :-)
Thanks for all the tips, and if I'm feeling particularly brave one day, might try the Realtek drivers again, but a little more carefully next time! (checkinstall, was it??!!)
Yes, but first look for SUSE specific rpm package. Redhat or Fedora rpm may work, but it can have the same effect as those that you have already seen.
Thanks a lot, John.
Linux is for the most of it's users the way to learn more and they are very reluctant to "just reinstall" even if that means more time used to find a solution. That is the reason to give you a lot of ideas just to avoid reinstallation. If the system is properly configured with separate /home than reinstallation can be faster than fixing it. -- Regards, Rajko. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Patrick Shanahan wrote:
* Rajko M. <rmatov101@charter.net> [05-21-07 22:20]:
I don't know internals of rpm --rebuilddb but I was using it and it seems that it doesn't search hard disk for installed third party software.
The sound driver is: realtek-linux-audiopack-4.05f.tar.bz2 and it will compile alsa driver and some XRealMixer v0.5 from sources. John mentioned that he removed directories, but I didn't ask which as installing alsa via YaST should bring sound in order.
Using an rpm-based system requires the use of rpm packages. The use of tar-balls will corrupt the rpm system and do not show up in the rpm database. Tar installations can replace libraries required by your (rpm) installed system and break things as you seem to have found with the alsa package. Removal of tar installations and source built installations is very difficult.
You must be experienced and knowledgable to incorporate a mix. The only really safe usage for the unknowning is those tar packages which are self contained static packages which install in their own directory and are removable by deleting that directory structure.
If you *must* build a driver (as it appears) you should incorporate the use of "checkinstall" which generates rpm packages for installation after build and allows for save removal, if necessary or desired.
Just installed checkinstall and in the absence of a man page... decided to use checkinstall -h to find out about usage .... the result was... well.. a bit weird :-o I think I have deciphered enough to use it, but I get the impression documentation needs a little work :-) . -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGUrtzasN0sSnLmgIRAoeDAKDh9Tmzdifx3E2C09gPLVdDMM4ctQCgwrB1 Fqmg4oi9L5hcVAqnoiuBH1M= =FzV/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
Just installed checkinstall and in the absence of a man page... decided to use
checkinstall -h
to find out about usage .... the result was... well.. a bit weird :-o I think I have deciphered enough to use it, but I get the impression documentation needs a little work :-)
You don't need any options listed in the -h list. Ordinarily you would ./configure [options] make make install to install a tarball and to use checkinstall you just replace "make install" with "checkinstall". That will build an rpm package that you either install with rpm -Uvh /complete/path/to/RPM-PACKAGE or with Yast. When you use Yast you have to add the /complete/path/to/RPM-PACKAGE to the Yast sources. Alternatively you could click in Konqueror on the file, because that fires up Yast, with the path already added IIRC. Regards, Regards, -- Jos van Kan registered Linux user #152704 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
G T Smith -
John -
John Bennett
-
Jos van Kan -
Patrick Shanahan -
Rajko M.