FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have installed free driver from linuxant for my connexant 56K modem. After successful installation, I tried to make the modem connection by using kppp tool in fedora 5. when i query the modem , an error invoked "unable to create the modem lock file". Please help.
Tried to run it with higher privileges? If you don't have write access to where ever it tries to create the lockfile (an empty file usually), that's the problem..
I am facing a similar problem with RHEL 4? How do I find the location where the lock file will be created?
And I don't think I can go any further higher than the root user for the priveleges :-). I got the "unable to create lock file" when I tried querying the modem fom my root user account via kppp.
I don't really know what exactly caused the file lock problem, but having edited the file /etc/ppp/options as:
lock
crtscts
defaultroute
noauth
and after subsequent reboots the problem was solved. Also, I found out that the link /dev/modem pointing to my internal modem /dev/ttySFSH0 was getting deleted everytime I rebooted. So I added the line,
ln -s /dev/ttySFSH0 dev/modem
to the /etc/rc.d/rc.local file and cleared that hurdle.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.