thomasdouwes 5 months ago • 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 5 months ago • 100%
dkms status doesn't even list half of my DKMS modules for some reason
thomasdouwes 5 months ago • 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 5 months ago • 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 5 months ago • 100%
hmm, maybe downgrading nvidia-dkms might work? I'll try that
thomasdouwes 5 months ago • 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 5 months ago • 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 5 months ago • 100%
It's an MSI GE72MVR 7RG, what do mean version?
and it's an integrated intel GPU.
thomasdouwes 5 months ago • 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 5 months ago • 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 5 months ago • 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 5 months ago • 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 5 months ago • 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 6 months ago • 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 6 months ago • 100%
640,000GHz is nice
thomasdouwes 7 months ago • 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 7 months ago • 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 7 months ago • 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 7 months ago • 100%
How do I even migrate??? I can't figure it out
thomasdouwes 7 months ago • 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.
thomasdouwes 7 months ago • 100%
The USB3 won't make a difference. It's actually a hardware issue with the rtl2832u in the SDR that causes the drop. I'm not sure why one controller is OK, but that's what I've heard.
I'll be honest that I don't really understand why oversampling helps. But as far as I know it only increases the dynamic range, and if you don't have a large difference between the weakest and strongest signals you are receiving there isn't any benefit. And also, yeah, the environmental noise is probably way higher that the ADC noise.
If you've been a ham for 9 years, you probably know more about this than me. I've been into radio/SDR for about 1.5 years now, and I've mostly just done satellite stuff in that time.
thomasdouwes 7 months ago • 100%
Yeah, I was going to suggest that if you had a second SDR
thomasdouwes 7 months ago • 100%
yeah, that might do it
thomasdouwes 7 months ago • 100%
Those look fine to me, maybe your USB controller is OK? Also might just not be visible. It is more apparent with digital signals like LRPT than APT. I would recommend switching to 2.4MHz sample rate though, nothing in the 137MHz band needs that much bandwidth, and the SNR gain of decimating from 3.2MHz won't make a difference in that band either.
I've not tried using a high samplerate with APT, but here is one with sample drops for a different reason:
They are the little mismatched lines in the middle, they are more obvious when you disable syncing:
thomasdouwes 7 months ago • 100%
137MHz is also quite close to the airband, sometimes nearby aircraft can cause overload
thomasdouwes 7 months ago • 100%
hmm, 152MHz seems quite a long way out from 137MHz to cause issues, but if it's very strong I guess that could the issue.
thomasdouwes 7 months ago • 100%
btw, unless you have a very specific USB controller, anything above 2.4MHz sample rate will drop samples and ruin the APT image.
I guess you already figured the pagers out the from the other comment, but you can find details on sigid wiki
thomasdouwes 7 months ago • 100%
What sample rate are you running here? There isn't much of the spectrum visible. it could be a powerful nearby signal overloading the SDR, but you need to see more spectrum to see it. I know there is a very strong testing pager near me that often causes this same dip on the RTL
thomasdouwes 8 months ago • 100%
This post is 4 months old, the AVHRR has mostly recovered since
thomasdouwes 8 months ago • 100%
I was testing a custom initramfs that would load a full root into a ramdisk, and when I was going to shut down I tried to run rm -rf --no-preserve-root /
to see what would happen, since I was on a ramdisk anyway. The computer would not boot after that because it nuked the UEFI options.
thomasdouwes 10 months ago • 100%
Computer plays video games
I want to make video games
Learn to program
Never even make video games
thomasdouwes 11 months ago • 50%
wtf happened to south america lol
thomasdouwes 11 months ago • 100%
The passes are currently very late at night here, around 4am, so I had to receive it automatically :(
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: ![](https://sopuli.xyz/pictrs/image/b47a2f4f-4ab2-40b5-ab51-84feb9cabdc5.png) ![](https://sopuli.xyz/pictrs/image/ab77dc62-146a-4e21-873d-e7a3ada69337.png)
thomasdouwes 11 months ago • 100%
Granted, now all computers run Linux. For a year. Then every computer switches back to windows, including all servers.
thomasdouwes 11 months ago • 100%
Usually they just don't start spinning, some of the NOAA ones have been going for 25 years and haven't ever lost orientation.
The satellite in this post is a russian one, they don't have an analog transmission anymore, this image is from digital transmission near the frequency of the NOAA analog one, so still easy enough to recieve.
But as for the analog NOAA transmission, There really isn't any reason to shut down the analog transmission, the satellite was built with enough power to run it, so shutting it down would just lead to a surpus of power on satellite. I don't think the design would even allow pushing more power on the digital signal.
NOAA will have some huge tracked dishes for this to get a perfect image even with the lowish power level.
Also, the satellites with analog are not the main ones anymore. NOAA has some new satellites with much higher resolution imagery that are not nearly as easy to receive as these older ones. they only broadcast at 8GHz instead of the 1.7GHz or 137MHz that the current ones do
thomasdouwes 11 months ago • 100%
oh, haha. You are probably thinking of @user224@lemmy.sdf.org saying they are in slovakia in this post, not me. I live in the UK.
This satellite is actually from 2023, I think having one light cell allows for higher resolution and multiple channels. This satellite also has 3 thermal infrared channels that are calibrated so you can see the exact temperature at each pixel, I don't think that would be possible with a traditional camera system.
thomasdouwes 11 months ago • 100%
I don't speak slovak, but I'll try to respond:
The satellite transmits constantly, so you are only limited by the time it is above the horizon. The duration of this transmission was about 15 minutes, but the signal was only strong enough for a much shorter time. I can't remember exactly how long this one was, it was a while ago.
These russian satellites seem to have a lot of problems with orientation. This is the first and only time so far this satellite has had issues, but the other ones have had a lot of issues before. When it is spinning it usually does send images of space, but I've not seen any where it's only space before.
Yes, The sensor is sensitive and would be damaged by the sun. One of the old satellites started spinning and the sun burned out the imager.
preložené:
Dúfajme, že to prekladateľ príliš nepokazil.
Ja síce po slovensky neviem, ale pokúsim sa odpovedať:
Družica vysiela nepretržite, takže ste obmedzený len časom, keď je nad horizontom. Dĺžka tohto vysielania bola asi 15 minút, ale signál bol dostatočne silný len oveľa kratší čas. Nepamätám si presne, aký dlhý bol tento, bolo to už dávno.
Zdá sa, že tieto ruské satelity majú veľa problémov s orientáciou. Toto je prvý a zatiaľ jediný prípad, keď mal tento satelit problémy, ale ostatné mali veľa problémov už predtým. Keď sa otáča, zvyčajne posiela snímky vesmíru, ale predtým som nevidel žiadne, kde by bol len vesmír.
Áno, snímač je citlivý a poškodilo by ho slnko. Jeden zo starých satelitov sa začal otáčať a slnko vypálilo snímač.
thomasdouwes 11 months ago • 100%
The satellite has a malfunction. The imager scans the planet one line at a time and the motor that scans it is stuck, and causing the motor to spin too slow. I'm not sure on the specifics, but the onboard computer ends up sending broken data, resulting in the artefacts in this image and the analog version.
The analog transmission is there for compatibility with old ground stations. It's much easier to receive, so cheap ground stations can be set up in places that don't have the money for a dish and rotor setup. The last satellite with the analog transmission was launched in 2009, all US satellites since have been only digital, and even removed the HRPT and replaced it with a much higher rate, harder to recive downlink.
Russian satellites have a digital signal at the same lower frequency instead of the analog signal for the same reason, but it looks much better because it is digital.
The image is the data as it was sent by the satellite, the vertical lines are probably coming from the satellite computer getting confused by the stuck scan motor.
thomasdouwes 11 months ago • 100%
The satellite is sending the sync pulse for the second channel twice in that middle bit, so the software fails to sync.
The scan motor current for this satellite is on this page under Telemetry/Scan Motor Current
There is a small digital signal (DSB) near this downlink that has some other sensors and telemetry.
There is also another digital signal (HRPT) at a much higher frequency (1.7GHz) that has all the sensors and also the raw data for this image. It requires a dish and tracking, but this satellite has a broken transmitter for that higher frequency, so it's much weaker. The artefacts look completely different in the raw digital image.
An image from this sat on HRPT:
thomasdouwes 11 months ago • 100%
and satdump for decoding
From 2023-10-12 Projected: ![](https://i3b.co/6352A68CAB10B439BC1A2E2AF44C1F1E.png) Day Microphysics projected: ![](https://i3b.co/937CE46E16291809CDF187A7C612AD69.png)
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 ![](https://i3b.co/9459A0B2FD498E223A29816E378A375E.png) official NOAA data: ![](https://www.star.nesdis.noaa.gov/data/smcd1/icvs_metrics/status/N15/AVHRR//2023/09/20230915_noaa15_motorcurrent_since_launch.png) 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.
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: ![](https://i3b.co/B942245C491F5BAF48AF7EDE49DAC637.png)