Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
03-18-2003, 07:19 PM
|
#1
|
Member
Registered: Apr 2002
Location: D.C - USA
Distribution: slackware-current
Posts: 488
Rep:
|
xawtv seg fault
I am trying to get xawtv running on my machine. I had it working on my old machine, but it just wants to be stubborn now ...
Quote:
lackluster@lackluster:~/software/xawtv-3.85/console$ xawtv
This is xawtv-3.85, running on Linux/i686 (2.4.20)
Segmentation fault
|
I am using xawtv 3.85 on slackware 8.1 kernel 2.4.20. Has anyone else encountered this?
v4l-conf:
Quote:
lackluster@lackluster:~$ v4l-conf
v4l-conf: using X11 display :0.0
dga: version 2.0
mode: 1024x768, depth=24, bpp=32, bpl=4096, base=0xe0000000
/dev/video0 [v4l2]: ioctl VIDIOC_QUERYCAP: Invalid argument
/dev/video0 [v4l]: configuration done
|
|
|
|
03-19-2003, 03:19 AM
|
#2
|
Senior Member
Registered: May 2001
Location: Left Coast - Canada
Distribution: s l a c k w a r e
Posts: 2,731
Rep:
|
What output do you get when you load the bttv drivers for your card? Erm.. I guess you should also post info about which tv card you're using.
|
|
|
03-19-2003, 06:08 PM
|
#3
|
Member
Registered: Apr 2002
Location: D.C - USA
Distribution: slackware-current
Posts: 488
Original Poster
Rep:
|
my dmesg:
Quote:
i2c-core.o: i2c core module
i2c-algo-bit.o: i2c bit algorithm module
bttv: driver version 0.7.96 loaded
bttv: using 4 buffers with 2080k (8320k total) for capture
bttv: Host bridge is VIA Technologies, Inc. VT8367 [KT266]
bttv: Bt8xx card found (0).
bttv0: Bt878 (rev 17) at 00:0b.0, irq: 5, latency: 32, mmio: 0xef000000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: BT878(AVerMedia TVPhone) [card=6,insmod option]
i2c-core.o: adapter bt848 #0 registered as adapter 0.
bttv0: using tuner=-1
bttv0: i2c: checking for MSP34xx @ 0x80... not found
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips: tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54 (PV951)
i2c-core.o: driver generic i2c audio driver registered.
i2c-core.o: driver i2c TV tuner driver registered.
tuner: probing bt848 #0 i2c adapter [id=0x10005]
tuner: chip found @ 0xc2
bttv0: i2c attach [client=Temic NTSC (4032 FY5),ok]
i2c-core.o: client [Temic NTSC (4032 FY5)] registered to adapter [bt848 #0](pos. 0).
bttv0: registered device video0
bttv0: registered device vbi0
|
Sorry, it's a Hauppage WinTV card (the kind everyone has).
|
|
|
03-19-2003, 06:15 PM
|
#4
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
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.
|
|
|
03-19-2003, 06:18 PM
|
#5
|
Senior Member
Registered: May 2001
Location: Left Coast - Canada
Distribution: s l a c k w a r e
Posts: 2,731
Rep:
|
Is this a source build?
|
|
|
03-19-2003, 07:26 PM
|
#6
|
Member
Registered: Apr 2002
Location: D.C - USA
Distribution: slackware-current
Posts: 488
Original Poster
Rep:
|
This is xawtv-3.86, running on Linux/i686 (2.4.20)
Segmentation fault
ACK! Source build, yeah. Maybe it would help to compile with debugging?
|
|
|
03-19-2003, 07:43 PM
|
#7
|
Member
Registered: Apr 2002
Location: D.C - USA
Distribution: slackware-current
Posts: 488
Original Poster
Rep:
|
Check this out :
Quote:
Starting program: /usr/local/bin/xawtv
(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 13688)]
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
(gdb) list
1 dl-debug.c: No such file or directory.
in dl-debug.c
(gdb) quit
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.
|
|
|
03-23-2003, 05:02 AM
|
#8
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417
|
what was that..? you're double posting..? tsk...
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.
|
|
|
08-18-2003, 12:12 AM
|
#9
|
LQ Newbie
Registered: Aug 2003
Posts: 3
Rep:
|
Its Nvidia
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.
|
|
|
All times are GMT -5. The time now is 08:25 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|