MacBook pro wireless problem Airport
24 July 2007
The new (July 2007) MacBook Pros have a problem with their wireless cards. The new cards are 802.11g and these have problems with slow data when connecting with some wireless hubs eg. Airport Express (which is the older 802.11n)
Really slow data rates, hanging pages. Memories of dial up.
This worked for me: using the Airport Utility application, in the Wireless tab, switch the Airport Express to "802.11b only" mode, rather than the more logical "b/g compatible".
I'm back up to speed. I think its supposed to be faster in 'g'. I don't know. WIreless so-called standards make my head hurt
Lots of stuff on the web and chatter, but no fixes yet.
Also, I've had the kernel panic too:
http://www.macmerc.com/news/troubleshooting/4072
Its when using wifi + no power adapter + airport station.
more posts in tech notes
- django.db.utils.DatabaseError: relation "django_content_type" does not exist
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 11.0px Monaco} I was getting an error while running unit tests and the test database was failing to be created.django.db.utils.DatabaseError: relation "django_content_type" does not existeventually found the problem. I had the following in a file that was imported to a models.py:hrd_type = ContentType.objects.get_for_model(HttpReferrerDomain)The idea being that it can just set the var when it loads up and after that its always there. But this means for creating a fresh database, the db is ...
- django has two classes called ValidationError
There is one in django.core.exceptions and one in django.forms.util Using that space age IDE Eclipse I have to say I'm enjoying how much time I've saved just going shift-command-O to organize and resolve all of my imports. But today I've just lost a few hours due to my ok-ing the wrong class. Quite mysterious it was, I raised a ValidationError (core exceptions one) in my form's clean() and watched as the try: except ValidationError: in django's full_clean() completely ignored my ...
- GDAL fails to build: `.rodata' can not be used when making a shared object; recompile with -fPIC
libtool: link: g++ -shared -nostdlib /usr/lib/gcc/x86_64-linux-gnu/4.4.1/../../../../lib/crti.o /usr/lib/gcc/x86_64-linux-gnu/4.4.1/crtbeginS.o .libs/libgdal.la.lnkscript -L/usr/local/lib /usr/local/lib/libgeos_c.so /usr/local/lib/libgeos.so /usr/local/lib/libexpat.so -L/usr/lib -lpq -lrt -ldl /usr/lib/libcurl.so -lssl -lcrypto -lz -L/usr/lib/gcc/x86_64-linux-gnu/4.4.1 -L/usr/lib/gcc/x86_64-linux-gnu/4.4.1/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/4.4.1/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/4.4.1/crtendS.o /usr/lib/gcc/x86_64-linux-gnu/4.4.1/../../../../lib/crtn.o -Wl,-soname -Wl,libgdal.so.1 -o .libs/libgdal.so.1.13.2 /usr/bin/ld: /usr/local/lib/libz.a(crc32.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/local/lib/libz.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[1]: *** [libgdal.la] Error 1 make[1]: Leaving directory `/home/crucial/tmp/gdal-1.6.2' ...
- installing MySQLdb on Ubuntu (mysql-python)
MySQLdb is the python support bindings for MySQL. Not that the name would lead you to beleive that. Its sourceforge page calls it http://sourceforge.net/projects/mysql-python/ which makes more sense. you need setuptools, which you usually already have: sudo aptitude install python-setuptools You need MySQL-devel to compile, but its not called that, its called: libmysql++-dev on Ubuntu sudo apt-get install libmysql++-dev download MySQLdb itself from: http://sourceforge.net/projects/mysql-python/ # the version you download will be more recent tar xfz ...
- Full index for tech notes
- django.db.utils.DatabaseError: relation "django_content_type" does not exist

