debian wi-fi?

[Jude DaShiell]

Many other linux flavors connect through our wi-fi network with no problem.  
Debian for whatever reason cannot connect.  I learned this trying to install 
bookworm and I have no ethernet available.  How is our wi-fi network so 
misconfigured that debian cannot get to the internet?

wi-fi code needs improving

[Jude DaShiell]

The part of the code used to connect a computer to wi-fi after passphrase
has been entered is defective.  It cannot be used to connect to any wi-fi
network in the neighborhood and no ethernet connection is available.  That
is why this computer uses a variant of archlinux called Jenux.


--
 Jude 
 "There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo.
 Please use in that order."
 Ed Howdershelt 1940.

wi-fi connect fails

[Jude DaShiell]

I moved to a new location where wi-fi connection fails.  In old location
wi-fi connection was successful so driver for card already comes with
debian bookworm.
The network is found and I select wpa psk and key in the password when
prompted and the installer goes through trying to connect and cannot
connect with connection failure.
I installed another form of Linux which is how I'm writing this message at
all.
When I installed with the other form of linux 7 local networks were found
as compared to debian's only 1.
No installation logs since the installation couldn't continue this time.
Devuan has the same failure and Fedora is one that works along with Jenux.
Interesting archlinux also fails.
In this local area some of the wi-fi networks have weird names and another
contact wonders if this could be messing up several flavors of linux
having a common error where those strange ssid's cause linux to fail to
connect to any wi-fi network in the area.  About this I do not know so
having encountered this situation I figured to pass some information
along.  The card I have is a qualcom atheros wi-fi card if that helps any.


--
 Jude 
 "There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo.
 Please use in that order."
 Ed Howdershelt 1940.

Re: Installation Errors

[Jude DaShiell]

nmtui I found works better.  It's possible the area of the drive with
/home in it is going bad.  I'm running smartctl -t long over here since
I'm pretty sure that's what's happening here.



Jude  "There are four boxes to be used in
defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

On Fri, 17 Mar 2023, D.J.J. Ring, Jr. wrote:

> Hello,
>
> This email is being sent to Debian-Accessibility and Debian-Boot separately.
>
> I installed from this file:debian-live-11.6.0-amd64-mate+nonfree.iso under
> Windows11 using. Win32 Disk Imager following the Debian Instructions, I had
> previously been using Unetbootin.
>
> I was asked to install this because I had failures using the "latest"
> Alpha2 iso.
>
> I still cannot log into the system using my user name and password.
> The system starts the GUI but fails and goes back to the log in screen, but
> only for user, root can run the GUI.
>
> The installer doesn't ask me where to put GRUB, I believe it should as
> I have multiple Linux distros and several hard drives.
>
> One big thing to the Accessibility Community is that the base packages
> - that is just installing the base packages and standard utilities
> without Debian Desktop Environment and any other Desktop Environment
> like MATE, is that either nmcli or nmtui should be installed.  It's
> difficult for many including myself to remember how to get a WiFi
> connection up and running without such a program.
>
> Debian Accessibility mentioned that it was going to put in a request
> that there be a choice to boot into the CLI text mode, many blind
> users love the CLI because it's unambiguous.
>
> The instructions I was given was to do this in /var/log/
>
> tar -cf log.tar.bz2 ./hardware-summary lsb-release partman status syslog
>
> However none of the files except syslog are there, so I just include a
> pastebin link for syslog.
>
> syslog is here: https://pastebin.com/GzYARtRG
>
> What I have to do is log in as root giving the root password.  Then I
> can start X, I can also from the root prompt, enter "su myusername"
> and start X. I also from root prompt entered "passwd myusername" and
> entered my usename password.  I still cannot log in.
>
> Best regards,
> David Ring
>

debian bookworm install

[Jude DaShiell]

I got an install done and when I hit enter to reboot the system I heard
grub beep and then heard nothing else.  I ought to have heard espeak and
orca starting up or with this standard installation only I ought to have
heard espeak come up talking.  That didn't happen.  So I powered off the
system and turned the system on again then heard the grub beep and the
screen reader came up talking.  That reboot may be a soft reboot rather
than a hard reboot and I think that's what caused this problem.



Jude  "There are four boxes to be used in
defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)

.

multimedia controler packages

[Jude DaShiell]

pulseaudio; alsa-utils, pipewire plus pipewire-media-manager pipewire plus
wireplumber sdl and enlightenment likely could all use an install feature
that would locate each possible sound card on a system and try to make it
speak or play tones if speaking isn't possible.  Once that card is found,
have the installer write a configuration such that when the sound
controler is run that configuration gets used.  I'm thinking along the
lines of making all of these sound controlers easier to install for
everybody, not just the accessibility user community.

Re: boot-time accessibility issues

[Jude DaShiell]

since several different kinds of accessibility can be provided, which kind
of accessibility is needed also needs sorting out.  Apple in 10.4 Tiger
had things set up such that if the computer was completely hooked up
including a set of speakers a question as to which language a user needed
came up on the screen and this had a time limit on it.  Failure to answer
that question resulted in VoiceOver being turned on to interact with the
user during installation and afterwards.
Speech would be no help for those with no hearing ability.  The deaf-blind
usually have refreshable braille displays if involved in education or
employment so perhaps detecting a refreshable braille display and
activating it would help that group.
Perhaps start by displaying a question in normal sized type.  No answer,
make the type larger until that's no longer possible.  Next detect a
braille display if present and display a question on that if available.
Next, try speaking a question with espeakup and see if that gets a
response from either a keyboard or perhaps a microphone if no keyboard is
used.  Perhaps a mouse response could be checked for as well somewhere in
that group but not all people have or use mice.  One thing that may be
necessary to do since some systems these days are missing pc speakers or
those are disabled would to play some tones on a sound card if one is
found and perhaps adjust the post-install boot to play those tones on the
sound card as well.  We had to do this with some very recent hardware so
my reason for bringing it up here.

One thing I really would like to see in a debian installer that installs a
graphical environment is an option for the user if they choose to have
debian start up in console then run ratpoison or startx to go into the
graphical environment since if the graphical environment breaks they have
at least logged in on the console and have a chance to repair the
graphical environment without the need to destroy the whole installation
and start from bare metal again.



--

Re: boot-time accessibility issues

[Jude DaShiell]

I would try something with timing and detection of a sound card in
addition to the monitor.  Ubuntu systems use ks.cfg files Debian uses
preseed files.  I saved from several years ago a ks.cfg file in braille
that was offered by a website in England and believe it or not actually
got ubuntu in an earlier version talking after an install from that
website file.  I don't know if a preseed file is more desireable than a
kickstart file and I think I can find the braille notes in my pile of
braille papers here.

On Thu, 12 Mar 2020, Rich Morin wrote:

> Date: Thu, 12 Mar 2020 12:28:49
> From: Rich Morin 
> To: debian-boot@lists.debian.org
> Cc: debian-accessibil...@lists.debian.org
> Subject: Re: boot-time accessibility issues
> Resent-Date: Thu, 12 Mar 2020 16:29:21 + (UTC)
> Resent-From: debian-accessibil...@lists.debian.org
>
> The idea of detecting the presence (or absence) of a blind-related device 
> seems worth pursuing, even if there are some issues to be resolved.
>
> For example, following Jude's notion of checking for a monitor, maybe Avahi 
> and SSH could be enabled whenever a monitor isn't found.  For that matter, 
> enabling Orca (or whatever) by default when no monitor is present wouldn't be 
> that big a problem for a sighted user.  Devin's notion of checking for a 
> braille display could be expanded to include a range of USB devices such as 
> braille printers and such.
>
> I've been wondering about the notion of checking for a USB flash drive that 
> contains some sort of magic files.  The files probably can't contain 
> executable binary files (due to hardware incompatibility issues), but they 
> could certainly contain textual configuration data.  Can anyone suggest ideas 
> for file content, format, naming, etc?
>
> -r
>
>

-- 

Re: boot-time accessibility issues

[Jude DaShiell]

full circle, solutions zero.

On Thu, 5 Mar 2020, Rich Morin wrote:

> Date: Thu, 5 Mar 2020 23:54:14
> From: Rich Morin 
> To: debian-boot@lists.debian.org
> Cc: debian-accessibil...@lists.debian.org
> Subject: Re: boot-time accessibility issues
> Resent-Date: Thu, 12 Mar 2020 02:07:16 + (UTC)
> Resent-From: debian-accessibil...@lists.debian.org
>
> Jude DaShiell said:
>
> > If dummy was used for monitor type, the screen reader could come up talking 
> > without any monitor attached. ...
>
> I can think of a couple of issues with this approach.  First, there are 
> various reasons for leaving a monitor off a system.  For example, if a RasPi 
> is being used as a server, running it "headless" might be a normal strategy, 
> having nothing to do with blindness.
>
> Contrariwise, there are various reasons a blind user might want to keep an 
> active  monitor.  They might have a sighted associate with whom they 
> occasionally collaborate. Alternatively, they might want to run a touch 
> screen (e.g., to type on).
>
> The fundamental problem is that keying off the presence of a monitor 
> complects two separate and otherwise independent phenomena.  So, it's just 
> asking for conflicts.
>
> -r
>
>

-- 

Re: boot-time accessibility issues

[Jude DaShiell]

If dummy was used for monitor type, the screen reader could come up
talking without any monitor attached.  Many linux distros including
debian can get a monitor turned on and off during operation and don't
let a screen reader know now we have a working monitor and now we don't
have a working monitor.  I'm thinking along these lines to attempt to
make installations bulletproof.  On the debian-user list earlier someone
had a monitor that required firmware to run it and debian wouldn't
install without that firmware.  I'm not sure with that radeon monitor if
vga normal could have been run on boot to eliminate the firmware
complaint.

On Thu, 5 Mar 2020, Rich Morin wrote:

> Date: Thu, 5 Mar 2020 03:53:30
> From: Rich Morin 
> To: debian-boot@lists.debian.org
> Cc: debian-accessibil...@lists.debian.org
> Subject: Re: boot-time accessibility issues
> Resent-Date: Thu,  5 Mar 2020 09:15:43 + (UTC)
> Resent-From: debian-accessibil...@lists.debian.org
>
> Thanks to everyone for considering these questions, offering suggestions, 
> etc.  Here are some comments and clarifications.
>
> I don't know all the ins and outs of preseeding, etc.  So, I'll talk about 
> use cases.  I'm mostly looking for a way to make freshly installed systems 
> (e.g., PC, RasPi) accessible in two situations:
>
> - The user plugs in a keyboard and a pair of headphones.
> - The user SSHs in from another machine on the LAN.
>
> In the first situation, the machine has to have some sort of screen reader, 
> so that the user can hear their commands and the responses.  In the second 
> situation, the user can fall back on the screen reader in the other machine.
> In either case, the user can now install whatever additional packages they 
> want (e.g., by means of a meta-package).
>
> John Doe said:
>
> > ... Having the standard image accessible means that all derivatives inherit 
> > the support: all kinds of network/cd images, Debian blends, derivative 
> > distributions, etc.
>
> I'm in violent agreement with this.  The more (kinds of) systems we can make 
> accessible at boot time, the more impact the changes will have.
>
> FWIW, the RasPi folks are already making some strong moves in the direction 
> of accessibility.  For example, the "Orca screen reader" section in a recent 
> blog seems quite promising:
>
> A new Raspbian update
> https://www.raspberrypi.org/blog/a-new-raspbian-update
>
> -r
>
>

-- 

Re: boot-time accessibility issues

[Jude DaShiell]

Another possibility could be to have the installer check for a monitor
and if no monitor is connected, turn on a screen reader.

On Mon, 2 Mar 2020, john doe wrote:

> Date: Mon, 2 Mar 2020 11:24:48
> From: john doe 
> To: Rich Morin , debian-boot@lists.debian.org,
> debian-accessibil...@lists.debian.org
> Subject: Re: boot-time accessibility issues
> Resent-Date: Mon,  2 Mar 2020 16:26:05 + (UTC)
> Resent-From: debian-accessibil...@lists.debian.org
>
> On 3/2/2020 5:13 PM, Samuel Thibault wrote:
> > john doe, le lun. 02 mars 2020 17:02:49 +0100, a ecrit:
> >> Prompting the user with a question asking if accessibility is desired
> >> would go a lon way.
> >
> > But we don't necessarily want to ask the question on all Debian systems
> > at all boot.
> >
> > I'm not saying that there is no solution. I'm saying that it's not just
> > a matter of adding a question, but rather to determine a reasonable way
> > to have it asked.
> >
>
> One way could be to emit that prompt when the "low" priority is used.
>
> That way, the question would not be asked for regular user but could be
> triggered by choosing the low priority or preseeded in a preseed file.
>
> --
> John Doe
>
>

-- 

Re: boot-time accessibility issues

[Jude DaShiell]

Apple solved this problem back in 2006.  That was when Mac OS Tiger 10.4
became available.  What Apple did was to put a message asking for
language to be used on the screen for about 10 seconds I think.  If that
message didn't get a keyboard response then VoiceOver got turned on
since Apple figured someone who couldn't see the screen then needed
VoiceOver turned on to do the installation.

On Mon, 2 Mar 2020, Samuel Thibault wrote:

> Date: Mon, 2 Mar 2020 10:57:18
> From: Samuel Thibault 
> To: Rich Morin , debian-boot@lists.debian.org,
> debian-accessibil...@lists.debian.org
> Subject: Re: boot-time accessibility issues
> Resent-Date: Mon,  2 Mar 2020 15:57:33 + (UTC)
> Resent-From: debian-accessibil...@lists.debian.org
>
> Rich Morin, le lun. 02 mars 2020 07:40:42 -0800, a ecrit:
> > In another forum, I've been told that Orca is a rather heavyweight solution 
> > for providing boot-time speech generation.  It was recommended that I 
> > consider Fenrir, instead.
>
> Fenrir is also quite heavy-weight, since it brings python. Brltty would
> be much less heavy-weight (but still bring e.g. libicu)
>
> > So, recasting my question, what would it take to make these changes to the 
> > default Debian installation?
> >
> > - include Fenrir, with some sort of key combination to activate it
>
> On the Linux console there is currently no way to activate a program
> through a key combination.
>
> What is the installation use case, actually? Is it again the raspi case?
> As mentioned previously the raspi team handles it, so it'd rather have
> to be discussed with them.
>
> > More generally, is there a better way to provide accessibility at boot time?
>
> The question is how to detect that it is needed. We can't just install
> and run a screen reader by default on all Debian systems, so something
> needs to trigger the screen reader startup.
>
> Samuel
>
>

-- 

Re: buster rc2 install resultsn

[Jude DaShiell]

Two voices heard in mate, I hear sound saying ok once before orca boots
and turns on but don't know the source of that spoken ok.

On Fri, 28 Jun 2019, Didier Spaier wrote:

> Date: Fri, 28 Jun 2019 14:10:17
> From: Didier Spaier 
> To: Cyril Brulebois , Jude DaShiell ,
> Samuel Thibault 
> Cc: debian-boot@lists.debian.org, debian-accessibil...@lists.debian.org
> Subject: Re: buster rc2 install resultsn
>
> Hi,
>
> Jude: are there two voices heard in console mode or in Mate?
>
> I ask as during installation the id of the selected card is stored in
> /var/run/espeakup.card, I presume to be set as default for espeakup in
> the installed system
> Samuel, is this right?
>
> But only one card id is stored so I fail to see how this can trigger two
> voices.
>
> But I have no idea if this setting is also used when starting Speech
> Dispatcher for Orca in Mate, hence my question.
>
> Also Cyril, should I assume that RC2 included a fix for the issue that I
> raised in this post?
> https://lists.debian.org/debian-accessibility/2019/06/msg00019.html
>
> I have a doubt as this iso:
> http://cdimage.debian.org/cdimage/buster_di_rc2/amd64/iso-cd/debian-buster-DI-rc2-amd64-netinst.iso
> is dated 2019-06-24 14:13
> and there are more recent post in the thread.
>
> Let me add that the issue is with  a Lenovo Thinkpad W520 which is a
> rather common hardware. I am not directly in concern being neither blind
> nor a Debian user, but still I hope this can be fixed before the release
> for the benefit of others.
>
> Cheers,
>
> Didier
> 2019-06-24 14:13d
> On 6/28/19 6:32 PM, Cyril Brulebois wrote:
> > Hi Jude,
> >
> > Thanks for your mail.
> >
> > Cross-posting this answer to debian-accessibility@:
> >
> > Jude DaShiell  (2019-06-27):
> >> First the log files I tried to get the system to save in /mnt were not
> >> saved and those choices got made using the debian main menu.
> >> I checked the disk integrity and the disk was found to be valid.
> >> I installed the mate desktop using the defaults in software selection.
> >> On boot, I get two voices first louder and second softer and playing
> >> identical text shortly after the first voice.  I don't know why this is
> >> and tried adjusting sound which cleared the problem when sound volume got
> >> increased in the mate menus until the next reboot.
> >
> > I think this might be a side effect of our trying hard to detect each
> > and every sound card, reading a prompt using all of them in turn, so
> > that users can press Return when they hear something. Maybe some state
> > in the sound card driver changes while iterating, which triggers this
> > difference in volumes?
> >
> > Just wild-guessing as I'm no sound expert?
> >
> >
> > Cheers,
>
>

-- 

buster rc2 install results

[Jude DaShiell]

First the log files I tried to get the system to save in /mnt were not
saved and those choices got made using the debian main menu.
I checked the disk integrity and the disk was found to be valid.
I installed the mate desktop using the defaults in software selection.
On boot, I get two voices first louder and second softer and playing
identical text shortly after the first voice.  I don't know why this is
and tried adjusting sound which cleared the problem when sound volume got
increased in the mate menus until the next reboot.



--

re: debian buster rc2

[Jude DaShiell]

Where can I download a validation file for this release?  I'll be testing
the amd64 iso.  I like to run sha512sum on isos before I test to ensure I
have a good download of the iso so I don't submit any bogus bug reports
caused by a less than perfect iso download.


--

install logging

[Jude DaShiell]

If in the course of a debian install I need to execute a shell and logs 
are being preserved, will what I type in the shell also be saved to one of 
the log files?  I have a procedure to get a secure wifi login done after 
reboot and post-install and this way I could send logs and it would be 
available for others.  The secure wifi connection happens with ifup with a 
little help from wpa_passphrase and grep and ex.




--

Re: (solved) Re: wireless fail after stretch installation

[Jude DaShiell]

Wifi doesn't come up after a console login once a normal install happens 
until after the network is configured on the post-install system unless 
the /etc/networks/interfaces file created as a result of the install 
process originally gets copied to the hard drive in the correct 
directory with the proper name and contents.  Many ways exist to solve 
this problem and it took a while to find out what to do and how because 
there's more and better support from debian-users than is in debian wiki 
or debian documentation.  I had learned how to do this earlier but 
apparently an individual known as longwind from China ran into this 
problem after I had learned to solve it on this end and the original 
message I read from Brian had a solution I hadn't read earlier and 
hadn't tried yet which involved far fewer steps.  Fortunately I have a 
hard drive available so I will try Brian's solution out on this end and 
see how it works.  Thanks for your assistance and interest.


On Sun, 4 Mar 2018, Philip Hands wrote:


Date: Sun, 4 Mar 2018 13:10:02
From: Philip Hands 
To: Jude DaShiell , Brian ,
debian-u...@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: Re: (solved) Re: wireless fail after stretch installation

Jude DaShiell  writes:


The least debian-boot membership could do would be to have a note come
up for installers to execute a shell and do the file copy before
rebooting once hard drive got mounted.  This is a problem for wifi users
with no impact for ethernet users.


Your tone does not encourage a civil response, but you're going to get
one anyway I'm afraid.

Since you didn't bother to say what you are complaining about in any
useful way, I thought I'd look at the first post in the first thread
referred to in the mail from Brian, which is about the fact that
desktop-configured wifi connections don't come up until someone logs in.

Given that one has generally specified the wifi password as the user in
the desktop environment, or at least indicated the fact that you want to
connect to that network, it would be inappropriate for the wifi to come
up earlier, because that might allow other users on the machine to
access a network that was intended to be private.

There is generally an option available in network manager that allows
one to indicate that the connection should be made available to others.
Ticking that box should make it come up at boot time AFAIK.

This seems to have very little to do with the installer.

Cheers, Phil.



--

Re: (solved) Re: wireless fail after stretch installation

[Jude DaShiell]

The least debian-boot membership could do would be to have a note come 
up for installers to execute a shell and do the file copy before 
rebooting once hard drive got mounted.  This is a problem for wifi users 
with no impact for ethernet users.


On Sun, 4 Mar 2018, Brian wrote:


Date: Sun, 4 Mar 2018 05:35:28
From: Brian 
To: debian-u...@lists.debian.org
Subject: Re: (solved) Re: wireless fail after stretch installation
Resent-Date: Sun,  4 Mar 2018 10:35:45 + (UTC)
Resent-From: debian-u...@lists.debian.org

On Sun 04 Mar 2018 at 08:41:00 +, Long Wind wrote:


Thank Brian! Your instructions are right, wireless works now!
the 1st time i use network installthis time i use cdrom install, it has same
problemas this problem is easily reproduced, why don't they fix it??
i attach wrong and right interfaces:t1 and t2 respectively(key removed)


The installer team do not consider there is anything to fix. This is the
way they want it. Some users think it is a bug and have said so in the
BTS (see the netcfg package).

We discused this recently on -user. The thread starts at

 https://lists.debian.org/debian-user/2018/01/msg00800.html

and continues at

 https://lists.debian.org/debian-user/2018/02/msg0.html




--

netinst network setup

[Jude DaShiell]

If a netinst version of the installer connects with the internet would it 
be possible to have a version as part of the installation process at least 
give the installer the option to save those network settings in 
/etc/network/interfaces so if that option were chosen the post-install 
debian version would connect to the internet?  The last time I installed 
debian, that didn't happen and installing mate/gnome and using the 
gnome-orca package and bringing up the network connections to get a wifi 
connection set up didn't work all that easily.  I only put a graphical 
interface on a system for two reasons.  It's new and I want to experiment 
with it, or more browser than lynx is needed to solve a captcha.  Other 
than that, I'm found in the command line for most of what I do and that's 
by preference.



--

Re: stretch installer question

[Jude DaShiell]

I don't need ssh-server, I need ssh-client and that's what was missing. 
Beyond that though, why is iwconfig on any of these isos?  The iw 
package was supposed to have replaced iwconfig especially with the more 
modern linux kernels.


On Sun, 22 May 2016, Steve McIntyre wrote:


Date: Sat, 21 May 2016 19:31:38
From: Steve McIntyre 
To: Jude DaShiell 
Cc: debian...@lists.debian.org, debian-boot@lists.debian.org
Subject: Re: stretch installer question

On Sat, May 21, 2016 at 12:13:10PM -0400, Jude DaShiell wrote:

Is the package selection section of the stretch installer as broken in all
versions as it is in the x86_64 version of firmware testing iso?  I preserved
logs but once installation was finished and system rebooted, ssh was nowhere
to be found on the new system.  I may be able to copy the installation log or
logs off of the new system onto a flash drive then copy those logs back onto
another hard drive to send them along but can't do it directly from the newly
installed system since neither telnet rlogin or ssh got onto it.


Not everybody wants to run servers (even ssh) by default on new
machine installations, so ssh isn't installed *by default*. However,
there is an option in tasksel to install "SSH server" if that's what
you want.




--

Re: Debian Installer Stretch Alpha 6 release

[Jude DaShiell]

Unless some compeling reason exists not to do it, could wireless-tools 
and iw get added to the isos?  I don't know why iwconfig continues to be 
on this type of debian when iw was supposed to have replaced it and is 
supposedly more harmonious with modern kernels.  I tried configuring my 
wifi connection to xfinity with iwconfig and wpa_supplicant and couldn't 
get it done post-install and suspect I need a few more tools and I'm 
doing this with command line.  If espeakup by default gets mate 
installed is orca also installed?


On Sat, 21 May 2016, Cyril Brulebois wrote:


Date: Sat, 21 May 2016 17:13:17
From: Cyril Brulebois 
Reply-To: debian-boot@lists.debian.org
To: debian-devel-annou...@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: Debian Installer Stretch Alpha 6 release

The Debian Installer team[1] is pleased to announce the sixth alpha
release of the installer for Debian 9 "Stretch".


Important changes in this release of the installer
==

* This release fixes the package installation issue which appeared
  lately with the previous alpha release (#814343).
* Debian Pure Blends can now be enabled directly from the Software
  selection screen. This might change in a later release though
  (#758116).


Improvements in this release


* brltty:
   - Install MATE desktop by default when brltty is used in d-i.
   - Disable auto-detection of Cebra, Albatross, and BrailleMemo
 devices in d-i, since they are rare and conflict with other
 devices (#782732).
   - prebaseconfig: Enable screen reader in KDE.
   - prebaseconfig: Support 4th bootline parameter.
   - brltty-udeb.udev.rules: Add new USB IDs.
* cdebconf:
   - gtk: Auto-scroll when switching between entries.
   - text: Print one screen worth of choices, and use +/- to switch
 between choices screens (#809739).
* debian-installer:
   - Bump linux kernel version from 4.3.0-1 to 4.5.0-2.
* espeakup:
   - Add support for multiboard systems: request the user to press
 enter at the right time to select a given board.
   - Improve language/voice lookup.
   - Install MATE desktop by default when espeakup is used in d-i.
* flash-kernel:
   - Avoid waiting for Ctrl-c when debconf is running (#791794).
* net-retriever:
   - Concentrate on SHA256 now, following archive-side changes.
* netcfg:
   - Improve behaviour when user-submitted input contains spaces
 (#818611).
   - Improve error checking in various places.
* network-console:
   - Improve support for multiple addresses (#816600).
* parted:
   - Fix problems with LVM and DASD devices (#814076).
* partman-auto:
   - Bump space requirements for a lot of recipes (#725642).
* partman-basicfilesystems:
   - Call mkfs.ext2 with -F to avoid hangs (#817174).
* partman-ext3:
   - Call mkfs.ext[34] with -F to avoid hangs (#767682).
* preseed:
   - Invert env-preseed and initrd-preseed so that the former
 overrides the latter (#805291).
   - url: correctly handle IPv6 addresses (#815166).
* rootskel:
   - Add GNU/screen support, when it's available.
* s390-zfcp:
   - New component to activate and configure FCP devices (#808041).
* wget:
   - Add udeb support, for later user.
* win32-loader:
   - Switch signature checking from MD5 to SHA256.
   - Improve support for new versions of Windows (#775055).


Hardware support changes


* debian-installer:
   - Provide u-boot images for OpenRD.
   - Use marvell flavour for orion5x and kirkwood.
   - Include mtd-modules in various images.
   - Generate image for Seagate Personal Cloud and Seagate NAS.
   - Improve armel/orion5x and armel/kirkwood for many different
 Buffalo Linkstation devices.
   - Add support for Firefly-RK3288.
   - Add support for BeagleBoard-X15.
   - ARM: sunxi: Add support for the Olimex A20-SOM-EVB.
   - Add sata-modules for arm64.
* grub-installer:
   - Install grub-xen when installing in a Xen PV guest.
* hw-detect:
   - Improve and split harddrive detection into DASD and SCSI
 dependency on s390x (#818586).
* libdebian-installer:
   - armel: Add various orion5x/kirkwood based Buffalo Linkstation
 devices supported by device-tree.
* linux:
   - [armhf] usb-modules: Add modules required for BeagleBoard-X15
 (#815848).
   - [mips*/octeon] udeb: Add ahci_octeon and ahci_platform modules
 to sata-modules.
   - [arm64] udeb: Add leds-modules package containing leds-gpio
 driver.
   - [arm64] udeb: Add regulators and SoC modules to core-modules.
   - [x86] udeb: Move scsi_transport_fc to scsi-core-modules, since
 hv_storvsc now depends on it.
   - [armhf] core-modules: Include regulator drivers by default.
   - mmc-modules: Include MMC controller drivers by default.
   - mmc-modules: Depends on usb-modules.
   - usb-modules: Include USB PHY drivers by default.
   - udeb: Combine scsi-{common,extra}-modules with scsi-modules.
   - udeb: Use wildcards to include entire classes of drivers.
   - u

stretch installer question

[Jude DaShiell]

Is the package selection section of the stretch installer as broken in all 
versions as it is in the x86_64 version of firmware testing iso?  I 
preserved logs but once installation was finished and system rebooted, ssh 
was nowhere to be found on the new system.  I may be able to copy the 
installation log or logs off of the new system onto a flash drive then 
copy those logs back onto another hard drive to send them along but can't 
do it directly from the newly installed system since neither telnet rlogin 
or ssh got onto it.
Thanks much for adding the firmware-ralink package so I could at least get 
out on the internet while doing an install.




--

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Jude DaShiell]

I had the hard drive slightly out of the machine so the dvd would boot. 
As soon as the dvd started I pushed the hard drive in and locked it. 
Then I hit s  shortly after the bppbeep and waited some time for 
speech to come on and it didn't happen.


On Sat, 21 May 2016, Samuel Thibault wrote:


Date: Fri, 20 May 2016 19:06:15
From: Samuel Thibault 
To: Jude DaShiell 
Cc: Brian Potkin ,
Nick Gawronski ,
debian-accessibil...@lists.debian.org, debian-boot@lists.debian.org
Subject: Re: debian-installer issues with no wireless network connection after
 a text based Jessie installation
Resent-Date: Fri, 20 May 2016 23:06:44 + (UTC)
Resent-From: debian-accessibil...@lists.debian.org

Jude DaShiell, on Fri 20 May 2016 19:00:17 -0400, wrote:

the whole espeakup dependency stack is missing from that dvd and I suspect
all other firmware dvd's.


?!

I've just tried 8.0.0, and I had espeakup working.

Where did you download it exactly?  How did you boot it exactly?

Samuel




--

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Jude DaShiell]

bash history comes to the rescue!

wget -bc --max-redirect=1 --trust-server-names 
http://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/8.4.0-live+nonfree/amd64/iso-hybrid/debian-live-8.4.0-amd64-standard+nonfree.iso


On 
Sat, 21 May 2016, Samuel Thibault wrote:



Date: Fri, 20 May 2016 19:06:15
From: Samuel Thibault 
To: Jude DaShiell 
Cc: Brian Potkin ,
Nick Gawronski ,
debian-accessibil...@lists.debian.org, debian-boot@lists.debian.org
Subject: Re: debian-installer issues with no wireless network connection after
 a text based Jessie installation

Jude DaShiell, on Fri 20 May 2016 19:00:17 -0400, wrote:

the whole espeakup dependency stack is missing from that dvd and I suspect
all other firmware dvd's.


?!

I've just tried 8.0.0, and I had espeakup working.

Where did you download it exactly?  How did you boot it exactly?

Samuel



--

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Jude DaShiell]

That shouldn't have killed speech post-install for you.  Only thing I 
can suggest is to do what you did before but this time in main menu save 
log files and save them to a mounted file system.  One will be offered 
on the target disk.  If you can get copies of everything in that 
directory and send it in email to debian-boot, they may either find 
errors that need fixing or assist you to get things going the correct 
way.


On Fri, 20 May 2016, Nick Gawronski wrote:


Date: Fri, 20 May 2016 15:00:43
From: Nick Gawronski 
To: Jude DaShiell ,
Alex ARNAUD ,
debian-accessibil...@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: Re: debian-installer issues with no wireless network connection after
 a text based Jessie installation

Hi, I used the S option to get speech during the installation then enabled 
the network console using the loading menu options and then entered in my 
password so had speech the entire installation and was mainly testing out the 
network console.  Are you saying even if I do that and have speech if I 
install using the network console speech will not be turned on after the 
installation even if it is used to start the network console? Nick Gawronski



On 5/20/2016 5:41 AM, Jude DaShiell wrote:
Windows 10 was probably why you didn't get speech post-install. Starting 
debian with the s boot parameter turns on speech that debian produces for 
the installation then by default keeps speech turned on post-install.  Use 
of a console with windows 10 enabled you to get the text over the console 
so I suspect you failed to enable debian speech during installation.  I 
hope this solves one of your problems.


On Fri, 20 May 2016, Nick Gawronski wrote:


Date: Fri, 20 May 2016 02:54:02
From: Nick Gawronski 
To: Alex ARNAUD ,
debian-accessibil...@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: Re: debian-installer issues with no wireless network connection 
after

 a text based Jessie installation
Resent-Date: Fri, 20 May 2016 06:54:31 + (UTC)
Resent-From: debian-accessibil...@lists.debian.org

Hi, The name of the iso I was using is firmware-8.0.0-amd64-netinst.iso

and it is in the archive for the debian-installer.  I ran the installation 
using this image as my network cards both wired and wireless require 
firmware and I also ran the installation on low priority and choose to 
install everything like non-free as well as backports.  For the main tasks 
for this text based installation I selected just the standard system as I 
want this system to be small.  Everything installed just fine and I was 
connected to the installation over the network as I wanted to test out the 
network console using my windows 10 system and was able to follow all 
prompts but then once the Debian system rebooted no internet settings were 
on the system in the /etc/network/interfaces or any other wifi packages 
that were installed such as wpa_supplicant.  My question is why does the 
installer not copy over the wireless networking settings from the 
installer to the target system when doing a text only install with speech? 
Nick Gawronski

On 5/20/2016 1:07 AM, Alex ARNAUD wrote:

Dear Nick

On 05/20/2016 06:52 AM, Nick Gawronski wrote:
Hi, I am using the net installer of Jessie version 8.0.0 that includes 
the firmware 

Could you give us the full name of the Jessie ISO?
as I am totally blind and found that the latest installer once it was 
installed I had no software speech after installing the system.
It depends on how you install your system. If you install you system in 
braille or in "normal" way it's the normal effect.
I was installing Debian Jessie on my laptop with just a text based 
system mainly for a rescue system for when X windows is down and for 
times when I don't wish to use X windows.  I found that during the 
installation I was able to connect to the internet and successfully 
install the system but once the system was rebooted I had no internet 
access over any network method. 

As I know, It seems there is no link with accessibility in this case.
What would it take for the debian installation to copy the network 
settings from the installer to the target system as it makes no sence 
why networking would be setup and working during a text based 
installation but not in the target system?  What file should I edit to 
add my wireless network as well as my wired network using DHCP so they 
both will work when my text based system boots?  Nick Gawronski

The tips I use is to install a new driver for your Debian system.
For doing something like that you need to follow some steps :
1) Find the model of your card and the related firmware package in 
Debian, if it's a Intel Wireless card it's the package firmware-iwlwifi 
<https://packages.debian.org/fr/jessie/firmware-iwlwifi>
2) Add the backports repo in your environment as explained in this page : 
http://backports.debian.org/Instructions/
3) Install the n

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Jude DaShiell]

A few minutes ago I tried the debian-8.4-x86_64-standard-firmware.iso 
and discovered something else.  If true for all firmware iso being made 
the only way these can be partly installed to the extent originally 
described in this thread is with a console running aan already talking 
operating system since the whole espeakup dependency stack is missing 
from that dvd and I suspect all other firmware dvd's.


On Fri, 20 May 2016, Brian Potkin wrote:


Date: Fri, 20 May 2016 14:12:24
From: Brian Potkin 
To: Nick Gawronski 
Cc: debian-accessibil...@lists.debian.org, debian-boot@lists.debian.org
Subject: Re: debian-installer issues with no wireless network connection after
 a text based Jessie installation
Resent-Date: Fri, 20 May 2016 18:12:54 + (UTC)
Resent-From: debian-accessibil...@lists.debian.org

On Fri 20 May 2016 at 01:54:02 -0500, Nick Gawronski wrote:


prompts but then once the Debian system rebooted no internet settings were
on the system in the /etc/network/interfaces or any other wifi packages that
were installed such as wpa_supplicant.  My question is why does the


Are you certain wpa_supplicant was not on the system? If the machine has
no ethernet connection you now have problems.


installer not copy over the wireless networking settings from the installer
to the target system when doing a text only install with speech?  Nick
Gawronski


It happens with any install. The thinking appears to be:

You used a wired install without selecting a desktop task. That means
you wanted a wired connection after the install.

You used a wired or wireless connection and selected a desktop task.
That means you wanted to use networkmanager.

That's ok up to there. There is some practical sense in it. You will
have connectivity after the first boot and can change what you want.

If you used a wireless onnection and did not select a desktop task
that means you want to select and set up your connectivity software
after first boot. Basically - you were just kidding when you used
wireless to install Debian; you didn't want immediate connectivity
afterwards.

Setting up wireless all over again is good fun when your passphrase
has 63 characters. Copy and paste? You could download gpm but

That is one of the reasons I preseed.

Regards.

Brian.




--

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Jude DaShiell]

I don't know if preserving installation logs menu selection captures an 
additional entry when debian's speech is enabled for an installation or 
not.  If so preserving log files and saving to a mounted file system 
would show whether or not debian speech was enabled for firmware install 
or not.  If debian's speech is enabled for installation the 
configuration to enable speech for post-install in stock debian 
distributions is copied to the target system by default to help with 
accessibility.


On Fri, 20 May 2016, Cyril Brulebois wrote:


Date: Fri, 20 May 2016 03:53:03
From: Cyril Brulebois 
To: Nick Gawronski 
Cc: Alex ARNAUD ,
debian-accessibil...@lists.debian.org, debian-boot@lists.debian.org,
debian...@lists.debian.org
Subject: Re: debian-installer issues with no wireless network connection after
 a text based Jessie installation

Hi Nick,

Nick Gawronski  (2016-05-20):

Hi, The name of the iso I was using is firmware-8.0.0-amd64-netinst.iso

 and it is in the archive for the debian-installer.  I ran the installation
using this image as my network cards both wired and wireless require
firmware and I also ran the installation on low priority and choose to
install everything like non-free as well as backports.  For the main tasks
for this text based installation I selected just the standard system as I
want this system to be small.  Everything installed just fine and I was
connected to the installation over the network as I wanted to test out the
network console using my windows 10 system and was able to follow all
prompts but then once the Debian system rebooted no internet settings were
on the system in the /etc/network/interfaces or any other wifi packages that
were installed such as wpa_supplicant.  My question is why does the
installer not copy over the wireless networking settings from the installer
to the target system when doing a text only install with speech?  Nick
Gawronski


In the general case, the installer (through its netcfg component) should
be copying the network settings over from the installer system to the
installed system.

I'm not familiar with the firmware version of installer images, so I'm
adding the debian-cd@ list to the loop, so that people building those
images can comment on this. They might appreciate if you could extract
the following log file from your system and attach it to an email:

   /var/log/installer/syslog

We might have a missing integration bit to enable non-free packages on
the installation system (this might be by design because of freeness
issues, or maybe an oversight; no idea), or maybe a buggy behaviour.

The log file mentioned above might help them figure out what happened on
your system.


KiBi.



--

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Jude DaShiell]

Windows 10 was probably why you didn't get speech post-install. 
Starting debian with the s boot parameter turns on speech that debian 
produces for the installation then by default keeps speech turned on 
post-install.  Use of a console with windows 10 enabled you to get the 
text over the console so I suspect you failed to enable debian speech 
during installation.  I hope this solves one of your problems.


On Fri, 20 May 2016, Nick Gawronski wrote:


Date: Fri, 20 May 2016 02:54:02
From: Nick Gawronski 
To: Alex ARNAUD ,
debian-accessibil...@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: Re: debian-installer issues with no wireless network connection after
 a text based Jessie installation
Resent-Date: Fri, 20 May 2016 06:54:31 + (UTC)
Resent-From: debian-accessibil...@lists.debian.org

Hi, The name of the iso I was using is firmware-8.0.0-amd64-netinst.iso

and it is in the archive for the debian-installer.  I ran the installation 
using this image as my network cards both wired and wireless require firmware 
and I also ran the installation on low priority and choose to install 
everything like non-free as well as backports.  For the main tasks for this 
text based installation I selected just the standard system as I want this 
system to be small.  Everything installed just fine and I was connected to 
the installation over the network as I wanted to test out the network console 
using my windows 10 system and was able to follow all prompts but then once 
the Debian system rebooted no internet settings were on the system in the 
/etc/network/interfaces or any other wifi packages that were installed such 
as wpa_supplicant.  My question is why does the installer not copy over the 
wireless networking settings from the installer to the target system when 
doing a text only install with speech?  Nick Gawronski

On 5/20/2016 1:07 AM, Alex ARNAUD wrote:

Dear Nick

On 05/20/2016 06:52 AM, Nick Gawronski wrote:
Hi, I am using the net installer of Jessie version 8.0.0 that includes the 
firmware 

Could you give us the full name of the Jessie ISO?
as I am totally blind and found that the latest installer once it was 
installed I had no software speech after installing the system.
It depends on how you install your system. If you install you system in 
braille or in "normal" way it's the normal effect.
I was installing Debian Jessie on my laptop with just a text based system 
mainly for a rescue system for when X windows is down and for times when I 
don't wish to use X windows.  I found that during the installation I was 
able to connect to the internet and successfully install the system but 
once the system was rebooted I had no internet access over any network 
method. 

As I know, It seems there is no link with accessibility in this case.
What would it take for the debian installation to copy the network 
settings from the installer to the target system as it makes no sence why 
networking would be setup and working during a text based installation but 
not in the target system?  What file should I edit to add my wireless 
network as well as my wired network using DHCP so they both will work when 
my text based system boots?  Nick Gawronski

The tips I use is to install a new driver for your Debian system.
For doing something like that you need to follow some steps :
1) Find the model of your card and the related firmware package in Debian, 
if it's a Intel Wireless card it's the package firmware-iwlwifi 

2) Add the backports repo in your environment as explained in this page : 
http://backports.debian.org/Instructions/
3) Install the new package with a command like that : "apt-get install -t 
jessie-backports FIRMWARE_NAME"

--
Alex ARNAUD





--

Re: State of gnome-orca in debian-installer

[Jude DaShiell]

I managed to install kali linux which is a security-minded fork of 
debian and default is a desktop interface post-install.  I used speakup 
in text mode to do the whole installation too in the usual manner.


On Tue, 27 Oct 2015, Samuel Thibault wrote:


Date: Tue, 27 Oct 2015 12:20:08
From: Samuel Thibault 
To: shirish 
Cc: debian-boot@lists.debian.org, debian-accessibil...@lists.debian.org,
hamara-devel 
Subject: Re: State of gnome-orca in debian-installer
Resent-Date: Tue, 27 Oct 2015 16:20:48 + (UTC)
Resent-From: debian-accessibil...@lists.debian.org

Hello,

shirish, le Tue 27 Oct 2015 20:37:22 +0530, a ?crit :

What sort of support is there for gnome-orca in debian-installer ?


None yet.  Supporting gnome-orca would require python support, which we
don't have yet.


I did see that there is support for espeak in d-i but nothing about
gnome-orca.


Yes, speech synthesis support is implemented through speakup, in
textmode.

Samuel




--

firmware-testing-amd64-netinst.iso bug

[Jude DaShiell]

I tried to get this iso to install on a real amd k8 athelon and network 
configuration was successful to the point that my rt2780 usb wifi adapter 
was found and used for installation of files not available on the dvd and 
updates for those that were available.  Unfortunately, I got link not 
ready in dmesg post-install and so far haven't figured out what to do to 
bring that link up persistently.  That's not such a big deal since the 
real amd-64 k8 athelon has talkingarch on it now running its wifi 
otherwise you wouldn't be reading this message.
The other equipment I tried this iso on was an Acer Aspire 5003 notebook. 
When network configuration happened, it failed completely to the point 
where the iso on the dvd behaved like it was a stock debian netinst disk 
and not the firmware iso.  It's true Acer is an AMD clone, and I'm 
wondering if the firmware iso is supposed to work on any amd clones.  If 
not, I'll have to install talkingarch on the notebook just to get it onto 
the internet.  If so, there is some kind of bug at issue here.  I 
downloaded the iso about two weeks ago if that helps at all.
I probably can repeat the debian tower installation and preserve logs 
since I have an external hard drive I can transfer those onto an 
internet-capable installation and send those here if anyone would be 
interested in reading them.





--

Re: <20120708001451.gm4...@mykerinos.kheops.frmug.org>

[Jude DaShiell]

I wouldn't use pitch by itself.  I think what would be better is a single 
beep for default, two beeps second with higher pitch than first for 
graphical, and three beeps in a rising pitch pattern for advanced.  That 
way if someone hasn't got good pitch ability they'll still be able to 
differentiate based on the number of tones. On Sat, 7 Jul 2012, Joey Hess 
wrote:

> Stefano Zacchiroli wrote:
> > It is not clear to me how accessible the initial splash screen --- the
> > one with currently contain the choice between default, graphical, and
> > advanced installation options --- is.
> > 
> > *If* that screen is accessible
> 
> It's not. Does occur to me that syslinux could be modified to add the
> ability to beep at different musical note frequencies, and we could
> then make it accessible, at least to those with good pitch.
> 
> 


Windows Pants: made entirely of patches on patches each with a picture of
a Microsoft Vacuum Cleaner; a computer mouse, or a dollar sign.

Jude 



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.01.1207080459000.85...@freire1.furyyjbeyq.arg

Bug#633620: Info received (Bug#633620: installation-report: espeakup amdk8 wheezy to sid)

[Jude DaShiell]

I expect the ata errors are happening because of the disk on which 
debian was installed.  It's in a drive sled and recently I asked a 
sighted friend to check the drive sled out and was told nothing is wrong 
with the drive sled.  Another drive sled that goes in the same slot on 
the same computer that has another Linux distribution on it has none of 
the ata errors when it comes up.

On Tue, 12 Jul 2011, Samuel Thibault wrote:

> Jude DaShiell, le Tue 12 Jul 2011 06:32:56 -0400, a ?crit :
> > http://www.shellworld.net/~jdashiel/dmesg.log has the current dmesg 
> > output.  A little over 50k so I put it on my web page.
> 
> 50k is not a problem, so attaching it, so it's not lost.
> 
> Samuel
> 





-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.00.1107130243020.61...@freire1.furyyjbeyq.arg

Bug#633620: Info received (Bug#633620: installation-report: espeakup amdk8 wheezy to sid)

[Jude DaShiell]

http://www.shellworld.net/~jdashiel/dmesg.log has the current dmesg 
output.  A little over 50k so I put it on my web page. On Tue, 12 Jul 
2011, Debian Bug Tracking System wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian Install Team 
> 
> If you wish to submit further information on this problem, please
> send it to 633...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 
> 





-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.00.1107120631350.28...@freire1.furyyjbeyq.arg

Bug#633620: installation-report: espeakup amdk8 wheezy to sid

[Jude DaShiell]

Mostly successful, alsa can't seem to figure out what sound card I have 
but the system still talks.  Soud card identification capability was lost 
in wheezy and not recovered in sid.On Tue, 12 Jul 2011, Samuel Thibault 
wrote:

> So, was it successful?
> 
> If so, great, and we'll happily close the bug report and thank you for
> reporting it (we also need successful report, not only issue reports)
> 
> Else, please provide details :)
> 
> Samuel
> 
> 





-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.bsf.2.00.1107120556520.26...@freire1.furyyjbeyq.arg

Bug#633620: installation-report: espeakup amdk8 wheezy to sid

[Jude DaShiell]

Package: installation-reports
Version: 2.45
Severity: normal



-- Package-specific info:

Boot method: network apt-get dist-upgrade
Image version: 
Date: 

Machine: amd k8 athelon
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20110517-23:41"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux md 2.6.32-5-486 #1 Tue Mar 8 21:03:02 UTC 2011 i686 GNU/Linux
lspci -knn: 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory 
Controller [10de:005e] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge 
[10de:0050] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] 
(rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB 
Controller [10de:005a] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB 
Controller [10de:005b] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:04.0 Multimedia audio controller [0401]: nVidia Corporation 
CK804 AC'97 Audio Controller [10de:0059] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: Intel ICH
lspci -knn: 00:06.0 IDE interface [0101]: nVidia Corporation CK804 IDE 
[10de:0053] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: pata_amd
lspci -knn: 00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA 
Controller [10de:0054] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: sata_nv
lspci -knn: 00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA 
Controller [10de:0055] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: sata_nv
lspci -knn: 00:09.0 PCI bridge [0604]: nVidia Corporation CK804 PCI Bridge 
[10de:005c] (rev a2)
lspci -knn: 00:0a.0 Bridge [0680]: nVidia Corporation CK804 Ethernet Controller 
[10de:0057] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: forcedeth
lspci -knn: 00:0b.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0c.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0d.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0e.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
lspci -knn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Address Map [1022:1101]
lspci -knn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] DRAM Controller [1022:1102]
lspci -knn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Miscellaneous Control [1022:1103]
lspci -knn: 05:00.0 VGA compatible controller [0300]: ATI Technologies Inc 
RV370 [Sapphire X550 Silent] [1002:5b63]
lspci -knn: Subsystem: PC Partner Limited Device [174b:1490]
lspci -knn: 05:00.1 Display controller [0380]: ATI Technologies Inc RV370 
seconda

Bug#633596: installation-report:

[Jude DaShiell]

Package: installation-reports
Version: 2.45
Severity: normal



-- Package-specific info:

Boot method: cd
Image version: http://people.debian.org/~sthibault/espeakup/espeakup-i386.iso 
6/10/2011
Date: 

Machine: amd athelon k8
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:




-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="6.0 (squeeze) - installer build 20110517-23:41"
X_INSTALLATION_MEDIUM=netboot

==
Installer hardware-summary:
==
uname -a: Linux md 2.6.32-5-486 #1 Tue Mar 8 21:03:02 UTC 2011 i686 GNU/Linux
lspci -knn: 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory 
Controller [10de:005e] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge 
[10de:0050] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] 
(rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB 
Controller [10de:005a] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: ohci_hcd
lspci -knn: 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB 
Controller [10de:005b] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:04.0 Multimedia audio controller [0401]: nVidia Corporation 
CK804 AC'97 Audio Controller [10de:0059] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: Intel ICH
lspci -knn: 00:06.0 IDE interface [0101]: nVidia Corporation CK804 IDE 
[10de:0053] (rev a2)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: pata_amd
lspci -knn: 00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA 
Controller [10de:0054] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: sata_nv
lspci -knn: 00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA 
Controller [10de:0055] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: sata_nv
lspci -knn: 00:09.0 PCI bridge [0604]: nVidia Corporation CK804 PCI Bridge 
[10de:005c] (rev a2)
lspci -knn: 00:0a.0 Bridge [0680]: nVidia Corporation CK804 Ethernet Controller 
[10de:0057] (rev a3)
lspci -knn: Subsystem: Elitegroup Computer Systems Device [1019:1b51]
lspci -knn: Kernel driver in use: forcedeth
lspci -knn: 00:0b.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0c.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0d.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:0e.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge 
[10de:005d] (rev a3)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100]
lspci -knn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Address Map [1022:1101]
lspci -knn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] DRAM Controller [1022:1102]
lspci -knn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 
[Athlon64/Opteron] Miscellaneous Control [1022:1103]
lspci -knn: 05:00.0 VGA compatible controller [0300]: ATI Technologies Inc 
RV370 [Sapphire X550 Silent] [1002:5b63]
lspci -knn: Subsystem: PC Partner Limited Device [174b:1490]
lspci -knn: 05:00.1 Display control