@ Wobo,

sorry it took us so long to respond.

Did you have a chance to install Mageia 2 Alpha 1? If so, was the issue still there?

CC: (none) => marja11, thierry.vignaud

No, I have not tested Alpha 1 on that machine.

CC: (none) => molch.b

(In reply to comment #2)
> No, I have not tested Alpha 1 on that machine.

@ wobo

If you get a chance to test (on Mga 2 alpha 1 or a newer version), please insert a USB key and run "bug" from tty2 during install and attach the resulting report.bug here

@ me
TODO: Test Alpha 1 (or 2) on a laptop with detached network cable, and run "bug"

@blino: maybe are we missing some files for wifi in installer?

CC: (none) => mageia

 (In reply to comment #3)
> 
> If you get a chance to test (on Mga 2 alpha 1 or a newer version), please
> insert a USB key and run "bug" from tty2 during install and attach the
> resulting report.bug here

Sorry for the questions:
How does 'bug' know which device to store the report to? I'm installing from one USB key, the other one should receive the report. Did not find a man page for 'bug'

Just try it, it'll ask you...

Ah, I was too fast at first try, the system was not ready for "bug" yet. :(

Ok, same as described, although I used a x86_64 now. To reproduce:

1. Installation from DVD - standard KDE install

2. In the summary click on configure for network connection, select wifi

3. The following window shows the correct chip (Atheros) for device wlan0 but then no networks are detected. Filled in all data (managed, WPA, password, start at boot), then started the test.

Result: system tells me "An error occured".no connection.

After reboot the connection comes up! 

More testing shows a possible explanation:

I did a text-only installation (without X), experiencing the same problem. Doing this on a terminal I could see a bit more detailed output: the password encryption did not work!
The cause here was that drakx-net (or drakconnect) tried to start the connection but did not start wpa_supplicant daemon before, so the connection to the WPA-secured network failed. I started the daemon manually and 'ifup wlan0' was a success. At reboot the wpa_supplicant daemon is started anyway and consequently wifi came up fine.

What I can not explain: why there were no networks available in the first installation.

Do you still need the report.bug? I did not find anything non-standard there.

No, your debugging should be enough

assigning

Assignee: bugsquad => mageia

It might have been fixed in cauldron with drakx-net 1.0, and in the installer if it has been rebuilt with new drakx-net.
Previously, wrong NM_CONTROLLED settings would have been written in ifcfg config files.
Is it still valid?

I have that bug too with the last mageia cauldron alpha dvd iso 64bit at the install.

The graphical installer can't detect network because there's no ifconfig up on the wlan0 after the module have been loaded.

i can do a ifconfig up into the console, and so a iwlist wlan0 scan show all available network.

After, i try to manually configure one (wpa2 psk), but it can't connect.

My card is a 05:00.0 Ethernet controller: Atheros Communications Inc. AR8151 v2.0 Gigabit Ethernet (rev c0), but i don't think it's the problem ;)

++
hurdman.

CC: (none) => yves

I've submtited a potential fix in drakx-net 1.2
A new installer has to be rebuilt for that.

Status: NEW => ASSIGNED

Thanks for the rebuild Titi

Just to revive this: bug still valid in Mageia 2 Beta 1

Please attach new log from beta1

Keywords: (none) => NEEDINFO

See comment #7 - nothing has changed.

The code has changed so we need to see the new logs. Same result doesn't mean the cause hasn't changed

Ok, now I'm confused, which log do you mean? I never provided a log of which you now want a new version - last time you wrote "your debugging should be enough".

Ah, maybe you mean the "report bug" - i did that but only wrote that there was nothing related in there.
I'll see if I can find the time to do a new installation.

We cannot do anything without those logs.
You may think there's nothing related but we may see interesting things.

Created attachment 1731 [details]
Created by 'bug' during installation

Added attachment #1731 [details] is a report of installation from Beta1 x86_64 DVD.

From the summary I configured wifi connection. The atheros chip was recognized, available networks were recognized. After giving the necessary data (password, etc.) the connection was to be started but failed.

After reboot wifi is available.

We need the logs _after_ you tried to set up the network...

And how do I get these? I let the usb key which was set up with 'bug' attached until I rebooted after installation, so 'bug' was active while and after wifi setup.

If there are no usable info in that attachment, I need a different way to get that log you need.

bug is a one time command that, when run copy the logs to the USB key.
Then it exits and you've your shell again.
So you must run "bug" after having tried to set up the network, let's say, when the installer offers to apply updates or when it offers to reboot

Ah, I misunderstood 'bug' to write a log during the whole process - because at the end when I shutdown for reboot the system says "closing log".

Ok, will give the command after I tried to setup wifi and get the message that "Connection fails".

Attaching now a report done after configuration. Relevant lines for wifi setup start at line #17,552.

Unfortunately the report.bug file is too large for an attachment. I uploaded it to ftp://ftp.mandrivauser.de/rpm/report.bug

Blino: hum, despite having udev installed we see:

* running: /lib/udev/write_net_rules 78:e4:00:50:12:ea with root /mnt
* program not found: /lib/udev/write_net_rules

Not dramatic but...

But this:
* running: /sbin/ifup wlan0 with root /mnt
Wireless device wlan0 is configured with a roaming daemon but isn't associated

Determining IP information for wlan0... failed; no link present.  Check cable?
matchbox-wm: X error warning (0x280a1a): 155 (opcode: 144)

blino: http://forum.mandriva.com/en/viewtopic.php?f=171&t=137296 suggests we should do a service network start first

More seriously, https://qa.mandriva.com/show_bug.cgi?id=61004 suggests running "rfkill unblock wifi wlan"

I may point back to my comment #7 where I did a no-X installation and wrote:

"The cause here was that drakx-net (or drakconnect) tried to start the
connection but did not start wpa_supplicant daemon before, so the connection to
the WPA-secured network failed. I started the daemon manually and 'ifup wlan0'
was a success."

It is probably because of this $::isInstall check in network::tools :

sub run_interface_command {
    my ($command, $intf, $detach) = @_;
    my @command =
      !$> || system("/usr/sbin/usernetctl $intf report") == 0 ?
        ($command, $intf, if_(!$::isInstall, "daemon")) :
        common::wrap_command_for_root($command, $intf);
    run_program::raw({ detach => $detach, root => $::prefix }, @command);
}

The code was never written with the goal to have wifi with WPA running during install.

I don't think that enabling ifplugd would work during install.
We could try to enable it between RC1 and RC2.
Any volunteer to test that?

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Created attachment 2391 [details]
executed after trying to get updates in last screen of installer

This is still valid, nothing changed.

Machine: x86_64
Wifi chip: Atheros AR9285 (Man.ID: 0x168c, Dev.ID: 0x002b, module: ath9k)
Medium: DVD

2 installations:
 - Gnome with standard installation
 - KDE with standard installation

I get the exactly same results: problem when trying to start the connection after configured, wifi working after reboot.

I said "yes" to the offer to install updates in the installer and after the installer returned to the next screen I did "bug" to an usb stick. 

Added as attachment

Thanks, wobo :)

Keywords: NEEDINFO => (none)
Whiteboard: (none) => MGA2TOO

Problem confirmed also with an ath9k chipset (Mageia 3 beta1).

CC: (none) => reinout

As M2 will not be fixed, please cbange whiteboard to e.g. 5beta1 or close?

Keywords: (none) => NEEDINFO

I haven't heard complaints about this in a long time, closing as fixed.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

But I misread the summary.... this is about during installation, not about after....... tbh, I did hear complaints about *during* install, and I haven't tried in a long time. Changing to closing as OLD, because this bug saw no real activity in a long time

Resolution: FIXED => OLD