[Linux] HOW-TO install XBMC for Linux on Asrock ION 330 with full Ubuntu Desktop - Printable Version
+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Announcements, Info, and General Discussion (/forumdisplay.php?fid=85)
+--- Forum: Tips, tricks, and step by step guides (/forumdisplay.php?fid=110)
+--- Thread: [Linux] HOW-TO install XBMC for Linux on Asrock ION 330 with full Ubuntu Desktop (/showthread.php?tid=54705)
- vikjon0 - 2009-08-21 08:11
Quote:Might be worth mentioning that hitting 'm' in Alsamixer mutes/unmutes the channel. Took me a second to figure that one out.Good point. My problem was getting that MM meant mute...
Quote:Vikjon0, I noticed that in your blog, you no longer are performing the "Policy kit section". What were those commands doing before?You mean my xbmcbuntu installation log? The changes to policykit gives the xbmc user root access to the power management. In the xbmcbuntu setup this in included in "sudo apt-get install xbmc-live python-apt"
- pacc - 2009-08-21 16:00
"HWCursor False" did actually turn off the mouse cursor in X for me and
introduced a lot of artifacts when the (invisible) cursor highlighted
menu's in ubuntu.
If you can handle a visible cursor I'd keep it "True"
- vikjon0 - 2009-08-21 17:03
Quote:"HWCursor False" did actually turn off the mouse cursor in X for me and
It is possible that this setting create problems in the desktop. I only use the gnome desktop remotly in NX server and I have not seen any problem. I also use a basic desktop with no themes etc.
- akmofo - 2009-08-21 19:53
I followed this set of instructions, and had pretty successful results. Some things I'd add:
1.)I didn't realize you were doing everything through SSH, but this makes a lot more sense now when you did killed GDM, and I lost access to the GUI.
2.)I set the power management screen-off setting to "Never" rather than the default of 40 mins.
3.)I disabled the lock setting in gconf-editor so that when I resume from standby/hibernate it doesn't ask for a password.
Go to apps / gnome-power-manager
Uncheck "lock_on_suspend" and "lock on hibernate"
4.)I'd recommend using the SVN at this point rather than the "stable version", because the stable version has the bug where you can't access the Audio settings OSD, or hit the "o" key without crashing the program.
5.)Still haven't gotten my wireless USB dongle to work properly yet. It's a Netgear WNDA3300. The ar9170 seems to work but I can only find an older-build of it, and signal strength is terrible. The updated driver is supposed to be included in the next Kernel, so hopefully that will fix it. Luckily I have a Ethernet to Wireless-N bridge to use in the interim.
- vikjon0 - 2009-08-21 20:17
Quote:1.)I didn't realize you were doing everything through SSH, but this makes a lot more sense now when you did killed GDM, and I lost access to the GUI.I always used ssh. I need to copy paste from my laptop.I will add a comment about that.
I am not going to use the GDM anymore but that does not mean I killed the GUI. It can be started in console with "startx" but mostly I connect with NX from the laptop extacly as before.
Quote:2.)I set the power management screen-off setting to "Never" rather than the default of 40 mins.I didn't need to do that when running in the xbmc-session. I am not 100% sure if thats because I did run on a minimal desktop the last few months but I don't think I ever had to do that on the ION 330.
Quote:3.)I disabled the lock setting in gconf-editor so that when I resume from standby/hibernate it doesn't ask for a password.mm, this sounds familiar maybe I did do this and never wrote it down. Will test in xbmcbuntu in a while. I don't use suspend normaly.
Quote:4.)I'd recommend using the SVN at this point rather than the "stable version", because the stable version has the bug where you can't access the Audio settings OSD, or hit the "o" key without crashing the program.I use SVN myself now, but stable worked pretty well for me. I could press o just fine and VDPAU also works. Now svn have some nice fixes for digital sound.
The problem with SVN is that sometimes they do not work....would be nice with a method to revert to an old svn. I guess I could make a backup of the binaries but it would be nice if they saved an older "successful" svn in the launchpad as a semi-stable PPA.
- akmofo - 2009-08-21 20:28
I saw where you installed SSH, but it didn't dawn on me how much easier it is to use when copying and pasting into it from another computer.
I was using VNC most the time, and it was admittedly, kind of a pain in the ass.
If I did it again, I would definitely use SSH over VNC.
- dev_don - 2009-08-22 01:21
does anyone know how I can install the latest Nvidia drivers for the Asrock such as nvidia-glx-190 - the version I have now is nvidia-glx-185
- vikjon0 - 2009-08-22 08:56
Quote:does anyone know how I can install the latest Nvidia drivers for the Asrock such as nvidia-glx-190Replace 185 with 190 in the instruction above. Do you have another PPA or manual build installed you need to remove that first
- thomash72 - 2009-08-22 11:03
Thanks a lot for this guide! I installed XBMC using my computer monitor and everything seemed perfect. The only problem I have now is that Ubuntu will not seem to recognize my TV when connected with VGA. My Panasonic PV-70 only support 1:1 pixel mapping on VGA (HDMI results in serious overscan). In NVIDIA control panel the screen is set to 'CRT-0 (CRT 0 on GPU 0)', and the screen resolution is set to 640x480. I have no options to change these settings. The NVIDIA driver version is 185.18.31. Any proposals ?
- vikjon0 - 2009-08-22 11:44
Problem is that I haven't done any troubleshooting at all with NVIDIA. With my old (very) TV and htpc with ATI it was hell to get to work over TV out. Now with the ASROCK and brand new full HD TV (? well brand new anyway) I have no problem.
It sounds like it should be possible to fix this with NVIDIA setting from the desktop. Did you try to re-run the nvidia config command?
BTW, I do know one thing. Don't have the VGA connected when trying HDMI. It screws up the resolution.
Connect only one cable and screen and re-run the config.