1. Debian Usb Install No Kernel Modules Were Found In Florida
2. Debian Usb Install No Kernel Modules Were Found In Texas

I'm trying to install Debian Testing (the KDE image) on one of my partitions. (amd64, iso-cd).However during the installation I get this error message: “No installable kernel was found inthe defined APT sources”. I aborted the installation in order to test this out in Virtualbox.This time I downloaded the regular Debian Testing image and installed it in Virtualbox. I did getthe same error message, but I was able to go ahead with the installation, and everythingseemed to work the way it was supposed to afterwards. (And I've previously successfullyinstalled Debian stable lxde in VB without getting this error message.)So I tried to just ignore the error message. (Using the KDE image in a regular installation on my machine.)I was able to finish the installation, and I installed the bootloader to /sda2. I then did a “update-grub” inmy main Ubuntu installation (which I always do after installing a new OS on another partition).

Debian wasrecognised as being present on sda2, but when I rebooted, there was no entry for Debian in the menu.I even tried a grub purge and reinstallation from Ubuntu. Debian is still found, but it's not present in themenu when I reboot. Wot?Any idea about what's going on here? I'm not sure if this is one or two separate problems.Cheers,Dry Lips Posts: 12 Joined: 2011-11-17 00:03. Fluxer wrote:Is the Debian root partition mounted when updating grub?Do you have os-prober installed on the Ubuntu OS?Hi! Thanks for replying.

Debian Usb Install No Kernel Modules Were Found In Florida

The answer is 'no' to both of your questions.Don't you know that those are testing images? From what I know - yes, they are broken. There are some topics on this forum where people say that installing Grub fails.I would suggest you to have another Live CD near you the next time you try to install with the testing ISO images so you can boot and repair the bootloader if needed.Oh, and you've done nothing yet to fix your problem (Debian not listed in the grub menu)?If you are able to boot Ubuntu:1. Reboot and boot into it2. Install os-prober3.

Mount the root Debian partition in Ubuntu4. Update-grubIf you are unable to boot any OS (broken bootloader):1. Reboot and boot into Live CD2. Install Grub to the master boot recored (recommended) or any other partition (must have boot flag)If you still are unable to see the Debian entry in the Grub menu then try to do the steps in the first case. Fluxer wrote:Don't you know that those are testing images? From what I know - yes, they are broken.

There are some topics on this forum where people say that installing Grub fails.I guess I knew that the testing images are in a somewhat fluid state, but I didn't expectthese kind of problems. When installing from the DVD I explicitly get the message thatinstallation of grub failed, as quoted above.My last installation was of the regular cd-iso.

I flagged the root partition where I installedDebian as bootable, but I didn't install the grub to the MBR, but to where I installedDebian (/dev/sda2.) (Do you have to use quotation marks when doing that? I left thequotation marks out). If you are able to boot Ubuntu:1.

Debian Usb Install No Kernel Modules Were Found In Texas

Reboot and boot into it2. Install os-prober3. Mount the root Debian partition in Ubuntu4. Update-grubActually I think os-prober was installed by default, I just hadn't heard about it before.I then just ran 'sudo os-prober' which gave this result:Code: /dev/sda2:Debian GNU/Linux (wheezy/sid):Debian:linux/dev/sda6:Linux Mint 12 Lisa (12):LinuxMint:linuxI next mounted the root Debian partition by clicking on it from the 'places' menu.Finally I ran sudo update-grub.Sorry, but it still isn't listed in the grub menu. Actually I think os-prober was installed by defaultIf my memory servers me well - it's not if you've installed the bare minimal. If you've installed from the full-blow CDs then it should be installed by default.Your problem may be that you already have Grub installed in the MBR and the one you are installing to /dev/sda2 is becoming 'useless' (correct me if I'm wrong).

I used to had issues with that in the past so I've done what is recommended - installed it to the MBR and problem solved! Unless there is a serious reason for not doing so then try it.

Fluxer wrote:Your problem may be that you already have Grub installed in the MBR and the one you are installing to /dev/sda2 is becoming 'useless' (correct me if I'm wrong). I used to had issues with that in the past so I've done what is recommended - installed it to the MBR and problem solved! Unless there is a serious reason for not doing so then try it.I usually triple boot, Ubuntu 11.04 is my main OS at the moment. Free lasting power of attorney forms. When I installother distros that I want to check out I always leave the MBR untouched and just do'update-grub' from Ubuntu afterwards. It always works and something like this hasnever happened to me before.I'm a bit reluctant to install to the MBR when there are something wrong about the images,the DVD-iso wouldn't install the Grub at all, perhaps there are something wrong with the installerof the Grub in the other images as well?What about installing Stable and upgrading to Testing afterwards? Is that a complicated affairor is it pretty much straight forward? Posts: 12 Joined: 2011-11-17 00:03.

Fluxer wrote:Don't you know that those are testing images? From what I know - yes, they are broken. There are some topics on this forum where people say that installing Grub fails.Maybe it's just me, but the 'But it's testing' excuse has become old, threadbare, and even downright tiresome.GRUB installation issue(s) in Wheezy are now several months old. They leech attention away from legitimate problems in these forums, and leave potential new users with a really bad first impression of the distro.I don't actually know for sure, but my very strong hunch is that the ongoing lack of a solution is due to lack of developer motivation, not inherent complexity of the problem itself.

Dasein wrote:I don't actually know for sure, but my very strong hunch is that the ongoing lack of a solution is due to lack of developer motivation, not inherent complexity of the problem itself.If I was able to help then I would do so for sure but duo to my limited knowledge about Bash (in which the Debian installer is written, or other?) I can't help much. I'm not a newbie nor guru. You can get more information by looking into a project of my. My knowledge about programming in general is very limited and I really trying to make my way to the top of it, I'm planning to learn C but who knows, only time will tell./off-topic.

I'm trying to install Debian Squeeze as the main OS on my computer, but it won't detect any of my network hardware. It gives me a message about how no ethernet card was detected, and I can select it from the list, but I don't see my driver there, so I select 'none of the above,' thinking that it will just let me use the wifi chip to install (with the netinst cd), and I can just download the ethernet driver once Debian's installed.Nope. Debian won't detect my wifi card either, so I have no networking capabilities at all if I go on with the installation. What do I have to do to get it to recognize my hardware?

The cd's (both CD install and netinst) both pass the integrity check, and I go through every step correctly (I've installed before on VMs with expert install), but my only other option is to find Linux drivers for the cards and hope they work during the installation. Is there some solution to this problem?I'm installing Squeeze on a Toshiba Satellite L855-S5280P, with a Qualcomm Atheros AR8162 PCI-E Fast Ethernet Controller, and a Realtek RTL8188CE Wireless LAN 802.11n PCI-E NIC.Edit: Found a solution. Realtek provides Linux drivers for their cards, and The Linux Foundation provides drivers for Atheros cards. I'll edit back if it doesn't work, but for now I'll leave this up for anyone with the same problem. Posts: 32 Joined: 2013-02-02 06:28.

I can find no useful info on that ethernet NIC, it's not supported by ath9k, so you will probably be downloading and compiling the proprietary driver for it. The wireless NIC is not supported by the squeeze kernel, so you'd need a newer kernel - Wheezy does seem like the best option as you should be able to get the wireless up and running first (but you'll need to supply the non-free firmware during install (firmware-realtek) to get it working at install time).Posts: 2396 Joined: 2008-09-25 08:49. Well, for some reason I can't compile build-essential. Even when logged in as root, I get a permission denied message.so I tried wheezy, but it still won't recognize the NIC or Ethernet adapter. I'll try the firmware tarball method.edit: Now I get a message that says 'No kernel modules were found.

This is probably due to a mismatch between the kernel used by this version of the installer and the kernel version available in the archive.' It goes on to explain that I can supposedly install another version of debian (squeeze, I guess) through a mirror (that I can't access), or that I can try installing the system without kernel modules, which probably won't work. I'm trying the network install CD for wheezy with non-free firmware included now. Posts: 32 Joined: 2013-02-02 06:28.

Cynwulf wrote:1) You have a wireless adapter - do you also have a wireless access point which you can connect to?2) Did you read the link I posted?3) If so, have you downloaded one of the cd images including firmware or put the firmware onto usb flash ready for use during install as the Debian Wiki article suggests?1. I tried both. It still didn't detect my network hardware with the tarballs (it gave me the message I posted) or with the iso that includes non-free drivers. Posts: 32 Joined: 2013-02-02 06:28.