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.


Messages - dison4linux

Pages: [1] 2
1
Users / Raspberry Pi as Media Directory
« on: December 26, 2012, 03:12:26 am »
I'm curious to know how likely it is that it will be possible to use a Raspberry Pi as a Media Director some day.

I have seen that there are 3-4 forum topics related to this as well as 2 wiki pages, but they all seem to describe work on very specific components of the big picture.  I am not a developer so I have a hard time following what is discussed in the forums.  I am a seasoned Linux SA and am also familiar with LinuxMCE.

I am looking more from a high level overview how close things are or if it is even possible.  I'd be more than happy to add content to the wiki pages and participate in any testing, I have two of the 512MB RPs myself.

2
Users / Re: Can't connect to samba shares on 10.04
« on: February 11, 2012, 03:45:53 am »
Are you trying to access the smb shares from the "inside" or "outside"?
If you are connecting from the outside is the firewall disabled or the necessary ports open?

3
Users / Re: Super 1004
« on: January 17, 2012, 03:04:10 pm »
I too am having success with 1004.  I do not use asterisk so I cannot comment on its working.  So far I have working the core/hybrid, two PXE boot MDs, FLAC audio files, DVD rips, Photo Screensaver, Web Orbiter.

After having used Ubuntu Linux as a desktop operating system for every releases starting from 7.04, I am glad to be able to use LinuxMCE atop 10.04, as I believe it is far more stable than 8.10, not to mention the Long-Term-Support.

4
Users / Core Only with TV Tuner?
« on: January 14, 2012, 03:40:53 am »
If you disable the media director from starting on your core (by setting AutostartMedia=0 in /etc/pluto.conf), can you still use TV Tuner cards located in the core on the other media directors?  Or does the media director need to be running in order to "serve" the TV Tuners over the net?

Thanks,
Jon

5
Users / Axis M1031-W
« on: January 23, 2011, 03:24:34 am »
I am looking for some guidance on getting an Axis M1031-W working in LinuxMCE.  As far as I can tell from the WIKI and the Forum, this model of camera is not supported by Plug & Play.  However, as soon as I plugged the camera into the network, I was prompted on orbiter to setup the camera.  After running through the setup questions, I went to the web admin and looked under Devices -> Surveillance Cameras and found that it had been setup in there as device template 1723.  The PATH, PORT, IP, and MAC were filled in and seemed to be correct.  It suggested that the url to my camera feed was http://192.168.80.131/axis-cgi/jpg/image.cgi which seems to be correct because I can go to that URL in a browser and see a still image of my camera feed.  I have also tried switching the PATH to /mjpg/video.mjpg which also seems correct in the browser, but gets me no further in LinuxMCE.  What happens when I click the button that says "AXIS IP CAMERA" in the orbiter is a blue screen comes up with buttons along the bottom for pan and zoom, but there is a big empty spot above them presumable where the image from the camera would be.

Am I missing a simple setup step, or is this model truly not compatible with LinuxMCE.

BTW I have the camera setup to not require a login to view the live feed and I have tried with and without the username/password fields populated on the config in the web-admin.

6
You are interested in getting a 7965 working, right?
I do not believe the 7960 firmware will work for the 7965 phones.

7
What was the file name of the firmware archive that you downloaded?

8
Users / Re: New LMCE sytem help
« on: January 22, 2011, 02:59:23 am »
I don't have any concrete advice, but I have heard that the new ATOM systems with the "Next Generation Ion" graphics are supported. 

I am going to purchase this board:
http://usa.asus.com/product.aspx?P_ID=iIZKMXSj0jZKiebE

And put it in this case which I already own which supports VESA 100x100 mounting if you buy the "special" screws from it.
http://www.mini-box.com/M350-enclosure-with-picoPSU-80-and-60W-adapter

I'll update my post after I try that board to make sure it is supported by LinuxMCE.
Really any of the ATOM boards with the ION graphics seem to work well as MDs but I always like to try the latest and hopefully greatest.

9
It sounds like it is looking for the firmware files.

[I believe] due to licensing issues, LinuxMCE does not include the firmware files in the /tftpboot directory.  You would have to download them from Cisco (provided you have a support subscription) and unzip them in the /tftpboot directory yourself.

10
Installation issues / Re: Failed to setup X
« on: January 09, 2011, 04:42:49 pm »
I think you need to edit or add the line AVWizardDone = 1
to /etc/pluto.conf

11
Installation issues / Re: Failed to setup X
« on: January 05, 2011, 07:52:58 pm »
Which field is it exactly that you modify in webadmin?

I tried setting the "Video Settings" field to 1024 768/75
and the "TV Standard" field to 1024x768
But that resulted in a smaller than full screen orbiter in the upper left-hand corner of the total screen area.

It was only when I manually edited the xorg.conf file to specify the resolution of 1024x768 that it worked correctly.

12
Installation issues / Re: Failed to setup X
« on: January 05, 2011, 02:55:16 pm »
I don't really have a fix, but I do have some new information.  If you edit /etc/pluto.conf to say that the AVWizard is already done.  Then it doesn't try to run the AVWizard to setup X.  If you delete the xorg.conf from /etc/X11/xorg.conf then X will startup correctly using the built in config.  The orbiter will come up after it is regenerated and everything will more or less work.

Now the bad news.  Since the AVWizard wasn't used, you are stuck with the BASIC UI.  Also the orbiter size may or may not (probably not) match the resolution that X automatically comes up with based on your monitor.  You can somewhat manipulate the orbiter size by setting "TVStandard" on the web based config for the media director.  And you can also create your own xorg.conf and manually set the resolution if you want.

In the end I had a more or less usable media director with the BASIC UI, but I could play DVDs, listen to music, etc.

13
Installation issues / Failed to setup X
« on: January 04, 2011, 04:07:01 am »
At the risk of getting "Search The Forum!" replies, I'm gonna throw this out there...

I am trying to Diskless Boot an Intel D510MO board (GMA3150) as a Media Director.  It goes through the PXE motions fine, but when it gets to the AVWizard step a white box on a blue background comes up stating "Failed to setup X"

I have searched the forums and have done everything I came across that I thought might pertain to my issues, to no avail.  I understand that nVidia is the way to go, but on this Atom board there is no slot for an add-in card, and I didn't spend the extra money for the Ion.

My biggest misconception is, since I can ALT-F2 to a terminal and type in startX and fire up KDE just fine, it doesn't seem like an X issue.

I have attached part of /var/log/Xorg.2.log... Xorg.0.log doesn't seem to state any errors.

Code: [Select]
(EE) open /dev/fb0: No such file or directory
(WW) Falling back to old probe method for fbdev
(II) resource ranges after probing:
        [0] -1  0       0xffffffff - 0xffffffff (0x1) MX[B]
        [1] -1  0       0x000f0000 - 0x000fffff (0x10000) MX[B]
        [2] -1  0       0x000c0000 - 0x000effff (0x30000) MX[B]
        [3] -1  0       0x00000000 - 0x0009ffff (0xa0000) MX[B]
        [4] -1  0       0x0000ffff - 0x0000ffff (0x1) IX[B]
        [5] -1  0       0x00000000 - 0x00000000 (0x1) IX[B]

Backtrace:
0: X(xf86SigHandler+0x79) [0x80c3019]
1: [0xb8085400]
2: X(InitOutput+0x80c) [0x80aab3c]
3: X(main+0x279) [0x8071b19]
4: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7c86685]
5: X [0x8071101]
Saw signal 11.  Server aborting.


14
Users / Multiple TV Tuners Question
« on: March 16, 2010, 01:26:48 pm »
I didn't really know what to search for to find the answer so forgive me if this has already been asked.

In my core I have a dual ATSC tuner board (HVR-2250) and an analog tuner board (PVR-250).  Presently the PVR-250 does nothing since there are analog OTA streams.  I am considering getting cable which will have some analog streams.

My question is how do you switch between tuners on LinuxMCE/MythTV?  Does it just list all of the channels in a row and automagically switch to the appropriate tuner depending on what type of channel you are watching?  What if you are watching an ATSC channel on the core and an analog channel on a MD, does that mean that your analog channel surfing abilities on the core are revoked?

Along the same line... since I have two tuners in the HVR-2250 does the machine deal with those automagically too?  In other words if the backend is already recording something on Tuner1 and I click on LiveTV will it choose Tuner2 to show me the LiveTV instead?

15
Users / Re: MD PXE Boot, used to work, now fails
« on: March 02, 2010, 03:24:46 am »
After running apt-get update, again, to get: Update 2010-02-28 22812 installed.

I deleted the media director from the web interface, ran Diskless_BuildDefaultImage.sh & Diskless_CreateTBZ.sh again and now everything is working as before.  Same e100 module, same computer with the "suspect" RAM.  The only thing that seemed to change was the recent apt-get update.

Go figure.

Pages: [1] 2