On Sun, 26 Jun 2016, Peter Baranyi wrote:
> >> when I turn on my desktop computer (i5 Skylake) with Debian testing,
Ensure you are using the latest BIOS/UEFI. Skylake systems with an old
BIOS are unsupportable and broken. This is always the first thing to
verify when any Skylake-based system beh
Dnia 2016-06-26, nie o godzinie 16:49 +0200, Peter Baranyi pisze:
> thanks, I disabled quiet, I'll check the messages.
>
> It is a new machine, 1-2 months old.
>
> On 23 June 2016 at 21:57, Norbert Kiszka wrote:
> > Dnia 2016-06-23, czw o godzinie 09:14 +0200, Peter Baranyi pisze:
> >> hi,
> >>
thanks, I disabled quiet, I'll check the messages.
It is a new machine, 1-2 months old.
On 23 June 2016 at 21:57, Norbert Kiszka wrote:
> Dnia 2016-06-23, czw o godzinie 09:14 +0200, Peter Baranyi pisze:
>> hi,
>>
>> when I turn on my desktop computer (i5 Skylake) with Debian testing,
>> on the
Dnia 2016-06-23, czw o godzinie 09:14 +0200, Peter Baranyi pisze:
> hi,
>
> when I turn on my desktop computer (i5 Skylake) with Debian testing,
> on the first try it always freezes right after the grub menu. Then
> when I press reset, it always boots correctly. I have one SATA SSD (/,
> /home), o
On Thu, 2016-06-23 at 09:14 +0200, Peter Baranyi wrote:
> hi,
>
> when I turn on my desktop computer (i5 Skylake) with Debian testing,
> on the first try it always freezes right after the grub menu. Then
> when I press reset, it always boots correctly. I have one SATA SSD
> (/,
> /home), one SATA
Nevermind, fixed.
Changed initramfs MODULES=dep to MODULES=most and it boots now.
/etc/initramfs-tools/conf.d/driver-policy
# Driver inclusion policy selected during installation
# Note: this setting overrides the value set in the file
# /etc/initramfs-tools/initramfs.conf
MODULES=most
Seems lik
On Wed, 25 Jan 2012, Marc Auslander wrote:
To update files that must be correct, one can write a new version,
sync, and then use mv to replace the old with the new version.
The only way to easily do that seems to always call any editor via a script
doing that.
The journal_data option pro
Pierre Frenkiel writes:
> On Tue, 24 Jan 2012, Pierre Frenkiel wrote:
>
>Remains the question "how /etc/modprobe.d/options was corrupted"
>May-be after a power failure, but I thought that this couldn't
>happen with a ext4 file system.
>
The default/normal configuration of ext4 journa
On Tue, 24 Jan 2012, Pierre Frenkiel wrote:
But may-be /etc/modprobe/options is used at kernel upgrade to create
the initrd image. That would explain why the same error occured with
my 2 kernels.
Running dpkg-reconfigure, I checked that this is true
Remains the question "how /etc/modp
On 24/01/12 23:30, Michael Lange wrote:
> Hi,
>
> Thus spoketh Pierre Frenkiel
> unto us on Tue, 24 Jan 2012 13:03:19 +0100 (CET):
>
> (...)
>> ===
>> [3.903186] scsi_mod: '20a' invalid for parameter 'inq_timeout'
>> done
On Tue, 24 Jan 2012, Brian wrote:
GRUB_CMDLINE_LINUX="scsi_mod.inq_timeout=20"
That works. I checked that the value in grub.cfg has precedence, as expected,
over the value in initrd.
It'a a precious help in cas of boot problems.
--
Pierre Frenkiel
--
To UNSUBSCRIBE, email to debian-user-
On Tue 24 Jan 2012 at 18:24:29 +0100, Pierre Frenkiel wrote:
> the quesion is: what to put after GRUB_CMDLINE_LINUX= ?
GRUB_CMDLINE_LINUX="scsi_mod.inq_timeout=20"
Then 'update-grub'.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble?
On Tue, 24 Jan 2012, Brian wrote:
You may already have thought of it but checking the same file on your
system is worthwhile, otherwise the problem may occur again with the
next kernel upgrade.
According all the tests I made /etc/modprobe/options is rewritten by
initrd: just replacing 20a
On Tue, 24 Jan 2012, Brian wrote:
'scsi_mod.inq_timeout=20a' passed to the kernel causes the same behaviour
here too. The parameter should be an integer, of course.
That is obvious, but what is not obvious is where this 20a comes
from! that looks like a bug in the kernel upgrade procedure
On Tue 24 Jan 2012 at 15:02:48 +0100, Pierre Frenkiel wrote:
> hi Michael,
> Thank you for your quick answer.
> You were right: in the unpacked /etc/modprobe.d directory, the options file
> contained:
> options scsi_mod inq_timeout=20a
> After replacing 20a with 20, I rebuilt the in
On Tue 24 Jan 2012 at 13:30:08 +0100, Michael Lange wrote:
> so apparently it's the "20a" that is passed as 'inq_timeout' to scsi_mod
> that makes insmod scsi_mod fail and so the disk is not recognized.
'scsi_mod.inq_timeout=20a' passed to the kernel causes the same behaviour
here too. The parame
On Tue, 24 Jan 2012, Brian wrote:
Did these entries boot prior to yesterday?
hi Brian,
it was the first reboot after a kernel upgrade
it's fixed now (cf my previous post)
My understanding is that mails with attachments are not blocked. You
could try again in your next mail by attaching
On Tue, 24 Jan 2012, Michael Lange wrote:
If it is not grub, it must be something in the initrd; I would try to
unpack the initrd with
hi Michael,
Thank you for your quick answer.
You were right: in the unpacked /etc/modprobe.d directory, the options file
contained:
options scsi_m
On Tue 24 Jan 2012 at 13:03:19 +0100, Pierre Frenkiel wrote:
> I had yesterday a very big boot problem:
> after choosing any linux entry in the grub boot menu,
> I got failure messages, and was dropped to a busybox shell
Did these entries boot prior to yesterday?
> I sent a post 1 hour ago wi
Hi,
Thus spoketh Pierre Frenkiel
unto us on Tue, 24 Jan 2012 13:03:19 +0100 (CET):
(...)
> ===
> [3.903186] scsi_mod: '20a' invalid for parameter 'inq_timeout'
> done
> Gave up waiting for root device. Common problem
On Tue, 2012-01-03 at 08:53 -0600, hvw59601 wrote:
[...]
>
> I had a hang: blank screen w/o the "Loading..." message. Waited a few
> secs. and hit the reset button.
>
> Hugo
>
>
No messages at all?
My machine has now booted 3 times without issue since I disconnected the
IDE drives, the last
Steven wrote:
On Sun, 2012-01-01 at 19:02 -0600, hvw59601 wrote:
[...]
But shouldn't it fail all the time then?
Not if it's a race condition of some sorts, which is quote possible, see
below.
Since I turned off 'quiet' it
hasn't failed yet...
Mine has, just now, I had to reset, second tim
On Sun, 2012-01-01 at 19:02 -0600, hvw59601 wrote:
[...]
>
> But shouldn't it fail all the time then?
Not if it's a race condition of some sorts, which is quote possible, see
below.
> Since I turned off 'quiet' it
> hasn't failed yet...
Mine has, just now, I had to reset, second time I turned
Steven wrote:
On Sun, 2012-01-01 at 08:04 -0600, hvw59601 wrote:
[*snip*]
This is a desktop with an Asus
M4N98TD EVO mobo, 4GB mem, 4 HDD's. No messages anywhere about the hang.
I have an Asus as well, P8H67, but this also happened with the previous
board, a MSI P45 Diamond, but not until ove
On Sun, 2012-01-01 at 08:04 -0600, hvw59601 wrote:
[*snip*]
> This is a desktop with an Asus
> M4N98TD EVO mobo, 4GB mem, 4 HDD's. No messages anywhere about the hang.
I have an Asus as well, P8H67, but this also happened with the previous
board, a MSI P45 Diamond, but not until over a year afte
Steven wrote:
Hi list,
First of all Happy New Year.
I'm running Debian Wheezy and the past month I have this strange problem
when doing a cold boot. The system hangs right after the GRUB2 selection
menu, before any md raid arrays have been started.
After the GRUB2 selection menu the screen only
On Sun, 01 Jan 2012 14:09:30 +0100, Steven wrote:
> First of all Happy New Year.
Same to you :-)
> I'm running Debian Wheezy and the past month I have this strange problem
> when doing a cold boot. The system hangs right after the GRUB2 selection
> menu, before any md raid arrays have been start
Steven wrote:
Hi list,
First of all Happy New Year.
I'm running Debian Wheezy and the past month I have this strange problem
when doing a cold boot. The system hangs right after the GRUB2 selection
menu, before any md raid arrays have been started.
After the GRUB2 selection menu the screen only
On Mon, Jul 13, 2009 at 21:52, lee wrote:
> On Mon, Jul 13, 2009 at 12:04:12PM -0700, Kelly Clowers wrote:
>> On Mon, Jul 13, 2009 at 11:18, Raphael
>> Bossek wrote:
>> > My problem is "Resourse or device busy" at this moment within the initrd
>> > environment afer hparm -z reloaded the partitionta
On Mon, Jul 13, 2009 at 12:04:12PM -0700, Kelly Clowers wrote:
> On Mon, Jul 13, 2009 at 11:18, Raphael
> Bossek wrote:
> > My problem is "Resourse or device busy" at this moment within the initrd
> > environment afer hparm -z reloaded the partitiontable and udev created the
> > device node.
That
On Mon, Jul 13, 2009 at 19:13, Andrew Reid wrote:
> On Monday 13 July 2009 21:13:16 Kelly Clowers wrote:
>> On Mon, Jul 13, 2009 at 17:52, Kelly Clowers wrote:
>> > On Mon, Jul 13, 2009 at 16:38, Andrew Reid wrote:
>
>> >> The other way to investigate the initramfs, incidentally,
>> >> is to just
On Monday 13 July 2009 21:13:16 Kelly Clowers wrote:
> On Mon, Jul 13, 2009 at 17:52, Kelly Clowers wrote:
> > On Mon, Jul 13, 2009 at 16:38, Andrew Reid wrote:
> >> The other way to investigate the initramfs, incidentally,
> >> is to just unpack it somehwere -- it's a cpio archive, you
> >> can
>>> The other way to investigate the initramfs, incidentally,
>>> is to just unpack it somehwere -- it's a cpio archive, you
>>> can google for instructions.
>>
>> Also good to know.
>
> Going to try this now, since break= does not seem to work for
> some reason...
and when I use
zcat "" | ( whil
On Mon, Jul 13, 2009 at 17:52, Kelly Clowers wrote:
> On Mon, Jul 13, 2009 at 16:38, Andrew Reid wrote:
>> On Tuesday 07 July 2009 15:26:54 Kelly Clowers wrote:
>>
>>> Is there a way to get a shell inside the initramfs, to
>>> look around?
>>
>> You can boot with "break=mount" as a kernel option,
On Mon, Jul 13, 2009 at 16:38, Andrew Reid wrote:
> On Tuesday 07 July 2009 15:26:54 Kelly Clowers wrote:
>
>> Is there a way to get a shell inside the initramfs, to
>> look around?
>
> You can boot with "break=mount" as a kernel option, it
> will drop you into a busybox shell just before mounting
On Tuesday 07 July 2009 15:26:54 Kelly Clowers wrote:
> Is there a way to get a shell inside the initramfs, to
> look around?
You can boot with "break=mount" as a kernel option, it
will drop you into a busybox shell just before mounting
the root directory. The initramfs environment doesn't
in
On Mon, Jul 13, 2009 at 11:18, Raphael
Bossek wrote:
> Hi,
>
> I'm a little bit happy reading this because my Debian system fails form one
> day to another (after an upgrade of the linux kernel 2.6.26-2-686). I've
> started a discussion about my broblem already without any solution.
> It would be i
Hi,
I'm a little bit happy reading this because my Debian system fails form one
day to another (after an upgrade of the linux kernel 2.6.26-2-686). I've
started a discussion about my broblem already without any solution.
It would be interesting for me to know if you partitions are deteced stering
On Tue, Jul 7, 2009 at 12:26, Kelly Clowers wrote:
> 2009/7/7 Nuno Magalhães :
>>> Nothing has worked, any further ideas are welcome.
>>
>> I had this issue after upgrading from 2.6.29-1-amd64 to
>> 2.6.29-2-amd64, all i did was reboot using the -1-. Upgraded again and
>> now i'm using 2.6.30-1-amd
2009/7/7 Nuno Magalhães :
>> Nothing has worked, any further ideas are welcome.
>
> I had this issue after upgrading from 2.6.29-1-amd64 to
> 2.6.29-2-amd64, all i did was reboot using the -1-. Upgraded again and
> now i'm using 2.6.30-1-amd64 since the previous is also failing. If
> it's the same
> Nothing has worked, any further ideas are welcome.
I had this issue after upgrading from 2.6.29-1-amd64 to
2.6.29-2-amd64, all i did was reboot using the -1-. Upgraded again and
now i'm using 2.6.30-1-amd64 since the previous is also failing. If
it's the same problem it's not HD-related.
HTH
-
On Mon, Apr 13, 2009 at 08:36:29AM -0700, Vwaju wrote:
> Out of the blue, Debian failed to boot.
Did it complain about some file system inconsistency? fsck can help
only in these cases. Some details of the failure would help here.
> Using debian-live-500-i386-rescue.iso I mounted the root parti
On Sat, Apr 11, 2009 at 07:04:31AM +0200, Sven Joachim (svenj...@gmx.de) wrote:
> Running fsck is not necessarily a bad idea, but you should only run it
> on _unmounted_ filesystems.
Usually fsck is also safe with read-only mounts.
You can turn existing mount to read-only with
mount -o remount,ro
On 2009-04-11 04:35 +0200, Vwaju wrote:
> Out of the blue, Debian failed to boot.
>
> Using debian-live-500-i386-rescue.iso I mounted the root partition /
> dev/hda1.
>
> I would like to examine the partition to find the reason for the
> failure.
>
> I'm guessing I should use fsck. Is this right?
On Apr 10, 5:20 pm, Andrew Sackville-West
wrote:
> On Fri, Apr 10, 2009 at 06:12:22AM -0700, Vwaju wrote:
> > Out of the blue, Debian failed to boot.
>
> > I have loaded debian-live-500-i386-rescue.iso, and now I would like to
> > mount the boot partition /dev/hda1 and...oops, I can't mount /dev/h
On Friday 10 April 2009 22:13:56 Vwaju wrote:
> Out of the blue, Debian failed to boot.
>
> Using debian-live-500-i386-rescue.iso I mounted the root partition /
> dev/hda1.
>
> I would like to examine the partition to find the reason for the
> failure.
>
> I'm guessing I should use fsck. Is this r
On Fri, Apr 10, 2009 at 06:12:22AM -0700, Vwaju wrote:
> Out of the blue, Debian failed to boot.
>
> I have loaded debian-live-500-i386-rescue.iso, and now I would like to
> mount the boot partition /dev/hda1 and...oops, I can't mount /dev/hda1
> without root permission, and I can't get root permi
Dan Davison wrote:
Before running the chroot command, you can type "mount" to see if the
[EMAIL PROTECTED] mount
/dev/root on / type ext2 (rw)
/dev/scd0 on /cdrom type iso9660 (ro)
/dev/cloop on /KNOPPIX type iso9660 (ro)
/ramdisk on /ramdisk type tmpfs (rw,size=186064k)
/proc/bus/usb on /pro
On Mon, 15 Nov 2004, Kent West wrote:
My / is on hda5 and /boot is on hda3 (another ext2 partition). I still
can't get the boot partition to mount in such a way that lilo can
open/write stuff to it. So I've taken your option of pasting file contents
and the results of some commands. etc/lilo.conf
Dan Davison wrote:
OK thanks a lot for helpful advice (Kent and other two repliers). Knoppix
is downloaded and running. One current problem: I haven't got to run lilo
under knoppix, because it won't recognise the location of the boot
partition (specified as /dev/hda3 in lilo.conf). I have mounted a
On Sun, 14 Nov 2004, Kent West wrote:
> Dan Davison wrote:
>
> >Any help with the following would be much appreciated: I was attempting to
> >update a kernel from 2.2.20 to 2.6.8 and it seems now that neither of the
> >kernel links in the lilo menu will boot. Both exit with the same kernel
> >pan
Dan Davison wrote:
Any help with the following would be much appreciated: I was attempting to
update a kernel from 2.2.20 to 2.6.8 and it seems now that neither of the
kernel links in the lilo menu will boot. Both exit with the same kernel
panic message and the output up to that point appears to be
--- Dan Davison <[EMAIL PROTECTED]> wrote:
> I answered yes to the
> question resulting from dpkg -i about making
> modifications to lilo...
>
> Dan
This was a mistake. It shouldn't be but it is and the
same thing happened to me. I was forced to use the
boot floppy to boot and then went to the
hi ya dan
On Sun, 14 Nov 2004, Dan Davison wrote:
> VFS: Cannot open root device "305" or unknown-block(3,5)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on unknown-block(3,5)
it means your boot config ( grub or lilo ) is configured to look
for /dev
Dave De Graff wrote:
I tried to install kernel-image-2.4.20-686-smp, following the prompts to
"add an 'initrd=/initrd.img' to the image=/vmlinux stanza of
/etc/lilo.conf", and the installation seemed to go fine until I rebooted the
machine.
During boot, the screen hung with a continuous rapid scro
55 matches
Mail list logo
