I have an AT&T Beam dongle, i.e Netgear AC340U. I can get a connection using it with Windows 7, but not Linux.
My Linux OS is Jessie +KDE, with current updates
When I plug the dongle into the Linux laptop, lsusb says that the device is present.
I have tried adding the net via KDE network manager. (I would post the screenshot, except I don't think that this forum permits that)
??
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
AT&T Beam broadband
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: AT&T Beam broadband
Attachments, How to post a screen shot and use code boxes
You can use the Image boxes, and upload the image to
a storage site, or your own site, and link to it,...see above link for details.
===========
you can just copy / paste the output into the "code boxes",... If you need to
you can put the output into a text file,
This will produce a text file named "lsusb-output.txt", the file will be in the same
directory you run the command in, and the same can be
applied to any output from the terminal.
You do need to "configure" network manager" a little bit, and enter some
information about the device , Did you do that ?
These may be of help to you:
https://wiki.debian.org/NetworkManager
https://wiki.debian.org/WiFi/HowToUse
There are more results using keywords:
And a search, but the first 2 I found , are specific for Debian,..and I did
not have time to look at the others.
You can use the
Code: Select all
[img][/img]
a storage site, or your own site, and link to it,...see above link for details.
===========
But also you do not need a "screen shot" to post the output of 'lsusb',lsusb says that the device is present.
I have tried adding the net via KDE network manager. (I would post the screenshot, except I don't think that this forum permits that)
you can just copy / paste the output into the "code boxes",... If you need to
you can put the output into a text file,
Code: Select all
lsusb > lsusb-output.txt
directory you run the command in, and the same can be
applied to any output from the terminal.
You do need to "configure" network manager" a little bit, and enter some
information about the device , Did you do that ?
These may be of help to you:
https://wiki.debian.org/NetworkManager
https://wiki.debian.org/WiFi/HowToUse
There are more results using keywords:
Code: Select all
How to configure network manager on Debian with KDE
not have time to look at the others.
Last edited by GarryRicketson on 2016-07-27 03:57, edited 3 times in total.
"What we expect you have already Done"
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
-
- Posts: 87
- Joined: 2010-08-23 16:05
Re: AT&T Beam broadband
I said that "lsusb" indicated that the device was present. I didn't realize that you needed the specifics:
william@harold:~$ lsusb
Bus 003 Device 004: ID 056a:00ec Wacom Co., Ltd
Bus 003 Device 003: ID 0483:91d1 STMicroelectronics
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:029d Acer, Inc
Bus 001 Device 033: ID 04f3:0254 Elan Microelectronics Corp.
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 032: ID 1199:9051 Sierra Wireless, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The Sierra wireless is the item in question.
You asked if I had "configured" the network manager. My configuration is the screen shot that I wanted to include. Here is a written description:
"Edit Connection 'AT&T'"
Mobile Broadband (gsm) page
Number: *99#
Username (blank)
Password (blank)
______Advanced
APN Broadband
Type Any
(check) Allow roaming
PIN (blank)
This is in accordance with a WIKI page that I found.
william@harold:~$ lsusb
Bus 003 Device 004: ID 056a:00ec Wacom Co., Ltd
Bus 003 Device 003: ID 0483:91d1 STMicroelectronics
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 5986:029d Acer, Inc
Bus 001 Device 033: ID 04f3:0254 Elan Microelectronics Corp.
Bus 001 Device 002: ID 8087:07dc Intel Corp.
Bus 001 Device 032: ID 1199:9051 Sierra Wireless, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The Sierra wireless is the item in question.
You asked if I had "configured" the network manager. My configuration is the screen shot that I wanted to include. Here is a written description:
"Edit Connection 'AT&T'"
Mobile Broadband (gsm) page
Number: *99#
Username (blank)
Password (blank)
______Advanced
APN Broadband
Type Any
(check) Allow roaming
PIN (blank)
This is in accordance with a WIKI page that I found.
- stevepusser
- Posts: 12930
- Joined: 2009-10-06 05:53
- Has thanked: 41 times
- Been thanked: 72 times
Re: AT&T Beam broadband
"lsusb" just means that the USB ID matches one in the USB ID database. It does not mean that a driver is installed or a network interface is present. Once you have the ID, you can do web searches for it and Linux to see if anyone else has solved the issue.
MX Linux packager and developer
- GarryRicketson
- Posts: 5644
- Joined: 2015-01-20 22:16
- Location: Durango, Mexico
Re: AT&T Beam broadband
Code: Select all
"Edit Connection 'AT&T'"
Mobile Broadband (gsm) page
Number: *99#
Username (blank)
Password (blank)
______Advanced
APN Broadband
Type Any
(check) Allow roaming
PIN (blank)
Ok, well that looks basically the same as I use for my broadband,..This is in accordance with a WIKI page that I found.
(different company) but ok,..
As Steve says, on Lsusb, It does not mean that a driver is installed or a network interface is present.
I think in some of the links I posted , there are some details on determining
what drivers or firm ware you have installed,..
Do you have "network manager" set to "connect automaticly", ?
If it is set to connect automaticly, and you have the correct driver , it should at least
try to connect, when you boot, and login.
On the searches: Key words:
Code: Select all
How to get missing firmware or drivers for Debian
-------------------------------------------------
****** https://raphaelhertzog.com/2011/03/14/m ... e-problem/******
-----------------------------------------
https://wiki.debian.org/Firmware
There are a whole bunch more results,... this is a very common problem,
just read some of the material, it usually is not to hard to get it all working,...
--------------------- edit ---------------------
In case you are wondering How to determine if network interface is present on Debian Jessie
-----------------------
https://wiki.debian.org/NetworkConfiguration
---------------------------------------
http://serverfault.com/questions/239807 ... rds-debian
-----------------------------------
http://www.cyberciti.biz/faq/howto-conf ... on-debian/
Again, there are lots more results, that might be help full, they were for me.
"What we expect you have already Done"
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
==========
Old Website
======================
For the Birds
==================
What Does a Parrot Know About PTSD?
-
- Posts: 87
- Joined: 2010-08-23 16:05
Re: AT&T Beam broadband
I found a WIKI: http://kb.netgear.com/app/answers/detai ... ar_organic
In accordance with that wiki, I get the following results:
From the output (above), it appears that the drivers are configured, and that the OS recognizes the device.
What am I missing?
In accordance with that wiki, I get the following results:
- root@harold:/home/william/projects# modinfo sierra
filename: /lib/modules/3.16.0-4-amd64/kernel/drivers/usb/serial/sierra.ko
license: GPL
description: USB Driver for Sierra Wireless USB modems
author: Kevin Lloyd, Elina Pasheva, Matthew Safar, Rory Filer
alias: usb:v0F3Dp68A3d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v0F3Dp68AAd*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p68ABd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p68AAd*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p68A3d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p6893d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6892d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p6891d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p6890d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p6880d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p685Ad*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6859d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6856d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6855d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6853d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6852d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6851d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6850d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p683Ed*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p683Dd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p683Cd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p683Bd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p683Ad*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6839d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6838d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6835d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6834d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6833d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6832d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6822d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6821d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6820d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6816d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6815d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6813d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6812d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6809d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6808d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6805d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6804d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6803d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p6802d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0029d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0028d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0027d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0026d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0025d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p0023d*dc*dsc*dp*icFFiscFFipFFin*
alias: usb:v1199p0301d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0120d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0112d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0021d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0019d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0224d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0024d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0022d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0220d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0020d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0218d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0018d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v1199p0017d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v03F0p1E1Dd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v03F0p211Dd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v03F0p1B1Dd*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0F3Dp0112d*dc*dsc*dp*ic*isc*ip*in*
depends: usbserial,usbcore
intree: Y
vermagic: 3.16.0-4-amd64 SMP mod_unload modversions
parm: nmea:NMEA streaming (bool)
root@harold:/home/william/projects# ls /dev/ttyUSB* -l
crw-rw---- 1 root dialout 188, 0 Jul 28 13:29 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Jul 28 13:29 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Jul 28 13:29 /dev/ttyUSB2
root@harold:/home/william/projects# modinfo sierra_net
filename: /lib/modules/3.16.0-4-amd64/kernel/drivers/net/usb/sierra_net.ko
license: GPL
version: v.2.0
description: USB-to-WWAN Driver for Sierra Wireless modems
author: Paxton Smith, Matthew Safar, Rory Filer
srcversion: 896313DAA9C61C842F37412
alias: usb:v0F3Dp68AAd*dc*dsc*dp*ic*isc*ip*in0B*
alias: usb:v0F3Dp68AAd*dc*dsc*dp*ic*isc*ip*in0A*
alias: usb:v0F3Dp68AAd*dc*dsc*dp*ic*isc*ip*in07*
alias: usb:v1199p68AAd*dc*dsc*dp*ic*isc*ip*in0B*
alias: usb:v1199p68AAd*dc*dsc*dp*ic*isc*ip*in0A*
alias: usb:v1199p68AAd*dc*dsc*dp*ic*isc*ip*in07*
alias: usb:v0F3Dp68A3d*dc*dsc*dp*ic*isc*ip*in0B*
alias: usb:v0F3Dp68A3d*dc*dsc*dp*ic*isc*ip*in0A*
alias: usb:v0F3Dp68A3d*dc*dsc*dp*ic*isc*ip*in07*
alias: usb:v1199p68A3d*dc*dsc*dp*ic*isc*ip*in0B*
alias: usb:v1199p68A3d*dc*dsc*dp*ic*isc*ip*in0A*
alias: usb:v1199p68A3d*dc*dsc*dp*ic*isc*ip*in07*
depends: usbnet,usbcore
intree: Y
vermagic: 3.16.0-4-amd64 SMP mod_unload modversions
root@harold:/home/william/projects# ls /dev/ttyUSB* -l
crw-rw---- 1 root dialout 188, 0 Jul 28 13:29 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Jul 28 13:29 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Jul 28 13:29 /dev/ttyUSB2
root@harold:/home/william/projects# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:367 errors:0 dropped:0 overruns:0 frame:0
TX packets:367 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:57700 (56.3 KiB) TX bytes:57700 (56.3 KiB)
wlan0 Link encap:Ethernet HWaddr 48:51:b7:d2:a3:43
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:33688 errors:0 dropped:0 overruns:0 frame:0
TX packets:26242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:19447613 (18.5 MiB) TX bytes:6862650 (6.5 MiB)
From the output (above), it appears that the drivers are configured, and that the OS recognizes the device.
What am I missing?