thomasdouwes
Now
•
100%
Looks like you where right about the udev rules earlier, I ran a pacman command to find all untracked files in /usr and I found /usr/lib/udev/rules.d/50-remove-nvidia.rules was there. Contents:
# Automatically generated by EnvyControl
# Remove NVIDIA USB xHCI Host Controller devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c0330", ATTR{power/control}="auto", ATTR{remove}="1"
# Remove NVIDIA USB Type-C UCSI devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c8000", ATTR{power/control}="auto", ATTR{remove}="1"
# Remove NVIDIA Audio devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x040300", ATTR{power/control}="auto", ATTR{remove}="1"
# Remove NVIDIA VGA/3D controller devices
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x03[0-9]*", ATTR{power/control}="auto", ATTR{remove}="1"
looks like EnvyControl left some extra files after uninstalling.
Personally, I think it's pretty weird that it put runtime files in /usr/lib, if they where in /etc I would have found them quickly.
The GPU is back on the bus now and I can run optimus-manager to get my extra screen. Thank you for the help troubleshooting this issue.
thomasdouwes
Now
•
100%
dkms status doesn't even list half of my DKMS modules for some reason
thomasdouwes
Now
•
100%
I don't seem to have an -F on my dkms? when I ran that it without, it didn't rebuild all the DKMS modules for some reason, just bbswitch and evdi
thomasdouwes
Now
•
100%
interesting, that did show the nvidia card in dmesg, still not in lspci though
[ 1110.598286] pci 0000:01:00.0: [10de:1ba1] type 00 class 0x030000
[ 1110.598301] pci 0000:01:00.0: reg 0x10: [mem 0xde000000-0xdeffffff]
[ 1110.598310] pci 0000:01:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref]
[ 1110.598318] pci 0000:01:00.0: reg 0x1c: [mem 0xd0000000-0xd1ffffff 64bit pref]
[ 1110.598324] pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f]
[ 1110.598330] pci 0000:01:00.0: reg 0x30: [mem 0xdf000000-0xdf07ffff pref]
[ 1110.599069] pci 0000:01:00.0: vgaarb: bridge control possible
[ 1110.599073] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[ 1110.599078] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
[ 1110.599125] pci 0000:01:00.1: [10de:10f0] type 00 class 0x040300
[ 1110.599135] pci 0000:01:00.1: reg 0x10: [mem 0xdf080000-0xdf083fff]
[ 1110.599327] pci 0000:01:00.0: BAR 1: assigned [mem 0xc0000000-0xcfffffff 64bit pref]
[ 1110.599335] pci 0000:01:00.0: BAR 3: assigned [mem 0xd0000000-0xd1ffffff 64bit pref]
[ 1110.599341] pci 0000:01:00.0: BAR 0: assigned [mem 0xde000000-0xdeffffff]
[ 1110.599344] pci 0000:01:00.0: BAR 6: assigned [mem 0xdf000000-0xdf07ffff pref]
[ 1110.599347] pci 0000:01:00.1: BAR 0: assigned [mem 0xdf080000-0xdf083fff]
[ 1110.599349] pci 0000:01:00.0: BAR 5: assigned [io 0xe000-0xe07f]
[ 1110.599384] pci 0000:01:00.1: extending delay after power-on from D3hot to 20 msec
[ 1110.599418] pci 0000:01:00.1: D0 power state depends on 0000:01:00.0
[ 1110.599509] snd_hda_intel 0000:01:00.1: enabling device (0000 -> 0002)
[ 1110.599624] snd_hda_intel 0000:01:00.1: Disabling MSI
[ 1110.599630] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[ 1110.603829] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=none,decodes=io+mem:owns=io+mem
[ 1110.628268] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input18
[ 1110.628341] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input19
[ 1110.628403] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input20
[ 1110.628464] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card2/input21
thomasdouwes
Now
•
100%
hmm, maybe downgrading nvidia-dkms might work? I'll try that
thomasdouwes
Now
•
100%
yeah, they are a bit of a pain, but it's a new one to me for the card to just disappear completely. It's hard to do any troubleshooting when you can't even access the card.
thomasdouwes
Now
•
100%
I had a look at /etc/udev, /etc/modprobe.d and /etc/modules-load.d, and don't see anything related to nvidia. Are there any more udev or blacklist folders to look at?
thomasdouwes
Now
•
100%
It's an MSI GE72MVR 7RG, what do mean version?
and it's an integrated intel GPU.
thomasdouwes
Now
•
100%
ls: cannot access '/sys/bus/pci/devices/0000:01:00.0': No such file or directory
I also tried booting an archiso and the GPU appears there, there must be something wrong with my install.
thomasdouwes
Now
•
100%
It disappeared without me booting into windows, I booted windows to test after it was gone. But I did just try to force a hard shutdown on windows and disabled fastboot, but it's still not appearing.
thomasdouwes
Now
•
100%
[ 1501.764754] nvidia-nvlink: Nvlink Core is being initialized, major device number 234
[ 1501.764761] NVRM: No NVIDIA GPU found.
[ 1501.765791] nvidia-nvlink: Unregistered Nvlink Core, major device number 234
I have an optimus laptop, and after the update to KDE6 optimus-manager stopped working. I needed a second display, and all my display outputs are on the Nvdia GPU, so I needed to switch. I tried many different X11 configs, envycontrol then more X11 configs, but I couldn't get it working right, it would only be the internal display or the external one, not both. after a few hours I gave up and tried optimus-manager again. This time I checked the error log and it was failing to load the nvidia module, I tried loading it manually but I got a "No such device" error, which is where the title of the post comes in. My GPU has disappeared from linux, it won't show up in lspci, lshw, nvidia-smi, or anything else it should. The only reference to the thing in dmesg I can find are : ``` [ 0.216410] pci 0000:01:00.0: [10de:1ba1] type 00 class 0x030000 [ 0.216419] pci 0000:01:00.0: reg 0x10: [mem 0xde000000-0xdeffffff] [ 0.216427] pci 0000:01:00.0: reg 0x14: [mem 0xc0000000-0xcfffffff 64bit pref] [ 0.216435] pci 0000:01:00.0: reg 0x1c: [mem 0xd0000000-0xd1ffffff 64bit pref] [ 0.216440] pci 0000:01:00.0: reg 0x24: [io 0xe000-0xe07f] [ 0.216445] pci 0000:01:00.0: reg 0x30: [mem 0xdf000000-0xdf07ffff pref] [ 0.216460] pci 0000:01:00.0: Enabling HDA controller [ 0.257300] pci 0000:01:00.0: vgaarb: bridge control possible [ 0.257300] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none [ 0.270521] pci 0000:01:00.1: D0 power state depends on 0000:01:00.0 ``` and then nothing, it doesn't even seem to try to load the nvidia module. I tried booting into windows and it shows up there fine, so the GPU didn't randomly die. As far as I can tell I've rolled back everything I did in my histfile until it stopped working, The only thing I could think is I upgraded my kernel to (6.7.9) from (6.6.10), could that have caused it? I also tried adding `pcie_port_pm=off` to the kernel params from the archwiki, but still nothing. I'm just at a loss here, anyone have any ideas? EDIT: I'm using the nvidia-dkms package EDIT2: one kernel downgrade later and it's still not appearing, so thats not it. EDIT3: fixed, see comments
thomasdouwes
Now
•
100%
Yeah, that is annoying. But for the "You won't BELIEVE what this microwave can do! 🤯🤯🤯" or worse the "This appliance from the 90s is going to REVOLUTIONIZE your kitchen!" at least become something that gives you some idea if you want to watch. Unfortunately some good videos are hidden behind shitty titles I otherwise wouldn't click.
Not technology connections obviously, their titles are fine.
thomasdouwes
Now
•
100%
It often overcorrects, like not every shitpost really needs a title that sounds like a news article. But for some really clickbaity YouTubers (most) it makes the titles much more usable. The titles are submitted by users, so if the streamer is very small there might be no one to write the titles.
- Enhancer for Youtube - uBlock Origin - CustomTube - Return YouTube Dislikes - Annotations Restored - SponsorBlock - DeArrow
I needed a PC to test a PCIe card recently, so I put something together with some spare parts. The only PSU I had around was a corsair CX750M I took from a prebuild from about 2014-2015, one with the green labels. Searching around the internet I see loads of people saying not to buy them, but what about one I already have? How bad really it is? Will it fry my motherboard or burn my house down? Or is it just inefficient?
thomasdouwes
Now
•
100%
Thanks for the detailed reply. I found a QSFP+ DAC that says it supports IB and Ethernet.
I don't have enough computers to set up a fabric, only the 2 I would be direct attaching have PCIE slots.
I've never used infiniband before so my reason for wanting to try it is just to learn what it is, and how it works. That said, some of those use-cases look very interesting, especially transporting NVMe namespaces, I didn't know that was possible.
I was found a listing on eBay for a "Mellanox CX354A ConnectX-3 FDR Infiniband 40GbE QSFP+" card for quite cheap. By the sound of the listing title it supports both infiniband *and* 40GbE, is that right? I would like to try out infiniband, but I would be buying for the 40GbE. And are there good drivers for modern linux distros for this card? Also, do I just buy some QSFP cables to direct attach them?
thomasdouwes
Now
•
100%
640,000GHz is nice
thomasdouwes
Now
•
100%
Yep, I wish I bought all my VR games from steam, but I bought a few from oculus when I first bought the headset. Also some games are oculus exclusive :/
thomasdouwes
Now
•
100%
I actually figured it out trying to login to the app, I just needed to login to meta with my oclulus account credentials and it migrated it, not the most obvious thing. I like how the app constantly asks for location permission despite me not having a quest to pair it to. Also I find it funny that they care so little for the CV1 it shows a rift S for its picture lol
thomasdouwes
Now
•
100%
Facebook has owned oculus since before the CV1, but I agree it was much less intergrated and still felt like a separate brand. I'm definitely biased as fuck, but "oculus" is infinitely better than "meta". Much better sounding name. I just made a meta account to migrate my oculus account, but I can't find any way to do it on PC without a quest. I don't have a quest, so I guess I'm fucked?
thomasdouwes
Now
•
100%
How do I even migrate??? I can't figure it out
thomasdouwes
Now
•
98%
How is this legal? Feels ridiculous to lose games I paid for just because I didn't migrate my account. Same with the Microsoft minecraft account migration. When I bought my CV1 there was the promise that I would not need a facebook account.
It's transmitting on 145.8MHz FM in the 2m HAM band times ([from amsat-uk](https://amsat-uk.org/2023/10/25/iss-sstv-verification-test-oct-27-nov-1/)): Fri Oct 27 at 12:15 GMT – Sun Oct 29 at 18:50 GMT Tue Oct 31 at 10:05 GMT – Wed Nov 01 at 18:10 GMT a couple more:  
From 2023-10-12 Projected:  Day Microphysics projected: 
Scan motor current is going up again, maybe it will fix?
The telemetry for the NOAA POES satellites is in the TIP data along with the HIRS and SEM data. The content is not known, but the format is. At least everything on the star nesdis page should be in there, including the AVHRR scan motor current I was looking for. I wrote a program to dump this telemetry to CSV and found the one column that rose at the same rate as the scan motor should. It's not a perfect match, NOAA probably multiplies it by some unknown value to find the actual current, and my data is only from when the satellite was overhead, so it's a bit low resolution  official NOAA data:  There are still hundreds of unknown values that I haven't and have no way of figuring out, here is the raw CSV data if anyone is interested: [link](https://i3b.co/D4E1E4F71108A9684DC31A6ABB68CFD1.zip) It's concatenated from months of data, so it's full of skips, there is a millisecond timestamp on the first column, but it's out a few hours and sometimes corrupted. Some fields are also super commutated still.
I have 3 old SCSI HDDs that were in a hardware RAID, I don't have the RAID controller anymore but I have imaged them with DD and a SCSI PCI card I have. Is there any way to assemble this array in software on Linux? I just want to get the data off so read only is fine. Running blkid on the drive shows it as an Adaptec RAID member. I believe the drives are in RAID 5. EDIT: I got it working, but I had to use windows. I installed ReclaiMe Free RAID Recovery to find the RAID parameters then used the UFS explorer Pro free trial to image the array to a virtual disk. After a quick (actual quite long) chkdsk I managed to mount the NTFS file system on the array EDIT2: There seem to be a lot of missing files, I don't think there was anything important on here anyway EDIT3: wow, the found.000 folder is huge. I guess the recovery failed, or the array got pretty badly corrupted on the ~10 years in storage.
I wonder what NOAA is doing? They did this on 2023-08-28 too.
github.com
I made a status page for the 137MHz weather satellites (like happysat's meteor one) Hopefully this is useful to someone, I think I went overboard on the details but maybe that's helpful [github link](https://github.com/thomasdouwes/137MHz-Weather-Satellite-Status) [self hosted forgejo link](https://forgejo.douwes.co.uk/thomas/137MHz-Weather-Satellite-Status)
The MIRP seems to be having trouble keeping channels in sync with the broken data, the sync pulses are different sizes on the black and white telemetry bars and breaking the software syncing. NOAA-APTs attempt at syncing: 
