On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
> And you should still try suggestion #2 because it's very likely to only affect
> one specific configuration.
Thanks, I did that just now. Took another, but didn't give me any more
data to go by. Getting set up for bisecting and doing real work on t
On Sunday, August 30, 2015 6:11:00 PM Fernando Rodriguez wrote:
> On Sunday, August 30, 2015 10:51:57 PM Peter Weilbacher wrote:
> > Hi Fernando,
> >
> > On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
> >
> > > 1. Add loglevel=7 to your kernel parameters and see what it prints
before
> it
> > >
On Sunday, August 30, 2015 10:51:57 PM Peter Weilbacher wrote:
> Hi Fernando,
>
> On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
>
> > 1. Add loglevel=7 to your kernel parameters and see what it prints before
it
> > hangs.
>
> That helped, it showed me something about drm, so...
>
> > 3. From
Hi Fernando,
On Sun, 30 Aug 2015, Fernando Rodriguez wrote:
> 1. Add loglevel=7 to your kernel parameters and see what it prints before it
> hangs.
That helped, it showed me something about drm, so...
> 3. From your kernel parameters I assume you're using the radeon free driver
> right? If that
On Tuesday, August 25, 2015 6:40:01 PM Peter Weilbacher wrote:
> Hi Alexander,
>
> On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
>
> > On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
wrote:
> > >
> > > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> > > upgraded to 4.
On Sat, 29 Aug 2015, Alexander Kapshuk wrote:
> You probably did look into this yourself, but did you double-check
> your /etc/lilo.conf? Is everything fine there?
At least it's identical between 4.0.5 and 4.1.6:
image=/boot/kernel-genkernel-x86_64-4.0.5
label=Linux405
read-only # read-onl
On Sat, Aug 29, 2015 at 3:09 PM, Peter Weilbacher
wrote:
> On Tue, 25 Aug 2015, Alexander Kapshuk wrote:
>
>> I've never experienced this particular kernel trouble myself, so I'm
>> not sure if my input would be of much help.
>> Here's what the kernel documentation has to say about this kind of is
On Tue, 25 Aug 2015, Alexander Kapshuk wrote:
> I've never experienced this particular kernel trouble myself, so I'm
> not sure if my input would be of much help.
> Here's what the kernel documentation has to say about this kind of issue:
>
> /usr/src/linux/Documentation/RCU/stallwarn.txt:29,33
[.
On Tue, Aug 25, 2015 at 7:40 PM, Peter Weilbacher
wrote:
> Hi Alexander,
>
> On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
>
>> On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
>> wrote:
>> >
>> > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
>> > upgraded to 4.1.5 last
Hi Alexander,
On Sun, 23 Aug 2015, Alexander Kapshuk wrote:
> On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
> wrote:
> >
> > after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> > upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
> > them. On the scree
On Sun, Aug 23, 2015 at 4:08 PM, Peter Weilbacher
wrote:
> Dear all,
>
> after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
> upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
> them. On the screen I see
>
>Decompressing Linux... Parsing ELF... done.
>
Dear all,
after successfully using kernel 4.0.5 (vanilla-sources) for a while, I
upgraded to 4.1.5 last week and 4.1.6 today. I cannot boot either of
them. On the screen I see
Decompressing Linux... Parsing ELF... done.
Booting the kernel.
as the last thing, then it just sits there.
To up
On Thursday 29 July 2010 12:39:46 I wrote:
> On Wednesday 28 July 2010 19:14:05 Bill Longman wrote:
> > In the Device Drivers section, (this is for 2.6.34!), turn OFF the
> > deprecated ATA/ATAPI/MFM/RLL support. That corresponds to
> > CONFIG_IDE in your .config. Then, turn ON, Serial ATA and Para
On Wednesday 28 July 2010 19:14:05 Bill Longman wrote:
> In the Device Drivers section, (this is for 2.6.34!), turn OFF the
> deprecated ATA/ATAPI/MFM/RLL support. That corresponds to CONFIG_IDE
> in your .config. Then, turn ON, Serial ATA and Parallel ATA drivers
> which corresponds to CONFIG_ATA
On 07/28/2010 11:54 AM, Mick wrote:
> On Wednesday 28 July 2010 17:35:44 KH wrote:
>> Am 28.07.2010 17:30, schrieb Bill Longman:
>>> On 07/28/2010 08:18 AM, KH wrote:
Hi Mick,
but typing ls /dev/hd* or ls /dev/sd* should show up something.
Shouldn't it? df -h shows /dev/hda3 is
On Wednesday 28 July 2010 17:35:44 KH wrote:
> Am 28.07.2010 17:30, schrieb Bill Longman:
> > On 07/28/2010 08:18 AM, KH wrote:
> >> Hi Mick,
> >>
> >> but typing ls /dev/hd* or ls /dev/sd* should show up something.
> >> Shouldn't it? df -h shows /dev/hda3 is mounted on /
> >> For me this is stran
On 07/28/2010 09:37 AM, KH wrote:
> Am 28.07.2010 17:27, schrieb Bill Longman:
>> On 07/28/2010 07:56 AM, KH wrote:
>>> Am 28.07.2010 15:45, schrieb Bill Longman:
Konstantin, please post what your kernel has for IDE support. If you
have /proc/config.gz, then please post the results f
Am 28.07.2010 17:27, schrieb Bill Longman:
> On 07/28/2010 07:56 AM, KH wrote:
>> Am 28.07.2010 15:45, schrieb Bill Longman:
>>>
>>> Konstantin, please post what your kernel has for IDE support. If you
>>> have /proc/config.gz, then please post the results from "zgrep IDE
>>> /proc/config.gz" so we
Am 28.07.2010 17:30, schrieb Bill Longman:
> On 07/28/2010 08:18 AM, KH wrote:
>>
>> Hi Mick,
>>
>> but typing ls /dev/hd* or ls /dev/sd* should show up something.
>> Shouldn't it? df -h shows /dev/hda3 is mounted on /
>> For me this is strange.
>
> How is /dev mounted right now? What does "udevad
On 07/28/2010 08:18 AM, KH wrote:
> Am 28.07.2010 16:04, schrieb Mick:
>> On 28 July 2010 14:53, Bill Longman wrote:
>>> On 07/28/2010 06:42 AM, Mick wrote:
On 28 July 2010 09:50, KH wrote:
> I installed grub by connecting the hdd to my workstation. This did not
> change anythin
On 07/28/2010 07:56 AM, KH wrote:
> Am 28.07.2010 15:45, schrieb Bill Longman:
>> On 07/28/2010 01:50 AM, KH wrote:
>>>
>>> Hi,
>>>
>>> I installed grub by connecting the hdd to my workstation. This did not
>>> change anything.
>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The
Am 28.07.2010 15:53, schrieb Bill Longman:
> On 07/28/2010 06:42 AM, Mick wrote:
>> On 28 July 2010 09:50, KH wrote:
>>
>>> I installed grub by connecting the hdd to my workstation. This did not
>>> change anything.
>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>> boo
Am 28.07.2010 16:04, schrieb Mick:
> On 28 July 2010 14:53, Bill Longman wrote:
>> On 07/28/2010 06:42 AM, Mick wrote:
>>> On 28 July 2010 09:50, KH wrote:
>>>
I installed grub by connecting the hdd to my workstation. This did not
change anything.
Also I changed /etc/fstab . Now I
On 28 July 2010 15:27, Bill Longman wrote:
> On 07/28/2010 07:04 AM, Mick wrote:
>> On 28 July 2010 14:53, Bill Longman wrote:
>>> On 07/28/2010 06:42 AM, Mick wrote:
On 28 July 2010 09:50, KH wrote:
> I installed grub by connecting the hdd to my workstation. This did not
> cha
Am 28.07.2010 15:45, schrieb Bill Longman:
> On 07/28/2010 01:50 AM, KH wrote:
>>
>> Hi,
>>
>> I installed grub by connecting the hdd to my workstation. This did not
>> change anything.
>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>> boots fine now. I can use it but ...
On 07/28/2010 07:04 AM, Mick wrote:
> On 28 July 2010 14:53, Bill Longman wrote:
>> On 07/28/2010 06:42 AM, Mick wrote:
>>> On 28 July 2010 09:50, KH wrote:
>>>
I installed grub by connecting the hdd to my workstation. This did not
change anything.
Also I changed /etc/fstab . Now I
On 28 July 2010 14:53, Bill Longman wrote:
> On 07/28/2010 06:42 AM, Mick wrote:
>> On 28 July 2010 09:50, KH wrote:
>>
>>> I installed grub by connecting the hdd to my workstation. This did not
>>> change anything.
>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>> bo
On 07/28/2010 06:42 AM, Mick wrote:
> On 28 July 2010 09:50, KH wrote:
>
>> I installed grub by connecting the hdd to my workstation. This did not
>> change anything.
>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>> boots fine now. I can use it but ... There is no /dev
On 07/28/2010 01:50 AM, KH wrote:
> Am 25.07.2010 15:57, schrieb Mick:
>> On Sunday 25 July 2010 09:18:33 Dale wrote:
>>> Alan McKinnon wrote:
On Sunday 25 July 2010 06:57:43 KH wrote:
>> You said you ran e2fsck and it was OK. What was the command?
>>
>>
>>
>> Normally with
On 28 July 2010 09:50, KH wrote:
> I installed grub by connecting the hdd to my workstation. This did not
> change anything.
> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
> boots fine now. I can use it but ... There is no /dev/hd* . Running
> mount /boot I get the answe
Am 25.07.2010 15:57, schrieb Mick:
> On Sunday 25 July 2010 09:18:33 Dale wrote:
>> Alan McKinnon wrote:
>>> On Sunday 25 July 2010 06:57:43 KH wrote:
> You said you ran e2fsck and it was OK. What was the command?
>
>
>
> Normally with an e2fsck on a journalled fs, the app will
On Monday 26 July 2010 21:46:40 Mick wrote:
> On Monday 26 July 2010 19:04:16 Alex Schuster wrote:
> > Isn't there also some other SCSI stuff (which does not get selected
> > automatically), necessary to make the new ATA drivers actually
> > work?
>
> You mean:
>
> Device Drivers --->
> Generic
On Monday 26 July 2010 19:04:16 Alex Schuster wrote:
> Peter Humphrey writes:
> > On Monday 26 July 2010 16:13:19 Mick wrote:
> > > On 26 July 2010 15:11, Peter Humphrey
> > >
> > > wrote:
> > > > So udev is wrong in saying CONFIG_IDE should not be set - on that
> > > > old P4 box it has to be to
Peter Humphrey writes:
> On Monday 26 July 2010 16:13:19 Mick wrote:
> > On 26 July 2010 15:11, Peter Humphrey
> > wrote:
> > > So udev is wrong in saying CONFIG_IDE should not be set - on that
> > > old P4 box it has to be to get ICH4 drivers.
> >
> > Hmm, did you try ATA_PIIX, or PATA_MPIIX, o
On Monday 26 July 2010 16:13:19 Mick wrote:
> On 26 July 2010 15:11, Peter Humphrey
wrote:
> > So udev is wrong in saying CONFIG_IDE should not be set - on that
> > old P4 box it has to be to get ICH4 drivers.
>
> Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH?
I've just tried it again n
On 26 July 2010 15:11, Peter Humphrey wrote:
> On Monday 26 July 2010 12:02:56 Mick wrote:
>
>> Another gotcha is when you disable the deprecated CONFIG_IDE in the
>> kernel and you don't update your grub.conf and /etc/fstab to rename
>> /dev/hda's into /dev/sda's.
>
> Drifting off topic somewhat,
William Kenworthy wrote:
Might be time for a new setup - amd athlon 2500+ are not so cool these
days :)
BillK
Mine still works well. Just have to blow out the dust every month or so.
Dale
:-) :-)
On Monday 26 July 2010 12:02:56 Mick wrote:
> Another gotcha is when you disable the deprecated CONFIG_IDE in the
> kernel and you don't update your grub.conf and /etc/fstab to rename
> /dev/hda's into /dev/sda's.
Drifting off topic somewhat, when I upgraded udev on my firewall box last
week I w
On 26 July 2010 11:54, William Kenworthy wrote:
> Fixed it - was grub after all - it renumbered my drives (0 and 1
> swapped :(
>
> Complicated because this was one of the early sata boards with a fake
> raid chip to handle the sata while the old IDE drives were on the normal
> bus.
>
> Further c
On Mon, 2010-07-26 at 09:05 +0800, Bill Kenworthy wrote:
> On Sun, 2010-07-25 at 22:08 +0200, Alan McKinnon wrote:
> > On Sunday 25 July 2010 10:18:33 Dale wrote:
> > > Alan McKinnon wrote:
> >
> > [snip]
> >
> > > > When done, reboot as normal and see if the machine boots up properly.
> > >
> >
On Sun, 2010-07-25 at 22:08 +0200, Alan McKinnon wrote:
> On Sunday 25 July 2010 10:18:33 Dale wrote:
> > Alan McKinnon wrote:
>
> [snip]
>
> > > When done, reboot as normal and see if the machine boots up properly.
> >
> > And I would stand guard to make sure housekeeping doesn't come around.
>
On Sunday 25 July 2010 17:24:46 cov...@ccs.covici.com wrote:
> > > When done, reboot as normal and see if the machine boots up properly.
> > >
> > >
> >
> >
> >
> > And I would stand guard to make sure housekeeping doesn't come around.
> > ;-) Cutting power during all this wold not be good.
>
On Sunday 25 July 2010 10:18:33 Dale wrote:
> Alan McKinnon wrote:
[snip]
> > When done, reboot as normal and see if the machine boots up properly.
>
> And I would stand guard to make sure housekeeping doesn't come around.
> ;-) Cutting power during all this wold not be good.
Here in Africa we
Dale wrote:
> Alan McKinnon wrote:
> > On Sunday 25 July 2010 06:57:43 KH wrote:
> >
> >>> You said you ran e2fsck and it was OK. What was the command?
> >>>
> >>>
> >>>
> >>> Normally with an e2fsck on a journalled fs, the app will replay the
> >>> journal and make a few minor checks. This
On Sunday 25 July 2010 09:18:33 Dale wrote:
> Alan McKinnon wrote:
> > On Sunday 25 July 2010 06:57:43 KH wrote:
> >>> You said you ran e2fsck and it was OK. What was the command?
> >>>
> >>>
> >>>
> >>> Normally with an e2fsck on a journalled fs, the app will replay the
> >>> journal and make
Alan McKinnon wrote:
On Sunday 25 July 2010 06:57:43 KH wrote:
You said you ran e2fsck and it was OK. What was the command?
Normally with an e2fsck on a journalled fs, the app will replay the
journal and make a few minor checks. This takes about 4 seconds, not
the 40 minutes it takes to
On Sunday 25 July 2010 06:57:43 KH wrote:
> > You said you ran e2fsck and it was OK. What was the command?
> >
> >
> >
> > Normally with an e2fsck on a journalled fs, the app will replay the
> > journal and make a few minor checks. This takes about 4 seconds, not
> > the 40 minutes it takes to do
Am 24.07.2010 23:46, schrieb James Wall:
> On 7/24/2010 3:25 PM, Alan McKinnon wrote:
>>
>> I think you might need to fsck without the journal. I know there's a
>> way to do
>> this but a cursory glance at the man page didn't reveal it. Maybe an
>> ext user
>> will chip in with the correct method
>
Am 24.07.2010 22:21, schrieb Alan McKinnon:
> On Saturday 24 July 2010 21:57:38 KH wrote:
>> Hi there,
[...]
>> Anyway the box won't boot anymore. grub starts up. Kernel boots. Then
>> there is checking root file system (or something like that).The message
>> is that my ext2 file system can not be
On Sat, Jul 24, 2010 at 9:21 PM, Alan McKinnon wrote:
> I think you might need to fsck without the journal. I know there's a way to do
> this but a cursory glance at the man page didn't reveal it. Maybe an ext user
> will chip in with the correct method
"e2fsck -f" should run the full system chec
On 7/24/2010 3:25 PM, Alan McKinnon wrote:
On Saturday 24 July 2010 21:57:38 KH wrote:
Hi there,
my server was running strait for 8 month now. I did updates regularly
but still used an 2.6.2x kernel. Never switched it of. Now someone from
houskeeping pulled the plug for the vacuum cleaner ...
On Saturday 24 July 2010 21:57:38 KH wrote:
> Hi there,
>
> my server was running strait for 8 month now. I did updates regularly
> but still used an 2.6.2x kernel. Never switched it of. Now someone from
> houskeeping pulled the plug for the vacuum cleaner ...
>
> Anyway the box won't boot anymor
On Saturday 24 July 2010 21:57:38 KH wrote:
> Hi there,
>
> my server was running strait for 8 month now. I did updates regularly
> but still used an 2.6.2x kernel. Never switched it of. Now someone from
> houskeeping pulled the plug for the vacuum cleaner ...
>
> Anyway the box won't boot anymor
Hi there,
my server was running strait for 8 month now. I did updates regularly
but still used an 2.6.2x kernel. Never switched it of. Now someone from
houskeeping pulled the plug for the vacuum cleaner ...
Anyway the box won't boot anymore. grub starts up. Kernel boots. Then
there is checking ro
Something very similar happened to me. baselayout-1.12.0_pre1-r1 was emerged
in the past day or two, and the next time I rebooted, it hung up on what at
first seemed to be having issues loading alsa. The boot did get into runlevel
3, so I was able to get in remotely and mess around. After prunin
Rumen Yotov wrote:
[EMAIL PROTECTED] wrote:
I'm ~x86 on a dell laptop.
I'm having some fun this morning. Everything was working this
morning, but I shut down the system for my daily commute and now it
won't boot. I seem to
Hi,
As there are problems with latest baselayout (2-3 persons) on
[EMAIL PROTECTED] wrote:
I'm ~x86 on a dell laptop.
I'm having some fun this morning. Everything was working this morning, but I
shut down the system for my daily commute and now it won't boot. I seem to
remember a few gnome emerges last night, but everything emerged cleanly and ran
etc-upda
I'm ~x86 on a dell laptop.
I'm having some fun this morning. Everything was working this morning, but I
shut down the system for my daily commute and now it won't boot. I seem to
remember a few gnome emerges last night, but everything emerged cleanly and ran
etc-update.
I have some failing in
hi everybody,
i'm a new gentoo user and i encountered following problem:
my computer is amd64 on abit ax8 mobo, installation started at stage2. i
put root on mirrored sata (raid1) disks. kernel compiled ok, i performed
all steps described in the installation guide with the modifications
describe
59 matches
Mail list logo
