Re: [PLUG] Cheese not working addn

[Arun Khan]

On Sun, Sep 9, 2012 at 11:13 AM, Sudheer Bedekar
 wrote:
> Please refer to my earlier post. I forgot to mention that I use Kubuntu 11.10.

OK Kubuntu 11.10 helps but ...

You need to provide info about your hardware (lspci) and the kernel
modules (lsmod) as mentioned in my response to your OP.

-- Arun Khan

___
Pune GNU/Linux Users Group Mailing List 

Re: [PLUG] Cheese not working addn

[म.हा.सा.ग.र]

On Sunday 09 Sep 2012 11:13:50 am Sudheer Bedekar wrote:
> Please refer to my earlier post. I forgot to mention that I use Kubuntu
> 11.10.

Wow, what a beauty of open source thinking you have in your behaviour...
directly giving your ૐ number and being 100 % sure that nobody plays a 
mischief... great thinking... keep it up...

___
Pune GNU/Linux Users Group Mailing List 

[PLUG] Re Cheese

[Sudheer Bedekar]

Thanks. Here is the output of two commands.

sudheer@ADA:~$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory
Controller Hub (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller (rev 09)
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 09)
00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #4 (rev 03)
00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #5 (rev 03)
00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #6 (rev 03)
00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2
EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 1 (rev 03)
00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 5 (rev 03)
00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express
Port 6 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB
UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2
EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI
Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8040
PCI-E Fast Ethernet Controller
06:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n
Wireless LAN Controller (rev 01)

sudheer@ADA:~$ lsmod
Module  Size  Used by
usbhid 41905  0
hid77367  1 usbhid
bnep   17923  2
parport_pc 32114  0
ppdev  12849  0
rfcomm 38408  10
dm_crypt   22565  0
joydev 17393  0
bcma   19571  0
arc4   12473  2
uvcvideo   67271  0
videodev   85626  1 uvcvideo
snd_hda_codec_realtek   254125  1
snd_hda_intel  24262  2
snd_hda_codec  91754  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep  13276  1 snd_hda_codec
snd_pcm80468  2 snd_hda_intel,snd_hda_codec
snd_seq_midi   13132  0
btusb  18160  2
snd_rawmidi25241  1 snd_seq_midi
brcmsmac  591864  0
brcmutil   16885  1 brcmsmac
bluetooth 148839  23 bnep,rfcomm,btusb
mac80211  272785  1 brcmsmac
snd_seq_midi_event 14475  1 snd_seq_midi
snd_seq51567  2 snd_seq_midi,snd_seq_midi_event
psmouse73673  0
snd_timer  28932  2 snd_pcm,snd_seq
snd_seq_device 14172  3 snd_seq_midi,snd_rawmidi,snd_seq
snd55902  13
snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
serio_raw  12990  0
cfg80211  172392  2 brcmsmac,mac80211
crc_ccitt  12595  1 brcmsmac
soundcore  12600  1 snd
snd_page_alloc 14115  2 snd_hda_intel,snd_pcm
lp 17455  0
parport40930  3 parport_pc,ppdev,lp
ahci   21634  2
libahci25727  1 ahci
sky2   49317  0
i915  505108  3
drm_kms_helper 32889  1 i915
drm   192226  4 i915,drm_kms_helper
i2c_algo_bit   13199  1 i915
video  18908  1 i915


Sudheer Bedekar

___
Pune GNU/Linux Users Group Mailing List 

Re: [PLUG] Cheese not working

[Sunil Beta Baskar]

On 9 September 2012 10:58, Arun Khan  wrote:
> On Sun, Sep 9, 2012 at 9:40 AM, Sudheer Bedekar :
>
>> I use RV 508 Samsung laptop. Webcam in it is WEBCAM SCB-0355N. I want
>> to use it for taking photo's and video. I installed Cheese and all
>> related packages. I also installed vlc and mplayer because I heard
>> this will solve the problem. Cheese still does not work. There is only
>> a black screen, all buttons are greyed out. Can someone help me ? I am
>> only a FOSS user, not a techie.
>
> ** Don't reveal phone numbers et al on a public archived mailing list **
>
> You should also mention which Linux distro + Version + 32/64 bit etc.
>
> The kernel probes the hardware in the system and ** automatically
> loads the kernel driver module if it exists **
>
> Most likely the Linux kernel does not have the kernel module for your
> webcam chipset.
>
> The output of 'lspci' and 'lsmod' should give us further clue about
> your hardware.
>
> lspci lists all the devices on the PCI bus.
> lsmod lists all the kernel modules loaded in the kernel.
>
> Share the out put of above in the list.
Sudheer,

Most Laptops use USB for their in-built camera. This is a hardware
convenience standard.

To best detect your camera, please run the following terminal commands
and post the output to the list.

(Most ubuntu installations come with lshw installed by default, so
this should provide all details necessary.)
$ sudo lshw

(For convenience, you can also run) and post the relevant output.
$ sudo usb-devices

This should list your camera as an 'Image Processing Device' or 'Image
Processor' on USB with the BUS-Id, Vendor-Id accurately identifying
all details.

Also as Arun has advised, please include the output of
$ lsmod

If you could not run 'lshw' for some reason, please ensure that you
provide kernel information by capturing the output of:
$ uname -a

This will make it possible to provide better help in the context.

Regards,
Beta

___
Pune GNU/Linux Users Group Mailing List