The next few things I'd check... driver and config... - Is this a default kernel or a custom compile? - Does it have the serial driver compiled-in? # uname -a Will give us kernel name and if it's a FC kernel RPM, this will give you kernel serial config parameters; # grep "SERIAL" /boot/config-`uname -r` I'm guessing you're talking about STD mobo serial ports... in that case, they are typically 16C550 compatible UARTs which should are usually on IRQ 3 & 4 @ IO Addresses 2f8/3f8/2e8/etc... all those settings can usually be set in BIOS... since these work in DOS, let's assume they are correct and working... they won't be listed by interrupt, but try ioports... # cat /proc/ioports | grep serial At least we can see if the hardware is "there and functional" (still not functioning - but the UART can be addressed by the kernel). You could be getting an IOPort address conflict but that would be pretty rare and very odd given normal operation and hardware. The skinny: When "ls /proc/tty/driver" lists "rfcomm" and nothing else, that implies the 8250/16C550 default serial driver is not loaded for some reason - could be it didn't detect the UART, IO/IRQ conflicts, etc. You have functional hardware (as shown by DOS) but getting the hardware to work with Linux and all the drivers/devices that are enabled/loaded by the kernel... Another thought - scan /var/log/messages and the dmesg for any weird ttyS* or serial driver messages... I hope something in here provides a lead to work from... - Gareth -----Original Message----- From: fedora-list-bounces@xxxxxxxxxx [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Erik Grootjans Sent: Wednesday, March 28, 2007 1:50 PM To: For users of Fedora Subject: Re: Minicom cant get info from /dev/ttyS0 and ttyS1 Hi, Thanks for your mail. on dmesg | grep tty i get : Xen virtual console succesfully installed on ttyS0 (That can explain why it is not weorking on ttyS0, but than why did it not work on ttyS1 --> i did get an device not found when i started minicom with a configuration) on # cat /proc/tty/driver/serial file or dir not found and a ls /proc/tty/driver i get: rfcomm So serial does NOT exist What do i have to do about that ??? compile a new kernel ??? Erik ----- Original Message ----- From: "Gareth Howlett" <gareth.howlett@xxxxxxxxxxxxxx> To: "For users of Fedora" <fedora-list@xxxxxxxxxx> Sent: Wednesday, March 28, 2007 8:48 PM Subject: RE: Minicom cant get info from /dev/ttyS0 and ttyS1 > Erik Grootjans wrote: > > Thanks > > > > But i m only in the first stage --> configuring as root > > and at this moment even that does not work. > > (as root im owner of the device - so rights must not be a problem, i > > guess > > > > The next step is then to get it working as an user. > > > > Erik > > > > Another thing to check - if the kernel actually detected those ports... > having dev nodes laying around but not attached to anything is not out > of the question. > > # dmesg | grep tty > > That should do the trick for detection... whether or not the uart is > properly supported can be checked by examining the output of: > > # cat /proc/tty/driver/serial > > - Gareth > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
