e first time I booted it; but
I don't recall which kernel that was. My cpu is an AMD Athlon(tm) 64
Processor 3800+, with /proc/cpuinfo listing the cpu MHz at 2411.746. the
board is identified by dmesg as an nvidia board, with an nforce3 chipset also
listed. My kernel is 2.6.12-1.
--
David L
iso available
with a 2.6.12 kernel that works fine, though. I guess, though, that if you
are able to mount your new disk to do the transfer, your kernel will be good.
--
David L. Johnson
__o | "A foolish consistency is the hobgoblin of little minds, adored
_`\(,_ | by little states
ire port, and dmesg is indescipherable to you, you can change the
settings in /etc/network/interfaces to eth1 and see what happens... if it
doesn't help, by all means change it back.
--
David L. Johnson
__o | "What am I on? I'm on my bike, six hours a
initrd.img-2.6.whatever-yours-is
For you, I'd guess it'd be better to add ide_disk instead. This forces
the loading of that module before the sata module, so that the ide devices
should be detected.
Sorry for using English, but you can understand that a lot better than my
Spanish, be
g from the original BIOS. My machine is a little
different from yours, but not that much.
> If anybody has a solution I'd greatly appreciate it. I really thought
> this was good hardware when I bought it (specifically for the AMD64
> port), so I'd hate to think I'
ould not find the drive at all. Unless the installation used a
newer kernel than was installed, this shouldn't have been the problem.
>
> > I'd like to know and be sure that I'm using 64-bit mode, and not 32-bit
> > mode. How can I check this to make sure I'm
info on how to do
this...)
mkinitrd -o /boot/initrd.img-2.6.12-1-amd64-generic
--
David L. Johnson
__o | And though I have the gift of prophecy, and understand all
_`\(,_ | mysteries, and all knowledge; and though I have all faith, so
(_)/ (_) | that I could remove mountains, and hav
he caption "Window
> > >Manager" but it stops there, no additional loads happen.
It may be that your ~/.xsession (or the defaut one) has both kde and gnome,
somehow. It shouldn't, of course. Your ~/.xsession should end with
exec gnome-session
(no & after that). Th
think,
to be recognized as an ide device. How do I do that without /dev/hdc? How
would I go about getting that device created?
--
David L. Johnson
__o | You will say Christ saith this and the apostles say this; but
_`\(,_ | what canst thou say? -- George Fox.
(_)/ (_) |
9 matches
Mail list logo
