Bug 15495

Summary: MGA5 B3 gives ethernet and wireless eth0 and eth1 names during install which is wrong
Product: Mageia Reporter: w unruh <unruh>
Component: InstallerAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: eatdirt, mageia, marja11, thierry.vignaud
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard: NEEDINFO
Source RPM: CVE:
Status comment:

Description w unruh 2015-03-15 08:14:47 CET
Description of problem:
Installing MGA5 B3 when it asks to set up the network, it gives the wired and wireless the wrong names-- eth0 and eth1, when they shoulc be the new incomprehensible names like etp20s05  wlp10s15 (those are made up as I cannot get at the machine right now.) which means that the network does not come up during the install. When I rebooted, both networks came up without problem. 

The network cards are a Diamond usb3-GBethernet and a Broadcom wireless which needs the wl driver (which I had to install by hand from the console in order to get wireless working)
Dell XPS 13 computer. 



Reproducible: 

Steps to Reproduce:
w unruh 2015-03-15 08:15:34 CET

Summary: MGA5 B3 gives ethernet and wireless eth0 and eth1 names which is wrong => MGA5 B3 gives ethernet and wireless eth0 and eth1 names during install which is wrong

Comment 1 Marja Van Waes 2015-03-15 09:55:04 CET
(In reply to w unruh from comment #0)
> Description of problem:
> Installing MGA5 B3 when it asks to set up the network, it gives the wired
> and wireless the wrong names-- eth0 and eth1, when they shoulc be the new
> incomprehensible names like etp20s05  wlp10s15 (those are made up as I
> cannot get at the machine right now.) which means that the network does not
> come up during the install. When I rebooted, both networks came up without
> problem. 

You say "the network does not come up", do you mean only WLAN doesn't come up, or should it have been plural, and did LAN not come up, either?

CC: (none) => marja11
Whiteboard: (none) => NEEDINFO

Comment 2 Marja Van Waes 2015-03-15 10:10:09 CET
If it was a traditional install, then please attach /root/drakx/report.bug.xz from that install, too.
Comment 3 w unruh 2015-03-15 16:38:33 CET
Neither ethernet nor wireless came up. 

It was a uefi install from usb flashdrive. I have now reinstalled about 4 times (long story, and fortunately with usb3 flashdrive and SSD disk, it only took 10 min each time) and did not even try to setup networking after that first time. 
If I do it again, I will send that report.
Comment 4 Thierry Vignaud 2015-03-16 10:25:25 CET
Please attach your /root/drakx/report.bug.xz

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

Comment 5 Colin Guthrie 2015-03-16 17:07:51 CET
Hmm, I thought this may have been due to the udev rule change thing, but that was added back in 51fef84dd2af00f92eab1de78cff31326a18a4dc (August) so shouldn't be an issue here.
Comment 6 David Walser 2015-03-17 20:41:39 CET
This seems to contradict Bug 12316, which says that the installer will use the new consistent naming scheme, but this bug says that it won't.  Which is it?
Comment 7 w unruh 2015-03-17 21:26:31 CET
I do not know. All I did was to report what I saw. And the network did not come up on installation and it used eth0 and eth1 during installation, but it did come up on reboot, together with  the new naming scheme. Unfortunately I have reinstalled about 3 times thereafter, but never bothered with even trying to enable networking during installation, having failed the first time so have no record of that first installation.  It could have been some peculiarity of my system, or of his system. Also his (12316) was for MGA4 RC and mine was for MGA5 B3. It is also unclear as to exactly when he saw the eth0 type names, whether during installation or during bootup. He clearly saw both the new and old style names at different times, which is what I also saw, and what we should not see. While I think the the new style name are a real pain (why does the user need to know the details of the hardware), Mageia has drunk the Kool-aid and should consistently use the new names.

I have so many other problems installing Mageia (graphics, grub-efi, trackpad, sound) on this machine, that redoing the installation is not high on my list of priorities, even if it does just take 15 min. (SSD disks are amazing as are usb3 flash drives:-)
 Note that in response to Thierry-- I reinstalled a number of times before he asked for root/drakx/report.bug.xz without even trying networking during install again, that the latest report.bug.xz will not be of any help I assume. If one where I did not even try to bring up networking could be helpful, I will gladly upload it.
Comment 8 Chris Denice 2015-03-18 08:23:04 CET
Dear Bill,
could you specify more exactly what is your laptop, I may have exactly the same model so I can try to reproduce that bug. Is that the xps 13 coming with ubuntu pre-installed?

thanks,
cheers.

CC: (none) => dirteat

Comment 9 w unruh 2015-03-18 17:03:52 CET
It is the 9343 -- early 2015 model of the XPS13 with HD graphics. Dell has announced that it will be shipped Ubuntu when they have worked out the Linux kinks from it. (Trackpad, sound, graphics). I have installed both Mageia 5B3 and fedora 21 on it-- mainly using Mageia.
Comment 10 Chris Denice 2015-03-29 18:18:59 CEST
Thanks, mine is the version just before (and works very fine with linux). It seems that this Dell release is pretty bad in terms of linux support and various other bios bugs. I guess you may find some help there too

https://major.io/2015/02/03/linux-support-dell-xps-13-9343-2015-model/

I like that one way to fix the sound is to pass acpi_osi="Windows 2013" at boot (it means what it means)... :(
Comment 11 Samuel Verschelde 2015-06-06 00:52:54 CEST
(In reply to w unruh from comment #7)
> I have so many other problems installing Mageia (graphics, grub-efi,
> trackpad, sound) on this machine, that redoing the installation is not high
> on my list of priorities, even if it does just take 15 min. (SSD disks are
> amazing as are usb3 flash drives:-)

You can either provide the needed information (when you can) or close this bug as wontfix, since nothing will happen without debug information. Marking the bug as NEEDINFO for now.

Keywords: (none) => NEEDINFO

Comment 12 w unruh 2015-06-06 01:21:58 CEST
Sorry. Can't reinstall It is being used by my son 5000 miles away right now. 

I did do an install of MGA 5 rc on an older Panasonic S10 and did not notice any problems, so perhaps the problem has been fixed by now-- or it was a peculiarity of that other system.
Comment 13 Samuel Verschelde 2015-06-06 01:26:24 CEST
It was probably a peculiarity of that other system. Let's close it for now, you can still reopen if you see it again in the future.

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