Debian Installation :: Dual Boot XP / Squeeze - Blank Screen With J On Restart
May 8, 2010
I've had Windows XP Home installed on my netbook (Toshiba NB205) and I've just tried to install squeeze via net install. In particular, I installed grub. Everything seemed to go ok during the installation, but when I boot up, all that appears is a blank screen with nothing but at "j" and a cursor. One thing I can think of that might offer a clue, is that when asked to installed grub, the installer said it recognized two operating systems: Microsoft Windows XP Home, and Windows NT/XP. The latter is not really an operating system, but the backup partition.
I don't know how this might affect grub's functioning. What does this "j" mean? Looking at this: [URL]. Could this have some thing to do with boot flag? Should I switch it to my NTFS partition instead of my root partition? Doing that at least let's me boot into Windows. But that's not what I want. I've never dual booted before. So I booted back up with my USB, intending to reinstall Debian, and it loaded grub instead. So apparently grub is now on my USB. Then it booted me into Debian.
I installed Debian squeeze on my old Dell Latitude C600 laptop. I Installed it from a cd that worked to a friend of mine. I finished the installation successfully. After booting the computer I can get to the grub screen and after choosing the OS (Debian GNU/LINUX, with linx 2.6.32-5-686) I see the computer loading and running command lines, but after few lines, I get black screen and I hear the computer "working" but can't see anything and it doesn't react to anything that I do.
I have installed Ubuntu 11.04 along side windows 7 ultimate. But the problem is as soon as I switch on my computer. There is only a blank screen with my TFT screen displaying a msg "Out of Range"
Then suddenly Ubuntu loads without showing any option to load windows 7.
I cannot count how many times I have re-installed squeeze, and do all kinds of fixes to grub, but no joy. Every time, there is this ntoskrnl.exe error, and to re-install it. I thought my WIN XP may be corrupted, so I reinstalled it, and updated it with sp3 and all updates. Then I re-installed squeeze (reformatting all partitions). At the end, the installer ask if I want to install grub to mbr. I replied yes. After reboot, only the 2.6.32.3-amd64 and the recovery kernels show up on the grub screen, no winxp.OK, I booted into squeeze kernel and looked at the /boot/grub/grub.cfg file, and there winxp is not included in /etc/grub.d/30_os-prober section. In terminal, I typed
#os-propber and it found winxp in /dev/sda1 then I typed #update-grub
and now /etc/grub.d/30_os-prober now show winxp.I rebooted, and winxp shows on the grub screen, and I chose winxp.It came back with "ntoskrnl.exe ...error... re-install ntoskrnl..."Here are the details:
I have an system that d8.2 appears to install correctly. On first (or subsequent) boot, I get the DB8 load screen, then a quick fsck, then nothing. I appear to have some sort of environment running as I can move a mouse pointer, but nothing else.
CTRL-ALT-F2 results in the mouse pointer vanishing, but nothing else. I expected to end up at the CLI.
I have tried different installs and options, always the same result. This machine ran an earlier version with issues.
So I tried to install ubuntu 10.04 on my 5 year old gateway laptop but the screen kept going blank when ubuntu was booting up. I was able to get to the menu screen and add "i915.modeset=1" after "quiet splash", which allowed ubuntu to load. I installed it on the hard drive successfully, but when I restarted the computer, it won't load again. I don't know how to fix this so I can run it from the hard drive.
I recently installed ubuntu on my PC. The installation went fine without any errors but ubuntu won't start up. The first weird thing I noticed after installing was it asked me to restart my computer. So I did so by clicking the "restart now" button but my computer never shut off. The monitor did but the pc itself did not. I manually restarted the computer myself and when it got the point of starting up Ubuntu all it showed was some white boxes and some text I couldn't really see and the screen just went blank. I waited for a while and nothing happened. The only way I'm able to write this is because I'm on the trial of Ubuntu. I installed the latest version of Ubuntu by the way...
I have just installed Debian 7.8.0 powerpc on my imac G3 (400Mhz, 256Mb Ram). I had repartitioned the drive with the view of having a dual boot machine, had OS9 installed on partition 1, linux installed on partition 2 and a ext4 data partition and a 1Gb swap partition. After I installed OS9, I ran Debian Installation CD and was successfully installed. Rebooted, got through the on screen text past file system check, then screen went blank. I searched Google and forund that if I ran ctrl+alt+f1 and logged in, then ran lspci, I could get the ID of the graphics. So I did, and:
I had a working ubuntu 8.04.x system. I ran the update manager to upgrade to 10.04.1 LTS. Everything seemed to run fine up to the point where it needed a restart. Upon restart, it spews out a stream of log messages, changes the font of the log messages already displayed, and then the screen goes blank and the system does not respond to keyboard or mouse. It appears as if the system is trying to set up the monitor and messes up.
If I ESC into grub after BIOS boot, I have the option of booting two different kernels: 2.6.32-27-generic and 2.6.24-28-generic. The original ubuntu 8.04 kernel was 2.6.24-24-generic(though I did do some updates might that be the 24-28 kernel?).
Booting the 32-27 kernel results in the behavior described above.
Booting the 24-28 kernel produces a stream of log messages that scroll past to fast to read and drops into ash. One of the last messages is: !ALERT /dev/disk/by-uuid/ xxxxxx does not exist -which is true because there is very little in the /dev directory.
I have always had Ubuntu installed along with Win 7 but rarely use it, i only use it if i am flashing firmware to my phone or something similar.
I uninstalled my older version of Ubuntu because it was becoming sluggish and have tried to install the 10.10 version a few times today, but every time i boot into Ubuntu, i get a blank purple screen and nothing else.
My mouse curser is the only thing that is working but there is nothing to click on and nothing shows if i right click.
i am trying to install opensuse 11.2 to my vaio laptop i have win7 pro 64 bit already installed so i'm trying dual booting i have followed the below steps1- on windows, shrink the c partition and create a new unused volume for suse2- install the suse 11.2 on the new unused volume with hdd config like sda4 swap 4 gb sda5 20 gb / ext4 sda6 120 gb ext43- selected custom packages and started the installaton4- installation started smoothly and after installing packages it tried to reboot the machine at the end. But after this point the reboot operation has failed and gave a blank screen.
At the end the installation failed.I started the machine vaio boot logo comes and stops. i can't even enterbios setup or change boot options.I have unplaged the hd reset the partions, pluged it again and recovered win7So i think the installation damaged the file system.i have tried the above steps 2 times and came up with the same result.I have installed fedora 13 before with no problem.
I installed Win7 after Ubuntu (10.10). I attempted to reload grub so that I would be able to run them dual boot and now I can't load anything.
I followed the guide here: [url] and went threw it a couple of times now to make sure it wasn't user error.
I am using a live cd from 10.04 because it's the only one I have. Any chance that's why it isn't working properly? I wouldn't think so, but I assume that it's possible.
If that is the case; Any way to solve it without using the live cd? I cannot burn a new disk because I have to boot from disk to use my computer right now.
I just get a flashing cursor on a blank screen when I try to load.
This problem goes back to when I first purchased my laptop 4 years ago: Dell Precision M90. It came with Vista, but I wanted Ubuntu on instead. In order to get bluetooth to work, I had to downgrade the firmware. This is all fine and means bluetooth works in XP too. However, now, I have a dual boot with Windows 7 and Squeeze, I use Vista drivers (as Dell don't provide 7 drivers) and this has upgraded the firmware, and broken bluetooth in Squeeze. How can I get bluetooth working in both Squeeze and Windows 7? Could changing the hardware help? If so, what to?
Every tutorial I've seen on installing a dual boot environment assumes you already have an installed OS (usually Windows). My wife's XP system is pretty hosed, and she's been interested in Ubuntu. Because she's ripe for an XP re-install anyway, I'm planning on backing up her data, completely wiping her hard drive, and installing a dual-boot Windows-XP/Ubuntu environment. Any good step-by-steps for this, with good hints on how to partition, etc.?
If not, my plan B is to reformat and install a basic XP system, and then follow one of the tutorials for going dual-boot over an existing install. Does that make sense? I should mention, I've used Linux for years as a user on my ISP, but have only been using Linux on a home system for a couple months; so I'm fairly new to the install and administer side.
I have this machine (motherboard ITX Jetaway NF94-270-LF based on CPU Atom N270, full specs here) as a server for some time now (about 4 years). Debian 8.1 is installed on it.
Two days ago, after a power failure, the machine was not able to complete the boot process. I attached a keyboard and a monitor (on VGA port, the motherboard also as a DVI one, but I don't have a suitable monitor) to be able to see what's happening and interact with the machine. Unluckily, at a certain point during the booting sequence the screen goes blank and the monitor goes in standby mode; apart from that, the boot process continues in the background.
As far as I can recall, this behaviour existed for at least a couple of years (if not from the beginning) and the boot process was always completed successfully until two days ago.
The screen goes blank after the setup of the keyboard mapping. I tried everything to avoid the screen going blank: in the Grub menu I set the "vga" parameter, the "nomodeset" parameter, the grub_gfxmode parameter, I removed the "quiet" option, I removed the "load_video" line, I forced the BIOS to only use the VGA port for the video and so on, in order to disable or configure differently the video and the framebuffer. All these stuff had no effect at all: the screen keeps going blank at the same point during the boot process.
The only way I was able to use a fully booted system through keyboard and monitor was via the rescue mode of the Debian 8.1 netinst image. But that way, of course, I wasn't able to observe the normal boot process. So, I checked the boot parameters of the rescue mode and I found that the only usefull parameter was "vga", which I already used and was ineffective.
I have some problem with Debian 7. Just installed Debian 7 wheezy.
Motherboard Intel D2500CC, graphics - Intel GMA 3600. Monitor (BenQ V2200 Eco) connected via VGA cable. No X server installed.
After GRUB boot as soon as modesetting kicks in, the monitor loses the signal and goes black. Keyboard does appear to be active, as Ctl-Alt-Del will cause a reboot.
I tried nomodeset, vga=791, 771 etc kernel parameters, but this won't work.
I've been using ubuntu for a couple of years rather successfully on my dual-boot Vista/Ubuntu. It upgraded to 8.0(4?) LTS, 10.04LTS and I kept it there until this afternoon I followed the instructions on the ubuntu site to open up a terminal and update-manager --somearg to provide me with a nice little "Upgrade" button on the update manager. I clicked said button per the instructions, let it do it's downloading and whatever else it does. The last step of the installation is a system reboot. I let it do that, and then my grub menu comes up as more-or-less this:
If I select the top one, I get: Code: Starting up ... with a blinking cursor under the S for a LONG time (used the power switch after ~40 mins). I tried the second 2.6.32-32 option for recovery mode. It spit a bunch of gibberish to the screen for a couple seconds and then stopped, presumably doing the same thing, just with 100% more gibberish. I tried booting into Vista, that worked fine. Just to reiterate, I've not yet seen a 10 LTS login screen or desktop, and can't get one yet (just a "Starting up ...") Just to add, I did try searching, but since the only info I had to go on was 8 LTS to 10 LTS upgrade, and "Starting up ...", well those are just hard keywords to get any meaningful info.
I'm trying to make dual boot system with Lenny (64bit) along with WinXP. I'm using one HDD with 2 partitions and installed first XP then Lenny. Everything seems fine till the first boot after fresh install. Lenny starts to boot and after same point the screen goes blank and then is turned off and that's it...nothing happens. Happens so fast that I'm unable to see the exact messages on the screen. Maybe somewhere around staring anarcon?
PC is: Athlon64 X2 5400+ Asus M2V-MX motherboard 3GB DDR2 800 500GB WD SATA2 HDD Radeon x800 GTO video
I reinstalled 2 times and it's the same. WinXP is working fine though but I really don't want it to be my OS... Another "hint" from today: The same happens when I use "Try without installing" of Ubuntu 10.04(i386) Live CD. It starts loading and at some point turns off the monitor. Tried also with 8.04(64bit): Boots till it reach something like "Settings sensor limits" and then it's stuck. I have consoles though (Ctrl+Alt+F1/2/3...).
I tried to dual boot Fedora on a vista system. Now fedora boots as primary and when i try to boot vista i get the message, bootmgr missing control, alt, delete to restart.
After doing a dist-upgrade today, my one year old install of squeeze will no longer boot. It stops with a black screen and has to be hard reset. Cant even get to tty1. The last line in dmesg is: cfg80211: Calling CRDA to update world regulatory domain
mike@vaio ~ $ lspci | grep Network 06:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100.Just wondered if anyone has any ideas before I restore from a backup?
I just recently got a Dell Inspiron 1525 laptop and have installed Debian on it. When I installed it, I did not install the 'Graphical desktop' packages...only the 'Standard system utilities'Everything has been fine, however when I installed Xorg (aptitude install xorg) and restarted my computer, my screen goes blank at bootup. I can see the grub menu, as well as the beginning bootup process, up until udev begins to load. I have a feeling it has something to do with KMS now being loaded but am not sure.
I am having the same problem, as soon as X tries to load my screen just goes blank. I have an ATI Radeon 9550. At first I tried switching between VGA and DVI as well but upon ruling that out, I switch to my on-board video card and that is working thus far, but I'm trying very hard to figure out a way to be able to switch back. Anyways I'll check back in later on if I have any new information I will post.
I have a blank screen on boot up. Has happened since 10.04.It's this problem[URL]I tired their three solutions did not work however clicking F6 and slecting nomodeset before booting got farther then ever and then saidI have tried different images, betas RCS full versions, netbook, derivatives and its all the same.hats going on? Can it be fixed and is this always going to happen now or is it just a two cycle bug?
I have a HP EliteBook 2730p. lspci reports this for my graphic card:
Code: 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 30eb Flags: bus master, fast devsel, latency 0, IRQ 30
[Code]....
I updated from Lucid to Maverick. When I boot with the new 2.6.35-22 kernel the screen stays blank after grub. When I boot the old 2.6.32-25 Kernel everything works fine. I tried to boot 2.6.35-22 in Recovery Mode. When I do this I see some kernel messages in text mode and then the screen goes blank again.
I upgraded 10.10 from 10.04 from the update button from within the update manager. It seemed to upgrade ok but after I shut down and turned it back on it goes to a blank screen. If I then hold the power button to turn it off and back on it then loads to a boot screen where about 6 options with recovery option are listed. The top 2 options do not work as they just go to a blank screen but the bottom 2 give me some other choice including seeming to boot up to a normal Ubuntu environment. How can I fix it so that it boots to a normal Ubuntu 10.10.
I have a toshiba satelite pro laptop (can't think of the exact model at the moment) with 4gb ram + 320gb hard drive. i have been dual booting ubuntu for roughly a year, and throughout all that time windows has become less and less used, therefore last night i took the plunge, and went about installing ubuntu(10.10) as my main operating system and removing windows, i did this via a usb, using Unetbootin.
I used one of the .ISO's from the official ubuntu site, and went through the installation processall went well, no errors within the installation process, hard drives were partitioned fine etc, however when i've come to turn my computer on for the first time this morning i get a black screen with a blinking underscore straight after the toshiba logo flashes up and i get the choice to go to bios options.
If i do go to bios options my hard drive is listed fine, and if i try to boot from my usb again, it doesnt work, and attempts to verify dhcp and eventually tells me it couldnt find a boot file, my laptop however is plugged in via an ethernet cable. it doesnt work with or without the ethernet cable. i have tried leaving it for about half an hour and nothing has changed, i also can't boot to GRUB.
I have a new laptop, I first installed Debian stable, but the wifi card didn't work, and the screen was 1024x768. So I installed kernel up to 3.16 with wheezy-backports, but after the boot, the screen become blank. The only way to see the screen is set "nomodeset" in /etc/default/grub, but It's impossible to see the screen beyond 1024x768 resolution.
I also tried to install linux-image deb packet from [URL] .... , because it worked for someone in internet, but not for me.
when booting my system, I get sometimes a blank screen. I searched around and couldn't find a proper solution. ATI Technologies Inc RV535 [Radeon X1650 Series] The only option I have is to reset the PC and hope for it to boot without the blank screen...
I have got myself into a situation where I see nothing during boot until X starts, and I have no text virtual consoles. I recently replaced my old 9.10 system running on hardware that seemed to be breaking down, with a new system with both an onboard graphics chip (which I disabled in the BIOS as the 1st step), and an Nvidia GeForce 8400 GS card. I installed Windows XP then Ubuntu 9.10, copied all my files across, modified /etc/fstab, /etc/hosts, etc etc., and as the last step I unplugged the 1920x1440 IBM CRT that I'd used during the install and tweaking, and plugged the display into the BenQ LCD on a Belkin 4-port KVM. Oh, I also installed Windows and Splashtop (that mini-Linux that fast boots from the Windows NTFS partition).
I had a problem at that point: I had a lot of trouble getting any signal on the LCD monitor, and eventually got it working but with the whole display half-shifted off the screen (everything was shifted to the right about six inches), and the Ubuntu splash during boot (the sort of spotlight effect with the glowing horizontal line with the light animating along it left and right) was shrunk and only occupied part of the screen. Nor could X detect what kind of monitor it was. I had a lot of problem with a lot of attempts prodding the LCD monitor to complain "Out of range!" (over the top of the Ubuntu three linked circles). I couldn't fix the problem, and in the end installed the Nvidia proprietary driver and ran its X configurator, and suddenly everything snapped back and began working correctly: X ran happily in 1680x1050, filling the screen properly, and X could now correctly detect the monitor as a BenQ.....
