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 10-30-2012, 10:09 PM   #16
ferrel
Member
 
Registered: Feb 2007
Location: Pasadena, Texas
Distribution: Slackware 14.0
Posts: 137

Original Poster
Rep: Reputation: 3

Thanks, here is lilo.conf in there segments.
Attached Images
File Type: jpg liloconf1.jpg (46.8 KB, 17 views)
File Type: jpg liloconf2.jpg (45.6 KB, 15 views)
File Type: jpg liloconf3.jpg (37.8 KB, 13 views)

Last edited by ferrel; 10-30-2012 at 10:11 PM.
 
Old 10-30-2012, 10:49 PM   #17
sse007
Member
 
Registered: Nov 2005
Posts: 39

Rep: Reputation: 15
config looks fine, have u tried boot into single user mode ?
for starting the 13.37 dvd, just hit enter at the boot: prompt or put in any options after typing huge.s and hit enter
 
Old 10-30-2012, 11:08 PM   #18
ferrel
Member
 
Registered: Feb 2007
Location: Pasadena, Texas
Distribution: Slackware 14.0
Posts: 137

Original Poster
Rep: Reputation: 3
I've tried using telinit 1, with no luck.
 
Old 10-30-2012, 11:41 PM   #19
sse007
Member
 
Registered: Nov 2005
Posts: 39

Rep: Reputation: 15
i reread your first post and notice your screen went blank and then show no input signal, i know slackware 13.37 and 14.0 use modesetting which will switch to higher resolution that your videio card can handle at some point during boot, just wondering if it is your monitor doesn't support that resolution, so what you can try during installation when you get to the lilo installation, select expert and at the append kernel parameter, put in video=800x600, that will make it use that resolution instead of switch to the higher resolution

Last edited by sse007; 10-30-2012 at 11:50 PM.
 
Old 10-31-2012, 12:10 AM   #20
ferrel
Member
 
Registered: Feb 2007
Location: Pasadena, Texas
Distribution: Slackware 14.0
Posts: 137

Original Poster
Rep: Reputation: 3
I tried it, same problem.
 
Old 10-31-2012, 06:03 AM   #21
bormant
Member
 
Registered: Jan 2008
Posts: 112

Rep: Reputation: 51
From http://wiki.linuxquestions.org/wiki/LILO_Error_Codes
Quote:
Causes
This error may occur, if the hard drive is in normal mode, but lilo has written the boot record using logical block addressing mode. Switching the bios hard drive parameters to logical block addressing allows the bootloader to start normally. Unfortunately a side effect of this is that now the system may not start properly, because geometry differences prevent the bootloader from locating the partitions properly.
 
Old 10-31-2012, 06:27 AM   #22
ferrel
Member
 
Registered: Feb 2007
Location: Pasadena, Texas
Distribution: Slackware 14.0
Posts: 137

Original Poster
Rep: Reputation: 3
Where in the install/boot process would I enter lilo -g?
 
Old 10-31-2012, 06:56 AM   #23
bormant
Member
 
Registered: Jan 2008
Posts: 112

Rep: Reputation: 51
You can boot into installed system with Slackware install media.
1) boot from the install DVD or CD
2) in syslinux prompt "boot:" answer as shown in example on screen
boot: huge.s root=/dev/sda1 rdinit= ro
where /dev/sda1 is your actual root partition; note space after "rdinit="

Anather way is to boot in Slackware install environment, mount root partition to /mnt and chroot into it:
1) boot from the install DVD or CD
2) press Eneter at syslinux "boot:" prompt and more until root shell prompt "#"
# mount /dev/sda1 /mnt
# for d in dev proc sys do; mount --bind /$d /mnt/$d; done
# chroot /mnt
where /dev/sda1 is your actual root partition.

Last edited by bormant; 10-31-2012 at 02:51 PM. Reason: Added mounting dev, proc, sys to new root
 
Old 10-31-2012, 07:32 AM   #24
jjthomas
Member
 
Registered: Jan 2004
Location: Tacoma, WA
Distribution: Slackware 14
Posts: 246
Blog Entries: 2

Rep: Reputation: 28
You have 4 partitions. One is your swap partition, what are the other three? Can you post your /etc/fstab?

-JJ
 
Old 10-31-2012, 10:35 AM   #25
ferrel
Member
 
Registered: Feb 2007
Location: Pasadena, Texas
Distribution: Slackware 14.0
Posts: 137

Original Poster
Rep: Reputation: 3
First method led to noise, blank screen, halt.
Other as show
Attached Images
File Type: jpg 2012-10-31 09.22.13-1.jpg (27.0 KB, 14 views)
 
Old 10-31-2012, 10:44 AM   #26
ferrel
Member
 
Registered: Feb 2007
Location: Pasadena, Texas
Distribution: Slackware 14.0
Posts: 137

Original Poster
Rep: Reputation: 3
Here it is
Attached Images
File Type: jpg 2012-10-31 09.39.15-1.jpg (26.5 KB, 11 views)
 
Old 10-31-2012, 02:28 PM   #27
ferrel
Member
 
Registered: Feb 2007
Location: Pasadena, Texas
Distribution: Slackware 14.0
Posts: 137

Original Poster
Rep: Reputation: 3
Before attempting this 14.0 install, my computer was a dual boot system
of xp and slackware64 13.1. I decided my 13.1 was getting dated, also
because I was having a problem with my video display when xscreensaver
was running. When running xp, there was no problem with the display at
all, only with 13.1 when xscreensaver was running. After xscreensaver
would start running, at some point the display would freeze, always
showing a series of diagonal lines of characters (blocks, dots, etc),
similar to a photo I posted in this thread earlier. This would sometimes
occur soon after xscreensaver began, or it might be many hours before
it would occur. It would always occur. So I wonder if there is some
connection with that, and with my current problem. This xscreensaver
problem is only a couple of months old; I assumed at the time that I
had botched my system my self in some way, and i made attempts to fix it,
without success. As mentioned earlier, it never occurred while xp was
running, which seemed to indicate the problem was software related,
rather than hardware related. Also, for the first year or so of the 13.1
installation, xscreensaver worked fine, with no freezing up with
those diagonal displays.

I had no problem installing lilo in the dual boot system.

I usually use cfdisk for partitioning, but I tried fdisk once during the 14.0
installation, primarily to try to begin my first sector on 1. The
default sector beginning was 2048; I tried to begin at 1, but
received an error message from fdisk that the value was
"out of range." The error about "cylinder number is too big"
appears to be related to this inaccessible space at the start on my hd.
I decided to not keep xp this time, so I'm wondering if this has
precipitated this problem?

Sorry for the long post, but I thought some background information
might be helpful.
 
Old 10-31-2012, 02:48 PM   #28
bormant
Member
 
Registered: Jan 2008
Posts: 112

Rep: Reputation: 51
I modified message #23 added mounting /dev, /proc and /sys to new root. This removes LILO warning about /proc/partitions. But this cannot do anything with kernel location after 1023 cylinder, so "-g" doesn't help.
If trouble in kernel location on disk (depends on BIOS, it's settings for this HDD) you can try to make separate small partition for /boot at the beginning of HDD.

Last edited by bormant; 10-31-2012 at 03:17 PM.
 
Old 10-31-2012, 03:50 PM   #29
jjthomas
Member
 
Registered: Jan 2004
Location: Tacoma, WA
Distribution: Slackware 14
Posts: 246
Blog Entries: 2

Rep: Reputation: 28
No worries on the long post:
Quote:
Originally Posted by ferrel View Post
primarily to try to begin my first sector on 1. The
default sector beginning was 2048; I tried to begin at 1, but
received an error message from fdisk that the value was
"out of range." The error about "cylinder number is too big"
appears to be related to this inaccessible space at the start on my hd.
I decided to not keep xp this time, so I'm wondering if this has
precipitated this problem?
I think that is your problem. Why not stick with the default 2048? Check out http://www.linuxquestions.org/questi...4/#post4701338

I remember reading somewhere that it was a bad idea to start a partition before 2048. Here is a google search: http://www.google.com/search?num=50&...1c.m0b85b_ezvY

The clunking on your hard disk concerns me. When my drives have clunked, they usually failed. However, I have an old Seagate 500 G that clunked a few years ago, and it is still running. YMMV.

My next step would be to erase the drive using dd, run fdisk and take the recommended starting partition of 2048. I would not enter sector 1 for a starting position. As Bormant suggested make sure you have a /boot partition and it needs to be you first partition.

Here is my suggestion (KISS):
/boot 128M
/ 30G
swap double RAM or 1G minimum
/home rest of drive

Creating a /boot partition is old school. But I still do it. I would not put /usr/local in a separate partition.

-JJ

PS On using dd you just need to erase the MBR, I let it run for a few seconds and ctrl-c out of it.
 
Old 11-01-2012, 12:44 AM   #30
ferrel
Member
 
Registered: Feb 2007
Location: Pasadena, Texas
Distribution: Slackware 14.0
Posts: 137

Original Poster
Rep: Reputation: 3
Success! One time! So far, not reproducible. I made the partition
table as recommended, did the simple auto lilo install, booted,
had an awkward split second when it made noise, and seemed on the
verge of hanging up . then the usual boot screen scrolled by,
although in much smaller type, and got a login prompt in single
user mode. telinit 4 gave a graphical login screen.
I've tried four times since then, same old problem.
Attached Images
File Type: jpg 2012-10-31 21.37.19-1.jpg (37.0 KB, 8 views)
 
  


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
[SOLVED] Slackware64 14.0 not installing, tried several methods. mpyusko Slackware - Installation 9 10-12-2012 04:57 PM
[SOLVED] Installing slackware64-13.37 0mani Slackware 4 04-10-2012 10:30 AM
[SOLVED] Installing AdobeReader in Slackware64 antonio-carioca Linux - Newbie 3 02-03-2011 11:08 AM
Doubts related to installing Slackware64-13. glore2002 Slackware 4 09-01-2009 08:53 PM
Slackware64 RC1: Installing Software rkfb Slackware 10 07-22-2009 11:28 PM


All times are GMT -5. The time now is 10:28 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