Odp: Webcam problem
juz sprawdziłem ;d
Nie jesteś zalogowany. Proszę się zalogować lub zarejestrować.
eko.one.pl → Oprogramowanie / Software → Webcam problem
Strony Poprzednia 1 2 3 Następna
Zaloguj się lub zarejestruj by napisać odpowiedź
juz sprawdziłem ;d
Witam próbuje skonfigurować kamerkę internetową w gargoyle na TL-WR1043ND
Sterowniki zainstalowane ok po wydaniu komendy ls -al /dev/video* mam
crw-r--r-- 1 root root 81, 0 Feb 6 22:27 /dev/video0
po uruchomieniu motion w logach mamMotion thread 1 restart
[1] Thread 1 started
[1] cap.driver: "vc032x"
[1] cap.card: "USB2.0 Web Camera"
[1] cap.bus_info: "usb-ar71xx-ehci-1.4.2"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: JPEG (JPEG)
[1] index_format 3 Test palette JPEG (320x240)
[1] Using palette JPEG (320x240) bytesperlines 320 sizeimage 29390 colorspace 00000007
[1] Error requesting buffers 4 for memory map. VIDIOC_REQBUFS: Device or resource busy
[1] MAP_FAILED: Invalid argument
[1] Could not fetch initial image from camera
[1] Motion continues using width and height from config file(s)
[1] Resizing pre_capture buffer to 1 items
[1] bind(): Address already in use
[1] Problem enabling stream server in port 8081: Address already in use
[1] Thread exiting
[0] Motion thread 1 restart
[1] Thread 1 started
[1] cap.driver: "vc032x"
[1] cap.card: "USB2.0 Web Camera"
[1] cap.bus_info: "usb-ar71xx-ehci-1.4.2"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: JPEG (JPEG)
[1] index_format 3 Test palette JPEG (320x240)
[1] Using palette JPEG (320x240) bytesperlines 320 sizeimage 29390 colorspace 00000007
[1] Error requesting buffers 4 for memory map. VIDIOC_REQBUFS: Device or resource busy
[1] MAP_FAILED: Invalid argument
[1] Could not fetch initial image from camera
[1] Motion continues using width and height from config file(s)
[1] Resizing pre_capture buffer to 1 items
[1] bind(): Address already in use
[1] Problem enabling stream server in port 8081: Address already in use
[1] Thread exitingCo jest nie tak obraz po wejsciu na adres rutera jest szary
Podpiołem inną kamerkę i to samo po wydaniu komendy motion
0] Processing thread 0 - config file /etc/motion.conf
[0] Unknown config option "ffmpeg_cap_new"
[0] Unknown config option "ffmpeg_cap_motion"
[0] Unknown config option "ffmpeg_timelapse"
[0] Unknown config option "ffmpeg_timelapse_mode"
[0] Unknown config option "ffmpeg_bps"
[0] Unknown config option "ffmpeg_variable_bitrate"
[0] Unknown config option "ffmpeg_video_codec"
[0] Unknown config option "ffmpeg_deinterlace"
[0] Unknown config option "movie_filename"
[0] Unknown config option "timelapse_filename"
[0] Unknown config option "sql_log_image"
[0] Unknown config option "sql_log_snapshot"
[0] Unknown config option "sql_log_mpeg"
[0] Unknown config option "sql_log_timelapse"
[0] Unknown config option "sql_query"
[0] Motion 3.2.11.1 Started
[0] Thread 1 is from /etc/motion.conf
[1] Thread 1 started
[0] motion-httpd/3.2.11.1 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[1] cap.driver: "sonixj"
[1] cap.card: "USB camera"
[1] cap.bus_info: "usb-ar71xx-ehci-1.1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: JPEG (JPEG)
[1] index_format 3 Test palette JPEG (320x240)
[1] Using palette JPEG (320x240) bytesperlines 320 sizeimage 29390 colorspace 00000007
[1] found control 0x00980900, "Brightness", range 0,65535
[1] "Brightness", default 32768, current 32768
[1] found control 0x00980901, "Contrast", range 0,127
[1] "Contrast", default 63, current 63
[1] found control 0x00980902, "Saturation", range 0,40
[1] "Saturation", default 25, current 25
[1] found control 0x0098090e, "Red Balance", range 24,40
[1] "Red Balance", default 32, current 32
[1] found control 0x0098090f, "Blue Balance", range 24,40
[1] "Blue Balance", default 32, current 32
[1] found control 0x00980910, "Gamma", range 0,40
[1] "Gamma", default 20, current 20
[1] mmap information:
[1] frames=4
[1] 0 length=32768
[1] 1 length=32768
[1] 2 length=32768
[1] 3 length=32768
[1] Error starting stream VIDIOC_STREAMON: Input/output error
[1] Failed with YUV420P, trying YUV422 palette: Invalid argument
[1] Failed with YUV422, trying YUYV palette: Invalid argument
[1] Failed with YUYV, trying RGB24 palette: Invalid argument
[1] Failed with RGB24, trying GREYSCALE palette: Invalid argument
[1] Failed with all supported palettes - giving up: Invalid argument
[1] Could not fetch initial image from camera
[1] Motion continues using width and height from config file(s)
[1] Resizing pre_capture buffer to 1 items
[1] Started stream webcam server in port 8089
[1] Retrying until successful connection with camera
[1] cap.driver: "sonixj"
[1] cap.card: "USB camera"
[1] cap.bus_info: "usb-ar71xx-ehci-1.1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: JPEG (JPEG)
[1] index_format 3 Test palette JPEG (320x240)
[1] Using palette JPEG (320x240) bytesperlines 320 sizeimage 29390 colorspace 00000007
[1] found control 0x00980900, "Brightness", range 0,65535
[1] "Brightness", default 32768, current 32768
[1] found control 0x00980901, "Contrast", range 0,127
[1] "Contrast", default 63, current 63
[1] found control 0x00980902, "Saturation", range 0,40
[1] "Saturation", default 25, current 25
[1] found control 0x0098090e, "Red Balance", range 24,40
[1] "Red Balance", default 32, current 32
[1] found control 0x0098090f, "Blue Balance", range 24,40
[1] "Blue Balance", default 32, current 32
[1] found control 0x00980910, "Gamma", range 0,40
[1] "Gamma", default 20, current 20
[1] Error requesting buffers 4 for memory map. VIDIOC_REQBUFS: Device or resource busy
[1] MAP_FAILED: Invalid argument
czyli rozumiem ze, nie mam mozliwosci na chwilę obecną uruchomić motion zeby działało poprawnie ?
Mialem podobny problem, ale udalo sie go obejsc:
http://eko.one.pl/forum/viewtopic.php?pid=17066#p17066
Wydaje mi się że nie. Sprawdź inną kamerę na innym sterowniku.
Daje sie skompilowac wersje modulu uvcvideo z kernela 2.6.34.8, ale ona nie rozwiazuje problemu z MJPEG, przynajmniej w moim przypadku.
Mietek a popróbuj w /etc/motion.conf zmienić palete (YUV, YUV24, RGB it..), tam chyba jest domyślnie 8 wybrana...
Ja przy swojej C210 musiałem zmienić na inną, nie mam tu dostępu do konfiga, to nie powiem Ci na jaką, próbuj empirycznie, to tylko 7 kombinacji.
Witam! Odświeże troche temat, ponieważ mam bardzo podobny problem, a może i dokładnie taki sam. Mój routher TP-Link TL WR1043ND, zainstalowany pakiet openwrt-ar71xx-tl-wr1043nd-v1-squashfs-sysupgrade.bin oraz Webcam, zgodnie z instrukcją. Próbowałem juz na 2 kamerkach (Creative CT6840, oraz Gear Head) i za każdym razem obraz przez www jest szary, na przemian z przebłyskami zielonych zakłóceń. Po wpisaniu komendy motion wyskakuje:
Dla Creative:
root@Gargoyle:~# motion
[0] Processing thread 0 - config file /etc/motion.conf
[0] Unknown config option "ffmpeg_cap_new"
[0] Unknown config option "ffmpeg_cap_motion"
[0] Unknown config option "ffmpeg_timelapse"
[0] Unknown config option "ffmpeg_timelapse_mode"
[0] Unknown config option "ffmpeg_bps"
[0] Unknown config option "ffmpeg_variable_bitrate"
[0] Unknown config option "ffmpeg_video_codec"
[0] Unknown config option "ffmpeg_deinterlace"
[0] Unknown config option "movie_filename"
[0] Unknown config option "timelapse_filename"
[0] Unknown config option "sql_log_image"
[0] Unknown config option "sql_log_snapshot"
[0] Unknown config option "sql_log_mpeg"
[0] Unknown config option "sql_log_timelapse"
[0] Unknown config option "sql_query"
[0] Motion 3.2.11.1 Started
[0] Thread 1 is from /etc/motion.conf
[0] motion-httpd/3.2.11.1 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[1] Thread 1 started
[1] cap.driver: "ov519"
[1] cap.card: "USB Camera (05a9:0511)"
[1] cap.bus_info: "usb-ar71xx-ehci-1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: O511 (O511)
[1] Unable to find a compatible palette format.
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] Resizing pre_capture buffer to 1 items
[1] Started stream webcam server in port 8081
[1] sync error in proc 2299: Invalid argument
[1] mcapture error in proc 2299: Invalid argument
[1] Video device fatal error - Closing video device
[1] Closing video device /dev/video0
[1] Retrying until successful connection with camera
[1] cap.driver: "ov519"
[1] cap.card: "USB Camera (05a9:0511)"
[1] cap.bus_info: "usb-ar71xx-ehci-1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: O511 (O511)
[1] Unable to find a compatible palette format.
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] sync error in proc 2299: Invalid argument
[1] mcapture error in proc 2299: Invalid argument
[1] Video device fatal error - Closing video device
[1] Closing video device /dev/video0
Natomiast dla 2 kamerki podobnie:
root@Gargoyle:~# motion
[0] Processing thread 0 - config file /etc/motion.conf
[0] Unknown config option "ffmpeg_cap_new"
[0] Unknown config option "ffmpeg_cap_motion"
[0] Unknown config option "ffmpeg_timelapse"
[0] Unknown config option "ffmpeg_timelapse_mode"
[0] Unknown config option "ffmpeg_bps"
[0] Unknown config option "ffmpeg_variable_bitrate"
[0] Unknown config option "ffmpeg_video_codec"
[0] Unknown config option "ffmpeg_deinterlace"
[0] Unknown config option "movie_filename"
[0] Unknown config option "timelapse_filename"
[0] Unknown config option "sql_log_image"
[0] Unknown config option "sql_log_snapshot"
[0] Unknown config option "sql_log_mpeg"
[0] Unknown config option "sql_log_timelapse"
[0] Unknown config option "sql_query"
[0] Motion 3.2.11.1 Started
[0] Thread 1 is from /etc/motion.conf
[0] motion-httpd/3.2.11.1 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[1] Thread 1 started
[1] cap.driver: "pac7311"
[1] cap.card: "USB Camera (093a:2620)"
[1] cap.bus_info: "usb-ar71xx-ehci-1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: PJPG (PJPG)
[1] Unable to find a compatible palette format.
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] Resizing pre_capture buffer to 1 items
[1] Started stream webcam server in port 8081
[1] sync error in proc 2359: Invalid argument
[1] mcapture error in proc 2359: Invalid argument
[1] Video device fatal error - Closing video device
[1] Closing video device /dev/video0
[1] Retrying until successful connection with camera
[1] cap.driver: "pac7311"
[1] cap.card: "USB Camera (093a:2620)"
[1] cap.bus_info: "usb-ar71xx-ehci-1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: PJPG (PJPG)
[1] Unable to find a compatible palette format.
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] sync error in proc 2359: Invalid argument
[1] mcapture error in proc 2359: Invalid argument
[1] Video device fatal error - Closing video device
[1] Closing video device /dev/video0
[1] Retrying until successful connection with camera
[1] cap.driver: "pac7311"
[1] cap.card: "USB Camera (093a:2620)"
[1] cap.bus_info: "usb-ar71xx-ehci-1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: PJPG (PJPG)
[1] Unable to find a compatible palette format.
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] sync error in proc 2359: Invalid argument
[1] mcapture error in proc 2359: Invalid argument
[1] Video device fatal error - Closing video device
[1] Closing video device /dev/video0Dodam że próbowałem zmieniać palety na wszystkie z 8 dostępnych i efekt cały czas ten sam
Bardzo prosze o pomoc!
Kup inną kamerę...
Jeżeli ktoś zdecyduje się na kamerkę Logitech HD WebCam C270 (cena 80-90 PLN), to działa ona na sterowniku kmod-video-uvc. Udało mi się uruchomić ją z fswebcam, motion oraz mjpg-streamer.
Dla motion największa rozdzielczość, jaką uzyskałem, to domyślne 352 x 288 przy ustawieniach
framerate 2
v4l2_palette 6Przy innych ustawieniach obraz jest szary lub uruchomienie motion wyrzuca błędy.
ps.
Poniższy błąd najprawdopodobniej wynika z zajętości portu 8081 przez inny serwis lub inną instancję samego motion.
Przed uruchomieniem motion należy sprawdzić w procesach, czy nie jest on już uruchomiony.
Problem enabling stream server in port 8081: Address already in useDla mjpg-streamer uzyskana rozdzielczość to maksymalne 1280x720, ale tylko dla 1 fps
config mjpg-streamer core
option device "/dev/video0"
option resolution "1280x720"
option fps "1"
option port "8082"
option enabled "true"Dla powyższej konfiguracji pojedyncze zdjęcie dostępne jest pod adresem
http://192.168.1.1:8082/?action=snapshot
a wideo pod adresem
http://192.168.1.1:8082/?action=stream
Dla fswebcam udaje się uzyskać pojedyncze zdjęcie z rozdzielczością 1280x720 przy użyciu poniższej komendy.
Czasem jednak coś może pójść nie tak i wynikowy plik jpg nie jest tworzy lub zawiera zakłócenia w postaci szarych
prostokątów.
fswebcam -r 1280x720 /tmp/output_hd.jpegDzięki wielkie za dobrą rade
przetestowałem 3 kamerkę i działa bez zarzutu. Mogę polecić: TRUST WB-3200G. Mam jeszcze jeden problem. Mianowicie chciałbym mieć podgląd do obrazu kamerki przez www, z zewnątrz. Próbowałem w ten sposób, że przekierowałem port 8081 na adres routhera i próbowałem dostać się do obrazu poprzez moje zewnętrzne IP, jednak to nie działa
prosze o podpowiedzi...
tutaj jak przekierowałem port:
http://img64.imageshack.us/img64/6186/p … owanie.jpg
Dodam jeszcze że wewnątrz sieci po wpisaniu w przeglądarce www mojego zewnętrznego adresu IP, od razu pojawia mi się obraz z kamerki i chciałbym żeby to działało także poprzez dostęp z zewnątrz.
Hmm, a po co tak? albo wpisz :8081, albo ustaw żeby nasluchowało na 80, i odblokuj oczywiście port na wanie.
ok więc zrobiłem tak:
1. Otworzyłem port ze strony WAN
# uci add firewall rule
# uci set firewall.@rule[-1]._name=kamera
# uci set firewall.@rule[-1].src=wan
# uci set firewall.@rule[-1].target=ACCEPT
# uci set firewall.@rule[-1].proto=tcp
# uci set firewall.@rule[-1].dest_port=8081
# uci commit firewallNastępnie przekierowałem port 8081 na adres routhera:
# uci add firewall redirect
# uci set firewall.@redirect[-1]._name=kamera
# uci set firewall.@redirect[-1].src=wan
# uci set firewall.@redirect[-1].proto=tcpudp
# uci set firewall.@redirect[-1].src_dport=8081
# uci set firewall.@redirect[-1].dest_port=8081
# uci set firewall.@redirect[-1].dest_ip=192.168.1.1
# uci commit firewalli teraz z tego co rozumiem powinno działać po wpisaniu do przeglądarki: http://417.97.188.180:8081/ (gdzie 417.97.188.180 to zewnętrzne IP). Działa tak ok, ale tylko u mnie w sieci, a z zewnątrz juz nie wchodzi, brak połączenia.
Ale po co to przekierowanie? Samo otwarcie wystarczy. Jeżeli tylko słuch ana wszystkim a nie tylko na 192.168.1.1.
hmm a jak sprawdzę czy słucha na wszystim? ewentualnie jak to ustawic? A to przekierowanie co zrobiłem to jak teraz wyłączyć? Jak moge sprawdzić czy port został prawidłowo otwarty? I jeszcze jedno pytanie, czy z zewnątrz po wpisaniu http://417.97.188.180 powinienem wejść do routhera?
Jeżeli odblokowałeś port 80 na firewallu to tak.
Usuń reguły po prostu.
Dla motion największa rozdzielczość, jaką uzyskałem, to domyślne 352 x 288 przy ustawieniach
framerate 2 v4l2_palette 6Przy innych ustawieniach obraz jest szary lub uruchomienie motion wyrzuca błędy.
U mnie kamerka C310 w motion dziala tez w takiej rodzielczosci:
width 640
height 368kamerka działa juz z dostępem z zewnątrz
mój błąd nie otwarłem portu 80 w firewallu. Dostałem dziś nowy sprzęt, ponieważ kamerka TRUST WB-3200G była pożyczana. Moja nowa to Media-tech MT4016. Niestety po raz kolejny problem, ponieważ obraz jest szary na przemian z zielonymi zakłóceniami. Po wydaniu komendy motion pokazało:
root@Gargoyle:~# motion
[0] Processing thread 0 - config file /etc/motion.conf
[0] Unknown config option "ffmpeg_cap_new"
[0] Unknown config option "ffmpeg_cap_motion"
[0] Unknown config option "ffmpeg_timelapse"
[0] Unknown config option "ffmpeg_timelapse_mode"
[0] Unknown config option "ffmpeg_bps"
[0] Unknown config option "ffmpeg_variable_bitrate"
[0] Unknown config option "ffmpeg_video_codec"
[0] Unknown config option "ffmpeg_deinterlace"
[0] Unknown config option "movie_filename"
[0] Unknown config option "timelapse_filename"
[0] Unknown config option "sql_log_image"
[0] Unknown config option "sql_log_snapshot"
[0] Unknown config option "sql_log_mpeg"
[0] Unknown config option "sql_log_timelapse"
[0] Unknown config option "sql_query"
[0] Motion 3.2.11.1 Started
[0] Thread 1 is from /etc/motion.conf
[0] motion-httpd/3.2.11.1 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[1] Thread 1 started
[1] cap.driver: "pac7311"
[1] cap.card: "USB Camera (093a:2620)"
[1] cap.bus_info: "usb-ar71xx-ehci-1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: PJPG (PJPG)
[1] Unable to find a compatible palette format.
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] Resizing pre_capture buffer to 1 items
[1] Started stream webcam server in port 8081
[1] sync error in proc 6441: Invalid argument
[1] mcapture error in proc 6441: Invalid argument
[1] Video device fatal error - Closing video device
[1] Closing video device /dev/video0
[1] Retrying until successful connection with camera
[1] cap.driver: "pac7311"
[1] cap.card: "USB Camera (093a:2620)"
[1] cap.bus_info: "usb-ar71xx-ehci-1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: PJPG (PJPG)
[1] Unable to find a compatible palette format.
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] sync error in proc 6441: Invalid argument
[1] mcapture error in proc 6441: Invalid argument
[1] Video device fatal error - Closing video device
[1] Closing video device /dev/video0
[1] Retrying until successful connection with camera
[1] cap.driver: "pac7311"
[1] cap.card: "USB Camera (093a:2620)"
[1] cap.bus_info: "usb-ar71xx-ehci-1"
[1] cap.capabilities=0x05000001
[1] - VIDEO_CAPTURE
[1] - READWRITE
[1] - STREAMING
[1] Supported palettes:
[1] 0: PJPG (PJPG)
[1] Unable to find a compatible palette format.
[1] Using VIDEO_PALETTE_YUV420P palette
[1] Using V4L1
[1] sync error in proc 6441: Invalid argument
[1] mcapture error in proc 6441: Invalid argument
[1] Video device fatal error - Closing video device
[1] Closing video device /dev/video0Można coś z tym poradzić? Czy jest to kolejna kamerka z cyklu nieobsługiwanych? ![]()
kolejna nie obsługiwana przez motion.
Więc tak mój routher przeżył failsafe i muszę teraz wgrać od nowa pakiety. Coś jest nie tak juz na samym początku przy instalacji modułów.
root@Gargoyle:~# opkg update
Downloading [url]http://ecco.selfip.net/gargoyle-pl/ar71xx/packages/Packages.gz.[/url]
wget: server returned error: HTTP/1.0 404 Not Found
Downloading [url]http://downloads.openwrt.org/backfire/10.03.1-rc4/ar71xx/packages/Pa[/url] ckages.gz.
Inflating [url]http://downloads.openwrt.org/backfire/10.03.1-rc4/ar71xx/packages/Pack[/url] ages.gz.
Updated list of available packages in /var/opkg-lists/packages.
Collected errors:
* opkg_download: Failed to download [url]http://ecco.selfip.net/gargoyle-pl/ar71xx/p[/url] ackages/Packages.gz, wget returned 1.
root@Gargoyle:~# opkg install komd-usb-core kmod-usb2 kmod-video-core
Unknown package 'komd-usb-core'.
Multiple packages (kmod-usb2 and kmod-usb2) providing same name marked HOLD or P REFER. Using latest.
Package kmod-usb2 (2.6.32.27-1cj) installed in root is up to date.
Installing kmod-video-core (2.6.32.25-1) to root...
Downloading [url]http://downloads.openwrt.org/backfire/10.03.1-rc4/ar71xx/packages/km[/url] od-video-core_2.6.32.25-1_ar71xx.ipk.
Multiple packages (kernel and kernel) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kernel and kernel) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kernel and kernel) providing same name marked HOLD or PREFER. Using latest.
Multiple packages (kernel and kernel) providing same name marked HOLD or PREFER. Using latest.
Not downgrading package kernel on root from 2.6.32.27-1cj to 2.6.32.25-1.
Collected errors:
* opkg_install_cmd: Cannot install package komd-usb-core.
* opkg_install_cmd: Cannot install package kmod-video-core.W czym może tkwić problem? Nie ma juz tych pakietów?
Nie ma już dawno takiego repo...
więc co muszę teraz zrobić, aby poprawnie uruchomić pakiet motion ?? może warto aktualizować instrukcje do instalacji webcam?
A co ma instrukcja do tego? Masz zdefiowane repo którego już nie ma, jest inne, http://ecco.selfip.net/backfire/packages/ . Z niego masz zainstalować pakiety.
a moge prosić o podpowiedź jak zdefiniować korzystanie z nowego repo
W /etc/opkg.conf
Tyle że masz gargoyle, więc zapewne moduły od usb już dawno masz zainstalowane...
Dzięki za cierpliwość
owszem mam gargoyle. Postępowałem zgodnie z instrukcją webcam i coś poszło nie tak bo nie moge wykryć kamerki, która poprzednio śmigała bez problemu
FAT: Directory bread(block 17233) failed
FAT: Directory bread(block 17234) failed
FAT: Directory bread(block 17235) failed
FAT: Directory bread(block 17236) failed
FAT: Directory bread(block 17237) failed
FAT: Directory bread(block 17238) failed
FAT: Directory bread(block 17239) failed
FAT: Directory bread(block 17240) failed
FAT: Directory bread(block 17241) failed
FAT: Directory bread(block 17242) failed
FAT: Directory bread(block 17243) failed
FAT: Directory bread(block 17244) failed
FAT: Directory bread(block 17245) failed
FAT: Directory bread(block 17246) failed
FAT: Directory bread(block 17247) failed
FAT: Directory bread(block 17248) failed
FAT: Directory bread(block 17249) failed
FAT: Directory bread(block 17250) failed
FAT: Directory bread(block 17251) failed
FAT: Directory bread(block 17252) failed
FAT: Directory bread(block 17253) failed
FAT: Directory bread(block 17254) failed
FAT: Directory bread(block 17255) failed
FAT: Directory bread(block 17256) failed
FAT: Directory bread(block 17257) failed
FAT: Directory bread(block 17258) failed
FAT: Directory bread(block 17259) failed
FAT: Directory bread(block 17260) failed
FAT: Directory bread(block 17261) failed
FAT: Directory bread(block 17262) failed
FAT: Directory bread(block 17263) failed
FAT: Directory bread(block 17232) failed
FAT: Directory bread(block 17233) failed
FAT: Directory bread(block 17234) failed
FAT: Directory bread(block 17235) failed
FAT: Directory bread(block 17236) failed
FAT: Directory bread(block 17237) failed
FAT: Directory bread(block 17238) failed
FAT: Directory bread(block 17239) failed
FAT: Directory bread(block 17240) failed
FAT: Directory bread(block 17241) failed
FAT: Directory bread(block 17242) failed
FAT: Directory bread(block 17243) failed
FAT: Directory bread(block 17244) failed
FAT: Directory bread(block 17245) failed
FAT: Directory bread(block 17246) failed
FAT: Directory bread(block 17247) failed
FAT: Directory bread(block 17248) failed
FAT: Directory bread(block 17249) failed
FAT: Directory bread(block 17250) failed
FAT: Directory bread(block 17251) failed
FAT: Directory bread(block 17252) failed
FAT: Directory bread(block 17253) failed
FAT: Directory bread(block 17254) failed
FAT: Directory bread(block 17255) failed
FAT: Directory bread(block 17256) failed
FAT: Directory bread(block 17257) failed
FAT: Directory bread(block 17258) failed
FAT: Directory bread(block 17259) failed
FAT: Directory bread(block 17260) failed
FAT: Directory bread(block 17261) failed
FAT: Directory bread(block 17262) failed
FAT: Directory bread(block 17263) failed
FAT: Directory bread(block 17232) failed
FAT: Directory bread(block 17233) failed
FAT: Directory bread(block 17234) failed
FAT: Directory bread(block 17235) failed
FAT: Directory bread(block 17236) failed
FAT: Directory bread(block 17237) failed
FAT: Directory bread(block 17238) failed
FAT: Directory bread(block 17239) failed
FAT: Directory bread(block 17240) failed
FAT: Directory bread(block 17241) failed
FAT: Directory bread(block 17242) failed
FAT: Directory bread(block 17243) failed
FAT: Directory bread(block 17244) failed
FAT: Directory bread(block 17245) failed
FAT: Directory bread(block 17246) failed
FAT: Directory bread(block 17247) failed
FAT: Directory bread(block 17248) failed
FAT: Directory bread(block 17249) failed
FAT: Directory bread(block 17250) failed
FAT: Directory bread(block 17251) failed
FAT: Directory bread(block 17252) failed
FAT: Directory bread(block 17253) failed
FAT: Directory bread(block 17254) failed
FAT: Directory bread(block 17255) failed
FAT: Directory bread(block 17256) failed
FAT: Directory bread(block 17257) failed
FAT: Directory bread(block 17258) failed
FAT: Directory bread(block 17259) failed
FAT: Directory bread(block 17260) failed
FAT: Directory bread(block 17261) failed
FAT: Directory bread(block 17262) failed
FAT: Directory bread(block 17263) failed
FAT: Directory bread(block 17232) failed
FAT: Directory bread(block 17233) failed
FAT: Directory bread(block 17234) failed
FAT: Directory bread(block 17235) failed
FAT: Directory bread(block 17236) failed
FAT: Directory bread(block 17237) failed
FAT: Directory bread(block 17238) failed
FAT: Directory bread(block 17239) failed
FAT: Directory bread(block 17240) failed
FAT: Directory bread(block 17241) failed
FAT: Directory bread(block 17242) failed
FAT: Directory bread(block 17243) failed
FAT: Directory bread(block 17244) failed
FAT: Directory bread(block 17245) failed
FAT: Directory bread(block 17246) failed
FAT: Directory bread(block 17247) failed
FAT: Directory bread(block 17248) failed
FAT: Directory bread(block 17249) failed
FAT: Directory bread(block 17250) failed
FAT: Directory bread(block 17251) failed
FAT: Directory bread(block 17252) failed
FAT: Directory bread(block 17253) failed
FAT: Directory bread(block 17254) failed
FAT: Directory bread(block 17255) failed
FAT: Directory bread(block 17256) failed
FAT: Directory bread(block 17257) failed
FAT: Directory bread(block 17258) failed
FAT: Directory bread(block 17259) failed
FAT: Directory bread(block 17260) failed
FAT: Directory bread(block 17261) failed
FAT: Directory bread(block 17262) failed
FAT: Directory bread(block 17263) failed
FAT: Directory bread(block 17232) failed
FAT: Directory bread(block 17233) failed
FAT: Directory bread(block 17234) failed
FAT: Directory bread(block 17235) failed
FAT: Directory bread(block 17236) failed
FAT: Directory bread(block 17237) failed
FAT: Directory bread(block 17238) failed
FAT: Directory bread(block 17239) failed
FAT: Directory bread(block 17240) failed
FAT: Directory bread(block 17241) failed
FAT: Directory bread(block 17242) failed
FAT: Directory bread(block 17243) failed
FAT: Directory bread(block 17244) failed
FAT: Directory bread(block 17245) failed
FAT: Directory bread(block 17246) failed
FAT: Directory bread(block 17247) failed
FAT: Directory bread(block 17248) failed
FAT: Directory bread(block 17249) failed
FAT: Directory bread(block 17250) failed
FAT: Directory bread(block 17251) failed
FAT: Directory bread(block 17252) failed
FAT: Directory bread(block 17253) failed
FAT: Directory bread(block 17254) failed
FAT: Directory bread(block 17255) failed
FAT: Directory bread(block 17256) failed
FAT: Directory bread(block 17257) failed
FAT: Directory bread(block 17258) failed
FAT: Directory bread(block 17259) failed
FAT: Directory bread(block 17260) failed
FAT: Directory bread(block 17261) failed
FAT: Directory bread(block 17262) failed
FAT: Directory bread(block 17263) failed
usb 1-1: new full speed USB device using ar71xx-ehci and address 3
usb 1-1: configuration #1 chosen from 1 choice
i2c /dev entries driver
Linux video capture interface: v2.00
gspca: main v2.7.0 registered
usbcore: registered new interface driver conex
conex: registered
usbcore: registered new interface driver etoms
etoms: registered
usbcore: registered new interface driver finepix
finepix: registered
gspca_gl860: driver startup - version 0.9d10
usbcore: registered new interface driver gspca_gl860
gspca_gl860: driver registered
usbcore: registered new interface driver jeilinj
jeilinj: registered
usbcore: registered new interface driver ALi m5602
ALi m5602: registered
usbcore: registered new interface driver mars
mars: registered
usbcore: registered new interface driver mr97310a
mr97310a: registered
usbcore: registered new interface driver ov534
ov534: registered
usbcore: registered new interface driver pac207
pac207: registered
usbcore: registered new interface driver pac7311
pac7311: registered
usbcore: registered new interface driver sonixb
sonixb: registered
usbcore: registered new interface driver sonixj
sonixj: registered
usbcore: registered new interface driver spca500
spca500: registered
usbcore: registered new interface driver spca501
spca501: registered
usbcore: registered new interface driver spca505
spca505: registered
usbcore: registered new interface driver spca506
spca506: registered
usbcore: registered new interface driver spca508
spca508: registered
usbcore: registered new interface driver spca561
spca561: registered
usbcore: registered new interface driver sq905
sq905: registered
usbcore: registered new interface driver sq905c
sq905c: registered
usbcore: registered new interface driver stk014
stk014: registered
usbcore: registered new interface driver STV06xx
STV06xx: registered
usbcore: registered new interface driver sunplus
sunplus: registered
usbcore: registered new interface driver t613
t613: registered
usbcore: registered new interface driver tv8532
tv8532: registered
usbcore: registered new interface driver vc032x
vc032x: registered
usbcore: registered new interface driver zc3xx
zc3xx: registered
root@Gargoyle:~# ls -al /dev/video*
ls: /dev/video*: No such file or directory
root@Gargoyle:~#System plików fat Ci się rozleciał. Tylko jeden driver to obsługiwał. I jego trzeba było zainstalować ![]()
wiem ze jeden driver obsługuje, ale zainstalowałem wszystkie bo mam jeszcze do sprawdzenia kilka nowszych kamerek niż ta którą mam. Hmm więc teraz co mi pozostało? Kolejny raz usunięcie całej konfiguracji poprzez polecenie firstboot?
Strony Poprzednia 1 2 3 Następna
Zaloguj się lub zarejestruj by napisać odpowiedź
eko.one.pl → Oprogramowanie / Software → Webcam problem
Forum oparte o PunBB, wspierane przez Informer Technologies, Inc