cdrtools /devel and wodim broken
Hello. Usually attempting to write DVD-R bombs out, after writing can't fixate DVD+R. Increasing timeout helps with fixating, but following error just destroys media. Any stupid mistake on my part? # cdrecord(wodim) dev=1,0,0 -v -data *.iso Track 01:0 of 2858 MB written.Errno: 5 (Input/output error), write_g1 scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 22.883s timeout 40s write track data: error after 0 bytes wodim: A write error occured. wodim: Please properly read the error message above. Writing time: 32.681s Average write speed 77.7x. Fixating... Fixating time: 22.473s wodim: fifo had 64 puts and 1 gets. wodim: fifo was 0 times empty and 0 times full, min fill was 100%. FreeBSD 8.1-STABLE #0 r213836 amd64 ahci, scbus, da, cd, pass compiled in kernel. best regards, - Jakub Lach -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p29978939.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: cdrtools /devel and wodim broken
Forgot to mention device. cd0 at ahcich1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) Previously it worked. -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p29978949.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: cdrtools /devel and wodim broken
on 16/10/2010 17:26 Jakub Lach said the following: > > Hello. > > Usually attempting to write DVD-R bombs out, after writing can't fixate > DVD+R. > Increasing timeout helps with fixating, but following error just destroys > media. > > Any stupid mistake on my part? And you have hald running? -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: C4B for modern FreeBSD [was: I4B: what happened, which options? [was: Policy for removing working code]]
On Thu, 9 Sep 2010, Bjoern A. Zeeb wrote: Hi, 2) I am (was) still running C4B on amd64 on RELENG_8 with a privately hacked together capi call log, which is a hack without me even thinking about capi (specs) when doing it, but was doing the job for me for 7 and 8. Getting the last C4B compiled for 8/HEAD or amd64 isn't a lot of patching and I can probably provide patches to you, if you want to make it a port. The PRIV constants needed for this in the base system have been shiping for a while: http://svn.freebsd.org/viewvc/base?view=revision&revision=192577 having sent out the patch to the only person who requested it privately, I thought for later reference I should post it here as well: ! Allow the latest Capi4BSD from http://www.nord-com.net/thomas.wintergerst/ ! to compile on amd64 as well as modern FreeBSD versions without suser() ! or I4B support. http://people.freebsd.org/~bz/20101016-01-c4b-amd64-priv.diff I have done some late changed to get the __FreeBSD_version checks as correct as possible and it compiles on my FreeBSD HEAD/amd64 but I haven't tested it more. I used to use it for a simple call log in the past but not more either. If you give it a try, send me feedback! /bz -- Bjoern A. Zeeb Welcome a new stage of life. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: cdrtools /devel and wodim broken
Andriy Gapon wrote: > > on 16/10/2010 17:26 Jakub Lach said the following: >> >> Hello. >> >> Usually attempting to write DVD-R bombs out, after writing can't fixate >> DVD+R. >> Increasing timeout helps with fixating, but following error just destroys >> media. >> >> Any stupid mistake on my part? > > And you have hald running? > > -- > Andriy Gapon > > > No, I don't use hal. Since when it's requirement? -- View this message in context: http://old.nabble.com/cdrtools--devel-and-wodim-broken-tp29978939p29979695.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Freebsd 8.1 + xorg + radeonhd hang
On 9/16/2010 12:20 PM, Eivind E wrote: > On Wed, 15 Sep 2010, Warren Block wrote: > >> On Wed, 15 Sep 2010, Eivind E wrote: >>> (WW) RADEONHD(0): !!! Option HPD is set !!! >>> This shall only be used to work around broken connector tables. >>> Please report your findings to radeo...@opensuse.org >> >> radeon doesn't have this option at all. >>> (II) RADEONHD(0): Output VGA_1 using monitor section Skjerm >> >> Odd. Later on on it looks like it's using DVI-I_1/analog. See my >> xorg.conf for an example of tying monitors to specific outputs in the >> Device section. > > I tried your configuration file so both of these should be fine, > however, I'm not quite sure what's correct for the Monitor-DVI-X > when using the adaptor to vga which came with the card. The monitor > is an old crt one. Not meaning to resurrect a month-old thread but I'm a bit behind on my list mail. I just thought I'd pass long that I had problems in the past with my older Radeon when using a VGA to DVI connector. Using either a normal VGA port, or a DVI cable on the DVI port worked fine. http://lists.freebsd.org/pipermail/freebsd-x11/2007-September/005251.html Jim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: cdrtools /devel and wodim broken
On Sat, 16 Oct 2010, Jakub Lach wrote: Usually attempting to write DVD-R bombs out, after writing can't fixate DVD+R. Increasing timeout helps with fixating, but following error just destroys media. Any stupid mistake on my part? # cdrecord(wodim) dev=1,0,0 -v -data *.iso Isn't wodim a branch of the real cdrecord? I can't find it in ports. Track 01:0 of 2858 MB written.Errno: 5 (Input/output error), write_g1 scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sense Key: 0x [], Segment 0 Sense Code: 0x00 Qual 0x00 (no additional sense information) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 22.883s timeout 40s I've had mixed success with cdrecord (sysutils/cdrtools-devel) over the years. Although growisofs is reputed to be less correct, I can't recall it ever having a problem. Oh, and I don't recall hal causing problems lately. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: cdrtools /devel and wodim broken
on 16/10/2010 20:21 Jakub Lach said the following: > No, I don't use hal. Since when it's requirement? Hm, why did you decide that it is a requirement? I just asked a question, and thanks for the answer. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kpanic on install >32GB of RAM
On Fri, 2010-10-15 at 09:38 -0700, Sean Bruno wrote: > On Fri, 2010-10-15 at 09:30 -0700, Boris Kochergin wrote: > > On 10/15/10 12:27, Jeremy Chadwick wrote: > > > On Fri, Oct 15, 2010 at 09:04:53AM -0700, Sean Bruno wrote: > > >> So, trying to get a massively overpowered HP box up with 7.3 amd64 > > >> version up and running. > > >> > > >> I can't tell at the moment, but it looks like the installer kernel is > > >> having issues with>32GB of RAM in this box. > > >> > > >> Are we using the i386 kernel on amd64 installs? > > > If you booted a FreeBSD image that has "amd64" in the ISO name, then the > > > kernel is actually 64-bit (amd64). The only i386 piece would be the > > > bootloader. > > > > > > There's probably someone here who can help with the issue you describe, > > > as there's occasional posts here and there from people who experience > > > issues/problems when using very large amounts of RAM. > > > > > I've got an amd64 machine with 48 GB of RAM that has run 7, 8, and now > > 9, which leads me to believe that your issue is not solely related to > > the amount of memory. > > > > -Boris > > __ > > Edge case at 64G perhaps? That's the minimum you can get in the HP > DL980 apparently. > > Sean Hrm, no success today setting available RAM to 32G and reducing the number of processors to 8. I've disabled and tweaked pretty much everything available to me here and have tried to boot up the fbsd 8 install media with the same result as using the fbsd 7 media: Repeated and continuous panics on all processors simultaneously after selecting install method from the boot menu. Not sure what to do at this point to get the system up and running. Suggestions? Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kpanic on install >32GB of RAM
On Sat, Oct 16, 2010 at 12:52:00PM -0700, Sean Bruno wrote: > On Fri, 2010-10-15 at 09:38 -0700, Sean Bruno wrote: > > On Fri, 2010-10-15 at 09:30 -0700, Boris Kochergin wrote: > > > On 10/15/10 12:27, Jeremy Chadwick wrote: > > > > On Fri, Oct 15, 2010 at 09:04:53AM -0700, Sean Bruno wrote: > > > >> So, trying to get a massively overpowered HP box up with 7.3 amd64 > > > >> version up and running. > > > >> > > > >> I can't tell at the moment, but it looks like the installer kernel is > > > >> having issues with>32GB of RAM in this box. > > > >> > > > >> Are we using the i386 kernel on amd64 installs? > > > > If you booted a FreeBSD image that has "amd64" in the ISO name, then the > > > > kernel is actually 64-bit (amd64). The only i386 piece would be the > > > > bootloader. > > > > > > > > There's probably someone here who can help with the issue you describe, > > > > as there's occasional posts here and there from people who experience > > > > issues/problems when using very large amounts of RAM. > > > > > > > I've got an amd64 machine with 48 GB of RAM that has run 7, 8, and now > > > 9, which leads me to believe that your issue is not solely related to > > > the amount of memory. > > > > > > -Boris > > > __ > > > > Edge case at 64G perhaps? That's the minimum you can get in the HP > > DL980 apparently. > > > > Sean > > Hrm, no success today setting available RAM to 32G and reducing the > number of processors to 8. > > I've disabled and tweaked pretty much everything available to me here > and have tried to boot up the fbsd 8 install media with the same result > as using the fbsd 7 media: Repeated and continuous panics on all > processors simultaneously after selecting install method from the boot > menu. > > Not sure what to do at this point to get the system up and running. > Suggestions? Can you boot a Linux liveCD installation of some sort for comparison? That would possibly rule out OS vs. hardware/BIOS ordeals. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kpanic on install >32GB of RAM
On Sat, 2010-10-16 at 13:16 -0700, Jeremy Chadwick wrote: > On Sat, Oct 16, 2010 at 12:52:00PM -0700, Sean Bruno wrote: > > On Fri, 2010-10-15 at 09:38 -0700, Sean Bruno wrote: > > > On Fri, 2010-10-15 at 09:30 -0700, Boris Kochergin wrote: > > > > On 10/15/10 12:27, Jeremy Chadwick wrote: > > > > > On Fri, Oct 15, 2010 at 09:04:53AM -0700, Sean Bruno wrote: > > > > >> So, trying to get a massively overpowered HP box up with 7.3 amd64 > > > > >> version up and running. > > > > >> > > > > >> I can't tell at the moment, but it looks like the installer kernel is > > > > >> having issues with>32GB of RAM in this box. > > > > >> > > > > >> Are we using the i386 kernel on amd64 installs? > > > > > If you booted a FreeBSD image that has "amd64" in the ISO name, then > > > > > the > > > > > kernel is actually 64-bit (amd64). The only i386 piece would be the > > > > > bootloader. > > > > > > > > > > There's probably someone here who can help with the issue you > > > > > describe, > > > > > as there's occasional posts here and there from people who experience > > > > > issues/problems when using very large amounts of RAM. > > > > > > > > > I've got an amd64 machine with 48 GB of RAM that has run 7, 8, and now > > > > 9, which leads me to believe that your issue is not solely related to > > > > the amount of memory. > > > > > > > > -Boris > > > > __ > > > > > > Edge case at 64G perhaps? That's the minimum you can get in the HP > > > DL980 apparently. > > > > > > Sean > > > > Hrm, no success today setting available RAM to 32G and reducing the > > number of processors to 8. > > > > I've disabled and tweaked pretty much everything available to me here > > and have tried to boot up the fbsd 8 install media with the same result > > as using the fbsd 7 media: Repeated and continuous panics on all > > processors simultaneously after selecting install method from the boot > > menu. > > > > Not sure what to do at this point to get the system up and running. > > Suggestions? > > Can you boot a Linux liveCD installation of some sort for comparison? > That would possibly rule out OS vs. hardware/BIOS ordeals. > We've successfully installed RHEL 5u4 on it, I'll fire that up and post the boot output shortly. Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: kpanic on install >32GB of RAM
On Sat, Oct 16, 2010 at 12:52:00PM -0700, Sean Bruno wrote: > On Fri, 2010-10-15 at 09:38 -0700, Sean Bruno wrote: > > On Fri, 2010-10-15 at 09:30 -0700, Boris Kochergin wrote: > > > On 10/15/10 12:27, Jeremy Chadwick wrote: > > > > On Fri, Oct 15, 2010 at 09:04:53AM -0700, Sean Bruno wrote: > > > >> So, trying to get a massively overpowered HP box up with 7.3 amd64 > > > >> version up and running. > > > >> > > > >> I can't tell at the moment, but it looks like the installer kernel is > > > >> having issues with>32GB of RAM in this box. > > > >> > > > >> Are we using the i386 kernel on amd64 installs? > > > > If you booted a FreeBSD image that has "amd64" in the ISO name, then the > > > > kernel is actually 64-bit (amd64). The only i386 piece would be the > > > > bootloader. > > > > > > > > There's probably someone here who can help with the issue you describe, > > > > as there's occasional posts here and there from people who experience > > > > issues/problems when using very large amounts of RAM. > > > > > > > I've got an amd64 machine with 48 GB of RAM that has run 7, 8, and now > > > 9, which leads me to believe that your issue is not solely related to > > > the amount of memory. > > > > > > -Boris > > > __ > > > > Edge case at 64G perhaps? That's the minimum you can get in the HP > > DL980 apparently. > > > > Sean > > Hrm, no success today setting available RAM to 32G and reducing the > number of processors to 8. > > I've disabled and tweaked pretty much everything available to me here > and have tried to boot up the fbsd 8 install media with the same result > as using the fbsd 7 media: Repeated and continuous panics on all > processors simultaneously after selecting install method from the boot > menu. > > Not sure what to do at this point to get the system up and running. > Suggestions? I can say it's not the RAM amount since I'm running 8 on: CPU: Intel(R) Xeon(R) CPU L5520 @ 2.27GHz (2261.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a Stepping = 5 Features=0xbfebfbff Features2=0x9ce3bd AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant real memory = 77310459904 (73729 MB) avail memory = 74596175872 (71140 MB) -- Brooks pgpFceR8F886J.pgp Description: PGP signature
