LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-30-2013, 08:53 AM   #16
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2

Quote:
Originally Posted by Terminator3000 View Post
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.
Really appreciate you getting back to me on this.
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.
 
Old 06-30-2013, 10:09 AM   #17
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,489

Rep: Reputation: 662Reputation: 662Reputation: 662Reputation: 662Reputation: 662Reputation: 662
Quote:
Originally Posted by textillis View Post
THanks, but my installation of slack boots and only when i launch X does it show the problems discussed in my initial post.
I forgot to mention this: on my two Dell machines, I have to add intel_agp and i915 modules explicitly to the initrd, so KMS can be used. I do this by adding them to the MODULES="ext4 ..." line in /etc/mkinitrd.conf and building the initrd with mkinitrd -F.
 
1 members found this post helpful.
Old 06-30-2013, 11:58 AM   #18
Lirey
Member
 
Registered: Sep 2009
Distribution: Slackware
Posts: 32

Rep: Reputation: 5
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
 
1 members found this post helpful.
Old 06-30-2013, 10:59 PM   #19
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2
THanks to all who responded!

Quote:
Originally Posted by Lirey View Post
Hi textillis.

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
This is what Allend and others have suggested.
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!

Last edited by textillis; 06-30-2013 at 11:06 PM.
 
Old 06-30-2013, 11:51 PM   #20
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.1
Posts: 1,412

Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
Quote:
Originally Posted by Terminator3000 View Post
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.
I still don't get why people who don't use a distribution come over here to give advice about it.

Slackware doesn't provide GDM, so perhaps you should reconsider recommending its use.
 
Old 07-01-2013, 12:54 AM   #21
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,377

Rep: Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824
Quote:
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?
If you are thinking of building a newer kernel in Slackware 14.0, then look at this. http://docs.slackware.com/howtos:sla...kernelbuilding
If you do this, consider using the -j option to make in this
Quote:
make bzImage modules # compile the kernel and the modules
If your hardware has the grunt, use it! The general recommendation for -j is number of CPU cores + 1.

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.
 
1 members found this post helpful.
Old 07-01-2013, 01:05 AM   #22
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2
Wink Leaning on the everlasting slackarmoury ....

Quote:
Originally Posted by allend View Post
If you are thinking of building a newer kernel in Slackware 14.0, then look at this. http://docs.slackware.com/howtos:sla...kernelbuilding
If you do this, consider using the -j option to make in this

If your hardware has the grunt, use it! The general recommendation for -j is number of CPU cores + 1.

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.
This is great! I didn't realize I could install -current, but rather I was under the misaprehension that I was obliged to upgrade from 14. That is why I posted that I felt underconfident to do that, given that I didn't haven't a properly functioning gui in my 14 install.

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!
 
Old 07-01-2013, 01:09 AM   #23
Terminator3000
Member
 
Registered: Jun 2012
Distribution: Centos 6 & Fluxbox
Posts: 86

Rep: Reputation: Disabled
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.
 
1 members found this post helpful.
Old 07-01-2013, 01:24 AM   #24
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2
Cheers, and good luck with slackware installation

Quote:
Originally Posted by Terminator3000 View Post
I am currently installing it on a spare machine I have and I do not anticipate any problems with it.

But you never know.
Terminator: I really appreciate the time you spent, the interest you took, in helping me.
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.
 
Old 07-01-2013, 07:25 AM   #25
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2
Grub in other OS not picking up newkernel in Slackware's lilo.conf

Quote:
Originally Posted by allend View Post
If you are thinking of building a newer kernel in Slackware 14.0, then look at this. http://docs.slackware.com/howtos:sla...kernelbuilding
I did as you suggested, Allend.
The process went almost without hitch, but finished with three warnings:
Code:
  1. LBA32 addressing assumed
  2. Unable to determine video adaptor in use in the present system
  3. Video Adaptor does not support VESA BIOS extensions needed for display of 256 colours. Boot loader will fall back on text only operation
None of which would seem to pose too big a problem, since this is only the bootloader, right?

I have a fresh problem arising out of this process, which i'll make the subject of a new post ... phew!

Last edited by textillis; 07-01-2013 at 07:41 AM.
 
Old 07-01-2013, 07:49 AM   #26
irgunII
Member
 
Registered: Jan 2012
Location: Directly above the center of the earth
Distribution: Slackware. There's something else?
Posts: 360

Rep: Reputation: 61
Quote:
Originally Posted by textillis View Post
I did as you suggested, Allend.
The process went almost without hitch, but finished with three warnings:
Code:
  1. LBA32 addressing assumed
  2. Unable to determine video adaptor in use in the present system
  3. Video Adaptor does not support VESA BIOS extensions needed for display of 256 colours. Boot loader will fall back on text only operation
None of which would seem to pose too big a problem, since this is only the bootloader, right?
I think I can actually help with this part...

In your /etc/lilo.conf you can add 'LBA32' and 'compact' so that it looks like this:

Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32
boot = /dev/sda
compact   # faster, but won't work on all systems.
That will stop the LBA message from popping up every boot.

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
# generated by 'liloconfig'
#
# Start LILO global section
lba32
boot = /dev/sda
compact        # faster, but won't work on all systems.
# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack14.0.2012.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255
# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Append any additional kernel parameters:
append=" vt.default_utf8=1"
prompt
#timeout = 300
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
#vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = SlackMain
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdb1
  label = SlackBackup
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
I hope that was a little help at least. I'm no guru by any means but can get things here and there, heh.
 
1 members found this post helpful.
Old 07-01-2013, 08:07 AM   #27
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,377

Rep: Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824Reputation: 824
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:
LBA32 addressing assumed
Informational message only that can be removed with an entry in the global section of /etc/lilo.conf
Code:
lba32 # Allow booting past 1024th cylinder with a recent BIOS
A recent BIOS in this context is probably anything post circa 1998.

Quote:
Unable to determine video adaptor in use in the present system

Video Adaptor does not support VESA BIOS extensions needed for display of 256 colours.
I suggest trying the setting
Code:
vga = normal
in the global section of /etc/lilo.conf (you may need to just uncomment an entry by removing the leading #).

Remember to run 'lilo' after making these changes.

Edit- irgunil was faster! The 'compact' option is also desirable.

Last edited by allend; 07-01-2013 at 08:11 AM.
 
1 members found this post helpful.
Old 07-01-2013, 08:10 AM   #28
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2
Thanks kindly for your help: looks great and should work!

Last edited by textillis; 07-01-2013 at 08:44 AM.
 
Old 07-01-2013, 08:18 AM   #29
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by allend View Post
a simple edit of /boot/grub/menu.lst should be all that is required. http://www.linuxquestions.org/questi...4/#post4367071
Thanks again Allend.
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
 
Old 07-01-2013, 10:20 AM   #30
textillis
Member
 
Registered: May 2013
Location: Northern Rivers, NSW, Australia
Distribution: Slackware64-current, Mint Nadya
Posts: 299

Original Poster
Rep: Reputation: 2
Quote:
Originally Posted by Lirey View Post
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
Hi Lirey,
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

Last edited by textillis; 07-01-2013 at 10:24 AM.
 
  


Reply

Tags
crashing, guis, salix


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] confused by flash performance Slackware vs Salix damgar Slackware 37 06-30-2010 05:46 PM
Can i run any xwindows in slackware 10.0 with limited hardware?Hello, cyto Slackware 18 09-03-2004 10:02 AM


All times are GMT -5. The time now is 02:45 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration