Choose style:

Author Topic: Boot time issues  (Read 1653 times)

0 Members and 1 Guest are viewing this topic.

Offline Bigoeuf

  • Trusted User
  • Member
  • *****
  • Posts: 175
  • Karma: 23
  • New Forum User
    • View Profile
  • Peppermint version(s): 8 & 7 (64bit)
Boot time issues
« on: September 15, 2016, 08:59:26 am »
Hello - had posted this under a different topic but removed it & started a new one because it is more appropriate.
Managed to scale new heights with boot time - almost 2 mins :o however I believe I know the problem - but rectifying it is a different matter.
Like I said boot time is long & on examining my dmesg i shows numerous instances of:
Code: [Select]
atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.

I have googled it & it appears that it is a not uncommon issue with Dell Inspiron 1501s - quite possibly that the BIOS is notifying me that "The AC adapter cannot be identified" (which has just recently started to be displayed on the screen during bootup between the BIOS screen & Grub screen.)

I have tried
Code: [Select]
setkeycodes e00d <keycode>
after reading this article here:
http://www.jveweb.net/en/archives/2011/01/configure-unrecognized-keys-in-linux.html

but the terminal returns:
Code: [Select]
Couldn't get a file descriptor referring to the console

On further research into the Dell Inspiron 1501s Battery/AC charger side of things - specifically theses postings:
http://askubuntu.com/questions/116538/atkbd-c-spamming-the-logs-how-to-get-rid-what-is-this

https://bugzilla.redhat.com/show_bug.cgi?id=454131

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/549741

I did the following:

    Shut down your laptop.
    Unplug the power cord from your laptop, and unplug it also from the power outlet.
    Remove the battery from your laptop.
    Press and hold the Power button for 2 to 3 seconds.
    Repeat this 2 to 3 times.
    Plug the power cord back into your laptop (while leaving the power cord unplugged from the wall outlet)
    Press and hold the Power button again for 2 to 3 seconds.
    Repeat this 2 to 3 times.
    Reinstall the battery (at least 30 seconds should have gone by since you removed it).
    Plug the power cord into the wall outlet.
    Start your laptop

When I started up the:
Code: [Select]
atkbd serio0: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
atkbd serio0: Use 'setkeycodes e00d <keycode>' to make it known.
reports in the dmesg had gone however new reports had appeared  under apparmor entries & the boot time is roughly as long  ???

Here is my latest dmesg:
http://s000.tinyupload.com/index.php?file_id=26165262606183989402

I don't know if there is anyone who can help me with what the apparmor entries mean & if there is anything I can do to reduce the boot time

Thanks  :)

 

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26466
  • Karma: 2884
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Boot time issues
« Reply #1 on: September 15, 2016, 08:59:26 am »
[THIS IS AN AUTOMATED RESPONSE]

If this is a new request for support and you haven't already done so, can you please be sure to include information about your system that will help us to help you.

Please open a terminal (Ctrl+Alt+T) and run the following command:
Code: [Select]
inxi -Fz
then copy what was returned in the terminal and post it back here.

Thanks in advance :)
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26466
  • Karma: 2884
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Boot time issues
« Reply #2 on: September 15, 2016, 09:37:09 am »
Please see the autoresponse above .. this is here to help us help you and to speed up troubleshooting, but will not achieve this if people ignore it ;)
« Last Edit: September 15, 2016, 09:38:45 am by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline Bigoeuf

  • Trusted User
  • Member
  • *****
  • Posts: 175
  • Karma: 23
  • New Forum User
    • View Profile
  • Peppermint version(s): 8 & 7 (64bit)
Re: Boot time issues
« Reply #3 on: September 15, 2016, 10:28:48 am »
Hello Mark
Yes of course - here it is:

Spoiler (click here to view / hide)
mick@mick-Inspiron-1501 ~ $ inxi -Fz
System:    Host: mick-Inspiron-1501 Kernel: 4.4.0-36-generic x86_64 (64 bit)
           Desktop: N/A Distro: Peppermint Seven
Machine:   System: Dell product: Inspiron 1501
           Mobo: Dell model: 0UW744 Bios: Dell v: 2.6.3 date: 12/07/2007
CPU:       Single core AMD Turion 64 Mobile MK-36 (-UP-) cache: 512 KB
           speed/max: 800/2000 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] RS482M [Mobility Radeon Xpress 200]
           Display Server: X.Org 1.18.3 drivers: ati,radeon (unloaded: fbdev,vesa)
           Resolution: 1280x800@60.96hz
           GLX Renderer: Gallium 0.4 on ATI RS480 GLX Version: 2.1 Mesa 11.2.0
Audio:     Card Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
           driver: snd_hda_intel
           Sound: Advanced Linux Sound Architecture v: k4.4.0-36-generic
Network:   Card-1: Broadcom BCM4311 802.11b/g WLAN driver: b43-pci-bridge
           IF: wlan0 state: down mac: <filter>
           Card-2: Broadcom BCM4401-B0 100Base-TX driver: b44
           IF: eth0 state: down mac: <filter>
Drives:    HDD Total Size: 60.0GB (21.4% used)
           ID-1: /dev/sda model: SAMSUNG_HM060HI size: 60.0GB
Partition: ID-1: / size: 9.1G used: 5.7G (66%) fs: ext4 dev: /dev/sda5
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 57.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 168 Uptime: 13 min Memory: 547.8/1873.0MB
           Client: Shell (bash) inxi: 2.2.35
[close]
Cheers  ;)

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26466
  • Karma: 2884
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Boot time issues
« Reply #4 on: September 15, 2016, 02:08:30 pm »
What happens if you uninstall apparmor
Code: [Select]
sudo apt-get remove --purge apparmor apparmor-notify
does that speed up booting ?
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline Bigoeuf

  • Trusted User
  • Member
  • *****
  • Posts: 175
  • Karma: 23
  • New Forum User
    • View Profile
  • Peppermint version(s): 8 & 7 (64bit)
Re: Boot time issues
« Reply #5 on: September 15, 2016, 04:43:10 pm »
It almost certainly would Mark - however we have been round this buoy before in this topic:
 Excessively slow startup in Peppermint 7
(https://forum.peppermintos.com/index.php/topic,4094.0.html)

...............................................

 
I too have a 'Slow Boot' - its about 60 secs, & that is with Samba removed.................................
(it was about 77secs before removal).

Also its highly likely that my original boot time was even longer than 77 secs as I had earlier removed & purged  btrfs-tools...............................

I also tried the Apparmor disable mod as posted by VinDSL in this topic:

BTW, here's my /etc/default/grub file ...

Code: [Select]
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="elevator=deadline apparmor=0 quiet splash init=/lib/systemd/systemd-bootchart"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

I didn't remove AppArmor.  I just disabled it on the kernel boot command line.   ;)

I did this because my 'dmesg.' output showed that apparmor was taking about 15 secs & indeed my boot time dropped by 15 secs on re-boot. I felt comfortable doing this as Mark had posted:

...............maybe try unistalling apparmor .. which IMHO isn't necessary anyway............

.....................................



I didn't remove it because you later posted this:

As with everything else it's all about paranoia levels .. me personally, I removed it because I kept getting error messages in the kern.log which was throwing up popups.

There is a way to stop it reporting the errors via popups, but I figured what the hell, Linux is secure enough for me anyway.

As for what's **right** for you .. well that's not my call, I just showed how, I make no calls on whether you should or not that's your decision to make ;)

And I don't have enough knowledge to make that call so I left it alone.

So there we are - Catch 22 ey? However like I said in the OP could you help me understand what the apparmor entries mean & is there anything I can do to rectify/eliminate them & maybe that would bring the boot time down?

Cheers  :)

Offline Slim.Fatz

  • Global Moderator
  • Veteran
  • *****
  • Posts: 1916
  • Karma: 506
  • Where's the mouse?
    • View Profile
  • Peppermint version(s): Peppermint 7, 8.5 & 10 - 64bit
Re: Boot time issues
« Reply #6 on: October 06, 2016, 07:12:26 am »
Hi Bigouef,

I would suggest trying PCNetSpec's last suggestion: removing apparmor and apparmor-notify. I did this at least three months ago and have had no problems.  8)

If you are very paranoid about not having it installed, try removing it temporarily and perform one or two reboots to see if it speeds up your boot time. Note the results, reinstall the two packages and report your findings here.  ;)

Regards,

-- Slim
"Life first -- Peppermint a close 2nd!" -- Zeb

Tread lightly: Fluxbox, JWM, i3, Openbox, awesome

Offline Bigoeuf

  • Trusted User
  • Member
  • *****
  • Posts: 175
  • Karma: 23
  • New Forum User
    • View Profile
  • Peppermint version(s): 8 & 7 (64bit)
Re: Boot time issues
« Reply #7 on: October 13, 2016, 06:29:31 pm »
Hello Slim
If you look at this portion of my post above you will see that I have effectively done this already & indeed it does work - the only reason I haven't made it permanent is because I don't fully understand apparmor & what the implications of removing it will be (I may get round to researching it a bit more & then do it  ;)):

"I also tried the Apparmor disable mod as posted by VinDSL in this topic:

BTW, here's my /etc/default/grub file ...

Code: [Select]
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="elevator=deadline apparmor=0 quiet splash init=/lib/systemd/systemd-bootchart"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

I didn't remove AppArmor.  I just disabled it on the kernel boot command line.   ;)

I did this because my 'dmesg.' output showed that apparmor was taking about 15 secs & indeed my boot time dropped by 15 secs on re-boot."

Offline Slim.Fatz

  • Global Moderator
  • Veteran
  • *****
  • Posts: 1916
  • Karma: 506
  • Where's the mouse?
    • View Profile
  • Peppermint version(s): Peppermint 7, 8.5 & 10 - 64bit
Re: Boot time issues
« Reply #8 on: October 14, 2016, 02:13:40 am »
Hi Bigouef,

For info about apparmor check out this wikipedia article. There are other internet descriptions and directions concerning usage of it, but put simply: it is highly unlikely that you will need it for software that you install from our standard repositories. It is more used for software that is obtained from sources that might be less trusted or secure and permits you to restrict what that software can do. You need to set up "profiles" to achieve this.

If you are interested there is another piece of software that can do similar things: firejail (usually used together with its GUI interface package firetools). I use these but that does not mean that they are better. I find them relatively easy to use and they do not impact my system performance the way that apparmor did.  ;)

I hope that this helps.  8)

Regards,

-- Slim
"Life first -- Peppermint a close 2nd!" -- Zeb

Tread lightly: Fluxbox, JWM, i3, Openbox, awesome

Offline zebedeeboss

  • Global Moderator
  • Hero
  • *****
  • Posts: 3221
  • Karma: 598
  • Life first... Peppermint a close 2nd :)
    • View Profile
  • Peppermint version(s): P10 / P9 Respin
Re: Boot time issues
« Reply #9 on: October 14, 2016, 02:49:51 am »
Hi Bigouef,

I would suggest trying PCNetSpec's last suggestion: removing apparmor and apparmor-notify. I did this at least three months ago and have had no problems.  8)
Regards,

-- Slim

For the record - so did I and I have suffered no ill effect by disabling it. However, my paranoia levels are virtually non existant...

Regards Zeb...
Be Kind Whenever Possible...   It is Always Possible - Dalai Lama

P10r x64 Desktop - AMD Threadripper 2950X - 64Gb RAM - NVIDIA RTX2080Ti 11Gb - 2 x 27" 4k

Offline Bigoeuf

  • Trusted User
  • Member
  • *****
  • Posts: 175
  • Karma: 23
  • New Forum User
    • View Profile
  • Peppermint version(s): 8 & 7 (64bit)
Re: Boot time issues
« Reply #10 on: February 26, 2017, 06:38:59 pm »
Hi Bigouef,

I would suggest trying PCNetSpec's last suggestion: removing apparmor and apparmor-notify. I did this at least three months ago and have had no problems.  8)
Regards,

-- Slim

For the record - so did I and I have suffered no ill effect by disabling it. However, my paranoia levels are virtually non existant...

Regards Zeb...


Perhaps you should be a Dylan rather than a Zebedee then lol  :D


Yep gonna give that a go - especially enlight of:

Hi Bigouef,

For info about apparmor check out this wikipedia article. There are other internet descriptions and directions concerning usage of it, but put simply: it is highly unlikely that you will need it for software that you install from our standard repositories. It is more used for software that is obtained from sources that might be less trusted or secure and permits you to restrict what that software can do. You need to set up "profiles" to achieve this.

If you are interested there is another piece of software that can do similar things: firejail (usually used together with its GUI interface package firetools). I use these but that does not mean that they are better. I find them relatively easy to use and they do not impact my system performance the way that apparmor did.  ;)

I hope that this helps.  8)

Regards,

-- Slim


Because I use Firejail too  ;)

Cheers Fellas  :)