Hi,
On 23/07/07, Ingmar RIeger <[EMAIL PROTECTED]> wrote:
Helo,
thanks for your tips. I tried it and here are my resultst step by step.
> $ 1) Reboot the computer.
Yes, I did.
> $ 2) check dmesg output "dmesg | tail -30" and you should see some
messages
> about finding USB devices.
Yes, there are some messages. Here is the output of "dmesg | tail -30 |
grep usb":
[EMAIL PROTECTED]:~$ dmesg | tail -30 | grep usb
[ 49.735491] usb 2-2: USB disconnect, address 4
[ 49.975376] usb 2-2: new low speed USB device using uhci_hcd and
address 5
[ 50.152854] usb 2-2: configuration #1 chosen from 1 choice
[ 50.176758] drivers/usb/input/ati_remote.c: Weird data, len=1 ff 00
00 00 00 00 ...
[ 288.284000] usb 2-2: USB disconnect, address 5
[ 288.528000] usb 2-2: new low speed USB device using uhci_hcd and
address 6
[ 288.704000] usb 2-2: configuration #1 chosen from 1 choice
[ 288.732000] drivers/usb/input/ati_remote.c: Weird data, len=1 ff 00
00 00 00 00 ...
> $ 3) do the modprobe, create /dev/gadget, and mount it.
Done this without errors.
> $ 4) run QEMU
The same as every try before.
[EMAIL PROTECTED]:~$ cd /home/myuser/openmoko/qemu-neo1973
&& ./arm-softmmu/qemu-system-arm -M neo -m 130 -mtdblock
openmoko/openmoko-flash.image -kernel openmoko/openmoko-kernel.bin -usb
-usbgadget -show-cursor -localtime -usbdevice keyboard
Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a
fatal
error, but for better emulation accuracy either use a 2.6 host Linux
kernel or
type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
Warning: could not find USB gadgetfs
I can only offer a guess. Please check that QEMU was compiled with
gadgetfs support, i.e. that "grep CONFIG_GADGETFS config-host.h"
prints:
#define CONFIG_GADGETFS 1
Another frequent cause of problems people have with qemu is that of
permissions on various files, the best way to check that the
permissions are Ok is by opening the given node using a tool like
"cat", e.g cat /dev/gadget/dummy_udc and checking if it reports
"Permission denied" for the user intending to run qemu. However in
your case this is not the problem because the Warning message would be
different then.
HTH,
Andrew
