hardware compatibility wiki

http://www.haikuware.com/hardware/

Yes, very nice Karl. The pictures are a nice touch but would prefer listdev info for hardware devices instead (more useful overall). With listdev info can verify if a driver is supposed to support certain hardware. Also, Haiku revision should always be listed because new drivers get added to the OS over time.

Someone (maybe me?) should take some time and quickly go through the drivers in Haiku and state what hardware is supported. This should give a general idea of what should work (has drivers). I may do this later on or maybe someone else wants to do it.

I can look through the driver code and state what hardware (lan, audio & video) has drivers for it. I will look to start in next few days. Next week will be busy for me.

Only issue is that some of these drivers list lots and lots of device ids. Not sure if I should list device ids or just general supported hardware (ie: nvidia driver: tnt1 to Geforce 7950). Showing device ids are very helpful but the list will go very long vertically. Reason why I have not done this type of list sooner. I expect, without device ids about 1/2 page long and with, about 3 pages (or more) long.

example of nvidia device ids (to show how long):
http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/drivers/g...

The work would be about the same for me either way. I will do a General listing, just with the supported hardware models (by name) & manufacturer(s). Just because I can do it more condensed, close to 1/2 page, and should be enough to let people know what drivers are available to them in Haiku.

The ID listing is nice to have too but you see how long it gets. Just for the nvidia driver it looks like maybe a page long. Some other drivers will have the same (ie: Radeon). It could turn into many, many pages if I include IDs.

Video drivers do not matter much because people can always use VESA mode. Network & Audio are the more important ones but I can do them all just to be complete.

I have finished with the graphics drivers. The audio should be kinda quick to do too. The network has 35 drivers and will take some time to go through.

These are the graphics drivers available in Haiku r36031 image.

NOTE: Just because a driver is supposed to support certain hardware (listed below) does not always mean it will. Example, some of the listed Radeon X models do not work with radeon driver. Some listed Intel chipsets do not work with intel_extreme driver.

GRAPHICS

ati: (all models of) 3D RAGE, 3D RAGE2, RAGE128, RAGE128 PRO

intel_extreme: i830GM, i845G, i865G, i855G, i910, i915, i915G, i915GM, i945G, i945GM, i945GME, i965G, i965GM, G33G, Q35G, Q33G, GM45

matrox: G450AGP (G550AGP), G400AGP, G200PCI, G200AGP, G100PCI, G100AGP, MGA 2164 PCI Millennium 2, MGA 2164 AGP Millennium 2, MGA 2064 PCI Millennium 1

neomagic: MagicGraph 128, MagicGraph 128V, MagicGraph 128ZV, MagicGraph 128ZV+, MagicGraph 128XD, MagicMedia 256AV, MagicMedia 256AV+, MagicMedia 256ZX, MagicMedia 256XL+

nvidia: TNT1 to Geforce 7950

radeon: Radeon Original (r100) to Radeon X850 (r481)

s3: (all models of) Trio64, Virge, Trio 3D, Savage3D, ProSavage, Savage, SuperSavage, Twister, ProSavage, Savage2000

vesa: 99% of all video cards out there will work; DEFAULT for video cards without graphics driver

Off your hardware page, http://haikuware.com/hardware , you may want to create a link to a general driver page OR have 3 separate links to driver pages (graphics drivers, audio drivers, network drivers).

Using link(s) to driver page(s) will:
1) Make the work much easier for you (simple & fast)
2) You can just copy what I have and format it to your liking. Sorta like a supported driver matrix page.
3) Just because a driver is supposed to support certain hardware it may not (if outdated or buggy). This leaves the hardware matrix where people can report their actual experience with certain hardware.

People can then click driver link(s) off hardware page to get to the driver page(s) to see if their hardware will be supported and by what driver.

I took shortcut for Radeon, Geforce, etc., because too many models to list in-between. Would have made the list very long. People should know where their model fits in hopefully.

For network, I am looking at taking a shortcut and not list supported hardware. Instead, I may list driver, say WIFI or Wired, BSD or Native. 35 network drivers is lots to look through and not sure if I want to scan through all that code. At least not presently but maybe later on. I will do audio over next few days.

I have suggested something similar for ReactOS without success...

BTW, I believe that the correct way to implement it is to submit the whole machine config to the HW database INSIDE Haiku directly.

Of course we do need a SIS (System Information Software) first.

Hope that inspires.

Audio section finished. I included vendor & device IDs this time. I might do the same for video too, except for Geforce & ATI which list too many cards.

For hda, I could not see any VIA or AMD support - vendor IDs not listed anywhere & not defined (maybe not needed? because other 3 were used for snooping(?)). Can anyone with VIA or AMD *chipset* hda confirm if working and post listdev for audio?

I may not get to networking for 2 or 3 months but I may do something simple to give general idea sooner than that.

Those that do not have audio device listed in Media preferences should install and try with Open Sound System (OSS) for Haiku.

EDITED VERSION 1

So, some years ago now, Haiku was supposed to get this "new device manager-based driver model" which was kinda like a primitive version of the way Windows 95 device management works. In that type of system the claims by a driver to support particular hardware are made explicit, rather than being implied by some nasty "probe" function deep in the driver source code.

This would have made your project a lot easier, but in reality the "new device manager-based driver model" has not replaced the BeOS-like behaviour even in many drivers that are part of the Haiku project itself. So, you're left rummaging through the source code trying to figure out whether this or that hard-coded numeric constant is a PCI vendor ID or whatever.

The situation with Intel HDA is that it's a class standard, like VGA or USB storage.

So in theory you write one driver which implements the software side of the standard according to the documentation, and all conforming hardware will work. The Haiku driver roughly follows this approach, its probe function matches any PCI device which has the class information indicating it implements Intel HDA. Thus probably anyone with a modern Intel HDA device (which is most new laptops and desktops) gets this driver selected.

However, the HDA specification itself represents the codec (the bit that actually converts between PCM data and any form of sound output or input connector) as a separately programmed component. It is often the case that additional code is needed for a particular vendor's codec, or for some applications (ie specific models of computer or sound cards) of that codec. The Haiku code includes some examples of such additional code, covering some very popular devices, but it looks rather less than comprehensive. So for some users the outcome is likely that Haiku's driver seems to work, except that no sound comes out (it is playing, but to some unconnected pins deep inside their laptop, not to the speakers), or the volume controls don't work, or the speakers on their laptop always play sound even with headphones plugged in, that sort of thing.

The codecs have unique hardware identifiers similar to PCI devices, so that the OS need only load driver software for the codecs used in the installed device. e.g. ALSA identifies the codec in this laptop and loads a driver for 'snd-hda-codec-id:14f15051' a Conexant chip. So if Haiku actually had the new Windows 95 style driver model, this information could have been gathered too. But it might not be that helpful, at a certain point you do have to rely on user feedback on whether it really works. The same Conexant chip that works fine in this laptop might be wired up differently in another model, leaving the microphone non-functional by default.

Thanks for the information NoHaikuForMe. I was actually hoping for a simple answer like, hda driver in Haiku currently supports following hardware ..... :-)

I or someone else will have to read the code to figure it out. At least, I was able to do the rest of them. So, that's a start to a general driver database.

In other words it would be great to have the (whole) community feedback on HW/drivers.
Instead, developers use a bug tracker to report problems. If a user is having an issue then they will report it, with listdev output if applicable, and developer will follow up with them. ie: if only 5% of users are having issues then you would only want their listdev info for troubleshooting. Developers only look at those having trouble and reporting it and the rest they assume are working well (with OS or program) and do not care about their info.

I get what you are saying, by having everyones HW info, developers could check if drivers work with other systems too (verify working or not working). Then group the not working (drivers) together in separate categories and try to fix the issues. A good idea but with a couple of concerns to think about.

FWIW, people do submit unsupported hardware to the hardware database. I've added an extra search parameter to allow searching for supported/unsupported hardware:

http://www.haikuware.com/search-dir

You can also enter device IDs in the general search and they'll get queried.

btw, I just poured through the video card sources for Haiku, and added almost all the supported video cards (doing the last one , the radeon branch). I've added all the device IDs and even pictures for the cards. Didn't take as long as I thought... That added about 300 supported video chipsets not including the radeon driver. I'll publish them when I'm done though. I'll probably do everything in audio, network and video. It's a daunting task, but needs to be done.

Now, if someone could find for me (because I've looked but can't find), which cards and device IDs the DVB driver supports, that'd be great!

thx

*edit, also, the network drivers that were imported from FreeBSD don't show the supported devices or IDs in their sources, or maybe didn't look hard enough... anyone know where these are?

*edit2, figured out that you can get the supported network hardware devices from the man pages. you can search for the driver man page here (e.g 'alc' just make sure you have FreeBSD 8 selected):

http://www.freebsd.org/cgi/man.cgi

You can then get the device IDs from here:

http://www.pcidatabase.com

I've finished the video drivers and moved on to network... done 3com, next!

I quickly looked at DVB & found:
http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/drivers/d...

{ 0x14f1, 0x8802, 0x0070, 0x9002, "Hauppauge WinTV-NOVA-T model 928" },

I have not looked if dvb driver is included in Haiku image.

Yes, not working or untested with newest Haiku revision. :-) You're right that they could work still. Can't be sure but you may want to include a note saying they are not part of default Haiku image and may or may not work if built. That way people do not expect them to be already present in Haiku.

:-) The PCMCIA & CF cards will not work. Sorry, just saw you mentioned only PCI.

that all the PCI drivers listed on that man page *should work under Haiku, and have added them in the database... If they don't, people can leave a comment :) as was commented above, people want to know what doesn't work as well. I can just adjust listings to supported or not easily.

Correct, sounds good Karl.

EDIT - minor corrections
EDIT2 - changed content

i've completed the most important drivers.

network, audio & video. (also did bluetooth and webcam).

i couldn't find info for audio>hda and dvb-t supported hardware.

i wrote and explained what i did here:

http://haikuware.com/20100415495/hardware-database-additions

*edit - whoops, @tonestone57 - didn't see your comment above re the dvb-t driver. i'll add that info now.

ok, are there any more of these??

Is it just me or are all the laptops listed discontinued by the manufacturer? I am not trying to be rude but has anyone tried installing on more current model laptops?

Those are actually for AC97 compliant driver (ich). From your link, look at lines 6&7.
6 * Original code : BeOS Driver for Intel ICH AC'97 Link interface
7 * Copyright (c) 2002, Marcus Overhagen <marcus@overhagen.de>

emuxki driver should not load for AC97 devices (what you have listed) because it is meant for SB Live/Audigy/Audigy2 cards. You can test with one of the listed sound cards to confirm. emuxki should only load for the Creative Lab cards.

Not sure how (or if) emuxki driver uses AC97. It also can be found under AC97:
http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/drivers/a...

And under ich driver (which actually should handle these sound cards)
http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/drivers/a...

You will see above italics text on lines 2 to 4 for these files under AC97.

I fixed up the emuxki driver and audigy driver listings and added a warning to the sb16 driver.

If someone else could post on the mailing list where to get a list of supported hardware for the HDA audio driver, that would be appreciated. I don't have an account there.

@mmontalvo - I don't think it should be necessarily surprising that the listings for laptops are outdated. These days, laptops are outdated/discontinued in three-six months. Most of these laptop listings are contributed by normal users.

Thanks Karl for fixing the emuxki driver. Just to let you know. The first listing is Vendor ID with driver name & description.
emuxki driver: Creative Labs (0x1102) SoundBlaster, Audigy 1 & 2 driver
I only point this out because it was grouped together with the other Device ID listings but no matter. Still good.

@mmontalvo
A good idea is to burn LiveCD ISO, boot new laptop from it and check audio & network in Haiku. Video likely will use VESA mode. Karl's hardware matrix depends on users submitting their information to the database to stay updated. Most network cards should work with FreeBSD layer - still good to check. Audio, may or may not work and something to watch out for.

If someone could write an app that gathers the user's hardware configuration information, performs a few tests, and asks to send it over the network to the database,

I think Pieter Panman has already thought about this and has laid some groundwork. Since alpha 1, an app written by him called "Devices", has found it's way into the nightlies. Under the single "Devices" menu item, he has two greyed out options "Report Compatibility" and "Generate System Information" so, I guess he already has this type of functionality in mind. Something like this has been done by Ubuntu linux for some time now by an item called "System Testing" under the "Administration" menu. My guess is that the greatest difficulty will be in making sure that such an app always has a working repository to send the results to.

Alan

An update.

I've changed our hardware database to use an ajax voting system. Registered users can now simply click on a checkmark or x to instantly vote up or down whether a hardware listing is supported or not. The more green checkmarks, the more users found this hardware to work on Haiku.

It's useful, because I added most all the theoretically supported hardware, based on Haiku's drivers, to the database; although the hardware may not be supported in real life - which is where voting comes in :)

http://www.haikuware.com/hardware/