• 1 Post
  • 53 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle






  • SteveTech@programming.devtoUnixporn@lemmy.mlI got a little distracted
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    Oh cool, I believe only 4bit colours are possible, you can use this table from Wikipedia and the escape sequence \e[<FG>m replacing<FG> with your chosen foreground colour. Also \e[0m to reset everything.

    funny how we use the same font XD

    Haha yeah! I noticed that too!

    I think I just used regex look aheads and look behinds to insert the colours easily.

    Edit: Oh you can change that actual TTY font to a bigger one, if the text is too small too.





  • IIRC the RTL chip inside them was originally designed for TV, so it works great! I’m actually using very cheap AliExpress clones for the TV ones, because they otherwise don’t work very well.

    I’m also using the outdoor TV antenna on my roof (common in Australia, idk elsewhere), and a splitter and adaptors. And with that I get every channel with no artifacts, at 30% strength, but that’ll probably be higher with not awful SDRs.


  • I’ve got an interesting setup I’d like to share:

    So I’ve got a Raspberry Pi with 4 RTL-SDRs, 2 for TV, 1 for radio, and 1 for plane transponders. That runs SatPi for the 2 TV SDRs, which TVHeadend running on my main server connects to, to record and stream. Jellyfin also connects to TVHeadend to properly index everything and for easy access to recordings and live TV.



  • Will I see any performance increase?

    Like others have said LLMs mostly use VRAM, they can use system RAM if you’re running them on CPU, but that’s ridiculously slow.

    It will however increase the speed of your compile times, which is especially useful if you’re compiling something large like the Linux kernel on a regular basis.

    I’m also worried about not having ECC RAM.

    If you are using it purely for LLMs, if it’s going to get bit flips, it’ll happen in VRAM.

    If you are compiling large things for customers, I’d recommend ECC, just in case, e.g. you don’t want a bricking firmware from a bit flip. But according to EDAC and my TIG stack, my server’s ECC RAM has never even detected an error in the past year, if I understand EDAC properly, so it’s really not important.



  • Is it possible to send the hint from OPNsense itself?

    Yes, to me it sounds like you’re already getting a big enough prefix from your ISP (all devices getting a /64), but you’ll have to request a bigger prefix from OPNsense. I believe it should give you the options to do this when you set the IPv6 mode to DHCPv6 on OPNsense, but I can’t say if your ISP router will handle it.




  • Idk, with I2C if it’s not something that needs a kernel level driver, there usually isn’t a problem with interacting with it from user space, for example basically all RAM RGB controllers are I2C and OpenRGB has no problem with them. I’m pretty sure I’ve only ever used an I2C device tree overlay for an RTC.

    Also I2C/SMBus is present everywhere on x86, like some graphics cards expose it through their HDMI ports, even some server motherboards have a header for it; but for GPIO I’m unaware of any motherboards that expose it, so good luck researching the chipset and tracing out the pins.