Every so often, when I try to do something, modprobe gives out about
something. Is there a procedure for tracking down what modules are
required, from their obscure names ? As in:
Nov 2 15:16:49 minbar modprobe: modprobe: Can't locate module tty-ldisc-3
WTF ? I just did:
[root at minbar linux]# grep ldisc */*/*.o
Binary file drivers/net/ppp_async.o matches
Binary file drivers/net/ppp_synctty.o matches
Binary file drivers/net/slip.o matches
[root at minbar linux]# insmod ppp_synctty.o
[root at minbar linux]# insmod ppp_async.o
And it worked. Is there a better way than this ?
Kate
--
Microsoft - the best reason in the world to drink beer
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
