LinuxMCE Forums
General => Installation issues => Topic started by: maverick0815 on October 18, 2009, 07:43:53 pm
-
Hi guys,
this is my beta-experience so far:
To get the hybrid/ core running so far as I have now, I had a few installations to do.
This is what I did: Installed from the DVD - choose Install Linuxmce
When that was done, I installed my TV-card (nova hd s2- as detailed in the wiki)
Then I rebooted and continued with the install of Linuxmce from the desktop
Ran through the AVWizard and selected basic UI, next I setup Mythtv
After the basic setup of Mythtv was done and I confirmed to receive TV on the hybrid, I went to the KDE-Desktop and
activated the latest nvidia-drivers (190.32). Doing that earlier resulted in fubar, because the orbiter wouldn't load and instead I got messages from
the dcerouter, that it tried to install the 180-drivers for some reason...I found out, that the 180-glx packages was supposed to be broken.
So far my remaining issues are those :
minor- mythweb says that www-data has no permissions to write to the data-directory - so right now I cannot access the channel-table to edit.
major- I cannot setup my MD, because I get messages like : kernel image could not be found. As mentioned in another thread, I can confirm that there are files missing in /tftpboot/pxelinux.cfg/ in fact it is empty... also I checked under /usr/pluto...there isn't even a directory diskless
I tried to manually add a mediadirector with the webadmin (under 7.10 entering the mac of the MD got the creation of the image started), but I was unsuccessful.
So far I cannot setup my MD.
Before I tried the new DVD I had the latest Alpha running, but doing an upgrade first destroyed Mythtv, because the avenard-repo made a change from mythtv.21 to a prerelease .22
It got really nice optics, but destroyed the mythconverg database, because it wanted to do an upgrade to the database-schema and failed. That's when I decided to give the DVD a run..much to my amazement I found out, that the new mythtv was already integrated.
So right now I don't know what do to....any ideas on how to get my MD setup ?
---------------------
update: I ran /usr/pluto/bin/Diskless_BuildDefaultImage.sh
that at least put the missing files and directories - I just noticed, that in /tftpboot I now have even a directory default, which wasn't there before.
when I now boot the MD I get Diskless setup failed. My MD is an ASROCK Ion330- now this is am64 capabable, but as we all know our LinuxMCE is 32bit, however it seems since the last alpha it keeps reporting as amd64 instead of i386....last time I had to manually change it to i386, which helped....lets see now
--------------------------
so far no change.....diskless setup failed...no matter how many times I try..delete the md, reload router, start md, receive error, repeat...
-
I just regenerated my orbiters....the hybrid says, that there are some devices, that have not started correctly...
-
I have the same problems. I searched the forum and tried al lot of things to get at least one MD going but no luck so far. I 'm up to my 15th reinstall of the core but I' very doubtfull this will work. Also I noticed there is no /usr/Pluto/Diskless folder and can't find the Diskless folder anywhere else. Is this normal?
-
Hi,
There is no diskless directory until you create an MD.
-
small update on mythweb: I set the owner of /usr/share/mythtv/mythweb/data to www.data
now at least mythweb is working and I can sort my channels again
other than that, I can't get the md up
like I said before:
I tried to create an MD from the webadmin- I get diskless setup failed.
I deleted the MD, reloaded the router and just tried the official way- which worked in the alpha until the latest upgrade...
The MD announced itself to the router and obviously reported itself back as amd64 instead of i386- I get diskless setup failed
The webadmin shows the md as amd64, I go to advanced, change it i386, save, update, rebuild image, start the md, diskless setup failed
all the while no diskless directory has been created..something got stuck and won't budge
---------------
did anyone chack what happens when you do apt-get update?
It seems some of the repositories aren't working....
Failed to fetch http://archive.ubuntu.com/ubuntu/dists/universe/main/binary-i386/Packages.gz 404 Not Found [IP: 91.189.88.30 80]
-
major- I cannot setup my MD, because I get messages like : kernel image could not be found. As mentioned in another thread, I can confirm that there are files missing in /tftpboot/pxelinux.cfg/ in fact it is empty... also I checked under /usr/pluto...there isn't even a directory diskless
<snip>
---------------------
update: I ran /usr/pluto/bin/Diskless_BuildDefaultImage.sh
that at least put the missing files and directories - I just noticed, that in /tftpboot I now have even a directory default, which wasn't there before.
when I now boot the MD I get Diskless setup failed.
--------------------------
so far no change.....diskless setup failed...no matter how many times I try..delete the md, reload router, start md, receive error, repeat...
Hey maverick0815 - FWIW same problem and flow for me using a Asus Eee Box (202) and 0810 beta.... (Diskless setup failed after announcing to router)
-
Perhaps some older code slipped inside the DVD-install.
Besides, did anyone try the windows orbiter? I noticed, that there are no binaries included with the install. Also on the windows orbiter I got no media buttons whatsoever- I have only Telecom and I believe security visible there.
-
For those having MD creation issues following a DVD Beta install, have you read: http://wiki.linuxmce.org/index.php/LinuxMCE-0810_beta
You need to create the initial MD image by running the script: /usr/pluto/bin/Diskless_CreateTBZ.sh before any MDs can be created.
J.
-
For those having MD creation issues following a DVD Beta install, have you read: http://wiki.linuxmce.org/index.php/LinuxMCE-0810_beta
You need to create the initial MD image by running the script: /usr/pluto/bin/Diskless_CreateTBZ.sh before any MDs can be created.
J.
I do have Myth installed but I get stuck here;
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
pluto-mythtv-player: PreDepends: mythtv-backend but it is not going to be installed
PreDepends: mythtv-frontend but it is not going to be installed
E: Broken packages
#### Package pluto-mythtv-player failed (/tmp/tmp.lFSpF13245) - We wait 10sec and try again - to stop retrying press Ctrl-C.
-
For those having MD creation issues following a DVD Beta install, have you read: http://wiki.linuxmce.org/index.php/LinuxMCE-0810_beta
You need to create the initial MD image by running the script: /usr/pluto/bin/Diskless_CreateTBZ.sh before any MDs can be created.
J.
I do have Myth installed but I get stuck here;
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
pluto-mythtv-player: PreDepends: mythtv-backend but it is not going to be installed
PreDepends: mythtv-frontend but it is not going to be installed
E: Broken packages
#### Package pluto-mythtv-player failed (/tmp/tmp.lFSpF13245) - We wait 10sec and try again - to stop retrying press Ctrl-C.
I have the same problem with the Mythtv packages. Left it for 15 min but kept repeating the message. Stil no MD running
-
I can confirm this...I have the same issue here now
broken packages...mythtvfrontend and mythtvbackend
---------------------------
Another question is: would this be the same, if we went back to the alpha-installation?
-
I'm taking a stab in the dark here but if your having the mythtv installation problems can you check your /etc/apt/sources.list file. Specifically the avenard repo.
3 or 4 days ago the avenard repository changed and the 'testing' repository is now tracking myth 0.22 fixes rather than myth 0.21 fixes as it had been. This could be causing a dependency problem on your installation.
Try remove 'testing' from the avenard repo line, if it exists, and be sure you leave 'release' (which is still tracking the 0.21 fixes).
Alpha 2.37 does not appear to have the avenard repo enabled at all. I installed Alpha 2.37 2 days ago and did not experience this issue and the avenard repo was not enabled by default. Try removing the 'testing' repo from you sources.list before bailing on the dvd install.
J.
-
well, to change to 0.21 would be quite problematic. The core already runs on 0.22 by default now. I ran into this problem when I last did an upgrade with the alpha. I was quite surprised, when I suddenly had a totally different mythtv... then I was dismayed, because it screwed around with the database. It wanted to upgrade the database, because the installed database was 29 versions behind...the upgrade didn't go through, so I dropped the database in mysql and created a new one...from there things didn't really go any better...
Essentially you proposal would mean to probably reinstall the whole core and change the sources there, which might have further implications, because I assume the developers thought about something, when they included the avenard repo testing...from there you will also get the latest nvidia-drivers. As I also saw there are some problems with nvidia-180-glx, which is also broken.
As far as I understand, currently there is no easy solution for this...except if you switch from mythtv to vdr, perhaps.
-
Essentially you proposal would mean to probably reinstall the whole core and change the sources there, which might have further implications, because I assume the developers thought about something, when they included the avenard repo testing...from there you will also get the latest nvidia-drivers. As I also saw there are some problems with nvidia-180-glx, which is also broken.
As far as I understand, currently there is no easy solution for this...except if you switch from mythtv to vdr, perhaps.
I believe the 'testing' repository was added to the DVD install before the avenard repository changed to 0.22-fixes. I could be wrong but I hadn't heard anything about support for 0.22 within LMCE0810. See: http://avenard.com/media/Ubuntu_Repository/Entries/2009/10/15_MythTV_0.22-fixes_RC1_in_testing.html
The nvidia-180-glx package is also from the avenard repository and has also undergone changes in the last few days. A checkout using the 'release' repo from avenard repo does work. Individuals requiring vdpau will have to manually install libvdpau0. See: http://avenard.com/media/Ubuntu_Repository/Entries/2009/10/4_VDPAU_packages.html
J.
-
did you also check this
:http://avenard.com/media/Ubuntu_Repository/Entries/2009/8/27_Trunk___MythTV.html ?
to go back, you'd have to do some major work....I tried that one before last Friday and it didn't really work out...that was exactly the reason, why I did try the DVD.
I imagine quite a number of people have the same problem right now and I don't think that this is really a solution. In this situation I'd rather wait for the devs to come up with something.
Either they can modify the setup to avoid going to mythtv 0.22 or they find a way to go with it. The first alternative would make me do a new install, the second might be a dist-upgrade.
Right now I'd rather not try the above mentioned method, because there is a high chance of screwing up more while trying to fix it and then having to reinstall everything again- something I'm not looking forward to.
My bet is, we will be seeing a new dvd soon or something like it, because there are a number of things missing or not working properly, unlike with the last alpha.
-
did you also check this :http://avenard.com/media/Ubuntu_Repository/Entries/2009/8/27_Trunk___MythTV.html ?
to go back, you'd have to do some major work....I tried that one before last Friday and it didn't really work out...that was exactly the reason, why I did try the DVD.
I have read that. Looks like the removal would introduce other problems.
J.
-
so I guess we'll have to wait for a while, because I don't think a reinstall would fix it, because the sources are coded in the installerscripts, right?
-
okay...now even the core is acting up...yesterday I could at least watch something there...now it seems the nvidia drivers crashed or somthing like that.
if I use the alpha-installer, will I run into the same problems, or will it be working without the hiccups from the DVD- because now I'm really in for another install it seems.
-
I installed alpha 2.37 the other day without a hitch. I had to enable the avenard repo manually to use vdpau, I only enabled 'release' and got mythtv 0.21-fixes. It looks like mythtv in LMCE is in transition to 0.22 from the avenard 'testing' repo and I was just behind on the info. ;D
-
...from there you will also get the latest nvidia-drivers. As I also saw there are some problems with nvidia-180-glx, which is also broken.
As far as I understand, currently there is no easy solution for this...except if you switch from mythtv to vdr, perhaps.
actually my main MD (Core/Hybrid) stopped working last night as well. The screen is just black with the white cursor (arrow). I have tried a few things to no avail - and noticed that nvidia-180-glx seemed to be busted also... Anyone else got this?
-
After a while I of fiddling around I got the core working again, but only with basic skin and static ui. I checked out the nvidia-drivers, but I could not activate any of them. I will most probably make a new install tonight and go back to alpha. After seeing the new mythtv, i am a little reluctant though to go back to the "old" one..it looked quite nifty so far....too bad.
-------------------------
I just saw this on trac :http://svn.linuxmce.org/trac.cgi/ticket/379
very interesting, I just wonder how this will affect the building of the bootimage for the MD, since there seems to be a problem with those packages, at least in the beta...don't know about the alpha
-
After a while I of fiddling around I got the core working again, but only with basic skin and static ui. I checked out the nvidia-drivers, but I could not activate any of them. I will most probably make a new install tonight and go back to alpha. After seeing the new mythtv, i am a little reluctant though to go back to the "old" one..it looked quite nifty so far....too bad.
-------------------------
I just saw this on trac :http://svn.linuxmce.org/trac.cgi/ticket/379
very interesting, I just wonder how this will affect the building of the bootimage for the MD, since there seems to be a problem with those packages, at least in the beta...don't know about the alpha
That ticket was closed yesterday evening at the request of phenigma, only reason given was "invalid" so sounds like there is not a problem with the mythtv repository. Hopefully phenigma can shed some light on this matter
NOS.
-
Well, I found this very interesting, because I thought the new mythtv was more like an "accident", especially considering the trouble it causes with the generation of the initial boot image for the Md in the beta.
Anyways, I'm in the middle of setting up with the alpha-script, hopefully this works better and lets me setup my MD successfully again. By the way, does anybody know if the v4l package has been updated too? The repo I found and described in the wiki (for the nova hd s2) seems pretty interesting and is supposed to get you s2-channels...if there is something similar included already, shouldn't it be enough to just put the firmware in its proper place and reboot?
-
Well, I found this very interesting, because I thought the new mythtv was more like an "accident", especially considering the trouble it causes with the generation of the initial boot image for the Md in the beta.
Anyways, I'm in the middle of setting up with the alpha-script, hopefully this works better and lets me setup my MD successfully again. By the way, does anybody know if the v4l package has been updated too? The repo I found and described in the wiki (for the nova hd s2) seems pretty interesting and is supposed to get you s2-channels...if there is something similar included already, shouldn't it be enough to just put the firmware in its proper place and reboot?
I thought the new mythtv was an accident as well, it had caused me issues on my ION board which had been using the avenard 'testing' repo when neither my core nor my other md used the avenard repos at all. I asked for the tickets to be closed after confirming that the switch is intentional.
When installing using the beta dvd the avenard 'testing' repo is active and myth is version 0.22. For alpha 2.37 it looks like using a stock LMCE install or using the avenard 'release' repo should work just fine, this would give you myth 0.21. Once the next alpha build is complete it looks like the alphas will need to use the 'testing' repo to stay compatibile with the mythtv protocol changes in svn.
J.
-
am i correct in stating that the only fix is going back to alpha 2.37?
-
thats what I did..anything else is probably not a good idea, since it will break a lot of things.
-
Did anyone of you try the windows orbiter? In the latest alpha as well as in the beta-dvd, there are no media buttons...the only thing visible is telecom and security.
-
Did anyone of you try the windows orbiter? In the latest alpha as well as in the beta-dvd, there are no media buttons...the only thing visible is telecom and security.
For a moment I had a Core running (but failed to install MD). When the core was up and running I tried the orbitter and it looked just fine. Seems like problems are very different for individual users.
-
Did anyone of you try the windows orbiter? In the latest alpha as well as in the beta-dvd, there are no media buttons...the only thing visible is telecom and security.
No problems here, I didn't re-install the orbiter software on my windows machine, it was there from a previous installation. I simply let the windows orbiter set itself up as a new orbiter in my new installation.
-
hmm, thats interesting...I will try the mobile orbiter on my n810....the onscreen orbiters are also fine...only the ones on windows are behaving oddly.
On a positive side, the didn't produce an error message unlike with the alpha on windows7
-
The Nokia N810 runs a standard Orbiter, not a mobile one.
-Thom
-
of course, my mistake :-)
-------------------------------
since I cracked my system accidentally last Friday with the updated mythtv I became a bit hesitant, but I can't help but wonder....how the existing installs from the alpha will make the shift to that one. If I could backup my exisiting install completely, I would like to try again. I think what caused most of the headache was the fact, that my MD first got the new version and I was scrambling to get my core to comply. Before I killed the beta-install I made a dump of the mythconverg, so that in case I could restore it again in a new install...I got pretty tired watching the progressbar for the tuning grow ever so slowly :-)
In theory I could just change the avenard repo to "release testing", drop the current mythconverg and do a aptitude update and aptitude dist-upgrade,reboot,restore my backup of the mythconverg and then proceed with the update of the MD
Right now I have a spare 200Gb hdd sitting around, which I could use to do a complete backup....any suggestion, what to use for that?
-
Hey maverick0815 - FWIW same problem and flow for me using a Asus Eee Box (202) and 0810 beta.... (Diskless setup failed after announcing to router)
[/quote]
Same here - Diskless Setup Failed. Any ideas how to get round this?
-
Same here - Diskless Setup Failed. Any ideas how to get round this?
Check this post: http://forum.linuxmce.org/index.php?topic=8425.msg61787#msg61787
J.
-
Cheers, will have a look at that tonight.
-
Right now everything is running A-okay again, even the windows orbiter - don't know why it didn't show the media buttons right away.
Anyways, I had some minor issue with Mythtv on the MD, but I could resolve it again with this one:
http://forum.linuxmce.org/index.php?topic=8971.msg61434#msg61434in case someone runs into this problem again
-
After reading all you peoples tips I finally managed to get passed the 'Diskless Setup Failed' message. The MD set up for a long time and now wants to try to load the AV Wizard but it fails and gives a Blue screen with the message 'AVWizard Failed to setup X' I searched the forum for this problem and found a lot of threads about this problem. I've tried a number of possible solutions like manually installing the latest Nvidia driver on the MD but I get stuck with the same message again. Maybe I should mention that my Core has no Nvidia graphics card (it's an Intel MB with onboard graphics) because I'm not using my Core for video playback. I tried this thread http://forum.linuxmce.org/index.php?topic=8460.msg56517#msg56517 and it worked fine but when I tried the 'dpkg-reconfigure -phigh xorg-server' it says: /usr/sbin/dpkg-reconfigure: xorg-server is not installed. Again I searched the forum for this but can't seem to find a solution.
I've got so far so i really would like to get to the AV Wizard. Any suggestions?
Thanks for the help so far
-
I tried this thread http://forum.linuxmce.org/index.php?topic=8460.msg56517#msg56517 and it worked fine but when I tried the 'dpkg-reconfigure -phigh xorg-server' it says: /usr/sbin/dpkg-reconfigure: xorg-server is not installed. Again I searched the forum for this but can't seem to find a solution.
I've got so far so i really would like to get to the AV Wizard. Any suggestions?
I've not attempted this myself but the package xorg-server is not a known package in ubuntu. Try xserver-xorg, I think that's the package you want.
J.
-
After reading all you peoples tips I finally managed to get passed the 'Diskless Setup Failed' message. The MD set up for a long time and now wants to try to load the AV Wizard but it fails and gives a Blue screen with the message 'AVWizard Failed to setup X' I searched the forum for this problem and found a lot of threads about this problem. I've tried a number of possible solutions like manually installing the latest Nvidia driver on the MD but I get stuck with the same message again. Maybe I should mention that my Core has no Nvidia graphics card (it's an Intel MB with onboard graphics) because I'm not using my Core for video playback. I tried this thread http://forum.linuxmce.org/index.php?topic=8460.msg56517#msg56517 and it worked fine but when I tried the 'dpkg-reconfigure -phigh xorg-server' it says: /usr/sbin/dpkg-reconfigure: xorg-server is not installed. Again I searched the forum for this but can't seem to find a solution.
I've got so far so i really would like to get to the AV Wizard. Any suggestions?
Thanks for the help so far
same problem, mine is a intel board using a sis chip, dont think nvidia drivers will apply, would it? its a D201GLY2 board and it was giving me ui2 (not so good though) with the last alpha release.
-
After reading all you peoples tips I finally managed to get passed the 'Diskless Setup Failed' message. The MD set up for a long time and now wants to try to load the AV Wizard but it fails and gives a Blue screen with the message 'AVWizard Failed to setup X'
Am now in exactly the same situation.
I did try having a play with the hardware acceleration options in LMCE Admin, but it didn't seem to make any difference.
May I also say thanks for all of the help so far. Am trying to add relevant information to the wiki as we go.
-
@Thingie
If I am not mistaken, the thread you referred to was for 7.10. I don't think you need to do any of this on 8.10. But one thing after another...if you don't want to use your core for playback, then you don't need to invest too much work with drivers there. For starters, I would suggest you use basic skin and the UI1 with static images for your core. Should you decide later on to use it, you can still try this later. I used to have an eee-box before, which also used an Intel graphics chipset, but that handled only UI2 with overlay.
About your MD, I suggest also for start ui1 and static images. Use this to setup your MD. Once your orbiter is setup completely, you can go to KDE-desktop and check with your restricted drivers. I also had some trouble at first with my ASROCK Ion 330- I couldn't even activate the restricted drivers.
I put the avenard release repository, did apt-get update, apt-get dist-upgrade and reboot. After that, I went to the KDE-Desktop again, opened a terminal and did nvidia-xconfig, which wrote me a new xorg.conf. With the next reboot I forced the AVWizard and set it up to fullHD and UI2 with alpha-blending.
Try it out and let me know if it helped.
----------
Now I have a question of my own: When I'm watching TV or movie, after some minutes the screensaver seems to kick in and blacks out my TV..how can I keep this from happening?
-
do you have a device template for your TV? This should not be happening at all, is the KDE desktop active while you're doing this? If so, you should disable its screensaver completely.
-Thomq
-
After reading all you peoples tips I finally managed to get passed the 'Diskless Setup Failed' message. The MD set up for a long time and now wants to try to load the AV Wizard but it fails and gives a Blue screen with the message 'AVWizard Failed to setup X'
Am now in exactly the same situation.
I did try having a play with the hardware acceleration options in LinuxMCE Admin, but it didn't seem to make any difference.
May I also say thanks for all of the help so far. Am trying to add relevant information to the wiki as we go.
well i tried another md, same result. has anybody got an md working or solution?
-
After reading all you peoples tips I finally managed to get passed the 'Diskless Setup Failed' message. The MD set up for a long time and now wants to try to load the AV Wizard but it fails and gives a Blue screen with the message 'AVWizard Failed to setup X'
Am now in exactly the same situation.
I did try having a play with the hardware acceleration options in LinuxMCE Admin, but it didn't seem to make any difference.
May I also say thanks for all of the help so far. Am trying to add relevant information to the wiki as we go.
well i tried another md, same result. has anybody got an md working or solution?
updated beta......same problem here too
-
About your MD, I suggest also for start ui1 and static images. Use this to setup your MD. Once your orbiter is setup completely, you can go to KDE-desktop and check with your restricted drivers. I also had some trouble at first with my ASROCK Ion 330- I couldn't even activate the restricted drivers.
I put the avenard release repository, did apt-get update, apt-get dist-upgrade and reboot. After that, I went to the KDE-Desktop again, opened a terminal and did nvidia-xconfig, which wrote me a new xorg.conf. With the next reboot I forced the AVWizard and set it up to fullHD and UI2 with alpha-blending.
Try it out and let me know if it helped.
How can I choose UI1 and static images if all I get is the 'Failed to setup X' screen? I never see anything of the AVwizard.
-
@Thingie,
okay...lets take this one at a time....
can I assume you have the core running so far, or do you have issues with the avwizard there too?
Then, what kind of MD are you running? I didn't see your hardware so far. Perhaps if you can elaborate on that one, maybe we can figure out, what drivers you need...or what causes your issues.
-
@Thingie,
okay...lets take this one at a time....
can I assume you have the core running so far, or do you have issues with the avwizard there too?
Then, what kind of MD are you running? I didn't see your hardware so far. Perhaps if you can elaborate on that one, maybe we can figure out, what drivers you need...or what causes your issues.
Ok maybe I should be more clear about my setup.
Core:
Intel mb (DG45CB) (http://www.intel.com/cd/products/services/emea/eng/motherboards/desktop/403009.htm (http://www.intel.com/cd/products/services/emea/eng/motherboards/desktop/403009.htm))
Core2Duo 2.5GHz CPU
2GB ram
One 160GB sata HD
2 x NIC (one onboard and one PCI)
AV wizard worked just fine
I use the onboard graphics with UI1 and it runs very smoothly.
MD:
Intel mb (DQ965GF) (http://downloadmirror.intel.com/15033/eng/DQ965GF_TechProdSpec.pdf (http://downloadmirror.intel.com/15033/eng/DQ965GF_TechProdSpec.pdf))
Core2Duo 2.2GHz CPU
2GB RAM
No HD
Nvidia 7600GS 512MB PCI-e
Audigy PCI
When loading AV Wizard 'Failed to setup X' message.
Thanks
-
I've had some troulbe too with getting nvidia drivers to cooperate. When you boot your md and finally the x-setup failed, try ctrl+alt+f1 or f2..it should give you the login
login there with linuxmce then do sudo apt-get update then sudo apt-get dist-upgrade. when you're done with that, reboot and if thex-setup fails yet again, go again to the console like before and do a sudo nvidia-xconfig.
lets see if that will help
-
well, about my screensaver problem- it only occurs if the kde-desktop has been used prior to watching anything. In my case I just used my windows orbiter to regenerate the onscreen orbiter, because that seemed to be the easiest way for me to get it back
-
I've had some troulbe too with getting nvidia drivers to cooperate. When you boot your md and finally the x-setup failed, try ctrl+alt+f1 or f2..it should give you the login
login there with linuxmce then do sudo apt-get update then sudo apt-get dist-upgrade. when you're done with that, reboot and if thex-setup fails yet again, go again to the console like before and do a sudo nvidia-xconfig.
lets see if that will help
I am trying to go through these steps as I am also stuck on the blue scree with a "Failed to setup X" message. At ctrl+alt+F1 I cannot do ctrl-C. At ctrl+alt+F2 the prompt is sambahelper@moon42. It does not accept any password that I enter. Does it have it's own default password?
Never mind... Got the answer here:
http://forum.linuxmce.org/index.php?topic=8700.20;wap2
Thanks to thezfunc and phenigma!
Lev
-
well, about my screensaver problem- it only occurs if the kde-desktop has been used prior to watching anything. In my case I just used my windows orbiter to regenerate the onscreen orbiter, because that seemed to be the easiest way for me to get it back
Did you get your screensave issue resolved? If not, next time you're in KDE, just hit Kickoff, go to System Settings, Desktop, and then under Screen Saver, uncheck Start Automatically.
-
@Levster
sambahelper has an empty password, so just hit enter
@team_steeze
thanks for the tip, I'll try that
-
I've had some troulbe too with getting nvidia drivers to cooperate. When you boot your md and finally the x-setup failed, try ctrl+alt+f1 or f2..it should give you the login
login there with linuxmce then do sudo apt-get update then sudo apt-get dist-upgrade. when you're done with that, reboot and if thex-setup fails yet again, go again to the console like before and do a sudo nvidia-xconfig.
lets see if that will help
Thx Maverick0815, that did the trick. I'm so happy to have a MD running after so many failures. ;D ;D ;D ;D
-
OK. After doing a bit of "running" around the forums, I was finally able to generate successfully my first MD. My MD is running on a Zotac IONITX-A-U Atom N330 board. Nothing extra. I can play video but the quality is sub-par, to say the least. AVIs come in fine, but the mkv files are terrible. Choppy, sound cutting out... Un-watchable.
What should I try next? Upgrade the video drivers on my MD?
I saw the very detailed installation explanation by thezfunk on:
http://forum.linuxmce.org/index.php?topic=8700.20;wap2 but did not go through the motions. The AV setup wizard completed and that is where I left it off.
I did not do anything extra on my MD other than apt-get update and apt-get dist-upgrade.
I know that the issue is not my network as I can stream mkvs to other PCs and my PCH box. I think that the Zotac is much more powerful compared to the PCH, and should easily be able to play MKVs.
By the way, my core is running on an AMD opteron 165 setup with 4GB ram and two 1 gig network cards (one on the board and the other PCI).
Please, any suggestions would be great!
-
As far as I know, VDPAU works only with MythTV so far. I haven't really come across instructions on how to get VDPAU for watching videos. I remember having read that totallymaxed did something like that in the LMCE-flavoured software his company is doing...
-
As far as I know, VDPAU works only with MythTV so far. I haven't really come across instructions on how to get VDPAU for watching videos. I remember having read that totallymaxed did something like that in the LinuxMCE-flavoured software his company is doing...
niz23 has provided patches to the current system to enable VDPAU in Xine and therefor through videos selected within orbiter. The patches have been merged into SVN and I would expect they will be available in the next round of builds. For for information see: http://trac.linuxmce.org/trac.cgi/ticket/383
I've been running with VDPAU on my Zotac IONITX-A-U all week without any issues.
J.
-
As far as I know, VDPAU works only with MythTV so far. I haven't really come across instructions on how to get VDPAU for watching videos. I remember having read that totallymaxed did something like that in the LinuxMCE-flavoured software his company is doing...
niz23 has provided patches to the current system to enable VDPAU in Xine and therefor through videos selected within orbiter. The patches have been merged into SVN and I would expect they will be available in the next round of builds. For for information see: http://trac.linuxmce.org/trac.cgi/ticket/383
I've been running with VDPAU on my Zotac IONITX-A-U all week without any issues.
J.
Phenigma,
As I understand, the following is a step-by-step instruction as to how to "enable" HD playback on Zotac boards:
How to setup VDPAU on MD My setup is a Zotac Atom 330 ION.
1. Make changes to /include/config/hardcoded.php to allow setting of auto and vdpau support as HW acceleration through lmce-admin
2. Setup MD as usual. Configure it and verify that video and sound is working as it should. Not HD content though. That´s what we is going to solve.
3. Add Avenard repot to /etc/apt/sources.list if it is not there.
4. Add Brandon Schniders PPA repo from Launchpad.
5. apt-get update
6. apt-get install nvidia-glx-185 (this is important otherwise the next step will remove your already installed nvidia driver)
7. apt-get dist-upgrade (will install some new binaries including updated mplayer packages from Avenard and libxine-1.1.16.3 with vdpau support from B Schnider)
8. Modify /etc/pluto/xine.conf, change video.driver:xv to video.driver:auto (must be done otherwise xine always start with xv based rendering)
9. Same as above but do it in /root/.xine/config (don´t know if this step is really necessary)
10. Reboot MD
When it comes up test a mpeg-4 HD movie.
If you have a ION gpu or equivalent you can also test mpeg-2 content.
Seems like mpeg-2 content use more cpu compared to mpeg-4. About twice as much.
It´s not much since a 1080P mpeg-4 with vdpau offload use around 5% cpu.
Can you explain the 1st, 3rd, 4th, and 9th step in a bit more detail? I am not sure I understand due to my lack of Linux experience, what it means Make changes to /include/config/hardcoded.php to allow setting of auto and vdpau support as HW acceleration through lmce-admin and so forth. I think that just a little more detail would do. Also, are there any other steps that need to be performed?
Thanks,
Lev
-
Can you explain the 1st, 3rd, 4th, and 9th step in a bit more detail? I am not sure I understand due to my lack of Linux experience, what it means Make changes to /include/config/hardcoded.php to allow setting of auto and vdpau support as HW acceleration through lmce-admin and so forth. I think that just a little more detail would do. Also, are there any other steps that need to be performed?
This is not supported by the devs in any way untill it's released and I don't really recommend this is if you don't know what you're doing but... if you really can't wait.
1) The file to edit is on the core under the /var/www/lmce-admin directory, it's part of the webadmin configuration.
3) Add the avenard repo, see: http://wiki.linuxmce.org/index.php/ZOTAC_ION
4) I think brandons builds are in the nvidia-vdpau launchpad ppa repo, google search should find it with instructions for adding it.
9) Do the same as step 8 only to the file referenced in step 9.
Step 1 is performed on the core, all other steps on the MD that has vdpau capabilities.
J.
-
This is not supported by the devs in any way untill it's released and I don't really recommend this is if you don't know what you're doing but... if you really can't wait.
I do not mind waiting for the official release, as long as it is not too long. I definitely do not want to screw up the core...
-
Any idea when the 810 beta 2 will be released? As I understand it that version is supposed to fix some of the issues that are in the 810 beta relating to MKV playback.
-
Any idea when the 810 beta 2 will be released? As I understand it that version is supposed to fix some of the issues that are in the 810 beta relating to MKV playback.
The devs have been working extremely hard to quash some large bugs and overcome issues introduced by changes in third party repositories. I am certain that as soon as a viable dvd install is ready the next beta will be announced and released.
J.
-
levster,
Any idea when the 810 beta 2 will be released? As I understand it that version is supposed to fix some of the issues that are in the 810 beta relating to MKV playback.
Don´t hope to much re mkv´s.
The problem is libxine itself that do not support it fully at the moment.
This will change in libxine 1.2 which far away for now and will not be part of lmce0810.
There might be way to work around this limit. But for now I cannot say if it can be done or not.
/niz23
-
levster,
Any idea when the 810 beta 2 will be released? As I understand it that version is supposed to fix some of the issues that are in the 810 beta relating to MKV playback.
Don´t hope to much re mkv´s.
The problem is libxine itself that do not support it fully at the moment.
This will change in libxine 1.2 which far away for now and will not be part of lmce0810.
There might be way to work around this limit. But for now I cannot say if it can be done or not.
/niz23
Thank you. MKV playback was one of the main reasons why I wanted to try LinuxMCE. Today, most of the "bundled" HD content is in form of an MKV. I've seen other users on this and other forums go through some pains-taking steps to rectify this issue, but the advice remained the same - unless you really know what you are doing, don't try it. I don't know. If MKV playback is such an important feature that I need, maybe I should try those steps and not wait for the "official" fix?
Lev