You are not logged in.
Pages: 1
Hi!
i just finished the basic installation of Arch Linux on My Acer Aspire V5 Netbook. After the basic installation , I installed the X Display Server , ATI Video Card Driver , XFCE Desktop Environment and LightDM Display Manager. Now I reboot my netbook , I get this error telling "kvm disabled by the bios" and everything halts. On Googling ,some suggested to turn "Virtualization" on from the BIOS set up. But I don't see any such option in the F2 setup screen. So please help!
Offline
http://www.youtube.com/watch?v=4Q8aOFKts7s
you have it at 1:48 (but I really don't think that halts your system.
“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson
Offline
Hi! Thanks for the reply! But I don't have such advanced options in my BIOS screen. All I have is Information,Main,Security,Boot,Exit. I did not have any problem initially ,I was able to install Arch Linux successfully and reboot the laptop..I was able to login as root and everything worked fine. Why am I not able to do that now ?
The system didn't halt actually. I used Alt-F2 and was able to login as root in another screen. But if I press Alt-F2 again , I go back to the screen where I get the problem "kvm disabled by the BIOS"
Last edited by thegyro (2013-12-13 14:37:18)
Offline
Contact acer support and ask then how to enable it?
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
But why didn't I get a similar error as soon as I finished installing Arch on it ?
Offline
Probably because the kvm module is not being loaded.
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
(but I really don't think that halts your system.
I have seen the error in past but arch would run fine.
Offline
Probably because the kvm module is not being loaded.
My Arch is running fine ,though the error KVM disabled is still there at the back . Is this a problem I should worry about or can I just neglect it ? What is the purpose of this module ?
Offline
if you're not using virtualization it probably doesn't matter
Offline
I've seen this message many, many times on different machines, and it's never caused any problems. The KVM module is in the stock Arch kernel; unless you have the vendor-specific virtualization stuff enabled in the BIOS/EFI setup menu, the KVM module won't load. The message is just telling you you can't use KVM on your system, which only matters if you really, really want to use KVM on your system.
EDIT---@OP: Since this is a new installation, have you ensured that you're booting into the correct target/runtime?
Last edited by ANOKNUSA (2013-12-15 15:21:08)
Offline
I've seen this message many, many times on different machines, and it's never caused any problems. The KVM module is in the stock Arch kernel; unless you have the vendor-specific virtualization stuff enabled in the BIOS/EFI setup menu, the KVM module won't load. The message is just telling you you can't use KVM on your system, which only matters if you really, really want to use KVM on your system.
EDIT---@OP: Since this is a new installation, have you ensured that you're booting into the correct target/runtime?
I am sorry but what does booting into the correct target/runtime mean ? Which is the correct one and how do I check it ?
Offline
By default, the system boots into multi-user.target, dropping the user at the command line after boot. If you're trying to boot into LightDM and log in from there, you'll need to enable lightdm.service (if you haven't already) and set systemd to boot into graphical.target instead. It may be the case that systemd is starting lightdm.service (if you enabled it), but booting into multi-user.target; hence the blank screen on TTY1, but login prompt on other TTYs.
Offline
If you are at all familiar with the old SysV way of doing things, then the target would be equivalent to /etc/inittab's runlevels. Use the search engine of your choice to learn more about systemd targets (and systemd units in general). Of course, systemd has great documentation as well, so you could reference the man pages too.
Basically what everyone is trying to tell you here is that the error, which you seem to have concluded is the root of your issue here, most likely has nothing to do with your inability to boot. You need to access the system's journal and see if you can determine what exactly is preventing the machine from coming up properly.
Offline
Pages: 1