Quantcast
Channel: openSUSE Forums
Viewing all 40713 articles
Browse latest View live

TUMBLEWEED Cant poweroff or reboot Tumbleweed.

$
0
0
Installed Tumbleweed june30. I kept it up-to-date whenever updates were available. Recently I noted that on reboot or logoff, using the Gnome interface,
I wait for and do not get the poweroff/reboot occurring. Hitting escape shows me a console message of "awaiting reboot", or some similar message.

I noted and will reconfirm, that if I do not use the GUI interface, but remain in xorg terminal mode, and then request a poweroff/reboot, Tumbleweed functions as expected.

Any clues where to look? Should I just reinstall TWD? I am using xorg and GNOME.

Same problem occurs with regular or hypervisor Tumbleweed boot folllowing gnome use.

TUMBLEWEED Repo Issue

$
0
0
Hi new to linux / suse im using tumbleweed.

When i run a sudo zypper update i get the below.list of repo errors. is this normal? how can i resolve it?

Thanks



Code:

Retrieving repository 'google-chrome' metadata .........................................................[done]
Building repository 'google-chrome' cache ..............................................................[done]
Repository 'Non-OSS Repository' is invalid.
[repo-non-oss|http://download.opensuse.org/distribution/leap/20190829/repo/non-oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Non-OSS Repository' because of the above error.
Repository 'Main Repository' is invalid.
[repo-oss|http://download.opensuse.org/distribution/leap/20190829/repo/oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Main Repository' because of the above error.
Repository 'Main Update Repository' is invalid.
[repo-update|http://download.opensuse.org/update/leap/20190829/oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Main Update Repository' because of the above error.
Repository 'Update Repository (Non-Oss)' is invalid.
[repo-update-non-oss|http://download.opensuse.org/update/leap/20190829/non-oss/] Repository type can't be determined.
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Skipping repository 'Update Repository (Non-Oss)' because of the above error.
Some of the repositories have not been refreshed because of an error.
Loading repository data...
Reading installed packages...

LEAP 15.1 New GNOME install, added MATE but it has no top panels to open apps with?

$
0
0
Folks:

Just did a fresh install of LEAP 15. 1 yesterday, and all went well, was having an issue with not being able to get into my twitter account in GNOME DE, so I added MATE via Yast Patterns and on reboot I can log into MATE DE, but there is no top or bottom control panels?? Tried to run a zypper ref && dup, but "nothing to do" . . . how would I get to something that will add panels into MATE? Back in GNOME session right now . . . but I do like MATE as my preferred DE . . . ???

I had the installer "use previous profile" for my install yesterday, and my preferred desktop background is loaded in MATE, but . . . no panels??

TUMBLEWEED How to install with encrypted root partition that includes /boot?

$
0
0
I have Windows 7 installed on a different drive, so I can't use Secure Boot.

I want to set up 3 encrypted partitions on the SSD:

/
/home
Swap

After it's set up I plan to set up keyfiles so that I only need to enter the LUKS password once:

https://en.opensuse.org/SDB:Encrypted_root_file_system

In the above article, it says:

"Warning: Do this only if you have an encrypted root partition that includes /boot (no separate /boot partition)!"

The problem is, I haven't been able to figure out how to install TW without the separate /boot partition.

I've tried going through the guided setup (selecting encryption, separate / and /home partitions), and it creates a separate unencrypted /boot partition. If I keep the current proposal and go into Expert Partitioner and remove the /boot partition, I get a number of warnings saying I won't be able to boot if I proceed with the install.

I didn't select LVM because I don't anticipate needing it - it's a 1 TB SSD, with 100 GB for / and 16 GB Swap and the rest for /home. I also know how to back up and restore LUKS partitions with Clonezilla but don't know how with LVM and LUKS.

The weird thing is, I did this successfully a month ago on a laptop (which dual booted with Windows 10) but I don't remember running into any issues with the install (or maybe I saw warnings that I just ignored and forgot after I saw it worked).

LEAP 15.1 MdContainer/device error during installation on Dell laptop

$
0
0
Platform: Dell Inspiron 15 5584 laptop
Processor: Intel Core i5-8265U
RAM: 12GB DDR4 2666MHz
Hard drive: 256GB Solid State m.2 / 16GB Intel Optane Memory
OS: MS Windows 10 Home (64-bit)
UEFI bios/secure boot enabled (can be disabled)

Install from USB drive (full and live)
ImageUSB used to create image (MD5 & sha1 checksums match; earlier successfully confirmed sha256 match).
EFI install

Just before the drive/storage configuration dialog when attempting both the off-line and live installs of Leap 15.1, I received the same warning, “Yast2 cannot delete MdContainer.” Summarizing the details, "error in system device – displayed information may not be accurate; installation may fail." And proceeding further, the proposed disk allocation seems off (but I would need to revisit that to be certain). I found two posts in this forum, but I am not able to conclude anything from them (I'm not familiar with MdContainer; may be a Java function or component). See https://forums.opensuse.org/showthre...te+mdcontainer and https://forums.opensuse.org/showthre...te+mdcontainer.


Given the warning, I'm reluctant to go further. Any advice would be welcome.

LEAP 15.1 Network configuration - Systemd-network versus Network Manager vs Wicked

LEAP 15.1 dish@a68:~>sshuttle

$
0
0
Code:

dish@a68:~>sshuttle
Code:

Output is

Code:

Traceback (most recent call last):  File "/usr/bin/sshuttle", line 6, in      from pkg_resources import load_entry_point ImportError: No module named pkg_resources  Reinstall python3-setuptools is not help.
Thank you for your help!

LEAP 15.1 Start menu taskbar gone

$
0
0
Good day

sorry um Iam stuck lol

i turned on my box and my start/taskbar is like gone

um how do I get it back ?

the one thing I noticed on start up it says
“error getting immou info is the immo enabled
error initializing immouv2
Device 1002:9074 not added due to errors”

um help lol?

LEAP 15.1 Changing existing home partition UUID to defined value.

$
0
0
Although quite basic I just want to be sure what I'm doing in terms of procedure, is correct.


I have three machines, all have ext4 file systems and a separate /home drive or partition.

I want to change the UUID of /home on two of those to match that of the first, i.e. all three machines have the same UUID for /home. [1]

As I understand it from the "manual", one can use tune2fs as follows:

Code:

tune2fs /dev/{device} -U {uuid}
So I would:

1) boot from a live USB
2) use tune2fs to change /home's UUID
3) edit the relevant entry in /etc/fstab to reflect the changed UUID

I assume as home is mounted after "switch root" there is no need to mkinitrd ?

4) reboot normally and the new UUID should be in effect


Normally I'd be quite happy to just try, but in this instance I want to be sure I'm not making some basic (stupid) error... ;)


[1] All three machines have an area below ~/ that I keep synchronised using "unison" ( https://software.opensuse.org/package/unison ). In general this works well. However "digikam" (https://software.opensuse.org/package/digikam ) stores within it's database not only the path(s) to it's image collection(s) but also the UUID of the partition. Each time digikam is opened following a synchronisation which includes it's database files from another machine, it is necessary to tell digikam it is dealing with the same collection, as the UUID has changed. My rationale was if /home's UUID was the same on each machine then digikam would no longer think the collection is (possibly) the wrong one.

TUMBLEWEED Cannot install Mullvad VPN - Dependency issues

$
0
0
openSUSE Tumbleweed KDE fresh install.

Downloaded the Mullvad commercial VPN .rpm but instructions are here only for Fedora: https://mullvad.net/en/guides/instal...vad-app-linux/

Code:

sudo rpm -i MullvadVPN-2019.7_x86_64.rpm
Code:

error: Failed dependencies:
        dbus-libs is needed by mullvad-vpn-2019.7.0-1.x86_64
        libnotify is needed by mullvad-vpn-2019.7.0-1.x86_64
        libnsl is needed by mullvad-vpn-2019.7.0-1.x86_64

I see libnotify and libnsl are installed in yast but still showing failed dependencies and nothing comes up for dbus. Do I just ignore the warning and install anyway?

Thanks

TUMBLEWEED Network Scanner Not Detected - Brother MFC-7440N

$
0
0
openSUSE Tumbleweed KDE installation. Brother MFC-7440N is a network printer connected to my local network.

Downloaded Brother printer installer tool which includes the scanner tool.

Code:

bash linux-brprinter-installer-2.2.1-1
Printer and scanner installed, manually entered ip address, test print is successfull!!!

Code:

Resolving package dependencies...

Nothing to do.
brsaneconfig3 -a name=MFC-7440N model=MFC-7440N ip=192.168.1.114

Scanner driver shows it is installed above with proper ip address. Skanlite and simple scan say scanner is not detected.

This scanner works wirelessly in Leap but oddly it is not found in Tumbleweed.

Code:

sudo brsaneconfig3 -q | grep myScanner
Doesn't provide any output. It shows it is installed in Yast but the version is in red?

I try to add a scanner through Yast and it shows the brscan3 driver but it says "no scanner recognized by this driver."

I think that's all the info I can give. Any help appreciated.

TUMBLEWEED Do I need to enable TRIM?

$
0
0
Fresh install of Tumbleweed KDE on an intel 660p 1TB ssd. Is it necessary to enable trim on openSUSE? I have always done this on my other disto installs with:

Code:

sudo systemctl enable fstrim.timer
I'd like to maximize the lifespan of my ssd. Thanks

LEAP 15.1 Failure to install LEAP 15.1

$
0
0
I'm attempting to install LEAP 15.1 onto a Lenovo laptop. There is a 42.1 version of OpenSuSE on there - so I have installed it there before. The old Suse version had a nasty crash (a while back), so, since I'm going to need the laptop again, I decided to upgrade. My desktop is running LEAP 15.0.

I downloaded 15.1 to my desktop (both machines are x86_64) then burned a DVD with K3b. All very smooth. I've previously amended the BIOS on the laptop to read the USB port first when I installed the earlier version of Suse so I thought this installation would be straightforward. The laptop itself is working, since I can run Windows on it (dual-boot fashion).

When I start the laptop the light on my external DVD reader comes on and I can hear the DVD whirring away, but the laptop then starts up its own grub menu. It seems to be reading the disks in the right order - USB port then hard drive - but not recognising that it should boot from the DVD.

Frustratingly I also don't seem to be able to get into the BIOS to check that the boot order is correctly set up there. (It should just appear when I hit Enter while the splash screen is up, bot it doesn't.) However, if the DVD drive is plugged in it takes longer for the grub screen to appear, confirming that it's trying to do something with the DVD drive.

The only thing I can think of is that there is a problem with the boot disk. I've burned it twice (different downloads) but no change in what happens.

Anyone got any advice on how to proceed?

TUMBLEWEED Cannot install Telegram in Yast - Conflict Resolution

$
0
0
Installed Tumbleweed KDE this morning for the first time and trying to get things setup. I pulled up Telegram in Yast for installation but a box pops up with a conflict resolution message that Telegram conflicts with:

libqt5-qtstyleplugins-platformtheme-gtk2


I can choose to deinstall the above or not install Telegram. I'm new to openSUSE package management so it looks like my only option is to uninstall the above package? Won't that break something else? Thanks for my newbie questions.

TUMBLEWEED Mount von lokalen und NFS-Platten -> User Login

$
0
0
Hallo zusammen,

ich bin kürzlich wieder auf Tumbleweed umgestiegen, weil meine Grafikkarte nicht unter LEAP 15.1 läuft. Mit Tumbleweed habe ich derzeit zwei gravierende Probleme und ich bin nicht sicher, ob das ein SUSe-Thema oder PEBKAC ist:
1) Auf meiner zweiten Festplatte liegen verschiedene Partitionen für /mnt/local/data und /mnt/local/Tausch sowie swap und /home. Während swap und /mnt/local/Tausch immer eingebunden werden, kommt das System manchmal hoch und /mnt/local/data ist nicht gemountet. Gerade eben hat /home gefehlt. Ich kann nicht sehen, was da fehlt? Die Platte an sich ist da, schließlich konnten die anderen Partitionen auch gemountet werden. Wenn ich als root manuell mounte, nimmt er die Partitionen auch online... Ist das hier schonmal jemandem passiert? Woran kann das liegen?

2) Ich habe in der fstab zwei NFS mounts gelistet. Diese sind nicht kritisch. Insbesondere sind dort keine Daten, die ein User so zwingend benötigt, dass ein Login unmöglich wäre. Dennoch scheint remote-fs eine zwingende Voraussetzung dafür zu sein, dass das System im Runlevel5 den grafischen login startet. Wenn mein Server mal ausgeschaltet ist, dann sehe ich nur den Tumbleweed-Schirm mit dem Unendlichzeichen. Auf den Startmeldungen steht dann: A start job is running for /mnt/remote/SoltauSuse/Server_Public (1min30s/no limit)
Das bekomme ich nur behoben, indem ich den Server einschalte.
In einem ersten Versuch habe ich in /etc/systemd/system beim Displaymanager das "wants" remote-fs heraus genommen. Ebenso beim multiuser-target. Hat aber nichts geholfen. Hat hier jemand einen Tipp?

Meine FSTAB sieht so aus:

Code:

UUID=ff56414d-9349-492e-b00d-ef7ee5104bdb  /                      btrfs  defaults                      0  0
UUID=ff56414d-9349-492e-b00d-ef7ee5104bdb  /var                    btrfs  subvol=/@/var                0  0
UUID=9acf2e86-4004-4c48-8cd7-797f4976731c  /usr                    xfs    defaults                      0  0
UUID=ae405401-3d9d-4f4d-9133-1f2450e939b2  /tmp                    xfs    defaults                      0  0
UUID=ff56414d-9349-492e-b00d-ef7ee5104bdb  /srv                    btrfs  subvol=/@/srv                0  0
UUID=ff56414d-9349-492e-b00d-ef7ee5104bdb  /root                  btrfs  subvol=/@/root                0  0
UUID=7e897a13-4839-442a-9768-86e5df104df0  /opt                    xfs    defaults                      0  0
UUID=f61c43a9-702a-4e05-b5a0-ec0d80f7e9a2  /mnt/local/data        xfs    defaults                      0  0
UUID=CD9C-F5E5                            /mnt/local/Tausch      vfat  iocharset=utf8                0  0
UUID=cd4c88af-0f8e-40d5-8a9b-2d0284ce0242  /home                  xfs    defaults                      0  0
UUID=ff56414d-9349-492e-b00d-ef7ee5104bdb  /boot/grub2/x86_64-efi  btrfs  subvol=/@/boot/grub2/x86_64-efi  0  0
UUID=ff56414d-9349-492e-b00d-ef7ee5104bdb  /boot/grub2/i386-pc    btrfs  subvol=/@/boot/grub2/i386-pc  0  0
UUID=CE24-B4AB                            /boot/efi              vfat  defaults                      0  0
192.168.3.2:/mnt/local/fileshares/public  /mnt/remote/SoltauSuseServer_Public  nfs  defaults,bg,rw,auto,user,soft    0  0
UUID=8137cdf5-59e1-4bb8-a545-b519d81d31aa  /mnt/local/extern1      ext4      defaults,rw,noauto,user  0 0
192.168.2.3:/mnt/local/Backup  /mnt/remote/DMZServer nfs defaults,bg,rw,auto,user,soft  0  0

Danke und Gruß,
Martin

LEAP 15.1 MATE desktop breaks with todays update

$
0
0
Since the update's yesterday - every MATE desktop is broken upon rebooting!!!!!

mate-panel gives the following error

Code:

user@John:~/Desktop> mate-panel --reset
mate-panel: symbol lookup error: mate-panel: undefined symbol: matemenu_tree_unref

There is no issue until you reboot - then you are stuck - you can get a terminal on the desktop by right-clicking and it will open a terminal in the user's Desktop and you can go from there

Virtual images from Friday night do not have an issue. All the have the problem after installing the updates again and rebooting.

TUMBLEWEED Newest Linux 5.2.10-1 - cannot switch to EFI VGA (Radeon)

$
0
0
Hello. I would like to report a problem with the inability to boot from the latest update of OpenSUSE, with Linux version 5.2.10. The last log message is "fb: switching to radeondrmfb from EFI VGA". (I was booting up the kernel without a quiet flag). After that message everything freezes - I can't login to the SSH or tty. Normally, after this message, the screen switches to graphic mode with higher resolution (1080p). The problem occurs on all my machines - desktop with AMD RX 560 graphics card and Lenovo Ideapad 720s laptop (Integrated Radeon Vega 10 Graphics). On version 5.2.9 the problem does not occur at all. I do not use amdgpu-pro, only open-source solution. I have a friend who's also recently had the same problem, but for the older version of OpenSUSE (and kernel) . For this reason, I am convinced that the problem exists on many machines with Radeon graphics.

Output from lspci (desktop computer, Linux 5.2.9):
08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev cf)

Output from glxinfo | grep OpenGL:
OpenGL vendor string: X.Org
OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.32.0, 5.2.9-1-default, LLVM 8.0.1)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.5
OpenGL core profile shading language version string: 4.50
OpenGL shading language version string: 4.50
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.1.5
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

Installed packages:
libdrm_amdgpu1 (2.4.99-1.1) x86_64
libdrm_radeon1 (2.4.99-1.1) x86_64
xf86-video-amdgpu (19.0.1-2.1) x86_64
libvdpau_radeonsi
libvulkan_radeon
Mesa (19.1.5-227.1)
Mesa-KHR-devel
Mesa-dri
Mesa-gallium
Mesa-libEGL1
Mesa-libGLES*
Mesa-libOpenCL
Mesa-libgl*
Mesa-libva



The computer boots properly with the "nomodeset" flag, but this is not the solution to the problem due to lack of graphical acceleration and low resolution (1024x768).



If necessary, I can give more information.

TUMBLEWEED Workgroup LAN via ethernet achieves less than 50% of expected Gigabit speed between two PCs

$
0
0
I am working to set up a local network between my two laptops for file sharing. Figured that a wired Gigabit ethernet connection should be fastest (1000 Gbit/s, i.e. s.th. like 110 MiB/s in practice), and this connection should be the bottleneck. Hard disks are SSDs (>500 MiB/s). Both laptops have Intel Gigabit cards; connection is done with a short CAT. 5E ethernet cable, no crossed cable needed since the cards are good enough.

Up front: When running both laptops on Windows (8.1 in my case) with the ethernet card drivers left in their default installation states, everything works well. I am getting 110 MiB/s when copying large iso files in any direction (from A to B and B to A, fetching and sending). In this case, all hard disk partitions involved are NTFS.

Going to the real case now: Running Linux on one machine, either Tumbleweed or Manjaro (dual bootable). Sticking to Windows 8.1 on the other machine. Same ethernet cable, hard disk partitions on the Linux side either ext4 or ntfs. Bottom line: The resulting file transfer speeds are not exactly acceptable, I am getting approx. 50 MiB/s only. Seldomly it's 55, mostly just below 50, quite often only 40. This is the case with both Tumbleweed and Manjaro, and I am out of clues now after consulting many websites and even two textbooks.

What I did is as follows (short summary, this holds for both TW and Manjaro):
  1. On the Linux side, I configured a Link-Local ethernet connection using Network Manager. I can use whatever setting for the card speed is GUI available here (use auto-negotiation set to auto or manual, full duplex or half duplex) - same result.
  2. On the Linux side, avahi-daemon is running to do zeroconf. On the Windows side, zeroconf is handled by Bonjour with the two well-known Apple drivers extracted from iTunes and installed.
  3. At this stage, each laptop can ping the other one using either their 169.254.x.x zeroconf private IPV4 addresses, their IPV6 addresses, or their computer names.
  4. In order to share files residing on the Windows machine to the Linux machine, I set up the usual file sharings and access permissions in Windows Explorer. On the Linux machine, a Samba Client is being run. For both Tumbleweed and Manjaro, this works quite easily using just the file managers (Dolphin/Krusader in TW KDE Plasma, Thunar in Manjaro Xfce).
  5. In order to share files residing on the Linux machine to the Windows machine, I set up a Samba Server. This was the most complicated part for me, but I got it set up. Within this task, I went through an unproductive period until I realized that setting things up as root in /etc/samba/smb.conf and fiddling simultaneously with file sharing in the file managers as user is absolutely not advisable. So I have the Samba Server set up cleanly as root in /etc/samba/smb.conf only. Windows can connect to the Linux Samba shares using Windows Explorer.
  6. Firewalls are set up appropriately, too. In Tumbleweed, firewalld is preset nicely and comprehensively, and one just needs to assign a firewalld zone to the Link Local connection in Network Manager. In Manjaro, ufw with the gufw interface is used, and it takes opening the pre-configured samba ports.
  7. At this point in time, I think things are basically set up. I figure I will have to read more on how to make this local workgroup network as safe as possible beyond the defaults.

So now, I would need some help to find out why my file transfers within this littel LAN workgroup are so **** slow.

What can I provide to help you diagnose and hopefully solve this issue? All terminal commands were run while Link Local was connected.
Code:

$ sudo ethtool enp0s25
[sudo] Passwort für root:
Settings for enp0s25:
        Supported ports: [ TP ]
        Supported link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: off (auto)
        Supports Wake-on: pumbg
        Wake-on: d
        Current message level: 0x00000007 (7)
                              drv probe link
        Link detected: yes

Code:

$ inxi -Fdxxxz
System:    Host: susytmblwdke8570 Kernel: 5.2.10-1-default x86_64 bits: 64 compiler: gcc v: 9.2.1
          Desktop: KDE Plasma 5.16.4 tk: Qt 5.13.0 wm: kwin_x11 dm: SDDM Distro: openSUSE Tumbleweed 20190829
Machine:  Type: Laptop System: Hewlett-Packard product: HP EliteBook 8570w v: A1028C1100 serial: <filter> Chassis:
          type: 10 serial: <filter>
          Mobo: Hewlett-Packard model: 176B v: KBC Version 50.1F serial: <filter> UEFI: Hewlett-Packard
          v: 68IAV Ver. F.71 date: 04/19/2019
Battery:  ID-1: BAT0 charge: 66.9 Wh condition: 66.9/66.9 Wh (100%) volts: 17.0/14.8 model: Hewlett-Packard Primary
          type: Li-ion serial: <filter> status: Full
          Device-1: hidpp_battery_0 model: Logitech M705 serial: <filter> charge: 60% rechargeable: yes
          status: Discharging
CPU:      Topology: Quad Core model: Intel Core i7-3720QM bits: 64 type: MT MCP arch: Ivy Bridge rev: 9
          L2 cache: 6144 KiB
          flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 41502
          Speed: 1198 MHz min/max: 1200/3600 MHz Core speeds (MHz): 1: 1198 2: 1197 3: 1197 4: 1197 5: 1198 6: 1204
          7: 1198 8: 1197
Graphics:  Device-1: NVIDIA GK107GLM [Quadro K1000M] vendor: Hewlett-Packard driver: nouveau v: kernel
          bus ID: 01:00.0 chip ID: 10de:0ffc
          Display: x11 server: X.Org 1.20.5 driver: nouveau unloaded: fbdev,modesetting,vesa alternate: nv,nvidia
          compositor: kwin_x11 resolution: 1600x900~60Hz
          OpenGL: renderer: NVE7 v: 4.3 Mesa 19.1.5 direct render: Yes
Audio:    Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel
          v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20
          Device-2: NVIDIA GK107 HDMI Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 01:00.1
          chip ID: 10de:0e1b
          Sound Server: ALSA v: k5.2.10-1-default
Network:  Device-1: Intel 82579LM Gigabit Network vendor: Hewlett-Packard driver: e1000e v: 3.2.6-k port: 5040
          bus ID: 00:19.0 chip ID: 8086:1502
          IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
          Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi v: kernel port: 4000
          bus ID: 25:00.0 chip ID: 8086:0082
          IF: wlo1 state: up mac: <filter>
Drives:    Local Storage: total: 5.46 TiB used: 1.50 TiB (27.5%)
          ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 2TB size: 1.82 TiB speed: 6.0 Gb/s serial: <filter>
          rev: 2B6Q scheme: GPT
          ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 4TB size: 3.64 TiB speed: 6.0 Gb/s serial: <filter>
          rev: 2B6Q scheme: GPT
          Message: No Optical or Floppy data was found.
Partition: ID-1: / size: 100.00 GiB used: 20.87 GiB (20.9%) fs: btrfs dev: /dev/sda4
          ID-2: /home size: 48.97 GiB used: 2.02 GiB (4.1%) fs: ext4 dev: /dev/sda5
          ID-3: /opt size: 100.00 GiB used: 20.87 GiB (20.9%) fs: btrfs dev: /dev/sda4
          ID-4: /tmp size: 100.00 GiB used: 20.87 GiB (20.9%) fs: btrfs dev: /dev/sda4
          ID-5: /var size: 100.00 GiB used: 20.87 GiB (20.9%) fs: btrfs dev: /dev/sda4
          ID-6: swap-1 size: 18.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda14
Sensors:  System Temperatures: cpu: 50.0 C mobo: N/A gpu: nouveau temp: 127 C
          Fan Speeds (RPM): N/A
Info:      Processes: 256 Uptime: 1h 15m Memory: 15.59 GiB used: 1.51 GiB (9.7%) Init: systemd v: 242 runlevel: 5
          target: graphical.target Compilers: gcc: N/A Shell: bash v: 5.0.7 running in: konsole inxi: 3.0.32

Code:

$ sudo hwinfo --netcard
12: PCI 2500.0: 0282 WLAN controller                           
  ... <omitted> ...
  Attached to: #17 (PCI bridge)

18: PCI 19.0: 0200 Ethernet controller
  [Created at pci.386]
  Unique ID: IDxx.xxxxxxx <edited out>
  SysFS ID: /devices/pci0000:00/0000:00:19.0
  SysFS BusID: 0000:00:19.0
  Hardware Class: network
  Model: "Intel 82579LM Gigabit Network Connection (Lewisville)"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x1502 "82579LM Gigabit Network Connection (Lewisville)"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x176b
  Revision: 0x04
  Driver: "e1000e"
  Driver Modules: "e1000e"
  Device File: enp0s25
  Memory Range: 0xd9400000-0xd941ffff (rw,non-prefetchable)
  Memory Range: 0xd943b000-0xd943bfff (rw,non-prefetchable)
  I/O Ports: 0x5040-0x505f (rw)
  IRQ: 34 (136310 events)
  HW Address: xx:xx:xx:xx:xx:xx <edited out>
  Permanent HW Address: xx:xx:xx:xx:xx:xx <edited out>
  Link detected: yes
  Module Alias: "pci:v00008086d00001502sv0000103Csd0000176Bbc02sc00i00"
  Driver Info #0:
    Driver Status: e1000e is active
    Driver Activation Cmd: "modprobe e1000e"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

Code:

$ testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

# Global parameters
[global]
        logon drive = P:
        logon home = \\%L\%U\.9xprofile
        logon path = \\%L\profiles\.msprofile
        map to guest = Bad User
        name resolve order = bcast host lmhosts wins
        netbios name = TMBLWD-8570
        preferred master = Yes
        server string = ""
        usershare allow guests = Yes
        usershare max shares = 100
        workgroup = LRLINWINGRP
        idmap config * : backend = tdb
        include = /etc/samba/dhcp.conf

[TW-AVs-I-shared]
        comment = I in AVs shared
        force user = myself
        path = /home/myself/AVs/I
        read only = No
        valid users = myself

[TW-VMs-V-shared]
        comment = VMs in VMs shared
        force user = myself
        path = /home/myself/VMs/VMs
        read only = No
        valid users = myself

[TW-XCs-X-shared]
        comment = X in XCs shared
        force user = myself
        path = /home/myself/XCs/X
        read only = No
        valid users = myself

Remarks: For setting up the Samba Servers on both Linuxes, the sticky post by swerdna here https://forums.opensuse.org/showthre...-the-local-LAN was most helpful - thanks for providing this.
I did also consult this very recent thread here https://forums.opensuse.org/showthre...ows(dual-boot), but despite the promising title I couldn't get much help for my problem from it.

I have a couple of questions or doubts regarding my procedure right away: Is it correct to have zeroconf (as avahi/Bonjour) running at the same time as Samba (netBIOS)? Is the "name resolve order = bcast host lmhosts wins" in /etc/samba/smb.conf the best possible way; it was taken from swerdna's post cited above.

Any help is gratefully apreciated in advance.

LEAP 15.1 Leap 15.x support for Dell XPS 7590 [Killer 1650x wi-fi network adaptor]

$
0
0
Is there going to be support for Dell XPS laptops doesn't appear to drivers for the Killer 1650x wi-fi network adaptor, it would be good to run Opensuse Leap 15.x on these machines.

TUMBLEWEED Can't get service to start on boot

$
0
0
Mullvad VPN won't enable on boot.

Code:

sudo systemctl enable mullvad-daemon.service
Code:

sudo systemctl start mullvad-daemon.service
VPN runs and connects successfully. But after reboot the application starts but hangs on "connecting to Mullvad system service."

I then
Code:

sudo systemctl start mullvad-daemon.service
and it connects and runs fine.

I check in Yast under services-manager on a fresh boot and it is in fact set to start on boot but it is listed as "Inactive(Dead)" until I manually start it.

What am I doing wrong? I thought using the enable flag sets it to start on boot so that one doesn't have to use the "start" flag every time on boot?

Thanks
Viewing all 40713 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>