I decided to remove the Addonics USB 3.0 to esata adaptor out of the loop to see if that is causing the problem. I installed one of my HD's in a single USB 3.0 external enclosure and connected it to see if this new kernel 3.0 rc2, recognizes and mounts the drive. As of now, it still doesn't connect and nothing is appearing in /media/usb. Here are excerpts from dmesg and lsusb: lsusb Bus 010 Device 002: ID 152d:2509 JMicron Technology Corp. / JMicron USA Technology Corp. Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 002: ID 1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI) Bus 001 Device 003: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub xhci_hcd error message from dmesg Jun 15 10:30:38 xbmclive64 kernel: [ 1812.358012] xhci_hcd 0000:03:00.0: WARN: Stalled endpoint Please let me know if there are any other logs / info you need. thanks, Steve sginn@xxxxxxx On Jun 13, 2011, at 4:30 PM, M. Steven Ginn wrote: > when I connect via esata and then boot, the system locks up because I believe all the /dev/sd* drives get mixed up even though I haven't mounted any of the JBOD drives. > > But, if I shut off the the raid tower, boot up and then turn on the raid, all the hard drive lights are green and I can see the drives in GParted. So the system can see the drives via esata (as long as I turn things on in the right order) but it can't seem them via the Addonics usb 3.0 to esata connection. According to Addonics, the drives should just appear like multiple usb drive connections. > > > > Steve > sginn@xxxxxxx > > > <wr.jpg> > On Jun 13, 2011, at 1:14 PM, M. Steven Ginn wrote: > >> ok I've gotten my video working again with the new kernel and my 4 HD's connected in my raid tower (JBOD config) via the Addonics USB 3.0 to esata are not being mounted. Looking in the media mount point, none of the usb mount points have anything mounted. >> >> any next steps or config files I need to check? Should I print out any log files? >> >> thanks, >> >> Steve >> sginn@xxxxxxx >> >> >> >> >> On Jun 12, 2011, at 3:10 PM, Sid Boyce wrote: >> >>> I have used both NVIDIA-Linux-x86_64-275.09 and NVIDIA-Linux-x86_64-275.09.04 with these changes from 3.0-rc1, so they are good. >>> # uname -r >>> 3.0.0-rc2-git7-smp >>> # cat /proc/driver/nvidia/version >>> NVRM version: NVIDIA UNIX x86_64 Kernel Module 275.09.04 Thu Jun 2 12:51:38 PDT 2011 >>> GCC version: gcc version 4.6.0 20110607 [gcc-4_6-branch revision 174741] (SUSE Linux) >>> Regards >>> Sid. >>> >>> On 12/06/11 20:50, M. Steven Ginn wrote: >>>> Thank you, I'll try it when I get home >>>> >>>> Do you recommend I use the latest beta drivers or can I use the stable one >>>> >>>> >>>> Sent from my iPhone >>>> >>>> On Jun 12, 2011, at 2:45 PM, Sid Boyce <sboyce@xxxxxxxxxxxxxxxx> wrote: >>>> >>>>> On 12/06/11 19:03, M. Steven Ginn wrote: >>>>>> is the only way to fix the problem by running this new kernel? >>>>>> >>>>>> I can't seem to get my video working again with this new one … >>>>>> >>>>>> >>>>>> Steve >>>>>> >>>>>> sginn@xxxxxxx >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Jun 12, 2011, at 12:21 PM, M. Steven Ginn wrote: >>>>>> >>>>>> >>>>>>> well I just updated to 3.0 rc2 and for some reason my Nvidia drivers did not update as well and now Grub seems unable to find my previous kernel 2.6.38 >>>>>>> >>>>>>> so, I guess I have to figure out how to now update the Nvidia drivers for the new kernel to be able to boot. Not sure if I have to use a different Nvidia driver for this new kernel >>>>>>> >>>>>>> >>>>>>> I know this is not your problem … I will let you know if / when I can get rc2 working >>>>>>> >>>>>>> Steve >>>>>>> >>>>>>> sginn@xxxxxxx >>>>>>> >>>>>>> >>>>>>> >>>>>>> <wr.jpg> >>>>>>> On Jun 12, 2011, at 11:15 AM, Greg KH wrote: >>>>>>> >>>>>>> >>>>>>>> On Sun, Jun 12, 2011 at 11:07:33AM -0500, M. Steven Ginn wrote: >>>>>>>> >>>>>>>>> Where do I get that kernel? >>>>>>>>> >>>>>>>> www.kernel.org >>>>>>>> >>>>>>>> -- >>>>>>>> To unsubscribe from this list: send the line "unsubscribe linux-usb" in >>>>>>>> the body of a message to >>>>>>>> majordomo@xxxxxxxxxxxxxxx >>>>>>>> >>>>>>>> More majordomo info at >>>>>>>> http://vger.kernel.org/majordomo-info.html >>>>> Two needed changes needed to the NVidia driver for 3.0 you can make by hand in the NVIDIA-Linux-*/kernel directory. The changes didn't make it into 275.09.04. >>>>> >>>>> conftest.sh script: >>>>> >>>>> @@ -76,7 +76,7 @@ >>>>> } >>>>> >>>>> build_cflags() { >>>>> - BASE_CFLAGS="-D__KERNEL__ \ >>>>> + BASE_CFLAGS="-O2 -D__KERNEL__ \ >>>>> -DKBUILD_BASENAME=\"#conftest$$\" -DKBUILD_MODNAME=\"#conftest$$\" \ >>>>> -nostdinc -isystem $ISYSTEM" >>>>> ----------------------------------------------------------------------------------------------------------- >>>>> nv-linux.h >>>>> - #elif LINUX_VERSION_CODE < KERNEL_VERSION(2, 7, 0) >>>>> + #elif LINUX_VERSION_CODE < KERNEL_VERSION(3, 1, 0) >>>>> >>>>> Regards >>>>> Sid. >>> >>> >>> -- >>> Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot >>> Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support >>> Senior Staff Specialist, Cricket Coach >>> Microsoft Windows Free Zone - Linux used for all Computing Tasks >>> >> >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-usb" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
