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?
View 14 RepliesI 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
View 8 Replies View RelatedI 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.
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.
View 2 Replies View RelatedJust 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...
View 3 Replies View RelatedA 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
[Code]...
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.
View 8 Replies View RelatedI 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
View 9 Replies View RelatedI 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 [23]
stop on runlevel [!23]
[Code]...
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.
I have an Acer Aspire One AOA110 that came with Windows XP.
I created a usb flash drive install for Ubuntu 10.10 netbook edition and went through the install process (wiped disk clean, not a dual boot with WINXP).
Before install, I was able to run Ubunut from the usb key with no problems.
At the end of the install, it told me I needed to restart, so I clicked the "restart" button and the removed the usb drive. Nothing happened and it never restarted and just completley hung for about 20 minutes. I manually shut down the computer by holding the power for 10 seconds and then rebooted the machine. Now all I get after the "acer bios" screen is a black screen with a blinking cursor. If I press any buttons, the computer beeps at me.
I have rebuild my system, with an Asus motherboard M4A88TD-V EVO/USB3 with radeon 4250 integrated 8 Gb memory
Athlon II 4x 640 2 x 1 TB sata3 WD Harddisks I installed 10.10 64bit, and ran through the whole install with the alternate CD without problems, Installed grub in the MBR on the 120 Gb partition for 10.10, it even recognised my 2 3ware pci raidcontroler on which 8.04 is installed.
When I start I get grub, when I choose for 10.10 I get a black screen with a cursor blinking in the left uppercorner. Luckily I can start into 8.04. I have no idea how to continu. for now I will burn a knoppix cd so I can read the ext4 partition with 10.10 and hope to find something to solve this.
I'm a fairly new linux user and I seem to have a problem with ubuntu 8.10 after installing it.To make sure everything was working fine before i could do a dual installation, i ran the live cd and it worked like a charm.Everything works fine in the live cd....the internet, sound, graphic drivers (even the special effects seemed to be work fine)I thought wow...after having a bitter experience with Ubuntu 8.04 and 7.10 (I couldnt install those at all coz of driver issues and stuff) I thought this is it!So I used the wubi installer to install ubuntu in my D drive (I didnt wanna use C just to be safe as the primary OS is installed there). Gave it a healthy space of 15 gb. Finished the installation and the rebooted.I went inside Ubuntu which started doing its installation and copying of files and stuff. So far so good.....
And then once it finished its installation and copying of files (100 %), the screen went blank and i see a cursor blinking. I thought maybe its restarting and thats why it must be doing this.I wait for nearly 10 mins and nothings happening except for the cursor blinking on the black screen. I press the caps lock key to see if anything is processing. Nope. So i manually shut it down and then load ubuntu.It loads like 20-30%....rests for a while....and then it loads a bit (not completley)....after that it takes me to a command line asking me for my password and username.I enter those correctly. But it doesnt get me into the main GUI screen yet.
It shows me a lot of the this error msg:
-bash: /dev/null:Permission denied
I'm still in command line (or terminal to be precise). So i use 'startx' (something which i learned from my csci labs ) to start a new session. It showed signs of starting a new session (i can see the mouse pointer and stuff) and then poof....back to the command line again.So I shut it down and load it again in recovery mode. It shows signs of the same symptoms in the splash screen (going very slow after 20-30 % ) and then this time, before i'm asked for my username and password in the command line, it shows a lot of warnings: fake daemon running (or something like that) and i cant even use startx!So i didnt know what to do, uninstalled ubuntu and did a fresh installation (wubi and in the same D drive). Reboot. Install and copy files 100% and then a blank screen again with the dreaded cursor blinking. I still wait for about 10 mins and nothing yet happens. So I manually shut it down (again) and then load ubuntu and unsurprisingly i have the same problem as what i described before....doesnt load properly and i'm not able to come out of the terminal.
I was going to set up an ubuntu server, but ran into some issues. When I try to install ubuntu server 9.10, it immediately goes to a black screen with a blinking cursor as soon as I press enter on the menu. I've tried pressing F6 and editing options - noapic, nolapic, irqpoll, vga=[something...] and nothing worked. I then downloaded a standard ubuntu desktop cd, and the livecd works, and I can successfully start the install!
I've heard that I should probably use the server install if I want to use this as a server (which I do; webserver for a group of people, website, ftp, ssh.) I've also heard that it's possible to just install everything needed overtop of an ubuntu desktop base. What should I do? Are there other things I should try to make the server install work? Or is it not worth the effort, and I should just go with a desktop install and then work from there? tasksel? (It's a Dell XPS, the graphics card is NVIDIA Geforce 9800 GT).
I am trying to boot up Linux Mint 7 after a packages upgrade and it boots up but then it shows this and stalls.And similar messages for GDM and then it just shows a black screen with a single blinking cursor on the middle left of the screen. I cannot do anything except press the CTR-ALT-DEL combination to re-boot, then it shows the usual shutting down messages and does the re-boot.I am running the 2.6.28-19 kernel and I have upgraded the Ubuntu packages on my Linux Mint 7 system from Jaunty to Karmic. Please help as I do not want to re-install. I am running Knoppix 6.3 ATM and I should be able to chroot from that if necessary. I am booting from /sda1 that has Linux Mint 8 installed and grub 1.97.
View 1 Replies View RelatedProblem-PC automatically boots into a black screen with blinking cursor. No message or nothing
I have 4 HD. Primary drive has Windows Vista, Secondary no OS installed. Sata1 HD Ubuntu 10.04, Sata2 Windows 7. Prior to installing windows 7 all was perfect but once I did it, grub got all screwed up. The only way I can boot into grub is if I manually select my Sata1 which has Ubuntu on it and only then it allows me to select Linux or Windows OS. How can I change that so it can boot up normally as before? I'm assuming that grub was installed in the primary drive which has vista on it, but once I installed windows 7 it got deleted and when I tried reinstalling Ubuntu, the grub was not installed in the primary drive.
I've got two laptops running Ubuntu. Both have had Lucid installed from the live cd. I have upgraded one of them to Maverick. Both distributions are running great after they boot up, but I haven't experienced any faster boot times with either distibution. Both boot to Bios and then the screen goes black with a blinking cursor in upper left corner of the screen. The black screen remains for 30 to 45 seconds and then I get the Ubuntu splash screen for maybe 5 seconds, and then desktop. Why am I not seeing faster boot times? I realize 45 to 60 seconds is good compared to other os's, but I anticipated much faster boot times. Shut down on the other hand is quite fast at maybe 5 to 10 seconds. Does anyone else get this black screen on boot? Seems like wasted time cause I can't tell what's going on during the time there is a black screen. This is not a real big deal breaker, as I don't reboot very often, but I just wonder why bootup isn't faster.
View 7 Replies View RelatedWhenever 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.
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.
View 1 Replies View RelatedI keep starting up Fedora and I'm not able to get far (although it's not always at the same time) before my screen will go black, except it shows the mouse/cursor - but it's frozen, and thhen the caps-lock light starts blinking and I can't do anything or get it to recover. Sometimes it happens after 30 seconds, sometimes 40+ seconds and sometimes within 15 or so seconds.
How do I stop this and diagnose this?
I've tried, in the boot-startup to choose an older kernel version, butt the same thing occurs!
I have:
Fedora 11
Kernel: 2.6.29.6-217.2.16.fc11 i586
Asus EEE PC 1002HA
One other thing, it does always seem to happen after I've turned on wireless. And I've been using F11 for months now with no issue.
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 installed some weeks ago Fedora 14 via burnt iso file downloaded from official Fedora site. It was working perfectly like a charm for me until yesterday when I tried to install zend server for PHP.During my first try of installation of zend server it corrupted out my apache server and I lost apache on http://localhost.I removed all "zend-server" like stuff from "Add Remove Software" screen.
Installed again apache 2 in the form of LAMP (Linux Apache Mysql Php)via terminal. Apache installed correctly and started workeing again ok on localhost.n again I tried to install zend server from install.sh file in downloaded zend server installation. It showed me after a while like "zend server installed successfully".I shut down my pc thinking everything is ok now.
Today when I started my system, it shows me boot screen of Fedora, I select fedora and then it shows me baloon filling up for around 5-7 secs. Then all of a sudden a black screen appears up with a cursor blinking at its top left and then nothing else happens further. I cannot find login screen to my desktop anymore.I remember one thing thating reinstallation of apache from terminal, I set following command like "chkconfig --level 235 httpd" (I guess that's what I have written as per some online tutorial for LAMP). Is that cause of mine problem ot its something else?
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.
I successfuly installed Ubuntu 11.04 through the NetInstall option on an Aspire 3810T laptop.
Using the default option, the laptop boots OK, I can ssh to it OK, but the screen on the host just displays a blinking cursor. I assume the stock Ubuntu doesn't have the right display driver:
Code:
root@ubuntu:~# lshw -short
H/W path Device Class Description
=========================================================
/0/100/2 display Mobile 4 Series Chipset Integrated Graphics Controller
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).
View 9 Replies View RelatedI 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.
View 9 Replies View RelatedI 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.
View 9 Replies View RelatedI have reinstalled the OS a couple times now. Not sure what else to check.(noobie)Its on a RAID 1 controller, so I'm wondering if that has something to do with it
View 2 Replies View Related