I am testing Parrot OS and would like to put it in full screen mode in Hyper-V
Tried seeking through parrotsec documentations but couldn't find any reference.
Found a solution.
Since Parrot OS is using Debian, I just tried to modify the Grub Setting by adding video=hyperv_fb:1440x900
nano /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=hyperv_fb:1440x900"
CTRL x + Y + Enter
sudo update-grub
sudo reboot
Then works as expected now. Thanks!
Another option I found is to enable enhanced session mode on Hyper V. On host run in powershell:
Set-VM "YourVMName" -EnhancedSessionTransportType HVSocket
On guest parrot os I used this script:
https://raw.githubusercontent.com/mimura1133/linux-vm-tools/master/kali/2021.x/install.sh
Bonus is clipboard between host and guest also works after this.
Related
I am new to Ubuntu 18.04. It has been a long time that I have not updated anything new on my current OS which is Loki (interestingly, besides Loki does not allow ppl to upgrade Juno).
For some reasons, I have to install another Linux OS on my machine, which is ubuntu 18.04 - the minimal installation. Although everything works perfectly to Ubuntu, it makes me cannot log in to my main OS.
Description of an issue: After selecting a boot of elementary, I log in my account on a log-in page of Elementary. It does not show anything else and move back to the log-in. Another try with a guest account (with no password), still the same problem.
Because most of my data and work in Elementary, I have to find a way to solve this problem. Is there anyone here giving me a hand? Thank you very much.
I ran into same problem once.
Login into tty mode by Ctrl+Shift+F1,and enter:
sudo dpkg --configure -a
sudo apt-get install ecryptfs-utils
sudo reboot
And I was able to login
Trying tty mode by Ctrl+Shift+F1, I was able to log-in in a terminal. Turn out that the Ubuntu has used almost the left memory to load an OS. By removing some files by the command rm -rf [filename] to release around 2GB, I was able to have everything back. It was freaking for a while. Phewww...
I try to build a reproducible automated build environment based on Debian 8.1 Jessie.
I created a boot iso image based on a netinstall image and put a preseed.cfg file in int for automatic installation.
I managed to get it bootable with BIOS and UEFI and can install a KDE Developer Debian in VMWare Workstation 11 fully automated.
I have also a server iso image to install a debian Server with Jenkins, both with BIOS and UEFI Boot.
But after the installation, the Version with UEFI Boot shows a black Screen when started.
I can blindly log in, start the gui with "startx" and see my installed xfce desktop. When i quit xfce the console is usable and visible.
I tried suggested bootparameters "nomodeset" and "vga=Linux" that i found with google to no avail.
I also tried to debug the boot prozess, to find out which command leads to a blank screen, but i did not find the right place to delay the processes at bootup so i can see when the messages dissapear (quiet bootparameter was removed :-)
I also tried to reset the console to no avail.
Can anybode point me to a tool that does the same "switching" like X so the console is useable?
Can anybody give me some hints how to debug the bootprocess to find out which command is causing this behaviour?
I dont want to install X because this should be a headless server system later.
I managed to get my system to boot using the kernel command line modprobe.blacklist=vmwgfx, or placing 'blacklist vmwgfx' in /etc/modprobe.d/*.conf
I assume it is some bug in the vmwgfx module, however as this workaround works for me I have no immediate need to investigate further.
I have been trying maybe weeks now to figure out how to configure VirtualBox to have 1366x768 resolution on a linux guest, which is on a windows 8.1 host.
My configuration:
Windows 8.1 as host
Linuxmint 17.1 as guest (tried ubuntu and debian too but no luck)
Virtualbox 4.3.26 and its extension pack
Laptop is powerful with 16GB ram and 4GB Nvdia
My problem is that it doesn't matter what I used, nothing worked.
Please do not post the answers on most known websites, I tried them already.
Once your VM is started, you need to run the VBox Linux Guest Additions.
First try to run it from the VirtualBox window's menu:
Devices >> Insert guest Additions CD image...
and follow the instructions.
If that fails, open a terminal and go to the directory where you CD reader is mounted (/run/media/ on Fedora or /media/ on Ubuntu for example).
Then type command sudo ./VBoxLinuxAdditions.run
Complete instructions can be found on the VirtualBox user manual
Once Guest Additions are installed, reboot your virtual machine. You should be able to resize your screen to your heart's content.
I installed the new VirtualBox 5.0.0_BETA2 and it solved my all problems. Great product is getting ready! Cant wait the latest release. more than a PERFECT software. Now you can remove top bar and/or bottom bar easily. Show what you need.
If you are having problem like me with 1366x768 I recommend you to install latest versin of VB even if it is Beta!
I have Ubuntu, version 12. I installed ATI driver and I'm getting an error running in low graphics mode.
I needed to install the driver because every time I update or upgrade Ubuntu, right after installing the packages the system runs in low graphics mode.
The answer here also couldn't help me.
Graphics card model: ATI Radeon HD 3600
Installing fglrx also didn't help. The ATI driver is still installed and it still runs in low graphics mode. What should I do?
First, you should understand that your graphics manager is messed up and that is what you want to fix. Now; here is a solution to your problem:
Here is a simple guide showing you how to do it step by step:
A step by step guide to fixing "your system is running on low graphics"
When you turn off your computer, reboot and hold these three keys:
CTRL + ALT + F1
This will open the terminal where you can enter commands that I am going to show you below:
sudo apt-get update
Next enter the following command:
sudo apt-get -d install --reinstall gdm
Next enter the following command:
sudo apt-get remove --purge gdm
Next enter the following:
sudo apt-get install gdm
Almost done; When asked to choose, please select GDM and then finally:
sudo reboot
That is all you need to solve this problem!
Ok. Let me try to help you :D
-Go to Recovery mode
-Enable network (so you have internet connection)
-Go to Root option (Recovery mode)
-When you are in terminal delete lightdm type without brackets {sudo apt-get remove --purge lightdm}
-Then type without brackets {sudo apt-get install lightdm} (wait to install it)
-Then type without brackets {sudo service lighdm start}
-When it's finished type exit (you will get back to Recovery console)
-Then go on third option dpkg (Repair broken packages)(confirm with Y)
-When it's finished with installing packages type without brackets {sudo reboot}
-After reboot you will have back your Ubuntu! :D
I solve this problem after 1 day... Im a new user :D
Almost forgot i have Ati Radeon HD6770 graphic card, if you have Nvidia try it... Hope this was helpful!
Another possible issue could be installing new programs in bin. I am not sure if that what is causing you the problem but I faced this issue because of the same issue. If I understand correctly, bin is supposed to contain only executables. By mistake I moved a whole big program to bin and when I restarted the system, I saw this error. A simple solution that I found is the following. Say you have moved the big folder ABC to bin.
Start terminal by typing Ctrl+Alt+F1 and login with your username and password.
Login to root by typing
sudo su
and providing password.
go to bin by typing
/usr/bin
type
ls -lrt
This last command will show all the files chronologically. See last few of them. One of those, say ABC, must be the one that moved by mistake to bin.
Remove that by typing
rm -r ABC
and then restart by
sudo reboot
And you get your graphics back!
You can try and turn off the switchable graphics in the BIOS:
after that, it will be possible to use the Intel video card only with proper drivers on Ubuntu.
Here is the source: http://thegeekyland.blogspot.com/2014/07/ubuntu-1404-lenovo-g510.html
In any ubuntu OS version 12.04,14.04 configured with the old graphic card ATI/RS690
change the setting as below
etc/default/grub/
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset "
sudo update-grub
Restart
I have a raspberry pi running arch linux connected to the TV and want to run commands on that screen by SSH'ing from my Ubuntu machine elsewhere.
I have tried running the command SSH -Y root# and starting xclock as a test. However I get the following error:
No protocol specified
Error: Can't open display: :0
I then tried running "export DISPLAY=:0" on the arch machine, but this doesn't solve the issue.
I have X running fine and can see it on the TV and I have edited the file /etc/ssh/ssh_config to allow X11 forwarding.
Anyone know what I am doing wrong?
Many thanks
The ArchLinux wiki has some good instructions on setting things up. I struggled for a while until I found them, but for me the key was to set up SSH forwarding within sshd_config (most distros seem to enable this by default, but Arch doesn't).
Once you've enabled X forwarding in SSHD, I also found it helpful to install the dummy video driver for Xorg ("pacman -S xf86-video-dummy"), which gets rid of irritating errors about missing the RANDR extension. This might not be necessary if you already have it running a real X server locally on the Pi - personally, I'm running mine completely headless.
I've found that I don't have to worry about setting up the DISPLAY variable, or xhost, when running with 'ssh -X' from an iMac. I'd expect Ubuntu to behave the same.
looks like an authentication problem. The answer used to be
xhost +
on the console of the X display. Might help.
You probably want to set
export DISPLAY=[IP_ADDRESS_OF_ARCH_BOX]:0
on your Ubuntu box, then when you run xclock from your Ubuntu box, it'll forward the screen to the Arch box.