problem with shell access - Page 2

Acid · 03-19-2008, 05:50 AM

I just thought - is it possible that iRex company has restricted the contentlister functionality to prevent script-based third-party soft starting?

It's a strange fact - if the latest firmware hasn't been changed since release date - why we could run scripts before and couldn't now?

godidog · 03-19-2008, 06:53 AM

"Never ascribe to malice that which is adequately explained by incompetence." - Napoleon Bonaparte

At least to start with...

Shaggy · 03-19-2008, 11:00 AM

Quote:

Originally Posted by JWLaRue

If it helps folks in troubleshooting, I downloaded the developers kit a week ago today...and shell access works fine on my iLiad (v1, v2.12)

-Jeff

It works fine for me too on 2.12, but I downloaded the developers kit right after 2.12 came out. I wonder if iRex updated the developers kit recently, and something they changed is causing new downloads to fail?

daudi, you seem to be thinking the same thing. Did you get any information from iRex, or are you just making the same guess?

daudi · 03-19-2008, 11:47 AM

I'm just guessing based on the fact that I had it working fine and it was not fine after downloading shell access again. I think there are enough people who suddenly started seeing this problem for it to be pretty strong evidence that something must have changed. I don't think there's anything any of us can do about it, we'll have to wait for irex to sort this out.

kinetic · 03-19-2008, 05:50 PM

But does Irex support this ? I mean...in previous versions Shell Access was implemented, now it was taken out of the equation..

Do Irex really care about this issues..I mean are they aware of this issues??

At iRex forums I havn't seen any of irex employees saying anything about this...

Regards,

Kinetic.

Adam B. · 03-19-2008, 05:57 PM

Quote:

Originally Posted by kinetic

But does Irex support this ? I mean...in previous versions Shell Access was implemented, now it was taken out of the equation..

Do Irex really care about this issues..I mean are they aware of this issues??

At iRex forums I havn't seen any of irex employees saying anything about this...

Regards,

Kinetic.

I don't think that the problem with shell access not functioning was intentional. Likely, the package on their server was corrupted or changed and they are unaware that it is broken. I've emailed one of the developers to notify him of the problem, but haven't heard a response.

I'm sure that once they know what the problem is, that they'll resolve it.

TurboProp · 03-20-2008, 07:16 AM

I've opened a ticket with iRex support and called them this morning. They are aware of the problem, it's been escalated to their engineering department, I've been told.

So the fix is coming, sooner or later. Knowing iRex,
more likely later

Adam B. · 03-20-2008, 09:07 AM

I setup SSH to start on boot, restored my registry to a clean version, requested the developer package, and I believe I've found the problem.

Below is the shell entry in the registry after downloading:

Quote:

<application type="SHELL">
<appCategory>viewer</appCategory>
<argMask><FILENAME></argMask>
<execute>/bin/sh</execute>
<supportFormat>
<extName>sh</extName>
</supportFormat>
<xResourceName>sh</xResourceName>
<ipcChannel>14</ipcChannel>
<appIconPath/>
</application>

Notice the argument mask. On the previous (working) version of the registry it is setup as:

Quote:

<application type="SHELL">
<appCategory>viewer</appCategory>
<xResourceName>sh</xResourceName>
<ipcChannel>14</ipcChannel>
<argMask>_FILENAME_</argMask>
<execute>/bin/sh</execute>
<supportFormat>
<extName>sh</extName>
</supportFormat>
<appIconPath/>
</application>

It's likely an error in the new installation script.

I've forwarded this information along to the iRex developers. I'm sure they'll get it resolved as soon as they can.

Adam B. · 03-20-2008, 11:55 AM

After talking with one of the iRex developers, the problem appears to be fixed.

Can those who weren't able to get shell access to work download the package again?

felonius · 03-20-2008, 12:48 PM

Quote:

Originally Posted by Adam B.

After talking with one of the iRex developers, the problem appears to be fixed.

Can those who weren't able to get shell access to work download the package again?

So... Do I need to reformat my iLliad? Cause it's still not working for me. Same behavior... Blah. Maybe I'll try again a little later...

Adam B. · 03-20-2008, 12:51 PM

Quote:

Originally Posted by felonius

So... Do I need to reformat my iLliad? Cause it's still not working for me. Same behavior... Blah. Maybe I'll try again a little later...

You probably will need to reflash with "format" in the config.txt to get it to work... The old (broken) entry is in the registry preventing the working one from being created.

Make sure you back up everything on the internal storage, as a format will erase everything!

TurboProp · 03-20-2008, 01:04 PM

Just downloaded the DP again, none of the scripts work. I'll try to reformat tonight....

DigiDirk · 03-20-2008, 01:04 PM

Yes, it is working.

Had my 2.10.2 iLiad away for 2(!) days joining the battery replacement program.

Came back with 2.12, no shell access (tried mrxvt).

Requested the development package and... voilà! It works.

Product Type: ER0100
PCBA Rev: 3
Software Version: 2.12 build 21201
Kernel: 2.4.19-rmk7-pxa2-irex1 #21100

I'm a happy camper again!

Dirk

TurboProp · 03-20-2008, 01:27 PM

Quote:

Originally Posted by DigiDirk

Yes, it is working.

Had my 2.10.2 iLiad away for 2(!) days joining the battery replacement program.

Came back with 2.12, no shell access (tried mrxvt).

...

Dirk

@DigiDirk: Man you're lucky! It works for you most likely because you never downloaded the broken DP. My iLiad came with 2.12 preloaded as well. But like Adam B. said the good package doesn't install properly over the broken one!

I'll see if iRex comes up with a workaround. If not, I'll have to reformat my iLiad.

DigiDirk · 03-20-2008, 01:42 PM

Yes, things worked out fine.

I was quite nervous having delayed firmware upgrade for a while,
sending away a perfect working iLiad... just to read shell access got broken!

Thanks to Adam B. that got fixed while it was away!

And - sorry - but I'm convinced you have to reformat your iLiad
because the registry won't get replaced any other way!

Hope you're back with shell access soon!

Dirk

03-20-2008, 07:16 AM	#22
TurboProp Junior Member Posts: 9 Karma: 10 Join Date: Jan 2008 Location: Ireland <-> Bay Area Device: Rex iLiad, Blackberry Curve	iRex is aware of the problem I've opened a ticket with iRex support and called them this morning. They are aware of the problem, it's been escalated to their engineering department, I've been told. So the fix is coming, sooner or later. Knowing iRex, more likely later

03-20-2008, 01:04 PM	#27
TurboProp Junior Member Posts: 9 Karma: 10 Join Date: Jan 2008 Location: Ireland <-> Bay Area Device: Rex iLiad, Blackberry Curve	No workie... Just downloaded the DP again, none of the scripts work. I'll try to reformat tonight....

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
iLiad shell access problem..	wklee	iRex Developer's Corner	10	07-20-2008 08:22 AM
Problem getting shell access	templario	iRex	1	03-17-2008 11:25 PM
Can't get shell access	MarkRPenn	iRex	11	10-26-2007 07:58 PM
Shell Access ?	grayfox	iRex	6	10-14-2007 05:56 PM
iLiad Shell access package	HarryT	iRex Developer's Corner	3	08-07-2007 09:07 AM

03-19-2008, 05:50 AM	#16
Acid Member Posts: 19 Karma: 10 Join Date: Mar 2008 Location: Moscow, Russia Device: iLiad	I just thought - is it possible that iRex company has restricted the contentlister functionality to prevent script-based third-party soft starting? It's a strange fact - if the latest firmware hasn't been changed since release date - why we could run scripts before and couldn't now?

03-19-2008, 06:53 AM	#17
godidog Iliadist Posts: 19 Karma: 10 Join Date: Feb 2008 Device: Iliad (broken screen fixed after 3 months), Treo	"Never ascribe to malice that which is adequately explained by incompetence." - Napoleon Bonaparte At least to start with...

03-19-2008, 11:47 AM	#19
daudi Addict Posts: 281 Karma: 904 Join Date: Oct 2007 Location: Kent, UK Device: iRex iLiad, Psion 5MX, nokia n800	I'm just guessing based on the fact that I had it working fine and it was not fine after downloading shell access again. I think there are enough people who suddenly started seeing this problem for it to be pretty strong evidence that something must have changed. I don't think there's anything any of us can do about it, we'll have to wait for irex to sort this out.

03-19-2008, 05:50 PM	#20
kinetic Junior Member Posts: 9 Karma: 10 Join Date: Jan 2008 Device: none currently	But does Irex support this ? I mean...in previous versions Shell Access was implemented, now it was taken out of the equation.. Do Irex really care about this issues..I mean are they aware of this issues?? At iRex forums I havn't seen any of irex employees saying anything about this... Regards, Kinetic.

03-20-2008, 11:55 AM	#24
Adam B. Addicted to Porting Posts: 1,697 Karma: 7194 Join Date: Oct 2006 Location: Indianapolis, IN Device: iRex iLiad, Nokia 770, Samsung i760	After talking with one of the iRex developers, the problem appears to be fixed. Can those who weren't able to get shell access to work download the package again?

03-20-2008, 01:04 PM	#28
DigiDirk Connoisseur Posts: 73 Karma: 156 Join Date: Dec 2006 Device: iLiad	Yes, it is working. Had my 2.10.2 iLiad away for 2(!) days joining the battery replacement program. Came back with 2.12, no shell access (tried mrxvt). Requested the development package and... voilà! It works. Product Type: ER0100 PCBA Rev: 3 Software Version: 2.12 build 21201 Kernel: 2.4.19-rmk7-pxa2-irex1 #21100 I'm a happy camper again! Dirk

03-20-2008, 01:42 PM	#30
DigiDirk Connoisseur Posts: 73 Karma: 156 Join Date: Dec 2006 Device: iLiad	Yes, things worked out fine. I was quite nervous having delayed firmware upgrade for a while, sending away a perfect working iLiad... just to read shell access got broken! Thanks to Adam B. that got fixed while it was away! And - sorry - but I'm convinced you have to reformat your iLiad because the registry won't get replaced any other way! Hope you're back with shell access soon! Dirk