SliTaz Forum
You are not logged in.
Thanks for the input. It doesn't help me, consdiering it's mostly about getting the guy to copy Xorg.0.log on his flash drive.
Anyway, I looked for "poulsbo '/dev/fb0: no such file or directory'" and ended up with some interesting results:
https://bbs.archlinux.org/viewtopic.php?id=134827#p1061886 <- post #7
http://crunchbang.org/forums/viewtopic.php?id=11040#p113708 <- post #11
^^^ this referes to http://edc.intel.com/App_Shared/Downloads/Intel-EMGD-v1.5.2-Released-Jan-2011.zip
It looks like the kernel and Xorg are essential, and SliTaz only has kernel 3.2.x. Could this be the reason?
Offline
According this old page http://doc.slitaz.org/en:guides:poulsbo
rcS.conf edit is for 4.0
tazpkg remove xorg-xf86-video-vesa
tazpkg get-install linux-staging
Package File
linux-staging /lib/modules/3.2.53-slitaz/kernel/drivers/staging/gma500/psb_gfx.ko.xz
linux64-staging /lib/modules/3.2.53-slitaz/kernel/drivers/staging/gma500/psb_gfx.ko.xz
Offline
Attempted to install SliTaz-5.0-RC2 on my SDHC microSD card and when the installation finished (without errors) I decided to wait a bit to ensure the data was actually written, then rebooted.
Due to the files being installed to the microSD card and not the harddrive, the boot menu had to be changed slightly.
hd(2,0) -> hd(0,0)
root=/dev/sdc1 -> root=/dev/sdb1
From then on, it started to load the SliTaz kernel, and seemingly finished doing that too. However, it dumps me to the busybox prompt. Alright, time for another challenge that I've yet to solve!
So right after the [Linux-bzimage, setup=0xdata, size=0xmoredata] message, I am met with the following errors:
[c]mount: can't read '/etc/fstab': No such file or directory
mkdir: can't create directory '/dev': File exists
udhcpc (v1.22.1) started
[some messages about sdb being loaded, which is the root system]
route: ioctl 0x890c failed: No such process
Sending discover...
Sending discover...
Sending discover...
route: ioctl 0x890c failed: No such process
No lease, forking to background
[busybox prompt appears here][/c]
Any takers? I'm not sure what went wrong here. It's worth noting that the sd card is fully functional, and was dd'd with /dev/zero all the way to the end to ensure it was completely clean before the installation began. Afterwards I created the partition table, a single partition, installed to that and it went fine.
However, now I am met with the above, and I am not sure how to get gonig from here on.
Offline
I fixed the issue. I mounted the SD card in a different system (Arch Linux), chrooted into it, and ran tazpkg recharge and tazpkg up. This fixed the issue.
Offline
Good evening everyone,
I am somehow stuck with Slitaz 5 RC 2. Everything runs fine using the VESA XOrg-Driver, but when I try to install the intel driver, XOrg fails.
I use the Intel GM965/GL960 chipset, which works without any problems under Slitaz 4.
Using tazx and choosing "intel" fails with
"Number of created screens does not match number of detected devices."
The Log indicates 2 PCI addresses (0:0:2:0) and (0:0:2:1), loads all the modules (intel module reporting its support for 965GM, too) and falls back to VESA mode.
If I try to push a little harder by uninstalling VESA and fbdev drivers (leaving intel as the only option), setup fails complaining "no screen found".
When checking tazhw detect-pci, the system asks for the agpgart_intel module, which is not present in any of the packages (at least tazpkg search-pkgname says so).
What else could I have missed?
Thanks a lot in advance,
Filou
Offline
the problem is, that the intel driver now needs the package libpthread-stubs - so before you run tazx you just need to install libpthread-stubs - so run
tazpkg -gi libpthread-stubs
Offline
Hi kultex,
thank you for the reply, which was the solution to what I experienced with RC 1 (where intel would not want to work at first, either...).
In RC 2, libpthread-stubs seems to have been added to xorg-xf86-intel, so it is already installed, but (this time) to no avail...
Offline
can you post the xorg.0.log when you removed VESA and fbdev drivers
Offline
Dell Inspiron E1505
VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940G
ML Express Integrated Graphics Controller (rev 03)
Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML
Express Integrated Graphics Controller (rev 03)
I see the same meaningless errors but start slim and intel driver loads OK
tazx :
"Number of created screens does not match number of detected devices."
tazhw detect-pci :
! Missing module : agpgart_intel
tazx installs:
2014-06-28 15:13:02 - Installed - xorg-libXv (1.0.8) - 6972ff5b993086fd41492309c72c735f
2014-06-28 15:13:02 - Installed - xorg-libXvMC (1.0.8) - a4e9e3db501479850357bbb63b5a636c
2014-06-28 15:13:02 - Installed - libpthread-stubs (0.2) - f759d468976016bd4ea0d70e5ed198bf
2014-06-28 15:13:03 - Installed - mesa (9.1.3) - 8faad6a542a698c4e584eb82baae7995
2014-06-28 15:13:04 - Installed - mesa-dri (9.1.3) - d88f72e70252d341e532c11744edc7ba
2014-06-28 15:13:05 - Installed - libdrm-intel (2.4.45) - 0ac5a617465b2387ef56277e74d0eedc
2014-06-28 15:13:05 - Installed - mesa-dri-intel (9.1.3) - f89e1962e1d9e4d9a54a104e647776c6
2014-06-28 15:13:05 - Installed - xorg-xf86-video-intel (2.21.9) - 6837320b5a52ff7234985894f1652d03
Offline
I have the same behaviour as mojo (at first): If I start slim again (after having killed it beforehand), it starts up ok and runs a X-session... BUT it seems to be a vesa session, still, concerning the lookout (unsharp due to non-native resolution).
After having closed this session, slim does not come up again and fails to be started again...
So for me it looks like X is not really using the intel driver... ?!?
My Xorg.log:
Offline
Some linux-distros contains a lot of files in [c]/etc/X11/xorg.conf.d[/c]
in slitaz these files for monitor and screen missed.
Offline
@Filou
Try replacing [c]nomodeset[/c] with [c]acpi_backlight=vendor[/c]
Reference: https://bbs.archlinux.org/viewtopic.php?id=162203
Offline
@Filou
Many open source drivers have removed support for non-kernel mode setting, so in those cases when you use nomodeset you will end up falling back to the very basic VESA driver
so youse nomodeset only if you want to use the vesa driver
Offline
I had to use the "nomodeset" in order for slitaz to come up graphically at all. That's why it was still in the grub config and still present as a kernel parameter.
This might be the reason for my faulty setup; I will try this out as soon as the machine is free for use again (my wife occupied it half an hour ago.... ;-) )
Thank you for the support; I will report back as soon as I have checked this one out...
Offline
Thanks again, you were totally right!!!
After removing "nomodeset" the system came up in the correct resolution in VESA mode even, but now also uses the intel driver correctly.
Nonetheless, agpgart_intel is still missing (which might end up in lower performance ?!). Does anybody know, if it was abandoned by slitaz? (It is part of the kernel, though).
Thank you again, learned a lot AGAIN.
Offline
Hello everyone! This is my first post here.
I just use Slitaz 5.0 RC2 as a Live CD, and I wanna say thanks for the SLitaz team.
It's a very nice operating system, and for me it's easy to understand and use.
It's amazing how you could make a 42MB-OS work, and it works fine here!
It has some minor bugs, but... every OS has it, hasn't it? ^.^ This won't make this OS less amazing.
I'm just waiting to stable version to really start using Slitaz on HDD. For a while I'll use it as Live CD.
Is there a prediction of when a stable version will come out?
Best regards,
Genesis.
P.S.: I don't know how to set an avatar image here.
P.P.S.: I apologize for my bad English.
Offline
@Genesis
Describe this minor bugs you found.
I'm just waiting to stable version to really start using Slitaz on HDD. For a while I'll use it as Live CD.
No reason to wait, you can install, then update. Now it's more stable than stable.
maybe only one small trouble comparing to 4.0 - sound 'mute' by default, (for numerous built-in ac97 but not for USB-soundcard). i hope setmixer will be implemented somewhere in start scripts.
Offline
What az_ua said is true, once you install any updates can be installed as they come out, allowing you to get the 'stable' version as soon as it is ready.
Offline
@az_ua
Thanks for you message.
These are the minor bugs:
1) as you said, there's no sound. I move up and down the volume control on Task Bar but nothing happens;
2) I can't change my screen resolution (1024x768). I tried it through the system configuration window (which I don't remember the name now), logged out/in and the resolution were back to the same.
Maybe these aren't really bugs, maybe it's my fault.
@p3ngu1n0
Thanks for your information; I didn't know about that. I'll try installing Slitaz RC2 on HDD.
Offline
Latest rolling core:
tazlito writeiso problem described in edited topic below with possible solution.
new bugs in rolling 5.0 compared with 4.0:
[c]bootlog | grep alsa[/c] alsactl errors causes mute by default.
no full Xorg log, just 3 short slim messages.
xterm crash on menuopen C^Rclick
wok repo packages:
virtualbox: vboxdrv wrong module path.
wine can't start, nothing in terminal.
e17 compiled without legacy hardware support.
Offline
Still have the Spanish keyboard problem with the letter "ñ" . It maps to "?". The rest of the keyboard works fine, but not that letter. On version 5-rc1 they advice me to run "tazx keyboard". That solve the problem of the rest of the keyboard mapping, however it gave me an error at the end of the process: "/usr/bin/tazx; line 262: genxseccion_not found". This error also appears when it ask the option to update the driver to pixman 0.28.2 and you try to run again tazx keyboard.
Now I update to slitaz 5.rev2 and the Spanish keyboard still has the wrong mapping to the letter ñ.
Even when you run "tazx keyboard", but this time it doesn't trow the error and doesn't tell you it could not finish nor it asks to update anything. However the mapping to the letter ñ to "?" continues. As far as I remember that problem didn't exits in version 3.0. They asked you at the beginning of installation for a "Spanish/Mexican" option, and it worked fine
Offline
I had stalled on the hard disk a swap partion on /dev/sda1 with Suse linux. When I stalled to the hard disk Slitaz 5.rc2 I erased all the devices except that one. I created partion /dev/sda2 with slitaz gparted and leave the /dev/sda1 untouch. I see that slitaz now it doesn't create a swap partion at installation. I have Slitaz instaled in /dev/sda2.
Question: Is Slitaz using /dev/sda1 as a swap space? Or do I have to created one with slitaz? If so, how can I create a swap partion for slitaz?
Offline
Hi compostela
After you have Slitaz 5.0-RC2 installed on the disk, you should have a line in /etc/fstab like this
/dev/sda1 swap swap defaults 0 0
If not, open sakura and type
$su the password root
#mkswap /dev/sda1
#swapon
#leafpad /etc/fstab and add the line above
Have a nice day with Slitaz
Offline
Hi Yves04. Thanks for your help.
No I don't have the line in /etc/fstab.
If I understood you correctly:
1) su to root
2) edit the file with an editor, (leafpad or vi)
3) add the following 2 lines at the end of the file /etc/fstab:
mkswap /dev/sda1
swapon
I did this after doing a new installation to the hard disk using the live CD.
I check with gparted to see if the swap partition was there and it wasn't.
Don't know if it has something to do with this but every time I boot slitaz 5-rc2 I get the following message:
/dev/sda1 was not clearly unmounted, check force.
Then I have to wait for the check until it finish. After that is ok. But It should not do that. It never have done it before. Always boot fast. I shutdown slitaz using the regular menu option.
Nothing strange on my dish. Slitas is the only system stalled on the disk.
Any idea of what's going on?
Offline
Hi
Sorry for my bad English and may be some bugs because of the keyboard of my iPod.
The line in /etc/fstab I was talking about is
/dev/sda1 swap swap defaults 0 0
This line will be automaticaly added to fstab by the installation
When you are installing Slitaz by mean of a CDROM you have to create (with gparted) at least two partitions one for / whose type is ext3 or ext4 and one for swap whose type is swap ; it´s convenient to have one more partition for home, same type as /
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.59 MiB (Peak: 1.77 MiB) ]