1 |
On Friday 18 May 2007 04:08, Walter Dnes wrote: |
2 |
> On Sun, May 13, 2007 at 04:18:54PM -0400, waltdnes@××××××××.org wrote |
3 |
> |
4 |
> > My ADSL connection had a short outage yesterday. I discovered, to my |
5 |
> > consternation, that my machine's internal modem wasn't being picked up. |
6 |
> > This is a 1999 Dell PIII that refuses to die. The PCI modem has worked |
7 |
> > in the past under Redhat and Gentoo. I am aware that I have to allocate |
8 |
> > more than 4 serial ports in make menuconfig. "lspci -v" shows... |
9 |
> > |
10 |
> > 00:10.0 Serial controller: 3Com Corp, Modem Division 56K FaxModem Model |
11 |
> > 5610 (rev 01) (prog-if 02 [16550]) Subsystem: 3Com Corp, Modem Division |
12 |
> > Unknown device baba Flags: medium devsel, IRQ 9 |
13 |
> > I/O ports at 1430 [size=8] |
14 |
> > Capabilities: [dc] Power Management version 2 |
15 |
> |
16 |
> A rather heavy-handed solution was to emerge "setserial" and execute |
17 |
> |
18 |
> setserial /dev/ttyS4 port 0x1430 irq 9 |
19 |
> |
20 |
> This initializes the port, and pppconfig now finds /dev/ttyS4 when |
21 |
> doing an auto-probe. And dialup works. This is nice to know, because |
22 |
> I'll be moving later this summer, and may be dialup-only for a few weeks |
23 |
> depending on circumstances. |
24 |
> |
25 |
> I've copied the above setserial command to /etc/conf.d/local.start to |
26 |
> ensure it's automatically executed at bootup. |
27 |
|
28 |
I have to run setserial manually to get my IrDA recognised. Not sure if this |
29 |
is a change in later kernels and/or udev. I would have thought that it would |
30 |
be picked up by the kernel/udev without much drama, but it seems that |
31 |
setserial is needed hereafter? |
32 |
-- |
33 |
Regards, |
34 |
Mick |