> wireless > Does it work after the installation? The installation media is supposed
I don't think so. The device is recognized. ifconfig reports stuff. I think I even got a DHCP address, but can't ping anything. I haven't setup wireless with OpenBSD in a while, so I might be doing something wrong. I do have it working on a macppc machine currently and used to have it on a sparc64 (switched to wired). > This is vecause you copied boot, bsd and bsd.rd to the root of the Aha. And "boot" varies, per configuration? The one I put there might not be correct? Thank you. I'll try again. > load code from an ext2fs partition, so the boot code can simply be > copied there instead of needing a special tool to put it on a magic area Is the boot code a constant file, or does it vary per install/config? That is..the one I put there, isn't already correct? Anyway, thank you, I'll try again with an empty ext2 partition, and see what the installer does. I should have copied the install files somewhere, downloading them repeatedly now (twice already, I can wait, but I'm wasting bandwidth). - Jay ---------------------------------------- > Date: Sat, 24 Jul 2010 17:07:26 +0000 > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: Re: trouble autobooting loongson on gdium? > > > Wireless network didn't work during setup. I used wireless. > > The device was recognized. ifconfig let me fiddle with it. > > It gets a DHCP address, but that's it. > > Maybe my local network. I have OpenBSD/macppc > > working wireless, but maybe I forgot how. > > Anyway, ok, move on. > > Does it work after the installation? The installation media is supposed > to have all the required firmware files, but one might have been > forgotten. > > > The instructions are a bit lacking if you have a completely > > empty USB key. The installer doesn't seem to handle this well. > > It seemed to create an ext2 partition, but it was too small I think. > > You are right. This has been fixed post release. > > > I couldn't figure out how to create the ext2 partition and file > > system in OpenBSD. > > The installer uses ``newfs -t ext2fs -O 1 -b 4096'' on gdium (the O and > b options are used to circumvent shortcomings in the PMON ext2fs code). > > > At the end of setup, I get an error: > > mkdir /mnt2/boot failed > > Won't be able to boot from sd1. > > > > > > /mnt2/boot is a file. > > This is vecause you copied boot, bsd and bsd.rd to the root of the > ext2fs partition. The installer (and the documentation) expect these > files to be in the boot/ subdirectory. > > > PMON> set al /dev/fs/e...@usbg0/boot/boot > > PMON> set rd /dev/fs/e...@usbg0/boot/bsd > > > > > > are a bit confusing and unclear to me. > > > > After I set the variables, then what? > > If you have the files in the root of the ext2fs partition, you will need > to adjust the path first: > PMON> set al /dev/fs/e...@usbg0/boot > PMON> set rd /dev/fs/e...@usbg0/bsd > > > Power cycle and it should autoboot? > > Yes. > > > What worked I think: > > > > load /dev/fs/e...@usb0/bsd > > g > > This will boot a kernel, but it will ask for its root device everytime > (which is why the boot loader is preferred over direct boot from PMON). > > > There's apparently no installboot here. > > No, there isn't. The bastardized PMON shipped on these machines can only > load code from an ext2fs partition, so the boot code can simply be > copied there instead of needing a special tool to put it on a magic area > on the disk. > > Miod
