Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
soc:2010:andreif:journal:week5 [2010/06/23 11:13] andreif |
soc:2010:andreif:journal:week5 [2010/06/28 09:15] (current) andreif |
||
|---|---|---|---|
| Line 26: | Line 26: | ||
| Everything's ready for the first test tomorrow. | Everything's ready for the first test tomorrow. | ||
| + | |||
| + | ==== Day 4 [ Thu 24 Jun 2010 ] ==== | ||
| + | |||
| + | Git commit: [[http://git.etherboot.org/?p=people/andreif/gpxe.git;a=commit;h=5756a78e83b6a83851a07fce80b2993772b772ce|5756a78e83b6a83851a07fce80b2993772b772ce]] | ||
| + | |||
| + | Lots'o'issues today. | ||
| + | |||
| + | * Using the ''forcedeth.usb'' image does not work. At first I thought that there was a problem with my USB stick, but then Marty confirmed that this seems to be an issue with a lot of systems and suggested I use SYSLINUX instead. And so I did. I followed the instructions from [[http://www.etherboot.org/wiki/eb_imagetypes?s[]=usb&s[]=boot#usb_flash_etherboot_-_general_hard_disk_boot_geometry|here]] to create the bootable stick. It worked, but SYSLINUX gave an error: **cannot find kernel image**. It was surprising since ''forcedeth.lkrn'' was there on the stick and the ''syslinux.cfg'' file was correct. Well, I learned something new because of this; since I formatted the disk with ''mkdosfs'', the filnames have [[http://en.wikipedia.org/wiki/8.3_filename|a restriction]]. Renaming ''forcedeth.lkrn'' to ''forcedet.lkr'' and modifying the ''syslinux.cfg'' accordingly, I managed to get gPXE to boot. | ||
| + | |||
| + | * And yet, it doesn't work! Naturally I now enabled debugging messages to see how the .probe routine behaved. Nothing showed up. I enabled debugging in PCI too and that didn't work either. In case someone else runs into the same problems, here are some of the things you might want to look for (all compiled from the discussion I had today with Marty and Stefan): | ||
| + | * the file you want to debug does have actual DBG messages | ||
| + | * output is redirected to the serial console (''config/console.h'') | ||
| + | * check the link map to see if the object you're debugging gets imported | ||
| + | * make sure the driver does have a PCI_ROM statement that corresponds to the NIC's characteristics | ||
| + | * call ''adjust_pci_device()'' | ||
| + | * make sure the struct pci_driver isn't tagged with an __unused label | ||
| + | |||
| + | The last two of these were the problems I've had, but I went through all of them in order to figure out what the problem was. As a result, .probe now works, life is good. Of course, bugs related to it will surface once I implement the other routines. | ||
| + | |||
| + | I didn't get to do anything else today, I'll have to catch up tomorrow. As Stefan said, booting from an USB stick can be a real pain because of the constant dd-ing and moving of the switch from one USB port to another. As he suggested, I'll get a switch and setup a small DHCP server that can service the forcedeth machine with an image it can chainload. | ||
| + | |||
| + | Hurray for using gPXE for the first time on a physical machine ^_^ | ||
| + | |||
| + | ==== Day 5 [ Fri 25 Jun 2010 ] ==== | ||
| + | |||
| + | Only managed to run a couple of tests on Virtual Box today, with console disabled. There was a clear difference in speed with the console disabled but overall speeds increased because of packet interception (my guess). I should investigate this, plus try it with the rtdsc timer. | ||
| + | |||
| + | ==== Day 6 [ Sat 26 Jun 2010 ] ==== | ||
| + | |||
| + | me.\m/() | ||
| + | |||
| + | ==== Day 7 [ Sun 27 Jun 2010 ] ==== | ||
| + | |||
| + | me.rest() | ||
