Camaleón wrote:
On Sun, 21 Nov 2010 12:19:24 -0600, Hugo Vanwoerkom wrote:
Camaleón wrote:
So, you have changed not only the board but also the disk interface (it
was ide and now is sata)? Does the new kernel has "libata" module
loaded?
It was a sata disk in an external enclosure connected
On Sun, 21 Nov 2010 12:19:24 -0600, Hugo Vanwoerkom wrote:
> Camaleón wrote:
>> So, you have changed not only the board but also the disk interface (it
>> was ide and now is sata)? Does the new kernel has "libata" module
>> loaded?
>
> It was a sata disk in an external enclosure connected with U
Maybe now is a good time for you to put your Grub's menu config (either upload
the full file to an external server or attach the file to the message). Also,
include the output of "fdisk -l" that will help us to get a better
understanding of your current system structure :-)
I use SGD. I at
Camaleón wrote:
On Sun, 21 Nov 2010 10:55:53 -0600, Hugo Vanwoerkom wrote:
Camaleón wrote:
(...)
Or maybe your GRUB has to be properly updated for looking into the
right "root (hdx,n)" device?
Let me do a grub-install, but it finds the root device and boots it, but
it hangs after init
On Sun, 21 Nov 2010 10:55:53 -0600, Hugo Vanwoerkom wrote:
> Camaleón wrote:
(...)
>> Or maybe your GRUB has to be properly updated for looking into the
>> right "root (hdx,n)" device?
>>
>>
> Let me do a grub-install, but it finds the root device and boots it, but
> it hangs after initrd w
On Sun, 21 Nov 2010 09:58:00 -0600, Hugo Vanwoerkom wrote:
> I changed motherboards and now when I boot I get "waiting for root file
> system".
(...)
Same motherboard or a different (brand/model) one?
How are the sata BIOS settings now and then (sata/ahci/raid)? Maybe you
need to load a kernel
Camaleón wrote:
On Sun, 21 Nov 2010 09:58:00 -0600, Hugo Vanwoerkom wrote:
I changed motherboards and now when I boot I get "waiting for root file
system".
(...)
Same motherboard or a different (brand/model) one?
Different motherboard/cpu/memory old:epox 8VTAI new:asus M4N98TD EVO +
Athl
On Sat, 22 Aug 2009, Niu Kun wrote:
> Robert P. J. Day 写道:
> > On Fri, 21 Aug 2009, Robert P. J. Day wrote:
> >
> >
> > > On Sat, 22 Aug 2009, Niu Kun wrote:
> > >
> > > (with respect to getting my /dev/sda* device files built)
> > >
> > >
> > > > So here, your best choice seems to try.
> > > > he
Robert P. J. Day 写道:
On Fri, 21 Aug 2009, Robert P. J. Day wrote:
On Sat, 22 Aug 2009, Niu Kun wrote:
(with respect to getting my /dev/sda* device files built)
So here, your best choice seems to try.
here's my z60_hdparm.rules file:
i'm assuming that's a brand new rules fil
On Fri, 21 Aug 2009, Robert P. J. Day wrote:
> On Sat, 22 Aug 2009, Niu Kun wrote:
>
> (with respect to getting my /dev/sda* device files built)
>
> > So here, your best choice seems to try.
> > here's my z60_hdparm.rules file:
>
> i'm assuming that's a brand new rules file, right? not just add
On Sat, 22 Aug 2009, Niu Kun wrote:
(with respect to getting my /dev/sda* device files built)
> So here, your best choice seems to try.
> here's my z60_hdparm.rules file:
i'm assuming that's a brand new rules file, right? not just adding
to an existing rules file since i have no such file.
>
Robert P. J. Day 写道:
ok, here's what i think i've discovered (given that, again, i'm a
relative newcomer to debian), so i'm going to ask some dumb questions
which might go a long way to clarifying some things.
no matter what i tried, when i booted this (recently upgraded to)
etch system to t
Niu Kun wrote:
>>
>>
>>
> Pretty cool.
> Really appreciate your detailed reply.
>
>
NP. hope it helps or gives you at least an idea how I'm doing this.
I've had several times related issues as I've been using raid/lvm and also
encryption, so years ago I wrote my own scripts to create initrd
Emanoil Kotsev 写道:
Niu Kun wrote:
and last but not least it's pretty tricky to boot broken initram but not
too hard if you know the steps.
Would you please say something about this?
Or any useful link that can be referenced?
regards
First of all I would try to provi
Niu Kun wrote:
>> and last but not least it's pretty tricky to boot broken initram but not
>> too hard if you know the steps.
>>
> Would you please say something about this?
> Or any useful link that can be referenced?
>> regards
First of all I would try to provide the root kernel option. If y
ok, here's what i think i've discovered (given that, again, i'm a
relative newcomer to debian), so i'm going to ask some dumb questions
which might go a long way to clarifying some things.
no matter what i tried, when i booted this (recently upgraded to)
etch system to the newly-installed 2.6
Emanoil Kotsev 写道:
Robert P. J. Day wrote:
On Fri, 21 Aug 2009, Niu Kun wrote:
Have you ever run update-initramfs command manually on the
pre-compiled kernel? I remember that I fixed such a problem once.
Hope this will help. And look forward to your feedback.
nope -- as i me
Robert P. J. Day wrote:
> On Fri, 21 Aug 2009, Niu Kun wrote:
>
>> Have you ever run update-initramfs command manually on the
>> pre-compiled kernel? I remember that I fixed such a problem once.
>> Hope this will help. And look forward to your feedback.
>
> nope -- as i mentioned earlier, i'm
On Fri, 21 Aug 2009, Niu Kun wrote:
> Have you ever run update-initramfs command manually on the
> pre-compiled kernel? I remember that I fixed such a problem once.
> Hope this will help. And look forward to your feedback.
nope -- as i mentioned earlier, i'm fairly new to debian so a good
deal
On Fri, 21 Aug 2009, Robert P. J. Day wrote:
> that is the *ultimate* goal, but i'm doing this in steps. on the
> chance that it's the default 2.6.18 etch kernel, i just upgraded that
> to the 2.6.24 etchnhalf kernel. we'll see if that fixes things.
upgrading to the 2.6.24 etchnhalf kernel
Robert P. J. Day 写道:
On Fri, 21 Aug 2009, Niu Kun wrote:
Robert P. J. Day 写道:
(NOTE: please ignore my earlier and utterly misinformed plea
for help. turns out that, in attempting to mount /dev/sda1 as the
alleged root filesystem, the new 2.6 kernel was finding the
external backup h
On Fri, 21 Aug 2009, Niu Kun wrote:
> Robert P. J. Day 写道:
> > (NOTE: please ignore my earlier and utterly misinformed plea
> > for help. turns out that, in attempting to mount /dev/sda1 as the
> > alleged root filesystem, the new 2.6 kernel was finding the
> > external backup hard drive at /d
Robert P. J. Day 写道:
(NOTE: please ignore my earlier and utterly misinformed plea for
help. turns out that, in attempting to mount /dev/sda1 as the alleged
root filesystem, the new 2.6 kernel was finding the external backup
hard drive at /dev/sda1. no surprise that that wasn't bootable.
ack.
On Friday 2009 January 23 01:38:57 lovecreatesbeauty.g-mail.c0m wrote:
>I updated kernel on debian-40r6 (2.6.18) to 2.6.28 from kernel.org,
>and got the error* "Waiting for root file system..." when booting the
>new kernel.
Ah, I've seen that a few times, myself.
>The linux's hosted in VMware Wor
On Jan 23, 4:00 pm, "lovecreatesbeauty.g-mail.c0m"
wrote:
> kernel /boot/vmlinuz-2.6.28.1 root=/dev/sda1 ro
> initrd /boot/initrd.img-2.6.28.1
>
sorry the occurences of "28.1" above should be "28" .
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subj
[EMAIL PROTECTED] skrev:
> [This message has also been posted to linux.debian.user.]
> This is becoming a FAQ. There is a problem with udev.
> Before udev, there was a strong association between
> device names and devices. With udev, that association
> is much weaker.
> There's new randomness in
[This message has also been posted to linux.debian.user.]
This is becoming a FAQ. There is a problem with udev.
Before udev, there was a strong association between
device names and devices. With udev, that association
is much weaker.
There's new randomness in how partitions are named
during boot.
Florian Kulzer skrev:
> On Thu, Jan 03, 2008 at 06:39:11 -0500, dave N wrote:
>
> [...]
>
>> Question: In the menu.lst grub file, how would I use
>> the label assignment in the line:
>>
>> kernel /vmlinuz-2.6.18-5-686 root=/dev/sdc2 ro
>
> I think this should be OK:
>
> kernel /vmlinuz-2.6.1
On Thu, Jan 03, 2008 at 06:39:11 -0500, dave N wrote:
[...]
> Question: In the menu.lst grub file, how would I use
> the label assignment in the line:
>
> kernel /vmlinuz-2.6.18-5-686 root=/dev/sdc2 ro
I think this should be OK:
kernel /vmlinuz-2.6.18-5-686 root=LABEL=your_root_label ro
I
--- Daniel Burrows <[EMAIL PROTECTED]> wrote:
> On Wed, Jan 02, 2008 at 10:24:07AM -0800, Andrew
> Sackville-West <[EMAIL PROTECTED]> was
> heard to say:
> > On Wed, Jan 02, 2008 at 06:24:07AM -0500, dave N
> wrote:
> > If you wait long enough (at least 30 seconds,
> maybe a couple minutes,
> > I
On Wed, Jan 02, 2008 at 10:24:07AM -0800, Andrew Sackville-West <[EMAIL
PROTECTED]> was heard to say:
> On Wed, Jan 02, 2008 at 06:24:07AM -0500, dave N wrote:
> If you wait long enough (at least 30 seconds, maybe a couple minutes,
> I can't remember) you should get dropped to a busybox shell. The
Andrei Popescu <[EMAIL PROTECTED]> wrote: On Wed, Jan 02, 2008 at 06:04:18AM
-0500, dave N wrote:
> I booted with Knoppix live and there is nothing in /var/log/messages, none of
> the logs appear to have changed since I last booted 2 days ago. I have not
> run fsck or anything else on this yet
On Wed, Jan 02, 2008 at 06:24:07AM -0500, dave N wrote:
> dave N <[EMAIL PROTECTED]> wrote: Hi:
>
> I've installed Etch r1 and the only real thing I've done to the system is
> updated the system, though during the update it updated the kernel to the
> same kernel that was installed during t
On Wed, Jan 02, 2008 at 06:04:18AM -0500, dave N wrote:
> I booted with Knoppix live and there is nothing in /var/log/messages, none
> of the logs appear to have changed since I last booted 2 days ago. I have not
> run fsck or anything else on this yet.
>
> Ideas?
This is usually a
dave N <[EMAIL PROTECTED]> wrote: Hi:
I've installed Etch r1 and the only real thing I've done to the system is
updated the system, though during the update it updated the kernel to the same
kernel that was installed during the installation (used the medium to try and
get more control over
Vidar Langseid wrote:
Hi
In article <[EMAIL PROTECTED]>, Johannes Wiedersich wrote:
Cameron L. Spitzer wrote:
[snip upgrade instructions]
Thanks for posting your experience! I am sure it will be useful to
others.
You could have a debate about whether this is an installer
bug, a kern
Hi
> [This message has also been posted to linux.debian.user.]
>
> In article <[EMAIL PROTECTED]>, Johannes Wiedersich wrote:
> > Cameron L. Spitzer wrote:
> > [snip upgrade instructions]
> >
> > Thanks for posting your experience! I am sure it will be useful to
> > others.
> >
> >> You could have
On Mon, Nov 05, 2007 at 09:14:18AM -0500, Douglas A. Tutty wrote:
> On Sat, Nov 03, 2007 at 09:14:44PM -0700, Andrew Sackville-West wrote:
>
> > it turns out you can do a reasonable amount of stuff in that busybox
> > shell and if the system is close to booting, you can get it to
> > go. What I w
On Sat, Nov 03, 2007 at 09:14:44PM -0700, Andrew Sackville-West wrote:
> it turns out you can do a reasonable amount of stuff in that busybox
> shell and if the system is close to booting, you can get it to
> go. What I was missing, and desperately wanted, was some kind of text
> editor. I ended
On Sat, Nov 03, 2007 at 02:38:36AM +, Cameron L. Spitzer wrote:
> In article <[EMAIL PROTECTED]>, Andrew Sackville-West wrote:
>
> > I've had to learn my
> > way around that having just reconfigured my laptop. The critical item
> > is the contents of $ROOT. The value of $ROOT gets set by the k
In article <[EMAIL PROTECTED]>, Andrew Sackville-West wrote:
>
> On Fri, Nov 02, 2007 at 03:33:06PM -0700, [EMAIL PROTECTED] wrote:
>> In article <[EMAIL PROTECTED]>, Johannes Wiedersich wrote:
>> > Cameron L. Spitzer wrote:
[ when I upgraded Etch to Lenny, device names changed and the
Lenny kernel
On Fri, Nov 02, 2007 at 03:33:06PM -0700, [EMAIL PROTECTED] wrote:
> [This message has also been posted to linux.debian.user.]
> In article <[EMAIL PROTECTED]>, Johannes Wiedersich wrote:
> >
> > Cameron L. Spitzer wrote:
> > [snip upgrade instructions]
> >
> > Thanks for posting your experience! I
[This message has also been posted to linux.debian.user.]
In article <[EMAIL PROTECTED]>, Johannes Wiedersich wrote:
>
> Cameron L. Spitzer wrote:
> [snip upgrade instructions]
>
> Thanks for posting your experience! I am sure it will be useful to others.
>
>> You could have a debate about whether
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron L. Spitzer wrote:
[snip upgrade instructions]
Thanks for posting your experience! I am sure it will be useful to others.
> You could have a debate about whether this is an installer
> bug, a kernel package bug, a udev bug, or operator error.
On Thu, Oct 25, 2007 at 04:17:33PM -0300, Cassiano Bertol Leal wrote:
> Hi
>
> I am trying to make a smooth transition fom windows to Debian in my work PC.
:)
>
> I needed to be sure that not having win on this machine wouldn't affect
> my work, since unfortunatelly we use many windows-based ap
Cassiano Bertol Leal wrote:
> Begin: Mounting root file system... ...
> Begin: Running /scripts/local-top ...
> Done.
> Begin: Waiting for root file system... ...
> And from there, I can only Control-Alt-Delete or do a cold reset.
> The machine is a Dell Optiplex GX280 P4-HT with 2GB RAM and a 80
46 matches
Mail list logo
