Re: Problems with New kernel 6.2.7

Joe Zeff wrote: > On 03/24/2023 11:03 AM, Robert McBroom via users wrote: >> Exactly, the 6.2.7 kernel doesn't compile from the akmod. > > A slight correction: the akmod compiles the kernel module, or kmod, not the > kernel itself. However, I'd check with Bugzilla, and if there's not a bug > repo

Re: Problems with New kernel 6.2.7

On 03/24/2023 11:03 AM, Robert McBroom via users wrote: Exactly, the 6.2.7 kernel doesn't compile from the akmod. A slight correction: the akmod compiles the kernel module, or kmod, not the kernel itself. However, I'd check with Bugzilla, and if there's not a bug report yet, file one. If th

Re: Problems with New kernel 6.2.7

On 3/23/23 04:45, Qiyu Yan wrote: 在 2023/3/23 11:22, Robert McBroom via users 写道: Total strangeness with the new kernel series on fedora 37. My update was from 6.1.14 to the 6.2.7, missing several editions. With the new kernel the display was only 1024x768 on the 27" monitor. Even though

Re: Problems with New kernel 6.2.7

在 2023/3/23 11:22, Robert McBroom via users 写道: Total strangeness with the new kernel series on fedora 37. My update was from 6.1.14 to the 6.2.7, missing several editions. With the new kernel the display was only 1024x768 on the 27" monitor. Even though x11 is selected in the display-ma

Problems with New kernel 6.2.7

Total strangeness with the new kernel series on fedora 37. My update was from 6.1.14 to the 6.2.7, missing several editions. With the new kernel the display was only 1024x768 on the 27" monitor. Even though x11 is selected in the display-manager the system comes up in wayland. Settings

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

the partitions in linux raid1, /boot inclusive, booting from EFI, the efi partition is sda1, and are remote machines, my only access is via ssh. I updated my laptop, ryzen, no raid, to 6.0.5, but it rebooted just fine with the new kernel re

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On 1/11/22 01:45, Tom Horsley wrote: On Mon, 31 Oct 2022 10:26:16 -0400 Tom Horsley wrote: So something about a complete power down seems to have made it better. And I tried rebooting again, and that is working now as well. So the power cycle does seem to have made it all better. I guess I'll

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On 10/30/22 13:00, Tom Horsley wrote: As an additional report, I did a dnf update this morning, got the same kernel, and had no problems at all. Must be one of those things mankind was not meant to know Another two reports: one on a Ryzen TR 2950X/6900XT with no issues, the second is a 12th Ge

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On Mon, 31 Oct 2022 10:26:16 -0400 Tom Horsley wrote: > So something about a complete power down seems to have made it better. And I tried rebooting again, and that is working now as well. So the power cycle does seem to have made it all better. I guess I'll find out in a few days if there is som

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

Slight weirdness for me too. Probably the first time since I installed 6.0.5 I tried to play a youtube video and got no sound (HDMI via rpmfusion nvidia driver). I tried to reboot to go back one kernel version and see if sound worked there, and the reboot blanked the screen, but then was stuck. I

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

Just a "me too" here, but I ran 6.0 fine when there was a call for testing. When I updated to 6.0.5 my computer (B550 w/ Ryzen 5 5700X) paused at the BIOS post for a long time and then kind of tried to load but stalled. I forced it off and turned off the PS for 10 seconds and rebooted, then it see

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On 31/10/22 09:14, Samuel Sieb wrote: On 10/30/22 10:06, Doug Herr wrote: Let this be a reminder to people upgrading over many version of Fedora. It does not hurt to update your grub boot sector every now and then. Maybe worth doing after each major Fedora version update. This only applies if

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On 10/30/22 4:33 PM, Barry Scott wrote: > >> On 30 Oct 2022, at 16:54, Doug H. wrote: >> >> Today was >> the big kernel jump to 6.x kernel. As someone who tests 6.0 stable regularly, I can *assure you* it's nothing major. > No it is not a big jump it the one after 5.19. > After 20 minors Linux

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On 10/30/22 10:06, Doug Herr wrote: Let this be a reminder to people upgrading over many version of Fedora. It does not hurt to update your grub boot sector every now and then. Maybe worth doing after each major Fedora version update. This only applies if you are still using legacy BIOS boot,

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On Sun, Oct 30, 2022 at 1:00 PM Tom Horsley wrote: > > On Sun, 30 Oct 2022 09:54:28 -0700 > Doug H. wrote: > > > Everything seems to be working, so I don't need any help, but wanted to > > report this just in case. > > As an additional report, I did a dnf update this morning, got the same > kernel

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

> On 30 Oct 2022, at 16:54, Doug H. wrote: > > Today was > the big kernel jump to 6.x kernel. No it is not a big jump it the one after 5.19. After 20 minors Linux runs out of fingers and toes and bumps the major. So after 6.19 with me 7.0 for example. Barry __

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On Sun, Oct 30, 2022, at 9:54 AM, Doug H. wrote: > I do dnf upgrade any morning where something shows up as new. Today was > the big kernel jump to 6.x kernel. Was not worried I guess since I just > ran the update like normal and rebooted to it. > > Ended up at: > > error: ../../grub-core/kern/dl.c

Re: New kernel install had issues. (6.0.5-200.fc36.x86_64)

On Sun, 30 Oct 2022 09:54:28 -0700 Doug H. wrote: > Everything seems to be working, so I don't need any help, but wanted to > report this just in case. As an additional report, I did a dnf update this morning, got the same kernel, and had no problems at all. Must be one of those things mankind wa

New kernel install had issues. (6.0.5-200.fc36.x86_64)

I do dnf upgrade any morning where something shows up as new. Today was the big kernel jump to 6.x kernel. Was not worried I guess since I just ran the update like normal and rebooted to it. Ended up at: error: ../../grub-core/kern/dl.c:429:symbol `grub_debug_is_enabled' not found. Entering rescu

Re: New kernel

On Fri, 2021-07-23 at 13:56 -0600, Chris Murphy wrote: > On Fri, Jul 23, 2021 at 12:48 PM Patrick O'Callaghan > wrote: > > > > On Fri, 2021-07-23 at 21:09 +0300, jarmo wrote: > > > Somethin went't wrong. Got updates of new kernel, > > > kernel-5.13.4

Re: New kernel

Fri, 23 Jul 2021 21:13:20 -0700 Samuel Sieb kirjoitti: > On 2021-07-23 11:09 a.m., jarmo wrote: > > An my wife's Toshiba Satellite, After I disabled /dev/zram0 from > > system, because from boot.log I could see, that It tried to create > > SWAP to /dev/zram0. That Toshiba has also partitions /swa

Re: New kernel

Fri, 23 Jul 2021 13:56:22 -0600 Chris Murphy kirjoitti: > If you can find the boot this happened in and file a bug against the > kernel, that would be great: > > This can help find the boot that it happened with > journalctl --list-boots Harmfully, at age of 70, I speak NERD very little :) Sor

Re: New kernel

On 2021-07-23 11:09 a.m., jarmo wrote: An my wife's Toshiba Satellite, After I disabled /dev/zram0 from system, because from boot.log I could see, that It tried to create SWAP to /dev/zram0. That Toshiba has also partitions /swap and / EXT4 no LVM no UEFI. Why did you disable it? __

Re: New kernel

On Fri, Jul 23, 2021 at 1:56 PM Chris Murphy wrote: > > Even better is if you can reproduce the high load and try to capture > one or more of the following: sysrq+l which will dump the result into Actually, sysrq+w is also useful. The root user can use: echo l > /proc/sysrq-trigger echo w > /pro

Re: New kernel

On Fri, Jul 23, 2021 at 12:48 PM Patrick O'Callaghan wrote: > > On Fri, 2021-07-23 at 21:09 +0300, jarmo wrote: > > Somethin went't wrong. Got updates of new kernel, > > kernel-5.13.4-200.fc34.x86_64. > > > > Now my HPlaptop won't start. I can writ

Re: New kernel

On Fri, 2021-07-23 at 21:09 +0300, jarmo wrote: > Somethin went't wrong. Got updates of new kernel, > kernel-5.13.4-200.fc34.x86_64. > > Now my HPlaptop won't start. I can write to loginwindow > asked passwd. After that everything hangs. > with kernel 5.12.15-300.fc34

New kernel

Somethin went't wrong. Got updates of new kernel, kernel-5.13.4-200.fc34.x86_64. Now my HPlaptop won't start. I can write to loginwindow asked passwd. After that everything hangs. with kernel 5.12.15-300.fc34.x86_64 works. I have system in legacy mode, no LVM no UEFI. Only patitions

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 16:48, Jerome Lille wrote: On Thu, 2021-02-25 at 13:19 -0400, George N. White III wrote: On Sun, 21 Feb 2021 at 12:46, Jerome Lille wrote: I tried to simply change type from nfs to nfs4 in the fstab in the client. Unfortunately I then get the response mount.nfs4: access denied b

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-25 at 13:19 -0400, George N. White III wrote: > On Sun, 21 Feb 2021 at 12:46, Jerome Lille > wrote: > > I tried to simply change type from nfs to nfs4 in the fstab in the > > client. Unfortunately I then get the response > > > > mount.nfs4: access denied by server while mounting

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 07:38, George N. White III wrote: So, I still can't find a way to duplicate the OP's problem without specifically changing a config file. There is always the possibility of some "invisible character" error in a config file. The OP has said he hadn't modified any config f

Re: New kernel errors after last update, Fedora 33

On Thu, 25 Feb 2021 at 18:11, Ed Greshko wrote: > On 26/02/2021 04:21, George N. White III wrote: > > On Thu, 25 Feb 2021 at 14:03, Ed Greshko > wrote: > > > > On 26/02/2021 01:19, George N. White III wrote: > > > I haven't used CentOS7 for several years, s

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 04:21, George N. White III wrote: On Thu, 25 Feb 2021 at 14:03, Ed Greshko mailto:ed.gres...@greshko.com>> wrote: On 26/02/2021 01:19, George N. White III wrote: > I haven't used CentOS7 for several years, so I was ignoring this > thread in the hope others could answer.

Re: New kernel errors after last update, Fedora 33

On Thu, 25 Feb 2021 at 14:03, Ed Greshko wrote: > On 26/02/2021 01:19, George N. White III wrote: > > I haven't used CentOS7 for several years, so I was ignoring this > > thread in the hope others could answer. > > > > My not very trustworthy memory is that "/etc/exports" on > > the server needs

Re: New kernel errors after last update, Fedora 33

On 26/02/2021 01:19, George N. White III wrote: I haven't used CentOS7 for several years, so I was ignoring this thread in the hope others could answer. My not very trustworthy memory is that "/etc/exports" on the server needs the "insecure" option for NFS4 to work, see: https://access.redhat.co

Re: New kernel errors after last update, Fedora 33

On Sun, 21 Feb 2021 at 12:46, Jerome Lille wrote: > I tried to simply change type from nfs to nfs4 in the fstab in the > client. Unfortunately I then get the response > > mount.nfs4: access denied by server while mounting ... > > There is nothing in the server logs about this. And it is not the >

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-25 at 07:40 +0800, Ed Greshko wrote: > > Well, I'm sorry but I'm out of ideas. > > I can mount file systems hosted on a Centos7 server from an F33 > client with no problems with nfsv4. > I can't figure out how to create the problems you're seeing without > modification to configur

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 22:22, Jerome Lille wrote: On Wed, 2021-02-24 at 05:41 +0800, Ed Greshko wrote: What is the output of cat /run/sysconfig/nfs-utils RPCNFSDARGS=" " RPCMOUNTDARGS="" STATDARGS="" SMNOTIFYARGS="" RPCIDMAPDARGS="" GSSDARGS="" BLKMAPDARGS="" GSS_USE_PROXY="yes" Oh, also, do you happ

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-24 at 05:41 +0800, Ed Greshko wrote: > > What is the output of > > cat /run/sysconfig/nfs-utils RPCNFSDARGS=" " RPCMOUNTDARGS="" STATDARGS="" SMNOTIFYARGS="" RPCIDMAPDARGS="" GSSDARGS="" BLKMAPDARGS="" GSS_USE_PROXY="yes" > Oh, also, do you happen to have a /etc/nfs.conf.d direc

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 05:41, Ed Greshko wrote: That polkitd message occurs here as well.  So, not an issue. What is the output of cat /run/sysconfig/nfs-util Oh, also, do you happen to have a /etc/nfs.conf.d directory? -- People who believe they don't make mistakes have already made one. __

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 04:41, Jerome Lille wrote: On Wed, 2021-02-24 at 02:38 +0800, Ed Greshko wrote: The other way to disable NFSv4 is to modify /etc/sysconfig/nfs to have the line # Optional arguments passed to rpc.nfsd. See rpc.nfsd(8) RPCNFSDARGS="--no-nfs-version 4" You should check that as well.

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-24 at 02:38 +0800, Ed Greshko wrote: > > The other way to disable NFSv4 is to modify /etc/sysconfig/nfs to > have the line > > # Optional arguments passed to rpc.nfsd. See rpc.nfsd(8) > RPCNFSDARGS="--no-nfs-version 4" > > You should check that as well. > > Bottom line, NFSv4 is

Re: New kernel errors after last update, Fedora 33

On 24/02/2021 00:27, Jerome Lille wrote: On Tue, 2021-02-23 at 23:16 +0800, Ed Greshko wrote: [mountd] debug=all And then restart the server. After doing the mount from the client, check the journal for rpc.mountd messages. Ok, what I got when doing 'mount -v server:/path /path' (i.e. it trie

Re: New kernel errors after last update, Fedora 33

On Tue, 2021-02-23 at 23:16 +0800, Ed Greshko wrote: > [mountd] > debug=all > > And then restart the server. > > After doing the mount from the client, check the journal for rpc.mountd > messages. Ok, what I got when doing 'mount -v server:/path /path' (i.e. it tried v4 first then succeeded on v

Re: New kernel errors after last update, Fedora 33

On 23/02/2021 21:58, Jerome Lille wrote: On Tue, 2021-02-23 at 04:37 +0800, Ed Greshko wrote: On 23/02/2021 00:27, Jerome Lille wrote: My nfs.conf is untouched. You do mean that file on the nfs server side, right? Exactly OK Modify that file to have # [mountd] debug=all And then

Re: New kernel errors after last update, Fedora 33

On Tue, 2021-02-23 at 04:37 +0800, Ed Greshko wrote: > On 23/02/2021 00:27, Jerome Lille wrote: > > My nfs.conf is untouched. > > You do mean that file on the nfs server side, right? Exactly > > When I do the following command > > mount -v server:/path /path > > > > I get the following > > I

Re: New kernel errors after last update, Fedora 33

On 23/02/2021 00:27, Jerome Lille wrote: On Mon, 2021-02-22 at 08:39 +0800, Ed Greshko wrote: On 22/02/2021 08:24, Ed Greshko wrote:  have not made any changes to the nfs server configuration file /etc/ nfs.conf so the defaults are in effect. # vers2=n # vers3=y # vers4=y # vers4.0=y # vers4.

Re: New kernel errors after last update, Fedora 33

On Mon, 2021-02-22 at 08:39 +0800, Ed Greshko wrote: > On 22/02/2021 08:24, Ed Greshko wrote: > >  have not made any changes to the nfs server configuration file /etc/ > > nfs.conf so the defaults are > > in effect. > > > > # vers2=n > > # vers3=y > > # vers4=y > > # vers4.0=y > > # vers4.1=y > >

Re: New kernel errors after last update, Fedora 33

On 22/02/2021 08:24, Ed Greshko wrote:  have not made any changes to the nfs server configuration file /etc/nfs.conf  so the defaults are in effect. # vers2=n # vers3=y # vers4=y # vers4.0=y # vers4.1=y # vers4.2=y Check to make sure these haven't been altered. FWIW, I did do a test and modi

Re: New kernel errors after last update, Fedora 33

On 22/02/2021 00:46, Jerome Lille wrote: I tried to simply change type from nfs to nfs4 in the fstab in the client. Unfortunately I then get the response mount.nfs4: access denied by server while mounting ... There is nothing in the server logs about this. And it is not the firewall, because ev

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-18 at 14:23 -0800, Gordon Messmer wrote: > On 2/18/21 8:38 AM, Jerome Lille wrote: > > But as I said the nfs shares seem to work fine, I can read and > > write to > > files on them. > > > Yep, everything will look fine until an application on your client > tries > to lock a file,

Re: New kernel errors after last update, Fedora 33

On 2/18/21 8:38 AM, Jerome Lille wrote: But as I said the nfs shares seem to work fine, I can read and write to files on them. Yep, everything will look fine until an application on your client tries to lock a file, and then it will hang forever. Locking files during editing is pretty common

Re: New kernel errors after last update, Fedora 33

On 19/02/2021 00:38, Jerome Lille wrote: On Thu, 2021-02-18 at 07:43 +0800, Ed Greshko wrote: On 18/02/2021 03:07, Jerome Lille wrote: 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora desktop that produces these error messages has some shares from it mounted. No errors on the

Re: New kernel errors after last update, Fedora 33

On Thu, 2021-02-18 at 07:43 +0800, Ed Greshko wrote: > On 18/02/2021 03:07, Jerome Lille wrote: > > 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora > > desktop that produces these error messages has some shares from it > > mounted. No errors on the NFS server and the nfs shares

Re: New kernel errors after last update, Fedora 33

On 18/02/2021 03:07, Jerome Lille wrote: 192.168.1.101 is the IP of my local NFS server (Centos7), my Fedora desktop that produces these error messages has some shares from it mounted. No errors on the NFS server and the nfs shares seems to work fine. Are you using NFSv3 or NFSv4 to mount the s

Re: New kernel errors after last update, Fedora 33

On Wed, Feb 17, 2021 at 12:08 PM Jerome Lille wrote: > Thanks for the suggestion. I did get more logging > > RPC: 5d78dc3a connect status 107 connected 0 sock state 7 > xs_tcp_setup_socket: connect returned unhandled error -107 > RPC: xs_tcp_state_change client 5d78dc3a

Re: New kernel errors after last update, Fedora 33

On Wed, 2021-02-17 at 11:43 -0700, Jerry James wrote: > On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille > wrote: > > After the latest update there are some errors in the log that I > > haven't > > seen before. > > > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > > > There

Re: New kernel errors after last update, Fedora 33

On Wed, Feb 17, 2021 at 10:33 AM Jerome Lille wrote: > After the latest update there are some errors in the log that I haven't > seen before. > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > There are two of those per minute continuously. I haven't noticed any > other pro

Re: New kernel errors after last update, Fedora 33

On Wed, 17 Feb 2021 10:10:23 -0800 Clifford Snow wrote: > I'm running 5.10.15-200.fc33.x86_64 and have not seen those errors. Same here. Sounds like some application is running that causes that error and I'm not running that app. ___ users mailing list

Re: New kernel errors after last update, Fedora 33

I'm running 5.10.15-200.fc33.x86_64 and have not seen those errors. On Wed, Feb 17, 2021 at 9:34 AM Jerome Lille wrote: > After the latest update there are some errors in the log that I haven't > seen before. > > kernel: xs_tcp_setup_socket: connect returned unhandled error -107 > > There are tw

New kernel errors after last update, Fedora 33

After the latest update there are some errors in the log that I haven't seen before. kernel: xs_tcp_setup_socket: connect returned unhandled error -107 There are two of those per minute continuously. I haven't noticed any other problems with the system, but wondering about those messages are abou

Weirdness with new kernel

I *think* I did a shutdown Friday instead of a suspend, as I had to powerup this evening instead of resume.  I will check back into the logs. So given this was a fresh boot (kernel 4.17.144), I did a dnf update and got a new kernel (4.17.19).  I rebooted, and it would not boot up.  I was

Re: new kernel?

On Sat, 25 Aug 2018 10:00:52 +0800 Ed Greshko wrote: > On 08/25/18 09:36, Ranjan Maitra wrote: > > But pulseaudio shows the microphone being recognized and the meter for the > > input going up and down as words are spoken in. I can not see what else > > could be wrong. > > > Well, there are a

Re: new kernel?

On 08/25/18 09:36, Ranjan Maitra wrote: > But pulseaudio shows the microphone being recognized and the meter for the > input going up and down as words are spoken in. I can not see what else could > be wrong. Well, there are actually 2 places in pavucontrol (I use pavucontrol-qt since I'm on K

Re: new kernel?

On Fri, 24 Aug 2018 21:35:14 +0800 Ed Greshko wrote: > On 08/24/18 21:13, Ranjan Maitra wrote: > > Great! I am looking for a new kernel. THe current one does not accept my > > microphone even though all settings indicate that it should. > > > Are you saying you'v

Re: new kernel?

On 08/24/18 21:13, Ranjan Maitra wrote: > Great! I am looking for a new kernel. THe current one does not accept my > microphone even though all settings indicate that it should. Are you saying you've booted a previous kernel to verify that is the source of your problem? FWIW, wh

Re: new kernel?

Great! I am looking for a new kernel. THe current one does not accept my microphone even though all settings indicate that it should. On Thu, 23 Aug 2018 13:39:45 -0600 Chris Murphy wrote: > On Tue, Aug 21, 2018 at 9:10 PM, Ranjan Maitra wrote: > > Just curious, there has not been a

Re: new kernel?

On Tue, Aug 21, 2018 at 9:10 PM, Ranjan Maitra wrote: > Just curious, there has not been a kernel in testing for a while. When is the > next kernel expected to land in Fedora? I guess that it will be a 4.18.3 now > perhaps? Rebasing Fedora 27 and Fedora 28 to kernel 4.18.x has already been anno

Re: new kernel?

For me, it is good to be out of the 'Kernel of the week club'. A little peace and quite is a good thing. :) On 08/21/2018 11:58 PM, Ranjan Maitra wrote: Thanks! I guess that I am just surprised that we have not had a new kernel for a while. We are at 4.17.14 and there is nothing

Re: new kernel?

Thanks! I guess that I am just surprised that we have not had a new kernel for a while. We are at 4.17.14 and there is nothing on updates-testing so I was thinking that perhaps we are moving on to 4.18 hence the delay. Best wishes, Ranjan On Wed, 22 Aug 2018 11:22:32 +0800 Ed Greshko wrote

Re: new kernel?

On 08/22/18 11:10, Ranjan Maitra wrote: > Just curious, there has not been a kernel in testing for a while. When is the > next kernel expected to land in Fedora? I guess that it will be a 4.18.3 now > perhaps? The latest build in koji for F28 is kernel-4.17.17-200 with the following in the chan

new kernel?

Just curious, there has not been a kernel in testing for a while. When is the next kernel expected to land in Fedora? I guess that it will be a 4.18.3 now perhaps? -- Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appr

Re: F27->F28 no new kernel

On 08/02/18 14:26, Samuel Sieb wrote: > On 08/01/2018 10:47 PM, Frank Elsner wrote: >> And in the near future I'll change to 64bit if I have a >> migration strategie to to this painless and quick. > > It isn't painless or quick.  It requires a reinstall.  You can run a 64-bit > kernel > even thoug

Re: F27->F28 no new kernel

On 08/01/2018 10:47 PM, Frank Elsner wrote: And in the near future I'll change to 64bit if I have a migration strategie to to this painless and quick. It isn't painless or quick. It requires a reinstall. You can run a 64-bit kernel even though the rest of the OS is 32-bit, but dnf might get

Re: F27->F28 no new kernel

On Wed, 1 Aug 2018 09:56:52 -0700 Samuel Sieb wrote: > On 07/31/2018 11:50 PM, Frank Elsner wrote: > > But on my TP x230i with 8GB running F28 file /var/log/dnf.rpm.log shows > > 2018-07-23T08:41:52Z INFO Installed: kernel-PAE-4.17.7-100.fc27.i686 > > ^^ ^^

Re: F27->F28 no new kernel

On 08/01/2018 09:56 AM, Samuel Sieb wrote: > On 07/31/2018 11:50 PM, Frank Elsner wrote: >> But on my TP x230i with 8GB running F28 file /var/log/dnf.rpm.log shows >> 2018-07-23T08:41:52Z INFO Installed: kernel-PAE-4.17.7-100.fc27.i686 >> ^^   ^ > >

Re: F27->F28 no new kernel

On 07/31/2018 11:50 PM, Frank Elsner wrote: But on my TP x230i with 8GB running F28 file /var/log/dnf.rpm.log shows 2018-07-23T08:41:52Z INFO Installed: kernel-PAE-4.17.7-100.fc27.i686 ^^ ^ I assume you're saying it's a ThinkPad. Why are you ru

Re: F27->F28 no new kernel

On 08/01/2018 09:50 AM, Rick Stevens wrote: Frank, we've said this before and I don't understand why you're not getting it: Starting with F28, 32-bit PAE kernels are NOT being built and placed in the the standard repos. The new F28 kernel you show is a pure i686, 32-bit kernel and _not_ PAE. T

Re: F27->F28 no new kernel

On 08/01/2018 12:06 AM, Frank Elsner wrote: > On Wed, 1 Aug 2018 08:50:27 +0200 Frank Elsner wrote: >> On Tue, 31 Jul 2018 23:15:57 -0700 Samuel Sieb wrote: >>> On 07/31/2018 10:57 PM, Frank Elsner wrote: Can you please explain the line 2018-08-01T05:53:36Z INFO Installed: kernel-4.17.9-2

Re: Re(2): F27->F28 no new kernel

On Wed, 2018-08-01 at 10:53 +0200, Frank Elsner wrote: > > I don't use yumex, but if it's looking in the yum database while dnf > > looks in the dnf one, there could be an inconsistency. Just a thought. > > Thanks. I didn't know that. > > But if I do "yum update" the newer kernel isn't offered :-

Re: Re(2): F27->F28 no new kernel

On Wed, 2018-08-01 at 09:06 +0200, Frank Elsner wrote: > On Wed, 1 Aug 2018 08:50:27 +0200 Frank Elsner wrote: > > On Tue, 31 Jul 2018 23:15:57 -0700 Samuel Sieb wrote: > > > On 07/31/2018 10:57 PM, Frank Elsner wrote: > > > > Can you please explain the line > > > > 2018-08-01T05:53:36Z INFO Instal

Re: Re(2): F27->F28 no new kernel

On Wed, 01 Aug 2018 09:40:37 +0100 Patrick O'Callaghan wrote: > On Wed, 2018-08-01 at 09:06 +0200, Frank Elsner wrote: > > On Wed, 1 Aug 2018 08:50:27 +0200 Frank Elsner wrote: > > > On Tue, 31 Jul 2018 23:15:57 -0700 Samuel Sieb wrote: > > > > On 07/31/2018 10:57 PM, Frank Elsner wrote: > > > > >

Re: Re(2): F27->F28 no new kernel

On Wed, 2018-08-01 at 09:06 +0200, Frank Elsner wrote: > On Wed, 1 Aug 2018 08:50:27 +0200 Frank Elsner wrote: > > On Tue, 31 Jul 2018 23:15:57 -0700 Samuel Sieb wrote: > > > On 07/31/2018 10:57 PM, Frank Elsner wrote: > > > > Can you please explain the line > > > > 2018-08-01T05:53:36Z INFO Instal

Re(2): F27->F28 no new kernel

On Wed, 1 Aug 2018 08:50:27 +0200 Frank Elsner wrote: > On Tue, 31 Jul 2018 23:15:57 -0700 Samuel Sieb wrote: > > On 07/31/2018 10:57 PM, Frank Elsner wrote: > > > Can you please explain the line > > > 2018-08-01T05:53:36Z INFO Installed: kernel-4.17.9-200.fc28.i686 > > > from /var/log/dnf.rpm.log

Re: F27->F28 no new kernel

On Tue, 31 Jul 2018 23:15:57 -0700 Samuel Sieb wrote: > On 07/31/2018 10:57 PM, Frank Elsner wrote: > > Can you please explain the line > > 2018-08-01T05:53:36Z INFO Installed: kernel-4.17.9-200.fc28.i686 > > from /var/log/dnf.rpm.log of my 32bit F28 system? > > What is there to explain? That is

Re: F27->F28 no new kernel

On 07/31/2018 10:57 PM, Frank Elsner wrote: Can you please explain the line 2018-08-01T05:53:36Z INFO Installed: kernel-4.17.9-200.fc28.i686 from /var/log/dnf.rpm.log of my 32bit F28 system? What is there to explain? That is version 4.17.9 of the kernel, 32-bit non-PAE, built for F28. Do yo

Re: F27->F28 no new kernel

On Tue, 31 Jul 2018 11:00:15 -0700 Samuel Sieb wrote: > On 07/31/2018 08:47 AM, Frank Elsner wrote: > > On Tue, 31 Jul 2018 08:33:08 -0700 Samuel Sieb wrote: > >> The PAE kernel is no longer being built. You either need to switch to > >> non-PAE or 64-bit. > > > > Since when? The TP x121e got the

Re: F27->F28 no new kernel

On 07/31/2018 08:47 AM, Frank Elsner wrote: On Tue, 31 Jul 2018 08:33:08 -0700 Samuel Sieb wrote: The PAE kernel is no longer being built. You either need to switch to non-PAE or 64-bit. Since when? The TP x121e got the kernel-PAE-4.17.7-100.fc27.i686 on 2018-07-17 19:19:51 Si

Re: F27->F28 no new kernel

On 07/31/2018 09:14 AM, Frank Elsner wrote: > On Tue, 31 Jul 2018 08:46:55 -0700 stan wrote: >> On Tue, 31 Jul 2018 15:57:48 +0200 >> Frank Elsner wrote: >> >>> I've just upgraded my TP X230i from F27 to F28 painless. >>> But I'm still on my last F27 kernel-4.16.16-200.fc27.i686+PAE. >>> No newe

Re: F27->F28 no new kernel

On Tue, 31 Jul 2018 08:46:55 -0700 stan wrote: > On Tue, 31 Jul 2018 15:57:48 +0200 > Frank Elsner wrote: > > > I've just upgraded my TP X230i from F27 to F28 painless. > > But I'm still on my last F27 kernel-4.16.16-200.fc27.i686+PAE. > > No newer kernel installed. > > > > During ame upgrade p

Re: F27->F28 no new kernel

On Tue, 31 Jul 2018 08:33:08 -0700 Samuel Sieb wrote: > On 07/31/2018 06:57 AM, Frank Elsner wrote: > > I've just upgraded my TP X230i from F27 to F28 painless. > > But I'm still on my last F27 kernel-4.16.16-200.fc27.i686+PAE. > > No newer kernel installed. > > > > During ame upgrade procedure on

Re: F27->F28 no new kernel

On Tue, 31 Jul 2018 15:57:48 +0200 Frank Elsner wrote: > I've just upgraded my TP X230i from F27 to F28 painless. > But I'm still on my last F27 kernel-4.16.16-200.fc27.i686+PAE. > No newer kernel installed. > > During ame upgrade procedure on my TP x121e kernel was updated to > kernel-4.17.7-

Re: F27->F28 no new kernel

On 07/31/2018 06:57 AM, Frank Elsner wrote: I've just upgraded my TP X230i from F27 to F28 painless. But I'm still on my last F27 kernel-4.16.16-200.fc27.i686+PAE. No newer kernel installed. During ame upgrade procedure on my TP x121e kernel was updated to kernel-4.17.7-100.fc27.i686+PAE. Both

F27->F28 no new kernel

Hello, I've just upgraded my TP X230i from F27 to F28 painless. But I'm still on my last F27 kernel-4.16.16-200.fc27.i686+PAE. No newer kernel installed. During ame upgrade procedure on my TP x121e kernel was updated to kernel-4.17.7-100.fc27.i686+PAE. Both systems are 32bit. What could prevent

Re: Stack clash and Fedora, new kernel vulnerability, from kernel list

On Tue, 20 Jun 2017 21:45:31 -0700 stan wrote: > On Tue, 20 Jun 2017 23:44:24 -0400 > Tony Nelson wrote: > > > It's not allocated memory. It's a Page Table Entry in the Kernel > > that ensures that no actual memory is mapped there and that the > > region is thus unreadable and unwritable. Thi

Re: Stack clash and Fedora, new kernel vulnerability, from kernel list

On Tue, 20 Jun 2017 23:44:24 -0400 Tony Nelson wrote: > It's not allocated memory. It's a Page Table Entry in the Kernel that > ensures that no actual memory is mapped there and that the region is > thus unreadable and unwritable. This is not unlike a swapped-out > page, except the Kernel Page

Re: Stack clash and Fedora, new kernel vulnerability, from kernel list

On 17-06-20 13:09:50, stan wrote: On Tue, 20 Jun 2017 12:20:57 -0400 Tom Horsley wrote: > That seems like it might be impossible without architecture changes > in the chips to allow bounds checking the stack pointer in hardware > (which certainly wouldn't fix any existing systems :-). I think

Re: Stack clash and Fedora, new kernel vulnerability, from kernel list

On Tue, 20 Jun 2017 17:08:09 +0100 Patrick O'Callaghan wrote: > Full details are in the report already cited, but briefly the fix > causes each page of the new stack frame to be probed to make sure it > doesn't overlap with the guard page (a write-protected page created to > prevent stack and hea

Re: Stack clash and Fedora, new kernel vulnerability, from kernel list

On Tue, 20 Jun 2017 12:20:57 -0400 Tom Horsley wrote: > That seems like it might be impossible without architecture changes > in the chips to allow bounds checking the stack pointer in hardware > (which certainly wouldn't fix any existing systems :-). I think the kernel fix was the first solutio

Re: Stack clash and Fedora, new kernel vulnerability, from kernel list

On Tue, 2017-06-20 at 12:20 -0400, Tom Horsley wrote: > On Tue, 20 Jun 2017 08:42:39 -0700 > stan wrote: > > > My > > assumption was that this was adding the strong stack protection to the > > kernel side of things. > > That seems like it might be impossible without architecture changes > in the

Re: Stack clash and Fedora, new kernel vulnerability, from kernel list

On Tue, 20 Jun 2017 08:42:39 -0700 stan wrote: > My > assumption was that this was adding the strong stack protection to the > kernel side of things. That seems like it might be impossible without architecture changes in the chips to allow bounds checking the stack pointer in hardware (which cert

  1   2   3   4   >