From: Paolo M. <pao...@gm...> - 2008-03-25 07:36:19
|
Hi, At home I have Vista Home Edition. I have some problems with colinux. Both 0.7.2 and 0.8.0 doesn't exit to console after "poweroff" and "halt" command. This happens only rarely, but almost everytime my colinux stops on "System halted" message, then I have to close manually the console. An other small problem is this. I have installed the driver (linux.sys). Then I use colinux and all is ok (I have only the problem of exit that I have explained before). When I restart the system and I launch the BAT that starts colinux, appears a message that tell to check the driver status. The driver is installed ! If I remove the driver and reinstall it, all works. But If I restarted the system there is the same problem. The daemon tell to check the driver status ..... I don't know if these problems depends on my system. Under XP I don't have these problems. Any ideas ? Regards Paolo |
From: Henry N. <Henry.Ne@Arcor.de> - 2008-03-25 22:12:44
|
Paolo Minazzi wrote: > At home I have Vista Home Edition. > I have some problems with colinux. > Both 0.7.2 and 0.8.0 doesn't exit to console after "poweroff" and > "halt" command. This happens only rarely, but almost everytime my > colinux stops on "System halted" message, then I have to close > manually the console. Have you set the environment in batch? set COLINUX_CONSOLE_EXIT_ON_DETACH=1 Is the FLTK-console Attached or Detached? Have you the last lines from the output of colinux-daemon.exe? (after the power off), for example EXT3 FS on cobd0, internal journal System halted. colinux: Linux VM terminated colinux: halted, exiting. Have you tryed the menu in fltk console: Monitor - Shudown? The same as you run the command: "shutdown -h now" > An other small problem is this. > I have installed the driver (linux.sys). > Then I use colinux and all is ok (I have only the problem of exit that > I have explained before). > When I restart the system and I launch the BAT that starts colinux, > appears a message that tell to check the driver status. > The driver is installed ! If I remove the driver and reinstall it, all works. > But If I restarted the system there is the same problem. The daemon > tell to check the driver status ..... Hm. First check the driver status with Windows tools. Open your hardware manager, enable "see all hidden devices" and say is the coLinux driver in running mode? If not, try to start it. Stays the "Start type" on "automatic"? Any errors in the driver properties? (German howto find coLinux driver in Windows Device Manager: http://www.henrynestler.com/colinux/screenshoots/HardwareDeviceManager.png, http://www.henrynestler.com/colinux/screenshoots/driver-details-grayed.png) What is the output of "colinux-daemon --status-driver" in the line "current state:..." if the driver is not usable? Sorry, have no Vista running. -- Henry N. |
From: Paolo M. <pao...@gm...> - 2008-03-26 07:38:03
|
Paolo Minazzi wrote: > At home I have Vista Home Edition. > I have some problems with colinux. > Both 0.7.2 and 0.8.0 doesn't exit to console after "poweroff" and > "halt" command. This happens only rarely, but almost everytime my > colinux stops on "System halted" message, then I have to close > manually the console. Have you set the environment in batch? set COLINUX_CONSOLE_EXIT_ON_DETACH=1 No ! In XP I don't have this variable setted but it works. I will try! I can try only at home. At work I have only XP, at home I have Vista. Is the FLTK-console Attached or Detached? I use only CONSOLE-NT. I don't use FLTK ! I think (I'm sure 90% :=) ) that it is deteach. I would like to verify it, but I'm almost sure. Have you the last lines from the output of colinux-daemon.exe? (after the power off), for example EXT3 FS on cobd0, internal journal System halted. colinux: Linux VM terminated colinux: halted, exiting. darkstar login: root Linux 2.6.22.18-co-0.8.0. Last login: Sun Mar 23 16:13:14 +0100 2008 on tty1. You have mail. root@darkstar:~# poweroff Broadcast message from root (tty1) (Sun Mar 23 16:14:28 2008): INIT: Switching to runlevel: 0 INIT: Sending processes the TERM signal root@darkstar:~# The system is going down for system halt NOW! INIT: Sending processes the KILL signal Running shutdown script /etc/rc.d/rc.0: Saving system time to the hardware clock (localtime). hwclock is unable to get I/O port access: the iopl(3) call failed. smbd: no process killed nmbd: no process killed Unmounting remote filesystems. Saving random seed from /dev/urandom in /etc/random-seed. Turning off swap. Unmounting local file systems. Remounting root filesystem read-only. System halted. Have you tryed the menu in fltk console: Monitor - Shudown? The same as you run the command: "shutdown -h now" I have tried poweroff and halt commands. I don't use FLTK. > An other small problem is this. > I have installed the driver (linux.sys). > Then I use colinux and all is ok (I have only the problem of exit that > I have explained before). > When I restart the system and I launch the BAT that starts colinux, > appears a message that tell to check the driver status. > The driver is installed ! If I remove the driver and reinstall it, all works. > But If I restarted the system there is the same problem. The daemon > tell to check the driver status ..... Hm. First check the driver status with Windows tools. Open your hardware manager, enable "see all hidden devices" and say is the coLinux driver in running mode? If not, try to start it. Stays the "Start type" on "automatic"? Any errors in the driver properties? (German howto find coLinux driver in Windows Device Manager: http://www.henrynestler.com/colinux/screenshoots/HardwareDeviceManager.png, http://www.henrynestler.com/colinux/screenshoots/driver-details-grayed.png) What is the output of "colinux-daemon --status-driver" in the line "current state:..." if the driver is not usable? This is he output C:\coLinux-0.8.0>colinux-daemon.exe -t nt @norm Cooperative Linux Daemon, 0.8.0 Daemon compiled on Fri Mar 21 18:14:03 2008 colinux: manager open: Impossibile trovare il file specificato. (in englishlanguage, "Impossible to find the specified file"); daemon: exit code 82c7400e daemon: can't access CoLinuxDriver, please check status driver! =========================================== norm =========================================== kernel=vmlinux mem=128 cobd0=c:\users\paolo\colinux-7.1\_base.img cobd1=\Device\CdRom0 cobd2=\Device\Harddisk0\Partition4 ro root=/dev/cobd0 cofs0=c:\ Sorry, have no Vista running. I'm sorry I had not attached exact logs in my previous email. In the next emails I will try to be more precise. ;=) Thanks, Paolo Minazzi |
From: Paolo M. <pao...@gm...> - 2008-05-08 09:19:09
|
>> An other small problem is this. >> I have installed the driver (linux.sys). >> Then I use colinux and all is ok (I have only the problem of exit that >> I have explained before). >> When I restart the system and I launch the BAT that starts colinux, >> appears a message that tell to check the driver status. >> The driver is installed ! If I remove the driver and reinstall it, all works. >> But If I restarted the system there is the same problem. The daemon >> tell to check the driver status ..... > > Hm. First check the driver status with Windows tools. Open your hardware > manager, enable "see all hidden devices" and say is the coLinux driver > in running mode? If not, try to start it. Stays the "Start type" on > "automatic"? Any errors in the driver properties? > (German howto find coLinux driver in Windows Device Manager: > http://www.henrynestler.com/colinux/screenshoots/HardwareDeviceManager.png, > http://www.henrynestler.com/colinux/screenshoots/driver-details-grayed.png) A brief news about my old topic. I realize in these days that under Vista the driver is not active after a boot. I I boot Vista and quicly I open a cmd.exe and run colinux, I have the problem that the driver is not active. If I wait some seconds, about 30 seconds, the driver become active and all is OK. I correct what I say in my original message ... I don't have to uninstall and remove the driver ... I only have to wait a moment and then run colinux. Bye, Paolo |