Re: Well actually @Spearchucker
In my experience, the various Ubuntu releases work on everything I've put it on with few or no problems.
In the last 8 years since I started using it, I've put it on lots of Thinkpads and other laptops, netbooks, and desktop systems, and while I won't say that I've never had problems, none of them have been show-stoppers.
OK, when I first used my eeePC 701, I had wireless problems until the slightly strange Atheros chipset gained a Linux driver. My Thinkpad T30 does not reset the sound correctly after suspend, and the Mobile Radeon graphics adapter is too old to work with Compiz well, and I came across a wireless card for which there was no Linux support on a Shuttle XPS (which, incidental, did not work in Windows very well either).
I suspect that your Vaio must have some very specific hardware in it, and only works on Windows because you have a system restore image prepared by Sony that contains the right drivers. I would be interested in seeing how well you managed to get it working with a retail windows install disk, and what would not work.
Windows users think that their systems 'just work', but this is mainly because the PC manufacturer has taken the necessary background steps of identifying the drivers and building a bundle of Windows and drivers specifically for their systems. If they went to the same lengths for Linux, it would be the same.
What is amazing in my view is that a single build (one CD, not even a DVD) of, say, Ubuntu will 'just work' on a huge number of different systems without all of the behind the scenes customisations that happen for Windows, because they are done for you.
One of the problems is that Windows drivers are specific to a particular instance of hardware, so a Atheros card from say Netgear would not work with the drivers supplied by Belkin for a card with the same chipset, and often not even with the driver for another card from the same supplier with the same chipset.
Linux is different here, because its drivers are largely manufacturer agnostic. It identifies something like an Atheros chipset, and it configures the driver regardless of the manufacturer (OK, I know Atheros is an old chipset not used much now, but it's the one that came to mind first).
Occasionally, you will come across some hardware for which the PCI or USB ID's are not in the database, so the module code cannot identify the required driver correctly, but this becomes less and less frequent as time goes by, and is usually fixed for what must be regarded as non-mainstream hardware (if it were mainstream, the ID's would be in the database) after a little Googling. Not everyone's forte, I accept, but you cant expect the distro maintainers to be omnipotent!