BodhiThis forum is for the discussion of Bodhi Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As far as I know Rufus has got better support than Unetbootin for some machines. So if you have access to Windows machine, try Rufus. Another solution is to boot from CD ROM.
If you're working from a Linux machine, I've had great success with dd.
Using dd to make a bootable USB stick from an ISO file:
run >> ls /dev/sd*
note the result
plug in USB medium
rerun above
the difference should tell you the path to the USB drive (/dev/sdx, where x is something)
cd to the location of the imagefile
>> sudo dd if=imagefilename.iso of=/dev/sdx [see above; x=something]
[Note: this takes a long time and there is no feedback until it’s done. DON’T PANIC]
I had the same problem with the Rufus produced drive - even after I edited syslinux.cfg according to the link that was provided.
I then tried dd ... the flashdrive was sdb1 ... and I used the script that was kindly provided by rrashkin. Yes ... it did take a very long time! When I attempted to boot, I received an error message that isolinux.bin was either missing or corrupt and that the operating system wasn't found. Because of possible corruption, I reproduced the drive a second time with dd ... only to get the same error message.
I found isolinux.bin inside the folder/directory = /media/Bodhi Linux 5.0.0 Legacy/ISOLINUX. It was not in the root directory of the flashdrive.
It does appear that the ISO is a problem. I tested the version that I originally downloaded ... and then re-dowloaded the ISO twice ... and re-tested with the same bad results ...
I used both check methods - and I neither received a checksum nor an "OK" with the alternative method.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.