Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Mar 2005 01:16:12 -0500
From:      scion+fbsdq@webrelay.net
To:        freebsd-questions@freebsd.org
Subject:   reading fdisk partitioned drives &ct from Sparc64
Message-ID:  <20050325061612.F03512FC0F@arwen.webrelay.net>

next in thread | raw e-mail | index | archive | help
Greetings,

I'm trying to read data from a USB/Firewire drive.  The drive
was formatted on a WinXP system with an NTFS.

I'm having numerous difficulties, and am wondering if I should
just go and buy a cheap PC chassis before continuing.

Problem one:

Though (with usbd running) the kernel is aware of my USB card:

ohci0: <NEC uPD 9210 USB controller> mem 0x4000-0x4fff at device 3.0 on pci2
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0
usb0: <NEC uPD 9210 USB controller> on ohci0
usb0: USB revision 1.0
uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1: <NEC uPD 9210 USB controller> mem 0x6000-0x6fff at device 3.1 on pci2
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0
usb1: <NEC uPD 9210 USB controller> on ohci1
usb1: USB revision 1.0
uhub1: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
ehci0: <NEC uPD 720100 USB 2.0 controller> mem 0x8000-0x80ff at device 3.2 on pci2
ehci0: [GIANT-LOCKED]
ehci_pci_attach: companion usb0
ehci_pci_attach: companion usb1
usb2: EHCI version 0.95
usb2: companion controllers, 3 ports each: usb0 usb1
usb2: <NEC uPD 720100 USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: NEC EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub2: 5 ports with 5 removable, self powered
uhub2: device problem, disabling port 3

umass isn't firing up.  umass will load (manually), but is
not autoloaded, and no umass instance pops up in dmesg.

# kldstat
Id Refs Address            Size     Name
 1    5 0xc0000000 4923e8   kernel
 2    2 0xc0900000 140000   usb.ko
 3    1 0xc0a4a000 10a000   umass.ko
 4    1 0xc0b54000 10e000   ntfs.ko


So, yank the usb cable, and install the firewire.  This moves along...

fwohci0: BUS reset
fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
firewire0: bus manager 1 (me)
fwohci0: BUS reset
fwohci0: node_id=0xc800ffc1, gen=3, CYCLEMASTER mode
fwohci0: txd err= 0 No stat
firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me)
firewire0: bus manager 1 (me)
firewire0: New S400 device ID:0010b92100603efb
da0 at sbp0 bus 0 target 0 lun 0
da0: <Maxtor OneTouch II 030d> Fixed Direct Access SCSI-4 device 
da0: 50.000MB/s transfers
da0: 194481MB (398297088 512 byte sectors: 255H 63S/T 24792C)


Cool, so now I've a disk.  But that doesn't really help...

# ls /dev/da*
/dev/da0

Nothing that would look like something to mount.  And indeed,

# mount_ntfs -o ro /dev/da0 /mnt
mount_ntfs: /dev/da0: Invalid argument

Am I just barking up the wrong tree, here.  Does the endian issue
preclude the da driver from seeing fdisk-style partitions on Sparc64?

If not, what might help mount_ntfs see a device. Then again, do endian
issues preclude ntfs from operating on Sparc64?

And lastly, referring to all of those USB devices referenced at:
  http://www.freebsd.org/releases/5.3R/hardware-i386.html#USB
and their absence at:
  http://www.freebsd.org/releases/5.3R/hardware-sparc64.html#USB

Do they really not work on Sparc64, or just haven't been tested?


Cheers!
-sam





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050325061612.F03512FC0F>