Macbook Pro

Message

stardotstar · Post by **stardotstar** » Thu Aug 10, 2006 9:50 am

I think there may be better ways to share your stuff - although I have not got to that yet I believe that read write HFS with journaling turned off is a way of using a volume (one of the free partitions if you don't want to triple boot) between Linux and OSX. I have sort of done it more round about - OSX and XP are my minor os's so I used FAT32 for Windows and now I can see that volume from both Linux and OSX etc etc

stardotstar · Post by **stardotstar** » Thu Aug 10, 2006 11:01 am

I am finding this much harder than I expected.

Although I have got a running system and think I have compiled the kernel correctly it won't load *any* modules.

The config I used is the MBP kernel config from mactel-linux based on the 2.6.17 gentoo sources kernel and the patches from mactel-linux.

The patches applied cleanly and the kernel built without error including (I thought) my modules (soooo many!)

So I booted the kernel - although it loaded none of the modules loaded - they were all not found as such...

I thought maybe I had failed to make clean and rebuilt the kernel and did a fresh make && make modules_install copying the new kernel over the last and rebooting. Same thing.

If I try and modprobe anything from:

Code: Select all

localhost ~ # modprobe bluetoth.ko
FATAL: Module bluetoth.ko not found.

This happens with all the modules - and I had made the list up in the 2.6 branch kernel modules.autoload.

Nonetheless the system is running, I am posting from Gnome 2.14 on modular x using the wired lan and the wireless usb/mouse works, the touchpad works - but only as one button mode. The resolution I think is stretched 1024x768 at 74 hz.

I tried to use the xorg.conf from mactel-linux but the server bombs because of missing modules associated with the ati prop drivers - which I tried to emerge but when the auto insert is called it fails and the emerge drivers fails...

Sort of stuck - will continue to hack away but would certainly appreciate some help from those of you who have gone before.

Will

BTW my clock is sorted since most recent update world.

jettjunker · Post by **jettjunker** » Fri Aug 11, 2006 3:10 am

stardotstar wrote:I think there may be better ways to share your stuff - although I have not got to that yet I believe that read write HFS with journaling turned off is a way of using a volume (one of the free partitions if you don't want to triple boot) between Linux and OSX. I have sort of done it more round about - OSX and XP are my minor os's so I used FAT32 for Windows and now I can see that volume from both Linux and OSX etc etc

"ect ect"? Do you mean that both Linux and OSX read/write on fat32 without headache?

Myself, I plan on running Gentoo primarily, and only going to OSX or XP for the odd program... but if I could put my media on the XP partition and have read/write all around that sure seems like the thing to do.

dmvianna · Post by **dmvianna** » Fri Aug 11, 2006 3:28 am

jettjunker wrote:"ect ect"? Do you mean that both Linux and OSX read/write on fat32 without headache?

That's correct. At this time, Linux can even read/write on NTFS, but not OSX. It's just that most people would like to preserve file permissions which are absent on fat32, so they would usually rather have HFS+ than fat32.

jettjunker · Post by **jettjunker** » Fri Aug 11, 2006 5:07 am

Great, thanks for your help guys. I just placed my order for a 13" macbook, with upgraded mem to a gig, and HDD to 80. I'll probably be back in this thread next week when I run into trouble... heh

Oh I hope their delivery is quick.

stardotstar · Post by **stardotstar** » Sat Aug 12, 2006 8:52 am

I can say that the latest ATI binary installer works fine for getting the resoltion sorted on the MBP17.

I am having to do some kernel rebuilding to get to the gl side of things but:

8.27.10

is working reporting:

MOBILITY RADEON X1600 (M56 71C5)
256 MByte

I just ran the installer and next next next... Then aticonfig --initial to update the xorg.conf (as root)

got 1680x1050 straight away.

https://support.ati.com/ics/support/def ... olderID=27
https://a248.e.akamai.net/f/674/9206/0/ ... .24.8.html

I am building a 2.6.17.8 kernel.org kernel now with the patches from mactel-linux and hopefully I can get accelerated gl happening real soon.

Currently emerging full gnome and then onto wireless, sound and power management.

A couple of questions at this point:

Is everyone getting burnt above the Fn keys

??
I am not yet using synaptics in my xorg.conf and although the touchpad is working pretty well it has a tendency to behave as though another finger (knuckle touch) is interfearing sometimes and the pointer pulses left and right... Because I have appletouch patched etc I suspect it is a synaptics/X configuration thing...

Wow these Core Duos compile *fast* I have never got through so many emerges so easily

Will

smitdane · Post by **smitdane** » Sun Aug 13, 2006 8:19 pm

I have the touchpad working wondefuly with synaptics. This includes the two-finger right click. You have to unload the usbhid module and modprobe appletouch, and re modprobe usbhid. I put it all in the rc.local script. Then you can configure it normally with synapics.

stardotstar · Post by **stardotstar** » Sun Aug 13, 2006 10:47 pm

Thanks smitdane - I had read that in the wiki but I am having trouble getting the synaptics integrated - not done it before - I will persist and eventually previal. I can't wait to have the touchpad working properly - single button is a major headache.

I'm still getting the occasional IO-APIC panics on boot and looking into that now. I have read about them earlier in this thread.

I have also managed to get the duo cores showing in the CPU Freq monitor in Gnome but only CPU0 takes governor settings and displays the scaling... I have read that this could mean that CPU1 is following suit but the graph shows 2.16G solid all the time and ignores governor setting. Is this right - I can understand if they cannot be governed independently since the software apparently ends up choosing the faster anyway but it would be useful to be able to see what is happening across the die.

Will

tsm23 · Post by **tsm23** » Mon Aug 14, 2006 12:28 am

Hi,

I posted a while back about getting sound working on the Macbook Pro. My problem was that even though alsa loaded properly I could only get digital audio ouput (no internal speaker or analog headphone sound). I just updated from 2.6.16-gentoo-r9 to 2.6.17-gentoo-r4 (using my old configuration and no patches) and can now get analog audio output from the headphone jack (though not the speakers). However, even when I set the alsamixer controls at maximum volume, I can barely hear the sound. Does anyone know what might be reducing the volume?

Thanks

stardotstar · Post by **stardotstar** » Mon Aug 14, 2006 1:11 am

Can't help specifically tsm but I have the symptom that sound works on the speakers after unmuting the headphone channel.

I have not got enough working properly to investigate further - ie cd is still awol so I can't play cds etc.

BTW I have the MBP17

stardotstar · Post by **stardotstar** » Mon Aug 14, 2006 2:39 am

WRT the accelerated ATI problem I was having - it was to do with the fact that the

General setup --->
() Local version - append to kernel release (Currently, ati-drivers won't fully compile if you append anything to your version)

Loadable Module Support --->
[*] Enable loadable module support

and

Unable to modprobe fglrx

If the module cannot be loaded ("operation not permitted"), check if the kernel Direct Rendering Manager (Device Drivers -> Character devices -> Direct Rendering Manager) is enabled. If so: Disable and recompile

Local version was checked below that - to auto append kernel release in the MBP config I was working from. Not sure if it was the DRM module but I removed that anyway.

I am getting consistent 241FPS +/- .5fps
with glxgears.

tsm23 · Post by **tsm23** » Mon Aug 14, 2006 3:18 am

Here's an update on my issue with the audio drivers (see two posts back):

As recommended at http://www.mactel-linux.org/wiki/Kernel ... uide#Sound, I downloaded the patch at http://www.madingley.org/macmini/kernel ... udio.patch. It's intended for the vanilla sources kernel 2.6.16.1, but I was able to apply it to 2.6.17-gentoo-r4 with only one problem (which I fixed by manually inserting a line). After recompiling, I now have analog audio output from the headphone jack at normal volume, but I also have sound coming out of the speakers and I can't turn off one without turning off the other. In the alsamixer panel, there's a single channel labeled "headphone" which controls the volume for both...

stardotstar · Post by **stardotstar** » Mon Aug 14, 2006 3:28 am

smitdane wrote:I have the touchpad working wondefuly with synaptics. This includes the two-finger right click. You have to unload the usbhid module and modprobe appletouch, and re modprobe usbhid. I put it all in the rc.local script. Then you can configure it normally with synapics.

When I rmmod usbhid I lose the keyboard completely

so I had to put all those commands into a single line.

rmmod usbhid appleir appletouch && modprobe appletouch && modprobe appleir && modprobe usbhid pb_fnmode=2

This seems to have worked in that the mouse and keyboard are working but I will need to look further into synaptics installation to get the rest working.

UPDATE:

Synaptics working but mouse movement is not quite ideal. I have two and three finger button simulation and the speed and general touchpad geometry seem OK - can anyone share their settings too?

Code: Select all

stardotstar@localhost ~ $ synclient -l
Parameter settings:
    LeftEdge             = 17
    RightEdge            = 1206
    TopEdge              = 12
    BottomEdge           = 350
    FingerLow            = 53
    FingerHigh           = 58
    MaxTapTime           = 180
    MaxTapMove           = 220
    MaxDoubleTapTime     = 180
    ClickTime            = 100
    FastTaps             = 0
    EmulateMidButtonTime = 75
    VertScrollDelta      = 100
    HorizScrollDelta     = 100
    MinSpeed             = 0.05
    MaxSpeed             = 1
    AccelFactor          = 0.8
    EdgeMotionMinZ       = 30
    EdgeMotionMaxZ       = 160
    EdgeMotionMinSpeed   = 1
    EdgeMotionMaxSpeed   = 400
    EdgeMotionUseAlways  = 0
    UpDownScrolling      = 1
    LeftRightScrolling   = 1
    UpDownRepeat         = 1
    LeftRightRepeat      = 1
    ScrollButtonRepeat   = 100
    TouchpadOff          = 0
    GuestMouseOff        = 0
    LockedDrags          = 0
    RTCornerButton       = 2
    RBCornerButton       = 3
    LTCornerButton       = 0
    LBCornerButton       = 0
    TapButton1           = 1
    TapButton2           = 2
    TapButton3           = 3
    CircularScrolling    = 0
    CircScrollDelta      = 0.01
    CircScrollTrigger    = 0
    CircularPad          = 0
    PalmDetect           = 1
    PalmMinWidth         = 10
    PalmMinZ             = 200
    CoastingSpeed        = 0

I am finding the vertical travel a little more limited than the horizontal (which feels wierd because it is a wide screen and traversing the left to right can be done in a single stroke and top to bottom can require two or three travelling strokes...) the tapping is probably a matter of finetuning and getting used to it but on the whole I am happier than with the standard touchpad actions. Not as good as OS X though... The fine movement is very notchy and I would have to use a mouse for working in the Gimp I am thinking. Nowhere near as good as the ThinkPad... Any ideas?
Will

stardotstar · Post by **stardotstar** » Tue Aug 15, 2006 12:09 pm

I think many of you are well advanced in getting this hardware sorted and I feel quite self conscious making posting avalanches in this topic which I feel should have more *meat* to it rather than ponderings of those of us struggling with some pretty basic Linux problems complicated only by the fact that we can't tell if it is to do with unfamiliarity with the hardware (ourselves and in general community) or just something Gentoo/Linux we know not yet!

So I have been reading very widely and begun to set my links and ponderings (simplistic and crude as they may be) in a simple phpBB forum where I invite anyone interested in this platform/genus of the intel architecture to discuss their woes, trials, tribulations and triumphs.

This is *not* a Gentoo forum - I want it to be distro agnostic - I want it to promote the resources on the web that already support the Mactel platform and act as a discussion/link resource for Threads, Wiki Resources and other online material that is of use to those of us struggling to come to terms with this new machine.

I do not want to draw traffic or content away from this thread or forum, and I don't pretend to have any specific answers - I just want to provide a place where there is the opportunity fully ou discuss our progress at all levels.

If the moderators here are ok with my invitation to you to come to a mactel specific forum for a friendly chat please come by and register, the server is reliable and won;t dissapear - I run it and other forums on it and have done permanently for over three years.

Best regards,

Will

http://www.sourcepoint.com.au/macintoo/forum

tsm23 · Post by **tsm23** » Fri Aug 18, 2006 6:10 am

Hi stardostar,

I still haven't had any luck with the audio, but I wanted to comment on your problems with the ati drivers. Though I thought my direct rendering was working using the standard "emerge ati-drivers" package (and glxinfo said I had direct rendering) the acceleration isn't anywhere near as fast as it ought to be. I know glxgears isn't a proper benchmark, but I've only been getting aroung 250 fps on my MacBook pro while my Gentoo desktop (which has a slower processor and older graphics card) gets several thousand fps. Looking around on the forums here, I saw that someone was reporting getting fps in the thousands on his MacBook pro. All this would suggest that for some reason, we aren't getting full acceleration (I saw that you reported about 241fps in glxgears). Do you have any ideas what the problem might be?

stardotstar · Post by **stardotstar** » Fri Aug 18, 2006 9:17 am

This is a spot on observation tsm. I too have noticed such high figure claims and only managed to produce figures like that by obscuring the window glxgears was running in.

When I enlarged it to full screen it was pittying. So I agree, other symptoms of non optimal video are the way the windows move - they are not smoothly rendered and drag and resize very poorly even though as you say the 3D drivers report ATI...

So... I am not sure the best way to proceed, I am trying to get frame buffer mode sorted right now and then power management - I have the machine on a laptop cooling platform which has made a huge difference in heat dissipation.

My next big gripe is the touchpad even with synaptics - I can't get the sensitivity that I get in OSX or what I had with my ThinkPad in Linux...

tsm23 · Post by **tsm23** » Sat Aug 19, 2006 11:40 pm

Since glxinfo claimed I had hardware acceleration, but my glxgears fps was only about 250, I tried upgrading to xorg 7.0-r1 and downgrading to the 8.24.8 version of the ati drivers (installed via an emerge). I now get a glxgears fps of around 4000, but when I try to run tuxracer or ut2004-demo or even just opening xine, the window manager freezes. Does anyone have any suggestions?

Thanks

dmvianna · Post by **dmvianna** » Sun Aug 20, 2006 12:08 am

tsm23:
Forgive me if I'm asking the obvious, but did glxinfo give you

Code: Select all

$ glxinfo | grep rendering
direct rendering: Yes

And what about

Code: Select all

$ cat /var/log/Xorg.0.log | grep fglrx

?

tsm23 · Post by **tsm23** » Sun Aug 20, 2006 7:14 am

Hi dmvianna,

Yes, I do have hardware rendering and glxgears runs as I would expect it to (about 4000 fps). As for the xorg log, greping for fglrx gives the following output:

Code: Select all

(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
(II) fglrx(0): pEnt->device->identifier=0x81f2a38
(II) fglrx(0): === [R200PreInit] === begin, [s]
(II) fglrx(0): PCI bus 1 card 0 func 0
(**) fglrx(0): Depth 24, (--) framebuffer bpp 32
(II) fglrx(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) fglrx(0): Default visual is TrueColor
(**) fglrx(0): Option "DesktopSetup" "0x00000100"
(**) fglrx(0): Option "MonitorLayout" "LVDS,CRT"
(**) fglrx(0): Option "UseInternalAGPGART" "yes"
(==) fglrx(0): RGB weight 888
(II) fglrx(0): Using 8 bits per RGB (8 bit DAC)
(==) fglrx(0): Gamma Correction for I is 0x06419064
(==) fglrx(0): Gamma Correction for II is 0x06419064
(==) fglrx(0): Buffer Tiling is ON
(II) fglrx(0): Primary V_BIOS segment is: 0xc000
(--) fglrx(0): Chipset: "MOBILITY RADEON X1600 (M56 71C5)" (Chipset = 0x71c5)
(--) fglrx(0): (PciSubVendor = 0x106b, PciSubDevice = 0x0080)
(--) fglrx(0): board vendor info: third party graphics adapter - NOT original ATI
(--) fglrx(0): Linear framebuffer (phys) at 0x80000000
(--) fglrx(0): MMIO registers at 0x98300000
(==) fglrx(0): ROM-BIOS at 0x000c0000
(II) fglrx(0): VESA BIOS detected
(II) fglrx(0): VESA VBE Version 3.0
(II) fglrx(0): VESA VBE Total Mem: 16384 kB
(II) fglrx(0): VESA VBE OEM: ATI ATOMBIOS
(II) fglrx(0): VESA VBE OEM Software Rev: 9.12
(II) fglrx(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc. 
(II) fglrx(0): VESA VBE OEM Product: M56P
(II) fglrx(0): VESA VBE OEM Product Rev: 01.00
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Loading /usr/lib/xorg/modules/linux/libfglrxdrm.so
(II) Module fglrxdrm: vendor="FireGL - ATI Technologies Inc."
(II) fglrx(0): ATI Video BIOS revision 9 or later detected
(--) fglrx(0): VideoRAM: 262144 kByte, Type: DDR3
(II) fglrx(0): PCIE card detected
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): MonitorLayout is no longer supported. 
(WW) fglrx(0): The hex number setting for DesktopSetup is deprecated,
(II) fglrx(0): Connected Display1: LCD on internal LVDS
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: APP  Model: 9c62  Serial#: 0
(II) fglrx(0): Year: 2006  Week: 15
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max H-Image Size [cm]: horiz.: 37  vert.: 23
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): No DPMS capabilities specified; RGB/Color Display
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.595 redY: 0.343   greenX: 0.319 greenY: 0.545
(II) fglrx(0): blueX: 0.154 blueY: 0.135   whiteX: 0.312 whiteY: 0.328
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported additional Video Mode:
(II) fglrx(0): clock: 119.0 MHz   Image Size:  367 x 230 mm
(II) fglrx(0): h_active: 1680  h_sync: 1728  h_sync_end 1760 h_blank_end 1840 h_border: 0
(II) fglrx(0): v_active: 1050  v_sync: 1053  v_sync_end 1059 v_blanking: 1080 v_border: 0
(II) fglrx(0):  LP171WE2-TLA1
(II) fglrx(0):  Color LCD
(II) fglrx(0): End of Display1 EDID data --------------------
(WW) fglrx(0): Specified desktop setup not supported: 8
(II) fglrx(0): Primary Controller - LCD on internal LVDS
(II) fglrx(0): Internal Desktop Setting: 0x00000004
(II) fglrx(0): POWERplay version 3.  4 power states available:
(II) fglrx(0):   1. 419/450MHz @ 60Hz [enable load balancing, performance mode]
(II) fglrx(0):   2. 128/135MHz @ 60Hz [low voltage, enable sleep]
(II) fglrx(0):   3. 209/135MHz @ 60Hz [low voltage, enable sleep]
(II) fglrx(0):   4. 311/297MHz @ 60Hz [enable sleep]
(==) fglrx(0): Qbs disabled
(==) fglrx(0): FAST_SWAP disabled
(==) fglrx(0):  PseudoColor visuals disabled
(==) fglrx(0): Using gamma correction (1.0, 1.0, 1.0)
(==) fglrx(0): Center Mode is disabled 
(==) fglrx(0): TMDS coherent mode is enabled 
(II) fglrx(0): Total of 11 modes found for primary display.
(--) fglrx(0): Virtual size is 1680x1050 (pitch 1728)
(**) fglrx(0): *Mode "1680x1050": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1680x1050"  119.00  1680 1728 1760 1840  1050 1053 1059 1080
(**) fglrx(0): *Mode "1024x768": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1024x768"  119.00  1024 1728 1760 1840  768 1053 1059 1080
(**) fglrx(0):  Default mode "1280x1024": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1280x1024"  119.00  1280 1728 1760 1840  1024 1053 1059 1080
(**) fglrx(0):  Default mode "1152x864": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "1152x864"  119.00  1152 1728 1760 1840  864 1053 1059 1080
(**) fglrx(0):  Default mode "800x600": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "800x600"  119.00  800 1728 1760 1840  600 1053 1059 1080
(**) fglrx(0):  Default mode "640x480": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x480"  119.00  640 1728 1760 1840  480 1053 1059 1080
(**) fglrx(0):  Default mode "640x400": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "640x400"  119.00  640 1728 1760 1840  400 1053 1059 1080
(**) fglrx(0):  Default mode "512x384": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "512x384"  119.00  512 1728 1760 1840  384 1053 1059 1080
(**) fglrx(0):  Default mode "400x300": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "400x300"  119.00  400 1728 1760 1840  300 1053 1059 1080
(**) fglrx(0):  Default mode "320x240": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "320x240"  119.00  320 1728 1760 1840  240 1053 1059 1080
(**) fglrx(0):  Default mode "320x200": 119.0 MHz (scaled from 0.0 MHz), 64.7 kHz, 60.0 Hz
(II) fglrx(0): Modeline "320x200"  119.00  320 1728 1760 1840  200 1053 1059 1080
(--) fglrx(0): Display dimensions: (370, 230) mm
(--) fglrx(0): DPI set to (115, 115)
(==) fglrx(0): NoAccel = NO
(==) fglrx(0): HPV inactive
(==) fglrx(0): FSAA enabled: NO
(==) fglrx(0): FSAA Gamma enabled
(==) fglrx(0): FSAA Multisample Position is fix
(==) fglrx(0): NoDRI = NO
(II) Loading sub module "fglrxdrm"
(II) LoadModule: "fglrxdrm"
(II) Reloading /usr/lib/xorg/modules/linux/libfglrxdrm.so
(II) fglrx(0): Depth moves disabled by default
(==) fglrx(0): Capabilities: 0x00000000
(==) fglrx(0): CapabilitiesEx: 0x00000000
(==) fglrx(0): cpuFlags: 0x8000001d
(==) fglrx(0): cpuSpeedMHz: 0x00000944
(==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
(==) fglrx(0): UseFastTLS=0
(==) fglrx(0): BlockSignalsOnLock=1
(==) fglrx(0): EnablePrivateBackZ = NO
(II) fglrx(0): UMM Bus area:     0x808f7000 (size=0x0f6f9000)
(II) fglrx(0): UMM area:     0x808f7000 (size=0x0f6f9000)
(II) fglrx(0): driver needs X.org 6.8.x.y with x.y >= 99.8
(II) fglrx(0): detected X.org 7.0.0.0
(II) fglrx(0): doing DRIScreenInit
(II) fglrx(0): [drm] DRM interface version 1.0
(II) fglrx(0): [drm] created "fglrx" driver at busid "PCI:1:0:0"
(II) fglrx(0): [drm] added 8192 byte SAREA at 0x2000
(II) fglrx(0): [drm] mapped SAREA 0x2000 to 0xb715f000
(II) fglrx(0): [drm] framebuffer handle = 0x3000
(II) fglrx(0): [drm] added 1 reserved context for kernel
(II) fglrx(0): DRIScreenInit done
(II) fglrx(0): Kernel Module Version Information:
(II) fglrx(0):     Name: fglrx
(II) fglrx(0):     Version: 8.24.8
(II) fglrx(0):     Date: Apr 11 2006
(II) fglrx(0):     Desc: ATI FireGL DRM kernel module
(II) fglrx(0): Kernel Module version matches driver.
(II) fglrx(0): Kernel Module Build Time Information:
(II) fglrx(0):     Build-Kernel UTS_RELEASE:        2.6.17-gentoo-r4
(II) fglrx(0):     Build-Kernel MODVERSIONS:        no
(II) fglrx(0):     Build-Kernel __SMP__:            no
(II) fglrx(0):     Build-Kernel PAGE_SIZE:          0x1000
(II) fglrx(0): [drm] register handle = 0x00004000
(II) fglrx(0): [pcie] 65536 kB allocated with handle 0xdeadbeef
(II) fglrx(0): [drm] ringbuffer size = 0x00100000 bytes
(WW) fglrx(0): [drm] using DRM defaults (QS_ID=99f0ffff)
(II) fglrx(0): [drm] DRM buffer queue setup: nbufs = 100 bufsize = 28672
(II) fglrx(0): [drm] texture shared area handle = 0x00008000
(II) fglrx(0): shared FSAAScale=1
(II) fglrx(0): DRI initialization successfull!
(II) fglrx(0): FBADPhys: 0x80000000 FBMappedSize: 0x008f7000
(II) fglrx(0): FBMM initialized for area (0,0)-(1728,1360)
(II) fglrx(0): FBMM auto alloc for area (0,0)-(1728,1050) (front color buffer - assumption)
(**) fglrx(0): Option "BackingStore" "true"
(**) fglrx(0): Backing store enabled
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using hardware cursor (scanline 1056)
(II) fglrx(0): Largest offscreen area available: 1728 x 296
(**) fglrx(0): DPMS enabled
(WW) fglrx(0): Option "RenderAccel" is not used
(WW) fglrx(0): Option "MetaModes" is not used
(II) fglrx(0): Using XFree86 Acceleration Architecture (XAA)
(II) fglrx(0): Acceleration enabled
(II) fglrx(0): X context handle = 0x1
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
(II) fglrx(0): Interrupt handler installed at IRQ 10.

Any ideas?

smitdane · Post by **smitdane** » Tue Aug 22, 2006 5:10 pm

Stardotstar, This is my synaptics config. Might I suggest increasing the min and max speeds. It will make it possible to cover the entire screen.

Section "InputDevice"
Identifier "Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Core Pointer"
Option "Device" "/dev/input/event2"
Option "Protocol" "evdev"
Option "LeftEdge" "0"
Option "RightEdge" "850"
Option "TopEdge" "0"
Option "BottomEdge" "645"
Option "MinSpeed" ".9"
Option "MaxSpeed" "1.3"
Option "AccelFactor" "0.1"
Option "FingerLow" "0"
Option "FingerHigh" "30"
Option "MaxTapMove" "15"
Option "MaxTapTime" "90"
Option "TapButton1" "1"
Option "TapButton2" "3"
Option "TapButton3" "2"
Option "HorizScrollDelta" "30"
Option "VertScrollDelta" "30"
Option "PalmDetect" "0"
Option "SHMConfig" "on"
Option "UseShm" "true"
Option "Buttons" "7"
EndSection

Hope that helps.

dmvianna · Post by **dmvianna** » Tue Aug 22, 2006 10:10 pm

tsm23 wrote:Hi dmvianna,

Yes, I do have hardware rendering and glxgears runs as I would expect it to (about 4000 fps). As for the xorg log, greping for fglrx gives the following output:
Code: Select all
(WW) fglrx(0): Option "RenderAccel" is not used
Any ideas?

Well, it looks like you don't have hardware acceleration enabled.

Did you use 'aticonfig' to set up everything for you? Did you try to find info about that option, or to enable it in xorg.conf?

tsm23 · Post by **tsm23** » Wed Aug 23, 2006 2:34 am

Hi dmvianna,

I'm not sure... Given that glxgears had such high framerates (4000 fps as opposed to about 150 when unaccelerated) I assumed that error just meant the option was deprecated or superfluous and therefore unused. The bottom of the output also says

Code: Select all

(II) fglrx(0): Direct rendering enabled

and glxinfo agrees. As for the xorg file, I copied most of it from another computer I set up which has a fully accelerated gentoo installation with an ati card.

After posting my last message, I tried downgrading to an older version of xorg but this completely broke the xserver so I went back to version 7. Since doing that, glxgears is back to only about 250 fps, but all the logs are the same as before and glxinfo claims direct rendering is enabled. I'm also able to run programs like xine, ut2004-demo, and opengl xscreensavers smoothly without crashing. I definitely have some kind of acceleration or else ut2004-demo would slow to a crawl.

Keeping in mind that glxgears isn't a reliable benchmark but can be a reasonable indicator, I ran it on my desktop gentoo system (which has an older graphics card and slower processor) and got an fps of about 7000. In light of this, it would seem that even the 4000 fps I was getting on my MacBook was lower than it should have been. Interestingly, when I run glxgears on my MacBook and hide the window, the framerate jumps to 11300 which is right about the value I'd expect given the relative power of its graphics card compared to my desktop's. All of this suggests that perhaps glxgears has a bug and actually I do have full acceleration.

Still, there are a couple things that don't work properly. Even though ut2004-demo ran as though it had full acceleration, sauerbraten runs as though it has only minimal or no acceleration. Also, dvds are very choppy when played in xine (the frame rate seems consistent with no acceleration) but xine does not print any errors suggesting a problem with the acceleration. I suspect the sauerbraten problem is just a quirk of the program and the dvd issue could simply be due to something like a missing dvd-related shared library rather than the overall xorg acceleration. I'll have to try some other 3d accelerated programs and see whether they work as expected. Do you have any ideas about this?

Thanks

dmvianna · Post by **dmvianna** » Wed Aug 23, 2006 3:54 am

tsm23 wrote:As for the xorg file, I copied most of it from another computer I set up which has a fully accelerated gentoo installation with an ati card.

Why don't you try running aticonfig? It's so straightforward, and works! Then if you would rather use free drivers, just go back, but you would know what it can do with the proprietary drivers. I should also point out that I don't get that warning message myself. And I did use aticonfig.

stardotstar · Post by **stardotstar** » Thu Aug 24, 2006 4:30 am

I have just reemerged from a couple of days hacking LFS onto the MBP and it was a most enlightening experience. As you would expect the hardware actually makes things pretty easy; the whole install proceeds exactly as the manual describes with the exception of needing to patch grub with the GateA20 patch at the appropriate moment.

One thing I am most impressed with is the ease with which triple booting can be setup. For example this time, having reorganised my drive partitions and completely reinstalling everything from OSX up I used rEFIt to do the LFS install on sda3 and added WindowsXP last and there were no complications at all. Grub works fine and so I find no complications with using EFI.

Having done the LFS install I tested the system with 2.6.17 kernel and got it to boot with the mactel patches. All was well and so having taken on board such a good learning curve I am going to reinstall Gentoo with a view to getting everything working in a more methodical way this time.

My commentry on the LFS setup and other ramblings are on my forum/ejournal - linked in a post above.

I am keen to revisit the accelerated performance of the new ati drivers since under Windows and OSX it is flawless.

Will

kaiRy · Post by **kaiRy** » Thu Aug 24, 2006 8:25 am

Does the 2 fingers right click can be use on Gentoo

Macbook Pro

Macbook Pro Audio

Sound Problems

Graphics Driver

Graphics Issues

Graphics Issues

Re: Graphics Issues

Graphics Issues

Re: Graphics Issues