From: strangewanderer <str...@gm...> - 2009-07-28 18:08:02
|
I am new to gumstix and linux. I ordered an overo earth and a palo 43 with the LCD. I followed the instructions for making the build environment with minimal issues (can't get the toolchain to compile). I decided to do what the instructions (http://www.gumstix.net/Documentation/view/Overo/Getting-started/109.html) said and do the getting started by connecting through kermit. I cannot even get my linux (Ubuntu) system to recognize the gumstix. Anytime I run the first command (kermit -l /dev/ttyUSB0), it says, "can't open device." Also, the gumstix is not listed when I use lsusb in the terminal. Is there some patch I need to add? I am sure I am just missing something small. Joe -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24699359.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: strangewanderer <str...@gm...> - 2009-07-28 19:55:06
|
I forgot to mention this earlier. Also, I am having issues with just a straight boot. Straight out of the box I powered the machine and it came to the angstrom login screen. I put root as the login, but it did not go anywhere. I tried using the resulting "root@overo:~#" lines as a command line but those yielded nothing. It seemed like the cursor was way off of the screen. I thought this was supposed to boot to linux. Is this supposed to be a really old version of linux? After many attempts and idea of how to get past this I found that if I used gumstix as the login it asked me for a password, but I cannot seem to find any password that will work. Is there some password I was supposed to set? The last thing I did was the boot from SD card tutorial. I checked the files several times to make sure they were correct. Also I made sure the SD card was unmounted correctly before disconnecting. -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24706713.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: anon4321 <ano...@co...> - 2009-07-30 19:12:28
|
The usb chip for the console is somewhat generic so the lsusb output won't have "overo" in it. Connect the overo via just usb again (no power required) and post the output of lsusb. Also note if a LED lights on the palo43 when the USB is plugged into without power. Futhermore, check that the overo is fully seated in the palo43 and that you have the USB cable plugged into the CONSOLE port which I believe is on the right side if the power connector is on the left side. strangewanderer wrote: > > I forgot to mention this earlier. > > Also, I am having issues with just a straight boot. Straight out of the > box I powered the machine and it came to the angstrom login screen. I put > root as the login, but it did not go anywhere. I tried using the > resulting "root@overo:~#" lines as a command line but those yielded > nothing. It seemed like the cursor was way off of the screen. I thought > this was supposed to boot to linux. Is this supposed to be a really old > version of linux? > > After many attempts and idea of how to get past this I found that if I > used gumstix as the login it asked me for a password, but I cannot seem to > find any password that will work. > > Is there some password I was supposed to set? > > The last thing I did was the boot from SD card tutorial. I checked the > files several times to make sure they were correct. Also I made sure the > SD card was unmounted correctly before disconnecting. > > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24745525.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: strangewanderer <str...@gm...> - 2009-07-30 19:22:04
|
When connected, the console LED is on. I am pretty sure that the Overo is seated correctly because it was able to boot from SD, unfortunately I need to fix the screen size issue now. While the cable is connected to the palo and the LED is on and connect to the computer, after a restart and a few minutes to be sure, this is what lsusb yields: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 062a:0000 Creative Labs Optical mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Thanks anon4321 wrote: > > The usb chip for the console is somewhat generic so the lsusb output won't > have "overo" in it. > Connect the overo via just usb again (no power required) and post the > output of lsusb. Also note if a LED lights on the palo43 when the USB is > plugged into without power. Futhermore, check that the overo is fully > seated in the palo43 and that you have the USB cable plugged into the > CONSOLE port which I believe is on the right side if the power connector > is on the left side. > > > strangewanderer wrote: >> >> I forgot to mention this earlier. >> >> Also, I am having issues with just a straight boot. Straight out of the >> box I powered the machine and it came to the angstrom login screen. I >> put root as the login, but it did not go anywhere. I tried using the >> resulting "root@overo:~#" lines as a command line but those yielded >> nothing. It seemed like the cursor was way off of the screen. I thought >> this was supposed to boot to linux. Is this supposed to be a really old >> version of linux? >> >> After many attempts and idea of how to get past this I found that if I >> used gumstix as the login it asked me for a password, but I cannot seem >> to find any password that will work. >> >> Is there some password I was supposed to set? >> >> The last thing I did was the boot from SD card tutorial. I checked the >> files several times to make sure they were correct. Also I made sure the >> SD card was unmounted correctly before disconnecting. >> >> > > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24745701.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: anon4321 <ano...@co...> - 2009-07-30 19:34:20
|
Sorry, I'm at work so I can't test stuff out before replying. Try lsusb -v or lsusb -t or lsusb -vt. Also, is the overo connected to a port directly on the PC or through a hub? -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24745903.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: strangewanderer <str...@gm...> - 2009-07-30 19:39:06
|
I'll try those. Thanks for the command. Straight to the PC. Does it need a hub? anon4321 wrote: > > Sorry, I'm at work so I can't test stuff out before replying. Try lsusb > -v or lsusb -t or lsusb -vt. > > Also, is the overo connected to a port directly on the PC or through a > hub? > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24745982.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: anon4321 <ano...@co...> - 2009-07-30 19:43:04
|
Straight to the PC is best to eliminate any hub problems. Post the output of lsusb -v and lsusb -t. Also post the output of ls -l /dev/tty*USB* strangewanderer wrote: > > I'll try those. Thanks for the command. Straight to the PC. Does it > need a hub? > > > anon4321 wrote: >> >> Sorry, I'm at work so I can't test stuff out before replying. Try lsusb >> -v or lsusb -t or lsusb -vt. >> >> Also, is the overo connected to a port directly on the PC or through a >> hub? >> > > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24746047.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: anon4321 <ano...@co...> - 2009-07-30 20:00:49
|
I haven't connected to the console under Ubuntu for some time and I forget if this is required but if ls -l /dev/tty*USB* shows /dev/ttyUSB0 (zero) exists then try this command to run kermit: sudo kermit -l /dev/ttyUSB0 (the option is dash-lowercase-L) If you get the kermit prompt, type set flow-control none set carrier-watch off set speed 115200 connect Then power-up the overo and get ready to press a key on the PC to stop autoboot. sudo may be required if only root can open /dev/ttyUSB0 which I vaguely remember to be the case. Good luck. anon4321 wrote: > > Straight to the PC is best to eliminate any hub problems. > > Post the output of lsusb -v and lsusb -t. > > Also post the output of ls -l /dev/tty*USB* > > > strangewanderer wrote: >> >> I'll try those. Thanks for the command. Straight to the PC. Does it >> need a hub? >> >> >> anon4321 wrote: >>> >>> Sorry, I'm at work so I can't test stuff out before replying. Try >>> lsusb -v or lsusb -t or lsusb -vt. >>> >>> Also, is the overo connected to a port directly on the PC or through a >>> hub? >>> >> >> > > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24746306.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: strangewanderer <str...@gm...> - 2009-07-30 20:51:12
|
I ran those commands they follow. I was looking through the output and it looks like the only USB that it has being used is the one with the mouse. mjl@mjl-linux:~$ lsusb -v Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0002 2.0 root hub bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 can't get hub descriptor: Operation not permitted can't get device qualifier: Operation not permitted can't get debug descriptor: Operation not permitted cannot read device status, Operation not permitted (1) Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) Bus 002 Device 002: ID 062a:0000 Creative Labs Optical mouse Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x062a Creative Labs idProduct 0x0000 Optical mouse bcdDevice 0.00 iManufacturer 0 iProduct 0 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 52 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 10 cannot read device status, Operation not permitted (1) Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 64 idVendor 0x1d6b Linux Foundation idProduct 0x0001 1.1 root hub bcdDevice 2.06 iManufacturer 3 iProduct 2 iSerial 1 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 255 can't get hub descriptor: Operation not permitted cannot read device status, Operation not permitted (1) mjl@mjl-linux:~$ lsusb -t Bus# 1 `-Dev# 1 Vendor 0x1d6b Product 0x0002 Bus# 2 `-Dev# 1 Vendor 0x1d6b Product 0x0001 Bus# 3 `-Dev# 1 Vendor 0x1d6b Product 0x0001 Bus# 4 `-Dev# 1 Vendor 0x1d6b Product 0x0001 mjl@mjl-linux:~$ ls -l /dev/tty*USB* ls: cannot access /dev/tty*USB*: No such file or directory -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24747092.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: anon4321 <ano...@co...> - 2009-07-30 22:42:26
|
Ok, now I'm home I can look on my machine. If you do just lsusb you should see a line similar to: Bus 002 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC FTDI makes to FT232 that is on the palo43. If you don't see that, linux isn't detecting the palo43. If you have a Windows machine, you can try plugging in the overo/palo43 under Windows to see if Windows detects the FTDI chip. If you are prompted for a driver disk, that is a good sign. You can download the drivers for Windows here: http://www.ftdichip.com/FTDrivers.htm If Windows sees the overo/palo43, you can try connecting to it under windows using something like TeraTerm http://en.sourceforge.jp/projects/ttssh2/ If Windows can't detect it, try a different USB port. If that fails, the palo43 may be bad, contact gumstix. strangewanderer wrote: > > I ran those commands they follow. I was looking through the output and it > looks like the only USB that it has being used is the one with the mouse. > > mjl@mjl-linux:~$ lsusb -v > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 0 Full speed (or root) hub > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0002 2.0 root hub > bcdDevice 2.06 > iManufacturer 3 > iProduct 2 > iSerial 1 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 Full speed (or root) hub > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0004 1x 4 bytes > bInterval 12 > can't get hub descriptor: Operation not permitted > can't get device qualifier: Operation not permitted > can't get debug descriptor: Operation not permitted > cannot read device status, Operation not permitted (1) > > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 0 Full speed (or root) hub > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0001 1.1 root hub > bcdDevice 2.06 > iManufacturer 3 > iProduct 2 > iSerial 1 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 Full speed (or root) hub > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0002 1x 2 bytes > bInterval 255 > can't get hub descriptor: Operation not permitted > cannot read device status, Operation not permitted (1) > > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 0 Full speed (or root) hub > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0001 1.1 root hub > bcdDevice 2.06 > iManufacturer 3 > iProduct 2 > iSerial 1 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 Full speed (or root) hub > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0002 1x 2 bytes > bInterval 255 > can't get hub descriptor: Operation not permitted > cannot read device status, Operation not permitted (1) > > Bus 002 Device 002: ID 062a:0000 Creative Labs Optical mouse > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x062a Creative Labs > idProduct 0x0000 Optical mouse > bcdDevice 0.00 > iManufacturer 0 > iProduct 0 > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 34 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 2 Mouse > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.10 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 52 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0004 1x 4 bytes > bInterval 10 > cannot read device status, Operation not permitted (1) > > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 0 Full speed (or root) hub > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0001 1.1 root hub > bcdDevice 2.06 > iManufacturer 3 > iProduct 2 > iSerial 1 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 Full speed (or root) hub > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0002 1x 2 bytes > bInterval 255 > can't get hub descriptor: Operation not permitted > cannot read device status, Operation not permitted (1) > mjl@mjl-linux:~$ lsusb -t > Bus# 1 > `-Dev# 1 Vendor 0x1d6b Product 0x0002 > Bus# 2 > `-Dev# 1 Vendor 0x1d6b Product 0x0001 > Bus# 3 > `-Dev# 1 Vendor 0x1d6b Product 0x0001 > Bus# 4 > `-Dev# 1 Vendor 0x1d6b Product 0x0001 > mjl@mjl-linux:~$ ls -l /dev/tty*USB* > ls: cannot access /dev/tty*USB*: No such file or directory > > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24748503.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Joe2 <joe...@ho...> - 2009-07-30 22:12:19
|
Well there is a chance you have a bad board, but it is unlikely. Just to check have you tried Sudo? Try this before trying "lsusb -v" do a "sudo su" with out the quotes, provide your password, then try the "lsusb -v" and kermit again. You will know your su because it will look like this: mjl@mjl-linux:~# with the "#" sign. This can also be done safer by typing sudo before each command you need executed in su. If your new to Linux su=sudo=root which is basically administrator. This should ensure that not seeing the usb is not a permissions thing. Also what version of ubuntu? as I recall there are some settings that have to be changed after 8.04. So if you are running 8.10 or 9.04 then you may need to check that. strangewanderer wrote: > > I ran those commands they follow. I was looking through the output and it > looks like the only USB that it has being used is the one with the mouse. > > mjl@mjl-linux:~$ lsusb -v > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 0 Full speed (or root) hub > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0002 2.0 root hub > bcdDevice 2.06 > iManufacturer 3 > iProduct 2 > iSerial 1 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 Full speed (or root) hub > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0004 1x 4 bytes > bInterval 12 > can't get hub descriptor: Operation not permitted > can't get device qualifier: Operation not permitted > can't get debug descriptor: Operation not permitted > cannot read device status, Operation not permitted (1) > > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 0 Full speed (or root) hub > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0001 1.1 root hub > bcdDevice 2.06 > iManufacturer 3 > iProduct 2 > iSerial 1 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 Full speed (or root) hub > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0002 1x 2 bytes > bInterval 255 > can't get hub descriptor: Operation not permitted > cannot read device status, Operation not permitted (1) > > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 0 Full speed (or root) hub > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0001 1.1 root hub > bcdDevice 2.06 > iManufacturer 3 > iProduct 2 > iSerial 1 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 Full speed (or root) hub > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0002 1x 2 bytes > bInterval 255 > can't get hub descriptor: Operation not permitted > cannot read device status, Operation not permitted (1) > > Bus 002 Device 002: ID 062a:0000 Creative Labs Optical mouse > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x062a Creative Labs > idProduct 0x0000 Optical mouse > bcdDevice 0.00 > iManufacturer 0 > iProduct 0 > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 34 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 2 Mouse > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.10 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 52 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0004 1x 4 bytes > bInterval 10 > cannot read device status, Operation not permitted (1) > > Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 9 Hub > bDeviceSubClass 0 Unused > bDeviceProtocol 0 Full speed (or root) hub > bMaxPacketSize0 64 > idVendor 0x1d6b Linux Foundation > idProduct 0x0001 1.1 root hub > bcdDevice 2.06 > iManufacturer 3 > iProduct 2 > iSerial 1 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xe0 > Self Powered > Remote Wakeup > MaxPower 0mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 Hub > bInterfaceSubClass 0 Unused > bInterfaceProtocol 0 Full speed (or root) hub > iInterface 0 > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0002 1x 2 bytes > bInterval 255 > can't get hub descriptor: Operation not permitted > cannot read device status, Operation not permitted (1) > mjl@mjl-linux:~$ lsusb -t > Bus# 1 > `-Dev# 1 Vendor 0x1d6b Product 0x0002 > Bus# 2 > `-Dev# 1 Vendor 0x1d6b Product 0x0001 > Bus# 3 > `-Dev# 1 Vendor 0x1d6b Product 0x0001 > Bus# 4 > `-Dev# 1 Vendor 0x1d6b Product 0x0001 > mjl@mjl-linux:~$ ls -l /dev/tty*USB* > ls: cannot access /dev/tty*USB*: No such file or directory > > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24748188.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: strangewanderer <str...@gm...> - 2009-07-30 22:33:42
|
I am using 9.04. I have always been using the sudo command. I tried the root but it did not work either. Do you have any idea what that change would be. I have been looking through the synaptic package manager for something about and I have added a lot of packages but with no change. -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24748410.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: anon4321 <ano...@co...> - 2009-07-30 22:46:56
|
I am using 9.04 also. As far as I can remember, there isn't anything you need to do to get the FTDI chip to be recognized. strangewanderer wrote: > > I am using 9.04. I have always been using the sudo command. I tried the > root but it did not work either. Do you have any idea what that change > would be. I have been looking through the synaptic package manager for > something about and I have added a lot of packages but with no change. > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24748557.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Joe2 <joe...@ho...> - 2009-07-30 23:02:13
|
Sorry I was mistaken, the adjustments were for the build environment. There should be nothing you need to do to get kermit working, nor to have the FTDI chip recognized, assuming your on a standard build and not one of the low disk space Ubuntu builds, there is some chance that drives were left out of the laptop (low space) build of Ubuntu. Any case the previous Message explains how to with windows, find another box and try it there. Good luck. anon4321 wrote: > > I am using 9.04 also. As far as I can remember, there isn't anything you > need to do to get the FTDI chip to be recognized. > > > strangewanderer wrote: >> >> I am using 9.04. I have always been using the sudo command. I tried the >> root but it did not work either. Do you have any idea what that change >> would be. I have been looking through the synaptic package manager for >> something about and I have added a lot of packages but with no change. >> > > -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24748706.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: strangewanderer <str...@gm...> - 2009-07-31 02:25:19
|
I am pretty sure it is not a space issue on the linux machine. I got an "older" (probably only 4 years) computer and reformatted that and it is my linux machine. Linux is the only thing on there. Would it be better for me to use and older version of Ubuntu or another version of linux? I figure, while I am still new I might as well go for what would be best. The board must be defective. I plugged the thing into all of the ports on both of my computers as well as all of the computers in the lab with no connections being made. The green LED always turns on though. I will contact gumstix tomorrow. Thank you for all of your help. I really appreciate it. -- View this message in context: http://www.nabble.com/Issues-all-around-tp24699359p24749962.html Sent from the Gumstix mailing list archive at Nabble.com. |