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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
well there doesn't look like there's anything wrong there. xawtv 3.86 came out yesterday, try upgrading for the sake of it. segfaults are very rarely down to somethign like that, normally complaining about glibc upgrades or something.
This is xawtv-3.86, running on Linux/i686 (2.4.20)
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 13688)]
0x40303554 in __nvsym17122 () from /usr/lib/libGL.so.1
1 dl-debug.c: No such file or directory.
The program is running. Exit anyway? (y or n) y
nv? As in nvidia? Could it possibly be my nvidia driver? I didn't have this video card in the last computer.
does appear to be nvidia though. i'd assume that that means you have installed an RPM rather than compiling the driver by source. i can't imagine that somethign like that would happen if the nv driver was compiled natively. personally i never had any trouble with xawtv / nvidia, but seeing as i'm boring i stopped using the nvidia drivers a while back and don't mess with opengl games now.
Nvidia doesn't provide the source for their driver, and the nv driver that comes with many distributions is inherently flawed. While it's flawed in favor of XawTV, if you upgrade to the improved Nvidia driver (which delivers better opengl performance for gaming and video), then I suggest you dump XawTV. It doesn't seem to me that it's being supported very well anymore,w hich is the risk you take with open source. I switched to TVTime http://tvtime.sourceforge.net/, which is beautiful. It has a sleek OSD, but it is lacking in GUI interfaces. You have to remember keybindings. At the very least, you can just use the keypad to enter in the channels, and yes it does have LIRC support. It also solved the fulscreen issue, where I couldn't get a true fullscreen out of XawTV.