Quote:
Originally Posted by WrightExposure
I think I need to run the makedev command. I know i haven't done and the person that helped me setup the box I don't think did either.
|
In the past running
makedev would not normally be needed; creation of the
/dev entries would be handled at installation. And I believe FC5 uses
udev to handle the
dev entries, so that
makedev would be completely inappropriate since
udev creates the
/dev entries automatically as devices are detected.
I debated about mentioning
udev in my first post but decided it might just make things too complicated at that point.
Udev started some where in the 2.6 kernel series (I just spent about 15 minutes unsuccessfully trying to determine at what point). Unfortunately virtually all of my experience is with 2.2 and 2.4 kernels. I do have a several month old version of DSL-N which uses a 2.6.12 kernel. But as best as I can determine it does not use
udev.
The info I posted earlier was from a 2.2 kernel. A little while ago I booted the same machine using DSL-N with its 2.6.12 kernel. It isn't configured to create log files, but
dmesg output did contain the following:
Code:
Serial: 8250/16550 driver $Revision: 1.90 $ 14 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
ttyS3 at I/O 0x2e8 (irq = 3) is a 16550A
So what did your log file say about uarts?
One thing you can try is running the
setserial command
as root as shown:
Code:
[root@Vectra jim]# setserial /dev/ttyS0
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
If it lists a number after "UART:" then it is surely seeing your uart. If it lists "unknown" then you might have trouble. If the entry
/dev/ttyS0 does not even exist then you should get a "/dev/ttyS0: No such file or directory" error.
You can also see what you can find out in the GUI that
shrikant.odugoudar mentioned. I am not up to date on the GUI interfaces.