Hallo,

Du bist in der richtigen Datei. Wenn der Eintrag dort fehlt könnte dies auch der Fehler sein.

So sieht die komplette Datei aus:

## Path:        Hardware/Hotplug
## Description: Common hotplug options
## Type:        list(default,off,verbose)
## Default:     default
## ServiceRestart:
#####################################################################
# Common Hotplug Options
# ^^^^^^^^^^^^^^^^^^^^^^
#
# This variable controls the amount of output of the hotplug service.  With
# 'default' (or '' or 'no') it prints only few messages and errors to syslog.
# Setting it to 'off' it will be absolutely quiet. With 'verbose' (or 'yes') it
# prints some extra debug output. With 'max' it will pollute your sysconfig
# with every single detail.
#
HOTPLUG_DEBUG="default"

## Type:        yesno
## Default:     yes
## ServiceRestart:
#
# If you like acoustical feedback at plugin then set this to 'yes'. It will
# beep like cardmgr does: Two beeps, one for module loading another for
# interface setup. High beep at success, low beep at failure.
HOTPLUG_BEEP="yes"

## Type:        string
## Default:     yes
## ServiceRestart:
#####################################################################
# USB Options
# ^^^^^^^^^^^
#
# Enable or disable USB hotplug event handling
# Attention: if you disable USB hotplug and you have
#            the USB input devices as module your keyboard
#            will be dead
#
HOTPLUG_START_USB=yes

## Type:        yesno
## Default:     no
## ServiceRestart:
#
# /sbin/usbmodules seems not to talk to the USB stack properly in all
# situations. And there is a alternativ function in usb.agent to use.
# Therefore we set the default to not using /sbin/usbmodules.
# You may change it here if you like to use it.
#
HOTPLUG_USB_USE_USBMODULES="yes"

## Type:        string
## Default:     "ehci-hcd ohci-hcd uhci-hcd usb-uhci uhci usb-ohci ehci-hcd"
## ServiceRestart: hotplug
#
# The hostcontroller drivers will be probed in that order
# It is useful for the uhci/usb-uhci battle
#
HOTPLUG_USB_HOSTCONTROLLER_LIST="ehci-hcd ohci-hcd uhci-hcd usb-uhci uhci usb-ohci ehci-hcd"

## Type:        string
## Default:     "evdev joydev"
## ServiceRestart: hotplug
#
# These modules will be loaded when usb hotplug starts. These are at least
# modules for which no hotplug events is created e.g. input devices
# If you are going to use old XFree86 3.x you may add 'mousedev' and 'input'.
#
HOTPLUG_USB_STATIC_MODULES="evdev joydev mousedev keybdev"

## Type:        string
## Default:     scanner
## ServiceRestart:
#
# These modules should be unloaded on an USB "remove" event
# It is useful for some device to reinitialize the hardware
#
HOTPLUG_USB_MODULES_TO_UNLOAD="scanner"

## Type:        string
## Default:     "pegasus usbnet catc kaweth CDCEther"
## ServiceRestart:
#
# If one of these modules are (un)loaded, we assume the device to be
# a network device and write a HW description for the following net
# event.
#
HOTPLUG_USB_NET_MODULES="pegasus usbnet catc kaweth CDCEther at76c503-rfmd at76c503-rfmd-acc at76c503-i3861 at76c503-i3863 prism2_usb"

## Type:        integer
## Default:     3
## ServiceRestart:
#
# The USB stack loads drivers in the background
# Other runlevel scripts may run before a needed driver is loaded
# As example, printer.o might not be available when rclpd runs
# If you get errors from lpd or gpm with your USB printer or
# USB mouse, increase this value to 5 or more.
# Hint: sleeping for minutes is nonsense
#
HOTPLUG_USB_DELAY="3"

## Type:        string
## Default:     yes
## ServiceRestart:
#####################################################################
# Network Options
# ^^^^^^^^^^^^^^^
#
# Enable or disable NET hotplug event handling
#
HOTPLUG_START_NET="yes"

## Type:        string
## Default:     8
## ServiceRestart:
#
# In future hotplug will hopefully be able to know which piece of hardware is
# behind a given network interface. But currently there is no easy way to get
# this information easily.
# At the moment we write HW descriptions at USB or PCI hotplug events, which
# then can be read by the NET event. This may cause race conditions if you
# plug several deveices at a time.
# If this does not work for any reason we use the string in
# HOTPLUG_NET_DEFAULT_HARDWARE when calling if{up,down}.
# Set it to what you use as hotplug NIC: pcmcia, usb, firewire.
#
HOTPLUG_NET_DEFAULT_HARDWARE=""

## Type:        string
## Default:     8
## ServiceRestart:
#
# Here you can adjust how long to wait for a HW description from an USB or PCI
# event. If set to '0' we dont try to get a HW description and always use the
# value from HOTPLUG_NET_DEFAULT_HARDWARE.
# Set time in seconds; default is '8', because some PCMCIA NICs need long for
# some negotiation jobs.
#
HOTPLUG_NET_TIMEOUT="8"

## Type:        yesno
## Default:     yes
## ServiceRestart:
#####################################################################
# PCI Options
# ^^^^^^^^^^^
#
# Enable or disable PCI hotplug event handling
#
HOTPLUG_START_PCI=yes

## Type:        string
## Default:     ""
## ServiceRestart:
#
# These modules should not be unloaded on a PCI "remove" event, because
# they cause then to much trouble.
#
HOTPLUG_PCI_MODULES_NOT_TO_UNLOAD=""

## Type:        yesno
## Default:     yes
## ServiceRestart:
#####################################################################
# IEEE1394 (Firewire) Options
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^
#
# Enable or disable IEEE1394 (Firewire) hotplug event handling
#
HOTPLUG_START_IEEE1394="yes"

## Type:   string
## Default   "ohci1394"
#
# Host controller type is either ohci1394 or pcilynx
HOTPLUG_IEEE1394_HOSTCONTROLLER_LIST="ohci1394"

## Type:   string
## Default   "raw1394"
#
# add IEEE1394 drivers that do not trigger hotplug events
HOTPLUG_IEEE1394_STATIC_MODULES="raw1394"

## Type:        string
## Default:     eth1394
## ServiceRestart:
#
# If one of these modules are (un)loaded, we assume the device to be
# a network device and write a HW description for the following net
# event.
#
HOTPLUG_IEEE1394_NET_MODULES="eth1394"

## Type:        string
## Default:     ""
## ServiceRestart:
#
# These modules should not be unloaded on a IEEE1394 "remove" event, because
# they cause then to much trouble.
#
HOTPLUG_IEEE1394_MODULES_NOT_TO_UNLOAD=""


Vielleicht hilft Dir das weiter.

Hei Penguintux,
nun habe ich auch die hotplug-datei ändern können, danke für die Hilfe.

Allerdings musste ich dann beim erneuten Bootversuch von Suse feststellen, dass auch dies das Problem nicht gelöst hat. Der Bootvorgang bleibt immer noch an der gleichen Stelle hängen, also bei den hotplugging services. Wenn ich von Harddisk mit failsafe boote, bleibt er jetzt allerdings mit blinkendem Cursor stehen. Wenn ich normal boote, kommt er jetzt manchmal bis "done" (nicht immer) bei den hotplugging services, aber dann hängt er.

Was ist denn eigentlich an failsafe beim Knoppix-booten anders als failsafe bei Suse 9.0, dass das eine geht und das andere nicht - wenn es also nicht an usb liegt?

Hei Penguintux!
Ich habe es hingekriegt. Ich habe die hotplug-Datei so verändert, dass vor ALLEN Kommandos Kommentarzeichen stehen. Damit dürfte wohl die Datei komplett deaktiviert sein. Danach klappte das Booten von Suse 9.0.
Alles läuft zwar immer noch nicht (Probleme mit serieller Maus), aber jetzt kann man wenigsten was machen...
Vielen Dank für die Hilfe und beste Grüsse

Sputnik