Sorry. I really don't know. I was just throwing that out there. I got a BCM4312 somewhat working on my Dell Mini using the bwn driver. I have no idea what your error message is about though.
Should be able to edit my posts any day now! But I thought I'd update and say I don't think that was it. The keyboard just works sometimes and doesn't work others. I guess I'll just be living with it for now.
Not sure what's going on here, but I moved the line
linux_enable="YES"
above the lines containing the dbus, hald, and gdm initializations and it's working again, for now.
Unfortunately, I celebrated too soon. The problem has reappeared after installing the linux flashplugin. I can't figure out why that would break it. Something tells me it working was just a fluke. So any suggestions would really be appreciated.
I figured out that the keyboard works if I start gnome manually using only: /usr/local/etc/rc.d/gdm onestart I tried deleting the line gnome_enable="YES" from my /etc/rc.conf file and now it works! I now have gnome and my wireless working on my machine. Almost there!
After a long, painful process, I have managed to get FreeBSD and gnome2 installed from the ports tree. Now I can't get gnome to recognize my keyboard to accept my password at the gnome login screen. I have installed Xorg and enabled hald and dbus in my rc.conf file. What am I doing wrong? Thanks.
Thanks. I did try fsck_ffs -y but I did not know about any /lost+found. I've decided to reinstall one last time, but it's not looking good. I still get an RX decryption attempted error after my wifi starts. I have a feeling this card might not work with FreeBSD. I appreciate the response.
What would be the cause of this panic? I get the message:
Panic in ffs_valloc
and my computer just restarts. I can only boot in single-user mode. It may be related to a bwn driver or maybe an incorrectly unmounted USB. I really don't know, but I'm running out of ideas and patience.
I am receiving the message:
RX decryption attempted (old 0 keyidx 0x1)
using a Broadcom BCM4312 (Dell Wireless 1397) and the bwn siba driver. The message repeats many times even after I have logged in. I have searched the forums and seen others with this problem, but I have not been able to...
I'm sorry, but I don't quite understand. How would I make this custom script? Would I simply add the kldload command to it? Once I make the script, how do I get it to run at boot time exactly? Would it be a line in /etc/rc.conf? Thanks for your help.
I am trying to configure the wireless on my Dell Mini. I created a driver module bcmwl5_sys.ko that I can get up and running issuing the commands:
kldload /boot/modules/bcmwl5_sys.ko
dhclient wlan0
However, I have the following line in my loader.conf that causes kernel panic...
I'm sorry about all the posts. I managed to edit my /etc/rc.conf. I found that you can execute:
unload
at the loader prompt. After that I issued:
load /boot/kernel/kernel
boot
And I was able to boot after that. Hopefully, you've heard the last of me on this issue. Thanks!
Well, here I am again. I found out what command was crashing my system after a reinstall. So I'm back to the same problem. Luckily, I have a working USB and can enter the shell through sysinstall. Now I just need to be able to edit my rc.conf. Is this possible to do? I'm assuming that I can if I...
Sorry for double posting, but it appears my USB drive had become corrupted. I got a new USB drive and the reinstallation is working. So we'll save everyone some heartache and I'll just reinstall. I appreciate your help. I have a feeling you haven't seen the end of me! Thanks!
Exactly the same thing happens in single user mode. I can't get to a command prompt. I had recently edited my rc.conf, loader.conf, and wpa_supplicant where I had successfully started wifi using /etc/rc.d/netif start. I should have rebooted then! Now I can't get it to mount my USB where I could...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.