Installling Bodhi 7Alpha4 broke my computer! (Not Really)

Hmm, I have installed BL 7 alpha4 in VM and it takes 250 MB after boot in idle.

Thanks much for reply and ideas!

So the hard drive is recognized if I hot plug it - meaning plug it in after I boot.  This is an internal sata drive so this is not typical operation method

I am running your dd command now, it's been going quite a while (over 30 mins), and no lockup, so I think it's doing good things!  When it finishes I'll reboot and see if I can get past BIOS with it still plugged in.   But if I can... dunno if I trust this drive.  I still want to test it in some way....

As to not using clonezilla and installing what I like on it, I dont want to install anything on it.  I know my initial message was long and confusing, but the goal is to copy an existing bodhi 6 to it from from another drive (SSD ) and still be bootable, so I can install bodhi 7 on the whole SSD.  The SSD is only 128GB which was more than enough for Bodhi 6+apps+data (55GB used).  The HDD will be a backup of Bodhi 6 only, no plans for long term use, because after testing bodhi 7, will continue to use and test it until release on the SSD.  I'll wipe and reinstall it again to check the next iso on the SSD, but the goal will be for it to remain bodhi 7, the HDD is just backup of bodhi 6 incase something goes wrong (and to copy stuff from), I doubt I'll use more than 128GB with bodhi 7 either.  This machine is too old to run giant games nor do I use it for video encoding or storage, so really can't see any reason why the 128GB SSD would fill up.

As to ram, this machine has plenty.  In fact, I just upgraded it from 1.5GB to 3.5GB last week, after taking home some memory from family who were spring cleaning and getting rid of some old 32-bit machines.  I do see Bodhi 7 using a small percentage more than Bodhi 6, but not significant.  I reduced my VM to 512MB and its working fine.  I'll test install at 512MB later, to see if we need to update minimum requirements, but as stefan said, once booted it's certainly fine, I see 250-300mb usage myself in virtual machine testing.  Looking forward to hardware testing soon!

As far as I know, the functionality is the same, but aside from some qt dependencies I just don't care for its appearance. It looks a little dated. Memory saving was about 20M on boot on my testing, using htop to measure system memory.



Interesting observation. I never paid any attention to the size of initrd.gz on the ISO vs the installed system. On the ISO, initrd.gz has crept up in size from BL6.0 even tho it is created by the exact same command in the script I use to make the ISO.

I briefly looked over my script and googled a few things. My conclusion was "the iso uses gzip for compression as that is what the mkinitrd command uses. The installed system, however, uses zstd compression." I could be wrong as my examination was very brief. But the script certainly uses mkinitrd to create initrd.gz.

The question would be is there any way to make mkinitrd.gz smaller on the ISO? And is it worthwhile to do so? I would think it would be worthwhile unless it creates problems for the ISO. As to how to do it I don't know at this moment.

The dd wipe that robur reccommended worked, then I could pass POST and boot again.

I tried to clone again, this time with dd. It locked things up, as always. And like before when I tried to clone, it passed POST but prevented boot until I unplugged the drive.   Weird stuff.

Both SATA, no need to set jumpers.

Does that mean you had to completely remove firmware and drivers? If so, that may be a solution for some, but obviously some people have that hardware and would need that stuff....   Or maybe I just don't understand what you're doing anyway, maybe you're just not unpacking that stuff to ram and leaving it on the dvd/usbdrive unless the user needs them, which obviously is better...