Re: [Dorset] Very slow Desktop startup problem
Has anything changed recently regarding your Internet setup? If SOmetimes a lo.o.o.ong delay at bootup is associated with a DNS timeout. If something is trying to get a connection, and waiting for a minute before failing, that should show up in the system logs too. best regards, 웃 Victor Churchill, Netley Abbey, Southampton 07970 844083 On Mon, 1 Jul 2019 at 09:31, John Carlyle-Clarke wrote: > You could try using systemd-analyze [1] to see how the boot time breaks > down. > > [1] > > https://wiki.archlinux.org/index.php/Improving_performance/Boot_process#Using_systemd-analyze > > On Sun, 30 Jun 2019 at 18:46, C Wills wrote: > > > Hi All > > > > My wife's desktop PC running Mint 18.10 takes a very long time in > > starting approx 4-5mins, (it used to start in less than 1min). It's also > > slow in 'logging in' and if trying to copy pictures from a USB stick to > > her /Pictures/ folder it takes ages at each operation. > > It would appear that something is happening in start up that loops round > > and hogs memory. > > > > How can I find out what's happening during the start up process please? > > > > -- > > C A Wills > > -- > > Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 > > Check to whom you are replying > > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > > > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
You could try using systemd-analyze [1] to see how the boot time breaks down. [1] https://wiki.archlinux.org/index.php/Improving_performance/Boot_process#Using_systemd-analyze On Sun, 30 Jun 2019 at 18:46, C Wills wrote: > Hi All > > My wife's desktop PC running Mint 18.10 takes a very long time in > starting approx 4-5mins, (it used to start in less than 1min). It's also > slow in 'logging in' and if trying to copy pictures from a USB stick to > her /Pictures/ folder it takes ages at each operation. > It would appear that something is happening in start up that loops round > and hogs memory. > > How can I find out what's happening during the start up process please? > > -- > C A Wills > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Hi Clive, > It would appear that something is happening in start up that loops > round and hogs memory. What makes you say that. Have you see an indication that memory usage is high? What's the output of `free -m' once it's up and running and behaving slowly, e.g. copying pictures described above. > How can I find out what's happening during the start up process > please? `journalctl -b' will show journal entries since the last boot. You will be in less(1) so `f' goes forward a page, `b' backwards, and `q' quits. The lines at the start will all have `kernel:' in them as nothing else is running. Note the start time and page forwards until that changes to `systemd:' showing the first process has been started. How long is the gap between the two? You could continue to page forward looking to see if there's a significant gap in time where nothing appears to happen because everything is waiting on something, though it probably won't show anything given your overall description. > My wife's desktop PC running Mint 18.10 takes a very long time in > starting approx 4-5mins, (it used to start in less than 1min). What changed around that time? Have a look at /var/log/apt/history.log for packages that were upgraded just before it slowed down. If history.log is empty then history.1.gz, or 2..., may be the file to inspect. -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
[Dorset] FRARS Hamfest 2019.
Hi, I thought this might be of interest to some list members. The Flight Refuelling Amateur Radio Society's festival is 11th August this year, 9 a.m. to 3 p.m., at Cobham Sports and Social Club. ‘Indoor and outdoor areas full of radio, computing, and electronics traders’. Its post code is BH21 3DA but just ask Google about 9C2WQ2M9+R5 for a more accurate position. https://www.frars.co.uk/event/hamfest-2019/ -- Cheers, Ralph. -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
Re: [Dorset] Very slow Desktop startup problem
Further to Keith's suggestion, 'dmesg' may also hold some clues. You would be surprised what shows in there. On Sun, 30 Jun 2019 at 22:07, Keith Edmunds wrote: > My first move would be to check /var/log/syslog or /var/log/messages for > any disk errors. > -- > Linux Tips: https://www.tiger-computing.co.uk/category/techtips/ > > -- > Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 > Check to whom you are replying > Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ > New thread, don't hijack: mailto:dorset@mailman.lug.org.uk > -- Next meeting: BEC, Bournemouth, Tuesday, 2019-07-02 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk/ New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
