Installer stops when incorrectly detects USB stick as a CDROM drive.

Timmi · 2017-10-31 08:20

I was trying to install it (custom install), when it hit a snag: it presumed that my USB stick was a CDROM drive (yet the computer doesn't even have one).

This is with the latest version of ISO (as of this writing) q4os-2.4-i386-instcd.r2 , and the md5 checked out.

The computer is an ASUS eeePC 1000he, with Atom N280, 2GB of RAM, 1024x600 graphics(physical, with 1024x768 logical with panning).
Specs: https://www.asus.com/ca-en/Laptops/Eee_ … fications/

I'll attach a photos of where it went wrong. I tried ignoring the error and moving onto the next step... no dice.

Is this because the image (as the filename suggests) is for CD/DVD only, and not USB?

Please, if technical stuff/programming can be avoided, that would be very much appreciated.
I'm hoping for an ISO with a fixed installer (preferably), or a user-friendly solution.

Attachments:

P1040978-.JPG, Size: 152.46 KiB, Downloads: 640

Dai_trying · 2017-10-31 16:33

You could try the live installer, it will allow easier (IMO) custom installation. The download page has images for 32 bit (591mb) or 64 bit (606Mb) and is what I always use. This also allows you to test the hardware compatibility and will allow you to check errors (if they occur) more easily.
You can also install software while in the live session so for instance you could install inxi and gather hardware configuration information for troubleshooting.

crosscourt · 2017-10-31 23:47

Agree with Dai as Ive seen this before, the live cd youll find easier to use.

Timmi · 2017-11-01 03:15

Thank you, that is the first I tried, but it wouldn't boot.

I suspect that it's because in the filename, it is labelled as PAE,
and perhaps the Atom is a non-pae?

Last edited by Timmi (2017-11-01 03:36)

Timmi · 2017-11-01 03:29

Correction:
this time I tried Mint's USBimagewriter, and 686-live is booting.
Trying it now.

Last edited by Timmi (2017-11-01 03:37)

Dai_trying · 2017-11-01 10:20

Out of curiosity what method did you use to write the image originally, it might be useful to know what methods are "less robust" when writing images to usb.

Timmi · 2017-11-01 20:28

There aren't exactly a boatload of choices out there, under Linux, for creating a multi-OS-boot USB.

The utility I used is called
MultiBootUSB ver.8.8.0
You can find info on it here: multibootusb.org

It works fine with most other distros. It lets you put as many Linux distros onto a bootable USB as space permits.
It also correctly detects when it's a live iso and offers to reserve space for persistence.

There is no wasted space, as in the case of the tool I had to use this time.

I have seen under Windoze, such utilities stop working (earlier this year I believe it was), when the Linux Kernel was updated. And the next update of the utils a couple of weeks later, worked fine again.

What I'm getting at, is before we label something as "less robust", we should consider the possible causes.

I would suggest, take a look at Q4: what is doing the detection in it - the live version won't launch the correct (pae/nonpae, I suspect), and the installer version assumes it's a different type of media.
See what in there is doing the detection, and can it be substituted with something "more robust" used by other distros? (it's all open source anyways).

Last edited by Timmi (2017-11-01 20:39)

Dai_trying · 2017-11-01 20:38

I have tried multiusb before but had very limited success, but that is almost definitely the cause of the problem. I find that usb devices are in such abundance now that I have around 15-20 of them and I have a couple of really old 1Gb ones which I can easily fit Q4OS on to and they still work without issue.
My advice would be to simply use one usb per distro, but I do wish you luck with multiboot, I really liked the idea of being able to fit loads of distros ont my 64Gb usb stick and be able to boot and install whichever image suited the machine I was working on, but it's only an idea in my experience as there were more failures than successes.

crosscourt · 2017-11-01 21:15

Never been able to get multiboot to work and stick to one per stick, same as Dai, too many failures.

Dai_trying · 2017-11-01 21:49

Another downside is the problem with using both legacy systems and uefi ones, just another reason to have separate usb's

crosscourt · 2017-11-02 00:01

Exactly Dai good point.

Q4OS Forum

#1 2017-10-31 08:20

Installer stops when incorrectly detects USB stick as a CDROM drive.

#2 2017-10-31 16:33

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#3 2017-10-31 23:47

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#4 2017-11-01 03:15

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#5 2017-11-01 03:29

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#6 2017-11-01 10:20

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#7 2017-11-01 20:28

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#8 2017-11-01 20:38

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#9 2017-11-01 21:15

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#10 2017-11-01 21:49

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

#11 2017-11-02 00:01

Re: Installer stops when incorrectly detects USB stick as a CDROM drive.

Board footer