I am back at trying to learn Linux (3rd try) and getting frustrated. I probably have the wrong computer to learn Linux. I have a Thinkpad T22. I learned from this forum that it may be a challenge to get my Linksys wireless adapter working because of Texas Instruments ACX 111 54Mbps Wireless Interface.
I have antix 13.2 loaded and now it boots to a black screen. I worked through the install, partitioning my hard drive and installing antix via a live CD. It worked fine until I rebooted, now I cannot get to the desktop. It seems that it is booting fine, then the black screen.

Has it got a"non-free" graphics card such as AMD or Nivia? If it has you need to run smxi in a non-X environment and install the drivers.

i.e. Reboot to a non-X screen, log in as root, type smx,i and answer all the questions that appear. Of course, this could be difficult if you have no screen output at all.

I tried a couple more times and now it boots to the desktop screen and appears to be working. Internet access via a ethernet cable works as well. So, I guess I will try getting wireless to work.

That's great news! Good luck getting the wireless working.

Works out of the box for me in AntiX with a Atheros wireless chipset


========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.ebay.com/itm/D-Link-WNA-1330-Wireless-G-Cardbus-Network-NoteBook-Adapter-/151093733633?pt=US_Laptop_Network_Cards&hash=item232de36901"
linktext was:"http://www.ebay.com/itm/D-Link-WNA-1330 ... 232de36901"
====================================


You can get your netgear working. You just have to learn some new tricks to make it so.
D.O. gave you the Debian link for that chip and the site explains firmware install.
Up to you to implement the install.

As far as the T22 goes. I own a A22M and T23 and use Belkin F5D7010 ver. 6 pcmcia wireless cards on them with a raylink chip and they work out of the box also. You have to be careful buying Belkin F5D7010
because they inserted different wireless chips depending on the .ver number. That is why I mentioned .ver 6 in my post.

Good Luck. Just take into account the hardware is old and some flaky ness can be attributed
to hardware age and intermittent failure can just be a cdrom drive not working correctly one time.

Now that antiX is running wireless, I would like to find a solution to this problem. I am running a dual boot antiX and W2k on a T22 laptop. If I boot directly into antiX, it stalls out to a blank screen. If I keep trying eventually it will completely load. However, if I boot W2k, then do a restart it will completely load antiX everytime. Any ideas?

I had a similar problem on an old laptop, it was because the booting process wasn't having enough time to find the root filesystem. Try adding rootdelay=10 to the grub kernel line.

Is the startup text still there during boot?
If it is then I would say that the computer is competing as to what driver to use for the graphical display. Seeing how it seems to have worked no problem with the live cd, I would consider that there are two options.
1) build an xorg.conf that uses vesa as the driver (I believe that the default option on the Live cd is"safe" and"safe" uses the vesa driver.... could be wrong)
2) try to install the proper driver and remove / disable the improper one.

Building an xorg.conf is stated in many places here, but I can write it again for you if you choose #1. Smxi/sgfxi as Alanarchy suggested using should work for #2. We can give you our opinion on what direction to go but we would need the graphical put off inxi. This can be found through the control center or by running inxi -G from terminal

Edit:
Looking at your other post it seems that this has already been done.
For reference in this thread :
Graphics: Card: S3 86C270-294 Savage/IX-MV X.Org: 1.12.4 drivers: savage (unloaded: fbdev,vesa) Resolution: 1024x768@60.0hz

Edit 2:
It seems more people have had similar issues to this with the use of the savage graphics. I am not to familiar with it, but that is not to say that I cannot (and will not) help. All this is saying is that if the live cd display works fine for your liking I would go the #1 route. Otherwise I will refer you to this post
post33519.html#p33519
Or
post31047.html#p31047

fatmac,
I am still pretty much a newbie at this. Could you walk me through that process?

Dave,
Startup text is there up until a line about wicd, then the screen goes blank and the computer just sits there. Everytime I do a restart from a W2k boot up it does fine. I don't touch the computer until It asks for my password.

When grub starts it shows its menu, at this stage press 'e' to edit, then 'e' to edit the kernel line, likely it is highlighted, add to that line, press return, then press 'b' to boot the system using those changes. If it all works, when the system is up & running, as the root user, or use sudo, open a terminal, then type Alter the kernel line as you did to start up & save the file. It should then work OK next time you boot up.

There is the line I added it to, but it did not make it boot like it should.

It was worth trying, sorry it didn't work for you.

Any other ideas out there? It is a pain booting up W2k, then doing a restart. Following that method, antiX boots everytime.

Maybe there are two graphics chips that needs to be switched in the bios so that only one is used.... but that is quite a shot in the dark as I do not see any of the results for the other 2 options I posted above. I am assuming that neither method worked nor the solutions for the savage chip set as posted in other sections of the forum. Some of which I have linked to but not all.

1) build an xorg.conf that uses vesa as the driver (I believe that the default option on the Live cd is"safe" and"safe" uses the vesa driver.... could be wrong)

I am still pretty much a novice and am not sure I fully understand the above.