[SOLVED] Can't install Slackware64-current on my Phenom box
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Can't install Slackware64-current on my Phenom box
Can somebody help this old Slacker out? I just FTP'ed the Slackware64-current, made a boot DVD, and trying to install it on my Phenom system it doesn't see the SATA drives. It installs and runs just fine on a spare partition on my old Athlon64-X2 with all EIDE drives. I have both Slack 12.2 and Bluewhite64 on the Phenom running just fine. Is there something I'm missing here or should I just wait for 13.0 before trying it on my Phenom again? Thanks.
My first immediate thought would be "Which kernel are you booting with?"
It comes with (if I recall) at least two kernels, maybe 3, one of which is 'huge-er' than the other(s). It *might* be called 'hugesmp'..
I don't have the actual names of the kernel(s) because I only downloaded one of them, just to get 64-current installed, and after that, built my own kernel.
Use the Function keys on the DVD main boot screen when it first starts, to select kernels/other options.
Anyhow, make sure you're using the 'fuller-featured' of the two/three kernels, if there is such a one, and post back if that works/fails.'
Also, have you read the README's, Gotcha's, and ChangeLog, in case there's anything relevant to your situation?
Can somebody help this old Slacker out? I just FTP'ed the Slackware64-current, made a boot DVD, and trying to install it on my Phenom system it doesn't see the SATA drives. It installs and runs just fine on a spare partition on my old Athlon64-X2 with all EIDE drives. I have both Slack 12.2 and Bluewhite64 on the Phenom running just fine. Is there something I'm missing here or should I just wait for 13.0 before trying it on my Phenom again? Thanks.
What is the manufacturer and model of the motherboard?
It sounds as if your SATA controller is not supported in that kernel.
Can you give the output of "uname -a" and "lspci -vv" and "zcat /proc/config.gz | grep 'SATA'"
from the Slack-12.2 or BlueWhite64 system running on that box?
And which kernel of Slackware64 -current are you using? Specifically
what is the date of the ChangeLog from the ISO image you used?
I'm especially interested, because my server is 7 years old and I'm
considered Phenom when I build something new.
What is the manufacturer and model of the motherboard?
It sounds as if your SATA controller is not supported in that kernel.
Can you give the output of "uname -a" and "lspci -vv" and "zcat /proc/config.gz | grep 'SATA'"
from the Slack-12.2 or BlueWhite64 system running on that box?
And which kernel of Slackware64 -current are you using? Specifically
what is the date of the ChangeLog from the ISO image you used?
I'm especially interested, because my server is 7 years old and I'm
considered Phenom when I build something new.
The mobo is the XFX 750a SLI. Here are the results from my Slack 12.2.
uname -a:
Code:
Linux quadcore 2.6.27.7-smp #2 SMP Thu Nov 20 22:32:43 CST 2008 i686 AMD Phenom(tm) 9500 Quad-Core Processor AuthenticAMD GNU/Linux
Thanks, Sasha! You know ... you win some, you lose some, some get rained out.
I just had a 250G drive on my server, with 7+ years of photos since we moved
to China, plus the backup of three boxen on the LAN, and other data; that went
south on me. Had some bad inodes, and actually it turned out to be a lot
worse than suspected... was hoping only the filesystem was bad, but the
disk is basically trash. Thanks to poor electrical setups in China, and
the unexpected outages (UPS on all comps, but sometimes we're not here).
However, I was blessed! Lost only three files ... thunderbird-0.9 something
source file, that no one needs; one photo from the snow of 2003, which was
in another located because I'm the King of Entropy, and one other photo
which might also be elsewhere. It's name was too mangled to know.
That server is a machine I built in 2003, running Slackware-10.1 and a custom
2.4.31 kernel. I've been preparing everything for Slackware-13.0, which is
why I found the bad drive. So, new drives already bought, and this time I'm
thinking of RAID5 (or better). But, I need to replace that machine, because
everything else could go any time.
I don't know what I'll buy, but being an AMD fan, the Phenom seems to be
good 'bang for the buck'. The motherboard is important, and of course,
I'll buy an Asus.
Since this thread is [solved] for intents & purposes, hopefully I/we won't be accused of hijacking:
Just an FYI that I came across the other day when doing some Googling while trying to help another OP running an Athlon II X2 --
Apparently, there are a number of certain-dated X3 processors out there that are actually X4 (4 core) units but with one core 'disabled'. If you get the right CPU model# and/or date of one of these units, the 4th core can be unlocked, thereby producing an X4 for the cost of an X3.
I didn't really pursue the subject to death, as I'm not in the market for such a processor; but if I were in that market, I'd be looking into it out of curiosity if nothing else. And it's a matter of speculation (of course, what with rumor mills and all..) whether AMD "did this deliberately" or if they slipped up -- it's up to the reader to decide.
Anyhow, this all may be of no import to you, but I found the subject & resulting discussions I found via Google, rather interesting.
And with that, let's end our hijack now, and refer further discussion of this 4-core Phenomenon (heh, get it??! *ahem*..) over Here or at the link above (same place).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
@ Bruce,
