SliTaz Forum
You are not logged in.
Hi there,
For those who are interested in such things:
I made the ISO based on LXQt. As far as I understand, LXDE, on which SliTaz is based, will not be developed anymore and LXDE developers are make LXQt now. LXQt is based on Qt framework, not on GTK+2 as our mainline SliTaz.
And, well, I have no skills to boot the LXQt desktop using this ISO. Something wrong there. Screen is just black. All I can is to switch to another virtual terminal using Ctrl + Alt + F2.
Xorg is started. You can start openbox using command
[c]openbox &[/c]
And then you may see black cursor arrow on the black screen.
That's all and I give up.
Anyone who want please make your input.
Ah, the link: http://mirror1.slitaz.org/iso/next/
Have a nice holidays!
Offline
Hi Aleksej
Is LXQT the most essential thing on «next»? I like LXQT, is a lot better than LXDE, but, actually, if I don't use SliTaz (for ex. because I miss some app's like gramps (ancestries tree application), or granule (flashcards to learn, for ex. to re-learn Russian ;-) ...), or marble-QT (corresponding to the earth of google, but as independant application made initially in KDE in Linux) or other like input methodes, as I was not able to activate those found in SliTaz like ibus etc.) I use a very small 32-bit installation (on the 64 laptop) of Devuan/Debian made on the base of
[strong]JWM[/strong]
the old standard window manager of SliTaz!
Why not JWM again: It would preserve the small and easy use of SliTaz in the future and the hability to add other Window / Sessions managers without to un-install LXDE/LXQT. The LXnn-environments are NOT a base for more! They are immediately MORE and an handicap for MORE! I found terrible to use MORE as a BASE instead a real base.
Else small distros using such other delusory (because in her background complexe) installations like openbox etc (I hate openbox for this reason: you often meet enormous difficulties if you try to desinstall it properly, you are often, combined with this very dependant over that from a specific file and tree browser!) are NOT FRIENDLY for those interesting to use an other WM or tree browser, equal if LXDE, LXQT, XFCE or ratpoison.
to desinstall jwm (only a few kilo bytes! is removing really intesting!!!?!!!) you only have to erase less than about 10 very small files and amend only one xinit point ...
... if you consider it as really productive (less than 400 kb ! it is the same as remove slim! both are under 1 Mb together in size!).
to desinstall other wm's, you have sometimes terrible efforts and deceptions after that, that the system doesn't be complete and doesn't work perfectly any more because you miss somewhat...
if the small system with JWM is running perfectly each one can develop himself more energy and try to install other wm's like kde or deepin (I like deepin! it is a progress!) if he wants and perhaps a fast way to add it starting the system (see puppy linux, special adaptations named T.O.P.L.E.S.S., where important choices can be included in / stick to «init» at starting time in Grub!)
why will you
[strong]limitate[/strong]
the next SliTaz like the olds one including a difficult remove window manager of relatively big size in it?
Offline
Hi oui,
Large-large text, as you like it 
Sorry, but I may miss some of your thoughts reading the large text in the limited time.
SliTaz Next is an experimental project.
It's NOT SliTaz 4.0 (aka Stable) NOR SliTaz Rolling (aka Unstable) intended to use by the SliTaz developers.
I only may recommend you NOT to use SliTaz Next, but to use one of the previously mentioned distributions.
SliTaz Next is a parallel individual project.
I started it to have up-to-date base to have ability to use the modern applications.
I wanted to see if we'll have the possibility to use the SliTaz Next in the role of next, updated SliTaz Rolling? Nope. Result is negative. SliTaz Next is a way bigger and resource-demanding to be the next SliTaz Rolling (recall, SliTaz declared to be such small to be used with 128 MB RAM). So, what is the SliTaz Next? One-year long unsuccessful experiment in the SliTaz upgrade.
I don't close or abandon the SliTaz Next project — it is one-year effort of two persons. Please, use it if you want, or don't use otherwise. Make your input, not only words, to the SliTaz Next development...
So, whats next with the SliTaz Next?
It may be the SliTaz Founders (I don't belong to them) will reconsider the paradigm what the SliTaz is — to recognize the SliTaz Next as one of the SliTaz distribution.
And I want to write few words about SliTaz Next distribution content. I learned how to update the packages during this year. But I have a certain difficulties to make the whole distribution to work, you see. Anyway, I planned to make a bunch of ISO with the different content: one is like regular SliTaz Rolling Core, based on GTK+2; other one is like SliTaz RazorQt (RazorQt + LXDE => LXQt) that I made few days ago; also we have some more interesting environments to be implemented as other SliTaz Next ISO: Compiz & Emerald, or Enlightenment, or MATE, or even GNOME And if you give me the precise list of the packages for the JWM-based ISO, then I will make that ISO and you will have ability to use your favorite environment 
Touching the packages list to be included into ISO — all of us have our own favorite list. For example, I need only: good web browser like Firefox or Vivaldi, some terminal emulator, developer text editor Sublime Text, and sometimes office suite LibreOffice, graphic editors GIMP & Inkscape, and music creation software LMMS. Not surprising the fact you don't want that.
Modern "problem" is the segmentation.
Many modern Linux distributions are come with both GTK+2 and GTK+3 on board.
Even closing GTK needs in this way you still may found good and indispensable applications that required Qt.
In my situation: Firefox or Vivaldi required GTK+2 & GTK+3; LibreOffice, GIMP, Inkscape required GTK+2; LMMS required Qt.
Offline
Thankx Aleksej.
slitaz-next-lxqt.iso 2017-Dec-21 20:56:13 102.7M
[attachment=45399,2561]
[attachment=45399,2562]
Offline
@ alanyih
how did you get lxqt started - or are you running it only in Virtual box?
@ Aleksej
first thank you very much for your extremely good work - and I think its not the point to give up!!!! Maybe somebody else can also help
1) start the iso in textmode - add the bootoption screen=text
2) add midnight commander as root wit Tazpkg - gi mc
3) get tux again with exit
4) startx and afterwards kill the desktop with strg+alt+backspace
you get an error, that lxqt is not found
5) now open mc - and then .xsession with F4
you change the last line
exec $WINDOW_MANAGER
to
startlxqt &
save with F2
6) startx again and kill again X
and now I get some errors.....
first some dbus error - D-Bus not built with -rdynamic
then some dri errors
DRI2 FAILED TO OPEN I965 AND SWRAST
this I get with my dell and now I have to check with other computers.......
Offline
the same with old dell.....
so searching for i965_dri.so
http://pkgs.slitaz.org/?file=i965_dri.so&version=n
leads to install mesa-dri
ok - I installed mesa-dri and after startingx and killing it
I get
/usr/lib/dri/i965_dri.so: undefined symbol: _sync_val_compare_and_swap_8
failed to load driver i965
and then its also missing libdrm_amdgpu.so.1
failed to load swrast driver
but again no error in the Xorg.0.log
but where is libdrm_amdgpu.so.1
http://pkgs.slitaz.org/?file=libdrm_amdgpu.so.1&version=n
so fare tonight.....
Offline
sorry about the libdrm_amdgpu-so.1 - this was a typing error - I changed my last post
Offline
@kultex
startx
Boot slitaz-next-lxqt.iso from pc.
switch to VT1: Ctrl-Alt-F1 (X: Ctrl-Alt-F7)
root@slitaz:~# history
0 ps
1 kill -9 2098
2 ps # recheck
3 rm -f /tmp/.X0-lock
4 sed -i 's/$WINDOW_MANAGER/startlxqt/' .xsession
5 cat .xsession # recheck
6 startx
7 history
root@slitaz:~#
[attachment=45406,2563]
root@slitaz:~# ps
[..]
1752 root 0:00 [i915/signal:0]
1754 root 0:00 [i915/signal:1]
1755 root 0:00 [i915/signal:2]
1757 root 0:00 [i915/signal:4]
1789 root 0:00 [kworker/1:1H]
1900 root 0:00 /sbin/udhcpc -b -T 1 -A 12 -i eth0 -p /var/run/udhcpc.eth0.pid
1930 messageb 0:00 /usr/bin/dbus-daemon --system
2016 root 0:00 /usr/sbin/inetd
2057 root 0:00 /usr/sbin/ntpd -p pool.ntp.org
2098 root 0:00 /usr/libexec/Xorg -auth /var/run/slim.auth vt07
2111 root 0:00 -sh
2112 root 0:00 /sbin/getty 38400 tty2
2113 root 0:00 /sbin/getty 38400 tty3
2114 root 0:00 /sbin/getty 38400 tty4
2115 root 0:00 /sbin/getty 38400 tty5
2116 root 0:00 /sbin/getty 38400 tty6
2117 root 0:00 /sbin/getty 115200 38400 9600 4800 2400 ttyS0
2128 root 0:00 ps
root@slitaz:~# cat .xsession
# ~/.xsession: Start X window session manually on your system (startx).
#
. $HOME/.config/slitaz/applications.conf
Xorg &
#xterm &
#xpad &
exec startlxqt
Offline
@alanyih
everything the same as before - I think, it is a intel driver problem - can you attach your Xorg.0.log
I mad you administrator to the forum - I hope you can attach txt files
Offline
leads to install mesa-dri
[ 1462.681] (EE) Failed to load module "glx" (module does not exist, 0)
[ 1462.703] (II) intel(0): SNA initialized with Eaglelake (gen4.5) backend
# tazpkg -gi mesa17-dri
# tazpkg -gi xorg-server-module-glamor
[ 2279.676] (II) LoadModule: "glx"
[ 2279.676] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 2279.684] (II) Module glx: vendor="X.Org Foundation"
[ 2279.684] compiled for 1.19.3, module version = 1.0.0
[ 2279.684] ABI class: X.Org Server Extension, version 10.0
[..]
[ 2279.765] (==) Depth 24 pixmap format is 32 bpp
[ 2279.765] (II) intel(0): SNA initialized with Haswell (gen7.5, gt1)backend
[ 2279.765] (==) intel(0): Backing store enabled
[ 2279.765] (==) intel(0): Silken mouse enabled
[ 2279.765] (II) intel(0): HW Cursor enabled
[ 2279.765] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 2279.765] (==) intel(0): DPMS enabled
[ 2279.765] (==) intel(0): Display hotplug detection enabled
[ 2279.765] (II) intel(0): [DRI2] Setup complete
[ 2279.765] (II) intel(0): [DRI2] DRI driver: i965
[ 2279.765] (II) intel(0): [DRI2] VDPAU driver: va_gl
[ 2279.765] (II) intel(0): direct rendering: DRI2 enabled
[ 2279.765] (II) intel(0): hardware support for Present enabled
[ 2279.765] (--) RandR disabled
[ 2279.775] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 2279.775] (II) AIGLX: enabled GLX_ARB_create_context
[ 2279.775] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 2279.775] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[ 2279.775] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 2279.775] (II) AIGLX: enabled GLX_SGI_swap_control
[ 2279.775] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[ 2279.775] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[ 2279.775] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[ 2279.775] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 2279.775] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[ 2279.775] (II) AIGLX: Loaded and initialized i965
[ 2279.775] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 2279.776] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 0, position (0, 0), rotation normal, reflection none
[ 2279.792] (II) intel(0): Setting screen physical size to 507 x 285
[ 2279.807] (II) config/udev: Adding input device Power Button (/dev/input/event2)
----
X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: SliTaz GNU/Linux
Current Operating System: Linux slitaz 4.9.30-slitaz #2 SMP Fri Jun 16 13:58:14 Europe 2017 i686
Kernel command line: BOOT_IMAGE=/boot/bzImage initrd=/boot/rootfs.gz rw root=/dev/null video=-32 font=ter-v14n autogin lang=en_US kmap=us tz=America/New_York
Build Date: 28 August 2017 11:09:22AM
Current version of pixman: 0.34.0
Before reporting problems, check http://www.slitaz.org/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jan 4 01:21:10 2018
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
(0xbfbaf46c) Warning: LockScreenManager couldn't start
get_cfg(): compton doesn't accept positional arguments.
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
/usr/bin/tazpkg-notify: line 78: yad: not found
/usr/libexec/tazpkg-notification: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory
root@slitaz:~# (II) Server terminated successfully (0). Closing log file.
Offline
mesa17 / mesa
leads to install mesa-dri
# tazpkg -gi mesa17-dri
mesa-dri 12.0.6
mesa17-dri 17.2.4
root@slitaz:~# tazpkg -s mesa
Search result for "mesa"
=======================================================================
Installed packages
-----------------------------------------------------------------------
mesa17 17.2.4 x-window
mesa17-libegl 17.2.4 x-window
mesa17-libgbm 17.2.4 x-window
=======================================================================
3 installed packages found for "mesa"
Available packages
-----------------------------------------------------------------------
libglu-mesa 9.0.0 x-window
libglu-mesa-dev 9.0.0 development
libglw-mesa 8.0.0 x-window
libglw-mesa-dev 8.0.0 development
libegl-mesa 12.0.6 libs
mesa 12.0.6 x-window
mesa-dev 12.0.6 development
mesa-dri 12.0.6 x-window
mesa17 17.2.4 x-window
mesa17-dev 17.2.4 development
mesa17-dri 17.2.4 x-window
mesa17-libegl 17.2.4 x-window
mesa17-libgbm 17.2.4 x-window
mesa17-libswrAVX 17.2.4 x-window
mesa17-libwayland-egl 17.2.4 x-window
mesa17-libxatracker 17.2.4 x-window
mesa17-osmesa 17.2.4 x-window
mesa17-vdpau 17.2.4 x-window
=======================================================================
18 available packages found for "mesa"
Offline
Hi there,
I apologize for the fact that I can't participate in the work on the distro.
We, the whole family, were poisoned 
The day before yesterday, my son was taken to the infectious disease department.
Then yesterday my wife and I felt bad. Yesterday, after visiting my son, I went to bed and slept for 24 hours, waking up many times and falling asleep again.
Today we are all better, but we are still weak.
Sorry again. In addition, I still have an urgent job. And I will go to work this evening, on my second day off. I hope that in a week I will be relatively free.
Thank you guys for your participation!
See you!
Offline
@ Aleksej - you dont need to apologize - take a good rest - its important - I had friends who died from a flue, because they did not respect the illness.
@ alanyih - I know your english is not so good, but do you have a working hardware? As fare a I see from your haswell log, I think, it does not work???
I am interested in the log from your second post with the lxqt-fix.jpg - because here lxqt is working....
its for me clear, that I have to install mesa17-dri and xorg-server-module-glamor - but non of my hardware works to get a workin desktop
Offline
ok - I just was analysing the Xorg.0.log file now from my old dell with mesa17-dri and xorg-server-module-glamor installed and compared it with Xorg.0.log-porteus-lxqt.txt - I have posted in my 3rd post.
On the end you find - [ 690.063] (II) Server zapped. Shutting down - this means that I used strg+alt+backspace to shut down the server
The problem is, that everything looks good and I dont find anything that is wrong, but still no desktop - only black screen.
If you compare it with the Xorg.0.log-lxde.txt - without glx and mesa-dri - these two lines
[ 676.949] (II) intel(0): Modeline "1280x800"x0.0 69.30 1280 1304 1336 1408 800 804 808 820 +hsync -vsync (49.2 kHz eP)
[ 676.949] (II) intel(0): Modeline "1280x800"x0.0 46.18 1280 1304 1336 1408 800 804 808 820 +hsync -vsync (32.8 kHz e)
tell, that xorg is working correctly.
I think, I have to check what happens with LXDE, when I install glx and mesa
Offline
ok - reckecked it with my lxde version of next glx and mesa installed
this boots without any problem - there is only one WW more in the next-lxqt
line 104[ 674.927] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
the lxde Xorg.0.log is attached
and I have to make also a little break now - to much other work....
EDIT: This seems to be fatal error, that stops X to work - there are a lot of threads on this setpgid failed error in the www......
Offline
glxgears
# vblank_mode=0 glxgears
root@slitaz:~# uname -a
Linux slitaz 4.9.30-slitaz #2 SMP Fri Jun 16 13:58:14 Europe 2017 i686 GNU/Linux
root@slitaz:~# glxinfo | egrep 'render|version'
direct rendering: Yes
server glx version string: 1.4
client glx version string: 1.4
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
GLX version: 1.4
GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
OpenGL renderer string: Mesa DRI Intel(R) Haswell Desktop x86/MMX/SSE2
OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.4
OpenGL core profile shading language version string: 4.50
GL_ARB_conditional_render_inverted, GL_ARB_conservative_depth,
GL_MESA_texture_signed_rgba, GL_NV_conditional_render, GL_NV_depth_clamp,
OpenGL version string: 3.0 Mesa 17.2.4
OpenGL shading language version string: 1.30
GL_ARB_compute_shader, GL_ARB_conditional_render_inverted,
GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_light_max_exponent,
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 17.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
GL_OES_fbo_render_mipmap, GL_OES_geometry_point_size,
root@slitaz:~# vblank_mode=0 glxgears
ATTENTION: default value of option vblank_mode overridden by environment.
52035 frames in 5.0 seconds = 10406.958 FPS
51978 frames in 5.0 seconds = 10395.498 FPS
52428 frames in 5.0 seconds = 10485.462 FPS
52128 frames in 5.0 seconds = 10425.471 FPS
[attachment=45421,2573]
Offline
!!! yep solved !!!
I am writing from my new Atom Dell Laptop using LXQT-next !!!
with alanyih's last post, it was clear, that hes haswell is ok..... it cant be, that only his haswell is working.
so what did I wrong - nothing.... all the same - only difference I started with screen=text and he started staight to LXQT
so I tried this and it works
so it is clear what Xorg.0.log says with using VT number 7 and setpigd failed
it wants topen LXQT on console 7 and it is not possible
I have no idea, why it is possible with with alanyihs method [attachment=45422,2574]
Offline
all the same - only difference I started with screen=text and he started staight to LXQT
text mode:
# /etc/init.d/dbus start
# startx
Ref:
/etc/init.d/rcS
# Start X session. Dbus must be started before Xorg and other daemons.
Offline
Cannot open font file ter-v14n
root@slitaz:~# egrep 'zcat|v14n|kmap|alsa' /var/log/boot.log
zcat: /proc/config.gz: No such file or directory
zcat: /proc/config.gz: No such file or directory
zcat: /proc/config.gz: No such file or directory
Setting console font to: ter-v14n...
Cannot open font file ter-v14n
Cannot open font file ter-v14n
Cannot open font file ter-v14n
Cannot open font file ter-v14n
Cannot open font file ter-v14n
Cannot open font file ter-v14n
Loading console keymap: us
/sbin/tazkeymap: line 83: can't open /usr/share/kmap/us.kmap: no such file
/etc/init.d/system.sh: line 125: alsactl: not found
root@slitaz:~#
Offline
ck-launch-session: No such file or directory
# ~/.xinitrc: Executed by Slim/LXDM login manager to startx X session.
EXEC="exec ck-launch-session dbus-launch --sh-syntax --exit-with-session"
root@slitaz:~# ls -l /usr/bin/ck-launch-session
ls: /usr/bin/ck-launch-session: No such file or directory
root@slitaz:~# tazpkg -sp ck-launch-session
Search result for package "ck-launch-session"
=======================================================================
consolekit2
=======================================================================
1 package
root@slitaz:~# tazpkg -s consolekit2
Search result for: consolekit2
=======================================================================
Installed packages
=======================================================================
=======================================================================
0 installed packages found for: consolekit2
Available packages
=======================================================================
consolekit2 1.0.2 system-tools
consolekit2-dev 1.0.2 development
=======================================================================
2 available packages found for: consolekit2
----
root@slitaz:~# cat .xinitrc
# ~/.xinitrc: Executed by Slim/LXDM login manager to startx X session.
# You can use F1 with Slim to change your window manager or configure
# it permanently with your personal applications.conf file.
#
. /etc/slitaz/applications.conf
tazbox mkmenu
[ "$1" ] && WINDOW_MANAGER="$1"
EXEC="exec ck-launch-session dbus-launch --sh-syntax --exit-with-session"
LOG="/dev/null" ; X=$LOG ; ERR=$X
case "$WINDOW_MANAGER" in
openbox|lxde*|icewm*|xfce4|compiz|karmen|dwm|fluxbox*|razor*|mate*)
$EXEC ${WINDOW_MANAGER%-session}-session ;;
enlightenment)
$EXEC enlightenment_start ;;
kde) $EXEC startkde ;;
lxqt) $EXEC startlxqt ;;
*) $EXEC $WINDOW_MANAGER ;;
esac 2>>$ERR >>$X
Offline
Hi there,
ISO were updated: http://mirror1.slitaz.org/iso/next/
[c]slitaz-next-lxqt.iso 2018-Jan-07 19:31:18 86.5M[/c]
(and flavor file included too)
It's still far from the usable state, I know.
For example, it missed locale packs and some ALSA/Pulseaudio modules...
But it should boot to the desktop this time.
Thanks all for the participation!
Offline
Thanks Aleksej.
UUID="2018-01-07-18-31-17-00" LABEL="SliTaz next-lxqt"
tux@slitaz:~$ slitaz
SliTaz GNU/Linux
===============================================================================
Release : next
Architecture : i486
Kernel : 4.9.30-slitaz
Machine type : i686
Home path : /home/slitaz
Configs : /etc/slitaz
Main config : /etc/slitaz/slitaz.conf
Log files : /var/log/slitaz
Packages DB : /var/lib/tazpkg
Installed : 263 packages
Mirror : http://mirror1.slitaz.org/packages/next/
System date : Mon Jan 8 03:39:12 America 2018
--------------
Boot options : BOOT_IMAGE=/boot/bzImage initrd=/boot/rootfs.gz rw root=/dev/null
video=-32 autologin lang=en_US kmap=us tz=America/New_York
===============================================================================
tux@slitaz:~$ blkid
/dev/sr0: UUID="2018-01-07-18-31-17-00" LABEL="SliTaz next-lxqt" TYPE="iso9660"
tux@slitaz:~$
[attachment=45438,2581]
Offline
virtualbox-5.2.4
[attachment=45461,2584]
Guest Additions
$ sudo tazpkg -i virtualbox-guestutils-5.2.4.tazpkg
$ reboot
tux@slitaz:~$ lsmod | grep vbox
vboxvideo 21478 2
ttm 52122 1 vboxvideo
drm_kms_helper 80539 1 vboxvideo
syscopyarea 2478 2 vboxvideo,drm_kms_helper
sysfillrect 2554 2 vboxvideo,drm_kms_helper
sysimgblt 1839 2 vboxvideo,drm_kms_helper
drm 195521 5 vboxvideo,ttm,drm_kms_helper
vboxguest 155608 3
tux@slitaz:~$ modinfo vboxvideo
filename: /lib/modules/4.9.30-slitaz/misc/vboxvideo.ko
version: 5.2.4 r119785
license: GPL and additional rights
description: Oracle VM VirtualBox Graphics Card
author: Oracle Corporation
srcversion: 17B3C051FAD1296B24802B7
alias: pci:v000080EEd0000BEEFsv*sd*bc*sc*i*
depends: drm,drm_kms_helper,ttm,syscopyarea,sysfillrect,sysimgblt
vermagic: 4.9.30-slitaz SMP mod_unload modversions 486
parm: modeset:Disable/Enable modesetting (int)
tux@slitaz:~$ ps | grep VBox
1153 root 0:00 [iprt-VBoxWQueue]
1597 tux 0:00 /usr/bin/VBoxClient --clipboard
1598 tux 0:00 /usr/bin/VBoxClient --clipboard
1612 tux 0:00 /usr/bin/VBoxClient --display
1613 tux 0:00 /usr/bin/VBoxClient --display
1621 tux 0:00 /usr/bin/VBoxClient --seamless
1622 tux 0:00 /usr/bin/VBoxClient --seamless
1630 tux 0:00 /usr/bin/VBoxClient --draganddrop
1631 tux 0:00 /usr/bin/VBoxClient --draganddrop
15352 tux 0:00 grep VBox
tux@slitaz:~$
[attachment=45461,2585]
Offline
Алексей, нашлись 2 проблемы.
1. netsurf как браузер редкостный мусор (я даже tazpanel открыть не смог). Если использовать Qt, то тогда лучше Arora (если ещё жива) или QupZilla.
2. как его на хард поставить-то?
Offline
Александр, приветствую.
[*]Не совсем. Не хочешь Netsurf — используй Tazweb. Но дело в том, что авторизация в TazPanel — и есть настоящий мусор. На каждый чих нужно авторизоваться. Снова и снова. Раньше такое я видел, открыв TazPanel в Firefox. Сейчас, после обновления WebKitGtk, такое же поведение и в TazPanel (и на всём на WebKitGtk основанном, да). Для браузера под Qt нужно сначала web-движок сконпелять. Пока мне лениво. Проще сделать "tazpkg -gi vivaldi" и пох, что он не родной под Qt — размер GTK по сравнению с размером браузера просто смешной.
[*]Наверное, распаковать руками и настроить загрузчик. Или, если доверяешь установщику Tazinst (я нет) — поставь его, запусти и скрести пальцы…
Offline
[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.63 MiB (Peak: 1.77 MiB) ]