Re: Talking Images for 64-bit Laptop
Linux for blind general discussion writes: > Don't press enter. Wait for the three tones then wait for speech to > happen. I did that all be it accidentally the first time. Nothing at all but the radio showed enough activity to indicate that it had gone on and was doing other stuff, just not telling me what it was doing. That was a good suggestion, however. Martin > > > -- Jude ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
Hi, The notes played by GRUB at boot time use the internal buzzer, not the sound card, that's why you could hear these notes. To understand the issue with your hardware it would help to use alsa-info.sh like this (as root to using sudo): alsa-info.sh --no-upload --output alsa-info.txt You can always get the last version of alsa-info.sh like this: wget http://www.alsa-project.org/alsa-info.sh Feel free to send me the file alsa-info.sh directly: didier at slint dot fr Cheers, Didier Le 26/09/2023 à 15:48, Linux for blind general discussion a écrit : > I am sorry, but I have bad news. I downloaded the image, sent it > to a 32-GB usb card and tried it. The system immediately found > the EFI partition and played the 3 notes in ascending order > within 5 or 10 seconds after powering on. I pressed Enter and > waited and waited and waited, left the room for a few minutes, > came back, waited some more but that was the last sound. > > Later, it occurred to me that I might get it to talk if > there was a usb sound card since those devices are in common use > everywhere. > > I now had this lap top with a 4-port extender containing > a full-size keyboard and the 128-GB thumb drive that was the > target of the Linux installation so why not also plug in a usb sound > card. > > I did and slint found that card. This is a very good way > to set this part of the installation since the person doing the > install must respond. > > I did make several later tries and confirmed that this > lap top's native sound interface is like a lot of native sound > interfaces in that it is too proprietary for it's own good. > > One of my favorite items when doing this sort of thing is a > portable AM radio to more or less get an electroencephalogram of > whether the computer seems to still be alive. One tunes to a > blank spot near the low end of the AM band if there is no radio > station there and listens to the static that the circuitry in the > computer makes as it computes. > > If something is wrong and the computer locks up, the > crackle, pop, beep and squeak abruptly stop and there is nothing > but the hiss of the radio. > > The computer, in this case, doesn't lock up but slint > never sees a viable native sound interface to probe. I hear lots > of zips, pops squeaks and beeps of all kinds indicating that the > computer is still alive and well but not talking. Adding the usb > sound card gives slint something it can recognize as a sound > interface. It did start voicing the screen just like it should > but it should have found the native interface automatically. > > I have another Debian 11 distribution that uses the same > concept of sending an English message to every sound card asking > one to press enter if this is the correct card and it talks all > the time through the installation process. > > For now, I am using that installer since it is the same > debian version I wanted anyway which is bullseye or debian 11. > > That install image does find the HP lap top's native > sound interface. When the installation is complete, it has > produced some unpleasant surprises on other systems I have used > it on if their native sound cards were particularly complex. One > system, for instance, talked all the way through the installation > but wouldn't reliably talk after booting to the installed system. > Simply unplugging the speaker or plugging in a set of headphones > would kill the audio. It turned out to think that hdmi was > supposed to be the correct output. > > If this helps any, this lap top appears to have no > trouble sending the musical notes at the boot time. The oldest > PC's had a system for making noises which you are probably very > familiar with which used a timer-counter integrated circuit that > was fed from a roughly 1-MHZ clock. The 16-bit counter in the > chip is fed with some constant depending upon what note or pitch > one needs. There is also a gate which connects pure DC to the > speaker or nothing if we are on the low half of the cycle. Tones > are produced by stuffing this constant in to the counter and the > counter counts down to 0 and then restarts after sending a pulse > to the speaker. > > You can get an amazing number of noises out of such a > circuit from Morse Code to at least video-game quality music. > > I am guessing this lap top has some modern version of > that noise-maker timer-counter-switch in order for the music to > come through but obviously, we need to find the built-in sound > card for speech to work. > > I am certainly not complaining about slint. As one who > likes to tinker with computers, PIC microcontrollers and radios, > I know how difficult it is to make just about anything work over > the broad range of situations that public users produce so, if > there is any information I can provide to help, I am glad to do > so. > > Linux for blind general discussion
Re: Talking Images for 64-bit Laptop
I bought a crystal usb sound card from thinkpenguin.com I can plug into a laptop like that and maybe have the laptop come up talking. I like amixer set Master 100% unmute && speaker-test to sometimes fix sound card problems like these. -- 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. On Tue, 26 Sep 2023, Linux for blind general discussion wrote: > > On 26/9/23 09:48, Linux for blind general discussion wrote: > > I did make several later tries and confirmed that this > > lap top's native sound interface is like a lot of native sound > > interfaces in that it is too proprietary for it's own good. > > A few suggestions: > > 1. Try a very recent kernel, just in case compatibility has improved. > > 2. You may need to play with ALSA settings (e.g., amixer) to get the audio > device working. > > If you can start sshd, you should be able to log in from another system to > work on it. > > ___ > Blinux-list mailing list > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list > > ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
On 26/9/23 09:48, Linux for blind general discussion wrote: I did make several later tries and confirmed that this lap top's native sound interface is like a lot of native sound interfaces in that it is too proprietary for it's own good. A few suggestions: 1. Try a very recent kernel, just in case compatibility has improved. 2. You may need to play with ALSA settings (e.g., amixer) to get the audio device working. If you can start sshd, you should be able to log in from another system to work on it. ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
Don't press enter. Wait for the three tones then wait for speech to happen. -- 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. On Tue, 26 Sep 2023, Linux for blind general discussion wrote: > I am sorry, but I have bad news. I downloaded the image, sent it > to a 32-GB usb card and tried it. The system immediately found > the EFI partition and played the 3 notes in ascending order > within 5 or 10 seconds after powering on. I pressed Enter and > waited and waited and waited, left the room for a few minutes, > came back, waited some more but that was the last sound. > > Later, it occurred to me that I might get it to talk if > there was a usb sound card since those devices are in common use > everywhere. > > I now had this lap top with a 4-port extender containing > a full-size keyboard and the 128-GB thumb drive that was the > target of the Linux installation so why not also plug in a usb sound > card. > > I did and slint found that card. This is a very good way > to set this part of the installation since the person doing the > install must respond. > > I did make several later tries and confirmed that this > lap top's native sound interface is like a lot of native sound > interfaces in that it is too proprietary for it's own good. > > One of my favorite items when doing this sort of thing is a > portable AM radio to more or less get an electroencephalogram of > whether the computer seems to still be alive. One tunes to a > blank spot near the low end of the AM band if there is no radio > station there and listens to the static that the circuitry in the > computer makes as it computes. > > If something is wrong and the computer locks up, the > crackle, pop, beep and squeak abruptly stop and there is nothing > but the hiss of the radio. > > The computer, in this case, doesn't lock up but slint > never sees a viable native sound interface to probe. I hear lots > of zips, pops squeaks and beeps of all kinds indicating that the > computer is still alive and well but not talking. Adding the usb > sound card gives slint something it can recognize as a sound > interface. It did start voicing the screen just like it should > but it should have found the native interface automatically. > > I have another Debian 11 distribution that uses the same > concept of sending an English message to every sound card asking > one to press enter if this is the correct card and it talks all > the time through the installation process. > > For now, I am using that installer since it is the same > debian version I wanted anyway which is bullseye or debian 11. > > That install image does find the HP lap top's native > sound interface. When the installation is complete, it has > produced some unpleasant surprises on other systems I have used > it on if their native sound cards were particularly complex. One > system, for instance, talked all the way through the installation > but wouldn't reliably talk after booting to the installed system. > Simply unplugging the speaker or plugging in a set of headphones > would kill the audio. It turned out to think that hdmi was > supposed to be the correct output. > > If this helps any, this lap top appears to have no > trouble sending the musical notes at the boot time. The oldest > PC's had a system for making noises which you are probably very > familiar with which used a timer-counter integrated circuit that > was fed from a roughly 1-MHZ clock. The 16-bit counter in the > chip is fed with some constant depending upon what note or pitch > one needs. There is also a gate which connects pure DC to the > speaker or nothing if we are on the low half of the cycle. Tones > are produced by stuffing this constant in to the counter and the > counter counts down to 0 and then restarts after sending a pulse > to the speaker. > > You can get an amazing number of noises out of such a > circuit from Morse Code to at least video-game quality music. > > I am guessing this lap top has some modern version of > that noise-maker timer-counter-switch in order for the music to > come through but obviously, we need to find the built-in sound > card for speech to work. > > I am certainly not complaining about slint. As one who > likes to tinker with computers, PIC microcontrollers and radios, > I know how difficult it is to make just about anything work over > the broad range of situations that public users produce so, if > there is any information I can provide to help, I am glad to do > so. > > Linux for blind general discussion writes: > > Hi Martin, > > > > sorry for the mistake in the Handbook. Of course I should have written: > > > > wget https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso > > wget > > https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso.sha256 > > > > then: > >
Re: Talking Images for 64-bit Laptop
I am sorry, but I have bad news. I downloaded the image, sent it to a 32-GB usb card and tried it. The system immediately found the EFI partition and played the 3 notes in ascending order within 5 or 10 seconds after powering on. I pressed Enter and waited and waited and waited, left the room for a few minutes, came back, waited some more but that was the last sound. Later, it occurred to me that I might get it to talk if there was a usb sound card since those devices are in common use everywhere. I now had this lap top with a 4-port extender containing a full-size keyboard and the 128-GB thumb drive that was the target of the Linux installation so why not also plug in a usb sound card. I did and slint found that card. This is a very good way to set this part of the installation since the person doing the install must respond. I did make several later tries and confirmed that this lap top's native sound interface is like a lot of native sound interfaces in that it is too proprietary for it's own good. One of my favorite items when doing this sort of thing is a portable AM radio to more or less get an electroencephalogram of whether the computer seems to still be alive. One tunes to a blank spot near the low end of the AM band if there is no radio station there and listens to the static that the circuitry in the computer makes as it computes. If something is wrong and the computer locks up, the crackle, pop, beep and squeak abruptly stop and there is nothing but the hiss of the radio. The computer, in this case, doesn't lock up but slint never sees a viable native sound interface to probe. I hear lots of zips, pops squeaks and beeps of all kinds indicating that the computer is still alive and well but not talking. Adding the usb sound card gives slint something it can recognize as a sound interface. It did start voicing the screen just like it should but it should have found the native interface automatically. I have another Debian 11 distribution that uses the same concept of sending an English message to every sound card asking one to press enter if this is the correct card and it talks all the time through the installation process. For now, I am using that installer since it is the same debian version I wanted anyway which is bullseye or debian 11. That install image does find the HP lap top's native sound interface. When the installation is complete, it has produced some unpleasant surprises on other systems I have used it on if their native sound cards were particularly complex. One system, for instance, talked all the way through the installation but wouldn't reliably talk after booting to the installed system. Simply unplugging the speaker or plugging in a set of headphones would kill the audio. It turned out to think that hdmi was supposed to be the correct output. If this helps any, this lap top appears to have no trouble sending the musical notes at the boot time. The oldest PC's had a system for making noises which you are probably very familiar with which used a timer-counter integrated circuit that was fed from a roughly 1-MHZ clock. The 16-bit counter in the chip is fed with some constant depending upon what note or pitch one needs. There is also a gate which connects pure DC to the speaker or nothing if we are on the low half of the cycle. Tones are produced by stuffing this constant in to the counter and the counter counts down to 0 and then restarts after sending a pulse to the speaker. You can get an amazing number of noises out of such a circuit from Morse Code to at least video-game quality music. I am guessing this lap top has some modern version of that noise-maker timer-counter-switch in order for the music to come through but obviously, we need to find the built-in sound card for speech to work. I am certainly not complaining about slint. As one who likes to tinker with computers, PIC microcontrollers and radios, I know how difficult it is to make just about anything work over the broad range of situations that public users produce so, if there is any information I can provide to help, I am glad to do so. Linux for blind general discussion writes: > Hi Martin, > > sorry for the mistake in the Handbook. Of course I should have written: > > wget https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso > wget > https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso.sha256 > > then: > sha256sum -c slint64-15.0-5.iso.sha256 > > I will fix that and/or make a link like slint64-15.0-latest.iso > > Cheers, > Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
sourceforge-net only stores an old 32-bit version. Didier Le 25/09/2023 à 16:29, Linux for blind general discussion a écrit : > That's how that's done on sourceforge.net. The webmaster would have to do > that, and now sourceforge.net is out of date on latest version for some > reason. > > > -- 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. > > On Mon, 25 Sep 2023, Linux for blind general discussion wrote: > >> That download is happening now. It's the same url except that >> the version number now is 15.5 which is fine and explains what is >> happening. What I copied from the handbook is 15.0. I wish all >> problems were this easy to figure out. A suggestion might be to >> make the url refer to something like latest_version and that designation >> would always describe whatever version was most current. >> >> Martin >> Linux for blind general discussion writes: >>> Have you tried: >>> https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
Hi Martin, sorry for the mistake in the HandBook. Of course I should have written: wget https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso wget https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso.sha256 then: sha256sum -c slint64-15.0-5.iso.sha256 I will fix that and/or make a link like slint64-15.0-latest.iso Cheers, Didier Le 25/09/2023 à 14:55, Linux for blind general discussion a écrit : > I am not sure what is wrong but everything looks normal in the > image-getting phase. I lifted this right out of the handbook: > > wget https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.iso > wget https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.iso.sha256 > > The results are as follows: > > --2023-09-25 07:18:15-- > https://slackware.uk/slint/x86_64/slint-15.0/iso/slint6 > 4-15.iso > Resolving slackware.uk (slackware.uk)... 216.119.155.61, > 2a02:2498:e004:2a::a861 > Connecting to slackware.uk (slackware.uk)|216.119.155.61|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2023-09-25 07:18:16 ERROR 404: Not Found. > > --2023-09-25 07:18:16-- > https://slackware.uk/slint/x86_64/slint-15.0/iso/slint6 > 4-15.iso.sha256 > Resolving slackware.uk (slackware.uk)... 216.119.155.61, > 2a02:2498:e004:2a::a861 > Connecting to slackware.uk (slackware.uk)|216.119.155.61|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2023-09-25 07:18:17 ERROR 404: Not Found. > > In the past, I have occasionally had urls fail and it was > my fault because I had written some perl code to make reading > email messages and the like read more smoothly by removing some > 8-bit charactors. This did, in fact clean things up but it's > like fire, a wonderful servant but a terrible master. It made > things look fine but sometimes altered punctuation marks and > special symbols so that they were either missing or mangled and > so I thought I had gotten rid of that helper code I had written > for the output handler so I don't know if that bug has bitten > again or what. > urls are where this happens most often. > > I put a textual screen shot of how the wget went so > whatever happened, it is sneaky. > > Anyway, thank you for your help. I am sure that this > should get working soon as I believe that system is probably okay > except for the corrupted Windows drive and I may have to find a > usb instance of Windows 11 for that issue but that's for another > list about the care and feeding of Windows 11. For here and now, > the only problem is that the wget is coming up with 404's all > round. > > Martin > > Linux for blind general discussion writes: >> Hi Martin, >> >> to clarify, I have provided an image of an installed system as you >> requested: >> https://slackware.uk/slint/x86_64/slint-14.2.1/minislint/README.minislint >> but it was for a previous Slint version. >> >> You'd be better off installing the most recent version in an USB stick >> (or a SD >> card in an USB enclosure) as indicated in: >> https://slint.fr/en/HandBook.html#_install_slint >> >> Cheers, >> Didier > > ___ > Blinux-list mailing list > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list > ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
That's how that's done on sourceforge.net. The webmaster would have to do that, and now sourceforge.net is out of date on latest version for some reason. -- 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. On Mon, 25 Sep 2023, Linux for blind general discussion wrote: > That download is happening now. It's the same url except that > the version number now is 15.5 which is fine and explains what is > happening. What I copied from the handbook is 15.0. I wish all > problems were this easy to figure out. A suggestion might be to > make the url refer to something like latest_version and that designation > would always describe whatever version was most current. > > Martin > Linux for blind general discussion writes: > > Have you tried: > > https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso > > ___ > Blinux-list mailing list > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list > > ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
That download is happening now. It's the same url except that the version number now is 15.5 which is fine and explains what is happening. What I copied from the handbook is 15.0. I wish all problems were this easy to figure out. A suggestion might be to make the url refer to something like latest_version and that designation would always describe whatever version was most current. Martin Linux for blind general discussion writes: > Have you tried: > https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
Have you tried: https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.0-5.iso -- 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. On Mon, 25 Sep 2023, Linux for blind general discussion wrote: > I appreciate all this information because I got in a bit of a > hurry and ended up at the wrong site and the web monster showed > me a 3-GB image for slint which I downloaded. The download went > fine and the image flowed like good wine on to a 4-GB usb stick. > > slint-14.2.iso?viasf=1 > > Whatever this is, it's not a bootable image but probably all the > sources which is a nice thing to have but won't do the job at > hand right now. I should mount it and see what's there but it > produced a thumb drive with 1 single partition of type hidden > according to fdisk -l /dev/sdx. > > This whole project is going fairly nicely in that my wife helped > me turn off secureboot and change the boot order to usb first > then internal drive and, if the internal drive wasn't sick, I'd > be up and running. > > Another debian-11 distro on a different thumb drive jups > right in to the installation routine if you type s at the beeps > and the system seems to just love it. > > Since the keyboard is a laptop keyboard, getting a > secondary tty is a bit tricky. I had good beginners' luck after > getting to the partitioner but I haven't been able to duplicate > that more than once. I held alt+F1, I think and got the second > console and was able to look around in /dev. The mentally-ill > internal drive, however, was nowhere to be found and the only > /dev/sdx listing was my boot drive for Linux. > > I killed everything and restarted but couldn't get the > second console or any of the others to show but the partitioner, > this time could see every drive in the system and their > descriptions were spot on so I could have installed then had I > wanted to do so. > > I could see that the internal drive is a Kingston ssD > with 2 terabytes and all the partitions including Microsoft's > partition were listed. I am sorely tempted to plug a real > keyboard in to a usb converter which has a number pad like the > good Lord meant keyboards to have, I mean a real number pad, not > these fake ones that only give you numbers but have no numlock to > cycle back and forth. > > When I was going to the school for the blind, they > started us in typing on QWERTY keyboards back in 1962 when I was > in the Fifth grade so it's nice when stuff stays in the usual > place. > > That time when I could see all the drives on the system > and could have installed Linux, I kept getting a really nice > keyboard help instead of the secondary consoles so I don't know > what changed but I couldn't call them up any more. > > The keyboard help said F1 when I pressed the key to the > right of Escape so alt + that should have switched to tty1 from > tty0. > > Anyway, I'll try your suggestion and see if I get slint > when I put that image in. > > When I get Windows 11 working again, I will have a laptop > with windows 11 or a Linux laptop if I plug in the slint image, > hopefully the correct one this time. > > I do see that the CMOS clock is right in that if I do the > date command from /dev/tty1, I see a utc date that is appropriate > for my time zone. Older Windows systems set the CMOS clock based > on local time so this one is new enough to do it the right way. > > Linux for blind general discussion writes: > > Hi Martin, > > > > to clarify, I have provided an image of an installed system as you > > requested: > > https://slackware.uk/slint/x86_64/slint-14.2.1/minislint/README.minislint > > but it was for a previous Slint version. > > > > You'd be better off installing the most recent version in an USB stick > > (or a SD > > card in an USB enclosure) as indicated in: > > https://slint.fr/en/HandBook.html#_install_slint > > > > Cheers, > > Didier > > ___ > Blinux-list mailing list > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list > > ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
Note that if you're in a graphical environment, switching to a virtual terminal is achieved with ctrl-altF1, ctrl-alt-F2, etc., and at least one of those terminals will be taken up by your graphical session. These days, tty1 is usually devoted to the graphical session; possibly tty2 as well. On 25/9/23 07:38, Linux for blind general discussion wrote: I appreciate all this information because I got in a bit of a hurry and ended up at the wrong site and the web monster showed me a 3-GB image for slint which I downloaded. The download went fine and the image flowed like good wine on to a 4-GB usb stick. slint-14.2.iso?viasf=1 Whatever this is, it's not a bootable image but probably all the sources which is a nice thing to have but won't do the job at hand right now. I should mount it and see what's there but it produced a thumb drive with 1 single partition of type hidden according to fdisk -l /dev/sdx. This whole project is going fairly nicely in that my wife helped me turn off secureboot and change the boot order to usb first then internal drive and, if the internal drive wasn't sick, I'd be up and running. Another debian-11 distro on a different thumb drive jups right in to the installation routine if you type s at the beeps and the system seems to just love it. Since the keyboard is a laptop keyboard, getting a secondary tty is a bit tricky. I had good beginners' luck after getting to the partitioner but I haven't been able to duplicate that more than once. I held alt+F1, I think and got the second console and was able to look around in /dev. The mentally-ill internal drive, however, was nowhere to be found and the only /dev/sdx listing was my boot drive for Linux. I killed everything and restarted but couldn't get the second console or any of the others to show but the partitioner, this time could see every drive in the system and their descriptions were spot on so I could have installed then had I wanted to do so. I could see that the internal drive is a Kingston ssD with 2 terabytes and all the partitions including Microsoft's partition were listed. I am sorely tempted to plug a real keyboard in to a usb converter which has a number pad like the good Lord meant keyboards to have, I mean a real number pad, not these fake ones that only give you numbers but have no numlock to cycle back and forth. When I was going to the school for the blind, they started us in typing on QWERTY keyboards back in 1962 when I was in the Fifth grade so it's nice when stuff stays in the usual place. That time when I could see all the drives on the system and could have installed Linux, I kept getting a really nice keyboard help instead of the secondary consoles so I don't know what changed but I couldn't call them up any more. The keyboard help said F1 when I pressed the key to the right of Escape so alt + that should have switched to tty1 from tty0. Anyway, I'll try your suggestion and see if I get slint when I put that image in. When I get Windows 11 working again, I will have a laptop with windows 11 or a Linux laptop if I plug in the slint image, hopefully the correct one this time. I do see that the CMOS clock is right in that if I do the date command from /dev/tty1, I see a utc date that is appropriate for my time zone. Older Windows systems set the CMOS clock based on local time so this one is new enough to do it the right way. Linux for blind general discussion writes: Hi Martin, to clarify, I have provided an image of an installed system as you requested: https://slackware.uk/slint/x86_64/slint-14.2.1/minislint/README.minislint but it was for a previous Slint version. You'd be better off installing the most recent version in an USB stick (or a SD card in an USB enclosure) as indicated in: https://slint.fr/en/HandBook.html#_install_slint Cheers, Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
I am not sure what is wrong but everything looks normal in the image-getting phase. I lifted this right out of the handbook: wget https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.iso wget https://slackware.uk/slint/x86_64/slint-15.0/iso/slint64-15.iso.sha256 The results are as follows: --2023-09-25 07:18:15-- https://slackware.uk/slint/x86_64/slint-15.0/iso/slint6 4-15.iso Resolving slackware.uk (slackware.uk)... 216.119.155.61, 2a02:2498:e004:2a::a861 Connecting to slackware.uk (slackware.uk)|216.119.155.61|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2023-09-25 07:18:16 ERROR 404: Not Found. --2023-09-25 07:18:16-- https://slackware.uk/slint/x86_64/slint-15.0/iso/slint6 4-15.iso.sha256 Resolving slackware.uk (slackware.uk)... 216.119.155.61, 2a02:2498:e004:2a::a861 Connecting to slackware.uk (slackware.uk)|216.119.155.61|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2023-09-25 07:18:17 ERROR 404: Not Found. In the past, I have occasionally had urls fail and it was my fault because I had written some perl code to make reading email messages and the like read more smoothly by removing some 8-bit charactors. This did, in fact clean things up but it's like fire, a wonderful servant but a terrible master. It made things look fine but sometimes altered punctuation marks and special symbols so that they were either missing or mangled and so I thought I had gotten rid of that helper code I had written for the output handler so I don't know if that bug has bitten again or what. urls are where this happens most often. I put a textual screen shot of how the wget went so whatever happened, it is sneaky. Anyway, thank you for your help. I am sure that this should get working soon as I believe that system is probably okay except for the corrupted Windows drive and I may have to find a usb instance of Windows 11 for that issue but that's for another list about the care and feeding of Windows 11. For here and now, the only problem is that the wget is coming up with 404's all round. Martin Linux for blind general discussion writes: > Hi Martin, > > to clarify, I have provided an image of an installed system as you > requested: > https://slackware.uk/slint/x86_64/slint-14.2.1/minislint/README.minislint > but it was for a previous Slint version. > > You'd be better off installing the most recent version in an USB stick > (or a SD > card in an USB enclosure) as indicated in: > https://slint.fr/en/HandBook.html#_install_slint > > Cheers, > Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
I appreciate all this information because I got in a bit of a hurry and ended up at the wrong site and the web monster showed me a 3-GB image for slint which I downloaded. The download went fine and the image flowed like good wine on to a 4-GB usb stick. slint-14.2.iso?viasf=1 Whatever this is, it's not a bootable image but probably all the sources which is a nice thing to have but won't do the job at hand right now. I should mount it and see what's there but it produced a thumb drive with 1 single partition of type hidden according to fdisk -l /dev/sdx. This whole project is going fairly nicely in that my wife helped me turn off secureboot and change the boot order to usb first then internal drive and, if the internal drive wasn't sick, I'd be up and running. Another debian-11 distro on a different thumb drive jups right in to the installation routine if you type s at the beeps and the system seems to just love it. Since the keyboard is a laptop keyboard, getting a secondary tty is a bit tricky. I had good beginners' luck after getting to the partitioner but I haven't been able to duplicate that more than once. I held alt+F1, I think and got the second console and was able to look around in /dev. The mentally-ill internal drive, however, was nowhere to be found and the only /dev/sdx listing was my boot drive for Linux. I killed everything and restarted but couldn't get the second console or any of the others to show but the partitioner, this time could see every drive in the system and their descriptions were spot on so I could have installed then had I wanted to do so. I could see that the internal drive is a Kingston ssD with 2 terabytes and all the partitions including Microsoft's partition were listed. I am sorely tempted to plug a real keyboard in to a usb converter which has a number pad like the good Lord meant keyboards to have, I mean a real number pad, not these fake ones that only give you numbers but have no numlock to cycle back and forth. When I was going to the school for the blind, they started us in typing on QWERTY keyboards back in 1962 when I was in the Fifth grade so it's nice when stuff stays in the usual place. That time when I could see all the drives on the system and could have installed Linux, I kept getting a really nice keyboard help instead of the secondary consoles so I don't know what changed but I couldn't call them up any more. The keyboard help said F1 when I pressed the key to the right of Escape so alt + that should have switched to tty1 from tty0. Anyway, I'll try your suggestion and see if I get slint when I put that image in. When I get Windows 11 working again, I will have a laptop with windows 11 or a Linux laptop if I plug in the slint image, hopefully the correct one this time. I do see that the CMOS clock is right in that if I do the date command from /dev/tty1, I see a utc date that is appropriate for my time zone. Older Windows systems set the CMOS clock based on local time so this one is new enough to do it the right way. Linux for blind general discussion writes: > Hi Martin, > > to clarify, I have provided an image of an installed system as you > requested: > https://slackware.uk/slint/x86_64/slint-14.2.1/minislint/README.minislint > but it was for a previous Slint version. > > You'd be better off installing the most recent version in an USB stick > (or a SD > card in an USB enclosure) as indicated in: > https://slint.fr/en/HandBook.html#_install_slint > > Cheers, > Didier ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
I used the current release of GRML today for system recovery purposes (Grub needed to be reinstalled). After booting it from a USB drive, I ran both BRLTTY and Speakup from the shell prompt. I probably could have enabled them during the boot procedure, but I was in a hurry. All worked as expected, including detection of the braille display. On 22/9/23 18:20, Linux for blind general discussion wrote: Hi Martin, to clarify, I have provided an image of an installed system as you requested: https://slackware.uk/slint/x86_64/slint-14.2.1/minislint/README.minislint but it was for a previous Slint version. You'd be better off installing the most recent version in an USB stick (or a SD card in an USB enclosure) as indicated in: https://slint.fr/en/HandBook.html#_install_slint Cheers, Didier Le 22/09/2023 à 22:56, Linux for blind general discussion a écrit : Thanks. I've wanted to give slint a try and this would be a perfect time to try it. Martin Linux for blind general discussion writes: I think slint can fill the bill for you. You can put slint on a flash drive if you need to do that and have it install for you. ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
Hi Martin, to clarify, I have provided an image of an installed system as you requested: https://slackware.uk/slint/x86_64/slint-14.2.1/minislint/README.minislint but it was for a previous Slint version. You'd be better off installing the most recent version in an USB stick (or a SD card in an USB enclosure) as indicated in: https://slint.fr/en/HandBook.html#_install_slint Cheers, Didier Le 22/09/2023 à 22:56, Linux for blind general discussion a écrit : > Thanks. I've wanted to give slint a try and this would be a > perfect time to try it. > > Martin > Linux for blind general discussion writes: >> I think slint can fill the bill for you. You can put slint on a flash >> drive if you need to do that and have it install for you. ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
Thanks. I've wanted to give slint a try and this would be a perfect time to try it. Martin Linux for blind general discussion writes: > I think slint can fill the bill for you. You can put slint on a flash > drive if you need to do that and have it install for you. ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
Re: Talking Images for 64-bit Laptop
I think slint can fill the bill for you. You can put slint on a flash drive if you need to do that and have it install for you. -- 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. On Fri, 22 Sep 2023, Linux for blind general discussion wrote: > I have a HP Pavilion lap top system which my wife was using to > run Windows 11 and it is presently failing to boot but > fortunately for this list, that is not what I am really here to > post about. > > What I think I need is a bootable version of linux which > is similar in behavior to the many Raspberry Pi images available > that can fit on a SSD card. Usually, they are compressed and > will fill the SSD card one has written the image to so they are > not your standard iso live CD's but one uses it as a > self-contained Linux system. What I want to do is keep Windows > 11 on the SSD but get the laptop capable of booting off of a > bootable usb drive if it is present. If not, it goes ahead and > boots Windows. > > This will probably require changing the BIOS settings to > turn off secureboot and have usb be the first boot candidate > tried. > > Right now, for this discussion, I am asking if there is > such an image for a 64-bit system. If it talks, that's the icing > on the cake but if not, I still might be able to use it via ssh > from a system that does talk. > > I want to use this instance of Linux to try to fix the > problem the dead box is having but also use Linux to backup the > box since Windows does not have a native backup program. This > also gives me yet another portable Linux box as if I needed one. > > As far as this list is concerned, is there something like > this out there and does it talk? > > Another reason why I have not simply tried to use a > debian installation image is frankly because there is a slight > chance of accidentally installing it on the SSD where Windows 11 > currently lives so I want to avoid that if possible. > > The idea is to do no more harm than has already been > done. From what I read based on the error screen, the problem is > fixable but if I write to the wrong device, that pretty well > blows things up so I am playing it safe if possible. > > One person mentioned grml with clonzilla which sounds > like a good thing but at this stage, I am open to any suggestion. > Don't forget that it's a laptop so one can't just pop drives and > memory cards in and out like one should be able to do in a > desktop system so I am trying to avoid doing that unless the SSD > proves to be bad. > > Thanks. > > Martin McCormick > > ___ > Blinux-list mailing list > Blinux-list@redhat.com > https://listman.redhat.com/mailman/listinfo/blinux-list > > ___ Blinux-list mailing list Blinux-list@redhat.com https://listman.redhat.com/mailman/listinfo/blinux-list
