ok - I have to try myself....
slitaz, GMA, xorg, opengl..
(64 posts) (5 voices)-
Posted 6 years ago #
-
ok everything works as it should...
you download:
http://mirror1.slitaz.org/iso/rolling/slitaz-rolling-core.iso
rename and copy rootfs-last.gz and vmlinuz-3.2.98-slitaz-last to /boot
and add the lines you see in the screenshot (adopt your language)
and you cannot run tazx when X is started.....
Posted 6 years ago # -
ty kultex
what i've done :
download the link you indicated
mount it
browse the boot dir
copy the vmlinuz to the /boot/vmlinuzlast of the computer
rebooted
edit in grub config to make booting on the vmlinuzlast
slitaz starts
moving in 60-device vesa and fbdev to intel
killed Xorg
logged as user in console
launched startxmodprobe : ERROR : could not insert 'i915' : Unknown symbol in module, or unknown parameter (see dmesg)
fatal server error :
no screen foundPosted 6 years ago # -
thats not necessary
"moving in 60-device vesa and fbdev to intel" - dont touch it
and you have to start slitaz in text mode then run tazx and this will do a new config...
Posted 6 years ago # -
@lm2:
Hopefully I do not write something further disturbing. But some years ago I had with the new Slitaz 4 similar problems with X. And I solved it like this:
Instead of such a kernel line
kernel /boot/vmlinuz-3.2.71-slitaz root=/dev/sda6 quiet modeset
I used this:
kernel /boot/vmlinuz-3.2.71-slitaz root=/dev/sda6 quiet nomodeset
Only 2 letters changed! ;-)
At that time it worked immediately.Posted 6 years ago # -
i just tried again, it's limited to 800x600 px.
Posted 6 years ago # -
boot this
and post your xorg.0.log
Posted 6 years ago # -
thanks kultex
the problem here is that your upload concerns a rootfs.gz
up to here i was testing with the vmlinuz, there is nothing about rootfs.gz in the grub boot..Posted 6 years ago # -
vmlinuz is just the kernel - the rootfs.gz contains all the rest...
initrd=/boot/rootfs.gz
Posted 6 years ago # -
ok, so i just did this with the only rootfs.gz you uploaded.
i'm wondering : if i have to change nothing in the xorg conf files, that means its like next, everything is done automatically?because when i do nothing, it's still in 800x600 without opengl...
Posted 6 years ago # -
opengl is the next stepp....
I need the Xorg.0.log and if next displays correct 1024x600 then also Xorg.0.log from next - if next is also 800x600 then the Xorg.0.log from another linux, that is 1024x600
Posted 6 years ago # -
ty for the reply
here, by using the uploaded rootfs.gz, with the already slitaz installed (not a live) sli5
https://paste.fedoraproject.org/paste/W6vS~zEpNADACYPjuzBJ-Q/raw
https://paste.fedoraproject.org/paste/Vi~gtqN8AKpxcZN79KayPg/rawPosted 6 years ago # -
the xorg in next live was showing proper 1024x600 screen; xorg.0.log was on previous pages.
Posted 6 years ago # -
this bootline is wrong and you are still using vesa...
root=/dev/sda6 quiet initrd=/boot/rootfs22.gz screen=text
this is for booting the iso/rootfs.gz
title SliTaz cooking
kernel /boot/vmlinuz-3.2.98 rw root=/dev/null vga=normal
initrd /boot/rootfs.gzthis is for boot from installation
title SliTaz GNU/Linux (cooking)
root (hd0,1)
kernel /boot/vmlinuz-3.2.98-slitaz root=/dev/sda2Posted 6 years ago # -
i dont understand..
when i try to boot on another file, here the rootfs.gz you uploaded, i put it in the /boot with another name, i change the name in the grub to make it booting on.i always keep the original files.
but it's booting the rootfs you uploaded..
(and i made back the changes by setting intel in the tazx tool, which is using the vesa so, as you asked to do not modify xorg conf files...)
Posted 6 years ago #
Reply »
You must log in to post.