memaloc unable to alcoate memory
there was no other error code it was like I just hit enter on a blank command line
X -configure rebooted the computer ( I will never understand how this happened )
untill I have the system setup and configured I run as root only
of the 20 times I tried to boot it it only booted 5 times and it would not boot at all from the install disk I would get a kernel panic no init found
why did I try slack 12 I upgraded the hard drive and had to reinstall any way might as well update slack while I'm at
when slack-12 bombed out on me I pluged the old hard drive back in as a slave booted from knopics
and cp-ed the old install over to the new partion

next on my list
I found a new 250gig hard drive for $25.00 and just could not pass it up
it was marked as not working the store manager sed I could bring it back if I could not get it to work I knew that most computers over 4 years old would chock on 250gig and I fugered this is what happend to the last guy that bought it and it worked fine for me and I still have the OEM's warrenty
to boot

Have you looked at your PATH? Also, just had an experience similar to yours with a customer machine where everything was going flaky and it turned out to be questionable RAM. Also, did you use the appropriate utility to thoroughly test your HD before you installed?

In all fairness I installed 12.0 on a machine and had a few issues, mainly in the area of some of the multi-media apps simply not working. Of course, the beautiful thing about Slackware and Linux in general is that bugs like this are addressed immediately and if fixes are necessary they'll be available very soon. I'm about to substantially upgrade my everyday desktop and will likely return to 11 for the time being but will continue to work with 12.

just this morning i resolved my Slackware-12 problems, i just had to take my time and sort thru the new packages that were not part of slackware before Slackware-12 was released, no big deal really just a little time consuming...

Linux gnu 2.6.22.2 #1 Sun Aug 12 08:51:33 CDT 2007 i686 AMD Athlon(tm) XP 1600+ AuthenticAMD GNU/Linux

before Slackware-12 (slack9 thru slack11) i could install slackware with my eyes closed...

12 is the best Slackware distribution I've used to date!

i have pentium II - intel celeron 533mhz, 128mb RAM, nvidia riva tnt 2 g.card...
and EVERYTHING works excellent...

so, if i can use slack 12 on my computer that's 7 years old, rob should too on his...

Dig It !!
the only way your ever going to tack slackware away from me is to pry it off my cold dead hard drive OK

I had just spent 2 days trying to install wind blows on a
large HDD the windbloz installer disrespected the parttion
table and insested the HDD was 1 Gig larger than the BIOS
thought it was and would lock up every time
the OEM of the computer couldn't tell me witch of 8 files
to download so I could update the BIOS and maybe fix this
problem so the only fix I could think of was to go ahead
and install slack put a working file system on the windbloz
parttion then run the windbloz installer ( this did work with slack-11 )
I think I am far from being a slack noob the slack I'm running
now started as slack-8 it was moved acrosst 3 hard drives and
upgraded through all versions from 8 to 11
the libaraies and X have been rebuilt to match my CPU 4
times that's right this install has run on 4 computers
I have also installed slack on 9 other computers 5 desktops
4 laptops I even cramed slack-4 on to a 200 Meg HDD laptop
I have NEVER!! NEVER!! seen slackware fall on it's face as
badly as it did this time
this is like being let down by a close reliable frind
and lot's of people here think I have no right to bitch about this????

i installed slack 12 a month ago and it works great no problems at all instead of x -configure try xorgconfig

Sure. No argument from me:-) I've just found Slack to be a bit more responsive with at least 256 MB RAM.

It works for me.

In fact, it's the best release of Slackware ever, IMHO!

I agree!
Slackware 12 has much better hardware detection for me. There are a few differences with setting permissions in 12, but that is easily remedied.
Congratulations Patrick, this is your best effort yet!!

Well, of course you can, but considering so many people (including me) seem to find Slack 12 a good release working perfectly, maybe you should consider that your problems are related to your particular setting instead of bragging outright that Slack 12 is garbage, shouldn't you?
Anyway, first of all, consider that this release use 2.6 kernel, not 2.4 kernel like the previous ones. Maybe you should check if your system is well supported first, as since there won't be 2.4 kernels anymore in newer Slackware releases, it had better be. Personnaly, having X -configure reboot the whole system give me the feeling of a badly supported chipset, especially PCI support in this particular chipset. Try disabling ACPI, for instance : it's probably not well supported on your old machine.
Second, did you make a fresh install or did you upgrade?

of course that you have every right to express your opinion about slack 12, but bare in mind that it's also our close reliable friend, and we don't like someone to talk bad about our friends, especially because we don't have any problem with it including the installation process...:-)

i'm kidding, but have an understanding for our point of view, too:-)

good luck with you struggle!

Hi,

I've fresh installed Slackware® 12.0 several times. Some on bench/development systems to purposely break the install to see what happens. I've experienced problems that you wouldn't normally have. Some were my fault by omission but others were traced to kernel default setups. The probing for devices is still an area for Linux to improve. I'm not just talking about udev or HAL. Some of the post scripting could use some checking.

Sure, a lot is still due to manufacture data availability but that is changing daily. M$ can only stop that for a while. Companies like IBM are using Linux therefore the device specifications will be made available sooner than later.

Fortunately, Slackware® 12.0 as any Slack will allow a knowledgeable user to setup/modify or simply correct a problem with a little research on that users part. Even a newbie should be able to work through a problem if they prepare themselves with a little reading, be it .txt information or even looking at the logs for clues to the problem. Google Linux & LQ searches will generally get you information or help to solve most problems.

My personal thought is that 'PV' & team have done a great job. Sure you can please part of the people part of the time but not all the people all the time. Some one will always have an opinion that may or may not align with ours.

Slack On!

Another very happy Slackware 12 user here. I'm using it on a Dell Latitude that's easily 5 or so years old and things seem better overall under Slack 12 than they did under Slack 11 on this same laptop. Prior to Slack 12 I was distro shopping for a good fit for this machine and I've chosen (and decided to stick with it) Slack 12 over Debian Etch, Kubuntu Feisty, Fedora Core 6.

So far so good. My other laptop (newer Dell) is running SuSE 10.2 and between these 2 machines I feel I've got the best of both worlds. My XP desktop (former main system due to better hardware) has essentially been relegated to a slave box for my SuSE machine to fire tasks at and generally push around.