2009-12-19, 23:34
FireMan Wrote:Hi flxfxp,
I agree with X3lectric: actual karmic kernel has some issues with ION chipset. If you grep for nForce in /var/log/syslog will return something like:
But I don't experiment any problem related to this issues. No hi CPU loads, no hangs, the time to copy files from (and to) USB are the same etc. The only real problem I found was related to lm-sensor (nothing to do with XBMC).Code:Dec 19 18:09:06 ASROCK2 kernel: [ 4.659537] ACPI: I/O resource nForce2_smbus [0x4e00-0x4e3f] conflicts with ACPI region SM00 [0x4e00-0x4e3f]
This bug was reported to Ubuntu and affects other NVidia's chipset beside ION.
Anyway, this bug has a workaround, according with this site:
http://ubuntuforum-pt.org/index.php?topic=59009.0 (sorry, but isn't in English)
I will try the workaround ("acpi_enforce_resources=lax" as kernel parameter) when switch back to karmic (I've give another try with 9.04).
Yesterday, like I said in a early post, I use your script to install in a friend's ASRock. I got 2 problems: vdpau wasn't working and USB isn't automounting.
The 1st problem was solved running and installing again. Probably, the files need are so fresh that aren't available at that time. But now NVidia's 190.53 are working with vdpau.
The 2nd problem has nothing to do with the script: USB automount look's broken in RC1! It was working in my ASRock and my desktop in beta2, but isn't working anymore after update to RC1 (i din't use the script to update, just to be sure).
According with X3lectric the script works with jaunty, but I can garanty it isn't. And has nothing to do with keyservers. As you said, it stopped to work after beta1.
After install and reboot xbmc will not start. And, if you run startx you will receive the following error like:
So, to finish, your script is working fine in karmic. Including the auto start part. The only problem I've found was the USB automount which I believe is related with XBMC and not the script.Code:xbmc@ASROCK2:~$ startx
exec: 5: /usr/bin/X11/X: not found
giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
Thanks for your hard work!
cheers,
FireMan.
http://forum.xbmc.org/showthread.php?p=4...post461927
hers some fixes but laxing the kernel will not really solve things the underlying issue is with modules and acpi banging same IO ports at same time which is not fixed though it may seem to be fixed it can really damage stuff, thats my friend is really bad. up 2 you if you wanna lucky it out....
enjoy all the fish