i can’t reliably rely on netinstall due to this consistent connect/disconnect of a wired internet. other live iso works fine. Using calamares with debugging enabled, i can see message related to this network instability shows up each times the New Connection notif pops-up:
this is happening on the new live iso, as well as the older one. Rebuilding the ISO does not do anything to remedy this.
Could you tell us which distro’s with an online installer do work and could you give us your hardware info?
We had bug reports about the ISO connecting to faulty mirrors, but you’re the first one with a network connection problem, making me think this could be hardware related.
ArcoLinuxB/D, ArchLabs, Antergos, Manjaro Architect, Debian, if it counts, arch’s iso. Its not just about able to use netinstall, the live iso should not have this constant network disconnect/connect issue. Any other live iso installer has no problems using the net including antiX, MX-Linux, Solus, openSuse etc.
As I said before, it’s the first time we had a report of this bug, 99% of our users, several vloggers and bloggers do have a stable network connection on the ISO.
It’s not that I don’t believe you, but we’re happy to look into it and if we don’t find the issue, please don’t be mad, apparently, you’ve found an abundance of choices for your hardware to get into Linux. And that’s what counts.
im not implying any feelings of being mad here, im just stating the issue coz this is new for as well and only happens with this ISO and to clearly send the message that this is not an install/mirror issue like what people experience on Antergos before. the Live ISO itself is connecting/disconnecting the network as seen on the screenshot counter. I can install arch manually fine, but do not have idea about the live ISO other than building it from prebuilt instructions.
i do only try to research if there is a known issue with this device or driver under Archbased… simple to see if there is a workaround to get the issue solved.
I believe Joe is simply trying to gather information in search of a solution. Sometimes the multicultural nature of this forum, and others, lends itself to communication glitches. People of different backgrounds and native languages all writing in English will occasionally come across as abrupt when that is not what is meant at all. Joe was not writing off your problem, but rather sharing what info he has so far. If there is a final solution to what you are experiencing (or a workaround) someone on this forum will be able to look at everything gathered and find it. There is a lot of brain power and knowledge here
I would need some logs to see if there was something failing for the device, and this is how we do work.
We need the community to report issues to help with testing solutions and then we can integrate this into ISO.
This is what we got shipped with current kernel:
Could be it was selecting wrong driver as there is no 8111/8168/8411 only r8169
So to test you could install r8168 driver and load the modules: