SliTaz Forum
You are not logged in.
Hi all,
So I spend the day testing different ISO flavors and way to configure Xorg. To anser Tom, yes we could go back to a ncurses lang/kmap config but I would prefer a GTK configs via tazbox.
This time I still include Xorg with DRI but Tazbox start Xorg with the option -nolock and Tazx confifure Xorg on DISPLAY 2 to avoid any conflict. Work for me but I need you to test it on your hardware.
Also a few Desktop polishing such as a new logout icon on the top right and remove logout function from Applications menu, new icon for TazPanel and TazWeb. And finaly please welcome Sakura Terminal in core, it's a much easier Terminal than Xterm with transparency and right click options to copy/paste commands.
As suggested by Mojo, we could go back to a simple Xorg and Vesa drivers without DRI, the nv and intel driver. Any opposition ?
http://mirror.slitaz.org/iso/rolling/slitaz-rolling.iso
http://mirror.slitaz.org/iso/rolling/slitaz-rolling.md5
http://mirror.slitaz.org/iso/rolling/slitaz-rolling.log
- Christophe
Offline
Do what you find to be appropriate - but under all circumstances manage an offer that will boot into an Xscreen without headaches. Anything else is a kill for each newcomer.
If dri, nv etc. are offered one would need a proper signal on the booting screen, not hidden!
Offline
@pankso
Ok, this rolling.iso boots on my PC wth this problematic oder nvidia card without any problem! Bravo!
Though I selected the right kmap after logging in I have the wrong keymap. /etc/keymap.conf is correct.
But in /etc/X11/xorg.d/40-Keyboard.conf the Option is wrong:
Option "XkbLayout" "dk"
I have to change it manually.Locale were selected ok.
Internet with Lan was connected automatically. With Slitay 3.0 I had to manually invoke it with ,,udhcpc".
Midori 0.4.4 is ok, the function to add bookmarks not visible straight away - but after one finds it it works.
Well done is my final remark.
Offline
Hi,
No chance on my Asus EB1502 (nvidia Ion)...
[c]<br />
X.Org X Server 1.9.5<br />
Release Date: 2011-03-17<br />
[ 118.796] X Protocol Version 11, Revision 0<br />
[ 118.796] Build Operating System: SliTaz GNU/Linux<br />
[ 118.797] Current Operating System: Linux slitaz 2.6.37-slitaz #2 SMP Wed Mar 7 10:36:39 CET 2012 i686<br />
[ 118.797] Kernel command line: initrd=/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz,/boot/rootfs1.gz lang=fr_FR kmap=fr-latin1 rw root=/dev/null vga=normal autologin BOOT_IMAGE=/boot/bzImage<br />
[ 118.797] Build Date: 18 March 2012 12:25:07AM<br />
.../...<br />
[ 119.718] (II) XINPUT: Adding extended input device "HID 046a:0023" (type: KEYBOARD)<br />
[ 119.718] (**) Option "xkb_rules" "evdev"<br />
[ 119.718] (**) Option "xkb_model" "evdev"<br />
[ 119.718] (**) Option "xkb_layout" "fr"<br />
[ 119.718] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"<br />
[ 119.718] (EE) HID 046a:0023: failed to initialize for relative axes.<br />
[ 119.719] (II) HID 046a:0023: initialized for absolute axes.<br />
.../...<br />[/c]
Is it really a problem with Xorg ???
At least no problem at all on my old Pavillon ze4282... With Slitaz it works like a new PC ! Bravo !
Offline
I have not tested that version but played yesterday with RC3 and found that ctrl+alt+backspace leads to a black screen. It eneded up rebooting (i think i hit ctrl+alt+del in the meantime).
Offline
On my PC still remains the same fault on starting Xscreen, as with previous releases RC series.
I am sure that many users have fallen if the defect in screen have chosen the wrong language,
were left without a graphic.
If the choice of language and keyboard gets the boot line (and only accepts lang = en_US).
As already reported by other error in the configuration of the keyboard.
On the graphic I have already expressed, I am opposed to the two bar-style little ubuntu,
Then how can you live with them especially with the new screens 16-9 to me remains a mystery.
Improved some icons and menu settings screen.
I believe good job, but you can still improve.
Offline
Tried installing latest rolling on my Lenovo Y550P laptop - installer does not allow me to choose HDD partition.
Offline
How critical/robust is Xorg on pre-install live boot, compared to Xvesa? Just wondering.
Offline
Xvesa is only good for < 2000 hardware. (Such as a Dell Latitude CPi)
Because a full X.Org is golden with Intel graphics, probably anything > 1999.
Seems to only add around 10 MiB.
Offline
Ah, the Intel dependency infiltrating DebIan & Xorg via GNU gcc and gas in recent years. Few distros are immune. Makes using humbler hardware dicey. Like 2003 AMD. My old pc boots RC1-xvesa, but nothing later.
Most newer distro versions turn my display off just before the desktop appears.
ByTheWay, is there a cheatcode to avoid using an existing swap partition? I couldn't find boot doc for that.
Offline
@Somewhat Reticent
Fertile ground for conspiracy-type theories? ;-)
Any background material available to understand this problem? How is that connected to gcc?
One thing is clear: a distro that turns the display off before the Desktop screen appears is impossible for any beginner. No way.
Offline
@Somewhat Reticent
There is no swapoff cheatcode.
http://hg.slitaz.org/slitaz-boot-scripts/file/4e3f09beb648/etc/init.d/bootopts.sh
Comment with # the beginning of lines 9->14
#leafpad /etc/init.d/bootopts.sh
Options/Line numbers
Swap will not be written to /etc/fstab
Generate iso with modification:
tazlito writeiso gzip
Offline
I ran across a natural assumption (at least for an Intel programmer donating code to GNU gcc and gas) about undocumented nopl and nopw assembler instructions normal in Intel i686 chips. Of course, this may not actually be the root cause of so many recent distros turning my display off just as the desktop should appear. Complex systems are sneaky!
Thank you, mojo - now I get to catch up on my homework - learning curve for a newbie.
(GPartEd wouldn't allow me to unmount swap in an extended partiton.) The adventure continues ...
Offline
Some random notes about the latest rolling. I don't know if they've been reported elsewhere, and I apologize if they're duplicates.
* Installing to disk with a different default username results in the openbox menu.xml not being written (it's blank), which gives an error message and no window manager after log in.
* Bug I noticed in v3, still present in v4: the username "tux" is hard-coded everywhere, not just in the live environment. For instance, after installing to disk and booting from the new installation, using tazlito will insist on creating the new ISO in /home/tux instead of /home/newusername
* Installing to disk with rolling succeeded on one virtual machine (VMware Fusion), but on my other machine (VMware Workstation) the GRUB config that was written to disk was very odd, attempting to boot from (hd3,0) instead of (0,0). There is only one HD attached to the system, it's an IDE disk. Apparently grub-probe failed in the most painful and agonizing fashion, and in its death throes it thought (hd3,0) was the correct location. I attempted this multiple times with various configuration params in the install wizard and in VMware, with no effect. I have attached the install log (EDIT: scratch that, upload failed. Here's a link instead: http://pastebin.ca/2133708 )
EDIT
Figured it out while working on my own software that I'm trying to get working in ST. ST is reserving devices hdaXXX, hdbXXX and hdc; the local disk is being mounted on /dev/hddXXX. Grub setup is in turn grokking that as disk #3. Probably should either cat /proc/partitions to see what's actually there instead of relying on the device name... (time to change my code to do that!)
Offline
Everything is working well, wireless is now persistant, eeepc701sdx & OTB,but 'mobile broadband' is problematic. It will connect but needs a trixar_za 'work-around'.
The 'Terminal' icon is not 'working' and it is necessary to go to Applications> .....not a big thing but 'just sayin!
Offline
@plumtreed Working on it. https://wiki.archlinux.org/index.php/3G_and_GPRS_modems_with_pppd looks like a promising guide so far...
Offline
@trixar_za Thanks for the link 
Offline
I'm using slitaz-rolling.iso from today. I'm running Slitaz on a usb drive I made with unetbootin. How can I install on hd?
THANKS
Offline
Running LiveCD of Rolling from 29Mar on an HPVectra (P4 1.6GHz) w/ 512MB RAM, NVidia GeForce FX5200 and Acer AL1917W widescreen monitor (1440x900). Running very well. According to 60-Device.conf, using "nv" driver. A few notes. Persistence of settings is a bit of a problem between TUX and ROOT. Setting screen resolution and refresh rate does not persist between logins, using only those settings recognized by XRandR and known to be good for my card/monitor combination. Default wallpaper (1600x1200) scales perfectly at some resolutions such as monitor default 1440x900 but not at other resolutions. Known good modelines etc. brought over from Puppy Linux don't seem to help. In this rolling release noticed that the bottom panel again tends to disappear completely from the screen (and from the directory) for both ROOT and TUX after I make changes to the displayed time format in the top panel. For now I make my changes and then immediately take away all permissions for both the 'panel' and 'bottom' files for both ROOT and TUX. Despite the few glitches, the progress with these rolling releases is just amazing! Very small, tight, and stable core to build on - your work is appreciated.
[I respond to myself] How can I install on hd?
I followed http://doc.slitaz.org/en:handbook:installation to install slitaz to hd. WOW I love it.
Offline
@plumtreed Can you test something for me?
Open a terminal program (xterm or sakura):
1. su to root
2. addgroup tux dialout (replace tux with your username if your not using tux as your user)
3. addgroup tux lp
4. chown root:root /usr/sbin/pppd
5. chmod u+s /usr/sbin/pppd
6. chmod 4755 /usr/sbin/pppd
7. Start your favorite dialer program or sakis3g
Tell me if it works, because I'm currently posting from the latest rolling iso using Midori as a normal user. One of those may have fixed our bug 
Offline
@Trixar_za
Didn't work for me....using tux,xterm and Sakis3G. Updated and latest available Slitaz.
Still works if I load Midori in xterm.
...sry 
Offline
Probably something in sakis3g then
Offline
What are you using?
Offline
I never had a problem with the display turning off or staying blank when booting with earlier hardware.
That usually occurs because of vice-versa. (When hardware came out after the distro version)
But with AntiX, the kernel keeps giving me a kernel panic about being unable to mount rootfs, even when I can't see anything wrong.
(On a 2003 Dell Dimension 2350)
With the exception of AntiX, the only IDE controller issues I had was on my Asus P5QL Pro board.
I think it's because most distros don't like the Marvell PATA controller.
SliTaz 3 was fine when I booted off a USB drive and made sure that it was mounted before running the installer to install to the HDD.
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]