Re: Debian Boot fails SCSI detect (AIC7902 Relion 240)

2003-09-02 Thread Todd Weaver 
On Sat, Aug 30, 2003 at 11:31:18AM +0200, Petter Reinholdtsen wrote:
 
 [Todd Weaver]
  aic79xx: PCI4:2:1 MEM region 0x0 unavailable. Cannot memory map device.
 
 The aic79xx kernel module was first included in kernel 2.4.21.  You
 will probably need to use a newer kernel to get it to work.

Thanks Petter,

Just for mailing list completeness...

I compiled the latest kernel with aic79xx, e1000, e100, software RAID, and
all the appropriate rescue floppy stuff (linked below) compiled in.

Then I followed the instructions on how to replace the rescue floppy kernel:
http://www.debian.org/releases/woody/i386/ch-boot-floppy-techinfo.en.html#s-rescue-replace-kernel

Booted that, and away I went.

I now have a Relion 240 with the AIC7902 running a slim version of debian.

(phew boy am I glad to have Debian instead of RedHat)

And to futher toot Debian's horn,
I had absolutely NO trouble installing the entire system after
my new rescue disk was made.

Todd.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Debian Boot fails SCSI detect (AIC7902 Relion 240)

2003-08-30 Thread Petter Reinholdtsen 

[Todd Weaver]
 aic79xx: PCI4:2:1 MEM region 0x0 unavailable. Cannot memory map device.

The aic79xx kernel module was first included in kernel 2.4.21.  You
will probably need to use a newer kernel to get it to work.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Debian Boot fails SCSI detect (AIC7902 Relion 240)

2003-08-28 Thread Todd Weaver 
I got a machine supplied with RedHat.
I don't want RedHat (obviously).

I have tried booting the standard and compact kernels.

No SCSI devices are detected so I cannot continue the install.
(I was planning on setting up Software Raid (md) like the below config)

The dmesg output from RedHat is provided...

A little push in the right direction would be helpful.

dmesg:

DE controller at PCI slot 00:1f.1
PCI: Enabling device 00:1f.1 (0005 - 0007)
ICH3: chipset revision 2
ICH3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: SAMSUNG CD-ROM SC-152A, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide-floppy driver 0.99.newide
ide-floppy driver 0.99.newide
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 65536 buckets, 512Kbytes
TCP: Hash tables configured (established 262144 bind 65536)
Linux IP multicast router 0.06 plus PIM-SM
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 283k freed
VFS: Mounted root (ext2 filesystem).
SCSI subsystem driver Revision: 1.00
aic79xx: PCI4:2:1 MEM region 0x0 unavailable. Cannot memory map device.
nvram_scb == 0xfe
SCBPTR == 0xff
Signature = BIOS
aic79xx: PCI4:2:0 MEM region 0x0 unavailable. Cannot memory map device.
nvram_scb == 0xfe
SCBPTR == 0xff
Signature = BIOS
scsi0 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.0.0
Adaptec aic7902 Ultra320 SCSI adapter
aic7902: Ultra320 WideChannel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs

scsi1 : Adaptec AIC79XX PCI-X SCSI HBA DRIVER, Rev 1.0.0
Adaptec aic7902 Ultra320 SCSI adapter
aic7902: Ultra320 WideChannel B, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs

  Vendor: SEAGATE   Model: ST318453LCRev: 0005
  Type:   Direct-Access  ANSI SCSI revision: 03
scsi0:A:3:0: Tagged Queuing enabled.  Depth 253
  Vendor: SEAGATE   Model: ST318453LCRev: 0005
  Type:   Direct-Access  ANSI SCSI revision: 03
  Vendor: SEAGATE   Model: ST318453LCRev: 0005
  Type:   Direct-Access  ANSI SCSI revision: 03
  Vendor: SEAGATE   Model: ST318453LCRev: 0005
  Type:   Direct-Access  ANSI SCSI revision: 03


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]