Re: Ethernet over USB and UDEV

2009-05-03 Thread Timo Juhani Lindfors
Esben Stien b...@esben-stien.name writes:
 Devices like these got no MAC address, apparently. 

Hmm? My usb0 surely has a mac address. What makes you think your
device doesn't?



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


[debian] can't install zhone

2009-05-03 Thread Jeffrey Ratcliffe
# apt-get install zhone
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  zhone: Depends: libevas-engines (= 0.9.9.050+svn20090204)
E: Broken packages

Are Debian users using a different dialer?

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


Re: disassembling the device?

2009-05-03 Thread Rask Ingemann Lambertsen
On Sat, May 02, 2009 at 03:43:24PM +0200, Dr. H. Nikolaus Schaller wrote:
 http://wiki.openmoko.org/wiki/Disassembling_Neo1973
 
 It is the same for the Neo Freerunner

   As to the part about bending the side of the back cover away from the
headphone connector, I found that it works relatively easily if you insert a
small (1.6 mm) flat head screwdriver between the headphone connector and the
PCB retaining clip right next to it. To the other side of the headphone
connector is a white plastic spacer that you might damage if you insert the
screwdriver there. And when you lift the side of the PCB, check that the
Bluetooth module clears the battery compartment before you move the PCB
sideways.

-- 
Rask Ingemann Lambertsen
Danish law requires addresses in e-mail to be logged and stored for a year

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


[debian] xfce startup problems

2009-05-03 Thread Jeffrey Ratcliffe
I'm getting the following errors in .xsession-errors when starting xfce:

matchbox-wm: unable to open theme: /usr/share/themes/Xfce/matchbox/theme.xml
(xfce4-panel:2373): xfce4-panel-WARNING **: xfce4-panel is not running
(xfce4-settings-helper:2374): xfce4-settings-helper-CRITICAL **: XI is
not present or too old.
(xfce4-settings-helper:2374): xfce4-settings-helper-CRITICAL **:
Failed to initialize the Xkb extension.
(xfce4-settings-helper:2374): xfce4-settings-helper-CRITICAL **:
Failed to initialize the Accessibility extension.
(xfce4-settings-helper:2374): Wnck-WARNING **: Property _NET_WM_NAME
contained invalid UTF-8

How do I get a keyboard up?

Regards

Jeff

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


Re: Ethernet over USB and UDEV

2009-05-03 Thread Mikko Rauhala
su, 2009-05-03 kello 23:13 +0200, Esben Stien kirjoitti:
 These type of cables presents itself to the operating system as
 Ethernet over USB devices, ie, network cards, but without any MAC
 address. This address has to be given by the operating system. 

Hm. I was under the impression that a USB ethernet gadget (for instance,
Neo) gives its MAC (which may be randomized from the locally
administered address space, if there's no reservation otherwise) to the
host, simply because it makes sense for a USB network adapter to work
this way - it's how every other kind of ethernet adapter does it... Thus
the gadget would be in control and a well-behaved gadget could have a
constant MAC (or not, as it happens, but this wouldn't be a general
property of Ethernet over USB devices).

This ol' bug entry and its first comment here seems to support my idea
of what's going on: http://docs.openmoko.org/trac/ticket/1023

I don't think we need any kernel patches for this. The kernel very well
supports fixed MAC addresses that are provided to it at kernel boot time
parameter. - laforge

It would be nice if that could be changed other than giving a boot
parameter; then the first boot could, before initializing USB
networking, load the BT MAC (again possibly flipping the local bit),
store it under /etc (for the following bootups, no need to power-up BT),
and use that.

'course, what you could do without tweaking the kernel is check the
bootloader's parameters for a MAC setting on boot, and if there isn't
any, stick the current purely randomized MAC in there. This would ensure
that the same randomized MAC would remain in use as long as the
bootloader settings remain, and would be implementable wholly in
userspace, given tools to read/write the bootloader environment.
Downside: no clear relationship to an existing MAC in the device, but
perhaps people can live without that. ;]

-- 
Mikko Rauhala m...@iki.fi   - http://www.iki.fi/mjr/blog/  
The Finnish Pirate Party - http://piraattipuolue.fi/  
World Transhumanist Association  - http://transhumanism.org/  
Singularity Institute- http://singinst.org/  



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


Re: The myth of missed phone calls (was: OM2008.12 - basic usage instructions?)

2009-05-03 Thread Joerg Reisenweber
Am So  3. Mai 2009 schrieb Rask Ingemann Lambertsen:
 On Sat, May 02, 2009 at 11:10:28AM +0200, Jeffrey Ratcliffe wrote:
 
  I have to access the image from somewhere. At 270Mb, it is to big to
  fit in flash at the same time as an OS. I can't plug in 2 uSDs,
 
USB card reader if you have one.
 
  so I
  would like to mount the directory where the image is stored on the
  host computer, so that I can dd to the device in /dev
 
One or more of the following ought to do the trick. If you use a USB card
 reader, it will be /dev/sda instead of /dev/mmcblk0:
 
 # wget URL-to-image -O /dev/mmcblk0
 # scp location-of-image /dev/mmcblk0
 sorry the image is .tgz, so you'll need to pipe it thru tar
/j


signature.asc
Description: This is a digitally signed message part.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support