colinux-users — coLinux users mailing list

Re: [coLinux-users] Problems on Vista Home Edition

[Paolo M. <pao...@gm...>]

>> 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

[coLinux-users] Pin hole camera toilet videos

[brigitte <bri...@OZ...>]

Your rod is set to get a lot of action http://www.burayebt.com/

Re: [coLinux-users] Unresponsive keyboard/mouse on Vista

[Paolo M. <pao...@gm...>]

On Tue, May 6, 2008 at 9:10 PM, Henry Nestler <Hen...@ar...> wrote:
> Hello Mark,
>
> Mark Rodriguez wrote:
>> I've tried getting coLinux running (tried latest release, stable, and
>> dev. snapshot) on my Vista laptop, but it consistently freezes all
>> input devices (keyboard and mouse don't work). Even after I'm unable
>> to move my mouse or type on my keyboard, I can see the console
>> messages (both on NT and FLTK) continue until it reaches the login. At
>> this point, I'm unable to type 'root' or navigate my mouse for any
>> other operation. It appears the machine is still alive since I'm able
>> to use my "non standard" function keys to do things like turn on the
>> keyboard light or access Lenovo's "ThinkVantage" menu options.
>>
>> Thinking this might be related to the console specifically, I even
>> tried running as a service, but it behaves the same way. Seems like
>> starting coLinux on Vista hijacks my input devices. The same
>> configuration works fine under XP. Any ideas, tips, suggestions?
>
> I feel, you have the same promblem as Andreas.
> Please try some of my debugging tips from help forum:
> http://sourceforge.net/forum/message.php?msg_id=4948804
>
> At other coLinux users with running Vista: Exist any difference between
> your Vista versions? Build number, Professional/Home, Service Packs or
> what ever?
>
> Please ansewer here in the list, not in the forum.
>
> --
> Henry N.
>

Hello,
on my PC with Vista there is a small problem about CTRL-C
I run colinux-0.7.2 (with you fix, Henry :=) ) and console-nt.
Then I run the following command :

> hexdump /dev/cobd1

where cobd1 is connected to my physical CDROM.
There are a lot of data.
If I want to stop, I press CTRL-C.
Under XP all is OK, the console-nt pass the CTRL-C to linux and
hexdump stops almost immediately.

Under Vista CTRL-C doesn't stops the hexdump command.
To be more clear, in Vista CTRL-C is not always bad.
For example, if I compile a program with this command :

> gcc myexample.c

and I press CTRL-C during compilation, CTRL-C works OK and stops the compiler.
It seems that it depends on the amount of data that pass throught the
console-nt or someting similar.

For Mark:
I dont't have your problem of freezing input device ....
It seems that on Vista everyone has a different problem :=(

Henry, your fix is OK .... no more hangs after IPI Shortcut mode :=)

Bye,
Paolo

[coLinux-users] Length and girth are very important

[Sasser <Far...@MA...>]

Bang her long and through the night easily with herbal remedies http://www.stalimne.com/

Re: [coLinux-users] Unresponsive keyboard/mouse on Vista

[Henry N. <Hen...@Ar...>]

Hello Mark,

Mark Rodriguez wrote:
> I've tried getting coLinux running (tried latest release, stable, and
> dev. snapshot) on my Vista laptop, but it consistently freezes all
> input devices (keyboard and mouse don't work). Even after I'm unable
> to move my mouse or type on my keyboard, I can see the console
> messages (both on NT and FLTK) continue until it reaches the login. At
> this point, I'm unable to type 'root' or navigate my mouse for any
> other operation. It appears the machine is still alive since I'm able
> to use my "non standard" function keys to do things like turn on the
> keyboard light or access Lenovo's "ThinkVantage" menu options.
> 
> Thinking this might be related to the console specifically, I even
> tried running as a service, but it behaves the same way. Seems like
> starting coLinux on Vista hijacks my input devices. The same
> configuration works fine under XP. Any ideas, tips, suggestions?

I feel, you have the same promblem as Andreas.
Please try some of my debugging tips from help forum:
http://sourceforge.net/forum/message.php?msg_id=4948804

At other coLinux users with running Vista: Exist any difference between
your Vista versions? Build number, Professional/Home, Service Packs or
what ever?

Please ansewer here in the list, not in the forum.

-- 
Henry N.

Re: [coLinux-users] nfs from colinux

[Henry N. <Hen...@Ar...>]

Antony Barton wrote:
> Simple question, is it possible to give coLinux direct and dedicated
> access to a network device, i presently have two devices, one which goes
> to my network and the other to a linux development board.
>  
> What would people recommend as a means of allowing this board to access
> an nfs share provided by coLinux and is this even possible?

Yes, with network type "pcap-bridge" you have full access to that interface.

This is not a "dedicated". This adds a second virtual adapater to that
card. Your development board will see two cards in this network. Ones
the coLinux and the other is the host (real) card.

Don't disable the complete device in windows! You can disable all
network services in the properties of this device. So, windows does not
use this interface. But, then you would have an other problem: Your host
self can not access to your development board.

-- 
Henry N.

[coLinux-users] No more lonely nights, herbal express

[brandie <nir...@2p...>]

I cannot believe my eyes when I woke up and saw my dick grew an inch http://www.iuffearn.com/

[coLinux-users] 2 for 1, limited period promo

[Pasqualino <697...@ST...>]

Britney is in the news again and I didn't make her pregnant http://www.alkehen.com/

[coLinux-users] 10 great tricks in bed

[Cobey <org...@CI...>]

Slam her from behind with your new pounder and hear her whimper in ecstasy. http://www.badegreai.com/

[coLinux-users] Big or small, it's your choice

[Kundinger <ker...@AS...>]

All your troubles will be solved today http://www.poweieanil.com/

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Luis L. <lui...@gm...>]

On Tue, Apr 29, 2008 at 5:36 AM, Henry Nestler <Hen...@ar...> wrote:
> Luis Lavena wrote:
>  >
>  > Now I'm getting something like this, since it appears the file system
>  > of the initrd is readonly and coLinux initrd is not able to create the
>  > lib directory. into defined root...
>  >
>  > Installing modules for coLinux 2.6.22.18-co-0.8.0-SVN1038
>
>  Oh, sorry. I putted some wrong. Kernel and modules are not from same
>  build. But, does no matter for your problem, the kernel file was ok.
>  File uploaded as "modules-2.6.22.18-co-0.8.0-SVN1038-20080428.tgz" now.
>

Thank you, downloaded and will check back later.

>
>  > Mounting cofs for vmlinux-modules.tar.gz
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: Cannot create directory `lib/': Read-only file system
>  > tar: lib/modules/2.6.22.18-co-0.8.0/kernel/arch/i386/crypto/aes-i586.ko: No such
>  >  file or directory
>  > Closing /
>
>  The messages above are from coLinux "initrd=intrd.gz", that is normal
>  for cramfs.
>
>
>  > VFS: Mounted root (cramfs filesystem) readonly.
>  > Trying to move old root to /initrd ... /initrd does not exist. Ignored.
>  > Unmounting old root
>  > Trying to free ramdisk memory ... okay
>  > Freeing unused kernel memory: 140k freed
>  >
>  > That was from the colinux console, this is from -v 3:
>  >
>  > RAMDISK: Compressed image found at block 0
>  > VFS: Mounted root (ext2 filesystem).
>  > ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on
>  >  cobd3
>  > VFS: Can't find ext3 filesystem on dev cobd3.
>  > VFS: Can't find an ext2 filesystem on dev cobd3.
>  > VFS: Mounted root (cramfs filesystem) readonly.
>
>  Don't use the initrd.gz from coLinux. This tries to intstall modules in
>  your cramfs. Cramfs is read only all times.
>  If you needs modules at some install point later, then install it
>  manualy with a mount over "cofs0".
>
>  You should use only the initrd from Distry for installing. I don't know
>  how you can stop from installing the distro kernel. For installing the
>  coLinux kernel you properly needs some hacks in the initrd, look arround
>  the coLinux-Knoppix boot...
>

Hmn, I got the impression that I needed to use initrd *from* coLinux
with any distro I want t install, but instead setting the root device
to the initrd supplied by my distro from this part of the wiki:

http://colinux.wikia.com/wiki/Full_CD-based%28iso%29_distro_install_and_config_steb-by-step_HOWTO_%28based_on_Xubuntu-7.10%29#THE_CLUE

I'll try again and see how it ends :-P

Thank you for your help.

-- 
Luis Lavena
AREA 17
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

[coLinux-users] Much ado about herbal express

[haseltine <rer...@AD...>]

She will love you more for what you can give her with this http://www.chaiteeae.com/

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Henry N. <Hen...@Ar...>]

Luis Lavena wrote:
> On Mon, Apr 28, 2008 at 7:28 PM, Henry Nestler <Hen...@ar...> wrote:
>> Luis Lavena wrote:
>>  > Thank you Jason for your answer, but the thing is that the kernel that
>>  > cames with coLinux is not possible to mount cromfs/cramfs, even on a
>>  > pre-installed distro like ubuntu using a loop device to extract the
>>  > initrd contents of the CD.
>>  >
>>  > If you look at my configuration file, you will see that I'm not trying
>>  > to boot from that, but just using as root, which seems not to work.
>>  >
>>  > In any case, I'll try a full boot with that distro and maybe convert
>>  > it to another format.
>>
>>  Try this, there crams is enabled:
>>  http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080428-cramfs/
>>
> 
> Thank you Henry, that actually made me get one step further...
> 
> Now I'm getting something like this, since it appears the file system
> of the initrd is readonly and coLinux initrd is not able to create the
> lib directory. into defined root...
> 
> Installing modules for coLinux 2.6.22.18-co-0.8.0-SVN1038

Oh, sorry. I putted some wrong. Kernel and modules are not from same
build. But, does no matter for your problem, the kernel file was ok.
File uploaded as "modules-2.6.22.18-co-0.8.0-SVN1038-20080428.tgz" now.

> Mounting cofs for vmlinux-modules.tar.gz
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: Cannot create directory `lib/': Read-only file system
> tar: lib/modules/2.6.22.18-co-0.8.0/kernel/arch/i386/crypto/aes-i586.ko: No such
>  file or directory
> Closing /

The messages above are from coLinux "initrd=intrd.gz", that is normal
for cramfs.

> VFS: Mounted root (cramfs filesystem) readonly.
> Trying to move old root to /initrd ... /initrd does not exist. Ignored.
> Unmounting old root
> Trying to free ramdisk memory ... okay
> Freeing unused kernel memory: 140k freed
> 
> That was from the colinux console, this is from -v 3:
> 
> RAMDISK: Compressed image found at block 0
> VFS: Mounted root (ext2 filesystem).
> ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on
>  cobd3
> VFS: Can't find ext3 filesystem on dev cobd3.
> VFS: Can't find an ext2 filesystem on dev cobd3.
> VFS: Mounted root (cramfs filesystem) readonly.

Don't use the initrd.gz from coLinux. This tries to intstall modules in
your cramfs. Cramfs is read only all times.
If you needs modules at some install point later, then install it
manualy with a mount over "cofs0".

You should use only the initrd from Distry for installing. I don't know
how you can stop from installing the distro kernel. For installing the
coLinux kernel you properly needs some hacks in the initrd, look arround
the coLinux-Knoppix boot...

-- 
Henry N.

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Luis L. <lui...@gm...>]

On Mon, Apr 28, 2008 at 7:28 PM, Henry Nestler <Hen...@ar...> wrote:
> Luis Lavena wrote:
>  > Thank you Jason for your answer, but the thing is that the kernel that
>  > cames with coLinux is not possible to mount cromfs/cramfs, even on a
>  > pre-installed distro like ubuntu using a loop device to extract the
>  > initrd contents of the CD.
>  >
>  > If you look at my configuration file, you will see that I'm not trying
>  > to boot from that, but just using as root, which seems not to work.
>  >
>  > In any case, I'll try a full boot with that distro and maybe convert
>  > it to another format.
>
>  Try this, there crams is enabled:
>  http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080428-cramfs/
>

Thank you Henry, that actually made me get one step further...

Now I'm getting something like this, since it appears the file system
of the initrd is readonly and coLinux initrd is not able to create the
lib directory. into defined root...

Installing modules for coLinux 2.6.22.18-co-0.8.0-SVN1038
Mounting cofs for vmlinux-modules.tar.gz
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: Cannot create directory `lib/': Read-only file system
tar: lib/modules/2.6.22.18-co-0.8.0/kernel/arch/i386/crypto/aes-i586.ko: No such
 file or directory
Closing /
VFS: Mounted root (cramfs filesystem) readonly.
Trying to move old root to /initrd ... /initrd does not exist. Ignored.
Unmounting old root
Trying to free ramdisk memory ... okay
Freeing unused kernel memory: 140k freed

That was from the colinux console, this is from -v 3:

RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on
 cobd3
VFS: Can't find ext3 filesystem on dev cobd3.
VFS: Can't find an ext2 filesystem on dev cobd3.
VFS: Mounted root (cramfs filesystem) readonly.


>  If that not work, then please detect the right type of filesystem of the
>  file "data\gobo\gobo-initrd", for example by booting a Knoppix and than
>  run "file gobo-initrd".
>
>  Should give such output:
>  initrd: Linux rev 1.0 ext2 filesystem data
>  ----------------------^^^^
>  But with other filesystem as "ext2" from my initrd.
>

Results from file:

/opt/gobo-initrd: Linux Compressed ROM File System data, little endian
size 761856 version #2 sorted_dirs CRC 0x14ec9052, edition 0, 441
blocks, 283 files

It seems is quite a challenge get GoboLinux (which doesn't follow FHS)
to work under coLinux... too bad :-(

Thank you for your time and helpful assistance.

-- 
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Henry N. <Hen...@Ar...>]

Luis Lavena wrote:
> Thank you Jason for your answer, but the thing is that the kernel that
> cames with coLinux is not possible to mount cromfs/cramfs, even on a
> pre-installed distro like ubuntu using a loop device to extract the
> initrd contents of the CD.
> 
> If you look at my configuration file, you will see that I'm not trying
> to boot from that, but just using as root, which seems not to work.
> 
> In any case, I'll try a full boot with that distro and maybe convert
> it to another format.

Try this, there crams is enabled:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20080428-cramfs/

If that not work, then please detect the right type of filesystem of the
file "data\gobo\gobo-initrd", for example by booting a Knoppix and than
run "file gobo-initrd".

Should give such output:
initrd: Linux rev 1.0 ext2 filesystem data
----------------------^^^^
But with other filesystem as "ext2" from my initrd.

-- 
Henry N.

[coLinux-users] Unresponsive keyboard/mouse on Vista

[Mark R. <ma...@gm...>]

I've tried getting coLinux running (tried latest release, stable, and
dev. snapshot) on my Vista laptop, but it consistently freezes all
input devices (keyboard and mouse don't work). Even after I'm unable
to move my mouse or type on my keyboard, I can see the console
messages (both on NT and FLTK) continue until it reaches the login. At
this point, I'm unable to type 'root' or navigate my mouse for any
other operation. It appears the machine is still alive since I'm able
to use my "non standard" function keys to do things like turn on the
keyboard light or access Lenovo's "ThinkVantage" menu options.

Thinking this might be related to the console specifically, I even
tried running as a service, but it behaves the same way. Seems like
starting coLinux on Vista hijacks my input devices. The same
configuration works fine under XP. Any ideas, tips, suggestions?

Thanks.

-- 
Mark F Rodriguez

[coLinux-users] Be the man of everyone's dreams

[Stearman <ate...@DC...>]

Make her reach climactic pleasure every night http://www.poeiaing.com/

[coLinux-users] Look forward to more action

[clayt <cla...@35...>]

Make sure you please your woman every night http://www.setnales.com/

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Luis L. <lui...@gm...>]

On Sun, Apr 27, 2008 at 4:29 AM, Jason Ahrens <ja...@co...> wrote:
> Luis Lavena said the following on 26/04/2008 11:20 PM:
>
> > But was impossible for me mount the initrd that came from the CD image:
>  >
>
>  coLinux uses a specially compiled kernel and modules. Standard distro's
>  don't use it. In general, it's still possible to use any distro you
>  want, but it's easiest to "inject" the kernel that comes with coLinux
>  into your distro.
>

Thank you Jason for your answer, but the thing is that the kernel that
cames with coLinux is not possible to mount cromfs/cramfs, even on a
pre-installed distro like ubuntu using a loop device to extract the
initrd contents of the CD.

If you look at my configuration file, you will see that I'm not trying
to boot from that, but just using as root, which seems not to work.

In any case, I'll try a full boot with that distro and maybe convert
it to another format.

Regards,
-- 
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

[coLinux-users] Be like brad, choose express herbals

[endacott <vu-...@BA...>]

Add a few revs to your daily lovemaking by viewing our product here http://www.Playbhes.com/

[coLinux-users] &#191; La inflaci&#243; n y los cursos de las divisas afectan sus econom&#237; as? Sabemos como luchar contra eso.

[colinyouell <col...@bi...>]

aqjdsmki

Re: [coLinux-users] installing distro that uses cramfs for initrd

[Jason A. <ja...@co...>]

Luis Lavena said the following on 26/04/2008 11:20 PM:
> But was impossible for me mount the initrd that came from the CD image:
>   

coLinux uses a specially compiled kernel and modules. Standard distro's 
don't use it. In general, it's still possible to use any distro you 
want, but it's easiest to "inject" the kernel that comes with coLinux 
into your distro.

Jason

[coLinux-users] installing distro that uses cramfs for initrd

[Luis L. <lui...@gm...>]

Hello List,

I found coLinux several days back and start playing with it, using
Ubuntu 7.04 that was available at the site.

For several reasons, i want to install GoboLinux, which is a different
kind of distro that don't follow standard FHS.

The thing is that following some of the instructions in the wiki page,
I cannot get the initrd to boot since is generated using cramfs.

http://colinux.wikia.com/wiki/Full_CD-based%28iso%29_distro_install_and_config_steb-by-step_HOWTO_%28based_on_Xubuntu-7.10%29

But was impossible for me mount the initrd that came from the CD image:

(-v 3):

Cooperative Linux Daemon, 0.7.3
Daemon compiled on Wed Apr 16 19:00:33 2008
...
Linux version 2.6.22.18-co-0.7.3 (hn@hn-lt) (gcc version 4.1.2) #1
PREEMPT Wed Apr 16 18:50:10 UTC 2008
...
VFS: Mounted root (ext2 filesystem).
ReiserFS: cobd3: warning: sh-2021: reiserfs_fill_super: can not find
reiserfs on cobd3
VFS: Can't find ext3 filesystem on dev cobd3.
VFS: Can't find an ext2 filesystem on dev cobd3.
Unable to identify CD-ROM format.
List of all partitions:
7503        744 cobd3 (driver?)
No filesystem could mount root, tried:  reiserfs ext3 ext2 iso9660
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(117,3)

and this is my configuration file:

kernel=vmlinux
mem=128
initrd=initrd.gz

cobd0=data\gobo\gobo_014_root.ext3.fs
cobd1=data\gobo\swap_256mb.fs
cobd2=D:\Downloads\Tools\GoboLinux\GoboLinux-014.01-i686.iso
cobd3=data\gobo\gobo-initrd
root=/dev/cobd3

eth0=slirp,02:00:00:00:00:01,tcp:8922:8922

Can anyone point me what I'm doing wrong?

Thank you in advance for your time.

-- 
Luis Lavena
Multimedia systems
-
Human beings, who are almost unique in having the ability to learn from
the experience of others, are also remarkable for their apparent
disinclination to do so.
Douglas Adams

[coLinux-users] Get a greater desire to have sex

[Alvina <Alv...@Eq...>]

Our genetically modified bacteria can mutate your toothpick into a tree trunk. http://www.dewilet.com/

[coLinux-users] Quick way to length, thicken and straighten

[Denell <aat...@80...>]

Thank goodness he had a big wang, if not I will be deprived for life. http://www.ubswift.com/