Thanks to those (Ben, Jonathan, Zentara) who answered my previous
query, re: not being able to boot after installing k_deflt.rpm.
Booting installed system via rescue disk, issuing 'depmod -a' and
'lilo', did the trick.
However, OSS would no longer work, nor would its sndshield module
recompile. So I downloaded the kernel sources for 2.2.16. Then I
realized that I'd best rebuild the kernel. Which I did, and
everything is working fine, in fact it seems to work better than
before. There *was* one big problem -- all root logins were disabled
when I rebooted. What could have been the cause of that? Anyhow,
I've fixed it.
The only problem now is that OSS still doesn't recompile sndshield. I have
wiped all trace of OSS from my system, removed the sound modules from
/usr.src.linux, downloaded a new OSS, and still I get the same
problem. The OSS documentation is rather petulant - "DON'T change the
.config file in /usr/src/linux! (except when we tell you to)" --
what's the point of building your own kernel, then? -- and their
online support merely repeats what is already unclear in their
documentation. Does anyone have any suggestions? Or should I try
ALSA? I know that OSS is SuSE's suggested solution, but I was never
very happy with the crackling and various other problems, which OSS
documentation always manages to blame on someone else's bad
programming. What is people's experience with ALSA?
Now, there is one thing I did not do, that OSS suggested I do:
that is, set CONFIG_MODVERSIONS=y
The reason is that this is warned against in several places, I didn't
have it enabled in 2.2.14, and I was also using the downloaded OSS
drivers with that kernel, not the ones that SuSE provides (only
because I didn't know they were there), yet OSS worked fine then and I
saw no reason why a clean install of OSS wouldn't work fine now. The
other reason is that I resent the bossy tone of their documentation.
One last question. At boot time I get the message,
devpts on /dev/pts type devpts (rw) failed
Now, the SuSE database says this is nothing to worry about if you're
not using USB devices, so I am not worried. I'm just curious why this
message never appeared with my 2.2.14 kernel as it shipped with 6.4.
Thanks again.
Corvin
--
Corvin Russell