LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
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 02-08-2007, 10:14 AM   #16
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53

Hi folks,

After mounting the floppy to read its contents I found something strange there. The bootload is grub;

# mount /dev/fd0 /mnt/floppy/
# ls /mnt/floppy/
Code:
boot/  lost+found/
# ls /mnt/floppy/boot/
Code:
grub/
# ls /mnt/floppy/boot/grub/
Code:
e2fs_stage1_5*  iso9660_stage1_5*  reiserfs_stage1_5*  ufs2_stage1_5*
fat_stage1_5*   jfs_stage1_5*      stage1*             vstafs_stage1_5*
ffs_stage1_5*   minix_stage1_5*    stage2              xfs_stage1_5*
I saved LILO on floppy. How it became grub


B.R.
satimis

Last edited by satimis; 02-08-2007 at 10:15 AM.
 
Old 02-08-2007, 05:09 PM   #17
syvy
Member
 
Registered: Sep 2005
Location: Germany
Distribution: slackware64
Posts: 110

Rep: Reputation: 16
Hi satimis,

sorry but I had to work so my answer comes a bit later. I have no idea why lilo became to grub. Very strange.
You can't simply copy the content from the floppy to hd and boot it. Maybe you should boot from floppy
or DVD again, uninstall grub and reinstall lilo. I don't have such problems here. My regular slackware installation
is on sda1 with lilo in the superblock, partition marked active. My slamd64 is on sda5 with lilo on floppy, it's only for
testing purposes because many things I need don't work with slamd out of the box.
 
Old 02-08-2007, 06:34 PM   #18
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,485

Rep: Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856Reputation: 856
That error message I have seen come up when there is no initrd present. Have you run mkinitrd?
 
Old 02-08-2007, 07:15 PM   #19
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
HI allend,

Quote:
That error message I have seen come up when there is no initrd present. Have you run mkinitrd?
I haven't run mkinitrd nor anything. Because after installation completed the PC can't boot.

Previously Slackware-11.0 ran on this PC without much problem. I suppose slamd64 is the same with only difference on 64bit.


B.R.
satimis
 
Old 02-08-2007, 07:25 PM   #20
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Hi syvy,

Quote:
Maybe you should boot from floppy
Booting from floppy is not a problem. I'm running it now.

I expect to find out a solution otherwise I'll go back to 32bit to continue my test on server building.

Quote:
uninstall grub and reinstall lilo.
I did not install grub. Neither there was an option for me to select. I only installed LILO as bootloader.

As far as I can remember during installation there were options for selecting SCSI, SATA, etc. I did not select either of them only continue on the highlighted option.

I'll reinstall slamd6-11.0 later. This is a fast PC, dual core with 2G dual channel RAM. It does not take much time.


B.R.
satimis
 
Old 02-09-2007, 07:25 AM   #21
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
SOLVED - slamd64 can boot now

Hi folks,

I have solved the booting problem with following steps;

Edited /etc/lilo.conf as follow;

# cat /etc/lilo.conf
Code:
# Start LILO global section
boot = /dev/sda
message = /boot/boot_message.txt
prompt
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x256
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda2
  label = Linux
  read-only
# Linux bootable partition config ends

Ran
# lilo -C /etc/lilo.conf
Code:
Added Linux *
Removed the boot floppy and rebooted PC. PC booted straight to runlevel 3 without problem.

# startx
Started KDE.


B.R.
satimis
 
Old 02-09-2007, 09:02 AM   #22
jets0n
Member
 
Registered: Aug 2006
Distribution: Slackware | Ubuntu | Debian | CentOS
Posts: 34

Rep: Reputation: 15
That's the way lilo should have been set up by default. what changes did you make? also, a tip - add "compact" to the top of lilo.conf, just above option "prompt" and rerun lilo. it should speed up that lilo's check on boot. glad you managed to fix your problem

Last edited by jets0n; 02-09-2007 at 09:03 AM.
 
Old 02-09-2007, 09:57 AM   #23
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Hi jets0n,

Quote:
what changes did you make?
Changes made as follows;
1)
Old:
boot = /dev/fd0
(because I saved LILO on floppy)

New:
boot = /dev/sda

2)
Old:
# VESA framebuffer console @ 1024x768x256
vga = 773

New:
vga = normal


Quote:
a tip - add "compact" to the top of lilo.conf, just above option "prompt" and rerun lilo. it should speed up that lilo's check on boot.
Whether as:
Code:
....
message = /boot/boot_message.txt
compact
prompt
timeout = 1200
....
and re-run;
# lilo -C /etc/lilo.conf


Tks.


B.R.
satimis
 
Old 02-09-2007, 10:01 AM   #24
jets0n
Member
 
Registered: Aug 2006
Distribution: Slackware | Ubuntu | Debian | CentOS
Posts: 34

Rep: Reputation: 15
yip,just like that. it shuld help you with that nagging "BIOS data check succesful screen" (by decreasing the check time)
 
Old 02-09-2007, 11:54 AM   #25
syvy
Member
 
Registered: Sep 2005
Location: Germany
Distribution: slackware64
Posts: 110

Rep: Reputation: 16
Hi satimis!

Im glad your slamd boots from hd now. There must have been something wrong in the lilo.conf before you tried booting from floppy.

The next step is compiling a smp-kernel to get full performance of your dual-core cpu.
 
Old 02-09-2007, 08:22 PM   #26
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Quote:
Originally Posted by jets0n
yip,just like that. it shuld help you with that nagging "BIOS data check succesful screen" (by decreasing the check time)
Hi jets0n]yip,

Your advice works here. Tks.


B.R.
satimis
 
Old 02-09-2007, 08:30 PM   #27
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Hi syvy,


Quote:
There must have been something wrong in the lilo.conf before you tried booting from floppy.
I don't know. What I can recall is on booting up the PC with slamd64_11.0-installer "Configure Reconfigure ..." did not work. Highlighting it and hitting [Enter], it jumped to the top "Help". That is why I suspected having some problem on the installer.

Quote:
The next step is compiling a smp-kernel to get full performance of your dual-core cpu.
Pls advise how to make it. Recompiling kernel? TIA

Pointer is appreciated.

Kernel 2.4 or 2.6 is running on slamd64-11.0? How to check it? Tks

B.R.
satimis
 
Old 02-10-2007, 12:17 PM   #28
syvy
Member
 
Registered: Sep 2005
Location: Germany
Distribution: slackware64
Posts: 110

Rep: Reputation: 16
Hi satimis!

Just type uname -r to find out your kernel version.

If you never compiled a kernel before it might be helpful to read a howto first. Here is a very good one:

http://www.digitalhermit.com/linux/K...ild-HOWTO.html

Be shure to have everything installed what you need: kernel source, kernel headers, gcc and so on. If you have a full installation of slamd you're fine. I'm not an expert compiling kernels but I got it and it's working fine here. So I tell you how I did.

I installed slamd64 11.0 with the huge26.s kernel. It's version 2.6.16.29. Starting point is the directory /usr/src/linux which should be a symlink to /usr/src/linux-2.6.16.29. If it's not, doesn't matter, just cd to /usr/src/linux-2.6.16.29. Now we need a config-file. I used config-generic-2.6.16.29 which you should find in /boot. Copy it to your kernel-source directory and rename it .config. Don't forget the dot. I have installed the kernel modules for 2.6.16.29 already, so I edited the .config-file under "general options" like this:

Quote:
CONFIG_LOCALVERSION="-smp"
This prevents your existing modules from overwriting. The new ones we compile later will go then to /lib/modules/2.6.16.29-smp instead of /lib/modules/2.6.16.29 where your existing modules are.

Type make oldconfig. If there come questions, answer them carefully. After that type make menuconfig and configure your
processor type, smp-support and other things depending on your hardware. Do this carefully and you should have read the kernel-build-howto at this point.

After that it's time to compile everything. I did it step by step. First make bzImage, which compiles only the kernel. Then make modules, then make modules_install. Before you copy everything to /boot it's a good idea to save the existing kernel to have a fallback if something goes wrong. Look in /boot: if there are vmlinuz-generic-2.6.16.29, System.map-generic-2.6.16.29, config-generic-2.6.16.29 and symlinks to them (vmlinuz, System.map, config), delete the symlinks. If there are only vmlinuz, System.map, config rename them by appending -generic-2.6.16.29 to each name.

Now copy the new files to /boot:
Quote:
cp arch/x86_64/boot/bzImage /boot/vmlinuz-2.6.16.29-smp
cp System.map /boot/System.map-2.6.16.29-smp
cp .config /boot/config-2.6.16.29-smp
and make symlinks there

Quote:
cd /boot
ln -s vmlinuz-2.6.16.29-smp vmlinuz
ln -s System.map-2.6.16.29-smp System.map
ln -s config-2.6.16.29-smp config
Before rebooting it's important to have a look at /etc/lilo.conf and add a pointer to your old kernel as a fallback.
Mine looks like this (I left out some commented (#) lines to keep it short):

Quote:
lba32 # Allow booting past 1024th cylinder with a recent BIOS
boot = /dev/fd0 # floppy here
#compact # faster, but won't work on all systems.
#prompt
timeout = 5
# VESA framebuffer console @ 1024x768x32k
vga=790

image = /boot/vmlinuz # the new kernel
root = /dev/sda5 # your / partition
label = slamd64
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.16.29 # the old kernel for fallback
root = /dev/sda5
label = oldslamd64
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
Now just type lilo, pray and reboot. If you see two penguins at the boot screen, you're not drunk. Each penguin stands for one CPU.

Good Luck!

Last edited by syvy; 02-10-2007 at 12:19 PM.
 
Old 02-10-2007, 01:01 PM   #29
syvy
Member
 
Registered: Sep 2005
Location: Germany
Distribution: slackware64
Posts: 110

Rep: Reputation: 16
Oh, I forgot something important:
Slamd runs fine with my smp-kernel but I have no more sound in KDE. There were others in the slamd-forum with this problem, too. Someone posted that he compiled alsa new to get the sound back but he didn't explain how he made it. Since my slamd is just for testing sound isn't that important to me. If I have some more time I try to solve this problem anyway.
 
Old 02-12-2007, 09:51 PM   #30
satimis
Senior Member
 
Registered: Apr 2003
Posts: 3,428

Original Poster
Rep: Reputation: 53
Hi syvy,

Tks for your detail advice.

I have been waiting a while for fred to upload the smp-kernel on the mirror. Now he has uploaded smp-kernel on the current tree "slamd64-current", for testing.

http://ftp.scarlet.be/pub/slamd64/sl.../huge26_smp.s/


Anyway I'll try your version later in order to fresh my recollection on kernel recompilation. Sound is not important to me. The important thing is to retain the old kernel allowing me to revert back in case of problem.

Tks.


B.R.
satimis
 
  


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
SUSE USB installation boot up fails dep. on IDE or SATA oozie Linux - Kernel 0 10-23-2006 06:00 PM
Slamd64 RC4 won't boot? cheater1034 Slackware - Installation 7 03-02-2006 11:24 PM
Mandrake 10.0 Community installation - boot floppy fails at reckognizing SCSI CDROM nixguide Mandriva 5 06-03-2004 12:38 PM
Installation success, boot load fails nimonm Linux - Newbie 2 01-12-2004 10:43 PM
RH9 installation fails on boot JezzerP Linux - Distributions 1 07-06-2003 07:20 AM


All times are GMT -5. The time now is 07:26 PM.

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