In dmesg repeats the old conclusion that I wrote, but in dmesg I found
information about five usbus and all except the last one (it has 2.0) written
usb 1.0. I tried to connect the hdd to last, but failed. Also about usbus
written that they are 2-port hub (probably built into the motherboard). In the
first four usbus is intel UHCI root HUB, at the last - intel EHCI root HUB
"ls / dev / da *" finds nothing
"camcontrol devlist" outputs only DVD RW
My hdd has an input for an external power supply, and it is already connected
to a second usb port.
07.07.2013, 00:37, "Polytropon" <free...@edvax.de>:
> Your research is correct so far.
>
> On Sun, 07 Jul 2013 00:18:11 +0400, Nazar Kazakov wrote:
>> I found on Google about bsdinstall segfault without disks.
>> Then I reboot computer, disconnected the hdd and connected
>> it immediately after starting bsdinstall, that's what I brought:
>>
>> usb_alloc_device: set address 2 failed (USB_ERR_STALLED, ignored)
>> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
>> USB_ERR_STALLED
>> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_STALLED,
>> ignored)
>> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
>> USB_ERR_STALLED
>> usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_STALLED,
>> ignored)
>> usbd_setup_device_desc: getting device descriptor at addr 2 failed,
>> USB_ERR_STALLED
>> ugen1.2: <Unknown> at usbus1 (disconnected)
>> uhub_reattach_port: could not allocate new device
> It should not matter when the disk is attached; bsdinstall
> will operate on any disk recognized by the system, no matter
> if detected at program runtime or system boot.
>> As I understand it, my external hdd is not mounted.
> The disk is not _recognized_. Only a file system can be
> mounted (which requires the disk to be recognized). For
> a USB disk, from the /dev/ugenX.Y device a /dev/daX device
> will be "generated", corresponding to the disk. The process
> you've shown above does not even reach that step.
>
> If you go to the shell, you can enter "dmesg" to see the
> last messages that will be the same. You can also check
> the content of /dev regarding daX devices ("ls /dev/da*")
> or use "camcontrol devlist" to check if they are present.
>> Maybe it's because I have a hdd with usb 3.0, but my computer
>> does not have usb 3.0.
> Yes, this looks like a typical "cannot connect" error.
> Normally, a USB 3 disk would "switch down" to USB 2.
> But USB 3 has a different current requirement, so it
> could be possible that the power drain from the USB port
> is insufficient for the disk to work properly. Can you
> try to attach a separate power supply to the disk?
> For USB 3, _all_ involved parts (disk, cable, ports,
> controller, OS) need to be in "USB 3 mode", else it
> probably won't work.
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
