Linux HowTo: Kali Linux 2017 W7 First boot black screen with cursor

Original Source Link

After installing Kali Linux 2017 W7 successfully from a usb, I restart my computer and boot into the hard drive. All I see is a black screen with a cursor blinking in the top left. I’ve tried mounting the image to my usb using Rufus (both ISO and DD) and win32 disk imager. Why am I booting into a black screen with a cursor?

May be Relevant:
I have windows installed on a different hard drive.
I did not put GRUB on the master boot record, I chose to put it on the hard drive that I installed Kali linux on.

Specs:

  • Motherboard: Asus sabertooth z77
  • Graphics card: 2x GTX 780
  • 2 Monitors

I had this same problem when I installed kali on my virtual box. The exact same thing was happening. I switched my view to scaled view and then kali appeared. I think you’re in the same situation. Boot your system. Then go to BIOS. Change the view to autoscale.

Tagged : / /

Making Game: Kali Linux 2017 W7 First boot black screen with cursor

Original Source Link

After installing Kali Linux 2017 W7 successfully from a usb, I restart my computer and boot into the hard drive. All I see is a black screen with a cursor blinking in the top left. I’ve tried mounting the image to my usb using Rufus (both ISO and DD) and win32 disk imager. Why am I booting into a black screen with a cursor?

May be Relevant:
I have windows installed on a different hard drive.
I did not put GRUB on the master boot record, I chose to put it on the hard drive that I installed Kali linux on.

Specs:

  • Motherboard: Asus sabertooth z77
  • Graphics card: 2x GTX 780
  • 2 Monitors

I had this same problem when I installed kali on my virtual box. The exact same thing was happening. I switched my view to scaled view and then kali appeared. I think you’re in the same situation. Boot your system. Then go to BIOS. Change the view to autoscale.

Tagged : / /

Linux HowTo: Can’t install Windows 7 from USB (GRUB)

Original Source Link

After 7 years of using windows 7 i decided to reinstall because it slowed down considerably. Used Rufus to create a USB using the ISO that i used to install it in 2013. But now when i try to boot through the USB i get the following screen:

enter image description here

Why is that?

Additional info:
I have Xubuntu in another partition in the same drive (Installed this year). GRUB 2 as the bootloader. Maybe that’s the issue?
ASUS motherboard.

It looks like a problem with the image on USB.
Please make sure you are using newest version of Rufus, however I found it not very reliable so I moved on to Etcher recently:
Balena Etcher

Xubuntu shouldn’t be an issue, however the GRUB would be most likely overwritten, so after installing windows, you would need to start Xubuntu from recovery media to re-install GRUB. otherwise you will no longer be able to start Xubuntu. You would also need to update GRUB with the information where it should look for windows.

Windows 7 is no longer supported, do you know that you can still upgrade it to windows 10 for free?

I get the feeling that you have two issues:

  1. Your display cannot handle basic graphics modes.
  2. You created a UEFI targeted bootable drive in Rufus instead of creating a BIOS/Legacy one.

No idea how you can ago around fixing the first issue, but for the second one, you may want to read this and recreate your USB in Rufus after making sure Target system is set to BIOS or UEFI-CSM.

Incidentally, I’m pretty sure that, if your monitor could show it, it would display a message that tells you that you are trying to boot a UEFI-only bootable drive in BIOS/Legacy mode, and that you need to recreate it to target BIOS/Legacy in Rufus so that it works.

Tagged : / / /

Making Game: Can’t install Windows 7 from USB (GRUB)

Original Source Link

After 7 years of using windows 7 i decided to reinstall because it slowed down considerably. Used Rufus to create a USB using the ISO that i used to install it in 2013. But now when i try to boot through the USB i get the following screen:

enter image description here

Why is that?

Additional info:
I have Xubuntu in another partition in the same drive (Installed this year). GRUB 2 as the bootloader. Maybe that’s the issue?
ASUS motherboard.

It looks like a problem with the image on USB.
Please make sure you are using newest version of Rufus, however I found it not very reliable so I moved on to Etcher recently:
Balena Etcher

Xubuntu shouldn’t be an issue, however the GRUB would be most likely overwritten, so after installing windows, you would need to start Xubuntu from recovery media to re-install GRUB. otherwise you will no longer be able to start Xubuntu. You would also need to update GRUB with the information where it should look for windows.

Windows 7 is no longer supported, do you know that you can still upgrade it to windows 10 for free?

I get the feeling that you have two issues:

  1. Your display cannot handle basic graphics modes.
  2. You created a UEFI targeted bootable drive in Rufus instead of creating a BIOS/Legacy one.

No idea how you can ago around fixing the first issue, but for the second one, you may want to read this and recreate your USB in Rufus after making sure Target system is set to BIOS or UEFI-CSM.

Incidentally, I’m pretty sure that, if your monitor could show it, it would display a message that tells you that you are trying to boot a UEFI-only bootable drive in BIOS/Legacy mode, and that you need to recreate it to target BIOS/Legacy in Rufus so that it works.

Tagged : / / /

Making Game: grub rescue: All paritions have unknown filesystem

Original Source Link

Similar to this post however it did not solve my issue. I have made a windows recovery USB but it does not show up when on ls command, and I do not see a way to search for new partitions.

Weirdly i’m not able to run any commands other than ls and set(of the commands that ive tested).

For some background I had windows 10 and manjaro on my system. I stupidly deleted the manjaro partition and now I’m here. If I can remove the manjaro boot loader in the efi parition will that solve the issue?

Tagged : / / /

Linux HowTo: GRUB menu customization (change menu appearance)

Original Source Link

In my GRUB (GRUB 0.97) menu the selector became invisible (changed of inversion color). I would like get my selector bar back and by the way customize a bit grub menu to be more fancy with colors. Where i could change the default b&w schema? Do i need add directives in /etc/grub.conf ? or rather use some tool to change grub menu appearance? In fedora repo i found grub-customizer-3.0.4 but i use centos and it seems the only way is to change grub files manually.

You should be able to just install using yum install grub-customizer.

If not try this Grub customizer for CentOS

Tagged : /

Making Game: GRUB menu customization (change menu appearance)

Original Source Link

In my GRUB (GRUB 0.97) menu the selector became invisible (changed of inversion color). I would like get my selector bar back and by the way customize a bit grub menu to be more fancy with colors. Where i could change the default b&w schema? Do i need add directives in /etc/grub.conf ? or rather use some tool to change grub menu appearance? In fedora repo i found grub-customizer-3.0.4 but i use centos and it seems the only way is to change grub files manually.

You should be able to just install using yum install grub-customizer.

If not try this Grub customizer for CentOS

Tagged : /

Making Game: Unable to boot FreeBSD 12.1 using GRUB

Original Source Link

This is not a duplicate question to https://unix.stackexchange.com/questions/109272/add-freebsd-to-grub2-boot-menu or Cant boot FreeBSD 10.1 using grub2.

Firstly I tried the mechanism suggested in https://unix.stackexchange.com/a/110091/377563 but that does not work. GRUB shows FreeBSD as an option but says that kfreebsd is not a valid command or something of that sort.
I am presently trying the code mentioned in https://help.ubuntu.com/community/Grub2%20Other%20Os#Direct_Kernel_Boot. However, sudo update-grub or sudo grub-mkconfig -o /boot/grub/grub.cfg shows a bug which was noted in the previous try as well, saying that it has Found unknown Linux distribution on /dev/sda16 which is where FreeBSD is supposed to be.

Tagged : / / / /

Making Game: Grub Rescue After Deleting Linux Partition Windows 10

Original Source Link

I need some help for fixing grub rescue mode. I was using Windows 10 Pro on my Lenovo-Ideapad 310 laptop.I installed Ubuntu With Dual Boot And Stupidly Deleted Linux Partition. I didn’t fix mbr. Now I’m getting an error while turning on

error: unknown filesystem.
Entering rescue mode…
grub rescue>

I tried to boot with Windows DVD it doesn’t works. Says, unknown filesystem. My DVD is Good. I am not a expert please reply with detail.Thanks in advanc, stay home stay safe.

Tagged : / / / /

Server Bug Fix: Grub2 reports physical volume pv0 not found when probing/installing

Original Source Link

I upgraded a Ubuntu Maverick to Precise server but I get the following error while updating grub:

error: physical volume pv0 not found.

Now, for my system I have /dev/sda through /dev/sde

  • /dev/sda1 is a Linux partition for /boot
  • and /dev/sda5 is an LVM partition
  • /dev/sdb through /dev/sde are PVs for the LVM

By looking at my vg config, pv0 is /dev/sda5

I only have one Volume Group called “ns2” where the root (/) and some other logical volumes for the system.

I tried looking on the Web for help but they said I should upgrade to Grub2 as it is better to LVM support. I did that and I get the same error.
I haven’t rebooted the server but I have the feeling it is not going to boot.
Still, I want to fix that error.

My boot partition is not in an LVM volume so even grub1 or grub2 should look at it without problems.

Any ideas?
I just tried reinstalling grub but I get the same error, still it seems to go “fine”.

What can I check before rebooting?
This server is in another location and I have no remote access to the console, so I want to go there ready if something needs to be done.

Edit: Added more information http://pastebin.com/Smr1pB8W

Edit: Added pvs information http://pastebin.com/yubMd232

It sounds like you didn’t reboot between upgrading LVM2/GRUB and the kernel.

You will want to “pin” an old grub version long enough to reboot your system into a current kernel version. At that point you should be good to unpin, upgrade grub and everything should be kosher.

Add this to /etc/apt/preferences:


# Force grub to 1.98+20100804-5ubuntu3
Package: grub-pc
Pin: release n=maverick
Pin-Priority: 1000

Now

 apt-get update && apt-get -s dist-upgrade

Assuming you get a line like Inst grub-pc [ 1.98+20100804-5ubuntu3]
....
(and the resulting dependency shuffling doesn’t break your
system… Watch for things like libc downgrades) you can apt-get dist-upgrade to force grub back to sanity. I would suggest running
update-grub one more time to make sure you’re not walking into an
un-bootable situation.

Let me know how it goes 🙂

Tagged : / / /