Es schrieb Dave Euser: > > I've read everything that I can find on this.....when I try to build > from the snapshots on bytesex.org, i can't load the saa7134 module - > everything else is fine.... I get the following: > > /lib/modules/2.4.23/v4l2/saa7134.o: /lib/modules/2.4.23/v4l2/saa7134.o: > unresolved symbol video_register_device > /lib/modules/2.4.23/v4l2/saa7134.o: /lib/modules/2.4.23/v4l2/saa7134.o: > unresolved symbol video_unregister_device > /lib/modules/2.4.23/v4l2/saa7134.o: /lib/modules/2.4.23/v4l2/saa7134.o: > unresolved symbol video_usercopy > /lib/modules/2.4.23/v4l2/saa7134.o: /lib/modules/2.4.23/v4l2/saa7134.o: > unresolved symbol video_device_release > /lib/modules/2.4.23/v4l2/saa7134.o: /lib/modules/2.4.23/v4l2/saa7134.o: > unresolved symbol video_device_alloc > /lib/modules/2.4.23/v4l2/saa7134.o: insmod > /lib/modules/2.4.23/v4l2/saa7134.o failed > /lib/modules/2.4.23/v4l2/saa7134.o: insmod saa7134 failed > > lsmod gives: > Module Size Used by Not tainted > v4l1-compat 12612 0 (unused) > video-buf 11920 0 (unused) > v4l2-common 3200 0 (unused) > i2c-core 13092 0 > parport_pc 15972 1 (autoclean) > lp 7040 0 (autoclean) > parport 25536 1 (autoclean) [parport_pc lp] > ide-scsi 10480 0 > > Running straight 2.4.23....any ideas? > Hi, read http://bytesex.org/v4l/build.html and apply latest 2.4.23-4/ patch-2.4.23-kraxel.gz first. Hermann