This is the TV console of A330 en route from Amsterdam to US. No movies for the whole plane. However, watching their attempts of rebooting it for an hour and a half was kind of entertaining :-) BTW, the TV remote control had some bugs as well.
Vladimir Vassilevsky DSP and Mixed Signal Design Consultant
It's great when it works, if you get that far. but, its very easy for the average Joe to break. Oh, and new versions are just as fun. You would think it came from Redmond.
Despite the fact that it's running a Linux kernel under the hood, there's nothing on that screen that looks like a generic linux distro, and it's already past the point where Linux itself is booting, and well into the application software startup. Hence, I'm more inclined to blame the group that created the custom software for the airline than the Linux kernel itself. The last flight I was on, they couldn't get the movie running either, but it was just a plain DVD player. My daughter couldn't get her truck to start one day - she was out of gas. We didn't blame the truck's manufacturer for that, either.
Usually when I have trouble getting a Linux box to boot, it turns out to be my own stupid fault, not the software's fault.
So before you go blaming "Linux" for problems, find out what the
*real* cause of the problem is. Otherwise you're just being a scaremonger.
In this application, booting the system off a DVD drive, and having two drives (or two computers), and spare boot DVDs would seem the way to go. Nothing like unwritable media for guaranteeing that things don't get stuffed up after they're working (provided the BIOS settings are left alone).
The failure to find an ext2 filesystem on a loopback device doesn't really sound to me like an application problem.
But I'm not sympathetic to the subject line premise, having spent three days recovering from the mess that occurred after letting Windows XP do one of its overly frequent security updates - it would no longer boot - and my reinstall attempts failed as well due to Windows XP in its pre SP1 form being incapable of driving my present hardware (that took a while to realise, because it kept looking like a HDD problem or motherboard problem).
Bullshit. Solid state drives or regular old hard drives.
That's what boot volumes and the like are for. Connection OS is not from an optical disc.
It was still booting, but the volume could not be found, so it sounds like a failed external storage server has failed.
You come in the group and act overly uneducated in the computing realm, so what is different?
You and your IT dept has never heard of slipstreaming? Jeez, you can even DL slipstreamed discs with the most recent SP built in. Your specialized drivers as well (if needed).
You one of those "re-install everything, hopelessly fail and blame it on Redmond" twits, aren't ya?
Nice... although I don't think any amount of rebooting is going to fix that. :-)
I took a 777 to New Zealand some 4 or so years ago now, and the inflight entertainment system was the pits (I don't know the OS it was running): Very slow to respond, and if you pressed buttons too fast it would freeze up and the flight attendent would have to reset the system for you. At the beginning of the flight they specifically told people to push buttons very deliberately and slowly if they wanted it to work. I kinda wonder if it's been improved yet or not...
/dev/loop0 is a loopback device, i.e. a file treated as a block device.
From the limited information in the picture, I'd guess that everything (including the boot image) is on a file server, and the server's either down or unreachable.
Having this kind of "appliance" log boot errors to the screen is pretty lame, though, as is not simply aborting when the initrd can't be mounted.
The passenger entertainment system isn't built by Airbus. Each airline specifies what they want and it may very well be the same manufacturer that builds systems for some Boeing planes.
--
Paul Hovnanian mailto:Paul@Hovnanian.com
------------------------------------------------------------------
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.