Suse Kernel 2.4.18 with NVIDIA confusion
I have upgraded my kernel from 2.4.17 to 2.4.18 with no problem, but now
need to rebuild the NVIDIA_kernel-1.0.2314.src.rpm. When I do the
rpm --rebuild (after rebooting into the new kernel in run level 3) I get 290
lines similar to the following.
/lib/modules/2.4.18-4GB/build/include/linux/modversions.h:290:
linux/modules/zorro.ver: No such file or directory.
Being new to Linux, I am not sure what the above line is telling me. (This
rebuild went off without a hitch with 2.4.17 kernel). The modversions.h file
is in the directory shown above, I looked at the modversions.h file and seen
the "#include
On Sunday 03 March 2002 14:11, Art Fore wrote:
I have upgraded my kernel from 2.4.17 to 2.4.18 with no problem, but now need to rebuild the NVIDIA_kernel-1.0.2314.src.rpm. When I do the rpm --rebuild (after rebooting into the new kernel in run level 3) I get 290 lines similar to the following. /lib/modules/2.4.18-4GB/build/include/linux/modversions.h:290: linux/modules/zorro.ver: No such file or directory.
Being new to Linux, I am not sure what the above line is telling me. (This rebuild went off without a hitch with 2.4.17 kernel). The modversions.h file is in the directory shown above, I looked at the modversions.h file and seen the "#include
" line along with the other 289 modules. The zorro.h file is in /lib/modules/2.4.18-4GB/build/include/linux/ directory along with the other files. So, I am confused. Should the modversion.h file have the linux/modules/ before the zorro.ver or should these files be in a /lib/modules/2.4.18-4GB/build/include/linux/linux/modules directory. There is a /lib/modules/2.4.18-4GB/build/include/linux/modules directory, but it is empty.
Could anyone clarify the confusion please?
Did you get the kernel-source.rpm from mantel? If so, you need to do cd /usr/src/linux make mrproper make cloneconfig make dep Then the rebuild should work. Since you could do a rebuild on 2.4.17 I assume you have the necessary patches to the nvidia code, so you shouldn't need to do any more than the above. //Anders
That got me one step closer. Now the --rebuild goes fine, but when I do the rpm -ivh, it comes up with depmod: /lib/modelses/s.4.18-4GB/modules.ieee1394map is not an ELF file depmod: cannot read ELF header from /lib/modules/s.4.18-4GB/modules.pnpbiosmap depmod: *** Unresolved symbols in /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: unresolved symbol kmap_page table /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver failed /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod NVdriver failed Have any suggestions for this? Art -----Original Message----- From: Anders Johansson [mailto:andjoh@cicada.linux-site.net] Sent: Sunday, March 03, 2002 5:13 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse Kernel 2.4.18 with NVIDIA confusion On Sunday 03 March 2002 14:11, Art Fore wrote:
I have upgraded my kernel from 2.4.17 to 2.4.18 with no problem, but now need to rebuild the NVIDIA_kernel-1.0.2314.src.rpm. When I do the rpm --rebuild (after rebooting into the new kernel in run level 3) I get 290 lines similar to the following. /lib/modules/2.4.18-4GB/build/include/linux/modversions.h:290: linux/modules/zorro.ver: No such file or directory.
Being new to Linux, I am not sure what the above line is telling me. (This rebuild went off without a hitch with 2.4.17 kernel). The modversions.h file is in the directory shown above, I looked at the modversions.h file and seen the "#include
" line along with the other 289 modules. The zorro.h file is in /lib/modules/2.4.18-4GB/build/include/linux/ directory along with the other files. So, I am confused. Should the modversion.h file have the linux/modules/ before the zorro.ver or should these files be in a /lib/modules/2.4.18-4GB/build/include/linux/linux/modules directory. There is a /lib/modules/2.4.18-4GB/build/include/linux/modules directory, but it is empty.
Could anyone clarify the confusion please?
Did you get the kernel-source.rpm from mantel? If so, you need to do cd /usr/src/linux make mrproper make cloneconfig make dep Then the rebuild should work. Since you could do a rebuild on 2.4.17 I assume you have the necessary patches to the nvidia code, so you shouldn't need to do any more than the above. //Anders -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
On Sunday 03 March 2002 15:10, Art Fore wrote:
That got me one step closer. Now the --rebuild goes fine, but when I do the rpm -ivh, it comes up with depmod: /lib/modelses/s.4.18-4GB/modules.ieee1394map is not an ELF file depmod: cannot read ELF header from /lib/modules/s.4.18-4GB/modules.pnpbiosmap depmod: *** Unresolved symbols in /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: unresolved symbol kmap_page table /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver failed /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod NVdriver failed
Have any suggestions for this?
Yep, but it makes me wonder how you built it for 2.4.17, since the same problem existed there. Grab the patch from mantel/next. It's called nvidia-pte-highmem do rpm -i on the src.rpm, and then rpm -bp on /usr/src/packages/SPECS/NVIDIA_kernel.spec That will get you the source in /usr/src/packages/BUILD/NVIDIA_kernel-1.0-2314 cd to that directory and do patch -p1 < nvidia-pte-highmem Then, as root, do 'make' and the module should build and install properly //Anders
That got me one step closer. Now the --rebuild goes fine, but when I do
Thanks Anders That got the Nvidia drivers installed and that seems to be working. Sound even kept working, but problem I was hoping to cure that came with 2.4.17 is still there. That is, the mouse is still flakey. When I click on the KDE start menu, most of the time, I have to click 3 or 4 times before the menu comes up and stays up. Most of the time it comes up and goes right away. It is almost like a contact bounce on the mouse switch, but did not have this problem until 2.4.17. Tried to adjust some settings in the mouse portion of the control panel, but that also did not help. This is quite irritating as it also does it when clicking on files in Konqueror, etc. Anyone have any ideas on this? Mouse is Microsoft intellieye wheel mouse with device = /dev/psaux and imps/2 protocol according to XF86Config. Vendor is AutoDetected and ZAxis Mapping is "4 5" Art -----Original Message----- From: Anders Johansson [mailto:andjoh@cicada.linux-site.net] Sent: Sunday, March 03, 2002 6:15 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse Kernel 2.4.18 with NVIDIA confusion On Sunday 03 March 2002 15:10, Art Fore wrote: the
rpm -ivh, it comes up with depmod: /lib/modelses/s.4.18-4GB/modules.ieee1394map is not an ELF file depmod: cannot read ELF header from /lib/modules/s.4.18-4GB/modules.pnpbiosmap depmod: *** Unresolved symbols in /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: unresolved symbol kmap_page table /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver failed /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod NVdriver failed
Have any suggestions for this?
Yep, but it makes me wonder how you built it for 2.4.17, since the same problem existed there. Grab the patch from mantel/next. It's called nvidia-pte-highmem do rpm -i on the src.rpm, and then rpm -bp on /usr/src/packages/SPECS/NVIDIA_kernel.spec That will get you the source in /usr/src/packages/BUILD/NVIDIA_kernel-1.0-2314 cd to that directory and do patch -p1 < nvidia-pte-highmem Then, as root, do 'make' and the module should build and install properly //Anders -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
* Art Fore (art_fore@3mts.com) [020303 22:48]: ->Thanks Anders -> ->That got the Nvidia drivers installed and that seems to be working. Sound ->even kept working, but problem I was hoping to cure that came with 2.4.17 is ->still there. That is, the mouse is still flakey. When I click on the KDE ->start menu, most of the time, I have to click 3 or 4 times before the menu ->comes up and stays up. Most of the time it comes up and goes right away. It ->is almost like a contact bounce on the mouse switch, but did not have this ->problem until 2.4.17. Tried to adjust some settings in the mouse portion of ->the control panel, but that also did not help. This is quite irritating as ->it also does it when clicking on files in Konqueror, etc. -> ->Anyone have any ideas on this? -> ->Mouse is Microsoft intellieye wheel mouse with device = /dev/psaux and ->imps/2 protocol according to XF86Config. Vendor is AutoDetected and ZAxis ->Mapping is "4 5" I've seen this with KDE 2.2.2 and you know what cured the weird mouse behavior and slow menu's for me..downgrading to QT 2.3.1. I didn't realize what a problem 2.3.2 was until I downgraded. Give that a shot if you are running 2.3.2 and see if it doesn't help. -----=====-----=====-----=====-----=====----- Ben Rosenberg mailto:ben@whack.org -----=====-----=====-----=====-----=====----- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC
Thanks Ben, but am running Qt 2.3.1 already. Art -----Original Message----- From: Ben Rosenberg [mailto:ben@whack.org] Sent: Sunday, March 03, 2002 10:52 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse Kernel 2.4.18 with NVIDIA confusion * Art Fore (art_fore@3mts.com) [020303 22:48]: ->Thanks Anders -> ->That got the Nvidia drivers installed and that seems to be working. Sound ->even kept working, but problem I was hoping to cure that came with 2.4.17 is ->still there. That is, the mouse is still flakey. When I click on the KDE ->start menu, most of the time, I have to click 3 or 4 times before the menu ->comes up and stays up. Most of the time it comes up and goes right away. It ->is almost like a contact bounce on the mouse switch, but did not have this ->problem until 2.4.17. Tried to adjust some settings in the mouse portion of ->the control panel, but that also did not help. This is quite irritating as ->it also does it when clicking on files in Konqueror, etc. -> ->Anyone have any ideas on this? -> ->Mouse is Microsoft intellieye wheel mouse with device = /dev/psaux and ->imps/2 protocol according to XF86Config. Vendor is AutoDetected and ZAxis ->Mapping is "4 5" I've seen this with KDE 2.2.2 and you know what cured the weird mouse behavior and slow menu's for me..downgrading to QT 2.3.1. I didn't realize what a problem 2.3.2 was until I downgraded. Give that a shot if you are running 2.3.2 and see if it doesn't help. -----=====-----=====-----=====-----=====----- Ben Rosenberg mailto:ben@whack.org -----=====-----=====-----=====-----=====----- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -JC -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
That got me one step closer. Now the --rebuild goes fine, but when I do
On Sun, 03 Mar 2002, you wrote: Thanks Anders That got the Nvidia drivers installed and that seems to be working. Sound even kept working, but problem I was hoping to cure that came with 2.4.17 is still there. That is, the mouse is still flakey. When I click on the KDE start menu, most of the time, I have to click 3 or 4 times before the menu comes up and stays up. Most of the time it comes up and goes right away. It is almost like a contact bounce on the mouse switch, but did not have this problem until 2.4.17. Tried to adjust some settings in the mouse portion of the control panel, but that also did not help. This is quite irritating as it also does it when clicking on files in Konqueror, etc. Anyone have any ideas on this? I know the shortcut is alt+f1 for whatever that is worth. Mouse is Microsoft intellieye wheel mouse with device = /dev/psaux and imps/2 protocol according to XF86Config. Vendor is AutoDetected and ZAxis Mapping is "4 5" Art -----Original Message----- From: Anders Johansson [mailto:andjoh@cicada.linux-site.net] Sent: Sunday, March 03, 2002 6:15 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse Kernel 2.4.18 with NVIDIA confusion On Sunday 03 March 2002 15:10, Art Fore wrote: the
rpm -ivh, it comes up with depmod: /lib/modelses/s.4.18-4GB/modules.ieee1394map is not an ELF file depmod: cannot read ELF header from /lib/modules/s.4.18-4GB/modules.pnpbiosmap depmod: *** Unresolved symbols in /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: unresolved symbol kmap_page table /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver failed /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod NVdriver failed
Have any suggestions for this?
Yep, but it makes me wonder how you built it for 2.4.17, since the same problem existed there. Grab the patch from mantel/next. It's called nvidia-pte-highmem do rpm -i on the src.rpm, and then rpm -bp on /usr/src/packages/SPECS/NVIDIA_kernel.spec That will get you the source in /usr/src/packages/BUILD/NVIDIA_kernel-1.0-2314 cd to that directory and do patch -p1 < nvidia-pte-highmem Then, as root, do 'make' and the module should build and install properly //Anders -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com --
is still there. That is, the mouse is still flakey. When I click on the KDE start menu, most of the time, I have to click 3 or 4 times before the menu comes up and stays up. Most of the time it comes up and goes right away. It
Run xev and look at the events being generated. If they make sense then it's not a hardware or X problem. -- 2:34pm up 19 days, 6:14, 1 user, load average: 0.16, 0.10, 0.03
Suse 7.1 kernel 2.4.17 & 2.4.4 My Xfree86 config for the Intellieye wheel mouse. Brian Marr Section "InputDevice" Driver "mouse" Identifier "Mouse[3]" Option "Device" "/dev/mouse" Option "InputFashion" "Mouse" Option "Name" "INTELLIPOINT MOUSE PS/2" Option "Protocol" "IMPS/2" Option "Vendor" "MICROSOFT" Option "ZAxisMapping" "4 5" EndSection On Tuesday 05 March 2002 01:02, you wrote:
On Sun, 03 Mar 2002, you wrote: Thanks Anders
That got the Nvidia drivers installed and that seems to be working. Sound even kept working, but problem I was hoping to cure that came with 2.4.17 is still there. That is, the mouse is still flakey. When I click on the KDE start menu, most of the time, I have to click 3 or 4 times before the menu comes up and stays up. Most of the time it comes up and goes right away. It is almost like a contact bounce on the mouse switch, but did not have this problem until 2.4.17. Tried to adjust some settings in the mouse portion of the control panel, but that also did not help. This is quite irritating as it also does it when clicking on files in Konqueror, etc.
Anyone have any ideas on this?
I know the shortcut is alt+f1 for whatever that is worth.
Mouse is Microsoft intellieye wheel mouse with device = /dev/psaux and imps/2 protocol according to XF86Config. Vendor is AutoDetected and ZAxis Mapping is "4 5"
Art
-----Original Message----- From: Anders Johansson [mailto:andjoh@cicada.linux-site.net] Sent: Sunday, March 03, 2002 6:15 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse Kernel 2.4.18 with NVIDIA confusion
On Sunday 03 March 2002 15:10, Art Fore wrote:
That got me one step closer. Now the --rebuild goes fine, but when I do
the
rpm -ivh, it comes up with depmod: /lib/modelses/s.4.18-4GB/modules.ieee1394map is not an ELF file depmod: cannot read ELF header from /lib/modules/s.4.18-4GB/modules.pnpbiosmap depmod: *** Unresolved symbols in /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: unresolved symbol kmap_page table /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver failed /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod NVdriver failed
Have any suggestions for this?
Yep, but it makes me wonder how you built it for 2.4.17, since the same problem existed there.
Grab the patch from mantel/next. It's called nvidia-pte-highmem
do rpm -i on the src.rpm, and then rpm -bp on /usr/src/packages/SPECS/NVIDIA_kernel.spec
That will get you the source in /usr/src/packages/BUILD/NVIDIA_kernel-1.0-2314 cd to that directory and do patch -p1 < nvidia-pte-highmem Then, as root, do 'make' and the module should build and install properly
//Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Problem is solved. Changed the mouse with the one on my desktop, it done the same thing with Windows, so it was contact bounce. Got a new mouse, now everything is OK. Thanks Art -----Original Message----- From: Brian Marr [mailto:cabernet@internode.on.net] Sent: Monday, March 04, 2002 12:47 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse Kernel 2.4.18 with NVIDIA confusion Suse 7.1 kernel 2.4.17 & 2.4.4 My Xfree86 config for the Intellieye wheel mouse. Brian Marr Section "InputDevice" Driver "mouse" Identifier "Mouse[3]" Option "Device" "/dev/mouse" Option "InputFashion" "Mouse" Option "Name" "INTELLIPOINT MOUSE PS/2" Option "Protocol" "IMPS/2" Option "Vendor" "MICROSOFT" Option "ZAxisMapping" "4 5" EndSection On Tuesday 05 March 2002 01:02, you wrote:
On Sun, 03 Mar 2002, you wrote: Thanks Anders
That got the Nvidia drivers installed and that seems to be working. Sound even kept working, but problem I was hoping to cure that came with 2.4.17 is still there. That is, the mouse is still flakey. When I click on the KDE start menu, most of the time, I have to click 3 or 4 times before the menu comes up and stays up. Most of the time it comes up and goes right away. It is almost like a contact bounce on the mouse switch, but did not have this problem until 2.4.17. Tried to adjust some settings in the mouse portion of the control panel, but that also did not help. This is quite irritating as it also does it when clicking on files in Konqueror, etc.
Anyone have any ideas on this?
I know the shortcut is alt+f1 for whatever that is worth.
Mouse is Microsoft intellieye wheel mouse with device = /dev/psaux and imps/2 protocol according to XF86Config. Vendor is AutoDetected and ZAxis Mapping is "4 5"
Art
-----Original Message----- From: Anders Johansson [mailto:andjoh@cicada.linux-site.net] Sent: Sunday, March 03, 2002 6:15 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Suse Kernel 2.4.18 with NVIDIA confusion
On Sunday 03 March 2002 15:10, Art Fore wrote:
That got me one step closer. Now the --rebuild goes fine, but when I do
the
rpm -ivh, it comes up with depmod: /lib/modelses/s.4.18-4GB/modules.ieee1394map is not an ELF file depmod: cannot read ELF header from /lib/modules/s.4.18-4GB/modules.pnpbiosmap depmod: *** Unresolved symbols in /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: unresolved symbol kmap_page table /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver failed /lib/modules/s.4.18-4GB/kernel/drivers/NVdriver: insmod NVdriver failed
Have any suggestions for this?
Yep, but it makes me wonder how you built it for 2.4.17, since the same problem existed there.
Grab the patch from mantel/next. It's called nvidia-pte-highmem
do rpm -i on the src.rpm, and then rpm -bp on /usr/src/packages/SPECS/NVIDIA_kernel.spec
That will get you the source in /usr/src/packages/BUILD/NVIDIA_kernel-1.0-2314 cd to that directory and do patch -p1 < nvidia-pte-highmem Then, as root, do 'make' and the module should build and install properly
//Anders
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Did you get the kernel-source.rpm from mantel? If so, you need to do
I should mention that the only thing 'mantel specific' about my answer is the 'make cloneconfig' bit. If you get a vanilla source you won't have that. incidentally, you could just do touch /usr/src/linux/include/linux/modversions.h //Anders
participants (6)
-
Anders Johansson -
Art Fore -
Ben Rosenberg -
Brian Marr -
Derek Fountain -
rev rob