All Activity

Honestly, I think it's more interesting as an example of its kind. If it has an x86 CPU, it's a very slow one (like a 450 mhz AMD Geode or maybe a 1 ghz VIA C7 if you're lucky), paired to a tiny amount of RAM and storage. You can shoehorn XP onto it, but I highly doubt anything newer would be remotely usable. https://wiki.laptop.org/go/Windows https://www.zdnet.com/article/microsoft-finalizes-windows-xp-for-olpc-laptops-6023001504/

Good morning, Does anybody know how to tell the different between a Dell Wyse 3040 and the PCoIP version of the same product without an OS installed or a remote connection. We have recently bought a bunch of these and as far as I can tell, there are no indicators whether they have this feature / function or not. Thanks, Sparks

RGB ram modules do not require any additional cable or connector. The RGB is managed through the DIMM slot. If you're not familiar with RGB yet, you might end up in "RGB hell" with all the different vendors requiring to use their (buggy) RGB control app. Or you might feel like you are trapped with one vendor (looking at you Corsair) to keep things easily manageable. OpenRGB is a great free alternative to manage all your RGB from one app (and for free). They use plugins to extend the features of the core app and they have a great supportive community. It may be a bit of a learning curve at the beginning (I'd say 1st 24-48h) but after you get the basics it all makes sense. Best, -a-

I thin zeroteir may be based on the wireguard vpn, but not 100%. You do not need knowledge of docker to use zerotier. You setup an account in zerotier. Then setup 'network' in zeroteir through the website. Download the zerotier software and connect to the 'network' In linux it is just a few simple command lines. Then in the zerotier website, approve the connections. The client (windows, mac, phone linux, IOS) are assigned IP addresses in the network. I have not used tailscale, but expect it to be similar.

Hi, so I've been running a Debian Server at home since 2022. It was running stable until 4 months ago. Since then it crashes once or even twice a week. I mean it really crashes hard to the point it has to reboot itself. The logs don't show anything. Memtest came back with no errors, so the RAM seems fine. I am going to switch out the powersupply next. Here some specs about the server: Mainboard: MSI H510I PRO WIFI Mainboard Mini-ITX CPU: Intel Core i5-11600 RAM 64GB: Mushkin Wave - D464GB 2800-17 Redline FB G3 K2 MSK PSU: Seasonic Prime Fanless PX-500 HDD: 2 x Toshiba MG09ACA18TE SSD: Samsung SSD 980 PRO 1TB NIC: MellanoxConnectX-3 Cooling (CPU): be quiet! Dark Rock TopFlow 2 BK031 Fans: 4 x Noctua (2x 80mm + 2x140mm) In my next attempt to narrow down the cause I will install a new PSU: Seasonic Prime 650W Ultra 80 Plus Titanium Full Modular On my server I am running some apllications as well all in docker containers: Jellyfin AMP (for game servers) Nginx-Proxy-Manager There is also a cronjob running every minute to update my DNS-Entry in case my IP changes since I don't have a fixed IP address. If you need further information, logs or else please just ask. Syslog from the latest crash: 2024-04-24T09:59:03.256792+02:00 jensi5server systemd[1]: Starting amptasks.service - AMP Instance Manager Pending Tasks... 2024-04-24T09:59:03.329635+02:00 jensi5server ampinstmgr[224751]: [Info] AMP Instance Manager v2.5.0.6 built 17/04/2024 22:10 2024-04-24T09:59:03.337685+02:00 jensi5server ampinstmgr[224751]: [Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV 2024-04-24T09:59:03.641161+02:00 jensi5server systemd[1]: amptasks.service: Deactivated successfully. 2024-04-24T09:59:03.641294+02:00 jensi5server systemd[1]: Finished amptasks.service - AMP Instance Manager Pending Tasks. 2024-04-24T10:00:04.772521+02:00 jensi5server systemd-modules-load[373]: Inserted module 'coretemp' 2024-04-24T10:00:04.772593+02:00 jensi5server kernel: [ 0.000000] Linux version 6.1.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Deb> 2024-04-24T10:00:04.772608+02:00 jensi5server kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-20-amd64 root=/dev/mapper/system-root ro quiet crashkernel=256M crashkernel=384M> 2024-04-24T10:00:04.772609+02:00 jensi5server kernel: [ 0.000000] BIOS-provided physical RAM map: 2024-04-24T10:00:04.772597+02:00 jensi5server systemd[1]: modprobe@drm.service: Deactivated successfully. 2024-04-24T10:00:04.772609+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable 2024-04-24T10:00:04.772616+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved 2024-04-24T10:00:04.772616+02:00 jensi5server systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. Here the kern.log: 2024-04-24T10:00:04.772593+02:00 jensi5server kernel: [ 0.000000] Linux version 6.1.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Deb> 2024-04-24T10:00:04.772608+02:00 jensi5server kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.1.0-20-amd64 root=/dev/mapper/system-root ro quiet crashkernel=256M crashkernel=384M> 2024-04-24T10:00:04.772609+02:00 jensi5server kernel: [ 0.000000] BIOS-provided physical RAM map: 2024-04-24T10:00:04.772609+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable 2024-04-24T10:00:04.772616+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x000000000009efff] reserved 2024-04-24T10:00:04.772617+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] usable 2024-04-24T10:00:04.772620+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved 2024-04-24T10:00:04.772623+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000849fefff] usable 2024-04-24T10:00:04.772623+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000849ff000-0x0000000084ffefff] reserved 2024-04-24T10:00:04.772624+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x0000000084fff000-0x00000000850fefff] ACPI data 2024-04-24T10:00:04.772625+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000850ff000-0x00000000852fefff] ACPI NVS 2024-04-24T10:00:04.772626+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000852ff000-0x0000000085efefff] reserved 2024-04-24T10:00:04.772627+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x0000000085eff000-0x0000000085ffefff] type 20 2024-04-24T10:00:04.772629+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x0000000085fff000-0x0000000085ffffff] usable 2024-04-24T10:00:04.772631+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x0000000086000000-0x0000000089ffffff] reserved 2024-04-24T10:00:04.772632+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x000000008a600000-0x000000008a7fffff] reserved 2024-04-24T10:00:04.772633+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x000000008b000000-0x00000000907fffff] reserved 2024-04-24T10:00:04.772633+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved 2024-04-24T10:00:04.772634+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved 2024-04-24T10:00:04.772634+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved 2024-04-24T10:00:04.772636+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved 2024-04-24T10:00:04.772637+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved 2024-04-24T10:00:04.772638+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved 2024-04-24T10:00:04.772638+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved 2024-04-24T10:00:04.772639+02:00 jensi5server kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000106f7fffff] usable 2024-04-24T10:00:04.772639+02:00 jensi5server kernel: [ 0.000000] NX (Execute Disable) protection: active 2024-04-24T10:00:04.772641+02:00 jensi5server kernel: [ 0.000000] efi: EFI v2.70 by American Megatrends 2024-04-24T10:00:04.772642+02:00 jensi5server kernel: [ 0.000000] efi: ACPI=0x85269000 ACPI 2.0=0x85269014 TPMFinalLog=0x8526c000 SMBIOS=0x85d1d000 SMBIOS 3.0=0x85d1c000 MEMATTR=0x7f26a198 ES> 2024-04-24T10:00:04.772643+02:00 jensi5server kernel: [ 0.000000] secureboot: Secure boot disabled 2024-04-24T10:00:04.772643+02:00 jensi5server kernel: [ 0.000000] SMBIOS 3.3.0 present. 2024-04-24T10:00:04.772644+02:00 jensi5server kernel: [ 0.000000] DMI: Micro-Star International Co., Ltd. MS-7D16/H510I PRO WIFI (MS-7D16), BIOS 1.30 09/09/2021 2024-04-24T10:00:04.772644+02:00 jensi5server kernel: [ 0.000000] tsc: Detected 2800.000 MHz processor 2024-04-24T10:00:04.772646+02:00 jensi5server kernel: [ 0.000000] tsc: Detected 2808.000 MHz TSC 2024-04-24T10:00:04.772647+02:00 jensi5server kernel: [ 0.000615] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved 2024-04-24T10:00:04.772648+02:00 jensi5server kernel: [ 0.000618] e820: remove [mem 0x000a0000-0x000fffff] usable 2024-04-24T10:00:04.772648+02:00 jensi5server kernel: [ 0.000629] last_pfn = 0x106f800 max_arch_pfn = 0x400000000 2024-04-24T10:00:04.772648+02:00 jensi5server kernel: [ 0.000781] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT 2024-04-24T10:00:04.772649+02:00 jensi5server kernel: [ 0.001497] last_pfn = 0x86000 max_arch_pfn = 0x400000000 2024-04-24T10:00:04.772649+02:00 jensi5server kernel: [ 0.020600] esrt: Reserving ESRT space from 0x000000008009a418 to 0x000000008009a450. 2024-04-24T10:00:04.772653+02:00 jensi5server kernel: [ 0.020605] e820: update [mem 0x8009a000-0x8009afff] usable ==> reserved 2024-04-24T10:00:04.772653+02:00 jensi5server kernel: [ 0.020629] Using GB pages for direct mapping 2024-04-24T10:00:04.772654+02:00 jensi5server kernel: [ 0.020965] RAMDISK: [mem 0x34057000-0x36022fff] 2024-04-24T10:00:04.772654+02:00 jensi5server kernel: [ 0.020968] ACPI: Early table checksum verification disabled

I’m looking to create a new Home Theatre for myself. Plan is to have a best native 4K Projector with best surround sound system. I was thinking of having the Epson LS12000 or LS11000 combined with the new Bravia Theatre quad and Apple TV 4K, not sure even if I should have the av receiver or which one if any? or Epson LS800 with Bravia theatre quad to avoid having complex setup, where there is no need for an av receiver and streaming is possible directly within the projector. please suggest if there’s any other combination that works.

Nixos for single file configuration. batoceraOS for all retro Games. Bazzite for gaming also included container distrobox Both would work really well.

Oof you're bios is confused where the efi is, you can attempt to manual boot by selecting boot file and see if you can boot that way. Once done then do sfc /scannow it probably will fix it. Otherwise use some rescue and repair bootloader.

Now for the real question, will Hoyoverse ban my account if I use this? They aren't so keen on people modding their games, last time I checked... Off topic, but there is a trick I accidentally found to get >60fps in their other game Honkai Star Rail. First set vertical sync to "On" in NVIDIA Control Panel / AMD Adrenalin, then set Vsync to "On" in the in-game settings (both must be on). Then see your FPS shoot up to whatever your display's max refresh rate is. Shame this trick doesn't work in GI though...

Have you checked in advanced sharing and on button permissions? Have you tried to add that account like PCNAME\NAME to your share permissions? Try make new folder call it "share" or "disk" And try again? You're using account of the pc you share to log in? Like prompt coming up? It's unusual to use same account to connect drive. Most people use different account usually it works that way. At least that's what i think. But is it really same account? Technical wise.

I'd probably recommend avoiding Vengeance kits, not because they're bad or anything, but because they tend to be kinda expensive compared to the competition for effectively the exact same RAM. As for the two free slots, just know that you'll only want to use them in very specific circumstances as they dramatically reduce the max memory speed. It will definitely be measurably worse, but not that noticeably worse. I'd still try to avoid the 5600MT/s rated kits though, since with 2x48GB at least the compatibility of them is kinda spotty. It's worse on AMD than it is on Intel, but they're still not great, and in the grand scheme of a system budget a 6400Mt/s kit isn't that much more than a 5600MT/s rated kit. I would personally get one of these two kits depending on if you want 64GB or 96GB: https://pcpartpicker.com/product/xJV2FT/oloy-blade-rgb-64-gb-2-x-32-gb-ddr5-6400-cl32-memory-nd5u3264320irkde https://pcpartpicker.com/product/xDcgXL/gskill-trident-z-rgb-96-gb-2-x-48-gb-ddr5-6400-cl32-memory-f5-6400j3239f48gx2-tz5rk There will be RGB software with the motherboard that allows you to control the RAM. That or if you go the Corsair route, use iCUE for the software. Also quote so we get a notification, I just happened to come back here.

Most likely the cable, unlikely the monitor or GPU.

These are all terrible deals. Like these are 100$ and less ebay laptops. https://www.ebay.com/itm/355641275875?itmmeta=01HW7JEM6KQHMZTTAMD19C4G3Q&hash=item52cddf35e3:g:qTEAAOSw7wRmHrBN&itmprp=enc%3AAQAJAAAAwD3PR8RRS%2Fl4FV9qA0%2FODVk1Gk4R8urSrV822DJReADsqdWIQX2A%2FHUe2PdqXJ5hNyZKCeyJdvo9JztKEyHOT1XLJBR878QbgifJTM54JYiB6MDVhNTEg%2BUuLzXDYeAm%2BqyVoMXuJxnygDshTV5viV%2FIgCp4Z%2BeDOvNZ2RxbiV50B7fAdVF%2BJCETIME4p9hwPgzGxAEdqC%2FN2Rj%2BkGrdcHY5AfP1MtImqJksJ7Lz9Ob1af2k%2F1uZpwY33ur2nlj3nQ%3D%3D|tkp%3ABk9SR87DuvLhYw All of 2 seconds on ebat and this laptop is SO much better its not even funny.

Sorry but i think majority people don't think they are humans.

Try to find a different DP cable to try first

Best lyrics ever in the history of metal

@ianm_ozzy It looks like using ZeroTier on DSM7 requires Docker CLI. Although I heard of Docker and I believe I have a vague idea of its concept, I am not at all familiar with it. I will thus keep this option as a "plan B". Thank you for suggestion, though.

Hello everyone Foreword: I consider myself a fairly "advanced" user (I learned over the years) but I'm not deeply familiar with technicalities related to either networking nor backup/synchronization or whatever. I have no training in informatics. I'm mostly "self" taught thanks to the many of you on the internet who patiently and kindly shared their knowledge and expertise (and I am very thankful to each of you). For many around me, I'm the person people go to when they have an issue with their computer. Imposter Syndrome for sure... I started using Synology years ago since I was comfortable with DSM and its GUI. I'm not super comfortable with CLI although I use it occasionally (usually when I have no other option, pardon my weakness). I'm not super familiar with TailScale. I don't fully understand how it works. for instance, I don't know what "Tailnet", "route" or "exit node" mean but it seemed to me like this was not necessary for what I was trying to achieve. Question: I experience a weird issue when trying to use TailScale between Synology devices. First let me explain the details of the setup. I have 5 Synology NASes, 4 at home and 1 at work. Let's identify them with letters: A) is my main NAS at home. It hosts all my files B) is my secondary NAS at home. It hosts mostly media files that I could re-download in case of an unrecoverable loss C) is my backup NAS at home. It hosts backup of A) and some of the content of B) D) is a smaller spare NAS at home. I use it mostly for tests/experiments E) is my backup NAS at work. It hosts backups of A) and some of the content of B), or at least it's what it is supposed to. I setup all the backup tasks using Synology Hyper Backup. all my NASes run DSM7 (7.1 or 7.2) and the current version of TailScale. The NAS at work is behind a firewall (or other network security solutions) that I have zero control over. At some point I could no longer connect from the outside in an easy way (we no longer had "public IPs" AFAIU). Therefore I started to use TailScale to be able to backup A) and some of the content of B) onto E). I installed TailScale on A), B) and E) and they all appear as connected on my TailScale admin console. I also installed TailScale on my laptop so that I can connect to DSM on E) and manage it from home. I setup weekly backups (A) + B) -> E) ) and everything worked fine for 5 weeks. After that A) could no longer reach E) although B) still could. Weird... In order to troubleshoot this (is the issue coming from A)?) I decided to install TailScale on C) and D) and see if they could reach E). They couldn't. Both C) and D) do appear as connected on TailScale's admin console. B) has no problem performing backup on E) thanks to TailScale, and this has been going on for over a year now. I don't understand why A) (C) or D) ) cannot do the same though. My laptop at home has no problem connecting to E) over HTTPS thanks to TailScale. I don't know how I could figure out the origin of the problem. I'd be very thankful if you would share any advice with me. Considering my limitations I will probably have to Google parts of your replies in order to figure out what you mean. (I understand that some would rather recommend to completely move away from Synology and use CLI based tools or different OSes. I'm not sure I feel ready for that ATM. I'm not familiar with Docker containers either.) Thank you very much in advance for your help. Best, -a-

Didn't expect to start such a debate Going to switch over to the 13700k based on the comments. Thoughts about considering the 13900k and if the extra $150 is worth it? I read something recently about a bunch of 13th and I think 14th gen chips failing so that made me a little wary of those for a while. I am a bit of an Intel fanboy (my current system is an AMD though) and I think they're back to making decent stuff again. I'm not all that concerned about upgradeability. I tend to stick with my builds for long enough that its' pretty out of date before I just build another one. I'll upgrade GPUs along the way. This will be my first windowed PC build (I've been building PCs for over 20 years) with the Corsair P2000 and I'm planning on the MSI B760 Project Zero. I'm digging the BTF stuff and will have some LED fans too. GPU will be an RTX 4070, probably the Tuf version since I read they the quietest relatively speaking. After looking at mobo prices some more I think I'm gonna go the DDR5 route. I did find Corsair Vengeance that I'm thinking I start with at 64 GB (which is still a ton) and I'll have two free slots to throw some more in if I need it. I also saw a 5600mhz variant in a 2x48 GB kit. Is the performance going to be that noticeable compared to the other one I linked running at 6400mhz? How does the RGB operate on this RAM? Like is it all through the motherboard or do I have to plug something into the RAM to control it?

Evaluations are not free for a reason. You're making them show up at your house to check the work that needs to be done. Travel time and time at your place, is time they can't work on a job at another customer's house. Them taking the cost of the evaluation off the total cost of the job is perfectly normal to do as that time would then be included in the time needed to complete the job. If you want a "free quote", it usually involves them not showing up, a 5 minutes phone call and would simply be an estimate based on other jobs they've done.

Online marketplaces like amazon tend to be able to pricematch and correct on the fly. So just buy one online and then get a phone plan for it.

All Open-Source PC. To see if you can survive with only free stuff (linux, firefox, libreoffice) and to recommend best open source software.

I tried reseating the card and still no chance. Could you send me that MSI tool? I looked a bit online and I found a few different articles and tools but I'm unsure as to which way to go.