Re: Installation Errors
Andrew, I believe it would meet the needs of the text console user community - many blind use text mode. If the minimum Debian Net Install iso would include nmtui. I know there's a way of connecting to Internet without it, but nmtui is very easy to use for even people like me who cannot remember the several commands needed to get networking on a text console, ifup and ifconfig I think I remember, it's difficult for me. nmtui is really easy it should be included. That way a user could make a SID version of Debian and have a rolling release by just taking the latest net install iso and changing /etc/apt/sources.list files to sid / unstable. Thanks, David
Re: Installation Errors
Andrew, I didn't file a bug because I have no idea what package caused the problem. I just sent this message (below my signature). 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 I'd be happy to file a bug report but I have no idea what the problem is. Usually it's a lot easier because it's not as big a problem. I cannot log in as user in text mode (in the text console) or in lightdm to get into Mate. I used the latest Alpha 2 that has the firmware. debian-live-11.6.0-amd64-mate+nonfree.iso When a new version is released I'll try that. Best regards, David On Sun, Mar 19, 2023, 17:19 Andrew M.A. Cater wrote: > On Sun, Mar 19, 2023 at 01:23:39PM -0400, D.J.J. Ring, Jr. wrote: > > Awesome, thanks! > > > > How can we get those that make the mini disk or the other iso files to > put > > in nmtui so that if a person that wants a text only installation as many > > blind users like have an easy way to connect without installing the GUI > > graphical desktop. > > > > nmtui and nmcli are both part of Network Manager which pulls in other > dependencies but it shouldn't be a problem in some sense. It might mean > adding Network Manager as part of Debian standard packages and the > recent trend is to cut down on the number of Debian packages installed > to allow for smaller minimum machines, containers and VMs. > > > Also it was promised that the installer would have an option to boot > > directly into text mode for those users who want this. > > > > *Which* installer? If you install using the debian-live media, then I think > all bets are off as far as accessibility goes for someone visually > impaired - > though the Debian-live standard .iso is probably OK since it includes only > text mode programs. > > The text mode install is directly there in a Debian > netinst as is the expert text mode install which asks all the questions > to include those at lower priority. I'd need to check - but I'm fairly > sure that the Bookworm installer coming up has a speech install option > and also a high contrast text mode install. > > > No one answered my bug report about not being able to log in using my > user > > account, so I will use "smartctl -t long" and see what is happening to my > > hard drive! > > > > Which bug report number, please? > > > Thanks, > > > > David > > > > > > With every good wish, as ever, > > Andy Cater > > > > > > > > > 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 i
Re: Installation Errors
Awesome, thanks! How can we get those that make the mini disk or the other iso files to put in nmtui so that if a person that wants a text only installation as many blind users like have an easy way to connect without installing the GUI graphical desktop. Also it was promised that the installer would have an option to boot directly into text mode for those users who want this. No one answered my bug report about not being able to log in using my user account, so I will use "smartctl -t long" and see what is happening to my hard drive! Thanks, David On Fri, Mar 17, 2023 at 12:56 PM Jude DaShiell wrote: > 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 > > >
Installation Errors
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
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
No, because the installer still might be selecting the wrong sound card, it's usually the second choice, so even without sound I press enter to at least choose something. How can I chose the sound card, I'll chose them one by one and try. David On Tue, Jan 18, 2022, 03:21 Samuel Thibault wrote: > D.J.J. Ring, Jr., le lun. 17 janv. 2022 22:01:59 -0500, a ecrit: > > Using firmware-10.11.0-amd64 installer, I gave this command: > > > > amixer -c 0 set IEC958,0 off > > > > I didn't get a response because my sound cards were renumbered. > > Ah, yes, sure. > > > So I changed the command to: > > amixer -c 1 set IEC958,0 off > > > > This is the response I received. > > > > Simple mixer control 'IEC958',0 > > Capabilities: pswitch pswitch-joined > > Playback channels: Mono > > Mono: Playback [off] > > And that didn't make espeakup start speaking? > > Samuel >
Bug#1002976: Debian 11
I just tried the mini iso again, the error about firmware was about the installer language question, it then asked me if I had a disk with firmware and if so to install it. This looks normal to me. I have since learned hot to download all the firmware and put it on my usb stick in a folder named 'firmware", when I do this, the mini.iso is able to see my wifi card and asks me the network ID number and password for my wifi and it will connect. Best regards, David On Mon, Jan 17, 2022 at 3:33 AM Samuel Thibault wrote: > D.J.J. Ring, Jr., le dim. 16 janv. 2022 21:44:55 -0500, a ecrit: > > The mini iso just gave me an error that firmware was missing for my wifi > - I > > found the instructions on how to load firmware and put it in a FAT > partition on > > USB stick in a directory named /firmware. No more error. > > That was not the question. Please *exactly* answer the question I am > asking: > > *When* was this error precisely? Before or after the installer language > question? > > That's the information I need, if you don't provide it we'll be unused > what works and what doesn't work, and won't be able to fix the bug. > > Samuel >
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
On Mon, Jan 17, 2022 at 4:55 AM Samuel Thibault wrote: > Hello, > > Thanks for the information. > > D.J.J. Ring, Jr., le dim. 16 janv. 2022 22:12:29 -0500, a ecrit: > > I already noticed something, in Buster, my digital card isn't listed > > with the cat /proc/asound/cards command. > > Yes, that's because in the bullseye case you have used the mini.iso. As > I wrote, please rather use the netinst bullseye iso image. The mini.iso > image was only to check whether the presence of the i915 driver would > help. > > > ## Output of amixer -c 0 scontents and amixer -c 1 scontents for the > Bullseys > > mini_amixer1contents > > > > > > ## Output of amixer -c 0 scontents amixer -c 1 scontents and amixer -c 1 > > 10.11.0_amixer1contents > > One thing I notice is this: > > Simple mixer control 'IEC958',0 > Capabilities: pswitch pswitch-joined > Playback channels: Mono > Mono: Playback [off] > > It's off in the Buster case and on in the Bullseye case. I guess you are > not using the IEC958 output. > > Could you try running this inside the bullseye installer: > > amixer -c 0 sset IEC958,0 off > > samuel > Hello Samuel, I'm trying to be very careful to do whatever you tell me, but I will probably make a mistake, but not on purpose, just because I misunderstood. Here's what I did. Using firmware-10.11.0-amd64 installer, I gave this command: amixer -c 0 set IEC958,0 off I didn't get a response because my sound cards were renumbered. So I changed the command to: amixer -c 1 set IEC958,0 off This is the response I received. Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] About the firmware error, it's right after language selection saying that some of my hardware requires firmware and that I should insert a disk with firmware on it. That looks normal to me. While my computer has a digital sound output, I don't use it, I use the small speaker 3.5mm TRS (tip, ring, sleeve) plug like music players use to go to an amplified speaker. Regards, David
Bug#1002976: Debian 11
Samuel, It was just an error that I needed firmware for my WiFi. I put firmware-iwlwifi_20210818-1_all.deb in a FAT formatted USB stick in /firmware and everything was happy. Thanks, David On Sun, Jan 16, 2022 at 7:13 PM Samuel Thibault wrote: > D.J.J. Ring, Jr., le ven. 14 janv. 2022 08:55:16 -0500, a ecrit: > > You gave me a mini.iso to try but when I booted from it, it gave me an > error > > that firmware for my WiFi was needed. > > Just to make sure, when was this error precisely? Before or after the > installer language question? > > Samuel >
Bug#1002976: Debian 11
The mini iso just gave me an error that firmware was missing for my wifi - I found the instructions on how to load firmware and put it in a FAT partition on USB stick in a directory named /firmware. No more error. Thanks you. David On Sun, Jan 16, 2022 at 7:15 PM Samuel Thibault wrote: > D.J.J. Ring, Jr., le ven. 14 janv. 2022 08:55:16 -0500, a ecrit: > > You gave me a mini.iso to try but when I booted from it, it gave me an > error > > that firmware for my WiFi was needed. > > Just to make sure, when was this error precisely? Before or after the > installer language question? > > Samuel > >
Bug#1002976: Debian 11
Sorry, Samuel, you misunderstand me. You gave me a mini.iso to try but when I booted from it, it gave me an error that firmware for my WiFi was needed. I do not have access to Ethernet, our housing has WiFi supplied to us only. So I could not test your mini.iso. Is there a way I can put the needed wifi firmware into the iso, or somehow be able to try your iso? Best wishes, David On Fri, Jan 14, 2022, 08:08 Samuel Thibault wrote: > D.J.J. Ring, Jr., le ven. 14 janv. 2022 08:00:27 -0500, a ecrit: > > Is there a way to use your mini iso somehow and load the wifi modules? > > Not directly, but that is unrelated. We don't need you to get the > network working, the only thing which is at stake is getting sound > working. > > Samuel >
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
It might have asked for the language, but I had no sound. I know I didn't get as far as networking, but I probably got as far as language and keyboard, I've done installs so much recently I just didn't notice. I'll try it again, I thought it was too soon to have logs. Usually when I go to the other console, I just have busybox and I don't know how to mount a CD stick with busy box. I'll try it again. David On Sat, Jan 8, 2022 at 8:53 PM Samuel Thibault wrote: > D.J.J. Ring, Jr., le sam. 08 janv. 2022 20:38:43 -0500, a ecrit: > > First, the mini.iso tried over and over to detect my soundcard, > > over and over, what do you mean? Was it failing to emit any sound at > all? > > > then it went to ask if I had a USB stick with Debian on it, > > didn't it first ask for the language? > > Did you try to press alt-f2 to get to the second console? > > Samuel >
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
No, luck. First, the mini.iso tried over and over to detect my soundcard, I currently have 3, first one is usually digital, next is PCH analog, I use that, and I had my USB camera plugged in. It kept repeating in a loop for 5 minutes, then I finally chose soundcard #1 then it went to ask if I had a USB stick with Debian on it, so I just pressed enter, thinking it was talking about the mini.iso. It went around and around for a good 10 minutes before I had decided it wasn't going to work. So again, no luck with the mini.iso. Best wishes, David On Sat, Jan 8, 2022 at 5:22 PM Samuel Thibault wrote: > D.J.J. Ring, Jr., le sam. 08 janv. 2022 16:34:09 -0500, a ecrit: > > This is in bash, not busy box, right? I can't figure out busybox! > > busybox is mostly like bash. > > > At what time do I mount a USB stick, > > The main menu will be fine. > > > and where is the command to save installer logs to it? > > The syslog is already in /var/log/syslog > > Samuel >
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
Is there anything else I can do to help solve this problem? I just tried the last daily iso with firmware with no luck. Also I've discussed the problem with GRUB inserting an entry in the EFI boot automatically which overrides user setting in BIOS. That means if I last booted into Debian I will go directly to Debian without having the ability to press F2 (or whatever key is needed to access BIOS settings).. I mentioned that this caused a problem on a multi system boot, especially for those of us who cannot see well, but also for everyone because the only way to change this is either to open up the computer or laptop and reset the BIOS by pressing a rubber domed switch which I suppose grounds the capacitor is there to holds a voltage on the computer CMOS to keep settings, pushing the little switch puts the voltage to zero and restore the factory settings. There is a problem and I'm trying to get someone to fix it. It's probably an unfortunate consequence of this "feature" - GRUB would work just right without this feature, and I cannot think of any reason that this "feature" exists. It appears to be a bug. It's certainly understandable to those who who must now take extraordinary measures to reset their BIOS by resetting the CMOS. For blind persons who have already obtained sighted help to et up their BIOS the way they want it, to boot from USB HD - a USB stick, it's totally unwanted and very inconvenient. I have no idea if GRUB is aware of this bug. I believe even if GRUB is intended to do this, it shouldn't, it seems to be be an unfortunate consequence of their work. Even if it can be overridden, it is much too complicated for the average computer user. (Some kind member of this list sent me instructions to override this new behavior of GRUB, but they are extremely complicated. If anything this "feature" should be enabled only as an option. I've just subscribed to GRUB bugs list to tell them of this, hopefully it can be fixed because it overrides the user's BIOS settings. Best wishes to all, David On Tue, Jan 4, 2022 at 2:54 PM D.J.J. Ring, Jr. wrote: > I have already done that, did it not go through? I did receive a message > saying that the message I sent because it didn't mention a package would be > disregarded. > It would have been sent from n...@arrll.net - any way of checking > further? Darn it, I should have BCC it to you, Samuel. > > Thanks, > > David > > On Tue, Jan 4, 2022 at 3:53 AM Samuel Thibault > wrote: > >> Hello, >> >> As already mentioned, please do this: >> >> install with the Buster image, and use reportbug to send the >> installation information, just like you did with Bullseye on Mon, 3 Jan >> 2022 14:18:39 -0500. >> >> Really, do please do that. >> >> Samuel >> >
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
I have already done that, did it not go through? I did receive a message saying that the message I sent because it didn't mention a package would be disregarded. It would have been sent from n...@arrll.net - any way of checking further? Darn it, I should have BCC it to you, Samuel. Thanks, David On Tue, Jan 4, 2022 at 3:53 AM Samuel Thibault wrote: > Hello, > > As already mentioned, please do this: > > install with the Buster image, and use reportbug to send the > installation information, just like you did with Bullseye on Mon, 3 Jan > 2022 14:18:39 -0500. > > Really, do please do that. > > Samuel >
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
On Tue, Jan 4, 2022, 01:09 Philip Hands wrote: > "D.J.J. Ring, Jr." writes: > > > Yes, I said that, but I am under the impression that whatever went wrong > > happened before partitions were mounted. > > > > I remembered using that advance menu configuration which I was unable to > > find in Bullseye - at least the same exact thing with the ability of > > obtaining an IP address and downloading files. I thought these files > were > > lost if the logs weren't sent to a web server or written during > > installation to a mounted hard drive. > > I think you've been misinformed there, unless you are aborting the > install early because you cannot drive it without the sound working. > > Assuming the install completes, the complete logs, including what happened > early in the install, are copied from the installer's /var/log (which is > in RAM) to the target system's /var/log/installer, where they can be > found once one boots the resulting installed system. > > Of course if you are not able to complete the install, because the lack > of working sound makes that impossible for you, then it will not get as far > as writing the logs to the target system's disk for you. > > > No errors are ever seen or heard - except that there is no sound after > the > > installer probes for sound card (press enter if this is your sound card, > > etc.). > > > > I'm going to install Bullseye once again because right now I have Buster > - > > but the sound is working in Buster and the screen readers orca and > console > > are both working. and sound from videos in the browser are all working. > > Now if I can only get this in Bullseye. > > If you have working buster, you could also try upgrading that to > bullseye to see if that ends up with a working setup. > > That ought to help narrow down whether the problem is really in the > installer, or is related to other changes between the releases. > > BTW I find `etckeeper` very useful for seeing what changes on a system > (it creates a git repository under /etc for you, and records changes > that happen), so you could install that before upgrading. It also > records the versions of packages that get changed in the git log as well > as the changes to files under /etc when you upgrade packages. > > Cheers, Phil. > -- > |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. > |-| http://www.hands.com/http://ftp.uk.debian.org/ > |(| Hugo-Klemm-Strasse 34, 21075 Hamburg,GERMANY > Thanks, Phil. I tried the daily Sid unstable and it also has no working sound screen reader during but once finished it's there. I'll believe you about the files because I cannot find an advanced menu that installs the screen reader like Buster.had. Buster is much easier to install. I'm going to try another installer tomorrow. David
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
Yes, I said that, but I am under the impression that whatever went wrong happened before partitions were mounted. I remembered using that advance menu configuration which I was unable to find in Bullseye - at least the same exact thing with the ability of obtaining an IP address and downloading files. I thought these files were lost if the logs weren't sent to a web server or written during installation to a mounted hard drive. No errors are ever seen or heard - except that there is no sound after the installer probes for sound card (press enter if this is your sound card, etc.). I'm going to install Bullseye once again because right now I have Buster - but the sound is working in Buster and the screen readers orca and console are both working. and sound from videos in the browser are all working. Now if I can only get this in Bullseye. Is there anything I can run while I have this installed? I'm going to wait for your response, it's past midnight on the Continent and 2000 hours here on the east coast USA. Also any suggestion of what to install thjat might be more helpful? Maybe the daily SID installer? Best wishes, David On Mon, Jan 3, 2022 at 8:35 PM Samuel Thibault wrote: > D.J.J. Ring, Jr., le lun. 03 janv. 2022 20:26:54 -0500, a ecrit: > > You mean take a video of the screen when I am trying to install Bullseye? > > Yes. > > > I don't get any error messages at all, it just doesn't speak to me. > > At some point you mentioned some errors: > > “the errors precede writing to disk.” > > Samuel >
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
Samuel, You mean take a video of the screen when I am trying to install Bullseye? I don't get any error messages at all, it just doesn't speak to me. Regards, David On Mon, Jan 3, 2022 at 7:03 PM Samuel Thibault wrote: > I'd like to emphasize this: > > john doe, le lun. 03 janv. 2022 09:39:41 +0100, a ecrit: > > - As far as I understand it, everything is working fine on Buster but > > not on Bullseye, tarring the logs from a Buster installation and from > > Bullseye might give us some clues on where this is failing. > > Yes, please do this, that should be extremely informative. > > Any error message from the kernel will be visible in there. > > Possibly there are some error messages from alsa itself, which may not > be there. Possibly you could use a smartphone to make a recording of the > screen while you are booting the bullseye installer, so we can see which > error messages you get there? > > Samuel >
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
No, John, it doesn't. The errors are being made prior to installation. I previously used something to copy these logs to a pastebin while I was installing, this was done somewhere around the time of package selection because networking was running. There was some screen where I could get these errors because I had been told they would be lost otherwise because they were prior to the installer writing to the mounted partition. At the time of the errors I have no system running, only the installer, there are no consoles with bash running, only busybox. If you don't know the answer, that's fine, but can you direct me to someone who does? I remembered the person who told me what to do to get this hidden menu where I can hopefully send up into a pastebin the errors or maybe even correctly select my sound card. I haven't tried it, and I have no idea why this isn't documented because I've never seen it except this person knew about it. Here's what I found out. It might be that this selection is available but I couldn't find it and I've been asking you and perhaps you don't know about it, but here it is. I still don't know if this will do what I did before to save files before the installation because the installation is successful, but the installation is also inaccessible. Here it is: You will need to go into the numbered menu during install. At the boot prompt before any speech comes up: 1) hit a then hit enter, 2) hit s then hit enter, 3) hit x then hit enter. Once that's done pick your sound card and after that you should hear a screen with a numbered menu on it. You need to set message priority to low which asks the most questions once done. You also want to choose save log files and store those on disk. All of those log files left on /mnt will need to be sent to debian-boot in order for you to get some help. I do this routinely whenever doing a debian install simply asa defensive measure. You get the numbered menu by hitting the < sign at prompts until the numbered menu shows up. That'll have about 25 choices in it and hitting enter in that menu does the next default part of the installation. You likely will get into the numbered menu after networking gets set up. Thanks, David
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
John Doe, Someone told me of a method of saving log files from the installer before it writes to the hard drive it's going to install to. The error occurs prior to writing to any partition. If these errors are kept in system RAM until the partitions are formatted and then written to that partition, all is OK, But the errors precede writing to disk. I've asked already, maybe you answered with your "debug d-i" comment but I have no idea what it means or how to use it to help the boot and installer developers. It seems this is an installer problem which wouldn't be written in the logs because it occurs before partitioning? Thanks, David
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
On Mon, Jan 3, 2022, 02:09 john doe wrote: > On 1/3/2022 12:18 AM, D.J.J. Ring, Jr. wrote: > > On Sun, Jan 2, 2022 at 8:25 AM john doe wrote: > > > >> On 1/2/2022 1:56 PM, D.J.J. Ring, Jr. wrote: > >>> On Sun, Jan 2, 2022, 03:59 Holger Wansing > wrote: > >>> > >>>> Hi, > >>>> > >>>> Am 2. Januar 2022 02:40:16 MEZ schrieb "David J. Ring, Jr." < > >> n...@arrl.net > >>>>> : > >>>>> > >>>>> lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation > Broadwell-U > >>>> Audio Controller [8086:160c] (rev 09) > >>>> > >>>> > >>>> As I already wrote: > >>>> my best guess for this one would be > >>>> https://www.debian.org/releases/stable/debian-installer/#errata > >>>> > >>>> > >>> > >>> So is this fixed? Does the daily our weekly installer with firmware > allow > >>> speech to be heard during installation? > >>> > >> > >> No it is not. > >> > >> Pick the desired architecture at (1) and remember that this is a work > >> in progress! > >> > >> Feedback from the comunity will eventually make this workable for all of > >> us. > >> > >> > >> 1) > >> > >> > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/daily-builds/sid_d-i/current/ > >> > >> -- > >> John Doe > >> > > > > Hello John Doe, > > > > I picked the correct architecture, downloaded, checked the sha250sum, > then > > used dd to make a usb bootable usb stick. > > > > It detected my sound card, but after that no sound was heard in the > > accessible install. > > > > I remember that someone told me there was a switch to somehow save log > > files while installing and a way to upload them to pastebin web site, > but I > > have forgotten how to do that, and I cannot find any documentation to > help > > me. > > > > I need something to tell the developers about the problems with the > > installer without actually installing Debian, as I have already installed > > Debian and I have the installer logs. > > > > How are you able to "Install Debian With Speach' if the installer does > not speak after having detecting your sound card? > > -- > John Doe > I use a magnifier glass to read the screen. Best to you, David > >
Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
On Sun, Jan 2, 2022 at 8:25 AM john doe wrote: > On 1/2/2022 1:56 PM, D.J.J. Ring, Jr. wrote: > > On Sun, Jan 2, 2022, 03:59 Holger Wansing wrote: > > > >> Hi, > >> > >> Am 2. Januar 2022 02:40:16 MEZ schrieb "David J. Ring, Jr." < > n...@arrl.net > >>> : > >>> > >>> lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U > >> Audio Controller [8086:160c] (rev 09) > >> > >> > >> As I already wrote: > >> my best guess for this one would be > >> https://www.debian.org/releases/stable/debian-installer/#errata > >> > >> > > > > So is this fixed? Does the daily our weekly installer with firmware allow > > speech to be heard during installation? > > > > No it is not. > > Pick the desired architecture at (1) and remember that this is a work > in progress! > > Feedback from the comunity will eventually make this workable for all of > us. > > > 1) > > https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/daily-builds/sid_d-i/current/ > > -- > John Doe > Hello John Doe, I picked the correct architecture, downloaded, checked the sha250sum, then used dd to make a usb bootable usb stick. It detected my sound card, but after that no sound was heard in the accessible install. I remember that someone told me there was a switch to somehow save log files while installing and a way to upload them to pastebin web site, but I have forgotten how to do that, and I cannot find any documentation to help me. I need something to tell the developers about the problems with the installer without actually installing Debian, as I have already installed Debian and I have the installer logs. In other words, I need to run the installer and when it doesn't speak, I need to find the reason and send it to someone. Regards, David
Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard
On Sun, Jan 2, 2022, 03:59 Holger Wansing wrote: > Hi, > > Am 2. Januar 2022 02:40:16 MEZ schrieb "David J. Ring, Jr." >: > > > >lspci -knn: 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U > Audio Controller [8086:160c] (rev 09) > > > As I already wrote: > my best guess for this one would be > https://www.debian.org/releases/stable/debian-installer/#errata > > > Holger > > > -- > Sent from /e/ OS on Fairphone3 > Holger, So is this fixed? Does the daily our weekly installer with firmware allow speech to be heard during installation? Thank you, David >
Re: Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can
On Sun, Jan 2, 2022, 00:39 john doe wrote: > On 1/2/2022 1:20 AM, D.J.J. Ring, Jr. wrote: > > I made a new partition for /home and I reinstalled Debian, this time I > > could lot in to MATE and I could log into the CLI. > > > > But the issue remains of after the Installation disk detects my sound > card, > > it seems to find my sound card, but immediately after finding it, no > > further sound is heard. > > > > This remains. > > > > That would be lovely if you could bottom post instead of top posting. > > The only thing that we can help you with is an issue with the Debian > installer. > > I must say, I lost track of what is the issue you are having so please > do the following: > > 1) Install Debian from scratch > > That is, let d-i wipe the all content of your drive, this will result in > a fresh install of Debian. > > > 2) Attach all files from '/var/log/installer' to this bug report. > > Please attached all of those files in one e-mail or create a tarball and > attached it: > > $ tar -C var/log -cf installer.tar.bz2 installer > > > 3) Take the time to describe one issue you are having per bugreport > > The more explicit you are and stick to the point the better we will be > able to help you. > > > Granted, this will take sometime to do but that is the only way we will > be able to fix the issue! > > > P.S. > > By 'we' I mean the comunity. > > -- > John Doe > I've done that and the only problem left is the installer doesn't speak, but after rebooting, everything is fine. Thanks very much. I've filed a new bug report as the other issues are gone. Regards, David > >
Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can
I made a new partition for /home and I reinstalled Debian, this time I could lot in to MATE and I could log into the CLI. But the issue remains of after the Installation disk detects my sound card, it seems to find my sound card, but immediately after finding it, no further sound is heard. This remains. Thanks for the help. David On Sat, Jan 1, 2022 at 6:16 PM D.J.J. Ring, Jr. wrote: > I don't know why when using the installer, not hearring espeak in console > isn't a installer issue. > > I believe I have already done what you are speaking of. > > I have /home/djringjr. > > At first I reused this, the installer permits NOT formatting a separate > /home partition. That's what I did. > > I had problems I could not log in as my regular named user using my old > /home/djringjr files. > > Then I reran the installer - again no sound during accessible > installation, This time I made up a brand new never before user name. > > The result was the very same, I could not log in with my user account, > only root. > > What is your next suggestion? > > There is an installer issue, not having speech during an accessible > installation is an installer issue . > > Making a brand new user account and not being able to log in might be > something else. Where do I go to get this part fixed? > > Thanks, > David > > On Sat, Jan 1, 2022 at 5:22 PM Holger Wansing > wrote: > >> Hi, >> >> Am 1. Januar 2022 21:38:39 MEZ schrieb "D.J.J. Ring, Jr." > >: >> >No on the first run after installation, I cannot log in using my user >> >account. >> > >> >I tried installation again, still keeping /home partition data but using >> a >> >brand-new user account. This installation also failed in the exact same >> >way. I had voice at the lightdm login prompt but I could not log in. I >> >could log in as previously by using root. >> > >> >So reusing by /home/djringjr folder won't let me log in, using a >> brand-new >> >user account with brand new files from /etc/skel won't let me run the >> GUI. >> >> When performing a default installation it is known, that logging in as a >> normal user. >> >> So, if you have over and over the same issue, using that unusual >> installation >> concept (re-using pre-existing home data), which is not officially >> supported by >> the installer, you should probably try a default install, without any >> old-home-data >> tricks - just for a test. >> >> If that works, you could then carefully merge your home data back into >> the new >> system. >> >> >> In summary, this all is not an installer issue, by the way. >> >> Holger >> >> >> >> >> -- >> Sent from /e/ OS on Fairphone3 >> >
Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can
I don't know why when using the installer, not hearring espeak in console isn't a installer issue. I believe I have already done what you are speaking of. I have /home/djringjr. At first I reused this, the installer permits NOT formatting a separate /home partition. That's what I did. I had problems I could not log in as my regular named user using my old /home/djringjr files. Then I reran the installer - again no sound during accessible installation, This time I made up a brand new never before user name. The result was the very same, I could not log in with my user account, only root. What is your next suggestion? There is an installer issue, not having speech during an accessible installation is an installer issue . Making a brand new user account and not being able to log in might be something else. Where do I go to get this part fixed? Thanks, David On Sat, Jan 1, 2022 at 5:22 PM Holger Wansing wrote: > Hi, > > Am 1. Januar 2022 21:38:39 MEZ schrieb "D.J.J. Ring, Jr." : > >No on the first run after installation, I cannot log in using my user > >account. > > > >I tried installation again, still keeping /home partition data but using a > >brand-new user account. This installation also failed in the exact same > >way. I had voice at the lightdm login prompt but I could not log in. I > >could log in as previously by using root. > > > >So reusing by /home/djringjr folder won't let me log in, using a brand-new > >user account with brand new files from /etc/skel won't let me run the GUI. > > When performing a default installation it is known, that logging in as a > normal user. > > So, if you have over and over the same issue, using that unusual > installation > concept (re-using pre-existing home data), which is not officially > supported by > the installer, you should probably try a default install, without any > old-home-data > tricks - just for a test. > > If that works, you could then carefully merge your home data back into the > new > system. > > > In summary, this all is not an installer issue, by the way. > > Holger > > > > > -- > Sent from /e/ OS on Fairphone3 >
Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can
To be clear, On the first run after installation, I could not log in using my user account. I tried installation again, still keeping /home partition data but using a brand-new user account. This installation also failed in the exact same way. I had voice at the lightdm login prompt but I could not log in. I could log in as previously by using root. At that time, I didn't know a way to disable lightdm login and just log in with the console. I suspect I'd get the same result as I do now, that I could not log in with any user account, only the supervisor account, root. At that time, I just suspected that my user account was just having problems accessing Xorg, that's why I included the Xorg error logs, now I see that the problem goes beyond this, that I cannot log in with any user either using my old djringjr home folder which works if I reinstall latest Debian 10, nor a previously non-existing username which created new file folder populated by /etc/skel files. I was able in all cases able to log into both the cli and the GUI with root. I was able to log into root in the CLI then su to my original username in all cases but starting GUI still failed. Regards, David On Sat, Jan 1, 2022, 15:38 D.J.J. Ring, Jr. wrote: > No on the first run after installation, I cannot log in using my user > account. > > I tried installation again, still keeping /home partition data but using a > brand-new user account. This installation also failed in the exact same > way. I had voice at the lightdm login prompt but I could not log in. I > could log in as previously by using root. > > So reusing by /home/djringjr folder won't let me log in, using a brand-new > user account with brand new files from /etc/skel won't let me run the GUI. > > Since then I've discovered with my current installation not only can't I > access the GUI but additionally I cannot access the CLI at least directly. > I can login as root then su to my user name and access my user CLI but > running startx still fails. > > I can install the last version of the previous Debian before Bullseye > perfectly with my current /home folder. > > Best wishes, > > David > > Regards, > > > > On Sat, Jan 1, 2022, 14:39 Holger Wansing wrote: > >> Hi, >> >> "D.J.J. Ring, Jr." wrote (Sat, 1 Jan 2022 13:37:20 >> -0500): >> > 1. Cannot boot into MATE GUI means that I cannot boot into the MATE >> > Graphical User Interface with the user account - which is what is >> expected >> > to happen after a normal successful installation. I did some >> > investigation into this. >> > >> > This is what I did: . I disabled lightdm using systemctl disable >> lightdm >> > then more recently I used the root command "systemctl set-default >> > multi-user.target" and now I see I cannot even log in as my regular >> user. >> >> This is what I had expected, so in the first run it's not an issue with >> the >> MATE GUI. >> >> > I tried a new named user and did the same installation, I had the very >> same >> > problems with the new username. >> > >> > My /home/djringjr/ folder was used successfully with the last Debian >> Buster >> > release. >> >> Hmm, I wonder what that means exactly, as well as the following sentence: >> >> > [...] When >> > installing for my normal user account, I do not format /home/myuser >> folder. >> >> Do you re-use an old/existing home folder of some user account somehow >> for the >> new user? >> I don't know if that is supposed to work. >> I only know the szenario, where a complete new home folder is created >> automatically, when a new user is added to the system (with the "useradd" >> command). >> >> > I have entered the root account and re-entered my useraccount >> password. I >> > have done this several times. Remember this also happened when I had an >> > entirely new user account with a newly made /home/newuser folder. >> >> So you have tried, to log in as root on the console and type >> "adduser yourusername" to create a completely new user? >> And see if you can successfully login into that new account with >> "su -l yourusername" ? >> >> >> > I know the username password is correct because as root I enter "su >> > myusername" and I am in user account, then from my user account, I type >> > "su myusername" and I receive a prompt for my password. I have further >> > checked by entering an incorrect password and received "authentication >> > failure" response. &g
Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can
No on the first run after installation, I cannot log in using my user account. I tried installation again, still keeping /home partition data but using a brand-new user account. This installation also failed in the exact same way. I had voice at the lightdm login prompt but I could not log in. I could log in as previously by using root. So reusing by /home/djringjr folder won't let me log in, using a brand-new user account with brand new files from /etc/skel won't let me run the GUI. Since then I've discovered with my current installation not only can't I access the GUI but additionally I cannot access the CLI at least directly. I can login as root then su to my user name and access my user CLI but running startx still fails. I can install the last version of the previous Debian before Bullseye perfectly with my current /home folder. Best wishes, David Regards, On Sat, Jan 1, 2022, 14:39 Holger Wansing wrote: > Hi, > > "D.J.J. Ring, Jr." wrote (Sat, 1 Jan 2022 13:37:20 -0500): > > 1. Cannot boot into MATE GUI means that I cannot boot into the MATE > > Graphical User Interface with the user account - which is what is > expected > > to happen after a normal successful installation. I did some > > investigation into this. > > > > This is what I did: . I disabled lightdm using systemctl disable > lightdm > > then more recently I used the root command "systemctl set-default > > multi-user.target" and now I see I cannot even log in as my regular user. > > This is what I had expected, so in the first run it's not an issue with > the > MATE GUI. > > > I tried a new named user and did the same installation, I had the very > same > > problems with the new username. > > > > My /home/djringjr/ folder was used successfully with the last Debian > Buster > > release. > > Hmm, I wonder what that means exactly, as well as the following sentence: > > > [...] When > > installing for my normal user account, I do not format /home/myuser > folder. > > Do you re-use an old/existing home folder of some user account somehow for > the > new user? > I don't know if that is supposed to work. > I only know the szenario, where a complete new home folder is created > automatically, when a new user is added to the system (with the "useradd" > command). > > > I have entered the root account and re-entered my useraccount password. > I > > have done this several times. Remember this also happened when I had an > > entirely new user account with a newly made /home/newuser folder. > > So you have tried, to log in as root on the console and type > "adduser yourusername" to create a completely new user? > And see if you can successfully login into that new account with > "su -l yourusername" ? > > > > I know the username password is correct because as root I enter "su > > myusername" and I am in user account, then from my user account, I type > > "su myusername" and I receive a prompt for my password. I have further > > checked by entering an incorrect password and received "authentication > > failure" response. > > > > root@debian:~# su djringjr > > djringjr@debian:/root$ su djringjr > > Password: [I enter the correct password\ > > djringjr@debian:/root$ exit > > exit > > djringjr@debian:/root$ su djringjr > > Password: [I enter an incorrect password\ > > su: Authentication failure > > djringjr@debian:/root$ > > > > You asked me to state the problems again, here they are. > > > > 1. During installation I chose accessible text installation, the > installer > > appeared to detect my sound card, but after that I hear no sound from the > > screen reader. > > That might be the issue described here: > https://www.debian.org/releases/stable/debian-installer/#errata > > I do not use a Braille device, so I cannot comment on > > Braille. I still have limited vision, so I was able to finish the > > installation. > > When I rebooted, I had screen reader, but there were additional problems. > > I also tried the live DVD to install and I had the exact problems. I > > believe I tried the 11.0 release with firmware four or five times, and I > > have tried the 11.2 firmware release at least four times, and the 11.2 > live > > release twice, all gave me the exact same problems. The system was > unusable > > as regular user in every case except it WAS usable in the console if I > > logged in as root, then logged in as username. > > > > 2. I cannot log in as my user account into console. This also means had > I > > not dis
Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can
Hello Holger Wansing, Thanks for helping me with these problems. Here are my answers to my best ability to answer them. 1. Cannot boot into MATE GUI means that I cannot boot into the MATE Graphical User Interface with the user account - which is what is expected to happen after a normal successful installation. I did some investigation into this. This is what I did: . I disabled lightdm using systemctl disable lightdm then more recently I used the root command "systemctl set-default multi-user.target" and now I see I cannot even log in as my regular user. I tried a new named user and did the same installation, I had the very same problems with the new username. My /home/djringjr/ folder was used successfully with the last Debian Buster release. If I reinstall the last Debian 10 firmware which I had been using prior to Bullseys 11.0 release which also failed in the exact same way, everything is excellent, my sound card is detected during accessible installation, when I boot i go to the lightdm screen and I can log in as my regular user. I also have sound as my regular user in GUI and also I have ORCA in the GUI. I have entered the root account and re-entered my useraccount password. I have done this several times. Remember this also happened when I had an entirely new user account with a newly made /home/newuser folder. When installing for my normal user account, I do not format /home/myuser folder. I know the username password is correct because as root I enter "su myusername" and I am in user account, then from my user account, I type "su myusername" and I receive a prompt for my password. I have further checked by entering an incorrect password and received "authentication failure" response. root@debian:~# su djringjr djringjr@debian:/root$ su djringjr Password: [I enter the correct password\ djringjr@debian:/root$ exit exit djringjr@debian:/root$ su djringjr Password: [I enter an incorrect password\ su: Authentication failure djringjr@debian:/root$ You asked me to state the problems again, here they are. 1. During installation I chose accessible text installation, the installer appeared to detect my sound card, but after that I hear no sound from the screen reader. I do not use a Braille device, so I cannot comment on Braille. I still have limited vision, so I was able to finish the installation. When I rebooted, I had screen reader, but there were additional problems. I also tried the live DVD to install and I had the exact problems. I believe I tried the 11.0 release with firmware four or five times, and I have tried the 11.2 firmware release at least four times, and the 11.2 live release twice, all gave me the exact same problems. The system was unusable as regular user in every case except it WAS usable in the console if I logged in as root, then logged in as username. 2. I cannot log in as my user account into console. This also means had I not disabled graphical user log on with lightdm, I would not be able to log on to the MATE GUI as is the subject of my error report. 3. I can log into my root account in console, and before I disabled lightdm I was able to log in with lightdm to the MATE GUI, however, running orca -s says no speech available. See the error file I produced by running "orca -s 2> orcaerrors" then interrupting the terminal with control-c. I also get multiple AT-SPI errors which are in the attached orcaerrors file. . Best regards, David On Sat, Jan 1, 2022 at 11:56 AM Holger Wansing wrote: > Hi, > > "D.J.J. Ring, Jr." wrote (Sat, 1 Jan 2022 09:39:26 -0500): > > Thanks, > > > > Here they are. > > > > Regards, > > David > > > > On Sat, Jan 1, 2022 at 8:59 AM Holger Wansing > wrote: > > > You should provide the installer log files (to be found in > > > /var/log/installer). > > > Sent them compressed to this bugreport. > > From your logs it seems your installation was a success, I cannot see any > grave issues. > > > So, we need to go back to the beginning: > What are your problems, exaclty? > What do you do, and what happens? Which error message exactly, and so on... > > > The subject of this bug has "Cannot boot into MATE GUI". > What does this mean? Could it be, that just the password is not correct? > (Maybe you now have a different keyboard layout active than during > installation, or similar?) > > > > Holger > > > -- > Holger Wansing > PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 > orcaerrors Description: Binary data
Bug#1002921: installation-reports: No Screen Reader, Cannot boot into MATE GUI, Root only can
Also I just used systemctl set-default multi-user.target to change to a console log in. I cannot log in as user, only as root. GUI can also only be started as root. Have espeakup in console by as soon as log into Mate using root account, no sound, Orca setup has no speech settings. Regards, David On Sat, Jan 1, 2022 at 9:39 AM D.J.J. Ring, Jr. wrote: > Thanks, > > Here they are. > > Regards, > David > > On Sat, Jan 1, 2022 at 8:59 AM Holger Wansing > wrote: > >> Hi, >> >> "David J. Ring, Jr." wrote (Sat, 1 Jan 2022 00:11:22 >> -0500): >> > Boot method: USB >> > Image version: Image version: firmware-11.2.0-amd64-DVD-1.iso >> https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.2.0+nonfree/amd64/iso-dvd/firmware-11.2.0-amd64-DVD-1.iso >> 2021-12-18 >> > Date: >> > >> > Machine: Machine: Intense-PC2-BRW (IPC2) (System SKUNumber) >> > Partitions: >> > >> > >> > Base System Installation Checklist: >> > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it >> > >> > Initial boot: [ ] >> > Detect network card:[ ] >> > Configure network: [ ] >> > Detect media: [ ] >> > Load installer modules: [ ] >> > Clock/timezone setup: [ ] >> > User/password setup:[ ] >> > Detect hard drives: [ ] >> > Partition hard drives: [ ] >> > Install base system:[ ] >> > Install tasks: [ ] >> > Install boot loader:[ ] >> > Overall install:[ ] >> >> You did not provide useful information about the installation, so there is >> no way to debug your situation. >> >> You should provide the installer log files (to be found in >> /var/log/installer). >> Sent them compressed to this bugreport. >> >> I ran a test installation of Debian 11 with MATE, and everything seems to >> work >> fine so far... >> >> >> Holger >> >> >> >> >> -- >> Holger Wansing >> PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076 >> >
Bug#1002921: Log Files
Further to my bug report. Installation detects my sound card but no screen reader present. System inaccessible, only root can run MATE. User can only access CLI. REGARDS, David -- Forwarded message - From: David J. J. Ring, Jr. Date: Thu, Dec 30, 2021, 18:03 Subject: Log Files To: David JJ Ring Jr Log files [ 1838.994] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [ 1838.994] Build Operating System: linux Debian [ 1838.994] Current Operating System: Linux debian 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 [ 1838.994] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-10-amd64 root=UUID=2bb51d3e-ddb2-4a56-bf34-52e828bf8fe0 ro quiet [ 1838.994] Build Date: 16 December 2021 05:08:23PM [ 1838.994] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support) [ 1838.994] Current version of pixman: 0.40.0 [ 1838.994]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 1838.994] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 1838.994] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Dec 30 17:09:15 2021 [ 1838.995] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 1838.995] (==) No Layout section. Using the first Screen section. [ 1838.995] (==) No screen section available. Using defaults. [ 1838.995] (**) |-->Screen "Default Screen Section" (0) [ 1838.995] (**) | |-->Monitor "" [ 1838.995] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 1838.995] (==) Automatically adding devices [ 1838.995] (==) Automatically enabling devices [ 1838.995] (==) Automatically adding GPU devices [ 1838.995] (==) Max clients allowed: 256, resource mask: 0x1f [ 1838.995] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 1838.995]Entry deleted from font path. [ 1838.995] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 1838.995] (==) ModulePath set to "/usr/lib/xorg/modules" [ 1838.995] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 1838.995] (II) Loader magic: 0x561e372abe40 [ 1838.995] (II) Module ABI versions: [ 1838.995]X.Org ANSI C Emulation: 0.4 [ 1838.995]X.Org Video Driver: 24.1 [ 1838.995]X.Org XInput driver : 24.1 [ 1838.995]X.Org Server Extension : 10.0 [ 1838.996] (++) using VT number 7 [ 1838.996] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 1838.996] (II) xfree86: Adding drm device (/dev/dri/card0) [ 1839.009] (--) PCI:*(0@0:2:0) 8086:1616:8086:2010 rev 9, Mem @ 0xc000/16777216, 0xa000/536870912, I/O @ 0x4000/64, BIOS @ 0x/131072 [ 1839.009] (II) LoadModule: "glx" [ 1839.009] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 1839.010] (II) Module glx: vendor="X.Org Foundation" [ 1839.010]compiled for 1.20.11, module version = 1.0.0 [ 1839.010]ABI class: X.Org Server Extension, version 10.0 [ 1839.010] (==) Matched modesetting as autoconfigured driver 0 [ 1839.010] (==) Matched fbdev as autoconfigured driver 1 [ 1839.010] (==) Matched vesa as autoconfigured driver 2 [ 1839.010] (==) Assigned the driver to the xf86ConfigLayout [ 1839.010] (II) LoadModule: "modesetting" [ 1839.010] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 1839.010] (II) Module modesetting: vendor="X.Org Foundation" [ 1839.010]compiled for 1.20.11, module version = 1.20.11 [ 1839.010]Module class: X.Org Video Driver [ 1839.010]ABI class: X.Org Video Driver, version 24.1 [ 1839.010] (II) LoadModule: "fbdev" [ 1839.010] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 1839.010] (II) Module fbdev: vendor="X.Org Foundation" [ 1839.010]compiled for 1.20.0, module version = 0.5.0 [ 1839.010]Module class: X.Org Video Driver [ 1839.010]ABI class: X.Org Video Driver, version 24.0 [ 1839.010] (II) LoadModule: "vesa" [ 1839.010] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 1839.010] (II) Module vesa: vendor="X.Org Foundation" [ 1839.010]compiled for 1.20.9, module version = 2.5.0 [ 1839.010]Module class: X.Org Video Driver [ 1839.010]ABI class: X.Org Video Driver, version 24.1 [ 1839.010] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 1839.010] (II) FBDEV: driver for framebuffer: fbdev [ 1839.010] (II) VESA: driver for VESA chipsets: vesa [ 1839.023] (II) modeset(0):
Bug#1002921: Xlog
Further to my bug report -- Forwarded message - From: David J. J. Ring, Jr. Date: Thu, Dec 30, 2021, 18:13 Subject: Xlog To: David JJ Ring Jr [ 5570.481] X.Org X Server 1.20.11 X Protocol Version 11, Revision 0 [ 5570.486] Build Operating System: linux Debian [ 5570.488] Current Operating System: Linux debian 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 [ 5570.488] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-10-amd64 root=UUID=2bb51d3e-ddb2-4a56-bf34-52e828bf8fe0 ro quiet [ 5570.492] Build Date: 16 December 2021 05:08:23PM [ 5570.493] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support) [ 5570.495] Current version of pixman: 0.40.0 [ 5570.499]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 5570.499] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 5570.506] (==) Log file: "/home/djringjr/.local/share/xorg/Xorg.1.log", Time: Thu Dec 30 18:11:26 2021 [ 5570.507] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 5570.508] (==) No Layout section. Using the first Screen section. [ 5570.508] (==) No screen section available. Using defaults. [ 5570.508] (**) |-->Screen "Default Screen Section" (0) [ 5570.508] (**) | |-->Monitor "" [ 5570.508] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 5570.508] (==) Automatically adding devices [ 5570.508] (==) Automatically enabling devices [ 5570.508] (==) Automatically adding GPU devices [ 5570.508] (==) Max clients allowed: 256, resource mask: 0x1f [ 5570.508] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 5570.508]Entry deleted from font path. [ 5570.508] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 5570.508] (==) ModulePath set to "/usr/lib/xorg/modules" [ 5570.508] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 5570.508] (II) Loader magic: 0x55ae00bf4e40 [ 5570.508] (II) Module ABI versions: [ 5570.508]X.Org ANSI C Emulation: 0.4 [ 5570.508]X.Org Video Driver: 24.1 [ 5570.508]X.Org XInput driver : 24.1 [ 5570.508]X.Org Server Extension : 10.0 [ 5570.508] (++) using VT number 2 [ 5570.510] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_311 [ 5570.511] (II) xfree86: Adding drm device (/dev/dri/card0) [ 5570.511] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0 [ 5570.513] (--) PCI:*(0@0:2:0) 8086:1616:8086:2010 rev 9, Mem @ 0xc000/16777216, 0xa000/536870912, I/O @ 0x4000/64, BIOS @ 0x/131072 [ 5570.513] (II) LoadModule: "glx" [ 5570.513] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 5570.514] (II) Module glx: vendor="X.Org Foundation" [ 5570.514]compiled for 1.20.11, module version = 1.0.0 [ 5570.514]ABI class: X.Org Server Extension, version 10.0 [ 5570.514] (==) Matched modesetting as autoconfigured driver 0 [ 5570.514] (==) Matched fbdev as autoconfigured driver 1 [ 5570.514] (==) Matched vesa as autoconfigured driver 2 [ 5570.514] (==) Assigned the driver to the xf86ConfigLayout [ 5570.514] (II) LoadModule: "modesetting" [ 5570.514] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 5570.514] (II) Module modesetting: vendor="X.Org Foundation" [ 5570.514]compiled for 1.20.11, module version = 1.20.11 [ 5570.514]Module class: X.Org Video Driver [ 5570.514]ABI class: X.Org Video Driver, version 24.1 [ 5570.514] (II) LoadModule: "fbdev" [ 5570.514] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 5570.514] (II) Module fbdev: vendor="X.Org Foundation" [ 5570.514]compiled for 1.20.0, module version = 0.5.0 [ 5570.514]Module class: X.Org Video Driver [ 5570.514]ABI class: X.Org Video Driver, version 24.0 [ 5570.514] (II) LoadModule: "vesa" [ 5570.514] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 5570.515] (II) Module vesa: vendor="X.Org Foundation" [ 5570.515]compiled for 1.20.9, module version = 2.5.0 [ 5570.515]Module class: X.Org Video Driver [ 5570.515]ABI class: X.Org Video Driver, version 24.1 [ 5570.515] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 5570.515] (II) FBDEV: driver for framebuffer: fbdev [ 5570.515] (II) VESA: driver for VESA chipsets: vesa [ 5570.515] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) [ 5570.515] (II) modeset(0): using drv
Re: building a custon talking debian installation image with build essential and other packages on the disc as well as the mate accessible desktop
Nick, Please use the non free images because many blind people are connecting by Wi-Fi and the drivers are only on the non free images. Also add the Unofficial multimedia sources so blind people can use the non free codecs. It takes a lot of work to make Debian normal. But Debian still is the best, I just wish they'd stop the non free prohibition and put printer and multimedia and Firefox in their ISO. Best wishes, David On Fri, Apr 24, 2020, 15:29 Nick Gawronski wrote: > Hi, I am totally blind and know about pressing s to start the installer > with speech as I do this then go back to the main menu and set debconf > priority to low so I have the most control during the installation > process. I looked into the simple-cdd package for building a debian > installation image but could not find out how to include the full mate > debian desktop with orca the screen reader setup for speech as well as > build-essential and other development packages. What would be the best > process for building such an image that starts automatically at low > priority with speech running and a highor volume level then normal for > systems where you would like speech to be not so soft during the > installation process? Nick Gawronski > >
Re: default desktop
I like your suggestion, too. It's so important to have a distro that installs a command line desktop. Debian has all the pieces to do it. Best wishes, David On Sat, Feb 9, 2019, 13:21 Mewtamer wrote: > This is just a suggestion, but perhaps, instead of having "Debian > Desktop Environment" as an alias for the default without any > explanation, perhaps it would be better to restructure the software > selection menu to something like: > > 1. Gnome Desktop Environment(Debian Default) > 2. Mate Desktop Environment(Recommended for Accessibility). > 3. LXDE(recommended for systems with limited resources) > 4. No Desktop Environment(System will be command-line only) > > Etc., adjusting numbers to accomodate whatever other desktop > environments can be installed at that point. And I suggest including > the no desktop environment option to simplify things for those who'd > rather start with a basic system and handle most software installation > manually afterward. Might just be me, but this feels much more > self-documenting, informs everyone who doesn't already know what the > default is, gives those who need accessibility or are setting things > up for accessibility a heads up that the default might not be best, > etc. > > Feel free to forward this to whoever would be in a position to > consider and/or implement it. > >