[<<] [<] Page 1 of 3 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
unresolved symbols
From: Jorge Nerin ####@####.#### Date: 7 Oct 2000 00:24:20 -0000 Message-Id: <39DE6DDA.EB143DBF@zaralinux.com> Hello I have a Colorado Direct 9600, wich BTW I don't know if it's supported by plustek module, bu t my problem is that: after downloading and compiling sane-1.0.3 and plustek-sane-0_36_35.tar.gz, when I try to insmod the module pt_drv in my system I get this: modprobe pt_drv /lib/modules/2.4.0-test9/misc/pt_drv.o: unresolved symbol get_user_ret /lib/modules/2.4.0-test9/misc/pt_drv.o: unresolved symbol put_user_ret /lib/modules/2.4.0-test9/misc/pt_drv.o: insmod /lib/modules/2.4.0-test9/misc/pt_drv.o failed /lib/modules/misc/pt_drv.o: unresolved symbol get_user_ret /lib/modules/misc/pt_drv.o: unresolved symbol put_user_ret /lib/modules/misc/pt_drv.o: insmod /lib/modules/misc/pt_drv.o failed /lib/modules/misc/pt_drv.o: insmod pt_drv failed My kernel is 2.4.0-test9 (SMP compiled and uncomented in the Makefile), but either way I can't insmod the driver. -- Jorge Nerin ####@####.#### | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: unresolved symbols
From: ####@####.#### (G. Jaeger) Date: 15 Oct 2000 10:33:21 -0000 Message-Id: <13kl8i-0d27QuC@fwd04.sul.t-online.com> On Sat, 07 Oct 2000 02:27:06 +0200, Jorge Nerin wrote: >Hello I have a Colorado Direct 9600, wich BTW I don't know if it's >supported by plustek module, bu t my problem is that: > >after downloading and compiling sane-1.0.3 and >plustek-sane-0_36_35.tar.gz, when I try to insmod the module pt_drv in >my system I get this: > >modprobe pt_drv >/lib/modules/2.4.0-test9/misc/pt_drv.o: unresolved symbol get_user_ret >/lib/modules/2.4.0-test9/misc/pt_drv.o: unresolved symbol put_user_ret >/lib/modules/2.4.0-test9/misc/pt_drv.o: insmod >/lib/modules/2.4.0-test9/misc/pt_drv.o failed >/lib/modules/misc/pt_drv.o: unresolved symbol get_user_ret >/lib/modules/misc/pt_drv.o: unresolved symbol put_user_ret >/lib/modules/misc/pt_drv.o: insmod /lib/modules/misc/pt_drv.o failed >/lib/modules/misc/pt_drv.o: insmod pt_drv failed > >My kernel is 2.4.0-test9 (SMP compiled and uncomented in the Makefile), >but either way I can't insmod the driver. > >-- >Jorge Nerin ####@####.#### > Hi Jorge, I have tested at least with 2.4.0-test7 and there it works. I decided to stop testing for Kernel 2.4 until there is an "official" version available, because each new test-release has some changes, that affect the driver. I always thought, that the test Kernels a prereleases of the upcomming new version to fix the last bugs, but even during the test phase they accept large patches and change system-structures so it's necessary to patch a kernel-mode driver each time a test-version has been released. I hope you understand my point of view. As far as there's a stable version 2.4 available, there will be a plustek-driver. Gerhard ---------------------------------------- ####@####.#### ---------------------------------------- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: unresolved symbols
From: "Jaeger, Gerhard" ####@####.#### Date: 25 Oct 2000 12:28:07 -0000 Message-Id: <00102514315300.02640@gja> Hi Jorge, On Sam, 07 Okt 2000, Jorge Nerin wrote: > Hello I have a Colorado Direct 9600, wich BTW I don't know if it's > supported by plustek module, bu t my problem is that: > I just found your mail again where you told us the scanner model. Well, I'm sorry but the Colorado Direct 9600 is NOT support by the Plustek driver. Please refer to the Primax site, there they claim to have a driver for your Primax model: http://thor.prohosting.com/~chrordig/Primax/ Sorry again (there's also the wrong model mentionend in the sane-plustek man-page) Gerhard | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: unresolved symbols
From: Jorge Nerin ####@####.#### Date: 25 Oct 2000 22:29:06 -0000 Message-Id: <39F71B0E.7BEE2C29@zaralinux.com> "Jaeger, Gerhard" wrote: > > Hi Jorge, > > On Sam, 07 Okt 2000, Jorge Nerin wrote: > > Hello I have a Colorado Direct 9600, wich BTW I don't know if it's > > supported by plustek module, bu t my problem is that: > > > > I just found your mail again where you told us the scanner model. > Well, I'm sorry but the Colorado Direct 9600 is NOT support > by the Plustek driver. Please refer to the Primax site, there they > claim to have a driver for your Primax model: > > http://thor.prohosting.com/~chrordig/Primax/ > > Sorry again (there's also the wrong model mentionend in the > sane-plustek man-page) > > Gerhard Well, thanks and sorry for wasting your time. Very god job of info and trying to help fixing a nonexistet bug. I'll try it then. -- Jorge Nerin ####@####.#### | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Unresolved Symbols
From: John Carroll ####@####.#### Date: 1 Jan 2001 20:27:41 -0000 Message-Id: <Pine.LNX.4.21.0101011429310.819-100000@groveton.com> A couple of months ago I compiled sane and pt_drv under RH linux 6.2 for the OpticPro 9636T and never got it working, though the scanner works fine under Win95. There are apparently lots of problems with the way I've set things up. Maybe somebody seeing these error messages can point me in the right direction. First, on bootup I get error messages telling me about "unresolved symbols" in /lib/modules/2.2.14-5.0/pt_drv.o and in /lib/modules/misc/pt_drv.o. When I try "make load" I get the following: /lib/modules/2.2.14-5.0/misc/pt_drv.o init_module: Device or resource busy /lib modules/2.2.14-5.0/misc/pt_drv.o insmod: /lib/modules/2.2.14-5.0/misc/pt_drv.o: insmod /lib/modules/misc/pt_drv.o failed make: *** [load] Error 1 Apparently because I have an old BIOS, I also get a message that /etc/conf.modules is more recent than /lib/modules/2.2.14-5.0/modules.dep However, when I do "touch" modules.dep, that gets rid of that error message. Any suggestions much appreciated. John Carroll | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Unresolved Symbols
From: "G. Jaeger" ####@####.#### Date: 3 Jan 2001 18:26:06 -0000 Message-Id: <14DsfA-2KMfw0C@fmrl03.sul.t-online.com> On Mon, 1 Jan 2001 15:30:42 -0500 (EST), John Carroll wrote: > >A couple of months ago I compiled sane and pt_drv under RH linux 6.2 for >the OpticPro 9636T and never got it working, though the scanner >works fine under Win95. There are apparently lots of problems with the >way I've set things up. Maybe somebody seeing these error messages can point >me in the right direction. > >First, on bootup I get error messages telling me about "unresolved >symbols" in /lib/modules/2.2.14-5.0/pt_drv.o and in >/lib/modules/misc/pt_drv.o. > >When I try "make load" I get the following: > >/lib/modules/2.2.14-5.0/misc/pt_drv.o init_module: Device or resource busy > >/lib modules/2.2.14-5.0/misc/pt_drv.o >insmod: /lib/modules/2.2.14-5.0/misc/pt_drv.o: insmod >/lib/modules/misc/pt_drv.o failed >make: *** [load] Error 1 > >Apparently because I have an old BIOS, I also get a message that >/etc/conf.modules is more recent than /lib/modules/2.2.14-5.0/modules.dep >However, when I do "touch" modules.dep, that gets rid of that error >message. > >Any suggestions much appreciated. > >John Carroll > Hi John, well first of all it doesn't matter if you have a old BIOS or not. Each time you change the /etc/conf.modules file, you have to call depmod then everything is fine. Next thing: unresolved symbols Can you tell us which symbols are missing? Can you also please tell us which SANE-version and which driver-version you're using? Gerhard ---------------------------------------- ####@####.#### ---------------------------------------- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Unresolved Symbols
From: John Carroll ####@####.#### Date: 4 Jan 2001 17:35:53 -0000 Message-Id: <Pine.LNX.4.21.0101041202450.1150-100000@groveton.com> On Wed, 3 Jan 2001, G. Jaeger wrote: > On Mon, 1 Jan 2001 15:30:42 -0500 (EST), John Carroll wrote: > > > > >A couple of months ago I compiled sane and pt_drv under RH linux 6.2 for > >the OpticPro 9636T and never got it working, though the scanner > >works fine under Win95. There are apparently lots of problems with the > >way I've set things up. Maybe somebody seeing these error messages can point > >me in the right direction. > > > >First, on bootup I get error messages telling me about "unresolved > >symbols" in /lib/modules/2.2.14-5.0/pt_drv.o and in > >/lib/modules/misc/pt_drv.o. > > > >When I try "make load" I get the following: > > > >/lib/modules/2.2.14-5.0/misc/pt_drv.o init_module: Device or resource busy > > > >/lib modules/2.2.14-5.0/misc/pt_drv.o > >insmod: /lib/modules/2.2.14-5.0/misc/pt_drv.o: insmod > >/lib/modules/misc/pt_drv.o failed > >make: *** [load] Error 1 > > > >Apparently because I have an old BIOS, I also get a message that > >/etc/conf.modules is more recent than /lib/modules/2.2.14-5.0/modules.dep > >However, when I do "touch" modules.dep, that gets rid of that error > >message. > > > >Any suggestions much appreciated. > > > >John Carroll > > > Hi John, > > well first of all it doesn't matter if you have a old BIOS or not. > Each time you change the /etc/conf.modules file, you have to call > depmod > then everything is fine. > Next thing: unresolved symbols > Can you tell us which symbols are missing? > Can you also please tell us which SANE-version and which driver-version > you're using? > > Gerhard Hi Gerhard, Thanks for your help. For what it's worth, the SANE-version is 1.0.3 and the driver version is 0.36-36 . I still get the message about "unresolved symbols" and I have no idea how to determine which symbols are missing. Now the EMBARRASSING part. The message: "Device or resource busy" went away when I noticed the scanner was unplugged and plugged it in. After that I was able to load the module and use "scanimage" to scan a photo. However, at this point it scans only the area where transparencies are placed to be scanned. So far Gimp hasn't been able to find the scanner, so I guess when I get that sorted out, I'll be able to adjust the image area, etc. Since the "unresolved modules" messages persist, I've appended the messages I get in /var/log/messages that appear related to the scanner. Maybe they'll throw some light on the "unresolved symbols question." Meanwhile, the scanner seems to work after a fashion whatever the symbols problem may be. Thanks for your help, and especially for the driver. John -------Modules material from /var/log/messages-------- 4 10:45:21 groveton depmod: depmod: Jan 4 10:45:22 groveton depmod: *** Unresolved symbols in /lib/modules/2.2.14-5.0/misc/pt_drv.o Jan 4 10:45:22 groveton depmod: depmod: Jan 4 10:45:22 groveton depmod: *** Unresolved symbols in /lib/modules/misc/pt_drv.o ********************************************************** Jan 4 10:53:04 groveton modprobe: Note: /etc/conf.modules is more recent than /lib/modules/2.2.14-5.0/modules.dep Jan 4 10:53:29 groveton insmod: Note: /etc/conf.modules is more recent than /lib/modules/2.2.14-5.0/modules.dep Jan 4 10:53:29 groveton kernel: PPP Deflate Compression module registered Jan 4 10:53:29 groveton insmod: Note: /etc/conf.modules is more recent than /lib/modules/2.2.14-5.0/modules.dep Jan 4 10:56:27 groveton kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2] Jan 4 10:56:27 groveton kernel: parport1: PC-style at 0x278 [SPP] Jan 4 10:56:28 groveton kernel: pt_drv : driver version = 0.36-36 Jan 4 10:56:28 groveton kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2] Jan 4 10:56:28 groveton kernel: parport1: PC-style at 0x278 [SPP] Jan 4 10:56:28 groveton kernel: pt_drv : driver version = 0.36-36 Jan 4 10:57:09 groveton kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2] Jan 4 10:57:09 groveton kernel: parport1: PC-style at 0x278 [SPP] Jan 4 10:57:10 groveton kernel: pt_drv : driver version = 0.36-36 Jan 4 10:57:10 groveton kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2] Jan 4 10:57:10 groveton kernel: parport1: PC-style at 0x278 [SPP] Jan 4 10:57:10 groveton kernel: pt_drv : driver version = 0.36-36 *************************************************** Jan 4 10:57:57 groveton kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2] Jan 4 10:57:57 groveton kernel: parport1: PC-style at 0x278 [SPP] Jan 4 10:57:57 groveton kernel: pt_drv : driver version = 0.36-36 Jan 4 10:57:57 groveton kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2] Jan 4 10:57:57 groveton kernel: parport1: PC-style at 0x278 [SPP] Jan 4 10:57:58 groveton kernel: pt_drv : driver version = 0.36-36 Jan 4 10:58:57 groveton PAM_pwdb[751]: (login) session opened for user jjc by LOGIN(uid=0) Jan 4 10:59:18 groveton modprobe: modprobe: Can't locate module char-major-81 Jan 4 10:59:19 groveton modprobe: modprobe: Can't locate module char-major-81 Jan 4 10:59:20 groveton modprobe: modprobe: Can't locate module char-major-40 Jan 4 10:59:52 groveton kernel: parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2] Jan 4 10:59:52 groveton kernel: parport1: PC-style at 0x278 [SPP] Jan 4 10:59:52 groveton kernel: pt_drv : driver version = 0.36-36 Jan 4 10:59:52 groveton kernel: pt_drv0: 9636T/12000T found on port 0x0378 Jan 4 10:59:52 groveton kernel: pt_drv0: Lamp-Timer set to 180 seconds. Jan 4 10:59:52 groveton kernel: pt_drv0: WarmUp period set to 30 seconds. Jan 4 10:59:52 groveton kernel: pt_drv0: Lamp untouched on driver unload. Jan 4 11:00:08 groveton modprobe: modprobe: Can't locate module char-major-81 Jan 4 11:01:03 groveton last message repeated 2 times Jan 4 11:02:05 groveton last message repeated 4 times | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Unresolved Symbols
From: "G. Jaeger" ####@####.#### Date: 4 Jan 2001 19:14:37 -0000 Message-Id: <14EFtZ-1PibI0C@fmrl06.sul.t-online.com> Hi John, I suggest to dive into the plustek_driver/h directory. There you'll find the file plustek_scan.h Open that file and find the line #if 0 (must be around line 79) change the 0 to 1, then recompile and reinstall the driver. This should help with the unresolved symbols. If you still have problems, I suggest to download the V0.37 Version and recompile the whole stuff (SANE and the driver) Have you set the following lines to your /etc/conf.modules? alias char-major-40 pt_drv pre-install pt_drv modprobe -k parport and after that you MUST call depmod -v Note: The install.txt file in v0.36 says post-install - this is wrong I hope this helps you Gerhard ---------------------------------------- ####@####.#### ---------------------------------------- | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
unresolved symbols
From: Steve Hanov ####@####.#### Date: 8 Feb 2002 16:51:50 -0000 Message-Id: <Pine.SOL.4.05.10202081143350.6874-100000@rees.math.uwaterloo.ca> I am trying to install the plustek driver, but I am having problems. I am using sane-backends-1.0.7.tar.gz and plustek-module-0_41_3.tar.gz with red hat linux-2.4.7-10. Any help is appreciated. [root@frodo linux]# insmod pt_drv Using /lib/modules/2.4.7-10/misc/pt_drv.o /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol proc_mkdir_Rsmp_220b03b4 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol get_fast_time_Rsmp_60743022 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol create_proc_entry_Rsmp_3a9bfbd2 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol add_timer_Rsmp_08d2a00e /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol tvec_bases_Rsmp_d29e5674 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol register_chrdev_Rsmp_65405f1d /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol remove_proc_entry_Rsmp_cfd23da1 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol del_timer_Rsmp_e239a3e9 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol proc_root_Rsmp_10df3dd9 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol __generic_copy_to_user_Rsmp_d523fdd3 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol unregister_chrdev_Rsmp_c192d491 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol __vmalloc_Rsmp_79995c5b /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol printk_Rsmp_1b7d4074 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol kfree_Rsmp_037a0cba /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol parport_unregister_device_Rsmp_608723fe /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol vfree_Rsmp_2fd1d81c /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol sprintf_Rsmp_3c2c5af5 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol kmalloc_Rsmp_93d4cfe6 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol parport_register_device_Rsmp_ff38484c /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol schedule_Rsmp_4292364c /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol __const_udelay_Rsmp_eae3dfd6 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol __udelay_Rsmp_9e7d6bd0 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol __generic_copy_from_user_Rsmp_116166aa /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol jiffies_Rsmp_0da02d67 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol parport_release_Rsmp_86118428 /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol parport_claim_Rsmp_929f160f /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol parport_enumerate_Rsmp_2aedfe75 [root@frodo linux]# lsmod Module Size Used by 3c59x 26336 1 (autoclean) ide-cd 27072 0 (autoclean) cdrom 28512 0 (autoclean) [ide-cd] i810_audio 14544 0 (autoclean) ac97_codec 8832 0 (autoclean) [i810_audio] soundcore 4464 2 (autoclean) [i810_audio] iscsi 21984 0 (unused) scsi_mod 95696 1 [iscsi] parport_pc 14768 1 (autoclean) lp 6416 0 (autoclean) parport 25600 1 (autoclean) [parport_pc lp] ds 7056 2 yenta_socket 9488 2 pcmcia_core 41600 0 [ds yenta_socket] autofs 11520 0 (autoclean) (unused) appletalk 20912 0 (autoclean) ipx 16448 0 (autoclean) ipchains 39200 0 nls_iso8859-1 2832 1 (autoclean) nls_cp437 4352 1 (autoclean) vfat 9584 1 (autoclean) fat 32384 0 (autoclean) [vfat] usb-uhci 21536 0 (unused) usbcore 51712 1 [usb-uhci] ext3 64624 3 jbd 40992 3 [ext3] [root@frodo linux]# -- perl -e 'open DSP, ">/dev/audio" or die; while (1) { # ####@####.#### print DSP (pack C, int((sin(0.34557519*$p)+sin(0.27488936*$p++))*64+127)); }; # http://www.student.math.uwaterloo.ca/~smhanov ' | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: unresolved symbols
From: "Jaeger, Gerhard" ####@####.#### Date: 8 Feb 2002 18:30:27 -0000 Message-Id: <16ZFSn-1hFbcWC@fmrl03.sul.t-online.com> This looks to me, as your kernel-configuration does not match the really installed and unsed kernel! You might recompile and install the kernel, and then recompile the driver... Gerhard On Friday, 8. February 2002 17:47, Steve Hanov wrote: > I am trying to install the plustek driver, but I am having problems. I > am using sane-backends-1.0.7.tar.gz and plustek-module-0_41_3.tar.gz with > red hat linux-2.4.7-10. > > Any help is appreciated. > > [root@frodo linux]# insmod pt_drv > Using /lib/modules/2.4.7-10/misc/pt_drv.o > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > proc_mkdir_Rsmp_220b03b4 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > get_fast_time_Rsmp_60743022 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > create_proc_entry_Rsmp_3a9bfbd2 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > add_timer_Rsmp_08d2a00e > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > tvec_bases_Rsmp_d29e5674 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > register_chrdev_Rsmp_65405f1d > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > remove_proc_entry_Rsmp_cfd23da1 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > del_timer_Rsmp_e239a3e9 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > proc_root_Rsmp_10df3dd9 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > __generic_copy_to_user_Rsmp_d523fdd3 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > unregister_chrdev_Rsmp_c192d491 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > __vmalloc_Rsmp_79995c5b > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > printk_Rsmp_1b7d4074 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol kfree_Rsmp_037a0cba > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > parport_unregister_device_Rsmp_608723fe > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol vfree_Rsmp_2fd1d81c > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > sprintf_Rsmp_3c2c5af5 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > kmalloc_Rsmp_93d4cfe6 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > parport_register_device_Rsmp_ff38484c > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > schedule_Rsmp_4292364c > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > __const_udelay_Rsmp_eae3dfd6 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > __udelay_Rsmp_9e7d6bd0 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > __generic_copy_from_user_Rsmp_116166aa > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > jiffies_Rsmp_0da02d67 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > parport_release_Rsmp_86118428 > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > parport_claim_Rsmp> > > ************************************************************* > Machen Sie Schluss mit dem Papierkram! > > Mit RECHNUNG ONLINE koennen Sie Ihre Telefonrechnung im > Internet einsehen, detailliert auswerten oder sich sogar per > E-Mail zuschicken lassen. > > Steigen Sie jetzt kostenlos ein unter: > http://www.telekom.de/rechnung-online > ************************************************************* > > > > Ihre Mail vom 07.02.2002 21:33: > Name: Jaeger > > >Kundennummer: 1940498768 > >Buchungskonto: 1940498768 > > > >Sehr geehrte Damen und Herren, > > > >zum zweiten Male wurden wir nun aufgefordert unsere eMail > > Adresse > > >unter https:/www.telekom.de/rechnung einzutragen. > >Dies ist schon vor einigen Wochen geschehen und kann auch > > via > > >Browser meinerseits immer wieder korrekt ausgelesen werden. > >Anscheinend ist die dahintersteckende Anwendung noch nicht > >ausgereift. > >Die eMail Adresse, die eingetragen ist, und wohin auch > >die Rechnungen gesandt werden sollen lautet: > > > ####@####.#### > > > >Bitte tragen Sie diese Adresse in der Rechnung-Online > > Datenbasis > > >ein, damit die Rechnung ordungsgemaess zugestellt werden > > kann. > > >Mit freundlichen Gruessen > > Gerhard Jaeger _929f160f > /lib/modules/2.4.7-10/misc/pt_drv.o: unresolved symbol > parport_enumerate_Rsmp_2aedfe75 > [root@frodo linux]# lsmod > Module Size Used by > 3c59x 26336 1 (autoclean) > ide-cd 27072 0 (autoclean) > cdrom 28512 0 (autoclean) [ide-cd] > i810_audio 14544 0 (autoclean) > ac97_codec 8832 0 (autoclean) [i810_audio] > soundcore 4464 2 (autoclean) [i810_audio] > iscsi 21984 0 (unused) > scsi_mod 95696 1 [iscsi] > parport_pc 14768 1 (autoclean) > lp 6416 0 (autoclean) > parport 25600 1 (autoclean) [parport_pc lp] > ds 7056 2 > yenta_socket 9488 2 > pcmcia_core 41600 0 [ds yenta_socket] > autofs 11520 0 (autoclean) (unused) > appletalk 20912 0 (autoclean) > ipx 16448 0 (autoclean) > ipchains 39200 0 > nls_iso8859-1 2832 1 (autoclean) > nls_cp437 4352 1 (autoclean) > vfat 9584 1 (autoclean) > fat 32384 0 (autoclean) [vfat] > usb-uhci 21536 0 (unused) > usbcore 51712 1 [usb-uhci] > ext3 64624 3 > jbd 40992 3 [ext3] > [root@frodo linux]# | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 3 [>] [>>] |