Failing with liveUSB persistence [solved]

[Member kaye]

Hello Friends.

I’ve managed to create a liveUSB using:

antiX-19.1_x64-full.iso

As I understand it, I have to press F5 upon booting the liveUSB, so that’s what I did. I then set it to “persistence-all” (I think that’s what it was).

Then I set the rootfs to 5GB and homefs to (I think) the default (around 300+MB).

However I could not get anything to stick. Not the installed applications, not the taskbar modifications, etc. If I reboot, it’s like I did nothing to it at all.

I’ve read the:

http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/persistence.html

but it’s insufficient for my under-developed brain.

There are apps relating to persistence in the menu of the liveUSB but I’m not sure which to use.

By the way, when I used one of those apps that would save my things in home, it said something like, 300+MB available, 900+MB needed.

The flash drive is 8GB, if that matters.

Thank you very much.

• This topic was modified 3 years, 2 months ago by anticapitalista. Reason: solved

[Member fatmac]

Helpful

Up

0

::

http://download.tuxfamily.org/antix/docs-antiX-19/FAQ/persistence.html#_how_does_it_work

From memory, you need to create the necessary files/partition on another drive, it can’t be added to the downloaded ‘live’ version, unless you remaster it. but the files could be on another pendrive.

Linux (& BSD) since 1999

[Forum Admin anticapitalista]

Helpful

Up

0

::

When you reboot you must use the F5 persist option.
Or, better, once you have set up your F keys, use F8 to save them.
Then F5 persist will be automatically saved.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member olsztyn]

Helpful

Up

0

::

anticapitalista wrote:

Or, better, once you have set up your F keys, use F8 to save them.
Then F5 persist will be automatically saved.

@kaye:
Just to add, while persistence function is well implemented in antiX and works very well, the fact you dedicated such a large 5GB space to rootfs suggests you intend to keep many future changes in persistence file, which is not optimal IMHO… My subjective experience indicates this will eventually extend boot time and in general it is a good idea to re-master ones you are happy with configuration. Start with fresh persistence file.
Although Live tools in antiX are well implemented the only function that is missing is to discard persistence file, should interim changes cause problems difficult to undo. This can be only done manually.

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Member kaye]

Helpful

Up

0

::

Hello Friends
Thanks for your input.
Is there a reason why my antix 19 LiveUSB running from my laptop cannot connect to wifi but if it’s plugged into my desktop computer it can connect to wifi?
Thank you !

[Anonymous]

Helpful

Up

0

::

.

[Member kaye]

Helpful

Up

0

::

I don’t understand the joke because I don’t understand your answer. Thank you

[Anonymous]

Helpful

Up

0

::

Okay, try again. I edited and removed the “joke”.

Effective troubleshooting requires attention to details.
Did you, in fact, choose “persistence-all” …or something else?

Does your boot media have a physical “lock” slider? If so, maybe the slider got bumped//moved into the read-only locked position.

restating anticapitalista’s comment “When you reboot you must use the F5 persist option”:
Understand that during each liveboot, we have the freedom of choice: yes, load+use persistence, or not.

antix 19 LiveUSB running from my laptop cannot connect to wifi but if it’s plugged into my desktop computer it can connect to wifi

Not a joke. Without hearing the details of the hardware in the misbehaving laptop, how can anyone troubleshoot a “reason” ?
lshw -C network
and paste the details into a followup post.

[Member seaken64]

Helpful

Up

0

::

kaye wrote:

Hello Friends
Thanks for your input.
Is there a reason why my antix 19 LiveUSB running from my laptop cannot connect to wifi but if it’s plugged into my desktop computer it can connect to wifi?
Thank you !

Different hardware often yields different results. The LiveUSB has settings for each different computer. You need to troubleshoot the wifi while on the laptop. Once it is solved on that hardware it will be saved on your LiveUSB for further use on that hardware.

Seaken64

[Member kaye]

Helpful

Up

0

::

Did you, in fact, choose “persistence-all” …or something else?

Yes I did. I now know that I should choose persistence-all if I want to see my personal settings every time I boot the live USB, things like taskbar on top position, my own time format, my preferred theme, etc.

Does your boot media have a physical “lock” slider?

No it does not.

“When you reboot you must use the F5 persist option”

That’s what I’ve been doing. I didn’t know that at first but I do now.

I’m not sure if it matters but here’s a more detailed scenario.

I’m regularly in two cities, City A and City B.

My internet service provider in City A is Telecom ABC.
My internet service provider in City B is Telecom XYZ.
(Two different telecom companies)

In City A, I use a desktop computer. I insert the live USB in that desktop computer and boot from it. It can connect to wifi, and it auto connects to wifi if I boot with persistence.

In City B, I use a laptop computer. I insert the live USB in that laptop computer and boot from it. It cannot connect to wifi. Both Ceni and the other one (forgot the name) are unable to find the wifi if I choose or click Scan.

I’ll post the details of ‘lshw -C network’ next.

[Member kaye]

Helpful

Up

0

::

A little improvement but still no internet connection.

I just noticed the message in Ceni. It said something like I can try to delete /run/wpa_supplicant , which I did. Then Ceni was finally able to detect the wifi when I chose Scan. I then proceeded to enter the password, but still no internet. Here is the output:

ifup: configuring interface wlan1=wlan1 (inet)
/bin/run-parts –exit-on-error –verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver nl80211,wext (default)
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan1.pid -i wlan1 -D nl80211,wext -C /run/wpa_supplicant
Starting /sbin/wpa_supplicant…
wpa_supplicant: creating sendsigs omission pidfile: /run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan1.pid
wpa_supplicant: ctrl_interface socket located at /run/wpa_supplicant/wlan1
wpa_supplicant: configuring network block — 0
wpa_supplicant: wpa-ssid “mywifi” — OK
wpa_supplicant: wpa-psk ***** — OK
wpa_supplicant: enabling network block 0 — OK

/sbin/dhclient -4 -v -i -pf /run/dhclient.wlan1.pid -lf /var/lib/dhcp/dhclient.wifup: configuring interface wlan1=wlan1 (inet)n1.leases wlan1
/bin/run-parts –exit-on-error –verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtool
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver nl80211,wext (default)
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan1.pid -i wlan1 -D nl80211,wext -C /run/wpa_supplicant
Starting /sbin/wpa_supplicant…
wpa_supplicant: creating sendsigs omission pidfile: /run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan1.pid5.255.255 port 67 interval 10
wpa_supplicant: ctrl_interface socket located at /run/wpa_supplicant/wlan1
wpa_supplicant: configuring network block — 067 interval 7
wpa_supplicant: wpa-ssid “mywifi” — OKort 67 interval 12
wpa_supplicant: wpa-psk ***** — OK5.255 port 67 interval 6
wpa_supplicant: enabling network block 0 — OK
No working leases in persistent database – sleeping.
ifup: configuring interface wlan1=wlan1 (inet)1.pid -lf /var/lib/dhcp/dhclient.w/bin/run-parts –exit-on-error –verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/ethtooln
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver nl80211,wext (default)re/dhcp/
wpa_supplicant: /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan1.pid -i wlan1 -D nl80211,wext -C /run/wpa_supplicant
Starting /sbin/wpa_supplicant…aa:c1:8c
wpa_supplicant: creating sendsigs omission pidfile: /run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlan1.pid5.255.255 port 67 interval 7
wpa_supplicant: ctrl_interface socket located at /run/wpa_supplicant/wlan1
wpa_supplicant: configuring network block — 067 interval 14
wpa_supplicant: wpa-ssid “mywifi” — OKort 67 interval 18
wpa_supplicant: wpa-psk ***** — OK5.255 port 67 interval 14
wpa_supplicant: enabling network block 0 — OK
No working leases in persistent database – sleeping.
/sbin/dhclient -4 -v -i -pf /run/dhclient.wlan1.pid -lf /var/lib/dhcp/dhclient.wlan1.leases -I -df /var/lib/dhcp/dhclient6.wlan1.leases wlan1
Internet Systems Consortium DHCP Client 4.4.1hi-daemon
Copyright 2004-2018 Internet Systems Consortium.l
All rights reserved. /etc/network/if-up.d/mountnfs
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan1/00:1b:b1:aa:c1:8c
Sending on LPF/wlan1/00:1b:b1:aa:c1:8c
Sending on Socket/fallback
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 9
No DHCPOFFERS received.
No working leases in persistent database – sleeping.
/bin/run-parts –exit-on-error –verbose /etc/network/if-up.d
run-parts: executing /etc/network/if-up.d/000resolvconf
run-parts: executing /etc/network/if-up.d/avahi-daemon
run-parts: executing /etc/network/if-up.d/ethtool
run-parts: executing /etc/network/if-up.d/mountnfs
run-parts: executing /etc/network/if-up.d/wpasupplicant

Press Enter key to continue …

Also, is this what you’re asking?

lshw -C network
bash: lshw: command not found

Thanks!

[Forum Admin anticapitalista]

Helpful

Up

0

::

1. Remove connman and cmst

sudo apt-get remove --purge connman cmst connman-bluetooth-firmware-antix

2. Delete the resolv.conf sym link in /etc/
3. Create a new symlink in etc like this (in a terminal)

sudo ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf

4. Try ceni again

• This reply was modified 3 years, 3 months ago by anticapitalista.
• This reply was modified 3 years, 3 months ago by anticapitalista.
• This reply was modified 3 years, 1 month ago by anticapitalista.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member kaye]

Helpful

Up

0

::

2. Delete the resolv.conf sym link in /etc/

There does not seem to have a file named resolv.conf in /etc
There is a folder named /etc/resolvconf .
Should I delete that folder?

Thank you.

[Forum Admin anticapitalista]

Helpful

Up

0

::

No. Create the symlink as shown in step 3

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member kaye]

Helpful

Up

0

::

anticapitalista wrote:

No. Create the symlink as shown in step 3

I have not tried this with the live USB but the installed antiX on the hdd cannot detect the wifi too, even after doing your step 3.

I did not have this issue with antiX 17.

Thank you.

[Author]

Posts