For those 10.10 Maverick users with 2.6.38 or 2.6.39 (64-bit) kernels, you can get fglrx playing nicely together with X.org 1.9.
Unfortunately this new driver does not support X.org 1.10 and that leaves 11.4 users to use the open-source drivers.
Custom build procedure:
My Vostro 1510 comes with an on-board wireless miniPCI card but it does not work “out of the box” with Ubuntu, even with the latest 2.6.39 kernel. The only option that works for me is the binary hybrid blob driver provided by Broadcom, but even that is out of date. They need help in order to work with 2.6.36 and upwards and I have a patch for that.
Chipsets supported by “Broadcom’s IEEE 802.11a/b/g/n hybrid Linux® device driver” are: BCM4311, BCM4312, BCM4313, BCM4321, BCM4322, BCM43224, and BCM43225, BCM43227 and BCM43228.
The my exact chipset from lspci command:
Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
My current project that involves hundreds of mini-ITX Atom machines and we are testing the performance difference between Infiniband and Intel Gigabit NICs.
In my testing the overhead of processing TCP is too high for a dual-core Atom. There is simply not enough processing power to handle the capabilities of the Intel NICs.
A possible solution is to replace TCP by using SDP (RDMA and Zerocopy) over Infiniband. Infiniband equipment has come down significantly in price (dual port 4xSDR card for around $50), which makes it attractive to high-performance and cost-sensitive applications like mine.
In theory we can get 4xSDR speeds (8 Gigabit/s), but the tested result is 1.5 Gigabit/s speeds because of TCP processing over Infiniband. This is almost exactly the performance we achieved using the Intel NICs. We then replaced TCP with SDP over Infiniband. With the switch we saw 4.2 Gigabits/s performance on one process. With two processes, one for each core of the Atom, we saw 7.8 Gigabit/s which is close to the theoretical limit of the Infiniband NIC.
X-Swat has not updated their ati packages in a long time which means that Natty users and Maverick users with 2.6.38 (64-bit) cannot run with fglrx video drivers.
In order to get the latest 2.6.38 kernel and fglrx playing nicely together you will need to build these packages yourself.
Custom build procedure:
Cisco’s new line of equipment now use a mini-USB cable for console configuration. There is no longer a need for a USB to serial adapter or a roll-over cable.
Connecting the USB cable on Linux should give you a new ACM device that looks something like this: “/dev/ttyACM0″.
To verify, you can also look through your dmesg or /var/log/messages :
[265430.720082] usb 4-1: new full speed USB device using uhci_hcd and address 4
[265430.914246] cdc_acm 4-1:1.0: This device cannot do calls on its own. It is not a modem.
[265430.914305] cdc_acm 4-1:1.0: ttyACM0: USB ACM device