[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: failing PCI-bus



Hi,

Here are some ideas:

1. The message you are seeing comes from ./arch/i386/kernel/bios32.c,
with a note :

/*
 * Several BIOS'es forget to assign addresses to I/O ranges.
 * We try to fix it here, expecting there are free addresses
 * starting with 0x5800. Ugly, but until we come with better
 * resource management, it's the only simple solution.
 */

Take a look in your BIOS to see if there is anything interesting you
can enable with that in mind.

2. Linux 2.4 doesn't have the above hack as far as I can tell, so it
might 'just work'.  You can try the woody install disks, the bf24
flavor here:

http://http.us.debian.org/debian/dists/woody/main/disks-i386/current/images-1.44/bf2.4/

3. If that doesn't work we should have a bug filed against the
kernel-image.

good luck,

David



Thu, May 09, 2002 at 08:56:54AM +0200 wrote:
> I hope I put this question in the right list.
> 
> I am able to start my IBM 520 8641 in DOS mode, initializing the RAID-array, but linux refuses to 'see' it.
> 
> The trouble is that linux can't enable the PCI-slots in this MCA-PC (6 MCA slots, 2 PCI-slots)
> 
> dmesg keeps reporting:
> PCI: PCI BIOS revision 2.10 entry at 0xfd82c
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Unable to handle I/O allocation for 00:40 (0200), tell <mj@ucw.cz>
> Complete list attached.
> I replied to mj@ucw.cz, but no answer.....
> 
> Also starting with the loadlin-command, using options like pci=conf2 (PCI type 2), pci=nopeer, mca-pentium (just trying), 
> pci-io=9000 etc gives the same outcome.
> 
> I need the PCI-slots (2 in total) because the ethernet and RAID controller are connected to them!
> 
> Information on the PCI-structure:
> 
> PCI		| PCI host bridge	| PCI RAID	| PCI ether	| PCI-ISA-bridge	| PCI MCA	| PCI VGA	 	| PCI SCSI bus	
> Latency timer	| 20		| 20		| 50		| 00		| 00		| 00		| 40
> Interrupt pin	| 0		| 1		| 1		| 0		| 0		| 1		| 1
> Interrupt line	| 0		| F		| A		| FF		| 0		| 0		| B
> Mem addr.	| -		| 40000080	| 40000000	| 500		| -		| 38000000	| 30000000
> I/O addr.		| -		| 9080		| 9000 		| -		| 508 & 510	| -		| C00
> 
> I used the kernels from Debian 2.2r2 and 2.2r6.
> 
> Is there a way to enable the PCI-slots??
> 
> Thanks for any help,
> Frank.

> Linux version 2.2.19 (herbert@gondolin) (gcc version 2.7.2.3) #1 Sat Jun 9 13:04:06 EST 2001
> BIOS-provided physical RAM map:
>  BIOS-88: 0009f000 @ 00000000 (usable)
>  BIOS-88: 03f00000 @ 00100000 (usable)
> Detected 133314 kHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 265.42 BogoMIPS
> Memory: 60788k/65536k available (1744k kernel code, 412k reserved, 996k data, 156k init)
> Dentry hash table entries: 8192 (order 4, 64k)
> Buffer cache hash table entries: 65536 (order 6, 256k)
> Page cache hash table entries: 16384 (order 4, 64k)
> VFS: Diskquotas version dquot_6.4.0 initialized
> CPU: Intel Pentium 75 - 200 stepping 0c
> Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
> Checking 'hlt' instruction... OK.
> Checking for popad bug... OK.
> Intel Pentium with F0 0F bug - workaround enabled.
> POSIX conformance testing by UNIFIX
> PCI: PCI BIOS revision 2.10 entry at 0xfd82c
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Unable to handle I/O allocation for 00:40 (0200), tell <mj@ucw.cz>
> Micro Channel bus detected.
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> TCP: Hash tables configured (ehash 65536 bhash 65536)
> Starting kswapd v 1.5 
> Detected PS/2 Mouse Port.
> Serial driver version 4.27 with no serial options enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> pty: 256 Unix98 ptys configured
> Real Time Clock Driver v1.09
> RAM disk driver initialized:  16 RAM disks of 4096K size
> loop: registered device at major 7
> Floppy drive(s): fd0 is 1.44M
> FDC 0 is a National Semiconductor PC87306
> md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
> sim710: No NCR53C710 adapter found.
> (scsi0) <Adaptec AIC-7870 SCSI host adapter> found at PCI 0/12/0
> (scsi0) Narrow Channel, SCSI ID=7, 16/255 SCBs
> (scsi0) Downloading sequencer code... 415 instructions downloaded
> scsi: <fdomain> Detection failed (no card)
> NCR53c406a: no available ports found
> sym53c416.c: Version 1.0.0
> Failed initialization of WD-7000 SCSI card!
> IBM MCA SCSI: Version 3.2
> IBM MCA SCSI: IBM SCSI-2 F/W Adapter found in slot 6, io=0x3540, scsi id=7,
>               ROM Addr.=off, port-offset=0x0, subsystem=enabled.
> IBM MCA SCSI: Combined bus mode (wide-addressing disabled)
> IBM MCA SCSI: Sync.-Rate (F/W: 20, Int.: 10, Ext.: 10.00) MBytes/s
> IBM MCA SCSI: Removing default logical SCSI-device mapping.
> IBM MCA SCSI: Probing SCSI-devices (this can take up to 2 minutes).
> IBM MCA SCSI: Mapping SCSI-devices.
> IBM MCA SCSI: Device order: New Industry Standard (pun=0 is first).
> megaraid: v1.11 (Aug 23, 2000)
> aec671x_detect: 
> 3w-xxxx: tw_findcards(): No cards found.
> scsi0 : Adaptec AHA274x/284x/294x (EISA/VLB/PCI-Fast SCSI) 5.1.33/3.2.4
>        <Adaptec AIC-7870 SCSI host adapter>
> scsi1 : IBM SCSI-Subsystem
> scsi : 2 hosts.
>   Vendor: IBM       Model: DCHS04U           Rev: 2727
>   Type:   Direct-Access                      ANSI SCSI revision: 02
> Detected scsi disk sda at scsi1, channel 0, id 1, lun 0
> scsi : detected 1 SCSI disk total.
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 8813870 [4303 MB] [4.3 GB]
> Partition check:
>  sda: sda1 sda2 < sda5 sda6 >
> RAMDISK: Compressed image found at block 0
> apm: BIOS not found.
> EXT2-fs warning: checktime reached, running e2fsck is recommended
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 156k freed
> kmod: runaway modprobe loop assumed and stopped
> kmod: runaway modprobe loop assumed and stopped
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> VFS: Disk change detected on device fd(2,0)
> VFS: Can't find an ext2 filesystem on dev fd(2,0).
> VFS: Can't find a Minix or Minix V2 filesystem on device 02:00.


-- 
To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: