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. OK. I'd try man depmod man modprobe and see if that gives you any ideas. on 8/30/00 6:50 AM, John-Paul Smith wrote: 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] 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 root device)
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. -- Jean-Louis Debert[EMAIL PROTECTED] 74 Annemasse France old Linux fan
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
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
Re: [expert] Mylex DAC960
Anyone know any tricks to get Linux installed on a Mylex DAC 960 raid controller? I am installing from a scsi cdrom connected to a adaptec 7880 scsi controller. Linux sees the 7880 but when I try to add the DAC960 when it asks if there are any more scsi controllers to add it cant find it. I know there is a module for the 960 but I need the os on before I can rebuild the kernel... The DAC960 is NOT considered as a SCSI controller under Linux but as a block device instead. The DAC960 driver should be loaded during the install nevertheless and you should be able to access RAID volumes at fdisk/diskdruid time. Kind regards, Yann -- Yann-Erick Proy -- [EMAIL PROTECTED] Quartz Informatique -- http://www.quartz.fr/ -- Annecy (F-74000) La diversité est source de richesse.
[expert] Mylex DAC960
Anyone know any tricks to get Linux installed on a Mylex DAC 960 raid controller? I am installing from a scsi cdrom connected to a adaptec 7880 scsi controller. Linux sees the 7880 but when I try to add the DAC960 when it asks if there are any more scsi controllers to add it cant find it. I know there is a module for the 960 but I need the os on before I can rebuild the kernel... Bill Beauchemin Sunnyvale MDC Control Center GlobalCenter (a Global Crossing company) 888-541-9888
