is problem.
Sigh, Thomas
-Original-Nachricht-
Betreff: Re: AW: Debugging initramfs, server hangs during boot process
Datum: 2023-08-30T12:00:56+0200
Von: "Michel Verdier"
An: "debian-user@lists.debian.org"
On 2023-08-30, thah...@t-online.de wrote:
> The last USB d
On 2023-08-30, thah...@t-online.de wrote:
> The last USB device in this list is a bluetooth card. I have blacklisted
> btusb,
> but this didn't help, still hangs.
> At 182 seconds I pressed CRTL_ALT_DEL and the times without sleep statements
> come down to like 11 seconds when it hangs.
You sh
wn to like 11 seconds when it hangs.
-Original-Nachricht-
Betreff: Re: AW: Debugging initramfs, server hangs during boot process
Datum: 2023-08-28T11:42:19+0200
Von: "Michel Verdier"
An: "debian-user@lists.debian.org"
On 2023-08-28, thah...@t-online.de wrote:
> It hangs i
On 2023-08-28, thah...@t-online.de wrote:
> It hangs in /usr/share/initramfs-tools/scripts/init-top/udev
>
> The 2nd last udev call hangs my box
> udevadm trigger --type=devices --action=add
Perhaps add before
udevadm trigger --verbose --dry-run --type=devices --action=add
On 28/08/2023 05:19, thah...@t-online.de wrote:
It hangs in /usr/share/initramfs-tools/scripts/init-top/udev
Unsure if it is related or not (I have not tried to debug it), but I
have noticed some issues with laptop boot when a USB hub with a keyboard
and a mouse is connected. It might be an u
The udev script is from the udev package
-Original-Nachricht-
Betreff: AW: Debugging initramfs, server hangs during boot process
Datum: 2023-08-28T00:20:33+0200
Von: "thah...@t-online.de"
An: "debian user"
It hangs in /usr/share/initramfs-tools/scripts/init-top/ude
ted root.
Sigh!
-Original-Nachricht-
Betreff: Re: AW: Debugging initramfs, server hangs during boot process
Datum: 2023-08-26T13:45:19+0200
Von: "Michel Verdier"
An: "debian-user@lists.debian.org"
On 2023-08-26, thah...@t-online.de wrote:
> Tried with clocksourche
On 2023-08-26, thah...@t-online.de wrote:
> Tried with clocksourche=hpet
> Now the Switched to clocksouce tsc is missing and the last line is
> clocksource: tsc: mask .
> like before the 2nd last line (as to be expected)
On my kernel I always have those 3 lines during boot :
clocksource: tsc
-Nachricht-
Betreff: Re: AW: Debugging initramfs, server hangs during boot process
Datum: 2023-08-26T12:04:46+0200
Von: "Tixy"
An: "debian-user@lists.debian.org"
On Sat, 2023-08-26 at 11:07 +0200, thah...@t-online.de wrote:
> I had debug on the command line before, just
On Sat, 2023-08-26 at 11:07 +0200, thah...@t-online.de wrote:
> I had debug on the command line before, just didn't know of debug=vc
> However the output on the screen is the same with either one.
>
> Last line is clocksource: Switched to clocksource tsc
I notice two 1 second delays during boot o
with debug prints just to find
where it is stuck
uaaah!
-Original-Nachricht-
Betreff: Re: Debugging initramfs, server hangs during boot process
Datum: 2023-08-26T10:20:54+0200
Von: "Michel Verdier"
An: "debian-user@lists.debian.org"
On 2023-08-26, Tixy wrote:
>&
On 2023-08-26, Tixy wrote:
>> I thought of that, too, but debug writes to a tmpfs (it has to, at this
>> point). If the machine locks up, the log is lost...
>
> Logs will appear on the screen so long as you don't have the 'quiet'
> parameter on the Linux commandline.
I think it always writes to t
On Sat, 2023-08-26 at 07:59 +0200, to...@tuxteam.de wrote:
> On Sat, Aug 26, 2023 at 07:40:21AM +0200, Michel Verdier wrote:
[...]
> >
> > Did you try with "debug" on the linux command line to get more logs
> > ?
>
> I thought of that, too, but debug writes to a tmpfs (it has to, at this
> point)
On Sat, Aug 26, 2023 at 07:40:21AM +0200, Michel Verdier wrote:
> On 2023-08-25, thah...@t-online.de wrote:
>
> > Looking at the initramfs manpages i found that I can get into the busybox
> > during
> > the boot process with break=... on the linux command line.
>
On 2023-08-25, thah...@t-online.de wrote:
> Looking at the initramfs manpages i found that I can get into the busybox
> during
> the boot process with break=... on the linux command line.
> break=top
> works, but
> break=modules
> is not reached. It hangs before that.
Di
Hi all,
being on sid, I know that there can be problems.
However, this seems to be a bit hard for me to solve without proper help.
The machine hangs during boot.
Looking at the initramfs manpages i found that I can get into the busybox
during
the boot process with break=... on the linux command
Hi,
sonbird wrote:
> i was just going to suggest that he clone your brain. :)
If brain cloning is a viable option then i propose those of
Vladimir Serbinenko and Daniel Kiper because of their experience as
maintainers of GRUB.
Have a nice day :)
Thomas
gt;live-boot *does* have these options. I've not used those in a while.
>'man 7 live-boot' mentions 'toram' and 'fromiso/findiso'.
>> I will need to log the boot process to study it.
>Perhaps you need 'debug', 'nosplash', and si
Thomas Schmitt wrote:
...
> If i wanted to expand my knowledge towards x86-related firmware,
> bootloaders, and the Linux kernel i would probably begin at
> https://en.wikipedia.org/wiki/BIOS
> https://uefi.org/specifications
> https://git.savannah.gnu.org/cgit/grub.git/tree/
> https://www.
Hi,
Albretch Mueller wrote:
> imagine you had to code a new bootloader now (as an exercise) in
> hindsight which books would you have picked?
I only know about the small bridges between computer firmware and the
first custom program to be started, which usually is a bootloader.
https://dev.lov
` images to add DOS and other small
systems.
[...]
I have been always intrigued about such matters and such differences,
between what I see as supposedly being standardized, like a boot
process.
Compare the boot process between amd64 and armhf to find out that there are
quite the
computer,
in order to liberate your DVD player after booting), ..., which DL
doesn’t have.
I know some RS232/USB converters are not reliable. Which ones do you
use? As far as I know laptops don’t come with RS232 anymore. I will
need to log the boot process to study it.
I have been always intrigued
On Mon, 23 Mar 2020 14:51:53 +0200
Andrei POPESCU wrote:
Hello Andrei,
>A standard[1] Debian install "requires[2] networking only for
>(security) updates.
Thanks for the info, Andrei.
A classic case of "a little knowledge" My little knowledge, of
course.
--
Regards _
/ )
On Lu, 23 mar 20, 10:47:14, Brad Rogers wrote:
>
> TBH, I wasn't sure. Certain things require networking availability, so
> that got me thinking. Anyhow, that turned out to be a blind alley.
A standard[1] Debian install "requires[2] networking only for (security)
updates.
[1] i.e. something
On Mon, 23 Mar 2020 12:26:05 +0200
Andrei POPESCU wrote:
Hello Andrei,
>In the default install the display manager does not wait for networking
>(why should it?), your problem is most likely elsewhere.
TBH, I wasn't sure. Certain things require networking availability, so
that got me thinking
On Du, 22 mar 20, 14:43:37, Brad Rogers wrote:
> Hello,
>
> For the first time, I'm having problems installing Debian testing on new
> hardware;
>
> Asus TUF X570 Plus mobo with onboard Realtek network L8200A i/f
>
> As things stand, it /seems/ that the boot process
On Sun, 22 Mar 2020 21:10:48 +0100
Bernd Gruber wrote:
Hello Bernd,
>Brad Rogers wrote:
>
>> Failed to start NVIDIA Persistence Daemon
>have you looked this up, I find it several times on ddg.
Briefly, but didn't pursue it, before I took myself down a blind alley.
I've not got time to look
Brad Rogers wrote:
> Failed to start NVIDIA Persistence Daemon
have you looked this up, I find it several times on ddg.
what does dmesg say?
Can you install systemd-bootchart and have a look at the bootchart (probably
on another machine)?
Bernd
On Sun, 22 Mar 2020 14:00:49 -0400
Marc Auslander wrote:
Hello Marc,
>Could it be https://wiki.debian.org/BoottimeEntropyStarvation
I thought that had been resolved some while ago.
However, no amount of random keypressing resulted in progress.
Thanks for the suggestion.
--
Regards _
On 3/22/2020 10:50 AM, Brad Rogers wrote:
Hello,
For the first time, I'm having problems installing Debian testing on new
hardware;
Asus TUF X570 Plus mobo with onboard Realtek network L8200A i/f
As things stand, it /seems/ that the boot process is waiting for the
network interface to co
On Sun, 22 Mar 2020 17:43:56 +
Daniel Harris wrote:
Hello Daniel,
>are you using dhcp or static ip addresses
I never entered addresses for IP during installation, so dhcp I suspect.
>what is in /etc/resolv.conf
search home
nameserver 192.168.1.1
nameserver 2001:8b0::2020
nameserver 2001:8
So you say you can ping your local lan. That indicated your networking is
working.
are you using dhcp or static ip addresses
what is in /etc/resolv.conf
On Sun, Mar 22, 2020 at 5:16 PM Brad Rogers wrote:
> On Sun, 22 Mar 2020 13:02:07 -0400
> Felix Miata wrote:
>
> Hello Felix,
>
> >Just a
On Sun, 22 Mar 2020 13:02:07 -0400
Felix Miata wrote:
Hello Felix,
>Just a thought: try another net install, this time configuring a static
>IP via installation cmdline options.
Two options already - yours and Daniel's. That's what's so good about
this list.
Thanks Felix.
I know re-installin
Brad Rogers composed on 2020-03-22 14:43 (UTC):
> The OS was installed using a net-install CD, so clearly, the network
> card is working. Having never previously encountered network i/f issues
> myself, I'm really rather at a loss as to how I should proceed.
Just a thought: try another net insta
On Sun, 22 Mar 2020 16:07:42 +
Daniel Harris wrote:
Hello Daniel,
>One thing, but if your networking was working during the install why did
>you install firmware-realtek. I would try removing that. Linux keeps
Because networking was failing after the install in any case, and there
was men
l keep it in mind, but a previous attempt at installing stable
> wouldn't give a graphical login - I found that my nVidia gfx card isn't
> supported by stable's nvidia drivers. To be fair, I didn't see any
> network issues, but that might have been because I got dro
talling stable
wouldn't give a graphical login - I found that my nVidia gfx card isn't
supported by stable's nvidia drivers. To be fair, I didn't see any
network issues, but that might have been because I got dropped to a tty
before the boot process got that far. I didn't test
the first time, I'm having problems installing Debian testing on new
> hardware;
>
> Asus TUF X570 Plus mobo with onboard Realtek network L8200A i/f
>
> As things stand, it /seems/ that the boot process is waiting for the
> network interface to come up, before proceeding to
Hello,
For the first time, I'm having problems installing Debian testing on new
hardware;
Asus TUF X570 Plus mobo with onboard Realtek network L8200A i/f
As things stand, it /seems/ that the boot process is waiting for the
network interface to come up, before proceeding to start the SDDM l
t and
keymap". Right before the virtual console (tty1) appears, the resolution
is reset to a lower 800x600. The window size decreased.
My questions:
1) What changes the tty screen resolution later in the boot process?
console-setup.service?
2) How to prevent the screen resolution from being
On Mon 04 Jun 2018 at 04:21:20 (-0500), Richard Owlett wrote:
> My explicit question is:
>Does an annotated list of boot process related log files and
>their locations exist?
Not AFAICT. But it's never to late to start writing a wiki.
> I did a reasonably typical inst
Richard Owlett wrote:
> My explicit question is:
> Does an annotated list of boot process related log files and
> their locations exist?
/var/log/installer ?
> I did a reasonably typical install from DVD-1 of Debian 9.1.0 .
> It is at least partly functional - I can
My explicit question is:
Does an annotated list of boot process related log files and
their locations exist?
I did a reasonably typical install from DVD-1 of Debian 9.1.0 .
It is at least partly functional - I can log in as root.
The only error message during boot was that it could not
> Sorry to see that you're having this problem. I'm stymied as to why it might
> happen with a VM. I had assumed that the new kernel had stopped supporting
> some piece of hardware in my rather unusual little notebook computer.
> The same day the kernel was updated on my system, pc-grub was also
On 11/03/2016 03:26 PM, Mike Conde wrote:
Have you checked your boot partition - does it have enough free space?
I don't have a separate boot partition, just one main partition that
is 40GB in capacity and 40% full.
Sorry to see that you're having this problem. I'm stymied as to why it
might
> Have you checked your boot partition - does it have enough free space?
I don't have a separate boot partition, just one main partition that
is 40GB in capacity and 40% full.
Mike Conde wrote:
> I am having exactly the same problem as Jape Person's post from Oct 22
> 2016, except my hardware environment is completely different.
>
> I am running Debian testing/Stretch 64-bit on a virtual machine under
> virtualbox. The host OS is Windows 7 64-bit.
>
> I don't know ex
I am having exactly the same problem as Jape Person's post from Oct 22
2016, except my hardware environment is completely different.
I am running Debian testing/Stretch 64-bit on a virtual machine under
virtualbox. The host OS is Windows 7 64-bit.
I don't know exactly which kernel update was the
On 10/23/2016 05:26 PM, Frank wrote:
Op 23-10-16 om 22:47 schreef Felix Miata:
I don't remember having any Stretch installations with fewer than two
installed kernels. The currently booted one, originally installed 51
weeks ago, has 6 installed. I've yet to discover any doc suggesting
anything a
Op 23-10-16 om 22:47 schreef Felix Miata:
I don't remember having any Stretch installations with fewer than two
installed kernels. The currently booted one, originally installed 51
weeks ago, has 6 installed. I've yet to discover any doc suggesting
anything about any possibility of automatic remo
On 10/23/2016 04:47 PM, Felix Miata wrote:
Jape Person composed on 2016-10-23 14:33 (UTC-0400):
Felix Miata wrote:
Does the same thing happen booting the previous kernel
(4.6?)?
Nope. The problem occurred on the first reboot after the
upgrade from 4.7.6-1 to 4.7.8-1. The upgrade process d
Jape Person composed on 2016-10-23 14:33 (UTC-0400):
Felix Miata wrote:
Does the same thing happen booting the previous kernel (4.6?)?
Nope. The problem occurred on the first reboot after the upgrade
from 4.7.6-1 to 4.7.8-1. The upgrade process didn't leave
4.7.6-1 in place so I could fall
her of you tried intercepting Grub and unquieting
the boot process? Remove quiet, and either change splash to splash=0 or
remove splash entirely. Then proceed to boot, and see what if anything shows
up on screen besides a blinking underline cursor in the upper left corner.
Yes, both of us have tr
On 10/23/2016 01:21 PM, Børge Holen wrote:
I have to use the nomodeset from time to time where the f*** gfx card has
unresolved issues with itself. Atleast it lets me boot to a prompt. Now
thinking of it, I have no blinking cursor, I just get a black screen... So
different issue all together and
On 10/23/2016 01:03 PM, Michael Lange wrote:
On Sun, 23 Oct 2016 12:14:39 -0400
"James P. Wallen" wrote:
Double checked to see if I was right about the video subsystem.
It is not ATI, it is Intel integrated. No docs on this thing. It
was never officially sold in U.S., where I live currently. S
the boot process? Remove quiet, and either change splash to splash=0 or
remove splash entirely. Then proceed to boot, and see what if anything shows
up on screen besides a blinking underline cursor in the upper left corner.
Does the same thing happen booting the previous kernel (4.6?)?
Hav
Heck I even remember a one-floppy live distribution that I had for just
this purpose.
On Sun, Oct 23, 2016 at 7:26 PM, Børge Holen wrote:
> Have you tried booting off a live distribution and inserted the old kernel
> and symlinked the libraries so you can rerun grub update? I remember we had
> t
Have you tried booting off a live distribution and inserted the old kernel
and symlinked the libraries so you can rerun grub update? I remember we had
to do that with lilo whenever I tried new kernels and forgot all about
lilo. Cannot even remember the last time I did it, since I found the rescue
o
I have to use the nomodeset from time to time where the f*** gfx card has
unresolved issues with itself. Atleast it lets me boot to a prompt. Now
thinking of it, I have no blinking cursor, I just get a black screen... So
different issue all together and I am just rambling on
On Sun, Oct 23, 2016 a
On Sun, 23 Oct 2016 12:14:39 -0400
"James P. Wallen" wrote:
> Double checked to see if I was right about the video subsystem.
> It is not ATI, it is Intel integrated. No docs on this thing. It
> was never officially sold in U.S., where I live currently. Since
> I can't boot it to usable state,
er left corner. I suspect that the boot process stops
immediately after grub. I cannot connect via ssh or even ping
the system. Using Ctrl-Alt-Del has no effect, but touching the
start-stop switch elicits a beep and immediate power-down.
The same results are obtained if I use the grub menu to sele
inux-image-4.7.0-1-686-pae (4.7.8-1) and grub-pc (2.02-beta3-1).
Upon reboot the system stops with a blinking underline cursor in
the upper left corner. I suspect that the boot process stops
immediately after grub. I cannot connect via ssh or even ping
the system. Using Ctrl-Alt-Del has no e
Update:
I've reported the bug here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801467
#801467
See also discussion there (similar case and possible solutions):
https://lists.debian.org/debian-user/2015/10/msg00175.html
Best regards,
Dmitry Piyavkin
.2.0-4-686-pae:i386 3.2.68-1+deb7u4 3.2.71-2
linux-headers-3.2.0-4-486:i386 3.2.68-1+deb7u4 3.2.71-2
linux-headers-3.2.0-4-common:i386 3.2.68-1+deb7u4 3.2.71-2
linux-libc-dev:i386 3.2.68-1+deb7u4 3.2.71-2
On the other day I wasn't able to boot up my system, because it freezes
dead at boot proc
On 6 August 2013 12:05, atar wrote:
> Hi there!!
>
> Can someone here help me please to know how to power on the numlock key
> automatically during the boot process?
>
> Thanks in advance!!
Hi Atar,
In the past, I've enabled num lock / caps lock on boot from my BIOS
setti
atar [2013-08-06 14:05:54 +03:00] wrote:
> Can someone here help me please to know how to power on the numlock
> key automatically during the boot process?
Usually people install "numlockx" package which it does the job
automatically. Also desktop environments may have an opt
Hi there!!
Can someone here help me please to know how to power on the numlock key
automatically during the boot process?
Thanks in advance!!
atar.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Debian Folks,
We loaded Debian Wheezy on a machine a few hours ago and on two
occasions out of five the boot process has ended abnormally.
The first lines on the KVMoIP display are:
Loading, please wait...
Volume group "bigd-mach01
Dne, 01. 01. 2011 12:36:14 je Lisi napisal(a):
On Sunday 19 December 2010 23:18:19 Bob Proulx wrote:
> I wouldn't transition to
> single user mode from multiuser mode directly myself.
I have never had any problems with init 1, wherever I used it from,
other than
that KDE doesn't shut down very
On Sunday 19 December 2010 23:18:19 Bob Proulx wrote:
> I wouldn't transition to
> single user mode from multiuser mode directly myself.
I have never had any problems with init 1, wherever I used it from, other than
that KDE doesn't shut down very cleanly in the sense that it does not save
every
On 12/19/2010 06:02 PM, Lisi wrote:
> So - Oh my friends be warned by me! init 1 is fine. init s is not. Paul
> has
> given a very clear exposition of the facts either above of below, depending
> on how you thread your emails.
I guess ( after reading Bob's reply) I forgot to mention, NORMALL
Lisi wrote:
> Bob Proulx wrote:
> > > probably about to tell me that it would. ;-)
> > Yes. I am going to say, "It should work." :-)
>
> My curtiosity being even more 'satiable than the elephant's child, I tried.
>
> The short answer is it doesn't work.
Note that I didn't say that it /did/ w
On Sunday 19 December 2010 19:09:46 Bob Proulx wrote:
> I don't think that "init s" would work - but you are
>
> > probably about to tell me that it would. ;-)
>
> Yes. I am going to say, "It should work." :-)
My curtiosity being even more 'satiable than the elephant's child, I tried.
The sho
On 12/19/2010 02:09 PM, Bob Proulx wrote:
>> tty) I use "init 1". I don't think that "init s" would work - but you are
>> > probably about to tell me that it would. ;-)
> Yes. I am going to say, "It should work." :-)
>
> Personally I wouldn't move from multiuser to single user directly. I
> w
Lisi wrote:
> If I want to boot into single user from a cold start, I do it via GRUB. But
> if I am in a GUI and I want to actually change (rather than just bring up a
> tty) I use "init 1". I don't think that "init s" would work - but you are
> probably about to tell me that it would. ;-)
Ye
On Sunday 19 December 2010 18:46:18 Bob Proulx wrote:
> Runlevel 1 is almost universially used to implement single user mode.
> When you ask why not use 1 instead of "single" the answer is that
> there isn't any reason. I just think it more clear to ask for single
> user mode directly and not jump
nfo for talking
about runlevels. Make sure you look at the Unix System V table
because that is the grandfather of all of the present systems.
http://en.wikipedia.org/wiki/Runlevel
Bob
P.S.
The confusion that results from people looking today (as opposed to
twenty years ago) at runlevels is
and I lose the keyboard again... do you know of a
> > > way of changing the runlevel to just console (no X) or aborting X
> > > startup during Linux boot process (some key combination or anything).
> >
> > I searched it and turned up to be pretty simple.
> >
t before X crashes and I lose the keyboard again... do you know of a
> > way of changing the runlevel to just console (no X) or aborting X
> > startup during Linux boot process (some key combination or anything).
> >
> > I'm running Debian Lenny.
>
> In addition
store the
> previous xorg.conf. But as X starts automatically I can't manage to do
> that before X crashes and I lose the keyboard again... do you know of a
> way of changing the runlevel to just console (no X) or aborting X
> startup during Linux boot process (some key combination
the runlevel to just console (no X) or aborting X startup during Linux boot
> > process (some key combination or anything).
>
> I searched it and turned up to be pretty simple.
>
> It's just needed to append the runlevel number to the kernel line, something
> like this e
: *Thu, 16 Dec 2010 12:06:31 +0100
> *To: *
> *Subject: *Spontaneously aborting X startup during Linux boot process
>
> Hello,
>
> I broke my X (again) trying to install a graphics device driver on my
> Vostro 1000, so now I don't have video and the keyboard does not respond.
>
audio
Date: Thu, 16 Dec 2010 12:06:31
To:
Subject: Spontaneously aborting X startup during Linux boot process
Hello,
I broke my X (again) trying to install a graphics device driver on my Vostro
1000, so now I don't have video and the keyboard does not respond.
I just need to be able to c
to do that before X
crashes and I lose the keyboard again... do you know of a way of changing
the runlevel to just console (no X) or aborting X startup during Linux boot
process (some key combination or anything).
I'm running Debian Lenny.
Thanks!
I have a system where I use a readonly nfs root with a local hard drive and I
need to have some local settings for each computer (mainly /etc/hosts, ip
address for network devices, hostname and nfs server settings). I do that by
mounting the local disk on /local and then overiding some settings usi
shimoto wrote:
>> Hey there,
>>
>> Something very weird is happening in my OS. I just compiled the kernel
>> 2.6.28.7 and to boot my machine I need to press ENTER many times
>> during the boot process. I've never seen anything similar to this issue.
>>
>> I
in my OS. I just compiled the kernel
> 2.6.28.7 and to boot my machine I need to press ENTER many times
> during the boot process. I've never seen anything similar to this
> issue.
>
> It's like to run the command:
>
> # cat /var/log/messages|less
>
> Then y
Hey there,
Something very weird is happening in my OS. I just compiled the kernel
2.6.28.7 and to boot my machine I need to press ENTER many times during
the boot process. I've never seen anything similar to this issue.
It's like to run the command:
# cat /var/log/messages|less
Th
' when booting using
> > Lilo?
> >
>
> I *think* you can just add kernel commands after specifying the
> image. So if the image you want to but is linked to vmlinuz then you
> could type
>
> vmlinuz init=1
>
> or
>
> vmlinuz init=/bin/bash
IIRC,
On 10/25/2007 11:17 AM, [EMAIL PROTECTED] wrote:
Thanks Keith! Unfortunately, this machine uses Lilo instead of Grub.
Can something similar be done to enter 'single user mode' when booting
using Lilo?
-- Mark
Please don't top-post.
How you get into runlevel 1 (system maintenance) with LI
On Thu, Oct 25, 2007 at 10:17:22AM -0600, [EMAIL PROTECTED] wrote:
> Thanks Keith! Unfortunately, this machine uses Lilo instead of Grub. Can
> something similar be done to enter 'single user mode' when booting using
> Lilo?
>
I *think* you can just add kernel commands after specifying the
ima
Quoting Keith Christian <[EMAIL PROTECTED]>:
> - Original Message
> From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> To: debian-user@lists.debian.org
> Sent: Thursday, October 25, 2007 8:17:58 AM
> Subject: boot process hangs on init of mysqld
>
ot; <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Sent: Thursday, October 25, 2007 8:17:58 AM
Subject: boot process hangs on init of mysqld
When my boot process starts mysqld, it hangs. How can I get it
unstuck? I cannot ssh into the machine because the boot process
hasn't progress
- Original Message
From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
To: debian-user@lists.debian.org
Sent: Thursday, October 25, 2007 8:17:58 AM
Subject: boot process hangs on init of mysqld
When my boot process starts mysqld, it hangs. How can I get it
unstuck? I can
When my boot process starts mysqld, it hangs. How can I get it
unstuck? I cannot ssh into the machine because the boot process
hasn't progressed far enough. So, I cannot edit the init scripts to
remove mysqld.
Is there some key-stroke sequence I might be able to try to interrupt
Serena Cantor wrote:
I have never used etch
upgrade means learning new things
I don't have time and energy
I am happy with sarge
I hate to say it and I know how you feel, but then Debian is not for you :-(
Upgrading Sid this very moment to try a Debian kernel modification...
Hugo
--- Dougl
On Thu, May 03, 2007 at 04:13:09PM -0700, Serena Cantor wrote:
> Oh, I use sarge, which defaults to kernel 2.4
> It seems I can't use initramfs
I *think* mkinitrd is what you want but I'm really not sure. try
apropos initrd
A
>
> --- Wayne Topa <[EMAIL PROTECTED]> wrote:
>
> > Serena Cantor([
I have never used etch
upgrade means learning new things
I don't have time and energy
I am happy with sarge
--- Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
> On Thu, May 03, 2007 at 02:43:09PM -0700, Serena Cantor wrote:
> > can't run update-initramfs
> > which package contains it?
>
> I see
On Thu, May 03, 2007 at 04:13:09PM -0700, Serena Cantor wrote:
> Oh, I use sarge, which defaults to kernel 2.4
> It seems I can't use initramfs
If ever you want to upgrade to Etch, the release notes make it pretty
clear that you first must upgrade Sarge to a 2.6 kernel.
Doug.
--
To UNSUBSCRIBE
On Thu, May 03, 2007 at 02:43:09PM -0700, Serena Cantor wrote:
> can't run update-initramfs
> which package contains it?
I see that you use Sarge. I don't have a sarge system anymore and the
initrd program has changed.
Is upgrading to Etch a possibility for this box?
Doug.
--
To UNSUBSCRIBE,
1 - 100 of 146 matches
Mail list logo
