Dear list members, I saw that some users were running 2.6.17-1.2174_FC5 kernels and I was running 2157_FC5 so I yum installed newer one. Upon booting I got some messages. When compiling slmodem-20060727 I got syslogd messages related to the messages at bootup. [olivares@ShuttleX slmodem-20060727]$ make KERNEL_VER=/lib/modules/2.6.17-1.2174_FC5/build/ make -C modem all make[1]: Entering directory `/home/olivares/Downloads/slmodem-20060727/modem' make[1]: Leaving directory `/home/olivares/Downloads/slmodem-20060727/modem' make -C drivers KERNEL_DIR=/lib/modules/2.6.17-1.2174_FC5/build make[1]: Entering directory `/home/olivares/Downloads/slmodem-20060727/drivers' make modules -C /lib/modules/2.6.17-1.2174_FC5/build SUBDIRS=/home/olivares/Downloads/slmodem-20060727/drivers make[2]: Entering directory `/usr/src/kernels/2.6.17-1.2174_FC5-i686' CC [M] /home/olivares/Downloads/slmodem-20060727/drivers/amrmo_init.o CC [M] /home/olivares/Downloads/slmodem-20060727/drivers/sysdep_amr.o CC [M] /home/olivares/Downloads/slmodem-20060727/drivers/st7554.o make[3]: *** [/home/olivares/Downloads/slmodem-20060727/drivers/st7554.o] Segmentation fault make[3]: *** Deleting file `/home/olivares/Downloads/slmodem-20060727/drivers/st7554.o' make[2]: *** [_module_/home/olivares/Downloads/slmodem-20060727/drivers] Error 2make[2]: Leaving directory `/usr/src/kernels/2.6.17-1.2174_FC5-i686' make[1]: *** [all] Error 2 make[1]: Leaving directory `/home/olivares/Downloads/slmodem-20060727/drivers' make: *** [drivers] Error 2 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: Oops: 0000 [#4] [olivares@ShuttleX slmodem-20060727]$ Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: CPU: 0 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: EIP is at _stext+0x3fbffde0/0x3c Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: eax: cdc3d5f8 ebx: 00000000 ecx: dc8e7260 edx: c80ccf0c Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: esi: c80cc000 edi: db29800e ebp: c80ccf0c esp: c80cce10 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: ds: 007b es: 007b ss: 0068 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: Process sh (pid: 2426, threadinfo=c80cc000 task=c7d56aa0) Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: Stack: c04695a4 00000000 db29800e 00000000 00000001 00000001 c80ccea4 cdc3d5f8 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: c80ccedc 00000010 c04b15f8 00000000 ec897d97 00000008 db298005 dbfe3d20 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: cdc3d5f8 c80cc000 c80ccf0c dbb8f4d0 dbfe3d20 c0469e93 db298000 dbb8f4d0 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: Call Trace: Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: <c04695a4> __link_path_walk+0x477/0xd1f <c04b15f8> inode_has_perm+0x5b/0x63 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: <c0469e93> link_path_walk+0x47/0xb9 <c046a23d> do_path_lookup+0x1f6/0x24d Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: <c0468ffc> getname+0x91/0x98 <c046aa1e> __user_walk_fd+0x2f/0x40 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: <c04645a0> vfs_stat_fd+0x19/0x40 <c0464654> sys_stat64+0xf/0x23 Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: <c0402cb3> syscall_call+0x7/0xb Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: Code: Bad EIP value. Message from syslogd@ShuttleX at Sun Aug 13 01:38:50 2006 ... ShuttleX kernel: EIP: [<00000000>] _stext+0x3fbffde0/0x3c SS:ESP 0068:c80cce10 slmodemd compiled and installed and I could connect [olivares@ShuttleX slmodem-20060727]$ su - Password: [root@ShuttleX ~]# modprobe ungrab-winmodem [root@ShuttleX ~]# modprobe slamr [root@ShuttleX ~]# slmodemd -c USA /dev/slamr error: mdm setup: cannot stat `/dev/slamr': No such file or directory error: cannot setup device `/dev/slamr' [root@ShuttleX ~]# slmodemd -c USA /dev/slamr0 SmartLink Soft Modem: version 2.9.11 Jul 28 2006 00:19:13 symbolic link `/dev/ttySL0' -> `/dev/pts/2' created. modem `slamr0' created. TTY is `/dev/pts/2' Use `/dev/ttySL0' as modem device, Ctrl+C for termination. To make a long story short, are those messages harmful? or as long as the PC works should I not worry about them. NOTE: This is the same pc with the udev (BUG) CPU Spin lock message. Thanks and Best Regards, Antonio __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
