Running Webex on Ubuntu
Webex running on Ubuntu and other non-Windows platforms is literally a click away, in this case the CMR (Collaboration Meeting Room).
Webex is a fact of life for many people and for many Linux (BSD and other non-Windows) users, it has been a thorn in the side with people going so far as to set up virtual machines just to run Cisco’s collaboration software. While Webex is written in Java, it isn’t so simple to get running everywhere and apparently not all features are available for non-Windows users.
Most likely you are running up against the following message after logging into *.webex.com
Your browser,browser version, or operating system is currently unsupported
This requires the intervention of whoever is administrating the *.webex.com account and they can modify it in the following way.
Vagrant, Virtualbox and Ubuntu Wily Weerwolf: Getting them to play along.
I recently upgraded to Ubuntu 15.10 (Wily Weerwolf) which automatically upgraded VirtualBox from 4.3 to 5.0 and broke compatibility with Vagrant 1.6 in the process. Thinking that Vagrant knows about this and they claim VBox 5.0 compatbility, I upgraded to 1.7 and came across the same error!
Vagrant attempted to execute the capability ‘configure_networks’ on the detect guest OS ‘linux’
There is a workaround!
Cross-compiling for Raspberry Pi on Ubuntu
While the Raspberry Pi 2 has four cores to churn through code, it still takes longer to compile than on most workstations and laptops. If you are feeling adventurous, you can try cross-compiling which has become easier to set up and get working.
Cross-compiling is when binaries created are for another target architecture than the one you are compiling on. This kind of set up is very typical when creating Android applications. The end result is that you can take the resulting binary and place on its target platform, and it will run there.
There are even tricks to getting the cross-compiled binary to also run on your native system!
In this guide, I’ll walk you through:
- Setting up a cross-compile toolchain in Ubuntu (15.04 Vivid)
- Setting up the proper exports
- Compiling a test program for your native and target armhf platform
- Compiling the latest Raspberry Pi 2 kernel with VC4 support.
Wireless BCM4312 with the 3.10, 3.11, 3.12 and 3.13 kernels
The hybrid driver from Broadcom was updated again in September (2013) with all the previous patches and a few other fixes as well. This brings them up to support linux kernel 3.9, which is very much welcome.
Sadly it breaks again with >= 3.10 with many warnings and errors which isn’t good considering that Ubuntu (13.10) Saucy Salamander is about to be released.
We do have a patch for you though that gets us working again up to the 3.11 kernel.
Chipsets supported by “Broadcom’s IEEE 802.11a/b/g/n hybrid Linux® device driver” are: BCM4311, BCM4312, BCM4313, BCM4321, BCM4322, BCM43224, BCM43225, BCM43227 and BCM43228.
Wireless BCM4312 with the 3.6, 3.7 and 3.8 kernel
As a follow up to , I’ve also tested the Broadcom hybrid driver with the 3.6, 3.7 and the soon to be released 3.8 kernels with success. There have been no major changes that should effect the operation of this driver.
To verify that everything is working as expected on the software side, when modprobe or insmod wl, you should get a similar dmesg output:
[ 307.560347] lib80211: common routines for IEEE802.11 drivers
[ 307.560353] lib80211_crypt: registered algorithm ‘NULL’
[ 307.564524] wl: module license ‘unspecified’ taints kernel.
[ 307.564529] Disabling lock debugging due to kernel taint
