>On 19 Feb 2024 22:44 +0100, from borde...@tutanota.com (Borden):
>>> Would you be willing to post your /boot/grub/grub.cfg for a setup
>>> where you get the blank screen GRUB?
>>
>> Yeah, I probably should have opened with that. Sorry:
>>
>> ```
&
> On 18 Feb 2024 21:28 +0100, from borde...@tutanota.com (Borden):
> > what the default is when neither of those are set (which doesn't
> > work). Is this another "undocumented feature" of GRUB?
>
> Would you be willing to post your /boot/grub/grub.cfg fo
> Or perhaps you have all colors set to blank.
> Try add something like
> GRUB_COLOR_NORMAL="light-blue/black"
> GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
Unfortunately, that didn't work. Still a blank screen. I'm curious that if
GRUB_TERMINAL=gfxterm works and
GRUB_TERMINAL=console works, what the
Thank you for the tip!
So `GRUB_TERMINAL=gfxterm` works, `GRUB_TERMINAL=console` works, but whatever
the default is supposed to be does not. Does this imply that "the platform's
native terminal output" is broken?
For a couple weeks now, I can't use graphical terminal in my GRUB
configuration. Setting `GRUB_TERMINAL=console` works fine. With that line
commented out, (thus using default settings), I get a blank screen on boot, 5
second timeout, then normal boot.
Curiously, keyboard commands work normally.
Good to see that the issue was just mis-installation, as I recently upgraded
from a Samsung 2TB EVO to a Crucial 2 TB drive without issue (well, I had
PLENTY of issues with Samsung's "customer service" and Newegg's "return
policy").
Resolved never to buy Samsung products again, as their "warran
> In fact, annoying volunteers tends to reduce their voluntarism...
That's fair. But people age and, if they're any good at what they do, have less
time to volunteer as they get busier and promote through their career.
So how do you encourage new volunteers to join and replace veterans? How do y
>>
>> You really should consider stopping to reply and leave things as they
>> are.
>
>I agree, it's time to stop this thread, I am satisfied with things how they
>are.
And nobody's learnt anything. The overwhelming consensus is that the class
system works and that anyone who thinks otherwise is
> We must live in different worlds, then.
Unless you're writing from the multiverse (in which case there are many people
who _really_ want to meet you), we live in very much the same world. Empathy is
the ability to step outside your own experience to see the world from someone
else's perspect
I sympathise with your frustrations.
The open source "community" - especially Debian - is not known for its
civility. There have been numerous articles (and backlashes) identifying the
rampant misogyny, racism, arrogance, murder and general rudeness amongst its
members and leaders. If you're ex
> It's only offensive to the people who are offended. Theoretically all
> words are offensive since any word can be offensive to anyone just because
> they deem it so. Censoring (i.e. changing the language) of everything to
> appease everyone 1) isn't possible, 2) is foolish at best, 3) is a
> wa
> A new portable hard drive and a new flash drive were, in turn, plugged into
> the USB 3 port, but fdisk -l, lsblk and lsusb outputs suggest that
> neither of these devices are recognised by the kernel when in that port.
I have a similar problem with my laptop with a USB 3.0 port. It works
in "le
> Please tell us the output of:
> dpkg -l | grep -i grub
Sorry for missing this. Please see below:
# dpkg -l | grep -i grub
ii grub-common 2.04-8 amd64
ii grub-efi-amd64-bin 2.04-8 amd64
ii grub-efi-amd64-signed 1+2.04+8 amd64
rc grub-imageboot 0.6 all
ii grub2-common 2.04-8 amd64
> The package
>> It would help if you said which version of Debian you're using.
>
>And which boot parameter.
Debian Bullseye. I want to add pci=nomsi to the boot parameters to
troubleshoot a USB 3 issue.
https://wiki.debian.org/Grub#Configuring_GRUB_v2 says that
/etc/default/grub ought to exist, if it doesn't
Not a direct answer to your question, but the etiquette on the lists
is to use plain text only messages wrapped at 80 characters to
maximise compatibility with clients - I assume because the list
forwards the messages using text-only headers.
I get digests. Even though I'm reading on modern e-mail
> So far the OP hasn't provided any information on what network management
> tool is in use, we can only guess.
Fair comment. I just assumed that everybody uses Network Manager these
days. I travel with my laptop to different WiFi networks, and I never
did learn any other form of WiFi setup. For t
I know this is an amateur question, but I want to make sure that I do
it correctly the first time. I want to add a boot parameter, so what
file do I edit/create to do so?
My computer doesn't have a /etc/default/grub file. I can't tell you
why. I didn't intentionally delete it. I have a bunch of co
> Use ps x to see how many copies of wpa_supplicant are running. If you have
> multiple copies started from the command line the wifi won't stay connected.
> I had the same problem.
Thank you for the suggestion. I checked when it started dropping and, not only
was there one instance of wpa_supplic
I'm looking for help on how to interpret journalctl to understand why
my wireless keeps disconnecting. I have two wireless adapters on my
laptop: an internal Intel card and a USB dongle. The former has driver
issues, so I generally rely on the latter.
I know that the hardware is fine because my ph
> I feel like we are missing a trick here. Even with a relatively slow I/O
> device (I was faintly amused to see SSD in the list of relatively slow
> devices, if SSD is slow what is fast?) it should eventually catch up
> UNLESS something is generating an insane amount of I/O over a sustained
> peri
> In my case. "timidity" was causing my problem. Within X, I did a "sudo kill
> timidity", and immediately my Volume control on the pane of KDE's Plasma
> desktop changed, and the volume control slider produced test clicks. I
> tried purging timidity, but it seems to want to take half of KDE with i
> I.e. 12309 bug is back. It's obscure and presumably fixed (at least four
> times fixed) bug that happens with relatively slow filesystem (be it
> SSD/HDD/NFS or whatever) and a large amount of free RAM. I first
> encountered the thing back in 2.6.18 days, where it was presumably
> implemented (as
> Date: Thu, 7 Jun 2018 01:32:27 +0300
> The first questions regarding Out Of Memory situation is, how much memory do
> you have, and what Desktop Environment and active programs (other than the
> browser) have you been using when OOM-killer got triggered?
I use KDE. That may be part of the proble
On 6 June 2018 at 15:26, wrote:
> Hi.
>
> On Tue, Jun 05, 2018 at 09:25:25PM -0400, Borden Rhodes wrote:
>> During the freeze, hard drive activity goes through the roof. Yes, my
>> hard drive is fine and works normally when doing anything else. I also
>> d
This is a follow-up to a question I posted here on 27 May for which I
got no response. In it, I complained that my "new" laptop running
Buster completely freezes when browsing certain Javascript-heavy
websites (like Google Docs, Facebook and YouTube) on Firefox 52.
Since that e-mail, I installed C
Since getting my new laptop and clean-installing Buster, Firefox-ESR
keeps locking my computer up so much that I usually have to hard
restart because the system is totally unresponsive. When I'm lucky, I
can drop into a TTY, kill Firefox and regain control.
According to iotop, I think the offendin
> Date: Thu, 2 Nov 2017 05:11:34 -0400
> From: Gene Heskett
>
>> What kernel or other settings can I set to let me keep control of my
>> computer during a runaway process? Basically, how do I tell Linux to
>> keep just enough resources free so I can drop into a shell terminal
>> and figure out wha
What kernel or other settings can I set to let me keep control of my
computer during a runaway process? Basically, how do I tell Linux to
keep just enough resources free so I can drop into a shell terminal
and figure out what's going wrong?
In context, this evening my computer hung for 30 minutes.
>> - Hello,
>> Is this the Chevrolet users' support group?
>> I just bought this new Chevy and I am having all kinds of problems I've
>> never had before with a Chevy or any other car for that matter.
>> - What problems are you having, because all other owners are happy.
>> - Pretty much anythi
>> > Do you find checking for possible rootkits is useless, or you are just
>> > not happy how rkhunter performs that function?
>>
>> A well-documented case of rkhunter discovering a rootkit in the last
>> ten years (the 1000s of false positives do not count) would go a long
>> way to establishing
Thank you for your response, Ben,
> What response did you get to the bug reports you filed from the problems you
> encountered?
One example includes an X regression that caused it to wait upwards of
8 minutes searching for my laptop's touchscreen. The bug was caused by
a typo where, instead of w
Hey Tony,
I had lots of problems with Stretch when it was in testing. A lot of
packages (KDE, X drivers, and the kernel come immediately to mind)
have manageable but irritating upstream regressions that didn't get
patched or backported in time for the release.
I was very surprised when they relea
Thank you again, Pascal, for your helpful reply.
> Le 20/08/2017 à 01:08, Borden Rhodes a écrit :
>
> You forgot the -k option before the version.
> Otherwise, you can directly probe the file :
Right you are. Here is the corrected output:
$ modinfo -k 4.12.0-1-amd64 xts
filename
Thank you for your response, Pascal,
Thank you, also, for your very clear instructions. It's nice not
having to guess the rest of the command I need to use. My kernel
hacking abilities are elementary, at best.
Here is the output from my system:
$ modinfo 4.12.0-1-amd64 xts
modinfo: ERROR: Module
I'm on the Buster repo. For all kernels released after 4.9, I can't
boot into my system, which has all encrypted partitions except for
/boot. I think tihs is my problem, as I get the same symptoms:
https://gitlab.com/cryptsetup/cryptsetup/issues/319
I decided to wait until the 4.12 kernel came out
Thank you for the suggestion, Felix, although I'm not quite ready to
levy my scorn and blame on KDE (yet). Since my last post, it turns out
that the full KDE desktop DOES start, but it takes an excruciating
amount of time (more on that in a second). systemd, systemd-analyze
and journald report noth
The Intel package driver was already purged from my system. I tried
reinstalling it to no use. Purged xwayland, too (which I don't use but
nevertheless installed). No help. I've also checked dmesg, messages,
Xorg.0.log & syslog and syslog and found nothing out of the ordinary
in those logs. It just
Thank you, Hans. My laptop has an Intel chipset, so nvidia doesn't
apply. I think the recommended driver for my chipset is the
framebuffer or vesa device, but I may try reinstalling the Intel
driver to see if that fixes it.
On 13 December 2016 at 12:37, Hans wrote:
> Note, that SDDM does not work
Thank you for the references, Felix.
Unfortunately, nothing you sent is applicable because SDDM doesn't
even start in the first place. Computer goes unresponsive when it
tries to start X and then I have to force shut down. I've been able to
start - just - by booting into multi-user.target and mask
I'd advise against running testing if you want stability. I get a lot
of breakages on my Stretch laptop with routine upgrades. When I look
into them, a number of breakages seem due to transitions to newer
library platforms where all the kinks haven't been worked out yet.
Other packages simply have
> [rsyslog maintainer speaking here]
>
>> One of the culprits in my full /var partition was a 3 gig syslog file
>> which has only been getting bigger since January despite running
>> logrotate -f. I try to run it this time but I'm told that it can't
>
> I'd be interested to find out, why logrotatio
> It sounds like btrfs specific behaviour. It would be interesting to know
> what kernel version and btrfs version you were using, if only to confirm
> my suspicion that even the versions in Debian are not suitable for use in
> production.
>
> I'm going to guess that it was a series of 'btrfs balan
> [rsyslog maintainer speaking here]
>
> Am 15.11.2016 um 06:00 schrieb Borden Rhodes:
>> One of the culprits in my full /var partition was a 3 gig syslog file
>> which has only been getting bigger since January despite running
>> logrotate -f. I try to run it this time
I tried booting up into Debian and got all sorts of systemd breakages
apparently because my /var partition was full. That's fair, but the
pain started when Debian frustrated any attempt to free up space. I'm
wondering if this is a 'feature' that needs removing or if there might
be a bug in the unde
After 3 months of going Little Red Hen on this, I think I figured it
out. My system had live-config & live-boot (with their dependencies,
live-boot-initramfs-tools, user-setup, live-tools and
live-config-systemd) installed. An aptitude purge command on these
packages got my system booting normally
I'm still stuck with this problem after wasting another 5 hours on it
last night. I'm still getting the time out error message but, without
any useful debugging information, don't know where to start
troubleshooting. Further, it appears the systemd maintainers have
given up responding to bug report
-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> On Friday 29 July 2016 00:51:42 Borden Rhodes wrote:
>> Thank you, Siard. I'm grateful for help no matter who gives it! Here's
>> the PNG of the offending toolbar in LibreOffice:
>> https://s31.postimg.org
debian.org
> Subject: Re: LibreOffice toolbars & menus are rendering badly
> Message-ID: <20160728095810.fc6d297c.shiems...@kpnplanet.nl>
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
>
> Borden Rhodes wrote:
>> Lisi: is there some other
in;
> charset="utf-8"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
>
> On Wednesday 27 July 2016 22:19:22 Borden Rhodes wrote:
>> If you can't load
>> the photo (because it's converted into plain text), the problem is
>> that
), minor code: 0
QXcbConnection: XCB error: 3 (BadWindow), sequence: 58762, resource
id: 125829121, major code: 18 (ChangeProperty), minor code: 0
no winId: probably startup task
Creating the cache for:
"/home/borden/business/clients/AikidoTendokai/Report.odt"
Already in database? true
F
I can `systemctl show ` these
devices but I can't disable them. Can someone tell me what they're
there for, what created them and how I can, for debugging purposes,
disable them from being called?
On 22 July 2016 at 00:09, Borden Rhodes wrote:
> During the 90 second wait before my boot times o
6 at 02:54, Borden Rhodes wrote:
> Thank you for your message, Michael, and please forgive the delay in
> responding.
>
> I tried booting with the 4.5 kernel after 4.6 failed to boot. It
> seems, by then, that the damage had been done as I got identical
> symptoms on both boot
Thank you for your message, Michael, and please forgive the delay in responding.
I tried booting with the 4.5 kernel after 4.6 failed to boot. It
seems, by then, that the damage had been done as I got identical
symptoms on both boots. I agree with you that the cryptsetup/LVM is to
blame (although
t
unit and display all of the dependant units in a nice, pretty format
to save me from having to do it myself (and making lots of mistakes in
the process)?
With thanks,
On 16 June 2016 at 23:51, Mark Fletcher wrote:
>
> On Fri, 17 Jun 2016 at 03:12, Borden Rhodes wrote:
>>
>> Than
any better ideas, I think I'm going to
redirect this conversation to bug 758808.
> Date: Thu, 16 Jun 2016 13:56:48 -0400
> From: Borden Rhodes
> To: debian-user@lists.debian.org
> Subject: Re: boot times out after dist-upgrade on Stretch
> Message-ID:
>
> Content-Typ
?
> Date: Wed, 15 Jun 2016 19:35:34 +0200
> From: Sven Joachim
> To: debian-user@lists.debian.org
> Subject: Re: boot times out after dist-upgrade on Stretch
> Message-ID: <8760tapd7d@turtle.gmx.de>
> Content-Type: text/plain
>
> On 2016-06-15 07:58 +, Borden
Good morning,
I ran apt dist-upgrade on Stretch (with a few Sid packages) which made
the following changes:
Start-Date: 2016-06-14 19:42:39
Commandline: apt-get dist-upgrade
Requested-By: me (1000)
Install: libdw1:amd64 (0.163-5.1, automatic),
linux-image-4.6.0-1-amd64:amd64 (4.6.1-1, automatic)
tart Linux'* design goal.
Borden
*Yes, I know that there are exceptions.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201105171521.26126.j...@bordenrhodes.com
I'm not sure this is a bug or a problem with me, so I'm posting it here so I
don't clutter up bug triaging with something which may not be an issue.
Here's my problem.
In spite of my earlier post ('Why does Linux crash?') I can every so often
CTRL+ALT+F# my way into a shell to recover a broken
Thank you, Boyd, that was just the sort of answer I was looking for. I tried
using Ctrl+Alt+F1 to drop into a terminal but, again, it wasn't responsive.
I'll commit your suggestions to memory for the next time the system locks up.
You touched on the crux of my complaint: sure, I expect the odd
Thank you for your reply, Axel; perfect answer. Now that I know that
these features of Linux exist I can go hunt them down and figure out
how to use them and stop this from happening again (like it did after
I sent my original e-mail).
With thanks again,
--
To UNSUBSCRIBE, email to debian-user
Thank you for your reply and your consolation that other people are
equally miffed with Eclipse. My question, though, is about Linux
control systems. Is one of the kernel's design goals to manage system
resources to prevent a buggy program from crippling the system and
forcing a hard restart? If
up so they can plug up the hole? I hate to think what
a malicious program could do to a web server if Eclipse can do this to
my computer.
With thanks,
Borden Rhodes
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
Well, I owe everyone a big apology. After searching unsuccessfully
with Nautilus, I took Arthur's suggestion and whipped out a terminal
and figured out how to use find's options. It turns out that the
folders had been dropped into one of the dot-folders (where, I guess,
Nautilus doesn't poke abou
ragging process destroyed all trace of the
files.
Luckily, I had those folders on a backup and firearms are regulated in
Canada. However, I'm assuming that destroying folders isn't part of
the design of Linux so I'd like to file a bug but I don't know what
evidence to collect. Can
Once again, Sven, I owe you my sanity. I've read that Debian was still
looking into framebuffer issues with Intel, whether to keep UMS or
migrate to KMS. Is that debate related to the DRI/shadow issue?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubsc
es" #
#Option "PageFlip" # []
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "82852/855GM Integrated Graphics Device"
BusID &
Can I get a second on Teddy's opinion? I tend to believe that I just
share the Linux experience, and if I can get something useful done
whilst the computer is willing, so much the better. Is this the truth
about open source software? Maybe I am in the wrong distribution and
I'm wasting the list'
goose chases. Surely there must be a better way to
troubleshoot FLOSS!
Finally, I don't care how software reaches this utopian state. It can
be top-down, bottom-up, sideways, revolutionary, explosive or any which
organisation or movement or argument or death threat which lets me
participate in the c
ing.
Again, I appreciate the feedback. I'm a lot less frustrated that we're
talking about it. I have hope that some good idea or initiative will
come of this.
Borden
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
Thank you for the response. Indeed, you are correct in that my problem
isn't specific to Linux kernel troubleshooting (although I could
dedicate a website to things that don't work there) but with the
software that runs on Debian in general.
To clarify, the problem I have is when the computer fre
(Sorry for the late reply to a thread started way back)
I'm pleased for all of the feedback and that I'm not the only person
who's frustrated. I tried proposing to debian-policy that it be
mandatory that all logs have timestamps
http://lists.debian.org/debian-policy/2010/02/msg00035.html but my
s
o way to get
it back to full brightness without restarting the computer. I've
fiddled with the power settings to no avail and tried every other form
of Linux trickery I know.
If I'm going to file a bug, is it the RandR library's fault or the Intel
driver's fault?
With thanks,
Bo
als with dumps and crashes and so
on?
Maybe I just haven't found the right manual yet that has all of these answers
so I'd appreciate any direction.
With regards,
Borden Rhodes
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201008150200.52677.j...@bordenrhodes.com
uld this, therefore, be reported as a wishlist bug
against Debian's Xorg?
Borden
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
vestigation.
Since, according to Google, I'm the first to ask this question, I'm guessing
I'm misunderstanding the purpose of Xorg.log and that time stamps are
counterproductive. Could someone please explain why this is the way that it
is?
With thanks,
Borden
--
To UNSUBS
76 matches
Mail list logo
