http://bugzilla.suse.com/show_bug.cgi?id=1000498 http://bugzilla.suse.com/show_bug.cgi?id=1000498#c2 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msuchanek@suse.co | |m) | --- Comment #2 from Michal Suchanek <msuchanek@suse.com> --- No. If you read the report you will see the installer is so broken there is no way to do anything in the installer. Unless you have some way to generate that report without a shell. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1000498 http://bugzilla.suse.com/show_bug.cgi?id=1000498#c4 --- Comment #4 from Stefan Hundhammer <shundhammer@suse.com> --- Since there are no logs at all, also please describe what you did, and what went wrong at what time during that process: What did you expect to happen, and what actually happened. Please elaborate where you did what: - In the boot menu - In linuxrc - In the YaST installer -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1000498 http://bugzilla.suse.com/show_bug.cgi?id=1000498#c6 --- Comment #6 from Stefan Hundhammer <shundhammer@suse.com> --- I didn't find any clearly specified system requirements for Tumbleweed, but for SLE-12 (which is very much the same code base), here the minimum specs are 512 MB RAM: https://www.suse.com/de-de/products/server/technical-information Leap has even stricter requirements: 1 GB RAM https://en.opensuse.org/Hardware_requirements You might get lucky with 256 MB if you try a text-based (ncurses) installation and avoid the detailed software selection and probably also the expert partitioner, but that amount of memory is clearly out of spec these days. Please notice that it's very difficult to come up with a useful error message in that case since things will fail in mysterious ways if we run out of memory: Creating objects in Ruby or C++ might fail, maybe external programs (parted, modprobe) fail. This is not good - we know that. But the only alternative would be to get back to the hard check for available memory and to refuse to even start the installation, which OTOH would mean that you don't have a chance to even try a low-profile installation like described above (text only, no fancy things). -- You are receiving this mail because: You are on the CC list for the bug.