First: I do not get net access often, so it may be a while between messages.

Install went fine until it tried to boot the default kernel... NOPE!

CPU is an older AMD. The multi-processor kernels will NOT run. (Error about some un-supported instruction)

I fixed that, improperly, but it works, for both the modular and hugh kernels.

Still not working:
1: I have a BUS mouse port, but no buss mouse! How to I get boot to recognize the correct mouse? /dev/mouse wants to point to the BUS port after EVERY boot. (UDEV???)

Likely if I can get this fixed, I can get access to the documentation (including mandatory .png images) to fix the following:

2: USB Flash drives: If at least one is cold-plugged (before boot) it will be recognized, and hot-plugged others will too... UNTIL there are zero connected. After that, it takes a boot to recognize one again! (UDEV again?)

Any clues for the clueless?

This is specifically for getting a synaptics touchpad to work, but I think this might also give you ideas for your mouse problem.

From http://wiki.msiwind.net/index.php/Slackware_Linux_12.1

Step 2: If the touchpad doesn't work at all, try the following:
Look in the /proc/bus/input/devices files; if you don't see a Synaptics touchpad listed, you should see a line that says "H: Handlers=mouse# event#" run "cat /dev/input/mouse# or /dev/input/event#" and move your touchpad, if you get garbled output; edit your /etc/X11/xorg.conf file. Find the section for your mouse and the part were it says "/dev/input/mice" or mouse[x] or event[x], change it to the file that gave you the output and restart the X-server. Your mouse should be active now.
Run "cat /dev/psaux" as root, move around on your touchpad, if it gives garbled output:
edit your /etc/X11/xorg.conf file. Find the section for your mouse and the part were it says "/dev/input/mice" or mouse[x] or event[x], change it to "/dev/psaux" and restart the X-server. Your mouse should be active now.
Try modifying your /etc/modprobe.d/psmouse file, commenting out the line there.



Also, From http://slackware.osuosl.org/slackware/PACKAGES.TXT
These are the packages found in the ./slackware/ directory:

PACKAGE NAME: gpm-1.20.1-i486-5.tgz
PACKAGE LOCATION: ./slackware/a
PACKAGE SIZE (compressed): 233 K
PACKAGE SIZE (uncompressed): 540 K
PACKAGE DESCRIPTION:
gpm: gpm (general purpose mouse server)
gpm:
gpm: The general purpose mouse server, or gpm, allows you to use the mouse
gpm: to cut and paste text from the screen. It also acts as a mouse
gpm: server for applications running on the Linux console, such as the
gpm: Midnight Commander file manager.
gpm:
gpm: NOTE: This program may cause problems when you start X on systems
gpm: that do not use a serial mouse. If you get an 'unable to open mouse
gpm: device' error from X, disable /etc/rc.d/rc.gpm.
gpm:



Since you mentioned modifying the kernel:

From http://forum.soft32.com/linux/instal...ict469121.html

uhci_hcd and ohci_hcd are mutual INcompatible, you either load the one
(with certain USB controllers) _or_ the other (with different ones).
So which one would you put into the kernel image?
As soon as you build a kernel with the former, that kernel will never
work with hardware that needs the latter, because you cannot UNload
a built-in driver.
Auto-loading, either from a ramdisk (if you're booting FROM an
USB-drive) or afterwards from the harddisk works fine as now the auto-
detect in udev/hotplug will detect AND load the correct one.

Other usb modules, like usb_storage cannot be loaded until the right
hardware driver has been loaded first.

You will also see that your USB keyboard and/or mouse will not work
early in the boot cycle, because of the same reasons.


From http://www.slackbook.org/html/book.h...INDOW-SYSTEM-1

If you're running GPM (the Linux mouse server) in repeater mode, you can set your mouse type to /dev/gpmdata to have X get information about the mouse through gpm. In some cases (with busmice especially) this can work better, but most users shouldn't do this.

First, the mouse problem: When Linux boots it sets a link (OVERIDES ANY EXISTIN) /dev/mouse to the empty PS2 mouse port. Then stuff like GPM sees that link, pointing to the wrong place, and I get no useable mouse.

Q: How do I get it to point where it belongs (/dev/ttyS0), or at least not replacing a link that I place there.

As for the USB problem: Note that the USB is recognized, but the USB-Storage devices are only recognized at boot or if the USB-Storage driver is currently active (because there has always been at least one device installed from boot.) UDEVd just never gets messages that one is plugged in except at boot OR if there is currently another recognized one installed.

Q Do I need to manually load the USB-Storage driver?

Let's get a better idea of what state your machine is in.

You did a fresh install of SW 12.1.
smp kernels don't work for you so you need to use the non-smp kernels
Did you patch the kernel sources like you were supposed to? (look in the /extra repo).
What do you mean by you fixed the kernel selection "improperly"?
What kernel are you using now? generic? huge? custom?

Are your users in the necessary HAL groups (plugdev, power)?
Is your /etc/fsab correct?

Perhaps you need to define better mouse options in /etc/modprobe.d/psmouse

If your modules are not built in the kernel and they aren't loading then your either need to unblacklist them or make sure they are loading by your rc.modules-* file.

Correct. (Some instruction not supported)
Where was THAT documented? I am using, mostly sucessfully, two of the four that install loaded. It just pointed lilo to the hugh-SMP.
Install set lilo to boot the Hugh SMP kernal.
I edited /etc/lilocfg (or some thing like that) to use the generic-NON SMP Modular kernal. ( and built the initrd as instructed) I also put the non-SMP hugh kernal in there for testing. (No diff.)
One user (other than root) is in there. But, the problem is that the /dev/sd* devices do not show up becouse the device hot-plug messages never reach the d-bus except 0: while booting. or, 1: If at least one was connected at all times after at least one at "0:"
If it was not, then I could not access when they do work. There is some thing else, much lower level than mount. I think lower level then udev, that is breaking after the boot script.
The mouse message that I get in dmsg (and on screen) that says something like "PS2 mouse common for all mice" is before init runs, but I will look at that.
[/QUOTE]
But it loads IF the device is connected at boot, and stays loaded until there are zero of that device connected. udev never gets the message to (re)load the module after it unloads, or if it is not loaded in the first place.

(I keep trying to put tabs in this message...Nope!)
Thanks for trying. I will look in to the rc.modules-*
kg6hno (Jèrel)

In CHANGES_AND_HINTS.TXT for Slackware 12.1:

Thanks:

Quote: If you decide to use one of the non-SMP kernels, you will need to follow the
instructions in /extra/linux-2.6.24.5-nosmp-sdk/README.TXT to modify your
kernel sources for non-SMP usage. Note that this only applies if you are
using the Slackware-provided non-SMP kernel - if you build a custom kernel,
the symlinks at /lib/modules/$(uname -r)/{build,source} will point to the
correct kernel source so long as you don't (re)move it.
Unquote.

I will look in to that. This sounds like it may be why the driver will not auto-load. But it WILL load while the boot-scripts are running. ?!?

Now, if I can just get the system to use the correct port for the mouse...

Jèrel.

It appears that this just patches kernel source items ??? It appears to make zero difference on the provided kernels. That is the opposite of what the text says. 8-{

I started trying to build a kernel with the drivers built in, but found that usb-storage insists on being a module because some thing un-named that it depends on is a module. That plus a kernel+modules build takes about eight hours. 8-{

For what it's worth, GPM is only meant for those who absolutely need to use their mouse in the shell (i.e. before you run "startx"). I had problems with it in like Slackware 10 or something ancient, and I have never used it since, and never had a mouse issue. I would strongly recommend disabling it unless (like I said) you absolutely need to use your mouse in the shell.

I want to be able to use the mouse for copy/paste in text screens too, at least until I get the mouse to work in X! X appears to be useless without a working mouse!

X appears to want to use the same link as GPM, so X can not find it. 8-{

Almost, all of my problems appear to be related with the differences between the 2.4 and 2.6 kernels.