Hijack 275 = No idle thread poll = Failure

Posted by: Janosch

Hijack 275 = No idle thread poll = Failure - 08/06/2002 05:55

I just upgraded (from 266) to the new 275 Hijack Kernel. After this my Unit fails to start up correctly. It hangs showing the following Message "No idle thread poll". This happens in the screen that comes up after the Boot Animation. Flashing back to my old (266) Hijack fixes this.

Has anybody else seen this problem (and a workaround) ?

janosch
Posted by: Janosch

Re: Hijack 275 = No idle thread poll = Failure - 08/06/2002 14:33

UPDATE: Here ist the serial output, just the player apps seems to fail. The VFD shows "Starting idle poll thread failed":

---------------------------------------------------------------------------
Freeing unused kernel memory: 4k initempeg init 0.8
I see this is a developer image!
Mounting proc
Mounting first music partition
Tried to mount /dev/hda4 as reiserfs but got error 19
Mounting second music partition
Remounting first music partition read-only
Remounting second music partition read-only
Press 'q' now to go into development mode. You Have Zero Seconds To Comply...
Starting player

hijack: removed menu entry: "Hard Disk Detection"
player.cpp : 385:empeg-car 2.00-beta11 2002/02/08.
! player.cpp : 291:MainThread::Init failed!
Restored terminal settings
Remounting first music partition read-only
Remounting second music partition read-only
Player exited normally: 0
Switching to shell-player loop
Starting bash.
empeg:/empeg/bin#
---------------------------------------------------------------------------

So the unit IS booting but with kernel 275 the player app fails to start. The last version that works for me is 273.

janosch
Posted by: mlord

Re: Hijack 275 = No idle thread poll = Failure - 08/06/2002 19:58

Can you post the entire boot log, please.
Posted by: Janosch

Re: Hijack 275 = No idle thread poll = Failure - 09/06/2002 03:08

Sorry, sorry, sorry. I'm just so stupid. i flashed the Mark1 Kernel Image into my Mark 2a. Bad Idea. Don't know how this mistake could happen. Now the correct 275 works fine. :-)

Next time i will carefully look which kernel i'm downloading.

(Still wondering that the wrong kernel got that far when booting the unit)

ok i'm sorry again blaming Hijaack for my mistake :-)

thanks

janosch