Acer AspireOne 522/AMD C-50/64-bit/11.4RC1: Boot hangs without ethernet connection

[thwibble]

Hi everyone,
I've installed 11.4RC1-64bit onto my sparkly new Aspire One 522. No errors on install. (Acer 10.1" AMD C-50 Netbook (AO522-BZ499) - Black : 10" Netbooks and Larger - Future Shop)

I have configured the wifi for my home network. Everything seems to work fine except for this:

• The unit will hang on boot if the ethernet cable is not plugged in (it hangs just as the desktop would normally kick-in)
• I can remove the ethernet cable once the unit has booted and the unit does not lock up and transfers to the wifi
• If I suspend the unit, when it awakens if the ethernet cable is not present it will freeze

I added 'Init 3' to boot without the ethernet cable and the last reported line before freezing is 'Connecting...' and then a count-down. It usually freezes somewhere between 21 and 16.

If I add 'Init 1' then I can get the text YAST to run, but whenever I try to fiddle with the network settings the unit will lock up about half-way down the list of things it's doing to preserve the changes, which I think is 'Writing new settings'.

SUSE is correctly identifying the wired/wireless NIC's and both work fine once the unit has booted. I just can't boot, or resume from suspend without the CAT5 connected!

Most odd.

I've got two other machines (one laptop, one desktop) both running 11.3; so I'm reasonably familiar with SUSE but by no means an expert.

Thanks!

Any thoughts much appreciated.

[Knurpht]

Hi, welcome here

Are you aware of the fact that 11.4 is not "ready" yet?

Did you check the install media?

A couple of remarks:
Runlevel 1 (init 1) means "single user", i.e. no X, no network. This means you could fiddle around for the rest of your life in runlevel 1, networking is not going to work. So when you're trying to configure it through Yast, at the end of it, it's trying to start the networking, which it cannot, since it's in runlevel 1.

[thwibble]

Hi, welcome here Thank you - I appreciate that

Are you aware of the fact that 11.4 is not "ready" yet? Yes, that's why I'm not to frantic to get it sorted out, I'm hoping that maybe in the formal release it gets sorted out. That said, I thought that it might be worth noting in case it had come up for a few people.

Did you check the install media? Yes. I've actually downloaded the 64bit image a couple of times, and made the USB-bootable a handful of times on at least two different USB sticks.

A couple of remarks:
Runlevel 1 (init 1) means "single user", i.e. no X, no network. This means you could fiddle around for the rest of your life in runlevel 1, networking is not going to work. So when you're trying to configure it through Yast, at the end of it, it's trying to start the networking, which it cannot, since it's in runlevel 1.

That makes sense.

[thwibble]

...still, if you have any idea's I'd love to hear them

[thwibble]

Poo - does the same thing with RC2 also

[lwfinger]

On 02/28/2011 11:36 PM, thwibble wrote:
>
> Poo - does the same thing with RC2 also

Are you using NetworkManager or ifup? If ifup, you need to make the wired
connection to be active only when plugged, not auto or on boot.

Have you killed the bootsplash with an escape to see where it hangs? You can
also switch to virtual console 1 (CTRL-ALT-F1) to see it is still hung after the
desktop comes up.

Are you mounting any NFS volumes from fstab? If so, does changing Defaultvers in
/etc/nfsmount.conf to 3 rather than 4 help?

[manticoretrader]

Confirmed, the laptop freezes as soon as shutting down the wired network (which itself works as long as connected). The only work-around I found is to enable the wired network on demand only (avoiding Networkmanager/WICD) and restart the laptop afterwards.

For details please check: manticore-projects • Linux on Acer Aspire one 522

[tactususe]

Sorry for pushing up an old thread, but this issue is still relevant.

For me, adding "blacklist atl1c" to /etc/modprobe.d/50-blacklist.conf helped.

If I need cabled connection I load atl1c driver only when cable is attached. Network-manager seem to discover and enable the interfaces automatically when I load or unload drivers. I made a quick shell script that make me switch between wireless and wired by loading and unloading wireless and ethernet drivers.

#!/bin/bash
# Network flip flop for Acer Aspire One 522 w/Atheros wireless.
# License: Public domain.
WIFI="ath9k"
ETHERNET="atl1c"

if [[ $EUID -ne 0 ]]; then
  echo "You must be a root user" 2>&1
  exit 1
fi

if [ -n "`lsmod | grep -o ^$WIFI`" ]
then
     echo "Switch to ethernet"
     echo "modprobe -r $WIFI"
     modprobe -r $WIFI
     sleep 5
     echo "modprobe $ETHERNET"
     modprobe $ETHERNET
else
     echo "Switch to wireless"
     echo "modprobe -r $ETHERNET"
     modprobe -r $ETHERNET
     sleep 5
     echo "modprobe $WIFI"
     modprobe $WIFI
fi
echo "End script"

[Ski_K2]

I found in my Aspire One 721 I had to blacklist acer_wmi tp get wifi to work.

It conflicted with my wifi driver brcm80211.

Maybe it's also conflicting with your nic driver?