Thanks for the advice, it helped me figure out how to get the I/O from lspci
-v. I've got the modem *sort of* working now: It seems to only work on IRQ
0 (shared with the timer), and at speeds no higher than 9600 baud. Examples:
# lspci -v
:02:0b.0 Serial controller: 5610 56K FaxModem 56K
Thanks for the advice, it helped me figure out how to get the I/O from lspci
-v. I've got the modem *sort of* working now: It seems to only work on IRQ
0 (shared with the timer), and at speeds no higher than 9600 baud. Examples:
# lspci -v
:02:0b.0 Serial controller: 5610 56K FaxModem 56K
Levi Waldron wrote:
>
> I just went out and bought a brand new, fully hardware PCI modem (for
> $68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
> to get assigned a ttyS* port during the boot process. The Modem HOWTO
> gives some tips for finding out the essential infor
Levi Waldron wrote:
I just went out and bought a brand new, fully hardware PCI modem (for
$68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
to get assigned a ttyS* port during the boot process. The Modem HOWTO
gives some tips for finding out the essential information, then
Levi Waldron wrote:
I just went out and bought a brand new, fully hardware PCI modem (for
$68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
to get assigned a ttyS* port during the boot process. The Modem HOWTO
gives some tips for finding out the essential information, then
I just went out and bought a brand new, fully hardware PCI modem (for
$68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
to get assigned a ttyS* port during the boot process. The Modem HOWTO
gives some tips for finding out the essential information, then says
without givin
6 matches
Mail list logo
