- Linux Mint Forums
- could not find kernel image: linux
- Re: could not find kernel image: linux
- Re: could not find kernel image: linux
- Re: could not find kernel image: linux
- Thread: Could not find kernel image: linux
- Could not find kernel image: linux
- Re: Could not find kernel image: linux
- Re: Could not find kernel image: linux
- Re: Could not find kernel image: linux
- Re: Could not find kernel image: linux
- Re: Could not find kernel image: linux
- Re: Could not find kernel image: linux
- Saved searches
- Use saved searches to filter your results more quickly
- could not find kernel image linux vmlinuz #489
- could not find kernel image linux vmlinuz #489
- Comments
- Footer
- Network booting couldn’t find kernel image
- 2 Answers 2
Linux Mint Forums
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
could not find kernel image: linux
Post by _sluimers_ » Tue Feb 10, 2009 7:09 am
I’m trying to install te latest 32-bit linux mint Felicia.
I either get a «boot error» or «could not find kernel image: linux» error when I try to
boot from either of my external harddisks.
as I don’t have a disk drive and my usb-sticks are not even recognized, except for the 500Mb one.
I use a VB8001 mobo, which is being very linux unfriendly, especially the 64-bit version of Ubuntu I’m running now.
The only way I’ve managed to install ubuntu was using a mini iso and then renamed vmlinuz into linux and put linux in /, but in this case it causes a kernel panic or «boot error».
I md5sumed the ISO too. It seems okay.
So what can I do? I’m clueless.
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: could not find kernel image: linux
Post by rivenought » Tue Feb 10, 2009 7:23 am
Looking at http://www.via.com.tw/en/products/mainb . ard_id=711 , I see VIA Chrome 9 HC graphics. Without knowing your exact hardware, and looking at this particular board, I have seen issues with that graphics chip in previous posts.
Have you tried using «compatibility mode» yet? During boot, press any key and choose «compatibility mode» from the pop-up menu. I have similar graphics, and have to use that with the 32-bit version of Mint 6. Oddly, the 64-bit version works fine.
This may not be your issue, but that is the first thing that comes to mind. The specs on that site say Linux as a supported operating system. Perhaps your problem is a simple click into «compatibility mode.» Might be worth testing out. If you could post your exact hardware, there might be something else amiss someone may notice.
Also, please consider registering with this forum so you can receive private messages, message notifications, and other features.
Re: could not find kernel image: linux
Post by jojo1028 » Tue Feb 10, 2009 8:09 am
Are you trying to boot the cd or did you manage to install mint and then it does not find your kernel when you re trying to reboot ?
Re: could not find kernel image: linux
Post by _sluimers_ » Tue Feb 10, 2009 11:20 am
Are you trying to boot the cd or did you manage to install mint and then it does not find your kernel when you re trying to reboot ?
Have you tried using «compatibility mode» yet? During boot, press any key and choose «compatibility mode» from the pop-up menu. I have similar graphics, and have to use that with the 32-bit version of Mint 6. Oddly, the 64-bit version works fine.
This may not be your issue, but that is the first thing that comes to mind. The specs on that site say Linux as a supported operating system. Perhaps your problem is a simple click into «compatibility mode.» Might be worth testing out. If you could post your exact hardware, there might be something else amiss someone may notice.
A 64-bit OS doesn’t seem compatible with the current via drivers at the moment given by linux.via.com.tw.
I get elfclass32 errors for a half the programs that use sound/video.
Thread: Could not find kernel image: linux
Gee! These Aren’t Roasted!
Could not find kernel image: linux
Ok, I have messed up my install of Ubuntu NBR on my eee pc.
Yesterday I tried installing backtrack on a small partition, and then ran sudo grub-update2 and messed around with things like that to try adding it to the grub boot list.
Now when I boot this show up immediatly, not the grub menu:
Could not find kernel image: linux
And the thing is, I dont wanna go for a fresh install since I have some things in my home folder that’s encrypted (unlocks when I login, but uses some long random phrase that ubuntu generated).
I can access my files from a live USB, but of course not the home folder since I’ve dont got that passphrase.
How can I recover grub2 so it works again?
Will be really grateful if anyone can help me with this..
Gee! These Aren’t Roasted!
Re: Could not find kernel image: linux
Skinny Soy Caramel Ubuntu
Re: Could not find kernel image: linux
So you basically can’t get into grub? Have you tried reinstalling grub from the liveCD? I’ll post a link in a sec.
Skinny Soy Caramel Ubuntu
Re: Could not find kernel image: linux
Gee! These Aren’t Roasted!
Re: Could not find kernel image: linux
Gee! These Aren’t Roasted!
Re: Could not find kernel image: linux
Okay, found the problem now, but now there is a new one.
Device Boot Start End Blocks Id System /dev/sda1 * 1 18 144553+ 83 Linux /dev/sda2 19 18503 148480762+ 5 Extended /dev/sda5 19 18254 146480638+ 83 Linux /dev/sda6 18255 18503 2000061 82 Linux swap / Solaris
sda1 is the boot partition. I had one named sda3 with backtrack on it, and that was flagged as boot, so I removed it and then added the boot flag to sda1. Now the computer says there is no operating system found. And my boot files are still in sda1, I can see them when I mount it.
What is the next step? Will I ever be able to unlock the encrypted partition if I reinstall grub2? I mean there must be like some kind of configuration on how to unlock it?
Skinny Soy Caramel Ubuntu
Re: Could not find kernel image: linux
I’m not sure, but I think the encryption is completely separated from the grub2 thing. So it shouldn’t be a problem if you reinstall grub2. Could someone more knowledgeable than I am please confirm/refute this?
Gee! These Aren’t Roasted!
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
could not find kernel image linux vmlinuz #489
could not find kernel image linux vmlinuz #489
Comments
I use the template and it produces this error.
So this seems to refer to the following lines in definition.rb
/install/vmlinuz noapic preseed/url=http://%IP%:%PORT%/preseed.cfg
I was able to create the with 10.04 but not 12.04.1.
Something wrong with my machine or what?
The text was updated successfully, but these errors were encountered:
The boot time was 120 second. I’ve tried 600 last night. I normally do this via ssh so i always supply -n . I am finally at work again today and so I got the chance to look at the gui.
You are right about the missing / .
I am on the machine so I can see the gui and it doesn’t take any longer than 10 seconds. I set it to 12 and it waits for it to do auto typing. I have to set //install with double // .
Also, for ubuntu12.04 and above, they use PAE kernel. We should also include :pae => ‘on’ (comment it out though) just in case. This probably enables the vbox pae emulator (which has performance hit).
It should be possible to build 11.10 server, then upgrade to 12.04.
I am thinking I should make a pull request later to include, at least that one file change?
I can test 12.04-package as well if you want me to confirm.
It’s strange as you said. Maybe for older machine it takes a little longer for the scene to switch, which has a delay so typing isn’t accurate? If so, maybe typing should be longer? I haven’t dived into the codebase yet but maybe adds delay to typing (at least the initial).
I just updated the veewee repo on my system, and did bundle update because of this new commit acec0d5, which might solve my issue.
I am not familiar with ruby so I assume doing update will update the underlying package.
But the same issue persist, unless I use double // .
Haha 🙂 this was a year ago. Probably 8-9 months I tried again and I don’t think I had any issue (really can’t recall now).
Thanks.
ok then — closing, please let me know if you hit it again
Footer
You can’t perform that action at this time.
Network booting couldn’t find kernel image
I have a problem with PXE booting. I followed these instructions on the Ubuntu help wiki. But I get an error on client machine:
Could not find kernel image: vmlinuz-3.13.0-24-generic
as per @BoeroBoy answer’s, make sure you gave it proper permissions. PXE won’t identify permissions problem, instead it yields couldn’t find file msg
2 Answers 2
The kernel image (and initrd) must be located relative to the root folder. If you follow that how-to, then you have configured the following parameters:
- DHCP server is configured to use /tftpboot/
- The boot image is /pxelinux.0 (relative to the TFTP root directory, so the actual path is /tftpboot/pxelinux.0 )
- PXELinux (part of syslinux) looks for its configuration in the /pxelinux.cfg/ directory. If it does not find a file matching the client MAC address or GUID, then it will fallback to a file named default ( /tftpboot/pxelinux.cfg/default ) in your case.
- That file should contain something like:
LABEL linux KERNEL vmlinuz INITRD initrd APPEND root=.
I would also suggest not to use /tftpboot/ as root directory for TFTP files, but /srv/tftpboot/ . That is a more suitable location for site-specific data.
For debugging, be sure to have a look at your syslog. I have used the dnsmasq DHCP server which sends its logs to syslog ( /var/log/syslog ). ISC’s DHCP sever should do something similar.