Re: CellHunter legend

2009-11-21 Thread Alex (Maxious) Sadleir
On Sun, Nov 22, 2009 at 12:39 PM, Walery Strauch  wrote:
> Hi,
>
> my CellHunter on SHR (pre-nov2009-core-updates) shows me:
>
> Provider:       o2 - de (262/07)
> Cell:           A102 / EA0E / 25
> ...
>
> I was trying to find some documentation about this but in vain...
> So my guess is this:
>
> Provider:       o2 - de (MCC/MNC)
> Cell:           LAC / cellID / signalStrength
>
Correct!
> but what says signalStrength?
> Is 25 much?
It comes from the FSO library that allows access to the GSM hardware (
http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.Monitor.html;hb=HEAD#GetNeighbourCellInformation
). In cellhunter, signal strength is defined as "(rxlevel / 2) +2"
where rxlevel is Recieved Field Level as a percentage. So 25 would be
almost half strength? I'm getting values between 12 and 18 so that's
not very good but my phone service isn't always stable.

> What is the maximum?
52? You would have to be very close to get that, I'm sure.
> How to find out which cell is on house of my neighbor?
There are some tools for accessing the Cellhunter database at the
bottom of the website - http://ch.omoco.de/cellhunter/
I think you would have to download the CSV GPS and plot/filter the
points to find which cell covers which house.
> Has cell on one house only one MNC, or are there splits for the provider?
Each SIM card can only pick up one MNC/network but one house may be
covered by several networks/MNC.
>
> Thanks
>
> Walery ;o)
>
> --
> Follow me:
> http://twitter.com/walery
>
> ___
> support mailing list
> support@lists.openmoko.org
> https://lists.openmoko.org/mailman/listinfo/support
>

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


CellHunter legend

2009-11-21 Thread Walery Strauch
Hi,

my CellHunter on SHR (pre-nov2009-core-updates) shows me:

Provider:   o2 - de (262/07)
Cell:   A102 / EA0E / 25
...

I was trying to find some documentation about this but in vain...
So my guess is this:

Provider:   o2 - de (MCC/MNC)
Cell:   LAC / cellID / signalStrength

but what says signalStrength?
Is 25 much?
What is the maximum?
How to find out which cell is on house of my neighbor?
Has cell on one house only one MNC, or are there splits for the provider?

Thanks

Walery ;o)

-- 
Follow me:
http://twitter.com/walery

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: connection between Freerunner and openSUSE 11.2

2009-11-21 Thread arne anka
tbh, i never really was happy mit nm or any "intelligent" automatism  
trying to manage the connection to the fr.
nm usually is overcharged with the concept of _multiple_ network  
interfaces being up and connected at the sam time and produces spretty  
much a mess.

your best bet is to handle it by yourself, using /etc/network/interfaces  
(be aware, taht suse since its earliest times refuse to use sensible and  
widely used mechanisms, but forces you to use that horrible yast!)

my /etc/network/interfaces looks like below

# The loopback network interface
auto lo
iface lo inet loopback

allow-hotplug usb0
iface usb0 inet static
 address 192.168.0.200
 netmask 255.255.255.0
 network 192.168.0.0
 post-up iptables -A POSTROUTING -t nat -j MASQUERADE -s  
192.168.0.0/24
 post-up echo 1 > /proc/sys/net/ipv4/ip_forward
 post-up iptables -P FORWARD ACCEPT

## The primary network interface
## network-manager stupidly seems to use the last defined connection
allow-hotplug eth0
iface eth0 inet dhcp

relevant is the usb0 stanza (i modified the udev rule to retain the device  
usb0, per default it should be ethX, probably eth1 on your box).

in theory, nm should ignore any device explicitely configured in the file  
above, but in praxi it usually fails, check
/etc/NetworkManager/nm-system-settings.conf
for the entry

[ifupdown]
managed=false

to (hopefully) force nm to ignore those devices in /etc/network/interfaces.

this works on a debian/unstable.
if suse does not allow this kind of configuration (yast creates its own  
little world), try yast and configure there manually the necessary  
information.

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


connection between Freerunner and openSUSE 11.2

2009-11-21 Thread Sven Hartrumpf
Hi all.

I am trying to connect via USB to a Freerunner
from an openSUSE 11.2 box (which uses NetworkManager).
When I connect the cable, the following messages occur
in /var/log/messages.

Nov 21 15:36:40 ki97 kernel: [32902.783138] usb 4-1: new full speed USB device 
using uhci_hcd and address 5
Nov 21 15:36:41 ki97 kernel: [32902.977210] usb 4-1: New USB device found, 
idVendor=1457, idProduct=5122
Nov 21 15:36:41 ki97 kernel: [32902.977219] usb 4-1: New USB device strings: 
Mfr=1, Product=2, SerialNumber=0
Nov 21 15:36:41 ki97 kernel: [32902.977227] usb 4-1: Product: RNDIS/Ethernet 
Gadget
Nov 21 15:36:41 ki97 kernel: [32902.977234] usb 4-1: Manufacturer: Linux 
2.6.29-rc3 with s3c2410_udc
Nov 21 15:36:41 ki97 kernel: [32902.977461] usb 4-1: configuration #1 chosen 
from 2 choices
Nov 21 15:36:41 ki97 kernel: [32902.992551] eth1: register 'cdc_ether' at 
usb-:00:1a.1-1, CDC Ethernet Device, 00:1f:11:01:32:3c
Nov 21 15:36:41 ki97 ifup: Service network not started and mode 'auto' -> 
skipping
Nov 21 15:36:45 ki97 nm-system-settings: Added default wired connection 'Auto 
eth1' for /org/freedesktop/Hal/devices/net_00_1f_11_01_32_3c
Nov 21 15:36:45 ki97 dhclient: Internet Systems Consortium DHCP Client V3.1.2p1
Nov 21 15:36:45 ki97 dhclient: Copyright 2004-2009 Internet Systems Consortium.
Nov 21 15:36:45 ki97 dhclient: All rights reserved.
Nov 21 15:36:45 ki97 dhclient: For info, please visit 
http://www.isc.org/sw/dhcp/
Nov 21 15:36:45 ki97 dhclient: 
Nov 21 15:36:45 ki97 dhclient: Listening on LPF/eth1/00:1f:11:01:32:3c
Nov 21 15:36:45 ki97 dhclient: Sending on   LPF/eth1/00:1f:11:01:32:3c
Nov 21 15:36:45 ki97 dhclient: Sending on   Socket/fallback
Nov 21 15:36:46 ki97 avahi-daemon[1820]: Registering new address record for 
fe80::21f:11ff:fe01:323c on eth1.*.
Nov 21 15:36:48 ki97 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 
interval 3
Nov 21 15:36:51 ki97 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 
interval 4
Nov 21 15:36:55 ki97 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 
interval 7
Nov 21 15:36:55 ki97 kernel: [32917.119292] eth1: no IPv6 routers present
Nov 21 15:37:02 ki97 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 
interval 9
Nov 21 15:37:11 ki97 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 
interval 15
Nov 21 15:37:26 ki97 dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 
interval 17

Afterwards ifconfig eth1 reports the following:

The problem is that no IP4 is assigned.
I have checked the wiki but they talk about older Linux versions.

Greetings
Sven

___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support