You are not logged in.
Pages: 1
I realized that it might sound as if I am questioning the need for separate Devuan packages. It is not the case. I am asking for specific reason.
I am also using Slackware. We have standard .tgz packages and we also often use Slackbuilds. Slackbuilds are similar to BSD ports. Most of the time, those are scripts which build the package from source code, supplying appropriate parameters to configure and make.
Sometimes, when the package is large, requiring hours to build from source, Slackbuild may rely on packages from other distributions. When it is possible. Those foreign packages are almost always coming from Debian repositories. Brave browser is a good example. In those cases, the script unpacks the original package and repacks it into Slackware standard .tgz format.
Standard Slackware packages do not keep track on dependencies, but normal installation contains reasonable selection of basic libraries, which makes it work most of the time.
So, I am guessing, if it was possible to create a Slackware package from Debian, Devuan package should be even easier.
I am sorry for being ignorant, but what makes Devuan package different from Debian ? Is it some sort of signature ? I mean, both a build from same sources and with same packaging tools. The naming convention seem the same, too.
Also, is there a specific tools which can repackage Debian into Devuan ?
How does one use that banned list, exactly ? Where can one read more about it ?
Forgive my ignorance, but what it takes to repackage for Devuan ? Most Debian packages work. I have a Debian repository added with very low priority, so that Devuan packages are favored. For purpose of installing whatever is not in Devuan repository. I suppose that packages depending on Systemd and similar needs to be developed separately, but majority should work.
I am new to Devuan, but used Debian for years at work previously. Before Systemd. So, I might be wrong about this.
I have installed firmware-intel-sound and it resolved the issue completely. Addition to rc.local is not needed any more.
I have considered this for a while, but my audio chip was not listed among those supported, so I hesitated. I did it anyway in the end and it worked.
I guess it all happened because I installed from minimal 1 CD media.
dd if=/dev/zero of=RAW_DEVICE bs=1M count=1
This might be faster if the device is large. It should be enough to wipe out the partition table and let you start new.
Far as I understand, ms-sys is MBR related. Are Windows 10 capable of being installed on MBR partitioned disk ? I don't know because I never went beyond Win7.
As for other problem, as previous poster said, try adding the repository to sources list. Also check the:
apt-cache policy
to see if there might be some pinning/priority related problem. Don't forget to run apt update after adding the repository to sources.list
Do you happen to have any extensions installed. Also you my try running Firefox from terminal, like this:
firefox > out.txt 2>&1
Firefox outputs quite a lot. When it freezes, wait a bit. The output might be buffered, so give it a minute. You might examine out.txt while firefox is still running and also after you stop it.
I am not sure I understood it correctly. You said that USB media worked properly previously. Previous to what ? What exactly did you do to make it work improperly ?
Also, what are you trying to do ? Are you trying to wipe off everything on the media and start fresh ? Or are you trying to write something on one of the partitions, while leaving others intact ?
Have you tried cfdisk or fdisk? Do you have any other OS installed on the same machine to try partitioning tools?
I have noticed that there are othe posts realated to the sound issues. However, I am not sure if mine is related to any of the.
In fact there were two problems. The quirky one was about a pin on the hardware interface, related to speakers, not being activated.The problem is solved with help of ChatGPT, and, to be honest, I don't really understand how and why it works,because it is very much hardware related. The sound device I am using is:
Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)It is Realtek chip, far as I can understand. Rather common sound hardware. It works fine with Slackware on the other partition. The solution which worked was to add the following to /etc/rc.local I have modified the script a bit
(
SDEV="/dev/snd/hwC0D0"
sleep 5
if [ -e $SDEV ]
then
hda-verb $SDEV 0x15 SET_PIN_WIDGET_CONTROL 0x40
else
echo "$DEV not found"
fi
alsactl restore
) & 'hda-verb' line is the key. I wish I understand the problem better, but I don't. I hope it might help somebody else with similar issue. Also, I should say that Excalibur was installed from single 'server' CD image (around 650M).Perhaps the installation from some larger image solves the problem somehow.
The second problem is trivial compared to the first one. I have two sound device on the system. The other is HDMI device in the NVIDIA card. It works with speakers attached to the monitor, which I don't have. So I blacklisted the device :
blacklist snd_hda_codec_hdmiAlso the initrd needs to be updated with update-initramfs. This second issue might be trivial, but till someone might lose hours getting around it.
Either way, the sound works now.
I am back on Devuan. Reainstalled the OS, problem persists. However, I've tried boot with "advanced/recovery" option from GRUB menu. My problem might actually be with sound.
NVidia card has sound chip on board. (a monitor has no built-in loudspeakers)
Motherboard has another (REALTEK) chip.
Judging by recovery boot screen output, NVidia sound chip gets initialized first. Then REALTEK gets initialized, too. After that boot hangs.
I also tried boot in text mode console. BTW, that is the way Slackware boots, to run level 3. It is up to user to log in and execute startx. If they feel like running a graphical desktop, I mean. That is why Slackware is Slackware, never assume anything about the users. If I wanted to compare operating systems to the rifles, Slackware would be AK-47.
In order to that, I disabled lightdm at run level 2. The machine does not boot any more. It happens regardless of nouveau, it might be blacklisted or not.
I can always recover from installation media, but that's not the point. Why can't I do simple and straightforward thing like booting into text mode ?
As part of my little research of Debian based distributions, I have installed PeppermintOS, version based on Devuan 5. Nouveau driver is installed and works without a problem. I have high resolution and good performance. It is definitely curios.
Distribution is very professionally done and so much polished that makes one feel guilty to tinker about it
. So, next week I am going to reinstall Devuan and see if I can get graphics to work properly.
Thanks, I am going to try that. I tried MX Linux, which is based on Debian Bookworm. Latter corresponds to Devuan Daedalus, if I am not mistaken. Nouveau worked without problem. I think I have got, at least, some acceleration. Most video players and browsers use acceleration today, and I watched some videos without visible performance penalty.
I am, kind of, exploring "Debian landscape", lately
. Debian distros without Systemd. Peppermint OS is next on my list, version based on Devuan.
I have an older PC with NVidia GT 1030 card. I am running Slackware 15 and Windows on the same machine. Recently installed Devuan 5 64 bit on empty partition and setup multi-boot.
There seems to be a problem with nouveau driver. System starts and I am getting lightdm prompt. However, resolution is limited to 1024x768. Also, I am unable to switch to virtual consoles (like Alt+Ctrl+F2). There is a blank screen with cursor when I try that. Also noticed that during booting the screen output stops after line "Waiting udevd to be populated".
Blacklisting nouveau solved the problem with consoles and I am now seeing all of the output during boot. However, I am still limited to 1024x768.
So I tried proprietary driver. The problem is that installer can't find kernel source. I installed linux-source and linux-headers- amd64-[version], where [version] was kernel version as reported by uname -r. No dice.
I must say that I am not a Debian man, but rather a Slackware man. I do have some experience maintaining existing Debian server on my previous job, but nothing like hardware or multimedia. Also, far as I can say, non-free repositories are enabled, but NVidia drive does not show.
So, I am trying to get familiar with Devuan. I'd like to know both, if there is a way to fix nouveau and what do I need to compile proprietary driver. Thanks.
Pages: 1