![](https://seccdn.libravatar.org/avatar/6d198f8c8f1c94ccef873cebcf4f5dfa.jpg?s=120&d=mm&r=g)
The 2.6 modules are all .ko. SuSE 9.0 modutils has been modified to take care of that. Also 9.0 mkinitrd has been altered to strip off the .o or .ko, so it's able to cope with either. /sbin/generate-modprobe.conf /etc/modprobe.conf did not give me a workable modprobe.conf, I had to edit the one that is part of SuSE 9.0 aaa_base-9.0-6 to add a line for my ethernet card.... alias eth0 8193too and cut and paste the alsa stuff from /etc/modules.conf, then all was well.......... alias sound-slot-0 snd-ens1371 alias sound-service-0-0 snd-mixer-oss alias snd-card-0 snd-ens1371 alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-11 snd-mixer-oss alias sound-service-0-12 snd-pcm-oss Regards Sid. Donn aka n5xwb Washburn wrote:
Philipp Thomas wrote:
Alex Daniloff
[Fri, 14 Nov 2003 14:19:23 -0800]: As far as I concern, if SuSE didn't reflect ALSA changed labeling option in its /etc/modprobe.conf or modules.conf - it's a bug on SuSE's side.
Kernel 2.6.0 is clearly stated as being unsupported! That's why you can neither install nor configure it via YaST2.
The 2.6.0 on the CD/DVD is there for the playful who know what they're dealing with and can handle the problems. Those who can't shouldn't blame SUSE for what was never stated as being supported.
The next version of SUSE Linux will most probably support kernel 2.6.0. If it's *then* still not working, you would be right in calling it a bug.
Philipp
I did compile a www.kernel.org version of 2.6.# and founds that the modules were file.lo and required the latest version of modutils. I might guess the reason 2.6 fails is that depmod/modprobe does deal with file.lo the same as file.o
-- Sid Boyce .... Linux Only Shop.