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

Pages: 1 ... 27 28 [29] 30 31
Users / Re: Post your MD Boottimes
« on: January 28, 2012, 07:40:41 pm »
Juice in "Suspend-to-RAM" is perhaps a bit over the top.. It should not use much... But please be warned - this is not something that is known to "just work"...

Really looking forward to this one  8)
(I would guess around 150 secs but could be surprised... Would think the limiting factor could be the rotation speed of your core HDD, which would never be a problem for recording/streaming large media files)


Via the 10/100 hub- MD boot timed at 11min 21s! - 681seconds. Crawling.
Via the Cat5e cross-over cable direct to core - 1min 55s - 115seconds. Smoking  8)

Well, that certainly answers my primary question: Is the network speed a limiting factor. The gig switch will be ordered first thing monday.

Users / Re: turn on bluetooth - netboot of media director hangs
« on: January 27, 2012, 07:37:08 am »
Gloves are still off- I just rebuilt the image for the MD from the admin website. Took ages but that seemed to sort it out... kind of... at least it boots now.

Bluetooth (integrated, onboard) is still a query though? Yes, I can get a usb dongle but it seems a waste when the notebook already has a bluetooth device onboard... I've searched the forum and wiki and not much discussion around this. Will do a bit more experimenting and see if I can come right with it.

Users / Re: Post your MD Boottimes
« on: January 27, 2012, 07:26:16 am »
You can just put them to sleep. Go into Media Director in the admin page, set the PowerOff mode to S instead of H.  My P4 MD wakes up in 10 seconds.

Good to know, Aviator. Once my system is stable  ;) I will try that to speed things up and see if I can get an idea of the comparative power consumption... presumably, even asleep, they draw some juice.

I'm going to borrow a cross-over cable from work today and time my MD boottimes via the network (with the hound-dog-slow hub) and direct nic to nic connection to see just how much of an impact the network speed is having.... should be interesting and if it comes out dramatic will light a fire under me to order the gig switch.

Users / Re: turn on bluetooth - netboot of media director hangs
« on: January 26, 2012, 08:45:08 am »
Aha more information from the wiki regarding the PXE boot -

So if I put on my elbow-length latex gloves and dive into the guts of the core I should find whether the appropriate file (/tftpboot/pxelinux.cfg/01-[mac address]) exists and, if so, what is in it! Maybe it's just instructing the machine to reboot to local. That would be embarassing. ::)

Users / Re: turn on bluetooth - netboot of media director hangs
« on: January 26, 2012, 08:36:34 am »
First step - I disabled the bluetooth dongle in the admin webpage for this MD.

Now when I boot the MD, she doesn't boot at all into MCE - the PXE starts up but then:

Code: [Select]
Trying to load: pxelinux.cfg/b3r25ef4-8115-e011-1e88-6d990e4
Trying to load: pxelinux.cfg/01-00-1a-4b-72-cb-33
Booting from local disk...
PXE-M0F: Exiting HP PXE ROM.

Which I presume means that the core recognises the MAC (which is why it doesn't hand over the standard new MD image) and the above files/images are referenced to this MD but for some reason cannot be loaded so the PXE systems bails back to the harddrive and win xp in this case.

But why....

  • I thought of trying to start over with the MD but I read on that deleting an MD from admin website is a baaad idea. Is that true? Is there another way to start from scratch?
  • Or, I thought of trying to check out the logs for the md (/usr/pluto/diskless/ (md number) /var/log/pluto)... maybe there's a clue there? Will try to do that this afternoon

Users / turn on bluetooth - netboot of media director hangs
« on: January 25, 2012, 09:20:37 am »
Don't know if the two are related but my MD hangs when I enabled blue-tooth from the admin website of that device. It now boots up as normal and the UI (1) flashes on the screen before the screen goes blank with a non-movable mouse prompt.

There may be another problem but I thought in case it is related and anyone's had similar I'd post here.

In the bluetooth setup wiki it refers to bluetooth dongles but presumably the onboard bluetooth of a notebook can be used? Or not  :-\


    Chassis: HP6710b notebook
    PSU: integrated
    Mobo: ? Chipset: Mobile™ Intel® 965GM Express
    CPU: Intel Core™2 Duo Processor T7500 @ 2.2Ghz
    RAM: 2Gb
    Cooling: ?
    HDD: WD2500BEVT - SATA 232Gb
    WLAN: 802.11b/g
    NIC1: Broadcom Netlink Gigabit Ethernet
    Bluetooth: Yes

Users / Re: Post your MD Boottimes
« on: January 25, 2012, 09:17:01 am »
I'm surprised this thread has not seen much activity- have searched but perhaps missed something.

I'm still in the early stages of setup and I repeat rule #1 every morning ;-)

My only MD at the moment is my work notebook - an HP6710b.
CPU: Intel Core™2 Duo Processor T7500 @ 2.2Ghz
RAM: 2Gb

Before I broke it (turning on bluetooth from admin website?), I timed it at

netbooting in 500s - 8min20s. Very slow.

I don't know if the speed is to do with the fact that it may still have been setting up/installing a few things or if it is just the slow network - 10/100 hub as the bottleneck. When It's stabilised, I'll try plugging it directly into the core NIC2 with a cross-over cable to test the difference before I splash out on my Gig switch.

I would think netboot times would be of interest- do most people leave most of their MDs on all the time or do they start them as required? I guess if it's around 2min it's ok - but at 8+ min that baby had better be left running!

Good to know, thanks, that would explain it. I've since wimped out to 8.10 but the days of 10.04 are coming again.

I saw your other thread on this... I think your drive is just too big. There is a limitation which prevents 810 from working on block devs that large. I recommend using a small drive as your core anyway, and adding a NAS for storage. Everything runs faster that way.
Too big indeed! Certainly the first time I've been accused of *that* and right on the money.

Have just swapped my workstation (250Gb) and core (2Tb) drives and busy installing 8.10 on the 250Gb drive. Kubuntu saw it no problem so I guess that was the issue. Thanks very much! Will see how the rest of the install goes.

Will possibly look into one of those NAS thingies if required for the media.

Actually, /usr/pluto/coredump is a symbolic link to

/home/coredump/1 (a folder which contains)

-rw------- 1 root root 28884992 2012-01-21 06:23 core_Picture_Viewer_1327127003_6
-rw------- 1 root root 28749824 2012-01-21 06:32 core_Picture_Viewer_1327127535_11
-rw------- 1 root root 49733632 2012-01-21 14:19 core_Picture_Viewer_1327155577_6

Does that mean anything to anyone?

Hi all. The euphoria of Friday has sunk a little when I brought my new core home and tried to boot. The machine comes up and rushes through quite a few boot messages (starting this, starting that, quite a few **failed**) too fast to read really and then the screen goes blank.... and stays that way!

I try the AVWizard keys to switch signal and resolution but no response (not surprising because AVWizard has already run and completed), then I try to ctrl-alt-Fx to try to find a terminal session to log into and no dice there!

I try to ping the machine from another on the network but no response. Eventually forced to power it off.

So far:
1. Installed Kubuntu 1004, no sweat
2. run the install script as recommended in the wiki- success
3. reboot to AVWizard - slight issues as documented in other thread - just had to press 6 to see AVWizard
4. ran through all steps of AVWizard successfully and system appeared to be functioning well although, this was all done at work so no media directors or anything else set up, just floor plan and basic setup of core machine.
5. shutdown machine in possibly non-conventional fashion - ran
Code: [Select]
sudo shutdown -h now from kde terminal because I needed to leave in a hurry and don't yet know how to shutdown lmce cleanly.
6. started machine at home, eth0 plugged into adsl router and experienced above problem.

Attempts to troubleshoot-

I boot with the live DVD and mount the hard drive to check out the logs. I'm not really sure where the best place to look is, but in the "messages" log (/var/log/messages I think) it seems that each attempted boot's last message is
ip6_tables: (C) 2000-2006 Netfilter Core Team

Thereafter, the next message is from the next boot after I've powered it off.

To add to that, I see that in /usr/pluto there is a core dump file that corresponds with the time of the last message! So it looks as if the process running at that point crashes and I guess it is either the process associated with
ip6_tables: (C) 2000-2006 Netfilter Core Team
or whatever follows that?

Any ideas on how to troubleshoot this?

If I can't, I will try the whole thing again, I guess, but that install script took ages to download all the stuff so I don't look forward to that.

Thanks in advance for any pointers  :)

Thanks for the suggestions l3mce.

That sounds like a hardware problem... and i wouldn't expect a different result from 1004... meaning the drive is bad, the SATA cable is bad, the power cable is bad, the motherboard socket is bad...

Don't think so because Fedora 16 and Kubuntu 10.04  seemed to go on very smoothly... just Kubuntu 8.10 that had issues. But I won't rule it out yet.

I would grab a hirens boot disk and check the drive for errors. You can boot live to the 810 disk and open a terminal and type
Code: [Select]
cat /proc/partitionsand paste the result here, that would be helpful too.
will do:
Code: [Select]
major minor #blocks       name
7       0          663212 loop0
8       0      1953514584 sda
8       1            1024 sda1
8       2      1944694784 sda2
8       3         8817664 sda3

I saw your other thread on this... I think your drive is just too big. There is a limitation which prevents 810 from working on block devs that large. I recommend using a small drive as your core anyway, and adding a NAS for storage. Everything runs faster that way.
Hmmm, that's certainly a possibility. Will definitely consider swapping out the big drive with my workstation if I'm still struggling with 10.04 as is currently the case- soon to post latest hassles  :P

Users / Re: Paradox SP6000 alarm system
« on: January 20, 2012, 11:03:00 am »
Thom, I'll try to answer both questions with a wee bit of research and some experimentation.

1) From what I understand so far, if I connect the IP100 module, it will have an ethernet port
2) This part (documented protocal) is often the challenge, I believe but I'll get in touch with the manufacturers and distributors and see what I come up with

I am more than willing to write a device template and code for it if it is within my capabilities and someone can point me in the right direction!

The systems (Paradox) are fairly popular in this part of the world so if I can help with compatability to LMCE, I'm sure that will be a good thing. Will get working on more detailed answers to the questions.

In case anyone else hits this point... fairly easily solved in the end-

Installed as per instructions on
On reboot, AVWIZARD (I assume) comes up but is just a noisy screen of messy pixels with a few pixels that move as you move the mouse.

Simple solution, in my case- press "6" to set the resolution and hey-presto, a visible AVWizard!

1004 install went smoothly! Thanks very much guys.

Users / Paradox SP6000 alarm system
« on: January 20, 2012, 10:18:02 am »
Hi Everyone

At about the same time (ie now), we are about to install our first LinuxMCE (yay!!!) in our home and also our first alarm system. I'm doing the MCE and I've eventually decided I need to leave the alarm up to the contractor.

However, before I sign on the dotted line.... does anyone have any thoughts, experience or comments regarding the Paradox SP6000 panel. The (alarm) system we will be installing will basically be a panel, wireless unit (for remote arming and sensors) and a bunch of hardwired PIRs and a keypad. The system will also have a radio and probably telephone link to the security company monitoring station.

Now I believe the SP6000 can connect to an IP100 module which plugs into an IP network and then allows user interfacing to the alarm via a) their proprietory "Winload" software or b) a web browser on the network. I haven't investigated this aspect thoroughly and the security companies I've spoken to locally have no experience with it.

It will be a large and fairly expensive bummer if the alarm system and LMCE cannot talk to each other.... well, not the end of the world, but certainly it would be nice if they could. So if anyone has any comments or experience to feed me before I sign the contract, please speak up! Otherwise, I'll take one for the team and document my experiences here for the next guy in the same situation.


Pages: 1 ... 27 28 [29] 30 31