Asus Eee PC 4G Surf (701) OS
by Robert Moskowitz
I have just dug out an old Asus Eee 701 from my bin. I have a little
project I want to use if for.
It looks like it has 1Gb mem, 4GB SSD, 7" monitor and has Fedora17 and I
think Gnome (Nautilus file manager).
250MB free disk space! :)
What is the latest ver of Fedora I can drop on this? And have Xfce
desktop. It was around Fedora 18 that I switched to Xfce on my main
laptops.
I am not adverse to putting in an SD card (it has a slot for one) and
putting part of the OS there.
It is not worth my effort to upgrade the SSD unless I get one really cheap!
I do seem to recall that given how narrow the screen is on this, some
fixed dialogs were not fully visible and I had to use some magic key
combinations to move dialogs around to see the bottom of them...
thanks
1 year, 3 months
Fedora 35 - enscript download failed
by Robert Moskowitz
Wanted to install enscript and it failed:
Installing:
enscript x86_64 1.6.6-27.fc35 fedora 413 k
Transaction Summary
================================================================================
Install 1 Package
Total download size: 413 k
Installed size: 1.8 M
Is this ok [y/N]: y
Downloading Packages:
0% [ ] 1.0 kB/s | 0 B
00:00 ETA
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
Status code: 404 for
https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64
(IP: 140.211.169.196)
Did a clean (0 files removed) and tried again:
Installing:
enscript x86_64 1.6.6-27.fc35 fedora 413 k
Transaction Summary
================================================================================
Install 1 Package
Total download size: 413 k
Installed size: 1.8 M
Is this ok [y/N]: y
Downloading Packages:
100% [====================] 1.2 kB/s | 359 B
00:00 ETA
The downloaded packages were saved in cache until the next successful
transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Error downloading packages:
Status code: 404 for
https://mirrors.fedoraproject.org/metalink?repo=fedora-35&arch=x86_64
(IP: 209.132.190.2)
Am I doing something wrong or is this prgm broken?
1 year, 3 months
USB problem
by Geoffrey Leach
This appears to be associated with a multi-port USB device. After a few
minutes I loose keyboard and (USB) mouse. Any ideas (other than the
multi-port is broken)?
Jan 16 08:41:41 star kernel: usb 2-3: new SuperSpeed USB device number
3 using x Jan 16 08:41:41 star kernel: usb 2-3: New USB device found,
idVendor=0bda, idPro Jan 16 08:41:41 star kernel: usb 2-3: New USB
device strings: Mfr=1, Product=2, Jan 16 08:41:41 star kernel: usb 2-3:
Product: USB 10/100/1000 LAN Jan 16 08:41:41 star kernel: usb 2-3:
Manufacturer: Realtek Jan 16 08:41:41 star kernel: usb 2-3:
SerialNumber: 001000001 Jan 16 08:41:49 star kernel: usb usb1-port1:
unable to enumerate USB device Jan 16 08:41:49 star kernel: usb 2-3:
reset SuperSpeed USB device number 3 using Jan 16 08:41:57 star kernel:
usb usb1-port1: attempt power cycle Jan 16 08:42:05 star kernel: usb
usb1-port1: unable to enumerate USB device Jan 16 08:42:14 star kernel:
usb usb1-port1: attempt power cycle Jan 16 08:42:22 star kernel: usb
usb1-port1: unable to enumerate USB device Jan 16 08:42:30 star kernel:
usb usb1-port1: attempt power cycle Jan 16 08:42:38 star kernel: usb
usb1-port1: unable to enumerate USB device Jan 16 08:42:46 star kernel:
usb usb1-port1: attempt power cycle Jan 16 08:42:55 star kernel: usb
usb1-port1: unable to enumerate USB device
1 year, 3 months
slow keyboard shortcuts in gnome 42.4 after update
by Amadeus WM
Just did a dnf update today, all is well, except my gnome keyboard
shortcuts take forever (15-20 seconds) to execute. Launching things from
the menu or from command line works instantly.
Anyone experiencing this? Any fix?
fedora 36
gnome 42.4
1 year, 3 months
No nameserver found after kernel upgrade
by Jouk
Hi all,
Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After rebooting no nameservers are found at the end of /run/systemd/resoilve/resolv.conf.
I found 2 ways to get the name resolve work again:
-reboot in kernel 6.0.16
-Change the internet adapter configuration from DHCP to Manual (and inserting the same info as before)
This looks to me to be a bug. (or am I wrong?)
regards
Jouk
1 year, 3 months
Manually get memtest 6.01 to work on both Legacy and UEFI boot with Fedora.
by Michael D. Setzer II
Memtest not working on Fedora correctly
With Legacy BIOS boot it installs the firstmenu entry,
but it fails.
Some time ago, I created the 2nd menu entry manually,
and it would work with Legacy boot.
Now have discovered there is a 6.01 version, and can get
it to work with manual entries, but requires different
options for booting with Legacy and UEFI.
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry 'Fedora Memtest memtest86+-5.31' {
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5
--hint-baremetal=ahci0,msdos5 --hint='hd0,msdos5'
fa908208-22bd-4031-b620-841498e0708c
else
search --no-floppy --fs-uuid --set=root
fa908208-22bd-4031-b620-841498e0708c
fi
insmod bsd
echo 'Loading Fedora Memtest
memtest86+-5.31 ...'
knetbsd /elf-memtest86+-5.31
}
menuentry 'Memtest' {
echo 'Loading memdisk'
linux16 /memdisk iso
echo 'Loading iso'
initrd16 /memtest86+-5.31b.iso
}
### END /etc/grub.d/20_memtest86+ ###
From https://memtest.org/ see the new 6.01 version.
Download new version.
https://memtest.org/download/v6.01/mt86plus_6.01_64.g
rub.iso.zip
Extract file and use isomaster mt86plus64.grub.iso
to view content. It has two different versions of memtest
one in legacy boot and one under efi. Extract both, and
rename.
Renamed them to
144344 memtest.leg
144384 memtest.uefi
With a legacy boot grub.cfg loads fine with.
menuentry 'Memtest' {
linux /memtest.leg
}
With my one machine with UEFI boot the grub.cfg works
with
menuentry 'Memtest' {
linux /memtest.uefi
}
If try the leg version it gives error message of Dos Magic
Number.
With the memtest installed as rpm on UEFI boot,
running setup gives this.
memtest-setup
ERROR: memtest86+ does not support EFI platforms.
Manually putting this in /boot/grub2/grub.cfg it works.
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry 'Memtest' {
linux /memtest.uefi
}
### END /etc/grub.d/20_memtest86+ ###
Don't have enough info on how the Fedora could be
updated to automatically setup the new 6.01 memtest,
but does show it is possible.
Thanks.
+------------------------------------------------------------+
Michael D. Setzer II - Computer Science Instructor
(Retired)
mailto:mikes@guam.net
mailto:msetzerii@gmail.com
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+
1 year, 3 months
umbrello?
by Tom Horsley
I've been getting update errors all week with umbrello conflicting
with various kde libraries. Usually errors like that go away in a day
or two, but since it kept happening, I finally asked "What the heck
is umbrello anyway?" and discovered it is a tool for making UML diagrams.
I've never had any use for such a tool, so I asked what depends on
it. Nothing depends on it. I removed it, and the errors went away.
I now wonder why it was on my system at all. Is it packaged with
fedora workstation by default for some reason?
1 year, 3 months
brightness-applet stopped working with kernel-6.1.5
by Frank Elsner
Hello,
I'm using Fedora 37 on an Lenovo ThinkPad x230i with the following
GRUB_CMDLINE_LINUX="net.ifnames=0 selinux=0 quiet acpi_backlight=vendor thinkpad-acpi.brightness_enable=1"
This worked until kernel 6.0.18. With kernel 6.1.5 the applet loads
but doesn't work.
Why this? What should I do to make it working again?
Kind regards,
Frank
1 year, 3 months
6.0.18 missing HDMI sound
by Eyal Lebedinsky
I am on f36, was running kernel 6.0.15 and did a 'dnf update' which installed 6.0.18.
On boot I had no HDMI sound, only line-out (which was plugged in) had sound.
Looking at the logs (grep 'sound') I see in 6.0.15
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input22
2023-01-13T11:08:16+1100 kernel: input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input23
2023-01-13T11:08:17+1100 systemd[1]: Reached target sound.target - Sound Card.
but in 6.0.18:
2023-01-13T10:45:12+1100 kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
2023-01-13T10:45:12+1100 kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
2023-01-13T10:45:12+1100 kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
2023-01-13T10:45:12+1100 kernel: input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
2023-01-13T10:45:12+1100 kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
2023-01-13T10:45:12+1100 kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
2023-01-13T10:45:12+1100 kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input20
2023-01-13T10:45:12+1100 kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:1f.3/sound/card0/input21
2023-01-13T10:45:13+1100 systemd[1]: Reached target sound.target - Sound Card.
2023-01-13T11:07:22+1100 systemd[1]: Stopped target sound.target - Sound Card.
You will notice the missing last two HDMI devices.
Looking at PulseAudio I see that the one HDMI that I usually use:
Digital Stereo (HDMI3) Output + Analog Stereo Input
is now unavailable:
Digital Stereo (HDMI3) Output + Analog Stereo Input (unavailable)
I rebooted again into 6.0.18 with no sound again. Booted 6.0.15 and sound is back.
Is there a simple way to get HDMI sound back with 6.0.18? I hate running a kernel older than the rest of the distro.
What other info will help?
More details that may be relevant
=================================
This was the recent update:
2023-01-13T10:10:36+1100 DEBUG Upgraded: amd-gpu-firmware-20221214-145.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: bash-5.2.15-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: blosc-1.21.2-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: emacs-filesystem-1:28.2-1.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: fluidsynth-libs-2.3.1-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: intel-gpu-firmware-20221214-145.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: iwl3945-firmware-15.32.2.9-145.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: iwl4965-firmware-228.61.2.24-145.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: jitterentropy-3.4.1-3.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: kbrickbuster-22.12.0-2.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: libertas-usb8388-firmware-2:20221214-145.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: libksba-1.6.3-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: librevenge-0.0.5-3.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: libsmbclient-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: libwbclient-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: linux-firmware-20221214-145.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: linux-firmware-whence-20221214-145.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: net-tools-2.0-0.62.20160912git.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: nvidia-gpu-firmware-20221214-145.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: perl-Exporter-Tiny-1.006000-1.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: python3-Automat-22.10.0-1.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: python3-samba-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: python3-samba-dc-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: rpmlint-fedora-license-data-1.10-1.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-client-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-client-libs-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-common-2:4.16.8-1.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-common-libs-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-common-tools-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-dc-libs-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-libs-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-winbind-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-winbind-clients-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: samba-winbind-modules-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: thunderbird-102.6.0-2.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: thunderbird-librnp-rnp-102.6.0-2.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: tpm2-tss-3.2.1-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: traceroute-3:2.1.1-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: vim-common-2:9.0.1160-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: vim-data-2:9.0.1160-1.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: vim-enhanced-2:9.0.1160-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: vim-filesystem-2:9.0.1160-1.fc36.noarch
2023-01-13T10:10:36+1100 DEBUG Upgraded: vim-minimal-2:9.0.1160-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: x265-3.5-5.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: x265-libs-3.5-5.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: xen-libs-4.16.3-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: xen-licenses-4.16.3-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Upgraded: xorg-x11-server-Xwayland-22.1.7-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Installed: kernel-6.0.18-200.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Installed: kernel-core-6.0.18-200.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Installed: kernel-devel-6.0.18-200.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Installed: kernel-modules-6.0.18-200.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Installed: perl-Lexical-SealRequireHints-0.011-18.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Installed: perl-Lexical-Var-0.009-28.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Installed: samba-dcerpc-2:4.16.8-1.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Removed: kernel-6.0.12-200.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Removed: kernel-core-6.0.12-200.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Removed: kernel-devel-6.0.12-200.fc36.x86_64
2023-01-13T10:10:36+1100 DEBUG Removed: kernel-modules-6.0.12-200.fc36.x86_64
If it matters: no GPU beyond the onboard Intel, X log shows:
[ 40.034] (II) LoadModule: "intel"
[ 40.034] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 40.036] (II) Module intel: vendor="X.Org Foundation"
[ 40.036] compiled for 1.20.14, module version = 2.99.917
[ 40.036] Module class: X.Org Video Driver
[ 40.036] ABI class: X.Org Video Driver, version 24.1
[ 40.036] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 40.036] (II) intel: Driver for Intel(R) HD Graphics
[ 40.036] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[ 40.036] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
--
Eyal Lebedinsky (fedora(a)eyal.emu.id.au)
1 year, 3 months
tigervnc fails with "Cannot establish any listening sockets - Make
sure an X server isn't already running(EE)"
by Alex
Hi,
I have a fedora37 desktop install with tigervnc-server and can't get it to
start. I'd like it to start on system boot.
I've followed the HOWTO.md as well as numerous examples online, and can't
figure out what's wrong. I've set the vncpasswd for the user listed in
vncserver.users.
/etc/tigervnc/vncserver.users:
:1=gary
$ cat ~/.vnc/config|grep -Ev '^$|^#'
session=gnome
securitytypes=vncauth,tlsvnc
geometry=800x600
# systemctl start vncserver@:1
Job for vncserver@:1.service failed because the control process exited with
error code.
See "systemctl status vncserver@:1.service" and "journalctl -xeu
vncserver@:1.service"
for details.
systemd[1]: Starting vncserver@:1.service - Remote desktop service (VNC)...
vncserver[5803]: WARNING: vncserver has been replaced by a systemd unit and
is now considered deprecated and removed in upstream.
vncserver[5803]: Please read /usr/share/doc/tigervnc/HOWTO.md for more
information.
vncserver[5803]: WARNING: The first attempt to start Xvnc failed, possibly
because the font
vncserver[5803]: catalog is not properly configured. Attempting to
determine an appropriate
vncserver[5803]: font path for this system and restart Xvnc using that font
path ...
vncserver[5803]: Could not start Xvnc.
vncserver[5803]: _XSERVTransSocketUNIXCreateListener:
...SocketCreateListener() failed
vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already
running
vncserver[5803]: (EE)
vncserver[5803]: Fatal server error:
vncserver[5803]: (EE) Cannot establish any listening sockets - Make sure an
X server isn't already running(EE)
vncserver[5803]: _XSERVTransSocketUNIXCreateListener:
...SocketCreateListener() failed
vncserver[5803]: _XSERVTransMakeAllCOTSServerListeners: server already
running
vncserver[5803]: (EE)
vncserver[5803]: Fatal server error:
vncserver[5803]: (EE) Cannot establish any listening sockets - Make sure an
X server isn't already running(EE)
systemd[1]: vncserver@:1.service: Control process exited, code=exited,
status=255/EXCEPTION
systemd[1]: vncserver@:1.service: Failed with result 'exit-code'.
systemd[1]: Failed to start vncserver@:1.service - Remote desktop service
(VNC).
Could missing fonts really cause this? What more can I do to troubleshoot
this?
1 year, 3 months
