MT hanging after internal reboot

RouterOS General
1

I have been troubleshooting htis for quite some time. I have two routers, based on a PC/104 SBC and a CM9. One unit I use for experimentations, the other for real. They have an identical hardware setup.

I have been able to successfully reboot on the experiementation unit, but only when it did not say: “Loading system with initrd”.

I have installed various different combinations of packages, including routerboard (as I have read that package is needed to reboot internally). My other critical packages are system, dhcp, wireless, and hotspot.

I am fairly certain at this point that the “initrd” functionality is the culprit, as without it, I reboot successfully.

How do I remove this option? OR any other ideas?

2

Without initrd, it wont’ even attempt to reboot.

This could be a disk / partition issue. Try a different compact flash card or hard drive…

–
C

3

OK, I have tried various other hard drives, DOM’s, CF’s and all have the same problem on a particular CPU SBC.

MT boots perfectly the first go round, then when I tell it to reboot from MT, it reboots, POST’s, and says:
Booting Operating System …
Loading system with initrd
Uncompressing Linux, OK. booting the kernel.
Starting…
Checking Disk integrity…
No errors found.

Then it hangs. I know where it hangs…
I have put the HD as slave on a Linux box and looked at the startup scripts. The hang-up is in the S06modules script, line 27. This line calls a pcipnp binary, so I don’t know exactly what is happening from there.

I have commented this line out and then I tested the reboot, it worked. However, because I did not tell it to do the pcipnp, my pci devices are gone (my 10/100 NIC, and my Atheros 802.11 card) so I don’t have any interfaces.

I can think of a few options from here but I don’t know exactly how to do them:

  1. Manually set up the pci devices
  2. look into why the system hangs on pcipnp only on the internal reboot
    During the shutdown script, do we need to release some memory, or
    clear some resistors, or reset something so the internal reboot matches
    the external reboot?
  3. Talk to my BIOS guy and see why the pcipnp doesn’t work well with MT
    (only with MT - it works perfectly with all other OS’s)
    Any suggestions an what in the BIOS would be failing?

Any help on any of these three, or another option is greatly appreciated.

Thank you,
Bart

4

I had a similar problem with motherboards based on SIS chipset, so I have replaced them vith VIA or INTEL chipset motherboards.

Regards.

Faton

5

Might be using some non-standard or unsupported PCI bridge. What board is this you are using?

6

I am using a EuroTech PC/104 CPU, CPU-1451. It is base on a 400MHz ultra low voltage Intel® Celeron® processor and Intel® 815E chipset.

It may incorporate a non-standard PCI bridge. If so, is there a work-around?
(Can I install a driver for the bridge) - I’ll look into what bridge it is.

It does work with all other Linux distros I have tried (Slackware, Knoppix, redhat, debian, suse, etc)…

7

If I disable the pcipnp, can I manually install the PCI devices?

8

Are you sure that this EuroTech PC/104 CPU, CPU-1451 is actually supposed to work? It looks like your BIOS is not up to standards. Contact their support, maybe there is a BIOS upgrade. RouterOS tries 4 different standart reboot commands, if none of them work … well contact this eurotech.

9

Parvus is EuroTech America. I will go talk with my BIOS man. Is the Pheonix BIOS supported, or does the Pheonix BIOS support MT?