Dingo Alpha 5 of 11 Jan. Issues (aka Bugs or Problems)

Message

HairyWill · #31 Post by **HairyWill** » Wed 16 Jan 2008, 08:06

John Doe wrote:If you rename 'make' to 'make-FULL' in the devx file

Do you even need to bother doing this. If you keep them the same name won't the version in the devx file just mask/overide the version in the pup_xxx.sfs if it is loaded.

John Doe · #32 Post by **John Doe** » Wed 16 Jan 2008, 08:39

HairyWill wrote:Do you even need to bother doing this. If you keep them the same name won't the version in the devx file just mask/overide the version in the pup_xxx.sfs if it is loaded.

didn't test it that way, but did think of that while typing at one point.

willing to give you odds that you are correct.

just strip out some of the logic in it and just make sure the echos for the script that is masked work prior to masking.

it's all irrelevant (but might be helpful to new users)

Dougal · #33 Post by **Dougal** » Wed 16 Jan 2008, 11:32

RE: PCMCIA

After the core driver is loaded, the device will appear in the output of lspsi/elspci and the correct module loaded like for a pci device (the modules [most of them, at least] are listed in modules.pcimap).

Sage · #34 Post by **Sage** » Wed 16 Jan 2008, 16:38

Tried to get cfdisk working with the full path specified - no go!

Pmount continues to annoy me - how to eject a CD with it?!

alienjeff · #35 Post by **alienjeff** » Wed 16 Jan 2008, 18:19

#36 Post by **Flash** » Wed 16 Jan 2008, 18:43

Alienjeff,

Sage, when I unmount a (mounted) CD, it ejects. Other than that, I have to push the eject button on the drive to eject it. Is it like that for you?

Caneri · #37 Post by **Caneri** » Wed 16 Jan 2008, 20:42

AJ...lol

It looks like someone's trying to abort a M$ Vista install...lol

Eric

BarryK · #38 Post by **BarryK** » Wed 16 Jan 2008, 23:45

Dougal wrote:RE: PCMCIA

After the core driver is loaded, the device will appear in the output of lspsi/elspci and the correct module loaded like for a pci device (the modules [most of them, at least] are listed in modules.pcimap).

That's not my problem. 'modules.pcimap' lists the PCI-to-PCMCIA interface modules, such as yenta-socket, but not the modules for a particular card, like the 'xirc2ps_cs' required by my PCMCIA network card. 'elspci' will not help either.

The old 'cardmgr' package has a database that determines what module to load for a particular card. The new 'pcmciautils' does not have that mechanism/database, or at least not that I can see.

BarryK · #39 Post by **BarryK** » Wed 16 Jan 2008, 23:48

Sage wrote:Pmount continues to annoy me - how to eject a CD with it?!

I just verified with Pmount, unmounted a CD, it automatically ejected, as per normal.

John Doe · #40 Post by **John Doe** » Thu 17 Jan 2008, 02:05

I think everyone misunderstood Sage.

I believe he is after a button to eject the CD without mounting and then unmounting it.

Rest of the JWM Config Wizard is on the way. I've got it all working, just have to write up a post later tonight and post it.

rerwin · #41 Post by **rerwin** » Thu 17 Jan 2008, 02:44

Line 49 of /etc/rc.d/rc.network is an IF statement that tests for file existence. But "-f /etc/eth[0-9]mode" is invalid because it expands internally to "-f /etc/eth0mode /etc/eth1mode", whereas the "-f" primary accepts only a single file name. The message "/etc/rc.d/rc.network: line 49: binary operator expected" (for two NICs) or ". . . [: too many arguments" (for three NICs) is generated and the conditional "sleep 3" does not occur. The message appears in /tmp/bootsysinit.log.

The following substitute statement works with multiple NIC eth?mode files (and should also with "*wireless"):

Code: Select all

if [ "`ls /etc | grep 'eth[0-9]mode\|ethernetmodules\|*wireless'`" != "" ];then

Richard

Sage · #42 Post by **Sage** » Thu 17 Jan 2008, 06:11

Is that a toaster you're poking with a paper clip, AJ?! All my paper clips are worn out - can you send a couple, please.
JD almost got it right. There is no 'EJECT' provided with Pmount. Never had any auto-ejects with the thousands of drives that passed this way.
Come on Jesse! let's have your MUT port and we can all sleep soundly again.....

disciple · #43 Post by **disciple** » Thu 17 Jan 2008, 07:14

The gimageview .pet in the repository has an & in gimageview.desktop, which causes an error if you do

Code: Select all

jwm -p

It doesn't actually seem to cause any problems, but it can be fixed by using &

John Doe · #44 Post by **John Doe** » Thu 17 Jan 2008, 07:39

Sage wrote:Is that a toaster you're poking with a paper clip, AJ?! All my paper clips are worn out - can you send a couple, please.

I almost started a poll to ask who has or doesn't have one of those bent paper clips next to them.

SHit my empty 4230-01-101-3984 has one of this in it. Much better than worrying about smokes.

Sage wrote:JD almost got it right. There is no 'EJECT' provided with Pmount. Never had any auto-ejects with the thousands of drives that passed this way.
Come on Jesse! let's have your MUT port and we can all sleep soundly again.....

I miss mut also. First thing I used to do when hitting the 'desktop' was change that icon to mut.

---

jwm config stuff tomorrow. drank too much again.

Dougal · #45 Post by **Dougal** » Thu 17 Jan 2008, 12:26

BarryK wrote:That's not my problem. 'modules.pcimap' lists the PCI-to-PCMCIA interface modules, such as yenta-socket, but not the modules for a particular card, like the 'xirc2ps_cs' required by my PCMCIA network card. 'elspci' will not help either

I was not referring to yenta-socket etc., but to the drivers for the actual devices: most of them are listed in modules.pcimap. I went over it a month or so ago and there were only a few that weren't.

dvw86 · #46 Post by **dvw86** » Thu 17 Jan 2008, 21:16

Barry,
I downloaded and tested the Jan 17th Alfa 5 (2.6.24-rc8 kernel) on the eeepc. I just copied the needed files to the internal SSD drive and used the current Grub install to boot it. It booted up and shutdown fine. Durring shutdown I saved the pup file to a SD card in the internal SD card reader slot. On reboot it found the correct file and loaded it. As a side note, one thing I noticed was that the default kernel that comes with the eeepc is 2.6.21.4

BarryK · #47 Post by **BarryK** » Thu 17 Jan 2008, 23:15

disciple wrote:The gimageview .pet in the repository has an & in gimageview.desktop, which causes an error if you do
Code: Select all
jwm -p
It doesn't actually seem to cause any problems, but it can be fixed by using &

Thanks, I fixed it.

BarryK · #48 Post by **BarryK** » Thu 17 Jan 2008, 23:20

Dougal wrote:
BarryK wrote:That's not my problem. 'modules.pcimap' lists the PCI-to-PCMCIA interface modules, such as yenta-socket, but not the modules for a particular card, like the 'xirc2ps_cs' required by my PCMCIA network card. 'elspci' will not help either
I was not referring to yenta-socket etc., but to the drivers for the actual devices: most of them are listed in modules.pcimap. I went over it a month or so ago and there were only a few that weren't.

None of the PCMCIA network drivers are in modules.pcimap. They are all the modules that end with '_cs'. The same would apply to any other specialist PCMCIA-card drivers, as these have nothing to do with PCI.

BarryK · #49 Post by **BarryK** » Thu 17 Jan 2008, 23:23

dvw86 wrote:Barry,
I downloaded and tested the Jan 17th Alfa 5 (2.6.24-rc8 kernel) on the eeepc. I just copied the needed files to the internal SSD drive and used the current Grub install to boot it. It booted up and shutdown fine. Durring shutdown I saved the pup file to a SD card in the internal SD card reader slot. On reboot it found the correct file and loaded it. As a side note, one thing I noticed was that the default kernel that comes with the eeepc is 2.6.21.4

That's good news.
My experiences with the 2.6.24-rc4 and -rc8 have been very positive. I intend to wait until it is released before releasing Dingo beta.

JustGreg · #50 Post by **JustGreg** » Fri 18 Jan 2008, 03:12

I did a fresh install to a 1 gigabyte USB flash device. I used an external USB CDROM with the iso to boot the Eee PC and do the installation to the USB flash device. Everything when well expect for the dreaded Syslinux unsafe /tmp permissions error. Saved a pup_save.2fs to the device. Rebooted and used Xandros to complete the syslinux process. Booted the USB device and it worked. The Dingo gold screen looks better on the small screen for some reason. The proper screen resolution (800x480) was available in both Xvesa and Xorg. I tried both video servers with no problems. The only thing missing was the network modules for the ETHERNET and WIFI cards. I could not try the networking.
The sound work fine at the start. I got the two "woofs". This version should work nicely once the card modules for networking are available.

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

Dingo Alpha 5 of 11 Jan. Issues (aka Bugs or Problems)

Re: Idea for devx, to help new users

Re: Idea for devx, to help new users

Invalid IF statement in rc.network script

Jan 17th Alfa 5

Re: Jan 17th Alfa 5