Bug#64500: CALL FOR HELP : debian boot floppies 2.2.15 on apus still not ok.
Sven LUTHER <luther@lambda.u-strasbg.fr> writes:
> i give the corrct place in the requester, and dbootstrap tries to loop mount
> the rescue.bin image to fetch the kernel and the modules, and fail.
>
> I then tried testing by hand, with :
>
> $ mount -r -t vfat -o loop=/dev/loop0 resceu.bin /mnt
> Mounting rescue.bin on /mnt failed : block device required
>
> well, i think i found the cause of this error, ...
>
> Now the strange thing, is that when i continue the installation stuff and
> reboot with the same kernel on the partition just installed from the base
> tarball, i can mount the rescue.bin image with the exact command given above.
>
> Thus i suspsect the problem lie with the root.bin image. or maybe the
> dbootstrap mount command.
>
> I have tested to see if loop device is modular or not, (i built the kernel
> with loops included) and got :
>
> $ grep loop /proc/ksyms
> c016a084 loops_per_ser
> c0161278 loopback_dev
> c00aeeac loop_register_transfer
> c00aeee4 loop_unregister_transfer
>
> this should be ok, since i get the same symbols on my i386 2.3.99-pre8 kernel
> here at work.
>
> also i did test the loop0 device :
>
> from the root.bin image :
>
> $ ls -l /dev/loop0
> brw-r--r--r 1 root root 7, 0 Jun 6 21:50 /dev/loop0
>
> (didn't change when i chmoded it to be 666 either :((()
>
> from the base installed system :
>
> $ ls -l /dev/loop0
>
> brw-rw---- 1 root disk ...
>
> Any idea of what is going wrong here ?
Sounds like busybox mount bug, yeah. Wonder why it only hits apus??
Did you ever get confirmation? Do you think you can pester andersee
directly?
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: