Posts by BenKurtz

I confirmed my theory. The ATI drivers work fine, with no patching, for 2.6.0-test7. Same drivers produce the aforementioned problem (VMALLOC, etc) for test8 and test9. Essentially, test8 broke it. I'm going back to test7...

The IMALLOC_VMADDR is probably a result of shifting locations or nomenclature for some define in a header file somewhere. As the kernel evolves, these things move around constantly. This is the number one reason for breakage in kernel...

Ok. Once more. I don't use emerge for kernel source or for kernel driver source. Nothing is happening "magically" which I am not aware of. I did not 'emerge ati-driver' or whatever, I downloaded the source and compiled...

I am using the gentoo distribution, but I'm using an unpatched test7 kernel from kernel.org. I had zero problems getting the ATI linux drivers to go on my M10 9600... I'm wondering how many people are having problems like yours,...

Well... ATI may not be able to code (granted, I've known some people who work there). On the other hand, Tungsten Graphics rocks, and they end up doing a lot of the linux radeon fb schtuff. I'm not clear on how your 'fix' is...

It is USB of some sort. It shows up in lsusb just like any other USB device. However, usbnet doesn't work on it and I can't get the Atmel drivers to compile. Do you have this working? P.S. The distro is gentoo 1.4. Good stuff,...

After a couple days of trials and tribulations, I've got the 2.6.0-test7 kernel up on the 8890. Everything works, except the internal wireless LAN card! UPDATE: Now even the wlan works! What you need to know: 1) The built-in RAID...

Go ahead and partition your drive with no swap. Worst case scenario, you can create a file (say 200mb or so) with dd, format it as swap, mount it through the loopback device, and swap on that file. This is actually a common method...