LinuxQuestions.org
Page 1 of 3 1 23
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Aug 28 current : no HAL, no mouse, no good ! (https://www.linuxquestions.org/questions/slackware-14/aug-28-current-no-hal-no-mouse-no-good-479558/)

EvilBill 09-01-2006 05:23 PM
Aug 28 current : no HAL, no mouse, no good !
 
I spent 28 hrs downloading these 2 cd's. I installed this version 3 times. I used the "huge26.s" kernel, everything installed the way it's suppose to.

This distro's installer is the same as Kateos 3.0. I installed it when I was 3/4 alseep, in the middle of the night, no problem, everything worked.

I tried 3 times with this august28 rc3 or whatever it is. Everytime I get to the point where I boot up using the "startx" command, & the mouse won't work. I have my KDE screen with no mouse usable. Then I read there is no HAL. Of course the mouse won't work, none of the other HAL dependant stuff will work either I'm sure.

What am I suppose to do now? This is like buying a car with no steering wheel, what good is it?

raska 09-01-2006 05:42 PM
Quote:
Originally Posted by EvilBill
...This distro's installer is the same as Kateos 3.0...
Everyone knows which one came first :scratch:

Quote:
Originally Posted by EvilBill
....I have my KDE screen with no mouse usable. Then I read there is no HAL. Of course the mouse won't work, none of the other HAL dependant stuff will work either I'm sure....
Well, I have never needed such... amusement... ahem... feature in order for my mouse to work.
Could you please post the contents of the /etc/X11/xorg.conf file? The Section "InputDevice", Identifier "Mouse1" or something like that should give us clues of what's happening. Also check the /var/log/Xorg.0.log file about what might be awry.

comprookie2000 09-01-2006 05:45 PM
In /etc/X11/xorg.conf
what does this section look like
Code:

Section "InputDevice"
        Identifier  "Mouse0"
        Driver      "mouse"
        Option            "Protocol" "IMPS/2"
        Option            "Device" "/dev/psaux"
        Option      "ZAxisMapping" "4 5"
EndSection
May get a hint in Xorg.0.log
Sorry, type way too sloooooow

EvilBill 09-01-2006 05:49 PM
Quote:
Originally Posted by raska
Everyone knows which one came first :scratch:


Well, I have never needed such... amusement... ahem... feature in order for my mouse to work.
Could you please post the contents of the /etc/X11/xorg.conf file? The Section "InputDevice", Identifier "Mouse1" or something like that should give us clues of what's happening. Also check the /var/log/Xorg.0.log file about what might be awry.
I can't, I wiped my hardrive clean. The mouse I installed was the default one at the top of the list, same as in Kateos 3.0. It worked there, my mouse is just a regular one, I am 99.99% certain I picked the right one.

I can see if it was me, I was a nitwit who doesn't know how to do a simple install, but I am fairly certian I am not to blame here. This is not rocket science or Gentoo. :rolleyes:

-------

Maybe I should try install attempt #4, & see what will happen. I looked at that thread about installing HAL, how it was in 10.2 then it was gone, & how to "fix it up".....oh brother.....

raska 09-01-2006 05:55 PM
Quote:
Originally Posted by EvilBill
I can't, I wiped my hardrive clean.
Then I can't help you right now, can I? Don't lose the will to overcome such small problems.

Quote:
Originally Posted by EvilBill
...I am 99.99% certain I picked the right one...
Try another install (I wouldn't trust those release candidates) but let me warn you that whatever type of mouse that you picked while the installation, I'm sure it was not for the X server, only for the gpm service for the CLI. Slackware is quite more based on CLI than most of the other distros as you would have noticed, but everything can work fine once properly configured.

Note: you don't need HAL for your mouse to work

titopoquito 09-01-2006 06:01 PM
Try for example /dev/mouse as device in /etc/X11/xorg.conf if you have a PS2 mouse. That's working fine here.
Can't help with HAL.

Franklin 09-01-2006 06:18 PM
Quote:
I used the "huge26.s" kernel,
Did you install the modules as well?

EvilBill 09-01-2006 06:31 PM
Quote:
Originally Posted by Franklin
Did you install the modules as well?
I don't know, I dealt with every screen, installed all the stuff, bootloader, everything it threw at me, I took care of. Where was/is this module business? I never saw that? All's I know is this "Huge26" kernel is suppose to have everything but the kitchen sink in it, that's still not enough?

I remember something at the start about a module, maybe I forget, whatever it was, I installed that to.

I can do another install, I can get it to the point where I am booted up with the KDE desktop, with the mouse pointer frozen in the middle. Is this fixable, if so I will do it now.


** I am running Slax right now, I can use it to go in there & edit any Slackware files that need to be fixed.

Franklin 09-01-2006 07:21 PM
huge is just the kernel, and while many things are built in (why it's huge) some things are not and the kernel modules will need to be installed from the 2.6.17.11 kernel directory in /extra. (or whichever kernel your install based huge on)

This may or may not have anything to do with your mouse issue, but certainly would rear it's head later on down the road.

HAL has never been in Slackware unless you installed a third party Gnome environment on top of it. As stated in other replies, this is not grounds for reinstalling. Configuring xorg.conf properly is often all that is required. I have also found that the mouse configuration module in the install (GPM setup as stated above) WILL leave you with a non responsive mouse in X if the right mouse type is not selected. To rule this out, you should disable GPM as a test. This is done by, as root, "chmod -x /etc/rc.d/rc.gpm" (no quotes).

Slackware is very easily customized. I would suggest installing the default 2.4.33.2 and make sure everything works as advertised and is configured. THEN install the 2.6.17.11 kernel, modules, and source (not headers) from the /extra directory. You will need to use an initrd, but this is relatively simple. Examples are given in the readme. If you use installpkg and not upgradepkg, you can have both kernels installed and go back to the working one while you trouble shoot. This will require editing lilo of course.

If any of this sounds vague or unfamiliar, I suggest you do some reading.

http://www.slackbook.org/

While I can understand your frustrations, I would recommend considering that if your problems were caused by slackware, you would have an entire forum without mouse function. Think about this before venting in the future. For now this seems to be a case of PEBCAK.

Have fun.

EvilBill 09-01-2006 07:37 PM
I installed everything all over again [#4] This time I loaded the "huge26" at the very start where it ived you those somewhat hidden options. I installed the "USB" mouse at the end thinking maybe that might do it, it is a usb/ps2 mouse plugged into a usb port. Same old story, frozen pointer with the system all loaded normal.

Quote:
Configuring xorg.conf properly is often all that is required. I have also found that the mouse configuration module in the install (GPM setup as stated above) WILL leave you with a non responsive mouse in X if the right mouse type is not selected. To rule this out, you should disable GPM as a test. This is done by, as root, "chmod -x /etc/rc.d/rc.gpm" (no quotes).
How am I suppose to get to the terminal to do that with no mouse?

This is my xorg config file

Quote:
# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me. :)

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the font modules
Load "type1"
Load "freetype"
#Load "speedo"

# This loads the GLX module
Load "glx"

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

# ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "DontZoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

# Set the basic blanking screen saver timeout.

# Option "blank time" "10" # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option "standby time" "20"
# Option "suspend time" "30"
# Option "off time" "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option "EstimateSizesAggresively" "0"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

# Set the keyboard auto repeat parameters. Not all platforms implement
# this.

# Option "AutoRepeat" "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

# Option "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

# Option "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
# Option "XkbLayout" "de"
#
# or:
#
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
# Option "XkbOptions" "ctrl:swapcaps"


# These are the default XKB settings for X.Org
#
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

EndSection


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

EndSection

# Some examples of extended input devices

# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 50.0

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# DefaultDepth 32

# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubsection
Subsection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubsection

EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

2Gnu 09-01-2006 07:52 PM
CTRL-ATL-F6

Log in

#pico filename

Are you sure you're using XFree86? If not, you're looking at the wrong file. Default for Slack is xorg.

rkelsen 09-01-2006 08:17 PM
Quote:
Originally Posted by EvilBill
Then I read there is no HAL. Of course the mouse won't work, none of the other HAL dependant stuff will work either I'm sure.
Since when are mice "HAL dependant"?? Nobody told me. I've been using my mouse without HAL for years! Come to think of it, what else is "HAL dependant"? Not much I can think of. All of my hardware certainly works fine without it.
Quote:
Originally Posted by EvilBill
What am I suppose to do now? This is like buying a car with no steering wheel, what good is it?
Bad analogy. A better one would be "buying a car with no sat-nav." You don't need it for the car to work, but you have to use your own brains...

Edit: As a long time Slacker, it is almost funny sitting here watching all these complaints about the lack of HAL in Slackware... :D There must be 3 to 4 posts here per week about it. I can only begin to imagine the email that PV must get about it!

rnicolson 09-01-2006 09:25 PM
Earlier you said this was a PS/2 - USB mouse plugged into a USB port. Try putting the ps/2 adapter back on and plugging it into the ps/2 port and I bet it will work. With Slackware-current my usb thumb drive will not mount when going through the system icon on the desktop(Need HAL) but when I mount it through command line it works fine. There is some information about HAL in slackware 10.2 and current found here. http://wiki.kde.org/tiki-index.php?p...r_kernel_2_6_x

theoffset 09-01-2006 09:55 PM
Quote:
Originally Posted by EvilBill
I don't know, I dealt with every screen, installed all the stuff, bootloader, everything it threw at me, I took care of. Where was/is this module business? I never saw that? All's I know is this "Huge26" kernel is suppose to have everything but the kitchen sink in it, that's still not enough?

I remember something at the start about a module, maybe I forget, whatever it was, I installed that to.

I can do another install, I can get it to the point where I am booted up with the KDE desktop, with the mouse pointer frozen in the middle. Is this fixable, if so I will do it now.
I think you're missing the kernel modules, just as somebody else just said.

After you install the huge kernel along with all the system, you have to install the kernel modules (the name of the PS/2 module is psmouse). They come as a package under <CD2>/extra/linux-2.6.17.11/kernel-modules-2.6.17.11-i486-1.tgz (here's a link, but be aware that because of its -current nature, the contents may not match your kernel if it takes you too long to get it, http://slackware.osuosl.org/slackwar....11-i486-1.tgz)

Just installpkg them and reboot (or modprobe manually or maybe changing runlevels modprobes most of them or you can also try re-starting udev).

You probably can do this from SLAX, using a syntax like:
"ROOT=/mnt/hda1 installpkg kernel-modules-2.6.17.11-i486-1.tgz"
and reboot into Slack (assumming it's installed in /dev/hda1 and SLAX automonted it under /mnt/hda1)

EvilBill 09-02-2006 12:07 AM
theoffset,

...thanks for trying to help me, but my nerves are too stressed by all this, I give up.[7 tries at installation, frozen everytime]

I threw the disks in the garbage. Slackware, I don't see how people can say this is a good distro. Tomorrow I'm going back to BSD, I've had it with Linux.......


All times are GMT -5. The time now is 11:40 AM.
Page 1 of 3 1 23
Show 50 post(s) from this thread on one page