Adam Hardy wrote:
> I don't understand how that is connected with udev though. Presumably
> running alsaconf set up the udev rule that tells udev to make a device
> for alsa?
>From the manpage:
Alsaconf will write a module-init-tools (or modutils) snippet which can be
then used by module-init-t
John O'Hagan on 16/04/06 14:55, wrote:
On Sun, 16 Apr 2006 06:24 pm, Adam Hardy wrote:
Hmm. I have installed all the appropriate alsa packages I could find in
synaptic, but I don't have the command alsaconfig on my system.
Where does it come from?
The command you're after is alsaconf.
Gre
On Sun, 16 Apr 2006 06:24 pm, Adam Hardy wrote:
>
> Hmm. I have installed all the appropriate alsa packages I could find in
> synaptic, but I don't have the command alsaconfig on my system.
>
> Where does it come from?
>
The command you're after is alsaconf.
HTH,
John
--
To UNSUBSCRIBE, emai
On Sun, 16 Apr 2006 09:24:48 +0100
Adam Hardy <[EMAIL PROTECTED]> wrote:
> Felipe Sateler on 15/04/06 22:30, wrote:
> > Adam Hardy wrote:
> >> I have been researching the issues. It looks like the appropriate
> >> drivers have not been created - for instance, the following paths are
> >> empty or
Felipe Sateler on 15/04/06 22:30, wrote:
Adam Hardy wrote:
I have been researching the issues. It looks like the appropriate
drivers have not been created - for instance, the following paths are
empty or non-existent:
/sys/bus/i2c/devices
/proc/sys/dev/sensors
/proc/acpi/thermal
Seems like you
Adam Hardy wrote:
> I have been researching the issues. It looks like the appropriate
> drivers have not been created - for instance, the following paths are
> empty or non-existent:
>
> /sys/bus/i2c/devices
> /proc/sys/dev/sensors
> /proc/acpi/thermal
Seems like you are not loading the modules yo
6 matches
Mail list logo
