Hello everybody, yes Sam, you are right, but this bios is a little bit different, there is only a setting regarding SATA: SATA0 legacy. with this option enabled, the kernel detects the hard drive, but is not able to initialize it in order to be partitioned . So i disabled this option and it is working properly (this happens for both kernels and i think that legacy code is no longer supported by the kernels, which is not an issue).
I tried an official image i386 installation image on different media and has the same problem. I tried the amd64 kernel and it works flawlessly, and detects more cpu flags than i386 kernel(including NX flag); thanks Stuart for this suggestion. The system is up and running, showing both cores on top command. Very nice. I put both dmesg on these addresses: http://swordfish.rotld.ro:8283/dmesgs/amd64_44_dmesg http://swordfish.rotld.ro:8283/dmesgs/i386_44_dmesg There are two issues regarding both kernels: 1. command 'halt' does halts the system but the keyboard, which is on usb, does not responds anymore, so the system cannot be restarted. but this is not a problem, as 'reboot', 'shutdown -r now' reboots the system properly, and 'halt -p' halts the system and shuts down the power, which is what i want; 2. the lan controller on board i think is faulty causing both kernels to panic. this si not a problem because i disabled it from bios, as i want to buy a real network card. the diagnose message is (i wrote it down on a piece of paper): panic: config_detach: force detach of re0 failed (45). i am not able to do any 'trace' an 'ps' commands, here, in this situation, because the keyboard freezes. please let me know if the above dmesg messages are accessible through that address and port configuration as it might be filtered. this is my machine at work and it is not supposed to be visible from outside, but hey we a trying to solve an issue here, so if we can make it visible, why not do so? just let me know if you can access it. Thank you very much for your support and suggestions bogdan
