Post the full pacman log, without it no indication what is happening in your install or how it possibly could pull in linux-next.
Adding a kernel does not change any how the original kernel boots, you just have 2 options in your bootloader.

But again, without logs no-one can see what actually is going on.
Logs:
https://kaosx.us/docs/

This was the output of the upgrade in Octopi:

Starting full system upgrade...

resolving dependencies...
looking for conflicting packages...
Package (16) Old Version New Version Net Change Download Size
core/cryptsetup 1.7.2-1 1.7.2-2 0.07 MiB 0.23 MiB
core/device-mapper 2.02.155-1 2.02.156-1 0.00 MiB 0.26 MiB
main/freetds 1.00-1 1.00.1-1 0.00 MiB 2.22 MiB
core/gettext 0.19.7-3 0.19.8.1-1 0.06 MiB 2.35 MiB
core/linux-firmware 20160602-1 20160609-1 0.56 MiB 36.24 MiB
core/linux-next 4.6.2-2 78.61 MiB 59.54 MiB
core/lvm2 2.02.155-1 2.02.156-1 0.02 MiB 1.01 MiB
core/make 4.2-3 4.2.1-1 0.00 MiB 0.40 MiB
main/mpd 0.19.15-1 0.19.16-1 0.00 MiB 0.26 MiB
core/netctl 1.11-1 1.12-1 -0.08 MiB 0.03 MiB
apps/nodejs 6.2.1-1 6.2.2-1 0.04 MiB 5.61 MiB
main/nvidia-bumblebee 364.19-1 367.27-1 0.71 MiB 6.16 MiB
main/nvidia-utils-bumblebee 364.19-2 367.27-1 -8.15 MiB 18.35 MiB
main/telepathy-qt5 0.9.6.1-2 0.9.7-1 -2.91 MiB 1.77 MiB
core/tzdata 2016d-1 2016e-1 0.00 MiB 0.21 MiB
main/youtube-dl 2016.05.30.2-1 2016.06.12-1 0.02 MiB 1.13 MiB
Total Download Size: 135.77 MiB
Total Installed Size: 401.91 MiB
Net Upgrade Size: 68.95 MiB

:: Retrieving packages...

tzdata-2016e-1-x86_64 
device-mapper-2.02.156-1-x86_64 
cryptsetup-1.7.2-2-x86_64 
gettext-0.19.8.1-1-x86_64 
linux-firmware-20160609-1-x86_64 
lvm2-2.02.156-1-x86_64 
make-4.2.1-1-x86_64 
netctl-1.12-1-x86_64 
linux-next-4.6.2-2-x86_64 
freetds-1.00.1-1-x86_64 
mpd-0.19.16-1-x86_64 
nvidia-utils-bumblebee-367.27-1-x86_64 
nvidia-bumblebee-367.27-1-x86_64 
telepathy-qt5-0.9.7-1-x86_64 
youtube-dl-2016.06.12-1-x86_64 
nodejs-6.2.2-1-x86_64 
checking keys in keyring 
checking package integrity 
loading package files 
checking for file conflicts 
checking available disk space 

:: Processing package changes...

upgrading tzdata 
upgrading device-mapper 
upgrading cryptsetup 
upgrading freetds 
upgrading gettext 
upgrading linux-firmware 
upgrading lvm2 
upgrading make 
upgrading mpd 
upgrading netctl 
upgrading nodejs 
installing linux-next 
>>> Updating module dependencies. Please wait ...
>>> Generating initial ramdisk, using mkinitcpio. Please wait...
==> Building image from preset: /etc/mkinitcpio.d/linux-next.preset: 'default'
-> -k /boot/vmlinuz-linux-next -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-next.img
==> Starting build: 4.6.2-2-next
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-next.img
bsdcpio: Failed to set default locale
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-next.preset: 'fallback'
-> -k /boot/vmlinuz-linux-next -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-next-fallback.img -S autodetect
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-next-fallback.img
Optional dependencies for linux-next
upgrading nvidia-utils-bumblebee 
upgrading nvidia-bumblebee 
cat: /lib/modules/extramodules-4.6/version: No such file or directory
upgrading telepathy-qt5 
upgrading youtube-dl 

:: Running post-transaction hooks...

Install DKMS modules
==> No kernel 4.6.2-2-next headers. You must install them to use DKMS!
Creating temporary files...
Updating the info directory file...
Updating the desktop file MIME type cache...

Command finished OK!
``

Sorry, that is not a pacman.log
Best use Octopi then (again, see the link to the docs page to give useful info).
Octopi > Tools > SysInfo
paste the link that returns here. Output so far shows no explanation why linux-next was updated/installed

Issue for Nvidia failing is found, please update (after making sure your mirror is synced).

Still would like to see your SysInfo for linux-next

Octopi > Tools > SysInfo gives me a little windows with the following text:
Error: "\xE2" on US-ASCII

I'm trying to sync my mirrors but I'm getting "'main' is not synced." (but "is synced." for 'core' and 'apps'). sudo pacman -Syy downloads something for core, main and apps and sudo pacman -Syu says "is up to date" for core, main and apps, but I keep getting "'main' is not synced." in Octopi.

If useful, I can post my /var/log/pacman.log

Vlad.

Edit: Just after posting "'main' is not synced." in Octopi disapeared. I'll try and report back.

Ok. Nvidia is working again after update. Thanks.

I'm still getting Error: "\xE2" on US-ASCII from Octopi > Tools > SysInfo after reboot, but everything seems to be working fine.

Vlad.

pacman has no say over when the mirror you use syncs with the main mirror, that is why the tool mirror-check is build into octopi. Updating a system on a (partial) unsynced is just not an option in a rolling distro.
Some mirrors are set to run a cron job hourly, others 4-6 times a day, KaOS has no control over that.

Petty SysInfo tool is showing issues, probably due to not supported language/characters.
But yes, full pacman.log might help figuring why linux-next was added.
And add the output of pacman -Qm
(DKMS message in octopi...)

Ok. pacman log is in https://paste.kde.org/pjxkzlogx and the output of pacman -Qm is:

brutalchess 0.5.2-2
dkms 2.2.0.3+git151023-1
exfat-utils 1.2.4-1
fping 3.13-1
franz 3.0.2-1
hstr 1.19-1
libcurl-compat 7.49.0-1
nbwmon 0.3.1-1
owncloud-client 2.2.1-1
performous 1.0-1
performous-freesongs 20100713-1
photoqt 1.4-1
pulseaudio-equalizer 2.7.0.2-1
putty 0.67-1
samsung-uld-printer 1.00.36_00.91-1
speedtest-cli 0.3.4-1
spotify 1.0.31-1
swh-plugins 0.4.15-1
vscode 1.1.1-1
xdm 5.0.47-1

Vlad.

That is a lot of packages not from the repos.....
What is the output of:

pacman -Qi dkms

Where did you gate all these packages from? Self compiled?

  • vlad replied to this.

    Thank you for the help in advance,

    I have been using KAOS for a few months now and I have not had any problems until now.

    I also updated almost immediately after it came out and now the exact same thing happened to me. I cannot get past the initial boot stage before the screen goes dark, any help or ideas would be appreaciated.

    Marlan

      marlan
      You will have to be a lot clearer then this to be able to help you.
      What exact same thing? You also have all these unsupported, non KaOS repo packages installed?

      I also updated almost immediately after it came out

      What is 'it'?
      You have nvidia issues?
      If non of those, then please open a new topic and explain your issue.

        demm pacman -Qi dkms

        Output of pacman -Qi dkms:
        Name : dkms
        Version : 2.2.0.3+git151023-1
        Description : Dynamic Kernel Module Support
        Architecture : x86_64
        URL : http://linux.dell.com/dkms/
        Licenses : GPL2
        Groups : None
        Provides : None
        Depends On : bash kmod gcc make patch
        Optional Deps : linux-headers [installed]
        Required By : None
        Optional For : None
        Conflicts With : None
        Replaces : None
        Installed Size : 172.00 KiB
        Packager : Unknown Packager
        Build Date : Mon Jun 20 12:43:01 2016
        Install Date : Mon Jun 20 12:43:09 2016
        Install Reason : Explicitly installed
        Install Script : Yes
        Validated By : None

        I got all of them from KCP (the packages listed with pacman -Qm).

        Vlad.

        • demm replied to this.

            marlan
            As demm says, you need to provide more information so others can understand what's happening in your case. I'm being able to login to KDE (past the screen goes dark), so not exactly the same thing.

            Anyway, when I was setting up nvidia on my laptop, I was stuck on (probably) the same point as you are now. Deleting (renaming) /etc/X11/xorg.conf and rebooting solved the problem for me.

            Hope it helps.

            Vlad.

              vlad
              Al points to dkms pulling in linux-next somehow. Not a KaOS maintained package so nothing I can do about it.

                It seems that nvidia-bumblebee is not compatible with Linux kernel 4.6. I need to uninstall bumblebee to upgrade KaOS 2016.06. After updated, you can no longer install bumblebee in KaOS.

                :: The following package cannot be upgraded due to unresolvable dependencies:

nvidia-bumblebee

:: nvidia-bumblebee: requires linux

                In terminal

                $ sudo pacman -S nvidia-bumblebee
a resolver dependências...
atenção: não é possível resolver "linux<4.6", uma dependência de "nvidia-bumblebee"
:: O seguinte pacote não pode ser actualizado devido a dependências não resolvidas:
      nvidia-bumblebee

:: Deseja ignorar o pacote acima para esta atualização? [s/N] 

erro: falhou ao preparar a transação (não foi possível cumprir as dependências)
:: nvidia-bumblebee: exige linux<4.6
                • demm replied to this.