Internal card reader causes long POST
 

Hi there.

I built a PC for my Dad and it always had this annoying problem of taking about a minute for the system to report the amount of RAM and then move onto the drive detection.

Finally, I set aside some time to figure out what was up and discovered the problem goes away when the Akasa internal card reader is disconnected. I have tried connecting it to another header but it still does it.

The motherboard is a Gigbayte P55UD3 I think. Can I change anything in BIOS to stop the detection or should I buy another reader? Also, is it likely that is a faulty unit or should I replace with a totally different one?

Thanks a lot.

Re: Internal card reader causes long POST
 

Unlikely the unit is faulty, this is something I have seen again and again, usually if you pop a SD card or something in, it will run normally, but it may also try and boot from it ;)

Re: Internal card reader causes long POST
 

Thanks.

Not sure what to do now. Suppose I'll need to try another brand.

Re: Internal card reader causes long POST
 

It might be worth checking the boot order in the bios. If the system is set to look at the card reader as a boot device *before* the hard disk that could be adding to the delay.

Re: Internal card reader causes long POST
 

True enough, but the delay is usually caused by the BIOS looking for drives and finding one which according to logic (USB Mass Storage) should contain a filesystem or boot partition and tries to check for it and can't suss why there's apparently nothing there

Re: Internal card reader causes long POST
 

I guess it's similar to the long delays when a network boot is set as one of the first options and there's no network.

Re: Internal card reader causes long POST
 

If it is looking at the USB as a boot device, take that out of the list of boot devices completely.

Re: Internal card reader causes long POST
 

Cheers. Will look at his bios settings next time I'm there.

---------- Post added at 17:37 ---------- Previous post was at 17:34 ----------

I forgot to say, the delay is between CPU and ram detection. Surely the delay should be at the drive detection stage?