Re: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On Thu, 18-Apr-2013 at 13:53:14 +0200, Alexander Motin wrote: > On 17.04.2013 12:47, Andre Albsmeier wrote: > > On Wed, 17-Apr-2013 at 10:53:54 +0200, Jeremy Chadwick wrote: > >> On Wed, Apr 17, 2013 at 08:26:00AM +0200, Andre Albsmeier wrote: > >>> On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote: > >>>> On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote: > >>>>> I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00) > >>>>> after going from 7.4 to 9.1 when using ATA_CAM. It is attached to > >>>>> a Promise PDC20268 UDMA100 controller. A standard harddisk drive > >>>>> attached to this controller works well. Cables, controller and drive > >>>>> where replaced already. > >>>>> > >>>>> Kernel gives me: > >>>>> > >>>>> atapci1: port > >>>>> 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f > >>>>> mem 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0 > >>>>> ata2: at channel 0 on atapci1 > >>>>> ata3: at channel 1 on atapci1 > >>>>> ... > >>>>> ada0 at ata2 bus 0 scbus2 target 0 lun 0 > >>>>> ada0: ATA-7 device > >>>>> ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) > >>>>> ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C) > >>>>> ... > >>>>> (cd2:ata3:0:0:0): got CAM status 0x50 > >>>>> (cd2:ata3:0:0:0): fatal error, failed to attach to device > >>>>> (cd2:ata3:0:0:0): lost device, 4 refs > >>>>> (cd2:ata3:0:0:0): removing device entry > >>>>> ... > >>>>> > >>>>> Attaching the CDROM drive to the controller that is integrated on > >>>>> the mainboard (Intel PIIX4 UDMA33 controller) does not show this > >>>>> problem (but here I don't have UDMA66). > >>>>> > >>>>> It also works when not using ATA_CAM: > >>>>> > >>>>> ... > >>>>> acd0: DVDR at ata3-master UDMA66 > >>>>> ... > >>>>> > >>>>> So this semes to be a problem with the Promise controller and ATA_CAM. > >>>>> > >>>>> Any ideas? Or should I file PR? > >>>> > >>>> The controller in question is a Promise Ultra100 TX2. > >>> > >>> Right. Tried with an Ultra133, same effect. > >>> > >>>> > >>>> The error message comes from sys/cam/scsi/scsi_cd.c, in function > >>>> cddone(). The logic is a little hard for me to follow (I understand > >>>> about 70% of it). Look at lines 1724 to 1877 for stable/9. > >>>> > >>>> 1. Can you provide full output from a verbose boot when the CD/DVD drive > >>>> is attached to the Promise controller? > >>> > >>> Attached below. I have just filtered out some ahc cruft... > >>> > >>> Later I will try to boot a -current kernel -- just to see > >>> how this behaves... > >>> > >>>> > >>>> 2. What firmware version the card is using? The PDC20268 had many, many > >>>> firmware problems relating to ATAPI devices. > >>> > >>> It is the latest BIOS: 2.20.0.15. > >>> > >>>> > >>>> 3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support > >>>> up to about 22MBytes/second so ATA66 isn't going to get you anything, > >>>> so as a workaround, using the PIIX4 for it would not hurt you. > >>> > >>> Probably. But I already had cdrecord complain when it > >>> came to the funky DMA speed test it is doing. It went > >>> away when using the UDMA66 port. And on the other hand > >>> I sometimes use the PIIX4 port for other stuff and I > >>> do not want to attach the cdrom to the slave port. > >>> > >>>> > >>>> 4. ONLY if this turns out to be a "controller thing": I'm not sure how > >>>> much effort should be spent trying to make this work, as the PDC20268 is > >>>> legacy/deprecated hardware (made/released 13 years ago). > >>> > >>> The whole box is more than 13 years old (good old Asus BX board) ;-) > >>> > >>> But since it worked in 7.4-STABLE
Re: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On 17.04.2013 12:47, Andre Albsmeier wrote:
On Wed, 17-Apr-2013 at 10:53:54 +0200, Jeremy Chadwick wrote:
On Wed, Apr 17, 2013 at 08:26:00AM +0200, Andre Albsmeier wrote:
On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote:
On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote:
I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
a Promise PDC20268 UDMA100 controller. A standard harddisk drive
attached to this controller works well. Cables, controller and drive
where replaced already.
Kernel gives me:
atapci1: port
0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem
0xdf80-0xdf803fff irq 11 at device 12.0 on pci0
ata2: at channel 0 on atapci1
ata3: at channel 1 on atapci1
...
ada0 at ata2 bus 0 scbus2 target 0 lun 0
ada0: ATA-7 device
ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C)
...
(cd2:ata3:0:0:0): got CAM status 0x50
(cd2:ata3:0:0:0): fatal error, failed to attach to device
(cd2:ata3:0:0:0): lost device, 4 refs
(cd2:ata3:0:0:0): removing device entry
...
Attaching the CDROM drive to the controller that is integrated on
the mainboard (Intel PIIX4 UDMA33 controller) does not show this
problem (but here I don't have UDMA66).
It also works when not using ATA_CAM:
...
acd0: DVDR at ata3-master UDMA66
...
So this semes to be a problem with the Promise controller and ATA_CAM.
Any ideas? Or should I file PR?
The controller in question is a Promise Ultra100 TX2.
Right. Tried with an Ultra133, same effect.
The error message comes from sys/cam/scsi/scsi_cd.c, in function
cddone(). The logic is a little hard for me to follow (I understand
about 70% of it). Look at lines 1724 to 1877 for stable/9.
1. Can you provide full output from a verbose boot when the CD/DVD drive
is attached to the Promise controller?
Attached below. I have just filtered out some ahc cruft...
Later I will try to boot a -current kernel -- just to see
how this behaves...
2. What firmware version the card is using? The PDC20268 had many, many
firmware problems relating to ATAPI devices.
It is the latest BIOS: 2.20.0.15.
3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support
up to about 22MBytes/second so ATA66 isn't going to get you anything,
so as a workaround, using the PIIX4 for it would not hurt you.
Probably. But I already had cdrecord complain when it
came to the funky DMA speed test it is doing. It went
away when using the UDMA66 port. And on the other hand
I sometimes use the PIIX4 port for other stuff and I
do not want to attach the cdrom to the slave port.
4. ONLY if this turns out to be a "controller thing": I'm not sure how
much effort should be spent trying to make this work, as the PDC20268 is
legacy/deprecated hardware (made/released 13 years ago).
The whole box is more than 13 years old (good old Asus BX board) ;-)
But since it worked in 7.4-STABLE I feel that this is some kind
of regression. I do not want to waste anyone's resources in fixing
it -- just if someone is curious and/or has an idea how to fix
it...
And here is the dmesg:
{snipping for mail brevity}
Thanks. CC'd ken@ and mav@ for advice on this. Here's the dmesg:
http://lists.freebsd.org/pipermail/freebsd-stable/2013-April/073131.html
Short details:
The device under scrutiny here is cd2 on ata3, which is an ATAPI
IDE-based optical drive. The drive works when either:
a) Connected to a different IDE controller (atapci0), or,
b) When ATA_CAM is removed (i.e. use ata(4) exclusively).
And just as a note: The -current kernel from
https://snapshots.glenbarber.us/Latest/FreeBSD-10.0-CURRENT-i386-20130316-r248381-bootonly.iso
shows the same problem...
Some of Promise controllers are known to have problems with ATAPI DMA.
Have you tried to disable DMA on that channel or device with loader
tunable like like hint.ata.3.mode=PIO4 ?
--
Alexander Motin
___
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: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On Wed, 17-Apr-2013 at 10:53:54 +0200, Jeremy Chadwick wrote:
> On Wed, Apr 17, 2013 at 08:26:00AM +0200, Andre Albsmeier wrote:
> > On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote:
> > > On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote:
> > > > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> > > > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
> > > > a Promise PDC20268 UDMA100 controller. A standard harddisk drive
> > > > attached to this controller works well. Cables, controller and drive
> > > > where replaced already.
> > > >
> > > > Kernel gives me:
> > > >
> > > > atapci1: port
> > > > 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f
> > > > mem 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0
> > > > ata2: at channel 0 on atapci1
> > > > ata3: at channel 1 on atapci1
> > > > ...
> > > > ada0 at ata2 bus 0 scbus2 target 0 lun 0
> > > > ada0: ATA-7 device
> > > > ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
> > > > ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C)
> > > > ...
> > > > (cd2:ata3:0:0:0): got CAM status 0x50
> > > > (cd2:ata3:0:0:0): fatal error, failed to attach to device
> > > > (cd2:ata3:0:0:0): lost device, 4 refs
> > > > (cd2:ata3:0:0:0): removing device entry
> > > > ...
> > > >
> > > > Attaching the CDROM drive to the controller that is integrated on
> > > > the mainboard (Intel PIIX4 UDMA33 controller) does not show this
> > > > problem (but here I don't have UDMA66).
> > > >
> > > > It also works when not using ATA_CAM:
> > > >
> > > > ...
> > > > acd0: DVDR at ata3-master UDMA66
> > > > ...
> > > >
> > > > So this semes to be a problem with the Promise controller and ATA_CAM.
> > > >
> > > > Any ideas? Or should I file PR?
> > >
> > > The controller in question is a Promise Ultra100 TX2.
> >
> > Right. Tried with an Ultra133, same effect.
> >
> > >
> > > The error message comes from sys/cam/scsi/scsi_cd.c, in function
> > > cddone(). The logic is a little hard for me to follow (I understand
> > > about 70% of it). Look at lines 1724 to 1877 for stable/9.
> > >
> > > 1. Can you provide full output from a verbose boot when the CD/DVD drive
> > > is attached to the Promise controller?
> >
> > Attached below. I have just filtered out some ahc cruft...
> >
> > Later I will try to boot a -current kernel -- just to see
> > how this behaves...
> >
> > >
> > > 2. What firmware version the card is using? The PDC20268 had many, many
> > > firmware problems relating to ATAPI devices.
> >
> > It is the latest BIOS: 2.20.0.15.
> >
> > >
> > > 3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support
> > > up to about 22MBytes/second so ATA66 isn't going to get you anything,
> > > so as a workaround, using the PIIX4 for it would not hurt you.
> >
> > Probably. But I already had cdrecord complain when it
> > came to the funky DMA speed test it is doing. It went
> > away when using the UDMA66 port. And on the other hand
> > I sometimes use the PIIX4 port for other stuff and I
> > do not want to attach the cdrom to the slave port.
> >
> > >
> > > 4. ONLY if this turns out to be a "controller thing": I'm not sure how
> > > much effort should be spent trying to make this work, as the PDC20268 is
> > > legacy/deprecated hardware (made/released 13 years ago).
> >
> > The whole box is more than 13 years old (good old Asus BX board) ;-)
> >
> > But since it worked in 7.4-STABLE I feel that this is some kind
> > of regression. I do not want to waste anyone's resources in fixing
> > it -- just if someone is curious and/or has an idea how to fix
> > it...
> >
> > And here is the dmesg:
> >
> > {snipping for mail brevity}
>
> Thanks. CC'd ken@ and mav@ for advice on this. Here's the dmesg:
>
> http://lists.freebsd.org/pipermail/freebsd-stable/2013-April/073131.html
>
> Short details:
>
> The device under scrutiny here is cd2 on ata3, which is an ATAPI
> IDE-based optical drive. The drive works when either:
>
> a) Connected to a different IDE controller (atapci0), or,
> b) When ATA_CAM is removed (i.e. use ata(4) exclusively).
And just as a note: The -current kernel from
https://snapshots.glenbarber.us/Latest/FreeBSD-10.0-CURRENT-i386-20130316-r248381-bootonly.iso
shows the same problem...
-Andre
___
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: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On Wed, 17-Apr-2013 at 10:53:54 +0200, Jeremy Chadwick wrote:
> On Wed, Apr 17, 2013 at 08:26:00AM +0200, Andre Albsmeier wrote:
> > On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote:
> > > On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote:
> > > > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> > > > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
> > > > a Promise PDC20268 UDMA100 controller. A standard harddisk drive
> > > > attached to this controller works well. Cables, controller and drive
> > > > where replaced already.
> > > >
> > > > Kernel gives me:
> > > >
> > > > atapci1: port
> > > > 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f
> > > > mem 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0
> > > > ata2: at channel 0 on atapci1
> > > > ata3: at channel 1 on atapci1
> > > > ...
> > > > ada0 at ata2 bus 0 scbus2 target 0 lun 0
> > > > ada0: ATA-7 device
> > > > ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
> > > > ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C)
> > > > ...
> > > > (cd2:ata3:0:0:0): got CAM status 0x50
> > > > (cd2:ata3:0:0:0): fatal error, failed to attach to device
> > > > (cd2:ata3:0:0:0): lost device, 4 refs
> > > > (cd2:ata3:0:0:0): removing device entry
> > > > ...
> > > >
> > > > Attaching the CDROM drive to the controller that is integrated on
> > > > the mainboard (Intel PIIX4 UDMA33 controller) does not show this
> > > > problem (but here I don't have UDMA66).
> > > >
> > > > It also works when not using ATA_CAM:
> > > >
> > > > ...
> > > > acd0: DVDR at ata3-master UDMA66
> > > > ...
> > > >
> > > > So this semes to be a problem with the Promise controller and ATA_CAM.
> > > >
> > > > Any ideas? Or should I file PR?
> > >
> > > The controller in question is a Promise Ultra100 TX2.
> >
> > Right. Tried with an Ultra133, same effect.
> >
> > >
> > > The error message comes from sys/cam/scsi/scsi_cd.c, in function
> > > cddone(). The logic is a little hard for me to follow (I understand
> > > about 70% of it). Look at lines 1724 to 1877 for stable/9.
> > >
> > > 1. Can you provide full output from a verbose boot when the CD/DVD drive
> > > is attached to the Promise controller?
> >
> > Attached below. I have just filtered out some ahc cruft...
> >
> > Later I will try to boot a -current kernel -- just to see
> > how this behaves...
> >
> > >
> > > 2. What firmware version the card is using? The PDC20268 had many, many
> > > firmware problems relating to ATAPI devices.
> >
> > It is the latest BIOS: 2.20.0.15.
> >
> > >
> > > 3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support
> > > up to about 22MBytes/second so ATA66 isn't going to get you anything,
> > > so as a workaround, using the PIIX4 for it would not hurt you.
> >
> > Probably. But I already had cdrecord complain when it
> > came to the funky DMA speed test it is doing. It went
> > away when using the UDMA66 port. And on the other hand
> > I sometimes use the PIIX4 port for other stuff and I
> > do not want to attach the cdrom to the slave port.
> >
> > >
> > > 4. ONLY if this turns out to be a "controller thing": I'm not sure how
> > > much effort should be spent trying to make this work, as the PDC20268 is
> > > legacy/deprecated hardware (made/released 13 years ago).
> >
> > The whole box is more than 13 years old (good old Asus BX board) ;-)
> >
> > But since it worked in 7.4-STABLE I feel that this is some kind
> > of regression. I do not want to waste anyone's resources in fixing
> > it -- just if someone is curious and/or has an idea how to fix
> > it...
> >
> > And here is the dmesg:
> >
> > {snipping for mail brevity}
>
> Thanks. CC'd ken@ and mav@ for advice on this. Here's the dmesg:
Thanks for trying to help.
>
> http://lists.freebsd.org/pipermail/freebsd-stable/2013-April/073131.html
>
> Short details:
>
> The device under scrutiny here is cd2 on ata3, which is an ATAPI
> IDE-based optical drive. The drive works when either:
>
> a) C
Re: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On Wed, Apr 17, 2013 at 08:26:00AM +0200, Andre Albsmeier wrote:
> On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote:
> > On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote:
> > > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00)
> > > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to
> > > a Promise PDC20268 UDMA100 controller. A standard harddisk drive
> > > attached to this controller works well. Cables, controller and drive
> > > where replaced already.
> > >
> > > Kernel gives me:
> > >
> > > atapci1: port
> > > 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem
> > > 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0
> > > ata2: at channel 0 on atapci1
> > > ata3: at channel 1 on atapci1
> > > ...
> > > ada0 at ata2 bus 0 scbus2 target 0 lun 0
> > > ada0: ATA-7 device
> > > ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes)
> > > ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C)
> > > ...
> > > (cd2:ata3:0:0:0): got CAM status 0x50
> > > (cd2:ata3:0:0:0): fatal error, failed to attach to device
> > > (cd2:ata3:0:0:0): lost device, 4 refs
> > > (cd2:ata3:0:0:0): removing device entry
> > > ...
> > >
> > > Attaching the CDROM drive to the controller that is integrated on
> > > the mainboard (Intel PIIX4 UDMA33 controller) does not show this
> > > problem (but here I don't have UDMA66).
> > >
> > > It also works when not using ATA_CAM:
> > >
> > > ...
> > > acd0: DVDR at ata3-master UDMA66
> > > ...
> > >
> > > So this semes to be a problem with the Promise controller and ATA_CAM.
> > >
> > > Any ideas? Or should I file PR?
> >
> > The controller in question is a Promise Ultra100 TX2.
>
> Right. Tried with an Ultra133, same effect.
>
> >
> > The error message comes from sys/cam/scsi/scsi_cd.c, in function
> > cddone(). The logic is a little hard for me to follow (I understand
> > about 70% of it). Look at lines 1724 to 1877 for stable/9.
> >
> > 1. Can you provide full output from a verbose boot when the CD/DVD drive
> > is attached to the Promise controller?
>
> Attached below. I have just filtered out some ahc cruft...
>
> Later I will try to boot a -current kernel -- just to see
> how this behaves...
>
> >
> > 2. What firmware version the card is using? The PDC20268 had many, many
> > firmware problems relating to ATAPI devices.
>
> It is the latest BIOS: 2.20.0.15.
>
> >
> > 3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support
> > up to about 22MBytes/second so ATA66 isn't going to get you anything,
> > so as a workaround, using the PIIX4 for it would not hurt you.
>
> Probably. But I already had cdrecord complain when it
> came to the funky DMA speed test it is doing. It went
> away when using the UDMA66 port. And on the other hand
> I sometimes use the PIIX4 port for other stuff and I
> do not want to attach the cdrom to the slave port.
>
> >
> > 4. ONLY if this turns out to be a "controller thing": I'm not sure how
> > much effort should be spent trying to make this work, as the PDC20268 is
> > legacy/deprecated hardware (made/released 13 years ago).
>
> The whole box is more than 13 years old (good old Asus BX board) ;-)
>
> But since it worked in 7.4-STABLE I feel that this is some kind
> of regression. I do not want to waste anyone's resources in fixing
> it -- just if someone is curious and/or has an idea how to fix
> it...
>
> And here is the dmesg:
>
> {snipping for mail brevity}
Thanks. CC'd ken@ and mav@ for advice on this. Here's the dmesg:
http://lists.freebsd.org/pipermail/freebsd-stable/2013-April/073131.html
Short details:
The device under scrutiny here is cd2 on ata3, which is an ATAPI
IDE-based optical drive. The drive works when either:
a) Connected to a different IDE controller (atapci0), or,
b) When ATA_CAM is removed (i.e. use ata(4) exclusively).
No idea if atapicam(4) during scenario (b) works or not. :-)
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| 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: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On Tue, 16-Apr-2013 at 21:38:22 +0200, Jeremy Chadwick wrote: > On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote: > > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00) > > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to > > a Promise PDC20268 UDMA100 controller. A standard harddisk drive > > attached to this controller works well. Cables, controller and drive > > where replaced already. > > > > Kernel gives me: > > > > atapci1: port > > 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem > > 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0 > > ata2: at channel 0 on atapci1 > > ata3: at channel 1 on atapci1 > > ... > > ada0 at ata2 bus 0 scbus2 target 0 lun 0 > > ada0: ATA-7 device > > ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) > > ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C) > > ... > > (cd2:ata3:0:0:0): got CAM status 0x50 > > (cd2:ata3:0:0:0): fatal error, failed to attach to device > > (cd2:ata3:0:0:0): lost device, 4 refs > > (cd2:ata3:0:0:0): removing device entry > > ... > > > > Attaching the CDROM drive to the controller that is integrated on > > the mainboard (Intel PIIX4 UDMA33 controller) does not show this > > problem (but here I don't have UDMA66). > > > > It also works when not using ATA_CAM: > > > > ... > > acd0: DVDR at ata3-master UDMA66 > > ... > > > > So this semes to be a problem with the Promise controller and ATA_CAM. > > > > Any ideas? Or should I file PR? > > The controller in question is a Promise Ultra100 TX2. Right. Tried with an Ultra133, same effect. > > The error message comes from sys/cam/scsi/scsi_cd.c, in function > cddone(). The logic is a little hard for me to follow (I understand > about 70% of it). Look at lines 1724 to 1877 for stable/9. > > 1. Can you provide full output from a verbose boot when the CD/DVD drive > is attached to the Promise controller? Attached below. I have just filtered out some ahc cruft... Later I will try to boot a -current kernel -- just to see how this behaves... > > 2. What firmware version the card is using? The PDC20268 had many, many > firmware problems relating to ATAPI devices. It is the latest BIOS: 2.20.0.15. > > 3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support > up to about 22MBytes/second so ATA66 isn't going to get you anything, > so as a workaround, using the PIIX4 for it would not hurt you. Probably. But I already had cdrecord complain when it came to the funky DMA speed test it is doing. It went away when using the UDMA66 port. And on the other hand I sometimes use the PIIX4 port for other stuff and I do not want to attach the cdrom to the slave port. > > 4. ONLY if this turns out to be a "controller thing": I'm not sure how > much effort should be spent trying to make this work, as the PDC20268 is > legacy/deprecated hardware (made/released 13 years ago). The whole box is more than 13 years old (good old Asus BX board) ;-) But since it worked in 7.4-STABLE I feel that this is some kind of regression. I do not want to waste anyone's resources in fixing it -- just if someone is curious and/or has an idea how to fix it... And here is the dmesg: Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-STABLE #6: Wed Apr 17 07:56:57 CEST 2013 r...@server.ofw.tld:/usr/obj/src/src-9/sys/bratfix i386 gcc version 4.2.1 20070831 patched [FreeBSD] Preloaded elf kernel "/boot/kernel/kernel" at 0xc097d000. Calibrating TSC clock ... TSC clock: 1405298309 Hz CPU: Intel(R) Celeron(TM) CPU1400MHz (1405.30-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Family = 0x6 Model = 0xb Stepping = 1 Features=0x383f9ff Instruction TLB: 4 KB pages, 4-way set associative, 32 entries Instruction TLB: 4 MB pages, fully associative, 2 entries Data TLB: 4 KB pages, 4-way set associative, 64 entries 2nd-level cache: 256 KB, 8-way set associative, 32 byte line size 1st-level instruction cache: 16 KB, 4-way set associative, 32 byte line size Data TLB: 4 MB Pages, 4-way set associative, 8 entries 1st-level data cache: 16 KB, 4-way set associative, 32 byte line size real memory = 268435456 (256 MB) Physical memory chunk(s): 0x1000 - 0x0009dfff, 643072 bytes (157 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c26000 - 0x0fb18fff, 250556416 bytes (61171 pages) avail m
Re: Lost CDROM on 9.1 with ATA_CAM on Promise controller
On Tue, Apr 16, 2013 at 07:55:20PM +0200, Andre Albsmeier wrote: > I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00) > after going from 7.4 to 9.1 when using ATA_CAM. It is attached to > a Promise PDC20268 UDMA100 controller. A standard harddisk drive > attached to this controller works well. Cables, controller and drive > where replaced already. > > Kernel gives me: > > atapci1: port > 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem > 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0 > ata2: at channel 0 on atapci1 > ata3: at channel 1 on atapci1 > ... > ada0 at ata2 bus 0 scbus2 target 0 lun 0 > ada0: ATA-7 device > ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) > ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C) > ... > (cd2:ata3:0:0:0): got CAM status 0x50 > (cd2:ata3:0:0:0): fatal error, failed to attach to device > (cd2:ata3:0:0:0): lost device, 4 refs > (cd2:ata3:0:0:0): removing device entry > ... > > Attaching the CDROM drive to the controller that is integrated on > the mainboard (Intel PIIX4 UDMA33 controller) does not show this > problem (but here I don't have UDMA66). > > It also works when not using ATA_CAM: > > ... > acd0: DVDR at ata3-master UDMA66 > ... > > So this semes to be a problem with the Promise controller and ATA_CAM. > > Any ideas? Or should I file PR? The controller in question is a Promise Ultra100 TX2. The error message comes from sys/cam/scsi/scsi_cd.c, in function cddone(). The logic is a little hard for me to follow (I understand about 70% of it). Look at lines 1724 to 1877 for stable/9. 1. Can you provide full output from a verbose boot when the CD/DVD drive is attached to the Promise controller? 2. What firmware version the card is using? The PDC20268 had many, many firmware problems relating to ATAPI devices. 3. I wouldn't worry about ATA66 vs. ATA33; this drive can only support up to about 22MBytes/second so ATA66 isn't going to get you anything, so as a workaround, using the PIIX4 for it would not hurt you. 4. ONLY if this turns out to be a "controller thing": I'm not sure how much effort should be spent trying to make this work, as the PDC20268 is legacy/deprecated hardware (made/released 13 years ago). -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | 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"
Lost CDROM on 9.1 with ATA_CAM on Promise controller
I have lost one of my CDROM drives (HL-DT-STDVD-RAM GH22LP20/2.00) after going from 7.4 to 9.1 when using ATA_CAM. It is attached to a Promise PDC20268 UDMA100 controller. A standard harddisk drive attached to this controller works well. Cables, controller and drive where replaced already. Kernel gives me: atapci1: port 0xb000-0xb007,0xa800-0xa803,0xa400-0xa407,0xa000-0xa003,0x9800-0x980f mem 0xdf80-0xdf803fff irq 11 at device 12.0 on pci0 ata2: at channel 0 on atapci1 ata3: at channel 1 on atapci1 ... ada0 at ata2 bus 0 scbus2 target 0 lun 0 ada0: ATA-7 device ada0: 100.000MB/s transfers (UDMA5, PIO 8192bytes) ada0: 286188MB (586114704 512 byte sectors: 16H 63S/T 16383C) ... (cd2:ata3:0:0:0): got CAM status 0x50 (cd2:ata3:0:0:0): fatal error, failed to attach to device (cd2:ata3:0:0:0): lost device, 4 refs (cd2:ata3:0:0:0): removing device entry ... Attaching the CDROM drive to the controller that is integrated on the mainboard (Intel PIIX4 UDMA33 controller) does not show this problem (but here I don't have UDMA66). It also works when not using ATA_CAM: ... acd0: DVDR at ata3-master UDMA66 ... So this semes to be a problem with the Promise controller and ATA_CAM. Any ideas? Or should I file PR? Thanks, -Andre ___ 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: Reading from CDROM broken on 9.0-RELEASE/sparc64
On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote: > Hello, > > I think that reading from CDROM is actually broken > in 9.0-RELEASE/sparc64. > > On FreeBSD 8.2-RELEASE/sparc64, mounting a physical > CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso > and running sha256 on usr/freebsd-dist/*.txz yields the same > results as listed in usr/freebsd-dist/MANIFEST. > > However, on FreeBSD 9.0-RELEASE/sparc64, mounting the > same CDROM (using /dev/cd0), and running sha256 on the > same usr/freebsd-dist/*.txz files yields completely different results: > > SHA256 (base.txz) = > a96e255a9379ec1a58b756c3e788e34345fd79e35234925df842d700ccb10e1a > SHA256 (doc.txz) = > 54674bb68b111c3465b0beca8893a6b514b80e20dc22f2bbd208b992568261dc > SHA256 (games.txz) = > b9bedddeea549640b4f41a577f4c5f09aa29d0c3d0d4c105bc4fe7d327bf9fcd > SHA256 (kernel.txz) = > 661df36b4a2e87d2aa88ce998b50d48f2a91892fc288452a0282e3c092739046 > SHA256 (ports.txz) = > 315cbfac6f252de5209a3513a846d14650b98e2dcf99c12779ffd1d32acaa287 > SHA256 (src.txz) = > 6b3a4a9536b1ca2618949bb7bb44478266db551ac9f09ccfc92b5469a715f3cf > > This also prevents an installation of 9.0-RELEASE/sparc64 > via bsdinstall from CDROM (bsdinistall says that the data sets > are corrupted). I was only able to get 9.0 on that SunBlade 1500 > by using a regular source upgrade from a running 8.2-RELEASE > system (using usr/freebsd-dist/src.txz from that very same CDROM > that checksummed correctly on 8.2-RELEASE). > > Just to make it clear: the CDROM media is correct and checksums > correctly on 8.2-RELEASE. It doesn't checksum correctly on 9.0-RELEASE > because reading from CDROM media is now (partially) broken. > > Just to make sure the 9.0-RELEASE sha256 program isn't at fault, > I've mounted FreeBSD-9.0-RELEASE-sparc64-disc1.iso via mdconfig > and run sha256 on the *.txz files again: same results as in MANIFEST. > So sha256 on 9.0 itself is okay, it's only the reading from physical > media that corrupts data (and prevents installation from CDROM -- funny > that this passed release engineering and testing...). Submitted as sparc64/164226 Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: Reading from CDROM broken on 9.0-RELEASE/sparc64
On Mon, Jan 16, 2012 at 2:54 PM, C. P. Ghost wrote: > Hello, > > I think that reading from CDROM is actually broken > in 9.0-RELEASE/sparc64. > > On FreeBSD 8.2-RELEASE/sparc64, mounting a physical > CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso > and running sha256 on usr/freebsd-dist/*.txz yields the same > results as listed in usr/freebsd-dist/MANIFEST. > > However, on FreeBSD 9.0-RELEASE/sparc64, mounting the > same CDROM (using /dev/cd0), and running sha256 on the > same usr/freebsd-dist/*.txz files yields completely different results: > > SHA256 (base.txz) = > a96e255a9379ec1a58b756c3e788e34345fd79e35234925df842d700ccb10e1a > SHA256 (doc.txz) = > 54674bb68b111c3465b0beca8893a6b514b80e20dc22f2bbd208b992568261dc > SHA256 (games.txz) = > b9bedddeea549640b4f41a577f4c5f09aa29d0c3d0d4c105bc4fe7d327bf9fcd > SHA256 (kernel.txz) = > 661df36b4a2e87d2aa88ce998b50d48f2a91892fc288452a0282e3c092739046 > SHA256 (ports.txz) = > 315cbfac6f252de5209a3513a846d14650b98e2dcf99c12779ffd1d32acaa287 > SHA256 (src.txz) = > 6b3a4a9536b1ca2618949bb7bb44478266db551ac9f09ccfc92b5469a715f3cf > > This also prevents an installation of 9.0-RELEASE/sparc64 > via bsdinstall from CDROM (bsdinistall says that the data sets > are corrupted). I was only able to get 9.0 on that SunBlade 1500 > by using a regular source upgrade from a running 8.2-RELEASE > system (using usr/freebsd-dist/src.txz from that very same CDROM > that checksummed correctly on 8.2-RELEASE). > > Just to make it clear: the CDROM media is correct and checksums > correctly on 8.2-RELEASE. It doesn't checksum correctly on 9.0-RELEASE > because reading from CDROM media is now (partially) broken. > > Just to make sure the 9.0-RELEASE sha256 program isn't at fault, > I've mounted FreeBSD-9.0-RELEASE-sparc64-disc1.iso via mdconfig > and run sha256 on the *.txz files again: same results as in MANIFEST. > So sha256 on 9.0 itself is okay, it's only the reading from physical > media that corrupts data (and prevents installation from CDROM -- funny > that this passed release engineering and testing...). One more thing: With a 9.0-RELEASE world installed, if I boot the old 8.2-RELEASE kernel (/boot/kernel.old/kernel), mount /dev/acd0 and checksum the files with sha256, everything is okay. If I boot again the new 9.0-RELEASE kernel (/boot/kernel/kernel), mount /dev/cd0 and checksum the files with sha256, I get the wrong results above. Since there's no /dev/acd0 on 9.0-RELEASE, I can't test mounting that on 9 and compare the results with /dev/cd0. But obviously, whatever /dev/cd0 returns to cd9660 seems to be silently corrupted on 9.0; at least on sparc64. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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"
Reading from CDROM broken on 9.0-RELEASE/sparc64
Hello, I think that reading from CDROM is actually broken in 9.0-RELEASE/sparc64. On FreeBSD 8.2-RELEASE/sparc64, mounting a physical CDROM burned with FreeBSD-9.0-RELEASE-sparc64-disc1.iso and running sha256 on usr/freebsd-dist/*.txz yields the same results as listed in usr/freebsd-dist/MANIFEST. However, on FreeBSD 9.0-RELEASE/sparc64, mounting the same CDROM (using /dev/cd0), and running sha256 on the same usr/freebsd-dist/*.txz files yields completely different results: SHA256 (base.txz) = a96e255a9379ec1a58b756c3e788e34345fd79e35234925df842d700ccb10e1a SHA256 (doc.txz) = 54674bb68b111c3465b0beca8893a6b514b80e20dc22f2bbd208b992568261dc SHA256 (games.txz) = b9bedddeea549640b4f41a577f4c5f09aa29d0c3d0d4c105bc4fe7d327bf9fcd SHA256 (kernel.txz) = 661df36b4a2e87d2aa88ce998b50d48f2a91892fc288452a0282e3c092739046 SHA256 (ports.txz) = 315cbfac6f252de5209a3513a846d14650b98e2dcf99c12779ffd1d32acaa287 SHA256 (src.txz) = 6b3a4a9536b1ca2618949bb7bb44478266db551ac9f09ccfc92b5469a715f3cf This also prevents an installation of 9.0-RELEASE/sparc64 via bsdinstall from CDROM (bsdinistall says that the data sets are corrupted). I was only able to get 9.0 on that SunBlade 1500 by using a regular source upgrade from a running 8.2-RELEASE system (using usr/freebsd-dist/src.txz from that very same CDROM that checksummed correctly on 8.2-RELEASE). Just to make it clear: the CDROM media is correct and checksums correctly on 8.2-RELEASE. It doesn't checksum correctly on 9.0-RELEASE because reading from CDROM media is now (partially) broken. Just to make sure the 9.0-RELEASE sha256 program isn't at fault, I've mounted FreeBSD-9.0-RELEASE-sparc64-disc1.iso via mdconfig and run sha256 on the *.txz files again: same results as in MANIFEST. So sha256 on 9.0 itself is okay, it's only the reading from physical media that corrupts data (and prevents installation from CDROM -- funny that this passed release engineering and testing...). Thanks, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: ATA/Cdrom(?) panic
On 16/11/2011 15:45, Joel Dahl wrote: > > Hmm. We're running many FreeBSD 8.2 machines as guests in VMware but have > never encountered the panic described above. Should I be worried? :-) > I've encountered them often enough that I started removing cdrom devices from the VMs. signature.asc Description: OpenPGP digital signature
Re: ATA/Cdrom(?) panic
On 16-11-2011 16:33, Alexander Motin wrote: > On 11/16/11 16:14, Bjoern A. Zeeb wrote: > > On Wed, 16 Nov 2011, Alexander Motin wrote: > > > >> Hi. > >> > >> On 11/16/11 08:43, Bjoern A. Zeeb wrote: > >>> we have seen this or a very similar panic for about 1 year now once in > >>> a while and I think I reported it before; this is FreeBSD as guest on > >>> vmware. Seems it was a double panic this time. Could someone please > >>> see what's going on there?It was on 8.x-STABLE in the past and this > >>> is 8.2-RELEASE-p4. > >> > >> The part of code reporting "completing request directly" is IMHO broken > >> by design. It returns request completion before request will actually be > >> completed by lower levels without any knowledge of what's going on > >> there. There is kind of protection against double request completion, > >> but it looks like not always working. May be because that part of code > >> is not locked and nothing prevents that semaphore timeout and normal > >> request timeout/completion to happen simultaneously. It is surprising to > >> see even two traps same time, not sure what synchronized them so > >> precisely. > >> > >> Simple removing that semaphore timeout is not an option, because it will > >> cause deadlock when this wait happen within taskqueue thread that is > >> used to handle requests completion and abort that wait. Avoid waiting > >> inside taskqueue is also impossible without major rewrite. That's why > >> ATA_CAM drops that code completely. > > > > So the bottom line of what you are saying is: > > 1) it's hard to fix right in 8 > > 2) it's not an issue in 9 anymore at all? > > Right. Hmm. We're running many FreeBSD 8.2 machines as guests in VMware but have never encountered the panic described above. Should I be worried? :-) -- Joel ___ 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: ATA/Cdrom(?) panic
On 11/16/11 16:14, Bjoern A. Zeeb wrote: > On Wed, 16 Nov 2011, Alexander Motin wrote: > >> Hi. >> >> On 11/16/11 08:43, Bjoern A. Zeeb wrote: >>> we have seen this or a very similar panic for about 1 year now once in >>> a while and I think I reported it before; this is FreeBSD as guest on >>> vmware. Seems it was a double panic this time. Could someone please >>> see what's going on there?It was on 8.x-STABLE in the past and this >>> is 8.2-RELEASE-p4. >> >> The part of code reporting "completing request directly" is IMHO broken >> by design. It returns request completion before request will actually be >> completed by lower levels without any knowledge of what's going on >> there. There is kind of protection against double request completion, >> but it looks like not always working. May be because that part of code >> is not locked and nothing prevents that semaphore timeout and normal >> request timeout/completion to happen simultaneously. It is surprising to >> see even two traps same time, not sure what synchronized them so >> precisely. >> >> Simple removing that semaphore timeout is not an option, because it will >> cause deadlock when this wait happen within taskqueue thread that is >> used to handle requests completion and abort that wait. Avoid waiting >> inside taskqueue is also impossible without major rewrite. That's why >> ATA_CAM drops that code completely. > > So the bottom line of what you are saying is: > 1) it's hard to fix right in 8 > 2) it's not an issue in 9 anymore at all? Right. -- Alexander Motin ___ 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: ATA/Cdrom(?) panic
On Wed, 16 Nov 2011, Alexander Motin wrote: Hi. On 11/16/11 08:43, Bjoern A. Zeeb wrote: we have seen this or a very similar panic for about 1 year now once in a while and I think I reported it before; this is FreeBSD as guest on vmware. Seems it was a double panic this time. Could someone please see what's going on there?It was on 8.x-STABLE in the past and this is 8.2-RELEASE-p4. The part of code reporting "completing request directly" is IMHO broken by design. It returns request completion before request will actually be completed by lower levels without any knowledge of what's going on there. There is kind of protection against double request completion, but it looks like not always working. May be because that part of code is not locked and nothing prevents that semaphore timeout and normal request timeout/completion to happen simultaneously. It is surprising to see even two traps same time, not sure what synchronized them so precisely. Simple removing that semaphore timeout is not an option, because it will cause deadlock when this wait happen within taskqueue thread that is used to handle requests completion and abort that wait. Avoid waiting inside taskqueue is also impossible without major rewrite. That's why ATA_CAM drops that code completely. So the bottom line of what you are saying is: 1) it's hard to fix right in 8 2) it's not an issue in 9 anymore at all? -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ___ 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: ATA/Cdrom(?) panic
Hi. On 11/16/11 08:43, Bjoern A. Zeeb wrote: > we have seen this or a very similar panic for about 1 year now once in > a while and I think I reported it before; this is FreeBSD as guest on > vmware. Seems it was a double panic this time. Could someone please > see what's going on there?It was on 8.x-STABLE in the past and this > is 8.2-RELEASE-p4. The part of code reporting "completing request directly" is IMHO broken by design. It returns request completion before request will actually be completed by lower levels without any knowledge of what's going on there. There is kind of protection against double request completion, but it looks like not always working. May be because that part of code is not locked and nothing prevents that semaphore timeout and normal request timeout/completion to happen simultaneously. It is surprising to see even two traps same time, not sure what synchronized them so precisely. Simple removing that semaphore timeout is not an option, because it will cause deadlock when this wait happen within taskqueue thread that is used to handle requests completion and abort that wait. Avoid waiting inside taskqueue is also impossible without major rewrite. That's why ATA_CAM drops that code completely. -- Alexander Motin ___ 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: ATA/Cdrom(?) panic
On 16/11/2011 07:43, Bjoern A. Zeeb wrote: > Hey, > > we have seen this or a very similar panic for about 1 year now once in > a while and I think I reported it before; this is FreeBSD as guest on Yes, IIRC I've also reported it before; it crashes randomly, when the machine is not doing anything with the cdrom. As a workaround, I now remove the cdrom device from vmware instances. > vmware. Seems it was a double panic this time. Could someone please > see what's going on there?It was on 8.x-STABLE in the past and this > is 8.2-RELEASE-p4. > > Thanks > /bz > > acd0: WARNING - READ_TOC taskqueue timeout - completing request directly > > > Fatal trap 12: page fault while in kernel mode > cpuid = 4; apic id = 04 > fault virtual address = 0x1f4 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc08a1e9f > > stack pointer = 0x28:0xe6ad5b9c > Fatal trap 12: page fault while in kernel mode > frame pointer = 0x28:0xe6ad5bb4 > cpuid = 2; > code segment= base 0x0, limit 0xf, type 0x1bapic id = 02 > = DPL 0, pres 1, def32 1, gran 1 > fault virtual address = 0x1f4 > processor eflags= > fault code = supervisor read, page not presentinterrupt > enabled, > instruction pointer = 0x20:0xc08a1e9fresume, > stack pointer = 0x28:0xe8e9e808IOPL = 0 > frame pointer = 0x28:0xe8e9e820 > current process = > code segment= base 0x0, limit 0xf, type 0x1b12 (swi6: > task queue) > = DPL 0, pres 1, def32 1, gran 1 > trap number = 12 > processor eflags= interrupt enabled, > panic: page faultresume, > cpuid = 4IOPL = 0 > current process = > KDB: stack backtrace:25162 (bsnmpd) > > trap number = 12#0 0xc08e0d07 at kdb_backtrace+0x47 > > #1 0xc08b1dc7 at panic+0x117 > #2 0xc0be4b53 at trap_fatal+0x323 > #3 0xc0be4dd0 at trap_pfault+0x270 > #4 0xc0be5315 at trap+0x465 > #5 0xc0bcbecc at calltrap+0x6 > #6 0xc08b0d86 at _sema_post+0x46 > #7 0xc056fa47 at ata_completed+0x727 > #8 0xc08eb97a at taskqueue_run_locked+0xca > #9 0xc08ebc8a at taskqueue_run+0xaa > #10 0xc08ebd53 at taskqueue_swi_run+0x13 > #11 0xc088903b at intr_event_execute_handlers+0x13b > #12 0xc088a75b at ithread_loop+0x6b > #13 0xc0886d51 at fork_exit+0x91 > #14 0xc0bcbf44 at fork_trampoline+0x8 > Uptime: 5d20h1m56s > > > (gdb) l *ata_completed+0x727 > 489 (request->callback)(request); > 490 else > 491 sema_post(&request->done); > 492 > 493 /* only call ata_start if channel is present */ > 494 if (ch) > 495 ata_start(ch->dev); > 496 } > 497 > 498 void > > signature.asc Description: OpenPGP digital signature
ATA/Cdrom(?) panic
Hey, we have seen this or a very similar panic for about 1 year now once in a while and I think I reported it before; this is FreeBSD as guest on vmware. Seems it was a double panic this time. Could someone please see what's going on there?It was on 8.x-STABLE in the past and this is 8.2-RELEASE-p4. Thanks /bz acd0: WARNING - READ_TOC taskqueue timeout - completing request directly Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0x1f4 fault code = supervisor read, page not present instruction pointer = 0x20:0xc08a1e9f stack pointer = 0x28:0xe6ad5b9c Fatal trap 12: page fault while in kernel mode frame pointer = 0x28:0xe6ad5bb4 cpuid = 2; code segment= base 0x0, limit 0xf, type 0x1bapic id = 02 = DPL 0, pres 1, def32 1, gran 1 fault virtual address = 0x1f4 processor eflags= fault code = supervisor read, page not presentinterrupt enabled, instruction pointer = 0x20:0xc08a1e9fresume, stack pointer = 0x28:0xe8e9e808IOPL = 0 frame pointer = 0x28:0xe8e9e820 current process = code segment= base 0x0, limit 0xf, type 0x1b12 (swi6: task queue) = DPL 0, pres 1, def32 1, gran 1 trap number = 12 processor eflags= interrupt enabled, panic: page faultresume, cpuid = 4IOPL = 0 current process = KDB: stack backtrace:25162 (bsnmpd) trap number = 12#0 0xc08e0d07 at kdb_backtrace+0x47 #1 0xc08b1dc7 at panic+0x117 #2 0xc0be4b53 at trap_fatal+0x323 #3 0xc0be4dd0 at trap_pfault+0x270 #4 0xc0be5315 at trap+0x465 #5 0xc0bcbecc at calltrap+0x6 #6 0xc08b0d86 at _sema_post+0x46 #7 0xc056fa47 at ata_completed+0x727 #8 0xc08eb97a at taskqueue_run_locked+0xca #9 0xc08ebc8a at taskqueue_run+0xaa #10 0xc08ebd53 at taskqueue_swi_run+0x13 #11 0xc088903b at intr_event_execute_handlers+0x13b #12 0xc088a75b at ithread_loop+0x6b #13 0xc0886d51 at fork_exit+0x91 #14 0xc0bcbf44 at fork_trampoline+0x8 Uptime: 5d20h1m56s (gdb) l *ata_completed+0x727 489 (request->callback)(request); 490 else 491 sema_post(&request->done); 492 493 /* only call ata_start if channel is present */ 494 if (ch) 495 ata_start(ch->dev); 496 } 497 498 void -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. ___ 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: ahci and user mount of cdrom
i think, usermount worked only with user owned and writable dir-s, example: mkdir ~/cdrom mount_cd9660 /dev/acd0 ~/cdrom On 12/28/09, Johan Hendriks wrote: > Hello all > I am on 8.0-STABLE now, and using the ahci driver. > > All works likei t should, but i can not mount my cdrom anymore as a > regular user. > > i have this in my sysctl.conf > > vfs.usermount=1 > > > > my /etc/devfs.conf looks like this > > #CDROM_BURNER permissions > > permacd00666 > > #permacd10666 > > permcd0 0666 > > #permcd1 0666 > > permcdrom 0666 > > #permcdrom1 0666 > > permpass0 0660 > > permpass1 0660 > > permpass2 0660 > > permpass3 0660 > > permpass4 0660 > > permpass5 0660 > > permpass6 0666 > > permxpt00660 > > > > dmesg list the following > > > > atapci0: port > 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f > mem 0xfe9ffc00-0xfe9f irq 16 at device 0.0 on pci3 > > atapci0: [ITHREAD] > > > > acd0: DVDR at ata2-slave UDMA66 > > > > later on in my dmesg i get the following > > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > (probe0:ata0:0:1:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > > (probe0:ata0:0:1:0): CAM Status: SCSI Status Error > > (probe0:ata0:0:1:0): SCSI Status: Check Condition > > (probe0:ata0:0:1:0): NOT READY asc:3a,1 > > (probe0:ata0:0:1:0): Medium not present - tray closed > > (probe0:ata0:0:1:0): Unretryable error > > > > > > cd0 at ata0 bus 0 scbus8 target 1 lun 0 > > cd0: Removable CD-ROM SCSI-0 device > > cd0: 66.000MB/s transfers > > cd0: cd present [329835 x 2048 byte records] > > > > my cdrom is attached to the pata port on the mainbord. > > > > Regards, > > Johan > > > > > > > > > > > > > ___ > 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" > ___ 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"
ahci and user mount of cdrom
Hello all I am on 8.0-STABLE now, and using the ahci driver. All works likei t should, but i can not mount my cdrom anymore as a regular user. i have this in my sysctl.conf vfs.usermount=1 my /etc/devfs.conf looks like this #CDROM_BURNER permissions permacd00666 #permacd10666 permcd0 0666 #permcd1 0666 permcdrom 0666 #permcdrom1 0666 permpass0 0660 permpass1 0660 permpass2 0660 permpass3 0660 permpass4 0660 permpass5 0660 permpass6 0666 permxpt00660 dmesg list the following atapci0: port 0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f mem 0xfe9ffc00-0xfe9f irq 16 at device 0.0 on pci3 atapci0: [ITHREAD] acd0: DVDR at ata2-slave UDMA66 later on in my dmesg i get the following acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 (probe0:ata0:0:1:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:ata0:0:1:0): CAM Status: SCSI Status Error (probe0:ata0:0:1:0): SCSI Status: Check Condition (probe0:ata0:0:1:0): NOT READY asc:3a,1 (probe0:ata0:0:1:0): Medium not present - tray closed (probe0:ata0:0:1:0): Unretryable error cd0 at ata0 bus 0 scbus8 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: cd present [329835 x 2048 byte records] my cdrom is attached to the pata port on the mainbord. Regards, Johan ___ 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: unable to boot 7.0-RELEASE cdrom on supermicro 5015b-mt
On Wednesday 23 July 2008 01:18:35 Jeremy Chadwick wrote: > On Tue, Jul 22, 2008 at 06:47:34PM +0100, ian j hart wrote: > > On Tuesday 22 July 2008 17:37:24 Jeremy Chadwick wrote: > > > On Tue, Jul 22, 2008 at 05:27:52PM +0100, ian j hart wrote: > > > > Same hardware as my other thread. > > > > http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm > > > > > > > > [using 2Gb RAM and SATA in legacy mode] > > > > > > > > I'd like to focus only on making the CDROM boot complete. > > > > > > > > Summary: hangs just after the CPUs are launched. > > > > > > > > 6.2-RELEASE works okay, no AHCI support > > > > 6.3-RELEASE works okay > > > > 7.0-RELEASE hangs > > > > 7.0-STABLE-200806-SNAPSHOT hangs > > > > 8.0-CURRENT-200806-SNAPSHOT hangs > > > > > > > > I thought I could do a binary search using the current snapshot > > > > boot-only CDs but they only go back to March. Are there any older > > > > ones available? > > > > > > Have you tried disabling ACPI to see if it makes any sort of > > > difference? > > > > Yes, but I'm happy to re-try. > > > > Which method is "best"? Or is it 1 + 2 or 3? > > > > 1) BIOS > > 2) Beastie menu option > > 3) loader prompt set hint > > Item #2 is the easiest. You should really be able to leave the BIOS > settings at their defaults (Factory Defaults) and have this system work > on FreeBSD. > > Items #2 and #3 are the same. The loader menu option for disabling ACPI > simply sets the hint. > > > > Also, AHCI should work just fine on those systems -- I know because I > > > have fairly extensive experience with Supermicro hardware, although > > > what you're using is newer than what I presently have. I don't know > > > why you're setting Compatible/Legacy mode on your controller (you > > > mention doing this in your other thread as well). > > > > Because I don't know what's wrong yet and AHCI support is newer than SATA > > support and this is a newish board? [At least 6.2 doesn't seem to support > > it and it has an AHCI legacy option!] > > > > I'd be happy to swap this over. Slight problem; the drives get > > renumbered, so I'd rather not swap back and forth. > > You *absolutely* should have AHCI enabled. There's a lot of reasons > why, too. I highly recommend avoiding the "SATA Compatible" mode. > > AHCI should work fine on FreeBSD 6.3 as well as 7.0 -- I know, because > we have many Supermicro boards running those versions which do have AHCI > enabled. Please use it, and stick with it. > > Here's added proof that AHCI works fine on 6.3: > > $ dmesg -a | grep -i ahci > atapci1: port > 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem > 0xe400-0xe7ff irq 19 at device 31.2 on pci0 atapci1: AHCI Version > 01.10 controller with 4 ports detected > $ uname -r -s > FreeBSD 6.3-PRERELEASE > > The adX device renumbering is expected. There are workarounds for this, > but I recommend you simply enable AHCI. Do not keep toggling it on/off. > > > > Below is what we use on our systems; factory defaults, then make the > > > following changes. (The G-LAN1 OPROM option you can do whatever you > > > want with -- it's specific to our environment). > > > > > > * Main > > > * Date > > > --> Set to GMT, not local time!!! > > > * Serial ATA > > > --> SATA Controller Mode --> Enhanced > > > --> SATA AHCI --> Enabled > > > > > > * Advanced > > > * Boot Features > > > --> Quiet Mode --> Disabled > > > --> Enable Multimedia Timer --> Enabled > > > * PCI Configuration > > > --> Onboard G-LAN1 OPROM --> Disabled > > > --> Large Disk Access Mode --> Other > > > * Advanced Processor Options > > > --> Intel(R) Virtualization Technology --> Enabled > > > --> C1 Enhanced Mode --> Enabled > > > > I've got as close as I can to this. > > > > This board also has an AHCI legacy option [disabled] which hides ports 5 > > and 6. I also disabled quickboot and POST errors. I assume multimedia > > timer is the same as HPET. Doesn't seem to be any disk translation > > option. I took the fans off 'flat out&
Re: unable to boot 7.0-RELEASE cdrom on supermicro 5015b-mt
On Wednesday 23 July 2008 01:18:35 Jeremy Chadwick wrote: > On Tue, Jul 22, 2008 at 06:47:34PM +0100, ian j hart wrote: > > On Tuesday 22 July 2008 17:37:24 Jeremy Chadwick wrote: > > > On Tue, Jul 22, 2008 at 05:27:52PM +0100, ian j hart wrote: > > > > Same hardware as my other thread. > > > > http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm > > > > > > > > [using 2Gb RAM and SATA in legacy mode] > > > > > > > > I'd like to focus only on making the CDROM boot complete. > > > > > > > > Summary: hangs just after the CPUs are launched. > > > > > > > > 6.2-RELEASE works okay, no AHCI support > > > > 6.3-RELEASE works okay > > > > 7.0-RELEASE hangs > > > > 7.0-STABLE-200806-SNAPSHOT hangs > > > > 8.0-CURRENT-200806-SNAPSHOT hangs > > > > > > > > I thought I could do a binary search using the current snapshot > > > > boot-only CDs but they only go back to March. Are there any older > > > > ones available? > > > > > > Have you tried disabling ACPI to see if it makes any sort of > > > difference? > > > > Yes, but I'm happy to re-try. > > > > Which method is "best"? Or is it 1 + 2 or 3? > > > > 1) BIOS > > 2) Beastie menu option > > 3) loader prompt set hint > > Item #2 is the easiest. You should really be able to leave the BIOS > settings at their defaults (Factory Defaults) and have this system work > on FreeBSD. You would think so, although I usually try to buy only "obsolete" hardware to give the drivers a chance to mature. That saves money too :) > > Items #2 and #3 are the same. The loader menu option for disabling ACPI > simply sets the hint. Okay, that's clearer now. I was probably confusing this with APIC. Anyway, result is. No change. FWIW without ACPI the boot dies at trying to mount md0. No drives appear to be probed (I'd need to double check that). > > > > Also, AHCI should work just fine on those systems -- I know because I > > > have fairly extensive experience with Supermicro hardware, although > > > what you're using is newer than what I presently have. I don't know > > > why you're setting Compatible/Legacy mode on your controller (you > > > mention doing this in your other thread as well). > > > > Because I don't know what's wrong yet and AHCI support is newer than SATA > > support and this is a newish board? [At least 6.2 doesn't seem to support > > it and it has an AHCI legacy option!] > > > > I'd be happy to swap this over. Slight problem; the drives get > > renumbered, so I'd rather not swap back and forth. > > You *absolutely* should have AHCI enabled. There's a lot of reasons > why, too. I highly recommend avoiding the "SATA Compatible" mode. > > AHCI should work fine on FreeBSD 6.3 as well as 7.0 -- I know, because > we have many Supermicro boards running those versions which do have AHCI > enabled. Please use it, and stick with it. Yes, it does work on 6.3. This thread is tangential to the problem I'm trying to fix. I'm experienced enough to know that noone is going to fix the kldload issue on 6.3. If I can get to 7.0-whatever there's at least some chance someone will look at it. My initial thought was to regression test the CDs. So I tried every one that I had lying around. This included 6.1 and 6.2, neither of which appear to have AHCI support, hence the messing about with the BIOS. [I've now tested 6.0 as well. The CDROM has some issue which results in danger will robinson. Presumably fixed in later versions.] Noone has yet suggested a source for 7.0-CURRENT boot CDROMs so I'm a bit stuck at the moment. > > Here's added proof that AHCI works fine on 6.3: > > $ dmesg -a | grep -i ahci > atapci1: port > 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem > 0xe400-0xe7ff irq 19 at device 31.2 on pci0 atapci1: AHCI Version > 01.10 controller with 4 ports detected > $ uname -r -s > FreeBSD 6.3-PRERELEASE > > The adX device renumbering is expected. There are workarounds for this, > but I recommend you simply enable AHCI. Do not keep toggling it on/off. > > > > Below is what we use on our systems; factory defaults, then make the > > > following changes. (The G-LAN1 OPROM option you can do whatever you > > > want with -- it's specific to our environment). > > > > > > * Main > > > * Date > > > --> Set to GMT, not loc
Re: unable to boot 7.0-RELEASE cdrom on supermicro 5015b-mt
On Tue, Jul 22, 2008 at 06:47:34PM +0100, ian j hart wrote: > On Tuesday 22 July 2008 17:37:24 Jeremy Chadwick wrote: > > On Tue, Jul 22, 2008 at 05:27:52PM +0100, ian j hart wrote: > > > Same hardware as my other thread. > > > http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm > > > > > > [using 2Gb RAM and SATA in legacy mode] > > > > > > I'd like to focus only on making the CDROM boot complete. > > > > > > Summary: hangs just after the CPUs are launched. > > > > > > 6.2-RELEASE works okay, no AHCI support > > > 6.3-RELEASE works okay > > > 7.0-RELEASE hangs > > > 7.0-STABLE-200806-SNAPSHOThangs > > > 8.0-CURRENT-200806-SNAPSHOT hangs > > > > > > I thought I could do a binary search using the current snapshot boot-only > > > CDs but they only go back to March. Are there any older ones available? > > > > Have you tried disabling ACPI to see if it makes any sort of difference? > > Yes, but I'm happy to re-try. > > Which method is "best"? Or is it 1 + 2 or 3? > > 1) BIOS > 2) Beastie menu option > 3) loader prompt set hint Item #2 is the easiest. You should really be able to leave the BIOS settings at their defaults (Factory Defaults) and have this system work on FreeBSD. Items #2 and #3 are the same. The loader menu option for disabling ACPI simply sets the hint. > > Also, AHCI should work just fine on those systems -- I know because I > > have fairly extensive experience with Supermicro hardware, although what > > you're using is newer than what I presently have. I don't know why > > you're setting Compatible/Legacy mode on your controller (you mention > > doing this in your other thread as well). > > Because I don't know what's wrong yet and AHCI support is newer than SATA > support and this is a newish board? [At least 6.2 doesn't seem to support it > and it has an AHCI legacy option!] > > I'd be happy to swap this over. Slight problem; the drives get renumbered, so > I'd rather not swap back and forth. You *absolutely* should have AHCI enabled. There's a lot of reasons why, too. I highly recommend avoiding the "SATA Compatible" mode. AHCI should work fine on FreeBSD 6.3 as well as 7.0 -- I know, because we have many Supermicro boards running those versions which do have AHCI enabled. Please use it, and stick with it. Here's added proof that AHCI works fine on 6.3: $ dmesg -a | grep -i ahci atapci1: port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xe400-0xe7ff irq 19 at device 31.2 on pci0 atapci1: AHCI Version 01.10 controller with 4 ports detected $ uname -r -s FreeBSD 6.3-PRERELEASE The adX device renumbering is expected. There are workarounds for this, but I recommend you simply enable AHCI. Do not keep toggling it on/off. > > Below is what we use on our systems; factory defaults, then make the > > following changes. (The G-LAN1 OPROM option you can do whatever you > > want with -- it's specific to our environment). > > > > * Main > > * Date > > --> Set to GMT, not local time!!! > > * Serial ATA > > --> SATA Controller Mode --> Enhanced > > --> SATA AHCI --> Enabled > > > > * Advanced > > * Boot Features > > --> Quiet Mode --> Disabled > > --> Enable Multimedia Timer --> Enabled > > * PCI Configuration > > --> Onboard G-LAN1 OPROM --> Disabled > > --> Large Disk Access Mode --> Other > > * Advanced Processor Options > > --> Intel(R) Virtualization Technology --> Enabled > > --> C1 Enhanced Mode --> Enabled > > I've got as close as I can to this. > > This board also has an AHCI legacy option [disabled] which hides ports 5 and > 6. I also disabled quickboot and POST errors. I assume multimedia timer is > the same as HPET. Doesn't seem to be any disk translation option. I took the > fans off 'flat out'. Okay, I've had a chance to review the board manual that comes with the X7SBi. You should set the following: Serial ATA: Enabled Native Mode Operation: Serial ATA SATA AHCI: Enabled SATA AHCI Legacy: Disabled The name "SATA AHCI Legacy" a horrible name for what it does. The ICH9 itself has support for 6 SATA ports, but (if I remember correctly, based on reading some Intel design documents) there are extra registers you have to tweak to get those ports to work, and the OS has to be fully aware of how to do that. The
Re: unable to boot 7.0-RELEASE cdrom on supermicro 5015b-mt
On Tuesday 22 July 2008 17:37:24 Jeremy Chadwick wrote: > On Tue, Jul 22, 2008 at 05:27:52PM +0100, ian j hart wrote: > > Same hardware as my other thread. > > http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm > > > > [using 2Gb RAM and SATA in legacy mode] > > > > I'd like to focus only on making the CDROM boot complete. > > > > Summary: hangs just after the CPUs are launched. > > > > 6.2-RELEASE works okay, no AHCI support > > 6.3-RELEASE works okay > > 7.0-RELEASE hangs > > 7.0-STABLE-200806-SNAPSHOT hangs > > 8.0-CURRENT-200806-SNAPSHOT hangs > > > > I thought I could do a binary search using the current snapshot boot-only > > CDs but they only go back to March. Are there any older ones available? > > Have you tried disabling ACPI to see if it makes any sort of difference? Yes, but I'm happy to re-try. Which method is "best"? Or is it 1 + 2 or 3? 1) BIOS 2) Beastie menu option 3) loader prompt set hint > > Also, AHCI should work just fine on those systems -- I know because I > have fairly extensive experience with Supermicro hardware, although what > you're using is newer than what I presently have. I don't know why > you're setting Compatible/Legacy mode on your controller (you mention > doing this in your other thread as well). Because I don't know what's wrong yet and AHCI support is newer than SATA support and this is a newish board? [At least 6.2 doesn't seem to support it and it has an AHCI legacy option!] I'd be happy to swap this over. Slight problem; the drives get renumbered, so I'd rather not swap back and forth. > > Below is what we use on our systems; factory defaults, then make the > following changes. (The G-LAN1 OPROM option you can do whatever you > want with -- it's specific to our environment). > > * Main > * Date > --> Set to GMT, not local time!!! > * Serial ATA > --> SATA Controller Mode --> Enhanced > --> SATA AHCI --> Enabled > > * Advanced > * Boot Features > --> Quiet Mode --> Disabled > --> Enable Multimedia Timer --> Enabled > * PCI Configuration > --> Onboard G-LAN1 OPROM --> Disabled > --> Large Disk Access Mode --> Other > * Advanced Processor Options > --> Intel(R) Virtualization Technology --> Enabled > --> C1 Enhanced Mode --> Enabled I've got as close as I can to this. This board also has an AHCI legacy option [disabled] which hides ports 5 and 6. I also disabled quickboot and POST errors. I assume multimedia timer is the same as HPET. Doesn't seem to be any disk translation option. I took the fans off 'flat out'. Thanks for your help. -- ian j hart ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unable to boot 7.0-RELEASE cdrom on supermicro 5015b-mt
On Tue, Jul 22, 2008 at 05:27:52PM +0100, ian j hart wrote: > Same hardware as my other thread. > http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm > > [using 2Gb RAM and SATA in legacy mode] > > I'd like to focus only on making the CDROM boot complete. > > Summary: hangs just after the CPUs are launched. > > 6.2-RELEASE works okay, no AHCI support > 6.3-RELEASE works okay > 7.0-RELEASE hangs > 7.0-STABLE-200806-SNAPSHOThangs > 8.0-CURRENT-200806-SNAPSHOT hangs > > I thought I could do a binary search using the current snapshot boot-only CDs > but they only go back to March. Are there any older ones available? Have you tried disabling ACPI to see if it makes any sort of difference? Also, AHCI should work just fine on those systems -- I know because I have fairly extensive experience with Supermicro hardware, although what you're using is newer than what I presently have. I don't know why you're setting Compatible/Legacy mode on your controller (you mention doing this in your other thread as well). Below is what we use on our systems; factory defaults, then make the following changes. (The G-LAN1 OPROM option you can do whatever you want with -- it's specific to our environment). * Main * Date --> Set to GMT, not local time!!! * Serial ATA --> SATA Controller Mode --> Enhanced --> SATA AHCI --> Enabled * Advanced * Boot Features --> Quiet Mode --> Disabled --> Enable Multimedia Timer --> Enabled * PCI Configuration --> Onboard G-LAN1 OPROM --> Disabled --> Large Disk Access Mode --> Other * Advanced Processor Options --> Intel(R) Virtualization Technology --> Enabled --> C1 Enhanced Mode --> Enabled -- | Jeremy Chadwickjdc at 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 "[EMAIL PROTECTED]"
unable to boot 7.0-RELEASE cdrom on supermicro 5015b-mt
Same hardware as my other thread. http://www.supermicro.com/products/system/1U/5015/SYS-5015B-MT.cfm [using 2Gb RAM and SATA in legacy mode] I'd like to focus only on making the CDROM boot complete. Summary: hangs just after the CPUs are launched. 6.2-RELEASE works okay, no AHCI support 6.3-RELEASE works okay 7.0-RELEASE hangs 7.0-STABLE-200806-SNAPSHOT hangs 8.0-CURRENT-200806-SNAPSHOT hangs I thought I could do a binary search using the current snapshot boot-only CDs but they only go back to March. Are there any older ones available? Thanks -- ian j hart ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On Fri, 1 Jun 2007, Daniel O'Connor wrote: > The other approach would be to just splat an install CD onto a flash > disk, eg.. > > fdisk -BI /dev/da0 > bsdlabel -w -B /dev/da0s1 > newfs -b 4096 -f 512 -i 8192 -O1 -U /dev/da0s1 > mount /dev/da0s1a /mnt > cd /mnt > tar zxf /dev/acd0 > umount /mnt > > ... actually that won't work because sysinstall doesn't know how to > mount UFS partitions to read dist files :( > > I did look at adding that when I did the patch for FAT partitions but > it's more complex (I wasn't sure of the canonical way to find them.. > Easiest would be to look in /dev I guess) As part of this I wrote a patch that teaches sysinstall how to load install.cfg from a CDROM or DOS partition (eg USB stick). I just submitted a PR but haven't got a number yet, here is the patch.. http://www.gsoft.com.au/~doconnor/sysinstall-cfg-menu.diff Currently I still use DVD for the actual install.. I have booted a sysinstall (I extracted it from mfsroot.gz into /sbin and did 'set init_path=/sbin/sysinstall in the loader), however I haven't fully tested it as I ran out of time. The problem is that unless you boot sysinstall as init it goes into "maintenance" mode and will not install stuff properly - by design. If anyone is interested in hacking on this sort of stuff feel free to get it touch with me :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: Unable to install FreeBSD from external USB cdrom
On Friday 01 June 2007 04:58, Vivek Khera wrote: > On May 31, 2007, at 1:49 AM, Daniel O'Connor wrote: > > Thanks so much, now I can have an automated install on a USB stick > > :) > > please, please, please share the recipes to make this. I would love > to omit CD rom drives on my future systems as the only thing i ever > use them for is install. > > also, can you run "fixit" mode from your USB stick, too? I haven't actually done it yet, however I was thinking of making a basic FreeSBIE disk but split it into a UFS and a DOS partition. I'd put the dist files on the FAT partition as well as a tar ball I splat over the disk after install (that contains all the packages etc.. it is much faster than pkg_add which is what I used to use, it is also more easily tweaked). The FAT partition would also have an install.cfg which sysinstall could read (I have sysinstall patches for this). The reason for using FAT to store the dist files etc is that it would allow people to easily tweak the config and the like (useful in our situation probably less so for you) One thing I'm not sure about is how to run sysinstall after boot. A normal install CD uses it as init but I don't think that will work very well here since FreeSBIE works differently. The other approach would be to just splat an install CD onto a flash disk, eg.. fdisk -BI /dev/da0 bsdlabel -w -B /dev/da0s1 newfs -b 4096 -f 512 -i 8192 -O1 -U /dev/da0s1 mount /dev/da0s1a /mnt cd /mnt tar zxf /dev/acd0 umount /mnt ... actually that won't work because sysinstall doesn't know how to mount UFS partitions to read dist files :( I did look at adding that when I did the patch for FAT partitions but it's more complex (I wasn't sure of the canonical way to find them.. Easiest would be to look in /dev I guess) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp3NxvlLcSIG.pgp Description: PGP signature
Re: Unable to install FreeBSD from external USB cdrom
On May 31, 2007, at 1:49 AM, Daniel O'Connor wrote: Thanks so much, now I can have an automated install on a USB stick :) please, please, please share the recipes to make this. I would love to omit CD rom drives on my future systems as the only thing i ever use them for is install. also, can you run "fixit" mode from your USB stick, too? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On Thursday 31 May 2007 09:39, Adriaan wrote: > "Because other OS's run the BIOS in real mode, and we run it in vm86 > mode and we don't emulate enough instructions in vm86 mode for the > Compaq/HP BIOS." > > In another post > http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/0287 >73.html he refers to a patch at > http://people.freebsd.org/~jhb/patches/btx_crx.patch Ah interesting, there was another patch earlier in this thread which is what I was testing. The patch does work, I hadn't installed the resulting code properly. I am not sure both patches address the same problem though. I added John to the CC list, hope he doesn't mind! It would be nice if these patches were committed before 7.0 too :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpFUCDFT7Ro1.pgp Description: PGP signature
Re: Unable to install FreeBSD from external USB cdrom
On Thursday 31 May 2007 12:33, Daniel O'Connor wrote: > On Wednesday 30 May 2007 22:52, Kostik Belousov wrote: > > > - > > > int=000d ... > > > ... > > > BTX halted > > > > You boot from the hard drive, right ? Then, boot2 shall be changed > > too, since it uses btx. You should apply the patch, build the > > world, then install _both_ new boot blocks using bsdlabel, and > > loader. > > Ahh I see, my bad! I did as you suggest and it works! Thanks so much, now I can have an automated install on a USB stick :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpiyRnzSv1Qm.pgp Description: PGP signature
Re: Unable to install FreeBSD from external USB cdrom
On Wednesday 30 May 2007 22:52, Kostik Belousov wrote: > > > > - > > int=000d ... > > ... > > BTX halted > > You boot from the hard drive, right ? Then, boot2 shall be changed > too, since it uses btx. You should apply the patch, build the world, > then install _both_ new boot blocks using bsdlabel, and loader. Ahh I see, my bad! -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpsAsQd2css6.pgp Description: PGP signature
Re: Unable to install FreeBSD from external USB cdrom
On 5/30/07, Daniel O'Connor <[EMAIL PROTECTED]> wrote: int=000d ... ... BTX halted According to John Baldwin in http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028774.html : "Because other OS's run the BIOS in real mode, and we run it in vm86 mode and we don't emulate enough instructions in vm86 mode for the Compaq/HP BIOS." In another post http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028773.html he refers to a patch at http://people.freebsd.org/~jhb/patches/btx_crx.patch =Adriaan= ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On Wednesday 30 May 2007 22:08, Kostik Belousov wrote: > > The second one is more accurate as I didn't copy it from a blurry > > photo :) > > Could you, please, show the complete output from the boot, including > btx banner ? That's it.. With my i965 system I don't appear to be able to get it to boot from USB without trying the RAID array as I have to press F5 to get it to boot from USB (even if I pick USB-HDD in the BIOS boot menu) So I press F5 and then it prints what I wrote.. F1DOS F2FreeBSD F5Drive 1 Default: F2 (I Press F5) - int=000d ... ... BTX halted -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp5Q4sHeXks2.pgp Description: PGP signature
Re: Unable to install FreeBSD from external USB cdrom
> Alas I still get a BTX halted after replacing loader with one from > that URL :( > int=000d err= efl=00030002 eip=2aca > eax=0900 ebx=55aa ecx= edx=0180 > esi= edi= ebp=03f0 esp=03da > cs=f000 ds=9e02 es=1400fs= gs= ss=9e02 > cs:eip=2e 0f 01 16 1c 2c 0f 20-c0 0c 01 0f 22 c0 b8 28 >00 8e d8 0f 20 c0 24 fe-0f 22 c0 eb 00 66 58 c3 > ss:esp=02 9e 00 00 20 22 01 41-02 9e 24 72 0f 08 00 00 >46 02 80 01 3a 07 10 00-01 00 00 00 00 14 00 00 > BTX halted > > (ds might be 9e82, not sure, shot is blury..) That was a Supermicro P8SCT, this is a Gigabyte GA-965P-PS3.. int=000d err= efl=00030002 eip=42b7 eax=0900 ebx=55aa ecx= edx=0180 esi= edi= ebp=03f0 esp=03d8 cs=f000 ds=9e02 es=1400fs= gs= ss=9e02 cs:eip=2e 0f 01 16 d8 44 0f 20-c0 0c 01 0f 22 c0 b8 20 00 8e d8 0f 20 c0 24 fe-0f 22 c0 eb 00 66 58 c3 ss:esp=02 9e 00 00 77 3a 01 41-00 14 02 9e 06 9e 0f 08 BTX halted The second one is more accurate as I didn't copy it from a blurry photo :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpGwp4ghBrTt.pgp Description: PGP signature
Re: Unable to install FreeBSD from external USB cdrom
On Monday 28 May 2007 13:35, Daniel O'Connor wrote: > > Yes, there is also a loader/pxeboot in the same directory. > > As kib@ told me, do not install this loader on your disk > > which may destroy your data. > > I see the binaries, I was thinking of trying one with a USB flash > boot disk, I'll unplug my actual disks for safety :) Alas I still get a BTX halted after replacing loader with one from that URL :( int=000d err= efl=00030002 eip=2aca eax=0900 ebx=55aa ecx= edx=0180 esi= edi= ebp=03f0 esp=03da cs=f000 ds=9e02 es=1400fs= gs= ss=9e02 cs:eip=2e 0f 01 16 1c 2c 0f 20-c0 0c 01 0f 22 c0 b8 28 00 8e d8 0f 20 c0 24 fe-0f 22 c0 eb 00 66 58 c3 ss:esp=02 9e 00 00 20 22 01 41-02 9e 24 72 0f 08 00 00 46 02 80 01 3a 07 10 00-01 00 00 00 00 14 00 00 BTX halted (ds might be 9e82, not sure, shot is blury..) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpZx6qfppQfS.pgp Description: PGP signature
Re: Unable to install FreeBSD from external USB cdrom
Rong-en Fan wrote: On 5/28/07, Daniel O'Connor <[EMAIL PROTECTED]> wrote: Daniel O'Connor wrote: >> kib@ has real mode BTX code which appears to work with affected >> systems of mine, however, the code has not yet made it into CVS. I >> spliced it into a 6.2 miniboot ISO and it worked. > > Ooh ahh, please sir, can I have some more^Wit? :) I did some googling.. Is this the patch? http://people.freebsd.org/~kib/realbtx/realbtx.2.patch (Going to try it today anyway :) [I'm CC'ing [EMAIL PROTECTED] Yes, there is also a loader/pxeboot in the same directory. As kib@ told me, do not install this loader on your disk which may destroy your data. I see the binaries, I was thinking of trying one with a USB flash boot disk, I'll unplug my actual disks for safety :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On 5/28/07, Daniel O'Connor <[EMAIL PROTECTED]> wrote: Daniel O'Connor wrote: >> kib@ has real mode BTX code which appears to work with affected >> systems of mine, however, the code has not yet made it into CVS. I >> spliced it into a 6.2 miniboot ISO and it worked. > > Ooh ahh, please sir, can I have some more^Wit? :) I did some googling.. Is this the patch? http://people.freebsd.org/~kib/realbtx/realbtx.2.patch (Going to try it today anyway :) [I'm CC'ing [EMAIL PROTECTED] Yes, there is also a loader/pxeboot in the same directory. As kib@ told me, do not install this loader on your disk which may destroy your data. Regards, Rong-En Fan -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ 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: Unable to install FreeBSD from external USB cdrom
Daniel O'Connor wrote: kib@ has real mode BTX code which appears to work with affected systems of mine, however, the code has not yet made it into CVS. I spliced it into a 6.2 miniboot ISO and it worked. Ooh ahh, please sir, can I have some more^Wit? :) I did some googling.. Is this the patch? http://people.freebsd.org/~kib/realbtx/realbtx.2.patch (Going to try it today anyway :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On 5/26/07, Bruce M. Simpson <[EMAIL PROTECTED]> wrote: Daniel O'Connor wrote: > > I believe this is most likely this issue... > http://www.nabble.com/BTX-issues-when-booting-from-a-USB-CD-ROM-t3047441.html > > Alas no solution yet as far as I am aware :( > Forgot to Cc: my reply to the list: kib@ has real mode BTX code which appears to work with affected systems of mine, however, the code has not yet made it into CVS. I spliced it into a 6.2 miniboot ISO and it worked. It also works on my ThinkPad X60 with 7.x boot cd. Regards, Rong-En Fan regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On Saturday 26 May 2007 22:00, Bruce M. Simpson wrote: > Daniel O'Connor wrote: > > I believe this is most likely this issue... > > http://www.nabble.com/BTX-issues-when-booting-from-a-USB-CD-ROM-t30 > >47441.html > > > > Alas no solution yet as far as I am aware :( > > Forgot to Cc: my reply to the list: > > kib@ has real mode BTX code which appears to work with affected > systems of mine, however, the code has not yet made it into CVS. I > spliced it into a 6.2 miniboot ISO and it worked. Ooh ahh, please sir, can I have some more^Wit? :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpQueiH1zEJQ.pgp Description: PGP signature
Re: Unable to install FreeBSD from external USB cdrom
Daniel O'Connor wrote: I believe this is most likely this issue... http://www.nabble.com/BTX-issues-when-booting-from-a-USB-CD-ROM-t3047441.html Alas no solution yet as far as I am aware :( Forgot to Cc: my reply to the list: kib@ has real mode BTX code which appears to work with affected systems of mine, however, the code has not yet made it into CVS. I spliced it into a 6.2 miniboot ISO and it worked. regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unable to install FreeBSD from external USB cdrom
On Friday 25 May 2007 16:39, Andrei Kolu wrote: > int=000d err= efl=00030002 eip=2abf > eax=0300 ebx= ecx=0001 edx=009f > esi=000c edi= ebp= esp=03f6 > cs=f000 ds=3fca es=3fac fs= gs= ss=9e3c > cs:eip=23 0f 01 16 0c 2c 0f 20-c0 0c 01 0f 22 c8 b8 28 > 00 8e d8 0f 20 c0 24 fe-0f 0f 22 c8 eb 00 66 58 c3 > ss:esp=ca 3f 00 00 10 22 01 4b-ca 3f e4 71 47 91 00 00 > 46 02 f8 47 89 00 b5 03-00 00 9f 00 00 00 00 00 > > BTX halted > --- > I tried with FreeBSD 6.1, 6.2, 6.2p4 > same result. Linux and Windows XP booted from cd just fine so I am > sure this is not hardware problem. I believe this is most likely this issue... http://www.nabble.com/BTX-issues-when-booting-from-a-USB-CD-ROM-t3047441.html Alas no solution yet as far as I am aware :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgp9fXKwsX0Jd.pgp Description: PGP signature
Unable to install FreeBSD from external USB cdrom
Bootloader gave me this error message: --- BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard _ int=000d err= efl=00030002 eip=2abf eax=0300 ebx= ecx=0001 edx=009f esi=000c edi= ebp= esp=03f6 cs=f000 ds=3fca es=3fac fs= gs= ss=9e3c cs:eip=23 0f 01 16 0c 2c 0f 20-c0 0c 01 0f 22 c8 b8 28 00 8e d8 0f 20 c0 24 fe-0f 0f 22 c8 eb 00 66 58 c3 ss:esp=ca 3f 00 00 10 22 01 4b-ca 3f e4 71 47 91 00 00 46 02 f8 47 89 00 b5 03-00 00 9f 00 00 00 00 00 BTX halted --- I tried with FreeBSD 6.1, 6.2, 6.2p4 same result. Linux and Windows XP booted from cd just fine so I am sure this is not hardware problem. Andrei ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: btx crashes when booting 6.1 from usb cdrom
Stephen Clark wrote: [...] If you could build custom boot images, try http://people.freebsd.org/~kib/realbtx realbtx.2.patch is the patch, and loader is the /boot/loader built with that patch applied. If you could rearrange CD image with that loader put into /boot, then try to load from it and report results. CAUTION: Do not install boot2 or loader on your harddrive, code had very little exposure and may cause you machine to become unbootable. Hi Konstantin, Thanks this worked. I have another question though. I mounted the distro 1 cd and cd to /cdrom and did tar cSf - . |(cd /usr/myboot;tar xSf -) so I could move in the new loader program. The problem is I ended up with an iso file system after I did mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /usr/myboot that was 991mb which was to big to put on a CD. Where did I go wrong? Since this was only a test I rm'ed packages, rescue and release directories, but how did it all fit on the CD originally? Many files are hardlinked on the original media (for example all in /rescue is hardlink to one binary), but tar makes a copy of each file. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: btx crashes when booting 6.1 from usb cdrom
Konstantin Belousov wrote: On Thu, Apr 05, 2007 at 09:21:05AM -0400, Stephen Clark wrote: Hello List, When I boot linux from my usb cdrom it works great - but when I try the 6.1 release media it fails - BTX crashes. I found a listed bug kern/85257 that seems to be the same problem. Had this been resolved? Will it be resolved? Thanks, Steve If you could build custom boot images, try http://people.freebsd.org/~kib/realbtx realbtx.2.patch is the patch, and loader is the /boot/loader built with that patch applied. If you could rearrange CD image with that loader put into /boot, then try to load from it and report results. CAUTION: Do not install boot2 or loader on your harddrive, code had very little exposure and may cause you machine to become unbootable. Hi Konstantin, Thanks this worked. I have another question though. I mounted the distro 1 cd and cd to /cdrom and did tar cSf - . |(cd /usr/myboot;tar xSf -) so I could move in the new loader program. The problem is I ended up with an iso file system after I did mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /usr/myboot that was 991mb which was to big to put on a CD. Where did I go wrong? Since this was only a test I rm'ed packages, rescue and release directories, but how did it all fit on the CD originally? Thanks, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
btx crashes when booting 6.1 from usb cdrom
Hello List, When I boot linux from my usb cdrom it works great - but when I try the 6.1 release media it fails - BTX crashes. I found a listed bug kern/85257 that seems to be the same problem. Had this been resolved? Will it be resolved? Thanks, Steve -- "They that give up essential liberty to obtain temporary safety, deserve neither liberty nor safety." (Ben Franklin) "The course of history shows that as a government grows, liberty decreases." (Thomas Jefferson) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cdrom after installing kernel
hi all I have got a little problem- after rebuilding the kernel my CD ROM doesn't work. I thought maybe I had commented something necessary (like CD9660), but even if I change ident and filename from GENERIC to something other after mount /cdrom I get this error: "cd9660: /dev/acd0c: Device not configured " (ofcourse I had put cd into the cdrom ) while using GENERIC kernel everything is all right otherwise device can't be configured...why thanks in advance... marek denis ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CDROM/CDRW devices not working.
>9660: /dev/acd0c: Device not configured Did you remake the devices? (cd /dev && sh MAKEDEV acd0) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
CDROM/CDRW devices not working.
When ever I try to burn cds, I get the following... burncd: open(/dev/acd1c): Device not configured When I try to mount cds I get a similar errorcd 9660: /dev/acd0c: Device not configured The devices are detected by the kernel, but they won't work. dmesg says... acd0: CDROM at ata0-slave UDMA33 acd1: CD-RW at ata1-master WDMA2 I used to work with 4.5-Release so the drivers should work Any ideas? FreeBSD 4.6-STABLE i386 i386 __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom: device not configured error
If I do a "boot -verbose" at the ok prompt when booting, the cdrom is detected and works fine! (And I do not get the ATA identify retries exceeded error). If I do not boot with -verbose, the cdrom does not work. What gives? Thanks for any and all ideas. Doug __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom: device not configured error
Doug wrote: > --- Kevin Oberman <[EMAIL PROTECTED]> wrote: > >>Have you deleted your acd* devices in /dev and used /dev/MAKEDEV to >>re-create them? The new ATA drivers require this as the minor mode >>must change. If you did a mergemaster after any upgrade, this should >>have been taken care of. >> >> >>>ls -l /dev/acd* >>> >>crw-r- 4 root operator 117, 0 Aug 9 11:17 /dev/acd0a >>crw-r- 4 root operator 117, 0 Aug 9 11:17 /dev/acd0c >>crw-r- 4 root operator 117, 8 Jul 25 15:46 /dev/acd1a >>crw-r- 4 root operator 117, 8 Jul 25 15:46 /dev/acd1c >> >>Note the major (117) and minor (0) mode of acd0?. If yours does not >>match, that is likely your problem. >> > > Yes, this has been done and that is how they look. > > Any other ideas? Do you have a slave device and no master on that controller? FreeBSD may not recognize it. Kent > > Thanks, > Doug > > > __ > Do You Yahoo!? > HotJobs - Search Thousands of New Jobs > http://www.hotjobs.com > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > > . > > -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom: device not configured error
--- Kevin Oberman <[EMAIL PROTECTED]> wrote: > Have you deleted your acd* devices in /dev and used /dev/MAKEDEV to > re-create them? The new ATA drivers require this as the minor mode > must change. If you did a mergemaster after any upgrade, this should > have been taken care of. > > > ls -l /dev/acd* > crw-r- 4 root operator 117, 0 Aug 9 11:17 /dev/acd0a > crw-r- 4 root operator 117, 0 Aug 9 11:17 /dev/acd0c > crw-r- 4 root operator 117, 8 Jul 25 15:46 /dev/acd1a > crw-r- 4 root operator 117, 8 Jul 25 15:46 /dev/acd1c > > Note the major (117) and minor (0) mode of acd0?. If yours does not > match, that is likely your problem. Yes, this has been done and that is how they look. Any other ideas? Thanks, Doug __ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom: device not configured error
Doug, Have you deleted your acd* devices in /dev and used /dev/MAKEDEV to re-create them? The new ATA drivers require this as the minor mode must change. If you did a mergemaster after any upgrade, this should have been taken care of. > ls -l /dev/acd* crw-r- 4 root operator 117, 0 Aug 9 11:17 /dev/acd0a crw-r- 4 root operator 117, 0 Aug 9 11:17 /dev/acd0c crw-r- 4 root operator 117, 8 Jul 25 15:46 /dev/acd1a crw-r- 4 root operator 117, 8 Jul 25 15:46 /dev/acd1c Note the major (117) and minor (0) mode of acd0?. If yours does not match, that is likely your problem. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ATA CDROM Problems 4.6 (and 4.6.1)
I just upgraded from 4.5 (off the CD Release) to 4.6 (off the CD release) and yadda yadda yadda ATA CDROM fails per the Errata (big read timeout, etc). The workaround DOESN'T /home/dob: cat /boot/loader.conf # -- sysinstall generated deltas -- # userconfig_script_load="YES" hw.ata.ata_dma="1" hw.ata.atapi_dma="1" /var/log: gzcat messages.0.gz | grep -i timeout Jul 21 19:28:55 yorky /kernel: acd0: READ_BIG command timeout - resetting Jul 21 19:29:25 yorky /kernel: acd0: READ_BIG command timeout - resetting Jul 21 19:29:55 yorky /kernel: acd0: READ_BIG command timeout - resetting Jul 21 19:30:26 yorky /kernel: acd0: READ_BIG command timeout - resetting I even tried a 4.6.1 GENERIC kernel a friend prepared and it fails. /var/log: gzcat messages.0.gz | grep -i timeout|grep GENERIC Jul 25 21:48:43 yorky /kernel.GENERIC: acd0: READ_BIG command timeout - resetting Jul 25 21:49:13 yorky /kernel.GENERIC: acd0: READ_BIG command timeout - resetting I'm now stuck without a way to upgrade to 4.7 (off the CD's) (not really, I kept the old 4.5 kernel and if I boot.old/kernel.old, the CDROM works perfectly). I always do a source buildworld, installworld, mergemaster, build/install kernel yadda yadda. I'm willing to play Guinea Pig for any and all fixes. I've got a generic 50X CDROM: dmesg | grep acd acd0: CDROM at ata1-master PIO4 It mounts, I can do ls, but "cat ports.tgz > /dev/null" results in the big read stuff. I've had one panic. Now what? I've seen others in the same boat. Thanks in advance, = Dan O'Brien, [EMAIL PROTECTED] Cell: 614-783-4859 Work: 614-476-8473 Home: 740-927-2178 Pataskala, OH USA '02 Suzuki DL1000 #00082 Grey __ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
VMware2 and CDROM image
Hi, I have a patch that allow to use CD-ROM images in VMware2 via vn device: http://sysoev.ru/freebsd/patch.vn_cd.txt Patch was made and tested on FreeBSD 4.2 and 4.3. I had used it to install Windows NT 4.0 from CD-ROM image in VMware2. It can be used on FreeBSD 4.x only (because it's using vn device). Russian description is available here: http://sysoev.ru/freebsd/vmware_cd_image.html In English, short: After appling of patch you need rebuild vnconfig and kernel. vnconfig will get new options - '-s cdrom': vnconfig -s cdrom -c vn0c image.iso After configuring vn device you can use it in VMware2 as /dev/vn0c instead of physical CD-ROM device. Igor Sysoev http://sysoev.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ATA Atapi Cdrom Problems
Hello. I have seen a few threads with regards to having a problem with ATAPI cdroms, on 4.6.rcx, and I also have the same problems.. I have several different hardware configurations that I have tested this with, as well as versions.. 4.5 was the last version that worked across the board.. 4.6 RC2 and RC3 both have the exact same problem reading cdroms, both commercial and inhouse burned.. Newer drives appear to work. I have several ACER and Toshiba 40X and 52X that refuse to read (beyond a directory listing). Error: READ_BIG command timeout - reseting It appears this problem began after ATA was mfc.. Not sure why there is not more noise with regards to this, however I do agree it to be a "Major Problem". --john To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom can't be mounted under freeBSD 4.5-stable
On Sat, Apr 27, 2002 at 04:32:18PM -0400, Scott M. Nolde wrote: > Ian Dowse([EMAIL PROTECTED])@2002.04.27 21:28:11 +: > > >Interesting, because in the /dev/MAKEDEV script is this concerning the > > >minor number: > > ... > > >... which is exactly what I have. What's in your MAKEDEV? When/why did > > >the "+ 2" get in there if it's incorrect? > > > > You have a stale MAKEDEV. You need at least revision 1.243.2.45 > > (March 18th) to pick up the changes that occurred with the big ATA > > merge from -current. Maybe you forgot to run mergemaster after > > updating? > > > > Ian > > Nope, I ran mergemaster and I was not promted to. Interesting you mention > the version. I have 1.243.2.44 2002/03/11 after running a cvsup this > morning and rebuilding everything. 1.243.2.45 was commited to RELENG_4 on the 18th March going by the logs, and it's now up to 1.243.2.47 :) -- Simon Dick [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom can't be mounted under freeBSD 4.5-stable
Ian Dowse([EMAIL PROTECTED])@2002.04.27 21:28:11 +: > >Interesting, because in the /dev/MAKEDEV script is this concerning the > >minor number: > ... > >... which is exactly what I have. What's in your MAKEDEV? When/why did > >the "+ 2" get in there if it's incorrect? > > You have a stale MAKEDEV. You need at least revision 1.243.2.45 > (March 18th) to pick up the changes that occurred with the big ATA > merge from -current. Maybe you forgot to run mergemaster after > updating? > > Ian Nope, I ran mergemaster and I was not promted to. Interesting you mention the version. I have 1.243.2.44 2002/03/11 after running a cvsup this morning and rebuilding everything. -- Scott Nolde GPG Key 0xD869AB48 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom can't be mounted under freeBSD 4.5-stable
>Interesting, because in the /dev/MAKEDEV script is this concerning the >minor number: ... >... which is exactly what I have. What's in your MAKEDEV? When/why did >the "+ 2" get in there if it's incorrect? You have a stale MAKEDEV. You need at least revision 1.243.2.45 (March 18th) to pick up the changes that occurred with the big ATA merge from -current. Maybe you forgot to run mergemaster after updating? Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom can't be mounted under freeBSD 4.5-stable
Ian Dowse([EMAIL PROTECTED])@2002.04.27 20:26:40 +: > In message <[EMAIL PROTECTED]>, "Scott M. Nolde" writes: > >As you can see, acd0 and acd1 are recognized properly by the system. I > >even remade the devices with /dev/MAKEDEV to no avail: > >crw-r- 2 root operator 117, 0 Apr 26 22:45 /dev/acd0a > >crw-r- 2 root operator 117, 2 Apr 26 22:45 /dev/acd0c > >crw-r- 2 root operator 117, 8 Apr 26 22:45 /dev/acd1a > >crw-r- 2 root operator 117, 10 Apr 26 22:45 /dev/acd1c > > Did you use mergemaster to update MAKEDEV before running it? I get > the following, which is different: > > crw-r- 4 root operator 117, 0 Apr 27 20:24 acd0a > crw-r- 4 root operator 117, 0 Apr 27 20:24 acd0c > crw-r- 4 root operator 117, 8 Apr 27 20:24 acd1a > crw-r- 4 root operator 117, 8 Apr 27 20:24 acd1c > > Ian Thanks for the comparison. I chamged the minor nodes by modifying the MAKEDEV script to recreate what you have and now the cdroms work. Thanks! -- Scott Nolde GPG Key 0xD869AB48 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom can't be mounted under freeBSD 4.5-stable
Ian Dowse([EMAIL PROTECTED])@2002.04.27 20:26:40 +:
> In message <[EMAIL PROTECTED]>, "Scott M. Nolde" writes:
> >As you can see, acd0 and acd1 are recognized properly by the system. I
> >even remade the devices with /dev/MAKEDEV to no avail:
> >crw-r- 2 root operator 117, 0 Apr 26 22:45 /dev/acd0a
> >crw-r- 2 root operator 117, 2 Apr 26 22:45 /dev/acd0c
> >crw-r- 2 root operator 117, 8 Apr 26 22:45 /dev/acd1a
> >crw-r- 2 root operator 117, 10 Apr 26 22:45 /dev/acd1c
>
> Did you use mergemaster to update MAKEDEV before running it? I get
> the following, which is different:
>
> crw-r- 4 root operator 117, 0 Apr 27 20:24 acd0a
> crw-r- 4 root operator 117, 0 Apr 27 20:24 acd0c
> crw-r- 4 root operator 117, 8 Apr 27 20:24 acd1a
> crw-r- 4 root operator 117, 8 Apr 27 20:24 acd1c
>
> Ian
Interesting, because in the /dev/MAKEDEV script is this concerning the
minor number:
i=0
while [ $i -le $units ]; do
dname=$name$i
rm -rf ${dname}* r${dname}*
mknod ${dname}a c $chr $(($i * 8)) root:operator
mknod ${dname}c c $chr $(($i * 8 + 2)) root:operator
ln -f ${dname}a r${dname}a
ln -f ${dname}c r${dname}c
i=$(($i + 1))
done
... which is exactly what I have. What's in your MAKEDEV? When/why did
the "+ 2" get in there if it's incorrect?
--
Scott Nolde
GPG Key 0xD869AB48
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom can't be mounted under freeBSD 4.5-stable
In message <[EMAIL PROTECTED]>, "Scott M. Nolde" writes: >As you can see, acd0 and acd1 are recognized properly by the system. I >even remade the devices with /dev/MAKEDEV to no avail: >crw-r- 2 root operator 117, 0 Apr 26 22:45 /dev/acd0a >crw-r- 2 root operator 117, 2 Apr 26 22:45 /dev/acd0c >crw-r- 2 root operator 117, 8 Apr 26 22:45 /dev/acd1a >crw-r- 2 root operator 117, 10 Apr 26 22:45 /dev/acd1c Did you use mergemaster to update MAKEDEV before running it? I get the following, which is different: crw-r- 4 root operator 117, 0 Apr 27 20:24 acd0a crw-r- 4 root operator 117, 0 Apr 27 20:24 acd0c crw-r- 4 root operator 117, 8 Apr 27 20:24 acd1a crw-r- 4 root operator 117, 8 Apr 27 20:24 acd1c Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom can't be mounted under freeBSD 4.5-stable
Hongbo Li([EMAIL PROTECTED])@2002.04.27 02:05:31 +: > Today I updated src and compiled the kernel using the > old kernel config file. After rebooting the box, I > found the cdrom can't be mounted. The message is: > > cd9660: /dev/acd0c: Device not configured > > what's wrong? > I am having the same problem. Here's some relevant system information from dmesg: FreeBSD 4.5-STABLE #6: Thu Apr 25 06:46:15 EDT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (869.83-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 268419072 (262128K bytes) avail memory = 256761856 (250744K bytes) Preloaded elf kernel "kernel" at 0xc0456000. Preloaded elf module "agp.ko" at 0xc045609c. VESA: v3.0, 65536k memory, flags:0x1, mode table:0xc03bf8c2 (122) VESA: NVidia netsmb_dev: loaded Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 8 entries at 0xc00f0e60 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 agp0: mem 0xe400-0xe7ff at device 0.0 on pci0 pcib2: at device 1.0 on pci0 pci1: on pcib2 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 9 at device 4.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: SanDisk ImageMate USB SmartMedia, rev 1.10/1.01, addr 2 ums0: Microsoft Microsoft IntelliMouse \M-. with IntelliEye, rev 1.10/1.07, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. pci0: (vendor=0x1106, dev=0x3050) at 4.3 fxp0: port 0xd000-0xd01f mem 0xd380-0xd38f,0xd700-0xd7000fff irq 5 at device 10.0 on pci0 fxp0: Ethernet address 00:50:8b:63:ea:40 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bktr0: mem 0xd600-0xd6000fff irq 10 at device 11.0 on pci0 bktr0: Hauppauge Model 44001 B110 bktr0: Hauppauge WinCast/TV, Philips NTSC tuner. pci0: (vendor=0x109e, dev=0x0878) at 11.1 irq 10 pcm0: port 0xb800-0xb83f irq 5 at device 14.0 on pci0 pcib1: on motherboard pci2: on pcib1 orm0: at iomem 0xc-0xcc7ff,0xd-0xd3fff,0xd4000-0xd47ff on isa0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 DUMMYNET initialized (011031) IPv6 packet filtering initialized, logging limited to 20 packets/entry IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to deny, logging limited t o 100 packets/entry by default IPsec: Initialized Security Association Processing. ad0: 38166MB [77545/16/63] at ata0-master UDMA66 ad1: 14664MB [29795/16/63] at ata0-slave UDMA66 acd0: CDROM at ata1-master UDMA33 acd1: CD-RW <8X4X32> at ata1-slave WDMA2 Mounting root from ufs:/dev/ad0s1a As you can see, acd0 and acd1 are recognized properly by the system. I even remade the devices with /dev/MAKEDEV to no avail: crw-r- 2 root operator 117, 0 Apr 26 22:45 /dev/acd0a crw-r- 2 root operator 117, 2 Apr 26 22:45 /dev/acd0c crw-r- 2 root operator 117, 8 Apr 26 22:45 /dev/acd1a crw-r- 2 root operator 117, 10 Apr 26 22:45 /dev/acd1c Got any other clues? Something broke in -STABLE recently. I just haven't had the need to mount a cd or burn a cdr until last night when I noticed. - Scott -- Scott Nolde GPG Key 0xD869AB48 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: CDROM sector size on 4.5
On Fri, Mar 15, 2002 at 13:11:43 -0500, Normand Leclerc wrote: > This is a SCSI drive. I am wondering, why would SCSI be different from > IDE in that matter? The drivers are different, and the SCSI driver uses the disk layer. The ATAPI cd driver does not. Please send full dmesg information, including any errors generated when you try to use 512 byte sectors. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: CDROM sector size on 4.5
This is a SCSI drive. I am wondering, why would SCSI be different from IDE in that matter? Normand Leclerc [EMAIL PROTECTED] > -Original Message- > From: Kenneth D. Merry [mailto:[EMAIL PROTECTED]] > Sent: March 14, 2002 8:33 PM > To: Normand Leclerc > Cc: [EMAIL PROTECTED] > Subject: Re: CDROM sector size on 4.5 > > On Thu, Mar 14, 2002 at 13:28:38 -0500, Normand Leclerc wrote: > > I was wondering if the CDROM sector size detection code has changed. > > I own a CDRW with a jumper that let me select the sector size (2048 or > > 512). It is set to 512 as this is the most convenient way for me to > > handle it. Lately, I tried to dump a CD ISO image on my hard drive but > > got a sector boundary error. I had to specify 2048 bytes of sector size > > to get dd to work properly. > > > > Is 4.5 different in that matter? > > > > Is this a SCSI or ATAPI drive? > > Ken > -- > Kenneth Merry > [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Asus A7V266-E and CDROM...
On 02/17/2002 08:24 AM, Simon Dick wrote: > On Sun, Feb 17, 2002 at 02:07:48PM +0100, Cliff Sarginson wrote: > >>On Sun, Feb 17, 2002 at 04:12:38AM -0500, Bryan Liesner wrote: >> >>>I just purchased and installed an Asus A7V266-E motherboard that has a >>>problem when trying to mount one of my CDROMs. I looked around on the >>>archives and didn't really see an answer. The motherboard sees the >>>CDROM, and the boot probe seems to detect it correctly too. >>> >>>mount /cdrom complains: >>>cd9660: /dev/acd0c: Invalid argument >>> >>>acd1c (a Sony 24x R RW) mounts just fine. >>> >>>Here's the fstab entries: >>> >>>/dev/acd0c /cdrom cd9660 ro,noauto 0 0 >>>/dev/acd1c /burner cd9660 ro,noauto 0 0 >>> >>>I tried putting the offending drive on the secondary controller with >>>the Sony, but no luck. >>> >>>dmesg is atached >>> >>>-- >>>== >>>= Bryan D. Liesner LeezSoft Communications, Inc. = >>>= A subsidiary of LeezSoft Inc. = >>>= [EMAIL PROTECTED] Home of the Gipper= >>>== >>> >>>ad0: 19595MB [39813/16/63] at ata2-master UDMA100 >>>ad1: 8693MB [17662/16/63] at ata3-master UDMA66 >>>acd0: CDROM at ata0-master using PIO4 >>>acd1: CD-RW at ata1-master using PIO4 >>> >>This does not look quite right, 4 masters, no slaves ? >> > > That looks reasonable to me, AFAIR the A7V266-E comes with a second set > of IDE ports (I know my A7V original does). > > Yes, sort of. A Promise raid controller is an option for this board but I opted out for that, since I already had an Promise Ultra 100 card to migrate to the new system. I just wanted to upgrade from my K6-II 500 MHz system. This guy is fast, it did a build world and kernel in 24 minutes! So, yes, I have hard drives as masters on the Promise and the CDs plugged into the motherboard. -- == = Bryan D. Liesner LeezSoft Communications, Inc. = = A subsidiary of LeezSoft Inc. = = [EMAIL PROTECTED] Home of the Gipper= == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: that atapi cdrom (really dvdrom) problem
OK, I take it back. I don't think it is a signed versus unsigned issue, though I still think it is dangerous the way atapi_read mixes them. I've been trying to follow the two pr's (kern/31530 and kern/31460) to see if the panics they're getting were related to the problem I reported earlier. It doesn't look like I am having the same kind of bytecount corruption problems reported in those pr's -- at least I'm not getting way large bytecounts. What seems to be happening is an atapi_read is partially completing and then an ATA_S_ERROR comes back on the status flag and this somehow leads me to an error message. Is anyone else, delving into this? And are there good places to read up on the specs for atapi-dvd-roms so I can make more sense as to how the drive should behave? - -r --- End of forwarded message --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: that atapi cdrom (really dvdrom) problem
OK, I take it back. I don't think it is a signed versus unsigned issue, though I still think it is dangerous the way atapi_read mixes them. I've been trying to follow the two pr's (kern/31530 and kern/31460) to see if the panics they're getting were related to the problem I reported earlier. It doesn't look like I am having the same kind of bytecount corruption problems reported in those pr's -- at least I'm not getting way large bytecounts. What seems to be happening is an atapi_read is partially completing and then an ATA_S_ERROR comes back on the status flag and this somehow leads me to an error message. Is anyone else, delving into this? And are there good places to read up on the specs for atapi-dvd-roms so I can make more sense as to how the drive should behave? -r To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: kernel panic if using SCSI CDROM as root device
Hi!
On Thu, Nov 15, 2001 at 12:30:27AM +0100, Dirk Froemberg wrote:
> I build an CDROM image with a boot image containing a GENERIC kernel
> and an "ordinary" FreeBSD-4.4-STABLE installation.
>
> After booting the kernel I get the "mountroot> " prompt. On systems
> having an ATAPI-CDROM mounting the CD as a root filesystem works
> (giving cd9660:/dev/acd0c as root), but not on SCSI systems (giving
> cd9660:/dev/cd0c as root). On such systems a kernel panic occurs
> ("Fatal trap 12: page fault while in kernel mode").
Now, some more debug information...
Regards Dirk
ok boot -C
/kernel text=0x203a28 data=0x39464+0x19cac syms=[0x4+0x30df0+0x4+0x353fc]
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.4-STABLE #0: Thu Nov 15 11:18:56 CET 2001
dirk@bach:/usr/obj/usr/src/sys/CDROM
Timecounter "i8254" frequency 1193182 Hz
Timecounter "TSC" frequency 166527838 Hz
CPU: Pentium/P55C (166.53-MHz 586-class CPU)
Origin = "GenuineIntel" Id = 0x543 Stepping = 3
Features=0x8001bf
real memory = 67043328 (65472K bytes)
avail memory = 61489152 (60048K bytes)
Preloaded elf kernel "kernel" at 0xc03bf000.
Intel Pentium detected, installing workaround for F00F bug
md0: Malloc disk
Using $PIR table, 6 entries at 0xc00fde70
npx0: on motherboard
npx0: INT 16 interface
pcib0: on motherboard
pci0: on pcib0
pcib2: at device 1.0 on pci0
pci1: on pcib2
isab0: at device 7.0 on pci0
isa0: on isab0
atapci0: port 0x6400-0x640f at device 7.1 on pci0
fxp0: port 0x6c00-0x6c3f mem
0xe900-0xe901,0xe902-0xe9020fff irq 9 at device 9.0 on pci0
fxp0: Ethernet address 00:02:b3:40:db:8c
inphy0: on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ahc0: port 0x7000-0x70ff mem 0xe9021000-0xe9021fff
irq 12 at device 10.0 on pci0
aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/255 SCBs
pci0: at 12.0 irq 10
pcib1: on motherboard
pci2: on pcib1
orm0: at iomem 0xc-0xc7fff,0xc8000-0xc97ff,0xca000-0xcf7ff on isa0
fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: at port 0x60,0x64 on isa0
atkbd0: flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x100>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
Waiting 15 seconds for SCSI devices to settle
Mounting root from cd9660:cd0a
cd0 at ahc0 bus 0 target 3 lun 0
cd0: Removable CD-ROM SCSI-2 device
cd0: 20.000MB/s transfers (20.000MHz, offset 16)
cd0: cd present [66018 x 2048 byte records]
da0 at ahc0 bus 0 target 0 lun 0
da0: Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled
da0: 8703MB (17824700 512 byte sectors: 255H 63S/T 1109C)
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x28
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01b51aa
stack pointer = 0x10:0xc03e1db4
frame pointer = 0x10:0xc03e1dd8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
interrupt mask = none
kernel: type 12 trap, code=0
Stopped at dsioctl+0x42: movl0xc(%eax),%ecx
db> trace
dsioctl(c0900b80,40046304,c03e1e28,1,c090e844) at dsioctl+0x42
diskioctl(c0900b80,40046304,c03e1e28,1,c0355b60) at diskioctl+0x6f
iso_get_ssector(c0900b80,c0355b60,0,c0909e00,c0355b60) at iso_get_ssector+0x2e
iso_mountroot(c0909e00,c0355b60,c03e1fb0,c0900e80,c090df30) at iso_mountroot+0x47
cd9660_mount(c0909e00,0,0,0,c0355b60) at cd9660_mount+0x2c
vfs_mountroot_try(c02dc78a) at vfs_mountroot_try+0x13d
vfs_mountroot(0,3dec00,3e6000,0,c0120670) at vfs_mountroot+0x3c
mi_startup(0,0,0,0,0) at mi_startup+0x68
begin() at begin+0x47
--
Dirk Froemberg
FreeBSD: The Power to Serve!http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: FreeBSD CD 4.4 CDROM subscriptions - who's doing what?
Warner Losh <[EMAIL PROTECTED]> wrote: > Yes. It appears The Daemon News is going to produce CDROM using the > official iso images that the project will release. The posting was at > great pains to say they are not associated with WindRiver. I expect > that others may do this, or something similar. FreeBSD Services in > the UK has already announced they are doing a DVD of all 4 ISOs plus a > bunch of extra stuff. Others may do other things too, but I don't > think I've seen an announcement from anyone else yet. You can regard this as an official announcement ... Lehmanns in Germany is selling a six CD-ROM set, which is essentially the first four original CDs plus some extra stuff, including Alpha installation bits, extra packages, archives of German BSD mailing lists, German documentation and German sysinstall with translated online help texts (optional, of course -- you can still run the original English sysinstall if you want). Regards Oliver PS: This is the URL: http://www.lob.de/cgi-bin/work/outputexpert?mode=viewone&titnr=210084150 -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "All that we see or seem is just a dream within a dream" (E. A. Poe) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom
In message <[EMAIL PROTECTED]> Bruce Burden writes: : > : > I'm getting a No such file or directory when I try to mount a CDROM with : > 4-STABLE. I've seen some stuff about this and have tried as many of the : > suggestions as I can, but no joy. : > : Is your pccard a 32 bit (CardBus) or a 16 bit (PCMCIA) card? :FreeBSD only currently supports 16 bit pccards. 5.0 is supposed to :have 32 bit support... We don't yet support cardbus ata cards. Of course I've seen three ata cards that had he fancy copper ridges on it that are a hallmark of cardbus cards that worked just fine as 16-bit cards. I dont' completely understand this. Maybe it is a fakeout, or maybe the card works for both 16-bit and 32-bit operations (not that I understand how this could work). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: cdrom
Bit more information. pccardc dumpcis gives... Configuration data for card in slot 0 Tuple #1, code = 0x1 (Common memory descriptor), length = 3 000: dc 00 ff Common memory device information: Device number 1, type Function specific, WPS = ON Speed = 100nS, Memory block size = 512b, 1 units Tuple #2, code = 0x15 (Version 1 info), length = 26 000: 04 01 20 00 4e 69 6e 6a 61 41 54 41 2d 00 56 31 010: 2e 30 00 41 50 30 30 20 00 ff Version = 4.1, Manuf = [ ], card vers = [NinjaATA-] Addit. info = [V1.0],[AP00 ] Tuple #3, code = 0x1a (Configuration map), length = 5 000: 01 23 00 02 03 Reg len = 2, config register addr = 0x200, last config = 0x23 Registers: XX-- Tuple #4, code = 0x1b (Configuration entry), length = 21 000: e1 01 3d 11 55 1e fc 23 f0 61 80 01 07 86 03 01 010: 30 68 d0 10 00 Config index = 0x21(default) Interface byte = 0x1 (I/O) Vcc pwr: Nominal operating supply voltage: 5 x 1V Max current average over 1 second: 1.5 x 100mA Wait scale Speed = 1.5 x 1 us Card decodes 16 address lines, full 8/16 Bit I/O I/O address # 1: block start = 0x180 block length = 0x8 I/O address # 2: block start = 0x386 block length = 0x2 IRQ modes: Level IRQs: 3 5 6 12 14 15 Memory space length = 0x10 Tuple #5, code = 0x1b (Configuration entry), length = 15 000: 22 38 f0 61 90 01 07 96 03 01 30 68 d0 10 00 Config index = 0x22 Card decodes 16 address lines, full 8/16 Bit I/O I/O address # 1: block start = 0x190 block length = 0x8 I/O address # 2: block start = 0x396 block length = 0x2 IRQ modes: Level IRQs: 3 5 6 12 14 15 Memory space length = 0x10 Tuple #6, code = 0x1b (Configuration entry), length = 15 000: 23 38 f0 61 a0 01 07 a6 03 01 30 68 d0 10 00 Config index = 0x23 Card decodes 16 address lines, full 8/16 Bit I/O I/O address # 1: block start = 0x1a0 block length = 0x8 I/O address # 2: block start = 0x3a6 block length = 0x2 IRQ modes: Level IRQs: 3 5 6 12 14 15 Memory space length = 0x10 Tuple #7, code = 0x14 (No link), length = 0 Tuple #8, code = 0xff (Terminator), length = 0 1 slots found I just finished resyncing and making 4-STABLE and I'm seeing the same behaviour... mount /cdrom still gives the same error :( david > AFAIK it's 16-bit. In fact after rebooting once it was identified as a > NinjaATA card, which is 16-bit. > > david > > > > > > I'm getting a No such file or directory when I try to mount a CDROM with > > > 4-STABLE. I've seen some stuff about this and have tried as many of the > > > suggestions as I can, but no joy. > > > > > Is your pccard a 32 bit (CardBus) or a 16 bit (PCMCIA) card? > >FreeBSD only currently supports 16 bit pccards. 5.0 is supposed to > >have 32 bit support... > > > > Bruce > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ATAPI CDROM not detected after Nov 5
It seems Andrew Reilly wrote: > > Nov 5 12:35:40 gurney /kernel: FreeBSD 4.2-BETA #0: Sun Nov 5 10:15:56 EST 200 > Nov 14 14:39:32 gurney /kernel: FreeBSD 4.2-BETA #0: Mon Nov 13 14:15:20 EST 200 Uhm, seems to me that this is the same source being built or what ?? Upgrade to at least 4.2-RELEASE... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ATAPI CDROM not detected after Nov 5
Hi, I know no-one else has kicked up a rumpus about this, so I assume that this is a problem with my configuration. I have a FreeBSD box that I track -STABLE with. I don't use my CD-ROM much, but recently discovered that it isn't working. In fact, checking dmesg showed that it isn't being detected. I haven't changed my configuration or my hardware. Any clues? Relevant evidence, exhibit 1: /var/log/messages from Nov 5: Nov 5 12:35:40 gurney /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Nov 5 12:35:40 gurney /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989 , 1991, 1992, 1993, 1994 Nov 5 12:35:40 gurney /kernel: The Regents of the University of California. All rights reserved. Nov 5 12:35:40 gurney /kernel: FreeBSD 4.2-BETA #0: Sun Nov 5 10:15:56 EST 200 0 Nov 5 12:35:40 gurney /kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GUR NEY Nov 5 12:35:40 gurney /kernel: Timecounter "i8254" frequency 1193182 Hz Nov 5 12:35:40 gurney /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (499.1 5-MHz 686-class CPU) Nov 5 12:35:40 gurney /kernel: Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Nov 5 12:35:40 gurney /kernel: Features=0x387f9ff Nov 5 12:35:40 gurney /kernel: real memory = 134152192 (131008K bytes) Nov 5 12:35:40 gurney /kernel: avail memory = 126799872 (123828K bytes) Nov 5 12:35:40 gurney /kernel: Preloaded elf kernel "kernel" at 0xc03c. Nov 5 12:35:40 gurney /kernel: Pentium Pro MTRR support enabled Nov 5 12:35:41 gurney /kernel: npx0: on motherboard Nov 5 12:35:41 gurney /kernel: npx0: INT 16 interface Nov 5 12:35:41 gurney /kernel: pcib0: on motherboard Nov 5 12:35:41 gurney /kernel: pci0: on pcib0 Nov 5 12:35:41 gurney /kernel: pcib1: at device 1.0 on pci0 Nov 5 12:35:41 gurney /kernel: pci1: on pcib1 Nov 5 12:35:41 gurney /kernel: pci1: at 0.0 irq 11 Nov 5 12:35:41 gurney /kernel: isab0: at devi ce 7.0 on pci0 Nov 5 12:35:41 gurney /kernel: isa0: on isab0 Nov 5 12:35:41 gurney /kernel: atapci0: port 0xf 000-0xf00f at device 7.1 on pci0 Nov 5 12:35:41 gurney /kernel: ata0: at 0x1f0 irq 14 on atapci0 Nov 5 12:35:41 gurney /kernel: ata1: at 0x170 irq 15 on atapci0 [...] Nov 5 12:35:41 gurney /kernel: ad0: 6149MB [13328/15/ 63] at ata0-master UDMA33 Nov 5 12:35:41 gurney /kernel: ad1: 6149MB [13328/15/ 63] at ata0-slave UDMA33 Nov 5 12:35:41 gurney /kernel: acd0: CDROM at ata1-master using UDMA33 Time passes, /var/log/messages from Nov 14: Nov 14 14:39:32 gurney /kernel: Copyright (c) 1992-2000 The FreeBSD Project. Nov 14 14:39:32 gurney /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989 , 1991, 1992, 1993, 1994 Nov 14 14:39:32 gurney /kernel: The Regents of the University of California. All rights reserved. Nov 14 14:39:32 gurney /kernel: FreeBSD 4.2-BETA #0: Mon Nov 13 14:15:20 EST 200 0 Nov 14 14:39:32 gurney /kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GUR NEY Nov 14 14:39:32 gurney /kernel: Timecounter "i8254" frequency 1193182 Hz Nov 14 14:39:32 gurney /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (499.1 5-MHz 686-class CPU) Nov 14 14:39:32 gurney /kernel: Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Nov 14 14:39:32 gurney /kernel: Features=0x387f9ff Nov 14 14:39:32 gurney /kernel: real memory = 134152192 (131008K bytes) Nov 14 14:39:32 gurney /kernel: avail memory = 126799872 (123828K bytes) Nov 14 14:39:32 gurney /kernel: Preloaded elf kernel "kernel" at 0xc03c. Nov 14 14:39:32 gurney /kernel: Pentium Pro MTRR support enabled Nov 14 14:39:32 gurney /kernel: npx0: on motherboard Nov 14 14:39:32 gurney /kernel: npx0: INT 16 interface Nov 14 14:39:32 gurney /kernel: pcib0: on motherboard Nov 14 14:39:32 gurney /kernel: pci0: on pcib0 Nov 14 14:39:32 gurney /kernel: pcib1: at device 1.0 on pci0 Nov 14 14:39:32 gurney /kernel: pci1: on pcib1 Nov 14 14:39:32 gurney /kernel: pci1: at 0.0 irq 11 Nov 14 14:39:32 gurney /kernel: isab0: at devi ce 7.0 on pci0 Nov 14 14:39:32 gurney /kernel: isa0: on isab0 Nov 14 14:39:32 gurney /kernel: atapci0: port 0xf 000-0xf00f at device 7.1 on pci0 Nov 14 14:39:32 gurney /kernel: ata0: at 0x1f0 irq 14 on atapci0 [...] Nov 14 14:39:32 gurney /kernel: ad0: 6149MB [13328/15/ 63] at ata0-master UDMA33 Nov 14 14:39:32 gurney /kernel: ad1: 6149MB [13328/15/ 63] at ata0-slave UDMA33 Nov 14 14:39:32 gurney /kernel: Waiting 5 seconds for SCSI devices to settle Nov 14 14:39:32 gurney /kernel: Mounting root from ufs:/dev/ad0s2a [note absence of acd0] The config file GURNEY still contains: # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI device
Re: My cdrom disappeared with the new ata-all.c :-(
> "Soren" == Soren Schmidt <[EMAIL PROTECTED]> writes: Soren> Oh, you shoudl definitly try the new patch diff-4.2-1... Soren> -Søren It definitely solved the case, thanks a lot :)). Any chance of integration into the tree before 4.2-R ? Regards Eric Masson -- Progress (n) : What led from smart users in front of dumb terminals to dumb users in front of smart terminals. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: sysinstall fails to access cdrom
Ralf Meyer wrote: > > Hej all, > > after rebuilding world and kernel /stand/sysinstall fails to access my > CDROM device with the following console messages: > > ata0-slave: too many segments in DMA table > acd0: READ_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=02 > > If I mount the device manually everything works. The old install (4.0-STABLE, > 25. May 2000) did not show this problem. The devices are recognized in the > dmesg-output as: > > atapci0: port 0x2020-0x202f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ad0: 6194MB [13424/15/63] at ata0-master using UDMA33 > acd0: CDROM at ata0-slave using WDMA2 > > Has anybody else this problem? Did you cd /usr/src/release/sysinstall and make all and make install it? It isn't built when you did the world and your kernel. Kent > > TIA > > Ralf > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:[EMAIL PROTECTED] http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
sysinstall fails to access cdrom
Hej all, after rebuilding world and kernel /stand/sysinstall fails to access my CDROM device with the following console messages: ata0-slave: too many segments in DMA table acd0: READ_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=02 If I mount the device manually everything works. The old install (4.0-STABLE, 25. May 2000) did not show this problem. The devices are recognized in the dmesg-output as: atapci0: port 0x2020-0x202f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ad0: 6194MB [13424/15/63] at ata0-master using UDMA33 acd0: CDROM at ata0-slave using WDMA2 Has anybody else this problem? TIA Ralf To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: CDROM support brokenness
[ On Friday, October 6, Sean O'Connell wrote: ] > > John- > > Have you included Soren Schmidt ([EMAIL PROTECTED]) on this thread? He No, I haven't explicitly. I was hoping to go sleuthing around the code a bit and have a general idea of where he should look before I bugged him directly. > is the maintainer/developer of the ATA stuff. Also, what ata stuff > do you have in your kernel? Do you do the full-blown, > > device ata0 at blah > device ata1 at blah > > or do you use the > > device ata > > and let the chips fall? I copied this kernel config from GENERIC and then edited appropriately. So, yes, I do have the "blah" as above, but you'll notice that "device ata1" is definitely commented out (and has been "forever") since I don't have anything there. # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 #device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #optionsATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | [EMAIL PROTECTED] http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
sym: scsi parity errors for cdrom
I see unrecovered SCSI parity errors under both 3.4- and 4.0 FBSD. I checked cables, connectors and terminations and all seem to be okay. There are other devices on this scsi bus but only cdrom shows errors. It looks like my UltraPlex PX 32CS is at fault. Audio works fine (even while as scsi errors abound). Can anyone interpret the following errors codes from sym driver? tnx. Jul 8 20:21:27 localhost /kernel: sym0: SCSI parity error detected: SCR1=1 DBC=1100 SBCL=29 Jul 8 20:21:27 localhost /kernel: sym0: SCSI parity error detected: SCR1=1 DBC=1100 SBCL=29 Jul 8 20:21:27 localhost /kernel: sym0: unexpected disconnect Jul 8 20:21:27 localhost /kernel: sym0: unexpected disconnect Jul 8 20:21:27 localhost /kernel: (pass0:sym0:0:0:0): unrecovered SCSI parity error. Jul 8 20:21:27 localhost /kernel: (pass0:sym0:0:0:0): unrecovered SCSI parity error. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: dd reading atapi cdrom
In message <[EMAIL PROTECTED]>, ian j hart writes: > I'm used to doing this > > #dd if=/dev/acd0c of=image > > [followed by vnconfig, mount, share using samba] > > This fails under 4.0-STABLE. The error message is Bad address. No data > is transfered. This is reprodusable on three machines. Also fails on > LS120, without error message. > > Am I doing something stupid. Don't answer that! Has anyone got a work > around/better method. Compressing the file would be nice :-) Try using the raw device. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: [EMAIL PROTECTED] Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Mounting an ATAPI-CDROM ?
Gregory Bond wrote in list.freebsd-stable: > > wdc0 ist the IDE controller, not the CD-ROM drive. > > Look for acd0 (ATAPI CD-ROM drive) in your boot messages. > > Type this command: dmesg | grep acd > > Depending on the vintage of his system, the ATAPI CD driver and corresponding > /dev/ entry have been called wcd0 and acd0 at various times, even in the life > of 3.x. That's true. However, this is the -stable mailing list, and he didn't mention the version of his OS at all, so I assumed that he has a "current" -stable, so to speak. ;-) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:[EMAIL PROTECTED]) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
