http://brainstorm.ubuntu.com/item/4444/
[1304 votes] Solution #1: Auto-generated solution of idea #4444


]]> en-us Thu, 13 Mar 2008 04:56:52 +0000 Fri, 23 Oct 2009 07:58:06 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/4444/ Thu, 13 Mar 2008 05:14:22 +0000 Thu, 13 Mar 2008 05:27:17 +0000
What's wrong with all the websites that are devoted to listing the hardware supported in Linux?]]> Thu, 13 Mar 2008 06:20:34 +0000
I'm proposing we do this in a way which makes the most sense. Java doesn't sound like a bad idea]]> Thu, 13 Mar 2008 07:10:56 +0000
I think some application for Windows that scans their hardware and gives a report is a good idea. Ubuntu has Wubi now, so it's not like a Windows app has never been made relating to Ubuntu.]]> Thu, 13 Mar 2008 08:41:53 +0000
This avoids testing multiple times - useful if the hardware is at family/friends place.

http://brainstorm.ubuntu.com/idea/3471/

]]> Thu, 13 Mar 2008 11:44:04 +0000 It's very nice in theory, but making it work on Windows means a lot of effort, and that effort won't be useful if you aren't running Windows for whatever reason.

I think the LiveCD should come with a hardware checklist. In other words, a list of hardware features, and a test for each. So you can run through the list and check whether you have 3D acceleration, sound, correct resolution graphics, standby/suspend to ram, or whatever else you're interested in.

Scanning for hardware would obviously be very useful for such a checklist, so it could automatically give you a list of what it thinks your hardware can do, and whether Ubuntu can use it. But there are obscure things e.g. support for authentication on wired networks which Ubuntu doesn't support out of the box (not without editting config files), where the user may not realise that it would be a problem, and they would only find out by trying to connect to the internet using a LiveCD.]]> Thu, 13 Mar 2008 15:39:38 +0000 Thu, 13 Mar 2008 19:56:50 +0000 Thu, 13 Mar 2008 20:15:05 +0000
This is aimed at people running other OSes....]]> Fri, 14 Mar 2008 01:17:51 +0000 >"How about running the app just once, which collects hardware data and uploads it to ubuntu. Then receive an email when the hardware is 100% compatible."



i disagree with the email thing, people should get a list of hardware they can buy that works now!, not wait millions of years till their winmodem works....

an ubuntu compatible store is what i propose:
http://brainstorm.ubuntu.com/idea/3575/

]]> Fri, 14 Mar 2008 05:06:02 +0000
So having a utility which scans the hardware, says "this is what I think you have" (can't be sure due to a few vendors mixing up ID numbers) and "this is what I support" would be great. Even better if there was some way of adding "not supported out the box but some reports of getting it to work".]]> Fri, 14 Mar 2008 10:16:23 +0000
Maybe, if it isn't already there, we need an "unsupported hardware" driver so at least such unsupported hardware gets explicitly recognised and flagged. Saves wasting time.]]> Fri, 14 Mar 2008 10:21:46 +0000
But what they just might allow is an online java tool that would check compatibility without having to open the CD drive. Thus, people can safely buy a "ubuntu ready" desktop.

And: sales people would become more and more interested in selling Ubuntu computers. In the end, they might even advise Ubuntu. ]]> Fri, 14 Mar 2008 13:48:35 +0000
With all due respect, I think you are completely wrong to exclude people who don't go out and buy ubuntu-ready hardware. Many people already have bought hardware.

We want to include anyone who is prepared to give ubuntu a try, and letting them know that their hardware is compatible is a great way to give them a good first experience.

Your "us versus them" attitude really isn't helpful.]]> Sun, 16 Mar 2008 18:48:23 +0000 Mon, 17 Mar 2008 21:52:01 +0000
If similar is available for Ubuntu the it will be good to know in advance for hardware compatibility issues,problems of not having drivers and so many,prior to installation.]]> Wed, 30 Apr 2008 08:16:22 +0000 Sat, 02 Aug 2008 15:28:41 +0000 My experience with the live installer -- the isntaller treats you like a no-nothing until its too late. This issue is less with the text based installer (it tells you more what it is doing and erros / issues on the way). The live installer just tells you that it is installing (little more).

For instance with my last installation with 8.04 (due to new main disk) -- wireless was deprecated from normal speed to 1 Mb/s -- why? hardware / driver recognition issue -- was working fine with 7.10. graphic adapter was not recognised and is a clunky vesa/vga or wahtever withs lots of issues and poor performance.

If instalations would start by saying -- this is your list of hw, for this and that there is no support but there are workarounds, try manual alternatives, etc, and then -- proceed or keep your system as is. Information from instalation could then be fed-back to a database of issues.
]]> Wed, 27 Aug 2008 15:59:44 +0000
http://brainstorm.ubuntu.com/idea/13304/]]> Sun, 21 Sep 2008 14:13:00 +0000
How about where these workarounds are known at release time, they are packaged up as -meta scripts and put on the CD? That way, you could have the following process flow..

User slips CD in drive, either boots from it or launches some kind of Wubi-like interface.
"Check hardware" option is offered (or mandatory); this tests not just against the current release, but the last one.
Hardware checker goes into action, testing models and running checks.. reporting back status. Make it nice and graphical - maybe like the Y2K testers that were common in the Wintel world, or like the System Mechanic-type apps that are in that industry.

Outputs something like...

Processor... i686 dual core... FULLY SUPPORTED
Memory.... ... FULLY SUPPORTED
(runs lspci)
Display controller.... ... GOOD/WARNING/UNSUPPORTED"

Big, bold and obvious... Red, amber, green. Windows end-users are used to this... think of the AV products out there.

Make the obvious checks first - display, input devices, Ethernet/Wireless. From here, this could feed into the installer, so correct packages are collected..

AMBER under Ethernet could mean that the installer prompts for a Windows driver, and tries to bring the interface up under ndiswrapper (but scripted)... or using Wubi might mean that the Windows filesystem and Registry could be checked for make/model/components.

In effect, two modes would be needed. One for bare-bones, running off a CD, and the other would be a Wintel app; info could be written to a USB stick or ramdisk before the actual install..

Thoughts?

Macs are probably easier, as there are fewer variants.
]]> Sat, 01 Nov 2008 13:48:20 +0000