On Tue, May 08, 2018 at 12:04:58PM -0700, Samuel Sieb wrote:
> On 05/03/2018 06:35 PM, Jim Simmons wrote:
> >In journalctl, I see this and I think it is the problem:
> >
> >WARNING: PV W0e1Cx-ByMA-iRX6-OGxr-KfWC-zaUP-YXWgW5 on /dev/sdb8 was
> >already found on sda8.
> >WARNING: PV W0e1C
On 05/03/2018 06:35 PM, Jim Simmons wrote:
In journalctl, I see this and I think it is the problem:
WARNING: PV W0e1Cx-ByMA-iRX6-OGxr-KfWC-zaUP-YXWgW5 on /dev/sdb8 was
already found on sda8.
WARNING: PV W0e1Cx-ByMA-iRX6-OGxr-KfWC-zaUP-YXWgW5 on /dev/md127 was
already found on sda
Hi,
On 04-05-18 01:36, Jim Simmons wrote:
On Thu, May 03, 2018 at 01:36:43PM -0700, Samuel Sieb wrote:
On 05/03/2018 01:07 PM, Joe Zeff wrote:
On 05/03/2018 12:46 PM, Samuel Sieb wrote:
Ok, so using the F27 installed kernel works on F28.
What else would you expect? The kernel doesn't care
On Thu, May 03, 2018 at 04:45:03PM -0700, Samuel Sieb wrote:
...
> Try installing "dracut-config-generic" and then reinstall the F28
> kernel. Make sure that the initramfs timestamp is updated. The
> file should also be larger after. If it still doesn't work, then
> removing "quiet" and "rhgb" f
On 05/03/2018 04:36 PM, Jim Simmons wrote:
I'm pretty sure it is dracut. Installing the normal kernel from
Fedora 27 and it won't boot either. I saw dracut complaining about
not finding busybox and biosdevname so I installed them and
reinstalled the kernel - same results. I also get a couple o
On Thu, May 03, 2018 at 01:36:43PM -0700, Samuel Sieb wrote:
> On 05/03/2018 01:07 PM, Joe Zeff wrote:
> >On 05/03/2018 12:46 PM, Samuel Sieb wrote:
> >>Ok, so using the F27 installed kernel works on F28.
> >
> >What else would you expect? The kernel doesn't care what version
> >of Fedora you're r
On 05/03/2018 01:07 PM, Joe Zeff wrote:
On 05/03/2018 12:46 PM, Samuel Sieb wrote:
Ok, so using the F27 installed kernel works on F28.
What else would you expect? The kernel doesn't care what version of
Fedora you're running. If it did, the upgrade would have removed the
F27 kernels.
Tha
On 05/03/2018 12:46 PM, Samuel Sieb wrote:
Ok, so using the F27 installed kernel works on F28.
What else would you expect? The kernel doesn't care what version of
Fedora you're running. If it did, the upgrade would have removed the
F27 kernels.
_
On 05/03/2018 02:43 AM, Jim Simmons wrote:
F28 only has the normal kernel - it doesn't seem to recognize
/dev/vg0/root correctly on a softraid mirrored volume for some strange
reason. The F27 PAE kernel does. I'm going to try the F27 "normal"
kernel and see if that works.
at happens between the two different types of kernel? Or is
> it something with F28 regardless of which kernel?
>
...
> As of F28, the PAE kernels have been discontinued.
F28 only has the normal kernel - it doesn't seem to recognize
/dev/vg0/root correctly on a softraid mirrored volum
;t critical and this system will be shutdown eventually
anyway, I just haven't been able to figure out what is going on yet.
I'll do some more experimenting and try to capture some logs - I was
just surprised that kernel-PAE was gone and I couldn't find any info
on why. Usually Fedora&
st haven't been able to figure out what is going on yet.
I'll do some more experimenting and try to capture some logs - I was
just surprised that kernel-PAE was gone and I couldn't find any info
on why. Usually Fedora's releases "just work" for me.
Thanks,
On 05/02/2018 03:26 AM, Jim Simmons wrote:
There don't appear to be any kernel-PAE* packages in the repos and I
don't see this mentioned anywhere in the docs I've found. Are they no
longer supported? A quick attempt at using the normal kernel didn't
work - the system we
On Wed, 2 May 2018 06:26:23 -0400
Jim Simmons wrote:
> I upgraded a 32-bit Fedora 27 system to Fedora 28 using the normal dnf
> upgrade procedure. The upgrade finished but the system is still
> running a Fedora 27 kernel.
>
> There don't appear to be any kernel-PAE* package
I upgraded a 32-bit Fedora 27 system to Fedora 28 using the normal dnf
upgrade procedure. The upgrade finished but the system is still
running a Fedora 27 kernel.
There don't appear to be any kernel-PAE* packages in the repos and I
don't see this mentioned anywhere in the docs I'
On Sun, Jul 26, 2015 at 9:11 AM, Patrick Dupre wrote:
> Hello,
>
> Where can I get the rpm package:
>
> kernel-PAE-3.19.5-100.fc20.i686 ?
Have you looked directly through koji?
http://koji.fedoraproject.org/koji/packageinfo?buildStart=50&packageID=8&buildOrder=-comple
Hello,
Where can I get the rpm package:
kernel-PAE-3.19.5-100.fc20.i686 ?
Thank
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Unive
Andre Robatino fedoraproject.org> writes:
> I noticed that with the latest F20 kernel update, the 3 packages
> NetworkManager-l2tp, kde-plasma-nm-l2tp, and xl2tpd were removed on a 32-bit
> PAE machine, but not on 64-bit or on 32-bit non-PAE. This turns out to be
> due to
I noticed that with the latest F20 kernel update, the 3 packages
NetworkManager-l2tp, kde-plasma-nm-l2tp, and xl2tpd were removed on a 32-bit
PAE machine, but not on 64-bit or on 32-bit non-PAE. This turns out to be
due to those packages depending on non-PAE kernel and kernel-modules-extra.
That
> > Yeah! This works:
> >
> > # mount.cifs //raptor/unix/FEDORA /raptor -o sec=ntlm
>
> Btw, for me, sec=ntlmssp and sec=ntlmv2 continue to work under all F18
> kernels stably released so far.
>
>
With AD authentication???
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe
gt; Mar 8 18:09:28 harrier kernel: [ 137.487899] Key type cifs.idmap
> >> registered
> >> Mar 8 18:09:28 harrier kernel: [ 138.043492] CIFS VFS: Send error in
> >> QFSUnixInfo = -95
> >> Mar 8 18:09:28 harrier kernel: [ 138.093133] CIFS VFS: cifs_read_super:
mount, no problem in kernel-PAE-3.7.9-205.fc18.i686
Try adding "sec=ntlm" to the mount options.
The error seen with recent kernels is usually "mount error(22): Invalid
argument" and adding the sec option fixes itso this may not be related.
Yeah! This works:
# mount.cifs /
On 03/09/13 08:32, Terry Polzin wrote:
> Bug 905929 -- nobody is interested in fixing it.
This was also discussed recently on the "test" list.
I don't happen to use windows shares all that often and the ones that I have
don't show the breakage that you and others are seeing. So, I don't have an
e cifs.idmap
> > registered
> > Mar 8 18:09:28 harrier kernel: [ 138.043492] CIFS VFS: Send error in
> > QFSUnixInfo = -95
> > Mar 8 18:09:28 harrier kernel: [ 138.093133] CIFS VFS: cifs_read_super:
> > get root inode failed
> >
> > Same mount, no problem in
super: get
> root inode failed
>
> Same mount, no problem in kernel-PAE-3.7.9-205.fc18.i686
Try adding "sec=ntlm" to the mount options.
The error seen with recent kernels is usually "mount error(22): Invalid
argument" and adding the sec option fixes itso thi
] Key type cifs.idmap
registered
Mar 8 18:09:28 harrier kernel: [ 138.043492] CIFS VFS: Send error in
QFSUnixInfo = -95
Mar 8 18:09:28 harrier kernel: [ 138.093133] CIFS VFS:
cifs_read_super: get root inode failed
Same mount, no problem in kernel-PAE-3.7.9-205.fc18.i686
--
Andreas M. Kirchwitz wrote:
> Freshly installed Fedora 16 for 32 bit (i686) from DVD on a Pentium 4
> with 1 GB RAM. Why does Fedora 16 installs a PAE kernel by default?
> Previous versions of Fedora (on that machine) did not install the
> PAE kernel but the regular one.
Does your Pe
Hello Fedora fans!
Freshly installed Fedora 16 for 32 bit (i686) from DVD on a Pentium 4
with 1 GB RAM. Why does Fedora 16 installs a PAE kernel by default?
Previous versions of Fedora (on that machine) did not install the
PAE kernel but the regular one.
I've seen people on th
On Sun, 2010-11-14 at 08:35 -0500, Lamar Owen wrote:
> On Saturday, November 13, 2010 07:51:17 pm Tom Horsley wrote:
> > I was finally getting around to tweaking my 32 bit fedora 14
> > partition when I noticed that I was running kernel,
> > not kernel-PAE.
>
>
On Saturday, November 13, 2010 07:51:17 pm Tom Horsley wrote:
> I was finally getting around to tweaking my 32 bit fedora 14
> partition when I noticed that I was running kernel,
> not kernel-PAE.
For what it's worth, my pre-upgraded F14 box pulled in the PAE kernel, but that
I was finally getting around to tweaking my 32 bit fedora 14
partition when I noticed that I was running kernel,
not kernel-PAE. PAE was previously the default. Did the
default change back to non-PAE, or did anaconda make
the wrong choice for my install? (I do have 8 gig
of memory, so I can use
Ed Greshko:
>> The fedora-l...@redhat.com address has been depreciated and using it
>> will forward to the fedoraproject address. Using the old redhat.com
>> address will lead to duplicate messages.
Bill Davidsen:
> Ed, it might be better to run down whatever adds that address to some posts
> th
Ed Greshko wrote:
> Please Do Not use the email address of fedora-l...@redhat.com for this list.
>
> Use only us...@lists.fedoraproject.org.
>
> The fedora-l...@redhat.com address has been depreciated and using it
> will forward to the fedoraproject address. Using the old redhat.com
> address will
On Sun, Oct 31, 2010 at 9:04 PM, Ed Greshko wrote:
> Please Do Not use the email address of fedora-l...@redhat.com for this list.
>
> Use only us...@lists.fedoraproject.org.
>
> The fedora-l...@redhat.com address has been depreciated and using it
> will forward to the fedoraproject address. Using
Please Do Not use the email address of fedora-l...@redhat.com for this list.
Use only us...@lists.fedoraproject.org.
The fedora-l...@redhat.com address has been depreciated and using it
will forward to the fedoraproject address. Using the old redhat.com
address will lead to duplicate messages.
On Sun, 31 Oct 2010, Patrick Dupre wrote:
> How am I update from "no pae" to PAE kenerl.
> Even setting DEFAULTKERNEL=kernel-PAE in /etc/sysconfig/kernel
> it is ignored by anaconda (from the DVD).
> How can I tell to the installer to use such option ?
>
> fedora 11,
Hello,
How am I update from "no pae" to PAE kenerl.
Even setting DEFAULTKERNEL=kernel-PAE in /etc/sysconfig/kernel
it is ignored by anaconda (from the DVD).
How can I tell to the installer to use such option ?
fedora 11, 12 or 1
On 10/27/2010 07:32 PM, eredicat...@hugedesigns.net wrote:
> On 10/28/2010 11:17 AM, JD wrote:
>> On 10/27/2010 06:03 PM, EredicatorX wrote:
>>
>>> Short version.
>>> OS: Fedora 13
>>> Kernel: 2.6.34.7-61.fc13.i686.PAE
>>> Hardware: L
On 10/28/2010 11:17 AM, JD wrote:
>On 10/27/2010 06:03 PM, EredicatorX wrote:
>
>> Short version.
>> OS: Fedora 13
>> Kernel: 2.6.34.7-61.fc13.i686.PAE
>> Hardware: Lenovo x100e
>> Problem:Trying to build drivers for realtec wireless lan.
>>
On 10/27/2010 06:03 PM, EredicatorX wrote:
>Short version.
> OS: Fedora 13
> Kernel: 2.6.34.7-61.fc13.i686.PAE
> Hardware: Lenovo x100e
> Problem:Trying to build drivers for realtec wireless lan.
>
> When I tried to build drivers initally with
> rtl8192se_linux_2.6.0
On Thu, Oct 28, 2010 at 12:03 PM, EredicatorX
wrote:
> Problem:Trying to build drivers for realtec wireless lan.
Not helpful for your building issue, but have you considered
installing kmod-staging package from RPMFusion?
yum install kmod-staging
depmod -a
modprobe r8192e_pci
-c
--
users maili
Short version.
OS: Fedora 13
Kernel: 2.6.34.7-61.fc13.i686.PAE
Hardware: Lenovo x100e
Problem:Trying to build drivers for realtec wireless lan.
When I tried to build drivers initally with
rtl8192se_linux_2.6.0018.1025.2010 every time I would try to load the
driver with modprobe it would error
t;>
> >>>> Sent: Aug 26, 2010 8:37 AM
> >>>> To: Fedora List
> >>>> Subject: 2.6.33.8-149.fc13.i686.PAE sleeps NOT
> >>>>
> >>>> The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up
> a
> >>>>
On 08/26/2010 01:28 PM, JD wrote:
> On 08/26/2010 09:29 AM, Geoffrey Leach wrote:
>
>> On 08/26/2010 09:06:33 AM, James Mckenzie wrote:
>>
>>> Geoffrey Leach wrote
>>>
>>>> Sent: Aug 26, 2010 8:37 AM
>>>> To: Fed
On 08/26/2010 02:18 PM, James Mckenzie wrote:
> JD wrote:
>> Sent: Aug 26, 2010 12:55 PM
>> To: Community support for Fedora users
>> Subject: Re: 2.6.33.8-149.fc13.i686.PAE sleeps NOT
>>
>> On 08/26/2010 09:34 AM, Geoffrey Leach wrote:
>>> On 08/26/
On 08/26/2010 09:02:31 AM, JD wrote:
> On 08/26/2010 08:37 AM, Geoffrey Leach wrote:
> > The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a
> few
> > seconds after being asked to sleep. 2.6.33.6-147.2.4.fc13.i686.PAE
> > does not have this problem. Has
On 08/26/2010 02:18 PM, James Mckenzie wrote:
> JD wrote:
>> Sent: Aug 26, 2010 12:55 PM
>> To: Community support for Fedora users
>> Subject: Re: 2.6.33.8-149.fc13.i686.PAE sleeps NOT
>>
>> On 08/26/2010 09:34 AM, Geoffrey Leach wrote:
>>> On 08/26/
On 08/26/2010 01:34 PM, Geoffrey Leach wrote:
> On 08/26/2010 12:55:46 PM, JD wrote:
>>On 08/26/2010 09:34 AM, Geoffrey Leach wrote:
>>> On 08/26/2010 09:02:31 AM, JD wrote:
>>>> On 08/26/2010 08:37 AM, Geoffrey Leach wrote:
>>>>> The newl
JD wrote:
>Sent: Aug 26, 2010 12:55 PM
>To: Community support for Fedora users
>Subject: Re: 2.6.33.8-149.fc13.i686.PAE sleeps NOT
>
> On 08/26/2010 09:34 AM, Geoffrey Leach wrote:
>> On 08/26/2010 09:02:31 AM, JD wrote:
>>>On 08/26/2010 08:37 AM, Geoffr
On 08/26/2010 12:55:46 PM, JD wrote:
> On 08/26/2010 09:34 AM, Geoffrey Leach wrote:
> > On 08/26/2010 09:02:31 AM, JD wrote:
> >>On 08/26/2010 08:37 AM, Geoffrey Leach wrote:
> >>> The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a
> >>
On 08/26/2010 10:17:33 AM, Greg Woods wrote:
> On Thu, 2010-08-26 at 08:37 -0700, Geoffrey Leach wrote:
> > The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a
> few
> > seconds after being asked to sleep.
>
> For the record, it works fine with this kern
On 08/26/2010 09:34 AM, Geoffrey Leach wrote:
> On 08/26/2010 09:02:31 AM, JD wrote:
>>On 08/26/2010 08:37 AM, Geoffrey Leach wrote:
>>> The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a
>> few
>>> seconds after being asked to sleep. 2.6.33
On 08/26/2010 09:29 AM, Geoffrey Leach wrote:
> On 08/26/2010 09:06:33 AM, James Mckenzie wrote:
>> Geoffrey Leach wrote
>>> Sent: Aug 26, 2010 8:37 AM
>>> To: Fedora List
>>> Subject: 2.6.33.8-149.fc13.i686.PAE sleeps NOT
>>>
>>> The newly
On Thu, 2010-08-26 at 08:37 -0700, Geoffrey Leach wrote:
> The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a few
> seconds after being asked to sleep.
For the record, it works fine with this kernel on my Dell E6410 (see the
thread on this system for all the fun I'
On 08/26/2010 09:02:31 AM, JD wrote:
> On 08/26/2010 08:37 AM, Geoffrey Leach wrote:
> > The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a
> few
> > seconds after being asked to sleep. 2.6.33.6-147.2.4.fc13.i686.PAE
> > does not have this problem. Has
On 08/26/2010 09:06:33 AM, James Mckenzie wrote:
> Geoffrey Leach wrote
> >Sent: Aug 26, 2010 8:37 AM
> >To: Fedora List
> >Subject: 2.6.33.8-149.fc13.i686.PAE sleeps NOT
> >
> >The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a
> few
>
Geoffrey Leach wrote
>Sent: Aug 26, 2010 8:37 AM
>To: Fedora List
>Subject: 2.6.33.8-149.fc13.i686.PAE sleeps NOT
>
>The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a few
>seconds after being asked to sleep. 2.6.33.6-147.2.4.fc13.i686.PAE
>does not h
On 08/26/2010 08:37 AM, Geoffrey Leach wrote:
> The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a few
> seconds after being asked to sleep. 2.6.33.6-147.2.4.fc13.i686.PAE
> does not have this problem. Has anyone experienced this? And perhaps
> discovered a solutio
The newly-released kernel, 2.6.33.8-149.fc13.i686.PAE, wakes up a few
seconds after being asked to sleep. 2.6.33.6-147.2.4.fc13.i686.PAE
does not have this problem. Has anyone experienced this? And perhaps
discovered a solution? (Bugzilla report against fc12 kernel for the
same problem was
Terry Barnaby wrote:
> Hi,
>
> For info, my systems have just been updated with the kernel
> 2.6.32.16-141.fc12.i686.PAE.
> This is causing problems on two of them that have ATI Radeon cards. There are
> occasional Kernel OOPS followed by very slow graphics.
What really pi
Hi,
For info, my systems have just been updated with the kernel
2.6.32.16-141.fc12.i686.PAE.
This is causing problems on two of them that have ATI Radeon cards. There are
occasional Kernel OOPS followed by very slow graphics.
The messages in /var/log/messages are:
Jul 15 16:15:50 beam kernel
On 06/01/2010 04:50 PM, Steven Stern wrote:
> When using the latest kernel, 2.6.33.5-112.fc13.i686.PAE, my machine
> crashes with the message
>
> Uhhuh. NMI received for unknown reason a0 on CPU 0.
> You have some hardware problem, likely on the PCI
> Dazed and confused, but
On 06/01/2010 02:50 PM, Steven Stern wrote:
> When using the latest kernel, 2.6.33.5-112.fc13.i686.PAE, my machine
> crashes with the message
>
> Uhhuh. NMI received for unknown reason a0 on CPU 0.
> You have some hardware problem, likely on the PCI
> Dazed and confused, but
When using the latest kernel, 2.6.33.5-112.fc13.i686.PAE, my machine
crashes with the message
Uhhuh. NMI received for unknown reason a0 on CPU 0.
You have some hardware problem, likely on the PCI
Dazed and confused, but trying to continue
And then it sits for a while and quietly digs itself a
On Sun, 2010-05-30 at 14:47 -0500, Steven Stern wrote:
> Try 'yum install kernel-PAE-devel'.
I had looked for kernel-PAE-devel in the gnome packagekit application,
it wasn't there. Yum found it. I have no idea why the packagekit
application didn't show it - but now that i
ules/2.6.33.4-95.fc13.i686.PAE there is a "build" symlink
> that links to /usr/src/kernels/2.6.33.4-95.fc13.i686.PAE - but that
> directory does not exist!
>
> What *does* exist is /usr/src/kernels/2.6.33.4-95.fc13.i686 (note that
> the .PAE extension is missing).
>
> I
I am trying to build the VirtualBox kernel module. It fails with this
error:
Makefile:159: *** Error: unable to find the sources of your current
Linux kernel. Specify KERN_DIR= and run Make again. Stop.
In /lib/modules/2.6.33.4-95.fc13.i686.PAE there is a "build" symlink
that links t
On Sat, 2010-04-10 at 10:08 -0400, Brian C. Huffman wrote:
> Kernel 2.6.32.11-99.fc12.i686.PAE causes my graphical desktop to come to
> a crawl. When I click on an item - menu, window border (to move), NM
> applet, it can take up to 3 seconds for response.
>
> I had to go back
Kernel 2.6.32.11-99.fc12.i686.PAE causes my graphical desktop to come to
a crawl. When I click on an item - menu, window border (to move), NM
applet, it can take up to 3 seconds for response.
I had to go back to the previous kernel (actually, two back b/c the last
one destroys my login after
69 matches
Mail list logo
