What is the command line that enabled the latest Kernel or 4.12 in Tumbleweed?
Hi
Add one of the kernel ‘standard’ repos… down here;
http://download.opensuse.org/repositories/Kernel:/
Head, stable or vanilla… if you break it, you fix it… 
Or are you wanting to compile your own?
I don’t get it. Which one is Kernel 4.12? Is there a set of command lines that do the work like in Ubuntu? How to add 4.12 to repo would be the question? How to know to version of tumbleweed I run?
Hi
It’s still an rc release, there are no version numbers for Tumbleweed, it’s a snapshot number (cat /etc/os-release)
The 4.12 rc2 is in vanilla repo;
zypper ar -f -g -n "repo-kernel-vanilla" http://download.opensuse.org/repositories/Kernel:/vanilla/standard/ openSUSE-kernel-vanilla
zypper ref
zypper dup --from repo-kernel-vanilla
I just don’t believe it! I have one PW only and I’m stuck with that message on every attempt::
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:
su: Authentication failure
ss@linux-2o2k:~>
At least I have the command lines to do so. Thanks for replying. Is it su or su -? Should I do it before or after (the way it is shown)?
Hi
As in did you set the admin password the same as you user on install? Always use su - (to set the environment variables)
Try;
sudo -i
passwd
The openSUSE sudo implementation is not like the Ub* hold your hand version.
Here’s what the terminal returns:
ss@linux-2o2k:~> sudo -i
sudo: effective uid is not 0, is /usr/bin/sudo on a file system with the 'nosuid' option set or an NFS file system without root privileges?
ss@linux-2o2k:~> su -
Password:
su: Authentication failure
ss@linux-2o2k:~>
You seem to use the wrong root passwd. And that is already subject of another thread of you https://forums.opensuse.org/showthread.php/524973-Torguard-app-installation-need-help?p=2823957#post2823957
As long as that issue is not solved, you can not install anything, nor add repos, etc., etc. In short, you can not manage your system.
To check one suggestion from the message of sudo, check:
ls -l /usr/bin/ | grep rws
ss@linux-2o2k:~> ls -l /usr/bin/ | grep rws
-rwsr-x--- 1 root root 52336 Oct 16 2016 at
-rwsr-xr-x 1 root shadow 50752 Mar 5 11:56 chfn
-rwsr-xr-x 1 root shadow 41472 Mar 5 11:56 chsh
-rwsr-x--- 1 root root 55944 Apr 7 08:02 crontab
-rwsr-xr-x 1 root shadow 19336 Mar 5 11:56 expiry
-rwsr-x--- 1 root root 31552 Oct 16 2016 fusermount
-rwsr-xr-x 1 root shadow 67232 Mar 5 11:56 gpasswd
-rwsr-xr-x 1 root root 43112 Apr 25 03:07 mount
-rwsr-xr-x 1 root root 36792 Mar 5 11:56 newgrp
-rwsr-xr-x 1 root shadow 51264 Mar 5 11:56 passwd
-rwsr-xr-x 1 root root 26648 Oct 16 2016 pkexec
-rwsr-xr-x 1 root root 30856 Apr 25 03:07 su
-rwsr-xr-x 1 root root 142840 Mar 10 15:09 sudo
-rwsr-xr-x 1 root root 30824 Apr 25 03:07 umount
ss@linux-2o2k:~>
Is there something I did wrong during the installation? Should I redo the installation… The thread you have mention is not really about PW, but like you say, I can apply or make any modifications to the system. All I can say is that I was dual boot with Win ten and LTS. I did something I never do: Deleted sda1 (system reserved) and made the fresh install on sda2. Kept sda3 to 7.
It may be this bug though:
http://bugzilla.opensuse.org/show_bug.cgi?id=1040041
Try to login as root to text mode (Ctrl+Alt+F1), does this work?
You could run zypper there.
This is the TTY terminal, but I did not try zypper. I was asking for the PW and was able to do sudo reboot, it reboots. I guess the PW works then. Indeed it is set to enlightenment and I’m on Kernel 4.11
Ok, but if you login as root, you don’t need to use sudo in the first place… 
Anyway, seems like you are affected by the mentioned bug.
I would suggest trying to boot an older kernel then instead of installing an unstable one which might not even have this bug fixed yet.
You should find other kernels in “Advanced Options” in the boot menu.
Unfortunately, the latest version of Tumbleweed does not have this option: There is only one Kernel on-board 4.11.1. Recovery mode did not help.
ss@linux-2o2k:~> su -
Password:
su: Authentication failure
ss@linux-2o2k:~>
Machine is AMD A10 9630P/DDR4
It does.
But there probably was a kernel rebuild which replaced the previous 4.11.1 kernel (and older ones were already uninstalled).
Well, then login as root and you won’t need sudo or su.
Or maybe try a different desktop, e.g. IceWM, maybe su/sudo works there. Just logout and you should get to the login screen with an option to choose.
PS: you should be able to install a “working” kernel with:
rpm -i http://download.opensuse.org/repositories/home:/tiwai:/bnc1040041/standard/x86_64/kernel-default-4.11.2-2.1.g6088b54.x86_64.rpm
Or, if it’s a 32bit installation:
rpm -i http://download.opensuse.org/repositories/home:/tiwai:/bnc1040041/standard/i586/kernel-default-4.11.2-2.1.g6088b54.i586.rpm
This looks OK.
Your other thread also is stuck on not being able to “become root” with su -.
I repeat: as long as that is not solved, you can not do the things you want (or are advised to do) inn both threads.
And Wolfi323’s suggestion is also an important test.
And doing a new installation is a useless and brainless thing to do. As long as you (and we) do not know what is wrong, repeating the same thing will only lead to the same problem. That is what computers are good at: doing exactly the same thing again and again and again. We humans are able (or should be able) to use our brains and find out what is wrong. After that we can decide what to do to repair. And most probably a new installation will not be part of it.
One thing at the time. This thread is about Custom Kernel and wish to run it without having Canonical Partners in my back. Root works in IceWM environment, but I got this message:
linux-2o2k:~ # zypper dup --from repo-kernel-vanilla
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Repository 'repo-kernel-vanilla' not found by its alias, number, or URI.
Use 'zypper repos' to get the list of defined repositories.
linux-2o2k:~ #
Made this modification to the first command line and it did not help:
zypper ar -f -g -n "repo-kernel-vanilla" http://download.opensuse.org-**tumbleweed**/repositories/Kernel:/vanilla/standard/ openSUSE-kernel-vanilla
Where is the error? Will now go back to original desktop and try *2-.2.1
And what exactly do you mean with “Custom Kernel”?
There is no single command to “run” a custom kernel, you need to download the source code and compile it…
Root works in IceWM environment, but I got this message:
linux-2o2k:~ # zypper dup --from repo-kernel-vanilla
You named the repo “openSUSE-kernel-vanilla”, so you’d need to run “zypper dup --from openSUSE-kernel-vanilla”.
Made this modification to the first command line and it did not help:
zypper ar -f -g -n "repo-kernel-vanilla" http://download.opensuse.org-**tumbleweed**/repositories/Kernel:/vanilla/standard/ openSUSE-kernel-vanilla
You changed the URL (the server name to be precise). Of course this does not help, as that server does not exist.
Maybe post your repo list now to see what actual repos you added…
zypper lr -d
You might get away with using one click install from here as a sudo password should work without any problems. Or any other kernel from the same software page search. Be warned there are lots of them. Just search kernel. If you want even more click on the spanner and set include development but those aren’t supported.
https://software.opensuse.org/package/kernel-default
That is tumbleweeds default kernel. There is no need for support scripts on opensuse as yast or zypper will do it’s best to install what ever you choose to do. If you want to install additional kernel functionality/modules that has to be done long hand. Something I haven’t needed to do for a long time but instructions can be found on the web. In terms of the steps used it doesn’t seem to matter which disto these were written up for. Also if you want to build a complete kernel yourself it has to be done by hand but bear in mind that various distro’s play around with kernels and that a vanilla kernel may or may not work on just about any distro. You would be better off starting from an opensuse kernel and downloading the kernel development pattern. That can be done from yast patterns. Zypper’s too.
Some on here might not realise that ubuntu hijacks the root account so users use sudo all of the time. I tried the dam thing once and tried to set a root account up - looked to be ok but then found that it didn’t work even though it provided the facilities to do this at the time.
Personally I always create a separate root account when I install. The option on opensuse crops up when a user is added during install, deselect administration and it will then ask for a root password at the next stage. Doing this doesn’t prevent the use of sudo but does allow root usage for as long as some one is logged in as root saving typing sudo all of the time. When work as root is finished just enter in my case su john and that will take you back to your normal account. su = switch user and defaults to root if no name is given. There is no such animal as a super user.
John
[QUOTE=wolfi323;2823976]PS: you should be able to install a “working” kernel with:
rpm -i http://download.opensuse.org/repositories/home:/tiwai:/bnc1040041/standard/x86_64/kernel-default-4.11.2-2.1.g6088b54.x86_64.rpm
QUOTE]
Need to be root to do so, but works in the other desktop. Will reboot to see if change was applied?
s@linux-2o2k:~> rpm -i http://download.opensuse.org/repositories/home:/tiwai:/bnc1040041/standard/x
86_64/kernel-default-4.11.2-2.1.g6088b54.x86_64.rpm
warning: /var/tmp/rpm-tmp.lt9Yxu: Header V3 RSA/SHA256 Signature, key ID f6e74bf5: NOKEY
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission denied)
ss@linux-2o2k:~> su -
Password:
linux-2o2k:~ # rpm -i http://download.opensuse.org/repositories/home:/tiwai:/bnc1040041/standard/x86
_64/kernel-default-4.11.2-2.1.g6088b54.x86_64.rpm
warning: /var/tmp/rpm-tmp.kVFm9l: Header V3 RSA/SHA256 Signature, key ID f6e74bf5: NOKEY
Creating initrd: /boot/initrd-4.11.2-2.g6088b54-default
dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.11.2
-2.g6088b54-default 4.11.2-2.g6088b54-default
dracut: dracut module 'systemd-bootchart' will not be installed, because command '/usr/lib/systemd/s
ystemd-bootchart' could not be found!
dracut: *** Including module: bash ***
dracut: *** Including module: systemd ***
dracut: *** Including module: warpclock ***
dracut: *** Including module: systemd-initrd ***
dracut: *** Including module: i18n ***
dracut: Could not find FONT_MAP none!
dracut: *** Including module: drm ***
dracut: *** Including module: plymouth ***
dracut: *** Including module: btrfs ***
dracut: *** Including module: kernel-modules ***
dracut: *** Including module: resume ***
dracut: *** Including module: rootfs-block ***
dracut: *** Including module: terminfo ***
dracut: *** Including module: udev-rules ***
dracut: Skipping udev rule: 40-redhat.rules
dracut: Skipping udev rule: 50-firmware.rules
dracut: Skipping udev rule: 50-udev.rules
dracut: Skipping udev rule: 91-permissions.rules
dracut: Skipping udev rule: 80-drivers-modprobe.rules
dracut: *** Including module: dracut-systemd ***
dracut: *** Including module: haveged ***
dracut: *** Including module: usrmount ***
dracut: *** Including module: base ***
dracut: *** Including module: fs-lib ***
dracut: *** Including module: shutdown ***
dracut: *** Including module: suse ***
dracut: *** Including modules done ***
dracut: *** Installing kernel module dependencies and firmware ***
dracut: *** Installing kernel module dependencies and firmware done ***
dracut: *** Resolving executable dependencies ***
dracut: *** Resolving executable dependencies done***
dracut: *** Hardlinking files ***
dracut: *** Hardlinking files done ***
dracut: *** Stripping files ***
dracut: *** Stripping files done ***
dracut: *** Generating early-microcode cpio image ***
dracut: *** Constructing AuthenticAMD.bin ****
dracut: *** Store current command line parameters ***
dracut: Stored kernel commandline:
dracut: resume=UUID=e7f3cb62-8ddd-4370-8e82-9918a9a48825
dracut: root=UUID=dae0b262-0f18-4772-9b68-572f35b4ee26 rootfstype=btrfs rootflags=rw,relatime,space_cache,subvolid=257,subvol=/@,subvol=@
dracut: *** Creating image file '/boot/initrd-4.11.2-2.g6088b54-default' ***
dracut: *** Creating initramfs image file '/boot/initrd-4.11.2-2.g6088b54-default' done ***
linux-2o2k:~ #uname -r
4.11.1-1-default
linux-2o2k:~ # sudo reboot
Thanks again for replying!