Dear Tim ,
Thanks for reply me ,
I verify nic id and it is like below :-
my nic is :- DFE 538 TX .
# lspci
01:0d.0 Ehternet Controller : Realtek Semiconductor Co., Ltd
RTL-8139/8139C/8139C+/ (Rev) 10
#lspci
01:0d.0 Ehternet Controller : Realtek Semiconductor Co., Ltd
RTL-8139/8139C/8139C + -r10 "8139" "434e"
please tell me above is correct pci device and vendor id.
I used eb-5[1].2.2-16ab-1101.zrom for burning rom (nm 27c256 ) . and enable
using dos diag.exe for activate rom ( 32 kb)
I have one question is there any difference in address like floopy using
address range [00013bd0,000249e0] to
[0feaf1f0,0fec0000] and boot rom addresses are [00024210,00033849] to
[0feb09d0,0fec0000]
please reply me
with best regards ,
Piyush Patel
-----Original Message-----
From: Timothy Legge [mailto:[EMAIL PROTECTED]
Sent: Friday, December 26, 2003 6:58 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Ltsp-discuss] Bootrom give error probing pci nic
> when i insert that boot rom in nic ,and restaring machine it gives me
> error like
>
> probing pci nic
> probinc isa nic
> <sleep>
>
> Can any one tell me where is problem . nic work find with bootable
> floopy . is there any bootrom error or settings .
Please ensure that you have selected the correct rom file the pci device and
vendor ids must match. Use lspci on Linux to verify the ids (copy lspci to
your ltsp root if necessary).
Tim
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Saturday, December 27, 2003 9:41 AM
To: [EMAIL PROTECTED]
Subject: Ltsp-discuss digest, Vol 1 #1379 - 6 msgs
Send Ltsp-discuss mailing list submissions to
[EMAIL PROTECTED]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Ltsp-discuss digest..."
Today's Topics:
1. Re: using eth1 in lieu of eth0 (chris bayley)
2. Re: Mandrake 9.2 and Ltsp3 (John McCreesh)
3. Bootrom give error probing pci nic (Piyush Patel)
4. Re: Bootrom give error probing pci nic (Timothy Legge)
5. Re: using eth1 in lieu of eth0 ([EMAIL PROTECTED])
6. Warning - ltsp_sound-3.0.1 not compatible with LTSP-4 (John McCreesh)
--__--__--
Message: 1
Date: Fri, 26 Dec 2003 21:50:09 +1300
From: chris bayley <[EMAIL PROTECTED]>
Subject: Re: [Ltsp-discuss] using eth1 in lieu of eth0
To: [EMAIL PROTECTED]
Sudev Barar wrote:
>On Wed, 2003-12-24 at 02:18, chris bayley wrote:
>
>
>>My kernel boots and detects 2 NICs, both eepro100, one built-in but
>>disfunctional(pxe) and the one that I have added.
>>Despite the fact the the built-in is disabled in BIOS it is still found
>>and made eth0 by the kernel the init/linuxrc script (actually I can't
>>find it) calls dhclient on eth0 which is unconnected and it all turns
>>pear shape.
>>
>>how to I specify that eth1 is to be used and not eth0, on a host by host
>>basis ?
>>
>>
>Similar setup issue here. What you need to do is specify the MAC address
>of eth1 in your /etc/dhcpd.conf file and give this workstation a fixed
>IP number. This should solve the problem. Let me know if you need format
>of the fixed ip section in dhcpd
>
>
Further study shows it not quite as simple as that;- yes I already fix
an address for eth1 in my dhcp.conf and that part goes ok until after
the kernel boots, but the kernel calls the "linuxrc" init script from
the initrd, "linuxrc" has "dhclient eth0" hardcoded in to it. So, it
will need to be hacked for eth1 or auto and the kernel/initrd rebuilt.
Just have to work that part through a little more and it should be all go.
FYI the above is true for LTSP3 - I haven't looked at 4 yet.
/chris
--__--__--
Message: 2
Date: Fri, 26 Dec 2003 09:11:13 +0000
From: John McCreesh <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: [Ltsp-discuss] Mandrake 9.2 and Ltsp3
Organization: At Home
I've had the same issue with a fresh install of ltsp-4 on Fedora Core 1.
I've changed two seetings in gdm.conf:
DisplaysPerHost=2
MaxSessions=16
and so far no problems...
John
On Thu, 25 Dec 2003 17:08:24 -0300
Bruno Luciani <[EMAIL PROTECTED]> wrote:
> I just have instaled Ltsp after reinstall my server with MDK 9.2
> To do this I change the version of Mandrake to 9.1 and the install
> works ok but I have a little trouble : after some boots of the
> workstations , its not starts anymore and crash with a message : xdmcp
> rached maximun number of sessions.
>
> I change the maximun sessions in gdm.conf but only works more time and
> then crash again ..
>
> Its seem that the server have an acount of sesions started and at some
> number of logins xdmcp crash.
>
>
> any help whit that
>
> thanks in advance
>
>
> Bruno Luciani
--__--__--
Message: 3
From: Piyush Patel <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Organization: ICubix infotech Limited
Date: 26 Dec 2003 18:45:31 +0530
Subject: [Ltsp-discuss] Bootrom give error probing pci nic
Dear All ,
I am facing a problem with boot rom .
I have realket 8139 chipset card , i download image from
www.rom-o-matic.net and burn it on nm27c256 boot rom ,
bootrom was successfully written .
when i insert that boot rom in nic ,and restaring machine it gives me
error like
probing pci nic
probinc isa nic
<sleep>
Can any one tell me where is problem . nic work find with bootable
floopy . is there any bootrom error or settings .
please reply me
with best regards ,
Piyush Patel ,
--__--__--
Message: 4
From: Timothy Legge <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>
Subject: Re: [Ltsp-discuss] Bootrom give error probing pci nic
Date: Fri, 26 Dec 2003 13:27:37 +0000
> when i insert that boot rom in nic ,and restaring machine it gives me
> error like
>
> probing pci nic
> probinc isa nic
> <sleep>
>
> Can any one tell me where is problem . nic work find with bootable
> floopy . is there any bootrom error or settings .
Please ensure that you have selected the correct rom file the pci device and
vendor ids must match. Use lspci on Linux to verify the ids (copy lspci to
your ltsp root if necessary).
Tim
--__--__--
Message: 5
Date: Fri, 26 Dec 2003 08:41:51 -0500 (EST)
From: [EMAIL PROTECTED]
To: chris bayley <[EMAIL PROTECTED]>
cc: [EMAIL PROTECTED]
Subject: Re: [Ltsp-discuss] using eth1 in lieu of eth0
On Fri, 26 Dec 2003, chris bayley wrote:
> Sudev Barar wrote:
>
> >On Wed, 2003-12-24 at 02:18, chris bayley wrote:
> >
> >
> >>My kernel boots and detects 2 NICs, both eepro100, one built-in but
> >>disfunctional(pxe) and the one that I have added.
> >>Despite the fact the the built-in is disabled in BIOS it is still found
> >>and made eth0 by the kernel the init/linuxrc script (actually I can't
> >>find it) calls dhclient on eth0 which is unconnected and it all turns
> >>pear shape.
> >>
> >>how to I specify that eth1 is to be used and not eth0, on a host by host
> >>basis ?
> >>
> >>
> >Similar setup issue here. What you need to do is specify the MAC address
> >of eth1 in your /etc/dhcpd.conf file and give this workstation a fixed
> >IP number. This should solve the problem. Let me know if you need format
> >of the fixed ip section in dhcpd
> >
> >
> Further study shows it not quite as simple as that;- yes I already fix
> an address for eth1 in my dhcp.conf and that part goes ok until after
> the kernel boots, but the kernel calls the "linuxrc" init script from
> the initrd, "linuxrc" has "dhclient eth0" hardcoded in to it. So, it
> will need to be hacked for eth1 or auto and the kernel/initrd rebuilt.
> Just have to work that part through a little more and it should be all go.
At the point that /linuxrc is running, the kernel doesn't know
anything about eth0 or eth1. they don't yet exist.
The /linuxrc script then looks at the pci bus, and sees the first
NIC and loads the appropriate kernel module for that nic, and
that is how it becomes eth0. If the 2 nics are the same, then
eth1 springs into existance as well.
I think a simple tweak to /linuxrc and the dhclient script to
tell it to use eth1 instead should handle this problem.
>
> FYI the above is true for LTSP3 - I haven't looked at 4 yet.
LTSP-3 and LTSP-4 use EXACTLY the same kernels, so this applies
equally to both.
Jim McQuillan
[EMAIL PROTECTED]
--__--__--
Message: 6
Date: Fri, 26 Dec 2003 14:42:18 +0000
From: John McCreesh <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Andrew Williams <[EMAIL PROTECTED]>
Organization: At Home
Subject: [Ltsp-discuss] Warning - ltsp_sound-3.0.1 not compatible with
LTSP-4
If you install ltsp-4, and then install ltsp_sound-3.0.1-i386.tgz, the
install.sh from ltsp_sound overrwites the new i386/bin/getltscfg with an
old version from ltsp_sound/i386/bin/getltscfg. Unfortuntely, the old
getlstcfg breaks the new scripts. If this happens, re-install ltsp-4,
but back up your lts.conf first as re-installing will overwrite any
changes you have made.
Jim - one for the errata page maybe?
John
--__--__--
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
End of Ltsp-discuss Digest
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
