7 ms·
Remembering Larry Finger, who made Linux wireless work
- ohmyiv 2y agoRIP. Thanks for the work on wifi drivers. NDISWrapper was a pain.
- toomuchtodo 2y agohttps://lwn.net/ml/all/77997185-86a6-41c5-af7a-74e4e9064437@lwfinger.net/ https://lwn.net/ml/all/77997185-86a6-41c5-af7a-74e4e9064437@... https://hkfuneralhome.com/larry-finger/ https://hkfuneralhome.com/larry-finger/
- bombcar 2y agohttps://lore.kernel.org/linux-wireless/20240625103929.1332926-1-kvalo@kernel.org/ https://lore.kernel.org/linux-wireless/20240625103929.133292... This has some serious GNU-Pratchett vibes - http://www.gnuterrypratchett.com http://www.gnuterrypratchett.com and nice to see
- tree666 2y ago:(
- kapilvt 2y agoArstechnica has a solid write up. He did a lot of work making linux wifi and driver ecosystem significantly better. https://arstechnica.com/gadgets/2024/06/larry-finger-linux-wireless-hero-was-a-persistent-patient-coder-and-mentor/ https://arstechnica.com/gadgets/2024/06/larry-finger-linux-w... I remember cursing ndis wrappers and Broadcom wifi ecosystem a long time ago, Larry helped fixed that, and mentored many others along the way. quote from the arstechnica article "In a 2023 Quora response to someone asking if someone without "any formal training in computer science" can "contribute something substantial" to Linux, Finger writes, "I think that I have." Finger links to the stats for the 6.4 kernel, showing 172,346 lines of his code in it, roughly 0.5% of the total."
- dang 2y ago(This was originally from https://news.ycombinator.com/item?id=40770724 https://news.ycombinator.com/item?id=40770724 but we merged those comments hither)
- haneefmubarak 2y agodang, could this merit a black bar in remembrance and honor?
- xbar 2y agoKudos to Ars Technica for this piece.
- xwiz 2y agoSorry to hear it. His work was a key part of my entry into the software world.
- nashashmi 2y agoI always think of him every week or so for his support of a belkin wireless card FG… I had as a broke college student in 2005 trying to get linux working on my machine. His driver worked better than the belkin supported windows driver. What do I think about? Why the hell did he volunteer his post work hours trying to do this menial job hardware thing. Did he not have a family or something? He did. And today they lost him.
- camkego 2y agoIt seems he was the best in the world at broad Linux Wi-Fi driver development. That’s quite a valuable accomplishment. Thanks, Larry Finger.
- freedomben 2y agoSame, if not for Larry I may not still be a Linux user. Unsung hero indeed.
- foobarian 2y ago> What do I think about? Why the hell did he volunteer his post work hours trying to do this menial job hardware thing. Did he not have a family or something? I wondered the same, imagining some 40-something FTE frustrated with bureaucratic work projects and with a couple young kids. Guess what, this guy passed at 84! Which means the driver work happened in his 60+ years. I will be lucky if I can remember my name at that age. :-)
- neogodless 2y agoSee also: https://lwn.net/Articles/979419/ https://lwn.net/Articles/979419/ https://www.phoronix.com/news/Larry-Finger-Linux-Wireless https://www.phoronix.com/news/Larry-Finger-Linux-Wireless https://arstechnica.com/gadgets/2024/06/larry-finger-linux-wireless-hero-was-a-persistent-patient-coder-and-mentor/ https://arstechnica.com/gadgets/2024/06/larry-finger-linux-w...
- dang 2y agoThanks - I've changed the URL to the last one of those (from https://www.developer-tech.com/news/2024/jun/24/linux-community-mourns-loss-wifi-driver-expert/ https://www.developer-tech.com/news/2024/jun/24/linux-commun...) because it seems to have the most background.
- freedomben 2y agoI know it violates the general guidelines to change the headline, but the new title doesn't make clear that he has passed away. I imagine there are a lot of people who might overlook it without that key part in the headline.
- dang 2y agoOk, I've grafted on a piece of the subtitle that makes it clearer.
- freedomben 2y agoawesome, looks great, thanks so much!
- loa_in_ 2y ago> will benefit users for years to come /years/decades/s
- kirth_gersen 2y agoWhat a hero. Rest in peace.
- freedomben 2y agoWow, this is sad news indeed for the world at large, but also me personally. I'm suddenly in deep regret for having procrastinated reaching out the thank him. He doesn't know this, but he was somewhat of a mentor for me. In the early 00s I bought a laptop that had an RTL 8188 CE card in it that ran awful under Linux. I forked his driver and made a number of changes to it and eventually got my wifi working really well (by doing things that could never be upstreamed due to legal/regulatory restrictions). Over the years I rebased often and reviewed the changes, and learned a lot from watching his code. It took a bit of getting used to, but a certain amount of beauty and appreciation emerged. One thing was very clear: This man was doing a lot of the work to keep the ship together. Even just keeping the driver compilable with each kernel release often took some non-trivial refactoring, which he did reliably and well. Larry, you will be missed my friend. RIP. If you are waiting to reach out to somebody, don't wait too long or it may suddenly be too late. The years can slip by in a flash.
- maCDzP 2y agoThis is what makes me come to HN every single day.
- nanna 2y agoThis is what makes me come here every single minute my anti-procastination setting allows me to.
- refulgentis 2y agoThis is what makes me delete my anti-procrastination setting and quit my job to spend more time here.
- freedomben 2y agoFound a small typo, but it's too late to edit the original. I meant early 2010s (not early 00s)
- exe34 2y ago> Even just keeping the driver compilable with each kernel release often took some non-trivial refactoring, I realise that the kernel contributors themselves are mostly volunteers and as such can just do what they want, and writers of non-upstreamed drivers will need to get used to chasing trunk, but to me this sort of thing seems like a waste of human talent. once something works, it should never not work again. it seems to me that despite all the layers of cruft that we've accumulated over the decades haven't really helped much with this, in fact they probably mean more work just to stay still.
- deleted 2y ago[deleted]
- AndrewKemendo 2y ago[flagged]
- smlavine 2y agoYour comment is rude and unhelpful.
- AndrewKemendo 2y agoI thought I wrote it nicely but I guess not I can’t think of a more powerful engineering endorsement than saying he did a Herculean effort to manually keep it all working Basically we’re all screwed now cause he was holding the whole thing up
- arp242 2y agoThis is a memorial thread, not a "rant about Linux WiFi thread". You're acting like a complete moron and asshole. This comment is the polite and sanitized version of what I would actually like to say.
- freedomben 2y agoWrong and terrible timing. There's a hell of a lot more to "Linux WiFi" than just the driver code that Larry maintained. I definitely wouldn't rule out hardware issues. I've seen race conditions in driver code before, but it's quite rare and Larry was really good at identifying and elimianting those. If your laptop is workable, pop the cover and make sure the wifi card connection is fully seated. Also check the dmesg logs early and often after boot and make note of anything related to wifi. Chances are good that if it's not a hardware issue, there's something in there to help point you in the right direction.
- dfox 2y agoProbably the most common reason for the integrated wifi card becoming “non-deterministically non-recognized” is that the OEM fucked up the rf-kill in that there are slight differences between what the EC firmware and ACPI expect and how the hardware is implemented (missing pull-ups, EMI induced into high-impedance logic trace somewhere…). Anecdotally, on any laptop that I have seen with these kinds of issues (basically every new Intel laptop I bought between 2017 and 2020, which includes lot of weird no-name tablet-in-laptop-formfactor crap, but also ThinkPad X270), it progresses such that the WLAN becomes unusable in Windows but you would hardly even notice in Linux, where it just works. [edit: obviously comparing Windows to Windows is nonsense, it works in _Linux_]
- Teknomancer 2y agoLegendary. Larry lead a full life. He mentored many hundreds over the years and his legacy will live on in those who he taught and inspired.
- mejare777 2y ago[flagged]
- tomrod 2y agoThis guy deserves the black bar, certainly.
- 01acheru 2y agoI came here to say the same, this guy pushed Linux desktop adoption forward like few others by himself and just for passion. RIP
- dbolgheroni 2y agoBesides Larry Finger, another Linux kernel developer passed away this week: https://lwn.net/Articles/979617/ https://lwn.net/Articles/979617/
- rob74 2y agoThis was posted here too, but unfortunately didn't gain a lot of traction (maybe because the title doesn't mention who he was?): https://news.ycombinator.com/item?id=40815468 https://news.ycombinator.com/item?id=40815468
- ginko 2y agoPeople keep making fun of the year of the linux desktop, but for me that year was distinctly around 2007 when wifi started working mostly painlessly on my thinkpad.
- renewiltord 2y agoWiFi in the late 2000s early 2010s was a crazy place, man. Looking at the code it's wild how much he contributed to the process. Damn.
- dougg3 2y agoLarry’s work on maintaining a bunch of Realtek’s vendor drivers on GitHub was huge for a lot of the community. Even today these forks often work much better than the mainline drivers. He will be missed! As others said, he was a huge inspiration.
- matheusmoreira 2y ago> Broadcom provided no code for its gear > so Finger helped reverse-engineer the necessary specs by manually dumping and reading hardware registers I really wanted to leave this quote here for all to see. The badassery of this act should not be underestimated. I've done a little bit of work along those lines. Reverse engineering my laptop's features, writing my own free software to drive them from inside Linux, emailing the manufacturer asking for documentation and receiving user help pages. It was mostly USB stuff, the most well documented interface imaginable, and it was still hard. I simply cannot fathom how he reverse engineered this Wi-Fi stuff. That's just a huge inspiration for me, I hope I can get near his level some day. Thank you so much for your work and RIP.
- racked 2y agoYou might enjoy this series of articles about writing a Wi-Fi driver using reverse engineering techniques: https://zeus.ugent.be/blog/23-24/open-source-esp32-wifi-mac/ https://zeus.ugent.be/blog/23-24/open-source-esp32-wifi-mac/
- matheusmoreira 2y agoYes I really enjoyed reading that article, thank you so much. I'm really looking forward to seeing a brave soul show up to try and reverse engineer those 50 thousand hardware initialization memory accesses. That sort of thing is just incredibly difficult. I'd really enjoy reading about that too. In my case I intercepted USB communications with wireshark and tried to make sense of the packets. I'd use the proprietary manufacturer app, capture what got sent over USB and correlate the packets to hardware behavior. Mapped out all the functions that way. There were hundreds of them but mercifully most of those were the same command but with different parameters. The result was this totally magical software which sends buffers containing seemingly random numbers to the hardware and somehow that makes things happen. /* Clevo Control Center * Effects * Wireshark Leftover Capture Data * * 0 Wave cc00040000007f * 1 Breathe cc0a000000007f * 2 Scan cc000a0000007f * 3 Blink cc0b000000007f * 4 Random cc000900000000 * 5 Ripple cc070000000000 * 6 Snake cc000b00000053 * * There seems to be no pattern to it. Does the value of the last byte matter? * My keyboard apparently doesn't support the ripple effect, * even though it is present in the Clevo Control Center interface. */ Mapping out 50 thousand memory accesses though? Whoever achieves that has my respect and my attention.
- Version467 2y ago> Larry Finger, and fish, from his Quora profile. The inclusion of the fish in the tagline made me smile. There’s an innocence to the sentence that captures the image really well.
- fragmede 2y agodamn. this one guy changed the world. if not for him, Linux would not have had those wireless drivers, and the downstream effects of younger teens being able to use Linux and then contribute to that ecosystem and and and. .
- throwaway423342 2y agoRest in peace. I'm still rocking Linux on my MacBook Pro from 2012 which has a bcm nic in it. Thank you.
- hbogert 2y agoIf that is the same as the macbook air's of that year, than good luck to ya. The chipsets of that year are a horrible mess. Even in macos is it was finicky with a 1+ year bug that wifi would not come up automatically if your macbook went to sleep with bluetooth on.
- franga2000 2y agoThe name didn't ring a bell, until I saw his username in the CREDITS commit - lwfinger! That username, along with "hadess" even more so, will be burnt into my memory forever. Compiling their drivers for the RTL8723BS card was the first time I got my hands dirty with the inner-workings of Linux, eventually getting a terrible little Intel Baytrail convertible to run Linux almost perfectly. I ended up posting a tutorial on the process to get Ubuntu working on it, which, assuming by the 80 start and long-running discussion below, helped a good number of people to keep using their win8.1 e-waste for quite some time.
- never_inline 2y agoI used one of his GitHub driver repos to make wireless work on a realtek driver. Rest in peace.
- racl101 2y agoLegendary.
- rmbyrro 2y agoWe need Larry Finger for hibernation. Please don't get me started on suspend-mode low energy consumption. It hasn't been true for any device I've owned. Perhaps yours, fine, but my anecdotal experiences and acquaintances' show you're in a minority.
- costco 2y agoI would've never used Linux and probably wouldn't have got into programming without https://github.com/lwfinger/rtl8723be https://github.com/lwfinger/rtl8723be (it took like five or six years to get mainlined). He's a hero.