Lockup detecting USB
 

Bear with me, I'm just getting into this whole Linux thing. It's going to take me a while.

I just downloaded Slackware 9 and burned the iso. When I boot the CD, it runs through it's routine, it locks when the kernel assigns the USB. The exact wording of the last line to print is:

"usb.c: new USB bus registered, assigned bus number 1"

Once it hits this point, the system become completly unresponsive. Only a hard reset gets it moving again, only to encounter the same error.

I'm starting the system using the bare.i kernel.

The unit is a Compaq Presario notebook, model 1214SR. Mobile Duron 850, 384Mb RAM, IDE drives.

Since I'm new to this, I spent about two hours searching the forums for anything that might help, but I'm at a loss.

Any help anyone could provide would be wonderful. It would mean a lot to me.

:newbie:

Thanks in advance

-Goon-kun

Which usb drivers do you have compiled into your kernel or which modules are you using. Different peopel seem to have different success with different ones.
I use the usb-uhci module in combination with the ehci-hcd module for USB 2 support. Since it's a compaq notebook you might want to try the usb_ohci module.

Ok I should read the post properly before I reply. It was the install cd that was locking up. Well I don't use slackware but you might want to try and see if there are any boot disks which you could use without usb support just to get the install started. Or maybe try and find a boot option which disables usb.

So far I haven't been able to find any parameters that disable USB detection on startup, and since I can't get the system to boot, I can't modify the kernel.

I do appriciate the help. Any ideas where I can find a list of modifiers that might assist my bootup? I read through all the documentation that came with Slack and haven't found anything even close to a problem like this.

Hopefully somebody here has had a similar problem and knows a work around. I'm not really interested in tracking down a recent copy of x86 Solaris, but I might have to if this keeps up.

Thanks again for the help.

-Goon-kun

Alright,

Using the boot and root disk images, I got the system to boot to the command line. I had to use the lowmem.i kernel. Now I've got to figure out syntax for fdisk.

I had to stop what I was doing this morning so I could go to work (yay) but I intend to mess around with this later tonight or tomorrow.

When I run setup later tonight, will the installer run from the CD? I want to install slackware from the CD, as I intend to use nearly all the packages contained on the disc.

After booting the system to the command prompt, can I simply mount the CD-ROM and run setup from the CD?

This is an interesting experience. I can't say I've ever had any real trouble with OS installs before. Whatever you can learn from is good, I guess.

Any answers to my questions are appriciated. Thanks in advance.

-Goon-kun

When you boot from the cd, can you get to a command prompt? Or does it hang before you can do anything?

If you can boot with a separate disk and get to a command prompt I don't think you can start the install script on the cd. Frankly because I don't know where those scripts are and what they expect of the system...

Good luck though!

No, I am unable to reach a command prompt using the CD as the installer. The bare.i kernel attempts to load drivers for the USB ports and locks before completing.

I'll mess around with the boot disk some more later, hopefully I can get everything running.

-Goon-kun