I-Appliance BBS
The Official Source for Internet Appliance Upgrades and Mods
Amazon Honor System Click Here to Pay Learn More
BBS Main List | Sign In | Sign Up | Search | Help | Linux-Hacker.netReply to Thread | Printer |

Home / I-Opener Areas / I-Opener Technical Stuff
NetBSD 1.4 -> Midori SANDisk
OS migration from NetBSD SANDisk image to Midori

New MessageNetBSD 1.4 -> Midori SANDisk (modified 0 times) djmanning
Profile
hello all. I've had a v2 or v3 iopener running NetBSD 1.4 for a few years. The SANDisk has NetBSD v1.4 running on it. I added a 515 Mb drive that is also running the same NetBSD but recompiled to add USB Ethernet. No problems booting from either disk or Sandisk.

I've been following the discussion about Midori and how nice it is. I backed up the Sandisk, dumped the m4i-2.3pre1_winchip.img file to /dev/wd1d

It completed and I realized that I need to update the boot information to actually see the new image.
When I reboot, I can only choose my 515 Mb drive with the default Netbsd boot tools.

Any ideas on how to get:

some other boot loader or manager on the Iopener without cracking the case?
or
a way for the netbsd boot manager to load the Midori linux image

Thanks for any suggestions.

03-31-2004 11:00:04

New MessageRE:NetBSD 1.4 -> Midori SANDisk (modified 0 times) ztw4
Profile
If you upgrade to the latest BIOS version (540A) and set the boot sequence to "SMARTBOOT" I believe it'll boot from any drives present, except (sadly) for USB.

Of course you'll have to work out a way to flash the BIOS; easiest way I know is hooking up an IDE SuperDisk drive, then running the flash proggy from an MSDOS formatted floppy.

I'd definitely be interested in hearing more about your SANdisk NetBSD image, though. Nice to have a failsafe, and hate to have all that lovely bootable disk-on-chip going to waste. What packages did you cram in? And is there any chance I could get a copy of the image (shame on me for not doing it myself, I know, but I'm very new with NetBSD and short on time these days). Would be willing to reimburse your costs, or even trade some stuff. Lemme know.

03-31-2004 15:07:09

New MessageRE:NetBSD 1.4 -> Midori SANDisk (modified 0 times) djmanning
Profile
Thanks for the tip. I bought a new BIOS chip from BadFlash, chipped out the goo and now have a 5.40 Iopener running. No more Iopener boot logo or having to hit "Tab" to get to the OS.

I changed it to smartboot and for hd1 I get "Disk Error 0x01" so I probably didn't dump my midori image to the sandisk correctly. Anyone know the sequence for preparing the sandisk under Netbsd for a new image? I was pretty sure that I just needed to dump it to wd1d.

I used fdisk(Netbsd, not DOS) and disklabel before I dumped the image. I shouldn't have to newfs it, right?

As far as a copy of the sandisk image.. I dumped the image to /tmp and realized after I did the dump and reboot that /tmp is cleared after reboot :(

I have the same kernel running on the 515 Mb drive though. I can tar up what I've got. It's pretty stock. I recompiled the kernel once and added Netscape. This is some very old software. The kernel says 1.4Y. I use it mostly as an X-terminal and web client for some monitoring software at work.

I'll try to dump the Midori image to the sandisk again.

Thanks again for the help.

04-02-2004 19:39:13

New MessageRE:NetBSD 1.4 -> Midori SANDisk (modified 0 times) ztw4
Profile
Well, as coincidence would have it, I decided to install Midori this weekend as well. Unfortunately I'm more familiar with DOS, so I can't give you Linux/Unix command instructions. But I'll tell you what I did anyway, maybe it'll give you some idea.

I have a V2 w/flashed 540a BIOS, original Winchip, 64mb memory, running Win98SE on the hard disk, with a USB external case containing an old Mitsumi 2x CDR. Haven't gotten a network adapter for the IO yet, so I burned the image onto a CD from my desktop, along with Dolly 2.43 and Ranish Partition Manager (VERY useful little proggy), then copied them into the hard drive root directory.

Went into the IO's BIOS, configured the SANDisk (NORMAL mode, not LBA), then booted into Win98 "safe mode command line only" and used RPM to delete the partitions and repartition as type DOS. Got Dolly running after a few goes, flashed the image, went back into BIOS and changed to "D,A,SCSI" boot.

Damn thing booted to hard disk regardless, so I disconnected it and tried again. This time it started to boot Midori, but hung up right after playing the startup sound. So reconnected the hard disk, reflashed the image, disconnected the HD, rebooted, same hangup. Redid the partition to Linux and reflashed, same results.

Took fifteen minutes to vent my frustration in Hitman2 before returning to the project. Figured the Midori image got corrupted somehow (old CDR doesn't like some media), burned a NEW cd, copied the image and Dolly'd it again, and bingo! Lovely M4I desktop. Tried reconnecting the hard drive, and for whatever reason SMARTBOOT worked fine after I got the SANDisk to boot initially.

So if you use the same method, here's a few things I found out:

1. Ranish Partition Manager - you can choose either Linux or DOS as a partition type before flashing, far as I can tell
2. Dolly - command line is "dolly243 newimage.img HD129:" with no need to include the "/c" parameter (which you'd normally do for drive cloning bootable drive images)
3. Win98 - make sure you change the "read-only" attribute of the image file, as Dolly won't accept a "read-only" image. Any time you copy over an image from a CD in pre-Win2000, it retains the "read-only" attribute. Irritating as hell.

04-05-2004 12:40:58

New MessageRE:NetBSD 1.4 -> Midori SANDisk (modified 0 times) djmanning
Profile
Thanks for the play by play. My plan is to remove the hard disk, load the apps you listed and try writing the sandisk as you outlined.

I'll post how it goes and what works.

Thanks.

04-05-2004 16:34:23

New MessageRE:NetBSD 1.4 -> Midori SANDisk (modified 0 times) djmanning
Profile
I just finished loading the latest midori image with your help. It runs great. I have to keep the boot order at "D,A,SCSI" in order to get it to boot from SANdisk though. If I move it back to SMARTBOOT and choose the SANdisk, I still get "Disk Error 0x01" - but I can boot the disk drive.

I'll keep monkeying with it. Thanks!

04-08-2004 19:56:55

Reply to Thread | Printer |
All times are PSTPowered by UltraBoard v1.62



Copyright © 2000, Netmake Inc. All Rights Reserved.
See Terms and Conditions for more information.




i-opener opener laptop notebook computer help drivers dll free windows dos repair fix linux mac macintosh 2000 95 98 nt pc configure hardware software sound video netscape explorer network networking lan wan software cmos fat bios printer card mouse modem ide scsi cd rom controllers scanner tape hard drive cgi scripts source code mp3