Bus 001 Device 003: ID 055d:9001 Samsung Electro-Mechanics Co. MPC-C30 AnyCam Premium for Notebooks [pwc]
But pwc driver in 2.6.6 kernel is not included because it's considered broken :-( According to the information from the author it's not really broken but he refused to change anything for now: http://www.smcc.demon.nl/webcam/
I hope this will be fixed soon (maybe with the next kernel release).
This driver is generally for philips webcams. When it works ok I'll try to add it to the wiki.
BTW I've just edited your howto to change small typo in the first url to sourceforge.net (qce.ga to qce-ga).
]]>thydian wrote:Please add your experiences to the Wiki though as a Howto...I have a webcam sitting around here somewhere that would be fun to use...
Please please please do this!
Dusty
I added a howto in the wiki. It's pretty poor now, but I'll fix more later. I think some drivers should be added to the official respitories.
]]>It wouldn't work, as dp sayd, cause of the dog being so loud. But I didn't know that then... :-D
]]>(psst you need win95B for USB support )
( ... but it will only work, if your dog is quiet and the computer is standing upside-down and you have a nice wallpaper --- all important parameters for win95B :-) ... )
]]>This is just personal opinion but: I find Linux more enjoyable and easier to configure than Windows. Windows is great for doing stuff automatically, but when something doesn't work, you are totally stuck. Documentation for more difficult problems is harder to find in Windows. Usually the manual says "press ok and it should..." but doesn't say what to do if you press ok and it throws a cryptic error. At the worst, (and this is a pretty bad worst) with Linux, if hardware doesn't work, you write a device driver for it (something I'm not about to attempt, mind you). With Windows, if it doesn't work you take it back to the store and they say "it should work but..."
I guess the point is you might have more luck with first time chances on Windows, but if it doesn't work first shot, Linux will get you up and running faster.
I had so much trouble getting USB support under Windows 95... compiled my first Linux kernel and my digital camera worked... ah the memories!
Dusty
]]>Please add your experiences to the Wiki though as a Howto...I have a webcam sitting around here somewhere that would be fun to use...
Please please please do this!
Dusty
]]>If you want to send the developers all the hardware you want supported, we can support it.
]]>As far as webmeeting/netmeeting/whatever: Either you need to forward some ports, or you connect to the other's pc, or it all goes via some central server (like most IM stuff...).
]]>That's where, for example, I learned how to get my simple USB keydrive up and running. As simple as it was to initialize in the end, I certainly didn't know the two or three required modules starting out.
Since I don't know how much insight an Arch maintainer has into the world of hardware they support I don't know how empowered they will be to come up with a "comprehensive" list or document. Maybe it's easier than I think...I'll leave it to someone more knowledgeable than myself to answer that.
Please add your experiences to the Wiki though as a Howto...I have a webcam sitting around here somewhere that would be fun to use...
In terms of autoconfiguring, I'm torn. Although I don't like the stress of spending days Googling and the like for tidbits of info to get a configuration right, I also don't like the mystery behind automated tools that sometimes do and sometimes don't work.
Hmmm...it didn't work...why? What did the automated tool do? Which files did it modify? Where are they? Everytime I migrate to a distro that configures stuff for me, I always find myself leaving sometime later to go back to a distro that doesn't. Bah...
Someday in the future when those tools do work 99% of the time, you can bet I'll take advantage though!
Good luck!
]]>Next, my normal user didn't have permission to the webcam... After researching devfsd.conf, I found a way to add normal user permissions to the /dev/video0.
I got gnomemeeting from pacman, and was ready to start a webmeeting, but even after opening all the ports on my router, it didn't work. I then gave up and booted into Windows.
When I booted into windows, Windows automatically detected and configured my webcam. I went into NetMeeting, placed my call... and boom! Everything worked!
I'm not saying that everything should just be "Boom!" and configured... But its seems a waste of time to go through a bunch of that mess just to get a webcam configured...
I think it would be a good idea to get a compilation of drivers and put them in packages... webcam-drivers, scanner-drivers, and other devices. Also in these drivers it should be asked at the end of installation if you would like for pacman to do required configuration (like adding the devfsd.conf line). It's not manditory, no one is forcing you to do it. Also to go along with this is a list of hardware devices on the documentation, what modules they need, what packages they're in, and any other configuration notes.
So, all one would have to do to configure a device is..
1) Go to the docs and search for the device
2) Install neccesary packages
3) Read extra configuration instructions on docs
4) Enjoy!
As Arch Linux as it is now, if I get another peice of hardware, I can't count on being able to configure it and use it within a day.
I know that Arch Linux is not a newbie distro. I can configure all the hardware if I give myself enough time, but some of this work I feel is uncessary. What are your thoughts on this? Flames, questions, suggestions, whatever, post them. Thanks!
]]>