Re: Can't compile without COMPAT_43 on i386
Mike Jakubik schrieb: I can compile an amd64 kernel just fine without the option COMPAT_43, but not i386. Why is this? /usr/src/sys/modules/linux/../../i386/linux/linux_sysvec.c:36:2: #error "Unable to compile Linux-emulator due to missing COMPAT_43 option!" mkdep: compile failed I don't want or need the Linux-emulator. The corresponding module will be built nevertheless. If you want to build only a selection of modules then you have to specify MODULES_OVERRIDE, e.g. makeoptions MODULES_OVERRIDE="acpi" in your kernel configuration file. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R/amd64: PXE boot can't handle .gz mfsroot?
Dmitry Morozovsky schrieb: BK> cat /tftpdroot/boot/loader.conf none Then loader.conf of your NFS root. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R/amd64: PXE boot can't handle .gz mfsroot?
On Tue, 9 May 2006, Dmitry Morozovsky wrote:
DM> Colleagues,
DM>
DM> ${SUBJ} says almost all. PXEboot leads to
DM>
DM> Can't work out which disk we are booting from.
DM>
DM> error.
DM>
DM> Ungzipping /boot/mfsroot.gz helps
This was too early positive. It does not help, as unzipped mfsroot is not
actually loaded as filesystem:
OK ls
/
? boot
? boot.config
? boot.catalog
? cdrom.inf
OK lsmod
0x10: /boot/kernel/kernel (elf kernel, 0x8e4268)
modules: linux.1 rr232x.1 io.1 splash.1 agp.1 nfsserver.1 nfslock.1 nfs.1
nfs4.1 wlan.1 if_gif.1 if_faith.1 ether.1 sysvshm.1 sysvsem.1 sysvmsg.1
cd9660.1 isa.1 pseudofs.1 procfs.1 ntfs.1 msdosfs.1 usb.1 cdce.0 random.1
ppbus.1 pci.1 pccard.1 null.1 mpt_raid.1 mpt.1 mpt_cam.1 mpt_core.1 miibus.1
mem.1 isp.1 sbp.1 fwe.1 firewire.1 exca.1 cardbus.1 ast.1 afd.1 acd.1 ataraid.1
atapci.1 ad.1 ata.1 ahc.1 ahd.1 ahd_pci.1 ahc_pci.1 ahc_isa.1 acpi_pci.1 acpi.1
linprocfs.1 cam.1
0x9e4268: /boot/mfsroot (mfs_root, 0x80)
So after loading kernel it complains:
init: not found in path
/sbin/init:/sbin/oinit:/sbin/init.bak:/rescue/init:/stand/sysinstall
panic: no init
(while there was line
md0: Preloaded image 8388608 bytes at 0x809e4268
a few lines before...)
... will experiment further...
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] ***
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RC and the audit group
Pieter de Goeje wrote: Hi Mark, On Wednesday 10 May 2006 00:51, Mark Kirkwood wrote: Just updated another box to 6.1-STABLE, and yes I did 'return' though it. The reason being mergemaster -p wanted to patch my group file to remove all the additions (i.e, useful groups and group -> user associations) as *well* as add the audit group. Well unless -p changes mergemaster's behaviour, the general idea is that you press 'm' for merge ( correct me if I'm wrong but I think mergemaster was named after this feature :P ). It will let you add the new audit group _and_ keep the extra groups. Thanks all - You are quite right - I'm clearly just being a bit thick... Cheers Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RC and the audit group
On May 9, 2006, at 7:03 PM, Pieter de Goeje wrote: Hi Mark, On Wednesday 10 May 2006 00:51, Mark Kirkwood wrote: Doug White wrote: On Sat, 6 May 2006, Mark Kirkwood wrote: I found that installworld stops, because the 'audit' group has not been created. Now I just pressed 'return' for the default actions during mergemaster -p, but I didn't notice any mention of the audit group. The default action is to do nothing, so its possible you just missed it as you were blazing through. :-) Just updated another box to 6.1-STABLE, and yes I did 'return' though it. The reason being mergemaster -p wanted to patch my group file to remove all the additions (i.e, useful groups and group -> user associations) as *well* as add the audit group. Well unless -p changes mergemaster's behaviour, the general idea is that you press 'm' for merge ( correct me if I'm wrong but I think mergemaster was named after this feature :P ). It will let you add the new audit group _and_ keep the extra groups. I can vouch for this working properly! I just ran mergemaster -p in the process of upgrading, when it gets to the passwd and group file, I press M for merge, and select from l and r (left and right) which side I want to keep. Thus I get the new FreeBSD ID string, the new audit group, and all my old local mods. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RC and the audit group
Hi Mark, On Wednesday 10 May 2006 00:51, Mark Kirkwood wrote: > Doug White wrote: > > On Sat, 6 May 2006, Mark Kirkwood wrote: > >> I found that installworld stops, because the 'audit' group has not been > >> created. Now I just pressed 'return' for the default actions during > >> mergemaster -p, but I didn't notice any mention of the audit group. > > > > The default action is to do nothing, so its possible you just missed it > > as you were blazing through. :-) > > Just updated another box to 6.1-STABLE, and yes I did 'return' though > it. The reason being mergemaster -p wanted to patch my group file to > remove all the additions (i.e, useful groups and group -> user > associations) as *well* as add the audit group. Well unless -p changes mergemaster's behaviour, the general idea is that you press 'm' for merge ( correct me if I'm wrong but I think mergemaster was named after this feature :P ). It will let you add the new audit group _and_ keep the extra groups. > > Would be possible (or sensible) to 2-stage this sort of thing? i.e: > > 1/ Add required new groups > 2/ Offer to patch 'em back to default. > > Cheers > > Mark > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Regards, Pieter ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-RC and the audit group
Doug White wrote: On Sat, 6 May 2006, Mark Kirkwood wrote: I found that installworld stops, because the 'audit' group has not been created. Now I just pressed 'return' for the default actions during mergemaster -p, but I didn't notice any mention of the audit group. The default action is to do nothing, so its possible you just missed it as you were blazing through. :-) Just updated another box to 6.1-STABLE, and yes I did 'return' though it. The reason being mergemaster -p wanted to patch my group file to remove all the additions (i.e, useful groups and group -> user associations) as *well* as add the audit group. Would be possible (or sensible) to 2-stage this sort of thing? i.e: 1/ Add required new groups 2/ Offer to patch 'em back to default. Cheers Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CFT: new ath hal (take 2)
On Monday 08 May 2006 12:48, Sam Leffler wrote: > If I had intended stable users to try this code I would have: > > 1. posted to stable@ > 2. provided specific changes for those users (e.g. a patch) > > You will note my initial post about a new hal was done to both mailing > lists. I did not post this hal to stable because I did not want to deal > with people complaining that things did not work because they had > problems back-patching the necessary changes. I included info in my > original post for those folks running current that were going to do it > anyway so they could save some time. > > I replied to your post because all it did was set people up for failures > that would result in mail to me that I don't have time to handle. Then > those people would either get frustrated by not getting an answer or > think there was some problem that wasn't being fixed. > > I treat the stable src tree VERY carefully. I do not inflict pain on > users running stable. I do not arbitrarily commit changes that require > people to manually alter their system or otherwise deal with binary > incompatibilities. I treat stable as a production code base and only > apply changes that are considered well-tested and appropriate to run in > a production environment. > got your point but this is free software and anybody can contribute as well as anybody may decide what works for him or not and use it then with the same spirit. It is oustanding that you are responsible and well organized with your work but this should not cut others freedom to mix it up for themselfs. Good talk, let's move on and may be you find some time to help me finding out why this damned ath cards sometimes stop rx/tx under load. João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
6.1 STABLE amd64 The last messages is: Device configuration finished. procfs registered linprocfs registered lapic: Divisior 2, Frecuency 99710124hz Timecounters "TSC" frecuency 1794793456 Hz quality 800 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 Linux ELF exec handler installed lo0: bpf attached rr232x: no controller detected. Thank you. El Martes, 9 de Mayo de 2006 13:09, Scot Hetzel escribió: > On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: > > Thank for your help, the problem is after to select installation default, > > whitout acpi or safe mode, in all cases the boot loader crashing after > > the next message: > > > > in 6.1 stable > > > > module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 > > Actually, this is from the kernel, not the boot loader. Is the system > hung at this point or is there any other information displayed after > this gets printed? As this information would help the developers > determine whats going wrong on your system. > > If there is additional information, a backtrace (bt) from the debugger > prompt would be useful. > > Scot > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
6.1 STABLE amd64 The last messages is: Device configuration finished. procfs registered linprocfs registered lapic: Divisior 2, Frecuency 99710124hz Timecounters "TSC" frecuency 1794793456 Hz quality 800 Timecounters tick every 1.000 msec module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 Linux ELF exec handler installed lo0: bpf attached rr232x: no controller detected. Thank you. El Martes, 9 de Mayo de 2006 13:09, Scot Hetzel escribió: > On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: > > Thank for your help, the problem is after to select installation default, > > whitout acpi or safe mode, in all cases the boot loader crashing after > > the next message: > > > > in 6.1 stable > > > > module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 > > Actually, this is from the kernel, not the boot loader. Is the system > hung at this point or is there any other information displayed after > this gets printed? As this information would help the developers > determine whats going wrong on your system. > > If there is additional information, a backtrace (bt) from the debugger > prompt would be useful. > > Scot > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: imap w/cleartext on 5.4-RELEASE
On Tue, 9 May 2006, Jonathan Noack wrote: Not to beat an off-topic horse, but... When I switched from Courier IMAP to Dovecot, I saw a huge increase in performance. Dovecot uses index files that prevent it from having to continually scan a mailbox for every request. For my largest folders (30,000+ messages), Dovecot was *at least* an order of magnitude faster. I got it to work right. It turns out that I had to make clean on both cclient and imap-uw, build cclient with "-D WITH_SSL_AND_PLAINTEXT", install it and then do the same with imap-uw. Oh, and it helps to spell "PLAINTEXT" correctly. "PLAIMTEXT" doesn't have the same effect. Thanks for the pointer to Dovecot - I'll check it out. Sorry about the mostly-OT chatter. -Jason - --- There are no ABSOLUTE STATEMENTS I'm very probably wrong. --- "The difference between genius and stupidity is that genius has its limits." - Albert Einstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: imap w/cleartext on 5.4-RELEASE
Mike Jakubik wrote: jason wrote: I'm trying to get imap-uw built on 5.4-RELEASE so that it wil allow plaintext logins. (All connections will be from localhost so I'm not concerned with SSL) But it doesn't want to behave itself. I've tried building it this way: This belongs more on the ports mailing list, not stable. I don't know why you have this problem, but i would suggest you use dovecot or courier as an imap server instead. Not to beat an off-topic horse, but... When I switched from Courier IMAP to Dovecot, I saw a huge increase in performance. Dovecot uses index files that prevent it from having to continually scan a mailbox for every request. For my largest folders (30,000+ messages), Dovecot was *at least* an order of magnitude faster. -Jonathan -- Jonathan Noack | [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: imap w/cleartext on 5.4-RELEASE
jason wrote: I'm trying to get imap-uw built on 5.4-RELEASE so that it wil allow plaintext logins. (All connections will be from localhost so I'm not concerned with SSL) But it doesn't want to behave itself. I've tried building it this way: This belongs more on the ports mailing list, not stable. I don't know why you have this problem, but i would suggest you use dovecot or courier as an imap server instead. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
imap w/cleartext on 5.4-RELEASE
I'm trying to get imap-uw built on 5.4-RELEASE so that it wil allow plaintext logins. (All connections will be from localhost so I'm not concerned with SSL) But it doesn't want to behave itself. I've tried building it this way: # cd /usr/ports/mail/imap-uw # make -DWITH_SSL_AND_PLAINTEXT and it complains that I'm buildling it with plaintext enabled, as it should: + + Building in PARTIAL compliance with RFC 3501 security + requirements: + Compliant: ++ TLS/SSL encryption is supported + Non-compliant: ++ Unencrypted plaintext passwords are permitted + + In order to rectify this problem, you MUST build with: ++ SSLTYPE=unix.nopwd + but when I install it then telnet there I get: # !telnet telnet 0 143 Trying 0.0.0.0... Connected to 0. Escape character is '^]'. * OK [CAPABILITY IMAP4REV1 LITERAL+ SASL-IR LOGIN-REFERRALS STARTTLS LOGINDISABLED] mail1.jasons.us IMAP4rev1 2004.357 at Tue, 9 May 2006 15:25:26 -0400 (EDT) So somewhere it's still not allowing cleartext log-ins. Any ideas? Alternatively I'd be glad to get squirelmail working with encryption but that doesn't want to work either. Suggestions welcome for either problem. -- -Jason - --- There are no ABSOLUTE STATEMENTS I'm very probably wrong. --- "The difference between genius and stupidity is that genius has its limits." - Albert Einstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R/amd64: PXE boot can't handle .gz mfsroot?
On Tue, 9 May 2006, Bj?rn K?nig wrote:
BK> > ${SUBJ} says almost all. PXEboot leads to
BK> > Can't work out which disk we are booting from.
BK> >
BK> > error.
BK> >
BK> > Ungzipping /boot/mfsroot.gz helps
BK>
BK> Hello Dmitry,
BK>
BK> I can't report any problems regarding this with 6.0-RELEASE. Can you show me
BK>
BK> find /tftproot -type f
pxeboot only
BK> cat /tftpdroot/boot/loader.conf
none
BK> Did you compiled pxeboot without gzip support accidentally?
No, I did mount release ISO via md as NFS root for given machine:
host gwp {
hardware ethernet 00:16:35:***;
filename "pxeboot";
option root-path "192.168.200.1:/pxe/amd64/6.1-R/";
option routers 192.168.200.1;
}
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] ***
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.1-R/amd64: PXE boot can't handle .gz mfsroot?
Dmitry Morozovsky schrieb:
Colleagues,
${SUBJ} says almost all. PXEboot leads to
Can't work out which disk we are booting from.
error.
Ungzipping /boot/mfsroot.gz helps
Hello Dmitry,
I can't report any problems regarding this with 6.0-RELEASE. Can you
show me
find /tftproot -type f
and
cat /tftpdroot/boot/loader.conf
please?
Did you compiled pxeboot without gzip support accidentally?
Regards
Björn
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.1-R/amd64: PXE boot can't handle .gz mfsroot?
Colleagues,
${SUBJ} says almost all. PXEboot leads to
Can't work out which disk we are booting from.
error.
Ungzipping /boot/mfsroot.gz helps
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] ***
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Can't compile without COMPAT_43 on i386
I can compile an amd64 kernel just fine without the option COMPAT_43, but not i386. Why is this? /usr/src/sys/modules/linux/../../i386/linux/linux_sysvec.c:36:2: #error "Unable to compile Linux-emulator due to missing COMPAT_43 option!" mkdep: compile failed I don't want or need the Linux-emulator. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: Thank for your help, the problem is after to select installation default, whitout acpi or safe mode, in all cases the boot loader crashing after the next message: in 6.1 stable module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 Actually, this is from the kernel, not the boot loader. Is the system hung at this point or is there any other information displayed after this gets printed? As this information would help the developers determine whats going wrong on your system. If there is additional information, a backtrace (bt) from the debugger prompt would be useful. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: Thank you for your help. I try to do that, but i get the same problem. now the error is: module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 after that the installation is stopped. I get this same error when I boot either a GENERIC kernel on my installed system, or from the FreeBSD/amd64 6.1-RELEASE CD. The CD does continue into the System Installation. I try to with 6.1 STABLE and get the same problem. When the boot loader comes up, try selecting the option to boot without acpi and see if that will allow the installation to proceed. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
Thank for your help, the problem is after to select installation default, whitout acpi or safe mode, in all cases the boot loader crashing after the next message: in 6.1 stable module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 in 6.0 stable timecounters tick every 1000 msec Linux ELF exec handler install lo0.bpf attached thank you. El Martes, 9 de Mayo de 2006 09:08, Scot Hetzel escribió: > On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: > > No, but i will install 6.1 STABLE > > > > thank you > > > > El Lunes, 8 de Mayo de 2006 20:31, Mike Jakubik escribió: > > > Alejandro Ruiz Robles wrote: > > > > I can't install freebsd 6.0 STABLE amd64 on my notebook: > > > > > > Have you tried 6.1-RC2? > > As Mike has suggested give FreeBSD/AMD64 6.1-RC2 a try. > > If you have a problem with the boot loader crashing after it loads > /boot/loader.conf from the install CD, just power off and on the > system, then when you see the boot loader, repeatedly hit the space > bar, until you see that it is loading /boot/kernel/kernel. After > this, it will then be able to load the system installer, and allow you > to install the system. When the system is installed you'll have no > problem booting the system from the harddrive. > > This is what I had to do on my HP Pavilion dv8xxx (AMD Turion 64 ML-37) > System. > > Scot > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
Thank for your help, the problem is after to select installation default, whitout acpi or safe mode, in all cases the boot loader crashing after the next message: in 6.1 stable module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 in 6.0 stable timecounters tick every 1000 msec Linux ELF exec handler install lo0.bpf attached thank you. El Martes, 9 de Mayo de 2006 09:08, Scot Hetzel escribió: > On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: > > No, but i will install 6.1 STABLE > > > > thank you > > > > El Lunes, 8 de Mayo de 2006 20:31, Mike Jakubik escribió: > > > Alejandro Ruiz Robles wrote: > > > > I can't install freebsd 6.0 STABLE amd64 on my notebook: > > > > > > Have you tried 6.1-RC2? > > As Mike has suggested give FreeBSD/AMD64 6.1-RC2 a try. > > If you have a problem with the boot loader crashing after it loads > /boot/loader.conf from the install CD, just power off and on the > system, then when you see the boot loader, repeatedly hit the space > bar, until you see that it is loading /boot/kernel/kernel. After > this, it will then be able to load the system installer, and allow you > to install the system. When the system is installed you'll have no > problem booting the system from the harddrive. > > This is what I had to do on my HP Pavilion dv8xxx (AMD Turion 64 ML-37) > System. > > Scot > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
Brian Szymanski writes: | kldload amr_linux did the trick for me, thanks! Good to hear. You might want to look at megarc and megamonitor for Linux. Hopefully, LSI updated megamonitor to fix the share memory leak or it will exit in about 1/2 hour on FreeBSD since we don't allow us much shared memory usage as Linux. It leaks on Linux. It just takes longer to use it all up. Doug A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
kldload amr_linux did the trick for me, thanks! Cheers, B > Boris Samorodov writes: > | On Tue, 9 May 2006 12:37:43 -0400 (EDT) Brian Szymanski wrote: > | > PS - mknod c 254 /compat/linux/dev/megadev0 (which is what the device > is > | > under linux) doesn't help :( > | > | I't only my imho, use it with care: > | > | # cd /dev > | # ln -s amr0 megadev0 > > Nope, it needs to show up in devfs. Making a node manually is going > to cause trouble. If there isn't a /dev/megadev0 then you don't > have the amr_linux loaded. You can try to kldload but you might > have to compile it in static. > > Doug A. > > Brian Szymanski Software and Systems Developer Media Matters for America [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
Boris Samorodov writes: | On Tue, 9 May 2006 12:37:43 -0400 (EDT) Brian Szymanski wrote: | > PS - mknod c 254 /compat/linux/dev/megadev0 (which is what the device is | > under linux) doesn't help :( | | I't only my imho, use it with care: | | # cd /dev | # ln -s amr0 megadev0 Nope, it needs to show up in devfs. Making a node manually is going to cause trouble. If there isn't a /dev/megadev0 then you don't have the amr_linux loaded. You can try to kldload but you might have to compile it in static. Doug A. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
Thank you for your help. I try to do that, but i get the same problem. now the error is: module_register_init: MOD_LOAD (arm_linux, 0x806205d0, 0) error 6 after that the installation is stopped. I try to with 6.1 STABLE and get the same problem. El Martes, 9 de Mayo de 2006 09:18, Scot Hetzel escribió: > On 5/9/06, Scot Hetzel <[EMAIL PROTECTED]> wrote: > > On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: > > > No, but i will install 6.1 STABLE > > > > > > thank you > > > > > > El Lunes, 8 de Mayo de 2006 20:31, Mike Jakubik escribió: > > > > Alejandro Ruiz Robles wrote: > > > > > I can't install freebsd 6.0 STABLE amd64 on my notebook: > > > > > > > > Have you tried 6.1-RC2? > > > > As Mike has suggested give FreeBSD/AMD64 6.1-RC2 a try. > > Just noticed that 6.1-RELEASE is available, give that a try. > > Scot > -- > DISCLAIMER: > No electrons were mamed while sending this message. Only slightly bruised. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
On Tue, 9 May 2006 12:37:43 -0400 (EDT) Brian Szymanski wrote: > PS - mknod c 254 /compat/linux/dev/megadev0 (which is what the device is > under linux) doesn't help :( I't only my imho, use it with care: # cd /dev # ln -s amr0 megadev0 > >> On Tue, 9 May 2006 10:15:31 -0400 (EDT) Brian Szymanski wrote: > >> > >>> Oh, duh, it's been so long since I used linux binary emulation that I > >>> forgot all about brandelf... Thanks Michael! > >> > >>> ... But now that the binary is properly branded, I get a different > >>> error: > >>> Error opening terminal: xterm. > >>> I get the same error for xterm-color, cons25, vt220, and everything > >>> else > >>> I've tried... (and I know for a fact that TERM=xterm works on my linux > >>> machines)... Any ideas? > >> > >> Just load > >> http://www.lsilogic.com/cm/License.do?url=/files/support/rsa/utilities/megamgr/ut_linux_mgr_5.20.zip&prodName=MegaRAID%20SATA%20150-4&subType=Miscellaneous > >> Unzipped it, branded and run ./megamgr.bin as root on _console_. I've > >> got "Failed to open driver node /dev/megadev0" (really I don't have > >> one). BTW on xterm it shows the same message. > > > > Oops - I was lacking a linux compat_linux port... Installed one, (fc3), > > and now I have the same problem about not finding megadev0, even tho I > > have an amr... > > > > Thanks for everyone's help so far... Any more ideas? WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone & Internet Service Provider ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
PS - mknod c 254 /compat/linux/dev/megadev0 (which is what the device is under linux) doesn't help :( > >> On Tue, 9 May 2006 10:15:31 -0400 (EDT) Brian Szymanski wrote: >> >>> Oh, duh, it's been so long since I used linux binary emulation that I >>> forgot all about brandelf... Thanks Michael! >> >>> ... But now that the binary is properly branded, I get a different >>> error: >>> Error opening terminal: xterm. >>> I get the same error for xterm-color, cons25, vt220, and everything >>> else >>> I've tried... (and I know for a fact that TERM=xterm works on my linux >>> machines)... Any ideas? >> >> Just load >> http://www.lsilogic.com/cm/License.do?url=/files/support/rsa/utilities/megamgr/ut_linux_mgr_5.20.zip&prodName=MegaRAID%20SATA%20150-4&subType=Miscellaneous >> Unzipped it, branded and run ./megamgr.bin as root on _console_. I've >> got "Failed to open driver node /dev/megadev0" (really I don't have >> one). BTW on xterm it shows the same message. > > Oops - I was lacking a linux compat_linux port... Installed one, (fc3), > and now I have the same problem about not finding megadev0, even tho I > have an amr... > > Thanks for everyone's help so far... Any more ideas? > > Cheers, > Brian > >> >> >> WBR >> -- >> Boris B. Samorodov, Research Engineer >> InPharmTech Co, http://www.ipt.ru >> Telephone & Internet Service Provider >> >> > > > Brian Szymanski > Software and Systems Developer > Media Matters for America > [EMAIL PROTECTED] > aim: xbrianskix > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
> On Tue, 9 May 2006 10:15:31 -0400 (EDT) Brian Szymanski wrote: > >> Oh, duh, it's been so long since I used linux binary emulation that I >> forgot all about brandelf... Thanks Michael! > >> ... But now that the binary is properly branded, I get a different >> error: >> Error opening terminal: xterm. >> I get the same error for xterm-color, cons25, vt220, and everything else >> I've tried... (and I know for a fact that TERM=xterm works on my linux >> machines)... Any ideas? > > Just load > http://www.lsilogic.com/cm/License.do?url=/files/support/rsa/utilities/megamgr/ut_linux_mgr_5.20.zip&prodName=MegaRAID%20SATA%20150-4&subType=Miscellaneous > Unzipped it, branded and run ./megamgr.bin as root on _console_. I've > got "Failed to open driver node /dev/megadev0" (really I don't have > one). BTW on xterm it shows the same message. Oops - I was lacking a linux compat_linux port... Installed one, (fc3), and now I have the same problem about not finding megadev0, even tho I have an amr... Thanks for everyone's help so far... Any more ideas? Cheers, Brian > > > WBR > -- > Boris B. Samorodov, Research Engineer > InPharmTech Co, http://www.ipt.ru > Telephone & Internet Service Provider > > Brian Szymanski Software and Systems Developer Media Matters for America [EMAIL PROTECTED] aim: xbrianskix ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
On Tue, 9 May 2006 10:15:31 -0400 (EDT) Brian Szymanski wrote: > Oh, duh, it's been so long since I used linux binary emulation that I > forgot all about brandelf... Thanks Michael! > ... But now that the binary is properly branded, I get a different error: > Error opening terminal: xterm. > I get the same error for xterm-color, cons25, vt220, and everything else > I've tried... (and I know for a fact that TERM=xterm works on my linux > machines)... Any ideas? Just load http://www.lsilogic.com/cm/License.do?url=/files/support/rsa/utilities/megamgr/ut_linux_mgr_5.20.zip&prodName=MegaRAID%20SATA%20150-4&subType=Miscellaneous Unzipped it, branded and run ./megamgr.bin as root on _console_. I've got "Failed to open driver node /dev/megadev0" (really I don't have one). BTW on xterm it shows the same message. I use FreeBSD 6.1-RC, emulators/linux_base-fc3 and x11/linux-xorg-libs ports. WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone & Internet Service Provider ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
Brian Szymanski wrote: > Oh, duh, it's been so long since I used linux binary emulation that I > forgot all about brandelf... Thanks Michael! > > ... But now that the binary is properly branded, I get a different error: > Error opening terminal: xterm. > I get the same error for xterm-color, cons25, vt220, and everything else > I've tried... (and I know for a fact that TERM=xterm works on my linux > machines)... Any ideas? I suspect its looking for xterm in your /compat/linux emulation environment. I don't know if there's a linux-xterm port available (I didn't see one), but you *might* be able to get away with hardlinking or copying /usr/X11R6/bin/xterm to /compat/linux/usr/X11R6/bin/xterm (assuming you have linux-XFree86-libs or linux-xorg-libs installed). Perhaps someone better versed in X11 and Linux emulation can answer to this. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
On 5/9/06, Scot Hetzel <[EMAIL PROTECTED]> wrote: On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: > No, but i will install 6.1 STABLE > > thank you > > El Lunes, 8 de Mayo de 2006 20:31, Mike Jakubik escribió: > > Alejandro Ruiz Robles wrote: > > > I can't install freebsd 6.0 STABLE amd64 on my notebook: > > > > Have you tried 6.1-RC2? > > As Mike has suggested give FreeBSD/AMD64 6.1-RC2 a try. Just noticed that 6.1-RELEASE is available, give that a try. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
Oh, duh, it's been so long since I used linux binary emulation that I forgot all about brandelf... Thanks Michael! ... But now that the binary is properly branded, I get a different error: Error opening terminal: xterm. I get the same error for xterm-color, cons25, vt220, and everything else I've tried... (and I know for a fact that TERM=xterm works on my linux machines)... Any ideas? Cheers, Brian > Brian Szymanski wrote: >> Hi... >> >> I saw this in the 6.1 release notes and eagerly upgraded: >> "The amr(4) driver now supports ioctl(2) requests necessary for Linux >> LSI MegaRaid tools on FreeBSD's Linux emulation environment." >> >> However, when I pulled over a megamgr.bin binary from a linux machine, >> and >> try to execute it on my freebsd machine, I get: >> [EMAIL PROTECTED] ~/src/megaraid]# ./megamgr.bin >> ELF binary type "0" not known. >> bash: ./megamgr.bin: cannot execute binary file >> >> Has anyone got this working? What did they need? Any help would be >> appreciated, as I'm seriously sick of megarc :) >> >> Thanks in advance! >> > > Since it appears to require Linux emulation, have you tried branding the > binary is a Linux ELF with brandelf(1)? > > > -Proto > > Brian Szymanski Software and Systems Developer Media Matters for America [EMAIL PROTECTED] skype: xbrianskix aim: xbrianskix ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
On 5/9/06, Alejandro Ruiz Robles <[EMAIL PROTECTED]> wrote: No, but i will install 6.1 STABLE thank you El Lunes, 8 de Mayo de 2006 20:31, Mike Jakubik escribió: > Alejandro Ruiz Robles wrote: > > I can't install freebsd 6.0 STABLE amd64 on my notebook: > > Have you tried 6.1-RC2? > As Mike has suggested give FreeBSD/AMD64 6.1-RC2 a try. If you have a problem with the boot loader crashing after it loads /boot/loader.conf from the install CD, just power off and on the system, then when you see the boot loader, repeatedly hit the space bar, until you see that it is loading /boot/kernel/kernel. After this, it will then be able to load the system installer, and allow you to install the system. When the system is installed you'll have no problem booting the system from the harddrive. This is what I had to do on my HP Pavilion dv8xxx (AMD Turion 64 ML-37) System. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: megamgr on 6.1?
Brian Szymanski wrote: > Hi... > > I saw this in the 6.1 release notes and eagerly upgraded: > "The amr(4) driver now supports ioctl(2) requests necessary for Linux > LSI MegaRaid tools on FreeBSD's Linux emulation environment." > > However, when I pulled over a megamgr.bin binary from a linux machine, and > try to execute it on my freebsd machine, I get: > [EMAIL PROTECTED] ~/src/megaraid]# ./megamgr.bin > ELF binary type "0" not known. > bash: ./megamgr.bin: cannot execute binary file > > Has anyone got this working? What did they need? Any help would be > appreciated, as I'm seriously sick of megarc :) > > Thanks in advance! > Since it appears to require Linux emulation, have you tried branding the binary is a Linux ELF with brandelf(1)? -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 6.1 Released
At 11:19 PM 08/05/2006, Scott Long wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It is my great pleasure and privilege to announce the availability of FreeBSD 6.1-RELEASE. This release is the next step in the development of the 6.X branch, delivering several performance improvements, many bugfixes, and a few new features. These include: Congratulations Scott and the RE team! We have a number of 6.1ish boxes (UP and SMP) in production being brutalized with spam and virual analysis and they are working great! ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
megamgr on 6.1?
Hi... I saw this in the 6.1 release notes and eagerly upgraded: "The amr(4) driver now supports ioctl(2) requests necessary for Linux LSI MegaRaid tools on FreeBSD's Linux emulation environment." However, when I pulled over a megamgr.bin binary from a linux machine, and try to execute it on my freebsd machine, I get: [EMAIL PROTECTED] ~/src/megaraid]# ./megamgr.bin ELF binary type "0" not known. bash: ./megamgr.bin: cannot execute binary file Has anyone got this working? What did they need? Any help would be appreciated, as I'm seriously sick of megarc :) Thanks in advance! Relevant bits of dmesg: FreeBSD 6.1-RELEASE #0: Tue May 9 09:01:31 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src-6.1/sys/OZELMO amr0: mem 0xef00-0xef00 irq 16 at device 13.0 on pci0 amr0: delete logical drives supported by controller amr0: Firmware 713N, BIOS G119, 64MB RAM ... amr0: delete logical drives supported by controller amrd0: on amr0 amrd0: 953656MB (1953087488 sectors) RAID 5 (optimal) [EMAIL PROTECTED] ~/src/megaraid]# kldstat Id Refs AddressSize Name 15 0xc040 504e7c kernel 21 0xc4bc2000 1a000linux.ko Brian Szymanski Software and Systems Developer Media Matters for America [EMAIL PROTECTED] aim: xbrianskix ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem Installing Freebsd 6.0 64 bit
No, but i will install 6.1 STABLE thank you El Lunes, 8 de Mayo de 2006 20:31, Mike Jakubik escribió: > Alejandro Ruiz Robles wrote: > > I can't install freebsd 6.0 STABLE amd64 on my notebook: > > Have you tried 6.1-RC2? > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best practices for remote upgrade?
On May 9, 2006, at 12:56 , Hans Lambermont wrote: David Wolfskill wrote: On Mon, May 08, 2006 at 02:29:23PM +0200, Scott Harrison wrote: I have some 4.x servers that I would like to upgrade to 5.x, and perhaps 6.x. However, I do not have any local access to these machines. I can ssh into them only. I would like to know whether it is possible for me to upgrade the machines with only ssh access, and what one should do to go about upgrading them. ... I then have little shell scripts to use "dump | restore" to "clone" the file systems from one slice to the other. ... * Reboot from the "other" slice (the target of the above operation). * Upgrade in place. * Reboot (without changing active slice). I do almost the same; I do not reboot to the other slice to upgrade it, instead I use the current slice to upgrade, and if that fails reboot to the other slice (the backup slice). It's the same idea, with one less reboot. This dual-boot-slice (or disk :) setup also allows for the UFS->UFS2 transition. This sounds nice except that I do not have my disk already partitioned like this. Can I take a 4.7 machine (for example) and live repartition it to be like this? -- ·𐑕𐑒𐑪𐑑 ·𐑣𐑺𐑦𐑕𐑩𐑯 Scott Harrison
Re: [HACKERS] semaphore usage "port based"?
Hi! On Mon, Apr 03, 2006 at 11:56:13PM +0100, Robert Watson wrote: > >>This is why it's disabled by default, and the jail documentation > >>specifically advises of this possibility. Excerpt below. > > > >Ah, I see, glad to see it's accurately documented. > > As it has been for the last five years, I believe since introduction of the > setting to allow System V IPC to be used with documented limitations. > > >Given the rather significant use of shared memory by Postgres it seems to > >me that jail'ing it under FBSD is unlikely to get you the kind of > >isolation between instances that you want (the assumption being that you > >want to avoid the possibility of a user under one jail impacting a user in > >another jail). As such, I'd suggest finding something else if you truely > >need that isolation for Postgres or dropping the jails entirely. > > > >Running the Postgres instances under different uids (as you'd probably > >expect to do anyway if not using the jails) is probably the right > >approach. Doing that and using jails would probably work, just don't > >delude yourself into thinking that you're safe from a malicious user in > >one jail. > > Yes, there seems to be an awful lot of noise being made about the fact that > the system does, in fact, work exactly as documented, and that the > configuration being complained about is one that is specifically documented > as being unsupported and undesirable. > > As commented elsewhere in this thread, currently, there is no > virtualization support for System V IPC in the FreeBSD Jail implementation. > That may change if/when someone implements it. Until it's implemented, it > isn't going to be there, and the system won't behave as though it's there > no matter how much jumping up and down is done. sysvipc has been implemented once, but it has been decided that it adds unnecessary bloat. That's sad. /fjoe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Best practices for remote upgrade?
David Wolfskill wrote: > On Mon, May 08, 2006 at 02:29:23PM +0200, Scott Harrison wrote: >> I have some 4.x servers that I would like to upgrade to 5.x, and >> perhaps 6.x. However, I do not have any local access to these >> machines. I can ssh into them only. I would like to know whether it >> is possible for me to upgrade the machines with only ssh access, and >> what one should do to go about upgrading them. ... > I then have little shell scripts to use "dump | restore" to "clone" the > file systems from one slice to the other. ... > * Reboot from the "other" slice (the target of the above operation). > * Upgrade in place. > * Reboot (without changing active slice). I do almost the same; I do not reboot to the other slice to upgrade it, instead I use the current slice to upgrade, and if that fails reboot to the other slice (the backup slice). It's the same idea, with one less reboot. This dual-boot-slice (or disk :) setup also allows for the UFS->UFS2 transition. regards, Hans Lambermont ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recent 6.1-PRE: burncd: ioctl(CDRIOCFIXATE): Input/output error
Hi! On Wed, Mar 15, 2006 at 04:27:13PM -0500, Scott Robbins wrote: > On Wed, Mar 15, 2006 at 12:51:50PM -0800, David Wolfskill wrote: > > I'm running: > > > > > > I just tried it again, using a different brand of media, and also got: > > > > localhost(6.1-P)[22] sudo burncd -s max -f /dev/acd0 data > > 6.1-BETA4-i386-disc1.iso fixate > > Password: > > next writeable LBA 0 > > writing from file 6.1-BETA4-i386-disc1.iso size 454082 KB > > written this track 454082 KB (100%) total 454082 KB > > fixating CD, please wait.. > > burncd: ioctl(CDRIOCFIXATE): Input/output error > > localhost(6.1-P)[23] > > > > There was a fair amount of time -- around 15 - 20 seconds -- between the > > "fixating CD, please wait.." message and the whine, during which there > > was activity involving the CD drive. > > > > Am I doing something stupid here? > > In my case, the CD burns without problem however, I get that error. > Googling found me a few other people with a similar issue. Have you > tried the CD afterwords to see if it works anyway? > > Out of curiosity, is it a Plextor drive, I think everyone who had a > problem was running into it with Plextors. > > Some people, like myself, only get the annoying error message and > everything is fine, others find that it doesn't work at all. It does not work on many other drives (including mine, I have NEC DVD RW ND-3520A/1.04). I have to fixate manually after the failure. cdrecord (over SCSI emulation) works fine. http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/73559 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/95344 http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/95979 http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/90839 http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/63319 /fjoe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
