Do you see what you're saying here? It means that the proven setup you describe here needs to be attained by the user. This is not something an average user will be able to do and even the tech crowd has many difficulties with it as shown in the other postz here.
And I disagree that it's the same as a clean windows install. See, for a clean install in windows I have a relatively well working to do list: the device manager. Yes I have to download the drivers manually, but IMO the package approach has one fatal flaw when it comes to built-in devices: which one will work for my hardware? If I just try, will removal still work afterwards? Usually it comes down to finding a community tutorial (which are often quite good, I admit). Of course, this difference comes from the fact, that most hardware vendors don't fully support linux. Ubuntu has made lots of progress here in that it tries to install the correct packages itself, but for bleeding edge hardware you're often out of luck.
Here's an idea: How about a webfrontend for that hardware auto configuration, Ubuntu uses? It would map some kind of hardware signature to package name, has some community mode built in as well as the vendor approved configurations (e.g. if distro+vendor mode fails, activate community. which configuration is pulled is being determined by 'votes' (does your sound work now? yes/no).
Do you see what you're saying here? It means that the proven setup you describe here needs to be attained by the user. This is not something an average user will be able to do and even the tech crowd has many difficulties with it as shown in the other postz here.
And I disagree that it's the same as a clean windows install. See, for a clean install in windows I have a relatively well working to do list: the device manager. Yes I have to download the drivers manually, but IMO the package approach has one fatal flaw when it comes to built-in devices: which one will work for my hardware? If I just try, will removal still work afterwards? Usually it comes down to finding a community tutorial (which are often quite good, I admit). Of course, this difference comes from the fact, that most hardware vendors don't fully support linux. Ubuntu has made lots of progress here in that it tries to install the correct packages itself, but for bleeding edge hardware you're often out of luck.
Here's an idea: How about a webfrontend for that hardware auto configuration, Ubuntu uses? It would map some kind of hardware signature to package name, has some community mode built in as well as the vendor approved configurations (e.g. if distro+vendor mode fails, activate community. which configuration is pulled is being determined by 'votes' (does your sound work now? yes/no).