[Thinbsd] ThinBSD connecting to OpenBSD X-Windows

[Francois Tigeot]

On Thu, Sep 22, 2005 at 01:28:14PM -0600, Whyzzi wrote:
> What are the chances of having the Intel 100/s series of network
> adapters supported?

Reasonably good.
I will try to build a new kernel with the fxp driver when I find a moment.

> I'm a complete and utter knewb setting up a test environment using
> OpenBSD as the XWindows server and ThinBSD as the pxe boot
> loader/graphical client. I've hit a wall in the boot process and all I
> can think of that would be wrong in my setup is the ethernet adapter.
> 
> ===================
> this is what my P3 600Mhz client spits out:
> 
> FreeBSD/i386 bootstrap loader, Revision 1.1
> (ftigeot at bajor.zefyris.com, Wed May 18, 20:40:09 UTC 2005)
> pxe_open: server addr: 172.16.6.5
> pxe_open: server path: /pxeroot
> pxe_open: gatewayip: 0.0.0.0
> start not found
> |
> can't load 'kernel'
> 
> Type '?' for a list of commands, 'help' for more help.
> OK _

>From what I see, the ethernet adapter is not the problem yet. The boot
loader is unable to load the kernel.

> ==============
> I'm using ISC DHCP3 form the openbsd prebuilt packages, although I am
> not too sure about the config: (I'm going to continue to play with
> this today and see what happens).
 
[...]

> subnet 172.16.6.0 netmask 255.255.255.0
> {
>      range 172.16.6.100 172.16.6.200;
>      option subnet-mask 255.255.255.0;
>      option broadcast-address 172.16.6.255;
> 
>      option domain-name "termserv.sapl.ab.ca";
>      option domain-name-servers 172.16.6.5;
>      server-name "dhcp";
>      server-identifier 172.16.6.5;
> 
>      max-lease-time 115200;
>      default-lease-time 86400;
> 
> 	filename "/boot/pxeboot";
> 	
> 	option thinbsd-lang "en_US";
> 	option thinbsd-use-rdp false;
> 	option x-display-manager 172.16.6.5;
> 	option font-servers 172.16.6.5;
> }

I see nothing wrong in this file.
The message 'start not found' is most suspicious. Be sure all the files in
the boot directory are present.

This is what I have in my /tftpboot/boot
-r--r--r--  1 root  wheel   6,8K 19 mai 10:42 beastie.4th
-r--r--r--  1 root  wheel   8,0K 19 mai 10:42 boot
-r--r--r--  1 root  wheel   512B 19 mai 10:42 boot0
-r--r--r--  1 root  wheel   512B 19 mai 10:42 boot0sio
-r--r--r--  1 root  wheel   512B 19 mai 10:42 boot1
-r--r--r--  1 root  wheel   7,5K 19 mai 10:42 boot2
-r--r--r--  1 root  wheel   1,2K 19 mai 10:42 cdboot
drwxr-xr-x  2 root  wheel   512B 19 mai 10:42 defaults
-r--r--r--  1 root  wheel   1,9K 19 mai 10:50 device.hints
-r--r--r--  1 root  wheel   2,2K 19 mai 10:42 frames.4th
drwxr-xr-x  2 root  wheel   512B 19 mai 15:44 kernel
-r-xr-xr-x  1 root  wheel   196K 19 mai 10:42 loader
-r--r--r--  1 root  wheel   7,6K 19 mai 10:42 loader.4th
-r--r--r--  1 root  wheel    14K 19 mai 10:42 loader.help
-r--r--r--  1 root  wheel   292B 19 mai 15:52 loader.rc
-r--r--r--  1 root  wheel   512B 19 mai 10:42 mbr
drwxr-xr-x  2 root  wheel   512B 19 mai 10:42 modules
-r--r--r--  1 root  wheel   198K 19 mai 10:42 pxeboot
-r--r--r--  1 root  wheel   692B 19 mai 10:42 screen.4th
-r--r--r--  1 root  wheel    36K 19 mai 10:42 support.4th

Extracting the boot tarball in the tftp directory should give you these
files.

-- 
Francois Tigeot