Neither slackware 14 nor salix will run on my new hardware
I run Mint 14, 64-bit, without problems on a new machine with the following specs:
The Problem Two linux OS will not run properly on my machine:
Symptoms:
Question: What element, common to both above-mentioned linux OS, might be responsible for this problem? Many thanks and big respect in advance to anyone who can shed some light on this for me. PS (holding myelf at the ready to re-install everything, since with last install I tried the option of a GPT Partition Table, instead of the straightforward option of Bios, which now means I can't "see" my slack files from my mint install, making it hard for me to produce the kinds of things one would need to really diagnose the problem: ie: var/log/xlog.0; lspci -vnn output; lsusb output etc, etc; though, if someone reading this would like to see a bit of history to this, including xlog.0 and lspci output, please go to http://www.linuxquestions.org/questi...tx-4175465855/) ** using any and all of the available DE, from KDE to flux, produces the same problems |
Hi, I have an i5-3550 and have no problems. Perhaps our differences will highlight the problem that you are having.
I use traditional bios. I use nvidia graphics. After reading your other thread I would tend to agree with them that the problem is with the integrated graphics. Searching the forum pulls up some useful threads, the simplest potential fix can be found here samac |
You don't state why you use a full blown gui when you don't need to. You get the same problems with Salix as in Slackware (Full blown gui ?) I assume Archbang and Mint run fine so it is not a hardware problem. Therefore problem IS with the software and providing you have i5 drivers (see below) possibly lies in the components of X server which are used for the two which don't work properly and/or don't work together with a particular package used in conjunction. As an experienced user your only GUI requirements are a Window Manager, File Manager and Terminal Emulator and as a Slackware user you are perfectly capable of setting this up properly provided you can find the right combination of packages and they are available. So I would try:
1: A minimal Slackware setup using Fluxbox, Thunar and Rxvt with just the minimal X server BUT using GDM instead of XDM or KDM (Fluxbox seems to work best with GDM but that is just an opinion). So you just need Xorg, GDM, Fluxbox, Thunar and Rxvt. That's it. It should narrow down any possible causes of the problem if it still occurs to one of those items and in fact probably just some aspect of the Xorg packages. This is probably a reinstall. If this completely fails to solve anything at all then just out of curiousity I would try 2: A minimal network installation of Centos 6 with again the same setup as above, Xorg, GDM, Fluxbox, Thunar and Rxvt. This RHEL clone is very stable and the setup above is about as fast as you can get. Not that you probably need it but there is a guide to installing this at http://minimallinux.blogspot.com I have run this on a variety of machines without any drama whatsoever and I would not expect to have any problems with any of the hardware you are using. Does Slackware have drivers for i5 cpu ? Centos does, some notes on it http://support.reliablesite.net/KB/a...e-i5-3550.aspx The above seem to be a reasonable approach if you haven't already solved the problem. All the best. |
Nice idea and much appreciated.
One major problem looms large: i quote from your highly readable tutorial: "Make sure you have an ethernet connection as although there is some wireless support, it is not guaranteed. Boot the disk taking the default option of install or upgrade existing." I'm using a usb dongle to connect wirelessly to internet. But I'm looking into your other suggestions and your frugal approach to the whole thing interests me, though I must say I'm rather keen on seeing the full power of KDE before dropping my bags and making my final home. thanks again |
You should still be able to load the wireless drivers. If samacs suggestion is not it, then it has to be something in the Xorg/Kde unless BOTH Salix and Slackware are short of i5 drivers.
I would try first suggestion though, you obviously prefer Slack and are able to use your wireless with it, so if you cant fix the KDE you might at least be able to get the Fluxbox/Thunar/Rxvt thing going providing its i5 compatible. In fact now I got on the sublect I might try that on a spare machine. There is LinuxQuestion thread on it also. |
That link by Terminator3000 suggests that the BIOS version may be a factor. Is your machine using the latest available BIOS?
|
I would also install the latest video drivers (probably Intel ?).
|
Just an idea. I have a couple of Intel-based Dell desktop PCs that won't boot Slackware unless I build an Initrd and configure the generic kernel before the initial reboot.
|
Quote:
|
Quote:
Edit: that just shows my profound ignorance and confirms my new-born status (premature, on life-support): you are suggesting that slackware 14 might not have the driver support for my in-built video card , right? But wouldn't the fact that the motherboard is released before the release of slack14 put this question to rest? |
Quote:
My machine uses megatrend american dual bios/uefi. I have the setting for "Legacy Only" set to on, out of a possible 3 choices:
I don't think it is the very latest, as the release date is 8 months old. Here is output for Code:
dmidecode Code:
# dmidecode 2.11 |
Quote:
I'm still waiting to receive, process and organize all these responses before making a move. |
Your BIOS version is F12, with the latest being F14 (changes to improve USB device compatibility). I expect that the cause of the problem is not the BIOS version though, as the F12 version appears to be the next to last stable version. I would _not_ advise trying a BIOS upgrade at this stage.
Looking back at the original thread http://www.linuxquestions.org/questi...tx-4175465855/ , I am unclear on whether you have tried the libdrm and intel driver packages from /testing in Slackware 14.0 |
Quote:
|
If I was to take a final shot seeing as everything needs to be digested (which means that some of the less labour intensive suggestions have maybe not been tried) and assuming we dont think it is a motherboard/graphics drivers issue then I would go with the minimal install Fluxbox logging in with GDM. With that you could even cut out xorg completely and use Xvesa. I know it is not KDE but sometimes it is best to start light. More checking on the driver issue is probably needed though.
|
Quote:
After weeks of trying to get Slackware running, I am about to give Archbang another go, as I know it runs quite sweet on this machine, and see Slackware as a destination to work towards. |
Quote:
|
Hi textillis.
Are you trying Slackware 14 or Slackware-current? Many months ago there were a number of threads on this and other forums about issues with the Ivy Bridge processors with integrated graphics not being supported by older kernels. The kernel and drivers in Slackware 14 are pretty old, but the kernel in slackware-current is up to date and works great with the latest processors. I'm running current on an i5-3570, using the integrated graphics, and I've had no problems. If you don't want to make the switch to the current branch, consider updating the kernel in Slackware 14 to one of the 3.8 or 3.9 kernels. - Lirey |
THanks to all who responded!
Quote:
It makes sense and this post has finally nailed it for me: that is what I'll do: update the kernel. One final question -which will show what a complete babe in the woods I am here, trying slackware - would you please tell me the code that I need to enter at konsole so as to effect the update of kernel? I need to be absolutely sure I'm right so that, within my system, with a broken gui, I will not run into any unforseen problems, when I am this close to getting started. Many thanks. Thanks to one and all for your generous and timely and informative input! |
Quote:
Slackware doesn't provide GDM, so perhaps you should reconsider recommending its use. |
Quote:
If you do this, consider using the -j option to make in this Quote:
If you thinking of upgrading to Slackware-current, then look at this. http://docs.slackware.com/howtos:sla...ystemupgrade?s[]=kernel&s[]=upgrade Alternatively, get a Slackware-current iso, and reinstall. |
Leaning on the everlasting slackarmoury ....
Quote:
You have been A1 in your help Allend. I think I'm coming close to joining the choir of slackers, "leaning on the everlasting arms" of slackware! |
Mr Cranium, I was under the impression this was not actually a question about Slackware, and a closer examination of the thread shows that I am correct. The question is about an i5 machine which is running no less than FOUR distributions, one of which is admittedly Slackware. The other malfuntioning OS is Salix. There are two other OSs running correctly.
I enter into these discussions if I feel I have some valid contribution to make which I believe I have. So there is no GDM in Slackware ? I quote from the Slackware installation page Slackware will by default look for the availability of GDM I rarely use Slackware but that is not to say I can't, it is not difficult to use Slackware, just difficult to find all the informaton in what remains a fairly dated and idiosyncratic distro with average support and a cult following. Regular users of course get used to where it all is but this alone does not make them genius's. I am currently installing it on a spare machine I have and I do not anticipate any problems with it. But you never know. I sincerely hope you dont break any bones when you detach yourself from the high horse. |
Cheers, and good luck with slackware installation
Quote:
I'm going to follow Allend, you (obliquely) and others in updating the kernel so as to thereby update driver support for my inbuilt graphics card. Cheers! and good luck with the slackware installation. |
Grub in other OS not picking up newkernel in Slackware's lilo.conf
Quote:
The process went almost without hitch, but finished with three warnings: Code:
I have a fresh problem arising out of this process, which i'll make the subject of a new post ... phew! |
Quote:
In your /etc/lilo.conf you can add 'LBA32' and 'compact' so that it looks like this: Code:
# LILO configuration file The video adapter thing is a driver problem. You're using the stock nvidia opensource driver at present (I'm presuming) but once you go with the standard nvidia driver from slackbuilds.org or as I do I get mine from nvidia, IIRR that will fix those two messages about video adaptor. Here's my complete lilo.conf, just in case I missed something somewhere: Code:
# LILO configuration file |
Not being a distrohopper, I think grubs belong in vegetative matter and not boot sectors, so I have no personal experience. However a simple edit of /boot/grub/menu.lst should be all that is required. http://www.linuxquestions.org/questi...4/#post4367071
Quote:
Code:
lba32 # Allow booting past 1024th cylinder with a recent BIOS Quote:
Code:
vga = normal Remember to run 'lilo' after making these changes. Edit- irgunil was faster! The 'compact' option is also desirable. |
Thanks kindly for your help: looks great and should work!
|
Quote:
I'll give it a go. (the "distrohopping" you refer to, in my case, is simply a matter of having a place I can go and chill and watch a video, do some mail, as respite from the hours I'm putting into this project of getting Slackware up and running properly; having said that, I will soon be at the point where I can leave grubs to those who have a taste for such things and relax on my lilo, needing thereafter only one distro to float me) cheers |
Quote:
I successfully built v3.8.1 from source today and it works but alas and alack, it has not altered my main problem one whit! I have placed a png here: http://www.linuxquestions.org/questi...-a-4175468008/ showing the sorry state of graphics: it is a shot of firefox being launched, then freezing, under Xfce. (if I try KDE, the system crashes) regs |
Quote:
Hope this helps! |
Quote:
Much appreciated. regs |
Quote:
So then I jumped right in and got the -current system upgrade successfully done: no change to problem!!! I wonder if I should now go back and try a more recent kernerl: 3.9? |
if your -current system upgrade was successfull you should be already running kernel version 3.9.7.
To check, please post output of: Code:
uname -a |
Quote:
|
Quote:
|
Quote:
I did just that! Unfortunately, temporary setback in that 2/3 of the way through (just when <slackpkg install-new> was about to finish), my internet server dropped me and made gui situation even worse (i have opened another thread on this) Really appreciate your time. Regs |
All times are GMT -5. The time now is 09:05 AM. |