That didn’t work out either…sure I coulda done the pre-historic route but this is 2010 not 1995…it shouldn’t be necessary.
So now here I sit…cdrom still busted in Linux…OpenOffice DB still chokes…OpenSuse cd’s still lock up…lotsa users continually complaining about updates that hose their system…Installs with borked X windows…driver updates that cause me to have to login as root and run X to fix it…and the straw that broke the camels back…disabling root logins by default to cause yet more unecessary headaches…
Going to bed now…wake me up at the next version…If the same thing happens maybe I’ll try gentoo or go back to mandriva. Too bad…I really kinda liked Suse…
>
> First I started out asking a simple question about the libata.force
> command: ‘libata force parameter’ (http://tinyurl.com/2bz4ys9)
>
> That didn’t work out…no real answers
In your OP, you asked: “My question is where do you find the proper
port.device numbers?”
kernel-parameters.txt says it:
"The format is comma separated list of “[ID:]VAL” where ID is
PORT.DEVICE]. PORT and DEVICE are decimal numbers
matching port, link or device. Basically, it matches
the ATA ID string printed on console by libata. "
So look in e.g. the output from dmesg.
> Then I thought I’d try compiling and hacking my own source:
> ‘Extract a config from running kernel’ (http://tinyurl.com/24ssfza)
You could have installed the qt3-devel package from the network, but
doing a “make menuconfig” will work just as well.