I am using on the harddrive btrfs, it did boot with all earlier snapshots ofc. As far as I can tell the bootloader has not changed in a while. Only the Kernel and the FS specific stuff. Am 13.08.2015 um 12:57 schrieb Joerg Schilling:
gargamel704 <gargamel704@hotmail.de> wrote:
As I said. The system was unable to boot. It essentially got stuck at the loading ramdisk stage. I did not read all messages as the Subject is not cdrtools related....
Does this mean that it did boot first?
As for the options: No. I assumed that the installer handles this. I The genisoimage program is not compatible to mkisofs. Around 2006, the Debian people changed some options back to a behavior that was annouced as deprecated in 2000 already and disabled in the code around 2004.
There may be a need to change the caller of mkisofs to match the documented behavior again.
installed the snapshot from 15.05 (or so). Note that this behavior has nothing to do with updating from this old snapshot. I had exactly the same issue when installing a very recent snapshot from the disk and after normally rolling with TW. If the bootloader successfully loaded into memory, there may be a problem with the filesystem support in the bootloader or kernel.
Is my assumption correct, that the primary bootloader could be loaded and started and then does not finish with loading the ramdisk?
What filesystem flavor do you use on the medium?
Why is an unmaintained fork used at all? Are there no alternatives? This was a result from political pressure from Debian. Suse switched back to the original software in 2013 because the Debian fork is unmaintained since May 2007, but this did not seem to have caused results in the install group yet.
Jörg
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org