1 |
On 24/04/06, Hans-Werner Hilse <hilse@×××.de> wrote: |
2 |
> Hi again, |
3 |
> |
4 |
> On Mon, 24 Apr 2006 15:09:43 +0100 Mick <michaelkintzios@×××××.com> |
5 |
> wrote: |
6 |
> |
7 |
> > I've got partial success! I can modprobe smsc-ircc2 which seems to |
8 |
> > successfully install the module: |
9 |
> > ===================== |
10 |
> > # modprobe -v smsc-ircc2 ircc_sir=0x3e8 ircc_irq=3 |
11 |
> > insmod /lib/modules/2.6.15-gentoo-r1/kernel/drivers/net/irda/smsc-ircc2.ko |
12 |
> > ircc_sir=0x3e8 ircc_irq=3 |
13 |
> |
14 |
> So it doesn't report an error here, correct? |
15 |
|
16 |
Yes, no error. The module is installed fine as long as I have run |
17 |
setserial first. |
18 |
|
19 |
> |
20 |
> > But only after I have run setserial: |
21 |
> > ===================== |
22 |
> > # setserial /dev/ttyS2 uart none |
23 |
> > ===================== |
24 |
> > |
25 |
> > The log shows: |
26 |
> > [...] |
27 |
> |
28 |
> OK, this probably means that you have the default serial driver |
29 |
> installed and it claims the device. The setserial is needed in order to |
30 |
> release the port again. You might want to try to have the default |
31 |
> serial driver not touch the IrDA port at all -- the simplest thing |
32 |
> would be to try running without serial plug support for the start. |
33 |
|
34 |
I am sure that if I could first improve my understanding with regards |
35 |
to how serial ports are being used, I would be able to find the |
36 |
solution much easier ;-) |
37 |
|
38 |
I have enabled serial drivers in the kernel because I intend to |
39 |
configure the winmodem for dialup connections, as well as being able |
40 |
to connect my Psion PDA on the serial port. |
41 |
|
42 |
How does it exactly work? What is the "serial plug support"? Are you |
43 |
referring to the kernel modules for serial ports? |
44 |
> |
45 |
> > Then I start /etc/init.d/irda: |
46 |
> > ===================== |
47 |
> > Apr 24 15:03:37 lappy irattach: tcgetattr: Input/output error |
48 |
> > Apr 24 15:03:37 lappy irattach: Stopping device /dev/ttyS2 |
49 |
> > Apr 24 15:03:37 lappy irattach: ioctl(SIOCGIFFLAGS): No such device |
50 |
> > Apr 24 15:03:37 lappy irattach: exiting ... |
51 |
> > ===================== |
52 |
> |
53 |
> This seems to indicate that you're trying to use /dev/ttyS2. But as |
54 |
> you're not using the serial port IrDA driver but an extended FIR driver |
55 |
> the device is probably "irda0" (and it doesn't have a path, as it's a |
56 |
> network device). Try "ifconfig -a", it should be listed. I don't have |
57 |
> IrDA on my current machine, so I can't tell what exact configuration |
58 |
> setting must be changed from "/dev/ttyS2" to "irda0". Start with this, |
59 |
> first. |
60 |
|
61 |
Actually, ifconfig gives me not ida0, but irlan0: |
62 |
======================== |
63 |
irlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 |
64 |
BROADCAST MULTICAST MTU:1500 Metric:1 |
65 |
RX packets:0 errors:0 dropped:0 overruns:0 frame:0 |
66 |
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 |
67 |
collisions:0 txqueuelen:4 |
68 |
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) |
69 |
======================== |
70 |
|
71 |
> > Should I perhaps run all this is a different order? |
72 |
> |
73 |
> As I said, try modprobing after the "setserial" call or even omit |
74 |
> serial support in the kernel. |
75 |
|
76 |
I will be rolling up a new kernel soon so I can try leaving out the |
77 |
serial support drivers. As I said above I desperately need to |
78 |
understand how the serial port functionality works in linux. If this |
79 |
is getting too much OT for the list please email me directly so that |
80 |
we don't consume bandwidth. :-) |
81 |
-- |
82 |
Regards, |
83 |
Mick |
84 |
|
85 |
-- |
86 |
gentoo-user@g.o mailing list |