Messages

1

Users / Re: AV Setup stuck in loop

« on: October 03, 2007, 06:59:23 am »

my guess is this is a diskless booting client.  says you got your main box up and running but the first client isn't working well.  i'm having the same issue myself with my second diskless MD which does have the exact same hardware (CPU/MEM/MoBo/VIDEO) except the audio card is different.  it worked before in a previous installation i'd had.

2

Users / Re: Is there a way to watch satellitetv with Timeshift

« on: October 03, 2007, 06:56:23 am »

only unencrypted signals can be viewed with LMCE and yes, this build of mythtv does in fact have the necessities to setup dvb-s.

3

Users / diskless MDs where did i go wrong??

« on: October 03, 2007, 06:53:30 am »

ok, have a honking machine setup as the main media director.  it runs fine.  have 2 identical machines to run as diskless media directors with one exception. the sound card in one is onboard, the other is a pci turtle beach with sp/dif out.

the one (working) uses stereo out to the tv, and Svidoe as the video connector.
the one (not working) uses toslink to an amp, and DVI<->HDMI as the video connector.

previously, with lmce 0704 i DID have this particular machine up and fine as a diskless MD.  Same hardware etc.

the point we get to is where the machine boots up for the first time, acquires IP and announces itself to the router.  from then on it works fine until we get to the video/audio wizard. this completes properly HOWEVER, the final tab listed at the top, the "Step 9 : Final" tab is never accessed. i set the video connector, moves on, set audio, moves on, until the last part at the DTS test screen.  No matter my answer, it's never moving forward from there.

it will/has/can sit there for days if I let it. 

I have removed the media director from the lmce web interface as a device, and rebooted the CORE, however if i let the machine PXE boot again, it gets same IP, and a different moon## and proceeds as normal.  that is, until we get to the AV Wizard setup.

any ideas.

4

Users / Re: where does ushare.conf get populated from/by?

« on: October 03, 2007, 06:44:26 am »

around the same time this happened, when one of my MDs booted up, it started saying it was detecting all KINDS of weirdness, and the closer i paid attention to the names, they were from a conf file, the exact one i've yet to narrow down.

that is to say, when the device was picked up, it would claim to be a "scanfullsubnet" for example or a "toremove unwanted" some random names it was pulling from a file and populating.

5

Users / Re: where does ushare.conf get populated from/by?

« on: October 02, 2007, 03:51:41 am »

bump!  not one reply

6

Users / where does ushare.conf get populated from/by?

« on: September 24, 2007, 11:33:08 pm »

issue i'm having is a remote filesystem is repeatedly mounted in /mnt/upnp by djmount... however blanking /etc/ushare.conf does not seem to prevent this remote fs from being discovered and re-populated.  this does not show as a device in the linuxmce web gui so of source i can't get rid of it.

it's basically seeing the MD array i have full of movies twice but only on the MDs so even a resync won't yank this out.  For instance, if i open "Media Files Sync" from the linuxmce web gui, there's only 1 instance of these media files in there, however, theres more than that in the MD gui when i go to Videos.

the supposed little share that it's finding isn't even from a hostname, but rather from a windows workgroup, which has since ceased to exist.  every reboot, this little pissant decides to re-pop with that. 

i can't find anything in rc2.d or rc3.d to yank out or remove whatever is calling djmount... even temporarily


please guide me

7

Feature requests & roadmap / Re: File finding without being DHCP

« on: August 24, 2007, 01:54:03 am »

well, if you go into the web-interface at http://dcerouter and configure your eth interface eth0:0 to participate on your existing local network, you can browse shares.

What I did, was to simply change the folders for audio, video etc from the local directories to existing smbfs shares that are already on the network... and then synchronize them.