LEAP 42.3 How do I run openSUSE on virtualized Raspberry Pi 2 with QEMU

April 6, 2018, 11:36 pm

≪ Previous: LEAP 42.3 using default subvolume Layout when installing on one of several existin partitions

Hi

I am running Leap 42.3 x64 (KDE desktop) fully updated.

I have run Rapbian with QEMU; it required a custom kernel to boot, which was readily available for download.

https://github.com/dhruvvyas90/qemu-rpi-kernel

Now where can I get a qemu-kernel for openSUSE??? If not, where can i get the instructions to build one myself.

Thanks
Emon

↧

TUMBLEWEED Guake is removed

April 7, 2018, 1:12 am

≫ Next: LEAP 42.3 How to resolve “npm-default: not found”?

≪ Previous: LEAP 42.3 How do I run openSUSE on virtualized Raspberry Pi 2 with QEMU

Hello Dears,

It's been more than 5 years than I'm using Guake as my default terminal emulator on daily basis.
after my last Tumbleweed upgrade "20180404" I noticed that it's removed and now I feel paralyzed without that!

I've tried to install it from CLI :
# zypper in guake
Loading repository data...
Reading installed packages...
'guake' not found in package names. Trying capabilities.
No provider of 'guake' found.
Resolving package dependencies...

Nothing to do.

and tried installing with 1 Click Install:
Software installation
Installation was only partially successful.
The following packages could not be installed

guake

Unfortunately I can't find any logs mentioning why this happens.

I would appreciate if anybody help me to find out what is the root cause of my errors and what breaks the package.

With Regards,
Arash

↧

LEAP 42.3 How to resolve “npm-default: not found”?

April 7, 2018, 1:18 am

≫ Next: TUMBLEWEED Desktop effects have been suspended by another application

≪ Previous: TUMBLEWEED Guake is removed

when I want to install npm package I see this error message:

Code:

npm install cody

Output is:

Code:

/usr/bin/npm: line 6: exec: npm-default: not found

And nano /usr/bin/npm Output is:

Code:

#!/bin/sh PROG=$(basename $0) PROG_VERSION=${NODE_VERSION:--default} exec ${PROG}${PROG_VERSION} "$@"

And
npm -v Output is:

Code:

/usr/bin/npm: line 6: exec: npm-default: not found

Any suggestions?

↧

TUMBLEWEED Desktop effects have been suspended by another application

April 7, 2018, 1:24 am

≫ Next: LEAP 42.3 Intel Core 2 Duo und Spectre / Meltdown

≪ Previous: LEAP 42.3 How to resolve “npm-default: not found”?

Problems
Yesterday, I switched my desktop system over from Leap 42.3 to Tumbleweed. Previously done my laptop and that worked fine, following instructions found here: https://www.techrepublic.com/article/how-to-upgrade-opensuse-leap-to-opensuse-tumbleweed (basically, swap out Leap repos for TW repos and zypper dup).
The only problem I have encountered on the desktop is with the NVidia card in the system, which worked fine under Leap. For some reason, desktop effects (KDE) keep getting suspended and using SHIFT+ALT+F12 doesn't switch them on but instead immediately produces the same message again (desktop effects have been suspended by another application). It would be helpful if it included some hint about which application was doing it. I am also seeing strange artifacts in the notification tray, unreadable text in that area, etc. I could live without desktop effects but not without working notifications.

Troubleshooting steps by me
To test, I quickly made a second user account to see if the problem was with the settings stored in my profile somewhere. The desktop behaved the same way for thew new user.

I then verified if I had used the correct NVidia repository for TW. This looks fine to me: https://download.nvidia.com/opensuse/tumbleweed

I uninstalled and reinstalled the NVidia driver using the methods described on this page: https://en.opensuse.org/SDB:NVIDIA_drivers (with reboots in between)
The problem remained the same.

Next, I thought I would give the Nouveau driver a go, to see if that had better results. Again, I removed the NVidia driver as per the instructions mentioned on the previous page, made sure the Nouveau driver wasn't blacklisted somewhere in /etc/modprobe.d and rebooted. After this, my login manager only produced a black screen with a mouse cursor on one of the two attached monitors.

To at least get a working desktop again, I reinstalled the NVidia drivers. This brought the login manager and KDE back to life.

Goals
What I would like to do, is one of the following (in order of preference):

Get the NVidia proprietary driver running correctly
Switch to Nouveau but with a working desktop
Switch back to Leap 42.3
Reinstall Leap 42.3 from scratch

I would appreciate your suggestions about the best course of action and how to get there successfully. The switch back to Leap throws very worrying dependency errors with resolutions involving the removal of modules related to accessing encrypted disks. Since I run encrypted LVM, I'm not sure I want to go that route...

Info
The card is:

Code:

hwinfo --gfxcard | grep Model

Model: "nVidia GK106 [GeForce GTX 645 OEM]"

If additional info is necessary, I will do my best to provide it of course. I'd appreciate your assistance since I am kind of stuck now. It's been a while since I had to troubleshoot graphics drivers on openSUSE. :\

↧

LEAP 42.3 Intel Core 2 Duo und Spectre / Meltdown

April 7, 2018, 1:56 am

≫ Next: TUMBLEWEED Create subvolume for /home in snapper

≪ Previous: TUMBLEWEED Desktop effects have been suspended by another application

Hallo,

seit dieser Woche ist es jetzt offiziell, dass es von Intel keine Patches mehr für meinen alten iMac geben wird. Wie muss ich damit umgehen? Ist der PC durch die Updates vom Betriebssystem und der Anwendungssoftware schon ausreichend geschützt? Noch sind doch gar keine Angriffsszenarien öffentlich? Dafür müsste der PC meines Wissens auch relativ lange laufen (weil der Speicher von vorne bis hinten ausgelesen wird?

--

Vielen Dank für Auskunft,
Felix

↧

TUMBLEWEED Create subvolume for /home in snapper

April 7, 2018, 4:32 am

≫ Next: TUMBLEWEED Bluetooth suddenly stopped working

≪ Previous: LEAP 42.3 Intel Core 2 Duo und Spectre / Meltdown

Hi!

Somehow during installation I must have said not to create /home in a separate volume, because right now it shows up in my snapshots, which I'm not too happy with, since I wouldn't want to revert the content of my home directory if the system is messed up...

Can I create the subvolume now, and get it out of the snapshots?

Thanks!

↧

TUMBLEWEED Bluetooth suddenly stopped working

April 7, 2018, 8:31 am

≫ Next: LEAP 42.3 leap 42.3 installed on thinkpad laptop

≪ Previous: TUMBLEWEED Create subvolume for /home in snapper

Hello,
I remember using Bluetooth before on this computer, but today when I tried to connect to my phone KDE just said “No Bluetooth adapters available”. The Bluetooth logo status light on my computer has turned off (I remember it being constantly on before).

Code:

$ lsusb | grep Blue 

Bus 003 Device 003: ID 0cf3:3004 Qualcomm Atheros Communications AR3012 Bluetooth 4.0

Code:

$ sudo rfkill list  

0: phy0: Wireless LAN 

       Soft blocked: no 

       Hard blocked: no 

1: hci0: Bluetooth 

       Soft blocked: no 

       Hard blocked: no

Code:

$ dmesg | grep -i blu 

[   22.590030] Bluetooth: Core ver 2.22 

[   22.590044] Bluetooth: HCI device and connection manager initialized 

[   22.590048] Bluetooth: HCI socket layer initialized 

[   22.590049] Bluetooth: L2CAP socket layer initialized 

[   22.590055] Bluetooth: SCO socket layer initialized 

[   24.884745] Bluetooth: hci0: don't support firmware rome 0x31010000 

[   32.308813] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 

[   32.308814] Bluetooth: BNEP filters: protocol multicast 

[   32.308817] Bluetooth: BNEP socket layer initialized

Code:

$ sudo hwinfo --bluetooth 

09: USB 00.0: 11500 Bluetooth Device                             

 [Created at usb.122] 

 Unique ID: eqBD.tx4ZIeIPK4B 

 Parent ID: uIhY.2DFUsyrieMD 

 SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-4/3-4:1.0 

 SysFS BusID: 3-4:1.0 

 Hardware Class: bluetooth 

 Model: "Qualcomm Atheros AR3012 Bluetooth 4.0" 

 Hotplug: USB 

 Vendor: usb 0x0cf3 "Qualcomm Atheros Communications" 

 Device: usb 0x3004 "AR3012 Bluetooth 4.0" 

 Revision: "0.01" 

 Driver: "btusb" 

 Driver Modules: "btusb" 

 Speed: 12 Mbps 

 Module Alias: "usb:v0CF3p3004d0001dcE0dsc01dp01icE0isc01ip01in00" 

 Driver Info #0: 

   Driver Status: ath3k is active 

   Driver Activation Cmd: "modprobe ath3k" 

 Driver Info #1: 

   Driver Status: btusb is active 

   Driver Activation Cmd: "modprobe btusb" 

 Config Status: cfg=new, avail=yes, need=no, active=unknown 

 Attached to: #7 (Hub)

Code:

$ bt-device -l      

** 

ERROR:lib/bluez/adapter.c:165:adapter_get_dbus_object_path: assertion failed: (ADAPTER_IS(self)) 

Aborted

Hope some of that command output helps.

↧

LEAP 42.3 leap 42.3 installed on thinkpad laptop

April 7, 2018, 8:48 am

≫ Next: Rejected posting to opensuse-factory

≪ Previous: TUMBLEWEED Bluetooth suddenly stopped working

# hwinfo --wlan
15: PCI 300.0: 0282 WLAN controller
[Created at pci.378]
Unique ID: y9sn.1M7X9Je0aV5
Parent ID: qTvu.J9rbDjpoNg4
SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:03:00.0
SysFS BusID: 0000:03:00.0
Hardware Class: network
Model: "Intel Centrino Advanced-N 6205 [Taylor Peak]"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x0085 "Centrino Advanced-N 6205 [Taylor Peak]"
SubVendor: pci 0x8086 "Intel Corporation"
SubDevice: pci 0xc220
Revision: 0x96
Driver: "iwlwifi"
Driver Modules: "iwlwifi"
Device File: wlan0
Features: WLAN
Memory Range: 0xf0c00000-0xf0c01fff (rw,non-prefetchable)
IRQ: 30 (no events)
HW Address: 8c:70:5a:c9:11:e8
Permanent HW Address: 8c:70:5a:c9:11:e8
Link detected: yes
WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153
WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62 5.64 5.66 5.68 5.7 5.745 5.765
WLAN encryption modes: WEP40 WEP104 TKIP CCMP
WLAN authentication modes: open sharedkey wpa-psk wpa-eap
Module Alias: "pci:v00008086d00000085sv00008086sd0000C220bc02sc80i00"
Driver Info #0:
Driver Status: iwlwifi is active
Driver Activation Cmd: "modprobe iwlwifi"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #9 (PCI bridge)

↧

Rejected posting to opensuse-factory

April 7, 2018, 12:41 pm

≫ Next: LEAP 42.3 Installed openSUSE on Legacy Mode. Now Can't Boot Windows in UEFI

≪ Previous: LEAP 42.3 leap 42.3 installed on thinkpad laptop

Hi,
I subscribed to opensuse-factory mailing list but my mail there was rejected. How can I get unblocked? I am not a spammer

Claes

↧

LEAP 42.3 Installed openSUSE on Legacy Mode. Now Can't Boot Windows in UEFI

April 7, 2018, 1:44 pm

≫ Next: TUMBLEWEED Trash is not accessible!

≪ Previous: Rejected posting to opensuse-factory

So I was installing openSUSE from a flash drive late one night and accidentally installed it in Legacy mode. Now when I want to go back to UEFI, Windows 10 will not boot up. A prompt appears, saying 'No bootable device found.' Before I realized I did it in Legacy mode, I thought I wrote over Windows 10. But looking at the partitions, the Windows file system is still there. My plans were to dual boot openSUSE and Windows 10, so if anyone has a solution for this problem it would be greatly appreciated. Let me know if you need more information.

↧

TUMBLEWEED Trash is not accessible!

April 7, 2018, 11:13 pm

≫ Next: TUMBLEWEED How do i debug Wicked and other networking tools??

≪ Previous: LEAP 42.3 Installed openSUSE on Legacy Mode. Now Can't Boot Windows in UEFI

This has bugged me for a while, I googled for days and have not yet found a solution.
What happened: When I click on Trash in nautilus, it shows "Sorry, could not display all the contents of "trash:///": The specified location is not supported."

What I did: I occasionally recover my system using backintime, I do full file system backup and recover except my home folder.
What I tried: I have Trash folder in ~/.local/share/, and I have /files and /info folders in my Trash folder. The permission is 700. I can use move to Trash from file manager, but I have to use terminal to go the ~/.local/share/files and rm to empty trash. I have tried other file manager other than nautilus, that I have the same problem, so it seems not to be the problem with the file manager. And I tried creating a new user, but the new user still cannot access to the Trash. So it seems to be some global setting.

Where is the setting that I can change the directory of my trash or get this fixed? PS: Desktop Environment: Gnome
Thanks

↧

TUMBLEWEED How do i debug Wicked and other networking tools??

April 8, 2018, 1:54 am

≫ Next: TUMBLEWEED Just updated TW now SMB daemon fails to start

≪ Previous: TUMBLEWEED Trash is not accessible!

i am recently finding that my wifi network spontaneously disconnects from the network. as a est i perform the ping command that pings the modem router and it gives me the error:

unreachable host. how do i go about stopping this from happening? it is anoying

↧

TUMBLEWEED Just updated TW now SMB daemon fails to start

April 8, 2018, 2:01 am

≫ Next: TUMBLEWEED "Dependency failed for Cryptography Setup" at boot

≪ Previous: TUMBLEWEED How do i debug Wicked and other networking tools??

Just updated today and now when I boot up SMB fails to start as a daemon. I can start both smbd and nmbd with the /i flag to run in foreground from a console but I am unable to start them via systemctl or from a console as a daemon, keeps saying

Code:

Becoming a daemon.

exit_daemon: STATUS=daemon failed to start: Failed to create session, error code 1

This was not happening prior to my update. Seems that the problem is in the daemon mode as it runs normally in interactive mode. Samba is showing as 4.8.0+git.19.f53c6c0aa6f-1.1

Anyone any ideas please?

Stuart

↧

TUMBLEWEED "Dependency failed for Cryptography Setup" at boot

April 8, 2018, 3:44 am

≫ Next: TUMBLEWEED systemsettings5 not working after update

≪ Previous: TUMBLEWEED Just updated TW now SMB daemon fails to start

Hi all,

I saw this pop up in other threads, but didn't find anything I could apply, or at least that I knew how to apply. So here is another thread...

I get this on boot:

Code:

[    **] A start job is running for dev-disk-by\x2duuid-d0129dc8\x2d17f1\x2d4393\x2d92b1\x2d993288330b06.device (1min 30s / 1min 30s[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-d0129dc8\x2d17f1\x2d4393\x2d92b1\x2d993288330b06.device.

[DEPEND] Dependency failed for Cryptography Setup for cr_sda1.

[DEPEND] Dependency failed for Local Encrypted Volumes.

so the thing waits 90 seconds, and then everything seems to boot fine.

Code:

# cat /etc/crypttab 

cr_sda1  UUID=d0129dc8-17f1-4393-92b1-993288330b06

Also, on a side note, I'm mounting an NFS partition, this is what's in fstab:

Code:

192.168.1.61:/share/nashome /mnt/nashome nfs4 defaults 0 0

and I get this at boot:

Code:

[FAILED] Failed to mount /mnt/nashome.

See 'systemctl status mnt-nashome.mount' for details.

[DEPEND] Dependency failed for Remote File Systems.

Once the system is up and I can log in I ran:

Code:

# systemctl status mnt-nashome.mount



● mnt-nashome.mount - /mnt/nashome

   Loaded: loaded (/etc/fstab; generated)

   Active: active (mounted) (Result: exit-code) since Sun 2018-04-08 11:22:17 BST; 19min ago

    Where: /mnt/nashome

     What: 192.168.1.61:/share/nashome

     Docs: man:fstab(5)

           man:systemd-fstab-generator(8)

  Process: 1276 ExecMount=/usr/bin/mount 192.168.1.61:/share/nashome /mnt/nashome -t nfs4 (code=exited, status=32)



Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

So, waiting a little time, also the NFS partition seems to be mounted... So why does it take so long to mount both?

Thanks a lot!

↧

TUMBLEWEED systemsettings5 not working after update

April 8, 2018, 4:32 am

≫ Next: TUMBLEWEED I accidentally broke KDE whilst rpm database was damaged

≪ Previous: TUMBLEWEED "Dependency failed for Cryptography Setup" at boot

Was on windows for a while and came back to 1000+ updates, after updating (just using the GUI method) systemsettings5 no longer works. Clicking on the Configure Desktop icon launches nothing and running systemsettings5 from terminal gives:

Code:

systemsettings5: symbol lookup error: systemsettings5: undefined symbol: _ZN10KWorkSpace14detectPlatformEiPPc

zypper lr -d

Code:

#  | Alias                               | Name                               | Enabled | GPG Check | Refresh | Priority | Type   | URI 

---+-------------------------------------+------------------------------------+---------+-----------+---------+----------+--------+-----------------------------------------------------------------------------------------------------+--------

 1 | download.opensuse.org-non-oss       | Main Repository (NON-OSS)          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/          

 2 | download.opensuse.org-oss           | Main Repository (OSS)              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | 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 | http-download.opensuse.org-13b88209 | home:malcolmlewis:openSUSE_General | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/malcolmlewis:/openSUSE_General/openSUSE_Tumbleweed/ |         

 5 | http-download.opensuse.org-9989fe02 | openSUSE:Tumbleweed                | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/                            |         

 6 | http-download.opensuse.org-bed4b33f | home:medozas74                     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/medozas74/openSUSE_Tumbleweed/                      |         

 7 | http-download.opensuse.org-f84be6b9 | home:malcolmlewis:TESTING          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/malcolmlewis:/TESTING/openSUSE_Tumbleweed/          |         

 8 | packman                             | packman                            | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/    

 9 | repo-debug                          | openSUSE-Tumbleweed-Debug          | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/         

10 | repo-source                         | openSUSE-Tumbleweed-Source         | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/

I am also having a few conflicts with zypper dup right now, not sure if the best bet is to go through and uninstall all conflicts or what the best course of action is for this:

Code:

12 Problems:

Problem: problem with installed package libmad0-0.15.1b-1.31.x86_64

Problem: problem with installed package libmp3lame0-3.99.5-1016.9.x86_64

Problem: problem with installed package libmpeg2-0-0.5.1-3.41.x86_64

Problem: problem with installed package libmpeg2convert0-0.5.1-3.41.x86_64

Problem: problem with installed package libtwolame0-0.3.13-3.3.x86_64

Problem: problem with installed package libgcj-gcc6-6.4.1+r251631-1.3.x86_64

Problem: problem with installed package libgcj-jar-gcc6-6.4.1+r251631-1.3.x86_64

Problem: problem with installed package libgcj-devel-gcc6-6.4.1+r251631-1.3.x86_64

Problem: problem with installed package libgcj_bc1-6.4.1+r251631-1.3.x86_64

Problem: problem with installed package libQtWebKit4-4.8.7+2.3.4-4.1.x86_64

Problem: problem with installed package qt3-3.3.8c-141.1.x86_64

Problem: libopenssl-1_0_0-devel-1.0.2n-2.1.x86_64 conflicts with libopenssl-devel > 1.0.2n provided by libopenssl-devel-1.1.0h-1.1.noarch

Anyhelp is greatly appreciated, I am still fairly new and learning. I understand a rolling release is not the best for someone learning, but I think it helps.

↧

TUMBLEWEED I accidentally broke KDE whilst rpm database was damaged

April 8, 2018, 6:17 am

≫ Next: TUMBLEWEED USB Stick

≪ Previous: TUMBLEWEED systemsettings5 not working after update

I had some issues that seemed to have coincided with a broken rpm database. I eventually fixed this following some advice, using the command:

Code:

rpm --rebuilddb

However, before I ran that command, as a result of the broken rpm database, KDE wouldn't load. Whilst trying to fix it I accidentally uninstalled all the KDE related rpms. Then when I tried to reinstall them, they all gave errors.

After the rebuild, it looks like I can reinstall them again, however I still can't get into KDE (either Plasma or OpenBox KDE), so I am still accessing this machine using IceWM.

It is possible that I haven't installed all of the KDE dependencies? I was hoping that Yast2 would automatically add them, but I may have missed something. Or maybe something else is wrong?

Context
This is an outstanding issue after fixing the issues described in another thread. Since the main issues in that thread are fixed I'm marking it resolved and starting a new thread for this issue.

Full details of what happened and advice followed so far, if it is useful.

↧

TUMBLEWEED USB Stick

April 8, 2018, 6:36 am

≫ Next: TUMBLEWEED Old Kernels not getting purged: mkinitrd compiles them, still in boot

≪ Previous: TUMBLEWEED I accidentally broke KDE whilst rpm database was damaged

Hello,
I have this problem when I use a USB stick, when I click on "Device Notifier"

↧

TUMBLEWEED Old Kernels not getting purged: mkinitrd compiles them, still in boot

April 8, 2018, 6:44 am

≫ Next: LEAP 42.3 Koma-Script Version?

≪ Previous: TUMBLEWEED USB Stick

I'm trying to clean up my Tumbleweed system. I noticed after recent updates (zypper dup) that kernels that should not be installed get compiled, they still show up in the boot menu and I can still find them in the /boot directory and in /lib/modules directory.

For example,

Code:

# rpm -qa kern*

returns:

Code:

kernel-default-devel-4.15.13-2.4.x86_64

kernel-syms-4.15.13-2.4.x86_64

kernel-devel-4.15.13-2.4.noarch

kernel-syms-4.15.13-1.6.x86_64

kernel-firmware-20180320-1.1.noarch

kernel-default-4.15.13-2.4.x86_64

kernel-default-devel-4.15.13-1.6.x86_64

kernel-devel-4.15.13-1.6.noarch

kernel-macros-4.15.13-2.4.noarch

kernel-default-4.15.13-1.6.x86_64

but

Code:

# ls /boot

returns:

Code:

.vmlinuz-4.15.13-1-default.hmac  boot.readme               initrd                         symtypes-4.15.9-1-default.gz   sysctl.conf-4.15.9-1-default  vmlinuz-4.15.13-2-default

.vmlinuz-4.15.13-2-default.hmac  config-4.15.13-1-default  initrd-4.15.13-1-default       symvers-4.15.13-1-default.gz   vmlinux-4.15.13-1-default.gz  vmlinuz-4.15.9-1-default

.vmlinuz-4.15.9-1-default.hmac   config-4.15.13-2-default  initrd-4.15.13-2-default       symvers-4.15.13-2-default.gz   vmlinux-4.15.13-2-default.gz

System.map-4.15.13-1-default     config-4.15.9-1-default   initrd-4.15.9-1-default        symvers-4.15.9-1-default.gz    vmlinux-4.15.9-1-default.gz

System.map-4.15.13-2-default     efi                       symtypes-4.15.13-1-default.gz  sysctl.conf-4.15.13-1-default  vmlinuz

System.map-4.15.9-1-default      grub2                     symtypes-4.15.13-2-default.gz  sysctl.conf-4.15.13-2-default  vmlinuz-4.15.13-1-default

and

Code:

# ls /lib/modules

returns:

Code:

4.11.6-1-default  4.11.8-2-default   4.12.7-1-default  4.13.10-1-default  4.13.3-1-default  4.13.9-1-default   4.15.0-1-default   4.15.13-1-default  4.15.3-1-default

4.11.8-1-default  4.12.11-1-default  4.12.8-1-default  4.13.12-1-default  4.13.6-1-default  4.14.11-1-default  4.15.10-1-default  4.15.13-2-default  4.15.9-1-default

when...

Code:

# rpm -qa *default

returns:

Code:

virtualbox-host-kmp-default-5.2.8_k4.15.13_2-2.3.x86_64

kernel-default-4.15.13-2.4.x86_64

icewm-default-1.4.2-6.1.x86_64

ghc-data-default-0.7.1.1-2.5.x86_64

bbswitch-kmp-default-0.8_k4.15.13_2-28.88.x86_64

kernel-default-4.15.13-1.6.x86_64

Yast only shows 4.15.13-2 and 4.15.13-1 being installed.

If I do

Code:

mkinitrd

I get:

Code:

Creating initrd: /boot/initrd-4.15.13-1-default

dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.15.13-1-default 4.15.13-1-default

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: suse-xfs ***

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: Skipping udev rule: 61-persistent-storage-compat.rules

dracut: *** Including module: biosdevname ***

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 GenuineIntel.bin ****

dracut: *** Store current command line parameters ***

dracut: Stored kernel commandline:

dracut:  resume=UUID=71befdee-3245-42f0-a4b5-a6bd95ada3e8

dracut:  root=UUID=e957e756-905d-4b97-8239-34bae6f2d47c rootfstype=btrfs rootflags=rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot,subvol=@/.snapshots/1/snapshot

dracut: *** Creating image file '/boot/initrd-4.15.13-1-default' ***

dracut: *** Creating initramfs image file '/boot/initrd-4.15.13-1-default' done ***

Creating initrd: /boot/initrd-4.15.13-2-default

dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.15.13-2-default 4.15.13-2-default

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: suse-xfs ***

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: Skipping udev rule: 61-persistent-storage-compat.rules

dracut: *** Including module: biosdevname ***

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 GenuineIntel.bin ****

dracut: *** Store current command line parameters ***

dracut: Stored kernel commandline:

dracut:  resume=UUID=71befdee-3245-42f0-a4b5-a6bd95ada3e8

dracut:  root=UUID=e957e756-905d-4b97-8239-34bae6f2d47c rootfstype=btrfs rootflags=rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot,subvol=@/.snapshots/1/snapshot

dracut: *** Creating image file '/boot/initrd-4.15.13-2-default' ***

dracut: *** Creating initramfs image file '/boot/initrd-4.15.13-2-default' done ***

Creating initrd: /boot/initrd-4.15.9-1-default

dracut: Executing: /usr/bin/dracut --logfile /var/log/YaST2/mkinitrd.log --force /boot/initrd-4.15.9-1-default 4.15.9-1-default

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: suse-xfs ***

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: Skipping udev rule: 61-persistent-storage-compat.rules

dracut: *** Including module: biosdevname ***

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 GenuineIntel.bin ****

dracut: *** Store current command line parameters ***

dracut: Stored kernel commandline:

dracut:  resume=UUID=71befdee-3245-42f0-a4b5-a6bd95ada3e8

dracut:  root=UUID=e957e756-905d-4b97-8239-34bae6f2d47c rootfstype=btrfs rootflags=rw,relatime,ssd,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot,subvol=@/.snapshots/1/snapshot

dracut: *** Creating image file '/boot/initrd-4.15.9-1-default' ***

dracut: *** Creating initramfs image file '/boot/initrd-4.15.9-1-default' done ***

I've tried rebuilding the rpmdb but not manually removing these old files and directories. I don't know where all the pieces are and I'm afraid to get things misaligned. I really don't want to leave so much extra stuff on the drive (SSD, space will eventually be an issue) and the problem of compiling kernels that shouldn't even be installed bothers me.

↧

LEAP 42.3 Koma-Script Version?

April 8, 2018, 7:04 am

≫ Next: TUMBLEWEED new Kernel4.16 and Nvidia Driver

≪ Previous: TUMBLEWEED Old Kernels not getting purged: mkinitrd compiles them, still in boot

Hallo,
wenn ich nicht ganz falsch liege, ist die neueste Koma-Script-Version die (bekannt fehlerhafte) 3.20. wie bekomme ich über SuSE aktuellere Pakete?
Danke
Aunaloge

↧