LinuxQuestions.org - slack newbie questions, vi, xorg 3button mouse, tripleboot with lilo

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - slack newbie questions, vi, xorg 3button mouse, tripleboot with lilo (https://www.linuxquestions.org/questions/slackware-14/slack-newbie-questions-vi-xorg-3button-mouse-tripleboot-with-lilo-293530/)

slack newbie questions, vi, xorg 3button mouse, tripleboot with lilo

I just installed slackware 10.1 and I have some questions.

In debian when I run vi and use i (for insert) I get a huge message at the bottom with --INSERT--. I think this is the mode the program is in. But in slack whether I run vi or vim I don't get that functionality. Can I fix that?

I want my mouse scroll wheel to work. I opened the /etc/X11/xorg.conf file and tried uncommenting the line about logitech mouses there but it didn't work. Neither did the m$ mouse thing work. I have a logitech mouse. How do I check if my dev is right. I just found out that the middle button works for copying and pasting files, how do I make it scroll then?

Quote:

# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

# Option "Protocol" "Auto"

# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
Option "Protocol" "PS/2"

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

# Option "Device" "/dev/mouse"
Option "Device" "/dev/psaux"
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"

# 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"

I'm a bit confused how lilo does the triple boot now. I have one HD with windows on it that works fine. The other HD has debian and slackware on it. What is shared between those. Cause I installed slack with a 2.4 kernel and after I ran lilo in debian slack uses the 2.6.8.1 kernel I use in debian.

When I run make install after the kernel compile I get this error:

Quote:

root@slackware:/usr/src/linux# make install
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/asm-i386/asm_offsets.h
CHK include/linux/compile.h
Kernel: arch/i386/boot/bzImage is ready
sh /usr/src/linux-2.6.8.1/arch/i386/boot/install.sh 2.6.8.1 arch/i386/boot/bzImage System.map ""
Warning: The boot sector and map file are on different disks.
Fatal: open /boot/vmlinuz-2.6.8.1: No such file or directory
make[1]: *** [install] Error 1
make: *** [install] Error 2

I assume this has something to do with my current setup with more kernels.

Quote:

# Linux bootable partition config begins
image = /boot/vmlinuz-2.6.8.1
root = /dev/hdb1
label = Debian
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb7
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = windows
table = /dev/hda
# Windows bootable partition config ends

When I run lilo from slack I get the 2.4 kernel in debian where I'd normally had a 2.6.8.1 kernel and if I run lilo in debian I get a 2.6.8.1 kernel in slack. So should I have made a small partition instead of trying to run 2 images from 2 different /boot folders?

hi dark leaf. The 'this is how i do it all' sticky in the slack forum shouldp point u in the right direction about the mouse.

Basically u need to specify Z X axis mapping and a 5 button mouse.....

The 2.4 kernel is still default in slack.

download the 2.6.10 kernel. Again the sticky above this post will guide you through. I can help if u run into probs (or try!!)

running two different boot images i fine. I imagine a kernel compiled in debian won't work in slack...

Quote:

Originally posted by satinet
hi dark leaf. The 'this is how i do it all' sticky in the slack forum shouldp point u in the right direction about the mouse.

Basically u need to specify Z X axis mapping and a 5 button mouse.....

The 2.4 kernel is still default in slack.

Thanks I know how that works but I thought that was just for xfree86 and not for x.org

Quote:

download the 2.6.10 kernel. Again the sticky above this post will guide you through. I can help if u run into probs (or try!!)

running two different boot images i fine. I imagine a kernel compiled in debian won't work in slack...

I know how to download and compile kernels and stuff and I choose not to use 2.6.10 now since it breaks my video card driver (nvidia tnt2).

The strange thing is that the kernels are quite interchangeable. Some options don't work but for most part there's no problem. And I the kernel from the distro I last ran lilo from. So something is wrong with my setup and I guess that's that I don't have a seperate /boot partition but try to run 2 images from 2 different partitions now?

Thanks for the help!

edit: I looked in that thread and getting the mouse working is in xf86 there not xorg

why don't you use the 2.6.8.1.kernel for both....?
just copy the module_tree from <deb>/lib/modules to <slack>/lib/modules,
and edit the lilo.conf to boot only that kernel with 2 diff. root part.'s.

egag

So also having both the /boot folders the same? Sounds like the easiest solution :) I already tries installing that kernel in slack but just copying will do as well I guess and since it gives an error anyway now. Think I'll do that but I'm still curious on how it's possible that the kernel from a completely different partition loads cause lilo was run last in there.

About the vi "problem" you should copy /usr/share/vim/vim63/vimrc_example.vim to ~/.vimrc
That will give you a nice configuration to start :)

Thanks for the info on vi!

I got my mouse working now too. Had to use IMPS/2 protocol.