Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
08-01-2021, 12:11 AM
|
#1
|
Member
Registered: Jun 2020
Posts: 104
Rep: 
|
Slow Boot with Kernal Error : drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:34:pipe A] flip_done timed out
So I am getting all these time out errors on boot and stuff that is slowing my boot to a crawl as I wait for them to time out... I have found a number of threads saying to edit my grub...
Code:
The solution is to edit the file /etc/default/grub and modify the entry
from: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to: GRUB_CMDLINE_LINUX_DEFAULT="video=SVIDEO-1:d"
but doesn't this just hide the problem and not fix it? Is doing this the correct way to go about this.. or should I find another solution... maybe uninstall xserver-xorg-video-intel or something?
I'm am using a fresh install of BunsenLab on a old HP Notebook from 2013, HP Compaq 6710b Notebook
Last edited by questionsBot; 08-03-2021 at 04:41 PM.
|
|
|
08-01-2021, 03:48 AM
|
#2
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,336
|
Is xserver-xorg-video-intel's driver actually being used? It's mostly appropriate for hardware in the 14 years old and older range. With a laptop from 2013, most likely you shouldn't need xserver-xorg-video-intel installed.
Don't make us look up your hardware specs. Do:
Code:
sudo inxi -GSaz
pastebinit /var/log/Xorg.0.log
sudo journalctl -b | pastebinit
and paste the output here so we know what you have and what's happening.
|
|
1 members found this post helpful.
|
08-01-2021, 01:03 PM
|
#3
|
Member
Registered: Jun 2020
Posts: 104
Original Poster
Rep: 
|
https://i.postimg.cc/tRdzh0gb/IMG-20210801-032443.jpg
https://i.postimg.cc/Dy2P6CWX/IMG-20210801-032519.jpg
I ended up doing the grub loader thing AND removing "xserver-xorg-video-intel" boot is now pretty fast considering the laptop is 10 years old and has 2GB ram.....
Is this the correct way to fix this?
Quote:
Originally Posted by mrmazda
Do:
Code:
sudo inxi -GSaz
pastebinit /var/log/Xorg.0.log
sudo journalctl -b | pastebinit
and paste the output here so we know what you have and what's happening.
|
I'll post this when I get back home to the laptop.
Last edited by questionsBot; 08-01-2021 at 01:05 PM.
|
|
|
08-02-2021, 02:46 AM
|
#4
|
Member
Registered: Jun 2020
Posts: 104
Original Poster
Rep: 
|
sudo inxi -GSaz
Code:
System:
Host: SlowerOX Kernel: 4.19.0-17-amd64 x86_64 bits: 64
Desktop: Openbox 3.6.1 Distro: BunsenLabs GNU/Linux 10.5 (Lithium)
Graphics:
Device-1: Intel Mobile GM965/GL960 Integrated Graphics driver: i915
v: kernel
Display: server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1680x1050~61Hz
OpenGL: renderer: Mesa DRI Intel 965GM v: 2.1 Mesa 18.3.6
pastebinit /var/log/Xorg.0.log
sudo journalctl -b | pastebinit
Last edited by questionsBot; 08-03-2021 at 04:40 PM.
|
|
|
08-02-2021, 12:25 PM
|
#5
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,336
|
video=SVIDEO-1:d disables the the S-Video output. Most people never use it, so it doesn't get much testing. If you never use it, there isn't any point in keeping it enabled.
The journal does have clues to the possibility of delays, e.g.:
Code:
ntpd[522]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3)
From your location you might be better off with other NTP servers, such as those from pool.ntp.org. You can change them in /etc/systemd/timesyncd.conf.
Code:
sudo journalctl | grep fail
will return lines containing the string fail. will allow perusal of the journal for the current boot.
You can measure startup speed with systemd-analyze, either alone, or with either of the options blame or critical-chain.
Usually the amount of RAM has no impact on boot speed. Where it matters is when you use multiple applications open at the same time, and/or applications that are heavy RAM consumers, such as web browsers. The more RAM, the less the likelihood that swap will be needed. Using swap results in noticeable slowdowns.
|
|
1 members found this post helpful.
|
08-03-2021, 04:30 AM
|
#6
|
Member
Registered: Jun 2020
Posts: 104
Original Poster
Rep: 
|
systemd-analyze
Code:
Startup finished in 7.134s (kernel) + 42.095s (userspace) = 49.230s
graphical.target reached after 33.762s in userspace
systemd-analyze blame : http://paste.debian.net/1206415/
Code:
22.994s man-db.service
17.459s udisks2.service
12.469s NetworkManager-wait-online.service
10.854s ModemManager.service
8.701s dev-sda1.device
8.650s NetworkManager.service
7.939s alsa-restore.service
7.919s apt-daily.service
7.073s loadcpufreq.service
6.501s logrotate.service
5.955s wpa_supplicant.service
5.870s atd.service
5.629s lm-sensors.service
5.516s systemd-logind.service
5.513s rsyslog.service
2.975s networking.service
2.272s apparmor.service
2.156s polkit.service
2.048s systemd-rfkill.service
1.743s systemd-udevd.service
1.595s upower.service
1.283s lightdm.service
1.034s ntp.service
917ms systemd-journald.service
...
systemd-analyze critical-chain
Code:
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 @33.762s
└─multi-user.target @33.762s
└─hddtemp.service @33.507s +252ms
└─network-online.target @33.503s
└─NetworkManager-wait-online.service @21.034s +12.469s
└─NetworkManager.service @12.372s +8.650s
└─dbus.service @12.367s
└─basic.target @12.260s
└─sockets.target @12.260s
└─dbus.socket @12.260s
└─sysinit.target @12.207s
└─swap.target @12.206s
└─dev-disk-by\x2duuid-1fb9ed54\x2dc5d8\x2d4170\x2dbb5e\x2dd5830bbc867e.swap @11.970s +235ms
└─dev-disk-by\x2duuid-1fb9ed54\x2dc5d8\x2d4170\x2dbb5e\x2dd5830bbc867e.device @11.969s
sudo journalctl | grep fail
Code:
Aug 03 18:07:16 SlowerOX kernel: acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 03 18:07:16 SlowerOX kernel: tg3 0000:18:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Aug 03 18:07:21 SlowerOX kernel: wl: module verification failed: signature and/or required key missing - tainting kernel
Aug 03 18:07:24 SlowerOX systemd-udevd[254]: Process '/sbin/crda' failed with exit code 249.
Aug 03 18:07:33 SlowerOX systemd-udevd[259]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.
Aug 03 18:07:33 SlowerOX udisksd[418]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 03 18:07:36 SlowerOX ntpd[526]: error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 03 18:07:36 SlowerOX ntpd[526]: error resolving pool 1.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 03 18:07:37 SlowerOX ntpd[526]: error resolving pool 2.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 03 18:07:38 SlowerOX ntpd[526]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 03 18:08:05 SlowerOX dbus-daemon[793]: [session uid=1000 pid=791] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 03 18:08:05 SlowerOX dbus-daemon[793]: [session uid=1000 pid=791] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
sudo journalctl -b : http://paste.debian.net/1206417/
Code:
-- Logs begin at Tue 2021-08-03 18:07:16 AEST, end at Tue 2021-08-03 18:27:51 AEST. --
Aug 03 18:07:16 SlowerOX kernel: microcode: microcode updated early to revision 0xba, date = 2010-10-03
Aug 03 18:07:16 SlowerOX kernel: Linux version 4.19.0-17-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-3 (2021-07-18)
Aug 03 18:07:16 SlowerOX kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-17-amd64 root=UUID=808da460-f639-4119-a123-fdb3b5ab5fb2 ro video=SVIDEO-1:d quiet splash
Aug 03 18:07:16 SlowerOX kernel: x86/fpu: x87 FPU will use FXSAVE
Aug 03 18:07:16 SlowerOX kernel: BIOS-provided physical RAM map:
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007f7affff] usable
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x000000007f7b0000-0x000000007f7c53ff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x000000007f7c5400-0x000000007f7e7fb7] ACPI NVS
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x000000007f7e7fb8-0x000000007fffffff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed99fff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x00000000feda0000-0x00000000fedbffff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x00000000ffb00000-0x00000000ffbfffff] reserved
Aug 03 18:07:16 SlowerOX kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
Aug 03 18:07:16 SlowerOX kernel: NX (Execute Disable) protection: active
Aug 03 18:07:16 SlowerOX kernel: SMBIOS 2.4 present.
Aug 03 18:07:16 SlowerOX kernel: DMI: Hewlett-Packard HP Compaq 6710b /30C0, BIOS 68DDU Ver. F.15 01/15/2009
Aug 03 18:07:16 SlowerOX kernel: tsc: Fast TSC calibration using PIT
Aug 03 18:07:16 SlowerOX kernel: tsc: Detected 2194.466 MHz processor
Aug 03 18:07:16 SlowerOX kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Aug 03 18:07:16 SlowerOX kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Aug 03 18:07:16 SlowerOX kernel: last_pfn = 0x7f7b0 max_arch_pfn = 0x400000000
.....
From your location you might be better off with other NTP servers, such as those from pool.ntp.org. You can change them in /etc/systemd/timesyncd.conf
Code:
[Time]
NTP=pool.ntp.org
FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org
#RootDistanceMaxSec=5
#PollIntervalMinSec=32
#PollIntervalMaxSec=2048
I also tried with the fallback hashed out... but I'm still getting ntp errors?
sudo journalctl | grep fail
Code:
Aug 03 19:49:48 SlowerOX kernel: acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 03 19:49:48 SlowerOX kernel: tg3 0000:18:00.0: VPD access failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update
Aug 03 19:49:53 SlowerOX kernel: wl: module verification failed: signature and/or required key missing - tainting kernel
Aug 03 19:49:56 SlowerOX systemd-udevd[264]: Process '/sbin/crda' failed with exit code 249.
Aug 03 19:50:04 SlowerOX udisksd[410]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 03 19:50:07 SlowerOX ntpd[513]: error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 03 19:50:07 SlowerOX ntpd[513]: error resolving pool 1.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 03 19:50:08 SlowerOX ntpd[513]: error resolving pool 2.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 03 19:50:09 SlowerOX ntpd[513]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3)
Aug 03 19:50:24 SlowerOX dbus-daemon[652]: [session uid=1000 pid=650] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Aug 03 19:50:24 SlowerOX dbus-daemon[652]: [session uid=1000 pid=650] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Last edited by questionsBot; 08-03-2021 at 04:39 PM.
|
|
|
08-03-2021, 04:31 AM
|
#7
|
Member
Registered: Jun 2020
Posts: 104
Original Poster
Rep: 
|
looks like the man data base is almost as slow as my entire boot... can this be changed to only check once a week or something instead of every boot? Or maybe make it update 20 mins after boot?
I also disabled the ModemManager.service ... yes this computer has a dial up modem in it! Yeah.. I will not be using that.
Code:
systemctl disable ModemManager.service
systemctl stop ModemManager.service
Last edited by questionsBot; 08-03-2021 at 04:40 PM.
|
|
|
08-03-2021, 12:00 PM
|
#8
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,336
|
Please enclose your pastes in code tags, not quote tags. Code tags preserve the formatting of the original.
Quote:
Originally Posted by questionsBot
looks like the man data base is almost as slow as my entire boot... can this be changed to only check once a week or something instead of every boot? Or maybe make it update 20 mins after boot?
|
IIUC, this is where it's controlled:
Code:
# systemctl cat man-db.timer
# /lib/systemd/system/man-db.timer
[Unit]
Description=Daily man-db regeneration
Documentation=man:mandb(8)
[Timer]
OnCalendar=daily
AccuracySec=12h
Persistent=true
[Install]
WantedBy=timers.target
IIRC if you
Code:
# systemctl edit man-db.timer
to change from daily to weekly or monthly that should do it. Another option might be simply to:
Code:
# systemctl disable man-db.timer
This way would leave it alone until changed by package updates. It's the path I've been implementing lately even though I'm not sure of its efficacy.
|
|
1 members found this post helpful.
|
08-03-2021, 04:38 PM
|
#9
|
Member
Registered: Jun 2020
Posts: 104
Original Poster
Rep: 
|
I just disabled it. If the man pages update when you update the apps with update/upgrade then, that seems to be pretty much the same thing, right?
Code:
sudo systemctl disable man-db.timer
sudo systemctl stop man-db.timer
Quote:
Originally Posted by mrmazda
Please enclose your pastes in code tags, not quote tags. Code tags preserve the formatting of the original.
|
sorry... went though and edited my old posts.
Last edited by questionsBot; 08-03-2021 at 04:43 PM.
|
|
|
All times are GMT -5. The time now is 06:14 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|