| 2006-09-20 02:08:20 |
Ben Collins |
linux-meta: statusexplanation |
|
This really makes no sense to me. Technically this should not even be possible unless you did something strange with your system.
First off, the -386 package is not available from the amd64 repository. There's no way synaptic should have even seen it.
Secondly, even if you did install the -386 kernel on an 64-bit system, it would not boot, simply because the 32-bit -386 kernel would not be able to run the x86_64 binaries.
So my guess is that you somehow manually installed the 64-bit kernel at some point and are now getting hosed by an upgrade that is setting your system back correctly.
What I need from you is the output of the following commands:
dpkg --print-architecture
uname -a
ls -l /boot/.
file -L /lib/libc.so.6
dpkg -l | grep linux
Send this in a follow up comment. Thanks. |
|
| 2007-06-06 18:12:46 |
Brian Murray |
linux-meta: statusexplanation |
This really makes no sense to me. Technically this should not even be possible unless you did something strange with your system.
First off, the -386 package is not available from the amd64 repository. There's no way synaptic should have even seen it.
Secondly, even if you did install the -386 kernel on an 64-bit system, it would not boot, simply because the 32-bit -386 kernel would not be able to run the x86_64 binaries.
So my guess is that you somehow manually installed the 64-bit kernel at some point and are now getting hosed by an upgrade that is setting your system back correctly.
What I need from you is the output of the following commands:
dpkg --print-architecture
uname -a
ls -l /boot/.
file -L /lib/libc.so.6
dpkg -l | grep linux
Send this in a follow up comment. Thanks. |
We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future. |
|
