puppyserialdetect is a bit slower than the latest puppyinputdetectFULL, and (puppyserialdetect) may be hazardous to some systems, i.e there are outstanding reports that it freezes some systems on boot, probably by not exiting.

Basically it just scans the kernel info about serial access ports, which is here /proc/tty/driver/serial which might be enough for you?
cat /proc/tty/driver/serial

Attached is source code of latest incarnation.

To detect the serial ports, use puppyinputdetectFULL with -swm command line options. Use -d for debug mode.

puppyinputdetectFULL is less likely to have problems as it does not attempt the complicated modem-detection any more (its removed), and also a full scan is not attempted unless -f is supplied on command line.

puppyinputdetectFULL will verify (and correct) any /dev/ttyS* nodes to make sure they are valid, and tell you if there is a mouse attached by sending/recving commands to the port, but this might confuse your device if you run it while it is being used.

puppyinputdetectFULL is less likely to have problems as it does not attempt the complicated modem-detection any more (its removed), and also a full scan is not attempted unless -f is supplied on command line.

puppyinputdetectFULL will verify (and correct) any /dev/ttyS* nodes to make sure they are valid, and tell you if there is a mouse attached by sending/recving commands to the port, but this might confuse your device if you run it while it is being used.

Regards
Jesse

Sorry for my delayd reply, been traveling and Internet access at several of the places we stayed was useless.

I have downloaded and extracted your serial detection app but am not certain how I should proceed. I always forget the correct steps to install .gz's

The moments I can grab to deal with things like this are often separated by weeks, sometimes months, so I cannot keep it in my head. (I have another problem with CUPS that I need to return to tomorrow - cannot print since I upgraded to 4.11 and then 4.12, was OK in 4.0 ... but that's another thread! Also cannot talk to my USB-serial adapter. Sigh.)

I have been printing and saving things lately to my Linux ring binder so if you'd please walk me through this I will do so in order to have it for the next .gz I need to handle.

In chasing down my serial port challenges I stumbled upon the following URL's, the first is clearly related, the third URL I just wanted to post in case someone knew of a thread where I should move it in case it is of use to someone chasing a relted problem.

http://www.ftdichip.com/Drivers/D2XX.htm
This appears to be the driver I need for my USB-Serial-RadioTransceiver project.

Laptops which use dynamic IP address assignment via DHCP have the problem that the boot process is much longer when no wire is connected to the Ethernet card. This is because the startup scripts have to wait for the DHCP request to time out.

ethwireck can detect if the physical layer of the Ethernet is up. This can then be used in the init script for your network card to determine whether or not an interface should be brought up. In other words a timeout is avoided.

ethwireck is similar to mii-tool but it can handle more ethernet cards (not only drivers with an mii interface).

Note: I discovered recently that ethwireck does not work with all cards as expected. The problem seems to be that some cards support the interface but do not report the status as expected. I am currently invesitgating this problem. Wait for ethwireck-1.3.

Just a quick observation...we must have installed puppy on well over three hundred computers now, and not once has puppy ever failed to correctly detect the mouse. This has been mostly with 2.15ce and earler versions. I do realise there is an occaisional report of serialdetect failing to detect mice on the forum, and it must happen at some point...but isnt that where a forum comes in?

One of the few things that seem to be a step backward in the new puppy is adding an additional screen to the first setup (xorgwizard?) to confirm the type of mouse. Adding an extra setup screen will lose us more users through decreased useability/complexity than the very few that serialdetect doesnt work for. Perhaps the serialdetect screen should be accessed separately from the xorgwizard with a command like "setmouse"?

That being said, I am glad that more work is being done to improve serialdetect, should it ever fail for me in the future!_________________Puppy Linux's Mission

I don't have any problems with the mouse, it is access to the serial port for access to/control of external devices e.g. programming a radio scanner or setting up my weather station.

I have the software I need but cannot get recognition of serial/comm ports.

I keep hoping that there is an app out there in the Linux worl that brings up a troubleshooting window, detects the hardware, then walks one through what settings are incorrect to re-establish reliable communications.

I have tried a USB-to-Serial and direct Serial connection but nothing works.

I am also unable to access any USB-based printer from this laptop, local or remote, and presume that the problems have a common denominator. (I had no problems with printers like this under 4.0 and prior.)

I do recall in a prior version, not sure if 4.0 or 4.11, there was a question about checking for Serial devices in the Boot stage.

The idea was to save time by skipping that check. I may have done so.

Is it possible that in the version upgrade that setting was maintained?

Anyone remember where that would have been set and how I might undo it if it has in fact been set, please?_________________Thanks! DavidHome page: http://nevils-station.comDon't googleSearch!http://duckduckgo.com
TahrPup64 & Lighthouse64-b602 & JL64-603

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum