Sluggish bootup.

Antonio Augusto (Mancha) mkhaos7 at gmail.com
Wed Apr 29 00:53:49 UTC 2009


On Tue, Apr 28, 2009 at 18:21, Steven Vollom <stevenvollom at sbcglobal.net> wrote:
>
>> Steven,
>> I think something is wrong with your mail client. The bootchart.png
>> that you sent was cuted, and showed only one little piece of the
>> image.
>> Try to send it again please.
>>
>> Cheers
>
> After clicking on restart, this is what took place to get a screen again.
>
> I clicked on restart at approximately 1:35 in the afternoon.  I waited with a
> black screen for 25 minutes to see if it would restart without help.  It
> wouldn't.  The reason for the delay is I decided to take a shower while I
> waited and didn't get back until 25 minutes to find the selfsame black screen
> prior to restart.
>
> I held the off button until the system turned off.  I waited about 10 seconds
> then turned it on again.
>
> Boot proceeded until the following was on the screen then paused:
>
> [  1.504346] ACPI expecting a preference[ package element, found type 0.
>
> I allowed it to sit with a blinking cursor until 2:04 before accepting the
> fact that it was stalled again and not just working behind the scene.
> Sometimes when I tap the space bar, it will resume.  I tapped it 4 times and
> nothing happened.  I pressed Crtl+Alt+Del and nothing happened.  I pressed the
> Off Switch, and instead of turning off, the boot resumed.
>
> The window that has the word Kubuntu with the thin progress bar appeared and
> showed progress to about 3/4 of an inch and paused.  I pressed the space bar
> and it resumed to about 1 1/4 inch and paused again.  I pressed thespace bar
> to get it to resume boot again.  It was not 2:07.  At about 1 1/2 inch the bar
> paused again, and I made it resume by pressing the space bar.
>
> The progress bar then proceeded rapidly to the end and the screen went blank
> and paused again.  At 2:08 I pressed the space bar an the boot resumed but
> stopped with the following window showing:  Uuntu is running in low-graphics
> mode.   Your screen, graphics card, and input device setings could not be
> detected correctly.  You will  need to configure these yourself.  I pressed OK
> to get the next instruction:  what would you like to do:
>
> X       Run Ubuntu in low graphics mode for just one session.
>        Reconfigure graphics
>        Trouble shoot the error
>        Exit to console again
>
> Stand by one minute while display restarts.  I chose the Run Ubuntu...... as
> indicated by the X, because I would not know what to do with the other choices
> anyway.
>
> Finally I got a new screen with numerous repetitive statements that only
> changed the number in the range shown:  It said the following:
>
> Warning:  Invalid uptime 330760      Ignoring sample.
> (the line repeated the full screen with the number changing on each line until
> it came to 331120).  Then it printed the following statement:
>
> Wrote image:  /var/log/bootchart/Yeshua-Jaunty- 20090428-.png.  It paused
> there again, so I pressed Ctrl+Alt+Del and it rebooted.  This time when it
> came to the pause points I pressed the appropriate space bar or off key to
> reduce the pauses.  It passed through the boot process this time and came to a
> workng screen again.  Several plasmoids did not work, but I was able to remove
> and reinstall and reprogram them and get them to work.  I am writing this
> email from the same computer that has the problem, right now.
>
> The Bootchart that you see is the one that was made when I was at that last
> point prior to pause without resume, then reboot to open system.
>
> Sorry about the long winded reply, but I had to write it all long hand to keep
> an accurate record of what I was doing.  I did not have access to copy and
> paste or a typewriter.
>
> I would like to say that I downloaded the Jaunty Rc, and formatted prior to
> installation, just to be sure the installation would be perfect.  I had the
> copy application verify that I had a perfect copy too.  Still installation was
> a little difficult.
>
> There is a comment that needs to be added into the boot sequence that I cannot
> remember how to do.  It is the inclusion of the term pci=nomsi.  I believe it
> is special for my graphics card and motherboard chip, I just can't remember,
> but it not being installed may be the heart of all my problems.  Until I get
> some help to put the comment in the correct place, I can do nothing.  I prefer
> not reinstalling if you can not help me.  I would like to add the comment
> first.  I just have to find out how, with an explanation that I can understand
> and then execute.  I hope you have experience in this area.
>
> I believe that this is the reason I was forced to use the Alpha and then Beta
> Jaunty applications while ill prepaired for what that involves, nonetheless,
> my motherboard is a bit high tech, and the Video card is fairly current
> technology requiring different treatment in the Kubuntu development package.
>
> Booting involves loosing plasmoids and having to re-establish them, which is a
> bit of a pain, but I am willing to try again with the bootchart feature if
> that is what you recommend; I believe we will get the same results though.
>
> When I was in the Alpha and Beta stages of Jaunty, my computer worked
> brilliantly except for a couple of non essential glitches that were fixed in
> the Rc, so I have been more than satisfied up until now.  It has been less
> problematic that all the apps from Feisty on until Jaunty.  I love the program
> and want to get my computer stabilized not change to another OS.  It wouldn't
> work anyway, because of my motherboard and processor, the amount of memory I
> am running, and the nVidia video card.  These are why Jaunty is required for
> my computer to work, unless I return to that dinosaur Vista.  I would rather
> live through the problems I have than do that.
>
> Steven

I had this kind of problem sometime ago, but i don't remember if this
was on a real machine or on a VM, and i don't really remember how i
got it fixed (if I got).
Anyways... your problem seens related to acpi. Yesterday there was a
upgrade for it, try upgrading it to see if this solves your issues.

Another option you can try is passsing noacpi as a parameter to your kernel.
To known how to get this take a look here:
https://help.ubuntu.com/community/GrubHowto#Setting%20kernel%20parameters

any doubts ask around :)

Cheers




More information about the kubuntu-users mailing list