Never seen that mirror before? And why is it in our mirror list?
Continued through the whole package list with majority of packages throwing that message.
That is a US Manjaro mirror and should be up-to date: http://repo.manjaro.org/
Well, unless your running on the unstable branch, that one is still out-of-date on that mirror.
Try changing your default mirror with: sudo pacman-mirrors -g
When you have a Manjaro mirror issue that command usually fixes it.
Since the updates of 2016-03-22, I am having unusual contents at boot screen. The screen shots are attached.
During updates what Octopi displayed is mentioned below for reference.
Is your system not booting up?
The virtualbox-guest-dkms package should have taken care of itself, this is not an issue.
Your monitor’s native resolution is not supported by your graphics cards supported VBE resolutions, this is the reason for the blue lines instead of the graphics splash showing.
As for the other errors, those are GPU backlight related, the thing that concerns me is plymouth requiring a password.
Do you have any of your hard drive partitions encrypted somehow?
Can you please give me the output of systemctl status systemd-modules-load.service?
This will give me an idea where to look for the issue.
I can boot the system and haven’t found any issue in last 4-5 days except the additional lines while booting.
My laptop is 15.6" Dell Vostro 1550 with onboard Intel graphics and is connected with external 24" LG monitor. Sometimes the duel head set up is messed up but I can rearrange it. The laptop is without backlit keys. Since installation in Nov 2015, I always get text boot, never had boot splash screen.
I never have encripted any of my hard disk partitions.
The output of systemctl status systemd-modules-load.service is
[jagdeesh@jld-lap-ntrr ~]$ systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2016-03-27 10:03:35 IST; 1h 16min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 169 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 169 (code=exited, status=1/FAILURE)
Mar 27 10:03:35 jld-lap-ntrr systemd-modules-load[169]: Inserted module 'vboxnetflt'
Mar 27 10:03:35 jld-lap-ntrr systemd-modules-load[169]: Inserted module 'vboxpci'
Mar 27 10:03:35 jld-lap-ntrr systemd-modules-load[169]: Inserted module 'nfs'
Mar 27 10:03:35 jld-lap-ntrr systemd-modules-load[169]: Failed to find module 'vboxguest'
Mar 27 10:03:35 jld-lap-ntrr systemd-modules-load[169]: Failed to find module 'vboxsf'
Mar 27 10:03:35 jld-lap-ntrr systemd-modules-load[169]: Failed to find module 'vboxvideo'
Mar 27 10:03:35 jld-lap-ntrr systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Mar 27 10:03:35 jld-lap-ntrr systemd[1]: Failed to start Load Kernel Modules.
Mar 27 10:03:35 jld-lap-ntrr systemd[1]: systemd-modules-load.service: Unit entered failed state.
Mar 27 10:03:35 jld-lap-ntrr systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
[jagdeesh@jld-lap-ntrr ~]$
I posted only because of failure warning in red at the time of booting. If that is not much serious, I can continue and you need not waste much time.
No problem for the time required or even if you could not reply.
I always do real installations with no external screen attached and thereafter also several times booted without external screen, but never had boot splash. In fact I used to think that Netrunner Rolling is like Debian in this matter. Netrunner 14.2-64bit is at sda3 on this laptop which is also booting in vorbos mode since @ 6 months though SolydK-64bit on sda1 boots with butiful splash screen…does not matter much.
Virtualbox is not a must for me. Not in hurry to remove it as there is no other problem. If removed, will post a reply regarding any change in boot.
Did the live media also not have the plymouth boot splash?
I ask because on a bios based systems the live media uses syslinux, where as the installed system would use grub2.
These use different methods for determining resolution, syslinux can use modes that are not supported by vbe, grub2 can not.
However, in UEFI mode the situation would be different.
How your drives are partitioned, and which distribution you have handling grub and it’s settings, could be what is causing your issues with the plymouth boot splash.
Live media gives boot splash after ‘Faild’ warnings (as attached) and after a long time (@ 10 min).Moreover I could not login today even with non-free drivers, but this is just for info , not for investigation as the iso is of 2015-11.
I think, this laptop-Dell Vostyro-1550 does not have UEFI, it was purchased in Aug 2012 which was having Ubuntu preinstalled.
[/code]
The grub is of Netrunner 14.2, version 2.02~beta2-9Ubuntu1.7
It is just to respond to your query, trouble shooting is not a must. I can live without boot splash.
I looked at the screenshot and your having an issue with logind.
Netrunner Rolling is based on Manjaro which uses systemd to start and stop services.
Netrunner 14.x was based on Ubuntu 14.04 which was still using upstart.
Are you using any shared partitions between the installed distributions?
Could you provide the output of the following command:
sudo systemctl status systemd-logind.service
Could you also provide the contents of your /boot/grub/grub.cfg file that is being used by the installed version of grub (Netrunner 14.2, version 2.02~beta2-9Ubuntu1.7).
I removed ‘VirtualBox’ on 28-03-2016 (in all 5 packages), thereafter the ‘Failed’ warnings at boot have gone and getting the ususl text boot with a single progress bar, which I used to get since installation in Nov 2015. The screenshots are attached.
Regarding the boot splash, as that problem is not due to 2016-03-22 updates, but since installation in Nov 2015, I shall start a new thread, pl. treat this one as solved for me.
