Re: 9.0-RELEASE amd64 Bricked My Hard Drive
Bill Tillman wrote: Today I encountered a problem which has me stumped. I downloaded and burned the ISO image for 9.0-RELEASE for amd64. I installed an older IDE hard drive to test the new OS with and did the install. I was very surprised at the (1) the dvd is actually a live CD if you wanted it to be and (2) the installers screens have all been revamped. I can't say for sure if the partitioning part was where it went south on me because I was attempting to setup some additional partitions but the input screens had me confused and I pressed Auto so it took off and made the default paritions. The computer would start up, show me the flash screen to do the Bios setup and then nothing. I put the other drive back in and it worked fine. I tried another computer and the results were the same. snip This is a known problem with bsdinstall in 9.0. Newer pc's have bios that use gpart format disk partition layouts (IE windows7) so for FreeBSD to be compatible with new PC hardware, Bsdinstall defaults to using the gpart format disk partition layouts. Bsdinstall provides no automatic way to create (mbr, Dos) format partitions. The user is suppose to know before installing 9.0 that their pc hardware requires (mbr, Dos) format partitions and instead of using the automatic gpart format disk partition layouts they must select the manual option which opens a shell where the installer must enter the native commands to create the (mbr, Dos) format partitions like sysinstall did in 8.2 and older releases. This puts a unfair burden on users to know beforehand whether their pc bios are gpart aware. Bsdinstall provides no displayed information informing the user of what they need to know about their equipment before selecting the disk format to use. I believe this user is just the tip of the iceberg of users installing 9.0 on older hardware. At this time the only way to automate the creation of the (mbr, Dos) format partitions using the 9.0 bsdinstall is to select the manual option in the disk config screen and them launch "sade", this is the disk configuration dialog from sysinstall that has been turned into a standalone utility. If you think "sade" should be made a option of the bsdinstall disk config dialog then post your comments here and cc to nwhiteh...@freebsd.org the author of bsdinstall. The bsdinstall has absolutely no built in HELP, But there is some new documentation in the online freebsd manual. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall.html It's under constant revision so it may not be totally accurate, but it will provide you some insight to your disk config problems. Note: before you can use that gpart disk to create mbr you have to delete the (crap) gpart writes at the end of the physical disk. This script works great to do that. http://www.wonkity.com/~wblock/docs/html/disksetup.html After running the script, then on same disk pc install 8.2 and reboot. If it boots fine then you know for sure your pc bios is not gpart aware, and you will always have to use mbr disk format on that pc hardware combination. The SADE utility will become your long time friend. Good luck. ___ 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"
Running 9.0-STABLE on a Soekris Net6501-70
Hi! I am running FreeBSD 9.0-STABLE on a Soekris Net6501-70 which has the following CPU: CPU: Genuine Intel(R) CPU@ 1.60GHz (1600.04-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x20661 Family = 6 Model = 26 Stepping = 1 Features=0xbfe9fbff Features2=0x40e3bd AMD Features=0x2010 AMD Features2=0x1 TSC: P-state invariant, performance statistics Running a GENERIC (i386) kernel the cpu by default runs at only 600Mhz: % sysctl dev.cpu dev.cpu.0.%driver: cpu dev.cpu.0.%parent: legacy0 dev.cpu.0.freq: 600 dev.cpu.0.freq_levels: 1600/-1 1400/-1 1200/-1 1000/-1 800/-1 600/-1 400/-1 200/-1 I either have to run 'sysctl dev.cpu.0.freq=1600' or run 'powerd' to make the cpu faster. Probaby related: ACPI Error: A valid RSDP was not found (20110527/tbxfroot-237) ACPI: Table initialisation failed: AE_NOT_FOUND ACPI: Try disabling either ACPI or apic support. [...] cpu0 on motherboard est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 615101c06000617 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1 on motherboard est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 615101c06000617 device_attach: est1 attach returned 6 [...] Can this be fixed or should I just add the following lines to /boot/loader.conf: hint.p4tcc.0.disabled=1 hint.acpi.0.disabled=1 hint.est.0.disabled=1 Thanks. -- Herbert ___ 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[2]: how to force 'device' sources to not compile?
Здравствуйте, Michael. Вы писали 7 января 2012 г., 0:28:55: MP> Коньков Евгений wrote: >> I have errors while compile kernel >> >> ===> et (all) >> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc >> -DHAVE_KERNEL_OPTION_HEADERS -include >> /usr/obj/usr/src/sys/KES_KERN_v9/opt_global.h -I. -I@ -I@/contrib/altq >> -finline-limit=8000 --param inline-unit-growth=100 --param >> large-function-growth=1000 -fno-common -g >> -I/usr/obj/usr/src/sys/KES_KERN_v9 -mno-align-long-strings >> -mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float -ffreestanding >> -fstack-protector -std=iso9899:1999 -fstack-protector -Wall >> -Wredundant-decls -Wnested-externs -Wstrict-prototypes >> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef >> -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs >> -fdiagnostics-show-option -c >> /usr/src/sys/modules/et/../../dev/et/if_et.c >> /usr/src/sys/modules/et/../../dev/et/if_et.c: In function 'et_dma_alloc': >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: 'ET_RING_ALIGN' >> undeclared (first use in this function) >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: (Each undeclared >> identifier is reported only once >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: for each function >> it appears in.) /usr/src/sys/modules/et/../../dev/et/if_et.c:790: error: >> 'ET_STATUS_ALIGN' undeclared (first use in this function) >> /usr/src/sys/modules/et/../../dev/et/if_et.c:845: error: 'struct et_softc' >> has no member named 'sc_rx_mini_tag' >> /usr/src/sys/modules/et/../../dev/et/if_et.c:854: error: 'struct et_softc' >> has no member named 'sc_rx_tag' >> /usr/src/sys/modules/et/../../dev/et/if_et.c:864: error: 'struct et_softc' >> has no member named 'sc_tx_tag' >> >> how to disable 'et' from compiling? MP> Why? Since others do not seem to have this problem wouldn't it instead be a MP> better idea to discover what you are doing wrong? Simply trying to 'not MP> build et' will not reveal what is wrong - fixing what is wrong would be MP> better. MFC r228333,228335-228336,228362,228368-228369,228381: from yongari already FIX that, kernel is builded, but see: http://www.freebsd.org/cgi/query-pr.cgi?pr=misc/163880 -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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: how to force 'device' sources to not compile?
Коньков Евгений wrote: > I have errors while compile kernel > > ===> et (all) > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc > -DHAVE_KERNEL_OPTION_HEADERS -include > /usr/obj/usr/src/sys/KES_KERN_v9/opt_global.h -I. -I@ -I@/contrib/altq > -finline-limit=8000 --param inline-unit-growth=100 --param > large-function-growth=1000 -fno-common -g > -I/usr/obj/usr/src/sys/KES_KERN_v9 -mno-align-long-strings > -mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float -ffreestanding > -fstack-protector -std=iso9899:1999 -fstack-protector -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef > -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs > -fdiagnostics-show-option -c > /usr/src/sys/modules/et/../../dev/et/if_et.c > /usr/src/sys/modules/et/../../dev/et/if_et.c: In function 'et_dma_alloc': > /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: 'ET_RING_ALIGN' > undeclared (first use in this function) > /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: (Each undeclared > identifier is reported only once > /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: for each function > it appears in.) /usr/src/sys/modules/et/../../dev/et/if_et.c:790: error: > 'ET_STATUS_ALIGN' undeclared (first use in this function) > /usr/src/sys/modules/et/../../dev/et/if_et.c:845: error: 'struct et_softc' > has no member named 'sc_rx_mini_tag' > /usr/src/sys/modules/et/../../dev/et/if_et.c:854: error: 'struct et_softc' > has no member named 'sc_rx_tag' > /usr/src/sys/modules/et/../../dev/et/if_et.c:864: error: 'struct et_softc' > has no member named 'sc_tx_tag' > > how to disable 'et' from compiling? Why? Since others do not seem to have this problem wouldn't it instead be a better idea to discover what you are doing wrong? Simply trying to 'not build et' will not reveal what is wrong - fixing what is wrong would be better. -Mike ___ 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[4]: how to force 'device' sources to not compile?
Здравствуйте, Devin. Вы писали 7 января 2012 г., 0:05:12: >> -Original Message- >> From: Коньков Евгений [mailto:kes-...@yandex.ru] >> Sent: Friday, January 06, 2012 1:46 PM >> To: Devin Teske >> Cc: freebsd-questions@freebsd.org >> Subject: Re[2]: how to force 'device' sources to not compile? >> >> Здравствуйте, Devin. >> >> Вы писали 6 января 2012 г., 23:42:54: >> >> >> >> >> -Original Message- >> >> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- >> >> questi...@freebsd.org] On Behalf Of ??? ??? >> >> Sent: Friday, January 06, 2012 1:40 PM >> >> To: freebsd-questions@freebsd.org >> >> Subject: how to force 'device' sources to not compile? >> >> >> >> I have errors while compile kernel >> >> >> >> ===> et (all) >> >> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc >> - >> >> DHAVE_KERNEL_OPTION_HEADERS -include >> >> /usr/obj/usr/src/sys/KES_KERN_v9/opt_global.h -I. -I@ >> >> -I@/contrib/altq >> DT> -finline- >> >> limit=8000 --param inline-unit-growth=100 --param >> >> large-function-growth=1000 - fno-common -g >> >> -I/usr/obj/usr/src/sys/KES_KERN_v9 -mno-align-long-strings - >> >> mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float >> >> -ffreestanding - fstack-protector -std=iso9899:1999 -fstack-protector >> >> -Wall -Wredundant-decls - Wnested-externs -Wstrict-prototypes >> >> -Wmissing-prototypes -Wpointer-arith - Winline -Wcast-qual -Wundef -Wno- >> pointer-sign -fformat-extensions - >> >> Wmissing-include-dirs -fdiagnostics-show-option -c >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c: In function 'et_dma_alloc': >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: 'ET_RING_ALIGN' >> >> undeclared (first use in this function) >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: (Each >> >> undeclared identifier is reported only once >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: for each >> >> function it appears in.) >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c:790: error: 'ET_STATUS_ALIGN' >> >> undeclared (first use in this function) >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c:845: error: 'struct >> >> et_softc' has >> DT> no >> >> member named 'sc_rx_mini_tag' >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c:854: error: 'struct >> >> et_softc' has >> DT> no >> >> member named 'sc_rx_tag' >> >> /usr/src/sys/modules/et/../../dev/et/if_et.c:864: error: 'struct >> >> et_softc' has >> DT> no >> >> member named 'sc_tx_tag' >> >> >> >> how to disable 'et' from compiling? >> >> DT> Try adding: >> >> DT> nodevice et >> >> DT> To a custom kernel config. >> >> I have tryed to remove 'device et', 'nodevice et', 'device et' same results >> =( >> DT> Apologies, let me clarify... DT> I would create a custom kernel config by executing (assumptions: your kernel DT> source is stored at /usr/src/sys): DT> cd /usr/src/sys/i386/conf DT> NOTE: Replace "i386" with another architecture (such as "amd64") depending on DT> your needs. DT> touch MYGENERIC DT> NOTE: Followint steps will overwrite "MYGENERIC" in the current working DT> directory if it already exists. If this file exists already, move it aside DT> before proceeding. DT> echo "include GENERIC" > MYGENERIC DT> echo "ident MYGENERIC" >> MYGENERIC DT> echo "machine i386" >> MYGENERIC DT> NOTE: Again, replace "i386" with your desired architecture if not "i386". DT> echo "nodevice et" >> MYGENERIC DT> Now, configure and compile your kernel by executing: DT> config -g MYGENERIC DT> cd ../compile/MYGENERIC DT> make cleandepend && make depend && make DT> Your new kernel is named "kernel" in the current working directory. cd /usr/src/sys/i386/conf cp GENERIC MYKERN open MYKERN in editor, find 'device et' and change it with 'nodevice et' or, Ithink, this must work also: echo 'nodevice et' >> /usr/src/sys/i386/conf/MYKERN cd /usr/src echo "bla-bla-bla" > /usr/src/sys/dev/et/if_et.c make buildkernel KERNCONF=MYKERN despite on there is 'nodevice et' system tryes to build 'et' and fail -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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: Re[2]: how to force 'device' sources to not compile?
> -Original Message- > From: Коньков Евгений [mailto:kes-...@yandex.ru] > Sent: Friday, January 06, 2012 1:46 PM > To: Devin Teske > Cc: freebsd-questions@freebsd.org > Subject: Re[2]: how to force 'device' sources to not compile? > > Здравствуйте, Devin. > > Вы писали 6 января 2012 г., 23:42:54: > > > > >> -Original Message- > >> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- > >> questi...@freebsd.org] On Behalf Of ??? ??? > >> Sent: Friday, January 06, 2012 1:40 PM > >> To: freebsd-questions@freebsd.org > >> Subject: how to force 'device' sources to not compile? > >> > >> I have errors while compile kernel > >> > >> ===> et (all) > >> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc > - > >> DHAVE_KERNEL_OPTION_HEADERS -include > >> /usr/obj/usr/src/sys/KES_KERN_v9/opt_global.h -I. -I@ > >> -I@/contrib/altq > DT> -finline- > >> limit=8000 --param inline-unit-growth=100 --param > >> large-function-growth=1000 - fno-common -g > >> -I/usr/obj/usr/src/sys/KES_KERN_v9 -mno-align-long-strings - > >> mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float > >> -ffreestanding - fstack-protector -std=iso9899:1999 -fstack-protector > >> -Wall -Wredundant-decls - Wnested-externs -Wstrict-prototypes > >> -Wmissing-prototypes -Wpointer-arith - Winline -Wcast-qual -Wundef -Wno- > pointer-sign -fformat-extensions - > >> Wmissing-include-dirs -fdiagnostics-show-option -c > >> /usr/src/sys/modules/et/../../dev/et/if_et.c > >> /usr/src/sys/modules/et/../../dev/et/if_et.c: In function 'et_dma_alloc': > >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: 'ET_RING_ALIGN' > >> undeclared (first use in this function) > >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: (Each > >> undeclared identifier is reported only once > >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: for each > >> function it appears in.) > >> /usr/src/sys/modules/et/../../dev/et/if_et.c:790: error: 'ET_STATUS_ALIGN' > >> undeclared (first use in this function) > >> /usr/src/sys/modules/et/../../dev/et/if_et.c:845: error: 'struct > >> et_softc' has > DT> no > >> member named 'sc_rx_mini_tag' > >> /usr/src/sys/modules/et/../../dev/et/if_et.c:854: error: 'struct > >> et_softc' has > DT> no > >> member named 'sc_rx_tag' > >> /usr/src/sys/modules/et/../../dev/et/if_et.c:864: error: 'struct > >> et_softc' has > DT> no > >> member named 'sc_tx_tag' > >> > >> how to disable 'et' from compiling? > > DT> Try adding: > > DT> nodevice et > > DT> To a custom kernel config. > > I have tryed to remove 'device et', 'nodevice et', 'device et' same results =( > Apologies, let me clarify... I would create a custom kernel config by executing (assumptions: your kernel source is stored at /usr/src/sys): cd /usr/src/sys/i386/conf NOTE: Replace "i386" with another architecture (such as "amd64") depending on your needs. touch MYGENERIC NOTE: Followint steps will overwrite "MYGENERIC" in the current working directory if it already exists. If this file exists already, move it aside before proceeding. echo "include GENERIC" > MYGENERIC echo "ident MYGENERIC" >> MYGENERIC echo "machine i386" >> MYGENERIC NOTE: Again, replace "i386" with your desired architecture if not "i386". echo "nodevice et" >> MYGENERIC Now, configure and compile your kernel by executing: config -g MYGENERIC cd ../compile/MYGENERIC make cleandepend && make depend && make Your new kernel is named "kernel" in the current working directory. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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: SSH Access To Live CD? (Was Re: FBSD-9.0-RC3 Disk 1 ISO Bootable?)
Здравствуйте, Drew. Вы писали 6 января 2012 г., 23:44:28: DT> On 1/6/2012 12:07 PM, Al Plant wrote: >> per...@pluto.rain.com wrote: >>> Al Plant wrote: >>> I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. >>> >>> I take it you either arranged for ssh to accept a direct root login, >>> or added a non-root username. Does the new installer do one of >>> these automatically, or is there more manual configuration involved? >> >> BSD Installer asks if you want to install sshd and click yes. Later >> you can go to another box on the lan and use the user account to ssh >> into the new box and su to root. This feature has been on the installs >> for a while. I used it on sysinstall on 7.*. DT> OK, so you didn't actually install remotely via ssh. You installed DT> locally and let the installer configure sshd for your new install and it DT> was available after you rebooted into your new install. DT> I'd like to actually be able to install via ssh. Basically I'd like ssh DT> access to the Live CD so I could partition my drives for zfs prior to DT> installing. And I'd like to do it from a computer that's connected to DT> the web so I can read and copy/paste examples. DT> Cheers, DT> Drew mfsBSD - is interesting project, that allow you to install/ reinstall system remotely! -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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"
SSH Access To Live CD? (Was Re: FBSD-9.0-RC3 Disk 1 ISO Bootable?)
On 1/6/2012 12:07 PM, Al Plant wrote: per...@pluto.rain.com wrote: Al Plant wrote: I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. I take it you either arranged for ssh to accept a direct root login, or added a non-root username. Does the new installer do one of these automatically, or is there more manual configuration involved? BSD Installer asks if you want to install sshd and click yes. Later you can go to another box on the lan and use the user account to ssh into the new box and su to root. This feature has been on the installs for a while. I used it on sysinstall on 7.*. OK, so you didn't actually install remotely via ssh. You installed locally and let the installer configure sshd for your new install and it was available after you rebooted into your new install. I'd like to actually be able to install via ssh. Basically I'd like ssh access to the Live CD so I could partition my drives for zfs prior to installing. And I'd like to do it from a computer that's connected to the web so I can read and copy/paste examples. Cheers, Drew -- Like card tricks? Visit The Alchemist's Warehouse to learn card magic secrets for free! http://alchemistswarehouse.com ___ 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[2]: how to force 'device' sources to not compile?
Здравствуйте, Devin. Вы писали 6 января 2012 г., 23:42:54: >> -Original Message- >> From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- >> questi...@freebsd.org] On Behalf Of ??? ??? >> Sent: Friday, January 06, 2012 1:40 PM >> To: freebsd-questions@freebsd.org >> Subject: how to force 'device' sources to not compile? >> >> I have errors while compile kernel >> >> ===> et (all) >> cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc >> - >> DHAVE_KERNEL_OPTION_HEADERS -include >> /usr/obj/usr/src/sys/KES_KERN_v9/opt_global.h -I. -I@ -I@/contrib/altq DT> -finline- >> limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 >> - >> fno-common -g -I/usr/obj/usr/src/sys/KES_KERN_v9 -mno-align-long-strings - >> mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float -ffreestanding - >> fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls >> - >> Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith - >> Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions - >> Wmissing-include-dirs -fdiagnostics-show-option -c >> /usr/src/sys/modules/et/../../dev/et/if_et.c >> /usr/src/sys/modules/et/../../dev/et/if_et.c: In function 'et_dma_alloc': >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: 'ET_RING_ALIGN' >> undeclared (first use in this function) >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: (Each undeclared >> identifier is reported only once >> /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: for each function it >> appears in.) >> /usr/src/sys/modules/et/../../dev/et/if_et.c:790: error: 'ET_STATUS_ALIGN' >> undeclared (first use in this function) >> /usr/src/sys/modules/et/../../dev/et/if_et.c:845: error: 'struct et_softc' >> has DT> no >> member named 'sc_rx_mini_tag' >> /usr/src/sys/modules/et/../../dev/et/if_et.c:854: error: 'struct et_softc' >> has DT> no >> member named 'sc_rx_tag' >> /usr/src/sys/modules/et/../../dev/et/if_et.c:864: error: 'struct et_softc' >> has DT> no >> member named 'sc_tx_tag' >> >> how to disable 'et' from compiling? DT> Try adding: DT> nodevice et DT> To a custom kernel config. I have tryed to remove 'device et', 'nodevice et', 'device et' same results =( -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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: how to force 'device' sources to not compile?
> -Original Message- > From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- > questi...@freebsd.org] On Behalf Of ??? ??? > Sent: Friday, January 06, 2012 1:40 PM > To: freebsd-questions@freebsd.org > Subject: how to force 'device' sources to not compile? > > I have errors while compile kernel > > ===> et (all) > cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc - > DHAVE_KERNEL_OPTION_HEADERS -include > /usr/obj/usr/src/sys/KES_KERN_v9/opt_global.h -I. -I@ -I@/contrib/altq -finline- > limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 - > fno-common -g -I/usr/obj/usr/src/sys/KES_KERN_v9 -mno-align-long-strings - > mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float -ffreestanding - > fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls - > Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith - > Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions - > Wmissing-include-dirs -fdiagnostics-show-option -c > /usr/src/sys/modules/et/../../dev/et/if_et.c > /usr/src/sys/modules/et/../../dev/et/if_et.c: In function 'et_dma_alloc': > /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: 'ET_RING_ALIGN' > undeclared (first use in this function) > /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: (Each undeclared > identifier is reported only once > /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: for each function it > appears in.) > /usr/src/sys/modules/et/../../dev/et/if_et.c:790: error: 'ET_STATUS_ALIGN' > undeclared (first use in this function) > /usr/src/sys/modules/et/../../dev/et/if_et.c:845: error: 'struct et_softc' has no > member named 'sc_rx_mini_tag' > /usr/src/sys/modules/et/../../dev/et/if_et.c:854: error: 'struct et_softc' has no > member named 'sc_rx_tag' > /usr/src/sys/modules/et/../../dev/et/if_et.c:864: error: 'struct et_softc' has no > member named 'sc_tx_tag' > > how to disable 'et' from compiling? Try adding: nodevice et To a custom kernel config. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ 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"
how to force 'device' sources to not compile?
I have errors while compile kernel ===> et (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/KES_KERN_v9/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -I/usr/obj/usr/src/sys/KES_KERN_v9 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-sse -mno-mmx -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /usr/src/sys/modules/et/../../dev/et/if_et.c /usr/src/sys/modules/et/../../dev/et/if_et.c: In function 'et_dma_alloc': /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: 'ET_RING_ALIGN' undeclared (first use in this function) /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: (Each undeclared identifier is reported only once /usr/src/sys/modules/et/../../dev/et/if_et.c:782: error: for each function it appears in.) /usr/src/sys/modules/et/../../dev/et/if_et.c:790: error: 'ET_STATUS_ALIGN' undeclared (first use in this function) /usr/src/sys/modules/et/../../dev/et/if_et.c:845: error: 'struct et_softc' has no member named 'sc_rx_mini_tag' /usr/src/sys/modules/et/../../dev/et/if_et.c:854: error: 'struct et_softc' has no member named 'sc_rx_tag' /usr/src/sys/modules/et/../../dev/et/if_et.c:864: error: 'struct et_softc' has no member named 'sc_tx_tag' how to disable 'et' from compiling? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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"
[OT] re: Realtek RTL8191SEvB Linux driver?
to Jerry at seibercom.net weapons make a polite society http://www.telegraaf.nl/binnenland/11138983/__Van_Uhm_is_wereldhit__.html there's no free piss it's recycled money for water/beer/juice/whatever Cheers Bas Disclaimer: http://www.ose.nl/email ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
Waitman Gobble wrote: On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman wrote: I had been running a similar computer with Windows XP with it. The drive was working fine a few moments before I did the install. I have a utility to test hard drives which boots from CD but like I said, when this drive is on a cable connected to any machine, booting is a non-option. I have an old IDE controller but it's ISA and I have not ISA slots on this computer. Looks like I may have to try the USB drive boot option to get on with this rescue. Weirdness.. ok, i was wondering - you said you installed an old drive to check it out, and I was thinking hmm 80gb, maybe setting on the shelf for a decade :) I do recall having a similar issue with a drive, but it was years and years ago- my memory hazed, and not necessarily (probably not) related to FreeBSD install. If you aren't getting POST then it sounds hardware related to me. Good Luck, Waitman ___ 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" Aloha, I had this happen with using [Cable Select] on an 80G ISA drive jumper and after I switched to [Master] it worked fine. In any case it does sound like hardware. Try switching the cable. It may be broken. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + < email: n...@hdk5.net > "All that's really worth doing is what we do for others."- Lewis Carrol ___ 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: FBSD-9.0-RC3 Disk 1 ISO Bootable?
per...@pluto.rain.com wrote: Al Plant wrote: I accessed the sshd from the new install screen as an option when I loaded it on the test box. I had to set up the lan manually to first get it up. Then you should be able to use ssh. I take it you either arranged for ssh to accept a direct root login, or added a non-root username. Does the new installer do one of these automatically, or is there more manual configuration involved? ___ 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" Aloha, BSD Installer asks if you want to install sshd and click yes. Later you can go to another box on the lan and use the user account to ssh into the new box and su to root. This feature has been on the installs for a while. I used it on sysinstall on 7.*. -- ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 7.2 - 8.0 - 9* + < email: n...@hdk5.net > "All that's really worth doing is what we do for others."- Lewis Carrol ___ 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: Apparently conflicting smartctl output
On Fri, 6 Jan 2012 12:32:14 -0700 (MST) Warren Block wrote: > On Fri, 6 Jan 2012, Bas Smeelen wrote: > > > On 01/06/2012 04:37 PM, Warren Block wrote: > >> On Fri, 6 Jan 2012, Bas Smeelen wrote: > >> > >>> On 01/06/2012 03:39 PM, Warren Block wrote: > On Fri, 6 Jan 2012, Bas Smeelen wrote: > > > I have had this with a drive and multiple read errors would not > > remap the > > sector. > > With write errors the sector would be remapped. This was a new > > Samsung laptop drive though, not a Western Digital. > > > > I could use dd if=/dev/random of=file seek=blocks_to_skip bs=100M > > the next time > > Yes, if you're not worried about existing data. But use /dev/zero > (faster and you can verify the value) and bs=1M count=100 (ties up > only 1M of buffer space). Thanks a lot. This was always confusing me, now I know! Cheers Disclaimer: http://www.ose.nl/email ___ 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: failure - write_dma issue
On Jan 6, 2012, at 10:03 AM, John Almberg wrote: > My FreeBSD servers have been quite reliable since I started using them 4 or 5 > years ago, so I don't have much experience debugging them. > > Can anyone give me a hint about what might be wrong (I assume with the HD), > and how/if it might be fixable? That's a typical sign of a disk failure. Whether it is just a bad sector, or whether the entire drive is toast is the question, and the smartctl utility from sysutils/smartmontools port will let you take a look and run drive self-tests to help answer it. Regards, -- -Chuck ___ 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"
failure - write_dma issue
One of my servers -- I believe running 6.x -- developed a HD problem last night. The console was displaying the following, over and over again: g_vfs_done():ad0s1d[WRITE(offset=970506240, length=-16384)error= 5 ad0: FAILURE - WRITE_DMA status=71 error=4 LBA=3918703 My FreeBSD servers have been quite reliable since I started using them 4 or 5 years ago, so I don't have much experience debugging them. Can anyone give me a hint about what might be wrong (I assume with the HD), and how/if it might be fixable? TIA: John “Wealth is the ability to fully experience life.” – Henry David Thoreau ___ 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: Browser
On 4 January 2012 17:18, RW wrote: > On Wed, 4 Jan 2012 12:56:38 -0500 > ill...@gmail.com wrote: > > >> If you have a few hours, lots of RAM, & you'd like to stress- >> test your system: >> cd /usr/ports/www/chromium && make install > > > Unless things have changed radically that sounds like a bit of an > exaggeration. Until about 9 months ago I was building it on a 7 year > old single core athlon in 1.5GB with the work-directory on tmpfs. It > was still perfectly usable as a desktop. I suppose it's relative. I compile it on a dual-core while doing other stuff & everything goes fine, it just seems to take a rather long time (comparable to [libre|open]office). I'll give it that chromium (8 tabs open) seems to use far less CPU than opera (6 tabs open) & less than 1/4 the memory of opera, as well. -- -- ___ 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: Apparently conflicting smartctl output
On Fri, 6 Jan 2012, Bas Smeelen wrote: On 01/06/2012 04:37 PM, Warren Block wrote: On Fri, 6 Jan 2012, Bas Smeelen wrote: On 01/06/2012 03:39 PM, Warren Block wrote: On Fri, 6 Jan 2012, Bas Smeelen wrote: I have had this with a drive and multiple read errors would not remap the sector. With write errors the sector would be remapped. This was a new Samsung laptop drive though, not a Western Digital. That's standard. Sectors are only remapped to spares on a write error. To get the sector remapped I had to fully write the drive and it was ok after that. Just writing to the sector should be enough. Of course, when one sector goes bad, others often follow. I just hope it does not develop more bad sectors. That's the worrying thing. Was it just a loose flake of oxide, or was it a strip that peeled off the disk? No way to know I guess From what I read on the "Bad block HOWTO for smartmontools" on sourceforge it's not trivial to just write to that sector and also it would destroy the filesystem? Finding the right block may not be too hard. /var/log/messages should show the block number, but then I don't know what tool is available to write to that specific block. Tools like that are not common because generally, growing bad sectors means the drive is starting to fail anyway. I could use dd if=/dev/random of=file seek=blocks_to_skip bs=100M the next time Yes, if you're not worried about existing data. But use /dev/zero (faster and you can verify the value) and bs=1M count=100 (ties up only 1M of buffer space). ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
On 5 January 2012 22:16, Bill Tillman wrote: ... > then I attempted to reboot the system but nothing happened. And by that I > mean the computer's flash screen would come up and give me the choice > to enter the Bios Setup or Boot Menu and that's all. I could not enter the > bios setup or the Boot menu. The keyboard was still responding as I > could press the CapLock key and toggle the light on and off, but outside > of that the computer would not boot. On the advice of some of the techs > in #FreeBSD channel I moved the drive over to another computer which > was working fine, and the same thing happened. The computer would > start up, show me the flash screen to do the Bios setup and then nothing. > I put the other drive back in and it worked fine. I tried another computer > and the results were the same. Now it gets really wierd. I thought that I > could just make this IDE drive a slave and boot with another drive and > cleanup the mess. But no matter which computer I chose, and no matter > how I setup the Slave/Master drive, as long as this drive which I had > installed FreeBSD-9.0-amd64 was in the loop, the computer would > lockup at the bios screen. I could not get anything to boot if this drive > was in the loop. If I removed it everything was fine. So basically, > FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive > and I can't seem to recover it. > > Any suggestions would be appreciated. I have an old IDE->USB adapter that I think I picked up for $15 a few years ago. (amazon has them for that right now http://amzn.to/xfyeOW Your local Beast Buy or MicroSinter may have such as well the newer once seem to all have eSATA ports too) Silly things like that come in handy once in a great while. Though you may have that rare case when your HDD's board cooked itself for some reason. -- -- ___ 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: FreeBSD on kvm
On Fri, 06 Jan 2012 18:49:41 +0100, Alessandro Baggi wrote: > On 01/06/2012 06:24 PM, Polytropon wrote: > > On Fri, 06 Jan 2012 17:50:41 +0100, Alessandro Baggi wrote: > >> Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give > >> me some "crash". > >> There is a possibility to run directly the system instead print the > >> menu? I must install lilo/grub? > > Let's first assume that you did not install the boot > > manager (which would be useless in your particular > > application case); instead, you have installed the > > standard MBR. > > > > Modify /boot/loader.conf to something like this: > > > > autoboot_delay="0" > > beastie_disable="YES" > > userconfig_script_load="NO" > > verbose_loading="YES" > > > > Refer to /boot/defaults/loader.conf for the meaning > > of the options if they're not obvious. :-) > > > > Regarding the autoboot delay, let me quote from that > > file: > > > > Delay in seconds before autobooting, > > set to -1 if you don't want user to be > > allowed to interrupt autoboot process and > > escape to the loader prompt, set to > > "NO" to disable autobooting > > > > That means ="0" would mean to boot immediately _with_ > > the option to get to the boot prompt - you just need > > to be fast at the keyboard. :-) > > > > Oh, and see "man loader.conf" for details. > > > > > Hi Polytropon, > yes, I've installed the standard mbr :/. > After this, I've make the setting, but reading on > /boot/defaults/loader.conf for meaning of userconfig_script_load, I > can't find nothing about it, and I suppose that it is an invalid option. Sorry, forgot about that - must be some cruft transitioned from older installs. Just remove that option, as I don't think it has _any_ effect here. :-) > Now it seems to work. > Thanks for the reply. Sometimes I don't remember to see manual page...my > big bug... In FreeBSD, there's a manpage for nearly everything: System binaries and command scripts, kernel interfaces, library functions, device drivers, configuration files, maintenance procedures and operation guidelines. You just have to make yourself familiar with the ideas that those actually do exist. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: FreeBSD on kvm
On 01/06/2012 06:28 PM, Damien Fleuriot wrote: On 1/6/12 6:20 PM, Alessandro Baggi wrote: On 01/06/2012 06:12 PM, Damien Fleuriot wrote: On 1/6/12 5:50 PM, Alessandro Baggi wrote: On 01/06/2012 05:40 PM, Damien Fleuriot wrote: On 1/6/12 4:18 PM, Alessandro Baggi wrote: On 01/06/2012 12:50 PM, Damien Fleuriot wrote: On 1/6/12 11:43 AM, Alessandro Baggi wrote: Hi list, i've a problem running freebsd as a guest on linux+kvm. The only problem is that sometimes, when I boot the system it dies and this happens also if I run the vm with and without -nographic option. Using the qemu GUI I can see the it stops on the boot loader menu after the countdown and the only mode to resume the system is reboot the vm. I've reduced the autoboot delay to 1 without no result. Someone know something about this problem? Thanks in advance. Hi, This is exactly how to *not* ask a question. Please take the time to read this very informative article: http://www.catb.org/~esr/faqs/smart-questions.html#beprecise For instance, you've omitted important information such as: - linux version - qemu version - freebsd version - freebsd error message when "it dies", if any - KVM configuration options (disk mode and such) We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM for over 3 years now for our pre-production environment and are very happy with it. Please post some more details, that we might be able to actually help. ___ 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" True, I'm sorry, too few informations. The host system is Slackware64 Linux 13.37 QEMU emulator version 0.14.0 (qemu-kvm-0.14.0), Copyright (c) 2003-2008 Fabrice Bellard FreeBSD 8.2-RELEASE-p3 kvm option: /usr/bin/qemu-system-x86_64 -pidfile $PIDFILE -cpu host -smp $NCPU -m $MRAM -k $KB -enable-kvm -drive file=$IMAGE,media=disk,index=0,cache=writeback -net nic,model=$NICMODEL,macaddr=$MAC -net tap,ifname=$TAP,script=no,downscript=no -runas $USER -monitor unix:$SOCKET,server,nowait -nographic -daemonize There are not errors. When there is the countdown it seems to die.For example it stops to 9 seconds or 6 and stop (die) No boot line, only the boot loader menu blocked. To avoid this I want say that freebsd work very well under kvm, the problem is presented every 2/3 startup of this virtual machine. What disk format do you use, with KVM ? QCOW2, RAW, VirtIO ? We're running with QCOW2 here, emulating IDE drives and we don't have any problem. ___ 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" I'm using QCOW2. For ide drives do you give -hda? Info: if I give Enter during the countdown, it starts, if i leave the countdown to finish, it crash. But running with -nographic there isn't sense to give "enter" Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give me some "crash". There is a possibility to run directly the system instead print the menu? I must install lilo/grub? Thanks in advance. QEMU emulator version 0.15.0 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard Find below the resulting command-line used to run a typical FreeBSD KVM from our Proxmox interface: /usr/bin/kvm -monitor unix:/var/run/qemu-server/141.mon,server,nowait -vnc unix:/var/run/qemu-server/141.vnc,password -pidfile /var/run/qemu-server/141.pid -daemonize -usbdevice tablet -name yournamehere -smp sockets=2,cores=2 -nodefaults -boot menu=on -vga cirrus -tdf -k fr -drive file=/var/lib/vz/images/141/vm-141-disk-1.qcow2,if=ide,index=0 -m 512 -netdev type=tap,id=vlan18d0,ifname=tap141i18d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=9E:6C:42:78:98:E2,netdev=vlan18d0 -netdev type=tap,id=vlan730d0,ifname=tap141i730d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=E6:BA:DA:56:C9:66,netdev=vlan730d0 -netdev type=tap,id=vlan731d0,ifname=tap141i731d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=8E:B5:8F:30:F2:C1,netdev=vlan731d0 -id 141 -cpuunits 1000 Also find below the contents of the config file for the guest: -> cat /etc/qemu-server/141.conf name: [snip] bootdisk: virtio0 ostype: other memory: 512 onboot: 1 sockets: 2 ide0: local:141/vm-141-disk-1.qcow2 vlan18: e1000=9E:6C:42:78:98:E2 cores: 2 vlan730: e1000=E6:BA:DA:56:C9:66 vlan731: e1000=8E:B5:8F:30:F2:C1 Do not pay attention to "bootdisk: virtio0", we use "ide0" for other FreeBSD KVMs just as well. I'm beginning to think your VM might be crashing while/because it's actually probing for other devices. What's the full list of devices you have attached to your VM ? Do we have any boot stages expert on the list ? _
Re: FreeBSD on kvm
On 01/06/2012 06:24 PM, Polytropon wrote: On Fri, 06 Jan 2012 17:50:41 +0100, Alessandro Baggi wrote: Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give me some "crash". There is a possibility to run directly the system instead print the menu? I must install lilo/grub? Let's first assume that you did not install the boot manager (which would be useless in your particular application case); instead, you have installed the standard MBR. Modify /boot/loader.conf to something like this: autoboot_delay="0" beastie_disable="YES" userconfig_script_load="NO" verbose_loading="YES" Refer to /boot/defaults/loader.conf for the meaning of the options if they're not obvious. :-) Regarding the autoboot delay, let me quote from that file: Delay in seconds before autobooting, set to -1 if you don't want user to be allowed to interrupt autoboot process and escape to the loader prompt, set to "NO" to disable autobooting That means ="0" would mean to boot immediately _with_ the option to get to the boot prompt - you just need to be fast at the keyboard. :-) Oh, and see "man loader.conf" for details. Hi Polytropon, yes, I've installed the standard mbr :/. After this, I've make the setting, but reading on /boot/defaults/loader.conf for meaning of userconfig_script_load, I can't find nothing about it, and I suppose that it is an invalid option. Now it seems to work. Thanks for the reply. Sometimes I don't remember to see manual page...my big bug... Polytropon +1 , Me -1 :D At the next. See u ___ 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: FreeBSD on kvm
On 1/6/12 6:20 PM, Alessandro Baggi wrote: > On 01/06/2012 06:12 PM, Damien Fleuriot wrote: >> On 1/6/12 5:50 PM, Alessandro Baggi wrote: >>> On 01/06/2012 05:40 PM, Damien Fleuriot wrote: On 1/6/12 4:18 PM, Alessandro Baggi wrote: > On 01/06/2012 12:50 PM, Damien Fleuriot wrote: >> On 1/6/12 11:43 AM, Alessandro Baggi wrote: >>> Hi list, >>> i've a problem running freebsd as a guest on linux+kvm. The only >>> problem >>> is that sometimes, when I boot the system it dies and this happens >>> also >>> if I run the vm with and without -nographic option. Using the qemu >>> GUI I >>> can see the it stops on the boot loader menu after the countdown >>> and the >>> only mode to resume the system is reboot the vm. I've reduced the >>> autoboot delay to 1 without no result. >>> >>> >>> Someone know something about this problem? >>> >>> Thanks in advance. >>> >> Hi, >> >> >> This is exactly how to *not* ask a question. >> Please take the time to read this very informative article: >> http://www.catb.org/~esr/faqs/smart-questions.html#beprecise >> >> >> For instance, you've omitted important information such as: >> >> - linux version >> - qemu version >> - freebsd version >> - freebsd error message when "it dies", if any >> - KVM configuration options (disk mode and such) >> >> >> We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM >> for >> over 3 years now for our pre-production environment and are very >> happy >> with it. >> >> Please post some more details, that we might be able to actually >> help. >> ___ >> 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" >> > True, I'm sorry, too few informations. > > The host system is Slackware64 Linux 13.37 > QEMU emulator version 0.14.0 (qemu-kvm-0.14.0), Copyright (c) > 2003-2008 > Fabrice Bellard > FreeBSD 8.2-RELEASE-p3 > > > > kvm option: /usr/bin/qemu-system-x86_64 -pidfile $PIDFILE -cpu host > -smp > $NCPU -m $MRAM -k $KB -enable-kvm -drive > file=$IMAGE,media=disk,index=0,cache=writeback -net > nic,model=$NICMODEL,macaddr=$MAC -net > tap,ifname=$TAP,script=no,downscript=no -runas $USER -monitor > unix:$SOCKET,server,nowait -nographic -daemonize > > There are not errors. When there is the countdown it seems to die.For > example it stops to 9 seconds or 6 and stop (die) No boot line, > only the > boot loader menu blocked. To avoid this > I want say that freebsd work very well under kvm, the problem is > presented every 2/3 startup of this virtual machine. > What disk format do you use, with KVM ? QCOW2, RAW, VirtIO ? We're running with QCOW2 here, emulating IDE drives and we don't have any problem. ___ 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" >>> I'm using QCOW2. >>> For ide drives do you give -hda? >>> >>> Info: if I give Enter during the countdown, it starts, if i leave the >>> countdown to finish, it crash. >>> But running with -nographic there isn't sense to give "enter" >>> >>> Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give >>> me some "crash". >>> There is a possibility to run directly the system instead print the >>> menu? I must install lilo/grub? >>> >>> Thanks in advance. >> >> QEMU emulator version 0.15.0 (qemu-kvm-devel), Copyright (c) 2003-2008 >> Fabrice Bellard >> >> >> Find below the resulting command-line used to run a typical FreeBSD KVM >> from our Proxmox interface: >> >> /usr/bin/kvm -monitor unix:/var/run/qemu-server/141.mon,server,nowait >> -vnc unix:/var/run/qemu-server/141.vnc,password -pidfile >> /var/run/qemu-server/141.pid -daemonize -usbdevice tablet -name >> yournamehere -smp sockets=2,cores=2 -nodefaults -boot menu=on -vga >> cirrus -tdf -k fr -drive >> file=/var/lib/vz/images/141/vm-141-disk-1.qcow2,if=ide,index=0 -m 512 >> -netdev >> type=tap,id=vlan18d0,ifname=tap141i18d0,script=/var/lib/qemu-server/bridge-vlan >> >> -device e1000,romfile=,mac=9E:6C:42:78:98:E2,netdev=vlan18d0 -netdev >> type=tap,id=vlan730d0,ifname=tap141i730d0,script=/var/lib/qemu-server/bridge-vlan >> >> -device e1000,romfile=,mac=E6:BA:DA:56:C9:66,netdev=vlan730d0 -netdev >> type=tap,id=vlan731d0,ifname=tap141i731d0,script=/var/lib/qemu-server/bridge-vlan >> >> -device e1000,romfile=,mac=8E:B5:8F:30:F2:C1,netdev=vlan731d0 -id 141 >> -cpuunits 1000 >> >> Also find below the contents of the config file
Re: Apparently conflicting smartctl output
On Thu, 05 Jan 2012 11:56:44 -0800 Chuck Swiger wrote: > On Jan 5, 2012, at 11:42 AM, Janos Dohanics wrote: > > - Do I have a bad hard drive (apparently, I do...) > > > > - Why are there "No Errors Logged" by smartctl? > > You've probably got a bad sector on the drive, anyway. > > The SMART error log is a funny thing governed by various drive's > firmware which have quirks. Some of 'em only have a self-test log, > but don't store the error log at all; others will only record an > error after they've given up trying to remap a failing sector. You > snipped too much of the smartctl output to see what the "Error > logging capability" section says-- the full output would be more > informative. > > You almost certainly want to do a full read-scan of the drive via "dd > if=/dev/ad4 of=/dev/null bs=64k", which will help the drive notice > any other failing sectors. Repeat dd if it aborts early with an > error (or add "conv=noerror", maybe). > > Regards, > -- > -Chuck Chuck, Thank you - dd says: dd: /dev/ad4: Input/output error 10025840+0 records in 10025840+0 records out 657053450240 bytes transferred in 5230.204427 secs (125626724 bytes/sec) I have to replace this drive. -- Janos Dohanics ___ 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: FreeBSD on kvm
On 01/06/2012 06:12 PM, Damien Fleuriot wrote: On 1/6/12 5:50 PM, Alessandro Baggi wrote: On 01/06/2012 05:40 PM, Damien Fleuriot wrote: On 1/6/12 4:18 PM, Alessandro Baggi wrote: On 01/06/2012 12:50 PM, Damien Fleuriot wrote: On 1/6/12 11:43 AM, Alessandro Baggi wrote: Hi list, i've a problem running freebsd as a guest on linux+kvm. The only problem is that sometimes, when I boot the system it dies and this happens also if I run the vm with and without -nographic option. Using the qemu GUI I can see the it stops on the boot loader menu after the countdown and the only mode to resume the system is reboot the vm. I've reduced the autoboot delay to 1 without no result. Someone know something about this problem? Thanks in advance. Hi, This is exactly how to *not* ask a question. Please take the time to read this very informative article: http://www.catb.org/~esr/faqs/smart-questions.html#beprecise For instance, you've omitted important information such as: - linux version - qemu version - freebsd version - freebsd error message when "it dies", if any - KVM configuration options (disk mode and such) We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM for over 3 years now for our pre-production environment and are very happy with it. Please post some more details, that we might be able to actually help. ___ 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" True, I'm sorry, too few informations. The host system is Slackware64 Linux 13.37 QEMU emulator version 0.14.0 (qemu-kvm-0.14.0), Copyright (c) 2003-2008 Fabrice Bellard FreeBSD 8.2-RELEASE-p3 kvm option: /usr/bin/qemu-system-x86_64 -pidfile $PIDFILE -cpu host -smp $NCPU -m $MRAM -k $KB -enable-kvm -drive file=$IMAGE,media=disk,index=0,cache=writeback -net nic,model=$NICMODEL,macaddr=$MAC -net tap,ifname=$TAP,script=no,downscript=no -runas $USER -monitor unix:$SOCKET,server,nowait -nographic -daemonize There are not errors. When there is the countdown it seems to die.For example it stops to 9 seconds or 6 and stop (die) No boot line, only the boot loader menu blocked. To avoid this I want say that freebsd work very well under kvm, the problem is presented every 2/3 startup of this virtual machine. What disk format do you use, with KVM ? QCOW2, RAW, VirtIO ? We're running with QCOW2 here, emulating IDE drives and we don't have any problem. ___ 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" I'm using QCOW2. For ide drives do you give -hda? Info: if I give Enter during the countdown, it starts, if i leave the countdown to finish, it crash. But running with -nographic there isn't sense to give "enter" Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give me some "crash". There is a possibility to run directly the system instead print the menu? I must install lilo/grub? Thanks in advance. QEMU emulator version 0.15.0 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard Find below the resulting command-line used to run a typical FreeBSD KVM from our Proxmox interface: /usr/bin/kvm -monitor unix:/var/run/qemu-server/141.mon,server,nowait -vnc unix:/var/run/qemu-server/141.vnc,password -pidfile /var/run/qemu-server/141.pid -daemonize -usbdevice tablet -name yournamehere -smp sockets=2,cores=2 -nodefaults -boot menu=on -vga cirrus -tdf -k fr -drive file=/var/lib/vz/images/141/vm-141-disk-1.qcow2,if=ide,index=0 -m 512 -netdev type=tap,id=vlan18d0,ifname=tap141i18d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=9E:6C:42:78:98:E2,netdev=vlan18d0 -netdev type=tap,id=vlan730d0,ifname=tap141i730d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=E6:BA:DA:56:C9:66,netdev=vlan730d0 -netdev type=tap,id=vlan731d0,ifname=tap141i731d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=8E:B5:8F:30:F2:C1,netdev=vlan731d0 -id 141 -cpuunits 1000 Also find below the contents of the config file for the guest: -> cat /etc/qemu-server/141.conf name: [snip] bootdisk: virtio0 ostype: other memory: 512 onboot: 1 sockets: 2 ide0: local:141/vm-141-disk-1.qcow2 vlan18: e1000=9E:6C:42:78:98:E2 cores: 2 vlan730: e1000=E6:BA:DA:56:C9:66 vlan731: e1000=8E:B5:8F:30:F2:C1 Do not pay attention to "bootdisk: virtio0", we use "ide0" for other FreeBSD KVMs just as well. I'm beginning to think your VM might be crashing while/because it's actually probing for other devices. What's the full list of devices you have attached to your VM ? Do we have any boot stages expert on the list ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/free
Re: FreeBSD on kvm
On Fri, 06 Jan 2012 17:50:41 +0100, Alessandro Baggi wrote: > Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give > me some "crash". > There is a possibility to run directly the system instead print the > menu? I must install lilo/grub? Let's first assume that you did not install the boot manager (which would be useless in your particular application case); instead, you have installed the standard MBR. Modify /boot/loader.conf to something like this: autoboot_delay="0" beastie_disable="YES" userconfig_script_load="NO" verbose_loading="YES" Refer to /boot/defaults/loader.conf for the meaning of the options if they're not obvious. :-) Regarding the autoboot delay, let me quote from that file: Delay in seconds before autobooting, set to -1 if you don't want user to be allowed to interrupt autoboot process and escape to the loader prompt, set to "NO" to disable autobooting That means ="0" would mean to boot immediately _with_ the option to get to the boot prompt - you just need to be fast at the keyboard. :-) Oh, and see "man loader.conf" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
acer ?? i had this with acer.. remove hdd...acess bios change ahci mode and try installing again. On Fri, Jan 6, 2012 at 8:16 PM, Matthias Apitz wrote: > El día Friday, January 06, 2012 a las 06:37:02AM -0800, Waitman Gobble > escribió: > > > On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman > wrote: > > > > > > > > I had been running a similar computer with Windows XP with it. The > > > drive was working fine a few moments before I did the install. I have > > > a utility to test hard drives which boots from CD but like I said, when > > > this drive is on a cable connected to any machine, booting is a > > > non-option. I have an old IDE controller but it's ISA and I have > > > not ISA slots on this computer. Looks like I may have to try the USB > > > drive boot option to get on with this rescue. > > > > > It seems that there are BIOS features which need to have access to > certain sectors of the disk with additional (Winblows) software. Once > you format the entire disk for FreeBSD you will not enter the BIOS > dialogue, nor it will boot anymore; google for a thread of FreeBSD > installation on Acer laptops. > > HIH > >matthias > -- > Matthias Apitz > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e - w http://www.unixarea.de/ > UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) > UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 > ___ > 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" > -- Best Regards, Mubeesh Ali.V.M ___ 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: FreeBSD on kvm
On 1/6/12 5:50 PM, Alessandro Baggi wrote: > On 01/06/2012 05:40 PM, Damien Fleuriot wrote: >> >> On 1/6/12 4:18 PM, Alessandro Baggi wrote: >>> On 01/06/2012 12:50 PM, Damien Fleuriot wrote: On 1/6/12 11:43 AM, Alessandro Baggi wrote: > Hi list, > i've a problem running freebsd as a guest on linux+kvm. The only > problem > is that sometimes, when I boot the system it dies and this happens > also > if I run the vm with and without -nographic option. Using the qemu > GUI I > can see the it stops on the boot loader menu after the countdown > and the > only mode to resume the system is reboot the vm. I've reduced the > autoboot delay to 1 without no result. > > > Someone know something about this problem? > > Thanks in advance. > Hi, This is exactly how to *not* ask a question. Please take the time to read this very informative article: http://www.catb.org/~esr/faqs/smart-questions.html#beprecise For instance, you've omitted important information such as: - linux version - qemu version - freebsd version - freebsd error message when "it dies", if any - KVM configuration options (disk mode and such) We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM for over 3 years now for our pre-production environment and are very happy with it. Please post some more details, that we might be able to actually help. ___ 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" >>> True, I'm sorry, too few informations. >>> >>> The host system is Slackware64 Linux 13.37 >>> QEMU emulator version 0.14.0 (qemu-kvm-0.14.0), Copyright (c) 2003-2008 >>> Fabrice Bellard >>> FreeBSD 8.2-RELEASE-p3 >>> >>> >>> >>> kvm option: /usr/bin/qemu-system-x86_64 -pidfile $PIDFILE -cpu host -smp >>> $NCPU -m $MRAM -k $KB -enable-kvm -drive >>> file=$IMAGE,media=disk,index=0,cache=writeback -net >>> nic,model=$NICMODEL,macaddr=$MAC -net >>> tap,ifname=$TAP,script=no,downscript=no -runas $USER -monitor >>> unix:$SOCKET,server,nowait -nographic -daemonize >>> >>> There are not errors. When there is the countdown it seems to die.For >>> example it stops to 9 seconds or 6 and stop (die) No boot line, only the >>> boot loader menu blocked. To avoid this >>> I want say that freebsd work very well under kvm, the problem is >>> presented every 2/3 startup of this virtual machine. >>> >> >> What disk format do you use, with KVM ? >> QCOW2, RAW, VirtIO ? >> >> We're running with QCOW2 here, emulating IDE drives and we don't have >> any problem. >> >> ___ >> 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" >> > I'm using QCOW2. > For ide drives do you give -hda? > > Info: if I give Enter during the countdown, it starts, if i leave the > countdown to finish, it crash. > But running with -nographic there isn't sense to give "enter" > > Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give > me some "crash". > There is a possibility to run directly the system instead print the > menu? I must install lilo/grub? > > Thanks in advance. QEMU emulator version 0.15.0 (qemu-kvm-devel), Copyright (c) 2003-2008 Fabrice Bellard Find below the resulting command-line used to run a typical FreeBSD KVM from our Proxmox interface: /usr/bin/kvm -monitor unix:/var/run/qemu-server/141.mon,server,nowait -vnc unix:/var/run/qemu-server/141.vnc,password -pidfile /var/run/qemu-server/141.pid -daemonize -usbdevice tablet -name yournamehere -smp sockets=2,cores=2 -nodefaults -boot menu=on -vga cirrus -tdf -k fr -drive file=/var/lib/vz/images/141/vm-141-disk-1.qcow2,if=ide,index=0 -m 512 -netdev type=tap,id=vlan18d0,ifname=tap141i18d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=9E:6C:42:78:98:E2,netdev=vlan18d0 -netdev type=tap,id=vlan730d0,ifname=tap141i730d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=E6:BA:DA:56:C9:66,netdev=vlan730d0 -netdev type=tap,id=vlan731d0,ifname=tap141i731d0,script=/var/lib/qemu-server/bridge-vlan -device e1000,romfile=,mac=8E:B5:8F:30:F2:C1,netdev=vlan731d0 -id 141 -cpuunits 1000 Also find below the contents of the config file for the guest: -> cat /etc/qemu-server/141.conf name: [snip] bootdisk: virtio0 ostype: other memory: 512 onboot: 1 sockets: 2 ide0: local:141/vm-141-disk-1.qcow2 vlan18: e1000=9E:6C:42:78:98:E2 cores: 2 vlan730: e1000=E6:BA:DA:56:C9:66 vlan731: e1000=8E:B5:8F:30:F2:C1 Do not pay attention to "bootdisk: virtio0", we use "ide0" for other FreeBSD KVMs just as well. I'm beginning to think y
Re: FreeBSD on kvm
On 01/06/2012 05:40 PM, Damien Fleuriot wrote: On 1/6/12 4:18 PM, Alessandro Baggi wrote: On 01/06/2012 12:50 PM, Damien Fleuriot wrote: On 1/6/12 11:43 AM, Alessandro Baggi wrote: Hi list, i've a problem running freebsd as a guest on linux+kvm. The only problem is that sometimes, when I boot the system it dies and this happens also if I run the vm with and without -nographic option. Using the qemu GUI I can see the it stops on the boot loader menu after the countdown and the only mode to resume the system is reboot the vm. I've reduced the autoboot delay to 1 without no result. Someone know something about this problem? Thanks in advance. Hi, This is exactly how to *not* ask a question. Please take the time to read this very informative article: http://www.catb.org/~esr/faqs/smart-questions.html#beprecise For instance, you've omitted important information such as: - linux version - qemu version - freebsd version - freebsd error message when "it dies", if any - KVM configuration options (disk mode and such) We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM for over 3 years now for our pre-production environment and are very happy with it. Please post some more details, that we might be able to actually help. ___ 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" True, I'm sorry, too few informations. The host system is Slackware64 Linux 13.37 QEMU emulator version 0.14.0 (qemu-kvm-0.14.0), Copyright (c) 2003-2008 Fabrice Bellard FreeBSD 8.2-RELEASE-p3 kvm option: /usr/bin/qemu-system-x86_64 -pidfile $PIDFILE -cpu host -smp $NCPU -m $MRAM -k $KB -enable-kvm -drive file=$IMAGE,media=disk,index=0,cache=writeback -net nic,model=$NICMODEL,macaddr=$MAC -net tap,ifname=$TAP,script=no,downscript=no -runas $USER -monitor unix:$SOCKET,server,nowait -nographic -daemonize There are not errors. When there is the countdown it seems to die.For example it stops to 9 seconds or 6 and stop (die) No boot line, only the boot loader menu blocked. To avoid this I want say that freebsd work very well under kvm, the problem is presented every 2/3 startup of this virtual machine. What disk format do you use, with KVM ? QCOW2, RAW, VirtIO ? We're running with QCOW2 here, emulating IDE drives and we don't have any problem. ___ 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" I'm using QCOW2. For ide drives do you give -hda? Info: if I give Enter during the countdown, it starts, if i leave the countdown to finish, it crash. But running with -nographic there isn't sense to give "enter" Leaving delay boot to 10 sec, always block. Set delay boot to 1, it give me some "crash". There is a possibility to run directly the system instead print the menu? I must install lilo/grub? Thanks in advance. ___ 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: Apparently conflicting smartctl output
On 01/06/2012 04:37 PM, Warren Block wrote: On Fri, 6 Jan 2012, Bas Smeelen wrote: On 01/06/2012 03:39 PM, Warren Block wrote: On Fri, 6 Jan 2012, Bas Smeelen wrote: I have had this with a drive and multiple read errors would not remap the sector. With write errors the sector would be remapped. This was a new Samsung laptop drive though, not a Western Digital. That's standard. Sectors are only remapped to spares on a write error. To get the sector remapped I had to fully write the drive and it was ok after that. Just writing to the sector should be enough. Of course, when one sector goes bad, others often follow. I just hope it does not develop more bad sectors. That's the worrying thing. Was it just a loose flake of oxide, or was it a strip that peeled off the disk? No way to know I guess From what I read on the "Bad block HOWTO for smartmontools" on sourceforge it's not trivial to just write to that sector and also it would destroy the filesystem? Finding the right block may not be too hard. /var/log/messages should show the block number, but then I don't know what tool is available to write to that specific block. Tools like that are not common because generally, growing bad sectors means the drive is starting to fail anyway. I could use dd if=/dev/random of=file seek=blocks_to_skip bs=100M the next time So I just copied a big iso file several times untill the sector got remapped, the disk was almost full then. This is a brand new disk, maybe I should return it under warranty then, though it did not develop more bad sectors? If possible, yes. It already lost some data. I'll talk to the supplier anyway when more bad sectors occur Cheers Disclaimer: http://www.ose.nl/email ___ 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"
creating a bootable iso for raid BIOS flash
Hi, I have an Intel SRCU42X raid controller that currently has firmware version 414D. The bios flash was done by a "system update package", from Intel which is an iso file that you can burn to a cd. The upgrade to 414D went fine. But the newest firmware version is 414I and is not available as a bootable iso, only as a 414I.rom file (windows only etc.). So I thought: lets alter the 414D iso to the newest 414I iso, and make a new bootable iso. But this was harder than I thought. I extracted the original iso file with file-roller and replaced the 414D.rom file with 414I.rom, and modified the .bat-files references from 414D to 414I. The files and directories in the original iso are: -rwxr-xr-x 1 marco wheel 7828 Feb 9 2006 LICENSE.TXT drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCS16 drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCS28X drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU41L drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU42E drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCU42L drwxr-xr-x 2 marco wheel 512 Jan 6 11:24 SRCU42X drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SRCZCRX drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 SROMB42E -rwxr-xr-x 1 marco wheel 1207 Aug 23 2004 SUP.BAT -rwxr-xr-x 1 marco wheel 3732 Feb 11 2006 SUP.TXT -rwxr-xr-x 1 marco wheel 4350 Mar 10 2006 SUP_Release_note.txt -rwxr-xr-x 1 marco wheel 5479 Feb 10 2006 UPDATE.BAT -rwxr-xr-x 1 marco wheel 244 Jan 6 11:25 VER_LOAD.BAT drwxr-xr-x 2 marco wheel 512 Jan 6 11:19 [BOOT] The SRCU42X directory contains the 414I.rom file, an irflash.exe update utility and a run.bat batch file (running irflash.exe with reference to the .rom file). The [BOOT] directory contains one file: Bootable_HardDisk.img. After that I tried to create the iso with: root@yokozuna:/data2/tmp# mkisofs -r -J -b [BOOT]/Bootable_HardDisk.img -hard-disk-boot -o raid.iso /data2/tmp which gives an error: mkisofs: No match First I thought the directory name [BOOT] was weird so I changed this to BOOT. Running mkisofs -r -J -b BOOT/Bootable_HardDisk.img -hard-disk-boot -o raid.iso /data2/tmp creates an iso, but when I burn this to a cd it doesn't boot. Strange thing also is the fact that the original iso has the size of ~17MB, but the created iso by me is ~10MB. So it seems I'm missing some files. So what am I doing wrong and what is the correct commandline to create a bootable iso for flashing a raid controller bios? Thanks, Marco -- If I promised you the moon and the stars, would you believe it? -- Alan Parsons Project ___ 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: FreeBSD on kvm
On 1/6/12 4:18 PM, Alessandro Baggi wrote: > On 01/06/2012 12:50 PM, Damien Fleuriot wrote: >> On 1/6/12 11:43 AM, Alessandro Baggi wrote: >>> Hi list, >>> i've a problem running freebsd as a guest on linux+kvm. The only problem >>> is that sometimes, when I boot the system it dies and this happens also >>> if I run the vm with and without -nographic option. Using the qemu GUI I >>> can see the it stops on the boot loader menu after the countdown and the >>> only mode to resume the system is reboot the vm. I've reduced the >>> autoboot delay to 1 without no result. >>> >>> >>> Someone know something about this problem? >>> >>> Thanks in advance. >>> >> Hi, >> >> >> This is exactly how to *not* ask a question. >> Please take the time to read this very informative article: >> http://www.catb.org/~esr/faqs/smart-questions.html#beprecise >> >> >> For instance, you've omitted important information such as: >> >> - linux version >> - qemu version >> - freebsd version >> - freebsd error message when "it dies", if any >> - KVM configuration options (disk mode and such) >> >> >> We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM for >> over 3 years now for our pre-production environment and are very happy >> with it. >> >> Please post some more details, that we might be able to actually help. >> ___ >> 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" >> > True, I'm sorry, too few informations. > > The host system is Slackware64 Linux 13.37 > QEMU emulator version 0.14.0 (qemu-kvm-0.14.0), Copyright (c) 2003-2008 > Fabrice Bellard > FreeBSD 8.2-RELEASE-p3 > > > > kvm option: /usr/bin/qemu-system-x86_64 -pidfile $PIDFILE -cpu host -smp > $NCPU -m $MRAM -k $KB -enable-kvm -drive > file=$IMAGE,media=disk,index=0,cache=writeback -net > nic,model=$NICMODEL,macaddr=$MAC -net > tap,ifname=$TAP,script=no,downscript=no -runas $USER -monitor > unix:$SOCKET,server,nowait -nographic -daemonize > > There are not errors. When there is the countdown it seems to die.For > example it stops to 9 seconds or 6 and stop (die) No boot line, only the > boot loader menu blocked. To avoid this > I want say that freebsd work very well under kvm, the problem is > presented every 2/3 startup of this virtual machine. > What disk format do you use, with KVM ? QCOW2, RAW, VirtIO ? We're running with QCOW2 here, emulating IDE drives and we don't have any problem. ___ 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: Apparently conflicting smartctl output
On Fri, 6 Jan 2012, Bas Smeelen wrote: On 01/06/2012 03:39 PM, Warren Block wrote: On Fri, 6 Jan 2012, Bas Smeelen wrote: I have had this with a drive and multiple read errors would not remap the sector. With write errors the sector would be remapped. This was a new Samsung laptop drive though, not a Western Digital. That's standard. Sectors are only remapped to spares on a write error. To get the sector remapped I had to fully write the drive and it was ok after that. Just writing to the sector should be enough. Of course, when one sector goes bad, others often follow. I just hope it does not develop more bad sectors. That's the worrying thing. Was it just a loose flake of oxide, or was it a strip that peeled off the disk? From what I read on the "Bad block HOWTO for smartmontools" on sourceforge it's not trivial to just write to that sector and also it would destroy the filesystem? Finding the right block may not be too hard. /var/log/messages should show the block number, but then I don't know what tool is available to write to that specific block. Tools like that are not common because generally, growing bad sectors means the drive is starting to fail anyway. So I just copied a big iso file several times untill the sector got remapped, the disk was almost full then. This is a brand new disk, maybe I should return it under warranty then, though it did not develop more bad sectors? If possible, yes. It already lost some data. ___ 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: FreeBSD on kvm
On 01/06/2012 12:50 PM, Damien Fleuriot wrote: On 1/6/12 11:43 AM, Alessandro Baggi wrote: Hi list, i've a problem running freebsd as a guest on linux+kvm. The only problem is that sometimes, when I boot the system it dies and this happens also if I run the vm with and without -nographic option. Using the qemu GUI I can see the it stops on the boot loader menu after the countdown and the only mode to resume the system is reboot the vm. I've reduced the autoboot delay to 1 without no result. Someone know something about this problem? Thanks in advance. Hi, This is exactly how to *not* ask a question. Please take the time to read this very informative article: http://www.catb.org/~esr/faqs/smart-questions.html#beprecise For instance, you've omitted important information such as: - linux version - qemu version - freebsd version - freebsd error message when "it dies", if any - KVM configuration options (disk mode and such) We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM for over 3 years now for our pre-production environment and are very happy with it. Please post some more details, that we might be able to actually help. ___ 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" True, I'm sorry, too few informations. The host system is Slackware64 Linux 13.37 QEMU emulator version 0.14.0 (qemu-kvm-0.14.0), Copyright (c) 2003-2008 Fabrice Bellard FreeBSD 8.2-RELEASE-p3 kvm option: /usr/bin/qemu-system-x86_64 -pidfile $PIDFILE -cpu host -smp $NCPU -m $MRAM -k $KB -enable-kvm -drive file=$IMAGE,media=disk,index=0,cache=writeback -net nic,model=$NICMODEL,macaddr=$MAC -net tap,ifname=$TAP,script=no,downscript=no -runas $USER -monitor unix:$SOCKET,server,nowait -nographic -daemonize There are not errors. When there is the countdown it seems to die.For example it stops to 9 seconds or 6 and stop (die) No boot line, only the boot loader menu blocked. To avoid this I want say that freebsd work very well under kvm, the problem is presented every 2/3 startup of this virtual machine. ___ 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: Apparently conflicting smartctl output
On 01/06/2012 03:39 PM, Warren Block wrote: > On Fri, 6 Jan 2012, Bas Smeelen wrote: > >> I have had this with a drive and multiple read errors would not remap the >> sector. >> With write errors the sector would be remapped. This was a new Samsung >> laptop drive though, not a Western Digital. > > That's standard. Sectors are only remapped to spares on a write error. > >> To get the sector remapped I had to fully write the drive and it was ok >> after that. > > Just writing to the sector should be enough. Of course, when one sector > goes bad, others often follow. I just hope it does not develop more bad sectors. >From what I read on the "Bad block HOWTO for smartmontools" on sourceforge it's not trivial to just write to that sector and also it would destroy the filesystem? So I just copied a big iso file several times untill the sector got remapped, the disk was almost full then. This is a brand new disk, maybe I should return it under warranty then, though it did not develop more bad sectors? Disclaimer: http://www.ose.nl/email ___ 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"
xfce4 / gtk-update-icon-cache fails with "cairo needs X11"
Hi, I am doing a fresh install of FreeBSD 9.0-RC3 from FreeBSD-9.0-RELEASE-i386-memstick.img on an Acer Aspire One netbook. Last night I attempted to install xfce4 from /usr/ports/x11-wm and it stopped with error: gtk-update-icon-cache-(version): Needs cairo build with X11 support (sorry, don't recall version off the top of my head) I remember that cairo was installed before getting to gtk-update-icon-cache. I checked /etc/make.conf and there is nothing X11 related, ie WITHOUT_X11 is NOT set. I went over to /usr/ports/graphics/cairo and did a make config, did not see anything about X11 as an option, did a make install clean and I saw libX11 in the output.. Think it's ok. Then I went back to /usr/ports/x11-wm/xfce4 and redid make install clean to build... it continued on without further issue (so far :) I found another post about gtk-update-icon-cache and cairo/X11 but it does not appear to be a related issue. At the moment the xfce4 build is working for me, so my issue is resolved.. But not sure why I received the error, might be something to check out? Is there a better place to report potential issues with RC versions? Excited about 9 on the netbook, I tried FreeBSD 7.0 when i first got the Acer but could not get wireless working at the time so i scrapped it. Thanks, Waitman Gobble San Jose California USA ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
El día Friday, January 06, 2012 a las 06:37:02AM -0800, Waitman Gobble escribió: > On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman wrote: > > > > > I had been running a similar computer with Windows XP with it. The > > drive was working fine a few moments before I did the install. I have > > a utility to test hard drives which boots from CD but like I said, when > > this drive is on a cable connected to any machine, booting is a > > non-option. I have an old IDE controller but it's ISA and I have > > not ISA slots on this computer. Looks like I may have to try the USB > > drive boot option to get on with this rescue. > > It seems that there are BIOS features which need to have access to certain sectors of the disk with additional (Winblows) software. Once you format the entire disk for FreeBSD you will not enter the BIOS dialogue, nor it will boot anymore; google for a thread of FreeBSD installation on Acer laptops. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
On Thu, 5 Jan 2012, Bill Tillman wrote: Well the install finished and then I attempted to reboot the system but nothing happened. And by that I mean the computer's flash screen would come up and give me the choice to enter the Bios Setup or Boot Menu and that's all. The BIOS on some systems expects a particular partition layout. In the old days, Compaq had a BIOS partition on the disk. Today, there are there are still weird things that can be vendor-specific. Or new standards like UEFI. So the problem could be specific to that particular computer model or brand. Attaching the drive to a USB to IDE adapter might avoid the problem, allowing a boot from another drive. Before rewriting the do-nothing drive, use 'gpart show' or fdisk to see the partition layout that is the problem. ___ 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: Apparently conflicting smartctl output
On Fri, 6 Jan 2012, Bas Smeelen wrote: I have had this with a drive and multiple read errors would not remap the sector. With write errors the sector would be remapped. This was a new Samsung laptop drive though, not a Western Digital. That's standard. Sectors are only remapped to spares on a write error. To get the sector remapped I had to fully write the drive and it was ok after that. Just writing to the sector should be enough. Of course, when one sector goes bad, others often follow. ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
On Fri, Jan 6, 2012 at 3:21 AM, Bill Tillman wrote: > > I had been running a similar computer with Windows XP with it. The > drive was working fine a few moments before I did the install. I have > a utility to test hard drives which boots from CD but like I said, when > this drive is on a cable connected to any machine, booting is a > non-option. I have an old IDE controller but it's ISA and I have > not ISA slots on this computer. Looks like I may have to try the USB > drive boot option to get on with this rescue. > > Weirdness.. ok, i was wondering - you said you installed an old drive to check it out, and I was thinking hmm 80gb, maybe setting on the shelf for a decade :) I do recall having a similar issue with a drive, but it was years and years ago- my memory hazed, and not necessarily (probably not) related to FreeBSD install. If you aren't getting POST then it sounds hardware related to me. Good Luck, Waitman ___ 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: Realtek RTL8191SEvB Linux driver?
On 01/06/12 07:42, Peter Harrison wrote: Thursday, 5 January 2012 at 9:04:40 +1000, Da Rock said: On 01/05/12 07:01, Peter Harrison wrote: On 4 Jan 2012, at 01:08, Da Rock wrote: On 01/04/12 10:38, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/04/12 02:10, Daniel Feenberg wrote: On Wed, 4 Jan 2012, Da Rock wrote: On 01/03/12 22:10, Jerry wrote: On Tue, 03 Jan 2012 16:44:30 +1000 Da Rock articulated: On 01/03/12 11:15, Jeffrey McFadden wrote: Don't ndis(4) ndiscvt and ndisgen(8) essentially accomplish what the OP is requesting? See the handbook section 12.8.1.1: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/config-network-setup.html or the man page for ndiscvt: http://www.gsp.com/cgi-bin/man.cgi?section=8&topic=ndiscvt While doing the conversion looks a bit beyond what we would expect of an end-user, it does seem to offer a path for using hardware whose manufacturer does not support FreeBSD. Is there anything beyond licensing issues preventing such drivers from being included in the distribution, or made downloadable in FreeBSD form? Oh yes, it is possible, just not probable :) At http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=Category:USB almost 800 compatible devices are listed. Not everything, but I have found that a willingness to spend a few dollars on a different card helps immensely in enjoying FreeBSD and Linux. For me at least it is easier to find a compatible card than to write a compatible driver. Indeed :) I did notice that the card in question wasn't on that list. But my own experience with ndiswrapper and wifi cards were far less than satisfactory- the firmware always got in the road. But I may have just been too stupid at the time :) I would also observe that most people involved with computers, whether as users or developers, have little symphathy for people with different needs from the device. This is a great impediment to progress. It is a mistake to assume that because you don't need something, another person's desire for it is illegitimate. In this case, I fully agree that it is an injustice that hardware vendors do not supply FreeBSD drivers, but that does not mean that users requiring such drivers are immoral or of poor character, and therefore to be ignored or insulted. There is little that FreeBSD coders and users can do about that injustice directly, however it is within their power to mitigate it with the NDIS wrapper. If that wrapper allows another user to enter the FOSS world, that will (in the fullness of time) contribute to reforming the vendor. No they are absolutely not of poor character, I agree. Some messages can be misconstrued, though, in that the replies can be terse and more logical than sympathetic. Sometimes it is easier to replace with a different card than flog a dead horse, although a user may take offense for emotional or financial reasons more than logical. Mitigation is a difficult path as I have found personally, although NDIS helps immensely with wired nics (not so much of a problem these days), and I believe Luigi Rizzo's work with the linuxulator and drivers is to be applauded ten fold. It takes a great deal of time though- I put forward the idea when I was still a BSD pup not entirely realising the challenges :) Luigi (and his colleagues) has been working hard ever since to facilitate the more challenging aspects of multimedia drivers (whether or not that had to do with my comments or not, I don't know). Da Rock, I've been using ndis drivers successfully with a Broadcom chip in my Lenovo s10-e since I bought it some years ago - to the extent that I've not yet switched over to the native drivers now available. I didn't find using ndisgen too problematic. Just a case of finding the right driver files and following the manpage. I'd strongly recommend trying it in preference to a usb stick (been there, done that) or buying new hardware - although I'd agree that depending on the model changing a mini-PCI card isn't necessarily that difficult (I changed it t an Intel card in my other Dell laptop some time ago - remember to attach the internal aerial cable!). Make no mistake I'm not being facetious. How did you do it? The biggest problem I had was that there are multiple firmware for different scenarios that are loaded. One for base station mode, one for adhoc, and one more I think... They got in the way of using it correctly. Da Rock, The short answer is, I'm not honestly sure. It was a couple of years ago and it's given absolutely no trouble since - a genuine "fit and forget" solution. I remember it as being a question of finding and unpacking the right file then using the .sys and .inf files to create a kernel module using ndisgen. Don't recall having any problems with firmware. The only issue I recall was I think to do with converting the .inf file to unicode, but I might have mis-remembered that. Sorry I can't be more help. I think I hit the same issue, b
Re: FreeBSD on kvm
On 1/6/12 11:43 AM, Alessandro Baggi wrote: > Hi list, > i've a problem running freebsd as a guest on linux+kvm. The only problem > is that sometimes, when I boot the system it dies and this happens also > if I run the vm with and without -nographic option. Using the qemu GUI I > can see the it stops on the boot loader menu after the countdown and the > only mode to resume the system is reboot the vm. I've reduced the > autoboot delay to 1 without no result. > > > Someone know something about this problem? > > Thanks in advance. > Hi, This is exactly how to *not* ask a question. Please take the time to read this very informative article: http://www.catb.org/~esr/faqs/smart-questions.html#beprecise For instance, you've omitted important information such as: - linux version - qemu version - freebsd version - freebsd error message when "it dies", if any - KVM configuration options (disk mode and such) We've been running FreeBSD 7 then 8 as a guest in Debian linux/KVM for over 3 years now for our pre-production environment and are very happy with it. Please post some more details, that we might be able to actually help. ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
From: Waitman Gobble To: Bill Tillman Cc: FreeBSD Questions Sent: Friday, January 6, 2012 5:09 AM Subject: Re: 9.0-RELEASE amd64 Bricked My Hard Drive On Thu, Jan 5, 2012 at 7:16 PM, Bill Tillman wrote: > Today I encountered a problem which has me stumped. I downloaded and > burned the ISO image for 9.0-RELEASE for amd64. I installed an older > IDE hard drive to test the new OS with and did the install. ... > Well the install finished and > then I attempted to reboot the system but nothing happened. And by that I > mean the computer's flash screen would come up and give me the choice > to enter the Bios Setup or Boot Menu and that's all. I could not enter the > bios setup or the Boot menu. ... > So basically, > FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive > and I can't seem to recover it. > > > Hi Bill, What was going on with this drive before the install? ie, it was sitting on the self not being used, it was a daily use machine running something else, ... etc. At the moment it sounds to me like an inconvenient hardware failure. Waitman ___ 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" I had been running a similar computer with Windows XP with it. The drive was working fine a few moments before I did the install. I have a utility to test hard drives which boots from CD but like I said, when this drive is on a cable connected to any machine, booting is a non-option. I have an old IDE controller but it's ISA and I have not ISA slots on this computer. Looks like I may have to try the USB drive boot option to get on with this rescue. ___ 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"
FreeBSD on kvm
Hi list, i've a problem running freebsd as a guest on linux+kvm. The only problem is that sometimes, when I boot the system it dies and this happens also if I run the vm with and without -nographic option. Using the qemu GUI I can see the it stops on the boot loader menu after the countdown and the only mode to resume the system is reboot the vm. I've reduced the autoboot delay to 1 without no result. Someone know something about this problem? Thanks in advance. ___ 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: 9.0-RELEASE amd64 Bricked My Hard Drive
On Thu, Jan 5, 2012 at 7:16 PM, Bill Tillman wrote: > Today I encountered a problem which has me stumped. I downloaded and > burned the ISO image for 9.0-RELEASE for amd64. I installed an older > IDE hard drive to test the new OS with and did the install. ... > Well the install finished and > then I attempted to reboot the system but nothing happened. And by that I > mean the computer's flash screen would come up and give me the choice > to enter the Bios Setup or Boot Menu and that's all. I could not enter the > bios setup or the Boot menu. ... > So basically, > FreeBSD-9.0-RELEASE bricked an otherwise good 80GB hard drive > and I can't seem to recover it. > > > Hi Bill, What was going on with this drive before the install? ie, it was sitting on the self not being used, it was a daily use machine running something else, ... etc. At the moment it sounds to me like an inconvenient hardware failure. Waitman ___ 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: Cannot create 2nd gmirror
On Fri, 6 Jan 2012 11:55:50 +1030 William Brown wrote: > > > > I am trying to add a second gmirror, gm1: > > > > # sysctl kern.geom.debugflags=16 > > kern.geom.debugflags: 16 -> 16 > > > > # gmirror label -v -b round-robin gm1 /dev/ad4 > > Metadata value stored on /dev/ad4. > > Done. > > > > # gmirror insert gm1 /dev/ad6 > > gmirror: No such device: gm1. > > > > Why does gm1 fail to be created? > > > > What is the output of gmirror list after you run the gmirror label? > > Alternately, according to > http://www.freebsd.org/cgi/man.cgi?query=gmirror&apropos=0&sektion=0&manpath=FreeBSD+6.1-RELEASE&format=html > you should be able to just run > > gmirror label -v -b round-robin gm1 /dev/ad4 /dev/ad6 > gmirror rebuild gm1 /dev/ad6 > > > Sincerely, > > William Brown > > Research & Teaching, Technology Services > The University of Adelaide, AUSTRALIA 5005 gmirror list only showed gm0; it did did not show gm1, nor were there any gm1* entries in /dev/mirror. However, as soon as I have unmounted /dev/ad4s1d, /dev/ad4s1e, and /dev/ad4s1f, gm1 was "automagically" created: Jan 4 20:21:27 <0.2> isolde kernel: GEOM_MIRROR: Device mirror/gm1 launched (1/1). Jan 4 20:21:27 <0.2> isolde kernel: GEOM: mirror/gm1s1: geometry does not match label (16h,63s != 255h,63s). Jan 4 21:22:32 <0.2> isolde kernel: GEOM_MIRROR: Device gm1: rebuilding provider ad6. Don't quite understand why creating gm1 happened only after unmounting the filesystems on ad4. -- Janos Dohanics ___ 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"
