![]() Trying now to boot up diffrent hardware, but taking your advice, before I do so, I've ordered in for a bunch of pendrives of different makes.įrom what I understand about Kernel Panic, its an internal error which is fatal. This is the same error I was getting with Kali Live. drm_kms_helper: panic occurred, switching back to text consoleĪnd that is all. Kernel Panic - not syncing: Attempted to kill init! exitcode=0x000000100 ![]() I just installed backbox on the same pendrive and tried to boot, gives me this error: If the device is able to boot, the function (and 'complexity') of persistence will be same for all methods. It is same for all methods - a "persistent" flag in the boot-loader, which looks for a "casper-rw" (or "home-rw") partition or file. ![]() I don't think adding persistence can add any complications. I also attempted to add persistence to the live boot. even ext2 in case of "Slitaz"), boot-loaders, creation methods etc.). Just try different available ones (different filesystems (fat/fat32. ![]() There is no one standard that one can recommend confidently for all systems. So the point is - USB booting still seems to be a job of patchworks at the firmware level. All those pendrives can boot other systems perfectly fine. It booted fine with USB hard disk (any kind of boot-manager - YUMI (whatever it uses), LILO, Grub2.). ![]() Tried to boot a Compaq laptop a few days ago - failed to boot. Sometimes it can be the USB flash drive itself, sometimes it can be a particular BIOS which boots only with some particular kind of flash drives or boot managers.įor instance, I had a Kingston Pen drive long ago which couldn't boot 'Any' computer that booted fine with a transcend pen drive of the same capacity, same methods, same boot managers.Ĭurrently, I have two 8GB Kingston (Ubuntu/Lubuntu), and a 1GB PNY (clonezilla - created using Unetbootin) drives. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |