From: cfajohnson@gmail.com   
      
   On 2012-12-22, unruh wrote:   
   > On 2012-12-22, herman.viaene@invalid.be.invalid  wrote:   
   >> unruh wrote:   
   >>   
   >>> This does not answer your question, but if stuff like this happens, kill   
   >>> of the /etc/rc5.d/ file for the IVTV so you can boot up.  You can always   
   >>> run it later. where you can at least look at its error messages.   
   >>> If this problem is happening before the init.d files are being processed   
   >>> (ie theones that list with OK on the bootup) then remove that file from   
   >>> the module loading (/etc/modprobe.conf?) and load the module afterwards.   
   >>> Reinstalling the whole operating system because one component misbehaves   
   >>> should not be necessary ( unless it is a hard drive say)   
   >>   
   >> Your advice might be helpfull in many ways, but in my case I don't believe   
   >> it would do any good. Mind you, I won't repeat the whole experience to prove   
   >> it.   
   >> Why do I think so? Because the hanging of the boot happens very quickly,   
   >> after - I guess - less than 20 seconds. Isn't that too quickly to be in that   
   >> stage of the process already?   
   >   
   > Nope. The modern Linux kernels get into that stage very quickly.   
   > Certainly less than 20 sec on my systems. IF you can get it to boot   
   > without that stupid splash screen, you could see where it is in the boot   
   > sequence. (I neer did understand the desire to have all of that stuff   
   > hidden from view.)   
      
     As it says on the splash screen, "Press ESC for verbose mode" (or   
     words to that effect).   
      
   --   
      Chris F.A. Johnson,    
      Author:   
      Pro Bash Programming: Scripting the GNU/Linux Shell (2009, Apress)   
      Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)