LILO, it's time to get this thing working...

EThitop · 06-01-2004, 10:14 PM

Hey that sounds good to me, I have tried current before, and I told it to update to current, but there is probably something I missed. There is most likely something somewhere that I would have to tell for all the updates to step into effect. Yeah, us men just don't read directions LOL. I think I will try to read a bit more about it though, so I can get Slackware Current. Well, it's off to installing stupid Windows XP Pro and then Slackware 9.1 (then hopefully upgrade to Current).

Thanks for all of your help!

(I created a new thread about swaret b/c it doesn't really belong in this thread, but you gave me an answer about it that I "wanted" to hear so thanks!)

Erik

wmakowski · 06-01-2004, 10:41 PM

I'll give you a couple more options. First, although LILO will eventually work, GRUB is a newer solution with more options and greater flexibility. Check out http://www.linuxgazette.com/issue64/kohli.html for installation instructions. Here's a mini-howto just in case you want to learn more http://www.tldp.org/HOWTO/Multiboot-with-GRUB.html.

Yet another option, how about using NTLDR to boot Linux? You'll still need to install a boot loader on the Linux boot partition to get this to work, but you can leave your MBR alone. Here is a set of instructions for you to peruse http://www.geocities.com/epark/linux...2k-HOWTO.html. There are a lot of other sites out there that cover this. Just use google and search for ntldr boot linux.

Bill

EThitop · 06-01-2004, 11:18 PM

Thanks! I'll be sure to check those out, and I can always switch boot loaders when I want right? Even though I'm sure it's not the "easiest" thing to do.

vectordrake · 06-02-2004, 06:58 AM

Grub and Lilo are pretty easy. Adding Linux to the NTLoader is the biggest job, but not too bad, by the looks of it. Its the one I haven't done yet.

wmakowski · 06-02-2004, 07:45 AM

Yes, you can switch boot loaders on a whim, but once you get a boot loader working there really isn't much need to do so unless you feel like becoming the next expert boot loader loader.

Interestingly enough I have three computers and they all use a different loader (LILO, NTLDR, and GRUB). I tried out the NTLDR method after correcting a problem with my MBR and wiping out GRUB during the fix. I knew I could get GRUB to work again, but thought I would experiment with NTLDR. Low and behold it worked the first time and I decided to keep it in place. Be sure and let us know how things turn out.

Bill

EThitop · 06-02-2004, 11:46 AM

Hey, I did the setup I mentioned earlier, Windows on HDE1, SWAP on HDE2, "/" on HDE3, and "/home" on HDE4. LILO works fine now, YAY!!! NTLoader is just the windows loader right? I know how to do that one and I don't like it (if it is the one you're talking about). I think I will give GRUB a try, just to see the diffence, but LILO is really easy.

Thanks for your help!

wmakowski · 06-02-2004, 02:19 PM

Congrats! Must feel good to finally get it working and booting without a boot disk. Yes, NTLDR is the windows loader. I would agree that it doesn't give you the kind of flexibility that LILO and GRUB have.

Bill

vectordrake · 06-02-2004, 03:47 PM

Now you can add your Slackware from the 200G drive to the /etc/lilo.conf and boot WinXP, Slack, or Slack. LOL

Great job! Many wouldn't have toughed it out.

EThitop · 06-02-2004, 04:32 PM

LOL yeah I think I did leave Slackware on the 200GB hard drive, I might do that to recover some of the old stuff. I have KDE 3.2.2 now, OMG it looks so much better than 3.1.4, who would have ever believed it. Almost like going from Windows 98/ME to Windowx XP, looks great. I can't thank you enough vectordrake for helping me out so much.

And yes it does feel great not having to use that stupid boot disk. The resolution is higher too, 1024x768, loads much faster, and I see the penguin!

Thanks!
Erik

vectordrake · 06-02-2004, 04:36 PM

ha ha! Yeah! BTW, 3.2 has a cute eye candy thing that I just love - bouncing busy cursor! I know its silly, but I love watching that bouncy icon instead of the blinky one of past (you have to enable it, of course)

I was thinking that if you wanted to wait to add the old install to your lilo config, you could add the partitions to your /etc/fstab, so that you could have them mounted and accessible at boot. Perhaps you'll just wipe 'em after all, but you have time to do that.

EThitop · 06-02-2004, 08:53 PM

Ohhhhh, that's how you mount drives at boot!!! I've been wanting to do that, thanks for the tip. Now I have a really embarrassing problem...

Last time I installed Slackware, my mouse didn't work at start, so I searched online and found out that if you edit your XF86Config file, by either browsing to it or using the xf86config wizard, that you can get your mouse working in there. I have the same mouse this time as I did last time, a Logitech Mx700 (a wireless optical mouse) and it is connected via USB. Last time, I got my mouse working no problem, I guess I chose the correct options the first time through, this time I have ran through xf86config so many times and I have been tryin all day to get my mouse to work. I've done several searches here and on google and everything I've found isn't working for me. Also, unfortunately I decided to delete my old Slackware installation (when I was installing the new one on /dev/hde).

I know my mouse is working, batteries are full and it works on Windows XP. I just wonder what I am doing wrong this time around...

If anyone can help, I appreciate it very much. Also, the following post is my XF86Config for my mouse.

EThitop · 06-02-2004, 09:07 PM

Well here is my XF86Config for the mouse section,

Code:

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"
    Option "Protocol"    "Auto"
    Option "Device"      "/dev/mouse"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"	"256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"	"Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"	"9600"
#    Option "SampleRate"	"150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection

Also, I have just thought of something.. Last time I don't think I had Hotplug enabled and this time I remember that I enabled it during the installation. Maybe that could be the problem...?

vectordrake · 06-02-2004, 09:44 PM

Try changing "/dev/mouse" to "/dev/input/mice". USB mice seem to like that. It may work after that. I haven't owned a wireless, but that should work.

EThitop · 06-02-2004, 10:01 PM

VECTORDRAKE!!! I'm sorry but can you be anymore of "THE MAN"??? You are too freaking awesome! When I read your reply, I thought to myself, I doubt that will work. IT WORKED!!! I am in such disbelief right now. You are my favorite person in Linuxquestions.org, you have helped me out so much!

Thanks again!
Erik

vectordrake · 06-02-2004, 10:13 PM

This would be the color of my face right now. I'm glad you're back in the saddle! BTW, if you're nuts enough to go with the latest kernel and KDE, you're gonna be surprised by the performance difference. I just pointed my sources at "Cooker" instead of "Official", so now I am getting the freshest Mandrake stuff. I have kernel 2.6.7 rc1 and KDE 3.2.2 loaded up right now. aRTs decided to crash, but I'm gonna try to downgrade it and see if I can get DKE sound sooner than later (although Cooker is quick like Debian Sid - it won't be broken for long). I can't believe the difference in response between 2.6.3-13/KDE 3.2.1 and the newer stuff. Wow, 2004 is gonna be a good year for the penguin.

Pay it forward, my friend....