Finally, up and running on #!, I had to manually install the .deb for linux-headers, after that i reinstalled the broadcom sta, and now its working.
Running noveou drivers for now, seems to be running hot. But dont want to tinker to much atm.
The screen is awesome, but the scale is way to big. Would you recommend the same DPI settings for me Chris? Or should I use different ones since its a differnet monitor?
Also, yes, the wifi is working, but I dont have a tray icon for it.
Great news :-)
It took you some hard work but you got there, enjoy the new #!
Last edited by Frostlock (2013-10-12 11:58:34)
Last edited by swansonaudio (2013-11-28 01:45:07)
Hi, swansonaudio, glad you got everything working. Maybe you could post a link or a brief description of what you did to correct your problem, just in case someone else runs into a similar problem.
Hi all! I'm just curious to know if you are booting the 32 or 64 bit #!? I have a Macbook 6,1 with Snow Leopard, I know that it's 64 bit capable, but I am wondering if any of you would advise installing the 32 bit over the 64 bit version? Also I recently installed #! on my desktop and love it! Thanks for your advise!
You can install either 32-bit or 64-bit. There are probably better resources out there that could explain the pros and cons of installing the different varieties. Generally, the rule of thumb I use is if you have 4 GB of RAM or more, install 64-bit. If you have less than 4 GB, install 32-bit. Others may have other recommendations.
There are also some programs that use 32-bit libraries, e.g., Steam. You can, of course, enable multiarch in a 64-bit installation. So it's not a problem, but it will involve a few tweaks here and there before those programs will run.
I have 64-bit on my MBR 7,1 and it works just fine.
Last edited by Cosmo (2014-01-30 21:12:10)
Last edited by odim (2014-07-10 13:23:02)
I have not checked this recently, but I believe you need to install #! from the original installation menu on boot. I don't remember if there is a way to install from within the Live Session.
While you are in the installation process, I believe when you get to the grub question, you may advance without specifying anything at all. You may also be able to hit the back button and then select from list of steps the step after grub and, as a result, skip it.
Sorry for the vagueness of this response. I haven't been through the installation in awhile now.
I've been following the original Frostlock post without any problem for a double boot install on an elderly Macbook1,1.
Then I went on Cosmo tips since I'm using refind (0.8.3) and not rEFIt, but it didn't seem to be working for me :
when I try to boot after uncommenting the showtools line in refind.conf, I've got one more menu icon for the options, but clicking on it wouldn't do anything: it would say "Tables are synchronized, no need to sync" and just below in yellow an error "Error: Not found returned from gptsync_ia32.efi"
Apparently refind cannot detect the newly installed crunchbang system, I don't quite get the error there.
Looking at odim comment, I tried to reinstall refind with the --alldrivers option and it did the trick: at the next reboot I ended up with an option for OsX, Debian, and a Linux that goes to the "No bootable device -- insert boot disk and press any key” message.
So refind with the drivrrs is able to directly detect the Crunchbang install and doesn't need to go through Grub.
Now I can remove the showtools line in refind.conf, but how do I get rid of the linux pinguin entry , how do I get rid of Grub?
I'm having a hard time understanding what's going on in the MBR: is it possible to remove the Grub entry in the MBR?
What tool could I use to visualize what's in the MBR and to modify it?
Last edited by nodje (2014-09-30 09:40:26)
thanks to earlier posters for explaining how to dual-boot clearly. I tried this several months ago, actually, using rEFIt and it didn't work. I had installed cruncbang after partition the disk in Disk Utility but the #! os didn't appear as an option.
This time, I used rEFInd and had a bootable CD. It took several restarts after installing rEFInd and the CD didnt't work the first time but after restarting, things ran relatively smoothly. I now have a late 2008 white macbook with Mac OS X 10.6.8 and #!
nodje, sorry I don't have an answer for you.
"A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines" -- RWE
Actually, I've started to realise that I'd probably need Grub to pass in some kernel options at boot time.
Is there another way to enable kernel option at boot time?
If not then I'd rather have a working Grub, which for now doesn't seem possible with refind.
[drm] Initialized drm 1.1.0 20060810 brcmsmac 0000:03:00.0: bus 3 slot 0 func 0 irq 0 wmi: Mapper loaded nouveau 0000:01:00.0: enabling device (0002 -> 0003) brcmsmac 0000:03:00.0: firmware: agent aborted loading brcm/bcm43xx-0.fw (not found?) [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [drm] Driver supports precise vblank timestamp query. i915 0000:00:02.0: Invalid ROM contents [drm] failed to find VBIOS tables vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=none:owns:io+mem vgaarb: transferring owner from PCI:0000:00:02.0 to PCI:0000:01:00.0 ieee80211 phy0: brcmsmac: Failed to find firmware usually in /lib/firmware/brcm brcmsmac: brcms_pci_probe: brcms_attach failed! applesmc: key=359 fan=2 temp=18 acc=1 lux=2 kbd=1 No connectors reported connected with modes [drm] Cannot find any crtc or sizes - going 1024x768
Last edited by Davos (2014-11-11 08:22:50)
Last edited by rwsChris (2014-11-13 13:21:05)
I've used both rEFIt and rEFInd when dual-booting Linux, first on a MacBook and then on an iMac. Personally, I prefer rEFIt, even if it's no longer actively maintained. Why? I've had mixed results with rEFInd and think rEFIt makes installing a Debian-based distro like #! easier. Sonny's quote from Frostlock above outlines the process best.
When you partition your drive for #!, you can create a separate bios/boot partition or boot from your /root partition. Either way, you just select GRUB to be installed in /dev/sda/.
The most important thing to remember is after you install #! and reboot, you should immediately click on the disk partition tool on the rEFIt boot screen. There, you'll see the previous disk configuration and the new one. It will ask you if you want to accept the new configuration. Choose y for yes and then proceed to boot #!. The system should recognize your GRUB install and boot successfully.