SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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:
alias eth0 8139too
alias ehci_hcd ehci-hcd
alias sub-fs subfs
Oddly enough, I still need to probe them manually. I wasn't exactly sure on how to do this...but tried my best.
Last edited by RoaCh Of DisCor; 07-13-2005 at 11:56 PM.
## Path: System/Kernel
## Description: Modules to load after initial boot
## Type: string
## ServiceRestart: boot.loadmodules
# This variable contains the list of modules to be loaded
# once the main filesystem is active
MODULES_LOADED_ON_BOOT="8139too ehci-hcd subfs"
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.
Nope this is not a default config. Probably you have copied config of 220.127.116.11-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_BIG_ENDIAN is not set
# 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.
yes, I did. The above part of config is taken from 2.6.12.
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
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.