antiX live usb issue

[rs55]

A suggestion:
If fuseiso* is only causing a problem for a certain subset of machines ( like mine), but necessary for other machines, then perhaps you could make fuseiso* optional, or at least allow users to uninstall it.(as it used to be prior to this latest version).

[rs55]

Are you sure the issue is lum etc and not your bleeding edge liquorix kernel?

I dont think its the liquorix kernel, because the problem also occurs in my Antix installation which is on 4.9 kernel.

[rs55]

have you tested on thinkpads circa 2011-2012 models? ( x220, x230, t420, w520 etc)? These are my favorite machines and I think they are quite popular with linux enthusiasts in general.

[anticapitalista]

have you tested on thinkpads circa 2011-2012 models? ( x220, x230, t420, w520 etc)? These are my favorite machines and I think they are quite popular with linux enthusiasts in general.

I have a Thinkpad L412

[dolphin_oracle]

running LUM from the command line with the "--force=nofuse" switch should then work if fuse is the problem. We can add that option to the gui easy enough.

[fehlix]

If fuseiso* is only causing a problem for a certain subset of machines ( like mine), but necessary for other machines, then perhaps you could make fuseiso* optional, or at least allow users to uninstall it.(as it used to be prior to this latest version).

Please verify that it works for you with disabling fuseiso from command line like this:

Code: Select all

sudo live-usb-maker  --force=nofuse 

Probably this can also be set permanently into the saved configfile.

[BitJam]

Urgent!!
In MX, I noticed the updater had updates for LUM and associated files including fuseiso and cli-..

I updated, created a new live usb and attempted to boot. Got a fatal error:
"Error: mount: mounting /dev/loop0 on /live/linux failed: Invalid argument"

This may not be a fuse problem. This error will occur when the kernel does not support the type of squashfs compression used to make the linuxfs file (but there could be other issues as well).

Please try again with the "bp=e" option. This will get you to a shell when the error occurs. Then run "dmesg | tail -n20". This will likely tell us more about what is going on.

Once the bootloader has run (and read the vmlinuz and initrd.gz files) then our fragmentation woes are over. The Linux kernel has no problem reading fragmented files so I suspect the problem is the compression method.

[rs55]

If fuseiso* is only causing a problem for a certain subset of machines ( like mine), but necessary for other machines, then perhaps you could make fuseiso* optional, or at least allow users to uninstall it.(as it used to be prior to this latest version).

Please verify that it works for you with disabling fuseiso from command line like this:

Code: Select all

sudo live-usb-maker  --force=nofuse 

Probably this can also be set permanently into the saved configfile.

Yes - it works with the command line and force=nofuse.
It would be great if the gui for LUM had a checkbox for fuse/nofuse. I dont think Iam the only one this issue with fuse- I believe dolphin was also having the same issue.

Where is the config file for LUM and how do I change it?

[fehlix]

Where is the config file for LUM and how do I change it?

I havn't tested the save config settings feature. But if you run live-usb-maker --help
such an option is mentioned. Need to check...

[BitJam]

@rs55, please run LUM again with fuse enabled. When you boot, please add these two options:

Code: Select all

checkmd5  bp=e

The first will check the integrity of the linuxfs file before we try to mount it. The 2nd will get you to a shell when the error occurs. In the shell run the command:

Code: Select all

dmesg | tail -n20

This should tell us why the mount failed. You could possible take a picture of the output if that is easy for you and it seems warranted.

If we are still getting fragmentation problems and we can't fix them then we may have to change our strategy and only use fuse when normal mounting fails. If I do give up then that will mean there will be some (rare) systems that LUM will not work on which is not a desirable outcome.

I want to first find out exactly what the problem is and then deal with it.