#tyndur · 2010-08-11

20 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen

  1. pcmattmankwolf: in vmware, I booted both Deustch and English variations and when it came to the "Select your keymap" screen, I couldn't move up or down or hit enter to pick one
  2. kwolfpcmattman: That's strange. So basically keyboard didn't work at all?
  3. pcmattmanNot at all
  4. pcmattmanThe serial line had something like "kbc: <german> scancode 0x7a"
  5. pcmattmanI was looking at seeing if the e1000 driver works in vmware for tyndur to see there's actually a problem with the driver or just Pedigree's CDI implementation
  6. kwolfRight... The e1000 driver doesn't work for Pedigree even in qemu?
  7. pcmattmanI haven't yet checked in QEMU, will do when I get home though
  8. pcmattmanJust thinking that if I can prove it's Pedigree you don't need to keep pestering me to fix e1000 ;)
  9. kwolfI just wonder what the problem with the keyboard could be. It's not like it was a horribly complex piece of hardware...
  10. kwolfWell, that EEPROM protocol that you implemented was needed for VBox, right?
  11. pcmattmanHmm, yes - to get the MAC, but a patch was submitted for VBox to implement the EERD anyway
  12. kwolfWouldn't hurt to have support for it anyway. There's certainly (real) hardware that needs it.
  13. pcmattmanRight, and I think I sent a patch for the eeprom stuff anyway
  14. kwolfThough I don't own an e1000 myself
  15. kwolfYou did, but there were some minor changes left that you wanted to do before committing
  16. kwolfI need to install a current VBox to actually test it, then I could do these changes myself
  17. pcmattmanIt should be okay to commit the eeprom stuff, I can't actually find the mail for that e1000 patch so I can't remember what I wanted to add/remove
  18. kwolfShould be in the mailing list archive
  19. kwolfMarch or something
  20. pcmattmanFound it