Re: [vox-tech] Boot problem

[John Wojnaroski <castle@mmMAPSinternet.com>]

OK, Jim,  I found a driver by goggling over to a wikipage on 
ndiswrapper. It might just work wirh 2.6.8. it's worth a try...

To autoload the ndiswrapper at boot time try

"# ndiswrapper -m"  which will write an entry to /etc/modprobe.conf

Thanks again
JW


John Wojnaroski wrote:

> I have 2.6.8 running but need to install the ieee80211xxx module and 
> ipw2200xxx driver for the Intel wifi hardware in the laptop. To do 
> that you need the source code that created the running kernel to 
> compile with the correct headers and such as well  the object files to 
> load and link correctly.  The 2.6.8 kernel boots just fine and I have 
> the kernel source for 2.6.8-2-386.
>
> Have not been able to find a compiled version of the Intel driver.  
> The debian apt/install system is great. Unfortunately, it is 
> impossible to provide packages for *everything*.
>
> would ndiswrapper work with the Intel 2200 chipset? I did not see it 
> in the list of supported cards and since Intel provides the source for 
> a native Linux driver (ipw2200-xxxx) that is probably the preferred 
> way to go. And since the chip is built into the laptop, changing cards 
> is not an option.
>
> Once I get by this boot problem, I suspect there will be a whole new 
> set getting the wifi to work ;-)
>
> Thanks
> John W.
>
> Jim George wrote:
>
> > After hours of googling I came across a site that helped me to update 
> > my kernel.  Here is the part that really helped me out:
> >
> > ...as quoted from 
> > http://www.howtoforge.com/forums/showthread.php?t=29 ....
> > "Why not install with 2.4 and then use apt-get command to 
> > download/install 2.6 kernel? That is what I did. Piece of cake.
> > # apt-cache search kernel-image
> >
> > It will then list what available and choose the latest kernel for 
> > your hardware (AMD K6, K7 or Intel i386, i686)
> >
> > Use this as an example: kernel-image-2.6.8-1-686
> >
> > # apt-get install kernel-image-2.6.8-1-686
> >
> > Then reboot
> >
> > # init 6
> >
> > Login and make sure you have the latest version
> >
> > # uname -r
> >
> > You're done."
> >
> > For a newb like me it was painless.  You will have to dig and find 
> > processor info though before you search.
> >
> > I too am tinkering with a wifi card using 2.6 kernel, ndiswrapper, 
> > and other things.  I got it to work but am having a hard time making 
> > it auto on hard boot ( btw, I have imput
> > auto wlan0
> > iface wlan0 inet dhcp  wireless-essid linksys
> > in my /interfaces file but still no go).
> >
> > Cheers,
> > Jimbo
> >
> > On Monday 04 September 2006 01:34 pm, John Wojnaroski wrote:
> >  
> > > Hi,
> > >
> > > Before posting to one of the linux forums, thought I might give it a 
> > > try
> > > here, the response here is so much faster and better.
> > >
> > > Building a new kernel 2.6.10 to set up my laptop for wifi. Linux 
> > > version
> > > is debian sarge (stable). The install was pretty much "out-of-the-box"
> > > using the "Desktop" packages option
> > >
> > > At boot the following msg occurs , followed by the usual "kernel panic"
> > >
> > > "modprobe: FATAL: Could not load /lib/modules/2.6.10/modules.dep: No
> > > such file or directory"
> > >
> > > some data and info follows:
> > >
> > > rampart:/# cd /lib/modules/2.6.10
> > > rampart:/lib/modules/2.6.10# ls
> > > build modules.alias modules.dep modules.inputmap modules.pcimap
> > > modules.usbmap
> > > kernel modules.ccwmap modules.ieee1394map modules.isapnpmap
> > > modules.symbols source
> > > rampart:/lib/modules/2.6.10#
> > >
> > > indicates the modules have been built and installed (listing of kernel
> > > directory omitted for brevity)
> > > symlinks build and source point to the correct linux directory, 
> > > although
> > > I don't believe this is an issue at boot time
> > >
> > > In the kernel ramdisk and initrd are enabled in block device section of
> > > .config
> > >
> > > Something in /etc/modules.conf ?? (understand this file is generated
> > > automatically and not to be hand edited)
> > > Kind of stumped. never had this problem building kernels in the past.
> > >
> > > Any thoughts or suggestions where to look would be appreciated
> > >
> > > Thanks
> > > John W.
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > vox-tech mailing list
> > > vox-tech@lists.lugod.org
> > > http://lists.lugod.org/mailman/listinfo/vox-tech
> > >   
> > _______________________________________________
> > vox-tech mailing list
> > vox-tech@lists.lugod.org
> > http://lists.lugod.org/mailman/listinfo/vox-tech
> >
> >
> >  
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech