Replying to myself.
I filed bug 275075 about the speakup kernel image not getting installed.
The bug should be fixed in the next build of the access floppies. It
took the developer no time to fix it. Just goes to show I'm still just
a user and not a programer.
Kenny
On Tue, Oct 05, 20
It installed the speakup kernel but I had to do the install as expert so I
would get a choice.
--
Cheryl
"Where your treasure is, there will your heart be also."
Good to hear. That means the problem of not installing the speakup
kernel is the only remaining problem. Did the Sarge cd you used install
the speakup kernel or the kernel image that matched your cpu?
Kenny
On Tue, Oct 05, 2004 at 11:36:33AM -0500, Cheryl Homiak wrote:
> I do know tha
I do know that when I installed with the first cdrom of the sarge cds I
burned )(I believe they were the week of September 20) with the expert
boot I was given a choice of a bunch of kernels and speakup was one of
them. So it is present in the mainstream install media.
--
Cheryl
"Where your tr
Hi. It looks like the problem with the nic drivers has already been
fixed in the latest images from the Debian site. I don't think I can
fix the kernel image problem. I'm just going to file an installer
report about it and quit. I've looked through the code I have from svn
and don't see where t
It's good that you're fixing this.
It also can be worked around by using the net.img floppy and loading it
when prompted.
Even with the regular first cd of the sarge set, I have to choose my 3com
from a list; it isn't automatically detected. Btw, my hacked cd did the
job for installing with brlt
Hi. It appears some common nic drivers are missing from the access
version of Debian installer. The 3c59x is an example. The problem can
be fixed by adding the line
nic-modules-${kernel:Version} *
to the
installer/build/pkg-lists/access-net-drivers/i386.cfg
file. The standard DI has this m
7 matches
Mail list logo
