Bug 48725

Summary:	i2c-i801 module don't load with kernel-2.4.3-12
Product:	[Retired] Red Hat Linux	Reporter:	Holger Hoffmann <hohoff>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.1
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 15:39:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Holger Hoffmann 2001-07-11 09:38:51 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.73 [en] (X11; I; Linux 2.2.9-2 i586)

Description of problem:
on a Asus CUSL2-C motherrboard with an intel 815EP chipset the i2c-i801
module don't load. The error message is:

i2c-i801.o version 2.5.5 (20010115)
i2c-i801.o: Error: Can't detect I801, function 3!
i2c-i801.o: I801 not detected, module not inserted.

This is with the kernel-2.4.3-12. It is all o.k. if I use the
kernel-2.4.2-2.

How reproducible:
Always

Steps to Reproduce:
1. boot a rh7.1 system with the kernel-2.4.3-12
2. modprobe i2c-i801
3.
	

Additional info:

Comment 1 Peter Verthez 2001-12-16 14:08:30 UTC

Idem in 2.4.9-12 (the latest official Red Hat 7.1 kernel).  This worked
with the standard 7.1 kernel before I upgraded to the newest kernel.

The error messages now are:

voyager_root:~# insmod i2c-i801
Using /lib/modules/2.4.9-12/kernel/drivers/i2c/i2c-i801.o
/lib/modules/2.4.9-12/kernel/drivers/i2c/i2c-i801.o: init_module: No such
deviceHint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters

Comment 2 Bugzilla owner 2004-09-30 15:39:04 UTC

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/