Written by andremachado the 26 Mar 10 at 23:09.

The idea to solve all this issues is: when Ubuntu boots, it will load only the essential services to raise graphical interace and a new service what will be connected with HAL and/or DBUS. This will made boot faster. When user connect or turn on a new hardware, like a printer, a bluetooth dongle or a webcam, this new service will detect this hardware and load the appropriate service to support it. When this hardware is disconnected or turned off, the new service will remove the service previously loaded from memory.

User will can configure this resource for: create an exception list, decide if a service will not be stopped once what it was started or a time to wait what it be stopped after hardware removal, as well as enable or disable this new resource.

UPDATED: For non-related hardware services, the new service would can start they when they're necessary too. For example: if a user has Apache and MySQL installed in your machine, this two services can start stopped and when system receives a network ping or request to 127.0.0.1, from Firefox, for example, these services would be started.

The idea to solve all this issues is: when Ubuntu boots, it will load only the essential services to raise graphical interace and a new service what will be connected with HAL and/or DBUS. This will made boot faster. When user connect or turn on a new hardware, like a printer, a bluetooth dongle or a webcam, this new service will detect this hardware and load the appropriate service to support it. When this hardware is disconnected or turned off, the new service will remove the service previously loaded from memory. User will can configure this resource for: create an exception list, decide if a service will not be stopped once what it was started or a time to wait what it be stopped after hardware removal, as well as enable or disable this new resource. UPDATED: For non-related hardware services, the new service would can start they when they're necessary too. For example: if a user has Apache and MySQL installed in your machine, this two services can start stopped and when system receives a network ping or request to 127.0.0.1, from Firefox, for example, these services would be started.

Written by mauricep the 1 Apr 10 at 20:36.

Whilst moving from Ubuntu loading all hardware services on boot to a user-configurable hardware services load configuration, the amateur user will likely not bother. As an alternative default, Ubuntu could intelligently select which hardware services to load on boot:

- Hardware services used with high frequency are loaded on boot
- Hardware services used with medium frequency are loaded after boot with a delay (e.g. one minute), or whenever system is first "idle".
- Hardware resource used rarely are loaded as needed (as proposed in other solution).

Whilst moving from Ubuntu loading all hardware services on boot to a user-configurable hardware services load configuration, the amateur user will likely not bother. As an alternative default, Ubuntu could intelligently select which hardware services to load on boot: - Hardware services used with high frequency are loaded on boot - Hardware services used with medium frequency are loaded after boot with a delay (e.g. one minute), or whenever system is first "idle". - Hardware resource used rarely are loaded as needed (as proposed in other solution).

Written by ibizatunes the 26 Oct 09 at 12:15.

I think that when running the hardware wizard you should be able to save the file to a location of your choice, and then upload to launchpad later

I think that when running the hardware wizard you should be able to save the file to a location of your choice, and then upload to launchpad later

Written by andrija the 22 Oct 10 at 17:13.

Create a collection of relatively simple post-install scripts that fix common issues based on detected hardware.

For example, if the script matches the output of lspci with the Lenovo U350 sound card, then execute

sudo apt-add-repository ppa:ubuntu-audio-dev/ppa && sudo apt-get update && sudo apt-get install linux-alsa-driver-modules-$(uname -r)

in order to prevent sound coming out from the speakers when headphones are plugged in (what an annoying bug).

Another example is the installation of Broadcom wireless drivers. Some BCM43xx chipsets do not work well with open source drivers. In my case, they do not work at all. I had to wade through that horrible Ubuntu "developer wiki" (read the heading page, the wiki isn't meant for finding help: https://wiki.ubuntu.com/) to figure out that I had to install three packages already on the CD. This wasted me hours, because there were many possible configurations and I wasn't sure which one to use so I had to try several (with steps including downloading data on another computer and transferring to this one because I had no Internet access). What should have happened is that Ubuntu should have figured out which driver I need (this is well documented, see http://forums.fedoraforum.org/showthread.php?t=239922, which has a freaking flow-chard of what to use), and then told me:

Create a collection of relatively simple post-install scripts that fix common issues based on detected hardware. For example, if the script matches the output of lspci with the Lenovo U350 sound card, then execute sudo apt-add-repository ppa:ubuntu-audio-dev/ppa && sudo apt-get update && sudo apt-get install linux-alsa-driver-modules-$(uname -r) in order to prevent sound coming out from the speakers when headphones are plugged in (what an annoying bug). Another example is the installation of Broadcom wireless drivers. Some BCM43xx chipsets do not work well with open source drivers. In my case, they do not work at all. I had to wade through that horrible Ubuntu "developer wiki" (read the heading page, the wiki isn't meant for finding help: https://wiki.ubuntu.com/) to figure out that I had to install three packages already on the CD. This wasted me hours, because there were many possible configurations and I wasn't sure which one to use so I had to try several (with steps including downloading data on another computer and transferring to this one because I had no Internet access). What should have happened is that Ubuntu should have figured out which driver I need (this is well documented, see http://forums.fedoraforum.org/showthread.php?t=239922, which has a freaking flow-chard of what to use), and then told me: "We need to use non-free drivers, or else you won't have Internet. Clicking this button will install three packages on the CD for you, because you shouldn't dig through random files and documentation to figure out which. If this doesn't work, you'll be offered to revert to your previous configuration." Finally, a lot of these common bugs (that you can expect simply by doing lspci and uname -r to match hardware and kernel) are fixable by adding just one option to one text file in /etc/something.conf. So a fix of the form cat option snd-hda-intel model="ideapad" >> /etc/alsa.conf (or whatever) can save the user a lot of time, nerves and (from a business perspective, most importantly) can make the user NOT switch away from Ubuntu.

Written by andrija the 22 Oct 10 at 22:56.

It might bt simpler, but less satisfying, to create a website where users can post their solutions in a form that asks for

1. problem
2. hardware/software configuration (uname -r, lspci line for affected hardware, ubuntu version)
3. fix

instead of posting individuals solutions to blogs

It might bt simpler, but less satisfying, to create a website where users can post their solutions in a form that asks for 1. problem 2. hardware/software configuration (uname -r, lspci line for affected hardware, ubuntu version) 3. fix instead of posting individuals solutions to blogs

Written by placid the 29 Oct 10 at 12:48.

The community provides fixes on a standardized website as in solution 2. Solutions can be verified, and "all in one" scripts/packages can be provided which apply all the necessary fixes automatically.

Hardware solutions should be DIScouraged from the forums and moved to the fix site, as information in forums is often hard to find or out of date.

This would be integrated into Ubuntu something like so:

On first install, after certain updates, or when clicking on a "help my computer isn't working" button Ubuntu asks:

"Your computer appears to be a *auto detected model*. Is this correct?" (Give option to manually define the computer model)

Check on the community site for possible issues if this isn't an officially supported machine. Display the issues inside the installer (no switching to the web browser). Give the option to install+run the "fix all" package if its available.

There is a trusted connection between Ubuntu and the community site and only verified scripts/packages can be automatically installed, so you can't accidentally break your computer. Just in case a "revert" function is included.

The community provides fixes on a standardized website as in solution 2. Solutions can be verified, and "all in one" scripts/packages can be provided which apply all the necessary fixes automatically. Hardware solutions should be DIScouraged from the forums and moved to the fix site, as information in forums is often hard to find or out of date. This would be integrated into Ubuntu something like so: On first install, after certain updates, or when clicking on a "help my computer isn't working" button Ubuntu asks: "Your computer appears to be a *auto detected model*. Is this correct?" (Give option to manually define the computer model) Check on the community site for possible issues if this isn't an officially supported machine. Display the issues inside the installer (no switching to the web browser). Give the option to install+run the "fix all" package if its available. There is a trusted connection between Ubuntu and the community site and only verified scripts/packages can be automatically installed, so you can't accidentally break your computer. Just in case a "revert" function is included. Result: you have fully working hardware without ever having to search the internet or even open your browser! The user always has the option to skip or to install whatever fixes manually from the wiki (important as only a limited number of fixes would likely be verified). The "skip" could be used to give feedback by giving several options: "These issues don't affect me" (which would flag the solution in the wiki for people to check that it still affects that hardware), "These are not the solutions i'm looking for" (the wiki doesn't have the needed fix, also flagged), or simply "Not now". After a successful auto-fix install Ubuntu follows the community site for updates. Power-users could have the option of registering their computer model and testing new updates before they go out to all users. This is particularly relevant for laptops which have well defined combinations of hardware for given models. A strictly organized and moderated wiki with a nice interface is crucial!

Written by Darwin Survivor the 5 Dec 10 at 21:14.

I think most of the issues brought here can be solved by creating "affects" tags. Any hardware that is affected by the bug will be added to the bug report as a "tag", then the bugtracker could have an automatically generated page for each tag so that you could search for "Acer Aspire xx2023" and get a list of all hardware-related bugs on one page.

You would also be able to search by hardware specifically such as "Intel 4500HD Graphics".

This could be made even easier by sorting them by manufacturer (similar to how the linux-printer-driver website does).

Right now the closest thing you can do is a manual search for your model number or hardware type, which brings a lot of false-positives as people are simply posting their model number if they are simply having a "similar" bug.

This would greatly improve the system and make it MUCH easier for people who just bought a machine (or are looking to buy one) to see what problems there may be and how they can be fixed (or if a fix is even available).

I think most of the issues brought here can be solved by creating "affects" tags. Any hardware that is affected by the bug will be added to the bug report as a "tag", then the bugtracker could have an automatically generated page for each tag so that you could search for "Acer Aspire xx2023" and get a list of all hardware-related bugs on one page. You would also be able to search by hardware specifically such as "Intel 4500HD Graphics". This could be made even easier by sorting them by manufacturer (similar to how the linux-printer-driver website does). Right now the closest thing you can do is a manual search for your model number or hardware type, which brings a lot of false-positives as people are simply posting their model number if they are simply having a "similar" bug. This would greatly improve the system and make it MUCH easier for people who just bought a machine (or are looking to buy one) to see what problems there may be and how they can be fixed (or if a fix is even available).

Written by ibizatunes the 12 Nov 08 at 13:33.

Ubuntu Brainstorm was updated in January 2009. Since the idea #15540 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #15540 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by nitrofurano the 9 May 09 at 11:31.

People know how to make sub-distros based on Ubuntu, and knows well how distros like PuppyLinux, DamnSmallLinux, TinyCore, TinyLinux, and others, works better on low-end and old hardware than Xubuntu, could help on the development of a kind of Tinybuntu which can be as appropriated as PuppyLinux, DamnSmallLinux, TinyCore, TinyLinux, and others are. This Tinybuntu should be able to be installed on machines such as having only 32mb of ram, low hard-disk space, and relativelly slow (below 200mhz-monocore), just like actual distros like PuppyLinux, DamnSmallLinux, TinyCore, TinyLinux, and others used to run fine. Would be great Ubuntu being part of this too!

People know how to make sub-distros based on Ubuntu, and knows well how distros like PuppyLinux, DamnSmallLinux, TinyCore, TinyLinux, and others, works better on low-end and old hardware than Xubuntu, could help on the development of a kind of Tinybuntu which can be as appropriated as PuppyLinux, DamnSmallLinux, TinyCore, TinyLinux, and others are. This Tinybuntu should be able to be installed on machines such as having only 32mb of ram, low hard-disk space, and relativelly slow (below 200mhz-monocore), just like actual distros like PuppyLinux, DamnSmallLinux, TinyCore, TinyLinux, and others used to run fine. Would be great Ubuntu being part of this too!

Written by Ferk the 10 May 09 at 08:22.

Why create yet another Ubuntu flavor and divide maintenance and development resources?
Xubuntu is intended to have a particular focus on low memory footprint. If it's not archiving this goal then this should be fixed.

Perhaps removing some daemons running in the background, investigating the causes and trying to find alternatives.

Why create yet another Ubuntu flavor and divide maintenance and development resources? Xubuntu is intended to have a particular focus on low memory footprint. If it's not archiving this goal then this should be fixed. Perhaps removing some daemons running in the background, investigating the causes and trying to find alternatives.

Written by corbintechboy the 14 May 09 at 21:51.

Have an option on install that would give only a base install. Then from the command line you could apt-get any package you may need.

Have an option on install that would give only a base install. Then from the command line you could apt-get any package you may need.

Written by daas88 the 28 May 09 at 02:35.

It's a ubuntu-based distro that uses the lxde desktop environment, so it's very very light on resources. It only needs an easier installation method, like a live cd or so. There might be other options but that one's more ubuntu-like.

http://u-lite.org/

It's a ubuntu-based distro that uses the lxde desktop environment, so it's very very light on resources. It only needs an easier installation method, like a live cd or so. There might be other options but that one's more ubuntu-like. http://u-lite.org/