Forum › Forums › New users › New Users and General Questions › [SOLVED] frugal install 32-bit antiX
Tagged: tags: extra large, use no bleach
- This topic has 153 replies, 10 voices, and was last updated May 5-10:25 pm by Brian Masinick.
-
AuthorPosts
-
April 9, 2022 at 7:22 pm #80945Member
dugin
::Non-Fatal Error Could not enable required root! persistence c = continue p = power off r = rebootIt’s a moot issue at this point, but I am not the first antiX user to encounter this error, and I don’t believe the issue was resolved. But if I substituted a backup directory, and got the same error, that would indicate the problem is outside of the frugal install, like maybe properties of the partition have changed. I haven’t been using antiX for the last few days, and this problem just occurred for no discernible reason. What would cause this problem?. It says, Non-Fatal Error, but without persistence this frugal install is unusable.
EDIT: It’s possible, which is not to say likely, that I accidentally used a 64-bit antiX DVD to boot my 32-bit frugal install, and this caused the error. I’m not going to try to repeat the error, just putting the idea out there in case it happens to someone else. I really don’t know what caused the error, but it is a pertinent fact that the backup folder produced the same error, indicating that the frugal install was not the cause, so possibly the error was caused by the wrong boot DVD. Just a possibility.
- This reply was modified 1 year, 1 month ago by dugin.
April 9, 2022 at 7:27 pm #80948Moderator
christophe
::The tutorial does make a helpful distinction, that so-called frugal install options refer to saves to hdd, so I should not be selecting Frugal-Root, as was recommended earlier. Rather, I should be selecting some variant of Persist-. What is the recommended Persist option?
Right. Choose the persist options rather than frugal when using live-usb.
The default persistence description is held in memory, and is sometimes described as “dynamic.”
You may instead use persistence saved to usb storage directly (not ram). This 2nd type is described as “static.”
You choose.
Some people think that the static persistence makes excessive write to their usb stick, and will cause it to fail sooner.
Dynamic persistence will use up your ram as storage, and needs to be saved to disk (stick) in order to be kept for next reboot.Lots for you to read up on. This is “antiX live 101” collegiate coursework for you. đ
- This reply was modified 1 year, 1 month ago by christophe.
confirmed antiX frugaler, since 2019
April 9, 2022 at 7:47 pm #80951Moderator
christophe
::I generated a live usb by running Live USB Maker. I booted from live usb, but couldnât proceed because the USB could not be used as a boot device since it was mounted.
I’m sorry. That makes no sense to me.
Please start over; read & watch the how-to’s of the live system. No matter how many times you’ve done it in the past, I insist that it is not that hard. Not hard at all, actually. So long as you make the live-usb from within antiX, the usb will be able to save & use persistence. Experiment with the various types of persistence. Read about what each type means, how it works in theory, while experimenting.
I insist that the antiX live system is easy to use. Please stop making it hard for yourself.
confirmed antiX frugaler, since 2019
April 9, 2022 at 7:53 pm #80953Memberdugin
::Can I change the Persist option once selected. For example, use Persist-static for a while, then change/edit to Persist-dynamic? How would I go about making that change?
April 9, 2022 at 8:01 pm #80954Moderator
christophe
::Can I change the Persist option once selected.
Yes.
How would I go about making that change?
Did you set one type of persistence at boot with F5? If so you do the same thing to select a different one. Save it with F8 if you want it saved.
- This reply was modified 1 year, 1 month ago by christophe.
confirmed antiX frugaler, since 2019
April 9, 2022 at 8:41 pm #80956Memberdugin
::The usb boot problem was because I selected Frugal-Root persistence option. Setting Persist-Root, the installation went normally.
Question: Is Persist-Root a dynamic persistence, that is, in RAM?- This reply was modified 1 year, 1 month ago by dugin.
April 9, 2022 at 8:55 pm #80958Moderator
christophe
::Question: Is Persist-Root a dynamic persistence, that is, in RAM?
Yes.
confirmed antiX frugaler, since 2019
April 9, 2022 at 9:48 pm #80959Memberdugin
::With USB 2.0, if I reboot without any changes to save, press Enter when I first encounter Custom Boot splash screen, it takes 2 min 41 sec to get back to desktop. Is this a normal reboot time? Pressing Enter at Custom Boot splash, boot time with toram option is 2 min 25 sec. Is that slow, or within normal range?
- This reply was modified 1 year, 1 month ago by dugin.
- This reply was modified 1 year, 1 month ago by dugin.
April 10, 2022 at 1:28 am #80968Memberdugin
::Have sound in firefox, no sound in seamonkey
https://www.antixforum.com/forums/topic/have-sound-in-firefox-no-sound-in-seamonkey/Okay, that edit fixed Seamonkey sound. The add-ons for SM are obsolete, not even an ad blocker!
This audio problem could also have been fixed by installing pulseaudio via antiX package installer. I only noticed the pulseaudio package today, for the first time.
It would be nice if xfburn was available via antiX package installer. I suggest this because I used synaptic to install SimpleBurn, but since SimpleBurn wasn’t really there, only listed, synaptic crashed and became inoperable. I had to start over, as in, re-install antiX. What I mean is, since xfburn is the default burner, it should be available from antiX package installer, available without having to resort to synaptic, please.- This reply was modified 1 year, 1 month ago by dugin.
- This reply was modified 1 year, 1 month ago by dugin.
- This reply was modified 1 year, 1 month ago by dugin.
April 10, 2022 at 3:06 am #80973Memberdugin
::I have a problem with European distributions. First time it happened was with Mint in 2008, and I never solved it. My clocks get reset every boot, usually 5 hours before current local time — usually, not always. Well, it’s happening again with antiX, even though I selected the correct time zone (-5 GMT/NYC) in the initial setup. It may stay correct for a while, but next time I use another distro, the clocks will go haywire again. As I recall, Mint was messing with my hardware clock, and that is why I dropped Mint. Maybe the problem was Windows, which I used until around 2010. But I haven’t used Windows for 12 years. XP was the last Windows I used, never really messed with Windows 7. My first Linux distro was Austrumi, mostly because it was downloadable at 50 MB. Mandrake was the first Linux distro I connected to the internet, on dialup, at a time when ethernet was becoming widely adopted. Honestly, I deserve a medal for that, getting Mandrake to do dialup. (maybe not)
EDIT: Yep, other distro’s clock is reading (reset) 4 hours ahead of current time (Daylight Saving Time).
- This reply was modified 1 year, 1 month ago by dugin.
- This reply was modified 1 year, 1 month ago by dugin.
- This reply was modified 1 year, 1 month ago by dugin.
April 10, 2022 at 7:47 am #80978Memberdugin
::How would I use this liveUSB I have created on a newer UEFI computer. In such a way that after I run antiX on the newer computer, I can put the liveUSB back in this older computer I am using now. Would I change persistence so the UEFI settings are not saved? Otherwise, would the liveUSB simply boot up the UEFI computer, or would the newer computer require that I make some preparations, or change boot parameters? Is this liveUSB a tool that I can put in any computer? Or is it best just dedicated to this one old computer?
I’m thinking I could boot up this old BIOS computer, set persistence to manual, shutdown, then use the liveUSB to boot the UEFI computer, or whatever, and when I’m finished, I could boot the old computer again, then set persistence back to automatic. Would that work without ruining my liveUSB install? Or is that risky activity?
- This reply was modified 1 year, 1 month ago by dugin.
- This reply was modified 1 year, 1 month ago by dugin.
April 10, 2022 at 8:54 am #80986MemberModdIt
::but next time I use another distro, the clocks will go haywire again,
what does that have to do with antiX ?.
running antiX for more than 2 years I can set my clock to anywhere I feel like and it works as expected.
Unless windoze or another setup changes time, then it takes a while for antiX to synch with timeservers.Set your other distros so they do not change the system clock and be happy.
Regarding Live USB, it is a tool which will work with most but not any computer. Plug it in and try to boot.
Preferably without persistence until you see whether it works or not. Recent computers may well not boot.
Secure boot is not driven by antiX and can be very bothersome.April 10, 2022 at 3:41 pm #80996Memberdugin
::but next time I use another distro, the clocks will go haywire again,
what does that have to do with antiX ?.
It’s a push-pull thing. Both distros are set to Eastern Time USA. If I correct the local time to current time in antiX by moving local time forward 4 hours, then next time I boot another distro (which has kept good time for 4 years) I have to set the other distro’s clock back by 4 hours; next time I boot antiX, its clock is 4 hours early again. And that is when the clocks make sense. Sometimes, the out of sync clocks don’t make sense. Another factor is, if I change distros within 4 or 5 hours of midnight, the day/date can be incorrect too. A lot of internet things don’t work if the time isn’t accurate. What antiX and Mint have in common is that they are European distros. It’s not a dealbreaker, it’s just inconvenient.
- This reply was modified 1 year, 1 month ago by dugin.
- This reply was modified 1 year, 1 month ago by dugin.
- This reply was modified 1 year, 1 month ago by dugin.
April 10, 2022 at 5:45 pm #81000MemberModdIt
::This is irritating for sure, and should be fixable. It is not because the distros are european
Is the BIOS Battery in your computer OK and system Time correct. Best to look in the BIOS after
not using the computer overnight at least.Please post result of ls -l /etc/localtime
Which should help us to figure out where the problem lies, or was.
My guess is the time and zone were incorrect at setup of at least one of the distros.
But I may be wrong. Lets figure things out.To setup your timezone please use below but correcting the command to your timezone
which you can search in the net and compare with /usr/share/zoneinfosudo ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime
The command works in almost all linux distros. And is where things get interesting.
You are using a frugal install, an ISO on yor drive as I understand things.I have never used frugal, my assumption is that to get timezone settings to stick
you will have to either set time while booting or use a custom ISO. Easy in antiX
for Mint, may be interesting.Maybe a forum member who uses the frugal options can help/educate on the final part.
- This reply was modified 1 year, 1 month ago by ModdIt.
- This reply was modified 1 year, 1 month ago by ModdIt.
April 10, 2022 at 8:52 pm #81008Moderator
christophe
::Regarding time zone: If you want to keep local time on your computer’s bios, try setting antiX to UTC. See if that fixes it for you.
confirmed antiX frugaler, since 2019
-
AuthorPosts
- You must be logged in to reply to this topic.