On Mon, Jan 26, 2009 at 10:51:47AM +0100, Cassiel wrote:
Just a question, what's the need in running
2.6.27? is it for wireless usage
only, ie. the rt2860sta module?
atl1e module IS in 2.6.26 and rt-13 patch works very well with this kernel
release though there is no rt2860sta module, but if the "or" logical
statement is valid.. :-)
I think I may have found an answer. I do indeed need the rt2860sta driver which is
different than the rt2860 driver. I also need the atl1e driver which is different from the
atl1 driver.
However, it seems that the good Debian-EEE maintainers didn't weave those into their
kernel tree, but instead made the source to the patches available as separate packages.
So, installing the rt2860-source and atl1e-source packages, then doing the m-a prepare and
m-a a-i dance should, if the patches apply cleanly to an Ingo kernel, get me the drivers I
need to get this thing running.
2009/1/26 Ken Restivo <ken(a)restivo.org>
> And here is the next installment in the saga of trying to get Ingo RT going
> on my Asus EEE.
>
> I successfully built and ran the 2.6.26.8-rt12 with the alsa_seq patch. It
> ran.
>
> The problem is that neither the Ethernet (atl1e) or wireless (rt2860sta)
> work. So I pretty much had to reboot back out of it immediately.
>
> It appears that the atl1e driver I need to get my Ethernet working, is not
> supported AT ALL in 2.6.26. The Debian Lenny kernel 2.6.26 has some kind of
> backport of all kinds of stuff from 2.6.27, including the atl1e I need.
>
> I could try to reverse-engineer whatever it is that the Debian maintaners
> have done to get atl1e backported (it seems they've had to fix some bugs in
> the backported driver too), or, I could just try with 2.6.27 or higher and
> thus have the hardware support I need to make my netbook usable.
>
> Only problem is, it doesn't look like there is any such thing as a 2.6.27
> Ingo RT patch yet. His stuff stops at 2.6.26.
>
> So now what? Any idea as to when there might be a nice stable RT kernel
> cocktail of the 2.6.27 or higher variety? Or am I going to have to try to
> figure out what portions of the Debian Lenny patches I have to apply to my
> Ingo-patched 2.6.26.8 kernel, and then try to get them to apply cleanly?
>