We have now new Server Hardware witch don´t work with Suse 10.2, now we Upgrade to 11.2, but the Devolo Modem doesnt work with the Drivers vor 10.2, No Problem, this Modems are sold out, i had to search for other Modems
Now I Test an Softmodem with Motorola Chipset, Bad Luck
Then i Think, Try a Hardware Modem From US-Robotics, Expensive but working on Linux: USR802981-OEM
But don´t working on Suse 11.2
It can find an Pci Device, but no I/O Adress, i Copy the HWinfo Printout:
> Then i Think, Try a Hardware Modem From US-Robotics, Expensive but
> working on Linux: USR802981-OEM
> But don´t working on Suse 11.2
> It can find an Pci Device, but no I/O Adress,
> i Copy the HWinfo Printout:
>
> 25: PCI 301.0: 0700 Serial controller (16550)
Okay, so your modem looks just like a regular 16550 UART.
Do you have any /dev/ttyS* devices?
> If you had some Other Modem (internal Pci) witch works for DialIn Data
> Connections please sent me Type and Configs
I don’t have any internal modems, but I do have a multi-port serial card
for PCI. I’ll check what I did with thatone, it’s been a while since
it was in use.
Try talking to that port using minicom - given that ttyS0-3 are on their
standard addresses, it’s a pretty good bet that ttyS4 is your modem.
Try commands ATI0, ATI1 etc.
>> Try talking to that port using minicom - given that ttyS0-3 are on
>> their standard addresses, it’s a pretty good bet that ttyS4 is your
>> modem. Try commands ATI0, ATI1 etc.
>>
>>
>>
>
> Hi
>
> With minicom i Can´t start Connection, i Thing Error Layer8 (user),
> can you wrote some instructions
Okay -
you probably need to run minicom as root - “minicom -s”
Here you need to change the serial port to /dev/ttyS4, and maybe the
speed to 9600n8 (9600baud, 8bit, no-parity).
Then “Save as default”, and exit the settings.
The baudrate may not match your modems default setting - maybe you can
find that in the manual, otherwise you have to experiment. To change
the baudrate whilst in minicom, you hit Ctrl A-Z, then P (Comms
parameters). Try 1200, 2400, 9600, 19200 and 115200.
>
> I test it with all possible Speed Settings, Always offline, Initialize
> Modem gets no effect, no Answer on commands
>
> i Still Think The ttyS4 has wrong settings
I was hurrying off to work when I first replied to your initial post, so dodn’t have time for detailed response. Have you tried starting yast > network devices > modem to try and discover the modem? Most serial modems should be detected easily if using standard UART with /dev/ttyS* nodes present. Alternatively, try using the wvdialconf CLI utility to try to discover your serial modem.
The ‘lspci -v’ command can reveal more info concerning your modem hardware - in particular it can show which I/O ports are associated with that card (which can confirm if /dev/ttyS0 is associated with it for example).
03:01.0 Serial controller: U.S. Robotics Device 0152 (rev 02) (prog-if 02 [16550])
Subsystem: Exar Corp. Device 0129
Flags: fast devsel, IRQ 22
Memory at fe401000 (32-bit, non-prefetchable) [size=1]
in Yast at Network, Modem is no Device, in yast, Hardware, hardware information, there´s no Modem, only one pci device (serial us robotics), that had to be my modem
i Think i had to find the right Port before The modem can be detected
i dont test ist with wvdialconf jet, it´s planed next–[/size]
>
> Per Jessen;2183066 Wrote:
>> cekey wrote:
>>
>> >
>> > I test it with all possible Speed Settings, Always offline,
>> Initialize
>> > Modem gets no effect, no Answer on commands
>> >
>> > i Still Think The ttyS4 has wrong settings
>>
>> What does ‘setserial -G /dev/ttyS4’ say?
>> –
>> Per Jessen, Zürich (27.5°C)
>> ‘User:Pjessen - openSUSE’ (http://en.opensuse.org/User:Pjessen)
>
> i worote all printouts, for ttyS4: /dev/ttyS4, UART: 16550A, Port:
> 0xf100, IRQ: 17
>
Okay. Well, judging from your previous posting, you have two serial
ports in your machine - ttyS0 (presumably a regular serial port?), and
ttyS4 - presumably your PCI modem. Is there a way to manually
configure your PCI modem - a utility or something?
If you do not have a regular serial port, I would also try ttyS0 and see
if you can talk to it with minicom.
> Youre right, one Onboard Serial port
>
> The Modem From Us robotics… They say on website it works with Linux
> from Kernel 2.6, Tere are no Tools and they give no Support
Okay, it was just a wild guess. Config utilities are really pre ISA
Plug-n-Play, but you never know.
Check /var/log/boot.msg - look for 16550. It might look like this:
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
<6>serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
<6>00:0e: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
<4>PCI: Enabling device 0000:00:0b.0 (0000 -> 0001)
<7>PCI: setting IRQ 11 as level-triggered
<6>PCI: Assigned IRQ 11 for device 0000:00:0b.0
<6>PCI: Sharing IRQ 11 with 0000:00:04.2
<6>0000:00:0b.0: ttyS4 at I/O 0xfc98 (irq = 11) is a 16550A
<6>0000:00:0b.0: ttyS5 at I/O 0xfca0 (irq = 11) is a 16550A
<6>0000:00:0b.0: ttyS6 at I/O 0xfca8 (irq = 11) is a 16550A
<6>0000:00:0b.0: ttyS7 at I/O 0xfcb0 (irq = 11) is a 16550A
<6>0000:00:0b.0: ttyS1 at I/O 0xfcb8 (irq = 11) is a 16550A
<6>0000:00:0b.0: ttyS2 at I/O 0xfce0 (irq = 11) is a 16550A
[snip]
Configuring serial ports…
/dev/ttyS0 at 0x03f8 (irq = 4) is a 16550A
/dev/ttyS1 at 0xfcb8 (irq = 11) is a 16550A
/dev/ttyS2 at 0xfce0 (irq = 11) is a 16550A
/dev/ttyS4 at 0xfc98 (irq = 11) is a 16550A
/dev/ttyS5 at 0xfca0 (irq = 11) is a 16550A
/dev/ttyS6 at 0xfca8 (irq = 11) is a 16550A
/dev/ttyS7 at 0xfcb0 (irq = 11) is a 16550A
Configured serial ports
If you don’t have anything like that, check if ‘serial’ is listed
by ‘lsmod’.
I’m puzzled that your lspci output did not mention:
Kernel driver in use: serial
Finally, try ‘modprobe serial’ and let us know what happens -
maybe post the last few lines of dmesg.