Michael Brechlin wrote:
> This is my first time writing to the list so I hope I am providing
> enough information.
Thanks for your full comment here. Very good. ;-)
> I have installed colinux 6.4 and 7.1. they are installed in separate
> directories. (c:\colinux and c:\colinux71)
> I am running Windows XP SP2 (MCE) with all current security updates.
> My boot.ini contains an entry for /NoExecute=AlwaysOff /NOPAE.
> My System specs are: AMD Athlon 64 mobile 4000+ (1.6ghz), 1GB RAM.
Think, "/NoExecute=AlwaysOff /NOPAE" is not need for AMD. In such error
cases your machine would be crash with a reboot directly befror see any
kernel messages. But, thanks for your full comment here. ;-)
> In my config file i have only one drive set, initrd default, vmlinux
> default, memory=256, network=TAP or disabled, no swap.
> I try --driver-remove and --driver-install before I try to run colinux,
> and status-driver says the driver is running with the correct version
Yes, linux driver is running.
These messages comes from linux kernel:
> Linux version 2.6.12-co-0.7.1 (george@...) (gcc version 3.4.4
> (prerelease) (Debian 3.4.3-13sarge1)) #256MB LOWMEM available.
> initrd enabled: start: 0xcff9a000 size: 0x00065ef7)
> On node 0 totalpages: 65536
> DMA zone: 0 pages, LIFO batch:1
> Normal zone: 65536 pages, LIFO batch:31
> HighMem zone: 0 pages, LIFO batch:1
> Built 1 zonelists
> Kernel command line: root=/dev/cobd0
> Initializing CPU#0
> Setting proxy interrupt vectors
> PID hash table entries: 2048 (order: 11, 32768 bytes)
> Using cooperative for high-res timesource
> Console: colour CoCON 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
colinux-net-daemon: auto selecting TAP
Memory: 255360k/262144k available (1535k kernel code, 0k reserved, 531k
data, 112k init, 0k highmem)
... should the next lines from kernel boots. I'm afraid something
problem with memory detection, or with cache settings.
Try follow steps:
* Is live CDROM runing on this machine? Try a Knoppix and compair the
missing boot messages near "cache hash table".
* Use the smalest config, you have.
For sample this command line with initrd only:
colinux-daemon.exe mem=32 kernel=vmlinux initrd=initrd.gz root=/dev/ram0
* Open a second command prompt and run the debugger:
colinux-debug-daemon.exe -d -p -s prints=31,misc=31 -f debug.xml
Than starting the colinux-daemon.
After your colinux-daemon is stopping, stop the debugger with CTRL-C,
and grep in the file debug.xml for the text "Console: colour CoCON
80x25". Is there any more information about your problem?
* Debug the memory (many more outputs). Run the debugger with output
colinux-debug-daemon.exe -d -p -s prints=31,misc=31,allocations=15 -f
Run colinux-daemon, stop the debugger and check the output.
* Incrase the memory from 32 up to 250, but not values with power of 2
(not the 256, not 128 ,...), and check with the "initrd only".
* Try the 20061210-Snapshot. That was build with differ compiler:
* Check the task manager: Is colinux-daemon.exe doing anything? Is it
idle or polling for any?
> The TAP adapter gives itself a 169.x IP address and claims to be
> connected, but refuses any ssh attempts.
The network is not setted up. The init process was not running, you
staning on the memory detection.
> # Slirp for internet connection (outgoing)
> # Inside running coLinux configure eth0 with this static settings:
> # ipaddress 10.0.2.15 <http://10.0.2.15> broadcast 10.0.2.255
> <http://10.0.2.255> netmask 255.255.255.0 <http://255.255.255.0>
> # gateway 10.0.2.2 <http://10.0.2.2> nameserver 10.0.2.3
> # Networking (tuntap as private network between gust and host)
If you don't use SLiRP, than set the first network (index 0) to TAP
You can see typical full boot with mem=256 eth0=slirp eth1=tap here: