If you have the time and inclination,
…and obscene hacking skills (which I do not).
If you have the time and inclination,
Not quite sure I understand this. I just open the Preference Pane to install a version then just launch it without bothering about anything to do with updates. Mind you, I'm running 10.9.5 so perhaps this doesn't apply to me?This is just a quick PSA for anybody trying to run Chromium Legacy on 10.7.5: When the Github page says all updates need to be installed, they mean it. Every. Single. Update. Trust me, it'll save you a lot of headache. Also consider installing updated certificates to connect to some websites.
It's really just 2014-004 that you need, if you're running Lion. If you can install that, you should be all set!This is just a quick PSA for anybody trying to run Chromium Legacy on 10.7.5: When the Github page says all updates need to be installed, they mean it. Every. Single. Update. Trust me, it'll save you a lot of headache. Also consider installing updated certificates to connect to some websites.
Fwiw, the primary one you need—ISRG Root X1—will be installed automatically if you use the latest version of my Chromium Legacy Downloader.Also consider installing updated certificates to connect to some websites.
There is absolutely a Chromium Legacy initiated kernel panic somewhere, and as far as I can tell it has been present since the earliest working builds of Chromium Legacy. Always with this (or similar) logged:Anyone else getting kernel panics? Earlier I had my 4th in 5 weeks - and I NEVER normally get them!
I'm only raising it here because Console reports for each panic :
BSD process name corresponding to current thread: Chromium Helper
FWIW, it's not been the same build of Chromium each time - I think I've had 3 versions in that time? At least 2 anyway.
panic(cpu 6 caller 0xffffff8014bc7ab4): "kqueue_scan_continue: - invalid wait_result (3)"@/SourceCache/xnu/xnu-2422.115.15/bsd/kern/kern_event.c:2167
keepsyms
boot argument.sudo nvram boot-args="-v keepsyms=1"
sudo nvram boot-args=""
.Since it's happening so much more often for you, it would be great if you could capture a backtrace with keepsyms turned on. Run in Terminal:
Code:sudo nvram boot-args="-v keepsyms=1"
And reboot. Whenever you're able to reproduce the kernel panic, make an issue on Github and post the backtrace. (Or post the backtrace here and I'll make a Github issue.)
Afterwards, you can turn keepsyms back off withsudo nvram boot-args=""
.
It usually pops up after you finish rebooting? But, it should also be in /Library/Logs/DiagnosticReports.I had another panic, first in about a month. Where do I access the backtrace?
A file with today's date and the `.panic` file extension.What am I looking for? There's nothing there called "backtrace"....
It's one of the first things in the log, after the date. But, just share the log file, please!oh I've seen that- but where in all that stuff is the trace?.
Ok, you asked for it!It's one of the first things in the log, after the date. But, just share the log file, please!
It's gone very quiet! Any thoughts on the trace data above?It's one of the first things in the log, after the date. But, just share the log file, please!
Check the Github issue: https://github.com/blueboxd/chromium-legacy/issues/44It's gone very quiet! Any thoughts on the trace data above?
mach_kernel
on the root of your boot drive. To use mine, you would rename the old one (as a backup), put mine in its place, run sudo nvram boot-args="-f -v keepsyms=1"
in the Terminal, and reboot. Please at minimum have a full time machine backup available, and make sure you would be comfortable restoring the original kernel from recovery mode (using recovery mode's Terminal to put the old kernel back) in the event that something goes wrong and OS X is unable to start up!Thanks for that. The technology is way beyond my paygrade, but I do understand that it's a low level (i.e. kernel) issue that can be resolved with a Terminal keepsyms change after inserting a different version of the kernel.Check the Github issue: https://github.com/blueboxd/chromium-legacy/issues/44
If you're desperate for a fix, I have compiled a custom XNU kernel for Mavericks which may make the problem go away (and if it doesn't, that would itself be useful to know). I am not necessarily recommending this, but it is an option, and I've been using it on my own machine for the past five days without problems. I'm also not sure there will be another (potential) solution in the near future, as no one working on Chromium Legacy has deep knowledge of the kernel.
The kernel is a hidden file namedmach_kernel
on the root of your boot drive. To use mine, you would rename the old one (as a backup), put mine in its place, runsudo nvram boot-args="-v -f keepsyms=1"
in the Terminal, and reboot. Please at minimum have a full time machine backup available, and make sure you would be comfortable restoring the original kernel from recovery mode (using recovery mode's Terminal to put the old kernel back) in the event that something goes wrong and OS X is unable to start up!
It's the modified kernel that should fix the problem. The terminal command primarily disables something called the kernel cache (that can be resolved with a Terminal keepsyms change after inserting a different version of the kernel.
-f
), which allows your Mac boot a few seconds faster but also makes it difficult to switch between different kernels. The other flags (-v keepsyms=1
) aren't actually necessary, but make it so that if something does go wrong, we'll be able to see a more useful log.Yes! You could also reinstall Mavericks from scratch (from a USB key, or network recovery) and restore from a time machine backup, or use the opportunity to start fresh. I just don't want anyone to end up with an unusable computer they rely on.I assume that I can simply boot from my Mavericks clone on an external HD and use Terminal there to restore the old kernel?
I haven't yet actually modified the kernel. I haven't had a kernel panic for a while now. Sadly I've had a few freezes when my Parallels Sierra VM is being suspended (i.e. on a Quit) but that's a separate issue altogether.^ FYI, it has come to my attention that modified kernels break iMessage. Not immediately, but after a month or so. (You can ofc switch back to a stock kernel to make it work again.)