modprobe.conf -- not working.
 

Ok, so I upgraded to a new kernel *compiled it myself*. Afterward, I noticed my network card, usb harddrive, and subfs were all not working. No problem..if I probe them by hand, all is fine. However, I want them to start at boot. I added this to my modprobe.conf:

Oddly enough, I still need to probe them manually. I wasn't exactly sure on how to do this...but tried my best.

Suggestions?

-RoaCh :)

Try a different approach:

add those modules to /etc/sysconfig/kernel

I don't think Suse 9.3 rely's particulary upon aliases in modprobe.conf for network interfaces anymore.

Have a look in /etc/sysconfig/hardware

cat each of the hwcfg-bus-pci files to see if any of them contain something like

MODULE='8139too'
MODULE_OPTIONS=''
STARTMODE='auto'

You should be able to get the last part of bus pci for eth0 when it's runing by doing

getcfg eth0

and looking at the line like this (from mine)

HWD_DEVICEPATH=/sys/devices/pci0000:00/0000:00:0a.0/0000:02:01.0;

so on my system it's the file:

/etc/sysconfig/hardware/hwcfg-bus-pci-0000:02:01.0

Did you compile submount?
This is not a part of vanilla kernel, so I don't know what are you expecting? Sort of miracle? In your previous tread I have explained that you need to compile submount separately.

EHCI is compiled in the kernel, not as a module by default. Have you changed it? Also Realtek is compiled into kernel. 2.6.12 (at least on SuSE) will have problems with NICs compiled as a modules, so if you have changed it you may need to recompile kernel with build-in NIC, and EHCI. As I explained before submount is not a part of the kernel.

In the standard kernel of 9.3, both ehci-hcd and the realtek drivers are compiled as modules in the default configuration.
Since he told us that the manual loading of the drivers works, one must assume that the modules are present.
So he may has taken your advice.

He kompiled 2.6.12 (read his previous tread). This is not SuSE kernel this is vanilla. So your examples are rather useless. I know how default SuSE kernel is configured.

In 2.6.12 SuSE has problems with NIC kompilad as modules (and this is not the case for 2.6.11.x)

Read my post, I quoted the default config of 2.6.12 for the ehci module.

BTW: did I mention that I really don't like your style?

Nope this is not a default config. Probably you have copied config of 2.6.11.4-20a-default to the new kernel and started from there.

That is not a default config of 2.6.12

default (not edited) portion of 2.6.12 config looks different:
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y <-
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set

and default Realtek looks like this:
CONFIG_8139CP=y <-
CONFIG_8139TOO=y <-
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set


In other words your "default" kernel is not really default.
loading all the crap from default SuSE kernel really makes no sense.

I can tell you what I did:

download and unpack linux-2.6.12.tar.gz from kernel.org
make config
answer all questions with the default setting.

The result is shown above.

EDIT: Maybe we should open another thread for this type of discussion. I feel a little bad about hijacking another thread.

yes, I did. The above part of config is taken from 2.6.12.

however command
#make config
will not show default options. It only allow to select one of tree (N/m/y) choices. so what defaults you see there? If I run
make config
and save it without any changes I still get
EHCI in the kenel, not module, same goes with Realtek. So whatever you do it is not default.

...so we have to think about what 'make config' does. Two people seem to do the same thing and get different results. I simply be as ignorant as you are and ignore that you claim I must have done something wrong. I end this discussion (hey, chance of last word again!), because this has nothing to do with the original thread.

Thanks for all the suggestions. Sadly my nvidia drivers didn't work with the newest kernel yet anyway...so I reinstalled SuSE's latest stable kernel with yast. All is well now. I'll try again, once the nvidia driver's can be built with a 2.6.12 kernel.