Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

On Thu, Nov 28, 2019 at 11:31 PM Toomas Soome wrote: > > > On 28. Nov 2019, at 22:20, Andrey Fesenko wrote: > > > > Fixed > > > > Thanks. And yea, that one is nasty. I have some guess but nothing too solid… > it may take time to get figured out. > > Have you tested BIOS boot? > > rgds, > toomas

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

On Thu, Nov 28, 2019 at 11:31 PM Toomas Soome wrote: > > > > > On 28. Nov 2019, at 22:20, Andrey Fesenko wrote: > > > > Fixed > > > > Thanks. And yea, that one is nasty. I have some guess but nothing too solid… > it may take time to get figured out. > > Have you tested BIOS boot? > > rgds, > too

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

> On 28. Nov 2019, at 22:20, Andrey Fesenko wrote: > > Fixed > Thanks. And yea, that one is nasty. I have some guess but nothing too solid… it may take time to get figured out. Have you tested BIOS boot? rgds, toomas > On Thu, Nov 28, 2019 at 11:18 PM Toomas Soome wrote: >> >> >> >> O

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

Fixed On Thu, Nov 28, 2019 at 11:18 PM Toomas Soome wrote: > > > > On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: > > On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > > > hi! > > I did try to reach you, but mail did bounce back… > > unicast ping me:) > > rgds, > toomas > > On 28. Nov 201

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

> On 28. Nov 2019, at 22:16, Andrey Fesenko wrote: > > On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome > wrote: >> >> hi! >> >> I did try to reach you, but mail did bounce back… >> >> unicast ping me:) >> >> rgds, >> toomas >> >>> On 28. Nov 2019, at 11:43, Andrey Fesen

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

On Thu, Nov 28, 2019 at 9:20 PM Andrey Fesenko wrote: > > On Thu, Nov 28, 2019 at 1:24 PM Eugene Grosbein wrote: > > > > 28.11.2019 16:43, Andrey Fesenko wrote: > > > > > Hello, > > > > > > Around starting 20191114 r354699 (memstick tested), my desktop not > > > boot normally. Boot only loader me

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

On Thu, Nov 28, 2019 at 3:03 PM Toomas Soome wrote: > > hi! > > I did try to reach you, but mail did bounce back… > > unicast ping me:) > > rgds, > toomas > > > On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > > > > Hello, > > > > Around starting 20191114 r354699 (memstick tested), my desktop n

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

On Thu, Nov 28, 2019 at 1:24 PM Eugene Grosbein wrote: > > 28.11.2019 16:43, Andrey Fesenko wrote: > > > Hello, > > > > Around starting 20191114 r354699 (memstick tested), my desktop not > > boot normally. Boot only loader menu (black and white mode) after > > start i'm see load modules, after thi

Re: EFI loader failure, after 20191114-r354699 Z87MX-D3H

hi! I did try to reach you, but mail did bounce back… unicast ping me:) rgds, toomas > On 28. Nov 2019, at 11:43, Andrey Fesenko wrote: > > Hello, > > Around starting 20191114 r354699 (memstick tested), my desktop not > boot normally. Boot only loader menu (black and white mode) after > star

EFI loader failure, after 20191114-r354699 Z87MX-D3H

Hello, Around starting 20191114 r354699 (memstick tested), my desktop not boot normally. Boot only loader menu (black and white mode) after start i'm see load modules, after this monitor gray, and 15-20s disabled, system block not disable but run silently. system not boot. If i'm change efi (EFI

Re: Lua Loader Failure to Include

On Mon, Feb 11, 2019 at 9:14 AM Cy Schubert wrote: > > On February 11, 2019 5:05:37 AM PST, Cy Schubert > wrote: > >Hi, > > > >Under the old Forth loader the line: > > > > include /boot/testbed/test_sys > > > >would load the file and execute loader commands. > > > >However the the Lua load

Re: Lua Loader Failure to Include

On February 11, 2019 5:05:37 AM PST, Cy Schubert wrote: >Hi, > >Under the old Forth loader the line: > > include /boot/testbed/test_sys > >would load the file and execute loader commands. > >However the the Lua loader results in the following: > >OK include /boot/testbed/amd64-current-r >no

Lua Loader Failure to Include

Hi, Under the old Forth loader the line: include /boot/testbed/test_sys would load the file and execute loader commands. However the the Lua loader results in the following: OK include /boot/testbed/amd64-current-r no error message OK Looking at the code, interp_include() expects to r

Re: loader failure

On 16-May-2002 Dag-Erling Smorgrav wrote: > John Baldwin <[EMAIL PROTECTED]> writes: >> e -n 100 > > Yep, this (well, e -w -n 100 blah, and a number of variations) is what > I tried. This works on my PWS 500au but not on the DS20. >> e -n 100 vmem: > > I guess the address space specifier is

Re: loader failure

On Wed, 15 May 2002, John Baldwin wrote: > On 15-May-2002 Dag-Erling Smorgrav wrote: > > John Baldwin <[EMAIL PROTECTED]> writes: > >> The kernel overflowed it's stack. In SRM, you can try to debug this > >> by using 'e sp' to get the stack pointer then get a stack dump and save > >> a copy of i

Re: loader failure

John Baldwin <[EMAIL PROTECTED]> writes: > e -n 100 Yep, this (well, e -w -n 100 blah, and a number of variations) is what I tried. > e -n 100 vmem: I guess the address space specifier is what was missing. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PR

Re: loader failure

> > Brian Somers <[EMAIL PROTECTED]> writes: > > > This was fixed an hour or so ago. Phk backed out the daddr_t size > > > change pending investigation. > > > > Does that fix the loader too, or just the kernel? > > I'm not sure, I'm just rebuilding now. > > Remember, /boot/loader.old is left

Re: loader failure

On 15-May-2002 Dag-Erling Smorgrav wrote: > John Baldwin <[EMAIL PROTECTED]> writes: >> The kernel overflowed it's stack. In SRM, you can try to debug this >> by using 'e sp' to get the stack pointer then get a stack dump and save >> a copy of it in a log or something, reboot the machine, then u

Re: loader failure

> Brian Somers <[EMAIL PROTECTED]> writes: > > This was fixed an hour or so ago. Phk backed out the daddr_t size > > change pending investigation. > > Does that fix the loader too, or just the kernel? I'm not sure, I'm just rebuilding now. Remember, /boot/loader.old is left around... handy in

Re: loader failure

Brian Somers <[EMAIL PROTECTED]> writes: > This was fixed an hour or so ago. Phk backed out the daddr_t size > change pending investigation. Does that fix the loader too, or just the kernel? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "u

Re: loader failure

> > no matter which kernel I try to boot. Booting my new kernel with the > > old loader (from the DP1 dist) works fine until it tries to start > > init(8): > > > > spec_getpages: preposterous offset 0xfff8f446 > > exec /sbin/init: error 5 > > spec_getpages: preposterous offset 0xfff8

Re: loader failure

John Baldwin <[EMAIL PROTECTED]> writes: > The kernel overflowed it's stack. In SRM, you can try to debug this > by using 'e sp' to get the stack pointer then get a stack dump and save > a copy of it in a log or something, reboot the machine, then use gdb's > list command on the kernel.debug to f

Re: loader failure

On Wed, May 15, 2002 at 02:22:04PM +0200, Dag-Erling Smorgrav wrote: > Trying to boot with a newly-built loader (make world earlier today > from fresh sources) results in: > > FreeBSD/alpha SRM disk boot, Revision 1.2 > ([EMAIL PROTECTED], Wed May 15 08:01:43 CEST 2002) > Memory: 262144 k > Loadi

Re: loader failure

Dag-Erling Smorgrav writes: > Trying to boot with a newly-built loader (make world earlier today > from fresh sources) results in: <..> > boot failure > > no matter which kernel I try to boot. Booting my new kernel with the > old loader (from the DP1 dist) works fine until it tries to sta

RE: loader failure

On 15-May-2002 Dag-Erling Smorgrav wrote: > Trying to boot with a newly-built loader (make world earlier today > from fresh sources) results in: > > FreeBSD/alpha SRM disk boot, Revision 1.2 > ([EMAIL PROTECTED], Wed May 15 08:01:43 CEST 2002) > Memory: 262144 k > Loading /boot/defaults/loader.c

loader failure

Trying to boot with a newly-built loader (make world earlier today from fresh sources) results in: FreeBSD/alpha SRM disk boot, Revision 1.2 ([EMAIL PROTECTED], Wed May 15 08:01:43 CEST 2002) Memory: 262144 k Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x283780+0x63670 / Hit [Ent