I got a Lenovo T430s and when I boot up the USB I am presented with different options like
install
install graphical
install 64
install 64 graphical
etc
When I pick one and hit Enter I am presented with a black screen.
I thought I'd breathe some new life into my aging PowerMac G5 desktop computer by installing debian. I burned the CD and ran the installer and everything installed okay, but when I went to boot it up for the first time, the screen blacked out after a few seconds of scrolling text and shows no signs of life after that. The computer just stops sending video to the monitor, and the only thing I can do is shut it down by holding down the power key.
View 13 Replies View RelatedI've just put a fresh install of 64 bit Lenny on my new HP server. All went well so I thought to install KDE. On reboot, the screen just goes black.Could I have some helpful suggestions on how to start working out what the problem could be?
View 7 Replies View RelatedI have installed Debian Jessie 8.0.3 64-bit net install on a MSI CX620. Installation went fine but trying to boot it up the first time nothing but a black screen shows up. I've tried:
Holding shift on startup - Nothing
Press down all keys - Not much, only ctrl+alt+delete makes the screen turn off and then on again.
I'm thinking that I had secure boot on which I now after installation see could be a problem, but I didn't think it would be a problem as I could just go into bios and turn it off, but seeing now that I can't even go into bios it may be a problem.
I installed jessie amd64 lxde to a thumb drive to use with a laptop. Vanilla install using the amd64 lxde live cd. Upon booting the usb system, I am presented with a black screen with blinking cursor. No grub screen, no ability to type any commands and no ability to switch to another terminal. I tried booting into the live cd and I could get into the intro splash screen. Booting to the live system from there would also hang at a black screen.
However, using the kernel parameter "nomodeset" from the splash screen did allow the live system to boot to the desktop. I booted the live system, mounted the usb system and chrooted into it. I edited /etc/default/grub to include "nomodeset" in the GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX variables and then ran update-grub.
Upon reboot to the usb system the problem still occurred. The video card in question is a amd firepro 5800m which has an lspci line of mobile radeon 5000 series. This card was supported in wheezy and apparently works with the live system.
I am using the actual "testing", Debian works in version 5 on my notebook (or at least starts), but I can't use it b/c I have too much new hardware what is already implemented in the testint Version. I already had debian 6 running but that wasn't the good way to do it.
I have an Alienware m17x R1, with a q9000, a nivida mobile 260gtx. I know that the Problem the basic Debian Driver for Nvidia cards is. It is enough if I can use at least the command line of Debian to install an actual Nvidida driver and get the system running. But that's not possible!
I solved it once, with plugging in an External Monitor to my Notebook, but I don't have one at home at the moment and honestly there must be a better way for. How to "let debian 6. use the Notebook Screen"?
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
[code]...
I appear to have the exact problem that is currently listed in the 7.6 errata about EFI boot and black screen while trying to install ("Potential issues with UEFI booting on amd64"). The problem is that their workaround is not an option for me. This is a new rig and the motherboard doesn't appear to have any kind of ability to disable secure boot. I also don't know if my problem is exactly what they're thinking when it comes to that entry.
I'm able to get to the Grub install screen where you have the option to install Debian but when I select an option (any option) the screen turns off, back on but is black. All activity in the system stops after a few seconds (3-5 seconds) and that's it, she's done. I've tried all the options to try and disable secure boot but the options listed below are as close as I can get (and apparently should be sufficient).
The CD ISO used was the 7.6 netinst CD. I've also tried the Jessie ISO (Testing) that was downloaded about 2 hours ago. Same results. Unlike the errata which says "intermittent booting problems", my issue is consistently reproduced with no other result no matter what I do.
The rig:
-Asus H97-Plus running revision 2202
-Intel i5-4570
-32GB DDR3-1600
-128GB SSD Drive
-No external video card - using on board only but have tried both VGA and HDMI ports with the same result.
BIOS settings (is it still called BIOS or is it UEFI now?)
-Fast Boot: Disabled
-Launch CSM: Enabled
-Boot Device Control: "Legacy OPROM Only" or "UEFI and Legacy OPROM" (tried both)
-Secure Boot State: Enabled (it's grayed out and I'm unable to change this)
-OS Type: Other OS (supposedly makes it so you can boot non-Windows OS)
The Debian page with the errata: [URL] ...
Look for "Potential issues with UEFI booting on amd64"
The obvious suggestions I've tried:
-tried USB boot & CD boot - same result
-tried altering the grub script to add the ACPI options - no effect
After installing debian squeeze I tried installing a nvidia driver. I had to type: /etc/init.d/gdm3 stop The nvidia driver wouldn't install because the 'make' command was missing in a path or something. Now I cannot get the GUI anymore. startx gives me a blank screen rebooting the computer gives me a blank screen. I can only boot in recovery mode. but the nic doesnt work so no internet connection.
View 1 Replies View RelatedI'm running an Acer 1810Tz, dual boot with win7.Under 9.10 and Grub I had no boot issues, however I have just completed the upgrade to 10.04 and upgraded GRUB to GRUB2.Everything boots just fine into Ubuntu, and my GRUB menu looks right, but when I select the Windows 7 option, the machine just hangs with a black screen, white cursor top left. I'm sure this is a trivial problem, something overwritten that shouldn't have been perhaps, but I have no clue where to start.
View 6 Replies View RelatedWhy isn't there a clear warning against selecting the 'update' option in Meerkat?I know it seems like a good idea to have it, but unless a server speed test is run, it adds a huge amount of time to the install (3 1/2 hours of downloading so far). It's not my internet connection (ADSL2+ - fast), so it must be an overloaded server and/or congested intercontinental data pipes.
After the installation, it's possible to find one's optimal (fastest) server before running updates - and I know from past experience that this makes a huge difference to little old me in Australia. I can certainly update everything much faster than I am currently seeing . I strongly recommend that, if this option is kept in future distributions, it should include a server speed test (and auto selection of the best server?) as well as a realistic warning to the user.
I'm trying to install Debian 8.1 LXDE 64bit on a Toshiba Chromebook cb30 from usb. When I select 'install' the laptop restarts and gets me back to the installer menu. I removed 'quiet' from the boot options and it seems that the reboot happens after initrd.gz is read. I previously installed the 32bit version on the chromebook and the installation process worked pretty much without any issues. I might have added 'mem=1024m' to the boot options, though even if I did, this doesn't do anything to my current attempt.
The chromebook processor according to `uname -a` is x86_64 Intel Celeron 2955U. how I could install the image or start debugging the issue?
another post about this. I just don't know how to handle this, as I'm pretty nsee the grub loading menu, but screen just freezes after, no way I can reboot, or open a console. In recovery mode I can log as root in console, though.I run Debian 6, 64 bits. I have an intel q6600 and a nvidia geforce 9800GX2.
View 9 Replies View RelatedDebian 60 (squeeze, testing) 64-bit
The window for selecting kernels at startup is NOT clear.
I have problem with my Debian. Sometimes after reboot I can see only mouse cursor (moveable) and black screen with command prompt in top -left corner. I don't know how to fix it...
Code: Select allroot@debian:/home/rafal# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 8.1 (jessie)
Release: 8.1
Codename: jessie
[code]....àwwwwwwwwwwwwwwwwwwww~s
I've been running 5.05. Just in the last few weeks after I update the screen will go black after a few reboots. I believe it has something to do with the ATI Drivers. If I clean install and install the smxi drivers after a few reboots the screen goes black right before the log in screen. This also happens with Mepis and Dream Linux which are Debian Base.
View 6 Replies View Relatedafter a couple of years using Debian derivatives, I decided to try debian 5. Seemed to install okay. Installed Mint afterwards (as debian didnt boot) and debian is visible in the boot menu. Upon selection of debian, I just get a black screen and the monitor gives the message "input not supported". I havent had any such problems with numerous distros over the 2 years.
View 10 Replies View RelatedI recently installed Debian squeeze on one of my older pcs. I have had this computer for a long time with windows so I know there is no hardware issue. About half an hour after being turned on in Debian the computer goes to a black screen and the num lock caps lock and scroll lock keys flash.
View 1 Replies View RelatedMy KT4AV-based PC has burned up two GEForce 6200 cards, so I decided to try an AGP bus Radeon HD 3650.At the same time as the nVidia card went "black screen" (no video at all, not even text) my CMOS battery died.I put in a new CMOS battery and fixed up the CMOS settings as well as I can.I put in an old Trident TVGA96PCI cardnd got as far as terminal mode, but even with the xserver-xorg-video-tridentdriver already n the system, I couldn't get the display manager to run. I gave up on the Trident card becauseold and bought a new Radeon HD 3650 card and changed the display bus from PCI toAGP in the CMOS settings.
The Radeon card now also gets me only to terminal mode.tried coaxing the system by renaming xorg.conf, but that didn't help - rebooting still gets me nowhere,no new xorg.conf file. The renamed one is still configured for the nVidia card. The xserver-xorg-video-radeon driveris also present, as "sudo apt-get install xserver-xorg-video-radeon" tells me it's already the latest version.I'm presently stuck without direct network support, as the ethernet connection hangs the computer during rebootthe message, "ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready." If I unplug the ethernet cablefor starting successfully, when I plug it back in while I'm at the command prompt, I get a message to the effectthat eth0 up and running,"ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready" messageappears again and the sytem again freezes.I have successfully pinged this PC from another on the network, but not while it's hung up at the above-quotedmessage. In that case, it's "unavailable."How do I purge the system of the nVidia stuff and replace it with an approporiate Radeon driver ?
I am trying to use a F14 network install CD to upgrade on an old HP Pavilion 9695C (Athalon 850MHz, nVidia NV5 RIVA TNT2/TNT2 Pro AGP) with F12 on it. This same disk successfully upgraded a HP Omnibook 6000 with F12. I boot with the network install CD and get the initial menu to select to install/upgrade, install using basic video driver, etc. After selecting either upgrade or basic video driver install, I see the CD being read, then nothing, just a blank screen. I had a similar problem with F12 network install on this machine. So I tried adding "vga=0x318 nomodeset" to the upgrade boot options. The only difference is a quick flash on the screen, then a blinking "underscore character" cursor. The "install using basic video driver" has the same result.
Have also tried:linux nofb
vga=791 [nomodeset]
vga=1 [nomodeset]
xdriver=nv nomodeset
xdriver=vesa nomodeset
However, I always end up with a blank screen or blank screen with blinking underscore cursor. I know this particular AGP has problems with the nouveau driver. On F12 I had to force it to use the nv driver. I submitted a bug but there was no interest on it as this was F12 and F13 was the latest at the time. I did try to upgrade to F13, but ran into this same problem. I was hoping F14 would be better.
I am a complete beginner to Linux (I understand a little bit of terminal from my OSX usage). I did a fresh install of Debian on an older Gateway laptop to try and make it usable for something. There is no other OS installed to this machine, I would like it to run Debian exclusively.
I used the UNetbootin application to install Debian from USB [URL] ..... Everything seemed to install just fine (no errors). However, upon 1st boot, I am presented with a black screen with a blinking white cursor. I cannot seem to get past this. I searched around and found this post: [URL] ... which seems identical except that their machine is a Mac. I had no luck using the REISUB reboot method. When I hold Alt+SysRq or Alt+PrtSc, it makes a lot of beeping noise. Issuing the REISUB keystrokes while holding does nothing.
I have a problem after installing Debian and running it on my machine. Instead of taking me to a splash login screen, it instead remains a black screen like a console where I type in my username and password, and it remains in this black command line mode beginning ben@ben-desktop:~$. Like it does in a terminal. What can I do to resolve this? This is completely new to me and hasn't happened to me in Ubuntu or Mint. I am familiar with using the terminal for the odd task but obviously I can't use it like this without a visible desktop.
View 14 Replies View RelatedI get black screen when i press ctrl-alt-f1 or when i try to stop gdm, pressing alt-f7 nothing happens.
vga is ati hd 5650 how can i fix?
why do i get the black screen at install just after when it loads
View 3 Replies View RelatedI have been using OpenSuse at work for years. My Windows 7 machine crashed on me. Instead of spending the time to fix it, I decided to take the plunge and install 11.2 on my home system. I have 4 one TB drives. My RAID card has a 2x2 1/0 RAID array defined (sdb, sdc, sdc, and sde). A fifth hard drive, outside of the arrary, which is a 250GB drive (sda). It is a software RAID. Here are the partitions I set up in the installer.
On the raid:
1.75 TB on /home
2.01 GB on swap
48.55 GB on /tmp
Off of the raid:
sda1 115 GB /
sda2115 GB /boot
(I know these are really big but I did not want to put any data outside of the RAID) In the final Installation Settings screen, I chose Booting and change from booting from the MBR to the /boot partition. The boot loader type is Grub and the status location is at /dev/sda2. I select Install and it installs without any error message.
After it installs, it restarts and I press ESC to see what is happening. It skips boot.cycle and continues to load to "starting HAL daemon ...done" and then the cursed black screen. I cannot SSH into it. It just sits there and I have to do a hard resest. Once I restart it, it boots into the non-RAD drive I get the follwing error message:
GRUB ..(it went to fast for me to get the rest of it)(hd1/1) message: file not found and I get the option the change the boot options of the Desktop -- openSUSE 11.2 and Failsage -- openSUSE 11.2 . I select e to edit the boot section of desktop and see
root (hd1,1)
kernal /vmlinz-2.6.31.5-0.1-desktop root=/dev/disk/by-id/ata-ST32508...
intrd /initrd-2.6.31.5-0.1-desktop.
I tried changing the root (hd1,1) to 0,1 1,0 2,0, etc with no luck.What do I do? I need to boot into OpenSUSE and finish the cursed installation.
PS: You can tell I work IT with the uber amount of details I put into this
I've been trying to install Ubuntu 10.04 on my Dell XPS 630 but every time i select INSTALL or TRY UBUNTU when booting from the cd, all i get is a black screen with a white blinking cursor. I have tried various options in the F6 menu but nothing has worked. I know the CD is working because I was able to install it inside Windows and dual boot, but I wish to do a fresh install.
View 9 Replies View RelatedI'm so desperate about my problems with installing ubuntu. I got a Fujitsu Siemens Computer AMD Athlon 64 Processor 3200+ 2.01 GHz and 1,50 gb RAM. I got Windows XP home edition on my computer, but i wanna completely switch to ubuntu.
At first I tried to install it with wubi, but it won't work always the same problem.
Then I tried it with the Live CD and tried demo and not install, but it fails. First there is a purple screen with a keyboard and a little guy in a circle, then there's a _ in a black screen blinking, and after that my monitor goes into standby mode. The CD is still loaded from the harddrive, but nothing happens. It feels like the Screen froze down and I can't see anything, what's going on.
I tried it with just installing, alternate install, but it's everytime the same problem.
After install I tried to install my video. Which happens to be nvidia and of course after reboot I now get a black screen showing login and password but it will not work I can only get in through recovery. I have a nvidia ge force 9500gt.
View 6 Replies View Relatedafter i installed ubuntu 11.04 and restart .. nothing appear only black screen i think my problem in my vga card ....i have switchable one in my laptop (ATI Radeon HD 5600 /intel )
View 9 Replies View RelatedI boot from my USB, and when I try to install my screen starts showing a bunch of white words while scrolling, then my screen goes black and my laptop stops running even though it is still on. I have also tried just running it, but the same thing basically happens.
View 5 Replies View Related