I restored from a month old backup using dd, and now have Fedora 28 installed. My audio issues are also gone.
Moral: Always backup your OS as well as your data.
2 Likes
I’m sorry I missed your reply. I’m using AMD Vega 64 and Samsung 1TB 970Evo on Asus Crosshair VII Wifi.
With new Ubuntu 18.10 install I again had troubles waking from USB.
step1 – sudo su
step2 - grep . /sys/bus/usb/devices/*/product
take note the usb buss number between device and product, mine shows
/sys/bus/usb/devices/3-2.1.1.2/product:G Pro Gaming Mouse
if you are not using a hub it may show just (usb1,usb2,usb3,usb4,usb5,usb6,usb7,usb8)
between the devices and product.
Step3 - lsusb which will show buss and product ID’s
take note of the 4 digits before and after the colon, mine shows
Bus 003 Device 006: ID 046d:c085 Logitech, Inc.
step4 - sudo nano /etc/udev/rules.d/10-wakeup.rules
add this line replacing the idVendor and idProduct from step 3 and the usb buss number between devices and power taken from step 2
ACTION==“add”, SUBSYSTEM==“usb”, ATTRS{idVendor}==“046d”, ATTRS{idProduct}==“c085” RUN+="/bin/sh -c ‘echo enabled > /sys/bus/usb/devices/3-2.1.1.2/power/wakeup’"
step5 – reboot and run grep . /sys/bus/usb/devices/*/power/wakeup to verify your device shows “enabled”
What kernel are you using?
Hi there. So AMDGPU drivers are still broken after two months of waiting. My main monitor is stuck at 60hz instead of 95hz. As everything I tried failed to get it to work I would like to make a bug report.
Where can I do that and how? This is going to be my first time ever doing any kind of linux related bug report.
what have you tried to get it to work - I have amdgpu with multi monitors and am currently overclocking both without difficulty.
If you want to try to debug this again:
- What Distro are you using?
- X11 or wayland?
- What GPU?
The problem you are having could be a wayland/x11 issue instead of the driver.
Fedora 29, X11, Vega64 and I am on the latest kernel 4.19.6-300.fc29.
Not to repeat myself. Here is my thread: Missing refresh rate for my monitor
I could add that I got what I think is a good Modeline out of the windows radeon display information. I used some modeline calculators online to get from 689.50 G.Pixel to 503.60 G.Pixel which is in windows and working.
Also Ubuntu 18.04 liveUSB with it’s ancient kernel works out of the box. That means anything they did in the past half year broke.
Ah I see - sorry didn’t know you had a thread going already. Would recommend trying 75hz to see if we can increase the refresh rate at all.
what do you get if you run:
gtf 3440 1440 75
#edit: reason I ask with gtf is I get different results than cvt and the cvt results doesn’t work with my machine.
I tried but it doesn’t work. The best part is I can’t even go past 60hz. Even 61hz results in a black screen or not even applying it out right. With cvt or gtf.
There is just something wrong with the open source drivers. And I have the feeling if I don’t report this somewhere it wont be fixed as these korean monitors are pretty uncommon.
I am baffled as to how Wendell didn’t encounter this problem. He has lots of them and I saw exactly this one in his last videos in the background. Then again he is running Windows 10 as far as I saw it.
I’m totally baffled then.
Thank you for helping anyway. If this won’t go anywhere, I have a few options. Installing AMDGPU-PRO but there is almost no tutorial guide for it. Swap vega for my GTX 980ti and install proprietary drivers. Or go back to Windows. Either way I will do something till the end of the year. I cannot stand this laggy mess anymore.
4.19.8-041908-generic
I was able to get my system waking from the usb mouse, I had to change the buss from usb3 to 3-2.1.1.2
From
“ACTION==“add”, SUBSYSTEM==“usb”, ATTRS{idVendor}==“046d”, ATTRS{idProduct}==“c085” RUN+=”/bin/sh -c ‘echo enabled > /sys/bus/usb/devices/usb3/power/wakeup’
TO
ACTION==“add”, SUBSYSTEM==“usb”, ATTRS{idVendor}==“046d”, ATTRS{idProduct}==“c085” RUN+="/bin/sh -c ‘echo enabled > /sys/bus/usb/devices/3-2.1.1.2/power/wakeup’
2 Likes
Interesting. Thanks for posting the fix.
How can I get Discord on Linux in its own window or as a tint2 tray widget without installing the close-source discord client? I don’t always have a web browser open and tend to close discord tabs by accident and not notice until hours later.
There’s a libpurple discord plugin that should let you use it with pidgin
Thanks, got it installed in Debian by compiling from source and adding the plugin to pidgin. It doesn’t seem to show unread messages in the tray icon, pull chat history, profile pictures, or sort messages by last activity. I don’t think this works for me.
I think a more elegant solution would be to have a separate firefox install/profile that has discord as the homepage. Running “firefox --profilemanager” to make a new profile then "firefox -p " would accomplish this. No tray icon, but you can enable desktop notifications to get nagged as new messages come in.
EDIT: A far simpler option is to open the discord web client in firefox, right click the tab and click “pin”. It will permanently be on the tab bar, can’t be closed, and will show unread messages through the little red number/circle in the tab icon. If you have desktop notifications enabled in discord and your OS, you will also get a toast notification.
I would recommend submitting an issue on the purple-discord github, maybe he can add those features at some point.
Could Someone help me understand what I have to do to fix this issue. I’m on Mint Cinnamon 19 and my computer keeps soft freezing and then hard freezing after this message appears in my kernel log:
mmap: qtdemux0:sink (3605): VmData 268607488 exceed data ulimit 268435456. Update limits or use boot option ignore_rlimit_data.
I have found a thread where Linus responds to this problem citing a Database Size Limit needing to be deleted or altered, but I’m not quite sure where to find this variable and in what config file it may reside. Thread: https://lkml.org/lkml/2016/9/16/585
I’m not a complete noob and I’m more than capable of editing a config file, but I just don’t know where to look. These hard freezes are really killing me and forcing me to hard reboot quite often. And it’s definitely consistent whereas this is the last message in my kern.log.1 everytime I hard Reset after a lockup.
Try editing /etc/systemd/system.conf and /etc/systemd/user.conf and raise the DefaultLimitNOFILE value
Thanks for the ultrafast response. I’m looking at those config files right now and those variables are currently commented out and have no value at the end. Should I uncomment it and add some arbitrarily larger value or is there a specific value you’d recommend to add to this? Also what’s the syntax, should it be just a large number in bytes or can I specify like 1GB or something?