Sabayon taking way too long to boot

Issues Related to Hardware (Sound, Video, Printers, Scanners, Webcams, Touchpads, Keyboards, Sensors, Drives, GRUB, etc.)

Moderator: Moderators

Sabayon taking way too long to boot

Postby denijane » Mon Jan 20, 2014 19:33

Hi all.
I'm with new laptop Asus N550JV. It's a decent machine with Intel Core i7-4700HQ, 16GB Ram and integrated Intel HD Graphics 4600 and Nvidia GeForce GT 750M. I think it is supposed to boot quite quickly. It doesn't. It takes more than a minute from boot menu to KDE login screen.
So I wanted to ask if someone with more experience than me could take a look at the dmesg and tell me if there is some kind of problem. In it I see tons of "Unknown symbol" messages, but the only errors that grep returns to me is:
Code: Select all
[    6.617438] usb 1-5: device descriptor read/8, error -110
[   11.733626] usb 1-5: device descriptor read/8, error -110
[   22.398176] usb 1-5: device not accepting address 3, error -62
[   32.961698] usb 1-5: device not accepting address 4, error -62
[   43.525181] usb 1-5: device not accepting address 5, error -62


So far the confirmed problems I have are:
- no blutooth working, even though the adapter is detected in kinfo
- sound works from the integrated speakers, but do not transfer to the audio jack (i.e. external speakers) or hdmi output.

Also I'd like to ask how I can check if my NVIDIA card is working all right.

Some outpit I though might be useful:
lspci
Code: Select all
00:00.0 Host bridge: Intel Corporation Haswell DRAM Controller (rev 06)                                                                                                                                                                                                       
00:01.0 PCI bridge: Intel Corporation Haswell PCI Express x16 Controller (rev 06)                                                                                                                                                                                             
00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06)                                                                                                                                                                           
00:03.0 Audio device: Intel Corporation Haswell HD Audio Controller (rev 06)                                                                                                                                                                                                   
00:14.0 USB controller: Intel Corporation Lynx Point USB xHCI Host Controller (rev 04)                                                                                                                                                                                         
00:16.0 Communication controller: Intel Corporation Lynx Point MEI Controller #1 (rev 04)                                                                                                                                                                                     
00:1a.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #2 (rev 04)                                                                                                                                                                                 
00:1b.0 Audio device: Intel Corporation Lynx Point High Definition Audio Controller (rev 04)                                                                                                                                                                                   
00:1c.0 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #1 (rev d4)                                                                                                                                                                                             
00:1c.1 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #2 (rev d4)                                                                                                                                                                                             
00:1c.2 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #3 (rev d4)                                                                                                                                                                                             
00:1c.3 PCI bridge: Intel Corporation Lynx Point PCI Express Root Port #4 (rev d4)                                                                                                                                                                                             
00:1d.0 USB controller: Intel Corporation Lynx Point USB Enhanced Host Controller #1 (rev 04)                                                                                                                                                                                 
00:1f.0 ISA bridge: Intel Corporation Lynx Point LPC Controller (rev 04)                                                                                                                                                                                                       
00:1f.2 SATA controller: Intel Corporation Lynx Point 6-port SATA Controller 1 [AHCI mode] (rev 04)                                                                                                                                                                           
00:1f.3 SMBus: Intel Corporation Lynx Point SMBus Controller (rev 04)                                                                                                                                                                                                         
01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev ff)                                                                                                                                                                                                   
04:00.0 Network controller: Atheros Communications Inc. AR9485 Wireless Network Adapter (rev 01)                                                                                                                                                                               
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 0c)


dmesg
http://pastebin.com/pKaTai4E

If there is a better way to find the problem than dmesg, please tell me, I'll post it.
denijane
Growing Hen
 
Posts: 155
Joined: Tue Feb 13, 2007 19:54
Location: Sofia

Re: Sabayon taking way too long to boot

Postby Fitzcarraldo » Mon Jan 20, 2014 19:49

You mention kinfo, so I assume you're using SL's KDE edition. Please see the post Re: Bluez daemon not running, unable to use bluetooth dongle. In SL, Bluetooth is broken in KDE because SL uses net-wireless/bluez-5.12 in order to be able to offer GNOME 3.10.* (which requires bluez-5.*). Actually, as I don't use GNOME I'm not even sure if Bluez-5 works in GNOME yet, so someone else will have to comment on that. Anyway, unfortunately you will not be able to use Bluetooth in SL with KDE at the moment. In Gentoo I am able to use Bluez-4 with KDE 4.12.0 because Bluez-5 is masked in Gentoo, so I can use Bluetooth. But with SL that is not possible.
User avatar
Fitzcarraldo
Sagely Hen
 
Posts: 7978
Joined: Sat Mar 10, 2007 5:40
Location: United Kingdom

Re: Sabayon taking way too long to boot

Postby batvink » Mon Jan 20, 2014 20:15

install net-wireless/blueman
User avatar
batvink
Old Dear Hen
 
Posts: 495
Joined: Sun Oct 28, 2007 11:44
Location: the netherlands

Re: Sabayon taking way too long to boot

Postby batvink » Mon Jan 20, 2014 20:20

also, as root, ouput of:
Code: Select all
systemd-analyze

Code: Select all
systemd-analyze blame

and
Code: Select all
systemd-analyze critical-chain
User avatar
batvink
Old Dear Hen
 
Posts: 495
Joined: Sun Oct 28, 2007 11:44
Location: the netherlands

Re: Sabayon taking way too long to boot

Postby Commander » Mon Jan 20, 2014 20:51

Fitzcarraldo wrote:Actually, as I don't use GNOME I'm not even sure if Bluez-5 works in GNOME yet, so someone else will have to comment on that.


I am using GNOME and right now Bluetooth isn't working for me.
Commander
Baby Hen
 
Posts: 6
Joined: Sun Jan 19, 2014 19:31
Location: Cologne

Re: Sabayon taking way too long to boot

Postby denijane » Mon Jan 20, 2014 21:51

Hi guys. Thanks for the quick response.

I have blueman installed. Still no blutooth.

As for the other stuff, here's the output you asked for:
Code: Select all
localhost  # systemd-analyze
Startup finished in 4.962s (kernel) + 43.943s (userspace) = 48.906s
localhost # systemd-analyze blame
         32.071s systemd-udev-settle.service
          8.149s NetworkManager.service
          5.167s systemd-logind.service
          3.168s x-setup.service
          3.085s ufw.service
          2.962s systemd-user-sessions.service
          2.635s systemd-fsck-root.service
          2.620s plymouth-start.service
          2.563s avahi-daemon.service
          2.421s systemd-vconsole-setup.service
          2.203s plymouth-quit-wait.service
          2.203s plymouth-quit.service
          2.195s dev-mqueue.mount
          1.955s sys-kernel-debug.mount
          1.955s dev-hugepages.mount
          1.928s dev-disk-by\x2duuid-5de9b296\x2d1968\x2d4ce2\x2db745\x2d79782c4a3819.swap
          1.259s systemd-modules-load.service
          1.230s systemd-udev-trigger.service
           993ms systemd-udevd.service
           984ms var-lock.mount
           984ms var-run.mount
           955ms sys-fs-fuse-connections.mount
           785ms lvm2-activation-early.service
           541ms udisks2.service
           347ms rtkit-daemon.service
           274ms systemd-sysctl.service
           270ms polkit.service
           244ms systemd-tmpfiles-setup-dev.service
           210ms systemd-tmpfiles-setup.service
           182ms lvm2-activation-net.service
           145ms systemd-tmpfiles-clean.service
           121ms bluetooth.service
           116ms wpa_supplicant.service
           101ms systemd-journal-flush.service
            96ms systemd-remount-fs.service
            66ms plymouth-read-write.service
            63ms systemd-random-seed-load.service
            59ms vixie-cron.service
            56ms upower.service
            18ms alsa-restore.service
             5ms lvm2-activation.service
             1ms tmp.mount
localhost # systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @43.943s
└─kdm.service @43.943s
  └─steambox.service @43.943s
    └─network.target @43.943s
      └─NetworkManager.service @35.793s +8.149s
        └─basic.target @35.775s
          └─timers.target @35.775s
            └─systemd-tmpfiles-clean.timer @35.775s
              └─sysinit.target @35.723s
                └─systemd-tmpfiles-setup.service @35.512s +210ms
                  └─local-fs.target @35.511s
                    └─tmp.mount @5.318s +1ms
                      └─local-fs-pre.target @4.150s
                        └─systemd-remount-fs.service @4.052s +96ms
                          └─systemd-journald.socket @1.354s
                            └─-.mount @1.353s


Does it make sense? Because it really boots very slowly.
denijane
Growing Hen
 
Posts: 155
Joined: Tue Feb 13, 2007 19:54
Location: Sofia

Re: Sabayon taking way too long to boot

Postby linuxfluesterer » Tue Jan 21, 2014 12:26

Hallo Denijane.
I have the same problem with bluetooth here (in KDE 4.12). But there is one thing I did to improve boot up speed a lot.
I've changed my mechanical hard drive into an ssd. And I have only an Acer notebook with Intel core I5 3210, 8GByte Ram, integrated Intel graphics and NVidia GT630M (which I've disabled). My boot up time from power on to login screen is about 20 seconds. SSD is the best to improve a computers speed in these times. Mayby you'll try?

-Linuxfluesterer (I love KDE ...)
TTIP is NOT YET stopped. Especially consider NHS and ISDS topics. Talk to your local politician to open eyes for danger to democracy because of TTIP
User avatar
linuxfluesterer
Old Dear Hen
 
Posts: 699
Joined: Thu Sep 20, 2012 19:47
Location: Germany

Re: Sabayon taking way too long to boot

Postby batvink » Tue Jan 21, 2014 12:36

Bluetooth indeed seems to be NOT working in SL.
There are more users with the same problem.
Since bluetooth isn't working anyway, you might as well temp. disable the service:
as root:
Code: Select all
systemctl disable bluetooth.service


X-setup is only used on live-dvd's, you can disable that too:
Code: Select all
systemctl disable x-setup.service


If you don't use steambox at all, disable it:
Code: Select all
systemctl disable steambox.service


Same goes for the firewall (ufw)
If you are behind a router (build-in firewall) i guess you can disable ufw.service

rtkit-daemon.service (Realtime Policy and Watchdog Daemon)
Did you installed that? i don't have or need it...

and then the systemd-udev-settle.service (udev Wait for Complete Device Initialization)
What it does is listening to kernel uevents.
I don't know why it takes so long on your machine (32 secs.), but mine takes less than 8 secs.
The behavior of the running daemon can be changed with "udevadm
e.g. : udevadm control --timeout=<seconds>
or try to change it in the unit:
Code: Select all
nano -w /usr/lib/systemd/system/systemd-udev-settle.service

under section [service]
TimeoutSec=180
User avatar
batvink
Old Dear Hen
 
Posts: 495
Joined: Sun Oct 28, 2007 11:44
Location: the netherlands

Re: Sabayon taking way too long to boot

Postby denijane » Tue Jan 21, 2014 15:49

Hi again.
Well, after inspecting the dmesg once again, I think I discovered what the problem is: xhci_hcd .
It seems that from the 12th second to the 44th second, all it's doing is waiting for xhci_hcd to do something.
Code: Select all
[   16.991818] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[   22.197007] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[   22.398176] usb 1-5: device not accepting address 3, error -62
[   22.551341] usb 1-5: new full-speed USB device number 4 using xhci_hcd
[   27.555368] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[   32.760555] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[   32.961698] usb 1-5: device not accepting address 4, error -62
[   33.114880] usb 1-5: new full-speed USB device number 5 using xhci_hcd
[   38.118812] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[   43.324020] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[   43.525181] usb 1-5: device not accepting address 5, error -62
[   43.525253] hub 1-0:1.0: unable to enumerate USB device on port 5
[   43.678385] usb 1-7: new high-speed USB device number 6 using xhci_hcd
[   43.790519] usb 1-7: New USB device found, idVendor=13d3, idProduct=5188
[   43.790523] usb 1-7: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[   43.790525] usb 1-7: Product: USB2.0 UVC HD Webcam
[   43.790527] usb 1-7: Manufacturer: Azurewave
[   43.790528] usb 1-7: SerialNumber: NULL
[   43.947597] usb 1-8: new high-speed USB device number 7 using xhci_hcd
[   43.958821] usb 1-8: New USB device found, idVendor=0bda, idProduct=0139
[   43.958823] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   43.958825] usb 1-8: Product: USB2.0-CRW
[   43.958826] usb 1-8: Manufacturer: Generic
[   43.958827] usb 1-8: SerialNumber: 20100201396000000
[   44.060635] usb 3-1: new high-speed USB device number 2 using ehci-pci
[   44.175068] usb 3-1: New USB device found, idVendor=8087, idProduct=8008
[   44.175070] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   44.175330] hub 3-1:1.0: USB hub found
[   44.175410] hub 3-1:1.0: 6 ports detected
[   44.278775] usb 4-1: new high-speed USB device number 2 using ehci-pci
[   44.393209] usb 4-1: New USB device found, idVendor=8087, idProduct=8000
[   44.393210] usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   44.393350] hub 4-1:1.0: USB hub found
[   44.393457] hub 4-1:1.0: 8 ports detected
[   44.410565] bbswitch: version 0.7
[   44.410568] bbswitch: Found integrated VGA device 0000:00:02.0: \_SB_.PCI0.GFX0
[   44.410572] bbswitch: Found discrete VGA device 0000:01:00.0: \_SB_.PCI0.PEG0.PEGP
[   44.410579] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)
[   44.410636] bbswitch: detected an Optimus _DSM function
[   44.410677] bbswitch: Succesfully loaded. Discrete card 0000:01:00.0 is on
[   44.412362] bbswitch: disabling discrete graphics
[   44.412370] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95)

I found a possible solution on http://www.pcl-developers.org/xhci-hcd-I-hate-you-USB-3-0-and-Primesense-Asus-Xtion-td5707949.htm but since it requires recompiling the kernel to set xhci_hcd and ehci_hcd drivers as modules, I'm not sure I'll be able to do that (I have no idea how to do it).

As for disabling some services, I'll probably do it, but if the problem is xhci_hcd then I guess this won't help.
denijane
Growing Hen
 
Posts: 155
Joined: Tue Feb 13, 2007 19:54
Location: Sofia

Re: Sabayon taking way too long to boot

Postby batvink » Wed Jan 22, 2014 12:29

can you try to boot with a customized kernel parameter, and test if it makes any difference?

1, boot your machine
2, at grubmenu press E to edit
3, goto the end of your kernelline and add: pcie_hp=nomsi
so, it looks something like:
Code: Select all
linux   /kernel-genkernel-x86-3.12.0-sabayon root=/dev/sda3 ro splash vga=791 quiet dokeymap keymap=us  resume=/dev/sda5 pcie_hp=nomsi 

and press F10 to boot the system with the customized settings.
User avatar
batvink
Old Dear Hen
 
Posts: 495
Joined: Sun Oct 28, 2007 11:44
Location: the netherlands

Next

Return to Hardware

Who is online

Users browsing this forum: No registered users and 1 guest