In terminfoemit the cvviscnorm or civis string e. The corresponding termcap entries are vsve and vi. These setting will not survive a terminal resetso you may find that it doesn't survive the launching of many full-screen applications.
You can overcome this difficulty by adding the cursor configuration changing sequence to your terminal's reset string. You can see that this undoes the effects of the above setting. You need to change cnorm to the above sequence in order for the TUI applications to reset the cursor to your preference. More info on this by Gilles but if you are looking for a quick fix try this:.
However, I noticed that sometimes after boot the cursor is still blinking. It would be good to know the correct way to permanently turn off cursor blinking via sysfs on a modern systemd system, does anyone have any tips?
Some experimentation showed that the 'c' at the end works better than 'c' listed above, it produces a white rather than grey cursor. To do so:. There should be lines that contain getty or agetty or similar. An example is:. A better alternative is to put ESC[? Doing this using vi is as follows:. Another alternative is keeping the hardware cursor instead of using a software cursor and stop blinking of the hardware cursor and make it a block cursor. Add ESC[?Review your favorite Linux distribution.
Welcome to LinuxQuestions. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Subscribe to RSS
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Are you new to LinuxQuestions.
If you need to reset your password, click here. Having a problem logging in? Please visit this page to clear all LQ-related cookies. Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.
They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Click Here to receive this Complete Guide absolutely free. Fresh debian install, boots to blank screen with blinking cursor Hello all, I finally got debian to install after three days of fatal grub errors. Figured out that I had to delete the partitions and recreate them instead of just reformatting.
A little information: Installed stable debian via debian The issues: First, no grub menu, boots directly into debian and I don't know how to fix that.
Second and most important, it boots to a blank screen other than a blinking cursor in the upper left hand corner that won't accept any input.
Please help, this has been quite an ordeal. I have a Linux book to help me learn the ins and outs but I need a working distro to follow along. Thanks in advance. Last edited by jacnj; at PM. I started aptitude to check installed packages and am seeing gnome and x11, try to startx and get: Code:.
From what I've read, this blinking cursor screen is presented by Ubuntu itself and not Grub, so I assume the boot process gets halted for some reason. Has anyone any guidance on how to diagnose this issue or what the cause is likely to be? Normally I need to press the reset button to reboot the PC and often it will reboot fine.
The fact that it is intermittent is what confuses me. It's been a while, mainly because my server has been up for a long time. It looks like I've captured a recurrence of this issue, I copied the messages file and the dmesg file and had a look where processing seems to have stopped and found the messages below.
I'm going to do some research on Google etc. I should mention that the ondemand governor failed message happens on successful boots but the other two don't appear to. Hold shift during boot, then hit e to edit the GRUB entry. Remove the part that says "quiet splash" and replace it with "text" to see what's happening during boot.
In my case, the blinking cursor was all I would ever get. No boot. It was upon installing a fresh Ubuntu Minimal. My system has 3 drives. Choose NO. Finally, I had to format my GB drive with a partition table of "gpt". That's the way things are done with GPT.
Second partition was my 3. Third partition was the remaining space formatted as "ext4". BTW, you have to choose Expert install from the menu at the beginning of the installation to do all this and format your HDD "manually" not "guided". I have had this problem in the past, and found that it appears to happen on some kernels and not others although I have not had this issue since upgrading to Meerkat. But often times I found I would have to select a prior Kernel to load into Ubuntu properly.
I like maco's answer, but another thing I'd check is that your hard drive is healthy. I've had that problem quite a few times now, but I could distinguish at least three different variants:.
Shell Programming and Scripting
This has led me to believe that when you see what you're describing, the actual problem is that the quiet boot option is hiding "something" from you. For instance, I could track down one of my incidents to the system recovering not the usual routine check my harddisk. I have since removed the quiet option from my grub entries. I was able to switch to a VT with alt-F1, so the machine was alive but had switched to vt7, despite no X being enabled. I had a similar issue in the past using the recommended version of a proprietary nVidia driver with a certain video card.
I'm not able to type any characters at the Git-Bash command line; all it shows is a blinking cursor. Git Bash was working fine yesterday, but I'm not able to do anything on it now.
What can I do to fix this? I found the answer to a problem with similar symptoms. I'll include it here for someone who finds this page looking for an answer, as I did. In my case, the cursor didn't move, or show my typing onscreen. However, it actually executed the command if I pressed Entereven though it looked like I didn't type anything in!
Turns out it can be an issue for any shell program cmd, git bash, etcnot necessarily just a Git Bash issue. It looks like Ctrl-C or Ctrl-Z can occasionally result in the terminal not echoing commands to the screen, depending on what process was running at the time it was killed.
I have a similar problem, I can type commands and it will execute them, but I cannot see what I type. I know this is may be late, but in case someone do like what happens with me. Then I tried to use git bash after while,I found only this blinking cursor. I tried many times to reset or even close it; however closing it caused an error so I got afraid of losing my work.
Learn more. Git Bash won't let me type anything, just shows a blinking cursor Ask Question. Asked 5 years, 2 months ago. Active 8 months ago. Viewed 20k times. SherylHohman 9, 13 13 gold badges 53 53 silver badges 66 66 bronze badges. Jeffery Jones Jeffery Jones 1 1 gold badge 3 3 silver badges 4 4 bronze badges. I'm afraid there is little Stack-Overflow users can do to help you Have you tried closing and relaunching Git Bash? Or rebooting your machine? I have noticed that when you move the cursor, and then move it back to the end of the line, it does not let you type anything until you hit Backspace.
Strauss Jan 22 '15 at Yea i tried to relaunching, rebooting and uninstalling and reinstalling, but it gives me nothing but the black blank screen with a blinking cursor, its so weird. This oddly started happening to me too. In my case, I can type commands, and they will execute; I just cannot see what I type.
Active Oldest Votes. SherylHohman SherylHohman 9, 13 13 gold badges 53 53 silver badges 66 66 bronze badges.Kali can run on many mobile phones and Raspberry pi, so hardware is not a big deal for the basics. That said, and while I understand virtualization is the way to go, you have two options I see here.
Get answers from your peers along with millions of IT pros who visit Spiceworks. Best Answer. We found 3 helpful replies in similar discussions:. Fast Answers! For a start set the BIOS time correctly for your location and try again. Was this helpful? Pure Capsaicin. Rod-IT Aug 03, Install Kali on the hardware direct 2. Use the live CD What would you gain in this setup by installing it on top of Lubuntu? See all 3 answers. Popular Topics in Desktop Virtualization. Spiceworks Help Desk. The help desk software for IT.
Track users' IT needs, easily, and with only the features you need. I assume you didn't take a snapshot to roll back from your install? No backups to restore? Can you break the boot sequence and run a disk check or repair? Then it is going to be more difficult to guide you. You need to break the boot sequence and run disk checks to ensure the state is consistent. Rod-IT wrote: Then it is going to be more difficult to guide you.
Jrojas23 This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Please mark your post as best answer so we know this is closed.
Replace Attachment. Add link Text to display: Where should this link go? Add Cancel. Insert code. Join me to this group.Linux/Ubuntu not Booting up FixED!!!!
Read these nextMenu Menu. Search Everywhere Threads This forum This thread. Search titles only. Search Advanced search…. Everywhere Threads This forum This thread. Search Advanced…. Log in. Category 1 Category 2 Category 3 Category 4. Support UI. X Donate Contact us. New posts Trending Search forums. What's new. New posts New profile posts Latest activity. Current visitors New profile posts Search profile posts Billboard Trophies.
Question of the Week: What are some tricks to getting the best performance out of our home computers? Kali Linux booting to a black screen with flashing cursor. Thread starter ElliotPoots Start date Jun 14, Sidebar Sidebar. Forums Software Open Source.
ElliotPoots Prominent. May 3, 11 0 0. I've been having issue installing Kali the past few days. I finally got it working after GRUB kept showing a normal. When I try and boot to this drive, it simply shows a black screen with a flashing cursor in the top left.Today we are going to do a main site post on how to fix an issue whereby the Ubuntu installer finishes but upon reboot only a blinking cursor and black screen is seen. This has happened to many users on several occasions so we thought we would take a quick look at a somewhat common installation issue and a quick way to fix it.
This guide was prompted by a forum post on this subject recently. We figured it was worth doing a quick guide on. The problem occurs after installing Ubuntu and removing the installation media.
At this point, the machine reboots and one sees a blinking screen with only a cursor as can be seen below:. Generally, the reason this occurs is due to the Ubuntu installation placing the GRUB bootloader on a partition that is not being booted to.
This can happen for a variety of reasons. We will have a review of the Zalman unit shortly but the device has a mode that allows a hard drive to emulate both an optical drive and have a normal hard drive volume accessible. As a result, the machine did not find the installation until BIOS settings were changed to boot from the correct drive. Here are a few quick tips for remedying the above blinking cursor after Ubuntu installation issue:. The above may not be the fanciest guide out there, but it will solve this problem a vast majority of instances where it is seen.
Hopefully these steps will help users quickly troubleshoot the blinking cursor after Ubuntu installation issue. I had this happen a couple of times while installing open stack using crowbar. It drove me nuts! Hope this helps. Thank you for this article. Not to mention the install media device… and 2 If the system would say something similar to not able to find the GRUB or anything it would have saved me hours of work.
Seems like a bug to me. Thanks a ton man. I was going nuts for over a week with this issue. And this little trick you shared worked. Thanks once again. Sign me up for the STH newsletter! Saturday, April 18, Cursor Blinking Screen.