You are not logged in.
Congratulations to the good people who maintain Devuan. With just a little trepidation I did my upgrade on one machine which was using 917 packages. The whole upgrade process took less than an hour, and all that I had to deal with was the usual questions about keeping modified configuration files. It seems as if everything works properly ... except the graphics, but that is an Nvidea problem, and both my X11 log and the email report on the installation give explicit instructions on how to handle the problem. I have had a lot more fallout from distribution upgrades in the past.
As regards graphics, oddly I am in a no-man's-land as I have a new machine that will not work without the 4.19.0 kernel, and my older ones which are having trouble with Nvidea and the Beowulf upgrade. It keeps me busy, and confined to the house, which is not a bad idea these days.
Offline
I am trying another test install, this time using ASCII as host.
I've used ASCII debootstrap, specified beowulf as suite.
Now I'm trying to update-grub from the chroot, and I'm getting the dreaded
/dev/sdX not initialized after 100000000000 microseconds message.
UPDATE: message does not seem to go away even after waiting for about 15 minutes.
UPDATE2: message goes away but takes a very long time.
Running grub-mkconfig took about an hour.
Last edited by dev-1-dash-1 (2020-04-03 11:37:11)
Offline
I am trying another test install, this time using ASCII as host.
I've used ASCII debootstrap, specified beowulf as suite.
Now I'm trying to update-grub from the chroot, and I'm getting the dreaded
/dev/sdX not initialized after 100000000000 microseconds message.UPDATE: message does not seem to go away even after waiting for about 15 minutes.
UPDATE2: message goes away but takes a very long time.
Running grub-mkconfig took about an hour.
Before entering the chroot:
mkdir chroot-dir/run/udev
mount --bind /run/udev chroot-dir/run/udev
That will get rid of the repeated warnings on update-grub.
Offline
dev-1-dash-1 wrote:I am trying another test install, this time using ASCII as host.
I've used ASCII debootstrap, specified beowulf as suite.
Now I'm trying to update-grub from the chroot, and I'm getting the dreaded
/dev/sdX not initialized after 100000000000 microseconds message.UPDATE: message does not seem to go away even after waiting for about 15 minutes.
UPDATE2: message goes away but takes a very long time.
Running grub-mkconfig took about an hour.Before entering the chroot:
mkdir chroot-dir/run/udev mount --bind /run/udev chroot-dir/run/udev
That will get rid of the repeated warnings on update-grub.
Great, straight on target!
That worked for the chroot.
I have debootstrapped another test system now, but when I boot it these messages still appear in the "starting lvm volume groups phase." Ctrl-c makes it go away, boot seems to proceed normally.
I am now having trouble getting the wireless network interface to come up. eth0 is there, but no wireless in sight. I am rebooting into an ascii system to look up for clues on the internet.
UPDATE:
Another test install completed.
Some feedback:
1)Kernel modules for my wifi card didn't load automatically, although they are present right there in the linux-image package.
Had to load them manually, than add them to /etc/modules to trigger their autoload at boot time.
2)Message udevd[672]: specified group 'kvm' unknown appears during boot time.
3)Sometimes the message about 'dev/sda not present in udev database' still appears during 'starting lvm' phase, ctrl+c gets rid of it.
4) Of course, after installing nvidia proprietary drivers (nvidia-legacy-...) system changed resolution and froze, had to do hard reset that boot into single user mode and finish config from there. Hello nvidia!
On the plus side, I've set up lvm, crypt, and zfs root and was able to boot successfully.
EDIT: Removed some complaints which turned out to be due to my misconfiguration rather than beowulf bugs.
Last edited by dev-1-dash-1 (2020-04-08 07:41:57)
Offline
hello ,
please don't forget to include pvr-iptvsimple for kodi *missing*
thank you!
Offline
please don't forget to include pvr-iptvsimple for kodi *missing*
It appears to be in ascii and ceres. Looks like that omission comes directly from debian as we have not forked that package. Have you checked backports?
Offline
Have you checked backports?
Thanks, how can i add backports?
E: Release file for http://deb.devuan.org/merged/dists/beowulf-backports/InRelease is not valid yet (invalid for another 9min 49s). Updates for this repository will not be applied.
E: Release file for http://it.deb.devuan.org/merged/dists/beowulf-updates/InRelease is not valid yet (invalid for another 9min 52s). Updates for this repository will not be applied.
deb http://deb.devuan.org/merged beowulf-backports main
deb-src http://deb.devuan.org/merged beowulf-backports main
Last edited by kapqa (2020-04-06 16:24:26)
Offline
Yes, That is correct. Was the package you were looking for there?
This is a useful page for sources.list information.
Offline
Something is a bit strange about beowulf backports or maybe more like the package search? I looked on my fileserver running Beowulf for about a year now. beowulf-backports are present, apt lists packages like linux-image-5.4.
When I use the https://pkginfo.devuan.org/cgi-bin/d1pk … se=beowulf to search for linux-image-5* that are present in backports, I get:
26 results for "linux-image-5*" in beowulf (in 7.427974ms)
[beowulf] linux-image-4.19.0-8-amd64-4.19.98-1
[beowulf] linux-image-4.19.0-8-amd64-dbg-4.19.98-1
[beowulf] linux-image-4.19.0-8-amd64-unsigned-4.19.98-1
[beowulf] linux-image-4.19.0-8-cloud-amd64-4.19.98-1
[beowulf] linux-image-4.19.0-8-cloud-amd64-dbg-4.19.98-1
[beowulf] linux-image-4.19.0-8-cloud-amd64-unsigned-4.19.98-1
[beowulf] linux-image-4.19.0-8-rt-amd64-4.19.98-1
[beowulf] linux-image-4.19.0-8-rt-amd64-dbg-4.19.98-1
[beowulf] linux-image-4.19.0-8-rt-amd64-unsigned-4.19.98-1
[beowulf] linux-image-amd64-4.19+105+deb10u3
[beowulf] linux-image-amd64-dbg-4.19+105+deb10u3
[beowulf] linux-image-amd64-signed-template-4.19.98-1
[beowulf] linux-image-cloud-amd64-4.19+105+deb10u3
[beowulf] linux-image-cloud-amd64-dbg-4.19+105+deb10u3
[beowulf] linux-image-rt-amd64-4.19+105+deb10u3
[beowulf] linux-image-rt-amd64-dbg-4.19+105+deb10u3
[beowulf-security] linux-image-4.19.0-6-amd64-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-amd64-dbg-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-amd64-unsigned-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-cloud-amd64-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-cloud-amd64-dbg-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-cloud-amd64-unsigned-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-rt-amd64-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-rt-amd64-dbg-4.19.67-2+deb10u2
[beowulf-security] linux-image-4.19.0-6-rt-amd64-unsigned-4.19.67-2+deb10u2
[beowulf-security] linux-image-amd64-signed-template-4.19.67-2+deb10u2
Whats wrong there?
rolfie
Offline
I think that may be a buster=stable beowulf=testing glitch and that things will normalize when we are also "stable" release.
Offline
I installed XFCE4 and lightdm. On the welcome screen, where you need to enter a username and password, the buttons for shutting down and rebooting are inactive at the top right. How to make them active? Maybe I missed something from the installation packages?
Offline
Look at this old thread: https://dev1galaxy.org/viewtopic.php?id=2023
rolfie
Offline
Yes, That is correct. Was the package you were looking for there?
This is a useful page for sources.list information.
Still getting error
E: The value 'beowulf-backports' is invalid for APT::Default-Release as such a release is not available in the sources
Maybe the error is related to the !Italian! sources.list?
Would be this package
https://packages.debian.org/search?keyw … iptvsimple
i still could include it via Deb-Multimedia, but those packages are built against Debian, so it would be a double-risk, but most of the time it is quite a good solution. Still it would be nice to find the package in Beowulf.
Noticed that on Ascii it is included, and on Beowulf it seems only few Kodi-addons avaiable.
Thank you.
Offline
Look at this old thread: https://dev1galaxy.org/viewtopic.php?id=2023
rolfie
It works. thx!
Offline
i still could include it via Deb-Multimedia, but those packages are built against Debian, so it would be a double-risk, but most of the time it is quite a good solution.
I think golinux said somewhere on this forum that devuan is 98% pure debian. That means using packages built against a corresponding debian release is 98% likely to work, on average. Unless you get packages which are heavily systemd related.
If it doesn't work, you can always blame golinux for lulling you into a false sense of security with the 98/2 statistics. (jk) :-)
I use oss4 packages from deb-multimedia on ascii system and they fit perfectly.
Offline
Still getting error
E: The value 'beowulf-backports' is invalid for APT::Default-Release as such a release is not available in the sources
Maybe the error is related to the !Italian! sources.list?
Take a close read of https://devuan.org/get-devuan, paragraph Package repositories and https://dev1galaxy.org/viewtopic.php?id=3276. Country codes are deprecated.
A simple deb http://deb.devuan.org/merged beowulf-backports main (contrib non-free) should do the job.
rolfie
Offline
I installed XFCE4 and lightdm. On the welcome screen, where you need to enter a username and password, the buttons for shutting down and rebooting are inactive at the top right. How to make them active? Maybe I missed something from the installation packages?
Here's the fix for lightdm power buttons that we're currently recommending. This will be in the final version of the release notes.
Power buttons are disabled in lightdm login screen with elogind.
(See Debian bug #932047)
Add the following line to /etc/pam.d/lightdm-greeter
session optional pam_elogind.so
Offline
I think golinux said somewhere on this forum that devuan is 98% pure debian. That means using packages built against a corresponding debian release is 98% likely to work, on average. Unless you get packages which are heavily systemd related.
Not exactly . . .
This from https://beta.devuan.org/os/packages :
Devuan package repositories are exclusive. Other repositories, including Debian, Ubuntu, Mint etc, should NOT be used directly.
If it doesn't work, you can always blame golinux for lulling you into a false sense of security with the 98/2 statistics. (jk) :-)
Your interpretation of what constitutes a Debian repository could lead to a Frankendevuan! FWIW, debmultimedia has always been a risky adventure. If you decide to go there check the package carefully and remember that you added a non-native package when the devuan version arrives.
Offline
dev-1-dash-1 wrote:I think golinux said somewhere on this forum that devuan is 98% pure debian. That means using packages built against a corresponding debian release is 98% likely to work, on average. Unless you get packages which are heavily systemd related.
Not exactly . . .
Well, I was quoting this thread, post 6
http://dev1galaxy.org/viewtopic.php?pid=20943#p20943
It is true that you did not say that there's a 98% probability of packages from external repos working correctly, that is something which I said, and I take the blame for bad advice if someone misreads the post. :-)
This from https://beta.devuan.org/os/packages :
Devuan package repositories are exclusive. Other repositories, including Debian, Ubuntu, Mint etc, should NOT be used directly.
I have not advocated adding repositories from other distributions and replacing devuan packages with alien ones.
Perhaps it is worth repeating for less experienced readers of this thread, that of course adding other distibutions repositories will likely lead to trouble, and should never be done.
Your interpretation of what constitutes a Debian repository could lead to a Frankendevuan!
I have stated before on this forum that I am EXTREMELY careful about adding other repos, even from different versions of Devuan itself, and I've repeated this point yet again in the previous paragraph of this post.
You are correct to bring attention to the point of never, ever adding sources from other distributions which may replace official Devuan packages. This is usually unnecessary and harmful. This point can not be overstated.
FWIW, debmultimedia has always been a risky adventure. If you decide to go there check the package carefully and remember that you added a non-native package when the devuan version arrives.
In this particular instance I've been talking about my experience of adding oss4 packages from deb-multimedia, which are, unfortunately, NOT provided AT ALL by Debian/Devuan in releases after jessie. Otherwise I would have to compile them myself, either using Ubuntu sources or adding patches manually, which is A LOT more trouble for nothing.
Hope that clears it up.
Last edited by dev-1-dash-1 (2020-04-08 18:39:00)
Offline
Also, since we are getting so strict and pedantic about our sources.list, which IS the right approach if we want a stable system to actually be stable.
I've read many times on this form that preferred way to access the official repositories is using
deb.devuan.org
in our sources.list. And it's been that way for some time already.
Why, then, my recently installed copy of beowulf contains
http://pkgmaster.devuan.org/merged
in file
/etc/apt/sources.list
???
Installation was performed by using debootstrap.
Offline
golinux wrote:This from https://beta.devuan.org/os/packages :
Devuan package repositories are exclusive. Other repositories, including Debian, Ubuntu, Mint etc, should NOT be used directly.You are correct to bring attention to the point of never, ever adding sources from other distributions which may replace official Devuan packages. This is usually unnecessary and harmful. This point can not be overstated.
Exactly. It needs to be stated over and over.
Hope that clears it up.
Mostly this discussion is about semantics which in documentation is more important than you might think.
Offline
Why, then, my recently installed copy of beowulf contains
http://pkgmaster.devuan.org/merged
in file
/etc/apt/sources.list
???
Installation was performed by using debootstrap.
What URL did you use in the debootstrap command? I just tried it using deb.devuan.org, and that's what shows up in sources.list.
Oh! I just tried it again without giving debootstrap any URL, and it hits pkgmaster.devuan.org. That makes perfect sense - that is the main repo that gets copied to all the mirrors. We ask people to use deb.devuan.org so that the load gets spread out over all the mirrors.
Offline
Mostly this discussion is about semantics which in documentation is more important than you might think.
Not exactly . . . I never said I thought semantics in documentation aren't important. :-)
What URL did you use in the debootstrap command? I just tried it using deb.devuan.org, and that's what shows up in sources.list.
I use debootstrap without URL parameters. I am operating under the assumption that it knows what it's doing.
Oh! I just tried it again without giving debootstrap any URL, and it hits pkgmaster.devuan.org. That makes perfect sense - that is the main repo that gets copied to all the mirrors. We ask people to use deb.devuan.org so that the load gets spread out over all the mirrors.
I read it like this: if my installer writes pkgmaster.devuan.org, it's a good idea to change it to deb.devuan.org to help spread out the load.
Why not make the deb.devuan.org the default? Just a thought.
Offline
Did you try the Get Devuan page?
Do ya need the apt-transport-https package?
I just updated -- all work -- even the ones using tor
miyoisomix.i2p
Offline
Why not make the deb.devuan.org the default? Just a thought.
It already is in a "normal" installation:
https://beta.devuan.org/os/packages
Offline