What's the lowdown on 12.0? - Page 3

onebuck · 07-21-2007, 10:29 AM

Quote:

Originally Posted by sombragris

I think this is uncalled for. I, for one, read all the documents you mention, including "Changes and Hints" and the release notes. I got my ISOs from BitTorrent, checked the MD5 sums, and verified the burns afterwards; and I am still having stability issues.

However, I think these might not be Pat's fault, but they can be traced to flaky Savage X11 drivers instead. But they are serious; I cannot use runlevel 4 anymore, and therefore my wife will have to learn yet another way how to access her desktop.

I also had serious trouble with my printer (who worked fine in Slack from versions 9 thru 11) despite carefully following the instructions of CHANGES_AND_HINTS.TXT. They only went away after I ditched my upgrade and did a clean install. Again, not because I did not read the docs, but despite that.

I, for one, do not blame the distro. And you, please, do not blame the users. I will "complain to the upstream maintainers" as Pat said; and you should admit that there are some unfortunate problems that are not Slack's fault.

Hi,

Quote:

Originally Posted by sombragris

I, for one, do not blame the distro. And you, please, do not blame the users. I will "complain to the upstream maintainers" as Pat said; and you should admit that there are some unfortunate problems that are not Slack's fault.

I was making a general statement. I stand by that statement. If that offends you then that is your problem. Most of the problems are indeed 'user' related. The user fails to read docs or investigate the problem properly therefore the resultant is a non-functional device or system.

You are going to complain to WHO? I have nothing to admit relative to your statement(s).

As for the 'user' problem(s) then an example;

Quote:

Originally Posted by sombragris

I also had serious trouble with my printer (who worked fine in Slack from versions 9 thru 11) despite carefully following the instructions of CHANGES_AND_HINTS.TXT. They only went away after I ditched my upgrade and did a clean install. Again, not because I did not read the docs, but despite that.

You should have investigated what the problem was with the install/upgrade that created a printer that did not work, instead of just clean install of OS. You would then have the reason for the failure.

Is this not a 'user' problem? Yes, it was you as the 'user'. But solved? No! Corrected? Yes, via by chance with a new clean install.

If this offends you then as stated; "Your Problem".

As for your stability problems, what are they? Hardware or software?

Quote:

Originally Posted by sombragris

However, I think these might not be Pat's fault, but they can be traced to flaky Savage X11 drivers instead. But they are serious; I cannot use runlevel 4 anymore,

What have you looked for? Any errors, dmesg, syslogs or xlogs?

hitest · 07-21-2007, 11:29 AM

Short answer for me.
Slack 12 is stable, rock-solid. I've been compiling from source, haven't noticed any issues.
Thanks PV for the excellent OS!!

arubin · 07-21-2007, 06:04 PM

I have gone back to Slackware 11

I had some minor problems with 12 because I did not read Changes and Hints carefully.

I had a minor problem with fonts which was easily fixed with the help of LQ. It has been explained to me here that the problem is a not a bug (though I do not understand why it isn't).

I had problems with crashes of 12 which were almost certainly due the latest Nvidia driver and not a Slackware problem.

I notice that some people are having problems with java on Slackware 12. I have not noticed any problem myself but I use Java a great deal and this would be a worry.

At the end of the day I was very happy with my 11 installation and I just did not see any advantages to me of going to 12. Perhaps I am missing something. I still have the partition with the 12 installation and am able to dual boot. If I want to use 12 I can use it but I am happy with 11 and that is what I am using.

hitest · 07-21-2007, 06:55 PM

Quote:

Originally Posted by arubin

I notice that some people are having problems with java on Slackware 12. I have not noticed any problem myself but I use Java a great deal and this would be a worry.

I need java to connect to my company oracle data base. Java works just fine for me on Slack 12; I haven't noticed anything.

north49er · 07-21-2007, 10:52 PM

Compared to slack11 2.6kernel, the sound, gxine, xine in slack 12 works right out of the box. Even mr. potatohead got his voice back. The only nit so far is static acrosslite1.2 doesn't work because it can't locate a libstdc++.so file. By the way, it looks like libstdc++.so.6 symlinks to a non-existing file (maybe a bug).

uselpa · 07-22-2007, 04:48 AM

I upgraded from 11.0 to 12.0 without major problems. There are some packages such as MPlayer, frozen-bubble and some KDE-related stuff that had to be recompiled but that's about it. Also, some light tweaking to the fonts had to be done. There's a few details on my blog.

The result is completely stable, all Java programs work well (such as ThinkingRock and FreeMind) as does my hardware. No complaint here.

rkelsen · 07-22-2007, 05:32 AM

Quote:

Originally Posted by north49er

By the way, it looks like libstdc++.so.6 symlinks to a non-existing file (maybe a bug).

Code:

$ ls -la /usr/lib/libstdc++.so.*
lrwxrwxrwx 1 root root     18 2007-07-03 07:06 /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.8*
-rwxr-xr-x 1 root root 906580 2007-02-15 07:39 /usr/lib/libstdc++.so.6.0.8*

Looks like you must have done something wrong.

uselpa · 07-22-2007, 05:50 AM

Same here:

Code:

root@slackw:~$ ls -la /usr/lib/libstdc++.so.*
lrwxrwxrwx 1 root root     18 2007-07-06 22:44 /usr/lib/libstdc++.so.6 -> libstdc++.so.6.0.8*
-rwxr-xr-x 1 root root 906580 2007-02-14 21:39 /usr/lib/libstdc++.so.6.0.8*
root@slackw:~$ vlpcheck which libstdc++.so.6
libstdc++.so.6
  part : /opt/openoffice.org2.2/program/libstdc++.so.6.1
           openoffice.org-2.2.1-i586-1kjz
  part : /usr/lib/google-earth/libstdc++.so.6
           google-earth-4.0.2723-i486-1kjz
  part : /usr/lib/libstdc++.so.6.0.8
           cxxlibs-6.0.8-i486-4
           gcc-g++-4.1.2-i486-1
  full : NO MATCH

Check your cxxlibs and gcc-g++ packages.

Crushing Belial · 07-22-2007, 10:51 AM

I had some performance issues with it, specifically related to Linux 2.6.21. I'm still shocked Pat V went with version 2.6.21 which contains a lot of brand new untested features. Even Andrew Morton admitted it was a bit buggier than it should have been.

http://www.linux-watch.com/news/NS8296942554.html

sombragris · 07-22-2007, 05:04 PM

Quote:

Originally Posted by rkelsen

To the people who are experiencing problems: Are you using one of the default kernels? Or do you compile your own?

In my case, I am using the default generic-smp kernel that came with Slack 12.

sombragris · 07-22-2007, 05:28 PM

Quote:

Originally Posted by onebuck

You should have investigated what the problem was with the install/upgrade that created a printer that did not work, instead of just clean install of OS. You would then have the reason for the failure.

Is this not a 'user' problem? Yes, it was you as the 'user'. But solved? No! Corrected? Yes, via by chance with a new clean install.

If this offends you then as stated; "Your Problem".

As for your stability problems, what are they? Hardware or software?

What have you looked for? Any errors, dmesg, syslogs or xlogs?

Onebuck, thanks for taking the time to reply. Why is that I should have investigated the problem? I did carefully follow the docs; if the printer borked even despite that fact, why is that it must be my problem and that I should have investigated?

I tried to investigate; but I had no answer; and the problem shouldn't have appeared because I followed the upgrade instructions carefully.

So, upgrade by carefully following the docs, get burned, try to solve the problem and come out empty... and then it's all the user's fault? That is certainly strange. Please stop blaming the users.

As for the stability problems, I said that the culprit might be some flaky Savage drivers in Slackware 12.0's Xorg. I arrived to that conclusion after looking at dmesg, syslog, messages, and Xorg.0.log. The Xorg.0.log registers a signal 11, and produces a traceback, under some reproducible circumstances.

Pat said... "complain to the upstream maintainers". That is good advice; I intend to report the bug to the Xorg people.

sombragris · 07-22-2007, 05:30 PM

This was accidentally posted in duplicate; please disregard. My apologies.

rkelsen · 07-22-2007, 07:00 PM

Quote:

Originally Posted by sombragris

In my case, I am using the default generic-smp kernel that came with Slack 12.

What happens when you compile a custom kernel?

SCerovec · 07-23-2007, 09:32 AM

This night I went to compile that custom 2.6.22.1.
The sole reason:
softmac802-11 in the kernel (finally)
So i downloaded it and extracted to ~/src/
in a terminal:

Code:

$ cd /src/linux[tab],[enter]
$ make xconfig

then I loaded the /boot/config-generic-x-smp
and started to disable modules taht I know I never need :-)
I did increase the machine to AMDopteron/hammer (I use a 64 X2 3600+)
after the third compile it did work - #1 didn't run so i disabled driver/virtualisation ...
Now i have the proprietary nvidia module, the rt2x00's rt61pci on that 12.0
for the sake of stability i didn't use preemption regarding rt2x00's advice
still to go:
VMware server or VirtualBOX...
So 12.0 is as slack as allways, 11.0 - 12.0 made a leap and we needed some time to fillow up, as allways...
All in all 12.0 is all true Slack as a Slack could be.
And still damn fast...

onebuck · 07-23-2007, 02:38 PM

Hi,

Quote:

Originally Posted by sombragris

Onebuck, thanks for taking the time to reply. Why is that I should have investigated the problem? I did carefully follow the docs; if the printer borked even despite that fact, why is that it must be my problem and that I should have investigated?

The system is yours for one. To investigate a problem is to find an answer or least an idea as to what could be the problem. We are not sitting beside you, if we were then things would be a lot simpler to solve. If the printer 'borked' then what does that mean? My crystal ball is cracked therefore the information is not discernible. Not to be smart but you are the one sitting in front of the computer and I can't see everything that's going on. You need to provide as much detail about the problem. 'Borked' does me or anyone no good.

Quote:

Originally Posted by sombragris

I tried to investigate; but I had no answer; and the problem shouldn't have appeared because I followed the upgrade instructions carefully.

So, upgrade by carefully following the docs, get burned, try to solve the problem and come out empty... and then it's all the user's fault? That is certainly strange. Please stop blaming the users.

This is Slackware! Yes, it is your lack of understanding for 'Your' system an the needs to use the software for that system. Therefore you need to understand all aspects for the setup for your system. Things are not always that vanilla for any OS. I have my opinions and I stand by the fact that most problems are related to the 'user' and not the OS, be it 'Slackware' or some other distro.
Sure there are times when a combination of hardware & software can cause some configuration problems. But still that requires the 'user' to get involved to solve or adjust the environment to get things functional. That will require the 'user' to get outside help or information to make the adjustments if they are beyond the scope of understanding for that 'user'.

Quote:

Originally Posted by sombragris

As for the stability problems, I said that the culprit might be some flaky Savage drivers in Slackware 12.0's Xorg. I arrived to that conclusion after looking at dmesg, syslog, messages, and Xorg.0.log. The Xorg.0.log registers a signal 11, and produces a traceback, under some reproducible circumstances.

Pat said... "complain to the upstream maintainers". That is good advice; I intend to report the bug to the Xorg people.

Good! I'm sure they would appreciate the feedback.

Instead of the drivers, try the vesa framebuffer to see if that indeed is the problem. Is the 'Savage' agp or pci? If pci try a move to another slot to change the irq and prority.

One other question, where did you get your install cd/dvd? Have you tried another download site and verify you have valid iso(s)? And valid cd/dvd disks compared to the original iso?