Re: Help with TL-WN823N on Fedora

One factor that makes dnf difficult when poor network communication causes downloads to time out is whatever partial file data has been read is discarded. Dnf starts a new download for the failed file from a different server. If that new download times out, whatever has been received is

Re: problems upgrading from Fedora 33 to Fedora 34

Qiyu Yan wrote on Sat, 01 May 2021 14:40:34 +0800: It not the last installed becomes the dafault, but the one with highest version nummber. And unluckily, there is a kernel downgrade with the upgrade from f33 to f34. That explains it. The recent F34 update to the 5.11.16-300 kernel

Re: problems upgrading from Fedora 33 to Fedora 34

If no F34 kernal is installed, something went awry during the offline upgrade. Perhaps try the upgrade again, to learn whether this is a consistent failure? One of my systems has a /boot filesystem that is too small. Before I can install a new kernel, I have to manually remove an older kernal

Re: problems upgrading from Fedora 33 to Fedora 34

After upgrade from F33 to F34, the newly-installed kernel was not the default to boot. I had to explicitly select the F34 kernel in lieu of an older F33 kernel at boot time. This was a surprise for me (I expected the last kernal installed to become the default), but it may not be germane in your

Re: pipewire and high-res audio

Lukas Ruzicka wrote on Tue, 6 Apr 2021 09:44:22 +0200: >what happened when you tried to reload the services (or restarting >computer)? Ah, the Power-On-Reset panacea. Cures many ills, and cured this one nicely. Both prior to pipewire (F33) and with pipewire (F34), it is possible to obtain 192

pipewire and high-res audio

Questions: 1. How can pipewire be configured for 192000 Hz audio output? 2. Are these problems with abrt at this time of Final Freeze a reason for concern, or normal for the release process? 3. Does the message "Can't find packages for 33 debuginfo files"? below signify some

Re: [Proposal] The dual head set-up criterion

Should multiple displays be a release-blocking criterion? I can imagine a desire to ship a new release on-schedule because of significant, content that works fine, but with multiple display support deferred for an update because upstream problems are likely to take a while to fix. I am

Re: wi-fi question

> Upgrading: grub2-efi-x64-1:2.06~rc1-3.fc35.x86_64 > 159/498 > warning: /boot/grub2/grubenv created as > /boot/grub2/grubenv.rpmnew > > Upgrading: grub2-efi-x64-1:2.06~rc1-3.fc35.x86_64

Re: Is the Fedora 35 repo having troubles?

Adam Williamson wrote on Wed, 24 Mar 2021 13:01:58 -0700: >You may have a bad systemd build with name resolution issues. Try >creating a file /etc/systemd/resolved.conf.d/nocache.conf with this >content: > >[Resolve] >Cache=no > >and restarting systemd-resolved.service, it may help. This worked

Re: Is the Fedora 35 repo having troubles?

Also happens with F34: Errors during downloading metadata for repository 'fedora-modular': - Curl error (7): Couldn't connect to server for https://mirrors.fedoraproject.org/metalink?repo=fedora-modular-34=x86_64 [] Error: Failed to download metadata for repo 'fedora-modular': Cannot prepare

Re: newbie question - Fedora 34

>In my opinion, a good review would be to install on hardware and show >actual real-world work being done with Fedora 34, such as a drawing in >FreeCAD, and how the system differs from Manjaro Gnome 40, Gnome OS, >Ubuntu 20.10, etc. Perhaps for the actual release, but this sounds premature for a

Re: F34 problem reporting problem

I filed: https://bugzilla.redhat.com/show_bug.cgi?id=1940944 for gnome-abrt to document the cpio problem during extraction of debuginfo from a downloaded file. ___ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to

Re: F34 problem reporting problem

Tried again after a few hours. Still trouble with the retrace server, but local analysis was able to say I experienced the already-reported https://bugzilla.redhat.com/show_bug.cgi?id=1937073 Temporary unavailability of the server sounds plausible for the original problem. There are

F34 problem reporting problem

Up-to-date F34 (18Mar21) originally installed from Fedora-Workstation-Live-x86_64-34-20210316.n.0.iso tries to report error and says: --- Running report_uReport --- Failed to upload uReport to the server 'https://retrace.fedoraproject.org/faf' Error: curl_easy_perform: Couldn't connect to

Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)

The key appears to be: >possible to switch between implementations. This will also allow for an >easy rollback. Provided this works easily (it should be an explicit part of the test activity) it is reasonable to accept some instability or missing function in the PipeWire facility in order to

Re: ifdown access denied

Root is pretty much allowed to do everything. If root cannot change your network operation, something indeed appears to be awry. If you cannot figure out what, re-install Fedore will probably set things straight. If not, at least you will have found a well-defined starting point that others

Re: ifdown access denied

Try: nmcli general permissions I suspect network-scripts is the "old way" and with Network Manager you need something else to specify who may do what with respect to network connections. ___ test mailing list -- test@lists.fedoraproject.org To

Re: criterion proposal: prevent services timing out on system shutdown

>When the UPS says the battery is exhausted, must shutdown now, it's more >than just an aggravation. It should not be. Worst case should be similar to abrupt power failure. (Real case: I pull the wrong plug out of my power strip, disconnecting my server instead of the device I intended to move.)

Re: criterion proposal: prevent services timing out on system shutdown

I think failure to shut down promptly should not be a "blocker" event. Is shutdown in three minutes instead of three seconds an aggravation for the user who wants to use a new kernal or another operating system? Yes. Does unreasonable time to shut down indicate lack of quality in Fedora? Of

Killer Wi-Fi 6 AX1650i

I am happy to see the 5.6.0-0.rc0.git5.1.fc32.x86_64 kernel recently deployed to Rawhide supports the "Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW)" in my Dell XPS 13 laptop. The earlier 5.5 kernels did not initialize and use this wireless hardware.

Rawhide selinux problem

After an update of my Rawhide system yesterday, it refused to boot. A change to /etc/selinux/config to set SELINUX=permissive avoids the problem. This may be a one-off situation due to my particular sequence of updates, unless others have similar troubles. The system log for the failing boot

gsd-power fault in Rawhide

With up-to-date (23 January 2020) Fedora Rawhide on a Dell XPS-13 7390 laptop machine, after resumption from suspend, or switching from an alternate colsole back to the graphical console, I see the expected graphical login screen. After I enter the correct password, I see a dark screen (or

gimp segfault

Can anyone report success to run gimp in Rawhide? I see its splash screen, a few messages about initialization, then a segfault. Full stack trace at: http://ryniker.org/Fedora/gimp_stack_trace GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C

Dell 7390 laptop.

For the first time, Fedora will boot on my Dell laptop: Fedora-Workstation-Live-x86_64-Rawhide-20200101.n.0.iso The kernel identifies the machine thus: DMI: Dell Inc. XPS 13 7390 2-in-1/06CDVY, BIOS 1.1.3 11/10/2019 and Dell identifies it with Service Tag 8NMBZY2. CPU info: vendor_id :

Re: [sane-devel] Umask and xsane

Olaf Meeuwissen wrote on Wed, 28 Aug 2019 20:18:26 +0900: Any files created by XSane (or any SANE frontend or backend for that matter) on behalf of the user should use the user's primary group, IMNSHO, *and* honour the user's umask, no matter how odd. I agree about umask, but do not

Re: Mystery empty file

>Are either of those using EFI with secure boot? According to the bug >report, that's the trigger. I believe you are right. To my surprise, after inspection of the BIOS displays in the machine that does allow data access, I find no mention at all of secure boot capability. The machine that

Re: Mystery empty file

This seems to depend on kernel version. On one F30 system it works: [root@yoga ryniker]# uname -r 5.0.17-300.fc30.x86_64 [root@yoga ryniker]# ls -l /sys/kernel/debug/usb/devices -r--r--r--. 1 root root 0 May 30 09:59 /sys/kernel/debug/usb/devices [root@yoga ryniker]# cat

Re: Mystery empty file

I think you will find the file is not truly empty. /sys is not an actual file system, merely an interface to kernel information. There is no directory structure that records the length or other attributes of a file, as is the case for data on real media such as disks. If you read the

Re: rawhide net install image doesn't work with bios partitions

Chris Murphy wrote on Mon, 27 May 2019 22:27:16 -0600: >Dual Fedora's isn't officially supported. The installer almost always >steps on the previous Fedora's bootloader making it unbootable, in >favor of a new bootloader for the new Fedora installation. This deserves some attention. I expect

[fedora-arm] Re: Connect to hidden wifi networks at boot.

>The router of the wifi network uses DHCP to give IP to connected >devices. Configure the DHCP server to allocate a fixed IP address to the RPi (based on its MAC address, which is now constant). Then you will know what address to use with ssh. ___ arm

[fedora-arm] Re: Raspberry Ugrade to ARM Fedora 30

> Dear All, to upgrade a Raspberry 3 I executed this commands > > sudo dnf -y upgrade --refresh > sudo dnf -y install dnf-plugin-system-upgrade > sudo dnf -y system-upgrade download --releasever=30 > sudo dnf -y system-upgrade reboot > > after the reboot dnf fails. Is anyone else having

[fedora-arm] Re: possible errors in generation of some arm7hl packages.

>I don't think it's a kernel problem, possibly a dnf cache issue, I too think it is not likely to be a kernel problem. A dnf cache problem also seems unlikely - each try retrieved new copies of the package files from a mirror, then failed in the same way. After the reboot, I think the dnf cache

[fedora-arm] Re: possible errors in generation of some arm7hl packages.

I tried again, with the same results for the three packages: kexec-tools-2.0.17-2.fc28.armv7hl.rpm httpd-2.4.33-5.fc28.armv7hl.rpm brltty-5.6-10.fc28.armv7hl.rpm I rebooted the Raspberry Pi and now the upgrade works smoothly. The kernel where it did not work was:

[fedora-arm] Re: aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

> I can manually configure my Raspberry Pi model 3B-plus on-board wired > Ethernet port to operate. It is indeed only DHCP configuration that > fails, but only with the on-board device; DHCP configuration of a USB > wired Ethernet port works fine. > > Have you tried the 4.16.0-300 kernel

[fedora-arm] aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

I can manually configure my Raspberry Pi model 3B-plus on-board wired Ethernet port to operate. It is indeed only DHCP configuration that fails, but only with the on-board device; DHCP configuration of a USB wired Ethernet port works fine. Curious.

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

>Why disable SELinux? It does not provide any significant value for my Raspberry Pi computer intended for use as an embedded system or in a DACS role, where network security is important but a simple (root or user) local privilege scheme is fine. The goals of SELinux are important, but its rocky

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

I used Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz and can boot successfully on my Raspberry Pi model 3B-plus. I used: fedora-arm-image-installer --target=rpi3 --media=/dev/sdi --norootpass --resizefs --selinux=off --image=fedora/F28/Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz to

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

See Peter Robinson's post on March 23, 2018, at 10:42 PM that details how to copy the Raspberry Pi device tree file for the model 3+. ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: F28 GNOME graphical login screen not displayed on Raspberry Pi 3.

https://bugzilla.redhat.com/show_bug.cgi?id=1561184 ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] F28 GNOME graphical login screen not displayed on Raspberry Pi 3.

After booting an image such as Fedora-Workstation-armhfp-28-20180324.n.0-sda.raw.xz on a Raspberry Pi model 3, the First Boot process completes, but no graphical login screen appears. The system becomes unresponsive after a graphical pointer arrow is displayed (on top of whatever text was

[fedora-arm] Re: Raspberry Pi 3+

>I tried an image I has never used before >(Fedora-KDE-armhfp-28-20180325.n.0-sda.raw.xz). And it works. Good to hear. It seems only gdm (or maybe gnome-shell) is broken (fails to display the graphical login screen.) I just tried the LXDE image Fedora-LXDE-armhfp-28-20180325.n.0-sda.raw.xz and

[fedora-arm] Re: Raspberry Pi 3+

Did you change the default boot target from graphical.target to mult-user.target? That is what I had to do to avoid the problem with graphical login to my RPi. Of course, without a working network connection, you might feel it is not worth the bother, but my machine boots OK to a text console

[fedora-arm] Re: Raspberry Pi 3+

Thank you, Peter Robinson, your instructions worked beautifully. Perhaps this will not work with the aarch64 version used by Tomáš Frolík, but you already explained in an earlier post why there is little reason to use that on a Raspberry Pi. I used the following to install on a SD card:

[fedora-arm] Re: Fedora-Workstation-armhfp-28-20180319.n.0

>There is an accepted blocker for selinux issues on the disk images, SELINUX=permissive in my case, therefore I believe that should not be the problem here. >Workstation is a bit sluggish with 1G of RAM. Yes, but if I access the machine with ssh (and do not use the local graphical desktop) it

[fedora-arm] Re: Fedora-Workstation-armhfp-28-20180319.n.0

Using a Raspberry Pi model 3. 28-20180319 boots fine to multi-user, but fails to start the graphical desktop. A pointer is displayed (in the middle of the text screen containing the last of the boot messages), but the graphical login screen does not appear. The same Raspberry Pi with the same

[fedora-arm] Re: Fedora-Workstation-armhfp-28-20180319.n.0

>Which device? I'm presuming a RPi of some sort Sorry. Yes, a Raspberry Pi model 3 (not the new 3+). >I suspect [a monitor with a HDMI interface] Just so. OK, a little cryptic, but innocuous. Thank you. ___ arm mailing list --

[fedora-arm] Fedora-Workstation-armhfp-28-20180319.n.0

Problem or just noise? "dnf upgrade" succeeded today (260+ packages updated, seems like a lot for a one-day-old build, but this may simply be a busy time.) System was booted to multi-user target after upgrade, this message was generated at login time (but login succeeded, and journalctl captured

[fedora-arm] Re: Raspberry Pi 3+

>I'm undecided whether I want to do the related work to get this support >into F-27. With F28 beta just a week or two away, I suggest that is the appropriate target. ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to

[fedora-arm] Raspberry Pi 3+

F27 will not boot on the new Model 3+. Green LED blinks 4 times (medium), then 4 times (fast), then repeats. The colored splash screen is displayed. Might this be just a device tree problem? Raspbian journal contains a line: raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 3 Model B

Re: [sane-devel] xsane 0.999

Use "Get Preview", and xsane places a rectangular frame around what it thinks is the relevant portion in the preview image. The user can drag the sides of this frame to what he prefers. "Scan" then captures just the area defined by this frame. Every subsequent scan will use this frame, until

[fedora-arm] Re: what do i have to do to enable spi on fedora 27 on a raspberry pi

You might try Fedberry. I uncommented "dtparam=spi=on" in /boot/config.txt and now see the /dev/spidev0.0 and /dev/spidev0.1 devices. The GPIO devices (gpiochip0, gpiochip1, and gpiochip2) are present by default, without any special configuration. With F27, uncertain about what device tree

Re: [sane-devel] libsane-imagescan.so.1' (No such file or directory)

libsane-imagescan.so.1 is in the rpm package at: http://ftp.gwdg.de/pub/opensuse/repositories/home:/zhonghuaren/Fedora_27/x86_64/imagescan-3.32.0-8.1.x86_64.rpm but I have only looked to see this file is there. I have not tried it. Perhaps it will offer you a path forward. I suspect the

Re: [sane-devel] libsane-imagescan.so.1' (No such file or directory)

Does Olaf Meeuwissen's post at https://www.mail-archive.com/sane-devel@lists.alioth.debian.org/msg33846.html help? It describes imagescan as an Epson product. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel

[fedora-arm] Re: Exactly how slow is Fedora 27 on an RP3 ? dnf update takes hours ?

It is definitely a good idea to check the system journal. If something wrong is recorded there, there are likely many instances logged to cause hours of unexpected delay. I find it better to use ssh to connect to my RPi than to suffer its slow graphics performance. Time information for a 'dnf

[fedora-arm] Re: Summary of Fedora on Odroid XU4

>This is where I put my grumpy hat on. Not grumpy, and it is no slur to call you realistic. (I would even venture to think you optimistic.) Thank you for cogent words about the Peter Robinson world. ___ arm mailing list -- arm@lists.fedoraproject.org

[fedora-arm] Re: Installing Updated Kernel on Raspberry Pi

"dnf upgrade" has installed many new kernels on my Raspberry Pi. ___ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: Help about install version 26

If nothing looks more promising, try a different display. I have experienced a problem that resembles yours when I tried to use a modern Dell 4K resolution (8 megapixel) display with my RPi 3. An older display (without 4K capability) works. I have not tried my high resolution display recently,

Re: F26 doesn't wake up after updates

I have found some problems with resume from suspended state to be much improved after I switched to "GNOME on xorg". It is too soon to conclude they will not recur, but several days have passed without difficulty. F26 up-to-date on a Lenovo Yoga 3 11-inch laptop, model name 80J8.

[fedora-arm] Re: Fedora ARM Installer

>compressed *.raw.xz images which must be unpacked (at least under >windows) to write on SD card. https://en.wikipedia.org/wiki/XZ_Utils provides links to programs that should expand the .xz file on a Windows system. The expanded file is what must be copied to a SD card and used in an ARM

Re: New Blocker Criterion Proposal: Same default packages for all arches

>> In an extreme situation, a release could be nearly impossible due to >> dependency cycles. > >You'd need to provide specific examples for "extreme" as this has not >happened in recent Fedora history (at least back to F-21) I cannot cite an historical example. With more than a thousand

Re: New Blocker Criterion Proposal: Same default packages for all arches

I agree with you that Firefox is an important resource that Fedora should deliver, but think a criterion that failure to supply the same default package set for all (blocking) architectures will do more harm than good. Release criteria should focus on the quality of what is delivered in a

[fedora-arm] Re: RPi 3 extremely slow with F25. Extremely !

If the slowdown is due to log writes, what is written into your journal? It may be awkward to access the journal using the RPi, but move the SD card to another Fedora system (many laptops have flash card readers built in, or use a USB device) and a "smoking gun" may be obvious. The journal

[fedora-arm] Re: F26 Python LC_CTYPE=C complaint.

I understood, will report as you suggested later today. Too many balls in the air right now. >The display and initial-setup should come up even with the module >blacklisted (perhaps not on workstation, not tested there), you lose some >performance but it should be very usable. I did want to

[fedora-arm] Re: F26 Python LC_CTYPE=C complaint.

>>> In order to boot F26 on a Raspberry Pi, it is necessary to blacklist the >>> vc4 module to avoid a kernel failure >>> (https://bugzilla.redhat.com/show_bug.cgi?id=1387733). This means the >> >>Hopefully this is no longer the case. On the 20170416 nightly images[1] I >>didn't need to blacklist

[fedora-arm] Re: F26 Python LC_CTYPE=C complaint.

>> In order to boot F26 on a Raspberry Pi, it is necessary to blacklist the >> vc4 module to avoid a kernel failure >> (https://bugzilla.redhat.com/show_bug.cgi?id=1387733). This means the > >Hopefully this is no longer the case. On the 20170416 nightly images[1] I >didn't need to blacklist on my

[fedora-arm] F26 Python LC_CTYPE=C complaint.

Running on Raspberry Pi 3, with updates to April 19: [ryniker@RPi3-2 ~]$ uname -a Linux RPi3-2 4.11.0-0.rc5.git0.1.fc26.armv7hl #1 SMP Mon Apr 3 21:06:36 UTC 2017 armv7l armv7l armv7l GNU/Linux [ryniker@RPi3-2 ~]$ /usr/bin/python3.6 --version Python detected LC_CTYPE=C: LC_ALL & LANG coerced to

[fedora-arm] Re: Raspberry Pi 3 B Gpio

>Yes, there's python3-libsoc which should support the RPi. libsoc uses the old, deprecated sysfs interface to access GPIO resources from user space. I wrote a Python module to use the newer, file descriptor ioctl interface. See: http://ryniker.org/raspberrypi/Fedora/gpiofd.py I welcome

[fedora-arm] Re: Fedora Server image - where is newaliases

newaliases is part of the sendmail package. exim does not use the binary (compiled) alias data that newaliases creates for sendmail, but exim provides a newaliases file that does nothing so that users who install exim do not have to change any scripts they may have that modify the aliases file

[fedora-arm] kernel 4.9.2-200.fc25.armv7hl

Additional problem on Raspberry Pi (model 3): there is no: /sys/class/gpio This does exist with the 4.8.15-300 kernel, but it has problems: [root@RPi3-1 gpiochip970]# echo 993 >/sys/class/gpio/export [root@RPi3-1 gpiochip970]# echo 1 > /sys/class/gpio/gpio993/value bash: echo: write error:

[fedora-arm] kernel 4.9.2-200.fc25.armv7hl

4.9.2 does not appear to do much good. The blank screen problem https://bugzilla.redhat.com/show_bug.cgi?id=1387733 continues, and the kernel: i2c-bcm2835 3f805000.i2c: i2c transfer timed out message still appears in the journal. The following document my experience:

[fedora-arm] Re: Raspberry Pi 2 - are post-install steps required?

Thank you, that provides a welcome solution. The Fedora case is slightly different: [ryniker@RPi3-1 ~]$ ls /sys/class/gpio export gpiochip970 unexport [ryniker@RPi3-1 ~]$ cat /sys/class/gpio/gpiochip970/base 970 Now the following works (at least there is no complaint; I

[fedora-arm] Re: Raspberry Pi 2 - are post-install steps required?

I believe GPIO is broken because the Raspbery Pi hardware platform is not correctly recognized, but I have not had available time to look carefully. [root@RPi3-1 ryniker]# uname -a Linux RPi3-1 4.8.4-301.fc25.armv7hl #1 SMP Tue Oct 25 02:01:39 UTC 2016 armv7l armv7l armv7l GNU/Linux Simple test

[fedora-arm] Re: Fedora 25 Candidate RC-1.3 for AArch64 Available Now!

Firefox (firefox.x86_64 49.0.2-1.fc24 @updates) complains (create an exception to allow Fedora to access the site)... https://arm.koji.fedoraproject.org/compose/25/Fedora-25-20161117.0/compose/ Peer’s Certificate issuer is not recognized. HTTP Strict Transport Security: false HTTP Public Key

Re: [sane-devel] A Cooperation Message from Plustek Inc.

>Isn't requiring anything beyond the point 1 a teensy bit over-reaching? Regarding binary stuff, no. If some blob of firmware must be delivered to the scanner, this firmware must be made available under terms that allow it to be copied and used by anyone who wishes to have SANE operate with a

[fedora-arm] Re: F25: black monitor on RPi 2

Sylvain Pasche on Tue, 25 Oct 2016 21:47:40 wrote: >My current workaround is just to blacklist vc4 (if that can help someone): >echo blacklist vc4 > /etc/modprobe.d/blacklist-vc4.conf That gives me a console on my RPi3, eliminates the "i2c-bcm2835 3f805000.i2c: i2c transfer

[fedora-arm] Re: F25 beta failure with RPi-3

Two more trials without any improvement: Using kernel-4.9.0-0.rc2.git0.2.fc26 does not help. I had no reason to think it would, but now that ssh to my RPi3 works well, it was easy to try. Changing the display to a Dell P2415Q (3840x2160 resolution, HDMI input) does not help. Again,

[fedora-arm] Re: F25 beta failure with RPi-3

Peter Robinson on Tue, 25 Oct 2016 10:23:13 wrote: >There's a new 4.8.4-301.fc25 kernel that I think should fix this issue No improvement with this new kernel. I set default to multi-user.target in an attempt to avoid any X11 confusion. After several screens of boot

[fedora-arm] Re: F25 beta failure with RPi-3

Peter Robinson wrote on Sat, 22 Oct 2016 15:18:00: >Can you just provide the output of dmesg? Yes, below, but it was a chore. How does one execute dmesg when there is no accessible user? The system boots far enough to initialize the Ethernet connection, and sshd is

[fedora-arm] F25 beta failure with RPi-3

Boots (a few screens of messages) but fails to run first boot user setup. There appears to be some confusion about the output display (HDMI connection) though it worked through u-boot and beyond the switch to framebuffer for additional line output. Journalctl output (from the 2016.10.18 nightly)

Re: again F25 on USB Flash medium - with legacy ok - only problem with EFI -Anaconda

>install F25 Beta in legacy mode on an 64GB flash medium. And surprise it >works. I think this suggests there is some configuration or BIOS problem with EFI and USB in your machine. Both Chris Murphy and I performed successful EFI installations, he with Apple and I with Samsung hardware. It may

Re: [sane-devel] Ubuntu 16.04.1 and Canoscan Lide 220

Your udev rules file has no entry for your scanner. Recall that sane-find-scanner reported: found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan]) There should be a udev rule for that device (i.e. one that matches the vendor and product codes reported by sane-find-scanner). For

Re: [sane-devel] Ubuntu 16.04.1 and Canoscan Lide 220

>$ sane-find-scanner >found USB scanner (vendor=0x04a9 [Canon], product=0x190f [CanoScan]) >at libusb:003:002 could not open USB device 0x1d6b/0x0002 at 003:001: >Access denied (insufficient permissions) This looks like a permission problem: the user who executed sane-find-scanner is not allowed

Re: Installation validation test change proposal: merge USB tests into 'default boot and install', add more environment columns

>an optical specific Live Workstation spin Sounds like the proper category: will not block a regular Fedora release, will not consume test resources for primary Fedora deliverables, and will provide a focus for those with some stake in optical media. While lack of community to support an

Re: Fedora on usb connected media

Might this be a clue (from your anaconda log)? 13:10:26,938 INFO anaconda: Running post-installation scripts 13:10:26,938 INFO anaconda: Running kickstart %%post script(s) 13:10:29,210 ERR anaconda: Error code 1 running the kickstart script at line 33 13:10:29,210 INFO anaconda: All

Re: Fedora on usb connected media

Works for me. I used a Samsung 940X laptop and a Sandisk 80GB USB3 external SSD. This is a UEFI machine, and I installed using manual partitioning to re-use partitions on the external device, which contained an old Fedora 23 system. My purpose here was to preserve an encrypted /home partition.

25_Alpha-2 installation to VM: boot loader install failed

The target VM has two virtual IDE drives, sda (8 GB) for / and sdb (0.5GB) for /boot. Installation proceded normally until time to install the bootloader, which failed. Pop-up window said bootloader installation failed, and I chose to continue anyway in order to acquire as much log information

Re: 'dnf system-upgrade reboot' doesn't do anything

I seem to have touched a sore spot on Mr. Murphy, and apologize if I have unintentionally irritated him. If he is the designer of the offline update mechanism, and I correctly perceive the implications of his explanation, then I do scold him for failure to mitigate the damage that might occur to a

Re: 'dnf system-upgrade reboot' doesn't do anything

I am unhappy with the suggestion that the semantics of kernel parameters may depend on some notion about how "temporary" they are. If a kernel parameter is specified, it is present; if not specified, it is absent. It is proper to design parameter syntax and default values to favor common usage.

Re: fedora-bookmarks prevents installation of curent updates in F24

The following worked for me: dnf erase astronomy-bookmarks (This also erased firefox.) dnf upgrade dnf install firefox (This also installed astronomy-bookmarks) -- test mailing list test@lists.fedoraproject.org To unsubscribe:

Re: [sane-devel] Need sane docs

I doubt a gigabit Ethernet connection will make any significant difference. Data rate from your scanner is dependent on the mechanical speed of the sensor and scan resolution. If you scan a page 8.5 by 11 inches at 600 pixels per inch resolution with 24 bits per pixel, there is about 100

Re: [sane-devel] Need sane docs

"Timed wait" is the final stage when a TCP connection is closed. TCP has the notion of "maximum segment lifetime" - how long a datagram might remain somewhere in the network. Before a connection is completely closed, it remains in the "timed wait" state for twice this maximum segment lifetime.

Re: criterion proposal: upgrading across 2 releases

>A month is a pretty long time in Fedora development True, but a month is only available if the problem is reported on day 1. If it takes a week or two for a user to report a problem, that interval lessens the remaining time to EOL. On the other hand, there is no prohibition against a fix after

Re: criterion proposal: upgrading across 2 releases

>It's not like dnf-system-upgrade would magically stop working when N-2 >reaches EOL, so honestly, overall, I just don't really see the problem >you're describing Like most of Fedora, dnf-system-upgrade gets limited testing before release. When N is released, a large number of users who did not

Re: criterion proposal: upgrading across 2 releases

System-upgrade across two releases raises an interesting End-of-Life policy issue. If system-upgrade from N-2 to N is so important it will block release of N until it works, how do we explain why it is no longer important after four weeks when N-2 reaches End of Life? Four weeks is little time

Re: criterion proposal: upgrading across 2 releases

On Tue, 24 Nov 2015 10:46:55 -0800, Adam Williamson wrote: > We have never really gone to any lengths to test or support N-1 upgrades > with 3rd party repositories or non-repo software either. That's a > different question. >From a user's perspective, the value of system-upgrade depends on its

Re: criterion proposal: upgrading across 2 releases

On Tue, 24 Nov 2015 07:52:47 -0500, Stephen Gallagher wrote: > I've upgraded several family members directly from Fedora 21 to Fedora 23 > in the last week with no issues whatsoever (of course, I also curate > their repository selection, so they don't end up with incompatible > packages). Aye,

Re: criterion proposal: upgrading across 2 releases

I believe a failure to upgrade from N-2 to N should not block the N release. The reason is limited resources, both for tests and for changes to fix problems. These resources are more valuable applied to the N release than to something two releases in the past. If someone wants to test a

Re: Grub Error in F23 Release? Grub stops in OS selection for Windows for ever.

When you change from the GRUB default boot item, the timer stops and no default boot occurs. You must use a key to tell GRUB to boot the current selection. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test

Re: comment to F23 Final RC10 - still card reader problem

I think you may be the victim of GNOME's "Do what you maybe probably want." attitude. This is something you might be able to configure to your taste, given sufficient knowledge about what specifications to change. I have a Lenovo machine with a Realtec card reader: [ryniker@lenovo ~]$ lspci |

Re: [sane-devel] New hardware / Fedora x86_64 / Canon LiDE 210: "invalid argument"

>And Fedora22 updated the sane packages to 1.0.25 yesterday! Also Fedora 21. Therefore, all supported versions of Fedora now use 1.0.25. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with

  1   2   3   >