Archive for the ‘linux’ Category

Compiz with fglrx on Mobility Radeon 3400

Sunday, March 8th, 2009

On 2009‒02‒16, I wrote:

While still in the mood for pointless Linux software, I tried Compiz Fusion again—again, with no success. I plan to wait until the RadeonHD driver is finished. I have not tried AMD’s proprietary fglrx driver thanks to horror stories of system crashes and hardware damage.

I tried fglrx anyways. I followed fedoraforum.org’s tutorial for my Dell Studio 15, Radeon Mobility, and Fedora 12, and I now have Compiz Fusion working. I encountered three issues:

  • Using the Animation plugin, effects are not displayed for the shade, focus, and minimize actions.
  • Occasionally when I switch back to Firefox, Firefox’s scroll bar will not function unless I maximize, resize, or move Firefox. This occurs even with all plugins disabled.
  • When opened, gnome-compiz-manager returns the error: “Type mismatch: Expected list, got string”. I cannot change the shortcut keys in any menu. (I use CCSM).

I will post any solutions here; otherwise I will file a bug report against freedesktop.org’s bug database.
Otherwise, Compiz is functioning beautifully on my Mobility Radeon HD 3400. I added compiz-fusion-icon to my Gnome startup scripts, which serves to load it automatically.
I’m off to spin my desktop. I might post screenshots later.

Fedora Plymouth Graphics and Compiz Fusion

Monday, February 16th, 2009

Here are two changes I made to my Fedora install recently—one successful, one not.

 

graphical Fedora Plymouth animation (success)

I will neglect my blog’s philosophy by covering a topic that has already been covered: Axel’s guide describes this process. Derek Hildereth also covered this process, citing Axel’s guide. ⟵I tried this one.

 

My Dell Studio 15 has an ATI Mobility Radeon HD 3400 graphics card, for which I am using x.org’s default open source driver. I had been using Plymouth’s text animation, assuming that the graphical modes would not work with my card. I followed Axel’s guide and now have an esthetic boot sequence. Briefly:

Add a VGA framebuffer resolution value to grub.conf. For example, I added the bold text in mine:

title Fedora (2.6.27.12-170.2.5.fc10.i686)
root (hd0,1)
kernel /vmlinuz-2.6.27.12-170.2.5.fc10.i686 ro root=/dev/VolGroup00/LogVol00 rhgb quiet vga=0×323
initrd /initrd-2.6.27.12-170.2.5.fc10.i686.img

vga should be specific to your display. Use the following table, which I obtained from Steven K. Baum’s reference.

Colours   640x480 800x600 1024x768 1280x1024 1600x1200
--------+---------------------------------------------
256     |  0301    0303     0305     0307      031C
32,768  |  0310    0313     0316     0319      031D
65,536  |  0311    0314     0317     031A      031E
16.8M   |  0312    0315     0318     031B      031F

You can configure Plymouth’s animation with the following two commands (as root):

plymouth-set-default-plugin pluginname {solar, fade-in, pulser, spinfinity}
/usr/libexec/plymouth/plymouth-update-initrd

 

Compiz Fusion on Mobility Radeon HD 3400 FOSS drivers (failure)

While still in the mood for pointless Linux software, I tried Compiz Fusion again—again, with no success. I plan to wait until the RadeonHD driver is finished. I have not tried AMD’s proprietary fglrx driver thanks to horror stories of system crashes and hardware damage. It seems that Mobility Radeon HD 3400 graphics cards do not enjoy stable drivers that enable hardware acceleration—yet.

Update: fglrx works perfectly on my Radeon HD 3400, and I have Compiz working.

If this worked or did not work for you, comment!

ABC’s Story on Abbie Schubert, Dell, and Ubuntu

Thursday, February 12th, 2009

On 2009‒01‒13, ABC’s WKOWTV posted a news story and article, where Abbie Schubert, a student enrolled in online courses at Madison Area Technical College bought a Dell computer with Ubuntu and blamed Dell, Ubuntu, and GNU–Linux for having to abandon her semesters. ABC writes:

She didn’t realize until the next morning her laptop defaulted to the Ubuntu operating system.

Her Verizon High-Speed Internet CD won’t load, so she can’t access the internet. She also can’t install Microsoft Word, which she says is a requirement for MATC’s online classes.
As a result, with no internet and no Microsoft Word, Schubert dropped out of MATC’s fall and spring semesters.

While first reading this article, I felt sympathetic for the student. I don’t anymore.

 

Ordering a PC with Ubuntu requires either awareness or negligence:

  1. On Dell’s front page, hover your cursor over the drop‐downs for Desktops or Laptops & Mini and select the option for Open‐Source PCs, despite the flashy image–links’ prominence. This brings you to Dell’s Ubuntu page.
  2. Ignore the warnings like Not sure Open Source is for You? and The main thing to note is that when you choose open source you don’t get a Windows® operating system. If you’re here by mistake and you are looking for a Dell PC with Windows, please use the following link.
  3. Ignore the description, with its own warnings like may not be compatible with the same software applications and hardware as Windows operating systems.
  4. Go through the typical web‐based configuration process, explicitly clicking Ubuntu, not noticing the selection options for Operating System, which again says Ubuntu. Ignore the Review screen which again says Ubuntu and click continue anyways. Add the item to your cart and again ignore the Ubuntu.
  5. While confirming your purchase email, ignore the information.

Is that really insufficient notice? Then, Abbie Schubert’s particular case also requires the following:

  • Not using alternatives, such as library computers (which her campus had).
  • Not requesting help from her peers or the Linux community.
  • Attempting to use wireless drivers in a CD explicitly for Windows.

Users accustomed to Windows find switching difficult, so I am sympathetic towards her confusion after the purchase. But I do object to her—or, more likely, only ABC’s—eagerness to blame Dell and Ubuntu.

 

The article itself rings of bias. For example:

[Ubuntu is] extremely popular with certain circles of computer users because it’s free.

Or perhaps because it is better? Even Dell makes buying computers with GNU–Linux difficult and more expensive; many if not most GNU–Linux users buy a PC with Windows and then install GNU–Linux.

 

Here is another:

But it is not Windows, and what works on Windows doesn’t always work on Ubuntu.

…and vice versa, perhaps?

 

At 1:35 of the Youtube movie, notice the ABC reporter: […] Ubuntu might look a lot like Windows, but it sure doesn’t act like it accompanied by a carefully‐chosen screenshot of an error in Firefox.

 

ABC’s implicit and explicit accusations that Dell forced her to use Ubuntu likely border on slander.

She called Dell the very next day and says the representative told her there was still time to change back to Windows.
But she says Dell discouraged her.
“The person I was talking to said Ubuntu was great, college students loved it, it was compatible with everything I needed,” said Schubert.

The question arises: what conversation preceded that quote? I highly doubt the representative said that randomly.

 

ABC also writes:

She also says Dell claimed it was now too late to get Windows and any changes she made herself would void her warranty.

…perhaps because that is their policy?
“Claimed” overtly suggests misinformation or fabrication. Dell certainly does not have a reputation for sincerity and integrity, but ABC has a reputation for providing information that is deliberately misleading.

 

Whether Abbie Schubert deliberately created Microsoft’s new‐found marketing weapon or ABC warped her story for mass‐appeal (I find the latter more probable), her issues are a direct result of her choice in purchase.
I wish her luck in her next semester.

Broadcom Wireless Drivers for Linux

Sunday, January 4th, 2009

On 2008-10-25, I wrote:

• (For Linux users) Configuration only supports Broadcom-based Dell wireless cards, which don’t have open source drivers, and Broadcom’s proprietary drivers work poorly with ndiswrapper²
² Broadcom is currently developing open source drivers that should be released soon: http://direct2dell.com/one2one/archive/2008/10

That was (as far as I know) correct, but I would like to add something: proprietary drivers for the 802.11 Linux sta, which work for Broadcom BCM4311‐, BCM4312‐, BCM4321‐, and BCM4322‐based wireless cards. This coverage includes the Dell‐branded wireless cards that shipped with the company’s Studio 15 and Studio 17 models when I bought my Studio 15 (it appears they now ship with Intel‐made cards). These drivers are supposedly kernel‐version‐independent and distribution‐independent (of course, verification is difficult because they’re proprietary). 32‐bit and 64‐bit ‐based architectures are supported. Dhananjay Singh wrote a brief tutorial that I used, resulting in working wireless card drivers for Gnu–Linux for my Studio 15. I also wrote:

Right now, I would recommend it to Windows users and Linux users who do not mind the headphones and wireless issues. Chances are I will excitedly advertize it to Linux users in a few months.

That month has come; now I would recommend it. If this worked or did not work for you, comment!

Fedora Cambridge: Annoyance Followed by Content

Friday, November 7th, 2008

On 2008‒11‒03, updates from Livna killed X on Fedora 9 on my Dell Studio 15. I will not elaborate further because I cannot. The timing was great: I had planned to install the Preview release of Fedora 10 (Cambridge) on its release date (2008‒11‒04), so I did that. Hell followed. Here are some pointers, many of which are specific to my system and personal stupidity:

  • When booting, the i386 install DVD image prompted me to press enter. I received no feedback when pressing enter and conceded.
  • I installed from the Fedora 10 beta i386 install DVD image. Unfortunately, changes made to GRUB for Plymouth as of then were incomplete, and updating them with Yum from Rawhide did not help. After my BIOS would load, GRUB would not display my menu and would start interactively (I could still boot to Fedora 10, which ran fine). The Plymouth readme showed me the light:

    “Plymouth isn’t really designed to be built from source by end users. For it to work
    correctly, it needs integration with the distribution. Because it starts so early,
    it needs to be packed into the distribution’s initial ram disk, and the distribution
    needs to poke plymouth to tell it how boot is progressing.”

  • Fedora Live CDs do not permit mountpoints on ext4 partitions. That was an issue because I had been using ext4 since I installed Fedora 9.
  • Anaconda’s partitioning screen gave inaccurate information on my ext4 partitions’ sizes.

I performed a clean install using the Fedora i386 Network Installer. My reactions:

  • The Echo icon theme is pretty.
  • Gnome 2.2x has nice but fairly insignificant changes.
  • Eclipse Ganymede features several improvements.
  • The OpenJDK VisualVM seems nifty.
  • RPM 4.6 has many improvements I have been wanting (namely bug fixes and support for SHA-256)
  • Much faster startup.
  • Plymouth resorted to the text-based loading plugin which is not as esthetic as RHGB was, but the consistency is nice)
  • SecurityAudit looks useful (I have hardly used it, though).
  • Cheese now crashes with my webcam.
  • sbin sanity pleased me.
  • Ultimately, the most useful change was Eclipse Ganymede—which I could have installed with Fedora 9. But I feel better simply because I am running Fedora 10—a result of OCD.

Internet Radio Stream Extraction

Sunday, October 26th, 2008

Do you listen to stream-based Internet radio and have certain times when you want to listen but can’t afford the lost bandwidth? Neither do I, but apparently some users do. Therefore I wrote a Bash script called Yell to extract and download an Internet radio stream for later use, which is available—but which requires further testinghere. The intent is for users to use during times where the consumed bandwidth is not an issue (like while sleeping) to listen to during times where it is (like at work). I based my code on the problem description and limited approach from “Shakir” (see the public domain Bash script here) but can’t find his full name. I wrote this software for legitimate use; please don’t abuse it.

Open Source Misses the Point

Wednesday, October 22nd, 2008

I find the debate between open source and Free software to be interesting. But until a few weeks ago, I did not understand the depth of the FSF’s disapproval of open source’s term and advocacy. In general, I find the difference to be technical: Free Software advocates directly for users’ freedom, while Open Source software advocates for users’ freedom under the guise of profitability—“switch to open source and your products will improve”. I was surprised that Richard Stallman disagrees: he says that “‘Open Source’ misses the point of Free Software.”; in his article (accessed 2008-10-21), Stallman argues that advocates of Open Source software do not understand the ethical aspect. I disagree—I find that most advocates understand the ethical issue. Despite this, I have noticed that everyday users—not developers—of Free and/or Open Source software often usually do not. The issue’s fault may indeed be Open Source’s name, which does not attribute a moral component (the name ‘Free Software’ has issues dissociating its advocacy from price—free as in speech, not beer). Regarding most Open Source developers, I disagree with Stallman, but his article raises interesting points. Despite this, I highly recommend reading the article to every computer user.

Linux Kernel Package Composition

Thursday, October 9th, 2008

Ever wondered how the Linux kernel’s source code is over 250 megabytes? I was recently curious what comprises the bulk of the Linux kernel’s full source and patch baseline packages. Kernel version 2.6.26 was over six million SLOCs (“5 things you didn’t know about linux kernel code metrics”. Maciej Sołtysiak. Accessed on 2008-10-08), so 250MB is reasonable. I downloaded the patch baseline package of Kernel version 2.6.27-rc9 and ran Markus Lausser’s gdmap on the extracted files. Here are the results:
Here are the colours I used in my configuration:

colour-coded file type composition of the Linux Kernel

colour-coded file type composition of the Linux Kernel

dark green (#004400): C sourcecode (.c .cc .agh .cpp .c_shipped)
light green (#00FF00): C headers (.h .hh .h_shipped)
orange (#FF6600): low-level language code (.S .s .dts .uc .reg .seq .ld .ucode .sa)
brown (#998844): scripting language code (.y .l .inc_shipped .pl .sh)
light blue (#66AAFF): documentation (.tmpl .mdb .src .ioctl .txt .po .history .oss .xsl .xml .html .htm)
dark pink (#CC2299): configuration and some documentation (some documentation files lack filename extensions¹).
olive (#443300): hexadecimal (.HEX, .h16, .ihex)
yellow (#EEEE00): images (.eps .ppm .pbm)
bright pink (#FF3333): Tex (.tex)
purple (#6600CC): Unicode definitions (.uni)
grey (#888888): testcase data (.tst)

I chose the filename extensions for each group by examining the MIME types and briefly checking the files individually; however some data might be inaccurate, especially for files that constitute less than .05% of the total. This image shows the package’s general makeup, but running gdmap should give you a better and more specific sense.

¹ gdmap relies exclusively on filename extensions. This group actually consists of every file not identified by another.