Well, the virtualbox e1000e is emulated, so it does not exactly match as comparisation.

And as manual ip does not work either, there is some other problem there...

What does lspcidrake -v (or lspci -vnn) sany for that card.

And do you see any errors on screen if you press Alt-F2 or Alt-F3 ?

CC: (none) => tmb

Ok,
I used system-rescue-cd to do lspci -vnn it shows;

00:19.0 Ethernet controller [0200]: Intel Corporateion 82567LM Gigabit Network Connection [8086:10f5] (rev 03)
        Subsystem: Lenovo Device [17aa:02ee]
        Flags: bus master, fast devsel, latency 0, IRQ 45
        Memory at fc200000 (32bit, non-prefetchable) [size=128K]
        Memory at fc225000 (32bit, non-prefetchable) [size=4K}
        I/O ports at 1840 [size=32]
        Capabilities: [c8] Power Management version 2
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [e0] PCI Advanced Features
        Kernel driver in use: e1000e
        Kernel modules: e1000e



Alt+f3 shows;

Total Memory: 134217728 Mbytes
PCI: device 8086 10f5 17aa 20ee is "Intel Corporation|82567LM Gigabit Network Connection", driver is e1001e
have to insmod e100e
found net interface lo, but blacklisted
      succeeded e100e
found net interface eth0
found net interface lo, but blacklisted
NET: alias eth0 e1000e
found net interface eth0
found net interface lo, but blacklisted
have to insmod af_packet
      succeeded af_packet
interface eth0 doesn't support wireless



after I try for DHCP it says this,

DHCP: sending DISCOVER
<sleep>
<sleep>
<sleep>
<sleep>
<sleep>
<sleep>
<sleep>
unsetting automatic



after that I try static IP this is what it says,

Total Memory: 134217728 Mbytes
found net interface eth0
found net interface lo, but blacklisted
interface eth0 doesn't support wireless
guessing netmask
configuring device eth0 ip: X.X.X.X nm: X.X.X.X nw: X.X.X.X bc: X.X.X.X
reverse name lookup on self failed
reverse name lookup on DNS failed
using hostname
using domain
configuring device lo ip: 127.0.0.1 nm: 255.0.0.0 nw: 127.0.0.0 bc: 127.255.255.255
HTTP: connecting to server mirrors.mageia.org:80 (no proxy)
getaddrinfo: unknown host

HTTP: unable to get mirrors list from mirrors.mageia.org (/api/basic.3.x86_64.list)





I also just tried to do an install of Mageia 2 using the boot-nonfree.iso and it works just fine.

Oh yeah and that is the alt+f3 from trying install of Mageia 3 beta 4 boot-nonfree.iso

Thanks for looking into this and let me know if there is any other info you need from me.

I have just run a test with a Lenovo T60 notebook and it is able to install Mageia 3 beta 4 using boot-nonfree.iso

I have also tried it on my custom built desktop machine with a Gigabyte 990FXA-UD3 motherboard and it is also able to install just fine.

I've just run a test with Mageia 3 RC boot-nonfree.iso on my Lenovo T500 and it is getting the same result as with Beta 4

*** Bug 10156 has been marked as a duplicate of this bug. ***

2 reports on the same hw => this suggests a driver issue => kernel (regression since mga2°.
Does the live CD succeeds in bringing up the network?
Does the network work if installing using the install DVD (not performing a network install)?

Keywords: (none) => NEEDINFO
Source RPM: (none) => kernel

Tested with Mageia 3 LiveCD KDE4 en 32bit
Results: Boots ok and has working Network.

Tested with Mageia 3 dual CD
Results: Boots ok and installs fine. Network is working post install.

It's just the network installer that seems to have this problem.

but in dual, does the network during the install ? like for downloading xml for online repo

Strange. Can you attach the /root/drakx/report.bug.xz from this late install?

I have done another install using Mageia 3 dual CD
This time I set up repo's at the beginning and installed KDE all went fine and it has working network post install.

Created attachment 4020 [details]
report.bug.xz from install 2013-05-21 using Mageia 3 Dual CD

Actually it's still only one report.

Can you locally rebuild the drakx-installer-images with %debug set to "1"?
See http://svnweb.mageia.org/packages/cauldron/drakx-installer-images/current/SPECS/drakx-installer-images.spec?revision=413545&view=markup
Then could you use the boot.iso from this newly build packages in order to get more data?
Just try again to do a network install. But now you'll get a shell on second console (tty2).
Can you try to get the whole dmesg output on some usb key or hard disk?

I've never dealt with a .spec file before. I found the section for %debug 1 but I do not know how to "rebuild" from this file. Just point me in the right direction and I will get you this info.

some links https://wiki.mageia.org/en/Drakx-installer_tips_and_tricks#rebuild_the_stage_2
(with one for rpm doc)

Looks like requested info is not forthcoming.

Please confirm if this applies to current installer (5beta1 or higher), because sorry to say older installers cannot be fixed.

If yes, please set whiteboard to '5beta1' (or higher) and wipe 'NEEDINFO'.

Alternatively -  it is regretted but - this must be closed "resolved" as 'OLD'.

(In reply to Dick Gevers from comment #16)

> 
> Alternatively -  it is regretted but - this must be closed "resolved" as
> 'OLD'.

Almost three years later: there was no more action in this report, so it seems no one hit this issue in a more recent Mageia release, and the requested information was not supplied. 

Closing as OLD.

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