Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Right, so I was never able to get my kernels to compile under Mandrake so I thought I'd try a different distribution (gentoo this time). Found a nice page at fearly.zapto.org/linux that said it was very simple and easy to get Toshiba 5100 laptops setup up. In anycase, the directions often times border on very vage, especially of course, the parts that I have questions on.
Well, in anycase, what I'm trying to do is patch Kernel 2.4.19 (either original kernel.org download or the gentoo-r10) but I can't find the acpi patch he's referring to
and the 2.4.19 patch that I get from memebeam.org (the actual toshiba_acpi.c's patches page that looks like what he's talking about) always gives me Hunk so and so failed!!! Can anybody instruct me on how to get it patched?
If you get hunks failed on a patching, try opening up the relevant .rej .c and .orig files and looked at the lines that failed. Often times you'll be able to see just where they were actually supposted to go in. If that is the case, then just throw the lines in where they should be, and the compile should work.
Thanks for the advise, but what if you can't tell by looking at the .rej files? I try comparing the Makefile.rej and Makefile as well as the Config.in.reg and Config.in but I cannot find similarities between them!
Oh, in the .rej file you should see a + or a - at the beginning of some of the lines, it should also list the lines that it thinks it should have gone into, which is a good place to start looking. Otherwise, you can just do a find on one of the lines it lists above or below which doesn't have a + or a - before it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.