1 |
On Saturday 02 September 2006 20:29, d2clon wrote: |
2 |
> hi: |
3 |
> |
4 |
> This is my sequence: |
5 |
> ------------------------------------------ |
6 |
> biit ~ # setserial /dev/ttyS2 uart none |
7 |
> /dev/ttyS2: No such device or address |
8 |
|
9 |
OK, this is telling you that ttyS2 is not the correct COM port for your irda |
10 |
device. However, looking at your dmesg there's only two serial ports |
11 |
reported, so ttS2 is not defined: |
12 |
=========================================== |
13 |
serio: i8042 AUX port at 0x60,0x64 irq 12 |
14 |
serio: i8042 KBD port at 0x60,0x64 irq 1 |
15 |
=========================================== |
16 |
You need to enable some virtual (COM) ports. In your kernel configuration you |
17 |
will need to set additional serial ports. Go to: |
18 |
|
19 |
Device drivers --> Character devices --> Serial Drivers --> |
20 |
|
21 |
and either enter a number higher than just 4 under: |
22 |
|
23 |
(4) Maximum number of 8250/16550 serial ports |
24 |
(4) Number of 8250/16550 serial ports to register at runtime |
25 |
|
26 |
or better, on the latest stable kernel select: |
27 |
|
28 |
[*] Extended 8250/16550 serial driver options |
29 |
[*] Support more than 4 legacy serial ports |
30 |
[*] Support for sharing serial interrupts |
31 |
|
32 |
If when you reboot you keep getting the same error then you need to try |
33 |
different ttySx number, where x is 0,1,2,3,4, . . . Note that some numbers |
34 |
could cause IRQ conflicts and could crash your machine. In that case reboot |
35 |
and try again. |
36 |
|
37 |
> biit ~ # /sbin/modprobe smsc_ircc2 |
38 |
> FATAL: Error inserting smsc_ircc2 |
39 |
> (/lib/modules/2.6.15-gentoo-r1/kernel/drivers/net/irda/smsc-ircc2.ko): |
40 |
> No such device |
41 |
|
42 |
Unless the COM port has been set correctly for your irda any module selection |
43 |
will fail. |
44 |
|
45 |
> ------------------------------------------ |
46 |
> |
47 |
> When i execute the next sentence: |
48 |
> ------------------------------------------- |
49 |
> biit ~ # irattach irda0 -s |
50 |
> ------------------------------------------- |
51 |
> |
52 |
> This is what appear into syslog: |
53 |
> ------------------------------------------- |
54 |
> Sep 2 21:53:04 localhost irattach: executing: '/sbin/modprobe irda0' |
55 |
> Sep 2 21:53:04 localhost irattach: + FATAL: Module irda0 not found. |
56 |
> Sep 2 21:53:04 localhost irattach: Trying to load module irda0 exited |
57 |
> with status 1 |
58 |
> Sep 2 21:53:04 localhost irattach: executing: 'echo biit > |
59 |
> /proc/sys/net/irda/devname' |
60 |
> Sep 2 21:53:04 localhost irattach: executing: 'echo 1 > |
61 |
> /proc/sys/net/irda/discovery' |
62 |
> Sep 2 21:53:04 localhost irattach: Starting device irda0 |
63 |
> Sep 2 21:53:04 localhost irattach: ioctl(SIOCGIFFLAGS): No such device |
64 |
> Sep 2 21:53:04 localhost irattach: Stopping device irda0 |
65 |
> Sep 2 21:53:04 localhost irattach: ioctl(SIOCGIFFLAGS): No such device |
66 |
> Sep 2 21:53:04 localhost irattach: exiting ... |
67 |
> ---------------------------------------------- |
68 |
|
69 |
Ditto. |
70 |
|
71 |
> > Does your dmesg show anything? e.g. mine shows: |
72 |
> > =================================================== |
73 |
> > found SMC SuperIO Chip (devid=0x0e rev=01 base=0x002e): LPC47N252 |
74 |
> > =================================================== |
75 |
> |
76 |
> This is my dmesg: |
77 |
> http://paste.lisp.org/display/25171 |
78 |
|
79 |
OK, it would be really strange if an irda chip of your type was detected just |
80 |
out of thin air without COM ports set in the kernel. Thankfully, it isn't. |
81 |
|
82 |
> > Other laptops are more straight forward, but mine seems to be of the more |
83 |
> > difficult variety . . . |
84 |
> |
85 |
> So mine. :) |
86 |
|
87 |
Some old laptops are even more problematic . . . |
88 |
|
89 |
-- |
90 |
Regards, |
91 |
Mick |