Re: Boot Problem

Stephen P. Molnar composed on 2023-12-05 13:33 (UTC-0500): > I decided to try something. I logged in to the rescue  mode as root and > entered startx at the prompt. This generated the error: I believe if xserver-xorg-legacy is not installed that startx failure is expected. I keep it installed o

Re: Boot Problem

Please forgive me if I somehow messed up the quote attribution. There was a lot of stuff I was able to cull. :) On 12/5/23, David Christensen wrote: > On 12/5/23 10:33, Stephen P. Molnar wrote: > > I decided to try something. I logged in to the rescue mode as root and > > entered startx at the

Re: Boot Problem

On 5 Dec 2023 11:05 -0500, from s.mol...@sbcglobal.net (Stephen P. Molnar): > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back tot he > login screen, over and over and . I got the same resul

Re: Boot Problem

On 12/5/23 08:05, Stephen P. Molnar wrote: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than opening my XFCE desktop I was sent back tot he login screen, over and over and . I got the same result attempting to login as root. I ha

Re: Boot Problem

My Os is up to date and running the version XFCE4 I've attached the log files that i could find. I hope that it will help. On 12/05/2023 02:26 PM, Alexander V. Makartsev wrote: On 05.12.2023 23:33, Stephen P. Molnar wrote: I decided to try something. I logged in to the rescue  mode as root an

Re: Boot Problem

Am Dienstag, 5. Dezember 2023, 18:56:48 CET schrieb Stephen P. Molnar: Not good! You have to start startx from the shell. However, when you see the login screen (gdm, lightdm, kdm, whatever), that means, the X-server is running and ok. So you have a problem with XFCE. Look at ~/.config/xfce4 an

Re: Boot Problem

On 05.12.2023 23:33, Stephen P. Molnar wrote: I decided to try something. I logged in to the rescue  mode as root and entered startx at the prompt. This generated the error: Unable to contact settings server failed to execute child process "dbus-launch" (No such file or directory) I vaguely re

Re: Boot Problem

I decided to try something. I logged in to the rescue  mode as root and entered startx at the prompt. This generated the error: Unable to contact settings server failed to execute child process "dbus-launch" (No such file or directory) On 12/05/2023 01:03 PM, Tom Furie wrote: "Stephen P. Moln

Re: Boot Problem

"Stephen P. Molnar" writes: > On 12/05/2023 12:47 PM, Tom Furie wrote: >> "Stephen P. Molnar" writes: >> >>> I have Bookworm installed on a 1TB SSD. When I attempted logging this >>> morning I failed! Rather than opening my XFCE desktop I was sent back >>> tot he login screen, over and over and

Re: Boot Problem

I've attached the log. I hope that someone can tell me what the problem is. Thanks inn advance. On 12/05/2023 11:59 AM, Joe wrote: On Tue, 5 Dec 2023 11:05:15 -0500 "Stephen P. Molnar" wrote: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than

Re: Boot Problem

Xfce4 graphical login screen On 12/05/2023 12:47 PM, Tom Furie wrote: "Stephen P. Molnar" writes: I have Bookworm installed on a 1TB SSD. When I attempted logging this morning I failed! Rather than opening my XFCE desktop I was sent back tot he login screen, over and over and ...

Re: Boot Problem

"Stephen P. Molnar" writes: > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back > tot he login screen, over and over and . I got the When you say "back to the login screen", do you mean ba

Re: Boot Problem

On Tue, 5 Dec 2023 11:05:15 -0500 "Stephen P. Molnar" wrote: > I have Bookworm installed on a 1TB SSD. When I attempted logging this > morning I failed! Rather than opening my XFCE desktop I was sent back > tot he login screen, over and over and . I got the > same result attempt

Re: Boot Problem

Am Dienstag, 5. Dezember 2023, 17:05:15 CET schrieb Stephen P. Molnar: To get closer to the cause, I suggest to remove temporaryly any loginmamanger out of the way Either /usr/bin/xdm, /usr/bin/kdm, /usr/bin/gdm or /usr/bin/ xdm, whatever. Copy it somewhere, i.e. to /root Then reboot and from th

Re: Boot Problem

Le 16/06/2019 à 15:53, Stephen P. Molnar a écrit : I have just installed a new SSD in my 64 bit Stretch platform. When I boot the machine I get the following error: error: file '/boot/grub/i386-pc/normalmod' not found Entering rescue mode .. . . grub rescue>_ Pressing Contro-Alt-Delete reboots

Re: Boot Problem

In-Reply-To: <5d0649da.40...@sbcglobal.net> On Sun, 16 Jun 2019, Stephen P. Molnar wrote: > > On 06/16/2019 12:16 PM, bw wrote: > > In-Reply-To: <5d0649da.40...@sbcglobal.net> > > > Stephen P. Molnar, Ph.D. says... > > > I have just installed a new SSD in my 64 bit Stretch platform. > > > > > >

Re: Boot Problem

On 6/16/19 6:53 AM, Stephen P. Molnar wrote: I have just installed a new SSD in my 64 bit Stretch platform. When I boot the machine I get the following error: error: file '/boot/grub/i386-pc/normalmod' not found Entering rescue mode .. . . grub rescue>_ Pressing Contro-Alt-Delete reboots the s

Re: Boot Problem

Stephen P. Molnar wrote: > I have just installed a new SSD in my 64 bit Stretch platform. what do you mean by "installed"? there is a lot of difference between plugging it in vs. plugging it in and putting something on it. what did you do? give details. we don't know what you did nor c

Re: Boot Problem

In-Reply-To: <5d0649da.40...@sbcglobal.net> >Stephen P. Molnar, Ph.D. says... >I have just installed a new SSD in my 64 bit Stretch platform. > >When I boot the machine I get the following error: > >error: file '/boot/grub/i386-pc/normalmod' not found >Entering rescue mode .. . . >grub rescue>_ > >

Re: boot problem after updating dropbear [solved -- MANUAL initrd works required]

Hi, Okay, it turns out that the only files that were missing were ones that I had in the /etc/initramfs-tools/root/ directory. The only files in the faulty initrd image were from the /etc/initramfs-tools/root/.ssh/ directory, so missing .profile and other required files. I modified the initr

Re: boot problem

Hi, you can open the Terminal and type: # grub-install /dev/sda1 And # update-grub2 This will do what you need. Em 06-03-2016 03:55, lina escreveu: > Hi, > > After install the debian, > > it goes to debian OS system directly, without showing me the option of > start Mac OS or debian OS. > > Any

Re: boot problem

g quicker. And you will get a menu. Original Message From: lina Sent: Mon Mar 07 01:01:31 AEDT 2016 To: Keith Bainbridge Cc: Debian Lists Subject: Re: boot problem df -h Filesystem Size Used Avail Use% Mounted on /dev/sda4 641M 235M 360M 40% / udev

Re: boot problem

df -h Filesystem Size Used Avail Use% Mounted on /dev/sda4 641M 235M 360M 40% / udev 10M 0 10M 0% /dev tmpfs 1.6G 9.1M 1.6G 1% /run /dev/sda819G 3.6G 14G 21% /usr tmpfs 3.9G 68K 3.9G 1% /dev/shm tmpfs 5.0M 4.0K

Re: boot problem

Good afternoon Lina Try holding the alt key as you boot. You should get a few icons to choose osx or linux. If not, please send us output of command df -h Original Message From: lina Sent: Sun Mar 06 17:55:17 AEDT 2016 To: Debian Lists Subject: boot problem Hi, After

Re: Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at "Switching to clocksource tsc" )

Le 06.10.2013 18:34, Curt a écrit : On 2013-10-06, berenger.mo...@neutralite.org wrote: Any idea about how to be able to run terminal stuff correctly in recovery mode? Maybe changing the terminal (if so, how could I do that?)? export TERM=linux says google Thanks. But, this line does o

Re: Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at "Switching to clocksource tsc" )

On 2013-10-06, berenger.mo...@neutralite.org wrote: > > Any idea about how to be able to run terminal stuff correctly in > recovery mode? Maybe changing the terminal (if so, how could I do > that?)? > export TERM=linux says google -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debia

Recovery mode: impossible to run dpkg ( was Re: boot problem: stuck at "Switching to clocksource tsc" )

Le 05.10.2013 14:54, berenger.mo...@neutralite.org a écrit : Hi. Since my last kernel update my desktop can not boot anymore, it is stuck at "Switching to clocksource tsc". Also, nothing at all reply, even the keyboard does just nothing. Of course, I was stupid enough to remove the last kernel w

Re: Boot problem : Operating System not found.

On Sat, 17 Mar 2012 18:30:51 +0100, Bruno Costacurta wrote: Bruno, you MUA is somehow deleting both "References:" and "In-Reply-To:" header fields and thus your posts are kept unthreaded. > [snip] >> I'll also try the SuperGrub2Disk ASAP. > [snip] > > Yes, it works when booting using a SuperGru

Re: Boot problem : Operating System not found.

[snip] I'll also try the SuperGrub2Disk ASAP. [snip] Yes, it works when booting using a SuperGrub2Disk CD. From SuperGrub2Disk boot menu : Detect any OS -> Debian correctly found on /dev/sda4 -> boot is OK. So I suppose the GRUB on the hard disk is incorrectly setup. As the boot-info script r

Re: Boot problem : Operating System not found

On Fri, 16 Mar 2012 20:52:37 +, luizlmarins hotmail.com wrote: (please, no html... thanks) > See here: > > http://linuxmeu.wordpress.com/grub-nao-aparece/ But GRUB does appear in this case. What happens is that it hangs when booting Debian. Greetings, -- Camaleón -- To UNSUBSCRIBE,

Re: Boot problem : Operating System not found.

It would've been helpful not to have snipped the "drive partition info" section! :) You have a gpt-labelled disk but sda1 isn't OK. As "File system", it should have "BIOS Boot partition". "Boot sector type" and "Boot sector info" cannot be right but I don't know what they should be. The two

Re: Boot problem : Operating System not found.

On Fri, Mar 16, 2012 at 3:13 PM, Bruno Costacurta wrote: > >  => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector >    946507840 of the same hard drive for core.img. core.img is at this >    location and looks for  on this drive. > ... > sda1: > >    File system:       vfat >

Re: Boot problem : Operating System not found.

'Operating System not found' is displayed once boot via GRUB command line. [snip] What's the output of bootinfoscript? [snip] So I ran boot_info_script.sh. Which returns the following (snipped to mainly show /dev/sda4 on which Debian is installed) : Boot Info Script 0.60from 17 May

Re: Boot problem : Operating System not found (was : how to make it verbose ?)

On Thu, 15 Mar 2012 19:55:39 +0100, Bruno Costacurta wrote: > .. >> Another thing you can test is manually booting your Debian system from >> GRUB2 boot menu by reaching the command line. This way if you're lucky >> any error you get will be printed on the screen. > .. > > Indeed you're right. >

Re: Boot problem : Operating System not found (was : how to make it verbose ?)

On Thu, Mar 15, 2012 at 2:55 PM, Bruno Costacurta wrote: >> >> Another thing you can test is manually booting your Debian system from >> GRUB2 boot menu by reaching the command line. This way if you're lucky >> any error you get will be printed on the screen. > > Indeed you're right. > 'Operating

Re: Boot problem : how to make it verbose ?

On Wed, 14 Mar 2012 20:48:03 +0100, Bruno Costacurta wrote: >>> I installed Debian Squeeze on a multi-boot PC where Ubuntu is the >>> first and bootable distro. >> Are you chainloading GRUB2s or are you loading Debian directly from >> Ubuntu's own GRUB2 version? > > I boot direclt from the Ubuntu

Re: Boot problem : how to make it verbose ?

On Wed 14 Mar 2012 at 20:48:03 +0100, Bruno Costacurta wrote: > Yes, the GRUB2 menu is reached (in fact, it's used to boot the other > system on same PC). The Debian system hangs direcly. Nothing is > displayed. > Yes, a LiveCD Debian 6 works fine (however it was a i386, the installed > Debia

Re: Boot problem : how to make it verbose ?

I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first and bootable distro. Are you chainloading GRUB2s or are you loading Debian directly from Ubuntu's own GRUB2 version? I boot direclt from the Ubuntu's own GRUB2 version. Using GRUB2, the options 'nosplash debug --verbose

Re: Boot problem : how to make it verbose ?

On Wed, 14 Mar 2012 11:06:04 +0100, Bruno Costacurta wrote: > I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first > and bootable distro. Are you chainloading GRUB2s or are you loading Debian directly from Ubuntu's own GRUB2 version? > Using GRUB2, the options 'nosplash debug

Re: Boot problem : how to make it verbose ?

On Wed 14 Mar 2012 at 11:06:04 +0100, Bruno Costacurta wrote: > I installed Debian Squeeze on a multi-boot PC where Ubuntu is the first > and bootable distro. > Using GRUB2, the options 'nosplash debug --verbose' are used, but Debian > freezes silently. > How to make boot verbose to see what hap

apt pinning (Re: Boot problem after crashed update)

Javier Barroso (javibarr...@gmail.com on 2011-05-12 19:11 +0200): > > Other possible solution would be pinning all packages from sid to > their current version (upgrading glibc with the bug, of course), and > removing sid from sources.list, and again wait, but this time you > could upgrade your sys

Re: Boot problem after crashed update

On Thu, May 12, 2011 at 8:35 PM, Jochen Schulz wrote: > Javier Barroso: >> >> So, why not, simply wait one month without upgrading, remove sid from >> your sources.list (and keep only wheezy), and then aptitude update; >> aptitude safe-upgrade; aptitude full-upgrade ? > > Because the OP would stil

Re: Boot problem after crashed update

12/05/2011 14:59, Simon Hoerder wrote: > Jochen Schulz wrote: > [...] >> Since you still have a bootable operating system, you may try the hint >> at . > > After taking a second look at Sven's link after lunch I discovered > similar hints

Re: Boot problem after crashed update

Javier Barroso: > > So, why not, simply wait one month without upgrading, remove sid from > your sources.list (and keep only wheezy), and then aptitude update; > aptitude safe-upgrade; aptitude full-upgrade ? Because the OP would still run some kind of more or less mixed wheezy/sid system even th

Re: Boot problem after crashed update

On Thu, May 12, 2011 at 6:26 PM, Jochen Schulz wrote: > Simon Hoerder: >> >> Is there an easy way to remove all unstable packages? > > No, at least no easy way I could come up with. You could use aptitude > search to identify installed packages from unstable, remove them and > reinstall them from

Re: Boot problem after crashed update

Simon Hoerder: > > Is there an easy way to remove all unstable packages? No, at least no easy way I could come up with. You could use aptitude search to identify installed packages from unstable, remove them and reinstall them from squeeze. But since you apparently already have libc from unstable,

Re: Boot problem after crashed update

Jochen Schulz wrote: [...] Since you still have a bootable operating system, you may try the hint at . After taking a second look at Sven's link after lunch I discovered similar hints there as well. These hints helped to some degree -

Re: Boot problem after crashed update

Simon Hoerder: > > deb http://ftp.de.debian.org/debian sid main contrib That line points to unstable, aka "sid". Sid is the permanent alias for the unstable distribution, unlike the rolling aliases for testing and stable. > Assuming Sven is correct: > B) Am I correct that the easiest way to retu

RE: Boot problem after crashed update

From: Simon Hoerder [mailto:si...@hoerder.net] > 1) This morning, I did the same (what the package manager calls a "safe" > update, no packages where removed or installed) but in between the >update crashed the system. > ... > udevd[58]: error: runtime directory '/run/udev' not writable, fo

Re: Boot problem after crashed update

Sorry, meant to send it to the list, not just to Jochen. Jochen Schulz wrote: >> I made a fresh install of debian squeeze just after its release and >> dutifully installed the updates suggested by the package manager >> whenever necessary. > > What's the content of your sources.list? deb http://

Re: Boot problem after crashed update

Eccles, David wrote: From: Simon Hoerder [mailto:si...@hoerder.net] 1) This morning, I did the same (what the package manager calls a "safe" update, no packages where removed or installed) but in between the update crashed the system. ... udevd[58]: error: runtime directory '/run/udev' no

Re: Boot problem after crashed update

On 2011-05-12 12:53 +0200, Jochen Schulz wrote: >> udevd[58]: error: runtime directory '/run/udev' not writable, for >> now falling back to '/dev/.udev' > > That looks like you are actually running testing or unstable. FWIW, the error message has not been present in udev versions before 168, and

Re: Boot problem after crashed update

> I made a fresh install of debian squeeze just after its release and > dutifully installed the updates suggested by the package manager > whenever necessary. What's the content of your sources.list? > 2) The only thing that worked was switching between x (ctrl+alt+f7) and >the terminal (ctrl

Re: boot problem

On Fri, Jan 2, 2009 at 5:30 PM, Mike Alterman wrote: > I installed Linux on a 2nd drive. This box is currently running win2K. > Downloaded the 1st dvd image file and created boot and root floppies. Question: can't your PC boot DVDs? That's why you need to create B&R floppies? > > The boot floppy

Re: boot problem

Mike Alterman wrote: > I installed Linux on a 2nd drive. This box is currently running win2K. > Downloaded the 1st dvd image file and created boot and root floppies. > > The boot floppy proved to be defective - image. Downloaded the boot > image from > http://ftp.nl.debian.org/debian/dists/etch/m

Re: boot problem

On Sun, Nov 23, 2008 at 02:12:53PM -0500, Douglas A. Tutty wrote: > The problem is in the /etc/rcS.d/S10checkroot.sh script, it gets an > error when it goes to remount the / fs rw (after the filesystem is > declared clean). > > "Cannot change data mode or remount > mount / not mounted already or b

Re: boot problem with custom kernel

"Nelson Castillo" <[EMAIL PROTECTED]> writes: >> 12. make-kpkg --append-to-version=.powertop kernel_image > > Hi, you missed the "--initrd" option. That way the package will make the > initrd when installed and the kernel will use it at boot time. Thanks, that did the trick. Not sure why I neve

Re: boot problem with custom kernel

12. make-kpkg --append-to-version=.powertop kernel_image Hi, you missed the "--initrd" option. That way the package will make the initrd when installed and the kernel will use it at boot time. Regards. -- http://arhuaco.org http://emQbit.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] wi

Re: Boot problem

Kent West wrote: Roelof Wobben wrote: But can't i be done with the boot-only cd from Sarge. Yes, but I'm unsure of the steps; I'm sure Google has it somewhere though. I want to use lilo instead of grub. Then instead of running grub-install, run lilo, once you're chroot'ed into your system

Re: Boot problem

On Fri, Nov 10, 2006 at 12:14:27PM +, Roelof Wobben wrote: From: Roelof Wobben <[EMAIL PROTECTED]> To: debian-user@lists.debian.org Subject: Re: Boot problem X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on murphy.debian.org X-Spam-Level: X-Spam-Status: No, score=0.5 requir

Re: Boot problem

Roelof Wobben wrote: But can't i be done with the boot-only cd from Sarge. Yes, but I'm unsure of the steps; I'm sure Google has it somewhere though. I want to use lilo instead of grub. Then instead of running grub-install, run lilo, once you're chroot'ed into your system. However, Windo

Re: Boot problem

On (10/11/06 12:14), Roelof Wobben wrote: > Oke, > > I understand how to fix it. > > But can't i be done with the boot-only cd from Sarge. > I have used this one to download and install Sarge. > > I want to use lilo instead of grub. I'm not sure if you can get to grub from the sarge disk but if

Re: Boot problem

Oke, I understand how to fix it. But can't i be done with the boot-only cd from Sarge. I have used this one to download and install Sarge. I want to use lilo instead of grub. Roelof _ 500 foto's per maand uploaden, GRATIS! http:

Re: boot problem

Roelof Wobben wrote: Hello, I have installed Debian Sarge on the second hard disk of my computer. Because lilo couldn't see windows , which is installed on the first disk, I couldn't start Windows. So i did a mbr repair of the mbr. But now i don't know how to het into Debian to change lilo s

Re: boot problem

On (10/11/06 10:35), Roelof Wobben wrote: > I have installed Debian Sarge on the second hard disk of my computer. > Because lilo couldn't see windows , which is installed on the first disk, I > couldn't start Windows. > So i did a mbr repair of the mbr. > > But now i don't know how to het into Deb

Re: Boot problem with a moved ext3 partition

High, On 28 Dec 2004, jean wrote: > Hi, > > I have a laptop with windows XP and Debian sarge, the boot is from > windows XP. I've transformed the debian ext3 partion in an extended > partition with inside the orginal partition (I've used Partion Magic > 8.0). The operation terminated with succe

Re: boot problem with new kernel-any idas?

John Foster <[EMAIL PROTECTED]> writes: > I recently downloaded, and using "make-kpkg buildpackage", built a > complete new kernel headers...etc. from a tarball( linux-2.4.21) > downloaded from www.kernel.org. It installed with no problems, > including running lilo. I rebooted and crapped out at

Re: Boot problem

On Tue, 25 Mar 2003 22:33:31 -0500 [EMAIL PROTECTED] wrote: > No, actually it makes great sense -- I just can't believe I might have > left something so obvious out! (I suppose I may have thought IDE > support was a default 'yes,' -- but I can see how it may be best > assumed NOT, because SCSI is

Re: Boot problem

[EMAIL PROTECTED] wrote: >On Tue, 25 Mar 2003 21:01:55 -0500 >[EMAIL PROTECTED] wrote: > >> one of times after which I recompiled a 2.4.16 kernel for the Official >> Deb (I got the source pkg. from the Libranet CD's), and carefully >> modified the /boot/grub/menu.lst on Libranet, I got a kernel pa

Re: Boot problem

On Tue, Mar 25, 2003 at 09:01:55PM -0500, [EMAIL PROTECTED] wrote: > request_module[ide-disk]: Root fs not mounted > hdb: driver not present > VFS: Cannot open root device "hdb3" or 03:43 > Please append a correct "root=" boot option > Kernel panic: VFS: Unable to mount root fs on 03:43 (is this...

Re: Boot problem

On Tue, 25 Mar 2003 21:01:55 -0500 [EMAIL PROTECTED] wrote: > one of times after which I recompiled a 2.4.16 kernel for the Official > Deb (I got the source pkg. from the Libranet CD's), and carefully > modified the /boot/grub/menu.lst on Libranet, I got a kernel panic on > the subsequent boot. >

Re: boot problem

#include * Mikkel Liisberg [Wed, Feb 12 2003, 04:51:10PM]: > i have just installed woody on my scsi HD. My problem is when i try to boot > from it i get a screen like this : > 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 > 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 0

Re: boot problem - UNSUBSCRIBE

begin Paul 'Baloo' Johnson quotation: > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > or visit http://lists.debian.org/ Telling him once, nicely, was kind of you. Telling him repeatedly, you risk becoming as much of a problem

RE: boot problem - UNSUBSCRIBE

On Fri, 22 Mar 2002, Jonathan Tabaco wrote: > Sorry to all those who are inconvenienced by this but I have tried > multiple times to get removed from the mailing list. > > I even sent in the confirm "CONFIRM u03180819391769" > > PLEASE REMOVE ME MANUALLY, as your automated system doesn't work. To

RE: boot problem - UNSUBSCRIBE

Sorry to all those who are inconvenienced by this but I have tried multiple times to get removed from the mailing list. I even sent in the confirm "CONFIRM u03180819391769" PLEASE REMOVE ME MANUALLY, as your automated system doesn't work. I will unfortunately have to resort to "spamming" the De

Re: boot problem

On Fri, 22 Mar 2002 17:16, Michal Novotny wrote: > Something else, there is in /boot/config-2.4.17-386 line: > CONFIG_BLK_DEV_SIS5513=y > that is my IDE controller > > but there is too: > CONFIG_IDE=m > CONFIG_BLK_DEV_IDE=m > CONFIG_BLK_DEV_IDEDISK=m > CONFIG_BLK_DEV_IDEPCI=y You have two options.

Re: boot problem

On Fri, 22 Mar 2002 14:22, Michal Novotny wrote: > I have a real problem booting my Debian. > I just upgraded all packages (running dselect). > Now what I get after reboot is (last lines): > > request_module[block-major-3]: Root fs not mounted > VFS: Cannot open root device "301" or 03:01 > Please

Re: boot problem

On Tue, 17 Jul 2001, D-Man wrote: >On Wed, Jul 18, 2001 at 01:12:56AM +1000, Sam Varghese wrote: >| On Tue, Jul 17, 2001 at 10:43:26AM +0100, J.A.Serralheiro wrote: >| > well maybe you misconfigured your video card. >| > Run xf86config. Its a text based environment and re-do the configurations. >|

Re: boot problem

Sorry. Ididnt check that, and its been a while since i did the last configuration.

Re: boot problem

On Wed, Jul 18, 2001 at 01:12:56AM +1000, Sam Varghese wrote: | On Tue, Jul 17, 2001 at 10:43:26AM +0100, J.A.Serralheiro wrote: | > well maybe you misconfigured your video card. | > Run xf86config. Its a text based environment and re-do the configurations. | > It may help. be sure you know what ch

Re: boot problem

On Tue, Jul 17, 2001 at 10:43:26AM +0100, J.A.Serralheiro wrote: > well maybe you misconfigured your video card. > Run xf86config. Its a text based environment and re-do the configurations. > It may help. be sure you know what chipset your board has. I think yuo can > also choose and "general" chip

Re: boot problem

well maybe you misconfigured your video card. Run xf86config. Its a text based environment and re-do the configurations. It may help. be sure you know what chipset your board has. I think yuo can also choose and "general" chipset that should work on most cards. If you can put it to work, then use X

Re: boot problem after kernel compile

Although I can't tell you what went wrong, don't reinstall yet. Using a windows machine, head over to tomsrtbt: http://www.toms.net/rb/home.html There is a version to install from windows. With tomsrtbt, you will be able to mount your original root partition and fix the problem. Gil Elad wrote:

Re: boot problem

I don't know for sure, but often - even under Linux - Ctrl+Alt+Del will do a reboot. That depends on your /etc/inittab settings though. And I can easily imagine a situation where that wouldn't work, if the keyboard is in raw mode (maybe ?), but it's at least worth a try. I hope this helps to answe

Re: boot problem

On Sat, Feb 03, 2001 at 06:53:47PM -0500, Tino Ionescu wrote: > Hi, > I installed a modem and configured(?) with pppconf. > Now the problem is that at boot time is trying to start the > pppd, configuration is probably wrong, so it get frozen - Cntr C > or anything else doesn't work. > > Any i

Re: Boot Problem

I would try reinstalling Lilo just off the top of my head that is what it looks like to me. -- Original Message -- From: "Janos Kramar" <[EMAIL PROTECTED]> Date: Sat, 28 Oct 2000 12:52:14 -0400 >After installing Debian without any apparent problems and reb

Re: Boot Problem - Pls Help

On Wed, Jan 03, 1996 at 01:17:56AM +0530, Jeetu Golani wrote: > Hi, > > I'm a novice to Linux and Unix in general. I've installed Debian on my system - a 133MHz Pentium with 32MB RAM and 2 Hard Disks with the Linux Swap partition being 8 MB and the core Linux Partition being 484MB.I dont have an

Re: Boot problem

Most of the time this means that you have Lilo configured wrong. There are essentially two steps needed to get Lilo going: editing the file /etc/lilo.conf to correctly reflect your setup, and then running the /sbin/lilo command to install Lilo. If you post more information, such as... 1) the loca

Re: Boot problem on new computer

as far as i know the athlon requires kernel 2.2.13 to boot(or newer) anything less will crash (i read that 2.2.12 works but from what i remember on the kernel mailing list 2.2.13 was the one to use) nate On Wed, 5 Jan 2000, Peter Schuller wrote: scode >Hello, scode > scode >I'm in a desperate ne

Re: boot problem

Quoting [EMAIL PROTECTED]: > >boot=/dev/hda1 > >root=/dev/hda1 > >append="ether=10,0x300,eth0 ether=11,0x310,eth1" > >compact > >install=/boot/boot.b > >delay=20 > >map=/boot/map > >vga=normal > >image=/vmlinuz > >label=Linux > >read-only > > I would remove the compact option. I n

Re: boot problem?

Hi On Tue, 09 Feb, 1999 à 10:48:53AM -0600, Jiao Lingxiu wrote: > Hello, > > When I boot, I got the following error messages > > . > Partition check: > hda1: hda1 > hdb: [DM6:DD0] [remap +63] [624/128/63] hdb1/hdb2 > attempt to access beyond end of device >

Re: Boot Problem

I think my ppp crapped out on me while I was sending my last email. Here it is again:--- Begin Message --- Viola! Success. That was rather strange. After booting with the floppy, I went and executed lilo like you said (actually I went to bin rather than sbin, but it worked anyway), rebooted sans fl

Re: Boot Problem

Viola! Success. That was rather strange. After booting with the floppy, I went and executed lilo like you said (actually I went to bin rather than sbin, but it worked anyway), rebooted sans floppy, and it booted without hesitation. What did I miss? At the end of the install, where you were given a

Re: Boot Problem

> Well, I loaded Debian from floppy. However, while it boots from the boot > floppy fine, when I try to boot from the hd, it doesn't appear to load > anything, and stops at a 1FA: prompt (to which nothing can be typed). Hm, to me it sounds like a problem with lilo. What does it say, if you execute

Re: Boot problem after installation

> That is the wrong solution to the problem. Something is probably wrong > with lilo.conf, or the wrong partition is marked active, but changing > lilo.conf isn't the best solution. As far as I can tell, the problem is with the boot disks, as it has happened on 2 of my friends computers as well, w

Re: Boot problem after installation (and a cfdisk query)

On Wed, 27 May 1998, Hamish Moffatt wrote: > On Tue, May 26, 1998 at 02:56:13PM -0400, Norbert Veber wrote: > > On Tue, May 26, 1998 at 08:27:09PM +0200, Tomas Petersson wrote: > > > Hello, I have just installed Debian Linux, everything > > > went fine except I can't boot from the harddrive. > > >

Re: Boot problem after installation

On Tue, May 26, 1998 at 02:56:13PM -0400, Norbert Veber wrote: > On Tue, May 26, 1998 at 08:27:09PM +0200, Tomas Petersson wrote: > > Hello, I have just installed Debian Linux, everything > > went fine except I can't boot from the harddrive. > > If I boot from the 'Custom Boot Floppy' it works, > >

Re: Boot problem after installation

On Tue, May 26, 1998 at 08:27:09PM +0200, Tomas Petersson wrote: > Hello, I have just installed Debian Linux, everything > went fine except I can't boot from the harddrive. > If I boot from the 'Custom Boot Floppy' it works, > but when I boot the harddrive I get the following > prompt: '2FA:', and

Re: Boot problem

"Erik Eriksson" wrote: >3. Can you recommend any SQL based freeware for Linux, we would like to do s >ome >tests. There are Debian packages for PostgreSQL, mSQL, mysql and nosql. (mSQL and mysql are in non-free.) -- Oliver Elphick[EMAIL PROTECTED] Isle

Re: boot problem with tbeach maui

Thank you! That's what I find about in other howto-s and documents about sound and scsi cards. Tamas Imrei [EMAIL PROTECTED] > "Tamas Imrei" <[EMAIL PROTECTED]> writes: > > > Does anyone know how I can disable this 'searching' for scsi at > > 0x330? > > Reconfigure and recompile your kernel

  1   2   >