Acer Aspire One 522 Wi-Fi Causes Crash.

Hey guys,

I moved to OpenSUSE from Ubuntu, because for some reason Ubuntu kept crashing at log-in. OpenSUSE has been great thus far, except that I can’t connect to the wi-fi.
The Wi-fi here doesn’t have a password because I am currently staying with my in-laws and they really don’t listen about security and such.

Well, every time I try to connect to the wi-fi I only have about 30 seconds after authenticating it as admin before the system just freezes. It sees the list of networks so I am assuming the card has been detected and is at least partially working.

Has anyone else had any issues like this? What do you guys suggest?

Many thanks,

Strange,

I also have this acer 522 and have the same problem since a long time. I also have tried several distro’s.
There must be many more people with this problem.

Why isn’t this one solved already?

gr. Marco

P.S. I solve this by connecting the wired network, so I can stil use open suse in the hope a solution will come quick.

On 03/17/2012 05:26 AM, lager703 wrote:
>
> Strange,
>
> I also have this acer 522 and have the same problem since a long time.
> I also have tried several distro’s.
> There must be many more people with this problem.
>
> Why isn’t this one solved already?
>
> gr. Marco
>
>
> P.S. I solve this by connecting the wired network, so I can stil use
> open suse in the hope a solution will come quick.

This is likely not an openSUSE, but a kernel problem. It isn’t solved because
there are not many people that have this device, and those that do have not
provided the info needed to solve it. When it “crashes”, what are the symptoms?
Is anything logged?

Without more basic information, we cannot help you. I have no idea what wireless
device Acer puts in a 522. It is possible that not all 522s even have the same
unit. You need to give us the PCI or USB IDs so that we know that information.
If your device is PCI, please post the output of ‘/sbin/lspci -nn’. If USB, then
post the output of ‘lsusb’.

Hey, Im using a Acer Aspire One AO-722, and I had the same problem, you could go in to you BIO’s, and change it to where connect to a network is first in the list, then, plug you computer with wire in to a router, and do updates, then it should be fine, just leave it on connect to a network first, it does take a few more seconds to boot up, but you got to do what you got to do.

I have no idea what wireless
device Acer puts in a 522. It is possible that not all 522s even have the same
unit. You need to give us the PCI or USB IDs so that we know that information.
If your device is PCI, please post the output of ‘/sbin/lspci -nn’. If USB, then
post the output of ‘lsusb’.[/QUOTE]

Hello,

thanks for your answer,

The netbook crashes when no cable is connected to the network.
It crashes everytime.

here are the results of

/sbin/lspci -nn

00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 14h Processor Root Complex [1022:1510]
00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 6250 [1002:9804]
00:01.1 Audio device [0403]: ATI Technologies Inc Wrestler HDMI Audio [Radeon HD 6250/6310] [1002:1314]
00:11.0 SATA controller [0106]: ATI Technologies Inc SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391]
00:12.0 USB Controller [0c03]: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
00:12.2 USB Controller [0c03]: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
00:13.0 USB Controller [0c03]: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397]
00:13.2 USB Controller [0c03]: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller [1002:4396]
00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 42)
00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] (rev 40)
00:14.3 ISA bridge [0601]: ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller [1002:439d] (rev 40)
00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40)
00:15.0 PCI bridge [0604]: ATI Technologies Inc SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0) [1002:43a0]
00:15.2 PCI bridge [0604]: ATI Technologies Inc SB900 PCI to PCI bridge (PCIE port 2) [1002:43a2]
00:15.3 PCI bridge [0604]: ATI Technologies Inc SB900 PCI to PCI bridge (PCIE port 3) [1002:43a3]
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 0 [1022:1700] (rev 43)
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 1 [1022:1701]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 2 [1022:1702]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 3 [1022:1703]
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 4 [1022:1704]
00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 6 [1022:1718]
00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 5 [1022:1716]
00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Family 12h/14h Processor Function 7 [1022:1719]
06:00.0 Ethernet controller [0200]: Atheros Communications AR8152 v2.0 Fast Ethernet [1969:2062] (rev c1)
07:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)

if any more data needed then let me know. I am a beginner in Linux but a big fan.

gr. Marco

On 03/18/2012 04:26 AM, lager703 wrote:
> 07:00.0 Network controller [0280]: Atheros Communications Inc. AR9285
> Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)

The above output is for your wireless device. AFAIK, the driver for that device
does not cause many problems.

What are the symptoms of the crash? No one has said exactly what happens when
the computer crashes. If the keyboard lights are flashing at 1 Hz, that means
there is a kernel panic. To see any diagnostics about such an event, you need to
switch to the logging console by using CTRL-ALT-F10 BEFORE the crash occurs.
You get back to the GUI with CTRL-ALT-F7. The crash information will need to be
copied by hand or you need to photograph the screen.

what happens is this,

when I startup with only wireless then everything freezes, even the mouse and nothing else works anymore, except a long press on the on/of button.

When I am working with the wired connected and i unplug the cable it also freezes, same like before.

I switched to the logging console and I disconnected the cable and the computer froze again. Then I made a picture from the screen.

How do I publish this photo btw?

hope you can make something of it.

sorry,

it seems I have two loginnames.

Gr… Marco

On 03/18/2012 04:46 PM, lager703 wrote:
>
> lager239;2449331 Wrote:
>> what happens is this,
>>
>> when I startup with only wireless then everything freezes, even the
>> mouse and nothing else works anymore, except a long press on the on/of
>> button.
>>
>> When I am working with the wired connected and i unplug the cable it
>> also freezes, same like before.
>>
>> I switched to the logging console and I disconnected the cable and the
>> computer froze again. Then I made a picture from the screen.
>>
>> How do I publish this photo btw?
>>
>> hope you can make something of it.
>
> sorry,
>
> it seems I have two loginnames.

Go to http://paste.opensuse.org/, and select the “image” link.

SUSE Paste

On 03/19/2012 12:36 PM, lager703 wrote:
>
> lwfinger;2449357 Wrote:
>> On 03/18/2012 04:46 PM, lager703 wrote:
>>>
>> Go to ‘SUSE Paste’ (http://paste.opensuse.org/), and select the “image”
>> link.
>
>
> ‘SUSE Paste’ (http://paste.opensuse.org/60560296)

The photo was shot from a little too close, and the traceback was hard to see,
but everything I saw was from the ATI proprietary driver, fglrx. As that
traceback finished 1.5 minutes before the log ended, it does not seem that your
“crash” actually crashed the kernel. There must be something else going on such
as an interrupt that is not setup correctly, one is not being cleared, or there
is a stuck process.

How long have you waited? If you have a stuck process, it will take at least 2
minutes to be reported.

I logged on to the logging console withh ctrl-alt-F10 and then after a minute unplugged the network cable…
Nothing else happened after that.
Also not after 2 or 3 minutes. Everything freezes. Even my keyboard and screen didn’t give any response.
I don’t know if a process can keep your linux busy forever. I always thought that in basic all processes could be killed by a command. But even that doesn’t work anymore.

Hope You can follow my dutch-english.

On 03/19/2012 06:16 PM, lager703 wrote:
>
> I logged on to the logging console withh ctrl-alt-F10 and then after a
> minute unplugged the network cable…
> Nothing else happened after that.
> Also not after 2 or 3 minutes. Everything freezes. Even my keyboard and
> screen didn’t give any response.
> I don’t know if a process can keep your linux busy forever. I always
> thought that in basic all processes could be killed by a command. But
> even that doesn’t work anymore.
>
> Hope You can follow my dutch-english.

No problem with your English.

Unless we know what is happening through some diagnostic logging, then there is
little that can be done. If you have only 1 CPU, and it is busy with some
high-priority task, then the keyboard will never get any attention.

The processor is an AMD C50 dual core.
I don’t believe it is because the processor is busy, because even when you wait for 10 minutes, still nothing happens.
How can I help with this diagnostic logging?
Or wich commands should I log. Or what else can I do?

On 03/21/2012 01:36 PM, lager703 wrote:
>
> lwfinger;2449757 Wrote:
>> On 03/19/2012 06:16 PM, lager703 wrote:
>>>
>>
>> Unless we know what is happening through some diagnostic logging, then
>> there is
>> little that can be done. If you have only 1 CPU, and it is busy with
>> some
>> high-priority task, then the keyboard will never get any attention.
>
>
> The processor is an AMD C50 dual core.
> I don’t believe it is because the processor is busy, because even when
> you wait for 10 minutes, still nothing happens.
> How can I help with this diagnostic logging?
> Or wich commands should I log. Or what else can I do?

Run the following command before you make it crash


sudo tail -f /var/log/messages

If nothing new is produced when it crashes, I have no ideas. If it had worked
with any kernel, we could bisect to find the bad commit; however, I see no
indication that it has ever worked.

I just purchased an AR9285 on E-bay and will see what it does when it comes.

this is from a file called warn

Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: RSDP 00000000000fe020 00024 (v02 ACRSYS)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: XSDT 000000006eef5120 00064 (v01 ACRSYS ACRPRDCT 00000003 01000013)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: FACP 000000006eef4000 000F4 (v04 ACRSYS ACRPRDCT 00000003 1025 00040000)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: DSDT 000000006eee8000 080AB (v01 ACRSYS ACRPRDCT F0000000 1025 00040000)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: FACS 000000006ee97000 00040
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: HPET 000000006eef3000 00038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: APIC 000000006eef2000 00084 (v02 ACRSYS ACRPRDCT 00000001 1025 00040000)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: MCFG 000000006eef1000 0003C (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: BOOT 000000006eee7000 00028 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: SLIC 000000006eee6000 00176 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: SSDT 000000006eee5000 0030C (v01 AMD POWERNOW 00000001 AMD 00000001)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: SSDT 000000006eee3000 012FA (v02 AMD ALIB 00000001 MSFT 04000000)
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Zone PFN ranges:
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] DMA 0x00000010 -> 0x00001000
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] DMA32 0x00001000 -> 0x00100000
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Normal empty
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Movable zone start PFN for each node
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] early_node_map[4] active PFN ranges
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] 0: 0x00000010 -> 0x0000009f
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] 0: 0x00000100 -> 0x0006d670
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] 0: 0x0006d870 -> 0x0006ed3f
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] 0: 0x0006eef6 -> 0x0006ef00
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 447118
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Policy zone: DMA32
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Fast TSC calibration using PIT
Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Detected 997.546 MHz processor.
Mar 21 20:51:07 linux-sw0c kernel: 0.163882] ACPI: Executed 1 blocks of module-level executable AML code
Mar 21 20:51:07 linux-sw0c kernel: 1.920272] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Mar 21 20:51:07 linux-sw0c kernel: 18.853676] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Mar 21 20:51:07 linux-sw0c kernel: 18.858177] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Mar 21 20:51:07 linux-sw0c kernel: 19.657357] fglrx: module license ‘Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY’ taints kernel.
Mar 21 20:51:07 linux-sw0c kernel: 19.657369] Disabling lock debugging due to kernel taint
Mar 21 20:51:07 linux-sw0c kernel: 20.072640] acer_wmi: No or unsupported WMI interface, unable to load
Mar 21 20:51:07 linux-sw0c kernel: 20.115893] SP5100 TCO timer: mmio address 0xb8fe00 already in use
Mar 21 20:51:10 linux-sw0c mcelog: mcelog read: No such device
Mar 21 20:51:11 linux-sw0c ntpd[1146]: bind(19) AF_INET6 fe80::ba70:f4ff:fe77:3853%2#123 flags 0x11 failed: Cannot assign requested address
Mar 21 20:51:11 linux-sw0c ntpd[1146]: unable to create socket on eth0 (3) for fe80::ba70:f4ff:fe77:3853#123
Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of key ‘Language’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of key ‘ShowUsers’ in section [X-
-Greeter] of /usr/share/kde4/config/kdm/kdmrc
Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of key ‘Theme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of key ‘UseBackground’ in section [X-
-Greeter] of /usr/share/kde4/config/kdm/kdmrc
Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of key ‘UseTheme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of key ‘AllowShutdown’ in section [X-:
-Core] of /usr/share/kde4/config/kdm/kdmrc
Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of key ‘AutoLoginEnable’ in section [X-:0-Core] of /usr/share/kde4/config/kdm/kdmrc
Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of key ‘AutoLoginUser’ in section [X-:0-Core] of /usr/share/kde4/config/kdm/kdmrc
Mar 21 19:52:05 linux-sw0c rtkit-daemon[2148]: Failed to make ourselves RT: Operation not permitted
Mar 21 20:52:06 linux-sw0c pulseaudio[2146]: [pulseaudio] pid.c: Stale PID file, overwriting.
Mar 21 20:52:11 linux-sw0c pulseaudio[2192]: [pulseaudio] pid.c: Daemon already running.
Mar 21 20:52:11 linux-sw0c pulseaudio[2195]: [pulseaudio] pid.c: Daemon already running.
Mar 21 20:52:12 linux-sw0c pulseaudio[2200]: [pulseaudio] pid.c: Daemon already running.

On 03/21/2012 03:56 PM, lager703 wrote:
>
> this is from a file called warn
>
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: RSDP
> 00000000000fe020 00024 (v02 ACRSYS)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: XSDT
> 000000006eef5120 00064 (v01 ACRSYS ACRPRDCT 00000003 01000013)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: FACP
> 000000006eef4000 000F4 (v04 ACRSYS ACRPRDCT 00000003 1025 00040000)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: DSDT
> 000000006eee8000 080AB (v01 ACRSYS ACRPRDCT F0000000 1025 00040000)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: FACS
> 000000006ee97000 00040
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: HPET
> 000000006eef3000 00038 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: APIC
> 000000006eef2000 00084 (v02 ACRSYS ACRPRDCT 00000001 1025 00040000)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: MCFG
> 000000006eef1000 0003C (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: BOOT
> 000000006eee7000 00028 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: SLIC
> 000000006eee6000 00176 (v01 ACRSYS ACRPRDCT 00000001 1025 00040000)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: SSDT
> 000000006eee5000 0030C (v01 AMD POWERNOW 00000001 AMD 00000001)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] ACPI: SSDT
> 000000006eee3000 012FA (v02 AMD ALIB 00000001 MSFT 04000000)
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Zone PFN ranges:
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] DMA 0x00000010
> -> 0x00001000
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] DMA32 0x00001000
> -> 0x00100000
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Normal empty
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Movable zone start
> PFN for each node
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] early_node_map[4]
> active PFN ranges
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] 0: 0x00000010 ->
> 0x0000009f
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] 0: 0x00000100 ->
> 0x0006d670
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] 0: 0x0006d870 ->
> 0x0006ed3f
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] 0: 0x0006eef6 ->
> 0x0006ef00
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Built 1 zonelists in
> Node order, mobility grouping on. Total pages: 447118
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Policy zone: DMA32
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Fast TSC calibration
> using PIT
> Mar 21 20:51:07 linux-sw0c kernel: 0.000000] Detected 997.546 MHz
> processor.
> Mar 21 20:51:07 linux-sw0c kernel: 0.163882] ACPI: Executed 1
> blocks of module-level executable AML code
> Mar 21 20:51:07 linux-sw0c kernel: 1.920272] Dquot-cache hash
> table entries: 512 (order 0, 4096 bytes)
> Mar 21 20:51:07 linux-sw0c kernel: 18.853676] ACPI: Deprecated
> procfs I/F for battery is loaded, please retry with
> CONFIG_ACPI_PROCFS_POWER cleared
> Mar 21 20:51:07 linux-sw0c kernel: 18.858177] ACPI: Deprecated
> procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER
> cleared
> Mar 21 20:51:07 linux-sw0c kernel: 19.657357] fglrx: module license
> ‘Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY’ taints
> kernel.
> Mar 21 20:51:07 linux-sw0c kernel: 19.657369] Disabling lock
> debugging due to kernel taint
> Mar 21 20:51:07 linux-sw0c kernel: 20.072640] acer_wmi: No or
> unsupported WMI interface, unable to load
> Mar 21 20:51:07 linux-sw0c kernel: 20.115893] SP5100 TCO timer:
> mmio address 0xb8fe00 already in use
> Mar 21 20:51:10 linux-sw0c mcelog: mcelog read: No such device
> Mar 21 20:51:11 linux-sw0c ntpd[1146]: bind(19) AF_INET6
> fe80::ba70:f4ff:fe77:3853%2#123 flags 0x11 failed: Cannot assign
> requested address
> Mar 21 20:51:11 linux-sw0c ntpd[1146]: unable to create socket on eth0
> (3) for fe80::ba70:f4ff:fe77:3853#123
> Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of
> key ‘Language’ in section [X--Greeter] of
> /usr/share/kde4/config/kdm/kdmrc
> Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of
> key ‘ShowUsers’ in section [X-
-Greeter] of
> /usr/share/kde4/config/kdm/kdmrc
> Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of
> key ‘Theme’ in section [X--Greeter] of /usr/share/kde4/config/kdm/kdmrc
> Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of
> key ‘UseBackground’ in section [X-
-Greeter] of
> /usr/share/kde4/config/kdm/kdmrc
> Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of
> key ‘UseTheme’ in section [X--Greeter] of
> /usr/share/kde4/config/kdm/kdmrc
> Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of
> key ‘AllowShutdown’ in section [X-:
-Core] of
> /usr/share/kde4/config/kdm/kdmrc
> Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of
> key ‘AutoLoginEnable’ in section [X-:0-Core] of
> /usr/share/kde4/config/kdm/kdmrc
> Mar 21 20:51:13 linux-sw0c kdm_config[1263]: Multiple occurrences of
> key ‘AutoLoginUser’ in section [X-:0-Core] of
> /usr/share/kde4/config/kdm/kdmrc
> Mar 21 19:52:05 linux-sw0c rtkit-daemon[2148]: Failed to make ourselves
> RT: Operation not permitted
> Mar 21 20:52:06 linux-sw0c pulseaudio[2146]: [pulseaudio] pid.c: Stale
> PID file, overwriting.
> Mar 21 20:52:11 linux-sw0c pulseaudio[2192]: [pulseaudio] pid.c: Daemon
> already running.
> Mar 21 20:52:11 linux-sw0c pulseaudio[2195]: [pulseaudio] pid.c: Daemon
> already running.
> Mar 21 20:52:12 linux-sw0c pulseaudio[2200]: [pulseaudio] pid.c: Daemon
> already running.

Nothing that is wifi related is shown here.