[Bug 26294] Re: Ubuntu is missing the alsa-firmware package

2015-04-02 Thread Angus Kerr
Ttoine, Answer 5 years later (!), but yes. Only needed to install the fiirmware (and have done so again with 14.04.2). For my sound card, where I don't think that the firmware has changed, it would appear that it's fine to have the alsa drivers and firmware at different versions. I presume this

[Bug 805232] Re: linux-image-2.6.38-8-server Missing lirc_i2c Kernel Module

2011-09-13 Thread Angus Kerr
I have also encountered this bug (lirc_i2c module missing in kernel 2.6.38-8-generic and 2.6.38-11-generic) in Mythbuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/805232 Title:

[Bug 805232] Re: linux-image-2.6.38-8-server Missing lirc_i2c Kernel Module

2011-09-13 Thread Angus Kerr
I have also encountered this bug (lirc_i2c module missing in kernel 2.6.38-8-generic and 2.6.38-11-generic) in Mythbuntu. ** Package changed: linux (Ubuntu) = mythbuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 805232] Re: linux-image-2.6.38-8-server Missing lirc_i2c Kernel Module

2011-09-13 Thread Angus Kerr
Some more googling seems to indicate the same problem in archlinux and gentoo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/805232 Title: linux-image-2.6.38-8-server Missing lirc_i2c Kernel Module

[Bug 655512] Re: /dev/lirc0 disappeared after upgrade from 2.6.35-20 to -22

2011-09-13 Thread Angus Kerr
Hi I have just encountered the same problem after installing the DKMS modules lirc-modules-source (v 0.8.7-0ubuntu4.1) I have a double whammy now, because the default kernel 2.6.38-8 and 2.6.38.11 does not have lirc_i2c driver installed which I need to get my remote to work, and the following

[Bug 805232] Re: linux-image-2.6.38-8-server Missing lirc_i2c Kernel Module

2011-09-13 Thread Angus Kerr
Unfortunately, ir-kbd-i2c did not work properly with my remote control (there was a spate of other users at the time using 9.04) who had the same problem. udev hooked the device before lirc could get it. I could not stop this from happening, and now on 11.04, my device is not recognised at all by

[Bug 598253] [NEW] automount of usb devices does not work in 10.04 (Ubuntu and Mythbuntu)

2010-06-24 Thread Angus Kerr
Public bug reported: On a fresh install of Mythbuntu 10.04 i386: Automount does not work. Inserting a USB drive does not bring up a desktop icon. It also does not show up in Thunar file manager. Mounting the device manually works (i.e. sudo mount /dev/sd*1 /media/disk) , but only root access is

[Bug 598253] Re: automount of usb devices does not work in 10.04 (Ubuntu and Mythbuntu)

2010-06-24 Thread Angus Kerr
OK, it seems this bug is already fixed. On installation of updates, things have returned to normal. But imho, not a good bug to be in a LTS release, where every fresh install from the CD is tainted. Will not be advising people to use this release until 10.10 -- automount of usb devices does

[Bug 581786] Re: Mute button not enabled by default in Ardour 2.8.6 Lucid AM64

2010-05-25 Thread Angus Kerr
Cool Great to see this getting some action! Thanks, Team. Angus -- Mute button not enabled by default in Ardour 2.8.6 Lucid AM64 https://bugs.launchpad.net/bugs/581786 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs

[Bug 26294] Re: Ubuntu is missing the alsa-firmware package

2010-05-13 Thread Angus Kerr
Toine Scholtz? just checking was Just hit the same issue after installing a clean 10.04 Ubuntu Studio with an EMU-1212 card. Grabbed the tarball from the alsa website and installed the old fashioned way. After the initial glitch of the firmware missing, I am very impressed with the distro.

[Bug 348600] Re: 8.10 installs, on reboot get Error 15

2009-05-06 Thread Angus Kerr
I think this bug is the same that I reported in https://bugs.launchpad.net/mythbuntu/+bug/371062 The most likely problem is that you selected VNC as an additional service, and used non-alphanumeric characters in your password. This crashes the installer when it configures vnc before it installs

[Bug 371062] Re: ubiquity crashes during 'configuring additional services' on 9.04 if a VNC password with non-alpha characters is used

2009-05-06 Thread Angus Kerr
*** This bug is a duplicate of bug 363153 *** https://bugs.launchpad.net/bugs/363153 I'll be happy to. I'm new to Mythbuntu (not Ubuntu - have used it since 6.06). This is my first install.being in South Africa with expensive bandwidth we usually wait for a release and then copy the

[Bug 46470] Re: System freeze with white screen

2008-09-03 Thread Angus Kerr
NB: This email and its contents are subject to the Eskom Holdings Limited EMAIL LEGAL NOTICE which can be viewed at http://www.eskom.co.za/email_legalnotice Hi There I have posted a workaround here:

[Bug 46470] Re: System freeze with white screen

2008-04-30 Thread Angus Kerr
This is still an issue with Gutsy and Hardy. The workaround still applies. I am concerned that a lot of new users will be put off because of this and other driver related issues..Like with Gutsy the boot CD - X works in 640x480 mode. In Hardy, X is broken and you need to boot up in failsafe

[Bug 46470] Re: System freeze with white screen

2007-10-10 Thread Angus Kerr
Thanks Davor I used sysv-rc-conf and disabled powernowd. This solved the problem, I haven't had a crash since then. -- System freeze with white screen https://bugs.launchpad.net/bugs/46470 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber.

[Bug 46470] Re: System freeze with white screen

2007-10-03 Thread Angus Kerr
Hi I have the same issue with Feisty (7.04) wih kernel 2.6.20 and all updates installed. System freezes to a white screen a few minutes after launch of Firefox (also up-to-date). The only recovery option is a hard reset. I have not looked at logs to see what happened in the kernel. Disabling