I have Windows on sda1 and just installed Slackware on sda2. There also is a hda data drive, which usually appears first on drive lists. During installation, LILO gave an error (I tried installing both to MBR and root, both times the error was about something like "root: (N6").
Then I did the following
-boot with installation cd
-hugesmp.s root=/dev/sda2 rdinit= ro
-login
[code]....
I have a PC with 2 Hard drives one of which has Windows XP Pro installed. I installed Red Hat Linux 7.2 on the other drive choosing LILO as the boot loader. When I reboot LILO only displays Red Hat 7.2 When I boot Red Hat and go into KDE boot settings I can see that hda has Windows NT. hdb has Red Hat 7.2. I then tried to make the Windows NT partition the default entry. When I try to confirm this an error displays warning me of danger if I proceed. Is there any way to make LILO recognize Windows (preferably without having to reinstall Red Hat), perhaps by installing another bootloader application!
View 2 Replies View RelatedI'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO. Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install. I cannot find 'LILO' type instructions, only 'GRUB' type instructions.
Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?
Edit: I'll probably regret it, but I used Puppy's GRUB installer.
when i load lilo, everything is greenish and weird, i tried to change the picture with Lilo.conf, fallowing the exact instruction given by linux forum, dosnt work. the linux logo got verry strange colors has well,verry ugly.
at first i tried to install my ati driver, but my x1800 is not supported anymore, so i decided to run xconfsetup to use the default ati driver. After that i have been in the xorg.conf generated by the setup and it seem they got the right driver, it say radeon in the device section. another problem i experience is that everytime i lod KDE my default resolution suck, and when i open the control panel and click on display, everything goes right.
the last problem is more serious, when i order my computer to shutdown either by command line or with the logout button, the screen goes black and nothing happen at all. Its sad beccause so far everything else seem to work fine, i installed my network card and my sound card properly.
I just did a fresh install of slack 13.1 on a separate drive to the one I was previously using. I've been having trouble getting lilo to work, so that I can choose between either drive. Lilo is currently installed to /dev/sda, with the old system on /dev/sda1 and the new installation on /dev/sdb1. I keep getting errors like these:
Code: Fatal: Trying to map files from unnamed device 0x0011 (NFS/RAID mirror down ?)
I managed to install lilo from the old system by copying the kernel image from the new system into the /boot/ directory and running lilo. I am now on the new system and trying the same thing in reverse but it isn't working. I have searched around a bit and there's a lot of talk of chroot-ing into the other partition to run lilo. I don't understand why the process isn't working both ways though. I can't run lilo on my new installation even with the two kernel images in the local /boot/ folder. Is this something to do with btrfs or am I missing something to do with lilo? This is my lilo.conf file. I am trying to run lilo using this file from my new installation on /dev/sdb1 and getting the error given above.
[Code]...
i installed slackware 13.1, previously i had slackware 13, i made the following partitions:
[Code]...
everything went fine until i rebooted slackware after installation. lilo didnt boot at all, just a black screen. i booted with the DVD, and checked the lilo config file. the contents on lilo looks fine, just like any other lilo on google. for example i have this: boot = /dev/sda
i installed lilo on the MBR., i then changed this to boot = /dev/sda1 , on root and nothing same thing lilo always complains at the end: Partition entry not found , but how come , /etc/fstab shows all partitions are mounted ,( i am doing this in KDE environment). i reinstalled again , same thing. I also get a warning: video doesnt not support VESA mode, i changed to vga = normal again it complains that video doesnt support vesa even when i set it to normal, (note that i am running lilo after i made those changes, even rebooting , and same thing happens.
when i installed lilo, it let me choose video modes for the boot screen because lilo showed that my video card supports vesa mode, but then it doesnt boot at all. did slackware 13.1 changed so much that my laptop is no longer supported?? everything was fine with slackware 13 or is it because slackware needs a separate /boot partition, if so how come i just installed slackware 13 with just / and swap?
I just installed Slackware 13.37, and it's my first version of Slack.
After installing, Grub was still installed on my system, but since it is supposed to boot an OS that's no longer on the hard drive by default, it drops to the Grub Rescue prompt every time I boot.
How can I boot Slackware from grub, or get lilo to boot my system instead of grub?
I have a question that is really probably a lilo question, but here goes. Can you use lilo to boot different linuxes on separate hard drives. Like this.
/dev/hda1 - Slackware 13 with lilo in MBR
/dev/hdb1 - Puppy linux
Here is my lilo image area:
[Code]...
Boots Slackware ok, but when booting puppy it screws up and seems to be printing the boot messages for the Slackware kernel on hda1. Now, how do I tell lilo to find the puppy kernel?
I have a laptop that I have installed Slack-current on, I am currently using the usb image to boot from. Windows7 is installed on sda2 and sda2 has been marked with the bootable flag, I would like to use lilo to boot the laptop do i install lilo to sda or to sda2?Will win7 still be able to boot using lilo as the boot loader ?
Another issue i noted during install is that the kernel panicked using the dvd to install with an error stating it could not read from the booting device, I eventually used the usb-pxe install to load the system however since 13.1 i have not been able to load a system using the dvd.
I currently have a Slackware system an am using Lilo. I just installed Fedora 13 on a different root partition to play around with, I chose not to install Grub. How can I add an entry to Lilo to boot Fedora? Almost everything I am reading online says to use Grub and not Lilo, is there a reason for this?
View 12 Replies View RelatedI have a WD 80GB ATAPI hard disk for my operatings systems.
The partition table is :
First i installed Windows and then Slackware.
The problem is that in MBR , looks that lilo never installed and when my pc starts, the lilo menu never load it . Boots directly to windows.
What i should do, in order to have the lilo menu in startup?
I'm familiar with editing Grub's "menu.lst" file to add additional OS's to the boot list. Does Slackwares Lilo have a similar config file ? I need to add a second physical drive with Windows 7 on it to the boot options in Lilo. If it's not a config file, how do I add a second os to it ? Slack and Windows are both already installed on two different physical drives so I won't be installing, I just need to add the Windows drive to Lilo.
View 5 Replies View RelatedAfter I complete a big project I'm working on I'm going to be wiping and re-doing my desktop machine, probably in the next day or three. I'm going to be setting up a dual-boot; my first in about three years. I'll be using separate hard disks for this, and installing Slackware second on the bigger of the two drives. When I've done this in the past I've used Grub; Is there anything I need to know or pitfalls I need to avoid doing it with Lilo?
View 5 Replies View RelatedI have just install both fedora 12 and slackware 13 on my laptop I did not install lilo because fedora uses grub I am able to use slackware by using the the DVD and booting from the command prompt I have attached my grub .conf file also when i boot from cd the command is as follows
[Code]...
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd
0801 47428608 sda1 <-- this is my Windows partition
0802 30719552 sda2 <-- this is my Linux partition
0b00 1048575 sr0 driver:sr
0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp
#mount /dev/device /slacktemp
#chroot /slacktemp
#cd /slacktemp/etc <-- for me it told me that doesn't exist
#vi lilo.conf <-- couldn't do nothing and was frozen
#lilo -v -t -b /dev/device
#lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I created a Fedora 13 x86 live image on USB using [URL] I've set it to boot using the USB and when it does I see the 10 sec countdown (or the options if I press a key), I tried all the options to boot the image but the screen just turns black for a few seconds and then the the monitor goes into "power saving mode" and nothing happens (I waited like 10 minutes). What's going on? I am trying to install fedora into an empty (secondary) HD, in the main HD I only have a win XP, and I don't want to burn a cd/dvd that's why I am trying to boot the USB.
View 2 Replies View RelatedI just installed Ubuntu on my laptop, which also has Vista installed. HOWEVER... On boot I only get five options: Ubuntu, Ubuntu (Rey), both MemTests and a Windows Recovery.Where's my Vista gone? I left it's partition completely alone during installation, and I can find all the Windows files in Ubuntu, but I can't boot it
View 5 Replies View Relatedi've had windows all my life. heard about ubuntu 10.0. thought i tried it out. i tried using some dual installation with windows or something (im running, well WAS running vista, btw) i dont know WHAT i did. i got ubuntu working, but Windows does NOT show up in the boot menu?
View 9 Replies View RelatedI'm fairly new to Ubuntu and I like it a lot. However, there's a graphical error which started to happen after the very first bootup. The startup screen (the purple one with the 5 dots that appear) isn't showing anymore. It is replaced by some console technical guff scrolling down my screen (which isn't a problem, because Ubuntu itself works fine, but it just looks a bit rough). Again, on shutdown, it displays some amalgamated mix of more technical jargon, and a terribly lo-res version of the shutdown screen.
Is there any way I can fix this?
Recently I had to a complete system install of ubunty 11.04 and win7. I installed unbutu first, then win7. Well when it was all said and done, I figured when I started, I would get the option to either boot in to ubuntu or win7,all I get is win7.Now I downloaded and installed EasyBCD2.0 configured it, but when I boot again I get either win7 or ubuntu. But when I choose ubuntu it doesn't show nothing. So how to I find ubuntu and get it to boot.
View 9 Replies View RelatedEach time I boot I have to restart samba to see the shared printer on other windows machine. I tought it was the cups problem listed on the forum, but I'm not sure anymore if it's related!Could it be related to the service sequence? I don't know how to look at the service load sequence in ubuntu?
View 5 Replies View RelatedI've got a dual-booting system with Windows 7 and Opensuse 11.2. I had a few other random kernels so I edited /boot/grub/menu.lst to remove them. This was fine after a reboot, then I went to YaST and changed the default boot partition to Windows, because I had edited the MBR and put Windows above the other boot partitions, YaST changed "default" to 0.
Now after a restart the Boot Loader doesn't appear, I just have a flashing cursor. When I try to boot from an OpenSuse installation disc and try repair the Repair Kernel loads but freezes on the OpenSuse splash screen. I've heard this is due to the fact I have an ATI Radeon card, if I hold shift during the CD load to prevent the graphical interface of the CD loading. I can type to boot "rescue" but it freezes on "starting udev...". Essentially I just need to be able to edit menu.lst back to the backup I made or change the "default" value back to 1.
I finally got everything installed and then slackware setup prompted me to reboot. then i did and it just took me back to windowsxpx64. so then i tried booting off my usb, and it worked, however when i login as root, i just get the bash commandline and not interface or programs or anything. i cannot login as any other user and the setup did not prompt me to make another user account. so how would i activate lilo or make it so i can boot with it to slackware? i rather use grub but for now i would just like to get slackware working right.
View 2 Replies View RelatedAnyway since I upgraded to Ubuntu 10.10 when I right-click on something and there is another menu in that menu, it doesn't show up for the first time!
for example if I want to create a an "Empty File", I'll right-click on desktop and when I want to go to "Create Document" menu, it doesn't show up! so I must click somewhere else and try again so for the second time it works!!
I have one install (Slack 12.2) on /dev/sda11, and GRUB (GNU GRUB 0.97) boots it without a problem. I just installed a new Slack 13.1 on /dev/sda1, and GRUB fails to boot it as follows:Quote:
grub> root(hd0,0)
> Filesystem id type ext2fs, partition type 0x83
grub> kernel /boot/vmlinuz root=/dev/sda1
[code]....
I look after some small office where computers run ubuntu. Sometimes they phone me for help. For that reason, I decided to install ubuntu alongside with my slack.I seem to have problems with lilo configuration. Ubuntu is installed on software raid :
/boot = md0 (raid 1 of sda1+sdb1)
/ = md1 (raid 0 of sda2+sdb2)
That's lilo.conf:
Code:
append=" vt.default_uft8=0"
boot = /dev/sda
bitmap = /boot/slack.bmp
[code]....
Code:
Fatal: open /vmlinuz-2.6.31-9-rt: No such file or directory
I can mount md0 without problems and the file name seems to be correct.
I finally installed Slackware and now I have Windows, Slackware and Ubuntu in my laptop. I installed Ubuntu at the last order and at that time GRUB the default loader. But I feel that I'd like to use lilo more, so I booted into Slackware and run "lilo" and then lilo became the default loader.But then I cannot access Ubuntu anymore. Because in lilo there're no information about Ubuntu. So I added some information about Ubuntu according to that of Windows in lilo. But that failed. I still cannot access Ubuntu. I searched for the posts about this problem, and this is what they say:
Quote:
image=/ub/vmlinuz
label=ubuntu
read-only
root=/dev/sda7
initrd=/ub/initrd.img-2.6.28-13-generic
or something like this. But in my slack I cannot find the image or the initrd.
I have been given a new old computer, Asus K8N-E with a 2GHz AMD Athlon 64.OpenBSD and Debian works like a charm. But with Slackware 13.1, LILO won't be installed properly. There are two disks: a 10GB ATA-drive with the system and a 250GB SATA-drive as a data repository.
Apparently the computer insists that the SATA is the first disk. Subsequently the bootable partition is not on the first disk and disables LILO to be installed. This is when I try to install LILO to a partition. When it is installed to MBR, it says something about overlapping and can't boot.
I've read that you can fix lilo after a bad edit by booting from install cd1 and entering: Code:boot: bare.i root=/dev/hda X noinitrd ro at the boot prompt. Can someone confirm this or suggest a better way? I'm using slackware 13.
View 3 Replies View RelatedI'm currently dual-booting slack 13.0 and ubuntu 10.04 When slack was originally installed, I had an earlier version of ubuntu on it, and lilo did not pick up the ubuntu. At that time, I didn't care, because I had no use for the 'old' ubuntu. When I installed ubuntu 10.04, the boot config file (/boot/grub/grub.cfg) did include an entry for slackware. Great! I am looking forward to upgrading slack to 13.1, but I want to make sure this time that I can also boot ubuntu, should I need to use it.
1)Slack installation instructions that would enable me to include the other distro in the initial install
2)Instructions on how to edit andprocess lilo.conf after the slack What follows is a dump of df from the ubunutu 'side'..
Code:
tim@bart:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda6 52866604 6227476 43953640 13% /
none 1478976 300 1478676 1% /dev
[code]....
