• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

gelöst Huawei E173, suse 13.1, KDE

K

KKN

Hallo zusammen, ich bring den Stick nicht zum Laufen.

User ist in dialout und uucp
yyyyyy:/ # lsusb
Code: 
Bus 001 Device 003: ID 12d1:1436 Huawei Technologies Co., Ltd. E173 3G Modem (modem-mode)
Bus 002 Device 002: ID 064e:d214 Suyin Corp. 
Bus 003 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Code: 
lapzozo:/home/klaus # service NetworkManager status
NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Mon 2014-03-03 00:14:02 CET; 6s ago
 Main PID: 1776 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           |-1776 /usr/sbin/NetworkManager --no-daemon
           `-1783 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-client.action -pf /var/run/dhclient-enp6s0.pid -lf /var/lib/NetworkManager/dhclient-79bca8aa-aa98...

Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info>   nameserver '192.168.2.1'
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info>   domain name 'Speedport_W_700V'
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Commit) started...
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> (enp6s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Commit) complete.
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> (enp6s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> NetworkManager state is now CONNECTED_GLOBAL
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> Policy set 'Kabelnetzwerkverbindung 1' (enp6s0) as default for IPv4 routing and DNS.
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> Activation (enp6s0) successful, device activated.
lapzozo:/home/klaus # service NetworkManager start

l
Code: 
apzozo:/home/klaus # service NetworkManager status
NetworkManager.service - Network Manager                                                                                                                     
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)                                                                                  
   Active: failed (Result: signal) since Mon 2014-03-03 00:16:28 CET; 1min 40s ago                                                                           
  Process: 1776 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=killed, signal=ABRT)                                                                    
 Main PID: 1776 (code=killed, signal=ABRT)                                                                                                                   
                                                                                                                                                             
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> Policy set 'Kabelnetzwerkverbindung 1' (enp6s0) as default for IPv4 routing and DNS.               
Mar 03 00:14:03 lapzozo.site NetworkManager[1776]: <info> Activation (enp6s0) successful, device activated.                                                  
Mar 03 00:14:23 lapzozo.site NetworkManager[1776]: <info> (enp6s0): IP6 addrconf timed out or failed.                                                        
Mar 03 00:14:23 lapzozo.site NetworkManager[1776]: <info> Activation (enp6s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...                             
Mar 03 00:14:23 lapzozo.site NetworkManager[1776]: <info> Activation (enp6s0) Stage 4 of 5 (IPv6 Configure Timeout) started...                               
Mar 03 00:14:23 lapzozo.site NetworkManager[1776]: <info> Activation (enp6s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.                                
Mar 03 00:16:28 lapzozo.site NetworkManager[1776]: <warn> (ttyUSB2) cannot enable modem: locked                                                              
Mar 03 00:16:28 lapzozo.site NetworkManager[1776]: <info> (ttyUSB2): device state change: disconnected -> need-auth (reason 'none') [30 60 0]                
Mar 03 00:16:28 lapzozo.site systemd[1]: NetworkManager.service: main process exited, code=killed, status=6/ABRT                                             
Mar 03 00:16:28 lapzozo.site systemd[1]: Unit NetworkManager.service entered failed state.                                                                   
lapzozo:/home/klaus # service NetworkManager start
lapzozo:/home/klaus # service NetworkManager status
NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
   Active: active (running) since Mon 2014-03-03 00:18:40 CET; 5s ago
 Main PID: 2025 (NetworkManager)
   CGroup: /system.slice/NetworkManager.service
           |-2025 /usr/sbin/NetworkManager --no-daemon
           `-2032 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-client.action -pf /var/run/dhclient-enp6s0.pid -lf /var/lib/NetworkManager/dhclient-79bca8aa-aa98...

Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info>   nameserver '192.168.2.1'
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info>   domain name 'Speedport_W_700V'
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Commit) started...
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info> (enp6s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Commit) complete.
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info> (enp6s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info> NetworkManager state is now CONNECTED_GLOBAL
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info> Policy set 'Kabelnetzwerkverbindung 1' (enp6s0) as default for IPv4 routing and DNS.
Mar 03 00:18:41 lapzozo.site NetworkManager[2025]: <info> Activation (enp6s0) successful, device activated.
lapzozo:/home/klaus #

/var/log/Networkmanager
Code: 
<info> ModemManager available in the bus
2014-03-03T00:18:41.430109+01:00 lapzozo NetworkManager[2025]: <warn> (ttyUSB2): failed to look up interface index
2014-03-03T00:18:41.448903+01:00 lapzozo NetworkManager[2025]: <info> (ttyUSB2): new Broadband device (driver: 'option1, cdc_ether' ifindex: 0)
2014-03-03T00:18:41.450422+01:00 lapzozo NetworkManager[2025]: <info> (ttyUSB2): exported as /org/freedesktop/NetworkManager/Devices/2
2014-03-03T00:18:41.451604+01:00 lapzozo NetworkManager[2025]: <info> (ttyUSB2): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
2014-03-03T00:18:41.458035+01:00 lapzozo NetworkManager[2025]: <info> (ttyUSB2): deactivating device (reason 'managed') [2]
2014-03-03T00:18:41.467888+01:00 lapzozo NetworkManager[2025]: <info> (ttyUSB2): device state change: unavailable -> disconnected (reason 'none') [20 30 0]
2014-03-03T00:18:41.478489+01:00 lapzozo NetworkManager[2025]: <info> (enp6s0): DHCPv4 state changed preinit -> reboot
2014-03-03T00:18:41.479763+01:00 lapzozo NetworkManager[2025]: <info>   address 192.168.2.104
2014-03-03T00:18:41.480714+01:00 lapzozo NetworkManager[2025]: <info>   prefix 24 (255.255.255.0)
2014-03-03T00:18:41.481639+01:00 lapzozo NetworkManager[2025]: <info>   gateway 192.168.2.1
2014-03-03T00:18:41.484013+01:00 lapzozo NetworkManager[2025]: <info>   nameserver '192.168.2.1'
2014-03-03T00:18:41.485928+01:00 lapzozo NetworkManager[2025]: <info>   domain name 'Speedport_W_700V'
2014-03-03T00:18:41.488652+01:00 lapzozo NetworkManager[2025]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
2014-03-03T00:18:41.489814+01:00 lapzozo NetworkManager[2025]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Commit) started...
2014-03-03T00:18:41.491386+01:00 lapzozo NetworkManager[2025]: <info> (enp6s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
2014-03-03T00:18:41.492754+01:00 lapzozo NetworkManager[2025]: <info> Activation (enp6s0) Stage 5 of 5 (IPv4 Commit) complete.
2014-03-03T00:18:41.494058+01:00 lapzozo NetworkManager[2025]: <info> (enp6s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
2014-03-03T00:18:41.565751+01:00 lapzozo NetworkManager[2025]: <info> NetworkManager state is now CONNECTED_GLOBAL
2014-03-03T00:18:41.567389+01:00 lapzozo NetworkManager[2025]: <info> Policy set 'Kabelnetzwerkverbindung 1' (enp6s0) as default for IPv4 routing and DNS.
2014-03-03T00:18:41.575550+01:00 lapzozo NetworkManager[2025]: <info> Activation (enp6s0) successful, device activated.
2014-03-03T00:19:01.415068+01:00 lapzozo NetworkManager[2025]: <info> (enp6s0): IP6 addrconf timed out or failed.
2014-03-03T00:19:01.416789+01:00 lapzozo NetworkManager[2025]: <info> Activation (enp6s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
2014-03-03T00:19:01.418110+01:00 lapzozo NetworkManager[2025]: <info> Activation (enp6s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
2014-03-03T00:19:01.420113+01:00 lapzozo NetworkManager[2025]: <info> Activation (enp6s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.

Einstellungen zum Stick
Automatisch verbinden
IPv4 Automatisch grundeinstellung
IPV6 automatisch
*99#
Benutzername fonic
Passwort leer
pinternet.interkom.de
Pin 1234 Speichern

wenn ich im bedienteil Mobile Breitbandverbindungen anklicke, ersscheint nebe dem Handi-Symbol : Autorisierung wird erwartet.
ich sag schon mal Dank für die Hiilfe
 
Heinz-Peter

Heinz-Peter

Ich weiß nicht ob dir das hilft aber hier in Forum hab ich das gefunden => http://forum.linux-club.de/viewtopic.php?p=723030#p723030

Grüße Heinz-Peter
 
OP
K

KKN

Auf der Sim- Karte war die Pin-Sperre aktiv. Die habe ich im Händi ausgeschaltet. Danach gings flugs voran. Der NM sackte nicht mehr zusammen.
 
Du musst dich einloggen oder registrieren, um hier zu antworten.
Oben