After some progress, a new topic.
Reference,
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mjmwired.net/kernel/Documentation/kernel-parameters.txt"
linktext was:"http://www.mjmwired.net/kernel/Document ... meters.txt"
====================================
This machine has no PCI bus. With this in grub/menu.lst, dma is
no longer a problem.
kernel /boot/vmlinuz-2.6.32-1-mepis root=/dev/hda1 nomce quiet nosplash acpi=off libata.dma=0 pci=off,nobios
But it comes to this.
ALERT! /dev/hda1 does not exist. Dropping to a shell!
Again the screen photo is at
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://easthope.ca/antiXTatung.jpg"
linktext was:"http://easthope.ca/antiXTatung.jpg"
====================================
.
hda1 is not found? Why?
The machine has a Geode cpu. Several of the options in the
reference relate to a timer or timers in the Geode. Any advice
about timers? Other ideas?
Thanks again, ... Peter E.
topic title: "ALERT! /dev/hda1 does not exist"
7 posts
• Page 1 of 1
-
Posts: 24
- Joined: 27 Nov 2015
-
Posts: 4,164
- Joined: 20 Feb 2009
#2
Post output of
cat /etc/fstab
to supply info on what is going on with what on what.
Code: Select all
sudo blkid
Code: Select all
sudo fdisk -l
Code: Select all
sudo parted -l
Code: Select all
inxi -Fxxx
-
Posts: 2,238
- Joined: 16 Dec 2007
#3
if I understand what you are doing, you are mixing a 2.6 kernel with an antix-15 core install. I think you'll find all kinds of things that are not going to work.
somewhere along the way, naming conventions for devices changed, and hda went away and all devices became sda. I'm not sure what controls the naming of the devices, but you might try sda1 instead of hda1 in your boot line. or root=UUID=uuid of the drive. most modern systems boot uuid designations instead of sdX designations because the udev spec allows for the names of devices to change every boot.
somewhere along the way, naming conventions for devices changed, and hda went away and all devices became sda. I'm not sure what controls the naming of the devices, but you might try sda1 instead of hda1 in your boot line. or root=UUID=uuid of the drive. most modern systems boot uuid designations instead of sdX designations because the udev spec allows for the names of devices to change every boot.
-
Posts: 24
- Joined: 27 Nov 2015
#4
> Post output of
> sudo blkid
> cat / etc/fstab
> sudo fdisk -l
> sudo parted -l
> inxi -Fxxx
> to supply info on what is going on
> with what on what.
For background, please refer to my preceding topic"Error inserting fan" ...
At this stage, the tablet has no keyboard and no mouse. The only way I imagine to obtain the information requested is to modify and recompile grub.
Sun Dec 13, 2015 6:28 am
> if I understand what you are doing, you are mixing a 2.6 kernel with an antix-15 core install.
I merely retrieved antiX-15-V_386-core-libre.iso from sourceforge
and installed to a CF card. Didn't change the kernel.
> ... try sda1 instead of hda1 in your boot line. or root=UUID=uuid of the drive.
Comes to equivalent results.
ALERT! /dev/sda1 does not exist.
and
ALERT! /dev/by-uuid/79...7 does not exist. Dropping to shell!
...
(initramfs)
(initramfs)
(initramfs)
> most modern systems boot uuid designations instead of sdX designations because
> the udev spec allows for the names of devices to change every boot.
Yes, I've always wondered why Linux missed the simple notation for
ATA drives, IDE<d>#<p>. Eg. IDE1#1 for 1st part of 2nd drive.
Incidentally, Native Oberon boots on the machine with no difficulty.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://en.wikipedia.org/wiki/Oberon_%28operating_system%29#Gallery"
linktext was:"https://en.wikipedia.org/wiki/Oberon_%2 ... 29#Gallery"
====================================
An elementary but obscure snag here with antiX.
Thanks, ... Peter E.
> sudo blkid
> cat / etc/fstab
> sudo fdisk -l
> sudo parted -l
> inxi -Fxxx
> to supply info on what is going on
> with what on what.
For background, please refer to my preceding topic"Error inserting fan" ...
At this stage, the tablet has no keyboard and no mouse. The only way I imagine to obtain the information requested is to modify and recompile grub.
Sun Dec 13, 2015 6:28 am
> if I understand what you are doing, you are mixing a 2.6 kernel with an antix-15 core install.
I merely retrieved antiX-15-V_386-core-libre.iso from sourceforge
and installed to a CF card. Didn't change the kernel.
> ... try sda1 instead of hda1 in your boot line. or root=UUID=uuid of the drive.
Comes to equivalent results.
ALERT! /dev/sda1 does not exist.
and
ALERT! /dev/by-uuid/79...7 does not exist. Dropping to shell!
...
(initramfs)
(initramfs)
(initramfs)
> most modern systems boot uuid designations instead of sdX designations because
> the udev spec allows for the names of devices to change every boot.
Yes, I've always wondered why Linux missed the simple notation for
ATA drives, IDE<d>#<p>. Eg. IDE1#1 for 1st part of 2nd drive.
Incidentally, Native Oberon boots on the machine with no difficulty.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://en.wikipedia.org/wiki/Oberon_%28operating_system%29#Gallery"
linktext was:"https://en.wikipedia.org/wiki/Oberon_%2 ... 29#Gallery"
====================================
An elementary but obscure snag here with antiX.
Thanks, ... Peter E.
-
Posts: 4,164
- Joined: 20 Feb 2009
#5
My thread on when I installed it on one of my atom touchscreen units running AntiX below.
viewtopic.php?f=4&t=5974&hilit=onboard
Your thread is way out of whack though.
I have no /grub/menu.list. I did long ago when I ran AntiX in the early years and we used grub legacy and the kernel used hd instead of sd for partition naming.
So something is not savvy here whether I refer to your other thread or not. You are not running AntiX 15 (but something way way older) from what I see you posting.
Even if you do say in the other thread
Okey Dokey then. Not really helpful for what I asked for. I did look though.
> Post output of
> sudo blkid
> cat / etc/fstab
> sudo fdisk -l
> sudo parted -l
> inxi -Fxxx
> to supply info on what is going on
> with what on what.
For background, please refer to my preceding topic"Error inserting fan" ...
Makes me wonder how the install buttons were hit. Using the screen? If so. On my touchscreen. For a onscreen keyboard. I use onboard.At this stage, the tablet has no keyboard and no mouse.
My thread on when I installed it on one of my atom touchscreen units running AntiX below.
viewtopic.php?f=4&t=5974&hilit=onboard
Your thread is way out of whack though.
Because this looks wrong as all get out for AntiX 15 which uses grub 2 and not grub legacyhda1 is not found? Why?
My AntiX 15 is like soWith this in grub/menu.lst, dma is
no longer a problem.
kernel /boot/vmlinuz-2.6.32-1-mepis root=/dev/hda1 nomce quiet nosplash acpi=off libata.dma=0 pci=off,nobios
Code: Select all
harry@biker:~
$ inxi -S
System: Host: biker Kernel: 4.2.1-antix.2-686-pae i686 (32 bit)
Desktop: IceWM 1.3.8
Distro: antiX-15-V_386-full Killah P 30 June 2015
harry@biker:~
$ cd /boot
harry@biker:/boot
$ ls
config-3.16.0-4-686-pae
config-3.17-7.dmz.2-liquorix-686-pae
config-4.2.1-antix.2-686-pae
extlinux
grub
initrd.img-3.16.0-4-686-pae
initrd.img-3.17-7.dmz.2-liquorix-686-pae
initrd.img-4.2.1-antix.2-686-pae
memtest86+.bin
memtest86+_multiboot.bin
System.map-3.16.0-4-686-pae
System.map-3.17-7.dmz.2-liquorix-686-pae
System.map-4.2.1-antix.2-686-pae
vmlinuz-3.16.0-4-686-pae
vmlinuz-3.17-7.dmz.2-liquorix-686-pae
vmlinuz-4.2.1-antix.2-686-pae
harry@biker:/boot
$ cd grub
harry@biker:/boot/grub
$ ls
fonts grub.cfg grubenv i386-pc locale unicode.pf2 Xerces.wav ZZ.wav
So something is not savvy here whether I refer to your other thread or not. You are not running AntiX 15 (but something way way older) from what I see you posting.
Even if you do say in the other thread
Maybe Anti knows what you are doing. Because I do not. Sorry. __{{emoticon}}__antiX-15-V_386-core-libre.iso was applied to install to a CF card.
-
Posts: 24
- Joined: 27 Nov 2015
#6
> Maybe Anti knows what you are doing. Because I do not. Sorry.
The"installation" was performed with the CF in a desktop machine running QEMU with the virtual machine booted from the iso. If antiX 15 is based on Debian testing, the kernel is 4.2. Kernel 2.6 here certainly is wrong.
When there is time I'll start from the beginning again. January maybe.
Thanks for the reply, ... Peter E.
The"installation" was performed with the CF in a desktop machine running QEMU with the virtual machine booted from the iso. If antiX 15 is based on Debian testing, the kernel is 4.2. Kernel 2.6 here certainly is wrong.
When there is time I'll start from the beginning again. January maybe.
Thanks for the reply, ... Peter E.
-
Posts: 24
- Joined: 27 Nov 2015
#7
> So something is not savvy here whether I refer to
> your other thread or not. You are not running AntiX
> 15 (but something way way older) ...
You are correct. I should have said that the
system was installed with antiX-M8.5-base-486.iso.
I tried to run antiX-15-V_386-full.iso and
antiX-15-V_386-core-libre.iso under QEMU a few days
back. Those installations ran for hours. The first
failed to conclude properly. I abandoned the second
after an hour or two.
After that I installed with antiX-M8.5-base-486.iso.
The previous reports should have referred to that.
Preoccupation with other work has distracted me
severely from this project.
The problem remains: install an antiX which works.
Continue trying to make M8.5-base boot? Try again to
install 15? Given the difficulty with QEMU, try the
boot fromiso method perhaps? Any suggestions are
welcome.
Thanks, ... Peter E.
> your other thread or not. You are not running AntiX
> 15 (but something way way older) ...
You are correct. I should have said that the
system was installed with antiX-M8.5-base-486.iso.
I tried to run antiX-15-V_386-full.iso and
antiX-15-V_386-core-libre.iso under QEMU a few days
back. Those installations ran for hours. The first
failed to conclude properly. I abandoned the second
after an hour or two.
After that I installed with antiX-M8.5-base-486.iso.
The previous reports should have referred to that.
Preoccupation with other work has distracted me
severely from this project.
The problem remains: install an antiX which works.
Continue trying to make M8.5-base boot? Try again to
install 15? Given the difficulty with QEMU, try the
boot fromiso method perhaps? Any suggestions are
welcome.
Thanks, ... Peter E.