[3047] in linux-scsi channel archive
Compaq Deskpro XL w/ linux 2.0.31 does not need movepci.sys
daemon@ATHENA.MIT.EDU (silvat@bose.com)
Tue Jan 6 16:47:48 1998
From: silvat@bose.com
Date: Tue, 6 Jan 1998 16:18:59 -0500
To: AHands@sprynet.com, linux-scsi@vger.rutgers.edu, Klaus.Liedl@uibk.ac.at,
silvat@bose.com
Regarding the mapping of the 32-bit BIOS extensions for probing PCI
devices on Compaq systems, I noticed a change made to
linux/arch/i386/kernel/bios32.c between kernel versions 2.0.7 and
2.0.31. In linux 2.0.7, it contains:
printk("pcibios_init: entry in high memory, unable to access\n");
In linux 2.0.31, it contains:
printk("pcibios_init: entry in high memory, trying direct PCI access\n");
Before I noticed this, and based on my reading XL-HOWTO-[1-5].html
from http://tci002.uibk.ac.at:80/XL/, I had been loading movepci.sys
version 4.1 from ftp://ftp.compaq.com/pub/softpaq/Drivers/sp1599.exe
in my Win95 config.sys prior to booting linux via loadlin. However,
once I noticed the change above, I decided to comment out the movepci
call in config.sys and, voila, my Compaq Deskpro XL 5100 can still see
its SCSI drives! (I have 2 hard disks and a CD-ROM.) During booting, I
see:
pcibios_init : BIOS32 Service Directory structure at 0x000fa000
pcibios_init: entry in high memory, trying direct PCI access
My machine is currently at home, so I could not verify that the Ethernet
also still works. However, the boot messages ("eth0 ...") seem to imply
that it too is still ok.
http://www.linux.ncsu.edu/LDP/HOWTO/SCSI-HOWTO-5.html currently says:
Failure of a PCI board in a Compaq System
A number of Compaq systems map the 32-bit BIOS extensions used to probe
for PCI devices into memory which is inaccessible to the Linux kernel
due to the memory layout. If Linux is unable to detect a supported PCI
SCSI board, and the kernel tells you something like
pcibios_init: entry in high memory, unable to access
Grab
ftp://ftp.compaq.com/pub/softpaq/Software-Solutions/sp0921.zip
which is a self-extracting archive of a program which will relocate the
BIOS32 code.
Assuming I haven't missed anything, would it make sense to update this
web page so suggest simply upgrading the kernel used (which gets rid
of "unable to access") instead of screwing around with movepci.sys?
Perhaps http://tci002.uibk.ac.at:80/XL/ should also suggest the kernel
upgrade.
-- Tony
Tony Silva tel: (508)766-4121
Bose Corporation FAX: (508)820-9522
The Mountain, M/S 234 Internet: silvat@bose.com
Framingham, MA 01701-9168 tony_silva@alum.mit.edu
--
Tony Silva tel: (508)766-4121
Bose Corporation FAX: (508)820-9522
The Mountain, M/S 234 Internet: silvat@bose.com
Framingham, MA 01701-9168 tony_silva@alum.mit.edu
