On Fri, Mar 11, 2005 at 01:20:00PM +0100, Andreas Tille wrote:
On Fri, 11 Mar 2005, Miros/law Baran wrote:
it worked. I really regard this problem as serious because it
probably leaves people with SATA hardware with an unbootable system
after kernel-image updates, because the kernel image
On Mon, 14 Mar 2005, Andrew Pollock wrote:
Sorry, I do not know anything about partition labels but if this is
the solution it should be done in the installer and if this works in
Grub menu.lst this should be done here as well.
I gave some of the relevant people in the d-i team an education on the
On Thu, 10 Mar 2005, Jesús Roncero wrote:
I've recently had those problems also on a Dell server, using SATA too. The
fine guys from #gpul helped me a lot on this. Basically, what happened to me
is that kernel 2.4 mapped the SATA drive as /dev/hdc and kernel 2.6 mapped it
to /dev/sda
Well, after
11.03.2005 pisze Andreas Tille ([EMAIL PROTECTED]):
it worked. I really regard this problem as serious because it
probably leaves people with SATA hardware with an unbootable system
after kernel-image updates, because the kernel image packages just
reinsert root=/dev/hda? into grub's
Miros/law Baran schrieb am Freitag, 11. März 2005 um 12:55:09 +0100:
11.03.2005 pisze Andreas Tille ([EMAIL PROTECTED]):
it worked. I really regard this problem as serious because it
probably leaves people with SATA hardware with an unbootable system
after kernel-image updates, because
On Fri, 11 Mar 2005, Miros/law Baran wrote:
it worked. I really regard this problem as serious because it
probably leaves people with SATA hardware with an unbootable system
after kernel-image updates, because the kernel image packages just
reinsert root=/dev/hda? into grub's menu.lst. Any idea
On Fri, 2005-03-11 at 13:01 +0100, Joerg Friedrich wrote:
Miros/law Baran schrieb am Freitag, 11. März 2005 um 12:55:09 +0100:
11.03.2005 pisze Andreas Tille ([EMAIL PROTECTED]):
it worked. I really regard this problem as serious because it
probably leaves people with SATA hardware
11.03.2005 pisze Joerg Friedrich ([EMAIL PROTECTED]):
Miros/law Baran schrieb am Freitag, 11. Mrz 2005 um 12:55:09 +0100:
11.03.2005 pisze Andreas Tille ([EMAIL PROTECTED]):
it worked. I really regard this problem as serious because it
probably leaves people with SATA hardware with an
Joerg Friedrich schrieb am Freitag, 11. März 2005 um 13:01:58 +0100:
Miros/law Baran schrieb am Freitag, 11. März 2005 um 12:55:09 +0100:
11.03.2005 pisze Andreas Tille ([EMAIL PROTECTED]):
it worked. I really regard this problem as serious because it
probably leaves people with SATA
On Fri, Mar 11, 2005 at 12:51:16PM +0100, Andreas Tille wrote:
On Thu, 10 Mar 2005, Jesús Roncero wrote:
I've recently had those problems also on a Dell server, using SATA too. The
fine guys from #gpul helped me a lot on this. Basically, what happened to
me
is that kernel 2.4 mapped the
On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille [EMAIL PROTECTED]
wrote:
ERROR: Removing 'trm290': Device or resource busy
ERROR: Removing 'vis82cxxx': Device or resource busy
pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
On Thu, 10 Mar 2005, Mike Hommey wrote:
On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille [EMAIL PROTECTED] wrote:
ERROR: Removing 'trm290': Device or resource busy
ERROR: Removing 'vis82cxxx': Device or resource busy
pivot_root: No such file or directory
/sbin/init: 432: cannot open
On Thu, 10 Mar 2005 15:48:55 +0100 (CET)
Andreas Tille [EMAIL PROTECTED] wrote:
On Thu, 10 Mar 2005, Mike Hommey wrote:
On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille
[EMAIL PROTECTED] wrote:
ERROR: Removing 'trm290': Device or resource busy
ERROR: Removing 'vis82cxxx':
On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille wrote:
Hi,
I've got a new Dell machine which I was able to install with Kernel 2.4.27.
It has a SATA drive but I disabled SATA in BIOS according to the manuals.
All I write in the following has this SATA disabled BIOS setting.
As I
might be fixable by regenerating a new initrd for the 2.6 kernel:
mkinitrd -v /boot/initrd-2.6.x-x.img 2.6.x-x
make sure to add this line to the grube menue.lst:
initrd /boot/initrd-2.6.x-x.img
On Fri, 11 Mar 2005 02:01:42 +1100, Paul Hampson wrote
On Thu, Mar 10, 2005 at 03:10:12PM +0100,
On Thu, 10 Mar 2005, Jacob S wrote:
Which version of the Debian-Installer did you use? We had similar
symptoms on a new Dell recently at work and had to grab the latest daily
build to get a working version. I can check on the exact date of the
daily build we used, if you want.
On my desk I see
On Thu, 10 Mar 2005, Thomas Schneller wrote:
mkinitrd -v /boot/initrd-2.6.x-x.img 2.6.x-x
I guess you mean here s/-v/-o/, right?
Well, I did so
mkinitrd -o /boot/initrd.img-2.6.10-1-686 2.6.10-1-686
(under
# uname -a
Linux wr-linux03 2.4.27-1-386 #1 Wed Dec 1 19:43:08 JST 2004 i686 GNU/Linux
Andreas Tille schrieb am Donnerstag, 10. März 2005 um 15:10:12 +0100:
Hi,
I've got a new Dell machine which I was able to install with Kernel 2.4.27.
It has a SATA drive but I disabled SATA in BIOS according to the manuals.
All I write in the following has this SATA disabled BIOS setting.
On Thu, 10 Mar 2005 17:04:55 +0100 (CET)
Andreas Tille [EMAIL PROTECTED] wrote:
On Thu, 10 Mar 2005, Jacob S wrote:
Which version of the Debian-Installer did you use? We had similar
symptoms on a new Dell recently at work and had to grab the latest
daily build to get a working version. I
On Thursday, 10 de March de 2005 15:10, Andreas Tille wrote:
I tried to upgrade to a 2.6.x kernel but failed always with kernel_panic.
I tried 2.6.8, 2.6.8 and 2.6.10 (here -1-386 and -1-686 versions) and
all failed with the same result:
ERROR: Removing 'trm290': Device or resource busy
20 matches
Mail list logo
