Welcome, Guest. Please login or register.
April 19, 2014, 01:28:15 AM
Home Help Search Calendar Login Register
Show unread posts since last visit.
News: Let Pardus-Anka become #1: Pardus-Anka Bug ReportPardus-Anka World Google+ | The Pardus wiki  | Visit Pardus-Anka official website  | Register as forum member?  Email the moderator!

+  Pardus Worldforum
|-+  Assistance
| |-+  Laptop
| | |-+  [solved]Pardus 2008 always hangs 3 min on booting
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: [solved]Pardus 2008 always hangs 3 min on booting  (Read 1510 times)
william5
Newbie
*
Posts: 28


View Profile
« on: July 05, 2008, 17:22:12 PM »

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
======
« Last Edit: July 05, 2008, 21:54:37 PM by Andreas » Logged
PhiX
Pardus Guru
****
Posts: 642



View Profile WWW
« Reply #1 on: July 05, 2008, 18:04:59 PM »

"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.
Logged

Team Pardus-fr - French Pardus tools translator
william5
Newbie
*
Posts: 28


View Profile
« Reply #2 on: July 05, 2008, 18:35:04 PM »

"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:

Quote
/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
======



« Last Edit: July 05, 2008, 18:39:51 PM by Andreas » Logged
Andreas
Guest
« Reply #3 on: July 05, 2008, 18:42:48 PM »

@wiliam5,

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

That is more clearly. Wink

Greetings
Andreas
Logged
PhiX
Pardus Guru
****
Posts: 642



View Profile WWW
« Reply #4 on: July 05, 2008, 19:54:36 PM »

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

Team Pardus-fr - French Pardus tools translator
william5
Newbie
*
Posts: 28


View Profile
« Reply #5 on: July 05, 2008, 20:27:58 PM »

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
======   
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  


Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!