|
Bugzilla – Full Text Bug Listing |
| Summary: | Dell Latitude c400 doesn't boot after update from Beta 3 | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Lars Müller <lmuelle> |
| Component: | Installation | Assignee: | Hannes Reinecke <hare> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | aj, hare, jsrain, snwint |
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Full hwinfo of the dell c400
lspci -vv tar ball of /var/log/YaST2/ |
||
|
Description
Lars Müller
2005-08-31 18:22:52 UTC
Created attachment 48354 [details]
Full hwinfo of the dell c400
Created attachment 48355 [details]
lspci -vv
mkinitrd -> hare (vacation) -> agruen I think we'll need the notebook to analyze the problem further; at least we need additional information. What does /etc/sysconfig/kernel:INITRD_MODULES contain? YaST is supposed to fill in the appropriate modules here; mkinitrd then uses this list. Maybe the YaST logs of the update would help? INITRD_MODULES="jbd ext3" I set it now to get the laptop up again to INITRD_MODULES="piix jbd ext3" Created attachment 48572 [details]
tar ball of /var/log/YaST2/
Andreas, please check out this bug, your requested information arrived, critical bugs should be solved soon. Yast did set INITRD_MODULES wrong. Reassigning to the Yast2 people. Hmm, the log doesn't contain the interesting part of installation :-( Trying to reproduce to get the correct part of the log... Put piix to INITRD_MODULES, did an update, and it was kept there. Sorry, but without logs containing whole update, I can't help here... The point is that the required hardware modules _always_ have to be in INITRD_MODULES. This affects updates on IDE machines, where previously the required modules have been added automatically by mkinitrd. YaST should check whether the required module is already present in INITRD_MODULES and add them if not. Please understand that problems with specific notebook-models are critical at best at the moment because it affects not much people. This is not a problem restricted to a specific notebook model as Hannes mentioned in comment #11. If YaST doesn't have any code to remove piix from /etc/sysconfig/kernel:INITRD_MODULES, then piix never was there. That's also the information I got from the etc.sysconfig-DATE.tar.gz backups from /var/adm/backup Jiri: Have you read Hannes comment? When we added piix automatically while creating the initrd and now no longer, then YaST has to fix this. The one who is (on YaST's side) responsible to add a module to initrd is the one who finds it needed - in this case, partitioner knows which disk contains the / partition and to which adapter it is connected. Thomas? Arvin? Need y2log files. To my knowledge there is no mechanism that adds the "piix" to INITRD_MODULES during update. So unless mkinitrd adds it, I would expect every update to fail booting if module piix is needed. No idea how this can be fixed. Reassigning to aj since I assume that the fact that every IDE system will not boot after update will not please him very much. Re-enabled scan for IDE devices in mkinitrd. Fixed mkinitrd submitted to STABLE. |