1. The shutdown works not completely. The system is shut down, but the machine (an Intel NUC) is still alive and the light are on. ASCII however did always a perfect job and shuts the machine totally down.
2. When looking for updates with sysnaptics it checks the packages and then give me a note with:
"Fehlschlag beim Holen von http://deb/devuan.org/merged/dists/beowulf/InRelease »deb« konnte nicht aufgelöst werden.Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt."
The sources.list does not contain above entry and I have no idea, where sysnaptics found this.
Any hints for me?
Regards
Berni
Hi
It is in backports. "apt install -t beowulf-backports linux-image-amd64" should do the trick
Have a nice day
Lars H
Thanks for that direction on kernel location and backports.
Uname -r now shows me 5.5.0-0.bpo.2-amd64.
And it works like a champ. Better than the 4.9.0-11-amd64 version I was running.
Thanks..
]]>OMG someone pushed it to master! And there are things that still need to be done there!!
]]>rolfie
]]>It is in backports. "apt install -t beowulf-backports linux-image-amd64" should do the trick
Have a nice day
Lars H
great . happy for that.
Now you say i should try kernel 5. how do i do that. is it simple like purging a kernel or is it more involved?
also where do i get it?
And by the was Beowulf looks and runs really well, so far.
]]>For very new hardware, it may be an useful option to add backports to the sources.list and to install the 5.5 kernel from there.
rolfie
]]>You should simply uninstall the old kernel with apt purge linux-image-4.19.0-9-amd64. But be carefull !!! I do not have an 4.19.0.11. I only have 4.19.0.9. So be sure. If you remove the running kernel the system will crash and you cannot reboot (this is called linux for a reason ;-).
Have a nice day
Lars H
What I did was I used apt-get dist-upgrade, and I ended up with Beowulf, from ASCII.
At boot time now I have the choice of booting with 4.19.0.09. Which is my first choice. That one doesnt boot which has the same problem that I have had all along.
The second choice 4.19.0.11 works like a champ. I nearly fell down when it came up just fine.
So now I would like to know how I get edit out that first choice - 4.19.0.09. So when things boot up automaticaly it will pick a kernel that works.
So how can I edit out that first line on the boot-screen,
]]>If you let the installer do the partitioning, it should give you what you need. (Note: the live installer doesn't do any partitioning for you. Only the installer isos do that.)
]]>Well - lets see if this works. I was using both the Live CD and the netinst units. So this time its the full shot. All files should be there. and all things should work..
I will let you guys know. And by the way I am going to install Beowulf this time under a UEFI bios. See if that makes any difference rather than under legacy bios.
-----------------------
Sorry to hear of all your difficulties - this shouldn't be happening.
From your latest report you now seem to be getting stuck at an earlier stage than you did before. Previously it seemed to be a problem with the Nouveau video driver, which LarsH is now reported wont work with your new NVIDIA GPU and has suggested a fix to get you to a console.
FWIW I've now installed Beowulf on two different AMD-64 PCs, one Intel and the other AMD (with NVIDIA graphics) and did not have the particular problems you are now reporting, though to be fair my components are not cutting edge like yours. One of these was an entirely new install and the other was alongside an existing ascii installation.
1) I've always gone for legacy bios. Worked both times. My older motherboard has EFI but not UEFI. With the newer one I had choice in the the BIOS.
2) I've never actually installed from the live ISO, just used to check that I could boot into Beowulf (and get the WiFi working). The live install (if that is what you are using) is designed to be straightforward and therefore pretty unbreakable for a straightforward one-disk install but I'm not aware of exactly what choices it makes for you.
3) if you are using one of the other installers they can get more complicated and there is greater scope to be confused.
However:
3) You don't have to install /boot on a separate partition. It may be a bit more robust to do so if you have more than OS installed or your disk config is complex. On one of of mine I choose to keep it separate/simple because my root and /home partition are mounted as RAID1, on the other because they are LVM.
4) The boot partition doesn't have to be formatted DOS or even EXT2. Both mine are EXT4.
5) The installers themselves haven't changed between ASCII and Beowulf. I note that other users have been finding some bugs in the isos, particularly if burnt to optical CD/DVD, rather than USB, which the developers are fixing, but these are mostly pretty minor.
6) As you're getting inconsistent results it may be worth confirming (if you haven't already done so) that you isos have not got corrupted.
CSM = traditional BIOS support can be enabled, then the boot disk should be MSDOS partitioned. When you boot the CD don't use the entry that says UEFI before the drives name.
Though I would recommend to use UEFI. Set the drive settings to UEFI driver first or similar, and disable CSM. Secure Boot to Other OS. The boot drive needs to be GPT partitioned. Boot the install CD with the UEFI label before the drives name.
If these dependencies are observed, it should be possible to easily install Beowulf, may be at first with a wired LAN connection to avoid any issues with wifi.
rolfie
]]>From your latest report you now seem to be getting stuck at an earlier stage than you did before. Previously it seemed to be a problem with the Nouveau video driver, which LarsH is now reported wont work with your new NVIDIA GPU and has suggested a fix to get you to a console.
FWIW I've now installed Beowulf on two different AMD-64 PCs, one Intel and the other AMD (with NVIDIA graphics) and did not have the particular problems you are now reporting, though to be fair my components are not cutting edge like yours. One of these was an entirely new install and the other was alongside an existing ascii installation.
1) I've always gone for legacy bios. Worked both times. My older motherboard has EFI but not UEFI. With the newer one I had choice in the the BIOS.
2) I've never actually installed from the live ISO, just used to check that I could boot into Beowulf (and get the WiFi working). The live install (if that is what you are using) is designed to be straightforward and therefore pretty unbreakable for a straightforward one-disk install but I'm not aware of exactly what choices it makes for you.
3) if you are using one of the other installers they can get more complicated and there is greater scope to be confused.
However:
3) You don't have to install /boot on a separate partition. It may be a bit more robust to do so if you have more than OS installed or your disk config is complex. On one of of mine I choose to keep it separate/simple because my root and /home partition are mounted as RAID1, on the other because they are LVM.
4) The boot partition doesn't have to be formatted DOS or even EXT2. Both mine are EXT4.
5) The installers themselves haven't changed between ASCII and Beowulf. I note that other users have been finding some bugs in the isos, particularly if burnt to optical CD/DVD, rather than USB, which the developers are fixing, but these are mostly pretty minor.
6) As you're getting inconsistent results it may be worth confirming (if you haven't already done so) that you isos have not got corrupted.
]]>