Bugzilla – Bug 135612
installation on Asus K8S-MX require manual creation of initrd
Last modified: 2007-08-11 15:37:42 UTC
+++ This bug was initially created as a copy of Bug #116747 +++ The bug is confirmed in 10.0 final. At boot the ssystem freeze failing in waiting for the hard disk to appear. You need to manualy modify /etc/sysconfig/kernel and recreate the initrd file including - in addition to sis5513 jdb ext3 processror fan - also ide-generic; After that the system finally boots. I hope that you are able to get it fixed by the time SuSE 10.0 final ships. regards, Blackdir
It is indeed true that ide-generic should be included as a fallback in the initrd/initramfs to allow to mount the root filesystem when the IDE controller isn't specifically supported, however here it seems that the SiS driver is not detecting the IDE chipset on this board. Which exact chipset does the board have? Is the disk connected to IDE or SATA? Can you provide the output of 'lspci -vvxxx' and 'dmesg -s 10000' on a booted system?
Please answer the questions from comment #1.
Created attachment 59607 [details] PCI output
You are right: the installation process was not able to detect the IDE chipset and I was asked to enter in the manual configuration. In manual configuration as soon as I added the ide-generic module the system was able to recognize both the HD and the CD and it was possible to complete the installation process. For this reason the only problem (IMHO) was that the installation process forgot to add the ide-generic module that I selected in the creation of initrd. Anyhow, to answer to you questions: - As shown on ASUS web site (http://www.asus.com/products4.aspx?modelmenu=2&model=377&l1=3&l2=14&l3=149) the southbridge is based on SiS 965L (2 IDE, 2 SATA) - the disk I installed suse 10 in was IDE Attached two files containing the requested output (which I got booting the system from DVD with rescue option) Let me know if you need further info
Created attachment 59608 [details] dmesg output
*** Bug 116747 has been marked as a duplicate of this bug. ***
I'll need the full dmesg, particularly the IDE detection messages, and the module list on the running machine.
Created attachment 61030 [details] tar file of proc filesystem
As I'm debugging using the rescue kernel from boot CD, dmesg outcome is null. In order to satisfy your request I'm attaching a tar file of /proc/*. I guess that you can read IDE outcome from there as well as running modules. As I mentioned before it is the ide-generic module that I loaded manually that allow me to access to the ide disk.
If PnP is modified NOT to disable the parallel port device on module unload, then everything works fine.
Oops, wrong bug.
Is this still a problem with 10.2?
No reaction since more than 2 months, therefore closing as CANTFIX (aka WONTFIX). If you can provide the needed information, feel free to reopen the bug.