On 01/12/2013 11:28 PM, Dave Reisner wrote:
...
Because mkinitcpio never created anything on upgrade or downgrade. The
initramfs image in /boot remained consistent with your 3.7.1 kernel.
Duh, that makes perfect sense ...
On Sat, Jan 12, 2013 at 11:19:17PM -0500, Genes Lists wrote:
> On 01/12/2013 11:09 PM, Dave Reisner wrote:
>
> >
> >mkinitcpio didn't generate a valid initramfs for the kernel... you can't
> >boot an ARCH kernel without an initramfs. Nothing is wrong with 3.7.2.
> >
>
> Was hoping you'd say that
On 01/12/2013 11:19 PM, Genes Lists wrote:
...
I will re-install 3.7.2 and try again!
Confirmed - 3.7.2 is booting and happily running .. Changed subject
line for clarity
thanks again for your help ... and sorry I missed the file-5.11
downgrade ...
On 01/12/2013 11:09 PM, Dave Reisner wrote:
mkinitcpio didn't generate a valid initramfs for the kernel... you can't
boot an ARCH kernel without an initramfs. Nothing is wrong with 3.7.2.
Was hoping you'd say that :-) Tho now am a tiny bit puzzled that the
initramfs created when I installe
On Sat, Jan 12, 2013 at 10:58:01PM -0500, Genes Lists wrote:
> On 01/12/2013 10:50 PM, Dave Reisner wrote:
>
> >
> > There's nothing wrong with the kernel. You've probably been ignoring the
> > warnings from pacman about file being newer than what's in the repos.
> > file-5.12 was removed from [t
On 01/12/2013 10:50 PM, Dave Reisner wrote:
>
> There's nothing wrong with the kernel. You've probably been ignoring the
> warnings from pacman about file being newer than what's in the repos.
> file-5.12 was removed from [testing] because it was misidentifying
> kernel images, which broke mkinit
On Sat, Jan 12, 2013 at 10:47:09PM -0500, Genes Lists wrote:
> On 01/12/2013 10:38 PM, Genes Lists wrote:
>
> Followup to my own post -
>
>(1) in spite of errors, 3.7.1 kernel seems to have been installed
> and the laptop once again boots.
>
>
>
>(2) I still don't understand th
On 01/12/2013 10:38 PM, Genes Lists wrote:
Followup to my own post -
(1) in spite of errors, 3.7.1 kernel seems to have been installed
and the laptop once again boots.
(2) I still don't understand the errors from mkinitcpio that
happened when installing linux in the chroot
Using testing repos - was fully updated and all working fine. Then
picked up the latest 3.7.2-1 kernel along with kdebase 4.9.5-2/
Rebooting after this latest update fails - it cannot find the
root device and drops to "recovery shell".
ls /dev/sdb1 (the usual root device)
On Sat, 12 Jan 2013 20:35:42 +
"P .NIKOLIC" wrote:
>
> Hi .
>
> Just had to completely rebuild the system using the latest ISO .
>
> I am now getting CPU usage of 100% on 1 core
>
> 143 root 20 0 721m 131m 22m R 00.0 2.1 16:30.31 systemd-journal is
> the line from top
>
> systemd
On 31.12.2012 11:00, Rodrigo Rivas wrote:
> On Mon, Dec 31, 2012 at 8:37 AM, Christoph Vigano wrote:
>
>>
>> How can I tell mkinitcpio to include a custom udev rule? Do I need to
>> write a hook for that? How can a hook for this look like?
>
>
> AFAIK, using FILES="path-to-udev-rule-file" shoul
Hi .
Just had to completely rebuild the system using the latest ISO .
I am now getting CPU usage of 100% on 1 core
143 root 20 0 721m 131m 22m R 00.0 2.1 16:30.31 systemd-journal is
the line from top
systemd version 196-2 all the latest updates .
Journal --verify reports file corrupt
On 2013-01-12 at 08:35 +1000, Allan McRae wrote:
> On 12/01/13 08:16, Evangelos Foutras wrote:
> > At least three bugs on our bug tracker can be solved by
> > making relevant truetype font packages provide 'ttf-font':
> > (...)
>
> Makes sense to me.
If you are a bit on the pedantic side the name
13 matches
Mail list logo
