On 23/07/2024 19:20, Thomas Schmitt wrote:
A bit off-topic question. In what wiki page you would expect to find
suggestions to inspect ~/.xsession-errors file and journalctl output?
I pasted ".xsession-errors" into the "Search:" field at the upper right
corner of any Debian wiki page and clicke
On Tue, Jul 23, 2024 at 14:20:43 +0200, Thomas Schmitt wrote:
> The only helpful match is
>
>
> https://wiki.debian.org/JigdoOnLive?action=fullsearch&context=180&value=.xsession-errors&fullsearch=Text
>
> "What Does The Log Say?
>...
>If you're doing something with your window manage
Hi,
Max Nikulin wrote:
> A bit off-topic question. In what wiki page you would expect to find
> suggestions to inspect ~/.xsession-errors file and journalctl output?
I pasted ".xsession-errors" into the "Search:" field at the upper right
corner of any Debian wiki page and clicked the "Text" butto
Max Nikulin wrote:
> On 23/07/2024 04:09, Thomas Schmitt wrote:
>>$ cat ~/.xsession-errors
> [...]
>>[fvwm][executeModule]: <> No such module 'FvwmConsole' in
>> ModulePath '/usr/lib/fvwm/2.6.8'
>
> A bit off-topic question. In what wiki page you would expect to find
> suggestions to insp
On 23/07/2024 04:09, Thomas Schmitt wrote:
$ cat ~/.xsession-errors
[...]
[fvwm][executeModule]: <> No such module 'FvwmConsole' in ModulePath
'/usr/lib/fvwm/2.6.8'
A bit off-topic question. In what wiki page you would expect to find
suggestions to inspect ~/.xsession-errors file and
Hi,
i wrote:
> > Four of five fingers point to me and my ~/.fvwm2rc":
> > ModulePath /usr/lib/fvwm/2.6.8
Greg Wooledge wrote:
> Why do you even have that line at all?
Cargo cult.
Once it was needed, then i carried it on, and finally i forgot about it.
The reason why i did not notice two years
On Mon, Jul 22, 2024 at 23:09:59 +0200, Thomas Schmitt wrote:
> Four of five fingers point to me and my ~/.fvwm2rc":
>
> ModulePath /usr/lib/fvwm/2.6.8
>
> I see traces that i adjusted this multiple times over the years:
> /usr/lib/X11/fvwm2 , /usr/lib/fvwm/2.6.5 , /usr/lib/fvwm/2.6.8.
>
> So
Hi,
(i begin to owe Greg Wooledge half a sysadmin salary and half one for a
geriatric nurse)
Greg Wooledge wrote:
> Error messages, if there are any, should be in ~/.xsession-errors
$ cat ~/.xsession-errors
Cannot parse color "dtcolor5"
couldn't create gradient
Cannot parse color "dtcolo
On Mon, Jul 22, 2024 at 21:37:05 +0200, Thomas Schmitt wrote:
> So how could i debug the start of fvwm Modules ?
> Is there any log file or configuration option ?
Error messages, if there are any, should be in ~/.xsession-errors for
most users. I'd start there.
Hi,
after the striking success with my previous vim problem, i want to
tackle another nuisance of the 11-to-12 upgrade.
The window manager fvwm2 does not start the Modules and does not produce
the Buttons which are prescribed by my ~/.fvwm2rc . I am direly missing
FvwmPager for my 8x2 multi
On Thu, 22 Feb 2024 21:13:46 +0500
Евгений Гостьков wrote:
> Can you add http_async_client.so to deb package
> `kamailio-extra-modules` or maybe make distinct deb package like a
> `kamailio-http-async-client` ?
Have you checked with kamailio support resources (mail lists, web
sites,
Package: kamailio-extra-modules
Version: 5.6.3-2
Information for package
https://packages.debian.org/bookworm/kamailio-extra-modules say about
kamailio module `http_async_client`
But the package doesn't install them.
https://packages.debian.org/bookworm/amd64/kamailio-extra-modules/fil
Hello everyone,
I am trying to follow the Debian's wiki about Secure Boot:
https://wiki.debian.org/SecureBoot
I've been able to carry out most of this one, from generating modules to
enrolling in the MOK cert, but it doesn't work the signing of the modules
as per the steps.
The
> the volume occupied by /usr/lib/modules/ (3.5GB) &
> /usr/lib/x86_64-linux-gnu (1.4GB) - as far as I can tell, this latter
> directory only has essential, current files. I have been using this
> volume for over a year, & the modules directory now has over a
> dozen kernels fr
This message is related to the 'Re: solution to / full' thread.
I am running my computer from a Debian 11.6 OS on a 25GB partition on
a USB stick. The root partition is now 70% full, with over 4GB (16%) of
the volume occupied by /usr/lib/modules/ (3.5GB) &
/usr/lib/x86_64-linux-gn
>
> Debian:
> Non-Volatile memory controller
> ASPM Disabled
> Kernel driver in use: nvme
>
> PCI bridge: Intel Corp 12th Gen
> ASPM Disabled
> Kernel driver in use: pcieport
>
> So the exact same driver is been used and I didn't find any config within
> /
Disabled
Kernel driver in use: pcieport
So the exact same driver is been used and I didn't find any config within /etc/
modprobe.d or /etc/modules or /etc/modules-load.d with respect to these
modules.
Do you have an idea why this happens (same computer, so BIOS settings should
have no impact)?
Than
heck kmod.c in kernel sources. If I create a file modprobe.fake [1]
and modify /proc/sys/kernel/modprobe to call this file, a standard
Debian shows the same behaviour than my Chromebook: If fat/vfat
modules are not loaded and I try to mount some fat filesystem
afterwards this fails with the same
functionality is missing.
Check kmod.c in kernel sources. If I create a file modprobe.fake [1] and
modify /proc/sys/kernel/modprobe to call this file, a standard Debian
shows the same behaviour than my Chromebook: If fat/vfat modules are not
loaded and I try to mount some fat filesystem afterwards this
x27;t work as no vfat module gets loaded (as
an example).
Likewise adding rules via iptables doesn't work, as the netfilter
modules are missing. I have to manually load the nf* modules and _then_
I'm able to use iptables.
I can load all those modules by hand via modprobe, but au
On Sat, 16 Jul 2022 at 23:41, Brian wrote:
> But you did not download and try the one I suggested? Therefore, you
> are working blindfolded. It is dated 2022-0 7-05. The archive modules
> may match the d-i kernel.
I successfully installed Sid using the Bullseye mini.iso that I
downlo
gested? Therefore, you
are working blindfolded. It is dated 2022-0 7-05. The archive modules
may match the d-i kernel.
> which is supposed to be the one to install Sid. The one you ask about
> seems to be not for Sid. There is another method of installation which
You are misunderstanding; all
/dev, and so on).
On BusyBox I ran 'uname -a' and it told me I am running the debian-sid
kernel 5.10.0-8, built on 2021-07-28. This might be the reason for the
error message I got, "No kernel modules found". It is a very old
kernel. So perhaps the mini.iso was not built in a long whi
On Sat, 16 Jul 2022 at 19:26, Charles Curley
wrote:
> Look in the installation logs for suspicious messages. During
> installation, they are at /target/var/log/installer/. After you reboot
> into the newly installed system, they are at /var/log/installer/.
I chose "Execute Shell", got a window w
On Sat, 16 Jul 2022 at 19:49, Brian wrote:
>
> On Sat 16 Jul 2022 at 18:27:29 +0100, Piscium wrote:
> > [1] https://wiki.debian.org/DebianUnstable
> > [2] deb.debian.org
>
> Is the mini.iso at
>
>
> http://ftp.nl.debian.org/debian/dists/bullseye/main/installer-amd64/current/images/netboot/
>
>
h all the various
> options without any error, network configuration also succeeded, then
> at the step "Download installer components" I got the error "No kernel
> modules found". The mirror is the default and recommended [2].
>
> Any ideas? Could it be that the
On Sat, 16 Jul 2022 18:27:29 +0100
Piscium wrote:
> … network configuration also succeeded, then
> at the step "Download installer components" I got the error "No kernel
> modules found". The mirror is the default and recommended [2].
>
> Any ideas? Cou
ed, then
at the step "Download installer components" I got the error "No kernel
modules found". The mirror is the default and recommended [2].
Any ideas? Could it be that the specified ISO got somehow out of sync
with what is available in the default mirror?
[1] h
On Fri, Jun 17, 2022 at 12:45 AM Keith Bainbridge wrote:
>
>
> On 17/6/22 00:08, Boyan Penkov wrote:
> > On Thu, Jun 16, 2022 at 12:09 AM Keith Bainbridge
> > wrote:
> >>> Cheers!
> >>
> >> Good afternoon Boyan
> >>
> >> What happened when you installed to 2 suggested items?
> > Hey Keith -- yes
On 17/6/22 00:08, Boyan Penkov wrote:
On Thu, Jun 16, 2022 at 12:09 AM Keith Bainbridge wrote:
Cheers!
Good afternoon Boyan
What happened when you installed to 2 suggested items?
Hey Keith -- yes, thanks for the pointer; you're absolutely correct...
Somehow linux-image-headers was not ins
headers, most likely linux-headers-amd64.
You will not be able to start VMs until this problem is fixed.
```
Modprobing for vboxdrv returns no modules.
Has anybody seen this with more recent virtualbox installs?
Cheers!
Good afternoon Boyan
What happened when you installed to 2
.
You will not be able to start VMs until this problem is fixed.
```
Modprobing for vboxdrv returns no modules.
Has anybody seen this with more recent virtualbox installs?
Cheers!
--
Boyan Penkov
On Mon 14 Feb 2022 at 10:54:21 (+0100), basti wrote:
> Hello,
>
> I try to use a USB Serial-Converter to output the grub menu on a
> Serial port.
>
> By the way the output is working at kernel boot time. (I See it on the
> remote host)
>
> How can I add usbserial_pl2303.mod to the GRUB core imag
Hello,
I try to use a USB Serial-Converter to output the grub menu on a Serial
port.
By the way the output is working at kernel boot time. (I See it on the
remote host)
How can I add usbserial_pl2303.mod to the GRUB core image?
The file is located in /boot/grub/i386-pc/ on the root partiti
On Sun 04 Jul 2021 at 23:53:15 -0500, David Wright wrote:
> On Sun 04 Jul 2021 at 21:12:10 (+0100), Brian wrote:
> > On Sun 04 Jul 2021 at 20:16:25 +0100, Brad Rogers wrote:
> > > On Sun, 4 Jul 2021 19:42:26 +0100 Brian wrote:
> > > >I did specify "as time goes on". Suppose one boots successfully
On Sun 04 Jul 2021 at 21:12:10 (+0100), Brian wrote:
> On Sun 04 Jul 2021 at 20:16:25 +0100, Brad Rogers wrote:
> > On Sun, 4 Jul 2021 19:42:26 +0100 Brian wrote:
> > >I did specify "as time goes on". Suppose one boots successfully a 100
> > >times with the new kernel. What need is there for a seco
On Sun 04 Jul 2021 at 20:16:25 +0100, Brad Rogers wrote:
> On Sun, 4 Jul 2021 19:42:26 +0100
> Brian wrote:
>
> Hello Brian,
>
> >I did specify "as time goes on". Suppose one boots successfully a 100
> >times with the new kernel. What need is there for a second kernel on
> >the system?
>
> Cle
On Sun, 4 Jul 2021 19:42:26 +0100
Brian wrote:
Hello Brian,
>I did specify "as time goes on". Suppose one boots successfully a 100
>times with the new kernel. What need is there for a second kernel on
>the system?
Clearly, you haven't understood what Tixy wrote.
--
Regards _
/ )
On Sun 04 Jul 2021 at 13:45:00 +0100, Tixy wrote:
> On Sun, 2021-07-04 at 10:08 +0100, Brian wrote:
> > On Sat 03 Jul 2021 at 20:49:01 -0600, Tom Dial wrote:
> >
> > >
> > >
> > > On 7/3/21 13:04, Brian wrote:
> > > > On Sat 03 Jul 2021 at 18:49:35 +0100, mick crane wrote:
> > > >
> > > > [...
On Sat 03 Jul 2021 at 14:20:28 (-0400), Stefan Monnier wrote:
> The only thing with `MODULES=dep` is that it runs a slightly higher risk
> of ending up with an unbootable system after a hardware or
> filesystem/LVM/MD/partition change.
Alternatively, use a little forethought and rebui
On Sun, 2021-07-04 at 10:08 +0100, Brian wrote:
> On Sat 03 Jul 2021 at 20:49:01 -0600, Tom Dial wrote:
>
> >
> >
> > On 7/3/21 13:04, Brian wrote:
> > > On Sat 03 Jul 2021 at 18:49:35 +0100, mick crane wrote:
> > >
> > > [...]
> > >
> > > > Can I not *just* move the older ones out of the way
On Sat 03 Jul 2021 at 20:49:01 -0600, Tom Dial wrote:
>
>
> On 7/3/21 13:04, Brian wrote:
> > On Sat 03 Jul 2021 at 18:49:35 +0100, mick crane wrote:
> >
> > [...]
> >
> >> Can I not *just* move the older ones out of the way so upgrade doesn't run
> >> out of space ?
> >
> > Why bother?
> >
On 7/3/21 13:04, Brian wrote:
> On Sat 03 Jul 2021 at 18:49:35 +0100, mick crane wrote:
>
> [...]
>
>> Can I not *just* move the older ones out of the way so upgrade doesn't run
>> out of space ?
>
> Why bother?
>
> apt purge linux...
>
> Why do you need two kernels anyway?
I rather havi
> The only thing with `MODULES=dep` is that it runs a slightly higher risk
> of ending up with an unbootable system after a hardware or
> filesystem/LVM/MD/partition change. Just make sure you have some way to
> do a "rescue boot" in those cases (typically via a USB flash k
ile system is simply too small if you
> plan to keep more than 2 kernels at a time.
Not at all. Just adjust the /etc/initramfs-tools/initramfs.conf with
MODULES=dep
COMPRESS=lzma
and you'll have room for many more kernels.
> One thing I'll note is that your initrd* file
On Sat 03 Jul 2021 at 18:49:35 +0100, mick crane wrote:
[...]
> Can I not *just* move the older ones out of the way so upgrade doesn't run
> out of space ?
Why bother?
apt purge linux...
Why do you need two kernels anyway?
Next time - don't have a separate boot partition. You will be happie
cklist those modules to prevent them from being
auto-loaded. Serves the same purpose without needing to manually build
update Kernels.
S°
--
Sigmentation fault. Core dumped.
On Sat, Jul 03, 2021 at 06:49:35PM +0100, mick crane wrote:
> root@pumpkin:/boot# df -h /boot
> Filesystem Size Used Avail Use% Mounted on
> /dev/sdb1 236M 159M 65M 71% /boot
This is the real issue. This file system is simply too small if you
plan to keep more than 2 kernels at a
Am Samstag, 3. Juli 2021, 19:01:02 CEST schrieb IL Ka:
Hi all,
> I was thinking then to remove the unwanted modules to make the kernels
>
> > smaller.
>
Some years ago I tested a few things.
I built a monolithic kernel with all the modules statically built in, as I
knew all m
On 2021-07-03 18:12, Greg Wooledge wrote:
On Sat, Jul 03, 2021 at 05:50:44PM +0100, mick crane wrote:
I did think that modules are for the kernel to interact with hardware.
There is for example "dell_smm_hwmon" followed "0" which you'd think
was to
be used by softw
On 2021-07-03 at 13:28, mick crane wrote:
> On 2021-07-03 18:03, The Wanderer wrote:
>
>>> I looked because "apt upgrade" failed to install things in /boot
>>> because no room left. I deleted the oldest kernel stuff of the 3
>>> there and "apt upgrade" worked.
>>
>> I hope you removed them by
On 2021-07-03 at 13:28, mick crane wrote:
> On 2021-07-03 18:03, The Wanderer wrote:
>
>>> I looked because "apt upgrade" failed to install things in /boot
>>> because no room left. I deleted the oldest kernel stuff of the 3
>>> there and "apt upgrade" worked.
>>
>> I hope you removed them by
On Sat 03 Jul 2021 at 17:50:44 (+0100), mick crane wrote:
> On 2021-07-03 17:29, The Wanderer wrote:
> > On 2021-07-03 at 12:06, mick crane wrote:
> >
> > > hello,
> > > If I type "lsmod" there is a big list of modules with many
> > > followed b
On 2021-07-03 18:03, The Wanderer wrote:
I looked because "apt upgrade" failed to install things in /boot
because no room left. I deleted the oldest kernel stuff of the 3
there and "apt upgrade" worked.
I hope you removed them by uninstalling their kernel packages, not by
just deleting the fil
On Sat, Jul 03, 2021 at 05:50:44PM +0100, mick crane wrote:
> I did think that modules are for the kernel to interact with hardware.
> There is for example "dell_smm_hwmon" followed "0" which you'd think was to
> be used by software for monitoring the PC hardwar
uz-5.10.0-0.bpo.7-amd64
6.5M/boot/vmlinuz-5.10.0-0.bpo.7-amd64
Modules are here:
$ du -sxh /lib/modules/5.10.0-0.bpo.7-amd64/
290M/lib/modules/5.10.0-0.bpo.7-amd64/
You must mean initrd, which contains selected kernel modules and is used
in the boot process:
$ du -sxh /boot/initrd.
On 2021-07-03 at 12:50, mick crane wrote:
> I did think that modules are for the kernel to interact with
> hardware. There is for example "dell_smm_hwmon" followed "0" which
> you'd think was to be used by software for monitoring the PC
> hardware.
>
ware monitoring.
Remove this module, and this file will disappear.
Do you need this file? We do not know, it is up to you to decide if you
want to monitor the fan and temperature of your laptop or not
https://www.kernel.org/doc/html/latest/hwmon/dell-smm-hwmon.html
I was thinking then to remove
On 2021-07-03 17:29, The Wanderer wrote:
On 2021-07-03 at 12:06, mick crane wrote:
hello,
If I type "lsmod" there is a big list of modules with many followed by
a
"0"
which I guess means they are not needed in the kernel ?
That depends what you mean by "needed&q
On 2021-07-03 at 12:06, mick crane wrote:
> hello,
> If I type "lsmod" there is a big list of modules with many followed by a
> "0"
> which I guess means they are not needed in the kernel ?
That depends what you mean by "needed".
As I understand matter
>
>
> hello,
> If I type "lsmod" there is a big list of modules with many followed by a
> "0"
> which I guess means they are not needed in the kernel ?
>
That means no module depends on it.
But it doesn't mean this particular module isn't requi
Hi.
On Sat, Jul 03, 2021 at 05:06:10PM +0100, mick crane wrote:
> If I type "lsmod" there is a big list of modules with many followed by a "0"
> which I guess means they are not needed in the kernel ?
Third column that lsmod shows is a kernel module reference
hello,
If I type "lsmod" there is a big list of modules with many followed by a
"0"
which I guess means they are not needed in the kernel ?
Does lsmod know about all installed software and if a module is needed
or does software have to be run first ?
If I don't need
Hi,
"Rick Thomas" wrote:
> On Thu, Jan 28, 2021, at 6:21 PM, Rick Thomas wrote:
>
> > Next thing to test -- can I install bullseye the same way?
>
> So I tried installing bullseye from [1] which, incidentally is dated Dec 2,
> 2020. Isn't this kinda old for a "current" Bullseye?
That's from
I would not be surprised if the version number indicated the module in not
Pure Perl, but rather includes some C source code. Which would then need
to be compiled specifically for the version of Perl installed.
mrc
t installed it in /usr/share/perl/5.30/Mail/DMARC.
>
> I thought that’s odd, why would it install it in a folder that has a perl
> version? Why not somewhere a bit more general like /usr/share/perl5?
The directory location may not suit you, but for the short
term you should be able to
ompatibility issues and isn't going to release something onto CPAN
that breaks things, but sometimes it's unavoidable and sometimes the
author isn't mindful of this. There is a big variance in quality of
CPAN modules.
So probably the best thing you can do is cpan2deb and stick with
thos
I see why mechanizing
such a process as apt does should be necessarily be bad. I'm not
talking about blind nightly updates.
If this is truely the best way at the moment to keep perl modules
maintainable, I will try it.
Thanks.
signature.asc
Description: PGP signature
Michael Grant wrote:
> > cpan2deb takes a CPAN module and builds it as a Debian package.
> > Use a common suffix like -mgrant and you can spot these in
> > package listings.
> >
> > When you upgrade, build new versions of all the -mgrant
> > packages.
>
> Thanks. So in one way this makes it eas
> cpan2deb takes a CPAN module and builds it as a Debian package.
> Use a common suffix like -mgrant and you can spot these in
> package listings.
>
> When you upgrade, build new versions of all the -mgrant
> packages.
Thanks. So in one way this makes it easier to remove the module which
cpan do
Michael Grant wrote:
> I try to keep my systems as up to date as possible. I use apt update
> regularly. When I can install a perl module from apt, I usually do so
> because then apt update picks up new versions of it. When I install
> something which has a dependency on a perl module in apt
like /usr/share/perl5?
What happens when Perl gets updated and /usr/share/perl/5.30/ is no longer in
perl’s search path for its modules? I’m worried that using this DMARC perl
module, updating perl could just break mail someday! Shouldn’t the default for
cpan be something other than this
On Sb, 06 iun 20, 14:06:42, Marc Shapiro wrote:
> I usually have three different distros installed. I was wondering if I
> could have a separate partition (possibly in an extended partition)
> containing /boot and /var/modules that would be mounted in each of the
> distros. This wou
On 6/6/20 2:58 PM, to...@tuxteam.de wrote:
On Sat, Jun 06, 2020 at 02:06:42PM -0700, Marc Shapiro wrote:
I usually have three different distros installed. I was wondering
if I could have a separate partition (possibly in an extended
partition) containing /boot and /var/modules that would be
On Sat, Jun 06, 2020 at 02:06:42PM -0700, Marc Shapiro wrote:
> I usually have three different distros installed. I was wondering
> if I could have a separate partition (possibly in an extended
> partition) containing /boot and /var/modules that would be mounted
> in each of the di
On 6/6/20 11:06 PM, Marc Shapiro wrote:
> I usually have three different distros installed. I was wondering if I could
> have a separate partition (possibly in an extended partition) containing /boot
> and /var/modules that would be mounted in each of the distros. This would
> elim
I usually have three different distros installed. I was wondering if I
could have a separate partition (possibly in an extended partition)
containing /boot and /var/modules that would be mounted in each of the
distros. This would eliminate having kernels, initrds and kernel
modules
Some progress has been made.
Today, I have gone to the TTY1 console, logged in to my account, stopped the
LightDM service, and started X. I looked at glxinfo, and saw the correct
info
instead of llvmpipe. It now says that I have "DRI Radeon R200..." in
renderer
string, and when I started Compiz, i
On Fri, 15 May 2020, Celejar wrote:
On Fri, 15 May 2020 01:41:21 -0400 (EDT)
moelmoel2714 wrote:
[...]
vlc worked fine before I did something I know not what. and it works
fine on the other computer. but, to repeat, the working system has a
ton of modules listed but this one has four or so
On Fri, 15 May 2020 01:41:21 -0400 (EDT)
moelmoel2714 wrote:
> On Fri, 15 May 2020, Celejar wrote:
>
> > On Thu, 14 May 2020 22:05:41 -0400 (EDT)
> > moelmoel2714 wrote:
> >
> >> Greets!
> >>
> >> not sure how I got into this bind but I see
On Fri, May 15, 2020 at 02:47:55AM -0400, moelmoel2714 wrote:
[...]
No idea who or what Q4OS is (and not sure I want to know).
> Q4OS puts everything in /etc/apt/sources.list.d/; always makes me a
> tad nervous. anyway, one of the files there, '20_debian.list' has
> non-free on all the active li
On Fri, 15 May 2020, Jude DaShiell wrote:
Have you tried aptitude install vlc -r yet? That switch on the end
installs additional recommended packages.
didn't know about that. didn't yield very much (line wraps ahead):
sudo aptitude install vlc -r
vlc is already installed at the requested ver
On Fri, 15 May 2020, Celejar wrote:
On Thu, 14 May 2020 22:05:41 -0400 (EDT)
moelmoel2714 wrote:
Greets!
not sure how I got into this bind but I seem to have lost the 'access
modules' that allow vlc to view video files (and likely do many other
things; I know I cannot convert vid
On Thu, 14 May 2020 22:05:41 -0400 (EDT)
moelmoel2714 wrote:
> Greets!
>
> not sure how I got into this bind but I seem to have lost the 'access
> modules' that allow vlc to view video files (and likely do many other
> things; I know I cannot convert video).
>
&g
Greets!
not sure how I got into this bind but I seem to have lost the 'access
modules' that allow vlc to view video files (and likely do many other
things; I know I cannot convert video).
when I try to look at an mp4, I get
Your input can't be opened:
VLC is unable to ope
Thanks for the response. However, I am not using VMware on my old PC to
virtualize Debian; I have installed it as a dual-boot system. By the way, when
I have executed "sudo apt list firmware-amd-graphics", it returns the following:
Listing... Done
firmware-amd-graphics/testing,now 20190717-2 all [
Le 07/05/2020 à 19:28, Sven Joachim a écrit :
> No, it is just listed because the llvmpipe driver was developed by
> VMWare. You can see this for yourself, setting LIBGL_ALWAYS_SOFTWARE=1
> in the environment makes libgl use the llvmpipe driver:
>
> ,
> | LIBGL_ALWAYS_SOFTWARE=1 glxinfo | gre
On 2020-05-07 09:50 +0200, didier gaumet wrote:
> Le 06/05/2020 à 22:15, EoflaOE ViceCity a écrit :
>> Hello. Sorry for the length of this problem, but I am trying to get the
>> X server to use my graphics card, AMD Radeon 9200 SE (RV280), instead of
>> my CPU to render things on the desktop. I ac
Le 06/05/2020 à 22:15, EoflaOE ViceCity a écrit :
> Hello. Sorry for the length of this problem, but I am trying to get the
> X server to use my graphics card, AMD Radeon 9200 SE (RV280), instead of
> my CPU to render things on the desktop. I actually have a newer
> computer, but I use the older co
9.3.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
OpenGL ES profile extensions:
To ensure that all of the necessary Radeon modules were loaded correctly, I
have grepped the X server logs (/var/log/Xorg.0.log) and dmesg with
"radeon" and "drm", a
On 4/6/20 5:11 PM, Anil F Duggirala wrote:
>> Python provides virtualenv, plus one can install most of the modules
>> locally with pip3 install --user which will install the
>> modules
>> in ~/.local/lib and tools in ~/.local/bin, so don't forget to add
>> this
> Python provides virtualenv, plus one can install most of the modules
> locally with pip3 install --user which will install the
> modules
> in ~/.local/lib and tools in ~/.local/bin, so don't forget to add
> this
> to your PATH.
>
Could you please explain (to a ne
Meanwhile, the
>> version documented on pypi.org is at version 8.2.0, and has at least one
>> recipe whose arguments are in a different order from the Debian
>> packaged version (grouper, whose order of arguments changed in version
>> 6.0.0). This causes problems, as you
On Sb, 04 apr 20, 11:01:24, Alex Mestiashvili wrote:
>
> Python provides virtualenv, plus one can install most of the modules
> locally with pip3 install --user which will install the modules
> in ~/.local/lib and tools in ~/.local/bin, so don't forget to add this
> to you
TOUCHÉ: Also should be careful with names of python packages since
mistyping can lead to installation of malicious software and with sudo it
makes it even more fun - google for "python malicious packages"
org is at version 8.2.0, and has at least one
> recipe whose arguments are in a different order from the Debian
> packaged version (grouper, whose order of arguments changed in version
> 6.0.0). This causes problems, as you might imagine, with other modules!
>
> So... do people gen
ed on pypi.org is at version 8.2.0, and has at least one
> recipe whose arguments are in a different order from the Debian
> packaged version (grouper, whose order of arguments changed in version
> 6.0.0). This causes problems, as you might imagine, with other modules!
>
> So..
on pypi.org is at version 8.2.0, and has at least one
> recipe whose arguments are in a different order from the Debian
> packaged version (grouper, whose order of arguments changed in version
> 6.0.0). This causes problems, as you might imagine, with other modules!
>
> So... do peop
I always use pip.
From: robo...@news.nic.it on behalf of Joe Pfeiffer
Sent: Friday, April 3, 2020 11:54:31 PM
To: debian-user@lists.debian.org
Subject: python3 modules -- apt vs pip?
I've been using apt (and friends) to maintain my systems, including
p
whose arguments are in a different order from the Debian
packaged version (grouper, whose order of arguments changed in version
6.0.0). This causes problems, as you might imagine, with other modules!
So... do people generally use pip to maintain their python libraries,
rather than apt? What's the r
1 - 100 of 2660 matches
Mail list logo
