Hi there!
I wonder if anyone can help me with the problem I'm having during boot of 8.10 Standard. The system takes rather a long time to boot up. For completeness of information The unit was originally Xandros powered. When I had problems with my huawei modem I reformatted the disks and installed xp to get over a pressing need. After that was over I started trying with eeebuntu. And I decided to reformat everything for a clean reinstall. I reloaded Windows since I understand it needs to go in first in a dual boot install. The eee900 now has XP loaded and had a guided installation of 8.10 using the remaining 13Gb partition of the 16Gb SSD for a dual boot. On power up the grub screen comes up OK, select 8.10 and the splash screen is seen. As the load progresses to about 90% the display changes to terminal messages. The last thing that has executed successfully is the disk temperature monitor daemon. The next message, that vanishes rather quickly is ata2.01: Exception EMASK 0x0 and a lot more that I can't read including the ominous LOCKED . Eventually the screen blanks and the desktop appears as expected. As far as I can see everything works except for some of the items like wifi toggling noted by other people. The only real issue is the startup time.

So the first thing is: Can anybody tell me how to enable boot logging since by default it appears to be off. Then maybe I can get more information about the exact problems. Is it possible that the formatting is causing this?

Any and all help will be gratefully received.

Doug Duncan eee900 , 8.10 - BIOS 0906, 1 Gb memory

I have te same problem.. has this something todo with acpi?

I have the EEE PC 900 Black, 4GB SDD and 16 GB SDD (I install on the 16GB SSD, and i get the error on that one, sdb)

I am having the same exact issue.

eee pc 1000 - 2gb RAM

I have it too. Figured it was the way t was supposed to boot.

I'm also getting this problem on my eeepc 901... plus my brightness adjustment buttons aren't working.. but it's possible I may have brokenn that by re-running the eeeconfigure stuff

If it can help, I think that this poblem also happened during the first installation boot with the SD card (for the installation of eeebuntu) on my eeeC 900.
First time I saw briefly the "exception emak" error message ...
I hope that this issue will be solved soon as it is very anoying to loose so much time during the boot ...
I also noted that the problem and boot time was even bigger/longer after the use of eeebuntu config !

That one is the problem. Disable the disk temperature monitor daemon and your problem should be solved. Worked for me on my 901go. The flash disk seems to have no temperature sensor and might not even implement the command to read it to fail gracefully. Would explain the exception and the short hang during boot.

The commands I used.



A bit of a hack, but it solved the issue for me.

I also removed the 'quiet splash' from the grub entry for the kernel in /boot/grub/menu.lst since I like the see the console messages at boot time.

Hope this helps

Tes

Hi
I've the same problem with my eeepc 901.
I've tried your hack for the disk temperature monitor daemon, but now i can't boot my system. When i try to boot my system i've this message :



What can I do ?

Hm, you must have made a typo since my hack only renames the link that starts the hddtemp-daemon so it's not found anymore. It should not give you the above message and also not become unbootable. The question is which file it cannot find anymore. Any more console messages that might be helpful?

Try to boot the system from the install media. Since it's a live CD (or USB-stick), you should be able to open a Terminal and mount the internal flash drive (The 901 has 2 of them as far as I know, usually sda and sdb with the OS on sda). Do not start the installer! When using a live CD, the internal drive might have shifted to 'sdb'. Might work along those lines if it's sdb:



This should let you take a look at what happened with the start links.

Another possibility is to try to boot the system into single user mode using the 'recovery' entry in the GRUB menu and then fix things from there. Press ESC at the right moment in the boot process and you should get that menu. I prefer the boot from the install/live media, better interface.

Tes (eeePC901go, 2GB RAM, no swap, eeebuntu 2.0 Standard)

Worked perfectly for me! Thanks Tes!

I have treid both ways and i get the error that the file direcotry does not exist. Do i erase the quiet splash if i want to see terminal messages or do not want to see terminal messages.
Cuz at the moment i still get a bunch.

if you remove 'quiet splash' in the menu.lst, you will see all console messages. That is what I prefer over the splash screen with the progress bar. But even with the splash screen in place, you will see the messages if the systems hangs or pauses too long during the boot process.

Back to your problem. Without knowing what file it tries to find and can't, it will be close to impossible to help you unfortunatly. If you enable the console messages (means removing the 'quiet splash'), what are the last messages you see before it stops booting?

Tes

How can I change my boot up so I don't see all the messages? I would much rather see the progress bar.

That behaviour should be the default. Unless you didn't disable the hddtemp-daemon yet, then you will see some messages scroll by and experience a pause. I described how to disable that daemon in another post in this thread.

Tes

No no no. It boots fine. It takes about a minute and a half. I see the eeebuntu spash screen for a bit, then i see the console messages which are somewhat along the lines of:

Updating System Clock [OK]

etc...

How long does it take you to boot?
Im not surre if it is normal to see what im seeing after the eeebuntu splash screen. But i did see these console messages when running ububuntu 8.04 but that was only for the first reboot of the system.