El Thu, 11 Jun 2015 16:20:53 +0200, laura escribió:
hola!
(ese html...)
esta mañana, al arrancar el sistema Debian de mi portátil me ha
anunciado que debido a un kernel panic no podía montar el disco donde
está linux instalado. Concretamente después de acceder al sistema
mediante Grub de
I have an i7-3612Qe system that has been giving kernel panics when running a
custom video streaming application pretty consistently after a couple minutes.
After the kernel panic, the machine reboots. When I turn off turbo mode in the
BIOS, the panics happen less frequently. Other BIOS
Bonjour,
Sur un portable, j'ai un kernel panic:
kernel panic - not syncing: No init found. try passing init= option to kernel
J'arrive a me logger en passant par mon CD rescue.
J'ai essayé de faire un update-initramfs, mais rien n'y fait. :-(
Je ne sais pas trop quoi faire, et j'hésite à
'initrd' en ajoutant un bon path de type
'/boot/initrd.img...'
Une fois booté, faire un 'grub-update'.
Bon courage!
Le 30/11/2014 11:19, Zuthos Oddy a écrit :
Bonjour,
Sur un portable, j'ai un kernel panic:
kernel panic - not syncing: No init found. try passing init= option to kernel
bonsoir,
quels sont les arguments de boot du noyau que tu as utilisé ? (en appuyant
sur 'e' dans le menu grub)
Le 30 nov. 2014 11:19, Zuthos Oddy zut...@laposte.net a écrit :
Bonjour,
Sur un portable, j'ai un kernel panic:
kernel panic - not syncing: No init found. try passing init= option
yo tengo el mismo problema. con el kernel 3.2.0-4 (32 bits) o inferior
se resuelve tu problema,
por cierto este fallo creo que tiene relación con el chip gráfico
nVidia, ahun no descubro (en mis ratos libres ) el por que de la falla,
con el driver privativo y el libre (nouveau) es el mismo
que le instale Debian Testing como tengo costumbre de hacer
hace mucho tiempo, el problema es que cada vez que ejecutaba Iceweasel
el sistema se congelaba de tal manera que ni las Magic Keys
funcionaba, un kernel panic en toda regla.
(...)
¿Quien de ustedes ha pasado por esto? ¿Alguna
ejecutaba Iceweasel
el sistema se congelaba de tal manera que ni las Magic Keys
funcionaba, un kernel panic en toda regla.
El problema en principio parecia ser Iceweasel, que tiene ya varios
bugs reportados con el mismo comportamiento de simplemente congelar la
maquina completamente y estaban
costumbre de hacer hace mucho
tiempo, el problema es que cada vez que ejecutaba Iceweasel el sistema
se congelaba de tal manera que ni las Magic Keys funcionaba, un kernel
panic en toda regla.
(...)
¿Quien de ustedes ha pasado por esto? ¿Alguna sugerencia?
Que otras distribuciones funcionen sin
140 + ECS Nvidia 6100 - M2 a la
que le instale Debian Testing como tengo costumbre de hacer hace mucho
tiempo, el problema es que cada vez que ejecutaba Iceweasel el sistema
se congelaba de tal manera que ni las Magic Keys funcionaba, un kernel
panic en toda regla.
(...)
¿Quien de ustedes ha
Good day!
I am getting kernel panic with the kernel version 2.6.32 - call trace is
available here:
http://i.imgur.com/kHfhRy9.jpg
Is there any ideas how to deal with this?
Thank you!
--
Vladimir Zagaychuk (VZ485-RIPE)
Hi
On Wed, Nov 06, 2013 at 12:39:42PM +0200, Vladimir Zagaychuk wrote:
Good day!
I am getting kernel panic with the kernel version 2.6.32 - call trace is
available here:
http://i.imgur.com/kHfhRy9.jpg
Is there any ideas how to deal with this?
Thank you!
Not really - to make sense
El Sun, 04 Aug 2013 10:30:14 -0300, Debian GMail escribió:
(...)
Lecciones aprendidas:
1 - Intel es poco claro al momento de especificar la aparatología
(hardware) compatible.
Supongo que cuando dices Intel te refieres al fabricante de la placa
base, que en tu caso (y si mal no recuerdo)
El 19/06/13 10:32, Camaleón escribió:
El Tue, 18 Jun 2013 17:24:37 -0300, Javier ArgentinaBBAR escribió:
Estimados:
Ya busqué por todas partes, y se me han quemado los papeles, por lo
solicito vuestra ayuda.
Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad
dual channel
El 04/08/13 15:30, Debian GMail escribió:
Bien. La solución ha sido fácil. Como Camaleón dijo, utilizo a partir de
hoy dos bancos de memorias Kingston KVR1333D3N9H/4G.
Es el tiempo que me costó poderlas encontrar por los serios problemas de
importaciones, y el inmenso favor que me hizo una
El día martes, 18 de junio de 2013, a las 17:24:37, Javier escribió:
JA Tengo una máquina con las siguiente características:
JA Desktop Board Intel® DH55PJ Intel® Core™ i3-540 Processor 1 x 2 GB RAM
JA Linux jap 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux
JA Me gasté unos pesos en un
Repito: no anda con el núcleo de 64 bits de Linux.
Me queda hacer una prueba con un núcleo x86 para ver si hay variación,
pero eso implica bajar el live-cd que aún no he tenido tiempo.
Pues no te va a quedar más remedio que probar vía x86, a ver...
no lo creo, hay otra solucion.
si es un
El Tue, 18 Jun 2013 17:24:37 -0300, Javier ArgentinaBBAR escribió:
Estimados:
Ya busqué por todas partes, y se me han quemado los papeles, por lo
solicito vuestra ayuda.
(...)
Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad
dual channel de la placa, por lo que
El 19/06/13 10:32, Camaleón escribió:
Me gasté unos pesos en un par de memorias de 4Gb para usar la capacidad
dual channel de la placa, por lo que instalé 2 x 4 GB RAM
http://www.ec.kingston.com/ecom/configurator_new/PartsInfo_ar.asp?
El Wed, 19 Jun 2013 11:34:42 -0300, Debian GMail escribió:
El 19/06/13 10:32, Camaleón escribió:
Me gasté unos pesos en un par de memorias de 4Gb para usar la
capacidad dual channel de la placa, por lo que instalé 2 x 4 GB RAM
Estimados:
Ya busqué por todas partes, y se me han quemado los papeles, por lo
solicito vuestra ayuda.
Tengo una máquina con las siguiente características:
Desktop Board Intel® DH55PJ
http://www.intel.la/content/www/xl/es/motherboards/desktop-motherboards/desktop-board-dh55pj.html
Intel® Core™
On Tue, 18 Jun 2013 17:24:37 -0300
Javier ArgentinaBBAR javier.debian.bb...@gmail.com wrote:
Le pasaste el memtest para empezar a descartar ?
Saludos
--
BSS Servicio :. $telnet bayresmail.com.ar 2323
MamaLibre Reader :. http://mamalibre.com.ar/reader/
Buscador del Sur :.
Hola Javier:
El 18/06/13 17:24, Javier ArgentinaBBAR escribió:
Estimados:
Ya busqué por todas partes, y se me han quemado los papeles, por lo
solicito vuestra ayuda.
Tengo una máquina con las siguiente caracterÃsticas:
Desktop Board Intel® DH55PJ
El día 18 de junio de 2013 17:39, Fabián Bonetti
mama21mama2...@yahoo.com.ar escribió:
Le pasaste el memtest para empezar a descartar ?
Saludos
Las memorias fueron probadas y están bien.
JAP
--
To UNSUBSCRIBE, email to debian-user-spanish-requ...@lists.debian.org
with a subject of
El día 18 de junio de 2013 18:04, Walter O. Dari wlin...@gmail.com escribió:
Hola Javier:
Supongo que ya lo habrás visto, pero no tendrá que ver con la velocidad de
las memorias ?
Me ha pasado con algunas PM Intel de cambiarle la configuración auto en la
velocidad de la memoria, colocarle
El 18/06/13 23:17, Javier ArgentinaBBAR escribió:
La placa no tiene forma de cambiar la velocidad de las memorias, pues
las reconoce automáticamente.
Y las está reconociendo bien.
Repito: no anda con el núcleo de 64 bits de Linux.
Me queda hacer una prueba con un núcleo x86 para ver si hay
Recuerdo que hace 2 meses atrás instale debian en un equipo core 2 quad que
trae 4 gb en memoria si no me equivoco unas DDR2 PC2-5300 y también medio
un error de kernel panic, y la iso que habia bajado era una AMD64 al final
recuerdo que baje la iso para x86
El 18 de junio de 2013 17:25
One change I made shortly before the problems started that might be
relevant: I enabled i386 architecture support (it's amd64 laptop).
On Tue, Jun 4, 2013 at 7:36 AM, Ari Epstein aepstein...@gmail.com wrote:
Hi all,
Got a new laptop and installed wheezy a few weeks ago. I noticed the HDMI
I was able to copy almost everything from dd images to a new set
of filesystems. The only thing that was excluded from the transfer
was /var/cache/apt, because something in there was causing the problem.
I performed the transfer by booting to a second system. Interestingly,
when this problem
On Thursday 11 April 2013 23:23:30 Roger Leigh wrote:
You could also try upgrading to a newer kernel e.g. 3.8.x. I've
done this myself due to btrfs issues with older kernels; you might
need to hand-build it though since Debian doesn't yet have it.
See kernel-package.
Debian has it in
So it looks like btrfs really is still experimental.
I have / and /var on two separate btrfs partitions and I consistently get
a kernel panic when I run aptitude update (see the end). I also managed
to get the same results by using find and dd to read every file in /var.
Although my oops
On Thu, Apr 11, 2013 at 03:50:19PM -0500, Alex Robbins wrote:
So it looks like btrfs really is still experimental.
I have / and /var on two separate btrfs partitions and I consistently get
a kernel panic when I run aptitude update (see the end). I also managed
to get the same results
Hola muy buenas, al arrancar un debian un pelín antiguo que tenemos un
proxy http montado, me ha reportado el siguiente error...
Según he leído, puede deberse a que el initrd esté dañado.
Alguien ha tenido el mismo error??
Saludos y gracias de antemano.
--
To UNSUBSCRIBE, email to
Boa tarde a todos,
Em primeiro lugar gostaria de agradecer a todos, pois o
problema foi resolvido de maneira adequada.
Quanto ao problema : Depois que retirei as hds e instalei em
outra maquina, consegui dar o boot normalmente (o que me espantou, pois
já considerava um caso
Congratulations =D
Em 18 de setembro de 2012 14:57, Informática HUT
c...@hutaubate.com.brescreveu:
Boa tarde a todos,
Em primeiro lugar gostaria de agradecer a todos, pois o problema
foi resolvido de maneira adequada.
Quanto ao problema : Depois que retirei as hds e
Bem lembrado,
Boa parte dos kernel panic que eu presenciei tinha sido hardware,
principalmente memórias... testar o hardware é uma das coisas a se
fazer nessas ocasiões...
[ ] 's
--
| .''`. A fé não dá respostas. Só impede perguntas.
| : :' :
| `. `'`
| `- Je vois tout
Bom dia a todos,
Estou com uma situação complicada por aqui, no fim de semana minha
máquina de backup apresentou a seguinte mensagem de erro:
[0.220408] initramfs unpacking failed : junk in compressed archive
[0.720799] kernel panic - not syncing : VFS : unable to mount root
fs
initramfs está corrompido (lixo no arquivo
comprimido). Não sei como isso pode ter acontecido.
[0.720799] kernel panic - not syncing : VFS : unable to mount
root fs on unknown-block (254,4)
Não consigo entrar no single-mode, na verdade a unica coisa que
consigo é entrar no prompt do
:
[0.220408] initramfs unpacking failed : junk in compressed archive
Aparentemente o arquivo initramfs está corrompido (lixo no arquivo
comprimido). Não sei como isso pode ter acontecido.
[0.720799] kernel panic - not syncing : VFS : unable to mount
root fs on unknown-block (254,4)
Não
apresentou a seguinte mensagem de erro:
[0.220408] initramfs unpacking failed : junk in compressed archive
Aparentemente o arquivo initramfs está corrompido (lixo no arquivo
comprimido). Não sei como isso pode ter acontecido.
[0.720799] kernel panic - not syncing : VFS : unable to mount
] initramfs unpacking failed : junk in compressed
archive
Aparentemente o arquivo initramfs está corrompido (lixo no arquivo
comprimido). Não sei como isso pode ter acontecido.
[0.720799] kernel panic - not syncing : VFS : unable to mount
root fs on unknown-block (254,4)
Não
como isso pode ter acontecido.
[0.720799] kernel panic - not syncing : VFS : unable to mount
root fs on unknown-block (254,4)
Não consigo entrar no single-mode, na verdade a unica coisa que
consigo é entrar no prompt do grub (teclando c ao escolher o kernel.
pergunta
Bonjour à tous,
J'ai mis sur mon PC les répertoires /boot et /usr
sur un disque SSD,
les autres répertoires sur un disque dur SATA.
Une fois sur deux, au boot, j'ai droit à un Kernel panic.
J'éteins le PC, le relance et 3 à 4 fois à nouveau un Kernel panic.
Puis enfin, au prochain reboot, tout
On Sun, 16 Sep 2012 22:23:40 +0200
andre_deb...@numericable.fr wrote:
J'ai mis sur mon PC les répertoires /boot et /usr
sur un disque SSD,
les autres répertoires sur un disque dur SATA.
Ben déjà avoir une copie des 2 dirs sur chaque HD, puis tester
lequel pose PB (SI c'est réellement un PB de
Pessoal, obrigado pelas respostas, achei a solução, agora meu singelo
notebook está bala.
No meu caso eu estava desabilitando algum módulo necessário para montar
as partições do HD, mesmo elas sendo reconhecidas.
Utilizei o make localmodconfig (excelente).
Aí depois dele dei uma tunada nas opções
Pessoal, resumindo meu problema, depois de recompilar o Kernel meu
sistema não inicia, fiz um teste para ver se era algum módulo faltando e
não era, pois no teste recompilei o Kernel com as configurações antigas
e retirei apenas o suporte a virtualização. Na minha compilação utilizei
o fonte do
faltou vc gera a imagem
na pasta /lib/module
digite
mkinitramfs -o /boot/initrd-kernel versao do kernel
Ai pode reiniciar.
Em 1 de agosto de 2012 15:31, Adiel de Lima Ribeiro
adiel.netad...@gmail.com escreveu:
Pessoal, resumindo meu problema, depois de recompilar o Kernel meu
sistema não
Tenta fazer assim.
apt-get install kernel-package libncurses5-dev fakeroot wget bzip2
build-essential
cd /usr/src
wget http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.4.7.tar.bz2
tar jxvf linux-3.4.7.tar.bz2
rm -rf linux
ln -s linux-3.4.7 linux
cd linux
cp /boot/config-SEU_KERNEL_DO_DEBIAN
romfs
Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block
Estou usando o Debian amd64, o sistema de arquivos é ext4 e está
habilitado no kernel, o método de compressão dele é lzma, também habilitei
o ROM filesystem support, o squash fs 4.0, o cramfs e o partition type
msdos
noite.
Após recompilar meu kernel, quando inicio o sistema com o kernel
recompilado estou tendo os seguintes problemas:
O sistema não boot e me retorna as seguintes mensagens de erro:
No filesystem could mount root, tried: cramfs vfat sysv v7 romfs
Kernel panic - not syncing: VFS: unable
com o kernel
recompilado estou tendo os seguintes problemas:
O sistema não boot e me retorna as seguintes mensagens de erro:
No filesystem could mount root, tried: cramfs vfat sysv v7 romfs
Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block
Estou usando o Debian amd64
recompilar meu kernel, quando inicio o sistema com o kernel
recompilado estou tendo os seguintes problemas:
O sistema não boot e me retorna as seguintes mensagens de erro:
No filesystem could mount root, tried: cramfs vfat sysv v7 romfs
Kernel panic - not syncing: VFS: unable to mount
tendo os seguintes problemas:
O sistema não boot e me retorna as seguintes mensagens de erro:
No filesystem could mount root, tried: cramfs vfat sysv v7 romfs
Kernel panic - not syncing: VFS: unable to mount rootfs on unknow block
Estou usando o Debian amd64, o sistema de arquivos é ext4 e
Pessoal, boa noite.
Após recompilar meu kernel, quando inicio o sistema com o kernel
recompilado estou tendo os seguintes problemas:
O sistema não boot e me retorna as seguintes mensagens de erro:
No filesystem could mount root, tried: cramfs vfat sysv v7 romfs
Kernel panic - not syncing: VFS
I saw a very strange error while installing debian cd -
kernel panic - not syncing vfs unable to mount root fs on unknown block
(254,6)
What might be the reason for this error? !!!
--
Harshad Joshi
?
Kirill Sotnikov
Maxifier, Inc.
phone: +79179468634
skype: wlan1024
On Fri, Jul 6, 2012 at 1:38 PM, Harshad Joshi firewal...@gmail.comwrote:
I saw a very strange error while installing debian cd -
kernel panic - not syncing vfs unable to mount root fs on unknown block
(254,6)
What
On Fri, 06 Jul 2012 15:08:18 +0530, Harshad Joshi wrote:
(please, no html posts, thanks...)
I saw a very strange error while installing debian cd -
kernel panic - not syncing vfs unable to mount root fs on unknown block
(254,6)
What might be the reason for this error? !!!
I've never
Hi,
I just installed 3.2.0-3-686-pae, but got a kernel panic when trying
to boot with it. As transcribed from my phone-camera screenshot
(there are 10 more lines of output I can transcribe if that'd help):
[ 0.987169] Kernel panic - not syncing : VFS: Unable to mount root
fs on unknown
On Fri 06 Jul 2012 at 03:23:33 -0700, John Magolske wrote:
I just installed 3.2.0-3-686-pae, but got a kernel panic when trying
to boot with it. As transcribed from my phone-camera screenshot
(there are 10 more lines of output I can transcribe if that'd help):
[ 0.987169] Kernel panic
On 4 March 2012 01:28, Brendon Higgins blhigg...@gmail.com wrote:
Any more ideas? As I said, I tried getting kdump working but have been having
trouble getting it to behave.
One more thought, but it's a bit of a long shot as to whether you have
the equipment. The most watertight way I know of
On 2012-03-04 09:16 +0100, Jason Heeris wrote:
On 4 March 2012 01:28, Brendon Higgins blhigg...@gmail.com wrote:
Any more ideas? As I said, I tried getting kdump working but have been having
trouble getting it to behave.
One more thought, but it's a bit of a long shot as to whether you have
Hi,
Jason Heeris wrote (Sun March 4, 2012):
The most watertight way I know of to capture kernel
output is a serial port and another computer. If, by any chance, you
have one on your machine
Not really an option (at least, not an easy one), I'm afraid. I only have two
machines, and neither of
0 /dev/whatever' for long
enough to reproduce the crash. Just in case.
Thanks for the tip. I gave that a try using the manual invocation of a kernel
panic (i.e., echo c /proc/sysrq-trigger) but I still get nothing in
/var/log/messages about this event. So, I'm doubtful this'll work when a real
Hi list,
For the better part of a year, now, something has been causing my machine to
freeze. The mouse stops moving on the screen, pressing any key (including keys
that should toggle lights) does nothing. The freezes are intermittent, without
warning, and I've been unable to determine if
On the next boot, /var/log/messages shoild contain the last printk's from
the kernel which would include any panic.
So, one should be able to tail /var/log messages and see what the kernel
did at the time of the freeze.
Remembdr that the fresh boot is appendex to /var/log/messages, so you need
On 2 March 2012 12:50, Charles Krinke charles.kri...@gmail.com wrote:
So, one should be able to tail /var/log messages and see what the kernel did
at the time of the freeze.
I've had problems with write caching causing the last few messages to
be lost after a panic*, so if you don't see
, j'obtiens immédiatement un plantage juste après grub :
Kernel panic... gnagna ... not syncing.
J'ai un peu vadrouillé sur les bigs reports, je ne semble pas être le
seul dans ce cas, mais je ne sais pas trop comment résoudre le
problème : je ne sais pas afficher les messages d'erreur au boot (je
mentionnés
dans le titre : le PC plante (une fois par mois, en gros), et quand
j'essaye de rebooter, j'obtiens immédiatement un plantage juste après
grub : Kernel panic... gnagna ... not syncing.
J'ai un peu vadrouillé sur les bigs reports, je ne semble pas être le
seul dans ce cas, mais je ne sais
On Tue, 28 Feb 2012 19:06:26 +0100
Nicolas FRANCOIS nicolas.franc...@free.fr wrote:
Vérifier si la RAM est en auto pour les timings.
Si c'est le cas, l'analyser avec un utilitaire et la régler
manuellement.
--
First Corollary of Taber's Second Law:
Machines that piss people off get
Le Tue, 28 Feb 2012 19:18:07 +0100,
Bzzz lazyvi...@gmx.com a écrit :
On Tue, 28 Feb 2012 19:06:26 +0100
Nicolas FRANCOIS nicolas.franc...@free.fr wrote:
Vérifier si la RAM est en auto pour les timings.
Si c'est le cas, l'analyser avec un utilitaire et la régler
manuellement.
Memtest
On Tue, 28 Feb 2012 20:32:38 +0100
Nicolas FRANCOIS nicolas.franc...@free.fr wrote:
Memtest va me dire cela ?
Pour le CAS vi, mais le RAS c'est moins sur; mais il-y-a des tas
d'utilitaires sur le net qui font ça très bien.
Si oui, que dois-je guetter dans les
affichages ? Quels sont les
Le Tue, 28 Feb 2012 19:12:39 +0100,
Bernard Schoenacker bernard.schoenac...@free.fr a écrit :
bonjour,
serait il possible de modifier le fichier de conf :
cat /etc/default/bootlogd
# Run bootlogd at startup ?
BOOTLOGD_ENABLE=Yes
en pager : most
Le Tue, 28 Feb 2012 19:12:39 +0100,
Bernard Schoenacker bernard.schoenac...@free.fr a écrit :
bonjour,
serait il possible de modifier le fichier de conf :
cat /etc/default/bootlogd
# Run bootlogd at startup ?
BOOTLOGD_ENABLE=Yes
en pager : most
On Tue, 28 Feb 2012 20:50:09 +0100
Nicolas FRANCOIS nicolas.franc...@free.fr wrote:
Et
où lit-on les bootlogs ? Dans /var/log ?
/var/log/messages
--
Darth Vader sleeps with a Teddywookie.
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists
Pour
On Tue, 28 Feb 2012 20:50:42 +0100
Nicolas FRANCOIS nicolas.franc...@free.fr wrote:
Sinon, je n'ai pas trouvé l'option memtest dans le boot, comme j'en
avais une sous Ubuntu. C'est exprès ?
Contrairement à trudububu, Debian considère que l'admin est un
adulte qualifié; il est donc de sa
Le Tue, 28 Feb 2012 20:50:42 +0100,
Nicolas FRANCOIS nicolas.franc...@free.fr a écrit :
Le Tue, 28 Feb 2012 19:12:39 +0100,
Bernard Schoenacker bernard.schoenac...@free.fr a écrit :
bonjour,
serait il possible de modifier le fichier de conf :
cat /etc/default/bootlogd
Bonjour,
Suite à une mise à jour hier soir, j'ai eu quelques kernel panic de
façon relativement aléatoire sur l'installation de testing sur mon macbook.
C'est la première fois que je suis confronté à des kernel panic et je ne
sais pas trop comment interpréter ces choses là.
J'ai fais une photo
On Mon, 26 Dec 2011 15:34:23 +0100
Goldy go...@goldenfish.info wrote:
C'est la première fois que je suis confronté à des kernel panic et je ne
sais pas trop comment interpréter ces choses là.
Il faut en faire une mauvaise interprétation.
J'ai essayé de changer de noyaux (en repassant à la
ran a
dpkg --configure -a to finish the job.
However, now, when I try to use my Windows HVM, I always get a kernel
panic dealing with the vbd. For example...
8=
kernel:[ 1919.981706] general protection fault: [#1] SMP
kernel:[ 1919.981714] last sysfs file: /sys
On 11/9/2011 7:55 PM, David Howland wrote:
Recently I lost power (along with much of New England) for eight days.
When the juice started flowing again, I restarted my Xen server (Debian
Squeeze, dual Xeon (8 cores), 16GB RAM), which came up fine but had a
pile of package updates pending...
On 11/9/2011 10:17 PM, Stan Hoeppner wrote:
On 11/9/2011 7:55 PM, David Howland wrote:
8=
kernel:[ 1919.981706] general protection fault: [#1] SMP
kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent
kernel:[ 1919.981870] Stack:
kernel:[
On 11/9/2011 9:56 PM, David Howland wrote:
On 11/9/2011 10:17 PM, Stan Hoeppner wrote:
On 11/9/2011 7:55 PM, David Howland wrote:
8=
kernel:[ 1919.981706] general protection fault: [#1] SMP
kernel:[ 1919.981714] last sysfs file: /sys/devices/vbd-3-832/uevent
Stephen Powell wrote:
On Tue, 01 Nov 2011 21:02:56 -0400 (EDT), Sian Mountbatten wrote:
Thank you all for your helpful advice and info.
I am giving up on squeeze because I get so many problems with
building
a series 3 kernel. I tried to download a kernel image from wheezy,
but
got
Arnt Karlsen wrote:
On Mon, 31 Oct 2011 13:56:46 -0700 (PDT), poenik...@operamail.com
wrote
in message
6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com:
On Oct 31, 7:20 pm, poenik...@operamail.com
poenik...@operamail.com wrote:
On Oct 31, 12:40 am, Stephen Powell
poenik...@operamail.com wrote:
On Oct 30, 8:10 pm, Hugo Vanwoerkom hvw59...@care2.com wrote:
snip
I suspect that my configuration of the kernel is at fault, but where
should I start looking for problems?
Problem solved by installing wheezy which comes with a 3.0.0 kernel.
Thank you all
On Mon, 31 Oct 2011 13:56:46 -0700 (PDT), poenik...@operamail.com wrote
in message
6a9c6581-5fbb-4848-9d92-81bf0dbce...@j36g2000prh.googlegroups.com:
On Oct 31, 7:20 pm, poenik...@operamail.com
poenik...@operamail.com wrote:
On Oct 31, 12:40 am, Stephen Powell zlinux...@wowway.com wrote:
On Mon, 31 Oct 2011 10:25:04 -0400 (EDT), Hugo Vanwoerkom wrote:
Stephen Powell wrote:
I would recommend using something like make localmodconfig to strip
out drivers your hardware doesn't need. There are many hidden
dependencies, such as SCSI support, that are not obvious.
...
That will
On Mon, 31 Oct 2011 14:54:37 -0400 (EDT), poenik...@operamail.com wrote:
I followed the instructions given in Kernel.htm and built a kernel
from the source tree I had
downloaded from www.kernel.org after issuing make-kpkg debian. I also
patched kernel-package
using the patch file
On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote:
It is important that you *not* use traditional device nomenclature, such
as
/dev/hda1 /dev/sda1
Why?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote:
On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote:
It is important that you *not* use traditional device nomenclature, such
as
/dev/hda1
/dev/sda1
Why?
Two reasons. First, whether an IDE hard disk shows up as
On Tue, 01 Nov 2011 20:00:54 -0400, Stephen Powell wrote:
On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote:
On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote:
It is important that you *not* use traditional device nomenclature,
such as
/dev/hda1 /dev/sda1
Why?
On Wed, 02 Nov 2011 01:10:02 +0100, Stephen Powell wrote:
On Tue, 01 Nov 2011 19:46:13 -0400 (EDT), Walter Hurry wrote:
On Tue, 01 Nov 2011 19:43:20 -0400, Stephen Powell wrote:
It is important that you *not* use traditional device nomenclature,
such as
/dev/hda1
/dev/sda1
Why?
On Tue, 01 Nov 2011 20:43:12 -0400 (EDT), Walter Hurry wrote:
But my (single internal) hard disk is always /dev/sda, and my two
external USB disks are always /dev/sdb and /dev/sdc. So what difference
does it make?
You mean that *so far* your internal hard disk is always /dev/sda
and *so
On Tue, 01 Nov 2011 21:02:56 -0400 (EDT), Sian Mountbatten wrote:
Thank you all for your helpful advice and info.
I am giving up on squeeze because I get so many problems with building
a series 3 kernel. I tried to download a kernel image from wheezy, but
got problems when I tried to
down squeeze, rebooted and chose the new 3.0.4 kernel. It
displayed an
error message (kernel panic) to the effect that it could not load the
root fs.
What have I done wrong?
I would recommend using something like make localmodconfig to strip
out drivers your hardware doesn't need. There are many
did not have
the relevant hardware.
...
I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
displayed an
error message (kernel panic) to the effect that it could not load the
root fs.
What have I done wrong?
I would recommend using something like make localmodconfig
On Oct 31, 7:20 pm, poenik...@operamail.com
poenik...@operamail.com wrote:
On Oct 31, 12:40 am, Stephen Powell zlinux...@wowway.com wrote:
Also, I recommend that you read
http://users.wowway.com/~zlinuxman/Kernel.htm
for a fairly comprehensive tutorial on kernel building in Debian
installed using
dpkg. grub was run which found the Linux kernels as well as Ubuntu
11.10.
I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
displayed an
error message (kernel panic) to the effect that it could not load the
root fs.
What have I done wrong?
I remember not choosing
-10.00.Custom_i386.deb which I
installed using
dpkg. grub was run which found the Linux kernels as well as Ubuntu
11.10.
I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
displayed an
error message (kernel panic) to the effect that it could not load the
root fs.
What have I done
of Debian packages
which included linux-image-3.0.4_3.0.4-10.00.Custom_i386.deb which I
installed using
dpkg. grub was run which found the Linux kernels as well as Ubuntu
11.10.
I closed down squeeze, rebooted and chose the new 3.0.4 kernel. It
displayed an
error message (kernel panic
101 - 200 of 2637 matches
Mail list logo
