Asus Xonar DS Ubuntu 10.04 not working
- Thread starter SamG
- Start date
Associate
- Joined
- 15 Apr 2008
- Posts
- 1,031
- Location
- West Didsbury, Manchester
Open a terminal and tell us what this spits out:
cat /proc/asound/version
Apparently alsa 1.0.23 supports the DS.
cat /proc/asound/version
Apparently alsa 1.0.23 supports the DS.
Associate
- Joined
- 15 Apr 2008
- Posts
- 1,031
- Location
- West Didsbury, Manchester
I see two options here, you can download the alsa 1.0.23 packages from here:
https://launchpad.net/ubuntu/+source/alsa-driver
With making sure that you download ALL the additional package files from the drop down list and see if it works or give this a go:
http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubuntu-lucid-lynx-10-04/
It's not simple package upgrade but should work.
https://launchpad.net/ubuntu/+source/alsa-driver
With making sure that you download ALL the additional package files from the drop down list and see if it works or give this a go:
http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubuntu-lucid-lynx-10-04/
It's not simple package upgrade but should work.
I tried this one a while ago and Ubuntu just hangs on the boot screen now. I'll reboot now and leave it for a while.
Still hangs on the Ubuntu loading screen.
Last edited:
Associate
- Joined
- 15 Apr 2008
- Posts
- 1,031
- Location
- West Didsbury, Manchester
Does it give you any error messages? If it is just hanging on the bootsplash then I think if you remove 'quiet' from the boot line in grub it should show you some more useful information.
Boot comp > grub > edit boot line (press e? it should tell you) > remove the word 'quiet' > press b to boot.
Hopefully that will give you a better idea of what is going on in the background. If it has an error messag then post it here, if not then anything will do, whatever the last line on the screen is.
Boot comp > grub > edit boot line (press e? it should tell you) > remove the word 'quiet' > press b to boot.
Hopefully that will give you a better idea of what is going on in the background. If it has an error messag then post it here, if not then anything will do, whatever the last line on the screen is.
Associate
- Joined
- 15 Apr 2008
- Posts
- 1,031
- Location
- West Didsbury, Manchester
This seems to be a well documented bug, but it is very generic, as in there a few things that could cause it. A couple of things to try:
1) have you got an USB drives or similar plugged in when booting that you didn't have before?
2) when you removed the option 'quiet' was there an option 'splash' too, if so try removing that also.
3) does the live cd still boot ok to rule out any hardware/bios problems.
4) Try adding the options 'nomodeset' and 'acpi=off' to the end of the 'kernel /yad/yada/ya ro' line
If all these fail then it looks like it could be something to do with the alsa module that you updated, either something failed or something doesn't sit quite right with it. Modprobe is when the drivers get there respective modules (kind of like .ini file in windows) loaded. So it seems as though the module is hanging and causing everything to grind to halt. As I said earlier I don't actually use ubuntu so i'm not 100% how they configure things.
If all else fails then I would try re-installing or using a 'proper' distro like Archlinux which will certainly have the updated alsa driver. If you want some help installing it then just drop me an email in trust and i'll pass on my instant messenger details so I can help in real time.
Jack.
1) have you got an USB drives or similar plugged in when booting that you didn't have before?
2) when you removed the option 'quiet' was there an option 'splash' too, if so try removing that also.
3) does the live cd still boot ok to rule out any hardware/bios problems.
4) Try adding the options 'nomodeset' and 'acpi=off' to the end of the 'kernel /yad/yada/ya ro' line
If all these fail then it looks like it could be something to do with the alsa module that you updated, either something failed or something doesn't sit quite right with it. Modprobe is when the drivers get there respective modules (kind of like .ini file in windows) loaded. So it seems as though the module is hanging and causing everything to grind to halt. As I said earlier I don't actually use ubuntu so i'm not 100% how they configure things.
If all else fails then I would try re-installing or using a 'proper' distro like Archlinux which will certainly have the updated alsa driver. If you want some help installing it then just drop me an email in trust and i'll pass on my instant messenger details so I can help in real time.
Jack.
I've tried all those suggestions now. I don't think it's a hardware problem as I can log into and use Windows fine. Alsa has been updated in 10.10 as I tried the Alpha 2 this afternoon and it worked straight away.
I've been wanting to try Archlinux for quite sometime so I'll give that a go this weekend.
If I get stuck I'll give you a poke.
Thanks very much for the help!
I've been wanting to try Archlinux for quite sometime so I'll give that a go this weekend.
If I get stuck I'll give you a poke.
Thanks very much for the help!