Kenny Hitt | 5 Oct 14:17 2004
Picon

fix for missing nic drivers in access version of DI

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 module on the root disk, but it seems to
have been removed to make space for packages in the access version.
Since this isn't a general DI problem, I'm posting it to this list.  I
still haven't fixed the problem of the speakup kernel not getting
installed by default on the access floppies.  When I fix it, should I
post the fix to this list or to the debian-boot list?

          Kenny

Cheryl Homiak | 5 Oct 16:07 2004
Picon

Re: fix for missing nic drivers in access version of DI

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 brltty though I realize it's not a proper 
presentation at this point.

--

-- 
Cheryl

"Where your treasure is, there will your heart be also."

Kenny Hitt | 5 Oct 18:21 2004
Picon

Re: fix for missing nic drivers in access version of DI

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 the system decides on what kernel image to install.
My guess is a package that gets installed during the base install
decides based on the hardware report.

          Kenny

On Tue, Oct 05, 2004 at 09:07:39AM -0500, Cheryl Homiak wrote:
> 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 brltty though I realize it's not a proper 
> presentation at this point.
> 
> 
> -- 
> Cheryl
> 
> "Where your treasure is, there will your heart be also."
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-accessibility-REQUEST <at> lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact 
> listmaster <at> lists.debian.org
(Continue reading)

Cheryl Homiak | 5 Oct 18:36 2004
Picon

Re: fix for missing nic drivers in access version of DI

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 treasure is, there will your heart be also."

Kenny Hitt | 5 Oct 18:39 2004
Picon

Re: fix for missing nic drivers in access version of DI

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 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 treasure is, there will your heart be also."
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-accessibility-REQUEST <at> lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact 
> listmaster <at> lists.debian.org
> 

Cheryl Homiak | 5 Oct 20:06 2004
Picon

Re: fix for missing nic drivers in access version of DI

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."

Kenny Hitt | 6 Oct 02:45 2004
Picon

Re: fix for missing nic drivers in access version of DI

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, 2004 at 11:21:40AM -0500, kenny wrote:
> 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 the system decides on what kernel image to install.
> My guess is a package that gets installed during the base install
> decides based on the hardware report.
> 
>           Kenny
> 
> On Tue, Oct 05, 2004 at 09:07:39AM -0500, Cheryl Homiak wrote:
> > 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 brltty though I realize it's not a proper 
> > presentation at this point.
> > 
> > 
> > -- 
(Continue reading)

Cheryl Homiak | 6 Oct 16:04 2004
Picon

A little bit confused about brltty.txt in svn debian installer


The brltty.txt in the installer/docs directory of the subversion checkout 
of the debian-installer says:
'Currently, the cdrom (2.88MB) i386 includes brltty by default.

Mario, since you wrote this, to what are you referring? Are you referring 
to the boot.img under the cdrom section or to something else? Has this 
been included for some time? If so, is this actually included in any of 
the bootable cds of the sarge distribution? I'm asking because invoking 
brltty with the format you indicate using the first cd from the September 
20 sarge set does not start brltty. So either this is more recent, or I'm 
trying to use the wrong cd, or I am misunderstanding something here. 
Please explain.
If I spent all that time hacking a cd so I could install sarge using 
brltty and it was already available, I'd like to know what I missed.
thanks.

--

-- 
Cheryl

"Where your treasure is, there will your heart be also."

Kenny Hitt | 7 Oct 16:26 2004
Picon

access floppies

Hi.  Looks like the state of the access floppies found at

http://people.debian.org/~joeyh/d-i/images/daily/floppy/access

changes daily.  On Oct 04, the 3c59x driver existed on the install
disks.  The kernel image problem mentioned in bug 275075 also existed.
On Oct 05, the 3c59x driver was missing from the install disks and bug
275075 still existed.  On Oct 06 (today) the disk won't boot on my
system.  I type "linux speakup_synth=dectlk" and the disk starts to
load.  After some disk access, the system reboots.  I would like to see
these disks work instead of having to build custom disks.  Should I
start doing daily testing and filing bug reports?  At this point, I
would need to file a new report for today's build, reopen 275075 based
on the fact it wasn't fixed in yesterday's build, and file a new report
on the missing nic drivers.  Is that the corect thing to do?

          Kenny
	  

Andor Demarteau | 7 Oct 19:51 2004
Picon

Re: A little bit confused about brltty.txt in svn debian installer

only note I can place here is that:
2.88mb sounds awfully simular to those 2.88 floppy-disks that have been
part of the debian-floppy creation for years.
why it's listed as cdrom *2.88mb), dunno.
On Wed, 6 Oct 2004, Cheryl Homiak wrote:

 >
 > The brltty.txt in the installer/docs directory of the subversion checkout
 > of the debian-installer says:
 > 'Currently, the cdrom (2.88MB) i386 includes brltty by default.
 >
 > Mario, since you wrote this, to what are you referring? Are you referring
 > to the boot.img under the cdrom section or to something else? Has this
 > been included for some time? If so, is this actually included in any of
 > the bootable cds of the sarge distribution? I'm asking because invoking
 > brltty with the format you indicate using the first cd from the September
 > 20 sarge set does not start brltty. So either this is more recent, or I'm
 > trying to use the wrong cd, or I am misunderstanding something here.
 > Please explain.
 > If I spent all that time hacking a cd so I could install sarge using
 > brltty and it was already available, I'd like to know what I missed.
 > thanks.
 >
 >
 >

--

-- 
Andor Demarteau                 E-mail: andor <at> nl.linux.org
student computer science        www: http://www.nl.linux.org/~andor
UU based & VU guest-student     jabber,icq,msn,voip: do ask ;)
(Continue reading)


Gmane