Showing posts with label USB. Show all posts
Showing posts with label USB. Show all posts

Monday, 27 October 2008

USB Mouse on Acer Aspire One

I recently tested the functionality of a USB mouse attached to my Acer Aspire One (AA1). I attached a Microsoft Optical Mouse Blue USB and PS/2 Compatible mouse and started the AA1 without issue. Both the left and right mouse buttons worked as did the scroll wheel and center mouse mouse button (scroll wheel).

The output from from dmesg is:


ALC INIT<6>usbcore: registered new interface driver hiddev
input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input8
input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:1d.0-2



Unplugging the mouse and reattaching while the AA1 is running again was no problem and produces a dmesg output of:



usb 2-2: USB disconnect, address 2
usb 2-2: new low speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 1 choice
input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/input/input9
input: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:1d.0-2

Sunday, 19 October 2008

Transfer files between a Blackberry Curve 8310 and an Acer Aspire One

It is easy to transfer files (e.g. photos) between a Blackberry Curve 8310 and an Acer Aspire One (AA1).

First a few background details: The AA1 comes with 5 usb ports (according to the dmesg output).



$ dmesg | grep 'new USB'
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5



When plugging the Blackberry into one of those USB ports, two events happen; one on the AA1 and the other on the Blackberry.



$ dmesg
...
scsi 4:0:0:0: Direct-Access RIM BlackBerry SD 0001 PQ: 0 ANSI: 4 CCS
sd 4:0:0:0: [sdb] Attached SCSI removable disk
sd 4:0:0:0: Attached scsi generic sg1 type 0
sd 4:0:0:0: [sdb] 3994624 512-byte hardware sectors (2045 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 53
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] 3994624 512-byte hardware sectors (2045 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 53
sd 4:0:0:0: [sdb] Assuming drive cache: write through



The Blackberry warns:

USB charging current is not sufficient. Verify that your handheld is connecting to a powered USB charging source and that the proper USB driver is installed.


acknowledging that message, one is presented with:


Do you want to turn on Mass Storage Mode? You might not be able to access some media files in this mode.


Then one is presented with the option:


Mass Storage Mode is being activated. Enter your device password to grant access:













Finally after acknowledging the warnings and supplying the Blackberry password access to the USB storage on the Blackberry is available. It then can be treated like all other storage devices.


Monday, 13 October 2008

PC-BSD on a USB memory stick

My goal was simple: create a bootable USB memory stick and copy the install image of PC-BSD onto the USB memory stick.

This was achieved w/o much trouble using my FreeBSD server at work. I performed the following operations logged in as root.

The USB image was downloaded from the PC-BSD website


Assumption: the USB memory stick is plugged into the server at /dev/da0

# fdisk -BI /dev/da0
# bsdlabel -w -B /dev/da0s1
# newfs /dev/da0
# dd if=/usr/home/kengell/PCBSD7-x86-USB.img of=/dev/da0 bs=1m