Содержание
- Arch Linux
- #1 2017-01-28 13:57:17
- Fatal server error: (EE) cannot run in framebuffer mode. Please specif
- #2 2017-01-28 14:39:34
- Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
- Debian10 framebuffer
- телепаты на самоизоляции 🙁
- Debian10 framebuffer
- Re: Debian10 framebuffer
- Debian10 framebuffer
- Re: Debian10 framebuffer
- Debian10 framebuffer
- Re: Debian10 framebuffer
- Debian10 framebuffer
- Re: Debian10 framebuffer
- Debian User Forums
- One more «X won’t start» issue (X cannot run in framebuffer)
- One more «X won’t start» issue (X cannot run in framebuffer)
- Fatal server error cannot run in framebuffer mode
- cannot run in framebuffer mode. Please specify busIDs
- 3 Answers 3
Arch Linux
You are not logged in.
#1 2017-01-28 13:57:17
Fatal server error: (EE) cannot run in framebuffer mode. Please specif
I did a long overdue update the other day after maybe 4-6 months of not updating (sudo pacman -Syu) and restarted this morning only to find this error when I try to log in to an account that runs startx (then goes back to the login prompt):
Fatal server error: (EE) cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices (EE) (EE)
I checked /var/log/Xorg.0.log, as it suggested and I see the same error and a bunch of data I don’t know the relevance of. I had to add the ‘-f’ flag to get the pacman update to run as one of the updates required it, and I wonder if it didn’t change my video libraries from like AMD to Nvidia. I see some GeForce mentions in the Xorg.0.log file, which I don’t think I was using any Geforce libraries before the update.
Any help would be greatly appreciated.
Last edited by casual (2017-01-28 14:07:53)
#2 2017-01-28 14:39:34
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
I see the same error and a bunch of data I don’t know the relevance of.
We can’t possibly know the relevance either unless you show them to us.
https://bbs.archlinux.org/viewtopic.php?id=57855
I had to add the ‘-f’ flag to get the pacman update to run as one of the updates required it
You forced the entire upgrade instead of reading the news. There’s no telling what damage forcing the entire system update could do.
«UNIX is simple and coherent. » — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
Источник
Debian10 framebuffer
Подождал почти год и обновился до 10-ки.
В X-ах получил: «Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices»
До обновления всё работало мно-о-о-го лет. Пытался загружать с 4.9.0-8 — результата нет.
Машина очень старая, карта VESA
В консоли (screen) всё хорошо.
телепаты на самоизоляции 🙁
именно обновился с 9-ки до 10-ки?
В X-ах получил: «Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices»
Xorg.0.log что говорит? логи смотри или показывай.
Пытался загружать с 4.9.0-8 — результата нет.
ядро откатывал или что?
Debian10 framebuffer
Да, Вы всё правильно поняли.
Re: Debian10 framebuffer
можешь перезалить на другой ресурс? в моём интернете блочат яндекс-диск.
Debian10 framebuffer
Всё непросто, это машина жены 🙂
Re: Debian10 framebuffer
видимо из-за старой карты и возникают проблемы. насколько я понял.
до этого всё было ожидаемо, вот тут «нежданчик» всплыл
дальше крах и то самое сообщение
Поэтому я предлагаю озвучить имя карты и уже по ней искать решение… И возможно появится кто-то кто более эксперт, чем я.
Debian10 framebuffer
$ lspci | grep -E «VGA|3D»
01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01)
Re: Debian10 framebuffer
Внимание! Далее вся ответственность за применение советов и последствия их применения лежит исключительно на Вас.
Пакет xserver-xorg-video-openchrome установлен? Если нет, установите его штатным образом, должно решить проблему.
Debian10 framebuffer
Re: Debian10 framebuffer
всё не просто с вашей картой. насколько я понимаю, основная причина не самоустранилась – файл /dev/dri/card0 по-прежнему не появляется
неожиданное заявление (для меня так точно)
в их git-е есть 0.6.224 (самая свежая версия на сегодня) от 2020-04-20, в установленном пакете версия от 2017-03-07
// хроника; комментарии лишние
В исходном коде имя Вашей карты упоминается, но её PCI ID в исходниках я не увидел
Что делать
В теории собрать свежую версию пакета* должно помочь. Но в этом процессе моя компетенция стремиться к нулю. Могу предложить только создать новый топик с описанием текущей ситуации (как вариант отредактировать или дополнить текущую тему):
- X-не стартуют, приложить (указать ссылки) 1-й и 2-й лог с указанием «до» и «после» установки пакета xserver-xorg-video-openchrome (прошу прощения ранее я указывал ссылку на пакет для Ubuntu; надеюсь Вы устанавливали штатными средствами)
- указать полный вывод lspci для вашей карты (возможно и модель ноутбука затребуют)
- описать предложенное мной решение – сборку из исходников
- изменить/добавить теги (не могу проверить есть такие или нет) «Xorg» «X» «Via» «DRI» «DRM» «KMS» «драйвер»
Источник
Debian User Forums
One more «X won’t start» issue (X cannot run in framebuffer)
One more «X won’t start» issue (X cannot run in framebuffer)
#1 Post by EIKA » 2021-01-01 16:47
My issue might look simple for Linux gurus. And there are a lot of similar threads here on board and other boards. But I spent 2 days working on it, and still no progress
Could you please, guys, look into and help me? I believe that we will be able solve this issue.
I installed Debian 10.7 from «firmware» distributive (at first I tried «netinstall» one, but lately switched to distributive that includes non-free firmware). I chose Desktop environment at tasksel tool at installation stage, as well as KDE Plasma. But system starts on console mode. And if I try to run it by entering X or startx, I am getting a lot of errors:
I googled a lot and found out 3 main directions for this or similar issue:
1. Installing ATI non-free drivers ( accordingly to this manual https://wiki.debian.org/AMDGPUDriverOnStretchAndBuster2 ; played with 20.45 version).
2. Installing free drivers ( accordingly this manual http://forums.debian.net/viewtopic.php? . 93#p720067 )
3. Updating kernel headers.
4. Installing xserver-xorg-video-openchrome package.
But sadly nothing helped. But I am not Linux specialist and probably can do something wrong. I need your help and guidance, please.
Here is how exactly I did method # 1 (installation of ATI proprietary drivers):
Also, it can be important, I skipped patching. Because patch tool failed (it was unable to locate target file «amdgpu_bios.c»). Even after cd to /usr/src/amdgpu* dir.
Here is more data you will probably need:
VGA adapter data:
So it’s AMD Athlon Gold 3150U CPU (codename «Picasso») containing GPU (probably Vega 3). Under Windows GPU recognizes as AMD Radeon 530 Series / AMD Radeon Graphics.
And here is Xorg logs taken from brand new / just installed system (recorded BEFORE installing any drivers / before any actions taken): https://pastebin.com/MWqEEYn2
Now I am ready to start from scratch. I re-installed Debian OS 10.7 and ready for new experiments.
Источник
Fatal server error cannot run in framebuffer mode
gentoo
location: /var/db/repos/gentoo
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
sync-rsync-verify-max-age: 24
sync-rsync-verify-jobs: 1
sync-rsync-extra-opts:
sync-rsync-verify-metamanifest: yes
amd64″
ACCEPT_LICENSE=»*»
CBUILD=»x86_64-pc-linux-gnu»
CFLAGS=»-march=native -O2 -pipe»
CHOST=»x86_64-pc-linux-gnu»
CONFIG_PROTECT=»/etc /usr/share/gnupg/qualified.txt»
CONFIG_PROTECT_MASK=»/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo»
CXXFLAGS=»-march=native -O2 -pipe»
DISTDIR=»/var/cache/distfiles»
EMERGE_DEFAULT_OPTS=»—quiet —with-bdeps=y —keep-going=y —ask-enter-invalid —jobs=12 —load-average=12″
ENV_UNSET=»CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR»
FCFLAGS=»-march=native -O2 -pipe»
FEATURES=»assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr»
FFLAGS=»-march=native -O2 -pipe»
GENTOO_MIRRORS=»ftp://mirror.bytemark.co.uk/gentoo/ https://mirror.bytemark.co.uk/gentoo/ http://mirror.bytemark.co.uk/gentoo/ ftp://mirrors.gethosted.online/gentoo https://mirrors.gethosted.online/gentoo http://mirrors.gethosted.online/gentoo https://www.mirrorservice.org/sites/distfiles.gentoo.org/ http://www.mirrorservice.org/sites/distfiles.gentoo.org/ ftp://ftp.mirrorservice.org/sites/distfiles.gentoo.org/ rsync://rsync.mirrorservice.org/distfiles.gentoo.org/ rsync://mirror.bytemark.co.uk/gentoo/»
LANG=»C.UTF8″
LDFLAGS=»-Wl,-O1 -Wl,—as-needed»
MAKEOPTS=»-j12″
PKGDIR=»/var/cache/binpkgs»
PORTAGE_CONFIGROOT=»/»
PORTAGE_RSYNC_OPTS=»—recursive —links —safe-links —perms —times —omit-dir-times —compress —force —whole-file —delete —stats —human-readable —timeout=180 —exclude=/distfiles —exclude=/local —exclude=/packages —exclude=/.git»
PORTAGE_TMPDIR=»/var/tmp»
USE=»X acl alsa amd64 bzip2 crypt dbus elogind glamour hardened iconv ipv6 libglvnd libtirpc multilib ncurses nls nptl openmp pam pcre pie readline seccomp split-usr ssl ssp unicode xattr xinerama xtpax zlib» ABI_X86=»64″ ADA_TARGET=»gnat_2019″ APACHE2_MODULES=»authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias» CALLIGRA_FEATURES=»karbon sheets words» COLLECTD_PLUGINS=»df interface irq load memory rrdtool swap syslog» CPU_FLAGS_X86=»aes avx avx2 f16c fma3 mmx mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3″ ELIBC=»glibc» GPSD_PROTOCOLS=»ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx» GRUB_PLATFORMS=»efi-64″ INPUT_DEVICES=»libinput» KERNEL=»linux» LCD_DEVICES=»bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text» LIBREOFFICE_EXTENSIONS=»presenter-console presenter-minimizer» LUA_SINGLE_TARGET=»lua5-1″ LUA_TARGETS=»lua5-1″ OFFICE_IMPLEMENTATION=»libreoffice» PHP_TARGETS=»php7-3 php7-4″ POSTGRES_TARGETS=»postgres12 postgres13″ PYTHON_SINGLE_TARGET=»python3_9″ PYTHON_TARGETS=»python3_9″ RUBY_TARGETS=»ruby26 ruby27″ USERLAND=»GNU» VIDEO_CARDS=»nouveau» XTABLES_ADDONS=»quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq proto steal rawnat logmark ipmark dhcpmac delude chaos account»
Unset: CC, CPPFLAGS, CTARGET, CXX, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, RUSTFLAGS
And here is a pastebin link to the output of dmesg
https://pastebin.com/G57R53hB Вернуться к началу
NeddySeagoon
Administrator
Зарегистрирован: 05 июл 2003
Сообщений: 51863
Откуда: 56N 3W
Добавлено: вт ноя 23, 2021 8:34 am Заголовок сообщения: | ||
TimCve,
It looks like your kernel is missing DPM support or dmesg would show the nouveau framebuffer drive in use.
That could be a warning sing that you have an Optimus graphics system in a laptop. Источник cannot run in framebuffer mode. Please specify busIDsfrom my previous question empty screen after booting from live persistent usb, I am able after boot to access all files and folders, but the X-server is unable to load (so I get only to tty1). From the previous question I was able to get to /var/log/Xorg.0.log and took a photo of it : Now I have to somehow specify «busIDs for all framebuffer devices» (as from the file error). So how can I do that? What config file should I edit? I get the very same error from startx (the fatal error of unable to run framebuffer mode). How to connect to X-server? 3 Answers 3I also faced this problem and solved it by installing a more recent kernel from backports. You can create a new file containing the line deb http://deb.debian.org/debian/ buster-backports main contrib non-free in /etc/apt/sources.list.d/ for enabling backports in apt if you are using Debian Buster. The contrib and non-free components will be useful if you also need to install the WiFi drivers. After that you need to install the most recent linux-image* package for the correct CPU architecture and reboot your system. In my case it was the linux-image-5.9.0-0.bpo.5-amd64 package. For checking whether your graphics drivers are installed you can run lshw -c display . If the device is not correctly recognized by the kernel, it will be marked as «UNCLAIMED». Also see this answer. TL;DR: make sure the version for your kernel and the version for the headers match. I was happily using my linux (debian with xfce) when suddenly it just restarted, but it couldn’t boot, it couldn’t even find the grub configuration. I didn’t know what happened. So I got a clonezilla liveCD and restored grub. Disk was fine, memory was fine. After that, I was able to boot ok, but I wouldn’t get a GUI. I tried manually starting X and got the same error, Cannot run in framebuffer mode. Please specify busIDs . I checked lshw -c display as mentioned by Antonio and it was saying «UNCLAIMED». I found that very odd. Everything was working fine, why suddenly I don’t have the drivers for the display? I had them before. so I checked more logs. In the boot log, I had this message: When I searched for that, I found that maybe the kernel was not loading the video drivers. I checked the boot log further back and found: I tried running this command, and found that the system was indeed not loading the nvidia modules. I searched for that and found that my /dev didn’t have any nvidia files. I tried following Antonio’s suggestion above, I added buster-backports to my sources.list , ran a apt-get update and apt-get upgrade first. nothing happened, but it did give me a message that linux-headers-4.19.0-14-XXX was not being used and it wasn’t needed. At first, I didn’t pay attention to that, I thought it was just left-over unnecessary header packages. But I noticed that Antonio mentioned the linux image 5.9 , and my linux image was 4.19 . Since the difference was so big, I decided to first run a apt-get dist-upgrade to see what would happen. and that’s when the magic happened. That command installed the new linux-headers-4.19.0-17-XXX , which matched the linux kernel that I was using, the version of which I hadn’t even payed attention to. After a reboot, my X was working again. So what was preventing my nvidia drivers from working and my X from starting was a mismatch between the kernel and the headers. The problem being that I didn’t update the kernel, the system did that automatically, and did a poor job at it 🙁 So the lesson for today is: disable all automatic updates, manually update your stuff and make sure the update is successful before you can reboot. (just kidding. or am I?) Источник Adblock |
- Index
- » Newbie Corner
- » Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Pages: 1
#1 2017-01-28 13:57:17
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Fatal server error: (EE) cannot run in framebuffer mode. Please specif
I did a long overdue update the other day after maybe 4-6 months of not updating (sudo pacman -Syu) and restarted this morning only to find this error when I try to log in to an account that runs startx (then goes back to the login prompt):
Fatal server error: (EE) cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices (EE) (EE)
I checked /var/log/Xorg.0.log, as it suggested and I see the same error and a bunch of data I don’t know the relevance of. I had to add the ‘-f’ flag to get the pacman update to run as one of the updates required it, and I wonder if it didn’t change my video libraries from like AMD to Nvidia. I see some GeForce mentions in the Xorg.0.log file, which I don’t think I was using any Geforce libraries before the update.
Any help would be greatly appreciated.
Last edited by casual (2017-01-28 14:07:53)
#2 2017-01-28 14:39:34
- Trilby
- Inspector Parrot
- Registered: 2011-11-29
- Posts: 27,838
- Website
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
casual wrote:
I see the same error and a bunch of data I don’t know the relevance of.
We can’t possibly know the relevance either unless you show them to us.
https://bbs.archlinux.org/viewtopic.php?id=57855
casual wrote:
I had to add the ‘-f’ flag to get the pacman update to run as one of the updates required it
You forced the entire upgrade instead of reading the news. There’s no telling what damage forcing the entire system update could do.
«UNIX is simple and coherent…» — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
#3 2017-01-28 16:21:53
- WorMzy
- Forum Moderator
- From: Scotland
- Registered: 2010-06-16
- Posts: 11,023
- Website
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Trilby wrote:
casual wrote:
I had to add the ‘-f’ flag to get the pacman update to run as one of the updates required it
You forced the entire upgrade instead of reading the news. There’s no telling what damage forcing the entire system update could do.
Also, the -f option was removed from pacman over five years ago. What spinoff are you running?
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
#4 2017-01-29 14:28:20
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
I just did a fresh install and I’m getting the exact same error so this must be unrelated to how I updated it. This is what’s in /var/log/Xorg.0.log: https://ptpb.pw/3e04
Last edited by casual (2017-01-29 14:32:37)
#5 2017-01-29 14:34:36
- Trilby
- Inspector Parrot
- Registered: 2011-11-29
- Posts: 27,838
- Website
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
So now the original error is not there. But as you’ve nuked the system and started from scratch there’s no way the original problem can be solved.
The reason it failed this time is that you did not follow all steps to install Xorg. You do not have a video driver.
«UNIX is simple and coherent…» — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
#6 2017-01-29 14:41:07
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Seems like a huge coincidence that I get the exact same error on a fresh install, and I do have a video driver, nvidia-304xx.
#7 2017-01-29 14:44:10
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Nvm, you’re right, the error is different.
#8 2017-01-29 14:45:42
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Honestly I would have tried to fix the original error but the way you responded I figured I bricked my system. My bad.
#9 2017-01-29 14:46:47
- Trilby
- Inspector Parrot
- Registered: 2011-11-29
- Posts: 27,838
- Website
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
(edit original post removed as it was cross posted with the above revisions).
Please note that you can edit your post rather than creating several new posts in sequence.
Are you sure the driver you have installed is the right one? What is your graphics hardware? Do you have the libgl package installed too? Do you need/have an xorg conf file for your nvidia driver?
Whatever happened before, the current problem is that your graphics driver is not properly installed or configured.
«UNIX is simple and coherent…» — Dennis Ritchie, «GNU’s Not UNIX» — Richard Stallman
#10 2017-01-29 15:00:47
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
I’m sure I have the driver the arch wiki suggested, which is for GF6000/7000 series. I have nvidia-304xx-libgl installed.
#11 2017-01-29 15:12:37
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
I just tried running ‘X -configure’ and got this error: https://ptpb.pw/nEEs
#12 2017-01-29 15:13:24
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,651
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
#13 2017-01-29 15:15:38
- seth
- Member
- Registered: 2012-09-03
- Posts: 35,416
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
«pacman -Q | grep nvidia», installing libgl is NOT enough. You also need to install nvidia-304xx
#14 2017-01-29 15:39:23
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Do I have to recompile the sources after I change the line? And where are the sources stored? I don’t have ‘locate’ setup.
#15 2017-01-29 15:49:35
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,651
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Patching_in_ABS#Applying_patches also from there the linked page covering ABS and from there the pages on makepkg and PKGBUILD.
It can be confusing the first time you attempt to build a package from source / apply a patch. If you still have issues applying the patch after having read the above please post the commands you have used and the PKGBUILD after you have modified it.
#16 2017-01-29 19:32:04
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
lol… I can’t even untar the damn thing. I’m afraid this is beyond me at the moment. Maybe I’m not cut out for Arch. Thanks for all the help though.
Last edited by casual (2017-01-29 19:32:53)
#17 2017-01-30 16:55:08
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Decided to give this another shot. I’m confused, why don’t I have /var/abs like the wiki is saying which stores all my PKGBUILDs?
#18 2017-01-30 17:24:57
- loqs
- Member
- Registered: 2014-03-06
- Posts: 15,651
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
https://bugs.archlinux.org/task/52734
Closed by Laurent Carlier (lordheavy)
Monday, 30 January 2017, 10:01 GMT
Reason for closing: Fixed
Additional comments about closing: nvidia-304xx-304.134-5
Is it not fixed with the version 5 release for you?
On the other point /var/abs will not be created until you run abs for the first time for instance
$ sudo abs extra/nvidia-304xx
Then copy the directory to somewhere belonging to the normal user to work on
$ cp -r /var/abs/extra/nvidia-304xx .
$ cd nvidia-304xx
You would apply the changes to PKGBUILD here
Build the package
#19 2017-01-30 18:19:16
- casual
- Member
- Registered: 2016-04-04
- Posts: 18
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Version 5 fixed it, thanks guys.
@loqs: so pacman doesnt use the abs system? Where does it store the PKGBUILDs then?
#20 2017-01-30 18:24:57
- mrunion
- Member
- From: Jonesborough, TN
- Registered: 2007-01-26
- Posts: 1,938
- Website
Re: Fatal server error: (EE) cannot run in framebuffer mode. Please specif
Matt
«It is very difficult to educate the educated.»
-
#1
This is what error I got after I run startx
Code:
(EE)
Fatal server error:
(EE) Cannot run in freamebuffer mode. Please specify busIDs for all framebuffer devices
(EE)
(EE)
please consult the The X.Org Foundation support
at http:/wiki.x.org
for help
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: connection refused
xinit: server error
within log file:
***
(EE) failed to load module "intel " (module does not exist, 0)
(EE) open /dev/dri/card0: No such file or directory
....
scfb trace: probe start
(II)scfb(1): using default device
scfb trace: probe done
(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
(EE) Screen 0 deleted because of no mathing config section
(II) UnloadModule: "modesetting"
I guess some drivers are missing or not supported by the hardware. How to deal with it?
-
#2
What’s your GPU (graphic card/chip)?
Are you running startx as root? Are you part of the video group?
-
Thread Starter
-
#4
What’s your GPU (graphic card/chip)?
Are you running startx as root? Are you part of the video group?
Code:
vendor = 'Intel Corporation'
deice = 'UHD Graphics 605'
class = display
subclass = vga
I am running startx as a root and no I am not part of video group
I am working on it, Sevendogsbsd. Thank you for guiding me.
-
#5
Do not run startx as root. Create an unprivileged user to run X sessions. Add the unprivileged user to the video group as Elazar suggested
-
Thread Starter
-
#6
I did it
Back to problem I did what was said in the handbook https://www.freebsd.org/doc/handbook/x-config.html
It seems like it does not want to obey the rules.
It keeps breaking
I did:
pkg install graphics/drm-kmod
and added to
/usr/local/etc/X11/xorg.conf.d/driver-intel.conf
this:
Code:
Section "Device"
Identifier "Card0"
Driver "intel"
# BusID "PCI:1:0:0"
EndSection
*****I created that file**** The files was not created by system
It keeps missing the driver. What to do next?
-
#8
I did it
Back to problem I did what was said in the handbook https://www.freebsd.org/doc/handbook/x-config.html
It seems like it does not want to obey the rules.
It keeps breaking
I did:
pkg install graphics/drm-kmod
and added to/usr/local/etc/X11/xorg.conf.d/driver-intel.conf
this:
Code:
Section "Device" Identifier "Card0" Driver "intel" # BusID "PCI:1:0:0" EndSection
*****I created that file**** The files was not created by system
It keeps missing the driver. What to do next?
You do not (normally) need an xorg.conf and that is not how the driver is loaded. The driver gets loaded in
/etc/rc.conf
.
Read the section SirDice posted a link to — it tells you exactly what you need to do.
-
Thread Starter
-
#9
Please help me I am confused. In the Xorg error it is specified that intel module is missing, and it is really missing from /boot/modules
How can I download it if It is not set up automatically via pkg install drm-kmod
-
#10
OK, nothing is set up automatically — you have to do it yourself. The install of drm-kmod will add the appropriate driver to the system, you just have to load the driver from
/etc/rc.conf
. Rename or move the xorg.conf file you made. Add this to
/etc/rc.conf
:
Code:
kld_list="/boot/modules/i915kms.ko"
. Also create an unprivileged user and add that user to the «video» group. Login as the unprivileged user and use that user to run startx
.
I think that should be all your have to do — someone else may correct me or add something I have missed.
-
Thread Starter
-
#11
Yeah I did it, but it keeps asking me of module intel, which is missing
And than a new error
(EE) no screen found
-
#12
Reboot to load the driver module.
-
Thread Starter
-
#13
Does not help with startx error
(EE) No drivers available
(EE)
Fatal server error:
(EE) no screen found(EE)
(EE)
please consult……
***
(EE) server terminated with error(1). Closing log file
But the module is loaded perfectly
I think I have to switch to scfb
-
#14
Interesting — maybe add your
/usr/local/etc/X11/xorg.conf.d/driver-intel.conf
back? My system works perfectly with
graphics/drm-kmod
installed and only the entry in
/etc/rc.conf
.
Perhaps someone else has another suggestion.
-
Thread Starter
-
#15
YAAAAYYY I changed in /usr/local/etc/X11/xorg.conf.d/driver-intel.conf from
Section «Device»
Identifier «Card0»
Driver «intel»
# BusID «PCI:1:0:0»
EndSection
to
Section «Device»
Identifier «Card0»
Driver «scfb»
EndSection
and it started to work.
not sure why does it work even when I load scfb driver from a file which name is driver-intel.conf not driver-scfb.conf but I am happy with it.
-
#16
not sure why does it work even when I load scfb driver
The scfb(4) driver is a generic driver.
from a file which name is driver-intel.conf
The name of that file is irrelevant.
-
#17
«scfb» is the frame buffer driver and not the Intel driver. You won’t have 3d acceleration if that is what you are looking for.
-
Thread Starter
-
#18
How can I see what drivers are compatible with my PC?
-
#19
Is this a PC or a laptop and what graphics card do you have?
-
Thread Starter
-
#20
Code:
vendor = 'Intel Corporation'
deice = 'UHD Graphics 605'
class = display
subclass = vga
It is PC
-
Thread Starter
-
#21
I will keep working on it
-
Thread Starter
-
#23
Nice idea!! thanks! the modules has been installed perfectly, but the error is still popping up.
As times goes on my subconsciousness tells me that I should find another way of testing drivers than just installing and trying drivers.
Side note: it is
x11-drivers/xf86-video-intel
that I downloaded
Sorry, your link does not contain useful information
-
#24
No need to download anything, just use pkg to install that driver.
-
Thread Starter
-
#25
BTW my PC works with UEFI mode only.
I hope someone will address the problem any time soon
Describe the bug
Hi there,
I am in the process of setting up an Asus ROG Zephyrus M16 2021 laptop with an Intel Tiger Lake Graphics and an Nvidia RTX 3070 Mobile.
I followed the advice of the README to remove /etc/X11/xorg.conf
, however I do not get a picture without letting xorg generate something itself using sudo Xorg :0 -configure
.
Even then, switching only results in a black screen with a blinking cursor.
I have tried switching between TTY’s, but it doesn’t help, the screen stays black.
Let me know if you need further details, thx.
System info
- Arch Linux
- i3
- LightDM
- Asus ROG Zephyrus M16 2021
- latest stable release (optimus-manager)
- config (see below)
Logs
/usr/share/X11/xorg.conf.d/10-nvidia-drm-outputclass.conf
Section "OutputClass"
Identifier "intel"
MatchDriver "i915"
Driver "modesetting"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
ModulePath "/usr/lib/nvidia/xorg"
ModulePath "/usr/lib/xorg/modules"
EndSection
/etc/X11/xorg.conf.d/10-optimus-manager.conf
Section "Device"
Identifier "integrated"
Driver "modesetting"
BusID "PCI:0:0:2:0"
Option "DRI" "3"
EndSection
/etc/optimus-manager/optimus-manager.conf
[optimus]
switching=bbswitch
pci_power_control=no
pci_remove=no
pci_reset=no
auto_logout=yes
startup_auto_extpower_mode=nvidia
[intel]
driver=modesetting
accel=
tearfree=
DRI=3
modeset=yes
[amd]
driver=modesetting
tearfree=
DRI=3
[nvidia]
modeset=yes
PAT=yes
DPI=96
ignore_abi=no
allow_external_gpus=no
options=overclocking
dynamic_power_management=fine
dynamic_power_management_memory_threshold=
/home/markus/.local/share/xorg/Xorg.0.log
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 109.493]
X.Org X Server 1.21.1.1
X Protocol Version 11, Revision 0
[ 109.500] Current Operating System: Linux M16 5.15.2-arch1-1 #1 SMP PREEMPT Fri, 12 Nov 2021 19:22:10 +0000 x86_64
[ 109.500] Kernel command line: BOOT_IMAGE=/arch/BOOT/default@/vmlinuz-linux root=ZFS=rpool/arch/ROOT/default rw zfs_import_dir=/dev/disk/by-id loglevel=3 quiet
[ 109.506]
[ 109.509] Current version of pixman: 0.40.0
[ 109.514] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 109.514] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 109.524] (==) Log file: "/home/markus/.local/share/xorg/Xorg.0.log", Time: Mon Nov 15 01:17:55 2021
[ 109.527] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 109.529] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 109.529] (==) No Layout section. Using the first Screen section.
[ 109.529] (==) No screen section available. Using defaults.
[ 109.529] (**) |-->Screen "Default Screen Section" (0)
[ 109.529] (**) | |-->Monitor "<default monitor>"
[ 109.529] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[ 109.529] (**) | |-->Device "integrated"
[ 109.529] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 109.529] (==) Automatically adding devices
[ 109.529] (==) Automatically enabling devices
[ 109.529] (==) Automatically adding GPU devices
[ 109.529] (==) Automatically binding GPU devices
[ 109.529] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 109.529] (WW) The directory "/usr/share/fonts/misc" does not exist.
[ 109.529] Entry deleted from font path.
[ 109.529] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF".
[ 109.529] Entry deleted from font path.
[ 109.529] (Run 'mkfontdir' on "/usr/share/fonts/TTF").
[ 109.529] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[ 109.529] Entry deleted from font path.
[ 109.529] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[ 109.529] Entry deleted from font path.
[ 109.529] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[ 109.529] Entry deleted from font path.
[ 109.529] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[ 109.529] Entry deleted from font path.
[ 109.529] (==) FontPath set to:
[ 109.529] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 109.529] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 109.529] (II) Module ABI versions:
[ 109.529] X.Org ANSI C Emulation: 0.4
[ 109.529] X.Org Video Driver: 25.2
[ 109.529] X.Org XInput driver : 24.4
[ 109.529] X.Org Server Extension : 10.0
[ 109.530] (++) using VT number 5
[ 109.531] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[ 109.531] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 109.531] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0
[ 109.532] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[ 109.533] (--) PCI:*(0@0:2:0) 8086:9a60:1043:132c rev 1, Mem @ 0x6230000000/16777216, 0x4000000000/268435456, I/O @ 0x00005000/64, BIOS @ 0x????????/131072
[ 109.533] (--) PCI: (1@0:0:0) 10de:249d:1043:132c rev 161, Mem @ 0x85000000/16777216, 0x6000000000/8589934592, 0x6200000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[ 109.533] (II) Open ACPI successful (/var/run/acpid.socket)
[ 109.533] (II) LoadModule: "glx"
[ 109.533] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 109.534] (II) Module glx: vendor="X.Org Foundation"
[ 109.534] compiled for 1.21.1.1, module version = 1.0.0
[ 109.534] ABI class: X.Org Server Extension, version 10.0
[ 109.534] (II) LoadModule: "modesetting"
[ 109.534] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 109.534] (II) Module modesetting: vendor="X.Org Foundation"
[ 109.534] compiled for 1.21.1.1, module version = 1.21.1
[ 109.534] Module class: X.Org Video Driver
[ 109.534] ABI class: X.Org Video Driver, version 25.2
[ 109.534] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 109.534] (WW) Falling back to old probe method for modesetting
[ 109.534] (II) modeset(0): using default device
[ 109.534] (II) modeset(G0): using drv /dev/dri/card0
[ 109.534] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 109.534] (EE)
Fatal server error:
[ 109.534] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 109.534] (EE)
[ 109.534] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 109.534] (EE) Please also check the log file at "/home/markus/.local/share/xorg/Xorg.0.log" for additional information.
[ 109.534] (EE)
[ 109.547] (EE) Server terminated with error (1). Closing log file.
optimus-manager.service:
-- Boot bf83c61b54e548b19957935b2d84d5ee --
Nov 15 01:16:15 M16 systemd[1]: Starting Optimus Manager Commands Daemon...
Nov 15 01:16:15 M16 python3[5074]: [19] INFO: # Daemon pre-start hook
Nov 15 01:16:15 M16 python3[5074]: [19] INFO: Removing /etc/X11/xorg.conf.d/10-optimus-manager.conf (if present)
Nov 15 01:16:15 M16 python3[5074]: [20] INFO: Copying /etc/optimus-manager/optimus-manager.conf to /var/lib/optimus-manager/tmp/config_copy.conf
Nov 15 01:16:15 M16 python3[5074]: [23] INFO: Startup mode is: integrated
Nov 15 01:16:15 M16 python3[5074]: [23] INFO: Writing state {'type': 'pending_pre_xorg_start', 'requested_mode': 'integrated', 'current_mode': None}
Nov 15 01:16:15 M16 python3[5074]: [24] INFO: Daemon pre-start hook completed successfully.
Nov 15 01:16:15 M16 python3[5074]: [24] INFO: Calling Xorg pre-start hook.
Nov 15 01:16:15 M16 python3[5705]: [9] INFO: # Xorg pre-start hook
Nov 15 01:16:15 M16 python3[5705]: [10] INFO: Previous state was: {'type': 'pending_pre_xorg_start', 'requested_mode': 'integrated', 'current_mode': None}
Nov 15 01:16:15 M16 python3[5705]: [10] INFO: Requested mode is: integrated
Nov 15 01:16:16 M16 python3[5705]: [712] INFO: Available modules: ['nouveau', 'bbswitch', 'acpi_call', 'nvidia', 'nvidia_drm', 'nvidia_modeset', 'nvidia_uvm']
Nov 15 01:16:16 M16 python3[5705]: [712] INFO: Unloading modules ['nvidia_drm', 'nvidia_modeset', 'nvidia_uvm', 'nvidia'] (if loaded)
Nov 15 01:16:16 M16 python3[5705]: [715] INFO: Loading module bbswitch
Nov 15 01:16:16 M16 python3[5705]: [719] INFO: Setting GPU power to OFF via bbswitch
Nov 15 01:16:16 M16 python3[5705]: [735] WARNING: bbswitch is enabled, pci_power_control option ignored.
Nov 15 01:16:16 M16 python3[5705]: [1351] INFO: Writing to /etc/X11/xorg.conf.d/10-optimus-manager.conf
Nov 15 01:16:16 M16 python3[5705]: [1351] INFO: Writing state {'type': 'pending_post_xorg_start', 'switch_id': '20211115T011615', 'requested_mode': 'integrated'}
Nov 15 01:16:16 M16 python3[5705]: [1351] INFO: Xorg pre-start hook completed successfully.
Nov 15 01:16:16 M16 systemd[1]: Started Optimus Manager Commands Daemon.
Nov 15 01:16:16 M16 python3[6503]: [0] INFO: # Commands daemon
Nov 15 01:16:16 M16 python3[6503]: [1] INFO: Opening UNIX socket
Nov 15 01:16:16 M16 python3[6503]: [1] INFO: Awaiting commands
> optimus-manager --status
ERROR: a GPU setup was initiated but Xorg post-start hook did not run.
Log at /var/log/optimus-manager/switch/switch-20211115T011615.log
If your login manager is GDM, make sure to follow those instructions:
https://github.com/Askannz/optimus-manager#important--gnome-and-gdm-users
If your display manager is neither GDM, SDDM nor LightDM, or if you don't use one, read the wiki:
https://github.com/Askannz/optimus-manager/wiki/FAQ,-common-issues,-troubleshooting
Cannot execute command because of previous errors.
/var/log/optimus-manager/switch/switch-20211115T011615.log
[9] INFO: # Xorg pre-start hook
[10] INFO: Previous state was: {'type': 'pending_pre_xorg_start', 'requested_mode': 'integrated', 'current_mode': None}
[10] INFO: Requested mode is: integrated
[712] INFO: Available modules: ['nouveau', 'bbswitch', 'acpi_call', 'nvidia', 'nvidia_drm', 'nvidia_modeset', 'nvidia_uvm']
[712] INFO: Unloading modules ['nvidia_drm', 'nvidia_modeset', 'nvidia_uvm', 'nvidia'] (if loaded)
[715] INFO: Loading module bbswitch
[719] INFO: Setting GPU power to OFF via bbswitch
[735] WARNING: bbswitch is enabled, pci_power_control option ignored.
[1351] INFO: Writing to /etc/X11/xorg.conf.d/10-optimus-manager.conf
[1351] INFO: Writing state {'type': 'pending_post_xorg_start', 'switch_id': '20211115T011615', 'requested_mode': 'integrated'}
[1351] INFO: Xorg pre-start hook completed successfully.
[4] INFO: # Xorg post-start hook
[957] INFO: Running /etc/optimus-manager/xsetup-integrated.sh
[995] ERROR: Cannot set DPI (xrandr error):
None
[996] INFO: Writing state {'type': 'done', 'switch_id': '20211115T011615', 'current_mode': 'integrated'}
[996] INFO: Xorg post-start hook completed successfully.
> prime-offload
[4] INFO: # Xorg post-start hook
[957] INFO: Running /etc/optimus-manager/xsetup-integrated.sh
[995] ERROR: Cannot set DPI (xrandr error):
None
[996] INFO: Writing state {'type': 'done', 'switch_id': '20211115T011615', 'current_mode': 'integrated'}
[996] INFO: Xorg post-start hook completed successfully.
> optimus-manager --status
Optimus Manager (Client) version 1.4
Current GPU mode : integrated
GPU mode requested for next login : no change
GPU at startup : integrated
Temporary config path: no
Hi all!
My issue might look simple for Linux gurus. And there are a lot of similar threads here on board and other boards. But I spent 2 days working on it, and still no progress
Could you please, guys, look into and help me? I believe that we will be able solve this issue.
I installed Debian 10.7 from «firmware» distributive (at first I tried «netinstall» one, but lately switched to distributive that includes non-free firmware). I chose Desktop environment at tasksel tool at installation stage, as well as KDE Plasma. But system starts on console mode. And if I try to run it by entering X or startx, I am getting a lot of errors:
Code: Select all
Fatal server error:
X cannot run in framebuffer mode
Please specify BusIDs for all framebuffer devices.
xinit: saving up
xinit: Server terminated with error (1).
xinit: Unable to connect to X server: connection refused
xinit: server error
I googled a lot and found out 3 main directions for this or similar issue:
1. Installing ATI non-free drivers ( accordingly to this manual https://wiki.debian.org/AMDGPUDriverOnStretchAndBuster2 ; played with 20.45 version).
2. Installing free drivers ( accordingly this manual http://forums.debian.net/viewtopic.php? … 93#p720067 )
3. Updating kernel headers.
4. Installing xserver-xorg-video-openchrome package.
But sadly nothing helped. But I am not Linux specialist and probably can do something wrong. I need your help and guidance, please.
Here is how exactly I did method # 1 (installation of ATI proprietary drivers):
Code: Select all
apt-get install linux-headers-$(uname -r)
tar -xvf amdgpu-pro-20.45-1164792-ubuntu-20.04.tar.xz
cd amdgpu-pro-20.45-1164792-ubuntu-20.04
dpkg -i amdgpu-dkms-firmware_*.deb
dpkg -i amdgpu-core_*.deb amdgpu-dkms_*.deb
Also, it can be important, I skipped patching. Because patch tool failed (it was unable to locate target file «amdgpu_bios.c»). Even after cd to /usr/src/amdgpu* dir.
Here is more data you will probably need:
VGA adapter data:
Code: Select all
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev ce)
So it’s AMD Athlon Gold 3150U CPU (codename «Picasso») containing GPU (probably Vega 3). Under Windows GPU recognizes as AMD Radeon 530 Series / AMD Radeon Graphics.
And here is Xorg logs taken from brand new / just installed system (recorded BEFORE installing any drivers / before any actions taken): https://pastebin.com/MWqEEYn2
Now I am ready to start from scratch. I re-installed Debian OS 10.7 and ready for new experiments.
View previous topic :: View next topic | |||||||
Author | Message | ||||||
---|---|---|---|---|---|---|---|
TimCve n00b Joined: 17 Jan 2021 |
|
||||||
Back to top |
|
||||||
mike155 Advocate Joined: 17 Sep 2010 |
|
||||||
Back to top |
|
||||||
TimCve n00b Joined: 17 Jan 2021 |
|
||||||
Back to top |
|
||||||
NeddySeagoon Administrator Joined: 05 Jul 2003 |
|
||||||
Back to top |
|
||||||
TimCve n00b Joined: 17 Jan 2021 |
|
||||||
Back to top |
|
||||||
|
You cannot post new topics in this forum |
Приобрел лицензию и ноутбук для изделия на предприятии. Ноутбук Dell Inspiron 3793 (BIOS only UEFI, NVME, I7 1065G7 + UHD 630, MX230).
При установке с диска Astra Linux SE, Astra Linux CE или Debian 10 одна и та же проблема: Установка проходит успешно, в GRUB меню выбираю любой режим ( на всех режимах одно и тоже), бежит текст запуска и в момент запуска GUI очищается консоль, в углу горит курсор и больше ничего не происходит. Кнопками Alt+F4 меняю рабочий терминал и там могу ввести логин и пароль в консоли и зайти в систему. В общем, ОС установилась, работает полностью все команды и инструменты, кроме Xorg. Выкачал логи и прикрепил https://yadi.sk/d/zrSFFzpK7ufBaw?w=1 . Что касается других ОС, то UBUNTU и Lubuntu работают отлично, оболочки Gnome и Lxqt Запускались без проблем. Полагаю дело в Dedian подобных ос и их особенностями общения с UEFI, читал несколько похожих вопросов на форуме, некоторые вопросы решались возвратом на Legacy mode, Но я так не могу, в моём биосе Dell полностью убрали поддержку Legacy режима. может удастся настроить BIOS и GRUB правильно, вот только я не знаю, если нужны скрины — пишете, прикреплю.
кратко лог Xorg:
[ 63.124] (II) intel: Driver for Intel(R) HD Graphics
[ 63.124] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 63.124] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[ 63.124] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 63.124] (II) FBDEV: driver for framebuffer: fbdev
[ 63.124] (II) VESA: driver for VESA chipsets: vesa
[ 63.124] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
[ 63.124] (WW) LoadKernelModule: Setting of real/effective user Id to 0/0 failed[ 63.125] (WW) LoadKernelModule: Setting of real/effective user Id to 0/0 failed[ 63.125] (WW) Falling back to old probe method for modesetting
[ 63.126] (II) modeset(1): using default device
[ 63.126] (II) Loading sub module «fbdevhw»
[ 63.126] (II) LoadModule: «fbdevhw»
[ 63.126] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 63.126] (II) Module fbdevhw: vendor=»X.Org Foundation»
[ 63.126] compiled for 1.20.4, module version = 0.0.2
[ 63.126] ABI class: X.Org Video Driver, version 24.0
[ 63.126] (EE) Unable to find a valid framebuffer device
[ 63.126] (WW) Falling back to old probe method for fbdev
[ 63.126] (II) Loading sub module «fbdevhw»
[ 63.126] (II) LoadModule: «fbdevhw»
[ 63.126] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 63.126] (II) Module fbdevhw: vendor=»X.Org Foundation»
[ 63.126] compiled for 1.20.4, module version = 0.0.2
[ 63.126] ABI class: X.Org Video Driver, version 24.0
[ 63.126] (EE) open /dev/fb0: Permission denied
[ 63.126] (II) modeset(G0): using drv /dev/dri/card0
[ 63.126] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 63.126] (EE) Screen 0 deleted because of no matching config section.
[ 63.126] (II) UnloadModule: «modesetting»
[ 63.126] (EE) Screen 1 deleted because of no matching config section.
[ 63.126] (II) UnloadModule: «fbdev»
[ 63.126] (II) UnloadSubModule: «fbdevhw»
[ 63.126] (EE)
Fatal server error:
[ 63.126] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
[ 63.126] (EE)
[ 63.126] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 63.126] (EE) Please also check the log file at «/var/log/fly-dm/Xorg.0.log» for additional information.
[ 63.126] (EE)
[ 63.129] (EE) Server terminated with error (1). Closing log file.
Кратко вывод команды Lspci:
00:02.0 VGA compatible controller: Intel Corporation Device 8a52 (rev 07) (prog-if 00 [VGA controller])
Subsystem: Dell Device 097a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 255
Region 0: Memory at b0000000 (64-bit, non-prefetchable) [size=16M]
Region 2: Memory at a0000000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 5000
[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [40] Vendor Specific Information: Len=0c <?>
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
Capabilities: [ac] MSI: Enable- Count=1/1 Maskable+ 64bit-
Address: 00000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 00008000, Page Request Allocation: 00000000
01:00.0 3D controller: NVIDIA Corporation Device 1d11 (rev a1)
Subsystem: Dell Device 097a
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at b1000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at 80000000 (64-bit, prefetchable) [size=256M]
Region 3: Memory at 90000000 (64-bit, prefetchable) [size=32M]
Region 5: I/O ports at 4000
Expansion ROM at <ignored> [disabled]
Capabilities: [60] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
<…>
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia