|
|
Post by pharrisire on Mar 10, 2012 14:48:54 GMT -5
-runs fine from disc, made the stick fine and boots to it,
made the hard drive install and is running on it now.
I don't yet know if the 'MySettings' will work yet, as I am loathe to
reboot after spending all that time getting things the way I want
them as 'MySettings' hasn't worked yet for me on '9' so each
reboot is start-from-scratch.
One glitch is still no wireless, but at least on this one the cable works.
|
|
|
|
Post by Kevin McAleavey on Mar 10, 2012 19:50:01 GMT -5
-runs fine from disc, made the stick fine and boots to it, made the hard drive install and is running on it now. I don't yet know if the 'MySettings' will work yet, as I am loathe to reboot after spending all that time getting things the way I want them as 'MySettings' hasn't worked yet for me on '9' so each reboot is start-from-scratch. One glitch is still no wireless, but at least on this one the cable works. Squirt me the diagnostics on this one as well ... hopefully we can get that wifi going. As for the "My settings" I'll repeat what I posted on the desktop query here as well: I'll repeat this reply in each of the threads here regarding the "My settings" stuff since we're doing it differently this time around as mentioned in the documentation that came with the download ... When you go to use the "Backup app settings" from KNOS' System tools, KNOS will pop up a save as dialog with the name already preset as either "KNOS_PREFS" for 32 bit systems or "KNOS_PREFS64" for 64 bit systems. This shouldn't be changed since those are the names that KNOS will look for when it boots. It won't see any other filename. The reason for two different filenames based on the OS is in case you boot a 32 and a 64 on the same machine. There are differences in what's stored between a 32 KNOS and a 64 KNOS and so both filenames are separate in case both end up on the same disk to ensure we load the correct Flash and other things. The file needs to be saved in your "personal" area as well since that's where KNOS will look for it on startup. The drive ALSO has to be plugged in and available at bootup as well. If you've put KNOS onto a hard drive, that's where you'll want to store it. If you use a USB stick for your personal files, then there is OK too. The stick will take precedence over the hard disk, so if you save those settings to a hard disk and want to plug in a USB with settings stored, then the hard disk will be skipped and the stick will be read instead. We thought that would allow other users to have their own settings on separate sticks. But for it to work, the original filename the settings are stored with should not be changed form the KNOS_PREFS offered at backup time, and it has to go to the root directory of whatever media your personal files are stored on. Should work fine then. The original way we did things for the few who wanted to do this back in KNOS 8 is no longer the way it's done - we thought this method would be a lot saner for folks doing it for the first time. |
|
|
|
Post by pharrisire on Apr 2, 2012 14:08:40 GMT -5
Lenovo hard-drive install, 32bit diags on its way
|
|
|
|
Post by Kevin McAleavey on Apr 3, 2012 3:50:58 GMT -5
Lenovo hard-drive install, 32bit diags on its way Hi there! Well, looks like we're using the NDIS driver from Windows/Linux for that Broadcom, it's a BCM4311, and they're a bit squirrely. Looks like it's getting picked up and detected but isn't responding. So just for laughs and giggles, give this a try and let's see if it makes it wake up ... When the machine is up, go up top and hit Applications, Internet, wifi manager. When it opens, it'll probably only show "no signal" ... if ALL you see listed is "no signal, then try this: Click on the "Rescan networks" button. It'll take about 30 seconds to do this, and when it's done you'll see the button light back up again. Hopefully, your network will appear. If so, uncheck "no signal" and check the box next to your network. If there's crypto stuff (WEP, WPA, etc) then fill in the info. When you're done, hit the "Save and reconnect" button. That'll also take about 30 seconds before it's done. Close and you should be connected. If you SEE your network when it comes up the first time, do similar - uncheck "no signal" and check the box next to your network and fill in any security info you need to, then do the "Save and reconnect" button. Sometimes the radio won't wake up during bootup, though it's rare. Unfortunately, for those radios not directly supported by BSD (yours is one of these) about all we can do is suffer the limits of the drivers that Broadcom DID make available, and those drivers do have issues but eventually work if the radio is detected at all. Not much we can do until Broadcom decides that perhaps supporting BSD might be in their interest. Let me know how it goes ... we can try a few other tricks, but the above should do it. |
|
|
|
Post by pharrisire on May 5, 2012 6:35:53 GMT -5
""Click on the "Rescan networks" button. It'll take about 30 seconds to do this, and when it's
done you'll see the button light back up again. Hopefully, your network will appear.""
Done, several times, but no connection.
Neither band of the Netgear WNDR4500 is seen or received.
|
|
|
|
Post by Kevin McAleavey on May 5, 2012 23:42:21 GMT -5
""Click on the "Rescan networks" button. It'll take about 30 seconds to do this, and when it's done you'll see the button light back up again. Hopefully, your network will appear."" Done, several times, but no connection. Neither band of the Netgear WNDR4500 is seen or received. Looked at the last diagnostics you sent, I usually don't keep them but a copy of your email remained, so snatched the attachment again. The wifi card did start to respond, but somehow didn't connect. Something you can try in the meantime though is open a terminal, type in su at the first prompt, and when you get the second prompt, try typing in this: wifi_reset (hit enter of course) This is a brute force "kick it in the head" we included ... those BCM4311 chipsets are "interesting" at times, but the NDIS driver should have picked it up and at least. I'd hate to think that the only way to wake it up is to force it, but I'd be curious to know if that does anything. Then, if you manage to get it to say that it has connected, then try the Wifi Manager again and see if you can hook up to your wifi base station. |
|
|
|
Post by pharrisire on May 7, 2012 13:44:20 GMT -5
wifi_reset resulted in:
wlan0: no link ..................... giving up
wifi_reset: broadcom kicked!
|
|
|
|
Post by Kevin McAleavey on May 8, 2012 4:38:37 GMT -5
wifi_reset resulted in: wlan0: no link ..................... giving up wifi_reset: broadcom kicked! OK ... if that didn't do it, then the driver for that BCM4311 we obtained from Broadcom does not support that particular radio. Any chance of shooting me a fresh diagnostics file AFTER you've done that again so I can see what the hardware responses are from it? I'll see about getting the BSD folks to get after Broadcom for what it's worth for a possible update down the road. Too close to release now and we've got the very latest from Broadcom. Looks like they missed something.  |
|
|
|
Post by pharrisire on May 8, 2012 12:08:08 GMT -5
KNOS 32 diags after wifi_reset is on its way.
|
|
|
|
Post by Kevin McAleavey on May 8, 2012 23:46:58 GMT -5
KNOS 32 diags after wifi_reset is on its way. Something curious about your machine ... did you buy it from a discounter? Or used? Reason why I ask is that the wifi card in that machine shouldn't be that Broadcom, it SHOULD have been a Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) which would work fine. In checking with Lenovo, they were surprised as well. The card in there now fits the socket of course, but that's not the card they manufactured those with. According to the diagnostics, that card you have in there now has a firmware revision that belongs to an older Broadcom driver which is no longer supported by Broadcom because ... wait for it ... Broadcom made that card for ... DELL. That isn't a Lenovo card in there though. |
|
|
|
Post by pharrisire on May 9, 2012 11:39:17 GMT -5
Without digging for the paperwork, all I remember is getting it online and trying
to get the best deal for the highest rated at the time I was looking - probably
was comparing on amazon.
Is this item worth the time/$ to replace, or is it even replaceable?
|
|
|
|
Post by Kevin McAleavey on May 10, 2012 1:26:37 GMT -5
Without digging for the paperwork, all I remember is getting it online and trying to get the best deal for the highest rated at the time I was looking - probably was comparing on amazon. Is this item worth the time/$ to replace, or is it even replaceable? It's not all that hard, or expensive. Two screws on the bottom opens the panel, two more screws holds the standard sized pci-e card in place. Two plugin connectors for the antenna and away you go. Picture showing yours opened up below. But for the moment, hang on ... let us get the release out the door and set up and we'll get back to this. I was just curious as to how the Broadcom ended up in there instead of the original Intel card. That kinda explains it. Dealer was stuck with a Broadcom, knew the Intel was worth more, solved two problems for them at the same time. I'd be surprised if Lenovo had done that, but a dealer, not a surprise at all. Here's what's involved with a wifi swap on that machine as well as most others: Attachments:
|
|
