I just did a fresh install of Slackware 13.1:
However, I get 4 grub listings for Slackware.
1. leads to kernel panic.
Code:
2. leads to kernel panic but with
Code:
3.... welcome to Linux 2.6.33.4 (tty1)
4. Welcom to Linux 2.6.33.4-smp (tty1)
I have never had any trouble with grub, and consequently never had to edit much in grub.
I installed grub from the extras directory on the Slackware DVD in the hope that it would 'find' all my linux systems and XP. (LILO would not find them.)It sort of found then, in that they seem to be listed in the grub menu at start up, but only the 'title Windows XP on (/dev/sda1)' and 'title Linux on (/dev/sda7)' actually launch.
View 4 Replies View RelatedI installed CentOS 5.5 last night using the DVD ISO (from a USB drive thanks to the Universal USB Installer). I selected the Server and Virtualization packages, and finished the install all the way through. At the end, the installer asked me to remove any installation media and reboot the system. After rebooting, the system hangs on a blank screen with a blinking cursor in the top left corner that does not accept text. This is before the GRUB screen appears. For partitioning, I created a 4GB swap partition on sdb and a 16GB ext3 partition on sda, mounted at /, with the remaining free space on sdb mounted at /storage.
Does anyone know why this system is hanging before the GRUB menu?
When i reinstalled Ubuntu i reinstall it on top of an existing not working ubuntu so now in the boot menu i still have 2.6.35-6-generic menu items but i can't find 2.6.35-6-generic anywhere how can i fix it?
View 4 Replies View RelatedI reinstalled Natty yesterday and then installed Fedora on a separate partition.
I now havedouble the menu items in GRUB2 for both of these.
I ran the update grub command in the terminal and it goes smoothly, but the extra menu items still don't go away.
Puzzingly the menu items point to the same partition on the drive as their clone. Both of the Fedora menu items point to sda8
For example.
tl;dr:
How can I remove menu entries in GRUB? I searched but could not find a reliable answer other than re-running update-grub.
How could I remove GRUB and replace it with Plymouth? Ubuntu Software Centre actually shows Plymouth as "Installed" even though it does not run on startup.
I installed Libreoffice from the PPA and understood OOo would be removed. However [URL] Drawing and [URL] Formula remain in the Office Menu. I ran
Code:
sudo apt-get purge openoffice*
but this removed my libreoffice-report-builder plugin and not the menu items. What should I check to see if any of OOo is still around, and how do I get rid of it without removing something Libreoffice uses?
I installed the xfce4-quicklauncher plugin from a tar file in Slackware 13.37. It is showing as installed in gslapt, but it is not showing in the xfce panel's "Add New Items" menu. (see attached images) I tried rebooting and a few google searches. What must I do to get the xfce4-quicklauncher plug-in to appear in the xfce panel's "add New Items" menu?
View 1 Replies View RelatedFirst off, I have spent several hours searching this and other forums looking for an answer to this, and have tried several things, none of which have fixed this issue. Here is what I'm seeing:I performed a new install of FC12 on a Thinkpad R40, 512Mb RAM, with a 40Gb HDD, 38Gb useable, from a live CD. That leaves a little over 9Gb free for expansion. All went well with the install, but the post-boot upgrade would not complete due to an error with the abrt files. I found a thread discussing this and used the suggested method of performing the updates from a shell, which worked fine. There were LOTS of installations, updates, and replacements, and finally the shell returned "Complete!". After a reboot I was going through the Fedora_12_ User_ Guide.pdf and noticed many items missing from the System Menu as described in section 3.1.1.3 "The System menu". Another thread seemed to address a similar issue with su - then yum groupinstall "GNOME Desktop Environment", which I did. It updated over 870 items, then completed with no errors. At this point I logged out and back in, no change, and then tried a reboot, which also did not change anything. Finally, I'm appealing to the community.
View 3 Replies View Relatedi have java app. i want make my Linux dedicated to that application.such that,when Linux load it start the app, start menu have Shutdown,reboot and my application luncher, only one window , desktop right-click also have the same menu-items as start-menu.
View 3 Replies View RelatedI wish to do a fresh install of Slackware without KDE. I could use my Slackware 13.1 DVD but I thought, why not give -current at try? Is there a -current ISO or must I install 13.1, without KDE, and then upgrade to -current? Or, is it possible to remove 'all things KDE' and then upgrade to -current?
View 8 Replies View RelatedI've been using Eric's KDE packages since last June or so, and have been using the same command the whole time to download them. But today I went to get KDE 4.4.5 for the fresh 13.1 install I just did on my wife's laptop and KDE 4.4.85 (hell, yeah!) for my -current box. In both cases the command returned the same error. Here's the command and error message on my -current machine:
Code:
gene@lemon:~$ rsync -av --progress rsync://alien.slackbook.org/ktown/4.5.85 .
@ERROR: Unknown module 'ktown'
rsync error: error starting client-server protocol (code 5) at main.c(1506) [Receiver=3.0.7]
I have 4 1GB memory modules in my AMD64 X2, and Slackware 64-13.1 'free' tells me I only have 3.7GB. Never heard of this problem on a 64bit system.
View 6 Replies View RelatedI'm trying to install FC15 x64, the install goes smooth and reports no errors, I looked around in /tmp/anaconda.log but couldn't see any relevant errors either, basically after rebooting and trying to boot my new install, I get:
error: file not found
Entering recue mode...
grub rescue> _
I've reinstalled 3 times now, first I was using USB, but now have tried with CD too. All I want is for GRUB to be installed on /dev/sda2 which is where my install is, and which is also the default location where the installer supposedly installs it to. I've also tried unplugging my other hard disks, and installing with just the first drive.
I have a new 500GB disk, with a partition with Windows XP, one with Windows 7, one for Ubuntu 10.04, one for /Home and one for swap. The systems were installed in that order. But after finishing with the Ubuntu installation, removing the CD from the drive and restarting, GRUB never showed up, and the system went straight to the Windows OS selector; the one prompting to start Windows 7 or an "Earlier version of Windows". So I can't get to Ubuntu, even though it seems it installed just fine.
As a note: just after the installation process ends and it shows the "remove CD" message, it spilled out a list of I/O errors in some sr0 device or something. But I just installed the same Ubuntu on a friend's computer and it showed a similar error list, yet his system works just fine... However, he doesn't have Windows 7, thus no OS selection screen other than GRUB. I didn't want to rush into editing the MBR or re-installing GRUB before I knew I had to do that.
I have an odd problem. I custom-built a workstation:
MSI Speedster 1 mobo
2x Opteron 2352
4x DDR2 ECC 4GB
3x 150GB WD Raptor, hardware RAID 0
1x 2TB WD Green, standalone
I had Linux Mint 8 installed, but before putting the machine to real use decided to toss Windows 7 on there to see how it worked. Now I am attempting to put Mint 8 back on to get everything set up. There have been no hardware changes since I had Mint installed before.
I can successfully install, but when I reboot I get a Grub error 17. The partition table looks like:
50GB / ext4
400GB /home ext4
...
2TB /backup /ext3
Grub is installed to (hd0), which is the 450GB hardware RAID. It does not make a difference when I run the installation (and then reboot) with the 2TB drive disconnected. Thinking maybe the new ext4 format was messing with Grub, I tried:
200MB /boot ext2
50GB / ext4
400GB /home ext4
And installed again and rebooted. No dice. I'd guess Grub has issues recognizing the hardware raid, except it worked before
Before i would to say sorry because my bad English,
i have install slackware 13.1 with no problem,but the problem is that i reboot after finish install.
in the middle it's stop booting and can't continue...
I installed slack 13 from disk 1, and then went ahead and installed the missing sets using slapt-get (t,tcl,x,xap and y). I skipped the kde and kdei sets. When I start xfce, the fonts are all messed up as shown in the attachment.
View 2 Replies View RelatedI'm not sure how you do it, but it seems like you should be able to. How do you upgrade the version to 13 without burning a new CD? I just used slackpkg update, slackpkg upgrade-all, but when I tried install-new it had nothing to do.
View 5 Replies View RelatedI have just installed Slackware 13.37. After the install - when executing startx for the first time, the xfce desktop freezes when its almost (?) fully loaded.
While loading I can move mouse and if I hit caps_lock the lamp at the keyboard turns on and off.
In the setup I choosed to use vesa - allthoug I afterr that even tried to boot from lilo into vga-mode.
I am, a litle rusty after have been brainwashed through Ubuntu for a few years (sigh) - so I really am not sure which config-file I should edit, and xorg.conf seems to be empty.
I started another thread about this to get help booting into openSUSE after Fedora rewrote my bootloader and deleted all other entries. I managed to fix it but I never did find out why the following commands caused my system to boot to the grub shell instead of the grub menu.
Code:
grub
root (hd0,3)
setup (hd0)
quit
reboot
Can anyone explain to me why these commands caused my system to boot directly to a grub shell? It's as if there were no /boot/grub/menu.lst files for it to use, but after I got everything back to normal, the files were still there.
If it helps, this is how the drive was setup before and now, except Fedora was on /dev/sda4 and has since been deleted.
Code:
Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 263 13316 104856255 83 Linux
/dev/sda3 * 13317 14621 10482412+ 83 Linux
I have a dual boot machine (Win XP + Ubuntu 9.10 on separate physical drives) which was working fine. I now want to replace the Ubuntu 9.10 with LinuxMCE which is based on Ubuntu 8.10. Using the LinuxMCE install disk, I did a fresh install of Ubuntu 8.10 over the top of Ubuntu 9.10 (repartitioning the whole drive). On reboot, I now get a Grub "no such disk" error. I have run the boot info script which produced the following RESULT.txt:
Code:
Boot Info Summary:
=> Grub 2 is installed in the MBR of /dev/sda and looks for
(UUID=6a59ab9e-041f-41e2-b27c-02b8ada4c1af)/boot/grub.
=> Grub 0.97 is installed in the MBR of /dev/sdb and looks on the same drive
in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> Windows is installed in the MBR of /dev/sdc
[Code]....
I did a fresh install of Lucid Lynx, and now when I start up it shows a blinking cursor for a second or so and then my monitor shows an "Input signal out of range" error. The same thing has happened before, and I was able to fix it by editing the boot options in grub to include 'nomodeset'. However, this time the usual grub loading screen where I would normally press esc to edit the boot options doesn't appear. (Spamming esc doesn't seem to work either.) If it matters (which I have an odd feeling that it does) I partitioned the hard drive into an ext4 partition that mounts at / , a swap partition, and another ext4 partition that mounts at /home . I attached a screenshot of what GParted says about it.
View 2 Replies View RelatedMy setup: a work laptop that has a corporate Win7 image, and to which I have added a few partitions to try various linux distributions. The MBR is governed by Lilo from the Slackware 13.37 installation in /dev/sda5. The MBR boots no kernel image directly, it only chainloads the boot sectors of partitions /dev/sda1, /dev/sda5, /dev/sda6 and /dev/sda7. The latter three are formatted ext4.The Win7 boot mechanism traditionally resides in /dev/sda1, and the linux distros are required to install their boot machines into their respective partitions.
What I am trying to say is, I installed Ubuntu 11.04 into /dev/sda7, and told the grub installer the same thing: install yourself into the boot sector of /dev/sda7. Kudos btw for the Ubuntu installer, it comes across as a very professional piece of software.
Bit new to linux but what i saw with gloria in my opinion was a better os than windows. Just done a fresh install with helena on my sata drive and a dual boot with xp pro which is on my on my ide drive my problem is on boot I get to grub loading then boot hangs for 5 minutes before the dual boot screen appears and when it does I can not move up or down to select any options eventually however helena does start.
View 7 Replies View RelatedI have a used PC that came pre-installed with suse 11.2.Unfortunately, I do not have the install disk to use in case of whatever.I already know that when configuring a dual boot with Windows and Linux, it is recommended to install Windows first.I do not have that luxury now as 11.2 is installed and GRUB is the boot loader.Question is, if I boot the Windows 98 install disk on boot, how to not mess up GRUB and still add Windows 98 to GRUB menu?
One hard drive only here. 98gb free.It seems that W98 install will overwrite GRUB in this situation - causing problems. Maybe not, I don't really know for sure.I just need to install windows 98 on the same hard drive and if possible, have suse and w98 visible on boot in GRUB.
An error accoured during the root filesystem check.
Installed fresh Slack 13.0 version, at 7GB virtual hdd, with cfdisk, created two primary partitions, 500 mb for swap, whats left, to second partition, made it bootable, installed full software package, used all default selections, only refused to configure network. At first restart, I got a screen with many statements, that looks like errors, and a last one, that looks like critical error.
An image I have been working on Windows my whole life and only worked with already installed linux systems a bit. Installed RedHat and FreeBSD on VirtualPC previously and succesfully. Now, I stumble upon this error and cant think of next step.
I just finished an install of Slack64 current and it's crashing when I try to start up KDE. I tried setting the VESA framebuffer to 'normal' in /etc/lilo.conf, but no dice.
Here's the log file: [URL]
GFX Card: Radeon HD 6850 (yeah I know.. this is probably the source of the conflict)
Now i've lost possibility to enter my Fedora system. during boot it lost it's modern blue boot screen (with filling drop), it was replaced by standard old boot screen with triple-color stripe. after this boot screen monitor start blinking going on and off. and on last step i'm getting "Fedora 14 boot bla bla bla something" on screen....nothing works except Ctrl+Alt+Delete....system reboots showing successful daemons shutting sequence. How can i edit grub menu from initial grub screen is it possible to it's own 'e' option or 'c' from grub command line?
View 6 Replies View RelatedI have a VIA Epia M 5000 system with 2 western digital 1TB NAS SATA drives connected through SATA<->IDE adapter. Everything installs and writes as expected except... grub. It never boots, after a message 'Grub loading' I always get 'error: no such disk'. I've tried numerous times and has been attemping to fix the issue for the past 2 days.
/dev/sda
0.999TB 0xfd linux raid autodetect partition
1GB 0xfd linux raid autodetect, logical partition
/dev/sdb exactly the same
0.999TB 0xfd linux raid autodetect partition
1GB 0xfd linux raid autodetect
/dev/md0
RAID1 of /dev/sda1 and /dev/sdb1
marked as ext4, boot point /
/dev/md1
RAID1 of /dev/sda5 and /dev/sdb5
marked as swap
update-grub2 in rescue mode generates grub.cfg with SET root=/mduuid/UUID_OF_SDA1
then after that there's search --no-floppy etc --set root=/mduuid/UUID_OF_MD0
I'm writing this from memory but simply the two uuids are different. Is this correct? I get those UUIDs to compare from blkid. All partitions are marked as bootable. grub-install /dev/sda and grub-install /dev/sdb produces no errors. grub-install /dev/md0 does not work, complains about superblocks or something similar.
Grub.cfg file contains insmod raid mdraid1x and similar lines, so that should be ok. Grub drops to rescue mode with message error: no such disk. Not device, but disk. Google finds many results for 'no such device' error, but I am not getting that error. 'ls' produces
(hd0) (hd0,msdos1) (hd1) (hd1,msdos1) ls ANY_VALID_PATH produces empty newline being printed, nothing more.
setting prefixes manually does not work, with error message 'error: file not found'. ls (hd0,msdos1)/boot/grub also produces empty line being printed. Rescue CD and auto-assemble of md0 and md1 works, the files are there, everything okay, except grub.
I just installed debian from debian-live-8.2.0-amd64-standard+nonfree.iso and after installation, which finished without problems, I cannot boot the system. I get the error:
Code: Select allfile '/boot/grub/i386-pc/normal.mod not found
From grub-rescue via ls command I see that I don't have the i386-pc folder inside /boot/grub. I have only two files:
unicode.pf2 and grub.cfg