Re: adding new disk
Unfortunately nothing helped. > # dd if=/dev/zero bs=1m of=/dev/rsd0c > 1+0 records in > 0+= records out > 0 bytes tranferred in 0.000 secs (0 bytes/sec) > ahci0: attempting to idle device > atascsi_disk_sync_done: error /rsd0* - same /sd0* - same /sd0 - dd works fine, but after writing the MBR (fdisk -i sd0) errors again :/ I even tried a fresh install process to use, but got the same... What the hell is wrong with this ssd? 2017-01-21 8:08 GMT+03:00 Asbel Kiprop : > Hi Nick! > > > I'd start by seeing if there are any firmware updates > ooowkey, im kinda confused, but there is no openbsd related firmwares > lmao http://www.goplextor.com/Support/Downloads > > > Boot from a bsd.rd, and > > # dd if=/dev/zero bs=1m of=/dev/rsdXc > I'll try it after work! > > 2017-01-21 7:26 GMT+03:00 Nick Holland : > >> On 01/20/17 21:21, Asbel Kiprop wrote: >> > Hi! >> > I got new Plextor ssd disk >> > root :: /home/ME : dmesg | grep sd0 >> > sd0 at scsibus1 targ 0 lun 0: SCSI3 >> 0/direct >> > fixed naa.5002303100b98e54 >> > sd0: 244198MB, 512 bytes/sector, 500118192 sectors, thin >> ... >> > But now: >> > >> > newfs sd0a >> > /dev/rsd0a: 5122.2MB in 10490368 sectors of 512 bytes >> > 26 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each >> > super-block backups (for fsck -b #) at: >> > newfs: wtfs: write error on block 32: Input/output error >> > >> > and this in dmesg: >> > ahci0: attempting to idle device >> > atascsi_disk_sync_done: error >> > >> > >> > What is my problem? >> >> Got me, so far you seem to be a reasonable person, and you include a >> dmesg with your problem report, so how horrible can you be? :) >> >> oh, the disk. right. sorry. >> >> Well... I'd start by seeing if there are any firmware updates for your >> SSD from the manufacturer. Seems to be that SSDs and "enterprise grade" >> disks are big on needing firmware updates. Hopefully, my sarcastic and >> snarky tone over "ship first, engineer later" design was conveyed. >> >> After that ... you might want to try writing something to the entire >> disk before using it. Boot from a bsd.rd, and >># dd if=/dev/zero bs=1m of=/dev/rsdXc >> This may help pre-lock-out any bad spots before trying to use them. >> (and yes, it says "write error", but on a file system, a write is often >> preceded by a read, and if the read fails, the write will be unable to >> be relocated. Or maybe I'm the one with problems.) >> >> I'm not convinced this will help you, but it has helped me. Really >> seemed to settle down some SSDs that I'd been fighting with. >> >> Nick.
Re: adding new disk
After changing SATA mode to "compatibility ": pciide0:0:0 bus-master DMA error: status=0x26 wd0: transfer error, downgrading to Ultra-DMA mode 1 wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 1 wd0k: aborted command, interface CRC error writing fsbn 64 of 64-191(wd0 bn 104568640; cn 6509 tn 24 sn 43), retrying wd0k: device timeout writing fsbn 64 of 64-191(wd0 bn 104568640; cn 6509 tn 24 sn 43), retrying etc Okay, as i understood my new SSD kinda BROKEN? 2017-01-21 19:13 GMT+03:00 Asbel Kiprop : > Unfortunately nothing helped. > > > # dd if=/dev/zero bs=1m of=/dev/rsd0c > > 1+0 records in > > 0+= records out > > 0 bytes tranferred in 0.000 secs (0 bytes/sec) > > ahci0: attempting to idle device > > atascsi_disk_sync_done: error > > /rsd0* - same > /sd0* - same > /sd0 - dd works fine, but after writing the MBR (fdisk -i sd0) errors > again :/ > I even tried a fresh install process to use, but got the same... > What the hell is wrong with this ssd? > > 2017-01-21 8:08 GMT+03:00 Asbel Kiprop : > >> Hi Nick! >> >> > I'd start by seeing if there are any firmware updates >> ooowkey, im kinda confused, but there is no openbsd related firmwares >> lmao http://www.goplextor.com/Support/Downloads >> >> > Boot from a bsd.rd, and >> > # dd if=/dev/zero bs=1m of=/dev/rsdXc >> I'll try it after work! >> >> 2017-01-21 7:26 GMT+03:00 Nick Holland : >> >>> On 01/20/17 21:21, Asbel Kiprop wrote: >>> > Hi! >>> > I got new Plextor ssd disk >>> > root :: /home/ME : dmesg | grep sd0 >>> > sd0 at scsibus1 targ 0 lun 0: SCSI3 >>> 0/direct >>> > fixed naa.5002303100b98e54 >>> > sd0: 244198MB, 512 bytes/sector, 500118192 sectors, thin >>> ... >>> > But now: >>> > >>> > newfs sd0a >>> > /dev/rsd0a: 5122.2MB in 10490368 sectors of 512 bytes >>> > 26 cylinder groups of 202.47MB, 12958 blocks, 25984 inodes each >>> > super-block backups (for fsck -b #) at: >>> > newfs: wtfs: write error on block 32: Input/output error >>> > >>> > and this in dmesg: >>> > ahci0: attempting to idle device >>> > atascsi_disk_sync_done: error >>> > >>> > >>> > What is my problem? >>> >>> Got me, so far you seem to be a reasonable person, and you include a >>> dmesg with your problem report, so how horrible can you be? :) >>> >>> oh, the disk. right. sorry. >>> >>> Well... I'd start by seeing if there are any firmware updates for your >>> SSD from the manufacturer. Seems to be that SSDs and "enterprise grade" >>> disks are big on needing firmware updates. Hopefully, my sarcastic and >>> snarky tone over "ship first, engineer later" design was conveyed. >>> >>> After that ... you might want to try writing something to the entire >>> disk before using it. Boot from a bsd.rd, and >>># dd if=/dev/zero bs=1m of=/dev/rsdXc >>> This may help pre-lock-out any bad spots before trying to use them. >>> (and yes, it says "write error", but on a file system, a write is often >>> preceded by a read, and if the read fails, the write will be unable to >>> be relocated. Or maybe I'm the one with problems.) >>> >>> I'm not convinced this will help you, but it has helped me. Really >>> seemed to settle down some SSDs that I'd been fighting with. >>> >>> Nick.
Re: touchscreen on advantech PPC-3100
On Fri, 20 Jan 2017 20:04:07 +0100 Benjamin Baier wrote: > On Fri, 20 Jan 2017 11:37:10 +0100 > Marko Cupać wrote: > > > On Fri, 20 Jan 2017 10:47:27 +0100 > > ludovic coues wrote: > > > > > xtsscale might help with the calibration process > > > > Thank you, hope I get to this part. Right now it appears I don't > > have any touchscreen functionality on this model. > > "PNP0F03" at acpi0 not configured > No driver yet. > Damn, I bought two of these for testing, and so far I couldn't make touchscreen work on either OpenBSD, FreeBSD, Ubuntu Linux and Linux Mint. It works on Windows 7 with proprietary driver installed. I can't return those boxes, so for now my only option is to buy two Windows 7 licenses. If there was someone who could write touchscreen drivers for OpenBSD I'd rather give money for that instead, feel free to contact me off-list. Regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
