desktop stick 64bit diags on its way
I'm seeing an interesting problem on this box ... seems as though it's not handling the USB stick properly from these errors:
Apr 2 15:13:16 KNOS-64 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
Apr 2 15:13:16 KNOS-64 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present
Apr 2 15:13:16 KNOS-64 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
Apr 2 15:13:16 KNOS-64 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present
Apr 2 15:13:16 KNOS-64 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
Apr 2 15:13:16 KNOS-64 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present
Apr 2 15:13:16 KNOS-64 kernel: (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0
Apr 2 15:13:16 KNOS-64 kernel: (da0:umass-sim0:0:0:0): SCSI sense: No sense data present
This is a BIOS problem. But yet the stick is booting?
I see that it's an 8GB stick, and it should have a personal area which would show up as roughly a little under 3GB for your files. Are you seeing that space? When freshly formatted, it will show up as a completely empty drive and that's where you would save your prefs.
Prefs for 32 bit is different from 64 since some folks would set up for 32 differently from 64 and so we have two FIXED filenames for 9. You can't choose a filename for 9 like we did back in 8. In order for KNOS to find the prefs, the names must remain the same name as chosen by the backup utility. That would be KNOS_PREFS (.tar.gz which is automatically added) for 32 bits, and KNOS_PREFS64 (.tar.gz) for 64 bits. In that backup dialog, the only thing you need to do is choose which drive the files go to and leave the name picked alone. Just wanted to be sure that it's not getting changed - that would cause the problem right there. If the dialog we use was able to only choose the drive, we would have gone that way.
If you're saving the prefs on a hard drive, then you'd choose the hard drive in question (again, not changing the name at all) and the way KNOS checks for a preloaded preferences is to try the hard drive first. If the system is booted from a stick, it'll check for personal space on there and ignore the hard drive. Finally, if a completely different stick is plugged in that contains the prefs, then that would take priority and load instead of the previous two options.
One of them should work ... but that little oddity in the diagnostics there seems to indicate a problem with that Kingston stick indicating that BIOS isn't ready when we're booting, and that's when we're looking for that prefs stuff before we kick into the desktop.
If you look carefully as KNOS is booting, you should see the following after networking setup shoots by:
"Looking for saved KNOS Preferences ..."
Within a second or two, you should see one of the following on the next line:
"Loading saved KNOS preferences from personal USB stick ..." ... or ...
"Loading saved KNOS preferences from Bootable KNOS stick ..." ... or ...
"Loading saved KNOS preferences from hard drive ..."
... or finally, if it can't find anything in those locations:
"No saved preferences were found ..."
If the latter occurs, it will be caused by either the drive not being available as KNOS is booting, OR the filename was not saved as KNOS_PREFS.tar.gz (for 32 bits) or KNOS_PREFS64.tar.gz (for 64 bits) as chosen by the backup your apps menu.
Check it, and let me know.
