noauthority.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Long live NAS!

Administered by:

Server stats:

1.3K
active users

#bios

1 post1 participant0 posts today
Replied in thread

This is the massive list of GRUB sub commands that I have to wade through

I have taken a Higher Grade Android to make this photograph and luckily this camera system knows how to capture the Light of the IPS LED panel in Total Darkness.

Compliments of Open Camera Android version

#bash#csh#ksh
Replied in thread

I'm going to include another photograph to give you an indication of how complex GRUB is in comparison to Legacy Lilo

When I press tab twice in Rapid Succession, the whole screen is filled with commands that I can execute within the GRUB sh {command environment}

I literally have to read all the man pages of those GRUB sub commands which give me an indication that they can do what I want, just so I can pass the parameters to the kernel

GRUB has made the distance between the command prompt and the kernel much bigger!

#bash#csh#ksh

Jumping in deep immediately

OS Linux
Kernel 6.x
found workaround for hardware errors on critical timer tsc

snippet from dmesg

[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1796.607 MHz processor

snippet two

[ 0.068905] AMD-Vi: Using global IVHD EFR:0x206d73ef22254ade, EFR2:0x0
[ 0.069804] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.074120] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x19e5a467a58, max_idle_ns: 440795257552 ns
[ 0.074127] Calibrating delay loop (skipped), value calculated using timer frequency.. 3593.21 BogoMIPS (lpj=1796607)
[ 0.074141] Zenbleed: please update your microcode for the most optimal fix

line [ 0.074141] clearly states that my microcode is not updated (not related to tsc)

[ 0.210124] TSC synchronization [CPU#0 -> CPU#8]:
[ 0.210124] Measured 2808 cycles TSC warp between CPUs, turning off TSC clock.
[ 0.210126] tsc: Marking TSC unstable due to check_tsc_sync_source failed
[ 0.210176] #1 #3 #5 #7 #9 #11 #13 #15

I added tsc=unstable to the boot options in grub, so from what I read here the parameter was passed to the kernel? Can someone please verify for me if this output states that?

The warning I get is that the BIOS of this machine is broken! and that the option tsc=unstable will work around that massive bug

#bash#csh#ksh

#matériel #BIOS
Note à moi-même : Ne jamais, JAMAIS activer, nulle part, dans aucun univers connu, l'option "FastBoot" dans le BIOS sinon tu va forcément t'en mordre les doigts.
Je répète: C'EST UNE MAUVAISE IDÉE.
(oui en bidouillant sur mon NAS, j'ai fait la connerie. Oui tu gagnes quelques secondes au boot, mais après t'as l'air con parceque la touche d'accès au BIOS devient inopérante. Et après tu es bon pour jouer du tournevis.)

Continued thread

Part 2/3
Though this has a 64-bit processor, let me try the Win10 x86 32-bit LTSP installer from 2019: and it worked! The install went fine, but it ran dog slow. I used the native browser to download and then upgraded the #BIOS to the latest for the W510 and everything was noticeably slow. Unfortunately, most of the tools I want to use are 64-bit so this version of Win10 is not really an option.
To test & try to troubleshoot, I installed the latest version of #Debian #Linux. The install went fine, and the user experience was much better than the 32-bit Win10 – no real noticeable slowness. Ok, Linux is an option – but not what I had planned for this laptop. Let me wipe the drive (getting rid of #GRUB) and retry installing Win11 or Win10 LTSP.
Now when I boot with either Win11 or Win10 LTSP #USBs the windows logo flashes and the dreaded black screen with blinking cursor appears. We don’t even get the option to install…. (Ugh!)
Currently I booted into #ShredOS and am wiping the drive as a load test.

#siliconValley #SillyValley #sanfrancisco #sanfran #sanfranciscocomputers #sanfrancomputers #sanfranciscovintagecomputers #sanfranvintagecomputers #sanfranciscovintagehardware #sanfranvintagehardware
#vintagecomputing #vintagecomputint #vintagecomputer #vintagecomputers #vintagecomputalk
#vintagehardware #computerHistory #retro #VCF #vintageComputerFestival
#retrocomputing #retroComputers #WallOfRetro #retroTech #retroTechnology
#nerdsOfVintage #happyNerding
#computer #tech #computerHardware #laptop #laptops
#IBM #thinkpad #thinkpads #VintageThinkPad #X86 #WindowsVista #IBMhardware #lenovoHardware #Thinkpadnium
#upcycle #restore #TechnologyRepair #ThinkPadRepair #WasteNoWantNot

Heute an der Installation von #Linux auf einem #asus #notebook gescheitert, noch bevor ich richtig angefangen habe: Das #bios (von 2012) hat trotz aller Versuche den (intakten, getesteten) Bootstick nicht als bootfähiges Medium akzeptiert oder auch nur in der Liste angezeigt.
Das hat sich bei mir noch kein Computer getraut. Freue mich auf Tipps, diese Schlacht will ich nicht verlieren.
(Windows secure boot ist deaktiviert gewesen, legacy boot aktiviert) #boost welcome