Ühel kenal päeval (reede, 27. veebruar 2004 23:53) kirjutas ellie philippen:

Thanks for the Yast help, and kjots works to a degree. Sometimes a new book will strangely dissapear. At startup from command line the following errors: Ellie@linux:~/dc> kjots QLayout "unnamed" added to QButtonGroup "ButtonGroup_2", which already has a layout kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. kdecore (KAction): WARNING: KAction::plugAccel(): call to deprecated action. I am close to uninstalling- but -any one have a better idea? Not crazy about knotes but it looks stable. Thanks

I use for my jots TuxCards (comes with SuSE too, package tuxcards). It is at least stable and can do some rtf-style formatting. ain

Anyone using this? I have the 878 chip and all, plus the hauppauge site says this model should just boot up fine with SuSE 6.x. But I have 9.0 and it doesn't run. I even updated the bttv and tv4linux drivers from ftp://ftp.suse.com/pub/people/kraxel/9.0-i386/src/ Card works fine under Win98SE. Under SuSE 9.0 it seems to boot fine, but no applications find it, plus it interferes with the Ethernet driver. Normal Ethernet works fine, but shutdown hangs at ETH0, plus running /sbin/ifconfig or ethtools hangs the session. My only option is to pull the card to run SuSE 9.0 gracefully. The PC is an old IBM Aptiva with K6, the ENet is a Netgear with NatSemi/Tulip driver. Any suggestions? Thanks - Lynn

On Sunday 29 February 2004 10:07, Örn Hansen wrote:

söndag 29 februari 2004 08:39 skrev Lynn Linse:

...

Anyone using this? I have the 878 chip and all, plus the hauppauge site says this model should just boot up fine with SuSE 6.x. But I have 9.0 and it doesn't run. I even updated the bttv and tv4linux drivers from ftp://ftp.suse.com/pub/people/kraxel/9.0-i386/src/

Yeah, well ... I've got the hauppauge WinTV as well. What I have to do, is I have to:

# modprobe bttv

<snip> Same here except that I place "modprobe bttv" into "/etc/boot/local" so that WinTV is always /dev/video0 whether the webcam is plugged in, or not. WinTV works well. Geoff

söndag 29 februari 2004 12:06 skrev Geoff Horn:

<snip>

Same here except that I place "modprobe bttv" into "/etc/boot/local" so that WinTV is always /dev/video0 whether the webcam is plugged in, or not. WinTV works well.

You mean, /etc/init.d/boot.local ... I should've thought of that. Simplifies things.

Geoff

On Thursday 04 March 2004 12:59, Lynn Linse wrote:

Kelly Fulks wrote:

...

On Sunday 29 February 2004 01:39, Lynn Linse wrote:

...

Anyone using this? I have the 878 chip and all, plus the hauppauge site says this model should just boot up fine with SuSE 6.x. But I have 9.0 and it doesn't run. I even updated the bttv and tv4linux drivers from ftp://ftp.suse.com/pub/people/kraxel/9.0-i386/src/

This is still not solved - anyone can suggest how to STOP SuSE 9.0 from auto-starting bttv so in the future I can try manual init with modprobe? For now I'll need to run Win98SE to watch the WinTV card.

1) to the IRQ sharing question, net card is on IRQ 10 and WinTV is on 11. The var log below mentions sharing IRQ11 between device 00:0f.0 and 00:0f.1, but BOTH are on the Hauppauge card ('TV Card' and 'Multi-Media Controller' respectively). a hardware info dump from YaST shows no other driver on IRQ 11

2) to the "just run 'modprobe bttv'" suggestion - that's not the answer. bttv is already being auto-loaded during boot - here is the /var/logs/messages trace from a normal boot: Mar 4 10:18:54 kernel: Linux video capture interface: v1.00 Mar 4 10:18:54 kernel: i2c-core.o: i2c core module version 2.8.0 (20030714) Mar 4 10:18:54 kernel: bttv: driver version 0.7.104 loaded Mar 4 10:18:54 kernel: bttv: using 4 buffers with 2080k (8320k total) for capture Mar 4 10:18:54 kernel: bttv: Host bridge is ALi Corporation. [ALi] M1541 Mar 4 10:18:54 kernel: bttv: Bt8xx card found (0). Mar 4 10:18:54 kernel: PCI: Found IRQ 11 for device 00:0f.0 Mar 4 10:18:54 kernel: PCI: Sharing IRQ 11 with 00:0f.1 Mar 4 10:18:54 kernel: bttv0: Bt878 (rev 17) at 00:0f.0, irq: 11, latency: 32, mmio: 0x80500000 Mar 4 10:18:54 kernel: bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb Mar 4 10:18:54 kernel: bttv0: using: BT878(Hauppauge (bt878)) [card=10,autodetected] Mar 4 10:18:54 kernel: bttv0: Hauppauge/Voodoo msp34xx: reset line init [5] Mar 4 10:18:54 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1 sda: 1 -- testing... Mar 4 10:18:54 kernel: i2c-algo-bit.o:1 scl: 1 sda: 0 Mar 4 10:18:54 kernel: i2c-algo-bit.o:2 scl: 1 sda: 1 Mar 4 10:18:54 kernel: i2c-algo-bit.o:3 scl: 0 sda: 1 Mar 4 10:18:54 kernel: i2c-algo-bit.o:4 scl: 1 sda: 1 Mar 4 10:18:54 kernel: i2c-algo-bit.o: bt848 #0 passed test.

3) a "lsmod | grep bttv" returns: "bttv 73728 (initializing)" which implies to me it is NOT fully starting up. No other modules in lsmod are just 'initializing' all day ;^)

4) Running the latest QtVision or KWinTV show no available tuners/devices.

5) Per Hauppauge tech support my card has an LG tuner, but not which one (they said they cannot support Linux as they don't know it themselves).

6) it *IS* possible this is a conflict between my ES1969 Solo-1 AudioDrive (sound card) built into the IBM motherboard. But normal sound seems to be working.

But I still think it is an issue that my new card (manuf end 2003) has a tuner that the current bttv (0.7.104) doesn't recognize. The CARDS file at latest bttv / video4linux doesn't mention LG for Hauppauge, but they do warn that Hauppauge has a habit of changing tuner chips without notice in the same models over time.

Thanks for the suggestion - now I just need to tell SuSE 9.0 *NOT* to try to start the card until I find an answer.

many thanks - Lynn

The BTTV driver gets started because of the : Load "v4l" line in the Modules section of the XF86Config file. If you take this out, it should stop loading the bttv driver. However, I won't swear that the bttv driver will work after that either. I would suspect that you still have an interrupt problem. You can check this with "cat /proc/interrupts" and see if anything shows up there. I don't know which version of the card you have, but I have had my Hauppauge WinTV card (model 401) for several years and haven't had any problems with it since clearing up my interrupt problems. The worst problem I had was when it conflicted with the video card. But that was a total system lock-up. -- Kelly L. Fulks Home Account near Huntsville, AL