[cooker-amd64] Re: Re: Re: Re: using and compiling rpms not specifically put together for amd64

[Duncan]

Arie Folger posted <200401290831.41045.afolger@aishdas.org>, excerpted
below,  on Thu, 29 Jan 2004 08:31:41 +0100:

>> FWIW, I'm having issues with sound as well, on the 2.6 kernel, tho 2.4 has
>> usable sound.  Thus, I have my own sound issues to work on, same i810
>> based sound.
> 
> I noticed in another post of yours. That is one reason why I'd wait with 2.6 
> until that is fully worked out, as one function of my amd64 is to work on 
> recordings (audio only and audio+video) of lectures I am giving (not computer 
> related). No sound=no proper use in this line of work.

I'm making steady progress on that..  I had unpacked both the tmb and the
regular 2.6.2-rc1 Mdk kernels, and at the time of my initial post, had
only done initial configuration, enough to compile and see that it would
actually run, on one.  I fine tuned the configuration on both, and ran
diff on the .config files to compare them, as well as to pull my attention
to anything I'd configured wrong in one or the other by the differences. 
Doing that and figuring out in more detail what each option I was unsure
about meant, took me over a day of hard work, plus with some other
detours, additional research, and tracing down a Mdk installkernel script
bug (which I need to file still), that was over two days, to get both
kernels comparably compiled.

Anyway, I'm now working on some of the stuff that didn't work.  I don't
think I mentioned my bind/named wasn't working (my system was using my
configured backup name servers as resolvers), but I traced that to having
built the Linux security capability module as a module, rather than
built-into the kernel, and having to manually load it.  (I put it in
modules.preload, for now, to automate that.  Since I only did it to get
keep the initial kernel size down, and I don't believe module was even an
option in 2.4, having it preload isn't a big issue.)  At first, I thought
it was because I'd not compiled the cryptography stuff in, as named uses
that to communicate with its controller, but that wasn't it, named and the
controller use their own userspace implementation, at least for now. 
However, that complicated finding the real problem.  It was a leap of
intuitive insight, more than anything else, that finally led me to the
problem.  One of those "I wonder if.." things..  <g>

I got sound (mostly) working now, too.  There were apparently two problems
there.  The one was some sort of incompatibility between my older ALSA I
had installed, and the new one.  Every time I boot between a 2.4 kernel
and a 2.6 kernel, either direction, I get a warning about a bad settings
file and all my sound goes zero and muted again.  It's that warning that
had me thinking it was a serious kernel issue.  However, it doesn't seem
to be quite THAT serious.  I switched ARTS back on under KDE (I'd had it
off due to instability under 2.4, but decided to try it again under 2.6,
on a hunch..)  The other thing is that while ARTS seemed unstable and
partly wouldn't work under 2.4, xmms won't work at all under 2.6, with ANY
output, ANY input, that I've tried.  (I tried wav and mp3 in, alsa, arts,
even diskwriter, out.  It starts to load the song, filling some sort of a
buffer, then stops, as soon as the buffer is full.)  As well, aplayer
doesn't seem to work under 2.6.. but ARTS does!?!

Anyway.. I got SOME sound, now.  I'll have to reinstall the rest of the
KDE audio stuff and see if I can play it for long periods, but it at least
works to SOME degree, now.

I haven't figured out mouse scrolling, just yet, but have an idea to try
on it, and as mentioned, I came across another non-kernel, but kernel
install scripts, bug to report.

Anyway, I've had some extra time off this week, and have been putting it
to good use... working, eating, sleeping, and dreaming (yes, literally),
kernel and related stuff.  <g>

-- 
Duncan - List replies preferred.   No HTML msgs.
"They that can give up essential liberty to obtain a little
temporary safety, deserve neither liberty nor safety." --
Benjamin Franklin