Thought I would share this solution/workaround.
I had a kernel dump happening following the kernel update
to 2.6.32 for Debian squeeze on an IBM x345. It looked like
this problem:
https://bugzilla.kernel.org/show_bug.cgi?id=26692
I tried removing 'quiet' from the kernel args but it simply
is a few lines from the
bottom of the screen. Other Linux distros (Ubuntu, Knoppix) have
problems booting too. The strange thing is, Windows boots just fine,
and I get the same error booting Debian's CD in Virtualbox.
I am running:
Mobo: Biostar TA770 A2+ SE
Add nopat to the boot options
) have problems
booting too. The strange thing is, Windows boots just fine, and I get the
same error booting Debian's CD in Virtualbox.
I am running:
Mobo: Biostar TA770 A2+ SE
--
Isaac Freeman
memotype (at) gmail.com
The diversity of mankind is a basic postulate of our knowledge of human
Hi!
I am trying to install Debian Lenny on my MacBook, by way of an external
USB hard disk and Refit. I have followed the instructions given in
http://ghaint.no-ip.org/~k2/debian/mbp-usb.html and succeeded in booting
from the i386 net-install for Lenny Beta 2, created partitions and installed
Andrew Reid wrote:
On Sunday 23 March 2008 01:57, Freddy Freeloader wrote:
I assume I'm running into problems with udev not naming
the devices consistently but am not quite sure of my diagnosis or how to
fix it if that is the problem.
I don't think udev rules will fix it, since
Hi All,
I'm building a server based on an Asus M2N-LR mobo, a 3Ware 9550SXU RAID
card, 8 gigs of ram and a dual core Opteron. The hard drives are all
sata Raptors with 4 of the 5 drives in a RAID 10 array. I'm running Etch.
The problem I'm having is an intermittent one with booting. I
On Sat, Mar 22, 2008 at 10:57:30PM -0700, Freddy Freeloader wrote:
I'm building a server based on an Asus M2N-LR mobo, a 3Ware 9550SXU RAID
card, 8 gigs of ram and a dual core Opteron. The hard drives are all
sata Raptors with 4 of the 5 drives in a RAID 10 array. I'm running Etch.
The
Douglas A. Tutty wrote:
On Sat, Mar 22, 2008 at 10:57:30PM -0700, Freddy Freeloader wrote:
I'm building a server based on an Asus M2N-LR mobo, a 3Ware 9550SXU RAID
card, 8 gigs of ram and a dual core Opteron. The hard drives are all
sata Raptors with 4 of the 5 drives in a RAID 10 array.
On Sun, Mar 23, 2008 at 05:14:44PM -0700, Freddy Freeloader wrote:
Douglas A. Tutty wrote:
On Sat, Mar 22, 2008 at 10:57:30PM -0700, Freddy Freeloader wrote:
I'm building a server based on an Asus M2N-LR mobo, a 3Ware 9550SXU RAID
card, 8 gigs of ram and a dual core Opteron. The hard
On Sunday 23 March 2008 01:57, Freddy Freeloader wrote:
I assume I'm running into problems with udev not naming
the devices consistently but am not quite sure of my diagnosis or how to
fix it if that is the problem.
I don't think udev rules will fix it, since the udev rules
are on the root
On Thu, 2007-11-29 at 08:29 +0900, David wrote:
Thierry Chatelet wrote:
On Wednesday 28 November 2007 22:24, I.E.Broadbent wrote:
Anyone have any comments or suggestions please.
Anyone heard of any problems with the CPU's or Boards mentioned above?
Thanks, Ian
Hi, I got a
AN UPDATE:
Especially to Thierry, Dave, Doug, ... some further news I have
just had a note from the chap that supplies my bits'n'bobs
(BTW ...anybody know of a reliable UK wholesaler of medium quantities
for DRAM/Processors/hardware/etc?) ... he has spotted (must get myself
a new pair of
I.E.Broadbent wrote:
AN UPDATE:
Especially to Thierry, Dave, Doug, ... some further news I have
just had a note from the chap that supplies my bits'n'bobs
(BTW ...anybody know of a reliable UK wholesaler of medium quantities
for DRAM/Processors/hardware/etc?) ... he has spotted (must get
On Thu, Nov 29, 2007 at 07:23:24PM +0900, David wrote:
I.E.Broadbent wrote:
AN UPDATE:
Especially to Thierry, Dave, Doug, ... some further news I have
just had a note from the chap that supplies my bits'n'bobs
(BTW ...anybody know of a reliable UK wholesaler of medium quantities
for
Douglas A. Tutty wrote:
snip
Note that I run an Athlon64 3800+ with one 1 GB stick. Runs just fine.
4GB is not a minimum size
There are a lot of CPUs around now that people are installing into
things like personal PCs and word processor/spreadsheet work stations
that will operate just fine
I built two boxes last week...
both (almost) identical
CPU - Both AMD Socket-AM2 64bit Dual Core (one 4300 and one 4600)
Memory - both identical - 4 x 1gig modules per motherboard
Motherboard - both identical - Gigabyte S-Series M61P-S3
Both using onboard Network and Graphics
One machine
On Wednesday 28 November 2007 22:24, I.E.Broadbent wrote:
Anyone have any comments or suggestions please.
Anyone heard of any problems with the CPU's or Boards mentioned above?
Thanks, Ian
Hi, I got a similar problem, which was soulve by increasing the voltage on the
memories sticks. No
Thierry Chatelet wrote:
On Wednesday 28 November 2007 22:24, I.E.Broadbent wrote:
Anyone have any comments or suggestions please.
Anyone heard of any problems with the CPU's or Boards mentioned above?
Thanks, Ian
Hi, I got a similar problem, which was soulve by increasing the voltage on the
On Wed, Nov 28, 2007 at 09:24:49PM +, I.E.Broadbent wrote:
I built two boxes last week...
both (almost) identical
CPU - Both AMD Socket-AM2 64bit Dual Core (one 4300 and one 4600)
Memory - both identical - 4 x 1gig modules per motherboard
Motherboard - both identical - Gigabyte
Hello,
I'm a Debian testing user. A few days ago I recompiled the kernel (2.6.18)
and I installed it in the Debian way (by creating a .deb package of the
kernel and installing it). But I've got a problem: when I boot the system
with the new kernel, appears a lot of times the message modprobe:
Jaume Alonso wrote:
Hello,
I'm a Debian testing user. A few days ago I recompiled the kernel
(2.6.18) and I installed it in the Debian way (by creating a .deb
package of the kernel and installing it). But I've got a problem: when
I boot the system with the new kernel, appears a lot of times
Try to run as root:
# update-modules
and see if it goes away!
Cassiano Leal
Marko Randjelovic wrote:
Jaume Alonso wrote:
Hello,
I'm a Debian testing user. A few days ago I recompiled the kernel
(2.6.18) and I installed it in the Debian way (by creating a .deb
package of the kernel and
On Dec 28, 9:00 am, Jaume Alonso [EMAIL PROTECTED] wrote:
Hello,
I'm a Debian testing user. A few days ago I recompiled the kernel (2.6.18)
and I installed it in the Debian way (by creating a .deb package of the
kernel and installing it). But I've got a problem: when I boot the system
with
I have installed Debian testing using the binary-1 CD. After fiddling
with the grub install (see below [*]) the kernel-2.6.15-1-i686-smp
boots and starts from the initramfs. The initramfs initializes among
other things the SCSI subsystem (AIC7899), device mapper and LVM2, and
my ethernet card
Nach einem dist-upgrade mit neuem 2.6er Kernel hört sid mit dieser
Meldung auf zu booten.
/bin/cat: /sys/block/hda/hda6/dev: No such file or directory
Die Installation des neuen Kernels lief problemlos ab.
Irgendwelche Ideen, wie ich das wieder hinbekomme?
TIA
juh
--
Haeufig gestellte
On 14.12.05 17:49:54, Jan Ulrich Hasecke wrote:
Nach einem dist-upgrade mit neuem 2.6er Kernel hört sid mit dieser Meldung
auf
zu booten.
/bin/cat: /sys/block/hda/hda6/dev: No such file or directory
Die Installation des neuen Kernels lief problemlos ab.
Irgendwelche Ideen, wie ich
Andreas Pakulat schrieb:
On 14.12.05 17:49:54, Jan Ulrich Hasecke wrote:
Nach einem dist-upgrade mit neuem 2.6er Kernel hört sid mit dieser Meldung auf
zu booten.
/bin/cat: /sys/block/hda/hda6/dev: No such file or directory
Etwas mehr Infos waeren nicht schlecht, u.a. an welcher Stelle im
On Wednesday 14 December 2005 17:49, Jan Ulrich Hasecke wrote:
Nach einem dist-upgrade mit neuem 2.6er Kernel hört sid mit dieser
Meldung auf zu booten.
/bin/cat: /sys/block/hda/hda6/dev: No such file or directory
Die Installation des neuen Kernels lief problemlos ab.
Irgendwelche Ideen,
- Original Message -
From: Paolo Pantaleo [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Subject: Problems booting kernel-image-2.6.8-2-k7
Date: Thu, 8 Sep 2005 19:45:45 +0200
-- Forwarded message --
From: Paolo Pantaleo [EMAIL PROTECTED]
Date: 8-set-2005 19.45
If I boot the system using kernel 2.6, after the message about starting gdm
(GNOME Display Manager), a messy image appears, similar to my desktop
background: except for the mouse, everything is blocked. To go on I have to
reset: mysteriously, after the reboot I can use kernel 2.6 (sometimes I
-- Forwarded message --
From: Paolo Pantaleo [EMAIL PROTECTED]
Date: 8-set-2005 19.45
Subject: Re: Problems booting kernel-image-2.6.8-2-k7
To: Alessandro Di Rubbo [EMAIL PROTECTED]
2005/9/8, Alessandro Di Rubbo [EMAIL PROTECTED]:
If I boot the system using kernel 2.6, after
After re-installing debian via knoppix on my parents computer, and
dist-updating. I installed grub again and at the time thought it was all
configured right.
But when it once re-started after the storm pass through the other night
what was seen on the screen was error 15 after stage 1.5. *sigh*
On Wed, 24 Dec 2003 01:04:17 -0600, Grant Bierman wrote:
After re-installing debian via knoppix on my parents computer, and
dist-updating. I installed grub again and at the time thought it was all
configured right.
But when it once re-started after the storm pass through the other night
Custom kernel 2.4.22 seems to boot fine up to the point where it deals
with the usb hotplug script, where there are a couple of segfaults,
but it gets past that, and then hangs at:
Cleaning: /etc/network/ifstate
/etc/network/interfaces is set up to auto lo, eth0, eth1. eth0 is
static (lan) and
My sid workstation had a boot drive failure. I replaced the failed drive
(a Maxtor 30GB) with a Maxtor 120GB. I kept the same partition layout
(swap hda1; / hda2; lvm hda3). I then rebuilt the base system from the
woody bf2.4disks and did an apt-get dselect-upgrade from the package list
in
Alberto == Alberto Cabello Sanchez [EMAIL PROTECTED] writes:
Alberto I just installed potato r3 on P75, 16 MB RAM and all worked
Alberto fine. But booting from hard drive seems impossible to me.
I suspect a hardware problem. Try running `badblocks /dev/hda'
--
G. ``Iggy'' Geens - ICQ:
Problem was solved yesterday with installation of GRUB as bootloader, so it
remains only as something rare, but not critical. I will continue investigating
a bit more.
Lilo output is normal, I think:
[EMAIL PROTECTED]:~# lilo
Added Linux *
[EMAIL PROTECTED]:~#
My lilo.conf reads (yes, it is a
I just installed potato r3 on P75, 16 MB RAM and all worked fine.
But booting from hard drive seems impossible to me. I have lilo
well config, and it boots well from floppy, but I always get
an error among this ones when booting from hard drive:
* crc error.
* Out of memory.
* Less than 4 MB
I just installed potato r3 on P75, 16 MB RAM and all worked fine.
But booting from hard drive seems impossible to me. I have lilo
well config, and it boots well from floppy, but I always get
an error among this ones when booting from hard drive:
* crc error.
* Out of memory.
* Less
On Thu, Apr 12, 2001, Len Cheatham wrote:
unreadable html
Hi Len,
I couldn't really follow your question, as I couldn't easily read your
html-formatted email (for the future, you're certain to get more
responses with text-only email, with line breaks at ~70 chars). But
I'm going to give it a
- Original Message -
From: Len Cheatham [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Sent: Thursday, April 12, 2001 10:29 PM
Subject: Major problems booting Debian 2.2 - Nothing works
I cannot get Debian 2.2 to boot up. I tried the following 2 methods, to no
avail:
ATTEMPT #1:
After
I cannot get Debian 2.2 to boot up. I tried the following 2 methods, to no avail:
ATTEMPT #1:
After downloading the CD from the Debian site, I burned a CD for Disk #1 and placed that in the CD drive. I booted the computer, and after going through all the install screens, Debian said that it
Hi there,
I am having a stragne problem with lilo that I have not seen before and
not sure how to solve it. I am running Debian unstable on anIBM Thinkpad
600X with a 12 G hard drive. Recently, about a week ago, lilo 1:21.6
went into the distribution. Since that point in time I have been unable
At 10:20 AM 1/13/01 -0500, you wrote:
Linux boots no problems as usual. NT does not.
When I boot NT I get a Blue screen of death with the error message
c135 and that winsrv.dll cannot find a DLL it needs.
Upon furthur investigation I have determined that somehow the second
NTFS partition is
Dear all,
A friend of mine used to have working hamm system. He upgraded his
processor memory, and then the sound and video card to a
Videologic Apocalypse 5D Sonic Accelerator card (sound and video card)
this has the PowerVR PCx2 3D processor
ET6100 chip (2D) and
ESS audio chipset
The
On Tue, 25 Feb 1997, Karl Sackett wrote:
I've been trying to upgrade my kernel using kernel-source-2.0.27. I
put the new kernel on a floppy, boot from the floppy, and instead of
loading the new kernel I get this on my display:
Loading..
8000
AX: 02FF
BX:
CX: 000B
DX:
On Mon, 3 Mar 1997, Dale Scheetz wrote:
On Tue, 25 Feb 1997, Karl Sackett wrote:
I've been trying to upgrade my kernel using kernel-source-2.0.27. I
put the new kernel on a floppy, boot from the floppy, and instead of
loading the new kernel I get this on my display:
Loading..
I've been trying to upgrade my kernel using kernel-source-2.0.27. I
put the new kernel on a floppy, boot from the floppy, and instead of
loading the new kernel I get this on my display:
Loading..
8000
AX: 02FF
BX:
CX: 000B
DX:
The hex code sequence keeps repeating until I reset my
I've built a kernel with the sources from 2.0.6, but I'm having problems
when I try to run it. I get the error:
VFS: Cannot open root device 03:02
Kernel panic: VFS: Unable to mount root fs on 03:02
This is what I have in my .config file:
#
# Filesystems
#
#
Hi,
VFS: Cannot open root device 03:02
your IDE driver is missing or can't find the disk. Is there any lines about
IDE disks on the screen?
Greetings
Bernd
Actually it looks like your root device isn't set up properly .. are you
using a boot disk .. if you are check out the rdev command it enables you
to set your root partition. If it is not set correctly then you will get
the following error.
Michael
Hi,
VFS: Cannot open root device
51 matches
Mail list logo
