On 05/07/2014 11:19 AM, Slavko wrote:
Ahoj,
Dňa Tue, 06 May 2014 17:46:29 -0500 Kent West napísal:
I'm running Debian jessie/sid (3.14-1-686-pae #1 SMP Debian 3.14.2-1
(2014-04-28) i686 GNU/Linux) on a MacBook (older white model).
It has the Broadcom BCM4321 wireless chipset (arg! non-free!)
Ahoj,
Dňa Tue, 06 May 2014 17:46:29 -0500 Kent West napísal:
> I'm running Debian jessie/sid (3.14-1-686-pae #1 SMP Debian 3.14.2-1
> (2014-04-28) i686 GNU/Linux) on a MacBook (older white model).
>
> It has the Broadcom BCM4321 wireless chipset (arg! non-free!).
>
> When I boot, the b43 modu
On Tue, 06 May 2014 17:46:29 -0500
Kent West wrote:
>
> How can I get the module to load at startup instead of me having to
> manually modprobe it every time?
>
> Thanks!
>
Try this:
- On a freshly booted system, run
modprobe -v b43
- Add the printed modules in /etc/modules the same orde
I'm running Debian jessie/sid (3.14-1-686-pae #1 SMP Debian 3.14.2-1
(2014-04-28) i686 GNU/Linux) on a MacBook (older white model).
It has the Broadcom BCM4321 wireless chipset (arg! non-free!).
When I boot, the b43 module is not auto-loading; I can drop into a
terminal and "sudo modprobe b43)
Hi
I have been follow unstable and it seems recently in the upgrade of
(udev ? hal ? acpi ? kernel ? ) that my modules don't seem to be
loading automagically ie snd_intel_hda and psmouse (this is rather a
pain).
any one else having these problems
the psmouse doesn't load even though its a t
This was the problem. Once I added myslef to the audio
group I was able to play music no problems. As someone
else from the list suggested I'll file a bug report
against alsaconf. Thanks.
Richard
--- Caleb Shay <[EMAIL PROTECTED]> wrote:
> Let me guess. You used alsaconf to configure alsa,
> rig
* Richard Weil ([EMAIL PROTECTED]) spake thusly:
> Yet another ALSA question ...
>
> Problems are with a maestro-2 (es1968) soundcard
> running on 2.4.18-ac3, ALSA compiled from source on an
> up-to-date Woody system.[Same problems occurred with
> other kernels, but I never fixed them.]
>
> In a
Let me guess. You used alsaconf to configure alsa, right? I ran into
the same problem. If you edit your alsa config file (in
/etc/alsa/modutils) you will see the line that contains the snd_dac_etc
stuff, just delete the whole line and things should work.
Caleb
On Tue, 2002-03-05 at 16:23, Rich
Yet another ALSA question ...
Problems are with a maestro-2 (es1968) soundcard
running on 2.4.18-ac3, ALSA compiled from source on an
up-to-date Woody system.[Same problems occurred with
other kernels, but I never fixed them.]
In a nutshell, the ALSA modules won't load
automatically. If I use "i
Chris Hessmann, 2002-Jan-29 00:22 +0100:
> Hello Jeff,
>
>
> > - From a fresh source extraction:
> > 1. make xconfig|menuconfig
> > 2. make-kpkg clean
> > 3. Adjust "Extraversion" in Makefile, e.g. -1 to make resultant
> > kernel "2.4.17-1"
> > 4. make-kpkg kernel_image
>
> oh, oh.
> Why
Hello Jeff,
> - From a fresh source extraction:
> 1. make xconfig|menuconfig
> 2. make-kpkg clean
> 3. Adjust "Extraversion" in Makefile, e.g. -1 to make resultant
> kernel "2.4.17-1"
> 4. make-kpkg kernel_image
oh, oh.
Why do I have to compile and install a kernel for debian in such a
s
On 27 Jan 2002, James Lindenschmidt wrote:
> This is my first time doing a kernel upgrade The Debian
> Way(tm).
>
> I am running sid on a Celeron system and am trying to
> upgrade from a 2.2.18 kernel to a 2.4.17.
>
> I downloaded the 2.4.17 tarball from kernel.org, and did
> the following:
>
>
--begin quoted message from Jeff,
> James Lindenschmidt, 2002-Jan-26 20:02 -0500:
>
> > Did I miss something? Is there an equivalent to make
> > modules and make modules_install that I'm missing? I
> > expected the make-kpkg to automate the modules.
>
> If you have modules in /usr/src/modules t
Jeff, 2002-Jan-27 05:01 -0800:
> James Lindenschmidt, 2002-Jan-26 20:02 -0500:
> > make clean
> > make xconfig
> > make-kpkg kernel_image
> > cd ..
> > dpkg -i linux-2.4.17(plus extensions).deb
>
> The process should be:
>
> - From a fresh source extraction:
> 1. make xconfig|menuconfig
> 2. ma
James Lindenschmidt, 2002-Jan-26 20:02 -0500:
> make clean
> make xconfig
> make-kpkg kernel_image
> cd ..
> dpkg -i linux-2.4.17(plus extensions).deb
The process should be:
- From a fresh source extraction:
1. make xconfig|menuconfig
2. make-kpkg clean
3. Adjust "Extraversion" in Makefile, e.
This is my first time doing a kernel upgrade The Debian
Way(tm).
I am running sid on a Celeron system and am trying to
upgrade from a 2.2.18 kernel to a 2.4.17.
I downloaded the 2.4.17 tarball from kernel.org, and did
the following:
make clean
make xconfig
make-kpkg kernel_image
cd ..
dpkg -i
when i boot up i get the message
modprobe: Note the file etc/modules.conf is more recent than the file
/lib/modules/2.4.9/modules.dep
and all the modules are not loading, this is a problem since my ethernet driver
is a module, i've tried to recompile the ethernet driver to be included in the
ke
On Fri, Jan 12, 2001 at 12:55:41AM -0600, Benjamin Pharr wrote:
> At 11:28 PM 1/11/01 , Kenward Vaughan wrote:
...
> >Have you just upgraded to the 2.4.0 kernel? If so, you need to make sure
> >you have the latest modutils package as well, as the older version doesn't
> >recognize the 2.4.0 module
» Benjamin Pharr said this and I say that:
> At 11:28 PM 1/11/01 , Kenward Vaughan wrote:
> >Have you just upgraded to the 2.4.0 kernel? If so, you need to make sure
> >you have the latest modutils package as well, as the older version doesn't
> >recognize the 2.4.0 modules directory structure.
At 11:28 PM 1/11/01 , Kenward Vaughan wrote:
On Thu, Jan 11, 2001 at 11:01:13PM -0600, Benjamin Pharr wrote:
> I have several modules in the /etc/modules file that are supposed to be
> loaded upon boot. I receive an error message for each one saying that
> can't be loaded. I know they were buil
On Thu, Jan 11, 2001 at 11:01:13PM -0600, Benjamin Pharr wrote:
> I have several modules in the /etc/modules file that are supposed to be
> loaded upon boot. I receive an error message for each one saying that
> can't be loaded. I know they were built and installed. I have checked and
> they
I have several modules in the /etc/modules file that are supposed to be
loaded upon boot. I receive an error message for each one saying that
can't be loaded. I know they were built and installed. I have checked and
they are in the right place. I have tried to load them manually with
insmod
-BEGIN PGP SIGNED MESSAGE-
On Mon, 18 Oct 1999, Marshal Wong wrote:
> I'm using the latest potato right now. The ALSA source compiled fine.
> I used make-kpkg to install the modules. But for some reason the
> module won't start. Every time I run /etc/init.d/alsa start, I get
> the foll
Marshal,
There is a Seg fault problem with the ALSA drivers.
I have a Creative Ensoniq PCI64 (ens1371) soundcard and the ALSA
drivers do the same thing to me. This is on a S.u.S.E. system with
kernel 2.2.5.
What I do is to put the modprobe command in a script in my /root/bin
directory and run i
I'm using the latest potato right now. The ALSA source compiled fine.
I used make-kpkg to install the modules. But for some reason the
module won't start. Every time I run /etc/init.d/alsa start, I get
the following.
Starting sound driver: snd-card-interwave /etc/init.d/alsa: line 10: 7070
Se
25 matches
Mail list logo
