|
Post by pharrisire on May 15, 2012 16:37:18 GMT -5
First, the download proceedure was much smoother this time! No Redownloading!!
Lenovo booting on the new disc saw my saved prefs and loaded them, which got me real excited!, but after doing the upgrade, KNOS no longer saw the 34G personal space, so no prefs. Went back to the disc and did the install instead of the upgrade, and now it sees the 34g, but of course the prefs could not survive that. Anyhows, its saving fine now so I'll build it back to where it was.
The stick build was not successful.
And a little oddity - changing the clock to 24hr and temp to F and wind speed to mph did not get saved in the prefs, while theme, background, firefox stuff, etc.... does.
|
|
|
Post by Kevin McAleavey on May 16, 2012 2:50:17 GMT -5
First, the download proceedure was much smoother this time! No Redownloading!! Lenovo booting on the new disc saw my saved prefs and loaded them, which got me real excited!, but after doing the upgrade, KNOS no longer saw the 34G personal space, so no prefs. Went back to the disc and did the install instead of the upgrade, and now it sees the 34g, but of course the prefs could not survive that. Anyhows, its saving fine now so I'll build it back to where it was. The stick build was not successful. And a little oddity - changing the clock to 24hr and temp to F and wind speed to mph did not get saved in the prefs, while theme, background, firefox stuff, etc.... does. As we indicated in the User manual on the desktop, we had to change the sizing for our kernel and thus I suspect that your disk was originally formatted in the old size. If it's any comfort, that won't happen again - we sized KNOS so that there's plenty of room for future expansion. As to the stick build, tell me more about what happened there and let's see if we can find out why. The clock settings ... did you set up your location and time zone? That's in that same edit button that you set those preferences in. It needs a location. Lots of us use that and it normally works just fine. Tell me more about that too. Perhaps a run of diagnostics might shed light on it if it's still misbehaving after a second save ...
|
|
|
Post by pharrisire on May 16, 2012 14:06:54 GMT -5
""The clock settings ... did you set up your location and time zone? . Perhaps a run of diagnostics might shed light on it if it's still misbehaving after a second save ...""
Well, it was more like the fifth or sixth save, but no matter cause its now saved. And a new diags is on its way.
|
|
|
Post by pharrisire on May 16, 2012 14:30:24 GMT -5
""As to the stick build, tell me more about what happened there and let's see if we can find out why.""
Here's a copy of the terminal output:
At the prompt below, type in EXACTLY what you see on the line below into the prompt below and then hit enter to make your KNOS stick:
sh knos2usb
If you wish to upgrade a previous installation of KNOS9 beta or later then type in THIS instead to preserve your existing data:
sh upgrade
KNOS-32# sh knos2usb Hit your enter key to format your device ... [Should be: /dev/da0]: diskinfo: /dev/da0: No such file or directory diskinfo: /dev/da0: No such file or directory diskinfo: /dev/da0: No such file or directory diskinfo: /dev/da0: No such file or directory knos2usb: arithmetic expression: expecting primary: "/1000000000" KNOS-32# su KNOS-32# sh knos2usb Hit your enter key to format your device ... [Should be: /dev/da0]: Unable to find /dev/da0, please check the pathname KNOS-32#
|
|
|
Post by Kevin McAleavey on May 16, 2012 20:21:21 GMT -5
""The clock settings ... did you set up your location and time zone? . Perhaps a run of diagnostics might shed light on it if it's still misbehaving after a second save ..."" Well, it was more like the fifth or sixth save, but no matter cause its now saved. And a new diags is on its way. Strange indeed ... that should have stuck the first time around since those settings are stored in the same location as all of the other settings for the top panel. We'll have to see if this happens to anyone else. Glad it's there finally, whatever it was that happened there ...
|
|
|
Post by Kevin McAleavey on May 16, 2012 20:23:54 GMT -5
Unable to find /dev/da0, please check the pathname KNOS-32# Strange indeed ... /dev/da0 is the first USB stick that is plugged in and the diagnostics you sent showed a USB hub with nothing attached. Any chance of doing that diagnostic thing one more time AFTER you've plugged in a USB stick? That might give a clue as to why it didn't show up there. If there's a problem with the USB stuff, that'll only show in the diagnostics once our kernel has had a chance to probe at it. The diags you sent didn't show any signs of any USB stuff at the time the snapshot was taken.
|
|
|
Post by pharrisire on May 17, 2012 10:01:31 GMT -5
KNOS9_32 diags right after
""Hit your enter key to format your device ... [Should be: /dev/da0]: Unable to find /dev/da0, please check the pathname ""
is on its way.
|
|
|
Post by Kevin McAleavey on May 18, 2012 1:11:44 GMT -5
KNOS9_32 diags right after ""Hit your enter key to format your device ... [Should be: /dev/da0]: Unable to find /dev/da0, please check the pathname "" is on its way. Hmmmm ... that stick seems to have a problem with your hardware there: May 17 10:53:22 KNOS-32 kernel: ugen4.2: <Kingston> at usbus4 May 17 10:53:22 KNOS-32 kernel: umass0: <Kingston DataTraveler 160, class 0/0, rev 2.00/1.00, addr 2> on usbus4 May 17 10:53:22 KNOS-32 kernel: da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 May 17 10:53:22 KNOS-32 kernel: da0: <Kingston DataTraveler 160 1.00> Removable Direct Access SCSI-2 device May 17 10:53:22 KNOS-32 kernel: da0: 40.000MB/s transfers May 17 10:53:22 KNOS-32 kernel: da0: 7624MB (15615620 512 byte sectors: 255H 63S/T 972C) May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 May 17 10:53:22 KNOS-32 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present May 17 10:53:24 KNOS-32 kernel: pid 4584 (hald-probe-volume), uid 0: exited on signal 6 KNOS sees it, tries to mount it, and the hardware in that machine is unable to determine what it is. After 10 tries, the automount gives up and exits. Are you by any chance trying to do that with the KNOS bootable USB stick? If so, that's not possible because of our security design which prevents a bootable KNOS stick (and its personal area) from being used by anything other than KNOS when booted from that stick. It's to prevent access to the ability to modify any of that personal data or saved settings outside of the KNOS it was created on. When personal data is saved on a FAT-32 (Windows) stick that doesn't have a KNOS boot on it, then you can access that data but we won't let Windows write to it. DO you perchance have another USB stick that you could try that with? The "No sense data present" indicates that the system does not like the way the stick you are using is formatted. Hopefully another stick will do the trick ... unless that's your KNOS bootable, you could try reformatting the stick on a Windows box as a FAT-32 stick. Maybe the format on it is messed somehow. A reformat usually cures cranky sticks.
|
|
|
Post by pharrisire on May 18, 2012 10:20:10 GMT -5
"" Are you by any chance trying to do that with the KNOS bootable USB stick? ""
It is the same stick that I had used for the previous versions of KNOS32. The other 8Gig stick is for KNOS64. IIUC, I will take the KNOS32 stick and reformat it FAT32 in windows, then try the 'Make bootable KNOS USB' again.
|
|
|
Post by Kevin McAleavey on May 19, 2012 1:40:04 GMT -5
"" Are you by any chance trying to do that with the KNOS bootable USB stick? "" It is the same stick that I had used for the previous versions of KNOS32. The other 8Gig stick is for KNOS64. IIUC, I will take the KNOS32 stick and reformat it FAT32 in windows, then try the 'Make bootable KNOS USB' again. OK ... a stick formatted for KNOS is no longer a FAT32 (Windows) stick. That's done for security to protect both us AND Windows from "cross-pollination." A regular FAT32 WINDOWS stick is what you'd need to have formatted in order for it to be loaded by KNOS as an "ordinary stick" since BIOS in those machines is set up for Windows. If you're going to use that stick for data (and for example the KNOS prefs backup) then it needs to be formatted as FAT-32 like a fresh stick you just bought. The provision for personal storage on a "larger than" 4GB stick is done on those sticks in KNOS format in order to protect that data. Hopefully your system will detect it and allow KNOS to load it once it's FAT32 again ...
|
|
|
Post by pharrisire on May 19, 2012 4:58:29 GMT -5
"" Hopefully your system will detect it and allow KNOS to load it once it's FAT32 again ... ""
I think the stick has just become an orphan - Windows said it could not complete the format, after a Lonnnggg time at about half-way through, and now says it can not format the stick. And now KNOS does not even acknowledge that the stick exists... What a kerfuffle,,,,,,,
|
|
|
Post by Kevin McAleavey on May 19, 2012 23:09:46 GMT -5
"" Hopefully your system will detect it and allow KNOS to load it once it's FAT32 again ... "" I think the stick has just become an orphan - Windows said it could not complete the format, after a Lonnnggg time at about half-way through, and now says it can not format the stick. And now KNOS does not even acknowledge that the stick exists... What a kerfuffle,,,,,,, Well then ... let's de-kerfuffle that bad boy then! Kingston's sticks have an unusual layout. Since Windows blew chunks on reformatting it, and apparently that's expected, Kingston has their OWN formatter which should make things happy again. Go grab their format utility here: www.kingston.com/us/support/technical/downloads?product=dthx30&filename=kingston_format_utilityOf note on that page, "Formatting this drive with Windows, Mac or Linux may cause a performance decrease." Theirs should work though to bring that stick back to sanity.
|
|
|
Post by pharrisire on May 21, 2012 12:47:58 GMT -5
Tried to save it direct to my 34G storage space, but it crashed the browser. So saved it to desktop first and then moved it over ok. The utility started up via Wine, but it could not see the stick. Went to the desktop and did it, and it seems to have De-Kerfuffled the stick successfully. Will now bring the stick back to KNOS and try the make-bootable routine.
|
|
|
Post by pharrisire on May 21, 2012 13:17:44 GMT -5
First try at make-bootable-usb yielded:
KNOS-32# sh knos2usb Hit your enter key to format your device ... [Should be: /dev/da0]: diskinfo: /dev/da0: No such file or directory diskinfo: /dev/da0: No such file or directory diskinfo: /dev/da0: No such file or directory diskinfo: /dev/da0: No such file or directory knos2usb: arithmetic expression: expecting primary: "/1000000000" KNOS-32#
-
|
|
|
Post by pharrisire on May 21, 2012 13:36:31 GMT -5
After a reboot with the stick in, it showed up top next to the 34G, as unmounted. Removed it, and followed the make-bootable-usb prompts, and this time the result was:
KNOS-32# sh knos2usb Hit your enter key to format your device ... [Should be: /dev/da0]: Unable to find /dev/da0, please check the pathname KNOS-32#
|
|