Bug#397133: marked as done (boot problem after installation)
Your message dated Wed, 08 Sep 2010 03:58:20 + with message-id e1otbng-0005os...@ravel.debian.org and subject line Closing old installation report #397133 has caused the Debian Bug report #397133, regarding boot problem after installation to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 397133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: DVD Image version: from DVD1: Debian 3.1r3 Released 31 August 2006, kernel-image-2.4.27-2-386, purchased on november 2, 2006, from delinuxspecialist.nl Date: november 4, 2006 Machine: HP Compaq nx9110 Processor: Pentium 4 2.8GHz Memory: 704 MB Partitions: according to debian-installer: ide1 master (hda) - 40.0 GB HITACHI_DK23FA-40 #1 primary 5.2 GB ntfs #4 primary23.7 GB fat32 #2 primary10.6 GB ext3/ #5 logical 493.5 MB swapswap contents of /target/etc/fstab: proc/procproc defaults 0 0 /dev/hda2 /ext3 defaults,errors=remount-ro 0 1 /dev/hda5 none swap rw 0 0 /dev/hdc/media/cdrom0iso9660ro,user,noauto 0 0 Output of lspci and lspci -n: I am unable to run lspci Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [-] = didn't try it Initial boot worked:[E] Configure network HW: [-] Config network: [-] Detect CD: [0] Load installer modules: [0] Detect hard drives: [0] Partition hard drives: [0] Create file systems:[0] Mount partitions: [0] Install base system:[0] Install boot loader:[0] (grub) Reboot: [-] Comments/Problems: After installing base system, first boot into new system fails, messages: pivot_root: no such file or directory /sbin/init: 432 cannot open dev/console kernel panic: Attempted to kill init! boot commands from the grub menu: root (hd0,1) kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda2 ro initrd /boot/initrd.img-2.4.27-2-386 savedefault boot Dear N, I am having a boot problem during installation. Please see below for details. If you need other details or specifications please let me know. Any help will be greatly appreciated. Yours, Igor Hoveijn Problem: Unable to boot into system after installation of base system Error message: kernel panic: Attempted to kill init! History: Initial system with four partitions, first two windows partitions then two linux partitions containing other linux distribution. Obtained Debian linux on two DVD. Boot system from DVD1, deleted two linux partitons and used debian-installer to automatically partition the free space. Further with debian installation, no problems. After installation of grub the installer suggests to boot the new system for the first time, which results in a kernel panic. Searched the web for 'attempted to kill init' etc. Can't use the hints because I can't get to the file system. I don't have a rescue CD, didn't get the chance to make one. Had to copy the partition table from screen. Please see below for contents of /target/etc/fstab. Also /target/dev exists and /target/dev/console. At least just before I said OK to try the first boot. It seems that I'm stuck here. ---End Message--- ---BeginMessage--- We are closing this installation report for one of the following reasons: - it was reported with a pre-lenny version of Debian Installer. - indications in the installation report give the feeling that the reported problem waslying in another software, unrelated to D-I, which we can't easily identify. - indications in the installation report suggest that it may have been fixed in a more recent version of a D-I component - it was successful and we forgot closing it..:-) - it has no information we consider useful The D-I team is currently in the process of cleaning out the old spool of installation reports that haven't bene processed yet. In case you think that the problem you reported has chances to be still present, please reiterate your installation test with a more recent image of D-I, if you're in position of doing this. You'll find daily builds at http://www.debian.org/devel/debian-installer. We recommend you choose the netboot image, in the daily builds section, then choose to install squeeze when prompted. If some problems are found, please report them with a new bug sent against installation-reports. Many thanks for your understanding and your help improving
boot problem after installation - device names changed
my system is QNAP TS-409, which is armed platform
I have 3 disks and 2 partitions on each
When I start Debian Lenny installer based on instruction from
http://www.cyrius.com/debian/orion/qnap/ts-409/install.html my disks are
assigned to /dev/sd{a,b,c}.
I choose /dev/sda1 as /boot partition and /dev/sdb1 as swap.
On end of installation somepart of system are flashed to memory.
When I boot after successful installation it will not boot.
Unfortunately I don't see the UBoot output, but when I try boot with
rescue image or start installation again I see the the /dev/sda1 is swap
and not /boot, so the order of disks changed.
Is this change of disk order the problem why system is not booting ? Is
this normal behaviour ?
Sincerely,
Martin
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4bebf2a2.5000...@gmail.com
Re: boot problem after installation - device names changed
* Martin Minka martin.mi...@gmail.com [2010-05-13 14:37]: Unfortunately I don't see the UBoot output, but when I try boot with rescue image or start installation again I see the the /dev/sda1 is swap and not /boot, so the order of disks changed. Is this change of disk order the problem why system is not booting ? Is this normal behaviour ? It's documented in the errata for lenny. In squeeze, this has been fixed by the use of UUIDs to refer to partitions rather than fragile names like sdX than can change. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100513131658.gh17...@jirafa.cyrius.com
Re: boot problem after installation - device names changed
* Martin Minka martin.mi...@gmail.com [2010-05-13 15:27]: does it mean I should follow your installation instruction and choose expert mode installer and choose debian version squeeze ? Will that work ? No, the lenny installer won't do UUIDs. You have to use the squeeze installer: http://ftp.fr.debian.org/debian/dists/unstable/main/installer-armel/current/images/orion5x/netboot/qnap/ts-409/ -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100513133125.gi17...@jirafa.cyrius.com
Re: boot problem after installation - device names changed
Hello Martin, does it mean I should follow your installation instruction and choose expert mode installer and choose debian version squeeze ? Will that work ? Thank you for you repeating help. On 13. 5. 2010 15:16, Martin Michlmayr wrote: * Martin Minkamartin.mi...@gmail.com [2010-05-13 14:37]: Unfortunately I don't see the UBoot output, but when I try boot with rescue image or start installation again I see the the /dev/sda1 is swap and not /boot, so the order of disks changed. Is this change of disk order the problem why system is not booting ? Is this normal behaviour ? It's documented in the errata for lenny. In squeeze, this has been fixed by the use of UUIDs to refer to partitions rather than fragile names like sdX than can change. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bebfe25.8020...@gmail.com
Re: Boot problem in squeeze, hang after Booting the kernel
I tried the 2.6.30 kernel you suggested, now it tries to boot, but I get a kernel panik after trying to mount the root. I cannot make out too much but I have console output which I do not have with the regular 2.6.32 kernel. I suspect they hang at the same place though, with the difference of the output o the screen, ( only if using the debug flag ) ... I get some messages about popullating the foot fs, and vfs, after that whe I get to kernel init its game over. I cannot scroll backwards with shift-pageup ... in order to see what happens when it fail, and if I could get some output I could try to diagnose. Any ide´a on how to proceed ? The biggest problem seems to be that it panics when mounting the root fs. But if I could get console output from the 2.6.32 kernel I would know a bit more, I know the i945g graphics chip can be a bit picky Any ideas ? Should I open a bug report ? / regards, Lars Segerlund. 2010/2/14 Frans Pop elen...@planet.nl: On Friday 12 February 2010, Lars Segerlund wrote: I have a Sony Vaio TX3 ( VGN-TX3XT ) , which runs a on an intel celeron ULW, and has a i945g graphics chip. I have reinstalled with the squeeze install cd, but cannot boot the kernels on the machine. So the installer boots and works correctly, but the installed system fails to boot. As the installer uses a 2.6.30 kernel and the installed system gets a 2.6.32 kernel, it sounds like a kernel regression that affects your system. I can get into the machine from the rescue mode on the installer, ( if I chroot into the env. it looks fairly ok ). Try installing a 2.6.30 linux-image package. You can find one here: http://stabile.debian.org:5001/package/linux-2.6/2.6.30-8/ If that works, then please file a BR against the linux-2.6 package. You may also want to try if 2.6.31 works or not. You can find packages for that if you move up one directory level in the URL above. You should also try the very latest 2.6.32 packages from unstable to see if the problem has already been fixed there. I have tried noapic nolapic acpi=off no-hlt no-irq nomodeset and most options I can find to the kernel. I suspect it hangs partly into the linux init() function, and if i set vga=788 or vga=777 the text clears and I am greeted with a blank screen ... ( vga=788 is what the installer cd uses ). Make sure you also remove the 'quiet' option so you get all the boot messages on your console. That may give a better idea where the boot is failing. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/80d224fa1002151251r6a6097efgdf6c36e70585f...@mail.gmail.com
Re: Boot problem in squeeze, hang after Booting the kernel
Part of the problem found ! I can now get console ouptup from 2.6.32 in the same way as 2.6.30-8 ... the thing is that I found some bad RAM. However the last thing I see is unpacking initrd something After that it dies in the kernel, ( I have the debug flag on ) ... it ends up in the kernel_init something ... ( threads ? ) I have checked the initrd image and it actually looks fine... So , it's probably NOT a bug with the debian kernels ! Any suggestions on how to proceed appreciated ... 2010/2/15 Lars Segerlund lars.segerl...@gmail.com: I tried the 2.6.30 kernel you suggested, now it tries to boot, but I get a kernel panik after trying to mount the root. I cannot make out too much but I have console output which I do not have with the regular 2.6.32 kernel. I suspect they hang at the same place though, with the difference of the output o the screen, ( only if using the debug flag ) ... I get some messages about popullating the foot fs, and vfs, after that whe I get to kernel init its game over. I cannot scroll backwards with shift-pageup ... in order to see what happens when it fail, and if I could get some output I could try to diagnose. Any ide´a on how to proceed ? The biggest problem seems to be that it panics when mounting the root fs. But if I could get console output from the 2.6.32 kernel I would know a bit more, I know the i945g graphics chip can be a bit picky Any ideas ? Should I open a bug report ? / regards, Lars Segerlund. 2010/2/14 Frans Pop elen...@planet.nl: On Friday 12 February 2010, Lars Segerlund wrote: I have a Sony Vaio TX3 ( VGN-TX3XT ) , which runs a on an intel celeron ULW, and has a i945g graphics chip. I have reinstalled with the squeeze install cd, but cannot boot the kernels on the machine. So the installer boots and works correctly, but the installed system fails to boot. As the installer uses a 2.6.30 kernel and the installed system gets a 2.6.32 kernel, it sounds like a kernel regression that affects your system. I can get into the machine from the rescue mode on the installer, ( if I chroot into the env. it looks fairly ok ). Try installing a 2.6.30 linux-image package. You can find one here: http://stabile.debian.org:5001/package/linux-2.6/2.6.30-8/ If that works, then please file a BR against the linux-2.6 package. You may also want to try if 2.6.31 works or not. You can find packages for that if you move up one directory level in the URL above. You should also try the very latest 2.6.32 packages from unstable to see if the problem has already been fixed there. I have tried noapic nolapic acpi=off no-hlt no-irq nomodeset and most options I can find to the kernel. I suspect it hangs partly into the linux init() function, and if i set vga=788 or vga=777 the text clears and I am greeted with a blank screen ... ( vga=788 is what the installer cd uses ). Make sure you also remove the 'quiet' option so you get all the boot messages on your console. That may give a better idea where the boot is failing. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/80d224fa1002152248s84961ddgfdce7232f3c62...@mail.gmail.com
Re: Boot problem in squeeze, hang after Booting the kernel
On Friday 12 February 2010, Lars Segerlund wrote: I have a Sony Vaio TX3 ( VGN-TX3XT ) , which runs a on an intel celeron ULW, and has a i945g graphics chip. I have reinstalled with the squeeze install cd, but cannot boot the kernels on the machine. So the installer boots and works correctly, but the installed system fails to boot. As the installer uses a 2.6.30 kernel and the installed system gets a 2.6.32 kernel, it sounds like a kernel regression that affects your system. I can get into the machine from the rescue mode on the installer, ( if I chroot into the env. it looks fairly ok ). Try installing a 2.6.30 linux-image package. You can find one here: http://stabile.debian.org:5001/package/linux-2.6/2.6.30-8/ If that works, then please file a BR against the linux-2.6 package. You may also want to try if 2.6.31 works or not. You can find packages for that if you move up one directory level in the URL above. You should also try the very latest 2.6.32 packages from unstable to see if the problem has already been fixed there. I have tried noapic nolapic acpi=off no-hlt no-irq nomodeset and most options I can find to the kernel. I suspect it hangs partly into the linux init() function, and if i set vga=788 or vga=777 the text clears and I am greeted with a blank screen ... ( vga=788 is what the installer cd uses ). Make sure you also remove the 'quiet' option so you get all the boot messages on your console. That may give a better idea where the boot is failing. Cheers, FJP -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201002141940.31335.elen...@planet.nl
Re: Boot problem in squeeze, hang after Booting the kernel
Hello and thanks, I will install 2.6.30 from stable tonight, I have tried 2.6.30 from squeeze both 486 686 ... none boots. I tried debian live ( standard ) yesterday with a 2.6.26 and it boots fine. I have alredy removed the 'quiet' option it still stops at Booting the kernel , I think I have no tty and no disk at this point. I will try the kernel from stable asap. And latest 2.6.32 .. Thanks, Lars On Feb 14, 2010 7:40 p.m., Frans Pop elen...@planet.nl wrote: On Friday 12 February 2010, Lars Segerlund wrote: I have a Sony Vaio TX3 ( VGN-TX3XT ) , which ru... So the installer boots and works correctly, but the installed system fails to boot. As the installer uses a 2.6.30 kernel and the installed system gets a 2.6.32 kernel, it sounds like a kernel regression that affects your system. I can get into the machine from the rescue mode on the installer, ( if I chroot into the env. ... Try installing a 2.6.30 linux-image package. You can find one here: http://stabile.debian.org:5001/package/linux-2.6/2.6.30-8/ If that works, then please file a BR against the linux-2.6 package. You may also want to try if 2.6.31 works or not. You can find packages for that if you move up one directory level in the URL above. You should also try the very latest 2.6.32 packages from unstable to see if the problem has already been fixed there. I have tried noapic nolapic acpi=off no-hlt no-irq nomodeset and most options I can find to th... Make sure you also remove the 'quiet' option so you get all the boot messages on your console. That may give a better idea where the boot is failing. Cheers, FJP
Re: Boot problem in squeeze, hang after Booting the kernel
Should I create a bug bugreport ? I was not sure until I checked with the list ? regards, Lars Segerlund On Feb 14, 2010 7:40 p.m., Frans Pop elen...@planet.nl wrote: On Friday 12 February 2010, Lars Segerlund wrote: I have a Sony Vaio TX3 ( VGN-TX3XT ) , which ru... So the installer boots and works correctly, but the installed system fails to boot. As the installer uses a 2.6.30 kernel and the installed system gets a 2.6.32 kernel, it sounds like a kernel regression that affects your system. I can get into the machine from the rescue mode on the installer, ( if I chroot into the env. ... Try installing a 2.6.30 linux-image package. You can find one here: http://stabile.debian.org:5001/package/linux-2.6/2.6.30-8/ If that works, then please file a BR against the linux-2.6 package. You may also want to try if 2.6.31 works or not. You can find packages for that if you move up one directory level in the URL above. You should also try the very latest 2.6.32 packages from unstable to see if the problem has already been fixed there. I have tried noapic nolapic acpi=off no-hlt no-irq nomodeset and most options I can find to th... Make sure you also remove the 'quiet' option so you get all the boot messages on your console. That may give a better idea where the boot is failing. Cheers, FJP
Boot problem in squeeze, hang after Booting the kernel
Hello, I have a Sony Vaio TX3 ( VGN-TX3XT ) , which runs a on an intel celeron ULW, and has a i945g graphics chip. I have reinstalled with the squeeze install cd, but cannot boot the kernels on the machine. I can get into the machine from the rescue mode on the installer, ( if I chroot into the env. it looks fairly ok ). I can boot memtest86 and memtest86+ from the boot menu on the hd, but not the kernels. I have looked at the initrd and it looks ok, ( atleast it is possible to gunzip, and un cpio it and have a look around ). grub2 reads the initrd image, unpacks the kernel and hans after writing 'Booting the kernel' I have tried noapic nolapic acpi=off no-hlt no-irq nomodeset and most options I can find to the kernel. I suspect it hangs partly into the linux init() function, and if i set vga=788 or vga=777 the text clears and I am greeted with a blank screen ... ( vga=788 is what the installer cd uses ). I have tried linux-image-2.6.32-trunk-686, linux-image-2.6.32-trunk-486 , linux-image-2.6.30-trunk-686 to no avail. I suspect I am loosing the display so that I don't get the kernel output, and I don't have a serial port on it. I simply does not know howto continue debugging this, does anyone have any idea? Any help apreciated. Next I will build the kernel from source on the system, and try. / regards, Lars Segerlund. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
NSLU2 USBstick and 500GB HDD boot problem solved
Hi Guys, Just to let you know. I have succesfully installed Debian-arm on NSLU2 with 2GB USB Penstick on USB port 2. After that, I was able to boot up with 20GB USB hard drive on port 1 but when I connected 500GB drive I was not able to boot it up. I was playing around with UUID and boot by disk label - no success. This morning I just connected the USB stick on port 1 (according to Linksys it should not work) and the 500GB usb hdd to the USB port 2 (just swap my drives over). And guess what? :-))) It started working and I was able to boot up my NSLU2 with 2 USB storage devices connected to it :-))) I boot the root partition by UUID on the USB stick and map the 500GB hard drive as last record in /etc/fstab. Anyway, I hope it might be helpful and do no get me wrong If I have not discovered anything new :-) Cheers Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
boot problem with ldap config
Hello, When I boot or server (ia64) I receive theses errors : Starting the hotplug events dispatcher: udevd udevd[]: nss_ldap: could not connect to any LDAP server as (null) - Can't contact LDAP server udevd[]: nss_ldap: failed to bind to LDAP server ldaps://foo.bar: Can't contact LDAP server udevd[]: nss_ldap: could not connect to any LDAP server as (null) - Can't contact LDAP server udevd[]: nss_ldap: failed to bind to LDAP server ldaps://foo.bar: Can't contact LDAP server udevd[]: nss_ldap: could not connect to any LDAP server as (null) - Can't contact LDAP server udevd[]: nss_ldap: failed to bind to LDAP server ldaps://foo.bar: Can't contact LDAP server udevd[]: nss_ldap: reconnecting to LDAP server (sleeping 4 seconds) ... sleep interval is doubled each time 4,8,16,32,64... and I wait more than 15 min ctrl-c stop udevd and the boot hangs How can I solve this problem ? Thanks in advance Guy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: kernel 2,6,17, boot problem
Hi Nobel. When you will upgrade from 2.4 to 2.6 you need to add one line your GRUB/LILO . initrd and /path .. For that you need to generate the initrd image also. So add this line and reboot it. Thanks Deepak Tripathi -Original Message- From: datatek [mailto:[EMAIL PROTECTED] Sent: Saturday, September 02, 2006 3:36 AM To: debian-boot Cc: ??? Subject: kernel 2,6,17, boot problem Dear boot-list, . We are now using kernel 2.4.31. We are trying to upgrade the kernel to 2.6.17. The compilation was fine, but booting was impossible. The last error message on console was the following. Warning : Unabe to open an initial console I attached the whole screen of the console. Could you please check this problem ? . Warm regards, Nobel The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. www.aztecsoft.com
Re: kernel 2,6,17, boot problem
Quoting datatek ([EMAIL PROTECTED]): Dear boot-list, . We are now using kernel 2.4.31. debian-boot is the list for developers of the Debian installer, not exatly a list for booting problems. As this is about compiling your own custom kernel on a Debian system, I suggest you ask this in the debian-user mailing lisy signature.asc Description: Digital signature
Re: Boot problem after flasing, led is not green.
Jean-Pierre Broeders wrote: I have a problem after i flashed for the last time using this manual: http://www.cyrius.com/debian/nslu2/ After is flashed debian-sda1.bin, I shutdown the power and connect my usb harddisk. When I power my nslu2 the only green led (also after some couple of hours) i see is the transfer led. The ready/status is orange. I tried to log in with SSH, but it also doesnt work. What can be wrong? Or am i forgotten something? An amber status led and green network led is actually normal for a running nslu2 system with debian on it right now (just checked mine). We haven't sorted out the necessary stuff to turn the status and disk leds green. ssh not working of course indicates a problem. Can you ping the system? -- see shy jo signature.asc Description: Digital signature
Re: Boot problem after flasing, led is not green.
On 24/07/06, Joey Hess [EMAIL PROTECTED] wrote: Jean-Pierre Broeders wrote: I have a problem after i flashed for the last time using this manual: http://www.cyrius.com/debian/nslu2/ After is flashed debian-sda1.bin, I shutdown the power and connect my usb harddisk. When I power my nslu2 the only green led (also after some couple of hours) i see is the transfer led. The ready/status is orange. I tried to log in with SSH, but it also doesnt work. What can be wrong? Or am i forgotten something? An amber status led and green network led is actually normal for a running nslu2 system with debian on it right now (just checked mine). We haven't sorted out the necessary stuff to turn the status and disk leds green. ssh not working of course indicates a problem. Can you ping the system? I have encountered a similar problem about a half year ago, talked with Martin Michmayr about it, but we couldn't spot the reason why this happens. I eneded up using debian armeb unofficial port, but solving this issue would be a real plus. Note: I find it very useful that the status led blinks when the NSLU is powered and running in debian armeb since I have experience seldom blockage of the router and at those times the blinking stops and is easy to spot. Still I am not sure if this is a side effect or the intended behaviour, but is nice. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem after flasing, led is not green.
Hello, I have a problem after i flashed for the last time using this manual: http://www.cyrius.com/debian/nslu2/ After is flashed debian-sda1.bin, I shutdown the power and connect my usb harddisk. When I power my nslu2 the only green led (also after some couple of hours) i see is the transfer led. The ready/status is orange. I tried to log in with SSH, but it also doesnt work. What can be wrong? Or am i forgotten something? Greets JP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
(forw) Re: boot problem on laptop compaq presario 2115EU
- Forwarded message from marcoux.olivier [EMAIL PROTECTED] - Date: Mon, 27 Feb 2006 12:43:21 +0100 Subject: Re: boot problem on laptop compaq presario 2115EU From: marcoux.olivier [EMAIL PROTECTED] To: bubulle [EMAIL PROTECTED] Thanks ! I finally get it working : the linux debian-installer/probe/usb=false was part of the answer. Next problem was that when the install tells me to reboot from hd to continue the installation I still had this keyboard issue and there was no way to put usb to false. Finally I found a strange - but working - solution : I used the keyboard all during the boot process and finally the keyboard was working for the rest of the install process. Thanks again ! olivier. Quoting marcoux.olivier ([EMAIL PROTECTED]): Hi, The installation of the 3.1r1 froze on keyboard select with my presario 2115EU laptop : Nothing respond on the keyboard even Ctrl-Alt-Suppr. Has anyone already experienced this kind of problem and found a solution ? Thank you very much, Have you tried the images available from http://www.debian.org/debian/debian-installer These are the development images of D-I. Using them to install the stable version of Debian is IIRC possible if you boot with linux26 mirror/suite=stable...but recent reports have shown us that this is not guaranteed to work. Another option is trying to boot the installer with: linux debian-installer/probe/usb=false This could solve the hang you described as it can be due to USB probing for a USB keyboard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34 /mn) ; tél : 08 92 68 13 50 (0,34/mn) - End forwarded message - -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
boot problem on laptop compaq presario 2115EU
Hi, The installation of the 3.1r1 froze on keyboard select with my presario 2115EU laptop : Nothing respond on the keyboard even Ctrl-Alt-Suppr. Has anyone already experienced this kind of problem and found a solution ? Thank you very much, Olivier Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34 /mn) ; tél : 08 92 68 13 50 (0,34/mn)
Re: boot problem on laptop compaq presario 2115EU
Quoting marcoux.olivier ([EMAIL PROTECTED]): Hi, The installation of the 3.1r1 froze on keyboard select with my presario 2115EU laptop : Nothing respond on the keyboard even Ctrl-Alt-Suppr. Has anyone already experienced this kind of problem and found a solution ? Thank you very much, Have you tried the images available from http://www.debian.org/debian/debian-installer These are the development images of D-I. Using them to install the stable version of Debian is IIRC possible if you boot with linux26 mirror/suite=stable...but recent reports have shown us that this is not guaranteed to work. Another option is trying to boot the installer with: linux debian-installer/probe/usb=false This could solve the hang you described as it can be due to USB probing for a USB keyboard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sarge sparc boot problem
Hi There,
My ultra sparc 80 (2CPU, 2GB RAM) doesn't boot after the installation by
using the netboot image. coule you please advise, thanks!
Regdars,
Le
boot msgs:
---
{1} ok boot disk1
Boot device: /[EMAIL PROTECTED],4000/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 File and args:
SILO Version 1.4.8
boot:
Allocated 8 Megs of memory at 0x4000 for kernel
Uncompressing image...
Loaded kernel version 2.4.27
Loading initial ramdisk (3391488 bytes at 0xBF802000 phys, 0x40C0
virt)...
/
Remapping the kernel... Booting Linux...
Starting CPU 2... Illegal Instruction
{2} ok
---
URLs where I downloaded the bootimage on 30th of Sep 2004:
http://www.debian.org/devel/debian-installer/ports-status
http://people.debian.org/~joshk/d-i/images/daily/sparc64/netboot/boot.img
--
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Le Chen, x62266, Sun Microsystems - Central Europe
Phone: +49.89.46008.2266 Email: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge sparc boot problem
On Fri, Oct 01, 2004 at 07:10:53PM +0200, Le Chen - Sun IT Operations Central Europe wrote: Hi There, My ultra sparc 80 (2CPU, 2GB RAM) doesn't boot after the installation by using the netboot image. coule you please advise, thanks! To me it sounds like http://bugs.debian.org/267428 Regdars, Le Cheers Geert Stappers pgpXvlb6ulEOT.pgp Description: PGP signature
Bug#240372: marked as done ([sparc] [20040326] [businesscard] boot problem, then broken fstab)
Your message dated Sun, 25 Jul 2004 23:14:25 +0200 with message-id [EMAIL PROTECTED] and subject line Processed: Bug#240372: boot problem, then broken fstab has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 27 Mar 2004 00:03:01 + From [EMAIL PROTECTED] Fri Mar 26 16:03:01 2004 Return-path: [EMAIL PROTECTED] Received: from pilsener.srv.ualberta.ca [129.128.5.19] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1B71Hx-0001Co-00; Fri, 26 Mar 2004 16:03:01 -0800 Received: from ualberta.ca (beast.cns.ualberta.ca [129.128.9.77]) by pilsener.srv.ualberta.ca (8.12.10/8.12.10) with ESMTP id i2R02x1u000425 for [EMAIL PROTECTED]; Fri, 26 Mar 2004 17:02:59 -0700 (MST) Message-ID: [EMAIL PROTECTED] Date: Fri, 26 Mar 2004 17:03:00 -0700 From: Peter Karbaliotis [EMAIL PROTECTED] Organization: University of Alberta User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312 Debian/1.6-3 X-Accept-Language: en, el, ja MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: SPARCstation 5 installation report Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: installation-reports Debian-installer-version: 2004/03/26 daily sparc-sarge-businesscard.iso uname -a: Linux opal 2.4.24-sparc32 #1 Fri Jan 30 16:04:55 EST 2004 sparc unknown Date: 2004/03/04 Method: network installation, CD-ROM, mirror: sunsite.ualberta.ca, not proxied Machine: Sun SPARCstation 5 Processor: 25MHz(?) sun4m Memory: 64 MB Root Device: SCSI /dev/hda 1GB Root Size/partition table: scsi(0,3,0)part1ext332MB/boot scsi(0,3,0)part2swap128MB scsi(0,3,0)part4ext3256MB /root scsi(0,3,0)part5ext3256MB /var scsi(0,3,0)part6ext2324MB /tmp scsi(0,4,0)part1ext32GB /usr scsi(0,4,0)part2reiser 2GB /home Output of lspci: N/A Base System Installation Checklist: Initial boot worked:[E] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [ ] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [E] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: Initial boot still requires explicity setting the root device: linux root=/dev/rd/0 rw. There was a comment, IIRC, yesterday on #debian-boot which suggested that initrd doesn't have the right pivot. Installed testing. Reboot: WARNING: Your /etc/fstab does not contain the fsck passno field. I will kludge around things for you, but you should fix your /etc/fstab file as soon as you can. And then the boot hangs because the root filesystem is read-only Note: today's sarge-sparc-netinst.iso fails to install because of a missing initrd-tools package. --- Received: (at 240372-done) by bugs.debian.org; 25 Jul 2004 21:13:53 + From [EMAIL PROTECTED] Sun Jul 25 14:13:53 2004 Return-path: [EMAIL PROTECTED] Received: from cpe.atm0-0-0-2421032.0x3ef2dbfa.arcnxx7.customer.tele.dk (host.kl-teknik.com) [62.242.219.250] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1BoqJc-0001Yo-00; Sun, 25 Jul 2004 14:13:53 -0700 Received: from mail.thepenguininvasion.dk (0x5358aaae.abnxx12.adsl-dhcp.tele.dk [:::83.88.170.174]) (AUTH: PLAIN [EMAIL PROTECTED]) by host.kl-teknik.com with esmtp; Sun, 25 Jul 2004 23:18:51 +0200 id 3F16.410423BB.2179 From: Frederik Dannemare [EMAIL PROTECTED] To: [EMAIL PROTECTED], Peter Karbaliotis [EMAIL PROTECTED] Subject: Processed: Bug#240372: boot problem, then broken fstab Date: Sun, 25 Jul 2004 23:14:25 +0200 User-Agent: KMail/1.6.2 Cc: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
DI-4 IA64 boot problem
I can't boot with the ia64 beta 4 on my notebook. The boot on the cd freeze the notebook. My screen show me ascii flashing caracters. here is my notebook - http://www.faurerap.perso.cegetel.net/ So i'm using the i386 version of DI beta 4 Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: DI-4 IA64 boot problem
* VETSEL Patrice [EMAIL PROTECTED] [2004-05-12 20:04]: I can't boot with the ia64 beta 4 on my notebook. here is my notebook - http://www.faurerap.perso.cegetel.net/ So i'm using the i386 version of DI beta 4 This notebook uses the AMD chip which is i386 and not ia64 compatible. The ia64 version is not supposed to work. -- Martin Michlmayr [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem on IBM 486 machine
I am trying to install Debian 3.0 Woody Vanilla on an IBM PS/ValuePoint 486 machine. It has 64 MB of mem, IDE bios extensions, and a Maxtor 90640D4 hard disk. The cmos on this machine will not allow a boot from CD, so I made set of 2 Vanilla boot floppies from CD#1. At the boot: prompt I entered 'linux hd=12495,16,63'. The hard disk shows up OK in the partition menu, and I put in Linux and Swap partitions, leaving some space free. The install seems to go OK up to the point where I try to boot for the first time from the hard disk. Something is messed up in the boot record, and instead of booting, it writes an 'L', then fills the screen slowly with ' 40'. I can boot with the custom floppy I made during the install and continue through the install. Just can't seem to get it to boot from the hard disk. At first I thought there might be something wrong with the MBR, so I reinstalled with the optional install of LILO to the Linux partition boot record. It boots through the MBR OK, but then does exactly the same thing. So it looks to me like there is something wrong with what the install is putting in the boot record. Any ideas what I may be hosing up? This is only the third install I have done (the other two, on Pentium II machines booting off CD, went well), so be gentle, I am only an egg! Thanks, JT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
aspire 1400 boot problem
Hi, when i try to boot my system with bf24 it hang on Compaq CISS driver (v 2.4.5 ) i'm using an Acer Aspire 1400 and debian 3.0 r2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: aspire 1400 boot problem
On Sun, Feb 01, 2004 at 02:38:45PM +0100, [EMAIL PROTECTED] wrote: Hi, when i try to boot my system with bf24 it hang on Compaq CISS driver (v 2.4.5 ) i'm using an Acer Aspire 1400 and debian 3.0 r2 Maybe you should try out the new debian-installer beta2, look at : http://www.debian.org/devel/debian-installer/ For details. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#223624: Installer Report - CD boot problem, IDE_SCSI module prevents IDE CDROM mounting, and inflexibility in options - but good hardware detection and working sound.
Am Mit, den 10.12.2003 schrieb Barrie James um 23:34: Suggestions : I'm surprised the network config is split into 2 sections, dhcp and static. I would have thought that this would be 2 options in a single section, maybe with dial-up as a further option as a lot of Debian users will have dial-up as their only network connection. I would also make a floppy a prominent option for LILO or GRUB - if you already have a working system I think it makes more sense to use a floppy for the first couple of boots rather than overwriting the mbr during a new install. This will be fixed soon. The next version of netcfg will combine dhcp and static configuration. gaudenz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#223624: Installer Report - CD boot problem, IDE_SCSI module prevents IDE CDROM mounting, and inflexibility in options - but good hardware detection and working sound.
Package:installation-reports Debian-installer-version: download 21 November - http://gluck.debian.org/ cdimage/testing/netinst/i386/beta-1/sarge-i386-netinst.iso 100MB uname -a: Linux localhost 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 GNU/Linux Date: 25 or 26 Nov. Method: Tried to boot CD (see comments), failed, and then used floppy image to boot the CD. Machine: Self-build. EPOX 8KHA+ Mobo (VIA KT266A, VT8366A and VT8233 onboard sound) Processor: AMD XP 1600+ Memory: 256MB DDR Root Device: IDE (IBM ATA100 HDD) : /dev/hda13 Root Size/partition table: A 5GB single partition on an existing extended partition Output of lspci: 00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] 00:0d.0 Ethernet controller: 3Com Corporation 3cSOHO100-TX Hurricane (rev 30) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/ A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.2 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:11.3 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:11.4 USB Controller: VIA Technologies, Inc. USB (rev 1b) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 30) 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 04) Base System Installation Checklist: Initial boot worked: [E] Configure network HW: [O] Config network: [E] Detect CD: [E] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [ ] Create file systems: [O] Mount partitions: [O] Install base system: [O] Install boot loader: [E] Reboot: [O] [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Comments/Problems: 1) This is the first CD that has ever failed to boot on my system. It booted a laptop OK, but my system failed completely. I've installed a range of distros on this box - Potato, Woody r0, Woody r1, Slackware 8, 9, 9.1, Mandrake 8.1, 8.2, 9 without any problems booting. I had the first few Sarge unofficial CDs from the .hu mirror and the first of these booted fine. The boot device selector floppy image on the installer CD solved the problem and I was able to start the process from the CD after booting the floppy. 2) I suffered the IDE-SCSI module problem (which I hadn't seen at the time). As I had got a few of the unofficial Sarge CDs I intended to register them as apt sources during the install, but this failed. Following the reboot it was clear that this was down to the IDE CD not being mounted. I got round it by simply removing the IDE-SCSI module and accessing the CD drive was was then fine. 3) The network configure with dhcp wouldn't let me leave it unconfigured. I have a separate Linux firewall connected by ethernet so my system is a static network with NAT on the firewall. I got around the installer throwing me back to the start of the dhcp config section by skipping ahead to network configuration without dhcp and after this it was ok. 4) I tried to avoid LILO but it refused to let me. I didn't want to re-write my mbr so put /dev/fd0 as the LILO target. It didn't like this for some reason. I then skipped ahead to the GRUB section and set this to a floppy which was OK. 5) My onboard VIA8233 sound chip has given quite a few Debian users a problem (as a quick google search will show), and the only real solution has been installing ALSA and recompiling the kernel - no big deal, but inconvenient compared to other distros which use ALSA and manage to get sound configured in the initial install. It's encouraging that the new Debian Installer managed to get sound working, although it uses the VIA 82cxxx module which isn't correct (Knoppix will happily boot my machine and also gets sound running on the VIA 82cxxx module) I haven't had a chance yet to really test the sound capabilities, but it does seem fine - a great result for a Debian installer. Conclusion : I had several problems, and can't say I particularly liked the installer. The hardware detection is certainly improved and is a very positive aspect, but the way that a couple of specific steps tried to prevent me leaving them was a negative. I doubt that a newbie would have a happy time with the installer on my box. Suggestions : I'm surprised the network config is split into 2 sections, dhcp and static. I would have thought that this would be 2 options in a single section, maybe with dial-up as a further option as a lot of Debian users will have dial-up as their only network connection. I would also make a floppy a prominent option for LILO or GRUB - if you already have a working system I think it makes more sense to use a floppy for the first couple of boots rather than overwriting the mbr during a new install. -- To UNSUBSCRIBE, email to [EMAIL
boot problem please help!
Hi AllI decided to try to install the Sarge (testing) version as it has the 2.4 kernel. I got it installed but when I went to reboot I get the following error.LILO 22.5.7.2 Loading LinuxEBDA is big; kernel setup stackoverlaps Lilo second stage.Can anyone tell me what the problem is and even more important is there anything I can do about it?Tom Masterson
d-i initial boot problem
The initial boot hangs with: modprobe: failed to load module vesafb I've tried mono and video=vga16:off as boot options. Same problem... I've tried both the businesscard and netinst iso. -Thomas _ Wußten Sie, daß Sie Ihren Hotmail-Posteingang auch über den MSN Messenger abrufen können? http://messenger.msn.de Jetzt kostenlos downloaden und einfach testen! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i initial boot problem
On Wed, Oct 01, 2003 at 08:15:07PM +0200, thomas corda wrote: The initial boot hangs with: modprobe: failed to load module vesafb I've tried mono and video=vga16:off as boot options. Same problem... I've tried both the businesscard and netinst iso. Thanks for telling. Are you willing to tell more? Like which images from which site you use. Tell also more about the hardware you are using. Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i initial boot problem
Thanks for telling. Are you willing to tell more? Like which images from which site you use. Tell also more about the hardware you are using. I've used the images from http://gluck.debian.org/cdimage/testing/netinst/i386/ The PC: Dual Celeron 500 (Abit BP6 MoBo) 256MB RAM 4 hd + 2 cd drives graphic: Nvidia GForce1 32MB ethernet: Realtek RTL8139 sound and isdn card I read that there is a bug in the usb-discover. The vesafb is modprobed right after the usb stuff. I got an 'E: Unimplemented function' on a refreshed screen. _ Freunde werben und kräftig abräumen mit der Messenger-Mania. http://messenger-mania.msn.de FreeSMS und 1 von 666 Webcams von Logitech sichern! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: d-i initial boot problem
On Wed, Oct 01, 2003 at 09:37:22PM +0200, thomas corda wrote: Thanks for telling. Are you willing to tell more? Like which images from which site you use. Tell also more about the hardware you are using. I've used the images from http://gluck.debian.org/cdimage/testing/netinst/i386/ The PC: Dual Celeron 500 (Abit BP6 MoBo) 256MB RAM 4 hd + 2 cd drives graphic: Nvidia GForce1 32MB ethernet: Realtek RTL8139 sound and isdn card I read that there is a bug in the usb-discover. The vesafb is modprobed right after the usb stuff. I got an 'E: Unimplemented function' on a refreshed screen. Okay, looks like http://lists.debian.org/debian-boot/2003/debian-boot-200310/msg00041.html Please file a bugreport for it. Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
On Mon, Aug 04, 2003 at 12:57:46AM -0400, soupman wrote: Hi! This: http://lists.debian.org/debian-boot/2003/debian-boot-200302/msg00253.html | | I think I only have 8MB of RAM is that maybe the problem? If so, is | | Yes. | | there a way to work around that? | | Get Slink disks from http://archive.debian.org and install with them. | appears to be an architecture problem. I have reached the installation screen without a problem using a computer with 8MB RAM, but it failed as per the message with another computer (Thinkpad AT clone) with 8MB RAM. What is the type number of the processor? Geert Stappers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem
Hi! This: http://lists.debian.org/debian-boot/2003/debian-boot-200302/msg00253.html appears to be an architecture problem. I have reached the installation screen without a problem using a computer with 8MB RAM, but it failed as per the message with another computer (Thinkpad AT clone) with 8MB RAM. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
boot problem
Hello,I am trying to install debian Linux over network, i am using floppies to boot a 50MHz 486 16meg of Ram , i get the 'boot:' prompt without problems, i then hit enter to install default optionScreen looks like thisBoot:Loading Linux.bin . . . . . . . . . . . . . . . . . . Ready. Then nothing, tried typing 'floopy0' or 'ramdisk0' at the boot: prompt but got a kernal not found error, so i just hit enter i don't know what to do now : ( after the Ready, i try pressing keys but nothing happens... what am i suppose to do? run a command? but i found that if i press lots of keys it beeps at my as if the keyboard buffer has been filled.hehehe... i wonder what it is ready for. . . . can u help please? Kind regards Michael
Re: boot problem
On Sat, Jul 12, 2003 at 10:21:01PM +1000, Michael wrote: Hello, I am trying to install debian Linux over network, i am using floppies to boot a 50MHz 486 16meg of Ram , i get the 'boot:' prompt without problems, i then hit enter to install default option Screen looks like this Boot: Loading Linux.bin . . . . . . . . . . . . . . . . . . Ready. Then nothing, tried typing 'floopy0' or 'ramdisk0' at the boot: prompt but got a kernal not found error, so i just hit enter i don't know what to do now : ( after the Ready, i try pressing keys but nothing happens... what am i suppose to do? run a command? but i found that if i press lots of keys it beeps at my as if the keyboard buffer has been filled. hehehe... i wonder what it is ready for. . . . can u help please? Kind regards Michael Read through the boot help screens, F1 through F8 or so. Try one of the other flavors, probably idepci. Your memory is marginal, you probably wouldn't be able to use a 2.4 kernel; so more memory would also be helpful. -- Debian GNU/Linux Operating System By the People, For the People Chris Tillman (a people instance) toff one at cox dot net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem
I recently installed Debian from the LordSutch.com ISOLINUX mini-iso. When I got to the step where you try to boot from the hard drive, it did not work. I can boot from the boot floppy created during installation. But when I try to boot from the hard drive I get a text screen that says: MBR 01 01 01 01 01 01... repeating forever until I reset. When I boot from floppy, I can access everything. Network works fine, installation continued to download needed application files etc. So here is my setup and conditions: I have two hard drives, Maxtor 4GB each. Windows 98 on the master (hda) Linux on the slave (hdb) On hdb are seven partitions. The first is bootable hdb1. It is only 8MB. The second is the \. Third through sixth are \usr, \home, \var \tmp. Last is SWAP. The installation program detected another bootable operating system , asked if I wanted to include it as a boot option. I answered 'yes'. Installation said I am setting up to boot from a drive that is not the master which is not supported by some BIOS. I said do it anyway. And then I rebooted. The first time through it booted windows 98 like previous to installation. So I modified the BIOS to boot from the slave. The next boot gave the endless 01 01 01.. like I stated above. Booting from the floppy works great, but I don't want to do this forever. Please give me some advice and assistance. Jeff [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
On Sun, Jul 06, 2003 at 06:57:47PM -0500, Jeff wrote: I recently installed Debian from the LordSutch.com ISOLINUX mini-iso. When I got to the step where you try to boot from the hard drive, it did not work. I can boot from the boot floppy created during installation. But when I try to boot from the hard drive I get a text screen that says: MBR 01 01 01 01 01 01... repeating forever until I reset. Fist check that you have made the root partition bootable in the installer's partitioner, and that /target/etc/lilo.conf points to that partition. I downloaded the lilo-21.tar.gz package and checked the README. You may have this README in your system under /target/usr/share/doc/lilo when you boot the installer. It says: --- Boot loader messages The boot loader generates three types of messages: progress and error messages while it is loading, messages indicating disk access errors, and error messages in response to invalid command-line input. Since messages of the latter type are usually self-explanatory, only the two other categories are explained. LILO start message - - - - - - - - - When LILO loads itself, it displays the word LILO. Each letter is printed before or after performing some specific action. If LILO fails at some point, the letters printed so far can be used to identify the problem. This is described in more detail in the technical overview. Note that some hex digits may be inserted after the first L if a transient disk problem occurs. Unless LILO stops at that point, generating an endless stream of error codes, such hex digits do not indicate a severe problem. (nothing) No part of LILO has been loaded. LILO either isn't installed or the partition on which its boot sector is located isn't active. L error ... The first stage boot loader has been loaded and started, but it can't load the second stage boot loader. The two-digit error codes indicate the type of problem. (See also section Disk error codes.) This condition usually indicates a media failure or a geometry mismatch (e.g. bad disk parameters, see section Disk geometry). LI The first stage boot loader was able to load the second stage boot loader, but has failed to execute it. This can either be caused by a geometry mismatch or by moving /boot/boot.b without running the map installer. LIL The second stage boot loader has been started, but it can't load the descriptor table from the map file. This is typically caused by a media failure or by a geometry mismatch. LIL? The second stage boot loader has been loaded at an incorrect address. This is typically caused by a subtle geometry mismatch or by moving /boot/boot.b without running the map installer. LIL- The descriptor table is corrupt. This can either be caused by a geometry mismatch or by moving /boot/map without running the map installer. LILO All parts of LILO have been successfully loaded. Disk error codes - - - - - - - - If the BIOS signals an error when LILO is trying to load a boot image, the respective error code is displayed. The following BIOS error codes are known: 0x00 Internal error. This code is generated by the sector read routine of the LILO boot loader whenever an internal inconsistency is detected. This might be caused by corrupt files. Try re-building the map file. Another possible cause for this error are attempts to access cylinders beyond 1024 while using the LINEAR option. See section BIOS restrictions for more details and for how to solve the problem. 0x01 Illegal command. This shouldn't happen, but if it does, it may indicate an attempt to access a disk which is not supported by the BIOS. See also Warning: BIOS drive 0xnumber may not be accessible in section Warnings. 0x02 Address mark not found. This usually indicates a media problem. Try again several times. 0x03 Write-protected disk. This should only occur on write operations. 0x04 Sector not found. This typically indicates a geometry mismatch. If you're booting a raw-written disk image, verify whether it was created for disks with the same geometry as the one you're using. If you're booting from a SCSI disk or a large IDE disk, you should check, whether LILO has obtained correct geometry data from the kernel or whether the geometry definition corresponds to the real disk geometry. (See section Disk geometry.) Removing COMPACT may help too. So may adding LINEAR. 0x06 Change line active. This should be a transient error. Try booting a second time. 0x07 Invalid initialization. The BIOS failed to properly initialize the disk controller. You should control the BIOS setup parameters. A warm boot might help too. 0x08 DMA overrun. This shouldn't happen. Try booting again. 0x09 DMA attempt across 64k
Debian 3.0 bf24 boot problem
Hi! I've try to boot Debian 3.0 with experimental 2.4 kernel, but after one screen of stuff the boot process stops. Actually it come to the point: enabled ExtINT on CPU#0 ESR value before enabling vector : 0002 Later I try to use kernel parameters debug, nomce, nmi_watchdog, but no luck. Same thing happened when I tried to boot Red Hat 8.0. The MB is PCChips M825ULR with AMD Duron 1200 MHz. Can you help me?
Boot problem
i cannot install Debain on a G4 867 dual becaus it can't find the hard disk. under mac OS x it is located in /dev/rdisk0 but Debian installer can't find it -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
On Sun, Nov 24, 2002 at 02:26:09PM +0100, Dario Meloni wrote: i cannot install Debain on a G4 867 dual becaus it can't find the hard disk. under mac OS x it is located in /dev/rdisk0 but Debian installer can't find it d-i powerpc port is currently suspended because noone works on it. bastian -- Oblivion together does not frighten me, beloved. -- Thalassa (in Anne Mulhall's body), Return to Tomorrow, stardate 4770.3. msg23808/pgp0.pgp Description: PGP signature
Re: Boot problem
On Sun, Nov 24, 2002 at 04:34:32PM +0100, Bastian Blank wrote: On Sun, Nov 24, 2002 at 02:26:09PM +0100, Dario Meloni wrote: i cannot install Debain on a G4 867 dual becaus it can't find the hard disk. under mac OS x it is located in /dev/rdisk0 but Debian installer can't find it d-i powerpc port is currently suspended because noone works on it. This refers to the sarge version. Were you using sarge, or woody? -- ** |Chris Tillman[EMAIL PROTECTED] | | To HAVE, GIVE all TO all (ACIM) | ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
smp/dac960/i440gx boot problem
Hello all, I'm with some troubles on trying to boot a kernel in a dual PPro machine. When a compile the kernel with smp support the machine hungs during the boot, this occurs exactly when the dac960 driver is being loaded. When I remove the smp support the driver is loaded but I have only one processor running. I think the problem is the i440gx pci bridge and the pci-apic irq transform. But I can't figure out why this is happening. If someone knows some workaround, please let me know. Thanks in advance, Carlos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: smp/dac960/i440gx boot problem
On Tue, 30 Apr 2002 20:37:53 -0300 Carlos Francisco Regis [EMAIL PROTECTED] wrote: I think the problem is the i440gx pci bridge and the pci-apic irq Actually it's a i450kx/gx. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
still boot problem
Ok, i wanted to install DeMuDi, dowloaded the RAW-file and wrote it to a CD. B ut because the CD was not bootable i just created Boot-Disks from the rescue.b in, root.bin and driver-1.bin in /dists/woody/main/disks-i386/3.0.0-200107-30 /images-1.44. So far so good. But when booting the rescue disk the system hags. I cannot do anything but pus h my reset-button. The last to lines I can see are: Try using the versions in the compact or idepci directories instead. Maybe one of those will work better. p. i already did this, but then DeMuDi searches the CD for the compact or idepci kernel, which is not on it and stops the installation. Loki -- ___ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup 1 cent a minute calls anywhere in the U.S.! http://www.getpennytalk.com/cgi-bin/adforward.cgi?p_key=RG9853KJurl=http://www.getpennytalk.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: still boot problem
On Mon, Dec 10, 2001 at 02:35:53AM +0800, Pablo Puerro wrote: Ok, i wanted to install DeMuDi, dowloaded the RAW-file and wrote it to a CD. B ut because the CD was not bootable i just created Boot-Disks from the rescue.b in, root.bin and driver-1.bin in /dists/woody/main/disks-i386/3.0.0-200107-30 /images-1.44. So far so good. But when booting the rescue disk the system hags. I cannot do anything but pus h my reset-button. The last to lines I can see are: Try using the versions in the compact or idepci directories instead. Maybe one of those will work better. p. i already did this, but then DeMuDi searches the CD for the compact or idepci kernel, which is not on it and stops the installation. Loki Sounds like you need to get with the DeMuDi folks (we're not them). -- *--v-- Installing Debian GNU/Linux 3.0 For PowerPC -v* | http://mirrors.kernel.org/debian/dists/woody/main/disks- | | (pause for breath)powerpc/current/doc/install.en.html| | debian-imac: http://debian-imac.sourceforge.net | |Chris Tillman[EMAIL PROTECTED] | | May the Source be with you | ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem
Sorry, I'am new of the list, I've a Acer Travel Mate 613 TXV with no floppy controller, when I boot for the installation of my Debian, the system stops after the line: floppy0: no floppy controller found md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 I've tested Debian rev3, rev4 Woody and SID. The Red Hat (6.2 and 7.1) work fine. Can I resolv my problem ?? Osvaldo P.S. Sorry for my English -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
On Tue, Dec 04, 2001 at 02:44:51PM +0100, Osvaldo wrote: Sorry, I'am new of the list, I've a Acer Travel Mate 613 TXV with no floppy controller, when I boot for the installation of my Debian, the system stops after the line: floppy0: no floppy controller found md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 I've tested Debian rev3, rev4 Woody and SID. The Red Hat (6.2 and 7.1) work fine. Can I resolv my problem ?? Woody is the best one for us to work with. Did you make a CD and try to boot from that, or how are you trying to boot? -- ** | .''`. | Debian GNU/Linux: http://www.debian.org | | : :' : | debian-imac: http://debian-imac.sourceforge.net | | `. `'` | Chris Tillman[EMAIL PROTECTED] | | `-|May the Source be with you| ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#113239: boot problem
Processing commands for [EMAIL PROTECTED]: retitle 113239 [i386] booting from DOS Bug#113239: boot problem Changed Bug title. tags 113239 + potato Bug#113239: [i386] booting from DOS Tags added: potato tags 113239 + moreinfo Bug#113239: [i386] booting from DOS Tags added: moreinfo thanks Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot Problem
I´m Ricardo Gastón Salomone, and yesterday I tried to install Debian 2.1 in my computer but I couldn´t. Following this, It is the detail of the boot part. After the message "DC390: 0 adapters Found" the systems hangs. The computer stops there. It didn´t tell me what´s the problem. First I thought That It could be my modem, or the sound card, the scsi card, my two network adapters, but I take all of them out of the pc and it still happens. The system hangs in the same point. What it could be??? My computer has a Gigabyte 71xe motherboard, with an Athlon 600 Mhz and 192Mbytes of memory. Please help me Thanks Ricardo Gastón Salomone. Probing PCI hardwareCalibrating delay loop... Ok - 604.57 BogoMIPSMemory: 62888k/66556 available (1144k kernel code , 384k reserved,1448k data)Swansea University Computer Society NET3.035 for Linux 2.0NET3: Unix domainsovkets 0.13 for Linux NET.034IP Prototcols: ICMP, IGMP, UDP, TCPChecking 386/387 coupling... Ok, fpu using exception 16 error reporting.Cheking 'hlt' instruction... Ok.Linux version 2.0.38 (root@lollypop) (gcc version 2.7.2.3)#2 thu Dec 9 04:30:31 PST 1999Starting kswapd v 1.4.2.2Real Time Clock Driver v 1.09Ramdisk driver initialized: 16 ramdisks of 4096k sizeLoop: registered device at major 7.Hda: SAMSUNG SV1296A, 12323MB w/482KB Cache, CHS=1571/255/63Hdc: HITACHI DVD-ROM GC-2500, ATAPI CDROM driveIde0 at 0x1f0-0x1f7, 0x3f6 on irq 14Ide1 at 0x170-0x177,0x376 on irq15Floppy drive(s): fd0is 1.44MFDC 0 is a post-1991 82077Md driver 0.36.3MAX_MD_DEV=4, MAX_REAL=8Sym53c416.c: version 1.0.0DC390: 0 adapters found
Boot Problem
I´m Ricardo Gastón Salomone, and yesterday I tried to install Debian 2.1 in my computer but I couldn´t. Following this, It is the detail of the boot part. After the message "DC390: 0 adapters Found" the systems hangs. The computer stops there. It didn´t tell me what´s the problem. First I thought That It could be my modem, or the sound card, the scsi card, my two network adapters, but I take all of them out of the pc and it still happens. The system hangs in the same point. What it could be??? My computer has a Gigabyte 71xe motherboard, with an Athlon 600 Mhz and 192Mbytes of memory. Please help me Thanks Ricardo Gastón Salomone. Probing PCI hardwareCalibrating delay loop... Ok - 604.57 BogoMIPSMemory: 62888k/66556 available (1144k kernel code , 384k reserved,1448k data)Swansea University Computer Society NET3.035 for Linux 2.0NET3: Unix domainsovkets 0.13 for Linux NET.034IP Prototcols: ICMP, IGMP, UDP, TCPChecking 386/387 coupling... Ok, fpu using exception 16 error reporting.Cheking 'hlt' instruction... Ok.Linux version 2.0.38 (root@lollypop) (gcc version 2.7.2.3)#2 thu Dec 9 04:30:31 PST 1999Starting kswapd v 1.4.2.2Real Time Clock Driver v 1.09Ramdisk driver initialized: 16 ramdisks of 4096k sizeLoop: registered device at major 7.Hda: SAMSUNG SV1296A, 12323MB w/482KB Cache, CHS=1571/255/63Hdc: HITACHI DVD-ROM GC-2500, ATAPI CDROM driveIde0 at 0x1f0-0x1f7, 0x3f6 on irq 14Ide1 at 0x170-0x177,0x376 on irq15Floppy drive(s): fd0is 1.44MFDC 0 is a post-1991 82077Md driver 0.36.3MAX_MD_DEV=4, MAX_REAL=8Sym53c416.c: version 1.0.0DC390: 0 adapters found
Re: Boot Problem
#include hallo.h Ricardo Gastón Salomone wrote on Mon Aug 27, 2001 um 10:06:35AM: I´m Ricardo Gastón Salomone, and yesterday I tried to install Debian 2.1 in my computer but I couldn´t. LOL. 2.1 has been released years ago, you cannot expect it running with the brand-new hardware without problems. Take Potato, or try your luck with woody if you have fast network connection. Following this, It is the detail of the boot part. After the message DC390: 0 adapters Found the systems hangs. The computer stops there. It didn´t tell me what´s the problem. First I thought That It could be my modem, or the sound card, the scsi card, my two network adapters, but I take all of them out of the pc and it still happens. The system hangs in the same point. What it could be??? My computer has a Gigabyte 71xe motherboard, with an Athlon 600 Mhz and 192Mbytes of memory. Which chipset? If KT133A, did you update your BIOS? Gruss/Regards, Eduard. -- Actually, Microsoft is sort of a mixture between the Borg and the Ferengi. Stimmt doch eh nicht, die letzten beiden wissen wenigstens, wie man etwas baut! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
On Sun, May 13, 2001 at 03:30:56PM +1000, Robert Butler wrote: Problem is I can't press that Continue button, so have never gotten past this screen. No response to any keyboard or mouse commands from this screen, including Ctrl-alt-delete: I have to reboot via the reset button. Of course it did respond to the keyboard up until the enter command to start installation. System is an AMD Athlon processor with 256MB pc133 dram, a Seagate Medalist drive 13GB with a MS natural keyboard connected to the PS2 keyboard connector, and a USB optical mouse connected to 'the first USB port. I don't know what other system info might be relevant to this situation? Just a wild suggestion, but please try a PS/2 mouse. There have been problems in the past with the mouse controller confusing the keyboard driver, for some kernels and some BIOSes. Make sure you don't move the mouse at all from the time you power up. Regards, Mark. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem
Hi, I wonder if anyone could help me with an installation problem. I'm trying to install Debian 2.2r2 from CD onto an AMD based PC. This is a completely empty drive I'm installing to. So far I have seen the black screen with the help pages (and read them), pressed enter, seen lots of info whizz past, and arrived at a credits screen with the word Continue and a blinking cursor at the bottom of the page, just waiting to be pressed.. Problem is I can't press that Continue button, so have never gotten past this screen. No response to any keyboard or mouse commands from this screen, including Ctrl-alt-delete: I have to reboot via the reset button. Of course it did respond to the keyboard up until the enter command to start installation. System is an AMD Athlon processor with 256MB pc133 dram, a Seagate Medalist drive 13GB with a MS natural keyboard connected to the PS2 keyboard connector, and a USB optical mouse connected to 'the first USB port. I don't know what other system info might be relevant to this situation? I am a complete beginner with Linux, though I have successfully installed Red Hat on a previous machine and played with it a bit, and so I have a very basic idea about what to expect of Linux. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem with Penguin Relion
"Kevin L. Gross" [EMAIL PROTECTED] writes: Hi, My Penguin Relion was running RedHat6.2 when I purchased the system. I upgraded to RedHat7.0 with no problems. I just purchased a Debian2.2_r2 CD set and booted directly off the CD. The boot process hangs after the last line shown here: megaraid:v1.11 (Aug. 23, 2000) megaraid: found 0x101e:0x1960:idx 0:bus 4:slot 0:func 0 scsi2: Found a MegaRAID controller at 0xfc804008, IRQ: 5 Try booting from the 2nd CD perhaps? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onshored.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem with Penguin Relion
Adam Di Carlo [EMAIL PROTECTED] writes: "Kevin L. Gross" [EMAIL PROTECTED] writes: Hi, My Penguin Relion was running RedHat6.2 when I purchased the system. I upgraded to RedHat7.0 with no problems. I just purchased a Debian2.2_r2 CD set and booted directly off the CD. The boot process hangs after the last line shown here: megaraid:v1.11 (Aug. 23, 2000) megaraid: found 0x101e:0x1960:idx 0:bus 4:slot 0:func 0 scsi2: Found a MegaRAID controller at 0xfc804008, IRQ: 5 Try booting from the 2nd CD perhaps? Err, unless there's something special/different about the 2nd CD, that won't help. It's basically the kernel MegaRAID bug; the only solution AFAIK is to boot using an older (= 2.2.14) or newer (= 2.2.19preX) kernel[1]. -- James [1] At least those are the versions boundaries we've used that worked; I don't recall exactly when the bug was introduced or when it was fixed. The latter at least is probably easy to determine from Alan's changelogs, if necessary. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Boot problem with Penguin Relion
Hi, My Penguin Relion was running RedHat6.2 when I purchased the system. I upgraded to RedHat7.0 with no problems. I just purchased a Debian2.2_r2 CD set and booted directly off the CD. The boot process hangs after the last line shown here: megaraid:v1.11 (Aug. 23, 2000) megaraid: found 0x101e:0x1960:idx 0:bus 4:slot 0:func 0 scsi2: Found a MegaRAID controller at 0xfc804008, IRQ: 5 Any help or pointers would be appreciated. I can be reached toll-free 1-866-726-3674 if needed. -Kevin L. Gross Randori News Inc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#70798: UDMA66 boot problem/HPT370
Adam Di Carlo wrote: Glenn McGrath [EMAIL PROTECTED] writes: Adam Di Carlo wrote: Glenn McGrath [EMAIL PROTECTED] writes: I just tested the 2.2.17-ide and 2.2.18-ide kernels and they both detect a HPT370 chip Where does this lead us? Are you saying the HPT370 problems should be fixed as of 2.2.18-ide (as opposed to 2.2.18pre21-ide which we are using now)? Well, i just tried the 2.2.18-ide kernel and detects the HPT370 chip as well, so i guess we should look elsewhere for the casue of failure. I don't see how that follows, since the latest release version of boot-floppies uses the 2.2.18pre21-ide kernel. Can you try with that kernel and see if it also detects the controller? Soryy, i should read my email before i send it, the first time i tried it with 2.2.17-ide and 2.2.18-ide, both worked, then i went back and tried 2.2.18pre21-ide and that also detected the HPT370. Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#70798: UDMA66 boot problem/HPT370
Glenn McGrath [EMAIL PROTECTED] writes: I just tested the 2.2.17-ide and 2.2.18-ide kernels and they both detect a HPT370 chip Where does this lead us? Are you saying the HPT370 problems should be fixed as of 2.2.18-ide (as opposed to 2.2.18pre21-ide which we are using now)? -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#70798: UDMA66 boot problem/HPT370
Adam Di Carlo wrote: Glenn McGrath [EMAIL PROTECTED] writes: I just tested the 2.2.17-ide and 2.2.18-ide kernels and they both detect a HPT370 chip Where does this lead us? Are you saying the HPT370 problems should be fixed as of 2.2.18-ide (as opposed to 2.2.18pre21-ide which we are using now)? Well, i just tried the 2.2.18-ide kernel and detects the HPT370 chip as well, so i guess we should look elsewhere for the casue of failure. I remember about 6 months ago i did hear of problems with the HPT366 and some samsung(i think) drives... apart from that i have no idea. Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#70798: UDMA66 boot problem/HPT370
I just tested the 2.2.17-ide and 2.2.18-ide kernels and they both detect a HPT370 chip Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#79459: Processed: reassign Re: Bug#79459: UDMA66/HPT370 boot problem
Glenn, you sent this followup to the wrong place. Resending. Glenn McGrath [EMAIL PROTECTED] writes: Acording to www.linux-ide.org hpt370 should be supported under the 2.2 series fo kernels, the first patch i see was to 2.2.16, so it should be integrated with anything above that. HPT370 is handled by the HPT370 driver as far as i can tell. Could you please try the latest udma66 flavour of boot-floppies. Yes. Please report precisely what version of boot-floppies you are using. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: UDMA66 boot problem/HPT370
To install debian potato on an abit kt7-raid motherboard: (well, this is what I roughly did) 1 Connect your disk to the first ide controller, not to the HTP370 controller 2 I used the debian/dists/potato/main/disks-i386/ 2.2.20.0.1-2000-12-03/images-1.44/idepci disk set 3 boot and install as usual 4 download and unpack kernel/v2.2/linux-2.2.18.tar.gz 5 download and apply patch kernel/people/hedrick/ ide.2.2.18.1209.patch.gz 6 make menuconfig - Block devices: [*]Generic PCI IDE chipset support ... [*] HPT366 chipset support Don't know about theese two but they seem to work for me [*]HPT366 Fast Interrupt support (WIP) [*]HPT366 mode three unsupported (WIP) (Note! this driver has no raid support, you just get the udma100 support and two more controllers, only connect discs to hpt controller) and whatever else you want in the kernel 7 make dep; make bzImage; make modules; make modules_install 8 cp arch/.../bzImage System.map to /boot 9 add new image to lilo.conf with root=/dev/hdexx instead of hda 10 run lilo 11 change hda to hde in /etc/fstab 12 shutdown -h now 13 poweroff 14 move disk cable to first HPT370 connector 15 boot Regards, /Karl --- Karl HammarAspö Data [EMAIL PROTECTED] Lilla Aspö 2340 +46 173 140 57Networks S-742 94 Östhammar +46 70 511 97 84 Computers Sweden Consulting --- -- From: "Alexander Sawallich" [EMAIL PROTECTED] Subject: UDMA66 boot problem/HPT370 Date: Tue, 12 Dec 2000 21:46:46 +0100 When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller, with the UDMA66 boot floppies, the system halts during the boot process. ... ... Abit KT7-Raid Motherboard ... Alexander -- From: Jon Branch [EMAIL PROTECTED] Subject: RE: UDMA66 boot problem/HPT370 Date: Wed, 13 Dec 2000 02:01:37 -0500 (EST) Hi Alexander Sorry no solution from me. I'm faced with a near identical problem using the HPT 370 on-board controller with a 2theMax BX7 +100 motherboard (actually with five of them). So I'll be interested to see the solution if/when you get one. Regards Jon Branch ... -- From: "Alexander" [EMAIL PROTECTED] Subject: RE: UDMA66 boot problem/HPT370 Date: Thu, 14 Dec 2000 23:18:15 +0100 I´m desperate to install debian eventhough it doesn´t seem to work with me. I had Suse installed a year ago, but I don´t want to put up with there funny rc.config-thingy any more. It seems that my onboard HPT370 controller should be supported on the udma66 floppies. I just got unlucky and so it doesn´t work. I already received a few replies by some other KT7 owners indicating that I´m not alone. I can boot into the setup assistant just fine from the regular 2.2r2 CD, but then I have no harddisk. There´s an option in the setup menu that lets you load modules from floppy, and I tried loading something from the UDMA66 driver1-4 disks, but then I only got an error telling me that the system is unable to mount the floppy (???). Also I´m not so sure if there´s a useful driver on those disks anyhow. When I boot from the udma66 floppies it just stops half way (see description below) . I really don´t know what more to do. Maybe I could boot from the CD by supplying a bunch of boot parameters, describing my disk. So if you have a clue what I (and many others) could do I would really appreciate if you send me a reply. Under Windows the HPT370 controller(ide2 ide3 ( counting from 0)) seems to run as a scsi device. If you need any information youst ask me. Thanks a lot. Alexander ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: UDMA66 boot problem/HPT370
Jon Branch wrote: Hi Alexander Sorry no solution from me. I'm faced with a near identical problem using the HPT 370 on-board controller with a 2theMax BX7 +100 motherboard (actually with five of them). So I'll be interested to see the solution if/when you get one. Regards I read up the HPT370 today, its supposed to be supported in the 2.2 kernel series (post 2.2.16 i think). It should be handled by the hpt366 driver, which is supported by the udma66 flavour, you could check the version of the kernel included in the boot-floppies you used, or try the latest release. Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Processed: reassign Re: Bug#79459: UDMA66/HPT370 boot problem
Debian Bug Tracking System wrote: Processing commands for [EMAIL PROTECTED]: reassign 79459 boot-floppies Bug#79459: UDMA66/HPT370 boot problem Bug reassigned from package `disks-i386' to `boot-floppies'. -- Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database) Acording to www.linux-ide.org hpt370 should be supported under the 2.2 series fo kernels, the first patch i see was to 2.2.16, so it should be integrated with anything above that. HPT370 is handled by the HPT370 driver as far as i can tell. Could you please try the latest udma66 flavour of boot-floppies. Thanks Glenn -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Boot problem
Grzegorz Bieszczak [EMAIL PROTECTED] writes: I am trying to install Debian 2.2 r0. While the first boot to start installation system hangs after the line: md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 I was able to install on this computer Redhat 7 and Mandrake 7.2, so the problem seems to be specific to Debian. Well, it's specific to the kernel on the first CD, I'll warrant. Do you have any ideas what's going on? Hardware conflict. Can you say "x86 is a crap architecture"? I suggest you try booting with the 2nd or 3rd CDs, which have kernels more optimized for modern (PCI) hardware. -- ..Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] After an attempt from 2nd CD I got additional message: sim710: No NCR53C710 adapter found. NCR reminds me of SCSI adapter, but I don't have nad SCSI device in my computer. Looks like Debian 2.2 requires a SCSI device to be present in the computer. Strange Greg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Boot problem
On Sun, Dec 17, 2000 at 04:43:49PM +0100, [EMAIL PROTECTED] wrote: Grzegorz Bieszczak [EMAIL PROTECTED] writes: I am trying to install Debian 2.2 r0. While the first boot to start installation system hangs after the line: md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 [...] Hardware conflict. Can you say "x86 is a crap architecture"? I suggest you try booting with the 2nd or 3rd CDs, which have kernels more optimized for modern (PCI) hardware. [...] After an attempt from 2nd CD I got additional message: sim710: No NCR53C710 adapter found. NCR reminds me of SCSI adapter, but I don't have nad SCSI device in my computer. Looks like Debian 2.2 requires a SCSI device to be present in the computer. Strange If you have read the documentation, you would know that there are 4 'flavors' of kernels in Debian. One of them only has drivers for SCSI drives, so you can't boot it on a IDE-only system. Try the idepci flavor. regards Marcin -- Marcin Owsiany [EMAIL PROTECTED] http://student.uci.agh.edu.pl/~porridge/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Boot problem
On Sun, Dec 17, 2000 at 04:07:05PM +0100 , Marcin Owsiany wrote:
On Sun, Dec 17, 2000 at 04:43:49PM +0100, [EMAIL PROTECTED] wrote:
Grzegorz Bieszczak [EMAIL PROTECTED] writes:
I am trying to install Debian 2.2 r0. While the first boot to start
installation system hangs after the line:
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
[...]
Hardware conflict. Can you say "x86 is a crap architecture"?
I suggest you try booting with the 2nd or 3rd CDs, which have kernels
more optimized for modern (PCI) hardware.
[...]
After an attempt from 2nd CD I got additional
message:
sim710: No NCR53C710 adapter found.
never mind. this is kernel autodetection. If you don't have this one, you
can sefely ignore this
NCR reminds me of SCSI adapter, but I don't have
nad SCSI device in my computer. Looks like Debian
2.2 requires a SCSI device to be present in the
computer. Strange
If you have read the documentation, you would know that there
are 4 'flavors' of kernels in Debian. One of them only has
No. The standard one has almost all SCSI drivers, but the others don't.
drivers for SCSI drives, so you can't boot it on a IDE-only
system.
yes, you can.
Petr Cech
--
Debian GNU/Linux maintainer - www.debian.{org,cz}
[EMAIL PROTECTED]
zpx it's amazing how "not-broken" debian is compared to slack and rh
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Boot problem
On Sun, Dec 17, 2000 at 05:45:01PM +0100, Petr Cech wrote: On Sun, Dec 17, 2000 at 04:07:05PM +0100 , Marcin Owsiany wrote: If you have read the documentation, you would know that there are 4 'flavors' of kernels in Debian. One of them only has No. The standard one has almost all SCSI drivers, but the others don't. Right. I don't know what made me think that 'compact' doesn't have IDE drivers. But it does have SCSI drivers, doesn't it? That's why it just hangs on that system. Marcin -- Marcin Owsiany [EMAIL PROTECTED] http://student.uci.agh.edu.pl/~porridge/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: Boot problem
On Sun, Dec 17, 2000 at 10:19:16PM +0100, [EMAIL PROTECTED] wrote: The problem is that I can't even get into installation program to choose kernel. You don't choose the kernel in the installation program. There are four kinds of installation sets, with four different kernels. If you have only one bootable CD, then you will have to write other 'flavor' of the installation system (and thus - kernel) to floppies. Marcin -- Marcin Owsiany [EMAIL PROTECTED] http://student.uci.agh.edu.pl/~porridge/ GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
Grzegorz Bieszczak [EMAIL PROTECTED] writes: I am trying to install Debian 2.2 r0. While the first boot to start installation system hangs after the line: md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8 I was able to install on this computer Redhat 7 and Mandrake 7.2, so the problem seems to be specific to Debian. Well, it's specific to the kernel on the first CD, I'll warrant. Do you have any ideas what's going on? Hardware conflict. Can you say "x86 is a crap architecture"? I suggest you try booting with the 2nd or 3rd CDs, which have kernels more optimized for modern (PCI) hardware. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: UDMA66 boot problem/HPT370
I´m desperate to install debian eventhough it doesn´t seem to work with me.I had Suse installed a year ago, but I don´t want to put up with there funnyrc.config-thingy any more.It seems that my onboard HPT370 controller should be supported on the udma66floppies.I just got unlucky and so it doesn´t work. I already received a few repliesby some other KT7 owners indicating that I´m not alone.I can boot into the setup assistant just fine from the regular 2.2r2 CD, butthen I have no harddisk.There´s an option in the setup menu that lets you load modules from floppy,and I tried loading something from the UDMA66 driver1-4 disks, but then Ionly got an error telling me that the system is unable to mount the floppy(???). Also I´m not so sure if there´s a useful driver on those disksanyhow.When I boot from the udma66 floppies it just stops half way (see descriptionbelow) .I really don´t know what more to do. Maybe I could boot from the CD bysupplying a bunch of boot parameters, describing my disk. So if you have aclue what I (and many others) could do I would really appreciate if you sendme a reply.Under Windows the HPT370 controller(ide2 ide3 ( counting from 0)) seems torun as a scsi device.If you need any information youst ask me.Thanks a lot.Alexander Alexander writes: Sorry no solution from me. I'm faced with a near identical problem usingthe HPT 370 on-board controller with a 2theMax BX7 +100 motherboard(actually with five of them). So I'll be interested to see the solutionif/when you get one. Regards Jon Branch --Original Message-- From: "Alexander Sawallich" [EMAIL PROTECTED] To: debian-user [EMAIL PROTECTED], debian-boot[EMAIL PROTECTED] Sent: December 12, 2000 8:46:46 PM GMT Subject: UDMA66 boot problem/HPT370 When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller,with the UDMA66 boot floppies, the system halts during the boot process.Why? Thnanks for any help. I´m sorry this description got so long, but ifsomeone really wants to help he might need some of the info below. I´m booting debian from the UDMA66 rescue disk. The disk works fine atmy friends computer (Promise UDMA 66 onboard) and I tried several ones withthe same result. When I boot from the Debian 2.2r2 CD I can successfully load the kerneland get into the install menu, but I have no harddisk detected. I triedloading modules from the UDMA66 driver1-4 disks but then I receive an errormessage saying : "Unable to mount disk". I also tried booting the UDMA flavor from DOS (loadlin) but then Ireceive the exact same result as shown below. If someone knows some really good boot parameters (and exact use) thatwill get my HPT370 controller to work with the standard flavor, that mightalso help. Those are the last boot messages I received. The earlier ones seemedunimportant. RAM disk driver initialized: 16 RAM disks of 16384K size loop: registered device at major 7 Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override withidebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 16 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:7.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda: DMA, hdb: DMA HPT370: IDE controller on PCI bus 00 dev 98 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xe400-0xe407, BIOS settings: hde: DMA, hdf: pio ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg: pio, hdh: pio hda: CDR-8482B, ATAPI CDROM DRIVE hdb: R/RW 4x4x24, ATAPI CDROM DRIVE ide: Assuming 33MHz system bus speed for PIO modes; override withidebus=xx This is were the system stops working. Nothing happens from here on. At a friends computer the last line was followed by some lines referringto his harddrive : Maxtor ... 512K cache ... I already tried adding idebus=33 as a boot parameter, but the systemjust stopped one line earlier. I´m not running a raid array. I just connected my one and only harddriveto the HPT370 controller to take advantage of the UDMA100 burst speed. I had the second ide channel (ide1) disabled in the BIOS in case someonewondered. Here´s a summary of my system Athlon TB 900 Abit KT7-Raid Motherboard IBM DTLA 307030 30GB UDMA100 harddrive connected to HPT370 onboard Raid controller (ide2 master) 128MB PC133 SDRAM Soundblaster PCI 128 Geforce II MX 32MB AGP video card SMC 1211TX EZ-Card - PCI network card USB Mouse Thanks a lot. If you are reading this line, I know that you tried. Alexander --- FREE! The World's Best Email Address @email.com Reserve your name now at http://www.email.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact[EMAIL PROTECTED]
UDMA66 boot problem /HPT370
When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller, with the UDMA66 boot floppies, the system halts during the boot process. Why? Thnanks for any help. I´m sorry this description got so long, but if someone really wants to help he might need some of the info below. I´m booting debian from the UDMA66 rescue disk. The disk works fine at my friends computer (Promise UDMA 66 onboard) and I tried several ones with the same result. When I boot from the Debian 2.2r2 CD I can successfully load the kernel and get into the install menu, but I have no harddisk detected. I tried loading modules from the UDMA66 driver1-4 disks but then I receive an error message saying : "Unable to mount disk". I also tried booting the UDMA flavor from DOS (loadlin) but then I receive the exact same result as shown below. If someone knows some really good boot parameters (and exact use) that will get my HPT370 controller to work with the standard flavor, that might also help. Those are the last boot messages I received. The earlier ones seemed unimportant. ... RAM disk driver initialized: 16 RAM disks of 16384K size loop: registered device at major 7 Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 16 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:7.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda: DMA, hdb: DMA HPT370: IDE controller on PCI bus 00 dev 98 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xe400-0xe407, BIOS settings: hde: DMA, hdf: pio ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg: pio, hdh: pio hda: CDR-8482B, ATAPI CDROM DRIVE hdb: R/RW 4x4x24, ATAPI CDROM DRIVE ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx This is were the system stops working. Nothing happens from here on. At a friends computer the last line was followed by some lines referring to his harddrive : Maxtor ... 512K cache ... I already tried adding idebus=33 as a boot parameter, but the system just stopped one line earlier. I´m not running a raid array. I just connected my one and only harddrive to the HPT370 controller to take advantage of the UDMA100 burst speed. I had the second ide channel (ide1) disabled in the BIOS in case someone wondered. Here´s a summary of my system Athlon TB 900 Abit KT7-Raid Motherboard IBM DTLA 307030 30GB UDMA100 harddrive connected to HPT370 onboard Raid controller (ide2 master) 128MB PC133 SDRAM Soundblaster PCI 128 Geforce II MX 32MB AGP video card SMC 1211TX EZ-Card - PCI network card USB Mouse Thanks a lot. If you are reading this line, I know that you tried. Alexander udma66.doc
UDMA66 boot problem/HPT370
When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller, with the UDMA66 boot floppies, the system halts during the boot process. Why? Thnanks for any help. I´m sorry this description got so long, but if someone really wants to help he might need some of the info below. I´m booting debian from the UDMA66 rescue disk. The disk works fine at my friends computer (Promise UDMA 66 onboard) and I tried several ones with the same result. When I boot from the Debian 2.2r2 CD I can successfully load the kernel and get into the install menu, but I have no harddisk detected. I tried loading modules from the UDMA66 driver1-4 disks but then I receive an error message saying : "Unable to mount disk". I also tried booting the UDMA flavor from DOS (loadlin) but then I receive the exact same result as shown below. If someone knows some really good boot parameters (and exact use) that will get my HPT370 controller to work with the standard flavor, that might also help. Those are the last boot messages I received. The earlier ones seemed unimportant. ... RAM disk driver initialized: 16 RAM disks of 16384K size loop: registered device at major 7 Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 16 VP_IDE: not 100% native mode: will probe irqs later VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:7.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda: DMA, hdb: DMA HPT370: IDE controller on PCI bus 00 dev 98 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xe400-0xe407, BIOS settings: hde: DMA, hdf: pio ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg: pio, hdh: pio hda: CDR-8482B, ATAPI CDROM DRIVE hdb: R/RW 4x4x24, ATAPI CDROM DRIVE ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx This is were the system stops working. Nothing happens from here on. At a friends computer the last line was followed by some lines referring to his harddrive : Maxtor ... 512K cache ... I already tried adding idebus=33 as a boot parameter, but the system just stopped one line earlier. I´m not running a raid array. I just connected my one and only harddrive to the HPT370 controller to take advantage of the UDMA100 burst speed. I had the second ide channel (ide1) disabled in the BIOS in case someone wondered. Here´s a summary of my system Athlon TB 900 Abit KT7-Raid Motherboard IBM DTLA 307030 30GB UDMA100 harddrive connected to HPT370 onboard Raid controller (ide2 master) 128MB PC133 SDRAM Soundblaster PCI 128 Geforce II MX 32MB AGP video card SMC 1211TX EZ-Card - PCI network card USB Mouse Thanks a lot. If you are reading this line, I know that you tried. Alexander
Processed: reassign Re: Bug#79459: UDMA66/HPT370 boot problem
Processing commands for [EMAIL PROTECTED]: reassign 79459 boot-floppies Bug#79459: UDMA66/HPT370 boot problem Bug reassigned from package `disks-i386' to `boot-floppies'. -- Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: reassign, hmmmm Re: Bug#79092: boot problem
Processing commands for [EMAIL PROTECTED]: reassign 79092 boot-floppies Bug#79092: boot problem Bug reassigned from package `boot -cd' to `boot-floppies'. -- Stopping processing here. Please contact me if you need assistance. Darren Benham (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Need some serious help with a Linux Boot Problem
Hello... My name is Darshan and I was broswing the web for a solution to my problem, when I came across a message board, which had your email addresses. I have a Pentium III 500 in which I have 2 operating systems. I have partioned my drives and I am running windows 98 as my mine and linux 7.0 as well. Everything was running perfectly fine. I had copied the loadlin.exe file and vmlinuz file to my C: directory in windows...so that when i reboot the computer into dos... i type the following command and it take me into linux... loadlin vmlinuz root=dev/hda3 everything worked fine until today...i get the following as an error...please give me some advice and a solution if possible...thanks Kernel panic : VFS : Unable to mount root fs on 00:de that is the message i get...please email me ASAP...thanks _ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot problem
n Fri 03 Nov, Tim Veazey wrote: Hello, I've just attempted to install debian for the first time (new to the linux world too). The installation seems to go ok. However, when it comes time to reboot, the system freezes after the following boot message: "Setting the System Clock using the Hardware Clock as a reference..." Anyone have any ideas? Thanks very much for your help. You don't say what system you are installing on, but this always happen if you install 2.2r0 on a riscPC (ARM) for example. Hit ctrl-C to get past this point. Then do update-rc.d hwclock remove to stop it happening every time (it will also hang on shutdown) We have done a new util dpkg-platform which can be used in scripts like hwclock to stop it running on platforms where it is broken. However this isn't in the main distribution yet until there is agreement about how the platforms are to managed in this respect. (Contact Chris rutter for details on how this is prgressing). Updated util-linux and debianutils packages to fix this problem are included in our (Aleph One's) ARM 2.2r0 unofficial debian distribution. Wookey -- Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel (00 44) 1223 811679 work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
boot problem
Hello, I've just attempted to install debian for the first time (new to the linux world too). The installation seems to go ok. However, when it comes time to reboot, the system freezes after the following boot message: "Setting the System Clock using the Hardware Clock as a reference..." The only other messages I see the loos like they might be errors are: modprobe: insmod * failed ...and... Mounting local filesystems... not mounted anything I've tried installing with and without the options "Set system clock to GMT". Anyone have any ideas? Thanks very much for your help. Sincerely, Tim Veazey Linux Newbie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: boot problem
Tim Veazey wrote: Hello, I've just attempted to install debian for the first time (new to the linux world too). The installation seems to go ok. However, when it comes time to reboot, the system freezes after the following boot message: "Setting the System Clock using the Hardware Clock as a reference..." The only other messages I see the loos like they might be errors are: modprobe: insmod * failed ...and... Mounting local filesystems... not mounted anything I've tried installing with and without the options "Set system clock to GMT". Anyone have any ideas? Thanks very much for your help. Sincerely, Tim Veazey Linux Newbie This wouldn't happen to be an install on a Macintosh Quadra 950 would it? If so just hit Ctrl-C when you get the message and the system will continue booting. After you log in as root go to the init.d directory and comment out the hwclock lines in hwclock.sh hwclock is broken for use on the Quadra 950. -- Ray Knight [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
HD BOOT PROBLEM
Hi! I've performed a standard installation with Debian 2.2. MBR installed /dev/hda (/boot mounted on /dev/hda1 which is 100MB) PC with Amibios v1.5 1995-12-19, Pentium 133, Disk 1,2GB and I have the following messages which appears (not the same message at each reboot, random..which is very stange!!.) LILO Loading Linux... Uncompressing Linux... OR LILO Loading Linux... Uncompressing Linux... crc error -- System halted OR LILO Loading Linux... Uncompressing Linux... Out of memory -- System halted Linux boots fine from "custom-boot" floppy which is saved by during Debian install process. Can somebody help me... Thanks Marc Prokop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Boot Problem
"Adam" == Adam Di Carlo [EMAIL PROTECTED] writes: Adam Sorry we haven't been able to help you here. Adam The only time I've heard of another reporting this problem, it was bad Adam memory in the machine. You might try a memory scrubber. Adam This is a hardware/kernel problem -- not much we can do about it in Adam this group. Why was I CC'd? I did not see the conversation; I've been off-list because of time constraints. Is it sig 11 (segv) problems? That's most often the CPU overheating. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Boot Problem
Sorry we haven't been able to help you here. The only time I've heard of another reporting this problem, it was bad memory in the machine. You might try a memory scrubber. This is a hardware/kernel problem -- not much we can do about it in this group. -- .Adam Di [EMAIL PROTECTED]URL:http://www.onShore.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#68946: Boot problem
Package: boot-floppies Version: 2.1.8-1999-02-22 architecture: i386 model: Systemax, Athlon 550Mhz memory:128MB scsi: None cd-rom:ATAPI*2 network card: None pcmcia:None During intallation boot, my system hangs. The last kernal message is: md driver 0.36.3 MAX_MD_DEV=4, MAX_REAL=8 I have tried the following with no success - booting from CD, from DOS, from floppy - removing my modem, sound card, network card - disabling the second CD drive with "hdd=none" Please can you help?? Many thanks Adam = - Adam Shepherd [EMAIL PROTECTED] Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Boot Problem
Hi Guys, We are having a problem getting Linux to boot on an Industrial Computer Source SB586P(V) Rev(C) computer board. The SB586 has a 100 Mhz Pentium and uses American Megatrent BIOS (1994, the latest version for this board). The system has 30 meg of main memory and is using the on-board Adaptec aic78xx v1.2 SCSI Controller with a Seagate Barracuda ST 32550N drive. We are using "Installing Debian GNU/Linux 2.2 for Intel x86" version 2.2.15 dated 24 May, 2000 as a guide. The Linux version is Potatoe and the file date is 6/7/2000 4:18pm. When the system boots, the Linux opening screen appears - when we begin the installation, as soon as the load process begins, we see "Lo" (a quick flash, so I'm not sure) and the system immediately re-boots. We have tried various combinations of BIOS settings and Linux load options parameters with no change in symptoms. I'd appreciate any help you can give. Thanks, Brit Rothrock [EMAIL PROTECTED] 617-476-8905 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
