The officially official Devuan Forum!

You are not logged in.

#1 Devuan Derivatives » How to Partition *and* Encrypt with LVM » 2022-12-25 03:45:31

Replies: 0

I get to the partitioning step in Uhuru (64bit AMD) and attempt to set up one partition (/dev/sda1) for encryption and the other (/dev/sda2) for cleartext.   From there I would like to be able to use LVM to complete my partitioning.   If there is an easy way to do this using the installer, then I must be missing it.

I can check the encrypt box, but only if I request formatting for, say, ext4.   If I request "unformatted" (since I will be using LVM, and there is no "LVM" formatting option, per se), then the checkbox disappears and only comes back if I select one of the other formats.    Of course, the LVM checkbox is available in the listing on the bottom.   The problem is getting LVM *and* encryption both.

I've tried several times with this release of Star.   I've had good luck with Devuan and Refracta, but for some reason, I cannot seem to figure out how to do what I want using the Uhuru installer.   Furthermore, depending on the steps I take, I find that the installer crashes completely (even after a fresh reboot).  I have 1G ram, 1 vCPU, and 20GB disk space.

Rather than try to analyze what I am doing wrong, I'd prefer to be instructed on how to do it the Star Linux way.   If someone could test the solution, that would really be helpful, and I'd be very grateful.  Thanks for your help, if you can.

#2 Re: Other Issues » msi quirk detected; hang on boot » 2021-12-25 16:31:47

Yes, it is definitely a hang.  I allow it to sit for a very long time.   You can't use ssh or a console screen this early in the boot.

My preference is to be very specific and detailed.  People who want to help will appreciate this.   Most times, omitting details will result in respondents asking for them anyway.   Also, it is difficult to describe this concisely given the multiple aspects of the environment this problem arises in.   I do respect your opinion, however, and thank you for your help.

#3 Other Issues » msi quirk detected; hang on boot » 2021-12-25 08:20:20

Replies: 2

While booting one particular PC, I get an error "msi quirk detected" which is followed by a hang.  I found out that msi means message sequence interrupt, which is part of the hardware technology used to make processing more efficient.  The message appears after the grub menu when the video does a screen clear (and I think changes the font and such).  I do not see this with my other PCs which are also hooked up through this same FJGEAR keyboard-video-mouse-switch ("KVMS").   This occurs when trying to boot this box with a Devuan Chimaera thumb drive, as well as an older Devuan which is installed on that PC.  This machine used to boot properly (into Jessie or Ascii, as well as some other distros).  All of them fail now after the screen clear, sometimes halting at the blank screen and other times halting after the msi quirk detected error.

In order to analyze this, I unhooked the machine from the KVMS and placed it on a table that I use as a sort of "bread board" layout.  I have additional power supplies, keyboard, mouse, etc. there; there is no KVMS there, however.  Also, the video connection is VGA there because I use an older terminal for hardware testing.  I found that booting the machine, which had not been turned on for at least a year or so, was a bit random -- sometimes it would boot, other times not.  I went about eliminating possible issues.  I did replace a SATA cable and moved the hard drive to a different location inside the box.   These steps seem to have helped somewhat, and the PC began to boot reliably each time, not getting stuck at the "msi quirk detected" error.   I believed I had resolved the issue.  I could boot the box from the internal hard drive or from a thumb drive consistently.

I moved the box back to the normal place and hooked it back up to the KVMS.   The error message appeared again upon boot.  This got me to thinking about a posting I read while browsing for the mentioned error message.  It said that it could have something to do with the USB subsystem.   One solution is to disable legacy USB, so I tried that.  The problem immediately became clearer to me:  The KVMS is USB (and HDMI), and likely one of the older USB standards.  So I had to re-enable the legacy USB which allowed me to at least have keyboard functionality.

I think the problem may be with the mainboard, which is a 760GM-P23 (ironically, this board is manufactured by MSI, which has nothing to do with the "msi quirk detected" problem reported by the boot; the naming is just coincidental, though maybe the manufacturer is using the technological term for marketing).  The board is also denoted as "MSI 7641."   The board clearly continues to work, as I am able to fully boot it  with VGA.  The board has VGA and DVI but not HDMI.   I use a DVI/HDMI converter when the box is connected to the KVMS.  Nominally, the configuration works, but somehow this board does not seem to enjoy talking to the keyboard through my switch sometime after the initial screen blanking.

There are lots of posts about this online, but most of them are more than 10 years old; I would think this issue had long since been addressed in recent kernels.  This is (was) a popular board so its chipset should have made it into the kernel blacklist by now.   The solutions suggested (if any) don't seem to help with my specific board.  There are some more recent posts, but I found them to be in the context of other issues.  I note that kernel mailing list discussions about msi date back as early as the mid-2000s, so the devs were tackling that already.

Since my other PCs work reliably enough through the same KVMS, I am leaning toward the board or the kernel or both not being capable of handling the switch traffic after some point in the boot process.  This is only my guess though -- I am really not much of a hardware guru, and I have not studied Linux internals deeply (though I have plenty of Unix internals study behind me).

One other thing to note is that I vaguely recall that many years ago when this board was in a different case and I was using it as my primary machine, I had run into a similar problem when trying to install an early version of (I think it was) Mageia.  I forget what the resolution was now, but I think it had been corrected with a subsequent release.  I haven't used this box in some time, but it appears to run fine, overall, and the problem may be innate to that particular model/chipset.

I have some other boards here I could use, but they are new and I'd prefer to save those for my other machines as their hardware needs replacement.   I run some older generation, Athlon II and FX8350 amd3 platform kit.  Since the market for those is kind of long past, it is becoming increasingly harder to find replacement parts... at reasonable prices.  I have been slowly stockpiling older parts as I find them.  I know that I will eventually have to upgrade to more recent generation hardware, but I like using what I already have for the time being.

I might just be running into the problems of using older hardware, but I'm not sure.   I am hoping someone knows of a kernel patch or some additional options I can try.  So far, I have tried passing pci=nomsi, acpi=off, noapic, and combinations thereof with the msi quirk message and hang still occurring.

#4 Re: Devuan Derivatives » xfce4 icons missing in starlinux derivative » 2020-12-26 19:50:34

Mark this one solved?  The problem was that there were no icon themes installed.   

I installed gnome-icon-theme (and a couple others like Tango) and now it works fine.   Hope this helps others running into the same issue.  Also hope that future releases of Star Linux will include gnome-icon-theme as a dependency of gnome-like desktops.

#5 Devuan Derivatives » xfce4 icons missing in starlinux derivative » 2020-12-26 19:05:41

Replies: 3

I did a brand new install of xfce4 on star linux 3.0.0 (spock).   (64bit version.)  After install completed, as root I installed xfce4 via the meta package.  However, not everything got installed that way, so I went back and did a "apt install xfce4-*" which did install numerous additional packages.  I have installed lightdm and configured it for auto login of my regular user I created during install.

When the desktop came up for the first time, it was prompted to create the desktop and selected the default panel configuration.   But after this, the desktop was missing most of the icons.  The desktop actually does work.  I tried logging out and back in, rebooting etc.  No change.  I also tried creating another regular user, but that created the same desktop without all the icons.

When I go to Settings->Appearance and select the Icons tab, there are no choices; the desktop themes tab is fine and has many to choose from.

I did DDG search (on different system) on "xfce4 missing icons" and found there were quite a few hits -- I tried some of them (which varied greatly, btw) but to no avail.  The #devuan IRC folks helped me a bit, but suggested I post here.  We tried a few things, including making sure the icon theme was set to Adwaita.

The only "customization" I did during install (for which I used the expert mode) was the disk and file system configuration.  I'm using LVM and have an encrypted /home.   The /home and /var and /usr partitions are on separate partitions.   Not sure any of this has any impact, but I wanted to be upfront about deviations from typical installation procedures in case there might be any issues.

Board footer

Forum Software