Wrong kernel selected during boot during RAID testing
I used a sarge amd64 netinst image to configure a two-disk system with two RAID1s, one of which is a mount point for /boot and one of which is used as a physical volume for LVM. I had experimented with the sarge amd64 installer, the sid amd64 installer, and the Ubuntu amd64 installer trying to get this setup working. Eventually, once I thought I had the partitioning process figured out, I returned to sarge. So I go through the installation process from scratch once again, trying to clear out everything and rebuild my partitions. sarge chooses grub as a bootloader, which is fine with me. I reboot, everything comes up clean, and I go through base-config. Then I shut down. At this point, the server is using the default 2.6.8 amd64- generic kernel that comes with the distro. Now I remove one of the two drives while the box is cold and start the machine. When it boots, there's an error about not finding the map for the kernel and somehow it finds a 2.6.12 kernel and boots with that, but none of the modules are there because the box was built and installed with a 2.6.8 kernel. So when it comes up, it's running the wrong kernel and has no networking. Where did this kernel come from, and how can I remove it? I feel like it must be a vestige of my installer experimentation, but I don't know how to clean the drives any more thoroughly during the partitioning stage of the sarge installer. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID, LVM, and LILO on amd64 sarge
On Nov 7, 2005, at 3:04 AM, A J Stiles wrote:
On Saturday 05 November 2005 00:22, Thomas F. O'Connell wrote:
On Nov 4, 2005, at 5:37 PM, Thomas F. O'Connell wrote:
On Nov 4, 2005, at 4:38 PM, Gilles wrote:
During partitioning, I set up both software RAID1 and LVM. After
partitioning, I tried to install LILO in the MBR on /dev/md0,
but it
didn't work. I tried advanced mode and tried /dev/mapper/vg-
root as
an installation target, but that was invalid, as well.
I think that you have to use an actual disk or disk partition as
target.
At least, that's how I did it with grub where a disk is
specified with
something like (hd0) and a partition as (hd0,0).
To have the loader available, even if one of the disks in the array
fails, you just install it on every disks that composes /dev/md0.
I thought I had read that grub didn't play well with sarge.
Unfortunately, now I'm struggling even to get RAID1 set up the way
I'd like, even without LVM.
Maybe this is about the methodology I'm using rather than a problem
with the installer, although I would expect the installer to be a
little more intuitive. I have a two-drive machine (two 250 GB
drives), and I'd like to configure them in a RAID1 such that each
disk is bootable.
I thought that I could just configure each disk with a single
physical RAID volume partition and then create a software RAID in
which I could create as many partitions as I want, including a /
boot partition if need be.
But I'm running into issues with seeing the remainder of the disk
space be flagged as unusable as soon as I create a partition in
the RAID1.
Okay. Sorry for the noise of my reply. I read this a little more
closely:
http://www.tldp.org/HOWTO/Software-RAID-HOWTO-11.html#ss11.1
But this leaves me with my original problem.
What I'm doing now is:
1. Set up a monolithic physical volume for RAID on each disk.
2. Configure RAID1 using these volumes.
3. Configure a single LVM volume group (vg) with four logical volumes
in it: root, swap, var, and home. I don't specifically create a
volume or mount point for /boot, but I haven't gathered that that
should be necessary.
This isn't specific to 64-bit systems. Basically, a bootstrap
loader such as
LILO has only a very primitive filesystem; it expects the kernel to
be in a
contiguous group of sectors on a single disk. Only once the kernel is
loaded, decompressed and running do the other, more complex file
systems
become available.
If you are using software RAID then you must have a /boot partition
which is a
non-RAID, ext3 or ext2 partition; and a separate swap partition on
each drive
{you don't need RAID on swap; if that goes down, the kernel's going
down
anyway. Not to mention it's a serious performance issue}. Note, the
bootstrap loader *doesn't* care about / -- when you configure it by
running /sbin/lilo, the kernel is already running, and it will be
able to
find the sector where the kernel begins. So your root partition
can {and
probably should} be RAID.
Build your system with a few megs ext3 / ext2 partition near the
beginning,
then a gig or so of swap {remember you will have 2 swap files, 1
on each
drive} and then your main partitions. Once your system is
installed then
you will have a boot partition on sda1 but not on sdb1. So you now
should
copy over the contents of sda1 to sdb1 using dd. In effect you are
doing
RAID manually! But this only needs to be done whenever you compile
a new
kernel.
Well, the funny thing is that last night, as I was about to dig into
manual intervention, I got the sarge amd64 installer to set things up
according to my ideal, and it seems to have worked.
I'm going to verify that I can boot by either drive today, but I
must've crossed my fingers just right during partitioning. In all
seriousness, it's possible (read: likely) that there was a detail
about one of the partitions I had attempted to setup that was
configured improperly during my previous experimentation with the
sarge installer.
Granted, I think it'd be wonderful if the installer eventually makes
the process a little more failsafe (while preserving flexibility),
but I guess that's what software development is about... :P
At the moment, though, I'm running sarge amd64 with two RAID1s, one
of which is using /boot as a mount point and one of which is a
physical volume for LVM, and this is just what I want.
--
Thomas F. O'Connell
Database Architecture and Programming
Co-Founder
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-469-5150
615-469-5151 (fax)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID, LVM, and LILO on amd64 sarge
In comparing the unofficial sarge to the sid_d-i CD, I find that I'm able to partition as I hope/expect with sid: disk1 1 small physical volume for RAID for /boot 1 large physical volume for RAID for rest of system disk2 1 small physical volume for RAID for /boot 1 large physical volume for RAID for rest of system RAID1 Use as ext3 for /boot RAID1 physical volume for LVM LVM vg0 root var swap home After doing so, LILO installs just fine (whereas it punks out in the sarge installer). This suggests a limitation at some level in sarge (whether kernel, installer, or LILO I don't know). Is this the sort of thing that's likely to get fixed in sarge, or should I just stick with sid? If any of this is not a known bug, I'd be happy to file one. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Nov 5, 2005, at 8:49 AM, Austin (Ozz) Denyer wrote: On Fri, 4 Nov 2005 20:54:16 -0600, Thomas F. O'Connell [EMAIL PROTECTED] wrote: So I finally made it through the installation process (see nearby thread about software RAID, LVM, and LILO), and lo and behold: networking isn't working. The primary ethernet card (of three) in this machine is an Intel Ethernet Pro 100, and the e100 module seems to load fine and be recognized, but I don't seem to be able to ping the router on my local network, so I'm suspicious of the network card. During installation, DHCP was not detected, and after reboot during base-config, apt setup couldn't be completed normally because, I suspect, of networking issues. Has anyone had any difficulty getting networking going under sarge amd64? It would help greatly if you could give us some error messages to chew on. Well, here's what happens: During installation, it gets to the point where it recognizes and displays my three network interfaces. I choose the e100, which has traditionally been eth0, as the primary interface. Looking on the Alt- F3 virtual console, I see the following lines: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/mii.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/e100.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/tg3.ko Then, back on the installer console, it tells me that it's going to detect DHCP. This fails. There are no further messages or errors on the other console other than: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/block/ floppy.ko FATAL: Error inserting floppy (/lib/modules/2.6.8-11-amd64-generic/ kernel/drivers/block/floppy.ko): No such device But that's not related to DHCP detection, is it? Then I try to configure the network manually with the IP the box had before I attempted to reinstall, along with the local network address for the router and the correct netmask. I leave the nameserver blank. The installer pauses for a bit and then returns with the hostname prompt. Is there any way to determine at this point in the installation process whether the network card has been successfully recognized and is working? Or to further diagnose why DHCP was not able to be autoconfigured? Would expert mode help? -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Nov 5, 2005, at 10:46 AM, Thomas F. O'Connell wrote: On Nov 5, 2005, at 8:49 AM, Austin (Ozz) Denyer wrote: On Fri, 4 Nov 2005 20:54:16 -0600, Thomas F. O'Connell [EMAIL PROTECTED] wrote: So I finally made it through the installation process (see nearby thread about software RAID, LVM, and LILO), and lo and behold: networking isn't working. The primary ethernet card (of three) in this machine is an Intel Ethernet Pro 100, and the e100 module seems to load fine and be recognized, but I don't seem to be able to ping the router on my local network, so I'm suspicious of the network card. During installation, DHCP was not detected, and after reboot during base-config, apt setup couldn't be completed normally because, I suspect, of networking issues. Has anyone had any difficulty getting networking going under sarge amd64? It would help greatly if you could give us some error messages to chew on. Well, here's what happens: During installation, it gets to the point where it recognizes and displays my three network interfaces. I choose the e100, which has traditionally been eth0, as the primary interface. Looking on the Alt-F3 virtual console, I see the following lines: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/mii.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/e100.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/tg3.ko Then, back on the installer console, it tells me that it's going to detect DHCP. This fails. There are no further messages or errors on the other console other than: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/block/ floppy.ko FATAL: Error inserting floppy (/lib/modules/2.6.8-11-amd64-generic/ kernel/drivers/block/floppy.ko): No such device But that's not related to DHCP detection, is it? Then I try to configure the network manually with the IP the box had before I attempted to reinstall, along with the local network address for the router and the correct netmask. I leave the nameserver blank. The installer pauses for a bit and then returns with the hostname prompt. Is there any way to determine at this point in the installation process whether the network card has been successfully recognized and is working? Or to further diagnose why DHCP was not able to be autoconfigured? Would expert mode help? For what it's worth, I am now having the same problem with the sid amd64 testing netinst image. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Nov 5, 2005, at 11:12 AM, Thomas F. O'Connell wrote: On Nov 5, 2005, at 10:46 AM, Thomas F. O'Connell wrote: On Nov 5, 2005, at 8:49 AM, Austin (Ozz) Denyer wrote: On Fri, 4 Nov 2005 20:54:16 -0600, Thomas F. O'Connell [EMAIL PROTECTED] wrote: So I finally made it through the installation process (see nearby thread about software RAID, LVM, and LILO), and lo and behold: networking isn't working. The primary ethernet card (of three) in this machine is an Intel Ethernet Pro 100, and the e100 module seems to load fine and be recognized, but I don't seem to be able to ping the router on my local network, so I'm suspicious of the network card. During installation, DHCP was not detected, and after reboot during base-config, apt setup couldn't be completed normally because, I suspect, of networking issues. Has anyone had any difficulty getting networking going under sarge amd64? It would help greatly if you could give us some error messages to chew on. Well, here's what happens: During installation, it gets to the point where it recognizes and displays my three network interfaces. I choose the e100, which has traditionally been eth0, as the primary interface. Looking on the Alt-F3 virtual console, I see the following lines: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/mii.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/e100.ko insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/net/tg3.ko Then, back on the installer console, it tells me that it's going to detect DHCP. This fails. There are no further messages or errors on the other console other than: insmod /lib/modules/2.6.8-11-amd64-generic/kernel/drivers/block/ floppy.ko FATAL: Error inserting floppy (/lib/modules/2.6.8-11-amd64-generic/ kernel/drivers/block/floppy.ko): No such device But that's not related to DHCP detection, is it? Then I try to configure the network manually with the IP the box had before I attempted to reinstall, along with the local network address for the router and the correct netmask. I leave the nameserver blank. The installer pauses for a bit and then returns with the hostname prompt. Is there any way to determine at this point in the installation process whether the network card has been successfully recognized and is working? Or to further diagnose why DHCP was not able to be autoconfigured? Would expert mode help? For what it's worth, I am now having the same problem with the sid amd64 testing netinst image. Okay. I'm a little closer to tracking it down, now. For comparison with sarge and sid, I tried the Ubuntu AMD64 installer CD. The installer is, of course, very similar to Debian, but the Ubuntu installer chose a different ordering for my network cards, putting one of the Broadcom NetXtreme cards as eth0 rather than the Intel Ethernet Pro 100. I had just been assuming that the Intel was the card I had been using before reinstalling this system, but I guess it's been one of the two Broadcoms because DHCP autoconfiguration worked. If I can be of assistance in improving default selection of the primary network interface for the Debian Installer, please let me know. I don't know if this is an amd64 issue or not, so also please let me know if I should post the results of all these attempts on another list. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID, LVM, and LILO on amd64 sarge
To continue this thread a bit, I'm curious whether the current state of boot loaders for Debian under amd64 is such that it is theoretically possible to configure LVM on software RAID on a multi- disk system without needing an isolated un-RAIDed /boot partition on one of the disks. I have a two-disk system. I'd like to create two RAID1s for this system. One of the RAID1s would exist across a /boot partition with the bootable flag set on each disk. This would be fairly small (100 MB or less). Then, I would have another RAID1 on both disks using the remainder of the disk space, and each of these would be a physical volume for LVM. When I've tried this, I'm able to complete the partition step, and then LILO is the only option, but it isn't able to recognize /dev/md0 (or /dev/md/0) as a valid disk or partition. Currently, what I have to do in order to get either grub or LILO to play with this setup is to create an un-RAIDed /boot partition on one of the disks and then create an unused partition opposite that on the other disk. Then I set up the LVM on RAID on the rest of the space on each disk. The reason the former scenario would be ideal is that I'd like to be able to boot from either disk in case one fails. With the workaround I'm using now, only one disk has a bootable /boot partition. Is there any way to achieve what I want to do (preferably from the installer), namely to have both disks have a bootable partition as well as running LVM on RAID1 for the rest of the system? I'm currently using the unofficial sarge amd64 netinst image to install. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID, LVM, and LILO on amd64 sarge
On Nov 5, 2005, at 12:31 PM, Gilles wrote: I have a two-disk system. I'd like to create two RAID1s for this system. One of the RAID1s would exist across a /boot partition with the bootable flag set on each disk. [snip] Is there any way to achieve what I want to do (preferably from the installer), namely to have both disks have a bootable partition as well as running LVM on RAID1 for the rest of the system? I didn't try the recent installers. When I installed (February), it wasn't possible to do it all at once (hence the above procedure). It certainly seems like it would be advantageous to allow the installers to support this functionality directly. If I can provide any information that would help the process along, please let me know. What's the easiest way to track progress on (and contribute to) an issue like this? From my point of view, I'm not sure whether it's something at the kernel level, the installer level, or the bootloader level (in terms of version compatibility with RAID/LVM). -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 Debian Installer netinst
On Nov 4, 2005, at 2:38 PM, Kurt Roeckx wrote: On Fri, Nov 04, 2005 at 02:05:48PM -0600, Thomas F. O'Connell wrote: After starting this thread on debian-boot, I was gently pushed to this list. I recently tried to get Debian Installer going on a single Opteron custom-built machine using the daily build of the netinst CD image from here: http://www.debian.org/devel/debian-installer/ Could you please provide an url to the actual location what image you downloaed? And on what date did you download those? The current is a symlink that changes every day. Some of the problems might have been fixed already. Kurt I grabbed today's daily (2005-11-04) at around 10:00 CST: http://amd64.debian.net/debian-installer/daily/ -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 Debian Installer netinst
On Nov 4, 2005, at 2:57 PM, Kurt Roeckx wrote: On Fri, Nov 04, 2005 at 02:47:52PM -0600, Thomas F. O'Connell wrote: I grabbed today's daily (2005-11-04) at around 10:00 CST: http://amd64.debian.net/debian-installer/daily/ Which is something completly different from what you said before. You said that you got the netinst image (100 MB). On that url are dirrerent things available like that netboot (5 MB). There is alot of difference for the daily builds between those two. Sorry, careless copy/paste. I grabbed this one: http://cdimage.debian.org/pub/cdimage-testing/daily/amd64/current/ debian-testing-amd64-netinst.iso -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 Debian Installer netinst
On Nov 4, 2005, at 3:15 PM, Kurt Roeckx wrote: On Fri, Nov 04, 2005 at 03:00:59PM -0600, Thomas F. O'Connell wrote: http://cdimage.debian.org/pub/cdimage-testing/daily/amd64/current/ debian-testing-amd64-netinst.iso So it seems that those image are broken, and waiting for some other things to get fixed first. I hope it should be fixed in a few days. Have you tried some other images already? Like the netboot, or the ones that came with sarge? I'm having pretty good luck with the sarge netinst image for amd64, but I'm trying to set up LVM on software RAID1, and it seems to causing problems for LILO at the point of installing the boot loader. I can't tell whether this is a lack of knowledge on my part (and the installer's, it would seem) in terms of how I need to specify LILO installation, but even when I try Advanced mode to set an installation target, I don't seem to be having any luck. I've seen a couple of posts that imply people have successfully configured this before, so I don't know whether this is an amd64/LILO/ LVM issue, or what. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Software RAID, LVM, and LILO on amd64 sarge
After discovering that the amd64 Debian Installer netinst images have been broken recently, I retreated to sarge. At first glance, I was having pretty good luck, but I ran into a snag during boot loader installation. During partitioning, I set up both software RAID1 and LVM. After partitioning, I tried to install LILO in the MBR on /dev/md0, but it didn't work. I tried advanced mode and tried /dev/mapper/vg-root as an installation target, but that was invalid, as well. I've seen posts suggesting that this ought to work without a non-LVM / boot partition, so I'm wondering whether this is an issue that's peculiar to sarge on amd64? -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Software RAID, LVM, and LILO on amd64 sarge
On Nov 4, 2005, at 5:37 PM, Thomas F. O'Connell wrote: On Nov 4, 2005, at 4:38 PM, Gilles wrote: During partitioning, I set up both software RAID1 and LVM. After partitioning, I tried to install LILO in the MBR on /dev/md0, but it didn't work. I tried advanced mode and tried /dev/mapper/vg-root as an installation target, but that was invalid, as well. I think that you have to use an actual disk or disk partition as target. At least, that's how I did it with grub where a disk is specified with something like (hd0) and a partition as (hd0,0). To have the loader available, even if one of the disks in the array fails, you just install it on every disks that composes /dev/md0. I thought I had read that grub didn't play well with sarge. Unfortunately, now I'm struggling even to get RAID1 set up the way I'd like, even without LVM. Maybe this is about the methodology I'm using rather than a problem with the installer, although I would expect the installer to be a little more intuitive. I have a two-drive machine (two 250 GB drives), and I'd like to configure them in a RAID1 such that each disk is bootable. I thought that I could just configure each disk with a single physical RAID volume partition and then create a software RAID in which I could create as many partitions as I want, including a / boot partition if need be. But I'm running into issues with seeing the remainder of the disk space be flagged as unusable as soon as I create a partition in the RAID1. Okay. Sorry for the noise of my reply. I read this a little more closely: http://www.tldp.org/HOWTO/Software-RAID-HOWTO-11.html#ss11.1 But this leaves me with my original problem. What I'm doing now is: 1. Set up a monolithic physical volume for RAID on each disk. 2. Configure RAID1 using these volumes. 3. Configure a single LVM volume group (vg) with four logical volumes in it: root, swap, var, and home. I don't specifically create a volume or mount point for /boot, but I haven't gathered that that should be necessary. The installer partitions all this just fine but can't seem to figure out what to do to install LILO (which is the only option available for boot loader once I've partitioned with LVM, reinforcing my thinking that grub doesn't play nicely with LVM). Once I reach this step, with this configuration is there any way to specify an actual disk or disk partition as a target for LILO? By default, it tries to select the Master Boot Record of /dev/md0, which doesn't work. The default attempt for Advanced mode is /dev/md/0, which also doesn't work. Nor does /dev/vg/root, nor /dev/mapper/vg-root. Again, I'm not sure whether this is a LILO/amd64 issue. If this is better posted on another list, please let me know. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Could not find kernel image: linux
On Nov 4, 2005, at 12:08 PM, Tony Power wrote: Hi! Two days ago I've finished downloading amd64 (testing) DVD images throwght jigdo. MD5 sums are ok. The DVDs are well burned. The problem is when I try to boot the DVD (to install it), I get the message: Could not find kernel image: linux boot: _ I have an Acer Aspire 1524 wlmi. Can anybody help? Thank you. Tony, I had the same problem just today regarding a netinst image and was told that the daily builds were having issues. I suspect you're seeing a slightly broken disk image. -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Networking not working
So I finally made it through the installation process (see nearby thread about software RAID, LVM, and LILO), and lo and behold: networking isn't working. The primary ethernet card (of three) in this machine is an Intel Ethernet Pro 100, and the e100 module seems to load fine and be recognized, but I don't seem to be able to ping the router on my local network, so I'm suspicious of the network card. During installation, DHCP was not detected, and after reboot during base-config, apt setup couldn't be completed normally because, I suspect, of networking issues. Has anyone had any difficulty getting networking going under sarge amd64? -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Networking not working
On Nov 4, 2005, at 9:04 PM, lordSauron wrote: Yes, it seemed to me that most of the NICs aren't supported yet. I had to forsake my mboard integrated Realtek Gigabit Ethernet for a old 3Com 100/10 PCI card until kernel -12 debuted, in which support was added. I don't know who to contact to request the addding of your particular card, but when you do, ensure to send him/her/it (you never know...) every single last detail about the card, all the way down to the S/N, so that there's no confusion about which driver they're working with. Hope you find a solution! Is there any way to track device driver support? -- Thomas F. O'Connell Database Architecture and Programming Co-Founder Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-469-5150 615-469-5151 (fax) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
