RE: [linux-usb] Close to a solution. Please help !

linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed

* RE: [linux-usb] Close to a solution. Please help !
@ 2000-04-24 15:22 Dunlap, Randy
  2000-04-24 21:53 ` Daniel Gonzalez
  0 siblings, 1 reply; 10+ messages in thread
From: Dunlap, Randy @ 2000-04-24 15:22 UTC (permalink / raw)
  To: 'Daniel Gonzalez', Matthew Dharm
  Cc: Sheldon Easterbrook, linuxppc-dev, linux-usb

Hi Daniel,

Please send us your linux/.config file.

> Well. The sources I have are taken from linuxcare (I think that is Paul's
tree,
> isn't?). I am using the devel tree, since I heard that was performing
better for the
> USB subsystem.

and from kernel messages:

> Apr 24 13:58:26 dhcp-213-224-12-204 kernel: Linux version 2.3.99-pre6
(root@dhcp-213-224-12-204.kabel.pandora.be) (gcc version 2.95.2 19991024
(release)) #5 Mon Apr 24 13:25:37 EDT 2000

> Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usb-ohci: Warning! Gobs of
> debugging output has been enabled.
> Apr 24 13:51:11 dhcp-213-224-12-204 kernel:           Check your
kern.debug
> logs for the bulk of it.
> Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usbcore: Registered new driver
mouse
> Apr 24 13:51:11 dhcp-213-224-12-204 kernel: USB HID boot protocol mouse
> driver registered.
> Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usbcore: Registered new driver
keyboard
> Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usbcore: Registered new driver
hub
> Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usbcore: Registered new driver
usb_scsi
> Apr 24 13:51:11 dhcp-213-224-12-204 kernel: USB SCSI support registered.

I'm still confused about what version of the kernel code this is.

The Linux boot message says 2.3.99-pre6, but the USB code is clearly
MUCH earlier than that.
Could you explain a little of how you came by this code?
I don't want the complete history, just enough to help us
understand what you are trying to use here.

Thanks,
Randy
___________________________________________________
|Randy Dunlap     Intel Corp., DAL    Sr. SW Engr.|
|randy.dunlap.at.intel.com            503-696-2055|
|NOTE:  Any views presented here are mine alone   |
|and may not represent the views of my employer.  |
|_________________________________________________|

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [linux-usb] Close to a solution. Please help !
  2000-04-24 15:22 [linux-usb] Close to a solution. Please help ! Dunlap, Randy
@ 2000-04-24 21:53 ` Daniel Gonzalez
  0 siblings, 0 replies; 10+ messages in thread
From: Daniel Gonzalez @ 2000-04-24 21:53 UTC (permalink / raw)
  To: Dunlap, Randy; +Cc: Matthew Dharm, Sheldon Easterbrook, linuxppc-dev, linux-usb

[-- Attachment #1: Type: text/plain, Size: 3030 bytes --]

"Dunlap, Randy" wrote:

> Hi Daniel,
>
> Please send us your linux/.config file.
>

There it goes. Please be aware that the system I have right nor is slightly
different than the
one I had this morning. I have recompiled everything and selected the 'compile
as module'
option for most of the stuff. The behaviour is the same, though.

>
> > Well. The sources I have are taken from linuxcare (I think that is Paul's
> tree,
> > isn't?). I am using the devel tree, since I heard that was performing
> better for the
> > USB subsystem.
>
> and from kernel messages:
>
> > Apr 24 13:58:26 dhcp-213-224-12-204 kernel: Linux version 2.3.99-pre6
> (root@dhcp-213-224-12-204.kabel.pandora.be) (gcc version 2.95.2 19991024
> (release)) #5 Mon Apr 24 13:25:37 EDT 2000
>
> > Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usb-ohci: Warning! Gobs of
> > debugging output has been enabled.
> > Apr 24 13:51:11 dhcp-213-224-12-204 kernel:           Check your
> kern.debug
> > logs for the bulk of it.
> > Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usbcore: Registered new driver
> mouse
> > Apr 24 13:51:11 dhcp-213-224-12-204 kernel: USB HID boot protocol mouse
> > driver registered.
> > Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usbcore: Registered new driver
> keyboard
> > Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usbcore: Registered new driver
> hub
> > Apr 24 13:51:11 dhcp-213-224-12-204 kernel: usbcore: Registered new driver
> usb_scsi
> > Apr 24 13:51:11 dhcp-213-224-12-204 kernel: USB SCSI support registered.
>
> I'm still confused about what version of the kernel code this is.
>
> The Linux boot message says 2.3.99-pre6, but the USB code is clearly
> MUCH earlier than that.
> Could you explain a little of how you came by this code?
> I don't want the complete history, just enough to help us
> understand what you are trying to use here.
>

I am using a development tree targeted for the PowerPC community. I suppose
this code
is periodically merged with the main linux tree, but I do not know how they put
together
the sources. Maybe I should use the main linux tree ?

The usb sources are:

[root@dhcp-213-224-12-204 usb]# grep \$Id /usr/src/linux/drivers/usb/*
2>/dev/nul
/usr/src/linux/drivers/usb/dabusb.c: *  $Id: dabusb.c,v 1.45 2000/01/31
10:23:44 fliegl Exp $
/usr/src/linux/drivers/usb/devices.c: * $Id: devices.c,v 1.5 2000/01/11
13:58:21 tom Exp $
/usr/src/linux/drivers/usb/devio.c: *  $Id: devio.c,v 1.7 2000/02/01 17:28:48
fliegl Exp $
/usr/src/linux/drivers/usb/drivers.c: * $Id: drivers.c,v 1.3 2000/01/11
13:58:24 tom Exp $
/usr/src/linux/drivers/usb/inode.c: *  $Id: inode.c,v 1.3 2000/01/11 13:58:25
tom Exp $
/usr/src/linux/drivers/usb/plusb.c: *  $Id: plusb.c,v 1.18 2000/02/14 10:38:58
fliegl Exp $
/usr/src/linux/drivers/usb/usb-uhci.c: * $Id: usb-uhci.c,v 1.228 2000/04/02
19:55:51 acher Exp $
/usr/src/linux/drivers/usb/usb-uhci.h:   $Id: usb-uhci.h,v 1.54 2000/04/02
19:55:53 acher Exp $
/usr/src/linux/drivers/usb/usb.c: * $Id: usb.c,v 1.53 2000/01/14 16:19:09 acher
Exp $

Regards,

Daniel


[-- Attachment #2: config --]
[-- Type: text/plain, Size: 16257 bytes --]

#
# Automatically generated by make menuconfig: don't edit
#
# CONFIG_UID16 is not set

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Platform support
#
CONFIG_PPC=y
CONFIG_6xx=y
# CONFIG_4xx is not set
# CONFIG_PPC64 is not set
# CONFIG_82xx is not set
# CONFIG_8xx is not set
CONFIG_ALL_PPC=y
# CONFIG_GEMINI is not set
# CONFIG_APUS is not set
# CONFIG_SMP is not set
CONFIG_ALTIVEC=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# General setup
#
# CONFIG_ISA is not set
# CONFIG_SBUS is not set
CONFIG_PCI=y
CONFIG_NET=y
CONFIG_SYSCTL=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_KCORE_ELF=y
CONFIG_BINFMT_ELF=y
CONFIG_KERNEL_ELF=y
# CONFIG_BINFMT_MISC is not set
# CONFIG_PCI_NAMES is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set
CONFIG_VGA_CONSOLE=y
CONFIG_FB=y
CONFIG_FB_COMPAT_XPMAC=y
CONFIG_PMAC_PBOOK=y
# CONFIG_MAC_FLOPPY is not set
CONFIG_MAC_SERIAL=y
# CONFIG_SERIAL_CONSOLE is not set
CONFIG_ADB=y
CONFIG_ADB_CUDA=y
CONFIG_ADB_MACIO=y
CONFIG_ADB_PMU=y
CONFIG_ADB_KEYBOARD=y
CONFIG_ADBMOUSE=y
CONFIG_PROC_DEVICETREE=y
CONFIG_BOOTX_TEXT=y
# CONFIG_MOTOROLA_HOTSWAP is not set
# CONFIG_CMDLINE_BOOL is not set

#
# Plug and Play configuration
#
# CONFIG_PNP is not set
# CONFIG_ISAPNP is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_LVM is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_STRIPED is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
CONFIG_NETLINK=y
# CONFIG_RTNETLINK is not set
# CONFIG_NETLINK_DEV is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_IP_ROUTER is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
CONFIG_IP_ALIAS=y
CONFIG_SYN_COOKIES=y
CONFIG_SKB_LARGE=y
# CONFIG_IPV6 is not set
# CONFIG_KHTTPD is not set
# CONFIG_ATM is not set
# CONFIG_IPX is not set
CONFIG_ATALK=m
# CONFIG_DECNET is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_BRIDGE is not set
# CONFIG_LLC is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# ATA/IDE/MFM/RLL support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
# CONFIG_IDEDISK_MULTI_MODE is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
CONFIG_BLK_DEV_IDESCSI=y
# CONFIG_BLK_DEV_CMD640 is not set
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_IDEPCI_SHARE_IRQ is not set
# CONFIG_BLK_DEV_IDEDMA_PCI is not set
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_IDEDMA_PCI_AUTO is not set
# CONFIG_BLK_DEV_IDEDMA is not set
CONFIG_IDEDMA_PCI_EXPERIMENTAL=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD7409 is not set
# CONFIG_AMD7409_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_CMD64X_RAID is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_HPT366_FIP is not set
# CONFIG_HPT366_MODE3 is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_PDC202XX_MASTER is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_VIA82CXXX_TUNING is not set
# CONFIG_BLK_DEV_SL82C105 is not set
CONFIG_BLK_DEV_IDE_PMAC=y
CONFIG_BLK_DEV_IDEDMA_PMAC=y
CONFIG_IDEDMA_PMAC_AUTO=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
CONFIG_BLK_DEV_IDE_MODES=y

#
# SCSI support
#
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_SD_EXTRA_DEVS=40
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_BLK_DEV_SR_VENDOR=y
CONFIG_SR_EXTRA_DEVS=2
CONFIG_CHR_DEV_SG=y
# CONFIG_SCSI_DEBUG_QUEUES is not set
# CONFIG_SCSI_MULTI_LUN is not set
CONFIG_SCSI_CONSTANTS=y
# CONFIG_SCSI_LOGGING is not set

#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_7000FASST is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AHA152X is not set
# CONFIG_SCSI_AHA1542 is not set
# CONFIG_SCSI_AHA1740 is not set
CONFIG_SCSI_AIC7XXX=y
# CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT is not set
CONFIG_AIC7XXX_CMDS_PER_DEVICE=8
CONFIG_AIC7XXX_PROC_STATS=y
CONFIG_AIC7XXX_RESET_DELAY=15
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_SCSI_IN2000 is not set
# CONFIG_SCSI_AM53C974 is not set
# CONFIG_SCSI_MEGARAID is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_DTC3280 is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_DMA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_GENERIC_NCR5380 is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_NCR53C406A is not set
# CONFIG_SCSI_SYM53C416 is not set
# CONFIG_SCSI_SIM710 is not set
# CONFIG_SCSI_NCR53C7xx is not set
# CONFIG_SCSI_NCR53C8XX is not set
CONFIG_SCSI_SYM53C8XX=y
CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
CONFIG_SCSI_NCR53C8XX_SYNC=20
# CONFIG_SCSI_NCR53C8XX_PROFILE is not set
# CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
# CONFIG_SCSI_NCR53C8XX_PQS_PDS is not set
# CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
# CONFIG_SCSI_PAS16 is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_PSI240I is not set
# CONFIG_SCSI_QLOGIC_FAS is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_T128 is not set
# CONFIG_SCSI_U14_34F is not set
# CONFIG_SCSI_DEBUG is not set
CONFIG_SCSI_MESH=y
CONFIG_SCSI_MESH_SYNC_RATE=5
CONFIG_SCSI_MAC53C94=y

#
# IEEE 1394 (FireWire) support
#
# CONFIG_IEEE1394 is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set

#
# Appletalk devices
#
# CONFIG_APPLETALK is not set
# CONFIG_DUMMY is not set
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_ETHERTAP is not set
# CONFIG_NET_SB1000 is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MACE=y
CONFIG_BMAC=y
CONFIG_GMAC=y
# CONFIG_NCR885E is not set
# CONFIG_OAKNET is not set
# CONFIG_NET_VENDOR_3COM is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_NET_ISA is not set
CONFIG_NET_PCI=y
CONFIG_PCNET32=y
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_AC3200 is not set
# CONFIG_APRICOT is not set
# CONFIG_CS89x0 is not set
CONFIG_DE4X5=y
# CONFIG_TULIP is not set
# CONFIG_DGRS is not set
# CONFIG_DM9102 is not set
# CONFIG_EEPRO100 is not set
# CONFIG_LNE390 is not set
# CONFIG_NE3210 is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_RTL8129 is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
# CONFIG_ES3210 is not set
# CONFIG_EPIC100 is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_YELLOWFIN is not set
# CONFIG_ACENIC is not set
# CONFIG_SK98LIN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
CONFIG_PPP=y
# CONFIG_PPP_MULTILINK is not set
# CONFIG_PPP_ASYNC is not set
# CONFIG_PPP_SYNC_TTY is not set
# CONFIG_PPP_DEFLATE is not set
# CONFIG_PPP_BSDCOMP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Console drivers
#

#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FB_RIVA is not set
# CONFIG_FB_CLGEN is not set
# CONFIG_FB_PM2 is not set
CONFIG_FB_OF=y
CONFIG_FB_CONTROL=y
CONFIG_FB_PLATINUM=y
CONFIG_FB_VALKYRIE=y
CONFIG_FB_IMSTT=y
CONFIG_FB_CT65550=y
# CONFIG_FB_S3TRIO is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_MATROX=y
CONFIG_FB_MATROX_MILLENIUM=y
CONFIG_FB_MATROX_MYSTIQUE=y
CONFIG_FB_MATROX_G100=y
# CONFIG_FB_MATROX_MULTIHEAD is not set
CONFIG_FB_ATY=y
CONFIG_FB_ATY128=y
CONFIG_FB_3DFX=y
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FBCON_ADVANCED is not set
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
# CONFIG_FBCON_FONTWIDTH8_ONLY is not set
CONFIG_FBCON_FONTS=y
# CONFIG_FONT_8x8 is not set
CONFIG_FONT_8x16=y
CONFIG_FONT_SUN8x16=y
CONFIG_FONT_SUN12x22=y
# CONFIG_FONT_6x11 is not set
# CONFIG_FONT_PEARL_8x8 is not set
# CONFIG_FONT_ACORN_8x8 is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SERIAL=m
# CONFIG_SERIAL_EXTENDED is not set
# CONFIG_SERIAL_NONSTANDARD is not set
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
CONFIG_BUSMOUSE=y
# CONFIG_ATIXL_BUSMOUSE is not set
# CONFIG_LOGIBUSMOUSE is not set
# CONFIG_MS_BUSMOUSE is not set
CONFIG_ADBMOUSE=y
CONFIG_MOUSE=y
CONFIG_PSMOUSE=y
# CONFIG_82C710_MOUSE is not set
# CONFIG_PC110_PAD is not set

#
# Joysticks
#
# CONFIG_JOYSTICK is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_NVRAM=y
# CONFIG_RTC is not set

#
# Video For Linux
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_DRM is not set
# CONFIG_DRM_TDFX is not set
# CONFIG_AGP is not set

#
# File systems
#
# CONFIG_QUOTA is not set
CONFIG_AUTOFS_FS=y
# CONFIG_AUTOFS4_FS is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
CONFIG_HFS_FS=y
# CONFIG_BFS_FS is not set
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=y
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_RAMFS is not set
CONFIG_ISO9660_FS=y
# CONFIG_JOLIET is not set
# CONFIG_MINIX_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_SYSV_FS_WRITE is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_ROOT_NFS is not set
CONFIG_NFSD=y
# CONFIG_NFSD_V3 is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_MOUNT_SUBDIR is not set
# CONFIG_NCPFS_NDS_DOMAINS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set

#
# Partition Types
#
CONFIG_PARTITION_ADVANCED=y
# CONFIG_ACORN_PARTITION is not set
# CONFIG_OSF_PARTITION is not set
# CONFIG_AMIGA_PARTITION is not set
# CONFIG_ATARI_PARTITION is not set
CONFIG_MAC_PARTITION=y
CONFIG_MSDOS_PARTITION=y
# CONFIG_BSD_DISKLABEL is not set
# CONFIG_SOLARIS_X86_PARTITION is not set
# CONFIG_UNIXWARE_DISKLABEL is not set
# CONFIG_SGI_PARTITION is not set
# CONFIG_SUN_PARTITION is not set
CONFIG_NLS=y

#
# Native Language Support
#
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set

#
# Sound
#
CONFIG_SOUND=y
CONFIG_DMASOUND_AWACS=y
CONFIG_DMASOUND=y
# CONFIG_SOUND_CMPCI is not set
# CONFIG_SOUND_ES1370 is not set
# CONFIG_SOUND_ES1371 is not set
# CONFIG_SOUND_ESSSOLO1 is not set
# CONFIG_SOUND_MAESTRO is not set
# CONFIG_SOUND_SONICVIBES is not set
# CONFIG_SOUND_TRIDENT is not set
# CONFIG_SOUND_MSNDCLAS is not set
# CONFIG_SOUND_MSNDPIN is not set
CONFIG_SOUND_OSS=y
# CONFIG_SOUND_TRACEINIT is not set
# CONFIG_SOUND_DMAP is not set
# CONFIG_SOUND_AD1816 is not set
# CONFIG_SOUND_SGALAXY is not set
# CONFIG_SOUND_ADLIB is not set
# CONFIG_SOUND_ACI_MIXER is not set
CONFIG_SOUND_CS4232=m
# CONFIG_SOUND_SSCAPE is not set
# CONFIG_SOUND_GUS is not set
# CONFIG_SOUND_ICH is not set
# CONFIG_SOUND_VMIDI is not set
# CONFIG_SOUND_TRIX is not set
# CONFIG_SOUND_MSS is not set
# CONFIG_SOUND_MPU401 is not set
# CONFIG_SOUND_NM256 is not set
# CONFIG_SOUND_MAD16 is not set
# CONFIG_SOUND_PAS is not set
# CONFIG_PAS_JOYSTICK is not set
# CONFIG_SOUND_PSS is not set
# CONFIG_SOUND_SOFTOSS is not set
# CONFIG_SOUND_SB is not set
# CONFIG_SOUND_AWE32_SYNTH is not set
# CONFIG_SOUND_WAVEFRONT is not set
# CONFIG_SOUND_MAUI is not set
# CONFIG_SOUND_VIA82CXXX is not set
# CONFIG_SOUND_YM3812 is not set
# CONFIG_SOUND_OPL3SA1 is not set
# CONFIG_SOUND_OPL3SA2 is not set
# CONFIG_SOUND_UART6850 is not set
# CONFIG_SOUND_AEDSP16 is not set

#
# USB support
#
CONFIG_USB=m
CONFIG_USB_DEBUG=y
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_UHCI is not set
# CONFIG_USB_UHCI_ALT is not set
CONFIG_USB_OHCI=m
# CONFIG_USB_PRINTER is not set
# CONFIG_USB_SCANNER is not set
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_ACM is not set
# CONFIG_USB_SERIAL is not set
# CONFIG_USB_IBMCAM is not set
# CONFIG_USB_OV511 is not set
# CONFIG_USB_DC2XX is not set
# CONFIG_USB_MDC800 is not set
CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DEBUG=y
# CONFIG_USB_USS720 is not set
# CONFIG_USB_DABUSB is not set
# CONFIG_USB_PLUSB is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_DSBR is not set
CONFIG_USB_HID=m
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_WMFORCE is not set
CONFIG_INPUT_KEYBDEV=m
CONFIG_INPUT_MOUSEDEV=m
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_EVDEV is not set

#
# Kernel hacking
#
CONFIG_MAGIC_SYSRQ=y
# CONFIG_KGDB is not set
CONFIG_XMON=y

^ permalink raw reply	[flat|nested] 10+ messages in thread

* RE: [linux-usb] Close to a solution. Please help !
@ 2000-04-24 16:06 Dunlap, Randy
  2000-04-24 22:29 ` Daniel Gonzalez
  0 siblings, 1 reply; 10+ messages in thread
From: Dunlap, Randy @ 2000-04-24 16:06 UTC (permalink / raw)
  To: 'Daniel Gonzalez'; +Cc: Matthew Dharm, linuxppc-dev, linux-usb


Hi Daniel,

I don't see anything that is obviously wrong in the
linux/.config file.

The recent advice from Joseph Fannin looks good.
Have you tried it?  (except change:
  alias char-major-8 sd_mod
to
  alias block-major-8 sd_mod
)

Give us a list of modules that are loaded when you connect
the Zip drive.

Switching to the main linux tree is likely just to give
you/us a different set of problems, but I'm just guessing
that based on Brad Hards's comments.

For USB source file comparisons, all of my 2.3.99-pre6-5
unzipped .c files are dated between Mar. 10 and Apr. 21, 2000.
None from the Jan.-Feb. timeframe as you listed.
There have been beaucoups changes in this time, especially
to the usb-storage driver.

~Randy


> -----Original Message-----
> From: Daniel Gonzalez [mailto:daniel.gonzalez@pandora.be]
> Sent: Monday, April 24, 2000 2:54 PM
> To: Dunlap, Randy
> Cc: Matthew Dharm; Sheldon Easterbrook;
> linuxppc-dev@lists.linuxppc.org;
> linux-usb@suse.com
> Subject: Re: [linux-usb] Close to a solution. Please help !
>
> > > Well. The sources I have are taken from linuxcare (I
> think that is Paul's tree,
> > > isn't?). I am using the devel tree, since I heard that
> was performing better for the USB subsystem.
> >
> >
> > I'm still confused about what version of the kernel code this is.
> >
> > The Linux boot message says 2.3.99-pre6, but the USB code is clearly
> > MUCH earlier than that.
> > Could you explain a little of how you came by this code?
> > I don't want the complete history, just enough to help us
> > understand what you are trying to use here.
> >
>
> I am using a development tree targeted for the PowerPC
> community. I suppose this code
> is periodically merged with the main linux tree, but I do not
> know how they put together
> the sources. Maybe I should use the main linux tree ?
>
> The usb sources are:
>
> [root@dhcp-213-224-12-204 usb]# grep \$Id /usr/src/linux/drivers/usb/*
> 2>/dev/nul
> /usr/src/linux/drivers/usb/dabusb.c: *  $Id: dabusb.c,v 1.45
> 2000/01/31
> 10:23:44 fliegl Exp $
> /usr/src/linux/drivers/usb/devices.c: * $Id: devices.c,v 1.5
> 2000/01/11
> 13:58:21 tom Exp $
> /usr/src/linux/drivers/usb/devio.c: *  $Id: devio.c,v 1.7
> 2000/02/01 17:28:48
> fliegl Exp $
> /usr/src/linux/drivers/usb/drivers.c: * $Id: drivers.c,v 1.3
> 2000/01/11
> 13:58:24 tom Exp $
> /usr/src/linux/drivers/usb/inode.c: *  $Id: inode.c,v 1.3
> 2000/01/11 13:58:25
> tom Exp $
> /usr/src/linux/drivers/usb/plusb.c: *  $Id: plusb.c,v 1.18
> 2000/02/14 10:38:58
> fliegl Exp $
> /usr/src/linux/drivers/usb/usb-uhci.c: * $Id: usb-uhci.c,v
> 1.228 2000/04/02
> 19:55:51 acher Exp $
> /usr/src/linux/drivers/usb/usb-uhci.h:   $Id: usb-uhci.h,v
> 1.54 2000/04/02
> 19:55:53 acher Exp $
> /usr/src/linux/drivers/usb/usb.c: * $Id: usb.c,v 1.53
> 2000/01/14 16:19:09 acher
> Exp $


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [linux-usb] Close to a solution. Please help !
  2000-04-24 16:06 Dunlap, Randy
@ 2000-04-24 22:29 ` Daniel Gonzalez
  0 siblings, 0 replies; 10+ messages in thread
From: Daniel Gonzalez @ 2000-04-24 22:29 UTC (permalink / raw)
  To: Dunlap, Randy; +Cc: Matthew Dharm, linuxppc-dev, linux-usb


Hi Randy,

Strange enough my /etc/conf.modules is empty. No wonder that the modules
are not automatically loaded ( I have to do it by hand )Any idea of what
should
I do to recreate that file ?

BTW, no sd_mod module present in my system ...


"Dunlap, Randy" wrote:

> Hi Daniel,
>
> I don't see anything that is obviously wrong in the
> linux/.config file.
>
> The recent advice from Joseph Fannin looks good.
> Have you tried it?  (except change:
>   alias char-major-8 sd_mod
> to
>   alias block-major-8 sd_mod
> )
>
> Give us a list of modules that are loaded when you connect
> the Zip drive.
>
> Switching to the main linux tree is likely just to give
> you/us a different set of problems, but I'm just guessing
> that based on Brad Hards's comments.
>
> For USB source file comparisons, all of my 2.3.99-pre6-5
> unzipped .c files are dated between Mar. 10 and Apr. 21, 2000.
> None from the Jan.-Feb. timeframe as you listed.
> There have been beaucoups changes in this time, especially
> to the usb-storage driver.
>
> ~Randy
>
> > -----Original Message-----
> > From: Daniel Gonzalez [mailto:daniel.gonzalez@pandora.be]
> > Sent: Monday, April 24, 2000 2:54 PM
> > To: Dunlap, Randy
> > Cc: Matthew Dharm; Sheldon Easterbrook;
> > linuxppc-dev@lists.linuxppc.org;
> > linux-usb@suse.com
> > Subject: Re: [linux-usb] Close to a solution. Please help !
> >
> > > > Well. The sources I have are taken from linuxcare (I
> > think that is Paul's tree,
> > > > isn't?). I am using the devel tree, since I heard that
> > was performing better for the USB subsystem.
> > >
> > >
> > > I'm still confused about what version of the kernel code this is.
> > >
> > > The Linux boot message says 2.3.99-pre6, but the USB code is clearly
> > > MUCH earlier than that.
> > > Could you explain a little of how you came by this code?
> > > I don't want the complete history, just enough to help us
> > > understand what you are trying to use here.
> > >
> >
> > I am using a development tree targeted for the PowerPC
> > community. I suppose this code
> > is periodically merged with the main linux tree, but I do not
> > know how they put together
> > the sources. Maybe I should use the main linux tree ?
> >
> > The usb sources are:
> >
> > [root@dhcp-213-224-12-204 usb]# grep \$Id /usr/src/linux/drivers/usb/*
> > 2>/dev/nul
> > /usr/src/linux/drivers/usb/dabusb.c: *  $Id: dabusb.c,v 1.45
> > 2000/01/31
> > 10:23:44 fliegl Exp $
> > /usr/src/linux/drivers/usb/devices.c: * $Id: devices.c,v 1.5
> > 2000/01/11
> > 13:58:21 tom Exp $
> > /usr/src/linux/drivers/usb/devio.c: *  $Id: devio.c,v 1.7
> > 2000/02/01 17:28:48
> > fliegl Exp $
> > /usr/src/linux/drivers/usb/drivers.c: * $Id: drivers.c,v 1.3
> > 2000/01/11
> > 13:58:24 tom Exp $
> > /usr/src/linux/drivers/usb/inode.c: *  $Id: inode.c,v 1.3
> > 2000/01/11 13:58:25
> > tom Exp $
> > /usr/src/linux/drivers/usb/plusb.c: *  $Id: plusb.c,v 1.18
> > 2000/02/14 10:38:58
> > fliegl Exp $
> > /usr/src/linux/drivers/usb/usb-uhci.c: * $Id: usb-uhci.c,v
> > 1.228 2000/04/02
> > 19:55:51 acher Exp $
> > /usr/src/linux/drivers/usb/usb-uhci.h:   $Id: usb-uhci.h,v
> > 1.54 2000/04/02
> > 19:55:53 acher Exp $
> > /usr/src/linux/drivers/usb/usb.c: * $Id: usb.c,v 1.53
> > 2000/01/14 16:19:09 acher
> > Exp $

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 10+ messages in thread

* RE: [linux-usb] Close to a solution. Please help !
@ 2000-04-24 16:21 Ian Blenke
  0 siblings, 0 replies; 10+ messages in thread
From: Ian Blenke @ 2000-04-24 16:21 UTC (permalink / raw)
  To: 'Daniel Gonzalez', Dunlap, Randy
  Cc: Matthew Dharm, linuxppc-dev, linux-usb

If you *really* want a fully loaded conf.modules (aka modules.conf), try
"modprobe -c".

 - Ian

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 10+ messages in thread

[parent not found: <20000424010537.73861.qmail@hotmail.com>]

[parent not found: <39048829.EA283A23@pandora.be>]

[parent not found: <390490A9.2D8EB962@pandora.be>]

* Re: [linux-usb] Close to a solution. Please help !
       [not found]   ` <390490A9.2D8EB962@pandora.be>
@ 2000-04-24 12:17     ` Matthew Dharm
  2000-04-24 20:15       ` Daniel Gonzalez
  2000-04-24 23:34     ` Brad Hards
  1 sibling, 1 reply; 10+ messages in thread
From: Matthew Dharm @ 2000-04-24 12:17 UTC (permalink / raw)
  To: Daniel Gonzalez; +Cc: Sheldon Easterbrook, linuxppc-dev, linux-usb

On Mon, 24 Apr 2000, Daniel Gonzalez wrote:

> THE DESCRIPTION:
> I have the following /etc/fstab entry for the Zip
>
> /dev/sdb4  /mnt/usbzip  auto noauto,user 0 0
>
> I have also tried with sda4.

Do you have support for SCSI disks available (either compiled in or as a
module)?

> THE GOOD SIGNS
> [root scsi]# cat /proc/scsi/usb-storage-0/2
> Host scsi2: usb-storage
>     Vendor: Iomega
>    Product: USB Zip 250
>   Protocol: Bulk only
>  Transport: Transparent SCSI
>       GUID: 059b0030059b003003005fc1

This is a very good sign.  It shows that the driver has identified the
device, and attempted to communicate that information to the SCSI layer.

> [root scsi]# cat /proc/filesystems

This isn't needed for debugging.

> THE BAD SIGNS
> [root scsi]# cat /proc/scsi/scsi
> Attached devices: none

Hrm... so the SCSI layer probed for the device, but didn't find
anything....

> This after I have issued a:
> [root scsi]# echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi

This command isn't really needed anymore.  Generally, when you attach a
device, it will appear immediately.

> But it could be that the creation of /proc/scsi/usb-storage-0/2 was caused
> by that last command. I did not pay attention to that.

No, it wasn't.  usb-storage-0/2 is created by connecting the device.

What you need to do now is set syslogd to save kern.* to a logfile, and
then attach the device and load all the drivers, and send me the logfile.
You also need to enable USB Mass Storage debugging.

I'm suspecting that this is an endian-ness problem.  I should be able to
identify that relatively quickly once you send me the logfile.

Matt Dharm

--
Matthew Dharm                              Home: mdharm@one-eyed-alien.net
Senior Engineer, QCP Inc.                        Work: mdharm@qualcomm.com

DP: And judging from the scores, Stef has the sma...
T:  LET'S NOT GO THERE!
					-- Dust Puppy and Tanya
User Friendly, 12/11/1997

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [linux-usb] Close to a solution. Please help !
  2000-04-24 12:17     ` Matthew Dharm
@ 2000-04-24 20:15       ` Daniel Gonzalez
  2000-04-25  5:50         ` Matthew Dharm
  0 siblings, 1 reply; 10+ messages in thread
From: Daniel Gonzalez @ 2000-04-24 20:15 UTC (permalink / raw)
  To: Matthew Dharm; +Cc: Sheldon Easterbrook, linuxppc-dev, linux-usb

[-- Attachment #1: Type: text/plain, Size: 2736 bytes --]

Hi Matt,


Matthew Dharm wrote:

> On Mon, 24 Apr 2000, Daniel Gonzalez wrote:
>
> > THE DESCRIPTION:
> > I have the following /etc/fstab entry for the Zip
> >
> > /dev/sdb4  /mnt/usbzip  auto noauto,user 0 0
> >
> > I have also tried with sda4.
>
> Do you have support for SCSI disks available (either compiled in or as a
> module)?
>

Yes. I have done everything I considered necessary to enable SCSI (my machine
has a real SCSI interface also, though I do not use it)

>
> > THE GOOD SIGNS
> > [root scsi]# cat /proc/scsi/usb-storage-0/2
> > Host scsi2: usb-storage
> >     Vendor: Iomega
> >    Product: USB Zip 250
> >   Protocol: Bulk only
> >  Transport: Transparent SCSI
> >       GUID: 059b0030059b003003005fc1
>
> This is a very good sign.  It shows that the driver has identified the
> device, and attempted to communicate that information to the SCSI layer.
>
> > [root scsi]# cat /proc/filesystems
>
> This isn't needed for debugging.
>
> > THE BAD SIGNS
> > [root scsi]# cat /proc/scsi/scsi
> > Attached devices: none
>
> Hrm... so the SCSI layer probed for the device, but didn't find
> anything....
>
> > This after I have issued a:
> > [root scsi]# echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi
>
> This command isn't really needed anymore.  Generally, when you attach a
> device, it will appear immediately.
>
> > But it could be that the creation of /proc/scsi/usb-storage-0/2 was caused
> > by that last command. I did not pay attention to that.
>
> No, it wasn't.  usb-storage-0/2 is created by connecting the device.
>
> What you need to do now is set syslogd to save kern.* to a logfile, and
> then attach the device and load all the drivers, and send me the logfile.
> You also need to enable USB Mass Storage debugging.
>

Done. Find the log attached.
The activity which the logs includes is:
- connecting the Zip drive to a USB port.
- loading manually the usb-storage module (insmod)
- disconnecting and connectingthe Zip.


>
> I'm suspecting that this is an endian-ness problem.  I should be able to
> identify that relatively quickly once you send me the logfile.
>

Thanks for your interest. I am not familiar with the USB specification, and
also
not with the linux usb code. Are you the mantainer of that subsystem?

BTW, I have sent half an hour ago another message regarding this problem.
Most of the information is duplicated, though.



>
> Matt Dharm
>
> --
> Matthew Dharm                              Home: mdharm@one-eyed-alien.net
> Senior Engineer, QCP Inc.                        Work: mdharm@qualcomm.com
>
> DP: And judging from the scores, Stef has the sma...
> T:  LET'S NOT GO THERE!
>                                         -- Dust Puppy and Tanya
> User Friendly, 12/11/1997

[-- Attachment #2: kern --]
[-- Type: text/plain, Size: 15375 bytes --]

Apr 24 16:03:07 dhcp-213-224-12-204 kernel: hub.c: port 2 connection change
Apr 24 16:03:07 dhcp-213-224-12-204 kernel: hub.c: portstatus 100, change 3, High Speed
Apr 24 16:03:07 dhcp-213-224-12-204 kernel: usb.c: USB disconnect on device 2
Apr 24 16:03:07 dhcp-213-224-12-204 kernel: hub.c: port 2 enable change, status 100
Apr 24 16:03:08 dhcp-213-224-12-204 kernel: hub.c: port 1 connection change
Apr 24 16:03:08 dhcp-213-224-12-204 kernel: hub.c: portstatus 101, change 1, High Speed
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: hub.c: portstatus 103, change 10, High Speed
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: usb.c: USB new device connect, assigned device number 2
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: usb.c: kmalloc IF c2189d60, numif 1
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: usb.c: new device strings: Mfr=1, Product=2, SerialNumber=5
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: usb.c: USB device number 2 default language ID 0x409
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: Manufacturer: Iomega
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: Product: USB Zip 250
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: SerialNumber: 059B003003005FC1
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: usb.c: unhandled interfaces on device
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: usb.c: This device is not recognized by any installed USB driver.
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   Length              = 18
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   DescriptorType      = 01
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   USB version         = 1.10
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   Vendor:Product      = 059b:0030
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   MaxPacketSize0      = 64
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   NumConfigurations   = 1
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   Device version      = 1.00
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   Device Class:SubClass:Protocol = 00:00:00
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     Per-interface classes
Apr 24 16:03:09 dhcp-213-224-12-204 kernel: Configuration:
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   bLength             =    9
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   bDescriptorType     =   02
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   wTotalLength        = 0027
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   bNumInterfaces      =   01
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   bConfigurationValue =   01
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   iConfiguration      =   03
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   bmAttributes        =   c0
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   MaxPower            =    0mA
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   Interface: 0
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:   Alternate Setting:  0
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     bLength             =    9
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     bDescriptorType     =   04
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     bInterfaceNumber    =   00
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     bAlternateSetting   =   00
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     bNumEndpoints       =   03
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     bInterface Class:SubClass:Protocol =   08:06:50
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     iInterface          =   04
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     Endpoint:
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bLength             =    7
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bDescriptorType     =   05
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bEndpointAddress    =   01 (out)
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bmAttributes        =   02 (Bulk)
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       wMaxPacketSize      = 0040
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bInterval           =   00
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     Endpoint:
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bLength             =    7
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bDescriptorType     =   05
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bEndpointAddress    =   82 (in)
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bmAttributes        =   02 (Bulk)
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       wMaxPacketSize      = 0040
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bInterval           =   00
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:     Endpoint:
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bLength             =    7
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bDescriptorType     =   05
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bEndpointAddress    =   83 (in)
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bmAttributes        =   03 (Interrupt)
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       wMaxPacketSize      = 0002
Apr 24 16:03:09 dhcp-213-224-12-204 kernel:       bInterval           =   20
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb.c: registered new driver usb-storage
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: USB Mass Storage device detected
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Endpoints In 2 Out 1 Int 3
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Result from usb_set_interface is 0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: New GUID 059b0030059b003003005fc1
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Transport: Bulk
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Protocol: Transparent SCSI
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: scsi2 : SCSI emulation for USB Mass Storage devices
Apr 24 16:04:30 dhcp-213-224-12-204 kernel:
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: scsi : 3 hosts.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Command TEST_UNIT_READY (6 bytes)
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage:   00 00 00 00 00 00 00 0d c2 7d
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command S 0x43425355 T 0x15 LUN 0 L 0 F 0 CL 6
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command transfer result=0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0010280
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: -- transport indicates transport failure
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: scsi cmd done, result=0x70000
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Command TEST_UNIT_READY (6 bytes)
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage:   00 00 00 00 00 00 00 0d c2 7d
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command S 0x43425355 T 0x16 LUN 0 L 0 F 0 CL 6
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command transfer result=-32
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0008200
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0010280
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: -- transport indicates transport failure
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: scsi cmd done, result=0x70000
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Command TEST_UNIT_READY (6 bytes)
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage:   00 00 00 00 00 00 00 0d c2 7d
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command S 0x43425355 T 0x17 LUN 0 L 0 F 0 CL 6
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command transfer result=-32
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0008200
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0010280
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: -- transport indicates transport failure
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: scsi cmd done, result=0x70000
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Command TEST_UNIT_READY (6 bytes)
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage:   00 00 00 00 00 00 00 0d c2 7d
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command S 0x43425355 T 0x18 LUN 0 L 0 F 0 CL 6
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command transfer result=-32
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0008200
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0010280
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: -- transport indicates transport failure
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: scsi cmd done, result=0x70000
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Command TEST_UNIT_READY (6 bytes)
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage:   00 00 00 00 00 00 00 0d c2 7d
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command S 0x43425355 T 0x19 LUN 0 L 0 F 0 CL 6
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bulk command transfer result=-32
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0008200
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: clearing endpoint halt for pipe 0xc0010280
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: -- transport indicates transport failure
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: scsi cmd done, result=0x70000
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bad device number (1/0) or dev 0xc3640ea0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bad device number (2/0) or dev 0xc3640ea0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bad device number (3/0) or dev 0xc3640ea0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bad device number (4/0) or dev 0xc3640ea0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bad device number (5/0) or dev 0xc3640ea0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bad device number (6/0) or dev 0xc3640ea0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: us_queuecommand() called
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread awakened.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: Bad device number (7/0) or dev 0xc3640ea0
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb-storage: *** thread sleeping.
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: WARNING: USB Mass Storage data integrity not assured
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: USB Mass Storage device found at 2
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: usb.c: usb-storage driver claimed interface c2189d60
Apr 24 16:04:30 dhcp-213-224-12-204 kernel: USB Mass Storage support registered.
Apr 24 16:08:04 dhcp-213-224-12-204 kernel: hub.c: port 1 connection change
Apr 24 16:08:05 dhcp-213-224-12-204 kernel: hub.c: portstatus 100, change 3, High Speed
Apr 24 16:08:05 dhcp-213-224-12-204 kernel: usb.c: USB disconnect on device 2
Apr 24 16:08:05 dhcp-213-224-12-204 kernel: usb-storage: storage_disconnect() called
Apr 24 16:08:05 dhcp-213-224-12-204 kernel: hub.c: port 1 enable change, status 100
Apr 24 16:08:06 dhcp-213-224-12-204 kernel: hub.c: port 1 connection change
Apr 24 16:08:06 dhcp-213-224-12-204 kernel: hub.c: portstatus 101, change 1, High Speed
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: hub.c: portstatus 103, change 10, High Speed
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb.c: USB new device connect, assigned device number 2
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb.c: kmalloc IF c21892e0, numif 1
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb.c: new device strings: Mfr=1, Product=2, SerialNumber=5
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb.c: USB device number 2 default language ID 0x409
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: Manufacturer: Iomega
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: Product: USB Zip 250
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: SerialNumber: 059B003003005FC1
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb-storage: USB Mass Storage device detected
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb-storage: Endpoints In 2 Out 1 Int 3
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb-storage: Result from usb_set_interface is 0
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb-storage: Found existing GUID 059b0030059b003003005fc1
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: WARNING: USB Mass Storage data integrity not assured
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: USB Mass Storage device found at 2
Apr 24 16:08:07 dhcp-213-224-12-204 kernel: usb.c: usb-storage driver claimed interface c21892e0

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [linux-usb] Close to a solution. Please help !
  2000-04-24 20:15       ` Daniel Gonzalez
@ 2000-04-25  5:50         ` Matthew Dharm
  0 siblings, 0 replies; 10+ messages in thread
From: Matthew Dharm @ 2000-04-25  5:50 UTC (permalink / raw)
  To: Daniel Gonzalez; +Cc: Sheldon Easterbrook, linuxppc-dev, linux-usb


This is a definate endian-ness problem.  I just tested a fix on a bronze
powerbook (lumbard) and it seems to work.

The fix will be in the next patch I send, tho that may be a while as I'm
converting the entire driver to URBs to allow proper handling of timeouts.

Matt

On Mon, 24 Apr 2000, Daniel Gonzalez wrote:

> Matthew Dharm wrote:
>
> > On Mon, 24 Apr 2000, Daniel Gonzalez wrote:
> >
> > > THE DESCRIPTION:
> > > I have the following /etc/fstab entry for the Zip
> > >
> > > /dev/sdb4  /mnt/usbzip  auto noauto,user 0 0
> > >
> > > I have also tried with sda4.
> >
> > Do you have support for SCSI disks available (either compiled in or as a
> > module)?
> >
>
> Yes. I have done everything I considered necessary to enable SCSI (my machine
> has a real SCSI interface also, though I do not use it)
>
> >
> > > THE GOOD SIGNS
> > > [root scsi]# cat /proc/scsi/usb-storage-0/2
> > > Host scsi2: usb-storage
> > >     Vendor: Iomega
> > >    Product: USB Zip 250
> > >   Protocol: Bulk only
> > >  Transport: Transparent SCSI
> > >       GUID: 059b0030059b003003005fc1
> >
> > This is a very good sign.  It shows that the driver has identified the
> > device, and attempted to communicate that information to the SCSI layer.
> >
> > > [root scsi]# cat /proc/filesystems
> >
> > This isn't needed for debugging.
> >
> > > THE BAD SIGNS
> > > [root scsi]# cat /proc/scsi/scsi
> > > Attached devices: none
> >
> > Hrm... so the SCSI layer probed for the device, but didn't find
> > anything....
> >
> > > This after I have issued a:
> > > [root scsi]# echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi
> >
> > This command isn't really needed anymore.  Generally, when you attach a
> > device, it will appear immediately.
> >
> > > But it could be that the creation of /proc/scsi/usb-storage-0/2 was caused
> > > by that last command. I did not pay attention to that.
> >
> > No, it wasn't.  usb-storage-0/2 is created by connecting the device.
> >
> > What you need to do now is set syslogd to save kern.* to a logfile, and
> > then attach the device and load all the drivers, and send me the logfile.
> > You also need to enable USB Mass Storage debugging.
> >
>
> Done. Find the log attached.
> The activity which the logs includes is:
> - connecting the Zip drive to a USB port.
> - loading manually the usb-storage module (insmod)
> - disconnecting and connectingthe Zip.
>
>
> >
> > I'm suspecting that this is an endian-ness problem.  I should be able to
> > identify that relatively quickly once you send me the logfile.
> >
>
> Thanks for your interest. I am not familiar with the USB specification, and
> also
> not with the linux usb code. Are you the mantainer of that subsystem?
>
> BTW, I have sent half an hour ago another message regarding this problem.
> Most of the information is duplicated, though.

--
Matthew Dharm                              Home: mdharm@one-eyed-alien.net
Senior Engineer, QCP Inc.                        Work: mdharm@qualcomm.com

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [linux-usb] Close to a solution. Please help !
       [not found]   ` <390490A9.2D8EB962@pandora.be>
  2000-04-24 12:17     ` Matthew Dharm
@ 2000-04-24 23:34     ` Brad Hards
  2000-04-24 12:43       ` Matthew Dharm
  1 sibling, 1 reply; 10+ messages in thread
From: Brad Hards @ 2000-04-24 23:34 UTC (permalink / raw)
  To: Daniel Gonzalez; +Cc: Sheldon Easterbrook, linuxppc-dev, linux-usb


Daniel Gonzalez wrote:
> After a very long week, I think I am close to actually access my 250 Usb Zip drive.
> I have now 2.3.99-pre6.
You should feel priviliged. It took me months on and off to think I
might be close.
I do have some bad news though - you probably should have stayed with
Paulus' tree,
since Matt did think that there was some endian bugs, and I am pretty
sure
Paul had at least a floppy disk working.

> THE PROBLEM: I am not able to mount my Zip drive:
>
> [root scsi]# mount /mnt/usbzip/
> mount: /dev/sdb4 has wrong major or minor number
weird

> THE DESCRIPTION:
> I have the following /etc/fstab entry for the Zip
>
> /dev/sdb4  /mnt/usbzip  auto noauto,user 0 0
>
> I have also tried with sda4.
Which should be the right device - this Powerbook is IDE, right? No SCSI
attached? Then it should be on /dev/sda. But maybe /dev/sda1 if it is
HFS disk? What does fdisk show as the partitions?

> How do I get the major and minor numbers for a given device?
>
> THE GOOD SIGNS
> [root scsi]# cat /proc/scsi/usb-storage-0/2
> Host scsi2: usb-storage
>     Vendor: Iomega
>    Product: USB Zip 250
>   Protocol: Bulk only
>  Transport: Transparent SCSI
>       GUID: 059b0030059b003003005fc1
Looks good, although mine shows up slightly differently:
bradh@isp651:~ > more /proc/scsi/usb-storage-0/0
Host scsi0: usb-storage
    Vendor: Iomega
   Product: USB Zip 100
  Protocol: Bulk only
 Transport: Transparent SCSI
      GUID: 059b00010000000000f41dea


> BTW, what is shm ?
SysV shared memory. You need to mount it on /var/shm

> THE BAD SIGNS
> [root scsi]# cat /proc/scsi/scsi
> Attached devices: none
This is definately not so good.

> This after I have issued a:
> [root scsi]# echo "scsi add-single-device 1 0 0 0" > /proc/scsi/scsi
I don't need to do this any more. Do you get anything without it?

> But it could be that the creation of /proc/scsi/usb-storage-0/2 was caused
> by that last command. I did not pay attention to that.
>
> What should I do know ?
This is showing up correctly in /proc/bus/usb/devices and
/proc/bus/usb/drivers, right? The drive shows up and the usb-storage
driver is associated with it?
Any more kernel debug messages?

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: [linux-usb] Close to a solution. Please help !
  2000-04-24 23:34     ` Brad Hards
@ 2000-04-24 12:43       ` Matthew Dharm
  0 siblings, 0 replies; 10+ messages in thread
From: Matthew Dharm @ 2000-04-24 12:43 UTC (permalink / raw)
  To: Brad Hards; +Cc: Daniel Gonzalez, Sheldon Easterbrook, linuxppc-dev, linux-usb


On Mon, 24 Apr 2000, Brad Hards wrote:

> Daniel Gonzalez wrote:
> > After a very long week, I think I am close to actually access my 250 Usb Zip drive.
> > I have now 2.3.99-pre6.
> You should feel priviliged. It took me months on and off to think I
> might be close.
> I do have some bad news though - you probably should have stayed with
> Paulus' tree,
> since Matt did think that there was some endian bugs, and I am pretty
> sure
> Paul had at least a floppy disk working.

Unfortunately, floppies work through completely different code paths than
Zips do.

Once I have the logs, I should be able to fix this.

Matt Dharm

--
Matthew Dharm                              Home: mdharm@one-eyed-alien.net
Senior Engineer, QCP Inc.                        Work: mdharm@qualcomm.com

I could always suspend a few hundred accounts and watch what happens.
					-- Tanya
User Friendly, 7/31/1998


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2000-04-25  5:50 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-04-24 15:22 [linux-usb] Close to a solution. Please help ! Dunlap, Randy
2000-04-24 21:53 ` Daniel Gonzalez
  -- strict thread matches above, loose matches on Subject: below --
2000-04-24 16:06 Dunlap, Randy
2000-04-24 22:29 ` Daniel Gonzalez
2000-04-24 16:21 Ian Blenke
     [not found] <20000424010537.73861.qmail@hotmail.com>
     [not found] ` <39048829.EA283A23@pandora.be>
     [not found]   ` <390490A9.2D8EB962@pandora.be>
2000-04-24 12:17     ` Matthew Dharm
2000-04-24 20:15       ` Daniel Gonzalez
2000-04-25  5:50         ` Matthew Dharm
2000-04-24 23:34     ` Brad Hards
2000-04-24 12:43       ` Matthew Dharm

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).