John is running a 2007 mac, and that core 2 duo is the problem with apple not supporting that model’s upgrade, like yours.
The 2011 would be supported… but according to this
https://support.apple.com/en-us/HT201475
the 2006 would not be… (probably hardware/drivers/cpu)
That sucks. Sorry for the OP.
In case anyone is in the same boat:
Can your Mac use Sierra?
macOS Sierra requires one of the following Mac models and versions of OS X. It also requires at least 2GB of memory and 8.8GB of storage space.
iMac (Late 2009 or newer)
MacBook (Late 2009 or newer)
MacBook Pro (Mid 2010 or newer)
MacBook Air (Late 2010 or newer)
Mac mini (Mid 2010 or newer)
Mac Pro (Mid 2010 or newer)
OS X El Capitan v10.11
OS X Yosemite v10.10
OS X Mavericks v10.9
OS X Mountain Lion v10.8
OS X Lion v10.7
There still is the option of installing Ubuntu on there.
I’m working on an installer that should work on Lion. Just taking a bit since I don’t have access to a Lion machine.
Please run the following commands and post output:
curl --version
wget --version
ruby --version
ruby -ropen-uri -e ‘p open(“https://getchannels.com/dvr/setup.sh”).read.size’
Last login: Tue Jan 17 21:27:46 on ttys000
Statler-and-Waldorf:~ Temp$ curl --version
curl 7.21.4 (universal-apple-darwin11.0) libcurl/7.21.4 OpenSSL/0.9.8z zlib/1.2.5
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate IPv6 Largefile NTLM SSL libz
Statler-and-Waldorf:~ Temp$ wget --version
-bash: wget: command not found
Statler-and-Waldorf:~ Temp$ ruby --version
ruby 1.8.7 (2012-02-08 patchlevel 358) [universal-darwin11.0]
Statler-and-Waldorf:~ Temp$ ruby -ropen-uri -e ‘p open(“https://getchannels.com/dvr/setup.sh”).read.size’
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:586:in connect': SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: tlsv1 alert internal error (OpenSSL::SSL::SSLError) from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:586:inconnect’
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:553:in do_start' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:542:instart’
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:242:in open_http' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:616:inbuffer_open’
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:164:in open_loop' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:162:incatch’
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:162:in open_loop' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:132:inopen_uri’
from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:518:in open' from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/open-uri.rb:30:inopen’
from -e:1
Statler-and-Waldorf:~ Temp$
Last login: Wed Jan 18 20:06:19 on ttys000
Statler-and-Waldorf:~ Temp$ curl https://channels-dvr.s3.amazonaws.com/latest.txt
2017.01.18.2126
Statler-and-Waldorf:~ Temp$
I have late 2007 macbook
Processor 2.2 GHz Intel Core 2 Duo
emory 4 GB 667 MHz DDR2 SDRAM
OSX 10.7.5
I was getting the same messages as john
tried curl -f -s https://channels-dvr.s3.amazonaws.com/setup.sh | sh
Kids-MacBook-419:~ henri$ curl -f -s https://channels-dvr.s3.amazonaws.com/setup.sh | sh
Downloading Channels DVR 2017.01.18.2126 (darwin-i386) to /Users/henri/channels-dvr
ERROR: Installation of Channels DVR failed.
ERROR: Please contact [email protected] with the full output above.
Kids-MacBook-419:~ henri$
1 Like
Looks like a 32-bit machine. We don’t have 32-bit builds for OSX at this time.
Ah, ok thanks. Didn’t realize that. I’ll have to keep using my Mbp for the dvr.
@sejmann mentioned earlier that these machines had a 32-bit kernel but 64-bit userland, so I guess that’s what is going on.
Since our 64-bit binaries are segfaulting, it doesn’t seem like the DVR can be used on these older systems at this time.
Here’s some weird old wacky instructions that might allow your Mac Mini to boot into 64bit mode:
If your Mac uses the 32-bit kernel by default, but supports the 64-bit kernel, you can start up using the 64-bit kernel by holding the 6 and 4 keys during startup.
If your Mac uses the 64-bit kernel by default, you can start up with the 32-bit kernel by holding the 3 and 2 keys during startup.
Your Mac will revert to the default kernel the next time you reboot it.
To select the 64-bit kernel for the current startup disk, use the following command in Terminal:
sudo systemsetup -setkernelbootarchitecture x86_64
To select the 32-bit kernel for the current startup disk, use the following command in Terminal:
sudo systemsetup -setkernelbootarchitecture i386
Oh well, it was definitely worth a shot. Thanks for the effort you guys put in. Love Channels.
The CPU is 64 bit capable and the weird old wacky instructions seemed to indicate that it would boot into 64 bit mode:
Kids-MacBook-419:~ henri$ sudo systemsetup -setkernelbootarchitecture x86_64
Password:
setting kernel architecture to: x86_64
changes to kernel architecture have been saved.
Kids-MacBook-419:~ henri$
but, alas, still no joy:
Kids-MacBook-419:~ henri$ curl -f -s https://channels-dvr.s3.amazonaws.com/setup.sh | sh
Downloading Channels DVR 2017.01.18.2126 (darwin-i386) to /Users/henri/channels-dvr
ERROR: Installation of Channels DVR failed.
ERROR: Please contact [email protected] with the full output above.
Kids-MacBook-419:~ henri$
Did you reboot after changing the architecture?
yes, and when it didn’t work then, rebooted again holding down 6 and 4. C’est la vie. I have it running on my MBP.
I think the 64bit kernel requires 64bit EFI, which wasn’t even available in my Lion install for my Core 2 Duo MBP. Apple also apparently blacklisted certain machines specifically, because 64bit graphics drivers weren’t available. Which, basically means to get some of these old machines to boot true 64bit would be similar to building a Hackintosh – patching the kernel and EFI, and somehow finding 64bit drivers and patching them for unsupported hardware.
Would significant changes be necessary on your end to target a 32bit build?
You can probably find a Lion 32 bit VMWare Image floating around the net to test against.