Altered Clonezilla disk not loading on AMD computers
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Using the latest version (2.1.1-7), no matter what I do with my customized auto-restore disk it absolutely will not load on any AMD computers I've tried (tried 2, one with an A6 and another with a A8). I've backtracked all the way to just altering the ocs-live run line with my restoreparts command and even just altering that caused the machines to not boot to it. I'm using PowerISO to change the iso images, and they work completely fine on Intel machines, but not AMD. Any ideas as to why?
The line I have (and it's not cleaned up, just using it for testing purposes at this point):
append initrd=/live/initrd.img boot=live config noswap edd=on nomodeset locales= keyboard-layouts= ocs_prerun="mount /dev/sda2 /mnt" ocs_prerun1="mount --bind /mnt/clonezilla /home/partimag/" ocs_live_run="ocs-sr -g auto -e1 auto -e2 -batch -r -j2 -k -p reboot restoreparts reload sda1" ocs_live_extra_param="" ocs_live_batch=no vga=788 ip=frommedia nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.blacklist=yes
The unaltered line was:
append initrd=/live/initrd.img boot=live config noswap edd=on nomodeset locales= keyboard-layouts= ocs_live_run="ocs-live-general" ocs_live_extra_param="" ocs_live_batch=no vga=788 ip=frommedia nosplash i915.blacklist=yes radeonhd.blacklist=yes nouveau.blacklist=yes vmwgfx.blacklist=yes
The thing I'm curious about is, I can't even get the initial menu screen up, so I'm not even sure how any of that would impact that, but then I don't know at what point it looks at that in the initial loading up process. Or if it's just the fact that AMD doesn't like that I've altered the base iso. If I just burn an unaltered version of that iso it loads fine, but as soon as I make ANY change to it it no longer loads.
Just confirmed this. Just simply adding a file into the isolinux folder that has nothing to do with anything causes the cd to not load. Again, the problem is specific to AMD computers. Could this be a bug?
Update on this: apparently the issue was PowerISO. Once I switched to another iso editor (WinISO) it stopped occurring.
OK, thanks for sharing that.
Steven.