SERIAL PORTS in KNOPPIX - comp.os.linux.misc

I have a hardware US-Robotics PCI modem; in Fedora core 1 it shows up as ttyS4 I/O port 2080 IRQ 11 as shown in dmesg & lspci -v. In KNOPPIX lspci -v shows the same port & IRQ however it is marked as [disabled] & there is no sign of it in dmesg. I have tried adding an entry for it in /var/lib/setserial/autoserial.conf but this doesn't help. Any ideas?

On Thu, 16 Mar 2006 19:03:55 -0500, Terry E. Dwyer <es290@ncf.ca> wrote: > I have a hardware US-Robotics PCI modem; in Fedora core 1 it shows up > as ttyS4 I/O port 2080 IRQ 11 as shown in dmesg & lspci -v. > > In KNOPPIX lspci -v shows the same port & IRQ however it is marked > as [disabled] & there is no sign of it in dmesg. > > I have tried adding an entry for it in > /var/lib/setserial/autoserial.conf but this doesn't help. > > Any ideas? Try lsmod in Fedora and Knoppix, to see if one uses modules that the other doesn't. They are different kernels 2.4.22/2.6.11 so lsmod is very different;Knoppix shows many more modules. The only thing that seems relevant is: serial_core 21120 1 8250 in Knoppix. I have noticed the same thing in Debian Mepis;they are both Debian based distributions so it's not surprising. The only serial ports that show up in dmesg are ttyS0/1 which just work for external or older ISA modems. Knoppix is not installed; it's just running from the live CD.

Terry E. Dwyer wrote: > On Thu, 16 Mar 2006 19:03:55 -0500, Terry E. Dwyer > <es290@ncf.ca> wrote: > >> I have a hardware US-Robotics PCI modem; in Fedora core 1 it shows up >> as ttyS4 I/O port 2080 IRQ 11 as shown in dmesg & lspci -v. >> >> In KNOPPIX lspci -v shows the same port & IRQ however it is marked >> as [disabled] & there is no sign of it in dmesg. >> >> I have tried adding an entry for it in >> /var/lib/setserial/autoserial.conf but this doesn't help. >> >> Any ideas? /dev/ttyS4 would make it the 5th serial port; I bet the knoppix kernel is compiled to support 4 ports and fedora is compiled to support > 4... --Yan

Terry E. Dwyer wrote: > > Yes I think that's correct about the no. of ports & I belive I got it to > work once in MEPIS 2.6.7 by adding it as ttyS2 in > /var/log/serial/serial.conf but this was more than a year ago & I can't > repeat it. You'd want /etc/serial.conf, not /var/log. Or use 'lspci -v' to get info about the card's I/O port and IRQ, then issue 'setserial /dev/ttyS2 port <ioport> irq <irq>' as root. You may need to use additional flags, too, see the man page for setserial. Since we're talking about Knoppix, I'm assuming you're using the Live CD so editing /etc/serial.conf isn't going to work. When you say you can't repeat what you did a year ago, where exactly is the difficulty? Is it just remembering what you did? Or is there some other obstacle? Is just that serial.conf is read-only on the CD?

John-Paul Stewart wrote: > Terry E. Dwyer wrote: > > > > Yes I think that's correct about the no. of ports & I belive I got it to > > work once in MEPIS 2.6.7 by adding it as ttyS2 in > > /var/log/serial/serial.conf but this was more than a year ago & I can't > > repeat it. > > You'd want /etc/serial.conf, not /var/log. Or use 'lspci -v' to get > info about the card's I/O port and IRQ, then issue 'setserial /dev/ttyS2 > port <ioport> irq <irq>' as root. You may need to use additional flags, > too, see the man page for setserial. Since we're talking about Knoppix, > I'm assuming you're using the Live CD so editing /etc/serial.conf isn't > going to work. > > When you say you can't repeat what you did a year ago, where exactly is > the difficulty? Is it just remembering what you did? Or is there some > other obstacle? Is just that serial.conf is read-only on the CD? Preface; I have a USR PCI 56K Modem as well installed on one machine here - but I use Ethernet through the installed NIC...so I don't use the modem while booted into Debian 3.1r1, nor have I had to set the modem up for use under linux (dual boot win98 box). FWIW - I've saved a KNOPPIX v3.6 bootup /etc/inittab output - for comparison to Debian when I was comparing the *default* runlevels (Knoppix=runlevel5 -- Debian=runlevel2). There's some info listed within which may prove useful for setting up Modems/Serials/Gettys; --------------------------------------------------------------------------------------- knoppix@ttyp0[knoppix]$ cat /etc/inittab # /etc/inittab: init(8) configuration. # $Id: inittab,v 1.9 2001/05/31 10:37:50 knopper Exp $ # The default runlevel. id:5:initdefault: # Boot-time system configuration/initialization script. # This is run first except when booting in emergency (-b) mode. si::sysinit:/etc/init.d/rcS # What to do in single-user mode. ~~:S:respawn:/bin/bash -login >/dev/tty1 2>&1 </dev/tty1 # /etc/init.d executes the S and K scripts upon change # of runlevel. # # Runlevel 0 is halt. # Runlevel 1 is single-user. # Runlevels 2-5 are multi-user. # Runlevel 6 is reboot. l0:0:wait:/etc/init.d/knoppix-halt l1:1:wait:/etc/init.d/rc 1 l2:2:wait:/etc/init.d/rc 2 l3:3:wait:/etc/init.d/rc 3 l4:4:wait:/etc/init.d/rc 4 l5:5:wait:/etc/init.d/rc 5 l6:6:wait:/etc/init.d/knoppix-reboot # What to do when CTRL-ALT-DEL is pressed. ca::ctrlaltdel:/etc/init 0 # Action on special keypress (ALT-UpArrow). kb::kbrequest:/bin/echo "Keyboard Request -- edit /etc/inittab to let this work." # What to do when the power fails/returns. pf::powerwait:/etc/init.d/powerfail start pn::powerfailnow:/etc/init.d/powerfail now po::powerokwait:/etc/init.d/powerfail stop # /sbin/getty invocations for the runlevels. # # The "id" field MUST be the same as the last # characters of the device (after "tty"). # # Format: # <id>:<runlevels>:<action>:<process> # 4 virtual consoles with immortal shells 1:12345:respawn:/bin/bash -login >/dev/tty1 2>&1 </dev/tty1 2:2345:respawn:/bin/bash -login >/dev/tty2 2>&1 </dev/tty2 3:2345:respawn:/bin/bash -login >/dev/tty3 2>&1 </dev/tty3 4:2345:respawn:/bin/bash -login >/dev/tty4 2>&1 </dev/tty4 # Example how to put a getty on a serial line (for a terminal) # #T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 #T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100 # Example how to put a getty on a modem line. # #T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3 #-- isdnutils begin # Change the lines below for your local setup and uncomment them. # Use "init q" to reread inittab. # look at the vboxgetty / mgetty manpage for more information (mgetty isn't # standard!) # #I0:2345:respawn:/usr/sbin/vboxgetty -d /dev/ttyI0 #I1:2345:respawn:/sbin/mgetty -D -m '"" ATZ OK AT&Eyourmsnhere OK AT&B512 OK' -s 38400 ttyI1 #-- isdnutils end # Run X Window session from CDROM in runlevel 5 w5:5:wait:/bin/sleep 2 x5:5:wait:/etc/init.d/xsession start --------------------------------------------------------------------------------------- I don't have much linux configuring experience, so perhaps others here can follow-up using any/some of the info I've posted. That said; once you get it up and running ok - you would likely want to use the "Save KNOPPIX configuration settings" option - found in "Utilities"....more info about all that; 1] http://groups.google.com/group/comp.os.linux.setup/msg/4bb3fd1deccde2f5?hl=en& 2] http://groups.google.com/group/comp.os.linux.misc/msg/8818c7370d226673?hl=en& 3] http://groups.google.com/group/comp.os.linux.setup/msg/4fc00fb8d9f30f1e?hl=en&

iforone wrote: > > FWIW - I've saved a KNOPPIX v3.6 bootup /etc/inittab output - for > comparison to Debian when I was comparing the *default* runlevels > (Knoppix=runlevel5 -- Debian=runlevel2). > > There's some info listed within which may prove useful for setting up > Modems/Serials/Gettys; Anything inittab pertaining to modems & getty would be if you're setting up dial-in access. To use your modem for dial-out connections, you don't need a getty nor anything else in inittab.

John-Paul Stewart wrote: > iforone wrote: > > There's some info listed within which may prove useful for setting up > > Modems/Serials/Gettys; > Anything inittab pertaining to modems & getty would be if you're setting > up dial-in access. To use your modem for dial-out connections, you > don't need a getty nor anything else in inittab. um...Ok - thanks -- I did not know that.. BTW - maybe this will help the OP ? $ uname -a Linux [hostname] 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i686 GNU/Linux $ sudo lspci -vv 0000:00:10.0 Communication controller: 5610 56K FaxModem WinModem Subsystem: 5610 56K FaxModem USR 56k Internal Voice WinModem (Models 297 4, 3529) Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Interrupt: pin A routed to IRQ 9 Region 0: Memory at f4001000 (32-bit, prefetchable) [disabled] [size=64] Region 1: Memory at f4010000 (32-bit, prefetchable) [disabled] [size=64K] Region 2: Memory at f4008000 (32-bit, prefetchable) [disabled] [size=32K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA PME(D0+,D1-,D2+,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=6 DScale=2 PME- I guess I could try to help further by booting into Knoppix LiveCD (only have v3.6 atm) -- wonder what version the OP is using (???). If anyone would like to give me some test commands to configure it -- lemme know - as I stated, I haven't even used the Winmodem yet in linux.

Similiar Articles:

VMWare Player running SCO 5.0.6? - comp.unix.sco.misc
... type=TSC/2.209786106Ghz serial 0x3f8-0x3ff 4 ... oss640a.001.000 remote: oss640a.001.000 200 PORT ... Also, try booting it with a live CD, such as Knoppix, and ...

Dumb terminal (non-telnet!!) via DB9 serial port - LinuxQuestions.org
Am trying out Knoppix on my Toshiba Tecra 550CDT. I would like to use it a console for my Cisco CCNP study lab, which I've done under Windows running

Serial Console when booting? - Knoppix Linux Boot CD, Download ...
I have a system that has no video card, CDROM, or floppy drive. There is only some USB ports, an HDD, some network cards and a serial console redirection port on the ...

7/11/2012 12:25:40 PM