Bug 151813 - Package Selection of Installtion still doesn't work correctly for laptops without PCMCIA controllers
Summary: Package Selection of Installtion still doesn't work correctly for laptops wit...
Status: RESOLVED FIXED
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 4
Hardware: Other Other
: P5 - None : Blocker (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-17 14:21 UTC by Daniel Gollub
Modified: 2006-03-09 14:33 UTC (History)
4 users (show)

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


Attachments
yast logs of intel development laptop (4.10 MB, application/x-gunzip)
2006-02-17 15:50 UTC, Daniel Gollub
Details
YaST logs of Medion MIM2080 - no PCMCIA controller (2.54 MB, application/x-gunzip)
2006-02-17 15:53 UTC, Daniel Gollub
Details
hwinfo --sys on Intel Development Laptop (no pcmcia) (327 bytes, application/octet-stream)
2006-02-28 16:29 UTC, Daniel Gollub
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Gollub 2006-02-17 14:21:02 UTC
On Laptops without PCMCIA slots the Package Selection will not install the Package  Group Laptop by default. It seems that YaST still checks for a PCMCIA controller.
There exists many subnotebooks without PCMCIA. YaST should only check for the formfactor of HAL. 

The network module of YaST seems to have (meanwhile) no problem by detecting a laptop (independent of PCMCIA), NetworkManager is select by default. You can find these discssion at #149976 and #149909

Do you need yast logs of the laptops without PCMCIA or further information?
Comment 1 Klaus Kämpf 2006-02-17 15:21:10 UTC
Its quite hard to prove/deny you assumptions without logs ...
Comment 2 Michael Gross 2006-02-17 15:38:50 UTC
Well... just to be on the safe side: Daniel, please attach the logs, I'll reassign it afterwards.
Comment 3 Danny Al-Gaaf 2006-02-17 15:42:56 UTC
IMO Yast does not use HAL to check if the machine is a laptop (if it would this should not happen because the machines are correct detected in HAL). But it should.

See fate feature #100199. This was implemented in HAL someone in the last year. You should check hal for key system.formfactor=laptop. This should detect nearly all machines.
Comment 4 Klaus Kämpf 2006-02-17 15:48:25 UTC
YaST uses hwinfo which should use HAL
Comment 5 Daniel Gollub 2006-02-17 15:50:28 UTC
Created attachment 69070 [details]
yast logs of intel development laptop
Comment 6 Daniel Gollub 2006-02-17 15:53:07 UTC
Created attachment 69072 [details]
YaST logs of Medion MIM2080 - no PCMCIA controller
Comment 7 Martin Vidner 2006-02-20 09:20:40 UTC
Klaus, yast uses .probe.has_pcmcia (via Arch::has_pcmcia()) from hwinfo. IMO it would be confusing to change the semantics of this to mean "laptop". Yast (Packages.ycp) should use the new API.

Implementation note: .probe.system is a LIST (singleton?) of maps.
Comment 8 Michael Gross 2006-02-20 09:56:06 UTC
Steffen: Can you provide a comment here?
Comment 9 Danny Al-Gaaf 2006-02-20 11:25:20 UTC
I hate this changes of the BST. This is a blocker since the most new laptops has no PCMCIA slot.
Comment 10 Steffen Winterfeldt 2006-02-20 14:31:07 UTC
hwinfo reads the formfactor entry from hal and provides it via
.probe.system (I think). The ancient .probe.has_pcmcia should not
be used as a base for laptop detection (it was never intended for this -
it originates from times where we had a special 'laptop' kernel with pcmcia
compiled in).
Comment 11 Michael Gross 2006-02-20 14:51:28 UTC
Jiri: I suppose this is something for you. If not please assgign it back to us.
Comment 12 Martin Vidner 2006-02-20 14:56:25 UTC
Please use Arch::is_laptop () which I will submit shortly.
Comment 13 Martin Vidner 2006-02-20 15:56:55 UTC
Stano fixed it.
Comment 14 Daniel Gollub 2006-02-27 22:22:57 UTC
It is still not working for non-pcmcia machines in beta 5.

Is the fixed package of yast (>= 2.13.31) also in the installtion system of beta5?

When i check for package version after installtion (beta5) it seems to be the package which should fix this problem (Version 2.13.31). Maybe on the installtion system is an older version of the yast package?

Please close this bug when the version of yast, on the installtion system of beta5, is less then 2.13.31.
Comment 15 Martin Vidner 2006-02-28 08:29:51 UTC
The correct version is there.
Either the detection is wrong or the triggered action is wrong.
Try "hwinfo --sys" on the second console during the installation to check.

If it detects the laptop formfactor then I guess the problem is with activating the proper selection/pattern -> jsrain. There the identity of the product that you are testing matters too.
Comment 16 Daniel Gollub 2006-02-28 16:28:39 UTC
hwinfo returns formfactor: laptop

See attachment.
Comment 17 Daniel Gollub 2006-02-28 16:29:24 UTC
Created attachment 70667 [details]
hwinfo --sys on Intel Development Laptop (no pcmcia)
Comment 18 Jiri Srain 2006-02-28 20:38:48 UTC
This looks correctly. I added check to the same place in code where laptop was being checked, hope it helps.

This fix will not be included in Beta6, but in following version.
Comment 19 Daniel Gollub 2006-03-09 14:33:23 UTC
in beta 7 it works now perfectly!
thanks!