OESF Portables Forum
Everything Else => Zaurus Distro Support and Discussion => Distros, Development, and Model Specific Forums => Archived Forums => OpenBSD => Topic started by: mathemajikian on March 18, 2007, 10:07:53 pm
-
And here it is! The moment we've all been waiting for:
$ dmesg
OpenBSD 4.1-current
pxammc0 at pxaip0: MMC/SD/SDIO controller
sdmmc0 at pxammc0
scsibus0 at sdmmc0: 2 targets
sd0 at scsibus0 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed
sd0: 14MB, 14 cyl, 64 head, 32 sec, 512 bytes/sec, 29120 sec total
Now OpenBSD based Z's can utilize the on board sd slot!
-
Great news! Is there any advancement on bluetooth front?
-albertr
-
That's great news. Does this mean that the C1000 will be a supported model now? I would love to try this on mine using my 4GB SD card.
-
That's great news. Does this mean that the C1000 will be a supported model now? I would love to try this on mine using my 4GB SD card.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156681\"][{POST_SNAPBACK}][/a][/div]
I'm going to see about running OpenBSD off an SD card. I'll post setup instructions if it works. Might take me a little while to complete since I'm undergoing numerous college courses at the moment.
-
Full (SD Booting, CF Extension Cards) OpenBSD support for C1000 will be great! Then my whole computers runs on Openbsd
What were the steps to do this?
Booting Openbsd from CF Card and try to take the installdrive sd0 (SD Card)? Or is it much complex?
greets
Andi
-
Full (SD Booting, CF Extension Cards) OpenBSD support for C1000 will be great! Then my whole computers runs on Openbsd
What were the steps to do this?
Booting Openbsd from CF Card and try to take the installdrive sd0 (SD Card)? Or is it much complex?
greets
Andi
I think all you'll need to do is create an image of your current Z's partitions onto a SD card. (You'll also have to edit /etc/fstab) Then recompile and install a kernel with the following changes:
config bsd root on wd0a to --> config bsd root on sd0a
Make sure and install the new kernel to the root partition of your current CF install and SD image. Don't delete the old kernel because if this doesn't work then you'll need it to reboot your system. So before installing the new kernel cp /bsd /bsd.bak and then after installing the new kernel rename the sd-root kernel as sdbsd, ie mv /bsd /sdbsd. Boot this kernel instead of the normal bsd kernel, ie at the boot prompt type:
boot> boot wd0a:/sdbsd
Note I have not tried this yet; hence, if you ruin your install don't blame me. However, I'm pretty sure this will work.
-
Great news!
So, apart from pxa270 SRAM support (video accel) which I would presume isn't done yet, is their anything else missing from the Zaurus OpenBSD kernel that a sharp rom/pdax user may expect to work? I'm not bothered about bluetooth personally.
Does it have working support for USB host on the cxxxx?
-
Does it have working support for USB host on the cxxxx?
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=156704\")
Enable usbf(4) and cdcef(4) on Zaurus: [a href=\"http://www.openbsd.org/plus41.html]http://www.openbsd.org/plus41.html[/url]
USBF(4) OpenBSD Programmer's Manual USBF(4)
NAME
usbf - introduction to Universal Serial Bus function support
SYNOPSIS
usbf* at pxaudc? # zaurus
cdcef* at usbf?
DESCRIPTION
OpenBSD provides machine-independent bus support and drivers for Univer-
sal Serial Bus (USB) functions, making it possible in principle for ma-
chines running OpenBSD to act as USB device to a USB host.
The OpenBSD usbf driver has three layers: the controller, the logical de-
vice, and the function layer. The controller attaches to a physical bus.
The logical device attaches to the controller and the function attaches
to the logical device.
Function drivers implement the characteristics of a particular USB device
class that the USB host will see when the device is connected to the bus.
Bluetooth devices work, but we are still lacking a communication protocol. It's in the works. NAND flash memory should be coming soon as can be seen from:
flash0 at pxaip0: Samsung K9F1G08U0A 128Mx8 3.3V
-
and about SDIO,
does it open us a way to true SDIO controllers like SDIO GPS or SDIO WLAN cards ???
-
Great!!! Have you test any 4g SD?!?
Thnx
-
Great!!! Have you test any 4g SD?!?
Thnx
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156797\"][{POST_SNAPBACK}][/a][/div]
I only have a 2GB card to test, but I don't see any reason why you couldn't use a 4GB SD card. (This isn't a Linux ROM )
-
i just gave 4.1 a whirl on my C1000, and install fails. The SD card isn't found and dmesg doesn't show
pxammc0 at pxaip0: MMC/SD/SDIO controller. I have been running obsd on a CF card, and I was looking forward to getting rid of my usb ethernet adapter and switching to a CF wifi card...
-
Great!!! Have you test any 4g SD?!?
Thnx
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156797\"][{POST_SNAPBACK}][/a][/div]
I only have a 2GB card to test, but I don't see any reason why you couldn't use a 4GB SD card. (This isn't a Linux ROM )
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156799\"][{POST_SNAPBACK}][/a][/div]
I just spoke to Uwe concerning this and here's what he had to say:
I have used a 4GB card in my laptop with sdhc(4), but not yet on the Zaurus.
The controller should not make a difference though.
The main difference, afaik, between small and large SD memory cards is that
they encode the block size in the card information structure differently.
Hence, there shouldn't be any issues in utilizing larger capacity SD cards.
-
i just gave 4.1 a whirl on my C1000, and install fails. The SD card isn't found and dmesg doesn't show pxammc0 at pxaip0: MMC/SD/SDIO controller. I have been running obsd on a CF card, and I was looking forward to getting rid of my usb ethernet adapter and switching to a CF wifi card...
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=156800\")
How did you install? If you just went and downloaded 4.1-release sources then this is understandable. The SD driver support was only added two days ago. To gain SD support your going to have to update your 4.1-release system via cvs to 4.1-current. Follow the cvs update instructions found on this page to update your Z to 4.1-current: [a href=\"http://exit3.i-55.com/%7Exikon/ZaurusUpgrade.html]Zaurus updating[/url]
Furthermore, trying to run/install OpenBSD off/on an SD card will require a little ingenuity. (See my earlier post) (https://www.oesf.org/forums/index.php?showtopic=23517&view=findpost&p=156703) This is mainly due to the limits of the current bootloader. Quoting Uwe once again The current standalone boot program doesn't know about "sd" or "wd" disks. All it has is "hd" devices, which map (in a non-intuitive way) to the linux devices /dev/hda, /dev/hdc, etc.
I'm going to try and get BSD running off an SD card later this week. I'll post my results.
-
Thanks I was taking it one step at a time. I just wanted to see the dmesg for the first time. I might try the CVS version later, thanks for pointing that out.
-
Running OpenBSD off an SD card isn't going to happen just yet. The driver is very buggy and is going to require a lot of tweaking.
-
Running OpenBSD off an SD card isn't going to happen just yet. The driver is very buggy and is going to require a lot of tweaking.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157126\"][{POST_SNAPBACK}][/a][/div]
do you mean the driver is buggy for using openbsd off an sdcard OR is it buggy for a common usage (only for storage) ???
-
Running OpenBSD off an SD card isn't going to happen just yet. The driver is very buggy and is going to require a lot of tweaking.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157126\"][{POST_SNAPBACK}][/a][/div]
do you mean the driver is buggy for using openbsd off an sdcard OR is it buggy for a common usage (only for storage) ???
[div align=\"right\"][a href=\"index.php?act=findpost&pid=157325\"][{POST_SNAPBACK}][/a][/div]
both.
-
Great!!! Have you test any 4g SD?!?
Thnx
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156797\"][{POST_SNAPBACK}][/a][/div]
I only have a 2GB card to test, but I don't see any reason why you couldn't use a 4GB SD card. (This isn't a Linux ROM )
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156799\"][{POST_SNAPBACK}][/a][/div]
I just spoke to Uwe concerning this and here's what he had to say:
I have used a 4GB card in my laptop with sdhc(4), but not yet on the Zaurus.
The controller should not make a difference though.
The main difference, afaik, between small and large SD memory cards is that
they encode the block size in the card information structure differently.
Hence, there shouldn't be any issues in utilizing larger capacity SD cards.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156801\"][{POST_SNAPBACK}][/a][/div]
I have an Apacer 4GB 150x SD.
dmesg reads:
scsibus0 at sdmmc0: 2 targets
sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct fixed
sd0: 3926MB, 125 cyl, 255 head, 63 sec, 2048 bytes/sec, 2010112 sec totalhotplug the card shows:
pxammc0: unhandled interrupt 1
mount_ffs: /dev/sd0c on /mnt/card: Input/output error
-
Great!!! Have you test any 4g SD?!?
Thnx
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156797\"][{POST_SNAPBACK}][/a][/div]
I only have a 2GB card to test, but I don't see any reason why you couldn't use a 4GB SD card. (This isn't a Linux ROM )
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156799\"][{POST_SNAPBACK}][/a][/div]
I just spoke to Uwe concerning this and here's what he had to say:
I have used a 4GB card in my laptop with sdhc(4), but not yet on the Zaurus.
The controller should not make a difference though.
The main difference, afaik, between small and large SD memory cards is that
they encode the block size in the card information structure differently.
Hence, there shouldn't be any issues in utilizing larger capacity SD cards.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=156801\"][{POST_SNAPBACK}][/a][/div]
I have an Apacer 4GB 150x SD.
dmesg reads:
scsibus0 at sdmmc0: 2 targets
sd0 at scsibus0 targ 1 lun 0: SCSI2 0/direct fixed
sd0: 3926MB, 125 cyl, 255 head, 63 sec, 2048 bytes/sec, 2010112 sec totalhotplug the card shows:
pxammc0: unhandled interrupt 1
mount_ffs: /dev/sd0c on /mnt/card: Input/output error[div align=\"right\"][a href=\"index.php?act=findpost&pid=160204\"][{POST_SNAPBACK}][/a][/div]
hu!
you're not lucky with your zaurus devices under openbsd...
-
No, not at all.
Actually I am very happy to keep OpenBSD running on my 3200. One main reason for me to upgrade from C1000 is to run this standard distro. I am quite sure things will just get better but not broken further.
The 4GB card can go to the debian on my 860 for now, if I manage to get debian loaded off SD with the Angstrom kernel. I still have a much abused 1gb card that can hold sources, packages and various documents, besides the 6gb microdrive which provides quite an ample workspace. Today I also ordered an AmbiCom WL1100C-CF dedicated to this setup (the Symbol Spectrum24 CF is actually NOT supported according to http://www.openbsd.org/zaurus.html#hardware (http://www.openbsd.org/zaurus.html#hardware) ).
Despite some room for improvement (primarily SD support), I think with OpenBSD a Z can really become a genuine full-fledged *nix box and a great laptop replacement.
-
pxammc0: unhandled interrupt 1<DATADONE>
mount_ffs: /dev/sd0c on /mnt/card: Input/output error
Did you create a ffs partition on the SD card? Try and mount the card without hotplug. If it's a msdos file system then use mount_msdos /dev/sd0c /mnt/card.
-
pxammc0: unhandled interrupt 1<DATADONE>
mount_ffs: /dev/sd0c on /mnt/card: Input/output error
Did you create a ffs partition on the SD card? Try and mount the card without hotplug. If it's a msdos file system then use mount_msdos /dev/sd0c /mnt/card.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160213\"][{POST_SNAPBACK}][/a][/div]
It's ext2. I tried all the nodes and only sd0c would do, but it returns this error.
Reboot the system with the card inserted gives the same error.
-
It's ext2. I tried all the nodes and only sd0c would do, but it returns this error.
Reboot the system with the card inserted gives the same error.
Then try and use mount_ext2fs not mount_ffs.
-
It's ext2. I tried all the nodes and only sd0c would do, but it returns this error.
Reboot the system with the card inserted gives the same error.
Then try and use mount_ext2fs not mount_ffs.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160215\"][{POST_SNAPBACK}][/a][/div]
Now it's this:
#mount_ext2fs /dev/sd0c /mnt/card
mount_ext2fs: /dev/sd0c on /mnt/card: specified device does not match mounted device
while all other sd0x show "Device not configured"
-
It's ext2. I tried all the nodes and only sd0c would do, but it returns this error.
Reboot the system with the card inserted gives the same error.
Then try and use mount_ext2fs not mount_ffs.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160215\"][{POST_SNAPBACK}][/a][/div]
Now it's this:
#mount_ext2fs /dev/sd0c /mnt/card
mount_ext2fs: /dev/sd0c on /mnt/card: specified device does not match mounted device
while all other sd0x show "Device not configured"
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160217\"][{POST_SNAPBACK}][/a][/div]
Does the device have a disklabel as well as an fdisk partition table? if not the disklabel will be assumed as default.
Quite often expect to see msdos partitions on sd0i but as this is ext2 you should verify what has been assumed by using..
disklabel sd0
This should print out what OpenBSD thinks the partitions are.
Good Luck,
-Andy
-
Thanks, Andy!
Here is the output of disklabel sd0:
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: Drive #01
flags:
bytes/sector: 2048
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 125
total sectors: 2010112
rpm: 3600
interleave: 1
trackskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg]
c: 2010112 0 unused 0 0 # Cyl 0 - 125*
-
Thanks, Andy!
Here is the output of disklabel sd0:
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: Drive #01
flags:
bytes/sector: 2048
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 125
total sectors: 2010112
rpm: 3600
interleave: 1
trackskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg]
c: 2010112 0 unused 0 0 # Cyl 0 - 125*[div align=\"right\"][a href=\"index.php?act=findpost&pid=160295\"][{POST_SNAPBACK}][/a][/div]
Ok, here's the problem. The disklabel isn't defaulting based upon an ext2 partition and can't determine the beginning of the logical device to say where the ext2 partition starts.
c will ALWAYS exist if the OS can recognise the disk geometry since c is always the full raw disk area.
If you aren't too fussed about what is on the drive I would suggest that you run..
disklabel -E sd0
Then add a partition, possibly a, and set it up in the disklabel then make your ffs or ext2 filesystem from OpenBSD.
This all may seem a little wacky but UNIX folks still regard MSDOS partition tables as particularly PC'ish and like to rely on their own more portable partition information
Good luck,
-Andy
-
@ZDevil Do you use the SD-Card Function on your C1000 or C3200.
Is it in the meanwhile possible to run the Z from a SD Card?
I think the new snapshot for the Z includes the SD Device, but i will try it today or tomorrow if it recognise my SD ...
# Enable pxammc(4) and sdmmc(4) on Zaurus RAMDISK kernels too.
# Initial support for PXA27x SD/SDIO/MMC controller on the Zaurus platform.
Greets from Germany
Andi
-
@ZDevil Do you use the SD-Card Function on your C1000 or C3200.
Is it in the meanwhile possible to run the Z from a SD Card?
I think the new snapshot for the Z includes the SD Device, but i will try it today or tomorrow if it recognise my SD ...
# Enable pxammc(4) and sdmmc(4) on Zaurus RAMDISK kernels too.
# Initial support for PXA27x SD/SDIO/MMC controller on the Zaurus platform.
Greets from Germany
Andi
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160350\"][{POST_SNAPBACK}][/a][/div]
The SD card funcionality, as already reported in this thread, is rather flaky; only read and no write (write tends to hang the system). AFAIK booting off SD is not yet supported, so at this point C1000 cannot run obsd off SD. Also perhaps because things have to be extracted to the root partition and the system partitions have to be formatted in ffs during installation, but there is no SD write support so installing things to SD is not feasible. But maybe i am wrong here...
Still getting extremely busy with work so no free time block yet to backup the nearly full 4GB SD and reformat it under obsd.
-
Now i am trying to reformat the 4GB SD into ext2 and mount it under obsd.
Following Andy's suggestion,
first i used disklabel -E sd0
then choose "a" to add a device
after offset and size,
I am asked to assign an FS type.
The default is "4.2BSD".
I try "Ext2", "ext2", "Linux", but i am told that it is "Unrecognized filesystem type..., treating as 'unknown'"
Then I try "MSDOS", which is supported,
but when i try to save, i got this:
Write new label: [y]
disklabel: ioctl DIOCWDINFO: Input/output error
disklabel: unable to write label
-
Write new label: [y]
disklabel: ioctl DIOCWDINFO: Input/output error
disklabel: unable to write label
Read your last post and you'll see why this is occuring. Here's the quote:
there is no SD write support so installing things to SD is not feasible.
hence, changing the disklabel via the onboard SD slot is unsupported at the moment , Use a supported external SD reader/writer to change the disklabel. However, writing to the SD card will result in the same input/output error no matter what filesystem it has been formatted with.
-
If you aren't too fussed about what is on the drive I would suggest that you run..
disklabel -E sd0
Then add a partition, possibly a, and set it up in the disklabel then make your ffs or ext2 filesystem from OpenBSD.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160311\"][{POST_SNAPBACK}][/a][/div]
@Andy:
How to make ext2 using disklabel? I've tried ext2, Ext2, EXT2, Linux, LINUX, all these are invalid. The man page of disklabel doesn't mention ext2 at all.
Searching "ext2" in the Man page search and i only got fsck_ext2fs (8) and mount_ext2fs (8).
Any hint? Thanks!
-
If you aren't too fussed about what is on the drive I would suggest that you run..
disklabel -E sd0
Then add a partition, possibly a, and set it up in the disklabel then make your ffs or ext2 filesystem from OpenBSD.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=160311\"][{POST_SNAPBACK}][/a][/div]
@Andy:
How to make ext2 using disklabel? I've tried ext2, Ext2, EXT2, Linux, LINUX, all these are invalid. The man page of disklabel doesn't mention ext2 at all.
Searching "ext2" in the Man page search and i only got fsck_ext2fs (8) and mount_ext2fs (8).
Any hint? Thanks!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=161210\"][{POST_SNAPBACK}][/a][/div]
I have fdisked the 4gb SD under the dualboot Cacko. Tried both FAT and Ext2 but the card fails to be recognized under obsd.
disklabel sd0 says: /dev/rsd0c: Device not configured
fdisk sd0 says: sd0: Device not configured
So I turned to my Mac...
Just found e2fsprogs and installed it in my OBSD setup on Macbook@Parallels.
First I used disklabel -E sd0 to add a partition [a], then choose the BSD4.2 as FS type.
After that I used mke2fs to create an ext2 filesystem on this SD.
This SD can be detected and mounted in OBSD on my Mac.
disklabel sd0 shows two partitions, [c] and [a] (the newly created one).
The card can be detected and mounted in Cacko on my 3200.
But ...
The 4.1 official release doesn't seem to have SD support at all.
So I install the latest kernel (dated 8 May).
Reboot and now the SD is detected.
But ...
on my 3200, disklabel sd0 shows only [c], and no [a].
So, now the card can be read by Mac@OBSD, 3200@Cacko, but not 3200@OBSD!
What do i do?
Did I go wrong in the attempt?
Thanks!
-
It seems that the current SD support is rather picky. My 1gb FAT16 SD can be detected and mounted, but my 4gb FAT32/Ext2/Ext3 SD simply fails. Hope this will fixed soon.
-
Thanks, Andy!
Here is the output of disklabel sd0:
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: Drive #01
flags:
bytes/sector: 2048
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 125
total sectors: 2010112
rpm: 3600
interleave: 1
trackskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg]
c: 2010112 0 unused 0 0 # Cyl 0 - 125*[div align=\"right\"][a href=\"index.php?act=findpost&pid=160295\"][{POST_SNAPBACK}][/a][/div]
i've just tried my 4gb Transcend sdcard under latest openbsd GENERIC#113 and i have the same problem with the same disklabel output... however mine is fat formatted... no hope to mount it ?
-
Not sure if it is relevant. For cards bigger than 2gb it has to be FAT32. And for now OBSD's SD driver doesn't seem to like FAT32 at all.