boot disks

[Steve Holmes]

Well, that's a possibility.  I don't remember the exact details just
now but the modules, .dep file and my kernel were probably never in
exact sync.  I think I had tried to use the supplied modules from
Debian and my kernel that I compiled and I bet that was never properly
matched up.  I could probably compile a new kernel, save off the
complete modules directory and make that available to the Debian
environment; maybe that would work.    Maybe I'll mess with Deb again
if it means getting the boot disks updated for others to use.  

On Wed, May 21, 2003 at 10:37:53AM -0400, Igor Gueths wrote:
> Actually, that probably had something to do with the libraries that wre
> linked into the 2.2.20 kernel binary. And you said you had no luck with
> any custom kernel you built yourself? That's very interesting. It could
> also be the modules.dep that didn't match with the modules on the Cd. Did
> you perhaps try building the necessary module for your ethernet card, and
> then making a bootable floppy or set of floppies with the module and the
> kernel itself?
> 
> May you code in the power of the source,
> may the kernel, libraries, and utilities be with you,
> throughout all distributions until the end of the epoch.
> 
> On Tue, 20 May 2003, Steve Holmes wrote:
> 
> > I went that route a while back and had a hell of a time getting
> > modules to load.  I got some basic stuff from the new Woody (3.0)
> > disks to come up on my machine but as soon as I tried to do anything
> > serious like setting up my network interface or just about anything
> > else, I kept getting unresolved module errors.  I could never seem to
> > get the modules to match up with the available kernels or any kernels
> > I custom built myself from my existing Slackware machine.  Also, the
> > default debian kernel is, I believe, 2.2.20 and Most other distros are
> > running 2.4.20 now.  Of course, Debian is updating regularly and
> > frequently so that might be old news by now.  Any how, I eventually
> > gave up on getting Debian to install on my box after fiddling with it
> > for over a week.  I went back to Slackware and had it up and running
> > within a few hours completely.
> >
> > On Tue, May 20, 2003 at 05:15:45PM +0000, igueths at attbi.com wrote:
> > > Hi. Potato is an outdated version of Debian. You should grab the latest stable
> > > binary isos form a mirror close to you, and use that to install your base
> > > system and other packages. However, you do want the kernel floppy included in
> > > the potato directory of the Speakup ftp site. Once you have your system up and
> > > running, you can upgrade your kernel. The other option is a network install.
> > > > Which disk image should I download for debian 2.2 potatoe so I can boot from the
> > > > floppy using speakup with a braille N speak?
> > >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup