Gnome's Video tool it gets stuck and flickering
and the Xorg server log file complains:
[ 822.310] (EE) modeset(0): Failed to make 1280x913x32bpp GBM bo
Any idea where that might come from?
Best
-Alex
On Wed, 2024-03-20 at 10:03 -0500, Hank Barta wrote:
> Boy, bash really did not
hings.
-Alex
On Wed, 2024-03-20 at 08:43 -0500, Hank Barta wrote:
> I'll give it a try.
>
> hbarta@cm4iob:~/bin$ cd /sys/devices/system/cpu/cpufreq/policy0/
> hbarta@cm4iob:/sys/devices/system/cpu/cpufreq/policy0$ cat
> scaling_driver scaling_governor
> cpufreq-dt
>
> That latest kernel I referred to is .76, not 69, sorry for the
> confusion.
>
> On Wed, 2024-03-20 at 11:48 +0100, Alex wrote:
> > Hi,
> >
> > Is there really no one who could and would just do that one test
> > for
> > me? I reproduced the prob
That latest kernel I referred to is .67, not 69, sorry for the
confusion.
On Wed, 2024-03-20 at 11:48 +0100, Alex wrote:
> Hi,
>
> Is there really no one who could and would just do that one test for
> me? I reproduced the problem with the actual 6.1.69 kernel from the
> De
query
by Raspberry userland (vcgencmd measure_clock arm), which is in my case
always identical to cpuinfo_cur_freq.
alex@aws:~:(6)> cd /sys/devices/system/cpu/cpufreq/policy0/
alex@aws:cpu/cpufreq/policy0:(4)> cat scaling_driver scaling_governor
cpufreq-dt
schedutil
alex@aws:cpu/cpufreq/p
Supposedly the i2c bus you found is one of the HDMI lines, they use i2c
for EDID and other information. My real time clock is on /dev/i2c-3.
alex@aws:~:(13)> i2cdetect -y 3
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
defined as per firmware or
config.txt. Shutting down the X server does not revert this.
For me this seems to be a gpu related issue ... ?
Regards,
Alex
On Wed, 2024-03-13 at 14:27 +0100, Alex wrote:
> >
>
> There was a typo in my last statement...
>
> > oldstable
>
There was a typo in my last statement...
> oldstable 5.10 --> governor *is* working
> oldstable 6.1 backport --> governor not working
> oldstable 6.1 RT backport --> governor is working
> stable 6.1 --> governor is working
On Wed, 2024-03-13 at 13:41 +0100, Alex w
orking
oldstable 6.1 RT backport --> governor working
stable 6.1 --> governor working
So after all, this does not seem to be a Devuan issue. I'd be glad to
help tracking down this issue.
Alex
On Tue, 2024-03-12 at 22:26 +, Andrew M.A. Cater wrote:
> On Tue, Mar 12, 2024 at 11:14:10
Sorry for mixing things up. Chimaera is oldstable and thus corresponds
to Bullseye...
On Tue, 2024-03-12 at 11:14 +0100, Alex wrote:
> Hi there,
>
> I am running a Raspberry Pi 4 with an oldstable release for a few
> years
> now. In fact, it is Devuan Chimaera, correspondi
, the kernel scheduler is not.
The CPU speed stays fixed at the maximum of 1800MHz, spouriously, every
nth boot, it springs to other values, but not really following the
governor. I will provide some data here. 1st try, my custom compiled
kernel, 2nd try, the 6.1.69 from the repository.
alex@aws
Milan Kupcevic wrote on 6/10/21 6:10 AM:
> On 6/10/21 12:53 AM, John Paul Adrian Glaubitz wrote:
>> On 6/10/21 2:08 AM, Paul Wise wrote:
The report and its recommendations may provide a means
to pierce the veil of closed platforms, like closed-sourced firmware.
>>>
>>> It seems unlikel
On Sun, May 8, 2011 at 6:54 PM, Peter Littmann
wrote:
> At least the Ram of only "128MB SDRAM" seams to be a little bit small,
> isnt it?
I can't comment on the platform itself, but 128MB is plenty. You will
need swap available for some apps (probably aptitude), but a basic
installation won't us
On Wed, Nov 24, 2010 at 10:19 PM, Luke Kenneth Casson Leighton
wrote:
> On Thu, Nov 25, 2010 at 12:48 AM, Wookey wrote:
>> +++ Luke Kenneth Casson Leighton [2010-11-24 23:17 +]:
>>> presently definitely down - help!
>>
>> Yes, as has been explained on the embedded-debian list we've had a
>> t
r some older version?
alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ight?) all to no avail.
What would the next step be?
alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> As I see it at the moment, debian-installer in Etch (the next release
> of Debian) will support Footbridge (Netwinder and CATS) and ixp4xx
> (NSLU2 and Loft), and supply kernels for a few other platforms (riscpc
> and s3c2410 at the moment). If other targets should be supported,
> please give a
ard flash and boots.
>From then on, d-i can partition and install to the USB drive
in the usual way and the only magic is remembering to copy
the new initrd from /boot in the rootfs into the onboard flash.
Alex.
PS. I gather that, in the medium term, the hardware vendor is hoping
to change the
, if the production system is known to have to use ARM,
that project needs to migrate away from Debian at the design stage.
Hope that helps,
Alex.
http://lists.debian.org/debian-arm/2005/10/msg00019.html
http://wiki.debian.org/armEtchReleaseRecertification
http://spohr.debian.org/~ajt/etch_arch_qualify.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
velopers.
When running as a buildd cluster or for similar Debian purposes,
it is advantageous to host the root filesystem over NFS on a
separate fileserver, just like you'd expect on many other clusters.
Since an NFSROOT doesn't need the USB, 2.6 may already be usable.
I'll look into it
The University of California at San Diego (UCSD) Extension program
for Embedded Computer Engineering (ECE) held a meeting on Thursday.
It turns out that there is considerable interest among the potential
student community (and their employers, who pay for the courses)
in having a course that teache
nd.c so I rewrote it. I've
attached my version to this message.
--
---- Alex Holden - http://www.linuxhacker.org
If it doesn't work, you're not hitting it with a big enough hammer
/*
* Jamie Guinan, December 1998
* Tidied up somewhat by Alex Holden, January 2001.
ss to
the slow RAM as a kind of RAM disk, then use it as a swap partition. ISTR
there was a patch floating around years ago for those crappy Pentium
motherboards (like mine) which only cache the first 64MB of RAM- it let
you use the lower 64MB in preference to the high memory.
--
--- Al
23 matches
Mail list logo
