computer takes ages to start-up... problem unknown

Questions about hardware,drivers and peripherals
Forum rules
Before you post please read how to get help
Post Reply
User avatar
Enna
Level 2
Level 2
Posts: 96
Joined: Sun Sep 12, 2010 1:34 am

computer takes ages to start-up... problem unknown

Post by Enna »

Hi everyone,

hope this is the right place to post my question:
When turning on my laptop, nothing happens on the screen, only waiting for maybe half a night or so, it will be ready to use.
I already declared the laptop for dead, but I tried turning it on again and forgot about it after 15 minutes, I just left it running and this morning, laptop was on and ready to use (in fact all fine now using it, only I will not turn it off because would like to fix problem first, if possible).
Is this a kernel issue?
Laptop model: ASUS KD 70AD
Linux Mint 15 Olivia / 64-bit / Cinnamon

Thanks for help!
Enna
Linux Mint 15 Olivia / 64-bit / Cinnamon
User avatar
karlchen
Level 21
Level 21
Posts: 13829
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: computer takes ages to start-up... problem unknown

Post by karlchen »

Hello, Enna.

Actually, the reason might be anything. Cannot tell.
Yet, here is a way of starting to find out:
  • Make sure your wrist watch and your Linux Mint 15 agree on the exact time.
  • Then reboot your machine.
  • Note down the time when your machine starts rebooting, i.e. when the Bios splash screen appears.
  • Later on, when you have managed to logon, launch the "Log File Viewer" from the menu. Or run the command gnome-system-log.
  • Inside the log file viewer go to the logfile syslog.
  • Press <Ctrl>f and look for the string "Command line: BOOT_IMAGE=/boot/vmlinuz" without the double quotes.
  • Make sure you find the occurence of this string that has been logged after you rebooted the machine.
  • How much time has passed between the Bios splash screen and this line?
  • Now scroll slowly down the lines. Each line has got a very precise timestamp.
  • Are there any obvious gaps? Gaps where it looks like the machine has been doing nothing?
  • If you like you might also post the complete syslog file for inspection.
    Yet, you cannot post it in the forum directly, because it may be too large. But you can upload it to http://www.pastebin.com and post the link to your syslog file here.
Kind regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Good Company
User avatar
Enna
Level 2
Level 2
Posts: 96
Joined: Sun Sep 12, 2010 1:34 am

Re: computer takes ages to start-up... problem unknown

Post by Enna »

Thank you for your fast reply!
I don't want to restart the computer now, because I fear that it doesn't start up again... can you make sense out of thes Log File? The last two times that I restarted the computer, it took 15+ to be ready to use, with a blank screen until it was ready.
Here is the Log File output(it's in German, hope it'll make sense to you):

Dec 31 08:04:33 Mnema rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1008" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Dec 31 08:04:33 Mnema anacron[3573]: Job `cron.daily' terminated
Dec 31 08:04:33 Mnema anacron[3573]: Normal exit (1 job run)
Dec 31 08:17:01 Mnema CRON[3922]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> (wlan0): bringing up device.
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> WiFi hardware radio set enabled
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> WiFi now enabled by radio killswitch
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> (wlan0): bringing up device.
Dec 31 08:23:09 Mnema kernel: [38078.472897] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 31 08:23:09 Mnema dbus[1002]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper)
Dec 31 08:23:09 Mnema dbus[1002]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> wpa_supplicant started
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> (wlan0) supports 4 scan SSIDs
Dec 31 08:23:09 Mnema NetworkManager[1088]: <warn> Trying to remove a non-existant call id.
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: starting -> ready
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: ready -> inactive
Dec 31 08:23:09 Mnema NetworkManager[1088]: <info> (wlan0) supports 4 scan SSIDs
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Auto-activating connection 'Automatisch Mnemosyne'.
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Activation (wlan0) starting connection 'Automatisch Mnemosyne'
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> (wlan0): preparing device.
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Activation (wlan0/wireless): connection 'Automatisch Mnemosyne' has security, and secrets exist. No new secrets needed.
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Config: added 'ssid' value 'Mnemosyne'
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Config: added 'scan_ssid' value '1'
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Config: added 'auth_alg' value 'OPEN'
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Config: added 'psk' value '<omitted>'
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> Config: set interface ap_scan to 1
Dec 31 08:23:10 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: inactive -> scanning
Dec 31 08:23:11 Mnema kernel: [38080.575071] wlan0: authenticate with 72:c0:6f:6b:59:f8
Dec 31 08:23:11 Mnema wpa_supplicant[4038]: wlan0: SME: Trying to authenticate with 72:c0:6f:6b:59:f8 (SSID='Mnemosyne' freq=2417 MHz)
Dec 31 08:23:11 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec 31 08:23:11 Mnema kernel: [38080.584829] wlan0: send auth to 72:c0:6f:6b:59:f8 (try 1/3)
Dec 31 08:23:11 Mnema wpa_supplicant[4038]: wlan0: Trying to associate with 72:c0:6f:6b:59:f8 (SSID='Mnemosyne' freq=2417 MHz)
Dec 31 08:23:11 Mnema kernel: [38080.589764] wlan0: authenticated
Dec 31 08:23:11 Mnema kernel: [38080.591584] wlan0: associate with 72:c0:6f:6b:59:f8 (try 1/3)
Dec 31 08:23:11 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dec 31 08:23:11 Mnema wpa_supplicant[4038]: wlan0: Associated with 72:c0:6f:6b:59:f8
Dec 31 08:23:11 Mnema kernel: [38080.596157] wlan0: RX AssocResp from 72:c0:6f:6b:59:f8 (capab=0x411 status=0 aid=1)
Dec 31 08:23:11 Mnema kernel: [38080.596287] wlan0: associated
Dec 31 08:23:11 Mnema kernel: [38080.596357] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 31 08:23:11 Mnema kernel: [38080.596474] cfg80211: Calling CRDA for country: ES
Dec 31 08:23:11 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: associating -> associated
Dec 31 08:23:11 Mnema kernel: [38080.607025] ath: regdomain 0x82d4 updated by CountryIE
Dec 31 08:23:11 Mnema kernel: [38080.607034] ath: EEPROM regdomain: 0x82d4
Dec 31 08:23:11 Mnema kernel: [38080.607039] ath: EEPROM indicates we should expect a country code
Dec 31 08:23:11 Mnema kernel: [38080.607044] ath: doing EEPROM country->regdmn map search
Dec 31 08:23:11 Mnema kernel: [38080.607049] ath: country maps to regdmn code: 0x37
Dec 31 08:23:11 Mnema kernel: [38080.607053] ath: Country alpha2 being used: ES
Dec 31 08:23:11 Mnema kernel: [38080.607056] ath: Regpair used: 0x37
Dec 31 08:23:11 Mnema kernel: [38080.607099] cfg80211: Regulatory domain changed to country: ES
Dec 31 08:23:11 Mnema kernel: [38080.607102] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec 31 08:23:11 Mnema kernel: [38080.607108] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Dec 31 08:23:11 Mnema kernel: [38080.607112] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Dec 31 08:23:11 Mnema kernel: [38080.607117] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Dec 31 08:23:11 Mnema kernel: [38080.607121] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Dec 31 08:23:12 Mnema wpa_supplicant[4038]: wlan0: WPA: Key negotiation completed with 72:c0:6f:6b:59:f8 [PTK=CCMP GTK=TKIP]
Dec 31 08:23:12 Mnema wpa_supplicant[4038]: wlan0: CTRL-EVENT-CONNECTED - Connection to 72:c0:6f:6b:59:f8 completed (auth) [id=0 id_str=]
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Mnemosyne'.
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> dhclient started with pid 4042
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> Activation (wlan0) Beginning IP6 addrconf.
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec 31 08:23:12 Mnema dhclient: Internet Systems Consortium DHCP Client 4.2.4
Dec 31 08:23:12 Mnema dhclient: Copyright 2004-2012 Internet Systems Consortium.
Dec 31 08:23:12 Mnema dhclient: All rights reserved.
Dec 31 08:23:12 Mnema dhclient: For info, please visit https://www.isc.org/software/dhcp/
Dec 31 08:23:12 Mnema dhclient:
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Dec 31 08:23:12 Mnema dhclient: Listening on LPF/wlan0/00:25:d3:ff:ee:af
Dec 31 08:23:12 Mnema dhclient: Sending on LPF/wlan0/00:25:d3:ff:ee:af
Dec 31 08:23:12 Mnema dhclient: Sending on Socket/fallback
Dec 31 08:23:12 Mnema dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x4d294f98)
Dec 31 08:23:12 Mnema dhclient: DHCPREQUEST of 192.168.1.2 on wlan0 to 255.255.255.255 port 67 (xid=0x4d294f98)
Dec 31 08:23:12 Mnema dhclient: DHCPOFFER of 192.168.1.2 from 192.168.1.1
Dec 31 08:23:12 Mnema dhclient: DHCPACK of 192.168.1.2 from 192.168.1.1
Dec 31 08:23:12 Mnema dhclient: bound to 192.168.1.2 -- renewal in 39147 seconds.
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> address 192.168.1.2
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> prefix 24 (255.255.255.0)
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> gateway 192.168.1.1
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> nameserver '192.168.1.1'
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> nameserver '192.168.1.1'
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> domain name 'localdomain'
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dec 31 08:23:12 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Dec 31 08:23:12 Mnema avahi-daemon[1053]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.2.
Dec 31 08:23:12 Mnema avahi-daemon[1053]: New relevant interface wlan0.IPv4 for mDNS.
Dec 31 08:23:12 Mnema avahi-daemon[1053]: Registering new address record for 192.168.1.2 on wlan0.IPv4.
Dec 31 08:23:13 Mnema avahi-daemon[1053]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::225:d3ff:feff:eeaf.
Dec 31 08:23:13 Mnema avahi-daemon[1053]: New relevant interface wlan0.IPv6 for mDNS.
Dec 31 08:23:13 Mnema avahi-daemon[1053]: Registering new address record for fe80::225:d3ff:feff:eeaf on wlan0.*.
Dec 31 08:23:13 Mnema NetworkManager[1088]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Dec 31 08:23:13 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Dec 31 08:23:13 Mnema NetworkManager[1088]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dec 31 08:23:13 Mnema NetworkManager[1088]: <info> Policy set 'Automatisch Mnemosyne' (wlan0) as default for IPv4 routing and DNS.
Dec 31 08:23:13 Mnema NetworkManager[1088]: <info> DNS: starting dnsmasq...
Dec 31 08:23:13 Mnema NetworkManager[1088]: <warn> dnsmasq not available on the bus, can't update servers.
Dec 31 08:23:13 Mnema NetworkManager[1088]: <error> [1388431393.876989] [nm-dns-dnsmasq.c:402] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name
Dec 31 08:23:13 Mnema NetworkManager[1088]: <warn> DNS: plugin dnsmasq update failed
Dec 31 08:23:13 Mnema NetworkManager[1088]: <info> Writing DNS information to /sbin/resolvconf
Dec 31 08:23:13 Mnema dnsmasq[4046]: Gestartet, Version 2.65 Cache deaktiviert
Dec 31 08:23:13 Mnema dnsmasq[4046]: Übersetzungsoptionen: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack
Dec 31 08:23:13 Mnema dnsmasq[4046]: DBus-Unterstützung eingeschaltet: mit Systembus verbunden
Dec 31 08:23:13 Mnema dnsmasq[4046]: Warnung: keine vorgelagerten (Upstream) Server konfiguriert
Dec 31 08:23:14 Mnema NetworkManager[1088]: <info> Activation (wlan0) successful, device activated.
Dec 31 08:23:14 Mnema dbus[1002]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 31 08:23:14 Mnema NetworkManager[1088]: <warn> dnsmasq appeared on DBus: :1.45
Dec 31 08:23:14 Mnema dnsmasq[4046]: vorgelagerte Server von DBus gesetzt
Dec 31 08:23:14 Mnema dnsmasq[4046]: Benutze Namensserver 192.168.1.1#53
Dec 31 08:23:14 Mnema NetworkManager[1088]: <info> Writing DNS information to /sbin/resolvconf
Dec 31 08:23:14 Mnema dbus[1002]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 31 08:23:24 Mnema ntpdate[4174]: step time server 91.189.94.4 offset 2.872367 sec
Dec 31 08:23:36 Mnema NetworkManager[1088]: <info> (wlan0): IP6 addrconf timed out or failed.
Dec 31 08:23:36 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Dec 31 08:23:36 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Dec 31 08:23:36 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Dec 31 08:37:54 Mnema wpa_supplicant[4038]: wlan0: CTRL-EVENT-DISCONNECTED bssid=72:c0:6f:6b:59:f8 reason=4
Dec 31 08:37:54 Mnema kernel: [38959.706425] cfg80211: Calling CRDA to update world regulatory domain
Dec 31 08:37:54 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dec 31 08:37:54 Mnema kernel: [38959.716996] cfg80211: World regulatory domain updated:
Dec 31 08:37:54 Mnema kernel: [38959.717000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec 31 08:37:54 Mnema kernel: [38959.717003] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 31 08:37:54 Mnema kernel: [38959.717006] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 31 08:37:54 Mnema kernel: [38959.717008] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 31 08:37:54 Mnema kernel: [38959.717009] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 31 08:37:54 Mnema kernel: [38959.717011] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 31 08:37:54 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec 31 08:38:10 Mnema NetworkManager[1088]: <warn> (wlan0): link timed out.
Dec 31 08:38:10 Mnema NetworkManager[1088]: <info> (wlan0): device state change: activated -> failed (reason 'SSID not found') [100 120 53]
Dec 31 08:38:10 Mnema NetworkManager[1088]: <warn> Activation (wlan0) failed for connection 'Automatisch Mnemosyne'
Dec 31 08:38:10 Mnema dbus[1002]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 31 08:38:10 Mnema NetworkManager[1088]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Dec 31 08:38:10 Mnema NetworkManager[1088]: <info> (wlan0): deactivating device (reason 'none') [0]
Dec 31 08:38:10 Mnema dbus[1002]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 31 08:38:10 Mnema NetworkManager[1088]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 4042
Dec 31 08:38:10 Mnema kernel: [38975.103466] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 31 08:38:10 Mnema avahi-daemon[1053]: Withdrawing address record for fe80::225:d3ff:feff:eeaf on wlan0.
Dec 31 08:38:10 Mnema avahi-daemon[1053]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::225:d3ff:feff:eeaf.
Dec 31 08:38:10 Mnema avahi-daemon[1053]: Interface wlan0.IPv6 no longer relevant for mDNS.
Dec 31 08:38:10 Mnema avahi-daemon[1053]: Withdrawing address record for 192.168.1.2 on wlan0.
Dec 31 08:38:10 Mnema avahi-daemon[1053]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.2.
Dec 31 08:38:10 Mnema avahi-daemon[1053]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dec 31 08:38:10 Mnema NetworkManager[1088]: <warn> DNS: plugin dnsmasq update failed
Dec 31 08:38:10 Mnema NetworkManager[1088]: <info> Removing DNS information from /sbin/resolvconf
Dec 31 08:38:10 Mnema dnsmasq[4046]: vorgelagerte Server von DBus gesetzt
Dec 31 08:38:10 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: scanning -> disconnected
Dec 31 09:17:01 Mnema CRON[4533]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Auto-activating connection 'Automatisch Mnemosyne'.
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) starting connection 'Automatisch Mnemosyne'
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0/wireless): access point 'Automatisch Mnemosyne' has security, but secrets are required.
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0/wireless): connection 'Automatisch Mnemosyne' has security, and secrets exist. No new secrets needed.
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Config: added 'ssid' value 'Mnemosyne'
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Config: added 'scan_ssid' value '1'
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Config: added 'auth_alg' value 'OPEN'
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Config: added 'psk' value '<omitted>'
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> Config: set interface ap_scan to 1
Dec 31 09:33:17 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dec 31 09:33:18 Mnema kernel: [42278.888338] wlan0: authenticate with 72:c0:6f:6b:59:f8
Dec 31 09:33:18 Mnema wpa_supplicant[4038]: wlan0: SME: Trying to authenticate with 72:c0:6f:6b:59:f8 (SSID='Mnemosyne' freq=2432 MHz)
Dec 31 09:33:18 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dec 31 09:33:18 Mnema wpa_supplicant[4038]: wlan0: Trying to associate with 72:c0:6f:6b:59:f8 (SSID='Mnemosyne' freq=2432 MHz)
Dec 31 09:33:18 Mnema kernel: [42278.899751] wlan0: send auth to 72:c0:6f:6b:59:f8 (try 1/3)
Dec 31 09:33:18 Mnema kernel: [42278.902049] wlan0: authenticated
Dec 31 09:33:18 Mnema kernel: [42278.903179] wlan0: associate with 72:c0:6f:6b:59:f8 (try 1/3)
Dec 31 09:33:18 Mnema wpa_supplicant[4038]: wlan0: Associated with 72:c0:6f:6b:59:f8
Dec 31 09:33:18 Mnema kernel: [42278.907445] wlan0: RX AssocResp from 72:c0:6f:6b:59:f8 (capab=0x411 status=0 aid=1)
Dec 31 09:33:18 Mnema kernel: [42278.907570] wlan0: associated
Dec 31 09:33:18 Mnema kernel: [42278.907641] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 31 09:33:18 Mnema kernel: [42278.907767] cfg80211: Calling CRDA for country: ES
Dec 31 09:33:18 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: authenticating -> associated
Dec 31 09:33:18 Mnema kernel: [42278.917690] ath: regdomain 0x82d4 updated by CountryIE
Dec 31 09:33:18 Mnema kernel: [42278.917699] ath: EEPROM regdomain: 0x82d4
Dec 31 09:33:18 Mnema kernel: [42278.917703] ath: EEPROM indicates we should expect a country code
Dec 31 09:33:18 Mnema kernel: [42278.917708] ath: doing EEPROM country->regdmn map search
Dec 31 09:33:18 Mnema kernel: [42278.917713] ath: country maps to regdmn code: 0x37
Dec 31 09:33:18 Mnema kernel: [42278.917717] ath: Country alpha2 being used: ES
Dec 31 09:33:18 Mnema kernel: [42278.917720] ath: Regpair used: 0x37
Dec 31 09:33:18 Mnema kernel: [42278.917760] cfg80211: Regulatory domain changed to country: ES
Dec 31 09:33:18 Mnema kernel: [42278.917764] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec 31 09:33:18 Mnema kernel: [42278.917769] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Dec 31 09:33:18 Mnema kernel: [42278.917774] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Dec 31 09:33:18 Mnema kernel: [42278.917778] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)
Dec 31 09:33:18 Mnema kernel: [42278.917783] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)
Dec 31 09:33:19 Mnema avahi-daemon[1053]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::225:d3ff:feff:eeaf.
Dec 31 09:33:19 Mnema avahi-daemon[1053]: New relevant interface wlan0.IPv6 for mDNS.
Dec 31 09:33:19 Mnema avahi-daemon[1053]: Registering new address record for fe80::225:d3ff:feff:eeaf on wlan0.*.
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: associated -> 4-way handshake
Dec 31 09:33:19 Mnema wpa_supplicant[4038]: wlan0: WPA: Key negotiation completed with 72:c0:6f:6b:59:f8 [PTK=CCMP GTK=TKIP]
Dec 31 09:33:19 Mnema wpa_supplicant[4038]: wlan0: CTRL-EVENT-CONNECTED - Connection to 72:c0:6f:6b:59:f8 completed (reauth) [id=0 id_str=]
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Mnemosyne'.
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> dhclient started with pid 4572
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> Activation (wlan0) Beginning IP6 addrconf.
Dec 31 09:33:19 Mnema avahi-daemon[1053]: Withdrawing address record for fe80::225:d3ff:feff:eeaf on wlan0.
Dec 31 09:33:19 Mnema avahi-daemon[1053]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::225:d3ff:feff:eeaf.
Dec 31 09:33:19 Mnema avahi-daemon[1053]: Interface wlan0.IPv6 no longer relevant for mDNS.
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Dec 31 09:33:19 Mnema dhclient: Internet Systems Consortium DHCP Client 4.2.4
Dec 31 09:33:19 Mnema dhclient: Copyright 2004-2012 Internet Systems Consortium.
Dec 31 09:33:19 Mnema dhclient: All rights reserved.
Dec 31 09:33:19 Mnema dhclient: For info, please visit https://www.isc.org/software/dhcp/
Dec 31 09:33:19 Mnema dhclient:
Dec 31 09:33:19 Mnema NetworkManager[1088]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Dec 31 09:33:19 Mnema dhclient: Listening on LPF/wlan0/00:25:d3:ff:ee:af
Dec 31 09:33:19 Mnema dhclient: Sending on LPF/wlan0/00:25:d3:ff:ee:af
Dec 31 09:33:19 Mnema dhclient: Sending on Socket/fallback
Dec 31 09:33:19 Mnema dhclient: DHCPREQUEST of 192.168.1.2 on wlan0 to 255.255.255.255 port 67 (xid=0x5fce8fc4)
Dec 31 09:33:20 Mnema avahi-daemon[1053]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::225:d3ff:feff:eeaf.
Dec 31 09:33:20 Mnema avahi-daemon[1053]: New relevant interface wlan0.IPv6 for mDNS.
Dec 31 09:33:20 Mnema avahi-daemon[1053]: Registering new address record for fe80::225:d3ff:feff:eeaf on wlan0.*.
Dec 31 09:33:22 Mnema dhclient: DHCPREQUEST of 192.168.1.2 on wlan0 to 255.255.255.255 port 67 (xid=0x5fce8fc4)
Dec 31 09:33:22 Mnema dhclient: DHCPNAK from 192.168.1.1 (xid=0x5fce8fc4)
Dec 31 09:33:22 Mnema NetworkManager[1088]: <info> (wlan0): DHCPv4 state changed preinit -> expire
Dec 31 09:33:22 Mnema dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x4f9013ef)
Dec 31 09:33:22 Mnema NetworkManager[1088]: <info> (wlan0): DHCPv4 state changed expire -> preinit
Dec 31 09:33:25 Mnema dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x4f9013ef)
Dec 31 09:33:25 Mnema dhclient: DHCPREQUEST of 192.168.1.2 on wlan0 to 255.255.255.255 port 67 (xid=0x4f9013ef)
Dec 31 09:33:25 Mnema dhclient: DHCPOFFER of 192.168.1.2 from 192.168.1.1
Dec 31 09:33:25 Mnema dhclient: DHCPACK of 192.168.1.2 from 192.168.1.1
Dec 31 09:33:25 Mnema dhclient: bound to 192.168.1.2 -- renewal in 40643 seconds.
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> address 192.168.1.2
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> prefix 24 (255.255.255.0)
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> gateway 192.168.1.1
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> nameserver '192.168.1.1'
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> nameserver '192.168.1.1'
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> domain name 'localdomain'
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
Dec 31 09:33:25 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Dec 31 09:33:25 Mnema avahi-daemon[1053]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.2.
Dec 31 09:33:25 Mnema avahi-daemon[1053]: New relevant interface wlan0.IPv4 for mDNS.
Dec 31 09:33:25 Mnema avahi-daemon[1053]: Registering new address record for 192.168.1.2 on wlan0.IPv4.
Dec 31 09:33:26 Mnema NetworkManager[1088]: <info> (wlan0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
Dec 31 09:33:26 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Dec 31 09:33:26 Mnema NetworkManager[1088]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dec 31 09:33:26 Mnema NetworkManager[1088]: <info> Policy set 'Automatisch Mnemosyne' (wlan0) as default for IPv4 routing and DNS.
Dec 31 09:33:26 Mnema NetworkManager[1088]: <info> Writing DNS information to /sbin/resolvconf
Dec 31 09:33:26 Mnema dnsmasq[4046]: vorgelagerte Server von DBus gesetzt
Dec 31 09:33:26 Mnema dnsmasq[4046]: Benutze Namensserver 192.168.1.1#53
Dec 31 09:33:26 Mnema NetworkManager[1088]: <info> Activation (wlan0) successful, device activated.
Dec 31 09:33:26 Mnema dbus[1002]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Dec 31 09:33:26 Mnema dbus[1002]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 31 09:33:34 Mnema ntpdate[4659]: adjust time server 91.189.94.4 offset 0.153810 sec
Dec 31 09:33:40 Mnema NetworkManager[1088]: <info> (wlan0): IP6 addrconf timed out or failed.
Dec 31 09:33:40 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Dec 31 09:33:40 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Dec 31 09:33:40 Mnema NetworkManager[1088]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Dec 31 10:17:01 Mnema CRON[4803]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 31 11:03:14 Mnema NetworkManager[1088]: <warn> nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
Dec 31 11:17:01 Mnema CRON[4981]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 31 12:17:01 Mnema CRON[5328]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 31 12:53:05 Mnema kernel: [54251.282071] asus_laptop: Unknown key 57 pressed
Dec 31 12:53:43 Mnema kernel: [54289.819875] usb 3-1: new low-speed USB device number 2 using ohci_hcd
Dec 31 12:53:43 Mnema kernel: [54289.999725] usb 3-1: New USB device found, idVendor=045e, idProduct=0039
Dec 31 12:53:43 Mnema kernel: [54289.999738] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 31 12:53:43 Mnema kernel: [54289.999746] usb 3-1: Product: Microsoft IntelliMouse® Optical
Dec 31 12:53:43 Mnema kernel: [54289.999752] usb 3-1: Manufacturer: Microsoft
Dec 31 12:53:44 Mnema mtp-probe: checking bus 3, device 2: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-1"
Dec 31 12:53:44 Mnema mtp-probe: bus: 3, device: 2 was not an MTP device
Dec 31 12:53:44 Mnema kernel: [54290.398397] usbcore: registered new interface driver usbhid
Dec 31 12:53:44 Mnema kernel: [54290.398406] usbhid: USB HID core driver
Dec 31 12:53:44 Mnema kernel: [54290.426987] input: Microsoft Microsoft IntelliMouse® Optical as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.0/input/input12
Dec 31 12:53:44 Mnema kernel: [54290.427629] hid-generic 0003:045E:0039.0001: input,hidraw0: USB HID v1.00 Mouse [Microsoft Microsoft IntelliMouse® Optical] on usb-0000:00:12.0-1/input0
Dec 31 13:13:10 Mnema kernel: [55455.107204] asus_laptop: Unknown key 58 pressed
Dec 31 13:13:10 Mnema anacron[6076]: Anacron 2.3 started on 2013-12-31
Dec 31 13:13:10 Mnema anacron[6076]: Normal exit (0 jobs run)
Dec 31 13:17:01 Mnema CRON[6184]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Dec 31 14:17:01 Mnema CRON[6538]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Thank you so much for your help!
Enna
Linux Mint 15 Olivia / 64-bit / Cinnamon
User avatar
karlchen
Level 21
Level 21
Posts: 13829
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: computer takes ages to start-up... problem unknown

Post by karlchen »

Hello, Enna.

Frankly speaking, the extract from the syslog file that you posted does not allow an meaningful interpretation.
The reason is trivial. I will try to explain using my own system as the example what I am after.

You write
When turning on my laptop, nothing happens on the screen, only waiting for maybe half a night or so, it will be ready to use.
So after powering your machine on, it takes a very long time till the logon screen appears.
We need to find out how long exactly: 5 minutes? 30 minutes? 120 minutes?
In order to find out we need the exact powering-on time and the time when the system thinks it is ready. Ideally we will have the exact time when the logon sceen appears as well.
syslog wrote:Dec 25 23:42:23 unimatrix0 kernel: Kernel logging (proc) stopped.
Dec 25 23:42:23 unimatrix0 rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="584" x-info="http://www.rsyslog.com"] exiting on signal 15.


Dec 25 23:43:22 unimatrix0 kernel: imklog 5.8.6, log source = /proc/kmsg started.
Dec 25 23:43:22 unimatrix0 rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="531" x-info="http://www.rsyslog.com"] start
Dec 25 23:43:22 unimatrix0 rsyslogd: rsyslogd's groupid changed to 103
Dec 25 23:43:22 unimatrix0 rsyslogd: rsyslogd's userid changed to 101
Dec 25 23:43:22 unimatrix0 rsyslogd-2039: Could not open output pipe '/dev/xconsole' [try http://www.rsyslog.com/e/2039 ]
Dec 25 23:43:22 unimatrix0 kernel: [ 0.000000] Initializing cgroup subsys cpuset
Dec 25 23:43:22 unimatrix0 kernel: [ 0.000000] Initializing cgroup subsys cpu
Dec 25 23:43:22 unimatrix0 kernel: [ 0.000000] Linux version 3.2.0-57-generic (buildd@lamiak) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #87-Ubuntu SMP Tue Nov 12 21:38:12 UTC 2013 (Ubuntu 3.2.0-57.87-generic 3.2.52)
On Sunday after having installed some updates I rebooted my machine.
As you can read the 2 blue lines stated that kernel logging stops. These are the last messages that you will read before a machine either reboots or shuts down. Simple reason: It stop logging its actions.

As you can read 59 Seconds later syslog says it has started logging kernel actions again. From now on it will log any relevant activity to syslog again.

This means, though this is definitely a slow machine, it takes a minute after power-on (reboot here) till thy syslog will log its activities.

1 min. 40 sec. later the machine has finished all its initialization steps when writing this to the syslog file:
Dec 25 23:44:59 unimatrix0 blueman-mechanism: Exiting
The logon screen usually comes up here about 75 seconds after pwer-on (while the machine is still working in the background on the system startup).
As soon as I have entered my password and pressed enter it will take a about 30 seconds till my xfce desktop has been painted on the screen and till the machine will accept my input.

So all in all from power-on, it takes roundabout 2 minutes for my slow Zotac machine to get ready.


Why do I explain such (boring) details:
  • We need exact timestamps for typical steps of the startup process in order to find out during which startup phase excessives dealys occur.
  • We need the exact powering on time and the exact time when kernel logging starts.
    If the time span is clearly above 1 minute then there is a good chancee that the Bios phase of your startup is causing the delay.
    Alternatively, Linux performs a full file system check on every (re)boot. If this is the case we need to find out why.
    In particular on large disks filled with data a file system check may take quite a long time.
  • We need to find out whether there are clearly identifiable delays logged to syslog which occur during the startup procedure.
    From the time kernel logging starts till the machine has finished its boot process, misconfiguration, hardware problems, software problems might cause identifiable delays, too. (Unlikely those will sum up to more than a minute or two)
  • We need your statement how long it takes between power-on and the appearance of the logon screen.
  • We need your statement how long it takes ater you have entered your password till the desktop is really ready to be used.
This is why we need another reboot to get all these time values.

The other things which will help:
  • The file /var/log/dmesg
  • The file ~/.xsession-errors
  • The file /boot/grub/grub.cfg
  • The output of the command

    Code: Select all

    inxi -Fx
    (Camouflage the MAC addresses before posting, please.)
Kind regards,
Karl
Image
Linux Mint 19.3 64-bit Cinnamon, Total Commander 9.51 64-bit
Good Company
Hitchhiker
Level 1
Level 1
Posts: 28
Joined: Thu Nov 21, 2013 7:36 am

Re: computer takes ages to start-up... problem unknown

Post by Hitchhiker »

This seems to be an issue with certain computers, especially certain laptops, with Linux or BSD. This is usually a firmware problem with the recommendation of updating the BIOS if possible. The other thing is if there is a lot of memory or two different, non-matching, memory modules in the computer. Sometimes a BIOS update will fix or at least help speed up booting with this problem. Other times it might be fixed by removing one memory module or disabling dual channel memory in the BIOS if possible.
computerbob
Level 4
Level 4
Posts: 283
Joined: Wed Jan 01, 2014 1:55 pm

Re: computer takes ages to start-up... problem unknown

Post by computerbob »

When someone gives me a laptop to look at, the first think I do is pull the battery. They go bad alot. Then I plug in the power cord. I've seen totally dead laptops work fine without a battery, which needed replacing, by the way.
Post Reply

Return to “Hardware Support”