[SOLVED] Translate this command equivalent for Mint?

widda · 02-14-2010, 07:10 AM

Sorry, title's confusing, but can't edit it.
I may not know what I'm talking about, but does anyone want to have a go at translating this suggestion I dug up into one that Mint 7 would act on?

sudo insmod /lib/modules/`uname -r`/kernel/drivers/usb/serial/usbs erial.ko vendor=0x16d8 product=0x6280

Object is to get drivers for telstra turbo which isnt recognised at all yet.

Hangdog42 · 02-14-2010, 07:50 AM

Mint should understand that command as is (with the typos fixed that is). Have you tried running it? And if so, what is Mint doing or not doing? Error messages would be very helpful. You could also try a modprobe variation of that command:

modprobe usbserial vendor=0x16d8 product=0x6280

Of course one of the questions is why you would need the vendor and product information. If you're working off of some different advice, please post a link.

widda · 02-14-2010, 12:09 PM

I don't remember where I got the command from - it was during hours of trawling about trying to get friend's new telstra turbo wireless modem to be seen by just-installed Mint.
I ran it, not noticing the space in it - I don't spot any other typos, but I wouldn't know for sure, not familiar enough. Just copying and pasting what I read from some forum
I think terminal said command not found.
But it.s useful to know that it looks like acceptable Mint command, and will get back to friend and try again.

Hangdog42 · 02-14-2010, 05:05 PM

The only other real potential gotcha is the backtick (`) around the uname -r command. Make sure you type a backtick and not an apostrophe. The backtick causes the command in between them to be evaluated, where an apostrophe won't.

widda · 02-14-2010, 08:14 PM

Thanks: It didnt like the modprobe idea btw:

laptop:~$ modprobe usbserial vendor=0x16d8 product=0x6280exitWARNING: All config files need .conf: /etc/modprobe.d/oss-compat, it will be ignored in a future release.

I don't get what kind of action is suggested by this response.

widda · 02-14-2010, 11:56 PM

I put the amended command in-"sudo insmod..."- and met with no objections (nor any sign of action except being ready for new command, which I took as a good sign)

jstephens84 · 02-15-2010, 12:01 AM

Quote:

Originally Posted by widda

I put the amended command in-"sudo insmod..."- and met with no objections (nor any sign of action except being ready for new command, which I took as a good sign)

Yes that is normally a good sign. You can check by using lsmod. Not sure how familiar you are with mint or Ubuntu based distro's but all commands that need elevated privileges must be ran with sudo.

Hangdog42 · 02-15-2010, 07:19 AM

Yeah, if modprobe is silent, that means that the command worked. Modprobe only gets vocal when something goes wrong. And since modprobe does load a kernel module, you need to be root or use sudo.

widda · 02-15-2010, 07:39 AM

thanks hangdog and jstephens, I appreciate the extra education