All of lore.kernel.org
 help / color / mirror / Atom feed
* Some installation questions
@ 2010-01-30 11:42 Klaus Schulz
  2010-02-01  8:07 ` Pavel Hofman
  0 siblings, 1 reply; 2+ messages in thread
From: Klaus Schulz @ 2010-01-30 11:42 UTC (permalink / raw)
  To: alsa-devel

Hi there.

I am still maintaining the (inoffical) Ubuntu Alsa Upgrade Script over at
http://ubuntuforums.org/showthread.php?t=1046137


Perhaps somebody can give me a hint on some installation problems I am
running into:


1. Quite some people reporting that /proc/asound/version is still showing
the "original" revision  after running  the upgrade-script instead of
1.0.22.1.

   What could be the issue? What is setting /proc/asound/version?


2. I also introduced a kind of restore function. What it does is basically
reinstalling all the required Ubuntu packages from the repo to overwrite the
(by my script) upgraded files again.
    a. My first problem was that I was only able to get the original modules
activated when running the module assistant. ( module-assistant -f -t -q a-i
alsa-source )
       Just a re-installation of kernel packages and alsa-packages didn't
work.
    b. When redoing the Alsa Upgrade  after the restore (by my script) , I
still see in /proc/asound the old Alsa version.

    Looks again a bit like I am having slight problems with the module
handling



FYI:

Below I run after the "make install" of the driver package

The way the .ko files are handled is that they are copied to
/lib/modules/`uname -r`/kernel/sound/

#####################

cd ${ALSASRCDIR}/${DRIVER}/

find ./ -name ''*.ko'' > /tmp/alsa_modules

header "Copy modules to target directories..."
if [ "`uname -a| grep "2.6.24"`" != "" ] ; then
 tar -cv -T /tmp/alsa_modules -f /lib/modules/`uname
-r`/ubuntu/sound/alsa-driver/${DRIVER}.tar
 cd /lib/modules/`uname -r`/ubuntu/sound/alsa-driver
 else
 tar -cv -T /tmp/alsa_modules -f /lib/modules/`uname
-r`/kernel/sound/${DRIVER}.tar
 cd /lib/modules/`uname -r`/kernel/sound/
fi
#Extract new modules, overwriting old ones
tar -xvf ${DRIVER}.tar
rm *.tar

depmod -a


##############################


I obviously lack some kind of understanding how all this works.

Perhaps somebody can show me directions how to tackle the subject.


THX
\Klaus

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Some installation questions
  2010-01-30 11:42 Some installation questions Klaus Schulz
@ 2010-02-01  8:07 ` Pavel Hofman
  0 siblings, 0 replies; 2+ messages in thread
From: Pavel Hofman @ 2010-02-01  8:07 UTC (permalink / raw)
  To: Klaus Schulz; +Cc: alsa-devel

Klaus Schulz napsal(a):
> Hi there.
> 
> I am still maintaining the (inoffical) Ubuntu Alsa Upgrade Script over at
> http://ubuntuforums.org/showthread.php?t=1046137
> 
> 
> Perhaps somebody can give me a hint on some installation problems I am
> running into:
> 
> 
> 1. Quite some people reporting that /proc/asound/version is still showing
> the "original" revision  after running  the upgrade-script instead of
> 1.0.22.1.
> 
>    What could be the issue? What is setting /proc/asound/version?
> 
> 
> 2. I also introduced a kind of restore function. What it does is basically
> reinstalling all the required Ubuntu packages from the repo to overwrite the
> (by my script) upgraded files again.
>     a. My first problem was that I was only able to get the original modules
> activated when running the module assistant. ( module-assistant -f -t -q a-i
> alsa-source )
>        Just a re-installation of kernel packages and alsa-packages didn't
> work.
>     b. When redoing the Alsa Upgrade  after the restore (by my script) , I
> still see in /proc/asound the old Alsa version.
> 
>     Looks again a bit like I am having slight problems with the module
> handling
> 
> 

Hi,

I do not know the actual cause. But some drivers in ubuntu are put to
/lib/modules/kernel_version/ubuntu, the backports package used to put
there alsa drivers too. Installing drivers from git required removing
them from the ubuntu directory, or somehow forcing depmod -a to skip the
directory. I do not remember the details, but you might have a look at that.

Regards,

Pavel.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-02-01  8:07 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-30 11:42 Some installation questions Klaus Schulz
2010-02-01  8:07 ` Pavel Hofman

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.