USB WIFI dongle
-
- Indlæg: 2667
- Tilmeldt: 21. nov 2006, 10:06
- Geografisk sted: Fredericia
USB WIFI dongle
Jeg har valgt at købe en USB WIFI dongle til min DELL M4800 fordi WIFI ikke virker - uagtet at den er certificeret til UBUNTU???
Men hvorom alt er mit valg faldt på en Sandberg dongle : http://www.computercity.dk/product/6230414/sandberg-micro-wifi-usb-adapter?ref=section.
Jeg testede den i butikken og den gik fint på nettet. Og den kører fint... i nogle minutter så slår den fra , hvorefter den skal hives ud og sættes i igen.
Jeg kører Ubuntu 14.04
lsusb giver følgende
lshw -C network giver:
Jeg har ikke den store viden om dette område og jeg har ikke kunnet google mig til en løsning - er der nogen der ved hvad det kunne være?
Men hvorom alt er mit valg faldt på en Sandberg dongle : http://www.computercity.dk/product/6230414/sandberg-micro-wifi-usb-adapter?ref=section.
Jeg testede den i butikken og den gik fint på nettet. Og den kører fint... i nogle minutter så slår den fra , hvorefter den skal hives ud og sættes i igen.
Jeg kører Ubuntu 14.04
lsusb giver følgende
Kode: Vælg alt
tj@tj-Precision-M4800:~$ lsusb
Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 003: ID 413c:8143 Dell Computer Corp.
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0c45:64d0 Microdia
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 012: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lshw -C network giver:
Kode: Vælg alt
tj@tj-Precision-M4800:~$ sudo lshw -C network
[sudo] password for tj:
*-network
description: Ethernet interface
product: Ethernet Connection I217-LM
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 04
serial: f0:1f:af:62:36:cf
width: 32 bits
clock: 33MHz
capabilities: pm msi cap_list ethernet physical
configuration: broadcast=yes driver=e1000e latency=0 multicast=yes
resources: irq:20 memory:f7a00000-f7a1ffff memory:f7a3d000-f7a3dfff ioport:f080(size=32)
*-network UNCLAIMED
description: Network controller
product: BCM4352 802.11ac Wireless Network Adapter
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
version: 03
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: latency=0
resources: memory:f5a00000-f5a07fff memory:f5800000-f59fffff
*-network
description: Wireless interface
physical id: 3
bus info: usb@3:1
logical name: wlan2
serial: 80:1f:02:c5:e4:ea
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=rtl8192cu driverversion=3.13.0-24-generic firmware=N/A ip=192.168.0.21 link=yes multicast=yes wireless=IEEE 802.11bgn
Jeg har ikke den store viden om dette område og jeg har ikke kunnet google mig til en løsning - er der nogen der ved hvad det kunne være?
Forfatter til Ubuntuguiden: http://www.vidas.dk/guides/ubuntuguiden.html
Kører LTS udgaverne.
"It's always easy if you know how to do it."
Kører LTS udgaverne.
"It's always easy if you know how to do it."
-
- Indlæg: 5095
- Tilmeldt: 27. apr 2008, 02:16
- IRC nickname: lars_t_h
- Geografisk sted: Fyn
Re: USB WIFI dongle
Kunne du lige poste de sidste par minutters aktivitet i kernens log ( i /var/log mappen).
Det skal ske når den usædvanlige hændelse lige har fundet sted..
Har du studeret release notes for 14.04? https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes
I den står der noget om kendte fejl.
- og når jeg nu har dig - kan du så ikke lige slette dine 2 andre identiske tråde med samme titel?
/Lars
Det skal ske når den usædvanlige hændelse lige har fundet sted..
Har du studeret release notes for 14.04? https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes
I den står der noget om kendte fejl.
- og når jeg nu har dig - kan du så ikke lige slette dine 2 andre identiske tråde med samme titel?
/Lars
Jeg er Software ingeniør (Diplomingeniør) i Informationsteknologi og indlejede systemer, hvor indlejrede systemer er computer (microcontroller) + elektronik i for eksempel et TV, en router, en vaskemaskine og den slags
-
- Indlæg: 5095
- Tilmeldt: 27. apr 2008, 02:16
- IRC nickname: lars_t_h
- Geografisk sted: Fyn
Re: USB WIFI dongle
Jeg lægger mærke til at der ved din Wireless chip står: Firmware N/A, så måske mangler du at installere en firmware pakke. Det er sådan at device driveren uploader firmware fra dit filsystem og så ind i selve hardwaren - uden firmware virker den ikke, og med forkert firmware vil microcontrolleren der styrer hardwaren nok crache meget hurtigt.
/Lars
/Lars
Jeg er Software ingeniør (Diplomingeniør) i Informationsteknologi og indlejede systemer, hvor indlejrede systemer er computer (microcontroller) + elektronik i for eksempel et TV, en router, en vaskemaskine og den slags
-
- Indlæg: 1133
- Tilmeldt: 6. nov 2009, 17:05
- Geografisk sted: Rudkøbing
Re: USB WIFI dongle
Arch på Toshiba Satellite C660-1NT og Acer Aspire One 532h
Manjaro på hjemmerullet pc.
Manjaro på hjemmerullet pc.
-
- Indlæg: 5095
- Tilmeldt: 27. apr 2008, 02:16
- IRC nickname: lars_t_h
- Geografisk sted: Fyn
Re: USB WIFI dongle
Der står at kildekoden kun er for Linux 2.6.18 til 2.6.28 og så Linux ., og min Xubuntu 14.04 LTS bruger Linux 3.13.0-24.
Det bedste er som start at finde ud af hvad device driverens navn er og se om den allerede er inkluderet som et kerne modul der bare skal loades med modprobe(8).
/Lars
Jeg er Software ingeniør (Diplomingeniør) i Informationsteknologi og indlejede systemer, hvor indlejrede systemer er computer (microcontroller) + elektronik i for eksempel et TV, en router, en vaskemaskine og den slags
-
- Indlæg: 1133
- Tilmeldt: 6. nov 2009, 17:05
- Geografisk sted: Rudkøbing
Re: USB WIFI dongle
lath skrev:Der står at kildekoden kun er for Linux 2.6.18 til 2.6.28 og så Linux ., og min Xubuntu 14.04 LTS bruger Linux 3.13.0-24.
Mystisk for release notes viser følgende
Har du sørget for at være scrollet ned til cus'en (det kan læses på en funny måde)
Arch på Toshiba Satellite C660-1NT og Acer Aspire One 532h
Manjaro på hjemmerullet pc.
Manjaro på hjemmerullet pc.
-
- Indlæg: 5095
- Tilmeldt: 27. apr 2008, 02:16
- IRC nickname: lars_t_h
- Geografisk sted: Fyn
Re: USB WIFI dongle
Åbenbart forsvandt 3.0.2 fra min tekst, men nok om det.
Vi skal lige have noget kernel log fra ham, og så skal vi vide hvilken device driver der bruges til den dims (Det er en lsmod kommando før og straks efter USB WiFi donglen er sat ind i computeren. Bagefter kan man køre en diff på de 2 output, hvorved diff finder forskellen.)
Hvis det ikke er den korrekte device driver der er i brug, så skal den med på listen over black listede device drivers.
/Lars
Vi skal lige have noget kernel log fra ham, og så skal vi vide hvilken device driver der bruges til den dims (Det er en lsmod kommando før og straks efter USB WiFi donglen er sat ind i computeren. Bagefter kan man køre en diff på de 2 output, hvorved diff finder forskellen.)
Hvis det ikke er den korrekte device driver der er i brug, så skal den med på listen over black listede device drivers.
/Lars
Jeg er Software ingeniør (Diplomingeniør) i Informationsteknologi og indlejede systemer, hvor indlejrede systemer er computer (microcontroller) + elektronik i for eksempel et TV, en router, en vaskemaskine og den slags
-
- Indlæg: 2667
- Tilmeldt: 21. nov 2006, 10:06
- Geografisk sted: Fredericia
Re: USB WIFI dongle
er det kern.log i skal kigge. Her er udskriften derfra hvor jeg 18:40:15 må trække usbkortet ud - og isætte det igen.
Så vidt jeg kan se er der ingen fejl. ?
Så vidt jeg kan se er der ingen fejl. ?
Kode: Vælg alt
Apr 27 18:38:42 tj-Precision-M4800 kernel: [ 12.857735] nouveau E[ PGRAPH][0000:01:00.0] 409000 - stat 0x00000000 0x00000000 0x00000002 0x00000009
Apr 27 18:38:42 tj-Precision-M4800 kernel: [ 12.857737] nouveau E[ PGRAPH][0000:01:00.0] 502000 - done 0x00000300
Apr 27 18:38:42 tj-Precision-M4800 kernel: [ 12.857743] nouveau E[ PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 27 18:38:42 tj-Precision-M4800 kernel: [ 12.857749] nouveau E[ PGRAPH][0000:01:00.0] 502000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 27 18:38:42 tj-Precision-M4800 kernel: [ 12.857751] nouveau E[ PGRAPH][0000:01:00.0] 50a000 - done 0x00000300
Apr 27 18:38:42 tj-Precision-M4800 kernel: [ 12.857757] nouveau E[ PGRAPH][0000:01:00.0] 50a000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 27 18:38:42 tj-Precision-M4800 kernel: [ 12.857763] nouveau E[ PGRAPH][0000:01:00.0] 50a000 - stat 0x00000000 0x00000000 0x00000000 0x00000000
Apr 27 18:38:42 tj-Precision-M4800 kernel: [ 12.857765] nouveau E[ PGRAPH][0000:01:00.0] init failed, -16
Apr 27 18:38:49 tj-Precision-M4800 kernel: [ 19.809038] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
Apr 27 18:38:49 tj-Precision-M4800 kernel: [ 19.877156] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
Apr 27 18:39:05 tj-Precision-M4800 kernel: [ 36.327620] input: Logitech Unifying Device. Wireless PID:1017 as /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.2/0003:046D:C52B.0003/input/input19
Apr 27 18:39:05 tj-Precision-M4800 kernel: [ 36.327729] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1017] on usb-0000:00:14.0-3:1
Apr 27 18:39:19 tj-Precision-M4800 kernel: [ 49.813320] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
Apr 27 18:39:19 tj-Precision-M4800 kernel: [ 50.017502] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.652723] usb 3-6: USB disconnect, device number 3
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.653720] wlan2: deauthenticating from 20:e5:2a:f6:f2:63 by local choice (reason=3)
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.653881] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffffffed value=0x1
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.653886] rtl_usb: reg 0x422, usbctrl_vendorreq TimeOut! status:0xffffffed value=0x70000
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.653890] rtl_usb: reg 0x542, usbctrl_vendorreq TimeOut! status:0xffffffed value=0xd38000
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.653894] rtl_usb: reg 0x608, usbctrl_vendorreq TimeOut! status:0xffffffed value=0x204
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.729883] cfg80211: Calling CRDA to update world regulatory domain
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.733237] cfg80211: World regulatory domain updated:
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.733241] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.733243] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.733245] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.733246] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.733248] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 27 18:40:15 tj-Precision-M4800 kernel: [ 105.733250] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.282983] usb 3-6: new high-speed USB device number 4 using xhci_hcd
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.300552] usb 3-6: New USB device found, idVendor=0bda, idProduct=8176
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.300561] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.300566] usb 3-6: Product: 802.11n WLAN Adapter
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.300570] usb 3-6: Manufacturer: Realtek
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.300574] usb 3-6: SerialNumber: 00e04c000001
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.301313] rtl8192cu: Chip version 0x10
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.332901] rtl8192cu: MAC address: 80:1f:02:c5:e4:ea
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.332907] rtl8192cu: Board Type 0
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.332978] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.333015] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.333300] ieee80211 phy1: Selected rate control algorithm 'rtl_rc'
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.333894] rtlwifi: wireless switch is on
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.379543] rtl8192cu: MAC auto ON okay!
Apr 27 18:40:16 tj-Precision-M4800 kernel: [ 107.398789] rtl8192cu: Tx queue select: 0x05
Apr 27 18:40:17 tj-Precision-M4800 kernel: [ 107.749992] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
Apr 27 18:40:17 tj-Precision-M4800 kernel: [ 107.750233] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
Apr 27 18:40:17 tj-Precision-M4800 kernel: [ 108.503917] wlan2: authenticate with 20:e5:2a:f6:f2:63
Apr 27 18:40:17 tj-Precision-M4800 kernel: [ 108.514774] wlan2: send auth to 20:e5:2a:f6:f2:63 (try 1/3)
Apr 27 18:40:17 tj-Precision-M4800 kernel: [ 108.615827] wlan2: send auth to 20:e5:2a:f6:f2:63 (try 2/3)
Apr 27 18:40:17 tj-Precision-M4800 kernel: [ 108.644713] wlan2: authenticated
Apr 27 18:40:17 tj-Precision-M4800 kernel: [ 108.647945] wlan2: associate with 20:e5:2a:f6:f2:63 (try 1/3)
Apr 27 18:40:18 tj-Precision-M4800 kernel: [ 108.702676] wlan2: RX AssocResp from 20:e5:2a:f6:f2:63 (capab=0x411 status=0 aid=4)
Apr 27 18:40:18 tj-Precision-M4800 kernel: [ 108.702733] wlan2: associated
Apr 27 18:40:18 tj-Precision-M4800 kernel: [ 108.702792] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
Forfatter til Ubuntuguiden: http://www.vidas.dk/guides/ubuntuguiden.html
Kører LTS udgaverne.
"It's always easy if you know how to do it."
Kører LTS udgaverne.
"It's always easy if you know how to do it."
-
- Indlæg: 2667
- Tilmeldt: 21. nov 2006, 10:06
- Geografisk sted: Fredericia
Re: USB WIFI dongle
@lath
hvordan bruger man den der diff kommando
hvordan bruger man den der diff kommando
Forfatter til Ubuntuguiden: http://www.vidas.dk/guides/ubuntuguiden.html
Kører LTS udgaverne.
"It's always easy if you know how to do it."
Kører LTS udgaverne.
"It's always easy if you know how to do it."
-
- Admin
- Indlæg: 3650
- Tilmeldt: 5. mar 2010, 19:58
- IRC nickname: nicky
- Geografisk sted: 192.168.20.42
Re: USB WIFI dongle
NAME
diff - compare files line by line
SYNOPSIS
diff [OPTION]... FILES
Så det er bare
Kode: Vælg alt
diff FIL1 FIL2
Hvad der så måtte være af forskelle, bliver skrevet til terminalen.
-
- Indlæg: 2667
- Tilmeldt: 21. nov 2006, 10:06
- Geografisk sted: Fredericia
Re: USB WIFI dongle
Nå der kom en "sjov" fejlmeddelelse nu.
Nedenfor dette stod der blot det samme igen igen:
Og denne tråd mener at det handler om bumblebee:
https://bbs.archlinux.org/viewtopic.php?id=170074
Kode: Vælg alt
Apr 28 17:22:11 tj-Precision-M4800 kernel: [ 1325.976292] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
Apr 28 17:22:11 tj-Precision-M4800 kernel: [ 1326.068523] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20131115/nsarguments-95)
Nedenfor dette stod der blot det samme igen igen:
Kode: Vælg alt
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1436.965541] usb 3-6: USB disconnect, device number 8
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1436.969092] wlan2: deauthenticating from 20:e5:2a:f6:f2:63 by local choice (reason=3)
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1437.061330] cfg80211: Calling CRDA to update world regulatory domain
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1437.066625] cfg80211: World regulatory domain updated:
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1437.066633] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1437.066639] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1437.066644] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1437.066649] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1437.066654] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:02 tj-Precision-M4800 kernel: [ 1437.066658] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.629599] usb 3-6: new high-speed USB device number 9 using xhci_hcd
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.647290] usb 3-6: New USB device found, idVendor=0bda, idProduct=8176
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.647293] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.647295] usb 3-6: Product: 802.11n WLAN Adapter
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.647296] usb 3-6: Manufacturer: Realtek
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.647297] usb 3-6: SerialNumber: 00e04c000001
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.647889] rtl8192cu: Chip version 0x10
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.679130] rtl8192cu: MAC address: 80:1f:02:c5:e4:ea
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.679135] rtl8192cu: Board Type 0
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.679207] rtl_usb: rx_max_size 15360, rx_urb_num 8, in_ep 1
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.679238] rtl8192cu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.679459] ieee80211 phy6: Selected rate control algorithm 'rtl_rc'
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.679897] rtlwifi: wireless switch is on
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.717415] rtl8192cu: MAC auto ON okay!
Apr 28 17:24:04 tj-Precision-M4800 kernel: [ 1439.734393] rtl8192cu: Tx queue select: 0x05
Apr 28 17:24:05 tj-Precision-M4800 kernel: [ 1440.086924] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
Apr 28 17:24:05 tj-Precision-M4800 kernel: [ 1440.087142] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.534374] wlan2: authenticate with 20:e5:2a:f6:f2:63
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.555917] wlan2: send auth to 20:e5:2a:f6:f2:63 (try 1/3)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.566875] wlan2: authenticated
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.569960] wlan2: associate with 20:e5:2a:f6:f2:63 (try 1/3)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.579509] wlan2: RX AssocResp from 20:e5:2a:f6:f2:63 (capab=0x411 status=0 aid=5)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.579582] wlan2: associated
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.579686] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.633206] wlan2: deauthenticating from 20:e5:2a:f6:f2:63 by local choice (reason=2)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.644580] wlan2: authenticate with 20:e5:2a:f6:f2:63
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.655467] wlan2: send auth to 20:e5:2a:f6:f2:63 (try 1/3)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.655605] cfg80211: Calling CRDA to update world regulatory domain
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.657756] cfg80211: World regulatory domain updated:
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.657759] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.657761] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.657762] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.657764] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.657765] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.657766] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.677682] wlan2: authenticated
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.677936] wlan2: associate with 20:e5:2a:f6:f2:63 (try 1/3)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.689314] wlan2: RX AssocResp from 20:e5:2a:f6:f2:63 (capab=0x411 status=0 aid=5)
Apr 28 17:24:06 tj-Precision-M4800 kernel: [ 1441.689337] wlan2: associated
Og denne tråd mener at det handler om bumblebee:
https://bbs.archlinux.org/viewtopic.php?id=170074
Forfatter til Ubuntuguiden: http://www.vidas.dk/guides/ubuntuguiden.html
Kører LTS udgaverne.
"It's always easy if you know how to do it."
Kører LTS udgaverne.
"It's always easy if you know how to do it."
-
- Indlæg: 2667
- Tilmeldt: 21. nov 2006, 10:06
- Geografisk sted: Fredericia
Re: USB WIFI dongle
nye meddelelser
Kode: Vælg alt
Apr 28 17:36:13 tj-Precision-M4800 kernel: [ 33.204852] type=1400 audit(1398699373.619:64): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2768 comm="apparmor_parser"
Apr 28 17:36:13 tj-Precision-M4800 kernel: [ 33.204855] type=1400 audit(1398699373.619:65): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2768 comm="apparmor_parser"
Apr 28 17:36:13 tj-Precision-M4800 kernel: [ 33.205078] type=1400 audit(1398699373.619:66): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2768 comm="apparmor_parser"
Forfatter til Ubuntuguiden: http://www.vidas.dk/guides/ubuntuguiden.html
Kører LTS udgaverne.
"It's always easy if you know how to do it."
Kører LTS udgaverne.
"It's always easy if you know how to do it."
-
- Indlæg: 5095
- Tilmeldt: 27. apr 2008, 02:16
- IRC nickname: lars_t_h
- Geografisk sted: Fyn
Re: USB WIFI dongle
thj01 skrev:nye meddelelserKode: Vælg alt
Apr 28 17:36:13 tj-Precision-M4800 kernel: [ 33.204852] type=1400 audit(1398699373.619:64): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2768 comm="apparmor_parser"
Apr 28 17:36:13 tj-Precision-M4800 kernel: [ 33.204855] type=1400 audit(1398699373.619:65): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2768 comm="apparmor_parser"
Apr 28 17:36:13 tj-Precision-M4800 kernel: [ 33.205078] type=1400 audit(1398699373.619:66): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2768 comm="apparmor_parser"
cupsd er UNIX printer servicen - du skal nok nærmere se på ACPI (strømstyring). Har du prøvet at deaktivere ACPI?
Man kan gøre det i BIOS, og sikkert også i UEFI, og også på kernens boot linie
Tilføj:
Kode: Vælg alt
acpi=off
... i slutningen af kernens boot linie.
Der er nævnt mange flere muligheder på https://www.kernel.org/doc/Documentation/kernel-parameters.txt:
acpi= [HW,ACPI,X86]
Advanced Configuration and Power Interface
Format: { force | off | strict | noirq | rsdt }
force -- enable ACPI if default was off
off -- disable ACPI if default was on
noirq -- do not use ACPI for IRQ routing
strict -- Be less tolerant of platforms that are not
strictly ACPI specification compliant.
rsdt -- prefer RSDT over (default) XSDT
copy_dsdt -- copy DSDT to memory
See also Documentation/power/runtime_pm.txt, pci=noacpi
acpi_rsdp= [ACPI,EFI,KEXEC]
Pass the RSDP address to the kernel, mostly used
on machines running EFI runtime service to boot the
second kernel for kdump.
acpi_apic_instance= [ACPI, IOAPIC]
Format: <int>
2: use 2nd APIC table, if available
1,0: use 1st APIC table
default: 0
acpi_backlight= [HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
(e.g. thinkpad_acpi, sony_acpi, etc.) instead
of the ACPI video.ko driver.
acpi.debug_layer= [HW,ACPI,ACPI_DEBUG]
acpi.debug_level= [HW,ACPI,ACPI_DEBUG]
Format: <int>
CONFIG_ACPI_DEBUG must be enabled to produce any ACPI
debug output. Bits in debug_layer correspond to a
_COMPONENT in an ACPI source file, e.g.,
#define _COMPONENT ACPI_PCI_COMPONENT
Bits in debug_level correspond to a level in
ACPI_DEBUG_PRINT statements, e.g.,
ACPI_DEBUG_PRINT((ACPI_DB_INFO, ...
The debug_level mask defaults to "info". See
Documentation/acpi/debug.txt for more information about
debug layers and levels.
Enable processor driver info messages:
acpi.debug_layer=0x20000000
Enable PCI/PCI interrupt routing info messages:
acpi.debug_layer=0x400000
Enable AML "Debug" output, i.e., stores to the Debug
object while interpreting AML:
acpi.debug_layer=0xffffffff acpi.debug_level=0x2
Enable all messages related to ACPI hardware:
acpi.debug_layer=0x2 acpi.debug_level=0xffffffff
Some values produce so much output that the system is
unusable. The "log_buf_len" parameter may be useful
if you need to capture more output.
acpi_irq_balance [HW,ACPI]
ACPI will balance active IRQs
default in APIC mode
acpi_irq_nobalance [HW,ACPI]
ACPI will not move active IRQs (default)
default in PIC mode
acpi_irq_isa= [HW,ACPI] If irq_balance, mark listed IRQs used by ISA
Format: <irq>,<irq>...
acpi_irq_pci= [HW,ACPI] If irq_balance, clear listed IRQs for
use by PCI
Format: <irq>,<irq>...
acpi_no_auto_serialize [HW,ACPI]
Disable auto-serialization of AML methods
AML control methods that contain the opcodes to create
named objects will be marked as "Serialized" by the
auto-serialization feature.
This feature is enabled by default.
This option allows to turn off the feature.
acpi_no_auto_ssdt [HW,ACPI] Disable automatic loading of SSDT
acpica_no_return_repair [HW, ACPI]
Disable AML predefined validation mechanism
This mechanism can repair the evaluation result to make
the return objects more ACPI specification compliant.
This option is useful for developers to identify the
root cause of an AML interpreter issue when the issue
has something to do with the repair mechanism.
acpi_os_name= [HW,ACPI] Tell ACPI BIOS the name of the OS
Format: To spoof as Windows 98: ="Microsoft Windows"
acpi_osi= [HW,ACPI] Modify list of supported OS interface strings
acpi_osi="string1" # add string1
acpi_osi="!string2" # remove string2
acpi_osi=!* # remove all strings
acpi_osi=! # disable all built-in OS vendor
strings
acpi_osi= # disable all strings
'acpi_osi=!' can be used in combination with single or
multiple 'acpi_osi="string1"' to support specific OS
vendor string(s). Note that such command can only
affect the default state of the OS vendor strings, thus
it cannot affect the default state of the feature group
strings and the current state of the OS vendor strings,
specifying it multiple times through kernel command line
is meaningless. This command is useful when one do not
care about the state of the feature group strings which
should be controlled by the OSPM.
Examples:
1. 'acpi_osi=! acpi_osi="Windows 2000"' is equivalent
to 'acpi_osi="Windows 2000" acpi_osi=!', they all
can make '_OSI("Windows 2000")' TRUE.
'acpi_osi=' cannot be used in combination with other
'acpi_osi=' command lines, the _OSI method will not
exist in the ACPI namespace. NOTE that such command can
only affect the _OSI support state, thus specifying it
multiple times through kernel command line is also
meaningless.
Examples:
1. 'acpi_osi=' can make 'CondRefOf(_OSI, Local1)'
FALSE.
'acpi_osi=!*' can be used in combination with single or
multiple 'acpi_osi="string1"' to support specific
string(s). Note that such command can affect the
current state of both the OS vendor strings and the
feature group strings, thus specifying it multiple times
through kernel command line is meaningful. But it may
still not able to affect the final state of a string if
there are quirks related to this string. This command
is useful when one want to control the state of the
feature group strings to debug BIOS issues related to
the OSPM features.
Examples:
1. 'acpi_osi="Module Device" acpi_osi=!*' can make
'_OSI("Module Device")' FALSE.
2. 'acpi_osi=!* acpi_osi="Module Device"' can make
'_OSI("Module Device")' TRUE.
3. 'acpi_osi=! acpi_osi=!* acpi_osi="Windows 2000"' is
equivalent to
'acpi_osi=!* acpi_osi=! acpi_osi="Windows 2000"'
and
'acpi_osi=!* acpi_osi="Windows 2000" acpi_osi=!',
they all will make '_OSI("Windows 2000")' TRUE.
acpi_pm_good [X86]
Override the pmtimer bug detection: force the kernel
to assume that this machine's pmtimer latches its value
and always returns good values.
acpi_sci= [HW,ACPI] ACPI System Control Interrupt trigger mode
Format: { level | edge | high | low }
acpi_skip_timer_override [HW,ACPI]
Recognize and ignore IRQ0/pin2 Interrupt Override.
For broken nForce2 BIOS resulting in XT-PIC timer.
acpi_sleep= [HW,ACPI] Sleep options
Format: { s3_bios, s3_mode, s3_beep, s4_nohwsig,
old_ordering, nonvs, sci_force_enable }
See Documentation/power/video.txt for information on
s3_bios and s3_mode.
s3_beep is for debugging; it makes the PC's speaker beep
as soon as the kernel's real-mode entry point is called.
s4_nohwsig prevents ACPI hardware signature from being
used during resume from hibernation.
old_ordering causes the ACPI 1.0 ordering of the _PTS
control method, with respect to putting devices into
low power states, to be enforced (the ACPI 2.0 ordering
of _PTS is used by default).
nonvs prevents the kernel from saving/restoring the
ACPI NVS memory during suspend/hibernation and resume.
sci_force_enable causes the kernel to set SCI_EN directly
on resume from S1/S3 (which is against the ACPI spec,
but some broken systems don't work without it).
acpi_use_timer_override [HW,ACPI]
Use timer override. For some broken Nvidia NF5 boards
that require a timer override, but don't have HPET
acpi_enforce_resources= [ACPI]
{ strict | lax | no }
Check for resource conflicts between native drivers
and ACPI OperationRegions (SystemIO and SystemMemory
only). IO ports and memory declared in ACPI might be
used by the ACPI subsystem in arbitrary AML code and
can interfere with legacy drivers.
strict (default): access to resources claimed by ACPI
is denied; legacy drivers trying to access reserved
resources will fail to bind to device using them.
lax: access to resources claimed by ACPI is allowed;
legacy drivers trying to access reserved resources
will bind successfully but a warning message is logged.
no: ACPI OperationRegions are not marked as reserved,
no further checks are performed.
acpi_no_memhotplug [ACPI] Disable memory hotplug. Useful for kdump
kernels.
add_efi_memmap [EFI; X86] Include EFI memory map in
kernel's map of available physical RAM.
/Lars
Jeg er Software ingeniør (Diplomingeniør) i Informationsteknologi og indlejede systemer, hvor indlejrede systemer er computer (microcontroller) + elektronik i for eksempel et TV, en router, en vaskemaskine og den slags
-
- Indlæg: 2667
- Tilmeldt: 21. nov 2006, 10:06
- Geografisk sted: Fredericia
Re: USB WIFI dongle
Hårh - det ser vildt ud...
Hvis jeg fjerne ACPI - forsvinder der så ikke nogle strømstyrings-features?
Hvis jeg fjerne ACPI - forsvinder der så ikke nogle strømstyrings-features?
Forfatter til Ubuntuguiden: http://www.vidas.dk/guides/ubuntuguiden.html
Kører LTS udgaverne.
"It's always easy if you know how to do it."
Kører LTS udgaverne.
"It's always easy if you know how to do it."
-
- Admin
- Indlæg: 20860
- Tilmeldt: 15. nov 2009, 15:04
- IRC nickname: AJenbo
- Geografisk sted: Vanløse, København
Re: USB WIFI dongle
Jo, de fleste af dem. Det er der for man lidt mere målrettet kan bruge nogle af de mange paramerer til kun at deaktivere den del man har problemer med.
Hvem er online
Brugere der læser dette forum: [Bot] og 0 gæster