Bug 160667 - Installation impossible on Sony VAIO Z600
Installation impossible on Sony VAIO Z600
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-06-16 10:37 EDT by Duncan Innes
Modified: 2015-01-04 17:20 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-30 17:08:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Screenshot of crash info (547.25 KB, image/jpeg)
2005-06-16 15:04 EDT, Duncan Innes
no flags Details

  None (edit)
Description Duncan Innes 2005-06-16 10:37:03 EDT
Description of problem:
Attempt installation from CD-ROM on VAIO Z600TEK

Version-Release number of selected component (if applicable):
Direct installation from the FC4 final CD's

How reproducible:
Every installation method has failed so far

Steps to Reproduce:
1. Boot machine with CD 1 in CD drive
2. type "linux ide2=0x180,0x386" at prompt
3. press ahead with installation

Actual results:
During package installation, the machine will crash.  Don't know if this is
linked to a specific package as yet as I've not been in the room when the
crashes have happened.

Expected results:
Expected installation to run through easily - as happened with the FC3 install
directly after so that I could actually use the machine.

Additional info:
I took photo's of the Ctrl+Alt+F3 and Ctrl+Alt+F4 screens after the crash.  I
will attach these images once I've managed to get them downloaded from my phone.
 They contained information about the Call Trace and "setting file_context_path"

I've also been unable to perform a network install on this machine as describer
in bug 158165 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=158165

I will try a HD based install when I can, but I don't hold out much hope.
Comment 1 Duncan Innes 2005-06-16 15:04:25 EDT
Created attachment 115558 [details]
Screenshot of crash info

Can't remember which screen I grabbed this from (Ctrl+Alt+F3 or Ctrl+Alt+F4).

Comment 2 Dave Jones 2005-07-07 19:22:22 EDT
could you boot with vga=791 (or vga=1 if that doesnt work), and try and get 1-2
more lines above that oops ?
Comment 3 Dave Jones 2005-07-15 17:47:45 EDT
[This comment has been added as a mass update for all FC4 kernel bugs.
 If you have migrated this bug from an FC3 bug today, ignore this comment.]

Please retest your problem with todays 2.6.12-1.1398_FC4 update.

If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..

mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak

Thank you.
Comment 4 Duncan Innes 2005-09-30 15:58:42 EDT
It's a long time I know, but I've managed to find time to attempt a re-install.

I did NOT use the official Fedora Core 4 CD's though.  Instead I used the
recently release unofficial CD's (with all the rpm's updated to the current set).

This has fixed the problem completely.

Has the installation kernel changed perhaps?
Comment 5 Dave Jones 2005-09-30 17:08:41 EDT
yes, it would have one of the errata kernels.

Comment 6 Dave Jones 2005-09-30 17:09:52 EDT
actually, can you give me a pointer to where that can be downloaded ?
It may be useful for me to point some other bug reports at.
Comment 7 Duncan Innes 2005-09-30 17:40:40 EDT


It's basically the original ISO's with the RPM's replaced with the latest FC4
rpm updates.

Seemed like a good idea to update the ISO's every now and again, but the idea
has been turned down evidently.

It's clear that in this instance, however, that I would not have been able to
perform an FC4 install unless someone created an unofficial update ISO set.

Hope this helps


Note You need to log in before you can comment on or make changes to this bug.