Once I failed captcha 4 times in a row. My colleagues told me: "Update your firmware, RoboCop"

Someday my toaster is going to have an IP address. A bad automatic firmware update will most likely cause it to get stuck on the bagel setting until I plug a usb key in and reflash the memory.

Grandma's refrigerator will probably get viruses, lock itself and freeze all the food inside, demanding bitcoin before defrosting.

My blender will probably be used in a massive DDoS attack because Ninja's master MAC address list got leaked and the hidden control panel login is admin/admin.

Ovens will burn houses down when people call in to have them preheat on their way home from work.

Correlations between the number of times the lights are turned on and how many times the toilet is flushed will yield recommendations to run the dishwasher on Thursdays because it's simply more energy efficient.

My dog will tweet when he's hungry and my smart watch will recommend diet dog food in real-time because he's really been eating too much lately--"Do you want to setup a recurring order on Amazon fresh?"

Sometimes living in a cave sounds nice...

Not a rant, but I found this funny enough to share.

About two weeks ago, I’m contacted by a third party development firm that is responsible for building the next iteration of a control board were are developing. Alongside build of the PCB they were scoped to flash the firmware and verify all connected components.

During the call, they tell me they don’t have the resources to build our testing environment with the Ansible script I provided, and they don’t know if the updates they have made will work with our control system. Ugh...really...

I attempt to walk them through the 3 pretty simple commands to launch the playbook. Instead of listening, their project manager insists that I need to load up the environment and send them a ready to go system.

I quickly load up a RaspberryPi and prepare it for shipping. I hand the box to our shipping clerk and fill out the shipping request documentation. Then about a week goes by and this is where the story really begins.

I get an email from the same rep asking where the environment is, and I head down to the warehouse to inquire where the RaspberryPi might be. After speaking with the head clerk, we can’t seem to track down the package. I’m assured that they will find the Pi and send me the shipment update.

I pass the information along and after about a day and a half I still didn’t receive word back from the warehouse team. I load up another Pi and head back down to the warehouse. I follow up with the warehouse staff. They inform me that they have not been able to locate my package and another warehouse worker is called over. He says he hasn’t seen it, but they they were having a food day that day and he thinks more than likely someone ate it.

Like it didn’t even click at first but after a few seconds I realize that these guys have literally been looking for a pie for the past two days...and I JUST DIE.

After the 5 or so minutes of laughing I show them the newly flashed RaspberryPi, and of course they know exactly where the original one was.

It’s shipped out now, but wow. Also, it turns out the PCB manufacturing company didn’t even really need this and it was all a guise to hide that they are behind schedule and that they will not be able to finish the work scoped. FML!

Buckle up kids, this one gets saucy.

At work, we have a stress test machine that trests tensile, puncture and breaking strength for different materials used (wood construction). It had a controller software update that was supposed to be installed. I was called into the office because the folks there were unable to install it, they told me the executable just crashed, and wanted me to take a look as I am the most tech-savvy person there.

I go to the computer and open up the firmware download folder. I see a couple folders, some random VBScript file, and Installation.txt. I open the TXT, and find the first round of bullshit.

"Do not run the installer executable directly as it will not work. Run install.vbs instead."

Now, excuse me for a moment, but what kind of dick-cheese-sniffing cockmonger has end users run VBScript files to install something in 2018?! Shame I didn't think of opening it up and examining it for myself to find out what that piece of boiled dogshit did.

I suspend my cringe and run it, and lo and behold, it installs. I open the program and am faced with entering a license key. I'm given the key by the folks at the office, but quickly conclude no ways of entering it work. I reboot the program and there is an autofilled key I didn't notice previously. Whatever, I think, and hit OK.

The program starts fine, and I try with the login they had previously used. Now it doesn't work for some reason. I try it several times to no avail. Then I check the network inspector and notice that when I hit login, no network activity happens in the program, so I conclude the check must be local against some database.

I browse to the program installation directory for clues. Then I see a folder called "Databases".

"This can't be this easy", I think to myself, expecting to find some kind of JSON or something inside that I can crawl for clues. I open the folder and find something much worse. Oh, so much worse.

I find <SOFTWARE NAME>.accdb in the folder. At this point cold sweat is already running down my back at the sheer thought of using Microsoft Access for any program, but curiosity takes over and I open it anyway.

I find the database for the entire program inside. I also notice at this point that I have read/write access to the database, another thing that sent my alarm bells ringing like St. Pauls cathedral. Then I notice a table called "tUser" in the left panel.

Fearing the worst, I click over and find... And you knew it was coming...

Usernames and passwords in plain text.

Not only that, they're all in the format "admin - admin", "user - user", "tester - tester".

I suspend my will to die, login to the program and re-add the account they used previously. I leave the office and inform the peeps that the program works as intended again.

I wish I was making this shit up, but I really am not. What is the fucking point of having a login system at all when your users can just open the database with a program that nowadays comes bundled with every Windows install and easily read the logins? It's not even like the data structure is confusing like minified JSON or something, it's literally a spreadsheet in a program that a trained monkey could read.

God bless them and Satan condemn the developers of this fuckawful program.

I live in an apartment building that has about 20 floors. About once every month, I'm either waiting for the elevator or in it, and the floor indicator display flashes "14" very quickly no matter what floor the elevator is actually on. Whenever this occurs, it's always 14 that gets shown.

This has made me think about what this bug looks like and if it will ever be fixed. Will they ever update the firmware in the elevators? Is it a software issue? It could also be a hardware problem. Either way, every time it happens I think about it and if this bug will ever be fixed.

I've decided to call it the "phantom floor 14 bug."

I installed a firmware update on my router, and discovered it both adds telemetry and breaks the navigation in firefox. 🤦‍♀️

It also started complaining that my password isn't secure (despite its length) because it doesn't contain a symbol.

Good freaking job.

If you are a salesperson, you can just go straight to hell. You're all a bunch of cocksucking twats and I'm amazed you manage to get yourselves dressed each day. You're a no good fucking waste of oxygen and you need to put your fork in a socket the next time you're eating.

I'm working on building a crm and ticket management system for use in the office to handle client passwords. Since I'm building from scratch I wanted to make sure I had properly planned my classes and functions before opening the code editor so I put a message on my door that says "Don't interrupt, thanks" followed by the date so people knew it was a fresh message and not something left from the previous day.

I'm deep in the zone, the psuedo code and logic is flowing, I'm getting classes planned and feeling really productive for an hour or so when suddenly my door flies open and in comes a sales person.

SP: "Hey, do you have any extra phones lying around? Mine's being slow and keeps hanging up on people."

Me: "Do you see the sign on my door right there at eye level which says not to bother me?"

SP: "oh, do you want me to come back later?"

Me: "You've already interrupted me now, let's go see what's going on before I spent an hour setting up a new phone for you." While we are walking across the office I asked him when the last time the phone rebooted.

SP: "idk, Salesperson#2 suggested that as I was headed over here but I figured I'd just ask you."

We get over to his desk and I see he has two phones sitting on his desk. "Where did this one come from?"

SP: "Oh that was on the desk over here but I figured I could use it."

Me: "Well aside from the fact that the phones are assigned to specific people for a reason, you took the time to unhook your phone to set this one up and you didn't think to reboot your phone first. Plug your phone back in."

He plugs the old phone, which is assigned to him, and while booting it does a quick firmware update and boots up fine. He tests a few things and decides it's all better now.

So someone suggested a fix for you and you decided, instead, you would break company IT policy by moving equipment from one station to another without notifying the IT department. You entered a room which had a closed door without knocking, and you disobeyed the sign on the actual door itself which politely requests that you go away. All because you couldn't be bothered to take 2 minutes and reboot your phone, which you had to do anyways.

You completely broke my train of thought and managed to waste 2 hours of effecient workflow because you had an emergency.

(Written March 13th at 2am.)

This morning (yesterday), my computer decided not to boot again: it halts on "cannot find firmware rtl-whatever" every time. (it has booted just fine several times since removing the firmware.) I've had quite the ordeal today trying to fix it, and every freaking step along the way has thrown errors and/or required workarounds and a lot of research.

Let's make a list of everything that went wrong!

1) Live CD: 2yo had been playing with it, and lost it. Not easy to find, and super smudgy.

2) Unencrypt volume: Dolphin reports errors when decrypting the volume. Research reveals the Live CD doesn't incude the cryptsetup packages. First attempts at installing them mysteriously fail.

3) Break for Lunch: automatic powersaving features turned off the displays, and also killed my session.

4) Live CD redux: 25min phonecall from work! yay, more things added to my six-month backlog.

5) Mount encrypted volume: Dolphin doesn't know how, and neither do I. Research ensues. Missing LVM2 package; lvmetad connection failure ad nauseam; had to look up commands to unlock, clone, open, and mount encrypted Luks volume, and how to perform these actions on Debian instead of Ubuntu/Kali. This group of steps took four hours.

6) Chroot into mounted volume group: No DNS! Research reveals how to share the host's resolv with the chroot.

7) `# apt install firmware-realtek`: /boot/initrd.img does not exist. Cannot update.

8) Find and mount /boot, then reinstall firmware: Apt cannot write to its log (minor), listed three install warnings, and initially refused to write to /boot/initrd.img-[...]

9) Reboot!: Volume group not found. Cannot process volume group. Dropping to a shell! oh no..

(Not listed: much research, many repeated attempts with various changes.)

At this point it's been 9 hours. I'm exhausted and frustrated and running out of ideas, so I ask @perfectasshole for help.
He walks me through some debugging steps (most of which i've already done), and we both get frustrated because everything looks correct but isn't working.

10) Thirteenth coming of the Live CD: `update-initramfs -u` within chroot throws warnings about /etc/crypttab and fsck, but everything looks fine with both. Still won't boot. Editing grub config manually to use the new volume group name likewise produces no boots. Nothing is making sense.

11) Rename volume group: doubles -'s for whatever reason; Rebooting gives the same dreaded "dropping to a shell" result.

A huge thank-you to @perfectasshole for spending three hours fighting with this issue with me! I finally fixed it about half an hour after he went to bed.

After renaming the volume group to what it was originally, one of the three recovery modes managed to actually boot and load the volume. From there I was able to run `update-initramfs -u` from the system proper (which completed without issue) and was able to boot normally thereafter.

I've run updates and rebooted twice now.
After twelve+ hours... yay, I have my Debian back!

oof.

Never update the firmware of your delta-fan driven server when your girlfriend is sleeping. Got thrown out of my own room!
Fml

I bought an internet radio from pioneer...
Unfortunately, the remote control has a small delay. So I thought, maybe there's an app to control the radio. But after downloading the app could not connect. During a network scan several services appeared. You are able to update the firmware via an unprotected web interface which makes me sad. But that's not the best thing yet. You can also connect to the device via the telnet port. Guess which user you are...

In the before time (late 90s) I worked for a company that worked for a company that worked for a company that provided software engineering services for NRC regulatory compliance. Fallout radius simulation, security access and checks, operational reporting, that sort of thing. Given that, I spent a lot of time around/at/in nuclear reactors.

One day, we're working on this system that uses RFID (before it was cool) and various physical sensors to do a few things, one of which is to determine if people exist at the intersection of hazardous particles, gasses, etc.

This also happens to be a system which, at that moment, is reporting hazardous conditions and people at the top of the outer containment shell. We know this is probably a red herring or faulty sensor because no one is present in the system vs the access logs and cameras, but we have to check anyways. A few building engineers climb the ladders up there and find that nothing is really visibly wrong and we have an all clear. They did not however know how to check the sensor.

Enter me, the only person from our firm on site that day. So in the next few minutes I am also in a monkey suit (bc protocol), climbing a 150 foot ladder that leads to another 150 foot ladder, all 110lbs of me + a 30lb diag "laptop" slung over my shoulder by a strap. At the top, I walk about a quarter of the way out, open the casing on the sensor module and find that someone had hooked up the line feed, but not the activity connection wire so it was sending a false signal. I open the diag laptop, plug it into the unit, write a simple firmware extension to intermediate the condition, flash, reload. I verify the error has cleared and an appropriate message was sent to the diagnostic system over the radio, run through an error test cycle, radio again, close it up. Once I returned to the ground, sweating my ass off, I also send a not at all passive aggressive email letting the boss know that the next shift will need to push the update to the other 600 air-gapped, unidirectional sensors around the facility.

5 stages of failing WIFI connectivity on Linux

This morning I woke up my laptop to start my work day. I have 2 very important meetings today, so I better get all prepared.

"Wifi connection failed"
Syslog says:
- wpa_supplicant: wlp9s0: SME: Trying to authenticate with <MAC>
- kernel: wlp9s0: authenticate with <MAC>
- kernel: wl9s0: send auth to <MAC> (try 1/3)
- kernel: wl9s0: send auth to <MAC> (try 2/3)
- kernel: iwlwifi: Not associated and the session protection is over already...
- kernel: wl9s0: send auth to <MAC> (try 3/3)
- kernel: wl9s0: authentication with <MAC> timed out

#### DENIAL #####

No biggie, let's try another AP (I have 3). All 3 failed to connect. Fine, let's try my phone's hotspot! FAILED!!!!!

w00t.... okay, let's restart the router... but failing to connect to a phone hotspot is already a worrying sign.

Wifi connection failed

wtf.. disable and re-enable wifi

Wifi connection failed

#### ANGER #####

the fuuuuuuck. Maybe my router is dead. But my phone connects to it, no fuss. My personal lappy also connects there easily.

wtf... Does that mean I'm about to lose my uptime?? Come one!! It's Linux - there MUST be something I could do! I don't see processes hanging in D state so the radio must be fine - it's gotta be a software issue!

ChatGPT – type all the log entries manually, via phone (that took a while...). Nothing useful there: update firmware, restart NetworkManager, etc.

#### BARGAINING #####

Alright... How about a USB dongle? Plug it in and wifi connects immediately! Yayyy!!! But that's only b/g/n and I'd very much like to have ac. It works well as a limping backup, but not something I'd use for the meetings.

rfkill block/unblock all the radios. No change. USB dongle connects right away but the PCIe adapter keeps throwing notifications at me with failure messages. It's annoying, to say the least.

So I've already tried
- restarting the router(s)
- disabling/reenabling the radios
- multiple APs
- suspending/waking again several times
- praying

#### DEPRESSION #####

The only thing I haven't tried yet is the most cruel one - restarting the laptop. But that's unfair... It's LINUX! How could it disappoint me. I have so many tmux sessions open, so many unsaved leafpad notes, terminal histories with oh so comfy ^r and ! retriggers all ready and waiting to be executed...

#### ACCEPTANCE #####

But I can't miss the meeting. So I slowly start closing off apps, starting with the least important ones, trying to preserve as much history and recent commands as I can. I'm gonna lose my uptime, that's the inevitable obvious truth... Linux has failed me. Or maybe it's a hardware issue... I can't be sure until I restart.

I must reboot.

#### A NEW HOPE #####
Hold on.. What if... What if before restarting I try to reload the Intel wifi kernel module? Just for the giggles. I've got nothing to lose anyway...

rmmod iwlmvm
rmmod iwlwifi
modprobe iwlwifi
modprobe iwlmvm

*WiFi Connected*

YESSSS!!!!!!!!! My uptime is saved!
403 days and counting! YEAH BABY!!!

Linux is the best!

What is it with these companies and mandatory updates?

Microsoft with windows 10. Sorry your doing work? Nah, we've decided your going to update now! Sorry, we based our default update time on people not working late at night.

Philips hue. Wanna turn on your lights? Sorry, mandatory firmware update. You'd better install that before being able to see.

YouTube app on ps4. No sorry, can't open this, mandatory 80mb update.

FUCK SAKE PEOPLE.

Sony updates the firmware on their wireless headphones over Bluetooth. For TWO FUCKING HOURS. If, for some reason, the connection was to break during that period, - perhaps because Bluetooth isn't a reliable connection and was never meant to be - then the device will turn itself off (as it does when it loses connection), and it will try to boot into the half-installed firmware the next time you turn it on.

My college updated a firmware of our device. The device stopped working. He then proceeded to update all the other devices one by one with the same new firmware before coming to a conclusion that it is indeed the firmware that is broken. We needed to send all the devices back to the manufacturer and almost missed our deadline.

This moment when you are laying in your bed trying to turn off the lights and the uncloseable firmware update window forces you to update your lights before be able to turn them off.

Dear boss,
I'm calling in sick today - this fucking thing has the bright idea to update the firmware on its own.

Regards,
@C0D4

This is a follow up to my previous rant where I complained about Lenovo firmware update failing and bricking a relative’s computer.

We bought a chip programmer, got the bios from some forum and the thing fucking worked. I’m actually surprised it did, I’m not used to doing shit like this. I was pretty fucking scared of burning something.

The programmer also came with a clamp so we could hook it to the chip without desoldering it. Thank god.

I’m terribly depressed so good timing with that I guess.

Laying cozy on sofa, watching yt from phone. Decide there's a need for a bigger screen but too cozy to adjust position to watch from TV. Grab trusty old chromebook running Debian from arm's reach instead. Haven't used that thing in a while. Try to connect bt headphones. Notice that the Bluetooth module is not detected according to the UI. Weird, never noticed that. Wonder what that's about. Apparently someone had fixed it in kernel already long ago, I'm on a much newer kernel. Too lazy to pick up wired headphones from across the room. Maybe I'll update the firmware, I haven't done that in a while. Oh, the script doesn't run because it requires newer glibc. Wait, I'm still on Debian 11, maybe it would be worth it to upgrade to 12. Wow, upgrading Debian is a surprisingly manual process. Wonder what I'll be doing tonight. Wait, what was I doing again?

THIS IS OUTRAGEOUS.

I recently got a secondhand Sony WH-1000XM3 headphones. they were used for less than a year, were in perfect shape and they still had warranty.

The app that is supposed to go alongside the headphones told me that I have a firmware update for my headphones. So naturally, I pressed install.

AGAIN, THIS IS A FIRMWARE UPDATE ISSUED BY SONY!!

It bricked the headphones. I can't turn them on.

The issue was probably Bluetooth file sharing. BTFS is SO unreliable and it's known to be unreliable and Sony updates their top tier headphones with this communication method.

Thankfully, I still have warranty. I had to fight with the official importers of Sony in Israel (called "Ishfar", you read it like you see it) to go through the process of repairing / giving me a replacement.

O U T R A G E O U S

I guess Motorola decided to join the Slow Down Your Device So You'll Buy The Next Model club. I had a Moto G5s Plus I bought not too long ago. I mainly use it for debugging now.

I mean, can't prove anything, all I can say for certain is their last update, literally, the final one they plan on releasing for that model, made the device so slow it was useless.

So I unlocked it and put LineageOS on it. Not easy, since there's no official build for it. Once I got it working, all the issues with the stock firmware vanished. It runs faster than it ever has.

Now I get greeted with a message when it boots telling me that the device was unlocked and can't be trusted, because, you know, we can all trust cell phone manufacturers to not put a bunch of spyware on our phones.

Recently I have updated my lubuntu to 18.04.
I don't use it regularly but I like to have it on the side of my window 10.
Anyway today I boot and decide to use it and get this error.
[0.000000] [Firmware Bug]: TSC_DEADLINE disabled du to errata; please update microcode to version 0x22 (or later)
and two MMIO read fault.

At first it sounds really dramatic and I was thinking, "Nice ... I never get a problem with Windows Update and when its Linux it doesn't work ..."

But lubuntu boots normally after so it's not a blocking problem.

So I do what most of us do in case like this, go to Google and search to know what the hell is going on.

And the answer is simple, my CPU microcode isn't up to date to prevent Spectre, one apt get install and a reboot later my 4700HQ is patched in 0x24 version and protected for Spectre where my windows didn't patch anything and worst disable the KB that I have installed manually before the last big update.

So thanks Linux, you scared me with your error but it was a good job to throw it :)

Reanimated an old e-ink tablet today.

First, I didn't even know it needed to be reanimated. I just copied my books there, but it didn't find them. When I connected it again, they were gone.
Factory reset. Format storage. The memory seems empty, but after rebooting I see that everything is still intact.
Ok, imma hit forums then. They tell me I need to replace the internal memory. But isn't that something you need soldering for? Wrong! The internal memory IS JUST A MICRO SD CARD on the motherboard. The card is some cheap no name one, and people tell the similar story of it burning out after like four years of use.
Damn! The vendor has the AUDACITY to charge for signing their firmware to be flashed to a new micro sd card.

But I won't go down this easily. I hit forums again, and apparently there is a tool to sign the firmware yourself, but you need to find the card's serial number. To do that, you have to flash a bootleg tool, boot from that card, and it will show you the data you need. Then, you have to insert them into some shady .ini file (why is everything touching bootleg firmware runs only on windows?).

So I do that. The problem is, I need an image for my book. I find some shady one online, sign & flash it — touchscreen doesn't work. But I have the official firmware. I put two and two together and figure out that if the reader is able to display the ui, it probably has the firmware update tool working. So, immediately after flashing, I launch the firmware update utility that picks up my firmware from the second sd card (yes, they have an additional external slot).

Bingo. It works.

So, here are the steps:
1. Find a shady sd serial number detection tool
2. Flash it on a memory card with a shady vendor-specific flashing tool
3. Insert the new (now shady) card
4. Boot, write down the serial number
5. Find a shady boot image online
6. Edit a shady .ini file of a shady self-signing tool to sign the shady boot image
7. Flash the altered shady boot image with the shady flashing tool on your memory card
8. Copy a shady firmware update on a new card
9. Insert both cards
10. Pray

TLDR; macOS wouldn’t update to the version I needed because I have a 3rd party SSD. All I needed was a firmware update only found deep within a google search and a secondary SO answer.

I have a video edit project this weekend. No big deal.

Except that the Final Cut Pro project was saved in the latest version of FCPX, for which I need latest MacOS version

As a music producer on the side, I had heard the new file system of MacOS High Sierra would possibly break audio plugins. I didn’t bother updating until now. Looked further into plugin problem, it would be simply a broken hard link which I can easily fix. No big deal.

Except that I have upgraded my MBP SSD from 256gb to this 3rd party 480gb SSD. macOS does not recognize this SSD as compatible with update. No big deal. Simple google search for a terminal command would do the trick.

Except that I found and tried several solutions, including wasting an entire hour updating the original ssd and booting from that to try to update it.

Nothing worked, but deep down in the google search, found in a secondary answer on SO, there was a link for a beta release of a firmware update for the SSD that took two minutes to install, and I was finally able to update.

That firmware update needs to be more prominent everywhere. Wasted well over 3-4 hours updating crap, swapping out SSDs, and googling when all I needed was a fucking firmware update.

My 2009 ThinkStation has been running loud for a couple of years now, reaching temps in the 70s-80s at max load (40s idle) with stock settings, fans spinning like jet engines to try to cool it. Only recently (today) did I consider that maybe there's dust stuck somewhere, so I took the fan off my cooler and began the hunt there.

IT WAS FUCKING COVERED. Half of the fin intake area behind the fan was completely clogged up with dust. I was starving the poor thing and I never figured out why until now.

I deep-cleaned the entire system, and now it's running a gentoo install with all cores maxed running compiler tasks... Fans are much quieter, barely above idle noise, the main difference is just pitch of the noise because of the higher RPMs.

I dont have the firmware installed to measure temps, but I will update once I get that data.

Specs, in case anybody is curious:

> Xeon W3520 4c/8t 2.67Ghz
> 8GB DDR3 1066MHz
> RX 460 2GB (my student-budget upgrade)
> Dual 500/750GB HDD

Bought a new toy drone to play with at home, Ryze Yello. It boasts an Open SDK on the box and claims to be programmable. Awesome, I think, I end up buying and going home to get to work.

All is great using the app, I can fly the drone and the video feed is mostly usable. Now let's get in to the SDK and see what we have.

Docs say I've got a few basic commands, 8 directional flips, 6 directions of movement, rotate, takeoff, and land. Plus a config option to set the speed. After a bit of tinkering I discovered that only 3 commands actually work: takeoff, flip, land. The rest error out with no (currently) useful message.

A bit more searching online tells me that they borked the commands with a recent firmware update and are working on it as of 3 months ago.

I wish I knew more about firmware or deconstructing the wifi packets from the app so I could try to do something useful.

So many stupid things I wanted to do with an automated drone and I'm stuck waiting for them to fix their firmware to put functionality back into the device.

Actually have a dev thing to say now.

I wrote a script to compile my kernel with the latest mainline version using my current config options. It works...so far. I'll check back with it in a couple months and hope it still works good. It also checks daily if my kernel is out of date (yes I'm one of those, fight me)

Also managed to get my laptop to boot from power on to LightDM in 15 seconds, and 9 of those seconds are firmware. It DOES have this thing on occasion where it freezes during the boot process while initializing everything tho?? I've been meaning to try and figure it out for a minute but I put it off so much cause I don't reboot that often anyways.

As for a personal update, I hung out with some good friends today and my best friend heard my singing voice for the first time, she said I have a good voice (she does a lot of musicals and stuff and just sings all the time, so I trust her opinion). I also gave that friend a gaming laptop as a late birthday gift/early graduation gift today because she doesn't have anything to game on and I didn't really use the laptop much anyways. Plus she's like my favorite person ever and she really deserves it. Unrelated note, I have had an off and on crush on this girl for 2 years. She's always been there for me and she's just an amazing person.

Hey Guys
So... I Have a question / rant / frustrated commenting to do...
WHY THA FUCK DO FIRMWARE TAKE SO LONG TO UPDATE!!!
been configuring my webserver and 2 p2p cameras to access from the outside, and for each click or change can take 1 to 5 minutes to implement...
And then, like 6 or 7 hours latter I notice that everytime the port wasn't associated, a small label in like size8 text shows that port is already in use...
And... Da FUCK??
I'm associating the ports myself... how can port 82, 83, 84, 85, 86, ... be In use?
I have my server in 80, WebDav e another non relevant port, and trying to find open ports for the p2p cams...
Fuck I'll just delete all that services that no one uses and are pre configured, like, emule? napster? FifaPC? WTF? I never played Fifa, don't like socker. KaZaA SERVER? WTF why does this shit comes pre-configured?
Btw I'm writing this while I wait for the router to finish every time :p

Just helped in the little 'Büdchen' (kiosk comes close, but in reality it is more of an little super market) around the corner to Update the firmware of a money bill verifier and counter... As there are new 50 Euro bills.

God. Serial to USB. After running installer and starting firmware update, the owner was a bit frightened as it took so long....

XD

Setup. 30 secs. Firmware. 6 Minutes. XD

Have a Dell desktop that was running Windows 11. Someone tried to revert to Windows 10. Now it will not even post. Anybody experience something this drastic?

I suspect it tried to do some kind of misguided firmware update in the process.

Fucking windows updates...

Went to do a job on a tank in 18 deg F Weather with snow on the ground. One guy brought an ice fishing tent (very nice). This is next to petroleum tank. We got guys on top of tank waiting for me to get data using a Windows 10 lappy.

Lappy comes up and tries to get into bios to do a firmware update. WTF! I reboot and it does it again! Go to look for power adapter as it wont do update without power. Not in bag. It has to have power to do update.

So I drive back to shop (with guys waiting on top of tank) which is 5 miles away. I am pissed. Its snowing and I have to drive slow. I find that adapter. I get back to the tank and plug it in. The AC source (battery based) starts alarming as the lappy takes too much power. Fuck! But somehow it boots Windows without doing firmware update. Fuck you Windows!

I get my job done, but don't fucking trust windows at all. Had this been a field tech he would be pissing his pants. Useless shitty software you have zero control over. Now considering changing their OS to Linux for field work. I am rewriting their software anyway with something can run Windows or Linux.

Anything made by asus is a fucking garbage.

My first asus laptop was eee pc 701. It had only 2 gigabytes “ssd” which was just a flash drive using usb 2.0 inside. Doing this instead of using a proper sata ssd is like using bunch of rats glued to a frisbee instead of roomba vacuum. It displayed “intel 800mhz processor” in settings but this was only the processor’s name string, in fact it was only 640mhz single core. I still managed to install totally stripped version of windows xp to it and play some old games but overall it was horrible. It also heated up as hell.

My second asus laptop was infamous z99h. It had windows vista and was slow as hell right out of the box. Also BOTH hinges broke in just like six months. It was horrible as well. The screen itself broke in a year.

I also used asus rt-series router and it required a restart every day just to deliver some wifi. Don’t you dare tell me to “uPdATe fIrMwArE”, I pay money for the product and I expect it to work right outside the box.

Asus smartphones was also garbage.

So why have asus laptop if you can have a real laptop like MacBook or thinkpad? Why have asus phone if you can have a real smartphone like iPhone or pixel? Why have asus router if you can have ubiquiti?

Asus drivers suck, and all of asus software is just bloatware.

Someone else updated a firmware and noticed that its worse than the older? The worst ia when you try to fix it and it broke another thing.
Too many bugs in a release (yes, a "verified" release)

!rant

My ecig mod (or box how some call it) started to missbehave, it started at random not liking more and more batteries and generally it was good time for replacment. Fast forward, im at shop, and I have few options, i dont want to cheap out becouse I know how it ends, and I want reaible box for longer and I can pay a little more for that.

So there was few quite competetive options, but most of them had build quality i wasnt fan of, some even plastic outter shell, magnets which tend to break off, but their feature list was quite competetive, and there most expensive of all (400 pln +-90ish $) that seller presented me had (seemingly) no features. No menu even. But build quality is solid buttons feel are just better, and it looks like it could survive longer than half a year. Fine, i shell out what it looked missing features for solid build quality.

I go home, rtfm, and wtf? "Before use update firmware with XYZ software". Okay, done. But hmmm what is that?

It has plethoria, absolute TON of customization but from PC program. Hell yeah, that was fucking good choice and seller missed whole selling point of this box. Like literally, he didnt know its best feature. I can go as far as customize entire GUI on that small screen. Its been awhile since I did my last pixelart thingy but monochromatic so not too bad :)

Recently many of us may have seen that viral image of a BSOD in a Ford car, saying the vehicle cannot be driven due to an update failure.
I haven't been able to verify the story in established news sources, so I won't be further commenting on it, specifically.
But the prospects of the very concept are quite... concerning.

Deploying updates and patches to software can be reasonably called *the software industry*. We almost have no V0 software in production nowadays, anywhere (except for some types of firmware).
Thus, as car and other devices become more and more reliant on larger software rather than much shorter onboard firmware, infrastructure for online updates becomes mandatory.
And large scale, major updates for deployed software on many different runtime environments can be messy even on the most stable situations and connections (even k8s makes available rolling updates with tests on cloud infrastructure, so the whole thing won't come crashing down).
Thereby, an update mess on automotive-OS software is a given, we just have to wait for it.

When it comes... it will be a mess. Auto manufacturers will adopt a "move fast and break things" approach, because those who don't will appear to be outcompeted by those who deploy lots of shiny things, very often.
It will lead to mass outages on otherwise dependable transportation - private transportation.
Car owners, the demographic that most strongly overlaps with every other powerful demographic, will put significant pressure on governments to do something about it.
Governments (and I might be wrong here) will likely adapt existing recall implementation laws to apply to automotive OS software updates.
That means having to go to the auto shop every time there is a software update.
If Windows may be used as a reference for update frequency, that means several times per day.
A more reasonable expectation would be once per month.
Still completely impossible for large groups of rural car owners.
That means industry instability due to regulation and shifting demographics, and that could as well affect the rest of the software industry (because laws are pesky like that, rules that apply to cars could easily be used to reign in cloud computing software).

Thus... Please, someone tells me I overlooked something or that I am underestimating the adaptability of the powers at play, because it seems like a storm is on the horizon, straight ahead.

Left my apartment this morning while pressing on "Yes, update firmware of soundsystem". What could possibly go wrong.

Listening to music using my iPhone right now.

I don’t know what my sister did but she trigged the firmware update mode by trying to charge her nexus 5x with my MacBook (USB C) wall charger.

I had to force restart the phone because it was in endless loop. Now everything is fine.

I've had to update some 200 scanning devices on the only available computer old enough to still have the necessary connector. Over a serial connection that was so slow I could've probably written the firmware faster than updating it. It took me 14 hours to update all devices.

The moment when you update your router's firmware.... then reboot!

I hate how I have battery issues with every smartphone/tablet I buy. They do well for 1 week and then I have to buy an additional charger for work because after 5 hours of only lying there it only has 50% which wouldnt be sufficient for 30 minutes car drive (Maps, Spotify, Bluetooth, GPS and mobile data)... Fml. I am tired of batteries. My next phone is going to be a huawei mate 10. Maybe I habe more luck with this one. I dont believe im Samsung anymore.

And anyway why the fuck do they introduce better CPUs more sensors etc whilst Keeping the battery capacity the same.. Instead they introduce fast charge etc. Another reason for me to go away from samsung is the fact they bloat each firmware up, my battery got worst after each system update (even the security ones) and also doing 14 factory resets didnt work. Support is shit. They also integrated Clean Master into the system and an "Antivirus Protection"... Can't get worst.

samsungrant@devrant.com # > submit && exit

I have been working on a long time, low progress project of mine that keeps on giving and giving.

Let's begin like two years ago where I dipped my toes into "more then gigabit" networking thanks to a Linus Techtips video about infiniband.
I had the dream of booting my Workstation from my NAS, a so called diskless setup.

Well, since I run FreeNAS on my Nas , a very nice Freebsd based Nas OS, everything's gonna be good.

In the beginning, there was no infiniband support.
Turns out, you don't need it, since the mellanox CX2 nics can do ETH too.
Yay.
Just took me a few weeks of anger.

So, to be able to boot something over the network, you need firmware that finds the bookable stuff and loads it.
That protocol and firmware is called PXE.
PXE needs a DHCP telling it what to do, and what is where and etc.

Freenas here I come! Installing dnsmasq on the actual freenas install turned out to be not that great of an idea because freenas thinks of itself as being an "appliance" that you don't fiddle with. So things work, until you update/ upgrade when everything will basically be wiped, except what you have done through the ui.
Ok. So I gona use a jail, a container like thing for that.
Everything is great, jail has internet, everything Installs fine, what could go wrong?
Dnsmasq can launch and work, but not as dhcp server. Some thing about permissions.
Turns out, jails have permission like things.
A few days of head scratching later, it has ALL the permissions.
Dnsmasq still can't work as DHCP server though, why you ask?
Because it needs a specific kernelmodule that isn't contained in the jail. Since jails are kind of like a docker container, they run on the same OS kernel, who does not have this module, I'd need to patch the freenas, which is an appliance, so fuck that.

Like a year later, freenas has finally added good VM support, so why not make a VM for the dhcpserver?

Well, about a year ago, I didn't know that the virtual Intel nic is a fucken unstable piece of garbage, crashing nearly any OS at some point.

So that was it for a while again.

Now to the last few weeks.
Finally dnsmasq is running in a freebsd VM with a good and working configuration which is rather simple, if those tutorial fuckers out there would explain shit instead of just telling you to copy, paste and replace X.

Now back to the PXE side.
I'm using iPXE because I have no clue how to boot anything over tftp so iSCSi it is, since that is what I can relate too.
The idea behind iscsi is to fake a SCSI disk over the network. Attached devices appear as if they are actually directly connected to the machine instead of over the network.

iPXE gets a lease from the server, can connect to it, everything is fucken great. Finally.
Except that if it "sanBoots" the iscsi drive, it can't find anything to boot.
Well fuck.
If I attach a Linux live USB over iscsi, it boots, finds grub, and crashes because the live iso isn't configured for network-boot.
But it boots.
So what's so different?

Well iPXE is booted in legacy mode, where as the content of the target is windows 10 in efi mode.
Ffff.

Ok. Can I get iPXE to boot in EFI mode?

Well yes, after like 3 days fiddling with it.
But it only finds the onboard Intel nic instead of the new Mellanox CX3 cards, and can't even connect to the target....

Sooo, I guess my options are as follows.
Either, get PXE efi to work on the network cards directly, its called flexboot and might be able to since I just found some firmware options for that.

Or give up on efi and install windows in legacy mode.
Which isn't that easy when it has to end up on a drive on my nas.