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?
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.
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.
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.
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.
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.