All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Klaus Schulz <kls.schlz@googlemail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Some installation questions
Date: Mon, 01 Feb 2010 09:07:09 +0100	[thread overview]
Message-ID: <4B668BAD.7020103@ivitera.com> (raw)
In-Reply-To: <d9690f191001300342ve4095cfl82e01a5b5118e1e8@mail.gmail.com>

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.

      reply	other threads:[~2010-02-01  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30 11:42 Some installation questions Klaus Schulz
2010-02-01  8:07 ` Pavel Hofman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B668BAD.7020103@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=kls.schlz@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.