I installed squeeze with 2 drives, one for squeeze (2.6.32-3-amd64 using 120GB hdd), and one for my old winxp. I used LVM with ext4 on /root, /home, and ext2 for /boot. The install gave me grub 1.98.
When booted, screen says
Loading Grub
Welcome to Grub
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:
fdisk -l
root@SHUM-AMD64:/home/shum# fdisk -l
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
[code]....
I have XP and win 7. I want to triple boot with Debian.When I install, grub finds win 7 and XP and says everything should be fine, but then when I boot, only debian appears.This was fixed by doing update-grub2 after logging in.Now, I have win 7 bootloader as an option. However, when I boot into XP, and then reboot, grub disappers. he screen just says welcome to grub and then a blinking cursor.
View 10 Replies View RelatedI decided to upgrade to Squeeze from Etch.
not upgrade, but moving from etch to squeeze.
Clean new install. Format disks, re-partition...etc.
All goes perfectly well, until I reboot into my newly installed Squeeze.
After the messages from the bios motherboard, there is a black screen with a flashing cursor, and nothing else happens. Now it should have been the GRUB coming up and asking which system to boot into. But there is nothing at all on my screen.
I thought I've done something wrong during install, so I formated the disks again, and re-installed squeeze again. Just paying close attention to every message, before I went further.
And AGAIN, when rebooting into the system, there is nothing on the screen.
Last nigth I upgrade my system to squeeze and it whent well except for grub-pc and udev. If i try to upgrade now udev will not install do to problems with the kernel version and grub-pc can't seem to find the boot image.
[Code].....
yesterday I updated my squeeze amd64 on my Phenom X4 and now it is not booting anymore. Have you experienced the same problem?
After that I noticed the shutdown was not working anymore, it just restarted instead of powering down. This morning it wouldn't boot squeeze anymore, when grub starts and prints "Welcome to grub" (or something like that) the list of operating systems is not shown.
I noticed the updated also included grub and I saw it correctly detected my operating systems.
I am planning to boot knoppix soon and try to reinstall grub from chroot, but currently I am at work.
I try to install to my desktop as Squeeze/ISPConfig3 server, but GRUB does not load after several re-installations.
I have
- 6 x 500GB HDs
- ASYS A8N-SLI Bios SLI-RAID active as only then RAIDSata1-RAIDSata4 can be seen 2 x RAID1 (has to have something) and all drives can be seen by Debian-installer as individuals Same has been working with LinuxMint (both LM10 and LM Debian Edition) (with and w/o fake-RAID)
1st test: Guided partitioning (LVM) for one disk (where /boot will be separated) => Installation OK and starting.
[Code]....
I'm configuring a machine with Debian 6. I booted from the DVD, took the defaults, and it eventually came up with a Gnome desktop. Everything worked as expected.
I then installed gcc, g++, the Debian kernel source, and built a new kernel with preemptive multitasking turned on. It built clean, I ran "make install" and it put the kernel files in /boot. I rebooted and got a kernel panic error, to the effect that it couldn't find the root filesystem.
/boot/grub/grub.cfg shows
"linux /boot/vmlinuz-2.6.32-5-686 root=UUID=1890437b-5884-4b83-97cf-62d39f63c872 ro single"
for the original install, but the entry for the new kernel has
"linux /boot/vmlinuz-2.6.30DW-preempt root=/dev/sda1 ro quiet"
/etc/fstab has
# / was on /dev/sda1 during installation
"UUID=1890437b-5884-4b83-97cf-62d39f63c872 / ext3 errors=remount-ro 0 1"
I've tried changing the grub entry to UUID, but the new kernel still panics. grub-mkconfig and update-grub just rebuild the split UUID=/sda1 grub.cfg. The new kernel still seems to be looking for /dev/sda1 even after changing grub.
I just installed squeeze and at finish it asked me if it write the MBR with gurb.
I say yes, but after restarintg, squeeze doesnot appear in grub.
I also have lenny in the same PC. code...
How can I run squeeze I just installed.
I recently purchased a new Lenovo Thinkpad T420i and am having problems installing the latest version of Squeeze from CD. After receiving the laptop, I started it up, configured Windows 7, and confirmed everything is working correctly. Next I went through the Debian installer, which completed successfully. I'll be dual-booting Windows 7 and Debian, so at the partitioning stage I resized my NTFS partition, added a shared VFAT partition, then used the "Guided" install to create my root and swap partitions. My partition layout is code...
I assumed something was wrong with grub, so I booted the CD into rescue mode and chose to reinstall grub onto the Master Boot Record. But nothing changed. Just to experiment, I went into fdisk, deleted all my new partitions (leaving just the Windows ones), and tried rebooting, but the same error happened. I then went through the Debian installer again, being careful to set everything up correctly, but still, the device won't boot.
I'm not even getting to the grub boot screen, so something is wrong even before the point. Reinstalling grub to the Master Boot Record (grub-install /dev/sda) isn't changing anything. How can I troubleshoot this?
I've installed Lenny with no problem, but I tried switching to Squeeze, and grub for some reason didn't pick up on the Windows partition this time - it just shows the two Linux options (debian and debian single-user). I check the menu.lst file (which I've edited under Lenny with no issues), but for some reason it doesn't exist at all in this install. Is it in a different location with Squeeze maybe?
why grub didn't pick up on my Windows install?
I'm trying to do is protect the computer against housemates. The standard procedure I do with Lenny:
1. Password protect BIOS.
2. In BIOS, always boot from hard drive. Disable booting from any other device such as USB or CD-ROM.
3. Password protect Grub (v1) using the "password --md5 $1$9MuaA/$5TDLgvmcEiCWNr5W9VaMK1" syntax in my menu.lst file.
With the above precautions in place, [I think] the only way to gain root access to the system is to take the case lid off and proceed to do stuff physically (like set jumpers and/or take out the hard drive). Am I correct? My reasoning for this is, the computer boots -> must boot from HD -> must load Grub -> must go to default menu item since others are protected, and cannot command prompt in Grub without password.
Anyhow, In Squeeze, I was a bit disappointed to find out, after doing a bit of Google-research, that Grub v2 (which is standard on Squeeze now) does not easily support password protecting the Grub menu. Am I correct? Will this issue perhaps be addressed in the Squeeze final release? Is this feature dumb anyways because the Grub password is of no use (i.e. my paragraph above is complete horseradish)?
Another thing I would like to do is change the console font and size back to something more "normal" or "classic", not some crazy tiny font that's only found in totally bleeding edge Linux distrubutions <gasp!>. I found that the Squeeze console font (e.g. when I type Ctrl+Alt+F1) is wicked tiny. I wanna change it to "normal". Grub v2 password and console font config?
My Squeeze installation has the horrific 80x25 line display, and I cannot stand it. I know it can do better, because the grub screen is very tiny. I ran dpkg-reconfigure console-setup, but the offerings there aren't much better. I don't know what happened to the good ol' days of grub when all you had to do was pass vga=791 to the kernel to get a decent console size... but it seems they are gone.
I don't really understand this new v2 grub... I don't know why it was necessary to change how it was configured, when it seemed to work so exquisitely. how I would accomplish the functional equivalent of passing vga=791 (1024x768@75hz) to the kernel in grub
i had windows 7 on my system and now i installed debian squeeze but grub does not show my windows 7 in menu for selecting how could repair this problem?
View 4 Replies View RelatedAfter upgrading to Squeeze, which comes with kernel 2.6.32, my system encountered DRM error and booted up with a blank screen. This happened intermittently. Searches on the Web did not give a definite answer. It seemed there was a bug in the kernel and this was cleared since 2.6.31 but I am using 2.6.32.
View 3 Replies View RelatedWhen I try and boot my Debian computer I get the messages: Grub Loading stage1.5. Grub loading, please wait... Error 15 Is there any way of recovering from this - or is it simply a fresh install? I was attempting an upgrade from Lenny to Squeeze and despite a few hurdles it looked like it was all happening. Got the new kernel loading, and the new grub. It looked as though grub2 was working so I ran the grub-remove-legacy-support command (something like that) and now my computer won't boot grub or Linux.
I'm assuming the MBR on my harddrive is lost, however I don't know what state the partition is in. I'm guessing that maybe this has been lost as well. I tried a few tools from the Ultimate Boot CD but nothing here was able to re-install my grub or boot from any partition or even mount my file-system. I'm fearing the worst but would like it confirmed before I blow it all away with a new install.
I just got Squeeze loaded on computer and getting several error message during boot up. Something about 368623 and 368761 PCI Bar 6 collision. This is a first for me on Debian OS. It happens so fast I can barely write it down. Is there a log I can access to see the entire entry?
View 14 Replies View RelatedI have installed vmlinuz and initrd.gz (squeeze) in /boot/newinstallation and added to Grub the lines:titleNova Instalaçãoroot(hd0,0)kernel/boot/newinstall/vmlinuzinitrd/newinstall/initrd.gzNevertheless, when I choose this option at the grub, it begins to start the kernel vmlinuz and thus restart the system. The installed Debian Lenny boots in a normal way.
View 10 Replies View RelatedI'm getting the following error when trying to extract a rar file using Squeeze in XFCE.
"Command exited with status 256."
On a fresh install of squeeze, I can't log in to an AIM account with being immediately disconnected and given this error: You have been connecting and disconnecting too frequently. Wait ten minutes and try again. If you continue to try, you will need to wait even longer.
I waited for several hours before trying to reconnect, but got the same message. Searching for the error led me to some bug reports from upwards of three years ago.
Strangely, this error hasn't occurred on any of my other squeeze systems.
I can ping login.oscar.aol.com as well as login.messaging.aol.com; both resolve to 205.188.251.43 for me. I tried changing the "Server" under "Advanced" to this address, but again I got the same error.
sshd is openssh-server 1:5.5p1-6.
I'm getting "Can't open display" all the time when I log in the server through ssh.
penguin@theblue:~$ xeyes
Error: Can't open display: laptop:0.0
penguin@theblue:~$ export DISPLAY=192.168.1.101:0.0
penguin@theblue:~$ echo $DISPLAY
[Code].....
The problem I found is sshd server set DISPLAY to localhost all the time.
I tried to install Open Office following a guide in OpenOffice.org but after several attempts debian refused to boot properly. I decided to re-install Debian 5.0. When we came to the installation of the boot loader GRUB refused to be installed. I stopped the installation expecting to go back to the beginning. But now it tries to boot saying:Grub loading stage 1.5.
Grub loading, please wait...
Error 15
This is an old Toshiba 3110 with Windows 98SE installed which I have successfully customized and do not want to loose. What can I do to get back into W98SE and then re-install Debian properly?
I try to update the packages before upgrade to wheezy,looks like when I run apt-get update,it shows error as per below:
W: GPG error: http://fosiki.com stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 379393E0AAEE96F6
rat:~# apt-key adv --keyserver keyserver.fosiki.com --recv-keys 379393E0AAEE96F6
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --
[code]....
I tried to install Debian-Squeeze 64-bit from CD [URL] as I thought mistakenly my cpu has 64 bit support. Ofcurse proccess stoped as the kernel wasn't compatible, but only when I removed the 'quiet' parameter I could see the error, when the 'quiet' parameter was passed, process gave no visible error,just stop in the start screen of debian-installer.
View 1 Replies View RelatedI have done a update from Lenny to Squeeze with the update manager within Gnome. And there was a error 126 and the update broke off leaving me with a non working system. The system does start into Debian Squeeze to the command line. Users are in place and a login is possible. X does not work and there a lot of broken and defect packages. I want to repair my system. Is a restore without losing the configuration possible?
View 14 Replies View RelatedJust added Squeeze multimedia repositories in source list,but get this after reload :
W: GPG error: ftp://ftp.debian-multimedia.org squeeze Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 07DC563D1F41B907
However,update for Audacity & Mplayer showed in Update Manager,and I successfully updated.
I downloaded skype 2.2 .deb package on the skype website and tried to install it via sudo dpkg -i skype-debian_2.2.0.25-1_i386.deb and got the following errors:
[code]...
What does the error mean? I am guessing I have a faulty package. old skype can't be used due to segmentation fault error, so I am really hoping for the new upgrade to solve my skype problem.
I am trying to compile Clanbomber in Squeeze but I get the following error message when running ./configure:
checking for DirectFB... found
checking for FusionSound... configure: error:
*** FusionSound 1.0.0 or newer is required. The latest
[code]...
This is my specific solution to my specific problem. After updating to Squeeze from my prior Lenny distro (amd64 with whole disk encrytion using LVM2, dm-crypt, LUKS) everything went well - at first. I was duped like so many, thinking that all was well and I could remove the legacy-grub (aka: Grub1) and just use grub-pc (aka: Grub2). As soon as I removed the legacy-grub and rebooted my laptop, I was confronted with:
GRUB Loading stage1.5 GRUB loading, please wait..Error 15 At this point I wasn't sure if it was a Grub problem or a deeper encryption problem - especially after reading that some people had missing packages in Squeeze (lvm2, dm-setup, initramfs-tools, etc.)
Okay, the solution for me.
1. download and burn to disk: debian-live-6.0.0-amd64-rescue.iso[URL]..
2. scroll to and press enter/return on: text rescue
3. choose a root directory - for example: /dev/blah/root (I wrote down the list of possible /dev/.... for reference - this helped me remember where and what I had partitioned in Lenny)
4. choose: Execute a shell in /dev/blah/root
5. once in the shell, I discovered I needed to mount a few of those partitions that I had written down in order to get access to grub-probe, update-grub, grub-install, etc. You may not have to if your partitions are minimal. I you need to use other partitions, type (for example):
[Code]...
I was upgrading from lenny to squeeze. At the apt-get dist-upgrade step, at some point (after upgrading and configuring) it tried to create a new certificate for my mail server but creation of the certificate failed, dpkg reported an error and the whole process exited with error. So I rebooted the machine and issued again apt-get dist-upgrade but now the certificate was created successfully . After that it upgraded mysql-client and the process finished.
But I don't know if configuring of the upgraded packages has stopped at the point where dpkg stopped. I suppose so, because very few packages were configured at that point. Is the solution to run dpkg-reconfingure -a (or -u ?) or dpkg --confingure -a or something else ? (dpkg has the PACKAGE STATES)
dpkg --configure --pending gives me no package for configuration.PS: At least I hope that all packages were upgraded and a few were not configured. Is there a way to confirm that all packages were upgraded ?