Re: [gentoo-user] Re: IrDA crashes every time
Hi, On Sun, 23 Apr 2006 13:47:24 +0200 Mick [EMAIL PROTECTED] wrote: Well, I've tried passing all sort of different parameters to the module but it comes back with errors: [...] Well, there are two things left I would try: #1: I remember some kind of findchip utility (try that name) that comes with irda-utils. It can print suggested settings. #2: Try IrPort drivers (unfortunately you'll be restricted to SIR, max. #115kBit) -hwh -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: IrDA crashes every time
On 24/04/06, Hans-Werner Hilse [EMAIL PROTECTED] wrote: Hi, On Sun, 23 Apr 2006 13:47:24 +0200 Mick [EMAIL PROTECTED] wrote: Well, I've tried passing all sort of different parameters to the module but it comes back with errors: [...] Well, there are two things left I would try: #1: I remember some kind of findchip utility (try that name) that comes with irda-utils. It can print suggested settings. #2: Try IrPort drivers (unfortunately you'll be restricted to SIR, max. #115kBit) I've got partial success! I can modprobe smsc-ircc2 which seems to successfully install the module: = # modprobe -v smsc-ircc2 ircc_sir=0x3e8 ircc_irq=3 insmod /lib/modules/2.6.15-gentoo-r1/kernel/drivers/net/irda/smsc-ircc2.ko ircc_sir=0x3e8 ircc_irq=3 = But only after I have run setserial: = # setserial /dev/ttyS2 uart none = The log shows: = Apr 24 13:25:18 lappy found SMC SuperIO Chip (devid=0x0e rev=01 base=0x002e): LPC47N252 Apr 24 13:25:18 lappy SMsC IrDA Controller found Apr 24 13:25:18 lappy IrCC version 2.0, firport 0x100, sirport 0x3e8 dma=1, irq=3 Apr 24 13:25:18 lappy No transceiver found. Defaulting to Fast pin select Apr 24 13:25:18 lappy IrDA: Registered device irda = Then I start /etc/init.d/irda: = Apr 24 15:03:37 lappy irattach: tcgetattr: Input/output error Apr 24 15:03:37 lappy irattach: Stopping device /dev/ttyS2 Apr 24 15:03:37 lappy irattach: ioctl(SIOCGIFFLAGS): No such device Apr 24 15:03:37 lappy irattach: exiting ... = findchip returns nothing. irdadump returns nothing. cat /proc/net/irda/discovery returns: IrLMP: Discovery log: . . . nothing. Should I perhaps run all this is a different order? What else could I try? -- Regards, Mick -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: IrDA crashes every time
Hi again, On Mon, 24 Apr 2006 15:09:43 +0100 Mick [EMAIL PROTECTED] wrote: I've got partial success! I can modprobe smsc-ircc2 which seems to successfully install the module: = # modprobe -v smsc-ircc2 ircc_sir=0x3e8 ircc_irq=3 insmod /lib/modules/2.6.15-gentoo-r1/kernel/drivers/net/irda/smsc-ircc2.ko ircc_sir=0x3e8 ircc_irq=3 So it doesn't report an error here, correct? But only after I have run setserial: = # setserial /dev/ttyS2 uart none = The log shows: [...] OK, this probably means that you have the default serial driver installed and it claims the device. The setserial is needed in order to release the port again. You might want to try to have the default serial driver not touch the IrDA port at all -- the simplest thing would be to try running without serial plug support for the start. Then I start /etc/init.d/irda: = Apr 24 15:03:37 lappy irattach: tcgetattr: Input/output error Apr 24 15:03:37 lappy irattach: Stopping device /dev/ttyS2 Apr 24 15:03:37 lappy irattach: ioctl(SIOCGIFFLAGS): No such device Apr 24 15:03:37 lappy irattach: exiting ... = This seems to indicate that you're trying to use /dev/ttyS2. But as you're not using the serial port IrDA driver but an extended FIR driver the device is probably irda0 (and it doesn't have a path, as it's a network device). Try ifconfig -a, it should be listed. I don't have IrDA on my current machine, so I can't tell what exact configuration setting must be changed from /dev/ttyS2 to irda0. Start with this, first. Should I perhaps run all this is a different order? As I said, try modprobing after the setserial call or even omit serial support in the kernel. -hwh -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: IrDA crashes every time
On 24/04/06, Hans-Werner Hilse [EMAIL PROTECTED] wrote: Hi again, On Mon, 24 Apr 2006 15:09:43 +0100 Mick [EMAIL PROTECTED] wrote: I've got partial success! I can modprobe smsc-ircc2 which seems to successfully install the module: = # modprobe -v smsc-ircc2 ircc_sir=0x3e8 ircc_irq=3 insmod /lib/modules/2.6.15-gentoo-r1/kernel/drivers/net/irda/smsc-ircc2.ko ircc_sir=0x3e8 ircc_irq=3 So it doesn't report an error here, correct? Yes, no error. The module is installed fine as long as I have run setserial first. But only after I have run setserial: = # setserial /dev/ttyS2 uart none = The log shows: [...] OK, this probably means that you have the default serial driver installed and it claims the device. The setserial is needed in order to release the port again. You might want to try to have the default serial driver not touch the IrDA port at all -- the simplest thing would be to try running without serial plug support for the start. I am sure that if I could first improve my understanding with regards to how serial ports are being used, I would be able to find the solution much easier ;-) I have enabled serial drivers in the kernel because I intend to configure the winmodem for dialup connections, as well as being able to connect my Psion PDA on the serial port. How does it exactly work? What is the serial plug support? Are you referring to the kernel modules for serial ports? Then I start /etc/init.d/irda: = Apr 24 15:03:37 lappy irattach: tcgetattr: Input/output error Apr 24 15:03:37 lappy irattach: Stopping device /dev/ttyS2 Apr 24 15:03:37 lappy irattach: ioctl(SIOCGIFFLAGS): No such device Apr 24 15:03:37 lappy irattach: exiting ... = This seems to indicate that you're trying to use /dev/ttyS2. But as you're not using the serial port IrDA driver but an extended FIR driver the device is probably irda0 (and it doesn't have a path, as it's a network device). Try ifconfig -a, it should be listed. I don't have IrDA on my current machine, so I can't tell what exact configuration setting must be changed from /dev/ttyS2 to irda0. Start with this, first. Actually, ifconfig gives me not ida0, but irlan0: irlan0Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:4 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Should I perhaps run all this is a different order? As I said, try modprobing after the setserial call or even omit serial support in the kernel. I will be rolling up a new kernel soon so I can try leaving out the serial support drivers. As I said above I desperately need to understand how the serial port functionality works in linux. If this is getting too much OT for the list please email me directly so that we don't consume bandwidth. :-) -- Regards, Mick -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: IrDA crashes every time
Hi, On Mon, 24 Apr 2006 17:50:37 +0100 Mick [EMAIL PROTECTED] wrote: Yes, no error. The module is installed fine as long as I have run setserial first. Hm, that's how it should be with fast infrared drivers. All OK, then, I guess. You might want to try to have the default serial driver not touch the IrDA port at all -- the simplest thing would be to try running without serial plug support for the start. I am sure that if I could first improve my understanding with regards to how serial ports are being used, I would be able to find the solution much easier ;-) I have enabled serial drivers in the kernel because I intend to configure the winmodem for dialup connections, as well as being able to connect my Psion PDA on the serial port. You need serial drivers (what I called serial plug support before) for the latter. The winmodem will probably use its own driver that provides a serial device which is functionally equal to the ones from the serial driver - but does not depend on the serial driver. But for actually using the real serial ports on the back of your PC you'll have to use the standard serial drivers. So no need for recompiling here, the setserial uart none should suffice. An option that's left would be compiling both IrDA drivers and serial device drivers as modules and probing IrDA first and serial second. How does it exactly work? What is the serial plug support? Are you referring to the kernel modules for serial ports? Yes, I was. This seems to indicate that you're trying to use /dev/ttyS2. But as you're not using the serial port IrDA driver but an extended FIR driver the device is probably irda0 (and it doesn't have a path, as it's a network device). Try ifconfig -a, it should be listed. I don't have IrDA on my current machine, so I can't tell what exact configuration setting must be changed from /dev/ttyS2 to irda0. Start with this, first. Actually, ifconfig gives me not ida0, but irlan0: [...] Hm, that's not how it should be. There should definately be the irda0, too. That's the device the smsc FIR driver should provide. I just had a look at the sources of the driver you're using (smsc-ircc2) and it indicates that the error message No transceiver found. Defaulting to Fast pin select may be an effect of a wrong ircc_fir setting. But I can't help much further, here. The only suggestion left, obviously not the best one, is to keep away from FIR and use SIR instead. As you'll be using the standard serial device driver anyway, you can then compile the IrTTY device driver instead of smsc-ircc2. I will be rolling up a new kernel soon so I can try leaving out the serial support drivers. As I said above I desperately need to understand how the serial port functionality works in linux. If this is getting too much OT for the list please email me directly so that we don't consume bandwidth. :-) I don't suggest leaving out the serial drivers, as you'll need them for the Psion connection. And reg. list traffic: You'll need this audience if further problems arise as I'm at the end of my wisdom right here ;-) -hwh -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: IrDA crashes every time
On 23/04/06, Hans-Werner Hilse [EMAIL PROTECTED] wrote: Hi, On Sun, 23 Apr 2006 02:17:20 +0200 Mick [EMAIL PROTECTED] wrote: Apr 23 01:01:01 lappy smsc_ircc_present: can't get sir_base of 0x3e8 Try checking and changing BIOS settings for IRDA IO port, IRQ settings and DMA and - maybe - PlugPlay. Then you might want to use the IO/IRQ/DMA parameters as options to the module (use modinfo -p to find out about those options). Just a guess, though. Thanks hwh, Unfortunately, the (buggy) BIOS settings for this laptop are almost non-existent! The bl**dy thing has just a couple of settings (like boot order and boot splash screen options). There's no where in there a setting for IrDA, IRQ's, or PnP. My mobile phone has a bigger choice of BIOS settings than this laptop! That said I can always experiment with forcing IO and IRQ numbers through modprobe. Is it possible to do that via /etc/modules.autoload.d, or will I need to do it by hand? -- Regards, Mick -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: IrDA crashes every time
On 23/04/06, Mick [EMAIL PROTECTED] wrote: On 23/04/06, Hans-Werner Hilse [EMAIL PROTECTED] wrote: Hi, On Sun, 23 Apr 2006 02:17:20 +0200 Mick [EMAIL PROTECTED] wrote: Apr 23 01:01:01 lappy smsc_ircc_present: can't get sir_base of 0x3e8 Try checking and changing BIOS settings for IRDA IO port, IRQ settings and DMA and - maybe - PlugPlay. Then you might want to use the IO/IRQ/DMA parameters as options to the module (use modinfo -p to find out about those options). Just a guess, though. Thanks hwh, Unfortunately, the (buggy) BIOS settings for this laptop are almost non-existent! The bl**dy thing has just a couple of settings (like boot order and boot splash screen options). There's no where in there a setting for IrDA, IRQ's, or PnP. My mobile phone has a bigger choice of BIOS settings than this laptop! That said I can always experiment with forcing IO and IRQ numbers through modprobe. Is it possible to do that via /etc/modules.autoload.d, or will I need to do it by hand? Well, I've tried passing all sort of different parameters to the module but it comes back with errors: === # modprobe -v smsc-ircc2 ircc_fir=0x100 ircc_sir=0x3e8 ircc_dma=1 ircc_irq=3 insmod /lib/modules/2.6.15-gentoo-r1/kernel/drivers/net/irda/smsc-ircc2.ko ircc_fir=0x100 ircc_sir=0x3e8 ircc_dma=1 ircc_irq=3 FATAL: Error inserting smsc_ircc2 (/lib/modules/2.6.15-gentoo-r1/kernel/drivers/net/irda/smsc-ircc2.ko): No such device === Logs: === Apr 23 12:45:33 lappy Overriding FIR address 0x0100 Apr 23 12:45:33 lappy Overriding SIR address 0x03e8 Apr 23 12:45:33 lappy smsc_ircc_present: can't get sir_base of 0x3e8 === I can't see any IRQ conflicts with the IrDA though: === # cat /proc/interrupts CPU0 0:3770091 XT-PIC timer 1: 4921 XT-PIC i8042 2: 0 XT-PIC cascade 7: 0 XT-PIC parport0 8: 2 XT-PIC rtc 9: 27 XT-PIC acpi 11: 244293 XT-PIC yenta, yenta, uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, Allegro, [EMAIL PROTECTED]::01:00.0, eth0 12: 636451 XT-PIC i8042 14: 9902 XT-PIC ide0 15: 49 XT-PIC ide1 NMI: 0 LOC: 0 ERR: 0 MIS: 0 === I even excluded irq 3 in /etc/pcmcia/config.opts, but it made no difference. I don't know what else to try. -- Regards, Mick -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: IrDA crashes every time
Hi, On Sun, 23 Apr 2006 02:17:20 +0200 Mick [EMAIL PROTECTED] wrote: Apr 23 01:01:01 lappy smsc_ircc_present: can't get sir_base of 0x3e8 Try checking and changing BIOS settings for IRDA IO port, IRQ settings and DMA and - maybe - PlugPlay. Then you might want to use the IO/IRQ/DMA parameters as options to the module (use modinfo -p to find out about those options). Just a guess, though. -hwh -- gentoo-user@gentoo.org mailing list
