jcduell_at_lbl_dot_gov
Date: Thu Mar 18 2004 - 12:07:11 PST
Gosh darn it--people like us! Um, I mean, our software, that is... -- Jason Duell Future Technologies Group <jcduell_at_lbl_dot_gov> Computational Research Division Tel: +1-510-495-2354 Lawrence Berkeley National Laboratory ----- Forwarded message from Karel Semsch <[email protected]> ----- From: Karel Semsch <[email protected]> Subject: Re: BLCR Date: Thu, 18 Mar 2004 20:46:41 +0100 (CET) To: JCDuell_at_lbl_dot_gov Thank you for your mail. We will soon upgrade our kernel to 2.4.22, so I think it will solve the problem. I am running blcr on another computer without and problems and it is very good program. Karel > Karel: > > I'm very sorry--your email somehow got lost in the piles that I get > every day. > > Are you still interested in getting blcr to work? Are you still having > the same problem? I haven't seen this particular error before, but I > can look into it if you're still interested. > > Sorry for the late reply, > > -- > Jason Duell Future Technologies Group > <jcduell_at_lbl_dot_gov> Computational Research Division > Tel: +1-510-495-2354 Lawrence Berkeley National Laboratory > > > On Tue, Mar 09, 2004 at 01:50:43AM +0100, Karel Semsch wrote: > > Hello! My name is Karel and I am student of CTU in Prague, Czech > > Republic. I wanted to install blcr on my computer, but it didn't > > function. I did these steps: > > 1. I downloaded blcr-0.2.0.tar.gz > > 2. I am running Red Hat 2.4.18-3, so I logged as root and: > > ./configure --with-linux=/usr/src/linux-2.4 --with-system-map=/boot/System.map --prefix=/home/s3/karel/blcr > > 3. make > > 4. make install > > > > When I wanted to do: insmod vmadump.o, there where such error messages: > > > > vmadump.o: unresolved symbol __d_path_R99ee740c > > vmadump.o: unresolved symbol do_munmap_Raa753c35 > > vmadump.o: unresolved symbol interruptible_sleep_on_timeout_R5a57b6ef > > vmadump.o: unresolved symbol register_chrdev_R8fd899d1 > > vmadump.o: unresolved symbol sys_call_table_Rdfdb18bd > > vmadump.o: unresolved symbol kmem_cache_free_R891f2686 > > vmadump.o: unresolved symbol kmalloc_R93d4cfe6 > > vmadump.o: unresolved symbol vfree_R2fd1d81c > > vmadump.o: unresolved symbol __wake_up_R127fda83 > > vmadump.o: unresolved symbol getname_R7c60d66e > > vmadump.o: unresolved symbol boot_cpu_data_R0657d037 > > vmadump.o: unresolved symbol get_zeroed_page_R0c2188c7 > > vmadump.o: unresolved symbol __generic_copy_to_user_Rd523fdd3 > > vmadump.o: unresolved symbol securebits_Rabe77484 > > vmadump.o: unresolved symbol register_binfmt_R6a640616 > > vmadump.o: unresolved symbol free_pages_R9941ccb8 > > vmadump.o: unresolved symbol dput_R1dfa0098 > > vmadump.o: unresolved symbol send_sig_R802e966d > > vmadump.o: unresolved symbol locks_mandatory_area_R86d766ac > > vmadump.o: unresolved symbol flush_signals_Rc2193fd3 > > vmadump.o: unresolved symbol fget_Ra7b18ba5 > > vmadump.o: unresolved symbol filp_open_Re08a875b > > vmadump.o: unresolved symbol mem_map_Rb38eb0a6 > > vmadump.o: unresolved symbol __mntput_R6e26a04a > > vmadump.o: unresolved symbol dump_fpu_Rf7e7d3e6 > > vmadump.o: unresolved symbol fput_R3b3f88a0 > > vmadump.o: unresolved symbol register_blkdev_Raeb4ccb3 > > vmadump.o: unresolved symbol kfree_R037a0cba > > vmadump.o: unresolved symbol names_cachep_Rd25469b4 > > vmadump.o: unresolved symbol do_execve_R9c62098f > > vmadump.o: unresolved symbol printk_R1b7d4074 > > vmadump.o: unresolved symbol kernel_flag_Ra99dd800 > > vmadump.o: unresolved symbol do_BUG_R577f4bff > > vmadump.o: unresolved symbol __vmalloc_R79995c5b > > vmadump.o: unresolved symbol dcache_lock_Rf7c32ca1 > > vmadump.o: unresolved symbol do_mmap_pgoff_R7b5ef43d > > vmadump.o: unresolved symbol unregister_binfmt_R3ad92e30 > > > > Can you help me? I thank you for your advices. > > > > Karel