have the following issues with kde: when I try to login it shows a blackscreen with black cross-shaped pointer for a moment and then again login box appears. When I execute startx from tty kde loading freezes at splashscreen: I see all icons in a row but the last one (KDE button) is blurred.I have debian wheezy/sid, kernel 2.6.37.2, xserver-xorg 7.6+7, xserver-xorg-core 1.10.3-1, nvidia driver version 275.21.Here are logs.
kdm.log: X.Org X Server 1.10.3 Release Date: 2011-07-08
Issue: Black screen displays after nVidia splashscreen.
History: I performed a clean install of Fedora 12. I performed NVidia driver "GEForce 4 and below" install for a PAE kernel as found here:[URL]..I kept a log of each command in the order performed:
[Code]...
Well, I just got back from the Pepsi Center after watching the Denver Nuggets NBA basketball team look silly against the Dallas Mavericks. 4.5 hours later and I still have a black screen. Was it Einstein who said, "it is insanity to do the same thing, the same way, over and over and expect a different result"? I feel I will been testing that hypothesis soon.
I was installing sqeeze i386 on my laptop VOSTRO 1400 and got this the 'grub-pc' package failed to install into /target/. without the GRUB boot loader, the installed system will not boot.
sudo chmod +x /etc/init.d/local.autostart And sudo update-rc.d local.autostart defaults 80. After this ubuntu hangs on the splash screen during shut down. If I remove the script by doing: sudo update-rc.d -f local.autostart remove
I don't like the username/password default screen, but i like the ones in /usr/share/backgrounds. I've been trying to change it for few hours. None of the advices on The Net work. I tried:
1) gconf-editor and /apps/gnome-session/options/splash_image gconf-editor /schemas/apps/gnome-session/options/splash_image I set it to picture file path, or splash/filename.png or even copied the desired picture to /usr/share/pixmaps/splash/ubuntu-splash.png - no changes
2) gdmsetup has no such option for me 3) also installed startupmanager - nothing as well.
I upgraded last night from 10.10 to 11.04. Things went well, download was quick, install was fine. I then tried to login, laptop accepted the password, splash screen appeared (jpeg file type); I had downloaded this quite a while ago;and I get the standard icons for KDE, but the laptop now freezes on the last icon, and stays there. The laptop makes the KDE login sounds/theme, but I cannot see the desktop.
I tried to login with out the desktop, which I can do, but I do not know where I have to go to remove the splash screen.
I'm running 64-bit 11.3 on a Dell 1535 laptop.At lunch today, the system booted-up as normal, then shut-down as normal. A handful of updates were installedduring that time.This evening, however, I arrive at the password splash screen, enter my password, and then the system churns a few seconds before resetting the splash screen. No error message, no "wrong password," just a normal splash screen. I tried going into Xen, the default 11.3 and failsafe -- same thing happened with each. When I navigated to the command line, my password worked fine, both for user and super-user.
I have no interest in eye-candy. I want to know how do I disable the boot splashscreen completely. I prefer a text-only boot screen, without any images or animation. NOTE: I am using Ubuntu 10.04 .
I am helping my pal to get into Debian (yes first timer).He is running W7 on a 500G SATA HDD and he has another 250G SATA HDD that he wants Debian to go to.Will Debian install grub on the master bootloader even if the installation is going on a separate hard drive?I have dual boot before but on the same hard drive.
I am trying to get Debian 6 to work on an hp Z400 - the problem is that it came with a NVIDIA Quadro NVS 295 graphics card; there may be a driver for Linux, but it doesn't matter, because GRUB insists on switching to some sort of graphics mode and the screen just blanks and switches itself off. Is there any way to make sure during installation that GRUB gets configured to stay in character mode only?
I have downloaded the Wheezy DVD 1 and started the istallation process. The installation time is strangely very short in respect to the Squeeze release, anyway
The GRUB installation step fails. I terminated the installation without a bootloader and rebooted from DVD with the rescue boot option.
Now I asked for a console to try to manually install the bootloader but the following command:
# grub-install /dev/sda1 [where sda1 is my root partition]
I'm attempting to install Debian to an NVMe SSD (Samsung 950 Pro), however both Jessie and Stretch images fail to install grub.
Checking the syslog reveals the following error: grub-probe: error: failed to get canonical path of /dev/nvme0n1p5
Further Information: Fast-boot is disabled in the UEFI, and boot mode is set to UEFI only, no CSM. I do not see any option for 'Secure Boot' if it's relevant to the issue.Windows 10 has already been installed, which created several partitions. The ESP/EFI partition appears to be on nvme0n1p2I only created one partition for Debian - / on nvme0n1p5, no separate partitions for /boot, /home etc.
I have just upgraded my Xen system from squeeze to wheezy. Things seem to have worked except for one very important problem: I'm getting two grub menus. I get one white-on-blue that comes up first. It says GNU GRUB version 1.99-27+deb7u2 at the top. (It defaults to the wrong image... but that is an issue to address later.) I choose "Xen 4.1-amd64".Then I get a second grub menu that is white on black: GNU GRUB version 1.99-27+deb7u2 at the top. I have two options "Debian GNU Linux with Xen 4.4-amd64 and Linux 3.2.0-4-amd64" and the other "Debian GNU/Linux, with Xen 4.1-amd64 and Linux 3.2.04-amd64 (recovery m->"
This is reminiscent of the cascade option from upgrading from legacy grub to grub2... but both menus say 1.99-27... so I don't know what the heck is going on here. I have tried running upgrade-from-grub-legacy and grub-install and grub-updater etc. etc... but it always comes up the same. I cannot have that. This is a server, I need it to boot to the appropriate kernel image -- and preferably with only one grub menu!Here are the grub-related packages I have installed:
Code: Select all# aptitude search grub i grub - GRand Unified Bootloader (dummy package) p grub-choose-default - Control Grub Default through a GUI i A grub-common - GRand Unified Bootloader (common files) p grub-coreboot - GRand Unified Bootloader, version 2 (Coreboot versi p grub-coreboot-bin - GRand Unified Bootloader, version 2 (Coreboot binar p grub-disk - GRUB bootable disk image (dummy package)
I have an amd64 system and am attempting to install 7.8. I have two 4TB hard drives, and would like them in this configuration:
[*]md0: RAID-1 root [*]md1: RAID-1 data filesystem (which will be about 3.9TB)
The drives have GPT.The debian installer worked fine until it was time to install grub, and then it said grub could not be installed (fatal error).I'm wondering if I need to create a small /boot partition (non-RAID)? Other than swap, the physical partitions supporting md0 and md1 are the only ones I created. fdisk shows the typical 1MB partition I see on GPT disks, though I'm not all that GPT-savvy.
I was wondering if a lot of people advise to install Grub in the MBR but that means the last distro installed will control the booting and that distro's grub will become the bootloader? I am finding it really difficult and complicated if you don't want that situation and want to control which distro's grub does the booting. Grub2 works differently than Grub Legacy but if you use Grub Legacy and the menu.lst, I never know what entry to use when you are adding them. I have some idea but when I edit a grub entry for another distro, it never boots properly because the content I have there isn't correct.
I had windows 7 and i installed ubuntu both on primary partitions. They were running normally and the dual boot was working well. After that I installed debian on a third different logical partition of my disk and then only debian was running and windows and ubuntu didn't. Ubuntu does not seem even when the computer starts! Then i reinstalled ubuntu over the debian so i can run only ubuntu. I cannot see windows 7 at all when grub starts
command sudo fdisk -l gives me:
Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes
[Code]....
Partition table entries are not in disk order
Why i have two * in boot column? I have tried some methods i found on the internet but didn't work.
I am trying to install Debian onto my ASUS Eee PC 1015PE from a USB flash drive. The problem I am having is that the primary HD is detected as the USB flash drive. I have to set it up this way so that it will launch the installer. Everything works great until I get to the part where it is installing Grub. It wants to install to /dev/sda instead of /dev/sdb. I don't see any place to change this. Once I install and remove the flash drive it will be sda.
After finishing installation of Debian to a USB drive with XP on disk0 , the system does not boot and reports the Grub error 21. I tried install for 2 times with same results.
I installed Windows Xp 64bit(in a partition called d:) with dual boot with Debian Wheezy. Installed first Windows Xp and after Debian Wheezy, but grub is not seeing Windows!
Look at my "fdisk -l". root@robgeek:/home/rob# fdisk -l
Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xe274e274
I am running Wheezy as my main OS in the first drive in my desktop. I use the 2nd drive for data. I am trying to add another OS to multiboot. When I ran grub-update in Wheezy, I am getting device letter for the root device instead of UUID in grub.cfg, in the os-prober section. Like this
I'm thinking about switching to Debian from Ubuntu, so I installed Debian (debian-7.8.0-amd64-DVD-1) in dual boot with my Ubuntu 14.10 (Uefi install). Installation process was OK (I think), I got a working GRUB that recognizes both OS, but Debian boots to a blank screen with a flashing cursor in the top left corner (Ubuntu boots perfectly). I also ran into some graphics-related problems while installing/booting Ubuntu, due to my AMD GPU graphics, that I solved adding the nomodeset option to the kernel in GRUB, but that no longer seems to do the trick here. Here's some info about my machine:
HP Envy 15 lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
[Code] ....
I don't know why they are listed as microsoft basic data.
I did an install of Jessie on a Macbook 2,1 to be the machine's only operating system, but it won't boot, showing only a black screen with a blinking cursor. I think the problem is caused by a mistake I made during the installation process, where I selected yes for the prompt:This machine's firmware has started the installer in UEFI mode but it looks like there may be existing operating systems already installed using "BIOS compatibility mode". If you continue to install Debian in UEFI mode, it might be difficult to reboot the machine into any BIOS-mode operating systems later.
If you wish to install in UEFI mode and don't care about keeping the ability to boot one of the existing systems, you have the option to force that here. If you wish to keep the option to boot an existing operating system, you should choose NOT to force UEFI installation here. Force UEFI installation?
i have installed debian but during installation my installed windows 10 was not found by the grubloader. i have installed windows 10 on my ssd and the debian on my hdd. nevertheless i installed the grub loader on the master boot record, because it said i could still configure it so it can boot both the windows and the debian.The debian installation is running fine. But i now want to boot the windows too. The problem is i have never worked with the grub loader yet and i am little scared that i will do something wrong.How can i get grub to load my windows ?
I had a dual boot with windows 10 and Ubuntu 14.04, and I just decided to move from Ubuntu to Debian, but I didn't unistall Ubuntu. I just deleted it's partitions (/, /home, swap) and used the new allocatable space. When I was doing the partitions I noticed that the installer didn't allow me to choose between logical and primary partitions (not sure if this is important).
When I continued with the installation process, in the GRUB section the installer detected two Windows Vista options and later I selected /dev/sda as the disk for the GRUB (MBR). When I tried to boot, a GRUB command line screen from ubuntu appeared, when I wrote exit a message appeared "Boot succesfull" and then it sent me to the Boot selection from my laptop.
From there I can choose to boot Windows 10 normally or select a disk partition that sends me to the Debian GRUB from where I can boot Debian normally, but the Windows entries that appear (Windows 8.1 and Windows 8 recovery mode) fail to boot. So when I boot the Debian GRUB appears.
I want to use my BootIt NG boot menu. How would I go about installing Debian 5.0.3 and prevent Grub from loading into MBR? I don't remember being asked by the installer where to put Grub. Unlike Fedora where you can choose MBR or boot section of the target partition. Debian 5.0.3 -
After one year of squeeze use without problem (and without upgrade) on a laptop and I decided to upgrade everything today. During the upgrade, I was asked what partition grub should handle. There was 2 choices /dev/sda and /dev/sda1. I checked only the last one and this is I think the source of my problem.
Now restarting the system, grub fails and reports
Entering rescue mode... error: the symbol `grub_xputs` not found and leave a useless prompt grub rescue>
I don't have a rescue cd at hand right now. I have a usb key with some old version of eeebuntu (my laptop is not a eeepc) and surprisingly I can boot on it.
I am new to Debian but have some basic experience with Linux and am currently trying to triple boot Windows 7, Fedora 16, and Debian on an HP Pavilion dv7. I have the Windows Boot Loader on my MBR because I've heard that Windows updates can cause boot issues if GRUB is installed there. This means that I've been installing GRUB in the /boot partition for each Linux distro and creating corresponding entries in the Windows boot menu.
This has worked in the past with both Fedora and Ubuntu, but I have not been able to work around it with Debian. When I choose my Debian option in the Windows boot loader, it loads GRUB but hangs after it prints "Welcome to GRUB!", and I have to restart the computer. I would like to hear what more experienced Linux users have to say both about why this isn't working for Debian and about if keeping the WIndows boot loader is the right way to go.
Also, here is my partition layout:
Partition 1: SYSTEM (HP pre-installed) (209 MB) Partition 2: Windows Partition (472 GB) Partition 3: Extended (160 GB) 1: /boot for Fedora (524 MB) 2: Physical Volume for other Fedora partitions (79 GB) 3: /boot for Debian (749 MB) 4: Physical Volume for other Debian partitions (80 GB) 118 GB free space Partition 4: HP_TOOLS (HP pre-installed) (108 MB)