Abbi pazienza, la ricerca continua

Moderatori: cb_123, thrantir, netvandal, CaberNET54
01:07.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01)
Subsystem: Animation Technologies Inc. LifeView FlyVIDEO2000
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (4000ns min, 10000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fdeff000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
aragorn@MinasTirith:~$ sudo modprobe saa7134 i2c_scan=1
FATAL: Error inserting saa7134 (/lib/modules/2.6.22-14-generic/kernel/drivers/media/video/saa7134/saa7134.ko): Invalid argument
FATAL: Error running install command for saa7134
aragorn@MinasTirith:~$
Aragorn ha scritto:cioè?
Errata - Loading Modules
After running the "make install" command, you might end up with *.ko files and their older compressed version *.ko.gz in the same directory. In this case, the modprobe command might fail (example with the saa7134 module):
sudo modprobe saa7134
FATAL: Error inserting saa7134 (/lib/modules/2.6.17-8mdv/kernel/drivers/media/video/saa7134/saa7134.ko):\
Unknown symbol in module, or unknown parameter (see dmesg)
The dmesg then returns a list of 'unknown symbol' error messages because of compatiblity issues between the new *.ko module files and the old *.ko.gz ones:
Unknown symbol ir_codes_pinnacle_color
Unknown symbol ir_codes_encore_enltv
Unknown symbol ir_codes_proteus_2309
Unknown symbol ir_rc5_timer_keyup
Unknown symbol ir_codes_asus_pc39
Unknown symbol ir_rc5_timer_end
Unknown symbol ir_codes_pinnacle_grey
All conflicting *.ko.gz files must be removed. The following command line can help you locate these conflicting files in all your installed kernels:
for file in `find /lib/modules -name "*.ko"`; do if -e $file.gz ; then echo "$file.gz should be removed"; fi; done
Usually all conflicting module files resulting of v4l-dvb installation will be located in:
/lib/modules/[your kernel version]/kernel/drivers/media
Once the conflicting *.ko.gz have been moved elsewhere or renamed (to *.ko.gz.disabled for example), use the v4l-dvb reload command (I usually add a depmod for safety in order to rebuild modules dependencies):
make reload
depmod -a
Your modules should now be loaded correctly.
Aragorn ha scritto:for file in `find /lib/modules -name "*.ko"`; do if -e $file.gz ; then echo "$file.gz should be removed"; fi; done
come faccio?
aragorn@MinasTirith:~$ #!/bin/sh
aragorn@MinasTirith:~$ for file in `find /lib/modules -name "*.ko"`; do if -e $file.gz ; then echo "$file.gz should be removed"; fi; done
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
bash: -e: command not found
diego.fiozzi ha scritto:ma comunque tutto quel macello lo puoi fare tranquillamente con la funzione cerca, inserendo *.ko come stringa da cercare
Visitano il forum: Nessuno e 1 ospite