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).
::
if mount -t vfat $fatNode /mnt/source
then
::
if [ -f "/mnt/source/${RR_PATH}/kernel-module-h4300-kbd-2.6_2.6.16-hh7-r0_h4000.ipk" ]
then
message "INSTALLING H4300 KEYBOARD SUPPORT."
if ipkg install "/mnt/source/${RR_PATH}/kernel-module-h4300-kbd-2.6_2.6.16-hh7-r0_h4000.ipk"
then
message "\t*DONE*"
else
message "\t*ERROR*"
exit 1
fi
else
message "\t*UNABLE TO FIND H4300_KBD IPK*"
exit 1
fi
depmod -ae
message "LOADING H4300 KEYBOARD MODULE."
if modprobe h4300-kbd
then
message "\t*DONE*"
else
message "\t*ERROR*"
exit 1
fi
umount /mnt/source
else
message "\tERROR MOUNTING SOURCE"
exit 1
fi
::
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.
If you want to fiddle and diagnose for yourself, I suggest you remove
the exit statement from custom.txt and log in to RR via ssh to run some
tests manually. In partnership with Paul, I would think that this approach
would solve the issue quickly and finally.
Have fun.
Marcus.
pizzaman_at_softhome.net wrote:
>> Hi Hasan,
>
>
>> Hasan Ammar wrote:
>>> Hello Marcus,
>>> thanks for replying. I've been quite eager to get this thing to work.
>>> The problem is that the kernel module for h4300 (the keyboard module)
>>> doesn't load up. It says something about file not found. I've checked
>> custom.txt and the file names match perfectly. Then, I went back and
>> looked into the archives and I noticed that this has been an issue
>> before as well, i.e. the .ipk module not being found. I've tried
>> putting it in different paths and changing custom.txt to reflect those
>> paths, and still it cant find the module.
>> Can you let me know which wiki page you're talking about. I followed
>> the instructions here:
>> https://sourceforge.net/project/showfiles.php?group_id=173841 and the
>> release notes here:
>> https://sourceforge.net/project/shownotes.php?release_id=448190&group_id=173841
>>
>>
>> I've also tried following
>> http://www.handhelds.org/moin/moin.cgi/RamdiskRescue I'm getting the
>> same error in the end.. module not found. Also, i figured even if the
>> keyboard didn't work, the hard buttons and navigator would. But
>> they're not working either, and i get stuck at the ramdisk rescue menu.
>> Regards
>> On 2/18/07, Marcus Brown <marcusbrutus_at_internode.on.net> wrote:
>>> Hasan Ammar wrote: > Hello, > > I am stuck trying to get the
>>> pre-built packages to work. I have an ipaq > 4350, and > none of the
>>> arrow keys, the hardware buttons or the keyboard work on > the
>>> ramdisk rescue menu page, so consequently i can't even get to the >
>>> installation. Can anyone please let me know how to get past that? > >
>>> Thank you. > > Regards > > Ammar
>>> Hi,
>>> Assuming everything else is setup _as_per_the_wiki_ you should find
>>> that all works ok, including buttons.
>>> You will note in the download section of the wiki that there is a
>>> custom.txt and a kernel module for the h4300 series. Please ensure
>>> that you have placed these files in /linux/rescue/
>>>
>>> Marcus.
>>
>>
>>
>> When I refer to "the wiki", I mean:
>> http://www.handhelds.org/moin/moin.cgi/RamdiskRescue
>>
>> Do not use instructions or files from other sources unless you know
>> what you are doing. They will _not_ work.
>>
>> If the files are all in their correct places, and the module still
>> won't load, I would suggest that the most likely reason for this error
>> is that you are using a kernel other than the one provided for Ramdisk
>> Rescue.
>>
>>
>> Good luck.
> Hi Marcus,
> As per your instructions I followed the wiki. As other people I can't
> the keyboard to work.
> Here is the list of my files in the rescue folder:
> E:\linux\rescue>dir
> Volume in drive E has no label.
> Volume Serial Number is DC24-8F1B
> Directory of E:\linux\rescue
> 04/02/2007 01:56 PM <DIR> .
> 04/02/2007 01:56 PM <DIR> ..
> 04/02/2007 02:32 PM 1,898 STARTUP.TXT
> 02/19/2007 09:51 AM 1,239,664
> zImage-2.6.16-hh9-hx4700-20070207203007
> 02/19/2007 11:24 AM 633,856 haret-0.3.8.exe
> 04/02/2007 02:31 PM 4,122
> kernel-module-h4300-kbd-2.6_2.6.16-hh7-r0
> _h4000.ipk
> 02/19/2007 11:23 AM 3,708,760 ramdisk-rescue-0.6.4.rootfs.ext2.gz
> 03/31/2007 03:13 PM 1,359,092
> zImage-2.6.16-hh7-h4000-20060920151019
> 04/02/2007 01:56 PM <DIR> image
> 02/19/2007 11:22 AM 6,268 Copy of custom.txt
> 04/02/2007 02:31 PM 6,268 custom.txt
> 04/02/2007 02:27 PM 1,359,152
> zImage-2.6.16-hh7-h4000-20061028020714
> 9 File(s) 8,319,080 bytes
> 3 Dir(s) 174,723,072 bytes free
> The specific error I am getting, which probably is the same error other
> people are getting is:
> EXECUTING CUSTOM RESCUE SCRIPT
> INSTALLING H4300 KEYBOARD SUPPORT.
> 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.
> Collected errors.
> Cannot find package kernel-module-h4300-kbd-2.6
> Check the spelling or perhaps run 'ipkg update'
> *ERROR*
> After this booting halts and rescuedisks screen doesn't load.
> Regards,
> Luis
> _______________________________________________
> H4100-port mailing list
> H4100-port_at_handhelds.org
> https://www.handhelds.org/mailman/listinfo/h4100-port
Received on Tue Apr 03 2007 - 20:18:53 EDT
This archive was generated by hypermail 2.2.0 : Tue Apr 03 2007 - 20:19:11 EDT