You are not logged in.
Hi
You can choose soundcard in alsamixer by pressing F6. To adjust volume make sure "Master" is selected (or headphone if you are using that) and then arrow up(down to adjust.
It looks like jack soundserver and pulseaudio is running. If jack is running (and as a musician I am using it myself when needed) please stop the daemon (maybe through qJackĆtl or commandline). Jack prevents other servers (as alsa) to use the soundcard. Just use jack for recording and mixing sound at a (semi) professional level. It does not work by default on games and in browsers. Pulseaudio also makes the setup more complicated than it need to be. Edit /home/user/.config/pulse/client.conf and set autospawn = no. Then it will not restart by iself when you stop it. Log out and in. If needed stop pulseausio by passing pulseaudio -k in a terminal. Using just alsa is the simplest way to get audio as an ordinary user on Devuan.
Hope this helps
Lars H
Hi,
Well, F6 does not show any other sound devices. The only thing jack related installed is libjack-jackd2, and I don't see any jack server process running. I got rid of pulseaudio altogether. Sound works, the mixers/volume controls/multiple audio apps all work - just not in stereo. In Debian buster, which is configured almost identically, it's stereo, and the output device is shown as Built-in Audio Analog Stereo. I just can't figure out what Devuan is doing differently...
Thanks for your input - somewhere in all this is a clue...
Can we see
lspci -knn | grep -A2 Audio aplay -Ll
But of course!
$ lspci -knn | grep -A2 Audio
00:1f.3 Audio device [0403]: Intel Corporation 200 Series PCH HD Audio [8086:a2f0]
Subsystem: Hewlett-Packard Company 200 Series PCH HD Audio [103c:82f2]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
$ aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
jack
JACK Audio Connection Kit
pulse
PulseAudio Sound Server
default:CARD=PCH
HDA Intel PCH, ALC891 Analog
Default Audio Device
sysdefault:CARD=PCH
HDA Intel PCH, ALC891 Analog
Default Audio Device
front:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
Front speakers
surround21:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=PCH,DEV=0
HDA Intel PCH, HDMI 0
HDMI Audio Output
hdmi:CARD=PCH,DEV=1
HDA Intel PCH, HDMI 1
HDMI Audio Output
hdmi:CARD=PCH,DEV=2
HDA Intel PCH, HDMI 2
HDMI Audio Output
hdmi:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 3
HDMI Audio Output
hdmi:CARD=PCH,DEV=4
HDA Intel PCH, HDMI 4
HDMI Audio Output
dmix:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
Direct sample mixing device
dmix:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample mixing device
dmix:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample mixing device
dmix:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample mixing device
dmix:CARD=PCH,DEV=9
HDA Intel PCH, HDMI 3
Direct sample mixing device
dmix:CARD=PCH,DEV=10
HDA Intel PCH, HDMI 4
Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
Direct sample snooping device
dsnoop:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct sample snooping device
dsnoop:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct sample snooping device
dsnoop:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct sample snooping device
dsnoop:CARD=PCH,DEV=9
HDA Intel PCH, HDMI 3
Direct sample snooping device
dsnoop:CARD=PCH,DEV=10
HDA Intel PCH, HDMI 4
Direct sample snooping device
hw:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
Direct hardware device without any conversions
hw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Direct hardware device without any conversions
hw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Direct hardware device without any conversions
hw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Direct hardware device without any conversions
hw:CARD=PCH,DEV=9
HDA Intel PCH, HDMI 3
Direct hardware device without any conversions
hw:CARD=PCH,DEV=10
HDA Intel PCH, HDMI 4
Direct hardware device without any conversions
plughw:CARD=PCH,DEV=0
HDA Intel PCH, ALC891 Analog
Hardware device with all software conversions
plughw:CARD=PCH,DEV=3
HDA Intel PCH, HDMI 0
Hardware device with all software conversions
plughw:CARD=PCH,DEV=7
HDA Intel PCH, HDMI 1
Hardware device with all software conversions
plughw:CARD=PCH,DEV=8
HDA Intel PCH, HDMI 2
Hardware device with all software conversions
plughw:CARD=PCH,DEV=9
HDA Intel PCH, HDMI 3
Hardware device with all software conversions
plughw:CARD=PCH,DEV=10
HDA Intel PCH, HDMI 4
Hardware device with all software conversions
usbstream:CARD=PCH
HDA Intel PCH
USB Stream Output
And as I indicated above, alsamixer shows
Card: HDA Intel PCH
Chip: Realtek ALC891
also in alsamixer, you may be able to set the default device. hth
I see no option to do so. It reports:
Card: HDA Intel PCH
Chip: Realtek ALC891
Hi
First try from commandline with alsamixer. If you get sound alsa is working (and this is just fine. Pulseaudio is just an unnecessary layer). Then install volumeicon-alsa. It is gtk based and can replace the pulseaudio based frontend on your system. Can be placed on the menuline as well.
Have a nice day
Lars H
I have sound - just not stereo. Alsamixer doesn't seem to offer any other options.
You know, I've been thinking (ouch!). It seems to me that Devuan, while still a relatively small project, is attracting more and more new people all the time, and many of them are perhaps unclear as to what Devuan is. In fact, some people seem to assume that Devuan is the answer to their personal Hopes and Dreams or something. A Rorschach test, as it were.
When I first encountered Devuan years ago, it seemed pretty clear: it was a project to create and maintain a systemd-free Debian. That's really all I wanted - pretty straightforward. But as the time went on, and I spent time on the forum and IRC, it became clear that different folks were forming rather different ideas as to what was the point of Devuan. There seems to be a contingent that feels that Devuan is/ought to be a super-minimalist system, and those who feel that it should be 'libre' to the max. Etc., etc.
Then come the SJW types. Devuan's association with Dyne I think might have contributed to this...
Dyne seems to be a very 'socially conscious' outfit (for lack of a better term). There is definitely a SJW vibe there, and some of the statements made by Jaromil and others strengthen that impression. Sometimes at the expense of the technology, such as the time Jaromil said that he didn't care if the repos were down for months at a time so long as the workers felt mellow and unstressed and fulfilled (or something - I don't remember the exact words). Now, as admirable as that might be, some folks/shops might not be real comfortable with that sentiment.
But others resonate with that, and next thing you know, you have folks like silver2 coming on trying to remake the IRC channel to his liking, appearing most thoughtful and gentle, and then flouncing off in a bitter cloud of invective when he receives pushback. To me, his proposals sounded like control-freakery, but whatever.
Me, all I ever wanted was a systemd-free Debian. That's really the point of Devuan, right?
I think that perhaps the rules could be made more obvious up front, but I see no reason for the sweeping changes you put forward. There is the tech support channel, and there's the the debian-fork channel for other matters. I for one do not want to to see the tech support channel bogged down with OT stuff and personal chit-chat, especially when an issue being actively worked. It is noise.
"The scope of on topic discussion should be broadened to explicitly include what users of devuan are doing with devuan even if they are not requesting support."
Strongly disagree. Maybe a third channel could be instituted for that. Or go to Dev1Galaxy. IMO it is underutilized.
I think having too many fiddly procedures and templates and whatnot is premature at this point. It can get pretty draconian pretty fast if you're not careful. Next thing you know you have some ridiculous CoC.
In any case, 'first offenses' are noted fairly gently. The main offenses, really, are hogging the channel for social chit-chat, reminiscing about the good old days, or rants. It is a tech support channel, and needs to stay on topic. I've never seen anyone tossed off mysteriously or for 'political' reasons. Usually, golinux says 'come on, that's not a support issue, take it to debian-fork'. She often gives several warnings. No problem. When a dialog drifts off topic, it seems to usually happen gradually, which requires a flexibility of response. I don't think we need templates and such.
I have been using beowulf/MATE for quite some time now, and have almost zero issues with it. But I do have one thing:
The sound output as shown in the 'Sound' app under 'Sound & Video' in the MATE menu shows as 'HD Intel PCH mono'. That is the only output device shown. In buster/MATE, it shows as 'Built-in analog stereo sound' (something close to that - going by memory here). This is also how it showed up in ascii/MATE.
This issue is present whether it's a clean install of beowulf or and upgrade from ascii, and whether I use pulseaudio or apulse. I would like to improve my sound quality, so if anyone has any ideas as to how I might fix this, I'm all ears :-)
TIA...
OK, I think I see what is going on. It works, but I didn't understand what it does. I thought it was actually supposed to turn down the 'red' part of all colors in the display. It's just dimming the display slightly. So what I want to do is really eliminate the blue light from anything I run on my desktop. Submarine-style "rig for night running" mode.
Is there a way to do that? Or will each program have to be individually configured to only use red colors? I suppose there is an all-red theme for XFCE, or one can be created. But the other programs might be more of a challenge.
It does turn down the color temperature, not just dim the display. I don't know what the problem is on your system, but I've never had any trouble with it.
When I install Redshift (and redshift-gtk) on a new system, I just run redshift-gtk once from the command line or alt-F2. I get the little icon on the top panel (I use MATE) that has enable/suspend/autostart/info/quit.
Autostart seems to be selected by default, and has always worked for me. Tweak redshift.conf in ~/.config to suit your tastes.
I've been using Beowulf full-time since January, and on and off for much longer than that. For the parts of the system that I use on a regular (or even occasional) basis, it has proven itself rock solid. I use the MATE DE, fwiw.
Well, the volume indicator issue was easily solved. - mate-volume-control-applet, contained in mate-media pkg. It was actually installed already - I just had to run the command once, and it was setup in startup programs after that. How strange...
Anyway, I did a netinstall, and it went very smoothly. No problem with grub, or sources.list, or anything.
Well, the beowulf installation I've been using for many months has one, my debian buster installation has one, my ubuntu 20.04 installation has one, plus another different one available in 'add to panel', so I don't know about that. In any case, I'd like to have one :-) We'll see how it shakes out...
OK, I copied in a dconf backup that I had from another install, and it got MATE to present properly. However, I notice there is no volume indicator on the top panel as usual, nor is there one available for adding.
Also, the sources.list had the entry for the install media uncommented, and did not have stanzas for the basic repos. Once I fixed that, apt worked fine.
I had to install grub-efi-amd64* in order to be able to grub-install and update-grub, but once I did, it worked fine.
So now I have a fully functioning beowulf/MATE (except the volume indicator). It was a bit more fiddly than perhaps it ought to be, but everything seems fine now.
I will try netinstall when I get a chance.
Another data point.
I installed using the Desktop DVD. Chose the MATE desktop. Installation seemed to go smoothly until the end, when it was unable to install grub. I just went ahead and finished up, since I had another install to boot from.
Upon booting into the new system, MATE was broken - the top and bottom panels were there, but completely unpopulated by any applets or what have you. I tried rebooting, but same thing.
I will do some troubleshooting a bit later. I think I might try the netinstall, too.
Did you really have to post that nonsense?
Just trying to brighten up your day! :-)
Get a load of this:
Head_on_a_Stick wrote:This is starting to ring a bell with me about an old fdn thread that p.H handled and subsequently opened a bug report about. I'll see if I can find it again...
Ha! found it: http://forums.debian.net/viewtopic.php? … 09&start=0
Bug report: https://bugs.debian.org/cgi-bin/bugrepo … bug=925309
So try copying /boot/efi/EFI/devuan to /boot/efi/EFI/debian
EDIT: or perhaps use
# grub-install --target=x86_64-efi --bootloader-id=debian
Thanks for tracking that down! I have just skimmed it for now, but there is a LOT of UEFI/grub lore in there. I will peruse it tomorrow with fresh eyes - my eyes just don't work very well at the end of the day...
sgage wrote:If you think it would help, I will post the output of bootinfoscript
No, let's leave it for now. I think it's aimed more at non-UEFI systems anyway.
sgage wrote:the problem seems to lie with grubx64.efi...
Indeed. This is starting to ring a bell with me about an old fdn thread that p.H handled and subsequently opened a bug report about. I'll see if I can find it again...
Yes, I took bootinfoscript for a spin, and it did seem to be geared for legacy type systems.
I'd be interested in knowing if others have encountered this. I have a workaround for now, but it's something that ought to get fixed...
Thanks for your help - really appreciate it!
sgage wrote:what is telling grub where to get its menu from?
I think the information is embedded in grubx64.efi
It may be time to unleash /usr/sbin/bootinfoscript — the output will be lengthy so perhaps use https://paste.debian.net/
Before I release the Kraken, I mean, unleash bootinfoscript, here's an interesting observation:
I saved an image of my beowulf install with dd, then restored an image of ascii to p6. It had been on p5, so I used grub-install to fix up the EFI/devuan directory. It indeed generated a new grubx64.efi, and did not touch grub.cfg. And it booted using the grub.cfg in ascii, at p6. So, I copied that grubx64.efi to a safe place, restored beowulf. It booted using beowulf's grub.cfg! Since, presumably, the /devuan/grubx64.efi points now to p6.
I ran grub-install, rebooted, and sure enough, it booted using the grub.cfg from p5 (a buster installation). I copied the grubx64.efi that I had saved back over to /devuan, and behold, it booted using grub.cfg from p6.
It seems to me that beowulf's grub-install is not generating a proper grubx64.efi. Does no one else have this issue?
If you think it would help, I will post the output of bootinfoscript, but the problem seems to lie with grubx64.efi...
How very strange
Is the EFI system partition definitely mounted under /boot/efi?
lsblk -f
Try changing /boot/efi/EFI/devuan/grub.cfg to this:
search.fs_uuid 9685be15-8423-402b-b734-f92844748a90 root hd0,gpt6 set prefix=($root)'/boot/grub' configfile $prefix/grub.cfg
I'm booting via $ESP/EFI/BOOT/bootx64.efi using GRUB but there is no grub.cfg in $ESP/EFI/BOOT/ so I'm not sure if that's actually needed.
Yes, EFI definitely mounted at /boot/efi.
Your grub change didn't change anything. I also tried
configfile (hd0,gpt6)/boot/grub/grub.cfg
that I got from an old script I had kicking around.
I am starting to believe that the grub.cfg in the EFI/(distro) isn't really being used. But then what is telling grub where to get its menu from? Yes, very strange...
sgage wrote:It seems that beowulf's grub does not parse the grub.cfg file in /boot/efi/EFI/devuan
Can we see the content of that file please.
sgage wrote:reinstalled grub to create a new one
How did you do that, exactly?
And can we please see the output of
# parted --list efibootmgr -v /sbin/blkid
The boot-info-script package (/usr/sbin/bootinfoscript) will show exactly what's going on but I can't be bothered trawling through the wall-of-output so give me a few posts to work it out for myself first. Thanks.
The grub.cfg generated in the /devuan directory is:
search.fs_uuid 9685be15-8423-402b-b734-f92844748a90 root
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg
It is the correct UUID for the beowulf partition.
I created the /devuan directory in EFI/ the way I have been for a couple of years now:
sudo grub-install --recheck --no-floppy --force
parted --list gives:
Number Start End Size File system Name Flags
1 1049kB 274MB 273MB fat32 EFI System Partition boot, esp
2 274MB 290MB 16.8MB Microsoft reserved partition msftres
3 290MB 275GB 275GB ntfs msftdata
4 275GB 344GB 68.7GB ntfs msftdata
5 344GB 370GB 25.8GB ext4
6 370GB 395GB 25.8GB ext4
efibootmgr -v gives:
# efibootmgr -v
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0005,0007,0000,0008,0002,000A,0003,0009,0004,0006,000B,000C
Boot0000* Windows Boot Manager HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...a................
Boot0001* devuan HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\DEVUAN\SHIMX64.EFI)
Boot0002* USB Floppy/CD VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0500000001)..BO
Boot0003* USB Hard Drive VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0200000001)..BO
Boot0004* ATAPI CD-ROM Drive VenMedia(b6fef66f-1495-4584-a836-3492d1984a8d,0300000001)..BO
Boot0005* debian HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\DEBIAN\SHIMX64.EFI)
Boot0006 UEFI:CD/DVD Drive BBS(129,,0x0)
Boot0007* ubuntu HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0008* debian HD(1,GPT,ba36c9c3-856c-4a3a-bf6b-a0aaa7decb7e,0x800,0x82000)/File(\EFI\DEBIAN\GRUBX64.EFI)
Boot0009* UEFI: SanDisk PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/HD(1,MBR,0x3bf4ec9f,0x390944,0x1f00)..BO
Boot000A* UEFI: SanDisk PciRoot(0x0)/Pci(0x14,0x0)/USB(5,0)/CDROM(1,0x390944,0x7c00)..BO
Boot000B UEFI:Removable Device BBS(130,,0x0)
Boot000C UEFI:Network Device BBS(131,,0x0)
Thanks for having a look...
I am experiencing a strange issue with grub in beowulf. It seems that beowulf's grub does not parse the grub.cfg file in /boot/efi/EFI/devuan, which is supposed to point to the grub.cfg in the /boot/grub partition of the beowulf root partition, and instead uses the /boot/grub/grub.cfg found in the first ext4 partition it encounters.
I have deleted /boot/efi/EFI/devuan and reinstalled grub to create a new one. I am definitely booting from /devuan - I bring up the BIOS boot menu and select 'devuan'.
Update-grub indeed generates the intended grub.cfg in the beowulf /boot/grub - if I copy it to /boot/grub of the first ext4 partition, grub comes up with the beowulf boot menu, in all of its cinnabar glory.
I am booting off of an nvme SSD drive, for what that's worth. nvme0n1p1 is the EFI partition, followed by some ntfs partitions. The first ext4 partition is p5 (currently buster), and beowulf is on p6.
I do a fair amount of experimentation with distros, and this is the first time I've encountered this. It's been going on for some weeks now.
What gives?
Still 4 polkit-related packages being held back as of today...
aut0exec wrote:Even saw some Dells the other day where CSM isn't an option within the firmware!
Yeah, Intel are planning to remove it completely: https://www.anandtech.com/show/12068/in … fi-by-2020
Bastards...
Is this still the timeline for eliminating CSM? (The article was written in 2017.)
Head_on_a_Stick wrote:basati wrote:The group of developers has to have an idea of where things are going
I can't speak for the developers but fsmithred has just released the first beowulf beta for Refracta so the release is approaching.
Yup. As soon as we get the installer isos right, we'll let you play with them. Meanwhile, I switched my main box to beowulf. (Bye bye Jessie. I'm sorry it didn't work out as we first expected, but I had nothing to do with that. I kept you as pure as I could.)
My main box would be beowulf if I could install wine32. Other than that. beowulf works beautifully on my machine.
[edit: Ack! I just checked, and I was able to install wine32! So I can run the one program that I need to run in wine. Ironically, wine (64-bit) won't install because of a few held back packages. I'm sure it will get sorted, but I don't need it anyway. My main box is now beowulf!]