When you try to start bios but you can't remember the key

This actually happend in my secondary school class. A new guy came to our class. The whole family moved from another city.
*new guy want to start conversation with me*
new guy: "So you into computers and stuff like that?"
me: "Yes" *seems like a cool guy , want to develop the conversation further* "what about you man? do you like computers? do yo program or smth?"
*new guy wants to look cool in front of me*
new guy: " Yeah dude, actually I am hacker"
*me saying to myself, oh fuck not again this shit*
he continues with: " Once I got into the NASA system"
*switches mode to making fun of him*
me: "what the fuck man? really? that´s freaking cool, how you manage to do that? "
new guy: " you know the thing when you press F10 when starting a comupter? "
me: "You mean BIOS?"
new guy : "yeah yeah man through that shit"
* I am done, laughing my ass off and walks away*

A quite normal Windows day:

Bios to Windows: "Go now! Get up!"

Windows to Bios: "Always slow with the young circuit boards."

"I've got something weird on screen."

Windows' answer: "Ignore it first."

Hardware assistant to Windows: "The user puts pressure. He wants me to identify this thing. Could be an ISDN card."

Windows: "Well, well."

Unknown ISDN card to all: "Will you please let me in?"

Network card to intruder: "You can't spread out here!"

Windows: "Quiet in the case! Or I'll cut both their support!"

Device Manager: "Offer compromise. The network card is allowed on Mondays, the ISDN card is on Tuesday."

Graphics card to Windows: "My driver retired yesterday. I'm crashing now."

Windows to graphics card: "When will you be back?"

Graphics card: "Well, not at first."

CD-Rom drive to Windows: "uh, I would have a new driver here..."

Windows: "What's ich´n supposed to do with it?!"

Installation software to Windows: "Leave it, I'll mach´ that already."

Windows: "That's nice to hear."

USB connection to interrupt management: "Alarm! Just been penetrated by a scanner cable. Request response."

Interrupt management: "Where are you coming from?"

USB connection: "I was in the computer right from the start. I'm joined by another colleague."

"You're not on my list." - "Say something."

Windows: "Hopefully there won't be another printer."

Graphics card: "The new driver twitches."

Windows: "We'll just have to get the old one out of retirement."

Uninstall program to new driver: "Go away."

Unwanted driver: "Fuck you."

Windows to Norton Utilities: "Kill him and his brood!"

Utilities to driver rests: "Sorry, we have to delete you."

Important system file: "Arrrrrrgghh!"

Windows on blue screen: "Gib´, the Norton Boys are over the top again."

Blue screen to user: "So, that's it for this week."

Excuse me for stealing your time

And I know it's way too long

I have this little hobby project going on for a while now, and I thought it's worth sharing. Now at first blush this might seem like just another screenshot with neofetch.. but this thing has quite the story to tell. This laptop is no less than 17 years old.

So, a Compaq nx7010, a business laptop from 2004. It has had plenty of software and hardware mods alike. Let's start with the software.

It's running run-off-the-mill Debian 9, with a custom kernel. The reason why it's running that version of Debian is because of bugs in the network driver (ipw2200) in Debian 10, causing it to disconnect after a day or so. Less of an issue in Debian 9, and seemingly fixed by upgrading the kernel to a custom one. And the kernel is actually one of the things where you can save heaps of space when you do it yourself. The kernel package itself is 8.4MB for this one. The headers are 7.4MB. The stock kernels on the other hand (4.19 at downstream revisions 9, 10 and 13) took up a whole GB of space combined. That is how much I've been able to remove, even from headless systems. The stock kernels are incredibly bloated for what they are.

Other than that, most of the data storage is done through NFS over WiFi, which is actually faster than what is inside this laptop (a CF card which I will get to later).

Now let's talk hardware. And at age 17, you can imagine that it has seen quite a bit of maintenance there. The easiest mod is probably the flash mod. These old laptops use IDE for storage rather than SATA. Now the nice thing about IDE is that it actually lives on to this very day, in CF cards. The pinout is exactly the same. So you can use passive IDE-CF adapters and plug in a CF card. Easy!

The next thing I want to talk about is the battery. And um.. why that one is a bad idea to mod. Finding replacements for such old hardware.. good luck with that. So your other option is something called recelling, where you disassemble the battery and, well, replace the cells. The problem is that those battery packs are built like tanks and the disassembly will likely result in a broken battery housing (which you'll still need). Also the controllers inside those battery packs are either too smart or too stupid to play nicely with new cells. On that laptop at least, the new cells still had a perceived capacity of the old ones, while obviously the voltage on the cells themselves didn't change at all. The laptop thought the batteries were done for, despite still being chock full of juice. Then I tried to recalibrate them in the BIOS and fried the battery controller. Do not try to recell the battery, unless you have a spare already. The controllers and battery housings are complete and utter dogshit.

Next up is the display backlight. Originally this laptop used to use a CCFL backlight, which is a tiny tube that is driven at around 2000 volts. To its controller go either 7, 6, 4 or 3 wires, which are all related and I will get to. Signs of it dying are redshift, and eventually it going out until you close the lid and open it up again. The reason for it is that the voltage required to keep that CCFL "excited" rises over time, beyond what the controller can do.

So, 7-pin configuration is 2x VCC (12V), 2x enable (on or off), 1x adjust (analog brightness), and 2x ground. 6-pin gets rid of 1 enable line. Those are the configurations you'll find in CCFL. Then came LED lighting which required much less power to run. So the 4-pin configuration gets rid of a VCC and a ground line. And finally you have the 3-pin configuration which gets rid of the adjust line, and you can just short it to the enable line.

There are some other mods but I'm running out of characters. Why am I telling you all this? The reason is that this laptop doesn't feel any different to use than the ThinkPad x220 and IdeaPad Y700 I have on my desk (with 6c12t, 32G of RAM, ~1TB of SSDs and 2TB HDDs). A hefty setup compared to a very dated one, yet they feel the same. It can do web browsing, I can chat on Telegram with it, and I can do programming on it. So, if you're looking for a hobby project, maybe some kind of restrictions on your hardware to spark that creativity that makes code better, I can highly recommend it. I think I'm almost done with this project, and it was heaps of fun :D

i am BEYOND pissed at google.

as some of you know, i recently got android studio to run on a chromebook (you read that right), but it being a chromebook and google being a protective fucktard of their crappy operating system, i had to boot into bios every time i started it.

when i was with some friends, i started up the chromebook, and left, after telling my friends how to boot the chromebook.

ten seconds and literally one press of the esc button later, he broke the entire thing.

but that's not what that rant was about, i honestly knew it would happen eventually (although, this wasn't the best time).

so now this screen pops up.

"chrome os is damaged or missing, please insert a usb recovery drive" or something like that.

well, i'll create one. simple enough.

no wait, this is google, just your average 750 billion dollar company who cares more about responsive design then a product actually responding.

i started to create the recovery usb. of course, chrome developers thought it would be a good idea to convert the old, working fine, windows executable usb recoverer, and replace with with a fucking chrome extension.

i truly hope someone got fired.

so, after doing everything fine with the instructions, it got to the part where it wrote the os image to the usb. the writing stayed at 0%.

now this was a disk thing, writing os's and shit, so i didn't want to fuck it up. after waiting ten minutes, i pressed 'cancel.'

i tried again many times, looked things up, and frantically googled the error. i even tried the same search queries on bing, yahoo, duckduckgo and ecosia because i had the feeling google secretly had tracked me over the past 7 years and decided to not help me after all the times i said google was a fucker or something similar.

google is a fucker.

after that, i decided to fuck with it, even if it formats my fucking c drive.

i got to the same point where the writing got stuck at 0% and proceeded to fuck. i start spamming random keys, and guess what?

after i press enter, it started.

what the fuck google?
1000s of people read the article on how to make the recovery drive. why not tell them to press the goddamn enter key?

i swear there are hundreds of other people in my same situation. and all they have to do is press one fucking key???

maybe tell those people who tried to fix the shit product you sold them.

fuck you google.

So to start off this happened today while I was at school.

Each student gets a netbook for school and the amount of restrictions put in place are probably up to government spec. Well I brought in my personal netbook and a flash drive with a few distros of Linux on it on it to mess with during study hall(all on my own hardware).

I told my friend that about it and said I doubted it would boot because the bios is password protected and the IT guy probably removed external drives from the boot list but let him use it anyway.

5 minutes later he is showing me his screen with Ubuntu running on it, I was freaking out some and asked for it back and he gave it back to me.

About a minute later he shows me his screen. All black with white text shooting down it saying windows disk integrity check or something like that. All I see is "file xyz deleted" and was freaking out even more. I just sat there for the next 20 minutes thinking of how to explain this to the IT guy and hopefully get in less trouble.

Finally after the longest 20 minutes of my life as a student I see the windows 7 boot screen appear. Probably the one time I actually wanted to see it honestly but I was so happy to see the end of the situation.

Sorry this was so long but I hope it's fine for a first post here, I've been putting it off but after this decided to finally post.

Always back up your data.

I came to my computer earlier today to find it on my Linux login screen. This could only mean one thing: something went horribly wrong.

Let me explain.

I have my BIOS set up to boot into Windows automatically. The exception is a reboot or something horrible happens and the computer crashes. Then, it boots me into Linux. Due to a hardware issue I never looked into, I have to be present to push F1 to allow the computer to start. The fact that it rebooted successfully, without me present, into *Linux*, could only mean one thing:

My primary hard drive died and was no longer bootable.

The warning was the BIOS telling me the drive was likely to fail ("Device Error" doesn't really tell me anything to be fair).

The massive wave of panic hit me.

I rebooted in hopes of reviving the drive. No dice.

I rebooted again. The drive appeared.

Let's see how much data I can recover from it before I can no longer mount it. Hopefully, I can come out of this relatively unscathed.

The drive in question is a 10 year old 1.5 TB Seagate drive that came with the computer. It served me well.

Press F to pay respects I guess.

On the bright side, I'll be getting an SSD as a replacement (probably a Samsung EVO).

In my day off I was eager to try overclocking in my pc and this is how it went:

- Fucked up overclocking parameters for cpu and ram speed.

- BIOS is broken, had to take out gpu to do a reset taking out the bios battery.

- BIOS is up again, default values loaded, bla bla

- Did not try to fuck off anymoar with overclocking, just kept playing star wars and went to sleep safe and sound like a baby.

- Gotta work now. docker does not start, closes itself after tried to start, docker panic, I panic, tried to uninstall, tried to update. nothing works

- Then I remember bios default values leaves virtualization off. enables it again, docker still not working. I panic again, restarted pc like 10 times between disabling/enabling hyper-v in windows.

- Docker dies. not gonna change my overclock options again. silly me 🤦‍♂️

TL:DR; DON'T GET INTEL+NVIDIA LAPTOP FOR LINUX.

In the same vain as Linus Torvalds: "Fuck Nvidia, and Intel".

Trying to get intel+nvidia laptop prime w/e working is a living hell.

I'm running Manjaro(arch for lazy people) with I3-gaps(larbs).

So Manjaro provides this handy script/program mhwd that supposedly would enable the non free blob Nvidia driver except it doesn't work cause it uses bumblebee and it's saying it can't find the clearly installed fucking Nvidia driver.

Bashing my head against a wall is more fucking productive then getting my cum stain of laptop to work properly.

"Just disable the intel graphics in bios"
I would except my old shitty Acer bios piece of fucking crap can't even after booting Windows for usb hdd and flashing BIOS.

GUESS WHAT LINUX COMMUNITY THAT'S WHY NOBODY WANTS TO FREAKING USE LINUX FOR GAMING.

I fucking love Linux but I gave up gaming for it.

I'll start joining red team from now on instead of trying to use your broken shit.

I hate that my bios take twice as long as Linux, to start. It is only 15 seconds, but still.

Tl; dr: Linux on Ryzen is a pain at the moment.
Now for the long part: Our student council got new computers because the old ones where slow as hell. As one of the admins, the others and I together decided that ryzen would be a good option, because they are not that expensive and we wouldn't have to buy gpus. (Wrong decision it turns out.) We settled on the ryzen 3 2200G and bought three systems to replace the old ones.

We meet Saturday morning and build the systems. All was fine and we were happy. The we tried to install ubuntu via preseeded netboot, which seemed to work fine at first. Then we started having weird screen issues and couldn't proceed with the installation. (See image) we then grumpily decided to just install them all one by one, flashed two usbs and started installing. On two systems the installation worked and we installed our packages, we weren't so lucky with the third one. It would crash on us all the time, even in bios. While that was going on we tried to set the other two up, turns out those two were also crashing but not as frequent as the other one. So we start to google and find people saying that kernel 4.19 kinda fixes it. We install it on the two working machines and the crashes get less frequent but are still there. At that point it was midnight and we went home.
Sunday morning: we reseated the cpu on the third system and it seems to be better now (it installed on the second try) and we were able to change the kernel. Yay. Now all three are in a state where they will sometimes randomly reset. :/ and we don't know what to try anymore.... Any suggestions?

So I did a clean Windows 10 restore recently on my laptop from Insider program to just Anniversary Update . Went away from my computer for a day or so by the time I got updates completed and Visual Studio up and running. So earlier today I went to start back up development on a project of mine to come across the emulators not working. The thing is that I lost 6 hrs of production to figure this out. I tried everything possible so I gave up and reinstalled VS to just remember I forgot to turn on my Hyper-V in BIOS setting. So I'm half way in VS reinstalling and I can't do anything about it. GOD FUCKEN DAMMIT W10!

Stories like the one I'm about to tell you are just another reason why people hate Windows. I know I usually preach 'Don't hate everything' and shit, but this is a real big fucking deal when it hits your desktop for no reason.
Now, onto the actual story...

Background: Playing with my Oculus, fixing issues like forgetting to use USB3 and stuff. I learned about an issue with Nvidia GPUs, where in Windows, they can only support 4 simultaneous displays per GPU. I only have the one GPU in my system, Nova, so I have to unplug a monitor to get Oculus and its virtual window thingy working. Alright, friend gave me idea of using my old GPU to drive one of my lesser used monitors, my right one. Great idea I thought, I'll install it a bit later.

A bit later...

I plug the GPU in (after 3 tries of missing the PCI-E slot, fuckers) and for some reason I'm getting boot issues. It's booting to the wrong drive, sometimes it'll not even bother TRYING to boot, suddenly one of my hard drives isn't even being recognized in BIOS, fuck. Alright, is the GPU at least being recognized? Shit, it isn't. FUCKFUCKFUCK.

Oh wait. I just forgot the power cable Duh. Plug that in, same issues. Alright, now I have no idea. Try desperately to boot, but it just won't I start getting boot error 0xc000000f. Critical device not found. Alrighty then. Fuck my life, eh?

Remove the GPU, look around a bit while frantically trying to boot the system, and I notice an oddly bent SATA cable. I look at it and the bastard is FRAYED AT THE END! Fuck, that's my main SSD! I finally replace the SATA cable and boot, still the same error... Boot into a recovery environment, and guess what?

Windows has decided to change my boot partition, ya know, the FUCKING C: DRIVE, from NTFS to RAW format, stripping it of formatting! What the actual fuck Microsoft? You just took a shit on yourself while having a seizure on the fucking MOON! Fine, fuck you, I have recovery USB! Oh, shit, that won't boot... I have an old installation! Boot ITS recovery, try desperately to find a fix online... CHKDSK C: /F... alright, repairing, awesome! Repaired, I can see data, but not boot. So now I'm at the point where I'm waiting for a USB installer to be created over USB 2.0. Wheeeeeeeeee. FML.

THESE are the times I usually hate Windows a lot. And I do. But it gets MOST of my work done. Except when it does this.

I'm already pissed, so don't go into the comments and just hate on Windows completely. Just a little. The main post is for the main hate. Deal with it. And I know that someone is going to come at me "Ohhhhh, you need FUCKIN LIIIIIIINUUUUUUUXXXXXXXX!' Want to know my response to that?

No.

Oh fucking hardware virtualization.
how many times have I failed at setting sth up googled it and just read "check your BIOS ... and enable..."
Well I would IF I FUCKING COULD. THERE AIN'T NOTHING TO ENABLE ON THIS CHEAP CPU.

I know. I know. Should just get a newer setup, this lappy ain't that powerful anyways - but still - it's frustrating to get excited, start sth and than hit that dead end realizing they presupposed sth I don't have.

Viruses are little monsters that eat your computer away (or what's left from it) after it's dead. They start with the heart (BIOS) and then go to the CMOS chip.

Ok... Can someone explain me this?
Happen a few weeks ago.
My pc would crach on any 3D program or game.
Did some tests, was the graphic card.
Send it to repair (amd, Asus made)
Placed my old Nvidia, installed drivers all good.
My new card came, nothing repaired, nothing found, passed all stress tests.
Placed the card back ok, no OS.
Bios detects both ssds but don't start (windows 10.... Ya tryed Linux but doesn't work for my main past time in pc, Arma 3).
Loaded the USB with the windows instalation, used command line drive C is completely empty but has 160gb used.
Ended ip formating.
GC works perfectly.
So... Wtf happen?

Probably a very stupid question.

Is it possible to customize the BIOS by changing colors/fonts/adding images/ascii art or even create a custom interface?

Anyone has any idea if this is possible and if so, some useful sources how to do this and where to start?

Thanks

!rant
My home pc has developed a sudden issue and wont boot up anymore.

Stays stuck on the POST phase and am unable to get into BIOS , just stuck with a big asus logo and a message to press
F2 or Delete to get into BIOS but the system seems frozen as the keyboard lights are on but unresponsive while the
Mobo reads an error code A2
( the manual claims that to be an IDE error although am using only SATA)

Unplugging all usb doesnt change anything.

Unplugging all other sata ssd ,hdd and disk drives except the os drive changes nothing.

Unplugging the os drive results in the system complaining about no bootmgr
(As expected), that allows me to at least look at the BIOS but there doesnt seem to be anything wrong or out of the ordinary..

Booting from a live cd works fine

Booted from a pc boot repair tool and plugged in the os drive into one of the hot swappable sata ports shows me the all the files still there and accessible , check disk revealed nothing wrong. Can't plug in the os drive pre boot as that locks everything up again)

Tried to boot with a windows cd then do a start up repair but plugging in the os drive into the hot swappable sata doesn't work since windows can't see the drive.

Tried to swap the os drive with another one of exact same model filled witb random files resulted in no boot mgr error as expected

Struggled a whole weekend to fix it but alas no progress
Ah and the OS drive's warranty ran out 2 weeks ago 😑

Mobo asus p9x79 deluxe
Os ssd samsung 840 250 gb
No changes in hardware for the last year
Or so
No BIOS changes in over a year

I did notice some odd files like 0002Found
On the os drive when i was using the boot repair live cd tool, will bring the drive to
The office where i can get my hands on an ssd sata to usb caddy and take a snapshot of The files there for you guys to see.

Any ideas ? 😞