shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

254
active users

#probook

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@cesarpose" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>cesarpose</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mrmasterkeyboard</span></a></span> depends on the model and <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hp</span></a> has something more sinister:</p><ul><li>In many <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProBook</span></a>|s they literally do a <em>"soft" <a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VendorLock</span></a></em> re <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a>, so if the stick's ain't hp-branded (as per SPD-EEPROM) the <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a> will brick <a href="https://infosec.space/tags/UnattendedBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnattendedBoot</span></a>, <a href="https://infosec.space/tags/UnattendedReboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnattendedReboot</span></a> &amp; <a href="https://infosec.space/tags/PXEboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PXEboot</span></a> by popping up an error message every boot that needs to be dismissed by hitting F1 on the internal keyboard (!!!) and can't be dismissed permanently.</li></ul><p>I literally had this with a client in the past and it's the reason a <a href="https://infosec.space/tags/refurbisher" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>refurbisher</span></a> I know didn't offer RAM-<a href="https://infosec.space/tags/Upgrades" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Upgrades</span></a> for HP machines <em>at all</em>…</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://trees.social/@posiputt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>posiputt</span></a></span> ja, bei den meisten Consumer-Geräten reicht es die CMOS-Batterie (!!!) rauszunehmen, ne Minute zu warten, dann nur mit Netzstrom neustarten und dann neue CMOS-Batterie rein!</p><ul><li>Business-Geräte wie <a href="https://infosec.space/tags/ThinkPad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinkPad</span></a>, <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProBook</span></a>, <a href="https://infosec.space/tags/Latitude" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Latitude</span></a>, etc. dagegen speichern das in nem verdchlüsselten Flash.</li></ul><p>Wenn das nicht hilft ggf. nen BIOS-Update auf CD/USB/FDD anbieten oder nach nem <em>"CLR CMOS"</em> pin-set aufm mainboard suchen....</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://corteximplant.com/@Sirs0ri" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>Sirs0ri</span></a></span> np.</p><p>I can recommend the <em>"upcycling"</em> &amp; <em>"reuse"</em> route given <a href="https://infosec.space/tags/ThinClients" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinClients</span></a> offer decent performance for a mini server and more often than not are completely fanless, making them excellent at home.</p><ul><li>I do use an <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hp</span></a> t620 for that myself, and unlike the <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProBook</span></a>|s it seems hp didn't do <a href="https://infosec.space/tags/DRM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DRM</span></a> with the <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a> on their <a href="https://infosec.space/tags/ThinClient" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinClient</span></a>|s... </li></ul><p>It's not that I don't say any other brand is bad, but those brands have been reliable to me and are known to use reliable &amp; new components and not new-old-stock or "upcycled" chips ripped from older machines and sticks.</p><ul><li>And since you ain't looking for some <em>"vintage"</em> SD-RAM there's no need to dive into those.</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@simonzerafa" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>simonzerafa</span></a></span> this is common with <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hp</span></a> devices.</p><p>They literally <a href="https://infosec.space/tags/brick" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>brick</span></a> <a href="https://infosec.space/tags/PXEboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PXEboot</span></a> on <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProBook</span></a>|s when you have any non-hp - branded <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a> sticks installed.</p><ul><li>You'll literally have to confirm you want to boot by pressing F1 on the <em>internal keyboard</em> EVERY SINGLE TIME it (re-)boots...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://limepeeps.perchinup.top/@radmin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>radmin</span></a></span> <span class="h-card" translate="no"><a href="https://wetdry.world/@tera" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tera</span></a></span> <span class="h-card" translate="no"><a href="https://wetdry.world/@critakitty" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>critakitty</span></a></span> yeah, <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> refusing to make a <a href="https://infosec.space/tags/TrackPoint" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TrackPoint</span></a> keyboard is kinda sad.</p><ul><li>Cuz it's not as if they can't make a call at <a href="https://infosec.space/tags/Sprintek" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sprintek</span></a> and maybe even get a custom-coloured rubber cap just to avoid <a href="https://infosec.space/tags/Lenovo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lenovo</span></a> claiming they violate the <a href="https://infosec.space/tags/UltraNav" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UltraNav</span></a> design / trademark.</li></ul><p>Not to mention this isn't unique to even <a href="https://infosec.space/tags/ThinkPad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinkPad</span></a> or <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hp</span></a> <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProBook</span></a> or <a href="https://infosec.space/tags/Dell" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Dell</span></a> <a href="https://infosec.space/tags/Latitude" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Latitude</span></a> &amp; <a href="https://infosec.space/tags/Getac" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Getac</span></a> devices, but even <a href="https://infosec.space/tags/Sony" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sony</span></a> (<a href="https://infosec.space/tags/Vaio" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Vaio</span></a> <a href="https://infosec.space/tags/P11Z" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>P11Z</span></a>) and <a href="https://infosec.space/tags/GPD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPD</span></a> did so...</p><ul><li>I hope they at least got a holder-hole and lanyard loop option for the <a href="https://infosec.space/tags/Stylus" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Stylus</span></a> like the <a href="https://infosec.space/tags/X230Tablet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>X230Tablet</span></a> has...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> Q: Aside from asymetric / non-exponential modules, have you tested 64GB &amp; 128GB sticks?</p><ul><li>Cuz Ideally I'd have 128-256GB on a <a href="https://infosec.space/tags/Framework13" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Framework13</span></a>... </li></ul><p>I guess I've to check your <a href="https://infosec.space/tags/QVL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>QVL</span></a> then...</p><ul><li>Jist please don't pull a <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hp</span></a> <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProBook</span></a> and <em>"<a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VendorLock</span></a>"</em> <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a> Sticks!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://kitty.haus/users/lamp" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lamp</span></a></span> I mean in terms of reliability.</p><ul><li>I had cheap 3rd party RAM be unstable on me even at it's designated ratings...</li></ul><p>Since then I'd rather pay a few cents more to get something more stable.</p><ul><li>But that's just bias from past experiences...</li></ul><p>Tho I wounder if one could easily reflash the SPD-EEPROM on those cheaper sticks to circumvent <a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VendorLock</span></a>|s from like <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hp</span></a> <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProBook</span></a>|s that will complain and demand to have F1 pressed every bootup when non-HP-branded sticks are installed!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://sfba.social/@mvilain" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mvilain</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@dangillmor" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dangillmor</span></a></span> <span class="h-card" translate="no"><a href="https://mamot.fr/@pluralistic" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pluralistic</span></a></span> yeah...</p><p>The only reason I still have my DeskJet 6122 hooked up is because that <em>lil shit</em> refuses to die!</p><ul><li><p>Like its glycol ink refuses to clog and it's easy to refill and reset the cartridges...</p></li><li><p>Otherwise I would've already replaced it with a WorkCentre multifunction laser...</p></li></ul><p>Worse are their <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProBook</span></a> line of <a href="https://infosec.space/tags/Laptops" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Laptops</span></a>: They literally <em>"Soft-<a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VendorLock</span></a>"</em> their <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RAM</span></a> to <a href="https://infosec.space/tags/HP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HP</span></a>-branded sticks, bricking <a href="https://infosec.space/tags/PXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PXE</span></a>-boot and requiring people to manually press F1 on the device keyboard <em>EVERY SINGLE BOOTUP / REBOOT</em> with <a href="https://infosec.space/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FUD</span></a> messages.</p><ul><li>Unlike with like <a href="https://infosec.space/tags/WiFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WiFi</span></a> and <a href="https://infosec.space/tags/WWAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WWAN</span></a> chips where one can <em>figleaf argue</em> that those <em>need</em> allow-listing for <em>"spectrum regulatory compliance"</em>, this doesn't apply to RAM!</li></ul><p>On the flipside I use a bunch of <a href="https://infosec.space/tags/fanless" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fanless</span></a> hp <a href="https://infosec.space/tags/ThinClient" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThinClient</span></a>|s as <a href="https://infosec.space/tags/MiniServers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MiniServers</span></a>, but that's because in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Germany</span></a> <a href="https://infosec.space/tags/electricity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>electricity</span></a> is absurdly expensive and for just doing <a href="https://infosec.space/tags/backups" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>backups</span></a> and <a href="https://infosec.space/tags/MediaSharing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MediaSharing</span></a> doesn't draw much power...</p>
Kevin Karhan :verified:Tech shitpost, memes