Bug 157972
Summary: | Crash with S3 Trio video card: KeyError: 'S3 Trio3D\nS3 Trio64 3D' | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dave Habben <dave.habben> |
Component: | hwdata | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | adamlau_au, ade_bisi, cajunman4life, johnlumby, rvokal, shadik79, thomson, trex |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 0.159-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-25 13:57:31 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: | |||
Bug Depends On: | |||
Bug Blocks: | 163907 |
Description
Dave Habben
2005-05-17 15:12:20 UTC
What does running ddcprobe provide? ddcprobe results from Fedora Core 3 (Which installs correctly) Videocard DDC probe results Description: S3 Incorporated. Trio3D Memory (MB): 4 Monitor DDC probe results ID: NEC65c6 Name: NEC LCD1550V Horizontal Sync (kHZ): 31-60 Vertical Sync (HZ) : 55-75 Width (mm): 300 Height(mm): 230 ddcprobe results from Fedora 4, test 3 Videocard DDC probe results Description: S3 Incorporated. Trio3D Memory (MB): 4 Monitor DDC probe results ID: NEC65c6 Name: NEC MultiSync LCD1550V Horizontal Sync (kHZ): 31-60 Vertical Sync (HZ) : 55-75 Width (mm): 300 Height(mm): 230 This really looks like something getting corrupted somewhere. Did your media pass mediacheck (http://rhlinux.redhat.com/anaconda/mediacheck.html)? Yes, I tested all four discs and the result on all of them was: PASS I have the exact same problem with fc4-test3 and the s3 trio video card. I'm using the dvd image and the media check passed. I received the same error message as Dave I have same problem on an IBM 300PL witrh integrated S3 video. Installing from CD-ROM fc4-test3. As in the examples above, all media passed checks and I received the identical error message string. Videocard DDC probe results Description: S3 Incorporated. Trio3D Memory (MB): 4 Monitor DDC probe results ID: @@@0000 Name: O\uffff\uffff\uffff Width (mm): 320 Height(mm): 240 I am experiencing the same problem on an IBM Netfinity 3000 with integrated S3 video. fc4-test3. Media check also passes for CD installation media, I am booting from CD-1. Same problem happens with the final release of fc4 I have the same problem with the final release of FC4. Mediacheck passes for all CDs. Everything is working fine with FC3. It is an IBM 300PL machine. ======= ddcprobe from FC3 ======= Videocard DDC probe results Description: S3 Incorporated. Trio3D Memory (MB): 4 Monitor DDC probe results ID: @BM1996 Name: IBM P76 Horizontal Sync (kHZ): 30-94 Vertical Sync (HZ) : 48-120 Width (mm): 330 Height(mm): 240 ======================================== I also have the same problem with an IBM 300GL with an integrated S3 Trio3D\nS3 Trio64 3D. I'm using FC4. The problem here is in hwdata/Cards around line 1299. There needs to be at least one blank line separating the "S3 Trio 3D" entry and the "S3 Trio64 3D" entry. Comment lines don't count. This is required by the algorithm in videocard.py:VideoCardInfo.readCardsDB The workaround I am using is to install with "linux headless". I used "linux pci=off" - the installer will detect the video card as generic VESA. The installation completed fine. After reboot GNOME started without any issues. But the ethernet card was not detected. Moreover, running Kudzo to detect the hardware gives the same error shown above! In FC4 release notes: "Some Sony VAIO® notebook systems may experience problems installing Fedora Core from CD-ROM. If this happens, restart the installation process and add the following option to the boot command line: pci=off ide1=0x180,0x386" I only used pci=off without the ide1 option (would that cause something?). Anyway, I would not recommend trying out this option (to solve this S3 problem) unless confirmed by someone more experienced in this issue! Reassigning to hwdata on the basis of comment #11. Added in CVS, will be in 0.159-1 (not very helpful for the installer, I realize.) I am also working on an IBM 300PL with integrated S3 video. When adding the pci=off (with or without ide1=0x180,0x386) option the installation hangs after a series of similar messages with the last one being: [<c01012b1>] kernel_thread_helper+0x5/0x14 nothing happens after this and only remedy is turning off the box. *** Bug 163256 has been marked as a duplicate of this bug. *** I have an IBM xSeries 240 server and installed FC4. Installation failed with similar messages as have been documented in previous postings. I used various options provided in the Release notes but none of them work. It asked me to manually select device drivers to load which I did. The installer says it cannot find any hard drive device to create partition. It then exit abnormally. All the four discs passed verification. My system information reports that the machine has S3 Inc. Trio3D. The original error I got without using any of the boot options is KeyError: 'S3 Trio3D\nS3 Trio64 3D' As stated before: ... Added in CVS, will be in 0.159-1 (not very helpful for the installer, I realize.) ... It's fixed in rawhide, the development tree. How can one get this fix to install? Or when will 0.159-1 be available? Is it possible to create installation discs from the development tree? Please advice. Until you have a release with this fix, you can avoid the problem by: 1. Invoke the installer with "linux headless". This gives a text mode install. 2. When the system tries to reboot after, Kudzu will fail with the same message. Edit the file /usr/share/hwdata/Cards inserting the blank line. 3. Rerun kudzu and continue. Don't use pci=off, it skips configuring much more than your video. (In reply to comment #20) > How can one get this fix to install? You'd have to create an update disk with the new Cards file. > Or when will 0.159-1 be available? It's already in the devel tree. After two attempts, I was finally able to get anaconda to install FC4 on IBM xSeries 240 server in text mode. I edited file /usr/share/hwdata/Cards inserting the blank line as suggested. I then ran kudzu, supplying the root password when prompted. However, kudzu kept coming back with Permission denied even though the root password I supplied is correct. I have SELinux enabled (active) during installation. I do not know if this has anything to do with 'Permission denied' I'm getting. If like me your machine can't boot from CD-Rom, then you are probably using the Generic Linux Boot Floppy. In that case, I discovered that the way to get it to invoke the anaconda with this "headless" option is to edit the kernel.opt on the diskette and edit the keyword parm --append=askmethod to --append=headless mv /tmp/dkt/kernel.opt /tmp/dkt/kernel.opt.askmethod; sed -e "s/askmethod/headless/g" /tmp/dkt/kernel.opt.askmethod >/tmp/dkt/kernel.opt Hello everyone, I too have a IBM PC 300PL. I was able to get Fedora with the GUI to work on my system. I had to piece together the various comments from Brian Thomson. I used the "headless" option in the installer. I did not use pci=off. I edited the "cards" file. I also downloaded a kernel update and I ran "rpm" on it. I could not "yum" on that kernel update. Please see Bill Nottingham's comment. Also, I had to do some extra steps. I just want to share these with the Fedora (Linux) community. I had to run "system-config-display" from the /usr/share/system-config-display directory. I could not simply re-run kudzu. "kudzu" failed to do anything useful for me. Also, since I followed Brian's comments and used the "headless" install option, I did not have a system that would automatically boot into the GUI. I had to edit one line in the "inittab". I had to change the line: id:3:initdefault: to: id:5:initdefault: Once I did all that, I had GNOME working and everything. I could login as root. I could add normal user accounts. I have everything I want except support for the on-board Crystal Semiconductor sound card and internal speaker. I think I'll just get a cheap SoundBlaster card and speakers. I'll try telling the BIOS to ignore the on-board sound card. I'll hunt and peck the BIOS setup for that option. lol... Thanks everyone for all your helpful comments!!!!!! Sincerely, Roger |