[Bug 577813] New: Fedora 13 Alpha x86_64 Produces Blank Screen during installation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: Fedora 13 Alpha x86_64 Produces Blank Screen during installation

https://bugzilla.redhat.com/show_bug.cgi?id=577813

           Summary: Fedora 13 Alpha x86_64 Produces Blank Screen during
                    installation
           Product: Fedora
           Version: rawhide
          Platform: x86_64
        OS/Version: All
            Status: NEW
          Severity: urgent
          Priority: low
         Component: Package Review
        AssignedTo: nobody@xxxxxxxxxxxxxxxxx
        ReportedBy: bugproxy@xxxxxxxxxx
         QAContact: extras-qa@xxxxxxxxxxxxxxxxx
                CC: notting@xxxxxxxxxx, fedora-package-review@xxxxxxxxxx
   Estimated Hours: 0.0
    Classification: Fedora
    Target Release: ---


IBM Bug Proxy <bugproxy@xxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
    External Bug ID|                            |IBM Linux Technology Center
                   |                            |61628

=Comment: #0=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 
The Fedora 13 Alpha x86_64 (ISO taken from
http://software.linux.ibm.com/pub/fedora/releases/test/13-Alpha/Fedora/x86_64/iso/)
produces Blank
screen during Installation process. Created the following entry in
/boot/grub/menu.lst on  an
existing Distro:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd1,0)
#          kernel /boot/vmlinuz-version ro root=/dev/sdb1
#          initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=30
splashimage=(hd1,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.18-190.el5xen)
        root (hd1,0)
        kernel /boot/xen.gz-2.6.18-190.el5 crashkernel=128M@32M
        module /boot/vmlinuz-2.6.18-190.el5xen ro root=LABEL=/1234 rhgb quiet
        module /boot/initrd-2.6.18-190.el5xen.img
title Red Hat Enterprise Linux Server-base (2.6.18-190.el5)
        root (hd1,0)
        kernel /boot/vmlinuz-2.6.18-190.el5 ro root=LABEL=/1234 rhgb quiet
        initrd /boot/initrd-2.6.18-190.el5.img
title F13 X86_64 Aplha Installation
        root (hd1,0)
        kernel /boot/vmlinuz-f13alpha-installation askmethod vnc ro
root=LABEL=/1234 rhgb quiet
        initrd /boot/initrd-f13alpha-installation

When I install, shortly after going through the usual booting up messages,
after /sbin/loader and
then, detecting hardware, F13 Alpha x86_64 Produces Blank Screen during
installation. Tried removing
askmethod & vnc arguments, but still it did not work.

Regards--
Subrata
=Comment: #1=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 
Fedora community mailing list also reported similar issue(s) with other
hardwares. However, somebody
suggested booting with ACPI=off. I tried the same. Now, i could see a hung
screen with the attached
BACKTRACE info.

Regards--
Subrata

=Comment: #2=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 

Backtrace on F13 Alpha Installation


=Comment: #3=================================================
Edward E. Pollard <edpollar@xxxxxxxxxxxxx> - 
could you try  booting with acpi=noirq ?

What type of hardware is this on other than x86_64? Video card? Machine
type/model? processor?


=Comment: #4=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 
Even acpi=noirq did not help.
=Comment: #5=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 
Here goes the results of much broader testing scenarios:
==================================================
Kernel-Args    vnc askmethod serial radeon.modeset=0
Serial-Console-Enabled  yes
Parallel Console-status  Screen Shows up
VNC Installation   YES
Modify Partition Layout  YES
Final Conclusion   VNC screen hangs after creating some Layout
==================================================
Kernel-Args    vnc askmethod serial
Serial-Console-Enabled  yes
Parallel Console-status  Blank Screen
VNC Installation   YES
Modify Partition Layout  YES
Final Conclusion   VNC screen hangs after creating some Layout
==================================================
Kernel-Args    vnc askmethod serial
Serial-Console-Enabled  yes
Parallel Console-status  Blank Screen
VNC Installation   YES
Modify Partition Layout  NO
Final Conclusion   Packages Chosen,
      Bug generated after all Packages were Installed
==================================================
Kernel-Args    vnc askmethod serial radeon.modeset=0
Serial-Console-Enabled  yes
Parallel Console-status  Screen Shows up
VNC Installation   YES
Modify Partition Layout  NO
Final Conclusion   Packages Chosen,
      Bug generated after all Packages were Installed
==================================================
Kernel-Args    askmethod serial
Serial-Console-Enabled  yes
Parallel Console-status  Blank Screen
VNC Installation   NO
Modify Partition Layout  NO
Final Conclusion   Bug generated even before Packages Installation
==================================================
Kernel-Args    askmethod vnc radeon.modeset=0
Serial-Console-Enabled  NO
Parallel Console-status  Screen Shows up
VNC Installation   YES
Modify Partition Layout  YES
Final Conclusion   VNC screen hangs after creating some Layout
==================================================
Kernel-Args    askmethod vnc radeon.modeset=0
Serial-Console-Enabled  NO
Parallel Console-status  Screen Shows up
VNC Installation   YES
Modify Partition Layout  NO
Final Conclusion   Minimal Installation Reboots, Sytem installed only in text
mode
==================================================

I can conclude the following problems:

1) VNC installation will always hang if you choose Partitioning Layout,
2) VNC installation will hang at the end of Packages installation if you choose
any Graphical Packages,
3) TEXT mode installation through Serial console bugs out even before starting
to format default
partitioning Layout,
4) Screen will always black out if the kernel boot parameter is not
radeon.modeset=0,

Sachin,

Should we be raising separate bugs for each of them ?

Also, following was the Partitioning Layout tried:
/boot - 2048MB - Forced as Primary,
/         - 20000MB - Primary/non-primary,
swap - 8192MB - non-primary,
1st 10000MB LVM - non-primary,
2nd 10000MB LVM - non-primary,
3rd 10000MB LVM - non-primary,
4th 10000MB LVM - non-primary,
VNC hangs here everytime.

Please note that the Disk Size if 136GB, so, space is still in plenty,
Machine Info:
mx3650b.in.ibm.com (sdb only),
Model: 7979,
platform: x86_64,
Serial No: 99k1161,

Regards--
Subrata

=Comment: #6=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 

/tmp/anaconda.log when VNC hangs at Partitioning Layout


=Comment: #7=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 

/tmp/anaconda-yum.conf when VNC hangs at Partitioning Layout


=Comment: #8=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 

/tmp/syslog when VNC hangs at Partitioning Layout


=Comment: #9=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 

VNC Default Paritioning Layout, Anaconda bug report post Packages Installation,
and, before reboot


=Comment: #10=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 

Text Mode Default Paritioning Layout, default Packages, Anaconda bug report
pre-installation


=Comment: #11=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 
The text Mode Serial Console Installation Bug is now tracked through a separate
report:
https://bugzilla.linux.ibm.com/show_bug.cgi?id=61716,

Regards--
Subrata

=Comment: #13=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 
Ok. The summary goes here:

The Fedora 13 Alpha x86_64 (ISO taken from
http://software.linux.ibm.com/pub/fedora/releases/test/13-Alpha/Fedora/x86_64/iso/)
produces Blank screen during Installation process. Created the following entry
in /boot/grub/menu.lst on  an existing Distro:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You do not have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /, eg.
#          root (hd1,0)
#          kernel /boot/vmlinuz-version ro root=/dev/sdb1
#          initrd /boot/initrd-version.img
#boot=/dev/sda
default=0
timeout=30
splashimage=(hd1,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.18-190.el5xen)
        root (hd1,0)
        kernel /boot/xen.gz-2.6.18-190.el5 crashkernel=128M@32M
        module /boot/vmlinuz-2.6.18-190.el5xen ro root=LABEL=/1234 rhgb quiet
        module /boot/initrd-2.6.18-190.el5xen.img
title Red Hat Enterprise Linux Server-base (2.6.18-190.el5)
        root (hd1,0)
        kernel /boot/vmlinuz-2.6.18-190.el5 ro root=LABEL=/1234 rhgb quiet
        initrd /boot/initrd-2.6.18-190.el5.img
title F13 X86_64 Aplha Installation
        root (hd1,0)
        kernel /boot/vmlinuz-f13alpha-installation askmethod vnc ro
root=LABEL=/1234 rhgb quiet
        initrd /boot/initrd-f13alpha-installation

When I install, shortly after going through the usual booting up messages,
after /sbin/loader and then, detecting hardware, F13 Alpha x86_64 Produces
Blank Screen during installation. Tried removing askmethod & vnc arguments, but
still it did not work.
Fedora community mailing list also reported similar issue(s) with other
hardwares. However, somebody suggested booting with ACPI=off. I tried the same.
Now, i could see a hung screen with the attached BACKTRACE info.
Even acpi=noirq did not help,

Machine Info:
mx3650b.in.ibm.com (sdb only),
Model: 7979,
platform: x86_64,
Serial No: 99k1161,

There is a similar bug on Fedora 12:
https://bugzilla.linux.ibm.com/show_bug.cgi?id=55864,

Regards--
Subrata

=Comment: #14=================================================
SUBRATA MODAK <Subrata Modak <subrata@xxxxxxxxxxxxxxxxxx>> - 
Any idea whether any fix is available for this ?

Regards--
Subrata

=Comment: #16=================================================
Edward E. Pollard <edpollar@xxxxxxxxxxxxx> - 
the fedora 12 bug ID at RH BZ is 
https://bugzilla.redhat.com/show_bug.cgi?id=522362

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review

[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]