This is a discussion on Serial Ports not found within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Kernel 2.6.9 Slackware 10 Soyo KT400 MB with 2 internal ports. After years, I decided to fire up an ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Kernel 2.6.9 Slackware 10 Soyo KT400 MB with 2 internal ports. After years, I decided to fire up an old external modem. Under kernel 2.4.2x, both ttyS0 and ttyS1 devices were created on boot and worked fine. Under 2.6.9, udev does NOT seem to be picking up these. I have serial support built into the kernel. In /proc/devices, under device 4, which should be the serial ports, I get 4 /dev/vc/0 4 tty So, udev IS getting the virtual and real console, just not the comm ports. Any ideas? Thx. |
| ||||
| Peter wrote: > Kernel 2.6.9 > Slackware 10 > Soyo KT400 MB with 2 internal ports. > Follow up: 1) I made the serial drivers modules, not built in to the kernel 2) I upgraded udev from 026 to 042 3) on reboot, still ttyS* devices not created. However, if I manually did modprobe 8250, then that module and the serial_core module loaded. In addition, the devices /dev/tts/0, 1, 2...etc were created with links from /dev/ttyS0,1,2, etc. Other than embedding commands in my rc.local startup script, is there a way to get these things to load on startup automatically? Thx |