Re: qemu trouble...
Hallo Did you run modprobe gadgetfs default_uid=your uid before running QEMU? Yes. Output from mount: gadget on /dev/gadget type gadgetfs (rw,noexec,nosuid,nodev) Output from ls /dev/gadget/: insgesamt 0 dr-xr-xr-x 1 reddog root0 2007-07-23 11:50 . drwxr-xr-x 16 root root 4,4K 2007-07-24 09:53 .. -rw--- 1 reddog root0 2007-07-23 11:50 dummy_udc I get continual kernel ring messages (dmesg, also reported in syslog) of: dummy_udc dummy_udc: dequeued req deb73c40 from ep-c, len 4096, buf No i haven't such a message. But when i type usb_add gadget:1, the qemu says in the QEMU monitor: (qemu) Could not remove USB device '0.5' Why? Seems to me like he gets some errors and want trys an automatic usb_remove... Additionally, there are three lines output from QEMU's stdout/err: s3c_udc_handle_packet: EP0 overrun pcf_write: automatic Fast-charge enabled s3c_udc_handle_packet: EP0 overrun I killed the qemu much fuster this time an i could see this messages, too: [...] gadget_read: event error: 4 gadget_ep_setup: endpoint configuration failed: -1 gadget_read: event error: 4 [...] gadget_read: event error: 4 gadget_ep_setup: endpoint configuration failed: -1 gadget_read: event error: 4 [...] gadget_read: event error: 4 gadget_read: event error: 51 gadget_read: event error: 4 [...] gadget_read: event error: 4 gadget_read: event error: 51 gadget_read: event error: 4 [...] gadget_read: event error: 4 s3c_udc_handle_packet: EP0 overrun gadget_read: event error: 51 gadget_read: event error: 51 gadget_read: event error: 4 pcf_write: automatic Fast-charge enabled. gadget_read: event error: 51 gadget_read: event error: 51 gadget_read: event error: 4 [...] gadget_read: event error: 4 gadget_read: event error: 51 gadget_read: event error: 4 gadget_read: event error: 4 s3c_udc_handle_packet: EP0 overrun gadget_read: event error: 51 gadget_read: event error: 51 gadget_read: event error: 51 gadget_read: event error: 51 gadget_respond: packet write error: 3 gadget_read: event error: 4 [...] gadget_read: event error: 4 [...] ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0 I haven't a usb0 device! :-( SIOCSIFADDR: Kein passendes Gerät gefunden usb0: ERROR while getting interface flags: Kein passendes Gerät gefunden SIOCSIFNETMASK: Kein passendes Gerät gefunden It also says can't find gadgetfs if you don't have it specified in the config.h file before compiling qemu. Wow ... it's not ... at first i thought this could it be, but then i looked in the file ../config-host.h wich is included by config.h. In ../config-host.h is #define CONFIG_GADGETFS 1. Or do you mean that i have to specify the directory /dev/gadget? How can i do this? Tim Niemeyer signature.asc Description: Digital signature ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
Tim Niemeyer [EMAIL PROTECTED] wrote : No i haven't such a message. But when i type usb_add gadget:1, the qemu says in the QEMU monitor: (qemu) Could not remove USB device '0.5' Why? Seems to me like he gets some errors and want trys an automatic usb_remove... I get this when I try with 2.6.18. I'm thinking that you probably need the same kernel version on the host machine as is running inside QEMU to stand a chance of this working. Wow ... it's not ... at first i thought this could it be, but then i looked in the file ../config-host.h wich is included by config.h. In ../config-host.h is #define CONFIG_GADGETFS 1. Or do you mean that i have to specify the directory /dev/gadget? How can i do this? config-host.h should contain #define CONFIG_GADGETFS 1. Add that line and rebuild qemu if it isn't. --- G O Jones ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
John Seghers skrev: Heh. Yeah, I was puzzled by that when I first read the web page that describes this. Basically, the ifconfig command is specifying the IP address for the Desktop's end of the USB connection. The QEMU side of the connection seems to be hardwired to 192.168.0.202. That worried me for a while. But it not more hardwired then a static rule in /etc/network/interfaces on the phone :-) Easy to change, easy to say dhcp instead of static :-) /LaH ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: qemu trouble...
Giles Jones wrote: On 25 Jul 2007, at 23:42, John Seghers wrote: ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0 ssh [EMAIL PROTECTED] Interesting that the IP you use for usb0 is 192.168.0.200, then ssh into 202. I thought this was a typo then considered that it was deliberate. Heh. Yeah, I was puzzled by that when I first read the web page that describes this. Basically, the ifconfig command is specifying the IP address for the Desktop's end of the USB connection. The QEMU side of the connection seems to be hardwired to 192.168.0.202. Fortunately, the local net here at work is set up on 192.168.10.x so that I didn't have to add routes to isolate the mini-subnet formed by the USB connection. So the ssh to .202 is making a connection between .200 -- .202 - John ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
Hello I have also some problems with qemu. I have build everything with the MokoMakefile and it works really nice! ;-) But when i want to use the gadged system to ssh into my moko, i get some trouble... I figured out that i had to recompile my default Debian Etch Kernel an did it. Now it seems to be all like in the wiki describes: http://wiki.openmoko.org/wiki/OpenMoko_under_QEMU#Setting_up_USB_connection Has anyone an idea for me? Is something wrong? But when i then do the usb_add gadget:1 command the qemu repeats: ### gadget_read: event error: 4 gadget_read: event error: 4 gadget_read: event error: 4 gadget_read: event error: 4 gadget_read: event error: 4 ### In my Syslog i can see many entrys: ### dummy_udc dummy_udc: binding gadget driver 'gadgetfs' gadgetfs: bound to dummy_udc driver dummy_hcd dummy_hcd: port status 0x00010101 has changes dummy_hcd dummy_hcd: port status 0x00010101 has changes dummy_hcd dummy_hcd: port status 0x00100503 has changes usb 6-1: new high speed USB device using dummy_hcd and address 5 gadgetfs: connected gadgetfs: disconnected dummy_hcd dummy_hcd: port status 0x00100503 has changes dummy_udc dummy_udc: set_address = 5 gadgetfs: connected dummy_udc dummy_udc: enabled ep-a (ep3in-intr) maxpacket 16 dummy_udc dummy_udc: disabled ep-a dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 usb 6-1: string descriptor 0 read error: -32 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 usb 6-1: string descriptor 0 read error: -32 usb 6-1: configuration #1 chosen from 1 choice gadgetfs: configuration #1 ### This seems to repeat till i kill qemu and see this in my syslog: ### BUG: warning at drivers/usb/gadget/dummy_hcd.c:49 8/dummy_free_request() [f8cf156c] dummy_free_request+0x41/0x4e [dummy _hcd] [f8cf7413] gadgetfs_unbind+0x47/0x50 [gadgetfs ] [f8cf13a6] usb_gadget_unregister_driver+0x79/0 xd2 [dummy_hcd] [f8cf721f] dev_release+0x11/0x44 [gadgetfs] [c015ae41] __fput+0x8a/0x13f [c01589aa] filp_close+0x4e/0x54 [c011ead3] put_files_struct+0x65/0xa7 [c011fa43] do_exit+0x1d1/0x71b [c0120003] sys_exit_group+0x0/0xd [c0127a6d] get_signal_to_deliver+0x395/0x3bc [c01023a6] do_notify_resume+0x71/0x5d7 [c0126fc1] group_send_sig_info+0x4e/0x56 [c0117778] default_wake_function+0x0/0xc [c0124657] do_gettimeofday+0x31/0xce [c0131ffc] sys_futex+0xdc/0xf1 [c0102d0a] work_notifysig+0x13/0x19 dummy_hcd dummy_hcd: port status 0x00010100 has c hanges dummy_hcd dummy_hcd: port status 0x00010100 has c hanges usb 6-1: USB disconnect, address 5 ### Thanks... Tim Niemeyer signature.asc Description: Digital signature ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: qemu trouble...
Did you run modprobe gadgetfs default_uid=your uid before running QEMU? I get continual kernel ring messages (dmesg, also reported in syslog) of: dummy_udc dummy_udc: dequeued req deb73c40 from ep-c, len 4096, buf Additionally, there are three lines output from QEMU's stdout/err: s3c_udc_handle_packet: EP0 overrun pcf_write: automatic Fast-charge enabled s3c_udc_handle_packet: EP0 overrun However, if I go ahead and configure the USB interface and connect via ssh, it works: ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0 ssh [EMAIL PROTECTED] - John PS: I found that the error output someone else was quoting, Warning: could not find USB gadgetfs near the beginning of QEMU's run is due to not having mounted /dev/gadget. Tim Niemeyer wrote: Sent: Wednesday, July 25, 2007 6:29 AM To: community@lists.openmoko.org Subject: Re: qemu trouble... Hello I have also some problems with qemu. I have build everything with the MokoMakefile and it works really nice! ;-) But when i want to use the gadged system to ssh into my moko, i get some trouble... I figured out that i had to recompile my default Debian Etch Kernel an did it. Now it seems to be all like in the wiki describes: http://wiki.openmoko.org/wiki/OpenMoko_under_QEMU#Setting_up_USB_connectio n Has anyone an idea for me? Is something wrong? But when i then do the usb_add gadget:1 command the qemu repeats: ## # gadget_read: event error: 4 gadget_read: event error: 4 gadget_read: event error: 4 gadget_read: event error: 4 gadget_read: event error: 4 ## # In my Syslog i can see many entrys: ## # dummy_udc dummy_udc: binding gadget driver 'gadgetfs' gadgetfs: bound to dummy_udc driver dummy_hcd dummy_hcd: port status 0x00010101 has changes dummy_hcd dummy_hcd: port status 0x00010101 has changes dummy_hcd dummy_hcd: port status 0x00100503 has changes usb 6-1: new high speed USB device using dummy_hcd and address 5 gadgetfs: connected gadgetfs: disconnected dummy_hcd dummy_hcd: port status 0x00100503 has changes dummy_udc dummy_udc: set_address = 5 gadgetfs: connected dummy_udc dummy_udc: enabled ep-a (ep3in-intr) maxpacket 16 dummy_udc dummy_udc: disabled ep-a dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 usb 6-1: string descriptor 0 read error: -32 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 dummy_udc dummy_udc: stale req = dd372840 dummy_hcd dummy_hcd: ep ep0 halted, urb e912d5c0 usb 6-1: string descriptor 0 read error: -32 usb 6-1: configuration #1 chosen from 1 choice gadgetfs: configuration #1 ## # This seems to repeat till i kill qemu and see this in my syslog: ## # BUG: warning at drivers/usb/gadget/dummy_hcd.c:49 8/dummy_free_request() [f8cf156c] dummy_free_request+0x41/0x4e [dummy _hcd] [f8cf7413] gadgetfs_unbind+0x47/0x50 [gadgetfs ] [f8cf13a6] usb_gadget_unregister_driver+0x79/0 xd2 [dummy_hcd] [f8cf721f] dev_release+0x11/0x44 [gadgetfs] [c015ae41] __fput+0x8a/0x13f [c01589aa] filp_close+0x4e/0x54 [c011ead3] put_files_struct+0x65/0xa7 [c011fa43] do_exit+0x1d1/0x71b [c0120003] sys_exit_group+0x0/0xd [c0127a6d] get_signal_to_deliver+0x395/0x3bc [c01023a6] do_notify_resume+0x71/0x5d7 [c0126fc1] group_send_sig_info+0x4e/0x56 [c0117778] default_wake_function+0x0/0xc [c0124657] do_gettimeofday+0x31/0xce [c0131ffc] sys_futex+0xdc/0xf1 [c0102d0a] work_notifysig+0x13/0x19 dummy_hcd dummy_hcd: port status 0x00010100 has c hanges dummy_hcd dummy_hcd: port status 0x00010100 has c hanges usb 6-1: USB disconnect, address 5 ## # Thanks... Tim Niemeyer ___ OpenMoko
Re: qemu trouble...
On 25 Jul 2007, at 23:42, John Seghers wrote: Did you run modprobe gadgetfs default_uid=your uid before running QEMU? I get continual kernel ring messages (dmesg, also reported in syslog) of: dummy_udc dummy_udc: dequeued req deb73c40 from ep-c, len 4096, buf Additionally, there are three lines output from QEMU's stdout/err: s3c_udc_handle_packet: EP0 overrun pcf_write: automatic Fast-charge enabled s3c_udc_handle_packet: EP0 overrun However, if I go ahead and configure the USB interface and connect via ssh, it works: ifconfig usb0 inet 192.168.0.200 netmask 255.255.255.0 ssh [EMAIL PROTECTED] - John PS: I found that the error output someone else was quoting, Warning: could not find USB gadgetfs near the beginning of QEMU's run is due to not having mounted /dev/gadget. It also says can't find gadgetfs if you don't have it specified in the config.h file before compiling qemu. Interesting that the IP you use for usb0 is 192.168.0.200, then ssh into 202. I thought this was a typo then considered that it was deliberate. ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
Jeff Rush skrev: Hi Jeff! As I said... I have build the neo1973 qemu... but 'by hand'... It's a small build vs the mokomakefile build everything that's huge. - Lars, Yes, the onscreen keyboard does work, as in the GUI keyboard you click on with the mouse. I click in the upper-left box (white area, not icon) and the onscreen keyboard comes up in my QEMU image. Did not have that white box... compiled qemu with alsa sound support... probably a mistake... Now, when I stopped esd before starting qemu the keyboard works :-) More strange... the today app got it's icons, did not have them before (?!?). Once the today app did not start on boot... it feels a little random. Probably should rebuild qemu with no extra. - I can say that the ability to 'ssh' into the QEMU does work here, but it requires a few steps in the QEMU monitor each time you use it re usb_add gadget:1 that cannot be automated. The usb networking seams to demand a rebuild of the host kernel... I'm not so keen on that. Did try the tun/tap and user network stuff... But I don't believe it will work. That expect to emulate a ethernet nic and neo don't have an ethernet nic. Could probably build a neo kernel with ethernet, but then I think u-boot most go for a 'normal' rootfs... OK for my us... but then I'm back at setting up a crosscompile env for moko... ether a lot of hard experiments or using mokomakefile that will kill my machine (and then I still have to figure out how to make changes). I really would like a solution that works with network 'out of the box'. Ether a rootfs and kernel with ethernet support, or a hack to neo1973 qemu so it emulate a 'built in' usb-ethernet device that in turn talk to qemu user network and tun/tap interface. But I'm not sure I have understand the problem correctly... If I was I file a wishlist bug on neo1973 qemu. /LaH ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qemu trouble...
Not sure if this is dev or community... I manage to build the neo qemu and it works :-) Have made (flash.sh, downloaded the files manualt as download.sh did not work (no lynx)) a open moko image and it boots but... No on-screen keyboard makes it pretty useless. Anyone having the same problem or even a solution? Network don't work (qemu -net user)... Is this a limitation in the moko image, the neo qemu or my hostsystem (ubuntu 7.04)? Is it somehow solvable? Anyone successfully got network on there qemu moko systems, an in that case how? TIA /LaH ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
Hey Lars, Huzzah to you, sir, for getting that far. I got my ubuntu system up yesterday, but I haven't gotten some of the other pieces working. I haven't used OpenEmbedded or bitbake before. I use perforce at work. My ubuntu system is a new dual core box. Does the development environment use distcc? Cheers, Dan On 7/22/07, Lars Hallberg [EMAIL PROTECTED] wrote: Not sure if this is dev or community... I manage to build the neo qemu and it works :-) Have made (flash.sh, downloaded the files manualt as download.sh did not work (no lynx)) a open moko image and it boots but... No on-screen keyboard makes it pretty useless. Anyone having the same problem or even a solution? Network don't work (qemu -net user)... Is this a limitation in the moko image, the neo qemu or my hostsystem (ubuntu 7.04)? Is it somehow solvable? Anyone successfully got network on there qemu moko systems, an in that case how? TIA /LaH ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
Daniel Robinson skrev: Hey Lars, Huzzah to you, sir, for getting that far. I got my ubuntu system up yesterday, but I haven't gotten some of the other pieces working. I haven't used OpenEmbedded or bitbake before. I use perforce at work. I have not set up a complete build env (don't have room)... Just build the qemu according to Manual setup on: http://wiki.openmoko.org/wiki/OpenMoko_under_QEMU And downloaded prebuilt kernel, rootfs and u-boot... all in the above instructions. The 'extra' preparation I did was: install gcc 3.4 and run: # apt-get build-dep qemu That probably will install gcc 3.4 to :-) Then add --gcc=gcc-3.4 to the .configure arguments. To 'flash' the image You need to install lynx (for download) and netpbm (for flashing). HTH /LaH ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
Lars Hallberg wrote: Daniel Robinson skrev: Hey Lars, Huzzah to you, sir, for getting that far. I got my ubuntu system up yesterday, but I haven't gotten some of the other pieces working. I haven't used OpenEmbedded or bitbake before. I use perforce at work. I have not set up a complete build env (don't have room)... Just build the qemu according to Manual setup on: http://wiki.openmoko.org/wiki/OpenMoko_under_QEMU And downloaded prebuilt kernel, rootfs and u-boot... all in the above instructions. The 'extra' preparation I did was: install gcc 3.4 and run: # apt-get build-dep qemu I've not had the problems I'm seeing discussed on this list but then I used the MokoMakefile approach. One thing to note -- the OpenMoko build system comes with its own version of QEMU, with changes specific to the Neo1973. Running a stock QEMU outside the build environment will probably limit what you can do, in particular it lacks the virtual Neo1973 hardware they added. Re a few of the troubles, - Giles, I didn't have to modify any .h files to make it work, nor did I see any problems with the 8ma power you saw. - Lars, Yes, the onscreen keyboard does work, as in the GUI keyboard you click on with the mouse. I click in the upper-left box (white area, not icon) and the onscreen keyboard comes up in my QEMU image. - out of the box, it does not let you type into it using your desktop keyboard but you can add -usbdevice keyboard to make it work - I can say that the ability to 'ssh' into the QEMU does work here, but it requires a few steps in the QEMU monitor each time you use it re usb_add gadget:1 that cannot be automated. - To network into the QEMU image you must have gadget support in your host kernel. The Neo1973 docs talk about having a /dev/gadget file, for example with a gadgetfs mounted on it. I have to create it by hand each time I boot, as the udev system doesn't keep it around on my Gentoo system. I checked the source and you cannot move it elsewhere - the path is hardcoded. I hopes this helps, -Jeff ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qemu trouble...
On 22 Jul 2007, at 19:16, Jeff Rush wrote: - Giles, I didn't have to modify any .h files to make it work, nor did I see any problems with the 8ma power you saw. Like I said, it probaly depends on your kernel version which is why I'd like to know which is the best version for QEMU? ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
