Hi
Your already root user, so the command to reboot would be;
systemctl reboot
If your going to use Tumbleweed, take your time and ask questions if not sure, forum users are here to help 
You need to assimilate yourself with openSUSE and discard the Ub* ways⌠
Thatâs gonna be a long journey of work. Thanks for your encouragement.
Only have good news:
ss@linux-2o2k:~> uname -r
4.11.2-2.g6088b54-default
ss@linux-2o2k:~> uname -a
Linux linux-2o2k 4.11.2-2.g6088b54-default #1 SMP PREEMPT Mon May 22 09:18:07 UTC 2017 (6088b54) x86_64 x86_64 x86_64 GNU/Linux
ss@linux-2o2k:~> su -
Password:
linux-2o2k:~ # **good news, it works now!**
Machine boots default in Kernel 4.11.2-2 in my original setup. I now have access to root. Thank you very much for this one.
Custom Kernel is the latest one under test. The one that Linus pulls out every Sunday. Is there another name in the house of Suse?
Hereâs what you ask for:
ss@linux-2o2k:~> zypper ar -f -g -n "repo-kernel-vanilla" http://download.opensuse.org/repositories/Kernel:/vanilla/standard/ openSUSE-kernel-vanilla
Root privileges are required for modifying system repositories.
ss@linux-2o2k:~> su -
Password:
linux-2o2k:~ # zypper ref
Repository 'Main Repository (NON-OSS)' is up to date.
Repository 'Main Repository (OSS)' is up to date.
Repository 'Main Update Repository' is up to date.
All repositories have been refreshed.
linux-2o2k:~ # zypper dup --from openSUSE-kernel-vanilla
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Repository 'openSUSE-kernel-vanilla' not found by its alias, number, or URI.
Use 'zypper repos' to get the list of defined repositories.
linux-2o2k:~ # zypper repos
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
--+----------------------------------+----------------------------+---------+-----------+--------
1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes
2 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes
3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes
4 | openSUSE-20170521-0 | openSUSE-20170521-0 | No | ---- | ----
5 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ----
6 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ----
linux-2o2k:~ #
linux-2o2k:~ # zypper lr -d
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+----------------------------------+----------------------------+---------+-----------+---------+----------+--------+-----------------------------------------------------------------------------------+--------
1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
2 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/oss/ |
3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
4 | openSUSE-20170521-0 | openSUSE-20170521-0 | No | ---- | ---- | 99 | yast2 | hd:///?device=/dev/disk/by-id/usb-Verbatim_TUFF_N_TINY_07073400D6443647-0:0-part1 |
5 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
6 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/tumbleweed/repo/oss/ |
linux-2o2k:~ #
Hi
Slow down look at where you are on the system⌠you need to be root user to add the repo⌠run the command to add at the # prompt, not the > oneâŚ
ss@linux-2o2k:~> su -
Password:
linux-2o2k:~ # zypper ar -f -g -n "repo-kernel-vanilla" http://download.opensuse.org/repositories/Kernel:/vanilla/standard/ openSUSE-kernel-vanilla
linux-2o2k:~ # zypper ref
linux-2o2k:~ # zypper dup --from openSUSE-kernel-vanilla
This is what Iâm getting now Malcom:
@linux-2o2k:~> su -
Password:
linux-2o2k:~ # zypper ar -f -g -n "repo-kernel-vanilla" http://download.opensuse
.org/repositories/Kernel:/vanilla/standard/ openSUSE-kernel-vanilla
Adding repository 'repo-kernel-vanilla' ..................................[done]
Repository 'repo-kernel-vanilla' successfully added
URI : http://download.opensuse.org/repositories/Kernel:/vanilla/standard
/
Enabled : Yes
GPG Check : Yes
Autorefresh : Yes
Priority : 99 (default priority)
Repository priorities are without effect. All enabled repositories share the sam
e priority.
linux-2o2k:~ # zypper ref
Repository 'Main Repository (NON-OSS)' is up to date.
Repository 'Main Repository (OSS)' is up to date.
Repository 'Main Update Repository' is up to date.
Retrieving repository 'repo-kernel-vanilla' metadata ------------------------\]
New repository or package signing key received:
Repository: repo-kernel-vanilla
Key Name: Kernel OBS Project <Kernel@build.opensuse.org>
Key Fingerprint: 4529410A B52F94C4 03BAB484 ECEEF210 03579C1D
Key Created: Wed Apr 22 08:25:51 2015
Key Expires: Fri Jun 30 08:25:51 2017 (expires in 37 days)
Rpm Name: gpg-pubkey-03579c1d-5537934f
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/? shows all options] (r): a
Retrieving repository 'repo-kernel-vanilla' metadata .....................[done]
Building repository 'repo-kernel-vanilla' cache ..........................[done]
All repositories have been refreshed.
linux-2o2k:~ # zypper dup --from openSUSE-kernel-vanilla
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Nothing to do.
linux-2o2k:~ # uname -r
4.11.2-2.g6088b54-default
linux-2o2k:~ #
Gotcha! Much easier than I thought. Changes are applied upon restart. Got the file there and it installs like a charm:
http://download.opensuse.org/repositories/Kernel:/vanilla/standard/x86_64/
Splash screen is better, but boots with some hesitation. Itâs OK for a release candidate. HDD and fans are not producing noise(s) like it does in *u.
uname -a
Linux linux-2o2k 4.12.0-rc2-1.gfe840ee-vanilla #1 SMP PREEMPT Mon May 22 10:03:10 UTC 2017 (fe840ee) x86_64 x86_64 x86_64 GNU/Linux
Thanks for help!
Hi
So when you update now, make sure you use (Only for Tumbleweed);
zypper ref
zypper dup --no-allow-vendor-change
This will ensure you remain on the vanilla kernel when it updates.
I have a problem with noise under Gnome desktop: HDD and fans are producing a very high pitch of noise when connecting to the web (intermittent almost every 2 minutes). Something to go crazy! It is worse under the lower one and not acceptable.
rpm -qa | grep -i kernel
kernel-default-4.11.1-1.2.x86_64
kernel-vanilla-4.12.rc2.52.g56fff1b-1.1.gb7d58d5.x86_64
kernel-firmware-20170511-1.1.noarch
Run top in a console and note CPU usage and what is using it. The fans are keeping the system cool and may indicate heavy CPU usage
Hmmmmm⌠I would say it is a kernel bug? Will see next time, but since I enabled my firewall (GUFW) rules it is better.
Possible a kernel issue since you run an experimental kernel. But even so top will show if any process is using an inordinate amount of CPU cycles. If running KDE there can be a period where a lot of file indexing happens but that should settle down after a while.
Unless it is an HP issue, this noisy bug was introduced in the Kernel 4.9 cycle.
Iâm using System Monitor to do so in Gnome, all I can say for now is that soffice.bin produces noise when open simultaneously with Gedit. To tell you the truth, all of this has got to do with data collection. May try later the scrip that removes commercial stuff in custom KernelâŚ
For the rest, it runs like a Swiss clock.
Regards,
Iâve spent some time tracking down disk noise. I changed disks and their access noise is louder than what I used previously. Baloo now looks to have a first run option where it indexes the lot. I never noticed this happening before i disabled it which suggests it does it slowly. MS last time I was around it did this another way - enable indexing and a message stating index being built popped up and it did this all in one go. It could take a few mins. KDE should settle down eventually but I have no idea how long it takes to complete itâs first run.
Once I had this out of the way I still had frequent disk noises that were occurring at regular intervals. This turned out to be down to ext4. Adding noatime to the fstab mount reduced the accesses a lot. I still need to look at nodiratime and relatime to see if these can help. There are also other mount options that may help.
When ext4 started doing this some time ago people on arch reported it as a bug but it turned out that ext4 was doing what it was supposed to do. Ext3 doesnât do it. Or at least didnât at the time.
The noisiest application in this respect seems to be firefox down to the fact in my case that user info is kept off $HOME. I canât be totally sure about that though. I use my new drives for the home directory. Itâs possible to see what disks are being accessed like this - grep for which ones are of interest.
iotop -obtqqq | grep md0
This area bugs me because I am sure it will wear my disks out ahead of time. Initially I thought it was baloo as per akonodi on kde4. I donât know if baloo file crawls in the same was as that did. I understand that the kernel emits a signal for higher level applications to use when the file system actually changes but none of the cataloguers might make any use of it. They clearly didnât in the past.