Alexander Heinz | 1 Feb 2005 01:11
Picon

Re: yet another boot scenario?

> the default scsi
> 
> the built-in pxe support crashes as well. . .but the old 5.2.2 disk 
> image works.

Your version of VMWare crashes if you use the PXE-ROM?
Please contact VMWare support...

BTW: I use IDE hard disk emulation. I have not tried SCSI. Did you try IDE?

Alex

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
Igor Naumov | 1 Feb 2005 02:12
Picon
Favicon

Re: [Thinstation-general] RE: Thinstation 2.1rc2 - PCMCIA

I have not tried rc1 or rc2 yet, hopefully it's all fixed in those versions,
so just in case somebody overlooked something (e.g. I found out that all
that stuff does not work without cardmgr).

The next thing would be to get the wireless working - I got as far as
loading the module, but the interface does not show up in wfconfig...

Igor

----- Original Message ----- 
From: "TechFan" <lists.sf.net@...>
To: "Igor Naumov" <igornaumov@...>
Cc: "Miles Roper" <mroper@...>; "Thinstation General"
<thinstation-general@...>;
<thinstation-developer@...>
Sent: Monday, January 31, 2005 5:26 PM
Subject: Re: [Thinstation-general] RE: Thinstation 2.1rc2 - PCMCIA

> Sounds like you got it working.  Good.  Actually, PCMCIA is already
> working starting in 2.1rc1.  Just the order modules are loaded still
> needs to be modified.  Just add the line:
>
> module ds
>
> after your module yenta_socket in the build.conf of 2.1rc2 and it should
> be working.
>
> so, the order in your build needs to be:
>
> pcmcia
(Continue reading)

Miles Roper | 1 Feb 2005 02:10
Picon
Favicon

RE: [Thinstation-general] RE: Thinstation 2.1rc2 - PCMCIA


wireless was included in rc1+2 :o) 

-----Original Message-----
From: Igor Naumov [mailto:igornaumov@...] 
Sent: Tuesday, 1 February 2005 02:12 p.m.
To: TechFan
Cc: Miles Roper; Thinstation General;
thinstation-developer@...
Subject: Re: [Thinstation-general] RE: Thinstation 2.1rc2 - PCMCIA

I have not tried rc1 or rc2 yet, hopefully it's all fixed in those versions,
so just in case somebody overlooked something (e.g. I found out that all
that stuff does not work without cardmgr).

The next thing would be to get the wireless working - I got as far as
loading the module, but the interface does not show up in wfconfig...

Igor

----- Original Message -----
From: "TechFan" <lists.sf.net@...>
To: "Igor Naumov" <igornaumov@...>
Cc: "Miles Roper" <mroper@...>; "Thinstation General"
<thinstation-general@...>;
<thinstation-developer@...>
Sent: Monday, January 31, 2005 5:26 PM
Subject: Re: [Thinstation-general] RE: Thinstation 2.1rc2 - PCMCIA

> Sounds like you got it working.  Good.  Actually, PCMCIA is already
(Continue reading)

Victor Sudakov | 1 Feb 2005 04:21
Picon

Re: Re: yet another boot scenario?

Alexander Heinz wrote:
> >Should have mentioned that I use pxelinux.0 & initrd and that works fine 
> >(didn't
> >try thinstation.nbi.zpxe.....). My understanding is that the new approach
> >replaces the need for thinstation.nbi.zpxe (I haven't tried loading the nbi
> >directly tho...).
> 
> That is correct. PXELinux works with PXE-ROMs and the latest version of 
> Etherboot.

Starting from what version does Etherboot support PXELinux ?
Does it also support other PXE loaders (e.g. the FreeBSD pxeboot(8) loader) 
or specifically PXELinux ?

--

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
Victor Sudakov | 1 Feb 2005 06:53
Picon

Re: Re: yet another boot scenario?

> > >Should have mentioned that I use pxelinux.0 & initrd and that works fine 
> > >(didn't
> > >try thinstation.nbi.zpxe.....). My understanding is that the new approach
> > >replaces the need for thinstation.nbi.zpxe (I haven't tried loading the nbi
> > >directly tho...).
> > 
> > That is correct. PXELinux works with PXE-ROMs and the latest version of 
> > Etherboot.
> 
> Starting from what version does Etherboot support PXELinux ?
> Does it also support other PXE loaders (e.g. the FreeBSD pxeboot(8) loader) 
> or specifically PXELinux ?

As it turned out, the Universal boot floppy (BootDisk522b.zip)
available from the thinstation download page, cannot load pxelinux.0
(says "invalid image"). If I migrate to the new approach (no NBI, just
PXE), where can I obtain the Universal boot floppy with PXE support?
Or can I create one myself?

--

-- 
Victor Sudakov,  VAS4-RIPE, VAS47-RIPN

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
TechFan | 1 Feb 2005 07:17

Re: Re: yet another boot scenario?

For me, SCSI is the default (and recommended in the settings) when 
creating a new machine.  It doesn't crash, but it fails to load the zpxe 
and nbi image fed via DHCP  I have the latest available version of 
VMWare 4.5.  again, the etherboot 5.2.2 disk works. . .so that is what I 
will stick with for now.

Alexander Heinz wrote:

>> the default scsi
>>
>> the built-in pxe support crashes as well. . .but the old 5.2.2 disk 
>> image works.
>
>
> Your version of VMWare crashes if you use the PXE-ROM?
> Please contact VMWare support...
>
> BTW: I use IDE hard disk emulation. I have not tried SCSI. Did you try 
> IDE?
>
> Alex
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
(Continue reading)

TechFan | 1 Feb 2005 07:33

Re: Re: yet another boot scenario?

I changed to IDE and then I was able to at least install to the 
harddrive.  With SCSI emulation fdisk finds no disks.  When using the 
floppy image installed to the harddrive. . .it still crashes the vm 
saying it would have reset the processor.

Alexander Heinz wrote:

>> the default scsi
>>
>> the built-in pxe support crashes as well. . .but the old 5.2.2 disk 
>> image works.
>
>
> Your version of VMWare crashes if you use the PXE-ROM?
> Please contact VMWare support...
>
> BTW: I use IDE hard disk emulation. I have not tried SCSI. Did you try 
> IDE?
>
> Alex
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Thinstation-developer mailing list
(Continue reading)

Victor Sudakov | 1 Feb 2005 09:54
Picon

Re: Re: yet another boot scenario?

I have come to the conclusion that my problems with booting from
Paolo's package ver. 5.3.12 are not specific to the package.

This borders on offtopic but perhaps someone will give me information
as to what is happening.

1. I go to http://rom-o-matic.net/5.3.12/ and make a .com image for my
NIC (Intel PRO/100 VE Network Connection, eepro100-1032). No
customizations.

2. I write the resulting ROM eb-5.3.12-eepro100.com
to a MS-DOS 6.22 floppy as a:\test.com

3. I boot from the floppy and run test.com

What happens next, the image finds the NIC and says

Searching for server
..Me: 172.16.138.74, Server: 172.16.138.120, Gateway 172.16.138.61
Loading 172.16.138.120:pxelinux.0 ..(PXE)done

After this, everything just waits forever, nothing is happening.

If I enable the hardware PXE LAN boot in BIOS, I get the thinstation
boot over network all right, which means the problem is not likely
with my DHCP or TFTP server configuration.

Any ideas?

--

-- 
(Continue reading)

Paolo Salvan | 1 Feb 2005 11:48
Picon

Re: Re: yet another boot scenario?

Hi Victor,

You should probably post your troubles to the etherboot-developer 
mailing-list

Before reporting your problem, test also if it happens with .zdsk file 
format (bootable floppy), just to understand if the image format is 
relevant or not.
And, if possible, try with another NIC also...

Bye,

Paolo

Victor Sudakov ha scritto:
> I have come to the conclusion that my problems with booting from
> Paolo's package ver. 5.3.12 are not specific to the package.
> 
> This borders on offtopic but perhaps someone will give me information
> as to what is happening.
> 
> 1. I go to http://rom-o-matic.net/5.3.12/ and make a .com image for my
> NIC (Intel PRO/100 VE Network Connection, eepro100-1032). No
> customizations.
> 
> 2. I write the resulting ROM eb-5.3.12-eepro100.com
> to a MS-DOS 6.22 floppy as a:\test.com
> 
> 3. I boot from the floppy and run test.com
> 
(Continue reading)

Victor Sudakov | 1 Feb 2005 12:10
Picon

Re: Re: yet another boot scenario?

Paolo Salvan wrote:
> 
> You should probably post your troubles to the etherboot-developer 
> mailing-list

I will. But does anyone here care to reproduce?
I think the universal boot floppy is part of the TS project, and if
etherboot does not work, neither will the floppy.

> 
> Before reporting your problem, test also if it happens with .zdsk file 
> format (bootable floppy), just to understand if the image format is 
> relevant or not.

Exactly the same behavior (stop after "..(PXE)done") with a .zdsk file.

> And, if possible, try with another NIC also...

I have just tried a rtl8139 as well, with the same negative result.

> 
> Victor Sudakov ha scritto:
> >I have come to the conclusion that my problems with booting from
> >Paolo's package ver. 5.3.12 are not specific to the package.
> >
> >This borders on offtopic but perhaps someone will give me information
> >as to what is happening.
> >
> >1. I go to http://rom-o-matic.net/5.3.12/ and make a .com image for my
> >NIC (Intel PRO/100 VE Network Connection, eepro100-1032). No
(Continue reading)


Gmane