LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
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 09-17-2009, 05:47 AM   #1
indubitableness
Member
 
Registered: Feb 2009
Distribution: Slackware64 14.0 multilib
Posts: 62

Rep: Reputation: 15
Why does my 32 bit slackware insist that it's 64 bits?


Okay. So I've tried multilib and it just wouldn't run anything 32 bit. (Specifically I used http://alien.slackbook.org/dokuwiki/...kware:multilib)

So I said screw it and I've installed along side it a Slackware 12.2 with the intention of dual booting. I added it to my lilo.conf and it boots up fine.

The problem is when I try to run any apps I get an error about how "This is an x86_64 platform" and it will not run any of the 32 programs.

Is it because my lilo is 64 bits? Is it loading the wrong kernel?

The 32 bit install uses a root partition at /dev/sda1 and the 64 bit is /dev/sda4 with a /home partition at /dev/sda3. At first I tried to share the /home partition between the two but I assumed it was causing the problem, but the problem persists even after using /dev/sda1 as the exclusive partition for slack12.2

I also tried using the lilo installed during the setup of 12.2 I was able to then load my 32 linux and play some wine games but I couldn't get back into my 64 bit install.

Is this normal? Shouldn't it be possible to dual boot 32 and 64 bit slackwares? Should I try grub?
 
Old 09-17-2009, 07:23 AM   #2
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,387

Rep: Reputation: 181Reputation: 181
Yes - you can dual boot. I suspect something wrong in lilo.conf. Post lilo.conf here and we can all have a look. It may just be a syntax error. I do those a lot.
 
Old 09-17-2009, 08:11 AM   #3
indubitableness
Member
 
Registered: Feb 2009
Distribution: Slackware64 14.0 multilib
Posts: 62

Original Poster
Rep: Reputation: 15
LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.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

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda4
label = Linux
read-only
# Linux bootable partition config ends

image = /boot/vmlinuz
root = /dev/sda1
label = linux32
read-only

-------------------------------------------------------------

I've removed a large section of comments "vga = 7**" but other than that this is my current lilo.conf. I've also tried it with "table = /dev/sda" included in the linux32 section with the same problem.

When I run lilo I get "One Warning issued" but I don't know where to look to check for the specific warning.

I'm trying multilib again. I'm hoping I just missed something last time (but I know I didn't) and that it'll magically work. This is driving me nuts. I need 32 bit support but the performance difference between 32 and 64 bit is substantial enough on this laptop that having a 32 OS as my main system isn't good enough.
 
Old 09-17-2009, 08:32 AM   #4
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,387

Rep: Reputation: 181Reputation: 181
There are probably different ways to do this, so I will show you the way I do this. Since lilo is installed from your 32bit install, you need to make a directory in /mnt and add an entry for the 64bit to /etc/fstab:

To make the dir:

Code:
# mkdir /mnt/Slackware64
Entry for fstab, change the filesystem type to suit your system:

Code:
/dev/sda4        /mnt/Slackware64   ext4        defaults         1   1
Change the entry in lilo.conf to this:

Code:
# Linux bootable partition config begins
image = /mnt/Slackware64/boot/vmlinuz
root = /dev/sda4
label = Linux
read-only
# Linux bootable partition config ends
Lastly, run this command as root:

Code:
# lilo
Now you should be able to boot either with the proper kernel.
 
Old 09-17-2009, 08:32 AM   #5
onebuck
Moderator
 
Registered: Jan 2005
Location: Midwest USA, Central Illinois
Distribution: SlackwareŽ
Posts: 11,473
Blog Entries: 4

Rep: Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525Reputation: 1525
Hi,

It looks like you are using the same kernel (image = /boot/vmlinuz) in each stanza of your '/etc/lilo.conf'.
 
Old 09-17-2009, 09:33 AM   #6
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,387

Rep: Reputation: 181Reputation: 181
I left out one very important command BEFORE running lilo:

Code:
# mount /mnt/Slackware
Then run lilo. I hope my omission has not caused you a headache this morning.
 
Old 09-17-2009, 10:28 AM   #7
swiger
LQ Newbie
 
Registered: Nov 2008
Location: Stuart, Florida USA
Distribution: slackware64-current
Posts: 5

Rep: Reputation: 0
You were booting the same kernel.

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda4
label = Linux
read-only
# Linux bootable partition config ends

# Linux 32bit bootable partition config begins
image = /mnt/Slackware/boot/vmlinuz
root = /dev/sda1
label = linux32
read-only
# Linux 32bit bootable partition config ends



-Sam-
 
Old 09-17-2009, 10:44 AM   #8
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,283

Rep: Reputation: 588Reputation: 588Reputation: 588Reputation: 588Reputation: 588Reputation: 588
I dual boot Slackware 13.0 and Slackware-current. I install Slackware-current's lilo to its root partition and use Slackware 13.0's lilo.conf to boot both distos. This lilo.conf set-up from my Slackware 13.0 partition works. My home partition is mounted on sda3.

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/root
  label = Linux
  read-only
# Linux bootable partition config ends
# Current
other = /dev/sda4
label = Current
 
Old 09-20-2009, 02:42 PM   #9
piratesmack
Member
 
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 518

Rep: Reputation: 133Reputation: 133
Install lilo to the superblock of the slack32 partition, then chainload it

Code:
other=/dev/sdxx
label linux32
EDIT:

Didn't see hitest's post
 
  


Reply


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
32 bits, why O why won't it run in 32 bit depth brokenteeth Linux - Hardware 2 09-22-2006 11:20 AM
LXer: 32-bit plugins under 64 bits LXer Syndicated Linux News 1 08-08-2006 05:05 PM
gdb won't recognize 64 bit executable on my RedHat 64 bits box cerniagigante Programming 1 02-23-2006 02:36 AM
synaptic - how to insist on remote sources voly Ubuntu 1 01-25-2006 06:51 AM
When will official Slackware 64 bits comes ? carlos.macleod Slackware 7 08-29-2005 07:57 AM


All times are GMT -5. The time now is 03:04 PM.

Main Menu
Advertisement
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