Red Hat / Fedora :: Only Get Blank Screen Alone With Blinking Cursor
Nov 13, 2010
After installation of Fedora core6, only i can access to Graphical interface(ctrl+alt+F7) only. When i press ctrl+alt+F1 ,F2, etc.only get blank screen alone with blinking cursor. My system configuration is PIII, Intel 810 chipset.
Whenever I boot the system after the fedora 12 bubble fills up I see a blank screen with a blinking cursor. Though I am able to access tty2 by pressing alt+ctrl+F2.
I have seen the boot logs and it shows a warning:
Code: Warning: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/
I have an ATI Radeon 3xxx series card and I have recently installed mesa-dri-drivers.x86_64. I guess the blank screen problem is because xorg for fedora 12 doesn't support these drivers.
I want to remove this package using yum, but when I try to do it using "yum remove" it shows 95 packages that would be uninstalled with it. I don't want to remove those packages as it has some that I use like Konversation.
how do I remove mesa-dri-drivers and what were the drivers that were being used before I installed mesa.
Whenever I boot the system after the fedora 12 bubble fills up I see a blank screen with a blinking cursor. Though I am able to access tty2 by pressing alt+ctrl+F2. I have an ATI Radeon 3xxx series card and I have recently installed mesa-dri-drivers.x86_64. I guess the blank screen problem is because xorg for fedora 12 doesn't support these drivers.
I want to remove this package using yum, but when I try to do it using "yum remove" it shows 95 packages that would be uninstalled with it. I don't want to remove those packages as it has some that I use like Konversation. Also I am not able to install anything using YUM. It gives the following error:
Code: [error 14] PYCURL ERROR 6-"" I work behind a proxy.
Please help as to how do I remove mesa-dri-drivers and what were the drivers that were being used before I installed mesa.
I have installed today Ubuntu 10.4 LTS ..after installation the OS does not boot and just shows blank screen with cursor blinking ...any idea ..I have searched the forum a lot but cannot understand why this is happening ..re-installed twice ..This is AMD64 bit but I am installing the 32 bit ubuntu 10.4 LTS.
This is probably not possible, but just wondering, restarted centos 5.2 remotely, hung at shutdown, kvm'ed to see what was hanging it up, control c'ed and then ctl alt del, just trying to kill the process, was brought back to the login screen, but unable to type anything. Alt-f1 switched to a different virtual console, which was just a blank screen and a blinking cursor, but now able to type things. Want to avoid hard shutdown. Is there anyway to force shutdown/reboot the machine from this console?
I have installed it from usb as the cd installation failed at the point where you decide which type of installation you want (lamp or samba, etc)the installation completed but when booting nothing happens, only a black screen with a blinking cursor. pressing the shift key or any other keys doesn't work.strangely when i boot from the usb flash drive again (and not from the hard drive) the server does boot and asks for the user name and password!i have chosen the guided lvm partition with 20% reserved for system files.my machine is an athlon xp 2GHz (32bit), 1GB, SATA hard drive, nvidia 6600 graphicsmy guess is that its a problem with grub and lvm.
Skype started to work well. However, after I rebooted the system, all I get is a blank screen with a blinking cursor. I am able ot get to tty by doing ctrl+alt+f2 but am not sure how to proceed from the above. I also erased the above packages thinking that that might solve. But it hasnot solved the issue.
1) Burned Ubuntu 10.10 to a disk, When tried to install (Select Install Ubuntu) screen goes blank with dim backlight and a blinking cursor on top. Same thing happens with Try Ubuntu without installing.. 2) Tried on Lenovo T410 and Dell 1330. issue exactly remains the same.3) Tried it on a VM Worksation 6.0, "This kernel requires an x86-64 cpu but only detected an i686 error is popping up". So thought its a Ubuntu x32 an compatibility, hence downloading the 64 bit now. Will burn and check it later.
Brand: Lenovo T410 Intel(R) Core(TM) i5 CPU M520 @2.40Ghz BIOS: A1674IMS Ver 1.0L
Just curious if there is any sort of issues with Ubuntu and JBOD assignments. I had my 2 500GB hdd's as JBOD through my mobo BIOS/RAID Config and it didn't like it. It installed just fine and showed the hard drives separately. I really didn't think anything of it so I continued on.After the install completed successfully, and I rebooted the system, it came to a blank screen with a blinking cursor and wouldn't continue on. So I tried restarting a few times, no luck. Finally I was like "okay screw this, going to install with no RAID setup or JBOD setup." (had RAID issues last night. rabble rabble) Removed RAID configurations and BAM started right up..S. Semi-new to Linux/Ubuntu. Know the basics and what not, just not some of the more advanced stuff.Edit: Okay, so I restarted my computer and removed my USB drive (which I had installed Ubuntu from) and it didn't boot. So it was NOT an issue with JBOD. Guess I'll look for a resolution for that, though.
I am using fedora 15 on my dell studio 1558 . Sometimes a black screen appears with a cursor blinking when i tries to reduce the brightness of the laptop and somethimes it automatically happens . And i am not able to do anything its just like the blue screen of death as in windows . the only way to get back is by restarting the computer
I am installing Fedora 12 on a VIA pico ITX and am running into some issues.
I had the same board but with an PATA/IDE drive, and on that it installed just fine. I needed a bigger/better drive so I did get an SATA drive for it.
After the install it either freezes/hangs when the post install begins or IF the post install works (when I use ide=nodma) it won't boot. I do get to see the grub screen (if I change the timeout in grub.conf) but as soon as the kernel starts loading it freezes. and I see a black screen with a prett fast blinking cursor.
With the live cd, if I try to boot: it reports, no root available going to sleep.
I downloaded the OS I wished to use, loaded it onto a clean 4.0GB drive, everything went as planned. But then I rebooted, and it never booted the file off of the USB. So, I changed the boot options, and tried it again. Now, every time I boot with the drive in, it goes normally and then opens a blank page with only one line of text detailing the date of copyright, something about Linux, etc... And a blinking cursor. Is this normal and I just have to wait for it to load, or is something not being processed? Any information you guys need I can obtain, I'm not new to computers but I am new to changing OS's.
After installing Fedora 15 from LiveUSB and rebooting it just hangs on a black screen with a blinking cursor (underscore) in the top left of the screen. If it's reached grub, it isn't responding to any commands, and mashing several key combinations (such as ctrl-alt-f1) will produce a beep usually emitted only by the BIOS (hinting that it may never be making its way to grub).
The only particularly interesting thing about the install is that by default it wanted to boot itself from the MBR on my primary-master (Windows) disk. Instead I selected the option to boot from "the first partition in sdb1", which is my primary-slave (Linux) disk, (the first partition being /boot). This way I can change which OS boots by changing the boot order in my BIOS, and so avoiding bootloader wars.
Although I managed fairly quickly to get 3D enabled on the GF 7600GS of my desktop, it took me longer to get 3D up on the GF 9650M GT of my Asus laptop M70Vn. Although I made extensive use of the numerous procedures outlined here, none of them worked and booting my laptop always ended up with me facing a jet-black screen and a completely inexpressive blinking white cursor. My solution was simple: I did not blacklist Nouveau and problems mysteriously disappeared.
when I fired up the installer, after asking to test the media (which I skipped) and starting up the actual installer (anakonda, akonadi, whatever the name was, can't remember now and too lazy to look it up), it seemed to start up fine, except I couldn't get the wizard to show up. I did see the cursor, and occasionally I would get the "searching for storage devices" message (I restarted it a few times to see if I would get it working), but nothing. I also tried random key presses (namely F12,F1-F4), and after some time got a message saying that I had to enter the root password, so I presumably got to the root password screen blind...? (meaning that the installer apparently is ther, I just don't see it?)
After several restarts, though, I managed to get the wizard visible (just luck?), so I went ahead with it, but apparently I messed it up, when I rebooted I didn't get the screen visible again, after some random keypresses I got to the login prompt but I obviously hadn't created any accounts, so :/ I tried booting from the DVD to the rescue mode and manually adduser-ing from the console, but when I tried logging on, it would just come up with some kinda bluetooth-related error message and then hang on there with only the background image on the screen. I didn't try the basic video driver thingy yet because this didn't seem like a video driver issue (well, not entirely anyways), and I need my 3D acceleration, so...
Basically, I'd be glad if anyone knows what's up with the installer, and if it's not fixable as such, would installing with the basic video driver and then installing the proprietary drivers afterwards be all right? Sorry for the wall-of-text, though, it's just one of those days, it's bedtime and I get carried away...
Just did a fresh Ubuntu 10.10 (minimal) install on my Asus EEE PC 1001PX.Before the minimal install I had Ubuntu Netbook Edition 10.10 which worked flawlessly, now all I get is a black screen with a blinking cursor:for the amazing quality, but I guess it's better than nothing.ctrl+alt+Fx does nothing, ctrl+alt+del reboots the computer.Booting with the usb-stick that was used for the install takes me to the login...
I recently followed instructions to enable the nvidia driver. run the following commands:
then rebooted, a tricoloured loading bar appeared and finished, then all i got was a blank screen with flashing cursor. I don't get a prompt to login and can't access my account. I am dual booting on this machine with ubuntu, is there anyway i can restore my fedora partition and enable my nvidia graphics
I just got an update notice two hours ago and after updating I rebooted my machine to find that it no longer boots. The update was for 23 bug fixes for Nvidia drivers and Nvidia support software. I get a black screen with the message "serial8250: too much work for irq17" and a blinking cursor. How do I recover from this?
I have a machine with Squeeze that currently boots from an USB thumb drive (that was the only drive on that box, referenced as SDA in /dev... Yep, no optical drive or HDD). I have installed an SSD on that machine. It is referenced a SDA, and the thumb drive has been nudged to SDB. I'd like to boot from the SSD and ditch the thumb.
I've partitioned and formatted the new Disk (ext4), created a swap file (to keep things simple, no swap partition), and used rsync -Sax / /media/USB0/ to clone the content of the root FS. I've edited the fstab file of the SSD to match the config (uuid of the drive, ext4 FS, swap file) then use grub-mkconfig -o /media/USB0/boot/grub/grub.cfg (I apt-get installed grub 2)
I've set the SSD as first boot device in the BIOS. Now when I boot from the SSD, all I get is a blinking cursor at the top of the screen (the thumb drive still boots fine). I guess I missed something .
I've been struggling with this for about 2 hours now (not the grub issue, the whole mess). I've tried googling this last problem, then searched this forum with no luck (I usually find stuff about people who want to boot from a drive other than the first one and must daisy-chain grub).
Bootloaders (and low level linux stuff) are new to me. I'm afraid to botch the bootloader of the thumb drive (grub 1.9x), and to be locked out of the machine.
A few weeks ago I installed Ubuntu 10.4 beta on a pc. I upgraded it to 10.4 RC and 10.4 final release. I think it was after upgrading to 10.4RC that I started having a problem during startup. Here is what happens: I turn the pc on the bootstrap process occurres, then the grub screen comes up I let ubuntu boot. For a few seconds I get a black screen with a blinking cursor. The Ubuntu splash screen flashes on the screen for maybe a second or two. Then I'm dumped to the command prompt on TTY1.
At this point I can log in with a username and password type startx and I'm at the ubuntu desktop. If I log off I'm back at the command prompt on TTY1. If I press alt-ctrl-F7 at the command prompt this is what I see, these are the last four lines of text: init: ureadahead-other main process (742) terminated with status 4
just did a dual boot install on a brand new DEll T1500. The machine has win7 on it. I booted off the live CD and all looked well. Installation went well. When I reboot, I get grub, select the top linux option and then see a small black blinking cursor for a few seconds, then nothing. The screen reports no signal.
I just installed 10.04 and for some reason once the grub screen loads and I can pick what I want to launch (regular kernel, or rescue mode), it attempts to load and then I just get a blinking cursor. I've found that I can't load the live CD either unless I use the nomodeset flag. I read in another post that this problem should be fixed by editing the /etc/default/grub file to add the nomodeset flag, which I did via nano. However, the file also says you must run update-grub after you edit the file. I tried this and it said something like it can't find / (is /dev mounted?) The hard drive itself is mounted, so I don't know why /dev wouldn't be mounted. How can I get this problem solved so I can boot to 10.04 successfully from the hard drive? (I'm typing this from the live CD right now).
I have here two old identical compaq pc's with 64mb ram.I want to copy drive/os from one machine to other. So i do a drive to drive clone (witn both hd's deing connected to another machine). And it says its done and okay. But the second (cloned) machine doesnt boot. And have the black screen with the blinking white cursor in top left corner. I have already tried to do fdisk /mbr and also copying partition table from original to destination disk. Because i think it is logical that with a drive to drive clone it sould be copied. But i have a doubt in that somehow. Because why would it not boot if it was copied then
I installed Ubuntu 10.10 alongside my Windows 7 os in a dual boot config. I used an installation disk and allowed the ubuntu installer to do all the resizing of partitions, installing of grub, etc. The install is working great and I haven't needed to boot my windows os since which is great. The only complaint I have is that it takes it takes a bit longer to boot than windows did for some reason. The culprit is a blinking cursor that comes up and remains for about 12-15 seconds before the grub menu appears. I already altered the boot option for the grub menu so that ubuntu is default and the option to select another os only appears for 3 seconds but I don't think this is related since the delay occurs before those options appear. I'm not really sure what is causing the delay. Is it looking for the loader? If so, is there a way to edit the configuration so doesn't have to search? As I mentioned, the install is running great otherwise.
I have a problem with booting from a USB flash drive. I have Acer TimelineX 3820TG. I have Windows 7 Home from Acer and I installed Mandriva OS from USB(from USB because this Acer doen't have a DVD drive). It was OK, but I want reinstall Windows 7 and so I did. Now I have Windows 7 Professional and it wrote over Mandriva's GRUB. It wasn't a big problem. For a while I was just using Windows 7 but now I am thinking that I need some OS with Linux and I am thinking about Ubuntu. But when I tried to boot from USB with Ubuntu I get a black screen with a blinking cursor after the BIOS POST.
I was trying many applications to create a bootable USB drive and many versions of Ubuntu (and other Linux distributions), but nothing worked. I tried to Google for answers but I found many problems where all booting goes to black screen but in my problem Windows 7 boots fine from disc but from USB doesn't work.
I have a problem - after installation of Ubuntu 9.10 I discovered that I do not have virtual terminals on my computer. When I am trying to switch, to another virtual terminal with, say, Ctr-Alt-F2, I am getting a black screen with lonely cursor blinking in the upper left corner (no login prompt).my tty2.conf file is
Code: # tty2 - getty # # This service maintains a getty on tty2 from the point the system is # started until it is shut down again. start on runlevel  stop on runlevel [!23]
I dual-boot Windows 7 and Ubuntu. Sometime between 4/18 and a few days ago, something happened with Windows booting up. Ubuntu boots fine, but whenever I try to boot Windows, it just goes to a black screen with a blinking cursor (the command line kind, not a pointer). At first I thought it was Windows, but I have run the repair CD and executed chkdsk /f and chkdsk /r on all partition related to windows. No effect.
I ran a system check designed for issues with booting up, and it found no errors. I have looked at my GRUB files, and they all look fine. I am not sure if it is GRUB or Windows. I tried reinstalling the Windows boot-loader, and it had the same effect, the only difference is that it bypassed GRUB. The reason I think it may be GRUB is that the error happened around the same time as me upgrading from Karmic to the Lucid RC. I have posted this on a Windows 7 forum.