Bug 135650 - YAST2 detects modem0 allthough no modem is connected
Summary: YAST2 detects modem0 allthough no modem is connected
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: i686 SuSE Linux 10.0
: P5 - None : Minor
Target Milestone: ---
Assignee: E-mail List
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-28 09:47 UTC by Karl-Anton Schmitz
Modified: 2008-06-25 09:53 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Karl-Anton Schmitz 2005-11-28 09:47:30 UTC 
I expect an error message if ttyS0 (on which the modem is connected) is disabled by bios. When serial i/o was enabled by bios the modem was connected sucessfully with its correct name.
Comment 1 Martin Lasarsch 2005-11-28 11:38:48 UTC 
please provide some information:

hwinfo --modem

when it's disabled in bios.
Comment 2 Michael Gross 2005-12-09 04:38:15 UTC 
Please reopen this bug if the requested information can be provided. I'll close this bug as a reminder now.
Comment 3 Stephan Kulow 2008-06-25 09:34:12 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 4 Stephan Kulow 2008-06-25 09:36:00 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 5 Stephan Kulow 2008-06-25 09:41:40 UTC 
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 6 Stephan Kulow 2008-06-25 09:53:06 UTC 
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(