as I thought - nothing changed

strange errors on older computers
(55 posts) (9 voices)-
Posted 13 years ago #
-
so Christophe, for me remains only the discussion you had with Antoine about "-O2" and "-Os"
- next time I will save the IRC chat....
just as idea one more time - http://en.gentoo-wiki.com/wiki/Safe_Cflags
Posted 13 years ago # -
Yes I know... -Os was my first intuition... this means rebuild all the distro...
IRC chan is logged:-> http://irc.slitaz.org/2012-03-05
Posted 13 years ago # -
sorry I have no idea, what this means - is it possible to try this on a local machine... - like godanes tank iso?
Posted 13 years ago # -
It means rebuilding all packages = ~72H of compile on Tank and one night to sync mirror... Yes you can rebuild packages from tank-dvd but will take some time :-)
Rebuild all slitaz with -O2 means quiet a few more Mb on core, since -Os generate smaller binaries. Before to take the decision to rebuild everything, I'm compiling Xorg with -O2 on my machine, will do an iso and let you test it.
xorg with -Os = 1 Mb compressed
xorg with -O2 = 1,2 Mb compressedPosted 13 years ago # -
So here is an ISO with Glibc and Xorg build with -02. I did a gtkonly flavor since it's smaller and faster to download and works like core but without any installed GTK applications.
Posted 13 years ago # -
sorry - same error...
and just a thought.... would it be a possibility, when Slitaz goes really i686 and the libre branch keeps compatibility with the rest? But there must be a isos with working repository....
Gokhlayeh how far are you? - the problem in libre is wireless, but compat-wireless compiles fine..... and I think, those people, who work with this ancient boxes are able to deal with.
And I can build two different SliTaz-Ola versions
Posted 13 years ago # -
I dont know why you say "when Slitaz goes really i686"... it's hours an hours I try to fix your bug, did many iso... And as we said many time libre use same ARCH and value to compile = i486. The -mtune=i686 optimisation is also in libre. SliTaz will not go i686 because we want to work on old hardware and be generic.
I also booted SliTaz on an old K6 today and no problem so it's not with all old machines.
Anyway, I did a last iso with Xorg and only the fbdev driver since vesa and geode crash. Also one more test you could do is boot a core with the option screen=text to see if it boot until the end. I realy would like to fix that Tom!
Posted 13 years ago # -
Hi Christophe,
sorry it did not change anything
let me first answer, why I wrote this - because I feel responsible for your time. I mean this bug was eating a lot of my time, and I do not want, that it eats a lot of your time. Sometime its necessary to step back and think different.
I have the problem, that I am very back with my work - I have to cut my radio-play, I have to prepare some tourneys and I will not be home from Friday morning for 2 weeks. So I cannot test anything.
And xorg is not the problem - because it would not work, when I just change glibc-base. And its also proved by the fact, that I get exactly this error in SliTaz-Libre, when I just install glibc-base from RC2. So there is no problem in xorg.All I was reading about this error is described, that it creates these "Illegal instruction" errors. And these errors makes different programs to crash. And all I was reading points somehow to libc and the problem seemed to start with the update from glibc to glibc 2.12.2.
This would also explain, why we have this problem since cooking from Mai, because in march cooking glibc-base is still 2.11.2.So I dont know, how to continue - perhaps one thing would be to add NOPL Patch to the kernel
http://marc.info/?l=linux-kernel&m=126748102722641&w=2
the other possibility seem to be rebuild evrything with -O2, because this seem to be the secret of SliTAz-Libre
Posted 13 years ago # -
Obviously you haven't been paying attention... That version pankso gave you that you CONFIRMED didn't work used -O2 compiling with Xorg and Glibc - pretty much the base that everything needs to work. Compiling with -O2 isn't a magic cheat code that makes everything magically work and I'm pretty sure it's not the secret to SliTaz Libre. Obsessively trying to force pankso to compile everything with -02 JUST so he can prove to you it doesn't work is just waste of his time. It's also delaying the release of SliTaz 4 and not allowing us to solve your problem because you refuse to consider other causes. Just accept that you have the wrong end of the stick and move on.
I think the reason Libre works is because it uses a completely Libre kernel rather than Linux kernel itself. It lacks certain code that is present in the main branch of the kernel and that's why it works. As simple as that. All we need to do is figure out what was removed from the Libre Kernel to make it work.
Posted 13 years ago # -
T@rixar_za I do not want to force anybody to to anything. I would like to find a solution, that eats as less time as possible.
Posted 13 years ago # -
and Trixar its not the kernel, because I described, that I could replace the libre-kernel with the kernel form RC2 and it still worked without any problems
Posted 13 years ago # -
Boys and girls!
Whatever your final decision will be: a Distro without an Xserver, which immediately greets the user after booting is something ridiculous.
Now, today, it is like this:
I boot from a fresh cooking, come into the text mode. Startx fails, lsmod shows that nouveau is up. So ,,tazx" => some minutes, I opt for ,,nv", some seconds. Then
#/etc/init.d/slim start
startx
, nice, looks good - but for me. No way to recommend such a thing to any non-linuxer.
Ach, I forgot: this functions only with Internet-access. With a CD-boot and no connection yet and no idea how to get it running no help.
Ok, for cooking this may work for some time. But for a real thing it is bizarre. With all respect for matching bleeding edge technology - a functioning Xscreen must be there.
Similar with networking - this functions easy out of the box (except with unusual very old hardware) or we are members of a minoritary sect.Posted 13 years ago # -
Eh, it works fine on my old PIII.
Also, am I missing something here? You replaced the kernel with the libre-kernel and it works. Yet the kernel is not the problem? oO
Posted 13 years ago # -
and what is a PIII? its i686 and I said it effects only non i686 CPUs - sorry please read carfully.
and what are you missing? Why should I replace RC2 kernel with libre kernel , when I get the error, when I just change glibc-base in libre and on the other hand dont get the error any more, when I change glibc-base in RC2
Posted 13 years ago #
Reply »
You must log in to post.