Messages

1

Installation issues / apt-get update -> "Hash Sum mismatch"

« on: April 24, 2010, 11:18:28 pm »

Hello,
I am trying to install LinuxMCE beta 2 from DVD, but I am running into issue with apt-get update after first login to the kubuntu.

I was looking at the bug database, ubuntu forums and this forum, but I couldn't find an clear answer.

Basically when I am running the command:

Code: [Select]

$ apt-get update

Then the error occurs:

Code: [Select]

[...]
Hit http://debian.slimdevices.com stable/main Packages
Fetched 2B in 1s (2B/s)
W: Failed to fetch http://www.avenard.org/files/ubuntu-repos/dists/intrepid/release/binary-i386/Packages.bz2  Hash Sum mismatch

E: Some index files failed to download, they have been ignored, or old ones used instead.

I was trying to run:
apt-get -f update, apt-get clean, apt-get autoclean, but no success. Any hints / help really welcome!

2

Users / Re: 8.10 Weborbiter strange behavior + connect to proxy orbiter failed

« on: November 27, 2009, 05:23:00 pm »

This has always "just worked" for me...  There are 3 things that need to happen - 1) device created, 2) router reloaded, 3) orbiter (re)generated

Once you get the device created in the web admin per instructions, reload the router.  If nothing comes up, go to Web Admin --> Devices --> Orbiters.  If the proxy orbiter isn't regenerating, you can tell it to do a full regen, and wait for the progress bar to go all the way full two times.  Once it's done, you should be able to look at the web orbiter.  Reload the router if there are still issues - but I'm usually running by this point.

Ok after a while I gave it a second try and it worked. So the problem was with my nvidia drivers which I have installed manually and from then nothing could be installed as apt-get was failing due to some unresolved dependency. I suspect that some packages needed to be installed to make weborbiter working properly.

3

Users / Network layout question - all-in-one router.

« on: November 19, 2009, 02:09:40 am »

Hello,
I was reading back and forward all the topics about using two network cards, but I am wondering how to set up core correctly when the modem which is provided by my ISP is an all-in-one DSL modem with router, 4 port switch and build in access point.
 In my setup I will have:
  - n800 tablet with Internet access, to access the MD (wifi connection)
  - one computer with Internet access, to access the MD through the generic weborbiter (ethernet connected to the switch)
  - one netbook with Internet access, to access the MD through the generic weborbiter (wifi connection)
  - NAS connected (ethernet connected to the switch)

I was planning to connect the MD to the 4 port switch in the router and also core to that switch together with NAS and extra computer, so all ports in the switch will be occupied and let the core give the DHCP addresses. Add one virtual NIC to the core, so it will go through the same utp6 cable to the switch, configure the first NIC to access the internet and the second one connected to the same switch to access the rest of the devices at home on another subnet running the dhcp server.

I am wondering if the wifi connected devices will get the DHCP addresses from the core in such setup.

I am trying to reduce the number of toys/hardware in this setup and I am reluctant to buy yet another switch and access point. Please let me know what do you think

4

Users / Re: 8.10 Weborbiter strange behavior + connect to proxy orbiter failed

« on: November 17, 2009, 06:50:39 pm »

I have the same problem this week-end (network install) and after read you post and made a core reboot this morning it worked now !

I was trying this several times, but it didn't help. I would like to know how to find what is wrong and possibly fix it, otherwise I am left with quite unusable system

5

Users / Re: 8.10 Weborbiter strange behavior + connect to proxy orbiter failed

« on: November 17, 2009, 12:03:52 am »

Did you reload the DCE Router?  If you don't the device won't start...

I did Quick Reload Router and this didn't worked, also later I have rebooted the whole system without success.

6

Users / 8.10 Weborbiter strange behavior + connect to proxy orbiter failed

« on: November 16, 2009, 11:33:10 pm »

Hello,
I have reinstalled my LinuxMCE with beta 8.10, before I was using some alpha version on top of 8.10.

I have added web-orbiter (generic-orbiter) and it finished regenerating after which I did the quick reload.

The orbiter was listed but when I was trying to login, I was always getting the:
"Connect to proxy orbiter failed, please try again"

After this I have removed the web-orbiter from my device tree and re-added. While accessing the weborbiter.php site nothing was listed this time in the Device dropdown, so I have added yet another generic orbiter and now it was listed (In the device tree I had two generic orbiters, but only one was listed through the weborbiter.php). Anyhow the symptoms while I was trying accessing were the same:
"Connect to proxy orbiter failed, please try again"

Basically I was following the instructions from:
http://wiki.linuxmce.org/index.php/Add_Web_Orbiter

Could someone point me to the information how I could fix/debug the problem? What log level should I enable to find what might go wrong?

7

Users / Re: N800 can't connect using LinuxMCE Orbiter software :-( (SOLVED)

« on: October 22, 2009, 05:50:39 pm »

Add your wireless AP to the LAN side of your Core. Make sure that the internal DHCP for the AP is turned off (Your Core must provide DHCP to the LAN) and that the AP is on the same subnet to the Core.

Andrew,
Thanks for fast response, so before I will start changing those things I would like to double confirm that EVEN if I can ping the core and browse the core using web-browser from my N800 those steps are STILL required.

Ok I got it working in one subnet. It seems that the orbiter can't be in another subnet even if using different interface and those two devices can see each other.

8

Users / Re: N800 can't connect using LinuxMCE Orbiter software :-(

« on: October 22, 2009, 05:38:57 pm »

Add your wireless AP to the LAN side of your Core. Make sure that the internal DHCP for the AP is turned off (Your Core must provide DHCP to the LAN) and that the AP is on the same subnet to the Core.

Andrew,
Thanks for fast response, so before I will start changing those things I would like to double confirm that EVEN if I can ping the core and browse the core using web-browser from my N800 those steps are STILL required.

9

Users / N800 can't connect using LinuxMCE Orbiter software :-(

« on: October 22, 2009, 05:01:31 pm »

Hello,
I was trying to set up the N800 tablet without joy. The steps I was following are from:
http://wiki.linuxmce.org/index.php/Nokia_N800

I would like to know how to debug what's wrong:

 - I have downloaded the newest firmware and installed OS2008 - (Software Edition 2008 version 5.2008.43-7 for Nokia N800 / The latest IT OS DIABLO release for Nokia N800 )
   - the orbiter software for N800 was installed by clicking on: http://diapub.com/~michael/install/diablo.install
 - The LinuxMCE which I am using is based on 0810 - new-installer-alpha-latest.tar.gz from 2009-09-30
 - I did disable the firewall as I thought that this might be the issue, my system contains two cards, one wired and one wireless. The wired is connected to dhcp server and wireless is manually configured for different subnet.

I did setup the wifi to connect ad-hoc to the device as due to some wired bug I couldn't get the dhcp address from my router:
    ifconfig wlan0 down
    sudo iwconfig wlan0 mode ad-hoc
    sudo iwconfig wlan0 essid "testme"
    sudo ifconfig wlan0 up
    sudo ifconfig wlan0 192.168.80.1

I can ping the tablet:
 ping 192.168.80.129
 PING 192.168.80.129 (192.168.80.129) 56(84) bytes of data.
 64 bytes from 192.168.80.129: icmp_seq=1 ttl=255 time=18.9 ms
 64 bytes from 192.168.80.129: icmp_seq=2 ttl=255 time=13.0 ms

Also from the tablet I can open web-orbiter based on the webpage:
  http://192.168.80.1/lmce-admin/weborbiter.php

So when I am starting the LinuxMCE Orbiter pointing at the correct IP address and the Orbiter ID 76, which is the correct one, the symptoms are as in the wiki:
 "(If the Start Orbiter button stays "pushed" (i.e. blue) for only a few seconds then changes back to normal, then something has gone wrong. Check your network connection and verify the IP and Orbiter ID are correct.) "

I believe that everything is fine. Is this orbiter working with 0810? How to find out what might be wrong?