[Pkg-sysvinit-devel] Bug#583312: Bug#583312: possible fix

[Romane]

Good morning Petter

I must thank you for your patience.
> As far as I know, changing the sequence number of a script will not
> affect parallel booting.  Did you use S7nvidia-glx or S07nvidia-glx?
> If the former, I suspect this caused the script to not run at all
> during boot.  I suspect there is some race issue causing some but not
> all boots to fail.
>    
Time has proven you correct, and my approach a failure anyways (hangs 
head). I had used S7, but even changing it to S07 made no difference. 
Back now to what it started at - S17nvidia-glx. Basically, whatever went 
right earlier on is now not going right; back to being dropped to the 
console.
> Btw, what is the name of the package providing /etc/init.d/nvidia-glx
> on your machine (dpkg -S /etc/init.d/nvidia-glx).
$ dpkg -S /etc/init.d/nvidia-glx
nvidia-glx: /etc/init.d/nvidia-glx

Installed from the repositories, but drivers downloaded from nVidia are 
affected also.
> Please try the adjusted header for nvidia-glx I posted earlier, and
> let me know if it helps.
Made that change, and no change to the boot issue. Rebooted a number of 
times, to make sure not a one-off.

So far, only thing that seems to get me through is to make that change 
mentioned in my earlier email to /etc/kde4/kdm/kdmrc with a timeout 
value of 120. After my earlier overconfident assurance that had possibly 
found a solution, won't say that have it fixed, but over the test boots 
just now done, each boot was successful at getting to the login screen. 
The time from when the screen goes blank to when am presented with the 
logon screen varies from 15 to 18 seconds (give or take). Before, it was 
tossing me to the console after about 12 to 15 seconds (give or take). 
On those grounds, at least things seem to be working, even if not as 
they should :) I have read in my searches that making this change is not 
the preferred method, but ... - I can also make a coffee while I wait 
(laughing).

Have another machine which have been holding off making this update to. 
Took the plunge a little earlier, and it came up on the first boot. Also 
an nVidia card. My 3 machines are always set up identically - can hop 
from one to the other without having to remember which machine am 
sitting at - different hardware, but same system otherwise. So, not a 
consistent issue, as you suggested in your reply to me. The third 
machine is not affected - ATI, not using proprietary drivers.

I have reached the end of my own options and limited knowledge (getting 
old and forgetful :)), but am most happy to use this machine to debug 
the issue with you if that will help improve further an already supurb 
distribution. Crashing it is not an issue - worst comes to worst, can 
reformat, reinstall (grinning).

Have babbled sufficient for now

> Happy hacking,
>    
With greetings

Romane