|
|
Post by pharrisire on Mar 10, 2012 14:49:28 GMT -5
Runs great as far as the OS is concerned from the disc, but not from
the stick (which works on the desktop).
However No wireless, and for some odd reason, no internet access even from
the cable.
|
|
|
|
Post by Kevin McAleavey on Mar 10, 2012 19:48:30 GMT -5
Runs great as far as the OS is concerned from the disc, but not from the stick (which works on the desktop). However No wireless, and for some odd reason, no internet access even from the cable. Sounds like the Toshiba isn't keeping track of where the stick is on its bootup unlike the others. Toshibas have been turning out to be "interesting" and not so much in a good way. Could you shoot me a copy of the diagnostics from 9RC on this one so I can look it over and see if there's something obvious about the bootup? DVD diags will be fine there. Also want to see what's up with the internets on there as well ... |
|
|
|
Post by pharrisire on Apr 2, 2012 14:36:30 GMT -5
Still can't get internet access to send you the diags from the Tosh, and it doesn't seem
to want me to copy the diags to a stick to move it to another computer to send to you
from there.
The wireless is Netgear dual band, and I've tried both Tosh's own cable as well as
the Lenovo's cable just to rule out that possibility.
|
|
|
|
Post by Kevin McAleavey on Apr 3, 2012 4:22:35 GMT -5
Still can't get internet access to send you the diags from the Tosh, and it doesn't seem to want me to copy the diags to a stick to move it to another computer to send to you from there. The wireless is Netgear dual band, and I've tried both Tosh's own cable as well as the Lenovo's cable just to rule out that possibility. Throw me the model number on that bad boy again. Some lappies shut down internet access unless it's woken up by Windows or LEFT in "on mode" when it's shut down from Windows. I've seen all sorts of strangenesses with Toshibas ... good news so far is at least yours boots!  I know I'm gonna get slapped by my superiors here for saying this, but Toshiba goes out of their way to ensure that nothing except for Windows will run on their toys. Their tech people have been very admant about that to me when I've contacted them. But let me see if I can research the model and find out what the problem might be. Pity we can't get the diagnostics on that, but I'm actually surprised it's booting at all. Toshiba would be my own absolute last choice for a machine, but that doesn't help anything here.  |
|
|
|
Post by pharrisire on Apr 3, 2012 14:11:02 GMT -5
I already had the Lenovo as the bottom of the barrel, but now I guess
the Toshiba bumps it up a notch....
Manufacturer: TOSHIBA
Product Name: Satellite Pro C650
Version: PSC2FU-00E003
Processor: Intel Core i3-2310M CPU @ 2.10GHz 64 bit
BIOS VendorL: INSYDE version 1.20 firmware version 1.40
|
|
|
|
Post by Kevin McAleavey on Apr 3, 2012 20:13:08 GMT -5
I already had the Lenovo as the bottom of the barrel, but now I guess the Toshiba bumps it up a notch.... Manufacturer: TOSHIBA Product Name: Satellite Pro C650 Version: PSC2FU-00E003 Processor: Intel Core i3-2310M CPU @ 2.10GHz 64 bit BIOS VendorL: INSYDE version 1.20 firmware version 1.40 I've been a big fan of Lenovo ever since the IBM Thinkpad days. In fact, I'm typing this on an old T30 right now. Lenovo's done some strange things in recent years and have put some Broadcoms in their more recent toys, but you can always plug in a Netgear or Atheros and all is well with the world. OK ... turns out that the C650 and C655's are designed for Windows 7 and have no actual BIOS. All of the "hardware" settings are actually a UEFI-based control panel thingy in Windows and supposedly no actual "BIOS setup" that can be gotten into at startup. From what I understand, they don't do Linux well either. The problem is that wifi, net and USB support are all handled within what is called ACPI, but it is not accessible. All settings are handled by Windows itself and so there's nothing for KNOS to "see" when booting up. While we can build a UEFI-based KNOS for such machines, it prevents that design of KNOS from booting on BIOS-based machines and therefore, we can't do both in one version. It's an either/or thing. In the Windows "HW SETUP" screen for that bad boy, there's a USB tab. In that tab is an option for "Legacy USB" ... for laughs and giggles, you might want to set that for the opposite of what the setting is now (you can always put it back the way it was in Windows after trying this) and see if the USB will wake up for KNOS after trying again after changing that. But I suspect the problem is that the "ACPI" stuff is not available at boot and that won't make any difference. I'd LOVE to see diagnostics out of that if at all possible - Toshiba's design kinda traps you into Windows and that explains why they're so adamant about "Windows only" on those toys. I'd like to fix that. Heh. But Toshiba's proprietary ACPI design controls wifi, net, USB, all those items listed in that "HW Setup" and that appears to be the root of the problem - trying to figure out how to get around it. If we had one of those toys here, I would have already beaten the truth out of it! |
|
|
|
Post by pharrisire on May 5, 2012 6:46:44 GMT -5
""In the Windows "HW SETUP" screen for that bad boy, there's a USB tab. In that tab is an
option for "Legacy USB" ... for laughs and giggles, you might want to set that for the
opposite of what the setting is now""
Tried both ways, many times - no change.
Won't boot from stick, no wireless, and
no internet access even from the cable.
|
|
|
|
Post by Kevin McAleavey on May 5, 2012 23:43:06 GMT -5
""In the Windows "HW SETUP" screen for that bad boy, there's a USB tab. In that tab is an option for "Legacy USB" ... for laughs and giggles, you might want to set that for the opposite of what the setting is now"" Tried both ways, many times - no change. Won't boot from stick, no wireless, and no internet access even from the cable. Looks like that Toshiba isn't going to happen then. Toshiba officially does not support anything other than Windows on those lappies, and I've been reading that even getting Linux going on it is a whole wad of manual dexterity for the same result in most cases. If none of that is coming up, then its internal BIOS is locking out any attempts to communicate with it to find out where the hardware is to talk to, sorry to say. That was my last hope there, guy. |
|
|
|
Post by pharrisire on May 7, 2012 13:46:57 GMT -5
Tried the "wifi_reset" on the Toshiba running from disc, and it gave absolutely
no response at all, it completely ignored it.
|
|
|
|
Post by Kevin McAleavey on May 8, 2012 4:33:54 GMT -5
Tried the "wifi_reset" on the Toshiba running from disc, and it gave absolutely no response at all, it completely ignored it. And here, it seems pretty clear that their EFI BIOS isn't letting us talk to anything. If you can shoot me diagnostics after trying that again, let's see what we're getting. There were some kernel patches that will be in the release, but the BSD folks are saying they've been completely uncooperative. I feel real bad about this, two fails. Linux has been having adventures with these as well but I suspect that once we get the release out, we may be able to do some tweaks that might work around this somehow. Did it work with the 8 version that had no Toshiba BIOS support at all? In 9, we have an ACPI-TOSHIBA module that's supposed to work with some of them, thus my question here. |
|
|
|
Post by pharrisire on May 8, 2012 12:25:03 GMT -5
I wish I could, but the Toshiba has not been able to get online, neither wireless nor cable, since KNOS9 - as well as its not booting to the same stick that the desktop does boot too. The only way KNOS9 runs on Toshiba is from disc, but as there is no internet connection I can't send you the diags (and it won't let me copy the diags to a stick to move it over to desktop to send from there). Don't let Toshiba whup us - get your KungFu Mojo on and beat this two-bit punk Toshiba into submission!! |
|
|
|
Post by Kevin McAleavey on May 8, 2012 23:57:13 GMT -5
I wish I could, but the Toshiba has not been able to get online, neither wireless nor cable, since KNOS9 - as well as its not booting to the same stick that the desktop does boot too. The only way KNOS9 runs on Toshiba is from disc, but as there is no internet connection I can't send you the diags (and it won't let me copy the diags to a stick to move it over to desktop to send from there). Don't let Toshiba whup us - get your KungFu Mojo on and beat this two-bit punk Toshiba into submission!! I'll have the BSD guys get back after them ... many Toshibas would never even boot to begin with without Windows on them. Everyone I've dealt with has said Toshiba is horrible to deal with and despite undercutting others on price, don't know anyone who's ever bought a second Toshiba. |
|
|
|
Post by pharrisire on May 10, 2012 15:06:24 GMT -5
|
|
|
|
Post by Kevin McAleavey on May 14, 2012 0:21:46 GMT -5
Actually, we've done a LOT of hardware ... we've run a few Toshibas through here which is why KNOS boots at all on most of them now. Perhaps one of the roughest machines were those Panasonic "tough books" that the military and law enforcement use. They're TRULY squirrely. Problem is that the only way to deal with oddballs with bad BIOS problems is to actually HAVE one of those machines in our lab. Then we can debug the BIOS and build our OWN BIOS file that KNOS can read instead of the defective BIOS. We've done plenty of those for corporate/government use by borrowing one of the machines long enough to build that file and then construct a custom version of KNOS for those machines. Works great. Only problem is getting our hands on one of them. For large orders of a custom version, we can even work with the manufacturer so long as we have a sample of the machine in question to wring out any issues and make use of BSD's ASL, acpidump, and IASL tools. From that, we can then finally build a custom AML file which will allow those machines to work as properly as if they'd had their BIOS manufactured bug free. When Windows is installed on a machine with buggy BIOS, it will drop to a generic driver and perhaps ask you to insert an "install disk from the manufacturer" which has the manufacturer's custom-built Windows driver. I'm sure you've encountered that. When the manufacturer doesn't have a driver file for BSD, that's when we have to go and do a custom build either working with the manufacturer's engineers OR borrowing the machine in question long enough to make an AML file ourselves and do a custom. But when the manufacturer refuses to cooperate or fix their errors, we have ways to work around them. It's just a bit time-consuming on our end. |
|
