You are not logged in.
Hi,
Burnt beowulf minimal LiveCD (no DT) onto a CD-R media, which booted just fine on the old MBP.
'grub-install' trapped the following error on the LiveCD VM install to HDD:Installing for i386-pc platform. grub-install: error: unable to identify a filesystem in hostdisk//dev/sda; safety check can't be performed.
Your comments, where the MBP is exempt from this glitch in the matrix?
englee
If you are installing from the minimal-live, there will already be at least one ext2/3/4 filesystem on the virtual disk when you get to the grub-install stage. What do fdisk and blkid show for the disk? What virtualization software are you using on the mac? Maybe it does something differently from what I expect.
No, mate-media in beowulf is the stock debian version. You can get the antofox forks here - http://hezeh.org/packages/
There's no specific iso for macs, but the amd64 desktop-live has both the 32 and 64-bit bootloaders and is know to work on at least one old macbook pro. If you do in fact need the 32-bit bootloader, you will need to install the grub-efi-ia32 package in the live environment before you install the system. You can install it with apt if you have network, or you can install it with
dpkg -i /grub-efi-ia32*.deb
When you install the package, don't let it install the bootloader at that time. The live installer (Refracta Installer) will let you choose the efi partition if there are two or more.
Make sure you check if that's what you need with
cat /sys/firmware/efi/fw_platform_size
before you try the 32-bit bootloader.
I'm not sure that will be enough. You still need a way to make the machine boot from the usb drive. Google says hold down the option key at boot and then select the usb drive.
Are you using 'allow-hotplug' or 'auto' in /etc/network/interfaces? Whichever one you're using, you could try the other and see if it makes a difference.
A netinstall from a 3.0 iso would give you 3.1 or actually a little newer than that since some packages have been upgraded since last week. Volume settings on my up-to-date mate don't get lost. I do keep losing the hardware setting. Analog Stereo Output keeps reverting to Analog Stereo Duplex.
I tried running 'alsactl store' before rebooting and 'alsactl restore' after reboot. It didn't save the hardware setting.
I'm going to update my backports test iso today and will post the link later.
The desktop-live isos already have firmware-amd-graphics installed. Maybe the version from backports is needed. I don't have an easy way to test that right now. And debian wiki suggests that this is not the problem. (4.19 is new enough)
FYI: Some macbook pros use a 32-bit efi bootloader with a 64-bit operating system. I know the 2011 ones did that. Not sure about the 2013 models or how to tell which grub it needs.
Missing from beomint:
https://paste.debian.net/1192135/
Missing from debbowulf:
https://paste.debian.net/1192136/
The one that looked obvious was debian-mate-default-settings, which is missing in the system that does save its settings. So I tried removing that from my mate. The result was no panel and no righ-click menu on the desktop.
I also tried installing and running dconf-editor to see if there was something about audio settings in it. There is. Toggling "use default mixer device" did not fix it.
I don't know what to try next. Do you know where mate saves its settings?
The post at Dev1 that I linked to, which had the same /usr/sbin/anacron --> /bin/true and deviations apparently was not/had not been using Refractainstaller.
So something other used live-config and generated the same problem.
https://dev1galaxy.org/viewtopic.php?id=1901
That was a miyolinux system, which uses refractainstaller.
The way it's designed, the live-config change should not need to be undone as it only exists in the running live system. If you mount the filesystem inside the live-iso to look at it when it's not running, you would find that the diverted file does not exist. It gets created by live-config when the system boots.
uh-oh...
I haven't been paying close attention to this thread.
live-config messes with anacron via the live-config script, /lib/live/config/1110-anacron which uses dpkg-divert to disable anacron. This is useful in a live-CD where everything is read-only.
This only activates when you boot into a live system, not an installed system.
Refractainstaller copies the RUNNING live system to hard drive.
You just uncovered a 10-year-old bug that I didn't know about. The installer needs to undo this during the installation.
I suspect that the right way to undo it is to use dpkg-divert.
# ls -l /usr/sbin/anacron*
lrwxrwxrwx 1 root root 9 Apr 2 2018 /usr/sbin/anacron -> /bin/true
-rwxr-xr-x 1 root root 38928 Feb 6 14:18 /usr/sbin/anacron.orig.anacron
# dpkg-divert --remove /usr/sbin/anacron
dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
Removing 'diversion of /usr/sbin/anacron to /usr/sbin/anacron.orig.anacron by live-config'
And then to verify that it really did what it was supposed to do (but did not):
# ls -l /usr/sbin/anacron*
lrwxrwxrwx 1 root root 9 Apr 2 2018 /usr/sbin/anacron -> /bin/true
-rwxr-xr-x 1 root root 38928 Feb 6 14:18 /usr/sbin/anacron.orig.anacron
Yet dpkg-divert thinks it did the right thing:
# dpkg-divert --remove /usr/sbin/anacron
dpkg-divert: warning: please specify --no-rename explicitly, the default will change to --rename in 1.20.x
No diversion 'any diversion of /usr/sbin/anacron', none removed.
Computer, do as I say!
# mv /usr/sbin/anacron.orig.anacron /usr/sbin/anacron
# ls -l /usr/sbin/anacron*
-rwxr-xr-x 1 root root 38928 Feb 6 14:18 /usr/sbin/anacron
root@nomad:/home/phred#
I'll reboot and see what happens.
Update: I see this in syslog for the first time after reboot. I think it's working now.
Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.daily' in 5 min.
Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.weekly' in 10 min.
Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.monthly' in 15 min.
Over here it's 04/01 and people have been doing this at least as long as debian-live has been around. This "new" implementation sounds like it might be a useful addition for a couple of specific cases.
If you have one of each of these systems, you could compare package lists. Or make two package lists and paste them somewhere like paste.debian.net and I will compare them.
dpkg -l | awk '/^ii/ { print $2 " " $3 }' > package_list
I fired up the antix full runit iso. Here's a list of runscripts they have that are not in Lorenzo's collection. This is as far as I've gotten with it. I haven't tried any of these yet or even looked inside the files.
AntiX has:
bluetooth, connman, ntp, ofono, rpcbind, rsync,
rsyslog, smartmontools, tlp, udevd, ufw
Here's the final version (I think). Tested in xfce (thunar) and mate (caja), both in chimaera. I'll rebuild the package later today.
.rubberband,
.view .rubberband,
view rubberband,
rubberband {
background-color: alpha (@theme_selected_bg_color, 0.35);
border-color: @theme_selected_bg_color;
border-style: solid;
border-width: 1px;
border-radius: 2px;
}
Back in June I posted in this thread and said there needs to be a live-config-runit package. Well, now there is. I forked live-config. The version currently in ceres includes live-config-runit. (11.0.2-1+devuan2). It will move into chimaera soon.
IMPORTANT NOTE: If you have live-config installed, when you try to install runit-init, apt will want to remove live-config (and refractasnapshot, if that's installed.) The way to get around this is to include live-config-runit in the command to install runit-init.
For beowulf, I just made an easy single live-config-runit package that isn't in the repo. You can get that here: http://distro.ibiblio.org/refracta/file … u1_all.deb Install it before you try to install live-config and after you install runit. (i.e. stuff might get put on the autoremove list. Just reinstall things if you need to.)
Another note: I did not replace the live-config init script with a run script. That's a project for a later date.
On my T420 running chimaera, I get the same message about iwl-debug-yoyo.bin, but there's no boot delay. I don't have any error messages about regulatory.db. That loads ok.
I don't know where to go with this. Just thought I'd add some data points.
Hi golinux,
I've been using the Chimaera theme for about a week now, and I really like it. But I just noticed a small glitch - on the MATE Desktop, the selection rectangle is an opaque solid white instead of translucent blue, covering up whatever it is one is trying to select. I guess I don't make group selections of things on the desktop very often, because I just noticed this yesterday :-) Anyway, thought you ought to know.
You're right. I just tried this in chimaera with mate. It also does it in beowulf with xfce and the cinnabar theme. Maybe we can figure out how adwaita does it and do the same in our themes.
Here's deepsea-icon-theme. It's in ceres now and will move down to chimaera next week.
deb package is here:
https://pkgmaster.devuan.org/devuan/poo … .0_all.deb
There were no new packages in chimaera for a couple of days, and now there are. I think it's possible that there really were no new packages. Buster is in freeze, so the changes should be slowing down.
set root=(hd0) # might be hd1 or hd2
linux /boot/isolinux/linux
initrd /boot/isolinux/initrd.gz
boot
But you will be booting and installing in uefi mode. Legacy boot will give you an isolinux boot menu instead of a grub boot menu. Is there a way to force a legacy boot?
I found the problem in the minimal-live. The fix is:
apt update
apt remove librsvg2-2
apt install librsvg2-2
That will drop the version from 2.44.10-2.1+deb10u3 to 2.44.10-2.1. And then you can install firefox-esr and the other stuff.
The problem is that the build process pulled in librsvg2-2 from beowulf-proposed-updates, but then that repo was removed from sources.list. I'll have to make a new set of isos.
Berni, if your last post is after a netinstall, then there may be another problem, too.
I'm using runit-init in chimaera. The getties, acpid and ssh were all set up automatically. I set up others using advice from this thread.
sendkey ctrl-alt-f2 worked. Thanks!
Also forgot to meniton - if you make a new runlevel and decide to change its name, don't change it while you are in that runlevel, and pay attention to the symlinks in /etc/runit/runsvdir. My system was unbootable because of a dead symlink for default that pointed to the old name.
I wanted to be able to boot to console on occasion. With sysvinit, I just turn off the display manager in runlevel 3 and put a '3' in the boot command when I want that. It's pretty easy to make a new runlevel in runit.
1. Create a directory in /etc/runit/runsvdir/ named for the new runlevel. Check man pages for the reserved names.
2. Populate it with symlinks to services in /etc/sv/
3. Change to that runlevel with a command or boot to that runlevel with a directive in the boot command.
I did it like this and got the symlinks right without having to make them all manually or script it.
cd /etc/runit/runsvdir
mkdir testt
cp -a default/* testt/
rm testt/lightdm
Add this to the linux line of a boot entry to be able to boot to the new runlevel:
runitdir=testt
This is working correctly.
To change to the new runlevel after a default boot:
runsvchdir testt
This isn't working for my example. It drops to a black screen with a blinking cursor, and I'm in a VM window, so I can't switch tty. It does work when changing to the default runlevel after booting to console.
People use virtualbox because it's easy to figure out how to do things with it.
So how does one attach a usb drive in qemu? I saw two ways to do it and one way not to do it in the man page, but not really an explanation of how to do it. Anyone have a quick answer so I don't have to spend the time experimenting?