Allegedly, on or about 25 July 2016, Rick Stevens sent:
> If the Bluetooth and 802.11b/g antennas are more than 3 meters apart,
> however, interface in minimal.
Bit hard to do that when the hardware is buried in a laptop, for
instance. I wonder if anyone's got information on manual configuration
Allegedly, on or about 25 July 2016, Ed Greshko sent:
> Actually I would find it very odd that "digital" devices would run
> slower as a battery weakens. I mean even my battery operated clocks
> at home work perfectly fine without losing time. When the battery
> "dies" they just cease to function
On 07/25/2016 07:00 PM, Michael D. Setzer II wrote:
process on two other machines twice, and they did not upgrade. Can't see
the systems during the reboot process, and didn't see anything in the /var/log
files to show any errors.
Run "dnf system-upgrade log" to see a list of upgrade attempts.
T
On Mon, Jul 25, 2016 at 11:57:24PM +0100, Patrick O'Callaghan wrote:
> On Tue, 2016-07-26 at 05:55 +0800, Ed Greshko wrote:
> >
> > On 07/26/16 02:49, Roger Wells wrote:
> > >
> > > Something changed (although not fatally):
> > > I use Bluetooth speakers quite often.
> > > Back in F22 or so after
On Mon, Jul 25, 2016 at 07:46:04AM -0400, Bob Goodwin wrote:
> On 07/24/16 18:42, Ed Greshko wrote:
> > > >It does what I asked!
> > You seem to have /dev/sdd1 already mounted on /mnt/temp.
> >
> > And you've manually mounted /dev/sde1 on /mnt/temp as well as it being
> > automounted on
> > /run/
Not sure what the issue is. Am currently 7 timezones away from my
classroom machines, but wanted to update a few before I get back. Had to
run the process 3 times on first machine before it finally did the upgrade.
fedup --network 24 --allowerasing
Process seems to go thru just fine, and then do
On 07/26/16 06:57, Patrick O'Callaghan wrote:
> On Tue, 2016-07-26 at 05:55 +0800, Ed Greshko wrote:
>> On 07/26/16 02:49, Roger Wells wrote:
>>> Something changed (although not fatally):
>>> I use Bluetooth speakers quite often.
>>> Back in F22 or so after pairing the device merely turning it on
On Tue, 2016-07-26 at 05:55 +0800, Ed Greshko wrote:
>
> On 07/26/16 02:49, Roger Wells wrote:
> >
> > Something changed (although not fatally):
> > I use Bluetooth speakers quite often.
> > Back in F22 or so after pairing the device merely turning it on caused
> > Fedora to connect to it.
> > Se
On 07/26/16 02:49, Roger Wells wrote:
> Something changed (although not fatally):
> I use Bluetooth speakers quite often.
> Back in F22 or so after pairing the device merely turning it on caused
> Fedora to connect to it.
> Several months ago, now on F23, (not sure when this problem appeared)
>
On 07/25/2016 09:38 AM, Ed Greshko wrote:
> On 07/25/16 22:30, Tim wrote:
>> Tim:
I'm sceptical, too (about that belief). I'm inclined to believe
that story has been conjured up by someone to explain things, and
everyone else has simply gone along with it.
>> Joe Zeff:
>>> Be as s
Something changed (although not fatally):
I use Bluetooth speakers quite often.
Back in F22 or so after pairing the device merely turning it on caused
Fedora to connect to it.
Several months ago, now on F23, (not sure when this problem appeared)
that changed and after turning the speaker on, I ha
On 07/23/2016 09:00 AM, Chris Murphy wrote:
> On Fri, Jul 22, 2016 at 2:37 PM, Tod Merley wrote:
>> .. so what mods are loaded to handle wifi and bluetooth ...
>
> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4331
> 802.11a/b/g/n [14e4:4331] (rev 02)
> Subsystem: Broadcom Corpor
On 07/25/2016 07:30 AM, Tim wrote:
I'd like to see some proof that it's actually designed to run slow when
the battery goes flat, as opposed that merely being what happens.
All I can tell you (not being a hardware geek) is that I learned about
it from the guy who's done all my hardware work si
On Mon, 2016-07-25 at 08:22 -0700, Jonathan Ryshpan wrote:
> I received the following message about 10 days ago, but still haven't seen it
> posted or received the moderators rejection notice. Since there seems to be
> no
> way to reach the moderator directly, I'm reduced to posting this to the l
I received the following message about 10 days ago, but still haven't seen it
posted or received the moderators rejection notice. Since there seems to be no
way to reach the moderator directly, I'm reduced to posting this to the list.
The original posting had
Subject: Dragon/Kplayer troub
On 07/25/16 10:52, Ed Greshko wrote:
And Thank You for your understanding that Jack Daniels isn't always compatible
with sound
advice.
+
Hick,
--
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10 FEDORA-24/64bit LINUX XFCE POP3
--
users mailing list
users@lists.fedoraproje
On 07/25/16 22:41, Bob Goodwin wrote:
> On 07/25/16 10:12, Ed Greshko wrote:
>> On 07/25/16 22:07, Bob Goodwin wrote:
>>> ># tune2fs -L st1000
>> Ooopppsss My bad Having a night cap and forgot the most important
>> part...
>>
>> tune2fs -L st1000 /dev/sdd1
>>
>> How else will it know wha
Well - i hate to butt in here but i can most definitely say that my wristwatch
for example most definitely indicates a dying battery by only moving the second
hand every 2 seconds instead of 1 second
- BUT it moves 2 increments each 2 seconds - but i have no idea if that has any
relevance!
> On
[snip]
I shall certainly check the battery but I don't see how the battery could
caise so many "bad" log entries spanning several hours in one minute.
Look again at the snippet I included.
Cheers,
Stephen
[snip]
Good, this is just methodology starting with the battery. Possible to
expand your s
On 07/25/16 10:12, Ed Greshko wrote:
On 07/25/16 22:07, Bob Goodwin wrote:
># tune2fs -L st1000
Ooopppsss My bad Having a night cap and forgot the most important part...
tune2fs -L st1000 /dev/sdd1
How else will it know what filesystem we're talking about? :-) :-)
--
+
And that sh
On 07/25/16 22:30, Tim wrote:
> Tim:
>>> I'm sceptical, too (about that belief). I'm inclined to believe that
>>> story has been conjured up by someone to explain things, and everyone
>>> else has simply gone along with it.
> Joe Zeff:
>> Be as skeptical as you want, but it's been true ever sinc
Allegedly, on or about 25 July 2016, Stephen Davies sent:
> I shall certainly check the battery but I don't see how the battery
> could caise so many "bad" log entries spanning several hours in one
> minute.
Is the log generated in real time, as it happens?
Or are you getting slew of things dumped
Tim:
>> I'm sceptical, too (about that belief). I'm inclined to believe that
>> story has been conjured up by someone to explain things, and everyone
>> else has simply gone along with it.
Joe Zeff:
> Be as skeptical as you want, but it's been true ever since I got my
> first PC in the late '80s
On 07/25/16 22:07, Bob Goodwin wrote:
> # tune2fs -L st1000
Ooopppsss My bad Having a night cap and forgot the most important part...
tune2fs -L st1000 /dev/sdd1
How else will it know what filesystem we're talking about? :-) :-)
--
You're Welcome Zachary Quinto
--
users mailing lis
On 07/25/16 09:43, Ed Greshko wrote:
On 07/25/16 21:40, Bob Goodwin wrote:
># tune2fs -l /dev/sdd1
>tune2fs 1.42.13 (17-May-2015)
>Filesystem volume name:
OK
Do
tune2fs -L st1000
and then
tune2fs -l
to see if changes
--
+
That's what I thought after reading through the man p
On 07/25/16 21:40, Bob Goodwin wrote:
> # tune2fs -l /dev/sdd1
> tune2fs 1.42.13 (17-May-2015)
> Filesystem volume name:
OK
Do
tune2fs -L st1000
and then
tune2fs -l
to see if changes
--
You're Welcome Zachary Quinto
--
users mailing list
users@lists.fedoraproject.org
To unsub
On 07/25/16 09:35, Ed Greshko wrote:
What is the output of "tune2fs -l /dev/sdd1"
# tune2fs -l /dev/sdd1
tune2fs 1.42.13 (17-May-2015)
Filesystem volume name:
Last mounted on: /mnt/temp
Filesystem UUID: a3cd7e7f-254d-410a-b120-e02524f75a29
Filesystem magic number: 0xEF53
Fi
On 07/25/16 19:46, Bob Goodwin wrote:
> On 07/24/16 18:42, Ed Greshko wrote:
>>> >It does what I asked!
>> You seem to have /dev/sdd1 already mounted on /mnt/temp.
>>
>> And you've manually mounted /dev/sde1 on /mnt/temp as well as it being
>> automounted on
>> /run/media/bobg.
>>
>> Not sure th
On 07/25/16 08:01, Joe Zeff wrote:
On 07/25/2016 04:46 AM, Bob Goodwin wrote:
So the command 'e2label /dev/sdd1 st1000' makes it possible to add
another device, it doesn't change the name. What did I miss in setting
up the external drive initially?
Two questions: first, have you rebooted, or
On 07/25/2016 04:46 AM, Bob Goodwin wrote:
So the command 'e2label /dev/sdd1 st1000' makes it possible to add
another device, it doesn't change the name. What did I miss in setting
up the external drive initially?
Two questions: first, have you rebooted, or otherwise
unmounted/remounted that
On 07/24/16 18:42, Ed Greshko wrote:
>It does what I asked!
You seem to have /dev/sdd1 already mounted on /mnt/temp.
And you've manually mounted /dev/sde1 on /mnt/temp as well as it being
automounted on
/run/media/bobg.
Not sure that is what you wanted to accomplish.
+
After boot this morni
hello Tim and Joe.
On 07/25/2016 01:03 AM, Joe Zeff wrote:
> On 07/24/2016 08:40 PM, Tim wrote:
>> I'm sceptical, too (about that belief). I'm inclined to believe that
>> story has been conjured up by someone to explain things, and everyone
>> else has simply gone along with it.
>
> Be as skepti
32 matches
Mail list logo
