vvv Click on the categories below to see other topic specific pages vvv



Table of Content for public:

More pages: February 2026 November 2025 October 2025 September 2025 April 2025 November 2024 October 2024 September 2024 April 2024 December 2023 November 2023 October 2023 September 2023 May 2023 October 2022 August 2022 June 2022 March 2022 November 2021 February 2021 June 2020 May 2020 March 2020 January 2020 December 2019 August 2019 May 2019 March 2019 November 2018 July 2018 May 2017 September 2016 May 2016 September 2015 May 2015 April 2015 December 2014 July 2014 April 2014 March 2014 October 2013 May 2013 April 2013 January 2013 October 2012 September 2012 July 2012 May 2012 April 2012 December 2011 November 2011 July 2011 April 2011 March 2011 December 2010 November 2010 October 2010 August 2010 July 2010 June 2010 April 2010 March 2010 February 2010 December 2009 November 2009 October 2009 September 2009 August 2009 June 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 June 2008 May 2008 April 2008 March 2008 January 2008 December 2007 November 2007 October 2007 September 2007 May 2007 March 2007 December 2006 November 2006 October 2006 September 2006 August 2006 June 2006 May 2006 February 2006 January 2006 December 2005 November 2005 October 2005 October 2004 August 2004 June 2004 May 2004 March 2004 September 1997 July 1996 September 1993 July 1991 December 1988 December 1985 January 1980





π 2026-02-14 01:01 in Linuxha, Public
I started with a Samsung QN90D which talked perfectly to my Denon AVR3808CI AV receiver. It was able to talk HDMI CEC to it, it knew how to send volume commands directly to the receiver while sending sound over optical fiber given that the receiver only supports HDMI 1.3 CEC but not HDMI 2.0 with eARC (audio return channel).

Unfortuantely the samsung had some ridiculous OS that kept forcing me into making and using a Samsung account for just about anything, including watching youtube, it was terrible. So, I decided to switch to a TCL instead. The TV panel is great, the Google TV OS on it is decent, but:

  • they are using a 32 bit ARM CPU in their top of the line TV. It will stop working in 12 years due to time_t year 2038 overflow because they saved a few dollars on the CPU (android will never support a 64bit time_t migration in 32bit userland because everyone will have or should have switched to 64bit CPUs)
  • the TV refused to use HDMI-CEC as soon as I turned optical output for sound. That same HDMI-CEC did work otherwise
  • Their GoogleTV also helpfully removed infrared support in the remote, so it cannot send IR codes to the receiver even though the remote and googleTV support it.
  • Then I spent 2.5 months with their tech support team. Worst experience ever. They asked me for my feedback, this is what I sent them. Not impressed TCL, this is a new level of amateur hour I had never seen in a company that size. Actually I also forgot to mention that after my TV never getting any update whatsoever, and support saying I should have a later version that wasn't pushing, they sent me one by Email, with a link to their intranet, requiring a microsoft live.com account, and eventually telling me I'm not a TCL intranet user so I can't download it. To this day, they have no idea how to fix it or how to send a file to any customer.

    First, I want to point out that I'm an engineer who has worked with android more than 15 years and filed over 1000 android bugs at google. I have also worked with many tech companies, found bugs in their products and helped them address them.
    I'm sorry to say, but this has been the worst support experience of any major company I've ever dealt with.
    1-2 days after I bought the TV, now 2.5 months ago I immediately called you to report the biggest issue with your software, namely that when using an older AV receiver that supports HDMI 1.3 with CEC, your TV is able to talk CEC to it, but as soon as I switch the TV sound to optical out, it refuses to send CEC commands over the HDMI cable coming from the receiver. This works perfectly with the Samsung TV I had, and fails with your because your engineers not only didn't test this, but did not even understand or envision that this exists and that it should work.
    The first agent, after being confused about how HDMI CEC works, said she would file a bug or a report and someone would get back to me. After a month, no one ever did, and no report was filed, it was just entirely lost.
    Now, what a normal company would have done is filed a bug, sent it to their engineering team for review, and they would decide whether they want to support this use case.
    With you, nothing went anywhere, no one got back to me when they said they would, and it took over 10 phone calls and followups from me to get some traction, often wasting 30 to 60 minutes with agents that simply do not understand that eARC and HDMI CEC are separate and that you can have one without the other. They kept repeating it's impossible to send volume commands over an optical cable, which is totally true, and would not understand that HDMI CEC is separate, is what the volume commands are sent over, and that it works totally fine with both your TV and my denon AVR 3808 receiver, until I turn optical output on and then you disable it.
    I spent over 5H on the phone with mostly agents that were undertrained, were unable to access my ticket in your own system (I should add it took you over 1.5 months before you even filed this ticket after I called multiple times asking why I had no ticket, no Email and no status). Why are your support agents not even able to access the ticket system, what madness is this?
    Emails sent in reply to the ticket went 100% unanswered, so I would have to call to get an agent to ask me questions for 10 to 30 minutes before they would have to call someone else to access the ticket system they can't see, and get what I typed there.
    I also tried to file 2 more bugs, which I think were both ignored, one of them being that Google TV, the HDMI dongle buy from google supports sending IR codes from the remote to the receiver to change volume directly. Once I re-paired my googletv remote with your TV, your TV wiped my remote, removed the IR codes that were working, and you also removed the part of googleTV that supports re-adding IR code to my remote. This is another example of already working functionality that you have removed, and no support agent ever acknowledged this and maybe filing a bug to consider adding it back, would be a good idea.

    Jow that you have wasted 2.5 months of my time before maybe finally filing one bug out of 3 internally, too late for me to return the TV and too long for me to keep waiting for this to ever work, so now I'm going to lose $1000 to $2000 to replace my top of line AV receiver with a newer one that supports eARC because of your unwillingness to support HDMI CEC without eARC or have ever considered how many AV receivers are in the field that do not support eARC and yet support HDMI CEC

    π 2025-11-14 01:01 in Public
    It had been many years since Neptune Project had last come here, it was a special event, and a good excuse to go back to DNA Lounge.

    It was fun to be back and see friends, the set however didn't work as well as the one I remember from 2018: it had some epic tracks that were up to 25 years old, but they were mixed with others that took me off the dream cloud. Still, it was a good time.










    Video Summary:

    π 2025-11-07 01:01 in Computers, Linux, Public
    My 2 main computers have been called magic and moremagic since the late 90's. Most people do not know wy, so here is the story I read back in the 90's, reposted from http://www.catb.org/jargon/html/magic-story.html

    A Story About 'Magic'

    Some years ago, I (GLS) was snooping around in the cabinets that housed the MIT AI Lab's PDP-10, and noticed a little switch glued to the frame of one cabinet. It was obviously a homebrew job, added by one of the lab's hardware hackers (no one knows who).

    You don't touch an unknown switch on a computer without knowing what it does, because you might crash the computer. The switch was labeled in a most unhelpful way. It had two positions, and scrawled in pencil on the metal switch body were the words 'magic' and 'more magic'. The switch was in the 'more magic' position.

    I called another hacker over to look at it. He had never seen the switch before either. Closer examination revealed that the switch had only one wire running to it! The other end of the wire did disappear into the maze of wires inside the computer, but it's a basic fact of electricity that a switch can't do anything unless there are two wires connected to it. This switch had a wire connected on one side and no wire on its other side.

    It was clear that this switch was someone's idea of a silly joke. Convinced by our reasoning that the switch was inoperative, we flipped it. The computer instantly crashed.

    Imagine our utter astonishment. We wrote it off as coincidence, but nevertheless restored the switch to the 'more magic' position before reviving the computer.

    A year later, I told this story to yet another hacker, David Moon as I recall. He clearly doubted my sanity, or suspected me of a supernatural belief in the power of this switch, or perhaps thought I was fooling him with a bogus saga. To prove it to him, I showed him the very switch, still glued to the cabinet frame with only one wire connected to it, still in the 'more magic' position. We scrutinized the switch and its lone connection, and found that the other end of the wire, though connected to the computer wiring, was connected to a ground pin. That clearly made the switch doubly useless: not only was it electrically nonoperative, but it was connected to a place that couldn't affect anything anyway. So we flipped the switch.

    The computer promptly crashed.

    This time we ran for Richard Greenblatt, a long-time MIT hacker, who was close at hand. He had never noticed the switch before, either. He inspected it, concluded it was useless, got some diagonal cutters and diked it out. We then revived the computer and it has run fine ever since.

    We still don't know how the switch crashed the machine. There is a theory that some circuit near the ground pin was marginal, and flipping the switch changed the electrical capacitance enough to upset the circuit as millionth-of-a-second pulses went through it. But we'll never know for sure; all we can really say is that the switch was magic.

    I still have that switch in my basement. Maybe I'm silly, but I usually keep it set on 'more magic'.

    1994: Another explanation of this story has since been offered. Note that the switch body was metal. Suppose that the non-connected side of the switch was connected to the switch body (usually the body is connected to a separate earth lug, but there are exceptions). The body is connected to the computer case, which is, presumably, grounded. Now the circuit ground within the machine isn't necessarily at the same potential as the case ground, so flipping the switch connected the circuit ground to the case ground, causing a voltage drop/jump which reset the machine. This was probably discovered by someone who found out the hard way that there was a potential difference between the two, and who then wired in the switch as a joke.

    π 2025-10-23 01:01 in Computers, Linux, Public
    After 25 years of running on donated hardware, magic.merlins.org aka marc.merlins.org aka ledtranceguy.org finally migrated to a server I built from scratch, for cheap, and was about 60 times more power efficient than the previous server (Dell Poweredge 2950). The Dell was almost 3 times slower since the hardware dated from 2006, and took more than 20 times more power (including the spinning rust drives).

    The more Raspberry Pi specific posts are here:

  • Using Raspberry Pi5 as a Server With Raid1, Btrfs, and Multiple NVME M2 or Sata Drives
  • Using a Raspberry Pi 5 (Rpi5) as a Server With Btrfs, Raid1, Serial Console and Dual NVME/SD Card Recovery Boot
  • Before you see the non professional looking mess of wires I built with 2 rPi5 and reclaimed/recycled drives (I only bought 2 new boot 2TB NVME for boot as I want those flash drives to work a long time), I considered another Dell server I had laying at home, not even sure where from or why. Looking it up, it was a Dell DSS1510 which seems to be a cheaper version of the R430. It's a very professional looking server with redundant power and all, and I did consider it, especially since Dell seems to use capacitors that don't just die years later and take the motherboard down with it.


    room for 8 2.5 Sata flash drives plugged into an unknow raid card
    room for 8 2.5 Sata flash drives plugged into an unknow raid card

    this shows the MB similar to R430 but with lots of stuff missing to save money
    this shows the MB similar to R430 but with lots of stuff missing to save money

    Research showed it was a system from 2016, an upgrade from my existing 2006 server :) but at the same time, do I really want to "upgrade" again to a server that is almost 10 years old? The colo I'm in (via.net, now nextlevel), nicely asked me if I could use less power for the monthly rate they are giving me, and this server can still peak at 200W. Even if it only takes a bit more than 100w, my double rPi5 solution takes less than 30W, probably between 10 and 20W when idle, and that's for 2 computers, giving better high availability and failover


    Good search said:

  • Single-Core Performance: The Raspberry Pi 5 and the Xeon E5-2620 v3 are remarkably close in single-core speed. The Pi 5's modern ARM architecture allows it to match the much older, higher-power Xeon core for single-threaded tasks. Both significantly outperform the ancient Xeon 5140 cores.
  • Multi-Core Performance: The Xeon E5-2620 v3 remains the leader due to its 12 threads. The Raspberry Pi 5 is second, still much faster than the dual Xeon 5140 setup.
  • Power Efficiency: The Raspberry Pi 5 maintains its huge advantage in efficiency, delivering similar single-core performance to the Xeon E5-2620 v3 while using vastly less power.
  • With 2 rPi5 I'm actually faster than the DSS 1510 for maybe 1/10th of the power, so not a bad deal :)

    So here is the end result I built:

  • 2 rPi5 with 32GB pro sdcard that will never be used except for recovery (I don't trust sdcards for long term use)
  • each system is setup to boot from 2TB NVME, top of the line Samsung 990 Pro. This is the one place where I spent money since drives are almost always the weak link long term
  • magic, server #1, has a leftover 2TB Sata M2 plugged via a USB3 adapter which gives very high performance, although it's really just a backup device I can failover and boot from if the NVME were to die (and I can do all this remotely)
  • moremagic, server #2 has 2 1TB Sata drives I had laying around plugged into an M2 Sata controller, allowing 6 drives total (middle of picture below)

  • The 2 things I had to engineer is using each server as a serial console server for the other one, as explained on my Using a Raspberry Pi 5 (Rpi5) as a Server With Btrfs, Raid1, Serial Console and Dual NVME/SD Card Recovery Boot blog.
    The next thing was how to get 5V power for those sata drives. My first solution was just to steal it from the GPIO port:


    But I found a dual sata power cable I had laying around and a 3 pin female plug with the right plastic bits to make it almost impossible to plug backwards (which would likely destroy the drives):

    this
    this

    to replace that
    to replace that


    The last relevant bit is to find those hard to find USB-C power supplies that give 5A on 5V (normally it's 3A max), although you could also get a real 5V power supply and feed the rPi through the GPIO pins, but that would bypass some protections. In the end, my very professional setup that did take many days to build and test, looked like this:


    oops, forgot to protect the back so it doesn't short when touching metal, duct tape to the rescue
    oops, forgot to protect the back so it doesn't short when touching metal, duct tape to the rescue

    the new setup on top fo the existing poweredge server running for a while as recovery/emergency
    the new setup on top fo the existing poweredge server running for a while as recovery/emergency

    And for shits and giggles, still found an original VA Linux server going strong, as a rack spacer :)



    Power Cycling

    Since the rPi5 sadly doesn't have full firmware support over serial (output only, no input to select the boot menu or do anything, really), expecting any kind of BMC functionality like power cycles is of course over optimistic. Due to this lack, I ended up adding a 3.3V controllable relay activatd power outlet that moremagic can toggle via GPIO (so basically moremagic can power cycle magic if it's truly hosed):


    Moremagic is back!

    I had magic and moremagic for many years (if you know the significance of those names, you are an ubergeek and you can Email me to brag, it's well deserved). Moremagic however died in Sept 2024, so I was running with no backup server for over a year, which was not good given that I'm not always home and could have suffered serious downtime if magic had died.

    Now I'm back with 2 servers, on the same network which is not ideal, but they are both redundant filesystem-wise and capable of taking over one another's duties if one were to die (likely the power supply I assume).

    Further reading

  • rescuing/rebuilding magic, and magic back online and live
  • Moremagic v1 died after 18 years of service
  • Magic v3 died, upgrade to V4, Dell Poweredge 2950 and 64bit linux!
  • Magic v5: From Dell Poweredge 2950 to Raspberry Pi 5 (skipping Dell DSS1510)
  • Finishing Upgrade of Year 2000 Linux System From i386 to amd64 to arm64 for Raspberry Pi5 with mailman 2.1.7 for Python 2 (the last 5% that took 70% of the time)
  • ]
  • Exim4 Mailman2 allow insecure tainted data local parts and local part data (what sadly made this migration a lot less fun around the end)
  • π 2025-09-28 01:01 in Outings, Public
    Just like I said last year, I can't call it Bay Area Maker Faire, as it's not really in the bay area anymore, Mare Island is honestly closer to Sacramento than it is from the South Bay. It's a bad location in my opinion, and this year it even drizzled most of the morning, how surprising for a location literally connected to the water... I also couldn't help but notice that the event is indeed smaller than it used to be back when it was in San Mateo (although someone pointed out to me that the sponsorship of bigger companies also brought in money that allowed for a bigger event).
    Anyway, after a longish drive, I ended up arriving 30mn before it opened, they let us in early, and after taking my time seeing everything, I was done by 16:00, 2H before it closed. Big contrast compared to earlier maker faires where I wrote on this blog that I really needed 2 days to see everything... I brought a minimal version of my LED outfit, which people still liked :)


    This year didn't really have anything too exciting compared to last year, to the point that given the very remote location, I'm not sure I'll go back next year.

    All that said, here are the pictures: i01*



    The dark room was probably the most fun location for me :)


    hi Erin :)
    hi Erin :)







    the cuttlefish crew made a new art car this year
    the cuttlefish crew made a new art car this year


    bad ass helmet
    bad ass helmet



    One thing new this year was the Luminarium, which costs $7 extra. You were supposed to reserve timeslots, but the whole thing didn't seem efficient, and was apparently oversold, so it soon had a long line that didn't move much. Mmmhh....






    I had plenty of spare time to see a few talks, not too many caught my eye, but those 3, did:

    a talk on wearable LEDs
    a talk on wearable LEDs

    batteries are often the issue :)
    batteries are often the issue :)

    nice one
    nice one

    the talk by Steve Wozniak was excellent
    the talk by Steve Wozniak was excellent

    The magician that uses physic properties and adds magic on top, did a great job:


    I had a chat with this guy, I was honestly worried about this "plane", given that it was meant to carry a human. The guy is a pilot and did his research. His goal was to fly in ground effect only, which will indeed limit the injuries if anything goes wrong, which it probably will a few times :) If he sticks to that, I wish him luck as long a no one tries to actually fly at altitude with that thing, since if any motor failure happens, this thing is going down and hard (glide ratio of a brick and no rudder to compensate for adverse yaw from a single motor failure):


    Other random things:






    make your own fireworks
    make your own fireworks

    the framework laptop I hope to own one day
    the framework laptop I hope to own one day





    Of course I wasn't the only person with costume:


    big LED earings need a big battery :)
    big LED earings need a big battery :)



    So there you go. Not sure when I'll go back, but here are the previous ones I went to if you're curious:

  • 2009
  • 2012
  • 2013
  • 2015
  • 2016
  • 2017
  • 2024
  • π 2025-09-26 01:01 in Aquariums, Public
    The real name is actually One World Interactive Aquarium:






    Also random fun birds and animals:


    small armadillo, so cute
    small armadillo, so cute


    very well protected
    very well protected

    they also had some larger ones
    they also had some larger ones



    cockatoo
    cockatoo


    wallabies
    wallabies



    And I finished the visit with pretty and friendly Bengal cats:






    More pages: February 2026 November 2025 October 2025 September 2025 April 2025 November 2024 October 2024 September 2024 April 2024 December 2023 November 2023 October 2023 September 2023 May 2023 October 2022 August 2022 June 2022 March 2022 November 2021 February 2021 June 2020 May 2020 March 2020 January 2020 December 2019 August 2019 May 2019 March 2019 November 2018 July 2018 May 2017 September 2016 May 2016 September 2015 May 2015 April 2015 December 2014 July 2014 April 2014 March 2014 October 2013 May 2013 April 2013 January 2013 October 2012 September 2012 July 2012 May 2012 April 2012 December 2011 November 2011 July 2011 April 2011 March 2011 December 2010 November 2010 October 2010 August 2010 July 2010 June 2010 April 2010 March 2010 February 2010 December 2009 November 2009 October 2009 September 2009 August 2009 June 2009 May 2009 April 2009 March 2009 February 2009 January 2009 December 2008 November 2008 October 2008 June 2008 May 2008 April 2008 March 2008 January 2008 December 2007 November 2007 October 2007 September 2007 May 2007 March 2007 December 2006 November 2006 October 2006 September 2006 August 2006 June 2006 May 2006 February 2006 January 2006 December 2005 November 2005 October 2005 October 2004 August 2004 June 2004 May 2004 March 2004 September 1997 July 1996 September 1993 July 1991 December 1988 December 1985 January 1980

    Contact Email