Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Please help. I am a complete Linux newbie. I only just recently escaped the clutches of MS and I now have almost everything working on Ubuntu. The only piece of hardware that doesnt work is my Dazzle DVD recorder. All I want is to be able to use it through TVTime.
I think I'm close in that I have found a C Program em28xx-cards.c and I have changed the lines as explained by Bernd above but what do I do now?
Do I need to copy it to somewhere? how do i compile it?
after you have modified the c file you have to recompile your kernel
and install the new one on your System.
But be carefull ! This is not dangerless for newbie's.
The file has to stay in the original directory (em88xx.c )
on all knewn by myself Linux Distros Kernel compliling should work
become root ( sudo bash or so... )
Change to the kernel source tree:
( evtually followowed by the Kernel Version or its a link on it )
make a Kernelconfigfile:
now it is better to rename your kernel so your still got the original
Kernel as failsave:
type make menuconfig and the go to General Setup and change the "local Version to anything else - your name or System f.e. - so you will get
an Kernel named for you - and the bootloader should give you both Kernels
after compiling and installing.
Leave the Programm selecting exit - until it asks you to write the new
config File accept it to yes.
after this compile the kernel and modules:
now install the Kernel:
now make the modules and install the modules:
now create the initial Ramdisk:
this all could take a while - depending on your Processor am Ram !
( my old PIII 1.2Ghz needs about some hours, my newer C2D needs 20mins )
After this procedre you should have a new Kernel found in /boot and:
new modules in /lib/modules/"kernelsversion"
Now it could could be nessesary to insert the new Kernel on your bootloader ( but on Suse it work automatically ).
Now an Reeboot should give you the self compiled Kernel selectable.
Try to start this Kernel !
NO WARRANTY !!! BE CAREFULL TRY TO GET LIVE HELP IF POSSIBLE !!
Excuse for my English - if anyone found an Error he could drink a Cup of Tee for each Mistake of mine ;-)
I have got a new system - for info it works too on Suse 10.3 x64.
Any Unbuntu Freaks here with better Help for Compiling the Kernel ?
(except for me it's /dev/video1) and I play the results it's just a green screen with no audio. I'm trying to fix the video part before I start working on the audio part. Any idea what I might be doing wrong? I live in the U.S. so I use ntsc. Could that be the difference? And if so what changes to the command do I need to make?
Okay, answered my own question on the video. Had to add norm=ntsc to the command.
With the sound I'm wondering if I can't get it to work because I'm using kde which I believe uses alsa devices. I tried hw.1,0 and hw.2,0 for adevice= but all I get is Unable to open 'hw.2,0': No such file or directory. So maybe I'm not on the right track here. Is there a way to find out what my alsa devices are? BTW, I also tried /dev/dsp and /dev/dsp1 with no luck. I also checked kmix and changed current mixer to DVC100 and made sure the record light was on and that the volume was up. Now I'm officially stuck again lol.
try to find the right device Name of the Audiopart of the dazzle
adevice=/dev/dsp2 worked on my old System - with 2 Soundcards AND the dazzle installed, you have to test on your
System on witch devicename youīll find the dazzle.
I assume it could be /dev/dsp1 because /dev/dsp should be your
emu1K1 - you could also too a look in the virtual direktory /dev
- you should see the possible dsp "files" - the last one should be
the dazzle ( dsp, dsp1, dsp2 os such things ).
It's working now with /dev/dsp1. Sometimes in windows when I'm using the Studio software I have no sound when trying to record so I have to do the safely remove the dazzle then unplug and plug it back in for the sound to come in. I assumed it was a problem with the software but I guess it's a problem with the hardware.
Does your dazzle do this too? If so, does simply unplugging then plugging it back in work for you?
> Sometimes in windows when I'm using the Studio software
- did you mean ^ M$ Windows ?
- i do not use M$ Windows - i have tryed the Dazzle with Windows and my ( old )
Computer wasnīt fast enoug for recording Video with the dazzle - so i figured out
to use it with Linux - and it works absolute fast enougt ( with same Hardware ).
On my new Computer the is only a small Windows for fun inside VirtualBox.
Only Fun is to show People Windows inside a KDE-Window "arrested".
Same Speed Problems on the old Hardware with DVBT-Card - Windows slow and
often crashes - Linux works fine.
So: i could not Help in Windowsproblems...
On Linux ( and on Windows? ) the device name of the Sound-Part of the Dazzle could
differ depending of the Time the Dazzle is connected ( and other Sounddevices ).
So - mostly the Onboard or PCI/PCIE Soundcards are /dev/dsp and the Dazzle as the
second Soundcard ist /dev/dsp1 - if there isnīt any more Soundhardware.
I use the Dazzle only with mencoder - for best Quality, i have tryed out to use it too for
ekiga Videotelephony - but ekiga does not like the Colormode of the Dazzle :-(.
I search for a conversation Tool for this ( small ) Problem - i donīt like the bad Quality
of the Webcams ( hope the Speed of my DSL Account is fast enough ).
I wasn't trying to get help on the windows program Studio, just asking if you had similar problems with linux. But that doesn't matter much. I'm back to post a revised command to capture in xvid format. I'm really new at this so some things may not be perfect and if anyone has suggestions I'd be willing to listen ;-) So here we go:
I've been wading through the man pages to see what all these options mean, but so far I haven't found some of them. So far I'm wondering what the -noskip, -noslices, and -noautoexpand do.
That's all for now. Now I'm going to try to find the best way to capture in mpeg-2 format since that's what I bought the dazzle for in the first place. Doesn't the mpeg-2 encoding happen in the dazzle hardware in the first place? I'd like to not have to re-encode at all if possible. Just dump the stream straight to the hard drive in mpeg-2.
I have to took a look inside the manpages too... .
Many Months ago where i figured out this ;-).
It is possible to save the Videofiles in compressed Codecs ist one (first)
pass - but i havenīt used it because my first ( old ) Computer was to slow
for it - now my new shout be fast enougt.
I will test and Report - an will try to explain the Options of mencoder you
want to knew - but not much time the next Days.
Okay, I finally found a great deal on a Hauppauge card so I'm officially not going to use the dazzle any more. I will keep an eye on this thread though because I'm keeping the dazzle in case anything happens to my new card Good luck everyone!
First of all, thanks bernd and others for providing ways to get this device to go. Unfortunately, it doesn't work for me. (I also have a Mac and their software doesn't work for me either. Argh!)
Following the v4l hack, I get the following error message when I boot up:
em28xx probing error: endpoint is non-ISO endpoint!
No /dev/video* exists, so that's a no-go.
I tried commenting out the if statement in em28xx-video.c that checks for ISO-compliance. It appears to work okay, creating /dev/video0 and /dev/dsp1. But when I run your mencoder line, I get these errors:
Audio capture - buffer 256 blocks of 16384 bytes, skew average from 16 meas.
Using a ring buffer for maximum 318 frames, 251 MB total size.
v4l2: ioctl queue buffer failed: Message too long
v4l2: 0 frames successfully processed, 0 frames dropped.
v4l2: up to 0 video frames buffered.
v4l2: ioctl set mute failed: Bad file descriptor
*** glibc detected *** mencoder: double free or corruption (out): 0x088e8d10 ***
Googling didn't help very much. I've even tried poking at it with libusb..
I'm running Ubuntu Gutsy Gibbon, kernel 2.6.22. Any ideas?
I've read this, but after a long Day of working i have no idea to
solve this for now.
That's OK! Thanks for the timely response -- I see this thread has been alive for a long time now.
Originally Posted by bernd
On Mac it will be the same Procedure - OS-X and up uses
Linux intern - so if it does not work in Linux... .
My Dazzle came with an OS X application, which does not work (crashes on startup). Also, OS X is built on top of FreeBSD, not Linux.. I've given up on trying to make their software work, so I'm now trying things on Linux.
Originally Posted by bernd
Kernel trys to start the dazzle, but the dazzle answeres not as the
Kernel aspected ?
Removing of the ISO-Stuff delayed the Problem to the first Data polling.
Originally Posted by bernd
Dazzle DVC100 ? newer Version ? New Chipssets ? An other Clone ?
Oops, sorry for not mentioning. This is actually a Dazzle DVC170. Since it has the same USB product ID as the Dazzle DVC150, I assume it has an identical interface (though perhaps better compression or fewer bugs).
Originally Posted by bernd
USB-Problems also possible ?
I'm willing to accept I have USB issues on my OS X box (though I can connect to the device using libusb). But quite a few people report the same "non-ISO endpoint" error on Linux.
What are my chances of being able to figure out how to get mpegs off of this Dazzle using libusb? I understand enough of the USB spec, but I don't know how to tell it to begin capturing. I hope it's as simple as:
* bulk_write 1 to tell it to begin capturing using the composite cables
* bulk_read ad nauseam
* bulk_write 0 to tell it to stop capturing
Unfortunately, without being able to run the software, figuring out what to send to the device isn't simple.