SliTaz Forum
You are not logged in.
Posted in previous post (2 back) that I lost wireless in RC2 but what happened was that it became less automatic.....entered details manually and it worked!
Offline
How can I make PPPoE connection on Slitaz 4.0 RC2 ?
Offline
midori + youtube = flash crash
is there any battery module for my eee ?
Hi I have a nvidia gf8200 and had some problems with video in RC2 (all previous stable, cooking and rolling versions worked great).
Without parameters i can't get a graphical login, it gives me the right resolution but stays in command line. If i enter startx it gives me an error and remains in console.
If i pass it 'nomodeset' i get a graphical login prompt with the right resolution but the screen appears missplaced in respect to the monitor to the upper right, with black margins in the left and bottom.
Thanks in advance.
PD: other distros with the nouveau driver worked well for me.
Offline
We have an issue with nouveau, we have the kernel module but not the Xorg driver. We will remove Kernel module and nv driver should work nicely.
@moulefritte C'an reproduce, I'm on youtube and midori listing to http://www.youtube.com/watch?v=ENBX_v1Po1Y
battery support is build in the kernel not as module
$ zcat /proc/config.gz | grep BATTERY
Offline
@pankso
The release is beautiful,your sense of style is amazing.
The tazpkg notification with menu is sweet!
IMO go back to xorg-server-light
xorg-server depends on libdrm that depends on linux-drm that owns nouveau
No xorg-server no nouveau frame buffer driver module to blank the screen.
Consider adding xorg-xf86-video-ati to release.
When I install xorg-server for dri and remove libdrm and linux-drm direct rendering still works.
It's not clear to me why libdrm and linux-drm are depends of xorg-server.
xorg-server+dri will not direct render to hardware on any of my computers.
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
Is there something left out of the compile options for xorg-server that is preventing hardware rendering?
sidenote:
TazPanel/Live/Live USB and Write a Live CD both broken.
I use tazusb instead:
#tazusb format fat32
#tazusb gen-liveusb
Slim login fails...
Fat32 format option in tazusb should be removed,it breaks slim login.
Offline
I'm having troubles getting RC2 to boot at all. I could dd-copy RC1 to a USB-stick and run it, but RC2 doesn't even register at boot. unetbootin isn't a viable alternative, since that leads to a kernel panic. What am I missing?
@mojo
Thanks for the polished side :-)
I saw this kernel nouveau module issue yesterday nignt and wanted to remove it from linux-drm, but you point out a better way, I will also do some test and if we not need kernel modules to get Xorg direct rendering, I'm going to remove linux-drm from Xorg deps (it will still depends on mesa, unlike xorg-server-light).
I will consider adding xorg-xf86-video-ati to release = + 1,2 Mb
"Is there something left out of the compile options for xorg-server that is preventing hardware rendering?" A kernel module for your Nvidia card... On my intel system:
$ glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: Yes
...
OpenGL renderer string: Mesa DRI Intel(R) 945GM x86/MMX/SSE2
I can't get-it to work in live into Tazpanel, on an hd install clicking on writeiso into Tazpanel open an xterm but not in live, why I did tazusb-box. Slim login on fat32 fails due to xauth, it's cant set permission and lock it. Yes we have to remove fat32 support I guess.
Offline
This is my first post on Slitaz.I am very impressed with Slitaz3 and more so with 4RC1 and RC2. I had a bit of difficulty with RC2 but mojo's suggestion to Paul helped . have got the Slitaz Core Live working by appending -nomodeset- to the boot menu. I have full functionality after a boot time 0f 21 secs. I think I got a little spoilt by Slitaz3 boot time of 6 secs according to the boot log!
My heartiest congratulations and thanks to all who have produed a Super Light Intelligent & Technically Advanced Zone..
Offline
Congratz for the release 
!
I had some problems though, X works, but the environment doesnt want to load
[attachment=7217,357]
What I learned from mojo:
You booted with ,,nomodeset" in the cmd-line?
Then:
#tazhw detect-pci
You should see the module nv
If yes:
#/etc/init.d/slim start
#startx
Worked with me. But before I had to do:
#tazx
Then select nv (I have a nvidia-graphic card) -let it install, then do the above mentioned things, feed back.
Offline
I have a similar problem like rexroom. Slitaz 3, RC1 and different former cookings booted on my EeePC without any problems. But the RC2 doen't boot at all. After attempting to boot from the USB-flash-drive (made with dd) the PC allways directly goes to the first partition of the first harddrive to boot my installed Linux distribution.
As already mentioned I didnt had such trouble with RC1. After some attempts with RC2 I changed back to the RC1 which boots without any problems (but there is no correct resolution bc of some xorg troubles...).
Offline
Two observations:
The monitor settings will not hold - I "apply" and "Save Configuration" but on bootup the settings have reverted to default
There does not appear to be a screen brightness control - the FN key options don't work
I am very impressed with Slitaz - I prefer it to Ubuntu - it is good to begin with a slimline system that you can adjust to your tastes - (even if that includes the Chrome browser) - People will use mainstream software so that they can switch between systems and retain full usability
Offline
Hey.
From the Live-cd everything works fine, but when installing ...
At first, just to load says:
ERROR: UNABLE TO LOCATE FOR GSI IOAPICs 1
ERROR: UNABLE TO LOCATE FOR GSI IOAPICs 8 ... ETC.
Then I have a nvidia driver and does not start. He stays on a black screen.
How I can fix it? I have to edit the grub entry and write nomodeset?
I'm new ...
Greetings.
I hope not to bother with bad translations of google.
Offline
Just do what I wrote some posts above! It is always the same with these nvidia cards! ;-)
Offline
Slitaz-4.0-RC2.
The installation to usb was very straightforward for the first time with persistence. Modifying extlinux.conf now allows boot into the os without having to stop for lang and keymap selections.
Is the boot log time reliable? I am getting times as low as 4 secs which seem different to the perceived time.
The following is excerpt fom the modified extlinux.conf.
LABEL core
MENU LABEL SliTaz core Live
KERNEL /boot/bzImage
append initrd=/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz,/boot/rootfs1.gz rw root=/dev/null vga=normal autologin home=2180a778-2056-4b30-81d3-778bcb2453a6 nomodeset lang=en_GB kmap=us
BTW Ihave an nvidia card which seems not to have problems except to include "nomodeset" as above.
Offline
@Nara Boot time dont include the kernel load, we start the timer when the Kernel execute the first boot script aka /etc/init.d/rcS and we stop it when the all 4 SliTaz boot scripts are executed. But X is started before the end of boot scripts so in some case you can get to the desktop before boot process finish. Here I got 7 sec in logs and get a desktop in 6 sec including kernel load.
One can also modify /etc/rcS.conf (main boot configuartion file) and enable FAST_BOOT_X to start X even earlier in boot process. This work only if Xorg was configured once, so only for HD install or custom LiveUSB.
Offline
Hello pankso,
Ah so desu ka!
Thank you for the swift reply.Mystery solved
I may have been a little premature with the persistence cry. I find sylphhed disappears on shut down and requires reinstallation. However the Mail folder created by Sylpheed together with all mail survives the reboot!
I did a writefs which resulted in the crearion of a 126Mb rootfs.gz which was subsequently added manually to the menu (5 gz files). Restarting does bring up Sylpheed but behaves as a fresh install requiring setup all over again.And the bottom panel disappeared!.. Removing the addition has returned as it was, except of course. sans Sylpheed .
The more I work with this gem the more amazing it appears in its elegant simplicity.
Offline
Hi, still stucked with Xorg and my nVidia graphic card here.
While trying to boot Slitaz 4 RC2 in default "Live" mode, I cannot get further than console, because of Xorg: the "nouveau" kernel module already claiming... (the device) ?
But there is more:
- no screen found (classic Dell one)
- no device found
- [c]tazhw detect-pci[/c] detects "nouveau"
I tried to copy my xorg.conf from my working stable SliTaz 3 HD-installed OS, no more success, same error.
I tried mojo's advices sequence, always the same error.
I tried to launch [c]hwsetup nvidia[/c] then, I got a xorg.conf more filled but still the very same errors.
I tried several other live options: justx, gtkonly, base: in the first time I was indifferently driven to the console after an xorg fail (excepted "base" option), and after a few try for every option excepted "base", I had a frozen keyboard and screen with "something graphic" but completely scrambled.
The "nomodeset" trick does not work.
My card is quite a classic one: GT-220 on Fast-PCI I guess (I did not open my desktop since a while, now).
Does it help someone ? Will it help me too ? ;-]
Regards,
--Babaorum
Offline
Ladies and gentlemen,
I am from Salvador in Bahia, Brazil
I am using google translator to talk to you
I need your help
Which off the GRUB is used in SliTaz 4.0-RC2?
Grub or Grub2?
How can I recover GRUB after installing windows 7
I await answers
Will embrace all
TI - Helpdesk
Silvio A. Sampaio
55 71 9153.0436
sampaiosp@hotmail.com
http://sampaiosp.blogspot.com
Offline
sampaiosp, it's grub4dos (based on first GRUB version).
Offline
As I wrote already yesterday I wasnt able to boot RC2 on my EeePC 901 with 2GB RAM. I created the USB-flash using the dd command. Everything worked fine with RC1 (I'm talking about the booting process, not the xorg troubles...).
Today I tried the RC2-loram iso and it worked out of the box. Even with the correct 1024*600 resolution!
Good that the loram-iso works fine, but I cannot understand why the ordinary iso doesnt boot.
What are the differences between does two isos? I thought there was just a less RAM-consuming compression-way on the loram iso, but why the ordinary iso doesnt boot on 2GB RAM? I think it cannot be a question of RAM!
For me it doesnt matter to use the loram-iso or the ordinary one. I was just wondering why it is as it is.
@rexroom
Did you try the loram-iso?
Offline
@Sebastian
RC2 version is why the graphics auto configured,not loram.
RC2 release includes intel,nv,geode graphics drivers which have superior autoconfiguration.
RC1 release only includes the generic vesa driver which requires manual configuration on some hardware.
Offline
sampaiosp, on a HDD install, it's grub1 (0,97):
http://www.gnu.org/software/grub
Offline
Thank you,
I managed to recover the windows 7
I changed the entry in menu.lst
I changed (hd0.1) to (hd0.0)
But I just can not recover the SliTaz
I still need help in this part
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]