You are Here:
Linux Lite 6.6 FINAL Released - Support for 22 Languages Added - See Release Announcement Section



Increasing RAM for Linux Lite guest in Virtualbox leads to desktop login prompt

Author (Read 6817 times)

0 Members and 1 Guest are viewing this topic.

 

Had Matter

  • PayPal Supporter
  • New to Forums
  • *****
  • 8
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: VIrtualbox on Win10
Hope this helps! :)
Thanks again! As Ithere was nothing essential on the virtual HD where Linux Lite was installed, I simply re-installed and will see how it goes.
 

 

Moltke

  • Platinum Level Poster
  • **********
  • 1134
    Posts
  • Reputation: 126
  • Linux Lite Member
    • View Profile

  • CPU: amd athlon 64 x2

  • MEMORY: 4Gb

  • VIDEO CARD: amd radeon hd 6750

  • Kernel: 5.x
Quote
It's an i7-7700K at 4.20GHz, 8 cores, 16 GB RAM. This machine I have the issue with is assigned 3 cores and 2GB RAM. Thanks for suggesting this could have to do with the issue.

Those specs looks good enough.

Quote
this login prompt issue just reappeared.

Did it reappear in a new VM you just created or on the same one?

Quote
Installed in VM according to this guide.

Maybe you should try a different approach; repeat the process but choose not to do something, I'd suggest you may try creating the VM without enabling "PAE/NX”. Leave that one since it's its default configuration unchecked and see how that goes. In any case, you can create a VM as simple as follows:

Open virtualbox, select "new" and follow the instructions, you already made it so you should know the procedure by now. Leave its defaults except for video memory which you can increase up to 256mb instead of the 128mb. You can find instructions on how to on this link https://www.linuxliteos.com/forums/off-topic/my-first-try/msg38800/#msg38800 You  should enable 3D accelaration as well. And if you wish you may assign your initial CPU and RAM config; 3 cores and 2GB respectively. Don't check/change anything else. Now, you could try this and see if it works.

Hope this helps! :)





Without each others help there ain't no hope for us :)
Need a translation service? https://www.deepl.com/es/translator
 

 

Had Matter

  • PayPal Supporter
  • New to Forums
  • *****
  • 8
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: VIrtualbox on Win10
How much RAM do you have at your disposal for this experiment?

 If your machine has something like this

It's an i7-7700K at 4.20GHz, 8 cores, 16 GB RAM. This machine I have the issue with is assigned 3 cores and 2GB RAM. Thanks for suggesting this could have to do with the issue.

BTW anything important is saved on a different (virtual) hard drive than the one Linux Lite is on, so I expect I can always recover any files - though I mostly use VMs to sandbox stuff such as accessing anything to do with money from the Windows PC, so the VMs themselves are disposable. Which appears to be a good thing since this login prompt issue just reappeared.
 

 

Moltke

  • Platinum Level Poster
  • **********
  • 1134
    Posts
  • Reputation: 126
  • Linux Lite Member
    • View Profile

  • CPU: amd athlon 64 x2

  • MEMORY: 4Gb

  • VIDEO CARD: amd radeon hd 6750

  • Kernel: 5.x
How much RAM do you have at your disposal for this experiment? I'm asking because Linux Lite needs only 1GB at the very least to run properly, of course, much more RAM means better performance...well, when it comes to VMs that may not be the case. You can assign lots of RAM and still get almost the same performance as with 1GB. If you're looking for better performance CPU is the key. If your machine has something like this or better yet like this one then you should be able to get a decent performance since you could assign more than one cpu to the VM, but if your machine has a quite old dual-core or even a quad-core processor it won't make much of a difference no matter how much RAM it uses cause you won't be able to surpass the 1 cpu limit unless you want to fry yours. I've been a virtualbox user for quite sometime now, run several VMs; Windows, Linux, android and  even Apple OS and I realized that they should be used for testing purposes only - at least for me - and not to take like a daily/work machine.


Hope this helps! :)
Without each others help there ain't no hope for us :)
Need a translation service? https://www.deepl.com/es/translator
 

 

bitsnpcs

  • Platinum Level Poster
  • **********
  • 3237
    Posts
  • Reputation: 305
    • View Profile
    • Try to Grow

  • Kernel: 4.x
experimenting with RAM amounts is not just something that can be done on the fly.

It is not on the fly but you can right click the machine and clone it, then try changes in the clone first, if they don't work delete the clone and make a new clone, it takes around < 1.5 minutes to make the clone etc.
So it saves a lot of time compared to making a new machine.
 

 

Had Matter

  • PayPal Supporter
  • New to Forums
  • *****
  • 8
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: VIrtualbox on Win10
Thanks - I didn't get to try your suggestion, the issue apparently went away after a couple of shutdowns (Virtualbox force shutdown).
 

 

trinidad

  • Platinum Level Poster
  • **********
  • 1463
    Posts
  • Reputation: 212
  • Linux Lite Member
    • View Profile
    • dbts-analytics.com

  • CPU: i7 4 cores 8 threads

  • MEMORY: 16Gb

  • VIDEO CARD: Intel HD graphics

  • Kernel: 5.x
Lightdm display: Other>
Type: linux
Hit Enter
Password> leave blank
Hit Enter again.

The UI doesn't always respond to mouse clicks, and requires two return/enter. You must return/enter linux as user name first, and then return/enter password as blank. Not particularly intuitive, just how it is. Confused me at first.

TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.
 

 

Had Matter

  • PayPal Supporter
  • New to Forums
  • *****
  • 8
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: VIrtualbox on Win10
If not the username may need changed to linux with no password.
Double-posting to add: username linux with no password does not work.

I made a new VM and now have the issue again after making some changes (and recklessly updated the guest additions to the latest version from virtualbox.org) and got locked out again. It appears I'm locked out of the machine unless I can get past this login prompt.
 

 

Had Matter

  • PayPal Supporter
  • New to Forums
  • *****
  • 8
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: VIrtualbox on Win10
Thanks! Yes, there is a stickied thread about that issue, but none of the suggestions there work. What then happens is the password and/or user gets rejected and the prompt pops back up.

Likely the fastest road in my case is to define a new VM with the amount of RAM I want, would be up and running in ½ an hour. But if that is necessary, experimenting with RAM amounts is not just something that can be done on the fly.
 

 

firenice03

  • Rockin' the FREE World
  • Global Moderator
  • Platinum Level Poster
  • *****
  • 1848
    Posts
  • Reputation: 284
  • Linux Lite Member
    • View Profile

  • CPU: AMD E2//Atom X5//AMD Phenom II X2

  • MEMORY: 4Gb

  • VIDEO CARD: AMD Mullin Radeon R2//Intel//AMD/ATI RS880

  • Kernel: 5.x
Can't say persay why.. But if you can't login, the Live enviroments at least in previous versions would occasionally display a login prompt especially on laptops; password was blank/empty. Hitting enter would bypass.
If not the username may need changed to linux with no password.


May atleast allow you access back in the system to further troubleshoot..
Good luck
LL4.8 UEFI 64 bit ASUS E402W - AMD E2 (Quad) 1.5Ghz  - 4GB - AMD Mullins Radeon R2
LL5.8 UEFI 64 bit Test UEFI Kangaroo (Mobile Desktop) - Atom X5-Z8500 1.44Ghz - 2GB - Intel HD Graphics
LL4.8 64 bit HP 6005- AMD Phenom II X2 - 8GB - AMD/ATI RS880 (HD4200)
LL3.8 32 bit Dell Inspiron Mini - Atom N270 1.6Ghz - 1GB - Intel Mobile 945GSE Express  -- Shelved
BACK LL5.8 64 bit Dell Optiplex 160 (Thin) - Atom 230 1.6Ghz - 4GB-SiS 771/671 PCIE VGA - Print Server
Running Linux Lite since LL2.2
 

 

Had Matter

  • PayPal Supporter
  • New to Forums
  • *****
  • 8
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: VIrtualbox on Win10
Using Linux Lite in a Virtualbox VM. Increased the RAM for the VM. After this booting the VM ends in a login prompt (to the desktop environment?) with user pre-filled as "linuxlite".

It looks as if something was reset when Linux Lite discovered the RAM increase - rolling the RAM increase back does not get rid of the login prompt. I assume this login was previously done behind the scenes with some stored password.

As it does not seem possible to skip this login, and the only visible desktop component is the wallpaper, the VM is stuck.

Is there a fix for this? Or is it a bug?

Details:
Linux Lite 4.0 64 bit downloaded from Linux Lite site.
Running on VirtualBox 5.2.16 r123759 (Qt5.6.2) on Windows 10.
Installed in VM according to this guide.

PS: Correct subforum? Lemme know if not and I'll try and move it
« Last Edit: October 29, 2019, 09:51:20 PM by firenice03 »
 

 

-->
X Close Ad

Linux Lite 6.6 FINAL Released - Support for 22 Languages Added - See Release Announcement Section