Hi,
I needed to access tty at the end of the boot, so instead of login to gdm, I hit Ctrl+Alt+F1 to get to tty1 : but just a full black screen welcomes me, same for tty2, 3, 4 then I hit one where is written:
* PCMCIA: probing PCI bus..
* not found.
* PCMCIA: probing for Intel PCIC (ISA)..
* not found.
* PCMCIA: probing for Databook TCIC-2 (ISA)..
* not found.
So I thought ok I wait a few seconds then I get to tty. But this probing lasts and lasts forever !
Hi Melodie,
Are you sure ? this is just a log about that probing ... but it's not the reason because you get a delayed login, which very probably is due to starting all enabled services ...
Hi AS,
I am sure, and I am also sure to be sure.

I have rebooted twice. Once I also tried to blacklist pcmcia but that didn't help so I removed it from the blacklist file and then I came here to ask for help. It looks like a log file, but it is a message in one of the ttys, though a ddebug.log is also created.
This is why in order to avoid posting before I find clues I did a research at the web. Then I found a message about the file "ddebug.log" which is created in /tmp after harddrake does the detection job, but that didn't help me either.
There is nothing to fix.
There must be something...

The next time, boot at runlevel 3 (grub, press F3 (options), hit enter and add a 3 at the end of the parameter line), this way you avoid to start the Xserver at all.
AS
I don't think so. I would rather invite you to test the next PCLinuxOS Education in English, (2012.04) which I will upload this night. This is the version with which I met with this annoyance (I have seen this message before and it bugs me, but I can't always post for every problem, so I had delayed this one).
Regards,
Mélodie
PS: About services I keep them always to the minimum as much as possible. I used to disable numlock to avoid being annoyed in some laptops where numlock means no access to the normal keyboard keys which are letters such as u, i, o, p, j, k, l, m and some punctuation. Now even disabled some process elsewhere turns it on again : is there any known way to change this behavior ?