Re: Fedora 12: Cannot boot with kernel-2.6.32.9-67.fc12.x86_64

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

 



On Mon, 2010-03-08 at 03:30 -0600, Steven P. Ulrick wrote:
> Hello Everyone
> The good news is that in my 10+ years using Linux, I am almost certain that 
> I have never had a kernel that would not boot...
> 
> Last night I ran "yum update" and it pulled in 
> kernel-2.6.32.9-67.fc12.x86_64.  When I attempted to boot it, the boot 
> process seemed to complete, but X never started.
> 
> Since I have never had this problem before, I don't know precisely what 
> information that you need.
> 
> I am running an NVidia video card, with the proprietary NVidia driver, 
> installed from RPMFusion.  After failing to boot 
> kernel-2.6.32.9-67.fc12.x86_64, I can reboot and choose another kernel and 
> it boots just fine.
> 
> >From /var/log/messages, this is the closest that I can find to anything 
> relevant:
> Mar  8 03:01:56 localhost kernel: DRHD: handling fault status reg 102
> Mar  8 03:01:56 localhost kernel: DMAR:[DMA Read] Request device [03:00.0] 
> fault addr 233038000 
> Mar  8 03:01:56 localhost kernel: DMAR:[fault reason 01] Present bit in 
> root entry is clear
> Mar  8 03:01:56 localhost kernel: NVRM: Xid (0003:00): 54, CMDre 00000000 
> 00000000 00000000 00000001 00000001
> Mar  8 03:01:56 localhost kernel: DRHD: handling fault status reg 202
> Mar  8 03:01:56 localhost kernel: DMAR:[DMA Read] Request device [03:00.0] 
> fault addr 235833000 
> Mar  8 03:01:56 localhost kernel: DMAR:[fault reason 01] Present bit in 
> root entry is clear
> Mar  8 03:01:56 localhost kernel: NVRM: Xid (0003:00): 6, PE007e 
> Mar  8 03:01:56 localhost kernel: DRHD: handling fault status reg 302
> Mar  8 03:01:56 localhost kernel: NVRM: Xid (0003:00): 6, PE007e 
> 
> Again, I can boot fine from every other kernel.  I just can't boot from 
> 2.6.32.
> 
> If all I need to do is try running without the proprietary NVidia driver, 
> please let me know specifically how to disable that driver the easiest 
> possible way.  Translation: so that I can just boot back into an older 
> kernel and continue using the proprietary NVidia driver if I decide to do 
> that.
> 
> Also, not only have I never had a problem with being able to boot a 
> particular kernel, I have never had any problems with the proprietary 
> NVidia driver.
> 
> Let me know any additional information that you may need to help me with 
> this issue.
> 
> Steven P. Ulrick

I also had this issue, found a report that is you add

iommu=soft

to the kernel line in the menu.lst 

EXAMPLE:
title Fedora (2.6.32.9-67.fc12.x86_64)
	root (hd0,0)
	kernel /vmlinuz-2.6.32.9-67.fc12.x86_64 ro  root=UUID=a729b820-4928-4823-ba21-d4233410109c quiet vga=794 selinux=0 iommu=soft
	initrd /initramfs-2.6.32.9-67.fc12.x86_64.img


It worked for me.
-- 
Brian Millett - [ Garibaldi and Jack, "Revelations"]
"Look if I were you, I'd start talking straight because right now
    you're in a whole world of trouble."
'You don't even know what trouble is... but you're gonna find out...
    real soon.'
        

Attachment: signature.asc
Description: This is a digitally signed message part

-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux