[SLE] Mantel's 2.6.5-11 and 2.6.5-12 kernels and Nvidia
Hi all, I tried to compile the nvidia.ko module (release 5336 or 4620) for these two kernels. It compiles without error but don't load !! Can someone share his experience with these kernels ? Thanks. Michel
Catimimi wrote:
Hi all,
I tried to compile the nvidia.ko module (release 5336 or 4620) for these two kernels. It compiles without error but don't load !!
Can someone share his experience with these kernels ?
Thanks.
Michel
Was this done from the command line or using YaST ?. I've had problems compiling it from the .run file under 2.6.6 kernels, compilation failed. I checked on the nvidia site and it recommended using YaST, but I haven't tried that yet. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
On Tue, 11 May 2004 14:05:05 +0100
Sid Boyce
Was this done from the command line or using YaST ?. I've had problems compiling it from the .run file under 2.6.6 kernels, compilation failed. I checked on the nvidia site and it recommended using YaST, but I haven't tried that yet.
Maybe:
Ivan Sergio Borgonovo wrote:
On Tue, 11 May 2004 14:05:05 +0100 Sid Boyce
wrote: Was this done from the command line or using YaST ?. I've had problems compiling it from the .run file under 2.6.6 kernels, compilation failed. I checked on the nvidia site and it recommended using YaST, but I haven't tried that yet.
Maybe:
[PATCH] ia32: 4Kb stacks (and irqstacks) patch ... At present 4k stacks are selectable in config. When the feature has settled in we should remove the 8k option. This will break the nvidia modules. But Fedora uses 4k stacks so a new nvidia driver is expected soon. from 2.6.6 Changelog
I was planning to move from 2.6.3 to 2.6.6... I think I'll wait till I can't see a new driver version on nvidia site.
I'm determined not to get caught by the 4KSTACKS patch again. The first time, it hung in int during boot, so I built on another HD and I could get at the files on the partially corrupt drive, I still have it there as hdc. The second time I only checked the .config file and forgot to reverse the patch, that time after building driver 5336 and doing "init 5", my HD was trashed totally, the only way out was to do a fresh install with reformatting. It's an evil patch, after much pressure, we got Andrew Morton to make it a config option, but at 2.6.6-mm1, he's made it permanent again .... permanently!, despite arguments that it has the potential to seriously impact a business. At least he's supplied separate patches in the brokenout.tar.gz. Knowing Corporates, I'd expect nvidia to come up with a new driver six months from now, a big MAYBE, but I'm open to surprises. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
On Tue, 11 May 2004 15:41:22 +0100
Sid Boyce
I'm determined not to get caught by the 4KSTACKS patch again. The
[snip] I didn't follow the thread. I was just planning to update my workstation before leaving to Hong Kong for 2 months.
in the brokenout.tar.gz. Knowing Corporates, I'd expect nvidia to come up with a new driver six months from now, a big MAYBE, but I'm open to surprises. Regards
Adding up the 40 days missing to my departure... I won't have to wait too much after I'll be back ;) anyway in the changelog they commented:
new nvidia driver is expected soon. Surely sooner than a MS security patch I hope ;) What did make you think we should wait so long for a fix from nvidia?
If nvidia drivers were Open, we wouldn't have this problem I think. BTW I'm lurking on suse-programming-e and it seems that YaST new license moved some people into YaST development.
Ivan Sergio Borgonovo wrote:
On Tue, 11 May 2004 15:41:22 +0100 Sid Boyce
wrote: I'm determined not to get caught by the 4KSTACKS patch again. The
[snip]
I didn't follow the thread. I was just planning to update my workstation before leaving to Hong Kong for 2 months.
in the brokenout.tar.gz. Knowing Corporates, I'd expect nvidia to come up with a new driver six months from now, a big MAYBE, but I'm open to surprises. Regards
Adding up the 40 days missing to my departure... I won't have to wait too much after I'll be back ;) anyway in the changelog they commented:
Good luck on your trip. I always travelled with a laptop and tried to connect a few times a week.
new nvidia driver is expected soon.
I certainly hope so.
Surely sooner than a MS security patch I hope ;) What did make you think we should wait so long for a fix from nvidia?
Well, most closed source stuff is not the most moveable, besides, these things are usually done by one or two people on a part time basis.
If nvidia drivers were Open, we wouldn't have this problem I think.
I just saw a post that said the affected part was, so hoping the guys who did sterling work on earlier nvidia drivers to get them to work with 2.5/2.6-pre can come up with an answer.
BTW I'm lurking on suse-programming-e and it seems that YaST new license moved some people into YaST development.
I'd been wondering about that only today, like what is likely to make a wish list of new features and improvements, I hope they canvas the lists for ideas. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
-----Message d'origine----- De : Sid Boyce [mailto:sboyce@blueyonder.co.uk] Envoye : mardi 11 mai 2004 15:05 A : SuSE Mailing List Objet : Re: [SLE] Mantel's 2.6.5-11 and 2.6.5-12 kernels and Nvidia
Catimimi wrote:
Hi all,
I tried to compile the nvidia.ko module (release 5336 or 4620) for these two kernels. It compiles without error but don't load !!
Can someone share his experience with these kernels ?
Thanks.
Michel
Was this done from the command line or using YaST ?. I've had problems compiling it from the .run file under 2.6.6 kernels, compilation failed. I checked on the nvidia site and it recommended using YaST, but I haven't tried that yet. Regards Sid.
It was done from the command line, I never tried YaST but I'll. Thanks Regards.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-----Message d'origine----- De : Sid Boyce [mailto:sboyce@blueyonder.co.uk] Envoye : mardi 11 mai 2004 15:05 A : SuSE Mailing List Objet : Re: [SLE] Mantel's 2.6.5-11 and 2.6.5-12 kernels and Nvidia
Catimimi wrote:
Hi all,
I tried to compile the nvidia.ko module (release 5336 or 4620) for these two kernels. It compiles without error but don't load !!
Can someone share his experience with these kernels ?
Thanks.
Michel
Was this done from the command line or using YaST ?. I've had problems compiling it from the .run file under 2.6.6 kernels, compilation failed. I checked on the nvidia site and it recommended using YaST, but I haven't tried that yet. Regards Sid.
-- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.
I downloaded from fernel.org kernel 2.6.6, patch TIOCGDEV and patch bk1. I compiled it with Mantel's options and without 4K stacks. Apart the fact that driver sym53C8xx is broken, it works fine and the vvidia.ko module compiles and load. It seems that the new Mantel's kernels use 4K stacks without the option to use 8K stacks. I'll report to him. Michel.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (4)
-
Anders Johansson
-
Catimimi
-
Ivan Sergio Borgonovo
-
Sid Boyce