jjg <jjge@xs4all.nl> wrote:
> I had to go back to Slack 12.0, since my USB disk became unusable. I got a
> never-ending stream of messages to the effect that a new address had been
> assigned to a new device, presumably my USB disk. The addresses ran
> sequentially up to 127, then back at 1.
> It is clearly a 12.1 issue, now I am back at 12.0, and everything is OK.
> Does anyone know more about this phenomenon?

jjg,

I've seen the same thing happen in another version of Slackware. I
think it was 10.2. I boot Slackware using a homemade grub boot CD-R
(kernel on the CD-R). I do this so I can carry my Linux system around
with me on a hard drive in a USB enclosure.

I end up booting from a variety of machines, since I sometimes try to
get some work done at my wife's place of work while I'm passing the
time (we car pool). I ask her "What machine can I boot from?", and she
directs me to an office cubicle that she thinks will be unoccupied for
a while.

In doing this I've found some machines that will sometimes show the
error you described. I was able to get around the error by using a
different USB connection on the machine. This really surprised me, but
it worked. That is not much of a solution, but it might work for you
in the short run.

Another suggestion is that you should try connecting your USB drive to
a completely different machine. This is a lot of work I know if you
have only data on your USB drive and not the whole OS. (You would have
to install Slackware 12.1 on the other machine too--or put Slackware
12.1 on the USB drive and use a boot disk like what I do.) My
experience showed that trying different machines can make a difference
with this problem.

BTW, I've only found a few machines that give me the error you
described.

-Joe