Bug 30744 - netinstall failure to find or use NET device
Summary: netinstall failure to find or use NET device
Status: RESOLVED DUPLICATE of bug 30535
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 8
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-14 05:14 CEST by Ole Reier Ulland
Modified: 2022-08-14 10:16 CEST (History)
0 users

See Also:
Source RPM: Mageia-8-netinstall-nonfree-x86_64.iso
CVE:
Status comment:


Attachments

Description Ole Reier Ulland 2022-08-14 05:14:15 CEST
When attempting to install Mageia 8 on my Samsung Galaxy Book i7-1165G7 using “Mageia-8-netinstall-nonfree-x86_64.iso”, from an updated mirror 2022-08-10, I was not able to get any network card to work.

The internal WiFi, a very old USB-WiFi and a USB mobile modem, all three resulted in,

"No NET device found."

A USB C-Ethernet adapter resulted in a possibility to select, "enp0s13f0u1c2 (cdc-ncm)". The specs for my USB-C-Ethernet-adapter says that there is a driver for it in the Linux kernel 3.2 and above and that is correct according to my experience with Mageia 8.

But after the installation program was trying to resolve DNS I used the Alt-F3 to show logs. This is what it showed,

* interface enp0s13f0u1c2 doesn't support wireless
* DHCP: sending DISCOVER
* <sleep>
* DHCP: sending  REQUEST
* got gateway 192.168.1.1
* got dns 192.168.1.1
* got dns2 192.168.1.1
* configuring device enp0s13f0u1c2 ip: 192.168.1.100 nm: 255.255.255.0 nw: 192.168.1.0 bc: 192.168.1.255
* 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
* FTP: trying to connect to 192.168.1.51
* FTP: error connect -6
* unsetting automatic

And then in Alt-F1,

Error: failed to connect to remote host.
Comment 1 sturmvogel 2022-08-14 07:51:01 CEST
Your DNS didn't answer. Check your DNS settings/routing.


Seems INVALID.
Comment 2 Manuel Hiebel 2022-08-14 10:16:30 CEST
duplicate

*** This bug has been marked as a duplicate of bug 30535 ***

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


Note You need to log in before you can comment on or make changes to this bug.