Hi, I'm new on KDE, (using gnome2 before) and I think its really great

My problem is my boot time seem not normal, I still can't understand the disscussion on this post, (my english wasn't good) so I think it will be better if I ask this question on a new post. I hope I'll get some explanation here

on my LMDE (tracking debian testing), I get this weird thing: real boot time (by stopwatch, from grub > enter until fully loaded desktop) is far different than dmesg output..
On my stopwatch, the desktop loaded after 2 minutes and 26 second but dmesg only show 55 sec..

here's my dmesg part:

Code: Select all

    [   10.020991] uvesafb: VBIOS/hardware supports DDC2 transfers
    [   10.360169] uvesafb: monitor limits: vf = 60 Hz, hf = 48 kHz, clk = 71 MHz
    [   10.360642] uvesafb: scrolling: redraw
    [   10.360652] uvesafb: request region 0x3c0-0x3e0 failed
    [   10.361257] uvesafb: probe of uvesafb.0 failed with error -5
    [   10.365750] vga16fb: initializing
    [   10.365759] vga16fb: mapped to 0xffff8800000a0000
    [   10.365770] checking generic (c0000000 300000) vs hw (a0000 10000)
    [   10.365883] fb1: VGA16 VGA frame buffer device
    [   10.997940] Btrfs loaded
    [   11.313187] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
    [   15.258619] udevd[381]: starting version 175
    [   16.547084] ACPI: acpi_idle registered with cpuidle
    [   16.946013] powernow-k8: Found 1 AMD E-350 Processor (2 cpu cores) (version 2.20.00)
    [   16.946176] powernow-k8:    0 : pstate 0 (1600 MHz)
    [   16.946180] powernow-k8:    1 : pstate 1 (1280 MHz)
    [   16.946184] powernow-k8:    2 : pstate 2 (800 MHz)
    [   17.014955] asus_wmi: ASUS WMI generic driver loaded
    [   17.220344] ACPI: Battery Slot [BAT0] (battery present)
    [   17.220820] ACPI: AC Adapter [AC0] (off-line)
    [   17.232151] asus_wmi: Initialization: 0x0
    [   17.233078] asus_wmi: BIOS WMI version: 0.9
    [   17.233440] asus_wmi: SFUN value: 0x0
    [   17.235219] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input6
    [   17.237038] ACPI: resource piix4_smbus [io  0x0b00-0x0b07] conflicts with ACPI region SMRG [io 0xb00-0xb0f]
    [   17.237051] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    [   17.245882] asus_wmi: Backlight controlled by ACPI video driver
    [   17.250285] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
    [   17.250490] SP5100 TCO timer: mmio address 0xbafe00 already in use
    [   17.373243] fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
    [   17.373258] Disabling lock debugging due to kernel taint
    [   17.456306] [fglrx] Maximum main memory to use for locked dma buffers: 3414 MBytes.
    [   17.456483] [fglrx]   vendor: 1002 device: 9802 count: 1
    [   17.457050] [fglrx] ioport: bar 1, base 0xf000, size: 0x100
    [   17.457074] pci 0000:00:01.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
    [   17.457083] pci 0000:00:01.0: setting latency timer to 64
    [   17.457522] [fglrx] Kernel PAT support is enabled
    [   17.457567] [fglrx] module loaded - fglrx 8.98.2 [Jul 27 2012] with 1 minors
    [   17.480143] cfg80211: Calling CRDA to update world regulatory domain
    [   17.483088] Bluetooth: Core ver 2.16
    [   17.483133] NET: Registered protocol family 31
    [   17.483137] Bluetooth: HCI device and connection manager initialized
    [   17.483142] Bluetooth: HCI socket layer initialized
    [   17.483146] Bluetooth: L2CAP socket layer initialized
    [   17.483156] Bluetooth: SCO socket layer initialized
    [   17.575972] Bluetooth: Generic Bluetooth USB driver ver 0.6
    [   17.576905] usbcore: registered new interface driver btusb
    [   18.131265] brcmsmac 0000:01:00.0: bus 1 slot 0 func 0 irq 7
    [   18.131376] brcmsmac 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [   18.131392] brcmsmac 0000:01:00.0: setting latency timer to 64
    [   18.149452] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.4, id: 0x1c0b1, caps: 0xd04733/0xa40000/0xa0400
    [   18.233158] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input7
    [   18.375559] snd_hda_intel 0000:00:01.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    [   18.375706] snd_hda_intel 0000:00:01.1: irq 43 for MSI/MSI-X
    [   18.375766] snd_hda_intel 0000:00:01.1: setting latency timer to 64
    [   18.507411] cfg80211: World regulatory domain updated:
    [   18.507425] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [   18.507436] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   18.507447] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [   18.507456] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
    [   18.507465] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   18.507474] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   18.584196] Bluetooth: hci0 command tx timeout
    [   18.745148] Linux media interface: v0.10
    [   18.784179] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0
    [   18.784569] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/sound/card0/input8
    [   18.786256] snd_hda_intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    [   18.920244] Linux video capture interface: v2.00
    [   18.958399] uvcvideo: Found UVC 1.00 device USB2.0 UVC VGA WebCam (13d3:5702)
    [   18.979570] input: USB2.0 UVC VGA WebCam as /devices/pci0000:00/0000:00:13.2/usb2/2-4/2-4:1.0/input/input9
    [   18.980786] usbcore: registered new interface driver uvcvideo
    [   18.980798] USB Video Class driver (1.1.1)
    [   19.000275] input: HDA ATI SB Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input10
    [   19.003338] input: HDA ATI SB Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input11
    [   19.255336] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
    [   19.258334] cfg80211: Calling CRDA for country: US
    [   19.271535] cfg80211: Regulatory domain changed to country: US
    [   19.271544] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
    [   19.271550] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
    [   19.271555] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
    [   19.271559] cfg80211:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   19.271564] cfg80211:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   19.271569] cfg80211:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
    [   19.271573] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
    [   23.541713] Adding 3066876k swap on /dev/sda2.  Priority:-1 extents:1 across:3066876k
    [   23.600133] EXT4-fs (sda6): re-mounted. Opts: (null)
    [   24.493413] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro
    [   24.982824] device-mapper: uevent: version 1.0.3
    [   24.984267] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
    [   25.306231] loop: module loaded
    [   27.958645] EXT4-fs (sda5): warning: maximal mount count reached, running e2fsck is recommended
    [   27.961564] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: errors=remount-ro
    [   28.334712] fuse init (API version 7.17)
    [   39.722818] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input12
    [   42.574920] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    [   42.574932] Bluetooth: BNEP filters: protocol multicast
    [   42.586109] Bluetooth: RFCOMM TTY layer initialized
    [   42.586128] Bluetooth: RFCOMM socket layer initialized
    [   42.586135] Bluetooth: RFCOMM ver 1.11
    [   44.005148] lp: driver loaded but no devices found
    [   44.129583] ppdev: user-space parallel port driver
    [   45.038049] ieee80211 phy0: brcms_ops_config: change monitor mode: false (implement)
    [   45.038068] ieee80211 phy0: brcms_ops_config: change power-save mode: false (implement)
    [   45.038968] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)
    [   45.039931] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [   51.278104] usbcore: registered new interface driver usbserial
    [   51.278159] USB Serial support registered for generic
    [   51.278795] usbcore: registered new interface driver usbserial_generic
    [   51.278803] usbserial: USB Serial Driver core
    [   52.539797] fglrx_pci 0000:00:01.0: irq 44 for MSI/MSI-X
    [   52.542279] [fglrx] Firegl kernel thread PID: 3493
    [   52.542711] [fglrx] Firegl kernel thread PID: 3494
    [   52.543243] [fglrx] Firegl kernel thread PID: 3495
    [   52.543448] [fglrx] IRQ 44 Enabled
    [   52.936826] [fglrx] Gart USWC size:1116 M.
    [   52.936838] [fglrx] Gart cacheable size:442 M.
    [   52.936855] [fglrx] Reserved FB block: Shared offset:0, size:1000000
    [   52.936865] [fglrx] Reserved FB block: Unshared offset:fc81000, size:37f000
    [   52.936875] [fglrx] Reserved FB block: Unshared offset:17ff4000, size:c000
    [   53.536153] usb 3-3: new low-speed USB device number 3 using ohci_hcd
    [   53.704216] usb 3-3: New USB device found, idVendor=1c4f, idProduct=0003
    [   53.704231] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [   53.704240] usb 3-3: Product: U+P Mouse
    [   53.704247] usb 3-3: Manufacturer: SIGMACH1P
    [   53.788193] input: SIGMACH1P U+P Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3:1.0/input/input13
    [   53.789091] generic-usb 0003:1C4F:0003.0001: input,hidraw0: USB HID v1.10 Mouse [SIGMACH1P U+P Mouse] on usb-0000:00:12.0-3/input0
    [   53.789365] usbcore: registered new interface driver usbhid
    [   53.789373] usbhid: USB HID core driver
    [   54.381356] usb 3-3: USB disconnect, device number 3
    [   55.332343] usb 3-3: new low-speed USB device number 4 using ohci_hcd
    [   55.501354] usb 3-3: New USB device found, idVendor=1c4f, idProduct=0003
    [   55.501369] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [   55.501378] usb 3-3: Product: U+P Mouse
    [   55.501385] usb 3-3: Manufacturer: SIGMACH1P
    [   55.509121] input: SIGMACH1P U+P Mouse as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3:1.0/input/input14
    [   55.510136] generic-usb 0003:1C4F:0003.0002: input,hidraw0: USB HID v1.10 Mouse [SIGMACH1P U+P Mouse] on usb-0000:00:12.0-3/input0
    faramir@faramir-1215b ~ $

Is that normal to have 2,5 minutes boot time ?? on my LinuxMint 11 (gnome2), its only ~ 45 sec

Hi,

nothing of the log you posted has anything to do with KDE. KDE starts after probably all in that log already happened.
If you want to know how much time KDE takes to start, count from pressing the Enter key at the login screen to the desktop. Everything else has nothing to do with KDE. For that time, I'd consider at most 20 seconds to be normal on an older machine.

Greetings,
Sven

Thanks Sven, now that I know the "normal time", I'll try to optimize the KDE loading time (seems like my default install load too many service)

scummos wrote:Hi,

nothing of the log you posted has anything to do with KDE. KDE starts after probably all in that log already happened.
If you want to know how much time KDE takes to start, count from pressing the Enter key at the login screen to the desktop. Everything else has nothing to do with KDE. For that time, I'd consider at most 20 seconds to be normal on an older machine.

Greetings,
Sven

what would you consider an "older" machine ? I consider mine fairly modern and it takes mine 20 sec to load KDE after a cold boot. This after applying all the optimizations I read about such as disabling pulseaudio, akonadi, nepomuk etc, desktop effects, defragging file system and so on.

KDE 3.5 started up faster than this on a single core 800 MHz laptop with a hard drive that had 1/3 the speed of my current one.

Are kde developers testing KDE on beefy 4/8 core systems with SSDs ? If so, be aware that most people aren't running on that kind of h/w and they shouldn't be.

I can't state exactly what an "older machine" would be, but I got a Thinkpad with an i5 C2D and SSD hard drive here, and it start up faster than 20 seconds. I don't know how long exactly tough.

I agree that testing performance stuff on older machines is probably a better idea than testing on a supercomputer.

Greetings

scummos wrote:I can't state exactly what an "older machine" would be, but I got a Thinkpad with an i5 C2D and SSD hard drive here, and it start up faster than 20 seconds. I don't know how long exactly tough.

I agree that testing performance stuff on older machines is probably a better idea than testing on a supercomputer.

Greetings

just as I suspected - it is alarming to see devs out of touch with reality and advocating throwing more h/w at a problem rather than fixing underlying inefficiencied in the s/w. I have seen many posts where people even with SSD are getting 15 secs KDE start time - this should be a wakeup call !

With an SSD, I ecpect KDE startup time < 1 sec. Period.

On my system, which is an i5 with a regular hard disk, it takes 20 seconds maximum I would estimate to login. A login without warm caches will take longer though.

Hi,

vmuppalla wrote:just as I suspected - it is alarming to see devs out of touch with reality and advocating throwing more h/w at a problem rather than fixing underlying inefficiencied in the s/w.

Sorry, but deducing this from my post is the only thing which is really out of touch with reality.
I don't have anything to do with KDEs overall performance or its startup time. If I had, I'd be sure to test with different hardware and not just SSDs (and I'm sure that people trying to optimize performance are doing this with different hardware). Plus, I didn't recommend anything, especially not buying better hardware; there was a question which asked for opinions about the "normal" startup time, and I just wrote down my personal experience.

On the contrary, I do agree that the current KDE startup time is too long (the startup time of every application always is too long). I suspect it's not that easy to optimize because no single developer is "responsible" for the startup process, but it is composed from a variety of different applications and daemons starting up. It would be a useful task to disable some and search for a bottleneck, then check (by asking the affected program's mailing list or so) whether it can be improved.

Greetings,
Sven

With an SSD, my KDE is about 20 seconds from the moment startkde is ran. But if I consider the end point when I hear the login chime, its closer to 30 seconds.