WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Core v4.4rc1  (Read 17190 times)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Core v4.4rc1
« Reply #15 on: February 26, 2012, 11:38:45 AM »
netnomad, have you tried wl-modules-3.0.21-tinycore.tcz?  See info file for blacklist requirements.
10+ Years Contributing to Linux Open Source Projects.

Offline netnomad

  • Hero Member
  • *****
  • Posts: 1026
Re: Core v4.4rc1
« Reply #16 on: February 26, 2012, 12:09:20 PM »
hi roberts,

i tried wl-modules-3.0.21-tinycore.tcz in my onboot.lst and succeeded.

i used following blacklist-bootcodes:
blacklist=snd_usb_audio
blacklist=ssb
blacklist=b43

but the further boot-messages are not so nice:
at the beginning there are still these messages i posted with missing b44...

later after loading the wl-module over the onboot.lst all drivers are initiated without further problems.

is this the only way to solve this with this error messages:
b44: Unknown symbol ssb_device_is_enabled (err 0)
b44: Unknown symbol ssb_pcicore_dev_irqvecs_enable (err 0)
b44: Unknown symbol ssb_bus_may_powerdown (err 0)
b44: Unknown symbol ssb_pcihost_register (err 0)
b44: Unknown symbol ssb_device_disable (err 0)
b44: Unknown symbol ssb_device_enable (err 0)
b44: Unknown symbol ssb_driver_unregister (err 0)
b44: Unknown symbol __ssb_driver_register (err 0)
b44: Unknown symbol ssb_bus_powerup (err 0)
b44: Unknown symbol ssb_clockspeed (err 0)
b44: Unknown symbol ssb_dma_translation (err 0)
EXT4-fs (sdb2): mounting ext3 file system using the ext4 subsystem
EXT4-fs (sdb2): warning: maximal mount count reached, running e2fsck is recommended
EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
intel_rng: FWH not detected
lib80211: common routines for IEEE802.11 drivers
b44 0000:02:05.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
lib80211_crypt: registered algorithm 'NULL'
cfg80211: Calling CRDA to update world regulatory domain
ssb: Core 0 found: Fast Ethernet (cc 0x806, rev 0x07, vendor 0x4243)
ssb: Core 1 found: V90 (cc 0x807, rev 0x03, vendor 0x4243)
ssb: Core 2 found: PCI (cc 0x804, rev 0x0A, vendor 0x4243)
libipw: 802.11 data/management/control stack, git-1.1.13
libipw: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
ssb: Sonics Silicon Backplane found on PCI device 0000:02:05.0
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq
ipw2200: Copyright(c) 2003-2006 Intel Corporation
b44: b44.c:v2.0
ipw2200 0000:02:07.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection
ipw2200: ipw2200-bss.fw request_firmware failed: Reason -2
ipw2200: Unable to load firmware: -2
ipw2200: failed to register network device
b44 ssb0:0: eth0: Broadcom 44xx/47xx 10/100BaseT Ethernet 00:00:f0:7d:e9:6b
ipw2200 0000:02:07.0: PCI INT A disabled
ipw2200: probe of 0000:02:07.0 failed with error -5
b44 ssb0:0: eth0: Link is up at 100 Mbps, full duplex
b44 ssb0:0: eth0: Flow control is off for TX and off for RX


Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10957
Re: Core v4.4rc1
« Reply #17 on: February 26, 2012, 11:21:15 PM »
IIRC this was fixed after the previous kernel release too, and I forgot to add it to sorter.sh. b44 is a wired card, please move ssb to base again Robert.
The only barriers that can stop you are the ones you create yourself.

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: Core v4.4rc1
« Reply #18 on: February 27, 2012, 03:36:48 PM »
Strictly speaking this might be seen as an extension request, but I guess we could do with a new linux-headers-3.0.21-tinycore.tcz as the other new kernel modules have now been added to the 4.x repository.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10957
Re: Core v4.4rc1
« Reply #19 on: February 27, 2012, 11:10:16 PM »
hats usually takes care of that, I either don't care about external modules or just use the full source. Ping him on irc :)
The only barriers that can stop you are the ones you create yourself.

Offline genec

  • Full Member
  • ***
  • Posts: 240
Re: Core v4.4rc1
« Reply #20 on: February 28, 2012, 03:05:36 PM »
Placing core.gz and vmlinuz in it's own boot directory under sda1/tce/boot, also move extlinux directory and it's contents to sda1/boot  with minor edits to extlinux.conf to point to /tce/boot proved a success,  core 4.4 boots    (no wbar, but am sure I'll figure that out a lot quicker than fixing the path to ldlinux.sys)

This points to 1) inconsistencies in your Syslinux config and 2) changes in the default install/search folders for TC.  Forcing the search folder or fully aligning with the current patterns would have likely solved this.

If you move the extlinux/ directory to sda1:tce/boot/ then run 'extlinux -u /mnt/sda1/tce/boot/extlinux/' then update config file references appropriately, this will solve your issue.  You can also watch the return value of the installer extlinux by doing something like 'echo $?' immediately afterwards.  0 is success.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Core v4.4rc1
« Reply #21 on: February 28, 2012, 05:39:41 PM »
IIRC this was fixed after the previous kernel release too, and I forgot to add it to sorter.sh. b44 is a wired card, please move ssb to base again Robert.
Done. Will be in rc2.
10+ Years Contributing to Linux Open Source Projects.

Offline uggla

  • Sr. Member
  • ****
  • Posts: 438
Re: Core v4.4rc1
« Reply #22 on: February 29, 2012, 09:13:37 AM »
There are still some wbar problems when loading Xprogs ondemand:
http://forum.tinycorelinux.net/index.php/topic,12339.msg69076.html#msg69076

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Core v4.4rc1
« Reply #23 on: February 29, 2012, 02:55:51 PM »
I've been getting some practice in updating more frugal systems from tc4.1 to tc4.4rc1 lately.    So far the most reliable method has been to make backups of filetool.lst and onboot.lst, then load up the latest tc-install and use that tool to install to an existing partition (using  install boot loader option) and copy over new tcz's.  After a reboot delete the existing boot directory and append the new filetool and onboot files as necessary from the old backed up versions and reboot.

I forgot something, run the tc-update and/or AppsAudit updates.
Also from 4.2  just realised these files needed updating.  Since they are not in a backup only a permanent store,  deleted them and rebooted.
.setbackground
.profile
.xsession

Not sure if I missed any other files?

Things are looking up now !
« Last Edit: February 29, 2012, 07:58:19 PM by coreplayer2 »

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Re: Core v4.4rc1
« Reply #24 on: March 01, 2012, 12:04:57 PM »
'Set' button at the lower-right corner of ScmBrowser is inactive, can't change path tp local repository. Same in TC 4.3
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Core v4.4rc1
« Reply #25 on: March 01, 2012, 02:49:38 PM »
The Set button has only ever been active when the tcedir is on /tmp and the initial status bar displaying tcedir is red. No other purpose.
10+ Years Contributing to Linux Open Source Projects.