[opensuse] remote installation
Hi, I have been trying to install the os on two computers that won't boot from the install dvd. I have been trying to install using tftp and pxe via lan, but its not working. I think the problem may be that I don't have the dhcp-server set up correctly on this computer, as the client computer isn't getting an ip address when it boots with dhcp. Is it possible to help me with setting up the server correctly? I don't know how to do this, really, so you will have to expect some replies that might seem kind of dumb until I learn what to do. Also, I have been trying to set it up to netboot, but I think it is possible to boot from the iso image that I have on the server computer. How would I do this? Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich wrote:
Hi, I have been trying to install the os on two computers that won't boot from the install dvd.
did you do this http://tinyurl.com/25ydj4a before the boot attempt? if not, try that first and if you have _any_ errors see the helpful info at, as you may have a corrupt download or disk: http://en.opensuse.org/SDB:Download_help http://tinyurl.com/yhf65pv http://tinyurl.com/2fbt7j9 DenverD -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 17:35 +0200, DenverD wrote:
Mark Misulich wrote:
Hi, I have been trying to install the os on two computers that won't boot from the install dvd.
did you do this http://tinyurl.com/25ydj4a before the boot attempt?
if not, try that first and if you have _any_ errors see the helpful info at, as you may have a corrupt download or disk:
http://en.opensuse.org/SDB:Download_help http://tinyurl.com/yhf65pv http://tinyurl.com/2fbt7j9
DenverD
Hi, no I haven't done a media check on the dvd, but I have used it on other computers to do a successful installation. It seems to be a problem with this computer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich wrote:
Hi, I have been trying to install the os on two computers that won't boot from the install dvd. I have been trying to install using tftp and pxe via lan, but its not working. I think the problem may be that I don't have the dhcp-server set up correctly on this computer, as the client computer isn't getting an ip address when it boots with dhcp.
You should be able to determine that from the /var/log/messages where your dhcp server is running.
Is it possible to help me with setting up the server correctly? I don't know how to do this, really, so you will have to expect some replies that might seem kind of dumb until I learn what to do.
Sure, let us know how far you have gotten. -- Per Jessen, Zürich (12.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 17:41 +0200, Per Jessen wrote:
Mark Misulich wrote:
Hi, I have been trying to install the os on two computers that won't boot from the install dvd. I have been trying to install using tftp and pxe via lan, but its not working. I think the problem may be that I don't have the dhcp-server set up correctly on this computer, as the client computer isn't getting an ip address when it boots with dhcp.
You should be able to determine that from the /var/log/messages where your dhcp server is running.
Is it possible to help me with setting up the server correctly? I don't know how to do this, really, so you will have to expect some replies that might seem kind of dumb until I learn what to do.
Sure, let us know how far you have gotten.
Hi, I found this message in /var/log/boot.omsg Setting up (remotefs) network interfaces: Setting up service (remotefs) network . . . . . . . . . .done Starting DHCP server Internet Systems Consortium DHCP Server V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ /var/lib/dhcp///etc/dhcpd.conf line 16: expecting numeric value. subnet 192.168.1.0netmask ^ Configuration file errors encountered -- exiting If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get this software from ftp.isc.org and have not yet read the README, please read it before requesting help. If you intend to request help from the dhcp-server@isc.org mailing list, please read the section on the README about submitting bug reports and requests for help. Please do not under any circumstances send requests for help directly to the authors of this software - please send them to the appropriate mailing list as described in the README file. exiting. failed After I installed the dhcp-server program with yast, I also didn't find a file like /etc/dhcp-server/dhcpd.conf. I did find /etc/dhcp.conf, and I pasted a sample configuration into it from the tutorial that I was using. The tutorial didn't go into depth about how to set up the server. My lan is my desktop computer connected to my wireless/wired router. The router is connected to my dsl modem via cable. The laptop computer that I am trying to install the os on is connected to the router via cable. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich said the following on 09/28/2010 12:42 PM:
My lan is my desktop computer connected to my wireless/wired router. The router is connected to my dsl modem via cable. The laptop computer that I am trying to install the os on is connected to the router via cable.
I no longer run a LAN quite like that, but when I did ... My ISP ran a DHCP _server_ that have the dynamic IP address to the (wired) internet-facing side of my wireless router. The wireless router had a bridge so that the wireless and the four Ethernet ports on the back were on the same subnet. (I can't say I like that, but never mind) The wireless router ran a DHCP _server_ for those ports My laptops(s) were wired in to the Ethernet ports. (Why? 'Cos they were on the same table. When I went out to the patio I used the wireless connection.) My laptop(s) ran DHCP __CLIENTS__ Not servers. CLIENTS They got their LAN address from the DHCP server on the wireless router. I think your problem is that you are running a server when you should be running a client. I might be wrong, I'm making a few suppositions about your network layout. You might also not have the DHCP server on your wireless/router turned on. Lots of "IF"s. But that's my guess. -- The whole art of teaching is only the art of awakening the natural curiosity of young minds for the purpose of satisfying it afterwards. -- Anatole France (1844 - 1924), The Crime of Sylvestre Bonnard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 13:08 -0400, Anton Aylward wrote:
Mark Misulich said the following on 09/28/2010 12:42 PM:
My lan is my desktop computer connected to my wireless/wired router. The router is connected to my dsl modem via cable. The laptop computer that I am trying to install the os on is connected to the router via cable.
I no longer run a LAN quite like that, but when I did ...
My ISP ran a DHCP _server_ that have the dynamic IP address to the (wired) internet-facing side of my wireless router. I think mine does as well.
The wireless router had a bridge so that the wireless and the four Ethernet ports on the back were on the same subnet. I don't know how to find that out. I can get to the gateway page and poke around in there to find out, it I knew what to look for. (I can't say I like that, but never mind)
The wireless router ran a DHCP _server_ for those ports I don't know how to find that out either. Same qualification as above. My laptops(s) were wired in to the Ethernet ports. (Why? 'Cos they were on the same table. When I went out to the patio I used the wireless connection.)
My laptop(s) ran DHCP __CLIENTS__ Not servers. CLIENTS
They got their LAN address from the DHCP server on the wireless router. I think that PXEboot is a client, its what I am trying to boot on the laptop. There is no operating system on the laptop, I am booting from the "boot from lan" option in the bios. I think your problem is that you are running a server when you should be running a client. I might be wrong, I'm making a few suppositions about your network layout. You might also not have the DHCP server on your wireless/router turned on. Lots of "IF"s.
But that's my guess. Here is a more detailed explanation of what I am trying to do that will hopefully clear up the confusion.
http://polishlinux.org/installation/installing-linux-over-network-no-cd-driv... I have been following this tutorial and others like it, trying to adapt it to suse.
-- The whole art of teaching is only the art of awakening the natural curiosity of young minds for the purpose of satisfying it afterwards. -- Anatole France (1844 - 1924), The Crime of Sylvestre Bonnard
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich wrote:
I think that PXEboot is a client,
Yes it is. It is a Preboot Execution Environment that some servers and network cards come with. Basically, the PXE setup will ask a DHCP server for an IP-address and the name of a TFTP server, then carry on from there.
http://polishlinux.org/installation/installing-linux-over-network-no-cd-driv...
I have been following this tutorial and others like it, trying to adapt it to suse.
You need a working DHCP server and a working TFTP server. They may be one and the same. In my case, I used to boot a cluster via PXE from etherboot@floppy. The DHCP dishes out an IP-address and a "next-server" and a filename. The PXE setup will then try to use TFTP to get <filename> from <next-server>. Because you already have a working PXE setup, courtesy of your network card, I'm not entirely sure how to continue - I would expect to find some messages from your tftp server that could point us in the right direction. -- Per Jessen, Zürich (10.5°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich said the following on 09/28/2010 01:26 PM:
On Tue, 2010-09-28 at 13:08 -0400, Anton Aylward wrote:
My ISP ran a DHCP _server_ that have the dynamic IP address to the (wired) internet-facing side of my wireless router.
I think mine does as well.
Very likely. Many do. If needed, which I doubt, you can phone and ask.
The wireless router had a bridge so that the wireless and the four Ethernet ports on the back were on the same subnet.
I don't know how to find that out. I can get to the gateway page and poke around in there to find out, it I knew what to look for.
I don't see why you should. You can just assume it is so for now and proceed with setting up your laptop to run a client.
The wireless router ran a DHCP _server_ for those ports I don't know how to find that out either. Same qualification as above.
Does the manual for the wireless router tell you how to "log in"? Mine - a SMC - tells me to have a machine (for example a laptop) access http://102.160.2.1 You'll have to check the manual for the address and the default login for your equipment. After logging in I'm sure you'll ave a "GEE! WOW!" moment. You'll be able to see a lot about how your router is and can be configured. But honestly, if you just press the reset button and proceed with below, you needn't worry about all that :-)
My laptops(s) were wired in to the Ethernet ports. (Why? 'Cos they were on the same table. When I went out to the patio I used the wireless connection.)
My laptop(s) ran DHCP __CLIENTS__ Not servers. CLIENTS
They got their LAN address from the DHCP server on the wireless router.
I think that PXEboot is a client, its what I am trying to boot on the laptop. There is no operating system on the laptop, I am booting from the "boot from lan" option in the bios.
Are you commuted to that? Is booting from a CD or a CD image on a USB stick completely forbidden? What is your priority here? Getting it loaded or getting PXEBoot to work?
I think your problem is that you are running a server when you should be running a client. I might be wrong, I'm making a few suppositions about your network layout. You might also not have the DHCP server on your wireless/router turned on. Lots of "IF"s.
But that's my guess.
Here is a more detailed explanation of what I am trying to do that will hopefully clear up the confusion.
http://polishlinux.org/installation/installing-linux-over-network-no-cd-driv...
I have been following this tutorial and others like it, trying to adapt it to suse.
I'm assuming you have the relevant PXE chip on your Ethernet card. PXE will ask for an address via DHCP. The DHCP service will need to give the address of the TFTP server. Do you have a TFTP server that is going to disk out the code? The one time I did this I had a PXE service that asked for the address of the TFTP server after it got the address to use as its own address from the DHCP server. I think you have a cascade of problems here and I think we are "fixing" the haphazardly. I you have a local server from which to do the installation then you don't need the router and internet connection (until you run updates). If you do have a server on your LAN and it has all the code needed for the install, ten we get back to your DHCP server configuration. I'm not sure why you gutted and replaced the server when there was just a type - it looked like a missing space - in your config file. My advice is to install form a CD or USB stick! When you have a running LAN, then gain experience with it and experiment with DHCP. Right now, we are advising you without enough contextual details and I suspect that you don't yet know the innards of your equipment well enough to answer some of our questions or to make reasonable assumptions about the details we omit. This is one of the problems with "debug-by-email" :-) We're not looking over your shoulder and seeing the details of what you do. And that's probably why some courses and "hands on" workshops are so popular :-) How important is completing the instillation? Important enough to go the CD route? -- The line, often adopted by strong men in controversy, of justifying the means by the end. Saint Jerome, Letter 48 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 14:37 -0400, Anton Aylward wrote:
Mark Misulich said the following on 09/28/2010 01:26 PM:
On Tue, 2010-09-28 at 13:08 -0400, Anton Aylward wrote:
My ISP ran a DHCP _server_ that have the dynamic IP address to the (wired) internet-facing side of my wireless router.
I think mine does as well.
Very likely. Many do. If needed, which I doubt, you can phone and ask.
The wireless router had a bridge so that the wireless and the four Ethernet ports on the back were on the same subnet.
I don't know how to find that out. I can get to the gateway page and poke around in there to find out, it I knew what to look for.
I don't see why you should. You can just assume it is so for now and proceed with setting up your laptop to run a client.
The wireless router ran a DHCP _server_ for those ports I don't know how to find that out either. Same qualification as above.
Does the manual for the wireless router tell you how to "log in"?
Mine - a SMC - tells me to have a machine (for example a laptop) access http://102.160.2.1 You'll have to check the manual for the address and the default login for your equipment. After logging in I'm sure you'll ave a "GEE! WOW!" moment. You'll be able to see a lot about how your router is and can be configured.
But honestly, if you just press the reset button and proceed with below, you needn't worry about all that :-)
My laptops(s) were wired in to the Ethernet ports. (Why? 'Cos they were on the same table. When I went out to the patio I used the wireless connection.)
My laptop(s) ran DHCP __CLIENTS__ Not servers. CLIENTS
They got their LAN address from the DHCP server on the wireless router.
I think that PXEboot is a client, its what I am trying to boot on the laptop. There is no operating system on the laptop, I am booting from the "boot from lan" option in the bios.
Are you commuted to that? Is booting from a CD or a CD image on a USB stick completely forbidden?
What is your priority here? Getting it loaded or getting PXEBoot to work?
I think your problem is that you are running a server when you should be running a client. I might be wrong, I'm making a few suppositions about your network layout. You might also not have the DHCP server on your wireless/router turned on. Lots of "IF"s.
But that's my guess.
Here is a more detailed explanation of what I am trying to do that will hopefully clear up the confusion.
http://polishlinux.org/installation/installing-linux-over-network-no-cd-driv...
I have been following this tutorial and others like it, trying to adapt it to suse.
I'm assuming you have the relevant PXE chip on your Ethernet card.
PXE will ask for an address via DHCP. The DHCP service will need to give the address of the TFTP server.
Do you have a TFTP server that is going to disk out the code?
The one time I did this I had a PXE service that asked for the address of the TFTP server after it got the address to use as its own address from the DHCP server.
I think you have a cascade of problems here and I think we are "fixing" the haphazardly.
I you have a local server from which to do the installation then you don't need the router and internet connection (until you run updates).
If you do have a server on your LAN and it has all the code needed for the install, ten we get back to your DHCP server configuration.
I'm not sure why you gutted and replaced the server when there was just a type - it looked like a missing space - in your config file.
My advice is to install form a CD or USB stick!
When you have a running LAN, then gain experience with it and experiment with DHCP.
Right now, we are advising you without enough contextual details and I suspect that you don't yet know the innards of your equipment well enough to answer some of our questions or to make reasonable assumptions about the details we omit.
This is one of the problems with "debug-by-email" :-) We're not looking over your shoulder and seeing the details of what you do. And that's probably why some courses and "hands on" workshops are so popular :-)
How important is completing the instillation? Important enough to go the CD route?
-- The line, often adopted by strong men in controversy, of justifying the means by the end. Saint Jerome, Letter 48
Hi, I am trying to get the operating system loaded. I think that you must be missing some of the earlier posts, or you wouldn't be asking the questions you have posted. I will try to bring you up to speed. One of the laptops has no internal cd drive, and won't boot from the external cd drive. The other laptop has an internal cd drive, but won't boot from the install dvd. I am not sure why. Neither laptop has an operating system installed. Making more cd's won't help, the laptops won't boot from them. Both laptops have a boot from lan feature using pxeboot. I thought that if I could get the boot software in via the dhcp server tftp server then I could do net installs. Yes, I do know how to get into the router's home page. But once I do, I don't find what I am looking for so I need some help to find it. Of even if I need to get in there to find anything. What isn't working is the transfer of the boot files from the desktop computer (Server)to the laptop computer (client). I have configured the desktop computer to have a dhcp server and a tftp server, but something isn't working. I believe that correct configuration is the problem, so I am asking for help to determine how to do this correctly. If I configure it correctly, then the process still doesn't work then something else must be the problem. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/09/28 14:57 (GMT-0400) Mark Misulich composed:
One of the laptops has no internal cd drive, and won't boot from the external cd drive.
Maybe both are Intel-chipped (most common old laptop chipsets), and you could do a minimal install on this laptop's HD by temporarily installing it in the other after figuring out how to install there.
The other laptop has an internal cd drive, but won't boot from the install dvd. I am not sure why.
The answer is in your own words. :-) If the internal drive were able to read DVDs it would be called a DVD drive, not a CD drive. ;-)
Neither laptop has an operating system installed. Making more cd's won't help, the laptops won't boot from them.
Unusual that an old laptop with a CD drive but lacking a floppy drive cannot be booted from a CD. Not unusual at all that a laptop BIOS must be changed to enable booting from the CD drive in preference to the HD, which is the more typical way to install an OS on such laptops. Assuming the CD drive is not broken if burning http://download.opensuse.org/distribution/11.3/iso/openSUSE-11.3-NET-i586.is... and booting it would not work after a necessary BIOS adjustment and CD drive cleaning I'd be surprised. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 15:26 -0400, Felix Miata wrote:
On 2010/09/28 14:57 (GMT-0400) Mark Misulich composed:
One of the laptops has no internal cd drive, and won't boot from the external cd drive.
Maybe both are Intel-chipped (most common old laptop chipsets), and you could do a minimal install on this laptop's HD by temporarily installing it in the other after figuring out how to install there.
The other laptop has an internal cd drive, but won't boot from the install dvd. I am not sure why.
The answer is in your own words. :-) If the internal drive were able to read DVDs it would be called a DVD drive, not a CD drive. ;-)
Neither laptop has an operating system installed. Making more cd's won't help, the laptops won't boot from them.
Unusual that an old laptop with a CD drive but lacking a floppy drive cannot be booted from a CD. Not unusual at all that a laptop BIOS must be changed to enable booting from the CD drive in preference to the HD, which is the more typical way to install an OS on such laptops. Assuming the CD drive is not broken if burning http://download.opensuse.org/distribution/11.3/iso/openSUSE-11.3-NET-i586.is... and booting it would not work after a necessary BIOS adjustment and CD drive cleaning I'd be surprised. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
Hi Felix, thanks for the reply. The drives actually are dvd drives, I should have been more correct in my terminology. One laptop won't boot from the external drive. The other won't boot from the 11.1, 2, or 3 install dvd's. It won't boot from Xubuntu 9 or 10 install cd's. It won't boot from EliveCD install cd. Both Xubuntu and EliveCD install cd's are live cd's, perhaps that is why they won't boot from them. It will boot from the PCBSD install DVD, but the graphic's driver is wrong and the screen won't display properly. I don't really want to put that on there anyways, or I would play around with the driver. I thought the easiest thing would be to do the net install starting with tftp. After all, the polish guy that wrote that article said it was easy. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 09/28/2010 12:39 PM, Mark Misulich wrote:
On Tue, 2010-09-28 at 15:26 -0400, Felix Miata wrote:
On 2010/09/28 14:57 (GMT-0400) Mark Misulich composed:
One of the laptops has no internal cd drive, and won't boot from the external cd drive.
Maybe both are Intel-chipped (most common old laptop chipsets), and you could do a minimal install on this laptop's HD by temporarily installing it in the other after figuring out how to install there.
The other laptop has an internal cd drive, but won't boot from the install dvd. I am not sure why.
The answer is in your own words. :-) If the internal drive were able to read DVDs it would be called a DVD drive, not a CD drive. ;-)
Neither laptop has an operating system installed. Making more cd's won't help, the laptops won't boot from them.
Unusual that an old laptop with a CD drive but lacking a floppy drive cannot be booted from a CD. Not unusual at all that a laptop BIOS must be changed to enable booting from the CD drive in preference to the HD, which is the more typical way to install an OS on such laptops. Assuming the CD drive is not broken if burning http://download.opensuse.org/distribution/11.3/iso/openSUSE-11.3-NET-i586.is... and booting it would not work after a necessary BIOS adjustment and CD drive cleaning I'd be surprised. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409
Felix Miata *** http://fm.no-ip.com/
Hi Felix, thanks for the reply. The drives actually are dvd drives, I should have been more correct in my terminology.
One laptop won't boot from the external drive.
The other won't boot from the 11.1, 2, or 3 install dvd's. It won't boot from Xubuntu 9 or 10 install cd's. It won't boot from EliveCD install cd. Both Xubuntu and EliveCD install cd's are live cd's, perhaps that is why they won't boot from them. It will boot from the PCBSD install DVD, but the graphic's driver is wrong and the screen won't display properly. I don't really want to put that on there anyways, or I would play around with the driver.
I thought the easiest thing would be to do the net install starting with tftp. After all, the polish guy that wrote that article said it was easy.
It actually is easy once you get the hang of setting up PXE. Below I've included part of my PXE default file. It lives in /tftpboot/pxeboot.cfg. /tftpboot/suse/11.3 contains the files linux and initrd taken from http://download.opensuse.org/distribution/11.3/repo/oss/boot/i386/loader/ default install-11.3-32 prompt 1 timeout 3000 # Install 32 bit i386 Linux 11.3 label install-11.3-32 kernel suse/11.3/linux append initrd=suse/11.3/initrd splash=silent vga=0x314 showopts install=http://download.opensuse.org/distribution/11.3/repo/oss good luck! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Felix Miata said the following on 09/28/2010 03:26 PM:
Assuming the CD drive is not broken if burning http://download.opensuse.org/distribution/11.3/iso/openSUSE-11.3-NET-i586.is... and booting it would not work after a necessary BIOS adjustment and CD drive cleaning I'd be surprised.
Which is actualy how I upgraded a 11.2 machine to 11.3 because .. Guess what! The machine would read a CD but not a DVD. Oh wow! -- If you can read this, we wasted 32 billion bucks. -- bumper sticker on stealth bomber -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich wrote:
On Tue, 2010-09-28 at 17:41 +0200, Per Jessen wrote:
Mark Misulich wrote:
Hi, I have been trying to install the os on two computers that won't boot from the install dvd. I have been trying to install using tftp and pxe via lan, but its not working. I think the problem may be that I don't have the dhcp-server set up correctly on this computer, as the client computer isn't getting an ip address when it boots with dhcp.
You should be able to determine that from the /var/log/messages where your dhcp server is running.
Is it possible to help me with setting up the server correctly? I don't know how to do this, really, so you will have to expect some replies that might seem kind of dumb until I learn what to do.
Sure, let us know how far you have gotten.
Hi, I found this message in /var/log/boot.omsg
Setting up (remotefs) network interfaces: Setting up service (remotefs) network . . . . . . . . . .done Starting DHCP server Internet Systems Consortium DHCP Server V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ /var/lib/dhcp///etc/dhcpd.conf line 16: expecting numeric value. subnet 192.168.1.0netmask ^ Configuration file errors encountered -- exiting
Okay, so to start with your dhcp server isn't properly configured. Looks like a blank is missing?
After I installed the dhcp-server program with yast, I also didn't find a file like /etc/dhcp-server/dhcpd.conf. I did find /etc/dhcp.conf, and I pasted a sample configuration into it from the tutorial that I was using. The tutorial didn't go into depth about how to set up the server.
This is a snippet from my dhcp conf which supports machines botting etherboot from floppy, then running pxe: group { filename "pxelinux.0"; next-server io64.local.net; host dell1 { hardware ethernet 00:0f:1f:dd:fc:50; fixed-address 192.168.2.81; } } -- Per Jessen, Zürich (11.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 19:45 +0200, Per Jessen wrote:
Mark Misulich wrote:
On Tue, 2010-09-28 at 17:41 +0200, Per Jessen wrote:
Mark Misulich wrote:
Hi, I have been trying to install the os on two computers that won't boot from the install dvd. I have been trying to install using tftp and pxe via lan, but its not working. I think the problem may be that I don't have the dhcp-server set up correctly on this computer, as the client computer isn't getting an ip address when it boots with dhcp.
You should be able to determine that from the /var/log/messages where your dhcp server is running.
Is it possible to help me with setting up the server correctly? I don't know how to do this, really, so you will have to expect some replies that might seem kind of dumb until I learn what to do.
Sure, let us know how far you have gotten.
Hi, I found this message in /var/log/boot.omsg
Setting up (remotefs) network interfaces: Setting up service (remotefs) network . . . . . . . . . .done Starting DHCP server Internet Systems Consortium DHCP Server V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ /var/lib/dhcp///etc/dhcpd.conf line 16: expecting numeric value. subnet 192.168.1.0netmask ^ Configuration file errors encountered -- exiting
Okay, so to start with your dhcp server isn't properly configured. Looks like a blank is missing?
After I installed the dhcp-server program with yast, I also didn't find a file like /etc/dhcp-server/dhcpd.conf. I did find /etc/dhcp.conf, and I pasted a sample configuration into it from the tutorial that I was using. The tutorial didn't go into depth about how to set up the server.
This is a snippet from my dhcp conf which supports machines botting etherboot from floppy, then running pxe:
group { filename "pxelinux.0"; next-server io64.local.net;
host dell1 { hardware ethernet 00:0f:1f:dd:fc:50; fixed-address 192.168.2.81; } }
-- Per Jessen, Zürich (11.0°C)
I think that the instructions are telling pxelinux.0 to boot then go to the local net. How do I find the address of the local net? Then I think that it is telling it to go to the host server, how do I exactly find the mac and ip addresses for it on the local net? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich wrote:
I think that the instructions are telling pxelinux.0 to boot then go to the local net. How do I find the address of the local net?
Try doing an "arp -n" and see what you get. -- Per Jessen, Zürich (10.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 13:52 -0400, Mark Misulich wrote:
group { filename "pxelinux.0"; next-server io64.local.net;
host dell1 { hardware ethernet 00:0f:1f:dd:fc:50; fixed-address 192.168.2.81; } }
-- Per Jessen, Zürich (11.0°C)
I think that the instructions are telling pxelinux.0 to boot then go to the local net.
No, the next-server directive gives the host name of the server running tftp. That is where the pxelinux.0 file is hosted Per is living on the edge by using .local as a domain, which is really a reserved name for zeroconf and shouldn't be used outside such an environment. Use whatever the hostname of your tftp server is
How do I find the address of the local net?
Then I think that it is telling it to go to the host server, how do I exactly find the mac and ip addresses for it on the local net?
The host directive is a static IP handed out by the dhcp server to the machine with a network card with that ethernet address. It is not the server but the machine being installed Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Johansson wrote:
On Tue, 2010-09-28 at 13:52 -0400, Mark Misulich wrote:
group { filename "pxelinux.0"; next-server io64.local.net;
host dell1 { hardware ethernet 00:0f:1f:dd:fc:50; fixed-address 192.168.2.81; } }
-- Per Jessen, Zürich (11.0°C)
I think that the instructions are telling pxelinux.0 to boot then go to the local net.
No, the next-server directive gives the host name of the server running tftp. That is where the pxelinux.0 file is hosted
Yep.
Per is living on the edge by using .local as a domain, which is really a reserved name for zeroconf and shouldn't be used outside such an environment.
I'm really using "local.net", but only because parts of my setup stem back to the 90s, way before I had any idea what I was doing :-) -- Per Jessen, Zürich (10.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 20:54 +0200, Per Jessen wrote:
Anders Johansson wrote:
On Tue, 2010-09-28 at 13:52 -0400, Mark Misulich wrote:
group { filename "pxelinux.0"; next-server io64.local.net;
host dell1 { hardware ethernet 00:0f:1f:dd:fc:50; fixed-address 192.168.2.81; } }
-- Per Jessen, Zürich (11.0°C)
I think that the instructions are telling pxelinux.0 to boot then go to the local net.
No, the next-server directive gives the host name of the server running tftp. That is where the pxelinux.0 file is hosted
Yep.
Per is living on the edge by using .local as a domain, which is really a reserved name for zeroconf and shouldn't be used outside such an environment.
I'm really using "local.net", but only because parts of my setup stem back to the 90s, way before I had any idea what I was doing :-)
-- Per Jessen, Zürich (10.1°C)
Hi, here are the contents of the /etc/dhcpd.conf file. I don't know for sure that this is the correct file for configuring the server, but I don't see any other likely candidate. So assuming this is the correct one, please reply with how it should be configured after viewing the file contents. # router localization option routers 192.168.0.1; # network mask option subnet-mask 255.255.255.0; # main DNS server to be used option domain-name-servers 194.74.65.68; # set up if our DHCP server is supposed to be the default one in the network authoritative ; # ping allowed ping-check = 1; # important! this is the location of the installation file! filename = "pxelinux.0"; ddns-update-style none; # subnet IP address # accepted IDs in the netmask subnet 192.168.1.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.0.1 192.168.1.254; } -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich wrote:
Hi, here are the contents of the /etc/dhcpd.conf file. I don't know for sure that this is the correct file for configuring the server, but I don't see any other likely candidate. So assuming this is the correct one, please reply with how it should be configured after viewing the file contents.
# router localization option routers 192.168.0.1; # network mask option subnet-mask 255.255.255.0; # main DNS server to be used option domain-name-servers 194.74.65.68;
Do you have access to this? It means having a NAT gateway on 192.168.0.1 (or thereabouts).
# set up if our DHCP server is supposed to be the default one in the network authoritative ; # ping allowed ping-check = 1; # important! this is the location of the installation file! filename = "pxelinux.0";
Okay.
ddns-update-style none; # subnet IP address # accepted IDs in the netmask subnet 192.168.1.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.0.1 192.168.1.254; }
Okay. (I'm not sure about the 'dynamic-bootp' bit). Now, where is your tftp server? -- Per Jessen, Zürich (10.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, 2010-09-28 at 21:10 +0200, Per Jessen wrote:
Mark Misulich wrote:
Hi, here are the contents of the /etc/dhcpd.conf file. I don't know for sure that this is the correct file for configuring the server, but I don't see any other likely candidate. So assuming this is the correct one, please reply with how it should be configured after viewing the file contents.
# router localization option routers 192.168.0.1; # network mask option subnet-mask 255.255.255.0; # main DNS server to be used option domain-name-servers 194.74.65.68;
Do you have access to this? It means having a NAT gateway on 192.168.0.1 (or thereabouts).
I don't know if I do or don't. How do I tell?
# set up if our DHCP server is supposed to be the default one in the network authoritative ; # ping allowed ping-check = 1; # important! this is the location of the installation file! filename = "pxelinux.0";
Okay.
ddns-update-style none; # subnet IP address # accepted IDs in the netmask subnet 192.168.1.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.0.1 192.168.1.254; }
Okay. (I'm not sure about the 'dynamic-bootp' bit).
Now, where is your tftp server?
That is a good question. I looked in yast to see if I could find an address or something for it, but nothing there. Other than that, I made a file /etc/xinetd and filled it with this: service tftp { disable = no socket_type = dgram wait = yes user = root server = /usr/sbin/in.tftpd server_args = -v -s /var/lib/tftpboot only_from = 192.168.1. 127.0.0.1 }
-- Per Jessen, Zürich (10.0°C)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mark Misulich said the following on 09/28/2010 03:18 PM:
service tftp { disable = no socket_type = dgram wait = yes user = root server = /usr/sbin/in.tftpd server_args = -v -s /var/lib/tftpboot
that means chroot to /var/lib/tftpboot so the file "pxelinux.0" should be there. Yes?
only_from = 192.168.1. 127.0.0.1 }
Well there's one problem! You DHCP is handning out ...
subnet 192.168.1.0 netmask 255.255.255.0 { range dynamic-bootp 192.168.0.1 192.168.1.254; }
subnet 192.168.1.0 netmask 255.255.255.0 {
Now that looks odd. Either the "192.168.0.1" is ignoed 'cos of the "subnet 192.168.1.0" or it isn't. If it isn't it means you're handing our addresses in "192.169.0.x" until they are exhausted. So if the PE machine gets "192.168.0.1" the the "only_from" of the TFTP isn't going to repsond. I don't know the code, but I wouldn't go there if I was you. You may also be clashing with your router's address :-! If you're starting at 192.168.0.1 ... isn't that the router's address? Well actually the DHCP server is supposed to check IP addresses to see if they are in use by sending an ICMP Echo request message to that address. It expects an response within a second. You can test this from the command line of your server to see if the router is presonding to ping requests. If I were you I'd use a stanza in the DHCP config like host laptop1 { hardware ethernet AB:CD:EF:12:34:56 ; fixed-address 192.168.1.10 ; } and host laptop1 { hardware ethernet EF:12:AB:12:34:AB ; fixed-address 192.168.1.11 ; } Use symbolic names. This way you can be sure of the address. If you insist on using the form then I'd make sure that the range is ONLY in that subnet. And I'd use the "range" statement KISS subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.1 192.168.1.254; } I'm aware that there are a number of thigns that DHCP servers can do with BOOTP clients, but they are not relevant here. We are not talking about a mixed pool of BOOTP and non-BOOTP clients, we are talking about a PXE installation. I'd suggest a look at http://www.stanford.edu/~alfw/PXE-Kickstart/PXE-Kickstart-4.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anton Aylward wrote:
Mark Misulich said the following on 09/28/2010 03:18 PM:
service tftp { disable = no socket_type = dgram wait = yes user = root server = /usr/sbin/in.tftpd server_args = -v -s /var/lib/tftpboot
that means chroot to /var/lib/tftpboot so the file "pxelinux.0" should be there. Yes?
That's right - as should the per-host files pxelinux.cfg/01-nn-nn-nn-nn-nn-nn (nn-nn-nn-nn-nn-nn being the MAC address of the NIC you're booting from.)
subnet 192.168.1.0 netmask 255.255.255.0 {
If you insist on using the form then I'd make sure that the range is ONLY in that subnet. And I'd use the "range" statement KISS
subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.1 192.168.1.254; }
Yep, looks good. -- Per Jessen, Zürich (10.4°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Per Jessen wrote:
Mark Misulich wrote:
On Tue, 2010-09-28 at 17:41 +0200, Per Jessen wrote:
Mark Misulich wrote:
Hi, I have been trying to install the os on two computers that won't boot from the install dvd. I have been trying to install using tftp and pxe via lan, but its not working. I think the problem may be that I don't have the dhcp-server set up correctly on this computer, as the client computer isn't getting an ip address when it boots with dhcp. You should be able to determine that from the /var/log/messages where your dhcp server is running.
Is it possible to help me with setting up the server correctly? I don't know how to do this, really, so you will have to expect some replies that might seem kind of dumb until I learn what to do. Sure, let us know how far you have gotten. Hi, I found this message in /var/log/boot.omsg
Setting up (remotefs) network interfaces: Setting up service (remotefs) network . . . . . . . . . .done Starting DHCP server Internet Systems Consortium DHCP Server V3.1.1 Copyright 2004-2008 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ /var/lib/dhcp///etc/dhcpd.conf line 16: expecting numeric value. subnet 192.168.1.0netmask ^ Configuration file errors encountered -- exiting
Okay, so to start with your dhcp server isn't properly configured. Looks like a blank is missing?
After I installed the dhcp-server program with yast, I also didn't find a file like /etc/dhcp-server/dhcpd.conf. I did find /etc/dhcp.conf, and I pasted a sample configuration into it from the tutorial that I was using. The tutorial didn't go into depth about how to set up the server.
This is a snippet from my dhcp conf which supports machines botting etherboot from floppy, then running pxe:
group { filename "pxelinux.0"; next-server io64.local.net;
host dell1 { hardware ethernet 00:0f:1f:dd:fc:50; fixed-address 192.168.2.81; } }
Hmm... not sure a dhcp server is a requirement. I do not run one and have installed succesfully using PXE in past... IIRC The PXE client client broadcasts a packet that contains the client MAC address... a PXE server then responds with the location of a boot image appropriate for the client associated with the MAC address which is downloaded and control is passed to that image (PXE is a more advanced version of BOOTP). There is a good reference on the SuSE site about installing via PXE (cannot remember link at moment). Thought there was a gotcha in the TFTP configuration... But of course to work, PXE support is required (usually in hardware, though I vaguely remember a reference to a software solution). No PXE support then forget it.... - -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkyjBosACgkQasN0sSnLmgKnNgCg+HMzXbN7NTS4H9QgFvwtq5kN 27wAoKlpdMQYc1DJ2HwW/XsRsq8YpJ8v =otzT -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
Hmm... not sure a dhcp server is a requirement. I do not run one and have installed succesfully using PXE in past...
IIRC The PXE client client broadcasts a packet that contains the client MAC address... a PXE server then responds with the location of
I suspect PXE Server = DHCP + TFTP.
a boot image appropriate for the client associated with the MAC address which is downloaded and control is passed to that image (PXE is a more advanced version of BOOTP).
I think that should have been "PXE uses BOOTP or DHCP"? -- Per Jessen, Zürich (12.1°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Per Jessen wrote:
G T Smith wrote:
Hmm... not sure a dhcp server is a requirement. I do not run one and have installed succesfully using PXE in past...
IIRC The PXE client client broadcasts a packet that contains the client MAC address... a PXE server then responds with the location of
I suspect PXE Server = DHCP + TFTP.
On checking, I found the original pages I used have been deleted from the SuSE site... IIRC the protocol originally was very low level, usually at network card MAC/Arp addressing (and normally non-routable as a consequence). Therefore, a properly configured PXE server config *is* required but a properly configured dhcp server is not (just a bit more useful in more complex environments). However, because DHCP now can handle PXE requests correctly it seems somebody has decided to enforce a requirement that a DHCP server be installed (argh !!! ). Red Hat have followed a similar path. (I am not sure how this approach is supposed to help the less technically literate with this need). As I do not personally wish to run a DHCP server, I have to find an alternative to SuSE's current approach in my next upgrade, A PXELinux/SYSLinux config seems the most promising at moment.
a boot image appropriate for the client associated with the MAC address which is downloaded and control is passed to that image (PXE is a more advanced version of BOOTP).
I think that should have been "PXE uses BOOTP or DHCP"?
BOOTP when I first came across it, worked for both IPX networks with and without TCP/IP support, the primary issue was that the boot image had to very small by today's standards. PXE servers can serve up boot options and download much larger boot images than many BOOTP servers were capable of. (IPX does not normally have the equivalent of DHCP servers as it does not need it). So I stand by original comment.
- -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkyjLdwACgkQasN0sSnLmgI6WQCgoynOfF8sPNXBhA7naVkF7SiJ GoQAoLhREWW3Mrt8LsQ7bgDgU7WyZGQ5 =SFGP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
IIRC the protocol originally was very low level, usually at network card MAC/Arp addressing (and normally non-routable as a consequence). Therefore, a properly configured PXE server config *is* required
Well, in my setup I have no such PXE server, has worked fine without it for a good few years. I have DHCP and TFTP though.
However, because DHCP now can handle PXE requests correctly it seems somebody has decided to enforce a requirement that a DHCP server be installed (argh !!! ). Red Hat have followed a similar path. (I am not sure how this approach is supposed to help the less technically literate with this need).
It's not really that new - my old cluster was built around 2002. It did PXE boot from floppy, got IP+filename+nextserver from DHCP and that was it.
As I do not personally wish to run a DHCP server, I have to find an alternative to SuSE's current approach in my next upgrade, A PXELinux/SYSLinux config seems the most promising at moment.
That's what I use - PXElinux.
a boot image appropriate for the client associated with the MAC address which is downloaded and control is passed to that image (PXE is a more advanced version of BOOTP).
I think that should have been "PXE uses BOOTP or DHCP"?
BOOTP when I first came across it, worked for both IPX networks with and without TCP/IP support, the primary issue was that the boot image had to very small by today's standards. PXE servers can serve up boot options and download much larger boot images than many BOOTP servers were capable of. (IPX does not normally have the equivalent of DHCP servers as it does not need it). So I stand by original comment.
AFAICT (by googling), a PXE server is exactly what I proposed, i.e. a DHCP+TFTP server. I haven't found any downloadable "PXE server" package, only instructions for setting one up - which invariably includes setting up DHCP and TFTP etc. PXE is a software environment (by Intel IIRC) on the client, not a protocol. -- Per Jessen, Zürich (14.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Per Jessen wrote:
G T Smith wrote:
IIRC the protocol originally was very low level, usually at network card MAC/Arp addressing (and normally non-routable as a consequence). Therefore, a properly configured PXE server config *is* required
Well, in my setup I have no such PXE server, has worked fine without it for a good few years. I have DHCP and TFTP though.
The PXELinux config does have the capability of loading a remote image without the need for a dhcp server. A static temporary TCP/IP address may be used for image transfer. See PXELinux documentation at... http://syslinux.zytor.com/wiki/index.php/PXELINUX As I stated before I have used PXE in an environment with no dhcp server with just a default directory defined with no problems.
That's what I use - PXElinux.
I think that should have been "PXE uses BOOTP or DHCP"?
AFAICT (by googling), a PXE server is exactly what I proposed, i.e. a DHCP+TFTP server. I haven't found any downloadable "PXE server" package, only instructions for setting one up - which invariably includes setting up DHCP and TFTP etc. PXE is a software environment (by Intel IIRC) on the client, not a protocol.
Which is not quite "PXE uses BOOTP or DHCP" !
- -- ============================================================================== I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone. Bjarne Stroustrup ============================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkyjOekACgkQasN0sSnLmgKw2gCgsWoujLLQ/gxXuUsDvU0pL7LJ NS4AoIhKJ+NQtN28A/PFHjP7VQyFHyzk =dw7A -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
G T Smith wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Per Jessen wrote:
G T Smith wrote:
IIRC the protocol originally was very low level, usually at network card MAC/Arp addressing (and normally non-routable as a consequence). Therefore, a properly configured PXE server config *is* required
Well, in my setup I have no such PXE server, has worked fine without it for a good few years. I have DHCP and TFTP though.
The PXELinux config does have the capability of loading a remote image without the need for a dhcp server. A static temporary TCP/IP address may be used for image transfer. See PXELinux documentation at...
Okay, I guess it is possible to use a static/temporary IP address, and specify/hardcode the tftp-server and the filename to load. I can't get my HP workstation to do that though - when I boot in PXE, the first thing it looks is a DHCP response. -- Per Jessen, Zürich (15.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Per Jessen wrote:
G T Smith wrote:
IIRC the protocol originally was very low level, usually at network card MAC/Arp addressing (and normally non-routable as a consequence). Therefore, a properly configured PXE server config *is* required
Well, in my setup I have no such PXE server, has worked fine without it for a good few years. I have DHCP and TFTP though.
The PXELinux config does have the capability of loading a remote image without the need for a dhcp server. A static temporary TCP/IP address may be used for image transfer. See PXELinux documentation at...
http://syslinux.zytor.com/wiki/index.php/PXELINUX
As I stated before I have used PXE in an environment with no dhcp server with just a default directory defined with no problems.
That's what I use - PXElinux.
I think that should have been "PXE uses BOOTP or DHCP"?
AFAICT (by googling), a PXE server is exactly what I proposed, i.e. a DHCP+TFTP server. I haven't found any downloadable "PXE server" package, only instructions for setting one up - which invariably includes setting up DHCP and TFTP etc. PXE is a software environment (by Intel IIRC) on the client, not a protocol.
Hi, I couldn't get the dhcp server to work yesterday evening after going
On Wed, 2010-09-29 at 14:06 +0100, G T Smith wrote: through the instructions given on the mail list. I did some more google searching and found that I could make a boot floppy for Xubunu that allowed me to install a boot manager. From that boot manager, I could select "boot from cdrom," which I did and was able to install from the dvd drive. That worked for one of the two laptops. The other laptop has an external dvd drive, and even the simple boot manager loaded from floppy disk doesn't recognize it. So I can't boot from the dvd on that computer. I plan on working on the tftp/dhcp boot again on that computer later today when I have some free time. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Per Jessen said the following on 09/29/2010 08:34 AM:
AFAICT (by googling), a PXE server is exactly what I proposed, i.e. a DHCP+TFTP server. I haven't found any downloadable "PXE server" package, only instructions for setting one up - which invariably includes setting up DHCP and TFTP etc. PXE is a software environment (by Intel IIRC) on the client, not a protocol.
Yup... Now I have been experimenting with Linux-on-a-stick. Its not hard to have a grub on a USB boot sector that does a foldback mount of the ISO image .... menuentry "Run Ubuntu Live 9.10" { loopback loop /ubuntu-9.10-desktop-i386.iso linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=/ubuntu-9.10-desktop-i386.iso splash -- initrd (loop)/casper/initrd.lz } And one or each and every ISO image you have on the USB stick. Of course you _also_ have a few local directories like /home an some config files that overwrite the ones on the ISO ... unless you custom build your ISOs. Now I have an old, old laptop that won't boot from USB. It will boot from the LAN - PXE. Is there a file to to tell it to boot via PXE from the USB? -- "Good judgement comes from experience, and experience -- well, that comes from poor judgement." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2010/09/28 11:22 (GMT-0400) Mark Misulich composed:
I have been trying to install the os on two computers that won't boot from the install dvd.
Will they boot anything whatsoever? If so, maybe you can install as I _normally_ install, using only existing installed Grub and the openSUSE installation linux and initrd. On a virgin system with nothing already installed, I partition first; then using Knoppix mkfs.ext2 some primary partition, install Grub and the openSUSE linux & initrd; then install openSUSE via Grub using HTTP and fixed IP as spelled out in http://en.opensuse.org/SDB:Remote_installation and http://old-en.opensuse.org/Linuxrc . -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Anders Johansson -
Anton Aylward -
Bruce Ferrell -
DenverD -
Felix Miata -
G T Smith -
Mark Misulich -
Per Jessen