Re: problem booting a new server on FreeBSD
On Tue, Jan 11, 2011 at 7:16 PM, Robert Bonomi bon...@mail.r-bonomi.com wrote: Try booting _with_ a disk in the CD drive. Well, I was at least for the first install since I booted from CD, time was the same about 1m to 1m30 before it boots. Also, assuming these are parallel ATA drives, check the master/slave jumper settings -- both on the CDROM and any other device on the same controller. Not a bad idea, have actually to open of the servers tomorrow so will check on that. Cheers, Steph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem booting a new server on FreeBSD
On Wed, Jan 12, 2011 at 2:03 AM, FRLinux frli...@gmail.com wrote: On Tue, Jan 11, 2011 at 7:16 PM, Robert Bonomi bon...@mail.r-bonomi.com wrote: Try booting _with_ a disk in the CD drive. Well, I was at least for the first install since I booted from CD, time was the same about 1m to 1m30 before it boots. Also, assuming these are parallel ATA drives, check the master/slave jumper settings -- both on the CDROM and any other device on the same controller. Not a bad idea, have actually to open of the servers tomorrow so will check on that. Cheers, Steph Try setting hint.atkbdc.0.disabled=”1 and hint.atkbd.0.disabled=”1″ in /boot/device.hints . This should solve your boot delay problems. If I am not wrong, it relates to usb keyboard. With regards Amitabh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem booting a new server on FreeBSD
On Fri, Jan 7, 2011 at 3:37 PM, FRLinux frli...@gmail.com wrote: When booting, i get to the screen where I can select which boot process i want for FreeBSD (normal, without ACPI, debug, single, etc...). Regardless of the option I select, it starts flickering the rotating cursor (\|/-) then freezes completely with no information. I'll respond to myself on this, turns out that if we wait between one and one minute thirty, boot actually happens without any error... I'll include a dmesg just for the record: Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RC1 #0: Wed Dec 22 17:34:20 UTC 2010 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (2399.98-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206c2 Family = 6 Model = 2c Stepping = 2 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x29ee3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AESNI AMD Features=0x2c100800SYSCALL,NX,Page1GB,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 8150986752 (7773 MB) ACPI APIC Table: INTEL S5500HCV FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 18 cpu5 (AP): APIC ID: 19 cpu6 (AP): APIC ID: 20 cpu7 (AP): APIC ID: 21 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 acpi0: INTEL S5500HCV on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 cpu4: ACPI CPU on acpi0 cpu5: ACPI CPU on acpi0 cpu6: ACPI CPU on acpi0 cpu7: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 28 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 igb0: Intel(R) PRO/1000 Network Connection version - 2.0.7 port 0x2020-0x203f mem 0xb3a2-0xb3a3,0xb3a44000-0xb3a47fff irq 40 at device 0.0 on pci1 igb0: Using MSIX interrupts with 5 vectors igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb0: [ITHREAD] igb0: Ethernet address: 00:15:17:fd:1e:54 igb1: Intel(R) PRO/1000 Network Connection version - 2.0.7 port 0x2000-0x201f mem 0xb3a0-0xb3a1,0xb3a4-0xb3a43fff irq 28 at device 0.1 on pci1 igb1: Using MSIX interrupts with 5 vectors igb1: [ITHREAD] igb1: [ITHREAD] igb1: [ITHREAD] igb1: [ITHREAD] igb1: [ITHREAD] igb1: Ethernet address: 00:15:17:fd:1e:55 pcib2: ACPI PCI-PCI bridge irq 24 at device 3.0 on pci0 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 30 at device 7.0 on pci0 pci3: ACPI PCI bus on pcib3 3ware device driver for 9000 series storage controllers, version: 3.80.06.003 twa0: 3ware 9000 series Storage Controller port 0x1000-0x10ff mem 0xb000-0xb1ff,0xb390-0xb3900fff irq 30 at device 0.0 on pci3 twa0: [ITHREAD] twa0: INFO: (0x15: 0x1300): Controller details:: Model 9650SE-24M8, 24 ports, Firmware FE9X 4.10.00.007, BIOS BE9X 4.08.00.002 pcib4: ACPI PCI-PCI bridge irq 32 at device 9.0 on pci0 pci4: ACPI PCI bus on pcib4 pci0: base peripheral, interrupt controller at device 16.0 (no driver attached) pci0: base peripheral, interrupt controller at device 16.1 (no driver attached) pci0: base peripheral, interrupt controller at device 17.0 (no driver attached) pci0: base peripheral, interrupt controller at device 17.1 (no driver attached) pci0: base peripheral, interrupt controller at device 20.0 (no driver attached) pci0: base peripheral, interrupt controller at device 20.1 (no driver attached) pci0: base peripheral, interrupt controller at device 20.2 (no driver attached) pci0: base peripheral, interrupt controller at device 20.3 (no driver attached) pci0: base peripheral at device 22.0 (no driver attached) pci0: base peripheral at device 22.1 (no driver attached) pci0: base peripheral at device 22.2 (no driver attached) pci0: base peripheral at device 22.3 (no driver attached) pci0: base peripheral at device 22.4 (no driver attached) pci0: base peripheral at device 22.5 (no driver attached) pci0: base peripheral at device 22.6 (no driver attached) pci0: base peripheral at device 22.7 (no driver attached) uhci0: Intel 82801JI (ICH10) USB controller USB-D port
Re: problem booting a new server on FreeBSD
On Mon, Jan 10, 2011 at 5:21 PM, FRLinux frli...@gmail.com wrote: On Fri, Jan 7, 2011 at 3:37 PM, FRLinux frli...@gmail.com wrote: When booting, i get to the screen where I can select which boot process i want for FreeBSD (normal, without ACPI, debug, single, etc...). Regardless of the option I select, it starts flickering the rotating cursor (\|/-) then freezes completely with no information. I'll respond to myself on this, turns out that if we wait between one and one minute thirty, boot actually happens without any error... I'll include a dmesg just for the record: Where during the boot process does this happeb? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem booting a new server on FreeBSD
On Mon, Jan 10, 2011 at 11:29 PM, Chris Brennan xa...@xaerolimit.net wrote: Where during the boot process does this happeb? As soon as you select any of the options of the boot (normal boot, boot without ACPI, boot single mode, etc...). It sits there for about 1mn to 1mn30 and then boots fine. We put the second server in production today, same CPU type and motherboard, same behavior. Cheers, Steph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem booting a new server on FreeBSD
On Mon, Jan 10, 2011 at 6:41 PM, FRLinux frli...@gmail.com wrote: On Mon, Jan 10, 2011 at 11:29 PM, Chris Brennan xa...@xaerolimit.net wrote: Where during the boot process does this happeb? As soon as you select any of the options of the boot (normal boot, boot without ACPI, boot single mode, etc...). It sits there for about 1mn to 1mn30 and then boots fine. We put the second server in production today, same CPU type and motherboard, same behavior. A stab in the dark here tells me a slow device ... but what, I do not know. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: problem booting a new server on FreeBSD
On Mon, Jan 10, 2011 at 11:55 PM, Chris Brennan xa...@xaerolimit.net wrote: A stab in the dark here tells me a slow device ... but what, I do not know. Yes, apparently, could well be the CDROM drive, it's a laptop format one (slim). Someone responded to me off-list mentioning the same problem happened to him. 1mn delay is no big deal on servers being rebooted every 2 months or so, besides I get to use FreeBSD on them since they work perfectly bar this delay. Cheers, Steph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
problem booting a new server on FreeBSD
Hello, We have purchased a brand new server running an Intel Motherboard which boots fine on Linux but not on FreeBSD, I have tried FreeBSD 8.1 and 8.2-RC1 without success. The motherboard is a S5500HCV (Version: E40912-455). It has 2 SATA drives connected in compatible mode in the BIOS (also tried AHCI without success). It also hosts a 3ware RAID controller (9750 series, 16 ports). When booting, i get to the screen where I can select which boot process i want for FreeBSD (normal, without ACPI, debug, single, etc...). Regardless of the option I select, it starts flickering the rotating cursor (\|/-) then freezes completely with no information. I have disabled a few options in the BIOS including advanced ACPI states for the CPU (Intel Xeon E5620), disabled HT and speedstep without much success. Any hint welcome, this server with be an NFS box and I don't fancy having Linux running on it. I am including the linux lspci to show what's on the box: [r...@localhost ~]# lspci 00:00.0 Host bridge: Intel Corporation 5500 I/O Hub to ESI Port (rev 22) 00:01.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 1 (rev 22) 00:03.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 3 (rev 22) 00:07.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 7 (rev 22) 00:09.0 PCI bridge: Intel Corporation 5520/5500/X58 I/O Hub PCI Express Root Port 9 (rev 22) 00:10.0 PIC: Intel Corporation 5520/5500/X58 Physical and Link Layer Registers Port 0 (rev 22) 00:10.1 PIC: Intel Corporation 5520/5500/X58 Routing and Protocol Layer Registers Port 0 (rev 22) 00:11.0 PIC: Intel Corporation 5520/5500 Physical and Link Layer Registers Port 1 (rev 22) 00:11.1 PIC: Intel Corporation 5520/5500 Routing Protocol Layer Register Port 1 (rev 22) 00:13.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub I/OxAPIC Interrupt Controller (rev 22) 00:14.0 PIC: Intel Corporation 5520/5500/X58 I/O Hub System Management Registers (rev 22) 00:14.1 PIC: Intel Corporation 5520/5500/X58 I/O Hub GPIO and Scratch Pad Registers (rev 22) 00:14.2 PIC: Intel Corporation 5520/5500/X58 I/O Hub Control Status and RAS Registers (rev 22) 00:14.3 PIC: Intel Corporation 5520/5500/X58 I/O Hub Throttle Registers (rev 22) 00:15.0 PIC: Intel Corporation 5520/5500/X58 Trusted Execution Technology Registers (rev 22) 00:16.0 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.1 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.2 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.3 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.4 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.5 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.6 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:16.7 System peripheral: Intel Corporation 5520/5500/X58 Chipset QuickData Technology Device (rev 22) 00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1 00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2 00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3 00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90) 00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller 00:1f.2 IDE interface: Intel Corporation 82801JI (ICH10 Family) 4 port SATA IDE Controller #1 00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller 00:1f.5 IDE interface: Intel Corporation 82801JI (ICH10 Family) 2 port SATA IDE Controller #2 01:00.0 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02) 01:00.1 Ethernet controller: Intel Corporation 82575EB Gigabit Network Connection (rev 02) 03:00.0 RAID bus controller: 3ware Inc 9750 SAS2/SATA-II RAID PCIe (rev 05) 06:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G200e [Pilot] ServerEngines (SEP1) (rev 02) fe:00.0 Host bridge: Intel Corporation Xeon 5600 Series QuickPath Architecture Generic Non-core Registers (rev 02) fe:00.1 Host bridge: Intel Corporation Xeon 5600
Big Problem booting the freebsd7 AMD64 !! I can't boot the cd! It frozes
The booting process stops at the line mounting root ufs /dev/md0 (Starting with the option for no acpi ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
video mode problem booting 6.2 CD
Has anyone had any problem with the booting of 6.2 release CD? I have an older server that is running 5.5 and was going to do a binary upgrade to 6.2. When I try to boot the 6.2 release CD 1, right after the loader message, the video gets funny, I see it trying to do what looks like drawing on the screen, but just see some flashing. It looks like some kind of video mode switch the builtin VGA adapter is having trouble with. I was wondering if anyone else had seen this problem and possibly had a work around. -Derek [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem booting from memory-stick with ASUS A7V-133
Hi all, hope this is the right list. I have a problem with booting from a 128MB USB-memory-stick with the ASUS A7V-133 motherboard. I downloaded the boot-floppy-imageboot.flp (version 6.2) from the FreeBSD-FTP-server and dd-ed it to a memory stick. Booting from this stick works fine with every other computer I have (a notebook and a newer workstation also with an ASUS-board). But trying to boot from the stick with the A7V gives me the following output: - 8 --- Not ufs Not ufs No /boot/loader FreeBSD/i386 boot Default: 0:fd(0,a)/boot/kernel/kernel boot: Not ufs No /boot/kernel/kernel - 8 --- So it seems to me that the BIOS reads the first sector of the memory-stick (the MBR) executes the code but then the bootloader seems to have problems with the drive geometry or something like this. So does anybody on this list have had similar problems or can give me a hint what to do to solve this problem? BTW: I know that the used floppy-image is just for installation and I'm not able to boot a fully running system from it. But it seems to me the best/fastest way to test whether booting from the stick works or not. Thanks a lot in advance Stefan _ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071distributionid=0066 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem booting from memory-stick with ASUS A7V-133
[EMAIL PROTECTED] wrote: Hi all, hope this is the right list. I have a problem with booting from a 128MB USB-memory-stick with the ASUS A7V-133 motherboard. I downloaded the boot-floppy-imageboot.flp (version 6.2) from the FreeBSD-FTP-server and dd-ed it to a memory stick. Booting from this stick works fine with every other computer I have (a notebook and a newer workstation also with an ASUS-board). But trying to boot from the stick with the A7V gives me the following output: - 8 --- Not ufs Not ufs No /boot/loader FreeBSD/i386 boot Default: 0:fd(0,a)/boot/kernel/kernel boot: Not ufs No /boot/kernel/kernel - 8 --- What happens if you enter: 0:da(0,a)/boot/kernel/kernel ...at the boot: prompt (as opposed to fd(0,a)? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem booting from memory-stick with ASUS A7V-133
Hi Steve, I have a problem with booting from a 128MB USB-memory-stick with the ASUS A7V-133 motherboard. I downloaded the boot-floppy-imageboot.flp (version 6.2) from the FreeBSD-FTP-server and dd-ed it to a memory stick. Booting from this stick works fine with every other computer I have (a notebook and a newer workstation also with an ASUS-board). But trying to boot from the stick with the A7V gives me the following output: - 8 --- Not ufs Not ufs No /boot/loader FreeBSD/i386 boot Default: 0:fd(0,a)/boot/kernel/kernel boot: Not ufs No /boot/kernel/kernel - 8 --- What happens if you enter: 0:da(0,a)/boot/kernel/kernel ...at the boot: prompt (as opposed to fd(0,a)? first of all: Thanks a lot for you very quick response. Entering this at the prompt gives me the following output (includes the entered data): - 8 --- boot: 0:da(0,a)/boot/kernel/kernelerror 1 lba 0 No /boot/kernel/kernel - 8 --- Any other things I should try? Best regards, Stefan _ Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! http://smartsurfer.web.de/?mc=100071distributionid=0066 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem booting
Hi all I know that this is regarding pfSense (1.0 beta3), but since it is running with a FreeBSD 6.1 RC1 kernel, I will try asking for help here. I've installed pfSense on the harddrive (tried this with a SATA disk and a normal disk), but when I boot I get a lot of junk. I can get: FreeBSD/i386 boot Default: 0:ad(0,a)/boot/loader boot: Right after this I get a lof of junk (registers and their values in hex) running endlessly down the screen. Any idea what's wrong? br db ps: The CPU is an intel and the motherboard is an Asus P5P800 SE. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problem booting FreeBSD 6.0 on IBM Blade
Hi I'm having a problem installing freebsd on an ibm blade the problem I face is that during boot, it always stops in OK prompt with the message can't load 'kernel' CD Loder 1.2 Building the boot loader arguments Looking up /BOOT/LOADER... Found Relocating the loader and the BTX Starting the BTX loader BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 630kB/2620340kB available memory FreeBSD/i386 bootstrap loader , Revision 1.1 ([EMAIL PROTECTED], Thu Nov 3 07:33:10 UTC 2005) \ can't load 'kernel' Type '?' for a list of commands, 'help' for more detailed.. can anyone point me out... it seems that when I try type in load /boot/kernel/kernel I get ? instead of / kveðja Gestur ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem booting FreeBSD 6.0 on IBM Blade
Gestur A. Grjetarsson wrote: Hi I'm having a problem installing freebsd on an ibm blade the problem I face is that during boot, it always stops in OK prompt with the message can't load 'kernel' [...] can anyone point me out... it seems that when I try type in load /boot/kernel/kernel I get ? instead of / Hi there - I don't think I know the answer , but I've managed to figure things out in the past by issuing 'lsdev' (no quotes) from that point and see what it says/ what devices it can see. Then you can usually change where it tries to find the kernel (passing the right path from the hardware/BIOs point of view). (and again, maybe not ;) ) hope it helps. Beto ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problem booting 5.3STABLE from USB2 flash drive
Hello, I'm hoping to use freebsd as a custom router. To minimize noise and failure points, I was hoping to boot from a USB2 flash stick which have gotten dirt cheap. I downloaded 5.3RELEASE-i386-miniinst.iso and burned it to CD - stuck my 512MB flash drive into a USB port, and let the CD boot up. Everything appears to work, in that the installer lets me partition and format device da0 fine as well as copy over all the files (doing a minimal base install), but after it finishes everything and goes to reboot, the machine just hangs. After a hard reset, at boot time I get: F1 FreeBSD Default: F1 but then the box just hangs there locked up tight as a drum. If instead of choosing the boot loader option during install, I choose the standard MBR option after reset, I get: No Operating System Seems that the boot loader option almost works - but not quite. Does anyone know what might be wrong. Possibly some sort of USB initialize timing problem with the kernel? FWIW, the board boots DOS fine off the USB key, so I know the BIOS/board are working as intended. Thoughts? Thanks, Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problem booting 5.2.1
(sorry for reposting this but i guess freebsd-bugs was the wrong place) i've installed 5.2.1 and after creating a new fat32 partition on the same disk it stopped booting, however as i had problems during the install i hope the description here should help narrow it down. - when i got the computer i had 2 preformatted fat32 partitions, so before installing i destroyed the second one and created a new smaller one so i could fit freebsd on a new. i started the installer and got created a partition and selected the boot manager, however when doing commit the installer complained about not being able to create/use a node named something in the lines of ad1s3.. (my guess is that there was no device present for the 3rd partition). i went back into XP and removed the second partition from there. after that the installer (kern/mfsroot floppies) refused to boot. after trying some things i was able to get the installer to start again by recreating the second partition i had when i did my first try. this time i deleted the second partition from within the installer and after that i was able to successfully install fbsd on a second partition (kinda confirms my suspicion about the installer, it might just be that a few nodes is missing from the mfsroot maybe?) having installed i was successful in booting both xp and fbsd. but i had 12 gigs of unused space after the bsd partition so i created a new fat32 drive from within xp, after doing that fbsd stopped booting. trying to boot the installer again gave the same error i had before with it hanging during boot. the UFS2 partition is still intact as i can access it thru the bootloader, using show and lsmod from within the bootloader also shows that it's trying to use the correct root. the hanging kernel pops up in slightly different places depending on if i try to boot the installer or the installed kernel. but roughly in the same place during device initialization, the installer kernel hangs after some pci_cfgintr line and the installed one hangs after displaying something about the agp bus (setting the verbose flag while booting shows the kernel saying setting setting gatt size to 256mb. however i guess that these lines are unrelated as i was able to install the kernel and even start Xfree. and that the problems has been connected to me changing the partition layout. but i hope that you can somewhat guess where the kernel gets stuck. the kernel approximately displays around 15-20 lines of output before hanging. Thanks in advance. / Jonas Lund ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem booting WinXP from second drive
On Sun, 1 Feb 2004 13:36:27 -0800, Relayer [EMAIL PROTECTED] wrote: I have a machine with FreeBSD 4.2 running on one drive. I wanted to try dual booting and mucking about with wine, so I decided to install WinXP as well. To avoid messing up my primary drive, I thought I would be able to accomplish the process in the following way: 1. disconnect primary drive 2. connect second drive (so it looks like the only one in the PC) and install WinXP on it 3. verify that WinXP boots off this drive 4. install FreeBSD boot loader on this drive 5. verify that WinXP boots using FreeBSD boot loader All works as expected to this point. Then I hook up the primary drive again and reboot. I see the following at boot time: F1: FreeBSD F2: FreeBSD F5: Drive 1 I hit F5. Then I see F1: DOS F5: Drive 0 When I hit F1, I expect WinXP to boot. But nothing happens. The machine just sits there. I have scanned a lot of material in the Handbook and on google today and yesterday, but I cannot figure out what I did wrong. Does anybody have any ideas that don't involve using grub or gag or something else? The sleight-of-hand with the drives is unnecessary. :) Let Windows stay on the first drive where it wants to be. FreeBSD is happy on the second drive. The FreeBSD boot loader must be installed on *both* drives. The loader will call your XP drive ??? if it's formatted using NTFS. It will boot XP just fine, it's just that there are several OSs that have filesystems resembling NTFS (e.g., OS/2 and QNX), and the FreeBSD bootloader doesn't have the extra space used by fancier bootloaders to store multiple user-selectable names. Jud ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem booting WinXP from second drive
I have a machine with FreeBSD 4.2 running on one drive. I wanted to try dual booting and mucking about with wine, so I decided to install WinXP as well. To avoid messing up my primary drive, I thought I would be able to accomplish the process in the following way: 1. disconnect primary drive 2. connect second drive (so it looks like the only one in the PC) and install WinXP on it 3. verify that WinXP boots off this drive 4. install FreeBSD boot loader on this drive 5. verify that WinXP boots using FreeBSD boot loader All works as expected to this point. Then I hook up the primary drive again and reboot. I see the following at boot time: F1: FreeBSD F2: FreeBSD F5: Drive 1 I hit F5. Then I see F1: DOS F5: Drive 0 When I hit F1, I expect WinXP to boot. But nothing happens. The machine just sits there. I have scanned a lot of material in the Handbook and on google today and yesterday, but I cannot figure out what I did wrong. Does anybody have any ideas that don't involve using grub or gag or something else? Thanks OP ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem booting WinXP from second drive
On Sun, 2004-02-01 at 15:36, Relayer wrote: [... snip ...] Then I hook up the primary drive again and reboot. I see the following at boot time: F1: FreeBSD F2: FreeBSD F5: Drive 1 I hit F5. Then I see F1: DOS F5: Drive 0 When I hit F1, I expect WinXP to boot. But nothing happens. The machine just sits there. I have scanned a lot of material in the Handbook and on google today and yesterday, but I cannot figure out what I did wrong. Does anybody have any ideas that don't involve using grub or gag or something else? Thanks OP I have the same setup. With that setup, you pretty much have to use GRUB or GAG (I suggest GAG, it works wonderfully). The issue is that Windows needs to think it is the first hard drive. GRUB and GAG can fool windows into thinking it is on the first drive. If you do not wish to install these boot loaders, you will have to change your cabling so that Windows is on the first drive and change your BIOS to boot off the second. Then the BSD loader will be able to boot Windows (AFAIK). PS: Sorry about miss-interpreting the message the first time I responded to you personally. -- greg [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem Booting (Bad Super Block)
I've started having problems on my FreeBSD box; I've installed FreeBSD on this system at least 5 times before without any problems. This time, the installation took many attempts, and the following error message occurs when I attempt to boot up: /dev/da0s1a: BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/da0s1a: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY Automatic file system check then fail, the boot process aborts, and the system starts in single user mode. How can I fix this error so that the machine boots normally? I am unable to run fsck from the prompt by just typing 'fsck' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem Booting (Bad Super Block)
On Fri, Nov 28, 2003 at 12:56:02AM -0800, Rishi Chopra wrote: I've started having problems on my FreeBSD box; I've installed FreeBSD on this system at least 5 times before without any problems. This time, the installation took many attempts, and the following error message occurs when I attempt to boot up: /dev/da0s1a: BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/da0s1a: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY Automatic file system check then fail, the boot process aborts, and the system starts in single user mode. How can I fix this error so that the machine boots normally? I am unable to run fsck from the prompt by just typing 'fsck' First thing you have to do is run fsck manually, like it says: # /sbin/fsck -y /dev/da0s1a With luck, this will fix the problems with your filesystem. Now, make sure that the rest of your filesystems are clean: # /sbin/fsck -p and then you should be able to reboot successfully. If you can't run /sbin/fsck then you must be running FreeBSD 5.x with the dynamic root patches. In this case, there should be a statically linked copy of fsck in /recover (? -- can't remember exactly what directory is used, but it's something like that). The question remains as to why you're seeing this problem. There are 3 obvious possibilities I can think of: i) You didn't shut down cleanly -- however, normally the automatic fsck on reboot should clear up any problems. If you're exceedingly unlucky, you might kill the system right in the middle of a critical operation and leave the disk in a nasty state leading to the effects you've seen. In this case, once you've cleared up this time, you shouldn't suffer from the problem again. ii) Your disk is failing. iii) You've got (or once had) FreeBSD 5.x installed on the same system and you mount your 4.x partitions under 5.x -- there have been changes to the superblock format in UFS1 between 4.x and 5.x: http://www.freebsd.org/cgi/query-pr.cgi?pr=54884 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: Problem Booting (Bad Super Block)
On 28 Nov, Rishi Chopra [EMAIL PROTECTED] wrote: /dev/da0s1a: BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/da0s1a: UNEXPECTED INCONSISTENCY: RUN fsck MANUALLY How can I fix this error so that the machine boots normally? I am unable to run fsck from the prompt by just typing 'fsck' I have this problem quite often in my version - 5.1-Release #9. The trick is to never reboot. g The bad superblock is always found on my second partition, mounted on /disc2 (of which I use half a gig as swap space, the other 5.5gigs do absolutely nowt) Sorry. Let's cut to the chase. Type newfs /dev/da0s1a and you should get back on the ball fairly quickly. John -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem booting 5.1 install CD
Over the weekend I was working on this and found an old 4.7 release CD lying around. I figured that it couldn't hurt to give that a try and see if it would boot. Sure enough 4.7 was fine. From there, I did a cvsup for the current set of 4.8 source files. When the 4.8 kernel was built, I excluded agp and a bunch of other bits from the GENERIC make file. Can't say if the problem exists in the 4.8 tree too. It was my hope that I could get my feet wet on 5.1 before going into real deployment testing. Any deployments would be on newer hardware so this problem may not be that big of an issue in the long run. I'm not happy about the idea of upgrading from 4.8 to 5.1. One of the things that I wanted to look closely at was extended ACLs on UFS2. Upgrading won't allow me to do that. From the Release Engineering Information section of the FreeBSD web site, it looks like 6-CURREWNT will be forked when 5.2-RELEASE is out. I would assume that this means there will be little work done on the 4 branch after 4.9 is released. -Original Message- From: Lowell Gilbert [mailto:[EMAIL PROTECTED] Sent: Saturday, October 04, 2003 11:09 AM To: Ross, Chris Cc: [EMAIL PROTECTED] Subject: Re: Problem booting 5.1 install CD Ross, Chris [EMAIL PROTECTED] writes: I am having a problem booting the FreeBSD 5.1 install CD. My machine hangs when it goes to pole agp. Is there a way to disable agp when booting from this CD? I don't think so. On my laptop, I can't directly install *any* recent releases, since AGP was put into the default kernel. I had to install 4.4 and update to -STABLE from there. Eric Anholt was planning on taking a look at this, but I hadn't heard about any results. I had narrowed it down to something weird in the aperture probe, but I couldn't see any reason for it to actually hang at that specific point. To be honest, I had been pretty sure it was just me, and I didn't have 100% confidence in my hardware anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem booting 5.1 install CD
Ross, Chris [EMAIL PROTECTED] writes: I am having a problem booting the FreeBSD 5.1 install CD. My machine hangs when it goes to pole agp. Is there a way to disable agp when booting from this CD? I don't think so. On my laptop, I can't directly install *any* recent releases, since AGP was put into the default kernel. I had to install 4.4 and update to -STABLE from there. Eric Anholt was planning on taking a look at this, but I hadn't heard about any results. I had narrowed it down to something weird in the aperture probe, but I couldn't see any reason for it to actually hang at that specific point. To be honest, I had been pretty sure it was just me, and I didn't have 100% confidence in my hardware anyway. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem booting 5.1 install CD
I am having a problem booting the FreeBSD 5.1 install CD. My machine hangs when it goes to pole agp. Is there a way to disable agp when booting from this CD? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem booting new kernel
Hi All, I'm just trying to install 4.7 onto a new PC and have compiled a customer kernel so that I can get the Prism II card working. However on reboot I'm getting VIA C3 CPU CPU Class not configured What did I do wrong? Cheers Rus -- http://www.65535.net | MSN: [EMAIL PROTECTED] Lifetime Linux or FreeBSD account: $100 || Lifetime Hosting: $150 Offsite Backups - Remote System Monitoring - Email Hosting To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problem booting new kernel
Hi! I'm just trying to install 4.7 onto a new PC and have compiled a customer kernel so that I can get the Prism II card working. However on reboot I'm getting VIA C3 CPU CPU Class not configured guess type=wild you have wrong cpu option in your custom kernel /guess -- Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ * ROM BASIC ERROR: Computer not found. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problem booting new kernel
Hi! I'm just trying to install 4.7 onto a new PC and have compiled a customer kernel so that I can get the Prism II card working. However on reboot I'm getting VIA C3 CPU CPU Class not configured guess type=wild you have wrong cpu option in your custom kernel /guess -- From my dmesg: - CPU: VIA C3 Samuel 2 (799.73-MHz 686-class CPU) Origin = CentaurHauls Id = 0x678 Stepping = 8 Features=0x803035FPU,DE,TSC,MSR,MTRR,PGE,MMX --- You need 686 class cpu Kjell To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Problem booting new kernel
Rus Foster [EMAIL PROTECTED] wrote: I'm just trying to install 4.7 onto a new PC and have compiled a customer kernel so that I can get the Prism II card working. However on reboot I'm getting VIA C3 CPU CPU Class not configured I'm not sure if a C3 is 586 or 686 class, but you've probably removed one of those from your custom kernel configuration. Put it back and remove the other one. It definitely isn't 386 or 486 so you can remove those. John. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
