Re: [arch] External USB devices

2007-01-25 Thread Manny Calavera
On Wed, Jan 24, 2007 at 08:26:31AM -0700, Derek Carlson wrote:
 I am experiencing some weirdness booting while an external USB storage 
 device is attached.  As background (and only because I hope it will give 
 a clue as to the exact software set), I am currently running from a 
 system that was installed from the Beta 0.8, base ISO.
 
 If I leave my external 200GB hard drive, attached through USB cable, 
 connected during the boot process, I get a number of errors during the 
 auto configuration process.  The log file reports this:
 
   snip 
 
 Jan 24 06:48:44 slacker1 usb 3-7: new high speed USB device using 
 ehci_hcd and address 4
 Jan 24 06:48:44 slacker1 usb 3-7: configuration #1 chosen from 1 choice
 Jan 24 06:48:44 slacker1 scsi5 : SCSI emulation for USB Mass Storage devices
 Jan 24 06:48:44 slacker1 usb-storage: device found at 4
 Jan 24 06:48:44 slacker1 usb-storage: waiting for device to settle 
 before scanning
 Jan 24 06:48:49 slacker1 usb 3-7: reset high speed USB device using 
 ehci_hcd and address 4
 Jan 24 06:48:49 slacker1 usb 3-7: device firmware changed
 Jan 24 06:48:49 slacker1 usb 3-7: USB disconnect, address 4
 Jan 24 06:48:49 slacker1 usb-storage: device scan complete
 Jan 24 06:48:49 slacker1 usb 3-7: new high speed USB device using 
 ehci_hcd and address 5
 Jan 24 06:48:50 slacker1 usb 3-7: device descriptor read/64, error -71
 Jan 24 06:48:56 slacker1 usb 3-7: device descriptor read/64, error -71
 Jan 24 06:48:56 slacker1 usb 3-7: new high speed USB device using 
 ehci_hcd and address 6
 Jan 24 06:48:57 slacker1 usb 3-7: device descriptor read/64, error -71
 Jan 24 06:49:02 slacker1 usb 3-7: device descriptor read/64, error -71
 Jan 24 06:49:02 slacker1 usb 3-7: new high speed USB device using 
 ehci_hcd and address 7
 Jan 24 06:49:08 slacker1 usb 3-7: device not accepting address 7, error -71
 Jan 24 06:49:08 slacker1 usb 3-7: new high speed USB device using 
 ehci_hcd and address 8
 Jan 24 06:49:08 slacker1 usb 3-7: device not accepting address 8, error -71
 
   snip 
 
  From there I can often times boot the system, but not necessarily or 
 always.  For example, one time my sound card was not discovered.  One 
 time I got a failure on a partition that was not being mounted and the 
 system halted.  Rebooting has solved these problems.
 
 If I can successfully boot and start gnome while the hard drive was 
 attached, the external drive will not show up as a mounted volume.   
 When I unplug and plug the external hard drive again, my USB mouse will 
 crap out, and only rebooting the computer will bring the mouse back again.
 
 If I leave *any* USB devices (flash drive for example) attached at boot 
 time, I'll get similar scenarios as above.
 
 If I remove all USB devices, save the mouse, the system will boot 
 correctly.  I can start gnome, and I can plug the external drive into 
 the USB port, and I can mount it through nautilus, but it will not auto 
 mount in spite of having HAL  daemon started,  and having installed 
 pmount and  (for some reason unknown to me but reported in a forum) 
 gnome-volume-manager.
 
 The last is a minor inconvenience, but the booting process being flaky 
 is a bit disconcerting.
 
 I've commented out the entries in fstab except for the /, home and swap 
 volumes.  pmount is installed.
 
 My main problem is booting and what has caused me difficulties is trying 
 to do is to get automount features to work again in gnome.  It works 
 fine on my other Arch partition which was installed a year ago or so, 
 currently upgraded to testing.  The old partition is booted with 
 earlymodules=piix.  I did not install legacy IDE support on the new 
 system.
 
 I am happy to post other information if someone has a clue as to what's 
 going on here.  I am unable to access this PC during the day, so I won't 
 be able to reply until tonight. 
 
 Your kind support would be appreciated.
 
 dViking
 
 ___
 arch mailing list
 arch@archlinux.org
 http://www.archlinux.org/mailman/listinfo/arch


I have not experienced your problem (as I have no reason to have any USB
peripherals connected during bootup), but have you tried possibly
booting with the Arch Kernel-fallback? Perhaps this may be a quick and
dirty fix to your problem.

Just a thought.

___
arch mailing list
arch@archlinux.org
http://www.archlinux.org/mailman/listinfo/arch


Re: [arch] External USB devices

2007-01-25 Thread Derek
On Thu, 2007-01-25 at 04:40 -0800, Manny Calavera wrote:
 On Wed, Jan 24, 2007 at 08:26:31AM -0700, Derek Carlson wrote:
  I am experiencing some weirdness booting while an external USB storage 
  device is attached.  As background (and only because I hope it will give 
  a clue as to the exact software set), I am currently running from a 
  system that was installed from the Beta 0.8, base ISO.
  
  If I leave my external 200GB hard drive, attached through USB cable, 
  connected during the boot process, I get a number of errors during the 
  auto configuration process.  The log file reports this:
  
snip 
  
  Jan 24 06:48:44 slacker1 usb 3-7: new high speed USB device using 
  ehci_hcd and address 4
  Jan 24 06:48:44 slacker1 usb 3-7: configuration #1 chosen from 1 choice
  Jan 24 06:48:44 slacker1 scsi5 : SCSI emulation for USB Mass Storage devices
  Jan 24 06:48:44 slacker1 usb-storage: device found at 4
  Jan 24 06:48:44 slacker1 usb-storage: waiting for device to settle 
  before scanning
  Jan 24 06:48:49 slacker1 usb 3-7: reset high speed USB device using 
  ehci_hcd and address 4
  Jan 24 06:48:49 slacker1 usb 3-7: device firmware changed
  Jan 24 06:48:49 slacker1 usb 3-7: USB disconnect, address 4
  Jan 24 06:48:49 slacker1 usb-storage: device scan complete
  Jan 24 06:48:49 slacker1 usb 3-7: new high speed USB device using 
  ehci_hcd and address 5
  Jan 24 06:48:50 slacker1 usb 3-7: device descriptor read/64, error -71
  Jan 24 06:48:56 slacker1 usb 3-7: device descriptor read/64, error -71
  Jan 24 06:48:56 slacker1 usb 3-7: new high speed USB device using 
  ehci_hcd and address 6
  Jan 24 06:48:57 slacker1 usb 3-7: device descriptor read/64, error -71
  Jan 24 06:49:02 slacker1 usb 3-7: device descriptor read/64, error -71
  Jan 24 06:49:02 slacker1 usb 3-7: new high speed USB device using 
  ehci_hcd and address 7
  Jan 24 06:49:08 slacker1 usb 3-7: device not accepting address 7, error -71
  Jan 24 06:49:08 slacker1 usb 3-7: new high speed USB device using 
  ehci_hcd and address 8
  Jan 24 06:49:08 slacker1 usb 3-7: device not accepting address 8, error -71
  
snip 
  
   From there I can often times boot the system, but not necessarily or 
  always.  For example, one time my sound card was not discovered.  One 
  time I got a failure on a partition that was not being mounted and the 
  system halted.  Rebooting has solved these problems.
  
  If I can successfully boot and start gnome while the hard drive was 
  attached, the external drive will not show up as a mounted volume.   
  When I unplug and plug the external hard drive again, my USB mouse will 
  crap out, and only rebooting the computer will bring the mouse back again.
  
  If I leave *any* USB devices (flash drive for example) attached at boot 
  time, I'll get similar scenarios as above.
  
  If I remove all USB devices, save the mouse, the system will boot 
  correctly.  I can start gnome, and I can plug the external drive into 
  the USB port, and I can mount it through nautilus, but it will not auto 
  mount in spite of having HAL  daemon started,  and having installed 
  pmount and  (for some reason unknown to me but reported in a forum) 
  gnome-volume-manager.
  
  The last is a minor inconvenience, but the booting process being flaky 
  is a bit disconcerting.
  
  I've commented out the entries in fstab except for the /, home and swap 
  volumes.  pmount is installed.
  
  My main problem is booting and what has caused me difficulties is trying 
  to do is to get automount features to work again in gnome.  It works 
  fine on my other Arch partition which was installed a year ago or so, 
  currently upgraded to testing.  The old partition is booted with 
  earlymodules=piix.  I did not install legacy IDE support on the new 
  system.
  
  I am happy to post other information if someone has a clue as to what's 
  going on here.  I am unable to access this PC during the day, so I won't 
  be able to reply until tonight. 
  
  Your kind support would be appreciated.
  
  dViking
  
  ___
  arch mailing list
  arch@archlinux.org
  http://www.archlinux.org/mailman/listinfo/arch
 
 
 I have not experienced your problem (as I have no reason to have any USB
 peripherals connected during bootup), 
It's more of just an inconvenience to worry about unplugging it before I
boot.  It's just usually attached, contains music.
 but have you tried possibly
 booting with the Arch Kernel-fallback? Perhaps this may be a quick and
 dirty fix to your problem.
The fall back image generated by 0.8Beta will not boot.  I am not using
the legacy IDE support, but it complains about devices HDA3 not
containing a valid superblock.  The HDA3 partion (suppose the software
should have referred to it as SDA3, so I'll make that assumption), is my
alternate Arch Linux boot partition.  The regular kernel26.img doesn't
exhibit this problem.
 
 Just a thought.
 
 

Re: [arch] External USB devices

2007-01-24 Thread Guillermo A. Amaral
On Wednesday 24 January 2007 15:26:31 Derek Carlson wrote:
 I am experiencing some weirdness booting while an external USB storage
 device is attached.  As background (and only because I hope it will give
 a clue as to the exact software set), I am currently running from a
 system that was installed from the Beta 0.8, base ISO.

 If I leave my external 200GB hard drive, attached through USB cable,
 connected during the boot process, I get a number of errors during the

 auto configuration process.  The log file reports this:
   snip 

 Jan 24 06:48:44 slacker1 usb 3-7: new high speed USB device using
 ehci_hcd and address 4
 Jan 24 06:48:44 slacker1 usb 3-7: configuration #1 chosen from 1 choice
 Jan 24 06:48:44 slacker1 scsi5 : SCSI emulation for USB Mass Storage
 devices Jan 24 06:48:44 slacker1 usb-storage: device found at 4
 Jan 24 06:48:44 slacker1 usb-storage: waiting for device to settle
 before scanning
 Jan 24 06:48:49 slacker1 usb 3-7: reset high speed USB device using
 ehci_hcd and address 4
 Jan 24 06:48:49 slacker1 usb 3-7: device firmware changed
 Jan 24 06:48:49 slacker1 usb 3-7: USB disconnect, address 4
 Jan 24 06:48:49 slacker1 usb-storage: device scan complete
 Jan 24 06:48:49 slacker1 usb 3-7: new high speed USB device using
 ehci_hcd and address 5
 Jan 24 06:48:50 slacker1 usb 3-7: device descriptor read/64, error -71
 Jan 24 06:48:56 slacker1 usb 3-7: device descriptor read/64, error -71
 Jan 24 06:48:56 slacker1 usb 3-7: new high speed USB device using
 ehci_hcd and address 6
 Jan 24 06:48:57 slacker1 usb 3-7: device descriptor read/64, error -71
 Jan 24 06:49:02 slacker1 usb 3-7: device descriptor read/64, error -71
 Jan 24 06:49:02 slacker1 usb 3-7: new high speed USB device using
 ehci_hcd and address 7
 Jan 24 06:49:08 slacker1 usb 3-7: device not accepting address 7, error -71
 Jan 24 06:49:08 slacker1 usb 3-7: new high speed USB device using
 ehci_hcd and address 8
 Jan 24 06:49:08 slacker1 usb 3-7: device not accepting address 8, error -71

   snip 

  From there I can often times boot the system, but not necessarily or
 always.  For example, one time my sound card was not discovered.  One
 time I got a failure on a partition that was not being mounted and the
 system halted.  Rebooting has solved these problems.

 If I can successfully boot and start gnome while the hard drive was
 attached, the external drive will not show up as a mounted volume.
 When I unplug and plug the external hard drive again, my USB mouse will
 crap out, and only rebooting the computer will bring the mouse back again.

 If I leave *any* USB devices (flash drive for example) attached at boot
 time, I'll get similar scenarios as above.

 If I remove all USB devices, save the mouse, the system will boot
 correctly.  I can start gnome, and I can plug the external drive into
 the USB port, and I can mount it through nautilus, but it will not auto
 mount in spite of having HAL  daemon started,  and having installed
 pmount and  (for some reason unknown to me but reported in a forum)
 gnome-volume-manager.

 The last is a minor inconvenience, but the booting process being flaky
 is a bit disconcerting.

 I've commented out the entries in fstab except for the /, home and swap
 volumes.  pmount is installed.

 My main problem is booting and what has caused me difficulties is trying
 to do is to get automount features to work again in gnome.  It works
 fine on my other Arch partition which was installed a year ago or so,
 currently upgraded to testing.  The old partition is booted with
 earlymodules=piix.  I did not install legacy IDE support on the new
 system.

 I am happy to post other information if someone has a clue as to what's
 going on here.  I am unable to access this PC during the day, so I won't
 be able to reply until tonight.

 Your kind support would be appreciated.

 dViking

 ___
 arch mailing list
 arch@archlinux.org
 http://www.archlinux.org/mailman/listinfo/arch

I've had this happen with my $pod, it might just be that the drive can't 
handle the stress and loses sync so it disconnects and all kinds of wonky 
things happen when it tries to complete it's scan.

In my case I had to get a better cable and stop using heavily

What kind of drive is it? is it an enclosure drive?
If so, you might need to get a high end enclosure, trust me T_T I've been 
there.

-- 
Guillermo A. Amaral, BCSE
@ site: http://www.guillermoamaral.com/
@ blog: http://blog.guillermoamaral.com/
# nick: thewonka / thewonka81


pgpuy75w0XY9u.pgp
Description: PGP signature
___
arch mailing list
arch@archlinux.org
http://www.archlinux.org/mailman/listinfo/arch


Re: [arch] External USB devices

2007-01-24 Thread dpcarlson
 Guillermo A. Amaral [EMAIL PROTECTED] wrote: 
 On Wednesday 24 January 2007 15:26:31 Derek Carlson wrote:
  I am experiencing some weirdness booting while an external USB storage
  device is attached.  As background (and only because I hope it will give
  a clue as to the exact software set), I am currently running from a
  system that was installed from the Beta 0.8, base ISO.
 
  If I leave my external 200GB hard drive, attached through USB cable,
  connected during the boot process, I get a number of errors during the
 
  auto configuration process.  The log file reports this:
snip 
 
  Jan 24 06:48:44 slacker1 usb 3-7: new high speed USB device using
  ehci_hcd and address 4
  Jan 24 06:48:44 slacker1 usb 3-7: configuration #1 chosen from 1 choice
  Jan 24 06:48:44 slacker1 scsi5 : SCSI emulation for USB Mass Storage
  devices Jan 24 06:48:44 slacker1 usb-storage: device found at 4
  Jan 24 06:48:44 slacker1 usb-storage: waiting for device to settle
  before scanning
  Jan 24 06:48:49 slacker1 usb 3-7: reset high speed USB device using
  ehci_hcd and address 4
  Jan 24 06:48:49 slacker1 usb 3-7: device firmware changed
  Jan 24 06:48:49 slacker1 usb 3-7: USB disconnect, address 4
  Jan 24 06:48:49 slacker1 usb-storage: device scan complete
  Jan 24 06:48:49 slacker1 usb 3-7: new high speed USB device using
  ehci_hcd and address 5
  Jan 24 06:48:50 slacker1 usb 3-7: device descriptor read/64, error -71
  Jan 24 06:48:56 slacker1 usb 3-7: device descriptor read/64, error -71
  Jan 24 06:48:56 slacker1 usb 3-7: new high speed USB device using
  ehci_hcd and address 6
  Jan 24 06:48:57 slacker1 usb 3-7: device descriptor read/64, error -71
  Jan 24 06:49:02 slacker1 usb 3-7: device descriptor read/64, error -71
  Jan 24 06:49:02 slacker1 usb 3-7: new high speed USB device using
  ehci_hcd and address 7
  Jan 24 06:49:08 slacker1 usb 3-7: device not accepting address 7, error -71
  Jan 24 06:49:08 slacker1 usb 3-7: new high speed USB device using
  ehci_hcd and address 8
  Jan 24 06:49:08 slacker1 usb 3-7: device not accepting address 8, error -71
 
snip 
 
   From there I can often times boot the system, but not necessarily or
  always.  For example, one time my sound card was not discovered.  One
  time I got a failure on a partition that was not being mounted and the
  system halted.  Rebooting has solved these problems.
 
  If I can successfully boot and start gnome while the hard drive was
  attached, the external drive will not show up as a mounted volume.
  When I unplug and plug the external hard drive again, my USB mouse will
  crap out, and only rebooting the computer will bring the mouse back again.
 
  If I leave *any* USB devices (flash drive for example) attached at boot
  time, I'll get similar scenarios as above.
 
  If I remove all USB devices, save the mouse, the system will boot
  correctly.  I can start gnome, and I can plug the external drive into
  the USB port, and I can mount it through nautilus, but it will not auto
  mount in spite of having HAL  daemon started,  and having installed
  pmount and  (for some reason unknown to me but reported in a forum)
  gnome-volume-manager.
 
  The last is a minor inconvenience, but the booting process being flaky
  is a bit disconcerting.
 
  I've commented out the entries in fstab except for the /, home and swap
  volumes.  pmount is installed.
 
  My main problem is booting and what has caused me difficulties is trying
  to do is to get automount features to work again in gnome.  It works
  fine on my other Arch partition which was installed a year ago or so,
  currently upgraded to testing.  The old partition is booted with
  earlymodules=piix.  I did not install legacy IDE support on the new
  system.
 
  I am happy to post other information if someone has a clue as to what's
  going on here.  I am unable to access this PC during the day, so I won't
  be able to reply until tonight.
 
  Your kind support would be appreciated.
 
  dViking
 
  ___
  arch mailing list
  arch@archlinux.org
  http://www.archlinux.org/mailman/listinfo/arch
 
 I've had this happen with my $pod, it might just be that the drive can't 
 handle the stress and loses sync so it disconnects and all kinds of wonky 
 things happen when it tries to complete it's scan.
 
 In my case I had to get a better cable and stop using heavily
 
 What kind of drive is it? is it an enclosure drive?
 If so, you might need to get a high end enclosure, trust me T_T I've been 
 there.
 
 -- 
 Guillermo A. Amaral, BCSE
 @ site: http://www.guillermoamaral.com/
 @ blog: http://blog.guillermoamaral.com/
 # nick: thewonka / thewonka81
Hi Guillermo,

The drive is a MAXTOR 200GB external drive.  It's housed in a pretty heavy, 
shielded case, and connects to the computer via a shielded USB cable.  The 
cable seems longer than necessary, but there's a heavy braided shield that 
would seem to protect it pretty well. 

Those are some good