Re: Problem for deployment to Target from Linux OS image (generate by Qplus)
Jerry Epplin <[email protected]> Mon, 24 Mar 2003 08:45:29 -0600
| Newsgroups | gmane.linux.qplus.devel |
|---|---|
| Message-ID | <[email protected]> |
It sounds like your kernel is configured with the wrong cpu type. You didn't mention your target hardware, but if, for example, you have a pentium, and you didn't change the processor from the default (P3, IIRC) this type of behavior is typical. To fix this, don't just change the processor type and rebuild -- you have to rebuild the kernel completely. Copying to qplus-devel, in case Heechul has anything else to add ... Jerry Kevin Yang wrote: >Hi Jerry, > >I have a problem for deploying Linux OS image (generated by Qplus) to Target >Machine. > >First, we run Qplus (Verson 1.2) on Redhat 7.1 and got the Linux OS image. >We followed the document from the link in your article and print out the >"Qplus-P Target Builder User's Guide" > >We have completed the following process according the menu. > >1. Chapter 1 to 2 (Build the OS Image and geterate the OS Image) > >2. For Chapter 3 "Deployment to Target (i386/Generic)" > We do the following: > a. 3.1 Check the Host Requirement -- Ok > b. 3.2 Making Etherboot boot floppy disk > -- we got the .lzdsk file from http://rom-o-matic.org the latest >version. > -- we successfully build the Bootup disk through the following >command > $ cat eb-5.0.14-rtl8139.lzdsk > /dev/fd0 > c. 3.4 Host system configuration for Etherboot > -- we configure the DHCPD > -- we modify /det/dhcpd.conf file as shown in the example of >document > -- we also gave command '/etc/ini.d/dhcpd restart' > then > -- we modify disable record in /etc/xinetd/tftp file to no and >issued the command > '/etc/initd/xinetd restart > >3. We basically followed the 3.7 Installing to the hard disk of target >system on the menu > a. select install to target system's option > b. Execute Build all in the menu > c. Execute Deploy Taget Image in the menu. > d. Check the files we create ----- No problem. > (/tftpboot/qplusp.etherboot.......) > e. Finally we boot the tagert system. > -- Target system has a floppy drive which contain the boot disk and >a > Hard Drive as the target place to store OS image, file >system.......... > After we have done the above and boot the target system > > The following is what we got > -- target system boot, connect to the host, download something from >host (this is what we think) > the target show the following message and immeidately reboot again >and again: > > Verifying DMA Pool Data........ > .000021.000 done > ROM Segment 0x0800 length 0x4000 reloc 0x00020000 > Etherboot 5.1.7 (GPL) Tagged ELF for [RTL8139] > Relocating _text from:[00023920, 000341f0) to [07ddf730, 07df0000) > Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? > Probing pic nic ... > Searching for server (DHCP)... > Me: 192.168.10.237, Server: 192.168.10.185 > Loading 192.168.10.185:qplus.etherboot XXXX(1549/...) > > Unfortunately, we though the Hard Drive should contain boot inform and >can continue get > OS image and file system from host. It is not. > > One thing we missed from the menu is that we can not find the file ended >with .lzdsk inside folder"<projdir>/tools/etherbooimgs" > which stated in the chapter 3.2 "Making Etherboot boot floppy disk". So >we got the boot image from http://rom-o-matic.org > > Another thing is that we are not sure if the Hard Drive on target >machine should format or not before the downloading process? > > So can you give us some advise or correction for what is going wrong on >our process? > Or you have any suggestion or soultion to us. > > Your help will be highly appreciated! > > Thank you very much and have a nice day! > > > Sincerely Yous > > Kevin > Embedded System Engineering Group, > CIVON CORP. > > email: [email protected] > tel: +886-2-8732-5035 ext. 108 > > > > > > > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf