SUCCESS!!!!!!!!!!!!!!!!

hugesmp.s root=/dev/sda4 rdinit= nohotplug
booted up to
darkstar login:

said something about having mail from Pavlov


so, what is hotplug, how do fix it and how do i get into GUI?

You tried my last suggestion ?
boot with: hugesmp.s root=/dev/sda4 rdinit= nohotplug

Your laptop is modern laptop, it should go well with acpi, I don't get it
At this point, I will attempt anything, I see it is delivered with windows vista, so why not let the bios beleive we want to boot windows vista instead of Linux?

Try boot with:
hugesmp.s root=/dev/sda4 acpi_os_name="Windows 2006" rdinit=

("Windows 2006" is the syntax for windows vista, see http://www.mail-archive.com/linux-ac.../msg10394.html)

[edit]
Ok, now try update /etc/lilo.conf with
append="nohotplug"

Congrat

Now follow standard slackware post install procedure:

first create a new user:
adduser
(follow the direction)

Then login into that user account and do:
xwmconfig
(choose your window manager)
then do:
startx

did you want me to boot it with the exact line?
"hugesmp.s root=/dev/sda4 acpi_os_name="Windows 2006" rdinit="
if so, it didn't work again failed at: hda_codec:...

now, when i am using:
hugesmp.s root=/dev/sda4 rdinit= nohotplug

process stops at one point, but i don't manage to read what is says, because some other text comes up
atkbd.c: unknown key was pressed
atkbd.c: unknown key was released
.
.
.
.
like ten times and then it waits for me to press [enter]. when i do, it boots fine to the darkstar login
is it some other error or just it stops due to our parameters entered?

where exactly do i do:
/etc/lilo.conf
append="nohotplug"
when it boots up and I login as root@darkstar?

ok so i used hugesmp.s root=/dev/sda4 rdinit= nohotplug, it stopped as i mentioned earlier and this time stayed for a little while, so i had a chance to read it. it said something about root partition being already mounted as read-write and that if i wanted for system to work correctly it should be mounted as read-only. and some instructions how to do that. but I guess- i'll worry about it later


what concerns
/etc/lilo.conf

as soon as i type that in, i get [access denied] message

Yes you have to use a text editor to edit this file, try:

jed /etc/lilo.conf

or:
nano /etc/lilo.conf

(use the one you're confortable with)
Then add the line: append="nohotplug"
in lilo.conf, under the line: root = /dev/sda4
save lilo.conf, then on the linux Console, type: lilo

Just to make sure, your lilo.conf slackware entry should look like:
#Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sda4
read-only
append = "nohotplug"
label = Linux

Also I forgot the ro option in the line:
hugesmp.s root=/dev/sda4 ro rdinit= nohotplug

(that's where the error about root partition mounted read write come from I guess)

try installing 12.1 using the huge.s kernel at the boot prompt at the begining of the installation.

i edited it, rebooted and now it's booting fine from my hd. i think from here i'll manage myself

i would like to thank you keefaz, and other guys who replied, so much for all your help. it's not called comunity-driven OS for nothing i see soon, i'll learn a little bit about linux and be back here helping others.
keefaz, if you're ever round london, give me a shout mantas1984@yahoo.com i'll buy you a drink

p.s. i know i'm being lazy here, but could you explain to me a little bit more in deph what is hotplug, apci and why mordern laptops should work with one but not the other and now that lilo has apend="nohotplug" is it disabling some device on my machine?

Linux drivers are called modules.
The job of hotplug is to detect your hardware and load the corresponding modules.
But sometimes it fails to detect the hardware or load a wrong module,
in this case the solution is to put the module on a blacklist, hotplug will not attempt to load the modules in the blacklist, the blacklist is: /etc/modprobe.d/blacklist

Now you have to find the module that possibly causes problem with hotplug, you could run:
/etc/rc.d/rc.udev start
and then: dmesg
see all error on output and from that find the wrong module
But I am not expert and I could be wrong on that, for now the only thing we know is that your system needs "nohotplug" kernel parameter to boot proprelly...


When you don't want to use hotplug, you can load the modules "by hand", eg modprobe <module name>
There is a script: /etc/rc.d/rc.modules*
You make it executable: chmod +x /etc/rc.d/rc.modules*
and you write the module you want to load in it, following the modprobe syntax (present in this file)

btw,

when i edited lilo, i got 3 warnings:
1.LBA32 addressing assumed
2.Unable to determine video adapter in use in the present system.
3.Video adapter does not support VESA BIOS extentions needed for display of 256 colors.Boot loader will fall back to the text only operation.

should i be worried about it? and is it the consequence of hotplug being disabled?

For hotplug, I tried to explain, see my edited post
1. LBA32 assumed, you have an extended partition made windows style, it is ok
2& 3: it is ok, unless you want display a nice background image in lilo boot, but it is only esthetic thing

You can add lba32 line in /etc/lilo.conf to avoid the lba32 warning,
add this line: lba32
(near the top of lilo.conf, like under "timeout ..." line)
Then run: lilo
to take the change in account

i'll worry about it later. thanx once again

Good show matt, that was the most tenacious show of install grit I've seen.
Glad to see it's working.
No small work work on the part of keefaz either ;-)