![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| BSD BSD, sometimes called Berkeley Unix, is a Unix operating system developed by the Computer Systems Research Group of the UC Berkeley. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| How to copy my system hdd usb stick from 4GB to 8GB ? | jack2 | UNIX for Dummies Questions & Answers | 7 | 04-03-2009 08:42 AM |
| Aix usb stick | BEVAN | UNIX for Dummies Questions & Answers | 2 | 08-21-2008 06:21 AM |
| Fedora on a stick | iBot | UNIX and Linux RSS News | 0 | 08-05-2008 11:10 AM |
| crontab does not stick | lulle | SUN Solaris | 4 | 02-21-2008 01:13 AM |
| Stick with Solaris 10 or try something else? | Filth Pig | UNIX for Dummies Questions & Answers | 5 | 08-23-2005 02:51 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
Detecting usb stick in freebsd
I inserted a 8GB usb stick in a number of machine with FreeBSD 7.1, but the medium was not detected:
Code:
$ dmesg | grep MB usable memory = 4263022592 (4065 MB) avail memory = 4082540544 (3893 MB) pci0: <serial bus, SMBus> at device 31.3 (no driver attached) ad0: 238475MB <WDC WD2500BEVT-00ZCT0 11.01A11> at ata2-master SATA300 da0: 40.000MB/s transfers cd0: 3.300MB/s transfers usable memory = 4280356864 (4082 MB) avail memory = 4099862528 (3909 MB) pci0: <serial bus, SMBus> at device 31.3 (no driver attached) ad0: 238475MB <WDC WD2500BEVT-00ZCT0 11.01A11> at ata2-master SATA300 cd0: 3.300MB/s transfers da0: 40.000MB/s transfers usable memory = 4280356864 (4082 MB) avail memory = 4099862528 (3909 MB) pci0: <serial bus, SMBus> at device 31.3 (no driver attached) ad0: 238475MB <WDC WD2500BEVT-00ZCT0 11.01A11> at ata2-master SATA300 cd0: 3.300MB/s transfers da0: 40.000MB/s transfers |
|
||||
|
Overheating is a concern indeed, since frying data is not always an option. Is there a way to protect oneself against overheating? Checking with another usb stick, the problem seems to have disappeared.
The more pertinent problem has been why the da0s1/da1s1 etc slices were not available, even when logged in as root? |
|
||||
|
Code:
# dmesg | grep usb usb0: OHCI version 1.0, legacy support usb0: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci0 usb0: USB revision 1.0 uhub0: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 usb1: OHCI version 1.0, legacy support usb1: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci1 usb1: USB revision 1.0 uhub1: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 usb2: OHCI version 1.0, legacy support usb2: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci2 usb2: USB revision 1.0 uhub2: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: <ALi M5239 USB 2.0 controller> on ehci0 usb3: USB revision 2.0 uhub3: <AcerLabs EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3 usb0: OHCI version 1.0, legacy support usb0: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci0 usb0: USB revision 1.0 uhub0: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0 usb1: OHCI version 1.0, legacy support usb1: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci1 usb1: USB revision 1.0 uhub1: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1 usb2: OHCI version 1.0, legacy support usb2: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci2 usb2: USB revision 1.0 uhub2: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2 usb3: EHCI version 1.0 usb3: companion controllers, 3 ports each: usb0 usb1 usb2 usb3: <ALi M5239 USB 2.0 controller> on ehci0 usb3: USB revision 2.0 uhub3: <AcerLabs EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3 |
|
||||
|
I have tried several machines and since the overheating problem was confined to only one stick, it seems that the problem was in the stick to begin with. The slice I am connecting alternative sticks to is /dev/da1s1
|
| Sponsored Links | ||
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|