|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|
|||
Box Wont Boot After Editing /etc/hostname.athn0
I am having a bit of a problem installing a wireless card.
The machine has one wired ethernet and one wireless card (athn0) The athn0 will act as an access point for wireless devices. The first thing I do is install OpenBSD 5.2 and reboot. I have no issues until I edit /etc/hostname.athn0 The wireless card I have is a d-link DWA-566 which uses the Atheros which should work according to http://www.openbsd.org/faq/faq6.html#Wireless After reading this http://www.openbsd.org/cgi-bin/man.c...athn&sektion=4 I see that in order to get this working as an AP I have to edit /etc/hostname.athn0 to this Code:
inet 192.168.1.1 255.255.255.0 NONE media autoselect mediaopt hostap nwid my_net chan 11 What am I doing wrong? |
|
|||
First note that I do not use wireless
This is a typical case that normally should be reported to the OBSD developers on the OpenBSD misc mailing list. However, if you would report this, the first thing they would ask is to install the latest snapshot to see whether this problem still exists. So try the latest snapshot to see if the problem persists
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
I went out and downloaded the latest 5.2 iso and thats what I am using.
mirror.esc7.net/pub/OpenBSD/5.2/i386/cd52.iso I am not sure what is mean by the latest snapshot but I seem to have the latest iso 5.2 installed.(above link) I bought a different brand and will reinstall it tonight with a fresh install. Thanks for the help! |
|
|||
Quote:
If you are unfamiliar with the difference between the -release & -current flavors, study Section 5.1 of the FAQ. In essence, -release is the CVS tagged version of OpenBSD officially released every six months. -current is the head of the CVS tree where all current development takes place. The ISO's of 5.2-release comes from work last dated August 2012 (as I recall....). The latest snapshot of -current was built earlier today, & contains the changes jggimi mentions. In addition, downloading cd52.iso only downloads the bsd.rd installation kernel (on a bootable CD...). You will still have to manually download the corresponding filesets through ftp(1), etc. You will find that the install52.iso ISO image contains the bsd.rd kernel + all filesets; nothing else needs to be obtained. Lastly, note that the size of cd52.iso is significantly smaller than install52.iso. The reason for the difference is the absence of the filesets. More related information on what can be found at the mirror sites can be found in Section 4.3 of the FAQ. Last edited by ocicat; 10th January 2013 at 05:07 AM. Reason: clarify when OpenBSD 5.2 was tagged |
|
|||
Final comment of the differences between -release & -current flavors.
Determining which flavor of OpenBSD is installed can be found by looking at the output of: $ sysctl kern.version For users of -current, output will be similar to the following (I compile my own releases, hence the unfamiliar domain name...):: Code:
$ sysctrl kern.version kern.version=OpenBSD 5.2-current (GENERIC.MP) #107: Sat Nov 24 23:05:33 CST 2012 webmaster@build.pricklyfish.org:/usr/src/sys/arch/i386/compile/GENERIC.MP $ Last edited by ocicat; 10th January 2013 at 05:17 AM. Reason: clarity |
|
||||
EverydayDiesel, obtaining alternate hardware would of course circumvent the problem. Solving the problem, however, means going beyond 5.2-release, which is static and will never change. Please take ocicat's recommendation and review FAQ 5.1 -- it will help you to get a clearer picture of the tests and then the solutions outlined below.
Recovery
Solution Testing
Last edited by jggimi; 9th January 2013 at 11:30 PM. Reason: clarity, typo |
|
||||
FYI - earlier today, a different athn(4) related panic (uvm_fault) was reported to the bugs@ mailing list. The user, on -current, was using Host AP mode with the AR9271 chipset The panic occurred after a device association. A developer has already supplied a patch to the user to test.
I too have an athn(4) NIC, but with yet another Atheros chipset, the AR9285. I didn't attempt to recreate your problem as yours is specific to the AR9300 series. I may attempt to recreate the one reported to bugs@, when I have time. Last edited by jggimi; 10th January 2013 at 02:36 PM. Reason: clarity |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
CFEngine 3.4 adds XML editing and VirtualBox support | J65nko | News | 0 | 29th November 2012 02:13 PM |
ifconfig athn0 | marconi | OpenBSD General | 6 | 25th March 2012 02:39 PM |
proftpd start at boot wont work | jjjustjjjay | OpenBSD General | 9 | 28th February 2010 12:40 AM |
Freebsd server wont boot | rpadilla | FreeBSD General | 5 | 11th June 2008 04:09 PM |