Re: Booting problem

2022-11-12 Thread David Wright
On Sun 13 Nov 2022 at 08:24:11 (+0530), Emilia Maher wrote: > Hello, > I have installed NetBeans through snapd process, as explained here: > > https://wiki.debian.org/Netbeans > > But after installation completed, I have faced booting problem. > Then I have removed the snapd through terminal comm

Re: Large initrd [Was: Re: booting problem (udev related?)]

2007-08-03 Thread Andrei Popescu
On Thu, Aug 02, 2007 at 08:34:00PM -0400, Douglas Allan Tutty wrote: > However, don't all those modules in the initrd end up staying in the > kernel anyway, or do they get unloaded during boot? If they stay, and > 'most' modules get added, how is that different than having a huge > monolithic ke

Re: Large initrd [Was: Re: booting problem (udev related?)]

2007-08-02 Thread Douglas Allan Tutty
On Fri, Aug 03, 2007 at 12:19:36AM +0300, Andrei Popescu wrote: > On Thu, Aug 02, 2007 at 10:35:01AM -0700, Andrew Sackville-West wrote: > > So what is the significance of initrd size? (other than the obvious > > filling up /boot issue). Is it really a problem to have "most" modules > > in there?

Re: Large initrd [Was: Re: booting problem (udev related?)]

2007-08-02 Thread Andrei Popescu
On Thu, Aug 02, 2007 at 06:40:52PM +0200, Florian Kulzer wrote: > On Thu, Aug 02, 2007 at 18:23:04 +0300, Andrei Popescu wrote: > > [...] > > > Yes, I know what you mean. I was using yaird to make my initrd, but it > > gave some errors on the latest upgrade (and Steve Langasek, Debian > > kerne

Re: Large initrd [Was: Re: booting problem (udev related?)]

2007-08-02 Thread Andrei Popescu
On Thu, Aug 02, 2007 at 10:35:01AM -0700, Andrew Sackville-West wrote: > same here. interesting. I'll have to play with that. You could > probably tighten it up even more by using the 'list' option and > putting a minimum-necessary list in /etc/initramfs-tools/modules. At > least that's how I rea

Re: Large initrd [Was: Re: booting problem (udev related?)]

2007-08-02 Thread Andrew Sackville-West
On Thu, Aug 02, 2007 at 06:23:04PM +0300, Andrei Popescu wrote: > On Wed, Aug 01, 2007 at 11:10:25PM -0600, Bob Proulx wrote: > > Miles Bader wrote: > > > Hmm, I didn't realize it analyzed the system when building the ramfs > > > contents. Maybe I could just reinstall the kernel while the new kern

Re: Large initrd [Was: Re: booting problem (udev related?)]

2007-08-02 Thread Florian Kulzer
On Thu, Aug 02, 2007 at 18:23:04 +0300, Andrei Popescu wrote: [...] > Yes, I know what you mean. I was using yaird to make my initrd, but it > gave some errors on the latest upgrade (and Steve Langasek, Debian > kernel maintainer suggested it is no longer maintained). Do you mean this problem?

Large initrd [Was: Re: booting problem (udev related?)]

2007-08-02 Thread Andrei Popescu
On Wed, Aug 01, 2007 at 11:10:25PM -0600, Bob Proulx wrote: > Miles Bader wrote: > > Hmm, I didn't realize it analyzed the system when building the ramfs > > contents. Maybe I could just reinstall the kernel while the new kernel > > is running (or is there an official "hint" mechanism I could use)

Re: booting problem (udev related?)

2007-08-01 Thread Bob Proulx
Miles Bader wrote: > Hmm, I didn't realize it analyzed the system when building the ramfs > contents. Maybe I could just reinstall the kernel while the new kernel > is running (or is there an official "hint" mechanism I could use)? Yes. Please try that. > [I thought it just included _every_ pos

Re: booting problem (udev related?)

2007-08-01 Thread Douglas Allan Tutty
On Thu, Aug 02, 2007 at 08:50:08AM +0900, Miles Bader wrote: > I seems like it may be related to udev because if I look in /dev, the disk > device nodes which should be there _aren't there_, even though the disk > hardware is recognized fine by the kernel. > Udev isn't running yet. The boot de

Re: booting problem (udev related?)

2007-08-01 Thread Miles Bader
[EMAIL PROTECTED] (Bob Proulx) writes: > I think the problem is your clue that previously you had compiled into > your kernel your required modules. This may be making it difficult > for mkinitramfs to determine which modules are required. If it fails > to detect this it would build an incorrect

Re: booting problem (udev related?)

2007-08-01 Thread Bob Proulx
Miles Bader wrote: > The problem is that with the new kernel, the system won't boot all the way. > It fails when it tries to mount the root partition, and dumps me into the > ramfs emergency shell. The error message is something generic like "File > not found" (sorry for the vagueness, those boot

Re: booting problem with tpconfig after removing it

2004-01-26 Thread Jan Minar
On Sat, Jan 24, 2004 at 07:03:05PM +0100, Jan Ulrich Hasecke wrote: > I encountered a strange problem today. Suddenly my notebook stops > booting after starting klogd. > > I am running 2.6.1 and unstable. > > After booting into single user mode I tried to manually start > everything in rc2.d via

Re: Booting problem

2001-01-15 Thread kmself
on Fri, Jan 12, 2001 at 07:37:29PM +0100, Bolem?nyi Attila ([EMAIL PROTECTED]) wrote: > HI! > > I have an Abit BE6-II motherboard with HPT370UDMA/ATA 100 raid > cintroller. > When I try to install the Potato, I have a message, so I have not a hard > disk. > How can I install the Potato to my comp

Re: Booting problem with AMD Athlon

2000-01-24 Thread Adam Di Carlo
Alain Birtz <[EMAIL PROTECTED]> writes: > I recently bought Debian 2.1 and I tried to install it on my brand new > PC. > However I was not capable to make it to the installer. > > When I start from the CD-ROM, I see the boot: prompt, I hit return and > then it starts loading stuff, like a normal

Re: Booting problem with AMD Athlon

2000-01-21 Thread Dave Blears
On Fri, Jan 21, 2000 at 03:51:35PM -0500, Alain Birtz wrote: > Hi, > > I recently bought Debian 2.1 and I tried to install it on my brand new > PC. > However I was not capable to make it to the installer. > > When I start from the CD-ROM, I see the boot: prompt, I hit return and > then it s

Re: Booting problem with AMD Athlon

2000-01-21 Thread aphro
99% chance i the kernel on the Cd is not compadible with athlon, you need to make your own boot disk, or, if possible it would be easier to install on a non athlon, upgrade the kernel then move the HD back to the athlon. you need linux 2.2.13 to boot on athlon.(or newer) nate On Fri, 21 Jan 2000