etherboot-developers Mailing List for Etherboot (Page 228)
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-developers — Discussion of developer issues
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(3) |
Oct
(10) |
Nov
(47) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(41) |
Feb
(107) |
Mar
(76) |
Apr
(103) |
May
(66) |
Jun
(72) |
Jul
(27) |
Aug
(31) |
Sep
(33) |
Oct
(18) |
Nov
(33) |
Dec
(67) |
| 2002 |
Jan
(25) |
Feb
(62) |
Mar
(79) |
Apr
(74) |
May
(67) |
Jun
(104) |
Jul
(155) |
Aug
(234) |
Sep
(87) |
Oct
(93) |
Nov
(54) |
Dec
(114) |
| 2003 |
Jan
(146) |
Feb
(104) |
Mar
(117) |
Apr
(189) |
May
(96) |
Jun
(40) |
Jul
(133) |
Aug
(136) |
Sep
(113) |
Oct
(142) |
Nov
(99) |
Dec
(185) |
| 2004 |
Jan
(233) |
Feb
(151) |
Mar
(109) |
Apr
(96) |
May
(200) |
Jun
(175) |
Jul
(162) |
Aug
(118) |
Sep
(107) |
Oct
(77) |
Nov
(121) |
Dec
(114) |
| 2005 |
Jan
(201) |
Feb
(271) |
Mar
(113) |
Apr
(119) |
May
(69) |
Jun
(46) |
Jul
(21) |
Aug
(37) |
Sep
(13) |
Oct
(4) |
Nov
(19) |
Dec
(46) |
| 2006 |
Jan
(10) |
Feb
(18) |
Mar
(85) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(10) |
Jul
(20) |
Aug
(9) |
Sep
(11) |
Oct
(4) |
Nov
(1) |
Dec
(40) |
| 2008 |
Jan
(19) |
Feb
(8) |
Mar
(37) |
Apr
(28) |
May
(38) |
Jun
(63) |
Jul
(31) |
Aug
(22) |
Sep
(37) |
Oct
(38) |
Nov
(49) |
Dec
(24) |
| 2009 |
Jan
(48) |
Feb
(51) |
Mar
(80) |
Apr
(55) |
May
(34) |
Jun
(57) |
Jul
(20) |
Aug
(83) |
Sep
(17) |
Oct
(81) |
Nov
(53) |
Dec
(40) |
| 2010 |
Jan
(55) |
Feb
(28) |
Mar
(36) |
Apr
(7) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
(10) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ebi...@ln...> - 2002-10-23 00:45:11
|
Ronald G Minnich <rmi...@la...> writes: > This is with fallback and normal LinuxBIOS images on E7500 mainboards. > They're loaded with the identical etherboot image, 5.1.2rc4.eb5. > > On fallback, etherboot goes right to the IDE disk after finding no good > ethernet link: [snip] > On normal, etherboot just loops forever until I tell it to go to disk: [snip] It is a bug. And it is fixed in the etherboot source tree. Ron for your cluster I just need to make a new build of LinuxBIOS and put the new etherboot in there. The boot order code was just broken, and I don't know how it lasted as long as it did. Ron can you check to see what your boot order is. As I recall it only happened with boot_first=Network boot_second=Network boot_third=Network In which case there is a work around available. I need to track this down before we start building up Pink. > I'm guessing I'm not the first person who will hit this, hence this > message to various lists. The code was fixed a little while ago, when I completed the e1000 support. As the bug also it prevented fail over from one nic to another. Eric |
|
From: Ronald G M. <rmi...@la...> - 2002-10-23 00:01:33
|
This is with fallback and normal LinuxBIOS images on E7500 mainboards. They're loaded with the identical etherboot image, 5.1.2rc4.eb5. On fallback, etherboot goes right to the IDE disk after finding no good ethernet link: Etherboot 5.1.2rc4.eb5 (GPL) ELF64 ELF (Multiboot) for [EEPRO100][IDE] Relocating _text from: [00024524,00034674) to [7ffefeb0,80000000) CPU 2469 Mhz Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? Probing pci...Found EEPRO100 ROM address 0x0000 [EEPRO100]The PCI BIOS has not enabled this device! Updating PCI command 0003->0007. pci_bus 04 pci_device_fn 10 Ethernet addr: 00:30:48:23:B8:2D Valid link not established Probing isa... Probing pci...Found IDE ROM address 0x0000 [IDE]The PCI BIOS has not enabled this device! Updating PCI command 0003->0007. pci_bus 00 pci_device_fn F9 PCI latency timer (CFLT) is unreasonably low at 0. Setting to 32 clocks. disk-1 16000k cap: 0200 Searching for image... ................................(ELF)... Loading image. On normal, etherboot just loops forever until I tell it to go to disk: Etherboot 5.1.2rc4.eb5 (GPL) ELF64 ELF (Multiboot) for [EEPRO100][IDE] Relocating _text from: [00024524,00034674) to [7ffefeb0,80000000) CPU 2470 Mhz Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? Probing pci...Found EEPRO100 ROM address 0x0000 [EEPRO100]The PCI BIOS has not enabled this device! Updating PCI command 0003->0007. pci_bus 04 pci_device_fn 10 Ethernet addr: 00:30:48:23:AD:1B Valid link not established Probing isa... No adapter found <sleep> Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? Note there is no 'probing pci' step. If I hit 'D' for disk it does probe pci: Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? D Probing pci...Found IDE ROM address 0x0000 [IDE]The PCI BIOS has not enabled this device! I'm curious if this is correct behaviour (in which case I need to change it) or some unintended consequence of a variable setting (CMOS)? Why would etherboot probe or not probe PCI? Why would telling it to load from disk cause it to then probe PCI? I'm guessing I'm not the first person who will hit this, hence this message to various lists. Thanks ron |
|
From: Doug A. <amb...@am...> - 2002-10-22 15:17:46
|
ke...@us... writes: | I have updated the tarball with Michael Brown's latest changes and it's | available from: | | http://www.etherboot.org/etherboot-5.1.2rc7.tar.bz2 | | I have tested it with a 3c509 and the following work: | | + mkelf-nfl image | + mkelf-linux image | + mknbi-fdos image | + mknbi-rom image (booting itself again, works repeatedly) | | It would be appreciated if people would test: | | Other NICs | mknbi-linux with and without --first32pm | -DRELOCATION | Other options | NFS booting | anything else you normally use | | and post here. | | You *need* mknbi-1.2-10 to make the images. mknbi-1.2-10 will appear at | the site as soon as the release system shows the files I have uploaded; | it seems to be taking a weekend holiday. I haven't tried to boot FreeBSD for a while. I needed to make some minor changes due to re-structure and a typo. I also added some Intel 10/100pro Id's. We should probably just match on anything matching 103X. I also haven't tried the external menu. I used the internal menu a lot and can't get the external menu to work or any older netboot images like nbgrub or netboot versions of tagged DOS images. Results from the netboot dos image. Probing pci nic... [E1000]Ethernet addr: 00:E0:81:50:15:F7 Searching for server (DHCP)... ..Me: 192.168.99.192, Server: 192.168.99.254, Gateway 192.168.99.254 Loading 192.168.99.254:/tftpboot/menu ..(NBI)........................... [ lots of dots deleted ] .....................................................Unable to load file. <sleep> <abort> [E1000]Ethernet addr: 00:E0:81:50:15:F7 Results from the nbgrub image. Searching for server (DHCP)... ..Me: 192.168.99.192, Server: 192.168.99.254, Gateway 192.168.99.254 Loading 192.168.99.254:/tftpboot/menu ..(NBI)segment [00010200, 0002E48C) overlaps etherboot [00020000, 000308D0) error: not a valid image Unable to load file. <sleep> I had similar trouble with the external menu. Actually I wasn't sure how to even create an external menu that functioned the same as the internal menu. I tried mknbi-1.2-10 but anything I did resulted in it not working. It might be usefull to show exactly how to create an external menu that is compatible to the old system. Either that or I'm just to dumb to figure it out. Anyhow here are the patches that boot FreeBSD image and build and FreeBSD. diff -r -u etherboot-5.1.2rc7.orig/src/eepro100.c etherboot-5.1.2rc7/src/eepro100.c --- etherboot-5.1.2rc7.orig/src/eepro100.c Tue Oct 15 05:56:37 2002 +++ etherboot-5.1.2rc7/src/eepro100.c Mon Oct 21 10:39:36 2002 @@ -669,6 +671,10 @@ { PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ID1029, "Intel EtherExpressPro100 ID1029" }, { PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ID1030, + "Intel Corporation 82559 InBusiness 10/100" }, + { PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ID1039, + "Intel Corporation 82559 InBusiness 10/100" }, + { PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_ID103A, "Intel Corporation 82559 InBusiness 10/100" }, { PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82562, "Intel EtherExpressPro100 82562EM" }, diff -r -u etherboot-5.1.2rc7.orig/src/etherboot.h etherboot-5.1.2rc7/src/etherboot.h --- etherboot-5.1.2rc7.orig/src/etherboot.h Tue Oct 15 05:56:37 2002 +++ etherboot-5.1.2rc7/src/etherboot.h Mon Oct 21 09:01:42 2002 @@ -720,7 +720,8 @@ extern unsigned char *end_of_rfc1533; #ifdef IMAGE_FREEBSD extern int freebsd_howto; -extern char freebsd_kernel_env[]; +#define FREEBSD_KERNEL_ENV_SIZE 256 +extern char freebsd_kernel_env[FREEBSD_KERNEL_ENV_SIZE]; #endif /* bootmenu.c */ diff -r -u etherboot-5.1.2rc7.orig/src/main.c etherboot-5.1.2rc7/src/main.c --- etherboot-5.1.2rc7.orig/src/main.c Tue Oct 15 05:56:37 2002 +++ etherboot-5.1.2rc7/src/main.c Mon Oct 21 09:02:20 2002 @@ -30,7 +30,7 @@ #ifdef IMAGE_FREEBSD int freebsd_howto = 0; -char freebsd_kernel_env[256]; +char freebsd_kernel_env[FREEBSD_KERNEL_ENV_SIZE]; #endif #ifdef FREEBSD_PXEEMU diff -r -u etherboot-5.1.2rc7.orig/src/nrv2b.c etherboot-5.1.2rc7/src/nrv2b.c --- etherboot-5.1.2rc7.orig/src/nrv2b.c Wed Aug 21 13:00:14 2002 +++ etherboot-5.1.2rc7/src/nrv2b.c Mon Oct 21 09:05:20 2002 @@ -36,7 +36,11 @@ #include <string.h> #include <ctype.h> #include <errno.h> +#ifdef __FreeBSD__ +#include <inttypes.h> +#else #include <stdint.h> +#endif #include <limits.h> #include <assert.h> #if UCLPACK_COMPAT diff -r -u etherboot-5.1.2rc7.orig/src/osloader.c etherboot-5.1.2rc7/src/osloader.c --- etherboot-5.1.2rc7.orig/src/osloader.c Tue Oct 15 05:56:37 2002 +++ etherboot-5.1.2rc7/src/osloader.c Mon Oct 21 12:46:24 2002 @@ -1390,7 +1390,7 @@ freebsd_howto |= 0x80000000; } - xstart32(entry, freebsd_hofwto, NODEV, 0, 0, 0, + xstart32(entry, freebsd_howto, NODEV, 0, 0, 0, virt_to_phys(&info.bsdinfo), 0, 0, 0); longjmp(restart_etherboot, -2); } diff -r -u etherboot-5.1.2rc7.orig/src/pci_ids.h etherboot-5.1.2rc7/src/pci_ids.h --- etherboot-5.1.2rc7.orig/src/pci_ids.h Tue Oct 15 05:56:37 2002 +++ etherboot-5.1.2rc7/src/pci_ids.h Mon Oct 21 09:26:14 2002 @@ -1620,6 +1620,8 @@ #define PCI_DEVICE_ID_INTEL_ID1029 0x1029 #define PCI_DEVICE_ID_INTEL_ID1030 0x1030 #define PCI_DEVICE_ID_INTEL_ID1038 0x1038 +#define PCI_DEVICE_ID_INTEL_ID1039 0x1039 +#define PCI_DEVICE_ID_INTEL_ID103A 0x103A #define PCI_DEVICE_ID_INTEL_82562ET 0x1031 #define PCI_DEVICE_ID_INTEL_82559ER 0x1209 #define PCI_DEVICE_ID_INTEL_82092AA_0 0x1221 |
|
From: <ke...@us...> - 2002-10-22 15:02:01
|
Eric, good to see your ELF format kernel build is a candidate for the next stable series of Linux. http://www.linuxandmain.com/modules.php?name=News&file=article&sid=258 |
|
From: <ebi...@ln...> - 2002-10-22 03:08:36
|
ke...@us... writes: > I have updated the tarball with Michael Brown's latest changes and it's > available from: > > http://www.etherboot.org/etherboot-5.1.2rc7.tar.bz2 > > I have tested it with a 3c509 and the following work: > > + mkelf-nfl image > + mkelf-linux image > + mknbi-fdos image > + mknbi-rom image (booting itself again, works repeatedly) Another fun test, and a little more stressful, is you can do: make xxx.{lz|nrv2b}elf And build an elf bootable etherboot image, that will also boot itself repeatedly. But there is no actuall rom header involved. The nrv2b is the suffix for images compressed with the compressor from upx. It does slightly better then the lz compressor, and it allows unlimited rom sizes. Another fun target is etherboot.rom which compiles in all of the etherboot drivers. > It would be appreciated if people would test: > > Other NICs > mknbi-linux with and without --first32pm > -DRELOCATION > Other options > NFS booting > anything else you normally use > > and post here. > Eric |
|
From: <ebi...@ln...> - 2002-10-21 23:38:36
|
ke...@us... writes: > I have updated the tarball with Michael Brown's latest changes and it's > available from: > > http://www.etherboot.org/etherboot-5.1.2rc7.tar.bz2 > > I have tested it with a 3c509 and the following work: > > + mkelf-nfl image > + mkelf-linux image > + mknbi-fdos image > + mknbi-rom image (booting itself again, works repeatedly) > > It would be appreciated if people would test: > > Other NICs > mknbi-linux with and without --first32pm > -DRELOCATION > Other options > NFS booting > anything else you normally use > > and post here. > > You *need* mknbi-1.2-10 to make the images. mknbi-1.2-10 will appear at > the site as soon as the release system shows the files I have uploaded; > it seems to be taking a weekend holiday. Testing multicast would be nice as well. Anyway more to come, it looks like multi archecture ports are quickly moving up in my priorities... Eric |
|
From: Chrissy <ada...@rn...> - 2002-10-21 21:19:50
|
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1= "> <meta name=3DProgId content=3DWord.Document> <meta name=3DGenerator content=3D"Microsoft Word 9"> <meta name=3DOriginator content=3D"Microsoft Word 9"> <link rel=3DFile-List href=3D"./mort-ad-2-20_files/filelist.xml"> <title>Untitled Document</title> <!--[if gte mso 9]><xml> <o:DocumentProperties> <o:Author>Paul W</o:Author> <o:Template>Normal</o:Template> <o:LastAuthor>Paul W</o:LastAuthor> <o:Revision>2</o:Revision> <o:TotalTime>20</o:TotalTime> <o:Created>2002-10-08T23:53:00Z</o:Created> <o:LastSaved>2002-10-08T23:53:00Z</o:LastSaved> <o:Pages>1</o:Pages> <o:Words>83</o:Words> <o:Characters>475</o:Characters> <o:Company>cc</o:Company> <o:Lines>3</o:Lines> <o:Paragraphs>1</o:Paragraphs> <o:CharactersWithSpaces>583</o:CharactersWithSpaces> <o:Version>9.2720</o:Version> </o:DocumentProperties> </xml><![endif]--> <style> <!-- /* Font Definitions */ @font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:536871559 0 0 0 415 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:blue; text-decoration:underline; text-underline:single;} p {margin-right:0in; mso-margin-top-alt:auto; mso-margin-bottom-alt:auto; margin-left:0in; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1027"/> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1"/> </o:shapelayout></xml><![endif]--> </head> <body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dblue style=3D'tab-i= nterval:.5in'> <div class=3DSection1> <div align=3Dcenter> <table border=3D0 cellpadding=3D0 width=3D"54%" style=3D'width:54.0%;mso-c= ellspacing: 1.5pt;border:outset #666666 1.5pt;mso-padding-alt:1.5pt 1.5pt 1.5pt 1.5pt= ' height=3D469> <tr style=3D'height:320.25pt'> <td valign=3Dtop style=3D'border:inset #666666 .75pt;padding:1.5pt 1.5pt= 1.5pt 1.5pt; height:320.25pt'> <table border=3D1 cellspacing=3D0 cellpadding=3D0 width=3D"100%" bgcolor= =3D"#000099" style=3D'width:100.0%;mso-cellspacing:0in;background:#000099;border:non= e; mso-padding-alt:3.0pt 3.0pt 3.0pt 3.0pt' height=3D11> <tr> <td style=3D'border:none;padding:3.0pt 3.0pt 3.0pt 3.0pt'> <p class=3DMsoNormal> </p> </td> </tr> </table> <p class=3DMsoNormal><span style=3D'display:none;mso-hide:all'><![if !su= pportEmptyParas]> <![endif]><o:p></o:p></span></p> <table border=3D1 cellspacing=3D0 cellpadding=3D0 width=3D"100%" bgcolor= =3D"#ffffcc" style=3D'width:100.0%;mso-cellspacing:0in;background:#FFFFCC;border:non= e; mso-padding-alt:3.0pt 3.0pt 3.0pt 3.0pt' height=3D8> <tr> <td style=3D'border:none;padding:3.0pt 3.0pt 3.0pt 3.0pt'> <p class=3DMsoNormal> </p> </td> </tr> </table> <h1 align=3Dcenter style=3D'text-align:center'><span style=3D'color:blue= '>Abosolute Mortgage Tool<o:p></o:p></span></h1> <h1 align=3Dcenter style=3D'text-align:center'><span style=3D'font-size:= 12.0pt; font-family:Arial;color:#333399'>- What are you waiting for -</span><spa= n style=3D'font-size:18.0pt;font-family:Arial;color:#CC0000'><br> </span><span style=3D'font-size:12.0pt;font-family:Arial;color:#CC0000'>= Interest Rates are the LOWEST they've been in 15 years!</span><u><span style=3D'font-size:12.0pt;font-family:Arial;color:#3333CC'><br> </span></u><u><span style=3D'font-size:12.0pt;font-family:Arial;color:bl= ue'><a href=3D"http://host.genebusinessmaster.com/mort01"><br> - Shop 100's of Lenders with just ONE CLICK -</a></span></u></h1> <h1 align=3Dcenter style=3D'text-align:center'><span style=3D'font-size:= 12.0pt; font-family:Arial;color:#333399'>Good Credit / Bad Credit / So-So Credit= <br> We have Special Programs for every type of credit history</span><span style=3D'font-size:7.5pt;font-family:Arial;color:#0000CC'><br> <br> </span><span style=3D'font-size:12.0pt;font-family:Arial;color:#CC0000'>= No Upfront Fees - No Hidden Fees - Approval in Minutes<br> <br> </span><span style=3D'font-size:12.0pt;font-family:Arial;color:#333399'>= - Get the CASH you need FAST -</span></h1> <p align=3Dcenter style=3D'text-align:center'><b><span style=3D'font-fam= ily:Arial; color:#333399'>It's easy to qualify and your loan review is FREE</span><= /b></p> <p align=3Dcenter style=3D'text-align:center'><b><span style=3D'font-fam= ily:Arial; color:#3333CC'> <a href=3D"http://host.genebusinessmaster.com/mort0= 1">Click Here</a></span></b><b><span style=3D'font-family:Verdana;mso-bidi-font-f= amily: Arial;color:#3333CC'> </span></b><b><span style=3D'font-family:Arial; color:#333399'>to learn more.</span></b><b><span style=3D'font-family:Ar= ial; color:#CC0000'> There is NO obligation</span></b><o:p></o:p></p> <table border=3D1 cellspacing=3D0 cellpadding=3D0 width=3D"100%" bgcolor= =3D"#ffffcc" style=3D'width:100.0%;mso-cellspacing:0in;background:#FFFFCC;border:non= e; mso-padding-alt:3.0pt 3.0pt 3.0pt 3.0pt' height=3D8> <tr> <td style=3D'border:none;padding:3.0pt 3.0pt 3.0pt 3.0pt'> <p class=3DMsoNormal> </p> </td> </tr> </table> <p class=3DMsoNormal><span style=3D'display:none;mso-hide:all'><![if !su= pportEmptyParas]> <![endif]><o:p></o:p></span></p> <table border=3D1 cellspacing=3D0 cellpadding=3D0 width=3D"100%" bgcolor= =3D"#000099" style=3D'width:100.0%;mso-cellspacing:0in;background:#000099;border:non= e; mso-padding-alt:3.0pt 3.0pt 3.0pt 3.0pt' height=3D8> <tr> <td style=3D'border:none;padding:3.0pt 3.0pt 3.0pt 3.0pt'> <p class=3DMsoNormal> </p> </td> </tr> </table> <p class=3DMsoNormal><o:p></o:p></p> </td> </tr> </table> </div> <p> </p> <p><![if !supportEmptyParas]> <![endif]><o:p></o:p></p> <p> </p> </div> </body> </html> |
|
From: Adam H. <woo...@te...> - 2002-10-21 20:58:52
|
HOW TO 'PICK UP' BEAUTIFUL WOMEN by John Eagan, THE BOOK THAT IS GETTING NOTICED! PENTHOUSE MAGAZINE promoted the author, John Eagan, as a "Miracle Worker." Penthouse Magazine's July '99 cover says "Getting Beautiful Girls - Self Styled Pick Up Guru Shares His 'Super Techniques.'" According to Penthouse Magazine, John Eagan had to take out an individual named "Bill." Penthouse described it as follows -(page 132) "John's got his work cut out for him with Bill who is in his 40's, balding, wears glasses and sports an ill advised goatee." Yet Penthouse goes on to say that Bill, using John Eagan's techniques, (page 133) "obtained 3 women's phone numbers that night." On November 20th '99, John Eagan - author of the book "How To Pick Up Beautiful Women" - appeared as a guest on the Howard Stern Radio Show, CBS TV. According to Howard Stern, John Eagan was asked to go out with the E! crew and their hidden cameras to get dates for some of their interns. Howard said the interns were the ugliest guys he could find. John Eagan had to coach the interns with his techniques by speaking into the interns ear pieces. Using John Eagan's techniques, these interns got dates with beautiful girls. Howard said "This guy is no bull, I've seen him in action. He's the real deal." Call for information call: 1-800-4-SECRET OR to receive more info by email click on link below. Mailto:jan...@ex...?Subject=tellmemore Read On. If we told you that an extremely respected national publication as "MEN'S FITNESS MAGAZINE" published an article claiming they got dates with every beautiful woman they approached by using techniques from John Eagan's book, would that interest you? The over 260 page book called "How To 'Pick Up' Beautiful Women, Secrets Every Man Should Know" by John Eagan was rated NUMBER 1 by Men's Fitness Magazine after they field tested the top books on the market. Men's Fitness Magazine decided to take on the challenge of employing the techniques of the top books on the market today. Their findings will astound you. "How to 'Pick up' Beautiful Women, Secrets Every Man Should Know" by John Eagan received the highest rating because his techniques got them dates with every beautiful woman they approached. No other book on the market came even close. Why waste your time with anything less than NUMBER 1. The author, John Eagan has acquired two college degrees writes a popular sex and dating column for "Muslemag International" and hosts his own radio show. He has interviewed over 2000 beautiful women and incorporates that with the latest university studies on dating for this powerful book. He has also appeared on many national TV and radio shows. Would you like to find out why: Call for information call: 1-800-4-SECRET OR to receive more info by email click on link below. Mailto:jan...@ex...?Subject=tellmemore >> HOWARD STERN said "This guy is no bull, he's the real deal. I've seen him in action." "Wait until you see how amazing this guy is." >> GERALDO RIVERA was quoted as saying, "This book can get men over their shyness." >> ROLLING STONE MAG called John's techniques "genius." >> DANNY BONADUCE said, "John Eagan is a genius, you could pick anyone up with this book." >> SALLY JESSY RAPHAEL was quoted as calling the techniques "Perfect." >> GORDON ELLIOTT told his audience, "Take this man's advice." >> HARD COPY was quoted as saying, "This book can make women melt." Imagine yourself dating a beautiful woman today. Why be left out in the cold - Join the millions of successful men who have already learned the secrets. If you would like to read the Men's Fitness article for yourself and the introduction to the book along with what other distinguished celebrities had to say about the book, simply call us anytime, 24 hours a day, at 1-800-4-SECRET. If you want a free copy of the Men's Fitness Magazine article which rated this book number 1, give us a call. Call for information: 1-800-4-SECRET OR Mailto:jan...@ex...?Subject=tellmemore The Book, "How To 'Pick Up' Beautiful Women..." by John Eagan can be ordered as follows: PRICE: $14.95 plus $3.00 s/h (within the US). International orders available. You can order this book with a VISA, MasterCard or American Express by calling us at 1-800-4-SECRET and an operator would be happy to help you - 24 hours a day. OR you can send a check or money order made payable to: ~Secrets~ and send it to the following address: Secrets P.O. Box 6312 Freehold, NJ 07728 We would then have a book shipped to you immediately. Delivery time is 7 - 14 days. If you would like to receive the book sooner - for an additional $2.00 s/h (US residents only), Priority Mail will have that book to you in approximately 3 - 5 days. ~30 day Money Back Guarantee ~ You can purchase this book directly from us (all orders shipped immediately) OR you can special order from amazon.com (which rates us as one of their top selling books), Barnes & Noble (Internet or bookstore), or Borders Books & Music. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If this email has reached you in error, we appologize. Just click on the link below and you will be removed. MailTo:tom...@ya...?Subject=remove-me |
|
From: <ke...@us...> - 2002-10-21 13:14:24
|
I have released Mknbi 1.2-10 at http://www.etherboot.org/ This release contains changes which are essential to work with the Etherboot development series 5.1.x. The changes are compatible with Etherboot 5.0.x. Mknbi users are encouraged to rebuild their images with 1.2-10 or a later version as soon as convenient. An announcement of 5.1.2 will be made when it's ready so please do not ask when the release is. I stress that the 5.1.x series is development so please do not expect everything to work just like 5.0.x used to. But we will welcome bug reports. Or just wait until it becomes a stable series 5.2.x. |
|
From: <ke...@us...> - 2002-10-20 14:53:41
|
I have updated the tarball with Michael Brown's latest changes and it's available from: http://www.etherboot.org/etherboot-5.1.2rc7.tar.bz2 I have tested it with a 3c509 and the following work: + mkelf-nfl image + mkelf-linux image + mknbi-fdos image + mknbi-rom image (booting itself again, works repeatedly) It would be appreciated if people would test: Other NICs mknbi-linux with and without --first32pm -DRELOCATION Other options NFS booting anything else you normally use and post here. You *need* mknbi-1.2-10 to make the images. mknbi-1.2-10 will appear at the site as soon as the release system shows the files I have uploaded; it seems to be taking a weekend holiday. |
|
From: Eric W B. <ebi...@ln...> - 2002-10-18 22:51:44
|
ebi...@ln... (Eric W. Biederman) writes: > Michael Brown <mb...@fe...> writes: > > > On 16 Oct 2002, Eric W. Biederman wrote: > > > > For 5.1, it's trickier, as Eric says as if Etherboot is running above 1 > > > > MB and you can't turn it off there and then. > > > It isn't a lot trickier, as there is always code that runs below 1MB > > > to jump to the entry point. So we just need to include the > > > code in stub that jumps to the 16bit entry point. That is a little > > > trickier because that one piece can no longer be in C. :( > > > > It's not just the 16-bit entry point that needs it - it's also needed > > whenever Etherboot returns to the BIOS, or boots from disk. > > Right. In particular for 5.1 > exit16, and xstart16 need to have the code to disable the A20 line. > Given the complexity of that code figuring out how to share code > between those two cases is desireable. > > 5.1 is cleaner in what actually needs to be modified, than 5.0. It > is just more of a pain because you cannot do it in C. I haven't gotten to this yet. I'm busy trying to get some changes into 2.5.x before the feature freeze. But I did run across a weird system where you cannot disable the a20 line. So we need to be careful how this gets implemented... Eric |
|
From: Boris <bo...@th...> - 2002-10-17 21:40:48
|
Has anyone tried to flash the latest prism2_pci etherboot cvs into their bios? I have the rtl8139 driver working but when I put the prism2_pci driver, It doesnt seem to recognize it. Any ideas? |
|
From: <ebi...@ln...> - 2002-10-17 07:58:48
|
Michael Brown <mb...@fe...> writes: > On 16 Oct 2002, Eric W. Biederman wrote: > > > For 5.1, it's trickier, as Eric says as if Etherboot is running above 1 > > > MB and you can't turn it off there and then. > > It isn't a lot trickier, as there is always code that runs below 1MB > > to jump to the entry point. So we just need to include the > > code in stub that jumps to the 16bit entry point. That is a little > > trickier because that one piece can no longer be in C. :( > > It's not just the 16-bit entry point that needs it - it's also needed > whenever Etherboot returns to the BIOS, or boots from disk. Right. In particular for 5.1 exit16, and xstart16 need to have the code to disable the A20 line. Given the complexity of that code figuring out how to share code between those two cases is desireable. 5.1 is cleaner in what actually needs to be modified, than 5.0. It is just more of a pain because you cannot do it in C. Eric |
|
From: Michael B. <mb...@fe...> - 2002-10-17 07:46:06
|
On 16 Oct 2002, Eric W. Biederman wrote: > > For 5.1, it's trickier, as Eric says as if Etherboot is running above 1 > > MB and you can't turn it off there and then. > It isn't a lot trickier, as there is always code that runs below 1MB > to jump to the entry point. So we just need to include the > code in stub that jumps to the 16bit entry point. That is a little > trickier because that one piece can no longer be in C. :( It's not just the 16-bit entry point that needs it - it's also needed whenever Etherboot returns to the BIOS, or boots from disk. Michael Brown http://www.fensystems.co.uk |
|
From: <ebi...@ln...> - 2002-10-16 23:32:33
|
ke...@us... (Ken Yap) writes: > >We call gateA20_unset() on some exit paths but not all. The proper > >solution would probably be to have a static inline void eb_exit(int) that > >calls gateA20_unset() (and maybe some other last-minute tidy-ups) before > >doing an exit(). All existing calls to exit() should then be replaced > >with calls to eb_exit(). However, I'm not sure that I completely > >understand all the places where exit() is currently used in Etherboot, so > >I'm not confident in doing this. For example, in main.c we have: > > case 255: > > exit(0); > > state = -1; > > break; > >i.e. code following an exit(), which is puzzling me. > > > >Thoughts? > > >From a glance at the code, that looks like the correct solution for 5.0. > All the occurences of exit are in main, except for one in bootmenu.c > which I'll do for completeness. Have you tried it and does it work? If > so I'll make the changes later today. > > For 5.1, it's trickier, as Eric says as if Etherboot is running above 1 > MB and you can't turn it off there and then. It isn't a lot trickier, as there is always code that runs below 1MB to jump to the entry point. So we just need to include the code in stub that jumps to the 16bit entry point. That is a little trickier because that one piece can no longer be in C. :( Eric |
|
From: Michael B. <mb...@fe...> - 2002-10-16 21:45:27
|
On Thu, 17 Oct 2002, Ken Yap wrote: > >We call gateA20_unset() on some exit paths but not all. The proper > >solution would probably be to have a static inline void eb_exit(int) that > >calls gateA20_unset() (and maybe some other last-minute tidy-ups) before > >doing an exit(). All existing calls to exit() should then be replaced > >with calls to eb_exit(). However, I'm not sure that I completely > >understand all the places where exit() is currently used in Etherboot, so > >I'm not confident in doing this. For example, in main.c we have: > > case 255: > > exit(0); > > state = -1; > > break; > >i.e. code following an exit(), which is puzzling me. > >Thoughts? > From a glance at the code, that looks like the correct solution for 5.0. > All the occurences of exit are in main, except for one in bootmenu.c > which I'll do for completeness. Have you tried it and does it work? If > so I'll make the changes later today. I tried temporarily adding gateA20_unset to one exit path and it worked (in the sense that Windows then booted normally). I haven't made any changes to the code - be my guest. I should have this test machine available for another few days if anyone wants to come up with a solution for 5.1, but it'll have to go back to its owner at some point. I don't have any other machines that exhibit this problem. Michael Brown http://www.fensystems.co.uk |
|
From: <ke...@us...> - 2002-10-16 20:57:18
|
>We call gateA20_unset() on some exit paths but not all. The proper >solution would probably be to have a static inline void eb_exit(int) that >calls gateA20_unset() (and maybe some other last-minute tidy-ups) before >doing an exit(). All existing calls to exit() should then be replaced >with calls to eb_exit(). However, I'm not sure that I completely >understand all the places where exit() is currently used in Etherboot, so >I'm not confident in doing this. For example, in main.c we have: > case 255: > exit(0); > state = -1; > break; >i.e. code following an exit(), which is puzzling me. > >Thoughts? From a glance at the code, that looks like the correct solution for 5.0. All the occurences of exit are in main, except for one in bootmenu.c which I'll do for completeness. Have you tried it and does it work? If so I'll make the changes later today. For 5.1, it's trickier, as Eric says as if Etherboot is running above 1 MB and you can't turn it off there and then. |
|
From: <ke...@us...> - 2002-10-16 20:23:14
|
>Yes, that's right. For sure returning to the BIOS we should disable the >A20 line. 16 bit entry should also not enable it. It's confusing to me at this hour of the morning whether it's enable or disable, but in any case I mean return the line to the state it was found at boot up. |
|
From: <ke...@us...> - 2002-10-16 20:16:53
|
>This is tricky. We cannot reenable the a20 line on all paths out of >etherboot. Anything with a 32bit entry point expects the a20 line >to be already enabled. > >But probably for all code with a 16bit entry we need to do this, >along with the case when we return to the BIOS. Ken is this correct? >I wonder if this explains the DOS failures. Yes, that's right. For sure returning to the BIOS we should disable the A20 line. 16 bit entry should also not enable it. |
|
From: <ebi...@ln...> - 2002-10-16 18:59:52
|
Michael Brown <mb...@fe...> writes: > On Thu, 19 Sep 2002, Michael Brown wrote: > > > > > > don't have time to hack on Etherboot at the moment. However, if > someone > > > > > > > can tell me why, on some machines, Windows 98 takes forever (45 mins+) > to > > > > > > > start up if booted via Etherboot's "Boot (L)ocal" option, then I might > > > > > > > regain some spare time. :-) > > > > > BIOS Bug. Almost certainly. All we do is return to the BIOS. > > > > > Unless there is something we don't reset to it's original state? Some > > > > > bits of test code (Returning ealier to the BIOS) could identify if > > > > > whatever it is has changed yet, so it should be trackable. > > > > Thanks; that's confirmed what I thought would be the best debug strategy. > > > > It's certainly a BIOS or hardware-specific problem; it will happen on a > > > > batch of machines of the same hardware type. We tried looking at Windows > > > > 98's idea of a diagnostic boot log, but gave up when we found it contained > > > > > only six (unhelpful) lines. > > > I thought of one other possibility to try. We might be stomping BIOS tables > > > > if etherboot is loading to high. Setting RELOCADDR lower might be worth > > > a shot. > > Will try, thanks. > > > Which vesion of etherboot does the crawl show up with? > > 5.0.7. I did send a floppy of 5.1 to be tried, but it wouldn't even load > > up. I won't find out any more until one of the problematic machines gets > > delivered to me for testing. > > Now that I've finally got one of the said problematic machines, I've found > the problem. gateA20_unset() is not called before returning to the BIOS. > On this machine (and some others), if the BIOS is set to "Fast Gate A20" > then this is sufficient to cause Windows 98 to take around 45 minutes to > boot up. > > We call gateA20_unset() on some exit paths but not all. The proper > solution would probably be to have a static inline void eb_exit(int) that > calls gateA20_unset() (and maybe some other last-minute tidy-ups) before > doing an exit(). All existing calls to exit() should then be replaced > with calls to eb_exit(). However, I'm not sure that I completely > understand all the places where exit() is currently used in Etherboot, so > I'm not confident in doing this. For example, in main.c we have: > case 255: > exit(0); > state = -1; > break; > i.e. code following an exit(), which is puzzling me. A sanity check in case the code ever gets there. It won't but... > Thoughts? I hadn't picked up on this as a problem before, but it makes sense that someone should have trouble with the a20 line settings. This is tricky. We cannot reenable the a20 line on all paths out of etherboot. Anything with a 32bit entry point expects the a20 line to be already enabled. But probably for all code with a 16bit entry we need to do this, along with the case when we return to the BIOS. Ken is this correct? I wonder if this explains the DOS failures. The really trick part is we need to be very careful where we reenable the a20 line. For 5.0.x it isn't a problem to do it whenever as we live below 1MB. For 5.1.x doing at the wrong time could kill us. So for 5.1.x we need to ensure the renabling of a20 is in the trampoline that calls 16bit code. BIOS calls do not have a problem with the a20 line enabled do they? Eric |
|
From: Michael B. <mb...@fe...> - 2002-10-16 18:39:08
|
On Thu, 19 Sep 2002, Michael Brown wrote:
> > > > > don't have time to hack on Etherboot at the moment. However, if someone
> > > > > can tell me why, on some machines, Windows 98 takes forever (45 mins+) to
> > > > > start up if booted via Etherboot's "Boot (L)ocal" option, then I might
> > > > > regain some spare time. :-)
> > > > BIOS Bug. Almost certainly. All we do is return to the BIOS.
> > > > Unless there is something we don't reset to it's original state? Some
> > > > bits of test code (Returning ealier to the BIOS) could identify if
> > > > whatever it is has changed yet, so it should be trackable.
> > > Thanks; that's confirmed what I thought would be the best debug strategy.
> > > It's certainly a BIOS or hardware-specific problem; it will happen on a
> > > batch of machines of the same hardware type. We tried looking at Windows
> > > 98's idea of a diagnostic boot log, but gave up when we found it contained
> > > only six (unhelpful) lines.
> > I thought of one other possibility to try. We might be stomping BIOS tables
> > if etherboot is loading to high. Setting RELOCADDR lower might be worth
> > a shot.
> Will try, thanks.
> > Which vesion of etherboot does the crawl show up with?
> 5.0.7. I did send a floppy of 5.1 to be tried, but it wouldn't even load
> up. I won't find out any more until one of the problematic machines gets
> delivered to me for testing.
Now that I've finally got one of the said problematic machines, I've found
the problem. gateA20_unset() is not called before returning to the BIOS.
On this machine (and some others), if the BIOS is set to "Fast Gate A20"
then this is sufficient to cause Windows 98 to take around 45 minutes to
boot up.
We call gateA20_unset() on some exit paths but not all. The proper
solution would probably be to have a static inline void eb_exit(int) that
calls gateA20_unset() (and maybe some other last-minute tidy-ups) before
doing an exit(). All existing calls to exit() should then be replaced
with calls to eb_exit(). However, I'm not sure that I completely
understand all the places where exit() is currently used in Etherboot, so
I'm not confident in doing this. For example, in main.c we have:
case 255:
exit(0);
state = -1;
break;
i.e. code following an exit(), which is puzzling me.
Thoughts?
Michael Brown
http://www.fensystems.co.uk
|
|
From: <ebi...@ln...> - 2002-10-16 12:45:27
|
Michael Brown <mb...@fe...> writes: > On Wed, 16 Oct 2002, Ken Yap wrote: > > >What I would like to do is create a setup where I can have multiple > > >Config files and each Config file would have it's own seperate bin > > >directory. > > >The easiest way I can think to do that right now is: > > >1) reverse the includes and have Config include Makefile > > > so we can be flexible about the name. > > >2) Have a variable in Config that specifies the bin directory, > > > or the directory the bin directory lives in. > > >3) Have a variable in Config that specifies where the Etherboot > > > source tree lives. > > >Being able to do: > > >make -f Config-lnxi blah > > >make -f Config-lnxi-lb blah > > >And generate all of the romimages I need would be very nice > > >when I am generating a binary rpm with all of the romimages I need. > > >And it would make compile testing with different Config easy > > >as well. > > Sounds good, do you want to do it? I will put in my todo list. I just don't know when I will get there as my schedule is up in the air beyond this week where I try to get code into the kernel. > One small request: please have Config include Makefile.inc (or something > similar) and have a Makefile that just contains: > > % : force > @$(MAKE) -f Config $@ > force : ; > > This is so that it's still possible to just type "make" and get something > built. It's a "beginner-friendly" thing; we probably don't want to put > off new developers by breaking the standard build procedure. Sounds good. I couldn't think of something sane with my initial proposal. And eventually we will want a variable in Config that tell the machine type to build for if are doing a cross compile. Does anyone see any value in a ./configure script at this time. Having something that goes out and tests to make certain you have a working compiler and linker at build time could be handy. But for now I will just plan on the baby step of turning the Makefile inside out. Eric |
|
From: Michael B. <mb...@fe...> - 2002-10-16 09:40:49
|
On Wed, 16 Oct 2002, Ken Yap wrote: > >What I would like to do is create a setup where I can have multiple > >Config files and each Config file would have it's own seperate bin > >directory. > >The easiest way I can think to do that right now is: > >1) reverse the includes and have Config include Makefile > > so we can be flexible about the name. > >2) Have a variable in Config that specifies the bin directory, > > or the directory the bin directory lives in. > >3) Have a variable in Config that specifies where the Etherboot > > source tree lives. > >Being able to do: > >make -f Config-lnxi blah > >make -f Config-lnxi-lb blah > >And generate all of the romimages I need would be very nice > >when I am generating a binary rpm with all of the romimages I need. > >And it would make compile testing with different Config easy > >as well. > Sounds good, do you want to do it? One small request: please have Config include Makefile.inc (or something similar) and have a Makefile that just contains: % : force @$(MAKE) -f Config $@ force : ; This is so that it's still possible to just type "make" and get something built. It's a "beginner-friendly" thing; we probably don't want to put off new developers by breaking the standard build procedure. Michael |
|
From: <ke...@us...> - 2002-10-16 08:49:21
|
>Can we merge everthing into just bin? > >Unless we setup for cross compilers we cannot build for multiple >architectures simultaneously. And currently I definitely cannot >build for LinuxBIOS and non LinuxBIOS simultaneously on the same >architecture. > >What I would like to do is create a setup where I can have multiple >Config files and each Config file would have it's own seperate bin >directory. > >The easiest way I can think to do that right now is: >1) reverse the includes and have Config include Makefile > so we can be flexible about the name. >2) Have a variable in Config that specifies the bin directory, > or the directory the bin directory lives in. >3) Have a variable in Config that specifies where the Etherboot > source tree lives. > >Being able to do: >make -f Config-lnxi blah >make -f Config-lnxi-lb blah > >And generate all of the romimages I need would be very nice >when I am generating a binary rpm with all of the romimages I need. >And it would make compile testing with different Config easy >as well. Sounds good, do you want to do it? |
|
From: <ebi...@ln...> - 2002-10-16 08:06:58
|
ke...@us... writes: > What do you think of the idea of merging both directories as ia32? > (bin was for stuff that was neither bin16 nor bin32, usually auxiliary > binaries or prefixes, but there is no more bin16 so this distinction is > no longer necessary.) Other architectures, when ported to, would then > compile to binaries under the architecture name. > > Just did a 2 minute experiment, s/bin(32)?/ia32/g in Makefile and > genrules.pl, rm Roms, and it builds fine. Can we merge everthing into just bin? Unless we setup for cross compilers we cannot build for multiple architectures simultaneously. And currently I definitely cannot build for LinuxBIOS and non LinuxBIOS simultaneously on the same architecture. What I would like to do is create a setup where I can have multiple Config files and each Config file would have it's own seperate bin directory. The easiest way I can think to do that right now is: 1) reverse the includes and have Config include Makefile so we can be flexible about the name. 2) Have a variable in Config that specifies the bin directory, or the directory the bin directory lives in. 3) Have a variable in Config that specifies where the Etherboot source tree lives. Being able to do: make -f Config-lnxi blah make -f Config-lnxi-lb blah And generate all of the romimages I need would be very nice when I am generating a binary rpm with all of the romimages I need. And it would make compile testing with different Config easy as well. Eric |
53 messages has been excluded from this view by a project administrator.