Re: passwörter (war: boot problem: woody, IDE to CF adapter, lilo error 80)
Am Mittwoch, den 16.02.2005, 10:17 +0100 schrieb Tobias Kraus: [...] Hab mal das gleiche Problem gehabt (hab aber HD-HD kopiert). Gelöst hab ich es, indem ich auf der neuen Platte die lilo.conf für das endgültige System konfiguriert habe (boot=/dev/hda, s.o.) und sie auf primary/master (hda) konfiguriert hab. Anschließend hab ich mit der Woody-CD und (IIRC) bf24 root=/dev/hda1 oder rescbf24 root=/dev/hda1 gebootet (war damals natürlich eine Woody-System). Dann ist das System mit dem CD-Kernel von meiner Root-Partition gelaufen. Ein anschließender lilo-Aufruf hat mir den bootloader richtig installiert. Super - danke, das hat funktioniert. Leider kann ich mich im System nicht einloggen, keines der Passwörter wird akzeptiert. Hab ich da beim rsync etwas falsch gemacht? rsync --verbose --stats -e ssh --exclude=smbshare \ -azH [EMAIL PROTECTED]::all /mnt/CF/ wobei hier all im rysncd für das / Verzeichnis festgelegt wurde. lG Manfred -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
boot problem: woody, IDE to CF adapter, lilo error 80
Hallo,
ich versuche gerade die Festplatte in meinem Heimrouter mit einer CF
Speicherkarte zu ersetzen. Dazu verwende ich einen IDE-CF Adapter den
man direkt auf das Motherboard stecken kann.
Das gute ist, die CF Karte wird erkannt:
hdparm -i /dev/hdc
/dev/hdc:
Model=SanDisk SDCFB-512, FwRev=Rev 0.00, SerialNo=X0107 20040519080929
Config={ HardSect NotMFM Removeable DTR10Mbs nonMagnetic }
RawCHS=993/16/63, TrkSize=0, SectSize=528, ECCbytes=4
BuffType=DualPort, BuffSize=1kB, MaxMultSect=1, MultSect=off
CurCHS=993/16/63, CurSects=1000944, LBA=yes, LBAsects=1000944
IORDY=no, tPIO={min:120,w/IORDY:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes:
AdvancedPM=no
Drive Supports : Reserved : ATA-10
Jetzt habe ich ganz einfach die Daten von der Originalplatte mit rsync
auf die CF Karte kopiert und chroot / lilo gemacht.
lilo.conf:
# Support LBA for large hard disks.
lba32
# Specifies the boot device. This is where Lilo installs its boot
boot=/dev/hdc
# Specifies the device that should be mounted as root. (`/')
root=/dev/hda1
install=/boot/boot-menu.b
# Specifies the location of the map file
map=/boot/map
# Specifies the number of deciseconds (0.1 seconds) LILO should
delay=20
# Specifies the VGA text mode at boot time.
vga=normal
# Kernel command line options that apply to all installed images go
append=apm=off acpi=force
# Boot up Linux by default.
default=Linux
image=/vmlinuz
label=Linux
read-only
Lilo wird ohne Fehler installiert, wenn ich aber nun den CF-Adapter mit
der Karte auf IDE Kanal 1 umstecke, kommt es beim booten zum Fall dass
Lilo wiederholt 80 80 80 80 80 80 80 80 usw schreibt und hängen bleibt.
Nun habe ich nicht wirklich herausfinden können was den Fehler bewirkt,
außer dass es ein Timing Problem am IDE Interface das Probelm sein
könnte. Ist in der lilo.conf etwas falsch?
Auf der CF-Karte ist ein ext2 Filesystem, Kernel 2.4.27
lG Manfred
--
Haeufig gestellte Fragen und Antworten (FAQ):
http://www.de.debian.org/debian-user-german-FAQ/
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: boot problem: woody, IDE to CF adapter, lilo error 80
Am Mittwoch, 16. Februar 2005 10:01 schrieb Manfred Sampl: Hallo, ich versuche gerade die Festplatte in meinem Heimrouter mit einer CF Speicherkarte zu ersetzen. Dazu verwende ich einen IDE-CF Adapter den man direkt auf das Motherboard stecken kann. [...] Jetzt habe ich ganz einfach die Daten von der Originalplatte mit rsync auf die CF Karte kopiert und chroot / lilo gemacht. lilo.conf: # Support LBA for large hard disks. lba32 # Specifies the boot device. This is where Lilo installs its boot boot=/dev/hdc ^ (s.u.) # Specifies the device that should be mounted as root. (`/') root=/dev/hda1 install=/boot/boot-menu.b # Specifies the location of the map file map=/boot/map # Specifies the number of deciseconds (0.1 seconds) LILO should delay=20 # Specifies the VGA text mode at boot time. vga=normal # Kernel command line options that apply to all installed images go append=apm=off acpi=force # Boot up Linux by default. default=Linux image=/vmlinuz label=Linux read-only Lilo wird ohne Fehler installiert, wenn ich aber nun den CF-Adapter mit der Karte auf IDE Kanal 1 umstecke, kommt es beim booten zum Fall dass Lilo wiederholt 80 80 80 80 80 80 80 80 usw schreibt und hängen bleibt. Hab mal das gleiche Problem gehabt (hab aber HD-HD kopiert). Gelöst hab ich es, indem ich auf der neuen Platte die lilo.conf für das endgültige System konfiguriert habe (boot=/dev/hda, s.o.) und sie auf primary/master (hda) konfiguriert hab. Anschließend hab ich mit der Woody-CD und (IIRC) bf24 root=/dev/hda1 oder rescbf24 root=/dev/hda1 gebootet (war damals natürlich eine Woody-System). Dann ist das System mit dem CD-Kernel von meiner Root-Partition gelaufen. Ein anschließender lilo-Aufruf hat mir den bootloader richtig installiert. HTH, Tobias PS: Wenns funktioniert, schreib doch bitte eine kurze Erfolgsmeldung. Interessiere mich auch für solch eine Konstruktion! Nun habe ich nicht wirklich herausfinden können was den Fehler bewirkt, außer dass es ein Timing Problem am IDE Interface das Probelm sein könnte. Ist in der lilo.conf etwas falsch? Auf der CF-Karte ist ein ext2 Filesystem, Kernel 2.4.27 lG Manfred -- Diese Email-Adresse dient nur als Spam-Ziel. Nachrichten an diese Adresse werden nicht gelesen! This email address is a spam-tarpit. Mails sent to this address are not read!
Boot problem with a moved ext3 partition
Hi, I have a laptop with windows XP and Debian sarge, the boot is from windows XP. I've transformed the debian ext3 partion in an extended partition with inside the orginal partition (I've used Partion Magic 8.0). The operation terminated with success and then I generated a new linux.bin to boot debian from windows but it doesn't work (on the screen appears only GRUB). I think that the ext3 partition is ok beacouse I can browse it with partition magic and if I boot with the debian CD I can mount (I found it in /dev/disks/ide1/part5) and browse it. Besides e2fsck doesn't report any error. With the debian CD (sarge 20040429) I tried to use the partition manager specifying to use the existent partition ext3 but I've the following messages: 1 - Filesystem was not cleany unmounted! you should e2fsck. Modifying an unclean filesystem could cause severe corruption (I press continue because I run e2fsck without error) 2 - This ext2 filesystem has a rather strange layout! Ported can't resize this (yet) 3 - The test of the filesystem with type ext3 in partition #5 of IDE1 master found uncorrect errors. If you don't go back to the partitioning menu and correct these errors the partition will not be used at all. What can be the problem? The extended partion I made with partition magic? An utility for windows, bootparts, sees it as type=f (Win95 XInt 13 extended), size= 36162315 KB, Lba Pos=44885610. The ext3 was wrongly moved by partion magic? But than how can I mount and use it! The boot sector of the ext3 partion was corrupted and than GRUB doesn't work? In this case, how can I repair it? Thanks a lot. Giannandrea -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem with a moved ext3 partition
High, On 28 Dec 2004, jean wrote: Hi, I have a laptop with windows XP and Debian sarge, the boot is from windows XP. I've transformed the debian ext3 partion in an extended partition with inside the orginal partition (I've used Partion Magic 8.0). The operation terminated with success and then I generated a new linux.bin to boot debian from windows but it doesn't work (on the screen appears only GRUB). I assume you reconfigured GRUB with 'root (hd0,4)' 'setup (hd0)'? I think that the ext3 partition is ok beacouse I can browse it with partition magic and if I boot with the debian CD I can mount (I found it in /dev/disks/ide1/part5) and browse it. Besides e2fsck doesn't report any error. With the debian CD (sarge 20040429) I tried to use the partition manager specifying to use the existent partition ext3 but I've the following messages: 1 - Filesystem was not cleany unmounted! you should e2fsck. Modifying an unclean filesystem could cause severe corruption (I press continue because I run e2fsck without error) 2 - This ext2 filesystem has a rather strange layout! Ported can't resize this (yet) 3 - The test of the filesystem with type ext3 in partition #5 of IDE1 master found uncorrect errors. If you don't go back to the partitioning menu and correct these errors the partition will not be used at all. What can be the problem? The extended partion I made with partition magic? An utility for windows, bootparts, sees it as type=f (Win95 XInt 13 extended), size= 36162315 KB, Lba Pos=44885610. This is wrong. The partition type should be Linux. Run fdisk and change the partition type. The ext3 was wrongly moved by partion magic? But than how can I mount and use it! Are you sure the number of blocks is still the same as it was before moving? The boot sector of the ext3 partion was corrupted and than GRUB doesn't work? In this case, how can I repair it? First change the partition type to Linux. Does e2fsck run properly now? Then edit /boot/grub/menu.lst to your new settings, something like: title Debian GNU/Linux, kernel 2.6.10 root(hd0,4) --- this is your extended partition kernel /boot/vmlinuz-2.6.10 root=/dev/hda5 ro --- idem. savedefault Also check your XP record (I don't run windoze, so I can't help you with that one). Then run grub and type: root (hd0,4) setup (hd0) and see if you are able to boot again. Greetz, Sebas -- English written by Dutch people is easily recognized by the improper use of 'In principle ...' The software box said 'Requires Windows 95 or better', so I installed Linux. Als Pacman in de jaren '80 de kinderen zo had be?nvloed zouden nu veel jongeren rondrennen in donkere zalen terwijl ze pillen eten en luisteren naar monotone electronische muziek. (Kristian Wilson, Nintendo, 1989) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot-Problem mit LILO je nach Default-Image
Baltasar Cevc schrieb am Donnerstag, 16. Dezember 2004 21:40: Tausche ich nun in der lilo.conf die beiden Eintraege, startet der Server nur noch, wenn das normale Image per Hand gewaehlt wird (Reboot mit einem best. Image bietet der Provider kostenlos an). Was verstehst Du unter Einträge tauschen? Gruß Chris -- This message was ROT-13 encrypted twice for extra security. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Boot-Problem mit LILO je nach Default-Image
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, ich habe ein sehr komisches Problem auf einem gemieteten Server (d.h. ich kann leider die Meldungen nicht sehen, wenn der Rechner nicht hochkommt). Und zwar: ich habe zwei Kernelimages (2.6.9 normal und 2.6.9 mit vserver-patch). Lilo-Einstellung 1 ist, dass der Rechner automatisch das normale Image hochfaehrt. Das laeuft soweit. Rufe ich lilo -R vserver vor dem Neustart auf, kommt der Rechner erfolgreich mit dem vserver-kernel hoch. Tausche ich nun in der lilo.conf die beiden Eintraege, startet der Server nur noch, wenn das normale Image per Hand gewaehlt wird (Reboot mit einem best. Image bietet der Provider kostenlos an). In den Log-Files tauchen von den boots, die Fehlschlagen keinerlei Eintraege auf. Hat jemand Ideen, in welcher Richtung das Problem zu suchen sein koennte? Wuerde mich sehr ueber Hinweise jeder Art freuen, bin am Ende meines ABC angelangt... Danke und liebe Gruesse aus dem nebelig-kalten Regensburg, Baltasar -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBwfJJp2YsmzTbIwYRAga3AJ4q5iKWFlAVXljdszoIBEIIdqquegCeOKrp E1Y3hXZ/WhqouogEVrTO0OI= =RO2a -END PGP SIGNATURE- -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Boot problem: Hang up on synchronising system clock to hardware clock
On a machine we recently installed (testing) we have this problem at boot Hang up on synchronising system clock to hardware clock Then if you Ctrl + C the boot procedure goes ahead. It stops again with the same message. If you Ctrl + C again, the boot procedure goes ahead successfully and completes. Any solution? Thanks in advance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot-Problem mit USB-Stick
Klaus Becker [u] wrote on 10/11/2004 19:19: auf meinem USB-Stick hab' ich Feather-Linux (eine Miniversion von Knoppix) installiert und versuche, es mit folgendem Eintrag in grub zu starten: title feather-usbstick kernel (sd0,0)/boot/vmlinuz-2.4.26 root=/dev/sda1 read-only acpi=off initrd (sd0,0)/boot/initrd.gz Grub beschwert sich: error 23: Error while parsing number. Der Stick entspricht sehr wohl /dev/sda1 und besitzt nur eine Partition. Was ist da falsch? Öhm, kann grub überhaupt USB-Devices ansprechen? Wenn ja, tut er das tatsächlich als SCSI-Device? Abschnitt 4.5 von http://www.freewebs.com/tsj/bootingUSB_ldp_v0.1.htm lässt mich vermuten, dass GRUB sehr wohl mit USB-Disks kann, sie aber als hd(x,y) und nicht als sd(x,y) anspricht, also nach den internen Harddiscs einsortiert. cu, sven -- Pinguine können ja bekanntlich nicht fliegen und stürzen deshalb auch nicht ab. RTL-Nachtjournal über Linux, 29.10.2004 -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Boot-Problem mit USB-Stick
n'Abend, auf meinem USB-Stick hab' ich Feather-Linux (eine Miniversion von Knoppix) installiert und versuche, es mit folgendem Eintrag in grub zu starten: title feather-usbstick kernel (sd0,0)/boot/vmlinuz-2.4.26 root=/dev/sda1 read-only acpi=off initrd (sd0,0)/boot/initrd.gz Grub beschwert sich: error 23: Error while parsing number. Der Stick entspricht sehr wohl /dev/sda1 und besitzt nur eine Partition. Was ist da falsch? schönen Abend Klaus
Re: Boot-Problem mit USB-Stick
hi, ich weiß ja nicht, kann mir aber kaum vorstellen das das so gehen könnte. wenn du von usb-stick booten willst mußt du das schon im bios einstellen. behaupte ich jetzt einfach mal... Klaus Becker wrote: n'Abend, auf meinem USB-Stick hab' ich Feather-Linux (eine Miniversion von Knoppix) installiert und versuche, es mit folgendem Eintrag in grub zu starten: title feather-usbstick kernel (sd0,0)/boot/vmlinuz-2.4.26 root=/dev/sda1 read-only acpi=off initrd (sd0,0)/boot/initrd.gz Grub beschwert sich: error 23: Error while parsing number. Der Stick entspricht sehr wohl /dev/sda1 und besitzt nur eine Partition. Was ist da falsch? schönen Abend Klaus -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Boot-Problem mit USB-Stick
Klaus Becker wrote: n'Abend, auf meinem USB-Stick hab' ich Feather-Linux (eine Miniversion von Knoppix) installiert und versuche, es mit folgendem Eintrag in grub zu starten: title feather-usbstick kernel (sd0,0)/boot/vmlinuz-2.4.26 root=/dev/sda1 read-only acpi=off initrd (sd0,0)/boot/initrd.gz Grub beschwert sich: error 23: Error while parsing number. Der Stick entspricht sehr wohl /dev/sda1 und besitzt nur eine Partition. Was ist da falsch? Hm das mainboard kann nich von usb booten.. (ne wilde vermutung ins blaue) hth wali -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
big boot problem with sid i-386 installer
Hello, I got into trouble with booting windows xp os after installed debian with current sid net-installer. First,I installed win xp pro in /dev/hda1, then installed debian with sid net-installer, and partitioned for linux with installer, everything went well.But after rebooted ,grub just couldn't recognize the NTFS partition and wouldn't boot the windows xp. Even worse,i couldn't install xp with windows xp cd again, xp installation can't merge the grub,so i couldn't proceed. So i think there might be some thing wrong with the installer 's partition program. But I really don't want to wast time on installation from scratch. HOW CAN I FIX THIS PROBLEM? Thanks in advance! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: big boot problem with sid i-386 installer
Hi, First,I installed win xp pro in /dev/hda1, then installed debian with sid net-installer, and partitioned for linux with installer, everything went well.But after rebooted ,grub just couldn't recognize the NTFS partition and wouldn't boot the windows xp. Even worse,i couldn't install xp with windows xp cd again, xp installation can't merge the grub,so i couldn't proceed. You would really help us help you solve the problem if you could post 1) The error grub generates when he doesn't recognize the NFTS partition 2) Your grub configuration ( /boot/menu/grub.lst on my debian testing) My guess would be problems arise because grub is not in /dev/hda1, but I'm not sure if that really is (or should be) a problem. Ciao, Dan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: big boot problem with sid i-386 installer
On (13/10/04 14:38), Dan Roozemond wrote: Hi, First,I installed win xp pro in /dev/hda1, then installed debian with sid net-installer, and partitioned for linux with installer, everything went well.But after rebooted ,grub just couldn't recognize the NTFS partition and wouldn't boot the windows xp. Even worse,i couldn't install xp with windows xp cd again, xp installation can't merge the grub,so i couldn't proceed. You would really help us help you solve the problem if you could post 1) The error grub generates when he doesn't recognize the NFTS partition 2) Your grub configuration ( /boot/menu/grub.lst on my debian testing) My guess would be problems arise because grub is not in /dev/hda1, but I'm not sure if that really is (or should be) a problem. It would also be useful to see the partition table grub boots from the mbr usually seen in the menu.lst as: # groot=(hd0,0) (the first partition on the first disk) grub will look for the kernel options where grub is installed - normally the root partition of your debian install - ie. which ever partition is / as follows: # kopt=root=/dev/hdaX ro (X = partition number) and your windows system should appear in menu.lst like this: # This entry automatically added by the Debian installer for a non-linux # OS on /dev/hda1 title Windows 95/98/Me root(hd0,0) savedefault makeactive chainloader +1 Regards Clive -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: big boot problem with sid i-386 installer
Please do not send private replies, reply only to the list # This entry automatically added by the Debian installer for a non-linux OS # on /dev/hda1 title Windows NT/2000/XP root(hd0,0) makeactive chainloader +1 In my gentoo grub config (that's the only linux I have together with windows XP) it says # Windows title=Windows XP root (hd0,0) chainloader (hd0,0)+1 So that sort of matches your configuration. I still find it rather strange that Windows XP won't reinstall. I'm pretty sure there is a utility called 'FIXMBR' which fixes the master boot record (as you would kinda expect) to boot to windows. You should be able to access it via the rescue disks (which you of course created when installing windows), or the installation cd. However, be warned that it might then be hard to get into your debian system again... Dan
Dual Boot Problem
I'm trying to install Debian Sarge stable as a second operating system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Also note, I'm running Woody at work no problem, but when I try to install Woody at home, the natsumi driver does not work for my Netgear ethernet card - and therefore cannot complete the installation. patrick- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Also note, I'm running Woody at work no problem, but when I try to install Woody at home, the natsumi driver does not work for my Netgear ethernet card - and therefore cannot complete the installation. patrick- What version of windoze? What does the rest of the partion table look like? How have you tried to setup the linux partitions? RRP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
Partition 1: 35g - Windows XP (ick - for my wife kids) Partition 2: 1g - / Partition 3: 1g - Swap Partition 4: 500m - /tmp Partition 5: 5g - /var Partition 6: 75g - /usr Partition 7: 20g - /home RRPotratz wrote: Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Also note, I'm running Woody at work no problem, but when I try to install Woody at home, the natsumi driver does not work for my Netgear ethernet card - and therefore cannot complete the installation. patrick- What version of windoze? What does the rest of the partion table look like? How have you tried to setup the linux partitions? RRP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
The strange one about this is that to restore the mbr in xp you are supposed to boot from the xp intallation cd, select recovery console and then run fix mbr and fix boot (might be fixmbr and fixboot, with no spaces) I wonder what fdisk /mbr did? Is partion 1 Fat32 or ntfs? RRP Patrick Moroney wrote: Partition 1: 35g - Windows XP (ick - for my wife kids) Partition 2: 1g - / Partition 3: 1g - Swap Partition 4: 500m - /tmp Partition 5: 5g - /var Partition 6: 75g - /usr Partition 7: 20g - /home RRPotratz wrote: Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Also note, I'm running Woody at work no problem, but when I try to install Woody at home, the natsumi driver does not work for my Netgear ethernet card - and therefore cannot complete the installation. patrick- What version of windoze? What does the rest of the partion table look like? How have you tried to setup the linux partitions? RRP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
After wiping out the debian partitions with debian's fdisk, I tried the XP installation cd - followed it's instructions, it failed I lost everything on the harddrive. Using debians fdisk to mark the windows partition as bootable got the thing going again. Partition 1 is ntfs. fdisk /mbr clears the boot loader off the mbr. This one definitely has me scratching my head . . . RRPotratz wrote: The strange one about this is that to restore the mbr in xp you are supposed to boot from the xp intallation cd, select recovery console and then run fix mbr and fix boot (might be fixmbr and fixboot, with no spaces) I wonder what fdisk /mbr did? Is partion 1 Fat32 or ntfs? RRP Patrick Moroney wrote: Partition 1: 35g - Windows XP (ick - for my wife kids) Partition 2: 1g - / Partition 3: 1g - Swap Partition 4: 500m - /tmp Partition 5: 5g - /var Partition 6: 75g - /usr Partition 7: 20g - /home RRPotratz wrote: Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Also note, I'm running Woody at work no problem, but when I try to install Woody at home, the natsumi driver does not work for my Netgear ethernet card - and therefore cannot complete the installation. patrick- What version of windoze? What does the rest of the partion table look like? How have you tried to setup the linux partitions? RRP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
http://kerneltrap.org/node/view/970 Has a good discussion about this with some possible fixes. It would be intresting to learn what ends up working. If that doesn't work? http://marc.free.net.ph/message/20040428.024535.b600e7e7.html RRP Patrick Moroney wrote: After wiping out the debian partitions with debian's fdisk, I tried the XP installation cd - followed it's instructions, it failed I lost everything on the harddrive. Using debians fdisk to mark the windows partition as bootable got the thing going again. Partition 1 is ntfs. fdisk /mbr clears the boot loader off the mbr. This one definitely has me scratching my head . . . RRPotratz wrote: The strange one about this is that to restore the mbr in xp you are supposed to boot from the xp intallation cd, select recovery console and then run fix mbr and fix boot (might be fixmbr and fixboot, with no spaces) I wonder what fdisk /mbr did? Is partion 1 Fat32 or ntfs? RRP Patrick Moroney wrote: Partition 1: 35g - Windows XP (ick - for my wife kids) Partition 2: 1g - / Partition 3: 1g - Swap Partition 4: 500m - /tmp Partition 5: 5g - /var Partition 6: 75g - /usr Partition 7: 20g - /home RRPotratz wrote: Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Also note, I'm running Woody at work no problem, but when I try to install Woody at home, the natsumi driver does not work for my Netgear ethernet card - and therefore cannot complete the installation. patrick- What version of windoze? What does the rest of the partion table look like? How have you tried to setup the linux partitions? RRP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
On Wed, Sep 08, 2004 at 10:18:45AM -0400, Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating Sarge is not yet stable---still testing system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 What kernel? Self compiled or from installation? What are your lilo/grub lines to the kernel? Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian Ok, I understand fixing the MBR to boot XP again, but why rm debian? I don't understand this problem. It is sufficient to just restore the MBR and mark windows as bootable. partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Why not just boot from a rescue disk (I think most/all install disks can be used as rescue disks also--check the boot options) and fix the lilo install so you can boot windows also? This at least fixes your boot options until you figure out the debian install problem. Alternately, I think XP allows you to create a boot menu that will boot another OS in its own partition (never tried this so can't vouch for how well it works). HTH -- Chris Harris [EMAIL PROTECTED] --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
CW Harris wrote: On Wed, Sep 08, 2004 at 10:18:45AM -0400, Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating Sarge is not yet stable---still testing --Understood - but I've successfully installed other machines. system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 What kernel? Self compiled or from installation? What are your lilo/grub lines to the kernel? --Whatever kernel with Sarge stable. --The kernel is from the installation - no customization --As far as lilo lines, I never get to boot into linux to see the lilo lines. I really don't want to use grub. Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian Ok, I understand fixing the MBR to boot XP again, but why rm debian? I don't understand this problem. It is sufficient to just restore the MBR and mark windows as bootable. --I remove debian for 2 reasons - to restore the PC to at least a functional windoze box. Also, I figure I did something wrong - maybe a fresh install will help - the whole process only takes 20 minutes - better safe than sorry. partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Why not just boot from a rescue disk (I think most/all install disks can be used as rescue disks also--check the boot options) and fix the lilo install so you can boot windows also? This at least fixes your boot options until you figure out the debian install problem. --Will do with regard to the rescue option - I'll look at the boot options. But pretty sure I tried this . . . Alternately, I think XP allows you to create a boot menu that will boot another OS in its own partition (never tried this so can't vouch for how well it works). --I basically would trust anything windoze - I'd rather Lilo control the booting. --pm HTH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
Patrick Moroney wrote: CW Harris wrote: On Wed, Sep 08, 2004 at 10:18:45AM -0400, Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating Sarge is not yet stable---still testing --Understood - but I've successfully installed other machines. system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 What kernel? Self compiled or from installation? What are your lilo/grub lines to the kernel? --Whatever kernel with Sarge stable. --The kernel is from the installation - no customization --As far as lilo lines, I never get to boot into linux to see the lilo lines. I really don't want to use grub. Please note, the reboot is unsuccessful, I never get to the step where it asks to set up mail or create a root password. I just get the above message. I can't scroll up to see any of the other messages. To recover and make the system so that I can at least boot back into windows is using a dos boot disk, do a fdisk /mbr - clear out the MBR, and then using debian's fdisk, blow away debian Ok, I understand fixing the MBR to boot XP again, but why rm debian? I don't understand this problem. It is sufficient to just restore the MBR and mark windows as bootable. --I remove debian for 2 reasons - to restore the PC to at least a functional windoze box. Also, I figure I did something wrong - maybe a fresh install will help - the whole process only takes 20 minutes - better safe than sorry. partions, and mark the windows NTFS as bootable. This has worked many times being as I've tried Lilo, Grub, and GAG as boot loaders - all successful. The machine is x86 box with ASUS motherboard, AMD 1800 CPU, gig of RAM, ATI video card, and Audigy sound card. Windows occupies the first 35 gig of the 200 gig board. Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. Why not just boot from a rescue disk (I think most/all install disks can be used as rescue disks also--check the boot options) and fix the lilo install so you can boot windows also? This at least fixes your boot options until you figure out the debian install problem. --Will do with regard to the rescue option - I'll look at the boot options. But pretty sure I tried this . . . Alternately, I think XP allows you to create a boot menu that will boot another OS in its own partition (never tried this so can't vouch for how well it works). --I basically wouldn't trust anything windoze - I'd rather Lilo control the booting. --pm HTH -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
On Wed, Sep 08, 2004 at 01:28:14PM -0400, Patrick Moroney wrote: CW Harris wrote: On Wed, Sep 08, 2004 at 10:18:45AM -0400, Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating Sarge is not yet stable---still testing --Understood - but I've successfully installed other machines. Not what I meant. At the moment, stable = Woody, testing = Sarge, so I still don't know what you mean by Sarge stable. Do you mean you are using the new Sarge netinstall CD to install stable? system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 What kernel? Self compiled or from installation? What are your lilo/grub lines to the kernel? --Whatever kernel with Sarge stable. What exactly are you using to install Sarge? CD from ??? Sarge netinstall CD (and what date)? --The kernel is from the installation - no customization --As far as lilo lines, I never get to boot into linux to see the lilo lines. I really don't want to use grub. Why not? Although grub is strange to use at first (if you are already used to linux device names and lilo), it does have the advantage that you can dynamically change what it is doing at boot time. This can be convenient to fix some boot problems. Anyway, that is not really the topic, but it might be something nice to play around with later. [...] Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. It is sounding like a boot floppy might at least help you boot into debian to finish the installation, but I wouldn't make that a permanent situation. The booting problems can be fixed. Why not just boot from a rescue disk (I think most/all install disks can be used as rescue disks also--check the boot options) and fix the lilo install so you can boot windows also? This at least fixes your boot options until you figure out the debian install problem. --Will do with regard to the rescue option - I'll look at the boot options. But pretty sure I tried this . . . Alternately, I think XP allows you to create a boot menu that will boot another OS in its own partition (never tried this so can't vouch for how well it works). --I basically would trust anything windoze - I'd rather Lilo control the booting. : I second that. Although I have set up dual boot where windows has control of the MBR and installed lilo to my / partition (marking it as the bootable partition) to avoid having windows trash my lilo installation when it crashed/fixed things or upgraded (I never bothered to figure out what circumstances lead windows to re-write the mbr shrug). Rescue CD/boot floppy works just as well. P.S. No need to CC me, I read the list. -- Chris Harris [EMAIL PROTECTED] --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
CW Harris wrote: On Wed, Sep 08, 2004 at 01:28:14PM -0400, Patrick Moroney wrote: CW Harris wrote: On Wed, Sep 08, 2004 at 10:18:45AM -0400, Patrick Moroney wrote: I'm trying to install Debian Sarge stable as a second operating Sarge is not yet stable---still testing --Understood - but I've successfully installed other machines. Not what I meant. At the moment, stable = Woody, testing = Sarge, so I still don't know what you mean by Sarge stable. Do you mean you are using the new Sarge netinstall CD to install stable? --It's a Sarge CD that when you boot, gives you 3 options, Stable, Testing, or Unstable (I think on the 3rd - I know I'll never use it . . .) But it is a net install. Overall, the install menus are different than the Woody disc I have. Unfortunately I made they CD a while ago, and don't have it with me. But I'm pretty sure it's 2.4 - 2.6 kernel. system on a 200 gig drive and not having a lot of success. The installation goes fine; I install Lilo in the MBR, the system goes for a reboot and then I get the following errors upon reboot: request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS Unable to mount root fs on 03:02 What kernel? Self compiled or from installation? What are your lilo/grub lines to the kernel? --Whatever kernel with Sarge stable. What exactly are you using to install Sarge? CD from ??? Sarge netinstall CD (and what date)? Net install - I'll get the date. --The kernel is from the installation - no customization --As far as lilo lines, I never get to boot into linux to see the lilo lines. I really don't want to use grub. Why not? Although grub is strange to use at first (if you are already used to linux device names and lilo), it does have the advantage that you can dynamically change what it is doing at boot time. This can be convenient to fix some boot problems. Anyway, that is not really the topic, but it might be something nice to play around with later. --actually I noticed that you could change the settings a boot with grub - which I thought was pretty cool - I actually was able to successfully boot once with grub - but once I rebooted it didn't work anymore; nor did it save the changes. Bottom line, I don't know grub, I know lilo - I'll probably spend some time researching grub though . . . [...] Should I make the system so that it will only boot into debian with a floppy? Any suggestions would be greatly appreciated. It is sounding like a boot floppy might at least help you boot into debian to finish the installation, but I wouldn't make that a permanent situation. The booting problems can be fixed. --I was coming to the same conclusion figuring I have to do some research on both lilo grub Why not just boot from a rescue disk (I think most/all install disks can be used as rescue disks also--check the boot options) and fix the lilo install so you can boot windows also? This at least fixes your boot options until you figure out the debian install problem. --Will do with regard to the rescue option - I'll look at the boot options. But pretty sure I tried this . . . Alternately, I think XP allows you to create a boot menu that will boot another OS in its own partition (never tried this so can't vouch for how well it works). --I basically wouldn't trust anything windoze - I'd rather Lilo control the booting. : I second that. Although I have set up dual boot where windows has control of the MBR and installed lilo to my / partition (marking it as the bootable partition) to avoid having windows trash my lilo installation when it crashed/fixed things or upgraded (I never bothered to figure out what circumstances lead windows to re-write the mbr shrug). Rescue CD/boot floppy works just as well. P.S. No need to CC me, I read the list. I friend of mine had similar problems as mine and it eventually just worked - but he didn't remember what he did to get it to work . . . -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Dual Boot Problem
On Wed, Sep 08, 2004 at 02:41:34PM -0400, Patrick Moroney wrote: CW Harris wrote: On Wed, Sep 08, 2004 at 01:28:14PM -0400, Patrick Moroney wrote: CW Harris wrote: [...] Why not just boot from a rescue disk (I think most/all install disks can be used as rescue disks also--check the boot options) and fix the lilo install so you can boot windows also? This at least fixes your boot options until you figure out the debian install problem. --Will do with regard to the rescue option - I'll look at the boot options. But pretty sure I tried this . . . You might also look over the errata for the installer (although I didn't see anything quickly related to your problem---but it may be as simple as booting the netinstall CD and booting the CD kernel as: linux root=/dev/hda2(IIRC this was your root - change as needed) (or linux26 if using the 2.6 kernel) (I have not played around a lot with the netinstall CD, but I know there are places where you can get to a shell and mount your partition to see what your lilo.conf looks like.) Or use Knoppix or other CD runnable disks as rescue disk for a more complete environment to troubleshoot. -- Chris Harris [EMAIL PROTECTED] --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel boot problem?
Hey, I kinda have a problem, I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. snip VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) end snip The other two kernels i did get stuck on this. snip VFS: Cannot open root device hda1 or unknown-block(0,0) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) end snip The only difference in the two messages is the unknown-block section. I used the old .config file so i would have what i needed for the new kernel and all i added was select a few sound card things. Have i added something that i shouldnt have ? or something i have missed ? I have checked the root= line in the grub config and it reads the same as the current kernel which is 2.6.7-1 and the one i am trying to compile is 2.6.8 Thanks in advance :) Grant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel boot problem?
#secure method=pgp mode=sign -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grant [EMAIL PROTECTED] writes: Hey, I kinda have a problem, I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. snip VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) end snip Sounds like you're making a kernel with no initrd and all the filesystems are modules. initrd is a pain in the butt, just compile the filesystems you need at boot time right into the kernel. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBNLybUzgNqloQMwcRAoDBAKCNsyVxXUMAZ7x+wU7ar+OV/snaXACfd8Ny vM6MkC8zmBqqXXbJXSclxSM= =4R3O -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel boot problem?
Paul Johnson wrote: #secure method=pgp mode=sign -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Grant [EMAIL PROTECTED] writes: Hey, I kinda have a problem, I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. snip VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) end snip Sounds like you're making a kernel with no initrd and all the filesystems are modules. initrd is a pain in the butt, just compile the filesystems you need at boot time right into the kernel. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBNLybUzgNqloQMwcRAoDBAKCNsyVxXUMAZ7x+wU7ar+OV/snaXACfd8Ny vM6MkC8zmBqqXXbJXSclxSM= =4R3O -END PGP SIGNATURE- Hey, Forgot to say that i am using make-kpkg then i am transfering it to my laptop to then installing the kernel. I just tried another 3times and this time i made sure i made the filesystems in the kernel and not modules, but i still got the same error. Is there a way i can use make-kpkg to make a initrd as the 2.6.7 (original kernel) has one but the one i keep trying to make is missing, is that the problem ? how would i make one and transfer it to the laptop... Thanks. Grant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel boot problem?
On Wed, Sep 01, 2004 at 01:43:47AM +0100, Grant wrote: Paul Johnson wrote: Grant [EMAIL PROTECTED] writes: I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) Sounds like you're making a kernel with no initrd and all the filesystems are modules. initrd is a pain in the butt, just compile the filesystems you need at boot time right into the kernel. Forgot to say that i am using make-kpkg then i am transfering it to my laptop to then installing the kernel. I just tried another 3times and this time i made sure i made the filesystems in the kernel and not modules, but i still got the same error. Is there a way i can use make-kpkg to make a initrd as the 2.6.7 (original kernel) has one but the one i keep trying to make is missing, is that the problem ? how would i make one and transfer it to the laptop... VFS: Cannot open root device hda1 or unknown-block(3,1) Try compiling your IDE controller and drive drivers into the kernel. (if you're one of the 1e-something of us who uses SCSI, change the directions.) -- The world's most effective spam filter: ln -sf /dev/full /var/mail/$USER -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel boot problem?
Stefan O'Rear wrote: On Wed, Sep 01, 2004 at 01:43:47AM +0100, Grant wrote: Paul Johnson wrote: Grant [EMAIL PROTECTED] writes: I have compiled now 4 kernel's and the first two kernel's got stuck on this message at boot. VFS: Cannot open root device hda1 or unknown-block(3,1) Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0) Sounds like you're making a kernel with no initrd and all the filesystems are modules. initrd is a pain in the butt, just compile the filesystems you need at boot time right into the kernel. Forgot to say that i am using make-kpkg then i am transfering it to my laptop to then installing the kernel. I just tried another 3times and this time i made sure i made the filesystems in the kernel and not modules, but i still got the same error. Is there a way i can use make-kpkg to make a initrd as the 2.6.7 (original kernel) has one but the one i keep trying to make is missing, is that the problem ? how would i make one and transfer it to the laptop... VFS: Cannot open root device hda1 or unknown-block(3,1) Try compiling your IDE controller and drive drivers into the kernel. (if you're one of the 1e-something of us who uses SCSI, change the directions.) Hey, *slaps forhead!* I didnt think someone said about doing that for the filesystems, i never thought about it might need it for other things, i guess that initrd is quite important if you use modules for your kernel... Anyways i will give that a try. Thanks again Grant. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
2.6.7 boot problem
Hi all, i tried to boot my debian on a 2.6.7 that i just compile ( reiserfs compile as module, my root fs is in reisefs), i installed lvm2 and make an initrd image with : mkinitrd -o kernel-2.6.7.img 2.6.7 i got this messages : Cpio : /etc/modprobe.conf : no suche file or directory Cpio : /lib/modules/modprobe.conf : No suche file or directory and when i ttry to boot this one : VFS : unable to mount root fs on unknown-block(0,0) any ideas to solve that ? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.7 boot problem
Looks like you deleted the /lib/modules/modprobe.conf file, you will have to restore it and then run mkinitrd -o... -ishwar On Fri, 9 Jul 2004, Yohann Desquerre wrote: Hi all, i tried to boot my debian on a 2.6.7 that i just compile ( reiserfs compile as module, my root fs is in reisefs), i installed lvm2 and make an initrd image with : mkinitrd -o kernel-2.6.7.img 2.6.7 i got this messages : Cpio : /etc/modprobe.conf : no suche file or directory Cpio : /lib/modules/modprobe.conf : No suche file or directory and when i ttry to boot this one : VFS : unable to mount root fs on unknown-block(0,0) any ideas to solve that ? Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.7 boot problem
Yohann Desquerre [EMAIL PROTECTED] writes: i tried to boot my debian on a 2.6.7 that i just compile ( reiserfs compile as module, my root fs is in reisefs), i installed lvm2 and make an initrd image with : mkinitrd -o kernel-2.6.7.img 2.6.7 i got this messages : Cpio : /etc/modprobe.conf : no suche file or directory Cpio : /lib/modules/modprobe.conf : No suche file or directory Which version of module-init-tools do you have installed? /etc/modprobe.conf and /lib/modules/modprobe.conf don't exist anymore since 3.1-pre2-1; see the Debian changelog for details. any ideas to solve that ? Perhaps you need a newer version of mkinitrd, but since I don't use initrd myself, I'm not sure. Otherwise, report a bug against mkinitrd that asks to reflect the module-init-tools changes. Martin -- ,--.Martin Dickopp, Dresden, Germany ,= ,-_-. =. / ,- ) http://www.zero-based.org/ ((_/)o o(\_)) \ `-' `-'(. .)`-' `-. Debian, a variant of the GNU operating system. \_/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.7 boot problem
Martin Dickopp wrote: Yohann Desquerre [EMAIL PROTECTED] writes: i tried to boot my debian on a 2.6.7 that i just compile ( reiserfs compile as module, my root fs is in reisefs), i installed lvm2 and make an initrd image with : mkinitrd -o kernel-2.6.7.img 2.6.7 i got this messages : Cpio : /etc/modprobe.conf : no suche file or directory Cpio : /lib/modules/modprobe.conf : No suche file or directory Which version of module-init-tools do you have installed? /etc/modprobe.conf and /lib/modules/modprobe.conf don't exist anymore since 3.1-pre2-1; see the Debian changelog for details. I use 3.1-pre5-1 version maybe there is another problèm in my kernel conf ? any ideas to solve that ? Perhaps you need a newer version of mkinitrd, but since I don't use initrd myself, I'm not sure. Otherwise, report a bug against mkinitrd that asks to reflect the module-init-tools changes. I ask me to up to date my version with the one i have it's seems to be Ok, but it didn't create th modprobe.conf file which sould replace the modules.conf of the 2.4 kernel !!! Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/dual-boot problem
Just a small update, since I'm sure someone will someday search and find this thread ... I got it working. The grub configuration in menu.1st was fine; windows had overwritten the MBR. I don't know if it's possible, but I *may* not have installed grub to the MBR the first time (I don't recall running install-grub /dev/hda) -- by marking the partition as bootable, it sort of worked. To fix it, I booted using gnoppix, mounted my /root directory and chroot'ed to it, mounted my /boot partition from there, then I ran install-grub and update-grub. Useful resources: HOWTO on Debianplanet, the discussion below it, and the rescue FAQ for Knoppix. Everything now works, but I do have a question: I have boot on a separate partition from /, so according to what I've read, I should have done: grub-install --root-directory=/boot /dev/hda This then installs into /boot/boot/grub, which seems sort of silly. So, I just did grub-install /dev/hda and it installs into /boot/grub. Is there a problem with this? Richard --- Derek Broughton [EMAIL PROTECTED] wrote: Chris Metzler wrote: Alex Malinovich [EMAIL PROTECTED] wrote: bootloader. This happened to me before, but you said you installed Debian AFTER you installed Windows, so this shouldn't be an issue. I agree that it shouldn't be an issue; but that's very much what this smells like. If he's not seeing GRUB or even briefly seeing the menu he's set up for grub, I bet the copy of grub in the MBR got trashed by Windows somehow. I'd agree his grub partition numbering must be right - he managed to get grub to boot into Linux and XP at least once. I can't help wondering if the fact that his /boot partition was _marked_ bootable is a problem. Linux certainly doesn't need to have a partition marked bootable, and iirc Windows (at least use to) have a problem with multiple bootable partitions. I though earlier versions simply refused to boot. Perhaps XP noted the wrong bootable partition and merrily rewrote things to match its version of reality. derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/dual-boot problem
On Fri, Apr 23, 2004 at 05:23:53AM -0700, Richard Weil wrote: Just a small update, since I'm sure someone will someday search and find this thread ... I got it working. The grub configuration in menu.1st was fine; windows had overwritten the MBR. I don't know if it's possible, but I *may* not have installed grub to the MBR the first time (I don't recall running install-grub /dev/hda) -- by marking the partition as bootable, it sort of worked. I haven't had much experience w/ XP, but I'm wondering if you had it booting on /boot partition (marked bootable). On rebooting the WinXP MBR booted the partition with the bootable flag. Then upon subsequently booting into WinXP it removed the bootable flag on your /boot partition, thus you never got to grub again? I'm mostly wondering because WinXP does have a multi-boot manager now, and this might be how it regains control if you haven't added your alternate OS into its menu? -- Chris Harris [EMAIL PROTECTED] --- GNU/Linux --- The best things in life are free. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
grub/dual-boot problem
I'm having a grub/dual-boot problem. I'm running Sarge with the kernel from the initial install. The hard drive has 4 primary partitions: part 1 = win xp part 2 = /boot -- marked bootable in partition table part 3 = / part 4 = swap I installed win XP into part 1. I then installed Sarge and updated grub. On reboot, everything was fine -- grub showed a menu with both win xp and linux. I could boot into linux fine. I had to then boot into windows. Now, on reboot, the grub menu doesn't come up; the machine goes straight into windows. Is there anything I can do in my grub setup to prevent this? It would be nice to actually be able to go back and forth. Thanks, Richard __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/dual-boot problem
On Thu, 2004-04-22 at 13:35, Richard Weil wrote: I'm having a grub/dual-boot problem. I'm running Sarge with the kernel from the initial install. The hard drive has 4 primary partitions: part 1 = win xp part 2 = /boot -- marked bootable in partition table part 3 = / part 4 = swap I installed win XP into part 1. I then installed Sarge and updated grub. On reboot, everything was fine -- grub showed a menu with both win xp and linux. I could boot into linux fine. I had to then boot into windows. Now, on reboot, the grub menu doesn't come up; the machine goes straight into windows. Is there anything I can do in my grub setup to prevent this? It would be nice to actually be able to go back and forth. Check your configuration. Your XP entry probably has something along the lines of savedefault set. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
Re: grub/dual-boot problem
I don't have the machine in front of me, but I'm nealry certain that I don't have savedefault set. I believe my grub entry for win xp was essentially the same as what is shown in the grub docs: title win root (hd0,1) makeactive chainloader +1 I set root to (hd0,1), which is the /boot directory (and where grub lives). Perhaps this is wrong, but I interpret root in the context of grub to basically mean grub's root. Richard --- Alex Malinovich [EMAIL PROTECTED] wrote: On Thu, 2004-04-22 at 13:35, Richard Weil wrote: I'm having a grub/dual-boot problem. I'm running Sarge with the kernel from the initial install. The hard drive has 4 primary partitions: part 1 = win xp part 2 = /boot -- marked bootable in partition table part 3 = / part 4 = swap I installed win XP into part 1. I then installed Sarge and updated grub. On reboot, everything was fine -- grub showed a menu with both win xp and linux. I could boot into linux fine. I had to then boot into windows. Now, on reboot, the grub menu doesn't come up; the machine goes straight into windows. Is there anything I can do in my grub setup to prevent this? It would be nice to actually be able to go back and forth. Check your configuration. Your XP entry probably has something along the lines of savedefault set. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 ATTACHMENT part 2 application/pgp-signature name=signature.asc __ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub/dual-boot problem
On Thu, 2004-04-22 at 14:09, Richard Weil wrote: I don't have the machine in front of me, but I'm nealry certain that I don't have savedefault set. I believe my grub entry for win xp was essentially the same as what is shown in the grub docs: title win root (hd0,1) makeactive chainloader +1 I set root to (hd0,1), which is the /boot directory (and where grub lives). Perhaps this is wrong, but I interpret root in the context of grub to basically mean grub's root. Based on the partition listing you gave in your original message, grub should be set up as follows: Windows: root (hd0,0) Debian: root (hd0,2) Keep in mind that in grub, partition 1 is actually 0, 2 is 1, 3 is 2, and so on. Since you said that the computer goes directly into Windows, I'm wondering if grub is kicking in at all? If you see GRUB on the screen when you boot, you can try holding left shift while booting to get the boot menu. The other possibility is that Windows overwrote your bootloader. This happened to me before, but you said you installed Debian AFTER you installed Windows, so this shouldn't be an issue. But if you don't see grub at all, this could be the problem. If that's the case, you'll need to boot off of either a recovery disk or your Debian install disk and re-run grub-install and update-grub. -- Alex Malinovich Support Free Software, delete your Windows partition TODAY! Encrypted mail preferred. You can get my public key from any of the pgp.net keyservers. Key ID: A6D24837 signature.asc Description: This is a digitally signed message part
Re: grub/dual-boot problem
On Thu, 22 Apr 2004 15:58:12 -0500 Alex Malinovich [EMAIL PROTECTED] wrote: Based on the partition listing you gave in your original message, grub should be set up as follows: Windows: root (hd0,0) Debian: root (hd0,2) Keep in mind that in grub, partition 1 is actually 0, 2 is 1, 3 is 2, and so on. Yes, but I still don't think you've got it quite right. He had XP on the first partition, /boot on the second, / on the third, and swap on the fourth. To grub, those are partitions 0, 1, 2 and 3 respectively, just as you say. However, the partition that you give grub with the root command is NOT intended to be the root partition of the booted operating system. It's where grub should look to find the kernel. If he has /boot in the second partition on his hard drive, he wants to tell grub that it should look in that second partition for the kernel: root (hd0,1) and then, to get linux to use the correct partition (the third one) for the root filesystem of the booted OS, one passes that information to the kernel as an argument, e.g. root (hd0,1) kernel vmlinuz root=/dev/hda3 boot or something like that. Not that this solves the poster's problem at all; but I just wanted to make sure that people didn't get the wrong idea about that root grub command. Since you said that the computer goes directly into Windows, I'm wondering if grub is kicking in at all? If you see GRUB on the screen when you boot, you can try holding left shift while booting to get the boot menu. The other possibility is that Windows overwrote your bootloader. This happened to me before, but you said you installed Debian AFTER you installed Windows, so this shouldn't be an issue. I agree that it shouldn't be an issue; but that's very much what this smells like. If he's not seeing GRUB or even briefly seeing the menu he's set up for grub, I bet the copy of grub in the MBR got trashed by Windows somehow. -c -- Chris Metzler [EMAIL PROTECTED] (remove snip-me. to email) As a child I understood how to give; I have forgotten this grace since I have become civilized. - Chief Luther Standing Bear pgp0.pgp Description: PGP signature
Re: grub/dual-boot problem
Chris Metzler wrote: Alex Malinovich [EMAIL PROTECTED] wrote: bootloader. This happened to me before, but you said you installed Debian AFTER you installed Windows, so this shouldn't be an issue. I agree that it shouldn't be an issue; but that's very much what this smells like. If he's not seeing GRUB or even briefly seeing the menu he's set up for grub, I bet the copy of grub in the MBR got trashed by Windows somehow. I'd agree his grub partition numbering must be right - he managed to get grub to boot into Linux and XP at least once. I can't help wondering if the fact that his /boot partition was _marked_ bootable is a problem. Linux certainly doesn't need to have a partition marked bootable, and iirc Windows (at least use to) have a problem with multiple bootable partitions. I though earlier versions simply refused to boot. Perhaps XP noted the wrong bootable partition and merrily rewrote things to match its version of reality. derek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot-Problem
Hallo, ich habe debian woody so installiert so dass er von Diskette startet. Ein zwei mal hat er das auch brav gemacht. Aber jetzt klappt das nicht mehr und er bricht mit der folgenden Fehlermeldung ab: Loading linux.bin.. Boot failed: please change disks and press a key to continue. Kann ich jetzt vielleicht mit der 1. Installations-CD booten und das installierte System starten? Ich würde eher lieber von hd booten allerdings möchte ich gerne auf der Platte noch gerne ein Win XP installieren und das würde den mbr ja zerstören. Ist es evt. möglich. - Windows auf die Debianplatte zu installieren - anschliessend Debian von CD booten und lilo zu installieren, dass das vorhandene Debian und Windows starten können? -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Boot-Problem
* Wilhelm Kutting [EMAIL PROTECTED] [040415 16:19]: Kann ich jetzt vielleicht mit der 1. Installations-CD booten und das installierte System starten? Ja, geb am Prompt einfach rescue root=$DEINE_ROOT_PARTITION ein, oder guck mal mit F3 oder so nach, wie der Parameter für das rescue Image mit 2.4er Kernel heisst (resc24?). Ist es evt. möglich. - Windows auf die Debianplatte zu installieren - anschliessend Debian von CD booten und lilo zu installieren, dass das vorhandene Debian und Windows starten können? Klar. Installer dein ... anderes Betriebssystem, boote von CD, kommentiere in der /etc/lilo.conf den other-Einrag am Ende aus, und pass ggf. die Partition an, dass sollte dann funktionieren. Yours sincerely, Alexander signature.asc Description: Digital signature
Boot-Problem
Title: ARCUS1 Briefpapier Hallo, ich habe leider ein boot-problem: es kommt nach der installation von einer gekauften cd-distribution 3.0 r0 (20020718) die meldung: mkdir: connot create directory /tmp/base-config.404: no space left on device INIT: Id "1" respawning too fast: desabled for 5 minutes Installiert wurde das System von den gelieferten cd's. tschüss, wilfried.
Re: Boot-Problem
ARCUS-SYSTEMS wrote: Hallo, ich habe leider ein boot-problem: Und ein HTML-Problem, und ein Problem mit der Groß- und Kleinschreibung... es kommt nach der installation von einer gekauften cd-distribution 3.0 r0 (20020718) die meldung: mkdir: connot create directory /tmp/base-config.404: no space left on device Klare Aussage: Dir ist der Festplattenplatz ausgegangen... Hast du vielleicht die Partition zu klein ausgelegt, in der das /tmp-Verzeichnis liegt? [...] Stefan -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
mysteriöses PCMCIA-boot-problem
Hi Liste, ich hab hier ein sehr merkwürdiges Problemchen: meine LevelOne WPC-0100 PCMCIA-Wlan-Karte will irgendwie nicht funktionieren und ich hatte mich auch schon fast damit abgefunden bis ich zufällig mal im Single-User-Mode gebootet habe (also mit der s Option). Dann habe ich in diesem Modus mit cardctl ident mal mein glück versucht -- war aber scheinbar nix -- also habe ich mit exit normal weitergebootet und auf einmal wurde die Karte korrekt erkannt. Ich habe das noch mal getestet um zu sehen ob es reproduzierbar ist und siehe da: 1) normaler Bootvorgang: Karte wird lediglich als Anonymous Memory erkannt und ist unbrauchbar: crash:~# cardctl ident Socket 0: no product info available crash:~# cardctl status Socket 0: 3.3V 16-bit PC Card function 0: [ready] crash:~# cardctl config Socket 0: Vcc 3.3V Vpp1 3.3V Vpp2 3.3V crash:~# cardctl info PRODID_1= PRODID_2= PRODID_3= PRODID_4= MANFID=, FUNCID=255 2) Bootvorgang im Single-User-Mode eingeloggt und sofort mit exit normal weitergebootet: Karte wird nicht korrekt erkannt, siehe 1) 3) Bootvorgang im Single-User-Mode eingeloggt cardctl ident gemacht (ein paar Warungen kamen cs: warning: no high memory space available! cs: unable to map card memory! cs: unable to map card memory! cs: unable to map card memory! cs: unable to map card memory! cs: unable to map card memory! cs: unable to map card memory! cs: unable to map card memory!) und sofort mit exit normal weitergebootet: Karte wird korrekt erkannt, siehe: crash:~# cardctl ident Socket 0: product info: Digital Data Communications, WPC-0100, Version 00.00, manfid: 0x0156, 0x0002 function: 6 (network) Was läuft in der dritten Variante nun anders als bei den ersten beiden? Hat jemand einen Hinweis für mich wie ich was-auch-immer-in-der-dritte-varianta-passiert auf den normalen bootvorgang übertragen kann? Falls das wichtig ist: ich habe nen selbsgebackenen 2.6.4er kernel, wireless-tools, hotplug und pcmcia-cs sind installiert. Danke schon mal und schöne Grüße Bastian
Re: mysteriöses PCMCIA-boot-problem
B. Venthur [EMAIL PROTECTED] writes: ich hab hier ein sehr merkwürdiges Problemchen: meine LevelOne WPC-0100 PCMCIA-Wlan-Karte will irgendwie nicht funktionieren [...] cs: warning: no high memory space available! cs: unable to map card memory! [...] Falls das wichtig ist: ich habe nen selbsgebackenen 2.6.4er kernel, wireless-tools, hotplug und pcmcia-cs sind installiert. Ich hatte ein ähnliches Problem mit meiner PCMCIA-Netzwerkkarte (nicht wireless), welches nur unter 2.6er Kerneln auftrat. Um es zu lösen, mußte ich in /etc/pcmcia/config.opts die Zeile include memory 0xa000-0xa0ff, memory 0x6000-0x60ff durch include memory 0x6000-0x60ff ersetzen. Ich weiß nicht, ob das in Deinem Fall auch hilft, aber versuchen könntest Du es ja mal. :) Martin -- ,--.Martin Dickopp, Dresden, Germany ,= ,-_-. =. / ,- ) http://www.zero-based.org/ ((_/)o o(\_)) \ `-' `-'(. .)`-' `-. Debian, a variant of the GNU operating system. \_/
Re: mysteriöses PCMCIA-boot-problem
Hallo Bastian, welches Notebook hast Du? Was läuft in der dritten Variante nun anders als bei den ersten beiden? Hat jemand einen Hinweis für mich wie ich was-auch-immer-in-der-dritte-varianta-passiert auf den normalen bootvorgang übertragen kann? Falls das wichtig ist: ich habe nen selbsgebackenen 2.6.4er kernel, wireless-tools, hotplug und pcmcia-cs sind installiert. Danke schon mal und schöne Grüße Bastian -- Mit freundlichen Gruessen Bjoern Schmidt -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
[solved] RE: mysteriöses PCMCIA-boot-problem
From: Martin Dickopp [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 17, 2004 1:36 PM To: [EMAIL PROTECTED] Subject: Re: mysteriöses PCMCIA-boot-problem [...] Ich hatte ein ähnliches Problem mit meiner PCMCIA-Netzwerkkarte (nicht wireless), welches nur unter 2.6er Kerneln auftrat. Um es zu lösen, mußte ich in /etc/pcmcia/config.opts die Zeile include memory 0xa000-0xa0ff, memory 0x6000-0x60ff durch include memory 0x6000-0x60ff ersetzen. Ich weiß nicht, ob das in Deinem Fall auch hilft, aber versuchen könntest Du es ja mal. :) Martin Hallo Martin, Danke, das war es! Weist du noch wie du darauf gekommen bist? Vielleicht kann ich meine Problemlösungsstrategie noch etwas verbessern ;) Ist das vielleicht ein Bug oder zumindest ein Fehlverhalten was man vielleicht nem Maintainer stecken sollte? Ich weis nicht so genau ob ich mir das bis zur nächsten Debian-Installation merken kann (man muss sich leider ziemlich viele Kleinigkeiten merken um seine Hardware zum laufen zu bekommen). Wenn ja an wen? An den Betreuer von pcmcia-cs? Und in welcher Form -- ich wüsste nicht so genau wie ich den Bug (wenn es denn einer ist) beschreiben soll. Jedenfalls vielen Dank und schöne Grüße Bastian
Re: [solved] RE: mysteriöses PCMCIA-boot-problem
B. Venthur schrieb: Ist das vielleicht ein Bug oder zumindest ein Fehlverhalten was man vielleicht nem Maintainer stecken sollte? Ich weis nicht so genau ob ich mir Kann man nicht wirklich als bug bezeichnen. Schau mal hier, kap. 3.5: http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-3.html -- Mit freundlichen Gruessen Bjoern Schmidt -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: [solved] RE: mysteriöses PCMCIA-boot-problem
B. Venthur [EMAIL PROTECTED] writes: From: Martin Dickopp [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 17, 2004 1:36 PM To: [EMAIL PROTECTED] Subject: Re: mysteriöses PCMCIA-boot-problem [...] Ich hatte ein ähnliches Problem mit meiner PCMCIA-Netzwerkkarte (nicht wireless), welches nur unter 2.6er Kerneln auftrat. Um es zu lösen, mußte ich in /etc/pcmcia/config.opts die Zeile include memory 0xa000-0xa0ff, memory 0x6000-0x60ff durch include memory 0x6000-0x60ff ersetzen. Ich weiß nicht, ob das in Deinem Fall auch hilft, aber versuchen könntest Du es ja mal. :) Danke, das war es! Weist du noch wie du darauf gekommen bist? Durch googlen. Ich weiß nicht mehr, welche Suchbegriffe ich verwendet habe, aber es hat lange (mehrere Stunden) gedauert. Dies ist einer der bedauerlichen Fälle, wo die Lösung zwar funktioniert, aber ich selbst nicht genau verstehe, warum sie das tut. :( Ist das vielleicht ein Bug oder zumindest ein Fehlverhalten was man vielleicht nem Maintainer stecken sollte? Ich weis nicht so genau ob ich mir das bis zur nächsten Debian-Installation merken kann (man muss sich leider ziemlich viele Kleinigkeiten merken um seine Hardware zum laufen zu bekommen). Ich habe mir aus diesem Grund ein Log aller Konfigurationsschritte angelegt, indem ich alles in einer Datei notiert habe. Wenn ja an wen? An den Betreuer von pcmcia-cs? Und in welcher Form -- ich wüsste nicht so genau wie ich den Bug (wenn es denn einer ist) beschreiben soll. Ja, Du könntest einen Bug gegen pcmcia-cs abschicken. (Falls Du mit dem Prozedere nicht vertraut bist, siehe http://www.debian.org/Bugs/.) Der Bugreport sollte im wesentlichen das enthalten, was Du auch in Deiner ursprüglichen Mail an diese Mailingliste geschrieben hast, und was als Lösung funktioniert. Wenn Du mir dann die Bugnummer mailst, ergänze ich den Report um den Hinweis, daß das gleiche auf meine Hardware zutrifft. Martin -- ,--.Martin Dickopp, Dresden, Germany ,= ,-_-. =. / ,- ) http://www.zero-based.org/ ((_/)o o(\_)) \ `-' `-'(. .)`-' `-. Debian, a variant of the GNU operating system. \_/
boot-problem
Hallo Leute, folgende Situation: /dev/hda2 DOS /dev/hda3 WIN98 /dev/hda7 Woody (2 Kernels, 2.4.18 / 2.4.25) Lilo in extended-partition /dev/hda4 installiert. bootflag auf /dev/hda4 gesetzt. Lilo bootet DOS -- ok Woody 2.4.18 -- ok Woody 2.4.25 (eigenbau) -- ok Win98 -- stoppt ( command.com fehlt oder fehlerhaft) -- Notmassnahme -- Bootflag von /dev/hda4 auf /dev/hda3 ändern. Win98 bootet wieder einwandfrei. Natürlich unter Umgehung von Lilo !!! -- Wechsel zum Tagesgeschäft -- Bootdisk rein, Woody booten, mit 'fdisk' bootflag wieder umschalten. Nun geht wieder Lilo aber Win98 nicht mehr. Wenn ich das jedesmal machen muß, um Win98 zu starten, bekomme ich bestimmt bald Pickel. Oder muß ich damit leben, weil Lilo in der Extended-Partition verankert ist. Gibt es Erfahrungen ? H.G. Keller -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: boot-problem
Am Sonntag, 7. März 2004 13:17 schrieb Hans Georg Keller: Hallo Leute, folgende Situation: /dev/hda2 DOS /dev/hda3 WIN98 /dev/hda7 Woody (2 Kernels, 2.4.18 / 2.4.25) Lilo in extended-partition /dev/hda4 installiert. Häh, versteh ich nicht! Eine eigene Partition nur für Lilo oder steh ich auf dem Schlauch? bootflag auf /dev/hda4 gesetzt. IMHO sollte Lilo bei dieser Konfiguration in den MBR, sprich /dev/hda. Dann kannst du die Win-Partition auf bootable setzen. Windows ist da ein wenig eigen ;-) Gruß, Uwe -- I AM DEATH, NOT TAXES. I TURN UP ONLY ONCE. -- (Terry Pratchett, Feet of Clay) -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: boot-problem
Uwe Malzahn [EMAIL PROTECTED] wrote: Am Sonntag, 7. März 2004 13:17 schrieb Hans Georg Keller: /dev/hda2 DOS /dev/hda3 WIN98 /dev/hda7 Woody (2 Kernels, 2.4.18 / 2.4.25) Lilo in extended-partition /dev/hda4 installiert. Häh, versteh ich nicht! Eine eigene Partition nur für Lilo oder steh ich auf dem Schlauch? Ja, stehst du. /dev/hda7 ist die dritte logische Partition in der erweiterten Partionen /dev/hda4. Und in dieser (primäre) erweiterten Partition bzw. dessen Bootsektor steht lilo. Alles ganz normal. S° -- 142 Reasons, Why You Can't Find Your System Administrator 141. They're actully in their office, but buried under the mound of paper, manuals and spare parts that just avalanced off their desk.. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: boot-problem
Am Sonntag, 7. März 2004 15:41 schrieb Uwe Malzahn: Am Sonntag, 7. März 2004 13:17 schrieb Hans Georg Keller: Hallo Leute, folgende Situation: /dev/hda2 DOS /dev/hda3 WIN98 /dev/hda7 Woody (2 Kernels, 2.4.18 / 2.4.25) Lilo in extended-partition /dev/hda4 installiert. Häh, versteh ich nicht! Eine eigene Partition nur für Lilo oder steh ich auf dem Schlauch? /dev/hda4 ist keine echte Partition sondern der Container für alle logischen Laufwerke in der erweiterten Partition /dev/hda5 und folgende. Das Beispiel ist sogar in einer LILO-Doku erklärt. bootflag auf /dev/hda4 gesetzt. IMHO sollte Lilo bei dieser Konfiguration in den MBR, sprich das wollte ich eigentlich vermeiden, weil dieser mit jeder Windows-Neuinstallation zermarmelt wird. /dev/hda. Dann kannst du die Win-Partition auf bootable setzen. Windows ist da ein wenig eigen ;-) Gruß, Uwe -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: boot-problem
Am 2004-03-07 13:17:07, schrieb Hans Georg Keller: Hallo Leute, folgende Situation: /dev/hda2 DOS /dev/hda3 WIN98 /dev/hda7 Woody (2 Kernels, 2.4.18 / 2.4.25) Lilo in extended-partition /dev/hda4 installiert. bootflag auf /dev/hda4 gesetzt. Lilo bootet DOS -- ok Woody 2.4.18 -- ok Woody 2.4.25 (eigenbau) -- ok Win98 -- stoppt ( command.com fehlt oder fehlerhaft) Das ist normal, denn Win98 wimm command.com v7.02 haben und Du hast auf /dev/hda2 DOS und somit maximal 6.22. Das verträgt sich nicht. Du mußt LILO so konfigurieren, wenn Du in Win98 booten willst, das er die /debv/hda2 versteckt, also Fat16 (hidden) setzt. Desweiteren mußt Du jebachdem, ob Du DOS oder Win98 booten willst, die partition als bootabel markieren. Wenn ich das jedesmal machen muß, um Win98 zu starten, bekomme ich bestimmt bald Pickel. Oder muß ich damit leben, weil Lilo in der Extended-Partition verankert ist. Neee, nur richtig konfigurieren. Gibt es Erfahrungen ? Habe das auf meinem Laptop vor zwei Jahren auch gehabt... Frage mich jetzt nicht wie ich das gemacht hatte, denn seit geraumerzeit habe ich kein Windows mehr und habe den Schwachsinn vergessen. H.G. Keller Greetings Michelle -- Registered Linux-User #280138 with the Linux Counter, http://counter.li.org/ -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
rescue disk boot problem
beim booten der rescue disk für eine neuinstallation von debian tritt bei mir folgender fehler auf: boot: Loading linux.bin ready. Wrong loader: giving up. da bleibt das system dann stehen. das system: amd k6-2 64mb ram 400mb festplatte kein cdrom ich habe andere disketten versucht, verschiedene rescue.bin s runtergeladen und ausprobiert, aber kein erfolg. für jede hilfe wäre ich sehr dankbar! -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: rescue disk boot problem
ja hallo erstmal,... Am Dienstag, 3. Februar 2004 15:01 schrieb Peter Gruber: beim booten der rescue disk für eine neuinstallation von debian tritt bei mir folgender fehler auf: boot: Loading linux.bin ready. Wrong loader: giving up. da bleibt das system dann stehen. das system: amd k6-2 64mb ram 400mb festplatte kein cdrom ich habe andere disketten versucht, verschiedene rescue.bin s runtergeladen und ausprobiert, aber kein erfolg. Probier mal eine neuere sysliunux Version. Was besseres fällt mir leider nicht ein. Keep smiling yanosz -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Uh-Oh - boot problem
On Sat, 3 Jan 2004 21:44:46 -0500, Kevin Mark [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]: On Sat, Jan 03, 2004 at 05:35:56PM -0800, Chris Cothrun wrote: Hi, My sid system won't boot. Kernel panic after a bunch of attempts to load modules. Output is something like: modprobe can't open dependancies file /lib/modules mount: you must specify filesystem type pivot_root: no such file or directory /sbin/init: cannot open /dev/console: no such file attempted to kill init kernel panic I think it is because apt-get upgraded my kernel, but I forgot to run lilo. Would that do it? I've got the Debian Woody install disk and I've tried booting my partitions from that but no luck, I get a kernel panic (but not the long list of module loading attempts). I can boot the install CD and get a console, any pointers on fixing things from here? I think I can mount the partition and then run lilo, right? Hi Chris, kernels are not deleted automatically. So, if you install another one, it is there still. If you have a GOOD LILO.CONF, the this will work. 1) get Knoppix 2) boot knoppix 3) go to a console (with ctrl-alt-fn1) or using the knoppix menu 4) mount the root parition from your HD (mount /dev/hda1 /mnt) ...as in:' mount -v -o,rw /dev/hda1 /mnt '... where hda1 is the location of your root. 5) chroot /mnt ...as in:' chroot /mnt /bin/bash ', or whatever shell you prefer. 6) lilo -v assuming lilo runs it will re-install lilo and when you reboot everything works. ..before playing with more disks, or if you need to scp the disk image or whatever;' mount -v -t proc /proc proc ', but do remember to ' umount -v /proc ', or ugly things happen. 7) just to be safe, also run 'mkboot' this will prompt you for a floppy and will make a 'boot disk' incase lilo doesnt install ok on the HD-Kev Trying the above, I've gone to the console and run e2fsck /dev/hda2, it listed a couple of inodes and then reported everything OK. After that I'm able to mount /dev/hda2 (root) but lilo complains about libc5.so (GLIBC_2.3 not found). -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Uh-Oh - boot problem
On 3 Jan 2004 , Chris Cothrun [EMAIL PROTECTED] wrote: My Debian system won't boot. Kernel panic after a bunch of attempts to load modules. I think it is because apt-get upgraded my kernel, but I forgot to run lilo. Thanks to Tom and John on lvlug and Arnt and Kevin on debian- user I got the system working. A Mepis boot CD (I had the ISO around from previous experimentations) helped immensely as well. The key seemed to be some kind of filesystem problem as I didn't make progress until I ran fsck from Mepis. I reverted to the 2.4.22 kernel image, removed the 2.4.23 image and then reinstalled it using synaptic. The apt tools do run lilo unless you tell them not to, but even then lilo should have been able to boot the 2.4.22 kernel. Now, on to messing things up with my own kernels :) Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Uh-Oh - boot problem
Hi, My sid system won't boot. Kernel panic after a bunch of attempts to load modules. Output is something like: modprobe can't open dependancies file /lib/modules mount: you must specify filesystem type pivot_root: no such file or directory /sbin/init: cannot open /dev/console: no such file attempted to kill init kernel panic I think it is because apt-get upgraded my kernel, but I forgot to run lilo. Would that do it? I've got the Debian Woody install disk and I've tried booting my partitions from that but no luck, I get a kernel panic (but not the long list of module loading attempts). I can boot the install CD and get a console, any pointers on fixing things from here? I think I can mount the partition and then run lilo, right? Trying the above, I've gone to the console and run e2fsck /dev/hda2, it listed a couple of inodes and then reported everything OK. After that I'm able to mount /dev/hda2 (root) but lilo complains about libc5.so (GLIBC_2.3 not found). TIA! Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Uh-Oh - boot problem
On Sat, Jan 03, 2004 at 05:35:56PM -0800, Chris Cothrun wrote: Hi, My sid system won't boot. Kernel panic after a bunch of attempts to load modules. Output is something like: modprobe can't open dependancies file /lib/modules mount: you must specify filesystem type pivot_root: no such file or directory /sbin/init: cannot open /dev/console: no such file attempted to kill init kernel panic I think it is because apt-get upgraded my kernel, but I forgot to run lilo. Would that do it? I've got the Debian Woody install disk and I've tried booting my partitions from that but no luck, I get a kernel panic (but not the long list of module loading attempts). I can boot the install CD and get a console, any pointers on fixing things from here? I think I can mount the partition and then run lilo, right? Hi Chris, kernels are not deleted automatically. So, if you install another one, it is there still. If you have a GOOD LILO.CONF, the this will work. 1) get Knoppix 2) boot knoppix 3) go to a console (with ctrl-alt-fn1) or using the knoppix menu 4) mount the root parition from your HD (mount /dev/hda1 /mnt) where hda1 is the location of your root. 5) chroot /mnt 6) lilo -v assuming lilo runs it will re-install lilo and when you reboot everything works. 7) just to be safe, also run 'mkboot' this will prompt you for a floppy and will make a 'boot disk' incase lilo doesnt install ok on the HD -Kev Trying the above, I've gone to the console and run e2fsck /dev/hda2, it listed a couple of inodes and then reported everything OK. After that I'm able to mount /dev/hda2 (root) but lilo complains about libc5.so (GLIBC_2.3 not found). TIA! Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: Boot-Problem : unable to open the initial console
Steffen Lorch wrote: [..] image=/vmlinuz hier liegt mit Sicherheit NICHT der Gentoo Kernel image=/pfad/zu/gentoo/vmlinz-2.4.23 label=Gentoo root=/dev/hda6 ... cu Steff Du hast recht (und ich das FM nicht richtig gelesen :-( ). Aus man lilo.conf: A per-image section starts with either a line image=pathname to indicate a file *or device* containing the boot image of a Linux kernel, or a line Sobald ich mal wieder zu einer vernünftigen Zeit nach Hause komme, probiere ich es aus. Danke für Deine Hilfe. regards Jerry -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Boot-Problem : unable to open the initial console
Du (Gerald Preissler) schriebst: image=/vmlinuz default=Woody image=/vmlinuz label=Gentoo / der Gentoo-Installation ist /dev/hda6, /boot ist /dev/hda1 Du nimmst denselben Kernel zum Booten? Du weist, dass Debian - zumindest in Woody - kein DevFS benutzt und Gentoo ohne DevFS nicht auskommt? Deine Lilo.conf ist kaputt. Boote den Gentoo Kernel, dann hast Du Aussichten auf Erfolg. - die Kernelkonfiguration habe ich von der Debian-Installation übertragen und dann mit make menuconfig noch um Support für ReiserFS erweitert. DevFS? Das ist der springende Punkt! Hast Du dei Gentoo Anleitung gelesen? - die Installation des Kernel erfolgte nicht wie in der Anleitung beschrieben, sondern mit make install. Der Kernel unter /boot hat die gleiche Größe und das gleiche Erstellungsdatum wie unter /usr/src/linux/arch/i386/boot. Daher gehe ich davon aus, dass die Installation geklappt hat. Sind die Module kopiert worden? Warum machst Du es nicht, wie es in der Anleitung steht? Aber wie gesagt, ich denk, dass Du gar nicht den Gentookernel bootest. Danach noch ein ln -s /boot/vmlinuz-2.4.20-gentoo-r9 /vmlinuz Hmmm... im Chroot? cu Steffen -- BOFH Excuse #83: Support staff hung over, send aspirin and come back LATER. pgp0.pgp Description: PGP signature
Re: Boot-Problem : unable to open the initial console
Hallo Steffen, Dir und natürlich auch Torsten danke für die Antwort. Steffen Lorch wrote: Du nimmst denselben Kernel zum Booten? Eigentlich nicht. Nochmal die aus meiner Sicht relevanten Teile von lilo.conf : image=/vmlinuz label=Woody root=/dev/hdc12 image=/vmlinuz label=Gentoo root=/dev/hda6 Der Debian-Kernel befindet sich auf /dev/hdc12 (/ in der Debian-Installation). Der Kernel für Gentoo befindet sich auf /dev/hda1 (/boot in der Gentoo-Installation), darauf ist dann von /dev/hda6 ( / in der Gentoo-Installation) verlinkt (siehe unten). Ich glaube, jetzt sehe ich auch den Unterschied. Wie war noch einmal die Konfiguration für Lilo für einen Kernel in einer seperaten Bootpartition? (Die Frage ist natürlich rethorisch...) Du weist, dass Debian - zumindest in Woody - kein DevFS benutzt und Gentoo ohne DevFS nicht auskommt? Deine Lilo.conf ist kaputt. Boote den Gentoo Kernel, dann hast Du Aussichten auf Erfolg. - die Kernelkonfiguration habe ich von der Debian-Installation übertragen und dann mit make menuconfig noch um Support für ReiserFS erweitert. DevFS? Das ist der springende Punkt! Hast Du dei Gentoo Anleitung gelesen? Argh, überlesen. Werde ich also als nächstes ausprobieren, zusammen mit einer aktualisierten lilo.conf. Danke für den Tip. - die Installation des Kernel erfolgte nicht wie in der Anleitung beschrieben, sondern mit make install. Der Kernel unter /boot hat die gleiche Größe und das gleiche Erstellungsdatum wie unter /usr/src/linux/arch/i386/boot. Daher gehe ich davon aus, dass die Installation geklappt hat. Sind die Module kopiert worden? Warum machst Du es nicht, wie es in der Anleitung steht? Aber wie gesagt, ich denk, dass Du gar nicht den Gentookernel bootest. Sorry, da war meine Beschreibung ein wenig unvollständig. Ein make modules_install ist natürlich auch gelaufen, ich hatte es nur nicht erwähnt weil es ja in der Installationsanleitung steht. Das make install war eher ein Reflex, bevor ich Debian verwendet habe, habe ich den Kernel immer so installiert. Danach noch ein ln -s /boot/vmlinuz-2.4.20-gentoo-r9 /vmlinuz Hmmm... im Chroot? Si. Ebenso wie das kompilieren des Kernels. cu Steffen Thanks Jerry p.s. Eigentlich war das Posting ja für die entsprechende Gentoo-Liste gedacht, wo es ja thematisch auch eher hingehört (war eben etwas spät gestern abend). Ich finde es toll, dass trotzdem konstruktive Kommentare und keine Flames kommen. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Boot-Problem : unable to open the initial console
* once Gerald Preissler [EMAIL PROTECTED] wrote: Hallo Gerald, Eigentlich nicht. Nochmal die aus meiner Sicht relevanten Teile von lilo.conf : image=/vmlinuz label=Woody root=/dev/hdc12 image=/vmlinuz label=Gentoo root=/dev/hda6 Eben nicht: image=/vmlinuz hier liegt der Debian Kernel label=Woody root=/dev/hdc12 image=/vmlinuz hier liegt mit Sicherheit NICHT der Gentoo Kernel image=/pfad/zu/gentoo/vmlinz-2.4.23 label=Gentoo root=/dev/hda6 ... cu Steff -- BOFH Excuse #200: The monitor needs another box of pixels. pgp0.pgp Description: PGP signature
Boot-Problem : unable to open the initial console
Hallo, bei der Installation von Gentoo ist bei mir ein Problem aufgetreten, zu dessen Lösung hier vielleicht der eine oder andere einen Tip geben kann. Das Symptom ist einfach und frustrierend: Beim booten der Gentoo-Installation ist nach kurzer Zeit als letzte Meldung zu lesen warning: unable to open the initial console, dann erfolgt nach ca. 2 Sekunden ein Reboot. Wenn ich die Gentoo-Partition von Debian aus mounte, ist leider kein Log des Bootvorgangs zu finden, daher ist die Fehlermeldung ein händischer Mitschrieb. Folgende Rahmenbedingungen: Installation von einem laufenden Debian-System aus wie auf der Gentoo-Website im Installguide beschrieben, mit folgenden Abweichungen: - Bootmanager sollte lilo sein, das Schreiben des Bootsektors erfolgt von der Debian-Installation aus. Hier die /etc/lilo.conf (ohne Kommentare): lba32 boot=/dev/hda root=/dev/hda6 install=/boot/boot-menu.b map=/boot/map delay=20 prompt timeout=150 vga=normal default=Woody image=/vmlinuz label=Woody read-only root=/dev/hdc12 image=/vmlinuz label=Gentoo read-only root=/dev/hda6 / der Gentoo-Installation ist /dev/hda6, /boot ist /dev/hda1 - die Kernelkonfiguration habe ich von der Debian-Installation übertragen und dann mit make menuconfig noch um Support für ReiserFS erweitert. - die Installation des Kernel erfolgte nicht wie in der Anleitung beschrieben, sondern mit make install. Der Kernel unter /boot hat die gleiche Größe und das gleiche Erstellungsdatum wie unter /usr/src/linux/arch/i386/boot. Daher gehe ich davon aus, dass die Installation geklappt hat. Danach noch ein ln -s /boot/vmlinuz-2.4.20-gentoo-r9 /vmlinuz Kann mir jemand einen Tip geben, wie ich von hier aus weitermachen kann? TIA Jerry -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Boot-Problem : unable to open the initial console
On Tue, Dec 09, 2003 at 10:59:30PM +0100, Gerald Preissler wrote: Gentoo-Installation ist nach kurzer Zeit als letzte Meldung zu lesen warning: unable to open the initial console, dann erfolgt nach ca. 2 Sekunden ein Reboot. Normalerweise passiert das, wenn /dev/console zu diesem Zeitpunkt nicht existiert. Grüße, Torsten -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
CD Boot Problem
I am trying to install Debian on my computer. I used jigdo to get the iso. Then I burned the iso to cd. When I try to boot from the cd, the drive spins up then spins down a lot. Sometimes I get a message from the BIOS that there was a boot failure. Other times, It starts booting, but then I get a message from the software on the cd that there was an error and that I should try again. When I try to access the cd on another os, It is accessible, but it spins up and down a lot. Also when I try to small text files on the cd sometimes there is a long delay (45 sec or more). The drive works well with other cds though. I'm not sure what is wrong. MA
RE: CD Boot Problem
sounds like the cd media you burned has an error. this can be caused by a manufacturing error on the cd. burn another cdrom and give it a try. also, try not burning at full speed. sometimes people burn disks that are rated 12x at 30x+ and will make cd's that behave like you describe. Preston -Original Message-From: Mustafa Al-Shawaf [mailto:[EMAIL PROTECTED]Sent: Wednesday, July 30, 2003 8:49 AMTo: [EMAIL PROTECTED]Subject: CD Boot Problem I am trying to install Debian on my computer. I used jigdo to get the iso. Then I burned the iso to cd. When I try to boot from the cd, the drive spins up then spins down a lot. Sometimes I get a message from the BIOS that there was a boot failure. Other times, It starts booting, but then I get a message from the software on the cd that there was an error and that I should try again. When I try to access the cd on another os, It is accessible, but it spins up and down a lot. Also when I try to small text files on the cd sometimes there is a long delay (45 sec or more). The drive works well with other cds though. I'm not sure what is wrong. MA
Re: CD Boot Problem
On Wed, 30 Jul 2003, Mustafa Al-Shawaf wrote: I am trying to install Debian on my computer. I used jigdo to get the iso. Then I burned the iso to cd. When I try to boot from the cd, the drive spins up then spins down a lot. [ ... snip ... ] The drive works well with other cds though. I'm not sure what is wrong. By other cds, do you mean other burned cds, or regular pressed cds? I've seen some rather old CD drives (usually found on pentium and earlier computers) have problems with CD-R/CD-RW cds while working fine with regular cds. Another suggestion would be to check the block size if you are burning an iso image. ~ Jesse Meyer -- icq: 34583382 / msn: [EMAIL PROTECTED] / yim: tsunad We are what we pretend to be, so we must be careful about what we pretend to be. - Kurt Vonnegut Jr : Mother Night pgp0.pgp Description: PGP signature
Re: Boot-Problem mit fehlenden root-Rechten
* Matthias Weinhold [EMAIL PROTECTED] wrote: Hei Marc, Hi. versuch mal booten mit der Knoppix, dann auf die Konsole wechseln und alle Partitionen mit fdisk -f /dev/hdxx der Reihe nach durchzuchecken. Daran lag's nicht, aber trotzdem danke fuer die Antwort. Ich habe mittlerweile rausgekriegt (u.a. durch Tips von anderen), dass es daran lag, dass bei allen(!) Dateien die uid und gid auf 1000 gesetzt worden ist. Nachdem ich bei den entsprechenden Dateien den owner wieder auf root gesetzt habe, startete das System wieder und ich konnte mich auch wieder einloggen. Warum Knoppix wegen einer falschen Bootopiton die Rechte von allen Dateien geaendert hat, ist mir allerdings schleierhaft. Gruss Marc -- Softwarepatente? Nein, danke! -- http://patinfo.ffii.org GPG Key-Id: 0xDFF26B2F | Registered GNU/Linux User #227895 pgp0.pgp Description: PGP signature
Re: Boot-Problem mit fehlenden root-Rechten
Hei Marc, versuch mal booten mit der Knoppix, dann auf die Konsole wechseln und alle Partitionen mit fdisk -f /dev/hdxx der Reihe nach durchzuchecken. Ich habe manchmal ähnliche Probleme, wenn mein Söhnchen meint, während des bootens den Rechner nochmal reseten zu müssen, beschriebenes hilft bei mir immer. Grüße Matthias -- Ich kann allem Widerstehen, nur nicht der Versuchung. -- Oscar Wilde -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Boot-Problem mit fehlenden root-Rechten
Hi. Ich habe eben mal die LinuxTag-DVD mit Knoppix ausprobiert. Dort hatte ich irrtümlicherweise beim Booten die /-Partition meines Debian-Systems als Home angegeben. Knoppix lief ohne Probleme, aber wenn ich jetzt mein Woody von der Platte starte, können einige Befehle nicht mehr ausgeführt werden (z.B. mount), da ihnen anscheinend die nötigen Rechte fehlen. Die ersten Fehlermeldungen beim Booten sehen folgendermassen aus: (...) mount: only root can do that Acivating swap. Adding swap: 184736k swap-space (priority -1) mount: only root can do that *** Error! Cannot fsck root fs because it is not mounted read-only! mount: only root can do that (...) Dann kommen einige Fehlermeldungen von diversen Diensten und von modprobe, z.B.: modprobe: Can't locate module net-pf-xx Es werden beim Booten also keinerlei Dateisysteme eingebunden, auch /proc nicht. Zum Schluß erscheint die login-Aufforderung. Ein login mit $user oder root ergibt aber nur die Meldungen: setgid: Operation not permitted oder initgroups: Operation not permitted. Ich habe danach nochmal mit Knoppix gestartet, und mich etwas auf dem Woody-System umgeschaut, aber ich konnte auf den ersten Blick keine Änderungen feststellen. Wenn jemand einen Tip hat, an welcher Stelle genau ich nachschauen muß, wäre das super. Gruß Marc -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
boot problem with new kernel-any idas?
I recently downloaded, and using make-kpkg buildpackage, built a complete new kernel headers...etc. from a tarball( linux-2.4.21) downloaded from www.kernel.org. It installed with no problems, including running lilo. I rebooted and crapped out at the line freeing unused kernel memory. I have built many kernels over the years but I need to get new usb devices implemented as well as scsi emulation etc. for cd-burner mustek scanner mods builtin. I thought no problem and proceeded to implement the old kernel and start over. To my great surprise the old kernel now craps out at the exact same place. Kind of makes me think it,s something other than the new kernel...however all was working fine before the reboot. However this is a SID system and I have recently upgraded other apps...very carefully. avoiding buggy proggies via apt-listbug. Any ideas as to what is going on? Anyone know of ANY bugs yielding this problem? Thanks! John -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot problem with new kernel-any idas?
John Foster [EMAIL PROTECTED] writes: I recently downloaded, and using make-kpkg buildpackage, built a complete new kernel headers...etc. from a tarball( linux-2.4.21) downloaded from www.kernel.org. It installed with no problems, including running lilo. I rebooted and crapped out at the line freeing unused kernel memory. I think that's the last thing in the kernel boot sequence before it calls init. Do you have an initrd kernel? (The stock Debian kernels are, so if you copied /boot/config.* from a preexisting Debian kernel you probably do.) If so, did you build an initrd, and give a pointer to it in your lilo.conf file? -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
On Tue, 25 Mar 2003 22:33:31 -0500 [EMAIL PROTECTED] wrote: No, actually it makes great sense -- I just can't believe I might have left something so obvious out! (I suppose I may have thought IDE support was a default 'yes,' -- but I can see how it may be best assumed NOT, because SCSI is right popular Linux keeps me humble... (yet proud I use it :-) ) Debian began supporting initrd with the 2.4 series kernels. Almost everything gets built as modules, and the ones needed to actually boot the system are put into an initial RAM disk, which is loaded along with the kernel. Initrd is basically a way to provide limited module support before modules can be loaded from /lib/modules/kernel name. The *reason* it's there is so kitchen-sink kernels can support many kinds of hardware. When you compile your own kernel you only need to support the stuff in your own machine, so there's no need for initrd -- just compile floppy disk, hard drive and root filesystem support right in. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Boot problem
I have two Linuxes on my system -- one per hard disk. I run Libranet 2.0 from /dev/hda3, Tater Deb on hdb3 (I was curious about pure version), and, ahem, Winblows on hda1. I use Grub to manage the booting (came w/Libranet). Here's the rub-- one of times after which I recompiled a 2.4.16 kernel for the Official Deb (I got the source pkg. from the Libranet CD's), and carefully modified the /boot/grub/menu.lst on Libranet, I got a kernel panic on the subsequent boot. Here are the exact 5 last lines (they all seemed relevant): request_module[ide-disk]: Root fs not mounted hdb: driver not present VFS: Cannot open root device hdb3 or 03:43 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:43 (is this a sector or block designation or something?) These two next pieces of info. may be relevant as well: * I remember the last lines from the std. output of the last make bzImage before the panic in question said something about the image being created at I think 3,67 -- or some 3,XX that WASN'T the 43 referenced above. * when I booted into the official Deb. (again, on /dev/hdb3) with a rescue root=/dev/hdb3 and ran fdisk to check the partitioning, fdisk says that /dev/hdb3 overlaps /dev/hdb1 (don't ask where /dev/hdb2 went, I haven't the foggiest). Are there some arguments I can put in the /boot/grub/menu.lst statement about where to find where the real kernel image actually lives? TIA, Mark __ Try AOL and get 1045 hours FREE for 45 days! http://free.aol.com/tryaolfree/index.adp?375380 Get AOL Instant Messenger 5.1 for FREE! Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promos=380455 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
On Tue, 25 Mar 2003 21:01:55 -0500 [EMAIL PROTECTED] wrote: one of times after which I recompiled a 2.4.16 kernel for the Official Deb (I got the source pkg. from the Libranet CD's), and carefully modified the /boot/grub/menu.lst on Libranet, I got a kernel panic on the subsequent boot. Here are the exact 5 last lines (they all seemed relevant): request_module[ide-disk]: Root fs not mounted hdb: driver not present VFS: Cannot open root device hdb3 or 03:43 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:43 (is this a sector or block designation or something?) * when I booted into the official Deb. (again, on /dev/hdb3) with a rescue root=/dev/hdb3 and ran fdisk to check the partitioning, fdisk says that /dev/hdb3 overlaps /dev/hdb1 (don't ask where /dev/hdb2 went, I haven't the foggiest). You don't have IDE support for your hard drive, and that's the reason request-module [ide-disk] fails. In fact, you shouldn't see a request-module at all. In menuconfig, check ATA/IDE/MFM/RLL support - IDE, ATA and ATAPI Block devices - Include IDE/ATA-2 DISK support. I'll bet you have an M there. Put a * there, and try again. While you're at it, check File systems, and make sure whatever you use for a root filesystem has support compiled in. Also check Block devices and make sure Normal PC floppy disk support has a * there. Check out the newbiedoc on kernel compiling: http://newbiedoc.sourceforge.net/system/kernel-pkg.html Let us know if any of that doesn't work or doesn't make sense. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Boot problem
On Tue, Mar 25, 2003 at 09:01:55PM -0500, [EMAIL PROTECTED] wrote: request_module[ide-disk]: Root fs not mounted hdb: driver not present VFS: Cannot open root device hdb3 or 03:43 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:43 (is this... ^ That's a device number in hex, identifying hdb3. Documentation/devices.txt in the kernel source tree tells you everything. That file is as precious as ESR's guide to asking smart questions. These two next pieces of info. may be relevant as well: * I remember the last lines from the std. output of the last make bzImage before the panic in question said something about the image being created at I think 3,67 -- or some 3,XX that WASN'T the 43 referenced above. It was. 0x43 (hex) == 67 (decimal) * when I booted into the official Deb. (again, on /dev/hdb3) with a rescue root=/dev/hdb3 and ran fdisk to check the partitioning, fdisk says that /dev/hdb3 overlaps /dev/hdb1 (don't ask where /dev/hdb2 went, I haven't the foggiest). Sounds hosed, casters-up mode. Good luck, Nick -- x--x | What your soldier wants -- really, really wants -- | |is no-one shooting back at him. | | (Terry Pratchett, alt.fan.pratchett) | |--| | Nicolas Kratz [EMAIL PROTECTED] [EMAIL PROTECTED] | x--x pgp0.pgp Description: PGP signature
Re: Boot problem
[EMAIL PROTECTED] wrote: On Tue, 25 Mar 2003 21:01:55 -0500 [EMAIL PROTECTED] wrote: one of times after which I recompiled a 2.4.16 kernel for the Official Deb (I got the source pkg. from the Libranet CD's), and carefully modified the /boot/grub/menu.lst on Libranet, I got a kernel panic on the subsequent boot. Here are the exact 5 last lines (they all seemed relevant): request_module[ide-disk]: Root fs not mounted hdb: driver not present VFS: Cannot open root device hdb3 or 03:43 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 03:43 (is this a sector or block designation or something?) * when I booted into the official Deb. (again, on /dev/hdb3) with a rescue root=/dev/hdb3 and ran fdisk to check the partitioning, fdisk says that /dev/hdb3 overlaps /dev/hdb1 (don't ask where /dev/hdb2 went, I haven't the foggiest). You don't have IDE support for your hard drive, and that's the reason request-module [ide-disk] fails. In fact, you shouldn't see a request-module at all. In menuconfig, check ATA/IDE/MFM/RLL support - IDE, ATA and ATAPI Block devices - Include IDE/ATA-2 DISK support. I'll bet you have an M there. Put a * there, and try again. While you're at it, check File systems, and make sure whatever you use for a root filesystem has support compiled in. Also check Block devices and make sure Normal PC floppy disk support has a * there. Check out the newbiedoc on kernel compiling: http://newbiedoc.sourceforge.net/system/kernel-pkg.html Let us know if any of that doesn't work or doesn't make sense. Kevin No, actually it makes great sense -- I just can't believe I might have left something so obvious out! (I suppose I may have thought IDE support was a default 'yes,' -- but I can see how it may be best assumed NOT, because SCSI is right popular Linux keeps me humble... (yet proud I use it :-) ) Thanks! the Linux Librarian (Mark) __ Try AOL and get 1045 hours FREE for 45 days! http://free.aol.com/tryaolfree/index.adp?375380 Get AOL Instant Messenger 5.1 for FREE! Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promos=380455 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
please help! multi-boot problem, i think
I was running windows me, used partition magic to partition linux partitions, then installed debian 3. Unwisely, I let it boot from the mbr. Now windows won't load at all, saying system files are missing or corrupt. lilo.conf looks like this for where windows should be: other=/dev/hda2 label=Other(hda2) It also says that Windows is at hda6, which can't be right (and doesn't even give me the error messages I get when trying to boot from hda2). When I boot from a windows me startup disk, c: is my data partition, but before installing debian, c: was naturally my windows partition. Now I'm stuck, b/c not only am I unfamiliar with Linux, I have installed only the minimal web-installer distribution of debian. Please help if you have any ideas. Thank you! _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: please help! multi-boot problem, i think
Wesley Harris said: I was running windows me, used partition magic to partition linux partitions, then installed debian 3. Unwisely, I let it boot from the mbr. Now windows won't load at all, saying system files are missing or corrupt. more info is needed: fdisk -l /dev/hda mount each of the win32 partitions and show output of ls of them e.g. if win9x is on /dev/hda2 then mkdir /mnt/c ; mount /dev/hda2 /mnt/c -t vfat same for any other win32 partitions, mount them on different mount points. sounds like you may of wiped out the wrong partition? not sure without more info. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
boot problem
Hi i have just installed woody on my scsi HD. My problem is when i try to boot from it i get a screen like this : 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 and so on. Why? i can start woody from the fdd.! Thanks Mikkel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot problem
#include hallo.h * Mikkel Liisberg [Wed, Feb 12 2003, 04:51:10PM]: i have just installed woody on my scsi HD. My problem is when i try to boot from it i get a screen like this : 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 and so on. Why? The mapping btw. BIOS and Kernel views differ. Look in the lilo.conf for an example for setting that mapping manually. Gruss/Regards, Eduard. -- Hallo Birkenstockträger! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Dual-Boot Problem
Hallo Leute! Ich möchte von SuSE 7.3 auf Debian Woody umsteigen. Dazu habe ich einen bestehenden Rechner eine neue Platte eingebaut und Debian installiert. Soweit funktioniert auch alles. Danach habe ich die alte Platte (SuSE, /dev/hda) wieder als Master eingebaut und die neue Platte (Debian, /dev/hdb) als Slave. In lilo.conf der SuSE-Platte habe ich ein weiters Boot-Image (/dev/hdb3) angelegt und lilo ausgeführt. Der Rechner bootet zwar Debian, aber es funktionieren manche Teile (z.B. das Netzwerk) nicht. Ich vermute, daß noch irgendwo Einträge vorhanden sind und geändert werden müssen, da ich Debian ja als /dev/hda installiert habe und jetzt als /dev/hdb verwende. Der Grund für diese komplizierte Vorgangsweise liegt eigentlich darin, nach einer gewissen Übergangsphase die Debian-Platte wieder als /dev/hda in dem Rechner zu belassen und die andere danach anderwertig zu verwenden. Hat jemand eine Idee? Schöne Grüße Oliver -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dual-Boot Problem
Oliver Vecernik schrieb: Hallo Leute! Ich möchte von SuSE 7.3 auf Debian Woody umsteigen. Dazu habe ich einen bestehenden Rechner eine neue Platte eingebaut und Debian installiert. Soweit funktioniert auch alles. Danach habe ich die alte Platte (SuSE, /dev/hda) wieder als Master eingebaut und die neue Platte (Debian, /dev/hdb) als Slave. In lilo.conf der SuSE-Platte habe ich ein weiters Boot-Image (/dev/hdb3) angelegt und lilo ausgeführt. Der Rechner bootet zwar Debian, aber es funktionieren manche Teile (z.B. das Netzwerk) nicht. Ich vermute, daß noch irgendwo Einträge vorhanden sind und geändert werden müssen, da ich Debian ja als /dev/hda installiert habe und jetzt als /dev/hdb verwende. Der Grund für diese komplizierte Vorgangsweise liegt eigentlich darin, nach einer gewissen Übergangsphase die Debian-Platte wieder als /dev/hda in dem Rechner zu belassen und die andere danach anderwertig zu verwenden. Hat jemand eine Idee? Schöne Grüße Oliver also bei einem Festplattenwechsel muß man lediglich die lilo.conf, fstab und evtl. noch automount-Geschichten und ein paar private Skripte die die Platte mounten ändern. Das sollte es gewesen sein. Jedenfalls hat das Netzwerk nix damit am Hut. Vielleicht mal route -n , ifconfig usw. kontrollieren. Und mal die dumme Frage, wieso schiebst du nicht die Suse nach hdb? Da musst Du auch nur lilo.conf, ... ändern. Wenn Du die Suse-Platte nicht mehr willst kannst Du sie einfach wegnehmen und brauchst an Debian nicht noch herumschrauben und kannst Dir sichersein das Debian auf hda läuft. Stefan -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dual-Boot Problem
Stefan Keul schrieb: Oliver Vecernik schrieb: [...] also bei einem Festplattenwechsel muß man lediglich die lilo.conf, fstab und evtl. noch automount-Geschichten und ein paar private Skripte die die Platte mounten ändern. Das sollte es gewesen sein. Jedenfalls hat das Netzwerk nix damit am Hut. Vielleicht mal route -n , ifconfig usw. kontrollieren. Und mal die dumme Frage, wieso schiebst du nicht die Suse nach hdb? Da musst Du auch nur lilo.conf, ... ändern. Wenn Du die Suse-Platte nicht mehr willst kannst Du sie einfach wegnehmen und brauchst an Debian nicht noch herumschrauben und kannst Dir sichersein das Debian auf hda läuft. Ok, hab ich gemacht. Also Debian auf hda und SuSE auf hdb. In /etc/lilo.conf habe ich ergänzt: other=/dev/hdb3 label=SuSE Leider meldet lilo: Fatal: First sector of /dev/hdb3 doesn't have a valid boot signature Wenn ich die beiden Platten aber vertausche, booted SuSE. Hat noch jemand einen Tipp? Oliver -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dual-Boot Problem
Oliver Vecernik schrieb: [...] Ok, hab ich gemacht. Also Debian auf hda und SuSE auf hdb. In /etc/lilo.conf habe ich ergänzt: other=/dev/hdb3 label=SuSE Leider meldet lilo: Fatal: First sector of /dev/hdb3 doesn't have a valid boot signature Wenn ich die beiden Platten aber vertausche, booted SuSE. Hat noch jemand einen Tipp? Noch eine Ergänzung: /dev/hdb1 ist eingehängt auf /boot /dev/hdb3 ist eingehängt auf / Wenn ich in lilo.conf statt /dev/hdb3 /dev/hdb1 nehme, dann läuft lilo zwar fehlerfrei (Added SuSE), aber beim Booten steht: LIWrong loader, giving up... Ich versteh' jetzt gar nichts mehr... Kann mich jemand erleuchten? Oliver -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dual-Boot Problem
Quoting Oliver Vecernik [EMAIL PROTECTED]: Ok, hab ich gemacht. Also Debian auf hda und SuSE auf hdb. In /etc/lilo.conf habe ich ergänzt: other=/dev/hdb3 label=SuSE Leider meldet lilo: Fatal: First sector of /dev/hdb3 doesn't have a valid boot signature S. lilo.conf(5). Da müsste so etwas stehen: image=/boot/Name_des_SuSE_Kernels label=SuSE read-only root=/dev/hdb3 HTH, Meinolf -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dual-Boot Problem
Hallo Oliver Oliver Vecernik wrote: Oliver Vecernik schrieb: [...] Ok, hab ich gemacht. Also Debian auf hda und SuSE auf hdb. In /etc/lilo.conf habe ich ergänzt: other=/dev/hdb3 label=SuSE Leider meldet lilo: Fatal: First sector of /dev/hdb3 doesn't have a valid boot signature Wenn ich die beiden Platten aber vertausche, booted SuSE. Hat noch jemand einen Tipp? Noch eine Ergänzung: /dev/hdb1 ist eingehängt auf /boot /dev/hdb3 ist eingehängt auf / Wenn ich in lilo.conf statt /dev/hdb3 /dev/hdb1 nehme, dann läuft lilo zwar fehlerfrei (Added SuSE), aber beim Booten steht: LIWrong loader, giving up... Vorsicht erst einmal, es könnte totaler Blödsinn sein, was ich jetzt schreibe. ;-) Du kannst über lilo zwei Wege nehmen, um ein System zu booten: - über den Bootrecord der Partition, dann muss der natürlich auch entsprechend geschrieben sein; in lilo.conf steht dann: other=/dev... - direkt den Kernel (image=...); dafür muss der Bootkernel zum Zeitpunkt des Schreibens von lilo greifbar sein, also die boot-Partition des anderen Linux gemountet sein und in der lilo.conf der _aktuelle_ (beim Schreiben von lilo gültigen) Pfad angeben werden. Gruß Rüdiger -- __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Möchten Sie mit einem Gruß antworten? http://grusskarten.yahoo.de -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dual-Boot Problem
Hallo Meinolf, * Meinolf Sander schrieb [16-10-02 14:24]: Quoting Oliver Vecernik [EMAIL PROTECTED]: Ok, hab ich gemacht. Also Debian auf hda und SuSE auf hdb. In /etc/lilo.conf habe ich ergänzt: other=/dev/hdb3 label=SuSE Das geht nur, wenn suse's lilo auf /dev/hdb3 eingetragen ist. Wenn das nicht der Fall ist, dann ... S. lilo.conf(5). Da müsste so etwas stehen: image=/boot/Name_des_SuSE_Kernels label=SuSE read-only root=/dev/hdb3 ... musst du so vorgehen. Gruss Udo -- Alkohol soll ja gleichgültig machen. Na und? msg21577/pgp0.pgp Description: PGP signature
Re: Dual-Boot Problem
Udo Mueller schrieb: [...] S. lilo.conf(5). Da müsste so etwas stehen: image=/boot/Name_des_SuSE_Kernels label=SuSE read-only root=/dev/hdb3 ... musst du so vorgehen. Gut , habe ich gemacht. Nur meckert lilo wieder, daß er den Pfad /boot/vmlinuz nicht finden kann (was ja eigentlich auch stimmt, da die /boot-Partition ja auf /dev/hdb1 liegt und / auf /dev/hdb3. Nur steht das ja in /etc/fstab der SuSE-Platte und ist jetzt unter Debian nicht aktiv. Habt Ihr noch den entscheidenden Tipp für mich? Grüße Oliver -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dual-Boot Problem
Oliver Vecernik wrote: Habt Ihr noch den entscheidenden Tipp für mich? Zum Beispiel könntest Du meine vorige mail lesen. Gruß Rüdiger -- __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Yahoo! präsentiert als offizieller Sponsor das Fußball-Highlight des Jahres: - http://www.FIFAworldcup.com -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: Dual-Boot Problem
Hallo Oliver, * Oliver Vecernik schrieb [16-10-02 16:51]: Udo Mueller schrieb: ... musst du so vorgehen. Gut , habe ich gemacht. Nur meckert lilo wieder, daß er den Pfad /boot/vmlinuz nicht finden kann (was ja eigentlich auch stimmt, da die /boot-Partition ja auf /dev/hdb1 liegt und / auf /dev/hdb3. Nur steht das ja in /etc/fstab der SuSE-Platte und ist jetzt unter Debian nicht aktiv. Auf Rüdiger hören oder: Du sagtest, dass /dev/hdb1 auf /boot eingehängt ist. Meinst du das /boot von Debian oder von Suse? Benutzt du für beide Systeme das gleiche /boot? Wenn Debian sein eigenes hat, dann musst du unter Debian hdb1 zur Vefügung stellen, z.B. unter /mnt/boot und in der lilo.conf entsprechend den Pfad angeben: image=/mnt/boot/kernel label=SuSE root=/dev/hdb3 Danach dann lilo ausführen. Das Ganze geht aber nur, wenn kernel auch auf /hdb1 drauf ist und hdb1 auf /mnt/boot gemountet ist. Gruss Udo -- F: Word? Was ist das? A: Das ist wohl das Programm, das ursrpünglich einmal Text heißen sollte. Da es aber für längere Dokumente ungeeignet ist, wurde es umbenannt. Inzwischen kann es aber bereits 97 Wörter verwalten. msg21584/pgp0.pgp Description: PGP signature
Re: Dual-Boot Problem
Ruediger Noack schrieb: [...] LIWrong loader, giving up... Vorsicht erst einmal, es könnte totaler Blödsinn sein, was ich jetzt schreibe. ;-) Du kannst über lilo zwei Wege nehmen, um ein System zu booten: - über den Bootrecord der Partition, dann muss der natürlich auch entsprechend geschrieben sein; in lilo.conf steht dann: other=/dev... - direkt den Kernel (image=...); dafür muss der Bootkernel zum Zeitpunkt des Schreibens von lilo greifbar sein, also die boot-Partition des anderen Linux gemountet sein und in der lilo.conf der _aktuelle_ (beim Schreiben von lilo gültigen) Pfad angeben werden. Wie gesagt: other=/dev/hdb ergibt: LIWrong loader, giving up... Ich hab's auch anders herum (also von SuSE als /dev/hda Debian auf /dev/hdb) probiert, da hängt sich lilo beim Booten gleich auf und schreibt lauter '40 ' auf den Schirm. Es muß irgend ein Problem mit den Versionen geben. SuSE lilo ist 21.7 und Debian 22.2. Leider kann ich auch unter SuSE den lilo von Debian nicht einfach verwenden, es gibt einen Versionskonflikt. Weiß noch jemand Rat? Grüße Oliver -- Häufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
