cbdougla
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Blogs
Posts posted by cbdougla
-
-
I would tend to agree that if you're doing an upgrade from 1.2 to 1.4, I would do 1.3 first since there are so many changes in 1.3.
That said, I would not reinstall X at the end of the 1.3 update but go ahead and do the 1.4 update first and make sure your video card related mix-ins are all set before reinstalling X.
-
Quick self-update.
I removed all of the x11-proto packages as suggested in the 1.2 to 1.3 upgrade procedure, removed the stuff I had put in the VIDEO_CARDS variable in make.conf and removed the USE variables for xa and the vmware video driver in various packages in package.use (libdrm, mesa, xorg-server)
I added the vmware-guest as a mixin and emerged the x11-proto, and xorg-server stuff and it all seems to work fine now.
Kudos..
-
I'm performing the 1.4 migration on my VM and it has mostly gone well but I am running into some of those issues with video cards.
I looked into using the video card mixins but I am running this in VMWare and I didn't see a mixin for that so I am bravely making lots of stupid mistakes.
At least, I'll claim to do them on purpose since the alternative is admitting that I don't know what I am doing.
Here's what I continue to get when I try to do an emerge --update for @world
cricket /etc/portage # emerge --update --deep --with-bdeps=y -j3 --keep-going @world
Calculating dependencies... done!emerge: there are no ebuilds built with USE flags to satisfy "media-libs/mesa[xa]".
!!! One of the following packages is required to complete your request:
- media-libs/mesa-19.1.3-r1::core-gl-kit (Missing IUSE: xa)
(dependency required by "x11-drivers/xf86-video-vmware-13.3.0::xorg-kit" [ebuild])
(dependency required by "x11-base/xorg-drivers-1.20::xorg-kit[video_cards_vmware]" [ebuild])
(dependency required by "x11-base/xorg-server-1.20.1-r1::xorg-kit" [ebuild])
(dependency required by "x11-base/xorg-x11-7.4-r3::xorg-kit" [installed])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
I can go post for help in the General Help forum if I can't figure it out shortly. I just figured this was topical to the 1.4 discussion so I would bring it up here.
-
This may not be very helpful but you could create a script to run the appropriate systemctl or rc-service commands and then call that script from your .xsession file with an & at the end to put it in the background.
Or perhaps put it in the /etc/init.d/local file, also with an "&" at the end. This would allow it to start on boot but it wouldn't delay the startup. Maybe. I'd need to try it myself.
If it were me and I didn't want it to start automatically, I would probably not want to to start from the .xsession either and would just opt to start it manually when I logged in.
-
well, I have an update to this.
I downloaded and compiled the xf86-video-vmware driver from the xorg gitlab repo (https://gitlab.freedesktop.org/xorg/driver/xf86-video-vmware) and copied the resulting driver into the /usr/lib/xorg/modules/drivers folder and it seems to be working.
Both drivers report to be version 13.3.0. There still seems to be some strange behavior (it's crashed a couple of times on startup because it couldn't find an input driver?).
Very odd.
-
2 hours ago, skyark said:
Have you include this in your make.conf file before?
VIDEO_CARDS="vmware" INPUT_DEVICES="evdev keyboard mouse synaptics vmmouse"If not doit then update your system whit your new make file.
emerge -auvDN --with-bdeps=y @worldAnd we'll see how it goes.
I remember doing something like that but I've tried so many things that I can't remember.
Just to be clear, it uses the vmware driver...or it tries to and then segfaults . If I move the vmware driver out of the way, it uses modeset and works fine.
I added those lines and did an emerge --newuse --deep --with-bdeps=y -q -j3 @world.
It rebuilt x11-drivers/xf86-input-vmmouse-13.1.0-r1 to and x11-base/xorg-drivers-1.20. I then rebooted and tried startx again with the same results.
Thank you for the suggestion.
-
21 hours ago, skyark said:
Hi, did you make a xorg.conf file?
Can you paste the output.
lspci -kand the
emerge --infoplease...
I should have included that information in the original post. Sorry about that.
I have not created an xorg.conf file. I am letting it autodetect.
I am attaching text files with the information requested.
-
I've been having a problem recently with my Funtoo VM (VMware for Windows host).
When I run startx with the vmware video driver installed, I get a segfault such as the following:
[ 326.599] (II) vmware(0): Initialized VMWARE_CTRL extension version 0.2
[ 326.599] (II) vmware(0): Initialized VMware Xinerama extension.
[ 326.599] (II) vmware(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0
[ 326.600] (EE) vmware(0): Unable to map mmio BAR. Invalid argument (22)
[ 326.607] (EE) vmware(0): Unable to map frame buffer BAR. Invalid argument (22)
[ 326.607] (EE)
[ 326.607] (EE) Backtrace:
[ 326.607] (EE) 0: Xorg (xorg_backtrace+0x4d) [0x555a895894cd]
[ 326.607] (EE) 1: Xorg (0x555a893e3000+0x1aa199) [0x555a8958d199]
[ 326.607] (EE) 2: /lib64/libpthread.so.0 (0x7f61c95c4000+0x14ab0) [0x7f61c95d8ab0]
[ 326.607] (EE) 3: /lib64/libc.so.6 (0x7f61c93fa000+0x16a82d) [0x7f61c956482d]
[ 326.607] (EE) 4: /usr/lib64/xorg/modules/drivers/vmware_drv.so (0x7f61ca984000+0x6e9b) [0x7f61ca98ae9b]
[ 326.607] (EE) 5: Xorg (AddScreen+0xd7) [0x555a8943a417]
[ 326.608] (EE) 6: Xorg (InitOutput+0x3fe) [0x555a89479e6e]
[ 326.608] (EE) 7: Xorg (0x555a893e3000+0x5af7f) [0x555a8943df7f]
[ 326.608] (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xe7) [0x7f61c941bbe7]
[ 326.608] (EE) 9: Xorg (_start+0x2a) [0x555a89427dea]
[ 326.608] (EE)
[ 326.608] (EE) Segmentation fault at address 0x0
[ 326.608] (EE)
Fatal server error:
[ 326.608] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 326.608] (EE)
[ 326.608] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 326.608] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 326.608] (EE)
[ 326.613] (EE) Server terminated with error (1). Closing log file.If I uninstall xf86-video-vmware or just move the driver file to a different name, the X11 starts up and uses the modeset driver and seems to work ok.
Because I can get it to work with modeset, this is really a minor issue but it bugs me that I can't use the vmware driver. I've searched several times for hints on how to fix this but I am at a loss.
I've tried various kernel versions (4.19.2-gentoo, 4.20.0-gentoo, 4.9.168_p1 from debian LTS and 5.0.0-pf2) and I've played around with USE flags to the point that I don't remember everything I have done.
In addition, I followed an article I found on how to get a good stacktrace so my system is currently built with the FEATURES="splitdebug" variable set in make.conf.
So I've got a full gdb backtrace also which I will post at the end.
Any advice would be greatly appreciated. I am definitely in over my head on this problem. Again, it's a minor issue.
-
I am having trouble upgrading from Zabbix 3.2.6 to Zabbix 3.2.7.
The configure script, on my system at least, does not detect the mysqlclient properly.
Here's the section of the configure script I am having trouble with:
if test -x "$MYSQL_CONFIG"; then
MYSQL_CFLAGS="`$MYSQL_CONFIG --cflags`"
_full_libmysql_libs="`$MYSQL_CONFIG --libs`"
for i in $_full_libmysql_libs; do
case $i in
-lmysqlclient)
_client_lib_name="mysqlclient"
;;
-lperconaserverclient)
_client_lib_name="perconaserverclient"
;;
-lmariadbclient)
_client_lib_name="mariadbclient"
;;
-L*)
MYSQL_LDFLAGS="${MYSQL_LDFLAGS} $i"
;;
esac
done
The problem is that when I run mysql_config --libs, I get the following:
ella zabbix-3.2.7 # mysql_config --libs
-L/usr/lib64 -lmariadb -lpthread -lz -ldl -lm -lssl -lcrypto
None of the strings in the case statement are matched so _client_lib_name is not set. So later on in the configure script, this happens:
configure:8148: x86_64-pc-linux-gnu-gcc -o conftest -march=native -O2 -pipe -I/usr/include/mysql -I/usr/include/mysql/.. -rdynamic
-Wl,-O1 -Wl,--sort-common -Wl,--as-needed -L/usr/lib64 conftest.c -l -lm -ldl -lresolv >&5
/usr/lib/gcc/x86_64-pc-linux-gnu/5.3.0/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -l-lm
collect2: error: ld returned 1 exit status
configure:8148: $? = 1
Notice the "-l -lm". After that "-l" is where the _client_lib_name variable is but since it's blank, configure dies thinking that it has not detected libmysqlclient.
I can make configure work by adding the following lines:
8060a8061,8063
> -lmariadb)
> _client_lib_name="mysqlclient"
> ;;
However, I am not a saavy enough programmer to suggest a permanent fix -- which is why I am posting here.
Any help on where to go from here would be greatly appreciated.
EDIT: I forgot to put in my USE flags:
net-analyzer/zabbix-3.2.6::gentoo was built with the following:
USE="agent frontend ipv6 ldap mysql openipmi server snmp ssl -curl -java -libxml2 -odbc -oracle -postgres -proxy -sqlite -ssh -static -xmpp"
Zabbix 5.0.2 Ebuild bug - UI code location change
in Portage Help
Posted
Sorry if this isn't the right place to do this. I clicked on the link to get an account on the bug tracker but it didn't work.
There's a bug in the ebuild for zabbix 5.0.2.
The source code has changed the location of the front-end UI and the ebuild has not been modified to reflect this change.
I humbly propose the attached patch. I am not much of a coder but I've installed the resulting ebuild and it is in production.
patch.txt