Also check your bios settings ( the basic computer settings).... many motherboards allow you to assign or disable onboard serial ports, or assign them irq settings, which will affect the ttyS* numbers.
Additionally you can test the availability of ports without the perl module,
open(PORT,"+>/dev/ttyS1") or die "Couldn't open serial port\n";
# etc etc
If you have some spare diskdpace, and can take the time to setup a dual boot, try a full-featured OS like OpenSuSE. I found that it is the best at finding and setting up hardware.
You might also want to look in your /dev after booting and see what
ttyS* links there are. Some distros do it differently, they may be real devices or links to some subdir like tts/*
Finally if you don't get the chipset recognized, because it is uncommon, or your distro didn't make a module for it, you can do an lspci (assuming it's a pci card) or hwinfo, etc., to get a list of the chipsets. Then you can google for the kernel patch or module to enable that chipset.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.