It is bad enough that the kernel gods have basically required that the whole kernel source tree be installed and configured to compile even a simple module but they have made it so a module compiled on one kernel will not work on any other.
To make the situation worse much of the configuration needed to successfully compile a module has been left out of open suse11.3.
If you want to replicate the problems may I suggest you attempt to compile the usb-skeleton.c driver example code that is included with each kernel.
If it is the intent of the linux community to limit driver development to the professionals then congratulations… your doing a great job
I don’t know specifically about usb-skeleton.c specifically but I do know that in general custom compiling to support most USB devices is being deprecated in favor of udev.
Besides udev (where I’d guess your real solution problem exists), I’d also recommend a quick look at LKM (Loadable Kernel Modules), those are generally pre-compiled modules which are appended to the base kernel image during bootup. Udev modules are generally accessible and can be invoked during runtime.
This isn’t just openSUSE, most Linux distros which are quickly adopting new kernel architecture to enhance device support, configuration and various options are doing this.
Hello BrianLarsen and sorry to hear you are so grumpy on your very first post. While I do not claim to be an expert on such things, I found an interesting article on the subject here you might read.
As always, to make sure you have all of the required tools installed, I suggest you open up YaST / Software / Software Management and then select the View Button on the top left and pick Patterns. In the resulting Pattern tree, make sure you have Base, C++ & Kernel Development selected and if not then do so and allow these packages to install. Finally, if you decide you need the entire kernel source file installed check out my bash script file called sakc and its companion script called klist:
Also forgot to mention, if you’re looking for improved device support you might also consider enabling Tumbleweed.
If you’re upgrading to 11.4 (official launch in 2 weeks as of this writing) it’s integrated.
If you’re running 11.3 and won’t be upgrading right away, you should see it as a repository to be added in YAST.
Tumbleweed will enable rolling upgrades which means as and when a package or component becomes “Tumbleweed enabled” you’ll get the bleeding edge <stable> version… Essentially meaning best and latest without sacrificing stability and your current apps.
As of today, if you are Tumbleweed enabled you should be getting kernel 2.6.37.1 which is far advanced than the standard kernel for 11.3 (2.6.7.xxx). Enabling and running the latest kernel ensures access and integration with the lastest and more device drivers, memory management and lots more.
i’d suggest you return your Linux to its maker and ask for your money
back.
and, go somewhere else to bellyache.
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
Just a reminder we are a support forum of enthusiasts and volunteers … We are not a packaging nor a development forum.
If one wishes to reach the packagers or developers of openSUSE then the place(s) to do so are clearly marked in the Communications channel wiki for openSUSE - where the places are the mailing list, and the IRC freenode chat channels such as #opensuse-factory. The openSUSE forums is not the place.
If one wishes to recommend an improvement to openSUSE, then the place to do so is openSUSE fate. The openSUSE forums is not the place.
For the OP, in case you did not know (and it definitely appears that way) the openSUSE forum is to provide support for problems, it is not the place for such observations if you wish to accomplish anything useful. If you wish help on a specific area, please post, and many volunteers who are NOT paid, will likely bend over to help.
I also remind everyone of the forum rules wrt being civil.
Suse 11.3 is suppose to be stable and nearly bug free. Stupid problems with the confugurations should have been weeded out a long time ago. UNACCEPTABLE in a .3 release. Big changes like this should have been push into the 12.0 version.
Compiling the usb-skeleton should be relatively easy and straight forward in any stable kernel. Im surprised no one tried it out before the release and corrected the problems.
I am quite aware of udev - I was planning to rewrite an unmaintained driver to move it passed all its obsolete code. At this point I suspect it will be useless to do so until some stability is restored to the kernel driver system.
Denver, I have been around a long time - take your troll arsed bull to a different thread.
On 02/27/2011 10:36 PM, BrianLarsen wrote:
> Denver, I have been around a long time - take your troll arsed bull to
> a different thread.
as oldcpu said, you need to talk to the devs, and they are not
here…if you had been around a long time you would have known that.
i’m not leaving and i’m not helping you–first time posting with bitch
from top to bottom…what is your claim to fame?
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11
Hi
Not sure but I always build KMP’s via rpm, doesn’t take long as it’s a
pretty standard template. Build locally or use the openSUSE Build
Service especially useful when using the update repo and a newer kernel
is release…auto build.
The other advantage is not only building different archs, but also the
other flavors eg Xen, pae etc and debuginfo.
The other change is that it gets put into the update area of the kernel
tree, then if the kernel gets updated it automatically gets move to the
weak updates and will keep working…
or, if you think it would be a nice feature to include a full
development package in the default install, so you don’t run into “the
configuration needed to successfully compile a module has been left
out of open suse11.3 [sic]” you may suggest that in FATE: https://features.opensuse.org/
and if you come back here try not to be so grumpy with the volunteer
helpers, ok?
–
DenverD
CAVEAT: http://is.gd/bpoMD
[NNTP posted w/openSUSE 11.3, KDE4.5.5, Thunderbird3.0.11, nVidia
173.14.28 3D, Athlon 64 3000+]
“It is far easier to read, understand and follow the instructions than
to undo the problems caused by not.” DD 23 Jan 11