Opened 15 years ago
Closed 12 years ago
#4447 closed enhancement (invalid)
Driver blacklist
| Reported by: | MrSunshine | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/Boot Loader | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
As ive got some kinda borked harware in my laptop, a si-3112 chip that wont work with the haiku si-3112 driver and a ati xpress 200M that wont work with the haiku ati driver ive got some huge booting problems with haiku alpha cd, so i was thinking, why not give a driver blacklist option in the boot menu ?
say i need to disable the si-3112 and ati driver to get it booted to fix the problem for my laptop, i just enter "si-3112 ati" into a text field in the boot menu, as it boots when it starts to load drivers, it will check against the blacklist and skip the drivers with these names, ridding me of my problem, giving me the ability to be able to go into the system directories and permanently (delete) the malfunctioning drivers.
Linux has this ability at boot time if you got malfunctioning hardware etc so you need to disable some drivers/driver combinations to make it boot so why should not haiku ? Im sure there are more people then me with problems with drivers/hw =)
Change History (3)
comment:1 by , 12 years ago
| Version: | R1/pre-alpha1 → R1/Development |
|---|
comment:2 by , 12 years ago
comment:3 by , 12 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Yes, but on the next boot he thinks to disable the problematic drivers. I'm just not sure how you could know which ones, and even their names to disable them.
Anyway, as long as this ticket was open, I would like to close it as invalid: we have the safe-mode for exactly that reason, and it pretty much covers the issue by not starting optional servers like the media server (ie. no one will try to open the audio driver), and by forcing the app_server to stay with VESA, ie. the ati driver wouldn't load either then.
If your disk controller doesn't work, you're stuck anyway.
That would be nice to have, but not easy to implement. IIUC, what you are talking about is a function of the desktop-environment/window-manager that happens after the OS has already loaded. On many modern *nix distros, it can seems like the OS and DE are one in the same, but they are not. A *nix system OS would most likely load fine. The graphical environment is completely separate, and GNOME and KDE have the benefit of a much larger developer base to have created such a useful fallback function that you describe.
Haiku does not have that separation of OS and DE. How is Haiku supposed to know that the driver does not work? You can't know until you try to boot Haiku and have problems. Then you are stuck, Haiku doesn't boot.