Geez, it looks like I'll wait to upgrade as lots of folks seems to be having problems with 12.0. Did Pat get ahead of himself?

I don't think so, masonm:-)
I've been running 12.0 for a few days now and I find it to be more stable than 11.0. Pat did a good job, the 2.6.21.5 kernel runs very well indeed.

masonm,

It's all good on two "Slackware" boxes at my house.

Let's make this a survey.

I wonder if most of the problems are with upgrades due to all the changes one must do. Also, "FOLLOWING THE INSTRUCTIONS CORRECTLY" with the amount of changes one must do, "MISTAKES" can happen. The fresh install went perfect, and I had already upgraded one box (from 11 to 12) but flushed it just to make sure there wasn't something laying around that may cause me problems later on.

i've got slack12 for 2days with not a single problem. I haven't even recompiled the kernel. just did the usual install and config the basics... easy as pie. maybe I just got lucky?

it seems a lot of the 'problems' have perhaps to do with the migration to a new Xorg, and hal + dbus...

us slackers are still getting used to these things yeah?

I had a few programs fail to install, but I checked the md5 from the burned disk, the hard disk and the site and they were all different. So I'm assuming I either got a corrupt burn or a corrupt dled. Even though I had these problems slackware still loaded fine, and what's more was fast as hell! It completely took me by suprise, it was the total opposite of what I was expecting. I ran into a few problems, it wouldn't let me access the root hard drive, it refused to let me use my soundcard, two problems slack 11 never had. So I'm assuming it's due to a bad burn or bad torrent or both.. So I'm downloading the torrent again now and I can't wait to reinstall it!

Well... There have been a *lot* of people running what was essentially "almost 12.0" (-current) for a while now with little to no problems, and countless others that are having no problems with 12.0 as is.

There is one (minor) issue with HAL (which I detailed in a previous post here on LQ as well as on alt.os.linux.slackware), and even that is not really a Slackware problem - it's a dbus issue. The only reason it's causing a problem is the attempt to make it "just work" without user intervention.

Otherwise, I only recall one other legitimate bug (with cdparanoia) here or elsewhere. That's not to imply that there aren't any, and there are probably still some pending cases that are unresolved, but so far, the vast majority of the issues I've seen here and elsewhere have been misconfiguration by users, usually as result of failing to read the CHANGES_AND_HINTS.TXT file.

Since I mentioned it, the cdparanoia issue isn't really a bug, as it does work, but it will be really slow for people who have scsi/sata optical drives due to the fact that the 2.6.x SG_IO patch was not applied to the build for 12.0. To further complicate matters, the build script for cdparanoia in the 12.0 sources is not a standard SlackBuild script, so it's not quite as easy for a user to build a new package with it unless they don't mind spamming their system (as the cdparanoia Makefile does not have DESTDIR support). I did some work on that earlier tonight, and the result is at http://slackware.com/~rworkman/cdparanoia/

I'm currently running one 12 box. Fresh install. Everything is fine. Install went without a hitch.

I do though have a weird error/notice message during boot, but I suspect its got something to do with the huge kernel trying to do some mumbo-jumbo with non-existant hardware. It doesn't seem to affect anything.

So far Slackware 12 seems like a winner..

Upgraded an AMD K6-II from Slackware 11 to 12 this afternoon with no problems. Haven't configured Apache2 yet, but I'll get to that tomorrow. Seems to be as slack as ever.

Please paste that error message here.

Good :-)

Looked at upgrading from 11, but there was way too much work to do. Installed version 12 RC1, upgraded through slapt-get through to final, and did a clean install of 12 final just for kicks with no problems whatsoever.

That error during boot mentioned earlier is probably the system trying to load the USB modules, which are already compiled into the "huge" kernel, as mentioned in CHANGES_AND_HINTS.TXT. If you add "ohci-ecd" and "ehci-ecd" to /etc/modprobe.d/blacklist, the errors will go away, although they don't hurt anything (except your eyes).

Checkinstall is MIA (and it looks like the developer's site's been "slackdotted" :-). Looking forward to getting that back.

Odd that bittornado was included in extra/ but not its wxPython dependency. Figuring out how to compile/install wxPython was not fun. (Sure, you could always just use it in "ncurses" mode.)

A fresh install of 12.0 here went without a hitch.

Slick, fast, up and runs fine. X even works decently except for slight flicker (CRT monitor) (now to run xorgconfig which rids it of the flicker 'cause gets it the correct driver to it and higher refresh rates)

Pent 4 socket 468 (or is it 478) motherboard Intel 2.8 GHZ Northwood CPU, 3 GB ram | motherboard is a rocking, Shuttle AB60R, keeps on rockin and rollin

So far it's using huge_smp though. I didn't yet see how to switch to generic instead.

Appears I need to install the generic then uninstall huge except for the headers.

More homework to do!

During boot I get some weird messages appears like the ones Pat mentioned of somewhere (in one of the text files in the slackware-12.0 folder) he said about huge and that switching to generic stops those messages (if my box will run on generic and I bet it will).

Alan.

No hassles here

just install and GREAT shiny new slack.
No problems as of yet.

Bonus : Plugging in a pen drive and seeing it pop up ready to use is also a +100, This in terms of getting other users to use linux will be a plus as generally local users dont want to have to tinker around just to open a simple usb stick.

Also Nvidia latest drivers installed flawlessly without a kernel compile. ++

TL_CLD just comment out a few options in /etc/rc.d/rc.modules
and the errors will go away.

Keep on slacking

;-)

Done so in another thread: http://www.linuxquestions.org/questi...41#post2812641


Thomas

Slackware 12.0 fresh install -> everything goes perfect.

I played with mkinitrd, switched kernels (huge > generic > nosmp), switched video drivers ("vesa", "ati", radeon", /extra/*ati, fglrx) -> not even a single problem, everything just works. VMware Server works (with any-to-any patch), wine works, my son's prefered games works, multimedia apps works and so on.

Great job indeed for Pat and his team!

It seems to me Slackware 12.0 runs much better than Slackware 11.0. I have no time for compiz and for my webcam, but I'll have.

I don't think so.

Slackware 12 is rock solid for me thus far.