(old)Puppy Linux Discussion Forum

Minnesota wrote:Boot halts with tiny print on the screen. I suspect, wizard has adjusted the video. NOTHING till I hit enter then something flashes on the screen. I get a desktop...Icons seem large, yet hardware info shows 1040x.

I am getting something similar, but only in PUPMODE=5 - a frugal install with no pupsave. I need to type "xwin" to get a desktop. I'm sure that no previous version behaved like this.

Also, sfs_load is still broken because of the change in kernel number. However, when I try to force it into SFSVER=4, the program breaks. (???)

Also, sfs_load is still broken because of the change in kernel number.

Sorry, somehow I didn't put that in. I'll attach a pet to fix it.

I am getting something similar, but only in PUPMODE=5 - a frugal install with no pupsave. I need to type "xwin" to get a desktop. I'm sure that no previous version behaved like this.

What kind of graphics card is that with?

kirk wrote:

Also, sfs_load is still broken because of the change in kernel number.

Sorry, somehow I didn't put that in. I'll attach a pet to fix it.

Your PET does the same weird thing as my patch. It breaks the gtkdialog so the file chooser icon no longer appears. Maybe someone else can test this.

kirk wrote:

I am getting something similar, but only in PUPMODE=5 - a frugal install with no pupsave. I need to type "xwin" to get a desktop. I'm sure that no previous version behaved like this.

What kind of graphics card is that with?

It's an old ATI Radeon Xpress 200G. But I believe that I also saw it happen on a newer machine with Intel graphics.

This morning I reported PPM update not working

Now, It working fine as you can seeMaybe a glitch somewhere between then and now. Interestingly, I was able to surf the web, and access the FATDOG site for PETs. But the PPM was not cooperating as it always had.

I ran some tests on a newer machine with Intel graphics and the video worked fine.

However, the sfs_load bug continues. The gtkdialog doesn't render properly.

First, I'd like to say great job on Fatdog64! Since I've bought my new Toshiba laptop (Satellite L755-5216), I've not been able to get if fully operational with Puppy 5.2.8 or 5.2.9 (referring to http://www.murga-linux.com/puppy/viewtopic.php?t=71023). Regardless I luv Puppy and it's only a matter of time before it'll will work out.

Last night, for S&Gs I tried Fatdog64, since the laptop came with 64-bit Win 7. Well, using Fatdog64, my video looks good (screen is at native resolution). I get audio (another positive). But my wifi nic was not recognized. So after some research, I found the

firmware-realtek_0.28_all.deb

file and installed it. Now I see my Realtek wifi nic. Although I'm prompted to setup and login into my router, it comes up as WPA and not WPA2. In any case, Fatdog says I'm connected but I cannot access the internet.

I went into the wireless diagnostics and created the attached tar.gz file. Any ideas? Thanks!

rcrsn51 wrote:

Minnesota wrote:Boot halts with tiny print on the screen. I suspect, wizard has adjusted the video. NOTHING till I hit enter then something flashes on the screen. I get a desktop...Icons seem large, yet hardware info shows 1040x.

I am getting something similar, but only in PUPMODE=5 - a frugal install with no pupsave. I need to type "xwin" to get a desktop. I'm sure that no previous version behaved like this.

This didn't happen to me on all the machines I throw 520 at - ATI, nvidia, Intel (I don't have any SIS graphics) - desktop, notebook, netbook. Not saying that it's not happening, but I can't reproduce it. I've looked at the code in /etc/rc.sysinit and /etc/profile, there isn't anything that stops the desktop waiting fro the key - except testing for previous run of Xorg /tmp/bootcnt.txt.

The messages are But these old ATI graphics have always been a bit wonky, so I'm not going to worry about it.

Has anyone else tested SFS-load-on-the-fly?

rcrsn51 wrote:The messages are

Code: Select all

/usr/X11R17/bin/Xinit (errno 11):
unable to connect to X server
no such process (errno 3): server error

This simply means that Xorg can't start. There may be additional error messages in /var/log/Xorg.0.log ... but it's really odd if you can then run "xwin" and everything works. Sounds like something is slow to start so that Xorg failed the first time, but then works the second time.

Now that I'm thinking about this, it may explain Sage's perceived slowness. Somewhere in beta/rc stage, kirk made acpid start synchronously (before that it started in the background), because sometimes Xorg started before acpid was fully running and it behaved weirdly. This means the whole boot process now needs to wait until acpid is ready - and that could explain why the boot process is now longer.

But these old ATI graphics have always been a bit wonky, so I'm not going to worry about it.

I agree heartily and won't pursue this further

Has anyone else tested SFS-load-on-the-fly?

Yes, in frugal install mode (PUPMODE=12), the fix works. But remember - try not to exceed the 6-SFS limit. If you exceed 6-SFS limit, weird things will happen (I can load beyond the 6-SFS limit but can't unload).

joe0855, I will get back to you when I have an answer. If you don't hear from me that means I don't have an answer for you

jamesbond wrote:

Has anyone else tested SFS-load-on-the-fly?

Yes, in frugal install mode (PUPMODE=12), the fix works.

I finally got it working. For some reason, sfs_load was detecting the presence of puppy_slacko-4.99.4.sfs in the same partition as Fatdog and the gtkdialog was choking on it.

Once I renamed that file, sfs_load was fine.

The box that I thought was a 939 turned out to be yet another recently acquired 754. Having discovered the real 939 , FD turned out to be a bit of a disaster - so many issues I haven't the time to record/list, so running it on Slacko and LM-LXDE11. [Slacko not without it's own' features', but these I can live with.]

joe0855,

You might give the Network Wizard a try. If the firmware isn't too huge we'll include it.

Also, I've fixed the dbus pet.

FYI: I have uploaded the contents of the emachines AMD Fusion laptop /tmp files here hopefully to help in hacking a solution to the hanging problem (even Slacko B2 hangs in that machine, but Fatdog64 511 does not).

Thanks Jamesbond and Kirk.

I tried using the Network Wizard (depreciated), which does allow more flexibility to choose the correct WPA protocol. However still no outside access to the internet (tried WPA/TKIP and WPA2). Frisbee is also a nogo.

I am however able to access my wireless router using the default browser. I can also ping internal IPs (ie 192.168.1.5) using the terminal application.

I then tried changing my browser settings to 'No proxy', still nogo.

Man, I'm sooo close. Got my video, audio... but wifi is kinda important though

Kirk, please pardon my ignorance, but what does the dbus pet do. Found 'dbus-1.2.16.pet' on the FD64 ibiblio, installed it but didn't notice any differences. Thanks again!

joe0855,

Can you ping 208.67.222.222? If you can then you are getting out to the internet and your DNS settings are wrong for some reason. /etc/resolv.conf contains the address to your DNS server. If you can ping 208.67.222.222, then put that in /etc/resolv.conf and try that. The dbus pet is only needed if you install some external package that requires dbus. Fatdog64 packages are compiled without dbus. The firmware you mentioned is already included.

raffy,

You said that your ati video works in 511. The big difference between 511 and 520 for radeon is that KMS is enabled by default. Try booting with nomodeset. The ati driver is supposed to run with or without KMS. All of the drivers have been updated as well and that could be the problem in your case.

Hi,
Just a question about the compiling of VLC.
Firstly any plans for a new compile?
If yes could you compile in the option for DVB

Or if the answers no could you post the options that were previously used as I'd like to have a go at compiling in a DVB option but don't know what else to include.
Any other tips for compiling for fat dog would also be appreciated.

thanks

DC

Try booting with nomodeset.

My old ATI Radeon Xpress card works much better with this option.

Tested on an old Sempron machine (I didn't realize that it was 64-bit) with nVidia graphics. Worked fine. Booted off a flash drive along with the devx. Used jamesbond's load-sfs tool and compiled some packages. Very quick.

gcmartin wrote:Responders here in this Off-Topic thread seemingly are not struggling with finances for computing resources or entertainment needs. I would bet that most, if not all, of this subset of forum users have at least 1, if not more that 1, 64bit PCs.

I don't see the connection. There is now lots of old 64-bit hardware around in the surplus market.

DC,

I re-uploaded the vlc-1.1.11.pet with dvb enabled and lirc too. I've tested nether function though. Xine works nice for me .

There is now lots of old 64-bit hardware around in the surplus market.

Untrue! Although I have a few, that's just because folks know of my interests in HW - and all were 'repair jobs'. If you read other threads, and more importantly, other Fora, you'd realise that the world doesn't stop at NYC, or, in your case, Newfoundland! Still plenty of 486/PI&II/Durons out in RoW. And don't forget, the world's richest nation has 50m folks living in total destitution, who not only don't have a PC, they live on the roadsides with nowhere to plug in...