Installation

Ab Kernel 2.6.28 wurde der Video-Modus der Grafikkarten vom XServer in den Kernel verlagert. Dadurch wurde es möglich, dass ein hochauflösender „Boot Splash“ (siehe Plymouth) flackerfrei angezeigt werden kann. Bei einigen Karten bleibt dieser „Boot Splash“ hängen oder endet in einem schwarzen Bildschirm. Dieses Verhalten tritt typischerweise bei Hardwre mit Intel und nVidia-Karten auf. Mi nomodeset wird der grafische Boot aus dem Kernel umgangen:

nomodeset

F3 = Text mode (ncurses) oder Kernel Parameter

Textmode=1

Automatisches Update des Installers (Download)

self_update=1

GRUB 2 for EFI on

openSUSE Leap does not support a boot prompt or function keys for adding boot parameters. By default, the installation will be started with American English and the boot media as the installation source. A DHCP lookup will be performed to configure the network. To change these defaults or to add additional boot parameters you need to edit the respective boot entry. Highlight it using the arrow keys and press E . See the on-screen help for editing hints (note that only an English keyboard is available now). The Installation entry will look similar to the following:

setparams 'Installation'

set gfxpayload=keep echo 'Loading kernel …' linuxefi /boot/x86_64/loader/linux splash=silent echo 'Loading initial ramdisk …' initrdefi /boot/x86_64/loader/initrd Add space-separated parameters to the end of the line starting with linuxefi. To boot the edited entry, press F10 . If you access the machine via serial console, press Esc – 0 . A complete list of parameters is available at http://en.opensuse.org/Linuxrc. The most important ones are:

Table 2.2: Installation Sources Report Bug #


CD/DVD (default)

install=cd:/

Hard disk

install=hd:/?device=sda/PATH_TO_ISO

SLP

install=slp:/

FTP

install=ftp:////ftp.example.com/PATH_TO_ISO//

HTTP

install=http:////www.example.com/PATH_TO_ISO//

NFS

install=nfs:/PATH_TO_ISO

SMB / CIFS

Table 2.3: Network Configuration Report Bug #


DHCP (default)

netsetup=dhcp

Prompt for Parameters

netsetup=hostip,netmask,gateway,nameserver

Host IP address

hostip=192.168.2.100

hostip=192.168.2.100/24

Netmask

netmask=255.255.255.0

Gateway

gateway=192.168.5.1

Name Server

nameserver=192.168.1.116

nameserver=192.168.1.116,192.168.1.118

Domain Search Path

domain=example.com

Table 2.4: Miscellaneous Report Bug #


Driver Updates: Prompt

dud=1

Driver Updates: URL

dud=ftp:////ftp.example.com/PATH_TO_DRIVER//

dud=http:////www.example.com/PATH_TO_DRIVER//

Installation Language

Language=LANGUAGE

Supported values for LANGUAGE are, among others, cs_CZ, de_DE, es_ES, fr_FR, ja_JP, pt_BR, pt_PT, ru_RU, zh_CN, and zh_TW.

Kernel: No ACPI

acpi=off

Kernel: No Local APIC

noapic

Video: Disable KMS

nomodeset

Video: Start Installer in Text Mode

Textmode=1

Warning: Custom Partitioning on UEFI Machines

A UEFI machine requires an EFI system partition that must be mounted to /boot/efi. This partition must be formatted with the FAT file system. If an EFI system partition is already present on your system (for example from a previous Windows installation) use it by mounting it to /boot/efi without formatting it.

Warning: Custom Partitioning and Snapper

openSUSE Leap can be configured to support snapshots which provide the ability to do rollbacks of system changes. openSUSE Leap uses Snapper in conjunction with Btrfs for this feature. Btrfs needs to be set up with snapshots enabled for the root partition. Refer to Book “Reference”, Chapter 3 “System Recovery and Snapshot Management with Snapper” for details on Snapper.

Being able to create system snapshots that enable rollbacks requires most of the system directories to be mounted on a single partition. Refer to Book “Reference”, Chapter 3 “System Recovery and Snapshot Management with Snapper”, Section 3.1 “Default Setup” for more information. This also includes /usr and /var. Only directories that are excluded from snapshots (see Book “Reference”, Chapter 3 “System Recovery and Snapshot Management with Snapper”, Section 3.1.2 “Directories That Are Excluded from Snapshots” for a list) may reside on separate partitions. Among others, this list includes /usr/local, /var/log, and /tmp.

If you do not plan to use Snapper for system rollbacks, the partitioning restrictions mentioned above do not apply.

Zypper

Repos hinzufügen

zypper ar https://ftp.fau.de/packman/ packman

Liste aller installierten Pakete exportieren

zypper search –installed-only» locutus_packages.txt

Alle Pakete von einem bestimmten Repo zeigen

zypper pa -ir

Andersrum: von welchem Repo stammt ein Paket:

zypper –no-refresh info atom

Welches RPM liefert eine bestimmte Datei:

zypper se --provides --match-exact libqconnmanbearer.so

Welche Abhängigkeiten hat ein Paket?

zypper info --requires libkde4-devel

Standard ist KDE 5.12 LTS, mit diesen Repos kommt 5.15 aufs System

zypper ar -p 75 http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_15.0 KQ
zypper ar -p 75 http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_15.0 KF
zypper ar -p 75 https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_15.0 KA
zypper -v dup --allow-vendor-change

Takashi Iwai 2018-04-30 17:15:52 CEST

Actually you don't need to install the whole images. I'm asking only testing the kernel from the newer distros but on the existing Leap 42.3 user-space.

That is, grab the kernel-default.rpm for Leap 15.0 or TW from OBS download URL, and install it manually on your system, and boot with it. Thanks to the multi-version of kernel package, the old kernel will be still kept.

(BTW, if you test multiple kernels, it's safer to increase the kernels to keep in /etc/zypp/zypp.conf. e.g. change multiversion.kernels line like

multiversion.kernels = latest,latest-1,latest-2,latest-3,running

to keep more kernels. </bz_coDokument_text>

Doku: https://de.opensuse.org/openSUSE:Snapper_Tutorial https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.snapper.html

Snapshots zeigen

snapper list

Snapshots löschen

snapper delete [] []

Snapshot Unterschiede

snapper status 41..39

Snapshot Diff

snapper diff 71..72 /etc/zypp/zypp.conf

Snapshot anlegen

snapper create --description "Snapshot für Woche 2 2014"

Säuberungs-Algorithmus

Wenn Sie keinen guten Grund haben es anders zu machen, sollten Sie imer den Säuberungs-Algorithmus mit aufführen, wenn Sie Snapshots erstellen. Sonst wird der Snapshot nie gelöscht, außer Sie machen das manuell. Sie machen das durch das Hinzufügen von Folgendem in Ihrem Snapper-Befehl

--cleanup-algorithm <Nummer|Zeitleiste|leeres-vor-nachher>

Rollback

Setzt einen aktuell aktiven read only snapshot auf read-write und erzeugt einen weiteren Snapshot als read-write Kopie. Für den Rollback Snapshot kann man eine Beschreibung hinzufügen, die im Grub gezeigt wird:

snapper modify --userdata "bootloader=rollback from 103 with nvidiaG04" 109

Dual Boot Windows 10 UEFI

Windows 10 legt standard mässig diese Partitionstabelle an:

locutus:/srv/vm/win10uefi # vmware-mount -p win10uefi.vmdk Nr Start Size Type Id Sytem – ———- ———- —- – ———————— 1 2048 1021952 GPT EE Unknown 2 1024000 202752 GPT EE Efi System 3 1226752 32768 GPT EE Microsoft Reserved 4 1259520 124567552 GPT EE Basic Data

EFI Daten liegen in Partition 2 (EFI System). Dort liegt auch der Windows Bootmanager:

locutus:/srv/vm/win10uefi # ls /mnt/vm1/EFI/Microsoft/Boot/
BCD           Resources     da-DK  es-MX  hu-HU           kd_02_14e4.dll  kd_07_1415.dll  memtest.efi  qps-ploc    sv-SE
BCD.LOG       bg-BG         de-DE  et-EE  it-IT           kd_02_15b3.dll  kd_0C_8086.dll  nb-NO        ro-RO       tr-TR
BCD.LOG1      boot.stl      el-GR  fi-FI  ja-JP           kd_02_1969.dll  kdstub.dll      nl-NL        ru-RU       uk-UA
BCD.LOG2      **bootmgfw.efi**   en-GB  fr-CA  kd_02_10df.dll  kd_02_19a2.dll  ko-KR           pl-PL        sk-SK       winsipolicy.p7b
BOOTSTAT.DAT  bootmgr.efi   en-US  fr-FR  kd_02_10ec.dll  kd_02_1af4.dll  lt-LT           pt-BR        sl-SI       zh-CN
Fonts         cs-CZ         es-ES  hr-HR  kd_02_1137.dll  kd_02_8086.dll  lv-LV           pt-PT        sr-Latn-RS  zh-TW

GRUB2 braucht einen separaten Menüeintrag, um Windows 10 zu starten. Dieser wird in /etc/grub.d/40_custom angelegt. EFI-UUID ist die UUID der EFI Partition, die man mit blkid findet. Alternativ kann grub2-probe genutzt werden:

grub2-probe -t fs_uuid -d /dev/sdaX

Menüeintrag in /etc/grub.d/40_custom, siehe auch https://ihaveabackup.net/article/grub2-entry-for-windows-10-uefi

menuentry "Windows 10" {
         insmod search_fs_uuid
         insmod chain
         search –fs-uuid –no-floppy –set=root [EFI-UUID]
         chainloader ($root)/EFI/Microsoft/Boot/bootmgfw.efi
         }

Anschliessend EFI Bootmenü Menü neu schreiben lassen:

grub-mkconfig -o /boot/efi/EFI/opensuse/grub.cfg

  • Windows Installations CD
  • Shift F8 » Windows Recovery Menu.
  • Troubeleshoot, Automatic Repair, Command line
  • bootrec.exe

bootrec / fixMbr

Linux Bootoption im Windows Bootmanager

KDE & Plasma

ps -ef | grep cra

Siehe https://gist.github.com/Trucido/b788017a18e1189e6703e42315e8829c

sudo zypper in pam_kwallet

Then edit the files /etc/pam.d/passwd, /etc/pam.d/login and /etc/pam.d/sddm as follows, i.e. add the lines beginning with a - (the hyphens are valid PAM syntax to reduce log entries if these PAM modules should not exist) and ending with the ### comment:

/etc/pam.d/passwd :

#%PAM-1.0 auth include common-auth -auth optional pam_kwallet5.so kdehome=.local/share # Add this line account include common-account password include common-password session include common-session

/etc/pam.d/login :

#%PAM-1.0 auth requisite pam_nologin.so auth include common-auth account include common-account password include common-password session required pam_loginuid.so session include common-session #session optional pam_lastlog.so nowtmp showfailed session optional pam_mail.so standard -session optional pam_kwallet5.so auto_start # Add this line

/etc/pam.d/sddm :

#%PAM-1.0 -auth optional pam_kwallet5.so kdehome=.local/share # Add this line auth include common-auth account include common-account password include common-password session required pam_loginuid.so session include common-session -session optional pam_kwallet5.so auto_start # Add this line

Now log out and in again to see if you do not have to type in your kwallet password.

Logout delay von 30 sek verringern:

locutus:/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/logout # ls Logout.qml Logout.qml.old LogoutButton.qml

function sleepRequested() { root.suspendRequested(2); } property real timeout: 10 property real remainingTime: root.timeout property var currentAction: { switch (sdtype) { case ShutdownType.ShutdownTypeReboot: return root.rebootRequested; case ShutdownType.ShutdownTypeHalt: return root.haltRequested; default: return root.logoutRequested; } }

Doku siehe http://doc.qt.io/qt-5/qtqml-index.html

Plasma Fonts

Hässliche Fonts in Leap 42.3, speziell auf Laptops. Siehe dazu http://www.ocsmag.com/2017/09/23/opensuse-fonts/

und https://build.opensuse.org/project/show/home:gldickens3

Config

kcmshell5 kwincompositing

Check

qdbus org.kde.KWin /Compositor org.kde.kwin.Compositing.active

Enable

qdbus org.kde.KWin /Compositor org.kde.kwin.Compositing.resume

Disable

qdbus org.kde.KWin /Compositor org.kde.kwin.Compositing.suspend

1) In the graphical session, find the value of DISPLAY and XAUTHORITY variables:

echo $DISPLAY :0 echo $XAUTHORITY /run/user/…

2) SSH into the computer from another machine using the same user as in the graphical session.

3) Set the DISPLAY and XAUTHORITY variables to the same values as above:

export DISPLAY=:0 export XAUTHORITY=/run/user/…

4) Start kwin in gdb in the ssh session:

gdb –args kwin_x11 –replace

5) Reproduce the issue.

6) The gdb is now hopefully showing segfault, abort or something. If not, hit CTRL+C to get gdb prompt. Then run the „generate-core-file“:

(gdb) generate-core-file

Saved corefile core.25218

Samba

Ab Samba 4.7.0 / (Ubuntu: Bionic Beaver) versucht smbclient die Verbindung im Dialekt SMB3_11 aufzubauen. In der Folge funktioniert das Browsing (smbclient -L <server>) nicht mehr. Lösung ist es den Dialekt SMB1 mittels Parameter -m zu erzwingen (smbclient -mNT1 -L <server>). Weitere Infos siehe Samba 4.7.0

Shares auf eineen Samba Server abscannen

anonym

thommie@locutus:~> smbclient -N -L nas2 Anonymous login successful Sharename Type Comment ——— —- ——- video Disk video photo Disk photo music Disk music admin Disk admin buch Disk buch downloads Disk downloads backup Disk backup datanas1 Disk datanas1 public Disk public data1 Disk data1 IPC$ IPC IPC Service (nas2 server) Reconnecting with SMB1 for workgroup listing. Anonymous login successful Server Comment

mit smbclient -L wird ein Passwort für den aktuellen Shell User abgefragt

Samba Share fest mounten

Mit User mounten

mount -t cifs -o vers=3.0,username=thommie, password=xxx nas2.netzwissen.loc/photo /mnt/nas_photo/

Anonym mounten für bestimmten USer

mount -t cifs -o vers=3.0,guest,uid=thommie,gid=users nas2.netzwissen.loc/photo /mnt/nas_photo/ xx

Nvidia & Bumblebee

Prüfen, welche Karten eingebaut sind (mit zypper in lshw)

odysseus3:~ # lshw -c video
  *-display UNCLAIMED
       description: VGA compatible controller
       product: GP107GLM [Quadro P2000 Mobile]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:b2000000-b2ffffff memory:70000000-7fffffff memory:b0000000-b1ffffff ioport:3000(size=128) memory:b3000000-b307ffff
  *-display UNCLAIMED
       description: VGA compatible controller
       product: UHD Graphics 630 (Mobile)
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:b4000000-b4ffffff memory:60000000-6fffffff ioport:4000(size=64) memory:c0000-dffff

Display Status prüfen

thommie@odysseus3:~> xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected primary 1920x1080+0+0 0mm x 0mm
   1920x1080     77.00*

Analyse mit inxi (zypper in inxi)

odysseus3:~ # inxi -Fxz
System:    Host: odysseus3 Kernel: 4.12.14-lp151.27-default x86_64 bits: 64 gcc: 7.4.0 Console: tty 0
           Distro: openSUSE Leap 15.1
Machine:   Device: laptop System: Dell product: Precision 7530 serial: <filter>
           Mobo: Dell model: 03RV2M v: A00 serial: <filter> UEFI: Dell v: 1.6.0 date: 12/25/2018
Battery    BAT0: charge: 60.4 Wh 100.0% condition: 60.4/64.0 Wh (94%) model: BYD DELL GHXKY8B status: Full
CPU:       Hexa core Intel Core i7-8750H (-HT-MCP-) arch: Skylake rev.10 cache: 9216 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 26496
           clock speeds: max: 4100 MHz 1: 2200 MHz 2: 2200 MHz 3: 2200 MHz 4: 2200 MHz 5: 2200 MHz 6: 2200 MHz
           7: 2200 MHz 8: 2200 MHz 9: 2200 MHz 10: 2200 MHz 11: 2200 MHz 12: 2200 MHz
Graphics:  Card-1: Intel Device 3e9b bus-ID: 00:02.0
           Card-2: NVIDIA Device 1cba bus-ID: 01:00.0
           Display Server: X.org 1.20.3 drivers: fbdev (unloaded: modesetting,vesa)
           tty size: 130x35 Advanced Data: N/A for root out of X
Audio:     Card Intel Device a348 driver: snd_hda_intel bus-ID: 00:1f.3 Sound: ALSA v: k4.12.14-lp151.27-default
Network:   Card-1: Intel Ethernet Connection (7) I219-LM driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6
           IF: em1 state: down mac: <filter>
           Card-2: Intel Device 2526 driver: iwlwifi bus-ID: 6f:00.0
           IF: wlan0 state: up speed: N/A duplex: N/A mac: <filter>
Drives:    HDD Total Size: 512.1GB (52.0% used)
           ID-1: /dev/nvme0n1 model: KXG5AZNV512G_NVMe_SED_TOSHIBA_512GB size: 512.1GB
Partition: ID-1: / size: 150G used: 23G (15%) fs: btrfs dev: /dev/nvme0n1p2
           ID-2: /var size: 150G used: 23G (15%) fs: btrfs dev: /dev/nvme0n1p2
           ID-3: /opt size: 150G used: 23G (15%) fs: btrfs dev: /dev/nvme0n1p2
           ID-4: /tmp size: 150G used: 23G (15%) fs: btrfs dev: /dev/nvme0n1p2
           ID-5: /home size: 120G used: 59G (50%) fs: xfs dev: /dev/dm-0
           ID-6: swap-1 size: 38.65GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p5
Sensors:   None detected - is lm-sensors installed and configured?
Info:      Processes: 351 Uptime: 0:53 Memory: 2537.2/31919.5MB Init: systemd runlevel: 5 Gcc sys: 7.4.0
           Client: Shell (bash 4.4.231) inxi: 2.3.40


  • opensuse.txt
  • Zuletzt geändert: vor 11 Tagen
  • von thommie3