Need help installing 6.3 to Acer Aspire with eMMC drive; sdmmc troubles

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Need help installing 6.3 to Acer Aspire with eMMC drive; sdmmc troubles

Nathan Clement
Hello,
I am new to OpenBSD, installing for the first time to an Acer Aspire
ES1-111M. The only internal drive it has is a 32GB eMMC card.
I have used dd to get install63.fs on a usb drive, and it boots fine.
However, the installer reports sd0 as 1024M, so naturally the partition
table it devises is no good.
When I check dmesg (which I have no way to save as I am in the
install medium?) I see the messages:

sdmmc0: can't re-read EXT_CSD
sdmmc0: mem init failed
scsibus0 at sdmmc0: 2 targets, initiator 0
scsibus0 targ 1 lun 0: <SD/MMC, HBG4e\\005, 0000> SCSI2 0/direct removable
sd0: 1024MB, 512 bytes/sector, 2097152 sectors

I am booting in UEFI mode, but the results were the same when I used
my BIOS' "Legacy" mode. disklabel also returns the same size, but
when I run fdisk on /dev/sd0c it says it can't read sector 0.
What should I do?
Thanks,
Nathan
Reply | Threaded
Open this post in threaded view
|

Re: Need help installing 6.3 to Acer Aspire with eMMC drive; sdmmc troubles

Maurice McCarthy-3
On 14/10/2018, Nathan Clement <[hidden email]> wrote:

> Hello,
> I am new to OpenBSD, installing for the first time to an Acer Aspire
> ES1-111M. The only internal drive it has is a 32GB eMMC card.
> I have used dd to get install63.fs on a usb drive, and it boots fine.
> However, the installer reports sd0 as 1024M, so naturally the partition
> table it devises is no good.
> When I check dmesg (which I have no way to save as I am in the
> install medium?) I see the messages:
>
> sdmmc0: can't re-read EXT_CSD
> sdmmc0: mem init failed
> scsibus0 at sdmmc0: 2 targets, initiator 0
> scsibus0 targ 1 lun 0: <SD/MMC, HBG4e\\005, 0000> SCSI2 0/direct removable
> sd0: 1024MB, 512 bytes/sector, 2097152 sectors
>
> I am booting in UEFI mode, but the results were the same when I used
> my BIOS' "Legacy" mode. disklabel also returns the same size, but
> when I run fdisk on /dev/sd0c it says it can't read sector 0.
> What should I do?
> Thanks,
> Nathan
>

Hi

Can't help with your problem but to get the dmesg I'd do something like this:

1. Drop to a shell in the installer (I think it is type in "!")
2. Plug in a fat32-formatted usb and note its device name, say sd1
3. cd to /dev and do chmod +x MAKEDEV
4. run ./MAKEDEV sd1 to create the device files.
5. mount_msdos /dev/sd1i /mnt2 (create the directory if necessary)
6. cat dmesg > /mnt2 and post it in.

Notes: The ramdisk is small so _don't_ do MAKEDEV all
            None system partitions always start from the letter i

Good Luck

Reply | Threaded
Open this post in threaded view
|

Re: Need help installing 6.3 to Acer Aspire with eMMC drive; sdmmc troubles

Nathan Clement
Thank you, Maurice!
Now at least I have dmesg, and also the output of disklabel:

> dmesg:

OpenBSD 6.3 (RAMDISK_CD) #98: Sat Mar 24 14:26:39 MDT 2018
    [hidden email]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 2007171072 (1914MB)
avail mem = 1942614016 (1852MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x78165000 (22 entries)
bios0: vendor Insyde Corp. version "V1.03" date 07/22/2014
bios0: Acer Aspire ES1-111M
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP UEFI MSDM HPET LPIT APIC MCFG SSDT SSDT SSDT SSDT
SSDT UEFI SSDT CSRT SSDT FPDT BGRT
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU N2840 @ 2.16GHz, 2167.08 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,SMEP,ERMS,SENSOR,ARAT,MELTDOWN
cpu0: 1MB 64b/line 16-way L2 cache
cpu0: apic clock running at 83MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec00000, version 20, 87 pins
, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus 2 (RP02)
acpiprt3 at acpi0: bus 3 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiec0 at acpi0
acpicpu at acpi0 not configured
acpipwrres at acpi0 not configured
acpitz at acpi0 not configured
"INT3396" at acpi0 not configured
"10250933" at acpi0 not configured
"PNP0C14" at acpi0 not configured
"PNP0C0C" at acpi0 not configured
"PNP0C0E" at acpi0 not configured
bytgpio0 at acpi0: GPO0 uid 1 addr 0xfed0c000/0x1000 irq 49, 102 pins
bytgpio1 at acpi0: GPO1 uid 2 addr 0xfed0d000/0x1000 irq 48, 28 pins
bytgpio2 at acpi0: GPO2 uid 3 addr 0xfed0e000/0x1000 irq 50, 44 pins
sdhc0 at acpi0: SDHD addr 0x90a02000/0x1000 irq 44
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
"80860F16" at acpi0 not configured
"INTL9C60" at acpi0 not configured
dwiic0 at acpi0: I2C1 addr 0x90a07000/0x1000 irq 32
iic0 at dwiic0
ihidev0 at iic0 addr 0x2c irq 67, vendor 0x6cb product 0x2991, SYN1B7D
ihidev0: 14 report ids
hid at ihidev0 reportid 2 not configured
hid at ihidev0 reportid 3 not configured
hid at ihidev0 reportid 4 not configured
hid at ihidev0 reportid 6 not configured
hid at ihidev0 reportid 7 not configured
hid at ihidev0 reportid 8 not configured
hid at ihidev0 reportid 9 not configured
hid at ihidev0 reportid 10 not configured
hid at ihidev0 reportid 11 not configured
hid at ihidev0 reportid 12 not configured
hid at ihidev0 reportid 13 not configured
hid at ihidev0 reportid 14 not configured
"INT33BD" at acpi0 not confi#gured
"ACPI0003" at acpi0 not configured
"PNP0C0A" at acpi0 not configured
"PNP0C0D" at acpi0 not configured
"INT3401" at acpi0 not configured
"INT3400" at acpi0 not configured
"INT3403" at acpi0 not configured
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Bay Trail Host" rev 0x0e
"Intel Bay Trail Video" rev 0x0e at pci0 dev 2 function 0 not configured
xhci0 at pci0 dev 20 function 0 "Intel Bay Trail xHCI" rev 0x0e: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
3.00/1.00 addr 1
"Intel Bay Trail TXE" rev 0x0e at pci0 dev 26 function 0 not configured
"Intel Bay Trail HD Audio" rev 0x0e at pci0 dev 27 function 0 not configured
ppb0 at pci0 dev 28 function 0 "Intel Bay Trail PCIE" rev 0x0e: msi
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 1 "Intel Bay Trail PCIE" rev 0x0e: msi
pci2 at ppb1 bus 2
"Atheros AR9565" rev 0x01 at pci2 dev 0 function 0 not configured
ppb2 at pci0 dev 28 function 2 "Intel Bay Trail PCIE" rev 0x0e: msi
pci3 at ppb2 bus 3
re0 at pci3 dev 0 function 0 "Realtek 8168" rev 0x0c: RTL8168G/8111G
(0x4c00), msi, address c4:54:44:c0:98:6a
rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0
"Intel Bay Trail LPC" rev 0x0e at pci0 dev 31 function 0 not configured
"Intel Bay Trail SMBus" rev 0x0e at pci0 dev 31 function 3 not configured
isa0 at mainbus0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard
efifb0 at mainbus0: 1366x768, 32bpp
wsdisplay0 at efifb0 mux 1: console (std, vt100 emulation), using wskbd0
sdmmc0: can't re-read EXT_CSD
sdmmc0: mem init failed
scsibus0 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SD/MMC, HBG4e\\005, 0000> SCSI2 0/direct
removable
sd0: 1024MB, 512 bytes/sector, 2097152 sectors
umass0 at uhub0 port 1 configuration 1 interface 0 "SanDisk Cruzer Glide"
rev 2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus1 at umass0: 2 targets, initiator 0
sd1 at scsibus1 targ 1 lun 0: <SanDisk, Cruzer Glide, 1.00> SCSI4 0/direct
removable serial.07815575110709116593
sd1: 14664MB, 512 bytes/sector, 30031872 sectors
uhub1 at uhub0 port 2 configuration 1 interface 0 "vendor 0x05e3 USB2.0
Hub" rev 2.00/85.37 addr 3
"vendor 0x0489 product 0xe078" rev 1.10/0.01 addr 4 at uhub1 port 1 not
configured
"Chicony Electronics Co.,Ltd. HD WebCam" rev 2.00/28.57 addr 5 at uhub0
port 4 not configured
softraid0 at root
scsibus2 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
umass1 at uhub1 port 2 configuration 1 interface 0 "Samsung Flash Drive"
rev 2.10/11.00 addr 6
umass1: using SCSI over Bulk-Only
scsibus3 at umass1: 2 targets, initiator 0
sd2 at scsibus3 targ 1 lun 0: <Samsung, Flash Drive, 1100> SCSI4 0/direct
removable serial.090c1000117120008081
sd2: 122400MB, 512 bytes/sector, 250675200 sectors

> disklabel /dev/sd0c

# /dev/sd0c:
type: SCSI
disk: SCSI disk
label: SD/MMC HBG4e
duid: 0000000000000000
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 130
total sectors: 2097152
boundstart: 0
boundend: 2097152
drivedata: 0

16 partitions:
#                size           offset  fstype [fsize bsize   cpg]
  c:          2097152                0  unused
 #
and finally #
>fdisk /dev/rsd0c

fdisk: Can't read sector 0!

Any idea, misc, what is happening to my emmc drive?

On Mon, Oct 15, 2018 at 7:02 AM Maurice McCarthy <[hidden email]>
wrote:

> On 14/10/2018, Nathan Clement <[hidden email]> wrote:
> > Hello,
> > I am new to OpenBSD, installing for the first time to an Acer Aspire
> > ES1-111M. The only internal drive it has is a 32GB eMMC card.
> > I have used dd to get install63.fs on a usb drive, and it boots fine.
> > However, the installer reports sd0 as 1024M, so naturally the partition
> > table it devises is no good.
> > When I check dmesg (which I have no way to save as I am in the
> > install medium?) I see the messages:
> >
> > sdmmc0: can't re-read EXT_CSD
> > sdmmc0: mem init failed
> > scsibus0 at sdmmc0: 2 targets, initiator 0
> > scsibus0 targ 1 lun 0: <SD/MMC, HBG4e\\005, 0000> SCSI2 0/direct
> removable
> > sd0: 1024MB, 512 bytes/sector, 2097152 sectors
> >
> > I am booting in UEFI mode, but the results were the same when I used
> > my BIOS' "Legacy" mode. disklabel also returns the same size, but
> > when I run fdisk on /dev/sd0c it says it can't read sector 0.
> > What should I do?
> > Thanks,
> > Nathan
> >
>
> Hi
>
> Can't help with your problem but to get the dmesg I'd do something like
> this:
>
> 1. Drop to a shell in the installer (I think it is type in "!")
> 2. Plug in a fat32-formatted usb and note its device name, say sd1
> 3. cd to /dev and do chmod +x MAKEDEV
> 4. run ./MAKEDEV sd1 to create the device files.
> 5. mount_msdos /dev/sd1i /mnt2 (create the directory if necessary)
> 6. cat dmesg > /mnt2 and post it in.
>
> Notes: The ramdisk is small so _don't_ do MAKEDEV all
>             None system partitions always start from the letter i
>
> Good Luck
>
Reply | Threaded
Open this post in threaded view
|

Re: Need help installing 6.3 to Acer Aspire with eMMC drive; sdmmc troubles

Stuart Henderson
On 2018-10-15, Nathan Clement <[hidden email]> wrote:
> Thank you, Maurice!
> Now at least I have dmesg, and also the output of disklabel:
>
>> dmesg:
>
> OpenBSD 6.3 (RAMDISK_CD) #98: Sat Mar 24 14:26:39 MDT 2018

Try a snapshot (or 6.4). Not sure if it will help but there were some
fixes to sdmmc since 6.3.


Reply | Threaded
Open this post in threaded view
|

Re: Need help installing 6.3 to Acer Aspire with eMMC drive; sdmmc troubles

Nathan Clement
> Try a snapshot (or 6.4). Not sure if it will help but there were some
> fixes to sdmmc since 6.3.

No dice.
I tried using install64.fs, but still it tells me of some mythical 1024MB
drive "sd0",
of which fdisk "can't read sector 0". Using 6.4 did get me a few more lines
about
sdhc:

sdhc0 at acpi0 SDHD addr 0x90a02000/0x1000 irq 44
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
sdhc1 at acpi0 SDHC addr 0x90a00000/0x1000 irq 47, gpio
sdhc1: SDHC 3.0, 100 MHz base clock
sdmmc1 at sdhc1: 4-bit, sd high-speed, mmc high-speed, dma

The lines about sdhc1 and sdmmc1 are new, not there in 6.3's dmesg.

This seems very strange to me.
How is the system just inventing a drive exactly 1.0GB? I have no such
drive,
I swear. What does it indicate that fdisk can't read sector 0?

I never got the understanding from the install faq that I would need to
pre-format my drive in any way. Is that correct?
Thanks for any advice!
Reply | Threaded
Open this post in threaded view
|

Re: Need help installing 6.3 to Acer Aspire with eMMC drive; sdmmc troubles

Stuart Henderson
On 2018/10/15 19:27, Nathan Clement wrote:

> > Try a snapshot (or 6.4). Not sure if it will help but there were some
> > fixes to sdmmc since 6.3.
>
> No dice.
> I tried using install64.fs, but still it tells me of some mythical 1024MB drive "sd0",
> of which fdisk "can't read sector 0". Using 6.4 did get me a few more lines about
> sdhc:
>
> sdhc0 at acpi0 SDHD addr 0x90a02000/0x1000 irq 44
> sdhc0: SDHC 3.0, 200 MHz base clock
> sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
> sdhc1 at acpi0 SDHC addr 0x90a00000/0x1000 irq 47, gpio
> sdhc1: SDHC 3.0, 100 MHz base clock
> sdmmc1 at sdhc1: 4-bit, sd high-speed, mmc high-speed, dma
>
> The lines about sdhc1 and sdmmc1 are new, not there in 6.3's dmesg.
>
> This seems very strange to me.
> How is the system just inventing a drive exactly 1.0GB? I have no such drive,
> I swear. What does it indicate that fdisk can't read sector 0?
>
> I never got the understanding from the install faq that I would need to
> pre-format my drive in any way. Is that correct?
> Thanks for any advice!

I think this basically means that there's something about your hardware
which isn't supported by the sdhc/sdmmc subsystem in OpenBSD, but (though
I'm no expert in the area) it feels like it probably doesn't give enough
information to point out a direction to look next.

I'd suggest installing to a USB drive instead. After booting that, collect
information from sendbug(1) to make a bug report (often simplest done by
running "sendbug -P > /tmp/sendbug.txt" and then sending the file from a
normal email client to [hidden email] with a description of what happens -
please run sendbug as root to get more information).

Not sure how familiar you are with OpenBSD, but if you can get it installed
as above and build a kernel with SDMMC_DEBUG defined, it's likely that would
get information that would have a higher chance of helping people who know
more about that area to track it down..

Reply | Threaded
Open this post in threaded view
|

Re: Need help installing 6.3 to Acer Aspire with eMMC drive; sdmmc troubles

Nathan Clement
> I'd suggest installing to a USB drive instead. After booting that, collect
> information from sendbug(1) to make a bug report (often simplest done by
> running "sendbug -P > /tmp/sendbug.txt" and then sending the file from a
> normal email client to [hidden email] with a description of what
happens -
> please run sendbug as root to get more information).

Thank you for the suggestion, Stuart! That was fun, but now the plot gets
thicker.
I installed 6.3 to a usb stick, but when I reboot into the install, my
eMMC is suddenly showing up as 29GB, as it should.

Should I try somehow manually installing from my openbsd install on the usb
to the eMMC? That seems convoluted but possibly fun.

Here are the sdmmc related lines from dmesg in the install environment:


sdhc0 at acpi0: SDHD addr 0x90a02000/0x1000 irq 44
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
...
sdmmc0: can't re-read EXT_CSD
sdmmc0: mem init failed
scsibus0 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <SD/MMC, HBG4e\\005, 0000> SCSI2 0/direct
removable
sd0: 1024MB, 512 bytes/sector, 2097152 sectors


And after installing to usb dmesg:


sdhc0 at acpi0: SDHD addr 0x90a02000/0x1000 irq 44
sdhc0: SDHC 3.0, 200 MHz base clock
sdmmc0 at sdhc0: 8-bit, sd high-speed, mmc high-speed, dma
...
sdhc_sdclk_frequency_select: command in progress
scsibus1 at sdmmc0: 2 targets, initiator 0
sd0 at scsibus1 targ 1 lun 0: <SD/MMC, HBG4e\\005, 0000> SCSI2 0/direct
removable
sd0: 29824MB, 512 bytes/sector, 61079552 sectors

So I'm not seeing the same error from my usb install of 6.3, and
am getting access to the full eMMC. Fdisk could see the whole thing.
I probably could have re-partitioned it.

Presumably my sendbug PR isn't worth much since the problem wasn't
happening in that system?

-Nathan