http://bugzilla.opensuse.org/show_bug.cgi?id=1206611 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Network |Installation Assignee|screening-team-bugs@suse.de |yast2-maintainers@suse.de QA Contact|qa-bugs@suse.de |jsrain@suse.com Severity|Critical |Major -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1206611 http://bugzilla.opensuse.org/show_bug.cgi?id=1206611#c5 --- Comment #5 from Joed L <jlopez777+opensuse@gmail.com> --- (In reply to Imobach Gonzalez Sosa from comment #4)

Hi Joed,

OK, I see. You do not have an editor because the installation media is not fully loaded (because of the failing network configuration). You are still in Linuxrc, which is responsible for initializing and loading the installation image.

How are you trying to set up the network? Which arguments are you passing when booting? In theory, you should not need an editor to set the configuration values (you can specify them when booting). Additionally, you have the "ip" and "wicked" commands to inspect the current status of the network.

Regards, Imo

What makes this odd is that I have to is ip command to get the network device to "turn on". Then I get an RFKILL error. I hit the "airplane mode" button on my laptop and then do the ip command to initialize the device, and it goes through. Not sure if the pressing of the button is actually the thing that works, or if it is just some time has to pass for the network device to initialize for it to work. THEN i can connect to tumbleweed repos.....but then I am told, I need to download a new boot image before moving forward....I do so, and NOW, the device that I got to turn on is working, and only lo network device is showing, but not activating or connecting....so now, i dont get a dhcp failure, I get "no network device or module loaded". I cant recall which one, but either way, unable to connect. I gave up and ended up installing via graphical installer w a bigger usb , but I was intrigued by this issue, and wanted to learn/find the underlying issue, in the event someone else had same issues. NEXT STEPS: I can maybe try again with an updated network installer? Is it possible to include vim in the network installer for such a time where going in and changing config files could actually help? Another might be include nmtui with the network installer so some of the network config can be done in a cleaner manner? I know the above isnt directly related w the issue, but these are some of my "findings" on the road in trying to solve this....is that out of the question to consider? Just wondering....thanks for your responses. -- You are receiving this mail because: You are on the CC list for the bug.