Re: USB Kernel problem with latest SHR unstable
On Fri, 24 Apr 2009 16:38:59 +1000 Denis Johnson wrote: > I'm not sure who or how to report this but since I have gone through > the test and it has taken some time to resolve. > > Flashing the latest SHR image and kernel from > http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April > > uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin > > I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb > on the host could see the neo but could not ifup usb0 > > Only after reflashing just the kernel back to Apr 9, could I again > reconnect via SSH. I have not tried kernels posted between those dates > to work out where the problem starts. > > Howver to confirm it, I have reflashed back to the latest 23rd April > but could not connect, then reflashed back to 9th April and worked > again. > > Both report 2.6.29-rc3 via 'uname -r' > > cheers Denis > have you tried "ifup ethx" (with x the number of the new interface)? I've been told it is eth on the host now, but it doesn't work for me either ... Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
Sorry to reply to my own post. Issue not quite as described. Between reflashing from 23rd April to 9th, one of the attempts at connecting also involved a reboot of my Ubuntu host. Which still failed to allow me to connect with the Kernel from the 2rd. Reflashing with the kernel from the 9th then worked. However, repeating the exercise as described bellow, also fails on the Kernel from the 9th. So something else is still at play here and it may be Ubuntu/host related. On Fri, Apr 24, 2009 at 4:38 PM, Denis Johnson wrote: > I'm not sure who or how to report this but since I have gone through > the test and it has taken some time to resolve. > > Flashing the latest SHR image and kernel from > http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April > > uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin > > I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb > on the host could see the neo but could not ifup usb0 > > Only after reflashing just the kernel back to Apr 9, could I again > reconnect via SSH. I have not tried kernels posted between those dates > to work out where the problem starts. > > Howver to confirm it, I have reflashed back to the latest 23rd April > but could not connect, then reflashed back to 9th April and worked > again. > > Both report 2.6.29-rc3 via 'uname -r' > > cheers Denis > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
Am Freitag 24 April 2009 08:57:48 schrieb Denis Johnson: > Sorry to reply to my own post. Issue not quite as described. > > Between reflashing from 23rd April to 9th, one of the attempts at > connecting also involved a reboot of my Ubuntu host. Which still > failed to allow me to connect with the Kernel from the 2rd. Reflashing > with the kernel from the 9th then worked. However, repeating the > exercise as described bellow, also fails on the Kernel from the 9th. > So something else is still at play here and it may be Ubuntu/host > related. > > On Fri, Apr 24, 2009 at 4:38 PM, Denis Johnson wrote: > > I'm not sure who or how to report this but since I have gone through > > the test and it has taken some time to resolve. > > > > Flashing the latest SHR image and kernel from > > http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April > > > > uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3 > >.4-om-gta02.bin > > > > I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb > > on the host could see the neo but could not ifup usb0 > > > > Only after reflashing just the kernel back to Apr 9, could I again > > reconnect via SSH. I have not tried kernels posted between those dates > > to work out where the problem starts. > > > > Howver to confirm it, I have reflashed back to the latest 23rd April > > but could not connect, then reflashed back to 9th April and worked > > again. > > > > Both report 2.6.29-rc3 via 'uname -r' > > > > cheers Denis > Did you try Franky's suggestion? It is indeed ethX now... Klaus 'mrmoku' Kurzmann ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Fri, Apr 24, 2009 at 09:59:26PM +1200, Robin Paulson wrote: > 2009/4/24 Klaus 'mrmoku' Kurzmann : > > Did you try Franky's suggestion? It is indeed ethX now... > > what number is 'x'? > > i tried with 0, 1 and 2, and 0 and 1 gave a 'no such device' error, 2 > gave 'unknown interface' Perhaps you could try looking in /var/log/syslog on Ubuntu? If unsure :- Unplug the USB, run 'tail -f /var/log/syslog' then plug it back in and post the output to the list. Cheers Ben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/24 Ben Thompson : >> i tried with 0, 1 and 2, and 0 and 1 gave a 'no such device' error, 2 >> gave 'unknown interface' > > Perhaps you could try looking in /var/log/syslog on Ubuntu? > > If unsure :- > Unplug the USB, run 'tail -f /var/log/syslog' then plug it back in and > post the output to the list. ok, i'm confused now. why do i want to run this on my host? the problem's with the phone, isn't it? anyway: Apr 24 22:20:01 inzy-laptop /USR/SBIN/CRON[16759]: (root) CMD ([ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null) Apr 24 22:20:04 inzy-laptop kernel: [12898.209072] eth1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge) Apr 24 22:20:34 inzy-laptop kernel: [12928.209045] eth1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: > 2009/4/24 Ben Thompson : > ok, i'm confused now. why do i want to run this on my host? the > problem's with the phone, isn't it? I don't know why, but the interface name on my host changed. For me it's now eth1. dmesg looks like this when i plug in my neo: usb 8-1: new full speed USB device using uhci_hcd and address 5 usb 8-1: New USB device found, idVendor=1457, idProduct=5122 usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 8-1: Product: RNDIS/Ethernet Gadget usb 8-1: Manufacturer: Linux 2.6.29-rc3 with s3c2410_udc usb 8-1: configuration #1 chosen from 2 choices eth1 (cdc_ether): not using net_device_ops yet eth1: register 'cdc_ether' at usb-:00:1d.3-1, CDC Ethernet Device, 00:1f:11:01:72:33 eth1: no IPv6 routers present so if u look at the beginning of the last three lines you see the interface name. greets Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/24 Klaus 'mrmoku' Kurzmann : > Did you try Franky's suggestion? It is indeed ethX now... what number is 'x'? i tried with 0, 1 and 2, and 0 and 1 gave a 'no such device' error, 2 gave 'unknown interface' ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
Robin Paulson wrote: > 2009/4/24 Klaus 'mrmoku' Kurzmann : >> Did you try Franky's suggestion? It is indeed ethX now... > > what number is 'x'? > > i tried with 0, 1 and 2, and 0 and 1 gave a 'no such device' error, 2 > gave 'unknown interface' > Please post here output of /sbin/ip link show It would be much easier for everyone than just guessing the name of the network device. signature.asc Description: OpenPGP digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann wrote: > Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: >> 2009/4/24 Ben Thompson : >> ok, i'm confused now. why do i want to run this on my host? the >> problem's with the phone, isn't it? > > I don't know why, but the interface name on my host changed. For me it's now > eth1. Check: http://lists.openmoko.org/pipermail/devel/2009-April/005384.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Friday 24 April 2009 15:16:38 Nelson Castillo wrote: > On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann > > wrote: > > Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: > >> 2009/4/24 Ben Thompson : > >> ok, i'm confused now. why do i want to run this on my host? the > >> problem's with the phone, isn't it? > > > > I don't know why, but the interface name on my host changed. For me it's > > now eth1. > > Check: > > http://lists.openmoko.org/pipermail/devel/2009-April/005384.html > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community On my Ubuntu 8.10 the shr-unstable behaves exactly as described in the link. The X depends on your number of network cards. I use a notebook which has a cable and a Wifi ethernet adapter named eth0 and eth1. However the Neo becomes eth3 as it connects. I collected the information from the Wiki about USB Networking in a script, which i use until I managed to integrate the Neo better into Ubuntu and it's various network configuration mechanisms. The script has a variable for the interface as the first line. Adapt it to your needs and run it after you have connected your Neo to the USB port. I use "ifconfig" to check out the known network cards and their configuration. Regards thomas No Neo: eth1 Link encap:Ethernet HWaddr 00:15:00:22:c5:db inet6 addr: fe80::215:ff:fe22:c5db/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:117175 errors:141 dropped:141 overruns:0 frame:0 TX packets:9346 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3955 (3.9 KB) TX bytes:4599 (4.5 KB) Interrupt:21 Memory:c840-c8400fff loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:48 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2560 (2.5 KB) TX bytes:2560 (2.5 KB) Neo connected: eth1 Link encap:Ethernet HWaddr 00:15:00:22:c5:db inet6 addr: fe80::215:ff:fe22:c5db/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:131173 errors:141 dropped:141 overruns:0 frame:0 TX packets:10491 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3955 (3.9 KB) TX bytes:4599 (4.5 KB) Interrupt:21 Memory:c840-c8400fff eth3 Link encap:Ethernet HWaddr 00:1f:11:01:2e:ee inet6 addr: fe80::21f:11ff:fe01:2eee/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1564 (1.5 KB) TX bytes:580 (580.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:48 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2560 (2.5 KB) TX bytes:2560 (2.5 KB) Neo configured with frnet.sh eth1 Link encap:Ethernet HWaddr 00:15:00:22:c5:db inet6 addr: fe80::215:ff:fe22:c5db/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:133181 errors:141 dropped:141 overruns:0 frame:0 TX packets:10667 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3955 (3.9 KB) TX bytes:4599 (4.5 KB) Interrupt:21 Memory:c840-c8400fff eth3 Link encap:Ethernet HWaddr 00:1f:11:01:2e:ee inet addr:192.168.0.200 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::21f:11ff:fe01:2eee/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:46 errors:0 dropped:0 overruns:0 frame:0 TX packets:57 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5546 (5.5 KB) TX bytes:10629 (10.6 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:48 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2560 (2.5 KB) TX bytes:2560 (2.5 KB) frnet.sh Description: application/shellscript ___ Openmoko community mailing list community@lists.openmoko.org http://lists
Re: USB Kernel problem with latest SHR unstable
On Fri, Apr 24, 2009 at 4:08 PM, Thomas Otterbein wrote: > On Friday 24 April 2009 15:16:38 Nelson Castillo wrote: >> On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann >> >> wrote: >> > Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: >> >> 2009/4/24 Ben Thompson : >> >> ok, i'm confused now. why do i want to run this on my host? the >> >> problem's with the phone, isn't it? >> > >> > I don't know why, but the interface name on my host changed. For me it's >> > now eth1. >> >> Check: >> >> http://lists.openmoko.org/pipermail/devel/2009-April/005384.html >> >> ___ >> Openmoko community mailing list >> community@lists.openmoko.org >> http://lists.openmoko.org/mailman/listinfo/community > > On my Ubuntu 8.10 the shr-unstable behaves exactly as described in the link. > The X depends on your number of network cards. I use a notebook which has a > cable and a Wifi ethernet adapter named eth0 and eth1. However the Neo becomes > eth3 as it connects. I collected the information from the Wiki about USB > Networking in a script, which i use until I managed to integrate the Neo > better into Ubuntu and it's various network configuration mechanisms. The > script has a variable for the interface as the first line. Adapt it to your > needs and run it after you have connected your Neo to the USB port. > I use "ifconfig" to check out the known network cards and their configuration. > On my Fedora 10 laptop nothing appears to happen anymore when I plug in the Neo. No messages in /var/log/messages, nothing in dmesg. [m8...@fedora10 ~]$ sudo /sbin/ip link show 1: lo: mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1c:23:01:c4:a0 brd ff:ff:ff:ff:ff:ff 3: wmaster0: mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ieee802.11 00:1b:77:60:df:64 brd ff:ff:ff:ff:ff:ff 4: wlan0: mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1b:77:60:df:64 brd ff:ff:ff:ff:ff:ff 5: pan0: mtu 1500 qdisc noop state DOWN link/ether 52:6d:38:6a:32:49 brd ff:ff:ff:ff:ff:ff I am booting from U-Boot (in NAND) though, the post referenced above mentions SHR-testing (the distro on the SD I'm booting from) behaving differently when booted from QI. I get the same result on my Xubuntu laptop so I fear that something else got broken with the opkg update, opkg upgrade I performed. So far I haven't found a description of what is needed on the side of the FreeRunner itself. When I check ifconfig -a on the FreeRunner I see an eth0 interface with no IP address, eth0:avah alias with IP 169.254.7.134 and the loopback device. ip link show shows the loopback device and the eth0 interface. When I check the /etc/network/interfaces it contains a comment right before the auto usb0 section saying: # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr ifup usb0 retruns: ifup: interface usb0 already configured but ifconfig usb0 returns: ifconfig usb0: error fetching interface information: Device not found modprobe g_ether on the FreeRunner fails to locate the module so maybe some modules are missing? Or is this module no longer needed? loading the usbnet module on either the Fedora or the Xubuntu laptop does not help. One final note: the hardware is fine, when I start FDOM from the device's main memory it is still recognized. Thanks in advance. Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/25 Nelson Castillo : > On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann > wrote: >> Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: >>> 2009/4/24 Ben Thompson : >>> ok, i'm confused now. why do i want to run this on my host? the >>> problem's with the phone, isn't it? >> >> I don't know why, but the interface name on my host changed. For me it's now >> eth1. > > Check: > > http://lists.openmoko.org/pipermail/devel/2009-April/005384.html well, this is interesting. lsusb no longer shows my neo as attached what gives? i rebooted the phone and the laptop, and still nothing dmesg gives this, which looks like it can see the phone, but not figure out what it is [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 [ 1481.644065] usb 1-1: device descriptor read/64, error -110 [ 1481.863121] usb 1-1: new full speed USB device using uhci_hcd and address 19 [ 1482.092099] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1483.696065] usb 1-1: new full speed USB device using uhci_hcd and address 20 [ 1498.808067] usb 1-1: device descriptor read/64, error -110 [ 1514.032503] usb 1-1: device descriptor read/64, error -110 [ 1514.248047] usb 1-1: new full speed USB device using uhci_hcd and address 21 [ 1529.361074] usb 1-1: device descriptor read/64, error -110 [ 1544.581050] usb 1-1: device descriptor read/64, error -110 [ 1544.797061] usb 1-1: new full speed USB device using uhci_hcd and address 22 [ 1555.205040] usb 1-1: device not accepting address 22, error -110 [ 1555.319135] usb 1-1: new full speed USB device using uhci_hcd and address 23 [ 1565.728069] usb 1-1: device not accepting address 23, error -110 [ 1565.729365] hub 1-0:1.0: unable to enumerate USB device on port 1 any ideas? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/24 Denis Johnson : > Flashing the latest SHR image and kernel from > http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April > > uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin > > I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb > on the host could see the neo but could not ifup usb0 > > Only after reflashing just the kernel back to Apr 9, could I again > reconnect via SSH. I have not tried kernels posted between those dates > to work out where the problem starts. > > Howver to confirm it, I have reflashed back to the latest 23rd April > but could not connect, then reflashed back to 9th April and worked > again. is this related to a discrepancy in the version of the modules? i.e. the modules not being the same as the version of the kernel? it's been pointed out to me that the kernel is version 2.6.29-rc3, while the modules are apparently version -rc2 where can i get an older version of the kernel - the only one on the shr site appears to be the latest, i.e. 22nd april? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/25 Robin Paulson : > 2009/4/24 Denis Johnson : >> Flashing the latest SHR image and kernel from >> http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April >> >> uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin >> >> I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb >> on the host could see the neo but could not ifup usb0 >> >> Only after reflashing just the kernel back to Apr 9, could I again >> reconnect via SSH. I have not tried kernels posted between those dates >> to work out where the problem starts. >> >> Howver to confirm it, I have reflashed back to the latest 23rd April >> but could not connect, then reflashed back to 9th April and worked >> again. well, i fixed it - i can now ssh into my freerunner. i'm not entirely sure what it was, but i think it was related to some fiddling i did with depmod and modprobe on the phone. i'm guessing some usb modules weren't loaded by default ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Sat, 25 Apr 2009 20:37:50 +1200 Robin Paulson wrote: > 2009/4/25 Robin Paulson : > > 2009/4/24 Denis Johnson : > >> Flashing the latest SHR image and kernel from > >> http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April > >> > >> uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin > >> > >> I could not connect via SSH over USB from my Ubuntu 8.10 host. > >> lsusb on the host could see the neo but could not ifup usb0 > >> > >> Only after reflashing just the kernel back to Apr 9, could I again > >> reconnect via SSH. I have not tried kernels posted between those > >> dates to work out where the problem starts. > >> > >> Howver to confirm it, I have reflashed back to the latest 23rd > >> April but could not connect, then reflashed back to 9th April and > >> worked again. > > well, i fixed it - i can now ssh into my freerunner. > > i'm not entirely sure what it was, but i think it was related to some > fiddling i did with depmod and modprobe on the phone. i'm guessing > some usb modules weren't loaded by default > ok, but how did you get to fiddle on the phone? Do you mean you actually used a terminal app, did some kind of modprobe on the phone and it started working? And now you don't remember what it was ... does this mean after the next reboot, you don't have ssh access anymore? Do the SHR people test these images? I've been told every time again it's the host (ethX instead of usb0), but I seriously believe something is wrong with the generated images ... my host fedora 10 system doesn't give any output in /var/log/messages when I plug in the phone with newer images (any "old" image reacts just fine), while it does give me info when I boot the phone in the NOR menu to flash it. To prove it myself, I will *again* flash my phone with the latest image/kernel found in http://build.shr-project.org/shr-unstable/images/ Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Sat, 25 Apr 2009 22:05:35 +0200 Franky Van Liedekerke wrote: > > ok, but how did you get to fiddle on the phone? Do you mean you > actually used a terminal app, did some kind of modprobe on the phone > and it started working? And now you don't remember what it was ... > does this mean after the next reboot, you don't have ssh access > anymore? Do the SHR people test these images? I've been told every > time again it's the host (ethX instead of usb0), but I seriously > believe something is wrong with the generated images ... my host > fedora 10 system doesn't give any output in /var/log/messages when I > plug in the phone with newer images (any "old" image reacts just > fine), while it does give me info when I boot the phone in the NOR > menu to flash it. To prove it myself, I will *again* flash my phone > with the latest image/kernel found in > http://build.shr-project.org/shr-unstable/images/ ok, I just tested this kernel and it seems to be ok now: it is eth1, and I've adapted my qtextended install script a bit, so it doesn't use the alias for the "rm" command. For the record, I tried from this url http://build.shr-project.org/shr-unstable/images/om-gta02/, the following rootfs and uImage: uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin openmoko-shr-lite-image-glibc-ipk--20090423-om-gta02.rootfs.jffs2 Although I don't like the following kernel messages, could somebody explain these? Apr 26 00:26:20 om-gta02 user.err kernel: [21474817.485000] HDQ error: 1 Apr 26 00:26:20 om-gta02 user.info kernel: [21474817.50] HDQ responds again Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/26 Franky Van Liedekerke : > ok, but how did you get to fiddle on the phone? Do you mean you > actually used a terminal app, did some kind of modprobe on the phone yes. > and it started working? And now you don't remember what it was ... does > this mean after the next reboot, you don't have ssh access anymore? no, i can still ssh in after rebooting > Do the SHR people test these images? I've been told every time again > it's the host (ethX instead of usb0), but I seriously believe something yes, eth4 on my laptop > is wrong with the generated images ... my host fedora 10 system doesn't > give any output in /var/log/messages when I plug in the phone with > newer images (any "old" image reacts just fine), while it does give me > info when I boot the phone in the NOR menu to flash it. try dmesg, you'll see lots of errors from it trying to recognise the phone when you try to connect to the phone, my understanding is it's talking to a kernel module on the phone. the relevant module was not loaded afaics. i ran lsmod on the phone, and nothing was returned. i think i ran depmod, then modprobe ehci_usb (or maybe ehci_usb) and depmod again, then plugged it in, and lsusb (on the laptop) revealed it as being connected (it wasn't previously shown) i could always see the phone fine while it was booted to nor > To prove it myself, I will *again* flash my phone with the latest > image/kernel found in http://build.shr-project.org/shr-unstable/images/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Sat, Apr 25, 2009 at 08:37:50PM +1200, Robin Paulson wrote: > i'm not entirely sure what it was, but i think it was related to some > fiddling i did with depmod and modprobe on the phone. i'm guessing > some usb modules weren't loaded by default The SHR packager forgot to run depmod before tarring up the rootfs. Alternatively, the initscripts should run depmod on startup. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
El Saturday, 25 de April de 2009 01:30:45 Robin Paulson va escriure: > rebooted the phone and the laptop, and still nothing > > dmesg gives this, which looks like it can see the phone, but not > figure out what it is > > [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 > [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and > address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 . > any ideas? I will try another usb cable or port ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/27 Jose Luis Perez Diez : > El Saturday, 25 de April de 2009 01:30:45 Robin Paulson va escriure: >> rebooted the phone and the laptop, and still nothing >> >> dmesg gives this, which looks like it can see the phone, but not >> figure out what it is >> >> [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 >> [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and >> address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 > . >> any ideas? > > I will try another usb cable or port no, there was nothing wrong with the port or cable - someone at shr hadn't run depmod before creating the tarball, and the modules for communicating over usb weren't being loaded. if you run depmod on your phone, it should clear it up ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Mon, Apr 27, 2009 at 10:43 AM, Robin Paulson wrote: > 2009/4/27 Jose Luis Perez Diez : >> El Saturday, 25 de April de 2009 01:30:45 Robin Paulson va escriure: >>> rebooted the phone and the laptop, and still nothing >>> >>> dmesg gives this, which looks like it can see the phone, but not >>> figure out what it is >>> >>> [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 >>> [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and >>> address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 >> . >>> any ideas? >> >> I will try another usb cable or port > > no, there was nothing wrong with the port or cable - someone at shr > hadn't run depmod before creating the tarball, and the modules for > communicating over usb weren't being loaded. if you run depmod on your > phone, it should clear it up It didn't when I tried this. I ended up flashing a newer version of SHR-testing (2009/04/22 if I remember corretly) and that one did work out of the box. That is untill I hit the "suspend" problem this morning... Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Mon, Apr 27, 2009 at 6:43 PM, Robin Paulson wrote: > no, there was nothing wrong with the port or cable - someone at shr > hadn't run depmod before creating the tarball, and the modules for > communicating over usb weren't being loaded. if you run depmod on your > phone, it should clear it up I apologise for reporting this and then disappearing. Sometimes there are just not enough hours in the day. I just want to confirm that a combination of running 'depmod' in terminal on the phone and also using 'ifconfig -a' on my host (now upgraded to Ubuntu 9.04), I found that when the phone is plugged in that I got an 'eth1' listed so I changed my scripts accordingly and I can now SSH in. I have not rebooted the neo or my host yet but if anything changes I will report here. Thanks, to all for your replies and assist. cheers Denis ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
