[expert] Load a module during installation (DPT Raid)
Hi all, I'm trying to install Mandrake 7.1 on a machine with a DPT Decade Raid card. DPT provide a driver for Linux in the form of a module, which I'd like to load during the Mandrake installation process. The module is wrapped up in a modules.cgz file (designed for RedHat), and modules.dep is provided also. I have extracted the actual module (dpt_i2o.o), but when I try to insmod it, I get an error from the perl based installer (can't tell you exactly what it is because I'm not in front of the machine at the moment). Is there any special procedure I need to follow to make this module work? As an alternative, I built a kernel (v2.2.5) and compiled in the DPT driver, and eepro100 which is required for my net card. When I try to use this with the blank.rdz installation disk, I get a couple of problems: 1) The graphical installer doesn't work (blank screen and PC just sits there) 2) Text mode works fine, until the network stage, where it fails to load the eepro100 module and therefore won't let me configure networking (even though eepro100 is compiled in so it doesn't need the module!) 3) If I skip to the next stage, it "can't retrieve zone info" and I have to reboot This is really driving me up the wall, if I can't find a solution I'm going to go back to RedHat :( Thanks for any help, John-Paul Smith Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
[expert] Mylex DAC960 root device
Hi, I'm trying to install Mandrake 7.1 on a machine with a Mylex DAC960PG RAID as the root device. The CD-ROM drive is on an AIC-7890 and is detected by the first stage of the installer, but when I try to manually add the DAC960, it can't find the device. That's not an immediate problem, because I can choose again in the main installer program, add the DAC960 and install with no problems. When I reboot, the kernel can't load the module for DAC960: kmod: failed to exec /sbin/modprobe -s -k block-major-48, errno = 2 VFS: Cannot open root device 30:05 I can't understand why this doesn't work, because I'm sure it used to! Any ideas? John-Paul Smith
Unresolved symbols (was: RE: [expert] Mylex DAC960 root device)
Ok, this was me being dense, the DAC960 module was on the root device, and the root device was the DAC960! I compiled a kernel on a another machine with the DAC960 code compiled in, and this worked ok. Now here's a problem which I've always wanted to know the answer to. Whenever I try to compile a kernel with modules, it never works properly. Basically, none of the modules will load due to unresolved symbols, e.g.: # modprobe 3c59x /lib/modules/2.2.15-4mdk/net/3c59x.o: unresolved symbol __global_cli /lib/modules/2.2.15-4mdk/net/3c59x.o: unresolved symbol __global_save_flags /lib/modules/2.2.15-4mdk/net/3c59x.o: unresolved symbol __global_restore_flags I've looked around on mailing list archives, etc, and this problem has been reported by quite a few different ppl, in various situations, and I have not seen any definitive solution. My compile procedure is: rm -fr /lib/modules/* make clean make dep make bzImage make modules make modules_install This is straight from the Mandrake book. I've also tried using make mrproper instead of make clean, and that makes no difference. The system is freshly installed Mandrake 7.1, but this also happened to me on RedHat 6.2. Thanks in advance :-) John-Paul Smith -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John-Paul Smith Sent: 30 August 2000 11:12 To: Mandrake Expert List Subject: [expert] Mylex DAC960 root device Hi, I'm trying to install Mandrake 7.1 on a machine with a Mylex DAC960PG RAID as the root device. The CD-ROM drive is on an AIC-7890 and is detected by the first stage of the installer, but when I try to manually add the DAC960, it can't find the device. That's not an immediate problem, because I can choose again in the main installer program, add the DAC960 and install with no problems. When I reboot, the kernel can't load the module for DAC960: kmod: failed to exec /sbin/modprobe -s -k block-major-48, errno = 2 VFS: Cannot open root device 30:05 I can't understand why this doesn't work, because I'm sure it used to! Any ideas? John-Paul Smith
RE: Unresolved symbols (was: RE: [expert] Mylex DAC960 rootdevice)
I just gave 3c59x as an example, I get the same unresolved symbols on all my modules. J-P -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Gavin Clark Sent: 30 August 2000 14:24 To: [EMAIL PROTECTED] Subject: Re: Unresolved symbols (was: RE: [expert] Mylex DAC960 rootdevice) on 8/30/00 5:57 AM, Jean-Louis Debert wrote: John-Paul Smith wrote: Now here's a problem which I've always wanted to know the answer to. Whenever I try to compile a kernel with modules, it never works properly. Basically, none of the modules will load due to unresolved symbols, e.g.: # modprobe 3c59x /lib/modules/2.2.15-4mdk/net/3c59x.o: unresolved symbol __global_cli /lib/modules/2.2.15-4mdk/net/3c59x.o: unresolved symbol __global_save_flags /lib/modules/2.2.15-4mdk/net/3c59x.o: unresolved symbol __global_restore_flags I've looked around on mailing list archives, etc, and this problem has been reported by quite a few different ppl, in various situations, and I have not seen any definitive solution. My compile procedure is: rm -fr /lib/modules/* make clean make dep make bzImage make modules make modules_install This is straight from the Mandrake book. I've also tried using make mrproper instead of make clean, and that makes no difference. I don't know whether this is Mandrake-specific, but it seems to me that modprobe needs _something_ to resolve "external" symbols. The "something" could be the new kernel (if already booted) but I rather think it is the System.map file (created in the top kernel source directory). Also, "make bzImage" does NOT _install_ the new kernel, it just compiles it ... and it's very possible that your new module _needs_ the new kernel already active ... Personally I always do this after compilation of a new kernel: 1. cp bzImage /boot/vmlinuz-new 2. rdev -R /boot/vmlinuz-new 1(this to make it read-only) 3. cp System.map /boot/System.map-new 4. cd /boot;ln -sf System.map-new System.map 5. add new entry to lilo.conf, pointing to new kernel 6. lilo -v -v 7. reboot and select label for new kernel Now, if you don't want to reboot, I'm not sure that the new module _can_ work with your previous kernel. If it can, I guess you could try to replace the System.map under /boot for modprobe to use. Are you sure 3c59x is the right module? I've seen that error when I was trying to load eepro when it should have been ne2k-pci. Gavin
[expert] Installation problem DB2 7.1 on Mandrake 7.1
Hi, I've been trying to install IBM DB2 V7.1 on a pretty much clean installation of Mandrake 7.1, and hitting a few problems. Initially, the install (db2setup) failed because it couldn't find db2. I manually added the /usr/IBMdb2/V7.1/bin directory to the path, then re-ran the installer. The log file is at http://www.doc.ic.ac.uk/~jcs97/db2setup.log The latest thing I've tried is: 1) Installing the rpms using db2_install 2) Manually creating users for the db2, db2fenc and db2admin instances 3) Following the instructions in the "Quick Beginnings for Linux" guide to set-up the instances When I do this manually I get the same result as in the log file :-( : SQL10007N Message "-1390" could not be retrieved. Reason code: "2". According to the IBM docs, this indicates a problem with file permissions, so I tried chown'ing the contents of the ~db2/sqllib directory to db2.db2. This fixed the above error, but now I get a much more obscure one. When I try to start the the instance (or the administration server) the "db2star2" program hangs (have to kill -9). IBM don't seem too forthcoming with their assistance, anyone here got any ideas? J-P Smith
