Author Topic: Oops not all packages from unstable are stable  (Read 2967 times)

zaai

  • Newbie
  • *
  • Posts: 44
    • View Profile
    • http://
Oops not all packages from unstable are stable
« on: October 14, 2004, 12:24:29 pm »
Hi, using RC5
Just installed a series  of packages from unstable and rebooted the Z.
Yes its unstable indeed.
Don't recall which packages exactly but be warned, some of them really screw up the system.
---
 dmesg spews out things like:
- cramfs: wrong magic
- FAT: bogus logical sector size 381
   Inode #8594 was a directory with children - removing those too...
   (11 more of these)
- Freeing init memory: 152K
   jffs: Too few erase blocks(0)
- Partition check:
   VFS: register(part1): could not append to parent, err: -17
   (three more of these)

startx fails with the following message:
Fatal server errror:
Could not open default font 'fixed'
---

My guess is that the extra fonts packages screwed up the basic font config, but I'll have to verify that.
Anyway, just a heads-up. I'm going to  reflash RC5 and do the same thing step by step.
Cheers,

ikm

  • Full Member
  • ***
  • Posts: 172
    • View Profile
    • http://
Oops not all packages from unstable are stable
« Reply #1 on: October 14, 2004, 12:38:48 pm »
Quote
Hi, using RC5
Just installed a series  of packages from unstable and rebooted the Z.
Yes its unstable indeed.
Don't recall which packages exactly but be warned, some of them really screw up the system.
---
 dmesg spews out things like:
- cramfs: wrong magic
- FAT: bogus logical sector size 381
   Inode #8594 was a directory with children - removing those too...
   (11 more of these)
- Freeing init memory: 152K
   jffs: Too few erase blocks(0)
- Partition check:
   VFS: register(part1): could not append to parent, err: -17
   (three more of these)

startx fails with the following message:
Fatal server errror:
Could not open default font 'fixed'
---

My guess is that the extra fonts packages screwed up the basic font config, but I'll have to verify that.
Anyway, just a heads-up. I'm going to  reflash RC5 and do the same thing step by step.
Cheers,
The only real problem you encountered here is a problem with the font indices overwritten by some font package. Maybe crox-cyrillic? Btw, all webfonts-* packages are safe to install.

All other stuff is perferctly normal, just disregard.

waalkman

  • Full Member
  • ***
  • Posts: 176
    • View Profile
Oops not all packages from unstable are stable
« Reply #2 on: October 14, 2004, 09:21:39 pm »
I got the same "Could not open default font 'fixed'" when I got a bit install-happy myself (RC2). Finally re-flashed to fix it...


John
C860, SMC Model SMC2642W, various sized memory cards

zaai

  • Newbie
  • *
  • Posts: 44
    • View Profile
    • http://
Oops not all packages from unstable are stable
« Reply #3 on: October 15, 2004, 05:40:44 am »
I tried again and things went wrong with the 'additional fonts' (freetype?) package. This package screws up the X-fonts configuration.I also had this in RC2 and RC3.
I probably had the wrong feed. This is a problem in RC2/3 only because in RC5 its preinstalled.

Another problem is that the battery drains very quickly. The 1500mAh battery is empty within 30-45 minutes. This is with Wifi, but even then its faster than ever before.
« Last Edit: October 15, 2004, 05:48:43 am by zaai »

iamasmith

  • Hero Member
  • *****
  • Posts: 1248
    • View Profile
Oops not all packages from unstable are stable
« Reply #4 on: October 15, 2004, 06:15:36 am »
Quote
dmesg spews out things like:
- cramfs: wrong magic
- FAT: bogus logical sector size 381
   Inode #8594 was a directory with children - removing those too...
   (11 more of these)
- Freeing init memory: 152K
   jffs: Too few erase blocks(0)
- Partition check:
   VFS: register(part1): could not append to parent, err: -17
zaai,

Just something worth mentioning when you reflash.

Am I right in assuming you chose a 121Mb root fs ? If so then you may want to knock out the line in fstab that tries to mount /home from the now non existent home partition.

The ROM will create the home structure on the root fs anyway.

You get a message similar to one of yours when you have this setup.

- Andy
OpenBSD 4.2 -current on full 4Gb of SL-C3000
Microdrive replaced with 4Gb SanDisk Extreme III card

scoutme

  • Hero Member
  • *****
  • Posts: 579
    • View Profile
Oops not all packages from unstable are stable
« Reply #5 on: October 15, 2004, 05:30:29 pm »
NO NEED TO REFLASH!!!!


simply you have to reinstall the font package you can find in the new feed


x11-fonts-misc_1.0.0_armv5tel.ipk


use ipkg from the commandline and X will be magically back


(consider using only rc5 compiled-for stuff, from the http://mirror1.pdaxrom.org/feed and http://www.pdaxrom.org/unstable)

zaai

  • Newbie
  • *
  • Posts: 44
    • View Profile
    • http://
Oops not all packages from unstable are stable
« Reply #6 on: October 18, 2004, 03:32:02 am »
Heh thanks for the tips everyone.

Yes Iamasmith, I am using a 121MB root fs. Just removed the /home mount line in fstab as indeed that one isn't needed anymore. Good tip.
The other errors still come up during boot but it doesn't seem to affect normal operation.

Scountme, that is a good workaround. Agreed we should only use RC5 packages and got them mixed up with RC3 by accident. Its good to know the package to fix it as reflashing was a bit of a brute force recovery method. Kinda like selling the car when you have a flat tire

scoutme

  • Hero Member
  • *****
  • Posts: 579
    • View Profile
Oops not all packages from unstable are stable
« Reply #7 on: October 18, 2004, 12:25:09 pm »
nice image