pISO
pISO copied to clipboard
ALSchwalm
cdrom emulation not supported by Kali
In doing some testing with the ISOS folder support, I attempted to boot Kali.
The bios portion of the boot saw the selected ISO as a CD drive, The boot kernel loaded, but was then unable to see the CD drive to complete the boot.
I've seen this before, when the correct CD driver is not present in the boot kernel. So this seems to be Kali's problem, not PISO. However there could be other systems with similar problems. I used to see this problem a lot when working with a Dell that had one of the first SATA CD drives, before the SATA CD drives were commonly supported in the Linux default kernel. Sometimes the problem is only with the boot kernel on the ISO, and if you are running the installer, a more complete kernel is installed. The fix back then was always to go get a parallel IDE drive, and install from that. I'm sure this isn't the exact same issue, but it is very similar. I can't tell if the driver is missing, or if the PISO virtual CD is supported but unrecognized. Where this is the largest issue is going to be for live ISO's, where the boot kernel is the kernel you need to run always.
I tested wit Kali 2017.2 (an admittedly old version of Kali, but not THAT old). I will cast a wider net and see how common this is across various ISOs I frequently use, and I will test with a more current Kali. Unless this turns out to be a common problem, I'm inclined to blame this on Kali, but I wanted to put this here in case other people are seeing a wider problem with other distributions
Kali boots to the grub menu, and depending on what you select you may or may not see the error displayed, which indicates the kernel can't find the CD. In some modes I get to watch the kernel try multiple drive types as it looks for the boot device.
Thanks for the issue report! What version of the pISO OS are you running?
Not sure where to look up the version, the image in the zip is dated 10/2... Guess I should go look for a fresh version.
I haven't had time to do much more testing, but I did tested with gparted.iso, one I downloaded new on 10/6, and it has problems booting as well. But it does sometimes successfully boot. It seems to be having some sort of timeout issue. On a failed boot example, I get lines of this error: "usb4-1.7: device descripter read/64, error-110" followed by two sets of "kworker blocked" error and a "task blocked", followed by a repeating "hung_task_timeout".(see attachment)
I will retest with 1.1.0 as it looks like you fixed a related issue affecting windows images (which is on my list to test with). I suspect the issues are related or the same.