My thoughts on Slackware, life and everything

Category: Hardware (Page 3 of 5)

Short maintenance downtime window coming up

My “Alien Pastures” blog will be down for two or three hours on Thursday, 27 July 2017, starting around 1700 UTC.

The blog runs on a server in the Teklinks datacenter, and that will be replaced by new hardware. Since this involves driving to the datacenter and doing physical work (thanks Robby Workman!) the slightly longer-than-usual downtime is needed.

Additionally, the following services that are running on the same hardware, will also be down:

The http, ftp, and git services of SlackBuilds.org will not be affected, as those are hosted on a different machine.

Cheers, Eric

taper.alienbase.nl mirror will lose rsync access

For the sixth time in just 5 days I had do a system_reset on my virtual machine which runs “taper.alienbase.nl” as well as “docs.slackware.com“. The virtual machine is crashing under the load that is put on it by demanding rsync processes. According to my pal who donated the use of this VM to me for free, the rsync download rate is at a continuous 100 Mbit/sec for most of the time. This is apparently too much for the server, as well as for my pal who had not anticipated this kind of bandwidth consumption. He has been paying quite a bit of extra money for the excess bandwidth during the past months.

I do not like it when someone loses money because of me, so drastic measures are required.

As of tomorrow (monday 15 Feb 2016) I will kill the rsync access to taper.alienbase.nl.

HTTP access will still be allowed, so people who configured slackpkg to download from my server will still be served.

I hope that this will put my pal at ease again, and also prevent the server from crashing.

Apologies for the inconvenience this causes to people who use rsync to keep their local mirrors up to date. I will try to find another location to host my SlackBuild repository as well as the multilib and KDE (ktown) repositories. The downtime of this VM caused downtime for docs.slackware.com as well which I think is unacceptible.

Eric

Raspberry Pi and Broadcom: a birthday present

475px-Raspberry_Pi_Logo.svg Two years ago (on 29 february 2012), the Raspberry Pi Model B went on sale. More than 2.5 million Raspberry Pis have been sold to date! An amazing number, considering that the original goal was to equip british school kids with cheap hardware for Computer Science education.

Thanks to these enormous sales numbers, the Raspberry Pi Foundation (a not-for-profit organisation) was able to sponsor several Open Source projects writing code which can be used with the hardware (XBMC, libav and many others).

And now, two years later, there is a new surprise. The Raspberry Pi has been developed as “open” as possible, however there was a part of the hardware which was not open: the VideoCore IV 3d graphics core on the Broadcom application processor for which only a “binary blob” exists and which is addressed by a thin layer of Open Source graphics kerneldriver. This is not unusual – most if not all of today’s ARM-based mobile hardware has a closed-source graphics stack and no public register-level documentation of the hardware.

This is changing now! As announced on their blog, Broadcom has decided to open up their VideoCore IV 3d core to accompany the two-year anniversary of the Raspberry Pi. The code of the graphics stack has been open-sourced under a liberal 3-clause BSD license and  it’s accompanied by complete register-level documentation for the graphics engine. This is unique for the ARM hardware platform as far as I know.

If you are an experienced hacker/programmer, you may be up to the challenge posed by the Raspberry Pi Foundation: to port the open-sourced graphics stack (for the BCM21553) to the Raspberry Pi’s processor (BCM2835). And they will pay you a bounty of $10,000 if you are the first person to demonstrate satisfactorily that you can successfully run Quake III at a playable framerate on Raspberry Pi using your ported drivers.

How cool is that? Of course I hope it will be a Slackware hacker who will reap this reward.

Have fun! Eric

mirror & wiki server temporarily down

The host machine which is running the virtual machine “taper.alienbase.nl” and “docs.slackware.com” has malfunctioned.

According to the story told by that server’s owner, the power cord got loose during the re-build of the RAID array after the guy replaced a failing hard drive.

After a power-on the RAID volume refused to mount…

It looks like the host server may be up and running at the end of the day, if the owner manages to recover from the partition corruption. In that case, my mirror server taper.alienbase.nl and the Slackware Documentatoin Project’s Wiki docs.slackware.com may be online a little later, provided that I can access the server and start the Virtual Machine.

In the worst case, the server will not be able to recover and I have to find a location where I can restore my daily backup of the Wiki content. It’s just bad co-incidence that I will travel to India tomorrow early morning. I have no idea how fast I would be able to arrange for a new host, fix the DNS entries, setup apache and start the Wiki… for the docs.slackware.com hostname I need to involve Pat.

More news later.

Eric

Update Fri Nov 23 18:55:29 UTC 2012 –

The server is back up! The server admin fixed it, no data was lost.

My Panasonic Lumix DMC-LX5

Back in february I bought the camera I had had my eyes on for over a year. It was a bit too expensive to consider it seriously, but then suddenly there was a discount of 75 euros and I grabbed the opportunity. A Panasonic DMC-LX5 was finally mine.

I had been using a relatively cheap Sony CyberShot DSC-P10 camera for years, after my first digital compact, a Canon PowerShot, broke down with the infamous E18 error (which earned its own web site http://e18error.com because so many people suffered by it). The Sony camera was meant to be temporary because I did not have money for a good replacement… but the money never came. I needed a better camera badly. What I really wanted was better light sensitivity and better wide-angle.

The LX-5 offers all of that and much more, with its f/2.0 24mm Leica lens, fast power-on and AF, full metal body and a battery that should last 400 photos on a single charge. Read more about its features, strengths and weaknesses (if any) at the PhotographyBLOG. I realize that this camera is not “new”, and lots of other types have entered the market and are competing with it, but I wanted a camera that is easy to carry, enables me to point-and-shoot while keeping the possibility for manual overrides, is sturdy and offers excellent picture quality in low-light circumstances. I don’t care for replaceable lenses or GPS geo-tagging, or superzoom lenses.

I discussed cameras with collegues and friends who shoot a lot of pictures, and the outcome was that I would best by either the LX5 or a Canon PowerShot S95… the latter because it has quite similar specs to the LX5 but also because there is custom firmware for the Canon line which lets you do a whole lot more with your camera: the Canon Hack Development Kit (CHDK).

In the end I decided against the Canon, the main reason being resentment about the E18 error which killed my first digital camera 1 day after end of warranty.

Why did it still take a year to buy the camera? I guess it was the price point. But I was following several photography related blogs and my enthousiasm was fueled by viewing the results of shooting with a LX5. That basically pushed me that final step. Special mention to Juha Haataja’s Light Scrape blog! I was fascinated by Juha’s stills, his comments about his daily encounters with the world and his overall philosophy with regard to what makes a good picture.

I took the camera with me (of course) during my holiday in Brittany, France. Back home and behind a computer I could evaluate the results. At first, I stuck mostly to the camera’s defaults (using Intelligent Auto or “iA”) because I still needed to get acquainted to it (for some reason, I never took the time to get to know the LX5 during those first months that I owned it – too busy with Slackware I guess).  But I quickly began to experiment, with the User Manual as a guide… luckily I downloaded that to my E-reader.

I don’t know if it is the result of my fiddling with the manual controls (or even fiddling too little) but I feel that some of the JPEGs, especially those taken in bright sunlight, seem a bit “ovet-processed”. Or perhaps that is just because I have been working with a mediocre camera for so long. I discussed this with Pat (who owns a Canon PowerShot and uses CHDK) and he suggested that I should try shooting JPEG+RAW and look what difference it would make when I do the image post-processing on my computer. So, that is what I am going to do in the next couple of weeks. I compiled an updated package of RAWtherapee, an open source RAW editor with support for the LX5’s RAW image format and I am going to play with that once I have shot a couple of RAW images.. If anyone knows equivalent or better alternatives to RAWtherapee (free software!) I would like to hear from you.

Here’s a couple of sample images from that first holiday batch (all JPEG). Let me state that I am very happy with the camera. The LX5 has a good grip, and the controls are easy to operate. The camera “radiates” quality. I could shoot pictures in awkward positions without fear of letting it slip. Its low light qualities are great, and I am curious to find out about all the possibilities of the manual controls. So far, it has enabled me to take pictures in situations where I would have failed with the old Sony. Despite my earlier comment about possible JPEG over-processing, I am impressed with the quality of the pictures.

Tell me what you thnk of them. Can the camera do better? Can I do better?

Eric

 

 

 

« Older posts Newer posts »

© 2025 Alien Pastures

Theme by Anders NorenUp ↑