Re: bttv driver sometimes oopses

2000-10-08 Thread Gerd Knorr

Koos Vriezen wrote:
> Hi,
> 
> Since i2c was added to the kernel, I have sometimes trouble with my bttv
> card. Before that, I never had any trouble with bttv since kernel 2.2.0.

Pick up a newer version from http://www.strusel007.de/linux/bttv/

  Gerd


--e98APlP24773.971000747/einhorn.in-berlin.de--
ReSent-Date: Sun, 8 Oct 2000 13:56:41 +0200 (CEST)
ReSent-From: Gerd Knorr <[EMAIL PROTECTED]>
ReSent-To: [EMAIL PROTECTED]
ReSent-Subject: Re: bttv driver sometimes oopses
ReSent-Message-ID: <[EMAIL PROTECTED]>

Koos Vriezen wrote:
> Hi,
> 
> Since i2c was added to the kernel, I have sometimes trouble with my bttv
> card. Before that, I never had any trouble with bttv since kernel 2.2.0.

Pick up a newer version from http://www.strusel007.de/linux/bttv/

  Gerd


--e98APlP24773.971000747/einhorn.in-berlin.de--

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



Re: bttv driver sometimes oopses

2000-10-08 Thread Gerd Knorr

Koos Vriezen wrote:
 Hi,
 
 Since i2c was added to the kernel, I have sometimes trouble with my bttv
 card. Before that, I never had any trouble with bttv since kernel 2.2.0.

Pick up a newer version from http://www.strusel007.de/linux/bttv/

  Gerd


--e98APlP24773.971000747/einhorn.in-berlin.de--
ReSent-Date: Sun, 8 Oct 2000 13:56:41 +0200 (CEST)
ReSent-From: Gerd Knorr [EMAIL PROTECTED]
ReSent-To: [EMAIL PROTECTED]
ReSent-Subject: Re: bttv driver sometimes oopses
ReSent-Message-ID: [EMAIL PROTECTED]

Koos Vriezen wrote:
 Hi,
 
 Since i2c was added to the kernel, I have sometimes trouble with my bttv
 card. Before that, I never had any trouble with bttv since kernel 2.2.0.

Pick up a newer version from http://www.strusel007.de/linux/bttv/

  Gerd


--e98APlP24773.971000747/einhorn.in-berlin.de--

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/



bttv driver sometimes oopses

2000-10-07 Thread Koos Vriezen

Hi,

Since i2c was added to the kernel, I have sometimes trouble with my bttv
card. Before that, I never had any trouble with bttv since kernel 2.2.0.
The modules are loaded when I start X with vidmode extension turned on. When
everything goes well I see the following in my syslog:

 kernel: Linux video capture interface: v1.00
 kernel: i2c-core.o: i2c core module
 kernel: i2c-algo-bit.o: i2c bit algorithm module
 kernel: bttv: driver version 0.7.38 loaded
 kernel: bttv: using 2 buffers with 1040k (2080k total) for capture
 kernel: bttv: Bt8xx card found (0).
 kernel: bttv0: Brooktree Bt878 (rev 2) bus: 0, devfn: 80, irq: 9, memory:
0xe700.
 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 1 -- testing...
 kernel: i2c-algo-bit.o:1 scl: 1  sda: 0
 kernel: i2c-algo-bit.o:2 scl: 1  sda: 1
 kernel: i2c-algo-bit.o:3 scl: 0  sda: 1
 kernel: i2c-algo-bit.o:4 scl: 1  sda: 1
 kernel: i2c-algo-bit.o: bt848 #0 passed test.
 kernel: bttv0: i2c: checking for eeprom @ 0xa0... found
 kernel: bttv0: card id: Hauppauge WinTV (0x13eb0070) => card=10
 kernel: bttv0: model: BT878(Hauppauge new (bt878)) [insmod option]
 kernel: bttv0: Hauppauge eeprom: tuner=Philips FM1216 (5)
 kernel: bttv0: Hauppauge msp34xx: reset line init
 kernel: bttv0: i2c: checking for MSP34xx @ 0x80... found
 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 1 -- testing...
 kernel: i2c-algo-bit.o:1 scl: 1  sda: 0
 kernel: i2c-algo-bit.o:2 scl: 1  sda: 1
 kernel: i2c-algo-bit.o:3 scl: 0  sda: 1
 kernel: i2c-algo-bit.o:4 scl: 1  sda: 1
 kernel: i2c-algo-bit.o: bt848 #0 passed test.
 kernel: bttv0: i2c: checking for MSP34xx @ 0x80... found
 kernel: msp3400: init: chip=MSP3410D-B4, has NICAM support
 kernel: msp3410: daemon started
 kernel: bttv0: i2c attach [MSP3410D-B4]
 kernel: bttv0: i2c: checking for TDA8425 @ 0x82... not found
 kernel: bttv0: i2c: checking for TDA985x @ 0xb6... not found
 kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found
 kernel: tuner: chip found @ 0x61
 kernel: bttv0: i2c attach [Philips PAL]
 modprobe: modprobe: Can't locate module char-major-81-1
 modprobe: modprobe: Can't locate module sound-slot-1
 modprobe: modprobe: Can't locate module sound-service-1-0
 modprobe: modprobe: Can't locate module sound-slot-1
 modprobe: modprobe: Can't locate module sound-service-1-0

Except that I don't know which aliases to use for the tvmixer. What are they?
Anyway, when it goes wrong I see:

 kernel: Linux video capture interface: v1.00
 kernel: i2c-core.o: i2c core module
 kernel: i2c-algo-bit.o: i2c bit algorithm module
 kernel: bttv: driver version 0.7.38 loaded
 kernel: bttv: using 2 buffers with 1040k (2080k total) for capture
 kernel: bttv: Bt8xx card found (0).
 kernel: bttv0: Brooktree Bt878 (rev 2) bus: 0, devfn: 80, irq: 9, memory:
0xe700.
 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 0 -- testing...
 kernel: i2c-algo-bit.o:1 scl: 1  sda: 0
 kernel: i2c-algo-bit.o:2 scl: 1  sda: 1
 kernel: i2c-algo-bit.o: bt848 #0 SDA stuck low!
 kernel: bttv0: model: BT878(Hauppauge new (bt878)) [insmod option]
 kernel: bttv: readee error
 kernel: bttv0: Hauppauge eeprom: tuner= (4)
 kernel: bttv0: Hauppauge msp34xx: reset line init
 kernel: i2c-core.o: unregister_adapter adap [bt848 #0] not found.
 kernel: i2c-algo-bit.o: Adapter: bt848 #0 scl: 1  sda: 1 -- testing...
 kernel: i2c-algo-bit.o:1 scl: 1  sda: 0
 kernel: i2c-algo-bit.o:2 scl: 1  sda: 1
 kernel: i2c-algo-bit.o:3 scl: 0  sda: 1
 kernel: i2c-algo-bit.o:4 scl: 1  sda: 1
 kernel: i2c-algo-bit.o: bt848 #0 passed test.
 kernel: tuner: chip found @ 0x61
 kernel: bttv0: i2c attach [Philips PAL]
 modprobe: modprobe: Can't locate module char-major-81-1
 modprobe: modprobe: Can't locate module sound-slot-1
 modprobe: modprobe: Can't locate module sound-service-1-0
 modprobe: modprobe: Can't locate module sound-slot-1
 modprobe: modprobe: Can't locate module sound-service-1-0

I can fix this by manually removing the bttv module, before starting XawTV.
But when I don't do that, next will happen:

 kernel: Unable to handle kernel paging request at virtual address c48a5a98
 kernel:  printing eip:
 kernel: c4893594
 kernel: *pde = 03dd7063
 kernel: *pte = 
 kernel: Oops: 
 kernel: CPU:0
 kernel: EIP:0010:[]
 kernel: EFLAGS: 00010246
 kernel: eax: c48a5a98   ebx: c48bd000   ecx: c48bfde0   edx: c48a5a98
 kernel: esi: c48bb000   edi: c48a5a40   ebp:    esp: c3aa3f68
 kernel: ds: 0018   es: 0018   ss: 0018
 kernel: Process rmmod (pid: 1839, stackpage=c3aa3000)
 kernel: Stack: c48bd000 c48bb000 c48bd000 bfffedf8 c4895e88 c48a5a98
c4895e9c 0001
 kernel:0001 c48bed0a c48bfde0 c0116213 c48bd000 c48bb000
 bfffedf8
 kernel:c011572e c48bd000 0001 c3aa2000 0061 bfffedf8
c0108d23 
 kernel: Call Trace: [] [] [] []
[] [] []
 kernel:[] [free_module+23/152] [] []
[sys_delete_module+378/448] [] [system_call+51/64]
 kernel: Code: 8b 1c aa 85 db 74 37 8b 4c 24 28 39 4b 30 75 2e 83 3d 80 5d

$