Hi Paul,
Paul Sokolovsky wrote:
> Hello Marcus,
>
> Wednesday, April 4, 2007, 3:03:19 AM, you wrote:
>
>> Hi,
>
>> Sorry, but this is a challenge, as I don't have a h4300.
>> The relevant part of the code that does the job is in
>> custom.txt (where custom.txt is sourced into ramdisk
>> rescue before the menu starts).
>
> []
>
>> Now, you should be able to see from that snippet, that the ipk _is_
>> found (ie. INSTALLING H4300 KEYBOARD SUPPORT."), however the installation
>> process b0rks with "*ERROR*" for some reason, best explained by the msgs:
>> Clearing state_want and state_flag for pkg=kernel-module-h4300.kbd-2.6
>> (arch_priority=0 flag=16 want=2)
>> Nothing to be done
>> An error ocurred, return value: 4.
>
>> I am reasonably sure that ipkg was/is working in RR, so I suspect
>> you will have more luck continuing this investigation with the h4000
>> maintainer (ok Paul? ;) as it is impossible for me to diagnose or test.
>
> Sorry for delay with response, but kernel hacking leaves
> little time ;-). As some of the previous messages to the list
> suggests, this was solved in different way: a separate machine ID (1291)
> was introduced for h4300, and keyboard driver is activated if kernel is
> started with this ID. So now, it can be safely compiled into the
> kernel.
>
> h4300 autodetection with HaRET is pending, so for now users
> will need to use "set MTYPE 1291" in startup.txt.
>
> The stuff described is available since 2.6.20-hh6.
>
>
> []
>
>
That long ago, huh? :)
Looks like I've got a bit of catching up to do ;)
Marcus.
Received on Tue Apr 17 2007 - 20:27:04 EDT
This archive was generated by hypermail 2.2.0 : Tue Apr 17 2007 - 20:27:20 EDT