Re: Installing rescue.bin -> udbootstrap exited

[Filippo Basso <filippo@zirak.it>]

> As it mentions in the manual, you can cause debug / verbose level messages
> by adding the boot arguments debug and/or verbose.

Thank you, I was remembering something like that, but didn't remember 
where... ;-)

What happens if I start with the "pxe debug verbose" at the "boot:" prompt is 
that after loading rescue.bin/drivers.tgz, either from network (http) or from 
hard-disk (yes, I've saved them in another partition the copies that 
dbootstrap does inside /target/tmp), suddenly there is a Segmentation Fault:

Segmentation Fault
Registers:
	EAX: 0000 0000
	EBX: bfff ccf4
	ECX: ffff ffff
	EDX: 0000 0006

	EDI: 0000 0000
	ESI: 0000 0000
	EBP: bfff cc60
	ESP: bfff cc5c

	EIP: 4006 f3ff
	EFLAGS: 0001 0246

	Trap: 0000 000e    Code: 0000 0004
Backtrace:
	/sbin/dbootstrap [0x80532d5]
	/sbin/dbootstrap [0x805654a]
	                 [0x7420676e]


???
any hints ?!?

> Hope it helps, looks like it's getting the files OK and runs into a hitch
> later. You could look to see if /target/boot contains your kernel, that's
> what should be happening when it exits?

no, the /target/boot/ is void (only "lost+found" directory)...

-------------------

Now, I think that I can jump out of the problem, because at that point I have 
network+scsi, so I can install a minimal linux downloading it with wget 
(already present in root.bin)... but if I can help somewhat to solve that 
problem it can be good.

Now I'm going to see if I can start in that "alternative" way... but please 
keep in touch to see if we can solve that problem in an smart way!

thank you,
	fi

P.S. what are now the ways to understand why that happened ?!?