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 - pigdog

Pages: 1 ... 5 6 [7]
Users / wiimote on 810 alpha2
« on: April 11, 2009, 12:24:17 am »
Adding a wiimote in 8.10 is alot easier than the LMCE 7.10 variant.

The following link explains...

You can have three different ways you can use your wiimote.

...use wiimote as a mouse using acceleration
...use the wiimote as a mouse using an Infra-Red light source
...use your wiimote and IR LED pen as a whiteboard

The instructions explain swapping default left and right mouse buttons, using your Wii remote for watching DVDs, Elisa Media Center, Music Players, etc and remapping the buttons / axis on your wiimote / classic controller / nunchuck.

I tested "Using your wiimote as a mouse using an Infra-Red light source".

It worked just fine, no fuss, no muss, no files to create, minor editing.

However, you still get asked to add it as a phone.

Users / 810 alpha2 not tearing but threading?
« on: April 10, 2009, 07:50:54 pm »

I've watched movies on one MD using UI2-masked and everything looked great over S-video to CRT. (And no freezing on the Playroom unit - yay!)

On a HDMI Aquos LCD I didn't get tearing but what look like little threads pulled out horizontally.  Almost scratchy?  Hard to explain.  UI2-alpha.

This happened for about three to five minutes and cleared up.  Timing or X-fer issue on network?

This is on Nvidia 180.11 driver.

Just thought I'd mention it.


Users / Crunchpad as orbiter?
« on: April 10, 2009, 05:29:40 pm »

I was just reading an article about the Crunchpad.

I'm looking for something to use as an orbiter. 

I like the WebPad DT366 for it's physical size and I would also like something that could be wall mountable.

I would go nuts trying to see images on something like an iPod Touch/IPhone or Nokia.

There seems to be alot of stuff about to be released for use as MD's etc.

I guess I just have to wait to see what is real.  Patience, patience, patience.

Via Wired News.

"The machine is as thin as possible, runs low end hardware and has a single button for powering it on and off, headphone jacks, a built in camera for video, low end speakers, and a microphone," wrote Arrington. The Crunchpad would also have Wi-Fi, 512 MB of memory, 4 GB solid state hard drive and no keyboard.

Developers / 810 alpha2 remote MD power down.
« on: April 09, 2009, 04:17:24 pm »

Don't know if this ever worked I had never tried it before.

Since there is no KDE desktop I thought I'd shutdown my MD's via the Core.

Menu> Advanced> Power>   Select the orbiter that you want to control.  Select room.  Then Power of m/d.

Everyone powers down.

Thanks for the other info jondecker76.


Developers / 810 alpha2 no KDE desktop on MD.
« on: April 09, 2009, 03:15:42 pm »

When going thru main menu to KDE Desktop (UI1, UI2-masked, UI2-alpha) the screen goes blank with cursor.

That's all.  Cursor moves but no joy.

I have seen the flickr screen saver kick in but there is no menu bar.


Developers / 810 alpha2 progress_window stall
« on: April 09, 2009, 02:54:01 pm »

I've seen this happen alot.

When booting up after external media identifier runs on the progress_window the screen clears to only showing green bars (no text).

I've let the system sit for 20 minutes with no change.

<CTRL/ALT> F1 on MD shows

Not starting device 41 External Media Identifier - binary "External_Media_Identifier" is not found.

I've had this happen on Core and both MD's.

It is not consistent.

<CTRL/ALT> F7 provides main menu screen.

Developers / 810 kernel and nvidia combos.
« on: April 08, 2009, 03:22:22 pm »
Hi all,

I've tried various kernel and nvidia combinations.

2.6.27-11 and nvidia-177
2.6.27-13 and nvidia-177
2.6.27-14 and nvidia-180

I don't know if I got better at it or was just lucky (finally), but the 14-kernel and 180-nvidia gave me the least amount of trouble.

I've had a few really good head scratchers.

Some I couldn't figure out so I just reloaded which fixed most problems.

Probably user error during installation.

One thing I did for the 14-kernel and 180-nvidia combo was have it all updated before installing alpha 2.7

Don't know if anyone else has seen this but during all setups/ all generics there was no audio during AVWizard.  (Core and MD's)

Once I ran AVWizard, set a volume level and restarted I had audio.

I've got more testing to do, some further setup tweaks.

I will post with hardware setups for Core/Hybrid plus both MD's.

I did see something flash by the screen on the 14-generic saying it did not support NFS.


Developers / 810 Alpha2
« on: April 04, 2009, 10:35:07 pm »
Hi all,

I'm trying this out on my setup just a Core, 2 MD's and a NAS.

I'm on my second attempt.  The first try I couldn't get past a network boot issue. 

This cleared up after downloading and re-installing the alpha2 load again.

My second attempt everything seems to be going along to what I have read on various wikis.

Presently I have a Sempron based processor and a Athlon64 based as MD's.

I've got an xorg problem to sort out on the Sempron/ATI card (it can be swapped for a 6XXX series NVIDIA).   (xorg or fglrx/kernel)

Since my Athlon is 64 bit I need to get into webadmin to change it to i386.

I've looked all over but since the launch manger is no more how do I run webadmin from a command line?

One thing on this load is I've lost my consoles/workspaces.  I've only F1 and F8 to look at messages.

F7 is MCE.  I'm using terminal on Kubuntu.


Users / MD Hardware Upgrade question.
« on: March 28, 2009, 05:50:21 pm »
Hi all.

I've got an old P4 1Gig which is PXE booting via ROM-O-Matic floppy.

Compared to my Home Theatre unit this system freezes a lot during DVD play back.

I thought I'd swap it out with another system that has a Sempron 2800+ / EP-8KDA3+ mobo 1Gig RAM.

I was wondering if I could cheat and go into webadmin/media directors and edit the ethernet MAC address?

I'm using the original video card because I need the S-video out.

I figure leaving it as architecture/Model i386 would be O.K.

Any suggestions?


Users / Floorplan Issues
« on: March 21, 2009, 05:57:35 pm »
Hi all.

I've got 2 MD's (+ core).  One MD is in room "Home Theatre (HT)" and the other "Playroom (PR)".

HT is running UI2+alpha while PR is UI2.

I created two separate floorplans (HT & PR) and added them on core via webadmin to floorplans/media.

On both MD's when I tried to switch between floorplans (for simultaneous play) I can only view one floorplan.

(I'm not sure if was the first or second one entered.)

One floorplan is layered on top of the other.

The second layered (covered) floorplan will flash for a second when selected via media floorplan screen.

So I figured image layering was a problem using UI2.

I then created a single floorplan with two entertainment rooms.

I deleted the other two floorplans via webadmin. 

I added this single floorplan via webadmin to floorplans/media.

I placed both Pluto MD's on the floorplan.

Core & MD's have been reloaded.

The core webadmin page shows the single floorplan.

Both MD's memu media/floorplan still show the "deleted" layered floorplans.

The /home/pluto/floorplans/inst76976 directory on the core has only 1.png file listed.

When opened and viewed it is the newer floorplan.

When I reboot my MD's I'll receive the message "There are some devices on this media director that did not correctly start blah, blah" etc.

I'm told that "You have recently changed scenarios, floorplans or other settings.  I need to regenerate the graphical screens etc."

If I agree to reload the orbiter I get into a loop.

I just keep on getting device on media director did not start correctly and need to regenerate messages.

I went back via webadmin and deleted the one existing .png floorplan and reloaded the core and MD's.

I'm still in the loop.

On the Core I double checked the /home/pluto/floorplans/inst76976 directory.  No floorplan.

On the MD I ran the video/audio setup and changed my UI2 alpha setting to UI1 and restarted.

Bad move. I now receive the following...

"The resolution has changed.  I'll regenerate the user interface."

Followed by ...

"The UI is being regenerated.  This will take between 15-30 minutes.  If you get this same message again after the regeneration is finished, then that means the gernerator on the Core"

These two messages keep looping.

I shut down the MD that I changed, went to the core, deleted the latest xorg.conf and copied in the backup.

I restarted the MD.

Same loop.

I restarted the Core.  When it had rebooted I restarted the modified MD (original xorg.conf).

I'm in the same regen loop.  Both messages, the launch manager screen, both messages, launch manager, etc.

I let this run for a hour.

All floorplans were created around 1200 x 1200.  Nothing larger.

I see basically two issues with floorplans - one being the layering effect and the second being the MD not reflecting the updated drawing change.

Getting stuck in this regen loop is something else.

Before I delete my MD's and re-add them any suggestions?

I have tried reloading the router, regen all orbiters on the Core and rebooting all systems.

Installation issues / Wiimote on diskless MD
« on: May 31, 2008, 07:26:24 pm »
Anyone get this working?

I kinda had it going the other day but when I reloaded the MD I got feedback vibration from the wiimote but no cursor movement.

I reloaded both Core and MD then completely a no go.

I rebuilt from scratch but all I'm getting now when I run wminputd from etc/init.d is...

Socket connect error (control channel)
Unable to connect

hcitool scan works fine - shows my wiimote MAC address.

I'm using a MSI 3G bluetooth dongle.

Any suggestions?


Sharp Aquos LC-46D64U installation notes for a diskless MD.

This is a fresh install of a diskless MD connected to a Sharp Aquos LC-46D64U.

No remotes or other optional equipment is involved.  This is just getting the TV going.

The LC-46D64U has Antenna/Cable in, USB terminal-service, RS232C terminal, 7 inputs (2 component, 2 composite and 3 HDMI) plus 1080p native resolution.

The diskless MD is connected between the COM1 port and the Sharp RS232 port.

The diskless MD is using a DVI/HDMI adapter with a HDMI cable connected to input 6 of the TV.

I am presently using analog sound via mobo AC 97 to the analog port on input 6.  This is the only input of the HDMI ports that has the mixed HDMI/Analog input.

I hope to find a compliant SPDIF cable to hook from the mobo SPDIF to my MSI NX8400GS card. A cable was not included in the kit.

Note: How to setup BIOS PXE network booting is beyound the scope of this document.

The diskless MD is set to network boot.

Start the diskless MD.

On my system on the first attempt I am announced to the router but the "Diskless setup failed" message is generated. 

My Core system runs i386 software.  My diskless MD is architecture amd64. 

On the core system open admin website and select Devices/Media Director. 

Under the Device column you'll see the architecture field set to amd64. 

Edit this to i386 and on the bottom of the page click the update button.

Restart the diskless MD.

Wait for to complete.  The cursor blinks for about 5 minutes before setup continues and the MD restarts. 

When the files are downloaded and the configuration is complete the system will beep. 

In my case since I am using the DVI/HDMI port my screen goes blank.  If I was using the default VGA port the setup AVWizard would appear. 

Inorder to use the DVI/HDMI port after the system beeps I press the 1 key on the keyboard.  You'll hear a beep and the AVWizard appears.

The AVWizard will be running in 640x480 mode not 1080p native resolution.

Setup the AVWizard (my case DVI,1080p,60hz,etc).

When the AVWizard is completed the system restarts.

The MD Launch Manager will run and the Setup Wizard will start, albeit in 640x480.

Go thru the Setup Wizard.  When it comes to setting up the LCxxD64U/LCxxD7u only 5 inputs are presented.  There are a total of 7 and I'm using #6. 

At this point I select input 5 and complete the Setup Wizard. 

I then reload the router from the Core MCE Launch Manager and when completed I reload the router on the MD (it usually asks to be loaded about 3 times) until the MD screen comes up.

On the Core MCE Launch Manager open the admin website and under the Wizard/Devices select General Serial Devices. 

Under Action select the Advanced button.  Select View for the Acquos LCxxD64U/LCxxD7u #1856. 

In the Device Template section select Edit Audio/Video Properties.  This pulls up the Edit IR codes. 

There is a line named Inputs Discrete: Input1, etc.  Select [change/explain]. 

Scroll down thru the field until you see Input6 and Input7.  Check their boxes.  At the bottom of the page select Save. 

Now scroll down to the Inputs section on the Edit IR codes page and you'll see at the top of the section a line saying "input commands not implemented Input6, Input7 (Click to add)".

At this point I highlight the <$"'|AVD5  \r"$> in the field of Input 5 and copy [CTRL]C the code.

The click to add Input 6.  In the popup box paste the code [CTRL]V edit 5 to 6 and the select Add Code. 

Allow the screen to refresh and do the same for input 7.  Click the Update button. 

Close your windows and go back to the LMCE Launch Manager and Reload router. 

When the router is finished loading go back to the MD.  Run the Setup Wizard. 

When asked to setup the Media Director select "No that is not the correct TV". 

Go thru selecting SHARP as the manufacture, the LCxxD64U/LCxxD7u as the model, Com1 as the interface and Input6.  Finish the Setup Wizard.

Now we need to get the TV to run in native resolution.

On the Core at the MCE Launch Manager screen press [CTRL][ALT]+F1.  Hit the enter button to get your dcerouter login prompt.  Log into the system.

We need to edit the xorg.conf file for the MD. Enter (no quotes) "cd /usr/pluto/diskless/XX/etc/X11"  (where XX is the number of your MD-for me it's 22).

Enter "ls" to see your directory listing.

Enter "sudo nano xorg.conf".

Supply your password.

In the xorg.conf file scroll down to Section "Device" and change Option "UseEDID" "false" to "true".  Change Section "Screen" Option "UseEDID" to "true" as well.

To exit [CTL]X.  Y to save.  Enter to write file name to xorg.conf.

Press [CTRL][ALT]+F7 to return to the MCE Launch Manger.  Select Reload router.

When finished restart the diskless MD.

We are now 1080p native resolution.

Hope this helps someone. :)

Installation issues / Installing LMCE on stand-alone Core.
« on: May 26, 2008, 04:12:24 pm »
Installing LMCE on stand-alone Core.

I use to spend hours and hours trying to get a system up and running - especially when I had errors.  This is the fastest way I've been able to get a system installed to-date.  Hope it helps someone. :)

The following is a general overview of what I do to get Kubuntu and LMCE loaded on a stand-alone Core system.

This procedure takes between 2 1/2 to 3 hrs to complete.

I am using the CD variant of LMCE. Due to network throttling it takes me forever to try and download a DVD version.

This procedure assumes you have the following disks on hand. 

   1) Kubuntu.iso
   2) Kubuntu image
   3) MCE-CD1.iso
   4) MCE-CD2.iso
   5) MCE-CD1 image

How to download the .iso disks, create an image, change BIOS settings, create folders, etc., is beyond the scope of this overview.

Setup your BIOS to boot from CD/DVD drive.

Insert your Kubuntu image disk into the drive and restart.

Install Kubuntu to meet your configuration requirements.

When completed restart Kubuntu.

At reboot setup your BIOS to boot from HDD, etc.

Login to Kubuntu and create a folder in your Desktop directory (i.e. LMCE-iso-files).

Copy the Kubuntu, MCE-CD1 and MCE-CD2 .iso files to this directory.

Insert the MCE-CD1 image disk into your CD/DVD drive and run the MCE installer program.

When completed remove the MCE-CD1 disk.

Click on the Install Linux MCE icon.

Configure MCE as per your requirements.

When asked to insert the LinuxMCE 1, 2 and Kubuntu disc select "I have an iso image on my hard drive".

Point the browser to the Desktop directory created earlier.

By using the .iso files on the hard drive you avoid the very painful cache-ing of each disk.

The program immediately begins to download packages.

A failure only requires a restart of the Install Linux MCE program.

Choosing a good mirror is important because some have broken links.

I usually always got the "Failed to install MYSQL error" messages during bad mirror downloads.

Without having to re-cache the CD1, CD2 and Kubuntu disks you just rerun the install program and choose another mirror until you find one that works.

When completed reboot your system.

Complete the AVWizard and you're away.

Pages: 1 ... 5 6 [7]