Re: [arch-general] 'base' package install with non-updated linux-kernel
On 10/19/19 8:53 PM, riveravaldez via arch-general wrote: > Hi, > > because of this problem [1] (apparently a kernel/driver/hardware > issue?) I'm forced to stay on linux-5.2.14-arch2-1 right now. > My question is: should/can I anyway install the 'base' package anyway > as explained in [2]? > > Thanks a lot > > [1] https://bbs.archlinux.org/viewtopic.php?id=249330 > [2] > https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ I would disable the nvidia card in the bios and move on with my life, never buying anything with a nvidia chip in it again, or until they have enough respect for their customers that you can use a FOSS driver and have it work 100%. --- Information Technology Works on the net: https://ITwrx.org on the fediverse: @it...@blurts.net
Re: [arch-general] 'base' package install with non-updated linux-kernel
You don't need to install the Linux package. I think generally that's why it was removed from base. You might look into using pacman.conf IgnorePkg to prevent upgrades... But I will try to post on that thread, it may not be an issue with the kernel. So check there shortly On Sat, Oct 19, 2019, 6:53 PM riveravaldez via arch-general < arch-general@archlinux.org> wrote: > Hi, > > because of this problem [1] (apparently a kernel/driver/hardware > issue?) I'm forced to stay on linux-5.2.14-arch2-1 right now. > My question is: should/can I anyway install the 'base' package anyway > as explained in [2]? > > Thanks a lot > > [1] https://bbs.archlinux.org/viewtopic.php?id=249330 > [2] > https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ >
Re: [arch-general] 'base' package install with non-updated linux-kernel
On 10/19/19 9:53 PM, riveravaldez via arch-general wrote: > Hi, > > because of this problem [1] (apparently a kernel/driver/hardware > issue?) I'm forced to stay on linux-5.2.14-arch2-1 right now. > My question is: should/can I anyway install the 'base' package anyway > as explained in [2]? > > Thanks a lot > > [1] https://bbs.archlinux.org/viewtopic.php?id=249330 > [2] > https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/ If your kernel issue was making you not do any updates at all, this seems... suboptimal as you then get no updates at all. The kernel is the one package it is completely okay to not upgrade with the rest of your system, since it doesn't exactly link to any libraries (or have anything link to it), and furthermore, it is totally fine to not have a kernel installed (for example, chroots and containers use the host kernel) or install any other kernel like the linux-lts kernel, currently at version 4.19.80-1. So my advice is to either add the "linux" package to IgnorePkg until your issue is resolved, or switch to the linux-lts kernel for now. The next LTS kernel will skip from 4.19 to 5.4, and hopefully by that time this bug will be fixed... Then simply keep up to date as normal, while keeping an eye on the referenced bugzilla.freedesktop.org ticket. Of course, once you are keeping your system up to date while handling the kernel separately and specially, you should have no problem installing or updating any other package, in this case 'base'. Also note that 'base' does not depend on 'linux'. -- Eli Schwartz Bug Wrangler and Trusted User signature.asc Description: OpenPGP digital signature
[arch-general] 'base' package install with non-updated linux-kernel
Hi, because of this problem [1] (apparently a kernel/driver/hardware issue?) I'm forced to stay on linux-5.2.14-arch2-1 right now. My question is: should/can I anyway install the 'base' package anyway as explained in [2]? Thanks a lot [1] https://bbs.archlinux.org/viewtopic.php?id=249330 [2] https://www.archlinux.org/news/base-group-replaced-by-mandatory-base-package-manual-intervention-required/
Re: [arch-general] Issue with 'eject -T'
On Sat, 2019-10-19 at 11:54 +0200, Guus Snijders wrote:
> Op za 19 okt. 2019 11:30 schreef Ralf Mardorf via arch-general
> :
> > Hi,
> >
> > 'eject -T' doesn't work anymore on my machine, resp. opening the DVD
> > drive doesn't work anymore, when using the traytoggle option. Opening
> > still works without an option and closing with the traytoggle option
> > also still works.
> >
> > $ eject -V
> > eject from util-linux 2.34
> > $ eject -T
> > eject: CD-ROM eject command failed: Device or resource busy
>
> 2 things that come to mind;
>
> - check the kernel messages (dmesg), there could be something useful
Hi,
there are no useful messages.
> - does eject (close) work as root? It could be a weird permission issue
Oops, yes, with root privileges the traytoggle option works for opening
and closing, but without root privileges the user can only open the tray
by using 'eject' without the toggle option.
There's an udev rule from end of last month, maybe it stopped already
working in the end of last month.
I don't understand the content of the udev rule, but as soon as I've got
more time, I'll take a look, if the rule did look different before.
[rocketmouse@archlinux ~]$ ls -hl /usr/lib/udev/rules.d/60-cdrom_id.rules
-rw-r--r-- 1 root root 1.1K Sep 22 20:35 /usr/lib/udev/rules.d/60-cdrom_id.rules
[rocketmouse@archlinux ~]$ cat /usr/lib/udev/rules.d/60-cdrom_id.rules
# do not edit this file, it will be overwritten on update
ACTION=="remove", GOTO="cdrom_end"
SUBSYSTEM!="block", GOTO="cdrom_end"
KERNEL!="sr[0-9]*|vdisk*|xvd*", GOTO="cdrom_end"
ENV{DEVTYPE}!="disk", GOTO="cdrom_end"
# unconditionally tag device as CDROM
KERNEL=="sr[0-9]*", ENV{ID_CDROM}="1"
# stop automatically any mount units bound to the device if the media eject
# button is pressed.
ENV{ID_CDROM}=="1", ENV{SYSTEMD_MOUNT_DEVICE_BOUND}="1"
# media eject button pressed
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $devnode",
GOTO="cdrom_end"
# import device and media properties and lock tray to
# enable the receiving of media eject button events
IMPORT{program}="cdrom_id --lock-media $devnode"
# ejecting a CD does not remove the device node, so mark the systemd device
# unit as inactive while there is no medium; this automatically cleans up of
# stale mounts after ejecting
ENV{DISK_MEDIA_CHANGE}=="?*", ENV{ID_CDROM_MEDIA}!="?*", ENV{SYSTEMD_READY}="0"
KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100"
LABEL="cdrom_end"
[rocketmouse@archlinux ~]$ ls -hl /usr/lib/udev/cdrom_id
-rwxr-xr-x 1 root root 30K Sep 22 20:35 /usr/lib/udev/cdrom_id
[rocketmouse@archlinux ~]$ file -i /usr/lib/udev/cdrom_id
/usr/lib/udev/cdrom_id: application/x-pie-executable; charset=binary
Regards,
Ralf
Re: [arch-general] Issue with 'eject -T'
Op za 19 okt. 2019 11:30 schreef Ralf Mardorf via arch-general < arch-general@archlinux.org>: > Hi, > > 'eject -T' doesn't work anymore on my machine, resp. opening the DVD > drive doesn't work anymore, when using the traytoggle option. Opening > still works without an option and closing with the traytoggle option > also still works. > > $ eject -V > eject from util-linux 2.34 > $ eject -T > eject: CD-ROM eject command failed: Device or resource busy > 2 things that come to mind; - check the kernel messages (dmesg), there could be something useful - does eject (close) work as root? It could be a weird permission issue Mvg, Guus Snijders
[arch-general] Issue with 'eject -T'
Hi, 'eject -T' doesn't work anymore on my machine, resp. opening the DVD drive doesn't work anymore, when using the traytoggle option. Opening still works without an option and closing with the traytoggle option also still works. $ eject -V eject from util-linux 2.34 $ eject -T eject: CD-ROM eject command failed: Device or resource busy $ grep util-linux /var/log/pacman.log | tail -6 [2019-06-21 08:19] [ALPM] upgraded libutil-linux (2.33.2-1 -> 2.34-2) [2019-06-21 08:19] [ALPM] upgraded util-linux (2.33.2-1 -> 2.34-2) [2019-06-21 08:19] [ALPM] upgraded lib32-util-linux (2.33.2-1 -> 2.34-1) [2019-06-29 11:40] [ALPM] upgraded libutil-linux (2.34-2 -> 2.34-3) [2019-06-29 11:40] [ALPM] upgraded util-linux (2.34-2 -> 2.34-3) [2019-10-06 12:37] [ALPM] reinstalled util-linux (2.34-3) I don't know when the issue started, but I'm quite sure it still worked last month. I'm usually using 'eject -T' to open or close the DVD drive by a keyboard shortcut. I accidentally reinstalled util-linux a few days back, IOW that it was reinstalled is meaningless, it might be that it even still worked this time. Could somebody with an up to date Arch Linux install please run 'eject -T' from command line? I want to know if it's an issue on my side or if it's a regression of a dependency or something else unrelated to my machine. TIA, Ralf -- $ uname -r 5.2.21-rt13-0-pussytoes
