Early boot became slower
Mattia Oss: This can be seen in the 3rd video. Lisi Reisz: By you. Not by me - nor apparently by Felix. It's really simple. It's the same size monitor. The "normal" characters are high resolution 24-bit colour graphics mode with 8*16 pixel glyphs, giving 240 columns by 67 rows. The "huge" characters are VGA text mode at 80 columns by 25 rows, giving glyphs that are in effect more than 24*32 pixels. As for why graphics mode has slowed down going from simple-framebuffer to vesafb, consider this and its implications: vesafb: scrolling: redraw
nosh version 1.32
The nosh package is now up to version 1.32 . * http://jdebp.eu./Softwares/nosh/ * https://www.freebsd.org/news/status/report-2015-07-2015-09.html#The-nosh-Project * http://jdebp.info./Softwares/nosh/ This release fixes two problems with Gentoo Linux (control group version detection and a problem with mounting API filesystems) that we hashed out on the Supervision mailing list. It furthermore contains a change to the way that convert-systemd-units generates service bundles that fixes problems with control group setup when the service unit defines a "slice" for the service or when the service unit is a template. In furtherance of that there's a new create-control-group command. Other things in this release include improvements to the (unpackaged) Z Shell command-line completions, which now display option completion menus properly; some improvements to the Terminals chapter in the Guide; fixes to various service bundles that were using shell reserved words and operators such as "for" and "&&" without explicitly invoking the shell; additions to userenv for setting DBus and XDG Runtime variables; and a fix that prevents "system-control reset" from looping indefinitely when run by an unprivileged user such as "messagebus" that lacks access to the control/status API. The major improvement in this release, though, is to console-fb-realizer on TrueOS. FreeBSD gives console-fb-realizer uhid device files to use for input devices, which speak the USB HID report protocol and which console-fb-realizer has been happy with for a long time. TrueOS provides either ums/ukbd devices, which lack various features because they speak the old sysmouse and atkbd protocols, or ugen devices. There are no uhid devices available. console-fb-realizer can now use the ugen devices. Moreover, it will detach the ums/ukbd drivers from the ugen devices using the new detach-kernel-usb-driver command, so that there aren't two things both attempting to read HID reports. console-fb-realizer also now correctly sets the keyboard LEDs on both FreeBSD and TrueOS. There have been several minor adjustments to the kernel VT sharing parts of console-fb-realizer, preparatory to splitting the program up into separate parts for input and output devices, permitting things such as multiple keyboards each with its own keyboard map and numlock semantics, in a future release.
Re: Early boot became slower
Jonathan de Boyne Pollard composed on 2017-01-30 08:45 (UTC): It's really simple. It's the same size monitor. The "normal" characters are high resolution 24-bit colour graphics mode with 8*16 pixel glyphs, giving 240 columns by 67 rows. The "huge" characters are VGA text mode at 80 columns by 25 rows, giving glyphs that are in effect more than 24*32 pixels. At what point exactly within either of those videos does 80 by 25 appear? All I saw anywhere appeared to be in the vicinity of 240 by 67. Is there something simpler than 'echo $ROWS $COLUMNS' or 'tput lines';'tput cols' to show the row and column count on a vtty one is using? Fbset leaves that info out of its report. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Re: How to reply a list message using Gmail with Evolution?
On 01/30/2017 01:40 AM, River Chiang wrote: Hello List, I use Firefox to read lists, when I clicked the link debian-user@lists.debian.org and tried to reply the message, Evolution's setup window showed. I tried to setup Evolution to use Gmail. Unfortunately I didn't make it. What mail user agent you use to view/reply messages on this list? I use Icedove (essentially our version of Thunderbird), which has a "Reply List" button Or how to setup Evolution to use a Gmail account? http://bfy.tw/9mI3 tony -- http://www.baldwinlinguas.com translations, localization, multilingual web development EN, ES, FR, PT
Re: bugs in reportbug ?
On 30/01/17 12:59 AM, Andreas Ronnquist wrote:
On Mon, 30 Jan 2017 00:37:42 -0500,
Frank M wrote:
Tried to file a bug today using reportbug but it crashed:
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2233, in
main()
File "/usr/bin/reportbug", line 1084, in main
if newui.initialize():
File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line
1580, in initialize gi.require_version('Vte', '2.91')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 118, in
require_version raise ValueError('Namespace %s not available' %
namespace)
ValueError: Namespace Vte not available
Does this look familiar to anyone ?
I am running 64 bit stretch and reportbug is the latest version.
See #851968 [1] - you will need to install the packages gir1.2-vte-2.91
and python3-gi-cairo for the GTK+ interface to work.
1 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851968
-- Andreas Rönnquist
mailingli...@gusnan.se
gus...@openmailbox.org
That solved it. I had python3-gi-cairo but was missing the second
package.
Thank you.
Re: How to reply a list message using Gmail with Evolution?
On Mon, Jan 30, 2017 at 02:40:34PM +0800, River Chiang wrote: > Hello List, > > I use Firefox to read lists, when I clicked the link > debian-user@lists.debian.org and tried to reply the message, > Evolution's setup window showed. I tried to setup Evolution to use > Gmail. > Unfortunately I didn't make it. > > What mail user agent you use to view/reply messages on this list? > > Or how to setup Evolution to use a Gmail account? > I use Gmail for this list. I have taught Inbox (Gmail) to put all messages for this forum into a user folder. Then I use fetchmail to download only that folder from Gmail and use mutt to read and/or reply to it on my local PC. The one slight non-optimal element of this is I still need to mark the mails in that folder as "Done" occasionally in Inbox, but that is no great hardship. I also separately have Evolution wired up to use Gmail, it was no particular sweat -- what in particular are you having trouble with? I do seem to recall Google insist you connect to them using TLS or SSL -- no insecure connections. Beyond that I recall it being straightforward. Mark
Re: How to reply a list message using Gmail with Evolution?
On Tue, 31 Jan 2017 00:13:56 +0900 Mark Fletcher wrote: Hello Mark and River, >seem to recall Google insist you connect to them using TLS or SSL -- no >insecure connections. Beyond that I recall it being straightforward. From what I've read online over the past year or so they (google) now also require that you allow 'insecure' software to connect to their systems in your user preferences. By the term insecure they mean 'not written by google'. Where the setting resides within their prefs pages, I have no idea. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Early morning when I wake up, I look like Kiss but without the make up Strong - Robbie Williams pgpzJZQCfB5Bt.pgp Description: OpenPGP digital signature
Re: Oddity noticed installing caja-gksu, Bug?
On Sun 29 Jan 2017 at 08:58:17 (-0600), Richard Owlett wrote: > I using Debian 8.6.0 [with *NO* updates] from set of purchased DVDs. > I use the Mate desktop. > > When I installed caja-gksu, it did not apparently have any effect > until after a reboot. Is this expected? Installation should affect new instances of caja. It won't affect any caja instances already running at the time you installed caja-gksu. Next time you install Debian, you could test examples of each type of instance, before and after, to establish the presence of any bug. > I found no indication either way in a web search. I don't think one would expect to, unless you searched for "ldconfig". Caja is just one program among thousands that would be expected to behave in the same way. Try: http://www.tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html Cheers, David.
Impossible to install debian-8.7.1-i386-netinst.iso
On an old computer, with an USB keyboard, the install stops on the first screen. The keyboard is not active (but it works fine in the bios !). A similar problem is described in http://www.kasploosh.com/weblog/14000/14016-debian_jessie_usb_keyboard.html Is there a workaround ? Thanks PC
Re: Recreating a second boot kernel in LILO
On 01/14/2017 05:38 PM, Stephen Powell wrote: On Sat, Jan 14, 2017, at 10:05, Richard Owlett wrote: On 1/14/2017 8:45 AM, Miroslav Skoric wrote: Hello all, Intro: I have been using LILO for ages. Now running Wheezy 7.11 LTS. As usual and for test purposes on older machines I have two kernel flavours: 486 and 686-rt. In LILO boot menu they appear as Linux486 and Linux686 (before renaming they were Linux and LinuxOLD). Both work nice on two desktops of different age. Anyway, few years ago I had a repetitive problem with the 686-rt kernel slowing down the touch pad on a laptop, so I decided to remove it completely. So in the LILO menu was left just one boot option. Recently I decided to install 686-rt again, and during the installation it added new config*, init.rd*, and vmlinuz* into /boot, but it did not add any new init.rd* and vmlinuz* links into /. And without that LILO still keeps one entry. Any idea how to produce new links in / in order to recreate the second boot entry? (In lilo.conf everything is the same as in desktops, however /sbin/lilo complains about missing links in /) M.S. You may find Steve Powell's LILO Page useful - http://www.stevesdebianstuff.org/lilo.htm Also http://www.stevesdebianstuff.org/index.htm may be of interest. HTH The default installation of lilo assumes that the user is only interested in booting the two most recently-installed kernels. By Debian convention, symbolic links are assigned to these kernels in / if "do_symlinks = yes" is specified in /etc/kernel-img.conf. The most recent kernel is assigned the symbolic link name "vmlinuz", and the next-most-recent kernel is assigned the symbolic link name "vmlinuz.old". The same pattern is followed with the initial RAM file system images that correspond to these kernel images. The most recent initial RAM file system image is given the symbolic link name "initrd.img", and the next-most-recent initial RAM file system image is given the symbolic link name "initrd.img.old". If "link_in_boot = yes" is present in /etc/kernel-img.conf, then these symbolic links are maintained in /boot instead of in /. However, these symbolic links are maintained only for stock Debian kernels. For custom kernels created with make-kpkg or "make deb-pkg", "do_symlinks = yes" in /etc/kernel-img.conf has no effect. In my web page, referred to above by Richard Owlett, I provide a reference to my kernel building web page where there are execs called zy-symlinks which will provide equivalent function for custom kernels. If there are special kernels that you want to be able to boot which are outside the normal "last two", then you must manually edit /etc/lilo.conf to provide the capability to boot this kernel, then run lilo. Thank you all for your comments. Anyway, I think when I made the initial install several years ago (it was Squeeze 6.0.1a) it offered more than one kernel option for installation, so I probably chose two flavours to be installed, or something like that. So whenever a new kernel update appeared after that, it flawlessly updated both flavours (486 version & 686-rt version). So I always ended with two new kernels, and I could test/use them interchangeably. Yes I know that was not in accord with best LILO practices, but it worked for me. And I also realized the risk of neither update to be of 100% quality, but what is a chance that both kernel flavours might fail in the same update cycle? Anyway, I have managed to recreate a second boot kernel in LILO, so things work nice for now. M.S.
Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016
Ennio-Sr writes: > Has any of you benn able to pair the subject keyboard with bluetooth > under linux debian/jessie or stretch? [...] I have a bluetooth keyboard different model (the model without numeric keys) and to pair in a debian stable I needed to install also the bluez-firmware package: after this I paired with standard gnome tools. -- leandro 1A0B 125B 2E4D 2DAE 4E26 4551 88FB BBCC 7A29 640B https://bbs.cybervalley.org/ChiaveLeandro/gpg.html http://6xukrlqedfabdjrb.onion signature.asc Description: PGP signature
Re: Oddity noticed installing caja-gksu, Bug?
On 01/30/2017 11:49 AM, David Wright wrote: On Sun 29 Jan 2017 at 08:58:17 (-0600), Richard Owlett wrote: I using Debian 8.6.0 [with *NO* updates] from set of purchased DVDs. I use the Mate desktop. When I installed caja-gksu, it did not apparently have any effect until after a reboot. Is this expected? Installation should affect new instances of caja. The last time I did any low level coding the 8085 was state of the art ;/ The key question is likely just what defines "a new instance". IIRC there were no open caja "windows". Could be mistaken. It won't affect any caja instances already running at the time you installed caja-gksu. Next time you install Debian, you could test examples of each type of instance, before and after, to establish the presence of any bug. Your timing is exquisite. I just solved a problem whose repercussions added much cuff to my install before I got it right. I was planning an install from scratch by the weekend. Due to previous install experiments, I've a customized preseed.cfg that makes test installs trivial. I found no indication either way in a web search. I don't think one would expect to, unless you searched for "ldconfig". Caja is just one program among thousands that would be expected to behave in the same way. Try: http://www.tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html Looks like I'm out of mischief for the weekend. Thanks Cheers, David.
CUPS in stretch Ricoh printer SP112 SP112-su
I used to try and set up a printer through localhost:631 in Jessie but now in stretch it is impossible. I foung some link about /etc/hosts.allow and deny and tried a few things but still no luck. Maybe I am not using the correct statement and tried localhost and 127.0.0.1 but still no luck. And this is for trying to plug a ppd that was hacked from an other Ricoh printer to fit an SP112 SP112-su I figured what did not work for jessie may work for stretch I had gotten the same printer to work on an other machine with jessie somewhere around 8.5 but not on this one. Any suggestions on how to reach the blocked :631 link?
Re: How to reply a list message using Gmail with Evolution?
On Mon, Jan 30, 2017 at 03:32:12PM +, Brad Rogers wrote: > On Tue, 31 Jan 2017 00:13:56 +0900 > Mark Fletcher wrote: > > Hello Mark and River, > > >seem to recall Google insist you connect to them using TLS or SSL -- no > >insecure connections. Beyond that I recall it being straightforward. > > From what I've read online over the past year or so they (google) now > also require that you allow 'insecure' software to connect to their > systems in your user preferences. By the term insecure they mean 'not > written by google'. Where the setting resides within their prefs pages, > I have no idea. > Yes, you are not the first person to say this -- but I didn't have to do anything like this to get Evolution to work. I suspect the need for this is less widespread than is being put about on the 'net. Mark
Early boot became slower
Felix Miata: At what point exactly within either of those videos does 80 by 25 appear? All I saw anywhere appeared to be in the vicinity of 240 by 67. I think that I have put my finger on the source of your perplexity. Remember where M. Oss said the following? Mattia Oss: This can be seen in the 3rd video. There's a third video, and it appears in the third video. It's definitely 80*25 VGA text mode in that third video. And just as M. Oss said, the text in the third video scrolls fairly briskly and the characters are ... Mattia Oss: HUGE characters. ... as one would expect with 80 columns by 25 rows on a widescreen display of that size. Now M. Oss and all of you get to play with the different ways that the VESA driver can do scrolling. (-:
Re: Impossible to install debian-8.7.1-i386-netinst.iso
On Mon, Jan 30, 2017 at 07:53:56PM +0100, Pierre Couderc wrote: > On an old computer, with an USB keyboard, the install stops on the first > screen. > > The keyboard is not active (but it works fine in the bios !). > > A similar problem is described in > http://www.kasploosh.com/weblog/14000/14016-debian_jessie_usb_keyboard.html > > Is there a workaround ? > I have a feeling someone else faced a similar problem somehwat recently (say in the last 6-12 months) and there was a boot parameter that sorted it for them. I'm afraid I don't remember details. The closest I have personally come to this is finding a Bluetooth keyboard not working at that stage, but a wired USB keyboard did work. That was a release or two of Jessie ago. I'd suggest that Google will make short work of searching the archives of this list to find the answer. Mark
Re: CUPS in stretch Ricoh printer SP112 SP112-su
On Mon, Jan 30, 2017 at 10:47:24PM +0100, r...@openmailbox.org wrote: > I used to try and set up a printer through localhost:631 in Jessie but now > in stretch it is impossible. I foung some link about /etc/hosts.allow and > deny and tried a few things but still no luck. Maybe I am not using the > correct statement and tried localhost and 127.0.0.1 but still no luck. > And this is for trying to plug a ppd that was hacked from an other Ricoh > printer to fit an SP112 SP112-su > I figured what did not work for jessie may work for stretch > I had gotten the same printer to work on an other machine with jessie > somewhere around 8.5 but not on this one. > > Any suggestions on how to reach the blocked :631 link? > Potentially stupid question -- are you sure the URL is blocked and it's not simply that CUPS is not running? $ ps -ef | grep cups on my system I get: root 907 1 0 Jan15 ?00:00:00 /usr/sbin/cups-browsed root 31985 1 0 07:35 ?00:00:00 /usr/sbin/cupsd -f That is the first possibility to eliminate. Mark
Re: CUPS in stretch Ricoh printer SP112 SP112-su
On Tue 31 Jan 2017 at 07:54:11 +0900, Mark Fletcher wrote: > On Mon, Jan 30, 2017 at 10:47:24PM +0100, r...@openmailbox.org wrote: > > I used to try and set up a printer through localhost:631 in Jessie but now > > in stretch it is impossible. I foung some link about /etc/hosts.allow and > > deny and tried a few things but still no luck. Maybe I am not using the > > correct statement and tried localhost and 127.0.0.1 but still no luck. > > And this is for trying to plug a ppd that was hacked from an other Ricoh > > printer to fit an SP112 SP112-su > > I figured what did not work for jessie may work for stretch > > I had gotten the same printer to work on an other machine with jessie > > somewhere around 8.5 but not on this one. > > > > Any suggestions on how to reach the blocked :631 link? > > > > Potentially stupid question -- are you sure the URL is blocked and it's > not simply that CUPS is not running? It doesn't really matter. Ricoh has the SP 112 down as using the DDST (whatever that stands for) language to communicate with the device. It needs a host-based driver on the computer. It is very doubtful there is a free one in Debian. -- Brian.
Re: CUPS in stretch Ricoh printer SP112 SP112-su
On 2017-01-30 22:47, r...@openmailbox.org wrote: And this is for trying to plug a ppd that was hacked from an other Ricoh printer to fit an SP112 SP112-su I figured what did not work for jessie may work for stretch I had gotten the same printer to work on an other machine with jessie somewhere around 8.5 but not on this one. Any suggestions on how to reach the blocked :631 link? Same printer, not very different AMD64, and based on the hacked ppd available on github it worked flawlessly ... I started on 8.6 on this one when it was fresh and never got it to work following the same procedure. But localhost:631 worked and the browser hasn't changed much (from what I do to it). I suspect it is running as you say but how do I reach it or what is blocking access to it? Or what do I put in host.allow hosts.deny to unblock it if that is the culprit. And WHY did debian change such a thing? Security security security? Basic early upgrade from stable to testing is the only change that I am responsible for. C:\ ps -ef | grep cups roots 361 1 0 Jan30 ?00:00:00 /usr/sbin/cupsd -l roots 467 1 0 Jan30 ?00:00:00 /usr/sbin/cups-browsed rock 6128 6115 0 01:20 pts/200:00:00 grep cups lp 15797 361 0 Jan30 ?00:00:00 /usr/lib/cups/notifier/dbus dbus:// C:\:)
Re: Early boot became slower
Jonathan de Boyne Pollard composed on 2017-01-30 22:31 (UTC): Felix Miata composed: At what point exactly within either of those videos does 80 by 25 appear? All I saw anywhere appeared to be in the vicinity of 240 by 67. I think that I have put my finger on the source of your perplexity. Remember where M. Oss said the following? Mattia Oss: This can be seen in the 3rd video. There's a third video, and it appears in the third video. It's definitely 80*25 VGA text mode in that third video. And just as M. Oss said, the text in the third video scrolls fairly briskly and the characters are ... Mattia Oss: HUGE characters. ... as one would expect with 80 columns by 25 rows on a widescreen display of that size. Now that I've seen that... Now M. Oss and all of you get to play with the different ways that the VESA driver can do scrolling. (-: ...I reread OP's thread posts and see he has yet to provide us a look at /proc/cmdline from a boot that produces (huge text) 80x25 mode. I would like to see that before I consider whether to respond further. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
Synaptic broke
I just ran across a problem with synaptic. When I start this program, I get a dialog box saying: The value 'jessie-backports' is invalid for APT::Default-Release as such a release is not available in the sources Synaptic then exits with no opportunity to make any changes. I have tried to find where this setting is to fix it, but have had no luck. I have purged and re-installed synaptic with no luck. I am running a fully updated jessie (8.7) system. Anyone have any ideas how to repair this?? -- 73's de Mike, WB5VQX
[Solved??] Re: Synaptic broke
On 01/30/2017 08:32 PM, Michael Milliman wrote: I just ran across a problem with synaptic. When I start this program, I get a dialog box saying: The value 'jessie-backports' is invalid for APT::Default-Release as such a release is not available in the sources Synaptic then exits with no opportunity to make any changes. I have tried to find where this setting is to fix it, but have had no luck. I have purged and re-installed synaptic with no luck. I am running a fully updated jessie (8.7) system. Anyone have any ideas how to repair this?? I ran apt-get update (which noted a hash sum mismatch on jessie-backports repositories) and apt-get upgrade. I then tried synaptic again, and it seems the problem has cleared itself. Very strange. -- 73's de Mike, WB5VQX -- 73's de Mike, WB5VQX
Re: Oddity noticed installing caja-gksu, Bug?
On Mon 30 Jan 2017 at 14:47:41 (-0600), Richard Owlett wrote: > On 01/30/2017 11:49 AM, David Wright wrote: > >On Sun 29 Jan 2017 at 08:58:17 (-0600), Richard Owlett wrote: > >>I using Debian 8.6.0 [with *NO* updates] from set of purchased DVDs. > >>I use the Mate desktop. > >> > >>When I installed caja-gksu, it did not apparently have any effect > >>until after a reboot. Is this expected? > > > >Installation should affect new instances of caja. > > The last time I did any low level coding the 8085 was state of the > art ;/ The key question is likely just what defines "a new > instance". IIRC there were no open caja "windows". Could be > mistaken. A process. I don't know what a caja window represents as I've never used it. But a newly started process will see new links to the libraries, including the one you just installed, libcaja-gksu. > It won't affect any > >caja instances already running at the time you installed caja-gksu. > >Next time you install Debian, you could test examples of each type > >of instance, before and after, to establish the presence of any bug. > > Your timing is exquisite. I just solved a problem whose > repercussions added much cuff to my install before I got it right. I > was planning an install from scratch by the weekend. Due to previous > install experiments, I've a customized preseed.cfg that makes test > installs trivial. Well, guessing that you will reinstall soon is a bit of a no-brainer; how many times have you installed Debian over the last five years? (Of course, one could just uninstall the library and then reinstall it to perform the tests.) > >>I found no indication either way in a web search. > > > >I don't think one would expect to, unless you searched for "ldconfig". > >Caja is just one program among thousands that would be expected to > >behave in the same way. Try: > > > >http://www.tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html > > Looks like I'm out of mischief for the weekend. > Thanks Cheers, David.
Re: Early boot became slower
On Mon 30 Jan 2017 at 22:31:28 (+), Jonathan de Boyne Pollard wrote: > Felix Miata: > > >At what point exactly within either of those videos does 80 by 25 > >appear? All I saw anywhere appeared to be in the vicinity of 240 > >by 67. > > I think that I have put my finger on the source of your perplexity. > Remember where M. Oss said the following? > > Mattia Oss: > > >This can be seen in the 3rd video. > > There's a third video, and it appears in the third video. It's > definitely 80*25 VGA text mode in that third video. Yes, there were three videos originally, viz. 16199062 goo-1-line-7-boot-4.8.0-1-amd64.mkv 15994161 goo-2-line-1-boot-4.9.0-1-amd64.mkv 10878351 goo-3-line-1-boot-text-4.9.0-1-amd64.mkv (though I guess the precise lengths my depend on the software used to download them?) But that only translated to two youtube videos, viz. 4587493 you-1-line-7-linux-image-4.8.0-1-amd64.bootvideo-NLWB7FyV7jU.mp4 5927576 you-2-line-4-linux-image-4.8.0-2-amd64.bootvideo-Nc1lgpdgaxQ.mp4 I don't see a low-res period in either of the latter. I suspect the OP didn't bother with the third video, notwithstanding the discussion about it. Should I take it that the "HUGE" characters are just a result of a period at 640x480 resolution? > And just as M. > Oss said, the text in the third video scrolls fairly briskly and the > characters are ... > > Mattia Oss: > > >HUGE characters. > > > ... as one would expect with 80 columns by 25 rows on a widescreen > display of that size. > > Now M. Oss and all of you get to play with the different ways that > the VESA driver can do scrolling. (-: But if the OP intended people to attend only to the rate at which lines appear on the screen, then posting videos at 1920x1080 was a waste of time for many, because the rate at which the video runs is a function of the power of the recipient's computer. None of mine are able to run these videos at all smoothly. Cheers, David.
Not sure where to report this issue...
I am running debian sid and currently all video players the video freezes when I try to play a video. Also the KDE desktop will freeze until I change to one of the virtual terminals with CTRL-ALT-F? and then back to KDE desktop with ALT-F7. It will then work for a bit then freeze again. mpv - freezes, both audio and video stop. mplayer - freezes, video stops, audio continues. xine - freezes, video stops, audio continues. I have to use the kill command on them to close them. On mpv if I use -vo= xv or x11 it will work all others (vdpau, opengl, sdl, vaapi) freeze except for drm which gets the below error [vo/drm] VT_GETMODE failed: Inappropriate ioctl for device [vo/drm] Failed to set up VT switcher. Terminal switching will be unavailable. [vo/drm] Cannot set CRTC: Permission denied Error opening/initializing the selected video_out (--vo) device. --- lspci -nn | grep VGA 08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] --- xrandr --listproviders Providers: number : 1 Provider 0: id: 0x54 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 2 outputs: 3 associated providers: 0 name:ATI Radeon 4800 Series @ pci::08:00.0 --- xrandr --setprovideroffloadsink radeon Intel Could not find provider with name radeon --- DRI_PRIME=1 glxinfo | grep "OpenGL renderer" OpenGL renderer string: Gallium 0.4 on AMD RV770 (DRM 2.48.0 / 4.9.0-1-amd64, LLVM 3.9.1) --- From /var/log/dmesg [ 12.804277] [drm] radeon kernel modesetting enabled. [ 12.859566] [drm] initializing kernel modesetting (RV770 0x1002:0x9440 0x1043:0x0388). [ 12.859595] [drm] register mmio base: 0xFE9E [ 12.859600] [drm] register mmio size: 65536 [ 12.860436] ATOM BIOS: 9440.11.17.0.18.AS01 [ 12.860492] radeon :08:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [ 12.860499] radeon :08:00.0: GTT: 1024M 0x4000 - 0x7FFF [ 12.860503] [drm] Detected VRAM RAM=1024M, BAR=256M [ 12.860507] [drm] RAM width 256bits DDR [ 12.860688] [TTM] Zone kernel: Available graphics memory: 4097956 kiB [ 12.860692] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [ 12.860695] [TTM] Initializing pool allocator [ 12.860707] [TTM] Initializing DMA pool allocator [ 12.860748] [drm] radeon: 1024M of VRAM memory ready [ 12.860752] [drm] radeon: 1024M of GTT memory ready. [ 12.860775] [drm] Loading RV770 Microcode [ 12.951699] radeon :08:00.0: firmware: direct-loading firmware radeon/RV770_pfp.bin [ 12.986773] radeon :08:00.0: firmware: direct-loading firmware radeon/RV770_me.bin [ 13.003314] radeon :08:00.0: firmware: direct-loading firmware radeon/R700_rlc.bin [ 13.080896] radeon :08:00.0: firmware: direct-loading firmware radeon/RV770_smc.bin [ 13.080912] [drm] Internal thermal controller with fan control [ 13.081034] [drm] radeon: power management initialized [ 13.081047] [drm] GART: num cpu pages 262144, num gpu pages 262144 [ 13.084763] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [ 13.088409] [drm] PCIE GART of 1024M enabled (table at 0x0004). [ 13.088434] radeon :08:00.0: WB enabled [ 13.088436] radeon :08:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x88022bd43c00 [ 13.088438] radeon :08:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0x88022bd43c0c [ 13.088440] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 13.088440] [drm] Driver supports precise vblank timestamp query. [ 13.088459] radeon :08:00.0: irq 90 for MSI/MSI-X [ 13.088467] radeon :08:00.0: radeon: using MSI. [ 13.088487] [drm] radeon: irq initialized. [ 13.134370] [drm] ring test on 0 succeeded in 1 usecs [ 13.134436] [drm] ring test on 3 succeeded in 1 usecs [ 13.134763] [drm] ib test on ring 0 succeeded in 0 usecs [ 13.134786] [drm] ib test on ring 3 succeeded in 0 usecs [ 13.135401] [drm] Radeon Display Connectors [ 13.135405] [drm] Connector 0: [ 13.135409] [drm] VGA-1 [ 13.135412] [drm] DDC: no ddc bus - possible BIOS bug - please report to xorg-driver-...@lists.x.org [ 13.135414] [drm] Encoders: [ 13.135417] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [ 13.135420] [drm] Connector 1: [ 13.135423] [drm] HDMI-A-1 [ 13.135426] [drm] HPD1 [ 13.135431] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [ 13.135433] [drm] Encoders: [ 13.135436] [drm] DFP1: INTERNAL_UNIPHY [ 13.135439] [drm] Connector 2: [ 13.135441] [drm] DVI-I-1 [ 13.135444] [drm] HPD2 [ 13.135449] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c [ 13.135451] [drm] Encoders: [ 13.135454] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 13.135457] [drm] DFP2: INTERNAL_KLDSCP_LVTMA [ 13.182521] [drm] fb mappable at 0xD0241000 [ 13.182529] [drm] vra
Re: Bluetooth: unable to pair Apple Wireless Keyboard Mod. A1016
On Monday, January 30, 2017 9:10:59 PM CET Leandro Noferini wrote: > I have a bluetooth keyboard different model (the model without numeric > keys) and to pair in a debian stable I needed to install also the > bluez-firmware package: after this I paired with standard gnome tools. I also believe you could give bluez-firmware a try. I had a pairing issue with a different device (a speaker), and I could only solved it with that package.
