boot problem ramdisk


Forum: Other Help Topics
Topic: boot problem ramdisk
started by: drio

Posted by drio on Oct. 26 2006,09:29
Hello

I am not that an experienced linux user, yet I had installed debian in several machines. This is my first experience with DSL but I get the following problem

I have a Pentium 133 with 16M ram and no bootable cdrom.

I boot from floppy and I have tried normal boot (just enter), lowram, and the super low ram as described in the wiki.

My main problem is the after
Scanning for harddisk partitions and creating /etc/fstab/ ... done
using swap partition /dev/hdc2

I get
mount can't find /ramdisk in /etc/fstab/ or /etc/mtab/

afterwards many others problems occur leading to a simple shell with no X.

Any help would be much appreciated :-)




Here's the full output:

======
lowram
======

starting init process
running linux kernel
Processor 0 is Pentium 75-200 132Mhz
Autoconfiguring devices ... done
Scanning for harddisk partitions and creating /etc/fstab/ ... done

using swap partition /dev/hdc2
mount can't find /ramdisk in /etc/fstab/ or /etc/mtab/
Automounter started for floppy cdrom
mkdir Cannot create directory /ramdisk/tmp: No such file or directory
chmod: /ramdisk/tmp: No such file or directory
chgrp: /ramdisk/tmp: No such file or directory

the same errors for these two
mkdir /tmp/mydsl.menu
mkdir /tmp/mydsl.icons

Checking for mydsl apps... ls: /tmp/mydsl.icons : No such file or directory

Done

Init entering runlevel 5:
su(oam_unix)[412]: session opened dor user dsl by (uid=0)
/usr/sbin/xsetup.sh: line 82 ambiguous redirect
Using Xvesa default 1024x768x32 -mouse "/dev/ttyS0" mouse

xauth: creating new authority file /home/dsl/.Xauthority
xauth: creating new authority file /home/dsl/.Xauthority

giving up
xinit: No such file or directory (erno 2): unable to connect to X server
xinit: No such such process (erno 3): server error

$shell#



==============
super low ram
==============
about the same. The difference is that I get some more skipping this and that. In the ende I get again
mount can't find /ramdisk in /etc/fstab/ or /etc/mtab/

Posted by drio on Oct. 31 2006,20:26
I forgot to mention that I used both the dsl-3.0.1.iso and the dsl-3.0.1-syslinux.iso with
a) no boot options
b) lowram
c) super low ram (as mentioned in the wiki)

but the result was always the same

I hope this helps a bit

Posted by ^thehatsrule^ on Oct. 31 2006,21:11
What does it say before "Starting init process."
from "Accessing DSL image at..."

If you can, you could also try pasting the output of 'dmesg' when you are in the shell.

Posted by drio on Nov. 01 2006,14:55
Hi

It begins with:

Accessing DSL image at /dev/scd0/
Total memory found: 13264 kB      ( <==== I have 16 MB)
Creating directories and symlinks on ramdisk ... Done
Starting init process
INIT: version 2.87-knoppix booting
Running Linux Kernel
etc (from now on, as described in my previous post)



Moreover, I noticed that before saying:
Uncompressing Linux Ok, booting the kernel

it says:
You passed an undefined mode number
Press <return> to see video modes available, <space> to continue or wait 30 secs.

I skipped this one as I sometimes went away from the PC fo more than 30 sec and it just continued. I selected a different mode but nothing different happened.

Posted by drio on Nov. 01 2006,15:08
oops I forgot the dmesg.

Here it is...

Linux version 2.4.26 (root@Knoppix) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 SMP Sa Apr 17 19:33:42 CEST 2004
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000001000000 (usable)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
16MB LOWMEM available.
On node 0 totalpages: 4096
zone(0): 4096 pages.
zone(1): 0 pages.
zone(2): 0 pages.
DMI not present.
ACPI: Unable to locate RSDP
Kernel command line: ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 initrd=minirt24.gz nomce noapic quiet BOOT_IMAGE=knoppix BOOT_IMAGE=linux24
No local APIC present or hardware disabled
Initializing CPU#0
Detected 132.728 MHz processor.
Console: colour VGA+ 132x25
Calibrating delay loop... 264.60 BogoMIPS
Memory: 12948k/16384k available (1371k kernel code, 3052k reserved, 561k data, 140k init, 0k highmem)
Dentry cache hash table entries: 2048 (order: 2, 16384 bytes)
Inode cache hash table entries: 1024 (order: 1, 8192 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Intel Pentium with F0 0F bug - workaround enabled.
CPU:     After generic, caps: 000001bf 00000000 00000000 00000000
CPU:             Common caps: 000001bf 00000000 00000000 00000000
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: none
CPU:     After generic, caps: 000001bf 00000000 00000000 00000000
CPU:             Common caps: 000001bf 00000000 00000000 00000000
CPU0: Intel Pentium 75 - 200 stepping 0c
per-CPU timeslice cutoff: 160.11 usecs.
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Waiting on wait_init_idle (map = 0x0)
All processors have done init_idle
ACPI: Subsystem revision 20040326
ACPI: Interpreter disabled.
PCI: PCI BIOS revision 2.10 entry at 0xfb150, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: ACPI tables contain no PCI IRQ routing entries
PCI: Probing PCI hardware (bus 00)
Limiting direct PCI/PCI transfers.
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Disk quotas vdquot_6.5.1
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
RAMDISK driver initialized: 16 RAM disks of 100000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIXa: IDE controller at PCI slot 00:07.0
PIIXa: chipset revision 2
PIIXa: not 100% native mode: will probe irqs later
PIIXa: neither IDE port enabled (BIOS)
PIIXb: IDE controller at PCI slot 00:07.1
PIIXb: chipset revision 2
PIIXb: not 100% native mode: will probe irqs later
   ide0: BM-DMA at 0x3000-0x3007, BIOS settings: hda:pio, hdb:pio
   ide1: BM-DMA at 0x3008-0x300f, BIOS settings: hdc:pio, hdd:pio
hdb: ASUS CD-S500/A, ATAPI CD/DVD-ROM drive
hdc: QUANTUM FIREBALL1280A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hdc: attached ide-disk driver.
hdc: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: task_no_data_intr: error=0x04 { DriveStatusError }
hdc: 2503872 sectors (1282 MB) w/83KiB Cache, CHS=2484/16/63
Partition check:
hdc: [PTBL] [621/64/63] hdc1 hdc2
ide: late registration of driver.
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
Initializing Cryptographic API
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 1024 bind 1024)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 314k freed
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
hdb: attached ide-scsi driver.
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
 Vendor: ASUS      Model: CD-S500/A         Rev: 1.3C
 Type:   CD-ROM                             ANSI SCSI revision: 02
Attached scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0
sr0: scsi3-mmc drive: 24x/50x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.12
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
cloop: Initializing cloop v2.01
cloop: loaded (max 8 devices)
cloop: /cdrom/KNOPPIX/KNOPPIX: 1891 blocks, 65536 bytes/block, largest block is 65552 bytes.
ISO 9660 Extensions: RRIP_1991A
Freeing unused kernel memory: 140k freed
Real Time Clock Driver v1.10f
apm: BIOS not found.
Linux Kernel Card Services 3.1.22
 options:  [pci] [cardbus] [pm]
Intel ISA PCIC probe: not found.
Databook TCIC-2 PCMCIA probe: not found.
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 19:48:59 Apr 17 2004
usb-uhci.c: High bandwidth mode enabled
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: deregistering driver usbdevfs
usb.c: deregistering driver hub
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: deregistering driver usbdevfs
usb.c: deregistering driver hub
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE]
parport0: irq 7 detected
Adding Swap: 276184k swap-space (priority -1)
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
hid-core.c: USB HID support drivers
mice: PS/2 mouse device common for all mice

Posted by ^thehatsrule^ on Nov. 01 2006,22:54
Try booting with mem=16M
however, if you used shared memory i.e. with your video, etc. subtract amount from 16 and use that instead.

Don't worry about the undefined mode # for now, but that's usually fixed by specifying the geometry to fit your monitor (by vga= )

Posted by drio on Nov. 02 2006,17:54
Quote (^thehatsrule^ @ Nov. 01 2006,17:54)
Try booting with mem=16M
however, if you used shared memory i.e. with your video, etc. subtract amount from 16 and use that instead.

boot: dsl mem=16M

I tried this and I still get the same :-(

Quote
Don't worry about the undefined mode # for now, but that's usually fixed by specifying the geometry to fit your monitor (by vga= )

Even if I leave it as is (press space) or choose any of the modes, the result is the same...

Hope you didn't run out of ideas :-)

Posted by ^thehatsrule^ on Nov. 02 2006,18:12
Are you sure you aren't using shared memory anywhere?
Maybe try booting with mem=12M  - try combinations with the superlowram/failsafe/etc.  Maybe you should also try booting directly to console first (dsl 2).

Hm, did you try like vga=787 etc?  Doesn't matter anyways atm. (maybe you need to use fb modes)

Also, did you check if your DSL media was corrupt, or if it worked on another machine?

Posted by drio on Nov. 02 2006,18:45
I am quite sure there is no shared ram. I mean that there is no audio or network or modem devices on the mainboard. I also have mounted a graphics card, which previoulsy worked with debian and X on this machine.

Is there any way to identify the usage of shared memory?

Also even if I try vga=787 and others I still get the indefined mode number...

I had previously checked the md5sum of both floppy and cd. I now tried the cd on my AMD sempron and it works fine. Now that I have seen DLS running, I must admit it's quite cool! Look what 50M of bytes can do :-)



I just noticed that for hdc "QUANTUM FIREBALL1280A, ATA DISK drive" (my hard drive) dmesg says:

hdc: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hdc: task_no_data_intr: error=0x04 { DriveStatusError }

Could there something be wrong with my hd drive? But then how does it creates /etc/fstab?

Posted by ^thehatsrule^ on Nov. 02 2006,19:04
"mounted" cards doesn't mean that it doesn't  use shared memory afaik...

You can output `lspci -v` maybe.

You'll probably have to manually compute a code for your monitor/video if the general vga or fb codes don't work.  What type of monitor are you using?


Hm, `cat /etc/fstab`? Maybe try disabling your hdd in your bios before trying to boot again.

Wonder if all these problems are because of one thing...

Posted by bkil on Nov. 02 2006,21:22
Quote (drio @ Nov. 02 2006,13:45)

Hi.

There's probably nothing wrong with your HDD, I've seen that message before on "functional" systems. Linux also detects 13MB for my config, 3MB isn't much for the kernel.
Furthermore, I think I have posted your solution here: < X problems - runlevel 2 >

Regards,
bkil

Posted by drio on Nov. 04 2006,18:58
bkil:
I tried to follow your instructions althought I don't think I understand what

/grub\ dsl 2

is this one.
Also I don't understand the

su dsl

from what I have seen only sudo su is needed.

Hoever all the other are working up to a point. In order to rm the directories I have to be su (I get permission denied). If I start X as su I get several stuff. But this could be due to the fact that su can't have X in dsl?


If I start X as user dsl everything is working fine :-) :-)

Thanks both bkil and ^thehatsrule^ for your time

Posted by bkil on Nov. 06 2006,12:39
Dear drio,

Glad to hear you've got DSL working. :)

About my instructions: well, I have to confess that I made them up from memory, :blush:  you see I don't boot LiveCD's too often, I only needed those commands as a quick hack to make harddrive install work on a PC... Let me try to clarify that post a bit (again from memory)

The first line was supposed to mean that I think it's sufficient for you to simply enter "dsl 2" at the grub boot prompt (you could append other parameters as you will), and as a consequence, the CD will log you into a rather clean root session (no "sudo su" needed for the empty /tmp, /opt recreation).
"su dsl" (or "su - dsl" if you'd like to have a login shell) is needed to change user from root to dsl, to enable you to run startx (it's not needed for installation of course).
After a harddrive install, you probably make both your /opt and /tmp non-volatile, so you don't need these "tricks" later on.
And the superuser can also start X sessions (at least on a hard install), his(her) config files in /root work the same way as any other user's in /home/*. Not that root would need X or anything... :D Anyway, if startx throws errors, you need to either set your home directory, or make sure you use a valid configuration by copying, creating or editing your (hidden) config files and scripts. (Though all worked as expected automagically after a full HD-install over here)

Yours,
bkil

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.