Fedora Linux Support Community & Resources Center

Go Back   FedoraForum.org > The Dungeon > Archived (Click Header To See Sub-Forums) > F26 Development Forum
FedoraForum Search

Forgot Password? Join Us!

F26 Development Forum F26 Development Forum Pretty much exactly what it sounds like it is. This is the place to discuss and assist in the community development of F26. WARNING: Any pre-release versions, Beta included, are for experienced testers only. Back up all existing data and read all threads in the version Development Forum before attempting an install. Errors can and will likely occur which may include data destruction or inability to boot other partitions on any and possibly all attached hard drives. While FedoraProject needs and appreciates testers, you must remember to report issues directly to Bugzilla, after checking for pre-existing bugs.

 
 
Thread Tools Search this Thread Display Modes
  #1  
Old 9th May 2017, 09:39 PM
Kobuck Offline
Registered User
 
Join Date: Feb 2009
Location: Florida
Posts: 509
linuxfedorafirefox
[SOLVED] BIOS setting for IOMMU affects F26 boot

Just sharing.

Since "rc8" was issued I have been unable to successfully boot F26. I could boot the rescue image, but not the release candidate. I was really struggling to determine where the boot was hanging.

My System:
Quote:
GA-990FXA-UD7/GA-990FXA-UD7, BIOS F10 10/26/2012
AMD Phenom(tm) II X6 1100T Processor
Linux 4.11.0-0.rc8.git0.1.fc26.x86_64
While working on another issue, by pure chance I found that "disabling" the IOMMU in the BIOS settings of my GigaByte MB allowed a successful boot of F26 "rc8".

Still no clue as to what the issue is, just found this works for me.
__________________
Laptop: ASUS K61IC/ Intel T6600 2.20Ghz x2/ 4GB/ 320GB SataII/ NVidia G96M/ fc26.x86_64
Tower: GigaByte (990FXA)/ AMD 1100T 3.3Ghz x6/ 16GB/ 7.5TB Sata III/ AMD 6770HD/ fc26.x86_64
Bookshelf: Shuttle DS61 (H61)/ i3-3225 3.3Ghz x2/ 16GB/ 320GB Sata II/ Intel HD 4000/ fc25.x86_64
Embedded: BeagleBone Blk / ARM AM3358 1 GHz x1/ 512MB/ 2GB eMMC/ PowerVR SGX530/ fc25.armv7hl
  #2  
Old 9th May 2017, 09:51 PM
antikythera Offline
Administrator
 
Join Date: Dec 2013
Location: United Kingdom
Posts: 4,748
windows_98_nt_2000chrome
Re: BIOS setting for IOMMU affects F26 boot

Have you tried blacklisting the timer watchdog module by adding this value before rhgb quiet to /etc/default/grub.cfg and re-building grub?

Code:
modprobe.blacklist=sp5100_tco
you can add it manually to test if it works for you as well by pressing e to edit the grub entry from the menu. please try that with IOMMU enabled and see if it makes any difference.
__________________
Download, Install and Share Fedora - Official ISO Torrents | Live ISO Respins containing post-release updates
  #3  
Old 9th May 2017, 10:53 PM
Kobuck Offline
Registered User
 
Join Date: Feb 2009
Location: Florida
Posts: 509
linuxfedorafirefox
Re: BIOS setting for IOMMU affects F26 boot

Quote:
Originally Posted by antikythera View Post
.... please try that with IOMMU enabled and see if it makes any difference.
No joy !!! Still a black screen.

However, there are some additional factors.

Following is under F25:
1) The other project I was working on was adding 2 sata ports with a PCIe card using the "Marvell 88SE9128" chipset.

2) My GigaByte MB includes 2 "Marvell 88SE9172" soldered on chips to deliver esata to front and back panels.

3) Although things worked fine with the original 88SE9172 MB chips, adding the 88SE9128 via PCIe generated errors during boot. The boot was successful, but the new disks were not accessible.

4) Disabling IOMMU in the BIOS eliminates the boot errors and the disks are accessible. ( probably doesn't deal with root problem )

5) Since I really don't need to directly access devices from Virtual machines, I can accept this "solution"

Under F26 "rc8":

1) Was getting a black screen hang with F26 "rc8" boot prior to the new PCIe card installation

2) Discovered booting F26 "rc8" with IOMMU disabled is successful

3) I reenabled IOMMU and edited "modprobe.blacklist=sp5100_tco" into kernel command line

3) I now get the same(as F25) boot errors from the Marvell chip issues.

4) I get the same???(how can you tell) F26 black screen halt as before

4) Whether the halt the same or not, I do not get a successful F26 "rc8" boot

Thanks for the suggestion, but for now I can live without IOMMU. I'm willing to try other suggestions to actually isolate the issue. I would hate to see this continue into the final F26 release. Right now I'm just not sure how I would define the issue to BugZilla.
__________________
Laptop: ASUS K61IC/ Intel T6600 2.20Ghz x2/ 4GB/ 320GB SataII/ NVidia G96M/ fc26.x86_64
Tower: GigaByte (990FXA)/ AMD 1100T 3.3Ghz x6/ 16GB/ 7.5TB Sata III/ AMD 6770HD/ fc26.x86_64
Bookshelf: Shuttle DS61 (H61)/ i3-3225 3.3Ghz x2/ 16GB/ 320GB Sata II/ Intel HD 4000/ fc25.x86_64
Embedded: BeagleBone Blk / ARM AM3358 1 GHz x1/ 512MB/ 2GB eMMC/ PowerVR SGX530/ fc25.armv7hl
  #4  
Old 10th May 2017, 07:58 AM
antikythera Offline
Administrator
 
Join Date: Dec 2013
Location: United Kingdom
Posts: 4,748
linuxchrome
Re: BIOS setting for IOMMU affects F26 boot

regarding bugzilla you could word the report exactly as per your reply to my suggestion above.

i vaguely recall a thread about marvell SATA controllers on this forum before. so it may be worth searching to see if there is an existing bugzilla report for the chip in the PCI-E card before creating a new one
__________________
Download, Install and Share Fedora - Official ISO Torrents | Live ISO Respins containing post-release updates
  #5  
Old 10th May 2017, 11:44 AM
krdondon Offline
Registered User
 
Join Date: Mar 2016
Location: seoul
Posts: 9
linuxfedorafirefox
Re: BIOS setting for IOMMU affects F26 boot

My recent experience ..
{
Fedora Linux on the mainboard with BIOS information ..
Continue to register more.

continuity..
It does not erase.
I installed a new linux ..
Even a swap partition ..

It does not erase. PE os mounted swap partition
So there is an error. / Dev / sda (partition error)
Table format

The computer is trying to force restore ..
Characteristic..

Using virtual RAM is a bug.
so I..

Dd if = / dev / zero of = / dev / sda bs = 512 count = 1245
reboot..

I have initialized the hard disk

After that, Bios is ..
It is cleanly organized.

conclusion..
If the error does not clean the hard disk ..
Registered as a virtual ...

Repeat. conclusion..}



If you have a bug in the past ...
It does not exist.

But it remains in virtual memory.
Repeated errors may occur.
scenario. (My reasoning)
Things that were real to me .. Truth.(swap ram bios

Uninitialized ... remains somewhere.
Tmp ..
So it is ..
Os itself features fast boot .. system ..
Efi .. (my guess ..)


Note:
If I get a bug ...
Clonezilla
Use the program to recover. ^^
/ Dev / sda (I can recover mbr / gpt even if I delete the partition.)

Last edited by krdondon; 10th May 2017 at 11:55 AM.
  #6  
Old 10th May 2017, 01:53 PM
antikythera Offline
Administrator
 
Join Date: Dec 2013
Location: United Kingdom
Posts: 4,748
linuxchrome
Re: BIOS setting for IOMMU affects F26 boot

what? that makes next to no sense and doesn't relate to this hardware compatibility problem
__________________
Download, Install and Share Fedora - Official ISO Torrents | Live ISO Respins containing post-release updates
  #7  
Old 10th May 2017, 03:21 PM
Kobuck Offline
Registered User
 
Join Date: Feb 2009
Location: Florida
Posts: 509
linuxfedorafirefox
Re: BIOS setting for IOMMU affects F26 boot

I believe the Marvell chips are only related to issue in that they caused me to disable IOMMU. I then discovered F26 "rc8" would successfully boot.

Previous to this ( before I installed the new PCIe card ), I was attempting to get more information on the boot hangup.

I edited the kernel command line as follows:
remove: rhgb quiet
add: rd.shell rd.debug log_buff_len=1M

Good news / Bad news
Booting with these settings resulted in a successful boot. Therefore I got no information leading to the problem.

After a successful boot everything works just fine.
This all makes me think this is a timing issue related to startup of various system services. I'm guessing there is a systemd script that needs tuning ( before, after, requires settings ) Tough to debug though.

I'm going to try this again with the Marvell card installed. (really don't want to be pulling new card to test )

Result

OK, I have booted successfully with IOMMU enabled and kernel command edits as above. Got errors on the Marvell chip as expected and no access to attached drives.
I have captured listings of the journalctl errors and as well as a full journalctl to study at liesure.
I am returning to F25 and no IOMMU until I can think of (or get suggestions) of other things to try.
BTW this was posted from the F26 "rc8" system.
__________________
Laptop: ASUS K61IC/ Intel T6600 2.20Ghz x2/ 4GB/ 320GB SataII/ NVidia G96M/ fc26.x86_64
Tower: GigaByte (990FXA)/ AMD 1100T 3.3Ghz x6/ 16GB/ 7.5TB Sata III/ AMD 6770HD/ fc26.x86_64
Bookshelf: Shuttle DS61 (H61)/ i3-3225 3.3Ghz x2/ 16GB/ 320GB Sata II/ Intel HD 4000/ fc25.x86_64
Embedded: BeagleBone Blk / ARM AM3358 1 GHz x1/ 512MB/ 2GB eMMC/ PowerVR SGX530/ fc25.armv7hl

Last edited by Kobuck; 10th May 2017 at 04:14 PM. Reason: update results
  #8  
Old 13th May 2017, 10:22 PM
Kobuck Offline
Registered User
 
Join Date: Feb 2009
Location: Florida
Posts: 509
linuxfedorafirefox
Re: BIOS setting for IOMMU affects F26 boot

The latest F26 Alpha kernel package release "Linux 4.11.0-2.fc26.x86_64" will boot successfully with AMD IOMMU enabled.

I kind of lost a pure before and after comparison on this because of my introduction of the PCIe card with Marvell chip errors, but F26 Alpha was not booting with IOMMU enabled before the introduction of the new PCIe card.

After the recent update of the kernel I can activate my IOMMU again and F26 Alpha will boot successfully
( I also note they have dropped the release candidate designation )

I then replaced the PCIe card using the Marvell 88SE9128 with a card that uses a Marvell 88SE9235. This eliminated the AMD-Vi errors in both F25 and F26 Alpha with IOMMU enabled.

I can now boot and access my disks in both F25 and F26 Alpha.


PS: The thread tools doesn't show me a solved option. Did the process for marking solved change??
__________________
Laptop: ASUS K61IC/ Intel T6600 2.20Ghz x2/ 4GB/ 320GB SataII/ NVidia G96M/ fc26.x86_64
Tower: GigaByte (990FXA)/ AMD 1100T 3.3Ghz x6/ 16GB/ 7.5TB Sata III/ AMD 6770HD/ fc26.x86_64
Bookshelf: Shuttle DS61 (H61)/ i3-3225 3.3Ghz x2/ 16GB/ 320GB Sata II/ Intel HD 4000/ fc25.x86_64
Embedded: BeagleBone Blk / ARM AM3358 1 GHz x1/ 512MB/ 2GB eMMC/ PowerVR SGX530/ fc25.armv7hl

Last edited by Kobuck; 13th May 2017 at 10:40 PM.
  #9  
Old 14th May 2017, 09:03 AM
antikythera Offline
Administrator
 
Join Date: Dec 2013
Location: United Kingdom
Posts: 4,748
linuxchrome
Re: BIOS setting for IOMMU affects F26 boot

there is no solved function in the development section. I'll edit the thread title and add it for you
__________________
Download, Install and Share Fedora - Official ISO Torrents | Live ISO Respins containing post-release updates
 

Tags
affects, bios, boot, f26, iommu, setting

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Can't boot Fedora 24/25 with kernel 4.8.* without iommu=soft JuhaniJaakola Installation, Upgrades and Live Media 4 16th January 2017 07:50 PM
Fedora won't boot with IOMMU enabled g00ey Hardware & Laptops 13 30th August 2011 02:53 PM
Install issue due to BIOS setting seabird Installation, Upgrades and Live Media 6 1st February 2009 01:17 AM
Fedora and GX270 solved (sound and graphics - new bios needed) ghenry Installation, Upgrades and Live Media 4 1st September 2004 01:13 AM


Current GMT-time: 15:06 (Wednesday, 16-08-2017)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat