i fixed it! i fixed it! yaayyy!
what' with reading all those dmesg and /var/log/messages. those make me feel sleepy....such long lines
anyways...for the benefit of the community...
1. all the "Setting up <servicename or stuff like that> [OK(or FAILED)] lines get piled up in a file called boot.log inside /var/log . i think this was one of my questions. dmesg has no information of this sort. now you might be thinkin "you know all then why ask?" i didn't know about such a file...except i used my windows knowledge of the presence of BOOTLOG.TXT .
2. now if setting up modules has failed it's easier to check files that deal with modules auto-loading viz. /etc/modules.conf (which as per my friend is the debian norm and also exists on my system...for compatilbilty reasons??) and /etc/rc.d/rc.modules (i forgot this filename and i was checkin al thru rc.d huge directory
2a. i don't really understand what are the alias lines doing in /etc/modules.conf they are for my broadcom drivers..ndiswrapper n stuff...ok let's not get carried away...
3. so finally got the culprit entries in rc.modules....which were present thanks to my semi-failed attempt to install true-crypt . if you see it being used o windows...you'd wish every one should have one...but linux....mount volumes use disk-level encryption ... use urandom...dm-crypt (this has like 2-3 similar sounding projects with different pages almost like linkin to each other when u click the 'download' link (not a bad idea for server load balancin...whaddya say?
) ....just hide my darn files!!! (no not the '.')
so one problem's solved...now to get the boot splash screen showin the text clearly...each new line overlaps over the previous line and all i see then is...whitewash