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
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]
(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]
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]
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]
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]
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
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]
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]
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]
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]
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: 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]
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]
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]
