Skip to main content

Installing Debian On ACER Altos 1200

Fiuh... one machine conquered! I will not discuss about the fiddling, struggling, and meddling parts (hmm... maybe just a 'little'), but let's take a look what's the insight.

I've got a funky machine, ACER Altos 1200 with the following specs:
- Memory 1536 MB
- RAID Controller AccelleRAID 362
- 6 SCSI [8,8,8,8,34,34] in RAIDs (1+0, 1).
- 2 Proc Pentium III

This thing made any debian based Installer (Etch and Hardy) failed to boot, rebooted with no reason. The machine didn't even bother to recognize OpenSolaris CD.

At first, I was thinking it was because of the VGA (Mach64) didn't do well. So, I did the "vga=771" option which resulted without luck. I even put off ACPI with "acpi=0ff", "noacpi", and "nolapic" combinations.
The problem was reproducible with different CDs and distros, so it was highly that this wasn't a CD problem. Knoppix also could boot although with a glitch about sometimes it only had one penguin detected. So, there was something else.

With my old unstable version of Debian Installer, I managed to have kernel panic with a clear problem: couldn't create RAMDISK for booting. After the problem found, I googled and found out that there was a posibility that different RAMs on board could confuse the kernel. From this point, there were 2 possible solutions:
  1. Take some of the RAM modules off so that the system only have one. This option is not viable for me, given the experience at the past that I had wrecked few servers (OK, I'm not that good with hardware).
  2. I found this later option in installation of Debian into SunFire machines. The thing is, you have to tell the installer how much the memory. So, I appended " mem=1536MB" option.
I booted with the following:
"expert mem=1536MB"

Why use expert, not standard installation? Well, because I'm an l33t... :D

Nah, the reason was because I would to make sure the installation went well. As my guess, there would be something wrong in the process which was installing the bootloader. None of GRUB and LILO could be installed. The problem was because the installer wouldn't recognize my RAID devices. It choked at funky name.

What's wrong anyway if the device is "/dev/rd/c0d0"?

So, I opened the second console and chrooted to /target (Debian's default mounted root directory) and trying to install manually LILO and GRUB. Because of laziness, which is a virtue according to Larry, I only managed to install GRUB. So, I choose GRUB because it probed my device well, this was its "/boot/grub/device.map" :
(hd0) /dev/rd/c0d0
(hd1) /dev/rd/c0d1
With that detected, I ran:
# update-grub

and then ran:
# grub-install /dev/rd/c0d0

and ignored all the warnings about funky device names.

and then I blogged it. Save house ahead.

Fin.
Labels:

Comments

  1. Anonymous12:51 PM

    coba gnewsense donk :D

    ReplyDelete
  2. Anonymous12:54 PM

    eh arsitekturnya apa tuh jep? 64-bit? ga ada harapan deh buat gnewsense klo selain x86 :(

    1337h4x indeed :D

    ReplyDelete
  3. refurbished computers2:30 PM

    I guess there would be something wrong while installing bootloader.

    ReplyDelete

Post a Comment

Popular posts from this blog

STAN vs. UI

Ugh, kasihan banget adek gue. Saking kepinteran dia jadi dapet Akuntansi UI dan STAN. Jadi bingung mau masuk yang mana. Beberapa orang (termasuk orang tua gue), menyarankan masuk STAN. Gue malah memperburuk suasana dengan membela memasuki Akuntansi UI, maklum bela almamater. Duh, gue jadi merasa bersalah bikin dia ragu-ragu. Kira-kira enakan masuk mana, yah? Gue juga gak tahu keuntungan masing-masing. Hasil debat sementara: ~ Untuk jangka panjang masuk UI, untuk jangka pendek STAN. ~~Tapi, dia itu kan cewek, ntar pas menikah kemungkinan besar karir terhambat. Eits, ntar, dulu, sekarang kan jamannya emansipasi, bisa aja cowoknya yang jadi BRT. ~ STAN sarang korupsi, kalo masuk STAN jadi pegawai negeri. Kalo mau kaya harus korupsi. Tapi kalo masuk UI, lulus masuk jadi akuntan publik. Sekarang ini, orang membayar akuntan publik untuk memanipulasi nilai pajak dan aset. *SIGH*. Jadi gak ada yang beres ~ dll. Yah, udah gue jadi bingung, apa lagi dia nanya saran gue. Buah, gue gak pengalaman ...
62 comments
Read more

Installing Goodix Fingerprint Reader Driver on Fedora

I currently have a Lenovo Thinkpad L14 laptop equipped with fingerprint. I was `belok` from KDE Neon to use Fedora 40 because of someone. Now I am tempted to enable my fingerprint: lsusb | grep -i fingerprint Bus 001 Device 004: ID 27c6:55b4 Shenzhen Goodix Technology Co.,Ltd. Fingerprint Reader Dump the firmware Assuming this is a fresh install, lets do some magic by getting some dependencies: sudo dnf install gcc git python-pip python-devel openssl Let's get the source code: git clone --recurse-submodules https://github.com/goodix-fp-linux-dev/goodix-fp-dump.git cd goodix-fp-dump Create an isolated Python environment: python -m venv .v source .v/bin/activate Do the magic: sudo su pip install -r requirements.txt python run_55b4.py exit There are some python scripts available. I run run_55b4.py because my device ID is 27c6: 55b4 . It will spell some nonsense, which is a good thing. That nonsense actually the firmware captured by our device. Also, I typed exit becaus...
2 comments
Read more

Vibe Coding Workflow

I am currently working for having A.I. workflow for generating projects. There are two things that need to be tackled for that: 1) hallucinations; and 2) old codes. I have met several patterns to tackle those two and just need to formulate the patterns into a general flow. Thankfully, a video of building fullstack app using A.I. from Raf Dev channel inspired me to make the formulation. He used multiple A.I. engines to his need: He used Google Gemini to onboard his ideas and summarized it. He forked a boilerplate of NextJS project into a new project. Then, he added the summary from Google Gemini into a file for context. He used QWEN Code, a QWEN3 code engine that is a fork from Gemini CLI, to build the project. When working with an existing project, A.I. will take the whole project as a context. It also means that it will stick with the version used by the libraries. It also will try to update its knowledge based on the common pattern in the project. Most of the time, it will use the c...
Post a Comment
Read more