Thomas Ronayne wrote:
>> It looks like the kernel only recognized your COM1 serial port. That
>> could mean there is only one in your computer, more than likely
>> actually.
>
> Odd, that.

From previous post:
lrwxrwxrwx 1 root root 10 Oct 24 10:48 modem2 -> /dev/ttyS1

This is your COM2(ttyS1). Looks like that winmodem has hijacked your COM
port. Try disabling the winmodem and see if you get your COM2 back.
Disabling the winmodem doesn't really sound like it would be a problem
for you. If disabling the winmodem is a problem see if you can force it
to another COM/ttyS* port. No idea what modem you have so can't give any
advice on that right now.

>> I think the "pilot" is a PalmPilot PDA device.
>
> Interesting -- I wonder where the heck that came from.

That is for Kpilot and/or Gnome-pilot. Palm syncing apps.

>> So, if I remember from your previous post you want to get a camera
>> working! I would suggest gphoto2 (thats what the package is called in
>> my Debian distribution). It accesses my Fuji DX10 just fine.
>
> Well, that's what I'm trying to get running -- the latest and greatest
> gPhoto2. The year+ gPhoto2 I had (and cannot get) worked just fine on
> this box with these ports (there are two).

Either use COM1/ttyS0 for your camera or disable the winmodem so you can
use COM2/ttyS1. Then configure Gphoto to use COM1.. or COM2 if you
disable your winmodem.

Thanks to all for the help and advice; however, I still can't get this
thing going.

Just to be sure, I booted WIN98SE and checked. COM1 (/dev/ttyS0, I
think) is at 03f8 and is used for the camera. COM2 (/dev/ttyS1) is the
LT 56K winmodem at efff. I tried both the camera and modem and they both
work.

On the Linix side, setserial -G /dev/ttyS0 returns

/dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base 115200 spd_normal
skip_test

setserial -G /dev/ttyS1 returns

/dev/ttyS1 uart unknown port 0x02f8 irq 3 baud_base 115200 spd_normal
skip_test

Looking at links in /dev, I found these (put there by ltmodem-8.26a9
installation I think) and removed them

lrwxrwxrwx 1 root root 11 Oct 24 10:48 modem -> /dev/ttyLT0
lrwxrwxrwx 1 root root 10 Oct 24 10:48 modem2 -> /dev/ttyS1

lsmod shows the following, and it doesn't look like any serial drivers
are loaded.

Module Size Used by Not tainted
snd-pcm-oss 37252 0
snd-mixer-oss 11992 0 [snd-pcm-oss]
hpusbscsi 6916 0 (unused)
uhci 24496 0 (unused)
usbcore 58400 1 [hpusbscsi uhci]
snd-ens1371 11596 0
gameport 1452 0 [snd-ens1371]
snd-pcm 55904 0 [snd-pcm-oss snd-ens1371]
snd-timer 13252 0 [snd-pcm]
snd-page-alloc 6004 0 [snd-pcm]
snd-rawmidi 12512 0 [snd-ens1371]
snd-seq-device 3920 0 [snd-rawmidi]
snd-ac97-codec 37240 0 [snd-ens1371]
snd 27460 0 [snd-pcm-oss snd-mixer-oss snd-ens1371
snd-pcm snd-timer snd-rawmidi snd-seq-device snd-ac97-codec]
soundcore 3332 6 [snd]
3c59x 26832 1
pcmcia_core 40032 0
ide-scsi 9424 0
agpgart 39576 0 (unused)

At this point I really don't know what to do -- do I have to modprobe
something, do something in rc.modules, fiddle with some configure file,
or just give up? I think I've gotten myself confused enough that I'm
just lost and I'd really appreciate any advice.

--
In what is probably a vain attempt to get off SPAM lists, you'll have to
delete the nonsense in my address if you want to just hit reply; sorry
about that, but enough is enough!

Thomas Ronayne wrote:
> Thanks to all for the help and advice; however, I still can't get this
> thing going.
>
> Just to be sure, I booted WIN98SE and checked. COM1 (/dev/ttyS0, I
> think) is at 03f8 and is used for the camera. COM2 (/dev/ttyS1) is the
> LT 56K winmodem at efff. I tried both the camera and modem and they both
> work.
>
> On the Linix side, setserial -G /dev/ttyS0 returns
>
> /dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base 115200 spd_normal
> skip_test

Looks normal.

Mine:
/dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base 115200 spd_normal
skip_test

Works fine with a camera, IR remote for TV(xmms) and a palmpilot.

[snip]
>
> At this point I really don't know what to do -- do I have to modprobe
> something, do something in rc.modules, fiddle with some configure file,
> or just give up? I think I've gotten myself confused enough that I'm
> just lost and I'd really appreciate any advice.

Ok, it worked in 98 on COM1. Why don't you use COM1/ttyS0 in Linux?

What happens if you load Gphoto and set the port to /dev/ttyS0 and then
try to acces your camera?

Thomas Ronayne <tronaREMOVETHIS@ameritech.net> wrote:

>Thanks to all for the help and advice; however, I still can't get this
>thing going.
>
>Just to be sure, I booted WIN98SE and checked. COM1 (/dev/ttyS0, I
>think) is at 03f8 and is used for the camera. COM2 (/dev/ttyS1) is the
>LT 56K winmodem at efff. I tried both the camera and modem and they both
>work.
>
>On the Linix side, setserial -G /dev/ttyS0 returns
>
>/dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base 115200 spd_normal
>skip_test
>
>setserial -G /dev/ttyS1 returns
>
>/dev/ttyS1 uart unknown port 0x02f8 irq 3 baud_base 115200 spd_normal
>skip_test
>
>Looking at links in /dev, I found these (put there by ltmodem-8.26a9
>installation I think) and removed them
>
>lrwxrwxrwx 1 root root 11 Oct 24 10:48 modem -> /dev/ttyLT0
>lrwxrwxrwx 1 root root 10 Oct 24 10:48 modem2 -> /dev/ttyS1
>
>lsmod shows the following, and it doesn't look like any serial drivers
>are loaded.
>
>Module Size Used by Not tainted
>snd-pcm-oss 37252 0
>snd-mixer-oss 11992 0 [snd-pcm-oss]
>hpusbscsi 6916 0 (unused)
>uhci 24496 0 (unused)
>usbcore 58400 1 [hpusbscsi uhci]
>snd-ens1371 11596 0
>gameport 1452 0 [snd-ens1371]
>snd-pcm 55904 0 [snd-pcm-oss snd-ens1371]
>snd-timer 13252 0 [snd-pcm]
>snd-page-alloc 6004 0 [snd-pcm]
>snd-rawmidi 12512 0 [snd-ens1371]
>snd-seq-device 3920 0 [snd-rawmidi]
>snd-ac97-codec 37240 0 [snd-ens1371]
>snd 27460 0 [snd-pcm-oss snd-mixer-oss snd-ens1371
>snd-pcm snd-timer snd-rawmidi snd-seq-device snd-ac97-codec]
>soundcore 3332 6 [snd]
>3c59x 26832 1
>pcmcia_core 40032 0
>ide-scsi 9424 0
>agpgart 39576 0 (unused)
>
>At this point I really don't know what to do -- do I have to modprobe
>something, do something in rc.modules, fiddle with some configure file,
>or just give up? I think I've gotten myself confused enough that I'm
>just lost and I'd really appreciate any advice.

So what is the problem you are having?

The camera is connected to COM1 in windows which is /dev/ttyS0 in
Linux, and it (the serial port) is recognized by Linux so all is good
so far.

Which application are you running to access the camera? What happens
when you run it, configure it then try to access the camera?

If it worked under a previous version of Slackware then compatibility
isn't the issue.

--
------------------------------------------------
http://www3.sympatico.ca/dmitton
SPAM Reduction: Remove "x." from my domain.
------------------------------------------------

Thomas Ronayne <tronaREMOVETHIS@ameritech.net> writes:
>
> Just to be sure, I booted WIN98SE and checked. COM1 (/dev/ttyS0, I
> think) is at 03f8 and is used for the camera. COM2 (/dev/ttyS1) is the
> LT 56K winmodem at efff. I tried both the camera and modem and they both
> work.

OK. So the hardware is correct.

>
> /dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base 115200 spd_normal
> skip_test

OK. ttyS0 seems to be working and settings look normal.

> Looking at links in /dev, I found these (put there by ltmodem-8.26a9
> installation I think) and removed them
>
> lrwxrwxrwx 1 root root 11 Oct 24 10:48 modem -> /dev/ttyLT0
> lrwxrwxrwx 1 root root 10 Oct 24 10:48 modem2 -> /dev/ttyS1

If the permissions you gave before for /dev/ttyS0 are still
in force, i.e. 666, then you should be able to access the port
itself.

It seems to me that your software configuration to access the
camera is at fault, probably misconfigured.

In a case like this, I would work laterally, using other software
like minicom to see what should be happening when the camera is
connected. Or other hardware such as another computer or terminal
attached to the serial port to examine what happens when you
use the camera software.

(Generally, I end up slapping myself across the forehead and saying
"Doh!" )

Jack
--
Vlad, Heisenberg & Thomas: The originators of FUD.

Jack Strangio wrote:
> Thomas Ronayne <tronaREMOVETHIS@ameritech.net> writes:
>
>>Just to be sure, I booted WIN98SE and checked. COM1 (/dev/ttyS0, I
>>think) is at 03f8 and is used for the camera. COM2 (/dev/ttyS1) is the
>>LT 56K winmodem at efff. I tried both the camera and modem and they both
>>work.
>
>
> OK. So the hardware is correct.
>
>
>>/dev/ttyS0 uart 16550A port 0x03f8 irq 4 baud_base 115200 spd_normal
>>skip_test
>
>
> OK. ttyS0 seems to be working and settings look normal.
>
>
>>Looking at links in /dev, I found these (put there by ltmodem-8.26a9
>>installation I think) and removed them
>>
>>lrwxrwxrwx 1 root root 11 Oct 24 10:48 modem -> /dev/ttyLT0
>>lrwxrwxrwx 1 root root 10 Oct 24 10:48 modem2 -> /dev/ttyS1
>
>
> If the permissions you gave before for /dev/ttyS0 are still
> in force, i.e. 666, then you should be able to access the port
> itself.
>
> It seems to me that your software configuration to access the
> camera is at fault, probably misconfigured.
>
> In a case like this, I would work laterally, using other software
> like minicom to see what should be happening when the camera is
> connected. Or other hardware such as another computer or terminal
> attached to the serial port to examine what happens when you
> use the camera software.
>
> (Generally, I end up slapping myself across the forehead and saying
> "Doh!" )
>
> Jack

You know, the further I go the behinder I get -- it does look like the
serial ports are working, and it does look like libgphoto or gphoto2 are
at fault (although, for the life of me, I cannot see where or why --
this is a supported camera). I have an old Wyse 99GT laying around, and
I'm going to hook that up (if I can find a *$&#(# 9-pin cable!) and see
what's what.

Why, oh why, he cries, do all this stuff have to be so... interesting.

Thanks to you and all others trying to help out; I do appreciate the input.

--
In what is probably a vain attempt to get off SPAM lists, you'll have to
delete the nonsense in my address if you want to just hit reply; sorry
about that, but enough is enough!