Bonjour,
Beaucoup de soucis avec cette installation de debian
sarge sur ibm x series 206m . Un serveur IBM xseries
206 m muni de 2 disques durs sata pilotés par un
contrôleur aic-9405w sas/scsi. Avec l'aide de jimmy ,
nous avons pu détecter les 2 disques et installer
debian sarge avec le noyau
In October last year, I sent the following message
to Debian-User mailing list :-
When just about to open a LaTeX file for
editing, the screen beeped, the following syslogd
messages appeared in xterm and then
the Caps Lock and Scroll Lock lights started
flashing in unison with the screen
saludos a todos..
estoy usando debian sarge 3.1, tengo un disco con xp y debian, todo
trabajo bien, hasta que se me ocurrio clonar con r-drive image, lo clono
bien y quedo ok, pero cuando ya deje y puse a trabajar un solo disco en
el mainboard y le coloque lectora a la maquina, me sale el
El mar, 14-03-2006 a las 08:27 -0500, Argos Perú. escribió:
saludos a todos..
estoy usando debian sarge 3.1, tengo un disco con xp y debian, todo
trabajo bien, hasta que se me ocurrio clonar con r-drive image, lo clono
bien y quedo ok, pero cuando ya deje y puse a trabajar un solo disco en
On Fri, 2005-10-14 at 10:47 -0400, Edward J. Shornock wrote:
michael bailey wrote:
[..]
kernel: CPU 0 : Machine Check Exception:
0004
kernel: Bank 4 : b2040151
kernel: Kernel panic: CPU context corrupt
After the reboot both the green power
light
When just about to open a LaTeX file for
editing, the screen beeped, the following syslogd
messages appeared in xterm and then
the Caps Lock and Scroll Lock lights started
flashing in unison with the screen
completely frozen. Ctrl-Alt-F1 didn't work
so had to reboot from the Power button.
To check for possible memory problems, memtest has
been run for about 5 days for a total of about 19
runs, all of which said no errors.
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
--
To UNSUBSCRIBE,
michael bailey wrote:
[..]
kernel: CPU 0 : Machine Check Exception:
0004
kernel: Bank 4 : b2040151
kernel: Kernel panic: CPU context corrupt
After the reboot both the green power
light and the orange disk light on the front of the PC
are steady (i.e. not flickering).
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Sorry again. After I emailed my response, I realized I for got to run
lilo. So ran it and got this error:
ChatagnierL-Home:/home/lchata# lilo
Fatal: Image name, label, or alias is too long: 'Linux-2.4.27-2-386'
Marty wrote:
Debian User Leonard Chatagnier wrote:
See below for links. Not sure what you mean by what happens when you
boot
using LinuxOLD. It boots normally as it did since first installed.
I do see that
Output module failed to load as was the case on my old sarge. If
your refering
to
Debian User Leonard Chatagnier wrote:
You can, if you will, tell me just how you remove a kernel(outline the
process).
Like any other package: apt-get remove pkgname or use aptitude, dselect,
etc.
I don't use the packaged kernels so I don't know but if it tries to re-install
LILO, I would
On Fri, Jun 24, 2005 at 01:35:23PM +0100, Clive Menzies wrote:
On (24/06/05 23:29), Chris Bannister wrote:
On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
Now I'm worried. Note: I don't have a reiserfs file system, only an
ext3 fs since day one on all
Marty wrote:
Debian User Leonard Chatagnier wrote:
You can, if you will, tell me just how you remove a kernel(outline
the process).
Like any other package: apt-get remove pkgname or use aptitude,
dselect, etc.
I don't use the packaged kernels so I don't know but if it tries to
re-install
Debian User Leonard Chatagnier wrote:
The 2.4.27-2-386 kernel was forced on me by the dist-upgrade. I planned
on going to the 2.6.6-2-686 kernel and will eventually, probably
soon. Kent
finally fixed lilo for me so that sarge boots now if you haven't
already read it.
You can, if you will,
On Fri, 24 Jun 2005 22:15:31 -0500, Debian User Leonard Chatagnier
[EMAIL PROTECTED] wrote:
I'm still trying to get a stable system for the last six months that
I've been using Debian ... Out of 3 or 4 sarge installs, only the last
one via testing worked out of the box and booted normally. The
Kent West wrote:
Debian User Leonard Chatagnier wrote:
The 2.4.27-2-386 kernel was forced on me by the dist-upgrade. I planned
on going to the 2.6.6-2-686 kernel and will eventually, probably
soon. Kent
finally fixed lilo for me so that sarge boots now if you haven't
already read it.
You
--- Kent West [EMAIL PROTECTED] wrote:
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice 301 or 30:01
Please append a correct root= boot option
Kernel panic: VFS unable to mount root fs on 30:01
Ok, not worried at this time as I have my woody
CD's and can do a
rescbf24 to mount
On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
Now I'm worried. Note: I don't have a reiserfs file system, only an
ext3 fs since day one on all partitions.
If anyone can help me to get the system bootable again, I think I can
correct the lilo.conf problem
On (24/06/05 23:29), Chris Bannister wrote:
On Thu, Jun 23, 2005 at 11:05:34AM -0500, Leonard Chatagnier wrote:
Now I'm worried. Note: I don't have a reiserfs file system, only an
ext3 fs since day one on all partitions.
If anyone can help me to get the system bootable
Debian User Leonard Chatagnier wrote:
-Doesn't look like Kent is going to reply
to my last post:
I missed seeing any such post. Nor do I find one in the archives:
http://lists.debian.org/debian-user/2005/06/thrd8.html
--
Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice 301 or 30:01
Please append a correct root= boot option
Kernel panic: VFS unable to mount root fs on
Debian User Leonard Chatagnier wrote:
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
Kent West wrote:
Sarge's boot is hosed, but you've tried to boot off the Woody
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
Kent West wrote:
Sarge's boot is hosed, but you've
Debian User Leonard Chatagnier wrote:
Kent West wrote:
The line should be:
initrd=/initrd.img
I put the / in front of initrd.img and rebooted with kernel panic
again giving
these same boot messages:
VFS: Cannot open root device 301 or 03:01
Please append a correct root= boot
Debian User Leonard Chatagnier wrote:
The output of cat /etc/fstab, cfdisk and lilo.conf are shown at the end
of this message.
Hi Leonard,
I looked over your files. First did you verify the links /vmlinuz
and /vmlinuz.old? Second, what happens when you boot using LinuxOLD?
(Lacking an
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent,
Sorry about my mixup. Found the original reply in drafts; never sent.
This is new reply that is more current. My reply is bolow:
Leonard Chatagnier wrote:
Kent West wrote:
Sarge's boot is hosed, but you've
Kent West wrote:
Debian User Leonard Chatagnier wrote:
Kent West wrote:
The line should be:
initrd=/initrd.img
I put the / in front of initrd.img and rebooted with kernel panic
again giving
these same boot messages:
VFS: Cannot open root device 301 or 03:01
Please
Marty wrote:
Debian User Leonard Chatagnier wrote:
The output of cat /etc/fstab, cfdisk and lilo.conf are shown at the end
of this message.
Hi Leonard,
I looked over your files. First did you verify the links /vmlinuz
and /vmlinuz.old? Second, what happens when you boot using LinuxOLD?
Debian User Leonard Chatagnier wrote:
See below for links. Not sure what you mean by what happens when you boot
using LinuxOLD. It boots normally as it did since first installed. I do see
that
Output module failed to load as was the case on my old sarge. If your refering
to my notes about
Debian User Leonard Chatagnier wrote:
Sorry again. After I emailed my response, I realized I for got to run
lilo. So ran it and got this error:
ChatagnierL-Home:/home/lchata# lilo
Fatal: Image name, label, or alias is too long: 'Linux-2.4.27-2-386'
ChatagnierL-Home:/home/lchata#
So, I
So frustrating, just fixed KDE Knotify problem and Debian only stayed fixed
until installed a dist-upgrade.
Stayed fixed less than a day. Ok, the problem is related to lilo.conf
for an initrd.img. I followed the dist-upgrade messages closely and
thought I did it as described, but apparently
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice 301 or 30:01
Please append a correct root= boot option
Kernel panic: VFS unable to mount root fs on 30:01
Ok, not worried at this time as I have my woody CD's and can do a
rescbf24 to mount woody still installed and correct the lilo.conf
--- Kent West [EMAIL PROTECTED] wrote:
Leonard Chatagnier wrote:
VFS: Cannot open rootdevice 301 or 30:01
Please append a correct root= boot option
Kernel panic: VFS unable to mount root fs on 30:01
Ok, not worried at this time as I have my woody
CD's and can do a
rescbf24 to
Bonjour,
Hier soir ma debian sarge c'est mise à me faire un sublime kernel panic au boot
juste après la détection des disques et donc au moment de les monter je pense.
Ma config:
Athlon 1,33MHz
640Mo
hda = 120 Go /8Mo cache Maxtor (il a 3 semaines)
hda1 = /root
hda2 = swap
Bonjour,
Hier soir ma debian sarge c'est mise à me faire un sublime kernel panic au boot
juste après la détection des disques et donc au moment de les monter je pense.
Ma config:
Athlon 1,33MHz
640Mo
hda = 120 Go /8Mo cache Maxtor (il a 3 semaines)
hda1 = /root
hda2 = swap
Bonjour,
Hier soir ma debian sarge c'est mise à me faire un sublime kernel panic au boot
juste après la détection des disques et donc au moment de les monter je pense.
Ma config:
Athlon 1,33MHz
640Mo
hda = 120 Go /8Mo cache Maxtor (il a 3 semaines)
hda1 = /root
hda2 = swap
Je reprends car le message est parti trop vite :-(
Bonjour,
Hier soir ma debian sarge c'est mise à me faire un sublime kernel panic au
boot juste après la détection des disques et donc au moment de les monter je
pense.
Ma config:
Athlon 1,33MHz
640Mo
hda = 120 Go /8Mo cache Maxtor (il a 3
Je ne sais pas pourquoi il est partit 3 fois...
Désolé pour la gêne occasionnée.
Selon [EMAIL PROTECTED]:
Bonjour,
Hier soir ma debian sarge c'est mise à me faire un sublime kernel panic au
boot
juste après la détection des disques et donc au moment de les monter je
I am attempting to install Borland JBuilder 7 on a Sarge system with the
Sun JRE/SDK 1.4.1-3 already installed (directly from Sun). The
installer is written in Java, so unfortunately I am not able to figure
out exactly what it causing the error. After asking all of its
questions the installer
Jonathan Brandmeyer wrote:
I am attempting to install Borland JBuilder 7 on a Sarge system with the
Sun JRE/SDK 1.4.1-3 already installed (directly from Sun). The
installer is written in Java, so unfortunately I am not able to figure
out exactly what it causing the error. After asking all of its
Roberto Sanchez wrote:
HFS is the apple file system. Was the CD burned on a Mac? Maybe
you do not all the necessarf stuff to support the HFS filesystem.
It could also be a kernel bug.. Interesting.
The disk is mounted as an iso9660 disk. The same CD contains installers
for Windows,
41 matches
Mail list logo
