4:07 p.m.
Installed latest nightly build tonight and I have found the following
issues:
1) there is no password request for root user
2) at start-up lines are out of the boundary of the screen (I am using a
32" Led TV full HD with resolution with 1920x1080 resolution): I had to
reduce also in Fedora to 1280×720 otherwise some space is out of the
screen, i.e. menu is invisible
3) at first boot I had a lot of updates, I told the computer to reboot
(installing updates) but at 97% screen froze..I made a hard reboot and
everything went fine. What happened?
Antonio Montagnani
Linux Fedora 24 (Workstation)
inviato da Gmail
8:22 a.m.
On Thu, Oct 20, 2016 at 10:07 PM, Antonio M
<antonio.montagnani(a)gmail.com> wrote:
Installed latest nightly build tonight and I have found the
following
issues:
1) there is no password request for root user
You set the root password as part of the initial setup
2) at start-up lines are out of the boundary of the screen (I am
using a 32"
Led TV full HD with resolution with 1920x1080 resolution): I had to reduce
also in Fedora to 1280×720 otherwise some space is out of the screen, i.e.
menu is invisible
There should be a menu option in the TV to adjust the output to fit.
Something like auto adjust, it's worked on 3-4 TVs that I've tested it
on.
3) at first boot I had a lot of updates, I told the computer to
reboot
(installing updates) but at 97% screen froze..I made a hard reboot and
everything went fine. What happened?
There should only be testing updates if it's the latest nightly. What
method were you using to apply updates. What desktop environment etc?
Peter
8:35 a.m.
1) there was no request of initial password fro root user in initial user,
I am sure of it
2) I have to check in my tv-set: I will report it back as soon I will be
back home
3) When I shut down I was asked if I wanted to apply pending updates and
reboot: I said yes and that's all. All updates were o.k., it seemed only a
frozen system
I am using Fedora Workstation with Gnome DE
I have another issue related to keyboard (I am using an Italian Keyboard
and it was set as italian): when I write something in the top line of Gnome
(when I am looking for application) when I push a character on the keyboard
I gent many characters (only in this window, terminal is o.k., i.e I push d
and I get ddd)
Tnx for help
Antonio Montagnani
Linux Fedora 24 (Workstation)
inviato da Gmail
2016-10-21 15:22 GMT+02:00 Peter Robinson <pbrobinson(a)gmail.com>:
On Thu, Oct 20, 2016 at 10:07 PM, Antonio M
<antonio.montagnani(a)gmail.com> wrote:
> Installed latest nightly build tonight and I have found the following
> issues:
>
> 1) there is no password request for root user
You set the root password as part of the initial setup
> 2) at start-up lines are out of the boundary of the screen (I am using a
32"
> Led TV full HD with resolution with 1920x1080 resolution): I had to
reduce
> also in Fedora to 1280×720 otherwise some space is out of the screen,
i.e.
> menu is invisible
There should be a menu option in the TV to adjust the output to fit.
Something like auto adjust, it's worked on 3-4 TVs that I've tested it
on.
> 3) at first boot I had a lot of updates, I told the computer to reboot
> (installing updates) but at 97% screen froze..I made a hard reboot and
> everything went fine. What happened?
There should only be testing updates if it's the latest nightly. What
method were you using to apply updates. What desktop environment etc?
Peter
9:29 a.m.
Peter Robinson ha scritto il 21/10/2016 alle 15:22:
On Thu, Oct 20, 2016 at 10:07 PM, Antonio M
<antonio.montagnani(a)gmail.com> wrote:
>
> 2) at start-up lines are out of the boundary of the screen (I am using a 32"
> Led TV full HD with resolution with 1920x1080 resolution): I had to reduce
> also in Fedora to 1280×720 otherwise some space is out of the screen, i.e.
> menu is invisible
from a survey of my Samsung Smart TV automatic option is disabled!!! but
in my opinion the boot procedure should know the screen resolution (as
Raspbian does) and in ant case I should see all the screen when set in
Fedora at 1920xsomething....
Any hint how to solve this isuue??
--
Antonio M
Skype: amontag52
Linux Fedora F24 (Workstation Edition)
on Fujitsu Lifebook A512
http://lugsaronno.altervista.org
http://campingmonterosa.altervista.org
4:55 a.m.
>> 2) at start-up lines are out of the boundary of the screen (I
am using a
>> 32"
>> Led TV full HD with resolution with 1920x1080 resolution): I had to
>> reduce
>> also in Fedora to 1280×720 otherwise some space is out of the screen,
>> i.e.
>> menu is invisible
>
>
from a survey of my Samsung Smart TV automatic option is disabled!!! but in
my opinion the boot procedure should know the screen resolution (as Raspbian
does) and in ant case I should see all the screen when set in Fedora at
1920xsomething....
Any hint how to solve this isuue??
So Raspbian uses a completely different kernel and driver stack, most
of the options documented in config.txt are completely irrelevant for
the new driver stack (nothing to do with the Fedora side of things).
The auto adjustment in the screen settings has worked every single
time for me, why can't you use this?
Peter
7:12 a.m.
I could set the screen resolution to correct resolution. The option is available only when
some devices are connected.
Tnx for help.
I started Firefox, DNF (Yumex) and a terminal in Gnome, but system froze, I tried to
connect by sshd, but no connection was available. I had to reset by hard reboot....
In another session using LXDE, DNF froze the system, and also setting froze the system...
7:30 a.m.
On Tue, Oct 25, 2016 at 1:12 PM, antonio montagnani
<antonio.montagnani(a)gmail.com> wrote:
I could set the screen resolution to correct resolution. The option
is available only when some devices are connected.
Was that with the new kernel?
Tnx for help.
I started Firefox, DNF (Yumex) and a terminal in Gnome, but system froze, I tried to
connect by sshd, but no connection was available. I had to reset by hard reboot....
It's only got 1Gb of RAM (some of which is used by the 3D driver) and
slow I/O so be aware it's not going to be the fastest at this and it
might run out of memory. Just remember it's a $35 device not a fast
x86 laptop.
In another session using LXDE, DNF froze the system, and also
setting froze the system...
On the 4 devices I have running (2 Pi3, 2 Pi2) a mix of minimal,
Workstation and XFCE they all run it "OK", it's by no means fast, I
tend to run dnf remotely via ssh in a screen session.
Peter
9:16 a.m.
I am running on 4.8.2-300.fc25.armv7hl, that is the only kernel that I have, as installed
from a nightly build from Fedora-Workstation-armhfp-25-20161019.n.0-sda.raw.xz
10:04 a.m.
after running dnf update I am running on 4.8.3-300.fc25.armv7hl.
Yumex-dnf doesn'f find any updates while dnf update founds 48 updates. Now I have only
the erratic behaviour of characters in the applicatio search window in Gnome.
Tnx for help
7:36 a.m.
Hi,
> from a survey of my Samsung Smart TV automatic option is
disabled!!! but in
So Raspbian uses a completely different kernel and driver stack,
most
of the options documented in config.txt are completely irrelevant for
the new driver stack (nothing to do with the Fedora side of things).
The auto adjustment in the screen settings has worked every single
time for me, why can't you use this?
Same problem here. Have configured overscan in config.txt[1]. That
works with the downstream kernel (and the BCM2708 fb driver). But as
you outlined already everything else (uboot, simplefb, vc4) ignores the
config.txt settings and I also havn't found any other way to configure
overscan.
I have a samsung tv too, with one of my rpi2's connected. Walked
through the tv menus playing with the settings, but couldn't make things
work properly.
So, no easy way out it seems?
cheers,
Gerd
[1]
overscan_left=24
overscan_right=24
overscan_top=16
overscan_bottom=16
disable_overscan=0
8:13 a.m.
On Tue, Nov 1, 2016 at 12:36 PM, Gerd Hoffmann <kraxel(a)redhat.com> wrote:
Hi,
> > from a survey of my Samsung Smart TV automatic option is disabled!!! but in
> So Raspbian uses a completely different kernel and driver stack, most
> of the options documented in config.txt are completely irrelevant for
> the new driver stack (nothing to do with the Fedora side of things).
> The auto adjustment in the screen settings has worked every single
> time for me, why can't you use this?
Same problem here. Have configured overscan in config.txt[1]. That
works with the downstream kernel (and the BCM2708 fb driver). But as
you outlined already everything else (uboot, simplefb, vc4) ignores the
config.txt settings and I also havn't found any other way to configure
overscan.
I have a samsung tv too, with one of my rpi2's connected. Walked
through the tv menus playing with the settings, but couldn't make things
work properly.
So, no easy way out it seems?
Not off hand, sadly we seem to be having the early adopters problem on
a 4.5 year old device :-/
It's a pity all the EDID and similarly related monitor detection stuff
wasn't shared across drivers in a central location. Going from a
closed driver with a forked kernel we've never supported to a fully
open upstream doesn't give us a lot of room. I'm not a graphics
developer, nor really a kernel developers, so we're at a combination
mercy of upstream and not even the ability to dig into the
driver/firmware to workout what the other driver does.
Open to suggestions but I've pulled in all the upstream fixes I'm aware of.
Peter
10:11 a.m.
Hi,
Not off hand, sadly we seem to be having the early adopters problem
on
a 4.5 year old device :-/
Indeed ...
It's a pity all the EDID and similarly related monitor detection
stuff
wasn't shared across drivers in a central location. Going from a
closed driver with a forked kernel we've never supported to a fully
open upstream doesn't give us a lot of room. I'm not a graphics
developer, nor really a kernel developers, so we're at a combination
mercy of upstream and not even the ability to dig into the
driver/firmware to workout what the other driver does.
When the firmware loads the kernel directly the downstream way (without
uboot) it adds a bunch of parameters to the kernel command line:
dma.dmachans=0x7f35
bcm2708_fb.fbwidth=1776 <- look
bcm2708_fb.fbheight=952 <- here
bcm2709.boardrev=0xa01041
bcm2709.serial=<censored>
smsc95xx.macaddr=<likewise>
bcm2708_fb.fbswap=1
bcm2709.uart_clock=48000000
bcm2709.disk_led_gpio=47
bcm2709.disk_led_active_low=0
vc_mem.mem_base=0x3dc00000 <- and
vc_mem.mem_size=0x3f000000 <- here
[ cmdline.txt content follows ]
So, the downstream firmware -> kernel parameter passing actually pretty
simple. I think at least parts of this are also passed via device tree
these days.
Given that downstream plans to switch to the vc4 driver I expected to
find some way to configure overscan with vc4 too (even if it doesn't
pick up the settings from config.txt). But so far I havn't found
anything. Sad to see you have no idea too.
cheers,
Gerd
10:32 a.m.
> Not off hand, sadly we seem to be having the early adopters
problem on
> a 4.5 year old device :-/
Indeed ...
> It's a pity all the EDID and similarly related monitor detection stuff
> wasn't shared across drivers in a central location. Going from a
> closed driver with a forked kernel we've never supported to a fully
> open upstream doesn't give us a lot of room. I'm not a graphics
> developer, nor really a kernel developers, so we're at a combination
> mercy of upstream and not even the ability to dig into the
> driver/firmware to workout what the other driver does.
When the firmware loads the kernel directly the downstream way (without
uboot) it adds a bunch of parameters to the kernel command line:
dma.dmachans=0x7f35
bcm2708_fb.fbwidth=1776 <- look
bcm2708_fb.fbheight=952 <- here
bcm2709.boardrev=0xa01041
bcm2709.serial=<censored>
smsc95xx.macaddr=<likewise>
bcm2708_fb.fbswap=1
bcm2709.uart_clock=48000000
bcm2709.disk_led_gpio=47
bcm2709.disk_led_active_low=0
vc_mem.mem_base=0x3dc00000 <- and
vc_mem.mem_size=0x3f000000 <- here
[ cmdline.txt content follows ]
So, the downstream firmware -> kernel parameter passing actually pretty
simple. I think at least parts of this are also passed via device tree
these days.
Given that downstream plans to switch to the vc4 driver I expected to
find some way to configure overscan with vc4 too (even if it doesn't
pick up the settings from config.txt). But so far I havn't found
anything. Sad to see you have no idea too.
Well as I mentioned I'm not a kernel/GPU/X developer so I wouldn't
expect myself to have much of an idea.... Jack of all trades...
My understanding is that downstream those are hacks and the intention
is to have it automatically deal with that like pretty much all other
drivers do so hacks won't be needed. I have no idea any form of
timeline for that.
2731
days inactive
2743
days old
12 comments
4 participants
participants (4)
-
Antonio M -
antonio montagnani -
Gerd Hoffmann -
Peter Robinson