WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: lirc ist not working TC4.1  (Read 5297 times)

Offline Da Alchemist

  • Newbie
  • *
  • Posts: 14
lirc ist not working TC4.1
« on: December 18, 2011, 12:11:33 PM »
Hello,

Ijust updated to TC4.1 and found Lirc not working.

When I try to load the Modules manually Ill get:

module lirc_serial not found in modules.dep

Is there a fix  ?

Regards

Da Alc

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: lirc ist not working TC4.1
« Reply #1 on: December 18, 2011, 12:23:59 PM »
lirc.tcz is a Version 3 extension, not a Version 4 extension.
lirc.tcz contains the the modules for 2.6.33.3-tinycore, not 3.0.3-tinycore

Offline Da Alchemist

  • Newbie
  • *
  • Posts: 14
Re: lirc ist not working TC4.1
« Reply #2 on: December 18, 2011, 12:56:55 PM »
So Ithink it has to be removed from the 4.x Repos or be recompiled  ;), I wish i would be able to do so ...

Regards

Da Alc


Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: lirc ist not working TC4.1
« Reply #3 on: December 18, 2011, 10:23:39 PM »
Well isn't this a bit weird, to have modules in an extensions that does not follow the 'name-KERNEL.tcz' convention.

Maybe it's time to split off 'lirc-modules-KERNEL.tcz' from 'lirc.tcz'. Likewise (at least when checking the *.list files of my own TC 4.x mirror) it appears that 'madwifi.tcz' is another case with "hidden" v2.6.33.3 modules.

And furthermore I spotted that 'ndiswrapper.tcz', 'openvswitch.tcz' and 'wl.tcz' contain a v3.0.3 module each, which prevents them from ever being able to support a 64-bit system. So maybe splitting off the modules or renaming the extension to follow the 'name-KERNEL.tcz' convention could be considered for those three as well (with the good news that I did not spot any problem WRT other dependency files).

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: lirc ist not working TC4.1
« Reply #4 on: December 19, 2011, 03:18:14 AM »
And furthermore I spotted that 'ndiswrapper.tcz', 'openvswitch.tcz' and 'wl.tcz' contain a v3.0.3 module each, which prevents them from ever being able to support a 64-bit system.

I'll split ndiswrapper into ndiswrapper and ndiswrapper-modules-3.0.3-tinycore and rename wl to wl-modules-3.0.3-tinycore.

Before I post them, it probably makes sense I compile ndiswrapper-modules-3.0.3-tinycore64 and wl-modules-3.0.3-tinycore64 - it's going to be somewhat awkward to test as my core64 machine has broadcom wireless hardware that will not be supported before linux-3.2, needs a new version of ndis and is not supported by the wl module either...

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: lirc ist not working TC4.1
« Reply #5 on: December 21, 2011, 01:28:38 AM »
wl-modules-3.0.3-tinycore and wl-modules-3.0.3-tinycore64 posted

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: lirc ist not working TC4.1
« Reply #6 on: December 21, 2011, 11:15:49 PM »
ndiswrapper-modules-3.0.3-tinycore and ndiswrapper-modules-3.0.3-tinycore64 posted

Offline AmatCoder

  • Full Member
  • ***
  • Posts: 179
    • AmatCoder Projects
Re: lirc ist not working TC4.1
« Reply #7 on: December 24, 2011, 12:09:10 AM »
Ijust updated to TC4.1 and found Lirc not working.

When I try to load the Modules manually Ill get:

module lirc_serial not found in modules.dep

Is there a fix  ?

Since 2.6.36 most lirc modules are already included in the kernel as drivers. But you need 0.9.0 version, 0.8.x series are incompatible with recent kernels.

I made an 0.9.0 extension and it's working fine for me. I could upload it to repository, but  you must keep in mind that:

1) I can not test every driver.
2) I don't supply any script to start it. User must do it himself.
3) smode2  is not available.
4) irxevent  and xmode2 are not available (I will try to compile them but I can not guarantee...) Edit: Done.
5) irman driver is not available (I can try it if anyone is interested...)

If this issues are acceptable to developers then I will send it.

Regards.
« Last Edit: December 26, 2011, 06:05:57 AM by AmatCoder »

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: lirc ist not working TC4.1
« Reply #8 on: December 24, 2011, 12:38:22 AM »
If this issues are acceptable to developers then I will send it.

It would be good to check by a PM with the maintainer of lirc (Thomas Genty) in the 3.x repo if he's OK with this, otherwise I don't think it would be a problem

Offline AmatCoder

  • Full Member
  • ***
  • Posts: 179
    • AmatCoder Projects
Re: lirc ist not working TC4.1
« Reply #9 on: December 26, 2011, 06:11:53 AM »
Today I send a PM (via forum), although he is not active since August 2010...  :'(

Offline Da Alchemist

  • Newbie
  • *
  • Posts: 14
Re: lirc ist not working TC4.1
« Reply #10 on: January 05, 2012, 06:22:08 AM »
Hello,

I don't know how long we have to wait for an answer. I think 10 Days without means that the former maintainer is not working with TC any more.

Could the new version now be updated?

Otherwise I think i have to fallback to 3.84..

Regards

Da Alc

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14516
Re: lirc ist not working TC4.1
« Reply #11 on: January 05, 2012, 08:34:33 AM »
I think 10 days is a reasonable amount of time to wait without reply, so it should be OK for AmatCoder to go ahead and submit an update

Offline AmatCoder

  • Full Member
  • ***
  • Posts: 179
    • AmatCoder Projects
Re: lirc ist not working TC4.1
« Reply #12 on: January 09, 2012, 07:56:19 AM »
Now I sent it to Jason...Apologizes for the delay.
 

Offline Da Alchemist

  • Newbie
  • *
  • Posts: 14
Re: lirc ist not working TC4.1
« Reply #13 on: January 12, 2012, 12:46:40 AM »
Just found the new modules in the repos.

It is working perfectly for me. :)

Thanks a lot!

Regards

Da Alc

Offline AmatCoder

  • Full Member
  • ***
  • Posts: 179
    • AmatCoder Projects
Re: lirc ist not working TC4.1
« Reply #14 on: January 12, 2012, 07:00:26 AM »
It is working perfectly for me. :)
I am glad to hear that.  ;)