SliTaz SliTaz Forum archive

This forum is now a read-only archive

The SliTaz community has moved to Maille, a forum made for SliTaz.

We looked hard for a replacement for this aging forum, including a move from bbPress to FluxBB last June. But spam bots now get through sign-up even with mail confirmation, and these forum engines are barely maintained anymore. So we wrote a forum in the SliTaz spirit: small, fast, no JavaScript, works on old machines and in text browsers. Everything here stays readable.

Go to Maille

You are not logged in.

#1 2011-06-29 05:46:09

ultrarad
Member
Registered: 2011-06-29
Posts: 8

consoles and sreen resolution on 20110531 and updated cooking

cooking livecd (whether or not upgraded, with or without additional packages):

consoles give only blank screen; also:

root@slitaz:~# deallocvt 2

VT_DISALLOCATE: Device or resource busy

deallocvt: could not deallocate console 2

also, booting with, e.g.

slitaz screen=1280x768x24

did nothing with basic cooking (yet to try upgrades; will shortly.)

Offline

#2 2011-06-29 06:21:43

ultrarad
Member
Registered: 2011-06-29
Posts: 8

Re: consoles and sreen resolution on 20110531 and updated cooking

tried;

slitaz screen=1280x768x24

did nothing with upgraded cooking

Offline

#3 2011-06-29 10:28:43

ultrarad
Member
Registered: 2011-06-29
Posts: 8

Re: consoles and sreen resolution on 20110531 and updated cooking

Resolved, as follows:

reconfigured xorg using tazx (for ati, which added ati packages for xorg, mesa, etc.);

remastered.

On boot (without added parameters) max resolution was autodetected.

Consoles now active and visible.

Comment:

tazx output refers to nonexistent /root/xorg.conf.new

Added comment:

In previous attempt to post this, in the upgraded cooking, midori exhibited the notorious freeze-while-trying-to-post-to-the-slitaz-forum behavior.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]