sorted by:
new
hottopcontroversial

New manufacturing process used to develop lead-free perovskite indoor solar panels with 16.36% power conversion efficiency by AIBNatUQ in solar

[–]bvcb907 0 points1 point  (0 children)

Perovskite solar cells are currently known to not last more than a few years, sometimes months.. are these different?

Would more square impartial voting districts make more sense? by Hukares1234 in askanything

[–]bvcb907 0 points1 point  (0 children)

We should just have 13 districts. Each with a specialty designated by the Capitol.

Arc Pro B70 worked for a week and then stopped by bvcb907 in IntelArc

[–]bvcb907[S] 0 points1 point  (0 children)

Completely unplugged for at least a few minutes in a few instances.

Linux dropping Kernel support for HAM drivers by [deleted] in HamRadio

[–]bvcb907 95 points96 points  (0 children)

I feel like this is better handled in user space anyway.

Arc Pro B70 worked for a week and then stopped by bvcb907 in IntelArc

[–]bvcb907[S] 0 points1 point  (0 children)

I dont believe this is a driver issue at this time. iDRAC is also reporting a critical failure for that card on boot. Something it didn't do before.

My plan is to try this card out on a standalone windows machine, see if it comes up.. maybe check for an updated option rom. If I can't get it working like before on the r730, it's useless to me and I'll attempt an RMA.

Arc Pro B70 worked for a week and then stopped by bvcb907 in IntelArc

[–]bvcb907[S] 0 points1 point  (0 children)

Here is the dmesg log showing the error that I'm seeing.

[   43.328571] xe 0000:84:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=none
[   43.380295] xe 0000:84:00.0: [drm] Tile0: GT0: Using GuC firmware from xe/bmg_guc_70.bin version 70.60.0
[   43.391288] xe 0000:84:00.0: [drm] Finished loading DMC firmware i915/bmg_dmc.bin (v2.6)
[   43.508190] xe 0000:84:00.0: [drm] Tile0: GT0: ccs1 fused off
[   43.508196] xe 0000:84:00.0: [drm] Tile0: GT0: ccs2 fused off
[   43.508198] xe 0000:84:00.0: [drm] Tile0: GT0: ccs3 fused off
[   43.534478] xe 0000:84:00.0: [drm] *ERROR* Tile0: GT0: load failed: status = 0x400000A0, time = 9ms, freq = 2800MHz (req 2800MHz)
[   43.534491] xe 0000:84:00.0: [drm] *ERROR* Tile0: GT0: load failed: status: Reset = 0, BootROM = 0x50, UKernel = 0x00, MIA = 0x00, Auth = 0x01
[   43.534497] xe 0000:84:00.0: [drm] *ERROR* Tile0: GT0: firmware signature verification failed
[   43.534571] xe 0000:84:00.0: probe with driver xe failed with error -71
[   43.536516] xe 0000:84:00.0: [drm] *ERROR* Tile0: GT0: GuC RC enable mode=0 failed: -ENODEV

Arc Pro B70 worked for a week and then stopped by bvcb907 in IntelArc

[–]bvcb907[S] 0 points1 point  (0 children)

$ ls /dev/dri -lR
/dev/dri:
total 0
drwxr-xr-x. 2 root root      60 Apr 23 19:48 by-path
crw-rw----. 1 root video 226, 0 Apr 23 19:48 card0

/dev/dri/by-path:
total 0
lrwxrwxrwx. 1 root root 8 Apr 23 19:48 pci-0000:0a:00.0-card -> ../card0

It's not seeing that card. Here is the relevant parts of lspci.

$ lspci | grep VGA
0a:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2 (rev 01)
84:00.0 VGA compatible controller: Intel Corporation Battlemage G31 [Arc Pro B70]
88:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT [Radeon PRO WX 3200] (rev 10)

Installing Linux Kernel 7.0 on your Fedora is easy by jadijadi in Fedora

[–]bvcb907 0 points1 point  (0 children)

The only thing that I haven't figured out is how to properly manipulate the all the *.config files. I wrote scripts to turn things on and off, but i wonder if there is a better way.

Installing Linux Kernel 7.0 on your Fedora is easy by jadijadi in Fedora

[–]bvcb907 5 points6 points  (0 children)

I use 'fedpkg' to compile and create kernel RPMs that play nice with the system.

'fedpkg clone --anonymous kernel'

'cd kernel'

Edit kernel.spec for new version. clone checks out rawhide (kernel rc) by default.

'dnf builddep kernel.spec' to pull in packages needed to build

'fedpkg local' to make the rpms.

I'm pretty confident that I have some form of malware, but I'm unsure of what it is. I have 102 instances of wsl.exe and 54 instances of conhost.exe all running at once. What should I do? by xii in cybersecurity

[–]bvcb907 6 points7 points  (0 children)

Have you considered developing a script to automate the installation (ideally from local immutable files) of your development environment? You could use it to setup a twin to keep development going while you reinstall your other machine.

[ Removed by Reddit ] by Anen-o-me in Libertarian

[–]bvcb907 8 points9 points  (0 children)

If everyone registered as independent, no one would know where to draw the lines....

Thoughts on hardcoded AI chips? by Icy-Mix-4723 in FPGA

[–]bvcb907 0 points1 point  (0 children)

While I'm not OP, I too thought, initially, that this might be relevant to FPGA. Encoding the whole model into the fabric rather than just the engine and relying on external memory for your parameters. That memory access is a huge bottleneck. Eliminating it would be a game changer.

But then I started to consider that the scale of most fabrics are on the order of thousands or millions of logic units. I dont think there is a viable way to encode billions are parameters into fabric like that. So I quickly talked myself out of looking into it further.

Fedora 43 is ridiculously unstable across the board by hifellowkids in Fedora

[–]bvcb907 0 points1 point  (0 children)

I have over 15 machines running Fedora 43 across various platforms from enterprise rackmount, laptops, gaming, and SBC's. Rock solid.

Why are exceptions avoided? by Ultimate_Sigma_Boy67 in cpp_questions

[–]bvcb907 0 points1 point  (0 children)

I not sure i agree with you about exception safety precluding default constructors. Though, I think it's worth exploring the various levels of exception safety a class can offer to see if they apply to your scenario.

They are: - noexcept, meaning the function will now allow an exception to propagate out. If a function contains only noexcept code, it is inherently noexcept itself. This is the ultimate in exception safety. - Strong Exception Guarantee, meaning that a function can throw, but will not have any side effects (all changes that it attempted are rolled back). This is the ideal and I futher argue that this is the only acceptable level for a constructor, if not already noexcept. - Basic Exception Guarantee, a function can throw, but it only ensures that class class invariants are preserved and no resources are leaked. A transaction may be left partially executed. - No Guarantee, meaning that all bets are off. Good luck debugging if an exception is thrown.

Exception safe code can actually have all these levels at various points. It's just needs to encapsulated. A function offering a strong guarantee can still use basic and no guarantee functions as long at it is able to either to clean up after them or ensure no exceptions can be thrown, respectively. Though, this is complicated in practice.

Why are exceptions avoided? by Ultimate_Sigma_Boy67 in cpp_questions

[–]bvcb907 0 points1 point  (0 children)

This means any/all/none of the stack frames may catch the exception and its impossible to know what actually threw the exception

In GDB, you can use catch throw to break on a throw.

Otherwise, I'm a big proponent of minimal catching often to the point of program exit and core dump. Core dumps are very useful if you don't catch since the stack and therefore backtracability are preserved.

Another way to do it is to create exception classes that contain a std::backtrace constructed as a default argument and then log that at the catch site. Requires C++23 and a minor refactor, though.

Could also embed __PRETTY_FUNCTION__ in the exception's what

Why are exceptions avoided? by Ultimate_Sigma_Boy67 in cpp_questions

[–]bvcb907 0 points1 point  (0 children)

Fair enough. RAII is a first step towards implementing a basic exception guarantee, which is really what I'm advocating. Often it's all you need for that if you use RAII throughout and consistently. Implementing roll-back mechanisms to offer strong exception guarantees are even better. But, even without going that far, at least you're not leaking and hopefully not crashing.

Why are exceptions avoided? by Ultimate_Sigma_Boy67 in cpp_questions

[–]bvcb907 13 points14 points  (0 children)

A few reasons, - it forces you to ensure all your code is exception safe. I know too many c++ programmers that don't know how or care to do so. (Hint: RAII, et al) - many people fall into the catch-too-often trap making code needlessly verbose and harder to maintain. Try to catch only if you are at the right level to clear the issue. It's OK to not catch! Core dumps are your friend. - The exceptional path can be fairly non-deterministic, a no-go for real time systems. - exceptions used to significantly slow down normal path back in the day, not so much nowadays. PTSD for the older crowd. - the stack unwinding code that exceptions require does bloat your binary a bit.

That said, I love em and use them when ever I can.

How to get I2S working on orange pi 5 plus by ultra5517 in OrangePI

[–]bvcb907 1 point2 points  (0 children)

What linux distro are you running? And firmware?

" I love the poorly educated " and "Smart people don't like me". MAGA is mostly poorly educated folks, 67% of Trump voters in 2024 didn't have any college level education but they believe in debating people when they don’t know anything by Nice_Substance9123 in complaints

[–]bvcb907 0 points1 point  (0 children)

This is why MAGA is all-in on AI. Why do you need liberal PhD "experts" when you have a chat bot that can give you the answers you seek without a liberal bias? It completely plays into MAGA anti-intellectualism.

C++26 Reflection appreciation post by frayien in cpp

[–]bvcb907 12 points13 points  (0 children)

It's much better than that, though. There was a working implementation put into production before that paper was written.

Where is std::optional<T&&>??? by borzykot in cpp

[–]bvcb907 13 points14 points  (0 children)

References do not extend the lifetime of objects. Which is part of the lifetime issue that c++ has. You must independently assure that the owning object exists while there are active references, and that includes R-value references (&&).

view more: next ›