just installed Mint 7 on my IBM Thinkpad. Except for one thing everything works well:When I boot the machine, it hangs for about 170 seconds when it registers the internal Trackpoint. After that, the boot continues very fast. Seems like there is a problem with my trackpoint. I already tried to remove my USB mouse in case this confuses the kernel somehow, but this had no effect.

I also generated a bootchart, but I have to admit that I'n not able to correlate that with my dmesg output; but maybe this helps somehow.For me that is very annoying, because if one would subtract that 'delay', the system would boot very fast.

Anyone else with that problem? What could I do?

Thanks,Regards, vbmazter

Attachments

bootchart

libertad-Gloria-20090704-1.png (109.7 KiB) Viewed 928 times

Last edited by vbmazter on Sun Jul 12, 2009 7:02 am, edited 1 time in total.

Sure, if you think it might be the parallel port or serial port, just disable them in the bios of the notebook..http://ubuntuforums.org/showthread.php?t=680762post #3--yes turn of the splash, so you can see the boot sequence on the screen, gives you a console view of the load/boot; you should be able to see which item is taking the longer times..

You can also, and be careful here, checking the names and descriptions

Remove applications you don't use--Bluetooth, if you have no bluetooth devices

Some Services--you can install rcconf, and alter the startup of various services on boot

Last edited by DrHu on Tue Jul 21, 2009 5:12 am, edited 1 time in total.

DrHu wrote:--you don't mention the Thinkpad model #: different versions have different hardware..

Mine it's a T61p (6457-AN9)

DrHu wrote:Sure, if you think it might be the parallel port or serial port, just disable them in the bios of the notebook..

Did this and it's still hanging...

DrHu wrote:--yes turn of the splash, so you can see the boot sequence on the screen, or enter ctrl alt F1, while booting for the same result, gives you a console view of the load/boot; you should be able to see which item is taking the longer times..

That is not as good as watching the data as the system boots to see which is the slowest device to be enabled/activated, whether it is a wireless or network card searching for a connection, or a hard drive that is full and slow to boot, or some device that sticks and is enabled later in the Linux OS boot

You also usually have the option in the bios of letting the bios decide how to active/enable/control the system or using Plug & play mode and letting the Linux OS try to fix any problems uit detects on the system, while devices are started

lunatico wrote:So this means that turning off parallel on the bios did changed something..[ 189.350305] Adding 1927760k swap on /dev/sda6. Priority:-1 extents:1 across:1927760k

in the meantime, I tried a few things. First I wanted to figure out more exactly what bootviz is showing. If I'm interpreting the output correctly, udev causes the delay. But - of course - it's an underlying function what might block.

So I turned on udev's debug output (look in /etc/udev/udev.conf ...it's described there).

Surprise: The delay is visible in the udev log, too (/var/log/udev, look at the time stamps)!:

So either the delay is in serio2, or its in that funny "i2c-adaptor" (anyway...where do I have such a device?! Maybe something internal on the mainboard, I guess). Eww...that adaptor...just to mention...has "pci" as parent. So maybe someone could tell me what it does.

Then I tried to add some rules to /etc/udev/rules.d/, in order to ignore both devices. Testing with udevadm I was told, that I2c and serio will be ignored. So, highly motivated, I did another reboot.

NO SUCCESS.

Know what? Udev still adds the devices, but just ignores the events. What implies, that the "answering" of one of the devices causes that delay. Unfortunately I have no options in my BIOS to disable both (what seems normal to me).

Someone might state that I did useless things here. In that case, I would appreciate any suggestions which might help.