SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I started with installing Win XP and everything went fine though i had some problems getting the correct drivers for my Raid controller had to use A8v insted of
A8v Deluxe that i got from the asus webpage, but anyways, back to the problem.
Ive got a 320gb Sata2 hdd with
Xp running on 80gb and has dev name sda1
then i made a Linux swap for 2000mb sda2
and the rest on Linux sda3.
It installed fine and i installed the full installation, but when rebooting i only get the Windows boot and cannot choose on what OS i wanna boot on.
Ive reed many forums about setting in lilo and still havent got it to work.
Now that it only boots on windows if i put on the first slack cd and boot from that where do i start and what commands do i have to fill in, would be grateful for all answers, because im really new to this and would like to have some help. thx....
That one uses the sk98lin module. If you have that ethernet controller, then issue "lsmod" and see if it lists that sk98lin module. If not, issue as root "modprobe sk98lin" and then check "lsmod" again. If it's there, run "netconfig" as root to setup your network. If not, post back.
As for the wireless, follow Eric's instructions here.
Ok now i got the option to choose my boot thx alot but only 1 problem getting a NTLDR file missing when trying to boot from windows, what am i doing wrong???
Yeah, I'm going to quote you so it doesn't look like I'm answering the wrong thing.
We got this neat resource on the internet now called Google!
And Google runs on Linux servers -- yeah, not that Windoze junk like your bank uses.
And Google has this neat feature called <Linux> Google where you can search and just get results for Linux questions -- no Windoze stuff. I took the liberty of running a search for you on the string "NTLDR file missing" and this is what I came up with.
You should be able to boot with your WinXP CD, press F8 to get the recovery console, and type "fixmbr" (without the quotes). That should restore your NTLDR (New Technology Loader) to the MBR. But when you do, it's going to overwrite LiLO. So afterwards, here's the drill to restore LiLO:
1 - Boot with the Slackware CD1 and at the boot prompt type
sata.i root=/dev/sda3 noinitrd ro
which will get you into your Slackware system. Just login as root and type "lilo" (without the quotes) and you should see something like this:
Added Slack *
Then reboot and you should have Slack and Windoze has choices, both booting okay now.
Thx bruce , but with the Marvell i just checked the help while trying to get it to work, tried everythin lsmod modeprobe and also pkgtool but finally i found the sk98lin and readed the helpindex and found loads of drivers to load and got it to work ofc had to reboot to get it to work , but the modprobe sk98lin and KAZAM it worked ,.
Can you post your own /etc/lilo.conf here plus the outpout of Bash command
The lines preceeding with a"#" sign are not used. The essential lines to boot the two two systems in your case should be
#Slackware always use the kernel name as vmlinux and no initrd
image = /boot/vmlinuz
root = /dev/hda3
label = Slackware
# A DOS or Windows partition is booted by statement other=
other = /dev/sda1
label = WindowsXP
There is a possibility that Lilo isn't comfortable with the 320Gb Sata disk. Slackware like stability and hence sticks with the older kernel and its Lilo may not be able to access a hard disk beyond 127Gb. I know for a fact that Lilo has an issue of seeing high number partitions.
My Slackware 10 boots at hda27 (5Gb large) with Lilo 22.5.9 (at about 100Gb position off a 300Gb disk)
My Slackware 10.2 (5Gb large) originally booted with Lilo 22.5.9 but refused to boot after being moved to partition hdc35, which is at about 180Gb position in another 300Gb disk. I overcome it by installing Grub.
A few days ago I installed Slackware 11 in a Sata sdb12, at about 140Gb position of the hard disk and ran into booting trouble with Lilo. Again I installed Grub and now Slackware boots fine.
I stick with the old kernels used by Slackware (2.4.26 for V10, 2.4.31 for V10.2 & 2.4.33 for V11) and the Linux does have an issue seeing partitions beyond 137Gb. For example (just re-checked again) with my SLackware 10.2 working in partition hdc35 normally by asking this Linux to mount /dev/hdc34 will return an error message "Special device /dev/hdc34 does not exist". This is of course wrong if I am using Slackware in a partition even higher up the hard disk.
To install/build Grub in SLackware is a 10 minutes job. The latest Grub 0.97 can be downloaded from GNU/Grub and the operation only take 3 to 4 lines of Bash commands fully documented in the Appendix A of Grub Manual (can be Googled).
After Grub has been build into the Linux you need to provide a Grub configuration file /boot/grub/menu.lst for booting the Slackware but this is possibly the easiest in the business and require only 3 lines. Together with booting Windows these are
title Say My Slackware in the 1st disk partition sda3
kernel /boot/vmlinuz root=/dev/sda3 ro
Title My Windows XP in sda1
#Explanation -->Grub counts from 0 so 1st partition of 1st disk is (hd0,0) and should be sda1
I don't have an issue of using Lilo, as I have about half dozen of them operating beyond the 137Gb barrier, but possibly not in Slackware with the older kernels.
I personally don't like lilo to be installed on my MBR. I honestly have been able to get around all of these issues once I started using the bootloader from windows. If you noticed that if you install two windows, you will have the ability to choose which one that you installed. This is MS's bootloader.
bascially what you are doing is installing grub or lilo to the boot partition of wherever linux is. you then use the "dd" command to copy the first 512 bytes from that drive into a file. That is the file contains information for you to use to launch lilo after you select it from windows boot manager. Here is a rundown.
install slackware not to the MBR but the first sector of the boot partition instead. After you are done installing, you still wont be able to boot into linux until you go into some type of rescue mode or use knoppix.
edit your /etc/lilo.conf file from something like above (saikee) had a good one and add your windows partition.
after you are done you must commit your changes so type:
then you are going to make a file.
dd if=/dev/sda3 of=./bootsect.lnx bs=512 count=1
that will make your boot file. I used "./bootsect.lnx"...but you understand relative pathing. "if" stands for input file and "of" stands for output file.
Copy that file to your booting drive of your windows partition, edit your boot.ini file to say "drive:\bootsect.lnx="Linux". From there you will be able to select windows when you boot and you are done.
I used to dual boot xp and 2000 and linux. I always had issues when I would goto format windows or whatever and I would have to "fix" my lilo bootloader. Sometimes it would work, sometimes It wouldn't.
the above, I have never had any problems with. Hope I have helped :-)