Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 08-12-2004, 06:46 AM   #1
Registered: Aug 2004
Distribution: SLACKWARE10.0
Posts: 65

Rep: Reputation: 15
S-ATA Boot problems. Slack 10. Help!

Boot problems Kernel configuration issue.

My problem:

Currently, I have Slackware 10 installed on my box but I cannot get it to load properly.
Even with the aid of floppy boot disks (which I hate to use) it will not boot.
The best I can get is a boot into the root terminal - darkstar@root .

A bit of history:

Im using the now infamous Via VT8237 southbridge as part of my ASUS motherboard.
SATA SATA SATA. Im also using a Seagate Barracuda 80GB S-ATA drive.

Originally I could do nothing. Then thanks to Bonecrushers floppy image sata.i, I could

finally use 'cfdisk' to configure my partitions. They are as follows

1 x 50GB /ext2 for my (now installed and configured?) Slack. as boot
1 x configured linux swap partition - 1GB (I have 512mb RAM)
1 x unformatted partion - 10GB also as boot (I believe this was the cause of LILO

problems, which are hopefully now gone)
1 x unformattedf parttion which I would eventually like to use as /home

That leaves 9GB left over for future.

I should also point out that my processor is an Athlon64, though I dont think that is

the problem.

I'll cut to the chase:

Firstly, after installing slack, my BIOS is now speaking to me in what I believe to be

Spanish (was English). I get this message if there is no boot medium:

'No se encuentra el sistema operativo'

I don't really care about that for now as I dont intend to have no boot medium very


I am currently using my Master Boot Record to base LILO. After deciding not to mess with

LILO in expert mode, I set it up using simple. It failed to install in my Linux

partition. Because I have 2 boot partitions? Because Im still using Bonecrushers sata.i

as kernel? I dont know. So I elected to put it into my MBR. I know, this may have beena

bad move.

But the results were better, I could now launch Linux from boot in LILO - no more 'No se

encuenta el.....'

The real problem now is that I keep getting the following message at boot:

'VFS: Insert root floppy and press enter.'

No matter what floppy I use, it doesn't work. Its not even trying to open a disk.

'Cannot open root device "202" or 2:02
Please append a "root=" boot option.

So, thats as far as I get!

The only way I can get into any kind of installed kernel is when I use my startup disk.

That foreces me to

mount root=/dev/sda1 ro- just gets me into darkstar@root in read only

If I try rw, I get nowhere.

If I try to mount /dev/sda1 rw I just get right back to 'VFS: Insert floppy..'

My feeling is that I need to get back to C_onfigure my syystem using the boot disks and

running setup from CD and just install a new Kernel. Could that work, or is it something


Is it beyond repair. Would a fresh install be better.

Any suggestions, advice etc. is most welcome.

Sorry to suck up your time :|

-- Paulinim

My box:

Athlon64 3000+ (s754)
Seagate Barracuda 80GB S-ATA Striped
Asus K8V-DX (uses VT8237 South bridge)
nVidia FX 5700 VTD 256
1 stick of 512mb PC3200 RAM
Old 08-12-2004, 07:51 AM   #2
Senior Member
Registered: Nov 2003
Location: NB,Canada
Distribution: Something alpha or beta, binary or source...
Posts: 2,280
Blog Entries: 4

Rep: Reputation: 47
What its looking for when you use the disk and get to
'VFS: Insert root floppy and press enter.'
is likely a ramdisk, or initrd. They can be created, but I don't know how. DOES ANYONE ELSE KNOW HOW? If its not too much trouble, you might want to try reinstalling, but its definitely worth trying to save what you have. I don't play with Slack enough to know how to get a different kernel installed at boot time, but it seems like your solution is to install a kernel that supports your s-ata.

Perhaps you'll be able to do that if you "chroot" into your Slack install. Technically, when you boot fromt he floppy kernel, you're running from that kernel as your system, which is why you can't write to the install.

Or, as the Slackware book says, you can choose a different kernel when you are installing (or after, if you can chroot with write permissions intact).


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
Asus P4P800 Deluxe, Slack 9.1, Serial-Ata Jetti Slackware - Installation 3 02-06-2004 03:52 AM
ATA RAID with Slack. trouby Slackware 4 01-30-2004 09:45 PM
Slack 9.1 First Boot problems fluxtux Slackware 2 11-05-2003 05:05 PM
help. ATA/SCSI Serial-ATA error: "ATA: Abnormal Status" xin Linux - Hardware 10 09-05-2003 10:59 PM
Psyche & Maxtor Ultra ATA/100 Boot Problems pimp10700 Linux - General 1 11-09-2002 03:29 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 10:17 AM.

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