Categories
- Databases (12)
- MySQL (8)
- Oracle (4)
- PostgreSQL (3)
- SQL Server (3)
- SQLite (1)
- General Info (8)
- Hardware (7)
- Hosted 64-bit Software (22)
- Lightning Plug-In (3)
- Xine RPMs (20)
- Linux (22)
- Audio / Video (3)
- Internet Apps (11)
- Office Productivity (4)
- Printing (1)
- Red Hat / Fedora (3)
- Samba (1)
- White Box (3)
- Wine (5)
- Wireless Support (8)
- Programming (26)
- C# / .NET (4)
- Mono (2)
- C++ (1)
- JavaScript (1)
- PHP (9)
- SQL (3)
- PL/SQL (1)
- Web Services (1)
- WordPress (13)
- Plug-Ins (7)
- C# / .NET (4)
- Projects (1)
- Security (3)
- Web Servers (6)
- Windows Open Source (1)
- Databases (12)
Archives
- January 2012 (1)
- November 2011 (1)
- October 2011 (2)
- September 2011 (1)
- August 2011 (1)
- May 2011 (1)
- September 2010 (2)
- August 2010 (3)
- March 2010 (1)
- April 2009 (1)
- February 2009 (1)
- January 2009 (1)
- October 2008 (2)
- June 2008 (3)
- May 2008 (1)
- March 2008 (4)
- January 2008 (2)
- December 2007 (2)
- November 2007 (1)
- October 2007 (1)
- September 2007 (2)
- August 2007 (5)
- July 2007 (2)
- June 2007 (2)
- May 2007 (3)
- November 2005 (1)
- August 2005 (2)
- June 2005 (3)
- September 2004 (7)
- August 2004 (2)
- July 2004 (8)
- June 2004 (10)
Category Archive: Wireless Support
Subcategories: No categories
ndiswrapper May Have Issues
We’re speedily working towards a Friday deadline at work, so tonight I had some analysis work to do on some COBOL code. Great, I thought, I can use my VSlick setup under wine. I moved my computer from the living room back to our now-empty bedroom (soon to be nursery), and booted it up. Kernel panics galore – never got past the network stuff. When I booted to Windows, I found that the wireless network didn’t reach that far, and I’m guessing that the ndiswrapper folks haven’t tried their driver a lot with a wireless card, but no wireless network. Once I get past that, I may grab the dumps from these kernel panics and see if the developers need them to see what went wrong. So, for tonight, I had to use WXP (in which I actually had to disable the wireless connection – seems Windows doesn’t handle a barely-there wireless connection much better than Linux).
The diagnostics I ran last night never found anything – they ran for about 10 hours. I suppose I’ll just have to wait until I have problems again, then run it right then. Another person from the WBEL users list suggested I check the way I have my hard drives set up; he thinks that a 2GB drive slaved to a 20GB drive may be causing conflicts, which would cause freezes or panics.
Success with Wine & Diagnostics
At work, we use an editor called Visual SlickEdit (VSlick). It’s got a lot of features, and supports color-coding for many different languages. I decided that I’d give wine another shot, as we only have the Windows version of this program. I installed wine and winesetuptk, used winesetuptk to configure the installation, then ran the installation program. Everything installed, and the program ran up to a point, when it started complaining about a missing DLL. I booted to WXP, found the DLL, copied it to the FAT32 drive, rebooted to Linux, and copied the DLL into the “fake windows” system directory. Soon, it was working great! I can’t believe it – success with wine!
I also have made little headway towards getting Apache and MySQL to working. I changed the process that Apache uses to run as “summersd”, and I was able to see pages (although any pages that relied on a database didn’t work). I still haven’t figured this one out yet…
I’m still getting kernel panics from time to time, and it seems to be whenever I access networking. A suggestion from one of the folks on the WBEL users list was to download the Ultimate Boot CD, filled with diagnostic programs. I downloaded it, burned it, and ran some memory checks. Those checked out, so I’m going to run a “CPU Burn-In” program to see if it can detect errors from the CPU. It runs for up to 7 days, but I think I’ll just run it overnight – folding@home didn’t take nearly that long to crash it before.
DVDs Are Back & Conflicting Wireless Networks
I downloaded xine and xine-ui again, just to get the freshest stuff. Compiled first time, worked first time. I must be learning how to do this stuff! I also did a “yum update” to get the most recent version of everything, and I upgraded ndiswrapper from .8 to .10.
I moved the computer into another room, and found that I was now getting conflicts on my wireless card. After some research, it appears that I’m picking up my next-door-neighbor’s wireless signal as well. I renamed our wireless network, and configured the cards to use only that network, and those conflicts went away.
Back to WBEL
Today, I reinstalled WBEL 3.0. I was able to compile ndiswrapper (as I kept that on my FAT32 drive), and get the network card working smoothly very quickly. (In fact, it seems to be more reliable under Linux than WXP!) With the network up, it was easy to download Firefox, Thunderbird, and OpenOffice, and installing them was a breeze. (I decided to put them under /opt this time, trying to stick with the FHS.) I decided to mount my FAT32 drive under my home directory, as /home/summersd/drive_d. E-mail works fine, but Apache gives me a 403 (Permission Denied) error. MySQL doesn’t seem to be working either – I’ll have to play with that later.
A Month in Summary
Well, the last month has been interesting. I was able to get my Windows and Linux installations synchronized by creating a mount point for my second drive under /mnt/drive_d . Under that, I created a directory called /thunderbird for my e-mail, and moved my e-mail and newsgroup folders over there. (The first time, I missed the “newsrc” file, which is important – it tells what newsgroups you’ve subscribed to and which messages you’ve read.) Under Windows, I pointed it to “D:\thunderbird\pop3.knology.net”, and under Linux, it was configured to “/mnt/drive_d/thunderbird/pop3.knology.net”. I then moved the “wwwroot” directory from “C:\Inetpub” to drive D:, and pointed IIS to the new location. Under Linux, I did something a little different. As “root”, I deleted the directory /var/www/html, and instead created /var/www/html as a symbolic link to /mnt/drive_d/wwwroot (the actual command is “ln -s /mnt/drive_d/wwwroot /var/www/html”). That worked great as well.
MySQL was more complicated, but I was eventually able to get it working as well. I created the directory “D:\mysql\data” for the data, then configured /etc/my.cnf under Linux to look at “/mnt/drive_d/mysql/data”. I kept getting “Could not connect to server using socket /var/lib/mysql/mysql.sock”. After some digging, it appeared to be a permissions problem. All the documentation said that the default socket was /tmp/mysql.sock, so I changed my.cnf to point there instead, restarted mysqld, and it worked! So, I have no idea what a Unix socket it, but I know that now I have one!
I was also able to get DVDs playing using xine, compiling it myself, and using libdvdcss, I can even watch commercial DVDs. I’m really impressed with xine – it handles all kinds of media out of the box, including DivX and up to version 8 of WMV files. You can add codecs to it as well, to support almost anything you want to do from an audio or video perspective. Compiling the player took around 20 minutes, and compiling the front end took another 5. And, it was simple – download the .tar.gz file, do “tar xvfz [name].tar.gz”, “cd [name]“, “./configure”, “make install”. The “./configure” script is the key in the whole process – it looks at what you have installed, and creates make files that will work with your compiler.
Everything started going south, though, when I started having freezes. Eventually, I got to where I could not boot without a kernel panic, and then boot errors (which I detailed in this e-mail to the WBEL user’s list. Encouraged by my success over the past month, I decided to return to WBEL – it’s supposed to be more stable than FC2, and I bet that I can get ndiswrapper, the dual-booting web server, the common e-mail, and maybe even some other stuff working again.
Sour Milk Is Right!
A user wrote back and suggested that I try a driver from SourMilk.net, which is an “adm8211″ driver project for Linux. When I downloaded it and started to compile it, I quickly became aware that it hoped I was on the 2.6 family of kernels (which is what the Fedora Project, and several of the newer distributions, are now using). WBEL 3.0 uses the 2.4 kernel, which is more established, but is beginning to drop off as most folks start developing for 2.6. Anyway, there was a 2.4 make file, but it was labeled “experimental.”
That pretty much describes how I spent my time this evening – experimenting. I have virtually no experience with large-scale C projects, and I got many, many compile errors. I tried tweaking the make file, to no avail. I don’t fault the driver, as it said up front that it is really targeted to 2.6. I may end up downloading a 2.6 distribution and trying it out.
A Cry for Help
I tried a few other things to make that module work, but nothing seemed to help. It’s also very difficult to download and try new things when you can’t get to the Internet to download them. I also posted a message to the WBEL user’s list, and rather than go into that detail, that message can be found here.