Re: Problem with kernel modules after upgrade FC2->FC3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 16 November 2004 20:55, Dusan Djordjevic wrote:
> Hi all,
>
> I upgraded my working FC2 to FC3. Mostly it works fine except one thing.
> When I try to compile some kernel modules (in my case it is module for
> modem) it compiles, loads and works perfectly. But when I reboot
> machine, it stops working. All modules are in right place
> (/lib/modules/2.6.9-1.667/extra/) but something is not working. When I
> try to start slmodemd (daemon that drives modem) won't load, and here
<snip>
> directory)
> write(2, "error: mdm setup: cannot stat `/"..., 71error: mdm setup:
> cannot stat`/dev/slamr0': No such file or directory
> ) = 71
> write(2, "error: cannot setup device `/dev"..., 41error: cannot setup
> device `/dev/slamr0'
> ) = 41
> exit_group(-1)
>
> Something similar happens with vmware modules.
> Any idea ?

udev is new in FC3. It doesn't create your specific devices at a boot time 
because it hasn't been told to do so.

The way to deal with it is described here :
http://fedora.redhat.com/docs/udev/

Copying the device files to /etc/udev/devices/ should work. Perhaps you may 
need to set correct permissions in /etc/udev/permissions

Regards,
Marcel





[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux