Problem with kernel modules after upgrade FC2->FC3
Patrick Boutilier
boutilpj at ednet.ns.ca
Tue Nov 16 18:58:45 UTC 2004
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
> is strace:
>
> ice~>strace slmodemd
> execve("/usr/sbin/slmodemd", ["slmodemd"], [/* 28 vars */]) = 0
> uname({sys="Linux", node="ice", ...}) = 0
> brk(0) = 0x812c000
> access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
> directory)
> open("/etc/ld.so.cache", O_RDONLY) = 3
> fstat64(3, {st_mode=S_IFREG|0644, st_size=134135, ...}) = 0
> old_mmap(NULL, 134135, PROT_READ, MAP_PRIVATE, 3, 0) = 0xf6fdf000
> close(3) = 0
> open("/lib/tls/libc.so.6", O_RDONLY) = 3
> read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 O\247\000"...,
> 512) = 512
> fstat64(3, {st_mode=S_IFREG|0755, st_size=1512400, ...}) = 0
> old_mmap(0xa60000, 1207532, PROT_READ|PROT_EXEC, MAP_PRIVATE|
> MAP_DENYWRITE, 3, 0) = 0xa60000
> old_mmap(0xb81000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
> MAP_DENYWRITE, 3, 0x120000) = 0xb81000
> old_mmap(0xb85000, 7404, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
> MAP_ANONYMOUS, -1, 0) = 0xb85000
> close(3) = 0
> old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0) = 0xf6fde000
> mprotect(0xb81000, 8192, PROT_READ) = 0
> mprotect(0xa5c000, 4096, PROT_READ) = 0
> set_thread_area({entry_number:-1 -> 6, base_addr:0xf6fdeaa0,
> limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
> limit_in_pages:1, seg_not_present:0, useable:1}) = 0
> munmap(0xf6fdf000, 134135) = 0
> stat64("/dev/slamr0", 0xfeffe83c) = -1 ENOENT (No such file or
> 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 ?
Try running make install in the source directory for slmodemd. This
should create the correct /dev devices. Then copy /dev/slamr* to
/etc/udev/devices/.
Might work.
More information about the fedora-list
mailing list