I’d like you, the user, to post in this thread the experiences you have had with hardware. Either hardware that doesn’t work with Linux, or has been difficult. This will help me update the hardware compatibility list. Make it more complete, more accurate, and more detailed.
I ask for as much participation as possible, and as much detail as you can possibly provide. What I will try and do in the following months is buy the hardware and put it in my machine, and see if I can get it working, and if so, how. So we may even see some howto’s and some revisions to existing howto’s.
Please, let’s not turn this into a rant. Let’s just stick to what I am asking for here.
It is supposed to work with the Mantis driver (which isn’t part of the kernel), but I couldn’t get it to work at all with openSUSE 11.2. In previous versions it worked, but Kaffeine choked on the CI/CAM.
For me its been so far so good with hardware on openSUSE 11.2, mostly its fine with whatever I throw at it.
But if I do bump into an issue I will notify you for sure
As has been beaten to death all over the forum, cards that are now “legacy” get no proprietary driver love from ATI/AMD:
Most of these cards are supported under the open source radeon driver, which has better 2D performance, but worse 3D performance. 3D can vary greatly from card to card, and usually requires a bit of tweaking to get decent performance. My experience in configuring my X800 Pro (AGP) under 11.2 has taught me a lot about the entire open source driver stack. I try to share this knowledge with everyone who is unfortunate enough to share my little corner of computing hell.
I think we need an easier way to edit the wiki. I would be glad to update it with each new release for my hardware, but have no idea how to use the wiki editor. I believe this would help tremendously as far as getting people to chip in with the HCL. There was a call to action by oldcpu a while back, but he wound up asking for info and editing it himself.
> Is this a product for Europe? I can’t seem to find this exact one in
> the U.S. As to the terratec site, the closest I can get is ‘TerraTec -
> Products - TV - Cable (DVB-C) - TerraTec Cinergy C PCI HD CI’
> (http://www.terratec.net/en/products/Cinergy_C_PCI_HD_CI_1612.html)
That’s the one. I don’t know if it is a Europe only product.
I agree, which is why I started this thread. One of the things I will be doing is updating the HCL. I have some ideas on this, but I’m not sure how to implement them. Ideas like and easier rating system. Maybe connecting the HCL to smolt. But the bottom line is, two things need to happen.
the HCL needs to be easier to edit
need more participation from users
See it’s kind of a loop here. Perhaps users don’t edit it because it’s not as easy as they’d like. On the other side, the HCL doesn’t get the love it needs cause the users don’t participate.
So let’s keep listing hardware here. At least that’s something for now.
The Hardware Compatibility List (HCL) is known problem for some time, but on the openSUSE wiki is so many open tasks and so little hands that wasn’t possible to do much to fix the problem.
HCL is still the same format as it was initially created with simplifications in some parts introduced by wiki users, like Printers.
In general:
Tables are not easy to navigate and edit, specially for normal wiki user. This limits number of contribution to the list.
They don’t provide a lot of information about hardware.
They don’t have the same look and feel,
Data retrieval is not easy as all relies on browsing menus and tables of content (TOC), or reading table.
HCL entries are mostly disjoint from information how to fix problems with some versions, or configurations.
There is no one of useful entry point for user that is looking for problem solution.
The HCl is in so called Main namespace so wiki search can’t be limited to HCL entries only, which gives crowded search results page.
The HCL is better than nothing, but far from what it can and should be.
Some time ago, I came up with idea to use small and very simple table that is not hard to fill in with data, and it is easy to read, but that will require a lot of work to cleanup current HCL.
Each current table line (row) will be separate table. It should be copied by hand in a new table format, that is easy to create and fill in.
Current pages would have to be split in a lot of smaller pages as new table will take more space on the computer screen, and long scroll to reach the entry that you want to see and edit doesn’t provide simplicity that is needed for inexperienced users.
The navigation should be provided trough Categories and top menu bar, not as subpages and top menu bar, as it is now. Subpages don’t provide top down navigation, just back links ie. bottom up navigation, and that is not only problem with them (renaming creates additional links, title is too long and crowded with redundant content, etc).
So the solution to the problem is to create team of volunteers that will take on HCL alone.
They will analyze current state and come up with different way to collect and present HCL information.
In my humble opinion, ideas presented with a smolt project are good base to think how to deal with HCL.
How it works now:
Smolt client collects data (with user permission),
Post it to the server and give the user password need to edit posted information.
Each hardware entry on the smolts server can be edited to tell other how hardware works, as posted information is in generic state where each device is marked as “unknown”.
There is smolts wiki entry for each device where user can post details and comments, but I’m not sure that information there is easy accessible.
Current problems with smolt client are limited functionality.
It is just a place to review data that will be posted and give password to the user.
Nothing else can be done from client.
Smolt is a good idea, but it needs improvements that will make it useful not only for developers, but for all users.
I do not know if this applies: I installed 11.2 about three weeks ago and the only thing I cannot use is an unsupported scanner: Canon CanoScan FB620U. Therefore I installed VirtualBox.
Pivoting monitors (ie those that can be turned to a vertical/portrait rather than horizontal/landscape orientation) cannot be made to work as second monitors with NVIDIA dualhead cards. Not without giving up one or the other of the following anyway: 1. a single desktop across both monitors (Twinview doesn’t support rotation of only one monitor), or 2. 3D acceleration (Xinerama doesn’t support compositing). XRandR 1.2 would solve the problem if the proprietary NVIDIA driver supported it, but it doesn’t.
Well, I still need makes and models. “All of them” doesn’t help.
It might well be a software issue, but with out the proper information, I won’t be able to track it down. If it’s drivers, and you mentioned nVidia, then that leads me to believe Xorg and nVidia.
Do you need a list of all pivoting LCD panels on the market???
No need to “track it down”. Track down what? I’ve described the issue, it’s well known, and only NVIDIA can do anything about it.
It’s a software problem I suppose but you asked which hardware doesn’t work properly and most hardware problems are due to driver issues 