PCBSD 9.0 Wireless Internet? - Page 3 - PC-BSD Forums

Cobalt · #21 04-12-2012, 03:43 AM

I'm not sure what you did wrong. The module loading at startup works fine on my system. I copied the rt2870_sys.ko file to /boot/modules and added the rt2870_sys_load="YES" (carriage return after that) to /boot/loader.conf and saved the file. Checking kldstat showed rt2870_sys

By the way, you don't need kdesu to run an application as superuser. You can just type su, enter your password, then enter the application. I think that's something I might have picked up when I was running FreeBSD. Sorry about that.

BBOSAK2143 · #22 04-12-2012, 11:45 AM

Will try that in a bit. Of course now is the atheros driver I listed above, but all listings are very similar to the Cisco one I was using. The modeswitch as I said above was a failure, so to continually have to remove the connector every time I boot up was not a great option.

Is strange with the modeswitch as the directions explicitly explained to install by config file, as I did. The computer put the file together into the makefile but when excecuting, plainly turned it down.

Also, I know I get detailed a lot times, but as I follow many posts, I also know others are reading so want to relay all information so all of us learn. This time around the "Kdesu dolphin" command was turned down.

Not a problem as long as you simply right click folder and open as administrator(su, alternatively) and enter your password. Very simple way for us old Windoze users(read Windoze on here and love the saying) Then simply drag the file to the administratively opened window/file.

Thanks for getting back to me will do as you say in a bit, if does not work have this long list of instructions I downloaded. Sounded great as it claims you don't have to reboot after changes and can just restart network. By hook or crook, this is my destiny to be on PC-BSD, I feel it! Take care and will let you know what works. Bob

BBOSAK2143 · #23 04-12-2012, 09:50 PM

The biggest thing I did wrong was editing with kword. What happened is, I was stupid and forgot to change the file extension. When a system boots and sees garbage like I gave it is no wonder it didn't boot.

Anyway when I re-installed last night I added the whole shabang, in a vain attempt to get to "Shambala"(3 Dog Night song am referring to this OS). Not sure if adding the Samba server and everything is helping the situation. I now have the information in the load.conf file with no problem, but also still no connection. Just moved a little higher up on kldstat is all.

The documentation I downloaded is apparently mostly for FreeBSD, which in some parts helps, but for this instance there appears to be some small differences. I am very suspicious that not having the WPA Supplicant filled in could cause my adapter not to show?

At this point, if I had some editor for those files in the ISO, I would find a way to load some stuff and get it cured from the get go. Alas, as of yet I don't know what editor is used so that option is only a dream. Personally, I would love to go under the hood(so to speak, as I am good with cars also) find some underlying problems and get some ideas how to fix them.

As this is what I live for to be working on software and OS's to make them great. I know my career is to be in BIT, but I want to go further. Anyway, when I get some more time I will search more for some answers, but any help you can offer will be greatly appreciated. Bottom line thanks again and you know I will keep fighting til I am connected. Bob

BBOSAK2143 · #24 04-13-2012, 07:48 PM

Am really out of ideas as have tried everything in the book, suggestions, websites and everything else. I have come to a conclusion(after trying 3 different adapters for wireless internet) that a wireless connection is as of yet not possible running this OS.

Second conclusion is ndisgen is not producing the information needed for the computer to use the new hardware properly. After, trying ndisgen a few times all it produces is a sys.ko file. When kldload command is initiated the module remains in the same place where it was produced.

The module is never moved to its proper place and all settings needed are never applied. To manually configure the entire device, requires core knowledge of the OS. If I understood exactly where things were going wrong, I would devise a way to fix it. Currently, I lack the knowledge it requires to fix it.

Hours searching thru documents on the internet and in system files have left me without finding the proper wpa supplicant.conf(file) to correct settings to fix situation. I have started a post about my theories on solving most issues, but at present I am unsure how to implement them.

I will continue to try solving my issues and others, but with my lack of knowledge, it will take time, which is not so available to me at present. Take care, I really appreciate all the time that was spent on my behalf and will also state I have spent many many hours.
I have lost a little sleep on it as I love a challenge, but unfortunately will have to cut it loose for a few weeks.

I am in sincere belief as I have mentioned about that this is a problem that needs to be addressed and solved by the OS developmental team. I am in hopes that some of my posts have been read by Application development that it might in some way lead to a fix for these problems. Once again will add that I am not trying to cut anyone down, only want to make a few suggestions that might help. Bob

Cobalt · #25 04-13-2012, 08:58 PM

Originally Posted by BBOSAK2143

Second conclusion is ndisgen is not producing the information needed for the computer to use the new hardware properly. After, trying ndisgen a few times all it produces is a sys.ko file. When kldload command is initiated the module remains in the same place where it was produced.

That's to be expected since it needs to be manually moved to /boot/modules

Ole Juul · #26 04-15-2012, 07:40 AM

Originally Posted by Cobalt

That's to be expected since it needs to be manually moved to /boot/modules

I wonder why he didn't want to do that.

BBOSAK2143 · #27 04-15-2012, 01:59 PM

Ole Juul, please don't do as I have done and not read everything through. Everything I have done doesn't work. Presently, I am developing theories as to why not? That is the post you are reading above. Module sys.ko(only one created) was moved into kernel folders, line added for boot process in loader.conf.

Since, all these actions do not work I developed a theory that ndisgen is not fully doing its job and is do to no internet connection. To create a file that runs internal commands for a computer system requires a lot of information. I theorize, for this system to properly use hardware there is at least 4 files created. Once again is all theory.

To manually find where all the information necessary to run my adapter is needed requires many hours. So I ask to please only offer relevant solutions, and fully read all posts and information. Bob

Ole Juul · #28 04-15-2012, 09:50 PM

Originally Posted by BBOSAK2143

To manually find where all the information necessary to run my adapter is needed requires many hours.

No it doesn't. Cobalt was kind enough to explain it. Just do it.

Bob, many people will see your posts, now and in the future. What you are doing does not make either yourself, nor PC-BSD look good. I sincerely suggest you consider your own reputation as well as the usefulness to others of what you are putting on the internet.

BBOSAK2143 · #29 04-16-2012, 01:06 PM

Ole Juul, consider the same for yourself. I have explained that everything Cobalt listed was tried and didn't work. This is a problem that requires time and development. PC-BSD is not the only OS affected by this problem. Is not a fault of PC-BSD, but is a fault of hardware manufacturer's failure to comply with systems other than Windows. So unless you have developed software to assist, please do not comment no more. Leave it open for those that have solutions or better ideas "PLEASE!"