Re: External Hard drive

From: Jeremy Faulkner (gldisater_at_gldis.ca)
Date: 11/02/04

  • Next message: Hugo Silva: "Re: Process states?"
    To: Lloyd Hayes <lloyd545220-trucker@yahoo.com>
    Date: Mon, 01 Nov 2004 22:10:34 +0000 clamav-milter version 0.80j on constans.gldis.ca
    
    
    

    On Tue, 2004-11-02 at 00:01, Lloyd Hayes wrote:
    > The information which you requested is at the bottom. dmesg, fstab, and
    > rc.conf.
    > While the 'dmesg' refers to a printer, I haven't hooked one up to this
    > system yet. I figured that I would deal with one problem at a time. So
    > far, none of the UNIX type systems has liked much of my equipment, and I
    > have a lot more to add to it....

    The "lpt0: <Printer> on ppbus0" is nothing to worry about, the system
    does *not* think you have a printer attached. It thinks you have a
    parallel port and created the associated printer port (in software).

     
    > But I attribute that to my own lack of
    > knowledge on UNIX type systems, and on networking in general.

    <snip>

    > FreeBSD seems to be very difficult for me to learn, but I also think
    > that it may be the way to go, too.

    The FreeBSD Handbook should be able to help with that.

    > uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0xfce0-0xfcff irq
    > 10 at device 7.2 on pci0
    > usb0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
    > usb0: USB revision 1.0
    > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
    > uhub0: 2 ports with 2 removable, self powered
    > uhub1: Genesys Logic USB Hub, class 9/0, rev 1.01/0.12, addr 2
    > uhub1: 4 ports with 4 removable, bus powered

    <snip>

    > ohci0: <NEC uPD 9210 USB controller> mem 0x88002000-0x88002fff irq 10 at
    > device 0.0 on cardbus1
    > usb1: OHCI version 1.0
    > GEOM: create disk ad0 dp=0xc2a55360
    > ad0: 6194MB <TOSHIBA MK6409MAV> [13424/15/63] at ata0-master UDMA33
    > acd0: CDROM <UJDA110> at ata1-master PIO4
    > usb1: <NEC uPD 9210 USB controller> on ohci0
    > usb1: USB revision 1.0
    > uhub2: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
    > uhub2: 3 ports with 3 removable, self powered
    > Mounting root from ufs:/dev/ad0s1a
    > cardbus1: Resource not specified in CIS: id=10, size=1000
    > ohci1: <NEC uPD 9210 USB controller> mem 0x88003000-0x88003fff irq 10 at
    > device 0.1 on cardbus1
    > usb2: OHCI version 1.0
    > usb2: <NEC uPD 9210 USB controller> on ohci1
    > usb2: USB revision 1.0
    > uhub3: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
    > uhub3: 2 ports with 2 removable, self powered
    > umass0: Buslink USB 2.0 Hard Drive, rev 2.00/11.00, addr 2

    Here is your hard drive.

    > cardbus1: Resource not specified in CIS: id=10, size=100
    > cardbus1: <serial bus, USB> at device 0.2 (no driver attached)
    > GEOM: create disk da0 dp=0xc2be6050
    > da0 at umass-sim0 bus 0 target 0 lun 0
    > da0: <SAMSUNG SV4002H QP10> Fixed Direct Access SCSI-0 device
    > da0: 1.000MB/s transfers
    > da0: 38204MB (78242976 512 byte sectors: 255H 63S/T 4870C)

    Here is the drive being created and to be accessible as a disk in the
    system.

    > umass1: Acer Labs USB 2.0 Storage Device, rev 2.00/1.03, addr 2

    Here is your cdrom.

    > GEOM: create disk cd0 dp=0xc2ae6600
    > cd0 at umass-sim1 bus 1 target 0 lun 0
    > cd0: < COMBO-52X16C 1.83> Removable CD-ROM SCSI-0 device
    > cd0: 1.000MB/s transfers
    > cd0: Attempt to query device size failed: NOT READY, Medium not present
    > - tray closed
    >

    Running usbdevs as root will show exactly what usb devices the system
    knows about (that are currently connected). You should expect to see a
    lot of usb hubs along with the hard drive and cdrom.

    > fstab:
    > # Device Mountpoint FStype Options Dump Pass#
    > /dev/ad0s1b none swap sw 0 0
    > /dev/ad0s1a / ufs rw 1 1
    > /dev/ad0s1e /tmp ufs rw 2 2
    > /dev/ad0s1f /usr ufs rw 2 2
    > /dev/ad0s1d /var ufs rw 2 2
    > /dev/cd0 /cdrom cd9660 ro,noauto 0 0
    > /dev/acd0 /cdrom1 cd9660 ro,noauto 0 0
    > /dev/da0 /usb0 msdos noauto 0 0

    The line for /dev/da0 should have ro,noauto or rw,noauto for the Options
    column.

    > # This file now contains just the overrides from /etc/defaults/rc.conf.
    > # Please make all changes to this file, not to /etc/defaults/rc.conf.
    > svr4_enable="YES"
    > linux_enable="YES"
    > ibcs2_enable="YES"
    > usbd_enable="YES"
    > lpd_enable="YES"
    > moused_enable="YES"
    > named_enable="YES"
    > apm_enable="YES"
    > exim_enable="YES"
    > sendmail_enable="NONE"
    > router_flags="-q"
    > router="/sbin/routed"
    > router_enable="YES"
    > rpcbind_enable="YES"
    > rpc_statd_enable="YES"
    > rpc_lockd_enable="YES"
    > sshd_enable="YES"
    > rwhod_enable="YES"
    > inetd_enable="YES"
    > ipv6_enable="YES"
    > start_vinum="yes"
    > hostname="traveler2.hayes.org"

    There are a lot of sysinstall generated comments that you don't need in
    your rc.conf file. Also, you have a lot of network server daemons
    running and no ip assignment in sight. A look back at your dmesg shows
    you don't have any network ports that were found by the system. Then
    again, you did say that you were testing the system, so I guess you're
    testing the configurations on the loop back device.

    -- 
    Jeremy Faulkner <gldisater@gldis.ca>
    
    



  • Next message: Hugo Silva: "Re: Process states?"

    Relevant Pages

    • Re: serial login to SBC
      ... One thing I've noticed on the FreeBSD dmesg is ... : sio0: port may not be enabled ... I enabled the first serial port in the BIOS, ... Can you post a dmesg? ...
      (freebsd-hackers)
    • Re: Serial Port Bug?
      ... port to turn on and off the transmitter in my radio. ... With a volt meter I find some pins have a constant -10.7 volts on ... Wanting a way to test the serial port I recalled minicom and after ... What I like to do with dmesg is #dmesg> dmesg.txt and then call - say ...
      (Fedora)
    • Re: Serial Port Bug?
      ... port to turn on and off the transmitter in my radio. ... I get nothing from dmesg | grep ttyS and I even tried ...
      (Fedora)
    • Re: dmesg not working on new system
      ... While the dmesg on my servers typically goes empty after awhile, I've never had any problem reviewing kernel output from a fresh boot using the dmesg command. ... (asking because busy network w/ lots of system messages seems to be what's flushing the buffer for me). ...
      (freebsd-questions)
    • Re: Inactive Network adapter DAVICOM 9102/A
      ... But now, if I use "Network", it becomes active ... family and should be supported by the dmfe module. ... Is there anything odd in dmesg about the card? ... Stock kernels from $DISTRO tend to have many more ...
      (comp.os.linux.misc)