- Grml - lists.mur.at

Accessibility works fine for me
by John G. Heim 07 Nov '11

07 Nov '11

My problems with my hardware synth are absolutely not grml problems. I've found the same problem occurs with the speakup module in the stock debian kernel in the testing release. There is something wrong with the kernel module for the doubletalk synt starting around kernel 2.6.38. It works in kkernel version 2.6.32 and it works in newer kernels on 32 bit machines. Its only newer 64 bit kernels where the problem occurs. I have not been able to get software speech to work but that's probably because I don't know how to unmute a sound card in character mode. There ought to be a linux package to set a rational configuration for sound cards. There used to be a program called alsaconf but it was dropped from the alsa packages a few years ago. I can't imagine why. It seemed to work like a charm. Anyway, personally, I am satisfied with hardware synth support and braille support. If you say software speech works, so much the better. Although, I think it would be both useful and cool for grml to pplay a little tune through the beep command when its done booting. Like ubuntu has its distinctive drum beat when the GUI is done loading. It would become the grml theme mmusic. I would make it my ring tone. I think it would be ccool to be on the bus and have my phone ring and have some other nerd recognize it as the grml boot tune. ----- Original Message ----- From: "Michael Whapples" <mwhapples(a)aim.com> To: <grml(a)mur.at> Sent: Sunday, November 06, 2011 11:20 AM Subject: [Grml] Accessibility works fine for me > Hello, > Just a quick note that for what I could test of the medium64 daily build > accessibility seemed to work. > > Here is what I tested: > * Let the ISO boot normally on a MacBookPro. > * I got nothing to indicate that the CD had finished booting (don't know > if that is what should happen currently). I just listened for when the CD > activity seemed to stop. > * I then tried to start brltty with no options and it started fine > detecting my Braille display. > * Then I checked sound levels. Everything except master seemed to be > muted. As there was one channel labelled front speakers I decided to raise > this volume first. Not sure if that is needed but if it is for sound > output then may be that needs to be changed so that I will not need to > raise that level. > * I loaded the speakup_soft module which worked fine. > * Started espeakup which also started fine. > > Things I could not test: > * I could not test hardware speech output as my apollo synthesiser > requires a serial port and the MacBookPro has no serial port. The > MacBookPro is the only 64-bit computer I have. > > The main issues which come out of this is, some way of knowing the CD is > booted (may be a sequence of beeps) and possibly the sound not being > properly unmuted (which possibly is a hardware specific issue and may be > harder to fix for "everyone"). > > Michael Whapples > _______________________________________________ > Grml mailing list - Grml(a)ml.grml.org > http://ml.grml.org/mailman/listinfo/grml > join #grml on irc.freenode.org > grml-devel-blog: http://blog.grml.org/ > >

1 0

Re: [Grml] Accessibility works fine for me
by Michael Whapples 07 Nov '11

07 Nov '11

Well if you want nerdy, how about GRML done out in morse code? As for the unmuting of the sound card, I used alsamixer with brltty, possibly not the most efficient combination but it worked for me. Michael Whapples On 7 Nov 2011, at 14:59, John G. Heim wrote: > My problems with my hardware synth are absolutely not grml problems. I've found the same problem occurs with the speakup module in the stock debian kernel in the testing release. There is something wrong with the kernel module for the doubletalk synt starting around kernel 2.6.38. It works in kkernel version 2.6.32 and it works in newer kernels on 32 bit machines. Its only newer 64 bit kernels where the problem occurs. > > I have not been able to get software speech to work but that's probably because I don't know how to unmute a sound card in character mode. There ought to be a linux package to set a rational configuration for sound cards. There used to be a program called alsaconf but it was dropped from the alsa packages a few years ago. I can't imagine why. It seemed to work like a charm. > > Anyway, personally, I am satisfied with hardware synth support and braille support. If you say software speech works, so much the better. > > Although, I think it would be both useful and cool for grml to pplay a little tune through the beep command when its done booting. Like ubuntu has its distinctive drum beat when the GUI is done loading. It would become the grml theme mmusic. I would make it my ring tone. I think it would be ccool to be on the bus and have my phone ring and have some other nerd recognize it as the grml boot tune. > > ----- Original Message ----- From: "Michael Whapples" <mwhapples(a)aim.com> > To: <grml(a)mur.at> > Sent: Sunday, November 06, 2011 11:20 AM > Subject: [Grml] Accessibility works fine for me > > >> Hello, >> Just a quick note that for what I could test of the medium64 daily build accessibility seemed to work. >> >> Here is what I tested: >> * Let the ISO boot normally on a MacBookPro. >> * I got nothing to indicate that the CD had finished booting (don't know if that is what should happen currently). I just listened for when the CD activity seemed to stop. >> * I then tried to start brltty with no options and it started fine detecting my Braille display. >> * Then I checked sound levels. Everything except master seemed to be muted. As there was one channel labelled front speakers I decided to raise this volume first. Not sure if that is needed but if it is for sound output then may be that needs to be changed so that I will not need to raise that level. >> * I loaded the speakup_soft module which worked fine. >> * Started espeakup which also started fine. >> >> Things I could not test: >> * I could not test hardware speech output as my apollo synthesiser requires a serial port and the MacBookPro has no serial port. The MacBookPro is the only 64-bit computer I have. >> >> The main issues which come out of this is, some way of knowing the CD is booted (may be a sequence of beeps) and possibly the sound not being properly unmuted (which possibly is a hardware specific issue and may be harder to fix for "everyone"). >> >> Michael Whapples >> _______________________________________________ >> Grml mailing list - Grml(a)ml.grml.org >> http://ml.grml.org/mailman/listinfo/grml >> join #grml on irc.freenode.org >> grml-devel-blog: http://blog.grml.org/ >> >

1 0

Accessibility works fine for me
by Michael Whapples 06 Nov '11

06 Nov '11

Hello, Just a quick note that for what I could test of the medium64 daily build accessibility seemed to work. Here is what I tested: * Let the ISO boot normally on a MacBookPro. * I got nothing to indicate that the CD had finished booting (don't know if that is what should happen currently). I just listened for when the CD activity seemed to stop. * I then tried to start brltty with no options and it started fine detecting my Braille display. * Then I checked sound levels. Everything except master seemed to be muted. As there was one channel labelled front speakers I decided to raise this volume first. Not sure if that is needed but if it is for sound output then may be that needs to be changed so that I will not need to raise that level. * I loaded the speakup_soft module which worked fine. * Started espeakup which also started fine. Things I could not test: * I could not test hardware speech output as my apollo synthesiser requires a serial port and the MacBookPro has no serial port. The MacBookPro is the only 64-bit computer I have. The main issues which come out of this is, some way of knowing the CD is booted (may be a sequence of beeps) and possibly the sound not being properly unmuted (which possibly is a hardware specific issue and may be harder to fix for "everyone"). Michael Whapples

1 0

Accessibility: espeakup and ALSA
by Michael Whapples 06 Nov '11

06 Nov '11

Hello, I seem to have a memory of a message saying that ALSA sound support in the medium ISO is being considered for removal, although I cannot find the message. Now as accessibility is being put in the medium ISO, the problem is that espeakup and espeak rely on working sound support to be of any use (as mentioned in the festival TTS documentation sound output is desirable, although having no sound card does mean less defects will be heard). I just thought I would bring this point to the attention of the developers, as there is no point in including espeakup and espeak unless sound support is there. Michael Whapples

1 0

Accessibility versus Packages
by Konrad Schrempf 05 Nov '11

05 Nov '11

Hi, even if I don't need the discussed accessibility-packages, they seem to me much more important than other packages. As an example I remind on the discussion about TeX/LaTeX some time ago. Unless almost all of the packages are provided it is necessary to install some more. So it is the same to install all of them later. For me the main point is to have that kind of running system to be able to extend it later. I like GRML very much for all the nice programs in textmode. Sometimes I use X11, with a lot of xterms running ... Is it really necessary to provide a graphical VIM? The use of the *-register should also be possible (as a compile-option) in standard VIM. For cease-fire reasons you would have to remove the graphical Emacs too ;-) What's about packages like cowsay? I find it funny but I could live without. GRML could still recommend some of these programs by providing a list with interesting examples. Regards, Konrad

2 1

Re: [Grml] Please don't take out accessibility away, I'll manage it
by John G. Heim 04 Nov '11

04 Nov '11

Doh! 64 bit image, 32 bit machine. ----- Original Message ----- From: "John G. Heim" <jheim(a)math.wisc.edu> To: "John G. Heim" <jheim(a)math.wisc.edu> Sent: Friday, November 04, 2011 12:02 PM Subject: Re: [Grml] Please don't take out accessibility away, I'll manage it > > ----- Original Message ----- > From: "John G. Heim" <jheim(a)math.wisc.edu> > To: <grml(a)ml.grml.org> > Sent: Friday, November 04, 2011 11:56 AM > Subject: Re: [Grml] Please don't take out accessibility away, I'll manage > it > > >> That daily build image doesn't boot on a OptiPlex GX280. I get the >> syslinux screen but after that, it hangs. Automatic boot in 4 seconds, >> 3, 2, 1, ... Nothing. >> >> ----- Original Message ----- >> From: "Christian Hofstaedtler" <ch(a)grml.org> >> To: <grml(a)ml.grml.org> >> Sent: Friday, November 04, 2011 11:24 AM >> Subject: Re: [Grml] Please don't take out accessibility away, I'll manage >> it >> >> >>>* Michael Gissing <m.gissing(a)tugraz.at> [111104 16:54]: >>>> On 2011-11-04 08:02, Christian Hofstaedtler wrote: >>>> >http://jenkins.grml.org/job/grml-medium-amd64/lastSuccessfulBuild/artifact/… >>>> >>>> HTTP 404? Does this link work for anybody? >>> >>> Apparently gone already. >>> >>> The daily grml64 medium ISOs should now also have espeakup: >>> http://daily.grml.org/grml64-medium_sid_latest.iso >>> >>> -ch >>> >>> _______________________________________________ >>> Grml mailing list - Grml(a)ml.grml.org >>> http://ml.grml.org/mailman/listinfo/grml >>> join #grml on irc.freenode.org >>> grml-devel-blog: >>> >>> >> >> _______________________________________________ >> Grml mailing list - Grml(a)ml.grml.org >> http://ml.grml.org/mailman/listinfo/grml >> join #grml on irc.freenode.org >> grml-devel-blog: >> > >

1 0

Please don't take out accessibility away, I'll manage it
by Doug Smith 04 Nov '11

04 Nov '11

Hi, all the people here on the grml mailing list. Please don't take away accessibility, I'll manage it. You will have to give me step-by-exact step instructioons for how you got it to work that way and I will do it. I can learn, if you will some how show me how to do it. I have a 64 bit machine, so I probably will be best to do the 64-bit version. I just want a system that is all command line and handles current web technologies as well or better than the gnome-orca-firefox combination if possible. Is it possible to rewrite all those graphical applications so that they will work in command line? Can this process be automated? On the other hand, how hard would it be to build a NSA-like system that captures all the contents of the internet and redistributes it in a non-graphical form? Can't the blind community just build or get hold of some kind of supercomputer and then use artificial intelligence to rework all the internet sites into a non-graphical format and then set up a network provider that can be accessed by command-line only users to get the same content everyone else does? That is a research project for the future. If anyone has that kind of computing power available, please direct me to it. If no one wants to do this, theen, can you direct me to a way of getting command line accessibility on the command line in a 64-bit bersion? Please don't take accessibility out of grml. If you will show me just exactly what to do to get it to work and then build an iso, I can manage it. Sincerely: Doug Smith

4 4

How are blind grml users handling current web technologies?
by Doug Smith 03 Nov '11

03 Nov '11

, everyone on the list. I am writing this to see how blind grml users are handling current web technologies such as flash and javascript. I am wishing to change back to GRML which I haven't been able to use in years. The main reason is that the gui world is going to change and there have been problems with accessibility. This doesn't, of course happen with good old command line, of course, and I just wonder if some of the blind people using grml now can tell me about their work-aroundds for such problems as flash and javascript. Is it possible to have mplayer be the viewer for all these streaming file formats and get it to work with w3m or edbrowse or whatever: Please let me know if there is something you are doing to handle current web technologies in command line mode and i will be glad to hear from you. Sincerely: Doug Smith _______________________________________________ Grml mailing list - Grml(a)ml.grml.org http://ml.grml.org/mailman/listinfo/grml join #grml on irc.freenode.org grml-devel-blog:

7 20

iscsitarget and iscsitarget-module-... in grml 2011.05
by Urs Blaser 03 Nov '11

03 Nov '11

Hello everyone After still using 2010.12 for a long time, i switched my troubleshooting usb-stick to 2011.05 and tried to export a local drive via iscsi. Sadly this didn't worked out of the box because the kernel module was missing. I checked the packages and found that iscsitarget-module-`uname -r` wasn't installed... After installing this, there was a module version mismatch which required a upgrade of iscsitarget. The module version mismatch is supposedly due to the fact that the packages evolved since the release. But why didn't the kernel module made it into the release when it's needed by iscsitarget that's shipped - and that http://grml.org/kernel/ advertises this module. What did i miss in the whole process? And how do i best prepare for the next use of iscsitarget from the liveCD? Best regards and thanks for all the good work. Ursus

2 1

Re: [Grml] Just a test
by Alexander Wirt 02 Nov '11

02 Nov '11

Alexander Wirt schrieb am Wednesday, den 02. November 2011: > Heho, > > this is just a test. > > Thanks for your attention And another, hope this is the last. Sorry Alex

1 0