Sony VAIO GT1 - side ccd camera operation

[rcrsn51]

You used the wrong commands to check if the modules were auto-loaded. Use lsmod instead.

[lurching]

You used the wrong commands to check if the modules were auto-loaded. Use lsmod instead.

Please be more specific then troubleshooting will be faster

lsmod | grep meye
displays:

Code: Select all

meye 210474 0
videodev 57950 1 meye
sony_laptop 23326 1 meye

lsmod | grep sony_laptop
displays:

Code: Select all

sony_laptop 23326 1 meye
rfkill 9954 2  cfg80211, sony_laptop

lsmod | grep sonypi
displays nothing

Edit: installed guvcview for Slacko 5.3 sucessfully, but as expected:

"Guvcview error:
Unable to open device
Please make sure the camera is connected
and that the driver is installed"

[rcrsn51]

We now know for sure that meye is auto-loaded at bootup. Because sony_laptop is a dependency of meye, it gets loaded too.

The sonypi module is irrelevant and you can delete the sonypi.conf file that you created.

Instead, create the file sony_laptop.conf in /etc/modprobe.d. One at a time, add these lines and reboot

Code: Select all

options sony_laptop  compat=1
options sony_laptop camera=1
options sony_laptop no_spic=1

Test by running mplayer tv://

[rcrsn51]

It's interesting that rfkill is associated with sony_laptop.

Run: rfkill list all

[lurching]

It's interesting that rfkill is associated with sony_laptop.

Run: rfkill list all

rfkill list all returns this:

Code: Select all

0: phy0: wlan
   Soft blocked: no
   Hard blocked: no

[rcrsn51]

What happened with my suggestions in the previous post?

[lurching]

We now know for sure that meye is auto-loaded at bootup. Because sony_laptop is a dependency of meye, it gets loaded too.

The sonypi module is irrelevant and you can delete the sonypi.conf file that you created.

Instead, create the file sony_laptop.conf in /etc/modprobe.d. One at a time, add these lines and reboot

Code: Select all

options sony_laptop  compat=1
options sony_laptop camera=1
options sony_laptop no_spic=1

Test by running mplayer tv://

Deleted the sonypi.conf.

Created sony_laptop.conf in /etc/modprobe.d

Running mplayer tv:// supplies following identical result:

Code: Select all

Playing tv://.
TV file format detected
Selected driver: v412
name: Video 4 Linux 2 input
author: Martin Olchewski <olschewski@zpr.uni-koeln.de>
comment: first try, more to come ;-)
v412: unable to open 'dev/video0': No such device or address
v412: ioctl set mute failed: Bad file descriptor
v412: 0 frames successfully processed, 0 frames dropped

Exiting... (End of file)

[rcrsn51]

I think that we are back to the same conclusion - neither the meye nor the sonly_laptop modules can communicate with the camera.

[lurching]

I think that we are back to the same conclusion - neither the meye nor the sonly_laptop modules can communicate with the camera.

Would it be possible that the 3.1.10 kernel would be too early a version to run those modules successfully? Also, how can we verify that the machine is indeed normally operational with these drivers? The documentation mentioned a kernel 4.x.x.

[rcrsn51]

Also, how can we verify that the machine is indeed normally operational with these drivers?

You would need to get a VAIO laptop with a genuine webcam.

[lurching]

Also, how can we verify that the machine is indeed normally operational with these drivers?

You would need to get a VAIO laptop with a genuine webcam.

Hahaha thanks for your enthusiasm! Never in a million years this machine rocks and is unprecedented!

Let’s try another way then:

Edit2: Let's try with the GSPCA driver then like we investigated earlier. Then there is also the Sony ccd driver investigated at the end the initial thread.

Edit: By the way, Slacko upon shutdown displays an error message that there's a pcmcia slot that is empty and hangs there. I suppose it is related to sony_laptop. How can I restore my frugal? Any idea? Maybe with another save file?

[lurching]

Update: I've installed an SSD PATA hard drive in the machine loading now several times faster.

I wonder if there are new attempts we could do with the camera driver. Any suggestions?