StarOS v2.00.3b5-4373 ready for testing

[tony]

Do not apply this update unless you have easy access to the system in question. Always backup your configuration before upgrading.

Read the previous beta release notes before applying this update.

Release notes for v2.00.3b5:
*) problem with using shared port and parent qshape options while using pipe ranges has been corrected.
*) development of v3 continues.

Release Caveats:
*) none

As with all betas, please report your success using this release.

STARUTIL 1.11
Linux:
http://www.star-os.com/downloads/starutil-linux-1.11.tgz
Windows:
http://www.star-os.com/downloads/starutil-windows-1.11.zip

DESKTOP SYSTEMS
Desktop Edition:
http://www.star-os.com/downloads/oem-vnc/strr-2.00.3b5-4373.iso
http://www.star-os.com/downloads/oem-vnc/strr-2.00.3b5-4373.bin
http://www.star-os.com/downloads/oem-vnc/strr-2.00.3b5-4373.raw

SPECIAL PURPOSE SYSTEMS
Soekris & MODO Edition:
http://www.star-os.com/downloads/oem-vnc/strrs-2.00.3b5-4373.iso
http://www.star-os.com/downloads/oem-vnc/strrs-2.00.3b5-4373.bin
http://www.star-os.com/downloads/oem-vnc/strrs-2.00.3b5-4373.raw

WRAP Edition:
http://www.star-os.com/downloads/oem-vnc/strrw-2.00.3b5-4373.iso
http://www.star-os.com/downloads/oem-vnc/strrw-2.00.3b5-4373.bin
http://www.star-os.com/downloads/oem-vnc/strrw-2.00.3b5-4373.raw

Routerboard Edition:
http://www.star-os.com/downloads/oem-vnc/strrb-2.00.3b5-4373.iso
http://www.star-os.com/downloads/oem-vnc/strrb-2.00.3b5-4373.bin
http://www.star-os.com/downloads/oem-vnc/strrb-2.00.3b5-4373.raw

CPE SYSTEMS
CPE Editions for v1.13.4b2 are available.

[bwbboot]

Works like a rock!!! thanks guys for the quick response and the very quick fix!!!!!

[tony]

Glad it is working well for you. :)

Works like a rock!!! thanks guys for the quick response and the very quick fix!!!!!

[datawork]

Hi Guys,

Just thought I'd share a little info I have stumbled upon doing various upgrades with Star-OS. This info is especially useful for those of you using the 733 ATX boards Lonnie was selling a year or so ago.

After running the firmware update DO NOT select Reboot Machine from the File Menu. This will almost certainly result in a hung server.

Instead, after the update Select Save Changes from the File Menu, Then Activate Changes from the File Menu. and Finally , Reboot Machine.

These two extra steps will almost certainly save you a trip to your remote POP.

We have been able to reproduce these results 100% of the time with the 733 boards and holds true to the most current beta's.

On another note:

Tony or Lonnie
The other quirk we have seen with 733 boards is if the Watchdog timer ever invokes a reboot you will be making an uplanned trip to your remote POP

Would it be possible to add the above two steps to the WatchDog Timer reboot with a Sleep 5 between each step.

As I am convinced that this would solve the Watchdog ping reboot issue problem. For whatever reason the 733 boards do not seem to be able to save the information to disk fast enough before the Reboot command is issued. Reulting in a hung server

[lonnie]

Please check your BIOS settings. It sounds to me like the USB is enabled. This mother has always had trouble rebooting with the USB enabled.

[datawork]

Please check your BIOS settings. It sounds to me like the USB is enabled. This mother has always had trouble rebooting with the USB enabled.

USB has been disabled from day one, along with other non essential ports (serial,Comm,FD,etc) to limit the potential for IRQ conflicts

[lonnie]

We have seen times when USB will get re-enabled. Did you check it or just assume that it had stayed the way you left it?

[David L. Vrablic]

I just had the exact same thing happen with the 733 board.
The USB was disabled when I first set it up and I doubled checked it when I drove up to reboot the machine.
-----------
I did find something I don't like.
IRQ seems to be shared ????? Hummmmm

---[ IRQ Information ]--------------------------------------
│ CPU0 │
│ 0: 24169284 XT-PIC timer
│ 1: 1192 XT-PIC keyboard │
│ 2: 0 XT-PIC cascade │
│ 5: 15937425 XT-PIC wpci0 │
│ 8: 0 XT-PIC rtc │
│ 10: 19780906 XT-PIC wpci1, eth0 │
│ 11: 155294 XT-PIC eth1 ·│
│ 14: 38970 XT-PIC ide0 │
│NMI: 0 │
│ERR: 0

[bobbyc]

Yup, 1 of the slots shares a IRQ with the ethernet. No way around it, except not to use that slot.
All motherboards seem to be like that...
Bob C

[David L. Vrablic]

Interesting Bob,
The example I showed beffore was a box that I had to use a NIC card because the on board works for the key but does not pass traffic.
(Most likely a pin or socket problem)

This is a snap of a new 5.8 project with a single radio plugged into the "Most inboard" socket.
Mechanically everything fits great using this one.
I can redesign if I have to but I would rather not.

I will have to check with it's twin and see if I can get rid of the sharing.

---[ IRQ Information ]-------------------------------------- ▒│
│ CPU0 ▒│
│ 0: 24169284 XT-PIC timer ▒│
│ 1: 1192 XT-PIC keyboard ▒│
│ 2: 0 XT-PIC cascade ▒│
│ 5: 15937425 XT-PIC wpci0 ▒│
│ 8: 0 XT-PIC rtc ▒│
│ 10: 19780906 XT-PIC wpci1, eth0 ▒│
│ 11: 155294 XT-PIC eth1 ·│
│ 14: 38970 XT-PIC ide0 ▒│
│NMI: 0 ▒│
│ERR: 0

Thanks for the info.

[datawork]

I double checked everything after the lockup. USB is still disabled. Here are the IRQ's from the System Info.

Leave the center PCI spot open to avoid sharing IRQ 10



│ CPU0
│ 0: 29046275 XT-PIC timer
│ 1: 98 XT-PIC keyboard
│ 2: 0 XT-PIC cascade
│ 5: 48818427 XT-PIC wpci1
│ 8: 0 XT-PIC rtc
│ 10: 45773606 XT-PIC eth0
│ 11: 8247122 XT-PIC wpci0
│ 14: 34372 XT-PIC ide0

[David L. Vrablic]

Something is a little strange here but we are closing in on it.
I am not using the middle or the outboard slot in my BH box.
Yet I get the IRQ 10 conflict and you don't.
--------------
Re your last post:
Is this how your box was set up when you got the reboot problem, or is this the way it is now after our exchange of info?
-----------------
Can you get it to fail now with these settings?
-----------------
It looks like you are using 2 wpci cards, what are they ?
--------------
Right now I am playing with the DWL AG530's with a hardware code of A3.
They are supposed to be the same as the ATHROS 5213 and don't require an adapter and have a RSMA connector. I don't think this has any bearing on our reboot lock-up problem.

[bobbyc]

I've had a AG530a2 and a senao 200mw/ricoh adapter in a 733 board for a few weeks, and haven't had any problems.
0: 343919195 XT-PIC timer ▒│
│ 1: 2 XT-PIC keyboard ·│
│ 2: 0 XT-PIC cascade ▒│
│ 5: 18987735 XT-PIC i82365, agere_cs ▒│
│ 8: 0 XT-PIC rtc ▒│
│ 10: 76269 XT-PIC eth0 ▒│
│ 11: 62747212 XT-PIC wpci0 ▒│
│ 14: 40968 XT-PIC ide0 ▒│
│NMI: 0 ▒│
│ERR: 0

Bob C

[datawork]

snip
--------------
Re your last post:
Is this how your box was set up when you got the reboot problem, or is this the way it is now after our exchange of info?
-----------------
Can you get it to fail now with these settings?
-----------------
It looks like you are using 2 wpci cards, what are they ?
--------------


This is the way we've had it set up from day one.

Yes

The cards are dwl-ag520's

This machine's twin has two 520's are well a 200mw Seano card, uses IRQ 10 due to center PCI being used and does the same thing.

I'm wondering if it might have something to do with the 32 Mb DiskonModules.

[David L. Vrablic]

Now that is really strange.
I "Had to use the center slot to not share an IRQ with anything else.

PC Chips board.
32 Meg DOM
Dlink WPCI AG530 (2513) Atheros
(Bought them way back when cards were not available)
NIC on board.
Nothing is shared.

Works like a champ.
I guess you just have to play chess till you win the game!