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

Pages: [1]
Users / CM11A Problems... Setup works, LMCE just can't talk to it.
« on: December 03, 2008, 04:30:40 pm »
Hey, I'm having a bit of trouble with my CM11A... I have the setup working, can control lights via my remote, and I have tested using heyu from the media director (where the CM11A is connected) and it works fine talking to /dev/ttyS0... (I can turn on and off lights using heyu)

When I add the CM11A using the instructions from the CM11 page in the wiki, then add a generic lightswitch on/off light... Set it to A1 address, controlled by CM11A, and set it's room...

(Currently I have lights on A1 - A10)

Anyway, when I do all that, then reload the router, I see the following in my log (/var/log/pluto/65_CM11A.log)
Code: [Select]
========== NEW LOG SECTION ==========
1       12/03/08 10:11:18       65 (spawning-device)    Starting... 1
1       12/03/08 10:11:18       65 (spawning-device)    Found /usr/pluto/bin/CM11A
05      12/03/08 10:11:23.825           Creating child 71 <0xb79846c0>
05      12/03/08 10:11:23.825           Note: Device manager has attached a device of type 37 that this has no custom event handler for.  It will not fire events. <0xb79846c0>
05      12/03/08 10:11:23.826           Note: Device manager has attached a device of type 37 that this has no custom handler for.  This is normal for IR. <0xb79846c0>

Ok so I'm confused by the no custom handler messages, but so far so good... (device 71 is the light I added)

So now I try sending an on or off command to the light... When I do... Nothing. Nothing shows in the CM11 log, and the light doesn't turn on or off...

So I wait about a minute or two... Then suddenly the following pops up in the log file (/var/log/pluto/65_CM11A.log)
Code: [Select]
01      12/03/08 10:12:47.440           No response from CM11A device. <0xb6941b90>
01      12/03/08 10:12:47.540           Failed sending address. <0xb6941b90>
01      12/03/08 10:13:02.565           No response from CM11A device. <0xb6941b90>
01      12/03/08 10:13:33.253           No response from CM11A device. <0xb6941b90>
01      12/03/08 10:13:48.369           No response from CM11A device. <0xb6941b90>
01      12/03/08 10:17:05.452           No response from CM11A device. <0xb6941b90>
01      12/03/08 10:17:50.852           Failed sending address. <0xb6941b90>

So what's going on here? The CM11A is definately set to talk to /dev/ttyS0 which is exactly how I configured heyu running from the media director, and heyu saw the CM11 right away, and fired off lighting commands without a hitch.

any suggestions would be helpful.


Installation issues / Nightmare Install Problems on new core
« on: November 11, 2008, 10:53:18 pm »
Ok, here's the skinny:

Tyan Thunder S2882
Dual Operon 200 series 2.0GHZ (not sure of precise model)
4GB Of ram
4X 3Ware 8506-4LP SATA RAID cards
10x Seagate 300GB HDDs (SATA)
4X Seagate 500GB HDDs (SATA)
1X Western Digital 120GB HDD (SATA) (connected to onboard SATA controller).
Dual Onboard Gigabit NICs
Single Onboard 10/100 NIC.

I installed this a couple days ago. First time trying it booted almost immediately to a prompt for BusyBox, Figured it was a cd read error or something wierd, so just rebooted. The install started, and finished just fine, LinuxMCE started up, walked through the av wizard, and came to a running core...

I fucked around with settings a bunch, broke some stuff, and decided to re-install (this was a new core, old one was still running so I had the option to experiment).

On the next install it took 5 reboots to get the install to go (Same thing as before) (note nothing is changing between these reboots, just hit reset button and wait for it to boot)

Did another reinstall... This time it installed with no reboots, first try.

Then tried another reinstall, this time took 20-30 reboots, (pissed me off) but installed fine... This time I left it up, and configured it somewhat, it was stable, and I rebooted the system a few times for various reasons, it rebooted fine no worries on the installed system.

(at this point I should mention that up until now, the first 4 bays running on the first 3ware card were populated with the 500GB drives, no other drives were populated yet, and the first 3ware card was configured for a 4 drive RAID5 hardware array with the 4 500 gb drives)

So I added that raid array as a drive in LMCE, and started migrating my media across from the old core to the new one (across the network, network ports working fine, tested both the 100mb and the gigabit ports)

Now with all the data migrated, I wanted to move some of the drives from the old system into the new system, and figured a fresh install wouldn't hurt (I know I know I probably didn't need it, but I did it anyway).

So I moved my drives across:
Installed a second 120GB drive on the onboard controller
Populated the remaining bays in the system with the 300gb drives
Added some ram from the other system to this one bringing it up to 6GB of ram.
I didn't configure the 300gb drives on hardware raid, I plan on letting lmce use software raid for those.
I did configure the 2x 120gb with raid using the motherboards bios, RAID1 mirror, so I could use that as my OS partition.

Reboot off the install DVD. this time it dies almost right away with:
Code: [Select]
udevd-event[2452]: run_program: '/sbin/modprobe' abnormal exit

BusyBox v1.1.3 (Debian 1:1.1.3-5ubuntu7) Built-in shell (ash)
Enter 'help' for a list of built-in commands.


So I assume it's the same issue as before, so I reboot about 30 times... then I got pissed off...

So then I notice that the modprobe abnormal exit is different this time than last time... So I decide lets put the hardware back exactly like before...

So I remove all the drives I add, remove the extra ram, and reset the raid settings on the onboard to be standard sata, with only the single 120 gb drive installed...

Still getting same error... retried another 10 times...

Then I tried reburning the disk in case disk was bad

Tried another 10 times....

Figured, must be a hardware failure or something... So I tried a centos 5 disk I had laying around...

(all drives and network working fine)

Installs fine, boots to a desktop...

Tried a Windows Server 2003 install... It works fine boots to a desktop (all drives and network working fine)

Then I tried searching on the error, found some bugs relating to seagate drives... Said to use all_generic_ide

So I tried that, that got it past the first error, but now it locks hard on "Configuring Network Interfaces"


So after some more searching I find that there are 2 kernel bugs known specifically with the 0710 kubuntu install livecd, that cause this error either on the seagate hdds or on certain onboard network interfaces.

So I go into the bios and disable the onboard nics entirely...

Reboot, now the installer starts... So I run through the install. but after the normal grub install part, when it spits the disk out and reboots, it does nothing (the screen blanks, leaving a blinking cursor in the top left corner, it responds to keystrokes, but does nothing else... hangs there forever, I left it for half an hour to be sure).

At this point I hit the reset button... It booted off the hard drive, but hung with a kernel panic??? what the hell???

So at this point I re-download the iso... MD5 Check it, it's fine... Re-burn it at 1X... Retry the boot... Same friggin deal...

So I retry the install again... using the all_generic_ide and only the gigabit nics disabled... No go... (still failing at configuring network)
Tried again with all_generic_ide and the 100mb nics disabled... No go... (still failing at configuring network)
Tried again with all nics disabled, but without the generic ide... Dies with busybox prompt...

So I retried again with all nics disabled and all_generic_ide... Again, install works fine, but hangs before reboot... Left it for half an hour, hit reset button...

This time it boots, loads the kernel, then my monitor gives me an error saying that the video signal it's recieving is out of it's refresh rate range... (no this is not the av wizard, this is IMMEDIATELY like within half a second of the kernel loading after the bootloader).

Left it for a bit, then hit reset again...

This time I stopped grub, and took off the quiet and splash options... This time it hung at...
udevd-event[2053]: run_program: '/sbin/modprobe' abnormal exit

So I reboot again, this time editing the grub line to pull out the quite/splash and to add all_generic_ide

This time it boots through the proper startup for dcerouter, which gets angry as all hell because I have no network interfaces, but it does get me to avwizard...
Then X starts, and the launch manager comes up.
Got the girl on the screen, did the config steps (whipped through with minimal config to see what's next)
It regenerated the orbiter
While it was doing that I dropped out to a terminal to edit my boot config to force it to set the all_generic_ide option, but the pass for linuxmce user I set during install wasn't working (that may have been a typo during install though)
It came up with onscreen orbiter fine, so I rebooted it via the menu.
This time I hit the bios and re-enabled the onboard NICs
then interrupted grub and added all_generic_ide and still disable the quiet and splash so I can see what's going on...
This time around, it passes configuring network interfaces, but not by much (didn't see the exact line unfortunately, after 4-5 more lines maybe? it kernel panics...
specifically: Kernel panic - not syncing: Aiee, killing interrupt handler

Anyway, so at this point I'm ready for a full blown nervous breakdown... Ready to smash something seriously... was up all night last night, was also si9ck as a dog... Feel like shit, and frustrated as hell right now...
AND sine it worked fine before, and I copied my data over, I have canibalized my old core, so now I am completely without a core! which is REALLY pissing me off lol...

Just for shits and giggles... I retried with the CentOS5.1 dvd again... To confirm it still works... (with the network cards enabled, and no special boot options) (to see if it works without any "workarounds")
The installer booted fine, detected nics fine, detected hard drives fine, with no errors...
The install completed fine with no errors.
And it rebooted and started udev fine...
Detected the nics fine...
fired up networking fine, and booted to X perfectly fine...
From within X I tested networking, and it's working perfectly...
Kernel was 2.6.18-53

So I ask a few questions:

#2 - Why would something that appears to be hardware incompatibility, work perfectly "sometimes", and then suddenly stop working at all unless it's hardware failure.
#3 - If it's not hardware failure, why does it work perfectly in all other OSs lol (including other linux distros)

ok, I'm done ranting now, just if anyone has any other suggestions for me to try PLEASE they would be much appreciated...


Users / New Media Tagging System
« on: November 08, 2008, 02:17:55 am »
Hey everyone, I figured I would make my first stab at contributing to the LMCE codebase... So I developed a new addition to the media tagging functionality within the web admin.

I know everyone finds it painful to tag each item individually, and there is no easy solution for TV Episodes... So I wrote a new system to handle that.

Basically it integrates to the media file sync screen, when your browsing a folder, you will see a button labeled "Apply These Tags Recursively". That lets you access the new system.

How this is meant to be used:
- First Put your media inside a folder structure of some kind. In my case, for TV Episodes for example I store it in TV/Showname/SeasonX/Filename.avi
- Also it helps alot if your files have a standard file naming convention, most downloaded packs do, but be careful if it's a mixed bag.
- Now you browse to (in the case of my example) the "Showname" directory.
- Now apply any tags that apply to the entire show (or use the search amazon function)
- Now click the Apply Recursively button. This allows you to copy these tags onto every file/folder contained within this one (fullly recursive)
- Once in the recursive screen, choose if you want it to apply to files, folders, or both.
- Also if you want to tag TV episodes automatically by their filename, check out the TV Episode Tagging Mode.
- Now click the "Confirm" button and see a sample of what it will affect. If there are any problems it will tell you here.
- Click the final approve button and it will go nuts tagging your files.
- Just because I target TV Episodes doesn't mean it can't be used for other types of media. The recursive tagger will recursively tag anything
- (it's just the file parsing tagger that's specific to tv episodes)
- This will recursively duplicate all attributes, long attributes, and images.

Some things to consider:
- IT WILL OVERWRITE ANY TAGS YOU HAVE! so please be careful where you use it.
- It is not 100% tested yet, there may be bugs.
- The tv series renamer is designed only for tv series (but since these are all that is really lacking in LMCE I thought that's fine)

Notes about the TV Episode Tagger:
- It is flexible. It can handle any case where files are uniformly named
- Example: S01E02 - Some Title [[HDTV-LOL]] or something like that.
- As long as the following conditions are met:
- Season number, and episode number must be fixed length (If you use 2 digits, it must be 2 digit everywhere, so 1 will be 01)
- Season and episode number must come before the title in the filename (but their order is not important)
- If those criteria are met, it should be able to glean the season number, episode number, and title from the filename.
- You can use the strip text field to rip off group tags like the [[HDTV-LOL]] in the example.
- It supports adding more than one strip text, so you can strip wierd file formats, or rip garbage out.
- Get creative with customizing the settings, and let me know how it works. I'm open to suggestions.

The file can be downloaded at:

The file is relative to the /var/www directory on the core. Extract it SOMEWHERE ELSE and make BACKUPS of your originals, then overwrite them with these.
Or you can search for PAUL MUMBY in the code, for comments which mark modifications made by me. And patch it in yourself.
I'm talking to the devs about getting this merged into the LMCE distro so you don't need to manually install it.

That's about it. I hope everyone enjoys! (if someone gets a chance, post some screenshots or more details install instructions, I haven't got time right now lol)

Shameless plug for my home business goes here: (if your interested let me know you came from LMCE for a 10% discount!)

Let me know if you have any problems, bugs, suggestions, or questions.

Pages: [1]