[Techtalk] debian etch, modem and kppp
mikecar52 at gmail.com
Sun Feb 18 13:16:27 UTC 2007
debian2:/etc/modprobe.d# grep -R slamr *
sl-modem-daemon.modutils:alias char-major-242 slamr
sl-modem-daemon.modutils:install slamr modprobe --ignore-install
ungrab-winmodem ; modprobe --ignore-install slamr; test -e
/dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 2>/dev/null &&
chgrp dialout /dev/slamr0)
ebian2:/etc/modprobe.d# apt-cache policy sl-modem-source
*** 2.9.9d+e-pre2-7 0
500 http://ftp.debian.org testing/non-free Packages
500 http://http.us.debian.org testing/non-free Packages
BTW modem-daemon doesn't seem to work from my limited knowledge. The
output you requested doesn't look right but I wouldn't know.
On 17/02/07, Wim De Smet <kromagg at gmail.com> wrote:
> On 2/16/07, Mike Carter <mikecar52 at gmail.com> wrote:
> > No errors,
> > inserted ok
> So, did the modem-daemon work then? If it does, consider filing a bug
> against sl-modem-source saying that modprobe doesn't work. (you can
> use 'reportbug' for filing bugs)
> Basically it seems to me modutils hasn't been configured correctly.
> Somewhere in /etc/modprobe.d/ there should be a line in one of the
> files that says something like:
> alias char-major-so-and-so slamr
> Well I think there should, but I'm not sure. Can someone else chime in
> on this one?
> Before you file a bug report, try going to /etc/modprobe.d/ and run
> the following command:
> grep -R slamr *
> This will look through all the files for the name 'slamr'. I noticed
> bug #264359 which caused the device major value to change in a
> newer release. It could be that the old configuration has been left
> behind in some way, which would explain why the kernel can't manage to
> load it. There's a ton of other stuff that could be going wrong
> though, I'm just guessing here. Be sure to post all output of commands
> etc. on here so we get a better idea of what's going on. Could you
> state specifically what version of sl-modem-source you compiled?
> (apt-cache policy sl-modem-source will tell you which one is
> > On 16/02/07, Mike Carter <mikecar52 at gmail.com> wrote:
> > > No errors,
> > > inserted ok
> > >
> > > On 16/02/07, Wim De Smet <kromagg at gmail.com> wrote:
> > > > On 2/15/07, Mike Carter <mikecar52 at gmail.com> wrote:
> > > > > Sorry, yes it was.
> > > > >
> > > > > On 16/02/07, Wim De Smet <kromagg at gmail.com> wrote:
> > > > > > On 2/15/07, Mike Carter <mikecar52 at gmail.com> wrote:
> > > > > > > Thanks Wim,
> > > > > > > I got : debian2:/# modprobe slmr
> > > > > > > FATAL: Module slmr not found.
> > > > > >
> > > > > > --> shouldn't this be "slamr"?
> > > > > >
> > > > > > > I read my dmesg log and there is no reference to a modem.
> > > > > > > However kde kinfocenter agrees it is here. BTW works fine on windows.
> > > > > >
> > > >
> > > > Hmm I'm not used to using kinfocenter. Try the following as root:
> > > > uname -r
> > > > -will give you the version of your current running kernel
> > > > -check if the module is indeed in /lib/modules/<version>/ (and not
> > > > installed for some other kernel version)
> > > > - then try to load it with insmod instead of modprobe
> > > > insmod /lib/modules/<version/.../slamr.ko
> > > > and note what kind of output this gives in errors etc.
> > > >
> > > > greets,
> > > > Wim
> Techtalk mailing list
> Techtalk at linuxchix.org
More information about the Techtalk