colinux-users

RE: [coLinux-users] crossing the bridge

[peter g. <plu...@bi...>]

checksum offload on some network cards has been known to cause problems with
communication from host-guest

if all else fails you can always buy a cheap realtek ;)

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of Curtis,
> Craig
> Sent: 12 October 2004 12:33
> To: col...@li...
> Subject: [coLinux-users] crossing the bridge
>
>
> It seems that only pinging is supported as a network protocol between
> the Windows side and Colinux on a bridged network.  I can ping just
> fine, but FTP, smb, and other protocols do not work on the same PC, but
> from another PC they do work.
>
> Is there a configuration on the PC-TAP network driver or in Win2K that I
> can change somewhere to allow this to work?
>
> Thanks,
> Craig
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

RE: [coLinux-users] crossing the bridge

[peter g. <plu...@bi...>]

btw colinux supports multiple network adaptors nowadays

so you can use tap for host-colinux and winpcap for network-colinux

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of Curtis,
> Craig
> Sent: 12 October 2004 20:16
> To: col...@li...
> Cc: peter green
> Subject: Re: [coLinux-users] crossing the bridge
>
>
> Yes.  This seems to be my problem.  I have an Intel Pro/1000 and I do
> not see a way to get to ChecksumRxTcp.  I found the other parameters in
> my registry, but ChecksumRxTcp does not appear to exist.  Could the
> networking docs have a typo?
>
> Otherwise, I may need to try a new network card...
>
> Thanks,
> Craig
>
> peter green wrote:
>
> >checksum offload on some network cards has been known to cause
> problems with
> >communication from host-guest
> >
> >if all else fails you can always buy a cheap realtek ;)
> >
> >
> >
> >>-----Original Message-----
> >>From: col...@li...
> >>[mailto:col...@li...]On Behalf Of Curtis,
> >>Craig
> >>Sent: 12 October 2004 12:33
> >>To: col...@li...
> >>Subject: [coLinux-users] crossing the bridge
> >>
> >>
> >>It seems that only pinging is supported as a network protocol between
> >>the Windows side and Colinux on a bridged network.  I can ping just
> >>fine, but FTP, smb, and other protocols do not work on the same PC, but
> >>from another PC they do work.
> >>
> >>Is there a configuration on the PC-TAP network driver or in Win2K that I
> >>can change somewhere to allow this to work?
> >>
> >>Thanks,
> >>Craig
> >>
> >>
> >>-------------------------------------------------------
> >>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> >>Use IT products in your business? Tell us what you think of
> them. Give us
> >>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> >>find out more
> >>http://productguide.itmanagersjournal.com/guidepromo.tmpl
> >>_______________________________________________
> >>coLinux-users mailing list
> >>coL...@li...
> >>https://lists.sourceforge.net/lists/listinfo/colinux-users
> >>
> >>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] reiserfs error during boot, but I have xfs?

[Brian K. <br...@kr...>]

Hi,

This is a snippet of my boot screen;

cobd5 size: 1020096 kb
cobd6 size: 522081 kb
cobd7 size: 5349613 kb
cobd: loaded (max 32 devices)
conet: loaded (max 16 devices)
conet0: initialized
FAT: bogus logical sector size 0
UMSDOS: msdos_read_super failed, mount aborted.
FAT: bogus logical sector size 0
FAT: bogus logical sector size 0
sh-2021: reiserfs_read_super: can not find reiserfs on cobd(117,7)
Kernel panic: VFS: Unable to mount root fs on 75:07

My partition layout (being XFS fs);

/dev/hda5 /boot = 1GB
/dev/hda6 swap = 500MB
/dev/hda7 / = 5GB

My xml;

<block_device index="5" path="\Device\Harddisk0\Partition4" enabled="true" 
/>
<block_device index="6" path="\Device\Harddisk0\Partition5" enabled="true" 
/>
<block_device index="7" path="\Device\Harddisk0\Partition6" enabled="true" 
/>
<bootparams>ro root=/dev/cobd7 colinux 4</bootparams>

Does any one have some ideas for me?
I'll buy you a beer.

Bri- 

Re: [coLinux-users] reiserfs error during boot, but I have xfs?

[Nuno L. <ml-...@xp...>]

Brian Krusic, dando pulos de alegria, escreveu :
[...]
> FAT: bogus logical sector size 0
> UMSDOS: msdos_read_super failed, mount aborted.
> FAT: bogus logical sector size 0
> FAT: bogus logical sector size 0
> sh-2021: reiserfs_read_super: can not find reiserfs on cobd(117,7)
> Kernel panic: VFS: Unable to mount root fs on 75:07
> 
> My partition layout (being XFS fs);
[...]

The current linux kernel has XFS as a module. When it tries to open the
root partition the modules aren't loaded yet, so it fails (after trying
the file systems it knows about).

The solution would be to either use a non-XFS image as root or
create an initrd image that will allow the xfs module to be loaded.

Another option is compiling a new kernel with xfs linked into.

-- 
Regards,
~Nuno Lucas

Re: [coLinux-users] reiserfs error during boot, but I have xfs?

[Ian B. <ib...@gm...>]

Ok, I think what Brian was talking about is why are there errors at
all here. I have a feeling that the way the new 2.6.8 kernel works is
that it doesn't have any filesystem drivers compiled into it, but
instead loads them at boot time. The only way to do that is by loading
an initrd and testing your filesystem for all the different filesystem
types. Hence, the error messages. (I.E. its trying to fsck-like-test
each filesystem driver against your partition, and the only one that
works, is the one that loads). Its a rather brute-force attack, but
its quite good if you want to ship out a generic kernel to a whole
slew of systems and insure that it works on all of them.

Ian

On Wed, 13 Oct 2004 02:23:15 +0100, Nuno Lucas <ml-...@xp...> wrote:
> Brian Krusic, dando pulos de alegria, escreveu :
> [...]
> > FAT: bogus logical sector size 0
> > UMSDOS: msdos_read_super failed, mount aborted.
> > FAT: bogus logical sector size 0
> > FAT: bogus logical sector size 0
> > sh-2021: reiserfs_read_super: can not find reiserfs on cobd(117,7)
> > Kernel panic: VFS: Unable to mount root fs on 75:07
> >
> > My partition layout (being XFS fs);
> [...]
> 
> The current linux kernel has XFS as a module. When it tries to open the
> root partition the modules aren't loaded yet, so it fails (after trying
> the file systems it knows about).
> 
> The solution would be to either use a non-XFS image as root or
> create an initrd image that will allow the xfs module to be loaded.
> 
> Another option is compiling a new kernel with xfs linked into.
> 
> --
> Regards,
> ~Nuno Lucas
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] crossing the bridge

[Curtis, C. <Cra...@ec...>]

Yes.  This seems to be my problem.  I have an Intel Pro/1000 and I do 
not see a way to get to ChecksumRxTcp.  I found the other parameters in 
my registry, but ChecksumRxTcp does not appear to exist.  Could the 
networking docs have a typo?

Otherwise, I may need to try a new network card...

Thanks,
Craig

peter green wrote:

>checksum offload on some network cards has been known to cause problems with
>communication from host-guest
>
>if all else fails you can always buy a cheap realtek ;)
>
>  
>
>>-----Original Message-----
>>From: col...@li...
>>[mailto:col...@li...]On Behalf Of Curtis,
>>Craig
>>Sent: 12 October 2004 12:33
>>To: col...@li...
>>Subject: [coLinux-users] crossing the bridge
>>
>>
>>It seems that only pinging is supported as a network protocol between
>>the Windows side and Colinux on a bridged network.  I can ping just
>>fine, but FTP, smb, and other protocols do not work on the same PC, but
>>from another PC they do work.
>>
>>Is there a configuration on the PC-TAP network driver or in Win2K that I
>>can change somewhere to allow this to work?
>>
>>Thanks,
>>Craig
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>>Use IT products in your business? Tell us what you think of them. Give us
>>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
>>find out more
>>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>>_______________________________________________
>>coLinux-users mailing list
>>coL...@li...
>>https://lists.sourceforge.net/lists/listinfo/colinux-users
>>    
>>

Re: [coLinux-users] crossing the bridge

[Brian K. <br...@kr...>]

Hi,

> not see a way to get to ChecksumRxTcp.  I found the other parameters in my 
> registry, but ChecksumRxTcp does not appear to exist.

Add the key and see what happens.

I've added keys before to manipulate tcp windows sizes, etc and it didn't 
break anything.

Bri-