You are not logged in.
https://sourceforge.net/projects/refracta/files/tools/
I just uploaded fixed live-boot deb packages I made for myself in October. These have a newer version number than what's in the repo, so they will replace the broken live-boot packages. I used these to make the daedalus live test isos.
Bug reports have been submitted for the live-boot-initramfs-tools problem.
https://bugs.debian.org/cgi-bin/bugrepo … ug=1010951
The fix is in git.
https://salsa.debian.org/live-team/live … 8678106523
Still waiting for the package to be built with the fix. I really don't want to fork live-boot for this.
Several years ago I discovered that the software that cycles through the USB ports looking for the non-free device drivers on a usb stick, only looks at USB-a and USB-b ports. It does not look beyond this to, say, USB-c (where I initially had the usb stick plugged in)... the code simply cycles back around and ask that a usb drive be inserted with the firmware on it
What software are you using that asks you to insert a usb with firmware? The only thing I know that asks that is the debian/devuan installer that's on the installer isos, not in the devuan live isos or any Refracta isos. That question comes up early in the installer and should usually be ignored. In most cases, the firmware will be installed automatically unless you do an expert install and tell it not to use non-free software. The main exceptions to this are certain broadcom devices that require an internet connection to get the wireless firmware - that poses a serious problem if someone is trying to install and doesn't have an ethernet connection.
If my guess is right, and you're talking about that early question in the debian/devuan installer, then I think the code is probably in the udeb package that asks for the firmware. I don't know that installer well enough to know which udeb that is.
If you install the firmware package while running the live iso on usb, it will be in the system memory only, so it won't survive a reboot. If you install the firmware then install the system to hard drive, the firmware will be in the installed system. It's also possible to install the system first, reboot into the installed system and then install the firmware package.
If you want a live-usb with your wifi driver, you need to set up a persistent volume (rw instead of ro) so your changes are saved. I use refracta2usb for that, but there are other ways.
https://sourceforge.net/projects/refracta/files/tools/refracta2usb-2.4.3.deb
Refracta xfce isos and the no-X isos do not have non-free firmware installed. There are firmware packages in the user's home directory that you can install with dpkg if you don't have a network connection. dpkg -i /home/user/firmware-iwlwifi*.deb
If you do have a network connection, you can add 'contrib' and 'non-free' to the deb lines in /etc/apt/sources.list then run apt update and apt install firmware-iwlwifi.
If you have to install without network, the desktop dvd (3G) is probably the easiest to deal with. But if the live iso worked, then the right firmware package should also be in the installer isos. What intel hardware is not recognized, and are you sure it's not recognized?
If you stopped at the very beginning because the installer told you that you needed to provide the drivers on a usb stick, then run the installer again and ignore that question and proceed. Hardly anyone needs to do that. (a few broadcom chips)
https://files.devuan.org/devuan_chimaera/installer-iso/
Use the netinstall iso unless you must install without using a network mirror. In that case, use the DVD.
The next step is to read the section "Install to RAID1" here: https://dev1galaxy.org/viewtopic.php?id=2323 and decide whether you really want to do it manually with mdadm and refractainstaller or if you would rather use an installer than knows how to set up a RAID without you having to run all the commands yourself. If you choose the latter, you will need to download one of the installer isos and re-image your usb stick.
Note: If I were going to do it manually with mdadm and refractainstaller, I would need to read those instructions I linked. Be aware that I'm the one who wrote those instructions and I'm the one who wrote refractainstaller, and I would still need to re-read the instructions.
Use fat32 for the EFI partition and give it the esp flag. (That will auto-check the boot flag, too.)
"There is no disk with a gpt partition table. You should exit this script and run gdisk to create one for uefi boot. There is no EFI partition. You will need to create one or else install the system without a bootloader."
I recognize that wording. You're using the live installer (refractainstaller) which does not support RAID. But it is possible to use the cli installer with a RAID1 that you created manually. See the first section of this thread: https://dev1galaxy.org/viewtopic.php?pid=11437#p11437
If you use one of the installer isos instead of a live iso, you'll get the debian/devuan installer which does support RAID installs. That process will be the way Ralph described it, and the installer will look more like the pictures in the install guide that you linked way back at the beginning of this thread.
The error message you got from the live installer is to let you know that you booted in uefi mode but your disk doesn't have a gpt partition table. You could re-partition the disk or you could switch to legacy bios boot and keep the mbr partition table. The installer isos will most likely figure out the right thing to do. The live installer expects you to tell it what to do.
I'm not seeing an obvious error there. Sorry. The only other idea I have right now is that somewhere between bios and grub and kernel there's confusion about the order of disks. And I'm not sure what to do to about that other than messing with the disk order in the bios.
Google says some other things to try are:
- use usb2 port instead of usb3 (or a usb2 hub if you don't have a usb2 port)
- try a different usb stick
- set bios to use AHCI instead of IDE (or RAID)
Hm, I thought I already said this, but I don't see it now -
Be sure to dd the iso to the whole device, and not to a partition, for example:
dd if=snapshot.iso of=/dev/sdb (not of=/dev/sdb1)
If you run the cli version of refractasnapshot (as you did) you can add the '-d' option to get a more verbose error log.
refractasnapshot -d
I'd like to see the error log. Either paste.debian.net or send it to me at gmail.
Other things to try: see if the usb boots on another computer, see if it works better with a different usb stick.
First thing I would do is check to make sure filesystem.squashfs was created. Mount the usb in a running system and look to make sure /live/filesystem.squashfs is on the usb. Mount the iso file and look for the same. Look in $work_dir/iso/live/ for the same.
Is this legacy bios boot or uefi boot?
If you go into the display setting, you should be able to set the external monitor to be the primary.
ExeGNU uses refractainstaller. (David Hare was a co-author.) By default, the installer formats the partitions you select. You can disable this in the options menu of the graphical installer or in the config file if you are using the cli installer. The option will affect all selected partitions. Installing a bootloader or not will not change this.
If you want to re-use an existing /home partition, you should not select it during the install. Just install to the root partition and edit fstab afterward to mount the old home partition to /home.
I got back sooner than I expected. At some point when I have more time, I might want to look closer at what you did to see how you got secure boot to work.
To avoid entering the password twice, you have to create a keyfile. On my system with unencrypted /boot and separate root and home partitions that are encrypted (without lvm) I have a keyfile in the root partition to open the home partition.
With encrypted /boot, you have to put the key inside the initramfs.
On this page, scroll down to "Add keyfile to avoid extra passphrase prompt"
Most of what is above that section was already done for you by the live installer. You might need to modify the instructions because the author was also using lvm.
Edit: Oops! "this page" was supposed to refer to
this page --> https://www.dwarmstrong.org/fde-debian/
But the one OP found looks as good or better.
You have:
Package: *
Pin: release o=Devuan, n=chimaera-proposed-updates
Pin-Priority: 100
I have:
Package: *
Pin: release a=chimaera-proposed-updates
Pin-Priority: 100
Check to make sure n= works. I think I changed to a= because that was the only way it worked, but I could be wrong.
Also, using /merged and o=Devuan might mean you won't get proposed updates from Devuan unless you specify proposed-updates, but you will get them from Debian. I'm not sure. You might need to either switch /merged to /devuan or remove the o=Devuan.
Edit: I tested both ways. n=chimaera-proposed-updates is correct, and a=chimaera-proposed-updates does not change the priority.
I think the instructions on the website were written before *-proposed-updates were merged with debian. When I added it to sources.list recently, I forgot about the advice to use /devuan and I made it /merged like all the others. It seems to be working, but there is a potential problem.
*-proposed-updates is a place to put updates that may need additional testing. I think maybe it should have a lower priority so those packages don't get installed automatically.
Edit: We will most likely continue doing it the same way as debian.
https://wiki.debian.org/StableProposedUpdates
Wow, that's weird and annoying. Try installing libc6=2.31-13+deb11u5 (with or without the -t...)
I just did 'apt upgrade' and got the version from chimaera-proposed-updates. I'm actually surprised that I got it, because I thought that proposed-updates did not get installed automatically. In the past, I had to add '-t chimaera-proposed-updates' to the install command. 'apt policy' shows me that proposed-updates has a priority of 500 just like the rest of the repo.
Oh, maybe because you're running u3 and I've been running u4 so there's nothing in the chimaera main repo for me - just in proposed.
apt -t chimaera-proposed-updates install libc6
should do it.
Also, I noticed that the forum link on the Refracta website appears to be dead. It should probably be replaced with this link.
Thanks. I removed three obsolete links. I keep forgetting about the ibiblio site because I mainly use the new website, refracta.org. I should probably replace a bunch of links to point to the new site.
If you don't want to re-make the usb with dd or cat, you might get around the problem with some creative symlinking to /cdrom. I've done it in the past, but it's been a few years. Try linking the usb mountpoint or a relevant directory on the usb to /cdrom.
And in a predictable future?
Debian will work out all the bugs and everything will be fine. Just like always.
(Sorry, I couldn't resist. Any other answer would have turned NSFW.)
I don't know why you're having problems removing wicd. Maybe try removing all the parts instead of just the metapackage.
I do know that you should only have one of those network gui programs installed. If you want to use connman, then remove all of wicd and all of network-manager. You'll have to make your own entry for connman in the startup program list. Tie it to connman-ui-gtk or connman-gtk-ui (whichever is the correct command.)