[LINUX] My Asrock 330 ION Tweaks, Tips, Tricks, and Fixes! - 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] My Asrock 330 ION Tweaks, Tips, Tricks, and Fixes! (/showthread.php?tid=61697)
- gekados - 2009-12-09 15:49
X3lectric Wrote:yea well Im not one to pussy foot around things I considered not responding just because I knew my response would be harsh and to the point.
I can understand the frustration when being asked questions when people should have know the answers. I worked for a tech support for a few years, so I can relate ;-)
No harm done, i'll try it on jaunty when i get a chance to reinstall / wrestle the remote from my girlfriend, hehe.
- fackamato - 2009-12-13 02:17
Why doesn't XBMC work with 2.6.32? What's the error?
- pinthenet - 2009-12-14 22:23
does anyone have any tips for the 330BD version with BC-5500S Bluray drive. I managed to rip a bluray disk using makemkv, admittedly after 2 or 3 attempts, but since I've updated the kernel to 2.6.28-17 it doesn't seem to recognise it as a bluray device. With a BD in the drive lshw shows
with a DVD loaded it shows
I can play DVDs & Audio CDs but makemkv and dumphd report no disk when I put in a BD
- X3lectric - 2009-12-15 00:42
Quote:logical name: /dev/scd0In my experience with asrocks it tends to be /dev/sr0 and it should show as such in fstab. I havent made any Linux installs on the BD versions. Depends if the device in /media is being mounted scd0 or sr0. Im willing to bet sr0, though it mounts as cdrom0, you dont report that... odd.
# dmesg should completely show what device type is discovered/recognized, (please use a pastebin to post that long output) don't forget however that blueray support in Linux is limited for free IF at all, I know that commercial programs for Linux exist which fully support BD, On it vanilla jacks I don't think so. I am not familiar with your app makemkv you used. but that's all I can say since for Linux installs blueray is not what I would suggest for time being. I am sure some others would have different opinions.
However if it worked with the previous kernel maybe if the old saying if it isn't broke don't fix it, applies? Boot the old kernel and see. And please don't ask how to boot your old kernel as I wont reply.
- pinthenet - 2009-12-15 08:49
Thanks, I'll look into that at home tomight. I failry certain that /dev/sr0 is reported in dmesg, but I als have /cdrom, /media/cdrom / /media/cdrom0
With regard to booting the old kernel (don't worry): unfortunately the reason I have the new kernel is that my update of XBMC beta 1 to beta 2 failed and I reinstalled from scratch leaving me with only the .17 kernel.....
- X3lectric - 2009-12-15 14:43
pinthenet Wrote:Thanks, I'll look into that at home tomight. I failry certain that /dev/sr0 is reported in dmesg, but I als have /cdrom, /media/cdrom / /media/cdrom0
yes the device is sr0 the rest is what formats the device supports, but Linux and BD let me more specific its about the dvd being decrypted Linux itself supports the formats. read more here
Im pretty sure it can be done and as for your .17 kernel theoretically it should work. mind im not about to or want to get into the legalities of achieving this and if you want please feel free to start own topic in how to get around this if you want though I suspect most savvy users already do it.
In a fully fledged desktop like Ubuntu this is straight, fwd however on a minimal install with just XBMC now that would be a treat for you BD users.
HOWEVER>>>> For readers pls do not start a discussion on this topic about the posted below this line. Thanks for respecting that.
But me being me I rather like this article I suggest its ppl that adopt their force-fed formats and technologies on ppl who are not aware of what it all really entails. http://bluraysucks.com/ and further on that link you get to this DRM more important than human life I suggest you have a read of that and if at all humanly possible get a non BD version of your box.
And that's all I am willing to discuss about BD and HD and if any you people are humans the you will stand alongside the real human side of the crowd lot.
- Novin - 2009-12-16 09:51
Since many cannot load the kernel module that is suggested in this thread and since it's also very stupid to load kernel modules downloaded off the Internet it's better to compile it yourself, it's fast and easy.
Follow this forum post: http://ubuntuforums.org/showthread.php?p=8507775#post8507775
- Novin - 2009-12-16 09:54
Easier way to get the GPU temp, no need to install/alter anything:
Is wood made out of trees? - X3lectric - 2009-12-16 13:36
Novin Wrote:Since many cannot load the kernel module that is suggested in this thread and since it's also very stupid to load kernel modules downloaded off the Internet it's better to compile it yourself, it's fast and easy.
Erm you cannot load the prepatched file onto karmic kernels because their buggy so compiling the module onto the kernel is the temp solution, However....
The kernel module downloaded off the internet is the result of the patch you suggest on your link in fact both the coretemp.patch and the prepatched module are downloaded from same placeholder
or pre-patched file
Which one is stupid exactly, which one is infected by rootkits? Show me the money!! I have a hard time distinguishing the forest from the trees. So your trusting the patch but not the prepatched file?! Funny this or is it just me? In order to determine what's going on you have to actually understand what's is going on with the patch file itself (I dont believe you do otherwise you wouldn't post stuff like that) and when you compare the patch and the result you know there's no rootkits in neither file except for the kernel strings it will show, I have to say this sounds a bit like scaremongering for any un-clued ppl reading, so I though I would gently open the tall grass and let you have a look at the whole scenery.
$ strings coretemp.ko | grep vermagic
and that will tell you what kernel it was compiled on.
Also your link-suggestion is incomplete it doesn't tell you what file actually needs patching following that to the letter errors out I know I been there I read that topic way b4 I started this one, seems like you posted there as well. Anywho!
If you can post a complete step by step in how to use your http://ubuntuforums.org/showthread.php?p=8507775#post8507775 from start to finish without errors then please post don't forget the kernel versions mentioned there are not necessarily the ones people will be using here.
Novin Wrote:Easier way to get the GPU temp, no need to install/alter anything:
Yes that suggestion as been posted on post 22 of this topic http://forum.xbmc.org/showpost.php?p=442559&postcount=22
Yes you right like I posted no need to intall something just to get the temperatures for GPU but nvclock does much more and since I use that extra functionality (e.g. When I login I get a status of all my hardware on terminal, I thought it would be best to share when I have more time I will post how to do that here.
Also if you read I personally have an problem running nvidia-settings -c :0 -tq GPUCoreTemp errors out display not connected. thus far no one presented solutions, maybe you can?
So if I just want the temperatures I can also do nvidia-smi -lsa no need to install anything for that either and has been documented on the starter posts.
Again Thx for your posts and valuable input will be looking forward for your how to's I cant wait...
- Novin - 2009-12-16 15:24
X3lectric Wrote:Erm you cannot load the prepatched file onto karmic kernels because their buggy so compiling the module onto the kernel is the temp solution, However....
First I don't see anything buggy in Karmic, you just cannot load kernel modules compiled for a different version than the one you are running. This is probably by design.
If I download a patch, this is plaintext. I can just look at it to determine what it does. If you look at http://mabene.icomedias.com/coretemp.patch you can quite easily determine that it does what you think it would. I'm not saying that the linked coretemp.ko is infected by a rootkit, I'm just saying that it could be and that you should be very careful to download kernel modules from other than official sources.
Running strings and looking at the version doesn't tell you anything, just that it is a kernel module of some version (which the hypothetical rootkit would also be).
Ubuntuforums is offline right now so I cannot look at my forum post there but IIRC I do 'patch -p1 <../coretemp.patch' and that is what patches coretemp.c in drivers/hwmon of the kernel source. I think you can follow my example and have a working coretemp.ko after that. Right now my example only works on Karmic but I can update it to also work on Jaunty (or any other really..).