SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I wonder whether you are experiencing the same problem that I have with my Huawei E160E USB modem. http://www.linuxquestions.org/questi...es-4175481152/
I found that I needed to revert an earlier version of dhcpcd to be able to connect.
Hi all,
I have follow the steps and encounter some errors.
i have installed the usb_modeswitch
The information below is what i have entered at the bottom if the usb_modeswitch.conf
Code:
# Configuration for the usb_modeswitch package, a mode switching tool for
# USB devices providing multiple states or modes
#
# Evaluated by the wrapper script /usr/sbin/usb_modeswitch_dispatcher
#
# To enable an option, set it to "1", "yes" or "true" (case doesn't matter)
# Everything else counts as "disable"
# Disable automatic mode switching globally (e.g. to access the original
# install storage)
DisableSwitching=0
# Enable logging (results in a extensive report file in /var/log, named
# "usb_modeswitch_<interface-name>" and probably others
EnableLogging=0
# Optional increase of "delay_use" for the usb-storage driver; there are hints
# that a recent kernel default change to 1 sec. may lead to problems, particu-
# larly with USB 3.0 ports. Set this to at least 3 (seconds) in that case.
# Does nothing if the current system value is same or higher
# SetStorageDelay=3
DefaultVendor=0x12d1
DefaultProduct=0x1506
TargetVendor=0x12d1
TargetProduct=0x1c05
CheckSuccess=20
MessageContent="55534243123456780000000000000011060000000000000000000000000000"
I run this command, usb_modeswitch -c /etc/usb_modeswitch.conf, i got the following error:
Code:
bash-4.2# usb_modeswitch -c /etc/usb_modeswitch.conf
Look for target devices ...
No devices in target mode or class found
Look for default devices ...
product ID matched
Found devices in default mode (1)
Access device 010 on bus 001
Get the current device configuration ...
OK, got current device configuration (1)
Use interface number 0
Error: can't use storage command in MessageContent with interface 0;
interface class is 255, expected 8. Abort
I would get the latest version of the code from a link given here http://www.freedesktop.org/wiki/Software/ModemManager/ using git, and then build a package using the modemmanager SlackBuild from the Slackware source.
bash-4.2# lsusb
Bus 001 Device 007: ID 12d1:1506 Huawei Technologies Co., Ltd. Modem/Networkcard
Bus 003 Device 002: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse
Bus 005 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
su -c '/usr/sbin/ModemManager --debug; /usr/sbin/NetworkManager --no-daemon --log-level=DEBUG &'
This suggests the problem that was supposed to be addressed by the patch linked in post#5. The modem has been queried with AT^SYSINFOEX and returned the unquoted string ^SYSINFOEX:2,3,0,1,,3,WCDMA,41,WCDMA
just download the version ModemManager-1.1.990.tar.xz
however requires this libqmi-glib library to continue. I am not able to find it in the slackbuild for 14.1. Any clues where to get 1?
Thanks
Code:
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for MM... yes
checking for LIBMM_GLIB... yes
checking for MMCLI... yes
checking for GUDEV... yes
checking for gobject-introspection... yes
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for vapigen... no
checking for POLKIT... yes
checking for MBIM... yes
checking for QMI... no
configure: error: Couldn't find libqmi-glib. Install it, or otherwise configure using --without-qmi to disable QMI support.
just download the version ModemManager-1.1.990.tar.xz
however requires this libqmi-glib library to continue. I am not able to find it in the slackbuild for 14.1. Any clues where to get 1?
It should be in the install CD. Grab it from packages.slackware.com . Search for "libqmi"
that has already been installed.
The installation of the modem manager still reports the same error that's why i tried to search in the slackbuild
Not sure if libqmi-1.4.0-i486-1.txz is the appropriate library for libqmi-glib
Grep the disc for libqmi
Code:
bash-4.2# pwd
/media/SlackDVD/slackware/n
bash-4.2# cd ..
bash-4.2# grep libqmi *
CHECKSUMS.md5:dea91e1bc04c33743b28a1a231d83dc0 ./n/libqmi-1.4.0-i486-1.txt
CHECKSUMS.md5:e79d0d2156d63529912fe1617b57453b ./n/libqmi-1.4.0-i486-1.txz
CHECKSUMS.md5:f317891f72d7897856bb5d1026eca34a ./n/libqmi-1.4.0-i486-1.txz.asc
FILE_LIST:-rw-r--r-- 1 root root 298 2013-10-08 07:07 ./n/libqmi-1.4.0-i486-1.txt
FILE_LIST:-rw-r--r-- 1 root root 309200 2013-10-08 07:07 ./n/libqmi-1.4.0-i486-1.txz
FILE_LIST:-rw-r--r-- 1 root root 198 2013-10-08 07:07 ./n/libqmi-1.4.0-i486-1.txz.asc
PACKAGES.TXT:PACKAGE NAME: libqmi-1.4.0-i486-1.txz
PACKAGES.TXT:libqmi: libqmi (QMI library and utils)
PACKAGES.TXT:libqmi:
PACKAGES.TXT:libqmi: libqmi is a glib-based library for talking to WWAN modems and devices
PACKAGES.TXT:libqmi: which speak the Qualcomm MSM Interface (QMI) protocol.
PACKAGES.TXT:libqmi:
PACKAGES.TXT:libqmi: Homepage: http://www.freedesktop.org/software/libqmi/
PACKAGES.TXT:libqmi:
grep: a: Is a directory
grep: ap: Is a directory
grep: d: Is a directory
grep: e: Is a directory
grep: f: Is a directory
grep: k: Is a directory
grep: kde: Is a directory
grep: kdei: Is a directory
grep: l: Is a directory
grep: n: Is a directory
grep: t: Is a directory
grep: tcl: Is a directory
grep: x: Is a directory
grep: xap: Is a directory
grep: xfce: Is a directory
grep: y: Is a directory
bash-4.2# ^C
bash-4.2#
Installed successful
Code:
bash-4.2# installpkg libqmi-1.4.0-i486-1.txz
Verifying package libqmi-1.4.0-i486-1.txz.
Installing package libqmi-1.4.0-i486-1.txz [REC]:
PACKAGE DESCRIPTION:
# libqmi (QMI library and utils)
#
# libqmi is a glib-based library for talking to WWAN modems and devices
# which speak the Qualcomm MSM Interface (QMI) protocol.
#
# Homepage: http://www.freedesktop.org/software/libqmi/
#
Executing install script for libqmi-1.4.0-i486-1.txz.
Package libqmi-1.4.0-i486-1.txz installed
Still the same error after the libqmi library install
Code:
checking for gobject-introspection... yes
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for vapigen... no
checking for POLKIT... yes
checking for MBIM... yes
checking for QMI... no
configure: error: Couldn't find libqmi-glib. Install it, or otherwise configure using --without-qmi to disable QMI support.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
