LinuxQuestions.org
Help answer threads with 0 replies.
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 11-21-2010, 02:04 AM   #1
hedron
Member
 
Registered: Jul 2009
Location: NYC
Distribution: Slackware64-multilib 14.2, SARPI
Posts: 286

Rep: Reputation: 27
Unable to determine video adapter


Code:
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007 and compiled at 20:09:28 on Feb 14 2010

Reading boot sector from /dev/sda
Warning: Unable to determine video adapter in use in the present system.
Using BITMAP secondary loader
Calling map_insert_data
Mapping bitmap file /boot/slack.bmp
Warning: Video adapter does not support VESA BIOS extensions needed for
  display of 256 colors.  Boot loader will fall back to TEXT only operation.
Calling map_insert_file

Boot other: /dev/sda1, on /dev/sda, loader CHAIN
Added Windows *

Boot image: /boot/vmlinuz
Added Linux

Boot image: /boot/vmlinuz.old2
Added old

The boot sector and the map file have *NOT* been altered.
2 warnings were issued.
I don't know what to do? My lilo.conf is pretty much default. I have to use my USB drive to boot slackware, as I get a kernel panic trying to boot either my new kernel or the default kernel. I haven't installed my video drivers, but it wouldn't make sense to need to have the proprietary nvidia drivers installed in order to boot linux. It was working fine before I compiled my kernel.

Last edited by hedron; 11-21-2010 at 02:13 AM.
 
Old 11-21-2010, 08:33 AM   #2
adamk75
Senior Member
 
Registered: May 2006
Posts: 3,091

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
As far as I can tell, those are just relatively harmless warnings tell you that the lilo bootloader is going to use text only mode. I see no indication that lilo failed to install.

Adam
 
Old 11-21-2010, 03:15 PM   #3
hedron
Member
 
Registered: Jul 2009
Location: NYC
Distribution: Slackware64-multilib 14.2, SARPI
Posts: 286

Original Poster
Rep: Reputation: 27
But linux won't boot ...
 
Old 11-21-2010, 03:24 PM   #4
stress_junkie
Senior Member
 
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873

Rep: Reputation: 334Reputation: 334Reputation: 334Reputation: 334
What is the exact error message issued by the kernel panic? Is it something like "Attempted to kill init. Unable to mount root partition on unknown block 0,0"?

If that is the case then that is (almost) always due to the kernel being unable to mount the root partition. That is because the kernel doesn't have the driver (module) for that particular file system built into it.

The file system driver for the root partition MUST be built into the kernel. You cannot load it as a module.
 
Old 11-22-2010, 02:33 AM   #5
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,367

Rep: Reputation: 838Reputation: 838Reputation: 838Reputation: 838Reputation: 838Reputation: 838Reputation: 838
Quote:
Originally Posted by stress_junkie View Post
The file system driver for the root partition MUST be built into the kernel. You cannot load it as a module.
Unless you use an initial ramdisk (initrd).
 
Old 01-12-2011, 05:40 PM   #6
David93
LQ Newbie
 
Registered: Feb 2009
Location: Bogota, Colombia
Distribution: Slackware
Posts: 10

Rep: Reputation: 0
Hi. Just a few minutes I have (I think) the same problem. In google, the solution I found was to check the BIOS load order. I hope it helps to you as it did for me.

I dont know how it works for me. Anybody knows?
 
  


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
HELP..... Unable to determine why squid is slow... suhas! Linux - Server 13 05-11-2009 04:42 AM
How do I determine which video driver to use jacatone Linux - Software 1 02-18-2008 12:23 AM
router unable to determine hostname kodon Linux - Wireless Networking 0 09-08-2004 12:57 PM
eth0 unable to determine IP, fedora cloks Linux - Newbie 2 03-24-2004 05:57 PM
proftpd - unable to determine IP address nathangg Linux - Networking 1 02-28-2003 07:57 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05: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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration