Bug 163577

Summary:	Kudzu fails to find serial modem during boot or running in shell
Product:	[Fedora] Fedora	Reporter:	Colin Hawke <colin>
Component:	kudzu	Assignee:	Bill Nottingham <notting>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4	CC:	h4x3r, rvokal
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:	2006-05-05 20:35:26 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 Colin Hawke 2005-07-19 03:42:14 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Start machine with modem on.
2.Attempt to configure modem in kppp
3.Run kudzu with modem off
4.Run kudzu with modem on
  

Actual Results:  Modem can't be found in kppp

Kudzu keeps asking for root password which it won't accept.

Expected Results:  Modem should be available for use.

Additional info:

Comment 1 Bill Nottingham 2005-07-19 17:59:20 UTC

kudzu doesn't ask for the root password - are you sure it's not kppp?

Comment 2 Colin Hawke 2005-07-19 23:50:52 UTC

No it's not kppp, it is kudzu being run in a shell. A message saying that kudzu
requires more information before it proceeds displays followed by a password:
prompt. The root password isn't accepted and the password: prompt re-appears.

Prior to Fedora Core 3, the modem installed perfectly on the same machine and
ran without any problems. Fedora Core 3 required a process of turning the modem
off, run Kudzu, turn modem on, run Kudzu, and then the modem would work. Fedora
4 - not detecting at all.

Comment 3 Bill Nottingham 2005-07-20 01:06:56 UTC

(In reply to comment #2)
> No it's not kppp, it is kudzu being run in a shell. A message saying that kudzu
> requires more information before it proceeds displays followed by a password:
> prompt. The root password isn't accepted and the password: prompt re-appears.

This is baffling. There's *nothing* in kudzu that would prompt for a password.

Comment 4 h4x3r 2005-07-21 01:51:29 UTC

Kudzu will in fact write data to hwconfig however, the driver is never loaded.
This makes me believe it may be the kernel not loading the correct data from
hwconfig.

however, as Colin Hawke pointed out, in my case, if there is a conflict of 
modules e,g; "nvidiafb and the official nvidia driver (currently) 7667" the 
system halts at Kudzu (on boot) and issues an error that you are trying to 
modify system-config-display "enter root password" which it will not allow you 
to enter a password and a system reboot is warranted.

The only way around this issue was to bypass kudzu and hand edit hwconf for the
official nvidia driver also having to delete the default nvidiafb module a
(conflict issue) if you will.

This is indeed not very good and yes, baffling.

Comment 5 Bill Nottingham 2005-09-28 21:29:47 UTC

Back to the original issue - what sort of modem? USB? Serial?

Comment 6 John Thacker 2006-05-05 20:35:26 UTC

Closing due to lack of response by reporter.