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

Pages: 1 2 3 [4] 5
I haven't researched this much further so I hope it hasn't been covered before but possibly not as these are pretty new spec machines. The above machine, when I try to detect and boot as MD from a 10.04 (or 8.10) core does more or less the following-

Picks up the PXE server etc, no problem, reads basic image but then goes through a whole lot of screen stuff and stops at something which usually has the word "panic" in it. I found similar behaviour with my newish HP Probook 6560b (although I haven't tried on my latest 10.04 core).

My question(s) are-

How do I troubleshoot to establish what the problem(s) are. It looks like unsupported hardware but which part.... if I can establish that we may be able to fix it or at least document which hardware is not supported to assist others.

Are there logs I can look at if it only gets this far? I can screenshot (literally) what shows up at the panic stage and attach but the original error has probably scrolled off the screen at that stage.

At one stage I thought I saw complaints about the NIC... could it be that? I could try to find the chipset or whatever of the onboard NIC.

Another thought for troubleshooting was to try to run a 10.04 live CD and see if it has any issues.... if so, it could be a basic kubuntu 10.04 issue that can be addressed, if not, I could at least report the system-specs in a linux-kind-of-way....

Any advice, pointers?

And, while I'm in a verbose mode, might be nice to have a kind of a troubleshooting flowchart on the wiki for things like this... yes, I'm volunteering ;-)


NIC: Integrated Intel 82579LM Gigabit Network Connection (10/100/1000 NIC)
CPU: Intel® Core™ i5-2520M (2.50 GHz, 3 MB L3 cache)
Chipset: Mobile Intel® QM67 Express
GPU: AMD Radeon HD 6470M with 512 MB dedicated DDR3 video memory

Users / Media director stuck in screensaver (8.10)
« on: April 29, 2012, 08:13:20 pm »
I've got a pretty stable 8.10 installation running but haven't had the media directors on for long periods of time. Today the thinkpad (Ibm T30 notebook) has run all day and at the moment is stuck in screensaver and not responding to keystrokes or mouse clicks. The images are still changing but I can't get back to the onscreen orbiter.

Any ideas how to troubleshoot? Logs I should look at?
Is there a way to "force" the MD to respond from another orbiter? Perhaps one of the commands in /usr/pluto/bin? Or a DCE command I should send?

aha- I see that starting up the audio (playing music) on that MD from another orbiter works- it brings up the remote and back to onscreen orbiter.
The only other thing that I can think of checking is the screensaver pics- I know they're supposed to be a certain max size and I'm using my own pics which definitely aren't sized appropriately... and I did see some notes in the screensaver log about downscaling- perhaps this is tying up the processor or something? I'll try sorting that out and seeing if it has any effect.

Other suggestions welcome.

Ok, may be related to my other post regarding the libdvdcss2 libraries.

Maybe it is a sources.list thing, I don't know but after the above, I tried running the and failed at the mdadm.conf stage as per the messages below. I have done nothing (not even apt-get update or apt-get upgrade) after doing a basic install from 8.10 final dvd, then installing libdvdcss2 (after a fashion) and then running Diskless_Create.

Anyone have any ideas?

Errors (and point of hang) from Diskless_Create script:
Code: [Select]
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.27-17-generic
Can not write log, openpty() failed (/dev/pts not mounted?)
Selecting previously deselected package pluto-storage-devices.
(Reading database ... 29382 files and directories currently installed.)
Unpacking pluto-storage-devices (from .../pluto-storage-devices_2. ...
Adding `diversion of /bin/umount to /bin/umount.wraped by pluto-storage-devices'
Adding `diversion of /bin/mount to /bin/mount.wraped by pluto-storage-devices'
Selecting previously deselected package pluto-test-serial-port.
Unpacking pluto-test-serial-port (from .../pluto-test-serial-port_2. ...
Selecting previously deselected package mdadm.
Unpacking mdadm (from .../mdadm_2.6.7-3ubuntu8_i386.deb) ...
Can not write log, openpty() failed (/dev/pts not mounted?)
Setting up mdadm (2.6.7-3ubuntu8) ...
Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: /dev/MAKEDEV: not found
Generating mdadm.conf...

My sources.list file, in case it's relevant-

Code: [Select]
deb file:/usr/pluto/deb-cache/ ./
deb stable  main
deb intrepid  beta2
deb intrepid  main restricted universe multiverse
deb intrepid-security  main restricted multiverse universe
deb intrepid-updates  main restricted multiverse universe
deb intrepid  free non-free
deb-src intrepid  main restricted multiverse universe
deb-src intrepid-security  main restricted multiverse universe
deb-src intrepid-updates  main restricted multiverse universe
deb intrepid  main universe multiverse
deb replacements_debian  main
deb main  main non-free contrib
deb 20dev_ubuntu  main

Anyone have any ideas? Any log files I should check?

Thanks in advance.


Installation issues / DVD libraries install 8.10
« on: April 11, 2012, 08:23:55 am »
Had a brief issue adding the libdvdcss2 ilbarary to my 8.10 install, thought I'd mention it here in case it helps someone-

Code: [Select]
apt-get update
apt-get install libdvdcss2
ran fine until I got errors:
Code: [Select]
Setting up radvd (1:1.1-2ubuntu2) ...                                           
Starting radvd: [Apr 11 08:05:41] radvd: syntax error in /etc/radvd.conf, line 2:                                                                               
[Apr 11 08:05:41] radvd: error parsing or activating the config file: /etc/radvd.conf                                                                           
invoke-rc.d: initscript radvd, action "start" failed.                           
dpkg: error processing radvd (--configure):                                     
 subprocess post-installation script returned error exit status 1               
Setting up libdvdcss2 (1.2.10-0.2medibuntu1) ...                               

Processing triggers for libc6 ...
ldconfig deferred processing now taking place
Errors were encountered while processing:   
E: Sub-process /usr/bin/dpkg returned an error code (1)
dcerouter_1027763:~# cp /usr/share/doc/radvd/examples/simple-radvd.conf /etc/radvd.conf   
I followed the steps in the following
I had the same issue.  I solved it by copying radvd.conf from /usr/share/doc/radvd/examples/simple-radvd.conf to /etc/radvd.conf, and then doing apt-get install to resume the upgrade.  I would concur with Murdock as it's likely an upstream issue.  The radvd.conf file that was installed by apt had two blank lines in it, which is why apt barfed an error on trying to restart the service.


And that got past the initial errors but when I reran apt-get install libdvdcss2 I got errors relating to the eth0 card:

Code: [Select]
Setting up radvd (1:1.1-2ubuntu2) ...
Starting radvd: [Apr 11 08:11:51] radvd: interface eth0 is not RUNNING
[Apr 11 08:11:51] radvd: interface eth0 does not exist
[Apr 11 08:11:51] radvd: error parsing or activating the config file: /etc/radvd.conf
invoke-rc.d: initscript radvd, action "start" failed.
dpkg: error processing radvd (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
E: Sub-process /usr/bin/dpkg returned an error code (1)
It seems that radvd was trying to do something with eth0 and on my system eth0 is actually the internal network... so I checked out the /etc/radvd.conf file and it had:
Code: [Select]
interface eth0
   AdvSendAdvert on;
   prefix 2001:db8::/64
So I switched the eth0 to eth1 in the above conf file and then the apt-get-install libdvdcss2 ran through fine.

I presume the above conf file needs to point to an external (internet) network.

Installation issues / Intel Sandy bridge graphics on 10.04 [solved]
« on: April 04, 2012, 10:58:41 am »
OK, I'm starting a new forking thread here. I mean, I'm forking the thread or something like that because my other can deal with the hanging after initrd on dvd install which is something else.,12499.0.html

The problem, to re-iterate, is "Failed to setup X".

The chipset is Intel Sandy Bridge graphics.
Code: [Select]
00:02.0 VGA compatible controller [0300]: Intel Corporation Sandy Bridge Integrated Graphics Controller [8086:0102] (rev 09)

The auto-setup wants to use an intel driver (fair enough, it's an intel chip) but the comment from l3mce below probably still applies


I will tell you that this will NOT work on Sandy Bridge/HD3000. Just too new for 1004.

So, where to now? Well, as far as the x-configuration goes - this is ultimately my headless core so I really just need basic graphics on it. Is there some way we can fall back to a simple vesa driver or something like that?

Or should I be doing something nasty to configure this one that will not work for everyone else

eg. I did find a link to a set of steps for getting sandy bridge graphics working under 10.04

I guess first prize would be to get it working well for everyone (ie right driver auto-installed etc). If possible, I'd like to help with that. Let me know l3mce?

2nd prize would be to get it working badly for everyone - ie wrong driver but enough graphics performance to use on very basic core.

3rd prize would be a nasty hack that allows me to set up my own system but has to be repeated by anyone else with similar hardware.

Installation issues / 1004 install hangs after INITRD message
« on: April 03, 2012, 01:12:07 pm »
Giving 1004 a go....

1. Downloaded 201203211118 snapshot and burned to DVD.
2. Install past the kubuntu stuff, seemed to go fine, got to the point where the text messages from lmce were coming up
3. Last text message that came up on the screen over the splash image was something to do with INITRD... stayed there a while, when I moved the mouse it disappeared and no activity
after that.

Eventually +- hour with no hdd or dvd activity and I powered off.

Is there any install log or anything I can look at to see how far it got and what the problem was?

In the meantime, I will try the internet install...

P.S. hardware:

NIC1: Integrated
Graphics: Integrated
NIC2: Realtek something or other PCI.

Users / core/hybrid hanging on ctrl-alt-fx keys - can't get back to ui
« on: January 31, 2012, 12:18:59 pm »
Has anyone else had this problem with MDs or hybrid/cores. My core is running UI1 because I'm planning for it to sit in the closet when I'm done setting up and not bothering with NVidia on this machine if I can avoid it....

That said, all seems to run ok until I try to switch out of the UI-

Either to get to command line via ctrl-alt-f2 or whatever or if I start the KDE desktop. In either case, I don't seem able to get back to the Orbiter UI.

Actually, I think they're different issues:

If I go to KDE desktop, the machine seems to carry on running OK but I can't get back to the UI. I've tried:
  • Clicking on the "Orbiter renderer" in the taskbar but nothing happens
  • Logging out of KDE - but then I just get to the KDE login screen
  • ctrl-alt-fx
  • but then I end up with the problem below:
If I go from the UI to a tty, using ctrl-alt-fx key, I can't get back to the UI. As soon as I hit ctrl-alt-f7 I see the UI but it has some blurred stripes at the top and the machine appears to hang. At that point nothing but a hard power-off works... I think, though I haven't tested extensively yet, it even stops functioning as a router/dhcp server etc.

I will investigate further but has anyone had these issues?

Hi All

Trying to keep the budget down and I have an old notebook that I'd like to use to supply basic stereo sound to my old Onkyo stereo AMP in the lounge.

I took out the HDD which was faulty and noisy and have successfully used the T30 to run as a thin-client off fedora 13 (using ltsp) and that worked reasonably for driving the audio.

Now that I'm embracing LMCE  :D I would like to try to get similar functionality there- basically be able to play my music through the amp. Theoretically, it should be a nicer solution, too, because using a mobile orbiter (or any other) I can control the music remotely.... pretty cool.

The problem I'm having, though, is the setup of the MD. When trying to start the AVWizard the first time, I get a blue screen with a text box saing "Failed to setup X". Naturally, this doesn't surprise me- after all it's an ATI Radeon card and I knew we need Nvidia chipsets for stuff to work nicely in LMCE. But... I don't need high quality video here, or even video at all for that matter, or even graphics... the MD could run headlessly once set up and be controlled via orbiter. But it first needs to be set up!

So, I'm wanting to try a couple of routes and need some advice-

First Prize: Try to get the AVWizard to work- get past the "Failed to setup X" point.
  • I've looked at the http:// wiki and haven't had much luck with that - it appears I already have the latest drivers but
    the Xorg log still shows "Fatal error No screens" or something similar
  • I've tried to replace xorg.conf.pluto.avwizard with an xorg.conf file off the web that supposedly works for the T30 but xorg.conf.pluto.avwizard seems to get "overwritten" everytime the MD is restarted, perhaps because AVWizard is running?

Second Prize: Bypass AVWizard somehow, "force" setup and just start it without X.
Is this an option? Can I potentially just setup my MD in the webadmin page. Video setup really isn't important to me provided the sound works. I probably won't even use the screen but obviously if the MD won't start up properly because of incorrect video config that would be a problem.

Any thoughts/advice/ help welcome. I'll post my findings here.

Starting a new thread on this one because I seem to have sorted out the MD to some extent so this is now more about how to get the above orbiter to work.

Some progress with onboard bluetooth of md (hp 6710b notebook)- UI detected my symbian 60 phone but when I tried to select it in the wizard, the phone popped up a message asking for a passcode or passkey to receive info from the MD. 1234 did not work. Should it do that? What passcode should I use? Now it doesn't seem to detect it any more. Will get into admin site and see if I can see the device.

I can get the MD to detect the device, I choose Symbian S60 but then when (I presume) the MD tries to send the app to the phone (Nokia 5800), the phone responds wanting a passcode. It (the phone) won't do anything until you enter some number.

I tried entering 1234, but no luck; I tried just waiting without entering anything. Either way, the MD soon says it failed to setup the device, try again or contact support.

I've searched the forum for this but it only comes up once or twice. The one solution is to open a kde desktop and then make the phone discoverable and pair at there. That didn't work for me... nothing popped up and when I tried from the MD side to search for the device it wants to make it an "input" device and can't find any "input" services on it.

Any ideas? What I didn't try, I think is searching for the "moon-33" from my phone and trying to connect so I'll try that one this evening.

However, to get back to the beginning, I found deleting the orbiter for the phone from the admin webpage, then restarting the MD and turning bluetooth on the phone on seemed to work to get the pop-up again.

Another question- can I just download the orbiter software to my phone some other way and then try to make it work?

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

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  :)

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.


This is just sad! I finally get to trying an install on my new hardware for my new core and I don't even get past step 1!

Basically I downloaded the image, verify MD5 checksum and burn image to DVD. Then I boot DVD on my new hardware and get to the Menu screen (Linux MCE, Install Kubuntu, Test CD etc) but whatever option I choose from there, I get the KUBUNTU plus scrolling bar for about 40 secs after which that disappears and the screen goes to sleep.

Have just, this morning, on the same machine, installed Fedora 16 with no issues at all from bootable DVD so the DVD drive seems to be working and no other major issues with hardware.

Where do I start trouble-shooting this?

Firstly, I booted the dvd on my laptop and tried the kubuntu live and it worked fine so the burn appears to be ok. Obviously some combination between this image/ software and my new hardware?

Now I'm busy downloading the latest snapshot LinuxMCE-8.10-25224-i386.iso hoping that will somehow be different. I can also try the internet install method.

Any other suggestions?

My hardware:

Motherboard: FOXCONN H61MX-V DDR3 LGA1155 M
HDD: SEAGATE 2TB SATA 3.0 3.5" 5900

Yes, I know, onboard graphics is not Nvidia... not sure what it is actually or how to find out but the place that built it had some issues putting in the cheaper Nvidia cards. Apparently motherboard threw errors. They reckoned the cheapest that would work was pretty expensive and would require a PSU upgrade. I thought I'd leave that and see if I could just get the install done... after all, this is ultimately supposed to be a headless core. Could the onboard graphics be the problem? Even at this stage of the install? Otherwise, how do I get to the bottom of it?

Any suggestions welcome.

Installation issues / Media Director with video capture
« on: January 06, 2012, 01:35:29 pm »
Hi Everyone

Some advice please- I believe the recommendation is to put the video capture card into the core. My planned layout at present (I'm planning the system but have already done most of the network wiring) has the core sitting in the closet with the Gig switch and ADSL modem but a long way from the satellite decoder.

My plan was to have a media director in the TV room with the capture card, then the output from the satellite decoder would be fed to the MD capture card and presumably magically through to the core for redistribution / recording etc.

Firstly, is this possible or does the capture card have to be on the core?

And, if so, what are the issues going to be? The most obvious to me seem to be that if you're capturing video directly to the core you don't use bandwidth on the network line between core and switch... the capture input arrives via the PCI bus instead. So any time video is captured it's narrowing the bottleneck to the core. Are there other factors?

I'm trying to think why I don't want the core in the TV room..... apart from noise and space.... when I remember the reason, I'll post back.

Pages: 1 2 3 [4] 5