Dando la chapa

El que no llora no mama, está más claro que el agua.

Hace una semana un friki postea en los foros de Ubuntu que ha estado haciendo pruebas y ha llegado a la conclusión de que un modelo de placa base tiene código específico para no funcionar bien en Linux. Además no sigue un estandar que dice seguir. Total que se pone en contacto con el fabricante, le explica el problema y el fabricante por supuesto pasa de su culo 100 pueblos. El cruce de mails no tiene desperdicio:

*** Foxconn:

Dear Ryan:

This board was never certified for Linux. It is only certified for Vista. See URL below. So please test under Vista. Does this issue also occured under Vista or Winxp?

*** Friki:

I’ve taken the liberty of filing the report in kernel.org, Red Hat, and Canonical’s Ubuntu bug tracking systems, and posting the contents of my kernel error log on my blog, which is in the first several results if you Google search “Foxconn G33M” or “Foxconn G33M-s”, “Foxconn Linux”, etc, as well as prominently in other search formats, so hopefully this will save other people from a bad purchase, and hopefully kernel.org can work around your broken BIOS in 2.6.26, as I understand that kernel is more forgiving of poorly written BIOSes built for Windows.

I’ve already gotten several dozen hits on those pages, so you guys are only hurting yourselves in the long run, by using bad BIOS ROMs, as people like me are quite vocal when dealing with a bad product.

*** Foxconn:

Making idle treats is not going to solve anything. As already stated this model has not been certified under Linux nor supported.

As you are unhappy with the product- using a non-support operating system nor certified, please contact your reseller for a refund.

*** Friki:

Yeah, well, I allege that you guys thoroughly suck. Learn how to write a BIOS before you go selling hardware with falsified specs.

*** Foxconn:

Dear Ryan, Stop sending us these!!!

Total, que como no hay más cosas que alegren Slashdot por las mañanas, allí que apareció claro: MoBo Manufacturer Foxconn Refuses To Support Linux.

Entonces a algún ingeniero de la compañía se le cae el sandwich de la boca una mañana cuando se entera por Slashdot de que un cliente suyo con Linux tiene problemas y está montando el 2 de Mayo en Internet. Y tiene toda la pinta de que el monkey de soporte para lo único que le pagan es para leer lo que pone en la etiqueta: “no certificado para Linux, funciona con Microsoft” en lugar de preocuparse de mandarle un mail al ingeniero a ver qué se puede hacer.

Resultado: una semana más tarde problema resuelto. El ingeniero sin sandwich se va a los foros de Ubuntu donde empezó todo y pide perdon:

And here I want to say Thank you to all the linux enthusiasts. From this case, Ryan and all of you gave us a lesson. And also as our plan, we will take more time on Linux OS testing.

Me quedo con este comentario de Slashdot:

So, you think it would have been fixed if there had not been angry, almost rabid, users? You know, the ones you refer to as “crazy zealots”?

I don’t believe so. I believe the issue would have been ignored, and Linux would have been patched in some obscene manner to “work around” the issue. Giving a bad reputation to Linux; “it doesn’t work — what kind of fucking shit is THIS?”. Hurting the reputations of many developers.

Sometimes, the only sane response is to be angry and rabid.

Educa al friki

Sunday, August 3rd, 2008 at 8:36 pm || TAGS: bugs, linux || Post RSS || Trackback