Skip navigation.
Home
My Public Diary

Ubuntu Linux

Voila!! pulseaudio is working within ubuntu karmic koala

About 3 weeks ago since my laptop's audio functionality hasn't been resolved and is not working still altogether within pulseaudio enabled/installed. Pulseaudio gave me nothing but problems.

Eventually, I came through some sites which in return leads me to upgrade to the latest unstable alsa/pulseaudio from the Launchpad PPA unstable repositoires. This Lanuchpad PPA/unstable comes with ALSA 1.0.22, Pulseaudio 0.9.21 and some others packages. It's also recommended to install/upgrade your kernel version to 2.6.32.1.

Voila!! Everything seems to be working once again.

Pulseaudio in karmic

Sounds like I am probably experiencing some bugs regarding pulseaudio not initializing correctly due to its module-udev-detect bailing when it hits the modem device. however, It should allow the device instead of bailing when detecting it.

In the meantime, I can either de-install slmodemd or alternatively use module-udev (the static hardware detection module) instead of module-udev-detect in ~/.pulse/default.pa

ATI Restricted Driver does not work on Intrepid 8.10

Eventually had been able to ''UPGRADE'' Ubuntu 8.04 Hardy to Ubuntu 8.10 Intriped. Most of the upgrade process went (seemingly) smooth except for the restricted driver of xorg-fglrx-driver. I was not able to start X! on Ubuntu intrepid. This was due to another overlaping files from another ATI-driver as I was able to resolve this issue by removing all xorg drivers and reinstalling xserver-xorg-video-ati one.

It could be done by something like this. (worked for me at least)

* apt-get remove --purge fglrx*
* apt-get remove --purge xserver-xorg-video-ati
* apt-get remove --purge xserver-xorg-video-radeon
* apt-get install xserver-xorg-video-ati

Now run "/etc/init.d/gdm restart" and you'll have your normal graphical login screen. There is no need to modify /etc/X11/xorg.conf

XGL session is no longer necessary in Ubuntu 7.10 Gusty Gibbon

The XGL server will be automatically started in Ubuntu Gutsy Gibbon as opposed to Ubuntu Fiesty Fawn, therefore the special X session you've created in your Ubuntu Fiesty Fawn is no longer needed to start the XGL server because it will likely fail to work properly as It did with me.

Consequently you've to select a regular session from your session manager to disable Xgl. or create a file named ~/.config/xserver-xgl/disable.

As eventually It works for me like a charm.

Note to Ubuntu Users seeking to run Beryl

You WILL have to force version 0.2.0 for the core, but everything else can still run 0.2.1. This can be done through Synaptics. Its not a bug with this method, its an Ubuntu issue unrelated to the drivers.  

Syndicate content