Fedora This forum is for the discussion of the Fedora Project. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
05-21-2004, 10:45 AM
|
#1
|
LQ Newbie
Registered: Feb 2004
Posts: 13
Rep:
|
nforce2 ide issues.
My fedora literally takes 6-8 minutes to boot. below is the issue. i assumed it was nforce driver issues, but well in fedora 1 i attempted to use the drivers, and it still did this along with confusing the onboard nic drivers.
Code:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hda: Maxtor 2B020H1, ATA DISK drive
hdb: CD-W58E, ATAPI CD/DVD-ROM drive
Using cfq io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: IBM-DTTA-351010, ATA DISK drive
hdd: WDC WD273BA, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
SiI3112 Serial ATA: IDE controller at PCI slot 0000:01:0b.0
SiI3112 Serial ATA: chipset revision 1
SiI3112 Serial ATA: 100% native mode on irq 11
ide2: MMIO-DMA , BIOS settings: hde:pio, hdf:pio
ide3: MMIO-DMA , BIOS settings: hdg:pio, hdh:pio
hde: no response (status = 0xfe)
hdg: no response (status = 0xfe)
hde: no response (status = 0xfe), resetting drive
hde: no response (status = 0xfe)
hdg: no response (status = 0xfe), resetting drive
hdg: no response (status = 0xfe)
it hangs very long looking for hde, and hdg. the HDD itself is an older 10 gig ibm drive.
any help would be appreciated.
thanx.
|
|
|
05-21-2004, 01:37 PM
|
#2
|
LQ Newbie
Registered: May 2004
Posts: 3
Rep:
|
You too...
Sorry to say this but I am glad it is not just me. I thought I was going ot have to scrap my MB.
I am running an Nforce2 400 motherboard by XFX with a Seagate 80 gig SATA.
I get intermittent start ups with the same response. Sometimes I will need to reboot three to four times before it picks up right off the bat.
|
|
|
05-22-2004, 12:43 AM
|
#3
|
LQ Newbie
Registered: Nov 2003
Location: Mx!!!
Distribution: Fedora Core 2
Posts: 10
Rep:
|
I got the same than j0ntar, the problem should be the Serial ATA driver.
If you don't have any SATA disk disable the controller in the Bios, check out your motherboard manual to see where is that option.
After that your computer should boot normal (or fast).
Hope it helps
|
|
|
05-22-2004, 11:20 AM
|
#4
|
LQ Newbie
Registered: Feb 2004
Posts: 13
Original Poster
Rep:
|
thanx nano -=] ill give it a try this evening. ill let you know if it worked or not.
|
|
|
06-11-2004, 01:48 PM
|
#5
|
LQ Newbie
Registered: Jun 2004
Distribution: Fedora Core 2
Posts: 4
Rep:
|
it is timing out because those drives don't exist. put:
hdg=none hdk=none
at the end of your kernel line in grub.conf
this way it won't waste time looking for them.
|
|
|
06-11-2004, 01:51 PM
|
#6
|
LQ Newbie
Registered: Jun 2004
Distribution: Fedora Core 2
Posts: 4
Rep:
|
oops. I meant:
hde=none hdk=none
or whatever drives are resetting that don't exist.
|
|
|
06-11-2004, 02:56 PM
|
#7
|
LQ Newbie
Registered: Dec 2002
Location: Ann Arbor, MI, USA
Distribution: Red Hat Linux 8.0
Posts: 9
Rep:
|
I have the same problem. I think that adding ide2=noprobe ide3=noprobe will stop it from probing those IDE controller channels. I haven't tested it yet though.
I checked the BIOS but couldn't find any option to disable the SATA controller.
|
|
|
06-11-2004, 08:08 PM
|
#8
|
LQ Newbie
Registered: May 2004
Distribution: Fedora Core 4
Posts: 20
Rep:
|
mslagel is right, doing this cuts Linux loading time to under 2 mins, Its a shame that there is no mention of this in the install as im sure there are many many people who will think that it is a hardware issue and buy a non NF2 MoBo.
As to petthedingo's problem with the intermitent startups, Im afraid I have the same problem even when I disable the drive with linux on, its usualy every other boot that it hangs on the SATA detection (System boot and not Linux boot), If you listen closley you will hear the SATA drive spin up about 1 min later, I will be testing me SATA drive on another MoBo sometime soon and will be playing around with my MoBo and drives (Have to strip my comp anyways to clean).
Windows is to Linux as INTEL is to AMD.
Complete your rebirth and make the switch!.
|
|
|
06-11-2004, 08:12 PM
|
#9
|
LQ Newbie
Registered: May 2004
Distribution: Fedora Core 4
Posts: 20
Rep:
|
Opps, forgot to add this,
As to disabling SATA on your NF2 MoBo, you can't, as it is not part of the main BIOS, nor can you (I think) make your SATA drive bootable. wich is why I was lucky not to ditch my 2 40GIG IDE drives.
If you can then please let me know.
|
|
|
06-11-2004, 08:29 PM
|
#10
|
LQ Newbie
Registered: Jun 2004
Distribution: Fedora Core 2
Posts: 4
Rep:
|
SATA drives can work fine as the bootable drives. We do them with 2 and 4 drives in our supermicro chassis.
|
|
|
06-12-2004, 06:06 AM
|
#11
|
LQ Newbie
Registered: May 2004
Distribution: Fedora Core 4
Posts: 20
Rep:
|
mslagel, is that on a NF2 MoBo?.
|
|
|
06-12-2004, 11:38 AM
|
#12
|
LQ Newbie
Registered: Jun 2004
Distribution: Fedora Core 2
Posts: 4
Rep:
|
actually, no, that is not if that's what you were referring to.
|
|
|
06-12-2004, 08:25 PM
|
#13
|
Member
Registered: Apr 2002
Location: Wales MA.
Distribution: openSuSE 11.1
Posts: 409
Rep:
|
I have tried SuSE 9.1 and Fedora Core 2 on an ASUS A7N8X Deluxe nf2 board with SATA, it boots just fine from that drive. It is a slow waiting for it to look for hdg, but I don't reboot that often so it isn't an issue for me. This is the only hard drive in the machine it is an120 gig SATA Maxtor. Works fine.
|
|
|
06-13-2004, 01:06 PM
|
#14
|
Member
Registered: Jun 2004
Distribution: Ubuntu 7.10, Debian 4.0
Posts: 49
Rep:
|
Actually veggiemanuk, I have a NF2 400 on an Abit NF-S v2 and I effectively can disable the sata on it from the main bios.
I'm using slackware 9.1 and I was having the same problem at boot time, The sata driver, when loading was taking at least 1 minute to mention that the ports of the sata controler where not responding. To solve that, I simply disabled the sata controler in the bios.
But now, I am about to test to boot from my hard drive and see if it works or not.
|
|
|
All times are GMT -5. The time now is 03:41 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|