Soft reboot hangs on FE upd 1
Soft reboot hangs on FE upd 1
Hi,
using AmigaOne X1000. After updating to AOS4.1 FE update 1, normal hard boot works as it should. When doing a soft reboot (CTRL-Alt-AltGR or shell command Reboot fast) the booting hangs when showing the final AmigaOS 4.1 logo. Tried taking out everything in WBStartup and even commenting out User-Startup and Network-Startup lines in Startup-Sequence, no change. When doing a hard reset with the Reset button of X1000, boots normally. Any ideas?
Marko R.
using AmigaOne X1000. After updating to AOS4.1 FE update 1, normal hard boot works as it should. When doing a soft reboot (CTRL-Alt-AltGR or shell command Reboot fast) the booting hangs when showing the final AmigaOS 4.1 logo. Tried taking out everything in WBStartup and even commenting out User-Startup and Network-Startup lines in Startup-Sequence, no change. When doing a hard reset with the Reset button of X1000, boots normally. Any ideas?
Marko R.
Marko
Re: Soft reboot hangs on FE upd 1
I cannot confirm this behaviour.
Soft Reboot works as good with upd1 as it did with FE
Soft Reboot works as good with upd1 as it did with FE
People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Re: Soft reboot hangs on FE upd 1
Are you sure that amigaboot.of has been updated?
When i got my X1000 the amigaboot.of was on a small FFS partition (50MB) named BDH0: (with disabled automount so that it does not show up normaly), and the OS itself was installed on DH0: using SFS.
I keeped it that way, but had to manually update the file (default path is SYS: ).
When i got my X1000 the amigaboot.of was on a small FFS partition (50MB) named BDH0: (with disabled automount so that it does not show up normaly), and the OS itself was installed on DH0: using SFS.
I keeped it that way, but had to manually update the file (default path is SYS: ).
Re: Soft reboot hangs on FE upd 1
Just for comparision..
amigaboot 53.21 (13.06.2016) on SYS:
amigaboot 53.21 (13.06.2016) on SYS:
People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Re: Soft reboot hangs on FE upd 1
Same for me.Raziel wrote:Just for comparision..
amigaboot 53.21 (13.06.2016) on SYS:
Marko
Marko
- MichaelMerkel
- Beta Tester
- Posts: 355
- Joined: Mon Dec 20, 2010 2:08 pm
- Location: Germany
- Contact:
Re: Soft reboot hangs on FE upd 1
he could open a shell and type:ZeroG wrote:Are you sure that amigaboot.of has been updated?
When i got my X1000 the amigaboot.of was on a small FFS partition (50MB) named BDH0: (with disabled automount so that it does not show up normaly), and the OS itself was installed on DH0: using SFS.
I keeped it that way, but had to manually update the file (default path is SYS: ).
Code: Select all
nvgetvar
Code: Select all
MENU_0_COMMAND=bootauto ; setenv amigaboot_quiet Y ; boot -fs=amigafs ide0.1:amigaboot.of
M
so to be sure check with mediatoolbox if there exists a "boot" partition before the actual partitions.
regards...
michael
Michael Merkel
(Member of Amiga Freunde Pfalz)
(Member of Amiga Freunde Pfalz)
Re: Soft reboot hangs on FE upd 1
Thanks for both, actually found the BDH0: partition which contained amigaboot.of v 53.4 and the boot partition is actually the partition 0:MichaelMerkel wrote:he could open a shell and type:ZeroG wrote:Are you sure that amigaboot.of has been updated?
When i got my X1000 the amigaboot.of was on a small FFS partition (50MB) named BDH0: (with disabled automount so that it does not show up normaly), and the OS itself was installed on DH0: using SFS.
I keeped it that way, but had to manually update the file (default path is SYS: ).in the resulting output check for all lines containing "amigaboot.of" e.g. smth like:Code: Select all
nvgetvar
this points to the place amigaboot is loaded from. in my case the first partition on the fist diskCode: Select all
MENU_0_COMMAND=bootauto ; setenv amigaboot_quiet Y ; boot -fs=amigafs ide0.1:amigaboot.of M
so to be sure check with mediatoolbox if there exists a "boot" partition before the actual partitions.
regards...
michael
Code: Select all
MENU_0_COMMAND=setenv amigaboot_quiet Y ;boot -fs=amigafs ide0.0:amigaboot.of
Marko
BTW, is the AmiUpdate/Installer able to mount these hidden boot partitions or is it the "things you just have to know" if amigaboot.of is updated in the future?
Marko
Marko
- MichaelMerkel
- Beta Tester
- Posts: 355
- Joined: Mon Dec 20, 2010 2:08 pm
- Location: Germany
- Contact:
Re: Soft reboot hangs on FE upd 1
no. it's the users choice where to place the amigaboot file and if the partition is visible or not.blmara wrote: BTW, is the AmiUpdate/Installer able to mount these hidden boot partitions or is it the "things you just have to know" if amigaboot.of is updated in the future?
so you could mount it and hide it from workbench to get a similar result. but then you can at least access it with filer/asl requester.
strange that you have this boot problem. no idea actually
regards...
michael
Michael Merkel
(Member of Amiga Freunde Pfalz)
(Member of Amiga Freunde Pfalz)
- tonyw
- AmigaOS Core Developer
- Posts: 1479
- Joined: Wed Mar 09, 2011 1:36 pm
- Location: Sydney, Australia
Re: Soft reboot hangs on FE upd 1
It can't be an amigaboot problem. Amigaboot doesn't affect a "warm" reboot, since amigaboot is only used to load Kickstart from disk during a cold reboot.
So the real question is: What is happening to kill the reboot?
If you connect a serial terminal, you can find the cause quickly - probably something is crashing. If you can't read the debug output, you could boot "Without Startup-Sequence" and see if that goes better, but that will be slow and frustrating. The serial terminal output is much more useful.
I have an SSD on my X1000 that sometimes won't come up ready. The disk driver then chokes and goes into a loop, spitting out a "timeout" message once a minute, while hogging the system. You will only see the "timeout" message if the system "Debuglevel" is 1 or more.
So the real question is: What is happening to kill the reboot?
If you connect a serial terminal, you can find the cause quickly - probably something is crashing. If you can't read the debug output, you could boot "Without Startup-Sequence" and see if that goes better, but that will be slow and frustrating. The serial terminal output is much more useful.
I have an SSD on my X1000 that sometimes won't come up ready. The disk driver then chokes and goes into a loop, spitting out a "timeout" message once a minute, while hogging the system. You will only see the "timeout" message if the system "Debuglevel" is 1 or more.
cheers
tony
tony
Re: Soft reboot hangs on FE upd 1
While it might be correct that the user can have the boot.of file anywhere he/she wants, it's still a fact that the original AmigaOS4 installer created a hidden bootable FFS partition on the very first install as first partition on the available hdd...and used that to boot from it.MichaelMerkel wrote:no. it's the users choice where to place the amigaboot file and if the partition is visible or not.blmara wrote: BTW, is the AmiUpdate/Installer able to mount these hidden boot partitions or is it the "things you just have to know" if amigaboot.of is updated in the future?
so you could mount it and hide it from workbench to get a similar result. but then you can at least access it with filer/asl requester.
strange that you have this boot problem. no idea actually
regards...
michael
This wasn't rectified or mentioned in the following update installers and as such still remains the default
Now, *if* there is *NEED* to have the boot.of updated (be it because of bug fixes or additions) and the installer does so only on the first "visible" partition it can access (which isn't used by default through CFE, as we just learned), then why doesn't the installer at least tell the user about that...or, even better takes care of the updating of the *used* boot.of file on said hidden partition?
I don't have a problem with updating it on the hidden partition, but other users might not have the knowledge and end up using a buggy boot.of which will draw even more problems in the future, won't it?
EDIT: Just checked, i still had 52.4 from 2010 on the boot partion, updated now, still fine on soft reboot
People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg