
You have a really creepy avatar.je_fro wrote:WPA is working fine with the new madwifi-ng build.
Now all that's left is to solve these ridiculous heat and power consumption issues...
I think the only way to solve this issue is to convince AMD/ATI to fix their crappy drivers. POWERplay is working on MBPv1, why not on MBPv2 ?je_fro wrote:Now all that's left is to solve these ridiculous heat and power consumption issues...
Code: Select all
# Module autoloading
# Autoload modules that lack aliases but have them defined inutoload modules
ENV{MODALIAS}=="?*", ACTION=="add", RUN+="modprobe.sh $env{MODALIAS}"Same here.miga wrote:When I boot udev tries 3 times to load the uvcvideo module (in the init process).
Maybe this is due to the new behaviour of pommed ? You have to "switch on" keyboard backlight using F8, then you can adjust the blacklight level with F9 and F10. Before, you just had to press F10 to enable backlight.john-boro wrote:I've just installed 2.6.21.1 and the keyboard backlight is no longer working. Pommed reports no errors, no does the applesmc tool. Anyone else had this?
It is most probably related with CFS. Please see with Ingo Molnar on the Linux Kernel ML. I can't give you any advice excepted that you should not use if it cause problems. Please note that I have enabled it here since v8, and I did not notice any problem (but I can't see a significant improvement either).je_fro wrote:Well, that new kernel (v2.6.21.1-mactel-r2 with the AHCI and CFS patches) is a dud... Using it my system seemed a little slower and became unresponsive when mounting CIFS shares....I couldn't unmount them, but then again I couldn't tell if they were mounted either...odd.
For example... /home/me/mountpoint is where I'd mount a remote CIFS share. Using bash tab completion I can just do cd mo<tab> and the name "mountpoint/" autocompletes. Not now. "mount mountpoint/" (it's in fstab so this works) seems to work but "ls mountpoint/" hangs that bash shell. So does "cd mountpoint/" or anything else...
I'll try searching and see if it's a problem with CFS or AHCI....I don't know what the culprit is...
Code: Select all
WITH AHCI
# hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 5630 MB in 2.00 seconds = 2820.61 MB/sec
Timing buffered disk reads: 116 MB in 3.04 seconds = 38.11 MB/sec
WITHOUT AHCI
# hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 6562 MB in 2.00 seconds = 3288.07 MB/sec
Timing buffered disk reads: 100 MB in 3.03 seconds = 32.95 MB/sec
The GPU is still what drains the most power on the MBPv2. Even with all the open source drivers fixed, don't hope for more than 2 hour of battery life.je_fro wrote:That's great news about the powersaving...I have to use OSX most of the time because of the heat and the battery usage under linux.
Yes, I forgot to report about it earlier, but I gain about 8-9MB/sec with AHCI. However the hard drive I'm using is not the standard one in the MBPv2. It is a SAMSUNG HM160JI (160GB), which is a bit faster.je_fro wrote: Also, the AHCI driver seems to be an improvement:Code: Select all
WITH AHCI # hdparm -tT /dev/sda /dev/sda: Timing cached reads: 5630 MB in 2.00 seconds = 2820.61 MB/sec Timing buffered disk reads: 116 MB in 3.04 seconds = 38.11 MB/sec WITHOUT AHCI # hdparm -tT /dev/sda /dev/sda: Timing cached reads: 6562 MB in 2.00 seconds = 3288.07 MB/sec Timing buffered disk reads: 100 MB in 3.03 seconds = 32.95 MB/sec
Code: Select all
# hdparm -tT /dev/sda
/dev/sda:
Timing cached reads: 5370 MB in 2.00 seconds = 2690.24 MB/sec
Timing buffered disk reads: 128 MB in 3.02 seconds = 42.42 MB/sec
HaHaHa....I'm so fscking 1337 that I _DO_ run beryl on my MBP, but I do so using the xeffects overlay. I also have Sync to VBlank checked and haven't noticed anything odd. Perhaps you should give xeffects a try?john-boro wrote:I know most of us who are l33t enough to install gentoo on an mbp probably don't care about beryl, but I think it's..well.. nice.
Yes this is a commun issue with this patch. see http://lkml.org/lkml/2007/5/15/259je_fro wrote:Pic0's mactel-sources has a "powersaving" USE flag that enabled a patch altering the touchpad code. With USE="powersaving" my mouse cursor would be real "wiggly" and the buttons wouldn't function properly after an X restart. Disabling that USE flag fixed the issue. It didn't appear to have any noticeable effect of battery life either.