SliTaz Forum
You are not logged in.
Pages: 1
Hello all!
I love slitaz! Its one of my favorite distros, and I dearly want to use it on my old Acer AOA-751h, with a GMA500 graphics chip. Thank you for restoring SCSI onto 4.0, so I can at least make it that far 
I've tried to follow the instructions on this link:
http://doc.slitaz.org/en:guides:poulsbo
And read extensively, but I am getting nowhere. The linux staging package does not seem to exist, and the instructions do not describe how to do this with tazpanel, for instance adding the rolling mirror.
Can somebody with more know-how update these instructions to provide step-by-step guide for those of us who can follow a guide, but can't seem to find the parts?
Lastly, I'll throw out a stupid question - is it possible to create a tazpkg that could make the modifications needed to enable psb_gfx?
Thanks for any help, I'm really eager to get this going.
Offline
shameless bump o' desperation
Offline
jes its not available in 4.0 - its just available in rolling - see screenshot
4.0 is Kernel 2.6.37 ?? and rolling 3.2.53- its available only from Kernel 3.0
so you have to take rolling - but its under developement, so things perhaps do not work as usual
http://mirror.slitaz.org/iso/rolling/
[attachment=27606,1294]
Offline
And please report, if rolling is booting fine on Pulsbo - fbdev is now included - it should work out of the box.
I had no chance until now to test, because nobody I know has a Pulsbo machine
Offline
Hi Kultex,
Thanks for the information. As you said, the guide is not working for me. I did try to do a direct installation of rolling, and it will not boot into a desktop, goes to the famous "Welcome to your box" message. I tried "startx" and got an error message, which I cannot give you verbatim since it's not in front of me right now. I'll try again when I get home and post the error here.
Now you know someone with a poulsbo machine I'll help any way I can.
Thanks,
TM
Offline
In the meantime, I don't know how useful this info will be, but here is some more on it:
The 751h will boot pretty much any current ubuntu derivative, like mint (Mate, cinnamon won't run) and peppermint 4, with native resolution of 1366x768, but performance is terrible with it's atom processor. Slitaz would be ideal for a netbook of this vintage.
I followed the guide by live booting a slitaz 4.0 (stable) usb key and then installing from the web using cooking, not rolling. The final result is that it boots into a desktop and reports a 2.x kernel. I could not run upgrades from Tazpanel, the list would recharge and check for upgrades, but on install it reported a long series of packages not found.
I tried to upgrade from terminal, and packages were found, but had multiple errors. Afterwards it booted to grub, then error when attempting to go further.
As I said, the live USB of rolling will not load the desktop, and I'm mostly helpless without one.
Thanks!
TM
Offline
ok lets try to get further -
you boot rolling until "Welcome to your box" - login as tux then 2 x enter
then you type: cat /etc/X11/xorg.conf.d/60-Device.conf
and please tell me whats written under "Driver" - vesa or fbdev
now you get root - just type: su and password root
when you are root you type:
tazpkg remove xorg-xf86-video-vesa
type: exit - now you are again user tux
now startx
tell me if you get now the desktop
if not log in as root again with su
tazpkg -gi linux-staging
exit to get user tux and again startx - now it should work, when the doc is correct
Offline
Hi kultex,
The error being generated by startx is
fatal server error:
no screens found
The driver from the cat command is "vesa" fbdev is listed as an option.
I ran the tazpkg commands as described, startx produces the same error.
Thanks!
TM
Offline
I will make 2 isos the next days for you for testing - as soon as I have time
Offline
I did a mistake in my last description - so I ask you to repeat these commands as root with the normal iso:
tazpkg remove xorg-xf86-video-vesa
tazpkg -gi linux-staging
modprobe psb_gfx
exit to get user tux and startx
its important to know, if tazx would work...
and here are the two isos to test:
https://dl.dropboxusercontent.com/u/92249974/slitaz-rolling-without-vesa.iso
https://dl.dropboxusercontent.com/u/92249974/slitaz-rolling-pulsbo.iso
Offline
Hi Kultex,
I tried the commands you listed out, same result, no changes that I could see, and same error. I selected fbdev in tazx and it installed, but did not change anything. I'll try the isos tonight and tomorrow, and let you know.
Thanks!
TM
Offline
Without Vesa Iso stalled during boot at "Loading Console Keymap"
Same on poulsbo iso, but the font was smaller
Offline
How you start? - USB or CD?
And with the two isos you do not end up on "Welcome to your box" ?
Offline
Hi Kultex,
I made a live USB using Universal USB Installer from pendrivelinux.com for every step - been using it for years without a hitch, and this netbook has no CD rom.
Both ISO froze at the same point, "Loading Console Keymap", never made it to "Welcome to your box". I left the Poulsbo iso run overnight in case it was an extended delay, and it was in the same condition this morning.
Before I switched it off, I did note the Poulsbo iso said something to the effect of "Driver = psb_gfx", sorry I don't remember the exact line, and I did not notice on the No Vesa iso, but at least it was referenced.
Also, the Poulsbo iso had a very different screen resolution for the text, the text was much smaller. This makes me think the graphics driver may have loaded, and the stopping was due to something else. But I'm no expert, just my 2-cents.
Thanks for all your help!
TM
Offline
as I remember, rolling is not anymore compatible with pendrive linux
so change your syslinux.cfg on the stick to
# Labels
COM
LABEL slitaz
MENU LABEL SliTaz Live
COM32 c32box.c32
append linux /boot/bzImage initrd=/boot/rootfs.gz rw root=/dev/null autologin
then copy all the files of from the iso, which are in isolinux folder to the syslinux folder
and the here are the two files - just rename them on the stick to rootfs.gz
https://dl.dropboxusercontent.com/u/92249974/rootfs-ohnevesa.gz
https://dl.dropboxusercontent.com/u/92249974/rootfs-pulsbo.gz
I hope, it is clear
Offline
Can I use tazusb with the iso files or should I just go this route?
Offline
tazusb to create a live USB ?
# tazusb gen-iso2usb <your-file.iso>
Offline
Hi guys,
I tried modifying the pendrivelinux syslinux file as described, but it would not load, wound up at boot: prompt. Tried both iso files using tazusb.exe, it locked up at the copyright line ending in "Peter Alvin".
Just for laughs, I also tried it with the standard rolling, no luck.
Offline
do you have windows running on the internal disk?
the gurb4dos is working like a charm - used a week ago http://doc.slitaz.org/en:guides:frugal
and I did a stick last September like I described you, because in those days tazusb did not work at all.
how to mount a iso file to copy the files the stick:
http://www.cyberciti.biz/tips/how-to-mount-iso-image-under-linux.html
Offline
I decided to sidestep the usb issue and got a usb cd-rom. I burned a cd of standard rolling, and the cd stopped booting at the copyright line as well.
Offline
I am verry sorry about that - but to help in this case is nearly impossible, maybe somebody else has an idea
Offline
ok I have posted a new thread to get help
http://forum.slitaz.org/topic/syslinux-troubles-with-intel-atoms-pulsbo-and-c32boxc32?replies=1#post-27669
in the meantime you just give me your keyboard and your languge, maybe I have another idea..
Offline
Problems with usb booting are often down to the system timing out before it finds its root filesystem.
Try adding 'rootdelay=9' on the kernel line of the grub bootloader.
@tmoulder - can you please try bellards iso - in the other thread - I think the best would be with the stick - when it boots chnage the rootfs.gz
Offline
@ tmoulder
tried both iso files using tazusb.exe, it locked up at the copyright line ending in "Peter Alvin"
Not sure tazusb.exe works
Copying all files from /boot/isolinux/ folder of the ISO to /boot/syslinux/ folder of your stick has replaced files /boot/syslinux/c32box.c32 and /boot/syslinux/vesamenu.c32. These 2 files must come from the same version than syslinux that is installed: syslinux is 4.06 on rolling but I don't know what release uses UUI. If different it's possible it's the cause of the problem.
Try again kultex instructions without select files /boot/isolinux/c32box.c32 and /boot/isolinux/vesamenu.c32.
EDIT :
My mistake: c32box.c32 is not a file of the syslinux project. So, just the original vesamenu.c32 file mustn't be changed or you can have problem at boot.
Offline
Pages: 1
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]