[SOLVED] Slackware appears to fail to recognize Intel Xeon E5-2690
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Slackware appears to fail to recognize Intel Xeon E5-2690
Hi.
I tried to install Slackware 15 on a server that has Intel Xeon E5-2690, under Oracle VirtualBox 7. The error message was that this needed a 64-bit system.
OSs that successfully handled an install were Debian12, SuSe, Fedora39, sidiuction, ubuntu23, and manjaro, all currently running successfully.
Slack has that in common with Haiku -- they both issue the same message, as does gparted.
I searched "Intel Xeon E5-2690" here and found nothing.
Suggestions? Thanks ... cheers makyo
( Data from inxi -c0 )
CPU(s)~2 Octa core Intel Xeon E5-2690 0s (-HT-MCP-SMP-)
speed/max~1200/3800 MHz Kernel~6.5.0-18-generic x86_64 Up~2 days
Mem~18834.8/225477.8MB HDD~8386.0GB(0.0% used) Procs~853
Client~Shell inxi~2.3.0
Distribution: ChromeOS,SlackWare,Android and Lubuntu
Posts: 68
Rep:
Could you please provide us with the Make and model of your machine? This will help us be better able to locate resources such as manuals provided by the OEM and which function key that it is required to be pressed BIOS set up utility.Secondly could you please provide the LQ community with the necessary log files which are most commonly found in the /var/logs folder.
This is the data from command lshw on the host running Ubuntu 22, through CPU 1 (of 32). There are 2000+ lines in the full report. What specific log files do you desire -- there are 60+ log files. Please remember that the slackware is booting into a VM under Virtualbox, so the second listing is from the first part of /var/log/installer/hardware-summary for a successfully installed VM of Debian12. Today Solaris was successfully installed as a VM on this host. ... cheers, makyo
The above ubuntu machine is running on a 64-bit CPU as you in the CPU flags have "lm".
However, you have one more level to consider: The virutalization provided by virtualbox. From the point of the guest operating system it does not matter much what kind of hardware is being used by the host operating system. The guest operating system only sees the virtual CPU and PCI devices provided by the virtual environment.
Is the above Ubuntu running as the host or in a virtual environment? As it has a VMWare VGA adapter it seems as if it could be running in a virtual environment. Did you configure your Slackware virtual environment the same way as you configured your Ubuntu virtual environment?
If you for some reason would prefer to give your Slackware virtual machine a 32-bit environment only there are also Slackware for 32-bit intel compatible machines.
I also guess the slackware guest is not configured correctly. Make sure in general it is configured for linux 64 bit. Vboxmanager does automatically detect and configure most distributions but not slack.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.