On Mon, Jun 04, 2012 at 06:58:07AM +0200, Wojciech Puchar wrote:
#
# 2. Replace the vendor installed NTFS with a UFS file system.
#
#$ newfs -U /dev/da1s1
#
#(No, I didn't bother to create BSD partitions)
#
# but why still create msdos partition?
I didn't create one, I just left it
I solved it. No kernel or other driver installations necessary
beyond those I already had (xhci).
1. Hook up disk to USB 2 Port.
- System detects drive and creates device nodes:
ugen3.2: Jmicron Corp. at usbus3
umass1: MSC Bulk-Only Transfer on usbus3
da1 at umass-sim1 bus 1
2. Replace the vendor installed NTFS with a UFS file system.
$ newfs -U /dev/da1s1
(No, I didn't bother to create BSD partitions)
but why still create msdos partition?
___
freebsd-questions@freebsd.org mailing list
On Thu, May 31, 2012 at 08:26:21PM +0200, Damien Fleuriot wrote:
...
# When I plug it to one of the two USB3.0 ports (using the xhci driver), I
# don't get device nodes in /dev created for it, but instead an ever
# growing list of
#
# ugen4.2: Jmicron Corp. at usbus4
# umass2: Jmicron
# mount -t ntfs -o ro /dev/da5s1 /mnt
mount_ntfs: /dev/da5s1: Invalid argument
)
your dmesg shows drive is properly detected.
seems like ntfs driver doesn't work OR MBR is't properly handled.
___
freebsd-questions@freebsd.org mailing list
On Thu, May 31, 2012 at 06:14:08PM -0400, Thomas Mueller wrote:
...
# I think you also need xhci driver in kernel config. xhci is for USB 3.0.
It's there. As I said, using a USB 3 *Stick* works fine. It is recogized as 3.0
and the speed is as expected. It's the *Disk* that is not recognized.
I have recompiled the kernel with device ada and put ahci_load=YES in
/boot/loader.conf.
you don't need ada driver for USB disk. anyway you need it for your SATA
disk to make things fast.
and mounting it works. Obviously, for the disk the device nodes aren't
created...
Is there something
Hi Wojciech et al,
On Fri, Jun 01, 2012 at 10:42:53AM +0200, Wojciech Puchar wrote:
# # mount -t ntfs -o ro /dev/da5s1 /mnt
# mount_ntfs: /dev/da5s1: Invalid argument
# )
# your dmesg shows drive is properly detected.
Yes, but this was only on a USB2 (two) port, and just an auxiliary
On 06/01/12 04:01, Jens Schweikhardt wrote:
My goal is to get it recognized on one of the two USB3 ports I have.
All I get there is
Jun 1 11:43:45 hal9000 kernel: ugen4.2:Jmicron Corp. at usbus4
Jun 1 11:43:45 hal9000 kernel: umass0:Jmicron Corp. Usb production, class
0/0, rev 3.00/1.00,
hello, world\n
so I decided to try two HW technology advancements in one go.
I have a brand new shiny 1TB USB3.0 external disk, that when plugged
to an USB2(two!) reports
da5 at umass-sim2 bus 2 scbus6 target 0 lun 0
da5: ST1000LM 024 HN-M101MBB Fixed Direct Access SCSI-2 device
On 31 May 2012, at 17:57, Jens Schweikhardt schwe...@schweikhardt.net wrote:
hello, world\n
so I decided to try two HW technology advancements in one go.
I have a brand new shiny 1TB USB3.0 external disk, that when plugged
to an USB2(two!) reports
da5 at umass-sim2 bus 2 scbus6
On 05/31/12 09:57, Jens Schweikhardt wrote:
so I decided to try two HW technology advancements in one go.
I have a brand new shiny 1TB USB3.0 external disk, that when plugged
to an USB2(two!) reports
da5 at umass-sim2 bus 2 scbus6 target 0 lun 0
da5:ST1000LM 024 HN-M101MBB
On 05/31/12 09:57, Jens Schweikhardt wrote:
so I decided to try two HW technology advancements in one go.
I have a brand new shiny 1TB USB3.0 external disk, that when plugged
to an USB2(two!) reports
da5 at umass-sim2 bus 2 scbus6 target 0 lun 0
da5:ST1000LM 024 HN-M101MBB
On Thu, 31 May 2012, Jens Schweikhardt wrote:
so I decided to try two HW technology advancements in one go.
I have a brand new shiny 1TB USB3.0 external disk, that when plugged
to an USB2(two!) reports
da5 at umass-sim2 bus 2 scbus6 target 0 lun 0
da5: ST1000LM 024 HN-M101MBB Fixed
14 matches
Mail list logo
