EPIA M series cannot pxe boot twice

[archived]

Hi,

I'm experiencing weird behaviour with both my epias M series mobos (me6000 and m9000). If I shutdown and then reboot, PXE boot rom exists with failure and boot is not proceeding.

it seems that problem is connected with rhine kernel driver :

http://forums.viaarena.com/messageview.aspx?catid=32&threadid=63005&highlight_key=y&keyword1=PXE

Also I found problem with rhine driver that it won't allow Wake on Lan - and there is also separate patch needed....

There is also older hack, cause those M series boards boot only with 386 kernel.... I guess this is going towards having separate diskless image for epias - that will be needed also cause of video drivers and other stuff...

Any chance that those will get into Pluto kernel when it is custom compiled ?


HTH,

Regards,

Rob.

[archived]

Hi Rob

Here I found some additional infos on your issue
http://forums.viaarena.com/messageview.aspx?catid=28&threadid=67379&enterthread=y

Maybe you have already read that, anyway here you can find solutions to both issues (pxe boot and wol).

Hope this helps

Regards
Marco

[archived]

Hi,

I'm experiencing weird behaviour with both my epias M series mobos (me6000 and m9000). If I shutdown and then reboot, PXE boot rom exists with failure and boot is not proceeding.

it seems that problem is connected with rhine kernel driver :

http://forums.viaarena.com/messageview.aspx?catid=32&threadid=63005&highlight_key=y&keyword1=PXE

Also I found problem with rhine driver that it won't allow Wake on Lan - and there is also separate patch needed....

There is also older hack, cause those M series boards boot only with 386 kernel.... I guess this is going towards having separate diskless image for epias - that will be needed also cause of video drivers and other stuff...

Any chance that those will get into Pluto kernel when it is custom compiled ?


HTH,

Regards,

Rob.

Hi Rob,

We have had the same problem with our EPIA motherboards. The 'fix' seems to be to remove the power from the motherboard (and remove the RJ45 to the network) after shutdown and then reconnect both to reboot. This is just a 'work around' obviously.

It sounds like a BIOS update and some tweaking of the Kernel may be required to do a rel fix for this.

Hope this helps.

Cheers

Andrew