Tiny Core Base > Alpha Releases

Tiny Core 3.0 Alpha 4 Testing

<< < (8/14) > >>

althalus:
Found another problem - I've built 2 compositing managers (xcompmgr and cairo-compmgr) which I've been testing before I submit to the repo.

If i install the graphics-KERNEL extension for TC3a4, both compositing managers breaks down (blank screen with occasional flicker of open windows).

Xcompmgr has been tested and is working in TC2.11 with the appropriate graphics-KERNEL for 2.x installed.

I can make the xcompmgr available for others to test with, but it's not really ready to submit as a proper extension yet (no info file, for starters)

EDIT: Probably important to mention
lspci

--- Code: ---01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200M]
--- End code ---

bigpcman:
I created a bootable flash card using the "usb install" tool then tried booting from it on a eeepc 900a.

Using boot codes "waitusb=15 base norestore pause tce=UUID="3EA1-E917" " everything comes up fine.
Note the "tce=UUID="3EA1-E917" " is inserted by the "install usb" tool.

Using boot codes "waitusb=15  norestore pause tce=UUID="3EA1-E917" " I get a stream of "bus error" messages right after the "loading Tiny Core Applications Extensions..." message. There are no extensions installed at this point.

After I install the 915resolution.tcz and reboot I get the same results - "bus errors".

However, if I add the "showapps" boot code then I get the extension loaded messages "including the Patch mode 50 to resolution 1024x600 complete" and the "bus error" messages go away.

Any ideas as to what is going on?

edit: tried the same above procedure using a usb stick instead of a flash card and the stream of "bus error" messages is reduced to one message when no extensions are installed. After I install 915resolution I get a message after the "loading Tiny core applications extensions" as follows: udev[96]: can not read '/etc/udev/rules.d/75-cd-dvd.rules'

edit2: I just tried all of the above with tc2.11.1 and everything works perfect! Great release!

curaga:
bigpcman, could you post your dmesg? Also, on a boot you see the udev error, the output of "ls -lh /etc/udev/rules.d".
Udev outputs that error when it can't read the file, or the file is empty.

bigpcman:

--- Quote from: curaga on May 25, 2010, 03:12:10 PM ---bigpcman, could you post your dmesg? Also, on a boot you see the udev error, the output of "ls -lh /etc/udev/rules.d".
Udev outputs that error when it can't read the file, or the file is empty.

--- End quote ---

I just noticed that the eeepc_laptop was not loaded at boot. Here is the 2.11.1 lsmod report:

--- Code: ---Module                  Size  Used by    Not tainted
vfat                    5652  1
fat                    29692  1 vfat
squashfs               11732  1
scsi_wait_scan           260  0
eeepc_laptop            5264  0
hwmon                    640  1 eeepc_laptop
atl1e                  19596  0
backlight               1404  1 eeepc_laptop
battery                 5976  0
rfkill                  4012  2 eeepc_laptop
ac                      1732  0

--- End code ---

and here is tc3alpha4 lsmod report


--- Code: ---Module                  Size  Used by    Not tainted
vfat                    5596  1
fat                    30220  1 vfat
squashfs               14884  1
ramzswap               10240  1
loop                    8068  2
scsi_wait_scan           276  0
sparse_keymap           1168  0
battery                 6028  0
video                  12712  0
backlight               1632  1 video
ac                      1696  0
output                   724  1 video
atl1e                  19316  0

--- End code ---

Does this explain the problems?

I tried to do a "modprobe eeepc_laptop" but it failed with the message "unknown symbol in module or unknown parameter"

See attached dmesg report for the usb stick boot failure. It seems to be the worst case. I reran the tests with a different usb stick so the "/tce" name is different than in my previous post.

edit: The following is reported in the syslog report:

--- Code: ---May 25 16:39:29 (none) user.warn kernel: eeepc_laptop: Unknown symbol hwmon_device_register
May 25 16:39:29 (none) user.warn kernel: eeepc_laptop: Unknown symbol pci_hp_deregister
May 25 16:39:29 (none) user.warn kernel: eeepc_laptop: Unknown symbol __pci_hp_register
May 25 16:39:29 (none) user.warn kernel: eeepc_laptop: Unknown

--- End code ---

See attached syslog:

maro:
I was wondering whether it would be desirable to use "KERNEL" within an extension name used as parameter of 'tce-load'. E.g.
    tce-load -wi filesystems-KERNEL
instead of
    tce-load -wi filesystems-$( uname -r)

AFAIK the "-KERNEL" placeholder is only used for dependency files but not available from the CLI.

Navigation

[0] Message Index

[#] Next page

[*] Previous page