Macbook Pro- Santa Rosa

[cyberdork33]

I'm trying to install the free nv driver in Kubuntu Gutsy Tribe 5, and it keeps complaining about not finding xorg-server, xproto, or fontsproto. Does anyone know where I can find them?

Ok, I know I sent you over here, but I think I found the package name of a couple:
I think you need x11proto-fonts-dev and maybe x11proto-video-dev

As for the xorg-xserver, i think you just need the dev package (as you should have the actual xorg-xserver package installed by default). So install these, then try compiling again. If you still have an error in the configure, then post back.

sudo apt-get install xserver-xorg-dev x11proto-fonts-dev x11proto-video-dev

[violinmandan]

Ok, I know I sent you over here, but I think I found the package name of a couple:
I think you need x11proto-fonts-dev and maybe x11proto-video-dev

As for the xorg-xserver, i think you just need the dev package (as you should have the actual xorg-xserver package installed by default). So install these, then try compiling again. If you still have an error in the configure, then post back.

sudo apt-get install xserver-xorg-dev x11proto-fonts-dev x11proto-video-dev

Grrr..... you were right about those packages, but....
Now it wants some more:

checking for XORG... configure: error: Package requirements (xorg-server >= 1.2 xproto fontsproto randrproto renderproto videoproto xextproto) were not met:

No package 'randrproto' found
No package 'renderproto' found
No package 'xextproto' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XORG_CFLAGS
and XORG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


Any of those ring a bell?

[cyberdork33]

Grrr..... you were right about those packages, but....
Now it wants some more:

Unfortunately this is probably going to be a tedious back ad forth thing. You can look in the readme, and make sure that all the dependencies are installed, or you can search for the missing packages every time you try to compile. The -dev packages are those libraries needed to compile against.

If you do:
sudo aptitude search proto you will see that there are several x11 proto packages. You can look for the right one (look for one that is close) and install it then try again. Again, I am not sure that the nv module will even work on your hardware, so this could be all for naught... good luck.

[Bazou]

At the risk of being condescending: have you checked that output volume in alsa mixer? When I compiled I remember it telling me about the volume being automatically set to mute.


Yes of course ;)

All channels are unmuted and the volume is set to the max.

Any other idea?

[salbo]

Unfortunately the driver install complains about the wrong run level from single user mode. you need to stop your X session. From Gnome do this:

sudo /etc/init.d/gdm stop

If you use KDE, replace gdm with kdm.

You also don't need to store your source in /usr/src/modules/. They modules can be built from ~/ just as easily.

Thanks. I got one step further now.

I get to applying the patch, by following the links. But where does the "nvdriver.conf" file come from?? I suppose I have to download it somewhere.

[alephsmith]

So you are installing the free nv drivers?

If you are you need to get it from git if you want it to work.

AFAIK you only need to apply a patch to the non-free drivers.

[Mister.K]

I've just compiled the 2.6.22.5 kernel on my MBP SR, and my restricted manager ask me... no... show me an error and ask me to install "mactel-linux-patches-2.6.22.5 drivers"... anyone noticed the same thing ?

[cyberdork33]

I've just compiled the 2.6.22.5 kernel on my MBP SR, and my restricted manager ask me... no... show me an error and ask me to install "mactel-linux-patches-2.6.22.5 drivers"... anyone noticed the same thing ?

It is just how the restricted drivers manager works. it is expects a *drivers package that has the same name as your kernel, which if you are using a custom kernel, will not exist. you can disable the manager, as it will give errors unless you use the normal ubuntu kernels.
In addition, if there were any drivers enabled in the restricted drivers manager, you will likely need to recompile them, linking them to your new kernel.

[violinmandan]

Again, I am not sure that the nv module will even work on your hardware, so this could be all for naught... good luck.

Well, I finally installed them and switched off the vesa driver, and it works!... sort of.
The video displays, but has a frame rate of about 1.5 fps and sometimes stops altogether.
Is there anything that can improve this, or is this always an issue with the free driver?

Also, I'm trying to compile stepmania, but it says it can't find an OpenGL library. Any idea where I could get my hands on that?

[salbo]

So you are installing the free nv drivers?

If you are you need to get it from git if you want it to work.

AFAIK you only need to apply a patch to the non-free drivers.

Thanks again for helping me out.

I've downloaded the newest nvidia driver as it says on the front page of this forum.

Can you please give me precise instructions on what I need to download and how to install it.

I've been using Linux for a few years, but I've never had to deal with problems like these before, so I don't know what to do.

Thanks again.

[alephsmith]

Download the lastet nvidia driver and the patch (to ~/ if it pleases you)

sh NVIDIA-Linux-x86-100.14.11-pkg1.run -x
cd NVIDIA-Linux-x86-100.14.11-pkg1/usr/src/
patch -p0 < ../../../nv_macbook.diff

stop X


cd NVIDIA-Linux-x86-100.14.11-pkg1
./nvidia-installer -aN

follow the prompts then restart.

That should be it.

[cyberdork33]

Well, I finally installed them and switched off the vesa driver, and it works!... sort of.
The video displays, but has a frame rate of about 1.5 fps and sometimes stops altogether.
Is there anything that can improve this, or is this always an issue with the free driver?

Also, I'm trying to compile stepmania, but it says it can't find an OpenGL library. Any idea where I could get my hands on that?

I think it is more of an issue with the very new graphics hardware in the Santa Rosa Macbooks, and still working out bugs. Someone else here may be able to give you more info.

Are you trying to compile for any partitcular reason? why not get a deb package... that should take care of any dependencies automatically... http://www.getdeb.net/app.php?name=Stepmania

[Bazou]

Hi everyone,

Can someone help me to have sound please?

I follow exactly these steps, all successfully:

rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-driver alsa
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-kernel alsa
cd alsa/alsa-driver
./hgcompile --with-cards=hda-intel
make;make install
/etc/init.d/alsasound stop
modprobe snd-hda-intel

With alsamixer the channels are at max and unmuted. My channels are:
headphone - PCM - Front - Surround - Line - Mic - IEC958 - 3 inputs

I tried the kernels 2.6.20-16-generic and the 2.6.22.5 with mactel patches.

I use alsa version 1.0.14. Is that your version?

With this last kernel my dmesg output is (when I load snd-hda-intel):

[ 1944.697245] PM: Adding info for No Bus:timer
[ 1944.724891] PM: Adding info for No Bus:seq
[ 1944.784005] PM: Adding info for No Bus:sequencer
[ 1944.784023] PM: Adding info for No Bus:sequencer2
[ 1944.829638] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 20 (level, low) -> IRQ 20
[ 1944.830480] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[ 1944.837344] hda_codec: Unknown model for ALC882, trying auto-probe from BIOS...
[ 1944.845170] PM: Adding info for No Bus:pcmC0D2c
[ 1944.845367] PM: Adding info for No Bus:pcmC0D1p
[ 1944.845520] PM: Adding info for No Bus:pcmC0D1c
[ 1944.845675] PM: Adding info for No Bus:adsp
[ 1944.845829] PM: Adding info for No Bus:pcmC0D0p
[ 1944.845980] PM: Adding info for No Bus:pcmC0D0c
[ 1944.846137] PM: Adding info for No Bus:dsp
[ 1944.846277] PM: Adding info for No Bus:audio
[ 1944.846427] PM: Adding info for No Bus:hwC0D0
[ 1944.846573] PM: Adding info for No Bus:controlC0
[ 1944.846740] PM: Adding info for No Bus:mixer

I also use KDE, and try "auto detection" and "alsa" as sound system. Something else must be set?


What are the exact step you did? did I forget something?

[violinmandan]

I think it is more of an issue with the very new graphics hardware in the Santa Rosa Macbooks, and still working out bugs. Someone else here may be able to give you more info.

Are you trying to compile for any partitcular reason? why not get a deb package... that should take care of any dependencies automatically... http://www.getdeb.net/app.php?name=Stepmania

I'm trying to compile it because the precompiled versions are only available for the i386. I'm using an i686.
Isn't there some way to get 32-bit binaries to work on a 64-bit system (without installing a 32-bit OS)? I can run a 32-bit windows binary through wine, but it seems a 32-bit Ubuntu binary won't work...

[cyberdork33]

I'm trying to compile it because the precompiled versions are only available for the i386. I'm using an i686.
Isn't there some way to get 32-bit binaries to work on a 64-bit system (without installing a 32-bit OS)? I can run a 32-bit windows binary through wine, but it seems a 32-bit Ubuntu binary won't work...

i386 vs i686 is not the same as 32bit vs 64bit.
Compiling anything is going to require pretty much the same procedure as previously, look at the error, and try to find the matching dependency. You will likely find many other packages that are 32bit only as 64bit has not taken off on the desktop.

[ico]

Hi all,

I am having issues with WPA wireless on my Santa Rosa MBP (17") running Ubuntu Studio. Tried getting the newest as well as recommended version of madwifi driver. Tried wcid and nm-applet although I do get a list of available networks (wcid works a bit better but has a buggy systray applet). I need the wireless to run WPA/WPA2 enabled. Hence, could someone please post their steps on how they got their ath0 wifi working? Should I also install latest wpasupplicant from CVS as well?

Many thanks!

Ico

[redrum]

Hi Guys,

Does anyone succeeded in making lm-sensors working with feisty 32-bits ?

[pepe#]

Bazou: You need to make;make install. You can't use snd-hda-intel of alsa version XY with some other kernels alsa subsystem. make install will remove all alsa modules from your *running* kernel and install the compiled ones. Then unload all old modules and modprobe snd_hda_intel.

Oh, and:

> Unknown model for ALC882, trying auto-probe from BIOS.

This means you either have a different sound chip from all other SR MBP users or you're not using the current alsa tree. If you supply the modprobe command with "model=wj2c", old versions of alsa will work partially.
If you have the correct alsa version, snd_hda_intel will auto-detect a mbp model.

[l3th0x]

Hi,

When I try to patch in alsa-kernel, this happens:

Reversed patch detected! Assume -R

Hunk #3 FAILED at 10608

(all to eight are succeded, except this.). I have not patched it before, so.. why is this happening? is there a manually form to patch it? or a method that I could unpatch it (I am a newbie..sorry if I said one or too much things that are not correct) .I´m using a 2.6.20-16-generic kernel.

Thank you very much. And thank you to this forum, it´s great!!:KS

Ah, OMT, I have too the "Unknow model for ALC882. Three weeks ago, when I made a clean ubuntu install all worked fine (sound included), but now, with the same (I swear..) clean install, the sound doesn´t work. (I read all the messages in the forum, and tried everything, but have not had results)

Thank you very much again.

[redrum]

I'm not sure you still need to patch alsa kernel. I'm using a non patched alsa kernel, the sound is working just find without a low sound.

[pepe#]

> I read all the messages in the forum, and tried everything, but have not had results

You missed the one where I wrote that the alsa patch is included in the current alsa tree. Current alsa should detect a new model 'mbp' automatically.

[l3th0x]

Hi,
Thank you for the answer.

I read it. But my alsa just not work. I do not why..that is why I am open to all possibilities..:(

Thnk you.

[pliz]

after installing unpatched alsa try the following:

sudo rm /lib/modules/2.6.22-10-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko
depmod

then sudo modprobe snd-hda-intel

This works for me. Alsa installs its working driver in a different place where Ubuntu's disfunctional driver is place and the disfunctional driver takes precedence somehow.

Cheers!

[l3th0x]

Hi,

Thank you for your answer, but still not luck..

I have compile my new gutsy kernel with the mactel patches...and still nothing..

but I think that is something about what you said.

When I restart, a message:

cannot locate resource region 5 ... appear after grub.

In the meantime now I am using the /etc/modprobe.d/options:

options snd_hda_intel model=w2jc solution, and now that works...but without the mic, headphones...

my alsa is there due to :

aplay -l
tarjeta 0:Intel [HDA Intel], dispositivo 0: ALC882 Analog [ALC882 Analog]
Subdispositivos: 1/1
Subdispositivos #0:subdevice #0
tarjeta 0:Intel [HDA Intel], dispositivo 1: ALC882 Analog [ALC882 Analog]
Subdispositivos: 1/1
Subdispositivos #0:subdevice #0

And ubuntu is detecting the presence of my soundcard :

lspci -v

00:1b.0 Audio Device: Intel Corporation 82801h (ICH8 Family) HD Audio Controller (rev 3)
Subsystem: Apple Computer Inc. Unknown device 00a0
Flags: bus master, fast devsel, latency 0, IRQ 20
Memory at 9b500000 (64 bit,n-p) size 16
capab. access denied.

so, now..I do not know,
I am reading google...:(

Thank you very much

[Bazou]

Bazou: You need to make;make install. You can't use snd-hda-intel of alsa version XY with some other kernels alsa subsystem. make install will remove all alsa modules from your *running* kernel and install the compiled ones. Then unload all old modules and modprobe snd_hda_intel.

Oh, and:

> Unknown model for ALC882, trying auto-probe from BIOS.

This means you either have a different sound chip from all other SR MBP users or you're not using the current alsa tree. If you supply the modprobe command with "model=wj2c", old versions of alsa will work partially.
If you have the correct alsa version, snd_hda_intel will auto-detect a mbp model.

Hi pepe,

As I wrote, I did make && make install with a synced alsa-tree.

after installing unpatched alsa try the following:

sudo rm /lib/modules/2.6.22-10-generic/ubuntu/media/snd-hda-intel/snd-hda-intel.ko
depmod

then sudo modprobe snd-hda-intel

I also tried:
rm /usr/src/linux-2.6.22.5/debian/linux-image-2.6.22.5-mactel/lib/modules/2.6.22.5-mactel/kernel/sound/pci/hda/snd-hda-intel.k

but nothing. I still have the same dmesg message.

I think that I have a very very low sound, but so low that i'm not event sure of it.

Discouraging...

[pepe#]

l3th0x...please follow this, check if the commands are successful, do everything as root(sudo bash)

boot your favorite kernel.
remove or disable the current alsa configuration in ubuntu, eg your options-entry for modprobe.
pliz said ubuntu may have drivers in strange locations, we find them with:

find /lib/modules/$(uname -r)/ -name snd\*

Delete *all* alsa modules. run depmod -a. try to load alsa, it should fail. eg modprobe snd-hda-intel. Verify via lsmod that no alsa-stuff is loaded.

If you deleted the alsa source tree, rsync again:
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-driver alsa
rsync -avz --delete rsync://alsa.alsa-project.org/hg/alsa-kernel alsa

cd alsa/alsa-driver
./hgcompile --with-cards=hda-intel
make;make install
depmod -a (just for fun)
modprobe snd_hda_intel

'dmesg' should report >>hda_codec: model 'mbp3' is selected<<

If it doesn't, use model=mbp3, this overrides auto-detection. If the driver still uses auto-detection or fails, you are still using some old alsa driver instead of the compiled one. Find out why.

You said you compiled the kernel yourself. Verify that alsa is configured as a module and that you are loading the correct kernel.

edit: make sure to use the above rsync URL, not the one mentioned one the alsa website, they are out of sync.
edit2: very low volume is typical for the w2jc model. speakers work and you can use the lineIN as HP-out by switching the 2ch/6ch mixer widget.


advertisement:

My wiki page still has all the latest info on what works and how to do it. No distribution-specific stuff as this would fill a lot of pages. If someone manages to get audio recording or appleIR to work, please tell us. https://cbg.dyndns.org/wiki/ReadingCorner/LinuxOnMacbookPro

[Bazou]

thanks for your help pepe.

As I got the same error, here are the result of your steps:

find /lib/modules/$(uname -r)/ -name snd\*
/lib/modules/2.6.22.5-mactel/kernel/sound/pci/hda/snd-hda-intel.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-timer.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-page-alloc.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/oss/snd-mixer-oss.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/oss/snd-pcm-oss.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-hwdep.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/seq/snd-seq-midi-event.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/seq/oss/snd-seq-oss.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/seq/snd-seq.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/seq/snd-seq-device.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-pcm.ko
/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-rtctimer.ko

root@MACKIE:/usr/src/modules/alsa/alsa-driver# rm /lib/modules/2.6.22.5-mactel/kernel/sound/pci/hda/snd-hda-intel.ko
root@MACKIE:/usr/src/modules/alsa/alsa-driver# rm /lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-timer.ko

(etc...)

root@MACKIE:/usr/src/modules/alsa/alsa-driver# find /lib/modules/$(uname -r)/ -name snd\*

root@MACKIE:/usr/src/modules/alsa/alsa-driver# depmod -a

root@MACKIE:/usr/src/modules/alsa/alsa-driver# /etc/init.d/alsasound restart
Shutting down sound driver: done
root@MACKIE:/usr/src/modules/alsa/alsa-driver# lsmod
Module Size Used by
af_packet 28044 2
ipv6 315752 12
hci_usb 21020 6
rfcomm 46888 6
l2cap 28672 5 rfcomm
bluetooth 63364 15 hci_usb,rfcomm,l2cap
ppdev 11400 0
capability 7176 0
commoncap 9600 1 capability
acpi_cpufreq 10760 1
cpufreq_stats 8288 0
cpufreq_userspace 6048 0
cpufreq_ondemand 10896 1
freq_table 6592 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
cpufreq_conservative 9736 0
cpufreq_powersave 3200 0
ac 7304 0
dock 12392 0
video 20496 0
button 10400 0
sbs 21520 0
container 6528 0
battery 12552 0
nls_iso8859_1 6656 1
nls_cp437 8320 1
vfat 16384 1
fat 60208 1 vfat
nls_utf8 3584 1
ntfs 104288 1
sbp2 27272 0
parport_pc 42024 0
lp 15048 0
parport 44300 3 ppdev,parport_pc,lp
snd_page_alloc 13200 0
nvidia 8115256 26
i2c_core 30208 1 nvidia
sky2 50564 0
shpchp 38300 0
pci_hotplug 36868 1 shpchp
intel_agp 30496 0
tsdev 10752 0
evdev 13184 5
ext3 146832 1
jbd 69104 1 ext3
mbcache 11400 1 ext3
sg 41512 0
sd_mod 32512 4
ide_cd 45344 0
cdrom 41896 1 ide_cd
usbhid 32576 0
hid 33536 1 usbhid
ata_piix 18820 3
ata_generic 10116 0
libata 141200 2 ata_piix,ata_generic
scsi_mod 172856 4 sbp2,sg,sd_mod,libata
ohci1394 38984 0
ieee1394 109656 2 sbp2,ohci1394
generic 7428 0 [permanent]
piix 12292 0 [permanent]
ehci_hcd 39564 0
uhci_hcd 29600 0
usbcore 160304 5 hci_usb,usbhid,ehci_hcd,uhci_hcd
thermal 16528 0
processor 36232 2 acpi_cpufreq,thermal
fan 6920 0
root@MACKIE:/usr/src/modules/alsa/alsa-driver# modprobe snd-hda-intel
FATAL: Module snd_hda_intel not found.

rsync ...
cd alsa/alsa-driver
./hgcompile --with-cards=hda-intel
(etc...)
ALSA modules were successfully compiled.

make
(etc...)
ALSA modules were successfully compiled.

make install
(etc...)
WARNING!!! The mixer channels for the ALSA driver are muted by default!!!
************************************************** ************************
You would use some ALSA or OSS mixer to set the appropriate volume.

depmod -a
modprobe snd_hda_intel

dmesg
(etc...)
[ 7702.759141] hda_codec: Unknown model for ALC882, trying auto-probe from BIOS...

Try with model=mbp3

modprobe snd_hda_intel model=mbp3
FATAL: Error inserting snd (/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for snd
WARNING: Error inserting snd_hwdep (/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-hwdep.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_timer (/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-timer.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd (/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for snd
WARNING: Error inserting snd_timer (/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-timer.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_pcm (/lib/modules/2.6.22.5-mactel/kernel/sound/acore/snd-pcm.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for snd_pcm
FATAL: Error inserting snd_hda_intel (/lib/modules/2.6.22.5-mactel/kernel/sound/pci/hda/snd-hda-intel.ko): Unknown symbol in module, or unknown parameter (see dmesg)


part of dmesg

[ 7846.913605] snd_pcm: Unknown symbol snd_ctl_unregister_ioctl
[ 7846.913734] snd_pcm: Unknown symbol snd_lookup_minor_data
[ 7846.913804] snd_pcm: Unknown symbol snd_ctl_register_ioctl_compat
[ 7846.913901] snd_pcm: Unknown symbol snd_info_create_card_entry
[ 7846.913971] snd_pcm: Unknown symbol snd_power_wait
[ 7846.914064] snd_pcm: Unknown symbol snd_device_free
[ 7846.914188] snd_pcm: Unknown symbol snd_card_file_remove
[ 7846.914258] snd_pcm: Unknown symbol snd_register_device_for_dev
[ 7846.914432] snd_pcm: Unknown symbol snd_device_register
[ 7846.914506] snd_pcm: Unknown symbol snd_info_get_line
[ 7846.919922] snd_hda_intel: Unknown symbol snd_ctl_add
[ 7846.920021] snd_hda_intel: Unknown symbol snd_pcm_new
[ 7846.920113] snd_hda_intel: Unknown symbol snd_pcm_limit_hw_rates
[ 7846.920190] snd_hda_intel: Unknown symbol snd_card_register
[ 7846.920260] snd_hda_intel: Unknown symbol snd_card_free
[ 7846.920330] snd_hda_intel: Unknown symbol snd_pcm_lib_preallocate_pages_for_all
[ 7846.920401] snd_hda_intel: Unknown symbol snd_card_proc_new
[ 7846.920632] snd_hda_intel: Unknown symbol snd_ctl_find_id
[ 7846.920726] snd_hda_intel: Unknown symbol snd_verbose_printk
[ 7846.920855] snd_hda_intel: Unknown symbol snd_ctl_new1
[ 7846.920990] snd_hda_intel: Unknown symbol snd_component_add
[ 7846.921078] snd_hda_intel: Unknown symbol snd_card_new

So, It didn't resolve the problem :(

[pepe#]

You're not using the alsa drivers you installed. Either there are some modules left somewhere or part of alsa is compiled static into the kernel. Everything needs to be a module.

[ilmarw]

I have the exact same issue. Updated the kernel, and now sound doesn't work.

[ilmarw]

Nevermind, did a restart, modprobe now ran fine. Sound OK. Thanks...

[l3th0x]

Jeloou!!

PEPE YOU ARE THE BEST, EVER!! Thank you, thank you very much.:guitar:

and thank you to all this forum, really I have never seen so much support (28 pages!!). You are all incredible!!

Now I am listening portishead, with my headphones :KS, from my very beautiful macbox

I have been "rm -r" the sound/core ones, only, and cannot made it, till now...really, thank you, thank you very much.

About appleir, in google, I am looking now the magarto page..

(yep, I compiled the alsa as module, I did with a 22.6 kernel, too much reading in google, to made it.), so now :

*appleir
*audio-recording. anyone has used CDDOIT??
*pommed keyboard (do not know why but something I have made wrong, due to I do not have iluminated keyboard :(
*my cannot locate resource region pci error message: does not dissapear..
*etc.etc. (I need to read moooree)


Again, arigato gosai mashita!!

[Bazou]

I removed all /sound/core folders and all "find /lib/modules/$(uname -r)/ -name snd\*" files.

My kernel is set with alsa as module.

I don't know why it doesn't work, but I'm now fed up with this, so I leave.

I will maybe try again with the gutsy release.

Anyway, thanks for your help.

bye

[Elv13]

did you tried my patch for the IR, if nobody test it, it will never work.

[DylanRE]

After installing nvidia drivers, madwifi stopped working. I rebooted and it just won't work. I tried modprobe ath_pci and it failed with this message:

FATAL: Error inserting ath_pci (/lib/modules/2.6.20-16-generic/net/ath_pci.ko): Unknown symbol in module, or unknown parameter (see dmesg)

dmesg contains this:

[ 1223.124000] ath_pci: Unknown symbol ieee80211_iterate_nodes
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_vap_attach
[ 1223.124000] ath_pci: Unknown symbol ieee80211_vap_attach
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_ibss_merge
[ 1223.124000] ath_pci: Unknown symbol ieee80211_ibss_merge
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_rate_attach
[ 1223.124000] ath_pci: Unknown symbol ieee80211_rate_attach
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_rate_detach
[ 1223.124000] ath_pci: Unknown symbol ieee80211_rate_detach
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_send_qosnulldata
[ 1223.124000] ath_pci: Unknown symbol ieee80211_send_qosnulldata
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_find_rxnode_debug
[ 1223.124000] ath_pci: Unknown symbol ieee80211_find_rxnode_debug
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_create_vap
[ 1223.124000] ath_pci: Unknown symbol ieee80211_create_vap
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_input_all
[ 1223.124000] ath_pci: Unknown symbol ieee80211_input_all
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_start_running
[ 1223.124000] ath_pci: Unknown symbol ieee80211_start_running
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_vap_detach
[ 1223.124000] ath_pci: Unknown symbol ieee80211_vap_detach
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_announce
[ 1223.124000] ath_pci: Unknown symbol ieee80211_announce
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_chan2ieee
[ 1223.124000] ath_pci: Unknown symbol ieee80211_chan2ieee
[ 1223.124000] ath_pci: disagrees about version of symbol ath_hal_init_channels
[ 1223.124000] ath_pci: Unknown symbol ath_hal_init_channels
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_dturbo_switch
[ 1223.124000] ath_pci: Unknown symbol ieee80211_dturbo_switch
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_crypto_encap
[ 1223.124000] ath_pci: Unknown symbol ieee80211_crypto_encap
[ 1223.124000] ath_pci: disagrees about version of symbol ieee80211_getrssi
[ 1223.124000] ath_pci: Unknown symbol ieee80211_getrssi
[ 1223.124000] ath_pci: disagrees about version of symbol ath_hal_getwirelessmodes
[ 1223.124000] ath_pci: Unknown symbol ath_hal_getwirelessmodes


There's a lot more in dmesg, but I'm not pasting it all- you get the point.

PLEASE help.

[pepe#]

> did you tried my patch for the IR, if nobody test it, it will never work.

I tried it and got nothing. Never used IR before so I may have missed a few things. Does it work for you? How did you set everything up? If you can't test it yourself, I'll be happy to help you with that.


DylanRE: Your problem is probably independent from the nvidia stuff. I messed a lot with nvidia and madwifi and they never interacted. It looks more like you are trying to combine old and new modules. Did you do madwifi-unload before loading the new driver?

[asoare]

Hey can someone pls tell me what has currently NOT been fixed with ubuntu under santa rosa MBP ?

[DylanRE]

DylanRE: Your problem is probably independent from the nvidia stuff. I messed a lot with nvidia and madwifi and they never interacted. It looks more like you are trying to combine old and new modules. Did you do madwifi-unload before loading the new driver?

Well now I can't even get into X (no idea why it stopped working, some error about not having any screens). I'm going to do a complete reinstall of the nvidia and madwifi drivers, and if that doesn't fix it, I'll do a complete reinstall of my system.

[DylanRE]

A reinstall of the driver fixed my video problem, but wifi will not work for me. I tried madwifi-unload, and it unloads ath_hal and wlan, but I still have the same problem when I modprobe ath_pci.

Any ideas?

[pepe#]

> Any ideas?

nothing special. rm -rf your module directory and possible modutil configurations, make;make modules_install, boot new kernel. now try to install nvidia/madwifi from a clean current source tree.. It should just work..


asoare: I don't care about ubuntu, but currently only the IR remote control does not work. Everything else works with a bit tweaking. You have to use a binary nvidia driver and seperate kernel modules for iSight, Sound, Wlan though. If you need paravirtualization, the nvidia module will break s2ram. Battery life is a bit less than with OSX. Did I forget something?

[DylanRE]

pepe, thanks for your help. I now have both the nvidia driver and madwifi installed and running; however, madwifi will not take an IP address. It sees networks but fails to join them. Once again, anyone have any ideas?

[pepe#]

> madwifi will not take an IP address. It sees networks but fails to join them.

what did you try, what did you get? you have to use athX, not wifiX. Also, read the README in the madwifi sources.

[trouble1313]

Just a heads up regarding the alsa module complaining about symbols after compiling. Do exactly what was recommended. Go find the alsa module in your kernel modules directory and delete it....Then do the make install and depmod and you can modprobe it. Just like what was suggested, the make install seems to put the module in a different spot so the modprobe tries to grab the old one. This occurred after I upgraded to Gutsy. It didn't happen with Feisty.

Regarding Gutsy, I can't really recommend bothering to go to it yet unless there's something you REALLY want that's newer. I've found little power improvement (though I haven't recompiled for the tickless kernel). There's also a 'bug'/'feature' where xserver-xgl gets in the way of the nvidia drivers and the ability to use Compiz. It can be worked around but it was annoying until I figured it out.

I've found little else that's changed though my Firebird fonts suck now. Same old gotchas seem to still apply.

-Trouble

[lv1001]

This might sound noobish, but just to spare this to others:

Even though I had no automake installed and the ./configure of alsa gave quite some errors, it ended with "ALSA modules were successfully compiled."

After installing automake, the rest of the alsa-install went just as is should.

Also I have the same thing about madwifi not working after installing/reinstalling/removing/whatever nvidia and even once or twice after trying to install alsa. However, "make install", "modprobe ath_pci" solves this.

LV

[DylanRE]

lv1001, thanks for the insight into madwifi; however, I did get it installed (basically using that same method), it just isn't working properly. Do you have any idea which revision you checked out from svn? I'm beginning to think maybe the revision I have is broken.

EDIT: Grabbed an older rev. and it fixed it. Thank you for your help, everybody (especially pepe)!

[brainiac]

would you mind telling which revision you compiled from? i've got the same issue.

Edit: nevermind... i found another thread here (http://ubuntuforums.org/showpost.php?p=2731459&postcount=25)
which tells me to use this revision here (http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2372-20070525.tar.gz)

will try and report later

[lv1001]

I was using madwifi rev 2695
However, after updating to the newest rev 2704 it still works like charm.

LV

[brainiac]

Are you on feisty or gutsy.... because i think ntwork-manager may be broken... i now get an ip.. but the manager pops up from time to time asking for my password seems like it "forgets" my wpa2 key

[cyberdork33]

Are you on feisty or gutsy.... because i think ntwork-manager may be broken... i now get an ip.. but the manager pops up from time to time asking for my password seems like it "forgets" my wpa2 key
I have noticed it doing that on completely unrelated hardware on gutsy.

[beelzebob]

WARNING - the latest automatic update broke my xserver - now it won't start! I have no idea which part of the update broke it, but just be warned....

[beelzebob]

Just to follow up my last post.... apparently, you need to rebuild/reinstall the nvidia drivers after installing the latest updates.

[DylanRE]

Just to follow up my last post.... apparently, you need to rebuild/reinstall the nvidia drivers after installing the latest updates.

Sometimes my nvidia driver just stops working and I have to rebuild it. So don't be too surprised if something goes wrong again.

[Elv13]

if it is a kernel update, update your modules

[pepe#]

Thanks to Stelian Pop, we now have a working IR remote control. His lircd.conf did not work for me so I had to create one with irrecord. If neither one works for you, please submit your lircd.conf.

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

Does someone know a nice remote control frontend like what apple uses to control multiple apps? Currently checking out mms...

[trouble1313]

Quick question about AppleIR....Can the receiver learn from arbitrary remotes or just the little Apple one that only gives a few functions?

-Trouble

[pepe#]

You should be able to register other remotes, tell me if it works.

stop lircd
irrecord -H macmini -d /dev/usb/hiddev0 myremote
mv myremote /etc/lircd.conf
start lircd

lircd.conf assigns symbols to the signals from the remote. ~/.lircrc assigns symbols to actions in programs.

[Elv13]

mythTV is the best media frontend i think

[[woodstock]]

Did anyone already started a wiki entry dedicated to the new MBP? This thread has become quite long, and the existing entry at wiki.ubuntu.com refers to this thread regarding the Santa Rosa MBP.

[cyberdork33]

;3346856']Did anyone already started a wiki entry dedicated to the new MBP? This thread has become quite long, and the existing entry at wiki.ubuntu.com refers to this thread regarding the Santa Rosa MBP.

No, but that is probably an excellent idea at this point. Although, it might be helpful to wait for Gutsy as that release could change a lot.

[subferno]

;3346856']Did anyone already started a wiki entry dedicated to the new MBP? This thread has become quite long, and the existing entry at wiki.ubuntu.com refers to this thread regarding the Santa Rosa MBP.

Yeah, a new wiki page would definitely help. I just got the MacBook Pro and struggling to get Ubuntu to work so far.

[alephsmith]

I'd contribute to that.
What would be the most transparent page name?

MacBookPro Rev 3
MacBookPro Rev C
MacBookPro SantaRosa

[martinbures]

BTW:
Recent updates in gutsy have audio working out-of-the-box.

[russell.h]

A wiki article would be great. I have had my SR MBP since July, but have been waiting for some of the bugs to get worked out (and to get an external drive to free up some space) before putting Ubuntu on it.

Currently this thread is the top hit on Google for "linux on santa rosa macbook pro", and I would be inclined to suggest that "MacBook Pro Santa Rosa" or "Santa Rosa Macbook Pro" would be the best names for the wiki article.

Anyway, I'm sure I'll be in here begging for assistance sometime next week when I give this installation a shot.

[alephsmith]

I have taken it upon myself to start a Wiki page based on this thread: https://wiki.ubuntu.com/MacBookPro_SantaRosa

Forgive my awful Wiki markup. Please feel free to add/remove stuff.

[Dhjiz]

Hello,

First of all, thanks for making that page on the Wiki, it'll be a great help for many people I think.


But I noticed some things that can be modified in my opnion:

Wouldn't it be a better idea to do the entire nvidia compilation thing in recovery mode, so that there is no gdm to stop. We could juste give the wget commands to download the rights files, then patch install and reboot to get it working easyily.
I read on the Debian website that the aptitude package manager is more recommended now than apt-get, so could we replace apt-get with aptitude in the commands?
Isn't there a better way to install the pommed and gpomme applications, using the package manager, for example using the gutsy packages ( http://packages.ubuntu.com/gutsy/utils/pommed ), or the debian packages?


Thanks.
I plan to edit the wiki page, depending of your answers.

[alephsmith]

1. Some people have problems getting an internet connection from a root terminal, including me. At this stage I think getting them into X first is a better option. Also it'll teach them how to get graphics (i.e. vesa) when nvidia breaks again. I also noticed that the installer script complains about the wrong init level in recovery. While it still works, it may confuse people using the wiki.

2. I use apt-get, and I thought it is the Ubuntu way. As far as the wiki I have no strong feelings either way.

3. Do the Debian packages include patches? I don't know. I personally didn't install pommed in that way, I just nabbed the instructions from the OP.

Please also add things to the wiki page. Including:

Super-drive: piix module (feisty) something else for gutsy
I seem to remember black listing some nvidia-modules, any one remember?
I never got iSight going. Anyone have some easy instructions
Mactel patches? should we mention them?
Remote control. I haven't tried this yet.


PS this was all from memory. I currently don't have Ubuntu on my MacBook Pro, so I must have made some errors in there.

[cyberdork33]

I use apt-get, and I thought it is the Ubuntu way. As far as the wiki I have no strong feelings either way.
There are good and bad reasons to use either. apt-get is fine.

[.bashrc]

Hey, while I would love to (and probably plan on) sifting through the last 32 pages of conversation on MBP santa rosa, I just got one and would love to put Ubuntu on it (had it on my MacBook, former Debian PPC user!). What's the current status of the "project," if you will, regarding MBP support?

Thanks in adv.

[Elv13]

Screen work
power management "work", but it can be better (a lot better)
keyboard light work
sensor all work
remote can work (i did not try)
webcam can work too
cpu clock work perfectly
usb/firewire work
3D accel work at 25% of what this card can do, but it is a bug in the driver, we can do nothing about it exept wait and see, but compiz-fusion work at 7-12 fps when moving transparent+reflection+fish cube
wireless work, but i am not able (and i am not alone) to setup WPA
wired network work
cdrom drive work

:

everything work, and will work better in few month, but i deleted OSX and i am fine under linux, so it is not that bad

[DeepB]

I have taken it upon myself to start a Wiki page based on this thread: https://wiki.ubuntu.com/MacBookPro_SantaRosa

Forgive my awful Wiki markup. Please feel free to add/remove stuff.

Check the renamed page
https://wiki.ubuntu.com/MacBookProSantaRosa

[runelord99]

Ok I know this is probably a stupid point but I had a look in the readme for the nvidia driver "NVIDIA-Linux-x86_64-100.14.11-pkg2.run" and it says that it supports the 8600 gt in the santa rosa MBP's and that it is for 32bit and 64bit linux. has anyone tried this to see if it works? or is it the same driver that needs to be patched?

[alephsmith]

It supports the GPU. Just not on the Macbook Pro. Current nvidia drivers need to be patched, or you must use on of the two other workarounds (dualhead-reboot or nv bait and switch).

[squell]

Regarding the Wiki page that has been setup (https://wiki.ubuntu.com/MacBookProSantaRosa), would it make more sense to refer to the Macbook Pro by its revision number and so therefore change the page name? My reasoning for this is when the next Macbook Pro comes out it will also have a Santa Rosa chipset but the configurations (for graphics, wireless etc) may be different.

[pepe#]

Could you please do wiki-related discussions in $wikipage:talk or so?


> wireless work, but i am not able (and i am not alone) to setup WPA

I've been using WPA2-PSK, i.e. CCMP with PSK. With wpa_supplicant, out of the box.

> power management "work", but it can be better (a lot better)

You get 3 to 4 hours depending on how serious you are with saving power. S2RAM works, s2disk shouldn't be a problem. Alsa does seem to support power management for the chip, but I didn't notice anything. At least one more hour should be possible. My guess is that the nvidia power management doesn't fully work. It's been about the same consumption with the free nv driver when I tested about a month ago.


Did somebody manage to boot linux without bios emulation, i.e. direct efi-boot?
Or am I the only one with serious delays between selecting linux in refit and starting lilo?
I would really like to reduce the time needed for bootstrapping..

[Elv13]

i looked at some webpage about that, if we try tu use EFI, we will break nvidia driver (bios required), wireless and sound so it is nto a really good idea...

You are not alone to find the boot slow, it take almost 20 second for me (grub). We can use EFI, i can try with my gentoo (ubuntu is the default, gentoo for multimedia/compiling) when i will have some time, but is not the case right now.

[l3th0x]

Hi,

New 100.14.19 nvidia display driver is out, and it works! (without patch, I mean).

Regards..

[Dhjiz]

I installed the new driver and I confirm there's no need to patch it anymore.

And best of all, the changelog says it support the new Xserver API, so we could hope it to work out-of-the-box in Gutsy, with the new Xorg and Xserver.

Great news.

EDIT: Here is the changelog: http://www.nvnews.net/vbulletin/showthread.php?t=98635

[drpynchon]

I've been following along the progress on this with glee, but I think in all the efforts to spruce things up I've lost track of something. Now that sound, graphics, and wireless are tackled, what exactly are the remaining issues with Ubuntu on the Santa Rosa MBP?

[Elv13]

I installed the new driver and I confirm there's no need to patch it anymore.

And best of all, the changelog says it support the new Xserver API, so we could hope it to work out-of-the-box in Gutsy, with the new Xorg and Xserver.

Great news.

EDIT: Here is the changelog: http://www.nvnews.net/vbulletin/showthread.php?t=98635

Gutsy use the same xServer than feisty, xserver 1.4 (X11 7.3) will be avalible only in 8.04. 7.3 had some delay and it came after feature freez.

[cyberdork33]

Gutsy use the same xServer than feisty, xserver 1.4 (X11 7.3) will be avalible only in 8.04. 7.3 had some delay and it came after feature freez.

doesn't feisty use xserver 1.2?

[Elv13]

yea, you are right, but gutsy will not use 1.4, both use xorg7.2

[Dhjiz]

No input and output hotplug for Gutsy?

That's completely crap!


That was the best feature of Gutsy. Whatever, what's the URL of the discussion page of the wiki? There's someone who rewrite part of the page to add buggy command and remove useful commands.

[psb6m]

The alsa instructions in the wiki are not working for me. I get down as far as
sudo modprobe snd-hda-intel model=mbp3
and I get these errors:
FATAL: Error inserting snd (/lib/modules/2.6.20-16-generic/kernel/sound/acore/snd.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for snd
WARNING: Error inserting snd_hwdep (/lib/modules/2.6.20-16-generic/kernel/sound/acore/snd-hwdep.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_timer (/lib/modules/2.6.20-16-generic/kernel/sound/acore/snd-timer.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd (/lib/modules/2.6.20-16-generic/kernel/sound/acore/snd.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for snd
WARNING: Error inserting snd_timer (/lib/modules/2.6.20-16-generic/kernel/sound/acore/snd-timer.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_pcm (/lib/modules/2.6.20-16-generic/kernel/sound/acore/snd-pcm.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for snd_pcm
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)

The output from dmesg is extensive; it says among other things "Unknown parameter `model'."

It is not at all clear what (if anything) is being done with the alsa-kernel source that I've downloaded. Can anyone supply more detailed instructions, or some troubleshooting?

Thanks

Peter

[Black Mage]

Is that the full error message?

And did you restart it? I got similiar messages like that and couldn't figure out why nothing was working until I restarted my computer.

[pepe#]

> It is not at all clear what (if anything) is being done with the alsa-kernel source that I've downloaded.

configure in alsa-driver will search and find the alsa-kernel directory if you follow the steps. alsa won't compile without it.

> Can anyone supply more detailed instructions, or some troubleshooting?

The usual error is that people do not unload the old alsa modules. Make sure that your old modules are all deleted. Look for them in /lib/modules/$(uname -r)/kernel/.

'make install' should delete them but it seems ubuntu stores them somewhere else. when you got rid of them, make install again, depmod -a, modprobe snd_hda_intel.

[psb6m]

Just restarting the computer did it. Thanks!

[idezmax]

ok :KS

[Dhjiz]

Does anybody knows if it's possible to boot directly Windows by choosing the Windows icon in rEFIt?

Currently, I installed OS X, rEFIt, Vista and then Ubuntu.
There are three icons in rEFIt: OS X, Ubuntu and Windows.

OS X leads directly to MAC OS X, but Ubuntu or Windows is the same, it leads to GRUB, and in GRUB I can choose between Ubuntu or Vista.

But I would like the Vista icon to launch Windows directly. Do you know if it's possible, and how to do it?

Thanks.

[Elv13]

rEFI is not a perfect solution yet, theire is no way to really control it.

[pepe#]

> Does anybody knows if it's possible to boot directly Windows by choosing
> the Windows icon in rEFIt?

It should just work. I installed Windows into the last partition, then Linux in between and everything was fine.

Maybe you installed grub to the wrong partition once? You can verify by browsing(man strings) the first bytes of the partition, it will contain strings like GRUB or NTLDR. You could try the recovery mode to recover the windows boot loader, or try fixing the mbr.

I don't think the mbr is of any use, but who knows. rEFIt should survive, just like it survived the original installation.

[cyberdork33]

Does anybody knows if it's possible to boot directly Windows by choosing the Windows icon in rEFIt?

Currently, I installed OS X, rEFIt, Vista and then Ubuntu.
There are three icons in rEFIt: OS X, Ubuntu and Windows.

OS X leads directly to MAC OS X, but Ubuntu or Windows is the same, it leads to GRUB, and in GRUB I can choose between Ubuntu or Vista.

But I would like the Vista icon to launch Windows directly. Do you know if it's possible, and how to do it?

Thanks.
Write the MBR code with Vista (see fixmbr), and then install grub to your Ubuntu partition. Right now, grub is in the MBR, and thus, it launches for both OS choices.

[Dhjiz]

Thanks very much for your answers

I didn't know it was possible to install GRUB on a partition and not in MBR.

I'll try what you said.

[DeepB]

hi, any snapshot for my AR5008 MacBook Pro Santa Rosa? ng-r2497 does not work in the long run, disconnect all the time.

[chem]

The sticky-post Apple Intel FAQ really needs a link to three things:

1. a summary of this thread
2. the new ubuntu SR MBP wiki page created somewhere in here
3. pepe's SR MBP wiki page


blah. This thread is so massive now! haha. Anyone tried gutsy-beta with all the latest apple firmware updates?

[trouble1313]

DeepB, I'm still running Madwifi from 6/13/07.....none of the newer versions seem to work for me. No idea why.


I am running Gusty now and it seems fine in general. Everything seems good out of the box except for the wireless.

-Trouble

[pepe#]

I've been using madwifi since months now, updated the modules whenever I felt like doing so. Actually pretty often as I played around a lot. Last time was today. Never had the driver NOT working.

Maybe try a make clean before make;make install. Make sure you're running the very kernel that you want to compile the modules for. Also note that 'make modules_install' for a vanilla kernel will delete all modules and install the vanilla ones.

[trouble1313]

Ok Pepe, you chided me in to fixing things. It seems that for whatever reason, Madwifi 9.3.2 official still does not seem to work on this platform (at least for me). I hadn't gone back and tried a checkout figuring that since there's been 2 official releases since it worked in the repo snapshots that it must have been merged. Seems not to be the case. So I grabbed today's snapshot and viola...it's fine. Go figure.

-Trouble

[Dhjiz]

Write the MBR code with Vista (see fixmbr), and then install grub to your Ubuntu partition. Right now, grub is in the MBR, and thus, it launches for both OS choices.

Hi,

I did that and it worked perfectly.
I did sudo grub-install /dev/sda3 to install grub into the partition. Then I rebooted into the DVD of Windows Vista, I chose the REcovery mode and launched the command bootrec.exe /fixmbr to make Vista recover the MBR and remove Grub.

Now each icon leads to its OS.

After these days' updates, the sound stopped working so I reinstalled it following the method in the wiki, but I couldn't control the sound volume with the hotkeys (F3, F4 and F5).

I upgraded the version of pommed following the method in the wiki but I still can't get the hotkeys working for controling the sound.

Does anyone have an idea about this?

Thanks.

[lv1001]

I did not have any issues with any updates regarding sound. It just works out of the box wih gutsy.
However with any one of the updates the during the last week (don't know which), the keyboard backlight stopped working...
Reinstalling pommed did not do the trick.
Anyone had something similar?

LV

[lv1001]

I am sitting out in the sun right now without access to my wlan using ubuntu.
I gave it a try and started MacOSX and guess what: Full connection!!! And even seing the neighbours wlan. Why is it that the wlan works that much better with MacOSX?
Don't care that much though, sunny days are rather rare here in northern germany and i can reach the wlan from everywhere inside the house.

BTW: Does anyone know where I can download the tickless kernel-patch for 64-bit? it is not included in gutsy and I did not find it searching the web.

LV

[dasein]

I'm also having problems with the madwifi drivers. They work but not so well after I updated gusty to the latest packages.

1) The madwifi drivers do not have the same signal strength as one would be lead to believe by the OS X indicator. I guess this could be just a difference in reporting the value and the network manager in gusty is just more sensitive.

2) The madwifi drivers do not allow setting the modulation manually through iwconfig. If you do 'iwlist modulation', it reports that there are no configuratiions available for ath0. Also I know that my wireless router only supports 802.11b and when I am connected it reports 802.11g which I guess is a problem with the development driver.

3) This is the biggest problem. I can only remain connected for a few minutes before I lose my IP address. This occurred after I updated gusty and rebuilt madwifi drivers for the new kernel. Basically network manager continues to report being connected but ifconfig reports no IP address for the wifi0 or ath0 and any attempt to use 'ping' reports 'network unreachable.' I then tried to manually configure the madwifi drivers using 'iwconfig essid blah key blah' which seems to work and then I attempt to renew my IP address from the DHCP server using 'dhclient ath0' which invariably fails. The only way at that point that I've been able to reconnect is to restart my computer which only again allows me to stay connected for a few minutes.

Any suggestions for mainly problem 3 would be greatly appreciated!

[Dhjiz]

So now that Gutsy is out, should I remove all the parts that concerns feisty in the wiki page of the macbookpro santa rosa and just remaine the gutsy-related information ?

[alephsmith]

Most of that page is now unecessary.

From my installations from RC1 only wifi and SuperDrive needed any prodding to work.

Has anyone installed fresh from an 7.10 final image?

[epaulin]

Is there anyone got microphone works?

I tested on skype and sound recorder, all I got is crazy noise.

[dremon]

SuperDrive worked for me out of the box since Gutsy beta, I didn't do any additional modprobing. The only things I've installed are pommed and wifi. BTW, madwifi has a 1-year old bug (see here (http://madwifi.org/ticket/1017)), still unsolved, which perodically hangs the Atheros card with rx overrun error. Might be a hardware issue as well.

Microphone works fine, also in Skype.

You can control the microphone volume with "Digital" slider on the "Recording" tab in the Volume Control applet. Also "Mic Boost" slider can be helpful.

My system: MBP3, Gutsy AMD64.

[epaulin]

dremon:
microphone works after I turn on digital and change Input source back to "Mic", tnx.
I also have SuperDrive works out of box.
About the bug related to madwifi, use can set "iwpriv ath0 bgscan 0" then everything works sweet.

[Elv13]

New NVIDIA driver, i hope that it will fixe the bug when switching from X11 to console 3 time.

EDIT: NVIDIA... sorry, i have 2 computer and i said the wrong vendor (my other have an ATI)

[russell.h]

AMD driver for what? As far as I know there are no AMD components in an SR MBP.

[DrCR]

So now that Gutsy is out, should I remove all the parts that concerns feisty in the wiki page of the macbookpro santa rosa and just remaine the gutsy-related information ?
Yes, I think we definitely should. At any rate, here's a new thread created for 7.10 Santa Rosa MBP discussion: Macbook Pro- Santa Rosa - 7.10 Gold (http://ubuntuforums.org/showthread.php?p=3575824). Keeping all the relevant info together for a particular version is a real boon to new users.


My comments:
Just install the x86 version, Desktop LiveCD version to my MBRed setup (http://www.linuxforums.org/forum/installation/105234-howto-osx-winxp-vista-grub-hiding-linux-one-hard-drive.html).

Right-Click -- I've found a three-finger tap to work for right-clicking. Neither three nor two for scrolling however.

Touchpad -- Highly sensitive such that when the palm of my hand occasinally touches the touchpad while typing the OS registers it as a single-click. (Happend a few times while typing this post).
Laptop Cooks Itself. -- Anyone know a smcFanControl (http://www.macupdate.com/info.php/id/23049) equivalent for Linux and/or Windows?! Blame rests squarely on Apple's shoulders. Either open up the firmware, or do a proper job (open preferred lol).


DrCR

___________________
MacBook Pro Santa Rosa, 2.2GHz, 250GB Scorpio, Ceramique compound
Pending: Tux Logo mod
OSX, WinXP, Vista (MSDN), Vector 5.8 SOHO, Sidux 2007-03
Pending Fusion "bootcamps" pointing to native OS installs

[pepe#]

> Right-Click -- I've found a three-finger tap to work for right-clicking.
> Neither three nor two for scrolling however.

Two-finger-scrolling works nice here, as does edge-scrolling, two/three-finger tapping etc. Corner buttons seem not very reliable.

> when the palm of my hand occasinally touches the touchpad while typing the
> OS registers it as a single-click.

I use syndaemon to deaktivate touchpad taps when the keyboard is in use. It doesn't quite seem to work right know, maybe because of S2RAM... Don't forget to GrabEventDevice and man synaptics.

> Laptop Cooks Itself

I'm happy with the default setting here. Sometimes I enable the fans because my skin doesn't like warm surface, but in general the laptop is idle and cold. And I mean cold, I warm it up with my palms. You can set a higher minimum fan speed via /sys/class/hwmon/ when you applied the applesmc patches from mactel-linux. I think the applesmc-driver is also in vanilla linux by now.

[Corpus_CT]

Hi,

New 100.14.19 nvidia display driver is out, and it works! (without patch, I mean).

Regards..

What Ubuntu release are you using?

I'm on Gutsy i386, and whenever I install the 100.14.19 nvidea driver, Ubuntu boots in low graphics mode and madwifi is broken. I have to madwifi-unload, re-build and re-install madwifi and finally re-probe the ath_pci mod to get wifi working again.

I've achieved some success using the nvidea-glx-new driver in that I can play Counter-Strike 1.6 in wine, but Source games such as CSS and Team Fortress 2 crash whenever they begin to actually render (ie. once a server has loaded).

[holr]

I have tried compiling the 2.6.23 kernel with mactel patches and can boot into the new kernel fine. However, the latest nvidia driver (100.14.19) installs fine but I keep getting the low-res option when I boot into it. Any ideas? The same happens with the default kernel when I tried compiling the nvidia driver, it works fine with the nvidia-glx-new though, problem is, without the 2.6.23 kernel, my p1i phone doesnt work well so I needed the new kernel with updated patches.

[Chrisj303]

Sorry if this has been answered before - but I have read through this entire thread and have found it extremely confusing !

I have a new MBP santa rosa. I would like to install gutsy to a partition on it.

All I need to know is this;

Will my graphics card work out-of-the-box with the 64bit Gutsy (final release) ?

And;

Is the edited first post in this thread still relevant? esp. the first 2 points. - can I still not install via a 32 or 64bit Live CD ?


Thanks in advance for any help!

chris

[cyberdork33]

https://wiki.ubuntu.com/MacBookPro/SantaRosa

[Chrisj303]

Aah, thanks a lot!

[lv1001]

The latest madwifi svn snapshot (rev. 2826) is broken for me. System freezes on connection.
Does anyone else experience this?
Also, I am effected by this (http://madwifi.org/ticket/1017) problem.
Again, am I the only one?

Thanks,
LV

[cyberdork33]

The latest madwifi svn snapshot (rev. 2826) is broken for me. System freezes on connection.
Does anyone else experience this?
Also, I am effected by this (http://madwifi.org/ticket/1017) problem.
Again, am I the only one?

Thanks,
LV
The svn versions break every once in awhile. They have before as well. Try an older revision.

In the Santa Rosa wiki page there is a (temp) fix for the bug you linked to.
https://wiki.ubuntu.com/MacBookPro/SantaRosa

[lv1001]

The connection seems to last longer with "iwpriv ath0 bgscan 0" but it still breaks from time to time.
BTW: It says in the wiki-page to put this line _after_ "exit 0". Isn't it useless then?

LV

[cyberdork33]

The connection seems to last longer with "iwpriv ath0 bgscan 0" but it still breaks from time to time.
BTW: It says in the wiki-page to put this line _after_ "exit 0". Isn't it useless then?

LV
yes. it should go before.

[hardawayd]

I just got my MBP and have tried with no success to install Ubuntu 7.10 using both the live cd-64 and the alternate 7.10 cd-64. During the installation it keeps indicating corrupt file error messages for some of the files and at the end of the base installation it says it failed. Have no idea what the problem is.

[hardawayd]

Nevermind. Got it working. Now have to figure out how to get the bluetooth mouse working.

[cyberdork33]

I just got my MBP and have tried with no success to install Ubuntu 7.10 using both the live cd-64 and the alternate 7.10 cd-64. During the installation it keeps indicating corrupt file error messages for some of the files and at the end of the base installation it says it failed. Have no idea what the problem is.

Please do not post in multiple locations.

Nevermind. Got it working. Now have to figure out how to get the bluetooth mouse working.

There is a Bluetooth How To in the FAQ.

[dremon]

Might be interesting to other MacBook Pro users.

Because there are no stable drivers for the Atheros AR5418 yet, I've replaced it with Intel 4965AGN which is well-supported and included in the 2.6.24 kernel (Hardy).
The detailed guide for replacing miniPCI-e adapter can be found at http://www.ifixit.com/Guide/Mac/MacBook-Pro-15-Inch-Core-2-Duo/115

The whole process was very simple and fast, the new adapter worked immediately out of the box, no problems so far.

The only disadvantage is that there are no drivers for Mac OS X, however I only use it for firmware updates so it was not an issue for me.

When Atheros will release a stable driver for Linux or Madwifi will mature into something usable, I will replace it back perhaps. For now I had too many troubles with it - random disconnects, unstable data stream, etc.

[sunbird]

Hi all,

I've read through this thread several times and still can't seem to figure out how to get madwifi working. I've tried installing using the instructions on the Macbook Pro wiki page, but no go.

I'd like to try installing the driver from 6/13/07 that some say works, but I'm such a noob that I don't know how... looked on madwifi page and can't find the link. Could someone point me to it? Or provide instructions to make it work?

FOUND IT: All snapshots are here (http://snapshots.madwifi.org/madwifi-ng/) and the 6/13/07 snapshot is here. (http://snapshots.madwifi.org/madwifi-ng/madwifi-ng-r2438-20070613.tar.gz)

Build 2438 works for me. So glad to be unplugged finally!

[pijon]

I'm having trouble with the restricted nvidia-drivers on my macbookpro (4,1). Some pixels are dead and ubuntu usually crashes within 10-15 minutes. Is there any solution to this problem?

[sunbird]

I'm having trouble with the restricted nvidia-drivers on my macbookpro (4,1). Some pixels are dead and ubuntu usually crashes within 10-15 minutes. Is there any solution to this problem?

Hi pijon,

you might check out this thread (http://ubuntuforums.org/showthread.php?t=717345&highlight=4th) or this one (http://ubuntuforums.org/showthread.php?t=720936&highlight=4th) instead... actually, I just looked there and no help on the video driver issue. What card do you have? Mine is a GeForce 8600M GT. This thread is for Macbook Pro 3,1, I'm not sure that the card is the same for v. 4.1 (though it might be).

For me, I had trouble getting it to work until I used Envy (http://www.albertomilone.com/nvidia_scripts1.html), but that script worked fine and my display is now working perfectly.

[pijon]

Thanks sunbird! Envy fixed the problem with the nvidia-card (8600 GT). :)