Red Hat Bugzilla – Bug 209589
modprobe mga causes kernel panic
Last modified: 2012-06-20 12:09:29 EDT
Description of problem:
modprobe mga results in kernel panic.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot to runlevel 3
2. modprobe mga
kernel panic, ctrl-alt-del not working, requires power cycle.
mga module should load.
The PC is a HP xw4300 Workstation with 64-bit Pentium 4.
Graphics card is a Matrox G450 Quad-head pci card.
Results are the same using RHEL 4.4 i386 and RHEL 4.3 x86_64.
Installation with graphics mode works as expected, i'm guessing anaconda
runs in vesa mode?
After installation, on the next boot the rhgb is started but all i see is a black
screen and then the PC is locked up.
I am guessing the starting of X automatically loads the mga driver which in
turn causes a kernel panic but i am unable to switch to any vt or log in via
Booting to runlevel 3 and running startx manually creates the same black screen
and i am unable to switch to any vt or log in via ssh.
Booting to runlevel 3 and running modprobe mga causes kernel panic.
Works as expected on same hardware with Fedora Core 5 i386.
Works as expected using kernel.org version 2.6.18 compiled on RHEL 4.4 x86_64
still causes panic
(In reply to comment #1)
> still causes panic
(In reply to comment #2)
> (In reply to comment #1)
> > still causes panic
> still panicing
Resolved by changing card to an nvidia quadro nvs 285 and using the nvidia
Leaving bug as new until there is a reply from someone other than myself.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life.
Please See https://access.redhat.com/support/policy/updates/errata/
If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.