|
Post by jerry on Nov 21, 2010 23:54:19 GMT -5
I've attached a picture of my laptop screen with the boot problems. I'm running a toshiba laptop Win 7 Home Premium 64 bit Intel Pentium Dual Core 2.3 Ghz 4 gigs of ram Attachments:
|
|
|
Post by Kevin McAleavey on Nov 22, 2010 1:51:06 GMT -5
Just to let you know, I have some BSD kernel guys looking into this - it's definitely a BIOS issue on that machine, but right now, I don't know what's causing it. Hopefully we'll have an answer for you later today, since several of us have been scratching our heads on this one today. We've gotten past BIOS issues before, hang in there and THANKS for letting us know! Glad the heavy diagnostics screen managed to produce a picture of where it hurts! Can you tell me the BRAND and MODEL of the machine in question? I'm sure they're going to ask me that once they show up later ...
|
|
|
Post by jerry on Nov 22, 2010 8:30:45 GMT -5
|
|
|
Post by Kevin McAleavey on Nov 22, 2010 13:28:14 GMT -5
Greetings ... according to the BSD guys, Toshiba did indeed have a bad BIOS build with that model and they apparently did a fix back in May for it. Only question of course is whether or not your machine got the fix or not. There IS a ACPI BIOS update listed on their site which should be the good one. Otherwise we'll have to come up with a special build of KNOS that has ACPI parsing turned off to avoid the hole in their code. We'd do this for a manufacturer that needed a special kernel, but what we have out there now doesn't have the ability to step over bad BIOS code. Toshiba has the download HERE if you're actually comfortable with the idea of doing a BIOS update yourself: www.csd.toshiba.com/cgi-bin/tais/support/jsp/modelContent.jsp?ct=DL&os=&category=&moid=2737394&rpn=PSC08U&modelFilter=C655-S5068&selCategory=2756709&selFamily=1073768663But if not, one of their techs would have to do it for you. Given the apparent age of your toy, I imagine it's still under warrantee. Sorry about this, but the problem is bad code in your BIOS which is causing KNOS to walk off a cliff when booting. Let me know if I can be of any help here, but not much I can do if the manufacturer stepped on a duck.
|
|
|
Post by jerry on Nov 22, 2010 14:13:11 GMT -5
I was thinking along the same lines and checked Toshiba's website for the newest bios. The newest code was released in may and is version 1.20. I looked in my setup and I have this listed: System BIOS version: 1.20 EC version: 1.10 I'm assuming I have the latest version, so I guess I'm SOL
|
|
|
Post by Kevin McAleavey on Nov 22, 2010 20:29:27 GMT -5
I was thinking along the same lines and checked Toshiba's website for the newest bios. The newest code was released in may and is version 1.20. I looked in my setup and I have this listed: System BIOS version: 1.20 EC version: 1.10 I'm assuming I have the latest version, so I guess I'm SOL Don't give up yet - we aren't about to ... I was just hoping it would be easy. Heh. Been after this ever since I saw your message - it would appear from the manuals from Toshiba that there isn't a standard BIOS in there and that apparently the only way to get at BIOS is from Windows 7 in their "HWsetup" screen. I'm not sure that there's anything in there that will make a difference, but just for laughs and giggles, you might want to play in the USB tab with "legacy settings" and see if setting the opposite mode makes any difference. If not, then toss it back where it was. In the SATA tab, might also want to try alternate settings (the manual does not show what any of the options are, so I'm flying blind on this idea) and see if that makes any difference too. I'm sort of hoping that between these two locations (can't see any others that might make a difference) we might get the settings memory to fill itself in and be "valid." Somehow I suspect that none of this will make any difference, but if you could give it a shot, perhaps this might get you going for now. There is a new piece of Toshiba-specific code that BSD has in their experimental "9 current" kernel, due out next year, that I'm thinking of borrowing and trying with a special test build for you. It'll take me about 2-3 weeks though to build it and upload it if you're willing to give that a try at that time. Our current kernel is the latest 8.1 stable and it doesn't have that feature in it yet. Given that your machine is apparently VERY popular, getting this right is a major priority to us. So give the HWSetup settings a try, and if that works, I'd still like to get that experimental build to you as soon as I can get it all built. Also need to know if you went with 32 bit KNOS or 64 so I can concentrate on the one flavor for this test. If you're using the 64, did you by any chance try the 32 to see if it behaves? If we had the resources, I'd just go out and pick up one of these machines myself to work here but we don't have the luxury of "lab rat" budget right now.
|
|
|
Post by jerry on Nov 22, 2010 23:22:10 GMT -5
Hello Kevin, glad to hear I'm not on a sinking ship. I tried using the HWSetup feature and changed both of the settings you mentioned. Unfortunately, it didn't change anything. Still showing same screen with general protection fault. I didn't know about the HWSetup feature though. Makes accessing the BIOS easier than F2 when booting up. So, thanks for that. I am using the KNOS 64 bit version but I tried the 32 bit as well with the same results.
|
|
|
Post by Kevin McAleavey on Nov 23, 2010 0:16:25 GMT -5
Hello Kevin, glad to hear I'm not on a sinking ship. I tried using the HWSetup feature and changed both of the settings you mentioned. Unfortunately, it didn't change anything. Still showing same screen with general protection fault. I didn't know about the HWSetup feature though. Makes accessing the BIOS easier than F2 when booting up. So, thanks for that. I am using the KNOS 64 bit version but I tried the 32 bit as well with the same results. Had a feeling ... been digging at this all night, and it's definitely a "BIOS" problem, but what's in your machine isn't a real BIOS, there's a kicker chip which copies stuff into RAM memory and the OS is supposed to take it from there. BSD is aware of this on Toshibas but we have a Bronx handshake going on. Seems from what I've been researching that Linux has problems with it too. Thanks for following up on the remaining possibilities on your end, definitely something we' ve got to follow up on since we just ran out of straws. Toshiba has a different ACPI system from the others and I've been going back and forth with the BSD guys who are quite curious as to this one. Seems that there were problem reports going back to last December so this one's got their attention. It's going to take me a few days before we can figure out where to to from here, but this is definitely up there in priority now that we've caught us a fish. Heh. Hang in a few days, this week's going to be a bit insane on this end but will get back to you once I have an idea as to what I can build and have you test to see where we go from here. I *will* get this fixed, just ain't quite sure how at the moment. THANK YOU VERY MUCH for spotting this! The photo really helped as well in spotting that the problem on your end is that your "BIOS" is claiming to have a TV output when there isn't any. That's what's actually causing the problem. It's pointing to a non-existent device!
|
|
|
Post by musicman on Dec 12, 2010 11:34:38 GMT -5
Interesting about the Toshiba BIOS's....My sister is downloading the KNOS beta 3 at this very moment....going to install on a Toshiba Satellite; Tomorrow I will be fixing several problems for a friend who will be downloading KNOS,and I am planning to test KNOS on his machine .....also a Toshiba Satellite. [will also test on 2 laptops here - both Toshiba Satellites....they both need replacement hard drives].... and a computer-wise friend of my sister's is going to download the beta today, and help my sister [don't know the make of his laptop.] Anyway, I'll let them know of this issue, and that is is being worked on. [just realized - another laptop I was going to test KNOS on is ALSO a Toshiba....]
|
|
|
Post by Kevin McAleavey on Dec 12, 2010 18:16:06 GMT -5
Interesting about the Toshiba BIOS's....My sister is downloading the KNOS beta 3 at this very moment....going to install on a Toshiba Satellite; Tomorrow I will be fixing several problems for a friend who will be downloading KNOS,and I am planning to test KNOS on his machine .....also a Toshiba Satellite. [will also test on 2 laptops here - both Toshiba Satellites....they both need replacement hard drives].... and a computer-wise friend of my sister's is going to download the beta today, and help my sister [don't know the make of his laptop.] Anyway, I'll let them know of this issue, and that is is being worked on. [just realized - another laptop I was going to test KNOS on is ALSO a Toshiba....] Hopefully we've got that all fixed now, or at least as fixed as it's going to get with BSD until they release their 9 build next year. There were some ACPI/AE/APIC configuration options that were released about two weeks ago and we've thrown them into beta3 to see if that solves it. I'm expecting it will.
|
|
|
Post by jerry on Dec 13, 2010 18:19:08 GMT -5
Hello Kevin, This is the original poster that provided the pic of the laptop screen. Will KNOS 3 work on my Toshiba if I redownload it now? Thanks, jerry
|
|
|
Post by Kevin McAleavey on Dec 14, 2010 0:54:56 GMT -5
Hello Kevin, This is the original poster that provided the pic of the laptop screen. Will KNOS 3 work on my Toshiba if I redownload it now? Thanks, jerry Yes indeed! Should work now with changes to our bootup configuration. Same kernel and stuff as the prior beta3 thus we're not incrementing the version name, but new "smarts" that should work for you now. Same link as before. Let me know how it goes and sorry for the wait, I thought you'd already gotten word.
|
|
|
Post by jerry on Dec 14, 2010 18:34:00 GMT -5
Hi Kevin, Wondering if the MD5 hash will change with this new build? I'm downloading as I type. Thanks for getting this new one out to hopefully be compatible with my Toshiba. I'll report back after giving it a whirl. regards, jerry
|
|
|
Post by jerry on Dec 14, 2010 21:36:43 GMT -5
Well, I burned the new disk. The MD5 hash didn't match which I'd suspected since the file was different than the previous. Unfortunately, this new build doesn't boot up. It went further but then seemed to get stuck in a loop. Here's another pic of the laptop screen: Attachments:
|
|
|
Post by Nancy McAleavey on Dec 14, 2010 21:41:41 GMT -5
Hi Jerry,
Here's the updated hashes. Hope this is useful to you.
knos32-b3.zip ------------------------------------------------ CRC32: D43511A5 MD5: 9EC3B8E4255153B3B9E513FEE9EBCDA3 SHA-1: FC3725EF74A26BDAA4BA3763A43585881653C332
knos.iso -------- CRC32: C0F4B608 MD5: 73B337FF0FB81CF169B3DD913DB91CF8 SHA-1: 820D420DA77F60BD03A986EE518CDA70B5944621
knos64-b3.zip ------------------------------------------------ CRC32: 0989A5E6 MD5: D4B645C775790A46F10FB6275D53716B SHA-1: ACB7A2F5C07105F1A0BF492FAE0DDED6C48D89CD
knos64.iso ---------- CRC32: 1FAD847E MD5: 9DB23A265EB4F23D94E3841DF312E8E8 SHA-1: CA9E5C36221CAAC254E6F4C337F8C3229A5FBB7A
|
|