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

OTHER VERSION Newby loaded CENTOS 8 cant get NightHawk 1900 driver to load

$
0
0
make command created this output:

make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.18.0-147.5.1.el8_1.x86_64/build M=/etc/NETGEAR_Nighthawk_AC1900 modules
make[1]: Entering directory '/usr/src/kernels/4.18.0-147.5.1.el8_1.x86_64'
CC [M] /etc/NETGEAR_Nighthawk_AC1900/core/rtw_cmd.o
In file included from /etc/NETGEAR_Nighthawk_AC1900/include/osdep_service.h:41,
from /etc/NETGEAR_Nighthawk_AC1900/include/drv_types.h:32,
from /etc/NETGEAR_Nighthawk_AC1900/core/rtw_cmd.c:22:
/etc/NETGEAR_Nighthawk_AC1900/include/osdep_service_linux.h: In function ‘_init_timer’:
/etc/NETGEAR_Nighthawk_AC1900/include/osdep_service_linux.h:273:8: error: ‘_timer’ {aka ‘struct timer_list’} has no member named ‘data’
ptimer->data = (unsigned long)cntx;
^~
/etc/NETGEAR_Nighthawk_AC1900/include/osdep_service_linux.h:274:2: error: implicit declaration of function ‘init_timer’; did you mean ‘_init_timer’? [-Werror=implicit-function-declaration]
init_timer(ptimer);
^~~~~~~~~~
_init_timer
In file included from /etc/NETGEAR_Nighthawk_AC1900/include/drv_types.h:35,
from /etc/NETGEAR_Nighthawk_AC1900/core/rtw_cmd.c:22:
/etc/NETGEAR_Nighthawk_AC1900/include/wifi.h: At top level:
/etc/NETGEAR_Nighthawk_AC1900/include/wifi.h:1019: warning: "IEEE80211_MAX_AMPDU_BUF" redefined
#define IEEE80211_MAX_AMPDU_BUF 0x40

In file included from ./include/net/cfg80211.h:21,
from /etc/NETGEAR_Nighthawk_AC1900/include/osdep_service_linux.h:87,
from /etc/NETGEAR_Nighthawk_AC1900/include/osdep_service.h:41,
from /etc/NETGEAR_Nighthawk_AC1900/include/drv_types.h:32,
from /etc/NETGEAR_Nighthawk_AC1900/core/rtw_cmd.c:22:
./include/linux/ieee80211.h:1444: note: this is the location of the previous definition
#define IEEE80211_MAX_AMPDU_BUF 0x100

cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:313: /etc/NETGEAR_Nighthawk_AC1900/core/rtw_cmd.o] Error 1
make[1]: *** [Makefile:1547: _module_/etc/NETGEAR_Nighthawk_AC1900] Error 2
make[1]: Leaving directory '/usr/src/kernels/4.18.0-147.5.1.el8_1.x86_64'
make: *** [Makefile:1699: modules] Error 2

Any suggestions?

Trying to build BR-CAD. Cmake out of memory?

$
0
0
So I was trying to build BRL-CAD with osc build command.

The spec file is in the branch here:
https://build.opensuse.org/package/s...brlcad/BRL-CAD

Some digging on "ReserveShadowMemoryRange failed while trying to map" and "Perhaps you're using ulimit -v" suggest that is could be a memory limit which building of BRL-CAD exceeds.

Is that really a problem? How do I raise limit?
My computer still have plenty of memory when building it.
Maybe building BRL-CAD might not be a best choice.

Code:

CMake Error at misc/CMake/BRLCAD_Util.cmake:90 (_message):
[  53s]  Could not run hostname reporting utility: ==1629==ERROR: AddressSanitizer
[  53s]  failed to allocate 0xdfff0001000 (15392894357504) bytes at address
[  53s]  2008fff7000 (errno: 12)
[  53s]
[  53s]  ==1629==ReserveShadowMemoryRange failed while trying to map 0xdfff0001000
[  53s]  bytes.  Perhaps you're using ulimit -v
[  53s]
[  53s]  Child aborted
[  53s] Call Stack (most recent call first):
[  53s]  CMakeLists.txt:3035 (message)
[  53s]
[  53s]
[  53s] -- Configuring incomplete, errors occurred!
[  53s] See also "/home/abuild/rpmbuild/BUILD/trunk-7.30.0.74914/build/CMakeFiles/CMakeOutput.log".
[  53s] See also "/home/abuild/rpmbuild/BUILD/trunk-7.30.0.74914/build/CMakeFiles/CMakeError.log".
[  53s] error: Bad exit status from /var/tmp/rpm-tmp.itTTya (%build)
[  53s]
[  53s]
[  53s] RPM build errors:
[  53s]    Bad exit status from /var/tmp/rpm-tmp.itTTya (%build)
[  53s]
[  53s] linux-edcv failed "build brlcad.spec" at Sun Feb 16 16:23:16 UTC 2020.

LEAP 15.1 .timer conflict?

$
0
0
systemctl status gives the following:

Code:

systemctl status fstrim.timer● fstrim.timer - Discard unused blocks once a week
  Loaded: loaded (/usr/lib/systemd/system/fstrim.timer; enabled; vendor preset: enabled)
  Active: active (waiting) since Sat 2020-02-15 04:58:46 MST; 1 day 11h ago
  Trigger: Mon 2020-02-17 00:00:00 MST; 7h left
    Docs: man:fstrim
   
systemctl status mlocate.timer
● mlocate.timer - Daily locate database update
  Loaded: loaded (/usr/lib/systemd/system/mlocate.timer; enabled; vendor preset: disabled)
  Active: active (waiting) since Sat 2020-02-15 06:22:11 MST; 1 day 10h ago
  Trigger: Mon 2020-02-17 00:00:00 MST; 7h left
    Docs: man:updatedb

They're both triggered at the same time. I know they are doing different things, but can they get in each other's way? (I just discovered that updatedb.timer is no more, and was replaced by mlocate.timer, which I enabled just yesterday. I've not got the foggiest why I didn't notice the db wasn't being updated automatically. I do run updatedb quite often, though.)

TIA

LEAP 15.2 The proper way to install jekyll with rbenv

LEAP 15.1 KDE desktop: Howto change action from single to double click?

$
0
0
Hello All,

On the desktop a single click on an icon launches the tool. How is that changed to double click?

Thanks,
Gert

LEAP 15.1 Removable device notification in Dolphin

$
0
0
Hi,
I'm running Leap 15.1 with KDE Plasma 5.12.8 and Dolphin 18.12.3. In the past removable devices showed up in the devices section on the left of the Dolphin screen. By clicking on it one could mount it or unmount it before removal. This feature has disappeared on my system recently. So when I plug in a USB stick I get three action choices of which I choose the one that starts another instance of Dolphin. I find that less handy than what I used to do. Is there a setting in the system settings to go back to what was before? What did I miss? Thanks for any hint!

TUMBLEWEED "at-bus-launcher not responding" error when trying to shut down????

$
0
0
Folks:

Posting in this sub-forum to follow up on what was a significant problem in TW and possibly grub, took a lot of heavy lifting from the forum gurus to repair, but since then the system has been running well . . . using the "default video module" as per "mrmazda's" suggestion . . . rather than "nouveau" or "nvidia" . . . although there might be some issues with getting a TTY shell to show up . . . ???? But that isn't today's complaint . . . .

Ran a search of "at-bus-launcher" and "no results found" was the response, so I'm posting here to report that every time I try to shut down from the main menu an error of "at-bus-launcher is not responding, would you like to shut down anyway?" error dialogue opens . . . if I click yes, the machine must go into a "shutting down in one minute, but from a few seconds from now . . ." mode, because the machine pauses for awhile before then beginning to shut down . . . .

I prefer that when I click "shut down" the machine just "shuts down" . . . no error window asking me if I "really want to shut down because people are still doing stuff and would like to keep doing that, particularly mr. bus-launcher is busy" type message . . . . Any way to work around that problem??

thanks kindly,

TUMBLEWEED QV4L2 segmentation fault (core dumped) | Tumbleweed

$
0
0
Hello,

when I try to start QV4l2 I have a segmentation fault on tumbleweed.

This program is available in official repos and the problem has been present for several weeks...

How can I try to solve that?

TUMBLEWEED Best Method To Install Audio/Video Codecs?

$
0
0
Hi,

Just noticed that I need to install audio/video codecs.
How can I do the above easily?
Thanks!

Jesse

TUMBLEWEED Computer temperature - AMD Ryzen 5 3600

$
0
0
Hello,


I just received my new computer which is very fast. Unfortunately, as it goes fast, this one heats up! I wonder: Do I really have the processor temperature with the sensors command:


Here is after a short game session:

Code:

florian@localhost:~> sensors
amdgpu-pci-2900
Adapter: PCI adapter
vddgfx:      725.00 mV
fan1:        863 RPM  (min =    0 RPM, max = 3200 RPM)
edge:        +63.0°C  (crit = +91.0°C, hyst = -273.1°C)
power1:      13.02 W  (cap = 196.00 W)


k10temp-pci-00c3
Adapter: PCI adapter
Tdie:        +80.5°C  (high = +70.0°C)
Tctl:        +80.5°C


Then I tried the command:


Code:

localhost:/home/florian # sensors-detect

Here's the result:


Code:

localhost:/home/florian # sensors
nct6795-isa-0a20
Adapter: ISA adapter
Vcore:                776.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                    1.03 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
AVCC:                    3.39 V  (min =  +2.98 V, max =  +3.63 V)
+3.3V:                  3.41 V  (min =  +2.98 V, max =  +3.63 V)
in4:                  1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                  152.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                  784.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
3VSB:                    3.38 V  (min =  +2.98 V, max =  +3.63 V)
Vbat:                    3.33 V  (min =  +2.70 V, max =  +3.63 V)
in9:                    1.85 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                    0.00 V  (min =  +0.00 V, max =  +0.00 V)
in11:                  712.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                    1.01 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                  608.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                    1.54 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                    0 RPM  (min =    0 RPM)
fan2:                  1200 RPM  (min =    0 RPM)
fan3:                  1290 RPM  (min =    0 RPM)
fan4:                    0 RPM  (min =    0 RPM)
fan5:                    0 RPM  (min =    0 RPM)
SYSTIN:                +36.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM  sensor = CPU diode
CPUTIN:                +35.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN0:                +38.0°C  (high = +115.0°C, hyst = +90.0°C)  sensor = thermistor
AUXTIN1:              -128.0°C    sensor = thermistor
AUXTIN2:                +42.0°C    sensor = thermistor
AUXTIN3:                -3.0°C    sensor = thermistor
SMBUSMASTER 0:          +44.5°C 
PCH_CHIP_CPU_MAX_TEMP:  +0.0°C 
PCH_CHIP_TEMP:          +0.0°C 
PCH_CPU_TEMP:            +0.0°C 
intrusion0:            ALARM
intrusion1:            ALARM
beep_enable:          disabled


amdgpu-pci-2900
Adapter: PCI adapter
vddgfx:      1000.00 mV
fan1:        834 RPM  (min =    0 RPM, max = 3200 RPM)
edge:        +41.0°C  (crit = +91.0°C, hyst = -273.1°C)
power1:      55.15 W  (cap = 196.00 W)


k10temp-pci-00c3
Adapter: PCI adapter
Tdie:        +44.1°C  (high = +70.0°C)
Tctl:        +44.1°C


During the configuration, the temperature went down ... But I don't see the temperature of each processor core ... And I only have the temperature of "Adapter: PCI adapter" is this normal?


I also tested the applet Simple System Monitor but it does not display the processor temperature ...


And if you have time, a small subsidiary question: when configuring sensors-detect I was told that certain detections were risky ... Do you know why?


Thanks for your help !

Mesa 19.3.4 уже вышла и уже доступна на Leap и TW

$
0
0
Раньше всех, до объявления на сайте Mesa :P

Имеется ввиду установка Experimental.

Quote:

Вс 16 фев 2020 17:00:00
Stefan Dirsch <sndirsch@suse.com>
- Update to version 19.3.4
* changes all over the tree, but aco and anv are leading the
way in changes
- supersedes u_Revert_gallium_Fix_big-endian_addressing_of_non-bitmask_array_formats.patch
Чт 06 фев 2020 17:00:00
Stefan Dirsch <sndirsch@suse.com>
- u_Revert_gallium_Fix_big-endian_addressing_of_non-bitmask_array_formats.patch
* replaces U_gallium-Fix-big-endian-addressing-of-non-bitmask-arr.patch
by an official merge request (bsc#1162252, gitlab issue#2472)
Пн 03 фев 2020 17:00:00
Stefan Dirsch <sndirsch@suse.com>
- U_gallium-Fix-big-endian-addressing-of-non-bitmask-arr.patch
* reverse apply since it caused a regression in rendering on
s390x (bsc#1162252)
Ср 29 янв 2020 17:00:00
Stefan Dirsch <sndirsch@suse.com>
- require and check for llvm-devel >= 9 instead of llvm9-devel on
openSUSE
Ср 29 янв 2020 17:00:00
Stefan Dirsch <sndirsch@suse.com>
- enabled build of gallium based llvmpipe driver for s390x
(related to jsc#IBM-369, jsc#SLE-7452)

TUMBLEWEED Please Release "Bleachbit" System Cleaner For Tumbleweed...

$
0
0
Hi,

Been using openSUSE Tumbleweed KDE 64Bit for about a week.
My only complaint is "BleachBit" system cleaner is not available for Tumbleweed.
Will it be released soon?

Jesse

TUMBLEWEED Inputs not used through USB hub

$
0
0
Hello,

I have a USB hub on my desk, 10 ports with external power supply, that I use for ease of access, powering random stuff, and for easy switching of keyboard and mouse to my Raspberry Pies. After dist-upgrading and rebooting this Sunday morning (2020-02-16T09:21Z), my keyboard and mouse did not work (I `zypper dup` every Sunday morning).

They work fine when plugged in the front USB ports of the PC. Keyboard works fine through the hub in BIOS and GRUB. USB sticks work fine through the hub. Hub works fine with another PC.

Outputs of `lsusb` and `dmesg` are strictly identical when connecting and disconnecting to the hub and front ports, modulus the actual USB tree structure and device numbers: they are correctly detected and drivers properly loaded.
Xorg log shows connection/disconnection when done through the front ports, but absolutely nothing when done through the hub.

I tried force-reinstalling libinput, but the problem persists.

Any idea? What could be interfering between the kernel and Xorg?

Thanks,

--
cigix

TUMBLEWEED Logitech K120

$
0
0
The Logitech K120 keyboard is a bare-bones wired keyboard which appears to be supported by Linux kernel 2.6+ (according to their website), yet is not recognized in Tumbleweed. The only reason I purchased this keyboard is to ensure I have something during my builds/setups, so I'm a little disappointed that such a basic device isn't recognized but such a sweet, sweet distribution.

I have a number of Logitech devices now that don't seem to be supported for whatever reason (M720 Triathlon mouse & N305 numberpad) and I'm looking to change that.

I know the basics of C and figure this is something I should really know how to do by now, but don't know where to start. Can anyone point me in the right direction for the basics of building device drivers for openSUSE?

Much appreciated.

TUMBLEWEED Kontact lost all email

$
0
0
I'm running an up-to-date version of tumbleweed with KDE plasma 5.18.0 and kernel 5.5.2-1. This morning I noticed that kmail wasn't downloading email from all my accounts. Following some advice I found at forum.kde.org, I tried the following:
Code:

akonadictl restart
But that led to a disaster. All the folders in kmail are now empty--inbox, sent mail, drafts, etc. All in all about 20,000 messages are gone. I tried restarting from a snapshot but that didn't restore the missing emails.

The storage path for the local folders in kmail is ~/.local/share/akonadi_maildir_resource_0. And when I open that folder in Dolphin it's filled with thousands of files but for some reason they're not showing up in the kmail desktop folders.

I'd be very grateful for any advice.

TUMBLEWEED /usr/sbin/named (BIND DNS server; named.service) not working anymore due to directory access issues

$
0
0
I suspect that this is a 'capabilities' issue, rather than a simple file permissions problem.

After upgrading Tumbleweed today, named.service (DNS server) doesn't run anymore. The error says:

17-Feb-2020 20:12:37.313 loading configuration from '/etc/named.conf'
17-Feb-2020 20:12:37.314 directory '/var/lib/named' is not writable
17-Feb-2020 20:12:37.314 /etc/named.conf:21: parsing failed: permission denied
17-Feb-2020 20:12:37.314 loading configuration: permission denied

That directory has reasonable permissions and ownership:

% ls -ld /var/lib/named
drwxr-xr-x 1 named named 222 Feb 17 20:04 /var/lib/named

Setting it to 775 doesn't fix things. However, setting it to 777 does, and gets me to the next problem:

17-Feb-2020 20:13:57.888 managed-keys-directory '/var/lib/named/dyn/' is not writable
17-Feb-2020 20:13:57.891 loading configuration: permission denied

Looking at the run (via "strace named -g"), I don't see anything that looks like a permissions problem at all. No obvious errors, in fact.

I tried disabling AppArmor (because that's almost always a cause of problems, at least for me), and that did nothing. I am NOT using SELinux. Before the upgrade ("zypper -n dup --no-recommends --auto-agree-with-licenses --replacefiles --allow-vendor-change"), the system was running correctly, including named.service.

Here's the only (really horrible!) work-around I've found that brings named back to life:

chmod 777 /var/lib/named /var/lib/named/dyn

Obviously, that can't be a long-term solution. But at least I'm back up and running.

I searched this forum and the bug reports to see if there was anything similar. I found nothing. I searched via google, and found users who had fat-fingered configuration files, but that's not the issue here. Something about the directory access or permissions model has gone haywire.

LEAP 15.2 Very, very early report on 15.2 Alpha running on VBox 6.1.2

$
0
0
Considering 15.2 is currently in Alpha,
I don't know what should be expected, only that things are so early one should expect a ton of things to be broken and will need to be fixed. And, for that reason it's really too early but the most curious to install 15.2 at the moment.

This is a short summary of current status of the very latest 15.2 configured for an original LXQt DE running on the very latest VBox installed from Oracle (6.1.2).

Noticed the extraordinarily large download (about 6GB total) which wasn't too surprising since until officially released I'd expect that there's plenty of tracking code everywhere that will be removed eventually.
Kernel 5.3 which is both surprising and disappointing. Had hoped to see at least something on par with TW. No real importance now though, of course. I expect that by the time 15.2 ships it will have at least 5.6 and that will likely involve lots of work modifying numerous applications.

One of the first things I noticed is that 15.2 seems to be continuing the broken install for DE other than the standard ones offered in "System Roles" -- Too bad, since it was removed IIRC literally a week before the 15.0 launch for unknown reasons, it's never been fixed so a long explanation has to be provided every time someone wants to install something other than Gnome or KDE as the only DE... which is often and growing as other distros eliminate their support for more than one or two DE and come to openSUSE for their favorite DE.

Currently, looks like not too much has been done to integrate LXQt, the usual apps display as menu options but the usual problems with every release are there... The background is default which usually means the path to where the openSUSE recommended images is likely incorrect.


It looks like the base install upon detecting Virtualbox might have tried to install the VBox HostOS (main) app instead of Guest packages.
So, my first test was to go ahead and install the VBox Guest packages, and there are a lot of them now (I think there were more than 6?). Despite being the correct version (6.1.2), they're currently broken. No change.
After uninstalling the openSUSE virtualbox packages (all of them)
I installed Guest Additions using the ISO.
Found that the compile dependencies were already installed (Is this intentional? I would have assumed those would have been removed even for the Alpha)
Successfully built the kernel modules, and install went fine.
Rebooted.
Found that the background was now completely black, but otherwise all the Guest Additions functionality I tested was working.

Again,
IMO 15.2 Alpha is only for the curious at this point,
There's plenty of work that has to be done before Users can experience something close to more usable than broken.
That is, unless Developers for specific areas have worked on something and put out a request for Users to try that out...

IMO,
TSU

TUMBLEWEED No app icons in the tray since Plasma 5.18

$
0
0
Hi all,
since the update to Plasma 5.18 I do not see application icons in the tray.
I do have applets visible in the tray, but all applications that show icons in the tray (e.g. Telegram desktop, RedNotebook, Wavebox, Remmina, ecc.) are completely gone.
Sometimes they do show for a split second, only to disappear immediately after. They are not visible even after expanding the tray to show hidden icons.
I tried to kill and restart xembedsniproxy, without success.
When restarting xembedsniproxy, however, I get this:
Code:

kde.xembedsniproxy: could not register SNI: "The name org.kde.StatusNotifierWatcher was not provided by any .service files"
kde.xembedsniproxy: could not register SNI: "The name org.kde.StatusNotifierWatcher was not provided by any .service files"
kde.xembedsniproxy: could not register SNI: "The name org.kde.StatusNotifierWatcher was not provided by any .service files"
Container window visible, stack below
Container window visible, stack below
Container window visible, stack below

Anybody else? Any ideas?

Thank you in advance
Cris

TUMBLEWEED installing obmenu

$
0
0
I installed openbox in the latest Tumbleweed. I can't install obmenu because it is not in the packman repos. How can I install obmenu?

TUMBLEWEED Installer doing weird things

$
0
0
So here's the thing, I had installed tumbleweed before with no problems.
This time after wiping my (sata)ssd i insert the usb to start the installation.
While the installer loads a screen pops up telling me that i need to download the kernel to proceed.
What that did is (for some reason) it copied my iso to a new partition on the ssd.
After that when reaching the partitioning section the ssd was not a choice.
I proceeded to the expert partitioner where i saw my ssd with a partition housing the copy of the iso.
I went a ahead and gave instructions to delete the partition and create the proper partitions needed.
Now mind you i booted from my usb stick initialy.
When reaching the point where the install begun an error popped saying that the partition of the iso cannot be deleted since it is busy.
Errors then followed for the rest of the partition creations saying that the command used to create them has also failed.
I tried this multiple times wiping my hard drive with a bios tool and making sure that it was empty each time.
Same error persisted.
From what i understand based on the way the process behaves it tries to boot from usb, realizes there is no kernel :sarcastic: and therefore proceeds to copy the iso to the drive and boot from there.

Any help will be appreciated, pictures will be posted when i get home if needed
Viewing all 40713 articles
Browse latest View live


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