Search results

script is attached to the first post the driver has been updated by intel: http://downloadmirror.intel.com/18404/eng/ICS_Dx32.exe the gen_ndis_ipw.sh won't work with this version, i'll try and update it asap P.S. iwi driver should work with 8.0 generic, with a compiled kernel there are...

same problem here with ghostscript8-8.70 (done make distclean/clean/rmconfig for ghostscript and freebsd-doc-en)

iwi is working with a simple wpa AP, in GENERIC, with a kernel compiled with some optimizations there are interrupt storms, seems sometimes ndis work good without interrupt storms also on optimized kernel.

i've tried to update the port version is 0.4.12 and seems like isn't working with actual pidgin port, i've tried to update to 0.4.20. i've managed to get Makefile/distfile updated, make/gmake fail with .po files: gmake[5]: Entering directory `/usr/home/ocean/pidgin-musictracker-0.4.20/po'...

mine took a few days when i cleaned it with alcool (i think something was in short-circuit, because some keys weren't working until it fully dried).

i called it gzip cause i've tar-gzipped it tar -czf gen_ndis_ipw.sh gen_ndis_ipw.tar.gz it was already specified in the code to use tar: howewer i've changed "gzip" with "tar". thanks. regards ocean

i think the problem is that you are reading from buffer without counting "\n" that will be read from the next scanf (buffered input) just change the scanf like this scanf("%100s%*c", book[i].author); "%*c" tells scanf to jump one character (the newline) :)

have you tried getting wlan interface up? http://forums.freebsd.org/showthread.php?t=8785 howewer for me iwi isn't working good :)

maybe it's not a question of posts count :e

i've done this on FreeBSD 8.0 so it could change a little for other versions. UPDATED 12/10/2009 i've updated the how-to, there were some errors before, now it should be fine i think. i've tried to keep this howto as simple as i can but please: read ALL the post, and understand what you are...

I forgot to say (sorry for double posts i can't edit) most of the topics are covered in the freebsd handbook. if you didn't read it, you should, it's the most comprehensive guide for freebsd, almost everything to get started is there ;) regards ocean

what you mean by black screen? a console or really a black (unusable) screen? if you need some graphic environment just read manual if you need a (more-or-less) quickly ready desktop environment you can install gnome or kde. (i prefer gnome) read the manual aragon linked to install X11...

great! also youtube-dl + {player of your choice} can do the job :D

I'm using freebsd 8.0, gnome installed from ports (installed gnome2-lite and added most of the gnome-programs excluding user-share and evolution) I cannot see any statistics in gnome-power-statistics gnome-power-statistics --verbose: TI:01:03:27 TH:0x2a32db80 FI:egg-debug.c...

nice idea but rather useless. could be usefull to specify what's the current freebsd distribution in use (i always forget to include it when asking something :P). howewer those kind of info can be also written in the signature for who think it's useful :) just my two cents. regards ocean

with ndis everything seems to work good :)

yes, thanks :) howewer i need to change often network (moving from home to university and such), so i prefer to do everything manually or through some little scripts. found also how to fix routing for dns after going from wireless (dhcp) to ethernet (static) /etc/rc.d/routing restart fixes it.

FreeBSD 8.0-RELEASE with recompiled kernel (same problems with generic). i didn't put -Dndis in wpa commandline now's working fine (i'm writing from the wireless right now :PP) howewer i was referring to ndis(4) device driver. thanks :beergrin there's only one thing that seems strange...

Hi, i've got some problems with iwi. I try to connect to a PEAP/MSCHAPv2 network network={ ssid="ssid" key_mgmt=WPA-EAP eap=PEAP identity="login" password="pass" phase1="peaplabel=0" phase2="auth=MSCHAPV2" } this kind of config worked just fine under linux...

seems power manager works fine instead Battery Charge Monitor 2.28.0 applet always shows "running on AC power" so the problem is with that. regards