Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - maverick0815

Pages: 1 ... 4 5 [6] 7
76
Users / need some help with the phonebook
« on: January 05, 2010, 07:26:34 pm »
I have slight problem with the phonebook entries. I live in Germany and have a phonenumber like this : 0049 371 1234567
However when I start putting the country code in the first field, what appears in the "dial as" is this: 90110049
I don't understand what causes the 9011 to appear. I checked in the trunk for the dial pattern, but this is still as I set it: X.
Since I finally managed to get the asterisk to talk to my fritzbox via sip, I would really like to start filling in the phonebook.

77
Installation issues / a question about sources
« on: December 07, 2009, 07:43:14 pm »
 Failed to fetch http://archive.ubuntu.com/ubuntu/dists/universe/main/binary-i386/Packages.gz  404 Not Found [IP: 91.189.88.31 80]
anyone else got this for the apt-get updates?
I did a little snooping on that server and found this location instead:
http://archive.ubuntu.com/ubuntu/dists/intrepid/universe/binary-i386/Packages.gz
is this the correct location for that and should we update the sources accordingly?

78
Installation issues / vdpau on ion330
« on: December 04, 2009, 08:08:34 pm »
I have an md running on an ion330. When I'm trying to run any HD-movie, the TV stays black, I can hear sound for about 5 seconds, then the player crashes. Is there a way to check what happens?

79
Installation issues / lmce-mythtv scripts
« on: November 30, 2009, 07:09:34 pm »
upon hearing the great news about the new beta2 (hurray)
I went to update my system- being a lazy slob,  I did a backup beforehand...
I got this in the end:
Quote
Unpacking lmce-mythtv-scripts (from .../lmce-mythtv-scripts_2.0.0.44.09112922522_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/lmce-mythtv-scripts_2.0.0.44.09112922522_i386.deb (--unpack):
 trying to overwrite `/usr/pluto/bin/SaveMythRecording.sh', which is also in package pluto-mythtv-player
Errors were encountered while processing:
 /var/cache/apt/archives/lmce-mythtv-scripts_2.0.0.44.09112922522_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

does anyone know how to fix this, short of a fresh install?

80
Installation issues / asterisk
« on: November 26, 2009, 07:52:04 pm »
I have some issues with asterisk. My router provides ip-telephony via sip....so I setup one account inside my router, I get a username,password and registrar to be used with the ip-telephone. With this I went on to configure asterisk. I created a amp-script as described in the wiki and edited the provider_list.txt. Now when I select the proper provider and type in the required data- I don't get anything there- nothing shows up, so I guess the configuration doesn't get applied.
Does anyone have an idea, on how to get it working?

81
Installation issues / mythtv .22
« on: November 21, 2009, 08:50:58 pm »
I took the plunge with a apt-get dist-upgrade today.
Fortunately I did a complete system-backup with partimage.
I got the new mythtv .22 installed and had to drop the mythconverg database.
After recompiling v4l I also got my tv-card running again, did the station scanning and everything else to get mythtv running.
So far it seemed nice, even on my MD, but its only running for a few seconds. Mostly I get something like this
Quote
video frame buffering failed too many times
at other times it seems, like the frontend cannot find the backend-server and asks if the IP has been setup correctly.
does anyone else has some experience with the new mythtv?

82
Users / safe to dist-upgrade?
« on: November 13, 2009, 06:28:52 pm »
I have the alpha 2.37 installed and today I tried an
apt-get update
apt-get dist-upgrade
so far I had the avenard repo activated. I now noticed that there are a bunch of updates including mythtv 0.22
is it safe to perform the upgrade, or am I going to face some major issues with that? The last time I did this, around the time the beta came out, it really screwed up my system.
I had to recreate the mythtv database and such...so can I do this, or will there be a "safe" upgrade path from the alpha to the beta?

83
Installation issues / beta-problem with MD
« 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...

84
Users / episode tag
« on: October 09, 2009, 05:36:12 pm »
Hello guys,

I've got a question about the episode tag...how am I supposed to use it? I'm tagging my TV-Shows as TV-Shows and they show up, but what will I put in the episode tag- the seaon and the episode number, or the title? I have no idead, really. I know that the plugin for recursively tagging the shows does not work, but I don't know yet how to sensibly handle those.

85
I recently revamped my whole network. My core is now running a athlon 7550 x2 on an Asus M2N-SLI Deluxe with 2 GB ram. In addition today I received an Asrock Ion 330.
I followed the wiki for setting it up with the nvidia-drivers and so far so good.
The big downside I'm facing is, that I don't get any sound at all from neither machine. I have them both hooked up to my sony receiver. The Core is connected with spdif coax, while the MD is using spdif optical. In the webadmin I've set them both to Nvidia HDA. I checked on the core with the alsamixer, that the iec958 is not muted and I cranked the volume up.
On the md I got no such thing, alsamixer shows me only 2 channels: one for PCM one for Front. Interesingly I found in the restricted drivers, that there is an Intel HDA activated, while aplay -l says its Nvidia HDA.
In addition to this mythtv still doesn't want to let me watch TV. The setup complains about the storage groups and the playback quits with "There was a problem displaying this video".
So currently all I can do is watch movies without sound...
Does anyone have any pointers for me, how I can solve any of those issues?
thanks in advance
[edit] the mythtv problem seems to be limited to the MD, TV works on the core...but still without any sound

86
Users / [solved]mythtv has problems, perhaps with storage groups?
« on: October 04, 2009, 08:26:07 pm »
Whenever I open Mythtv on my MD it stops after a few seconds saying, that there was a problem displaying the video.
I checked the Setup many times. So far the only thing I've come up with, is about the storage groups. Whenever I want to leave the setup, it tells me that there are some paths that don't exist. Those are actually the ones from two other disks. I can see them, I can access them, but it seems to me, that Mythtv can't.
The question is, what can I do about it?

87
Users / silly question
« on: September 30, 2009, 09:17:34 am »
I just want to make sure what happens, so just don't bite my head off:
I recently added a new harddisk to my core and told it to use linuxmce filestructure. Now I need to reinstall the the whole system. When the new install finds this drive and asks me to use the linuxmce filestructure again, what happens to the existent content on that disk? Will it be wiped off, or does linuxmce recognize the structure and just put it back where it belongs?

Like I said, I just want to make sure....

88
Installation issues / [SOLVED- at last]eee-box 202 and lmce 8.10
« on: July 21, 2009, 07:28:43 pm »
Last weekend I tried my luck with the latest 8.10 alpha. I installed it on my core and after having done that part successfully proceeded setting up my MD (eee-box 202)
As I read here before it should be supported out of the box, since the drivers for the nic have been included now, unlike in 7.10. So I had high hopes and didn't expect much of a problem.
Unfortunately I got a "kernel-panic - not syncing" I got past the message "We announce ourselves to the core"...shortly before the kernel-panic I noticed eth0 link down.
I read here in the forum, that there might be some issue with ACPI, so I went to the Bios and changed the value (don't remember if it was enabled or disabled) and tried again-without luck

So does anyone here have a eee-box running successfully with 8.10 and if so- how did you make it?

89
Users / SOLVED nova hd s2
« on: July 17, 2009, 05:57:28 pm »
Guys, I am contemplating on making the switch to the current version 8.10 (alpha2?). I am currently running 7.10. So far it is running rather nicely, except for some glitches with my MD (eee-box) where I had to rebuild and patch up the image several times...and some media files which I can't play because they don't show up on the orbiters.
So far so good, the only remaining question is, whether or not my TV-card will be supported out of the box already, or if I have to manually install it, like I had to do on 7.10
Thanks in advance

90
Installation issues / eee box troubles
« on: January 04, 2009, 04:11:53 pm »
Hello friends,

yesterday I became a supposedly happy owner of an Asus eee Box. I read about the pxe-boot issues and tried to replicate the steps in the wiki about the unkown nic together with this one: http://wiki.linuxmce.org/index.php/R8168
I also have two different cpu-architectures running. The Core/Hybrid is running in 64bit and the EEE Box, obviously, 32bit. I manually generated the MD with the Admin-Website. Since LMCE was a bit stubborn and insisted the EEE Box to get only the 64bit-Package, I did some research and found out, that you had to go to Mediadirector-> Advanced (for the appropriate MD)->Device Template View. This will open a pop-up, where you have to edit Entry #112 to i386 as well as #233 to LMCE_MD_u0710_i386 . For the latter you should also tick the Allowed to modify. Save and Close. This will automatically change the 64bit MD to 32bit and generate a new image.
So then I proceeded to follow the instructions to include the correct driver for the NIC. I finally succeeded with the available r8168.ko from Sethj and followed his instructions for the Asus M3A78-EM.
After that the EEE-Box finally started booting....BUT
I get the following error:
nfs: server 192.168.80.1 is not responding, still trying
This goes on for several minutes. Eventually the booting resumes. I can get through the AV-Wizard and complete the setup. As soon as the onscreen-Orbiter starts however, the whole system freezes. I can still move the mouse, but thats about it.
What are your experiences so far with the EEE-Box? Any hints for me, how to do this? Or perhaps this is still a NIC-issue? I also tried to download the Realtek drivers, but the version they are offering is already higher than the one mentioned in the wiki

Pages: 1 ... 4 5 [6] 7