|
|
Post by pharrisire on May 15, 2012 16:42:18 GMT -5
Booted and ran fine from the disc.
The stick was made successfully and
ran fine, but preferences put in the
2+Gigs left over were not available
on the next boot.
|
|
|
|
Post by cybrguy on May 15, 2012 16:56:47 GMT -5
Loaded from disk well. Made USB stick and am running from that now. Seems very solid so far, though there apparently are no Wifi drivers for my ASUS K53e so I am using wired for now...
|
|
|
|
Post by Kevin McAleavey on May 16, 2012 2:51:14 GMT -5
Booted and ran fine from the disc. The stick was made successfully and ran fine, but preferences put in the 2+Gigs left over were not available on the next boot. Try saving it again to that area and let me know what happens ... |
|
|
|
Post by Kevin McAleavey on May 16, 2012 2:52:51 GMT -5
Loaded from disk well. Made USB stick and am running from that now. Seems very solid so far, though there apparently are no Wifi drivers for my ASUS K53e so I am using wired for now... Sorry for the wait ... had to look into this. That machine comes with an Atheros ar9485 chipset. Unfortunately, Atheros hasn't provided any driver technical information on it to anyone other than Microsoft so far. Even the Linux ath9x driver doesn't run for it and unfortunately BSD won't be working on a driver for it until sometime over the summer and even there, they've encountered a number of problems. If we were faced with a custom build requirement for that machine, we could build a special "NDIS" driver in a specific build for it and then cross-compile the Windows driver, but it would end up being a special build just for that one machine. Customs are what we do here, but it wouldn't be practical for one copy. And apologies about the wifi card there ... hopefully once there IS a driver for it, we can put out an update. But at the moment, no driver for it exists |
|
|
|
Post by pharrisire on May 16, 2012 15:24:55 GMT -5
""Try saving it again to that area and let me know what happens ... ""
Perseverance pays = I just kept on saving and rebooting to see if it took,
and it finally did!
A KNOS64 diags from stick is on its way
|
|
|
|
Post by Kevin McAleavey on May 16, 2012 20:25:55 GMT -5
""Try saving it again to that area and let me know what happens ... "" Perseverance pays = I just kept on saving and rebooting to see if it took, and it finally did! A KNOS64 diags from stick is on its way All looks good with the exception of that Microsoft mouse you're using. System is indicating that it doesn't like it and keeps attaching and disattaching it until it finally settles down. Looks like some sort of timing error in the hardware there, but KNOS doesn't care once it settles down. Other than the flaky mouse behavior, didn't see anything out of the ordinary. My first guess though is that possibly that had something to do with it, but the mouse *does* settle down eventually. |
|
