X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/47a971aed6baf7dadc35c9d1e0a846cc2861695e..6e4cef5be1eb912bb0051f3a210e9bd7496335fd:/blog/index.rss diff --git a/blog/index.rss b/blog/index.rss index 0a36c793af..636b125548 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,37 @@ http://people.skolelinux.org/pere/blog/ + + KDM fail at boot with NVidia cards - and no one try to fix it? + http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html + http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html + Tue, 1 Jun 2010 17:05:00 +0200 + +<p>It is strange to watch how a bug in Debian causing KDM to fail to +start at boot when an NVidia video card is used. The problem seem to +be that the nvidia X.org driver uses a long time to initialize, and +this duration is longer than kdm is configured to wait.</p> + +<p>I came across two bugs related to this issue, +<a href="http://bugs.debian.org/583312">#583312</a> initially filed +against initscripts and passed on to nvidia-glx when it became obvious +that the nvidia drivers were involved, and +<a href="http://bugs.debian.org/524751">#524751</a> initially filed against +kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.</p> + +<p>To me, it seem that no-one is interested in actually solving the +problem nvidia video card owners experience and make sure the Debian +distribution work out of the box for these users. The nvidia driver +maintainers expect kdm to be set up to wait longer, while kdm expect +the nvidia driver maintainers to fix the driver start faster, and +while they wait for each other I guess the users end up switching to a +distribution that work for them. I have no idea what the solution is, +but I am pretty sure that waiting for each other is not it.</p> + +<p>I wonder why we end up handling bugs this way.</p> + + + Parallellized boot seem to hold up well in Debian/testing http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html @@ -460,79 +491,5 @@ change.</p> - - Thoughts on roaming laptop setup for Debian Edu - http://people.skolelinux.org/pere/blog/Thoughts_on_roaming_laptop_setup_for_Debian_Edu.html - http://people.skolelinux.org/pere/blog/Thoughts_on_roaming_laptop_setup_for_Debian_Edu.html - Wed, 28 Apr 2010 20:40:00 +0200 - -<p>For some years now, I have wondered how we should handle laptops in -Debian Edu. The Debian Edu infrastructure is mostly designed to -handle stationary computers, and less suited for computers that come -and go.</p> - -<p>Now I finally believe I have an sensible idea on how to adjust -Debian Edu for laptops, by introducing a new profile for them, for -example called Roaming Workstations. Here are my thought on this. -The setup would consist of the following:</p> - -<ul> - - <li>During installation, the user name of the owner / primary user of - the laptop is requested and a local home directory is set up for - the user, with uid and gid information fetched from the LDAP - server. This allow the user to work also when offline. The - central home directory can be available in a subdirectory on - request, for example mounted via CIFS. It could be mounted - automatically when a user log in while on the Debian Edu network, - and unmounted when the machine is taken away (network down, - hibernate, etc), it can be set up to do automatic mounting on - request (using autofs), or perhaps some GUI button on the desktop - can be used to access it when needed. Perhaps it is enough to use - the fish protocol in KDE?</li> - - <li>Password checking is set up to use LDAP or Kerberos - authentication when the machine is on the Debian Edu network, and - to cache the password for offline checking when the machine unable - to reach the LDAP or Kerberos server. This can be done using - <a href="http://www.padl.com/OSS/pam_ccreds.html">libpam-ccreds</a> - or the Fedora developed - <a href="https://fedoraproject.org/wiki/Features/SSSD">System - Security Services Daemon</a> packages.</li> - - <li>File synchronisation with the central home directory is set up - using a shared directory in both the local and the central home - directory, using unison.</li> - - <li>Printing should be set up to print to all printers broadcasting - their existence on the local network, and should then work out of - the box with CUPS. For sites needing accurate printer quotas, some - system with Kerberos authentication or printing via ssh could be - implemented.</li> - - <li>For users that should have local root access to their laptop, - sudo should be used to allow this to the local user.</li> - - <li>It would be nice if user and group information from LDAP is - cached on the client, but given that there are entries for the - local user and primary group in /etc/, it should not be needed.</li> - -</ul> - -<p>I believe all the pieces to implement this are in Debian/testing at -the moment. If we work quickly, we should be able to get this ready -in time for the Squeeze release to freeze. Some of the pieces need -tweaking, like libpam-ccreds should get support for pam-auth-update -(<a href="http://bugs.debian.org/566718">#566718</a>) and nslcd (or -perhaps debian-edu-config) should get some integration code to stop -its daemon when the LDAP server is unavailable to avoid long timeouts -when disconnected from the net. If we get Kerberos enabled, we need -to make sure we avoid long timeouts there too.</p> - -<p>If you want to help out with implementing this for Debian Edu, -please contact us on debian-edu@lists.debian.org.</p> - - -