Hi,
Daniel Lewart wrote:
> I did find 215 MiB of exact duplicate files.
> ...
> 24724624 Oct 30 10:07 firmware/firmware-atheros_20240909-2_all.deb
> 24724624 Oct 30 10:07
> pool/non-free-firmware/f/firmware-nonfree/firmware-atheros_20240909-2_all.deb
These two most probably share their content i
Hi,
Sakkra Billa wrote:
> In order to
> install it on my VM I installed calamares, calamares-settings-debian and
> rsync
My advise from debian-user to ask at debian-boot was rather a reply to
your other statement:
Sakkra Billa wrote:
> > I tried debian di too but wasn't successful in that
> > ei
Hi,
John Paul Adrian Glaubitz wrote:
> But in the end, I get:
> libisofs: WARNING : Cannot add /debian to Joliet tree. Symlinks can only be
> added to a Rock Ridge tree.
This is normal, unavoidable, and harmless. All debian-cd runs will issue
this kind of message if symbolic links are present in
Hi,
Wouter Verhelst wrote:
> http://anonscm.debian.org/cgit/d-i/debian-installer.git/tree/build/util/geniso_hybrid_plus_firmware_partition
> I add a line isohybrid -u "$iso"
This last isohybrid run replaces the partition which was crafted
by the fdisk run.
This is also the reason why fdisk does
Hi,
Wouter Verhelst wrote:
> This image however does not support booting on a UEFI-only system.
It does support EFI booting from CDROM. At least with qemu and OVMF
as EFI firmware.
> Is there anyone with the required knowledge who would be willing to
> look into fixing that?
I downloaded
ht
Hi,
Steve McIntyre wrote:
> I'm told
> that Grub can do all the needed stuff to boot CDs as well, so I'm
> curious to test it.
Debian kfreebsd mini.iso already uses GRUB2 for BIOS.
amd64 and i386 have about the same equipment:
Volume id: 'ISOIMAGE'
El Torito catalog : 55 1
El Torito
Hi,
Aurelien Jarno wrote:
> I have no idea if they support booting over a
> CD-ROM or USB image. Does someone known if we can do so on a Loongson 3
> or Octeon machine?
Maybe one should ask grub-de...@gnu.org mailing list or
Vladimir Serbinenko directly.
-
Hi,
the new images of august 28 2015 boot with qemu-system-x86_64.
The i386 one boots with qemu-system-i386.
I will now study whether and how it is appropriate to
close this bug.
Have a nice day :)
Thomas
Hi,
since my test ISO was only BIOS El Torito, and not isohybrid
and EFI El Torito, i repeated the test with the original
/isolinux.bin of mini.iso and only BIOS El Torito.
This one does not boot.
So it is really about the binary, not obscure stray effects
from fancy boot records.
Have a nice d
Hi,
i now tested on real hardware:
AMD 4x2.4 MHz five years old, Award BIOS 6.00
with amd64 mini.iso on USB stick and DVD+RW.
Same effect as with qemu.
It makes no progress after saying "EHDD" or "ETCD".
Since it cannot get any worse, i replaced /isolinux.bin
of amd64 mini.iso by /isolinux/isol
Package: debian-installer
Version: ?
Severity: important
Tags:
Dear Maintainer,
http://ftp.debian.org/debian/dists/unstable/main/installer-amd64/current/images/netboot/mini.iso
http://ftp.debian.org/debian/dists/unstable/main/installer-i386/current/images/netboot/mini.iso
with website date "20
Hi,
Sébastien Bernard:
> Cheers to team work.
Special cheers to Patrick Baggett !
And thanks to all who cared for this problem. I'd need more
users who don't shrug but complain and tell me that i'm wrong.
The bug fix is now committed as
http://libburnia-project.org/changeset/5324
(We still d
Hi,
Sebastien's machine now has a xorriso-1.3.7 (the current development
snapshot) with changed libburn/async.c.
The callers of add_worker() now declare:
union w_list_data o;
rather than
struct union_member o;
The type of the fourth parameter of add_worker has been changed
fro
Hi,
> No, it's plain wrong. Unions are fine, if used properly. You aren't
> using them properly.
Duh. You convinced me. The callers do it wrong, indeed.
They would have to use local union variables instead of their actual
structs. The parameter of add_worker() should be a pointer to the
union, no
Hi,
> I really need a disassembly and to be able to probe the runtime
> stack a bit, so that really means that I need to build the code. :)
The current example would be a bit too opulent, i guess:
-rwxr-xr-x 1 thomas thomas 3753398 avril 28 17:49 xorriso/xorriso
(wget http://www.gnu.org/softw
Hi,
i wrote:
> struct write_opts write;
> ...
> add_worker(Burnworker_type_writE, d,
> (WorkerFunc) write_disc_worker_func, &o);
Urgh. I copied the wrong struct definition. Line 592 bears of course:
struct write_opts o;
which is used in the call of add_worker().
Ha
Hi,
Patrick Baggett:
> Could you explain the context around this code? Perhaps the source is
> not really "alignment safe" and could use some patching upstream? I'd
> be happy to provide advice or code samples.
The context was misposted to bug report 731806 as message #87:
https://bugs.debian.o
Hi,
sorry for mis-posting the first reply for bug 746254 to this bug 731806.
Meanwhile it turned out that the SIGBUS vanishes if i do not
compile with -O2 or if i replace "a->u =" by memcpy().
So it seems worth to check whether genisoimage resp. strcmp() work
properly if not compiled with -O2.
Hi,
> Program received signal SIGBUS, Bus error.
> add_worker (w_type=3, d=0x161128 , f=0xd1b20
> 149 a->u = *(union w_list_data *)data;
Other than expected from the first report in bug 731806,
the problem does not sit in libisofs but in libburn/async.c.
(Other predecessor developer
Hi,
Sébastien Bernard:
> result from strcmp('\','\0001' is 0)
> result from strcmp('\','\0001' is -1)
> Typicaly, an endianness error.
But one in strcmp(), not in your code or the one of genisoimage.
You compare an empty string with a string that contains one
character 0x01.
This is under
Hi,
> I may provide you access to a shell account on my machines if needed.
Yes, please.
Plus a directory tree
./tmp/miniiso/cd_tree
which can cause the xorriso crash.
> Sparc architecture is extremely picky about alignement. Bad alignement,
> yields SIGSEGV whereas intel only do it in the l
Hi,
> I tried with the xorriso -as mkisofs command, with no luck.
> This command terminates with a SIGBUS no matter of the options I pass on
> the command line.
Ouch.
I have no Debian of arch "sparc" in reach.
> xorriso -as mkisofs -r -J -o ./tmp/miniiso/mini.iso -G /boot/isofs.b -B
> ... ./t
Hi,
Steven Chamberlain:
> I'm unfamiliar with xorriso but the man page mentions "-joliet on"
The problem is that argument "--" marks the end of the parameter
list of xorriso command "-as mkisofs".
Both versions of grub-mkrescue start xorriso with that command and
use mkisofs-ish options to define
Hi,
> I'm not sure we want to continuously give it back until it builds (which
> it might on schroeder, since it didn't fail there yet)...
I would assume the problem is deterministic and depends on
the exact tree of file names which is given to genisoimage
as input.
So adding a few names of empty
Hi,
Cyril Brulebois wrote:
> genisoimage: Error: './tmp/miniiso/cd_tree/boot/.' and
> './tmp/miniiso/cd_tree/boot/..' have the same ISO9660 name ''.
> [...]
> Probably some FS-dependent fun? Anyone would have a clue about it?
Looks like an internal error of genisoimage.
'.' should be mapped to a
Hi,
> We'll just have to see if we get any more feedback.
Please keep me informed about any problems which are suspicious
to come from the early boot stages when the firmware has to find
its first piece of software on the medium.
(There are potential problems with partition tables at later
stage
Hi,
> will hopefully fix a number of the issues we're seeing with UEFI.
What problems are there in particular ?
Similar as with BIOS we have two main starting points of booting:
El Torito for CD, DVD, BD.
GPT for hard disk and alike.
But i do not know whether the distinction between both is as s
Hi,
out of curiosity i compared systemrescuecd-x86-3.2.0.iso and
debian-wheezy-amd64-efi-test5.iso.
One important difference is that systemrescuecd has no MBR or GPT.
The whole system area is filled with zeros, where test5 is generously
equipped with hard disk partition tables. I see MBR, GPT, an
Hi,
> 1.2.4 apparently comes with quite a number of improvements in the EFI area,
And it had some bugs with -partition_offset and GPT.
I am in the progress of releasing 1.2.6 with libisoburn/xorriso
release note:
* Bug fix: -partition_offset 16 kept -isohybrid-gpt-basdat from writing
Hi,
Bjørn Mork wrote:
> On a default Debian system you need to be a member of
> the "floppy" group.
Ferenc Wagner wrote:
> What about recommending /dev/disk/by-id/usb-X instead?
I understand that the instructions about creating a Debian installation
medium shall be usable on as many systems as
Hi,
Steve McIntyre wrote:
> (http://www.debian.org/releases/stable/amd64/ch04s03.html.en) but
> skipped straight past section 4.3.1. Looks like we could do with a big
> clear message "DO THIS UNLESS YOU HAVE SPECIAL NEEDS" to make it more
> obvious. :-)
I am a bit scared by the catastrophic poten
Hi,
> Fedora/RH folks recently added more
> hacks to isohybrid to support booting on Macs:
> http://mjg59.dreamwidth.org/11285.html
This is achieved by applying ISOLINUX program isohybrid from a recent
ISOLINYX version to the already produced ISO images. syslinux-4.05
should probably do.
It is a
Hi,
Ryan Braun wrote:
> And for reference, here is the command I used to build
> the image, as for all my googling I could not find an example of
> using xorriso to make an image (outside of .disk/mkisofs that wasn't
> working for me :) )
The image production command in .disk/mkisofs consists of
Hi,
Ryan Braun wrote:
> Ok guys, having some trouble getting a working iso out of xorriso. It
> generates an iso, but there are some warnings.
I do not see this option among your xorriso -as mkisofs arguments:
-boot-info-table
It is necessary for the ISOLINUX boot image to work properly.
The
Hi,
Ryan Braun wrote:
> > is there some kind of magic that needs to be done to the iso
> >in order to be able cat squeeze.iso > /dev/sdb?
Steve McIntyre wrote:
> -isohybrid-mbr syslinux/usr/lib/syslinux/isohdpfx.bin -partition_offset 16
Instead of syslinux/usr/lib/syslinux/isohdpfx.bin one may
Hi,
maybe one should mention the following points in an
expert section:
- The whole isohybrid aspect can be removed by zeroing
the first 32 kB of the image.
Then it is a conventional CD bootable ISO image.
This solved the problem to mount on "Snow Leopard" systems.
http://lists.debian.
36 matches
Mail list logo
