You are not logged in.
Success!
I used the devuan_daedalus_5.0.1_amd64_netinstall.iso to install onto this 5 year old HP laptop. It boots fine and I thank each of you for your input.
Andre4freedom, thank you for that list above. It is exactly what I did and it worked. Now I am good to go with a fairly modern laptop.
Thanks again guys!
-niXer
Thanks guys, I appreciate this information. I will never understand this UEFI think unless I actually use and experience it. So, I need to continue trying and learning. I will follow up on this and let you know how it goes, after I read it a few times ... (-;
I am thinking that instead of trying and forcing the legacy BIOS and MBR thing, I just may try and use the intended UEFI install without the secure boot option and see how that goes. I will follow up on this when I have something to report... like success, hopefully.
Thank you both for your suggestions.
first thing that comes to mind is, ensure the boot partition has the "boot" flag
The /boot partition 1gb, is formatted ext2, and the boot flag is active.
Try using grub install from the live disk
I did this as one of my efforts to work around this issue, but not from the live disk. I ran "grub-install /dev/nvme0n1" while booted with the aid of supergrub. This command installed grub to the beginning of the drive. Should I have installed it to the /boot partition instead? For over 19+ years of using linux, I have always installed grub to the drive and not a partition. Does efi change this behavior?
I was recently gifted a HP 15 dy-1023 laptop computer with 4-cores and 12gb ram and and I am not having any success with a working grub install. Any idea or help is appreciated.
I have updated the laptop BIOS to the latest version and the BIOS settings shows that Legacy Mode is "enabled" which disables the "secure boot" option. The Legacy Boot options are listed in the BIOS. But the BIOS also says that the UEFI options will be a higher precedent. After making these changes, the MBR USB flash drive was recognized and the live drive booted. I immediately wiped the old proprietary system, created a new legacy msdos MBR on the drive and created the /root and /swap partitions. The live install completed normally. I used refracta-tools to build the snapshot and installed from a daedalus legacy mbr install (no gpt drive or UEFI, thus a regular grub install).
The only way that I can get this install to boot is to use supergrub boot disk.
My troubleshooting is mostly trial and error, after researching the need for EFI installs using extra partitions like a 1mb unformatted partition if using a gpt drive on a legacy system, a /efi (fat32) partition, and a /boot (ext2) partition. I have tried the install using both options together and individually using legacy grub and grub-efi-amd64 but I still get the same HP error upon booting. The error is this:
Boot Device Not Found
Please Install an Operating System
Hard Disk - (3FO)
I think this is a hardware and/or grub install issue since it will boot using supergrub.
Final note... everything that deals with U(EFI) in the BIOS is supposedly disabled, and the hard drive has a msdos master boot record. But the install does have /sys/firmware/efi folder and it is populated with some files and folders , which leads me to believe that it is actually trying to use efi. Is this correct? If so, this may be part of the problem. I read some posts on a different linux forum board about HP laptops not actually having true legacy bios functions but a simulated ability, which makes me confused. Just mentioning this as a possible consideration.
I like legacy technology and I have fought this GPT and UEFI thing as long as I can. My question is, what do I need to do to successfully get this thing to boot into Devuan? If I have to start over and reinstall, no problem.
To repeat myself,
you may want to replace the deb.devuan.org name with the actual name of one of the actual mirror repositories
I did this because I started having some dns resolving issues on my home network. It "probably" has something to do with me using the "unbound" dns resolver package instead of the default DNS from my internet service provider. I am pleased with this result but after changing the repo line in my sources.list file to an actual repo location, my apt updates has worked flawless.
THE most sensible set of rules for any forum I have ever seen just about perfection.
+1
I would try it again later. One of the round-robin dns locations may not be online for some reason.
If this happens more often, you may want to replace the deb.devuan.org name with the actual name of one of the actual mirror repositories.
https://pkgmaster.devuan.org/mirror_list.txt
Too get this latest version of if this will not cause problems ?
I would not do that. I would use the current version shown for the chimaera release. Generally speaking, you should not mix "newer" versions of a program unless they were found in the "backports" section of that release cycle. Even this could be considered for more advanced users. I would use the version of wireguard for chimaera, as shown in my first post above. It works fine and it installs and configures the same way.
I have some links to the tutorials that I used to configure wireguard, but there are many guides that can be found on the internet.
I have wireguard installed on chimaera. Only "wireguard" and "wireguard-tools" are installed:
root@localhost:/home/user# apt policy wireguard*
wireguard-dkms:
Installed: (none)
Candidate: 1.0.20210219-1
Version table:
1.0.20210219-1 500
500 http://gnlug.org/pub/devuan/merged chimaera/main amd64 Packages
wireguard-tools:
Installed: 1.0.20210223-1
Candidate: 1.0.20210223-1
Version table:
*** 1.0.20210223-1 500
500 http://gnlug.org/pub/devuan/merged chimaera/main amd64 Packages
100 /var/lib/dpkg/status
wireguard-modules:
Installed: (none)
Candidate: (none)
Version table:
wireguard:
Installed: 1.0.20210223-1
Candidate: 1.0.20210223-1
Version table:
*** 1.0.20210223-1 500
500 http://gnlug.org/pub/devuan/merged chimaera/main amd64 Packages
100 /var/lib/dpkg/status
I "think" I installed it with
apt install wireguard
Wireguard works fine. There are many good tutorials on the web about setting up the keys after installing.
I think the wireguard-dkms and wireguard-modules packages are for the older packages that were before wireguard was included in the kernel.
This is interesting. My first try using on devuan was not a failure, but it was not a success either. It had to do with the configuration of the script especially with the excludes_list part of my host system that caused me to bail out of this attempt. I will try again.
However, I successfully tested the creation of a snapshot on a Void system on a virtual machine, successfully. As a matter of fact, I am posting this from within the live system running in a virtual machine now.
The first thing that I noticed in the alpha-utilz.sh script is that there is a scrolling and selection error on the screen where options are highlighted and selected. The scrolling will change the selected option, which is confusing.
I have come this far, so I may as well try the void-install, soon. I am mainly interested in using this for other systems. For Devuan, the default refracta-tools are hard to improve upon, in my opinion.
Thank you for this alphalpha.
Ok, I have the program loading now. It did not automatically create the folder /home/snapshot , and this caused the problem. After manually creating the folder, it works.
The only file that was created in the /.config/alpha-utilz folder was "snapshot.conf". No log was created. I guess the failure was before the point of log creation.
I have something to use now. Thank you.
This looks very interesting, especially if it can work on hyperbola, void, and artix.
I tried to run the script on my devuan and void machines and I got the same reply from each on the terminal:
Error: function check_chown needs exactly two argumenrs.
Any quick instructions on how to use it? I did not see anything on the gitlab project site.
As for dependencies, I have refracta-tools installed so its dependencies are installed as well. Are there any other dependencies required?
This was tried on my devuan unstable (ceres) install.
Just a rambling thought here... wanted to make sure you knew about sysv-rc-conf.
in the absence of a program to enable/disable startup services
Maybe I am misinterpreting what you are trying to do, but have you used sysv-rc-conf ?
apt install sysv-rc-conf
And then as root from the terminal:
sysv-rc-conf
It will handle the "update-rc.d" commands for you before making the final.iso build, and it certainly is not a hard program to master in order to restart the services later on. Maybe make a small script to start the program in a terminal so that others can toggle the start/stop of the services at boot? It is a handy little program that I have used many, many times in years past.
Hope this helps.
I created a init script /init.d/....
with
sysctl -w net.ipv6.conf.default.disable_ipv6=1
sysctl -w net.ipv6.conf.all.disable_ipv6=1
I don't think that would do much, but I would simply add the two lines to the /etc/sysctl.conf file and then test it out. Be sure to run "sysctl -p" after saving the file.
If you wanted to run the lines of code at boot, you might want to try adding them to the /etc/rc.local file, but I think the /etc/sysctl.conf file would be better.
This is what I use to enable ipv6 in /etc/sysctl.conf . This enables both ipv6 and ipv4
net.ipv6.bindv6only= 0
This would disable ipv6:
net.ipv6.bindv6only=1
Also,
I did a quick web search and this was a top reply. I forgot to save the link, sorry.
How to disable IPv6 with Sysctl?
Open the /etc/sysctl.conf file with the following command:
$ sudo nano /etc/sysctl.conf
Add the following lines to it:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
Reload. sysctl.conf. with the following command:
sysctl -p
I think that one, or both, of these methods should work.
Sometimes you run across something that really does open your eyes and makes you appreciate what you have - for example, Devuan.
Yesterday I ran across a mailing list post from 2010 from Lennert Pottering. It really opened my eyes regarding his consideration of linux and his purpose for systemd. I now have a better understanding why non-systemd systems were created and do still exist. I really do not want to fan the flames of fire towards systemd. Everyone reading this has probably already read enough about this. It is well documented and preserved. However, this entire post is short and I did extract the worst of it, but I added nothing. It is what it is.
I really have to wonder why and what is the purpose of such benevolence towards others and their creations?
Coersion ?
...it is definitely our intention to gently push the distributions in the same direction so that they stop supporting deviating solutions ...
Consideration?
... our plan is to enable all this by default ... we want to put the burden on the packagers, so that eventually we end up with the same base system on all distributions, ...
Conquering?
If a distro decides ... then it's their own job to disable ours and plug in their own instead. Sooner or later they'll hopefully notice that it's not worth it and cross-distro unification is worth more.
I have a new appreciation on what Devuan is and what it stands for.
I have been using Devuan since before it even had an installer. In the earliest days it has a bootstrap method of "installation" which, while not elegant, it worked.
To those that create and develop Devuan, congratulations on being available to the public for over 10 years now. My heartfelt "thank you" goes out to everyone who has worked to make it what it is today.
The entire post is found at https://lists.freedesktop.org/archives/ … 00391.html
Debian had a point release update on the 31st of August. It affected both chimaera and daedalus. I had about 50 updates on my desktop system(s).
if it so, why this important thing not mentioned in the rsync manual at first place?
That I do not know. I have moved/archived/copied installs this way for several years now. When using only devuan to copy or rsync an install this was never an issue, so I never used the "--numeric-ids" in my rsync command. However, once I used a different operating system, this became an issue. So I tried it on the recommendation in the Void forums, and it worked. I used devuan to rsync a different linux OS, and "--numeric-ids" worked.
It is mentioned in the rsync man file:
man rsync
--numeric-ids don't map uid/gid values by user/group name
As a suggestion, I mentioned adding the "--numeric-ids" option. It seems that by default rsync will sync user information as user:group and not UID:GID, which can cause some permissions issues. The "--numeric-ids" will change this behavior. The user and group name will still copy over but this seems to fix any issued caused by a different operating system handling the rsync data. Sorry for not being too technical but a search request reveals this:
--numeric-ids With this option rsync will transfer numeric group and user IDs rather than using user and group names and mapping them at both ends. By default rsync will use the username and groupname to determine what ownership to give files.
Hey, I tried it and it worked. So, I thought I would mention it as it sounds like you are having similar issues.
i did
home:[freeartist-artix]:~$ sudo rsync -aXHx --info=progress2 /mnt/Dev1/ /mnt/Dev2/
Allow me to ask, what operating system did you use to copy the source partition to the destination partition? Devuan or another?
I do rsync copying pretty often and I recently had a situation where I had to add "--numeric-ids" to the rsync command. This was because there was a different operating system involved in the mix, not just devuan. In this instance I used devuan to host a Void virtual machine and I copied the virtual machine onto a locally mounted partition. Essentially, I moved a VM onto a physical partition. It worked fine after the fstab file was altered with the new UUID's, grub reinstalled, and the initramfs was rebuilt.
The actual command used that worked for me, from a VM to a locally mounted partition:
rsync -aHAXv --numeric-ids --exclude={"/dev/*","/proc/*","/sys/*","/run/*","/media/*","/mnt/*","/lost+found"} /* root@10.0.0.1:/media/User/Void/ --delete
Hope this helps.
What error message? What repository? Was it actually a devuan repo or one of the debian round robin dns repos accessed with deb.devuan.org?
There have been some information about similar issues but I have had no problems at all with the devuan repos. Sometimes I do have a problem with one of the debian repos accessed with the round robin dns name. It may be slow, time out, etc. When it does this, I just try again later.
When you are trying to update, you will see the server name that you are trying to download from mentioned. Similar issues have been noted by others. You might want to search this forum board and/or the mailing list.
For google-earth,
https://www.google.com/intl/en/earth/versions/
For librewolf, don't know about Otter
https://librewolf.net/installation/debian/
As for the synaptic file for installed packages, a web search is your friend as I know it can be done. But, I have never done it, yet.
For the video card issue, I suggest to download the video drivers needed before changing the cards, then install after the hardware change. If after changing the hardware the X desktop does not come up, you may have to boot into recovery mode to install the drivers. This is what I have done on several occasions.
It runs fine for me on ceres (unstable). I also have it installed on excalibur (testing), and daedalus (stable). It is installed with apt with the brave repository active. But note, I have not booted into the stable and testing install in a while so I don't know if it runs, but it installs and updates without error.
pcalvert,
Were you able to do anything regarding alpine linux? I looked at the packages involved and it is the "live-boot and live-config" packages that are missing and I don't know what could be used to replace their function - if this is possible.
The refracta-tools scripts have spoiled me.
Yes, it is the version that I updated to that broke my second profile. I removed that version and installed the previous version and my second profile works as expected.
The version that works correctly is
125.0.6422.60-1 500
500 http://deb.devuan.org/merged excalibur/main amd64 Packages