I'm looking for 1 of 2 things:
A: Is there a way to identify what patches have been applied to a kernel's source tree?

B: Is there a place that list available kernel patches?

LinuxMint and KateOS both have patches that make my Laptop ACPI send events, but other kernels don' thave it... I'm trying to identify what patches have been applied to these kernels.

You can get everything you want at Alice's Restaurant. err, ahem, at kernel.org.

ok, so B is answered =D

Is there a way to identify what patches have been applied to say, Ubuntu kernel sources? or some way to identify the patches applied to a custom source tree. (Not the official source)

Normally the patchlevel is identified by the final digit in the kernel. E.g. for kernel 2.6.27 patch level 5 would 2.6.27.5. Of course, it's possible that someone has made some manual changes to the source and compiled that, but that would be nasty to find. If you can tell us what you're trying to find out, then maybe we can give you some better help. As it is, it's hard to tell what you're really looking for. Be specific.

With KateOS and LinuxMint Live CDs, all of my Toshiba's ACPI Events (AC, Lid, Power, etc...) function 100%. With the 'stock' kernel, I can only trap the Power event.

Laptop Model: TOSHIBA Satellite L305D-S5874
Newegg: http://www.newegg.com/Product/Produc...&nm_mc=OTC-RSS - I got mine directly from Toshiba though...

I know LinuxMint uses a patched linux kernel (with Ubuntu patches) but i don't know what patches... It's also an older kernel so my Wireless (ath5k) and Sound (Intel HD ...) won't work.

I've tried the Experimental ACPI patch on 2.6.27.4 (.5 came out a week later) and that wasn't successful to get my events...

So either Ubuntu's patches are more abundant than just ACPI or for ACPI to function on my laptop, i need to enable something else...

Linux Distro: Slackware 12.1 -- A number of other distros have the same problem as Slackware (no events other than the power button)

As to whether there are some special patches for the Ubuntu kernel, I'm skeptical. Mostly likely they just put their config on it, compile it, and ship it. Of course, I could be wrong, but I'd like to see someone say exactly how and where it's patches, rather than they're just sure it's got special patches "because".

But, if you know how to apply patches and recompile your kernel, then you're probably ready for the real thing. Abandon all caution , download 2.6.27.5 from kernel.org, and compile it from scratch with the options you want. To download the whole thing, just hit the letter "F" after the kernel on the main page. It's a bz2 file.

It's unlikely to be patches against the kernel - but certainly could be. I suspect it will be too hard to find unless commented well; you can pull the Ubuntu (patched) source from their git repo and scan that if you like. See this article.
I might be inclined to look for external indicators - grep /etc for "tosh", check the config in /boot, eyeball lsmod for any likely suspects ...

syg00, thanks for the correction. I never would have believe it.

They do, in fact they have a menu in 'make menuconfig' under drivers called Ubuntu drivers -- one of which is -toshiba acpi- which still won't load on my box and I can't make it build IF anything in that area is selected.

Yup, been doing this for about 3 weeks now... I think maybe something else is required beyond ACPI to make it work... like today i noticed HPET has ACPI messages in dmesg...

I went so far as to copy the kernel and initrd from the Live CDs and they worked on my slackware os... After i tweaked the kernel a bit i didn't even have to use the initrd - just the kernel... again though, this kernel was out of date so no wireless and no sound =( but ACPI events worked =)

I'll check the URL and see how that goes! thanks!

btw... 'gutsy: git://kernel.ubuntu.com/ubuntu/ubuntu-gutsy.git' is the kernel that my ACPI components work in... (It's Linux Mint 4.0 Mini - uses the gutsy kernel from ubuntu)

Wow, that link has some info... I may try that kernel to see if it works... I'd still like to know what patches are applied for sanity sake... I even rebuilt my own ACPI DSDT file and cleaned up errors in it. (didn't help either)

Thanks for the information! My search still isn't over - probably won't be for a while, but i now have new leads =D

Well, this restores some faith in my judgment. Adding a package, I can easily see, but patching things without the patches going into the kernel tree, I can't. The numbers get out of hand after only a few patches and a few new kernels from Ubuntu.

There is one thing i have not done yet that may help...

* Get the ubuntu kernel source that has patches (or extra drivers)
* Get the official kernel source for the same version
* do a big - diff (file level first for sanity)

And

I haven't tried the official kernel for that revision (again, no wireless or sound support so why would i?) -- but i need to verify the official kernel doesn't support my ACPI for that rev as well...

(versions below are going to be wrong as i don't remember off the top of my head, but it's similar to them)
I think ubuntu uses 2.6.19... Slackware came with 2.6.22.7 (i think - ther version is different) -- So I'll try this too.

As Micah says, the right way is to download the kernel for Ubuntu (or whatever), then the vanilla kernel for the same version, then diff them.

I doubt that's going to be of use for the OP though.

The other way is to dive in the web of the distributor, and look for the info. Most distros do ship their kernel patches separately, or at least give some indications in one or another place about their kernel patching policy. If not, you can always ask on their mailing lists, forums, etc etc.

heh - i think micah is the op =D

I've already been on the LinuxMint's forums to find out the use the ubuntu kernel w/ ubuntu patches... I'll be doing more of this as well after I can get back to where i can do a diff =D

(I blasted the box and started over yesterday - just got my wireless back as i went to bed last night)

Thanks for the information! When i have more details I'll post back in case any other toshiba owners have the same problem.

Someone forgot to take his coffee this morning hehehehe Sorry about the confussion