possible to go back to 2.3 old kernel after installing 2.3 kernel 3.1.1?

[squirelly666]

Hi All,

Just thought I'd check before I try it, but does any know of any issues downgrading to the original 2.3 release (from oct) after installing the 2.3 (Linux 3.1.1) image released on xmas day?

I've been running 2.3 fine for the last month or so, but since installing the kernel 3.1.1 image on boxing day I've been having nothing but trouble. The box hangs (by hang I mean it carries on showing live tv, but won't respond to remote and the vix logo just spins in the corner and I need to power down the box to get it back up) or crash (just a random reboot, no error message or crash log) almost every time when I'm recording a channel that requires decrypting (using cccam 2.2.1 downloaded from 'cams for vix' thread on this forum) and I try to do something else at the same time such as change channel, or playback another recording.

If downgrading is a no go, is there a newer version of cccam I need for this 3.1.1 image?

 

[Stanman]

Before you give up mate, have you enabled logs? if not can you do so and than please post up the logs and any crash reports from when this happens.

We cannot resolve issues when they are neither reported to us or debug and crash logs attached to post.

As for downgrading, on VU+ models this is not an issue and you can roll back to an earlier image without any issues.

Also CCcam 2.3.0 is out and is in the same place as the others.

 

[squirelly666]

I thought I had logs enabled and for some reason it wasn't producing one, however I've just double checked and they weren't enabled (doh!).

I've now turned on debug logs, and detailed crash logs, so next time it happens I'll post up the logs.

 

[squirelly666]

right, box has just crashed again this time switching from an encrypted channel to a FTA one.

When it happened box showed channel I switched to ok, but would not respond to remote with VIX logo spinning in top corner. After about 30 seconds box rebooted itself.

I have attached log files from either side of the event, but it doesn't seem to have produced a crash log, despite the fact that I have detailed crash logs enabled in the settings. Are crash logs stored in the same location as regular log files?

Thanks.

 

[Markymark]

Also CCcam 2.3.0 is out and is in the same place as the others.

Slightly off topic, however just been searching for this and doesnt find anything. Where is the "same place as all the others"? Also does the upgrade automatically go over the top of any older version of CCcam or do I have to do some installing?

 

[squirelly666]

Slightly off topic, however just been searching for this and doesnt find anything. Where is the "same place as all the others"? Also does the upgrade automatically go over the top of any older version of CCcam or do I have to do some installing?

For download it's in the 'cams for vix images' sticky in the vix downloads section.

Not sure about upgrading though, think it replaces what's there.

 

[Stanman]

If you do it as an IPK install than it will be in addition to any other cam yo have installed.

Needs to be FTP to TMP folder and than installed via blue button>vix>install local extensions

 

[Markymark]

But as I have CCcam 2.1.1 then it will just go over the top of this one? No need to try and install it or anything like that.

 

[Stanman]

Sorry you have lost me.
If you do it the way I posted above, than you will have both cams in softcam manager.

The old one will not be overwritten

 

[Markymark]

Am I doing something wrong as ive FTP the file in the temp folder and followed instructions, however its not showing in the vix install local extensions folder. Now after looking back at the tutorial the version of CCcam in there as a file ending.ipk however the one that I have in this new version ends .mipsel

Is this right or am I using the wrong CCcam file in this 2.3v folder that I have downloaded? There isnt one with .ipk at the end of it though.

 

[Larry-G]

Am I doing something wrong as ive FTP the file in the temp folder and followed instructions, however its not showing in the vix install local extensions folder. Now after looking back at the tutorial the version of CCcam in there as a file ending.ipk however the one that I have in this new version ends .mipsel

Is this right or am I using the wrong CCcam file in this 2.3v folder that I have downloaded? There isnt one with .ipk at the end of it though.

you need the one from here

http://www.4shared.com/dir/wnyHV50A/VIX_CAMS.html

 

[squirelly666]

thread seems to have gone a bit OT, but I've had another crash.

Logs attached from before, and after, the crash but once again no crash log created unless they are stored in a different location. The box hung for a short time and was unresponsive to remote commands so I had to power it off at the back to get it back up and running again.

I'm going to upgrade cccam next to see if that stops the crash.

on a related subject any idea why the log files are dated 1970?

 

[Larry-G]

I know this is not helping you but to clarify, A crash log is only generated when the box actually crashes and you see the black death screen with white text on the screen. the fact that you are powering the box down means it's not technically crashing but hanging.

 

[squirelly666]

I thought might be the case, which I guess means it's going to be a little trickier to work out whats going on?

I think I'm going to try latest cccam and if that doesn't solve it, then I'll go back to the earlier 2.3 that worked fine until the kernel upgrade.

 

[walter_red]

I have the same problem and keep being told on here there's no need to go back......it's doing my head in since 'upgrading' - freezing, dead remote, reboots, picture break up. Wish I'd stuck with the old image as it now seems to be packed with stuff I don't want anyway!

 

[Stanman]

I have the same problem and keep being told on here there's no need to go back......it's doing my head in since 'upgrading' - freezing, dead remote, reboots, picture break up. Wish I'd stuck with the old image as it now seems to be packed with stuff I don't want anyway!

If you want to go back thats your preorgative but we are not going to be able to fix issues if we dont have crash reports / logs to look at.

There are 10's of thousands of lines of code in the image and trying to find an issue with out the logs is worse than a needle in a haystack. That is why every time we ask for them.

I appreciate people have issues and want them fixed yesterday but bear in mind this is a hobby and we all have other commitments in our life. Once an issue is known and is due to the image and not plugins etc, than we will fix but folks need to bear with us.

 

[walter_red]

If you want to go back thats your preorgative but we are not going to be able to fix issues if we dont have crash reports / logs to look at.

There are 10's of thousands of lines of code in the image and trying to find an issue with out the logs is worse than a needle in a haystack. That is why every time we ask for them.

I appreciate people have issues and want them fixed yesterday but bear in mind this is a hobby and we all have other commitments in our life. Once an issue is known and is due to the image and not plugins etc, than we will fix but folks need to bear with us.

I'm not having a go at anyone on here who takes the time and effort to make/write this stuff and then take the time to reply to people who just moan.

The problem is that the people like me who just know enough to get by, are frustrated when something, like an update for instance, causes more problems than it solves. 'JUST' watching tv is probably way below what these boxes are capable of, but equally there must be thousands of people (rightly or wrongly) that ARE only using them to save money on subs.

I love the way I can get stuff off it and stick it on my popcorn hour - not possible with s*y, but it does need to be watchable!

cheers

 

[Rob van der Does]

Just a long shot: does any one who has trouble use a loopthrough to another box?

 

[walter_red]

Just a long shot: does any one who has trouble use a loopthrough to another box?

Not sure what you mean so I guess no! I only have one box, both tuners are set to single, simple etc

BTW - new crash, this time while trying to set static IP - crash log attached