Re: Booting problem
On Sun 13 Nov 2022 at 08:24:11 (+0530), Emilia Maher wrote: > Hello, > I have installed NetBeans through snapd process, as explained here: > > https://wiki.debian.org/Netbeans > > But after installation completed, I have faced booting problem. > Then I have removed the snapd through terminal command as well I followed > the instructions given here: > https://wiki.debian.org/ReduceDebian#Remove_unnecessary_kernel_modules > > To clear the unwanted packages but still I am facing the same booting > problem. > Please let me know what I can do to fix booting problem. It might be an idea to explain what the nature of your booting problem is. Cheers, David.
Booting problem
Hello, I have installed NetBeans through snapd process, as explained here: https://wiki.debian.org/Netbeans But after installation completed, I have faced booting problem. Then I have removed the snapd through terminal command as well I followed the instructions given here: https://wiki.debian.org/ReduceDebian#Remove_unnecessary_kernel_modules To clear the unwanted packages but still I am facing the same booting problem. Please let me know what I can do to fix booting problem. Thanks and Regards
pxe booting problem
Hi,
I tried to install debian via PXE.
following the doc, I install netboot.tar.gz which contains pxe file.
I configured the dhcpd.conf here is relevant part :
host 00016CB3066E{ # MAC
hardware ethernet 00:01:6C:B3:06:6E;
fixed-address172.19.6.224;
server-namedebian225;
next-serverdebian225;
filename /var/lib/tftpboot/pxelinux.0;
}
I decompressed netboot.tar in /var/lib/tftpboot ,
I installed tftpd-hpa
first problem:
the file contains /etc/default/tftpd-hpa
RUN_DAEMON=no
OPTIONS=-l -s /var/lib/tftpboot
so the standalone tftpd-hpa is disabled, ??
While the file /etc/inetd.conf contains the good line
tftp dgram udp waitroot /usr/sbin/in.tftpd
/usr/sbin/in.tftpd -s /var/lib/tftpboot
When I boot a remote machine, I get correct address from the dhcp,
but the error is : file not found tftp error ?
why I declared pxelinux0 in the /var/lib/tftpboot
question: must I run a standlone /tftpd-hpa or thru inetd, where I have to
declare pxelinux0for the connection
thanks a lot
bela
Re: pxe booting problem
Hi,
I tried to install debian via PXE.
following the doc, I install netboot.tar.gz which contains pxe file.
I configured the dhcpd.conf here is relevant part :
host 00016CB3066E{ # MAC
hardware ethernet 00:01:6C:B3:06:6E;
fixed-address172.19.6.224;
server-namedebian225;
next-serverdebian225;
filename /var/lib/tftpboot/pxelinux.0;
}
I decompressed netboot.tar in /var/lib/tftpboot ,
I installed tftpd-hpa
first problem:
the file contains /etc/default/tftpd-hpa
RUN_DAEMON=no
OPTIONS=-l -s /var/lib/tftpboot
so the standalone tftpd-hpa is disabled, ??
Yes, that's correct: the tftp-Server is not running stand-alone, but it
will be executed by inetd whenever neede (so you have to verify that the
inetd-server ist really running).
Of course - if you prefer - you can also use the standalon tftp-Server
and uncomment the line in inetd.conf - it shouldn't make any difference
While the file /etc/inetd.conf contains the good line
tftp dgram udp waitroot /usr/sbin/in.tftpd
/usr/sbin/in.tftpd -s /var/lib/tftpboot
When I boot a remote machine, I get correct address from the dhcp,
but the error is : file not found tftp error ?
why I declared pxelinux0 in the /var/lib/tftpboot
The easiest would be to use a network sniffer like wireshark in order to
verify which file the client is trying to download exactly. However, in
your configuration of the tftp-Server, the file
/var/lib/tftpboot/pxelinux.0 on the server will be accessed by
pxelinux.0 - without the directory. So just try
filename pxelinux.0;
instead of
filename /var/lib/tftpboot/pxelinux.0;
maybe that will work...
HTH,
Axel
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pxe booting problem
On Mon, Sep 14, 2009 at 12:53:31PM +0100, abdelkader belahcene wrote:
Hi,
I tried to install debian via PXE.
following the doc, I install netboot.tar.gz which contains pxe file.
I configured the dhcpd.conf here is relevant part :
host 00016CB3066E{ # MAC
hardware ethernet 00:01:6C:B3:06:6E;
fixed-address172.19.6.224;
server-namedebian225;
next-serverdebian225;
filename /var/lib/tftpboot/pxelinux.0;
Make that:
filename /tftpboot/pxelinux.0;
Note the option -s in the command-line of tftpd .
}
I decompressed netboot.tar in /var/lib/tftpboot ,
I installed tftpd-hpa
first problem:
the file contains /etc/default/tftpd-hpa
RUN_DAEMON=no
OPTIONS=-l -s /var/lib/tftpboot
so the standalone tftpd-hpa is disabled, ??
While the file /etc/inetd.conf contains the good line
tftp dgram udp waitroot /usr/sbin/in.tftpd
/usr/sbin/in.tftpd -s /var/lib/tftpboot
When I boot a remote machine, I get correct address from the dhcp,
but the error is : file not found tftp error ?
why I declared pxelinux0 in the /var/lib/tftpboot
This should indeed be easy to test. 'tftp' is a tftp client.
question: must I run a standlone /tftpd-hpa or thru inetd, where I have to
declare pxelinux0for the connection
Shouldn't really matter.
--
Tzafrir Cohen | tzaf...@jabber.org | VIM is
http://tzafrir.org.il || a Mutt's
tzaf...@cohens.org.il || best
ICQ# 16849754 || friend
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: pxe booting problem
On Mon, Sep 14, 2009 at 12:53:31PM +0100, abdelkader belahcene wrote:
Hi,
I tried to install debian via PXE.
following the doc, I install netboot.tar.gz which contains pxe file.
I configured the dhcpd.conf here is relevant part :
host 00016CB3066E{ # MAC
hardware ethernet 00:01:6C:B3:06:6E;
fixed-address172.19.6.224;
server-namedebian225;
next-serverdebian225;
filename /var/lib/tftpboot/pxelinux.0;
}
I decompressed netboot.tar in /var/lib/tftpboot ,
I installed tftpd-hpa
first problem:
the file contains /etc/default/tftpd-hpa
RUN_DAEMON=no
OPTIONS=-l -s /var/lib/tftpboot
so the standalone tftpd-hpa is disabled, ??
While the file /etc/inetd.conf contains the good line
tftp dgram udp waitroot /usr/sbin/in.tftpd
/usr/sbin/in.tftpd -s /var/lib/tftpboot
When I boot a remote machine, I get correct address from the dhcp,
but the error is : file not found tftp error ?
why I declared pxelinux0 in the /var/lib/tftpboot
question: must I run a standlone /tftpd-hpa or thru inetd, where I have to
declare pxelinux0for the connection
Did you /etc/init.d/openbsd-inetd restart after editing its config
file?
-Rob
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Multiple SATA disks, two OSs and booting problem
On 2/20/08, Tero Mäntyvaara [EMAIL PROTECTED] wrote: Owen Townend wrote: On 2/20/08, *Tero Mäntyvaara* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Owen Townend wrote: On 2/20/08, *Tero Mäntyvaara* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I have got motherboard that has support for four (4) SATA devices. I have installed Debian 4.0r2 AMD64 on filesystem witch has been build on top of LVM system. LVM is on top of software-raid1 device md0 with two SAMSUNG SP1614C (SATA) disks. Everything works well. But if I connect two other disks (SATA2), there is volume group (named VG1) on those disks and KnoppMyth OS installed on one partition of the other disk, booting into Debian fails. Further investigated: If I connect either of the two KnoppMyth VG1 disks Debian boots well. And while all disks connected booting into KnoppMyth goes well. Here is the output: kinit: name_to_dev_t(/dev/mapper/VG0-LV--swap) = dm-8(253,8) kinit: trying to resume from /dev/mapper/VG0-LV--swap Attempting manual resume kinit: No resume image, doing normal boot... resume: libgcrypt version 1.2.3 resume: Could not read the image Done. kjournald starting. Commit internal 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned of (initramfs) Here is the illustration of the disks: Debian: -- FS: /boot (LV-dir-boot) /usr (LV-dir-usr) /var (LV-dir-var) /home (LV-dir-home) /usr/local (LV-dir-usr-local) / (LV-root) /tmp (LV-dir-tmp) swap (LV-swap) - LVM: LVs: LV-dir-boot LV-dir-usr LV-dir-var LV-dir-home LV-dir-usr-local LV-root LV-dir-tmp LV-swap VG: VG0 -- RAID: md0 (RAID1): hde1, hdg1 -- Partitions: hde hde1 (Auto RAID) hdg hdg1 (Auto RAID) -- Disks: SAMSUNG SP1614C (hde) SAMSUNG SP1614C (hdg) -- KnoppMyth: -- FS: / (sdb1) swap (sdb2) - LVM: LVs: myth VG: VG1 (sda2, sdb3) -- Partitions: sda sda1 (linux swap) sda2 (linux LVM) sdb sdb1 (linux) sdb2 (linux swap) sdb3 (linux LVM) -- Disks: SAMSUNG HD300LJ (sda) SAMSUNG HD321KJ (sdb) -- Tero Mäntyvaara -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Hey, Looks like it can't find the right disks/partitions to boot from. The order may be being re-arranged when you attach them all at once. Could be an issue with
Multiple SATA disks, two OSs and booting problem
Hi, I have got motherboard that has support for four (4) SATA devices. I have installed Debian 4.0r2 AMD64 on filesystem witch has been build on top of LVM system. LVM is on top of software-raid1 device md0 with two SAMSUNG SP1614C (SATA) disks. Everything works well. But if I connect two other disks (SATA2), there is volume group (named VG1) on those disks and KnoppMyth OS installed on one partition of the other disk, booting into Debian fails. Further investigated: If I connect either of the two KnoppMyth VG1 disks Debian boots well. And while all disks connected booting into KnoppMyth goes well. Here is the output: kinit: name_to_dev_t(/dev/mapper/VG0-LV--swap) = dm-8(253,8) kinit: trying to resume from /dev/mapper/VG0-LV--swap Attempting manual resume kinit: No resume image, doing normal boot... resume: libgcrypt version 1.2.3 resume: Could not read the image Done. kjournald starting. Commit internal 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned of (initramfs) Here is the illustration of the disks: Debian: -- FS: /boot (LV-dir-boot) /usr (LV-dir-usr) /var (LV-dir-var) /home (LV-dir-home) /usr/local (LV-dir-usr-local) / (LV-root) /tmp (LV-dir-tmp) swap (LV-swap) - LVM: LVs: LV-dir-boot LV-dir-usr LV-dir-var LV-dir-home LV-dir-usr-local LV-root LV-dir-tmp LV-swap VG: VG0 -- RAID: md0 (RAID1): hde1, hdg1 -- Partitions: hde hde1 (Auto RAID) hdg hdg1 (Auto RAID) -- Disks: SAMSUNG SP1614C (hde) SAMSUNG SP1614C (hdg) -- KnoppMyth: -- FS: / (sdb1) swap (sdb2) - LVM: LVs: myth VG: VG1 (sda2, sdb3) -- Partitions: sda sda1 (linux swap) sda2 (linux LVM) sdb sdb1 (linux) sdb2 (linux swap) sdb3 (linux LVM) -- Disks: SAMSUNG HD300LJ (sda) SAMSUNG HD321KJ (sdb) -- Tero Mäntyvaara -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Multiple SATA disks, two OSs and booting problem
On 2/20/08, Tero Mäntyvaara [EMAIL PROTECTED] wrote: Hi, I have got motherboard that has support for four (4) SATA devices. I have installed Debian 4.0r2 AMD64 on filesystem witch has been build on top of LVM system. LVM is on top of software-raid1 device md0 with two SAMSUNG SP1614C (SATA) disks. Everything works well. But if I connect two other disks (SATA2), there is volume group (named VG1) on those disks and KnoppMyth OS installed on one partition of the other disk, booting into Debian fails. Further investigated: If I connect either of the two KnoppMyth VG1 disks Debian boots well. And while all disks connected booting into KnoppMyth goes well. Here is the output: kinit: name_to_dev_t(/dev/mapper/VG0-LV--swap) = dm-8(253,8) kinit: trying to resume from /dev/mapper/VG0-LV--swap Attempting manual resume kinit: No resume image, doing normal boot... resume: libgcrypt version 1.2.3 resume: Could not read the image Done. kjournald starting. Commit internal 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned of (initramfs) Here is the illustration of the disks: Debian: -- FS: /boot (LV-dir-boot) /usr (LV-dir-usr) /var (LV-dir-var) /home (LV-dir-home) /usr/local (LV-dir-usr-local) / (LV-root) /tmp (LV-dir-tmp) swap (LV-swap) - LVM: LVs: LV-dir-boot LV-dir-usr LV-dir-var LV-dir-home LV-dir-usr-local LV-root LV-dir-tmp LV-swap VG: VG0 -- RAID: md0 (RAID1): hde1, hdg1 -- Partitions: hde hde1 (Auto RAID) hdg hdg1 (Auto RAID) -- Disks: SAMSUNG SP1614C (hde) SAMSUNG SP1614C (hdg) -- KnoppMyth: -- FS: / (sdb1) swap (sdb2) - LVM: LVs: myth VG: VG1 (sda2, sdb3) -- Partitions: sda sda1 (linux swap) sda2 (linux LVM) sdb sdb1 (linux) sdb2 (linux swap) sdb3 (linux LVM) -- Disks: SAMSUNG HD300LJ (sda) SAMSUNG HD321KJ (sdb) -- Tero Mäntyvaara -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Hey, Looks like it can't find the right disks/partitions to boot from. The order may be being re-arranged when you attach them all at once. Could be an issue with identification, are you using device paths or uuid's in grub? On the subject of grub, what's your boot setup? Where is the boot manager installed and what's in your menu.1st (or equiv non-grub) ? If in doubt post your /boot/grub/menu.1st Just a thought. cheers, Owen.
Re: Multiple SATA disks, two OSs and booting problem
Owen Townend wrote: On 2/20/08, *Tero Mäntyvaara* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I have got motherboard that has support for four (4) SATA devices. I have installed Debian 4.0r2 AMD64 on filesystem witch has been build on top of LVM system. LVM is on top of software-raid1 device md0 with two SAMSUNG SP1614C (SATA) disks. Everything works well. But if I connect two other disks (SATA2), there is volume group (named VG1) on those disks and KnoppMyth OS installed on one partition of the other disk, booting into Debian fails. Further investigated: If I connect either of the two KnoppMyth VG1 disks Debian boots well. And while all disks connected booting into KnoppMyth goes well. Here is the output: kinit: name_to_dev_t(/dev/mapper/VG0-LV--swap) = dm-8(253,8) kinit: trying to resume from /dev/mapper/VG0-LV--swap Attempting manual resume kinit: No resume image, doing normal boot... resume: libgcrypt version 1.2.3 resume: Could not read the image Done. kjournald starting. Commit internal 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned of (initramfs) Here is the illustration of the disks: Debian: -- FS: /boot (LV-dir-boot) /usr (LV-dir-usr) /var (LV-dir-var) /home (LV-dir-home) /usr/local (LV-dir-usr-local) / (LV-root) /tmp (LV-dir-tmp) swap (LV-swap) - LVM: LVs: LV-dir-boot LV-dir-usr LV-dir-var LV-dir-home LV-dir-usr-local LV-root LV-dir-tmp LV-swap VG: VG0 -- RAID: md0 (RAID1): hde1, hdg1 -- Partitions: hde hde1 (Auto RAID) hdg hdg1 (Auto RAID) -- Disks: SAMSUNG SP1614C (hde) SAMSUNG SP1614C (hdg) -- KnoppMyth: -- FS: / (sdb1) swap (sdb2) - LVM: LVs: myth VG: VG1 (sda2, sdb3) -- Partitions: sda sda1 (linux swap) sda2 (linux LVM) sdb sdb1 (linux) sdb2 (linux swap) sdb3 (linux LVM) -- Disks: SAMSUNG HD300LJ (sda) SAMSUNG HD321KJ (sdb) -- Tero Mäntyvaara -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Hey, Looks like it can't find the right disks/partitions to boot from. The order may be being re-arranged when you attach them all at once. Could be an issue with identification, are you using device paths or uuid's in grub? On the subject of grub, what's your boot setup? Where is the boot manager installed and what's in your menu.1st (or equiv non-grub) ? If in doubt post your /boot/grub/menu.1st Just a thought. cheers, Owen. Hi, LILO has installed in system by default. Installation target was /dev/md0 and I remember that there was some problems with that in installer. Here is also content of the lilo.conf: # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', # --- `install-mbr(8)', `/usr/share/doc/lilo/', # and `/usr/share/doc/mbr/'. # +---+ # |!! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt' (if you have created it), or | # | install a new kernel. The computer will most likely fail to | # | boot if a kernel-image post-install script or you don't | # | remember to run `lilo'. | # | | # +---+ #
Re: Multiple SATA disks, two OSs and booting problem
On 2/20/08, Tero Mäntyvaara [EMAIL PROTECTED] wrote: Owen Townend wrote: On 2/20/08, *Tero Mäntyvaara* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I have got motherboard that has support for four (4) SATA devices. I have installed Debian 4.0r2 AMD64 on filesystem witch has been build on top of LVM system. LVM is on top of software-raid1 device md0 with two SAMSUNG SP1614C (SATA) disks. Everything works well. But if I connect two other disks (SATA2), there is volume group (named VG1) on those disks and KnoppMyth OS installed on one partition of the other disk, booting into Debian fails. Further investigated: If I connect either of the two KnoppMyth VG1 disks Debian boots well. And while all disks connected booting into KnoppMyth goes well. Here is the output: kinit: name_to_dev_t(/dev/mapper/VG0-LV--swap) = dm-8(253,8) kinit: trying to resume from /dev/mapper/VG0-LV--swap Attempting manual resume kinit: No resume image, doing normal boot... resume: libgcrypt version 1.2.3 resume: Could not read the image Done. kjournald starting. Commit internal 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned of (initramfs) Here is the illustration of the disks: Debian: -- FS: /boot (LV-dir-boot) /usr (LV-dir-usr) /var (LV-dir-var) /home (LV-dir-home) /usr/local (LV-dir-usr-local) / (LV-root) /tmp (LV-dir-tmp) swap (LV-swap) - LVM: LVs: LV-dir-boot LV-dir-usr LV-dir-var LV-dir-home LV-dir-usr-local LV-root LV-dir-tmp LV-swap VG: VG0 -- RAID: md0 (RAID1): hde1, hdg1 -- Partitions: hde hde1 (Auto RAID) hdg hdg1 (Auto RAID) -- Disks: SAMSUNG SP1614C (hde) SAMSUNG SP1614C (hdg) -- KnoppMyth: -- FS: / (sdb1) swap (sdb2) - LVM: LVs: myth VG: VG1 (sda2, sdb3) -- Partitions: sda sda1 (linux swap) sda2 (linux LVM) sdb sdb1 (linux) sdb2 (linux swap) sdb3 (linux LVM) -- Disks: SAMSUNG HD300LJ (sda) SAMSUNG HD321KJ (sdb) -- Tero Mäntyvaara -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Hey, Looks like it can't find the right disks/partitions to boot from. The order may be being re-arranged when you attach them all at once. Could be an issue with identification, are you using device paths or uuid's in grub? On the subject of grub, what's your boot setup? Where is the boot manager installed and what's in your menu.1st (or equiv non-grub) ? If in doubt post your /boot/grub/menu.1st Just a thought. cheers, Owen. Hi, LILO has installed in system by default. Installation target was /dev/md0 and I remember that there was some problems with that in installer. Here is also content of the lilo.conf: # /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)', # --- `install-mbr(8)', `/usr/share/doc/lilo/', # and `/usr/share/doc/mbr/'. # +---+ # |!! Reminder !! | # | | # | Don't forget to run `lilo' after you make changes to this | # | conffile, `/boot/bootmess.txt' (if you have created it), or | # | install a new
Re: Multiple SATA disks, two OSs and booting problem
Owen Townend wrote: On 2/20/08, *Tero Mäntyvaara* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Owen Townend wrote: On 2/20/08, *Tero Mäntyvaara* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, I have got motherboard that has support for four (4) SATA devices. I have installed Debian 4.0r2 AMD64 on filesystem witch has been build on top of LVM system. LVM is on top of software-raid1 device md0 with two SAMSUNG SP1614C (SATA) disks. Everything works well. But if I connect two other disks (SATA2), there is volume group (named VG1) on those disks and KnoppMyth OS installed on one partition of the other disk, booting into Debian fails. Further investigated: If I connect either of the two KnoppMyth VG1 disks Debian boots well. And while all disks connected booting into KnoppMyth goes well. Here is the output: kinit: name_to_dev_t(/dev/mapper/VG0-LV--swap) = dm-8(253,8) kinit: trying to resume from /dev/mapper/VG0-LV--swap Attempting manual resume kinit: No resume image, doing normal boot... resume: libgcrypt version 1.2.3 resume: Could not read the image Done. kjournald starting. Commit internal 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory Done. mount: Mounting /sys on /root/sys failed: No such file or directory mount: Mounting /proc on /root/proc failed: No such file or directory Target filesystem doesn't have /sbin/init BusyBox v1.1.3 (Debian 1:1.1.3-4) Built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned of (initramfs) Here is the illustration of the disks: Debian: -- FS: /boot (LV-dir-boot) /usr (LV-dir-usr) /var (LV-dir-var) /home (LV-dir-home) /usr/local (LV-dir-usr-local) / (LV-root) /tmp (LV-dir-tmp) swap (LV-swap) - LVM: LVs: LV-dir-boot LV-dir-usr LV-dir-var LV-dir-home LV-dir-usr-local LV-root LV-dir-tmp LV-swap VG: VG0 -- RAID: md0 (RAID1): hde1, hdg1 -- Partitions: hde hde1 (Auto RAID) hdg hdg1 (Auto RAID) -- Disks: SAMSUNG SP1614C (hde) SAMSUNG SP1614C (hdg) -- KnoppMyth: -- FS: / (sdb1) swap (sdb2) - LVM: LVs: myth VG: VG1 (sda2, sdb3) -- Partitions: sda sda1 (linux swap) sda2 (linux LVM) sdb sdb1 (linux) sdb2 (linux swap) sdb3 (linux LVM) -- Disks: SAMSUNG HD300LJ (sda) SAMSUNG HD321KJ (sdb) -- Tero Mäntyvaara -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Hey, Looks like it can't find the right disks/partitions to boot from. The order may be being re-arranged when you attach them all at once. Could be an issue with identification, are you using device paths or uuid's in grub? On the subject of grub, what's your boot setup? Where is the boot manager installed and what's in your menu.1st (or equiv non-grub) ? If in doubt post your /boot/grub/menu.1st Just a thought. cheers, Owen. Hi, LILO has installed in system by
RocketRAID, SATA disks and booting problem
Hi, I have installed Debian 4.0r2 AMD64 on filesystem witch has been build on top of LVM system. LVM is on top of software-raid1 device md0 with two SAMSUNG SP1614C disks. Disks are connected to RocketRAID 1640 SATA-controller. Everything works well. But if I connect two other disks to controller that is on the motherboard, there is LVM VG1 on these disks and KnoppMyth OS installed on one partition of the other disk, booting into Debian fails. I have choosen to boot from RocketRAID. If I swap the disks on RockerRAID to the motherboard controller and disks on motherboard conroller to the RocketRAID there is no difference. Here is the illustration of the disks: Debian: -- FS: /boot (LV-dir-boot) /usr (LV-dir-usr) /var (LV-dir-var) /home (LV-dir-home) /usr/local (LV-dir-usr-local) / (LV-root) /tmp (LV-dir-tmp) swap (LV-swap) - LVM: LVs: LV-dir-boot LV-dir-usr LV-dir-var LV-dir-home LV-dir-usr-local LV-root LV-dir-tmp LV-swap VG: VG0 -- RAID: md0 (RAID1): hde1, hdg1 -- Partitions: hde hde1 hdg hdg1 -- Disks: SAMSUNG SP1614C (hde) SAMSUNG SP1614C (hdg) -- KnoppMyth: -- FS: / (sdb1) swap (sdb2) - LVM: LVs: myth VG: VG1 (sda2, sdb3) -- Partitions: sda sda1 (linux swap) sda2 (linux LVM) sdb sdb1 (linux) sdb2 (linux swap) sdb3 (linux LVM) -- Disks: SAMSUNG HD300LJ (sda) SAMSUNG HD321KJ (sdb) -- Tero Mäntyvaara -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Dual Core Booting Problem -And S...S...st...stutt...stuttering Operation
Hi folks... The saga with the speed and booting issues with this new 64bit-AMD-dual- core continues (for those who recall the earlier posts with a similar/same subject line). I eventually swapped out the 4x1gig memory modules for Kingston Units and it is at least now booting with all 4 slots occupied but I'm still not happy with the speed of the machine, or with it's constant hanging/freezing whenever I am typing. (E.g. in the time it took me to type this above the input and screen updating froze three times each time for about 6 seconds .. (it's just done it again). I have upgraded the BIOS to version '6f' from the gigabyte site but was then getting the 8254 Bug -no timer connected to IO-APIC at POST. This has been cleared by specifying NOAPIC at boot... but I am still suffering from this 'freezing/stuttering' when typing and the whole machine just seems sluggish. For info: Its a gigabyte motherboard M61p-S3 AMD Dual Core 64 bit 4600+ (running at a BIOS reported 2400mhz and a 200mhz clock) with 4 x1gig 660mhz Kingston Modules. It's a 550watt PSU, and a 7200rpm 360gig drive Anyone else come across this stuttering and a 'just too slow' operation. It takes 6 seconds to fire up Evolution and a whopping 32 seconds to bring up Open Office. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Large initrd [Was: Re: booting problem (udev related?)]
On Thu, Aug 02, 2007 at 08:34:00PM -0400, Douglas Allan Tutty wrote: However, don't all those modules in the initrd end up staying in the kernel anyway, or do they get unloaded during boot? If they stay, and 'most' modules get added, how is that different than having a huge monolithic kernel? It may not matter on a box with huge memory, but I have mostly small-memory boxes. I may be wrong, but I think that only the needed modules are actually loaded. As for xorg-video-foo, that's why I don't install the xorg metapackage. I choose from its dependencies what I need. Same here /rant There's a growing kitchen-sink approach in Debian (perhaps all of Linux, I don't know). There's the kernel/initrd size, there's the variable device name problems, to name two. It suggests to me that there's a missing piece of infrastructure. Perhaps the installer system should create a hardware inventory file that initrdtools (or whatever the nom de jure) can access to generate a tailord initrd, that apt can consult for what drivers to download, etc. The installer rescue mode could offer a tool to regenerate the inventory file for times when one changes hardware. /end rant True, but you have to consider the competition. If you plug a new device into a Windows machine the driver gets installed automatically or you get prompted for the drivers if Windows doesn't have them. You have to admit that this is pretty convenient functionality which has been there at least since Windows 2000 (how this is cluttering the registry and the fact that it isn't always working is a totally different topic). The big advantage on linux (and especially Debian) is that power users still have the possibility to customize the setup (like using a different mkinitrd, different options, purge unneeded packages, ...) that a Windows user doesn't have. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
design focus [was Large initrd, was booting problem (udev related?)]
On Fri, Aug 03, 2007 at 05:54:57PM +0300, Andrei Popescu wrote: On Thu, Aug 02, 2007 at 08:34:00PM -0400, Douglas Allan Tutty wrote: However, don't all those modules in the initrd end up staying in the kernel anyway, or do they get unloaded during boot? If they stay, and 'most' modules get added, how is that different than having a huge monolithic kernel? It may not matter on a box with huge memory, but I have mostly small-memory boxes. I may be wrong, but I think that only the needed modules are actually loaded. As for xorg-video-foo, that's why I don't install the xorg metapackage. I choose from its dependencies what I need. Same here All these extra packages together take a lot of disk space, a lot of download bandwidth to install and maintain. /rant There's a growing kitchen-sink approach in Debian (perhaps all of Linux, I don't know). There's the kernel/initrd size, there's the variable device name problems, to name two. It suggests to me that there's a missing piece of infrastructure. Perhaps the installer system should create a hardware inventory file that initrdtools (or whatever the nom de jure) can access to generate a tailord initrd, that apt can consult for what drivers to download, etc. The installer rescue mode could offer a tool to regenerate the inventory file for times when one changes hardware. /end rant True, but you have to consider the competition. I guess the problem is related to this notion of trying to compete with MS. If people 'buy' brand A because they like features x,y, and z, and brand B has the goal of gaining market share, it will tend to morph into a clone (feature-wise) of brand A. However, it will tend to take on some of the compromises of brand B that go with features x, y, and z. I stick with debian on my big box because of inertia, the debian policy, the debian security support for all packages in debian/main, and the absolute ease of applying bug fixes with aptitude. Debian also supports my trackball mouse's scroll wheel (IMPS/2) whereas OpenBSD does not. However, my older computers are transitioning away from Debian to BSD because of the newer debian (perhaps all linuxes) being so much slower on them than either older debians or new BSDs. If you plug a new device into a Windows machine the driver gets installed automatically or you get prompted for the drivers if Windows doesn't have them. You have to admit that this is pretty convenient functionality which has been there at least since Windows 2000 (how this is cluttering the registry and the fact that it isn't always working is a totally different topic). That convenience comes at a huge price in terms of system resource utilization on boxes with few resources. Compare it to OpenBSD, for example, where there is no such thing as eth0, but network interfaces based on driver name (eg. ne) and configuration; my 486 has one NIC as ne1. Its not convenient to have to look up in a file for the supported configurations of different hardware to ensure that your NIC is set up to match one of them then configure networking based on ne1. However, its only done once. The big advantage on linux (and especially Debian) is that power users still have the possibility to customize the setup (like using a different mkinitrd, different options, purge unneeded packages, ...) that a Windows user doesn't have. True, but rather than hotplugging, I would prefer a program that can be run as needed each time a new piece of hardware is attached for the first time, which would create the device node and load the appropriate module and parameters. Once done, it would get out of the way. On subsequent attachment of a device, everything would be pre-existing. It all comes down to the notion of competition and market share. If Debian is going to focus on market share and competing with MS it will have to target MS's target market. Since I'm not in that market, Debian will be shifting its focus on the market I'm in. It won't be that I'm drifting away from Debian but that Debian is drifting away from me. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: design focus [was Large initrd, was booting problem (udev related?)]
On Aug 3, 2007, at 9:25 AM, Douglas Allan Tutty wrote: I guess the problem is related to this notion of trying to compete with MS. If people 'buy' brand A because they like features x,y, and z, and brand B has the goal of gaining market share, it will tend to morph into a clone (feature-wise) of brand A. However, it will tend to take on some of the compromises of brand B that go with features x, y, and z. I stick with debian on my big box because of inertia, the debian policy, the debian security support for all packages in debian/main, and the absolute ease of applying bug fixes with aptitude. Debian also supports my trackball mouse's scroll wheel (IMPS/2) whereas OpenBSD does not. However, my older computers are transitioning away from Debian to BSD because of the newer debian (perhaps all linuxes) being so much slower on them than either older debians or new BSDs. I don't think it's so much Microsoft's influence as it is a difference in philosophy. Linux distributions put a lot of effort into being convenient desktop OSs. BSD tends to be aimed more at servers, where things like hotplugging aren't as important. If you have to check dmesg for the right device node and then run 'mount' to access a USB flash drive on a server, it doesn't matter much because you aren't going to be doing that often. If you have to do that on your desktop machine every time you plug in your digital camera, it gets old in a hurry. For that matter, ten years ago Linux distributions were already doing fully automated installers while NetBSD and OpenBSD still required you to get out a calculator to figure out the cylinder boundaries for the slices on your hard disk. The two OSs just occupy different points on the easy of use vs. compactness scale. You see this in hardware support, too. Linux tries to support the newest stuff, because that's what's in desktop machines (and sometimes suffers instability because of it), while BSD tends to take a more conservative approach. Hardware that's seen in desktops but rarely in servers often isn't supported or maintained well in BSD, because it's just not a priority. (The 3c509 ethernet driver, for example, was buggy for *years* in FreeBSD. It never really got fixed, the cards just became obsolete. ;) Another example: The Marvell Yukon gigabit ethernet chipset, common in desktops but rare in servers, is much slower under FreeBSD than under Linux.) It could be for your particular application, BSD is just the right tool for the job. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: design focus [was Large initrd, was booting problem (udev related?)]
On Fri, Aug 03, 2007 at 12:25:15PM -0400, Douglas Allan Tutty wrote: On Fri, Aug 03, 2007 at 05:54:57PM +0300, Andrei Popescu wrote: On Thu, Aug 02, 2007 at 08:34:00PM -0400, Douglas Allan Tutty wrote: However, don't all those modules in the initrd end up staying in the kernel anyway, or do they get unloaded during boot? If they stay, and 'most' modules get added, how is that different than having a huge monolithic kernel? It may not matter on a box with huge memory, but I have mostly small-memory boxes. I may be wrong, but I think that only the needed modules are actually loaded. I think this is correct, only the needed modules are actually loaded into the kernel. The initrd makes the *available* for loading. And when / pivots, I think the initrd memory gets freed. So its really only an issue during the initial bootstrap. A really large initrd on a memory-bound machine could get in the way. A really large initrd on an I/O bound machine can take a long time to load in. But, IMO, for general purpose machines, its not a big deal. As for xorg-video-foo, that's why I don't install the xorg metapackage. I choose from its dependencies what I need. Same here All these extra packages together take a lot of disk space, a lot of download bandwidth to install and maintain. yeah, the extra packages definitely are an issue. I'm not so sure tht the extra kernel modules are all that big a deal in the long run. but that's just a gut feeling. /rant There's a growing kitchen-sink approach in Debian (perhaps all of Linux, I don't know). There's the kernel/initrd size, there's the variable device name problems, to name two. It suggests to me that there's a missing piece of infrastructure. Perhaps the installer system should create a hardware inventory file that initrdtools (or whatever the nom de jure) can access to generate a tailord initrd, that apt can consult for what drivers to download, etc. The installer rescue mode could offer a tool to regenerate the inventory file for times when one changes hardware. /end rant True, but you have to consider the competition. I guess the problem is related to this notion of trying to compete with MS. If people 'buy' brand A because they like features x,y, and z, and brand B has the goal of gaining market share, it will tend to morph into a clone (feature-wise) of brand A. However, it will tend to take on some of the compromises of brand B that go with features x, y, and z. I think that on the whole, debian strikes a decent balance. You get the kitchen sink, but have the option to switch over to a bare pipe sticking out of the wall for no charge other than your own labor. :) A signature.asc Description: Digital signature
Large initrd [Was: Re: booting problem (udev related?)]
On Wed, Aug 01, 2007 at 11:10:25PM -0600, Bob Proulx wrote: Miles Bader wrote: Hmm, I didn't realize it analyzed the system when building the ramfs contents. Maybe I could just reinstall the kernel while the new kernel is running (or is there an official hint mechanism I could use)? Yes. Please try that. [I thought it just included _every_ possible module on the ramfs -- judging from the enormous size of the installed kernel package, it seems like it!] :-) Yes, I know what you mean. I was using yaird to make my initrd, but it gave some errors on the latest upgrade (and Steve Langasek, Debian kernel maintainer suggested it is no longer maintained). So now I'm exploring the initramfs-tools package. The first initrd was about *5 (five)* times bigger! I changed the config for including modules from 'most' to 'dep' and I got a much smaller (but still a bit bigger then yaird) initrd. Haven't tried to boot with it yet, though ;) Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Large initrd [Was: Re: booting problem (udev related?)]
On Thu, Aug 02, 2007 at 18:23:04 +0300, Andrei Popescu wrote: [...] Yes, I know what you mean. I was using yaird to make my initrd, but it gave some errors on the latest upgrade (and Steve Langasek, Debian kernel maintainer suggested it is no longer maintained). Do you mean this problem? yaird error: unrecognised line in /proc/bus/input/devices: U: Uniq= (fatal) That can be fixed relatively easily, see bug #431534, followup 1. (/usr/lib/yaird/perl/InputTab.pm is patched to simply ignore these new lines in /proc/bus/input/devices.) -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Large initrd [Was: Re: booting problem (udev related?)]
On Thu, Aug 02, 2007 at 06:23:04PM +0300, Andrei Popescu wrote: On Wed, Aug 01, 2007 at 11:10:25PM -0600, Bob Proulx wrote: Miles Bader wrote: Hmm, I didn't realize it analyzed the system when building the ramfs contents. Maybe I could just reinstall the kernel while the new kernel is running (or is there an official hint mechanism I could use)? Yes. Please try that. [I thought it just included _every_ possible module on the ramfs -- judging from the enormous size of the installed kernel package, it seems like it!] :-) Yes, I know what you mean. I was using yaird to make my initrd, but it gave some errors on the latest upgrade (and Steve Langasek, Debian kernel maintainer suggested it is no longer maintained). So now I'm exploring the initramfs-tools package. The first initrd was about *5 (five)* times bigger! wow! I never noticed that. And in fact I probably wouldn't have as this system doesn't have any initrd's left from yaird. My server which was an etch/testing box for a while has a couple older initrd's that are 1.4 megs or so versus the newer ones at 5-6megs. yikes. I changed the config for including modules from 'most' to 'dep' and I got a much smaller (but still a bit bigger then yaird) initrd. Haven't tried to boot with it yet, though ;) same here. interesting. I'll have to play with that. You could probably tighten it up even more by using the 'list' option and putting a minimum-necessary list in /etc/initramfs-tools/modules. At least that's how I read it. So what is the significance of initrd size? (other than the obvious filling up /boot issue). Is it really a problem to have most modules in there? I can think of some situations where it might be nice to have most of them -- mobo fails catastrophically and you want to be able to just boot, for example. Finally, I have on this (sid) system both initrd-tools and initramfs-tools installed. The latter is brought in by the kernel dependencies, and the former is manually installed. Who knows why or when I did that, but is one preferred over the other? A signature.asc Description: Digital signature
Re: Large initrd [Was: Re: booting problem (udev related?)]
On Thu, Aug 02, 2007 at 10:35:01AM -0700, Andrew Sackville-West wrote: same here. interesting. I'll have to play with that. You could probably tighten it up even more by using the 'list' option and putting a minimum-necessary list in /etc/initramfs-tools/modules. At least that's how I read it. That's too much hacking for my taste. So what is the significance of initrd size? (other than the obvious filling up /boot issue). Is it really a problem to have most modules in there? I can think of some situations where it might be nice to have most of them -- mobo fails catastrophically and you want to be able to just boot, for example. This is about it. Debian wants to provide an initrd that works even ehn changing hardware. Same reason for installing all -xorg-video-foo packages. Finally, I have on this (sid) system both initrd-tools and initramfs-tools installed. The latter is brought in by the kernel dependencies, and the former is manually installed. Who knows why or when I did that, but is one preferred over the other? AFAIU initrd-tools are deprecated and should not be used: http://wiki.debian.org/InitrdReplacementOptions There is also a nice comparison of initramfs-tools vs. yaird, though I'm not sure how recent this is. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Large initrd [Was: Re: booting problem (udev related?)]
On Thu, Aug 02, 2007 at 06:40:52PM +0200, Florian Kulzer wrote: On Thu, Aug 02, 2007 at 18:23:04 +0300, Andrei Popescu wrote: [...] Yes, I know what you mean. I was using yaird to make my initrd, but it gave some errors on the latest upgrade (and Steve Langasek, Debian kernel maintainer suggested it is no longer maintained). Do you mean this problem? yaird error: unrecognised line in /proc/bus/input/devices: U: Uniq= (fatal) That can be fixed relatively easily, see bug #431534, followup 1. (/usr/lib/yaird/perl/InputTab.pm is patched to simply ignore these new lines in /proc/bus/input/devices.) Sure I could do this (actually I found another workaround, see #435560), but that's not the point. And I'm (by far) not knowledgeable enough to take over. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: Large initrd [Was: Re: booting problem (udev related?)]
On Fri, Aug 03, 2007 at 12:19:36AM +0300, Andrei Popescu wrote: On Thu, Aug 02, 2007 at 10:35:01AM -0700, Andrew Sackville-West wrote: So what is the significance of initrd size? (other than the obvious filling up /boot issue). Is it really a problem to have most modules in there? I can think of some situations where it might be nice to have most of them -- mobo fails catastrophically and you want to be able to just boot, for example. This is about it. Debian wants to provide an initrd that works even ehn changing hardware. Same reason for installing all -xorg-video-foo packages. However, don't all those modules in the initrd end up staying in the kernel anyway, or do they get unloaded during boot? If they stay, and 'most' modules get added, how is that different than having a huge monolithic kernel? It may not matter on a box with huge memory, but I have mostly small-memory boxes. As for xorg-video-foo, that's why I don't install the xorg metapackage. I choose from its dependencies what I need. /rant There's a growing kitchen-sink approach in Debian (perhaps all of Linux, I don't know). There's the kernel/initrd size, there's the variable device name problems, to name two. It suggests to me that there's a missing piece of infrastructure. Perhaps the installer system should create a hardware inventory file that initrdtools (or whatever the nom de jure) can access to generate a tailord initrd, that apt can consult for what drivers to download, etc. The installer rescue mode could offer a tool to regenerate the inventory file for times when one changes hardware. /end rant Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
booting problem (udev related?)
For a long time, I used self-compiled kernels, with no problems. Recently I installed a debian kernel package, linux-image-2.6.22-1-686 (version 2.6.22-3). [It was a tight fit -- my root partition only has 130MB on it, and the debian kernel package used up 60MB -- but it did fit with about 4MB to spare!] The problem is that with the new kernel, the system won't boot all the way. It fails when it tries to mount the root partition, and dumps me into the ramfs emergency shell. The error message is something generic like File not found (sorry for the vagueness, those boot messages don't get saved anywhere and I didn't write them down). I seems like it may be related to udev because if I look in /dev, the disk device nodes which should be there _aren't there_, even though the disk hardware is recognized fine by the kernel. Indeed, I can fix things enough in the emergency shell to get the boot to succeed; I just use the following commands: mknod /dev/sda1 b 8 1 mount -text2 /dev/sda1 /root Then I hit ^D to the shell prompt to exit the shell, and the boot continues sucessfully (I'm typing in that running system now)! So it appears that for some reason, udev didn't create the appropriate /dev/sda1 node for the root to be mounted?!? Oddly, once booting continues, everything works fine, including mounting of my /usr partition from /dev/sda3 (notice that I didn't create /dev/sda3 above, and it certainly wasn't there initially). [I know my raw /dev directory has an entry for /dev/sda3 from before udev existed; does udev notice that and somehow copy it?] With my old self-compiled kernels, I have no problems, using exactly the same system. Those kernels though, have compiled-in drivers for all my devices, and don't use initramfs (or initrd) at all, so perhaps it's a module-loading issue? The last self-compiled kernel I used was version 2.6.19.7 btw. Does anybody have any idea what's going on, and how I might try to fix it? BTW, my system uses a SCSI disk with an old Adaptec SCSI card, if that's relevant... here's some related msgs from dmsg: SCSI subsystem initialized ... scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 Adaptec 2940 Ultra SCSI adapter aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs ... scsi 0:0:5:0: Direct-Access SEAGATE ST34555N 0930 PQ: 0 ANSI: 2 target0:0:5: Beginning Domain Validation target0:0:5: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15) target0:0:5: Domain Validation skipping write tests target0:0:5: Ending Domain Validation sd 0:0:5:0: [sda] 924 512-byte hardware sectors (4551 MB) sd 0:0:5:0: [sda] Write Protect is off sd 0:0:5:0: [sda] Mode Sense: 93 00 10 08 sd 0:0:5:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sd 0:0:5:0: [sda] 924 512-byte hardware sectors (4551 MB) sd 0:0:5:0: [sda] Write Protect is off sd 0:0:5:0: [sda] Mode Sense: 93 00 10 08 sd 0:0:5:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA sda: sda1 sda2 sda3 sd 0:0:5:0: [sda] Attached SCSI disk Thanks greatly, -Miles -- If you can't beat them, arrange to have them beaten. [George Carlin] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: booting problem (udev related?)
Miles Bader wrote: The problem is that with the new kernel, the system won't boot all the way. It fails when it tries to mount the root partition, and dumps me into the ramfs emergency shell. The error message is something generic like File not found (sorry for the vagueness, those boot messages don't get saved anywhere and I didn't write them down). This sounds to me as if the initrd did not load the device drivers, as you suggested later in your message. Look in the /boot/grub/menu.lst file and verify that the initrd is being loaded. Check that you have current versions of 'module-init-tools' and 'initramfs-tools' packages. The 'mkinitramfs' command is what builds the initrd.img file. I think the problem is your clue that previously you had compiled into your kernel your required modules. This may be making it difficult for mkinitramfs to determine which modules are required. If it fails to detect this it would build an incorrect initrd.img and have similar results to what you are reporting. You may need to hint to it a module to help bootstrap the system along. BTW, my system uses a SCSI disk with an old Adaptec SCSI card scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 Adaptec 2940 Ultra SCSI adapter That was a great card. I have one too but it is no longer in use. I miss SCSI. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: booting problem (udev related?)
[EMAIL PROTECTED] (Bob Proulx) writes: I think the problem is your clue that previously you had compiled into your kernel your required modules. This may be making it difficult for mkinitramfs to determine which modules are required. If it fails to detect this it would build an incorrect initrd.img and have similar results to what you are reporting. You may need to hint to it a module to help bootstrap the system along. Hmm, I didn't realize it analyzed the system when building the ramfs contents. Maybe I could just reinstall the kernel while the new kernel is running (or is there an official hint mechanism I could use)? [I thought it just included _every_ possible module on the ramfs -- judging from the enormous size of the installed kernel package, it seems like it!] BTW, my system uses a SCSI disk with an old Adaptec SCSI card scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 Adaptec 2940 Ultra SCSI adapter That was a great card. I have one too but it is no longer in use. I miss SCSI. Yeah this system gives me the warm fuzzies, despite the very small disk size; I guess next system will be SATA though, it's just too hard to justify anything else... :-/ Thanks, -Miles -- My spirit felt washed. With blood. [Eli Shin, on The Passion of the Christ] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: booting problem (udev related?)
On Thu, Aug 02, 2007 at 08:50:08AM +0900, Miles Bader wrote: I seems like it may be related to udev because if I look in /dev, the disk device nodes which should be there _aren't there_, even though the disk hardware is recognized fine by the kernel. Udev isn't running yet. The boot devices/modules are loaded in the initramfs. I've never compiled a kernel so I haven't had to fitz with initramfs. Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: booting problem (udev related?)
Miles Bader wrote: Hmm, I didn't realize it analyzed the system when building the ramfs contents. Maybe I could just reinstall the kernel while the new kernel is running (or is there an official hint mechanism I could use)? Yes. Please try that. [I thought it just included _every_ possible module on the ramfs -- judging from the enormous size of the installed kernel package, it seems like it!] :-) Yeah this system gives me the warm fuzzies, despite the very small disk size; I guess next system will be SATA though, it's just too hard to justify anything else... :-/ Yep. I have given into the dark side too. They have cookies. Bob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Loadlin Booting Problem
Hi Paul, On Thu, Aug 11, 2005 at 04:05:22AM -0700, Paul Kranz wrote: I would like help getting Loadlin to work with Linux 3.0 r6 which is using kernel 2.4.18-bf2.4 and Windows 98. Loadlin boots the vanilla version of the kernel 2.2.20 as expected, however it seems to have a problem uncompressing kernel 2.4.18-bf2.4 and displays the following messages at bootup. unocmpressing linux . invalid compression format (err=2) --- system haulted The 2.4.18-bf2.4 kernel boots fine from the boot floppy. I'm using the Loadlin instructions in Chris Fischer's Loadlin + Win 95/98/ME mini-HOWTO. The debian-boot mailing list is a list for discussing the development of the Debian installer. The list you want for this sort of question is debian-user. FWIW, it might be advisable to grab a copy of Debian 3.1 instead, as 3.0r6 is no longer the current stable release. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I will move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Booting Problem SATA large disk
Hi: I am running unstable Debian with Linux 2.6.6. kernel. My computer is a Gateway computer with a large (160GB) disk with SATA controller. I have Windows XP on hda1, and linux on hda2, with partitions hda3,5,6 etc for home, usr, var, etc. I had problems installing Linux on the hard drive because of the SATA drive. Knoppix seemed to boot up, and with the help of that I managed to install 2.6.0-test9 kernel. The Hard drive seemed to be changed to sdb, with Linux on the sdb2 partition. The 750 MB Iomega zip was recognized as sda. The dvd rom was recognized as sr0. I changed the /etc/fstab to these values and managed to make a bootdisk with syslinux; I do not remember precisely what I did, but I presume I used Knoppid. It boots up only when I do not give any parameters at the boot prompt. If I attempt to give root=/dev/sdb2, it goes into kernel panic. This is able to boot up, but I am unable to dual-boot from Windows: it just hangs. I recently thought I would install the 2.6.6. kernel. They recommend that the cd use hte ide-cd rather than the scsi and I built the kernel accordingly. I used syslinux to make a boot disk, but this goes into kernel panic, wanting a valid root= paramter. No parameter seems to work. I have tried, lilo and grub and all of them do the same thing. I presume this has something to do with the fact that to the bios the disk is hda, and when the scsi SATA is used in 2.6.6 this is changed. Any suggestions as to how to proceed will be appreciated. Thanks. Sebastian Canagaratna Department of Chemistry Ohio Northern University Ada, OH 45810 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: booting problem with tpconfig after removing it
On Sat, Jan 24, 2004 at 07:03:05PM +0100, Jan Ulrich Hasecke wrote: I encountered a strange problem today. Suddenly my notebook stops booting after starting klogd. I am running 2.6.1 and unstable. After booting into single user mode I tried to manually start everything in rc2.d via /etc/init.d xyz start and discovered that /etc/init.d/tpconfig hangs. In the shell I could kill it with Ctrl-C, but during boot up there was no chance to kill it. Hi, Jan (heh! :-) You haven't file a bugreport, have you? Please do ``reportbug tpconfig''. Jan. -- Jan Minar Please don't CC me, I'm subscribed. x 9 pgp0.pgp Description: PGP signature
booting problem with tpconfig after removing it
Hi, I encountered a strange problem today. Suddenly my notebook stops booting after starting klogd. I am running 2.6.1 and unstable. After booting into single user mode I tried to manually start everything in rc2.d via /etc/init.d xyz start and discovered that /etc/init.d/tpconfig hangs. In the shell I could kill it with Ctrl-C, but during boot up there was no chance to kill it. Maybe it is because the tpconfig package was removed. I don't know. So if anybody encountered the same problem. Just remove the links from /etc or purge the package. juh -- Die Schröder-Dummies Der Autokanzler hat verstanden. http://www.sudelbuch.de/2002/20021001.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need to resolve booting problem
On Tue, Nov 11, 2003 at 10:57:34AM -0600, Ron Johnson wrote: On Mon, 2003-11-10 at 14:58, Joachim Fahnenmueller wrote: On Mon, Nov 10, 2003 at 09:48:17AM -0500, Parfait BINI wrote: Good morning Sir, My name's Parfait BINI, I got a boot problem with my computer. [snip] Parfait BINI Remove all that Windoze stuff and install Debian. [Or what sort of answer did you expect from this list?] Could all these guys asking Windows questions really be trolls, seeing how we react? I think they are for _sure_. And people insist on feeding them. You can tell when a Windows user has a serious question because it won't be _that_ moronic. The really moronic ones are trolls and should be ignored, no matter how tempting. A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need to resolve booting problem
On Mon, Nov 10, 2003 at 09:48:17AM -0500, Parfait BINI wrote: Good morning Sir, My name's Parfait BINI, I got a boot problem with my computer. I had a new RAM for playing Playstation games,when I start by Win98 iI don't have no problem but when I start by WindowsXP it shows me an error of imcompatibility. I've remove this RAM and since this day ,I no more use my slot extension and I can start my computer with my Sound card and network card. Please give INformation to resolve that. Hoping to hear from you soon.Thanks. Parfait BINI Remove all that Windoze stuff and install Debian. [Or what sort of answer did you expect from this list?] HTH [?] -- Joachim Fahnenmüller # Hi! I'm a .signature virus. Copy me into # your ~/.signature to help me spread! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need to resolve booting problem
On Mon, 2003-11-10 at 14:58, Joachim Fahnenmueller wrote: On Mon, Nov 10, 2003 at 09:48:17AM -0500, Parfait BINI wrote: Good morning Sir, My name's Parfait BINI, I got a boot problem with my computer. [snip] Parfait BINI Remove all that Windoze stuff and install Debian. [Or what sort of answer did you expect from this list?] Could all these guys asking Windows questions really be trolls, seeing how we react? -- - Ron Johnson, Jr. [EMAIL PROTECTED] Jefferson, LA USA Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. Brian W. Kernighan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need to resolve booting problem
On Tue, 11 Nov 2003 10:57:34 -0600, Ron Johnson [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]: On Mon, 2003-11-10 at 14:58, Joachim Fahnenmueller wrote: On Mon, Nov 10, 2003 at 09:48:17AM -0500, Parfait BINI wrote: Good morning Sir, My name's Parfait BINI, I got a boot problem with my computer. [snip] Parfait BINI Remove all that Windoze stuff and install Debian. [Or what sort of answer did you expect from this list?] Could all these guys asking Windows questions really be trolls, seeing how we react? ..benefit of doubt can't hurt for the first timers. ;-) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need to resolve booting problem
On Tue, Nov 11, 2003 at 07:01:32PM +, Jess Anderson wrote: But isn't this group moderated No, it's not. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need to resolve booting problem
On Tue, Nov 11, 2003 at 10:57:34AM -0600, Ron Johnson wrote: On Mon, 2003-11-10 at 14:58, Joachim Fahnenmueller wrote: On Mon, Nov 10, 2003 at 09:48:17AM -0500, Parfait BINI wrote: Good morning Sir, My name's Parfait BINI, I got a boot problem with my computer. [snip] Parfait BINI Remove all that Windoze stuff and install Debian. [Or what sort of answer did you expect from this list?] Could all these guys asking Windows questions really be trolls, seeing how we react? Hmm... they never ever respond, either on list or off... I CCed one of them once, asking quite politely what they thought debian-user was and why they thought we should know if AOL had their credit card details. Didn't get a response! -- Pigeon Be kind to pigeons Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F pgp0.pgp Description: PGP signature
Need to resolve booting problem
Good morning Sir, My name's Parfait BINI, I got a boot problem with my computer. I had a new RAM for playing Playstation games,when I start by Win98 iI don't have no problem but when I start by WindowsXP it shows me an error of imcompatibility. I've remove this RAM and since this day ,I no more use my slot extension and I can start my computer with my Sound card and network card. Please give INformation to resolve that. Hoping to hear from you soon.Thanks. Parfait BINILèche-vitrine ou lèche-écran ? Yahoo! Magasinage.
Re: Need to resolve booting problem
On Mon, 10 Nov 2003 09:48:17 -0500 (EST) Parfait BINI [EMAIL PROTECTED] wrote: Good morning Sir, My name's Parfait BINI, I got a boot problem with my computer. I had a new RAM for playing Playstation games,when I start by Win98 iI don't have no problem but when I start by WindowsXP it shows me an error of imcompatibility. I've remove this RAM and since this day ,I no more use my slot extension and I can start my computer with my Sound card and network card. Please give INformation to resolve that. Hoping to hear from you soon.Thanks. Parfait BINI Hello Parfait, It has been a long time since I did anything with a Microsoft distribution, but I believe from memory that XP takes a reading of your system at registration time, and then refuses any further additions to that system, yes, even unto a RAM upgrade. I believe that they implemented this so that it would make it difficult to put XP onto more than one system. There was a big stink about the level of arrogance involved in dictating how people were permitted to employ their own property from memory, and I think if you ring the operator on the number provided on your install CD that they are able to make some configuration change which will permit you to use new hardware upgrades that you have purchased for use on your own machine in conjunction with the operating system that you have also purchased. But other than that, I don't have any advice to offer. Perhaps you might like to try Debian? Debian isn't arrogant at all. To start off with Debian I personally would advise using Knoppix or Libranet. If you search for either of those two terms with Google you will achieve the kind of result that left windose behind for me some time ago. I will never go back. Regards, David. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Need to resolve booting problem
David Palmer. wrote: Perhaps you might like to try Debian? Debian isn't arrogant at all. ROTFL!!! (Okay, out of context, but still, that was funny!) :-) -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel-image-2.4.1-di booting problem....
Gong Yi LIAO wrote: I had apt-get install kernel-image-2.4.1-di several hour ago, Why did you do that? Package: kernel-image-2.4.1-di Description: Linux kernel binary image for the Debian installer This package contains the Linux kernel image version 2.4.1-di, for the experimental Debian installer project. This kernel is very modular, and will only work on Debian systems that boot into an initrd. Note that debian does not yet use an initrd, so this is rather unlikely to work on your system yet. How should I do for booting the kernel image 2.4.1-di correctly ? I hope you have lilo configured to let you boot your old kernel, or have a rescue CD or floppy. Herbert, I see you're beginning to work on some initrd stuff. Is there a package I can make kernel-image-di depend on that sets up an inird? -- see shy jo
Kernel-image-2.4.1-di booting problem....
Hi ,gurus I had apt-get install kernel-image-2.4.1-di several hour ago, and I tried to boot the kernel from hda on my machine(x86) ,but I got trouble while the kernel mount root file system , the error: VFS:error ,can not find root file system ,or: I can not get root I want to scream How should I do for booting the kernel image 2.4.1-di correctly ? Thanx!!!
Re: Booting problem
on Fri, Jan 12, 2001 at 07:37:29PM +0100, Bolem?nyi Attila ([EMAIL PROTECTED]) wrote: HI! I have an Abit BE6-II motherboard with HPT370UDMA/ATA 100 raid cintroller. When I try to install the Potato, I have a message, so I have not a hard disk. How can I install the Potato to my computer? I just found a HPT366 floppy images. Please post the exact error message(s) and where in the boot process they occur. You may wish to find a support list in a familiar language -- your English is not very clear. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgpisZqMo3Cwc.pgp Description: PGP signature
Booting problem
HI! I have an Abit BE6-II motherboard with HPT370UDMA/ATA 100 raid cintroller. When I try to install the Potato, I have a message, so I have not a hard disk. How can I install the Potato to my computer? I just found a HPT366 floppy images. Attila
Re: Booting problem with AMD Athlon
Alain Birtz [EMAIL PROTECTED] writes: I recently bought Debian 2.1 and I tried to install it on my brand new PC. However I was not capable to make it to the installer. When I start from the CD-ROM, I see the boot: prompt, I hit return and then it starts loading stuff, like a normal boot does. However, when it arrives at the line NCR53c406a: no available ports found it hangs there. The cursors waits at the beginning of the next line. Generally, it is the *next* message (the one that doesn't appear) which is the trouble-maker. Some people told me that, because of my Athlon processor, I should try boot floppies with potato. True. I made the floppies and was able to boot from the rescue floppy. It asked me for the root disk and I put it in. It loads the the ramdisk, free some memory, then freezes. here is the log: VFS: Insert root floppy disk to be loaded into RAM disk and press ENTER RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 140k freed _ hangs here Very strange! Here is the list of my hardware: AMD Athlon 550 Mgz 1 IDE hard-disk: 13 gig 128 meg of RAM Nothing SCSI FUJITSU motherboard (AMI BIOS ) Sceptre Monitor 17 inch (VGA comptible) S3 Trio3D/2X cheap graphic card Ethernet card: StarTech Do you have any idea of what could be wrong? Not offhand. We will be uploading a new potato boot-floppies (2.2.5) soon, which is 2.2.14 based. Maybe that will fare better. If not, we'll file a bug against the kernel, that is, file a bug against kernel-image-2.2.14. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/
Booting problem with AMD Athlon
Hi, I recently bought Debian 2.1 and I tried to install it on my brand new PC. However I was not capable to make it to the installer. When I start from the CD-ROM, I see the boot: prompt, I hit return and then it starts loading stuff, like a normal boot does. However, when it arrives at the line NCR53c406a: no available ports found it hangs there. The cursors waits at the beginning of the next line. Here is my transcription of the log: ... VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hda:DMA, hdb:pio hda: JUBITSU MPE3136AT, ATA DISK drive hdc: ATAPI CD-ROM DRIVER 40X MAXIMUM, ATAPI CDROM drive ide0 at 0x1f0-0x1f7, 0x3f6 on irq 14 ide1 at 0x170-0x177, 0x376 on irq 15 hda: FUJITSU MPE3136AT, 13031MB w/512kB Cache, CHS=1661/255/63 hdc: ATAPI 40X CD-ROM drive, 128 kB Cache Uniform CDROM driver Revision: 2.55 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 NCR53c406a: no available ports found _ (hangs here) I looked in the Learning Debian book for boot arguments, and I found NCR53c406a corresponded to NCR 53c406a-based SCSI host adapters: I have NO SCSI device on my computer, I only have an IDE HD. Therefore I find rather normal that it cannot find 'ports' for it since there are none. I tried using max-scsi-luns=0 (and =1) arguments to prevent it to scan for SCSI device...it still hangs at the same point. I tried using ncr53c406a=0 to disable interrupts and it didn't work too I also tried disabling several BIOS options that could have lead to trouble...no luck. But, when I gave boot arg pci=off, I got 2 extra lines before hangs: NCR53c406a: no available ports found eata_dma: No BIOS32 extensions present. This driver release still depends on it. o Skipping can for PCI HBAs. hangs> Some people told me that, because of my Athlon processor, I should try boot floppies with potato. I made the floppies and was able to boot from the rescue floppy. It asked me for the root disk and I put it in. It loads the the ramdisk, free some memory, then freezes. here is the log: VFS: Insert root floppy disk to be loaded into RAM disk and press ENTER RAMDISK: Compressed image found at block 0 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 140k freed _ hangs here> Here is the list of my hardware: AMD Athlon 550 Mgz 1 IDE hard-disk: 13 gig 128 meg of RAM Nothing SCSI FUJITSU motherboard (AMI BIOS ) Sceptre Monitor 17 inch (VGA comptible) S3 Trio3D/2X cheap graphic card Ethernet card: StarTech Do you have any idea of what could be wrong? Thanks, -Laurent Birtz [EMAIL PROTECTED]> Alain Birtz Qc, Canada Internet: [EMAIL PROTECTED], [EMAIL PROTECTED]
Re: Booting problem with AMD Athlon
99% chance i the kernel on the Cd is not compadible with athlon, you need to make your own boot disk, or, if possible it would be easier to install on a non athlon, upgrade the kernel then move the HD back to the athlon. you need linux 2.2.13 to boot on athlon.(or newer) nate On Fri, 21 Jan 2000, Alain Birtz wrote: abz Hi, abz abz abz I recently bought Debian 2.1 and I tried to install it on my brand new abz PC. abz abz However I was not capable to make it to the installer. abz abz abz When I start from the CD-ROM, I see the boot: prompt, I hit return and abz then it starts loading stuff, like a normal boot does. However, when abz it arrives at the line abz abz NCR53c406a: no available ports found abz abz it hangs there. abz abz The cursors waits at the beginning of the next line. abz abz abz Here is my transcription of the log: abz abz ... abz abz VP_IDE: IDE controller on PCI bus 00 dev 39 abz abz VP_IDE: not 100% native mode: will probe irqs later abz abzide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:pio abz abzide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hda:DMA, hdb:pio abz abz hda: JUBITSU MPE3136AT, ATA DISK drive abz abz hdc: ATAPI CD-ROM DRIVER 40X MAXIMUM, ATAPI CDROM drive abz abz ide0 at 0x1f0-0x1f7, 0x3f6 on irq 14 abz abz ide1 at 0x170-0x177, 0x376 on irq 15 abz abz hda: FUJITSU MPE3136AT, 13031MB w/512kB Cache, CHS=1661/255/63 abz abz hdc: ATAPI 40X CD-ROM drive, 128 kB Cache abz abz Uniform CDROM driver Revision: 2.55 abz abz Floppy drive(s): fd0 is 1.44M abz abz FDC 0 is a post-1991 82077 abz abz md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 abz abz NCR53c406a: no available ports found abz abz _ (hangs here) abz abz abz abz I looked in the Learning Debian book for boot arguments, and I found abz NCR53c406a corresponded to NCR 53c406a-based SCSI host adapters: abz abz abz I have NO SCSI device on my computer, I only have an IDE HD. Therefore abz I find rather normal that it cannot find 'ports' for it since there are abz none. abz abz abz I tried using max-scsi-luns=0 (and =1) arguments to prevent it to scan abz for SCSI device...it still hangs at the same point. abz abz abz I tried using ncr53c406a=0 to disable interrupts and it didn't work abz too abz abz abz I also tried disabling several BIOS options that could have lead to abz trouble...no luck. abz abz abz But, when I gave boot arg pci=off, I got 2 extra lines before hangs: abz abz abz NCR53c406a: no available ports found abz abz eata_dma: No BIOS32 extensions present. This driver release still abz depends on it. abz abz o Skipping can for PCI HBAs. abz abz hangs abz abz abz Some people told me that, because of my Athlon processor, I should try abz boot floppies with potato. abz abz abz I made the floppies and was able to boot from the rescue floppy. It abz asked me for the root disk and I put it in. abz abz abz It loads the the ramdisk, free some memory, then freezes. abz abz abz here is the log: abz abz VFS: Insert root floppy disk to be loaded into RAM disk and press abz ENTER abz abz RAMDISK: Compressed image found at block 0 abz abz VFS: Mounted root (ext2 filesystem) readonly. abz abz Freeing unused kernel memory: 140k freed abz abz _ hangs here abz abz abz Here is the list of my hardware: abz abz AMD Athlon 550 Mgz abz abz 1 IDE hard-disk: 13 gig abz abz 128 meg of RAM abz abz Nothing SCSI abz abz FUJITSU motherboard (AMI BIOS ) abz abz Sceptre Monitor 17 inch (VGA comptible) abz abz S3 Trio3D/2X cheap graphic card abz abz Ethernet card: StarTech abz abz abz Do you have any idea of what could be wrong? abz abz abz Thanks, abz abz -Laurent Birtz abz abz abz [EMAIL PROTECTED] abz abz Alain Birtz abz abz Qc, Canada abz abz Internet: [EMAIL PROTECTED], [EMAIL PROTECTED] abz abz abz abz -- abz Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null abz [mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- 1:17pm up 155 days, 1:22, 2 users, load average: 1.51, 1.62, 1.62
Re: Booting problem with AMD Athlon
On Fri, Jan 21, 2000 at 03:51:35PM -0500, Alain Birtz wrote: Hi, I recently bought Debian 2.1 and I tried to install it on my brand new PC. However I was not capable to make it to the installer. When I start from the CD-ROM, I see the boot: prompt, I hit return and then it starts loading stuff, like a normal boot does. However, when it arrives at the line NCR53c406a: no available ports found it hangs there. The cursors waits at the beginning of the next line. 1) on an msi mainboard i found the fllowing worked well i found that by turning off UDMA and forcing the hard drives to mode 0 during the install it made it thru and i was able to download a 2.2.14 kernel and compile it. i then turned all the ide stuff back to normal and it went thru fine. 2) on an asus mother i couldnt find any way to get thru it without the md driver freezing. i placed the hard drive on another motherboard, did the install, put the 2.2.14 kernel on the mother, and away it went. hope it helps -- Best Regards Dave --- Closer To Home Systems * Shop 6, 44 King Street * Caboolture, Qld, 4510 Ph 07 5499 3000 * Fax 07 5499 1822 * Mob 0416 173 522 * [EMAIL PROTECTED] ICQ 1955906 * We Specialise in Computing Solutions and Personal Support New Systems * Upgrades * Repairs * Small Business Networking * Software ---
Debian 2.0 booting problem
Hi, I installed debian 2.0 on pc there is the strange problem: Sometimes it boots up well. I have installed only the base system and netwoking code (NIS and Automount) Sometimes the boot process hangs with the following error message: qlogicisp: PCI bios not present eata_dma : No BIOS32 extensions present. This driver still depends on it 0 Skipping scan for PCI HBAs eata_pio: No BIOS32 extensions present. This driver still depends on it 0 Skipping scan for PCI HBAs When the machine boots up properly, the above stage does not occur. I dont doubt the cdrom as I used the same to install debian on another machine. This is my second debian install and I have no idea what to do. Any comments are welcome Suresh Suresh Kumar.R Lecturer Dept of Electronics Communication College of Engineering Trivandrum - 695 016 INDIA Email: [EMAIL PROTECTED]
Re: Debian 2.0 booting problem
On Wed, Nov 17, 1999 at 05:25:02PM +, Suresh Kumar.R wrote: Sometimes it boots up well. I have installed only the base system and netwoking code (NIS and Automount) Sometimes the boot process hangs with the following error message: qlogicisp: PCI bios not present eata_dma : No BIOS32 extensions present. This driver still depends on it 0 Skipping scan for PCI HBAs eata_pio: No BIOS32 extensions present. This driver still depends on it 0 Skipping scan for PCI HBAs When the machine boots up properly, the above stage does not occur. I dont I might ask for a stupidity, but how old is the battery of the cmos clock/ram ? JY -- Jean-Yves F. Barbier [EMAIL PROTECTED] The Macintosh is Xerox technology at its best.
Re: Debian 2.0 booting problem
I have been having the same problem... the system often hangs right before this process (not showing it), often so long that i get impatient and just power my system down and boot back up, it seems to only hang momentarily every other time i boot... I don't have any PCI slots (it's an old 486 DX2), so I suspect that is why... any way to disable all these PCI checks? and, as to JY's reply to Suresh's original post re: battery, I suspect the battery for this system is pretty old. I got it second hand, but considering that it's a 486, i'd have to assume. Thanks for help, Nick -- Original Message - From: Suresh Kumar.R [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Wednesday, November 17, 1999 11:25 AM Subject: Debian 2.0 booting problem Hi, I installed debian 2.0 on pc there is the strange problem: Sometimes it boots up well. I have installed only the base system and netwoking code (NIS and Automount) Sometimes the boot process hangs with the following error message: qlogicisp: PCI bios not present eata_dma : No BIOS32 extensions present. This driver still depends on it 0 Skipping scan for PCI HBAs eata_pio: No BIOS32 extensions present. This driver still depends on it 0 Skipping scan for PCI HBAs When the machine boots up properly, the above stage does not occur. I dont doubt the cdrom as I used the same to install debian on another machine. This is my second debian install and I have no idea what to do. Any comments are welcome Suresh Suresh Kumar.R Lecturer Dept of Electronics Communication College of Engineering Trivandrum - 695 016 INDIA Email: [EMAIL PROTECTED] -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Booting problem
I recently installed Debian from an official set, slowly the things get better. The last changes that I managed to do ( a whole adventure for a windows newcomer!) left me with even a connection to the internet through wvdial. My main problem is that I have very little memory (about 1.3 gig). Any way, after this last change, when I tried to boot again, I got a cycle of Lilo . and back to the reboot, never ending. So I put the floppy created during first installation, trying to fix the matter. But I don't think it is fixed. Now, I wanted to remove a bunch of things trying to clean a little and leave room for a more bare installation, but it does not remove much. Tells me that dpkg is not good. How do I re-install it? Even better, I would do a re-installation from scratch, getting a bare little one with may be some TeX, math utilities, gcc++, and web connection. But I have no idea how to do it. Please help, give detailed indications if possible, I am just now getting used to the UNIX environment, now learning to use emacs, but not sure yet. Thanks, Antonio.
lilo Booting problem..
G'day all, I have a machine running redhat that I am about to upgrade rebuild as a debian system. I have been having a problem booting and was wondering if I could find a solution to implement when I change to debian. There are only SCSI disks /dev/sda2 900833 735118 119175 86% / /dev/sdc18595876 5910768 2239306 73% /home/u3 /dev/sda1 100118 1459480354 15% /var/spool /dev/sdb1 598634 364658 203053 64% /home/www I am currently booting from the floppy as when it tries to boot from one of the HD's it locks up at LILO I see LI on the screen and it freezes (which as I understand it means that it failed to load the secondary boot record) Now the other weird thing is in an attempt to diagnose this problem I used fdisk and lilo to change all the partions to be non bootable and not have a LILO boot record but it still does the same thing even though there are no bootable partions and no partions with a LILO signature Then I made /dev/sda2 bootable again and still the same error!! I know the 9Gig disk might cause trouble but its not booting from it so it should be ok (is this correct?). Does anyone have any ideas on how to get it booting from a HD??? Thanks in advance for any help. ---Gareth
Booting Problem with Linux 2.0 from CHIP
We are trying to install Debian Linux 2.0 which we got from CHIP. After running through the installation and when the system should boot for the first time the following message occurs: Loading linux. Uncompressing Linux... Out of memory ...System halted (Our System has 48MB of memory) What might be the reason? [EMAIL PROTECTED]
Booting problem after install (Same as Tommas)
I 've installed debian on a p 166 with windows 95 on i split my HDD to make room for debian and i install lilo as it said in the installation menu.when i boot from my hdd win95 strart as default,when i press Tab to select i get 1FA: an the system waits.if i press down arrow or Tab again it displays 2FA: and then win95 boot my config of Hdd is :hda1 used by win95 :hda2 extented partition :hda3 primary partition for debian(flagged non bootable) :hda5 logical partition inside hda2 PS the floppy boot works fine __ Get Your Private, Free Email at http://www.hotmail.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
