[solved]Pardus 2008 always hangs 3 min on booting

[william5]

Hi,

I run Pardus 2008 on a Fujitsu Lifebook laptop. Everything works great (wireless, printing, sound, video, dual monitors, etc.). It is absolutely a fantastic Linux distro (and I have tried quite a few). The only issue that is annoying is that during boot-up the systems hangs for about 3 min. Alt-F2 shows that it is working on "populating /dev". I does that every time I start the system. I am not sure that I understand what that means. Identifying my hardware? Is there a way to accelerate this process?   

william5
======

[PhiX]

"populating /dev" means creating the device files related to the hardware components of your laptop.

Look in the following log files with Konqueror, you may find some clue (error messages) : /var/log/messages, /var/log/syslog, /var/log/mudur.log. Give us a copy of today's logs.

[william5]

"populating /dev" means creating the device files related to the hardware components of your laptop.

Look in the following log files with Konqueror, you may find some clue (error messages) : /var/log/messages, /var/log/syslog, /var/log/mudur.log. Give us a copy of today's logs.

Here they are:

/var/log/messages:

driverbyte=DRIVER_OK,SUGGEST_OK
Jul  5 12:28:09 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul  5 12:28:09 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
Jul  5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] READ CAPACITY failed
Jul  5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul  5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul  5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
Jul  5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] READ CAPACITY failed
Jul  5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul  5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul  5 12:28:11 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off

/var/log/syslog:

Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] READ CAPACITY failed
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Mode Sense: 00 00 00 00
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Asking for cache data failed
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Assuming drive cache: write through
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] READ CAPACITY failed
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Sense not available.
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Write Protect is off
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Mode Sense: 00 00 00 00
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Asking for cache data failed
Jul  5 12:29:41 localhost klogd: sd 7:0:0:0: [sdd] Assuming drive cache: write through

/var/log/mudur.log:

Jul 05 04:13:03 (up 9.44) /sbin/mudur.py sysinit
Jul 05 08:15:54 (up 179.98) /sbin/mudur.py boot
Jul 05 08:15:55 (up 181.00) /sbin/mudur.py default
Jul 05 09:23:28 (up 9.44) /sbin/mudur.py sysinit
Jul 05 13:26:18 (up 179.63) /sbin/mudur.py boot
Jul 05 13:26:19 (up 180.51) /sbin/mudur.py default
Jul 05 10:56:37 (up 5610.92) /sbin/mudur.py reboot
Jul 05 06:57:43 (up 9.44) /sbin/mudur.py sysinit
Jul 05 11:00:33 (up 179.76) /sbin/mudur.py boot
Jul 05 11:00:34 (up 180.61) /sbin/mudur.py default

william5
======

[Andreas]

@wiliam5,

I set your output of var/log/messages in a "Quode-Block".

That is more clearly.

Greetings
Andreas

[PhiX]

It looks like the kernel has a problem with your laptop's card reader. Maybe the BIOS allows you to disable it ?

[william5]

It looks like the kernel has a problem with your laptop's card reader. Maybe the BIOS allows you to disable it ?

PhiX:

You are absolutely right! I checked the boot time by eliminating all my external drives one by one. I have an external hard drive, a CF drive, an SD drive and a flash drive typically connected. When I disengaged the CF drive, the delay in booting was gone and it booted fast. This CF drive is not seen by the system, whether I boot with it or not. This is remarkable as some other distros (Ubuntu, PCLinuxOS) that I have, do see the CF drive. PCLinuxOS does not see the SD drive, on the other hand.

I consider this problem solved, as I really do not need the CF drive. Thanks.

william5
======