Do I have to do something special to get the serial ports -- the "com1"
and "com2" ones -- to be available to Slackware 9.1? I've read through
the howto, though /etc/rc.d/rc.serial, and I'm a little lost (probably
from reading too much stuff and missing the simple one somewhere).
Something in rc.modules? Something else?
--
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:

> Do I have to do something special to get the serial ports -- the
> "com1" and "com2" ones -- to be available to Slackware 9.1? I've read
> through the howto, though /etc/rc.d/rc.serial, and I'm a little lost
> (probably from reading too much stuff and missing the simple one
> somewhere). Something in rc.modules? Something else?

depends, what do you want to do with them? login consoles? external
modem? serial mouse?

--
-alex49201

alex49201 wrote:
> Thomas Ronayne wrote:
>
>
>>Do I have to do something special to get the serial ports -- the
>>"com1" and "com2" ones -- to be available to Slackware 9.1? I've read
>>through the howto, though /etc/rc.d/rc.serial, and I'm a little lost
>>(probably from reading too much stuff and missing the simple one
>>somewhere). Something in rc.modules? Something else?
>
>
> depends, what do you want to do with them? login consoles? external
> modem? serial mouse?
>
Unload pictures from a H-P PhotoSmart C200 -- not a USB camera -- that
worked just fine with Slackware 8.

As an aside, I finally got the windmodem in this thing working (why, I
dunno, it's connected to a DSL hub, but there you are).

--
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!

>> depends, what do you want to do with them? login consoles? external
>> modem? serial mouse?
>>
> Unload pictures from a H-P PhotoSmart C200 -- not a USB camera -- that
> worked just fine with Slackware 8.

Never had to work with anything like that via serial, so all i can say
is check the basics (com ports enabled in bios?) then look into how the
device is being emualated..like some usb flash drives are emulated as a
scsi-device at /dev/sda, etc... Hope this helps...

--
-alex49201

To make sure the kernel has found your serial ports open a shell
window and type `dmesg | more` and look for lines like this (I
included the parallel port as well):

Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport_pc: Via 686A parallel port: io=0x378

So, in Linux COM1 = /dev/ttyS00 and COM2 = /dev/ttyS01.

Quite often aliases are made up for them to make them easier to
remember, so if you type `ls -l /dev/ | grep ttyS | more` you'll see
something like:

lrwxrwxrwx 1 root root 5 Oct 20 15:53fujifilm->ttyS1
lrwxrwxrwx 1 root root 5 Oct 15 22:51 modem -> ttyS0
lrwxrwxrwx 1 root root 5 Oct 14 05:20 pilot -> ttyS0
crw-rw-rw- 1 root dialout 4, 64 Oct 21 05:05 ttyS0
crw-rw-rw- 1 root dialout 4, 65 Sep 23 14:38 ttyS1

Which shows that my system set up a "modem" on /dev/ttyS0 (COM1)and my
camera on /dev/ttyS1 (COM2).

Now, I don't know why the first list has "00" and "01" and the second
"0" and "1" BUT it works! :-)

Thomas Ronayne <tronaREMOVETHIS@ameritech.net> wrote:

>Do I have to do something special to get the serial ports -- the "com1"
>and "com2" ones -- to be available to Slackware 9.1? I've read through
>the howto, though /etc/rc.d/rc.serial, and I'm a little lost (probably
>from reading too much stuff and missing the simple one somewhere).
>Something in rc.modules? Something else?

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

Doug Mitton wrote:

>
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
> SERIAL_PCI ISAPNP enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
> parport_pc: Via 686A parallel port: io=0x378
>
> So, in Linux COM1 = /dev/ttyS00 and COM2 = /dev/ttyS01.

Yeah, that's the way it was in Slackware 8 (and the camera does work on
COM1 in WIN98SE, for whatever that's worth).
>
>
dmesg shows:

fb0: VESA VGA frame buffer device
pty: 512 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT
SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
Real Time Clock Driver v1.10e

The ttyS' show up as:

lrwxrwxrwx 1 root root 10 Oct 24 10:48 modem2 -> /dev/ttyS1
lrwxrwxrwx 1 root root 5 Oct 18 14:37 pilot -> ttyS0
crw-rw-rw- 1 root uucp 4, 64 Jul 17 1994 ttyS0
crw-rw-rw- 1 root uucp 4, 65 Jul 17 1994 ttyS1

Modem2 is the link made by ltmodem-8.26a9 (to get the winmodem to work;
again, I don't know why I bothered other than it's there and it ought to
work). So, what the heck is a "pilot?"

I notice that the only ttyS that shows up in dmesg is ttyS00, but I've
no idea what that could mean.

It looks like something is missing, but for the life of me...

--
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 <tronaREMOVETHIS@ameritech.net> wrote:

>Doug Mitton wrote:
>
>>
>> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ
>> SERIAL_PCI ISAPNP enabled
>> ttyS00 at 0x03f8 (irq = 4) is a 16550A
>> ttyS01 at 0x02f8 (irq = 3) is a 16550A
>> parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
>> parport_pc: Via 686A parallel port: io=0x378
>>
>> So, in Linux COM1 = /dev/ttyS00 and COM2 = /dev/ttyS01.
>
>Yeah, that's the way it was in Slackware 8 (and the camera does work on
>COM1 in WIN98SE, for whatever that's worth).
>>
>>
>dmesg shows:
>
>fb0: VESA VGA frame buffer device
>pty: 512 Unix98 ptys configured
>Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT
>SHARE_IRQ SERIAL_PCI enabled
>ttyS00 at 0x03f8 (irq = 4) is a 16550A
>Real Time Clock Driver v1.10e
>
>The ttyS' show up as:
>
>lrwxrwxrwx 1 root root 10 Oct 24 10:48 modem2 -> /dev/ttyS1
>lrwxrwxrwx 1 root root 5 Oct 18 14:37 pilot -> ttyS0
>crw-rw-rw- 1 root uucp 4, 64 Jul 17 1994 ttyS0
>crw-rw-rw- 1 root uucp 4, 65 Jul 17 1994 ttyS1
>
>Modem2 is the link made by ltmodem-8.26a9 (to get the winmodem to work;
>again, I don't know why I bothered other than it's there and it ought to
>work). So, what the heck is a "pilot?"
>
>I notice that the only ttyS that shows up in dmesg is ttyS00, but I've
>no idea what that could mean.
>
>It looks like something is missing, but for the life of me...

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.

I think the "pilot" is a PalmPilot PDA device.

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.

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

>
>
> 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.
>
> I think the "pilot" is a PalmPilot PDA device.

Interesting -- I wonder where the heck that came from.
>
> 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).

It's the ring around the rosey rag.

Ah, well. I still have no idea what to do or how to do it but I'll keep
on keepin' on.

Thanks for the input.
>
> --
> ------------------------------------------------
> http://www3.sympatico.ca/dmitton
> SPAM Reduction: Remove "x." from my domain.
> ------------------------------------------------


--
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 <tronaREMOVETHIS@ameritech.net> writes:
>
> The ttyS' show up as:
>
> lrwxrwxrwx 1 root root 10 Oct 24 10:48 modem2 -> /dev/ttyS1
> lrwxrwxrwx 1 root root 5 Oct 18 14:37 pilot -> ttyS0
> crw-rw-rw- 1 root uucp 4, 64 Jul 17 1994 ttyS0
> crw-rw-rw- 1 root uucp 4, 65 Jul 17 1994 ttyS1
>
> Modem2 is the link made by ltmodem-8.26a9 (to get the winmodem to work;
> again, I don't know why I bothered other than it's there and it ought to
> work). So, what the heck is a "pilot?"

"pilot" is a historical reference to a Palm PDA (original name was "Palm
Pilot"), which used a serial cradle to 'sync' data between the PDA and the
PC. It's just a soft-link for convenience. Don't worry about it.


> I notice that the only ttyS that shows up in dmesg is ttyS00, but I've
> no idea what that could mean.
>
> It looks like something is missing, but for the life of me...

what information do you get with

setserial -G /dev/ttyS0


Is the baud rate set correctly? Are the interrupts correct?

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

Thomas Ronayne <tronaREMOVETHIS@ameritech.net> 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.
>>
>> I think the "pilot" is a PalmPilot PDA device.
>
>Interesting -- I wonder where the heck that came from.
>>
>> 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).
>
>It's the ring around the rosey rag.
>
>Ah, well. I still have no idea what to do or how to do it but I'll keep
>on keepin' on.
>
>Thanks for the input.

What is the problem? Your initial post just asked about looking for
the serial ports. It looks like you have one so that shouldn't be the
problem. Details?

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