Description of problem: Confusing message about network troubles but network actually works. Version-Release number of selected component (if applicable): beta 2 DVD 32bit How reproducible: This happens in Slovene language but probably others too. Steps to Reproduce: 1. boot DVD 2. configure network (wired in my case) 3. click on connect button 4. message says that connection was not successful but it was established already and works fine (for updates)
CC: (none) => thierry.vignaudAssignee: bugsquad => thierry.vignaud
Created attachment 473 [details] First addition of sources
Created attachment 474 [details] Setting up connection type
Created attachment 475 [details] Chosing ethernet card
Created attachment 476 [details] DHCP or not
Created attachment 477 [details] IP settings
Created attachment 478 [details] Connection control
Created attachment 479 [details] Connect now?
Created attachment 480 [details] Wizard done, but connection doesn't work At Beta 2 I got this same confusing message but connection was established in RC it was not.
I tried RC Dual arch CD this time with a little different results. For better report I pictured the process. This time message was the same about connection, but connection itself didn't work. I tried to go back to "Setting up connection type" (sorry for guesing from Slovenian) and connection was established automatically. This could be a workaround but should be at least mentioned in Errata.
Summary: Confusing message about network configuration during install => Trouble with wired network connection during install
Severity: enhancement => normal
Source RPM: (none) => drakx-net
ping?
CC: (none) => marja11
Unfortunately I don't install as much as I did in in the past. But here is recent experience from another PC. I'm installing Mageia 1 Dual arch CD but dd-ed to USB on eee PC 701 netbook. There is still a "confusing message about network troubles but network actually works".
CC: (none) => filip.komar
I tried with Mageia 2 Alpha2 DVD 32bit. Connection didn't work in setup. It didn't even work later. It did when I unchecked "Allow interface to be controled by Network Manager". See attachment 478 [details]. So it seems conected with that. I'll try to verify that.
Thanks for debugging this!
Keywords: (none) => PATCHStatus: NEW => ASSIGNEDCC: (none) => mageiaSummary: Trouble with wired network connection during install => network connection fails during install due to NetworkManager option
Created attachment 1330 [details] disable NM by default while installing (mga#1138) Blino, WDYT?
Attachment 473 is obsolete: 0 => 1 Attachment 474 is obsolete: 0 => 1 Attachment 475 is obsolete: 0 => 1 Attachment 476 is obsolete: 0 => 1 Attachment 477 is obsolete: 0 => 1 Attachment 479 is obsolete: 0 => 1 Attachment 480 is obsolete: 0 => 1
(In reply to comment #13) > Thanks for debugging this! Thanks. I'm grateful user ;). Connection is working but PARTIALLY if I uncheck "Allow interface to be controlled by Network Manager" during install. How partially: I can ping DNS IP but not internet domain names. If I go back to dialog with connection choice and click "Back" it tries to start connection by itself and it then works fully. BTW, I have wired connection to router with PPPoE over "VDSL" router.
NM should not be checked by default during install, that's weird. Thierry: your patch will override the user choice by always disabling NM when writing the file from install
NM is unchecked by default during install. I only wanted to say that if NM is checked network doesn't work at all under any other combination of check boxes. Sorry for not being clear enough. What is strange that it works partially as described in Comment 15.
Created attachment 1347 [details] prevent enabling NM at install time side effect: in order to enable NM, one has to wait rebooting in the installed system. Best way would be to alter /etc/sysconfig/network-scripts/network-functions so that NM_CONTROLLED would not be enabled when DURING_INSTALL is set
Attachment 1330 is obsolete: 0 => 1
Which means we'll need to handle in systemd eventually when shell script will eventually get killed...
CC: (none) => mageia
I found this same issue after a clean install of an x64 system, the problem no long occures NM_Controlled was set to false. Loading dhcpcd manually would also load the network. The defaul choice, dhclient, would not load at all.
CC: (none) => lazerousz
As I was afraid there is another issue connected with this bug. I tried fresh install of M2B2 on HD. Connection is working PARTIALLY during install. I can ping DNS IP but not internet domain names. If I go back to dialog with connection choice and click "Back" it tries to start connection by itself and it then works fully. BTW, I have wired connection to router with PPPoE over "VDSL" router.
but???
(In reply to comment #22) > but??? Sorry Thierry, I don't understand your question. Did you read full comment #21? If install logs are needed to debug this more I can provide them. Would it help if I try loading dhcpcd manually as Andrew suggests in comment #20? I plan another test install. This time will be upgrade with copied /home. I'll report if there will be any difference or new info. I agree that this is not a show stopper because user can update on reboot. Another workaround is already mentioned in comment #21. But in these days we don't expect wired network trouble. Maybe we could mention that on errata?
Sorry your answer was truncated in the email I read and I though your answer wasn't complete
I tried upgrade install of M2b2 but unfortunately it was even worse. NM and all other flags were checked so network didn't work at all. After unchecking NM it was the same as described in comment #21. I also tried with dhcpcd from GUI with the same results.
Unfortunately bug title no longer reflect one left issue: I tried many times unsuccessfully and repeatably with in Mageia 2 Beta3 DVD Europe1. Connection is working PARTIALLY after adding sources in install. I can ping DNS IP but not internet domain names. If I go back to dialog with connection choice and click "Back" it tries to start connection by itself and it then works fully. Unfortunately before downloading updates installer tries to start network again despite that it worked during installation of packages and connection is lost again. Strange thing is that LIVE CD works. I discovered this in dmesg just after message "link is up...": "netlink: 33 bytes leftover after parsing attributes" It seems connected with this issue. Module used is tg3. Network card is: Dell (by Broadcom) / NetXtreme BCM5751 Gigabit Ethernet PCI Express (see attachment 475 [details]).
This bug is still present in the second version of the final dvd iso for Mageia 2.
CC: (none) => davidwhodgins
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
Keywords: (none) => NEEDINFO
(In reply to comment #27) > This bug is still present in the second version of the final dvd iso for > Mageia 2. so 99,999% chance it is still valid
Keywords: NEEDINFO => (none)Whiteboard: (none) => MGA2TOO
Still valid in Mageia3 alpha2: Hitting the checkbutton after configuring the network still creates a very long timeout and then displays a false failed message.
CC: (none) => juergen.harmsWhiteboard: MGA2TOO => 3alpha2 MGA2TOO
Blocks: (none) => 7557
In a discussion in the QA discuss ML, mention was made of two bugs on related issues (both closed now): - #5772 on a false failure report during install WHEN A NEW ONLINE MEDIUM is declared - #5830 on a false failure report BY DRAKCONNECT WHEN AT INSTALL-TIME NO NETWORK HAD BEEN AVAILBLE. #1183 is on the failure of the network test during installation WITH AN AVAILABLE NETWORK CONNECTION AT THAT TIME. The initial description of the present bug does not explicitely mention that the system is connected to a network while the install is going on, but the comments make clear that this is the case. And I confirm, I have this problem with an active network connection during install (and the system boots immediately after install with a fully functional network interface configured). I think to remember that this problem has been observed by other users and discussed in the forum, but forum search is at present not available.
It is working for me with Mageia3Alpha2 Test Procedure - Using MGA3A2 DVD - i586, boot in VBox After partitioning stage when asked is additional media available select ftp. After installing base software network dialogue appears. Regardless whether the NM checkbox is selected or not, the network test succeeds without a delay. 2nd Test - Using MGA3A2 DVD - i586, boot in VBox Complete install without declaring additional media and at the Summary near the end of installation select 'Network-Configure' Select the NM checkbox in the network dialogue. Once again network test succeeds without a delay.
CC: (none) => derekjenn
This problem evidently happens on some machines and on some others not. I reproducibly have the problem on my x86-64 Dell desktop (a fast dual-core machine). The problem is not present on my Dell D820 laptop, a rather slow i586 machine. Will tomorrow install Alpha2 on the i586 machine of my wife and post the result.
Please refer to the discussion in bug#7873 and bug#2160 and see if your problems with NM go away if you either allow GNOME (if you have it installed) to activate it or you install plasma-network-management under KDE, add it to your panel, and use it to configure your SSID. For NM to handle wireless correctly, it needs to create SSID-specific files of its own by parsing the ifcfg files produced by drakconnect. GNOME's nm-applet does this automatically, since it has no option to *not* use NM, but since NM isn't the default yet for other desktops, it doesn't happen automatically there. You'll need to install NM and let it start, and recreate your wireless interface with drakconnect specifying "Allow NM to control this interface". Please test and post your results, as whether NM works for all the chips involved when it's properly configured will have a significant impact on how it needs to be handled for non-GNOME desktops in MGA3.
(In reply to comment #34) n/a here.
CC: (none) => ftg
Taking this as a reminder: I have now also installed Alpha 2 on my fast x86-64 desktop (wired ethernet, fixed IP address. Result: the network comes up smoothly, the problem is not there any more. For me, the problem has been resolved sometime during Alpha2 development. Re comment #34: n/a here
(for filip)
I tested Mageia-3-alpha3-i586-DVD once and unfortunately I still experienced ONLY PARTIALLY working connection during install. I can ping DNS IP but not internet domain names. There is a change in the install process as it's not possible to select type of connection again when going back. Before downloading updates installer tries to start network again but IIRC without success. I'll try some more and report. BTW on both LIVE media network worked as expected.
I happen to precisely look at this issue when I installed Alpha3 x86-64 on a Dell Latitude 6530: works like a charm. For me, the problem has been solid in the past and now has gone away. Is it possible to get more evidence on the specific environment that makes the difference between working and not working?
Clean install of Mageia-3-i586-DVD.iso didn't showed such symptoms so I'm closing this bug as no one seems to experience it.
Version: Cauldron => 3Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED