Need to wait 2 minutes before wireless connects

Installed openSUSE Factory using the openSUSE-Factory-NET-i586-Current.iso.
During installation, wireless is detected but unable to connect so the installation was performed with Ethernet (RJ45) cable instead of wireless.

After installation,
noticed that when using Ethernet (RJ45) cable, do not need to wait much for the internet connection to be established during boot up.
However, if I were to remove the Ethernet cable and try to connect using wireless during boot up, will need to** wait approximately 2 minutes** before openSUSE activates the wireless connection.

Not wanting to wait for the 2 minutes for wireless to connect,
wanted to configure wireless in Yast but the option is masked out as shown below.

http://oi59.tinypic.com/1zm04ll.jpg

Any advise how I can configure the wireless properly?

are you using auto or manual DHCP?

wifi may be faster if manual is used

wifi will always be slower than wire due to the security negotiations

also try selecting Traditional Method with ifup, then reboot,

then try your setup again, there are lots of threads on this point

I have not tried this with wireless on factory.

When you get that Yast “network settings” screen, click the “Global Options” tab.

Near the top of the screen, you will see that NetworkManager is selected. Switch that to using “wicked”.

Then go back to the “Overview” tab, and you should be able to configure your wireless card.

Hi keellambert,

openSUSE Factory does not have **Traditional Method with ifup **any more,
it comes with nrickert had mentioned,

  • NetworkManager Service
  • Wicked Service
  • Network Services Disabled.

Hi nrickert,

Did try switching to Wicked and Disbling Network Service.
It allows the configuring of the Wireless and Ethernet connection but the 2 minutes wait is still there, even after reboot.

Thanks anyway, 2 minute is a long time but still bearable.

Hi
After the system is up, can you open a terminal and post the output from;


systemd-analyze blame

Just to be sure it’s not something else masking the delay.

On 08/10/2014 09:26 PM, malcolmlewis wrote:
>
> Hi
> After the system is up, can you open a terminal and post the output
> from;
>
> Code:
> --------------------
>
> systemd-analyze blame
>
> --------------------
>
> Just to be sure it’s not something else masking the delay.

You should be able to eliminate any bootup delay when using NetworkManager if
you uncheck the “System Connection” box in the Connection Manager. If not, you
should report a bug for Factory.

On 2014-08-11 04:16, michalng wrote:
>
> Hi keellambert,
>
> openSUSE Factory does not have *Traditional Method with ifup *any more,

which is why you should have asked in the prerelease-beta forum, aka
factory forum, here: because there you have more chances of finding
people familiar with factory and its new features.

:wink:


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

I’m not running factory on my laptop.

On a desktop, network startup is noticeably slower with NetworkManager than with wicked, but that’s for ethernet. It’s probably still less than 2 minutes. So you may have something else happening that slows down wireless.

Below is the output of systemd-analyze blame, NetworkManager.service is at 325ms.
But the connection is still the same wait.

     11.317s [email]systemd-cryptsetup@cr_ata\x2dST9500420AS_5VJ4010J\x2dpart6.servic[/email]e
      6.319s systemd-udev-settle.service
      3.613s display-manager.service
      3.609s ModemManager.service
      3.408s nscd.service
      3.348s SuSEfirewall2_init.service
      2.583s plymouth-start.service
      2.077s lvm2-activation.service
      1.957s lvm2-activation-early.service
      1.816s vboxdrv.service
      1.440s systemd-fsck-root.service
      1.237s systemd-udev-root-symlink.service
       947ms systemd-tmpfiles-setup-dev.service
       912ms mnt-garden.mount
       806ms sys-kernel-debug.mount
       804ms dev-mqueue.mount
       803ms dev-hugepages.mount
       764ms [email]systemd-fsck@dev-mapper-cr_ata\x2dST9500420AS_5VJ4010J\x2dpart6.servic[/email]e
       646ms systemd-udev-trigger.service
       559ms systemd-sysctl.service
       475ms systemd-tmpfiles-setup.service
       433ms systemd-modules-load.service
       413ms postfix.service
       411ms lvm2-lvmetad.service
       364ms apparmor.service
       
       325ms NetworkManager.service
       
       299ms SuSEfirewall2.service
       293ms dm-event.service
       219ms [email]systemd-rfkill@rfkill0.servic[/email]e
       203ms dev-disk-by\x2duuid-ddb09b76\x2db96e\x2d4523\x2dbb6a\x2d00aa950fb8c1.swap
       176ms systemd-udevd.service
       166ms kmod-static-nodes.service
       135ms plymouth-read-write.service
       118ms systemd-random-seed.service
       109ms polkit.service
       106ms systemd-logind.service
        86ms alsa-restore.service
        81ms systemd-user-sessions.service
        77ms rc-local.service
        77ms iscsi.service
        75ms systemd-localed.service
        72ms bluetooth.service
        71ms systemd-readahead-replay.service
        68ms avahi-daemon.service
        66ms wpa_supplicant.service
        59ms systemd-readahead-collect.service
        58ms [email]user@1000.servic[/email]e
        40ms NetworkManager-dispatcher.service
        39ms ntpd.service
        35ms systemd-hostnamed.service
        27ms vboxballoonctrl-service.service
        21ms vboxautostart-service.service
        20ms cycle.service
        16ms vboxweb-service.service
        11ms systemd-journal-flush.service
         9ms systemd-remount-fs.service
         7ms auditd.service
         5ms [email]systemd-backlight@backlight:acpi_video0.servic[/email]e
         5ms NetworkManager-wait-online.service
         5ms systemd-vconsole-setup.service
         5ms systemd-update-utmp.service
         4ms systemd-update-utmp-runlevel.service
         3ms sys-fs-fuse-connections.mount
         1ms [email]systemd-rfkill@rfkill1.servic[/email]e

lwfinger

You should be able to eliminate any bootup delay when using NetworkManager if
you uncheck the “System Connection” box in the Connection Manager. If not, you
should report a bug for Factory.

Couldn’t locate the “System Connection”. Maybe because I’m running Factory ?

robin_listas

which is why you should have asked in the prerelease-beta forum, aka
factory forum, here: because there you have more chances of finding
people familiar with factory and its new features.

Thought of that before posting and afraid someone may say “this is a Network/Internet” problem
rotfl!

On 08/10/2014 10:26 PM, michalng wrote:
>
> lwfinger
>
>> You should be able to eliminate any bootup delay when using
>> NetworkManager if
>> you uncheck the “System Connection” box in the Connection Manager. If
>> not, you
>> should report a bug for Factory.
>
> Couldn’t locate the “System Connection”. Maybe because I’m running
> Factory ?
>
>
> robin_listas
>
>> which is why you should have asked in the prerelease-beta forum, aka
>> factory forum, here: because there you have more chances of finding
>> people familiar with factory and its new features.
>
> Thought of that before posting and afraid someone may say “this is a
> Network/Internet” problem
> rotfl!

No matter what subsystem is causing a problem, difficulties with pre-release
systems should be reported in the prerelease-beta forum.

I ran Factory on one of my machines for a while and found wicked to be opaque.
After an upgrade rendered the box unbootable, I switched back to 13.1. I will
try Factory later. Fortunately, I have two alternative partitions for /.

On 2014-08-11 05:26, michalng wrote:

> Thought of that before posting and afraid someone may say “this is a
> Network/Internet” problem
> rotfl!

It is… but one that only happens in factory, because that’s the only
one that has wicked :slight_smile:

I only know of that thing by name, have never met it.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

On 08/12/2014 06:43 AM, Carlos E. R. wrote:
> On 2014-08-11 05:26, michalng wrote:
>
>> Thought of that before posting and afraid someone may say “this is a
>> Network/Internet” problem
>> rotfl!
>
> It is… but one that only happens in factory, because that’s the only
> one that has wicked :slight_smile:
>
> I only know of that thing by name, have never met it.

My expectation is that you won’t like it until 13.3! At least my early
encounters with wicked were not a complete success.

On 2014-08-12 14:36, Larry Finger wrote:
> On 08/12/2014 06:43 AM, Carlos E. R. wrote:

>> I only know of that thing by name, have never met it.
>
> My expectation is that you won’t like it until 13.3! At least my early
> encounters with wicked were not a complete success.

Thankfully, 13.1 will be supported by Evergreen :wink:


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Noticed that I’ve forgotten to update the status here.

Have make a bug report here and the developers had review, resolved and fixed the issue.

If anyone is using Factory here, would be good if you can help to check and confirm if everything is okay now. Thanks.