Am Freitag, 2. Juli 2010, 15:52:20 schrieb sferic:
> I currently use shr unstable 2.6.32 on an ext3 partition of sd card.
> Everything works fine except networking on usb. As far as I can see is the
> USB host resource is not loaded:
> root@om-gta02 / # shr-settings Connectivity shr_usb.Usb
> SHR Settings
> DeprecationWarning: object.__init__() takes no parameters
> super(Connection, self).__init__(*args, **kwargs)
> DEBUG: creating window: ['Connectivity', '', ['shr_usb.Usb']]
> Launcher loaded in 3.64 sec
> Loading module shr_usb.Usb...
> Module shr_usb.Usb can't be loaded!
> Traceback (most recent call last):
> File "/usr/bin/shr-settings", line 72, in renderModules
> cont = mod2.createView()
> File "/usr/lib/python2.6/site-packages/shr_settings_modules/shr_usb.py",
> line 94, in createView
> usbpolicy = self.usb.GetResourcePolicy("UsbHost")
> File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 68, in
> return self._proxy_method(*args, **keywords)
> File "/usr/lib/python2.6/site-packages/dbus/proxies.py", line 140, in
> File "/usr/lib/python2.6/site-packages/dbus/connection.py", line 622, in
> message, timeout)
> DBusException: org.freesmartphone.Usage.ResourceUnknown: Resource UsbHost
> had never been registered
> Page loaded in 0.90 sec
> The wifi connection works fine, however. The wifi connection works fine,
> however, and updates are easily made. Who can help?
With the new kernel the usb interface on your _host_ will be something
different than with the old one... ethX changed.
> Many thanks in advance
Am Freitag, 2. Juli 2010, 16:13:49 schrieb Fox Mulder:
> Am 02.07.2010 16:05, schrieb Klaus 'mrmoku' Kurzmann:
> > With the new kernel the usb interface on your _host_ will be something
> > different than with the old one... ethX changed.
> You mean that the host (pc and not gta02) will enumerate another name
> than ethX or just another number X when i attach my gta02?
on PC another X like in eth2 instead of eth1 for example.
> I'm right in the middle of the big upgrade to 2.6.32 so i have to wait
> until i can test it. :)
go ahead now :-)
OK, had no more problems. SHR-U appears as eth8 and I could connect without problems through ssh. But I had made mistakes in the allocation of performance rights for the various scripts that I need to get me to connect through my PC to the Internet (at three different distrubution is perhaps understandable ).