16 Jul
2020
16 Jul
'20
3:19 p.m.
Hello all,
I am having a few problems with Debian 10 (Buster) 64 bit, the image,
even during the boot sequence, more than fills the screen. I loose
some of the text off the left edge of the screen, and more all round
once up and running with Wayland, including the top bar. I also am
having trouble resizing windows, currently Firefox is running
maximised, but I want to reduce it a bit and I am having trouble
getting any response.
It is running on an AMD Ryzen 5 with 16 Gb of ram, and Gigabyte Nvidia
Geforce GT 710 video card (NV106) driving a 24" LED Wintal 12V TV.
While I can comprehend what Wayland is trying to do, and why, I am
finding the discard of the older metaphors and way of working to be a
serious "bug". They do have some excellent ideas, the top left corner
hotspot is not intuitive, at least at first, and the new "menu" is not
without merit, but such abandonment of prior ways of working is more
than just irritating, it gets in the way of doing things.
Regards,
Mark Trickett
17 Jul
17 Jul
11:39 p.m.
On Thursday, 16 July 2020 3:19:19 PM AEST Mark Trickett via luv-main wrote:
It is running on an AMD Ryzen 5 with 16 Gb of ram, and
Gigabyte Nvidia
Geforce GT 710 video card (NV106) driving a 24" LED Wintal 12V TV.
Firstly while it's not related to the issues you are having, I think you
should consider buying an ATI video card. Every time I've used NVidia I've
had problems related to driver support. Currently I'm supporting a Windows 10
system that's reliably running with a 4K video card that would cause regular
system crashes in two different Linux systems.
https://mjg59.dreamwidth.org/8705.html
Next what type of TV is this and how are you connecting to it? The above blog
post has some information on how TVs don't work in a sane manner, possibly
some of the issues in that post apply to you. If so you can probably get it
working properly (with some effort) but probably can't get the best quality.
https://www.kogan.com/au/buy/kogan-24-full-hd-curved-75hz-freesync-gaming-m…
Here's a 24" FullHD monitor for $160 plus postage. That should just work for
the full screen display and not look fuzzy. Then you can have TV playing as
well while you look at your computer during ad breaks. ;)
https://www.kogan.com/au/buy/kogan-24-qhd-freesync-75hz-monitor-2560-x-1440/
Here's a 24" 2560*1440 monitor for $280.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
18 Jul
18 Jul
3:47 p.m.
Hello Russell,
On 7/17/20, Russell Coker <russell(a)coker.com.au> wrote:
On Thursday, 16 July 2020 3:19:19 PM AEST Mark
Trickett via luv-main wrote:
The card was a relatively cheap option to work with a new motherboard,
the PC that you gave me failed, seemed like MB or CPU, income had
improved, enough, so I bought a MSI mainboard and Ryzen CPU, the board
had video connectors, but the CPU did not include the video. It was a
way to have video, without having any recommendation. I may buy
something else, but timing is a bit of a pain at the moment with not
supposed to travel.
To get it as I currently want, I just need to be able to tell the
video system to not use a uniform margin all round. The colour and
crispness is not an issue, although I would not rely on the colour for
photography, that is where I would look at the monitors you suggest.
It may be that I need to redo the initial probe and detection for
video configuration. As to TV at home, I have no free to air land
based signal, I have to use a VAST box (Viewer Assisted Satellite
Television), that is currently out of service. It is a UEC box,
actually a small Linux box, but without external access, it has an
ethernet port, but not enabled. If it continues to not work and I get
another, I would like to bring it to a LUV workshop for the curious.
It is running on an AMD Ryzen 5 with 16 Gb of
ram, and Gigabyte Nvidia
Geforce GT 710 video card (NV106) driving a 24" LED Wintal 12V TV.
Firstly while it's not related to the issues you are having, I think you
should consider buying an ATI video card. Every time I've used NVidia I've
had problems related to driver support. Currently I'm supporting a Windows
10 system that's reliably running with a 4K video card that would cause regular
system crashes in two different Linux systems. https://mjg59.dreamwidth.org/8705.html
Next what type of TV is this and how are you connecting to it? The above
blog post has some information on how TVs don't work in a sane manner, possibly
some of the issues in that post apply to you. If so you can probably get it
working properly (with some effort) but probably can't get the best
quality.
it is a 12V Wintal 24" LED TV, I bought from Radio Parts, I intend to
use it more with a Raspberry Pi to have a 12V system for mobile and
remote computing. When I go to various events demonstrating
handspinning, I would like to have computing facility, and the
capacity to play a video of what I do when I have to go to the toilet
or get lunch.
https://www.kogan.com/au/buy/kogan-24-full-hd-curved-75hz-freesync-gaming-m…
Here's a 24" FullHD monitor for $160 plus postage. That should just work
for the full screen display and not look fuzzy. Then you can have TV playing as
well while you look at your computer during ad breaks. ;)
https://www.kogan.com/au/buy/kogan-24-qhd-freesync-75hz-monitor-2560-x-1440/
Here's a 24" 2560*1440 monitor for $280.
I am also running into another issue, a Debian bug with scanning. I
have been reading up, but the behaviour is puzzling. SimpleScan works,
but scanimage and the other command linme tools do not see the
scanner, but it is there when I do lsusb. The scanner is a Canon LIDE
210, and it works well on the out of date Debian on the Acer
TravelMate 3230. I appear to have appropriate permissions and such,
but some detail is still out of place. I may try adding myself to the
scanner group, but that should not be necessary. I want to use
scanimage as I can increment an index number for each page the way I
want, which is not the way SimpleScan does.
Regards,
Mark Trickett
12:24 a.m.
Hi Mark.
I had a similar problem with a TV and a raspberry pi model 4B.
Turned out the answer in my case was the TV was doing the
trim off the edges trick to make broadcast content look a
bit clearer and less fuzzy around the edges.
Turned off the function on the TV and all the problems went away.
The pi was happily setting itself to the reported 1920x1080 resolution,
but the TV wasn't displaying the full reported resolution.
It may not be your case, but it's another thing worth checking.
Regards,
Morrie.
-----Original Message-----
From: luv-main [mailto:luv-main-bounces@luv.asn.au] On Behalf Of Mark
Trickett via luv-main
Sent: Thursday, 16 July 2020 3:19 PM
To: Luv Main
Subject: Resizing the whole screen with Debian 10 and Wayland
Hello all,
I am having a few problems with Debian 10 (Buster) 64 bit, the image,
even during the boot sequence, more than fills the screen. I loose
some of the text off the left edge of the screen, and more all round
once up and running with Wayland, including the top bar. I also am
having trouble resizing windows, currently Firefox is running
maximised, but I want to reduce it a bit and I am having trouble
getting any response.
It is running on an AMD Ryzen 5 with 16 Gb of ram, and Gigabyte Nvidia
Geforce GT 710 video card (NV106) driving a 24" LED Wintal 12V TV.
While I can comprehend what Wayland is trying to do, and why, I am
finding the discard of the older metaphors and way of working to be a
serious "bug". They do have some excellent ideas, the top left corner
hotspot is not intuitive, at least at first, and the new "menu" is not
without merit, but such abandonment of prior ways of working is more
than just irritating, it gets in the way of doing things.
Regards,
Mark Trickett
_______________________________________________
luv-main mailing list
luv-main(a)luv.asn.au
https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
3:51 p.m.
On 7/18/20, Morrie Wyatt via luv-main <luv-main(a)luv.asn.au> wrote:
Hi Mark.
I had a similar problem with a TV and a raspberry pi model 4B.
Turned out the answer in my case was the TV was doing the
trim off the edges trick to make broadcast content look a
bit clearer and less fuzzy around the edges.
Turned off the function on the TV and all the problems went away.
The pi was happily setting itself to the reported 1920x1080 resolution,
but the TV wasn't displaying the full reported resolution.
It may not be your case, but it's another thing worth checking.
That has worked. I do not remember doing that previously when I had
less of an issue. It may have been reset at some point since then.
Regards,
Morrie.
Regards,
Mark Trickett
984
days inactive
986
days old
4 comments
3 participants
participants (3)
-
Mark Trickett -
Morrie Wyatt -
Russell Coker