network and screen resolution not saved across logins

D-zaster · posted: 2017-10-13 04:50

I'm using Anti-X installed from antiX-16_x64-full.iso, using the IceWM desktop. I have been able to change the screen resolution to 1920x1080 (native size of my monitor) and have networking configured. The only problem is that if I log out and back in (maybe reboot, maybe just logout/login), I have to manually go into network and select my connection (I don't have to change anything, just say OK to everything) and then it works fine. Same thing for resolution, though I have to manually pick the resolution I need. As far as I can tell, these are the only 2 items that don't seem to persist across logins.

I'm running Anti-X under VirtualBox 5.1.28, and have no problems with other VMs w/r/t the persistence of either network configuration or screen resolution. Anti-X VM is the only one having this difficulty. I have the latest 5.1.28 guest additions installed.

Is there some action I must take to make my changes permanent?

skidoo · posted: 2017-10-13 05:55

hopefully the instructions here will provide a solution:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://askubuntu.com/questions/211163/virtualbox-how-do-i-change-guest-precise-resolution-to-169-1920x1080-inste"
linktext was:"https://askubuntu.com/questions/211163/ ... 1080-inste"
====================================

D-zaster · posted: 2017-10-13 23:02

skidoo wrote: hopefully the instructions here will provide a solution:

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://askubuntu.com/questions/211163/virtualbox-how-do-i-change-guest-precise-resolution-to-169-1920x1080-inste"
linktext was:"https://askubuntu.com/questions/211163/ ... 1080-inste"
====================================

I'm not sure which of the many solutions offered there you had in mind. I tried hinting the size to the guest (though, strangely, I've never had to do this for ANY guest I've ever run under VBox) but it does no good. I still get the default (640x480?) screen resolution after reboot and logging in.

Anyway, the page you suggest does not address the network persistence issue. I might try re-installing the whole mess and see if that"solves" anything. I'm becoming frustrated with Anti-X.

Is there a"save" control somewhere in the control center that will save the screen resolution and network settings across reboots/logins?

skidoo · posted: 2017-10-13 23:44

Your post mentioned both"installed" and"virtualbox", so I'm unsure what your scenario is.
I haven't used virtualbox in a while. I did read (on the forum here?) that the virtualbox extensions weren't working properly.
Someone else may post to fill in the blanks regarding antiX+virtualbox.

D-zaster · posted: 2017-10-14 00:19

I installed anti-X on Virtualbox as a VM, yes. That's my"scenario," as you put it.

Now, that bit about reading on the forum that the extensions arent working -- I would be surprised if this is true. All my other VMs are working with the current extensions. Or do you mean guest additions, which are an entirely different set of code?

I figured out some things. The"networking" service is disabled by default -- anti-X seems to expect that users will use wicd. But the ceni interface IS available, and that's what I had done. Configuration from ceni is NOT persistent for some reason, but OK. Wicd does work correctly and persists across reboots.

The full 1920x1080 resolution is persistent using the vbox guest additions that come with the default (installation) configuration of anti-X. I had tried to update them to the latest, which appears to be the reason my changes to the resolution were not persistent. The only issue with this is that 4.3 is very old GA's and Vbox support is not likely to support this combination (4.3 GA with 5.1 host Vbox software); I'm a long-time user of Vbox and I know that they will tell you -- before any other remedy -- to update Guest Additions to match the host version of vbox.

dolphin_oracle · posted: 2017-10-14 00:38

D-zaster wrote: I installed anti-X on Virtualbox as a VM, yes. That's my"scenario," as you put it.

Now, that bit about reading on the forum that the extensions arent working -- I would be surprised if this is true. All my other VMs are working with the current extensions. Or do you mean guest additions, which are an entirely different set of code?

I figured out some things. The"networking" service is disabled by default -- anti-X seems to expect that users will use wicd. But the ceni interface IS available, and that's what I had done. Configuration from ceni is NOT persistent for some reason, but OK. Wicd does work correctly and persists across reboots.

The full 1920x1080 resolution is persistent using the vbox guest additions that come with the default (installation) configuration of anti-X. I had tried to update them to the latest, which appears to be the reason my changes to the resolution were not persistent. The only issue with this is that 4.3 is very old GA's and Vbox support is not likely to support this combination (4.3 GA with 5.1 host Vbox software); I'm a long-time user of Vbox and I know that they will tell you -- before any other remedy -- to update Guest Additions to match the host version of vbox.

interesting... I'm having zero trouble with the networking in virtualbox. "networking" (configured thru ceni) is the default on the live. wicd is disabled by default. You can edit /etc/default/wicd.conf to change this behavior. This is easy from the liveCD prior to installation, just choose the wicd option from the boot menus.

BitJam · posted: 2017-10-14 01:20

FYI, we are planning to add the following to the desktop-session startup file:

Code: Select all

grep -q"START_DAEMON=no" /etc/default/wicd || wicd-client -t &

so the wicd taskbar icons will be controlled by the the 'wicd" and"nowicd" cheats.

Maybe we should add a wicd entry in the main (legacy) bootloader menu. This should make it more obvious to people.

D-zaster · posted: 2017-10-14 01:51

dolphin_oracle wrote:
interesting... I'm having zero trouble with the networking in virtualbox. "networking" (configured thru ceni) is the default on the live. wicd is disabled by default. You can edit /etc/default/wicd.conf to change this behavior. This is easy from the liveCD prior to installation, just choose the wicd option from the boot menus.

It sounds like you might be doing things differently. I am not running liveCD. I installed to the (virtual) disk in my VM. After install, booted into Anti-X. By default, it seems, wicd is enabled. I tried disabling it, but it made no difference w/r/t persistence. Finally, I configured my networking via wicd and it works. I do not need wireless, obviously, in a VM. I even tried enabling"networking" service, but it makes no difference because it is enabled for the S run level, and I am guessing it remains"up" after that point (but I'm not sure).

This issue of wicd (or NetworkManager on some distros) versus the ceni (or equivalent on those other distros) appears to be an ongoing problem for years.

skidoo · posted: 2017-10-14 03:48

Setting Video resolution on VM

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"./viewtopic.php?f=16&t=4049&p=27103&hilit=video#p27103"
linktext was:"viewtopic.php?f=16&t=4049&p=27103&hilit=video#p27103"
====================================

How to install the antiX 16.1 Alpha to VirtualBox

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"./viewtopic.php?f=16&t=6257&p=45579&hilit=virtualbox#p45579"
linktext was:"viewtopic.php?f=16&t=6257&p=45579&hilit ... box#p45579"
====================================

v--------- tutorial videos:

^---- embedded YouTube-hosted video: https://www.youtube.com/njj6geeCOds

^---- embedded YouTube-hosted video: https://www.youtube.com/adpalUl4LqI

D-zaster · posted: 2017-10-14 11:50

skidoo wrote: Setting Video resolution on VM

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"./viewtopic.php?f=16&t=4049&p=27103&hilit=video#p27103"
linktext was:"viewtopic.php?f=16&t=4049&p=27103&hilit=video#p27103"
====================================

How to install the antiX 16.1 Alpha to VirtualBox

========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"./viewtopic.php?f=16&t=6257&p=45579&hilit=virtualbox#p45579"
linktext was:"viewtopic.php?f=16&t=6257&p=45579&hilit ... box#p45579"
====================================

v--------- tutorial videos:

^---- embedded YouTube-hosted video: https://www.youtube.com/njj6geeCOds

^---- embedded YouTube-hosted video: https://www.youtube.com/adpalUl4LqI

The VM is ALREADY installed with Anti-X. The resolution problem, as I have already posted, is resolved. The networking issue was the one I was stuck on, and that too is now resolved. How would these help NOW?

Maybe you need to get off that skidoo and slow down a bit, dude. Stop and read the thread first.

anticapitalista · posted: 2017-10-14 12:43

Just wondering. Why not use antiX-16.2. It is the latest stable release.
BTW antiX-17 should be released soon.

Ontopic -re ceni. Did you try setting it to use auto or hot-plug, it is in the ceni menu? Try the other and see if it sticks. We are assuming you are using the default repos, is that correct?

rokytnji · posted: 2017-10-14 14:18

How would these help NOW? Maybe you need to get off that skidoo

Mod response:
Future searchers of the same problem on the internet for one. Instead of being snarky. Be nice.
Happy trails, Rok

dolphin_oracle · posted: 2017-10-14 15:52

D-zaster wrote:
dolphin_oracle wrote:
interesting... I'm having zero trouble with the networking in virtualbox. "networking" (configured thru ceni) is the default on the live. wicd is disabled by default. You can edit /etc/default/wicd.conf to change this behavior. This is easy from the liveCD prior to installation, just choose the wicd option from the boot menus.
It sounds like you might be doing things differently. I am not running liveCD. I installed to the (virtual) disk in my VM. After install, booted into Anti-X. By default, it seems, wicd is enabled. I tried disabling it, but it made no difference w/r/t persistence. Finally, I configured my networking via wicd and it works. I do not need wireless, obviously, in a VM. I even tried enabling"networking" service, but it makes no difference because it is enabled for the S run level, and I am guessing it remains"up" after that point (but I'm not sure).

This issue of wicd (or NetworkManager on some distros) versus the ceni (or equivalent on those other distros) appears to be an ongoing problem for years.

No, I'm using it installed in a VM, but just because I haven't seen the problem doesn't mean there isn't one. I didn't even need to set the network up because the wired interfaces were predefined.

D-zaster · posted: 2017-10-17 12:54

The problem has gone away. The only change I made was enabling the VTx in the BIOS. I did not realize it had gotten disabled; I did not do this intentionally, but it may have happened upon one of the many reboots. I notice that this is one of the features that gets reset when the board resets -- but why THAT happens is a mystery.

What tipped me off was the dialog that popped up when starting the VM. It said the system would fail without the hardware virtualization. But this did not occur the preceding times I launched the VM, or I would have changed it in the BIOS sooner, possibly avoiding this whole problem.

Thanks to all who offered considered, constructive criticism.

D-zaster · 17 Oct 2017, 12:59 #15 2017-10-17 12:59

rokytnji wrote:
How would these help NOW? Maybe you need to get off that skidoo
Mod response:
Future searchers of the same problem on the internet for one. Instead of being snarky. Be nice.
Happy trails, Rok

Then the poster might have stated that these were instructions for those who were trying to understand how to perform the basics, not the issue at hand. Obviously, we were far beyond these more basic questions. I think this is clear from the context.

Thank you and Skidoo for your input(s).