Re: Happy 30 Years Debian Project

2023-08-17 Thread Martin Petersen

happy birthday Debian !

and thanks to all you contributors and nice people in this community.

i chose debian as a noob after my first experiments w. suse around 
'98/'99 and never looked back.  best os on the planet and simply my 
digital home.


a cheerful toast to this wonderful creation. the whole is indeed greater 
than the sum of it parts.


rip ian <3

On 2023-08-16  13:31, Luna Jernberg wrote:

Happy Birthday 30 years of the Debian Linux Project

https://www.gamingonlinux.com/2023/08/happy-debian-day-going-30-years-strong/
https://wiki.debian.org/DebianDay/2023
https://wiki.debian.org/DebianHistory?action=AttachFile&do=get&target=Debian-announcement-1993-pic-by-Ian_Murdock.png






Re: Xfce destop environment

2023-01-30 Thread Martin Petersen

Hi William,

xfce configuration files relevant to your user session are stored in 
your home dir.


you can more or less just delete / move the config files and they should 
get recreated upon logging in to a xfce session.


I searched on google for "reset xfce configuration" and found many posts 
like this:


https://forums.linuxmint.com/viewtopic.php?t=122332

"Open a terminal, back up your current configuration:

Code: Select all

mv ~/.config/xfce4  ~/.config/xfce4.bak

Then either leave it like that, which will reset to a default Xfce 
desktop (no Linux Mint customizations), or copy the skeleton files with 
the following command, which will reset to a default Linux Mint Xfce 
desktop:


Code: Select all

cp -r /etc/xdg/xfce4 ~/.config

Then log out and log in again to effectuate the new configuration."

I believe you good get results in such a way.

It also might be just smth small which is broken.

Could you describe "broken" some more? A panel might be hidden but u can 
access all xfce configuration panels by right clicking on the empty 
desktop open a menu, than applications follwed by settings.


Also take a look at the xfce project documentation, it's quite large 
with many screenshots to demonstrate the principles of xfce


https://docs.xfce.org/xfce/getting-started#the_desktop_environment

Nearly everything is just a right click from configuration separated.

You could also create a new user account with xfce configured as default 
session and copy your files over :)


Good luck :)

Cheers,

Martin

On 2023-01-30  19:57, William Torrez Corea wrote:

On Mon, Jan 30, 2023 at 12:43 AM David  wrote:


On Mon, 2023-01-30 at 00:07 -0600, William Torrez Corea wrote:

What happened with my desktop environment?

My desktop environment has problems, the title bar is hidden.


Well, William, from your extensive description of the situation, you
may well have enabled full-screen or have a resolution problem.
It could be anything.
When did this first start happening?
Is there any possible causative action you might have taken which
initiated this behaviour?
Cheers!




The problem started 1 month ago. I don't know what caused the problem, a
day logged in on my laptop and the desktop environment is ruined.

I decided to change my desktop environment for gnome but I want to recover
my old desktop environment XFCE.

*What command is needed to show the error?*

In this way I can supply more information about the problem.

P.D: I search some help in https://wiki.debian.org/Xfce but the problem
still exist





Re: freezing / unstable Debian Testing on MSI Stealth GS77 laptop

2023-01-29 Thread Martin Petersen

Hi JD,

sorry to hear that you have these kind of troubles. I dont know much 
about this gpu/igpu setups, but I want to give some proceedings I would 
choose:


You write that there dont seem to be any logs.

Where did You look? I would expect, that there might me /var/log/syslog 
messages concerning kernel panics or maybe SystemD journal entries from 
that last boot (journalctl -b 1 or smth).


What kind of logs did You check or are some logs Your google searches 
might have produced not there or empty? They might have to bee enabled.


Also there might be error messages of the xserver /var/log/Xorg.0.log.

On top I would take a look into the messages of my Xsession itself 
(~.xsession-errors)	


Many places to check, I'm afraid to say :)

If You have another system You could ssh into Your crash prone laptop to 
get messages live.


Posting some details about the versions of the nvidia modules and such 
might be useful. Some other readers might be able to compare such strings.


And which CPU version does Your notebook have? (cat /proc/cpuinfo, 
maybe). If this is a CPU in a combo setup "some big/beefy cores and some 
lightweight/lowpower cores" it have implications w. applications in my 
opinion.


And one thing I would like to recommend: try another, maybe more recent 
system. Boot from a ubuntu or fedora or some outher fresh distributions 
live iso and check / compare modules and configuration parameters and - 
if possible - behaviour of the particular applications.


Good luck and please post log contents or snippes of logs, if You find some.

Cheers,

Martin


On 2023-01-25  09:56, JD wrote:

Hello,

I'm trying to find some help in order to debug or resolve the issues I'm 
facing. Hopefully, someone will be able to help me here.


The main problem that prevents me from trying to solve it myself is the 
absence of logs and messages.



So, my laptop MSI Stealth GS77 with a Debian testing (up to date) 
installed on it can freeze when launching 3D programs (both with setting 
the nVidia card or the integrated Intel chipset). Once it also 
complained about missing SSD drive (nvme). I currently don't know if 
both could be related, but I'd say it's unlikely.



Some information about my system:

I installed Debian testing since latest Debian stable had many issues 
(no audio, not wifi, unstable 3D graphics...). Debian stable with 
backports didn't helped much (it fixed some issues but not all). 
Therefore, the most practicable is Debian testing.



The issue I have is that seldom (but quite often), when running a 3D 
program, the OS is completely freezing. There is no way to retrieve any 
logs or information about the issue. The screen freezes, the keyboard 
doesn't respond. The only thing I can do is to use a long press on the 
power button to switch the laptop off (alt sys o doesn't work either). 
And on the next reboot, my filesystem fixes wrong inodes and therefore 
this is not possible to consultate any logs.



I don't really like to say that, but the laptop works well on Windows 11 
(no freeze, no crash, no nvme issues). Thus my belief that the issue is 
on the Linux side.



More information:

Desktop: XFCE

nvidia: latest proprietary modules available on Debian. Also tested with 
modules directly provided by nVidia.


3D programs run on nVidia or the Intel chipset (with setting 
appropriately __NV_PRIME_RENDER_OFFLOAD and __GLX_VENDOR_LIBRARY_NAME).


I played a lot with bumblebee, update-glx, keeping updating packages, 
but nothing worked at this time.



uname -a
Linux wormhole 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 
(2023-01-07) x86_64 GNU/Linux



lspci
00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host 
Bridge/DRAM Registers (rev 02)
00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI 
Express x16 Controller #1 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P 
Integrated Graphics Controller (rev 0c)
00:04.0 Signal processing controller: Intel Corporation Alder Lake 
Innovation Platform Framework Processor Participant (rev 02)
00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI 
Express x4 Controller #0 (rev 02)
00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI 
Express Root Port #1 (rev 02)
00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor 
Gaussian & Neural Accelerator (rev 02)
00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB 
Controller (rev 02)
00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI 
#0 (rev 02)
00:0d.3 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI 
#1 (rev 02)
00:12.0 Serial controller: Intel Corporation Alder Lake-P Integrated 
Sensor Hub (rev 01)
00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI 
Host Controller (rev 01)

00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi 
(r

Re: An AMD graphics bug is coming to unstable/testing repo

2023-01-15 Thread Martin Petersen

Hi David, hi All :)

thank You very much for this informative mail, David. It is very kind of 
You to think about all AMD Debian users. Much appreciated !


I don't have to add much. The issue at Freedesktop.org is:

https://gitlab.freedesktop.org/drm/amd/-/issues/2171

There is a fix but everybody is unsure when it will find it's way into 
mainline.


Thank You again, David & have a nice day, Y'all,

Martin

On 2023-01-15  12:04, David wrote:

Hi list readers

A FYI: I am far from expert in these things but I noticed that a kernel
with a known bug affecting AMD graphics is about to enter the unstable
distribution [1], and possibly the testing distribution as well.

[1]:"""
I would like to upload linux version 6.1.6-1 to unstable.
[...]
Notably though there is no fix for #1028451
"""

So I quote below from that bug report [2][3] for readers here so that you
can decide if you want to go read it.

My words end here, the rest of this message is quotes from the footnotes
given at the bottom.

[2]: """
Basically this issue breaks all usage of Displayport MST on amdgpu systems.
Which roughly translates to breaking external monitors for everyone using
an USB-C docks with multiple display outputs (which is pretty common these
days) on AMD laptops. As  well as those like myself who daisy-chain display
port monitors with an amdgpu using graphics card.

So I would expect this impacts a lot of people :/ Which is also why there
is loads of activity and duplicates on the fd.o bug now that 6.1 is
trickling into distributions.

For what it's worth; The revert as currently suggested also reverts big
chunks for Intel and nvidia based GPUs, which unsurprisingly the
maintainers of those aren't too thrilled about. And really i'd be amazed if
it doesn't cause regressions for those systems... Unless the AMD folks pull
a small/targetted fix out their hats, this is likely going to take weeks if
not months before it's resolved in a way that's acceptable for 6.1.y :/
"""

[3]: """
The revert may cause much wider issues which upstream may or may not care
(much) about. And it would be a divergence from upstream.

Getting wider testing of the 6.1 kernel is something I find much more
important. There could be other issues lurking which would not get exposure
and therefor wouldn't get fixed until this bug would be fixed.

Uploading 6.1.6 now would give (us/)upstream a couple of more days to
figure out a potential *better* way to deal with it. One which should be
acceptable for the upstream Stable Kernel maintainers.

But I wouldn't let this bug cause further delays to Testing.  Testing is
meant to test things for the next Stable release and things can and will
break from time to time.  If people can't deal with that, they should not
be running Testing.
"""

[1] https://lists.debian.org/debian-kernel/2023/01/msg00169.html
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028451#35
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028451#40






Lilo-Guru for SoftwareRaidSetup wanted ...

2004-02-17 Thread Martin Petersen
Dear Debian Users,

I am a intermediate user of Debian an SuSE Linux. But I have a Problem, 
which I don`t seem to get solved.

(Plz excuse my English, I am currently in german law exams, so 
everything I say and write should be regarded as nonsense ;).

I want to set up a Software Raid Box with the Raidtools2 in two 
identical IDE Disks. I followed this tutorial 
http://wwwhomes.uni-bielefeld.de/schoppa/raid/woody-raid-howto.html and 
tried to help myself with the Software-Raid-Howto.

The idea is to install Linux on hda, compile a kernel with raid support, 
set up the raid on hdb (with hda as the failed-disk 1 in /etc/raidtab), 
copy the system to raid and then zap the installation on hda.

Everything runs fine until the moment to boot from raid.

The author of my tutorial suggests to create a boot disk first:

dd if=/vmlinuz of=/dev/fd0 bs=2k
rdev /dev/fd0 /dev/md0
rdev -r /dev/fd0 0
rdev -R /dev/fd0 1
This disk doesn't work for me. I know that he writes the kernel to fd0. 
But the system boots from hda, so I guess I didn`t configure Lilo correctly.

Could someone out there plese drop me a few lines 'bout how to setup the 
lilo-configuration?

Thank you in advance,

Martin from Cologne


begin:vcard
fn:Martin Petersen
n:Petersen;Martin
email;internet:[EMAIL PROTECTED]
x-mozilla-html:FALSE
version:2.1
end:vcard