SliTaz Forum
You are not logged in.
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
Offline
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/raw
Offline
the xorg in next live was showing proper 1024x600 screen; xorg.0.log was on previous pages.
Offline
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.gz
this is for boot from installation
title SliTaz GNU/Linux (cooking)
root (hd0,1)
kernel /boot/vmlinuz-3.2.98-slitaz root=/dev/sda2
Offline
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...)
Offline
but when I look the the Xorg.0.log, I just can see, that there is somesthing wrong
[ 20.941] Kernel command line: root=/dev/sda6 quiet initrd=/boot/rootfs22.gz
root=/dev/sda6 is wrong
and then the lines
[ 21.761] (II) UnloadModule: "intel"
[ 21.761] (II) Unloading intel
tell, that you are using vesa not intel driver
can you add this line to your menu.lst
title SliTaz cooking with intel driver
kernel /boot/vmlinuz-3.2.98 rw root=/dev/null vga=normal
initrd /boot/rootfs22.gz
and then boot this
Offline
i'm gonna try;
just understand:
tazx, select intel driver ==> vesa/fbdev, no intel driver added to xorg conf files; not in RC5.
i'm gonna try for the root=/dev/null
Offline
just replaced /dev/sda6 by /dev/null :
kernel panic - not syncing : vfs unable to mount root fs on unknown block (0;0)
i knew i had to let this.. it's not about to boot linux without this
Offline
post your grub lines
Offline
title SliTaz GNU/Linux (Kernel 3.2.71-slitaz)
(hd0.4)
kernel /boot/vmlinuz-3.2.71-slitaz root=/dev/sda6 quiet initrd=/boot/rootfs22.gz
Offline
you have to add this to your menu.lst and boot this!
title SliTaz cooking with intel driver
kernel (hd0,0)/boot/vmlinuz-3.2.98 rw root=/dev/null
initrd (hd0,0)/boot/rootfs22.gz
and there must be vmlinuz-3.2.98 my rootfs.gz is with 3.2.98
and adopt the (hd0,0) where your /boot folder is.....
Offline
doing this just crashes linux at startup..
Offline
@ Kultex
Isn't there a mistake? If you boot from an installed Slitaz you will not use a initrd-line, will you?
And if you use this frugal install the first kernel line must be /boot/bzImage rw root=/dev/null nomodeset
I just booted from Live-CD on an older machine with this graphic card:
NVIDIA Corporation C51 [GeForce 6150 LE] (rev a2)
Without nomodeset I see a disturbed unuseful crazy screen, with it it works flawlessly.
Offline
@ michaelbischof
in your case it is clear - nomodeset forced the iso to use vesa instead of fbdev driver - some geforce cards dont work with fbdev. But to get full grafic power, you have to install the nvidia driver.
lm2 has a intel video card and I made him a rootfs.gz with intel drivers and I wanted, that he boots this rootfs.gz not his installed slitaz.
@lm2
maybe my rootfs.gz was damaged with up and download from wetransfer..
no more ideas - only try it with the normal iso - and try it with screen=text and tazx
because you can boot the normal iso.....
Offline
what do you call normal iso?
up to here on this thread i was dealing with the installed slitaz: rc5, and the only one time i changed was with the Next iso.
so i dont know what to do;
ps: on slitaz 5, when using tazx to install intel driver, yes, that puts vesa in the first card on the 60-device.
Offline
the problem with your installed slitaz version is, that I do not know what you changed - I just see in the xorg.0.log strange bootlines, I dont know what you mean with rc5 - I gess you mean RC3 - but rc3 is now nearly 3 years old and there are hundreds of changes.
The only possibilty I see is - you have to boot last slitaz rolling to text mode, get root, run tazx, get back to tux, startx manually and post the output of Xorg.0.log
and one more time, you cannot run tazx, when X is running with vesa
Offline
so i'm talking about rc3 yes, the 3rd RC of slitaz 5, sorry
i'm using slitaz 5 since two years now, i'm not gonna upgrade because it's enough well for me
so slitaz rolling means s5rc3? the HDD installation so...
i can try the text mode... to xorg.0.log experiment in few hours.
i always run tazx in command; when i put intel on the 60-device, xorg just doesnt launch; but i always have access to the tazx tool, even in command line
Offline
maybe its a matter of security? and not a matter of enough well?
and maybe we have now a new kernel and the packages you install now dont fit to the old packages from RC3?
and if I dont see screen=text in the Xorg.0.log as bootparameter, no more help
Offline
so here if i understand well you want the xorg.0.log of each :
slitaz 5 rc3 booting in liveusb
slitaz 5 on installed hdd
slitaz next
?
with for each one, the screen=text, and do i have to do a tazx for installing intel driver on taz5? do i have to check if it's intel or vesa?
Offline
btw i just booted on liveusb slitaz 5Rc4 20180211 with screen=text in grub line (then enter right?)
==> directly to the lxde desktop, it doesnt boot directly in shell/tty
Offline
only last rolling iso - nothing else
Offline
yes, so :
i put it on usb stick
i boot on it
i tab just after language
i add screen=text
i wait the shell or desktop
i give you the xorg.log
i just did this, it goes on the lxde desktop
Offline
@ lm2,
In Rolling ISO, you have a first screen for language then a second with core, web boot...
On this second screen, select core, hit [Tab] and add screen=text at the end of the line. SliTaz will boot in text mode.
Offline
@ceel thankies
here it is, for rolling of taz5 :
https://paste.fedoraproject.org/paste/JJ3gJb2l6Ftsm~Zhx3ysNg/raw
https://paste.fedoraproject.org/paste/ChQS0ld7z12RTiJOh9DYXA/raw
staying at your disposition to solve this..
Offline
please explain what is xorg.0.log and xorg.2.log
and it would be nice to have the Xorg.0.log from next - it is not in former posts
and for the future please use only screen=text no home=
Offline
[ Generated in 0.020 seconds, 8 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]