Right. I copied my desktop .config to the tosh, edited it for IDE controller, AGP, ethernet, touchpad and NTFS support, recompiled and just like that: it works! I still don't know what the problem was, though the front-runner would have to be the register arguments stuff. Still, right at this moment, I don't care enough to go fishing for evidence.

@Gentree, thanks again for the help._________________Don't let THEM immanentize the Eschaton!

Interesting that reg args did not give apparent pbs. I was only going from the help on this item:

Code:

CONFIG_REGPARM:
x Compile the kernel with -mregparm=3. This uses an different ABI x
x and passes the first three arguments of a function call in registers. x
x This will probably break binary only modules.

I just recompiled with regargs on: the only thing I did change. Did the nv remake as well , I rebooted and I was back to square one with exactly the same error from the nvidia driver not managing to initialise.

I reversed the step and I am back up with nVidia.

Without a doubt this is what has been stuffing my system for the last 10 days.

A case of a bridge too far in the optimisation stakes.

Quote:

mmm... I looked at that when I took it out and I must admit, I wondered how my desktop machine had ever worked. However:

Well this seems to be a "may break" rather than "will break" . I had turboprint and Opera on this system for a while both of which also contain binaries and this had no pb with regparm.

Fairly obviously it will depend on what the binary does and how its coded.

What does seem odd (if I understand your last post) is that your Tosh now seems happy to run nvidia with this option on ! Beats me.

Anyway , I'm running , you're running and some cleaver bugger who actually understands this rather than using empirical guess work will later tell us why.

In the meantime this is all off-topic since it turns out to be nothing to do with love-sources other than to confirm , once again , how good they are.

I will try to gather my thoughts and post a howto, since there was little help in finding this issue and it may save a lot of people some time to gather the threads together.

Love has win4lin in it - it works fine here (they have been using the 2.6.5 win4lin patches and so they might want the updated ones for the next love release).

Love has had them for a couple of releases now, have you tried this latest version? Apart from that, if you want to do it by hand, there were a few rejects that needed sorting out by hand but now all that hassle has been taken away by OneofOne and Steel.

Let us know some more details if its not working properly in this release as it should do and does here

I just now got it up and running. It was the first chance I had to reboot. Win4Lin works great. The only thing that didn't work was the nvidia. I'll have to see what is going on with that. I'm running using "nv" right now.

It's extremely hard for the /proc/splash to be created if there's no "splash_init();" in fbcon.c and it's missing in the 2.6.6-love1 sources

Did you perhaps miss that there are 3 hunks which fail to apply to fbcon.c and need to be adjusted? the first and third hunks appear to be easy to adjust, the middle hunk in the "if (resize) {" block worries me since that code section was redone in mm.

Note: This does provide the initial bootsplash, but the text problem in verbose mode with the scroll area not being properly setup on for boot messages (same as in the 2.6.6-rc releases) is still there. The /etc/init.d/bootsplash setting that happens much later does clear this up properly. silent mode appears to be working.

As always this works here, but no promises it won't blow up your computer, cause cancer, etc.

Time to do more hunting but I've had limited access to the test machine to try new patches.

For completeness sake just in case someone can't use 2.6.6-love2 or newer.

bootsplash fix for improperly sized verbose mode (you still need to apply the patch above to get bootsplash working in 2.6.6-love1). This should apply to the 2.6.6-rc versions which had the wrong size as well if someone still needs to use those.