Macbook Pro- Santa Rosa

[trouble1313]

***UPDATED EDIT***

Special thanks to Elv13 for this great, straight to the point howto on getting most capabilities working on the Santa Rosa Based MacBook Pro. We've come a long way in just over a month!

MBP Rev 3 HOWTO:

To install ubuntu on your macbookpro santa rosa:
1- downlaod the alternate cd 32 or 64bit
2- burn it under OSX/Windows/linux as an image
3- downlaod and install bootcamp or rEFI
4- boot on the ubuntu cd by holding the c key during boot
5- install ubuntu

To use ubuntu:
1- restart your mac and hold the alt key
2- press escape
3- boot on the failsafe kernel
4- edit the /etc/X11/xorg.conf file (nano /etc/X11/xorg.conf) and change "nv" for "vesa"
5- start X (/etc/init.d/gdm start)
6- download the lastet nvidia driver from the internet (you need to be wired) and patch it using this link https://cbg.dyndns.org/wiki/ReadingCorner/LinuxOnMacbookPro#graphics
*dont forget to install build-essential before
7- follow the rest of this link to get things working

To install pommed (powermanagement and driver):
1- cd /usr/src/modules
2- grab it svn co svn://svn.debian.org/pommed
3- downlaoad deps sudo apt-get build-dep pommed
4- cd pommed
5- make
6- follow instruction in INSTALL (file) to install it
7- get the init script from a .deb or the web and copy it to /etc/init.d

To install wireless:
1- sudo apt-get install build-essential
cd /usr/src/modules/
svn checkout http://svn.madwifi.org/trunk madwifi
cd madwifi
make;make install
modprobe ath_pci


To install alsa driver (sound):
1- install deps of alsa (automake, autotools, autoconf ans some other (please provide the list if you do this, i dont remermber it)
cd /usr/src/modules/
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-driver alsa
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-kernel alsa
[download patch_realtek.c.diff] https://bugtrack.alsa-project.org/alsa-bug/file_download.php?file_id=2097&type=bug
cd alsa/alsa-kernel
patch -p1 < ../../patch_realtek.c.diff
cd ../alsa-driver
./hgcompile
make
make install
/etc/init.d/alsasound stop
lsmod [verify all snd modules are unloaded]
modprobe snd-hda-intel


*** Original Thread Post***
Just starting a thread to document what works and what doesn't on my new Santa Rosa based MBP. Ok, it's been out all of two weeks now and here's how it stands with Feisty. System was installed and all updates added.
-
Installation:
-
rEFIt, which allows you to boot more than two OS's (ala Bootcamp) has been fixed and now does work just fine on the SR MBPs. Stellar piece of software!
-
I was unable to boot/install the standard 64 bit desktop CD. I had to use the alternate installer CD. This was strange since an old feisty beta (rev 3?) DID boot just fine.
-
After installation:
-
Booting: Issue- Leaving splash turned on seems to hang the machine. Since the screen is black, I have no idea what happens. Turning splash off in grub lets the machine boot (likely a vga=xxx added as a boot option would fix this.)
-
Ethernet: Works just fine with sky2. This is a good thing! I've had many a problem with the Yukon drivers on other platforms. The MBP implementation of the card seems to be top notch with great Ethernet features available (jumbos, flow control, offload etc).
-
Wifi: Does not work out of the box - and be careful here. I grabbed the svn trunk of madwifi and it still didn't work right. I ended up grabbing a snapshot of the 6/13/07 tree and it's working just fine. Power management and all settings seem great. Be advised, todays (6/14/07) snapshot would not compile for me. Madwifi is working with WPA-PSK and running just fine for me.
-
Keyboard and trackpad: Overall working. I am unable to get keyboard backlighting. I installed gsynaptic and it got rid of the terrible tap. I did have to turn on the shared memory setting and set up the xorg.conf as detailed by many other people on the net. I am unable to middle or right click even with F11/F12. This is frustrating.
-
NVidia driver (latest): BROKEN - Crazy colors though X does start. This issue with the 'nvidia' driver has also been noted on nvnews.net. There does not seem to be a solution yet. The 'nv' driver does not work for me at all. I am currently running the 'vesa' driver.
-
Screen: Works but no screen control features. By default, pressing the brightness up and down keys did nothing. I took a look at the hal devices and saw that this new MBP is defined as a 'MacBook Pro3,1 1.0' and the manufacturer is now 'Apple Inc.' instead of 'Apple Computer, Inc' I made changes to the hal devices xml files and now I get the pop up showing that I am hitting the brightness up/down but it doesn't change anything. It still runs full brightness. This also applies to the light sensor and keyboard backlight as it seems they are defined by hal.
-
Sound: Broken - Device appears correctly but no sound comes out of the speakers. Researching this leads to an issue with the revision of alsa that is available through the repository. This is also noted with a fix here in this forum (upgrade the alsa version). I have not upgraded alsa yet.
-
Power management: Mostly broken - Suspend does suspend the computer and completely turn off the LCD but it is not able to resume. I've found no option other than turning the system off with the power button. Hibernate is also not working. Upon hitting hibernate, the system tries to hibernate but immediately comes back.
-
Superdrive: Not working correctly - Though the system installed from CD just fine, the system does not see the CD drive at this point. I'm guessing with a bit of playing I can get this going but as it stands, it doesn't work. There are no /dev/cd* , /dev/dvd*, /dev/hd* or /dev/sd* (other than sda which is the hard drive).

iSight: Sort of works- Honestly I've spent little time playing with this. Since Ekiga is installed by default, I checked it out to see if the video worked. Video does start but it's very choppy and unusable. After ~5 seconds the program crashes. the iSight was configured as V4L2 with both PAL and NTSC settings. Both behaved identically. This could totally be an issue with Ekiga rather than the isight driver.


Hopefully, some of you have some work arounds and we can share our fixes!

-Trouble

[yanaventer]

Just to clarify, you used the "Ubuntu v7.04 (Feisty Fawn) Alternate AMD64 ISO" to do your installation?

[TrekkieGod]

Just to clarify, you used the "Ubuntu v7.04 (Feisty Fawn) Alternate AMD64 ISO" to do your installation?

I have almost the exact same nvidia problem as trouble1313, and I did use "Ubuntu v7.04 (Feisty Fawn) Alternate AMD64.iso for my installation. The difference is that although the splash screen and trying loading X with "nv" driver cause my system to hang, I get a "could not open the device file /dev/nvidia0 (Input / Output Error)" when I try to use the nvidia driver. Vesa works fine.

I should also point out that although the splash screen also made the system hang with the live cd, the video card problem wasn't the only thing preventing me from using it. When I took the quiet and splash options out of the boot parameters, I got a "can't access tty" error. Alternate cd worked perfectly though, I just have to disable the splash screen and I can't use nv or nvidia drivers after it's installed.

[trouble1313]

Yes, I used the alternate amd64 desktop CD. I had exactly the same issues as Trekkiegod with the regular desktop CD. I believe it has something to do with the drivers for CD and HD and libata? I faced similar issues with an Asus P5B recently.

-Trouble

[trouble1313]

Solution for the CDROM

Load the piix module.

I figured it was something this simple :)


(put piix in /etc/modules)


-Trouble

[TrekkieGod]

Solution for the CDROM

Load the piix module.

I figured it was something this simple :)


(put piix in /etc/modules)


-Trouble

Cool, thanks for hunting that down, trouble. Now if we can only fix that nvidia problem...

I'm wondering if the nvidia hardware in the apple laptops is significantly different from their standard hardware so that modified drivers will be needed. Other thing I can think of is that the video bios isn't getting initialized properly. I installed windows as well though, and if refit was somehow screwing that up I probably would be seeing problems with 3d acceleration in windows too.

[xpaulbettsx]

I collected some kernel info info for anyone who is interested (lspci, lshal, dmesg, etc)

http://blog.paulbetts.org/index.php/2007/06/16/santa-rosa-macbook-pro-hardware-info/

[trouble1313]

Ok folks, I still cant get sound working. I've recompiled from the actual alsa release (several times!) vs. the rc versions and it just isn't working. Have any of you gotten sound to work? It bums me out that the device is identified correctly but I just can't get any audio out of headphones or speakers. I'm kind of ok with Nvidia picking their wedgies before they release a fix since vesa works but I just can't get alsa to work. Have any of you gotten it to work? What am I missing?


On a side note, my keyboard backlight seems to work now. I noticed a hal update and applied it though it may not be the cause (not enough time in bright rooms vs. dark rooms to tell). However, it seems to be an either on or off setup. Either the backlighted keyboard is on, or it's off. To the point of me not being able to tell whether it was something in my environment causing it not to come on previously. The keyboard backlight controls are totally dead for me.


I've noticed over time that CPU throttling does seem to be working effectively, scaling CPU from 800MHz up to the 2.3xx that it does at full tilt. The FSB speed doesn't seem to change though the multiplier does. Vista seems to be able to throttle FSB whether it's due to it knowing about Santa Rosa or a platform driver on the Bootcamp 1.3 drivers disk, I don't know, but it does a bit better. I don't think that HD spindown is working and of course, the screen never really turns off. I find myself coming out of closed lid scenario at around 61 degrees C. That ain't great. I come out of closed lid 'suspend' in Vista at ~12C (room temp give or take).


Lets see some input.

-Trouble

[trouble1313]

Bumping because I see too many of the same questions looking for resolution (Santa Rosa or other that directly apply) mentioned on this forum but I've yet to see much in terms of solutions except from a few. We really need solutions. Concatenate into a single thread, I don't care, I just want stuff to work and I've got no more answers or time to play as of yet.


-Trouble

[ivesjd]

One thing you could try Trouble, is actually messing with the alsa settings, and the system sound settings. It might be trying to push the sound through something else. That's what was happening on my MacBook 1st gen.

[ronocdh]

One thing you could try Trouble, is actually messing with the alsa settings, and the system sound settings. It might be trying to push the sound through something else. That's what was happening on my MacBook 1st gen.
I too went mad trying to get sound on my MBP, and in the end it was just a simple Sound Preferences change. Sigh.

[trouble1313]

Aha! LIFE! Thank you for the replies. Unfortunately, no, trying to push sound out through OSS or the ALC device itself doesn't seem to work. Everything possible (front, speaker, iec, etc) has also been unmuted. No sound comes out of the machine. Again, I've recompiled based on the threads in this and other forums but just don't get a peep. I have no confirmation that anyone has any sound out of a SR chipset MBP under Feisty or any other distro.

-To update on the nvidia driver based on the nvnews.net discussion....Well it's certain there's a problem but it's kind of unknown what the cause is.

-As for the screen brightness and keyboard backlight- I have not gotten either to work any further with hal config changes.

[chem]

AI have no confirmation that anyone has any sound out of a SR chipset MBP under Feisty or any other distro.


Is this really the case? What audio chipset is in the SR MBP? Not integrated Intel sound? What of reports of people recompiling alsa from the dev tree and getting it working, were those just rumors? How long do you think it would be until the alsa folks got this working, if it's still broken?

I am trying to decide between a new MBP and a new T61 or T61p. It's not an easy decision.

[trouble1313]

I'd love to be wrong here! No sound is the killer for me right now. I've recompiled the alsa driver (and lib) but still get nothing. The device is identified apparently correctly and I can futz with volume and the like but I get nada. I even put some headphones in just to see if it was a speaker issue but still...nothing. Now of course I can't say that NOBODY has gotten this working but I've yet to find any confirmation that somebody has :(


-Trouble

[saserlite]

Got Santa Rosa Macbook 17" yesterday.

Current status:

No luck with standard 7.04 (AMD64) client install, alternate 7.04 (AMD64) client installed ok using the "text install" option.
Gutsy Gibbon alternate version installs ok, but appears to have even more serious graphics issues: i can't even get vesa working for graphics.
no sound - have tried alsa mixer to no avail
no nvidia drivers work - although vesa is effective (and surprisingly the open gl screensavers work fine)
i can't for the life of me get the wifi working with madwifi (i get compilation errors) - any help here would be appreciated
wired ethernet is fine though
no hibernate/suspend yet
cd-rom - doesnt work out of box, but adding piix to the modules list fixes this

[ronocdh]

Got Santa Rosa Macbook 17" yesterday.

Current status:

No luck with standard 7.04 (AMD64) client install, alternate 7.04 (AMD64) client installed ok using the "text install" option.
Gutsy Gibbon alternate version installs ok, but appears to have even more serious graphics issues: i can't even get vesa working for graphics.
no sound - have tried alsa mixer to no avail
no nvidia drivers work - although vesa is effective (and surprisingly the open gl screensavers work fine)
i can't for the life of me get the wifi working with madwifi (i get compilation errors) - any help here would be appreciated
wired ethernet is fine though
no hibernate/suspend yet
cd-rom - doesnt work out of box, but adding piix to the modules list fixes this

Could you guys run sudo update-pciids and lspci so we know your soundcard info?

[adcurtin]

Could you guys run sudo update-pciids and lspci so we know your soundcard info?

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
seems to be the only this pertaining to audio.

I used an UbuntuStudio install dvd, which worked fine, it's a text installer. I tried getting rid of the splash and quiet options in the 32bit feisty livecd/installer, and setting the graphics mode to 1280x1024, but neither worked.

[chem]

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
seems to be the only this pertaining to audio.


If that's the Intel integrated (Santa Rosa) audio, then some people with the Thinkpad T61 have been able to download dev tree alsa and get it to work (Thinkpad has intel, too). I don't know if it's the same audio, though. Good luck.

[ivesjd]

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
seems to be the only this pertaining to audio.

I used an UbuntuStudio install dvd, which worked fine, it's a text installer. I tried getting rid of the splash and quiet options in the 32bit feisty livecd/installer, and setting the graphics mode to 1280x1024, but neither worked.

If your having problems with Ubuntu Studio. You might consider reinstalling with fiesty. Wireless didnt work in US out of the box for me. Dont know what else didnt work cause I installed Fiesty after that. But you can install all the meta packages for US afterword. Let me know, I've got a how-to saved somewhere if you want it.


Here's my sound info for my MacBook 1st gen (just for reference)
Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
So it seems that they are using a newer sound chip in the SR MBP. Hope you guys can get it working. :)

[ronocdh]

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
seems to be the only this pertaining to audio.

I used an UbuntuStudio install dvd, which worked fine, it's a text installer. I tried getting rid of the splash and quiet options in the 32bit feisty livecd/installer, and setting the graphics mode to 1280x1024, but neither worked.
Interesting. Welcome and aboard and please remember to post your hardware info so people can better understand your issue. So that you know, there's also a text-based Feisty installation CD called the "alternate," but I can't attest to its working on the SR MBPs.

[saserlite]

Could you guys run sudo update-pciids and lspci so we know your soundcard info?

Here's the output from my 17" Santa Rosa Macbook Pro:

00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile PM965/GM965/GL960 PCI Express Root Port (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Contoller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3)
00:1f.0 ISA bridge: Intel Corporation 82801HEM (ICH8M) LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA IDE Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0407 (rev a1)
0b:00.0 Network controller: Atheros Communications, Inc. AR5418 802.11a/b/g/n Wireless PCI Express Adapter (rev 01)
0c:00.0 Ethernet controller: Marvell Technology Group Ltd. Unknown device 436a (rev 13)
0d:03.0 FireWire (IEEE 1394): Texas Instruments TSB82AA2 IEEE-1394b Link Layer Controller (rev 02)

[saserlite]

Instructions on how to get a graphical install of Ubuntu on a Santa Rosa MBP:


Install Ubuntu Alternate AMD64 7.04 via text install (note must be the Alternate version)
Once installed, at the grub loader press "Esc"
Choose recovery mode (this is because the GUI doesn't work out of the box)
Type in: "sudo dpkg-reconfigure xserver-xorg", choose the vesa driver, leave all the defaults, but ensure the native resolution of your macbook is selected
Once returned to the shell prompt, type "gdm", this will launch gnome


When I log-in using Gnome I get an error: "Internal Error, failed to initialise HAL!"

Also the hardware information applet doesn't work on my system

Your mileage may vary.

[chem]

No replies here in a couple of days...

For people with sound or suspend problems, have you tried the solutions listed in the Feisty w/ T61 thread? http://ubuntuforums.org/showthread.php?t=471563

There are quite detailed instructions on how to get audio working with the alsa cvs tree, and kernel command line tips for suspend. Also general tips about backporting gutsy's kernel.

As both the MBP and the T61 use the same chipset and (I think) same audio, this should work... right?

[russell.h]

My 15" MBP is supposed to ship next week! Ahh, can't wait that long!

Er... Back on topic.

[chem]

Silly question, but... does right clicking work in Ubuntu with a MBP? The two-finger touchpad right click? Any special configuration required?
And for those just joining us, I'm still hoping someone tries out the sound/suspend stuff I mention a couple posts up. -.-

EDIT: To get sound, suspend, or nvidia video working, it may be worthwhile to file bugs in the ubuntu database. I have been reading through that a bit, and it looks like the ubuntu devs actually respond to reports and fix them (even for MacBook Pro specific bugs!). As Gutsy Tribe 2 was just released, this would be a great time to install that and file bugs against gutsy. Maybe everything will work out of box by gutsy-release!

https://bugs.launchpad.net/ubuntu/+bugs
https://wiki.ubuntu.com/DebuggingProcedures
https://help.ubuntu.com/community/ReportingBugs

[pepe#]

nvidia: http://www.nvnews.net/vbulletin/showpost.php?p=1301201
alsa: modprobe snd_hda_intel model=w2jc

No headphones, but mic and front speaker.

Sensors, keyboard illumination and shortcuts work with patches from mactel-linx and current pommed.

If you have information about iSight or other updates, please mail me, pepe "at" cbg.dyndns.org.

https://cbg.dyndns.org/wiki/ReadingCorner/LinuxOnMacbookPro


/pepe

[trouble1313]

Pepe, thank you! I actually had come here to post your alsa modprobe option that I found over at nvnews.net (I figure you're the same pepe ;) ) and saw you put it up....Great find man, made a huge diff for me to stop booting Vista and get back in here to Feisty on this sexy little machine.
Thanks again!


Just to expand and document how everyone can make it work at reboot:


Put the following line in /etc/modprobe.d/options:

options snd_hda_intel model=w2jc



-Trouble

[trumpcool]

To get a right and middle click you can install mouseemu. By default, F12 is right click and F11 is middle click. The button mappings are supposed to be configurable by editing the /etc/default/mouseemu file but I haven't had any luck so far.

edit> A side effect is that the lights for caps lock and num lock no longer work.

[cyberdork33]

To get a right and middle click you can install mouseemu. By default, F12 is right click and F11 is middle click. The button mappings are supposed to be configurable by editing the /etc/default/mouseemu file but I haven't had any luck so far.

edit> A side effect is that the lights for caps lock and num lock no longer work.

Thanks, that was annoying since I didn't need it.

[Elv13]

Hi, i am looking for a new laptop and the santa rosa MBP is an interesting choice. I just have few questions:

Do synaptic is able to enable 2 finger scrolling, multi finger tapping and all these options on the mac book pro (it work on my pc)

Do sensor (accelerometer and light sensor) work? They are probably the same since power book so did someone wrote a driver for them?

Did someone found a way to fix the brightness control?

What about the NouVeau driver? It is an alternative (in early development) nvidia driver. They do support up to 7950, but who know, there is some developer working on 8*** support since month, it can load.

Is it a good laptop or it start to do some overheating out of the box.

[detjoe]

Hey folks, thanks for all the hints. I got sound working as described by pepe. Weird thing is that headphones/external speakers work with the INPUT jack. Its still kind of low volume and a white noise but it works. Front speakers are not muted though.

[chem]

Hey folks, thanks for all the hints. I got sound working as described by pepe. Weird thing is that headphones/external speakers work with the INPUT jack. Its still kind of low volume and a white noise but it works. Front speakers are not muted though.

That's a really weird observation about the headphones. Maybe you (or... anyone with a SR MBP) could work with the alsa-user mailing list to get headphones properly / fully working? My MBP should arrive in 3 weeks! I will help out then :P

http://www.alsa-project.org/
http://news.gmane.org/gmane.linux.alsa.user

[detjoe]

Oh, I should have mentioned that this only works with 6ch activated in the alsa mixer. There is some other stuff you can try like enable/disable optical IO (which works for me). Found all that at http://wiki.debian.org/MacBookPro and http://wiki.debian.org/MacBook . The Volume control for the headphones with the line in and muting the internal speakers didn´t work.

[ilmarw]

I got the NVIDIA drivers working, external screen and all, by following this guide: http://albertomilone.com/latest_nvidia_udsf_edgy.html

[trouble1313]

Ilmarw, you got me excited but after looking at that page, are you sure you're on a MBP with the 8600GT M graphics card? I see no reference to it, it seems to discuss older drivers that don't work with the card at all and the SR MBP has specific problems. Did I miss something?

[alephsmith]

I can't get the nvidia drivers working even with the external screen->sleep->wake->reboot hack.

I think I'll just wait till the next release and give it another go then. Vesa is killing my eyes.

[ilmarw]

100% positive...

Plus, now I got the sound working, too. Recompiled alsa from CVS, followed the instructions here: http://alsa.opensrc.org/index.php/AlsaCVS

[chem]

100% positive...

Plus, now I got the sound working, too. Recompiled alsa from CVS, followed the instructions here: http://alsa.opensrc.org/index.php/AlsaCVS

Did you use the model=w2jc option for snd_hda_intel ? Or does the latest alsa CVS correctly autodetect the SR MBP's sound chipset? That would be a first report of this. Does your headphone jack work, volume control and all?

[Elv13]

100% positive...

Plus, now I got the sound working, too. Recompiled alsa from CVS, followed the instructions here: http://alsa.opensrc.org/index.php/AlsaCVS

About graphic card
Do you use the 32 or 64 bit version and you did the second method unmodified? And you are using edgy of feisty (the guide talk about edgy)?

[Paerez]

Hey all. I am running on a new MBP santa rosa with 8600m GT, as you all are.

I installed with the amd64 alt cd and edited my grub/menu.lst to turn off splash. I am using the vesa driver for xorg.

I was able to get the close-lid switcheroo to work but it was a pain so I am back to vesa (I used the envy app in feisty to get it to work).

My sound half-worked out of the box. When I plug headphones in and turn all volumes all the way up I can faintly hear music I am playing, but my speakers don't work.

My wifi worked once I upgraded fiesty.

I have not yet tackled suspend or right clicking (I am using a usb mouse for now).


Mainly I am just saying hi and subscribing to the thread, and I will post my victories as I achieve them. I am sure that support will come along for the major components (like sound and video) but the niceties may take a whie (auto-illuminated keyboard).

[ahaller]

Hi,

unfortunatly i have no sound using Gutsy Gibbon Testing. Neither through the internal speakers nor through the headphones (or line input).

I tried modprobe snd_hda_intel model=w2jc . I also tried fumbling around with the also-mixer but no success.
Anyone s testing Gutsy and got sound to work?

Bye,
Andreas

[ilmarw]

About graphic card
Do you use the 32 or 64 bit version and you did the second method unmodified? And you are using edgy of feisty (the guide talk about edgy)?

Sorry, I should have been more spesific. I am using Feisty 32-bit version, and I used the second method from the guide mentioned.

[ilmarw]

Did you use the model=w2jc option for snd_hda_intel ? Or does the latest alsa CVS correctly autodetect the SR MBP's sound chipset? That would be a first report of this. Does your headphone jack work, volume control and all?

Yes, I use model=w2jc. I tried it earlier, but it didn't work until I used the CVS version. I still do not get jack, and the channels are not right, but I got sound, and that I am happy with.

[trouble1313]

Ilmar, please help us out on the Nvidia front...You say you used the directions at the site you mentioned...That site references older drivers, that's cool...But those drivers totally don't handle the MBP SR vidcard...The latest Nvidia drivers supposedly support the 8600GT M but are rather broken by default on the MBP SR for whatever reason and have multiple people reporting 'crazy colors' (which is a good way to describe it, and I'd describe what I get out of them similarly). So how are you getting things to work when the rest of us can't?

Are you using Pepe's (the guy I saw post this hack first) 'use an external keyboard and monitor to set it up' workaround?

Then I say ok, cool, PITA workaround but seems to work I guess...

Are you saying that you just installed the driver and it works just dandy?

If that's the case, I have to call shenanigans because it seems nobody else has been able to get it working properly.

Fill us in!

-Trouble

[csaldan]

I also just bought a new MBP , Santa rosa.

Im pretty new to linux so im not sure how to solve my problem. i tried installing feisty but i get stuck at this one point. During installation when it asks me to start the installation it loads some of the drivers and other stuff and at one point the screen jus goes black and i dont know whts goin on.

Can someone help me with this problem?

Thanks:confused:

[red star]

Which os are you using? I had the same problem but it was in the iso. I downloaded another copy and it was fine. That could be your problem, or you need to turn splash off.

[pepe#]

hi all,


I got two reports that the current version of xfree-nv driver from git is working, but not at the native resolution it seems.

nvidia color problem is reported by everyone so far. One guy in the nvidia forums said it's going to be fixed in the next version. Full 3d support+external display etc. work with the mentioned workaround. Also note that this works without external keyboard if you are fast enough and close your display before osx wakes up and detects the screens.

I got no further feedback from alsa-dev concerning the audio problem. It looks like a simple problem, as if the channels are mixed up a little. The driver source doesn't look that complicated but I have no time to investigate this further...

trouble1313: I just noticed that I didn't reply to your pm. I read it in the email notification and got motivated enough try again and got iSight working with the mplayer compiled from svn. so cudos to you :)

csaldan: maybe your installer tries to start X? Current nv drivers give a blank display. Try installing without X or with VESA...

Paerez: sound, keyboard backlight, video, s2ram, iSight, touchpad all sort of work. If you or anyone find additional information or patches it would be great if you leave a small note in https://cbg.dyndns.org/wiki/ReadingCorner/LinuxOnMacbookPro

/pepe

[csaldan]

I tried using the x86_64 iso. Could you tell me how to change it to "vesa"?

Thanks a lot

[Elv13]

use the alternate install cd to boot in rescue mode, mount your partition following instruction on screen, write:
nano /etc/X11/xorg.conf

and replace nv with vesa

[asoare]

Hello,

I am a new owner of a Santa Rosa MBP and am trying to install ubuntu. As you all said, booting from the live cd doesn't work, something about tty, I don't know.

So I read I must install from Ubuntu Alternate AMD64 7.04 ? But why not Ubuntu i386 alternate ? MBP is intel-based, not AMD.

Also, can you please direct me in detail on how to install from the command line? I am a linux newbie (windows all my life) and want to make the switch and I need some help.

And is it possible to make the graphical install work ? from the live cd ? also I would like to make the gparted live cd work, since it also doesn't work.

Thank you.

[ahaller]

hi,

yes, the new MBP has an intel cpu, but the core 2 duo is a 64bit cpu, so the "AMD64" release should fit best. Dont get irritated by the "AMD"-name. The "64" is the interesting part of it.
On the download page (http://www.ubuntu.com/getubuntu/download) the 64bit relase is correctly describes as for "64bit AMD and Intel computers".
You can also use the 32bit version ("i368") version as i do. But i think 64bit should be the better choice.
(i dont really know about this stuff well, i only use 32bit because i am currently testing the unstable gutsy relase, and the development usually seems to be a bit slower for 64bit platforms compared to "standard" 32 bit.)

As for the installtion, have you already tried the alternate cd? The installation process is not really more difficult than the grafical installation.

Here's a short description of what i did:
Install OSX
Since the standart installation of OSX came with a few things i did not want to be installed (like dozends of additional language packs i dont use), i reinstalled OSX. During installation i partitoned the harddisk to get some space free for ubuntu (sth like 70gb in my case). You cannot choose the ext3 filesystem, so i just chose "free space" or sth like that.
Use the alternate cd to install Ubuntu linux.
I just chose "use free space" or so, when being ask where to install it.


Just one thing for you as a beginner. Don't expect everything to run out of the box (like with OSX). Since the new MBP is very new (new chipset, new graphics card) there are issues with getting 3d graphics and sound to work. But, as with every problem for ubuntu, there are (or will be) people who help with finding solutions for these issues.

[Elv13]

i386 = 32bit
AMD64= 64bit

core 2 duo are 64 bit, it is why you can install ubuntu AMD64. If you want to install Ubuntu i386, you can, you will have flash more easily but you will not take adventage of the power of your hardware.

And dont worry about the alternate installer, it is very easy, all information will be on screen and you will be able to make your partition like with gparted, just without mouse.

[pepe#]

for the 64bit people:

do the drivers work? all of them? nvidia probably not, so no 3d accel?

[csaldan]

use the alternate install cd to boot in rescue mode, mount your partition following instruction on screen, write:
nano /etc/X11/xorg.conf

and replace nv with vesa

I m using the ubuntu 7 amd64 iso, i hope this is wht u r talking about. I m sorry but i dont noe where to put in those instructions which u jus gave me. How do i get into rescue mode?

Thanks

[csaldan]

so im downloading the alternate version now and this is wht i think im gonna do

At installation command line, i type in

boot: linux rescue

and then follow instructions for mounting the CD-rom and then i change the videocard driver from nv to vesa in the xorg.conf file?

thanks :)

[detjoe]

Hi. I used the normal 32bit version.

Boot from the CD.
Choose "save graphics mode" and press F6.
Remove "splash", "quiet" and "--" then add "all_generic_ide"

That worked for me.

[asoare]

Isn't 32bit more likely to be compatible than 64bit ? Aren't more drivers available and more things working for 32bit ?

@detjoe: nice, it worked for me too, but can you please explain what quiet, -- and all_generic_ide mean ? And why it works this way and not the normal way ?

I used gparted to create a fifth partition (ntfs) for data storage but it doesn't work in vista, it is considered unallocated space, because it is the fifth primary partition. How do I create it without making it primary ?

Also, can you please guide me in installing from graphical ? i want a triple boot and read in the guide :

For triple boot, make a swap file because of partion number limit explained
on http://wiki.onmac.net/index.php/Trip...t_via_BootCamp
Open a terminal. (Application>Accessories>Terminal)
Quote:
sudo su
mkdir /mnt/linux
mount -t ext3 /dev/sda3 /mnt/linux
sudo dd if=/dev/zero of=/mnt/linux/swap bs=1024 count=2097152
mkswap /mnt/linux/swap
swapon /mnt/linux/swap

sudo dd if=/dev/zero of=/mnt/linux/swap bs=1024 count=2097152 --> doesn't do anything ... what is it supposed to do and how do I make it work ? and how do I choose swap as file ?

[alephsmith]

for the 64bit people:

do the drivers work? all of them? nvidia probably not, so no 3d accel?

Nvidia: (+twinview) works using the sleep & external screen thing. Compiz-fusion is working fine. I'm using packages from uPure64 repos.

alsa: works from after compiling from latest snapshot.

madwifi: works, but not from svn. I took an older snapshot and I can't remember the exact date. Was a bit of pot luck. Also setting up WPA2 was a pain.

Haven't tried iSight yet.

Flash: works via nspluginwrapper

[alephsmith]

I just received a Software update in OS X:

Macbook Pro EFI Firmware Update 1.3

Will this screw up my dual boot setup? Should I be wary?

[pepe#]

> Will this screw up my dual boot setup? Should I be wary?

It could overwrite the refit bootloader, see here what to do: http://refit.sourceforge.net/doc/c1s4_osxupdates.html

The enable-script is somewhere in /efi/refit or so, do not use the one from the install package. installing again will probably work too...

> alsa: works from after compiling from latest snapshot.

Works as in 'works' or do you mean with model=w2jc?
I've seen nothing at alsa-devel that would fix santa-rosa mbp during the last days.

Latest status is w2jc + seperate front and linout mute switches as described in http://article.gmane.org/gmane.linux.alsa.devel/47539. Just browse the realtek_patch.c for where the w2jc mixer settings are defined and you'll see what you need to change.

[csaldan]

so im downloading the alternate version now and this is wht i think im gonna do

At installation command line, i type in

boot: linux rescue

and then follow instructions for mounting the CD-rom and then i change the videocard driver from nv to vesa in the xorg.conf file?

thanks :)


i still cannot install it , once i boot in rescue mode, it starts asking me for my keyboard type and after it s done doing the network configurations it doesnt do anything after tht , it jus gives me a blue screen with rescue mode written on the top

[Elv13]

so im downloading the alternate version now and this is wht i think im gonna do

At installation command line, i type in

boot: linux rescue

and then follow instructions for mounting the CD-rom and then i change the videocard driver from nv to vesa in the xorg.conf file?

thanks :)

When to boot with the alternate cd, you will have this option right on your screen. Then follow instruction.

[alephsmith]

@pepe

Yes, you are right. It works when set to model=w2jc
I've done so many things trying to get everything to work I tend to the steps I've taken.

[Corvias]

OK. So I just spent the last hour posting bugs relating to gutsy and the macbook pro. Let's get to work and make sure that the final release of gutsy works flawlessly on the MBP SR! Being active on launchpad is the only way that we'll get things working by default, rather than having to jump through hoops to get a fully functioning system

I'll even make it easy on you. Below are the links to launchpad of the six bugs I posted. Please add comments and details, so the devs know that there is an interest!

https://bugs.launchpad.net/ubuntu/+bug/125911
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/125914
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/125915
https://bugs.launchpad.net/ubuntu/+bug/125916
https://bugs.launchpad.net/ubuntu/+bug/125918
https://bugs.launchpad.net/ubuntu/+bug/125919

these refer to the display brightness, the default nv xorg module, the mvidia-glx package, the "crazy colors" bug under feisty, the keyboard light sensors, and the wifi adapter.

Lastly, there's also a bug posted related to the sound problems someone posted recently. It can be found here:

https://bugs.launchpad.net/ubuntu/+bug/125332

Make some noise!

[isitbreakfastyet]

Well done for doing that.

I have a brand new Santa Rosa MBP and have had to switch to OSX until this is fixed. :-( , and have to say that although OSX is a nice OS, I really miss alot of Linux apps, such as Amarok, Rosegarden and Konqueror. Being in OSX feels like being in a mercedes with a 1.0 litre engine.

I have got Kubuntu installed fine after disabling the splash screen etc.

Any developments and I will be happy to test them out.

[amonsul]

Hi!
Im in New York Applestore thinking about buying a Macbook. I need Final Cut Pro. But i work with Ubuntu too so reading yor post im getting a little afraid. It seems that we have a lot of Problem running Ubuntu on a Macbookl.

Maybe it would be nice to develop a Ubuntuversion especially created for macbook pros.

Bye

[cyberdork33]

Hi!
Im in New York Applestore thinking about buying a Macbook. I need Final Cut Pro. But i work with Ubuntu too so reading yor post im getting a little afraid. It seems that we have a lot of Problem running Ubuntu on a Macbookl.

Maybe it would be nice to develop a Ubuntuversion especially created for macbook pros.

Bye

It's not a problem of a special version, it is a problem of getting things to work at all... in any version of linux.

[dpope]

Hi All,

I currently own a MacBook Pro 15" rev 2 (merom core 2 duo and ATI X1600 card) but this laptop has many problems under linux. I'm planning to sell it and get a new laptop, either a rev 3 with a Nvidia card or maybe some other laptop. I've skimmed over all the posts on this thread and see that the santa rosa MBP is not spectacularly well supported under linux but things seem to be improving. I would appreciate it if someone could explain/list what the major open issues are and if they think these will be resolved.

My impression is that Nvidia, unlike ATI, makes decent, albeit closed-source, driver for linux so, even if they don't work right now they likely will improve soon. One of the major problems with the rev 2 MBP is the very high power consumption which many people think is related to the fact that the X1600 on the rev2 (unlike the rev1) could not be powered down to a lower clock rate. Does power management currently work for the GPU on the Santa Rosa MBPs? What kind of battery life are people currently getting in Linux (vs OS X)? Does the machine run much hotter in Linux and does it consume much more power.

Two issues which I don't think have been fixed in the SR MBP are the low dpi (1440 at 15" is not impressive) and the limited tilt angle of the screen which makes it hard to read things on your lap quite often. If anyone knows of a laptop with similar specs/weight as the MBP but has a higher res screen please let me know.

thanks

[ahaller]

hi dope,
i can say that the rev. 3 MBP is not getting as hot as the rev. 2. One Problem i had with the rev. 2. was that the fan was spinning almost always. The fan of the rev. 3 does not spin all the time. Eventually i would say the fan spins like in osx - so you dont care about it.

In spite of that, i cannot say that the power consumption has improved very much. The gpm-applet says that the fully charged battery "provides 1 hour 55 minutes battery runtime". But i did not test these numbers.

I am running the vesa driver, because the nvidia driver does not work at the moment, as you mentioned.
I dont know any laptop with a better screen. I hope and believe, that the linux situation of the MBP will improve. So i say one of the most steadfast arguments against the MBP is the lack of a second mouse button... (and maybe the price)

[ilmarw]

Ilmar, please help us out on the Nvidia front...You say you used the directions at the site you mentioned...That site references older drivers, that's cool...But those drivers totally don't handle the MBP SR vidcard...The latest Nvidia drivers supposedly support the 8600GT M but are rather broken by default on the MBP SR for whatever reason and have multiple people reporting 'crazy colors' (which is a good way to describe it, and I'd describe what I get out of them similarly). So how are you getting things to work when the rest of us can't?

Are you using Pepe's (the guy I saw post this hack first) 'use an external keyboard and monitor to set it up' workaround?

Then I say ok, cool, PITA workaround but seems to work I guess...

Are you saying that you just installed the driver and it works just dandy?

If that's the case, I have to call shenanigans because it seems nobody else has been able to get it working properly.

Fill us in!

-Trouble

It just worked out of the box, I never attached an external monitor or keyboard to it until it worked. What you sais got me thinking. I hardly ever use OSX, so I tried to reboot Linux after I had started OSX. It seems that I experienced the same problem as you guys, sorry to get you excited.

The only explanation for this would be that I entered the state that pepe described not in the exact way he did, but through waking up my machine using the remote control (i did that once). I haven't tried to reproduce that (haven't got the time).

ilmar

[[woodstock]]

hi dope,
In spite of that, i cannot say that the power consumption has improved very much. The gpm-applet says that the fully charged battery "provides 1 hour 55 minutes battery runtime". But i did not test these numbers.

Close to 2 h battery life with a fully charged battery? That isn't much indeed.
Has anyone tried a kernel > 2.6.21 (Gutsy for instance or a self patched kernel) yet? I have read somewhere that there should be some improvements concerning the power consumption under linux. Can anyone confirm that?

[dpope]

hi dope,
i can say that the rev. 3 MBP is not getting as hot as the rev. 2. One Problem i had with the rev. 2. was that the fan was spinning almost always. The fan of the rev. 3 does not spin all the time. Eventually i would say the fan spins like in osx - so you dont care about it.

In spite of that, i cannot say that the power consumption has improved very much. The gpm-applet says that the fully charged battery "provides 1 hour 55 minutes battery runtime". But i did not test these numbers.

I am running the vesa driver, because the nvidia driver does not work at the moment, as you mentioned.
I dont know any laptop with a better screen. I hope and believe, that the linux situation of the MBP will improve. So i say one of the most steadfast arguments against the MBP is the lack of a second mouse button... (and maybe the price)

Thanks for the response. I think there is a lot that can be done to improve power management. First, once the nvidia driver works (open source or closed source) it should provide power states that can reduce power usage. Second, as I understand, you can't dim the screen yet and that will obviously have a big effect. Third, the new kernel >2.6.21 has a feature (whose name I've forgotten now) that lets the cpu take better advantage of its deep sleep states so that should also help. If you look on the mactel-users mailing list you should see that people with rev 1 macbook pros were able to get pretty decent power consumption on their machines. You can compare you linux and os x power usage directly by comparing the "Power" section in the OS X system profiler with the output of some file in /proc/power/BAT0/ under linux (exact path might be wrong but its something like that). You have to do this while running on battery and then you can see how much power you're eating up.

Just the fact that the fans aren't spinning all the time is encouraging for me though because this is a serious problem on my MBP rev 2.

How about any other hardware -- does anything else seem like its not going to work anytime soon? I have potential buyers for my MBP rev 2 so I want to find out ASAP if I should let go of it and get the rev 3.

Incidentally I find the trackpad two and three tap options a nice replacement for having multiple buttons though the linux implementation of two-finger scrolling still needs some work (though the appletouch driver seems to be getting better every time I try it).

The screen on these machine IMHO is not very impressive. I had a 17" sony with 1920x1200 res and that is still the most amazing screen. It can be read from any angle, even on top, is extremely crisp and has superb colors. I think a 15" should at least be available at 1600x1200. This is one of my major hold-ups in replacing my rev 2 MBP with a rev 3 (and the limited tilt angle of the screen). If anyone has interesting alternatives please let me know.

[chem]

I'll even make it easy on you. Below are the links to launchpad of the six bugs I posted. Please add comments and details, so the devs know that there is an interest!

https://bugs.launchpad.net/ubuntu/+bug/125911
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/125914
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/125915
https://bugs.launchpad.net/ubuntu/+bug/125916
https://bugs.launchpad.net/ubuntu/+bug/125918
https://bugs.launchpad.net/ubuntu/+bug/125919

these refer to the display brightness, the default nv xorg module, the mvidia-glx package, the "crazy colors" bug under feisty, the keyboard light sensors, and the wifi adapter.

Lastly, there's also a bug posted related to the sound problems someone posted recently. It can be found here:

https://bugs.launchpad.net/ubuntu/+bug/125332

Make some noise!

Very nice post Corvias! Hopefully this will lead to things like ALSA and the nv driver being updated so that they "just work" on gutsy.



Also, regarding dpope and lowering linux laptop power consumption: http://www.linuxpowertop.org/results.php

I think the new feature you're talking about is the dynamic tick (tickless?) kernel, which may or may not be in gutsy (I don't know) for x86-64. Anyway, that website has a bunch of good tips.

Let's try to keep the chat here related to linux/ubuntu and the rev.3 MBPs, not general ranting and chat about screen resolutions, eh? :)

[0deuce0]

Hey everyone...


What we really need is the first post of this thread to summarize the installation process. What do to...


For example:

- Installation. Use the XXX CD.
- Video
Instructions for the VESA / or the nvidia
- Sound
- Camera ...


Kind of how the first post is, but maybe keep it upto date with what people have found...


Just a thought... because Im going through all of this thread wondering where to begin...

[chem]

I received my MBP today. Partitioned with diskutil, installed refit, and tried gutsy tribe 3. Desktop cd refused to install, but alternate worked. Had all the same bugs everyone else reported, plus the Superdrive refused to read an audio disc (didn't try data disc) after ubuntu was installed. One other person had already reported that in launchpad. I added comments to the other bugs in launchpad.

In short, no improvement with gutsy tribe 3. I am going to just use mac OS X for a while; the BSD shell in there + fink is pretty good anyway.

[buti]

... Below are the links to launchpad of the six bugs I posted. Please add comments and details, so the devs know that there is an interest!

https://bugs.launchpad.net/ubuntu/+bug/125911
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/125914
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/125915
https://bugs.launchpad.net/ubuntu/+bug/125916
https://bugs.launchpad.net/ubuntu/+bug/125918
https://bugs.launchpad.net/ubuntu/+bug/125919

these refer to the display brightness, the default nv xorg module, the mvidia-glx package, the "crazy colors" bug under feisty, the keyboard light sensors, and the wifi adapter.

Lastly, there's also a bug posted related to the sound problems someone posted recently. It can be found here:

https://bugs.launchpad.net/ubuntu/+bug/125332

Make some noise!

what about the dvd drive? does it work on your gutsy-system? it doesn't work for me. i'm booting through refit, might this be a cause?

[Paerez]

buti, are you loading the module piix? You can "sudo modprobe piix" or add the text "piix" to the end of "/etc/modules".

[Corvias]

what about the dvd drive? does it work on your gutsy-system? it doesn't work for me. i'm booting through refit, might this be a cause?

Actually I submitted that one a few days ago: :)

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126908

[Baladahn]

Hello,

So I read I must install from Ubuntu Alternate AMD64 7.04 ? But why not Ubuntu i386 alternate ? MBP is intel-based, not AMD.


If you want the 64 bit version of the OS, AMD64 is for both Intel and AMD CPUs, as AMD made the current standard x86-64 instruction set.

[pepe#]

little word of warning: After updating the EFI firmware with OSX, the workaround for the current nvidia driver doesn't seem to work anymore. As nv has no xv support, I'm now waiting for the new nvidia driver... :-/

[grabbies200]

hello,
i am trying to install ubuntu on my MBP. I d like to install ubuntu on an external usb hard drive. I know grub doesn't support efi/mbr hybrid and i was wondering is someone knows how to install grub2 or eilio so i can boot from my exteranl HD. right now refit sees i have an external hd with linux, but if i try to boot it it tells me that the firmware doesn't support booting from an external hard drive.
:confused:

[Elv13]

with the darwin (not bootcamp) bootloader it is possible i think, but i cant test, i dont have mine yet.

[alephsmith]

little word of warning: After updating the EFI firmware with OSX, the workaround for the current nvidia driver doesn't seem to work anymore. As nv has no xv support, I'm now waiting for the new nvidia driver... :-/

Unfortunately, I have found the same thing.

I am leaving Ubuntu on my MBP for the time being. I may return when the things start working out of the box. I don't have the time to tinker too much at the moment.

[trouble1313]

Great news today from nvnews.net! A simple trick to get the NVidia binary official drivers to work on the SR MBP!

Start X with the nv driver

quit X

change your xorg.conf from the nv driver to the nvidia driver

start X

viola!

All functionality seems to work, xv, glx etc. Beryl runs great.

I automated the starting, stopping, changing driver, restarting with a simple script and have it run on startup in place of /etc/init.d/gdm. It adds maybe 15 seconds to the startup process but I have a good 10 seconds of sleeps in there. I didn't mess with the timing, just guessed so I'll bet it can be cut down a bit.

Running under the nvidia driver seems to have dropped my coretemp a good 10 degrees and I think shaved ~6 watts off battery usage. (I'm going based on my memory here). My coretemp is at 56 now during usage, was 65 idling. The external heat difference has been very noticeable.

In other words, I'm pretty stoked!

-Trouble

[axlsd]

Hello guys,

can anyone tell me how to install nv drivers?? ..so I can do the nv->nvidia workaround!
now I have just installed the nvidia drivers (with the crazy-colors problem..).

Someone help me please!
Thanks!
ps: I'm an italian user :) , please forgive my mistakes..

[dpope]

Hi Trouble,

What is your power usage and battery life now (you said it dropped six watts but you didn't say from what value)? Also, do the fans not run much?

thanks

[Corvias]

Great news about that little trick! Ummm. Any chance of sharing that script?

This is going to sound newbish, but how exactly do you quit x?

[alephsmith]

This is going to sound newbish, but how exactly do you quit x?

sudo /etc/init.d/gdm stop

can anyone tell me how to install nv drivers?? ..so I can do the nv->nvidia workaround!
http://www.nvnews.net/vbulletin/showpost.php?p=1314378&postcount=73

[dpope]

Hi Trouble,

What is your power usage and battery life now (you said it dropped six watts but you didn't say from what value)? Also, do the fans not run much?

thanks

Actually, a more specific question: can you run beryl without your temp going up and your fans running at higher speeds?

[axlsd]

I downloaded xorg-dev, downloaded xorg tarball from the official site, installed it (./configure, make, make install)..
but there is no sub-directory drivers on /usr/local/lib/xorg/modules/
Where is the mistake?

[alephsmith]

I used the tarball from here:

http://lists.freedesktop.org/archives/xorg-announce/2007-July/000324.html

[pepe#]

> I downloaded xorg-dev, downloaded xorg

Not needed anymore, gimli posted a patch to the glue-code of the nvidia driver.
I'm unable to download the attachment of his mail in the list archive, so I linked it:

https://cbg.dyndns.org/wiki/ReadingCorner/LinuxOnMacbookPro#graphics

Patch, including short hotwo: https://cbg.dyndns.org/store/config/nv_macbook.diff


have fun :)

[trouble1313]

Sorry, I'm away from my laptop right now so I'll try to post that script later...but it really doesn't do anything other than copy an xorg.conf.xxx with nv or nvidia defined into xorg.conf and do gdm start and stop.


From a power aspect, in testing yesterday, I was idling at about 24 watts. I was at 30 with nv or vesa. Idle temp with nvidia was down to 51 degrees. I ended up with 2 hours and 23 minutes before shutdown on battery BUT I worked it pretty good...compiled a few things, looked at youtube a bit, AND BURNED A DVD! Burning the DVD pushed power up to like 35 watts! 2.5 hours under normal easy use should be no issue at all. Not great, but better and in line with what I see in Vista. During all of this time, Beryl was running and I was playing with it. I don't think the fans ever kicked up to be honest. Beryl doesn't seem to be adding much of a load to the system at all.


Suspend is still broken. I didn't try hibernating.
For some reason I've lost my keyboard backlight...I don't know if it was due to a normal feisty kernel upgrade or due to nvidia.
-Trouble

[axlsd]

Thanks for your help!
I finally found my error and now all seems ok! nv->nvidia workaround works fine.
Anyway.. maybe can help someone.. so, the right procedure to install nv drivers is:
apt-get install xorg-dev
then download the following pkg: http://xorg.freedesktop.org/archive/individual/driver/xf86-video-nv-2.1.2.tar.gz
extract it, go into the directory just created and type:
sudo ./configure
sudo make
sudo make install
if you read the last rows of the installation process you can see that the new module is installed in the local directory : /usr/local/lib/xorg/modules/drivers/
so.. rename the current nv module and create a symbolic link to the module just builded:
cd /usr/lib/xorg/modules/drivers
sudo mv nv_drv.so nv_drv.su.backup
ln -s /usr/local/lib/xorg/modules/drivers/nv_drv.so

Last steps (nv->nvidia workaround), stop gdm, change the xorg.conf so it can load first the nv driver then type startx and log-out.
Change again the xorg.conf so it can load the nvidia driver then type startx.
That's all.

Ps: again, forgive my bad english writing..

[pepe#]

You can start X directly:

Xorg -novtswitch -config ~root/nv-driver.conf
sleep 5
killall Xorg


Anyways, restarting X/gdm is not neccessary with the patch by gimli I posted above. No need screwing around with latest x11 tarballs.

Edit:

There is now a patch for alsa and a tool for backlight control:

https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3242
http://felipe-alfaro.org/blog/2006/09/11/basic-backlight-support-for-macbook-pro/

Together with the modified nvidia driver, the macbook gets quite useable.

trouble1313, you said you have no suspend. If you mean s2ram, I have this working with the nvidia driver. However, the text consoles are broken afterwards and vbetool doesn't seem to help. Just make sure to unload alsa,madwifi and the sky2 module. Then execute this:

chvt -t 9
echo mem > /sys/power/state
chvt -t 7
chvt -t 9
chvt -t 7

[Paerez]

I used the diff patch in a previous post and my MBP is now compiz-fusion-tastic!

[trouble1313]

Awesome...that patch worked great! Great find.

[axlsd]

The diff patch works fine, I installed compiz-fusion.. It seems a little heavy sometimes.. in particular way if I try to rotate the cube when reflex are activated, the framerate is lower. Has anyone the same "problem"?

[Paerez]

It's probably just because you're asking for it to do a lot of work, so it's laggy.

Remember compiz technology is so new it may not do effects you're used to in video games as quickly as a video game can do them.

I haven't played with compiz much, but it seemed pretty snappy to me.

[epaulin]

> I downloaded xorg-dev, downloaded xorg

Not needed anymore, gimli posted a patch to the glue-code of the nvidia driver.
I'm unable to download the attachment of his mail in the list archive, so I linked it:

https://cbg.dyndns.org/wiki/ReadingCorner/LinuxOnMacbookPro#graphics

Patch, including short hotwo: https://cbg.dyndns.org/store/config/nv_macbook.diff


have fun :)


hi, pepe, tnx for your great infomation.

Could your mail it to me, seems my network can't access it neither through tor.

epaulin _AT_ gmail dot com

[cyberdork33]

It's probably just because you're asking for it to do a lot of work, so it's laggy.

Remember compiz technology is so new it may not do effects you're used to in video games as quickly as a video game can do them.

I haven't played with compiz much, but it seemed pretty snappy to me.

Yea it is actually one of the suprising things that people catch, compiz-fusion seems to have a much faster response than beryl does.

[axlsd]

Still another thing, I installed Ubuntu with lilo bootloader (I read somewhere that linux boots only with it).. but I can boot with splashscreen and framebuffer with a good resolution.. Does anyone boot linux with grub? ..and can give me a hand to configure it?:)
Thanks!

[pepe#]

pommed now includes the display control code from above in svn rev 346:

svn co svn://svn.debian.org/pommed


Automatic keyboard backlight was also updated in v1.8.
Debian/unstable still has an older version, don't know for ubuntu.

if you find something new with how the alsa driver is working or is supposed to, please post it here: https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3242

[epaulin]

I got a error when I was following instruction to build NVIDIA module which is a link from pepe

Is here any one got it work on Ubuntu gutsy with AMD64 version, gcc 4.1.3 20070718, 2.6.22-8-generic?

here is the error msg:
{{{
r/src/nv/nvacpi.c:15:
include/asm/compat.h: In function ‘compat_alloc_user_space’:
include/asm/compat.h:202: warning: pointer of type ‘void *’ used in arit
hmetic
ld -m elf_x86_64 -r -o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg
1/usr/src/nv/nvidia.o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/us
r/src/nv/nv-kernel.o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr
/src/nv/nv.o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/
nv-vm.o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/os-ag
p.o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/os-interf
ace.o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/os-regi
stry.o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/nv-i2c
.o /media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/nvacpi.o
ld: Relocatable linking with relocations from format elf32-i386 (/media/tmp/
software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/nv-kernel.o) to format e
lf64-x86-64 (/media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/
nvidia.o) is not supported
make[3]: *** [/media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv
/nvidia.o] Error 1
make[2]: *** [_module_/media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/us
r/src/nv] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
-> Error.
:

}}}

[macmatt]

How to lose a Mac's original UI beauty....

Install Ubuntu...

UGHH!!!!:(

Does Linux community not "get it" like us Mac OS users do?. I want my car to drive, but I don't wanna stop every 1/2 mile to repair it!. Mac OS X... yummy, powerful AND simple to run. When Leopard comes, you bunnies better get ya cloning hats on, like you did with Expose ;)

[pepe#]

ld: Relocatable linking with relocations from format elf32-i386 (/media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/nv-kernel.o) to format elf64-x86-64 (/media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/nvidia.o) is not supported

Looks like you are trying to combine 32bit and 64 bit. Both files are from x86, so maybe your system is x64?


> How to lose a Mac's original UI beauty....

Some day, somebody need to explain to me how in the world people came up using a mouse-driven GUI for laptops. Devices which don't even have a mouse most of the time..

And...you know...some people need more that chat and paint. Have you ever tried to use your home/end keys in the console? Or partitioning your drives with OSX' fdisk?

But I agree that OSX is nice for painting. Of course, a pencil would do, too...

[macmatt]

ld: Relocatable linking with relocations from format elf32-i386 (/media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/nv-kernel.o) to format elf64-x86-64 (/media/tmp/software/NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/nv/nvidia.o) is not supported

Looks like you are trying to combine 32bit and 64 bit. Both files are from x86, so maybe your system is x64?


> How to lose a Mac's original UI beauty....

Some day, somebody need to explain to me how in the world people came up using a mouse-driven GUI for laptops. Devices which don't even have a mouse most of the time..

And...you know...some people need more that chat and paint. Have you ever tried to use your home/end keys in the console? Or partitioning your drives with OSX' fdisk?

But I agree that OSX is nice for painting. Of course, a pencil would do, too...

You evidently don't "get it" then! lol.

Mouse-driven GUI?. Uhhm most GUIs are, by their very nature, mouse-operated; even Ubuntu - what on earth was that meant to mean?!!.

[pepe#]

Ubuntu is no gui. And yes, ubuntu features many window managers that are not primarily mouse-operated.

Please go back to painting.

[trouble1313]

Folks, don't feed the troll fanbois that are out of their element. You degrade yourselves and feed their foolishness.

-Trouble

[epaulin]

>> Looks like you are trying to combine 32bit and 64 bit. Both files are from x86, so maybe your system is x64?


I'm so stupid, I downloaded x86 32 version driver from NVIDIA site.

Now my Macbook Pro works sweet:

* sound: alsa-driver from CVS
* backlight: pommed 0.18
* wifi: madwifi
* 8600GT: patch from pepe's link

tnx a lot, pepe.

[alephsmith]

pommed now includes the display control code from above in svn rev 346


Thanks pepe#. Works great at my end. Although what is the purpose of wmpomme? Currently it just sits in an irritating window.

Tried compiling alsa with the patch but can't seem to get it working.

Gimlis nvidia patch works well.

One thing that keeps bugging me is that if I kill X (crtl+alt+bksp) I am faced with my desktop background rather than restarting gdm like it used to. I have no idea where to go looking to fix the problem. Currently I'm forced to do a hard reboot.

[macmatt]

Ubuntu is no gui. And yes, ubuntu features many window managers that are not primarily mouse-operated.

Please go back to painting.

Did you ever hear of 'Darwin'?. I assume you'd know what that was. If I were putting ANY Linux on my MacBook Pro, it would be Linux Mint; IMHO a vast improvement on Ubuntu, and BASED upon it.

[epaulin]

NVIDIA driver failed toinitialize when I were restart my computer, I look up the dev dir, the nvidia and nvidiactl devices was created, I don't know what I'm doing wrong.


It works when I start the computer and reinstall the nvidia drivers, I assume this is a devfs or udev setting issue, but really don't know how to fix it.

{{{
(**) NVIDIA(0): Enabling RENDER acceleration
(II) NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) NVIDIA(0): enabled.
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module! Please ensure
(EE) NVIDIA(0): that there is a supported NVIDIA GPU in this system, and
(EE) NVIDIA(0): that the NVIDIA device files have been created properly.
(EE) NVIDIA(0): Please consult the NVIDIA README for details.
(EE) NVIDIA(0): *** Aborting ***
(II) UnloadModule: "nvidia"
(II) UnloadModule: "wfb"
(II) UnloadModule: "fb"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found
}}}

[alephsmith]

I had something similar and needed to explicitly stop the nv and nvidia_new modules from loading.

sudo nano /etc/default/linux-restricted-modules-common

changing

DISABLED_MODULES=""
to
DISABLED_MODULES="nv nvidia_new"

[pepe#]

epaulin:
> sound: alsa-driver from CVS

Suppose you mean alsa from cvs(hg, in fact) and patched with https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3242


aleph:
> Although what is the purpose of wmpomme?

Huh? Its made for nextstep-style window managers. They include these little apps in bars: http://malison.org/uploads/Screenshots/2004-11-23-2_1024x768.png

> Tried compiling alsa with the patch but can't seem to get it working.

Wanted to buy chocolate yesterday but all shops were closed.


clueless fanboy:
> Did you ever hear of 'Darwin'?

Nice. Now go back to my first answer and notice that I already gave examples about the amazing usablity of the BSD subsystem in OSX.

And yes, I have no doubt you would install linux-mint. But with your requirements(painting, 3d eye-candy, clueless), you should just stay with OSX. And please don't assume everyone has your requirements. I'll recommend OSX to my girlfriend(painting, chat,..) at any time, its a great solution there. But please, not for me...

[cyberdork33]

Please stop. there is no need to argue about this.

[ahaller]

Still another thing, I installed Ubuntu with lilo bootloader (I read somewhere that linux boots only with it).. but I can boot with splashscreen and framebuffer with a good resolution.. Does anyone boot linux with grub? ..and can give me a hand to configure it?:)
Thanks!

hi. i think the lilo-only thing has been solved some time ago.
i installed feisty on the rev. 2 MBP and gutsy on the rev. 3 / santa-rosa just with the alternate cd (after having installed refit).
so i always use grub. but i cannot tell you, how to change from lilo to grub.
my assumption would be just to install the grub package, and the do a grub-install, but i really don't know.

maybe these pages help
https://wiki.ubuntu.com/MacBookProFeisty
https://help.ubuntu.com/community/GrubHowto

[pliz]

Guys, was anyone successful with suspend/resume on MBP 3? My machine goes to sleep without a problem, but I do not have both screen and keyboard alive after it wakes up. Can log into it by ssh with no problem though.

If you have suspend working at your machine can you share the steps you took, please?

[epaulin]

alephsmith :
>> I had something similar and needed to explicitly stop the nv and nvidia_new modules from loading.

>> sudo nano /etc/default/linux-restricted-modules-common
>> DISABLED_MODULES="nv nvidia_new"

tnx, this works.

pepe#:
>>Suppose you mean alsa from cvs(hg, in fact) and patched with https://bugtrack.alsa-project.org/al...ew.php?id=3242

No, My system is gutsy, what I'm doing is compiled alsa-driver component which sync from alsa cvs, and with the option you post it before:
options snd_hda_intel model=w2jc

I haven't alsa bug track account yet, so I don't what exactly the bug is.

[pepe#]

> If you have suspend working at your machine can you share the steps you took, please?

- do it manually
- and again
- try something else
- ...
- find out that you need to remove some modules like alsa and madwifi and that you need to switch to console and back to X two times and load usb afterwards because otherwise you have no keyboard, like posted above

> I haven't alsa bug track account yet, so I don't what exactly the bug is.

Give it a try when you feel like using the headphone output...there's a guest account..

[pliz]

Thanks, pepe#

So I assume you do all the steps with a script? When keyboard is not working switching back and forth between console and X seems problematic. Do you mind sharing the script?

Thanks again!

[Paerez]

Sorry if I am asking something already mentioned ....

I am attempting to install alsa. I have rsynced the alsa-driver and alsa-kernel. I patched alsa-kernel with the patch linked by pepe#.

Then I ran:
./hgcompile --with-cards=hda-intel
sudo make install
sudo modprobe snd_hda_intel model=w2jc

and I got:
FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.20-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)

modprobe without the card specified returns the same thing.

dmesg | tail:
[ 1223.200000] snd_hda_intel: Unknown symbol snd_hda_parse_generic_codec

Did I miss something?

[Dhjiz]

Hi,

I think maybe I've found another workaround for the Nvidia drivers.

Everytime I reboot now, the drivers launches withouth any problem and I can launch Beryl after that.

I run under a MacBook Pro 15", 2,2ghz, with the TwinView mode activated.

Here's my xorg.conf file :

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder3) Wed Jun 13 18:40:26 PDT 2007

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder3) Wed Jun 13 18:39:30 PDT 2007
# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
#Section "InputDevice"
# Driver "wacom"
# Identifier "stylus"
# Option "Device" "/dev/input/wacom"
# Option "Type" "stylus"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
#EndSection
#Section "InputDevice"
# Driver "wacom"
# Identifier "eraser"
# Option "Device" "/dev/input/wacom"
# Option "Type" "eraser"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
#EndSection
#Section "InputDevice"
# Driver "wacom"
# Identifier "cursor"
# Option "Device" "/dev/input/wacom"
# Option "Type" "cursor"
# Option "ForceDevice" "ISDV4" # Tablet PC ONLY
#EndSection

Section "ServerLayout"

# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section "Files"

# path to defoma fonts
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection

Section "ServerFlags"
Option "Xinerama" "0"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
Option "XkbOptions" "lv3:rwin_switch"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
HorizSync 28.0 - 72.0
VertRefresh 43.0 - 60.0
Option "DPMS"
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "Apple Color LCD"
HorizSync 30.0 - 75.0
VertRefresh 60.0
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "ViewSonic E651-3"
HorizSync 30.0 - 56.0
VertRefresh 50.0 - 120.0
EndSection

Section "Device"
Identifier "nVidia Corporation NVIDIA Default Card"
Driver "nvidia"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600M GT"
EndSection

Section "Device"
Identifier "Videocard1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600M GT"
BusID "PCI:1:0:0"
Screen 1
EndSection

Section "Screen"
Identifier "Default Screen"
Device "nVidia Corporation NVIDIA Default Card"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1440x900" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1440x900" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1440x900" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1440x900" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1440x900" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1440x900" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "Screen1"
Device "Videocard0"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "DFP: 1440x900 +0+0; DFP: 1024x768 +0+0; DFP: 800x600 +0+0; DFP: 640x480 +0+0"
EndSection

Section "Screen"

# Removed Option "TwinView" "0"
# Removed Option "metamodes" "CRT: 1024x768_60 +0+0"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
Option "TwinView" "1"
Option "metamodes" "CRT: 1024x768_60 +0+0, DFP: 1440x900 +1024+0; DFP: 1024x768 +0+0; DFP: 800x600 +0+0; DFP: 640x480 +0+0"
EndSection

Section "Extensions"
Option "Composite" "Enable"
EndSection



Here's the configuration :

MacBook Pro 15", 2,2ghz with the lateste nvidia drivers obtained via the Envy script. I'm running under Kubuntu Feisty Fawn, and I used the TwinView mode from the Nvidia Settings gui. I configured everything with the gui and I copy and paste the code from the gui to my xorg.conf file (because the nvidia-settings aren't launch as root, so it cannot write directly to the file). The other screen is a ViewSonic E651 located at the left of my laptop, with a resolution of 1024x768.

Everytime I boot under Kubuntu, after the splash screen, I can see a broken nvidia logo (the logo isn't recognizable) and after login, I can enjoy 3D desktop directly. I didn't patch the drivers.

Under Max OS X, sometimes I use the dual screen mode, and sometime I don't, and when I reboot under Linux I always get the nvidia drivers working.

EDIT: you may say what happens when I start Linux without the other screen ? Xorg consider I'm using a huge resolution (2464x900) as if the second screen was present. But, because the CRT screen is at the left, every window I launch doesn't appear on the screen but in the hidden part. But the driver still launches successfully.

EDIT2: I installed the 386 version of Ubuntu, not the AMD64 one.

[pepe#]

> Did I miss something?

You need to reboot.

hehe, just kidding. Try to reload all alsa modules...

> When keyboard is not working switching back and forth between
> console and X seems problematic.

But does not matter, because if it would work, you'd still have no input devs..

kbd and touchpad are usb devices, you need to take care that the corresponding drivers are either unloaded and reloaded correctly or surrive the suspend. My script does not reload usb drivers, so they probably can surrive. Stil, it may be that I oversaw some obscure script shipped with the distro. I'm sure I've seen the default acpi scripts to reload usb. So try it manually first and/or be sure to disable possible interference..

/etc/init.d/pommed stop
/etc/init.d/alsasound stop
/etc/init.d/alsa unload
ifconfig eth1 down
ifconfig ath0 down

rmmod snd_page_alloc snd soundcore
rmmod sky2 i2c_i801 ohci1394 ieee1394
rmmod ath_pci ath_hal ath_rate_sample wlan_scan_sta wlan

chvt -t 9
echo mem > /sys/power/state
chvt -t 7
chvt -t 9
chvt -t 7


/etc/init.d/alsasound start
/etc/init.d/pommed start
modprobe snd_hda_intel
modprobe ath_pci
modprobe sky2

this is probably not all needed, firewire and basic snd modules may surrive too..

[Paerez]

pepe - after installing i did reboot, since I wasn't sure what modules and init scripts had to be reloaded. And I get the same errors when i modprobe.

People do have sound working right?

[trouble1313]

I can confirm that it does work, at least based on the day I checked out the code. I compiled it, re insmod'd it with the module option and all was well. Now if I understand correctly, the more recent posts have alluded to not needing the kernel option and better/full support of the devices themselves.
-Trouble

[bluemoth]

Hi,

I tried to reinstall alsa both unpatched and patched from hg and get the unknown symbol errors:
>> modprobe snd_hda_intel model=w2jc
FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.20-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)

So either something has changed since the fi was posted or I'm dong the same mistake. It would be nice to hear from someone who successfully go sound going this way recently.

Just to update the curious, I was able to install the feisty desktop (32bit) using the "all_generic_ide" boot option. Got graphics going using the nv driver and got the wifi going using madwifi.

I plan to wait for the nvidia drivers and am still trying to get sound going. I also plan to test gutsy tribe 4 when it's released.

Cheers.

[pepe#]

>> modprobe snd_hda_intel model=w2jc
FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.20-16-generic/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)


what does dmesg say?

With the patched alsa tree, you don't need the model=w2jc option, a new model mbp3 is introduced with the patch and the device is recognised automatically.

And please check that the provided patch applies correctly, that you download the newer of the two postet patches and that you followed the instructions for patching.

[Paerez]

[EDIT] I got it by doing this:

then I went into a temp directory I made and typed:
wget https://bugtrack.alsa-project.org/alsa-bug/file_download.php?file_id=2097&type=bug
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-kernel .
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-driver .
cd alsa-kernel
patch -p1 < ../patch_realtek.c.diff
cd ../alsa-driver
./hgcompile --with-cards=hda-intel --with-card-options=all
sudo make install
sudo /etc/init.d/alsasound restart
sudo modprobe snd-hda-intel

Then I turned up PCM and Front in gnome's volume manager. and I got sound out the front. Can't figure out headphones though ...

It was the hgcompile option that was messing it up for me the first time.

[pepe#]

You have to use a kernel with fully modular alsa support. Anyway..

cd /usr/src/modules/
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-driver alsa
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-kernel alsa
[download patch_realtek.c.diff (https://bugtrack.alsa-project.org/alsa-bug/file_download.php?file_id=2097&type=bug)]
cd alsa/alsa-kernel
patch -p1 < ../../patch_realtek.c.diff
cd ../alsa-driver
./hgcompile
make
make install
/etc/init.d/alsasound stop
lsmod [verify all snd modules are unloaded]
modprobe snd-hda-intel

[Paerez]

ok now how do I get my headphones to play?

EDIT: Also anyone know how to get two-finger (or three finger, I don't care) right click working? Here is an excerpt from xorg.conf:

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "SHMConfig" "on"
Option "AccelFactor" "0.1"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "MaxTapTime" "150"
Option "MaxTapMove" "220"
Option "MaxDoubleTapTime" "180"
Option "LockedDrags" "on"
Option "VertTwoFingerScroll" "1"
Option "TapButton1" "1"
Option "TapButton2" "2"
Option "TapButton3" "3"
Option "Emulate3Buttons" "true"

EndSection

[scottptsn]

Hi guys I am a brand new Linux user (as in one week to date exactly). I have a new 15’ macbook pro that I have installed the 64bit Ubuntu onto. Thanks to reading these forums I have the wifi, CD, and touchpad working. I am now trying to get the graphics fix to work. I am trying to use the fix pepe posted. Everthing worked until I got to the last simple command. “./nvidia-installer –aN”. I get a “No such file or directory” error. I am root and the group and permissions look right and it is an executable file. Even ls shows that it’s there, but I can’t run it. A co-worker thought it could be a problem with the shell and had me switch from /bin/bash to /bin/ksh however the problem is still there. I am stuck so if anyone has any ideas I would be very grateful. If you need any more info just ask and please remember I am a noob J

[Paerez]

ok well here are a couple things to check. I am covering ALL the bases, so please don't be offended if you think I am being condescending:

1) Are you in the directory with the file? If you type "ls" (thats an L), it should show the name of the script.

2) Is the script executable? if you type "ls -l nvidia-installer" there should be some Xs in the permissions.

3) Is the name right? Did you spell it correctly, correct capitalization, etc

If none of that works, post the output of "ls -l" so we can see the file.

EDIT:
here is my ls -l:
total 236
-r--r--r-- 1 nick nick 5725 2007-06-13 21:59 LICENSE
-rwxr-xr-x 1 nick nick 214488 2007-06-13 21:59 nvidia-installer
-rw-r--r-- 1 nick nick 8076 2007-06-13 22:26 pkg-history.txt
drwxr-xr-x 8 nick nick 4096 2007-06-13 21:59 usr

[scottptsn]

No offense taken I am new, but I did already try those things so here is my ls –l

-r—r—r— 1 root root 5725 2007-06-13 18:59 LICENSE
-rwxrwxrwx 1 root root 214488 2007-06-13 18:59 nvidia-installer
-rw-r—r-- 1 root root 8076 2007-06-13 19:26 pkg-history.txt
drwxr-xr-x 8 root root 4096 2007-06-13 18:59 usr

The reason the file is rwx to all is that I changed the permissions just to make sure.

[Paerez]

OK and it is a single . before the /?

So its:
./nvidia-installer

not
../nvidia-installer?

Also the terminal has a nice auto-complete feature done by hitting tab. So if you type in ./ and then hit tab twice it will show you everything you could type after that.

Try typing ./n and then hitting tab and see if it shows nvidia.

I've got to admit this is weird :-D

[cyberdork33]

OK and it is a single . before the /?

So its:
./nvidia-installer

not
../nvidia-installer?

Also the terminal has a nice auto-complete feature done by hitting tab. So if you type in ./ and then hit tab twice it will show you everything you could type after that.

Try typing ./n and then hitting tab and see if it shows nvidia.

I've got to admit this is weird :-D

.. means back a directory, . is the current directory. So, if you are in the terminal at ~/Desktop/myfolder you could run a script in your home folder by typing "../../myscript" you put the ./ in front a script because bash will get confused sometimes. You can also use the script's command to run it. This is often done for perl scripts and the like more often than bash scripts:

$ perl myperlscript.pl

[scottptsn]

That’s very cool about the tab I am sure I will use that a lot and yes it’s ./ that I am using. I wonder if maybe I installed it wrong or something and it’s trying to access something that’s in the wrong place or there is a dependency I don’t have?

[Dieter@be]

Hi,

I think maybe I've found another workaround for the Nvidia drivers.

Everytime I reboot now, the drivers launches withouth any problem and I can launch Beryl after that.

I run under a MacBook Pro 15", 2,2ghz, with the TwinView mode activated.

Here's my xorg.conf file :

(...)
.

Hello Ubuntu people. I don't use ubuntu (my boxes run Arch and Gentoo, the servers I administer run Debian) but I would like to participate in this discussion, and more importantly I want to confirm that the xorg.conf posted by Dhjiz works ! It uses an external display at the left, and the mbp display is the right. And like he said, the nvidia logo is borked but after that everything looks fine.

I have the binary drivers version 100.14.11-4, and I run a i686 system (similar to i386 but with some optimizations for newer architectures not important in this context). My xorg is version 11R7.0-1
I didn't patch anything or did no fancy tricks like running with another driver first. I do have to say I took the xorg.conf exactly the way it was, so I'll need to change settings to my likings (eg: I don't use an external display so I can hope to alter the config without it ceasing to work), and I'll do some more testing (e.g. rebooting, booting OSX in between, I could even try an opengl game but my time is limited right now)

edit: first test results:
rebooting into Linux seems to give no problems
trying to get rid of second screen: setting TwinView to 0 gives the "crazy colors" on the external screen, no image on the mbp screen. Gonna try some more methods to fix it , I'm even considering leaving the twinview as it is and configuring my DE to not use the left space

[Paerez]

Here is my twinview xorg.conf.

[pepe#]

> ok now how do I get my headphones to play?

It should just work if you plugin HP into the HP output. The speakers will automatically be muted and the HP out will be unmuted.

Note that the line-in can still be switched to lineout and has seperate volume control, so your girlfriend can listen, too.

> EDIT: Also anyone know how to get two-finger (or three finger, I don't care)
> right click working? Here is an excerpt from xorg.conf:

> Option "Emulate3Buttons" "true"

This one is not in my config and not in the synaptics manpage. Other than that I can see no errors. TwoFinger or even Threefinger tapping with linux was very bitchy, so I decided to use the corner-buttons, which still sucks, but less..

I don't know if the appletouch module from mactel-patches is required. I have it.

You also want 'GrabEventDevice' so you can define an additional generic mouse device for usb mice to work.

[trouble1313]

Yeah I have to concur that the trackpad sucks. I've also gone to the corner or an external mouse for right clicking. If I could just do the 2 finger plus button click I'd be a happy man. Anyway, I took the emulate3buttons out as well and it does not affect the situation. Really, make sure you have Gsynaptics or QSynatpics or whatever uninstalled. Until I got rid of GSynatpics, things were screwy and the clicking didn't work.
-Trouble

[scottptsn]

I have been doing some more researcher on my problem and the only thing I can find is that if the binary is hard coded to point to an object and that object is not were it is supposed to be then you can get my error. I have no experience with editing binary is there anyway some one could help me out and let me know if the file points to something that maybe I moved or didn't install in the correct place? Thanks for all your help guys.

I got my track pad working with the previously discussed qsynaptics and the xorg edit and it works great I use two finger tap for right click and the circle drag for scrolling.