[Bug 899895] New: NET install using .iso of snapshot 20141004 can not be used with WiFi
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 Bug ID: 899895 Summary: NET install using .iso of snapshot 20141004 can not be used with WiFi Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: freek@opensuse.org QA Contact: jsrain@suse.com Found By: --- Blocker: --- Copied openSUSE-Factory-NET-x86_64-Snapshot20141002-Media.iso to a USB stick and tried to use it on a new laptop with EFI. The system boots from the USB stick, but later I get in an old fashioned type of screen the message: Please make sure your installation medium is available. Retry? I have to select No to continue. Still in these old fashioned screens I can configure access to the WiFi network, but it does not work. There is no option to scan the WiFi network, but I know the SSID. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 Freek de Kruijf <freek@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|NET install using .iso of |NET install using .iso of |snapshot 20141004 can not |snapshot 20141002 can not |be used with WiFi |be used with WiFi -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 Neil Rickert <nrickert@ameritech.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nrickert@ameritech.net --- Comment #1 from Neil Rickert <nrickert@ameritech.net> --- I see the same thing with snapshot 20141001. My comment to bug 888130 was about this. I have just retried, with the same results. I did go through the network setup step, giving the SSID and passphrase for the network. There are no yast logs. "/var/log/YaST2" is empty. The file "/etc/sysconfig/network/ifcfg-wlp18s0 contains only: BOOTMODE="dhcp" STARTMODE="auto" In particular, there is nothing WiFi related in that ifcfg file. wpa_supplicant.log reports "Successfully initialized wpa_supplicant". However, "/etc/wpa_supplicant/wpa_supplicant.conf" still has a Sept 29 file date, so has not been touched. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers@suse.de |snwint@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 --- Comment #2 from Steffen Winterfeldt <snwint@suse.com> --- You cannot setup wifi using the old dialogs atm. But you should be able to setup the interface using the WIRELESS_* ifcfg entries, using a boot option like this: ifcfg=wlan0=dhcp,WIRELESS_ESSID=mynet,WIRELESS_AUTH_MODE=xxx,... Does this work for you? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 --- Comment #3 from Neil Rickert <nrickert@ameritech.net> ---
Does this work for you? (c#2)
No, that did not help. The same failure. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(nrickert@ameritec | |h.net) --- Comment #4 from Steffen Winterfeldt <snwint@suse.com> --- Well, was ifcfg written correctly? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 --- Comment #5 from Freek de Kruijf <freek@opensuse.org> --- On an UEFI system one does not get the screen to enter this text. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 --- Comment #6 from Steffen Winterfeldt <snwint@suse.com> --- Press 'e', then add it to the linuxefi line. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 Neil Rickert <nrickert@ameritech.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(nrickert@ameritec | |h.net) | --- Comment #7 from Neil Rickert <nrickert@ameritech.net> ---
Well, was ifcfg written correctly?
I'm not completely sure what the question is asking. I'm also not sure if I followed the example correctly.
From my notes, I used (on kernel command line):
ifcfg=wlp18s0=dhcp,WIRELESS_AUTH_MODE=psk,WIRELESS_ESSID='the appropriate ssid',WIRELESS_WPA_PSK='the network key' After the connection failure, I checked "/etc/sysconfig/network/wlp18s0" and it contained only the same two lines as before. On my first attempt, I did it a bit wrong. I began the command line parameter with: ifcfg=wlp18s0,WIRELESS_AUTH=... and, in that case, a third line appeared in the "ifcfg-wlp18s0" file. I did not write it down, but I believe it was: IPADDR=wlp18s0 I'm not sure this is useful. Even if kernel parameters could work, it will be too difficult for many users. I know it is getting late for the 13.2 release. I'm willing to download and test NET install iso images from openQA, if a fix can make it that far in time. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 --- Comment #8 from Steffen Winterfeldt <snwint@suse.com> --- The option looks correct. Can you please boot with startshell=1 and check the ifcfg file _before_ yast starts?. Also, if you switch to console 3 early on, you can watch linuxrc logging what it writes into ifcfg. I can see atm no reason why the WIRELESS_* options should not be written correctly. Yes, the dialogs still have to be adjusted. But technically the config will be the same as now. That's why I'd really like to know if it works or not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 --- Comment #9 from Freek de Kruijf <freek@opensuse.org> --- I pressed e and did the same as Neil except my device is called wlp2s0, and watched the output on 3. It looks like there are only two lines in ifcfg-wlp2s0. On 9 I could add the three WIRELESS lines to this file and the command ifup wlp2s0 made interface come up. However somehow the Retry did not try the remote repository. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 --- Comment #10 from Neil Rickert <nrickert@ameritech.net> --- I used "startshell=1", but that did not seem to do anything. As soon as I was prompted for network setup, I went to console 9. The ifcfg-wlp18s0 file had two lines. I also looked at console 9. It reported network failure on ethernet, not much else. I went through the setup dialog, then looked again at console 3. I saw, among other things: interface setup: wlp18s0 wpa-supplicant -B -Dwext -i(null) -c/tmp/wpa_supplicant.conf sh -c line 0 syntax error near unexpected token `(' I then went to console 9, and looked at /tmp/wpa_supplicant.conf and it did seem to have the ssid and key for my network. So I think that syntax error might be the problem (or part of the problem). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899895 http://bugzilla.opensuse.org/show_bug.cgi?id=899895#c13 Claudiu Cismaru <claudiu@virtuamagic.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |claudiu@virtuamagic.com --- Comment #13 from Claudiu Cismaru <claudiu@virtuamagic.com> --- Confirming the null interface from comment 2014-10-09 17:43:43 UTC, on Leap 42.1. This null interface issue has been around for a while, I haven't had time to report it. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com