|
Post by pharrisire on May 16, 2012 15:47:25 GMT -5
On the desktop, KNOS64 from stick will not shut down when using the timer to shut down - it just goes to a blank screen, but machine stays running. And when clicking the shut-down button, it does not shut down but rather reboots. Not a problem now that I know, just something to be aware of.
|
|
|
Post by Kevin McAleavey on May 16, 2012 20:26:49 GMT -5
On the desktop, KNOS64 from stick will not shut down when using the timer to shut down - it just goes to a blank screen, but machine stays running. And when clicking the shut-down button, it does not shut down but rather reboots. Not a problem now that I know, just something to be aware of. We ARE giving it a power off command through BIOS when shutdown is called by KNOS. I trust that you're going up top, System, shutdown and selecting the shutdown button there? If so, that's a hardware call to shutdown. Just for laughs and giggles, try this instead and let me know what happens: Open a terminal, put in su and hit enter at the first prompt. At the second prompt, type in this and then hit enter: shutdown -p now That's what we're calling in the desktop, let me know if it behaves differently from terminal. If that shuts it down, then for some reason, BIOS is ignoring our system call. We'll figure it out.
|
|
|
Post by pharrisire on May 17, 2012 9:50:41 GMT -5
""Open a terminal, put in su and hit enter at the first prompt. At the second prompt, type in this and then hit enter:
shutdown -p now ""
That did it !!
|
|
|
Post by pharrisire on May 17, 2012 10:51:36 GMT -5
Using 'shutdown -p now' gives the familiar lines of text as the system shuts down, but using System>Shut Down>Shut Down results in a blank screen then a completely black screen until it reboots.
|
|
|
Post by Kevin McAleavey on May 18, 2012 1:12:43 GMT -5
Using 'shutdown -p now' gives the familiar lines of text as the system shuts down, but using System>Shut Down>Shut Down results in a blank screen then a completely black screen until it reboots. Squirrels in BIOS then ... if shutdown worked, the other should as well. The only difference between the two is that the terminal call causes a system halt, and the one through gnome calls halt through a BIOS function instead. Let me see what I can do, the code that does that is in Gnome's code and is not part of KNOS. I'm going to have to file a PR with the Gnome folks over it. Wish I'd known about this during the test process. That code hasn't changed through several iterations of Gnome. I'll look at that 64 bit diagnostics a little deeper and see if anything obvious turns up, but it's definitely BIOS-related in the power control settings since the power button is often used in some designs to also control sleep/hibernation and they might be doing something nonstandard with it ... whose product is that one again?
|
|
|
Post by pharrisire on May 18, 2012 10:11:58 GMT -5
"" ... whose product is that one again? ""
The desktop is a 'beige box'. CPU - Intel Core I7 2600K RAM - DDR3 16G Motherboard - Gigabyte Z68MA-D2H-B3 Chipset - Intel Sandy Bridge 09 Southbridge - Intel ID1C44 05 BIOS - Award ver. F9 Graphics - GeForce 7300 LE
|
|
|
Post by Kevin McAleavey on May 19, 2012 1:38:57 GMT -5
"" ... whose product is that one again? "" The desktop is a 'beige box'. CPU - Intel Core I7 2600K RAM - DDR3 16G Motherboard - Gigabyte Z68MA-D2H-B3 Chipset - Intel Sandy Bridge 09 Southbridge - Intel ID1C44 05 BIOS - Award ver. F9 Graphics - GeForce 7300 LE OK ... just confirmed with Gigabyte's tech people that there IS a BIOS issue, and it also affects some Windows7 users as well with that oddity with Award BIOS. They supposedly did an update which they THINK fixes it, you might want to check for it with Gigabyte for that model. If you're in a position where you don't want to or can't do the BIOS update, let me know and I can slap together a custom thingy for you that you can plant on your desktop that will do that "shutdown now" thing. Since you're backing up prefs now, I can key it so that it's OK to add and save. I have your diagnostics from there, so I can make a key for it that will allow KNOS to accept it from "mommy" here.
|
|
|
Post by pharrisire on May 21, 2012 14:02:31 GMT -5
"" If you're in a position where you don't want to or can't do the BIOS update, let me know and I can slap together a custom thingy for you that you can plant on your desktop that will do that "shutdown now" thing. Since you're backing up prefs now, I can key it so that it's OK to add and save. I have your diagnostics from there, so I can make a key for it that will allow KNOS to accept it from "mommy" here. ""
I am willing to give that BIOS update a try, but I would feel a whole lot better if I had that custom thingy planted, and saved, first - if that's OK with you.
|
|
|
Post by Kevin McAleavey on May 22, 2012 2:01:09 GMT -5
"" If you're in a position where you don't want to or can't do the BIOS update, let me know and I can slap together a custom thingy for you that you can plant on your desktop that will do that "shutdown now" thing. Since you're backing up prefs now, I can key it so that it's OK to add and save. I have your diagnostics from there, so I can make a key for it that will allow KNOS to accept it from "mommy" here. "" I am willing to give that BIOS update a try, but I would feel a whole lot better if I had that custom thingy planted, and saved, first - if that's OK with you. OK ... right now, we're still in process of bringing other customers with custom builds up to version 9 - those have to be finished first. Once I'm caught up, we'll write you that special code. Shouldn't be more than a couple more days.
|
|