Hi.
Not sure about a step-by-step guide, but I suggest reading classic old
books series "Definitive Guides to the X Window System" (aka "colour
books")
Especially "X Windows System Administrator's Guide" and "X Windows System
User Guide".
They are pretty old but really helped me with understand the
So, you have 2 video outputs:
One is R128:
> [32.185] (WW) R128(0): DDC2/I2C is not properly initialized
> [32.185] (WW) R128(0): DDC2/I2C is not properly initialized
> [32.185] (II) R128(0): EDID for output VGA-0
It doesn't see any monitor.
Another is modeset (kernel) based driver f
I do not have experience with R128 driver, unfortunately.
> [32.360] (II) R128(0): initializing int10
> [32.361] (EE) R128(0): V_BIOS address 0x35d70 out of range
I believe that means the card can't emulate the old Video BIOS interface.
It shouldn't prevent it from working
> [32.362]
>
>
> Does anyone have any idea what to do to get that root prompt back?
>
> Hi.
Debian list is a better place for this question.
Reboot, click "tab", and when you see GRUB menu, choose the "recovery"
entry.
Or in the same menu click "e" to open the boot menu editor.
Find linux command (it should
>
>
> '-b&h-lucidatypewriter-medium-r-normal-sans-0-0-100-100-m-0-iso10646-1'
> Warning: Cannot convert string
> "-b&h-lucidatypewriter-medium-r-normal-sans-0-0-100-100-m-0-iso10646-1"
> to type FontStruct
> Warning: Missing charsets in String to FontSet conversion
> Missing charset ISO8859-1 for f
>
> xterm: cannot load font
> '-b&h-lucidatypewriter-medium-r-normal-sans-11-80-100-100-m-70-iso10646-1'
>
Hi.
What does ``xfontsel`` show?
Have you tried to provide a font explicitly with ``xterm -fn``?
You can also try xft/fontconfig fonts (they are rendered on the client, not
server) and much s
Hi.
I believe xsession could be used:
https://wiki.debian.org/Xsession
On Fri, Feb 5, 2021 at 12:09 PM aprekates wrote:
> OS: Debian GNU/Linux 10 (buster) x86_64
> Kernel: 4.19.0-13-amd64
> DE: KDE
> Display: x11
> server: X.Org 1.20.4
>
> I managed to create a custom xkb mapping using a home di
ig/GiveConsole
Ilya.
On Mon, Oct 19, 2020 at 7:40 AM Chris Sorenson wrote:
> Those snippets from your scripts look correct, is your sessreg set to
> executable?
>
> Does anyone else have access to your system?
>
> Might it have been hacked to prevent programs like "w,&qu
#x27;t show the login. What does your Xstartup
> say?
>
>
> On 10/18/2020 07:00 AM, xorg-requ...@lists.x.org wrote:
> >
>
> >
> > Message: 1
> > Date: Sun, 18 Oct 2020 00:12:22 +0300
> > From: IL Ka
> > To: xorg
> > Subject: xdm-config f
Hello.
I found that xdm-config has the following lines
DisplayManager*startup: /usr/lib64/X11/xdm/Xstartup
DisplayManager._0.startup: /usr/lib64/X11/xdm/GiveConsole
As I understand, that means GiveConsole is run instead of Xstartup,
so sessreg is not called, and I do not see my login in "w" outpu
Here is what happened:
> [ 347.043] (WW) RADEON(0): No outputs definitely connected, trying again...
> [ 347.043] (WW) RADEON(0): Unable to find connected outputs - setting
> 1024x768 initial framebuffer
> [ 347.043] (II) RADEON(0): mem size init: gart size :7fbcf000 vram size:
> s:800
I now answering my own question:)
ZaphodHeads is exactly what I was looking for.
I created 2 devices with Screen and ZaphodHeads, and it know works
Section "Monitor"
Identifier "External"
Option "PreferredMode" "1920x1200"
Option "RightOf" "Onboard"
EndSection
Section "De
PS: I was able to separate them with "ZaphodHeads", but Zaphod is for
multiseats, and I do not want to have different keyboards and mice.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/ma
Hello,
I use intel driver for laptop with two outputs: LVDS and HDMI.
Both monitors are merged to one big screen, but I want them to use separate
screens, so I can use DISPLAY=:0.1.
I was trying to declare separate screens, but it doesn't work: I see two
screens in my log, but X still has one scr
In most cases there is no need to run "-configure" since X can autodetect
many things using defaults provided by distro.
Have you tried official debian wiki (it is about amdgpu, not general
modesetting)
https://wiki.debian.org/AtiHowTo ?
I think that "/dev/dri/card0: No such file or directory" m
Hello.
1. Window manager is a separate client. Word processor and Web browser do
not use it directly. They talk to XOrg an XOrg consults Window manager (if
any) asking it to draw window. Technically, you can run client even without
of Window manager.
2. Drivers may be in Kernel or in Xorg itself.
Hello.
Any errors in /var/log/Xorg.0.log ?
On Thu, Sep 12, 2019 at 11:25 AM sujan mlr wrote:
> Hello,
>
> I am getting following error after the patching and reboot of the machine.
> Patched form Oracle Linux 7.6 to 7.7, Now GUI is not coming ssh to the
> machine works fine.
>
> Error:
>
>
>
>
>
[20.515] (==) FBDEV(0): Default visual is TrueColor
[20.515] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[20.515] (II) FBDEV(0): hardware: hyperv_fb (video memory: 8192kB)
On Mon, Feb 25, 2019 at 8:06 PM Adam Jackson wrote:
> On Mon, 2019-02-25 at 18:33 +0300, IL Ka wr
Hello Adam,
Could have fooled me. I see fbdev driver builds in current versions of
> Arch, Debian, Fedora, Gentoo, and openSUSE. What distro are you using
> that lacks it?
>
Slackware:) I see xf86-video-fbdev in "extras" folder, but it is i586
version.
And there is no x64 version.
After reading
Hello.
I run Linux as Hyper-V guest.
It seems that there is no DRI/DRM driver for Hyper-V videocard, but there
is Framebuffer driver for it.
So, I enabled framebuffer driver and my idea was to run XOrg using fbdev
driver on top of it.
But there is no such driver in modern Linux distros.
Questio
20 matches
Mail list logo
