SliTaz Forum
You are not logged in.
I changed the slitaz 4 package mirror to the slitaz 5 package mirror using tazpkg setup-mirror. The idea is that I'd like to use some more up-to-date packages with slitaz 4.
The reason I still use slitaz 4 is because I had bad experiences with slitaz 5 RC2 (some programs I used a lot, like mountbox, ... were no longer present, video driver issues, keyboard mapping issues, ...) and also there's the issue that slitaz 4 is finished, whereas slitaz 5 is still under development.
I was wondering which packages can't be updated because else, they will give problems ?
Can you give a list ? Perhaps I can then blacklist them at etc/modprobe.d/blacklist.conf ?
Also, I found that some programs I wanted from the mirror don't work at slitaz 4 (all though installation works, and system remains stable):
* geany
* gajim
* conky
Some packages I'd like that are not present on the slitaz 4 nor slitaz 5 mirror:
* ipkungfu
* youtube-viewer
* firejail
* pypar2
I have them as a debian package (you can download them from http://sourceforge.net/projects/linuxefficiencyscripts/files/scriptsindevelopment/ ) and tried tazpkg convert *.deb but that didn't yield a working tazpkg; it seems a lot more user unput needs to be done on it.
Offline
This will not work, except by chance, because most (if not all) library versions are different. Even the GNU libc which is the very core of Linux is 2.13 in ST4 and 2.14.1 in ST5.
As regards package conversion, I think you have to check consistency of the version of the library dependencies, tazpkg doesn't check versions as far as I know.
The fact that ST5 is under development is not really a problem: if some day you find that ST5 fulfils your needs and you fear an update might break something, simply don't update it anymore (OK, this is not very secure, so you'll probably have to keep yourself informed of security bugfixes in sensitive software like your web browser, encrypting libs, etc.).
As a side note, modprobe.d/blacklist.conf is used to block kernel modules, it has no effect on packages. Tazpkg has a "block" command; not sure it works well in older versions, though.
Offline
So it isn't possible to say, update all libraries, or even parts of the entire directory structure to the slitaz 5 libraries/directories ?
I'll probably retry my project with slitaz 5 as a base, assuming the above won't work neither.
As for the package conversion: so you mean tazpkg will make a usable tazpkg from a debian package, normally (rather than just make some files like the recipe, ... yet with no rootfs folder /actual files) ? If so, could doing the conversion in slitaz 5 correct the issue ? Also, can you tell me how to convert files in bulk, for example straight from PCManFM. I had to convert every single package manually by the command tazpkg convert filenamepart*.deb in xterm. I hope there's a far faster way, then I can convert everything in a single go, correctly, in slitaz5. tazpkg convert * doesn't work btw, I tried that all ready.
Offline
So it isn't possible to say, update all libraries, or even parts of the entire directory structure to the slitaz 5 libraries/directories ?
I think the chain of dependencies would eventually make you update everything.
so you mean tazpkg will make a usable tazpkg from a debian package
I think it is supposed to. Never used this feature, though.
can you tell me how to convert files in bulk
With just a few shell commands in a terminal:
[c]for pack in filenamepart*.deb ; do
tazpkg convert $pack
done[/c]
Offline
I've started on making the slitaz 5 distro with my changes.
I'm having trouble getting xvesa to run though; I deleted
xorg-xf86-input-synaptics
xorg-xf86-video-fbdev
Screen still remains black upon starting the custom slitaz 5 though.
alternatively can I append a command at boot to override whatever video driver that loads; also tell me what video driver still needs to be deleted, or what files need altering
Offline
I also deleted
xorg-xf86-input-evdev
I tried switching off my video card in the BIOS, and switching to on-board graphics instead (also changed cable to on board video port). That allowed to show the "welcome to my box" text, but no X was started neither.
Also, when I tried deleting xorg-xf86-input-evdev, the mouse no longer worked with the PC that does run X (even on xorg video drivers)
It's annoying considering the fact that on slitaz 4 I did manage to get everything working with no problems; packagelist= taz 01 to 06, see http://sourceforge.net/p/taz/wiki/slitaz4corepackagesfortaz/ Note that I believe I took out xorg-server-Xvesa and it still ran.
any suggestions ?
I could put in
xorg-xf86-video-ati-7.1.0.tazpkg
xorg-xf86-video-i740-1.3.4.tazpkg
xorg-xf86-video-intel-2.21.9.tazpkg
xorg-xf86-video-sis-0.10.7.tazpkg
nvidia-96xx-96.43.23_3.2.71.tazpkg
nvidia-173xx-173.14.39_3.2.71.tazpkg
xorg-xf86-video-nv-2.1.20.tazpkg
xorg-xf86-video-radeonhd-1.3.0.tazpkg
and then cross my fingers hoping that slitaz automatically takes a correct driver, but I rather keep packages to a minimum, using only an xvesa driver
Offline
First, "xorg-xf86-input-*" are for... input, so no wonder why your mouse doesn't work anymore. You're lucky your keyboard still did!
Second, we cannot guess your hardware... Indeed Xorg should pick up the most appropriate driver, so you can install all those packages, then look into [c]/var/log/Xorg.0.log[/c] to see which one it uses, then remove all other packages.
Maybe Xvesa is in xorg-xf86-video-vesa?
Offline
"xorg-xf86-input-*" are for... input, so no wonder why your mouse doesn't work anymore. You're lucky your keyboard still did!
--> Hmm, perhaps it didn't. Don't know any more, just scrapped that iso and tried anew.
thanks for that path/info !
Yes, xorg-xf86-video-vesa is xvesa I believe. The trouble was that though I deleted most if not all other drivers, and so xvesa should/is? loaded, my screen still remains black. This, despite that using xvesa on slitaz 4 (with the exact same pc) worked fine.
I'll try putting in a range of drivers on the custom slitaz, and then see if it works.
Can you tell me whether there's a boot prompt command to force slitaz to load the xorg-xf86-video-vesa driver ? Something like vga=xorg-xf86-video-vesa, ...; see http://www.damnsmalllinux.org/wiki/vga_xxx.html (I also read about the command "nomodeset", see https://en.opensuse.org/SDB:Configuring_graphics_cards and "failsafe" ? Or can I make xorg to force using the xvesa driver by manipulating any of xorg's config files (is the file to alter /etc/X11/xorg.conf.d/newfilename.conf (https://wiki.archlinux.org/index.php/Xorg ) ?
Offline
Hi,
When you say screen remains black, you mean you don't even have a console (Ctrl-Alt-F1)? If so, you probably lack a kernel module, rather than an Xorg driver. You still didn't tell us what your hardware is.
If you have a working ST4, run these commands in a terminal in an X session:
[c]lspci -k > /tmp/lspci.out
lsmod > /tmp/lsmod.out[/c]
Then paste files /tmp/lspci.out, /tmp/lsmod.out, and /var/log/Xorg.0.log there: paste.slitaz.org , and post the file links here.
As far as I know the nomodeset and vga= parameters are intended to set the resolution for the consoles, and they may also influence Xorg, but it's not all clear to me. The preferred method to set the driver is using xorg.conf or xorg.conf.d/60-Device.conf, indeed. Do you have a strong reason why you want vesa rather than a driver specific to your card (intel, nvidia, ati...)?
Offline
Yes. I don't even have a console.
The problems occur even with the original slitaz 5 RC3, so it's not because of something I deleted.
For my hardware: the problem occurs on 2 of my pc's: one desktop and one laptop. The laptop is an Fujitsu siemens lifebook (c-series) -i think model 1000 or 1020 or so, so probably having a Xpress 1100 onboard graphics card -; the desktop is a Dell PowerEdge SC420, graphics card added was an ATI Radeon 7000 Legacy (normally requires catalyst driver I believe, which is no longer available on slitaz5 mirror).
The only pc that does boot X is an Acer Aspire 3003 laptop I have. Sadly, this doesn't even have enough ram for me to continue modifying slitaz as I reached about the limit of the ram capacity required for the tazlito writeiso command. Once I've been able to run slitaz on my desktop, I could continue the modifying.
Offline
Just to be sure: did you try to hit Ctrl-Alt-F1 (even when screen is blank)? Wait until the end of the boot process, which you can monitor by the HDD activity LED.
No, catalyst (the proprietary driver) is not required, the free driver "radeon" should be enough (I'll let you search the web to check if your cards are indeed supported by it, I didn't).
Are these packages installed: linux-drm, linux-firmware, linux-agp?
Reminder:
If you have a working ST4, run these commands in a terminal in an X session:
lspci -k > /tmp/lspci.out
lsmod > /tmp/lsmod.out
Then paste files /tmp/lspci.out, /tmp/lsmod.out, and /var/log/Xorg.0.log there: paste.slitaz.org , and post the file links here.
Offline
linux-drm, linux-firmware, linux-agp are indeed installed.
I added in the logs of the desktop in annex to this post
I didn't hit ctrl +alt +F1 when the screen was blank, I'll try that.
Offline
here are the laptop logs
Offline
tried ctrl alt F1, ctrl alt F2, ctrl alt F3, ... nothing worked after booting slitaz 5. Screen just stayed black.
Offline
=== For the desktop ===
Try to force loading of the radeon kernel module by appending [c]modprobe=radeon[/c] to the kernel line of the bootloader (/boot/grub/menu.lst for Grub). If it doesn't work, also add [c]nomodeset[/c], or [c]vga=normal[/c] (try both, one at a time).
Since it is a radeon card, add the xorg-xf86-video-ati package to the ISO.
=== For the laptop ===
The kernel module is not loaded: do you have consoles in ST4 on this machine? Try [c]modprobe=savage[/c] on the kernel line.
The Xorg log tells this is a 1024x768 display, but Xorg selected 1280x768 resolution: did you really have a blurry screen? If your display is really 1024x768, you can try the [c]vga=791[/c] or [c]vga=792[/c] boot parameter; or [c]nomodeset[/c].
This is a Savage card, add the xorg-xf86-video-savage package to the ISO.
Offline
I made another custom cd with the ati, savage package (along with other packages; ie cd needs to be useful for others too, with other hardware).
On the laptop, things now work; resolution is correct (1024x786 shown in lxrandr)
As for the desktop;
did you mean I need to add the text "modprobe=radeon" in the file /boot/grub/menu.lst ?
Or do I need to type in "modprobe=radeon" during boot ? If it's the latter, that doesn't work (tried that). It gives an error stating it doesn't recognise the command.
If you mean I need to alter the file /boot/grub/menu.lst, on the livecd, then how do I do that ? The folder /boot isn't present when running slitaz 5 from the clitaz 5 livecd (on /boot in PCManFm). So I can't alter it and then do tazlito writeiso again; rather it's only present on the livecd itself. I could open the iso in 7zip or isomaster, and then try to uncompress and modify the file, reinsert it and make an iso from it again; though I'm not sure whether that will yield a correct, bootable iso, and as mentioned I'm not even entirely sure whether this is the method you proposed.
One other thing: grub isn't present on slitaz5, rather it's isolinux. There is the file isolinux.cfg and the file vesamenu.c32 I could modify; is one of these the correct file ?
Offline
Grub is used on hard disk installs, isolinux on Live CD.
You should be able to enter additional kernel parameters at the boot menu. From a websearch, it seems you have to press Tab after highlighting the menu entry of your choice. Then you should be given the opportunity to edit the "kernel..." line.
Yes you can try editing isolinux.cfg. vesamenu.c32 is a binary file.
Offline
I got it working on my desktop pc by using tab on the main menu (where you select the language) just before enter-ing. I added modprobe=radeon nomodeset and it worked; modprobe=radeon alone and modprobe=radeon vga=normal didn't work.
It's a bit weird that adding modprobe=radeon nomodeset doesn't work on the typed screen though (the one shown after the language selection screen. Perhaps that's something worth fixing later ?
Regarding the exact error message returned when putting in the modprobe=radeon nomodeset at the typed screen: this was "could not find kernel image:modprobe".
Thanks for the help !
Offline
[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]