The error message about the "broken module" would probably help.

CC: (none) => boklm

I'll boot it again then.

NET: was expecting another network interface (broken net module?)

attach the file /root/drakx/report.bug.gz as an attachment

Keywords: (none) => NEEDINFO
Source RPM: Net-based installation iso => drakx-installer

This issue keeps following me around in every installation now no matter what kind of iso I use.

Version: Cauldron => 1

Created attachment 999 [details]
Here's the requested report-file

Created attachment 1012 [details]
dmesg-output

Note that I've also tested an external USB wireless adapter after installing rt73-firmware & that didn't help to.

I see the solution lies in this:

Do rfkill list & see if your wlan0-interface is both software & hardware-blocked.

Then you do rfkill unblock 0

Do rfkill list again & see that the wlan0-interface is now only hardware-blocked

Now do rfkill unblock all

Do rfkill list & voila! The wlan0-interface isn't blocked in any way anymore.

Your fist comment was about stage1, I'am not sure that wifi can work at this stage. And now you speak about rfkill ? That is AFTER the install no ?

Source RPM: drakx-installer => drakx-installer-stage1

Yes, but I think the rfkill-issue is already active when you start the initialization of the 1st stage.

Bug report is bogus, should be closed as invalid from what i can see after an 2-hours wireless troubleshooting session on IRC. This is not working in a full installation, because the wireless adapter can't even see the AP, so this can never work in either stage1 or stage2, IMHO.

CC: (none) => doktor5000

Well, I can see other connections & therefor I'll object to this.

other connections = other APs? If yes then on what channel is the AP you want to connect?

CC: (none) => sander.lepik

(In reply to comment #13)
> Well, I can see other connections & therefor I'll object to this.
after the install ?

(In reply to comment #15)
> (In reply to comment #13)
> > Well, I can see other connections & therefor I'll object to this.
> after the install ?

Yes.
When I used rfkill to unblock all devices.

(In reply to comment #14)
> other connections = other APs? If yes then on what channel is the AP you want
> to connect?

Channel? Doesn't AP mean Access Point which in this case is my router?

Yes, but which channel is your router using? you need to have some channel for wifi.. If it's above 11 then it's quite possible that your computer might not see it.

Anyway closing as invalid

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Please don't close it until we've found the cause of this issue that's valid in stage 1 of the installer & when you've installed Mageia.

(In reply to comment #18)
> Yes, but which channel is your router using? you need to have some channel for
> wifi.. If it's above 11 then it's quite possible that your computer might not
> see it.

Do you know how to find that channel in the router?

My router is a DIR-825 from D-Link.

I do know how to login to my router so the only thing I need to know where I can find what channel it's using.

You could look it up in the documentation for the router, this is what it should look like: http://support.dlink.com/emulators/dir825/113NA/Device_Info.html

Scroll down to Wireless LAN and look for Channel:

(In reply to comment #23)
> You could look it up in the documentation for the router, this is what it
> should look like:
> http://support.dlink.com/emulators/dir825/113NA/Device_Info.html
> 
> Scroll down to Wireless LAN and look for Channel:

It says Channel: 3

(In reply to comment #24)
> (In reply to comment #23)
> > You could look it up in the documentation for the router, this is what it
> > should look like:
> > http://support.dlink.com/emulators/dir825/113NA/Device_Info.html
> > 
> > Scroll down to Wireless LAN and look for Channel:
> 
> It says Channel: 3

That's for 2.4GHz band.

For 5GHz band it says Channel: 161

D'oh! Didn't you say you know how to login to YOUR router?

I just posted a link to a demo installation of the web frontend for documentation purposes of your router model to show you where to look. In YOUR router.

(In reply to comment #26)
> D'oh! Didn't you say you know how to login to YOUR router?
> 
> I just posted a link to a demo installation of the web frontend for
> documentation purposes of your router model to show you where to look. In YOUR
> router.

Well, I didn't know exactly where to look for such setting when I've logged in.

Just booted the Remix Live-edition of Ubuntu 11.10 & I have no issues connecting to my wireless-connection there.

This is the link to the Remixed Live-edition of Ubuntu that I'm trying: http://home.danielnylander.se/ubuntu/11.10/ubuntu-11.10-nordic-remix-desktop-amd64.iso

This is output of iwconfig in Ubuntu just to show the difference to Mageia:

wlan0     IEEE 802.11bg  ESSID:"Kristoffer"  
          Mode:Managed  Frequency:2.417 GHz  Access Point: 00:26:5A:F4:11:0D   
          Bit Rate=48 Mb/s   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=70/70  Signal level=-37 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:35   Missed beacon:0

Output of dmesg | grep 80211 in Ubuntu-version is this:

http://pastebin.com/n5h8ft2j

Comparing the dmesg output from ubuntu to the one from mageia it seems on mageia it sets it to SE regulatory domain, but not for ubuntu and the 80211 / CRDA output is slightly different.

But still you did not post which channel your router runs on.

(In reply to comment #32) 
> But still you did not post which channel your router runs on.

I believe I did that in Comment 24.

You posted what the demonstration router shows in the documentation. You tell that your router at home runs on the exact same channels as the one in the dlink documentation?

(In reply to comment #34)
> You posted what the demonstration router shows in the documentation. You tell
> that your router at home runs on the exact same channels as the one in the
> dlink documentation?

Yes, I do.

The issue has been reported several times in Ubuntu with any of the 2.6-kernels:

https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=Atheros+AR5001&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=

There seems to be a solution ready if you take a look at this thread about the same issue, but for similar HP Compaq Presario CQ60-models that has the same Atheros Wireless-card in them.

(In reply to comment #36)
> The issue has been reported several times in Ubuntu with any of the
> 2.6-kernels:
> 
> https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=Atheros+AR5001&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
> 
> There seems to be a solution ready if you take a look at this thread about the
> same issue, but for similar HP Compaq Presario CQ60-models that has the same
> Atheros Wireless-card in them.

Here's the possible solution to adapt to Mageia's installer somehow:

http://ubuntuforums.org/showpost.php?p=11093401&postcount=10

Adjusting URL field as there is already a Mandriva bug report about the same issue.

URL: http://ftp.nluug.nl/pub/os/Linux/distr/mageia/distrib/cauldron/x86_64/install/images/boot.iso => https://qa.mandriva.com/show_bug.cgi?id=61033

Created attachment 1030 [details]
Here's all info from running the Live-version of Ubuntu to see what the difference is that makes it work

(In reply to comment #38)
> Adjusting URL field as there is already a Mandriva bug report about the same
> issue.

There reason for two reports for the same issue is to prove that this has followed me to Mageia as well.

Reopning this bugreport again since this problem appears after reboot.

You have to do the solution again to make it work.

Status: RESOLVED => REOPENED
Resolution: INVALID => (none)

I got this issue in my stationary computer now as well.

The fix works, but I get the same error again when I reboot the kernel.

This is what I do in Terminal:
[root@localhost ~]# rmmod -f rt73usb
[root@localhost ~]# rfkill unblock all
[root@localhost ~]# modprobe rt73usb
[root@localhost ~]# ifup wlan0

Determining IP information for wlan0... failed; no link present.  Check cable?

Now I go to create a new interface for wlan0 & filling in the credentials needed for my network:

[root@localhost ~]# drakconf
[root@localhost ~]# "/usr/bin/drakmenustyle" is not executable [Menus] at /usr/sbin/drakconf.real line 822.
"/usr/sbin/drakbackup" is not executable [Backups] at /usr/sbin/drakconf.real line 822.
"/usr/sbin/drakvirt" is not executable [Virtualization] at /usr/sbin/drakconf.real line 822.
"/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/sbin/drakconf.real line 822.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Gtk-CRITICAL **: gtk_cell_view_set_cell_data: assertion `cell_view->priv->displayed_row != NULL' failed at /usr/lib/libDrakX/interactive/gtk.pm line 522.
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory
Reloading vnstatd configuration:                                      [  OK  ]
Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlan0 ; Invalid argument.
Väntar på att nätverket är uppe                                       [  OK  ]

If I delete the eth0-interface & set the wlan0-interface to load at systemstart it works perfectly. So is the issue in initrd or someplace else?

@ Florian,

Reading and trying to understand the above 43 comments to find out if there is anything Bug Squad should do with this bug, is going to take me a lot of time. 

I see you already know a lot about this bug report, so it would probably take you less time. Do you mind helping?

Is the required information there?
Is it a valid bug?
Is drakx-installer-stage1 the correct culprit?

We don't seem to have a drakx-installer-stage1 package, btw, but I think I've seen a drakx-installer-stage1 bug being assigned to blino, so cc'ing him.

@ blino

Are you the maintainter of drakx-installer-stage1 and if so, what is the proper name of that package?

CC: (none) => marja11

(In reply to comment #44)

> 
> We don't seem to have a drakx-installer-stage1 package, btw, but I think I've
> seen a drakx-installer-stage1 bug being assigned to blino, so cc'ing him.
> 
> @ blino
> 
> Are you the maintainter of drakx-installer-stage1 and if so, what is the proper
> name of that package?

And now really cc'ing Olivier

CC: (none) => mageia

(In reply to comment #44)
 
> Is the required information there?
> Is it a valid bug?
> Is drakx-installer-stage1 the correct culprit?

Well, the current bugreport mangles multiple seperate issues, and is therefore not valid, IMHO.

First, it's about wireless setup during installation (which is not supported currently) another is about rfkill behaviour, and another one would be about the wireless setup in general, but seems this is more a PEBKAC problem from what i can tell, as other users had no problem getting their wireless working with the same adapter/driver being used.

(In reply to comment #46)
> (In reply to comment #44)
> 
> > Is the required information there?
> > Is it a valid bug?
> > Is drakx-installer-stage1 the correct culprit?
> 
> Well, the current bugreport mangles multiple seperate issues, and is therefore
> not valid, IMHO.
> 
@ Florian

Thanks a lot!


@ Kristoffer

Sorry, this isn't a valid bug report, so I must close it. 

TBH, I had already spend some time on it yesterday and this morning, but the report confused me. I wasn't aware the separate issues caused the confusion, so I'm really glad Florian pinpointed that.

Please don't open this report again

Status: REOPENED => RESOLVED
Resolution: (none) => INVALID